top - download
⟦455c62ec4⟧ Wang Wps File
Length: 99214 (0x1838e)
Types: Wang Wps File
Notes: MWHQ
Names: »2498A «
Derivation
└─⟦21670ed14⟧ Bits:30006224 8" Wang WCS floppy, CR 0211A
└─ ⟦this⟧ »2498A «
WangText
…00……00……00……00……00… …02……00……00…
…1f……0f……1f… …1e……0b……1e……0c……1e……0f……1e……02……1d……09……1d……0a……1d…
…1c……0b……1c…
…1b……0a……1b……0b……1b……01……1a……0a……1a……02……19……09……19……00……19……06……18……0d……18……05……17……0e……17… …16……0a……16……02……15……0a……15……00……15… …14……0b……14……01……14……07……13……0d……13……02……13……06……13……07……12……08……12……09……86…1 …02… …02… …02…
…02…SYS/820728…02……02…#
PART IV
OPERATIONAL PROPOSAL…02……02…MWHQ-MEDS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
4.6 N/A .........................................
21
4.7 EMERGENCY OPERATION .........................
21
4.8 TERMINAL OPERATION ..........................
21
4.8.1 General .................................
21
4.8.2 Terminal Functions ......................
22
4.8.3 Terminal Identification .................
22
4.8.4 Terminal User Authorisation .............
22
4.8.5 Generation of Messages ..................
23
4.8.6 Receipt of Messages .....................
23
4.8.7 Message Communication with other
Terminals ...............................
24
4.8.8 Interrogation of the File with
Incoming Messages .......................
24
4.8.9 Interrogation of the File with
Outgoing Messages .......................
24
5 INSTALLATION MEDS ...............................
25
5.1 REQUIREMENT ANALYSIS ........................
25
5.2 INSTALLATION PLANNING .......................
26
5.2.1 Shelter Surveys .........................
27
5.2.2 Shelter Preparation Requirements ........
27
5.2.3 Equipment Installation Drawings .........
28
5.2.4 Shelter Readiness Verification ..........
28
5.3 INSTALLATION ACTIVITIES .....................
29
5.3.1 Transportation ..........................
29
5.3.2 Shelter Installation ....................
30
5.3.3 Hardware Configuration ..................
32
5.3.4 System Acceptance .......................
38
6 WORD PROCESSOR ..................................
39
6.1 GENERAL .....................................
39
6.2 TYPE OF WORD PROCESSORS .....................
39
6.3 MODIFICATION OF THE WORD
PROCESSOR FOR MWHQ USE ......................
39
6.4 APPLICATION SOFTWARE ........................
40
7 MEDS - BUSSYSTEM ................................
41
7.1 SYNCHRONIZATION OF TDX-NET TRAFFIC ..........
43
7.2 TDX-NET FRAME FORMAT AND ADDRESSING .........
44
7.3 BANDWIDTH ...................................
49
7.4 POWER-UP PROCEDURES .........................
49
7.5 TDX-NET PROTOCOL ............................
49
7.5.1 Physical Level (level 1) ................
50
7.5.2 Link Level (level 2) ....................
57
7.5.3 Network Level ...........................
70
7.5.4 Bandwidth Allocation ....................
72
7.5.5 Diagnostic and Statistic ................
73
8 MEDS FLOPPY-DISC SYSTEM .........................
74
8.1 FUNCTIONAL SUMMARY ..........................
76
8.2 BLOCK DIAGRAM ...............................
76
8.2.1 Main Processor ..........................
78
8.2.2 Front Processor .........................
78
8.2.3 Floppy Disc Controller ..................
78
8.2.4 Multibus Interface ......................
79
8.2.5 Multimodule Interface ...................
79
8.2.6 Bus Arbiter & Control Logic .............
79
8.3 APPLICATION SOFTWARE ........................
80
9 MEDS PRINTER ....................................
81
10 MEDS CRYPTO CONVERTERS ..........................
83
11 MEDS EXCHANGE ...................................
84
12 MEDS TERMINALS ..................................
85
12.1 ALPHANUMERICAL DISPLAY ......................
85
12.1.1 Screen ................................
86
12.1.2 Keyboard ..............................
88
APPENDIX ..........................................
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
The Christian Rovsing A/S proposal for a Message Entry
& Distribution System (MEDS) for the AFCENT MWHQ is
based on our Local Area Network TDX-Bus,which has been
produced since 1978 and implemented in various Military
and Commercial Projects.
In FIGURE 1-1a System Layout is shown to give an overview
of the Message Entry & Distribution System. Two MEDS
are included, one for the Main Element and one for
the Leapfrog Element, where the Main Element is the
one currently operational while the Leapfrog Element
is being moved to a new site for installation.
The MEDS will:
- control preparation of outgoing messages originated
in the MWHQ Staff Element, i.e. message preparation
and co-ordination at VDUs.
- process already prepared messages by storing and
subsequent presentation for supervisors for conversion
to transmission formats.
- transmit all outgoing messages via MWHQ switching
system.
- receive all incoming messages for the AFCENT MWHQ.
- process already received messages by storing and
subsequent presentation for supervisors for distribution.
- assist the supervisory personnel in distribution
of incoming messages to users in the Staff Element.
The TDX-net solution to the MEDS is a flexible and
versatile approach, providing AFCENT with a truly distributed
system. Only a small number of different hardware
modules are used in order to simplify the spare part
handling. The processing power of the MEDS is distributed
over various micro-computer and inter communication
is via the TDX-bus, which is a twisted pair of two
coaxiial cables. The TDX-bus has been utilised in
other military projects like CAMPS and FIKS.
SYSTEM LAYOUT…01…FIGURE 1 - 1a
The MEDS will be equipped with word processing systems
(3) to enable the supervisory personnel to convert
the message format from the internal format to the
external format, i.e. ACP-127
Christian Rovsing A/S has developed other systems which
require utilisation of the ACP 127 procedures, e.g.
CAMPS and FIKS. Also, implementation of a user-
friendly man-machine interface on the Delta Data T7260
Terminals has been done in the CAMPS System.
2̲ ̲M̲E̲D̲S̲ ̲H̲O̲U̲S̲I̲N̲G̲
The MEDS for one element (Main or Leapfrog) will be
housed in three shelters, named:
- The MESSAGE-shelter
- The CRYPTO-shelter
- The CEROFF-shelter
The MEDS Equipment installed in the Message-shelter
will perform processing and storage of both incoming
and outgoing messages.
The MEDS Equipment installed in the Crypto-shelter
will interface to the on-line e̲n̲c̲r̲y̲p̲t̲i̲o̲n̲/̲d̲e̲c̲r̲y̲p̲t̲i̲o̲n̲
̲equipment and will act as intermediate equipment to
the MWHQ Central Switching System.
The MEDS Equipment, i.e. user VDUs, will be installed
in various Staff-Office shelters in the Staff Element.
3̲ ̲M̲E̲D̲S̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲
The customers outline of the MEDS is shown in FIGURE
3-1. The outline describes the MEDS Equipment in the
three shelters, Message, Ceroff and Crypto, while the
user VDUs will be installed in various shelters in
the Staff Element. In appendix A is shown datasheets
for individual hardware equipment.
3.1 C̲r̲y̲p̲t̲o̲-̲S̲h̲e̲l̲t̲e̲r̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The Crypto-Shelter will be equipped with two standard
tele-printers for emergency operation. They can be
interfaced to two 50 baud crypto-devices for transmission
and reception of off-line encrypted message.
These tele-printers are identical to the other tele-printers
used in the Message Shelter and the Ceroff Shelter,
except that they are equipped with paper tape reader
and puncher.
The Convertor System in the Crypto Shelter provides
the conversion of messages for both outgoing and incoming
messages. The format used inside the three subsystems
will be the standard TDX-Format, whereas the format
on the various external lines will depend on the type
of communication lines, e.g. from 50 to 600 baud.
Outgoing messages are received from the Message Shelter
subsystem via the XNP Network port of the convertors
and routed to the various communication line interfaces
based on the internal addressing information in the
bus format. The Convertor System is initially equipped
with 20 line interfaces, and can be expanded.
The TDX Controller of the convertor subsystem is the
central device of the TDX bus system. It controls
all traffic on the bus and ensures that all devices
attached to the bus are polled in correspondance with
the associated bandwidth.
MEDS CONFIGURATION…01…FIGURE 3 - 1
3.2 M̲e̲s̲s̲a̲g̲e̲ ̲S̲h̲e̲l̲t̲e̲r̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The Message Shelter Subsystem will be attached to the
convertor in the Crypto Shelter via a special cable
of maximum 5 metres length. The Interface will be
in accordance with a V24 Interface.
The two printers in the Message Shelter - for printing
of incoming and outging messages, respectively - will
be identical High Speed Matrix Printers. The printing
speed will be 150 cps, corresponding to 64-440 LPM
depending on the number of characters per line. The
printers will have their own control system with set-able
baud rates of 100-9600 baud and line buffers of 256
characters in order to optimise traffic flow on the
interface between the bus system and the printer.
The Message Shelter Subsystem will be equipped with
two identical floppy disc systems for storing incoming
and outgoing message respectively plus one extra floppy
disc system for initialisation of user floppy discs.
Each of the two main floppy disc systems controls four
disc stations.
The Floppy Disc System, which stores outgoing messages
will have its disc stations dedicated as follows:
One station will contain messages that have been prepared
and co-ordinated at the user VDUs but not yet transmitted.
These messages will be stored in an internal format
different from the full ACP-127 format used on the
communication lines. The Floppy Disc System will store
messages in a queue system with different subqueues
per precedence levels, ensuring that high priority
messages are handled first. Within each precedence
level messages are handled on a first in first out
basis.
The second disc station is used for capacity overflow
storage of outgoing messages which have not yet been
transmitted.
The third station will be used for storage of messages
that have already been transmitted. These messages
can be retrieved afterwards by one of the terminals
for interrogation. The fourth station will provide
an overflow backup for station three.
Disc Station One on the incoming system will store
all incoming messages prior to distribution to the
word processors.
The second disc station will provide overflow backup
for disc station one.
The third disc station will be used for storage of
messages that have already been distributed to the
user terminals. Interrogation can be made to these
messages from the various terminals.
The fourth station will provide as overflow backup
for disc station three.
The Message Shelter Subsystem will be equipped with
three word processors to be installed in three T7260
TC Delta Data Terminals, which are hardware identical
to the terminals in the Staff Element, but equipped
with different software in order to provide the word
processing capability needed in the Message Shelter.
The Word Processor Terminals are equipped with a floppy
disc system in order to store the various subprograms
and data for handling incoming and outgoing messages.
Each Word Processor is able to provide message conversion
from the internal format generated in the Staff Element
to the ACP-127 Format used on the communication lines.
The Word Processor Operator can retrieve the ACP-127
address lines in the second floppy disc station. After
conversion the operator will send the message in ACP-127
Format via the bus to the converter in the Crypto Shelter
which in turn will route the message to the appropriate
line interface and accomodate variances in the different
communication lines, e.g. band rates.
Each word processor is able to distribute incoming
messages to the user terminals in the Staff Element.
This is accomplished by using a file relating the
SIC Codes and the various terminals. A file on the
second disc station contains the necessary information.
The bus used in all three subsystems is the versatile
TDX-bus system manufactured by Christian Rovsing A/S
for various military and commercial system. The CAMPS
Project, which consists of installation of 16 computerised
messages processing systems throughout the NATO countries,
utilises the TDX bus system for interfacing the various
terminals and communication lines to the main processor.
In FIKS, which is an Integrated Tri-service Communication
System for the Danish Defence, the TDX bus is used
in a similar fashion.
The bus system is controlled by a TDX-controller, which
polls all the devices attached to the bus system.
All the attached devices have their own micro computer
based controllers to provide independent, distributed
processing throughout the system.
The exchange in the Message Shelter will be implemented
as a separate TDX bus system. The elements of Exchange
are the same hardware components used in the rest of
MEDS. This provides greater flexibility and easier
maintenance. The initial exchange can handle up to
64 lines and can easily be upgraded if more lines are
requested.
A TDX-Controller performs all the necessary polling
of devices on the bus in the exchange. In order to
control communication between all of the terminals
in the Staff Element, the Bus System in the exchange
will be equipped with a XNA-network administrator.
Communication between the terminals in the Staff Element
will be initiated by the operator at the originating
terminal, who enters the identification of the recepient
terminal. The Bus System then sends the message to
the XNA, which interprets the destination identification,
and ensures that the message is sent to the appropiate
terminal.
The Message Shelter will be provided with one tele-printer,
which will be used for:
- communication with other tele-printers and terminals
in the MWHQ via the exchange
- testing the communication via the exchange
- printing incoming and outgoing messages on command
of the word processors to provide additional copies
if one of the Staff Cells wishes to receive a written
copy of a message.
This teleprinter is identical to the other teleprinter
in the MWHQ except for the lack of a paper tape reader
and puncher.
A full description of the signalling on the TDX-NET,
i.e. between the terminals and others devices is described
in section 7.
3.3 C̲E̲R̲O̲F̲F̲-̲S̲h̲e̲l̲t̲e̲r̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The CEROFF-Shelter will be provided with two tele-printers,
each equipped with paper tape readers and punchers.
They will be identical to the other tele-printers
to be delivered for the MWHQ. The Teleprinter can
be used for transmission and reception of messages
which have been/will be off-line encrypted/decrypted
by AROFLEX Equipment. The AROFLEX Equipment is to
be provided by SHAPE.
3.4 M̲E̲D̲S̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
The Staff Element of the MWHQ will be equipped with
twelve Delta Data Terminals which are hardware wise
identical to those VDU installed in CAMPS and SCARS.
However, the terminals will be installed with floppy
discs and speciallly developed software for the MWHQ.
3.5 P̲o̲w̲e̲r̲ ̲S̲u̲p̲p̲l̲y̲
The MEDS Equipment offered by Christian Rovsing A/S
will operate at AC voltage limitation of 220 v + 10%/-6%
with a frequency of 50 Hz, (optionally 60Hz)+/- 0.5Hz.
The MEDS Equipment must be protected against super-positioned
peak voltages or any short time increase or interrupt
of voltage.
E̲l̲e̲c̲t̲r̲i̲c̲a̲l̲ ̲S̲a̲f̲e̲t̲y̲
TBD
4̲ ̲ ̲M̲E̲D̲S̲ ̲O̲P̲E̲R̲A̲T̲I̲O̲N̲
4.1 G̲e̲n̲e̲r̲a̲l̲
The MEDS can run in three different modes:
- standard operation
- operation without TARE
- special operations without TARE
- emergency operation
In each mode a distinction is made between incoming
and outgoing messages.
The three word processors, which control the flow of
incoming and outgoing messages, work completely independently,
i.e. one word processor can be allocated for any task
irrespective of what the other word processors are
doing.
The performance requirement imposed on MWHQ by the
external lines is 600 baud plus 6 times 50 bauds equivalent
to 900 bits per second or the double amount in cases
where two Crypto Shelters are attached to the same
Message Shelter. This amount of 2 kbit/sec per second
is far below the theoretical maximum of 1.8 Mbit/sec
of the TDX bus.
The traffic flow limitation for the MEDS will be the
human operator at the word processors: the flexible
TDX bus system can handle virtually any number of word
processors or other equipment attached.
4.2 S̲t̲a̲n̲d̲a̲r̲d̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
4.2.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲S̲t̲a̲n̲d̲a̲r̲d̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
An outgoing message will be generated/initiated on
one of the terminals in the Staff Element by a Staff
Officer. These terminals can accept messages in an
almost totally free format. In order that the MEDS
can automatically recognise the various priority
levels when storing messages on the floppy disc, strict
rules must be set up to indicate the priority level.
Likewise routines must be set up to handle all messages
with unrecognisable priority levels.
While the terminals can accept free format messages
AFCENT may establish procedural rules which will guide
the Staff Officers in generating messages that are
easier to transform to ACP-127 messages, thus easing
the burden of the word processor operators.
A message can be sent from one terminal to another
via the exchange in the Message Shelter without being
stored on the floppy disc system.
Each terminal will be provided with a Unique Software
Oriented Identification Code: This code be generated
by the Senior Officer into the message as a sign of
approval before it is sent to the next terminal for
approval and so forth. Eventually it arrives to the
floppy disc system with all its identification codes
for storage and further processing.
Outgoing message, that have just been transferred from
the Staff Element will be stored on disc number 1 and
2 of outgoing message storage. They are stored in
a queue structure, which contains one subqueue per
precedence level. A special subqueue may be allocated
for messages with unrecognisable precedence levels,
or these messages may be put in one of the existing
precedence queues. If a message of "flash" priority
is stored for further processing for transmission,
the word processor will give an acoustical warning
and a short text with a time indication will be displayed
in a special area of the word processors as an optical
warning.
The word processor will be a Delta Data T7260 TC Terminal
with special word processing software. It contains,
among other features, 16 splits which can be used for
various purposes. One split of 2 lines will be allocated
for the abovementioned optical warning of "flash" priority
message awaiting processing for transmission.
Each of the three word processors will be equipped
with two floppy disc stations, one containing programs
and the other containing various, often used ACP 127
parameters.
The word processor operator who is responsible for
outgoing messages will handle one message at a time.
The message with the highest priority will be handled
first, or if there are more messages with the same
precedance level, the oldest one will be handled.
It is the responsibility of the word processor operator
to transform the free format message entered by any
Staff Officer into a correct ACP 127 message. For this
transformation he will use the special software available
in the word processor.
The word processor can format the line length of a
message to maximum 69 characters per line (ACP-127
rule) and it can end each line at the end of a word
by a single command of the operator.
The word processor can also assist the operator in
the paging of a message. It is possible to store the
header line for each page under a special function
key, thus minimising the entry work for the operator.
The terminals will have an internal memory of 22,000
characters, allowing creation of large messages. In
order to manage these large data amount, the terminal
will be equipped with a scroll and page facility, making
the terminal screen a moveable window into the internal
memory.
The word processor operator will transform the message
into a correct ACP-127 message by using all the capabilities
of the terminal. As an example, the opertor can retrieve
the correct Plain Language, Address, PLA, and the
appropriate Routing Indicator RI, from the second floppy
disc station.
The word processor operator will insert or change the
priority indication in accordance with ACP-127. He
will also insert the date-time-group. Finally he will
retrieve the ACP-127 closing lines from the floppy
disc and insert them after the message, before pressing
the button for "transmission".
The message will be sent to three devices on the TDX-bus,
namely:
1) the Convertor in the Crypto-Shelter
2) the Printer for outgoing messages
3) Floppy Disc Station 3 or 4, allocated for storage
of the message for future interrogation by one
of the terminals in the Staff Element.
In the case of an identical message to more than one
destination, the operator will be able to combine the
addresses to have the message transmitted to all of
its destinations by a NATO TARE.
4.2.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲S̲t̲a̲n̲d̲a̲r̲d̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
In contrast to the standard procedure for outgoing
messages, which will transmit messages via a TARE only,
incoming messaages may enter the MEDS from a TARE as
well as from one of the six dedicated crypto-devices.
Messages can be received simultaneously on all crypto
devices in both the Main Element and the Leapfrog Element.
When incoming messages are transferred from the converter
to the TDX-bus in the Message Shelter, they are sent
to 2 devices:
1) the floppy disc station 1 or 2 for incoming messages.
2) the incoming message printer for printing.
Incoming messages will be stroed in accordance with
the indicated precedance level. If the precendance
level is not detectable by the floppy disc system,
the message will be stored in a queue for garbled messages
to be specially processed by the operator. An acoustical
and optical warning will be issued by the system to
alert the operator.
Please note that Christian Rovsing A/S has interpreted
the classification to mean precedance level and not
security level. However, we can implement it as security
classification if required by AFCENT.
One, two or three word processors can be used for processing
of incoming messages. The attached floppy disc stations
will be used as follows: number one contains Software
Programs for handling of incoming messages, while number
two contains Subject Indicator Codes, (SIC) and the
Associated Staff Cells. These SIC Codes can be updated
by the operators.
The operators of a word processor will retrieve incoming
messages from the floppy disc system in order of precedence.
He will locate the SIC code of the message and re-call
that SIC code with its Associated Staff Cells. Then
he will send a copy to each staff cell and the word
processor will delete the name of the staff cells,
one by one, each time the operator has sent a copy.
If a Staff Cell is busy, either preparing a message
or reading another newly received message, the word
Processor Operator will be notified by a warning and
the Staff Cell name will not be deleted.
Incoming messages requiring off-line decryption will
be addressed to the CEROFF-Shelter.
After distribution the message is transferred to disc
station 3 or 4 for incoming messages. From this disc
the Staff Cells can make interrogation and request
printed copies via a telephone call to a Message Shelter
Operator.
4.3 O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲
4.3.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲)̲
Message preparation and storage will be done as described
under standard operation.
When operating without TARE the Word Processor Operator
will insert the floppy disc for this type of operation,
one disc with programs and one disc with parameter
data.
The parameter data disc will contain data for the appropriate
ACP-127 opening lines for each possible recipient over
the dedicated lines, i.e. Plan Language Address(PLA),
Routing Indicator (RI) etc.
The following procedures are identical to operation
with TARE, except when identical messages are intended
for more than one destination. In this case the operator
will recall the message from the interrogation disc
and change the address before it is transmitted over
a new line. The changed version is stored separately
and printed on the printer for outgoing messages.
4.3.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲)̲
The only difference between this mode and the standard
mode for incoming messages is the absence of messages
from the TARE line. This will not cause any difference
in the required operator procedures.
4.4 S̲p̲e̲c̲i̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲
4.4.1 G̲e̲n̲e̲r̲a̲l̲
The flexibility of the TDX-bus system as a MEDS allows
AFCENT to reconfigure the MEDS in various respects
beneficial to AFCENT.
The XNP's interfacing the converter with the crypto
devices can also be used for interfaces one remote
convertor in the Leapfrog Element with the convertor
in the Main Element on a crypto secured line.
4.4.2 O̲u̲t̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲S̲p̲e̲c̲i̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲
Generation and storage of messages will be identical
to those procedures described in 4.2.1.
Because of the changed configuration, the disc file
containing parameter data has to be changed accordingly
before starting this mode. The senior system controller
shall decide which crypto line will be allocated to
connect the Leapfrog Element with the Main Element,
and the addresses to be reached by relaying messages
to the Leapfrog Element have to be entered on the parameter
data disc. This could be in the format "MEDS: normal
address".
All XNP interfacing the crypto devices will be able
to receive and monitor a status signal from the crypto
device. This can be used to give a warning to the
operator if the crypto device is not attached, and
it can prevent transmission of nonencrypted messages.
The handling of the relayed messages in the Main Element
will be similar to that of none relayed, but the operator
in the Leapfrog Element will remove the "MEDS"in the
address line and then transmit the message over the
appropriate line.
4.4.3 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲S̲p̲e̲c̲i̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲T̲A̲R̲E̲)̲
In the case of relayed messages, these will enter the
Main Element via a dedicated crypto line from the Leapfrog
Element which contains the address line: "MEDS: etc".
These messages will not be distributed locally, but
the operator will remove the text "MEDS": in the address
and put the message in the file for outgoing messages
to be processed as described in 4.4.2
4.5 U̲p̲d̲a̲t̲i̲n̲g̲ ̲o̲f̲ ̲L̲e̲a̲p̲f̲r̲o̲g̲ ̲M̲E̲&̲D̲S̲ ̲f̲o̲r̲ ̲R̲e̲-̲d̲e̲p̲l̲o̲y̲m̲e̲n̲t̲
4.5.1 G̲e̲n̲e̲r̲a̲l̲
In normal operation the MEDS in the Main Element functions
as an operational input/output message center of the
MWHQ, while the Leapfrog Element functions as a back
up or relay station.
During re-deployment of the MWHQ, the procedures for
the Main and the Leapfrog element will change. All
outgoing messages from the Main Element will be duplicated
and a copy will be transmitted to the Leapfrog MEDS.
Likewise, all incoming messages will be duplicated
and a copy transmitted to the Leapfrog Element.
As soon as the MEDS of the Leapfrog Element has been
made operational after installation on a new site,
the Leapfrog Element is ready to receive and transmit
messages.
If Staff Elements are not moved from the Main Element
to the Leapfrog Element before the Leapfrog Element
is operational again, messages for the concerned Staff
Cells can be transferred immediately to the Leapfrog
Element, awaiting the arrival of the Staff Cells. If
the Leapfrog Element is moved in the same time period
as some Staff Cells, then the duplication copy will
be kept in the Main Element until the Leapfrog Element
is operational. At that time a transfer of all the
copies intended for the Leapfrog Element can be started.
During the redeployment period, the dedicated crypto
lines will have their functions gradually changed,
i.e. the communication lines to SHAPE, 2ATAF, 4ATAF,
etc. will be moved one by one from the Main Element
to the Leapfrog Element. During this period messages
are duplicated to both the Main and the Leapfrog Element.
When all functions have been transferred to the Leapfrog
Element, it becomes the Main Element and the duplication
of messages stops.
4.5.2 S̲p̲e̲c̲i̲a̲l̲ ̲U̲p̲d̲a̲t̲i̲n̲g̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
It will be possible to let the two MEDS operate in
parallel, serving two groups of Staff Elements in a
coordinated way as described in 4.5.1.
In this case two crypto lines will be dedicated for
communication between the two MEDS. All communication
between the MEDS is done by operators in the Message
Shelters, and it is not possible for the users in the
Staff Elements of the two groups to communicate directly
with each other.
4.5.3 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲D̲u̲r̲i̲n̲g̲ ̲R̲e̲-̲d̲e̲p̲l̲o̲y̲m̲e̲n̲t̲
The generation of messages will be performed as during
normal operation, but the coordination of messages
might be different. If a certain Staff Cell is in transition
and cannot give approval to a generated message, the
Staff Element Commander shall decide whether the message
may be transmitted or not. In the first case the message
is transmitted and the duplication copy is sent to
the Leapfrog MEDS. In the second case the message is
transferred to the Leapfrog Element MEDS with the special
code: "MEDS:TRANSFER" in the message address line to
indicate that the message will have to be authorised
by a Staff Cell in the Leapfrog Element.
The Message storage of outgoing messages will be done
as described in 4.2.1, while outgoing message processing
will be somewhat different. The word processor operators
will have a special button marked "TRANSMISSION WITH
UPDATE" which will allow the operator to continue with
the various operation modes. By using the special button
the message will be transmitted on the appropriate
line and a copy will be sent to the Leapfrog Element
to be stored on the disc for interrogation by the terminals
on the Staff Element.
If the word processor operator recalls a message from
the outgoing floppy disc system with the address "MEDS:TRANSFER"
he will use the button "TRANSMISSION" when it is finally
sent out because a copy of the message already exists
on the MEDS in the other Element.
4.5.4 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲D̲u̲r̲i̲n̲g̲ ̲R̲e̲-̲d̲e̲p̲l̲o̲y̲m̲e̲n̲t̲
The procedures related to origin and storage of messages
of this type are identical to those earlier described,
but distribution procedures are different.
Messages with the identification "MEDS:TRANSFER will
be distributed for coordination to the appropriate
Staff Cell. However, the Staff Cell in question might
not have arrived at the site. This means that the message
has to be stored for later distribution. The message
queuing procedures of the floppy disc system will allow
messages to remain in the queue and be temporarily
bypassed by the operator. However, from time to time,
by either a floppy disc system parameter or an operator
procedure request, the non-delivered messages will
be presented to the operator for the attempt of a new
distribution. Only when all requested Staff Cell have
received their copy the message will be removed from
the queue.
4.6 N/A
4.7 E̲m̲e̲r̲g̲e̲n̲c̲y̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
Various emergency operation procedures are possible.
If the Message Shelter is not available, the teleprinters
in the Crypto Shelter and the CEROFF Shelter can be
used for message communication. This can be done by
interfacing the teleprinters to the crypto equipment.
4.8 T̲e̲r̲m̲i̲n̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
4.8.1 G̲e̲n̲e̲r̲a̲l̲
The Staff Element of the MWHQ will be equipped with
twelve Delta Data T7260TC terminals, each equipped
with one floppy disc station.
4.8.2 T̲e̲r̲m̲i̲n̲a̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Each terminal will be capable of fulfilling the following
functions:
- generation of messages
- receipt of messages
- message communication with other terminals
- interrogation with file of incoming messages
- interrogation with file of outgoing messages.
All the above functions will be supported by software
in the terminal. The terminal has a floppy disc attached
for the various loadable programs.
4.8.3 T̲e̲r̲m̲i̲n̲a̲l̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
All terminals will have a unique software generated
identification code which will be used by the exchange
for addressing the terminal in question. These codes
will be stored on the respective floppy disc as part
of the terminal software, one code on each disc. This
will prevent unauthorised personnel from using the
terminal.
4.8.4 T̲e̲r̲m̲i̲n̲a̲l̲ ̲U̲s̲e̲r̲ ̲A̲u̲t̲h̲o̲r̲i̲s̲a̲t̲i̲o̲n̲
Each user will have a personal floppy disc which will
be initialized by the senior systems operator. The
floppy disc will contain information about:
- the maximum classification to be handled by this
Staff Officer for transmission
- the maximum priority to be handled by this Staff
Officer for transmission
- a personal code name to be verified against the
code name entered by the user
- name and rank of the Staff Officer.
The terminal will periodically ask the user to enter
his personal code name to ensure that the actual user
is an authorised user.
4.8.5 G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The format for generation of messages shall be different
from the ACP-127 format in order to distinguish the
internal draft from the external ACP-127 format.
The user will initiate the generation of messages by
recalling the format to the screen. The first line
will contain the priority and the second line will
contain the security classification followed by the
actual message in a format different from ACP-127,
i.e. 80 characters per line, no page division with
DTG and channel designator, etc.
If the user is authorised to offer the message to the
MEDS for processing without asking for approval from
other Stall Cells, then he will give his name and rank
to close the message. The terminal will check the
entered name and rank against the floppy disc before
passing the message to the outgoing floppy disc system.
If the user needs approval from other Staff Cells the
message will be closed by a special closing line with
twelve positions, one position for each terminal.
The Staff Officer generating the message will insert
his own individual code in all the positions corresponding
to the terminals that have to give approval.
Approval will be given by replacing the code of the
generating terminal by the code of the terminal giving
authorisation. This code will always be linked with
the name and rank of the officer giving approval and
will always be checked against the similar codes on
the disc.
4.8.6 R̲e̲c̲e̲i̲p̲t̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
When a message is directed to a terminal from the exchange,
it will be stored in the memory of the terminal and
an acoustical and optical signal will indicate that
a message has arrived. A special warning including
several acoustical signals will be given when the message
is a "flash" message.
The staff officer will finish or interrupt the work
he is doing and recall the new message to the screen.
The message under preparation will be stored if sufficient
memory is available in the VDU. The Delta Data T7260C
contains a buffer area of 20,000 characters, allowing
storage of both an incoming and an outgoing message
of extensive length. Normal length of a message is
estimated to less than 2000 characters.
The user will be able to store the DTG of a message
on the floppy disc, but he will not be able to store
the actual message. If he wishes to have a printed
copy, he can ask the Message Shelter operator by telephone.
The operating system will allow a future inclusion
of printers in the Staff Office Shelters.
4.8.7 M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲ ̲O̲t̲h̲e̲r̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
It is not possible to transmit messages directly between
terminals in ACP-127 format. Messages for other terminals
shall have the special closing line as described in
4.8.5.
A terminal can receive incoming messages in ACP-127
format as well as in the internal format.
If a Staff Officer considers a message which he has
received to be interesting for another Staff Cell,
he can inform them by giving the DTG and the author
of the message by telephone to the appropriate Staff
Officer(s), who may recall it from the incoming message
file.
4.8.8 I̲n̲t̲e̲r̲r̲o̲g̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲F̲i̲l̲e̲ ̲w̲i̲t̲h̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The users can retrieve incoming messages from the disc
system by addressing the floppy disc system and indicating
the DTG and the author of the message. If the message
is not available on the floppy disc a warning will
be given to the user, who can request the Message Shelter
operator to insert the appropriate disc.
4.8.9 I̲n̲t̲e̲r̲r̲o̲g̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲F̲i̲l̲e̲ ̲w̲i̲t̲h̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Retrieval from this file can be done as with the incoming
file except that the user has to indicate DTG and address
of the requested message.
5̲ ̲ ̲I̲N̲S̲T̲A̲L̲L̲A̲T̲I̲O̲N̲ ̲M̲E̲D̲S̲
It has been agreed that Christian Rovsing A/S will
deliver the required MEDS equipment F.O.B. Huizen,
Netherland and that HSA/PAGE will be responsible for
installation. However, Christian Rovsing A/S is prepared
to perform the installation as an option as described
in the following
5.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
a) Subcontractor shall make the following major deliveries
to Maincontractor:
- Shelter Preparation Requirements
- Equipment Installation Drawings
- Delivery and Installation of Equipment
b) Shelter Preparation Requirements (SPR) shall specify
the extent of shelter preparation Maincon-
tractor must undertake before equipment is installed.
In order to generate the SPR, subcontractor will
conduct a Shelter Survey. Furthermore, SPR specify
division of responsibilities between maincontractor
and sub- contractor regarding installation.
d) Delivery and installaton of equipment will be performed
in accordance with the master schedule after subcontractor
has verified that the shelters have been prepared
in accordance with the Shelters Preparation Requirements.
Packaging of central equipment and peripherals
will correspond to requirements for air and truck
transport to the installation site.
5.2 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
a) The planning of the installation will start immediately
after contract award. The time span from contract
award to completion of installation will be divided
into major phases regarding installation planning:
1. Shelter Preparation
2. Shelter Installation
b) The main activities in plase 1 are:
1. Shelter surveys within two months after contract
award.
2. Preparation and delivery of site preparation
requirements 6 months prior to on-site installation.
3. Preparation and delivery of equipment installation
drawings 3 months prior to on-site installation.
4. Shelter readiness verification prior to start
of equipment installation.
The main activities in phase 2 are:
1. Transportation to site
2. On-site installation
3. Site acceptance
c) A more detailed description of the phase 1 and
2 activities is presented in the following sections.
5.2.1 S̲h̲e̲l̲t̲e̲r̲ ̲S̲u̲r̲v̲e̲y̲s̲
a) During the first 2 months after contract award,sub-
contractor will perform shelter surveys with maincontractor
participation. The purpose is to verify the shelter
information given in the invitation to tender and
to collect supplementary information. The results
of the survey will be used by subcontractor to
prepare shelter preparation requirements and plans
for on-site integration and installation.
b) An important task to be performed during the survey
meetings is to determine a tentative equipment
shelter layout.
c) Subcontractor will prepare a list of site documentation
(equipment shelter drawings and installations)
to be given to the subcontractor at the meeting
and submit it to maincontractor 2 months prior
to the site survey.
5.2.2 S̲h̲e̲l̲t̲e̲r̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
a) Subcontractor will prepare shelter preparation
requirements (SPR) concerning the preparation of
each site for installation of the proposed equipment.
The SPR will be submitted to maincon-
tractor for approval 6 months prior to start of
installation at each site.
b) The SPR will be based on the site data collected
during the site survey, the shelter layout and
the physical characteristics of the proposed equipment.
c) The SPR will contain requirements to access, space,
power, power distribution, quantity and location
of power outlets, heat dissipation, cable ducting,
etc.
d) Maincontractor will prepare the site for equipment
installation in accordance with these requirements.
5.2.3 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲D̲r̲a̲w̲i̲n̲g̲s̲
a) Subcontractor will deliver equipment installation
drawings to maincontractor for approval 3 months
prior to start of installation.
b) The approved installation drawings will be used
for the installation of the proposed equipment
into each shelter.
c) The equipment installation drawings will be based
on the approved shelter preparation requirements,
the hardware configuration, and the equipment characteristics.
d) The drawings will show how the proposed equipment
is to be installed and integrated, including detailed
cabling instruction.
A detailed list of checks to be carried out prior
to the application of power.
A detailed list of check-outs to be carried out
following the power-up procedure.
A list of tools and portable test equipment required
for installation and check-out of the equipment
5.2.4 S̲h̲e̲l̲t̲e̲r̲ ̲R̲e̲a̲d̲i̲n̲e̲s̲s̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) Prior to start of on-site installation, subcontractor
and maincontractor will jointly perform a shelter
verification.
b) The purpose is to verify that the shelters are
ready for installation, i.e. that the shelters
are prepared in accordance with the shelter preparation
requirements.
c) Final arrangements concerning transportation to
site and subcontractor's presence at site during
installation and test are also to be made at time
of site verification.
5.3 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
5.3.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲
a) The delivery of equipment will follow the master
schedule. Actual shipping dates are selected to
be in accordance with the readiness of site and
time for transportation.
b) The equipment will be shipped by air or truck and
packed accordingly. Subcontractor will try to arrange
the transportation so that his installation team
will be present at site for reception.
c) The packing and marking are proposed to be in accordance
with subcontractor's standard procedures for CR
equipment. The following is a brief discussion
of the method:
d) The computer equipment is constructed in a modular
fashion, i.e. 19" EMI stand alone racks containing
crate assemblies with plug-in modules. This is
reflected in the packaging as follows:
1) Modules are packed in styropor containers designed
to fit each module size. A number of modules
are put into a card board box or similar of
Europe pallet standard size (see figure 5.3-1).
2) Crates are packed with styropor corners so
that they fit into a card bord box of Europe
pallet standard size (see figure 5.3-2).
e) Packing lists are forwarded with every shipping
container. One copy of the packing list is enclosed
in the container; one copy will be attached to
the exterior of the container in an envelope clearly
marked "Packing List".
f) Each container is to be clearly marked on the exterior
surface with at least:
- purchaser identification
- manufacturer's name and address
- shipping address
In addition each container is clearly marked with
colli No. and precautionary markings applicable
to handling.
g) Since the shipping documents to be exchanged between
the two parties are to be defined, the following
is proposed:
- packing lists
- proforma invoice
- customs document
- bill of lading
5.3.2 S̲h̲e̲l̲t̲e̲r̲ ̲I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
a) Subcontractor will prepare internal shelter installation
procedures based on the shelter preparation requirements
and the equipment installation drawings. These
procedures will detail the installation sequence
and the installation check-out procedures.
b) Subcontractor will set up an installation team
to perform the installation. The team will be working
in accordance with the detailed installation procedures.
c) The team will install the equipment in accordance
with the maincontractor approved installation drawings.
Any changes during installation will be marked
on the drawings. Corrected drawing will be submitted
to customer after completion of site installation.
d) Major installation tasks will be:
C̲r̲y̲p̲t̲o̲ ̲S̲h̲e̲l̲t̲e̲r̲
Integration of Converter Rack.
Installation of I/F cables in maincontractor mounted
cable channels between Converter Rack and Red Patch
Panel.
Installation of V24 interconnection in maincontractor
mounted metallic conduit to message shelter.
M̲e̲s̲s̲a̲g̲e̲ ̲S̲h̲e̲l̲t̲e̲r̲
Integration of Exchange Racks I and II.
Installation of terminals (VDU and printers).
Installation of I/F cables in maincontractor mounted
cable channels between Exchange Racks I and II.
Installation of I/F cables in maincontractor mounted
cable channels between rack and terminals.
Installation of V24 interconnection from Crypto
Shelter to Exchange Rack I.
Installation of I/F cables from Exchange Rack II
to LTU.
C̲e̲r̲o̲f̲f̲ ̲S̲h̲e̲l̲t̲e̲r̲
Installation of Paper Tape Reader/Punch (PTR/PTP).
Installation of I/F cables in maincontractor mounted
cable channels from PTP/PTR to LTU.
S̲t̲a̲f̲f̲ ̲O̲f̲f̲i̲c̲e̲ ̲S̲h̲e̲l̲t̲e̲r̲
Installation of terminals (VDU).
T̲e̲s̲t̲
Complete test according to test specification document.
e) Installation check-out encompassing hardware verification
will be performed in accordance with an installation
check-out procedure. This task will complete the
installation and indicate the start of acceptance
test.
5.3.3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
Figure 5.3-1 shows the configuration of the Exchange
Rack I in the message shelter.
Figure 5.3-2 shows the configuration of the Exchange
Rack II in the message shelter.
Figure 5.3-3 shows the configuration of the converter
in the Crypto shelter.
For preliminary characteristics of subcontractor delivered
equipment please refer to table 5.3-1.
The integration of the subcontractor delivered equipment
will take place in the maincontractor delivered 19"
racks.
Front and side access to the racks used by subcontractor
is required as shown in figure 5.3-4.
Figure 5.3-1…01…Message Shelter…01…Exchange Rack I
Figure 5.3-2…01…Message Shelter…01…Exchange Rack II
Figure 5.3-3…01…Crypto Shelter…01…Converter Rack
Figure 5.3-4…01…Access Plan
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM DIMENSIONS WEIGHT POWER MAX
̲ ̲N̲O̲.̲ ̲ ̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲H̲x̲W̲x̲D̲ ̲(̲c̲m̲)̲ ̲ ̲ ̲ ̲ ̲K̲G̲ ̲ ̲ ̲ ̲ ̲C̲O̲N̲S̲U̲M̲P̲T̲I̲O̲N̲
̲(̲K̲W̲)̲
1 Exchange Rack I 70 0.50
2 Exchange Rack II 200 1.70
3 Converter Rack 90 0.65
4 PTP/PTR 20 x 64 x 64 42 0.23
5 DELTA VDU 43 x 76 x 48 45 0.20
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Table 5.3-1…01…Characteristics of…01…CR delivered Equipment
5.3.4 S̲y̲s̲t̲e̲m̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲
System acceptance is the act whereby maincontractor/
customer will acknowledge by protocol that CR has fully
demonstrated that the system is ready and complete
for operation and will take place when the following
requirements have been met:
- Completion of the agreed acceptance test as specified
in the Acceptance Test Procedures. The test will,
in case no real data is available, be performed
with simulated data and will constituted a relevant
subset of the Formal Factory Acceptance Test.
- Verification of the inventory.
- If applicable, availability of a mutually agreed
discrepancy list showing the agreed date for clearance
of each listed discrepancy.
6̲ ̲ ̲W̲O̲R̲D̲ ̲P̲R̲O̲C̲E̲S̲S̲O̲R̲
6.1 G̲e̲n̲e̲r̲a̲l̲
The MEDS of the MWHQ will be equipped with word processors
for the processing of outgoing and incoming messages.
Each Message Shelter will be equipped with three word
processors, which will be able to work independently
of each other in the various operating modes.
6.2 T̲y̲p̲e̲ ̲o̲f̲ ̲W̲o̲r̲d̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲s̲
The word processor for the MEDS will be based on Christian
Rovsing A/S CR8 microcomputer, which is implemented
on the same hardware as used in other components of
the MEDS, i.e. XNA network administrator in the exchange
and XNP network ports between the exchange and the
main bus as well as in the crypto converter.
The word processor will consist of a Delta Data T7260TC
VDU with two 8" floppy discs and the above mentioned
microcomputer.
6.3 M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲W̲o̲r̲d̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲f̲o̲r̲ ̲M̲W̲H̲Q̲ ̲U̲s̲e̲
The VDU of the word processor has already been tempest
cleared and approved by SHAPE COMSEC for NATO-use in
the CAMPS project. The word processor is well suited
for interfacing to the Message Shelter main bus system
and it has sufficient buffer memory to accommodate
a steady traffic flow between the word processor and
the TDX-bus system.
6.4 A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲
All new application software will be written in PASCAL,
while existing system software is implemented as firmware.
The supplied software will include standard software
like disk erasure, disk duplication and disk reconstruction.
A distinction will be made between various application
software for handling the following cases
- standard operation with outgoing messages
- operation without TARE with outgoing messages
- special operation without TARE with outgoing messages
- handling of incoming messages
- recalling messages and printing
These application programs will be stored on 8" program
disk to be used by the wordprocessor.
The wordprocessor can also initialize the 5"disk for
the Staff Officers, i.e. name, rank, authorization
and personal codeword.
Special software will exist on a separate disk to load
new software into the system.
7̲ ̲ ̲M̲E̲D̲S̲ ̲-̲ ̲B̲U̲S̲S̲Y̲S̲T̲E̲M̲
The TDX-Net is an efficient, fast digital link between
terminals (VDUs, printers etc.) and other terminals
or a number of small and large computers.
The TDX-Net consists of one controller, TDX-Net cable
and wall outlets.
The design has been especially aimed to ensure very
high immunity to electrical interferences and low generation
of interference itself. The TDX-Net can therefore safely
be used - instead of conventional data transmission
- in electrically noisy locations or where it is essential
to restrict radiated noise to a minimum.
Utilizing two screened twisted pair cables, one for
data transport to TDX-Net stations (lower bus) and
the other for data transport from the stations (upper
bus), data is transported in packets between TDX-Net.
The addressing scheme allows up to 254 stations to
share a single TDX-Net. This greatly reduces the number
of separate circuits required in many systems, so that
many large and expensive multicore cables can be replaced
by a single pair of cables.
Full packet protocol with error detection and correction
is implemented in TDX-Net for data integrity.
The unique addressing scheme allows multiple connections
between stations on a single TDX-Net as each station
comprises several datastreams distinguished by "Data
Type" (see 7.2). Furthermore multiple connections between
stations on different, interconnected TDX-Nets are
supported.
(figure)
7.1 S̲Y̲N̲C̲H̲R̲O̲N̲I̲Z̲A̲T̲I̲O̲N̲ ̲O̲F̲ ̲T̲D̲X̲-̲N̲E̲T̲ ̲T̲R̲A̲F̲F̲I̲C̲
The TDX-Net Controller outputs a continuous bit stream
of 1.8432 Mbit/sec on the lower bus. This stream is
divided into 6400 time slots of 288 bit each per second.
Each time slot on the lower bus contains a standard
HDLC frame with control information (5 bytes), DATA
to be transferred (16 bytes), and CCITT-16 (2 bytes)
cyclic redundancy check (CRC). The HDLC frame starts
at the beginning of a time slot and takes up maximally
236 bit of the 288 bit in the time slot, the remaining
bits being all "ONES" and from bit No. 240 all "ZERO'es".
The TDX-Net controller inserts as first byte in the
HDLC frame on the lower bus a unique address from a
MUX table (hereafter called MUX-No) which is scanned
according to the required bandwidth.
(figure)
All devices with their unique address on the TDX-Net
look at the MUX No., and if address and MUX-No are
identical this TDX-Net station has the use of the upper
bus to transmit data at the end of the frame on the
lower bus, provided that the lower bus CRC shows no
errors, thereby ensuring that only one device will
transmit on the upper bus at any time.
7.2 T̲D̲X̲-̲N̲e̲t̲ ̲F̲r̲a̲m̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲a̲n̲d̲ ̲A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲
The two TDX-Net frame formats are shown overleaf for
lower and upper bus. They only differ on two points,
namely that lower bus includes MUX No. M in its data
field, and upper bus has an ABORT byte (all ONE's)
as preamble.
Both upper and lower bus frames are standard HDLC FRAMES
with bitstuffing in order to have a unique synchronization
byte (FLAG: 01111110). Bitstuffing is done between
the beginning FLAG and ending FLAG, each time five
ONE's are met in the data stream, a zero is then removed
at receiving end, thereby restoring the original data.
The bit stuffing (depending on number of subsequent
ONE's in data stream) makes the length of frames variable
- on the lower bus between 200 and 236 bit, and on
the upper bus between 200 and 235 bits.
L̲O̲W̲E̲R̲ ̲B̲U̲S̲ ̲F̲O̲R̲M̲A̲T̲
Following the flag each byte has the following function:
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲1̲,̲ ̲M̲u̲x̲ ̲N̲o̲.̲ ̲M̲:̲
This byte is inserted by the TDX-Net Controller to
signal that the station with the unique address M is
to transmit on the upper bus at the end (actually at
bit count 241) of the frame on the lower bus.
TDX-Net…01…FRAME FORMAT
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲2̲ ̲a̲n̲d̲ ̲3̲ ̲(̲C̲R̲-̲I̲D̲)̲
Byte No. 2 and 3 are used in the addressing scheme
of the TDX-Net and they are named CR-ID (C̲hannel R̲outing
I̲dentifier).
Four different interconnections of TDX-Net Stations
are available.
a) From a Port or a Consumer Adapter to a Port or
Consumer Adapter. The CR-ID has the following format:
LSB MSB
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
d d d d h h h h t t t t t t t t
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
h: E*
d: Datatype (O-F)*
t: Address of destination Station
b) From a Port or a Consumer Adapter to a Super Port.
The CR-ID has the following format:
LSB MSB
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
d d d d h h h h t t t t t t t t
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
h: Super Port Address O-C* (Destination)
d: Datatype (O-F)*
t: Address of source Station
* Hexadecimal
c) From a Super Port to a Port or a Consumer Adapter.
The CR-ID has the following format:
LSB MSB
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
d d d d h h h h t t t t t t t t
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
h: F*
d: Datatype (O-F)*
t: Address of destination Station
d) From a Super Port to a Super Port. The CR-ID has
the following format:
LSB MSB
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
d d d d h h h h t t t t t t t t
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
h: Super Port Address O-C* (Destination)
d: Super Port Address O-C* (Source)
t: Datatype (O-F)*
* Hexadecimal
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲4̲,̲ ̲C̲O̲M̲M̲U̲N̲I̲C̲A̲T̲I̲O̲N̲ ̲B̲Y̲T̲E̲:̲
This byte is used for the TDX-Net Packet protocol control.
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲5̲,̲ ̲N̲o̲.̲ ̲O̲F̲ ̲D̲A̲T̲A̲ ̲B̲Y̲T̲E̲S̲ ̲I̲N̲ ̲F̲R̲A̲M̲E̲:̲
BITS 5-7: inserted by the originating station of the
frame to sequentially number frames, modulo 8 in a
communication with a specific receiving station, in
order that the receiving device can request retransmission
when a jump in SEQ. No. occurs. This is used for Error
Detection and Correction, as in the following example:
A CRC error occurred in frame with SEQ.No. n; this
frame was therefore thrown away by the receiving device.
At correct recieval of frame with SEQ. No. n+1, the
receiving device detects an increase in SEQ. No. of
2, from previous correctly received SEQ. No. n+1. The
Link-level of the receiving device accordingly requests
retransmission.
B̲I̲T̲S̲ ̲0̲-̲4̲:̲
As the number of bytes in the DATA field transmitted
is fixed at 16 (128 bits), the five least significant
bits of this byte indicate the number of actual DATA
bytes in a possible partly filled data field (hexadecimal:
00 - 10, decimal: 0 - 16)
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲6̲ ̲t̲o̲ ̲b̲y̲t̲e̲ ̲N̲o̲.̲ ̲2̲1̲,̲ ̲D̲A̲T̲A̲:̲
This is the information field containing data to be
communicated from originating station (source) to receiving
station (destination).
B̲y̲t̲e̲ ̲N̲o̲.̲ ̲2̲2̲ ̲&̲ ̲N̲o̲.̲ ̲2̲3̲,̲ ̲C̲R̲C̲:̲
The Cyclic Redundancy Check (CCITT-16) is inserted
by the originating station and utilized by the receiving
station to verify the correctness of the total received
frame.
T̲r̲a̲i̲l̲i̲n̲g̲ ̲"̲O̲N̲E̲"s̲ ̲a̲f̲t̲e̲r̲ ̲F̲r̲a̲m̲e̲
Following the frame, the controller inserts "I" until
bitcount of time slot reaches 241 and thereafter "0"
until end of time slot. The change from 1 to 0 is used
for starting transmission on the upper bus by the selected
TDX-Net station (MUX No.) at an exact point in the
time slot.
7.3 B̲a̲n̲d̲w̲i̲d̲t̲h̲
The Bandwidth allocated to each TDX-Net station is
dynamically changeable by requests from any TDX-Net
Station in the network. By a request about changed
bandwidth to a station, the TDX-Net Controller (XCT)
reconfigures the MUX-No table, whereby the required
bandwidth on the TDX-Net is achieved, provided the
total bandwidth of the TDX-Net is not exceeded.
7.4 P̲o̲w̲e̲r̲-̲u̲p̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲:̲
The TDX-Net is designed such that any components, including
the XNA, can be attached or dismounted, with no need
for a global power up. This is guaranteed by letting
the XNA continuously poll all devices, requesting their
internal status and delivering their link parameters.
7.5 T̲D̲X̲-̲N̲e̲t̲ ̲P̲R̲O̲T̲O̲C̲O̲L̲
The TDX-Net and the TDX-Net protocol described in this
chapter provides facility of high speed communication
among various kind of data communication equipment.
The architecture of the TDX-Net is in analogy with
the ISO Open System Model. The protocol implemented
on the TDX-Net is a packet protocol which is able to
transfer packets with sizes from 0 bytes to 64K bytes.
Data transferred are chopped into frames of 16 databytes
encapsulated with protocol information in a HDLC-frame.
The frames are decapsulated and collected via link-level,
which performs the error-detection and correction.
3 NETWORK LEVEL
2 LINK LEVEL
1 PHYSICAL LEVEL
(FRAME-LEVEL)
L̲O̲W̲E̲R̲ ̲L̲E̲V̲E̲L̲S̲ ̲O̲F̲ ̲T̲H̲E̲ ̲T̲D̲X̲-̲N̲E̲T̲ ̲P̲R̲O̲T̲O̲C̲O̲L̲
7.5.1 P̲h̲y̲s̲i̲c̲a̲l̲ ̲L̲e̲v̲e̲l̲ ̲(̲l̲e̲v̲e̲l̲ ̲1̲)̲
The communication medium of the TDX-Net is two shielded
twin-leaded cables. The interfaces to the cables are
a balanced split phase driver and a differential receiver.
The balanced split phase driver is capable of switching
12 volt over the transmission line load in less than
50ns.
The driver can be tristated against the twisted line
pair by the MOS switches at the output, showing an
impedance of 25K ohm in parallel with 50 pf for each
switch against the line at 10 Mhz.
F̲L̲O̲A̲T̲I̲N̲G̲ ̲T̲H̲R̲E̲E̲-̲S̲T̲A̲T̲E̲ ̲D̲R̲I̲V̲E̲R̲
The output of the driver is short circuit protected
by on-resistance of MOS switches, transformer core
characteristic and signals sensing circuit at the output.
The differential receiver has a worst case differential
mode switching band of +/- 120mV at twisted line side
of line transformer. Both driver and receiver circuits
are floating in relation to the TDX-Net cable, separated
by galvanic isolation, making the circuits withstanding
high common mode voltage pulses and DC voltages between
TDX-Net cable and local ground of attached devices.
The driver/receiver circuit is completely powered by
+ 5V and the transmitter is tristated against the TDX-Net
cable when no power is applied.
Conservatively specifying +/- 240mV as safe min. value
for switching of receiver (corresponding to 6 dB safety
factor) the maximum tolerable attenuation between driver
and receiver is:
̲1̲2̲ ̲
ATT = 20 log = 34dB
max 0.24
At 2 Mhz ( 1.8432 Mhz of bit clock) the attenuation
of:
TM3078 cable: 2.18dB/100m
RG 111 A/U or RG22 B/U cable: 1.3 dB/100m
RG 108 A/U cable: 3.2 dB/100m
…86…1 …02… …02… …02… …02… …02…
C̲l̲o̲c̲k̲ ̲E̲n̲c̲o̲d̲e̲r̲ ̲a̲n̲d̲ ̲D̲e̲c̲o̲d̲e̲r̲
Data and clock are communicated on the TDX-Net using
the self-clocking differential split phase code SPL-D.
SPL-D changes polarity at start of each bit cell, and
in the middle of bit cells to indicate a zero. This
allows data and clock to be transmitted via the same
set of wires. Phase ambiguity is solved by the decoder
when a "one" is inputdted.
Therefore, on the lower bus where SPL-D is continuously
transmitted, phase ambiguity is automatically solved.
On the upper bus, where transmission is discontinuous,
the ABORT byte (all ones) preceeding each frame solves
the phase ambiguity.
Transmitting clock together with data on the busses
have several advantages. The major one being that the
bus delay has no significance for the correct decoding
as clock and data are delayed equally. Also, no need
exists to synchronize a transmitter and receiver.
Also that the TDX-Net controller closk is continuously
transmitted on the lower bus makes this available to
all devices. One appliction for example being to use
this clock for modems attached to the TDX-Net thereby
eliminating the problem of modem clocks being slightly
out of phase, and the difference in transfer speed
is thereby slowly accumulating in data buffers until
overflow.
The following schematics show circuits and waveforms
of the SPL-D encoder and decoder.
FIGURE
FIGURE
F̲r̲a̲m̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
Transfer of frames between link-levels is carried out
by means of two procedures, which handle all communication
between the physical level and the link-level.
o T̲r̲a̲n̲s̲m̲i̲t̲t̲e̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
PROCEDURE T FRAME (INTEGER D,H,T,S,Z,W; STRING(16))
This procedure encapsulates data and protocol information
in a HDLC-frame and executes the transmissionn
to the network. All parameters are inserted by
higher levels and are declared as follows:
D,H,T is CR-ID(see 7.2)
S is link-protocol
header
Z is sequence no.
(0-7)
W is bytecount
STRING(16) is 16 databytes
of which some or
all may be dummy.
o R̲e̲c̲e̲i̲v̲e̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
PROCEDURE R FRAME (STRING(21))
This procedure receives and decapsulates all frames
transmitted in the network. If the first character
in the string is identical to the unique TDX-Net
device no. the transmitter procedure is allowed
to be executed. This character is inserted by the
controller and is called a MUX-No.
The CR-ID is used in the routing algorithm to select
the correct datastream in the next higher level.
7.5.2 L̲i̲n̲k̲ ̲L̲e̲v̲e̲l̲ ̲(̲l̲e̲v̲e̲l̲ ̲2̲)̲
The TDX-Net Link Level protocol controls the data traffic
on each datastream in the network. When data is delivered
from link level to higher levels, it is guaranteed
error-free by the CRC-16 bit check of the physical
level. The TDX-Net protocol is served autonomously
for at many data streams as set up by the packet level
(see 7.2)
N̲e̲t̲w̲o̲r̲k̲ ̲L̲e̲v̲e̲l̲ ̲t̲o̲ ̲L̲i̲n̲k̲ ̲L̲e̲v̲e̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The two primary services provided to the network level
by the data link level are transmission and reception
of data-packets. The network level uses these services
through a pair of routines: Transmit packet and Receive
packet. By call of the routines a reference to a data
buffer is made. The data link level returns a status
code in the data-bufferheader, which indicates if transmission/reception
is O.K. or an unrecoverable transmission error has
occurred.
The network level transmits a packet by calling:
T̲r̲a̲n̲s̲m̲i̲t̲p̲a̲c̲k̲e̲t̲ (LINE, BUFFADDR.)
LINE is a number, which identifies the logical
line.
BUFFADDR. is the address of a bufferheader, which
is associated with the databuffer containing
the packet to be transmitted.
The reception of a packet is enabled by calling:
R̲e̲c̲e̲i̲v̲e̲p̲a̲c̲k̲e̲t̲ (LINE, BUFFADDR.
LINE identifies the logical line by a number.
BUFFADDR. points at the bufferheader, which is associated
with the data buffer to contain the received
packet.
The packet level detects the completion of reception
or transmission by calling the two routines:
R̲e̲t̲u̲r̲n̲ ̲T̲ ̲B̲u̲f̲f̲e̲r̲ (LINE, BUFFADDR)
R̲e̲t̲u̲r̲n̲ ̲R̲ ̲B̲u̲f̲f̲e̲r̲ (LINE, BUFFADDR)
LINE is the identifying number of the logical
line.
BUFFADDR. is an output parameter, which refers to
the data buffer containing the packet.
In the bufferheader, a status-code indicates
either successful transmission/reception
or an error, which was unrecoverable by
the datalink level.
T̲D̲X̲-̲N̲e̲t̲ ̲L̲i̲n̲k̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The functions of the protocol is determined by two
state-event action diagrams. One for the routine that
receives data from the TDX-Net called the ingoing protocol
routine and the other which determines functions of
the outgoing protocol routine, which sends data to
the TDX-Net.
The smallest data unit the protocol works with, is
the TDX-Net frame. From a protocol point of view a
frame contains one protocol byte, a 3 bit sequence
number, a 5 bit byte count and between 0 and 16 data
bytes.
The logical data units of the protocol are called TDX-Net
packets. TDX-Net packets may contain data from several
TDX-Net frames. The size of a packet is determined
by the application programs in the outputting device.
To transmit a packet over the TDX-Net without error,
between two ready TDX-Net stations, packet control
and status information must be sent in both directions
of the TDX-Net connection.
For each packets there is an "outputter" at the end
of the link that originally had the packet and an "inputter"
at the other end that finally gets the packet. These
terms must be distinguished from "sender" and "receiver"
which are used in the conventional way to distinguish
the two ends of a single transmission, for a "control
byte" sent in one direction may contain information
about a packet output in the other direction.
T̲D̲X̲-̲N̲E̲T̲
P̲R̲O̲C̲O̲C̲O̲L̲ ̲-̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲F̲L̲O̲W̲ ̲T̲H̲R̲O̲U̲G̲H̲ ̲A̲ ̲T̲D̲X̲-̲N̲E̲T̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲
OUTPUT PHASE
OUTPUT STATE
OUTPUTTER 1 INPUTTER 1
INPUT PHASE
INPUT ACK/NAK
INPUT PERMIT
INPUTTER 2 OUTPUTTER
2
Because the link is full duplex (but not necessarily
the same speed in each direction) for output and input
as well as for sending and receiving, two packets may
be transmitted independently and simultaneously in
opposite directions over the link.
A p̲a̲c̲k̲e̲t̲ consists of one or more TDX-Net frames. The
frames within a packet is contiguously numbered modulo
8, starting with zero for the first frame in the packet.
The first and the last frame in the packet contains
a communication control byte (shown overleaf) with
"return to inputter valid bit" set which indicates
the begin and end of the packet (output state) as well
as the output phase (0 or 1) of the packet.
Completeness of a received packet is ensured by the
inputter through contiguous numbered (modulo 8) frames
between the first and the last frame in the packet.
All errors will result in frame being rejected at the
receiving station, errors are therefore detected by
the protocol by the following frame arriving out of
sequence (or time out, if last frame in packet), the
complete packet is rejected immediately (without waiting
for completion of packet) and retransmission requested
by replying NAK. The packet phase indicated in the
first and last frame of a packet is also checked, if
it is n+1 (modulo 2), where n was the last packet accepted
it is accepted via ACK. If it is n, it is accepted
via ACK, but it is thrown away by the inputter station
since it must have been a duplicate transmission caused
by an error in one of the acknowledgements.
ACK/NAK is transmitted by the inputter by setting the
"return to outputter valid bit" in the communication
control byte. The communication control byte is transmitted
either contained in a frame in a packet going from
the inputter (any frame (first, last or in the middle
of packet) as this have no influence on the validity
of the "return to inputter part" of comm. control byte)
or initiates sending of a frame, outside packets, containing
no data and which is discarded by the inputter except
for the content of the "return to outputter bits" of
the comm. control byte. This allows for immediate ACK/NAK
response by the inputter, to a packet received from
the outputter.
At the transmitter each acknowledgement is also checked
for errors, if erroneous it is thrown away, if error
free and ACK, then packet n+1 is transmitted, and if
NAK then packet n i retransmitted. A timer at the transmitter
initiates retransmission of packet n in case that neither
ACK nor NAK is received within a specified Ttime (e.g.
lost due to error of the link, transmission is attempted
3 times before the protocol gives up on output.
Provision is also included for transmission of short
packets in a single frame and for synchronizing packet
phase between both ends of the link.
P̲a̲c̲k̲e̲t̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲B̲y̲t̲e̲
Three of the eight bits in the control byte are input
status (bits 6, 5 and 4), valid content indicated by
bit 7 set, and three are output status (bits 2, 1 and
0) valid content indicated bit 4 set.
Bit 6, the input phase bit, and bit 2, the output phase
bit, indicate node phases. At any given time, a node
is in one of two phases (0 or 1) associated with input.
In each case, the phases alternate as successive packets
are transmitted. Change in a node's output phase occurs
whenever it sends a packet, while the input phase is
always made to conform to the output phase most recently
received (without error) from the other node. A phase
is essentially a modulo-2 packet counter (counting
0, 1, 0, 1, ...) used to prevent confusion about which
packet's status is being indicated.
The eight bits of a control byte are explained from
high to low order.
B̲i̲t̲ ̲7̲ - Return to outputter valid bit - when set indicates
valid content of bit 6, 5 & 4(Input status).
B̲i̲t̲ ̲6̲ - input-phase bit - indicates the input phase
of the sender.
B̲i̲t̲ ̲5̲ - input-acceptance bit - is set if, and only
if, the packet input by the sender during its current
input phase was accepted, that it was received without
error and forwarded for further processing according
at higher level protocols. A packet is received with
error if it is part of an erroneous transmission (a
transmission is judged to be erroneous and its contents
ignored if the frame protocol detects an error) or
is accompanied by an improper output state (defined
in discussion of bits 1 and 0).
B̲i̲t̲ ̲4̲ - input-permit bit - is set if, and only if,
the sender is prepared to input a new packet.
B̲i̲t̲ ̲3̲ - Return to inputter valid bit - when set indicates
valid content of bits 2, 1 & 0 (output status).
B̲i̲t̲ ̲2̲ - output-phase bit - indicates the output phase
of the sender.
B̲i̲t̲s̲ ̲1̲ ̲a̲n̲d̲ ̲0̲ - the output-state bits - indicate the
state of the sender with regard to output.
Output state = 00:
If the output-state bits are equal to 00, indicating
the RESET LINK state, the control byte accompanies
a single frame packet (frame seq.no. = 0), with or
without data. The purpose being to force synchronization
of the inputter phase to the phase of the outputter
(indicated in bit 2, Output phase bit).
The inputter will respond with ACK upon successful
reception and set its output phase to the opposite
of that received. In case of NAK or time out at the
Outputter (failure to receive ACK or NAK within a specified
time) retransmission is initiated up to three times
by the outputter.
Output state 00 is utilized either for initialization
of link or to check for input permission from the inputter.
Output state = 01:
If the output-state bits are equal to 01, indicating
that the control byte accompanies the first frame (frame
seq.no. = 0) in a packet consisting of two or more
frames.
The inputter checks that the control byte shows a change
in the sender's output phase from the previous successfully
received packet, which has been remembered as the receiver's
input state, if this is not the case, the receiver
responds with ACK (input acceptance bit 5 = 0) and
discards of the following frames until receiving a
new start of packet, as the packet start just received
must be part of a retransmission by the outputter due
to failure of receiving acknowledge (retransmission
initiated by "time out" at outputter) or an ACK erroneous
received as NAK.
TDX-NET…01…PACKET LEVEL PROTOCOL
In the following data frames (not containing a valid
"return to inputter" part in comm. control byte) until
receiving end of packet (output state 10), the inputter
check for contiguous frame sequence numbering (modulo
8), in case of out of seq. error the inputter responds
with NAK and discards of previously received data in
packet.
Output state 10:
If the output state bits are equal to 10, indicating
that the control byte accompanies the last frames,
the inputter checks that the control byte shows a change
in sender's output phase from previously successfully
received packet, if not response is ACK as for output
state 01 (packet start). If phase is changed from previous
received packet, inputter checks that the corresponding
packet start (output state 01) has been received and
that frame seq. no. has been incremented by one from
previous frame, if n̲o̲t̲ inputter responds with NAK,
otherwise ACK is returned to outputter to indicate
successful reception of packet and receiver changes
its input phase.
Output state 11:
If the output state bits are equal to 11, indicating
that the control byte accompanies a packet consisting
of a single frame, the inputter checks that the control
byte shows a change in sender's output phase from the
previous successfully received packet, which has been
remembered as the receiver's input state, if this is
not the case, the receiver responds with ACK, and discards
the data contained in frame (packet), as the packet
just received must be part of a retransmission due
to failure of acknowledge. If phase is changed from
previous received packet and frame seq. no. = 0 the
receiver responds with ACK to the outputter, to indicate
successful reception of packet and receiver changes
its input phase.
I̲n̲p̲u̲t̲t̲e̲r̲ ̲&̲ ̲O̲u̲t̲p̲u̲t̲t̲e̲r̲ ̲S̲t̲a̲t̲e̲ ̲D̲i̲a̲g̲r̲a̲m̲s̲
Find overleaf the state diagrams of the inputter and
outputter parts.
I̲N̲P̲U̲T̲T̲E̲R̲,̲ ̲S̲T̲A̲T̲E̲ ̲D̲I̲A̲G̲R̲A̲M̲
O̲U̲T̲P̲U̲T̲T̲E̲R̲,̲ ̲S̲T̲A̲T̲E̲ ̲D̲I̲A̲G̲R̲A̲M̲
7.5.3 N̲e̲t̲w̲o̲r̲k̲ ̲L̲e̲v̲e̲l̲
The primary service of the network level is to setup
datastreams between TDX-Net stations. The interface
through which the application level uses the facilities
of the network level consists of the routines: OPEN
and CLOSE. These routines respond with a status code
indicating if the operation succeeded or a failure
has occurred. The operations are synchroneous, in the
sense that each routine-call must be completed before
a new request may be served. The next higher level
sets up a line by calling:
OPEN (DEST, SOURCE)
DEST is the CR-ID of the remote end of the line:
SOURCE is the CR-ID of the local (subscribing) device:
A logical line is removed by application level by calling:
CLOSE (LINE), where
LINE is the number of the logical line.
Another service of the network level is to request
the TDX-Net Controller to change the bandwidth assigned
to the actual station on the TDX-Net. A request is
made by application level by calling:
REQBW (t, LEVEL), where
t: is the TDX-Net station device no. (0 to 255)
LEVEL is a number between 0 and 14, which represents
baudrates on:
0, 100 baud, 200 baud, 400 baud,..., 800K baud.
The network level responds with a status code indicating
if the request is accepted or rejected by the controller.
The network level carries out its services through
logical channel 0 for OPEN/CLOSE and channel 1 for
bandwidth requests. The channel 1 traffic is a point
to point connection between the actual device and the
TDX-Net controller, and is monitored by a subset of
the TDX-Net packet protocol. The communication on channel
0 may be shifting between the actual device and several
other TDX-Net stations, and is therefore supervised
by a Message Protocol.
A channel is setup by sending a datagram containing
the subscribing CR-ID and the remote CR-ID. The remote
device reassigns the CR-ID of channel 0, opens the
requested channel if it is free (closed) and responds
with a datagram containing the CR-ID of the new-opened
channel together with on ACK-status code. If the remote
requested channel is already open or under opening
a datagram containing an "Not-accepted"-status code
is responded.
7.5.4 B̲a̲n̲d̲w̲i̲d̲t̲h̲ ̲A̲l̲l̲o̲c̲a̲t̲i̲o̲n̲
The TDX-Net supports two different ways to request
new bandwidth to a device, either by request from the
application layer or automatic adaptive allocation
from the frame manager which requests bandwidth depending
of no. of frames queued waiting to be transmitted.
The two methods may be used mixed in a network configuration
as it is possible to lock and unlock the automatic
bandwidth request.
The automatic bandwidth allocation method requires
two parameters from higher levels indicating the maximal
and minimal bandwidths wanted on the device. These
parameters are used in the algorithm shown below.
(figure)
The improved requesting algorithm both supports very
strict requirements to allocated bandwidth as e.g.
synchronous encrypted modem connections and supports
extremely large virtual bandwidth in burst traffic
environment as typical in man-machine interface.
7.5.5 D̲i̲a̲g̲n̲o̲s̲t̲i̲c̲ ̲a̲n̲d̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲
System diagnostic consists of a low priority task in
the controller supervising all appended TDX-Net devices
with a frequency of typically a few devices per second.
Three requests from the controller not answered by
the device, results in an error-message to higher levels.
Furthermore a fast switching between optionally dualized
upper buses is implemented ensuring the best transmission
path is selected. The switching criteria is the ratio
of no. of valid frames in the network measured in two
consecutive comparable time intervals. If this ratio
is more than 4, a switch is executed.
Statistic and diagnostic information may be requested
from each TDX-Net device from higher levels via the
system communication on the TDX-Net. The information
received are the following:
o no. of transmitted packets
o no. of retransmitted packets
o no. of retransmissions exceeding 3
o no. of received packets
o no. of received timeouts
o identification of lower bus used to reception.
This information is available to the XNA (customized
version).
8̲ ̲ ̲M̲E̲D̲S̲ ̲F̲L̲O̲P̲P̲Y̲-̲D̲I̲S̲C̲ ̲S̲Y̲S̲T̲E̲M̲
The floppy disc systems will be controlled by the versatile
MP-sqare micro computer of Christian Rovsing A/S.
Each Message Shelters will be equipped with two 8"
floppy disc systems, each of which will be functionally
subdivided in 2 virtual systems in order to perform
the required functions.
In the following is given a description of the microcomputers
which controls the floppy disc system.
The Multi Purpose Multi Processor ((MP)square) specified
in this chapter is a high performance dual microcomputer
configured with a Multibus interface by which the module
may communicate with slavemodules as well as master
modules.
The two microcomputers are configured as general microcomputers
with common access to all on board in- output devices,
to the Multibus and to all on board memory, except
for that part of each processors memory being reserved
to contain its program code, which optionally can be
protected via the address decoder.
Both computers may be equipped with up to 64 K memory
(Dynamic RAM).
To obtain the highest degree of expandability the internal
bus structure ((MP)square Bus) is connected to three
36 pin on board connectors to which Multimodules and
CR custom interface modules may be plugged in.
To control the Multibus (MP)square Bus and its interfaces
a central Bus Control And Arbiter Logic is implemented.
A PROM area is interfaced to the (MP)…0e…2…0f… Bus. This area
is normally only accessed during a boot load procedure
or after a system-reset when the programs for built-in-
-test are accessed. This PROM area is 4K Byte Bus is
extendable to 64K by use of a small on board extension
board.
FIGURE
8.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲u̲m̲m̲a̲r̲y̲
This brief functional description is based on the block
diagram on fig. 2. The description handles only special
interfaces and conditions as the (MP)square is designed
to be a simple general microcomputer with birectional
access to a common bus system. All referred circuits
are implied to be wellknown by the reader and only
the HW interfaces and the addresses are included in
this document.
The real performance of this module will not be obtained
without an operating system controlling the interface
between the two systems and the use of all common addressable
devices as the DMA, the MAP register etc. by f.x. semaphore
protection technics.
8.2 B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Fig. 2 shows the (MP)square Block Diagram containing
common internal busstructure called (MP)square Bus
interfacing to the following logic functions:
o Main Processor
o Front Processor
o Multibus Interface
o Multimodule Interface
o Bus Arbiter & Control Logic
o Boot Load Prom
The following sections describe briefly the functions
and control of these logic blocks.
FIGURE
8.2.1 M̲a̲i̲n̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲
The Main Processor is a microcomputer with its own
local bus, 8 bit data bus and 20 bit address bus allowing
control of 1 MByte memory.
The Main Processor consists of a CPU (i8088), an interruptcontroller
(i8259), a 16/64K Ram-memory with parity control and
a (MP)square Bus interface. Refresh and control of
the memory is automatic generated by the Ram interface
circuit.
8.2.2 F̲r̲o̲n̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲
The Front Processor is a microcomputer with its own
local bus, 8 bit databus and 16 bit address bus extended
during global access with a 4 bit MAP-register.
The Front Processor consists of a CPU, a 16/64K RAM-memory
with parity control, a (MP)…0e…2…0f…-Bus interface, a timer,
a DMA and some in- output circuits.
8.2.3 F̲l̲o̲p̲p̲y̲ ̲D̲i̲s̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲l̲e̲r̲
A general floppy disc controller (WD 1797 or 1793)
has been implemented for accessing one to four single
or double density, single or double sided, 8" or 51/4"
floppy disc. drives.
The controller is connected to a DMA channel and to
an interrupt-input of the Front Processor which means
that data transfers are normally controlled by this
processor.
8.2.4 M̲u̲l̲t̲i̲b̲u̲s̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The structure of the Multibus is built upon the masterslave
concept where the master device in the system takes
control of the Multibus interface and the slave device
upon decoding its address, acts upon the command provided
by the master. Multimasters are allowed to interface
the Multibus, controlled by a simple arbitor/grant
technic.
The (MP)square Multibus interface is provided to act
as master or as an intelligent slave on the Multibus
addressing 1M byte on a 8-bit databus structure. The
interface is buffered and controlled according to the
multibus specifications. (sect. ??)
8.2.5 M̲u̲l̲t̲i̲m̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
On the (MP)square board three connectors are placed
for interfacing standard iSBX modules or special purpose/
function modules.
Each of the three connectors are addressed in a separate
I/O area of 16 consecutive addresses.
Interrupt request lines are connected to main processor
but DMA-request lines have no connection on the (MP)square-board.
8.2.6 B̲u̲s̲ ̲A̲r̲b̲i̲t̲e̲r̲ ̲&̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The (MP)square-bus includes an 8-bit databus, 20-bit
address bus and a control bus.
The interfaces to the bus are separated in the slave
interfaces (multimodule I/F) and the master/slave inter-
faces (Multibus I/F, Main Proc., Front Proc.)
Seen from the Bus-Arbiter and Control Logic there is
no difference between the three interfaces and the
complete function is issued by a state controller performing
a rotating access-priority scheme and a very fast arbitration
mechanism operating with the functions request/grant/release.
8.3 A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲
All new application software for the floppy disc system
will be made in PASCAL.
9̲ ̲ ̲M̲E̲D̲S̲ ̲P̲R̲I̲N̲T̲E̲R̲
The characteristics of the high speed printers to be
delivered for the MEDS is given in the following Data
Sheet.
DATASHEET FOR…01…MATRIX PRINTER CR 8333-/064--/00
1̲0̲ ̲ ̲M̲E̲D̲S̲ ̲C̲R̲Y̲P̲T̲O̲ ̲C̲O̲N̲V̲E̲R̲T̲E̲R̲S̲
The crypto converters will be build upon TDX-Net like
the Exchange and the Main Bus in the Message Shelters.
This will greatly simplify the operation of the MEDS,
i.e. spare parts, training and maintenance and give
higher flexibility for emergency situations.
For a detailed description, please refer to section
7.
The interfaces between the crypto convertor and the
crypto devices will be controlled by the XNP, TDX-network
ports, which are build upon a MP-square microcomputer
(refer section 8 for a detailed description). This
will allow a well-functioning interface. Christian
Rovsing has implemented similar microcomputers interfaces
towards BID 1000, BID 610 and KW7 in projects like
NICS TARE, CAMPS and FIKS, for transmission of ACP
127 messages.
No special buffer memory consideration are required
for the crypto converter, due to the high capacity
of the TDX-Net, i.e. 6 duplex 100 baud lines and 2
duplex 600 baud lines equals approximately 3600 bits/sec.
and the speed of the TDX-Net is approximately 2,000,000
bits/sec.
The Standard memory allocation, in excess of requirement
will be used to the ease development and maintenance.
The application software for the crypto converters
will be PASCAL in order to provide better documentation
and easier maintenance.
1̲1̲ ̲ ̲M̲E̲D̲S̲ ̲E̲X̲C̲H̲A̲N̲G̲E̲
The exchange of the Message Shelter will be build upon
the TDX-Net like the crypto converter and the Main
Bus.
For a detailed description, please refer to section
7.
The TDX-Net solution provides the capability to attach
a practical unlimited number of terminals.
1̲2̲ ̲ ̲M̲E̲D̲S̲ ̲T̲E̲R̲M̲I̲N̲A̲L̲S̲
The T 7260 TC Terminal is used in NATO projects like
CAMPS, SCARS, and FIKS, and we have seen it in new
NATO projects as NATO authorized single source procurement
equipment.
CR expects the T 7260 TC Terminal to become a NATO
standard.
The terminal will be equipped with an MP-square multiprocessor
to allow software development in PASCAL.
12.1 A̲L̲P̲H̲A̲N̲U̲M̲E̲R̲I̲C̲A̲L̲ ̲D̲I̲S̲P̲L̲A̲Y̲
a) E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The modified T 7260 TC Terminal can be used for
entry, display, and manipulation of data. It can
work on free format text as well as with formatted
data. It can also be interconnected to other devices
like floppy discs and hardcopy printers, which
can be controlled and supervised from the VDU.
The following main functions are available:
1) Data entry by the keyboard
2) Display of data on the screen
3) Miscellaneous text editing functions controlled
by special keys on the keyboard
- insertion of characters
- deletion of character, word, field, line,
to end of line, to end of split
- justification of text in connection with
insertion of new text in excess of line
length. The VDU can automatically move
entire words of the following lines as
a consequence of new text insertion.
- forward and backward paging and scrolling
over the entire memory area.
4) Keyboard controlled function calls
5) Tabulation, setting and deletion
6) Display of status in dedicated status line
7) S/W controlled acoustic signal
8) Access controlled by physical key
b) P̲h̲y̲s̲i̲c̲a̲l̲ ̲A̲p̲p̲e̲a̲r̲a̲n̲c̲e̲
The modified T 7260 TC Terminal comprises a screen
and a separate keyboard, which can be hooked on
the screen.
12.1.1 S̲C̲R̲E̲E̲N̲
a) T̲ ̲7̲2̲6̲0̲ ̲T̲C̲ ̲S̲c̲r̲e̲e̲n̲
The screen is used for display of alphanumerical
information. It includes the following functions:
1) Display of capital and small letters
2) Display of digits
3) Display of special signs
4) Display of various special characters
5) The modified T 7260 TC Terminal is configured
with the English alphabet.
6) The modified T 7260 TC Terminal has an all
caps function ensuring that all characters
will be entered as capitals, while other keys
act normal.
7) Various different attributes exist like inverse
video, half intensity and underline.
8) Individual characters can also appear blinking
on the screen.
9) 16 different split can be defined and used
for any purpose.
10) Cursor display type is setable to inverse video,
blinking and underscore, and is positioned
by S/W and keys.
11) Display attributes comprise three intensities,
full, half, and dark intensity.
b) T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲A̲p̲p̲e̲a̲r̲a̲n̲c̲e̲
The modified T 7260 TC Terminal is well suited
for installation on general tables or special dedicated
tables, which allow individual positioning of the
terminal.
The light intensity and the focus can be controlled.
The screen is a single colour green display screen.
The diagonal of the screen is approximately 30
cm and the screen contains 28 lines of 80 positions.
(1 line is used for terminal status display).
The character generation of the screen is based
on the matrix principle.
c) S̲p̲e̲c̲i̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The adjustable light intensity allows operation
in daylight as well as artificial light.
The modified T 7260 TC Terminal is TEMPEST CERTIFIED
in accordance with AMSG 720A and is suitable for
installation in accordance with the AMSG 719B.
The terminal has a BITE function as well as a setable
transmission speed (110-9600 baud). The character
set resides in memory and can be changed.
The terminal can operate with 220V and 50Hz in
a normal office environment and dissipates less
than 200W.
The terminal will have a V24 interface as standard,
but modifications can be introduced.
12.1.2 K̲E̲Y̲B̲O̲A̲R̲D̲
a) D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The keyboard of the modified T 7260 TC Terminal
is used for entry of alphanumeric information and
for control of any attached devices, e.g. hardcopy
printer. The capabilities comprise:
1) Entry of all possible data to be displayed
on the screen.
2) Special keys allow cursor movements up, down,
left, right and home (upper left corner). The
tab key is used for positioning of the cursor
in accordance with the tab-setting or the defined
data entry fields. A special key is used for
moving the cursor from one split to another.
3) The modified T 7260 TC Terminal has 36 programmable
keys. These can be set by the user.
4) The above mentioned function keys can also
be set by the host system.
5) The above mentioned function keys can be programmed
with sequence of keys, including other function
keys, but recursive calling of keys is not
allowed.
6) The modified T 7260 TC Terminal is equipped
with a numerical key-pad.
7) Text editor functions like search and replacement
of character strings are controlled by special
keys.
8) Functions like transmit, "all caps" and tab-setting
are controlled by keys.
9) Keys exist for printing hard copies on a printer
attached directly to the VDU, but some of the
programmable function keys can be used to request
hard copies on a printer attached to the host.
b) T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲A̲p̲p̲e̲a̲r̲a̲n̲c̲e̲
The keyboard is attached to the screen via a cable
which allows individual positioning of keyboard
and screen.
The alphanumerical keyboard is based on a typewriter
keyboard.
The layout of the key pads for programmable function
keys allows the utilization of user friendly instruction
plates.
The keys of the keyboards are either coloured in
various colours or grouped in various key pads
to make them distinguishable from each other.
A̲P̲P̲E̲N̲D̲I̲X̲
