1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 4 TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU4%2-).!,G0G0%15)0-%.4G0G0!.$G0G002/4/#/,3G0G0(b) the need to transfer messages of different types having a large variety of formats;(c) that within the X Series of Recommendations services and optional user f
2、acilities for public data networksare defined;(d) that the F Series of Recommendations defines telematic services and that the T Series ofRecommendations defines terminal equipment and control procedures for telematic services;(e) that a set of Recommendation describes various aspects of message han
3、dling systems: X.400 Series;(f) that Recommendation T.300 describes general principles of telematic interworking,unanimously declaresthat this Recommendation describes the access protocol to be used by telematic terminals when makingadditional use of the interpersonal messaging system.CONTENTS0 Intr
4、oduction1 Scope and field of application2 References3 Definitions4 Abbreviations5 Conventions6 Overview of telematic access to IPMS6.1 Abstract model6.2 Functional model6.3 Access for registered and non-registered users7 IPMS in the context of telematic interworking7.1 Objects and ports description7
5、.2 Origination, reception and management ports, services and operations7.3 Miscellanea port services and operations8 Refinement of the TLMA object8.1 Object and ports description8.2 The mhs-doc-xfer port operations2 Fascicle VII.5 - Rec. T.3309 Abstract errors10 Realization of abstract operations10.
6、1 Description of TAPDU10.2 Operation of the TLMAU11 Formats and coding of TAPDU11.1 Principles11.2 Structure and format of TAPDU11.3 Coding of TAPDU11.4 Format of TAPDU11.5 Reference between TAPDU components and its coding format12 Error recovery13 Control procedures13.1 Session control procedures13
7、.2 Document control procedures13.3 Log-on proceduresAnnex A - Formal definition of TLMA abstract serviceAnnex B - Format of TAPDU componentsAnnex C - Element ID listAnnex D - Element of service for TTX/IPM service intercommunications0 IntroductionRecommendation T.330 is one of a series of Recommenda
8、tions dealing with telematic interworking. Telematicinterworking is the generic name for a set of applications provided to telematic users. Each of those applications is calleda telematic interworking application (TIA).Access to and participating in interpersonal messaging system (IPMS) are one of t
9、he telematic interworkingapplications. This Recommendation aims at specifying this application.1 Scope and field of applicationThis Recommendation defines the abstract service provided by the telematic agent (TLMA) which is definedas an object of IPMS. It specifies not only abstract operations provi
10、ded by TLMAU but also access protocol (P5) to beused between a TLMAU and a telematic (TLM) terminal, when participating in and accessing the IPMS. The P5 accessprotocol is a generalized access protocol; it is applicable to other applications such as network based storage for theteletex service. The
11、TLM terminals being considered in this Recommendation are teletex, G4 facsimile and mixed modeterminals. The use of other types of TLM terminals are for further study.Other Recommendations in the series contain description on telematic interworking model, the functions of thetelematic access unit (T
12、LMAU), and telematic access protocol to specific services, such as telematic, telex, directory,etc. Recommendation T.300 outlines the principles of telematic interworking procedures.Section 6 of this Recommendation defines overview of telematic access to IPMS provided by TLMA object.Section 7 define
13、s the IPMS in the context of telematic interworking. Section 8 refines the TLMA object and definesabstract operations at a specific port of TLMAU and TLM terminal. Section 9 defines abstract errors used in telematicinterworking. Section 10 specifies an access protocol (P5). Section 11 specifies form
14、atting and coding rule of protocol.Section 12 specifies an error recovery mechanism. Section 13 specifies control procedures.Fascicle VII.5 - Rec. T.330 3The purpose of a TLMAU is to aid the user of a TLM terminal in gaining access to the features of the IPMS.The TLMAU, which is associated with a me
15、ssage transfer system (MTS), provides the TLM terminal with access to theIPMS.The TLMAU may also provide a document storage (DS) facility to accept delivery of messages from the MTSfor TLM users. Document storage is basically defined as a TLM terminal storage extension facility located in theTLMAU a
16、llowing reservation of a specific amount of storage for an individual user. Users of TLM terminals may alsobe registered as users of DS.2 ReferencesThis Recommendation cites the documents listed below.2.1 Telematic interworking- Rec. T.300: General principles of telematic interworking.2.2 Message ha
17、ndling systems- Rec. X.400: Message handling systems: System and service overview- Rec. X.402: Message handling systems: Overall architecture- Rec. X.407: Message handling systems: Abstract service definition conventions- Rec. X.411: Message handling systems: Message transfer system: Abstract servic
18、e definition andprocedures- Rec. X.413: Message handling systems: Message store: Abstract service definition- Rec. X.419: Message handling systems: Protocol specifications- Rec. X.420: Message handling systems: Interpersonal messaging system2.3 Control procedures- Rec. T.62: Control procedures for T
19、eletex and Group 4 facsimile services2.4 ASN.1 coding- Rec. X.208: Specification of abstract syntax notation one (ASN.1)- Rec. X.219: Remote operation2.5 Address- Rec. X.121: International numbering plan for public data networks2.6 Character repertoires- Rec. T.61: Character repertoire and coded cha
20、racter sets for the international Teletex service2.7 Intercommunication- Rec. F.422: Intercommunication between Teletex service and IPM service.- Rec. F.203: Network based storage for the Teletex service.3 DefinitionsThis Recommendation uses the terms many of those used in Recommendations X.402, X.4
21、11 and X.420.In addition to the above terms, this Recommendation uses as terms the names of abstract objects, ports,operations and errors; the names of ASN.1 data types; the names of the information item types and values thisRecommendation specifies.4 Fascicle VII.5 - Rec. T.3304 AbbreviationsASN.1
22、Abstract syntax notation oneAU Access unitC Conditional/consumerCDC Command document continueCF Conversion facilityCSCC Command session change controlCSS Command session startDN Delivery status notificationDS Document storageG3 Group 3 facsimileG4 Group 4 facsimileID IdentityIP InterpersonalIPM Inte
23、rpersonal messagingIPMAS Interpersonal messaging abstract serviceIPME Interpersonal messaging environmentIPMS Interpersonal messaging systemIPM-UA Interpersonal messaging user agentIPN Interpersonal notificationM MandatoryS Message storeT Message transferTA Message transfer agentTAS Message transfer
24、 abstract serviceMTS Message transfer systemNDN Non-delivery status notificationNL New lineNRN Non-receipt notificationO/R Originator/receiptPDAU Physical delivery access unitPTTXAU Public Teletex access unitP5 Telematic access protocolRN Receipt status notificationS SupplierTAPDU Telematic access p
25、rotocol data unitTIA Telematic interworking applicationTID Terminal identificationTLM TelematicTLMA Telematic agentTLMAU Telematic access unitTLM-TER Telematic terminalTLXAU Telex access unitTTXTeletexUA User agentFascicle VII.5 - Rec. T.330 55 ConventionsThis Recommendation uses the descriptive con
26、ventions identified below.5.1 ASN.1This Recommendation uses the following ASN.1-based descriptive conventions for the indicated purposes:a) to specify the functional objects, the OBJECT and REFINE macros and associated conventions ofRecommendation X.407;b) to specify the information objects (and oth
27、er data types and values of all kinds), ASN.1 itself;c) to specify the abstract service, the PORT and ABSTRACT-BIND, -UNBIND, -OPERATION, and-ERROR macros and associated conventions of Recommendation X.407.5.2 GradeWhenever this Recommendation describes a class of data structure (e.g. Headings) havi
28、ng components (e.g.fields), each component is categorized as one of the following grades:a) Mandatory (M): A mandatory component shall be present in every member of the class.b) Conditional (C): A conditional component shall be present in a member of the class as dictated by thisRecommendation.6 Ove
29、rview of telematic access to IPMS6.1 Abstract modelThis Recommendation makes use of the message handling abstract service definitions conventions defined inRecommendation X.407. These conventions provide a descriptive tool for the specification of information processingtasks in abstract terms. This
30、ensures that a tasks functional requirements are stated independently of its realization.6.2 Functional modelThis section provides a functional model of telematic access to IPMS. The purpose of this model is to providea general description of the functional entities, which are then explicitly define
31、d using the definitions and conventionsfound in Recommendation X.407, and further refined as necessary, in following sections (see Figure 1/T.330).FIGURE 1/T.330Telematic access to IPMS: Functional model6 Fascicle VII.5 - Rec. T.330The functional model comprises the following functional entities:- T
32、elematic agent (TLMA): Logical entity only which comprises the TLMAU and the telematic terminal.The TLMA is useful as an object in the refinement of the IPMS.- Telematic access unit (TLMAU): Functional entity which provides all of the interworking functionsbetween telematic codes and protocols and I
33、PMS codes and protocols. The TLMAU also supports the DSfunctionality.- Telematic terminal (TLM-TER): The telematic terminal.- Access unit (AU): Functional entity which provides access to message handling applications for indirectusers of the MTS.- Document storage (DS): Extension of the telematic te
34、rminal storage capabilities. The TLMAU mayoptionally, on a subscription basis, deliver messages to a DS. The terminal may then retrieve the messagefor the document storage when convenient.- Message store (MS): Functional entity which provides single direct user of message handling withcapabilities f
35、or message storage. Although the MS and DS provide a similar functionality, there is norelationship between the two.- Message transfer system (MTS): Functional entity which conveys information objects between individualusers and members of distribution lists.- User agent (UA): Functional entity by m
36、eans of which a direct user engages in message handling.6.3 Access for registered and non-registered usersTwo types of access to the IPM service are defined within this Recommendation. Registered users of the IPMservice who wish to use telematic terminal equipment to access the IPM service are provi
37、ded with complete IPM servicefunctionality with any full implementation of this Recommendation.Telematic terminal equipment users who are not registered IPM service subscribers but who wish to direct amessage to an IPM service user are provided with a subset of the functionality defined within this
38、Recommendation, inaccordance with Recommendation F.422 and Annex D of this Recommendation. This functionality is referred to as apublic teletex access unit (PTTXAU).7 IPMS in the context of telematic interworking7.1 Objects and ports descriptionThe refinement of the IPMS is found in Recommendation X
39、.420 (interpersonal messaging system). The IPMSrefinement describes secondary objects, one of which is the telematic agent (TLMA) which is paired to the MTS by theimport and export ports.The TLMA is visible to the telematic user through four ports, namely: origination, reception, management andmisce
40、llanea. The origination, reception and management port services and operations are described fully inRecommendation X.420. The miscellanea port services and operations are described in this Recommendation. Theimport and export port services and operations are described in Recommendation X.411.tlma O
41、BJECTPORTS origination S,reception S,management S,miscellanea S,import C,export C: = id-ot-tlmaThe IPMS comprises any number of TLMA.TLM users are communicants in telematic interworking. A TLM user originates or receives informationobjects whose types are specified in Recommendation X.420 and this R
42、ecommendation.Fascicle VII.5 - Rec. T.330 7tlm-user OBJECTPORTS origination C,reception C,management C,miscellanea C: = id-ot-tlm-userA telematic user is associated with the TLMA by means of the origination, reception, management andmiscellanea ports. A telematic user is a supplier S of no ports and
43、 a consumer C of all TLMA ports. The TLMA is asupplier of all TLMA ports and consumer of no ports.The general access to IPMS is illustrated in Figure 2/T.330.FIGURE 2/T.330General access to IPMSAn interpersonal messaging user agent (IPM-UA) is a secondary object that provides the interpersonalmessag
44、ing abstract service (IPMAS) to a single IPM user. An IPM-UA is a specialized instance of the more generalobject, UA. An IPM-UA performs its function with help from the MTS.A telematic agent (TLMA) is an object that provides the abstract service which comprises IPMAS andtelematic specific abstract s
45、ervice, to a single TLM user. A TLMA is an instance of the more general object UA. ATLMA performs its function with help from the MTS.A message transfer system (MTS), upon which all other IPMS components relay, is the provider of themessage transfer abstract service (MTAS). It performs its function
46、without assistance.An interpersonal messaging system (IPMS) is the object by means of which all users communicate ininterpersonal messaging.The access unit (AU) could be a physical delivery access unit (PDAU), or telex access unit (TLXAU). Thedescriptions of these objects found in relevant Recommend
47、ations,8 Fascicle VII.5 - Rec. T.3307.2 Origination, reception and management ports, services and operationsThe abstract operations available at these ports, as described in X.420, are:origination PORTCONSUMER INVOKERS OriginateProbe,OriginateIPM,OriginateRN,CancelIPM : = id-pt-originationreception
48、PORTCONSUMER INVOKERS ReceiveReport,ReceiveIPM,ReceiveRN,ReceiveNRN : = id-pt-receptionmanagement PORTCONSUMER INVOKERS ChangeAutoDiscard,ChangeAutoAcknowledgment,ChangeAutoForwarding : = id-pt-managementThe abstract operations are fully described in Recommendation X.420.7.3 Miscellanea port service
49、s and operationsBesides IPM abstract services, the following abstract services are available at the miscellanea port. They areprovided by the TLMA object as the miscellanea abstract services.miscellanea PORTSUPPLIER PERFORMS ChangeSubscriptionProfile,DSList,DSDelete,DSFetch,MessageStatus : = id-pt-miscellanea7.3.1 ChangeSubscriptionProfileThe ChangeSubscriptionProfile abstract operation enables a user to change the registered subscription profilewhich specifies relationship with the TLMAU, such as DS mode, error recovery mode and message delete
