home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Standards
/
CD2.mdf
/
ccitt
/
1992
/
t
/
t330_5.asc
< prev
next >
Wrap
Text File
|
1993-08-16
|
32KB
|
2,346 lines
C:\WINWORD\CCITTREC.DOT_______________
The drawings contained in this Recommendation have been done in
Autocad.
12 Error recovery
This section specifies the error recovery mechanisms for errors which
may occur during the communication between a TLM terminal and a
TLMAU. The type of recovery will depend upon whether the error occurred
during the transmission of control information or a normal document. The
recovery mechanism of Recommendation T.62 shall apply. In addition, the
qualifications given in the following paragraphs shall apply.
For both directions of transfer, if an error is detected during the trans-
mission of a document containing control information, the transmitted part
shall be discarded and the complete TAPDU retransmitted.
If an error is detected during the transmission of a document contain-
ing message body, the recovery mechanism depends upon the direction of
transfer. In the TLMAUùtoùTLM terminal direction, two possibilities for
recovery are available, the first one is to apply the rules of Recommendation
T.62 using CDC, the second one is the complete retransmission of the
TAPDU. In the TLM terminalùtoùTLMAU direction, three possible
recovery mechanisms are identified, the choice of which is a national mat-
ter:
1) No recovery is provided. The complete TAPDU (control informa-
tion and message body) must be retransmitted.
2) The TLMAU shall retain the received part up to the last acknowl-
edged checkpoint. The originating TLM terminal is required to
resume the sending of the remainder of the TAPDU by using CDC
protocol element as described in Recommendation T.62. The
TLMAU shall automatically link the retained part with the
resumed part prior to sending to the MTS. If the originating TLM
terminal does not resume the sending within a predetermined time
or if the TLMAU receives new TAPDU within that time, the
TLMAU shall discard the received part of the TAPDU.
3) The last acknowledged normal document is considered the end of
the TAPDU. The TLMAU will send this part to the MTS as a com-
plete message. If the TLM terminal wishes to resume transmission
of the interrupted TAPDU, it must first resend the control informa-
tion. There is no correlation between the original message and the
continued message at a receipient TLMAU or IPMùUA.
Note 1 ù For failures occurring between document boundaries, the last
acknowledged document shall be regarded as the end of the current
TAPDU.
Note 2 ù A TAPDU, which may be composed of more than one document,
cannot be considered complete before at least two documents were received.
Note 3 ù If there is a relationship between the sequence of normal docu-
ments (for example a multiùpart body message) being transferred, the
recovery mechanism 2 should not be used.
13 Control procedures
13.1 Session control procedure
The session control procedures shall be in accordance with Recom-
mendation T.62. However, the qualifications listed in the following subsec-
tions shall also apply.
13.1.1 Session element of procedure
The values of mandatory parameters used during session establish-
ment shall be as given in Table 7/T.330. The format of the TLMAU terminal
identifier shall be that specified in Recommendation F.200.
13.1.2 Session rules
Change control (CSCC/RSCCP exchange) may occur inside TAPDU
boundaries but should occur outside document boundaries.
13.2 Document control procedures
The document control procedures shall be in accordance with Recom-
mendation T.62.
Control information is conveyed in either a control document or a
normal document. Where encoded information types of the control informa-
tion is Teletex, the body of the IPùmessage is conveyed in a sequence (at
least one) of normal documents.
Note ù The use of the normal document for conveying control infor-
mation should be restricted to Teletex access to IPMS.
TABLE 7/T.330
Mandatory parameter values during session establishment
Call Originator
T.62 parameters
TLM terminal
TLMAU
Terminal identifier of
calling terminal (in
CSS)
TLM TID
TLMAU's TID
Terminal identifier of
called terminal (in
RSSP)
TLMAU TID
TLM TID
Date and time
Date and time the TLM
terminal originated call
Date and time the
TLMAU terminal orig-
inated call
Service identifier
Telematic
Telematic
Window size
Note 1
Note 1
Session user data
Basic terminal capabil-
ities and interchange
format(s) which are
available as receiving
capabilities of the TLM
terminal (Note 1)
Basic terminal capabil-
ities and interchange
format(s) which are
available as receiving
capabilities of the
TLMAU (Note 1)
Note 1 ù This parameter is mandatory for the Group 4 facsimile service.
Note 2 ù TID means terminal identification.
Note 3 ù Negotiation of the capabilities of handling control documents
encoded in T.61 characters is not needed.
In a multipleùTAPDU session, the TAPDUs are delimited by at least one of
the following methods:
1) implicity, that is, by the first document of the TAPDU being a con-
trol document;
2) explicitly, that is, by the first document of the TAPDU containing a
parameter indicating the number of subsequence documents in the
TAPDU.
Note ù The second method is mandatory for multipleùactionùunit ses-
sion, where the first document of the TAPDU is a normal document.
When a single TAPDU is sent on a session connection, the TAPDU is delim-
ited only by the end of the session.
13.3 Logùon procedure
It is conceivable that many subscribers will commonly use a single
TLM terminal, some mechanism is required to identify a specific user by
intermediate system, i.e. logùon procedure using user name and password.
Detailed procedure requires further study.
ANNEX A
(to Recommendation T.330)
Formal definition of TLMA abstract service
This Annex is an integral part of this Recommendation.
This Annex, a supplement to º 7, formally defines for reference pur-
poses the abstract service TLMA (telematic agent). It uses the PORT
and ABSTRACTùBIND, ùUNBIND, ùOPERATION, and ù
ERROR macro of Recommendation X.407.
TLMAAbsService { ccittùt330 }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
ùù Prologue
EXPORTS
ùù Primary port types
miscellanea
IMPORTS
ùù Abstract service
origination, reception, management
FROM IPMSAbstractService { jointùisoùccitt
mhs(6) ipms(1) modules(0) abstractùservice(3) }
import, export
FROM MTSAbstractService { jointùisoùccitt
mhs(6) mts(3) modules(0) mTSùabstractùser-
vice(3) }
ùù Information objects and their aspects
IPM, RN, NRN
FROM IPMSInformationObjects { jointùisoùccitt
mhs(6) ipms(1) modules(0) informationù
objects(2) }
ùù Functional objects
tlma
FROM IPMSFunctionalObjects { jointùisoùccitt
mhs(6) ipms(1) modules(0) functionalù
objects(1) }
ùù MTAS aspects
MessageDeliveryEnvelope, ORName, MessageIdentifier, Prior-
ity, Time, ReportDeliveryEnvelope,
PerRecipientReportDeliveryFields
FROM MTSAbstractService { jointùisoùccitt
mhs(6) mts(3) modules(0) mTSùabstractùser-
vice(3) }
ùù Abstract services macros
OBJECT, PORT, ABSTRACTùBIND, ABSTRACTù
ERROR, ABSTRACTùOPERATION
FROM AbstractServiceNotation { jointùisoùccitt
mhs(6) adsdc(2) modules(0) notation(1) }
DateandTime ::= Time
ùù Object
tlma OBJECT
PORTS {
origination [S],
reception [S],
management [S],
miscellanea [S],
import [C],
export [C] }
::= idùotùtlma
ùù Ports
miscellanea PORT
SUPPLIER PERFORMS {
ChangeSubscriptionProfile,
DSList,
DSDelete,
DSFetch,
MessageStatus }
::= idùptùmiscellanea
TLMAAbsService (continuation)
ùù Miscellanea port specific abstract error problems
SubscriptionProfileProblem ::= ENUMERATED {
notùchanged(0) }
DSProblem ::= ENUMERATED {
noùmessageùinùds(0),
dsùnotùsupported(1),
dsùnotùsubscribed(2),
retrievalùidentifierùinvalid(3),
parameterùinvalid(4) }
MessageStatusProblem ::= ENUMERATED {
queryùidentifierùinvalid(0) }
ùù RetrievalIdentifier
RetrievalIdentifier ::= PrintableString
ùù CallIdentification
CallIdentification ::= SEQUENCE {
TLMAU TID [0] TerminalIdentifier,
TLM TID [1] TerminalIdentifier,
dateùandùtime [2] DateAndTime,
documentùrefùnum [3] DocumentReferenceNumber,
additionalùsessionùrefùnum [4] AdditionalSessionReferenceNumber
OPTIONAL }
TerminalIdentifier ::= PrintableString ùù defined in Recommendation
F.200 ùù
DocumentReferenceNumber ::= NumericString
AdditionalSessionReferenceNumber ::= NumericString
ùù Change subscription profile abstract operation component types
DSMode ::= SET {
[0] Mode,
frequency [1] Frequency OPTIONAL,
time [2] DateandTime OPTIONAL }
Mode ::= CHOICE {
[0] autoùoutput,
[1] retrieval }
Frequency ::= NumericString ùù in minutes ùù
ErrorRecoveryMode ::= CHOICE { ùù see º 12 in this Recommendation
ùù
[0] recoveryù1, ùù noùrecovery ùù
[1] recoveryù2, ùù fullùsupportùofùT.62ùrecoveryùprocedures ù
ù
[2] recoveryù3 ùù recoveryùofùdocumentùbasis ùù }
MessageDeleteMode ::= CHOICE {
[0] autoùdelete,
[1] manualùdelete }
ùù DS List abstract operation component types
ListReport ::= SET {
retrievalùid [0] RetrievalIdentifier,
messageùtype [1] MessageType,
priority [2] Priority OPTIONAL,
messageùlength [3] MessageLength OPTIONAL,
originatorùname [4] ORName OPTIONAL }
MessageType ::= CHOICE {
[0] ipm,
[1] receiptùnotice,
[2] nonùreceiptùnotice,
[3] report }
MessageLength ::= NumericString ùù in octet ùù
TLMAAbsService (continuation)
ùù DS Fetch abstract operation component types
DeleteAfterOutput ::= CHOICE {
[0] delete,
[1] keep }
MessageReport ::= CHOICE {
ipmùfetch [0] IPMFetch,
rnùfetch [1] RNFetch,
nrnùfetch [2] NRNFetch,
reportùfetch [3] ReportFetch }
IPMFetch ::= SEQUENCE {
envelope [0] MessageDeliveryEnvelope,
content [1] IPM }
RNFetch ::= SEQUENCE {
envelope [0] MessageDeliveryEnvelope,
ùù not used intendedùrecipientùname and other recipientùname
of deliverùenvelope in RNFetch ùù
content [1] RN } }
NRNFetch ::= SEQUENCE {
[0] numberùofùdocs [0] NumberOfAssociatedDocuments OPTIONAL,
[1] SET {
envelope [1] MessageDeliveryEnvelope,
ùù not used intendedùrecipientùname and other recipientùname
of deliverùenvelope in NRNFetch ùù
content [2] NRN } }
ReportFetch ::= SEQUENCE {
[0] SET {
numberùofùdocs [0] NumberOfAssociatedDocuments OPTIONAL,
callùid [1] CallIdentification },
[1] SET {
envelope [0] ReportDeliveryEnvelope,
returnedùcontent [1] IPM OPTIONAL } } }
NumberOfAssociatedDocuments ::= NumericString
ùù Message status abstract service
QueryIdentifier ::= CHOICE {
submissionùid [0] MessageIdentifier,
callùid [1] CallIdentification }
StatusInfo ::= SET {
[0] Status,
perùrecipientùinfo [1] PerRecipientReportDeliveryFields
OPTIONAL }
Status ::= CHOICE {
[0] inùprocess,
[1] delivered,
[2] nonùdelivered }
ùù Miscellanea abstractùoperations
ChangeSubscriptionProfile ::= ABSTRACTùOPERATION
ARGUMENT SET {
dsùmode [0] DSMode OPTIONAL,
errorùrecoveryùmode [1] ErrorRecovery-
Mode OPTIONAL,
messageùdeleteùmode [2] MessageDelete-
Mode OPTIONAL }
RESULT { }
ERRORS {
nameùerror,
dsùerror,
subscriptionùprofileùerror }
TLMAAbsService (continuation)
DSList ::= ABSTRACTùOPERATION
ARGUMENT { }
RESULT SET {
listùreports [0] SET OF ListReport OPTIONAL }
ERRORS {
subscriptionùerror,
nameùerror,
dsùerror }
DSDelete ::= ABSTRACTùOPERATION
ARGUMENT SET {
selector [0] SET OF RetrievalIdentifier }
RESULT
ERRORS {
subscriptionùerror,
nameùerror,
dsùerror }
DSFetch ::= ABSTRACTùOPERATION
ARGUMENT SET {
selector [0] SET OF RetrievalIdenti-
fier,
deleteùafterùoutput [1] DeleteAfterOutput
OPTIONAL }
RESULT SET {
retrievalùid [0] RetrievalIdentifier,
messageùreport [1] MessageReport }
ERRORS {
subscriptionùerror,
nameùerror,
dsùerror }
MessageStatus ::= ABSTRACTùOPERATION
ARGUMENT SET {
[0] QueryIdentifier }
RESULT SET {
reportùtime [0] DateandTime,
reportedùmessageùid [1] MessageIdentifier,
reportedùmessageùid [2] SET OF StatusInfo }
ERRORS {
subscriptionùerror,
nameùerror,
messageùstatusùerror }
ùù Miscellanea port specific abstract errors
subscriptionùprofileùerror ABSTRACTùERROR
PARAMETER SET {
problem [0] SubscriptionProfileProblem }
::= 0
dsùerror ABSTRACTùERROR
problem [0] DSProblem }
::= 1
messageùstatusùerror ABSTRACTùERROR
PARAMETER SET {
problem [0] MessageStatusProblem }
::= 2
END ùù of TLMAAbsService
ANNEX B
(to Recommendation T.330)
Format of TAPDU components
In this Annex the formats of the control information for different
examples TAPDUS are shown. The principles of encoding are given
in º 11. The formats of elements as defined in º 11 are illustrated by
the use of the following four different syntax elements:
1) The elements number field is represented by a sequence of numeric
graphic characters.
2) The element name field is represented by a text string giving the
CCITT language reference name of the field. The actual value
shall be a languageùdependent representation of that reference
name.
3) Separators are shown as they shall be represented in the actual con-
trol information.
4) Element value fields are shown in square brackets (ô[ö and ô]ö).
The actual parameter values are described in º 11.
Note ù The examples shown below are not exhaustive. Not all types (ele-
ment value of the TAPDU description in º 10 (ASN.1 description) are
included.
B.1 Conventions
Following symbols are used in this Annex:
1) NL new line function such as (CR LF or LF CR) or LF.
2) space character.
3) [ ] element value field. Actual values are defined in º 11 of this Rec-
ommendation.
4) [ ] iteration.
B.2 Example of TAPDU
B.2.1 SendùTAPDU
3.1: SEND:
62: QUANTITYùOFùDOCS:[numberùofùdocs]
13: PRIORITY:[priorityùind]
19: FLAGS:
[deferredùdeliveryùtime] `NL`
=[discloseùrecipients],[alternateùrecipientùallowed]
16: CONVERSION:[conversionùprohibited]
17: CONTENTùINFO:[contentùreturnùrequest]
27: THISùIPM:
[thisùipmùid]
20: FROM:
[originatingùuser]
21: AUTHORIZING:
[ [authorizingùuser] `NL` ]
22: TO:
[ [primaryùrecipient] `NL`
=[userùreportùrequest],[rnùrequest],[nrnùrequest],[re-
turnùrequest],[replyùrequest] `NL` ]
23: CC:
[ [copyùrecipient] `NL`
=[rnùrequest],[nrnùrequest],[returnùrequest],[replyù
request] `NL` ]
24: BCC:
[ [blindùcopyùrecipient] `NL` ]
30: REPLIEDùTOùIPM:
[repliedùtoùipmùid]
29: OBSOLETES:
[ [obsoletedùipmùid] `NL` ]
28: RELATEDùIPMS:
[ [relatedùipmùid] `NL` ]
26: SUBJECT:
[subjectùcontent]
18: CONTENTùINDICATOR:
[expiryùtime] `NL`
=[importance],[sensitivity]
25: REPLY:
[replyùtime] `NL`
[ [replyùrecipient] `NL` ]
31: BODYùTYPE: [ [bodyùpart], ]
B.2.2 SendAckùTAPDU
3.14: SENDùACK:
1: CORRELATIONùINFORMATION:
[callùid]
65: SUBMISSIONùID:
[submissionùmsgùid]
33: SUBMISSIONùTIME:
[submissionùtime]
B.2.3 ExceptionùTAPDU
3.12: EXCEPTION:
1: CORRELATIONùINFORMATION:
[callùid]
9: ERRORS: [errorùcause]
B.2.4 ProbeùTAPDU
3.2: PROBE:
B.2.5 ProbeAckùTAPDU
3.15: PROBEùACK:
1: CORRELATIONùINFORMATION:
[callùid]
66: PROBEùID:
[probeùmsgùid]
33: SUBMISSIONùTIME:
[submissionùtime]
B.2.6 ExplicitRNùTAPDU
3.6: EXPLICITùRN:
15: RECIPIENTS:
[recipientùname]
13: PRIORITY:[priorityùind]
71: SUBJECTùIPM:
[subjectùipmùid]
69: IPNùORIGINATOR:
[ipnùoriginatingùuser]
47: TIMEùOFùRECEIPT:
[receiptùtime]
44: CONVERTEDùINFORMATIONùTYPES:
[ [eIT], ]
B.2.7 ExplicitRNAckùTAPDU
3.16: EXPLICITùRNùACK:
1: CORRELATIONùINFORMATION:
[callùid]
65: SUBMISSIONùID:
[submissionùmsgùid]
33: SUBMISSIONùTIME:
[submissionùtime]
B.2.8 CancelùTAPDU
3.13: CANCEL:
65: SUBMISSIONùID:
[submissionùmsgùid]
1: CORRELATIONùINFORMATION:
[callùid]
B.2.9 DeliverùTAPDU
3.3: DELIVER:
62: QUANTITYùOFùDOCS:[numberùofùdocs]
13: PRIORITY:[priorityùind]
14: ORIGINATOR:
[originatorùname]
39: THISùRECIPIENT:
[thisùrecipientùname]
40: INTENDEDùRECIPIENT:
[intendedùrecipientùname]
41: OTHERùRECIPIENTS:
[ [otherùrecipientùname] `NL` ]
33: SUBMISSIONùTIME:
[submissionùtime]
35: DELIVERYùID:
[deliveryùmsgùid]
42: CONVERSIONùINDICATION:
[ [eIT], ] [conversionùprohibition]
44: CONVERTEDùINFORMATIONùTYPES:
[ [eIT], ]
27: THISùIPM:
[thisùipmùid]
20: FROM:
[originatingùuser]
21: AUTHORIZING:
[ [authorizingùuser] `NL` ]
22: TO:
[ [primaryùrecipient] `NL`
=[rnùrequest],[nrnùrequest],[returnùrequest],[replyù
request] `NL` ]
23: CC:
[ [copyùrecipient] `NL`
=[rnùrequest],[nrnùrequest],[returnùrequest],[replyù
request] `NL` ]
24: BCC:
[ [blindùcopyùrecipient] `NL`
=[rnùrequest],[nrnùrequest],[returnùrequest],[replyù
request] `NL` ]
30: REPLIEDùTOùIPM:
[repliedùtoùipmùid]
29: OBSOLETES:
[ [obsoletedùipmùid] `NL` ]
28: RELATEDùIPMS:
[ [relatedùipmùid] `NL` ]
26: SUBJECT:
[subjectùcontent]
18: CONTENTùINDICATOR:
[expiryùtime] `NL`
=[importance],[sensitivity],[autoforwarded]
25: REPLY:
[replyùtime] `NL`
[ [replyùrecipient] `NL` ]
67: EXTENSIONS:
[ [extensionùtype] `NL`
[extensionùvalue] `NL` ]
31: BODYùTYPE:[bodyùpart]
32: FORWARDEDùINFO:
[forwardedùtime] `NL`
//The deliveryùenvelope follows.
B.2.10 ReceiptStatusNoticeùTAPDU
3.5: RECEIPTùSTATUSùNOTICE:
62: QUANTITYùOFùDOCS:[numberùofùdocs]
13: PRIORITY:[priorityùind]
35: DELIVERYùID:
[deliveryùid]
14: ORIGINATOR:
[originatorùname]
39: THISùRECIPIENT:
[thisùrecipientùname]
33: SUBMISSIONùTIME:
[submissionùtime]
4: TIMEùOFùDELIVERY:
[deliveryùtime]
42: CONVERSIONùINDICATION:
[ [eIT], ] [conversionùprohibition]
44: CONVERTEDùINFORMATIONùTYPES:
[ [eIT], ]
43: NOTIFICATIONùTYPE:[reportùtype]
71: SUBJECTùIPM:
[subjectùipmùid]
69: IPNùORIGINATOR:
[ipnùoriginatingùuser]
70: PREFERREDùRECIPIENT:
[preferredùrecipient]
//The following three elements appear in case of RN.
47: TIMEùOFùRECEIPT:
[receiptùtime]
48: TYPEùOFùRECEIPT:
[typeùofùreceipt]
68: SUPPLEMENTARYùINFORMATION:
[supplùreceiptùinfo]
//The following three elements appear in case of NRN.
49: NONùRECEIPTùINFO:
[nonùreceiptùreason],[discardùreason]
50: COMMENTS:
[comments]
51: MESSAGEùRETURNEDùINDICATION:
B.2.11 DeliveryStatusNoticeùTAPDU
3.4: DELIVERYùSTATUSùNOTICE:
62: QUANTITYùOFùDOCS:[numberùofùdocs]
1: CORRELATIONùINFORMATION:
[callùid]
65: SUBMISSIONùID:
[submissionùmsgùid]
66: PROBEùID:
[probeùmsgùid]
[ //repeated for each recipient
3: REPORTEDùRECIPIENT:
[reportedùrecipientùname]
43: NOTIFICATIONùTYPE:[reportùtype]
40: INTENDEDùRECIPIENT:
[intendedùrecipientùname]
44: CONVERTEDùINFORMATIONùTYPES:
[ [eIT], ]
//The following three elements appear in case of DN.
4: TIMEùOFùDELIVERY:
[deliveryùtime]
45: TYPEùOFùUA:
[typeùofùua]
68: SUPPLEMENTARYùINFORMATION:
[supplùinfo]
//The following two elements appear in case of NDN.
46: NONùDELIVERYùREASON:
[reasonùcode],[diagnosticùcode]
]
72: CONTENTùRETURNEDùINDICATION:
B.2.12 RegisterùTAPDU
3.11: REGISTER:
73: EXPIREDùDISCARD:[discardùipm]
74: OBSOLETEDùDISCARD:[discardùipm]
76: AUTOùFWDùIPMS:
[autoùfwdùipms]
77: AUTOùFWDùRECIPIENTS:
[ [autoùfwdùrecipient], ]
78: AUTOùFWDùHEADING:
[autoùfwdùheading]
79: AUTOùFWDùCOMMENT:
[autoùfwdùcomment]
58: DSùMODE:[dsùmode]
59: TLMAUùOPERATION:[errorùrecoveryùmode],[autoù
acknowledgement]
60: AUTOùOUTPUT:
[frequency] `NL`
[outputùtime]
81: MESSAGEùDELETEùMODE:[messageùdeleteùmode]
//and other components require further study.
B.2.13 RegisterAckùTPDU
3.11: REGISTERùACK:
B.2.14 DSQueryùTAPDU
3.7: DSùQUERY:
B.2.15 DSReportùTAPDU
3.8: DSùREPORT:
[ //repeated for each message
38: RETRIEVALùID:
[retrievalùid]
52: MESSAGEùTYPE:[messageùtype]
14: ORIGINATOR:
[originatorùname]
13: PRIORITY:[priorityùind]
37: MESSAGEùLENGTH:[messageùlength]
]
B.2.16 MessageDeleteùTAPDU
3.18: MESSAGEùDELETE:
82: MESSAGEùSELECTOR:
[ [retrievalùid] `NL` ]
B.2.17 OutputRequestùTAPDU
3.9: OUTPUTùREQUEST:
[ //repeated for each retrieval identifier
38: RETRIEVALùID:
[retrievalùid]
80: DELETEùAFTERùOUTPUT:[deleteùafterùoutput]
]
B.2.18 OutputMessageùTAPDU
3.10: OUTPUTùMESSAGE:
[ //repeated for each message
62: QUANTITYùOFùDOCS:[numberùofùdocs]
38: RETRIEVALùID:
[retrievalùid]
52: MESSAGEùTYPE:[messageùtype]
4: TIMEùOFùDELIVERY:
[deliveryùtime]
]
The remaining Components of this TAPDU are identical to the com-
ponents in the Delivery. DeliveryStatusNotice and ReceiptStatusNoticeù
TAPDU. The actual components to be used depend upon the Message Type
parameter value specified in the Message Type component.
B.2.19 StatusQueryùTAPDU
3.19: STATUSùQUERY:
14: ORIGINATOR:
[originatorùname]
65: SUBMISSIONùID:
[submissionùmsgùid]
1: CORRELATIONùINFORMATION:
[callùid]
B.2.20 StatusReportùTAPDU
3.20: STATUSùREPORT:
1: CORRELATIONùINFORMATION:
[callùid]
84: TIMEùOFùREPORT:
[reportùtime]
75: REPORTEDùMESSAGEùID:
[reportedùmessageùid]
[ //repeated for each message
83: MESSAGEùSTATUS:
[status]
4: TIMEùOFùDELIVERY:
[deliveryùtime]
45: TYPEùOFùUA:
[typeùofùua]
46: NONùDELIVERYùREASON:
[reasonùcode],[diagnosticùcode]
]
ANNEX C
(to Recommendation T.330)
Element ID list
This Annex provides a table which maps the coding of TAPDU and
the corresponding element ID. The element ID list Table Cù1/T.330
comprises:
1) The first column contains the element number and element name, as
defined in º 11 of this Recommendation.
2) The second column contains the TAPDUId or ElementId name
defined in º 10 of this Recommendation.
3) The third column contains the type of the TAPDU element, defined
in º 10 of this Recommendation.
4) The fourth column contains the Remarks.
TABLE Cù1/T.330
Element ID list
TAPDUId/element ID
Name
Type
Remarks
3.1:SEND:
send
ù
3.2:PROBE:
probe
ù
3.3:DELIVER:
deliver
ù
3.4:DELIVERYùSTATUSù
NOTICE:
deliveryStatus-
Notice
ù
3.5:RECEIPTùSTATUSù
NOTICE:
receiptStatus-
Notice
ù
3.6:EXPLICITùRN:
explicitRN
ù
3.7:DSùQUERY:
dsQuery
ù
3.8:DSùREPORT:
dsReport
ù
3.9:OUTPUTùREQUEST:
outputRequest
ù
3.10:OUTPUTùMESSAGE:
outputMessage
ù
3.11:REGISTER:
register
ù
3.12:EXCEPTION:
exception
ù
3.13:CANCEL:
cancel
ù
3.14:SENDùACK:
sendAck
ù
3.15:PROBEùACK:
probeAck
ù
3.16:EXPLICITùRNùACK:
explicitRNAck
ù
3.17:REGISTERùACK:
registerAck
ù
3.18:MESSAGEùDELETE:
messageDelete
ù
3.19:STATUSùQUERY:
statusQuery
ù
3.20:STATUSùREPORT:
statusReport
ù
1:CORRELATIONùINFOR-
MATION:
correlationInfo
Primitive
2:
Reserved
for CF
3:REPORTEDùRECIPIENT:
reportedRecip-
ient
Primitive
4:TIMEùOFùDELIVERY:
timeOfDeliv-
ery
Primitive
5:
Reserved for
CF
6:
Reserved
for CF
7:
Reserved
for CF
8:
Reserved
for CF
9:ERRORS:
errors
Primitive
10:
Reserved
for CF
11:
Reserved
for CF
12:RECEIVEDùTID:
Reserved
for CF
13:PRIORITY:
priority
Primitive
14:ORIGINATOR:
originator
Con-
structor
15:RECIPIENTS:
recipients
Con-
structor
16:CONVERSION:
conversion
Primitive
17:CONTENTùINFO:
contentInfo
Con-
structor
18:CONTENTùINDICATOR:
contentIndica-
tor
Con-
structor
19:FLAG:
per Message
Indicator
Con-
structor
TABLE Cù1/T.330 (cont.)
TAPDUId/element ID
Name
Type
Remarks
20:FROM:
from
Primitive
21:AUTHORIZING:
authorizing
Con-
structor
22:TO:
to
Con-
structor
23:CC:
cc
Con-
structor
24:BCC:
bcc
Con-
structor
25:REPLY:
reply
Con-
structor
26:SUBJECT:
subject
Primitive
27:THISùIPM:
thisIPM
Primitive
28:RELATEDùIPMS:
relatedIPMS
Con-
structor
29:OBSOLETES:
obsoletedIPMS
Con-
structor
30:REPLIEDùTOùIPM:
repliedToIPM
Primitive
31:BODYùTYPE:
bodyType
Con-
structor
32:FORWARDEDùINFO:
forwardedInfo
Con-
structeur
For fur-
ther study
33:SUBMISSIONùTIME:
submission-
Time
Primitive
34:LATESTùDELIVERY:
date and time
Primitive
35:DELIVERYùID:
deliveryId
Primitive
36:RETURNùADDRESS:
return address
Primitive
37:MESSAGEùLENGTH:
message-
Length
Primitive
38:RETRIEVALùID:
retrievalId
Primitive
39:THISùRECIPIENT:
thisRecipient
Primitive
40:INTENDEDùRECIPIENT:
intendedRecip-
ient
Primitive
41:OTHERùRECIPIENTS:
otherRecipi-
ents
Con-
structor
42:CONVERSIONùINDICA-
TION:
conversion-
Indication
Con-
structor
43:NOTIFICATIONùTYPE:
notification-
Type
Primitive
44:CONVERTEDùINFOR-
MATIONùTYPES:
convertedInfo-
Types
Primitive
45:TYPEùOFùUA:
typeOfUA
Primitive
46:NONùDELIVERYùREA-
SON:
nonDelivery-
Reason
Primitive
47:TIMEùOFùRECEIPT:
timeOfReceipt
Primitive
48:TYPEùOFùRECEIPT:
typeOfReceipt
Primitive
49:NONùRECEIPTùINFO:
nonReceipt-
Info
Primitive
50:COMMENT:
comment
Primitive
51:MESSAGEù
RETURNEDùINDICATION:
messageRe-
turnedInd
ù
52:MESSAGEùTYPE:
messageType
Primitive
53:LANGUAGE:
languageInd
Primitive
54:REDIRECTEDùFROM:
redirected from
Con-
structor
TABLE Cù1/T.330 (end)
TAPDUId/element ID
Name
Type
Remarks
55:
ù
ù
Not used
56:
ù
ù
Not used
57:
ù
ù
Not used
58:DSùMODE:
dsMode
Primitive
59:TLMAUùOPERATION:
tLMAUOpera-
tion
Con-
structor
60:AUTOùOUTPUT:
autoOutput
Con-
structor
61:
ù
ù
Not used
62:QUANTITYùOFùDOCS:
quantityOf-
Docs
Primitive
63:
Not assigned
64:
Not assigned
65:SUBMISSIONùID:
submissionId
Primitive
66:PROBEùID:
probeId
Primitive
67:MSGùINCOMPLETE:
68:SUPPLEMENTARYù
INFORMATION:
supplReceipt-
Info
SupplInfo
Primitive
69:IPNùORIGINATOR:
IPNOriginator
Primitive
70:PREFERREDùRECIPI-
ENT:
preferre-
dRecipient
Primitive
71:SUBJECTùIPM:
subjectIPM
Primitive
72:CONTENTù
RETURNEDùINDICATION:
contentRe-
turned
ù
73:EXPIREDùDISCARD:
expiredDiscard
Primitive
74:OBSOLETEDùDIS-
CARD:
obsoletedDis-
card
Primitive
75:REPORTEDùMES-
SAGEùID:
reportedMes-
sageId
Primitive
76:AUTOùFWDùIPMS:
autoFWDIPMs
Primitive
77:AUTOùFWDùRECIPI-
ENTS:
autoFW-
DRecipient
Primitive
78:AUTOùFWDùHEAD-
ING:
autoFWD-
Heading
Con-
structor
For fur-
ther study
79:AUTOùFWDùCOM-
MENT:
autoF-
WDComment
Primitive
80:DELETEùAFTERùOUT-
PUT:
deleteAfter-
Output
Primitive
81:MESSAGEùDELETEù
MODE:
messageDele-
teMode
Primitive
82:MESSAGEùSELECTOR:
messageSelec-
tor
Con-
structor
83:MESSAGEùSTATUS:
messageStatus
Primitive
84:TIMEùOFùREPORT:
timeOfReport
Primitive
Conventions:
1) Primitive: element contains only one component
2) Constructor: element contains more than one component
3) : space character
ANNEX D
(to Recommendation T.330)
Element of service for TTX/IPM service intercommunication
This PTXAU provides only the services listed in Table Dù1/T.330 to
telematic users. These services may be implemented using only the mhsù
docùxfer abstract operations: message send, message delivery, receipt sta-
tus notice and delivery status notice.
When a nonùregistered user attempts to access a service not within the
PTTXAU set of services, then a subscription error will be returned.
TABLE Dù1/T.330
Element of service
Referen
ce Rec.
F.400
Annex B
F.400 Elements of service
Message
submissio
n from
TTX to
PTTXAU
Message
delivery
to TTX
from
PTTXAU
Informati
on gener-
ated by
PTTXAU
B.5
Authorizing users indica-
tion
X
B.6
Autoùforwarded indica-
tion
X
B.8
Blind copy recipient indi-
cation
X
B.9
Body part encryption indi-
cation
X
B.12
Content type indication
X
X
B.13
Conversion prohibition
X
X
B.15
Converted indication
X
B.18
Crossùreferencing indica-
tion
X
B.21
Delivery notification
X
NA
X
B.22
Delivery time stamp indi-
cation
X
X
B.25
Disclosure of other recipi-
ents
X
B.26
DL expansion history indi-
cation
X
X
B.29
Expiry date indication
X
B.31
Forwarded IPùmessage
indication
X
B.32
Grade of delivery selection
X
X
B.34
Implicit conversion
X
B.35
Importance indication
X
B.37
IPùmessage identification
X
B.38
Language indication
X
B.39
Latest delivery designation
X
B.41
Message indentification
X
B.45
Multiùdestination deliv-
ery
X
NA
X
B.46
Multiùpart body
X
B.47
Nonùdelivery notification
NA
B.48
Nonùreceipt notification
request indication
X
NA
B.52
Obsoleting indication
X
B.54
Original encoded informa-
tion types indication
X
X
B.55
Originator indication
X
B.56
Originator requested alter-
nate recipient
X
X
B.62
Primary and copy recipi-
ents indication
X
B.72
Reply request indication
X
B.73
Replying IPùmessage
indication
X
B.80
Sensitivity indication
X
B.88
Subject indication
X
X
B.89
Submission time stamp
indication
X
NA No applicable
X Applicable