ISO/IEC 10021-8:1995

Information technology - Message Handling Systems (MHS) - Part 8: Electronic Data Interchange Messaging Service

Technologies de l'information — Systèmes de messagerie (MHS) — Partie 8: Service de messagerie avec échange de données informatisé

General Information

• Status: Withdrawn
• Publication Date: 26-Jul-1995
• Withdrawal Date: 26-Jul-1995
• ICS: 35.240.20 - IT applications in office work
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 17-Oct-2000
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 13433:2006 - Geosynthetics - Dynamic perforation test (cone drop test)
• Effective Date: 06-Jun-2022
• Revised: ISO/IEC 10021-8:1999 - Information technology - Message Handling Systems (MHS) - Part 8: Electronic Data Interchange Messaging Service
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISOJIEC
10021-8
STANDARD
First edition
1995-08-01
Information technology - Message
Handling Systems (MHS) -
Part 8:
Electronic Data Interchange Messaging
Service
Technologies de I’informa bon’ - Systkmes de messagerie (MHS) -
Partie 8: Service de messagerie avec &change de don&es in format;&
Reference number
GO/l EC 10021-8: 1995(E)
ISO/IEC 10021-S : 1995 (E)
Page
Contents
iv
...............................................................................................................
Foreword
V
............................................................................................................
Introduction
..............................................................................................................
1 Scope
2 Normative references .
.......................................................................................................
3 Definitions
...............................................
3.1 Terms defined in this part of ISO/IEC 10021
............................................................................................
3.1.1 ED1 forwarding
................................................................................................
3.1.2 ED1 message
.....................................................................................
3.1.3 ED1 messaging user
...........................................................................................
3.1.4 ED1 notification
..........................................................................
3.1.5 ED1 message responsibility
3 -
............................................................
3.2 Terms imported from ISO/IEC 9735
..................................................................
3.3 Terms imported from ANSI X 12
4 Abbreviations .
....................................................................................................
5 Conventions
6 ED1 messaging service .
6.1 Introduction .
.............................................................................................
6.2 ED1 messaging
........................................................................
6.3 ED1 messaging environment
.....................................................................................
6.4 ED1 messaging user
.....................................................................................
7 ED1 messaging system
.................................................................................................
7.1 Introduction
...................................................................
7.2 Information flow in the EDIMS
......................................................
7.3 ED1 messaging service functional model
...........................................................................
7.4 Structure of ED1 messages
.........................................................................................
7.5 ED1 notification
..............................................................
8 EDIM responsibility and forwarding
...............................................................................................
8.1 Introduction
.......................................................
8.2 Forwcvding and secondary distribution
...............................................................................
8.3 Case 1: No forwarding
............
8.4 Case 2: Content not changed and EDIM responsibility forwarded.
................................................
8.5 Case 3: EDIM responsibility not forwarded
.................................................
9 ED1 maming, addressing and use of directory
..................................................................................................
10 ED1 security
......................................
11 Intercommunication with physical delivery services
...............................................................................................
11.1 Introduction
..........................................................................
11.2 Delivery and notifications
.................................................................
11.3 Tmnsfer of EDIM responsibility
......................................................................................
11.4 Physical rendition
........................................................................
12 Use of message store for ED1
13 Elements of service .
..............................................................
14 Classification of elements of service
.....................................................................
14.1 Basic ED1 messaging service
............................................
14.2 ED1 messaging service optional user facilities
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized
electronic or mechanical, including photocopying and microfilm, without
in any form or by any means,
permission in writing from the publisher.
l W-121 1 Geneve 20 l Switzerland
ISO/IEC Copyright Office l Case postale 56
Printed in Switzerland
ISO/IEC 10021-8 : 1995 (E)
0 ISO/IEC
Quality of service . 25
..................................................................................... 25
15.1 ED1 message status
service . 25
15.2 Support by providers of ED1
..................................................... 25
15.3 Model of delivery and notification times
.............................................................. 26
15.4 ED1 message delivery time targets
....................................................................... 27
15.5 ED1 notification time targets
15.6 Error protection .
15.7 Availability of service .
ANNEXES
A- Glossary of terms .
B - Definitions of elements of service .
C - Security overview .
................................................ 45
D - ED1 naming, addressing, and use of directory
E - Cross referencing overview .
TABLES
1 -Case 1: No forwarding .
2 - Case 2: EDIM responsibility forwarded .
3 - Case 3: EDIM responsibility not forwarded .
..................
4 - Provision and use of secure messaging elements of service by MHS
components . 18
.21
5 - Elements of service belonging to the basic ED1 messaging service .
6 - ED1 messaging optional user facilities selectable on a per-message basis. . .2 3
7 - ED1 messaging service optional user facilities agreed for a contractual period of
time .
8 - EDIN time targets .
FIGURES
1 - ED1 messaging environment . 6 ,
...................................................................................... 7
2 - ED1 messaging system
3 - Information flow in ED1 messaging system . 8
............................................................
4 - ED1 messaging service functional mode
....................................................................................
5 - ED1 message structure
.......................................
6 - ED1 message structure for a typical ED1 transaction
....................................................................................
7 -Case 1: No forwarding
..........................................................
8 - Case 2: EDIM responsibility forwarded
.........................................
9 - Case 3: EDIM responsibility not forwarded, Part 1
...................................................
10 - Case 3: EDIM responsibility not forwarded
.................................................
11 - M/PD delivery and notification times model
................................................................................
12 - Notification time model
......................................................................
C- 1 - EDIM Responsibility transfer
.............................................................
D-l - DIT structure for ED1 requirements
example .
D-2 - An aliasing
...........................................................
D-3 - A country oriented aliasing example
............................................................
E-l - Cross referencing in ED1 messaging
. . .
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for worldwide
standardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity.
IS0 and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with
IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the
joint technical committee are circulated to national bodies for voting. Publication
as an International Standard requires approval by at least 75 96 of the national
bodies casting a vote.
International Standard ISO/IEC 10021-8 was prepared by ITU-T (as ITU-T
Recommendation F.435) and was adopted, under a special “fast-track procedure”,
by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel
with its approval by national bodies of IS0 and IEC.
ISO/IEC 10021 consists of the following parts, under the general title Information
technology - Message Handling Systems (MHS):
Part I: System and Service Overview
- Part 2: Overall Architecture
- Part 3: Abstract Service Definition Conventions
- Part 4: Message Transfer System: Abstract Service Definition and
Procedures
- Part 5: Message Store: Abstract Service Definition
- Part 6: Protocol Specification
- Part 7: Interpersonal Messaging System
- Part 8: Electronic Data Interchange Messaging Service
Part 9: Electronic Data Interchange Messaging System
Annexes A and B form an integral part of this part of ISO/IEC 10021. Annexes C,
D and E are for information only.
iv
0 ISO/IEC
ISO/IEC10021-8:1995(E)
Introduction
This part of ISO/IEC 10021 is one of a number of parts of ISO/IEC 1002P
(Information technology - Message Handling Systems (MI-IS)).
Message handling systems and services enables users to exchange of 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 other users, the message’s recipients. A user may interact directly with the
MT’S, or indirectly via a message store (MS).
The MTS comprises a variety of interconnected functional entities called
message transfer agents (MTAs). MTAs cooperate to transfer messages and deliver
them to their intended recipients. 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 part of ISO/IEC 10021 was initially developed and published by the ITU-T in
1991. The ITU-T version is published as CCITT Recommendation F.435 (1991) as
amended by the MHS Implementor’s Guide (version 12).
This part of ISO/IEC 10021 defines the overall system and service description of
the message handling application called ED1 Messaging.
ISO/IEC NOTE
As stated in the ITU-T version of this part of ISO/IEC 10021 [i.e., F.435 (1991)],
“Administration” is used for conciseness to indicate both a
the expression
telecommunication Administration and a recognized private operating agency.

This page intentionally left blank

INTERNATIONAL STANDARD O1somc
ISO/IEC 1002143 : 1995 (E)
Information technology - Message Handling
Systems (MHS) -
Part 8 :
Electronic Data Interchange Messaging Service
1 Scope
This part of ISO/IEC 10021 defines the overall system and service of ED1 messaging.
Other aspects of message handling systems and services are defined in other parts of ISO/IEC 10021. The layout of
Standards I Recommendations defining the message handling system and services is shown in table 1 of ISO/IEC
10021-l I CCITT Recommendation X/F.400. The public services built on MHS, as well as access to and from the
MHS for public services are defined in the ITU-T’s F.400-Series of Recommendations.
The technical aspects of MHS are defined in the multi-part series numbered ISO/IEC 10021 and ITU-T’s X.400-Series
of Recommendations. The overall system architecture of MHS is defined in ISO/IEC 10021-2 I CCITT
Recommendation X.402. The technical aspects of ED1 messaging are defined in ISO/IEC 10021-9 I CCITT
Recommendation X.435.
Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part of
ISO/IEC 10021. At the time of publication, the editions indicated were valid. AI1 standards are subject to revision, and
parties to agreements based on this part of ISO/IEC 10021 are encouraged to investigate the possibility of applying the 9
most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid
International Standards.
ISO/IEC 9594-2:1990, Information technology - Open Systems Interconnection - The Directory -Part 2: Models.
(See also CCITT Recommendation X.501 (1988))
Open Systems Interconnection - The Directory - Part 7: Selected
ISO/IEC 9594-7: 1990, Information technology -
object classes.
(See also CCITT Recommendation X.521 (1988))
ISO/IEC 9594-8: 1990, Information technology - Open Systems Interconnection - The Directory - Part 8:
Authentication framework.
(See also CCITT Recommendation X.509 (1988))
IS0 9735: 1988, Electronic data interchange for administration, commerce and transport (EDIFACT) - Application
level syntax rules.
ISO/IEC 10021-l: 1990, Information technology - Text Communication - Message-Oriented Text Interchange Systems
(MOTIS) - Part 1: System and Service Overview.
(See also CCITT Recommendation F.400 (1992) I X.400 (1993))
- Message-Oriented Text Interchange Systems
ISO/IEC 10021-2: 1990, Information technology - Text Communication
(MOTIS) - Part 2: Overall Architecture.
(See also CCITT Recommendation X.402 (1992))

ISO/IEC 10021-S : 1995 (E)
0 ISO/IEC
ISO/IEC 10021-5: 1994, Information technology - Text Communication - Message-Oriented Text Interchange Systems
(MOTIS) - Part 5: Message Store: Abstract Service Definition.
(See also CCITT Recommendation X.4 13 (1992))
ISO/IEC 10021-7: 1990, Information technology - Text Communication
- Message-Oriented Text Interchange Systems
(MOTIS) - Part 7: Interpersonal Messaging System.
(See also CCITT Recommendation X.420 (1992))
ISO/IEC 10021-9: 1995, Information technology - Message Handling Systems (MHS) - Part 9: Electronic Data
Interchange Messaging System.
(See also CCITT Recommendation X.435 (1991))
CCITT Recommendation F.401 (1992), Message handling services: Naming and addressing for public message
handling services.
CCITT Recommendation F.415 (1992), Message handling services: Intercommunication with public physical delivery
servtces.
Definitions
For the purposes of this part of ISO/IEC 10021, the following definitions, and those defined in annex A apply.
Definitions of the elements of service applicable to ED1 messaging are contained in annex B of this part of
ISO/IEC 10021. The elements of service applicable to the Message Transfer service, and used by ED1 messaging, are
called out in this part of ISO/IEC 10021, however their definitions are contained in ISO/IEC 10021-l I CCITT
Recommendation F.400, annex B.
31 . Terms defined in this part of ISOlIEC 10021
3.1.1 ED1 forwarding: Onward transfer of a received EDIM to one or more recipients determined by the
forwarding ED1 user agent/message store.
ED1 forwarding takes place when an ED1 message having been delivered to an ED1 user agent or ED1 message store is
forwarded onward to another ED1 user agent or EDI message store.
ED1 message: Information in electronic form that is transferred between ED1 messaging users. An EDI
3.1.2
message is a member of the primary class of information objects conveyed between ED1 messaging users.
See also ISO/IEC 10021-9 I CCITT Recommendation X.435 clause 8.
ED1 messaging user: User that engages in ED1 messaging. An ED1 messaging user originates, receives, or
3.1.3
both originates and receives ED1 messages. The ED1 messaging environment contains any number of ED1 messaging
users. An ED1 messaging user may be a person or a computer process. An ED1 messaging user may access the ED1
messaging system through an access unit.
3.1.4 ED1 notification: Member of the secondary class of information objects that indicates to the originator of an
ED1 message the disposition of EDIM responsibility for the ED1 message.
ED1 message responsibility: ED1 message responsibility indicates whether the subject ED1 message has
3.1.5
been made available to a specific user by its ED1 user agent/message store. ED1 message responsibility carries no legal
significance within this part of ISO/IEC 10021 and ISO/IEC 10021-9 I CCITT Recommendation X.435.
ISO/IEC 10021-8 : 1995 (E)
0 rso/IEc
Terms imported from IS0 9735
32 .
l
Acknowledgment request
l Application reference
l Communication agreement ID
Date/time of preparation
Functional group header
l
l Interchage control reference
Interchange header
Interchange recipient
Interchange sender
Message header
l Processing priority code
l Recipients reference, password
l Service string advice
l Syntax identifier
Test indicator
. UNA
l UN-B
l UNG
l UN-H
l UNT
l UNZ
NOTE - These terms are further expanded in annex A of this part of ISO/IEC 10021 and annex K of ISO/IEC 10021-9 I CCITT
Recommendation X.435.
Terms imported from ANSI Xl2
Application reference
Date and Time of Transmission
GS
Interchange header
Functional group header
Transaction set header
ISA
IEA
Recipient;s transmission reference/password
ST
Transmission sender
0 ISO/lEC
ISODEC 10021-8 : 1995 (E)
Transmission recipient
Transmission priority code
NOTE - These terms are further expanded in annex A of this part of ISO/IEC 10021 and annex K of ISO/IEC 10021-9 I CCITT
Recommendation X.435.
Abbreviations
ANSI American National Standards Institute
AU Access unit
DIT Directory information tree
DL Distribution list
DUA Directory user agent
ED1 Electronic data interchange
EDIFACT Electronic data interchange for Administration, commerce and transport
EDIM ED1 message
EDIME ED1 messaging environment
EDIMG ED1 messaging
EDIMS ED1 messaging system
EDI-AU ED1 access unit
EDI-MS ED1 message store
EDI-UA ED1 user agent
EDIN ED1 notification
FN Forwarded notification
ID Identifier
IPM Interpersonal messaging
Management domain
Message handling
MHS Message handling system
Message store
MS
Message transfer
MTA Message transfer agent
MTS Message transfer system
NDN Non-delivery notification
Negative notification
Originator/Recipient
O/R
PD Physical delivery
PDAU Physical delivery access unit
Physical delivery system
PDS
PN Positive notification
Private management domain
PRMD
Telematic agent
TLMA
User agent
UA
United Nations, trade data interchange
UNTDI
Coordinated universal time
UTC
5 Conventions
In clause 2, CCITT aligned standards are cited.
Common language practices have been applied as far as possible in the use of capitalization of words.
0 ISO/lEC ISO/IEC 10021-8 : 1995 (E)
ED1 messaging service
61 . Introduction
The ED1 messaging service provides an ED1 messaging user with features to assist in communicating with other EDI
messaging users. ED1 messaging users are in many cases computer processes. The ED1 messaging service uses the
capabilities of the Message Transfer service (see also Recommendation F.410) for sending and receiving EDI
messages. The elements of service describing the features of the EDI messaging service are defined in annex B, and
classified in clause 14.
EDI, electronic data interchange, can be described as computer to computer exchange of structured business data, such
as invoices and purchase orders. In some cases the EDI messaging service can be used to transmit an ED1 interchange
to a physical rendition system, such as a physical delivery system, or facsimile.
The ED1 messaging service is provided by ED1 messaging.
62 . ED1 messaging
ED1 messaging (EDIMG) consists of the exchange of ED1 messages (EDIMs), and ED1 notifications (EDINs), which
are information objects specified in ISO/IEC 10021-9 I CCITT Recommendation X.435.
63 . ED1 messaging environment
The environment in which ED1 messaging takes place can be modelled as a functional object which is hereafter
referred to as the ED1 messaging environment (EDIME). When refined (i.e., functionally decomposed), the EDIME
can be seen to comprise lesser objects referred to as the primary objects of ED1 messaging. They include a single
central object, the ED1 messaging system (EDIMS), and numerous peripheral objects called ED1 messaging users
(EDIMG users).
The structure of the EDIME is depicted in figure 1.

ISO/IEC 10021-S : 1995 (E)
0 ISO/IEC
TO101260-93
Figure 1 - ED1 messaging environment
ED1 messaging user
64 .
An ED1 messaging user (EDIMG user) is a user that engages in ED1 messaging. An EDIMG user originates, receives,
or both originates and receives EDIMs. The EDIME contains any number of EDIMG users.
An EDIMG user may be a person or a computer process. An EDIMG user may access the EDIMS through an
access unit.
7 ED1 messaging system
7.1 Introduction
The ED1 messaging system (EDIMS) is the functional object by means of which all EDIMG users communicate with
one another in ED1 messaging.
The EDIMS can be modelled as comprising lesser functional objects which interact with one another These lesser
objects are referred to as the secondary objects of EDI messaging. They include a single, central object, the message
transfer system (MTS), and numerous peripheral objects of three kinds: EDI user agents (EDI-UAs), ED1 message
stores (EDI-MSs), and ED1 access units (EDI-AUs).
The structure of the EDIMS is depicted in figure 2. As shown in figure 2, EDI-UAs, EDI-MSs, and EDI-AUs are the
objects by which the EDIMS provides service to EDIMG users.
0 1s0/IEc ISO/IE@ 10021-S : 1995 (E)
EDI messaging system
TO101270-93
Figure 2 - ED1 messaging system
7.1.1 ED1 user agents
An ED1 user agent (EDI-UA) is a user agent tailored so as to better assist a single EDIMG user to engage in ED1
messaging. It helps that EDIMG user originate and receive messages containing EDIMs. The EDIMS contains any
number of EDI-UAs.
NOTE - An exact definition of the boundary between the EDI-UA and the EDIMG user is beyond the scope of this part of
ISO/IEC 10021.
7.1.2 ED1 message store
An ED1 message store (EDI-MS) is a message store tailored so as to better assist a single EDI-UA engage in ED1
messaging. It helps that EDI-UA submit, take delivery of, store, and retrieve messages containing EDIMs.
7.1.3 Message transfer system
In the present context the message transfer system (MTS) conveys EDIMs or ED1 notifications (EDINs) between EDI-
UAs, or between an EDI-UA and an access unit. The EDIMS contains a single MTS.
7.1.4 ED1 access units
An EDIMG user may have access to/from the EDIMS through an access unit (AU). One type of access unit is the
physical delivery access unit (PDAU). In EDIMG, the physical delivery access unit provides the ability to send
messages to EDIMG recipients through a physical delivery system (PDS). Other types of EDI-AUs (e.g., facsimile
access units) may be the subject of future standardization.
7.2 Information flow in the EDIMS
Figure 3 expands on figure 2 and shows the principal information flows in ED1 messaging.
NOTE - Figure 3 illustrates aspects of the ED1 encoded data exchanged in this model, not the actual details.

ISO/IEC 1002118 : 1995 (E)
@ ISO/IEC
EDMG user
(EDI application)
EDI messaging system
- Generates EDI heading and submit envelope from interchange
control info plus other info in EDI interchange (receiver ID maps
into X.400 O/R name)
- Places EDI heading + EDI interchange in submit envelope
and submits to MTS
- On delivery from MTS extracts EDI interchange and passes
to EDI application
EDIMG
+ user
TO1 01280-93
NOTES
1 - For abbreviations and acronyms see clause 4 and annex A of this part of ISO/IEC 10021.
2 - The structure of the information exchanged between the EDIMG user and the EDI-UA is not
defined by this part of ISO/IEC 10021. In addition to the ED1 interchange, the control information
may comprise information carried in the envelope, EDIM heading, interchange header, etc. The
control information could also be extracted from the ED1 interchange and/or form other sources.
Figure 3 - Information flow in ED1 messaging
73 . ED1 messaging service functional model
Figure 4 shows the functional model of the ED1 messaging service. The UAs used in the EDI messaging service
comprise a specific class of cooperating UAs. The optional PDAU allows EDIMG users to send messages to indirect
users outside of the ED1 messaging environment. The message stores used in the ED1 messaging service have specific
ED1 related functions and can optionally be used by EDIMG users to take delivery of messages on their behalf. The
telematic agent (TLMA) shown in figure 4 will allow access to telematic services and may be the subject of future
standardization.
0 ISO/IEC
ISO/IEC 10021-8 : 1995 (E)
Recipient
c3
T0101290-93
Figure 4 - ED1 messaging service functional model
74 . Structure of ED1 messages
The ED1 class of UAs create messages containing a content specific to the ED1 messaging service. The specific
content that is sent from one EDI-UA to another is a result of an originator, which is generally an application process,
composing and sending a message, called an ED1 message (EDIM). The EDIM carries the ED1 interchange and
optionally other information associated with the ED1 interchange. Only one ED1 interchange shall be present in an
EDIM. Every EDIM shall contain an ED1 interchange body part on origination of the EDIM. Any of the body parts
can subsequently be removed (wholly, not partially) when forwarding an EDIM, except a forwarded body part, which
cannot be removed. Body parts that are removed when forwarding are replaced with place holders to indicate what
type of body part was removed. The heading of an EDIM shall not be removed when forwarding an EDIM. The
structure of an EDIM as it relates to the basic message structure of MHS is shown in figure 5. The EDIM is conveyed
with an envelope when being transferred through the MTS.

ISO/IEC 10021-8 : 1995 (E) 0 ISO/IEC
Basic message
structure
E
D
.
I
. . ‘Bbdy.
_.
.
.&;$g-f-J
. .
*,.
_.
.*.
:
....&c~~~j:...
:
. .
.... .- - - - - - - -
T0101300-93
Figure 5 - ED1 message structure
EDIFACT
interchange
<
\
UNA
\
\
\
I UNB I
\
\
I UNH I Field 3
Heading
User
data
*.
.
Field n
\
segments
UNT
I I
UNZ
I I
Body
Additional
information
(e.g. drawings)
T0101310-93
Figure 6 - ED1 message structure for a typical ED1 transaction
Figure 6 shows a mapping between a typical ED1 interchange, and the corresponding ED1 message structure. The ED1
interchange is mapped entirely within one body part, called the primary body part, and may be an EDIFACT, ANSI
X12, UNTDI or privately defined ED1 interchange. Other body parts are available to convey information associated
0 ISO/IEC ISO/IEC 10021-8 : 1995 (E)
with the ED1 interchange such as drawings, explanatory text, etc. The heading of the EDIM contains various fields of
information, some of which are present in the EDIFACT interchange header segments (or corresponding ISA or STX
segments for ANSI Xl2 and UNTDI), and others containing service requests from the originator. The heading and
body part(s) form the EDIM.
75 . ED1 notification
An EDIMG user can request that a recipient return an ED1 notification (EDIN) indicating the disposition of the ED1
message received. This notification is requested by an originating EDI-UA, and is generated by a recipient EDI-UA,
EDI-MS, or AU. There are three possible conditions that can be requested and reported on, resulting in either the
generation of a positive notification (PN), a negative notification (NN), or a forwarded notification (FN). The implied
meanings of the responses PN, NN, and FN are described in 8.1. It is possible to forward a received ED1 message
unchanged and forward the obligation to respond to the notification request to the recipient to whom the ED1 message
is forwarded, or intermediate recipients, who then shall respond to the original originator of the message. An
originating EDI-UA may request to be notified if the obligation to respond to the notification request has been
forwarded. In this case, the EDI-UA or EDI-MS that forwards the EDIM shall send to the originating EDI-UA an ED1
forwarded notification (FN).
In all cases, including notifications sent by EDI-UAs to whom the EDIM has been forwarded, the notifications shall
contain the OR-name of the recipient that was specified by the original originator.
The originating EDI-UA request any combination of the several EDINs from any combination of the recipients to
may
whom the EDIM is sent. If no notifications are requested by an originator, none shall be sent by the recipient(s).
ED1 notifications cannot be forwarded, and ED1 notifications cannot be requested for EDINs.
8 EDIM responsibility and forwarding
81 . Introduction
The EDIMS includes a concept called EDIM responsibility. This concept is key to the description below of EDINs and
forwarding. In order to simplify the descriptions in the text below, all forwarding is shown as performed by the EDI-
UA. It should be noted that the descriptions apply equally to forwarding performed by the EDI-MS.
a
The purpose for introducing the concept of EDIM responsibility is primarily to provide a method for confirming the
passing of messages amongst EDI-UAs. EDIM responsibility may apply to access units in certain cases. The concept
of EDIM responsibility is described as follows.
EDIM responsibility indicates that the EDIM is made available to the EDIMG user by the receiving EDI-UA.
EDIM responsibility shall always be accepted when the EDI-UA adds or removes body parts when forwarding. An
EDIM cannot leave the EDIMS unless EDIM responsibility has been accepted (delivery to a PDAU is a special case as
described in 11.3). If requested to do so by the originating EDI-UA, the recipient EDI-UA, and possibly intermediate
EDI-UAs (if requested), shah send EDINs to the originating EDI-UA.
When an EDI-UA receives an EDIM it shall, if requested to do so, inform the originating EDI-UA that the recipient
EDI-UA has accepted or refused EDIM responsibility by sending an appropriate EDIN. Subclause 8.2 below contains a
detailed description of the EDINs that are sent in various scenarios.
If notifications are requested, then when an EDI-UA accepts, refuses, or forwards EDIM responsibility, it shall send an
appropriate EDIN to the originator, and if forwarding, it shall create the appropriate heading fields in the forwarded
EDIM. The details of these operations are described in ISO/IEC 10021-9 I CCITT Recommendation X.435.
Body parts that are forwarded cannot be changed in any way. If EDIM responsibility is forwarded, the forwarded
EDIM cannot be changed in any way. If EDIM responsibility is accepted, body parts may be removed from, or added
to the original EDIM when creating the forwarded EDIM. Body parts that are removed when forwarding are replaced
with place holders to indicate what type of body part was removed. EDIM responsibility forwarding is limited to only
one recipient.
EDIMG includes mechanisms to prevent looping when forwarding.
ISO/IEC 1002143 : 1995 (E) 0 ISO/lEC
82 . Forwarding and secondary distribution
In EDIMG it may be desirable to receive ED1 messages at a central ED1 user agent, with subsequent forwarding to the
fmal ED1 user agents. Such a practice would, for example, enable a large organization to perform centralized functions
such as logging, auditing, etc., on all ED1 message traffic entering that organization. After performance of these
functions the traffic would be distributed to the EDI user agents serving the recipient EDI applications. Similarly, a
value added network service provider might operate a similar intermediary stage on behalf of its customers. The
following text describes the use of an EDI-UA as such an intermediary stage.
Since an intermediate EDI-UA will generally not be the final EDI-UA, there is a need to provide end-to-end
confirmation of EDIM responsibility acceptance for an EDIM within EDIMG. The element of service
“ED1 notification request” allows an originator to request from each recipient, positive, negative and forwarded
notifications. Together with protocol elements defined in ISO/IEC 10021-9 I CCITT Recommendation X.435, the
allows intermediate EDI-UAs to indicate, in a forwarded message, whether or not
“ED1 notification request”
EDIM responsibility has been accepted. These tools allow EDIM responsibility acceptance to be deferred until an
EDIM reaches the final EDI-UA, and provide an indication to that EDI-UA that a notification is to be returned to the
original originator.
In order to illustrate the use of an EDI-UA as an intermediate stage, three cases are described below. In all cases, an
EDIM originates in EDI-UAl and terminates in EDI-UA3. EDI-UA2 is the intermediate EDI-UA. In cases 1 and 2 it is
assumed that the EDIM is forwarded with content unchanged. In all three cases it is assumed that EDI-UAl has
requested notifications.
NOTE - Events described in the following tables are not necessarily performed in the exact sequential order shown in the
83 . Case 1: No forwarding
The EDIM prepared by EDI-UAl is addressed to EDI-UA3. The EDIM is submitted to MTAl, transferred to MTA3,
delivered to EDI-UA3 and retrieved by EDIMG user 3. EDI-UA3 will respond with an appropriate EDIN, accepting
EDIM responsibility (i.e., PN). (If EDI-UA3 had determined that EDIMG user 3 could not retrieve the message, EDI-
UA3 would have responded with an EDIN refusing EDIM responsibility (i.e., NN)). Figure 7 illustrates the flow of
information. The sequence of EDIMs and EDINs is depicted in table 1.
EDIMG
user 2
cl 1
EDI messaging environment
TO10132083
---b Direction of transfer EDIN
Direction of transfer EDIM
Figure 7 - Case 1: No forwarding
0 ISO/IEC ISODE@ 1002143 : 1995 (E)
Table 1 - Case 1: No forwarding
Events EDIM EDIN
1 EDI-UAl submits EDIM to MTAl
MTAl transfers EDIM to MTA3
3 MTA3 delivers EDIM to EDI-UA3
4 EDI-UA3 submits PN/NN to MTA3
5 MTA3 transfers PN/NN to MTAl
6 MTAl delivers PN/NN to EDI-UAl
84 . Case 2: Content not changed and EDIM responsibility forwarded
In this case an intermediary EDI-UA forwards a message from EDI-UAl to EDI-UA3. The final recipient is EDI-UA3,
and EDI-UA2 performs a forward operation, forwarding EDIM responsibility to EDI-UA3. The EDIM prepared by
EDI-UAl is addressed to EDI-UA2. The EDIM is delivered to EDI-UA2, which forwards it unchanged to EDI-UA3,
based on selection criteria known to EDI-UA2.
EDIM responsibility is handled as follows:
When EDI-UA2 forwards EDIM responsibility, it shall create the forwarded EDIM so that requested
EDINs are received by EDI-UAl, (see ISO/IEC 10021-9 I CCITT Recommendation X.435 for details).
The following EDINs may be sent.
a) If EDI-UAl requested notification of forwarding of EDIM responsibility, EDI-UA2 shall send
forwarded notification - FN to EDI-UAl. This EDIN is sent when EDI-UA2 successfully submits
the EDIM to MTA2.
b) If EDI-UA2 receives a non-delivery notification from MTA3 (via MTA2) it may send negative
notification - NN to EDI-UAl.
NOTE - EDI-UA2 has the choice to send, or not to send, the EDIN in this case.
No other EDINs may be requested or sent. For example, EDI-UA2 cannot request notifications
from EDI-UA3, and EDI-UA3 cannot send EDINs to EDI-UA2.
In the case of non-delivery, EDI-UA2 may attempt to resubmit the EDIM to the intended recipient.
In this case, the NN to EDI-UAl is sent only when EDI-UA2 determines that it shall no longer
attempt to resubmit the EDIM to EDI-UA3.
c) If forwarding succeeds, EDIUA3 shall send an appropriate EDIN to EDI-UAl, accepting or
refusing EDIM responsibility.
Figure 8 illustrates the information flow described above for case 2. The sequence of possible EDIMs and EDINs is
explained in table 2. Events (8,11,13,15 ) and (10, 12, 14, 16 ) are mutually exclusive.
ISOhEC 10021-8 : 1995 (Ej 0 ISO/IEC
,
9,15,16
\ / I2 I 1
Message transfer system
WTS)
EDI messaging system
(EDIMS)
ED1 messaging environment
(EDIME)
mo133sQ3
- ----b Direction of transfer EDIN, NDN
b Direction of transfer EDIM
Figure 8 - Case 2: EDIM responsibility forwarded
Table 2 - Case 2: EDIM responsibility forwarded
Events EDIM EDIN NDN
1 EDI-UAl submits EDIM to MTAl
2 MTAl transfers EDIM to MTA2
MTA2 delivers EDIM to EDI-UA2
If requested, EDI-UA2 submits FN
to MTA2
EDI-UA2 submits forwarded EDIM
to Mm2
6 MTA2 transfers FN to MTAl
7 MTA2 transfers EDIM to MTA3
8 MTA2 sends NDN to EDI-UA2
WA1 delivers FN to EDI-UAl
10 MTA3 delivers EDIM to EDI-UA3
EDI-UA2 submits NN to MTA2
EDI-UA3 submits PN/NN
to MTA3
13 MTA2 transfers NN to MTAl
MTA3 transfers PN/NN to MTAl
15 MTAl delivers NN to EDI-UAl
MTAl delivers PN/NN
to EDX-UA 1
0 ISO/IEC ISO/IEC 10021-S : 1995 (E)
The following should be noted:
1) EDI-UAl will usually receive several EDINs if it requests FN ( forwarded notification).
2) EDI-UAl may receive EDINs in a sequence other than that in which they were created.
3) EDI-UAl may receive no EDIN whatsoever even if it requested FN (for example, in the case of
catastrophic failure of EDI-UA2 after MTA2 has delivered the EDIM to EDI-UA2).
It is up to EDI-UAl to correctly handle 1 through 3 above. Item 1 can be handled for example, by keeping track of:
a) the EDIM ID,
the original recipient,
b)
c) the submission time, and
d) the ED1 notifications expected.
Item 2 can be handled by using the UTC time included in the EDIN (EDIN creation time). Item 3 can be handled with
a time-out mechanism in EDI-UAl. Mechanisms to handle 1 to 3 are local implementation issues, thus beyond the
scope of this part of ISO/IEC 10021.
85 . Case 3: EDIM responsibility not forwarded
This scenario provides for the case where the EDIM prepared by EDI-UAl is addressed to EDI-UA2, and EDI-UA2
accepts EDIM responsibility for the message prior to forwarding to EDI-UA3. This would occur, for example, if EDI-
UA2 were to add or remove body parts when forwarding (changes of the content). When EDIM responsibility is
accepted, EDI-UA2 sends an EDIN to the originator (i.e., PN), and creates the forwarded EDIM so that no further
EDINs are received by EDI-UAl (the originator) (see ISO/lEC 10021-9 I CCITT Recommendation X.435 for details).
As in case 2, EDI-UAl addresses the EDIM to EDI-UA2. As in both previous cases EDI-UA3 represents the fina
destination.
Upon retrieval of the EDIM, EDI-UA2 returns an appropriate notification to EDI-UAl. The message is then forwarded
to EDI-UA3. Since initial EDIM responsibility has now been accepted, EDI-UA2 is at liberty to request EDIM
responsibility or not, as desired. If requested, the resulting EDIM responsibility relationship shall apply between EDI-
UA3 and EDI-UA2, i.e. not end to end as in the previous cases. In the scenario described here EDIM responsibility is
assumed to have been requested, with the result that EDI-UA3 responds to EDI-UA2 with an appropriate notification.
Figures 9 and 10 illustrate the flow of information for case 3. The sequence of EDIMs and EDINs for case 3 is
explained in table 3.
ISO/IEC 10021-8 : 1995 (E)
0 ISO/IEC
ED! messaging environment
(EDIME)
Direction of transfer EDIN
Direction of transfer EDIM
Figure 9 - Case 3: EDIM responsibility not forwarded, Part 1
EDI messaging system
EDI messaging environment
(EDIME)
T0101350-93
---b D irection of transfer EDIN
dD irection of transfer EDIM
Figure 10 - Case 3: EDIM responsibility not forwarded, Part 2
0 ISO/IEC
ISO/IEC 10021-8 : 1995 (E)
Table 3 - Case 3: EDIM responsibility not forwarded
4 EDI-UA2 submits PN to MTA2
5 EDI-IJA2 submits forwarded EDIM to MTA2
MTA2 transfers PN au MTAl
7 MTA2 transfers EDIM to MTA3
MTAl delivers PN to EDI-UAl
9 MTA3 delivers EDIM to EDI-UA3
10 EDI-UA3 submits PN/NN to MTA3
11 MTA3 transfers PN/NN to MTA2
12 MTA2 delivers PN/NN to EDI-UA2
9 ED1 naming, addressing and use of directory
The MHS use of Directory as defined in ISO/IEC 10021-l 1 CCITT Recommendation X/F.400, clause 13 is used to
provide the Directory services required for ED1 messaging.
Each management domain should provide directory services for its EDIMG users.
ED1 messaging, naming and addressing and the subsequent directory service requirements are outlined in annex D of
this part of
...