top - download
⟦a9ad277d4⟧ Wang Wps File
Length: 78793 (0x133c9)
Types: Wang Wps File
Notes: CPS/SDS/010
Names: »1046A «
Derivation
└─⟦2b76602a5⟧ Bits:30006036 8" Wang WCS floppy, CR 0060A
└─ ⟦this⟧ »1046A «
WangText
9…08…9…0e…9 8…09…8…86…1
…02…
…02…
…02…
…02…CPS/SDS/010
…02…KNB/810801…02……02…
TRAFFIC HANDLING
…02……02…CAMPS
4.2.2.4 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
This section defines the major dataitems used during
routing and conversion.
4.2.2.4.1 R̲o̲u̲t̲i̲n̲g̲ ̲L̲i̲s̲t̲s̲
a) L̲a̲y̲-̲o̲u̲t̲ ̲R̲I̲-̲L̲I̲S̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
RI CODE RI NETWORK TYPE CIRCUIT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 14 Bytes
Size: Max. 250 Records
Total: 3500 Bytes
R̲I̲-̲C̲o̲d̲e̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲
0 = Select ok
1 = No channels open this circuit
2 = Classification mismatch RI
3 = Too low circuit classification
4 = Too many destinations (routes)
5 = X-PLA
R̲I̲ ̲(̲9̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲)̲
The Routing Indicator selected under selective
Routing Procedures, assigned under preparation
(e.g. ASM) or assigned by Message Service.
N̲e̲t̲w̲o̲r̲k̲ ̲T̲y̲p̲e̲ ̲(̲C̲h̲a̲r̲a̲c̲t̲e̲r̲)̲
A = CCIS
C = CAMPS Local
S = SCARS
T = TRC/Point-to-Point
N = NICS TARE
C̲i̲r̲c̲u̲i̲t̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲
A code indicating the circuit-ID to which the RI
is assigned.
b) L̲a̲y̲-̲O̲u̲t̲ ̲S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲I̲-̲L̲i̲s̲t̲:̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
4 * CLASSIFICATION RI NETWORK CIRCUIT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 52 Bytes
Size: 1 record
Total: 52 Bytes
C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲C̲h̲a̲r̲a̲c̲t̲e̲r̲)̲
A character indicating the highest classification
associated to the following route (RI)
R̲I̲ ̲(̲9̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲)̲
The Routing Indicator available for select.
N̲e̲t̲w̲o̲r̲k̲ ̲a̲n̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲
As for the RI-list.
The up to 4 RIs available for select in accordance
with classification, will be arranged with the
lowest first, in order to establish the logical
sequence of processing:
The RI selected from the selective RI-list will
be assigned the RI-list.
c) L̲a̲y̲-̲O̲u̲t̲ ̲O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲R̲I̲-̲L̲i̲s̲t̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
RI…0e…1…0f… RI…0e…2…0f… RI…0e…3…0f… RI…0e…4…0f…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 36 Bytes
R̲I̲…8e…1̲…8f… ̲-̲ ̲R̲I̲…8e…4̲…8f…
The four RIs associated to the originators HQ.
The purpose of these RIs is to select one of them
to be used when formatting FL3.
RI…0e…1…0f… = NICS TARE
RI…0e…2…0f… = TRC/Point-to-Point
RI…0e…3…0f… = ?
RI…0e…4…0f… = ?
4.2.2.4.2 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲B̲u̲f̲f̲e̲r̲s̲
Size: 1024 Bytes
Buffer-1: Message parts for conversion
Buffer-2: Formatted variable text
TOTAL: 2048 Bytes
The size of these buffers might be redefined during
detailed design in accordance with available resources
and performance.
At this stage the buffers are estimated to contain
1 sector of data each.
4.2.2.4.3 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲L̲i̲s̲t̲s̲
a) L̲a̲y̲-̲O̲u̲t̲ ̲V̲I̲E̲W̲-̲L̲I̲S̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VIEW-REF
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 2 bytes
Size: 15
Total: 30 bytes
V̲I̲E̲W̲-̲R̲E̲F̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲
View Identifications of formatted and section separated
message views for multiple transmissions.
b) L̲a̲y̲-̲O̲u̲t̲ ̲C̲i̲r̲c̲u̲i̲t̲-̲L̲i̲s̲t̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
CIRCUIT ID NETWORK CODE COPIES
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 4 Bytes
Size: 33 records
Total: 132 Bytes
C̲i̲r̲c̲u̲i̲t̲ ̲I̲D̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲
A number representing the queue to which the message
shall be directed after conversion.
- NICS TARE circuit queue
- TRC/Point-to-point circuit queues
- SCARS circuit queue
- CCIS circuit queue
- Message Distribution queue
- PTP queue
N̲e̲t̲w̲o̲r̲k̲ ̲C̲o̲d̲e̲ ̲(̲B̲y̲t̲e̲)̲
A code indicating the network type, depending on
which the message shall be formatted:
A = CCIS
C = CAMPS Local
S = SCARS
T = TRC/Point-to-Point
N = NICS TARE
C̲O̲P̲Y̲ ̲(̲H̲a̲l̲f̲ ̲I̲n̲t̲e̲g̲e̲r̲)̲
The number of transmissions needed to include all
RIs of FL2 using the associated View-Ref as basis.
c) C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲C̲o̲u̲n̲t̲e̲r̲s̲
Integers: Number of Sections
Number of Routes
Number of Networks
4.2.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The environment of this sub-package is as depicted
in figure 4.2.2.5-1. This figure illustrates the other
sub-packages of THP and packages that this sub-package
interfaces to. The interfaces to system-oriented packages
are described in section 3.4
4.2.2.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 sub-packages and packages that the
ACP127-conversion sub-package interface to are:
- Message Distribution Package (MDP)
- Terminal Package (TEP)
- Transport Sub-package (TRS)
- ACP127 Analysis Sub-Package (AAS)
- Log Package (LOG)
FIGURE 4.2.2.5-1…01…INTERFACES ACP127 CONVERSION SUB-PACKAGE
4.2.2.5.1.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲
A̲C̲S̲ ̲t̲o̲ ̲M̲D̲P̲:̲
a) Plaindress or data messages for incoming message
distribution (Local PLA - Format E1).
4.2.2.5.1.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
A̲C̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲
a) Message service for RI-assignment.
b) Security and warning Reports for printout at the
supervisor position.
T̲E̲P̲ ̲t̲o̲ ̲A̲C̲S̲:̲
a) User prepared plaindress and data messages for
RI-assignment and conversion.
b) Supervisor prepared ASM and service messages for
RI-validation and conversion. (Return Completion-code).
c) User prepared comments and VDU-pages in complete
SCARS/CCIS E1-format that shall be forwarded to
these systems. (Return status-code originator).
d) Re-entering from outgoing message service after
RI-assignment with a notation indicating whether
the following subfunctions have been performed:
- Relay assignment
- Punch
- Clear.
(Return Completion Code)
e) Supervisor initiated readdressal and rerun.
(Return Completion Code)
4.2.2.5.1.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲R̲S̲
A̲C̲S̲ ̲t̲o̲ ̲T̲R̲S̲:̲
a) Messages for transmission to:
- NICS TARE
- TRC/Point-to-point
- SCARS
- CCIS
The messages will be forwarded to the corresponding
circuit-queue.
b) Re-routed messages for transmission and retransmission.
The messages for retransmission shall be supplied
with a suspected duplicate pilot (ACP127 or E1
in accordance with format-type).
c) Messages to be punched at the dedicated PTP for
off-line decryption.
d) A command indicating that a message of precedence
flash has been forwarded to a circuit or PTP-queue
will be sent to the transmission control queue
in order to initiate preemption (not NICS TARE).
T̲R̲S̲ ̲t̲o̲ ̲A̲C̲S̲:̲
a) Messages for re-routing (any case of channel close).
It shall be indicated whether the message had been
partly transmitted or not (if possible).
4.2.2.5.1.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲A̲S̲
A̲A̲S̲ ̲t̲o̲ ̲A̲C̲S̲:̲
a) Complete outgoing messages for Routing and automatic
release before transmission.
b) Plaindress released messages from SCARS/CCIS for
RI-assignment and conversion.
4.2.3 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲
4.2.3.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 incoming transport receives message lines from
incoming channels via IOC, checks for reception errors,
extracts message characteristics, divides and stores
message lines into several fields depending on the
message type and condition (garbled characters). The
incoming transport finally forwards the recieved message
to the Analysis Queue.
There are four types of external channels which the
incoming transport will serve. They are as follows:
- TRC, Point-to-Point
- NICS TARE
- SCARS/CCIS
- PTR
For the external channel types listed above, the incoming
transport is described in detail in the following and
the functions which will be performed are depicted
in figures 4.3.2-1 to 4.2.3-5. For further details
see HIPO diagrams section 4.2.3.3.
4.2.3.1.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲T̲R̲C̲,̲ ̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
The main functional components contained within the
incoming transport, related to TRC, Point-to-Point
connections are as follows:
- Initial transport
- Error control
- Message characteristics
- Message division
The functions listed above are depicted in figure 4.2.3-2
and described in detail in the following.
4.2.3.1.1.1 I̲n̲i̲t̲i̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Initial transport allocates buffers to IOC into which
message lines will be delivered by IOC upon reception
of a message on the external channel.
The initial transport consists of 2 functions which
are as follows:
- Buffer control
- Input control
a) T̲h̲e̲ ̲B̲u̲f̲f̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ takes care of the sequence in
which the buffers shall be allocated to IOC.
b) I̲n̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ performs the command communication
between incoming transport and IOC, and analyzes
the response codes which will be returned from
IOC.
4.2.3.1.1.2 E̲r̲r̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
Error control checks the received message lines for
the following errors which may occur. The necessary
actions upon the errors detected will be taken, e.g.
termination of message, channel report, and character
deletion.
- 2. SOTF
- EOTF detected before the actual end of message
- Too long line
- Oversized message
- Halted message
- 140 identical consecutive characters
- 100 characters detected, counted from the last
received EOTF, without detection of a SOTF
- Preemption
The error types listed above will be described in detail
in the following.
a) 2̲ ̲S̲O̲T̲F̲ ̲D̲e̲t̲e̲c̲t̲e̲d̲ ̲W̲i̲t̲h̲o̲u̲t̲ ̲a̲n̲ ̲E̲O̲T̲F̲ ̲I̲n̲ ̲B̲e̲t̲w̲e̲e̲n̲
This function will detect the SOTF of the incoming
message and in case of 2 SOTF without an EOTF in
between. The message will be terminated upon detection
of the second SOTF. The message will be forwarded
to Analysis with an indication of the error-type.
A channel report indicating the incident will be
forwarded to the supervisor's printer.
The second detected SOTF will be assumed to be
the SOTF of a new message.
b) E̲O̲T̲F̲ ̲D̲e̲t̲e̲c̲t̲e̲d̲ ̲B̲e̲f̲o̲r̲e̲ ̲t̲h̲e̲ ̲A̲c̲t̲u̲a̲l̲ ̲E̲n̲d̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
This functon will upon detection of an EOTF terminate
the incoming message and in the following case
an error code will follow the message to analysis.
EOTF detected within Text 1 part of the message.
c) T̲o̲o̲ ̲L̲o̲n̲g̲ ̲L̲i̲n̲e̲
If this error occurs in a message, except in text
part of a data message, it will cause a channel
report to be forwarded to the supervisor's printer.
An error list containing a pointer to the error
line and an error code will follow the message
to analysis. The error will be marked in the QEL
too.
d) O̲v̲e̲r̲s̲i̲z̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
This error will cause the message to be automatically
terminated and a channel report will be printed
out at the supervisor's printer. An error code
contained within a QEL will follow the message
to analysis. The characters following the character
number 12.000 will be discarded until detection
of a SOTF.
e) H̲a̲l̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
This condition will result in automatic termination
of the message and a channel report will be forwarded
to the supervisor's printer. An error code will
follow the message to analysis.
f) 1̲4̲0̲ ̲I̲d̲e̲n̲t̲i̲c̲a̲l̲ ̲C̲o̲n̲s̲e̲c̲u̲t̲i̲v̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲
If this error occurs within a message, except for
text part of data messages, it will result in automatic
termination of the message and a channel report
will be forwarded to the supervisor's printer.
A QEL containing an error code will follow the
message to analysis. The following characters will
be discarded until detection of a SOTF.
g) 1̲0̲0̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲ ̲D̲e̲t̲e̲c̲t̲e̲d̲,̲ ̲C̲o̲u̲n̲t̲e̲d̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲L̲a̲s̲t̲
̲R̲e̲c̲e̲i̲v̲e̲d̲ ̲E̲O̲T̲F̲,̲ ̲W̲i̲t̲h̲o̲u̲t̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲a̲ ̲S̲O̲T̲F̲
The only action which will be performed upon occurance
of this error is that a channel report indicating
the incident will be forwarded to the Supervisor's
printer.
h) P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲
Upon detection of preemption, the message will
be automatically terminated and a channel report
will be printed out at the supervisor's printer.
An error code will follow the message to analysis
within a QEL. The characters following preemption
will be discarded until detection of an SOTF.
4.2.3.1.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
Message characteristics extract the following information
from the message lines, if they are present:
- Channel designator
- Transmission serial number
- Precedence level
- Classification
- Special handling instruction for data message only
- Group count
- Paging
The characteristics listed above will be detected,
if they are present using the following functions:
- FL1 check
- FL2 check
- FL3 Detect
- FL4 check
- FL6 Detect
- FL11, FL13 Detect
- Unpaging
- FL15 check
a) F̲L̲1̲ ̲C̲h̲e̲c̲k̲
This function detects the channel designator and
upon occurrence of an error. This will cause an
error code to follow the message to analysis.
The FL1 check detects the Transmission serial number
and in case of an error the following instructions
will be used.
1) If the TSN is missing, a channel report will
be forwarded to the supervisor's printer, a
log record indicating channel discontinuity
will be created and an error code will follow
the message to analysis.
2) If the received TSN is less than the expected
TSN, a channel report will be forwarded to
the Supervisor's printer, a log record, indicating
channel discontinuity, will be created and
an error code will follow the message to analysis.
3) If the received TSN is greater than the expected
TSN, a channel report will be forwarded to
the supervisor's printer, a log record indicating
channel discontinuity will be made and an error
code will follow the message to analysis. Finally,
the expected TSN will be set equal to the received
value.
b) F̲L̲2̲ ̲C̲h̲e̲c̲k̲
This function will detect the precedence level
of the message in accordance with the acceptable
deviation (ref. ICD 0003 para 3.2.3). In case of
an acceptable deviation, the precedence level letters
will be corrected. If no detection of precedence
level, Immediate will be assigned the message and
an error code will follow the message to analysis.
c) F̲L̲3̲ ̲D̲e̲t̲e̲c̲t̲
This function detect "DE" of the format line 3
if present and in case of detection the information
will be used by the Message Division.
d) F̲L̲4̲ ̲C̲h̲e̲c̲k̲
This function will detect the classification of
the message in accordance with the acceptable deviations
(ref. ICD/0003 para 3.4.3.a). In case of an acceptable
deviation, the classification letters will be corrected.
If no detection of the classification is possible,
the classification of the channel will be assigned
the message and an error code will follow with
it to analysis.
The FL4 check also performs detection of special
handling instructions in accordance with the acceptable
deviations (ref. ICD/0003 para 3.4.3.b). In case
of an acceptable deviation, the special handling
instruction will be corrected. If no special handling
instruction for data message has been detected,
the message will be further processed as not being
a data message.
e) F̲L̲6̲ ̲D̲e̲t̲e̲c̲t̲
Detection of format line 6 will be performed by
this function. Message Division uses the information
for field selection.
f) F̲L̲1̲0̲ ̲C̲h̲e̲c̲k̲
This function detects the Group Count indicator,
if present, and in case of detection, the information
will follow the message to analysis.
g) F̲L̲1̲1̲,̲ ̲F̲L̲1̲3̲,̲ ̲D̲e̲t̲e̲c̲t̲
Format Line 11 and 13 contain the letters "BT",
and this function will detect these lines if they
are present. Message Division will use the information
for field selection.
h) U̲n̲p̲a̲g̲i̲n̲g̲
Detection will be performed on messages except
for data messages. This function detects the End-Of-Page-Function
(EOPF) and if the following line contains the page
identification, both lines will be discarded.
If only the EOPF is present, this is also the only
line which will be discarded.
i) F̲L̲1̲5̲ ̲C̲h̲e̲c̲k̲
If the line is present this function will extract
the station serial number from the line and store
it in the view-information field.
4.2.3.1.1.4 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
Divides and stores message lines into fields in such
a way that the format lines starting with FL1 and further
on until detection of "DE" are stored in field "Head
1".
The format lines starting from FL3 and further on until
detection of "FM" are stored in field "Head 2".
FL6 and the following format lines until detection
of "BT" are stored in field "Head 3". FL11 containing
"BT" is not stored, but the following lines until detection
of the FL13 will be stored in field Text 1. FL13 will
not be stored.
The format lines following FL13 will be stored in field
Text 3, except for the format line containing the EOTF.
4.2.3.1.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
The functions contained within the Incoming Transport,
related to NICS TARE external channels are the same
as those described for TRC, point-to-point connections
except for the following.
- P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲
This will not be performed on NICS TARE external
channels.
4.2.3.1.3 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲
The functional components contained within the Incoming
Transport related to SCARS/CCIS external channels are
the same as those described for TRC, point-to-point.
Only the exceptions will be described in the following.
4.2.3.1.3.1 E̲r̲r̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
Contains the following exceptions:
- Start of message
- Too long line
- Block sequence error
a) S̲t̲a̲r̲t̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲
This function will upon reception of message in
ACP127 format, follow the procedure as described
for TRC, point-to-point. If the message is in
format E1, the detection of FL1 will be based on
the channel designator.
b) T̲o̲o̲ ̲l̲o̲n̲g̲ ̲l̲i̲n̲e̲
This function will in accordance with the message
type detect too long lines, for lines respectively
69 and 80 char. If a too long line is detected,
the further procedure will be as described for
TRC, point-to-point.
c) B̲l̲o̲c̲k̲ ̲s̲e̲q̲u̲e̲n̲c̲e̲ ̲e̲r̲r̲o̲r̲
If an error code returned from IOC, indicates error
in the sequence of received message blocks on link
level. This function will set a mark in the QEL
indicating the error type.
4.2.3.1.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
Contain the following exceptions.
- Message-ID
- FL1
- FL11, FL13, FL J.
a) M̲e̲s̲s̲a̲g̲e̲-̲I̲D̲
This function will extract the following information
from the start-of-message-block.
- Block type
- Message type
- Precedence level
- Classification
If the received message is a Transaction Acknowledgement,
this function will compare the received TSN with
the expected TSN in the Time-out Table. In the
case of match, the outgoing transport will be allowed
to continue transmission of the next message.
In the case of no match between received and expected
TSN, the Transaction Acknowledgement will be discarded.
The reason for discarding is that the message
is already under transmission.
b) F̲L̲1̲
This function differs from the one specified for
TRC, point-to-point, because the Incoming Transport
will receive messages in format ACP127 and format
E1 from the SCARS/CCIS external channels. Therefore
this function will accept format line 1 with or
without the SOTF (VZCZC). After analysis of the
format line, a command will be sent to Transport
Control, indicating that Transport Control shall
create a Transaction Acknowledgement to be transmitted
by the Outgoing Transport.
c) F̲L̲1̲1̲,̲ ̲F̲L̲1̲3̲,̲ ̲F̲L̲ ̲J̲
This function will detect the following, if present.
depending on the message type.
- format line 11 containing "BT"
- format line 13 containing "BT"
- format line J containing "MSGID"
The information collected by this function will
be used for field selection within message division.
4.2.3.1.3.3 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
Contains the following exceptions:
- Head 1
- Text 1
a) H̲e̲a̲d̲ ̲1̲
Accepts format line 1 with or without SOTF (VZCZC)
as the first line to be stored in field "Head 1".
b) T̲e̲x̲t̲ ̲1̲
Upon detection of either "BT" or "MSGID", this
function will store the message lines in field
"Text 1", except for the format lines containing
"BT".
4.2.3.1.4 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲P̲T̲R̲
The functional components contained within the Incoming
Transport related to the PTR external channels is the
same as those specified for TRC, point-to-point. Only
the exceptions are described in the following.
4.2.3.1.4.1 E̲r̲r̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
Contains the following exceptions:
- Start of message
- Halted message
a) S̲t̲a̲r̲t̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲
This function will upon reception of a message
from the PTR external channel, discard characters
until detection of either format line 1 or format
line 2.
b) H̲a̲l̲t̲e̲d̲ ̲m̲e̲s̲s̲a̲g̲e̲
If this condition occurs, the message will be discarded
and a report forwarded to the supervisor.
4.2.3.1.4.2 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
Contains the following exception:
- Head 1
a) H̲e̲a̲d̲ ̲1̲
This function will accept either format line 1
or format line 2 to be the first message line stored
in field "Head 1".
4.2.3.1.5 M̲S̲O̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
The MSO Transport is a collection of functions which
shall be used after a message has been corrected at
a Message Service Position. See figure 4.2.3-6.
The environment of this incoming transport is the ACP127
Analysis Process, where these functions will be used
as described above.
The input to the MSO transport modules will be a message-view
containing only one message field.
The output will be a new message-view separated into
the message fields required to complete the ACP127
analysis.
Fig. 4.2.3-1…01…INCOMING TRANSPORT FUNCTIONAL BREAKDOWN
Fig. 4.2.3-2…01…INCOMING TRANSPORT TRC, POINT-TO-POINT.…01…FUNCTIONAL BREAKDOWN
Fig. 4.2.3-3…01…INCOMING TRANSPORT NICS TARE…01…FUNCTIONAL BREAKDOWN
Fig. 4.2.3-4…01…INCOMING TRANSPORT…01…SCARS/CCIS FUNCTIONAL BREAKDOWN
Fig. 4.2.3-5…01…INCOMING TRANSPORT PTR, FUNCTIONAL BREAKDOWN
4.2.3.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The incoming transport is a coroutine working inside
a transport process. It serves an incoming channel
from NICS TARE, TRC/Point to point, SCARS, CCIS or
PTR.
The input is buffered lines received via IOC.
The output is messages mainly formatted into ACP127
format delivered to analysis.
There is no queue associated to an incoming transport
coroutine.
For each different transport process as specified in
section 4.1.2 there will be an associated incoming
transport coroutine with almost identical capabilities
(except PTP). For functional differences see section
4.2.3.1 for details.
In this section, the structure of a general incoming
transport coroutine will be specified.
The software structure is almost identical to the functional
breakdown depicted in figures 4.2.3-1 to 4.2.3-5.
Also see section 4.2.3.3 for data flow and control
logic.
4.2.3.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
The incoming transport module will perform the following
processing in an unlimited loop:
a) Call the Initial Transport module (2.1) which will
deliver a buffer of data (lines) for continuing
processing when ready.
If no data are incoming, the coroutine will go
into await condition at this point.
The following modules will then be activated in
a loop equal to the number of lines contained in
the transport buffer.
b) Error control module (2.2) will perform tolerance
checks and react upon errors detected during the
Initial Transport.
c) Message Characteristics (2.3) will detect specific
format lines and certain message characteristics
to be used during the processing flow.
d) Message Division module (2.4) will write the lines
down into a field in the internal format representation
for messages in ACP127.
e) If this was the end of that message, it will now
be forwarded to the ACP127 analysis process, before
the sequence of processing will be repeated.
4.2.3.2.2 I̲n̲i̲t̲i̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲1̲)̲
The Initial Transport Module will fulfil its functions
by activating the:
- Buffer control module (2.1.1) and
- Input control module (2.1.2)
The first module will allocate buffers to be used by
the second module.
Errors that occur during this processing will be flagged
and used as input to the next module.
4.2.3.2.3 E̲r̲r̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲2̲)̲
The input to this module will be the transport buffer
filled up with data plus the Input-Code associated
to the termination.
The Input Code can be an error code or a normal completion
code.
The Error Control module will then line by line detect
illegal conditions as described in section 4.2.3.1.1.2
and based upon the error-type, initiate a termination
of the message.
The error detection (tolerance control) is considered
to take place within the Error Control module itself.
From this module a channel report module shared with
the Message Characteristics module will be activated.
If a too long line condition occurs, a module generate
error-list will be activated to pick up the location
for that error.
4.2.3.2.4 M̲e̲s̲s̲a̲g̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲3̲)̲
The Message Characteristics module will fulfil its
functions as described in section 4.2.3.1.1.3 by activating
the modules:
- FL1 Check (2.3.1)
- FL2 Check (2.3.2)
- FL3 Detect
- FL4 Check (2.3.3)
- FL6 Detect
- FL10 Check (2.3.4)
- FL11 Detect
- Unpaging (2.3.5)
- FL13 Detect
- FL15 Check (2.3.6)
These modules will be activated in a sequential schedule
determined by the message field which is in use at
the moment (e.g. having reached "Head 2" part of message
the FL1 and FL2 modules will not be activated again
on this message).
Having reached the text-part of a message, the unpaging
module (2.3.5) will be activated with the purpose of
removing such indication.
The FL1 check module will in case of channel discontinuity
(TSN mismatch) activate a channel discontinuity log
module and a channel report module.
If a new format line is detected, this information
will be returned to be used as input to the Message
Division module.
4.2.3.2.5 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲4̲)̲
The input to this module is the format-line last detected.
This module maintains an internal variable indicating
the message field in use for the moment. If a new
format line has been detected and this format line
applies to change for a new message field, this will
be done by storing the present field and initiating
the next relevant field.
See section 4.2.3.1.1.4 for functional details.
4.2.3.2.6 O̲t̲h̲e̲r̲ ̲M̲o̲d̲u̲l̲e̲s̲
At this point all modules included in an Incoming Transport
coroutine has either been described or mentioned.
The modules only mentioned will be described during
detailed design.
4.2.3.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 HIPO diagrams that follow this section illustrate
the data flow through this subpackage.
The top level control logic is illustrated by means
of FLOGRAM and also to some extent via the HIPO diagrams.
I̲N̲C̲O̲M̲I̲N̲G̲ ̲T̲R̲A̲N̲S̲P̲O̲R̲T̲
LOOP:
INITIAL TRANSPORT (2.1)
WAIT FOR COMPLETION
LOOP LINES:
ERROR CONTROL (2.2)
MESSAGE CHARACTERISTICS (2.3)
MESSAGE DIVISION (2.4)
END LOOP LINES:
END OF MESSAGE? QUEUE MESSAGE-VIEW TO ANALYSIS
END LOOP
4.2.3.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Each Incoming Transport coroutine will have the following
private data elements.
4.2.3.4.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲B̲u̲f̲f̲e̲r̲s̲
Length: 512 bytes
No. of buffers: 2
Size: 1024
Total: 33 x 1024 = 33.792 bytes
The transport buffers shall be used during the incoming
transport. One for fill-up with data while the other
is being emptied.
4.2.3.4.2 P̲o̲i̲n̲t̲e̲r̲ ̲B̲u̲f̲f̲e̲r̲
Length: 10 integers
Total: 33 x 20 = 660 bytes.
The purpose of the pointer-buffer is to contain pointers
to format lines in a transport buffer.
The line pointed out shall not be included in the internal
message format.
4.2.3.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
The environment of this subpackage is as depicted in
figure 4.2.3.5-1. This figure illustrates the other
subpackages of THP and packages that the incoming transport
subpackage interfaces to. Also the external interfaces
to this subpackage are illustrated.
The other subpackages and packages interfaced to/from
this subpackage are:
- Outgoing Transport Subpackage (OTS)
- Transport Control Subpackage (TCS9
- ACP127 Analysis Subpackage (AAS)
- Terminal package (TEP)
- Log package (LOG)
4.2.3.5.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲O̲T̲S̲
I̲T̲S̲ ̲t̲o̲ ̲O̲T̲S̲: (via semaphore 1)
a) Transaction Acknowledgement received on SCARS/CCIS
channel.
4.2.3.5.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲C̲S̲
I̲T̲S̲ ̲t̲o̲ ̲T̲C̲S̲:
a) Command send Transaction Acknowledgement for received
message from SCARS/CCIS.
4.2.3.5.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲A̲S̲
I̲T̲S̲ ̲t̲o̲ ̲A̲A̲S̲:
a) Incoming message received via an external channel
for ACP127 analysis.
b) Complete message entered via a PTR for ACP127 analysis.
c) The messages directed to ACP127 analysis may be
attached with an error code associated to the possible
type of garble characteristic detected during transport.
(e.g. oversized message).
4.2.3.5.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
I̲T̲S̲ ̲t̲o̲ ̲T̲E̲P̲: (not PTR)
a) Channel Reports to be printed at the supervisor
position.
1) Channel discontinuity
2) Halted message
3) Premature termination
4) 100 characters received after EOTF without
detect of SOTF
5) Oversized message
6) 140 identical consecutive characters
7) No EOTF.
4.2.3.5.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲o̲g̲
Channel discontinuity log.
Fig. 4.2.3.5-1…01…INTERFACES INCOMING TRANSPORT
4.2.4 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.4.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 Transport Control subpackage is responsible for
control of the incoming and outgoing traffic of messages.
For this purpose it receives timer events from the
timer and commands from Analysis, Conversion, Supervisor,
SSC, Incoming Transport and Outgoing Transport via
the Channel Command Queue (CCQ). The functional components
which are identified within this subpackage are the
following:
- Timeout control
- Command control
These functional components are used to serve traffic
control of the following external channels.
1. TRC, point-to-point
2. NICS TARE
3. SCARS/CCIS
4. PTR
5. PTP
For the external channels listed above, the functions
contained within the Transport Control subpackage are
described in detail in he following and depicted in
figures 4.2.4-1 to 4.2.4-6.
4.2.4.1.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲,̲ ̲T̲R̲C̲,̲ ̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
The Transport Control for TRC, point-to-point external
channels consists of the following functional components:
- Timeout control
- Command control
4.2.4.1.1.1 T̲i̲m̲e̲o̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
Timeout Control is based on the timer event, which
is requested to be received every minute in the CCQ
from the timer, used to update and control the Time-out
Table. The functions contained within the Time-out
Control are as follows:
- Update Time-out Table
- Incoming traffic
- Reception of a self-originated self-addressed channel
check.
- Transmission of a channel number reset
- Reception of a channel number reset
- Reception of Flash acknowledge
a) U̲p̲d̲a̲t̲e̲ ̲t̲i̲m̲e̲o̲u̲t̲ ̲T̲a̲b̲l̲e̲
This function updates the timeout table every
minute upon reception of a timer-event. The
updates include besides decrement of the timeout
values, a check for changes in the incoming
and outgoing channel status which have influence
on whether a timeout function shall be performed
or not.
The following function will only be performed
upon timeout.
b) I̲n̲c̲o̲m̲i̲n̲g̲ ̲t̲r̲a̲f̲f̲i̲c̲
- Forward a self addressed channel check
to Outgoing Transport.
- Start timeout on reception of a self-originated
self-addressed channel check.
c) Reception of a self-originated self-addressed
channel check.
- A channel report will be forwarded to the
supervisor's printer upon timeout.
d) T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲o̲f̲ ̲a̲ ̲c̲h̲a̲n̲n̲e̲l̲ ̲n̲u̲m̲b̲e̲r̲ ̲r̲e̲s̲e̲t̲
- A channel number reset will be sent to
Outgoing Transport for transmission.
e) R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲a̲ ̲c̲h̲a̲n̲n̲e̲l̲ ̲n̲u̲m̲b̲e̲r̲ ̲r̲e̲s̲e̲t̲
- A channel report will be forwarded to the
Supervisor's printer.
f) R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲f̲l̲a̲s̲h̲ ̲a̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲
- The flash message will be sent to Outgoing
Transport for retransmission.
- A channel report will be forwarded to the
Supervisor's printer.
4.2.4.1.1.2 C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
This will carry out the functions related to the commands
which may be received by the Transport Control subpackage
from the following sources:
- Analysis
- Conversion
- Supervisor
- SSC
- Outgoing Transport
The commands and functions related to these are described
in detail in the following.
a) A̲n̲a̲l̲y̲s̲i̲s̲
1) Transmit a flash acknowledge.
Parameter: TI of the received flash message
requiring acknowledge.
This will cause a flash acknowledge to be forwarded
the Outgoing Transport for transmission.
2) Received a flash acknowledge
Parameter: TI of the transmitted flash message
requiring
acknowledge.
If the TI exists in the timeout table, the
timeout on this particular acknowledge will
be stopped and cleared.
Log and statistics will be created and the
flash message stored.
If the TI does not exist in the timeout table,
the flash acknowledge will be forwarded to
the Supervisor's printer.
3) Received a self-originated self-addressed channel
check.
If no self-addressed channel check message
is expected back because the timeout has occured,
the received self-addressed channel check will
be forwarded to the Supervisor's printer.
If the message is expected the timeout will
be cleared.
4) Received a channel number reset.
If the message has not been detected by the
Incoming Transport, it will result in a reset
of the transmission serial number to the value
002 as the next expected TSN of an incoming
message.
If the channel number reset was detected by
the Incoming Transport, no further action will
be taken.
5) Received an "Outgoing channel opening" ASM.
This will cause a TEST message to be forwarded
to the Outgoing Transport for transmission
and the outgoing channel status will be set
"open". A channel report indicating the event
will be sent to the supervisor's printer.
6) Received an outgoing channel closing ASM.
The outgoing channel status will be set "closed"
and the Outgoing Transport will be ordered
to stop transmission. A channel report will
be forwarded the supervisor's printer. Statistics
will be created.
7) Transmit a TEST reply indicating "Test correct"
ZBZ 5.
The TEST reply will be sent to the outgoing
transport for transmission.
8) Transmit a TEST reply indicating "TEST Garbled"
ZBZ 1.
The incoming channel status will be set "closed"
and the TEST reply message will be forwarded
to the Outgoing Transport for transmission.
A channel report indicating the event will
be sent to the Supervisor's printer. Log and
statistics will be created.
9) Received a TEST reply indicating "TEST garbled"
ZBZ 1.
This will cause the outgoing channel status
to be set "closed" and the Outgoing Transport
will be ordered to stop transmission. A channel
report will be forwarded the Supervisor's printer.
Statistics will be created.
10) Transmit an identical character report.
If an identical character report shall be transmitted
on this channel, the message will be forwarded
the Outgoing Transport for transmission. A
channel report will be sent to the Supervisor's
printer.
b) C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲
1) Flash notification.
The Transport control will check with the Channel
Profile whether or not preemption shall be
performed on this channel.
If preemption shall be performed, the Outgoing
Transport will be ordered to carry out preemption
within a specified time limit.
c) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲
1) Incoming channel opening.
This command will result in an incoming channel
opening message be forwarded to the Outgoing
Transport for transmission and the incoming
channel status will be set "open". A channel
report indicating the event will be sent to
the Supervisor's printer. Statistics will
be created.
2) Incoming channel closing.
The incoming channel status will be set "closed"
upon reception of this command. An incoming
channel closing ASM will be sent to the Outgoing
Transport for transmission. A channel report
will be forwarded to the Supervisor's printer.
Statistics will be created.
d) S̲S̲C̲
1̲)̲ Start-up.
This command will cause the Transport Control
to check with the channel profile whether or
not the traffic shall be opened.
If the message traffic shall be opened, this
function will perform the following:
- Forward an open incoming channel ASM to
Outgoing Transport for transmission
- Forward a channel report to supervisor
- Create log
- Create statistics
2) Close-down
The Transport Control will perform the following
upon reception of this command:
- Decrement Circuit Availability Counter.
- Set incoming and outgoing channel status
"closed"
- Forward a close order with a specified
time limit to the Outgoing Transport
- Create log
- Create Statistics.
e) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
1) Outgoing message log and statistics.
This command will cause the Transport Control
to perform the following:
- Generate outgoing message log
- Generate outgoing message statistics
- Store outgoing message.
4.2.4.1.2 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲,̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
The Transport Control for NICS TARE external channels
contains the same main functional components as for
TRC, point-to-point. Only the exceptions will be described
in the following.
4.2.4.1.2.1 T̲i̲m̲e̲o̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
This function contains the following exceptions:
- Incoming traffic NICS TARE
- Outgoing traffic NICS TARE
Upon timeout on the functions listed above, the following
actions will take place.
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲t̲r̲a̲f̲f̲i̲c̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
A channel report will be forwarded to the Supervisor's
printer.
b) O̲u̲t̲g̲o̲i̲n̲g̲ ̲t̲r̲a̲f̲f̲i̲c̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
A channel continuity message will be sent to the
Outgoing Transport for transmission.
4.2.4.1.2.2 C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Command Control performs the same functions as
those specified for TRC, point-to-point except for
the following.
- Received a self-originated self-addressed channel
check.
A self-addressed channel message does not exist
on NICS TARE external channels.
- Flash Notification.
Preemption shall not take place on NICS TARE
external channels.
- Transmit an identical character report. This
shall not take place on NICS TARE external
channels.
4.2.4.1.3 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲,̲ ̲S̲C̲A̲R̲S̲/̲C̲C̲I̲S
The Transport Control for SCARS/CCIS external channels
contains the same main functional components as for
TRC, point-to-point. Only the exceptions will be described
in the following.
4.2.4.1.3.1 T̲i̲m̲e̲o̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
- Incoming traffic SCARS/CCIS
- Reception of Transaction Acknowledgement
Upon timeout on the functions listed above the following
actions will take place
a) Incoming traffic SCARS/CCIS
- A channel check message will be sent to the
Outgoing Transport for transmission.
b) Reception of Transaction Acknowledgement.
- The message awaiting Transsaction Acknowledgement
will be forwarded to the Outgoing Transport
for retransmission, except for a channel check
message where a channel report will be forwarded
to the Supervisor's printer. The channel status
will be set "closed".
4.2.4.1.3.2 C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Command Control performs the functions depicted
in figure 4.2.4-4 and those functions which are not
the same as for TRC, point-to-point will be described
in the following.
- Transmit a Transaction Acknowledgement. This
command is received from the Incoming Transport,
and it contains the TI of the received message.
This function will create a Transaction Acknowledgement
and forward it to the Outgoing Transport for
transmission.
4.2.4.1.4 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲,̲ ̲P̲T̲R̲
The Transport control for a PTR contains the following
main functional component command Control.
4.2.4.1.4.1 C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
Performs the following functions related to the commands
which will be received via the PTR command queue.
- Start-Up
- Close-Down
a) S̲t̲a̲r̲t̲-̲U̲p̲ procedures for the PTR has not yet been
identified.
b) C̲l̲o̲s̲e̲-̲D̲o̲w̲n̲ procedures for the PTR has not yet been
identified.
4.2.4.1.5 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲,̲ ̲P̲T̲P̲
The Transport Control for a PTP contains the following
main functional component
- Command Control
4.2.4.1.5.1 C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ performs the functions related
to the commands received by the Transport Control
subpackage from the following sources
- Conversion
- SSC
a) C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
- Flash notification.
The same procedure as for TRC, point-to-point will
be performed.
b) S̲S̲C̲
- start-up
- close-down
The functions listed above have not yet been identified.
FIGURE 4.2.4-1…01…TRANSPORT CONTROL…01…FUNCTIONAL BREAK-DOWN
FIGURE 4.2.4-2…01…TRANSPORT CONTROL…01…TRC, POINT-TO-POINT…01…FUNCTIONAL BREAK-DOWN
FIGURE 4.2.4-3…01…TRANSPORT CONTROL…01…NICS TARE, FUNCTIONAL BREAK-DOWN
FIGURE 4.2.4-4…01…TRANSPORT CONTROL,SCARS/CCIS…01…FUNCTIONAL BREAK-DOWN
FIGURE 4.2.4-5…01…TRANSPORT CONTROL…01…PTR, FUNCTIONAL BREAK-DOWN
FIGURE 4.2.4-6…01…TRANSPORT CONTROL…01…PTP, FUNCTIONAL BREAK-DOWN
4.2.4.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Transport Control is a coroutine working inside
a Transport Process. It serves a queue to which commands
are directed from other processes.
The queue consists of one subqueue only.
For each different Transport Process as specified in
section 4.1.2, there will be an associated Transport
Control Coroutine with slightly different capabilities.
In this section the structure of a general Transport
Control Coroutine will be specified. For functional
differences see section 4.2.4.1 for details.
Also see section 4.2.4.3 for data flow and control
logic.
4.2.4.2.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲1̲.̲0̲)̲
The Transport Control Module will perform the following
processing in an unlimited loop:
a) Receive the next queue-element from the Channel
Command Queue
b) Determine if the item received is the timer-event
expected once per minute.
c) If timer event, it will activate the time-out Control
Module.
d) If not timer event, it will activate the Command
Control Module.
e) Dismantle the queue element and wait for the next
command.
The structure of this module is the same as depicted
at the top level functional break-down illustrated
in section 4.2.4.1.
4.2.4.2.2 T̲i̲m̲e̲-̲O̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
This module is activated once per minute. The structure
is depicted in figure 4.2.4.2-1. It will then determine
if some timeout has occurred and take the proper action
upon that event.
The module will perform the following processing:
a) Check if the channel is available. If not, the
timer functions are suspended due to ordered close
down etc. and no further actions will be performed.
The Channel Status Check Module (2.1) will be activated
for that purpose.
b) The Time-out Maintenance Module (2.2) will then
be activated with the task to decrement all timer
values.
c) The Time-out Table will then be searched with the
purpose of determining if some time-out action
shall be taken.
The time-out actions are performed via a case structure.
The cases are corresponding to the record numbers
of the time-out table (see section 4.1.4 for organization).
The following modules are activated via this case structure:
- Generate Channel Check ASM (2.3.1)
- Generate Channel Number Reset (2.3.2)
- Channel Report (2.3.3)
- Retransmission (2.3.4)
4.2.4.2.3. C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲3̲.̲0̲)̲
The Command Control Module is responsible for handling
of all commands except the timer command. The structure
of this module is depicted in figure 4.2.4.2-2.
The command itself forms the basis for a sequence of
case structures, all associated to specific functions
whichin combination shall be performed.
The module performs the following processing:
a) Determines if the command is a Start-up.
If so, it will activate the start-up Module (3.1)
which in accordance with a subcommand indicating
the nature of start-up will activate the proper
sequence of modules relevant for that type of start-up.
b) If any parameters shall be updated the Parameter
update module (3.2) will be called.
It will maintain counters and flags on basis of
the command-type.
- Set Channel Open
- Set Channel Close
- Reset TSN
- Reset Timer
- Set Preemption
In accordance with reset of timer the entry in
the Time-out Table will first be calculated. For
the Set Preemption, it will first be calculated,
whether preemption shall take place or not.
c) If the command directly or indirectly applies for
automatic generation of an ASM, this will be done
via a Generate ASM Case structure with the following
separate modules:
- Generate Channel Open Module (3.3.1)
- Generate Channel Close Module (3.3.2)
- Generate Channel Continuity Module (3.3.3)
- Generate Self-addressed Channel Check Module
(3.3.4)
- Generate Channel Test Module (3.3.5)
- Generate Channel Test Reply Module (3.3.6)
- Generate Identical Character Module (3.3.7)
- Generate Flash Acknowledge Module (3.3.8)
- Generate Transaction Acknowledgement Module
(3.3.9)
All ASM-types that apply for automatic generation
have been specified. The menu of applicable
ASMs will of course depend on the Transport
Process in which this Transport Control Coroutine
shall operate, e.g. the module "Generate Self-addressed
Channel Check" will not be present in a SCARS/CCIS
Transport Control Coroutine.
d) A channel report shall in most cases be forwarded
to the supervisor. The Channel Report module (3.4)
will via a case-structure similar to the previously
described fulfil that job. This is considered as
one module.
e) If a timer has been reset or the channel has been
opened or closed the module for Log and statistics
(3.5) will be activated.
f) The Close-Down Module (3.6) will be activated in
a similar manner as described for the start-up
module.
It will have the capability for ordering the Outgoing
Transport to empty the queue for outgoing messages
waiting for transmission by returning them to conversion
for rerouting.
4.2.4.2.4 O̲t̲h̲e̲r̲ ̲M̲o̲d̲u̲l̲e̲s̲
In the previous description all modules have been mentioned.
The lowest level modules will be described in detail
during detailed design.
FIGURE 4.2.4.1-1…01…SOFTWARE STRUCTURE…01…TIME-OUT CONTROL
FIGURE 4.2.4.2-2…01…SOFTWARE STRUCTURE…01…COMMAND CONTROL
4.2.4.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.
The Control Logic is to some extend also illustrated
into the HIPO diagrams.
Control Logic related to the top level modules specified
in section 4.2.4.2.
- Transport Control
- Time-out Control
- Command Control
are specifically specified in the flowgrams also to
be found in this section.
For Logic related to the use of semaphores see section
4.1.3.
T̲R̲A̲N̲S̲P̲O̲R̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲1̲.̲0̲)̲
LOOP:
RECEIVE NEXT QEL FROM CCQ
TIMER-EVENT? TIME-OUT CONTROL (2.0)
COMMAND CONTROL (3.0)
DISMANTLE QEL CCQ
RETURN
T̲I̲M̲E̲-̲O̲U̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲2̲.̲0̲)̲
CHANNEL STATUS CHECK (2.1)
CHANNEL UNAVAILABLE?
TIME-OUT TABLE MAINTAINANCE (2.2)
SET UP START-POINTER TIMER-TABLE
LOOP TIMER-ENTRIES:
TIME-OUT? CASE TIMER-OUT OF:
1: CHANNEL CHECK
2: CHANNEL NUMBER RESET
3: CHANNEL REPORT
ELSE: RETRANSMISSION
END: TIME-OUT CASE
END LOOP TIMER-ENTRIES
RETURN
HIPO Diagrams
(nine pages)
4.2.4.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
The Transport Control Subpackage has no important private
data areas.
It mainly operates in the Time-Out Table specified
in section 4.1.6 under common data.
Apart from that a SCARS/CCIS Transport Control Coroutine
will have a data-area for generation of a Transaction
Acknowledgement. It is assumed that this type of acknowledgement
not shall be stored and it will therefore be convenient
to build up the acknowledgement in a buffer shared
with the corresponding Outgoing Transport coroutine.
4.2.4.4.1 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲m̲e̲n̲t̲ ̲B̲u̲f̲f̲e̲r̲
Length: 128 bytes
Size: 2 buffers (SCARS and CCIS)
Total: 156 bytes.
4.2.4.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
The environment of this subpackage is as depicted in
figure 4.2.4.5-1. This figure illustrates the other
subpackages of THP and Packages that the Transport
Control Subpackage interfaces to.
The other Subpackages and Packages interfaced to/from
this subpackage are:
- Outgoing Transport Subpackage (OTS)
- Incoming Transport Subpackage (ITS)
- ACP 127 Analysis Subpackage (AAS)
- ACP 127 Conversion Subpackage ACS)
- Terminal Package (TEP)
- System Status and Control (SSC)
- Log Package (LOG)
- Statistics Package (STP)
4.2.4.5.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲ ̲O̲T̲S̲ ̲(̲v̲i̲a̲ ̲S̲e̲m̲a̲p̲h̲o̲r̲e̲ ̲2̲)̲
T̲C̲S̲ ̲t̲o̲ ̲O̲T̲S̲:̲
a) Message for Retransmission
b) Automatically Generated ASM for transmission (not
PTP)
1) Channel Number Reset
2) Channel Continuity (not TRC)
3) Selfaddressed Channel Check (only TRC)
4) Channel Test (not SCARS/CCIS)
5) Channel Test Reply (not SCARS/CCIS)
6) Identical Character Report (only TRC)
7) Channel Open
8) Channel Close
9) FLASH Acknowledge
10) Transaction Acknowledgement (only SCARS/CCIS)
4.2.4.5.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲I̲T̲S̲
I̲T̲S̲ ̲t̲o̲ ̲T̲C̲S̲:̲
a) Command for automatic generation of Transaction
Acknowledgement on SCARS/CCIS channel.
4.2.4.5.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲A̲S̲
A̲A̲S̲ ̲t̲o̲ ̲T̲C̲S̲:̲
a) Command for automatic generation of the following
ASMs:
1) Flash Acknowledgement
2) Identical Character Report
3) Channel Test Reply
b) Command indicating receipt of the following ASMs:
1) FLASH Acknowledge
2) Selfaddressed Channel Check (self originated)
3) Channel Number Reset
4) Channel Test Reply indicating bad quality (ZBZ1)
5) Channel Close
6) Channel Open
4.2.4.5.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲C̲S̲
A̲C̲S̲ ̲t̲o̲ ̲T̲C̲S̲:̲
a) A command indicating that a message of precedence
flash has been queued for outgoing transport. Preemption
shall be considered (not NICS TARE)
4.2.4.5.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
T̲E̲P̲ ̲t̲o̲ ̲T̲C̲S̲:̲
a) Supervisor command for automatic generation of
the following ASMs:
1) Channel Open
2) Channel Close
T̲C̲S̲ ̲t̲o̲ ̲T̲E̲P̲
a) FLASH Acknowledge ASM not recognized to be printed
at the Supervisor Position (the flash message had
been retransmitted)
b) Channel Report to be printed at the Supervisor
Position.
1) Time-out Flash acknowledge
2) Outgoing Channel closed
3) Outgoing Channel opened
4) Incoming Channel Test ASM was garbled (ZBZ1)
5) Time-out selfaddressed channel check
6) Identical Character Report has been transmitted.
7) Incoming Channel opened
8) Incoming Channel closed
4.2.4.5.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲S̲C̲
S̲S̲C̲ ̲t̲o̲ ̲T̲C̲S̲:̲
a) Command for automatic generation of the following
ASMs:
1) Channel Open
2) Channel Close
4.2.4.5.7 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲O̲G̲
Outgoing message log when acknowledgement has been
received.
4.2.4.5.8 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲T̲P̲
a) Statistics outgoing message when acknowledgement
has been received.
b) Statistics channel availability upon channel open/close.
FIGURE 4.2.4.5-1…01…INTERFACES TRANSPORT CONTROL
4.2.5 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.5.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 functional responsibility of the Outgoing Transport
subpackage is to transport messages received from Conversion,
Analysis, Supervisor and Transport control, to the
external channels via IOC. The main functional components
contained within this subpackage are:
- Message assembly
- Message formatting
- Final transport
- Channel close down
These functional components are used to serve outgoing
traffic of messages on the following external channels.
1) TRC, point-to-point
2) NICS TARE
3) SCARS/CCIS
4) PTP
For the external channels listed above the functional
components are described in detail in the following
and depicted in figures 4.2.5-1 to 4.2.5-5.
4.2.5.1.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲,̲ ̲T̲R̲C̲,̲ ̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
The Outgoing Transport for TRC, point-to-point external
channels contain the following main functional components.
- Message assembly
- Message formatting
- Final transport
- Channel close down
4.2.5.1.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲
Creates the last message components which will be added
to the message before it can be transmitted and retrieval
keys will be created too. The subsequent functions
which will be performed are the following.
- FL1
- Pilot
- Page ID
- Retrieval keys
a) F̲L̲1̲. This function creates a format line 1 to all
messages which shall be transmitted. After creation
the TI of the message will be stored in view information
field. In case of retransmission, the new TSN will
be appended to the old TI. Upon creation of the
format line there will be used information from
- Message View: classification for UU or HH
- Global Serial Numbers: Transmission Serial
Number (TSN).
- System Parameters: 5 x space or 18 x space.
b) P̲i̲l̲o̲t̲. If the message requires a pilot, then this
function will create one and store it in field
"Pilot". Upon creation of the pilot the following
format lines will be used.
- FL2
- FL4
- FL1 without SOTF, Channel Designator and Transmission
serial number (TSN)
There will be inserted a suspected duplicate indicator
in FL4 within the pilot only (ZFD).
c) P̲a̲g̲e̲ ̲-̲ ̲I̲D̲. This function will create a page identification
to messages except for data messages. The page
ID will not be stored but buffered ready for insertion.
The information used for creation of the page ID
is as follows:
- FL3: Routing indicator of the station of origin
and station serial number.
- Message View: Security classification UNCLASS/CLEAR
d) R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲K̲e̲y̲s̲. This function will forward the
message view to SAR where generation of retrieval
keys will take place.
4.2.5.1.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
Performs insertion of message lines which will not
be stored and line blocking in the way required for
transmission via IOC. The functions contained within
message formatting are the following.
- Get message lines
- "BT" insertion
- Paging
- Line blocking
a) G̲e̲t̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲l̲i̲n̲e̲s̲ will read message lines from
online storage in the sequence of which they shall
be transmitted.
b) "̲B̲T̲"̲ ̲i̲n̲s̲e̲r̲t̲i̲o̲n̲. Will insert FL11 and FL13 in messages
except for abbreviated service messages (ASM).
c) P̲a̲g̲i̲n̲g̲. Will insert a message line containing an
End-of-page function (EOPF) and next a line containing
the page identification. The buffered page number
will be incremented ready for the next insertion.
d) L̲i̲n̲e̲ ̲b̲l̲o̲c̲k̲i̲n̲g̲. This function will create line blocks
to preceed each message line before they are handed
over to IOC for transmission.
The line block consists of 3 bytes as follows:
- Separator Byte used to recognize one line from
the next.
- Byte Count containing the number of bytes in
the message line.
- Flag Byte indicating the type of message line
e.g. control characters.
When the last message line has been line blocked
an additional line containing the EOTF will be
appended.
4.2.5.1.1.3 F̲i̲n̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Perform the following functions upon transmission of
messages
- Buffer control
- Output control
- Preemption
a) B̲u̲f̲f̲e̲r̲ ̲c̲o̲n̲t̲r̲o̲l̲ will take care of the sequence in
which the message lines and line blocks shall be
handed over to IOC for transmission.
b) O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ performs the command communication
between Outgoing Transport and IOS. This function
will, upon reception of a completion code for the
last part of message, generate the following.
For messages not requiring acknowledge
- Transport control will be ordered to generate
outgoing message log and statistics.
For messages requiring acknowledge
- Outgoing transport will insert the QEL referencing
the outgoing message in the time-out table
surrounded by the start of transaction time
and time-out value.
If output control receives a termination code from
IOS indicating that no further transmission can
take place, this will result in forwarding a request
to Transport Control for closing the outgoing channel.
…86…1 …02… …02… …02… …02…
c) P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲. If this is ordered from Transport Control,
then this function will determine whether preemption
shall take place or not.
If the Outgoing Transport performs transmission of
one of the following message types at the moment when
the order arrives, preemption will not take place.
- transmission of a flash message
- transmission of an ASM.
If there is less than the specified number of seconds
left of the transmission, then no preemption will take
place.
In the case where the Outgoing Transport performs transmission
of a message with precedence lower than flash and there
is more than the specified number of seconds left for
transmission, preemption will be performed in the following
way:
- Insertion oof a message line, containing the preemption
indicator (ZPH), as the last line in the next buffer
to be transmitted.
- The pointer to the preempted message will be sent
back into the semaphore.
Next step is to return to the semaphore for the
next message to be transmitted which will be the
message which caused preemption to take place.
4.2.5.1.1.4 C̲h̲a̲n̲n̲e̲l̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
The following events will cause the channel to be closed:.
1) A termination code returned from IOC indicating
that no further transmission can take place
(e.g. a line termination).
2) An order from Transport Control indicating
that the channel shall be closed. The order
will contain a time-limit for the close down..
To carry out the channel close down the following functions
are used
- Determine close procedure
- Drain semaphore
a) Determine close procedure. This function will determine
in which way the channel close down shall be performed
depended on the events listed above.
ad. 1) The Transport Control will be ordered to:
- decrement circuit availability counter
- set channel status "closed"
- generate channel report
- generate log record
- generate statistics record.
ad. 2) Depending on the time-limit given by the
order, the following will be performed:
- If the time-limit is less than the
transmission time for the buffer on
transmission at moment, nothing will
be done.
- If the time-limit is greater than
the transmission time for the buffer,
but less than the transmission time
for the rest of the message, the message
will be preempted by inserting a preemption
indicator as the first line of the
next buffer to be transmitted.
- If the time-limit is greater than
the transmission time for the rest
of the message, the transmission will
be finished.
b) Drain semaphore will read the semaphore and sort
the messages which may be contained by it. The
sorting will be performed in a way so that messages
coming from the Circuit Queue and those from Transport
Control which are not ASMs, will be forwarded to
the Conversion Queue.
4.2.5.1.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲,̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
The outgoing transport for NICS TARE external channels
contains the same main functional components as for
TRC, point-to-point. Only the exceptions are mentioned
in the following.
4.2.5.1.2.1 F̲i̲n̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲,̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
The exception contained within Final Transport is that
preemption shall not take place and will not be ordered
from Transport Control.
4.2.5.1.3 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲,̲ ̲S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲
The Outgoing Transport for SCARS/CCIS external channels
contains the same main functional components as for
TRC, point-to-point. Only the exceptions are mentioned
in the following.
4.2.5.1.3.1 M̲e̲s̲s̲a̲g̲e̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲
Because of the different types of message formats,
which shall be transmitted on the SCARS/CCIS external
channels the following functions are format depending.
- FL1
- Pilot E1
- Page ID
- Start/End of message block
a) F̲L̲1̲ Depending on the message format type the format
line 1 will be created with or without the SOTF
(VZCZC)
If format ACP127 then with SOTF
If format E1 then without SOTF
Otherwise the same procedure as for TRC, point-to-point.
b) P̲i̲l̲o̲t̲ ̲E̲1̲.̲ If the message requires a pilot such
one will be created after the specifications for
SCARS/CCIS.
c) P̲a̲g̲e̲-̲I̲D̲ shall only be created for the message type
specified for SCARS/CCIS.
d) Start/End of message block. This function will
create the start and end of message blocks which
will contain the following information.
- Block type
- Message type
- Message precedence
- Message classification
4.2.5.1.3.2 F̲i̲n̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
The exception contained within Final Transport is the
output control.
a) O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
The output control will perform the same functions
as specified for TRC, point-to-point and an additional
function which will perform the following upon
reception of the completion code from IOC for the
last part of the transmitted message.
Not depending on message type.
- Set pointer to the transmitted message in the
timeout table
- Start timeout upon reception of the corresponding
Transaction Acknowledgement
Wait in the semaphore 2 for further actions
4.2.5.1.4 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲,̲ ̲P̲T̲P̲
The outgoing transport for PTP external channel contains
the same main functional components as for TRC, point-to-point.
Only the exceptions are mentioned in the following.
4.2.5.1.4.1 M̲e̲s̲s̲a̲g̲e̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲ contains the following exceptions.
a) No FL1 will be created
b) No pilot will be generated
c) Start of tape. This function will
- create 20 cm of blank tape
- create a document control number to be punched
in front of the message
- create an additional 30 cm of blank tape.
4.2.5.1.4.2 M̲e̲s̲s̲a̲g̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ contains the following exceptions.
a) L̲i̲n̲e̲ ̲b̲l̲o̲c̲k̲i̲n̲g̲ will in addition to the functions
described for TRC, point-to-point, append additional
message lines containing blank characters enough
to create 30 cm of blank tape as an indication
of the end of message.
4.2.5.1.4.3 F̲i̲n̲a̲l̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ contains the following exceptions.
a) C̲o̲m̲m̲a̲n̲d̲ ̲c̲o̲n̲t̲r̲o̲l̲ will perform the same functions
as described for TRC, point-to-point, except for
the following.
- No use of timeout table because it does not
exist for the PTP external channel.
b) P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲ will perform the same procedures as
described for TRC, point-to-point but instead of
the additional message line containing ZPH it will
contain blank characters enough to show that preemption
has occured.
FIGURE 4.2.5-1…01…OUTGOING TRANSPORT…01…FUNCTIONAL BREAK-DOWN
FIGURE 4.2.5-2…01…OUTGOING TRANSPORT…01…TRC, POINT-TO-POINT…01…FUNCTIONAL BREAK-DOWN
FIGURE 4.2.5-3…01…OUTGOING TRANSPORT…01…NICS TARE, FUNCTIONAL BREAK-DOWN
FIGURE 4.2.5-5…01…OUTGOING TRANSPORT…01…PTP, FUNCTIONAL BREAK-DOWN
FIGURE 4.2.5-4…01…OUTGOING TRANSPORT…01…SCARS/CCIS, FUNCTIONAL BREAK-DOWN
4.2.5.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The Outgoing Transport is a coroutine working inside
a Transport Process. It serves an outgoing channel
to NICS TARE, TRC/Point-to-Point, SCARS, CCIS or PTP.
The input to an Outgoing Transport is delivered to
a Circuit Queue (CIQ), which may be shared with other
Outgoing Transport Coroutines (only NICS TARE). The
Circuit Queue is organized in a precedence structure
(6 subqueues).
For each different Transport Process as specified in
section 4.1.2 there will be an associated Outgoing
Transport Coroutine with almost identical capabilities
(except PTR). For functional differences see section
4.2.5.1 for details.
In this section the structure of a general Outgoing
Transport Coroutine will be specified.
The software structure is identical to the functional
break-down depicted in figures 4.2.5-1 to 4.2.5-5.
Also see section 4.2.5.3 for Data Flow and Control
Logic.
4.2.5.2.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
The outgoing Transport Module will perform the following
processing in an unlimited loop:
a) Receive the next queue element from the corresponding
circuit queue.
b) Activate the Message Assembly Module (2.1) which
will make the necessary initial preparations of
the transport. The next two modules will be activated
in a loop that terminates at end of message.
c) Message Formatting Module (2.2) reads and formats
pieces of the message into buffers.
d) Final Transport Module (2.3) Controls the communication
with IOC.
e) After each transport a check upon channel availability
will be performed. If the channel has been closed
during transport the Channel Close Down Module
(2.4) will be activated. This module will also
be activated in case of loss of control with IOC
during point d).
f) Finally the queue element from the Circuit Queue
will be dismantled unless a preemption has been
executed.
4.2.5.2.2 M̲e̲s̲s̲a̲g̲e̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲1̲)̲
The message Assembly Module is responsible for all
initial preparations related to the message before
the actual outgoing transport can begin.
It will fulfil its functions by activating the following
modules in sequence:
a) If the previously described module fulfils its
task successfully, a FL1 will be generated by activating
the Format Line 1 Module (2.1.2).
b) If the message has been marked for retransmission
a pilot will be generated by activating the pilot
module (2.1.3)
c) Finally the character sequence to be used during
paging will be generated by the Page ID Module
(2.1.4)
4.2.5.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲2̲)̲
The message formatting module is considered one module
with the following functional capabilities.
- read ahead from the message
- insert "BT", page identifications and other
format parameters
to format each FL into the format used by IOC.
The sequence of these activities will depend on the
moment of buffer allocation/exchange with the Final
Transport Module.
4.2.5.2.4 F̲i̲n̲a̲l̲ ̲t̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲3̲)̲
The Final Transport Module will during Transport maintain
the communication with IOC and perform the activities
related to a successful terminated transport. It is
activated when a buffer has been filled up by the message
formatting module.
It will process as follows:
a) Activate the Buffer Control Module (2.3.1) which
will determine which buffer shall be used and free
the other buffer for continuing refill by the Message
Formatting Module.
b) The output Control Module (2.3.2) will next be
activated and take care of the communication with
IOC.
C) When the buffer has been emptied by IOC, the Preemption
Module (2.3.3) will be activated. It will check
if preemption shall take place and initiate transmission
of the ZPH-sequence. If no preemption shall take
place the sequence a, b and c will be repeated
until EOTF.
d) The last activity is to call the module for retrieval-keys
(2.3.4) if the message shall not be acknowledged.
Otherwise references to the message will be inserted
into the time-out table and the transport control
will take over the responsibilitiy for the message.
4.2.5.2.5 C̲h̲a̲n̲n̲e̲l̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲3̲.̲4̲)̲
This module will be activated in case the communication
line for some reason should break down or if a close
down indirectly has been ordered via the Transport
Control.
a) In the first case it will set the channel closed
and report the event to the supervisor. In both
cases the circuit availability counter will be
decremented.
b) If this decrement gives the result that no channel
is available any more at that circuit, the circuit
queue will be emptied by directing all messages
to the ACP127 Conversion Subpackage for rerouting.
4.2.5.2.6 O̲t̲h̲e̲r̲ ̲M̲o̲d̲u̲l̲e̲s̲
At this point all modules included in an Outgoing Transport
Coroutine has either been described or mentioned. The
modules only mentioned will be described during detailed
design.
4.2.5.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 HIPO diagrams that follow this section illustrate
the Data Flow through this Subpackage.
The top level Control Logic is illustrated via Flogram
and also to some extent via the HIPO diagrams.
For the Logic related to the use of semaphores see
section 4.1.3 for details.
O̲U̲T̲G̲O̲I̲N̲G̲ ̲T̲R̲A̲N̲S̲P̲O̲R̲T̲
LOOP:
RECEIVE QEL FROM CIQ
OPEN LINE, IF FAULT
MESSAGE ASSEMBLY (2.1)
LOOP UNTIL END OF MESSAGE:
MESSAGE FORMATTING (2.2)
FINAL TRANSPORT (2.3)
PREEMPTION? EXIT LOOP
CHANNEL UNAVAILABLE? EXIT LOOP
END MESSAGE LOOP
CHANNEL CLOSE DOWN
(2.4)
DISMANTLE QEL CIQ
CHANNEL CLOSED?
CLOSE LINE
END LOOP
4.2.5.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Each Outgoing Transport Coroutine will apart from the
shared data elements, time-out table, and the Transaction
Acknowledgement Buffer specified respectively in section
4.1.6 and 4.2.4.4 have the following private data elements.
4.2.5.4.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲B̲u̲f̲f̲e̲r̲s̲
Length: 512 Byte
Number of buffers: 2
Size: 1024
Total: 33 x 1024 = 33.792 Bytes
The purpose of the two transport buffers is to keep
the transmission busy by filling one with data, while
the other buffer is used for transmission.
4.2.5.4.2 P̲a̲g̲e̲ ̲B̲u̲f̲f̲e̲r̲
Length 40 bytes
Total: 33 x 40 = 1320 bytes
The purpose of the page buffer is that it shall contain
the sequence of characters used during paging. It may
also be used to contain the character sequence for
preemption etc.
4.2.5.4.3 P̲o̲i̲n̲t̲e̲r̲ ̲B̲u̲f̲f̲e̲r̲
Length: 10 integers
Total: 33 x 20 = 660 bytes
The purpose of the pointer buffer is to contain references
to other buffers than the Transport Buffer. If the
page sequence or a "BT" etc. shall be inserted in a
transport buffer. This will be managed via a pointer
to be found in the pointer buffer.
4.2.5.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
The environment of this subpackage is as depicted in
figure 4.2.5.5-1.
This figure illustrates the other subpackages of THP
and Packages that the Outgoing Transport Subpackage
interfaces to. Also the external interfaces to this
subpackage are illustrated.
The other Subpackages and Packages interfaced to/from
this Subpackage are:
- Incoming Transport Subpackage (ITS)
- Transport Control Subpackage (TCS)
- ACP 127 Analysis Subpackage (AAS)
- ACP 127 Conversion Subpackage (ACS)
- Terminal Package (TEP)
- Storage and Retrieval (SAR)
4.2.5.5.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲I̲T̲S̲
I̲T̲S̲ ̲t̲o̲ ̲O̲T̲S̲:̲
a) Message for retransmission
b) Automatically generated ASM for transmission (not
PTP)
4.2.5.5.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲C̲S̲
T̲C̲S̲ ̲t̲o̲ ̲O̲T̲S̲
a) Message for retransmission
b) Automatic generated ASM for transmission (not PTP).
4.2.5.5.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲A̲S̲
A̲A̲S̲ ̲t̲o̲ ̲O̲T̲S̲:̲
a) Relayed outgoing message for transmission
b) Incoming selfaddressed Channel Check ASM (not self
originated) for transmission (only TRC)
c) Incoming Encrypted message to be punched at the
dedicated PTP for off-Line decryption.
4.2.5.5.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲C̲S̲
A̲C̲S̲ ̲t̲o̲ ̲O̲T̲S̲:̲
a) Outgoing messages in ACP 127-format for transmission.
b) Outgoing messages in SCARS/CCIS E1-format for transmission.
c) Messages for retransmission.
d) Outgoing plaindress messages for punch at the dedicated
PTP for off-line encryption.
e) Messages for repeated punch at the dedicated PTP.
O̲T̲S̲ ̲t̲o̲ ̲A̲C̲S̲:̲
a) Messages for rerouting due to channel unavailability.
4.2.5.5.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
T̲E̲P̲ ̲t̲o̲ ̲O̲T̲S̲:̲
a) Supervisor initiated rerun for retransmission.
O̲T̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲
a) Channel Report indicating that a transmission has
been prematurely terminated.
4.2.5.5.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲A̲R̲
a) Delivery of retrieval keys associated with outgoing
message.
FIGURE 4.2.5.5-1…01…INTERFACES OUTGOING TRANSPORT
4.3 M̲E̲M̲O̲R̲Y̲ ̲L̲A̲Y̲O̲U̲T̲
In this section the resource requirements related to
use of memory will be specified for the Traffic Handling
Package. The calculations for program size are based
upon an average module of 150 source statements.
The calculations for data size is an extract of the
specified Common Data and Subpackage Data
For each Subpackage it is estimated that the following
number of modules shall be developed:
ACP 127 Analysis 62
ACP 127 Conversion 35
Incoming Transport 15 (+3)
Transport Control 21 (+4)
Outgoing Transport 1̲6̲ ̲(̲+̲3̲)̲
Total 149 (159)
For each Transport process shall in addition be developed
at least one individual top level module = ( )
FIGURE 4.3.1…01…ANALYSIS PROCESS
FIGURE 4.3.2…01…CONVERSION-PROCESS
FIGURE 4.3.3…01…TRANSPORT PROCESS NICS TARE
FIGURE 4.3.4…01…TRANSPORT PROCESS TRC/POINT-TO-POINT
FIGURE 4.3.5…01…TRANSPORT PROCESS SCARS/CCIS
FIGURE 4.3.6…01…TRANSPORT PROCESS PTP
FIGURE 4.3.7…01…TRANSPORT PROCESS PTR
