home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Standards
/
CD2.mdf
/
ccitt
/
1992
/
t
/
t330_3.asc
< prev
next >
Wrap
Text File
|
1991-12-31
|
89KB
|
3,933 lines
The drawaing contained in this Recommendation have been done in Autocad
10.2 Operation of the TLMAU
The section describes how the TLMAU will provide the TLM abstract service.
The TLM abstract operations have been defined by abstract operations, sometimes
with associated results or errors. These abstract operations, results and errors
are realized via the exchange of TAPDUs between the TLM terminal and the TLMAU.
The realization of the abstract operations for the import and export ports
linking the TLMAU and the MTS, is beyond the scope of this Recommendation. For
the purpose of this section import and export operations will be considered to be
similar to submission and delivery port operations.
10.2.1 MessageSend
The MessageSend operation will be provided by the TLMAU via the Send-,
SendAck- and Exception-TAPDUs:
Upon receipt of Send-TAPDU by the TLMAU, the TLMAU will take the following
actions:
1) The TLMAU will invoke the MTAS import abstract operation
MessageSubmission with the following argument values:
Source of MTAS MessageSubmission arguments
CorrespondingSend-TAPDU
component
MessageSubmission argument Element Value name Operation
name
originator-name - - Authenticate User
(remarque 1)
original-encoded-informati - - set by TLMAU to EITs of
on-types submitted IPM's body
content-type - - set by TLMAU to "IPMS"
content-identifier - - Local matter
content-correlator - - Local matter
PAGE36 Fascicle VII.5 - Rec.T.330
recipient-name to, cc, primary-, constructed by TLMAU
bcc copy-,
blind-copy-recip
ient
Note 1 - Authenticate User is constructed from TID obtained from CSS terminal ID.
Note 2 - The IPM submitted as the content is constructed by the TLMAU. Send-TAPDU
components representing IPMS elements are mapped onto the corresponding IPMS
application protocol data unit (APDU) elements.
Note 3 - A multi-document messages will be submitted as an IP message with a
multi-part body, each body part corresponding to a submitted document.
Note 4 - When this-IPM of IPMS element is omitted, the TLMAU shall construct this
component which consists of the following components: originator name, Date and
Time and, if necessary, a sequence number.
Fascicle VII.5 - Rec.T.330 PAGE57
Other message submission arguments have a corresponding Send-TAPDU
component. If this component is omitted, the default value applies.
2) If the MessageSubmission operation results in an error or if an error
is detected in the Send-TAPDU, the TLMAU will return an Exception-TAPDU
to the originating TLM terminal.
3) The TLMAU will, when required, return a SendAck-TAPDU to the
originating TLM terminal following the successful completion of the
MessageSubmission operation. The values of the SendAck-TAPDU will be
set as follows:
Source of SendAck-TAPDU components
SendAck-TAPDU component
Element name Value name Source
correlationInf call-id CallIdentification that
o identifies previous Send-TAPDU
being reported on
submissionId submission-msg MTS
-id message-submission-identifier
submissionTime submission-tim MTS message-submission-time
e
4) The TLMAU will maintain a one-to-one correlation between MTS
message-submission-identifiers and correlation information values to
facilitate status query.
10.2.2 MessageProbe
The MessageProbe operation is provided by the TLMAU via the Probe-,
ProbeAck- and Exception-TAPDUs.
Upon receipt of the Probe-TAPDU by the TLMAU, the TLMAU will take the
following actions:
1) The TLMAU will invoke the MTAS import abstract operation
ProbeSubmission with the following argument values:
Source of MTAS ProbeSubmission arguments.
See S 10.2.1 - MessageSubmission arguments.
2) If the Probe operation results in an error or if an error is detected
in the Probe-TAPDU, the TLMAN will return an Exception-TAPDU to the
originator.
3) The TLMAU will, when required, return a ProbeAck-TAPDU to the
originator, following the successful completion of the probe operation.
The values of the ProbeAck-TAPDU will be set as follows:
PAGE36 Fascicle VII.5 - Rec.T.330
Source of ProbeAck-TAPDU components
ProbeAck-TAPDU component
Element name Value name Source
correlationInf call-id CallIdentification that
o identifies previous Probe-TAPDU
being reported on
probeId probe-msg-id MTS probe-submission-identifier
submissionTime MTS probe-submission-time
submission-tim
e
10.2.3 ExplicitReceive
The ExplicitReceive operation is provided by the TLMAU via the
ExplicitRN-, ExplicitRNAck- and Exception-TAPDUs.
Upon receipt of the ExplicitRN-TAPDU the TLMAU will take the following
actions:
1) The TLMAU will invoke the MTAS import abstract operation
MessageSubmission with the following argument values:
Source of MTAS MessageSubmission components
Corresponding
MessageSubmiss ExplicitRN-TAPDU Operation
ion argument component
Element Value name
name
originator-nam - - authenticate user
e
original-encod
Fascicle VII.5 - Rec.T.330 PAGE57
ed-information - - set by TLMAU to "unspecified"
-types
content-type - - set by TLMAU to "IPMS"
content-identi - - Local matter
fier
priority priority
priority-in
d
per-message-in
dicators - - set to
disclose-recip - - "disclosure-of-recipient-prohibi
ients - - ted"
conversion-pro - - set to "conversion-prohibited"
hibited set to
alternate-reci "alternate-recipient-prohibited"
pient-allowed set to
content-return "content-return-not-requested"
-request
recipient-name recipients recipient-n
ame
originator-rep - - set by TLMAU to "no report"
ort-request
content - - identified as IPN
Note 1 - The IPN submitted as the content is constructed by the TLMAU.
PAGE36 Fascicle VII.5 - Rec.T.330
ExplicitRN-TAPDU elements representing IPMS elements are mapped onto the
corresponding IPMS APDU elements.
Note 2 - If receipt-time is omitted, the TLMAU extracts the Receipt time from the
CSS of the session in which this TAPDU was transferred to. This time may differ
from the time of actual receipt of IPM.
Note 3 - Set acknowledgment-mode of IPN to "manual".
2) If the Message-Submission operation results in an error, or if an error
is detected in the ExplicitRN-TAPDU, the TLMAU will return an
Exception-TAPDU to the originator.
3) The TLMAU will, when required, return a ExplicitRNAck-TAPDU to the
originator, following the successful completion of the
MessageSubmission operation. The values of the ExplicitRNAck-TAPDU will
be set as follows:
Source of ExplicitRNAck-TAPDU components
ExplicitRNAck-TAPDU component
Element name Value name Source
correlationInf call-id CallIdentification that
o identifies previous
ExplicitRN-TAPDU being reported
on
submissionId submission-msg MTS
-id message-submission-identifier
submissionTime submission-tim MTS message-submission-time
e
10.2.4 MessageCancel
The MessageCancel operation is provided by the TLMAU via the Cancel- and
Exception-TAPDUs.
Upon receipt of the Cancel-TAPDU by the TLMAU, the TLMAU will take the
following actions:
The TLMAU will invoke the MTAS abstract operation CancelDeferredDelivery
with the following argument value:
Source of CancelDeferredDelivery arguments
Corresponding Cancel-TAPDU
component
CancelDeferredDe Element name Value name Operation
livery argument
message-submissi submissionId
on-identifier
Fascicle VII.5 - Rec.T.330 PAGE57
submission-msg-i
d
If the CancelDeferredDelivery operation results in an error, or if an
error is detected in the Cancel-TAPDU, the TLMAU will return an Exception-TAPDU
to the originating TLM terminal.
10.2.5 MessageDeliver
The MessageDeliver operation is provided by the TLMAU via the
Deliver-TAPDU.
When the MTAS abstract operation MessageDelivery is invoked by the MTS
with an IPM as the MTS message content, the TLMAU will take the following
actions:
1) The TLMAU will construct a Deliver-TAPDU for transmission to the
destination TLM terminal with the following element values:
PAGE36 Fascicle VII.5 - Rec.T.330
Source of Deliver-TAPDU component
Deliver-TAPDU component Corresponding MessageDelivery
argument Operation
Element Value name
name
when control
Information is
conveyed by a
quantityO number-of-docs - normal document,
fDocs set number of
associated
documents in
Deliver-TAPDU
priority priority-ind priority
originato originator-name originator-name
r
thisRecip this-recipient-name
ient this-recipient-name
intendedR
ecipient intended-recipient- originally-intended-recipient
name -name
otherReci other-recipient-names
pients other-recipient-nam
e
Fascicle VII.5 - Rec.T.330 PAGE57
submissio submission-time message-submission-time
nTime
timeOfDel delivery-time message-delivery-time
ivery
deliveryI delivery-msg-id message-delivery-identifier
d
conversio eIT
nIndicati original-encoded-information-
on types
conversio delivery-flags
nIndicati conversion-prohibit
on ed
converted eIT
InfoTypes converted-encoded-information
-types
Note 1 - The IPM received by TLMAU is used to construct the Deliver-TAPDU,
Deliver-TAPDU elements, representing MTS and IPMS elements of service, are
constructed by the TLMAU from the MessageDeliver operation arguments and IPMS
application protocol data unit (APDU) values as indicated above.
Note 2 - Multi-part body message will be sent to the destination TLM terminal by
the TLMAU as a multi-document message, each document corresponding to an IP
message body part.
2) If the TLMAU is unable to deliver the constructed Deliver-TAPDU to the
designation TLM terminal, then an IPN will be constructed for return to
the IPMS originator. This IPN will be submitted according to S 10.2.6.
3) The definition of the export port MessageDeliver abstract operation
should include a result argument indicating successful delivery or
non-delivery. The MTS would then return delivery notifications to the
originators of messages routed through a TLMAU only after the result
value was indicated.
10.2.6 ReceiptStatus Notice
The ReceiptStatusNotice operation is provided by the TLMAU via the
ReceiptStatusNotice-TAPDU.
When the MTAS abstract operation MessageDelivery is invoked by the MTS
with an IPN as the IPMS content, the TLMAU will take the following actions:
1) The TLMAU will construct a ReceiptStatusNotice-TAPDU for transmission
to the destination TLM terminal with the following element values:
Source of ReceiptStatusNotice-TAPDU components
ReceiptStatusNotice-TAPDU Corresponding
component
PAGE36 Fascicle VII.5 - Rec.T.330
MessageDelivery and Operation
Element Value name receive RN/NRN argument
name
when control
Information is
conveyed by a
quantityO number-of-docs - normal document,
fDocs set number of
associated
documents in
ReceiptStatusNot
ice-TAPDU
priority priority-ind priority
deliveryI delivery-id message-delivery-identifi
d er
if this element
is omitted, this
originato originator-name originator-identifier argument should
r be constructed
from TID obtains
from CSS
thisRecip this-recipient-nam this-recipient-identifier
ient e
submissio submission-time message-submission-time
nTime
timeOfDel delivery-time message-delivery-time
ivery
Fascicle VII.5 - Rec.T.330 PAGE57
conversio eIT original-encoded-informat
nIndicati ion-types
on
conversio conversion-prohibi delivery-flags
nIndicati ted
on
converted eIT converted-encoded-informa
InfoTypes tion-types
notificat report-type choice
ionType
subjectIP subject-ipm-id subject-ipm
M
iPNOrigin ipn-originating-us ipn-originator
ator er
preferred preferred-recipien ipm-preferred-recipient
Recipient t
timeOfRec receipt-time receipt-time
eipt
PAGE36 Fascicle VII.5 - Rec.T.330
typeOfRec type-of-receipt acknowledgment-mode
eipt
supplRece suppl-receipt-info suppl-receipt-info
iptInfo
nonReceip non-receipt-reason non-receipt-reason
tInfo
nonReceip discard-reason discard-reason
tInfo
comment comments auto-forward-comment
messageRe - returned-ipm
turnedInd
Note - What is received by the TLMAU is used to construct the
ReceiptStatusNotice-TAPDU. ReceiptStatusNotice-TAPDU elements representing MTS
and IPMS elements of service, are constructed by the TLMAU from the
MessageDeliver operation arguments and IPMS APDU values, as indicated above.
Fascicle VII.5 - Rec.T.330 PAGE57
10.2.7 DeliveryStatusNotice
The DeliveryStatusNotice operations are provided by the TLMAU via the
DeliveryStatusNotice-TAPDU.
When the MTS abstract operation ReportDelivery is invoked by the MTS, the
TLMAU will take the following actions:
1) The TLMAU will construct a DeliveryStatusNotice-TAPDU for transmission
to the destination TLM terminal with the following element values:
Source of DeliveryStatusNotice-TAPDU components
DeliveryStatusNotice-TAPDU Corresponding ReportDelivery Operation
component argument
Element Value name
name
when control
Information is
conveyed by a
quantityO number-of-docs - normal document,
fDocs set number of
associated
documents in
DeliveryStatusNo
tice-TAPDU
CallIdentificati
correlati call-id - on that
onInfo identifies
previous
Send-TAPDU being
reported on
priority priority-ind priority
submissio submission-id subject-identifier
nId
probeId submission-id subject-identifier
reportedR
PAGE36 Fascicle VII.5 - Rec.T.330
ecipient reported-recipient- actual-recipient-identifier
name
notificat report-type report
ionType
intendedR intended-recipient- originally-intended-recipien
ecipient name t
converted eIT converted-encoded-informatio
InfoTypes n-types
timeOfDel delivery-time message-delivery-time
ivery
typeOfUA type-of-ua type-of-MTS-user
nonDelive reason-code non-delivery-reason-code
ryReason
nonDelive diagnostic-code non-delivery-diagnostic-code
ryReason
contentRe
Fascicle VII.5 - Rec.T.330 PAGE57
turned returned-content
2) When required, the TLMAU will accumulate notifications pertaining to a
single Send-TAPDU and construct a single DeliveryStatusNotice-TAPDU
from multiple ReportDelivery operations.
10.2.8 Register
The register operation is provided by the TLMAU via the register-,
RegisterAck- and Exception-TAPDUs.
Upon receipt of the Register-TAPDU, the TLMAU will take the following
actions:
- If a message delete mode was selected, the TLMAU will subsequently
operate according to the new mode with respect to messages output from
the DS of the TLM terminal originating the Register-TAPDU.
- If an error recovery mode was selected, the TLMAU will subsequently
handle error recovery according to the selected criteria for all
transactions with the originator of the Register-TAPDU.
- If a DS mode was selected, the TLMAU will subsequently either hold for
retrieval, or auto output messages in the DS of the originator of the
Register-TAPDU according to the DS mode selected in this TAPDU.
- If the auto discard mode was enabled by the Register-TAPDU, then the
TLMAU will commence automatic deletion of messages in the DS belonging
to the originator of the Register-TAPDU when they are obsoleted by
subsequent received IPM's.
- If the auto acknowledgement function was enabled by the Register-TAPDU,
then the TLMAU will automatically format and submit receipt
notifications for subsequent IP messages directed to the originator of
the Register-TAPDU. These notifications will be submitted, either
following successful delivery of the IP message to the TLM terminal, or
upon deposit of the IP message in the TLM terminal's DS.
- If an error is detected with the Register-TAPDU, the TLMAU will return
an Exception-TAPDU to the originator.
10.2.9 DSList
The DSList operation is implemented by the TLMAU as an internal operation
and does not involve the MTS. The DS list operation is provided via the DSQuery-,
DSReport- and Exception-TAPDUs as follows:
Upon receipt of the DSQuery-TAPDU by the TLMAU, the TLMAU will take the
following actions:
- The TLMAU will prepare a DSReport-TAPDU for return to the originator.
If there are no messages in DS, the DSReport-TAPDU will indicate this.
- If an error is detected with the DSQuery-TAPDU, the TLMAU will return
an Exception-TAPDU to the originator.
10.2.10 DSDelete
The DSDelete operation is implemented by the TLMAU as an internal
operation and does not involve the MTS. The DS Delete operation is provided via
the DSDelete- and Exception-TAPDUs as follows:
- The TLMAU will delete the indicated message(s) from the DS.
- If an error is detected with the DSDelete-TAPDU or the message
indicated is not available for deletion, the TLMAU will return an
Exception-TAPDU to the originator.
10.2.11 DSFetch
The DSFetch operation is implemented by the TLMAU as an internal operation
and does not involve the MTS. The DSFetch operation is provided via the
OutputRequest-, OutputMessage- and Exception-TAPDUs as follows:
Upon receipt of the OutputRequest-TAPDU by the TLMAU, the TLMAU will take
the following actions:
- For each message indicated in the OutputRequest-TAPDU and found in the
DS, the TLMAU will prepare and return an OutputMessage-TAPDU.
- If the delete-after-output function was indicated in the
OutputMessage-TAPDU the TLMAU will delete the indicated message(s) from
the DS after output.
- If the "auto delete" message delete mode is subscribed to then the
TLMAU will delete the indicated message(s) from the DS after output
regardless of whether the delete-after-output function was selected in
the OutputRequest-TAPDU.
- If an error is detected with the OutputRequest-TAPDU or the message(s)
indicated were not available for output, the TLMAU will return an
PAGE36 Fascicle VII.5 - Rec.T.330
Exception-TAPDU to the originator. If some of a list of indicated
messages are available in DS then the TLMAU will output those
available, and then return an Exception-TAPDU for those not available
or incorrectly indicated.
- If the "auto output" DS mode is subscribed to then the output and
associated deletion functions will be executed when the user subscribed
conditions are met.
10.2.12 OutputMessage
The delivery-time in this TAPDU is the time when the DS received the
message.
10.2.13 MessageStarus
The MessageStatus operation is implemented by the TLMAU as an internal
operation and does not involve the MTS. This operation is applicable only when
the TLMAU accumulates notifications for previously submitted multi-address
messages. The operations provided by the TLMAU via the StatusQuery-,
StatusReport-and Exception-TAPDUs.
Upon receipt of the StatusQuery-TAPDU by the TLMAU, the TLMAU will take
the following actions:
- The TLMAU will construct a StatusReport-TAPDU from accumulated
notifications pertaining to the message identified in the
StatusRequest-TAPDU.
- The TLMAU will not allow StatusQuery operation for ReceiptStatusNotice.
- If an error is detected with the StatusReport-TAPDU or there is no
record of the message indicated, the TLMAU will return an
Exception-TAPDU to the originator.
11 Formats and encoding of TAPDU
11.1 Principles
Elements of a telematic access protocol data unit (TAPDU) shall be coded
using human-readable graphic characters of Recommendation T.61 coding scheme.
Other coding rules such as mechine-readable coding are for further study.
11.2 Structure of TAPDU
1) A TAPDU is composed of one or more documents. The first one contains
control information optionally followed by one or more documents with
text (message body information). Within one session one or more TAPDU
may be conveyed.
2) Control information is conveyed in either a control document or a
normal document.
3) The control information is subdivided into a TAPDUs and elements each
containing a number field and/or name field, and optionally one or more
element value fields. An element number field, which is language
independent, and the element name, which is language dependent,
uniquely identify an element. In case of international access, the
element number field must always be present.
4) The value fields of an element may contain the same TAPDU information
types or different TAPDU information types. The element value fields
(called components) are categorized as follows:
- components with pre-defined values, i.e. components with a
specific, enumerable set of known, unique values (predefined
value);
- components with a wide range of values which are not pre-defined
(general value).
5) There are two different types of component fields:
- primitive component;
- constructor component.
6) Each primitive component contains only one parameter. Each constructor
component contains more than one parameter.
7) A parameter contains a parameter value, optionally preceded by a
Parameter-Id, which identifies the parameters.
8) The formal description of the structure of a TAPDU is shown in Table
3/T.330.
9) A line may contain an Element-Id field and component fields, or the
Fascicle VII.5 - Rec.T.330 PAGE57
first component field of the element starts on a new line.
10) If the number of characters of the component exceeds the remaining
number of characters on this line, the component must be divided into
two or more lines by "NL" function. However, it is not allowed to
divide the component within a parameter.
PAGE36 Fascicle VII.5 - Rec.T.330
TABLE 3/T.330
The structure of TAPDUs
TAPDU ::= SEQUENCE {
ControlInfo,
SEQUENCE OF MessageBodyInfo
OPTIONAL },
ControlInfo ::= SEQUENCE {
TAPDUId,
Elements OPTIONAL }
TAPDUId ::= SEQUENCE {
TAPDUNumber OPTIONAL,
TAPDUName OPTIONAL }
-- One of this must be present.
Elements ::= SEQUENCE {
ElementId,
ElementValues }
ElementId ::= SEQUENCE {
ElementNumber OPTIONAL,
ElementName OPTIONAL }
-- One of this must be present.
ElementValues ::= SET OF Component
-- See Note
Component ::= CHOICE {
PrimitiveComponent,
ConstructorComponent }
PrimitiveComponent ::= Parameter
ConstructorComponent ::= SET OF Parameter
Parameter ::= SEQUENCE {
ParameterId OPTIONAL,
ParameterValue }
Note - Order of components as prescribed by the TAPDU descriptions in S 10.
11.3 Coding rule
11.3.1 TAPDU ID
1) The TAPDU number assigned to TAPDU shall consist of two parts separated
by a "period" (.). The first part identifies the application, for
example, "3" is assigned to this application. The second part
identifies the procedures specified in the application.
2) Where national requirements dictate the use of non-standardized TAPDU
numbers. Administrations may choose any values in the range 1000-1999
for the first part of non-standardized application identifiers.
3) Other rules applied to TAPDU number and name are same as those of the
element number and name, described below.
11.3.2 Element ID
1) The element number shall be sequentially assigned a different number.
2) An element number is always closed by the character "colon" (:).
3) There shall be no restriction of the number of digits for element
numbers and any leading zeros are ignored.
4) Where national requirements dictate the use of non-standardized element
numbers Administrations may choose any values in the range 1000-1999
for non-standardized elements.
charac
character "space".
6) An element name shall be represented by a text string, that is a
sequence of graphic characters. Capital and small characters have the
same effect.
7) An element name is always closed by the character "colon" (:).
11.3.3 Element value fields
For unregistered TLM-users with international access, the pre-defined
values as defined in the following tables have to be applied. For all other
Fascicle VII.5 - Rec.T.330 PAGE57
cases, these values can be replaced by nationally defined values.
11.3.4 Separators and common rules
1) TAPDU-Ids and elements shall be preceded by the following delimiters:
- "CR LF" sequence, or
- "CR LF BS +" sequence.
2) The Element-Id and the first component shall be separated by the
character "space" or "New Line" functions ("NL" = "CR LF" or "LF CR").
3) Components shall be separated by "comma" (",") and optionally "NL".
4) When components with pre-defined and not pre-defined values are
contained in an element, they shall be separated by a "NL" and the line
with the pre-defined values should start with the character "=".
5) Parameters within one component field shall be separated by the
character "slash" ("/") or "semicolon" (";"). "CR LF" within a
parameter is not allowed, except if the parameter is longer than 1
line.
6) The actual value of a parameter value is encoded by a sequence of
graphic characters. Capital and small characters have the same effect.
7) If some pre-defined values are absent but required, then their default
value shall apply.
8) The element ID and the first element value field shall be separated by
the character "space" or the "NL" function.
9) Contiguous "NL" and "LF" are considered as one "NL".
10) Contiguous embeded space are considered as one space. Leading spaces in
a line are ignored.
11) The character sequence "Space //" indicates that the following of the
line shall be considered as a comment.
11.4 Format of TAPDU
The format of each TAPDU according to the above coding rules is shown in
Annex C of this Recommendation.
11.5 Reference between TAPDU components and its coding format
This section provides the tables necessary for the encoding of TAPDU
components.
11.5.1 TAPDUId and elementId (see Table 4/T.330)
Table 4/T.330 comprises four columns:
1) The first column contains the TAPDUId or Element-Id name as used in the
ASN.1 description of S 10.
2) The second column contains the type of this element:
a) primitive: the element contains only one elementValue field;
b) constructor: the element may contain more than one elementValue
field.
3) The third column contains the actual coding format of the TAPDUId or
element-Id.
4) The last column contains remarks.
11.5.2 ElementValues (see Table 5/T.330)
Table 5/T.330 comprises five columns:
1) The first column contains the ElementValue name (component name) as
used in the ASN.1 description of S 10.
2) The second column contains the type of ElementValue field:
a) primitive: the component contains only one parameter;
b) constructor: the component may contain more than one parameter.
3) The third column contains the type of the value:
a) predefined;
b) general, as defined in this section.
PAGE36 Fascicle VII.5 - Rec.T.330
4) The fourth column contains the actual coding format, or, in case of
general value, a reference name which points to the actual coding
format in Table 6/T.330.
5) The last column contains remarks.
11.5.3 General values (see Table 6/T.330)
Table 6/T.330 comprises five columns:
1) The first column contains the reference name (general value name) used
in Table 5/T.330.
2) The second column contains the name of the parameter.
3) The third column contains the code of the value.
4) The fourth column contains the keyword and format of this parameter.
5) The last column contains remarks.
Fascicle VII.5 - Rec.T.330 PAGE57
TABLE 4/T.330
Format encoding of TAPDU and ElementId
TAPDUId Type T.61 Character coding format Remarks
and
Element
Id name
authori Constructo 21:AUTHORIZING:
zing r
autoFWD Primitive 79:AUTO-FWD-COMMENT:
Comment
autoFWD 78:AUTO-FWD-HEADING: for further
Heading study
autoFWD Primitive 76:AUTO-FWD-IPMS:
IPMs
autoFWD Constructo 77:AUTO-FWD-RECIPIENTS:
Recipie r
nts
autoOut Constructo 60:AUTO-OUTPUT:
put r
bcc Constructo 24:BCC:
r
PAGE36 Fascicle VII.5 - Rec.T.330
bodyTyp Constructo 31:BODY-TYPE:
e r
cancel - 3.13:CANCEL:
cc Constructo 23:CC:
r
comment Primitive 50:COMMENT:
content Constructo 18:CONTENT-INDICATOR:
Indicat r
or
content Primitive 17:CONTENT-INFO:
Info
content - 72:CONTENT-RETURNED-INDICATION:
Returne
d
convers Primitive 16:CONVERSION:
ion
Fascicle VII.5 - Rec.T.330 PAGE57
convers Constructo 42:CONVERSION-INDICATION:
ionIndi r
cation
convert Primitive 44:CONVERTED-INFORMATION-TYPES:
edInfoT
ypes
correla Primitive 1:CORRELATION-INFORMATION:
tionInf
o
deleteA Primitive 80:DELETE-AFTER-OUTPUT:
fterOut
put
deliver - 3.3:DELIVER:
deliver Primitive 35:DELIVERY-ID:
yId
deliver - 3.4:DELIVERY-STATUS-NOTICE:
yStatus
Notice
dsMode Primitive 58:DS-MODE:
dsQuery
PAGE36 Fascicle VII.5 - Rec.T.330
- 3.7:DS-QUERY:
dsRepor - 3.8:DS-REPORT:
t
errors Primitive 9:ERRORS:
excepti - 3.12:EXCEPTION:
on
expired Primitive 73:EXPIRED-DISCARD:
Discard
explici - 3.6:EXPLICIT-RN:
tRN
explici - 3.16:EXPLICIT-RN-ACK:
tRNAck
forward Constructo 32:FORWARDED-INFO:
edInfo r
from Primitive
Fascicle VII.5 - Rec.T.330 PAGE57
20:FROM:
PAGE36 Fascicle VII.5 - Rec.T.330
TABLE 4/T.330 (cont.)
TAPDUId Type T.61 Character coding format Remarks
and
Element
Id name
orgInte Primitive 40:INTENDED-RECIPIENT:
ndedRec
ipient
iPNOrig Primitive 69:IPN-ORIGINATOR:
inator
languag Primitive 53:LANGUAGE:
e
latestD Primitive 34:LATEST-DELIVERY:
elivery
message - 3.18:MESSAGE-DELETE:
Delete
message Primitive 81:MESSAGE-DELETE-MODE:
DeleteM
ode
message Primitive 37:MESSAGE-LENGTH:
Length
Fascicle VII.5 - Rec.T.330 PAGE57
message - 51:MESSAGE-RETURNED-INDICATION:
Returne
dInd
message Primitive 82:MESSAGE-SELECTOR:
Selecto
r
message Primitive 83:MESSAGE-STATUS:
Status
message Primitive 52:MESSAGE-TYPE:
Type
msgInco - 67:MSG-INCOMPLETE: This element
mplete has not
value
Primitive 46:NON-DELIVERY-REASON:
nonDeli
veryRea
son
nonRece Primitive 49:NON-RECEIPT-INFO:
iptInfo
43:NOTIFICATION-TYPE:
PAGE36 Fascicle VII.5 - Rec.T.330
obsolet Primitive 74:OBSOLETED-DISCARD:
edDisca
rd
obsolet Constructo 29:OBSOLETED:
edIPMs r
otherRe Constructo 41:OTHER-RECIPIENTS:
cipient r
s
outputM - 3.10:OUTPUT-MESSAGE:
essage
outputR - 3.9:OUTPUT-REQUEST:
equest
perMess Constructo 19:FLAGS:
ageIndi r
cators
preferr Primitive 70:PREFERRED-RECIPIENT:
edRecip
ient
priorit Primitive 13:PRIORITY:
y
probe
Fascicle VII.5 - Rec.T.330 PAGE57
- 3.2:PROBE:
probeAc - 3.15:PROBE-ACK:
k
probeId Primitive 66:PROBE-ID:
quantit Primitive 62:QUANTITY-OF-DOCS:
yOfDocs
recipie Constructe 15:RECIPIENTS:
nts ur
receipt - 3.5:RECEIPT-STATUS-NOTICE:
StatusN
otice
redirec Constructe 54:REDIRECTED-FROM:
tedFrom ur
registe - 3.11:REGISTER:
r
registe -
rAck
PAGE36 Fascicle VII.5 - Rec.T.330
3.17:REGISTER-ACK:
Fascicle VII.5 - Rec.T.330 PAGE57
TABLE 4/T.330 (end)
TAPDUId Type T.61 Character coding format Remarks
and
Element
Id name
related Constructo 28:RELATED-IPMS:
IPMs r
replied Primitive 30:REPLIED-TO-IPM:
ToIPM
reply Constructo 25:REPLY:
r
reporte Primitive 75:REPORTED-MESSAGE-ID:
dMessag
eId
reporte Primitive 3:REPORTED-RECIPIENT:
dRecipi
ent
retriev Primitive 38:RETRIEVAL-ID:
alId
returnA Primitive 36:RETURN-ADDRESS:
ddress
PAGE36 Fascicle VII.5 - Rec.T.330
send - 3.1:SEND:
sendAck - 3.14:SEND-ACK:
statusQ - 3.19:STATUS-QUERY:
uery
statusR - 3.20:STATUS-REPORT:
eport
subject Primitive 26:SUBJECT:
subject Primitive 71:SUBJECT-IPM:
IPM
submiss Primitive 65:SUBMISSION-ID:
ionId
submiss Primitive 33:SUBMISSION-TIME:
ionTime
Fascicle VII.5 - Rec.T.330 PAGE57
supplIn Primitive 68:SUPPLEMENTARY-INFORMATION:
fo
supplRe Primitive 68:SUPPLEMENTARY-INFORMATION:
ceiptIn
fo
thisIPM Primitive 27:THIS-IPM:
thisRec Primitive 39:THIS-RECIPIENT:
ipient
timeOfD Primitive 4:TIME-OF-DELIVERY:
elivery
timeOfR Primitive 47:TIME-OF-RECEIPT:
eceipt
timeOfR Primitive 84:TIME-OF-REPORT:
eport
tLMAUOp Constructo 59:TLMAU-OPERATION:
eration r
to
PAGE36 Fascicle VII.5 - Rec.T.330
Constructo 22:TO:
r
typeOfR Primitive 48:TYPE-OF-RECEIPT:
eceipt
typeOfU Primitive 45:TYPE-OF-UA:
A
Conventions:
1) Primitive: element contains only one element value field.
2) Constructor: element may contain more than one element value field.
3) abcde: underlined characters, i.e. "abc" are mandatory in case of
international access (see S 11.2).
4) : space character.
Fascicle VII.5 - Rec.T.330 PAGE57
TABLE 5/T.330
Format encoding of elements values
Type of
Element element Type of T.61 character coding format Remarks
value value value
name field
alternate Primitive Predefine Allowed
-recipien d
t-allowed
authorizi Construct - 21:AUTHORIZING:
ng or
authorizi Construct General R Descriptor
ng-user or
auto-ackn Primitive Predefine Auto-Receipt, Manual-Receipt
owledgmen d (défaut)
t
auto-forw Primitive Predefine Auto-forwarded,
arded d
Not-Auto-
forwarded
(default)
PAGE36 Fascicle VII.5 - Rec.T.330
auto-fwd- Primitive General any Text
Comment
auto-fwd- Primitive Predefine Auto-forwarded,
ipms d
Not-Auto-
forwarded
(default)
auto-fwd- Construct General OR Name
recipient or
-name
blind-cop Construct General OR Descriptor
y-recipie or
nt
body-part Primitive Predefine IA5Text, TLX, Voice, G3Fax,
d G4Fax-Class1, TTX, Videotex,
Message, Mixed-Mode,
Encrypted
Fascicle VII.5 - Rec.T.330 PAGE57
call-id Primitive General Call Identification
comments Primitive General Comments
content-r Primitive Predefine Content-Return-Request
eturn-req d
uest
conversio NO, Yes;
n-info WLOSS
copy-reci Construct General OR Descriptor
pient or
deferred- Primitive General Date and Time
delivery-
time
delete-af Primitive Predefine
ter-outpu
t
PAGE36 Fascicle VII.5 - Rec.T.330
d Keep, Delete
delivery- Primitive General Message Identifier
msg-id
Primitive General Date and Time
Unrecognized-OR-Name,
Ambiguous-OR-Name,
MTS-Congestion,
Loop-Detected,
Recipient-Unavailable,
diagnosti Primitive Predefine Maximum-Time-Expired,
c-code a) d Content-Too-Long,
Conversion-Impractical,
Encoded-Information-Type-Uns
upported,
Conversion-Prohibited,
Invalid-Arguments,
Implicit-Conversion-Not-Subs
cribed,
Content-Syntax-Error,
Pragmatic-Constraint-Violati
on, Protocol-Violation,
Content-Not-Supported,
Too-Many-Recipient,
No-Bilateral-Agreement
Fascicle VII.5 - Rec.T.330 PAGE57
TABLE 5/T.330 (cont.)
Type of
Element element Type of T.61 character coding format Remarks
value value value
name field
discard-i Primitive Predefine Discard (default),
pm d Not-Discard
discard-r Primitive Predefine IPM-Expired, IPM-Obsoleted,
eason d User-Subscription-Terminated
disclose- Primitive Predefine No-Disclosure
recipient d
s
dsMode Primitive - 58:DS-MODE:
ds-mode Primitive Predefine Auto-Output, Retrieval
d
eIT
PAGE36 Fascicle VII.5 - Rec.T.330
Primitive Predefine IA5Text, TLX, Voice, G3Fax,
d G4Fax-Class1, TTX, Videotex,
Undefined, Mixed-Mode
IPMS-Element-of-Service-Not-
Subscribed,*
MTS-Element-of-Service-Not-S
ubscribed,* Name-Malformed,*
IPM-Not-Submitted, *
IPM-Transferred, optionally
IPM-Delivered, followed by
error-cau Primitive Predefine Element-of-Service-Not-Subsc the name,
se d ribed,* Message-Delivered, service,
Message-Transferred, parameter,
Originator-Invalid,* etc.
Query-Identifier-Invalid,* concerned
Recipient-Improperly-Specifi in
ed,* ½ . . . ╗
Submission-Identifier-Invali
d,* No-Message-in-DS,
DS-Not-Supported,
DS-Not-Subscribed,
Retrieval-Identifier-Invalid
,* Parameter-Invalid,*
Not-Changed
error-rec Primitive Predefine Recovery-1, Recovery-2,
overy-mod d Recovery-3
e
expiry-ti Primitive General Date and Time
me
explicit- Primitive Predefine TLX, IA5, G3, G4, VTX, TTX
conversio d
n
forwarded Primitive General Date and Time
-time
frequency Primitive General Frequency
Fascicle VII.5 - Rec.T.330 PAGE57
importanc Primitive Predefine Low, Normal (default), High
e d
intended- Construct General OR Name
recipient or
-name
ipn-origi Construct General OR Descriptor
nating-us or
er
language- Primitive Predefine ffs
ind d
latest-de Primitive General Date and Time
livery-ti
me
message-d Primitive Predefine Auto-Delete (default),
elete-mod d Manual-Delete
e
message-l Primitive
ength
PAGE36 Fascicle VII.5 - Rec.T.330
General Message Length
messageTy Primitive - 52:MESSAGE-TYPE:
pe
non-recei Primitive Predefine IPM-DISCARD,
pt-reason d IPM-Auto-forwarded
nrn-reque Primitive Predefine NRN-Request
st d
number-of Primitive General Number Of Associated
-docs Documents
Fascicle VII.5 - Rec.T.330 PAGE57
TABLE 5/T.330 (cont.)
Type of
Element element Type of T.61 character coding format Remarks
value value value
name field
obsoleted Construct General IPM Identifier
-ipm-id or
originati Construct General OR Descriptor
ng-user or
originato Construct General OR Name
r-name or
originato Construct General OR Name
r-request or
ed-
alternate
-recipien
t
other-rec Construct General OR Name
ipient-na or
me
output-ti
PAGE36 Fascicle VII.5 - Rec.T.330
me Primitive General Date and Time
Physical- Primitive Predefine "PDM="OM (defaut), EMS,
delivery- d SPEC, COL, TLXA, TTXA, PHA,
mode BFAX
Physical- Primitive Predefine "REP="UND (defaut), PDS,
delivery- d MHS, PDMHS
report-
request
Physical- Primitive Predefine PFAR
forwardin d
g-
address-r
equest
Physical- Primitive Predefine PFP
forwardin d
g-
prohibite
d
postal-ad Primitive General OR Name
dress
preferred Construct General
-recipien or
t
Fascicle VII.5 - Rec.T.330 PAGE57
OR Descriptor
primary-r Construct General OR Descriptor
ecipient or
priority- Primitive Predefine Urgent, Non-Urgent, Normal
ind d (défaut)
probe-msg Primitive General Message Identifier
-id
reason-co Primitive Predefine Transfer-Failure,
de d Unable-To-Transfer,
Conversion-Not-Performed
receipt-t Primitive General Date and Time
ime
recipient Construct General OR Name
-name or
recipient
PAGE36 Fascicle VII.5 - Rec.T.330
-number-f Primitive General CALL="Number
or-advice
recipient Primitive Predefine RRP
-reassign d
ment-
prohibite
d
redirecte Construct General OR Name
d-from or
registere Primitive Predefine NRM (defaut), RM, RMA
d-mail-ty d
pe
related-i Construct General IPM Identifier
pm-id or
replied-t Construct General IPM Identifier
o-ipm-id or
reply-rec Construct General
ipient or
Fascicle VII.5 - Rec.T.330 PAGE57
OR Descriptor
reply-req Primitive Predefine Reply, No-Reply (default)
uest d
reply-tim Primitive General Date and Time
e
reported- Primitive General Message Identifier
message-i
d
PAGE36 Fascicle VII.5 - Rec.T.330
TABLE 5/T.330 (end)
Type of
Element element Type of T.61 character coding format Remarks
value value value
name field
reported- Construct General OR Name
recipient or
-name
report-ti Primitive General Date and Time
me
report-ty Primitive Predefine Receipt, Non-Receipt,
pe d Delivery, Non-delivery
requested Primitive Predefine "RDL="ANY (défaut), MAS, PD,
-delivery d TLX, TTX, G3, G4, IA5, VTX
-method
retrieval Primitive General Retrieval Identifier
-id
return-re
Fascicle VII.5 - Rec.T.330 PAGE57
quest Primitive Predefine Return-Request
d
rn-reques Primitive Predefine RN-Request
t d
sensitivi Primitive Predefine Personal, Private,
ty d Company-Confidential
status Primitive Predefine In-Process, Delivered,
d Non-Delivered
subject-c Primitive General Subject
ontent
subject-i Primitive General Message Identifier
pm-id
submissio Primitive General
n-msg-id
PAGE36 Fascicle VII.5 - Rec.T.330
Message Identifier
submissio Primitive - 33:SUBMISSION-TIME:
nTime
suppl-inf Primitive General Supplementary Information
o
suppl-rec Primitive General Supplementary Information
eipt-info
terminal- Primitive Predefine "TTyp=" TLX, TTX, G3, G4,
type d IA5, vtx
this-reci Construct General OR Name
pient-nam or
e
this-ipm- Construct General IPM Identifier
id or
type-of-r
Fascicle VII.5 - Rec.T.330 PAGE57
eceipt Primitive Predefine Manual (défaut), Automatic
d
type-of-u Primitive Predefine Private, Public (défaut)
a d
user-repo Primitive Predefine No-Report,
rt-reques d Non-Delivery-Report, Report
t
a) More diagnostic-codes can be found in Recommendation X.411 and should b
translated into appropriate T.61 text.
Note - The character strings in italics in the fourth column are the entry name
of the General value list, Table 6/T.330.
Conventions:
1) Primitive: elementary or value contains only one component.
2) Constructor: element or value contains more than one component.
3) abcde: underlined characters, i.e. "abc" are mandatory.
PAGE36 Fascicle VII.5 - Rec.T.330
Fascicle VII.5 - Rec.T.330 PAGE57
PAGE36 Fascicle VII.5 - Rec.T.330
Fascicle VII.5 - Rec.T.330 PAGE57
PAGE36 Fascicle VII.5 - Rec.T.330
