top - download
⟦bc6de6ddc⟧ Wang Wps File
Length: 23329 (0x5b21)
Types: Wang Wps File
Notes: LKSAA PROPOSAL
Names: »4215A «
Derivation
└─⟦37660ca85⟧ Bits:30006030 8" Wang WCS floppy, CR 0386A
└─ ⟦this⟧ »4215A «
WangText
Issue 1.4
LKSAA - VOLUME II
SYS/84-04-24
Part 2
TECHNICAL PROPOSAL
Page
2 OUTGOING MESSAGE PROCESSING .....................
2.1 INJECTION OF MESSAGES .......................
2.2 STORAGE .....................................
2.3 HEADER AND TEXT CONTROL .....................
2.3.1 Message Preparation .....................
2.3.2 Message Validation ......................
2.3.2 Message Queues ..........................
2.3.4 Message Release .........................
2.4 AUTOMATIC PROCESSING ........................
2.4.1 Logging .................................
2.4.2 General Comments on Message Processing ..
2.4.2.1 Priority ............................
2.4.2.2 Addressing Receivers ................
2.4.2.3 Messages in Plain Text ..............
2.4.2.4 Messages To Be Encrypted ............
2.4.3 Creation of Message Control Data ........
2.4.3.1 Message Synthesis ...................
2.4.3.2 Conversion Procedures ...............
2.4.3.3 Transmission Procedures .............
2.4.3.4 Message Routing .....................
2.4.3.4.1 Completed Routing ...............
2.4.3.4.2 Selective Routing ...............
2.4.3.4.3 Routing Assistance ..............
2.4.4 Message Generation ......................
2.5 TRANSMISSION ................................
2.6 REDIRECTION .................................
2.7 REPETITION ..................................
2.8 CLASSIFIED MESSAGE PROCESSING ...............
2.9 ERROR PROCESSING ............................
2̲ ̲O̲U̲T̲G̲O̲I̲N̲G̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
2.1 I̲N̲J̲E̲C̲T̲I̲O̲N̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
Messages can be injected to the ZVA-system from the
following input devices:
o Terminals and workstations in the working area.
o Terminals and devices in the control room, such
as:
o Optical Character Reader
o Papertape Reader
o VDU's
o Relay from incoming channels.
Messages consist of Header Data (Control Data) and
Text Data.
2.2 S̲T̲O̲R̲A̲G̲E̲
The system has the capability to store all incoming
and outgoing messages to allow users to subsequently
retrieve them as required.
Messages are stored in the format as prepared and validated.
Messages are stored on on-line as well as off-line
devices. Messages are kept on-line up to 30 days after
which they are dumped to off-line devices.
Messages are stored together with a number of retrieval
parameters which are internal system number, time of
occurance (System Data and time), release (Data time
Group), originating AV, message identification, channel
identification, station serial number, subject indicator
code, message identification and user code.
The mentioned parameters not applicable to the RFP,
may be provided as options.
A retrieval can take place by one or more of the above
mentioned parameters. In addition to the above parameters,
a time range can be specified for which messages shall
be retrieved.
If more than one message meet the criteria, a retrieval
catalogue is presented, which refers to messages fitting
the key.
The user can based on the catalogue display select
the one to be chosen.
2.3 H̲E̲A̲D̲E̲R̲ ̲A̲N̲D̲ ̲T̲E̲X̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲
2.3.1 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
See Message Flow diagrams Figure 1.3-3 and 1.3-4 for
the principle flow of an outgoing message.
The user has a number of terminal functions that supports
preparation of messages and they are:
- Initial message preparation, supporting preparation
of message header and text according to AA format
and ACP 127 format (if this option is exercised).
- Message coordination sending a drafted message
to other organizational units than the drafter
for coordination according to a specified distribution
(if this option is exercised)
- Message comments providing the user with an electronic
mail capability for communication between terminals
within the LKSAA.
- Datasets providing user defined predefined messages
where the construction is based upon standardized
message skeletons and text (if this option is exercised)
Messages are in general prepared via VDUs. This interactive
preparation process is controlled by the Terminal Package.
The process involves:
1) Various methods of text preparation (VDU input;
appending texts of other message; use of predefined
messages with validation of formatted data)
2) Validation of information to be used in the header
of the message (addresses, precedence, security
classifications) and therefore access to the appropriate
address tables
3) Operator assistance in the Message Preparation
of Header Data associated with the messages text
if header data for routing is not complete.
4) Validation of message subject and distribution
information (SICs, and local distribution information)
and therefore access to the appropriate tables
5) Acceptance of instructions concerning the further
processing of the message (for example, coordination,
release and special handling). Provided the message
has not been queued for release, it may be edited
and changed and is held by the system pending the
release verdict.
Messages can furthermore be entered into the system
via Teletypes, Paper Tape Readers and an Optical Character
Reader. Text Processing Equipment and Intelligent Workstations
can be interfaced as an option.
Messages entered from these sources will be validated
and if not accepted, an error message will be generated.
The message can then be corrected and reentered or
it can be assisted by the Message Service Operator.
Having prepared and coordinated a message the user
has to send it for release before conversion into AA
format or ACP127 format (if this option is exercised)
and subsequent transmission.
See figure 2.3.1-1 for example of general preparation
format.
Figure 2.3.1-1
Figure 3.4-2
Format A-1/1
Figure 3.4-3
Format A-1/2
Figure 3.4-5
Format A-2
2.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Before an outgoing message can be processed, the user
must ensure the completeness of the text of the message,
its addresses or Routing Indicators (RIs), security
classification, precedence etc. Message preparation
is a general name for all the processing involved in
collecting this information. The actual processes vary
according to the type and source of a message, but
the end result will be a stored message with an unique
Message Identifier.
In case of unsuccessful validation, error codes will
be displayed in the margin and the erroneous fields
will be highlighted in inverse video for ease of error
correction, in addition plain language error messages
will be displayed by entering the error codes shown.
Messages with insufficient control information for
automatic processing and routing will be distributed
to the Message Service Operator (MS0) for assistance.
Append of messages text is provided in a user dialogue.
By selecting the appropriate command, a screen format
will be shown on the VDU. Text may in addition be inserted
from a file, a papertape and an optical character reader.
2.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲Q̲u̲e̲u̲e̲s̲
Messages are handled according to precedence. The precedence
levels are FLASH, IMMEDIATE, PRIORITY and ROUTINE.
All system queues are implemented for these four precedence
levels. Flash priority is an option.
The system will display queue status on the VDU's for
various system queues such as release queue, retrieval
queue and message presentation queue.
The user can get access to the messages displayed in
his queues by a "get message" function. Furthermore
he has the capability to delete or save a message,
which he has requested to get access to.
An example of the queues displayed at a message preparation
terminal is presented in figure 2.3.1-1 and further
discussed below.
The number of messages queued for the terminal by precedence
as well as those for coordination, release, display,
or response on a terminal will be shown. Each category
is identified by a alpha descriptor and the number
of items of this category in the terminal queue.
Queue information is updated every minute except when
FLASH messages are queued which causes immediate update
and a short audio alarm.
In the category "coordination" is contained the number
of messages for coordination. Coordination is an option.
In the category "release" is contained the number of
messages for release.
In the category "display" is contained the number of
incoming message, comments, and outgoing messages.
In the category "response" is contained the number
of retrieved messages (from off-line database), append
notifications (off-line append), delete notifications
and release notifications.
2.3.4 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲
A message prepared via a VDU has to be presented to
an appropriate user/terminal for release. Release does
not alter a message; it allocates a release date-time
group (file time) and a station serial number to the
message. Release is an interactive transaction controlled
by the terminal package which has one of the following
results:
1) M̲e̲s̲s̲a̲g̲e̲ ̲r̲e̲l̲e̲a̲s̲e̲d̲
The message is queued for the format Synthesis
Process.
2) R̲e̲l̲e̲a̲s̲e̲ ̲r̲e̲f̲u̲s̲e̲d̲
The Releaser sends an appropriate comment to the
user/terminal associated with the drafting of the
message.
3) R̲e̲l̲e̲a̲s̲e̲ ̲D̲e̲f̲e̲r̲r̲e̲d̲
The Releaser sends an appropriate comment to the
user/terminal associated with the drafting of the
message.
2.4 A̲U̲T̲O̲M̲A̲T̲I̲C̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
2.4.1 L̲o̲g̲g̲i̲n̲g̲
When a prepared message is accepted by the Terminal
Package, a log record is automatically generated. The
logged information containing a unique message identifier,
date-time-stamp, classification, working unit for message
preparation, name and phone number of drafter, identification
of user (operator) will be inserted from the user profile
and other tables. The stored log record will not be
part of the transferred message.
2.4.2 G̲e̲n̲e̲r̲a̲l̲ ̲C̲o̲m̲m̲e̲n̲t̲s̲ ̲o̲n̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
2.4.2.1 P̲r̲i̲o̲r̲i̲t̲y̲
As described in section 1.4.2 and 2.3.3, messages will
be processed according to the priority levels: routine,
priority, immediate and flash (optional). Within priority
levels messages will be handled on a first in first
out basis.
On certain telex channels, all messages shall be processed
immediately after establishing the connection, i.e.
independantly of the priority levels for other messages
for other circuits. Information for this decision on
processing of outgoing messages will be contained in
the system tables for selection of circuits and routes.
2.4.2.2 A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲R̲e̲c̲e̲i̲v̲e̲r̲s̲
Messages can be addressed as follows:
- A single addressee, identified by a plain language
address.
- A variable number of addresses identified by a
number of plain language addresses.
- A group of addresses identified by an addressee
group identifier.
- A group of addresses with exeption of certain addresses
identified by an address group identifier and the
relevant exeption plain language addresses. This
is an optional facility.
Addresses, circuits and routes are contained in a set
of related tables managed by the Table Management System.
Table entries can be added, changed or deleted by the
Supervisor by means of a VDU dialogue.
2.4.2.3 M̲e̲s̲s̲a̲g̲e̲s̲ ̲i̲n̲ ̲P̲l̲a̲i̲n̲ ̲T̲e̲x̲t̲
A message is handled as a plain message when the classification
is "offen" and the route for the addressee is not marked
for forced encryption.
For addressees, which can be reached via an on-line
channel, the message is routed automatically. In case
only an off-line network is available, the message
is punched on papertape and a handling instruction
is printed.
2.4.2.4 M̲e̲s̲s̲a̲g̲e̲s̲ ̲t̲o̲ ̲b̲e̲ ̲E̲n̲c̲r̲y̲p̲t̲e̲d̲
As message is to be encrypted if this is indicated
in the control data or if the route for the addressee
requires encryption according to the routing table.
Messages for off-line encryption can be handled either
ZVA-internal or ZVA-external. Encryption is processed
separately before transmission.
Messages for on-line encryption will be encrypted and
transmitted in parallel processing. If the encryption
device and the channel is not on-line connected to
the ZVA, the messages will be punched on papertape
and a handling instruction will be printed.
2.4.3 C̲r̲e̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲D̲a̲t̲a̲
2.4.3.1 M̲e̲s̲s̲a̲g̲e̲ ̲S̲y̲n̲t̲h̲e̲s̲i̲s̲
Much of the information needed for the header of a
message is supplied during the various message preparation
functions. The format synthesis function continues
the build-up of this information.
Priority, classification, encryption demand and sender
identification are supplied during message preparation.
The Station Serial Number, the filing-time and the
Data Time Group is supplied at release of the message.
The Routing Indicators is selected automatically during
the following routing procedures (ref. description
2.4.3.4).
The remaining synthesis and formatting procedures are
provided as follows:
2.4.3.2 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The messages being prepared at terminals are stored
in an internal message format. After release of messages,
they are sent for format-conversion.
The functions of format-conversion are:
- Formatting of precedence, called station and calling
station of complete entered messages
- Formatting of encryption control data
- Formatting of Supervisor prepared Service Messages
- Conversion and formatting of user prepared messages
into complete AA-, ACP127, COREU or WUI -format
- Separation into sections if applicable for that
message
- Preparation of separate transmissions in case multiple
routes or limit exceeded on RI's
- Insert of ZEN in front of plain language addresses
where multiple routes are applicable
The messages are after conversion forwarded to transmission
upon a channel indicated via the circuit selected under
Routing. A message containing Local Plain language
addresses will, however, be directed for local distribution.
2.4.3.3 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of Transmission Procedures are:
- Formatting of start-off-transmission, station and
channel designator, figure shift, letter shift
and security warning prosign.
- Formatting of Pilots upon automatic or
Supervisor initiated retransmissions (reruns)
- Preemption for transmission of flash message where
applicable
- Delivery of format-lines for transmission including
insertion of formal parameters
- Insertion of delimiter line
- Insertion of crypto control data
- A transmitted message will after successful transmission
be taken care of by the Transmission Control Procedures,
if the message shall be acknowledged.
2.4.3.4 M̲e̲s̲s̲a̲g̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲
Routing of messages is performed after message release
and before completion of message synthesis.
The basic functions of routing is to select one or
more output-circuits upon which the message or message
̲views shall be transmitted after conversion into external
message format.
Two routing functions are provided
- completed routing
- selective routing
2.4.3.4.1 C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲
The complete routing functions are to select circuits
for transmission based upon a list of RI's.
These RI's might have been derived through called station
of a complete entered message, assigned during Service
Message Prepare or assigned via RI-assignment procedures
(MSO). Anyway the message classification shall be compared
with the RI and circuit classification and the availability
of the pre-selected circuits shall be checked before
the message may continue for transmission.
Unknown RI's will result in RI ̲assignment.
Misrouted and missent messages are detected during
format analysis (no local RI found/no local PLA found).
2.4.3.4.2 S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲
The subjects for selective Routing are local prepared
messages of Plaindress-type entered for Conversion
first time (second time will be after RI-assignment
or for Rerun etc.).
The function is to select a RI for each PLA.
Up to 4 alternatives for select of an RI may exist
for each PLA.
The following principles for select of a RI will be
used:
a) The first RI with a classification higher than
or equal to the classification of the message will
be selected.
b) If the classification of the associated circuit
is lower than the classification of the RI a logical
error is found in the RI-table, a warning will
be sent to the supervisor printer and the next
RI will be selected.
c) If the circuit referenced via the RI is disconnected
or no channels are available upon that circuit
(closed), the next RI will be selected.
d) If no more RI's can be selected the message will
be rejected for RI-assignment with the last tested
RI (if any) as a suggestion, i.e. distributed for
routing assistance.
If a "ZEN" is associated to the PLA, no RI will
be selected.
2.4.3.4.3 R̲o̲u̲t̲i̲n̲g̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
Manual intervention might be needed for assignment
of alternative Routing Indicators (RIs) in case
- the Plain Language Address (PLA) is unknown
- the RI is unknown
- no circuit is assigned to the RI
- the classification of the RI is too low
- all channels associated to an output-circuit has
been closed
The message is presented at a message service position
together with a Routing-List where the RI's in question
is flagged with an explainable error ̲code.
The MSO reenters the message for continued Routing
and Conversion after his assignments.
2.4.4 M̲e̲s̲s̲a̲g̲e̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
As mentioned in section 2.4.2 and 2.4.3, the Conversion
Package will handle message synthesis and generate
messages according to the required addressees and channels
and in respect to classification and encryption in
compliance to the detailed rules mentioned in the RFP.
These procedures will not be repeated in this text.
2.5 T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲
Messages will be transmitted through the following
carriers:
- leased lines
- dial-up lines
- radio channels
Transmission and protocols (if applicable) will be
handled by the Transport Package.
For radio channels the connection will be established
manually from the radio control position for the ZVA.
The Supervisor has capabilities to open and close,
connect and disconnect channels by means of a VDU dialog,
but the connection will not be established automatically
from the ZVA. While the connection is existing, it
will be handled by the ZVA as a point-to-point line.
For dial-up lines, the ZVA will automatically establish
a connection when required. In case of errors in establishing
a connection, the ZVA will retry a specified number
of times and after a time interval repeat the establishing
procedure.
Before insertion of an on-line encryption and transmission
the ZVA will ensure that a connection is established.
2.6 R̲E̲D̲I̲R̲E̲C̲T̲I̲O̲N̲
The Message Service Operator has capabilities for rerun
(rerouting), redirection, and readdressing of messages
by means of separate commands for the corresponding
VDU dialog.
Furthermore the Supervisor dynamically can change the
system tables such as routing tables and addressing
tables.
2.7 R̲E̲P̲E̲T̲I̲T̲I̲O̲N̲
The Message Service Operator (MSO) has the capability
to receive and prepare service messages in plain text
as well as in standardized and abbreviated lay-out.
At reception of a service message requesting message
repetition (rerun), the MSO can by means of a VDU dialog
rerun the messages.
The Traffic Handling Package on the ZVA system is able
to send and receive abbreviated service messages. Based
on such a request, the ZVA can automatically rerun
messages.
An abbreviated service message for rerun will contain
information on station-serial numbers (possibly a number
interval) and addressees, or channel-serial number
(possibly an interval), status request for reencryption
and rerun and status request for message rerun.
Abbreviated service messages, which cannot be handled
automatically by the ZVA, will be distributed to the
MSO for manual assistance.
A rerun of a message will generate a log record and
for manual reruns the operator identification will
be logged.
The maximum level for reruns (number of reruns) is
a system parameter, which can be changed by the Supervisor
by means of command and VDU dialog. In case this rerun
level is exceeded, a report will be generated. Automatic
rerun will then be stopped. For certain channels rerun
may be prevented.
2.8 C̲L̲A̲S̲S̲I̲F̲I̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
All classified messages will be logged in a security
log containing a unique message identifier amongst
other information. The security log will be printed
on the supervisor printer.
Security is described in part 2, section 1.7 and in
part 1, section 2.7.
2.9 E̲R̲R̲O̲R̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
Erroneous messages will be handled either by the drafter
or by the Message Service Operator according to the
type of error.
Messages, which are not finally processed by the drafter,
can be stored in the system and processing can be resumed
on a later point of time (if the option for Continue
Message Preparation is exercised) by means of a VDU
dialog.
A draft message may be coordinated with one or more
other organizational units than the drafter and comments
may be sent between terminals using the electronic
mails facilities.
Before a prepared message can be sent it must be released.
This is done on a VDU dialog between the drafter and
the releaser and a release notification is sent to
the drafter.
Status of outgoing messages can at any time be displayed
using a simple command.
Additional facilities are described in section 2.3.
