top - download
⟦9a11b9e4c⟧ Wang Wps File
Length: 27827 (0x6cb3)
Types: Wang Wps File
Notes: VANDENBERG
Names: »4918A «
Derivation
└─⟦27551141f⟧ Bits:30006195 8" Wang WCS floppy, CR 0468A
└─ ⟦this⟧ »4918A «
WangText
. …86…1
…02…
…02…
…02…
…02…
…02…KNB/840516…02……02…#
VANDENBERG MESSAGE
SWITCH
…02……02… XFOX
1 SCOPE ..........................................
3
2 MESSAGE HANDLING ...............................
4
2.1 MESSAGE RECEPTION ..........................
10
2.1.1 Reception Procedures ...................
10
2.1.2 Analysis Procedures ....................
10
2.2 SERVICE MESSAGES ...........................
11
2.3 FLASH MESSAGES .............................
12
2.4 MESSAGE CORRECTION .........................
12
2.4.1 Message Service Operator (MSO) .........
12
2.4.2 Message Distribution Operator (MDCO) ...
15
2.5 MESSAGE DISTRIBUTION .......................
17
2.6 MESSAGE STORAGE AND RETRIEVAL ..............
18
2.7 MESSAGE PREPARATION ........................
21
2.8 MESSAGE RELEASE ............................
24
2.9 MESSAGE SYNTHESIS ..........................
24
2.9.1 Conversion Procedures ..................
25
2.9.2 Transmission Procedures ................
25
2.10 MESSAGE ROUTING ..........................
26
2.10.1 Completed Routing ....................
26
2.10.2 Selective Routing ....................
27
2.10.3 Routing Assistance ...................
27
2.11 MESSAGE QUEUES ...........................
28
2.12 COMMUNICATION MANAGEMENT .................
29
1̲ ̲ ̲S̲C̲O̲P̲E̲
The purpose of this document is to present a short-form
description of existing message switching facilities
developed by Christian Rovsing A/S, which with that
expierence in general can be recommended for use in
the future Vanderberg message switch.
The presentation will be based upon a walk through
the normal message handling functions associated with
processing of messages formatted in accordance with
the
ACP127 NATO Procedures and ACP126 (JANAP) Procedures.
The NASCOM message formats are very similar to the
ACP127 message formats, and the reader of this document
can therefore relate:
ACP127 to NASCOM, and
ACP126 to JANAP.
2̲ ̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲
This section describes the automated message handling
capabilities, which support exchange of information
via messages to and from the message switch over external
networks between national headquarters.
The system shall process two types of messages, which
are service messages dealing with communication related
activities and non-service (operational) messages containing
information pertinent to the message switch.
The Message Handling System described is already in
existance developed for NATO by Christian Rovsing A/S.
Christian Rovsing A/S intends to make the maximum use
of the existing software, which means more than 90&.
Furthermore, the system developed is very modular and
flexible, ensuring a low cost/risk in relation to further
expansion.
The system being developed for NATO is currently being
evaluated for level of security and the current status
is that the system is likely to be certified as a level
B3.
As examples of the provided message handling functions
the following diagrams represent the basic message
flow:
- incoming operational message (Fig. 2-1)
- incoming service message (Fig. 2-2)
- outgoing operational message (Fig. 2-3)
- outgoing service message (Fig. 2-4)
The symbolism of these diagrams is summarized and described
as below, and detailed in the following subsections.
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲
(See Figure 2-1)
1. Reception error detected.
Supervisor Report.
2. Incoming message for ACP ̲analysis.
3. Analysis errors detected.
Message Correction.
4. Reentering after correction.
5. ACP ̲analysis OK.
Flash message received.
6. Send Flash Acknowledge service message.
7. Distribute message.
8. Incoming Message Distribution.
b) I̲n̲c̲o̲m̲i̲n̲g̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲
(See Figure 2-2)
1. Command = open for incoming traffic.
2. Send Channel Open Service Message.
3. Report = Incoming Channel Opened.
4. Incoming message for ACP analysis.
5. Analysis OK
Service Message not recognized for automatic
handling.
c) O̲u̲t̲g̲o̲i̲n̲g̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲
(See Figure 2-3)
1. The prepared message is sent for release.
2. Distribution to the releasing officer.
3. Release OK.
Routing.
Conversation into Transmission Format.
4. Transmission.
5. Local distribution of outgoing message.
6. Individual deliveries to user positions.
d) O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲
(See Figure 2-4)
1. The prepared Service Message is sent for conversation.
Automatic Release.
2. Routing Error.
3. Another Routing Indicator Assigned.
4. Transmission.
Incoming Operational Message
- flash predence
- reception errors
Figure 2-1
Incoming Service Message
- open for traffic
- service message for supervisor
Figure 2-2
Outgoing operation message
- release
- transmission and local distribution
Figure 2-3
Outgoing Service Message
- RI ̲assignment
Figure 2-4
2.1 M̲E̲S̲S̲A̲G̲E̲ ̲R̲E̲C̲E̲P̲T̲I̲O̲N̲
The messages will be received as a stream of blocks
from for example the NICS TARE channels and a stream
of characters from the low-speed telegraph channels
(which if received in ITA2 code will be converted to
ITA5). The reception process handles the spooling of
these streams and turns them into discrete messages,
and files each message in its "as-received form" with
an attached unique message identifier. This process
will detect certain channel and message error conditions.
The reception processing is carried out by the Incoming
Transport depicted at Figure 2-1 to 2-4.
2.1.1 R̲E̲C̲E̲P̲T̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
The channel and message error conditions detected are:
- Too long lime (more than 69 char.)
- Oversized Message (more than 12.000 chars.)
- No EOTF detected before start of next message.
- Missing BT (only one text separator detected)
- Halted Message (premature termination)
- Preempted Message (ZHP detected)
- Transmission Identifier discontinuity.
During the assembling into a complete message, the
PAGE indicators are stripped (if any) facilitating
internal presentation using other paging principles.
2.1.2 A̲N̲A̲L̲Y̲S̲I̲S̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
Next the message will undertake an analysis to check
that the incoming message has been fully received in
accordance with the ACP127 or ACP126 construction rules.
(Ref. Analysis Figure 2-1 +2).
Due to security provisions it is required that all
messages contains format line 4 as a mandatory line
(contains message classification).
When text separators are used (e.g. "BT"s) it is required
that format line 5 is mandatory.
The functions of the Analysis Process are:
- message type determination
- (service or operational message)
- format line detection and validation
- internal format conversion
- detection of messages with a Pilot
- detection of a readdressed message
- detection of Service Messages for internal handling
(i.e. Channel Check, Channel Test and Flash Acknowledge.)
- consistency checks (i.e. Security-check)
Detailed procedures for ACP127 and ACP126 analysis
and NICS TARE Communication have been laid down into
Interface Control Documents which can be reviewed per
request to Christian Rovsing A/S.
2.2 S̲E̲R̲V̲I̲C̲E̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
Message flow diagrams figure 2-2 and 2-4 represent
the principle processing of an incoming service message
respectively a supervisory prepared outgoing message.
Two types of Service Messages are detected during ACP126
analysis:
- Abbreviated Plaindress Service Message
- Plaindress Service Message
Three types of Service Messages are detected during
ACP127 analysis:
- ASM (Simplified Service Message)
- Abbreviated Plaindress Service Message
- Plaindress Service Message
The ASM is characterized not having the text enveloped
with BT…08…s, the Abbreviated Plaindress does not contain
format lines 6 through 9.
All types of service messages are accepted as incoming
and can be prepared and transmitted from supervisory
positions.
Both incoming and outgoing service messages are logged.
2.3 F̲L̲A̲S̲H̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
See flow of an incoming flash message in figure 2-1.
The received flash message not containing the operating
signal ZGC in Format Line 4 is automatically acknowledged
by returning a Flash Acknowledge ASM to the originator.
In addition the message can be sent to a message service
operator for inspection with the notation FLASH INSPECTION.
During distribution of the flash message to a specified
user position, the ZZ-field of the status line will
be incremented as a discrete warning to the users,
that a flash message has arrived to his queue.
2.4 M̲E̲S̲S̲A̲G̲E̲ ̲C̲O̲R̲R̲E̲C̲T̲I̲O̲N̲
Errors, inconsistencies, garbles, channel faults and
messages which cannot be analyzed or distributed are
detected by the system and sent to the communication
personnel.
Two categories of operators are defined:
One is the Message Service Operator (MSO), who process
non valid, erroneous and garbled messages; the other
is the Message Distribution Operator (MDCO) who handles
distribution of all messages for which there is no
automatic distribution criteria.
2.4.1 M̲E̲S̲S̲A̲G̲E̲ ̲S̲E̲R̲V̲I̲C̲E̲ ̲O̲P̲E̲R̲A̲T̲O̲R̲ ̲(̲M̲S̲O̲)̲
Messages are sent to garble correction because of different
reasons. Main errors will be displayed in the system
line while detected analysis errors will be indicated
in the left hand margin area by error codes. The message
which needs garble correction will be presented on
the VDU screen in 3 parts:
- HEADING
- TEXT
- ENDING
See VDU screen layout figure 2.4.1-1
Fields within the format are unprotected and the user
will be able to modify and correct fields presented.
Main errors could occur due to one of the following
reasons:
- TOO LONG LINE
- NO EOTF
- MISSING BT (after the text)
- OVERSIZED MESSAGE
- HALTED MESSAGE
- UNIDENTIFIED MESSAGE
- ANALYSIS ERRORS
The main error displayed in the response line will
give an idea about what and where in the message format
the problem occurs.
Another mode of the Message Service Functions is the
Inspections:
- TI Inspection
- Pilot Inspection
- Flash Inspection
When the function is inspection, the Message Service
Operator cannot alter anything because all fields are
protected.
TI inspection is when some discrepancy or discontinuity
is found in the Transmission Identifies of format line
1 during Reception Procedures. If the Transmission
Serial Number as an example is equal to the one of
the last received messages, the now received message
might be a duplicate. The MSO has to be the judge of
this and reenter the message for continued ACP-analysis
is case the message is not a duplicate. The same is
the case for Pilot inspection, where the pilot is detected
during analysis.
Figure 2.4.1-1
2.4.2 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲(̲M̲D̲C̲O̲)̲
Messages are sent for "incoming message assistance"
because of the following reasons:
- Missing or garbled SICs
- Detection of special SICs (AAA, ABA or ADA)
- Detection of Internal Handling Instructions.
- Detection of Special Handling Instructions of categories
Exclusive or Crypto Security
- Detection of more than one Special Handling Instruction.
The annotation line will inform the MDCO why the message
is sent for assistance. Refer to figure 2.4.2-1 showing
the VDU screen layout.
The MDCO has the capability to specify for which terminal
(staff cells, SCD's) a distribution shall take place.
N̲O̲T̲E̲:̲
SIC is a subject indicator code used as distribution
criteria inside NATO. Other distribution criteria could
be Routing Indicator, Call Sign, Plain Language Addressee,
Address Group, Address Indicator Group and so on. The
message switch provided by CHRISTIAN ROVSING A/S can
be adjusted to any of above principles and others as
required.
Figure 2.4.2-1
2.5 M̲E̲S̲S̲A̲G̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲
Incoming non-service messages are after message analysis
and validation queued for internal distribution. The
distribution is based on the following information:
- The headquarters to which distribution shall be
performed at site
- Up to three subject indicator codes (SICs).
Each headquarter SIC combination will point out a standard
distribution list. From these lists the message distribution
process will generate a nominal distribution list.
After generation of the nominal distribution list,
the incoming messages are either distributed to the
staff cells in the list or queued for support by the
Message Distribution Officer (MDCO).
Incoming messages are deferred to the MDCO for the
following reasons:
- Missing or garbled SICs
- Special SICs
- Internal Handling Instructions
- Special Handling Instructions of category exclusive
or crypto security
- More than one Special Handling Instruction.
Outgoing messages are distributed by means of staff
cell designators specified by the message originator.
The delivery of messages to appropriate user terminals
will be performed by precedence queuing. Each transaction
is logged separately.
2.6 M̲E̲S̲S̲A̲G̲E̲ ̲S̲T̲O̲R̲A̲G̲E̲ ̲A̲N̲D̲ ̲R̲E̲T̲R̲I̲E̲V̲A̲L̲
The system has the capability to store all incoming
and outgoing messages in ACP127 or ACP126 format to
allow users to subsequently retrieve them as required.
Messages are stored on on-line as well as off-line
devices. Messages are kept on-line up to 30 days after
which they are dumped to off-line devices.
Messages are stored together with a number of retrieval
parameters which are time of occurrance, release DTG
(Date Time Group), originating headquarter, message
identification, channel identification, station serial
number, subject indicator code, Message Identification
and user code.
A Retrieval can take place by one or more of the above
retrieved parameters. In addition a time range for
the above parameters can be specified for which messages
shall be retrieved.
If more than one message meet the criteria, a retrieval
catalogue is presented, which refers to messages fitting
the key.
The user can, based on the catalogue display, select
the correct one.
Below is presented some examples of a retrieval formats,
one available to the user, the other available to the
system supervisor. (Figures 2.6-1 and 2.6-2).
Figure 2.6-1
Figure 2.6-2
2.7 M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲
See Message Flow diagrams Figure 2-3 and 2-4 for the
principle flow of an outgoing message.
The user has a number of terminal functions that support
preparation of messages and they are:
- Initial message preparation, supporting preparation
of message header and text according to ACP127
(i.e.NASCOM) and/or ACP126 (JANAP) format respectively.
- Message coordination sending a drafted message
to staff cells for coordination according to a
specified distribution
- Message comments providing the user with an electronic
mail capability for communication between terminals
within the headquarter.
- Datasets providing user defined predefined messages
where the construction is based upon DB information.
Before an outgoing message can be processed, the user
must ensure the completeness of the text of the message,
its addresses or RIs, security classification, precedence
etc. Message preparation is a general name for all
the processing involved in collecting this information.
The actual processes vary according to the type and
source of a message, but the end result will be a stored
message with an unique Message Identifier.
Messages are prepared via VDUs. This interactive preparation
process is controlled by the Terminal Pakcage. The
process involves:
1) Various methods of text preparation (VDU input,
appending texts of other messages, use of predefined
messages with validation of formatted data).
2) Validation of information to be used in the header
of the message (addresses, precedence, security
classifications).
3) Validation of message subject and distribution
information (SICs, exercise data, and local distribution
information).
4) Acceptance of instructions concerning the further
processing of the message (for example coordination
and release).
Messages can furthermore be entered into the system
via a Paper Tape Reader device.
Having prepared and coordinated a message the user
has to send it for release before conversion into ACP127
or ACP126 format and subsequent transmission.
See figure 2.7-1 for general preparation format.
Figure 2.7-1
2.8 M̲E̲S̲S̲A̲G̲E̲ ̲R̲E̲L̲E̲A̲S̲E̲
A message prepared via a VDU has to be presented to
an appropriate user/terminal for release. Release does
not alter a message, it allocates a release date-time
group (file time) and a station serial number to the
message. Release is an interactive transaction controlled
by the terminal package which has one of the following
results:
1) M̲e̲s̲s̲a̲g̲e̲ ̲r̲e̲l̲e̲a̲s̲e̲d̲
The message is queued for the ACP Synthesis Process.
2) R̲e̲l̲e̲a̲s̲e̲ ̲r̲e̲f̲u̲s̲e̲d̲
The Releaser sends an appropriate comment to the
user/terminal associated with the drafting of the
message.
3) R̲e̲l̲e̲a̲s̲e̲ ̲D̲e̲f̲e̲r̲r̲e̲d̲
The Releaser sends an appropriate comment to the
user/terminal associated with the drafting of the
message.
2.9 M̲E̲S̲S̲A̲G̲E̲ ̲S̲Y̲N̲T̲H̲E̲S̲I̲S̲
Much of the information needed for the ACP127/ACP126
header of a message is supplied during the various
message preparation functions. The ACP synthesis function
continues the build-up of this information.
The Station Serial Number (FL3), the filing time (FL3)
and the Data Time Group (FL5) is supplied at release
of the message.
The Routing Indicators (FL2) are selected automatically
during the following routing procedures (ref. description
2.10).
The remaining synthesis and formatting procedures are
provided as follows:
2.9.1 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The messages being prepared at terminals are stored
in an internal message format. After release of messages,
they are sent for ACP conversion.
The functions of ACP conversion are:
- Formatting of FL2 and FL3 of complete entered messages
- Formatting of Supervisor prepared Service Messages
- Conversion and formatting of user prepared messages
into complete ACP127 or ACP126 format applicable
for the transmission circuit
- Separation into sections if applicable for that
message
- Preparation of separate transmissions in case multiple
routes or limit exceeded on RIs
- Insert of ZEN in front of PLA's where multiple
routes are applicable.
The messages are after conversion forwarded to transmission
upon a channel indicated via the circuit selected under
Routing. A message containing Local PLA's will, however,
be directed for local distribution.
2.9.2 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of Transmission Procedures are:
- Formatting of FL1
- Formatting of Pilots upon automatic or Supervisor
initiated retransmissions (reruns)
- Preemption for transmission of flash message where
applicable
- Delivery of format-lines for transmission including
insertion of formal parameters
- A transmitted message will after successful transmission
be taken care of by the Transmission Control Procedures,
if the message shall be acknowledged.
2.10 M̲E̲S̲S̲A̲G̲E̲ ̲R̲O̲U̲T̲I̲N̲G̲
Routing of messages is performed after message release
and before completion of message synthesis.
The basic functions of routing are to select one or
more output-circuits upon which the messge or message
views shall be transmitted after conversion into the
applicable transmission format.
Two routing functions are provided
- completed routing
- selective routing.
2.10.1 C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲
The complete routing functions are to select circuits
for transmission based upon a list of RIs or call signs.
These RIs might have been derived through FL2 of a
complete entered message, assigned during Service Message
Prepare or assigned via RI-assignment procedures (MSO).
The message classification shall be compared with the
RI and circuit classification and the availability
of the pre-selected circuits shall be checked before
the message may continue for transmission.
Unknown RIs will result in RI assignment.
Misrouted and missent messages are detected during
ACP analysis (no local RI found/no local PLA found).
2.10.2 S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲
The subjects for selective Routing are locally prepared
messages of Plaindress type entered for conversion
first time (second time will be after RI-assignment
or for Rerun etc.).
The function is to select an RI for each PLA.
Up to 4 alternatives for selection of an RI may exist
for each PLA.
The following principles for selection of an RI will
be used:
a) The first RI with a classification higher than
or equal to the classification of the message will
be selected.
b) If the classification of the associated circuit
is lower than the classification of the RI a logical
error is found in the RI-table, a warning will
be sent to the supervisor printer and the next
RI will be selected.
c) If the circuit referenced via the RI is disconnected
or no channels are available upon that circuit
(closed), the next RI will be selected.
d) If no more RIs can be selected the message will
be rejected for RI-assignment with the last tested
RI (if any) as a suggestion.
If a "ZEN" is associated to the PLA, no RI will
be selected.
2.10.3 R̲o̲u̲t̲i̲n̲g̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
Manual Intervention might be needed for assignment
of alternative Routing Indicators in case
- the PLA is unknown
- the RI is unknown
- no circuit is assigned to the RI
- the classification of the RI is too low
- all channels associated to an output circuit has
been closed
The message is presented at a message service position
together with a Routing List where the RIs in question
are flagged with an explainable error code. The MSO
reenters the message for continued Routing and Conversion
after his assignments.
2.11 M̲E̲S̲S̲A̲G̲E̲ ̲Q̲U̲E̲U̲E̲S̲
Messages are handled according to precedence. The precedence
levels are FLASH, IMMEDIATE, PRIORITY and ROUTINE.
All system queues are implemented for these four precedence
levels.
The system will display queue status on the VDUs for
various system queues such as release queue, retrieval
queue and message presentation queue.
The user can get access to the messages displayed in
his queues by a "get message" function. Furthermore
he has the capability to delete or save a message,
which he has requested to get access to.
An example of the queues displayed at a message preparation
terminal is presented in figure 2.7-1 and further discussed
below.
The number of messages queued for the terminal by precedence
as well as those for coordination, release, display,
or response on a terminal will be shown. Each category
is identified by an aplha descriptor and the number
of items of this category in the terminal queue.
Queue information is updated every minute except when
FLASH messages are queued which causes immediate update
and a short audio alarm.
In the category "coordination" is contained the number
of messages for coordination.
In the category "release" is contained the number of
messages for release.
In the category "display" is contained the number of
incoming messages, comments, and outgoing messages.
In the category "response" is contained the number
of retrieved messages (from off-line database), append
notifications (off-line append), delete notifications
and release notifications.
2.12 C̲O̲M̲M̲U̲N̲I̲C̲A̲T̲I̲O̲N̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
The communication personnel has the capability to introduce/delete
channels/circuits/terminals to/from the system and
allocate physical devices over which these are operating.
Furthermore the communication personnel has the capability
to open and close channels or circuits to specify maximum
classification of message to be processed over the
channel/circuit and to manipulate queues by blocking/unblocking,
deletion or removal of messages contained in the queues.
Examples of these capabilities presented below by showing
the associated VDU display.
See figures 2.12-1, 2.12-2, and 2.12-3.
The system supervisor has the capability to update
Routing and Distribution Tables. Examples of tables
he can manipulate are:
- PLA Tables (Plain Language Address)
- AIG Tables (Address Indicator Group)
- RI Tables (Routing Indicator)
- SIC Tables (Subject Indicator Codes)
- SDL Tables (Standard Distribution List)
- SCD Tables (Staff Cell Designator)
- User/channel/terminal profiles.
The communication personnel has a number of functions
available to them which support:
- retransmission of messages
- rerouting of messages
- readdressal of messages
- preparation of service messages
In addition to the above communication procedures the
system automatically, without any involvement of communication
personnel, maintains communication with other systems
by sending abbreviated service messages related channel
open/close, channel continuity check, channel test
and flash receipt.
For all message transactions across channels or circuits
logging and statistics are maintained. They are available
on request by the system supervisor and/or communication
personnel.
Figure 2.12-1
Figure 2.12-2
Figure 2.12-3
