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 name

Value name

Operation

originator-name

-

-

Authenticate User (remarque 1)

original-encoded-informati on-types

-

-

set by TLMAU to EITs of submitted IPM's body

content-type

-

-

set by TLMAU to "IPMS"

content-identifier

-

-

Local matter

content-correlator

-

-

Local matter

recipient-name

to, cc, bcc

primary-, copy-, blind-copy-recip

ient

constructed by TLMAU

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.

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

o

call-id

CallIdentification that identifies previous Send-TAPDU being reported on

submissionId

submission-msg

-id

MTS message-submission-identifier

submissionTime

submission-tim

e

MTS message-submission-time

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:

Source of ProbeAck-TAPDU components

ProbeAck-TAPDU component

Element name

Value name

Source

correlationInf

o

call-id

CallIdentification that identifies previous Probe-TAPDU being reported on

probeId

probe-msg-id

MTS probe-submission-identifier

submissionTime

submission-tim

e

MTS probe-submission-time

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

MessageSubmiss

ion argument

Corresponding

ExplicitRN-TAPDU component

Operation

Element name

Value name

originator-nam

e

-

-

authenticate user

original-encod

ed-information

-types

-

-

set by TLMAU to "unspecified"

content-type

-

-

set by TLMAU to "IPMS"

content-identi

fier

-

-

Local matter

priority

priority

priority-in

d

per-message-in

dicators

disclose-recip

ients

conversion-pro

hibited

alternate-reci

pient-allowed

content-return

-request

-

-

-

-

-

-

-

-

set to "disclosure-of-recipient-prohibi

ted"

set to "conversion-prohibited"

set to "alternate-recipient-prohibited"

set to "content-return-not-requested"

recipient-name

recipients

recipient-n

ame

originator-rep

ort-request

-

-

set by TLMAU to "no report"

content

-

-

identified as IPN

Note 1 - The IPN submitted as the content is constructed by the TLMAU. 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

o

call-id

CallIdentification that identifies previous ExplicitRN-TAPDU being reported on

submissionId

submission-msg

-id

MTS message-submission-identifier

submissionTime

submission-tim

e

MTS message-submission-time

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

livery argument

Element name

Value name

Operation

message-submissi

on-identifier

submissionId

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:

Source of Deliver-TAPDU component

Deliver-TAPDU component

Corresponding MessageDelivery

argument

Operation

Element name

Value name

quantityO

fDocs

number-of-docs

-

when control Information

is conveyed by a normal document, set number of associated documents in Deliver-TAPDU

priority

priority-ind

priority

originato

r

originator-name

originator-name

thisRecip

ient

this-recipient-name

this-recipient-name

intendedR

ecipient

intended-recipient- name

originally-intended-recipient -name

otherReci

pients

other-recipient-nam e

other-recipient-names

submissio

nTime

submission-time

message-submission-time

timeOfDel

ivery

delivery-time

message-delivery-time

deliveryI

d

delivery-msg-id

message-delivery-identifier

conversio

nIndicati

on

eIT

original-encoded-information- types

conversio

nIndicati

on

conversion-prohibit ed

delivery-flags

converted

InfoTypes

eIT

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 component

Corresponding MessageDelivery and

Operation

Element name

Value name

receive RN/NRN argument

quantityO

fDocs

number-of-docs

-

when control Information is conveyed by a normal document, set number of associated documents in ReceiptStatusNo tice-TAPDU

priority

priority-ind

priority

deliveryI

d

delivery-id

message-delivery-identifi er

originato

r

originator-name

originator-identifier

if this element is omitted, this argument should be constructed from TID obtains from CSS

thisRecip

ient

this-recipient-nam e

this-recipient-identifier

submissio

nTime

submission-time

message-submission-time

timeOfDel

ivery

delivery-time

message-delivery-time

conversio

nIndicati

on

eIT

original-encoded-informat ion-types

conversio

nIndicati

on

conversion-prohibi ted

delivery-flags

converted

InfoTypes

eIT

converted-encoded-informa tion-types

notificat

ionType

report-type

choice

subjectIP

M

subject-ipm-id

subject-ipm

iPNOrigin

ator

ipn-originating-us er

ipn-originator

preferred

Recipient

preferred-recipien t

ipm-preferred-recipient

timeOfRec

eipt

receipt-time

receipt-time

typeOfRec

eipt

type-of-receipt

acknowledgment-mode

supplRece

iptInfo

suppl-receipt-info

suppl-receipt-info

nonReceip

tInfo

non-receipt-reason

non-receipt-reason

nonReceip

tInfo

discard-reason

discard-reason

comment

comments

auto-forward-comment

messageRe

turnedInd

-

returned-ipm

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.

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 component

Corresponding ReportDelivery

argument

Operation

Element name

Value name

quantityO

fDocs

number-of-docs

-

when control Information is conveyed by a normal document, set number of associated documents in DeliveryStatusNo tice-TAPDU

correlati

onInfo

call-id

-

CallIdentificati on that identifies previous Send-TAPDU being reported on

priority

priority-ind

priority

submissio

nId

submission-id

subject-identifier

probeId

submission-id

subject-identifier

reportedR

ecipient

reported-recipient- name

actual-recipient-identifier

notificat

ionType

report-type

report

intendedR

ecipient

intended-recipient- name

originally-intended-recipien t

converted

InfoTypes

eIT

converted-encoded-informatio n-types

timeOfDel

ivery

delivery-time

message-delivery-time

typeOfUA

type-of-ua

type-of-MTS-user

nonDelive

ryReason

reason-code

non-delivery-reason-code

nonDelive

ryReason

diagnostic-code

non-delivery-diagnostic-code

contentRe

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 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 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.

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 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.

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.

TABLE 4/T.330

Format encoding of TAPDU and ElementId

TAPDUId and ElementId name

Type

T.61 Character coding format

Remarks

authori

zing

Constructo r

21:	AUTHORIZING:

autoFWD

Comment

Primitive

79:	AUTO-FWD-COMMENT:

autoFWD

Heading

78:	AUTO-FWD-HEADING:

for further study

autoFWD

IPMs

Primitive

76:	AUTO-FWD-IPMS:

autoFWD

Recipie

nts

Constructo r

77:	AUTO-FWD-RECIPIENTS:

autoOut

put

Constructo r

60:	AUTO-OUTPUT:

bcc

Constructo r

24:	BCC:

bodyTyp

e

Constructo r

31:	BODY-TYPE:

cancel

-

3.13:	CANCEL:

cc

Constructo r

23:	CC:

comment

Primitive

50:	COMMENT:

content

Indicat

or

Constructo r

18:	CONTENT-INDICATOR:

content

Info

Primitive

17:	CONTENT-INFO:

content

Returne

d

-

72:	CONTENT-RETURNED-INDICATION:

convers

ion

Primitive

16:	CONVERSION:

convers

ionIndi

cation

Constructo r

42:	CONVERSION-INDICATION:

convert

edInfoT

ypes

Primitive

44:	CONVERTED-INFORMATION-TYPES:

correla

tionInf

o

Primitive

1:	CORRELATION-INFORMATION:

deleteA

fterOut

put

Primitive

80:	DELETE-AFTER-OUTPUT:

deliver

-

3.3:	DELIVER:

deliver

yId

Primitive

35:	DELIVERY-ID:

deliver

yStatus

Notice

-

3.4:	DELIVERY-STATUS-NOTICE:

dsMode

Primitive

58:	DS-MODE:

dsQuery

-

3.7:	DS-QUERY:

dsRepor

t

-

3.8:	DS-REPORT:

errors

Primitive

9:	ERRORS:

excepti

on

-

3.12:	EXCEPTION:

expired

Discard

Primitive

73:	EXPIRED-DISCARD:

explici

tRN

-

3.6:	EXPLICIT-RN:

explici

tRNAck

-

3.16:	EXPLICIT-RN-ACK:

forward

edInfo

Constructo r

32:	FORWARDED-INFO:

from

Primitive

20:	FROM:

TABLE 4/T.330 (cont.)

TAPDUId and ElementId name

Type

T.61 Character coding format

Remarks

orgInte

ndedRec

ipient

Primitive

40:	INTENDED-RECIPIENT:

iPNOrig

inator

Primitive

69:	IPN-ORIGINATOR:

languag

e

Primitive

53:	LANGUAGE:

latestD

elivery

Primitive

34:	LATEST-DELIVERY:

message

Delete

-

3.18:	MESSAGE-DELETE:

message

DeleteM

ode

Primitive

81:	MESSAGE-DELETE-MODE:

message

Length

Primitive

37:	MESSAGE-LENGTH:

message

Returne

dInd

-

51:	MESSAGE-RETURNED-INDICATION:

message

Selecto

r

Primitive

82:	MESSAGE-SELECTOR:

message

Status

Primitive

83:	MESSAGE-STATUS:

message

Type

Primitive

52:	MESSAGE-TYPE:

msgInco

mplete

-

67:	MSG-INCOMPLETE:

This element has not value

nonDeli

veryRea

son

Primitive

46:	NON-DELIVERY-REASON:

nonRece

iptInfo

Primitive

49:	NON-RECEIPT-INFO:

43:	NOTIFICATION-TYPE:

obsolet

edDisca

rd

Primitive

74:	OBSOLETED-DISCARD:

obsolet

edIPMs

Constructo r

29:	OBSOLETED:

otherRe

cipient

s

Constructo r

41:	OTHER-RECIPIENTS:

outputM

essage

-

3.10:	OUTPUT-MESSAGE:

outputR

equest

-

3.9:	OUTPUT-REQUEST:

perMess

ageIndi

cators

Constructo r

19:	FLAGS:

preferr

edRecip

ient

Primitive

70:	PREFERRED-RECIPIENT:

priorit

y

Primitive

13:	PRIORITY:

probe

-

3.2:	PROBE:

probeAc

k

-

3.15:	PROBE-ACK:

probeId

Primitive

66:	PROBE-ID:

quantit

yOfDocs

Primitive

62:	QUANTITY-OF-DOCS:

recipie

nts

Constructe ur

15:	RECIPIENTS:

receipt

StatusN

otice

-

3.5:	RECEIPT-STATUS-NOTICE:

redirec

tedFrom

Constructe ur

54:	REDIRECTED-FROM:

registe

r

-

3.11:	REGISTER:

registe

rAck

-

3.17:	REGISTER-ACK:

TABLE 4/T.330 (end)

TAPDUId and ElementId name

Type

T.61 Character coding format

Remarks

related

IPMs

Constructo r

28:	RELATED-IPMS:

replied

ToIPM

Primitive

30:	REPLIED-TO-IPM:

reply

Constructo r

25:	REPLY:

reporte

dMessag

eId

Primitive

75:	REPORTED-MESSAGE-ID:

reporte

dRecipi

ent

Primitive

3:	REPORTED-RECIPIENT:

retriev

alId

Primitive

38:	RETRIEVAL-ID:

returnA

ddress

Primitive

36:	RETURN-ADDRESS:

send

-

3.1:	SEND:

sendAck

-

3.14:	SEND-ACK:

statusQ

uery

-

3.19:	STATUS-QUERY:

statusR

eport

-

3.20:	STATUS-REPORT:

subject

Primitive

26:	SUBJECT:

subject

IPM

Primitive

71:	SUBJECT-IPM:

submiss

ionId

Primitive

65:	SUBMISSION-ID:

submiss

ionTime

Primitive

33:	SUBMISSION-TIME:

supplIn

fo

Primitive

68:	SUPPLEMENTARY-INFORMATION:

supplRe

ceiptIn

fo

Primitive

68:	SUPPLEMENTARY-INFORMATION:

thisIPM

Primitive

27:	THIS-IPM:

thisRec

ipient

Primitive

39:	THIS-RECIPIENT:

timeOfD

elivery

Primitive

4:	TIME-OF-DELIVERY:

timeOfR

eceipt

Primitive

47:	TIME-OF-RECEIPT:

timeOfR

eport

Primitive

84:	TIME-OF-REPORT:

tLMAUOp

eration

Constructo r

59:	TLMAU-OPERATION:

to

Constructo r

22:	TO:

typeOfR

eceipt

Primitive

48:	TYPE-OF-RECEIPT:

typeOfU

A

Primitive

45:	TYPE-OF-UA:

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.

TABLE 5/T.330

Format encoding of elements values

Element value name

Type of element value field

Type of value

T.61 character coding format

Remarks

alternate

-recipien

t-allowed

Primitive

Predefine

d

Allowed

authorizi

ng

Construct

or

-

21:	AUTHORIZING:

authorizi

ng-user

Construct

or

General

R Descriptor

auto-ackn

owledgmen

t

Primitive

Predefine

d

Auto-Receipt, Manual-Receipt (défaut)

auto-forw

arded

Primitive

Predefine

d

Auto-forwarded,

Not-Auto-

forwarded (default)

auto-fwd-

Comment

Primitive

General

any Text

auto-fwd-

ipms

Primitive

Predefine

d

Auto-forwarded,

Not-Auto-

forwarded (default)

auto-fwd-

recipient

-name

Construct

or

General

OR Name

blind-cop

y-recipie

nt

Construct

or

General

OR Descriptor

body-part

Primitive

Predefine

d

IA5Text, TLX, Voice, G3Fax, G4Fax-Class1, TTX, Videotex, Message, Mixed-Mode, Encrypted

call-id

Primitive

General

Call Identification

comments

Primitive

General

Comments

content-r

eturn-req

uest

Primitive

Predefine

d

Content-Return-Request

conversio

n-info

NO, Yes; WLOSS

copy-reci

pient

Construct

or

General

OR Descriptor

deferred-

delivery-

time

Primitive

General

Date and Time

delete-af

ter-outpu

t

Primitive

Predefine

d

Keep, Delete

delivery-

msg-id

Primitive

General

Message Identifier

Primitive

General

Date and Time

diagnosti

c-code a)

Primitive

Predefine

d

Unrecognized-OR-Name, Ambiguous-OR-Name, MTS-Congestion, Loop-Detected, Recipient-Unavailable, Maximum-Time-Expired, 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

TABLE 5/T.330 (cont.)

Element value name

Type of element value field

Type of value

T.61 character coding format

Remarks

discard-i

pm

Primitive

Predefine

d

Discard (default), Not-Discard

discard-r

eason

Primitive

Predefine

d

IPM-Expired, IPM-Obsoleted, User-Subscription-Te rminated

disclose-

recipient

s

Primitive

Predefine

d

No-Disclosure

dsMode

Primitive

-

58:DS-MODE:

ds-mode

Primitive

Predefine

d

Auto-Output, Retrieval

eIT

Primitive

Predefine

d

IA5Text, TLX, Voice, G3Fax, G4Fax-Class1, TTX, Videotex, Undefined, Mixed-Mode

error-cau

se

Primitive

Predefine

d

IPMS-Element-of-Service-Not- Subscribed,* MTS-Element-of-Service-Not-

Subscribed,* Name-Malformed,* IPM-Not-Submitted, IPM-Transferred, IPM-Delivered, Element-of-Service-Not-Subsc

ribed,* Message-Delivered, Message-Transferred, Originator-Invalid,* Query-Identifier-Invalid,* Recipient-Improperly-Spe cifi

ed,* Submission-Identifier-Invali

d,* No-Message-in-DS, DS-Not-Supported, DS-Not-Subscribed, Retrieval-Identifier-I nvalid

,* Parameter-Invalid,* Not-Changed

*	optionally followed by the name, service, parameter, etc. concerned in

½ . . .

error-rec

overy-mod

e

Primitive

Predefine

d

Recovery-1, Recovery-2, Recovery-3

expiry-ti

me

Primitive

General

Date and Time

explicit-

conversio

n

Primitive

Predefine

d

TLX, IA5, G3, G4, VTX, TTX

forwarded

-time

Primitive

General

Date and Time

frequency

Primitive

General

Frequency

importanc

e

Primitive

Predefine

d

Low, Normal (default), High

intended-

recipient

-name

Construct

or

General

OR Name

ipn-origi

nating-us

er

Construct

or

General

OR Descriptor

language-

ind

Primitive

Predefine

d

ffs

latest-de

livery-ti

me

Primitive

General

Date and Time

message-d

elete-mod

e

Primitive

Predefine

d

Auto-Delete (default), Manual-Delete

message-l

ength

Primitive

General

Message Length

messageTy

pe

Primitive

-

52:MESSAGE-TYPE:

non-recei

pt-reason

Primitive

Predefine

d

IPM-DISCARD, IPM-Auto-forwar ded

nrn-reque

st

Primitive

Predefine

d

NRN-Request

number-of

-docs

Primitive

General

Number Of Associated Documents

TABLE 5/T.330 (cont.)

Element value name

Type of element value field

Type of value

T.61 character coding format

Remarks

obsoleted

-ipm-id

Construct

or

General

IPM Identifier

originati

ng-user

Construct

or

General

OR Descriptor

originato

r-name

Construct

or

General

OR Name

originato

r-request

ed- alternate

-recipien

t

Construct

or

General

OR Name

other-rec

ipient-na

me

Construct

or

General

OR Name

output-ti

me

Primitive

General

Date and Time

Physical-

delivery-

mode

Primitive

Predefine

d

"PDM="OM (defaut), EMS, SPEC, COL, TLXA, TTXA, PHA, BFAX

Physical-

delivery-

report- request

Primitive

Predefine

d

"REP="UND (defaut), PDS, MHS, PDMHS

Physical-

forwardin

g- address-r

equest

Primitive

Predefine

d

PFAR

Physical-

forwardin

g- prohibite

d

Primitive

Predefine

d

PFP

postal-ad

dress

Primitive

General

OR Name

preferred

-recipien

t

Construct

or

General

OR Descriptor

primary-r

ecipient

Construct

or

General

OR Descriptor

priority-

ind

Primitive

Predefine

d

Urgent, Non-Urgent, Normal (défaut)

probe-msg

-id

Primitive

General

Message Identifier

reason-co

de

Primitive

Predefine

d

Transfer-Failure, Unable-To-Transfer, Conversion-Not-Perfor med

receipt-t

ime

Primitive

General

Date and Time

recipient

-name

Construct

or

General

OR Name

recipient

-number-f

or-advice

Primitive

General

CALL="Number

recipient

-reassign

ment- prohibite

d

Primitive

Predefine

d

RRP

redirecte

d-from

Construct

or

General

OR Name

registere

d-mail-ty

pe

Primitive

Predefine

d

NRM (defaut), RM, RMA

related-i

pm-id

Construct

or

General

IPM Identifier

replied-t

o-ipm-id

Construct

or

General

IPM Identifier

reply-rec

ipient

Construct

or

General

OR Descriptor

reply-req

uest

Primitive

Predefine

d

Reply, No-Reply (default)

reply-tim

e

Primitive

General

Date and Time

reported-

message-i

d

Primitive

General

Message Identifier

TABLE 5/T.330 (end)

Element value name

Type of element value field

Type of value

T.61 character coding format

Remarks

reported-

recipient

-name

Construct

or

General

OR Name

report-ti

me

Primitive

General

Date and Time

report-ty

pe

Primitive

Predefine

d

Receipt, Non-Receipt, Delivery, Non-delivery

requested

-delivery

-method

Primitive

Predefine

d

"RDL="ANY (défaut), MAS, PD, TLX, TTX, G3, G4, IA5, VTX

retrieval

-id

Primitive

General

Retrieval Identifier

return-re

quest

Primitive

Predefine

d

Return-Request

rn-reques

t

Primitive

Predefine

d

RN-Request

sensitivi

ty

Primitive

Predefine

d

Personal, Private, Company-Confidential

status

Primitive

Predefine

d

In-Process, Delivered, Non-Delivered

subject-c

ontent

Primitive

General

Subject

subject-i

pm-id

Primitive

General

Message Identifier

submissio

n-msg-id

Primitive

General

Message Identifier

submissio

nTime

Primitive

-

33:SUBMISSION-TIME:

suppl-inf

o

Primitive

General

Supplementary Information

suppl-rec

eipt-info

Primitive

General

Supplementary Information

terminal-

type

Primitive

Predefine

d

"TTyp=" TLX, TTX, G3, G4, IA5, vtx

this-reci

pient-nam

e

Construct

or

General

OR Name

this-ipm-

id

Construct

or

General

IPM Identifier

type-of-r

eceipt

Primitive

Predefine

d

Manual (défaut), Automatic

type-of-u

a

Primitive

Predefine

d

Private, Public (défaut)

user-repo

rt-reques

t

Primitive

Predefine

d

No-Report, Non-Delivery-

Report, Report

a)	More diagnostic-codes can be found in Recommendation X.411 and should be 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.