top - download
⟦b7e9059f8⟧ Wang Wps File
Length: 65813 (0x10115)
Types: Wang Wps File
Notes: CPS/SDS/033
Names: »1981A «
Derivation
└─⟦c59a533be⟧ Bits:30006100 8" Wang WCS floppy, CR 0155A
└─ ⟦this⟧ »1981A «
WangText
…0f……00……00……00……00…8…0a……00……00…8…0b…4…05…3…00…3…05…3…06…3…07…2…08…2…09…2…0e…2 1…09…1…0d…1
0…09…0…0d…0 /…0a…/…00…/…05….…0b….…0f…. -…08…-…0d…-…00…-…05…,…0a…,…0f…, +…08…+…0c…+…0d……86…1 …02… …02…
…02…
…02…CPS/SDS/033
…02…831101…02……02…
TRAFFIC HANDLING
DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS
4.2.6 OUTGOING TRANSPORT SUBPACKAGE .............
4.2.6.l Functional Specification ..............
4.2.6.1.1 Outgoing Traffic Control ..........
4.2.6.1.1.1 Start Transport ...............
4.2.6.1.1.2 Stop Transport ................
4.2.6.1.1.3 Close Down ....................
4.2.6.l.l.4 Log Acknowledge ...............
4.2.6.l.l.5 ASM TRansmission ..............
4.2.6.l.2 Outgoing Message Handling .........
4.2.6.l.2.l Buffer Control ................
4.2.6.l.2.2 Tramsmission Start ............
4.2.6.l.2.3 Message Transmission ..........
4.2.6.l.2.4 Transmission End ..............
4.2.6.l.2.5 Paging of Long Messages .......
4.2.6.l.l.6 Preemption ...................
4.2.6.l.2.7 Log for Outgoing Messages .....
4.2.6.l.2.8 Statistics for Outgoing Message
4.2.6.l.3 Message Line Generation ...........
4.2.6.l.3.l ACP127 Format Line 1 ..........
4.2.6.l.3.2 ACP 127 Pilot .................
4.2.6.l.3.3 E1 - Pilot ....................
4.2.6.l.3.4 ACP127 Page Id ................
4.2.6.l.3.5 Pre-emption ...................
4.2.6.l.3.6 ACP127 Format Line 14 (Fl 14)
.
4.2.6.l.3.7 ACP127 Format Line 15 (Fl 15)
.
4.2.6.l.3.8 ACP127 Format Line 16 (Fl 16)
.
4.2.6.l.3.9 ACP127 Text Separators ........
4.2.6.l.3.l0 E1 Format Line B .............
4.2.6.l.3.11 PTP Dummy Formal Line 1 ......
4.2.6.1.3.12 Start of Tape Sequence .......
4.2.6.l.3.l3 End of Tape Sequence .........
4.2.6.l.3.14 PTP Pre-emption Sequence .....
4.2.6.l.3.15 Start of Message Black (SOM)
4.2.6.1.3.16 End of Message Black (EOM)
...
4.2.6.l.4 Automatic Generation of ASM .......
4.2.6.l.4.l ACP127 Format ?? ASM ..........
4.2.6.l.4.2 E1 Format for ASM .............
4.2.6.l.4.3 ASM for TRC/POIN TO POINT .....
4.2.6.l.4.4 ASM FOR NICS TARE .............
4.2.6.l.4.5 ASM FOR SCARS/CCIS ............
4.2.6.2 SOFTWARE STRUCTURE ....................
4.2.6.2.l Outgoing Traffic Control Module
...
4.2.6.2.2 Outgoing Start/Stop Control Module
4.2.6.2.3 Outgoing Message Handling Module
..
4.2.6.2.4 Outgoing Message Transmission .....
4.2.6.2.5 Message Line Generation Module
....
4.2.6.4.3.3 Module Components .............
4.2.6.4.3.4 Data Description ..............
4.2.6.4.3.5 Module Design ................
4.2.6.4.4 PTP Outgoing Traffic Control ......
4.2.6.4.4.1 Functional Specification ......
4.2.6.4.4.2 Module Interface ..............
4.2.6.4.4.3 Module Components .............
4.2.6.4.4.4 Data Descriptions .............
4.2.6.4.4.5 Module Design .................
4.2.6.4.5 Outgoing Start Stop Control .......
4.2.6.4.5.1 Functional Specification ......
4.2.6.4.5.2 Module Interface ..............
4.2.6.4.5.3 Module Components .............
4.2.6.4.5.4 Data Descriptions .............
4.2.6.4.5.5 Module Design ................
4.2.6.4.5 TRC/PTOP Outgoing Message Handling
4.2.6.4.5.1 Functional Specification ......
4.2.6.4.5.2 Module Interface .............
4.2.6.4.5.3 Module Components .............
4.2.6.4.5.4 Data Description ..............
4.2.6.3 Data FLOW AND CONTROL LOGIC ...........
4.2.6.3.l Introduction ......................
4.2.6.3.2 Receive Buffer for External Message
4.2.6.3.3 Outgoing Control Marks ............
4.2.6.4 MODULE SPECIFICATION ..................
4.2.6.4.l TRC/P TO P OUTGOING TRAFFIC CONTROL
4.2.6.4.1.1 Functional Specification ........
4.2.6.4.1.2 Module Interface ..............
4.2.6.4.l.3 Module Components .............
4.2.6.4.l.4 Data Descriptions .............
4.2.6.4.l.5 Module Design ................
4.2.6.4.2 NICS TARE Outgoing Traffic Control
4.2.6.4.2.l Functional Specification ......
4.2.6.4.2.2 Module Interface ..............
4.2.6.4.2.3 Module Components .............
4.2.6.4.2.4 Data Description ..............
4.2.6.4.2.5 Module Design .................
4.2.6.4.3 SCARS/CCIS Outgoing Traffic Control
4.2.6.4.3.1 Functional Specification ......
4.2.6.4.3.2 Module Interface ..............
4.2.6 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.6.l F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Outgoing Transport Subpackages (OTS) supplies the
modules for handling of the outgoing traffic of messages.
The outgoing messages are received through the Circuit
Queue (CIQ) related to the transport subprocess.
Furthermore the OTS will construct and transmit the
Abreviated Service Messages (ASM), which are ordered
from the Transport Control (TCS).
The OTS supports the following types of outgoing transport:
TRC/POINT TO POINT
NICS TARE
SCARS/CCIS
PTP
Each transport subprocess has its own OTS-function,
which is running independent of the other subprocesses
(ref. section 4.2.3).
The functional components of the OTS are devided into
the following main groups:
Outgoing Traffic Control
Outgoing Message Handling
Message Line Generation
Automatic ASM Generation
The functional components mentioned above are described
in the following sections, and depicted on figure 4.2.6-l
to 4.2.6-4.
fig. 4.2.6-l…86…1 …02… …02… …02… …02…
fig. 4.2.6-2
fig. 4.2.6-3
fig. 4.2.6-4
4.2.6.1.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Outgoing Traffic Control takes care of the functions
related to the operations, which are received from
the Transport Control (TCS). A general description
of these operations is given in section 4.2.3.7.
4.2.6.1.1.1 S̲t̲a̲r̲t̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
This operation works as a start-up for the Outgoing
Transport, which initiates the transfer of messages
from the Circuit Queue.
4.2.6.1.1.2 S̲t̲o̲p̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
This operation will immediately stop the activity of
the outgoing transport.
If all channels related to the circuit queue has been
closed at this moment, the OTS will return all messages
in the queue to the Conversion for rerouting.
In the PTP transport, all messages will stay in the
circuit queue during a stop.
The OTS acknowledge the operation to the Transport
Control and remain passive until a new start Transport
operation is received, i.e. it will not initiate any
new transfer of messages from CIQ.
4.2.6.1.1.3 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
This operation indicates that the OTS shall stop all
activities. The operation contains two possibilities:
INIT CLOSE DOWN
FINAL CLOSE DOWN
a) I̲n̲i̲t̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
If a transmission takes place it will be completed.
The Init Close Down is always followed by a Final
Close Down.
No new transfer of messages from the circuit queue
is initiated.
b) F̲i̲n̲a̲l̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
The OTS acts as if a Stop Transport has been received
(see 4.2.6.1.1.2).
The final Close Down is always followed by a System
Init.
The OTS will not start any transmission before
a start operation is received from the Transport
Control.
4.2.6.l.l.4 L̲o̲g̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲
This operation indicates that the LOG Package has accepted
a log record for an outgoing message.
If the message has been received from the circuit queue,
the OTS will dismantle the queue element. Note however
the following exceptions:
a) A flash message requiring a flash receipt is not
dismantled until the receipt has been received.
b) A message from SCARS/CCIS is not dismantled until
the Transaction Acknowledge has been received.
If no ASM transmission has been requested from the
TCS, the OTS will inititate a new transfer from The
Circuit Queue.
4.2.6.l.l.5 A̲S̲M̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
This operation will make the OTS generate and transmit
the ASM, which is specified in the operation.
If the OTS is transmitting a message this will be completed
before transmission of the ASM
When the ASM has been transmitted the OTS sends an
acknowledge to Transport Control.
If the outgoing traffic is closed only the following
ASM will be transmitted:
QRV : Open Incoming Traffic
QRT : Close Incoming Traffic
INT ̲ZBZ : Channel Test
ZBZ-N : Channel Test Reply
4.2.6.l.l.6 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲
This operation is only defined for SCARS/CCIS Outgoing
Transport. Two possibilities exists:
a) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲ ̲R̲e̲c̲e̲i̲v̲e̲d̲
In this case a legal transaction acknowledge has
been received. The OTS will initiate a new transfer
of a message from the Circuit Queue.
b) T̲i̲m̲e̲o̲u̲t̲ ̲f̲o̲r̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲k̲n̲o̲w̲l̲e̲d̲g̲e̲
The OTS will retransmit the message for which the
timeout has occured.
If the maximum number of retransmissions is reached,
the OTS transfers a report to the Supervisor Printer.
4.2.6.l.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The Message Handling contains the functions which are
related to the basic flow control of messages through
the Outgoing Transport.
The message received from the Circuit Queue has been
stored in the External Message Format (EMF) containing
four fields:
a) ACPl27 Parameter Field
b) Header Field
c) Text Preamble Field
d) Text Field
First the OTS will read the Parameter Field which specifies
a number of parameters necessary for transmission of
the message.
Then the OTS will read and transmit the other fields
in the sequence indicated above.
The message may not contain any Text Preamble and/or
Text.
4.2.6.l.2.l B̲u̲f̲f̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Buffer Control supplies the functions necessary
for receiving messages from the Circuit Queue and assignment
of Buffers for transmission of messages through IOC.
The structure of these functions is described in section
4.2.6.3.
4.2.6.l.2.2 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲S̲t̲a̲r̲t̲
This component includes the functions which take place
when a new message has been received from the Circuit
Queue.
a) T̲R̲C̲/̲P̲O̲I̲N̲T̲ ̲T̲O̲ ̲P̲O̲I̲N̲T̲
If the outgoing channel is closed the message is
returned to conversion for rerouting. The logical
circuit number is inserted into the queue element
following the message in order to indicate the
circuit from which the transport was closed.
If the outgoing channel is open the OTS will initiate
the following actions:
- Construction of a Message Control Mask indicating
the type of message lines which are to be supplied
by the OTS.
- Start-up of message transmission according
to the Message Control Mask.
b) N̲I̲C̲S̲ ̲T̲A̲R̲E̲
If the outgoing channel is closed, the message
from CIQ is only returned for rerouting if all
channels within the circuit have been closed. If
at least one channel is open, the message is returned
to CIQ, in order to let another NICS TARE subprocess
transmit the message.
If the outgoing channel is open the start actions
are the same as for TRC/POINT TO POINT.
c) S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲
The channel is always open. A Message Control Mask
indicating the sequence of message line transmission
is constructed. The mask also indicates the type
of message lines which are to be supplied by the
OTS.
d) P̲T̲P̲
The channel is always open. The start action is
the same as for TRC/POINT TO POINT. Note however,
that the message lines to be supplied differ from
TRC/ POINT TO POINT.
4.2.6.l.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
The Message Transmission functions control the sequence
of message lines which are transferred to IOC for transmission
on the outgoing channel.
The sequence is established by a Message Control Mask
constructed prior to the start of transmission.
4.2.6.l.2.4 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲E̲n̲d̲
When the IOC has returned a completion code for transmission
of the last line, the OTS will activate the following
actions:
a) T̲R̲S̲/̲P̲O̲I̲N̲T̲ ̲T̲O̲ ̲P̲O̲I̲N̲T̲
- a procedure for generation of a log record
is called. (ref. 4.2.6.1.2.7).
- a procedure for generation of a record for
statistics is called. (ref. 4.2.6.1.2.8)
- a procedure for storage of a message is called.
(ref. 4.2.6.1.2.9)
- if the message transmitted is a flash message,
a timer is activated in the local timer table.
The TSN of the message and the QEL-Reference
(to circuit queue)is assigned to the timer.
The timer is not activated if the queue element
referencing the message specifies that the
flash message shall not be acknowledged.
- If the TCS has requested transmission of an
ASM the OTS will construct and transmit the
ASM.
b) N̲I̲C̲S̲ ̲T̲A̲R̲E̲
As for TRS/POINT TO POINT.
A timer related to the transmission of the Continuity
Message (ASM) is activated in the local timer table.
c) S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲
- Procedures for generation of records for log,
statistics and message storage are called.
- A timer for supervision of the return of the
Transaction Acknowledge is activated in the
local timer table.
d) P̲T̲P̲
- Procedure for generation of log record is called.
4.2.6.l.2.5 P̲a̲g̲i̲n̲g̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
If the message received from CIQ is to be devided into
pages, the OTS will insert a page function for each
20 lines as described below.
l) R̲e̲l̲a̲t̲e̲d̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The first page shall consist of Format lines 1,2,3
and 4 and the succeeding 20 lines.
2) All other pages of the message shall consists of
not more than 20 lines.
3) From the second page onwards each page shall be
identified by a page identifier as defined in section
4.2.6.1.3.4.
4) Machine functions used between pages shall be 2
CR and 4 LF.
The procedure above is only activated if the queue
element following the message from CIQ indicates
that the message are to be divided into pages.
The parameters necessary for construction of the
"Page ID Lines" are supplied in the ACP127 Parameter
Field in the External Message Format containing
the message. The page number is generated by means
of a local counter.
Note: The text end separator "BT" is always included
in the page containing the last text line.
4.2.6.l.2.6 P̲r̲e̲-̲e̲m̲p̲t̲i̲o̲n̲ ̲
For each line transferred to IOC the OTS examines if
the pre-emption indicator (PRE-EMPT) has been updated
by the TCS. If so, the transmission may be interrupted
by inserting a specific sequence of characters (ref.
4.2.6.1.3.5 and 4.2.6.1.3.14).
A pre-empted message is returned to the circuit queue
with a mark in its queue element indicating that the
message shall be supplied with a pilot next time it
is transmitted
If the message already contains a Pilot, this has been
marked in its queue element.
Each time a message is preempted, a report is forwarded
to the supervisor's printer.
Two types of pre-emption procedures are included:
a) S̲t̲o̲p̲ ̲P̲r̲e̲-̲e̲m̲p̲t̲i̲o̲n̲
Unconditional pre-emption used by the TCS when
a Stop or Final Close Down command has been received
from SSC. The stop Pre-emption indicates an immediately
stop of the outgoing transmission.
This type of pre-emption is included in the Outgoing
Transport for TRC/POINT TO POINT, NICS TARE, SCARS/CCIS
and PTP.
b) F̲l̲a̲s̲h̲ ̲P̲r̲e̲-̲e̲m̲p̲t̲i̲o̲n̲
Conditional pre-emption used by the TCS when a
Flash Notification command has been received from
the Conversion or the Analysis.
Pre-emption only takes place if:
- The message to pre-empt is not a flash message
or an ASM generated by OTS.
- The circuit queue contains at least one flash
message.
This type of pre-emption may occur for TRC/POINT
TO POINT, SCARS/CCIS and PTP.
4.2.6.l.2.7 L̲o̲g̲ ̲f̲o̲r̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
This function creates a log record when the end of
a message has been transferred to the IOC for transmission.
The OTS will wait for a log acknowledge from the Transport
Control before a new message is transmitted.
Note: Log records are generated for all outgoing
messages including ASM's generated by OTS (except
Transaction Acknowledge for SCARS/CCIS).
4.2.6.l.2.8 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲f̲o̲r̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
This function creates a record with statistic information
when a message has been transmitted.
The record is transferred to STP through a System Call.
Note: Statistics are generated for all outgoing messages
including ASM's generated by OTS (except Transaction
Acknowledge for SCARS/CCIS).
No statistics are generated for PTP transport.
4.2.6.l.2.9 S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
This function creates the Retrieval Keys for storage
of a message which has been transmitted.
Retrieval Keys are n̲o̲t̲ generated for the following
types of messages:
- VDU Page to SCARS/CCIS
- COMMENTS to SCARS/CCIS
- ASM generated by OTS
- Messages with a queue element profile, which indicates
one of the following possibilities: Encrypted message,
Classification = CTS or Special
Handling Designator = ATOMAL.
Retrieval keys contains the elements:
- Storage Type
- Channel Designator
- Transmission Serial Number
Retrieval keys are stored into the queue element following
the message to SAR (i.e. ISQ).
Note: No storage is made for messages transmitted
by PTP outgoing transport.
4.2.6.l.3 M̲e̲s̲s̲a̲g̲e̲ ̲L̲i̲n̲e̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
Before the OTS transmits a message on the outgoing
channel, it will insert a number of message lines which
are not included in the External Message Format received
from the Circuit Queue (CIQ).
The lines inserted by OTS are all related to the framing
of the message to make it follow ACP127/E1 standard.
The following sections give a short description of
the lines inserted by OTS.
4.2.6.l.3.l A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲1̲
This function inserts the first message line for all
messages which are to be transmitted according to ACP
127 standard.
The line contains the following components.
SOTF DESIGNATOR TSN 5 or 18 spaces UU or HH EOLF
.
A detailed description of the line components are given
in ICD 003.
For flash messages to TRC/P to P the OTS will insert
a bell signal after format line 1 specified above (i.e.
in front of format line 2).
4.2.6.l.3.2 A̲C̲P̲ ̲1̲2̲7̲ ̲P̲i̲l̲o̲t̲
The OTS will insert a pilot in front of the message
if this is specified in the queue element following
the messages from the circuit queue.
The following lines are inserted according to ACP127
standard.
1) F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲A̲ (Fl A)
Equivalent to format line 1 (sec. 4.2.6.1.3.1)
2) F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲B̲ (Fl B)
Equivalent to format line 2 of the message. The
ACP127 Parameter Field of the External Message
Format includes a pointer to Fl 2.
3) F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲C̲ ̲(̲F̲l̲ ̲C̲)̲
Equivalent to format line 4 of the message extended
with a suspected duplicate indicator, i.e. terminated
with the following sequence:
Space ZFD Space DE RI
If the extension above makes Fl C exceed, the maximum
line length, only " space ZFD " is inserted.
If this is not possible no extension is made, i.e.
Fl C equal to Fl 4.
DE RI is CAMPS DE RI as defined in the NETWORK
PARAMENTER.
To make the OTS able to construct Fl C the ACP127
Parameter Field of the External Message Format
includes a pointer to Fl 4.
4) F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲1̲A̲
Fl C of a Pilot is followed by the last sequence
at a normal ACP127 Format Line l (see 4.2.6.1.3.1):
5 space UU or HH EOLF
4.2.6.l.3.3 E̲1̲ ̲-̲ ̲P̲i̲l̲o̲t̲
If the transmission is in E1-format (only for SCARS/CCIS)
a comparable pilot is inserted if specified by the
queue element following the message from the circuit
queue.
This is done by changing the Message Type (received
from the ACP127-Parameter-Field) into a new type which
is stored in the start of Message Block.
The following conversion is used:
M̲e̲s̲s̲a̲g̲e̲ R̲e̲c̲e̲i̲v̲e̲d̲ ̲t̲y̲p̲e̲ N̲e̲w̲ ̲T̲y̲p̲e̲
Display, E1 'C' 'O'
Comments, E1 'D' 'P'
Narrative Msg.E1 'M' 'Q'
Data Msg,E1 'N' 'R'
Furthermore the operating signal 'ZFD' is appended
to the first line (format line b) as follows:
designator TSN /ZFD
The Outgoing Transport automatically append the E1-Pilot
if the message is retransmitted.
4.2.6.l.3.4 A̲C̲P̲1̲2̲7̲ ̲P̲a̲g̲e̲ ̲I̲d̲
If the message is to be divided into pages the OTS
will insert a Page Id in front of each page.
Each time a new page is transmitted the following lines
are inserted:
1) P̲a̲g̲e̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Pages are separated by the following function:
2 CR 4LF
2) P̲a̲g̲e̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Page SP Page Number SP DE RI SSN SP Classific,
Page Number : Maintained by OTS
DE RI : Station of origin
SSN : Station Serial Number
Classific : Security Classification
The parameters above are all specified in the ACP127
Parameter Field of the External Message Format.
The Line component classific is equivalent to one
of the following text strings:
0) NATO UNCLAS
1) N A T O R E S T R I C T E D
2) N A T O C O N F I D E N T I A L
3) N A T O S E C R E T
4) C O S M I C T O P S E C R E T
5) CLEAR
4.2.6.l.3.5 P̲r̲e̲-̲e̲m̲p̲t̲i̲o̲n̲
Each time the transmission of a message is pre-empted
the OTS will insert the following lines (except for
PTP transport).
ZPH space ZPH EOLF
End of transmission function
4.2.6.l.3.6 A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲1̲4̲ (Fl 14)
The OTS will insert Fl 14 at the end of encrypted message
received from the Circuit Queue
The following sequence is inserted:
GR Group Count EOLF
where Group Count is a number (0-9999) included in
the ACP127 Parameter Field of the External Message
Format.
FL14 is only appended if Text Preamble Field or Text
Field is available.
4.2.6.l.3.7 A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ 15 (Fl 15)
The OTS will insert Fl 15 at the end of a message received
from the Circuit Queue (except for VDU page or comments
for SCARS/CCIS).
The following sequence is inserted:
Station Serial Number EOLF ,
where Station Serial Number (0-999) is included in
the ACP127 Parameter Field at the External Message
Format.
FL15 is only appended if Text Preamble Field or Text
Field is available.
4.2.6.l.3.8 A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲1̲6̲ (Fl 16)
The OTS will insert Fl 16 at the end of a message received
from the Curcuit Queue (also when pre-emption takes
place).
The following sequence is inserted:
7 line feeds
NNNN EOLF
12 letter shifts
4.2.6.1.3.9 A̲C̲P̲1̲2̲7̲ ̲T̲e̲x̲t̲ ̲S̲e̲p̲a̲r̲a̲t̲o̲r̲s̲
If a message includes a Text-field,the OTS will insert
the following sequence in front of the text part and
after the text part.
BT EOLF
Note: If the message contains a Text Preamble the
first seperator (BT) is inserted in front of
the first line of this field.
4.2.6.l.3.10 E̲1̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲B̲
This function inserts the first message line for all
messages which are to be transmitted according to E1
standard.
The line contains the following components:
Channel Designator TSN EOLF
An operating signal 'ZFD' is appended if the message
shall contain a 'pilot' (ref. 4.2.6.l.3.3).
4.2.6.l.3.11 P̲T̲P̲ ̲D̲u̲m̲m̲y̲ ̲F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲1̲
This function may insert the first message line for
messages which are to be transmitted to the PTP.
The queue element following the message from the Circuit
Queue specifies if the function shall be activated.
The line contains the following components:
VZCZC EOLF
(see also 4.2.6.4.11).
4.2.6.1.3.12 S̲t̲a̲r̲t̲ ̲o̲f̲ ̲T̲a̲p̲e̲ ̲S̲e̲q̲u̲e̲n̲c̲e̲
Before a message is transmitted to PTP, the OTS will
insert a sequence of specific characters which appear
as a readable Document Control Number and 20 cms of
blank tape.
The sequence is inserted in front of the message. The
Document Control Number contains digits (0001-9999).
4.2.6.l.3.l3 E̲n̲d̲ ̲o̲f̲ ̲T̲a̲p̲e̲ ̲S̲e̲q̲u̲e̲n̲c̲e̲
When a message has been transmitted to PTP, the OTS
will append a sequence of specific characters which
appear as 30 cms of blank tape.
4.2.6.l.3.14 P̲T̲P̲ ̲P̲r̲e̲-̲e̲m̲p̲t̲i̲o̲n̲ ̲S̲e̲q̲u̲e̲n̲c̲e̲
If a message for PTP is pre-empted, the OTS will append
a sequence of specific characters which appear as:
1) 10 cms of blank tape
2) ZHP (readable characters)
3) 10 cms of blank tape
4.2.6.l.3.15 S̲t̲a̲r̲t̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲B̲l̲o̲c̲k̲ ̲(̲S̲O̲M̲)̲ ̲
The communication with IOC requires that a special
Start of Message block shall be transferred in front
of each message going to NICS TARE or SCARS/CCIS.
The SOM block for SCARS/CCIS shall also be supplied
with the message type and the precedence delivered
by the ACP127 Parameter Field of the External Message
Format.
4.2.6.1.3.16 E̲n̲d̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲B̲l̲o̲c̲k̲ ̲(̲E̲O̲M̲)̲
The communication with IOC requires that a special
End of Message block shal be tranferred at the end
of each message going to NICS TARE and SCARS/CCIS.
4.2.6.l.4 A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲A̲S̲M̲
4.2.6.l.4.l A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲A̲S̲M̲
Abbreviated Service Message formats will contain the
ACP127 message format lines 1,2,3,4,12g, and 16. The
ASM have the following general layout:
FL 1 VZCZC(TI)(5xsp)UU(EOLF)
FL 2 (XX) (sp) (TO RI) (EOLF)
FL 3 DE(sp) FROM RI (sp) (0000)(sp) (TOF) (EOLF)
FL 4 ZNR(sp)UUUUU(EOLF)
FL 12g (Text)
FL 16 (EOTF)
Where:
TI is the station and channel designator (3
characters) plus the channel serial number
(3 or 4 digits)
XX is the repeated precedence prosign
"TO RI" is the Routing Indicator of the receiver
station(stored in Channel Profile).
"FROM RI" is the Routing Indicator of the transmitter
station (stored in Network Table).
SSN is the originating station serial number.
CAMPS will not generate a SSN when transmitting
an ASM. When receiving an ASM the SSN is
optional.
TOF is the Julian data (NNN) and time group
(NNNN). (Time of filing).
"Text" is format text
EOLF is two carriage return, line feed
EOTF is two carriage return, eight line feeds,
end-of-message indicator (NNNN) and twelve
letter shift characters.
4.2.6.l.4.2 E̲1̲ ̲F̲o̲r̲m̲a̲t̲ ̲f̲o̲r̲ ̲A̲S̲M̲
Abbreviated Service Messages for CCIS will contain
E1 format lines B,C,D1, 12g and 16, and have the following
general layout:
FL B (TI) (EOLF)
FL C SPECIAL (sp) UUUUU (EOLF)
FL D1 PREC (sp) R (EOLF)
FL 12g (Text) (EOLF)
FL 16 (EOTF)
Where:
TI, Text, EOLF and EOTF have the same meaning as for
ACP 127 ASM format described in 4.2.6.1.4.1
4.2.6.l.4.3 A̲S̲M̲ ̲f̲o̲r̲ ̲T̲R̲C̲/̲P̲O̲I̲N̲T̲ ̲T̲O̲ ̲P̲O̲I̲N̲T̲
C̲O̲N̲S̲E̲C̲U̲T̲I̲V̲E̲ ̲I̲D̲E̲N̲T̲I̲C̲A̲L̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲S̲
VZCZC(TI) (5xsp)UU(EOLF)
OO(sp)(TRC/P-to-P RI) (EOLF)
DE(sp)(CAMPS RI) (sp)(TOF) (EOLF)
ZNR(sp)UUUUU(EOLF)
ZBC(sp)(channel designator of faulty channel)(EOLF)
(EOTF)
F̲L̲A̲S̲H̲ ̲R̲E̲C̲E̲I̲P̲T̲
VZCZC(TI)(5xsp)UU(EOLF)
OO(sp)(TRC/P-to-P RI)(EOLF)
DE(sp)(CAMPS RI)(sp)TOF)(EOLF)
R(sp)Z(sp)(TI of FLASH Message)(EOLF)
(EOTF)
S̲E̲L̲F̲-̲A̲D̲D̲R̲E̲S̲S̲E̲D̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲C̲H̲E̲C̲K̲
VZCZC(TI)(5xsp)UU(EOLF)
OO(sp)(CAMPS RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
CHANNEL CHECK (EOLF)
(EOTF)
Z̲I̲D̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(TRC, P-to-P RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
ZID(sp)(TI of last msg. from TRC/P to P prior to reset)(EOLF)
(EOTF)
Q̲R̲V̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(TRC/P-to-P RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
QRV(sp)(S&CD)(EOLF)(see Note)
(EOTF)
Note: If the channel has been disconnected, the moment
of transport stop is appended.
Q̲R̲T̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
OO(sp)(TRC/P-to-P RI)(EOLF
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
QRT(sp)(S&CD)(sp)(9xA)(EOLF) (See note for QRV ASM)
(EOTF)
Z̲B̲Z̲ ̲(̲N̲)̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(TRC/P-to-P RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
ZBZ(N)(EOLF)
(EOTF)
I̲N̲T̲ ̲Z̲B̲Z̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(TRC/P-to-P RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
TEST(sp)THE(sp)QUICK(sp)BROWN(sp)(FOX(sp)JUMPS(sp)OVER(sp)THE
(sp)LAZY(sp)DOG(sp)(EOLF)
1234567890(sp)RYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYR(EOLF)
INT(sp)ZBZ(EOLF)
(EOTF)
4.2.6.l.4.4 A̲S̲M̲ ̲F̲O̲R̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲
F̲L̲A̲S̲H̲ ̲R̲E̲C̲E̲I̲P̲T̲
VZCZC(TI)(5xsp)UU(EOLF)
OO(sp)(NICS TARE RI)(EOLF)
DE(sp)CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
R(sp)Z(sp)(TI of FLASH Message)(EOLF)
(EOTF)
C̲H̲A̲N̲N̲E̲L̲ ̲C̲O̲N̲T̲I̲N̲U̲I̲T̲Y̲ ̲M̲E̲S̲S̲A̲G̲E̲
VZCZC(TI)(5xps)UU(EOLF)
OO(sp)(NICS TARE RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
CHANNEL CHECK (EOLF)
(EOTF)
Z̲I̲D̲ ̲A̲S̲M̲
VZCZC(TI)5xsp)UU(EOLF)
RR(sp)(NICS TARE RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF
ZNR(sp)UUUUU(EOLF
ZID(sp)(TI of last msg. from TARE prior to reset)(EOLF)
(EOTF)
Q̲R̲T̲ ̲A̲S̲M̲
VZCZC(TI) (5xsp)UU(EOLF)
OO(sp) (NICS TARE RI) (EOLF)
DE(sp) (CAMPS RI) (sp) (TOF) (EOLF)
ZNR(sp)UUUUU(EOLF)
QRT(sp) (S&CD) (sp) (9xA) (EOLF) (See Note for QRV
ASM)
(EOTF)
Q̲R̲V̲ ̲A̲S̲M̲
VZCZC(TI)(5xps)UU(EOLF)
RR(sp)(NICS TARE RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
QRV(sp)(S&CD)(EOLF) (See Note)
(EOTF)
Note: If the channel has been disconnected, the moment
of transport stop is appended.
Z̲B̲Z̲ ̲(̲N̲)̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(NICS TARE RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
ZBZ(N)(EOLF)
(EOTF)
I̲N̲T̲ ̲Z̲B̲Z̲ ̲A̲S̲M̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(NICS TARE RI)(EOLF)
DE(sp)(CAMPS RI)(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
TEST(sp)THE(sp)QUICK(sp)BROWN(so)FOX(sp)JUMPS(sp)OVER(sp)
THE(sp)LAZY(sp)(DOG(sp)(EOLF)
1234567890(sp)*U*U*U*U*U*U*U*U*U*U*U*U(EOLF)
INT(sp)ZBZ(EOLF)
(EOTF)
4.2.6.l.4.5 A̲S̲M̲ ̲F̲O̲R̲ ̲S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲
T̲R̲A̲N̲S̲A̲C̲T̲I̲O̲N̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲
(TI of transaction to be acknowledged)(EOLF)
A̲C̲P̲1̲2̲7̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲C̲H̲E̲C̲K̲ ̲M̲E̲S̲S̲A̲G̲E̲
VZCZC(TI)(5xsp)UU(EOLF)
RR(sp)(SCARS RI(EOLF)
DE(sp)(CAMPS RI)(sp)0000(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
CHANNEL CHECK(EOLF)
(SC ̲EOTF)
A̲C̲P̲1̲2̲7̲ ̲F̲I̲N̲A̲L̲ ̲N̲U̲M̲B̲E̲R̲ ̲R̲E̲P̲O̲R̲T̲ ̲M̲E̲S̲S̲A̲G̲E̲
VZCZC(CD)001(5xsp)UU(EOLF)
RR(sp)(SCARS RI)(EOLF)
DE(sp)(CAMPS RI)(sp)0000(sp)(TOF)(EOLF)
ZNR(sp)UUUUU(EOLF)
ZID(sp)(TI of last transmitted message)(EOLF)
(SC ̲EOTF)
E̲1̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲C̲H̲E̲C̲K̲ ̲M̲E̲S̲S̲A̲G̲E̲
(TI)(EOLF)
SPECIAL(sp)UUUUU(EOLF)
PREC(sp)R(EOLF)
CHANNEL CHECK(EOLF)
(SC ̲EOTF)
E̲1̲ ̲F̲I̲N̲A̲L̲ ̲N̲U̲M̲B̲E̲R̲ ̲R̲E̲P̲O̲R̲T̲ ̲M̲E̲S̲S̲A̲G̲E̲
(TI)(EOLF)
SPECIAL(sp)UUUUU(EOLF)
PREC(sp)R(EOLF)
ZID(sp)(TI of last transmitted message)(EOLF)
(SC ̲EOTF)
4.2.6.2 S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
The software structure of the Outgoing Transport is
based on a coroutine running under control of the CSF
Coroutine Monitor.
The principle placing of this coroutine in a transport
subprocess has been described in section 4.2.3.2.
The structure of the OTS software has been broken down
into a number of modules, which are closely related
to the functional break down described in section 4.2.6.l.
The modules supporting each type of outgoing Transport
is shown on figure 4.2.6.2-l.
Each module contains a number of procedures related
to a specific function within the Outgoing Transport.
figure 4.2.6.2-l
Figure 4.2.6.2-2
4.2.6.2.l O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲
This module contains the coroutine which implements
the basic control logic of the Outgoing Transport software.
The coroutine includes the main waiting-point (ref.
4.3.3.3.2.2.) through which the Outgoing Transport
communicates with IOC, Transport Control and the Curcuit
Queue.
The coroutine activates all procedures which are related
to the functions of the Outgoing Traffic Control as
described in section 4.2.6.l.l.
Each type of Outgoing Transport has its own Outgoing
Traffic Control Module.
4.2.6.2.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲t̲a̲r̲t̲/̲S̲t̲o̲p̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲o̲d̲u̲l̲e̲
This module is common to all types of transport and
includes procedures, which are related to:
- START ̲UP
- STOP ̲TRANSPORT
- CLOSE ̲DOWN
4.2.6.2.3 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
This module supplies all procedures necessary for handling
the flow of message lines through the Outgoing Transport
as described in section 4.2.6.1.2.
Each type of transport has its own Outgoing Message
Handling Module.
4.2.6.2.4 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
This module takes care of transmission of messages
lines in the sequence precribed by the ACP-Parameters
following the message from the Circuit Queue.
4.2.6.2.5 M̲e̲s̲s̲a̲g̲e̲ ̲L̲i̲n̲e̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
This module includes the procedures which generate
the message lines inserted by the Outgoing Transport.
The functions inplemented in this module is described
in section 4.2.6.l.3.
The module supports all types of transport.
4.2.6.2.6 A̲S̲M̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
This module supplies procedures for generation of Abbreviated
Service Messages which are automatically transmitted
by CAMPS.
The module supports all types of transport.
4.2.6.2.7 O̲T̲S̲ ̲C̲o̲m̲m̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲
This module contains a number of procedures common
to all types of transport.
4.2.6.2.8 T̲R̲S̲ ̲-̲ ̲A̲u̲x̲i̲l̲a̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The OTS also make use of the TRS Auxilary Functions
defined in section 4.2.3.6.
4.2.6.3 D̲A̲T̲A̲ ̲F̲L̲O̲W̲ ̲A̲N̲D̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲L̲O̲G̲I̲C̲
4.2.6.3.l I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
This section describes the main data structure and
control logic within the OTS.
Four buffers have been introduced to implement the
flow of messages through the OTS (see figure 4.2.6.3.l-l):
OUT ̲EMF ̲BUF
OUT ̲ACP ̲PARAM ̲BUF
OUTG ̲MSG ̲FRAMING ̲BUF
OUT ̲IOC ̲BUFFER
Messages are received through the circuit Queue (CIQ).
A queue element received from CIQ will reference a
CIF, which makes it possible for OTS to read the content
of the CIF.
First the OTS will transfer the ACP127 Parameter Field
of the EMF from CIF to the OUT ̲ACP ̲PARAM ̲BUF. The parameter
field contains the number of message lines within each
of the EMF fields: Header Field, Text Preamble Field
and Text Field.
In the next step the OTS transferes the message lines
to be transmitted from these fields to OUT ̲EMF ̲BUF.
The message lines are transmitted on the outgoing channel
by packing them into a buffer (OUT ̲IOC ̲BUF) which are
made available to the IOC through a call to the IOS
Procedure "APPEND BYTES".
Two buffers are used for this purpose in order to make
it possible for the OTS to store message lines into
one buffer while the content of the other is transmitted
by IOC.
When the OTS packs the message lines into OUT ̲IOC ̲BUF,
it will insert a number of new lines which serves the
purpose of framing the message (see functions described
in 4.2.6.l.3). The lines are constructed in OUTG ̲MSG
̲FRAMING ̲BUF on the basis of information stored in OUT
̲ACP ̲PARAM ̲BUF and the queue element.
When all lines from the OUT ̲EMF ̲BUF have been transmitted
a new transfer is made from the CIF. This goes on until
all message lines contained in the CIF have been transmitted.
Messages generated inside the OTS, i.e. Abbreviated
Service Messages ASM, are constructed directly into
the "OUT ̲EMF ̲BUF".
Parameters describing the ASM are stored into OUT ̲ACP
̲PARAM ̲BUF.
From the OUT ̲EMF ̲BUF the ASM is transmitted in the
same way as messages received through the CIQ.
Figure 4.2.6.3.l-l
4.2.6.3.2 R̲e̲c̲e̲i̲v̲e̲ ̲B̲u̲f̲f̲e̲r̲ ̲f̲o̲r̲ ̲E̲x̲t̲e̲r̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲F̲o̲r̲m̲a̲t̲
The OTS will receive the message lines of the External
Message Format stored in a CIF by means of the following
data structure (see figure 4.2.6.3.2-l).
a) O̲U̲T̲ ̲E̲M̲F̲ ̲B̲U̲F̲
Array of characters for reception of message lines
from the External Message Format contained in a
CIF.
b) O̲U̲T̲ ̲A̲C̲P̲ ̲P̲A̲R̲A̲M̲ ̲B̲U̲F̲
Record with a structure equel to the ACP-PARAMETER
̲FIELD within the EMF. This field is the first one
which are read when a message is transmitted.
c) O̲U̲T̲ ̲F̲I̲E̲L̲D̲ ̲L̲I̲S̲T̲
Data record with calling parameters for the system
call "READ ̲CIF", which transfer the message lines
from a CIF to OUT ̲EMF ̲BUF.
The FILED ̲LIST specifies for each field of the
External Message Format the first position to be
loaded and the number af characters to be transfered
to OUT ̲EMF ̲BUF. If the number is zero the transfer
will continue with the next field in the list.
The characters are stored consecutively in OUT
̲EMF ̲BUF
in the sequence specified by Field List.
Figure 4.2.6.3.2-l
4.2.6.3.3 O̲u̲t̲g̲o̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲a̲r̲k̲s̲
a) O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲t̲a̲t̲e̲ ̲M̲a̲s̲k̲ (ref. fig. 4.2.6.3.3-l)
Specifies the state of the Outgoing Message Handling.
b) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲a̲s̲k̲
(Ref. fig. 4.2.6.3.3-2 and 4.2.6.3.3-3).
Indicates the sequence of message lines for the
Outgoing Message Transmission. The mask is constructed
prior to the transmission of the first message
line.
c) O̲u̲t̲g̲o̲i̲n̲g̲ ̲D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲M̲a̲s̲k̲ (ref. fig. 4.2.6.3.3-4)
Indicates the type of data collections to be performed
at the end of a transmission.
The mask is constructed prior to the transmission
of the first message line.
d) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲i̲m̲e̲r̲ ̲M̲a̲s̲k̲ (Rel. figure 4.3.6.3.3-5)
Indicates the type of timer to be activated at
the end of transmission. The mask is constructed
prior to the transmission of the first message
line.
Figure 4.2.6.3.3-l
Figure 4.2.6.3.3-2
Figure 4.2.6.3.3-3
Figure 4.2.6.3.3-4
Figure 4.2.6.3.3-5
4.2.6.4 M̲O̲D̲U̲L̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
4.2.6.4.l T̲R̲C̲/̲P̲ ̲T̲O̲ ̲P̲ ̲O̲U̲T̲G̲O̲I̲N̲G̲ ̲T̲R̲A̲F̲F̲I̲C̲ ̲C̲O̲N̲T̲R̲O̲L̲
4.2.6.4.l.l F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This module supplies the basic control logic of the
Outgoing Transport for TRC/POINT TO POINT.
The module includes the TP ̲OT ̲COROUTINE, which contains
the main waiting point of the Outgoing Traffic.
The module activates the functions which are related
to the Outgoing Traffic Control (ref. sec. 4.2.6.l.l):
- Start Up
- Stop Transport
- Close Down
- Outgoing Message Handling
- Generation of ASM
- Log Acknowledge
4.2.6.4.1.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) TP ̲OT ̲COROUTINE
b) TP ̲OT ̲COROUTINE (R6):OK
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R6 LINK (destr)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
N.A There is no return from the
TP ̲OT ̲COROUTINE, which is implemented
with an endless loop.
4.2.6.4.l.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of this module are depicted on figure
4.2.6.4.1.3-1.
4.2.6.4.l.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲s̲
All data used are included in "Data Record for TRC/POINT
TO POINT TRANSPORT" defined in section 4.2.3.5.2
4.2.6.4.l.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲ ̲
All procedures within this module are reentrant.
M̲o̲d̲u̲l̲e̲ ̲E̲n̲t̲r̲y̲: (see flowgram 4.2.6.4.1.5-1)
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲P̲ ̲O̲T̲ ̲C̲O̲R̲O̲U̲T̲I̲N̲E̲
(R6) C D LINK
This procedure is implemented with an endless loop
in order to make it run as coroutine under control
of the CSF COROUTINE MONITOR.
The procedure the main waiting point OT ̲OPSEM through
which it receives:
- TRS ̲OPERATIONS from the TCS
- Buffers returned from IOC as a reply for the system
call APPEND ̲BYTES
- View received from the CIRCUIT QUEUE as a reply
for the system call RECEIVE ̲FIRST ̲QEL
M̲o̲d̲u̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲:
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲P̲ ̲N̲E̲W̲ ̲O̲U̲T̲G̲O̲I̲N̲G̲ ̲M̲S̲G̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure inputs a QEL from the circuit queue
an excamines if it contains a view and has a subtype
equal to FOR ̲TRANSMISSION ̲TO ̲TRS ̲PTOP.
The message is transmitted if:
- The outgoing channel status is open
- No close down or stop command has been received
from the TCS
- No device error has been detected
- The view has not been stoppped
- The transmission is not busy
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲A̲S̲M̲ ̲T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure takes care of ASM transmission requests
received from the TCS.
Exits: OKAY - ASM request accepted
ERROR - ASM request not accepted
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲A̲S̲M̲ ̲T̲P̲ ̲L̲O̲G̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure handles the functions related to the
log acknowledge receive from the TCS the last outgoing
message.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲R̲E̲E̲M̲P̲T̲I̲O̲N̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure handles preemption requests received
from the TCS.
FIGURE 4.2.6.4.1.3-1
PROCEDURE TP ̲OT ̲COROUTINE
EQUIVALENCE(PARAM ̲BASE,TRP: TRANSPORT ̲PARAMETERS)
START
LOOP "Forever"
READ ̲BASE () (PARAM ̲BASE)
WAIT ̲TRS ̲OPSEM (TRP.OT ̲OPSEM) "Main Waiting Point"
(TRP.OT ̲OPERATION)
CASE TRP.OT ̲OPERATION.OP ̲TYPE
OUTG ̲MSG ? TP ̲NEW ̲OUTG ̲MSG
TR ̲ASM ? ASM ̲TRANSMISSION ̲REQUEST
TRS ̲LOG ̲ACK ? TP ̲LOG ̲ACKNOWLEDGE
TRS ̲PREEMPT ? PREEMPTION ̲REQUEST
TRS ̲START ? OUTG ̲START ̲STOP(TRC ̲STOP,TRS
̲START)
TRS ̲STOP ? OUTG ̲START ̲STOP(TRC ̲PTOP,TRS
̲STOP)
TRS ̲CLOSE ? OUTG ̲START ̲STOP(TRC ̲PTOP,TRS
̲CLOSE)
IOC ̲REPLY ? TP ̲OUTG ̲MSG ̲HANDLING(IOC ̲BUF)
OTHERWISE ? TRS ̲INTERNAL ̲ERROR(TP ̲OT ̲COROUTINE,
TRS ̲OP ̲ERROR,OP
̲TYPE)
END CASE
END LOOP
RETURN
Flowgram 4.2.6.4.l.5-l
4.2.6.4.2 N̲I̲C̲S̲ ̲T̲A̲R̲E̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲
4.2.6.4.2.l F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This module supplies the NT ̲OT ̲COROUTINE, which contains
the basic control logic of the Outgoing Transport for
NICS TARE.
All functions related to the Outgoing Traffic Control
for NICS ̲TARE are activated from this module (ref.4.2.6.l.l).
4.2.6.4.2.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) NT ̲OT ̲COROUTINE
b) NT ̲OT ̲COROUTINE (R6): OK
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R6 LINK (destr)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
N.A. There is no return from the NT ̲OT ̲COROUTINE,
which is implemented with an endless loop.
4.2.6.4.2.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of this module are depicted on figure
4.2.6.4.2.3-1.
4.2.6.4.2.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲s̲
All data used are included in "Data Record for NICS
TARE Transport" as defined in section 4.2.3.5.3.
4.2.6.4.2.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
All procedures within this, modules are reentrant:
M̲o̲d̲u̲l̲e̲ ̲E̲n̲t̲r̲y̲: (see flowgram 4.2.6.4.2.5-1)
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲N̲T̲ ̲O̲T̲ ̲C̲O̲R̲O̲U̲T̲I̲N̲E̲
(R6) C D LINK
This procedure is implemented with an endless loop
in order to make it run as coroutine under control
of the CSF COROUTINE MONITOR.
The procedure the main waiting point OT ̲OPSEM through
which it receives:
- TRS ̲OPERATIONS from the TCS
- Buffers returned from IOC as a reply for the system
call APPEND ̲BYTES
- View received from the CIRCUIT QUEUE as a reply
for the system call RECEIVE ̲FIRST ̲QEL
FIGURE 4.2.6.4.2.3-1
PROCEDURE NT ̲OT ̲COROUTINE
EQUIVALENCE(PARAM ̲BASE,TRP: TRANSPORT ̲PARAMETERS)
START
LOOP Forever
READ ̲BASE()(PARAM ̲BASE)
WAIT ̲TRS ̲OPSEM(TRP.OT ̲OPSEM EQ) Main Waiting
Point
(TRP.OT ̲OPERATION)
CASE TRP.OT ̲OPERATION.OP ̲TYPE
OUTG ̲MSG ? NT ̲NEW ̲OUTG ̲MSG
TR ̲ASM ? ASM ̲TRANSMISSION ̲REQUEST
TRS ̲LOG ̲ACK ? NT ̲LOG ̲ACKNOWLEDGE
TRS ̲START ? OUTG ̲START ̲STOP(NICS ̲TARE,
TRS ̲START)
TRS ̲STOP ? OUTG ̲START ̲STOP(NICS ̲TARE,
TRS ̲STOP)
TRS ̲CLOSE ? OUTG ̲START ̲STOP(NICS ̲TARE,
TRS ̲CLOSE)
IOC ̲REPLY ? TP ̲OUTG ̲MSG ̲HANDLING (IOC ̲BUF)
OTHERWISE ? TRS ̲INTERNAL ̲ERROR (TRS ̲OP
̲ERROR,NT ̲OTCOROUTINE,OP ̲TYPE))
END CASE
END LOOP
RETURN
Flowgram 4.2.6.4.2.5-1
M̲o̲d̲u̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲:
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲N̲T̲ ̲N̲E̲W̲ ̲O̲U̲T̲G̲ ̲M̲S̲G̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure inputs a QEL from the circuit queue
an examines if it contains a view and has a subtype
equal to FOR ̲TRANSMISSION ̲TO ̲NICS ̲TARE.
The message is transmitted if:
- The outg. channel status is open
- No close down or stop command has been received
from the TCS.
- No device error has been detected
- The view has not been stopped
- The transmission is not busy
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲N̲T̲ ̲L̲O̲G̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure handles the functions relaed to the
log acknowledge receive from the TCS for the last outgoing
message.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲A̲S̲M̲ ̲T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
ERROR ̲OK
This procedure takes care of ASM transmission requests
received from the TCS.
EXITS: OKAY - ASM request accepted
ERROR - ASM request not accepted
4.2.6.4.3 S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲
4.2.6.4.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̲
This module supplies the basic control logic of the
Outgoing Transport for SCARS/CCIS.
The module includes the SC ̲OT ̲COROUTINE, which contains
the main waiting point.
The module activates the procedures, which are related
to the Outgoing Traffic Control (ref.sec.4.2.6.l.l):
Start Up
Stop Transport
Close Down
Outgoing Message Handling
Generation of ASM
Log Acknowledge
Transaction Acknowledge
4.2.6.4.3.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) SC ̲OT ̲COROUTINE
b) SC ̲OT ̲COROUTINE (R6):OK
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R6 LINK (destr)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
N.A. No return. The SC ̲OT ̲COROUTINE is implemented
with an endless loop.
4.2.6.4.3.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of thes module are depicted on figure
4.2.6.4.3.3-1.
4.2.6.4.3.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
All data used by SC ̲OT ̲COROUTINE are included in "Data
Record for SCARS/CCIS Transport as defined in section
4.2.3.5.4.
4.2.6.4.3.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲ ̲
The SC ̲OT ̲COROUTINE is implemented as a reentrant procedure
with a flow as depicted on flowgram 4.2.6.4.3.5-l.
M̲o̲d̲u̲l̲e̲ ̲E̲n̲t̲r̲y̲:
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲C̲ ̲O̲T̲ ̲C̲O̲R̲O̲U̲T̲I̲N̲E̲
(R6) C D LINK
Outgoing coroutine for SCARS/CCIS transport subprocess.
This procedure is implemented with an endless loop
in order to make it run as coroutine under control
of the CSF COROUTINE MONITOR.
The procedure the main waiting point OT ̲OPSEM through
which it receives:
- TRS ̲OPERATIONS from the TCS
- Buffers returned from IOC as a reply for the system
call APPEND ̲BYTES
- View received from the CIRCUIT QUEUE as a reply
for the system call RECEIVE ̲FIRST ̲QEL
FIGURE 4.2.6.4.3.3-1
M̲o̲d̲u̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲:
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲C̲ ̲N̲E̲W̲ ̲O̲U̲T̲G̲ ̲M̲S̲G̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure inputs a QEL from the circuit queue
an examines if it contains a view and has a subtype
equal to FOR ̲TRANSMISSION ̲TO ̲SCARS or FOR ̲TRANSMISSION
̲TO ̲
CCIS.
The message is transmitted if:
- No close down or stop command has been received
from the TCS.
- No device error has been detected
- The view has not been stopped
- The transmission is not busy
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲A̲S̲M̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure takes care of ASM TRANSMISSION REQUESTS
received from the transport control.
The following ASM types are accepted:
ACP ̲FINAL ̲MSG, ACP ̲CHN ̲CHK ̲MSG, E1 ̲FINAL ̲MSG,
E1 ̲CHN ̲CHK ̲MSG
FATAL ERROR: ASM request already active.
Illegal ASM type.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲C̲ ̲A̲C̲K̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲
(R0 C D BOOLEAN (TYPE OF ACKNOWLEDGE HANDLING)
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure takes care of actions related to log
acknowledge and transaction acknowledge.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲R̲A̲N̲S̲M̲I̲T̲ ̲A̲C̲K̲N̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure initiates transmission of an transaction
acknowledge ASM.
EXIT: TRUE - Transmission Initiated
FALSE - Transmission not allowed
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲R̲A̲N̲S̲M̲I̲T̲ ̲A̲S̲M̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
BOOLEAN
This procedure initiates transmission of an ASM if
the OUTG ̲ASM ̲REQUEST indicaes so.
In case that the ASM to be transmitted is equal to
FINAL ̲MESSAGE the procedure will reset the GSN related
to the outgoing channel (if specified by supervisor).
EXITS: TRUE - ASM transmission initiated
FALSE - ASM transmission not allowed
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲R̲E̲T̲R̲A̲N̲S̲M̲I̲T̲ ̲M̲S̲G̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure retransmits a message. If the message
has been retransmitted more than MAX ̲RETRANSMISSION
a report is generated for the supervisor.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲R̲E̲E̲M̲T̲I̲O̲N̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 C D TRS ̲PREEMPTION TYPE
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
BOOLEAN
This procedure handles preemption requests received
from the TCS.
EXITS: TRUE - Preemption request accepted
FALSE - Preemption request not accepted
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲C̲ ̲S̲T̲A̲R̲T̲ ̲S̲T̲O̲P̲
(R0 D
R1 C D FUNCTION ID
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure takes care of the actions related to:
START ̲UP, CLOSE ̲DOWN and STOP ̲COMMANDS.
PROCEDURE SC ̲OT ̲COROUTINE
EQUIVALENCE(PARAM ̲BASE,TRP:TRANSPORT ̲PARAMETERS)
START
LOOP "Forever"
READ ̲PARAM ̲BASE ()(PARAM ̲BASE)
WAIT ̲TRS ̲OPSEM(TRP.OT ̲OPSEM)
TRP.OT ̲OPERATION)
CASE TRP.OT ̲OPERATION.OP ̲TYPE
OUTG ̲MSG ? SC ̲NEW ̲OUTG ̲MSG
TR ̲ASM ? ASM ̲REQUEST
TRS ̲LOG ̲ACK ? SC ̲LOG ̲ACKNOWLEDGE(TRUE)
TRS PREEMPT ? PREEMPTION ̲REQUEST(FLASH ̲PREEMPT)
TRS ̲START ? SC ̲START ̲STOP(TRS ̲START)
TRS ̲STOP ? SC ̲START ̲STOP(TRS ̲STOP)
TRS ̲CLOSE ? SC ̲START ̲STOP(TRS ̲CLOSE)
IOC ̲REPLY ?
SC ̲OUTG ̲MSG ̲HANDLING(IOC ̲BUF)
OUTG ̲TRANSMISSION ̲BUSY ?
SC ̲ACK ̲HANDLING(FALSE)
ACK ̲REC ?
TRP.OT ̲OPERATION.INFO1 EQ OK ?
TRP.RETRANS ̲NO + 1
SC ̲ACK ̲HANDLING (TRUE)
SEND ̲ACK ? TRS ̲INTERNAL ̲ERROR(SC ̲OT ̲COROUTINE,
TRS ̲OP ̲ERROR, OP ̲TYPE)
OTHERWISE ? TRS ̲INTERNAL ̲ERROR (SC ̲OT ̲COROUTINE,
TRS ̲OP ̲ERROR,
OP ̲TYPE)
END CASE
RETURN
Flowgram 4.2.6.4.3.5-l
4.2.6.4.4 P̲T̲P̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲
4.2.6.4.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̲
This module supplies the basic control logic of the
Outgoing Transport for PTP.
The module activates the procedure related to the Outgoing
Traffic Control (ref. 4.2.6.l.l):
- Start Up
- Stop Transport
- Close Down
- Outgoing Message Handling
- Log Acknowledge
4.2.6.4.4.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) PTP-OT ̲COROUTINE
b) PTP ̲OT ̲COROUTINE(R6):OK
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R6 LINK (Destr)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
N.A. No return. The PTP ̲OT ̲COROUTINE is
implemented with an endless loop.
4.2.6.4.4.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of this module are depicted on figure
4.2.6.4.4.3-1.
4.2.6.4.4.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲s̲
All data used by PTP ̲OT ̲COROUTINE are included in "Data
Record for PTP ̲TRANSPORT" as defined in section 4.2.3.5.5.
4.2.6.4.4.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
All procedures within this module are reentrant.
M̲o̲d̲u̲l̲e̲ ̲E̲n̲t̲r̲y̲: (Flowgram 4.2.6.4.4.5-1)
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲T̲P̲ ̲O̲T̲ ̲C̲O̲R̲O̲U̲T̲I̲N̲E̲
(R6) C D LINK
This procedure is implemented with an endless loop
in order to make it run as coroutine under control
of the CSF COROUTINE MONITOR.
The procedure the main waiting point OT ̲OPSEM through
which it receives:
- TRS ̲OPERATIONS from the TCS
- Buffers returned from IOC as a reply for the system
call APPEND ̲BYTES
- View received from the CIRCUIT QUEUE as a reply
for the system call RECEIVE ̲FIRST ̲QEL
FIGURE 4.2.6.4.4.3-1
M̲o̲d̲u̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲:
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲T̲P̲ ̲N̲E̲W̲ ̲O̲U̲T̲G̲ ̲M̲S̲G̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure inputs a QEL from the circuit queue
an examines if it contains a view and has a subtype
equal to FOR ̲PUNCH.
The message is transmitted if:
- The outg. channel status is open
- No close down or stop command has been received
from the TCS.
- No device error has been detected
- The view has not been stopped
- The transmission is not busy
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲T̲P̲ ̲S̲T̲A̲R̲T̲ ̲S̲T̲O̲P̲
(R0 C D COMMAND: TRS ̲START, TRS ̲CLOSE, TRS ̲STOP
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure takes care of the actions related to
START ̲UP, CLOSE ̲DOWN and stop of the outgoing transport.
Commands: TRS ̲START - Transfer of message from the
circuit is initiated.
TRS ̲CLOSE - Close down indication is set
to prevent new transferes from
the circuit queue.
TRS ̲STOP - If the transmission is busy
all APPEND ̲BYTE syscalls are
cancelled. Otherwise CLOSE
̲ACK is returned to TCS, an
initiated RECEIVE ̲FIRST ̲QEL
from the circuit queue is cancelled.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲T̲P̲ ̲L̲O̲G̲ ̲A̲C̲K̲N̲O̲W̲L̲E̲D̲G̲E̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure handles the functions related to the
log acknowledge received from the TCS for the last
outgoing message.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲P̲R̲E̲E̲M̲T̲I̲O̲N̲ ̲R̲E̲Q̲U̲E̲S̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure handles preemption requests received
from the TCS.
PROCEDURE PTP ̲OT ̲COROUTINE
EQUIVALENCE(PARAM ̲BASE,TRP:TRANSPORT ̲PARAMETERS)
START
LOOP "Forever"
WAIT ̲TRS ̲OPSEM(TRP.OT ̲OPSEM)
TRP.OT ̲OPERATION)
CASE TRP.OT ̲OPERATION.OP ̲TYPE
OUTG ̲MSG ? PTP ̲NEW ̲OUTG ̲MSG
TRS ̲LOG ̲ACK ? PTP ̲LOG ̲ACKNOWLEDGE
TRS PREEMPT ? PREEMPTION ̲REQUEST
TRS ̲START ? PTP ̲START ̲STOP(TRS ̲START)
TRS ̲STOP ? PTP ̲START ̲STOP(TRS ̲STOP)
TRS ̲CLOSE ? PTP ̲START ̲STOP(TRS ̲CLOSE)
IOC ̲REPLY ? PTP ̲OUTG ̲MSG ̲HANDLING (IOC
̲BUF)
OTHERWISE TRS ̲INTERNAL ̲ERR(TRS ̲OP ̲ERROR, PTP
̲OT ̲COROUTINE,
OP ̲TYPE)
END CASE
END LOOP
END
Flowgram 4.2.6.4.4.5-l
4.2.6.4.5 O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲t̲a̲r̲t̲ ̲S̲t̲o̲p̲ ̲C̲o̲n̲t̲r̲o̲l̲
4.2.6.4.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̲
This module supplies the procedures, which are related
to:
- start up
- stop transport
- close down
for NICS TARE and SCARS/CCIS.
All functions above are activated from the OT ̲COROUTINE
as a result of an operation received from Transport
Control (i.e. TC ̲COROUTINE).
Each of the functions above are described in section
4.2.6.1.1.
4.2.6.4.5.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) OUTG ̲START ̲STOP (FUNCTION ̲ID, CIRCUIT)
b) OUTG ̲START ̲STOP (R0, R1, R6)
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R0 Circuit (destr.)
R1 Function Id. (destr.)
R6 LINK (kept)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
None (All registers destroyed)
Function Id: TRS ̲STRAT, TRS ̲STOP, TRS CLOSE
4.2.6.4.5.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of this module are depicted on figure
4.2.6.4.5.3-1.
4.2.6.4.5.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲s̲
Ref. 4.2.3.5
4.2.6.4.5.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
All procedures within this module are reentrant:
OUTG ̲START ̲STOP: Flowgram 4.2.6.4.5.5-1
M̲o̲d̲u̲l̲e̲ ̲E̲N̲T̲R̲Y̲:
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲O̲U̲T̲G̲ ̲S̲T̲A̲R̲T̲ ̲S̲T̲O̲P̲
(R0 C D CIRCUIT (TRC ̲PTOP OR NICS ̲TARE)
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure is entry point for the OT ̲START module.
A branch is made to one of the following functions:
START ̲UP
STOP ̲TRANSPORT
CLOSE ̲DOWN
Fig. 4.2.6.4.5.3-1
PROCEDURE OUTG ̲START ̲STOP (FUNCTION ̲ID)
START
SAVE ̲LINK (LINK)(PARAM ̲BASE)
CASE FUNCTION ̲ID
TRS ̲START
TRS ̲START ? START ̲UP
TRS ̲STOP ? STOP ̲EXC ̲TRANSPORT
TRS ̲CLOSE ? CLOSE ̲TRANSPORT
END CASE
RESTORE ̲LINK
RETURN
Flowgram 4.2.6.4.5.5-1
4.2.6.4.6 T̲R̲C̲/̲P̲T̲O̲P̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
4.2.6.4.6.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 TP ̲Outgoing Message Handling supplies the procedures
which take care of the basic flow of message lines
through the Outgoing Transport for TRC/POINT TO POINT.
The following functions are included:
a) T̲P̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲S̲t̲a̲r̲t̲
- Receives queue element from Circuit Queue.
- Reads ACP ̲PARAMETERS of the External message
Format specified by queue element.
- Updates Outgoing State Mask, Outgoing Message
Control Mask, Outgoing Data Collection Mask,
and Outgoing Timer Mask on the basis of information
stored in ACP ̲PARAMETERS and queue element.
- Prepares a field list for sequential reading
from CIF containing the message.
b) I̲O̲C̲ ̲B̲u̲f̲f̲e̲r̲ ̲R̲e̲c̲e̲i̲v̲e̲d̲
Receives the empty buffer from IOC and returns
it to IOC ̲OUT ̲POOL.
c) A̲S̲M̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲R̲e̲q̲u̲e̲s̲t̲
If no transmission is going on, construction and
transmission of the requested ASM is initiated.
d) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
Ref. section 4.2.6.4.10.
e) O̲u̲t̲g̲o̲i̲n̲g̲ ̲L̲o̲g̲
Constructs outgoing log if specified.
f) O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲t̲o̲r̲a̲g̲e̲
Constructs outgoing storage if specified.
g) O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Constructs statistics for outgoing message if specified.
h) T̲P̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲i̲m̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
Activates timers indicated by OUTG ̲TIMER ̲MASK
4.2.6.4.6.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) TP ̲OUTG ̲MSG ̲HANDLING (FUNCTION ̲ID)
(CC): Ok
b) TP ̲OUTG ̲MSG ̲HANDLING (R0,R1,R2,R3,R4,R5,R7,R6)
R̲e̲g̲i̲s̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
C̲a̲l̲l̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
R0 Function Id (destr)
R6 LINK (kept)
R̲e̲t̲u̲r̲n̲ ̲R̲e̲g̲i̲s̲t̲e̲r̲s̲
None (All registers destroyed)
Function Id: (NEW ̲MSG, IOC ̲BUF, ASM ̲REQ, NEW ̲ASM)
4.2.6.4.6.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The components of this module are depicted on figure
4.2.6.4.6.3-1.
4.2.6.4.6.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
All data structures for TP ̲OUTG ̲MSG ̲HANDLING Module
are defined in section 4.2.3.5.
4.2.6.4.6.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
All procedures included in this module are reentrant.
M̲o̲d̲u̲l̲e̲ ̲E̲N̲T̲R̲Y̲: (Flowgram 4.2.6.4.6.5-1)
E̲x̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲P̲ ̲O̲U̲T̲G̲ ̲M̲S̲G̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲
(R0 C D TRS ̲MSG ̲HND ̲TYPE
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure makes the entry point for the TP ̲OUT
̲HND module and contains the main logic of this module.
M̲o̲d̲u̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲:
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲I̲N̲P̲U̲T̲ ̲I̲O̲C̲ ̲R̲E̲P̲L̲Y̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure inputs the IOC ̲REPLY initiated by the
systemcall APPEND ̲BYTES.
The following functions are included:
- Input of IOC ̲BUFFER returned from the systemcall
APPEND ̲BYTES
- Check IOC completion codes
- Return TRS ̲IOC ̲OPERATION to OUT ̲IOC ̲POOL
- Activation of timers if the IOC ̲BUFFER returned
has contained the last line of a message.
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲P̲ ̲T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲ ̲S̲T̲A̲R̲T̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R POINTER TO TRANSPORT PARAMETERS
R6) C D LINK
This procedure initiates transmission of a message
for TRC/POINT to point. This includes the following
main tasks:
- Reading of ACP ̲PARAMETERS
- Init of OUTG ̲MSG ̲CHARACTERS
- Init of OUTG ̲MSG ̲CTR ̲MASK
- Init of paging parameters if paging is required
- Init of data collection mask
P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲P̲ ̲O̲U̲T̲G̲ ̲T̲I̲M̲E̲R̲
(R0 D
R1 D
R2 D
R3 D
R4 D
R5 D
R7 R
R6) C D LINK
This procedure will activate timers related to the
outgoing transport for TRC/POINT TO POINT. The following
timer functions are included:
- Flash timer is activated if a flash message requires
acknowledge.
- ZID timer is activated if the TSN transmitted
is equal to one and the supervisor has specified
that the TSN shall be set to one at midnight.
NOTE: This procedure contains a waiting point.
Fig. 4.2.6.4.6.3-1
PROCEDURE TP ̲OUTG ̲MSG ̲HANDLING (TRS ̲MSG ̲HND ̲TYPE)
EQUIVALENCE (PARAM ̲BASE, TRP: TRANSPORT ̲PARAMETERS)
START
SAVE ̲LINK (LINK)(PARAM ̲BASE)
CASE TRS ̲MSG ̲HND ̲TYPE
NEW ̲MSG ? TP ̲TRANSMISSION ̲START
IOC ̲BUF ? INPUT ̲IOC ̲REPLY
NEW ̲ASM ? GENERATE ̲ASM
END CASE
Outgoing Transmission Busy ?
Outgoing Transmission End ?
OUTG ̲MSG ̲TRANSMISSION
Outgoing Data Collect EQ FALSE ?
Outgoing Log EQ FALSE ?
TRS ̲OUTG ̲LOG
Outgoing Storage EQ FALSE ?
TRS ̲OUTG ̲STORAGE
Outgoing Statistics EQ FALSE ?
TRS ̲OUTG ̲STATISTICS
RETORE ̲LINK()(PARAM ̲BASE)
RETURN
Flowgram 4.2.6.4.6.5-1
