`
`
`
`
`
`INTERNATIONAL TELECOMMUNICATION UNION
`
`_. “571%
`
`c C ITT
`
`THE INTERNATIONAL
`TELEGRAPH AND TELEPHONE
`CONSULTATIVE COMMITTEE
`
`jI/FMF-{L I (2:
`
`_
`BLUE BOOK
`
`ELIE-E153- ELI-III???
`260w FLO‘KDRD
`RICHARDSON TX 75083
`
`VOLUME || — FASCICLE ”.6
`
`“MESSAGE HANDLING
`
`AND DIRECTORY SERVICES, /,
`
`OPERATIONS AND DEFINITION OF SERVICE
`
`RECOMMENDATIONS F.400~F.422, F.500
`
`IXTH PLENARY ASSEMBLY
`
`MELBOURNE, 14~25 NOVEMBER 1988
`
`KR
`\x,
`
`(Y)
`‘ W
`
`i
`
`Geneva 1939
`Page 1 of 79
`
`IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIHIIIIIIIIIIII
`
`'
`
`AT&T EXHIBIT 1019
`
`Page 1 of 79
`
`AT&T EXHIBIT 1019
`
`

`

`
`
`
`
`© ITU
`
`Printed in Switzerland
`
`Page 2 Of 79
`
`Page 2 of 79
`
`

`

`
`
`CONTENTS OF THE CCIT’I‘ BOOK
`APPLICABLE AFTER THE NINTH PLENARY ASSEMBLY (1988)
`
`BLUE BOOK
`
`Volume I
`
`FASCICLE 1.1
`
`Minutes and reports of the Plenary Assembly.
`
`«.-
`
`List of Study Groups and Questions under study.
`
`FASCICLB 1.2
`
`Opinions and Resolutions.
`
`Recommendations on the organization and working procedures of CCITT (Series A).
`
`Terms and definitions. Abbreviations and acronyms. Recommendations on means of
`expression (Series B) and General telecommunications statistiCs (Series C).
`Index of Blue Book.
`
`General tariff principles — Charging and accounting in international telecommunications
`services. Series D Recommendations (Study Group 111).
`Telephone network and ISDN — Operation, numbering,
`Recommendations E.100—E.333 (Study Group 11).
`
`routing and mobile service.
`
`Telephone network and ISDN - Quality of service, network management and traffic
`engineering. Recommendations BABE—13.880 (Study Group II}.
`
`Telegraph and mobile services — Operations and quality of service. Recommenda—
`tions F.1—F.140 (Study Group I).
`
`Telematic, data transmission and teleconference services — Operations and quality of
`service. Recommendations F.160—F.353, F.600, F.601, Rifle-F1730 (Study Group 1).
`
`Message handling and directory services — Operations and definition of service. Recom-
`mendations F.400—FA-22, F500 (Study Group 1).
`
`General characteristics of international telephone connections and circuits. Recommenda-
`tions 610043.181 (Study Groups X11 and XV).
`
`International analogue carrier systems. Recommendations Gill-(3.544 (Study Group XV).
`
`Transmission media 7 Characteristics. Recommendations 6601-6654 (Study Group XV).
`
`transmission systems;
`General aspects of digital
`tions G.700-G.795 (Study Groups XV and XVIII).
`
`terminal equipments. Recommenda-
`
`Digital networks, digital sections and digital line systems. Recommendations G.801-G.961
`(Study Groups XV and XVIII).
`
`111
`
`FASCICLE 1.3
`
`FASCICLE 1.4
`
`Volume II
`
`FASCICLE 11.1
`
`FASCICLE 11.2
`
`FASCICLE 11.3
`
`FASCICLE 11.4
`
`FASCICLE 11.5
`
`FASCICLE 11.6
`
`Volume III
`
`FASCICLE 111.1
`
`FASCICLE 111.2
`
`FASCICLE 111.3
`
`FASCICLE 111.4
`
`FASCICLE 111.5
`
`Pat—36 3 of 79
`
`Page 3 of 79
`
`

`

`FASCICLE 111.6
`
`Line transmission of non-telephone signals. Transmission of sound-programme and televi-
`sion signals. Series H and .1 Recommendations (Study Group XV).
`
`FASCICLE 111.7
`
`Integrated Services Digital Network (ISDN) , General structure and service capabilities.
`Recommendations 1.1101257 (Study Group XVIII).
`
`FASCICLE 111.8
`
`Integrated Services Digital Network (ISDN) — Overall network aspects and functions,
`ISDN user-network interfaces. Recommendations 1.3101470 {Study Group XVIII).
`
`FASCICLE 111.9
`
`Integrated Services Digital Network (ISBN) 7 lnternetwork interfaces and maintenance
`principles. Recommendations 1500-1605 (Study Group XVIII).
`
`Volume IV
`
`FASCICLE 1V.l
`
`FASCICLE [VJ
`
`transmission systems and
`General maintenance principles: maintenance of international
`telephone circuits. Recommendations M.10-M.782 (Study Group IV).
`
`Maintenance of internationai telegraph, phototelegraph and leased circuits. Maintenance of
`the international public telephone network. Maintenance of maritime satellite and data
`transmission systems. Recommendations M.8004M.1375 (Study Group IV).
`
`FASCICLE IV.3
`
`sound-programme and television transmission Apircuits.
`international
`Maintenance of
`Series N Recommendations (Study Group IV).
`
`FASCICLE IVA
`
`Specifications for measuring equipment. Series 0 Recommendations (Study Group IV).
`
`Volume V
`
`Telephone transmission quality. Series P Recommendations (Study Group XII).
`
`Volume V1
`
`FASCICLE V1.1
`
`General Recommendations on telephone switching and signalling. Functions and informa-
`tion flowa for services in the ISDN. Supplements. Recommendations Q.1-Q.118 bis (Study
`Group XI).
`
`FASCICLE V1.2
`
`Specifications of Signalling Systems Nos. 4 and 5. Recommendations Q.120-Q.180 (Study
`Group X1).
`
`FASCICLE V1.3
`
`Specifications of Signalling System No.
`Group X1).
`
`6. Recommendations Q.251-Q.300 (Study
`
`FASCICLE V1.4
`
`Specifications of Signalling Systems R1 and R2. Recommendations Q.310-Q.490 (Study
`Group X1).
`
`FASCICLE V1.5
`
`Digital local, transit, combined and international exchanges in integrated digital networks
`and mixed analogue-digital networks. Supplements. Recommendations Q.500-Q.554 (Study
`Group'Xl). .
`
`FASCICLE V1.6
`
`lnterworking of signalling systems. Recommendations Q.601—Q.699 (Study Group XI).
`
`FASCICLE V1.7
`
`FASCICLE V1.8
`
`Specifications of Signalling System No.
`Group X1).
`
`Specifications of Signalling System No.
`Group X1).
`
`7. Recommendations Q.700-Q.716 (Study
`
`7. Recommendations Q.'121-Q.766
`
`(Study
`
`FASCICLE V1.9
`
`Specifications of Signalling System No.
`Group XI).
`
`7. Recommendations Q.771-Q.79S (Study
`
`FASCICLE V1.10
`
`Digital subscriber signalling system No.
`Q.920-Q.921 (Study Group X1).
`
`1
`
`(D38 1), data link layer. Recommendations
`
`[V
`
`Page 4 of 79
`
`Page 4 of 79
`
`

`

`FASCICLE- V1.11
`
`Digital subscriber signalling system No. l (DSS 1), network layer, user-network. manage-
`ment. Recommendations Q.930-Q.94O (Study Group XI).
`
`FASCICLE V1.12
`
`Interworking with ISDN and PSTN. Recommenda-
`Public land mobile network.
`tions Q.10007Q.1032 (Study Group XI).
`-
`
`FASCICLE V1.13
`
`FASCICLE V1.14
`
`Public land mobile network. Mobile application part and interfaces. Recommenda-
`tions Q.1051-Q.1063 (Study Group X1).
`3’
`Interworking with satellite mobile
`systems. Recommendations Q.llUO—Q.1152
`Group XI).
`
`(Study
`
`Volume VII
`
`FASCICLE V111
`
`FASCICLE V112
`
`FASCICLE V113
`
`FASCICLE VIL4
`
`FASCICLE V115
`
`FASCICLE V116
`
`FASCICLB V117
`
`Volume VIII
`
`FASCICLE VIII.1
`
`FASCICLE V1112
`
`FASCICLE V1113
`
`FASCICLE V1114
`
`FASCICLE 1’1115
`
`FASCICLE V1114?
`
`FASCICLE V1117
`
`FASCICLE VIII.8
`
`Telegraph transmission. Series R Recommendations. Telegraph services terminal equip-
`ment. Series S Recommendations (Study Group 1X).
`
`Telegraphiswitching. Series U Recommendations (Study Group 1X).
`Terminal equipment and protocots for
`telematic services. Recommendations T.0-T.63
`(Study Group VIII).
`Conformance testing procedures for the Teletex Recommendations. Recommendation 1264
`(Study Group VIII).
`:3;
`Terminal equipment and protocols for
`telematic services. Recommendations T.65-T.101,
`T.150-T.39I3 (Study Group V111).
`
`Terminal equipment and protocols for telematic services. Recommendations 1400-11418
`(Study Group VIII).
`Terminal equipment and protocols for telematic services. Recommendations T.431-T.564
`(Study Group VIII).
`
`Data communication over
`Group XVII).
`networks:
`Data
`communication
`tions X.1-X.32 (Study Group VII).
`
`the telephone network. Series V Recommendations (Study
`
`services
`
`and
`
`facilities,
`
`interfaces. Recommenda-
`
`transmission, signalling and switching, network aspects,
`Data communication networks:
`maintenance
`and administrative arrangements. Recommendations X.40-X.131 {Study
`Group VII).
`
`Data communication networks: Open Systems Interconnection (OSI) — Model and nota-
`tion, service definition. Recommendations X.200—X.219 (Study Group VII).
`Data communication networks: Open Systems Interconnection (081) a Protocol specifica—
`tions, conformance testing. Recommendations X.220-X.290 (Study Group V11).
`Data communication networks: interworking between networks, mobile data transmission
`systems, internetwork management. Recommendations X.300-X.37fl (Study Group VII).
`Data communication networks: message handling systems. Recommendations X.400«X.420
`(Study Group VII}.
`Data
`communication
`Group V11).
`
`Recommendations X.500-X.521
`
`(Study
`
`networks:
`
`directory.
`
`Volume 1X
`
`Protection against interference. Series K Recommendations (Study Group V). Construction,
`installation and protection of cable and other elements of outside plant. Series L Recom-
`mendations (Study Group V1).
`
`p..._-.
`
`E
`Page 5 of 79
`
`Page 5 of 79
`
`

`

`Volume X '
`
`FASCICLE X.1
`
`Functional Specification and Description Language (SDL). Criteria for using Formal
`Description Techniques (FDTs). Recommendation 21.100 and Annexes A, B, C and E,
`Recommendation Z110 (Study Group X).
`
`FASCICLE X2.
`
`Annex D to Recommendation 2.100: SDL user guidelines (Study Group X).
`
`FASCICLE x.3
`
`FASCICLE x.4
`
`Annex F.1
`Group X).
`
`to Recommendation 2.100: SDL formal definition.
`
`Introduction (Study
`
`Annex F? to Recommendation 2.100: SDL formal definition. Static semantics (Study
`Group X).
`
`FASCICLE X5
`
`Annex F3 to Recommendation 2.100: SDL formal definition. Dynamic semantics (Study
`Group X).
`
`FASCICLE X.6
`
`CCIT’I‘ High Level Language (CHILL). Recommendation 2.200 (Study Group X).
`
`FASCICLE X.7
`
`Man-Machine Language (MML). Recommendations 2301—2341 (Study Group X).3"“
`
`V1
`
`Page 6 of 79
`
`Page 6 of 79
`
`

`

`~in
`
`This material may be protected by Copyright law (Title 17 us. Code)
`
`SECTION 1
`
`MESSAGE HANDLING SERVICES
`
`Recommendation E400 ‘)
`
`5/
`
`MESSAGE HANDLING SYSTEM AND SERVICE OVERVIEW
`
`in various countries of telematic services and computer based store and forward
`The establishment
`messaging services
`in association with public networks creates a need to produce standards to facilitate
`international message exchange between subscribers to such services.
`
`The CCITI',
`
`considering
`
`the need for message handling systems;
`(a)
`the need to transfer and store messages of different types;
`(b)
`that Recommendation X100 defines the reference model of open systems interconnection for CCI’I‘T
`(0)
`applications;
`(d)
`that Recommendations X208, X217, X218 and X219 provide the foundation for CCITI‘ applica-
`
`tions:
`
`that the X.500-Serics Recommendations define directory systems:
`(e)
`that message handling systems are defined in a series of Recommendations: X400, X.402, X.403,
`(t)
`x407, x.4os, x.411, Km and x.419:
`'
`(g)
`that interpersonal message is defined in Recommendation X.420 and T330;
`(11)
`that several F-Serics Recommendations describe public message handling services: E400, R401, R410
`and R420;
`that several F-Series Recommendations describe intercommunication between public message handling
`' (i)
`services and other services: E421, E415 and E422,
`
`unanimously declarer
`the View that the overall system and service overview of message handling is defined in this Recommen-
`
`dation.
`
`
`
`‘) Recommendation X400 is identical to E400.
`
`Fascicle “.6 — Rec. E400
`
`5
`
`Page 7 of 79
`
`

`

`CONTENTS
`
`PART] -— Introduction
`
`0
`
`1
`
`2
`
`3
`
`4
`
`5
`
`Introduction
`
`Scope
`
`References
`
`Definitions
`
`Abbreviations
`
`Conventions
`
`PART 2 — General description of MHS
`
`6
`
`7
`
`8
`
`Purpose
`
`Functional model of MHS
`
`7.1
`7.2
`
`7.3
`7,4
`
`Description of the MHS model
`Structure of messages
`‘
`_
`
`Application of the MHS model
`Message store
`
`Message transfer Serviee
`8.1
`Submission and delivery
`82
`Transfer
`13.3
`Notifications
`8.4
`User agent
`8.5
`Message store
`8.6
`Access unit
`8.?
`Use of the MTS in the provision of public services
`
`9_
`
`.
`
`[PM service
`9:1
`[PM service functional model
`9.2
`Structure of IP—rnessages
`I 9.3
`lP-notif‘ications
`
`-
`
`10
`
`11
`
`Intercommtmicaiion with physical deiivery'services
`10.1
`Introduction
`
`10.2
`
`Organizationai configurations
`
`Specialized Iaccess
`1 1.1
`Introduction
`11.2
`Teietex access
`11.3
`Telex access
`
`PARTS — Capabilities ofMHS
`
`12
`
`Naming and addressing
`12.1
`Introduction
`12.2
`Director},r names
`12.3
`O/R names
`12.4
`O/R addresses
`
`6
`
`Fascicie [1.6 u Rec. E480
`
`Page 8 of 79
`
`Page 8 of 79
`
`

`

`MHS use of directory
`13.1
`Introduction
`13.2
`Functional model
`13.3
`
`Physical configurations
`
`Introduction
`
`' Distribution lists in MHS
`14.1
`14.2
`14.3
`14.4
`14.5
`14.6
`14.7
`14.8
`14.9
`14.10
`14.11
`
`Properties of 3 DL
`Submission
`DL use of a directory
`DL expansion
`
`Nesting
`Recursion control
`
`Delivery
`Routing loop control-
`Notifications
`
`DL handling policyr
`
`13
`
`14
`
`15
`
`16
`
`17
`
`Security capabilities of MHS
`15.1
`Introduction
`15.2
`15.3
`15.4
`15.5
`
`MHS security threats
`Security model
`MHS security features
`Security management
`
`Conversion in MHS
`
`Use of the MHS in provision ofpubiic services
`
`PART 4 — Eiemenis of service
`
`1 8
`
`19
`
`Purpose
`
`Cicssb’icaiicn
`
`19.1
`19.2
`
`19.3
`19.4
`19.5
`
`19.6
`19.7
`19.8
`19.9
`
`Purpose of classification
`Basic message transfer service
`
`MT service optional user facilities
`Base MH/PD service intercommunication
`
`Optional user facilities for MH/PD service intercomrnunication
`Base message store
`MS optional user facilities
`Basic interpersonal messaging service
`1PM service optional user facilities
`
`Annex A — Glossary of terms
`Annex B —— Definitions of elements of service
`
`Annex C — Elements of service modifications with respect to the 1984 Version
`Annex D 7 Differences between CCITT Recommendation E401} and ISO Standard 10021-1
`
`Fascicle I[.6 # Rec. E400
`
`Page 9 of 79
`
`Page 9 of 79
`
`

`

`PART]. — INTRODUCTION
`
`0
`
`Introduction
`
`{1 set of Recommendations for message handling. The entire set provides a
`.
`.
`.
`.1
`handling comprising any number of cooperating open-systems,
`
`This Recommendation is one of
`comprehensive specification for message
`Message handling systems and services enable users to exchange messages on a store-and—forward basis. A
`message submitted by one user, the originator,
`is conveyed by the message transfer system (MTS), the principal
`component of a larger message handling system (MHS), and is subsequently delivered to one or more additional
`users, the message‘s recipients.
`
`An MHS comprises a variety of interconnected functional entities. Message transfer agents (MTAS)
`cooperate to perform the store~and-forward message transfer function. Message stores {MSs) provide storage for
`messages and enable their submission, retrieval and management. User agents (UAs) help users access MHS.
`Access units (AUs) provide links to other communication systems and services of various kinds (e.g. other
`telematic services, postal services).
`
`This Recommendation specifies the overall system and service description of message handling capabilities.
`
`1
`
`Scope
`
`This Recommendation defines the overall system and service of an MHS and serves as a general overview
`of MHS.
`
`Other aspects of message handling systems and services are defined in other Recommendations. The layout
`of Recommendations defining the message handling system and services is shown in Table l/F.400. The public
`services built on MHS, as well as access to and from the MHS for public services are defined in the PAW-Series
`of Recommendations.
`
`The technical aspects of MHS are defined in the X.400-Series of Recommendations. The overall system
`architecture of MHS is defined in Recommendation X402.
`
`8
`
`Fascicle 11.6 — Rec. E400
`
`"'Page100f79
`
`Page 10 of 79
`
`

`

`TABLE 1/F.4OD
`
`Structure of MHS Recommendations
`
`
`
`Name of Recommendation/Standard
`'
`
`—l
`
`Joint MHS
`
`
`
`Joint support
`
`CCIT'ii only
`
`com"
`
`ISO
`
`CCITT
`
`150
`
`System
`
`Service
`
`XAGU
`
`X402
`
`10021-1
`
`10021-2
`
`XAO?
`
`100216
`
`X.411
`
`10021-4
`
`X413
`
`X3119
`K420
`
`10021-5
`
`10021-6
`10021—7
`
`MHS: System and service overview
`
`MHS: Overall architecture
`
`MHS: Conformance testing
`MHS: Abstract service definition
`conventions
`
`MHS: Encoded information type
`conversion rules
`
`MHS: MTS: Abstract service definition
`and procedures
`MHS: MS: Abstract service definition
`
`MHS: Protocol specifications
`MHS:
`Interpersonal messaging system
`Telematic access to IPMS
`
`MHS: Naming and addressing for public
`MH services
`
`MHS: The public message transfer service
`MHS:
`Intercommunication with public
`physical deliver),' services
`MHS: The public 1PM service
`MHS:
`Intercomrnunication between 1PM
`service and telex
`
`MHS:
`
`Intercommunication between {PM
`service and teletex
`
`1—051:
`051:
`
`OSI:
`
`Basic reference model
`Specification of abstract syntax
`notation one (ASN.1)
`
`Specification of basic encoding
`rules for abstract syntax notation
`one (ASN.1)
`
`OSI: Association control: service
`definition
`
`05]:
`
`0312:
`
`Reliable transfer: model and service
`definition
`
`Remote operations: model, notation
`and service definition
`
`DSI: Association control: protoco}
`specification
`
`051:
`
`Reliable transfer: protocol
`specification
`
`x403
`
`X403
`
`T330
`
`1— F400
`
`R401
`
`17.410
`F.415
`
`E420
`17.421
`
`R422
`
`X5100
`X208
`
`X3109
`
`7498
`8824
`
`8825
`
`X21?
`
`8649
`
`X218
`
`9066-1
`
`X219
`
`X227
`
`901124
`,
`
`8650
`
`X228
`
`90664
`
`
`
`
`
`
`
`
`
`
`
`
`OS]:
`
`Rcmote operations: protocol
`L
`specification
`
`
`X.229
`
`9012-2
`
`Fascicle [1.6 - Rec. E4013
`
`9
`
`Page11 of79
`
`Page 11 of 79
`
`

`

`2
`
`References
`
`This Recommendation cites the documents listed below:
`
`Recommendation F.60
`
`Recommendation F269
`
`Operational provisions for the international telex service
`Plan for the telex destination codes
`
`4'
`
`Recommendation F.72
`
`International telex store-and-forward - General principles and operational aspects
`
`Recommendation F160
`
`General operational provisions for the international public fascimile services
`
`Recommendation F200
`
`Teletex service
`
`Recommendation F.300
`
`Videotex service
`
`Recommendation E400
`
`Recommendation E401
`
`Message handling —- System and service overview (see also ISO 10021-1)
`message handling
`
`Message handling services — Naming and addressing for public
`services
`
`Recommendation R410
`
`Recommendation F.415
`
`Message handling services — The public message transfer service
`Message handling services — Intercommunication with public physical delivery gervices
`
`Recommendation E420
`
`Recommendation E421
`
`Message handling services — The public interpersonal messaging service
`Message handling services — Intercommunication between the IPM service and the
`telex service
`
`Recommendation R422
`
`Message handling services — lntercommunieation between the IPM service and the
`teletex service
`
`Recommendation 'I'.61
`
`Character repertoire and coded character sets for the international teletex service
`
`Recommendation T330
`
`Recommendation U30
`
`Recommendation U204
`
`Recommendation X200
`
`Telematic access to IPMS
`International teletex store-and-forward —- Access from telex
`lnterworking between the telex service and the public interpersonal messaging service
`Reference model of open systems interconnection for CCITT applications (see also
`ISO 7498)
`
`Recommendation X208
`
`Recommendation X.209
`
`Specification of abstract syntax notation one (ASN.1) (see also ISO 8824)
`Specification of basic encoding rules for abstract syntax notation one (ASN.1) (see also
`ISO 8825)
`
`Recommendation X217
`
`Association control: Service definitions (see also ISO 8649)
`
`Recommendation X218
`
`Reliable transfer model: Service definition {see also ISO/IEC 9066-1)
`
`Recommendation X219
`
`Recommendation X400
`
`Recommendation X402
`
`Remote operations model: Notation and service definition (see also ISO/[EC 9072-1)
`Message handling — System and service overview (see also ISO/IEC 10021-1) -
`Message handling systems — Overall architecture (see also ISO/[EC 10021-2)
`
`Recommendation X3303
`
`Recommendation X1107
`
`Message handling systems — Conformance testing
`Message handling systems - Abstract service definition conventions (see also 150/
`IEC 10021-3)
`
`Recommendation X403
`
`Recommendation X411
`
`Message handling systems - Encoded information type convention rules
`Message handling systems —— Message transfer system: Abstract service definition and
`procedures {see also lSO/IEC 10021-4)
`
`10
`
`Faseicle 11.6 - Rec. E400
`
`Page 12 of 79
`
`Page 12 of 79
`
`

`

`Recommendation X413
`
`Message handling systems — Message store: Abstract service definition (see also
`ISO/[EC 10021-5)
`
`Recommendation K419
`
`Recommendation X420
`
`Recommendation X500
`
`Recommendation X501
`
`Recommendation X509
`
`Recommendation X511
`
`Recommendation X518
`
`Recommendation X519
`
`Recommendation X520
`
`Recommendation X521
`
`3
`
`Definitions
`
`Message handling systems # Protocol specifications (see also ISO/’IEC 10021-6)
`Message handling systems — Interpersonal messaging system [see
`also 130/
`[BC 10021-7)
`Directory — Overview {see also ISO/{EC 9594-1)
`Directory — Models (see also ISO/IBC 9594—2)
`
`i“
`
`Directory —- Authentication (see also ISO/’IEC 9594-8)
`Directory — Abstract service definition (see also ISO/{EC 9594-3)
`Directory — Procedures for distributed operations (see also ISO/IEC 9594-4)
`Directory - Protocol specifications (see also ISO/[EC 9594—5)
`Directory h Selected attribute types (see also ISO/IEC 959445)
`Directory - Selected object classes (see also ISO/IEC 9594-7)
`
`This Recommendation uses the terms listed below, and those defined in Annex A.
`Definitions of the elements of service applicable to MHS are contained in Annex B.
`
`3.1
`
`Open systems interconnection
`
`This Recommendation uses the following terms defined in Recommendation X200:
`a) Application layer;
`b) Application—process;
`c) Open systems interconnection;
`d)
`031 reference model.
`
`3.2
`
`Directory systems
`
`This Recommendation uses the following terms defined in Recommendation X500:
`:1)
`directory entry;
`13)
`directory system agent;
`c)
`directory system;
`(1)
`directory user agent.
`This Recommendation uses the following terms defined in Recommendation X501:
`e)
`attribute;
`8
`group;
`g) member;
`11)
`name.
`
`4
`
`Abbreviations
`
`A
`
`ADMD
`
`AU
`
`CA
`
`DL
`
`DSA
`
`DUA
`
`Additional
`
`Administration management domain
`Access unit
`
`Contractual agreement
`
`Distribution list
`
`Directory system agent
`
`Directory user agent
`
`Fascicle 11.6 - Rec. E400
`
`ll
`
`Page 13 of 79
`
`Page 13 of 79
`
`

`

`EIT
`
`1/0
`
`IP
`
`1PM
`
`IPMS
`
`M D
`
`MH
`
`MHS
`
`MS
`
`MT
`
`MTA
`
`MTS
`
`N/A
`
`0/ R
`
`081
`
`PD
`
`PDAU
`
`PDS
`
`PM
`
`PR
`
`PRMD
`
`Essential
`
`Encoded information type
`
`lnput/ output
`
`Interpersonal
`
`Interpersonal messaging
`
`Interpersonal messaging system
`
`Management domain
`
`Message handling
`
`Message handling system
`
`Message store
`
`Message transfer
`
`Message transfer agent
`
`Message transfer system
`
`Not applicable
`
`Originator/ recipient
`
`Open system interconnection
`
`Physical delivery
`
`Physical delivery access unit
`
`Physical delivery system ‘
`Per-message
`
`Per-recipient
`
`Private management domain
`
`PTLXAU
`
`Public telex access unit
`
`TLMA
`
`TLX AU
`
`'I'TX
`
`UA
`
`Telematic agent
`
`Telex access unit
`
`Teletcx
`
`User agent
`
`5
`
`Conventions
`
`“Administration" is used for shortness to indicate a telecommuni-
`In this Recommendation the expression
`and, in the case of intercommunication with public
`cation Administration, a recognized private operating agency,
`delivery service, a postal Administration.
`is identical to Recommendation X400. Because of the desired alignment
`Note — This Recommendation
`dopted for the structure of this text. These conventions
`with ISO, the conventions of ISO standards have been a
`4UD-Series are in accordance with CCIT’I‘
`differ from the CCITT style. The other Recommendations of the F.
`conventions.
`
`l2
`
`Fascicle 11.6 _ Rec. F.4{Ifl
`
`Page 14 of 79
`
`Page 14 of 79
`
`

`

`PART 2 7 GENERAL DESCRIPTION OF MHS
`
`6
`
`Purpose
`
`This Recommendation is one of a set of Recommendations and describes the system model and elements
`of service of the message handling system (MHS) and services. This Recommendation overviews the capabilities of
`an MHS that are used by Administrations for the provision of public MH services to enable users to exchange
`messages on a store—and—forward basis.
`
`The message handling system is designed in accordance with the principles of the reference model of open
`systems interconnection (OSI reference model) for CCI'I'I' applications (Recommendation X200) and uses the
`presentation layer services and services offered by other, more general, application service elements. An MHS can
`be constructed using any network fitting in the scope of 051. The message transfer service provided by the MTS is
`application independent. An example of a standardized appiication is the [PM service. End systems can use the
`MT service for specific applications that are defined bilaterally.
`
`Message handling services provided by Administrations belong to the group of telematic services defined
`in F-Series Recommendations.
`
`telematic services and telex (Recommendations F.60, F160, E200, E300, etc.), data
`Various other
`transmission services (X1), or physical delivery services (E415) gain access to, and intercommunicate with, the
`[PM service or intercommunioate with each other, via access units.
`
`Elements of service are the service features provided through the application processes. The elements of
`service are considered to be components of the services provided to users and are either elements of a basic
`service or they are optional user facilities, classified either as essential optional user facilities, or as additional
`optional user facilities.
`
`7
`
`Functional model of MHS
`
`The MHS functional model serves as a tool to aid in the development of Recommendations for MHS, and
`aids in describing the basic concepts that can be depicted graphically. It comprises several different functional
`components that work together to provide MH services. The model can be appiied to a number of different
`physical and organizational configurations.
`
`7.1
`
`Description of the MHS model
`
`A functional view of the MHS model is shown in Figure l/F.400. In this model, a user is either a person
`or a computer process. Users are either direct users (i.e. engage in meSSage handling by direct use of MHS), or are
`indirect users (Le. engage in message handling through another communication system (eg. a physical delivery
`system) that is linked to MHS). A user is referred to as either an originator (when sending a message) or a
`recipient (when receiving a message). Message handling elements of service define the set of message types and the
`capabilities that enable an originator to transfer messages of those types to one or more recipients.
`
`An originator prepares messages with the assistance of his user agent. A user agent (UA) is an application
`process that interacts with the message transfer system (MTS) or a message store (MS), to submit messages on
`behalf of a single user. The MTS delivers the messages submitted to it, to one or more recipient UAs, access units
`(AUs), or MSs, and can return notifications to the originator. Functions performed soiely by the UA and not
`standardized as part of the message handling elements of service are called local functions. A UA can accept
`delivery of messages directly from the MTS, or it can use the capabilities of an MS to receive delivered messages
`for subsequent retrieval by the UA.
`
`The M'I‘S comprises a number of message transfer agents (MTAs). Operating together,
`forward manner, the MTAs transfer messages and deliver them to the intended recipients.
`
`in a store-anci-
`
`Access by indirect users of MHS is accomplished by AUs. Delivery to indirect users of MHS is
`accomplished by AUs, such as in the case of physical delivery, by the physical delivery access unit (PDAU).
`
`The message store (MS) is an optionai generai purpose capability of MHS that acts as an intermediary
`between the UA and the MTA. The MS is depicted in the MHS functional model shown in Figure 1/F.400. The
`MS is a functional entity whose primary purpose is to store and permit retrieval of delivered messages. The MS
`also allows for submission from, and alerting to the UA.
`
`The collection of EMS, MSs, AUs and MTAs is called the message handling system (MHS).
`
`Fasciele 11.6 — Ree. E400
`
`13
`
`Page 15 of 79
`
`Page 15 of 79
`
`

`

`
`
`Note 4 Messag
`notifications.
`
`0 input from PD Services to MHS is for further study. Flow from ?D
`
`Services to the PDAU shown is for
`
`FIGURE U F401]
`
`MHS functional model
`
`.
`
`7.2
`
`Stmcrm'e of messages
`The basic structure of messages conveyed by the MTS is shown in Figure 2/F.400. A message is made up
`of an envelope and a content. The envelope carries information that is used by the MTS when transferring the
`message within the MTS. The content is the piece of information that the originating UA wishes delivered to one
`or more recipient UAs. The MTS neither modifies or examines the content, except 1‘or conversion (see § 16).
`
`+
`
`Content
`
`Envelope
`
`CCI‘IT — 0100 530- 83
`
`FIGURE. 21132400
`
`Basie message structure
`
`14
`
`Fascic‘le [1.6 — Rec. E400
`
`Page 16 of 79
`
`Page 16 of 79
`
`

`

`7.3
`
`Application of the MHS modei
`
`7.3.1
`
`Physieai mapping
`
`Users access UAs for message processing purposes, for example, to create, present, or file messages. A user
`can interact with a UA via an input/output device or process (e.g. keyboard, display, printer, etc). ALL-UA can be
`implemented as a (set of) computer process(es) in an intelligent terminal.
`
`A UA and MTA can be (lo—located in the same system, or a UA/MS can be implemented in physically
`separate systems. In the first case the UA accesses the MT elements of service by interacting directly with the
`MTA in the same system. In the second case, the UA/MS will communicate with the MTA via' standardized
`protocols specified for MHS. It is also possible for an MTA to be implemented in a system without UAs or MSs.
`
`Some possible physical configurations are shown in Figures 3/F.4{}0 and 4/F.40t]. The different physical
`systems can be connected by means of dedicated lines or switched network connections.
`
`
`
`
` IID device
`
`IIO device
`
`CCJTT — (”00590
`
`‘1'?
`
`Processing system
`FIGURE 3 f E400
`
`(Io-resident Lin and [WM
`
`
`IIO device l
`
`I
`
`l
`l
`
`ccn‘r — 0100600-89
`
`.
`terminal
`"Intelllgent"
`
`.
`I
`
`,
`
`_
`.
`___
`Processing system
`
`_J
`
`l
`
`-
`_
`-
`Processing system
`
`FIGURE 4! 1-2400
`
`Stand—alone DA and era-resident MSIMTA and USIMTA
`
`7.3.2
`
`Organizational mapping
`
`An Administration or organization can play various roles in providing message handling services. An
`organization in this context can be a company or a non-commercial enterprise.
`
`least one MTA, zero or more UAS, zero or more MSs, and zero or more AUs
`The collection of at
`operated by an Administration or organization constitutes a management domain (MD). An MD managed by an
`Administration is called an Administration management domain (ADMD). An MD managed by an organization
`other than an Administration is called a private management domain (PRMD). An MD provides message
`handling services
`in accordance with the classification of elements of service as described in §19. The
`relationships betwoen management domains is shown in Figure 5/ R400.
`
`Faseicle 11.6 — Ree. E400
`
`15
`
`Page 17 of 79
`
`Page 17 of 79
`
`

`

`
`
` CCITT - 0100321 -85
`
`Country B
`
`FIGURE 5 I [-1400
`
`Relationships between management domains
`
`Note 1 — It shouid be recognized that the provision of support of private messaging systems by CCI'IT
`members falls within the framework of national regulations. Thus the possibilities mentioned in this paragraph
`may or may not be offered by an Administration which provides message handling services. In addition, the UAs
`depicted in Figure S/F.400 do not imply that UAs belonging to an MD must be exclusively located in the same
`country as their MDs.
`Note 2 _ Direct interactions between PRMDs and internal interactions within an MD are outside the
`scope of this Recommendation.
`Note 3 — An Administration, in the context of CCITT, that manages an ADMD, is understood as being
`a member of ITU or a recognized private operating agency (RPOA), registered by a country with the ITU.
`
`7.3.3 Administration management domain
`
`In one country one or more ADMDs can exist. An ADMD is characterized by its provision of relaying
`functions between other management domains and the provision of message transfer service for the applications
`provided within the ADMD.
`An Administration can provide access for its users to the ADMD in one or more of the following ways:
`— users to Administration provided UA
`
`- private UA to Administration MTA
`r
`private UA to Administration'MS
`— private UA to Administration MTA
`_ user to Administration provided UA.
`
`See also the examples of configurations shown in Figure 3/E400 and Figure 4/F.400.
`
`l6
`
`Fascicle 11.6 — Ree. F.40l]
`
`Page 18 of 79
`
`Page 18 of 79
`
`

`

`Administration provided UAs can exist as part of an intelligent terminal that the user can use to access
`MHS. They can also exist as part of Administration resident equipment being part of MHS, in which case the user
`obtains access to the UA via an [/0 device.
`
`In the case of a private UA, the user has a private stand-alone UA which interacts with the Administration
`provided MTA or MS, using submission, delivery and retrieval functions. A private, stand—alone UA can be
`associated with one or more MDs, provided that the required naming conventions are preserved.
`3,.
`
`A private MTA as part of an P—RMD can access one or more ADMDs in a country, following national
`regulations
`
`Access can also be provided by Administration provided AUs described in §§ 10 and 11.
`
`7.3.4
`
`Private management domain
`
`An organization other than an Admin