top - download
⟦494d1980f⟧ Wang Wps File
Length: 31878 (0x7c86)
Types: Wang Wps File
Notes: CPS/SDS/033 , Missing sectors
Names: »1930A «
Derivation
└─⟦d6c5ca2c3⟧ Bits:30006095 8" Wang WCS floppy, CR 0149A
└─ ⟦this⟧ »1930A «
WangText
:…07…9…0a…9…0d…9…00…9…05…8…0a…8…0e…8 7…08…7…0c…7…86…1
…02…
…02…
…02…
…02…
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
The package specification for the Traffic Handling
Package (CPS/SDS/033) is written to fulfil the following
objectives:
a) To provide detailed definition of the package functions
and software architecture.
b) To provide user operational and development personnel
details of the ongoing analysis.
c) To define in detail the interfaces with other packages
and to describe their facilities.
The Traffic Handling Package provides functions for
message reception and transmission (level 4), ACP l27
analyzes of incoming messages, Routing and ACPl27-conversion
of outgoing messages.
This document contains the complete design of the Traffic
Handling Package to a level sufficient for a programmer
to start detailed design with a minimum of design effort
of the architecture.
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲d̲o̲c̲u̲m̲e̲n̲t̲s̲
The following documents are applicable to the Traffic
Handling Package Design Specification.
Contract Document
Contract No. CE 80-9009-INF
CAMPS System Requirements
CPS/210/SYS/0001
User Procedure,
doc. no. CPS/230/ICD/0001
Supervisor Commands and Procedures
CPS/230/ICD/0002
ACP127 NATO Supp. 3 Procedures
CPS/230/ICD/0003
NICS/TARE
CPS/ICD/004
SCARS II
CPS/ICD/005
ACE CCIS
CPS/ICD/006
TRC, Point-to-Point Connection
CPS/ICD/007
CAMPS System Design Specification,
doc. no. CPS/SDS/001.
CAMPS Data Base Design Document,
doc. no. CPS/DBD/001
CAMPS Software Interface Control Document,
doc. no. CPS/ICD/009
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
D̲O̲C̲U̲M̲E̲N̲T̲ ̲N̲A̲M̲E̲
CAMPS System Functions
CPD/SDS/024
Message Management
CPS/SDS/025
Table Management
CPD/SDS/026
Input/Output Control
CPS/SDS/028
System Status and Control
CPS/SDS/029
Storage and Retrieval
CPS/SDS/030
Statistics
CPS/SDS/03l
Logging
CPS/SDS/032
Message Distribution
CPS/SDS/034
Supervisor Distribution
CPS/SDS/035
Supervisor Printer
CPS/SDS/036
MDCO VDU
CPS/SDS/037
MSO VDU
CPS/SDS/038
USER VDU
CPS/SDS/039
OCR
CPS/SDS/040
Printer
CPS/SDS/04l
1.2.3 P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
The following documents are listed for reference purposes
only. The listing does not constitute the contents
of the documents as Systen Requirements but is intended
to serve the Contractor in providing supplementary
information in cases of interpretation of the requirements
specifically stated in System Requirements Specification:
ACP131, Jul. 74
ACP117, SEPT. 1977, ACP117 Supp. 16. Dec. 79
ACP121, Supp. 17. Jan. 1970, 121E Jul. 1970
ACP100, NATO SUPP, 1E May 1978
ACP127, NATO SUPP. 3 May 1973, 127 (E) OCT 74
NASIS-APP.3 JAN 1978
1.3 I̲T̲E̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 T̲e̲r̲m̲s̲
Channel designator Identification of an external
channel.
Checkpoint Point from which restart/recovery
can take place.
Circuit CAMPS to node connection
for the appropriate Network.
A circuit may consist of
one or more channels.
Close-down Action taken to bring processing
within the system or a part
thereof to a stop - can be
either an ordered sequence
of steps or an abrupt termination.
External Channel A channel in a telegraph
circuit or non telegraph
circuit.
Initialization The definition in the CPS/SDS/001
and subsequent documents
is described as follows:
Brings the system from cold
or dead start into operational
use. No recovery actions
are included.
Message Distribution Denotes the total group of
Control Function commands/procedures which
may be performed from a VDU
with Message Distribution
Control capability.
Message Service Denotes the total group of
Function commands/procedures which
may be performed from a VDU
with Message Service capability
Message View A subset of fields within
a message.
Non Telegraph CCIS and SCARS
Circuit
Plain Language The PLA representing a
Address Headquarter
Process Execution of a specific program
operating on a specific set
of data.The active components
of the system to which security
and process control as well
as resource management is
applied.
Queue Process communication tool
within CSF.
Queue Element The elements which can be
in a queue.
Queue Monitor The part of CSF supplying
Queue facilities.
Restart Reestablishes the dynamic
behaviour of the system based
upon recovered data.
Recovery Reestablishes continuity
in memory and file contents.
Sub queue Part of a Main Queue
Supervisor Person located at supervisor
terminals in CAMPS central
equipment room
Supervisor's Person with responsibility
for
Assistant special Message Service
Stand-alone device Medium speed teleprinter,
low speed teleprinter (PTP,PTR,
ROP) OCR, PTR, and PTP.
Start up Includes all aspects of initialization,
recovery and restart.
Switchover Relates to a dualized configuration
containing an active and
a stand-by device into active
state and the other active
device off-line.
System Parameter A simple variable, holding
part of the system state,
and controlled by TMP.
Telegraph circuit NICS TARE, Point-to-Point
and TRC.
Terminal VDU, Medium Speed Teleprinter,
Low Speed Teleprinter, Line
Printer, PTP/PTR and OCR.
Terminal Position VDU and associated (shared)
ROP.
User a) Person with responsibility
for input and output
of messages.
b) Person located at the
user terminals in the
staff cells.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
AAS ACP127 Analysis Subpackage
ACP127 ALLIED Communication Procedures No. 127
ACS ACP127 Conversion Subpackage
AIG Address Indicator Group
ANQ Analysis Queue
ASM Abbreviated Service Message
CAMPS Computer Aided Message Processing System
CCQ Channel Command Queue
CCIS Command & Control Information System
CIF CAMPS Information Field
CIQ Circuit Queue
COQ Conversion Queue
CPS CAMPS
CSF CAMPS System Functions
CTS Cosmic Top Secret
DTG Data Time Group
EOLF End of Line Feed
EOPF End of Page Function
EOTF End of Transmission Function
FIFO First In, First Out
FL Format Line
HQ Headquarters
ICD Interface Control Document
IOC Input/Output Control Package
ITS Incoming Transport Subpackage
LOG Log and Accountability Package
MCQ MDCO Queue
MDCO Message Distribution Control
MDP Message Distribution Package
MSO Message Service Operator
MSQ Message Service Queue
NA Not Applicable
NICS Nato Integrated Communication System
OTS Outgoing Transport Subpackage
PLA Plain Language Address
PLA# Plain Language Address Reference Number
PTP Paper Tape Puncher
PTR Paper Tape Reader
P-to-P Point-to-Point
QEL Queue Element
SAR Storage and Retrieval
SCARS Status Control and Reporting System
SCD Staff Cell Designator
SDS System Design Specification
SFM Storage and File Management Package
SIC Subject Indicator Code
SOTF Start of Transmission Function
SRS System Requirements Specification
SSC System Status and Control
SSN Station Serial Number
STP Statistic Package
SVC Service Message
TARE Telegraph Automatic Relay Equipment
TCS Transport Control Subpackage
TD Terminal Designator
TEP Terminal Package
THP Traffic Handling Package
TI Transmission Identification
TMP Table Management Package
TOC Time of Occurrence
TRS Transport Subpackage
TSN Transmission Serial Number
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The Traffic Handling Package provides the functions
for Transport, ACP127-analysis, Routing and ACP127
-conversion of messages.
Incoming messages are received via external channels
(NICS TARE, TRC/Point-to-Point, SCARS and CCIS) and
transported to analysis for subsequent internal distribution.
Outgoing messages are received from other Packages
for routing, conversion and transport for transmission
via above mentioned external channels.
The functions for handling of complete messages related
to PTR/PTP are also provided within this Package.
The Interfaces of the Traffic Handling Package are
as depicted in figure 2.1-1. The chart illustrates
the environment of this package and inter-relationships
between external/internal interfaces.
FIGURE 2.1-1…01…TRAFFIC HANDLING PACKAGE
a) E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
NICS TARE
TRC/Point-to-Point
SCARS
CCIS
PTR
PTP
Low speed Teleprinters operating as PTR or PTP.
b) I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Message Distribution Package (MDP)
Terminal Package (TEP)
Log Package (LOG)
Statistics Package (STP)
Storage and Retrieval (SAR)
Table Management (TMP)
CAMPS System Functions (CSF)
Message (MMS)
Input/Output Control (IOC)
System Status and Control (SSC)
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
The functions performed by this package will in the
following two sections (2.2.1 and 2.2.2) be described
in the main functions under normal operation and the
more special functions performed under more specific
circumstances.
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The main functions performed during normal operation
are:
a) Reception Procedures
b) ACP127-analysis
c) Routing
d) ACP127-conversion
e) Transmission Procedures
f) Transmission Control Procedures
The terms used under a, e and f are corresponding to
- Incoming Transport (a)
- Outgoing Transport (e)
- Transport Control (f)
2.2.1.1 R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions associated to Reception Procedures are:
- Assembling of format-lines into messages in ACP127-format
or SCARS/CCIS E1-format
- Channel Discontinuity Procedures
- Tolerance Control for detection of garble characteristics.
The received messages are considered as incoming from
the external networks NICS TARE, TRC, Point-to-points
and the external systems SCARS and CCIS.
Under reception procedures are also considered input
via the dedicated PTR or Low Speed Teleprinters operating
like PTR's. These messages are entered into complete
ACP127-format and mainly considered as outgoing messages.
The messages described are always directed for ACP127-analysis.
2.2.1.2 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
The functions of ACP127-analysis are:
- Handling of errors detected during Reception Procedures
involving a message.
- Format-Line detect and control
- Message Type Determination
- Relaying
- ASM-Handling
- Handling of messages received in SCARS/CCIS E1-format
- Flash acknowledge
- Consistency Control
- Internal Format Conversion
After ACP127-analysis a message might be directed to
a message service position for:
- Garble Correction
- Message Inspection
Otherwise the message will be directed to its proper
destinations into CAMPS according to the message type.
2.2.1.3 R̲o̲u̲t̲i̲n̲g̲
The functions of routing are:
- Select of Routing Indicators related to PLA's or
AIG's (entered during Message Prepare) in accordance
with message classification.
- Circuit allocation in accordance with channel availability
and classification on basis of related Routing
Indicator.
- Message Service Invocation for RI-assignment in
case above described functions fail.
- Automatic release of complete entered messages.
During Routing the PTP will be selected as "circuit"
for plaindress messages of type Crypto Security and
in accordance with MSO-decision where no RI with proper
classification can be found.
Local PLA's will also be detected.
2.2.1.4 A̲C̲P̲1̲2̲7̲-̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
The messages received for ACP127-conversion are messages
that have been routed.
The functions of ACP127-conversion are:
- Formattting of FL2 and FL3 of complete entered
messsages.
- Formatting of Supervisor prepared Service Messages
- Conversion and formatting of user prepared messages
into complete ACP127-format.
- Separation into sections if applicable for that
message
- Preparation of separate transmissions in case multiple
routes or limit exceeded on RI's.
- Insert of ZEN in front of PLA's where multiple
routes are applicable.
The messages are after conversion forwarded to transmission
upon a channel indicated via the circuit selected under
Routing. A message containing Local PLA's will, however,
be directed for local distribution
2.2.1.5 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of Transmission Procedures are:
- Formatting of FL1
- Formatting of Pilots upon automatic or Supervisor
intiated retransmissions (reruns)
- Preemption for transmission of flash message where
applicable.
- Delivery of format-lines for transmission including
insert of formal parameters.
To the Transmission Procedures are also considered
the functions for punch on a PTP; the first two functions
described are then a bit different, but still relevant.
A transmitted message will after successful transmission
be taken care of by the Transmission Control Procedures,
if the message shall be acknowledged.
2.2.1.6 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of the Transmission Control are:
- Automatically Generation of ASMs of the type channel
continuity, channel number reset etc. upon timer-event.
- Time-out control and initialization of retransmissions
or supervisor reports upon that event.
- Generation of flash acknowledge ASM, Identical
Character ASM etc. upon request via a command.
- Initiate channel open and close (via command) by
generation of an ASM or at receipt of such ASM.
2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
The more special functional responsibilities provided
by the THP, will in the following sections be specified.
2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
2.2.2.1.1 The Analysis and Conversion Processes will during
initialization perform the following functions:
- accept configuration parameters from SSC
- initialize data areas
- report subprocess identification to CSF.
The transport processes will perform the same functions
described above, but he initialization of data-areas
is transport-type depending and may include more subprocesses
with individual initialization of coroutinesand semaphores.
After initialization the Analysis and Conversion Processes
will be running immediately, while the transport subprocesses
will wait for an individual start-command from SSC;
(see principle section 2.2.2.l.3 as for Restart) this
command will follow an initialization always; the individual
transport subprocesses will then wait for reception
of an incoming channel open ASM before transmission
of messages begins (open of outgoing channel), and
upon a supervisor command for open of the incoming
channel before reception of incoming messages can be
expected - the last described procedures do not include
SCARS, CCIS, PTR and PTP, who will be immediately running
after initialization.
2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
Close Down of the Analysis and the Conversion Processes
will be done immediately after reception of the SSC-command;
this command is detected when the message during analyses
or conversion is finished (if any).
To the Transport Processes are associated two SSC-commands
for Close Down and an individual stop-command:
- Init Close Down
- Final Close Down
- Stop
These commands are detected immediately and may result
in termination of the message during transmission or
reception.
a) I̲n̲i̲t̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
No more messages will be transmitted after the
message present under transmission; no influence
on reception of messages.
b) F̲i̲n̲a̲l̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲ ̲o̲r̲ ̲S̲t̲o̲p̲
If necessry the messages under transmission and
reception will be terminated (preemptied/halted)
and the following functions executed:
- transmission of incoming channel Close ASM
(no change of own incoming status).
- close of outgoing channel
- checkpointing of channel status
- empty circuit-queue
- disconnect from logical channel
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
Restart of the analyses and conversion processes is
the same as initialization. A transport sunprocess
is restarted via a START-command from SSC; the following
is the executed:
- connect to logical channel
- read of channel profile associated to that
logical channel.
- read of associated channel status parameters.
- transmission of either a channel OPEN ASM or
channel CLOSE ASM depending on the incoming
channel status.
2.2.2.2 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
2.2.2.2.1 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
After reception of the EOTF an incoming message
will be checkpointed.
When the message has been succesfully analyzed
it will be checkpointed again.
b) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
After conversion from the IMF to EMF (ACPl27-format
mostly), the outgoing message is checkpointed.
When the message has been transmitted it will be
checkpointed again.
2.2.2.2.2 R̲e̲c̲o̲v̲e̲r̲y̲
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
An incoming message which has not been complete
analyzed or not been delivered to all internal
destinations after analyzes, will be analyzed again.
b) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
As for incoming messages, outgoing messages not
complete routed and concverted will be converted
again. Messages for transmission will be transmitted
duplicate pilot, if marked with a recovery flag.
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
THP will perform two types of error handling:
- data error handling
- processing error handling
a) D̲a̲t̲a̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
If a QEL fetched via a THP-queue is not in accordance
with the QEL/View-type specified for THP-interfaces
(ref.CPS/SDS/009), the QEL (maybe
referencing a message-view) will be sent to the
GAQ-queue served by SSC; there the contants of
the QEL will be dumped at the operator position.
The THP-process will then continue its processing
with the next QEL (message).
b) P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
This type of Error Handling is associated to system-calls.
If an unexpected completion-code is returned from
a system call, SSC will be notified with resulting
retirement of the process.
The unexpected completion-code, the call-type and
the register-contents will be dumped at the operator
position.
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
For an incoming Message, THP will validate all Format
lines and adjust acceptable deviations of an ACP127
- or SCARS/CCIS E1 - formatted message in order to
ensure the integrity of future operations.
For user prepared outgoing messages all data are assumed
having been validated during preparation.
For complete messages entered from a PTR, and service
messages entered by the Supervisor certain transactions
will be validated. (e.g. routing indicators)
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
The following Data Collection will be provided by THP
- Collection of Statistics
- Collection of Retrieval keys
- Collection of Log information
- Reports to Supervisor
THP will collect statistics on the following objects:
- Incoming message
- Invalid incoming message
- Outgoing message
- Channel open/close
THP will collect Retrieval keys on the following objects:
Incoming valid message after analysis
Outcoming message after transmission
Automatically released outgoing message
THP will collect log information on the following objects
Incoming message
Invalid incoming message
Outgoing message
Channel discontinuity
PTP
THP will generate the following Supervisor Reports:
a) Security Reports:
- Circuit classification too low upon circuit
XX
b) Warning Reports:
- No available channels upon circuit XX
c) Channel Reports:
- Discontinuity in TSN of incoming message
- Missing TSN of incoming message
- Halted message condition
- A message has been prematurely terminated
- 100 characters have been received on a channel
after EOTF but without detection of VZXZC
- Oversized incoming message
- More than 140 identical consecutive characters
except for text part in data message.
- Time out on flash receipt
- Outgoing channel opening/closing
- Incoming test message garbled
- Selfaddressed channel check time out
- Outgoing channel test not successful
- No channel number reset ASM received
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
When an incoming message is received on a circuit it
will automatically be assigned an access classification
(Queue Profile) equal to the circuit classification.
THP will during the analysis of the message identify
the message classification, and change the access attributes
in accordance with the classification of the message
(if lower); if higher the message is rejected to MSO.
For an outgoing message the RIs are selected in accordance
with the message classifications; before forwarding
the message to transmission, the classification of
the circuit will be compared with the messsage classification.
If no RI and circuit with proper classification exists,
the message will be sent to an MSO position for re-assignment
with a notification.
Messages having been "cleared" will as outgoing be
considered unclassified, and as incoming minimum confidential.
The considered classifications will be the ones used
during the processing of the message in accordance
with access control through CAMPS; the originally assigned
classification will remain unchanged. THP will in accordance
with this procedure change the classification attributes,
enabling the message to be transmitted.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
2.3.1.1 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲ ̲T̲i̲m̲e̲
The throughput time is for an incoming message from
the time where EOTF is detected until the time where
the message is delivered to either MDP, TEP or punched
at a PTP. The throughput time is for an outgoing message
from the time where the message is queued to ACP127-conversion
until the time for start of transmission.
The troughout time for a message of average length
(= 1500 characters) with 7 PLA's and 5 RT'S will in
the following be specified.
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Direct CPU = 30 ms
20 IOC calls * 20 ms = 400 ms
(using a 80 bytes buffer)
l2 CFS calls * 20 ms = 2̲4̲0̲ ̲m̲s̲
Total CPU: = 670 ms
======
Write message = 3 access
Read field(sector boundary) = l -
Checkpointing = ̲ ̲l̲ ̲ ̲ ̲-̲ ̲
̲ ̲ ̲ ̲
Total Disk-access: = 5 accesses
= ============
b) A̲n̲a̲l̲y̲s̲i̲s̲
Direct CPU = 60 ms
l8 CFS calls * 20 ms = 360 ms
l5 TMP calls * 20 ms = 3̲0̲0̲ ̲m̲s̲
Total CPU: = 720 ms
= ======
Read message = l access
Write message = l -
Table-search (lAIG+lPLA) = 2 -
Checkpointing = ̲ ̲l̲ ̲ ̲ ̲-̲ ̲
̲ ̲ ̲ ̲
Total Disk-access: = 5 accesses
============
2.3.1.2 R̲e̲s̲p̲o̲n̲s̲e̲ ̲T̲i̲m̲e̲
Response time for THP is only applicable for messages
returned after MSO assistance. The MSO will after finished
analysis or conversion receive a response from THP.
Response time for the incoming MSO
CPU access time: 20 ms
Number of monitor calls to CSF: 1 read access
1 write access
Number of monitor calls to TMP: 3
(Where the information is
stored on disk
Response time for the outgoing MSO
CPU access time: 20 ms
Number of monitor calls to CSF: 2 read access
3 write access
Number of monitor calls to TMP: 14
Where the information is stored
on disk.
2.3.1.3 P̲r̲i̲o̲r̲i̲t̲i̲e̲s̲ ̲i̲m̲p̲o̲s̲e̲d̲ ̲b̲y̲ ̲I̲n̲p̲u̲t̲
The THP will process incoming messages in the sequence
of arrival independent of the message precedence, except
for precedence flash.
Outgoing messages will be processed after the same
principles during conversion, but be transmitted by
precedence.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The THP shall support the following throughput (in
busy minute, busy hour, 24 hour period)
30,530…0e…x)…0f…,3000 Incoming messages for analysis
6,250…0e…xx)…0f…,900 Outgoing messages for conversion
x) incl. 15 comments but not 150 VDU-pages
xx) incl. VDU-pages and 15 comments
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
In general the software structure of THP has been built
up after structured methods, which in itself makes
the package flexible to maintain and makes it easy
to incorporate new software.
However, the structure of the ACP127-analysis shall
be emphazised. The logic related to that processing
is of very complex nature, where future changes to
requirements have been foreseen by developing an analysis
guide table; this table can be maintained off-line.
The ACP127-conversion software can be expanded to convert
any message format.
The transport software has been structured in a manner
where only the top level software shall be changed
in order to create a new transport process type.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲ ̲a̲n̲d̲ ̲V̲a̲l̲i̲d̲i̲t̲y̲
THP has no requirements to accuracy for incoming messages.
Any piece of data will be accepted; should a piece
of data, however, turn out not to be one of the acceptable
formatted message types, it is the responsibility of
THP to reject such data (e.g. garble correction).
Messages sent to ACP127-conversion as outgoing from
a release position has to be accurate; no check for
validity will be performed for such messages because
they are expected to be proper validated by TEP before
the release. Abbreviated and normal service messages
entered from a supervisor position will be accepted
with certain erroneous data-elements for ACP127-conversion
(e.g. routing indicators)
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The system software used by this package is the software
included in the following packages:
- SFM
- CSF
- IOC
- SSC
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The software used for development of this package is
the software supported by the Support Software Package.
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Traffic Handling package interfaces via IOC the
following externals:
a) N̲I̲C̲S̲ ̲T̲A̲R̲E̲
Ref. CPS/230/ICD/0004
b) S̲C̲A̲R̲S̲
Ref. CPS/230/ICD/0005
c) C̲C̲I̲S̲
Ref. CPS/230/ICD/0006
d) T̲R̲C̲/̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
Ref. CPS/230/ICD/0007
e) P̲T̲R̲
f) P̲T̲P̲
g) L̲o̲w̲ ̲S̲p̲e̲e̲d̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
In the following the package interfaces with other
application packages and SSC will be identified (except
system-interfaces to SFM, CSF and IOC)
Ref. figure 2.1.1 for overview.
3.3.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲
- Incoming messages for local distribution
- Outgoing messages for local distribution.
3.3.2.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
a) T̲E̲P̲ ̲t̲o̲ ̲T̲H̲P̲
- Outgoing released messages for routing and
conversion
- Supervisor prepared service messages for conversion.
- Supervisor initiated rerun.
- Supervisor initiated channel control
- Comments and VDU-pages for distribution to
SCARS/CCIS
- Reenterings from message service
- Supervisor initiated readdressal
b) T̲H̲P̲ ̲t̲o̲ ̲T̲E̲P̲
- Incoming service messages to be printed at
a supervisor position.
- Incoming messages from SCARS/CCIS to be presented
at a terminal position
- Reports to be printed at a Supervisor position
- Message service invocation for:
Garble Correction
Pilot Detect
Relay Assistance
RI-assignment
Too low TSN.
3.3.2.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲A̲R̲
Delivery of retrieval-keys associated to incoming and
outgoing messages before conversion to internal format
respectively after conversion to external format.
3.3.2.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲O̲G̲
- Incoming message logs
- Outgoing message logs
- Channel Discontinuity log
3.3.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲T̲P̲
- Statistics incoming message
- Statistics outgoing message
- Statistics channel availability
3.3.2.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲M̲P̲
The following parameters and tables controlled by TMP
are used by this package:
- AIG-table
- PLA-tables
- RI-tables
- Circuit table
- Channel Profiles
- ACP127 parameters
- Channel Sequence Numbers
3.3.2.7 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲S̲C̲
SSC interfaces THP for close-down and start-up of each
channel. The modes of start-up or close-down can differ
upon the situation (switch-over, partly close-down,
total close-down etc.)
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
The functions maintained by other packages are the
functions related to the operating system.
a) C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲S̲C̲F̲)̲
- Checkpointing
- Control of access rights related to queues
- Timer functions
b) S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲F̲i̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲(̲S̲F̲M̲)̲
- Access and access control to files (messages)
Automatic delete of CTS and atomal messages.
c) I̲n̲p̲u̲t̲/̲O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲I̲O̲C̲)̲
- Access to external channels and devices
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
In overview the Traffic Handling Package consists of
3 main areas with completely different functional capabilities:
- ACP127 analysis
- ACP127 conversion
- Transport
The transport functions consist of 3 subjunctions:
- Outgoing Transport
- Transport Control
- Incoming Transport
As shown in figure 4.1-1 the Traffic Handling Package
has been separated into the following subpackages:
1) ACP127 Analysis Subpackage
2) ACP127 Conversion Subpackage
3) Incoming Transport Subpackage
4) Transport Control Subpackage
5) Outgoing Transport Subpackage
Figure 4.1-1 also illustrates how these subpackages
relate to processes and coroutines.
FIGURE 4.1-1…01…PACKAGE OVERVIEW
4.1.1 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
In the following the functions associated to the groups
specified in package overview, will be identified.
- ACP127 Analysis Functions
- ACP127 Conversion Functions
- Transport Functions
The Transport Functions will be described separately
for:
- NICS TARE Transports
- TRC/Point-to-point Transports
- SCARS/CCIS Transports
- PTR Transport
- PTP Transport
At last the common function
