top - download
⟦773bc36fd⟧ Wang Wps File
Length: 65268 (0xfef4)
Types: Wang Wps File
Notes: TRAFFIC HANDLING SW PACK.
Names: »1031A «
Derivation
└─⟦2b76602a5⟧ Bits:30006036 8" Wang WCS floppy, CR 0060A
└─ ⟦this⟧ »1031A «
WangText
9…00……00……00……00…+…02……00……00…+
*…0b…*…02…)…08…)…0e…) (…0a…(…01…'…08…'…0e…' &…0c…&…01…& &…06…%…09…%…0b…%…0e…%…00…%…02…%…06…$…09…$…0d…$…0f…$…02…$…06…#…08…#…0a…#…0c…#…0f…#…01…#
#…05…#…07……86…1 …02… …02… …02…
…02…CPS/SDS/010
…02…KNB/810801…02……02…
TRAFFIC HANDLING
…02……02…CAMPS
4.2.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The structure of the ACP127 Analysis Subpackage is
of uncomplex nature. It is one process receiving
messages from the analysis Queue (ANQ) in an unlimited
loop.
The ANQ is organized on FIFO basis with one subqueue
for flash and one for non-flash, plus a command subqueue
to be used by SSC and TEP (reentering MSO). Because
paging and unpaging of messages in ACP127 format is
provided within the Transport Subpackage, this subpackage
will not need to examine the text part of a message
and will therefore have a good performance that will
be satisfied with the use of a FIFO-queue. If however,
these calculations should fail when coming to reality,
the Analysis Process can be implemented as two incarnated
coroutines.
The software structure of the analysis Process will
be described in detail in the following.
As reference to this description, the functional break
down in section 4.2.1.1, the HIPO-diagrams and Flowgrams
in section 4.2.1.3 will be used. Also this description
will expand these sections to some extent.
The functional break-downs depicted in figures 4.2.1.1-1
to 4.2.1.1-4 are kept on a level where the break-down
had stopped at a level ensuring that the lowest identified
software module did not exceed 250 SWELL statements.
Furthermore, the identified functions are arranged
in a logically correct order that satisfies a structured
allocation of software modules.
4.2.1.2.1 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲1̲.̲0̲)̲
This is the highest level module the function of which
is to:
a) receive queue-elements from the ANQ.
b) determine the originator of the message and based
upon this information initiate either the incoming
analysis, complete analysis or the PTR analysis.
c) when it gets control again, it will dismantle the
queue-element from the ANQ that triggers all during
the analysis sent message-views and commands to
be checkpointed.
d) before returning to the start-point it will send
a completion-code to the Incoming MSO command queue,
if these procedures had been involved.
4.2.1.2.2 L̲e̲v̲e̲l̲ ̲1̲ ̲M̲o̲d̲u̲l̲e̲s̲
The level 1 modules are the Incoming analysis, the
Complete analysis and the PTR analysis modules.
They will as input receive the information associated
to the message view and the queue-element (View-info
and Queue-info).
Their functions are to control the lower level modules
from where they receive control information that forms
the processing through that analysis.
4.2.1.2.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
On the basis of already existing information and information
supplied by the lower level modules (Info. Field, View
Info. and Queue Info.) this module will sequentially
activate the needed modules to fulfil an incoming analysis.
a) Initiate an incoming analysis:
- determine the message type
- set up pointers to the incoming analysis guide
table.
b) Determine if errors had occured during reception
of the message (Queue-Info.) and activate the Reception
Error Handling Module.
c) Activate the E1-analysis Control Module if the
message originator is CCIS or SCARS.
d) Activate the ACP127-analysis Control Module for
all messages except comments and VDU-pages.
e) Activate the Flash acknowledge module if the received
message is of precedence flash.
f) Activate the LOG, STP, and SAR module.
g) Activate the Internal Format Conversion Module.
h) Finally, it will activate the Finish Incoming Analysis
Module where the analyzed message and the results
of it will be directed to the various destinations
inside CAMPS.
4.2.1.2.2.2 C̲o̲m̲p̲l̲e̲t̲e̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲
The function of this module is the same as for the
Incoming Analysis Module; the difference is the start
and exit and that it controls fewer lower level modules.
a) Initiate the complete analysis.
- determine the message type
- set pointers to the complete analysis guide
table.
b) Activate the Complete Error Handling module if
an error-code is found in the queue-info.
c) Activate the ACP127-Analysis Control Module.
d) Activate the Internal Format Conversion Module.
e) Finally, it activates the Finish Complete Analysis
Module where the analyzed message will be directed
to ACP127 conversion or to the MSO for garble correction.
4.2.1.2.2.3 P̲T̲R̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲4̲.̲0̲)̲
Compared with the Complete Analysis Module, the difference
is the start, possibly the error handling and the exit.
The PTR analysis accomplishes the following:
a) Initiate the PTR analysis
- determine the message type
- set pointers to the PTR analysis guide table
b) Activate the PTR Error Handling Module if an error
is indicated in the Queue-info.
c) - e) as for complete analysis.
f) The final activity for the PTR analysis is either
to direct an outgoing message to conversion or
to MDP for internal distribution.
4.2.1.2.3 L̲e̲v̲e̲l̲ ̲2̲ ̲M̲o̲d̲u̲l̲e̲s̲
The level 2 modules are the modules activated by the
Incoming analysis, the Complete analysis and the PTR
analysis modules.
The major module in this complex is the ACP127 Control
Module that will be specifically described as this
module is common to the level 2 modules.
The module for Internal Format Conversion is also considered
a common module.
4.2.1.2.3.1 I̲n̲i̲t̲i̲a̲t̲e̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲2̲.̲1̲)
I̲n̲i̲t̲i̲a̲t̲e̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲3̲.̲1̲)̲
I̲n̲i̲t̲i̲a̲t̲e̲ ̲P̲T̲R̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲4̲.̲1̲)̲
Three modules with one common function:
- the Message Type Determination Module.
Otherwise, they will set up start values and pointers
to their respectively different analysis guide tables,
that form the principles for the following ACP127 Control
module.
This applies also for the Complete and the PTR Analysis.
For the Incoming Analysis, a message received from
SCARS or CCIS will be initiated an E1-analysis guide
table.
4.2.1.2.3.2 R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲2̲.̲2̲)̲
C̲o̲m̲p̲l̲e̲t̲e̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲3̲.̲2̲)̲
P̲T̲R̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲4̲.̲2̲)̲
Three Error Handling modules that will take action
upon an error condition occured and detected by the
Transport Subpackage.
At this stage of the design, the Error Handling Modules
are considered as different to the analysis-types,
but a close examination may show that this is one common
module. This will be clarified during detailed design.
Even if the Error Handling Modules are considered three
independent modules, it is assumed that they will handle
the same error characteristics:
- the halted message
- 140 identical characters
- oversized message
- too long lines
- preempted message
- too low TSN
Associated to Reception Error Handling is, that receipt
of a message with 140 identical characters may, depending
on a system parameter, result in a command to the Transport
Channel Command Queue (CCQ) to send an Identical Character
ASM.
The preempted message and the too low TSN condition
are assumed not to occur for messages entered via a
PTR or teleprinter operating as a PTR. If there should
be errors related specifically to PTR-input, these
types will be defined during detailed design.
4.2.1.2.3.3 E̲1̲-̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲3̲)̲
The operational description of this module is as for
the ACP127-analysis module (see 4.2.1.2.3.4).
Its function is to control the format line analysis
modules that will validate the specific E1-format lines:
1 = Analysis FL B
2 = Analysis FL C
3 = Analysis FL D1
4 = Analysis FL D2
5 = Analysis FL D3
6 = Analysis FL D4
7 = Analysis FL E
8 = Analysis FL J1
9 = Analysis FL J2
10 = Analysis FL J3
During the E1-analysis some message handling modules
may be activated.
1 = Garble Correction
2 = E1 Pilot Detect
3 = Released Message Handling
4 = Unreleased Message Handling
5 = Coordination Message Handling
6 = Comment Handling
7 = VDU-Page Handling
If the message type for E1-analysis is not of type
comment or VDU-Page, the Incoming Analysis Guide Table
will be initiated to continue the processing from FL5.
4.2.1.2.3.4 A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲)̲
This module is the most important module of the entire
ACP127-analysis. The principles for the very complex
analyzing logic has been centralized to this Control
Module.
In order to make this logic maintainable, it will operate
on the basis of an Analysis Guide Table (see section
4.2.1.4 for an example).
The principles are that the lower level analysis modules
will be used to determine if the specific Format-Line
is identical to the one activated via the table. Depending
on whether this is true or false, the next most possible
analysis target (Format-Line) will be selected.
Also depending upon false and true conditions, some
message handling modules might be activated during
that process.
This logic has been placed into the different analysis
guide tables, that also will contain a termination
code (-1), that may indicate a successful completed
analysis if no message handling case is associated
to it; otherwise this will indicate a garbled message,
where the format lines could not be detected, or it
could cause a break of the analysis (Pilot or Readdressal
Detect) until a new table entry is defined.
The Format Line Analysis Modules are:
1 = analysis FL1
2 = analysis FL2
3 = analysis FL3
4 = analysis FL4
5 = analysis FL5
6 = analysis Fl6
7 = analysis FL7
8 = analysis FL8
9 = analysis FL9
10 = analysis FL10
11 = analysis FL 1A (Pilot)
12 = analysis FL 4A (relay)
13 = analysis FL 12A
14 = analysis FL 12B
15 = analysis FL 12C
16 = analysis FL 12D
Input data to these modules are the previously analyzed
FL.
If these Format Line Control Modules detect a garbled
condition, they will report back to the ACP127 Analysis
Control Module, that independing upon the Analysis
Guide table step will cause a stop of the analysis.
The conditions under which a Format Line Control Module
will act like this will be specified during detailed
design. Normally they will only detect the format
line and update the Error-List and not cause a break.
The message handling modules that might be activated
during the analysis are:
1 = Garble Correction
2 = Pilot Detect
3 = Relaying
4 = ASM Handling
5 = Readdressal Detect
As an extra control function, the Field Control Module
is developed. It will normally set up pointers to
the next FL, but will also in case of Message Field
exchange perform a cross-reference between the next
available field and the next format-line to be analyzed
in order to detect and stop the analysis if this is
out of sequence. It will be defined during detailed
design whether this feature shall be implemented;
the negative side to this cross-check is that the analysis
guide tables become less flexible.
Finally having successfully completed the analysis,
the Consistency Control Module will be activated in
order to compare logically related data with each other.
(E.g. classification and classification word).
4.2.1.2.3.5 F̲l̲a̲s̲h̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲5̲)̲
If the received message is of precedence flash, this
module will initiate a command to the Channel Command
Queue corresponding to the received incoming channel.
The serving coroutine will then create and transmit
the flash acknowledge to the originator of the flash
message.
4.2.1.2.3.6 L̲o̲g̲,̲ ̲S̲T̲P̲ ̲a̲n̲d̲ ̲S̲A̲R̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲6̲)̲
This module may turn out to be 4 modules with the following
responsibilities:
- Invalid Message Log
- Incoming Message Log
- Statistics Incoming Message
- Retrieval keys Incoming Message
If the message is successfully analyzed, the last three
cases are executed, otherwise only the invalid message
log and the statistics.
4.2.1.2.3.7 I̲n̲t̲e̲r̲n̲a̲l̲ ̲F̲o̲r̲m̲a̲t̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲7̲)̲
The function of this module is to determine whether
some Internal Format Conversion will be needed for
that particular message type depending on whether it
is incoming or outgoing.
The decisions are as follows:
a) E̲r̲r̲o̲r̲-̲L̲i̲s̲t̲
The Format-Line Control Modules have collected
a sequence of buffered error-codes that now shall
be stored into an Error-List before the message
is forwarded to the MSO for Garble Correction.
b) R̲I̲-̲L̲i̲s̲t̲
A message is outgoing, and the routing indicators
buffered during analysis of FL2 shall be stored
into a RI-List to be used by the ACP127 Conversion
Subpackage for Routing.
c) P̲L̲A̲-̲L̲i̲s̲t̲
A released message received from SCARS or CCIS
is assumed not having been assigned any RIs. During
analysis of FL 7-9, a list of PLA RIs had been
created for validation purposes. This buffered
list shall now be stored to be used by the ACP127
Conversion Subpackage when creating a Selective
RI-List.
d) H̲e̲a̲d̲-̲3̲ ̲F̲i̲e̲l̲d̲ ̲w̲i̲t̲h̲o̲u̲t̲ ̲R̲I̲s̲
The message type is Plaindress or Data message
and it is incoming.
A version of the Head-3 Field with addressees not
preceded of RIs shall therefore be created in order
to complete the message view in format E1.
e) H̲Q̲/̲S̲I̲C̲ ̲L̲i̲s̲t̲
Same criterias as under d). Message Distribution
Package will need the results of the analysis related
to local HQs and SICs in order to distribute the
message.
4.2.1.2.3.8 F̲i̲n̲i̲s̲h̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲2̲.̲8̲)̲
F̲i̲n̲i̲s̲h̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲3̲.̲3̲)̲
F̲i̲n̲i̲s̲h̲ ̲P̲T̲R̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲(̲4̲.̲3̲)̲
The description of these modules is as described in
section 4.2.1.1 under functional specifications and
will not be repeated here.
The following is however to be added: If a message
of precedence flash is to be directed to a PTP for
off-line encryption, a command will also be forwarded
to the PTP command queue in order to determine preemption.
This facility will be implemented in a similar manner
in the interface to the Terminal Package.
If a message has been directed to a Message Service
Position for Garble Correction etc., the re-entered
message will pass through the very same analysis part
(e.g. the Incoming Analysis) and in case of another
erroneous analysis be directed to the same MSO position
for further corrections.
4.2.1.2.4 L̲e̲v̲e̲l̲ ̲3̲ ̲M̲o̲d̲u̲l̲e̲s̲
To this stage all modules have either been described
or mentioned. The level 3 modules are mainly of the
last category belonging to the Format Line Analysis
and Message Handling Group.
Except from the following most interesting modules
they will all be described under detailed design.
4.2.1.2.4.1 M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲ ̲D̲e̲t̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
This module is common to/included into the Initiate
Analysis Modules.
It might be remarkable that an analysis starts with
a message type determination and not did this as a
result of the analysis.
The answer to this event is the Internal Format Organization
and the processing performed by the Incoming Transport
modules. These modules will collect the message parts
into different fields that will form a distinct pattern
that together with other during transport collected
data can be used to determine the message type. This
information is considered very valuable in order to
fulfil a perfect ACP127-analysis.
4.2.1.2.4.2 R̲e̲l̲a̲y̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲.̲2̲.̲3̲)̲
The relaying module will be activated after analysis
of FL 4A (relay instruction). As input it will receive
two RIs. The first RI is the one that shall be used
for relaying.
The second RI is the local RI that is responsible for
the relaying and will only be present if it shall not
receive a copy of the message. A new FL2 will be created
only containing the Relay-RI and the message will be
directed to a Circuit Queue for onward transmission.
The local RI will be flagged as such in the list of
local RIs that should receive a copy of the message.
The final determination as to whether the HQ related
to that local RI shall receive a copy of the message
will be handled by the create HQ/SIC module. Done
like this, it will satisfy more relayings in the same
message plus a normal situation where FL2 still contains
local RIs after execution of all relayings.
- the first without local copy
- the second with local copy
It is assumed that this case will never occur.
4.2.1.2.4.3 P̲i̲l̲o̲t̲ ̲D̲e̲t̲e̲c̲t̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲.̲2̲.̲2̲)̲
This module will be activated after analysis of FL
1A (pilot). At this point of the analysis, it is totally
clear that a message contains a pilot and not just
is incomplete due to a missing FL3.
If the message is incoming, the analysis will simply
stop at this point, and the message will be directed
to a Message Service Position with the notification
"Pilot Detected".
If however the incoming message had already been inspected
by MSO and now is reentered still preceded with the
pilot, the situation is different. (MSO could also
have removed the Pilot). In this case, the analysis
will be initiated to continue from FL3. The analysis
guide table will be flexible enough to handle this
situation.
A̲S̲M̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲.̲2̲.̲4̲)̲
This module might for functional reasons be separated
into additional submodules as depicted in the functional
break-down figure 4.2.1.1-5.
It will maintain the functions depicted in that figure:
- Determine the ASM-type, that shall be one of the
following if to be further processed by this module.
- Channel Number Reset
- Channel Check (selfaddressed)
- Channel Continuity
- Channel Test
- Channel Test Reply
- Channel Open
- Channel Close
- Flash Acknowledge
This module will not generate any reply to a received
ASM of above types, but report the event to the Transport
Control Subpackage, which will actually generate an
ASM as reply if required. This report may be supplied
with data that shall be used in that reply (e.g. ZBZ5
to a Channel Test).
4.2.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The following HIPO diagrams illustrate the DATA Flow
through this subpackage. All activities that have
been framed in the processing part, are the functions
as depicted in figures 4.2.1.1-1 to 4.2.1.1-5.
The Control Logic is shown in the FLOGRAMS that follow
the HIPOs. To some extent they supply each other.
- The HIPO illustrating the DATA FLOW.
- The FLOGRAM illustrating the Control Logic.
A̲C̲P̲ ̲1̲2̲7̲ ̲-̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲1̲.̲0̲)̲
START
LOOP:
RECEIVE QUEUE-EL FROM ANQ
ORIGINATOR DEDICATED PTR? P̲T̲R̲-̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲0̲)̲
ORIGINATOR PTR? COMPLETE-ANALYSIS (3.0)
I̲N̲C̲O̲M̲I̲N̲G̲-̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲0̲)̲
DISMANTLE QUEUE-EL ANQ
MESSAGE SERVICE AWAITING? SEND COMPLETION CODE
END LOOP
STOP
I̲N̲C̲O̲M̲I̲N̲G̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲0̲)̲
I̲N̲I̲T̲I̲A̲T̲E̲ ̲I̲N̲C̲O̲M̲I̲N̲G̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲1̲)̲
ERROR AT RECEPTION? R̲E̲C̲E̲P̲T̲I̲O̲N̲ ̲E̲R̲R̲O̲R̲ ̲(̲2̲.̲2̲)̲
SCARS/CCIS E1-FORMAT? E̲1̲-̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲3̲)̲
A̲C̲P̲ ̲1̲2̲7̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲4̲)̲
F̲L̲A̲S̲H̲?̲ ̲ ̲F̲L̲A̲S̲H̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲ ̲(̲2̲.̲5̲)̲
INVALID MESSAGE? LOG INVALID MESSAGE (2.6.1)
LOG INCOMING MESSAGE (2.6.2)
RETRIEVAL KEYS INCOMING MESSAGE (2.6.4)
STATISTICS INCOMING MESSAGE (2.6.3)
I̲N̲T̲E̲R̲N̲A̲L̲ ̲F̲O̲R̲M̲A̲L̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲(̲2̲.̲7̲)̲
F̲I̲N̲I̲S̲H̲ ̲I̲N̲C̲O̲M̲I̲N̲G̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲8̲)̲
RETURN
I̲N̲I̲T̲I̲A̲T̲E̲ ̲I̲N̲C̲O̲M̲I̲N̲G̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲1̲)̲
READ HEAD-1
SET PREVIOUS FORMAT-LINE = 0
SET NEXT FORMAT-LINE = 1
SCARS/CCIS E1 FORMAT? START-ENTRY = E1 GUIDE TABLE
START-ENTRY = INCOMING ANALYSIS GUIDE TABLE
MESSAGE TYPE DETERMINATION (2.1.1)
ILLEGAL MESSAGE? SET FLAG = ILLEGAL MESSAGE
RETURN
M̲E̲S̲S̲A̲G̲E̲ ̲T̲Y̲P̲E̲ ̲D̲E̲T̲E̲R̲M̲I̲N̲A̲T̲I̲O̲N̲ ̲(̲2̲.̲1̲.̲1̲)̲
GET MESSAGE-VIEW
COMMENT
OR HEAD-1 AND TEXT-1?
VDU-PAGE
HEAD-1
SPECIAL HANDLING = HEAD-2 DATA MESSAGE
DDDDD? HEAD-3
TEXT-1
HEAD-1
HEAD-3? HEAD-2 GROUP COUNT? ENCRYPTED PLAINDRESS
HEAD-3
TEXT-1
PLAINDRESS
HEAD-1
GROUP COUNT? HEAD-2 CODRESS
TEXT-1
HEAD-1
HEAD-2 SERVICE MESSAGE
TEXT-1
HEAD-1 ABBREVIATED SERVICE MESSAGE
HEAD-2
SET FLAG = ILLEGAL MESSAGE TYPE
RETURN
R̲E̲C̲E̲P̲T̲I̲O̲N̲ ̲E̲R̲R̲O̲R̲ ̲(̲2̲.̲2̲)̲
CORRECTED BY MESSAGE SERVICE?
PREEMPTED MESSAGE?
140 IDENTICAL CHARACTERS? TEST SYSTEM-PARAMETERS
NO REPORT?
BUILD QUEUE-INFO
COMMAND = 140 IDENT. ASM
SEND COMMAND CHANNEL CONTROL
SET FLAG = INVALID MESSAGE
RETURN
E̲1̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲3̲)̲
LOCATE FIRST TABLE-ENTRY
LOOP:
TABLE-TYPE ? TYPE MESSAGE-TYPE? INC TABLE-ENTRY
E1-LINE-CONTROL = NEXT FORMAT-LINE
CASE E1-LINE-CONTROL (2.3.1) :
1 ANALYSIS FL B
2 ANALYSIS FL C
3 ANALYSIS FL D1
4 ANALYSIS FL D2
5 ANALYSIS FL D3
6 ANALYSIS FL D4
7 ANALYSIS FL E
8 ANALYSIS FL J
END E1-LINE-CONTROL
CONTINUE
CONTINUED E1 ANALYSIS CONTROL
TRUE FORMAT-LINE? CASE-TRUE = ?
E1-HANDLING = CASE-TRUE
CASE-FALSE = ?
E1-HANDLING = CASE-FALSE
CASE E1-HANDLING (2.3.2)
1 GARBLE CORRECTION (2.4.2.1)
2 RELEASED MESSAGE (2.3.2.2)
3 MESSAGE FOR RELEASE (2.3.2.3)
4 MESSAGE FOR COORDINATION (2.3.2.4)
5 VDU-PAGE (2.3.2.5)
6 COMMENT (2.3.2.6)
7 E1-PILOT DETECT (2.3.2.1)
END E1-HANDLING CASE
STOP-VALUE = -1? EXIT LOOP
FALSE FORMAT-LINE? TABLE-ENTRY = STEP FALSE
TABLE-ENTRY = STEP TRUE
PREVIOUS FORMAT-LINE = E1-LINE-CONTROL
TABLE-ENTRY = -1? COMMENT OR VDU-PAGE? EXIT LOOP
START-ENTRY = INCOMING GUIDE
TABLE
MESSAGE FIELD CONTROL
(2.4.3)
PREVIOUS FORMAT-LINE = 4
NEXT FORMAT-LINE = 5, EXIT
LOOP
END LOOP
RETURN
A̲C̲P̲ ̲1̲2̲7̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲4̲)̲
LOCATE FIRST TABLE-ENTRY
LOOP:
STOP-VALUE = - 1 EXIT LOOP
TABLE-TYPE ? TYPE MESSAGE TYPE? INC TABLE-ENTRY
FORMAT-LINE-CONTROL = NEXT FORMAT-LINE
CASE F̲O̲R̲M̲A̲T̲-̲L̲I̲N̲E̲-̲C̲O̲N̲T̲R̲O̲L̲ ̲ ̲(̲2̲.̲4̲.̲1̲)̲:
1 ANALYSIS FL1
2 ANALYSIS FL2
3 ANALYSIS FL3
4 ANALYSIS FL4
5 ANALYSIS FL5
6 ANALYSIS FL6
7 ANALYSIS FL7
8 ANALYSIS FL8
9 ANALYSIS FL9
10 ANALYSIS FL10
11 ANALYSIS FL 1A
12 ANALYSIS FL 4A
13 ANALYSIS FL 12A
14 ANALYSIS FL 12B
15 ANALYSIS FL 12C
16 ANALYSIS FL 12D
END FORMAT-LINE-CONTROL CASE
CONTINUE
C̲O̲N̲T̲I̲N̲U̲E̲D̲ ̲A̲C̲P̲1̲2̲7̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲
TRUE FORMAT-LINE? CASE-TRUE = ?
MESSAGE-HANDLING = CASE TRUE
CASE-FALSE = ?
MESSAGE-HANDLING = CASE FALSE
CASE M̲E̲S̲S̲A̲G̲E̲-̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲(̲2̲.̲4̲.̲2̲)̲
1 GARBLE CORRECTION (2.4.2.1)
2 P̲I̲L̲O̲T̲ ̲D̲E̲T̲E̲C̲T̲ ̲(̲2̲.̲4̲.̲2̲.̲2̲)̲
3 A̲S̲M̲-̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲(̲2̲.̲4̲.̲2̲.̲4̲)̲
4 R̲E̲L̲A̲Y̲I̲N̲G̲ ̲(̲2̲.̲4̲.̲2̲.̲3̲)̲
5 R̲E̲A̲D̲D̲R̲E̲S̲S̲A̲L̲ ̲D̲E̲T̲E̲C̲T̲ ̲(̲2̲.̲4̲.̲2̲.̲5̲)̲
6 Flag incoming message
7 Flag outgoing message
END MESSAGE-HANDLING CASE
STOP-VALUE = -1? EXIT LOOP
FALSE FORMAT-LINE? TABLE-ENTRY = STEP FALSE
TABLE ENTRY = STEP TRUE
PREVIOUS FORMAT-LINE = FORMAT-LINE-CONTROL
TABLE-ENTRY = -1? EXIT LOOP
MESSAGE FIELD CONTROL (2.4.3)
STOP-VALUE = -1? EXIT LOOP
END LOOP
CONSISTENCY CONTROL (2.4.4)
RETURN
P̲I̲L̲O̲T̲ ̲D̲E̲T̲E̲C̲T̲ ̲(̲2̲.̲4̲.̲2̲.̲2̲)̲
OUTGOING MESSAGE?
REENTERED FROM MSO?
GET QUEUE-ID MSO
QUEUE-INFO = "PILOT DETECT"
SEND MESSAGE-VIEW
SEPARATE PILOT FROM HEAD-1
STORE PILOT-FIELD
STORE NEW HEAD-1 FIELD
READ HEAD-2 FIELD
RETURN
A̲S̲M̲-̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲(̲2̲.̲4̲.̲2̲.̲4̲)̲
CHANNEL NUMBER RESET? GET CHANNEL-ID
GET ASSOCIATED CCQ
CHANNEL CONTINUITY? PREPARE CONTROL-COMMAND
CHANNEL OPEN? SEND COMMAND
CHANNEL CLOSE?
CHANNEL TEST? CORRECT QUALITY?
CONTROL-INFO = "ZBZ1"
CHANNEL TEST REPLY? ZBZ1?
CHANNEL CHECK? NOT SELF ORIGINATED?
FLASH ACKNOWLEDGE? GET CHANNEL-ID
GET ASSOCIATED CCQ/CIQ
CONTROL-INFO = ACK
SEND MESSAGE-VIEW
RETURN
R̲E̲L̲A̲Y̲I̲N̲G̲ ̲(̲2̲.̲4̲.̲2̲.̲5̲)̲
GET CIRCUIT ASSOCIATED TO RELAY-RI
IF NOT EXISTING
PREPARE NEW FL2
ASSIGN PRECEDENCE AND RELAY-RI TO FL2
PILOT DETECTED? LOCATE FL4
UNTIL END HEAD-1 DO:
APPEND LINE
READ NEXT LINE
END DO
CREATE NEW PILOT-FIELD
CREATE NEW HEAD-1
RI FOR LOCAL COPY? FLAG RI FOR LOCAL COPY
FLAG RI FOR NO LOCAL COPY
CHECK RELAY-RI SECURITY
CIRCUIT AVAILABILITY
AND CLASSIFICATION
OK? GET CIRCUIT-ID ASSOCIATED TO RELAY-RI
SEND RELAY MESSAGE-VIEW
MARK QUEUE-INFO "RELAY-ASSISTANCE"
MSO AWAITING? SELECT WAITING-QUEUE
SELECT MSO-QUEUE CLEAR COMPLETION-CODE
SEND MESSAGE VIEW FOR RELAY-ASSISTANCE
RETURN
M̲E̲S̲S̲A̲G̲E̲ ̲F̲I̲E̲L̲D̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲4̲.̲3̲)̲
MORE LINES BUFFERED? SET POINTERS NEXT LINE
NEXT = HEAD-2? NEXT-FL = FL 3? READ HEAD-2
NEXT = HEAD-3? NEXT-FL = FL 6? READ HEAD-3
NEXT = TEXT-1? NEXT-FL = FL12A? READ TEXT-1
COMMENT
OR NEXT = FLJ?
VDU-PAGE
GARBLE CORRECTION
SET FLAG = INVALID MESSAGE
SET STOP-VALUE = - 1
RETURN
I̲N̲T̲E̲R̲N̲A̲L̲ ̲F̲O̲R̲M̲A̲T̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲(̲2̲.̲7̲)
ERRORS DETECTED? CREATE ERROR-LIST (2.7.1)
SCARS/CCIS RELEASED MESSAGE? CREATE PLA-LIST (2.7.5)
OUTGOING MESSAGE? CREATE RI-LIST (2.7.2)
PLAINDRESS
OR CREATE HEAD-3 WITHOUT RIs (2.7.3)
DATA MESSAGE
CREATE HQ/SIC LIST
RETURN
F̲L̲A̲S̲H̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲ ̲(̲2̲.̲5̲)̲
PREEMPTED MESSAGE?
ZGC?
FLASH ACK ALREADY SENT?
READ CHANNEL-ID
GET ASSOCIATED CHANNEL-COMMAND-QUEUE
PREPARE QUEUE-INFO TO CCQ
SEND COMMAND
FLAG FLASH ACK SENT
RETURN
F̲I̲N̲I̲S̲H̲ ̲I̲N̲C̲O̲M̲I̲N̲G̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲2̲.̲8̲)̲
ALL MESSAGE-VIEWS SENT?
GARBLED MESSAGE? PRECEDENCE IMMEDIATE?
FL 12C NOT DETECTED?
SELECT DISTRIBUTION-QUEUE
MSO AWAITING? SELECT WAITING QUEUE
SELECT MSO-QUEUE
SCARS/CCIS RELEASED
OR SELECT CONVERSION-QUEUE
MSO FORCED OUTGOING?
MESSAGE FOR COORDINATION? SELECT RECEIVE-QUEUE
MESSAGE FOR RELEASE? SELECT RELEASE-QUEUE
CODRESS
OR SELECT PTR-QUEUE
ENCRYPTED PLAINDRESS
PLAINDRESS
OR SELECT DISTRIBUTION-QUEUE
DATA MESSAGE
SERVICE MESSAGE
OR SELECT SUPERVISOR-SVC-QUEUE
NOT ACCOUNTED ASM
SEND MESSAGE VIEW
RETURN…86…1 …02… …02… …02… …02… …02…
C̲O̲M̲P̲L̲E̲T̲E̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲3̲.̲0̲)̲
READ MESSAGE-VIEW
INITIATE COMPLETE ANALYSIS (3.1)
INPUT ERROR? COMPLETE ERROR (3.2)
ACP127 ANALYSIS CONTROL (2.4)
INTERNAL FORMAT CONVERSION (2.7)
FINISH COMPLETE ANALYSIS (3.3)
RETURN
I̲N̲I̲T̲I̲A̲T̲E̲ ̲C̲O̲M̲P̲L̲E̲T̲E̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲3̲.̲1̲)̲
READ HEAD-1
SET PREVIOUS FORMAT-LINE = 0
SET NEXT FORMAT-LINE = 1
START-ENTRY = COMPLETE ANALYSIS GUIDE TABLE
MESSAGE TYPE DETERMINATION (2.1.1)
ILLEGAL MESSAGE? SET FLAG = ILLEGAL MESSAGE
RETURN
F̲I̲N̲I̲S̲H̲ ̲C̲O̲M̲P̲L̲E̲T̲E̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲3̲.̲3̲)̲
GARBLED?
MSO AWAITING? SELECT WAITING-QUEUE
SELECT MSO-QUEUE
SELECT CONVERSION-QUEUE
SEND MESSAGE-VIEW
RETURN
P̲T̲R̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲0̲)̲
READ MESSAGE-VIEW
I̲N̲I̲T̲I̲A̲T̲E̲ ̲P̲T̲R̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲1̲)̲
INPUT ERROR? PTR ERROR (4.2)
A̲C̲P̲1̲2̲7̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲4̲)̲
I̲N̲T̲E̲R̲N̲A̲L̲ ̲F̲O̲R̲M̲A̲T̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲(̲2̲.̲7̲)̲
F̲I̲N̲I̲S̲H̲ ̲P̲T̲R̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲3̲)̲
RETURN
I̲N̲I̲T̲I̲A̲T̲E̲ ̲P̲T̲R̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲1̲)̲
READ HEAD-1
SET PREVIOUS FORMAT-LINE = 0
SET NEXT FORMAT-LINE = 1
START-ENTRY = PTR ANALYSIS GUIDE TABLE
MESSAGE TYPE DETERMINATION (2.1.1)
PLAINDRESS? CORRECT TO PLAINDRESS ENCRYPTED
SERVICE MESSAGE? CORRECT TO CODRESS
SET FLAG = ILLEGAL MESSAGE
RETURN
F̲I̲N̲I̲S̲H̲ ̲P̲T̲R̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲(̲4̲.̲3̲)̲
GARBLED MESSAGE?
OUTGOING ? SELECT CONVERSION QUEUE
MSO AWAITING? SELECT WAITING
QUEUE
SELECT MSO-QUEUE
RETRIEVAL KEYS INCOMING MESSAGE
SELECT DISTRIBUTION QUEUE
SEND MESSAGE-VIEW
RETURN
4.2.1.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
This section will define the major data-items that
are used during an analysis.
In this description they are all considered as buffers
even if they are named "List or Table".
4.2.1.4.1 A̲n̲a̲l̲y̲s̲i̲s̲ ̲G̲u̲i̲d̲e̲ ̲T̲a̲b̲l̲e̲s̲
Record Layout:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
MESSAGE PREV. NEXT STEP STEP CASE CASE
TYPE FL FL TRUE FALSE TRUE FALSE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 7 integers
Size: max. 200 records
Total: 2.800 Bytes
Message Type:
0 = all message types
1 = ASM
2 = Service Message
3 = Codress
4 = Encrypted Plaindress
5 = Plaindress
6 = Data Message
7 = Comment
8 = VDU-page
P̲r̲e̲v̲i̲o̲u̲s̲ ̲a̲n̲d̲ ̲n̲e̲x̲t̲ ̲F̲L̲
The number of the Format-Line Analysis module that
was previously activated respectively is to be activated
next (see 4.2.1.2.3.3 and 4.2.1.2.3.4 for number assignments).
S̲t̲e̲p̲ ̲t̲r̲u̲e̲/̲f̲a̲l̲s̲e̲
The next table entry to be used relative to the start
of this specific table. (-1 means stop analysis).
The condition true or false is control information
received from the Format Line Analysis of "NEXT FL".
C̲a̲s̲e̲ ̲t̲r̲u̲e̲/̲f̲a̲l̲s̲e̲
Corresponds to the Message Handling Case to be executed
before executing the indicated next table entry. (0
= no message handling case).
The message handling cases are numbered as shown in
4.2.1.2.3.3 and 4.2.1.2.3.4.
The Analysis Guide Tables shown in full at the next
pages are examples of:
- Incoming Analysis Guide Table and the PTR Analysis
Guide Table.
Incoming Analysis Guide Table I
Incoming Analysis Guide Table II
Incoming Analysis Guide Table III
PTR Analysis Guide Table I
PTR Analysis Guide Table II
4.2.1.4.2 A̲n̲a̲l̲y̲s̲i̲s̲ ̲B̲u̲f̲f̲e̲r̲
Size: 2048 Bytes
Contents: variable text.
This buffer is to be used during analysis of a message.
The intention is that it shall contain several Format
Lines to be analyzed in order to reduce disk-accesses.
The size might therefore be redefined later in the
design. At this level, it is estimated to contain
four sectors of data.
4.2.1.4.3 E̲r̲r̲o̲r̲ ̲L̲i̲s̲t̲
Record layout:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FIELD LINE NO. ERROR FROM TO
GROUP CODE POS. POS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 5 Integers
Size: max. 100 records
Total: 100 Bytes.
F̲i̲e̲l̲d̲ ̲G̲r̲o̲u̲p̲
The number of the Field-Group in which the error has
been located.
L̲i̲n̲e̲ ̲N̲o̲.̲
The Line number in that field group where the error
has been detected.
E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲
A code indicating the error type.
F̲r̲o̲m̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The position in that line (byte number) from where
the erroneous part starts.
T̲o̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The position in that line (byte number) where the erroneous
part ends.
4.2.1.4.4 R̲I̲-̲L̲i̲s̲t̲
Record Layout:
̲ ̲ ̲ ̲ ̲ ̲
RI
̲ ̲ ̲ ̲ ̲ ̲
Length: 9 bytes
Fill value: space
L̲O̲C̲A̲L̲ ̲R̲I̲-̲L̲i̲s̲t̲
Size: 8 records
N̲O̲T̲ ̲L̲O̲C̲A̲L̲ ̲R̲I̲-̲L̲i̲s̲t̲
Size: max. 250 records
R̲E̲L̲A̲Y̲ ̲R̲I̲-̲L̲i̲s̲t̲
Size: 2 records
TOTAL RI-LISTS = 2340 Bytes
4.2.1.4.5 H̲Q̲/̲S̲I̲C̲ ̲L̲i̲s̲t̲
Layout:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
LOCAL SICs
PLA REF
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 18 Bytes
L̲O̲C̲A̲L̲ ̲P̲L̲A̲ ̲R̲e̲f̲.̲
An organization of binary data. 1 word reserved for
that purpose.
Bit 1 set = local HQ no. 1
Bit 2 set = local HQ no. 2
etc.
S̲I̲C̲s̲
FL 12B except the parameter "SIC".
Fill value = space.
The Local PLA-REF will be transferred to MDP via a
word in the queue-info-field. The SICs will be stored
in the CIF-Info-field.
4.2.1.4.6 P̲L̲A̲-̲L̲i̲s̲t̲
Record layout:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PLA REF PLA ZEN LOCAL
CODE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: bytes
Size: max. 250 records
Total. 1000 bytes.
P̲L̲A̲ ̲R̲e̲f̲.̲ ̲#̲ ̲(̲1̲ ̲i̲n̲t̲e̲g̲e̲r̲)̲
The reference number in the PLA-table.
P̲L̲A̲ ̲C̲o̲d̲e̲ ̲(̲1̲ ̲b̲y̲t̲e̲)̲
0 = "X" = PLA
1 = Action PLA
2 = Action PLA from AIG
3 = Info PLA
4 = Info PLA from AIG
5 = XMT PLA
Z̲E̲N̲ (Boolean)
Indication of ZEN.
L̲o̲c̲a̲l̲
Indication for local PLA.
4.2.1.4.7 O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲s̲ ̲L̲i̲s̲t̲
Layout:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
OPERATING SIGNAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 4 bytes
Size: max. 12
Total: 48 bytes
O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲
Containing the operating signals located during analysis
FL4 and FL5.
4.2.1.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The environment of this subpackage is as depicted in
figure 4.2.1.5-1. This figure illustrates the other
subpackages of THP and Packages that this Subpackage
interfaces to.
The interfaces to system oriented Packages are described
in section 3.4.
Fig. 4.2.1.5-1…01…INTERFACES ACP127-ANALYSIS SUBPACKAGE
4.2.1.5.1 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The application Packages and Subpackages that the ACP127
Analysis Subpackage interfaces to are:
- Message Distribution Package (MDP)
- Terminal Package (TEP)
- Transport Subpackage (TRS)
- ACP127 Conversion Subpackage (ACS)
- Log Package (LOG)
- Statistics Package (STP)
- Storage and Retrieval (SAR)
4.2.1.5.1.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲
A̲A̲S̲ ̲t̲o̲ ̲M̲D̲P̲:
a) Plaindress or Data Messages for incoming message
distribution (Format E1).
4.2.1.5.1.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
A̲A̲S̲ ̲t̲o̲ ̲T̲E̲P̲:
a) Incoming Message Service assistance:
- Garble Correction
- Pilot Detect
- Relay Assistance
- Too low TSN
b) Abbreviated and normal Service Messages to Supervisor
Printer.
c) Comments and VDU-pages to be presented at a terminal
position.
d) Message for coordination to be viewed as a "Continue
Prepare" to a Prepare Position. (Receive-queue
for transfer to prepare-queue).
e) Message for Release to be presented for release
at a Release Position. The releaser will in this
case be viewed as the "preparer" of the message.
f) Message for Alternative Delivery to be presented
to the MDCO.
T̲E̲P̲ ̲t̲o̲ ̲A̲A̲S̲:
a) Messages reentered for analysis from an Incoming
Message Service Position. It may be indicated
whether the message has been corrected or not and
the function performed (the reason for MSO invocation)
b) Messages entered as readdressal from a Supervisor
Position.
4.2.1.5.1.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲R̲S̲
A̲A̲S̲ ̲t̲o̲ ̲T̲R̲S̲
a) Incoming Codress or Plaindress Encrypted Message
to be punched at the PTP.
b) Request for automatic generation and transmission
of:
- Flash Acknowledge ASM
- Channel Test Reply ASM
- Identical Character ASM
c) Request for transmission of.
- Incoming Selfaddressed Channel Check ASM on
the corresponding outgoing channel.
d) Notification followed by a message view in case
receipt of:
- Flash Acknowledge.
e) Notification in case receipt of:
- Outgoing selfaddressed Channel Check
- Channel Number Reset ASM
- Channel Close ASM
- Channel Open ASM
- Channel Test Reply ASM with ZBZ lower than
4.
f) Message for relaying, and messages for local distribution
SCARS/CCIS.
Channel Command Queue: b - d - e
Circuit Queue: a - c - f
If a message of precedence flash is queued to a Circuit
Queue a command indicating this event will be queued
to the corresponding Channel Command Queue (not NICS
TARE).
T̲R̲S̲ ̲t̲o̲ ̲A̲A̲S̲
a) Input of messages for ACP127 - analysis with an
originating source code:
- Incoming Analysis
- Complete Analysis
- PTR Analysis
The source code indicating:
- NICS TARE
- TRC/Point to point
- SCARS
- CCIS
- PTR (teleprinter)
- Dedicated PTR
b) Input of messages that have been automatically
terminated or detected as garbled during the incoming
transport.
- Halted message
- Preempted message
- Oversized message
- 140 identical consecutive characters
- too long lines
- expected TSN too low
An error-code indicated by a queue-info shall indicate
the error-type.
4.2.1.5.1.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲C̲S̲
A̲A̲S̲ ̲t̲o̲ ̲A̲C̲S̲
a) Released message in SCARS/CCIS E1 Format, that
shall be automatically released and converted into
ACP127-format before onward transmission. A PLA-List
will follow the message-view for generation of
a Selective Routing List.
b) Plaindress and Data messages entered as complete
messages from a PTR (teleprinter) for Routing and
onward transmission. A RI-List will follow the
message-view for routing purposes.
4.2.1.5.1.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲o̲g̲
a) Invalid message log.
b) Incoming message log.
4.2.1.5.1.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲T̲P̲
a) Statistics Incoming Message.
b) Statistics Incoming Invalid Message.
4.2.1.5.1.7 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲A̲R̲
Delivery of retrieval-keys associated to an incoming
message.
- Channel Identification (Ti)
- SSN + DTG
4.2.2 A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The ACP127 Conversion Subpackage receives messages
for routing and conversion from the Terminal Package,
the ACP127 analysis subpackage and the Transport Subpackage.
The nature of the routing and conversion subjects
received from above mentioned Packages and Subpackages
will be described in detail in section 4.2.2.5.
The functional Break-Down depicted in figures 4.2.2.1-1
to 4.2.2.1-4 describes the functions of this subpackage,
and the interrelationships between these.
The main functional components of this subpackage are:
- Routing
- ACP127 Formatting
- Traffic Separation.
4.2.2.1.1 R̲o̲u̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The functional responsibility of Routing is to select
a circuit on which the message shall be transmitted:
The functions are as depicted in figure 4.2.2.1-2 and
as described in detail in the following.
a) Rerouting of messages to which channels are unavailable;
that is a channel unavailability caused at a point
after another Routing Function had been successfully
passed (e.g. a system break down or channel close).
b) Routing of messages in a complete SCARS/CCIS E1-Format
(Comments and VDU-pages).
c) Routing of messages to which all Routing-Indicators
has already been assigned:
- complete message entered via a PTR.
- supervisor prepared ASM
- supervisor prepared Service Message.
The assigned RIs will all relate to the same circuit.
d) Automatic Release of the types described under
c). (not supervisor prepared ASM).
e) RI-assignment of messages passed to ACP127 Conversion
without any assigned RIs:
- User prepared Plaindress and Data Message.
- SCARS/CCIS already released message received
in E1-format.
For each PLA up to 4 alternatives may exist for
RI-assignment.
1) The first RI with a classification higher than
or equal to the message classification will
be selected.
2) If the classification of the related circuit
is too low, or no channels are available into
that circuit, the next RI of proper classification
(if any) will be selected.
3) A RI assigned by MSO will in this situation
be viewed as a PLA with only 1 alternative
for select (that is no alternative).
4) A X-PLA assigned by a user will in this situation
be viewed as if no RI at all is associated
to the PLA.
Therefore this situation will always end unsuccessfully.
5) If no RI of proper classification could be
found and the message is not a Data Message,
the message will be sent for RI assignment.
MSO can then decide whether the message shall
be punched or cleared. If punch, its destination
will be changed to the dedicated PTP. (for
off-line encryption). The dedicated PTP will
also be selected as "circuit" in case the message
has been assigned the special handling designator
CRYPTO SECURITY at preparation.
6) If no circuit of proper classification or no
circuit with available channels can be found,
the message will be sent to a Message Service
Position for RI-assignment.
7) The under e5) and e6) mentioned conditions
are valid if just a single PLA cannot be assigned
an RI.
8) If a message has been "cleared" this will have
no special effect on the RI-assignment, because
the message classification attributes during
this procedure have been changed to unclassified.
f) Message Service Invocation for RI-assignment with
the following notifications:
1 = no channels open in this circuit (ref. all)
2 = classification mismatch RI (ref. e5 - data
message)
3 = too low circuit classification (ref. all)
4 = too many destinations (ref. c)
5 = X-PLA (ref. c4)
If no. 1, a warning report will be sent to supervisor.
If no. 3, a security report will be sent to supervisor.
4.2.2.1.2 A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The responsibility of this functional group is to create
or complete the formatting of FL 3 to 5 in messages
that shall be converted to ACP127 format.
The functions are as depicted in figure 4.2.2.1-3 and
as described in detail in the following:
a) Formatting of FL3 and FL4 in a supervisor prepared
ASM.
The ASM will be assigned a DTG but no SSN.
b) Formatting of FL3, FL4, and FL5 in a supervisor
prepared Service Message.
SSN + DTG will be assigned.
c) Formatting of FL3 in messages entered in complete
ACP127-format (via a PTR). Such message shall
have assigned a new FL3 containing the SSN + DTG
from the automatic release.
d) Formatting of FL3, FL4, and FL5 in a user prepared
plaindress or data message.
This formatting is completely based upon information
collected during prepare and the following release
before the message were forwarded to ACP127 conversion.
e) The originators RI to be inserted FL3 will be selected
in accordance with the following:
1) The originators RI located in FL3 of complete
entered message, supervisor prepared ASM and
Service Messages.
2) The originator RI corresponding to the originating
HQ and the network types to which the message
shall be transmitted after conversion.
1 = NICS TARE
2 = TRC/Point to Point (all)
3 = (TBD)
4 = (TBD)
f) Operating signals will be inserted into FL4 and
FL5 in accordance with the notations in the operating
signals table; otherwise, in FL4. ZGC will be
inserted automatically if specified.
g) Relay-instructions assigned via a supervisor prepare(ASM
or Service Message) will be appended to a formatted
FL4.
No validation rules have been identified for relay-RIs
and associated RIs FL2, so this will not be performed.
4.2.2.1.3 T̲r̲a̲f̲f̲i̲c̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The responsibility of this functional group is to section
messages and to form FL2 and related FL6-FL9 of messages
that are subject to multiple transmissions.
The functions are as depicted in figure 4.2.2.1-4 and
as described in detail in the following:
a) Prepared Plaindress and Service Messages are subject
for section separation (Long message/text). The
calculation for sections will follow the rules
as defined for ACP127.
Supplementary details:
1) If a section should only contain the last "BT"
of a message, this section will not be created,
but this "BT" added to the previous section.
2) Each section will be included Internal Handling
Instructions and subject if entered at prepare.
3) Exercise nickname will be inserted into FL
12C if specified at prepare.
4) If also specified, the classification word
"CLEAR" will be inserted as FL 12A.
b) Messages that had been subject for selective routing
are also subject to route separation. That is,
PLAs specified into prepared Plaindress or Data
message and SCARS/CCIS released message may indicate
separate routes over which the message shall be
transmitted. A "route" is from this point of view
identical to the network types: NICS TARE, SCARS
and CCIS but in relation to TRC/Point to Point
each connection represents a route.
1) Separate "FL2s" will be formatted during above
described conditions.
2) If a message contains local PLAs, these will
be preceded with a ZEN.
3) The PLAs not relevant to this route will also
be preceded with a ZEN, otherwise, the RIs
from FL2 will be inserted in front of the PLAs.
c) Messages of which the RIs in FL2 exceed 200, will
be separated into separate transmissions to that
route - each transmission not exceeding 200 RIs
in FL2.
1) ZEN will be inserted in front of PLAs not included
in that transmission copy.
2) If a transmission-copy only contains INFO addressees
(RIs), the precedence prosign of FL2 will be
changed to the one representing the INFO precedence.
d) If a supervisor parameter so indicates, the message
will not be forwarded to transmission, but be directed
to a PTP for punch.
This rule also applies to messages of Special Handling
Category equal to CRYPTO SECURITY (dedicated PTP).
Fig. 4.2.2.1-1…01…FUNCTIONAL BREAK-DOWN ACP127 CONVERSION
Fig. 4.2.2.1-2…01…FUNCTIONAL BREAK DOWN ROUTING
Fig. 4.2.2.1-3…01…FUNCTIONAL BREAK DOWN ACP127 FORMATTING
Fig. 4.2.2.1-4…01…FUNCTIONAL BREAK DOWN TRAFFIC SEPARATION
4.2.2.2 S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The structure of the ACP127 Conversion Subpackage is
of uncomplex nature. It is one process receiving messages
for conversion from the Conversion Queue (COQ) in an
unlimited loop.
The Conversion Queue is organized in a FIFO structure
with one subqueue for flash and one for non-flash plus
a command sub-queue. As this process is not supposed
to be busy, the FIFO Queue structure will satisfy the
performance requirements.
Should it be necessary to increase performance, the
Conversion Process can be implemented as two incarnated
coroutines.
The software structure of the Conversion Process will
in the following be described in detail.
As reference to this description, the functional break-down
in section 4.2.2.1, the HIPO-diagrams and FLOGRAMS
in section 4.2.2.3 will be used. Also this description
will expand these sections to some extent.
The functional breakdowns depicted in figures 4.2.2.1-1
to 4.2.2.1-4 are kept on a level where the breakdown
had stopped ensuring that the lowest identified software
module did not exceed 250 SWELL-Statements. Furthermore,
the identified functions are arranged in a logically
correct order that satisfies a structured allocation
of software modules.
4.2.2.2.1 A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲1̲.̲0̲)̲
This is the highest level module whose function is
to:
a) Receive the next Queue-element from COQ.
b) Activate the Routing Module.
c) Activate the ACP127 Formatting Module if the routing
was complete.
d) Perform traffic separation by activating the Section
Separation Module and the Route Separation Module.
e) Dismantle the queue-element from the Conversion
Queue.
f) Before it returns to the start-point, it will send
a completion code to a supervisor or MSO command
queue, if such is required.
4.2.2.2.2 R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
The purpose of this module is to locate the circuit
or circuits upon which the message shall be transmitted.
a) If the message is received with a notification
for rerouting, this message view is also followed
by a code indicating the circuit upon which the
message should have been transmitted.
The Rerouting Module is then activated.
b) If the message type is Comment or VDU-page, the
message view is followed by a code indicating whether
SCARS or CCIS (or both) shall receive the message.
The E1-routing Module is then activated.
c) Messages received with a Routing-List supplied
by the ACP127-analysis or by prepare of an ASM
or Service Message will be handled by the Completed
Routing Module.
d) Messages received with a PLA-List supplied by the
ACP127-analysis for SCARS/CCIS released messages
or by prepare of Plaindress or Data messages will
activate the selective Routing Module.
4.2.2.2.2.1 R̲e̲r̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲1̲)̲
Because some circuits may have associated up to 6 channels
of same associated classification, a failed transmission
over one channel might succeed over another channel
associated to that circuit.
Another availability test shall therefore be performed.
If this test fails, the message is directed to Message
Service for RI-assignment.
4.2.2.2.2.2 E̲1̲-̲R̲o̲u̲t̲i̲n̲g̲ ̲(̲2̲.̲2̲)̲
This module is responsible for classification and availability
check of comments and VDU-pages before they are forwarded
to transmission to either SCARS or CCIS (or both).
It is assumed that the "preparer" of the comment or
VDU-page shall be notified via an error-code (notification)
in case of a failed transmission, rather than directing
the message for RI-assignment (no RIs).
The user may then later retrieve the prepared comment
or VDU-pages and send them again.
4.2.2.2.2.3 C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲3̲)̲
Input to this module is a Routing-List only containing
RIs.
The following activities are performed:
- check if all RIs relate to the same circuit.
- check channel availability and classification.
- check for RI classification mismatch.
Finally this module will assign the next SSN and DTG
to the message (automatic release).
4.2.2.2.2.4 S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲)̲
The functional responsibility for this module is to
select the Routing Indicators associated to the addressees
from FL7-9.
This is done as the following:
- A module that creates a selective Routing List
is activated. The input to this module is a List
of PLA-Refs extracted from FL7-9.
- When the selective routing list has been created,
the procedures as described in section 4.2.2.1.1c
will be performed.
- The result will be a list of selected Routing Indicators
and their associated circuits/networks.
- If the list is not complete, it will be directed
to MSO for RI-assignment.
4.2.2.2.3 A̲C̲P̲ ̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲3̲.̲0̲)̲
The function of this module is to format the lines
from FL3 to FL5 (if present).
The messages prepared and entered to the system in
various formats, will after having passed this module
be equal in relation to above mentioned format lines.
Depending upon message originator, following modules
will be activated to complete the ACP127-formatting.
a) ASM Formatting Module (3.1)
- supervisor prepared ASM.
b) Service Message Formatting Module (3.2)
- supervisor prepared service message.
c) Complete Message Formatting Module (3.3)
- complete entered messages from PTR.
d) Prepared Message Formatting Module (3.4)
- prepared plaindress and data messages
- SCARS/CCIS released messages
The 4 Formatting Modules will depending on their needs
activate one or more Conversion Modules in accordance
with the Format type.
- Conversion FL3 (3.1.1)
- Conversion FL4 (3.1.2)
- Conversion FL5 (3.2.3)
The Prepared Message Formatting Module will in addition
be able to format up to 4 combinations of FL3-5, each
with a different RI in FL3 representing the external
network to which the message shall be transmitted.
A message view might after having passed this module
be multiplied by up to 5 (4 external networks + 1 local
network).
Further details about these modules will be supplied
during detailed design. See section 4.2.2.1.2 for
functional details.
4.2.2.2.4 S̲e̲c̲t̲i̲o̲n̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲4̲.̲1̲)̲
This module is responsible for the formatting of FL12A
to FL12D for CAMPS prepared Plaindress, Service Messages
and Data Messages. The Plaindress and Service Messages
may in addition to that be separated into sections.
To achieve this, the module controls the following
modules:
a) Calculate sections (4.1.1)
- returns the number of sections, into which
the message shall be separated.
b) Conversion FL 12A (4.1.2)
c) Conversion FL 12B (4.1.3)
d) Conversion FL 12C (4.1.4)
e) Conversion FL 12D (4.1.5)
The Conversion FL 12A - 12D will be performed as many
times as necessary to form the sections. Each section
and its text-part will be stored in a separate message-view.
If the message at this point has been separated into
sections, the number of message views will be:
Number of networks + number of sections.
The original views containing the full text will not
be touched if it had been necessary to create sections.
Further details about the modules controlled from the
section separation modules will be supplied during
detailed design.
See section 4.2.2.1.3 for functional details.
4.2.2.2.5 R̲o̲u̲t̲e̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲4̲.̲2̲)̲
This module will finish the ACP127 conversion by formatting
FL2 and the associated FL6-9 if relevant for that message
type.
The input to this module is:
- a routing list
- a list of formatted views separated into sections
- number of sections
It will start by calculating the number of routes (=
circuits + local PLA + PTP) and the number of transmission
(copies) necessary to fulfil this transmissions in
case the limit of 200 RIs should be exceeded.
This will be performed by the Calculate Routes Module,
which delivers a List of circuit-IDs + copies.
This list will be sorted in the following order:
- NICS TARE
- TRCs
- LOCAL PLA
- SCARS
- CCIS
The arrangement of this list forms the logical order
in which the following conversion shall be performed.
Counters for Networks, Sections, Routes and Copies
now forms the principles under which the Conversion
of FL2 and FL6 to FL9 will be performed. The conversion
modules used are:
a) Conversion FL2 (4.2.2)
b) Conversion FL6 (4.2.3)
c) Conversion FL7 (4.2.4)
d) Conversion FL8 (4.2.5)
e) Conversion FL9 (4.2.6)
f) Readdressal (4.2.7)
After each conversion, the converted message view will
be forwarded to the circuit-queue, a PTP-queue or to
local distribution.
A message view to a collocated Headquarter (local PLA)
will be formatted in the incoming message format E1.
The difference between this format and the outgoing
ACP127-format is, that PLAs shall not be preceded with
RIs or anything else.
It is assumed that SCARS and CCIS accept messages in
ACP127 format (except comments and VDU pages).
Because comments and VDU pages are prepared in E1 format,
no conversion to SCARS/CCIS E1 format will be needed
in this subpackage.
If the message is a supervisor initiated readdressal,
the final formatting to the readdressal format will
be performed as the last activity.
For functional details see section 4.2.2.1.3.
Finally the number of transmissions can be calculated
like this:
TRANSMISSIONS = ROUTES * SECTIONS + (TOTAL COPIES -
ROUTES)
4.2.2.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The following HIPO diagrams illustrate the data flow
through this subpackage. All activities that have
been framed in the processing part, are the functions
as depicted in figures 4.2.2.1-1 to 4.2.2.1-4.
The Control Logic is shown in the FLOGRAMs which follow
the HIPOs. To some extent they supply each other.
- The HIPO illustrating the Data Flow.
- The FLOGRAM illustrating the Control Logic.
To illustrate the complex logic of traffic separation,
figure 4.2.2.3-1 gives an example of a User Prepared
Plaindress message which shall be forwarded to NICS
TARE and 2 TRC circuits plus be separated into 2 sections.
The lists and counters used in the example, are the
ones described in section 4.2.2.4.
Fig. 4.2.2.3-1…01…TRAFFIC SEPARATION EXAMPLE
A̲C̲P̲ ̲1̲2̲7̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲(̲1̲.̲0̲)̲
START
LOOP:
RECEIVE QUEUE-EL FROM COQ
ROUTING (2.0)
FLAG CONVERSION STOP?
ACP127 - FORMATTING (3.0)
SECTION SEPARATION (4.1)
ROUTE SEPARATION (4.2)
SUPERVISOR OR MSO AWAITING? SEND COMPLETION-CODE
DISMANTLE QUEUE-EL COQ
END LOOP
STOP
R̲O̲U̲T̲I̲N̲G̲ ̲(̲2̲.̲0̲)̲
READ MESSAGE-VIEW
REROUTED MESSAGE? REROUTING (2.1)
COMMENT
OR E1-ROUTING (2.2)
VDU PAGE
COMPLETE MESSAGE
OR
PREPARED ASM COMPLETED ROUTING (2.3)
OR
SERVICE MESSAGE
SELECTIVE ROUTING (2.4)
RETURN
R̲E̲R̲O̲U̲T̲I̲N̲G̲ ̲(̲2̲.̲1̲)̲
GET UNAVAILABLE CHANNEL-ID FROM QUEUE-EL
GET ASSOCIATED CIRCUIT
CHECK CIRCUIT AVAILABILITY
OK? MARK QUEUE-EL FOR RETRANSMISSION
RETURN MESSAGE-VIEW TO CIRCUIT-QUEUE
MARK QUEUE-EL FOR RI-ASSIGNMENT
GET QUEUE-ID FOR MSO
SEND MESSAGE-VIEW TO MSO-QUEUE
FLAG CONVERSION STOP
RETURN
E̲1̲ ̲-̲ ̲R̲O̲U̲T̲I̲N̲G̲ ̲(̲2̲.̲2̲)̲
GET CIRCUIT-ID SCARS/CCIS
GET MESSAGE CLASSIFICATION
CHECK CIRCUIT AVAILABILITY
CHECK CIRCUIT CLASSIFICATION
OK? SEND MESSAGE-VIEW TO SCARS/CCIS CIRCUIT-QUEUE
BUILD QUEUE-INFORMATION WITH ERROR TYPE
GET ORIGINATORS QUEUE ID
SEND INFORMATION TO DRAFTER
FLAG CONVERSION STOP
RETURN
C̲O̲M̲P̲L̲E̲T̲E̲D̲ ̲R̲O̲U̲T̲I̲N̲G̲ ̲(̲2̲.̲3̲)̲
READ PREPARED RI-LIST
ASSIGN CIRCUIT-ID AND NETWORK TYPE TO ALL RIs
DIFFERENT CIRCUIT-IDs? "TOO MANY ROUTES"
CIRCUIT UNAVAILABLE? "NO CHANNELS OPEN"
CIRCUIT CLASS MSG CLASS? "TOO LOW CLASSIFICATION"
NETWORKS = 1 BUILD QUEUE-INFO
RI-ASSIGNMENT AND ERROR-TYPE
SEND MESSAGE-VIEW MSO
FLAG CONVERSION STOP
AUTOMATIC RELEASE (2.3.1)
RETURN
S̲E̲L̲E̲C̲T̲I̲V̲E̲ ̲R̲O̲U̲T̲I̲N̲G̲ ̲(̲2̲.̲4̲)̲
RETURN MSO RI-ASSIGNMENT? GET RI-LIST
GET PLA-LIST
SET UP START POINTERS
LOOP SELECT:
SELECT NEXT ENTRY PLA-LIST; AT END EXIT LOOP
RI THIS ENTRY ASSIGNED?
X-PLA MARK PLA-LIST? "X-PLA"
GET RIs ASSOCIATED TO PLA-REF.
SELECT NEXT RI OF MAX. 4
CIRCUIT UNAVAILABLE? MORE RIs?
"NO CHANNEL OPEN"
CIRCUIT CLASS. MSG CLASS.? MORE RIs?
"TO LOW CLASSIFICATION"
CLASS RI CLASS MSG? MORE RIs?
"CLASSIFICATION MISMATCH"
DATA MESSAGE?
CHANGE SELECTED CIRCUIT-ID TO PTP-QUEUE
END SELECT LOOP
MISSING SELECTS? BUILD QUEUE INFO
RI-ASSIGNMENT
SEND MESSAGE VIEW MSO
FLAG STOP CONVERSION
RETURN
S̲V̲C̲ ̲F̲O̲R̲M̲A̲T̲T̲I̲N̲G̲ ̲(̲3̲.̲2̲)̲
CONVERSION FL3 (3.1.1)
CONVERSION FL4 (3.1.2)
RELAY-INSTRUCTIONS? ADD RELAY-FIELD
DELETE RELAY-FIELD
CONVERSION FL5 (3.2.3)
STORE HEAD-2 FIELD
RETURN
A̲C̲P̲1̲2̲7̲ ̲-̲ ̲F̲O̲R̲M̲A̲T̲T̲I̲N̲G̲ ̲(̲3̲.̲0̲)̲
PREPARED ASM? ASM FORMATTING (3.1)
PREPARED SERVICE MSG.? SERVICE MESSAGE FORMATTING
(3.2)
COMPLETE ENTERED MSG.? COMPLETE MESSAGE FORMATTING
(3.3)
PREPARED MESSAGE FORMATTING (3.4)
RETURN
A̲S̲M̲ ̲F̲O̲R̲M̲A̲T̲T̲I̲N̲G̲ ̲(̲3̲.̲1̲)̲
CONVERSION FL3 (3.1.1)
CONVERSION FL4 (3.1.2)
RELAY-INSTRUCTIONS? ADD RELAY-FIELD
DELAY RELAY-FIELD
ADD TEXT-2 FIELD
STORE HEAD-2 FIELD
DELETE TEXT-1 FIELD
RETURN
P̲R̲E̲P̲A̲R̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲F̲O̲R̲M̲A̲T̲T̲I̲N̲G̲ ̲(̲3̲.̲4̲)̲
GET ORIGINATORS PLA-REF. (HQ)
GET ASSOCIATED 4 RIs
CALCULATE NETWORKS (3.4.1)
LOOP NETWORKS:
SELECT NEXT NETWORK
LOCAL NETWORK?
NICS TARE? SELECT RI NUMBER 1
TRC/POINT TO POINT? SELECT RI NUMBER 2
CONVERSION FL3 (3.1.1)
CONVERSION FL4 (3.1.2)
CONVERSION FL5 (3.2.3)
CREATE NEW HEAD-2 FIELD
MORE NETWORKS? COPY MESSAGE-VIEW
VIEW-LIST + (NETWORK - 1) = VIEW-REF
END NETWORKS LOOP
RETURN
C̲O̲M̲P̲L̲E̲T̲E̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲F̲O̲R̲M̲A̲T̲T̲I̲N̲G̲ ̲(̲3̲.̲3̲)̲
READ HEAD-2 FIELD
LOCATE FL3
CONVERSION FL3 (3.1.1)
RELAY-INSTRUCTIONS ASSIGNED? READ RELAY FIELD
APPEND TO HEAD-2
CODRESS? LOCATE FL5
APPEND TO FL5
STORE HEAD-2
ENCRYPTED PLAINDRESS? - READ HEAD-3
APPEND TO HEAD-3
STORE HEAD-3
RETURN
S̲E̲C̲T̲I̲O̲N̲ ̲S̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲(̲4̲.̲1̲)̲
SELECT RECEIVED VIEW
PREPARED PLAINDRESS
OR CALCULATE SECTIONS (4.1.1)
PREPARED SERVICE MESSAGE?
SECTIONS = 1
PREPARED DATA MESSAGE? LOOP SECTIONS:
CONVERSION FL 12A (4.1.2)
CONVERSION FL 12B (4.1.3)
PLAINDRESS CONVERSION FL 12C
(4.1.4)
OR DATA?
CONVERSION FL
12D (4.1.5)
SECTIONS = 1?
COPY RECEIVED VIEW
VIEW LIST+(NETWORKS-1)+(SECTION-1)=VIEW-REF
STORE TEXT-1
SECTIONS = 1?
SELECT TEXT-PART TEXT-2
STORE NEW TEXT 2
END SECTIONS LOOP
RETURN…86…1 …02… …02… …02… …02… …02…
R̲O̲U̲T̲E̲ ̲S̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲(̲4̲.̲2̲)̲
CALCULATE ROUTES (4.2.1)
LOOP ROUTES:
SELECT NEXT CIRCUIT-ID
GET ASSOCIATED NETWORK-POSITION IN NETWORK-TABLE
LOOP SECTIONS:
SELECT VIEW = VIEW-LIST + NETWORK POSITION
SECTIONS 1? SELECT VIEW = VIEW LIST+(NETWORKS-1)+SECTION
NR
FINAL SECTION? COPY MESSAGE-VIEW
INCLUDE HEAD-1 FROM VIEW-LIST+NETWORK-POSITION
PLA-LIST? CONVERSION FL6 (4.2.3)
CONVERSION FL7 (4.2.4)
CONVERSION FL8 (4.2.5)
CONVERSION FL9 (4.2.6)
STORE HEAD-3
LOOP COPIES:
READDRESSED MESSAGE? READDRESSAL (4.2.7)
CONVERSION FL2 (4.2.6)
STORE HEAD-1
LOCAL NETWORK? BUILD UP HQ/SIC INFORMATION
SEND MESSAGE-VIEW
MORE COPIES? COPY MESSAGE-VIEW
END COPIES LOOP
END SECTIONS LOOP
END ROUTES LOOP
RETURN
