top - download
⟦1e9d7bf2a⟧ Wang Wps File
Length: 25052 (0x61dc)
Types: Wang Wps File
Notes: CPS/SDS/001
Names: »1378A «
Derivation
└─⟦2c95d9416⟧ Bits:30006059 8" Wang WCS floppy, CR 0091A
└─ ⟦this⟧ »1378A «
WangText
…19……0a……19……0c……19……0f……19……86…1
…02…
…02…
…02…
…02…CPS/SDS/001
…02…KNB/811020…02……02…
CAMPS
SYSTEM
DESIGN
SPECIFICATION
…02…ISSUE
1.1…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.13 TRAFFIC HANDLING PACKAGE ................ 568
5.13.1 General ............................. 568
5.13.1.1 Purpose and Scope ............... 568
5.13.1.2 Applicable Documents and Project
References Special for Section
5.13 ............................
568
5.13.1.2.1 Applicable Documents......... 568
5.13.1.2.2 Project References........... 568
5.13.1.3 Terms and Abbreviations Special
For Section 5.13 ................ 568
5.13.1.3.1 Terms........................ 568
5.13.1.3.2 Abbreviations................ 569
5.13.2 Summary of Requirements.............. 570
5.13.2.1 Package Description.............. 570
5.13.2.2 Package Functions................ 572
5.13.2.2.1 Main Functions............... 572
5.13.2.2.1.1 Reception Procedures..... 573
5.13.2.2.1.2 ACP 127 Analysis......... 573
5.13.2.2.1.3 Routing.................. 574
5.13.2.2.1.4 ACP 127 Conversion....... 575
5.13.2.2.1.5 Transmission Procedures.. 575
5.13.2.2.1.6 Transmission Control
Procedures ..............
576
5.13.2.2.2 Functional Responsibilities.. 576
5.13.2.2.2.1 Initialization, Close
Down and Restart ........
576
5.13.2.2.2.1.1 Initialization ...... 577
5.13.2.2.2.1.2 Close Down .......... 577
5.13.2.2.2.1.3 Restart.............. 577
5.13.2.2.2.2 Check Pointing and
Recovery.................
578
5.13.2.2.2.2.1 Checkpointing ....... 578
5.13.2.2.2.2.2 Recovery ............ 578
5.13.2.2.2.3 Error Detection and Error
Handling................. 579
5.13.2.2.2.4 Integrity of Operation... 580
5.13.2.2.2.5 Data Collection.......... 580
5.13.2.2.2.6 Security................. 581
5.13.2.3 Characteristics.................. 582
5.13.2.3.1 Timing....................... 582
5.13.2.3.1.1 Throughput Time ......... 582
5.13.2.3.1.2 Response Time ........... 584
5.13.2.3.1.3 Priorities Imposed by
Input ...................
584
5.13.2.3.2 Throughput................... 585
5.13.2.3.3 Flexibility.................. 585
5.13.2.3.4 Accuracy and Validity........ 586
5.13.3 Environment.......................... 587
5.13.3.1 Equipment........................ 587
5.13.3.2 Software......................... 587
5.13.3.2.1 System Software.............. 587
5.13.3.2.2 Development Support Software. 587
5.13.3.3 Interfaces....................... 587
5.13.3.3.1 External Interfaces.......... 587
5.13.3.3.2 Package Interfaces........... 588
5.13.3.3.2.1 Interface MDP ........... 588
5.13.3.3.2.2 Interface TEP ........... 588
5.13.3.3.2.3 Interface SAR ........... 589
5.13.3.3.2.4 Interface LOG ........... 589
5.13.3.3.2.5 Interface STP ........... 589
5.13.3.3.2.6 Interface TMP ........... 589
5.13.3.3.2.7 Interface SSC ........... 590
5.13.3.4 Functions Maintained by Other
packages ........................
590
5.13 T̲R̲A̲F̲F̲I̲C̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.13.1 G̲e̲n̲e̲r̲a̲l̲
5.13.1.1 P̲u̲r̲p̲o̲s̲e̲ ̲a̲n̲d̲ ̲S̲c̲o̲p̲e̲
N/A.
5.13.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̲.̲ ̲S̲p̲e̲c̲i̲a̲l̲
̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲3̲
N/A.
5.13.1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲d̲o̲c̲u̲m̲e̲n̲t̲s̲
N/A.
5.13.1.2.2 P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
N/A.
5.13.1.3 T̲e̲r̲m̲s̲ ̲a̲n̲d̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲3̲
1.3.1 T̲e̲r̲m̲s̲
N/A.
5.13.1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
AAS ACP127 Analysis Subpackage
ACS ACP127 Conversion Subpackage
ANQ Analysis Queue
ASM Abbreviated Service Message
CCQ Channel Command Queue
CIQ Circuit Queue
COQ Conversion Queue
EOPF End of Page Function
EOTF End of Transmission Function
MCQ MDCO Queue
MSQ Message Service Queue
OTS Outgoing Transport Subpackage
SVC Service Message
TCS Transport Control Subpackage
TRS Transport Subpackage
5.13.2 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
5.13.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 to 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 5.13.2.1-1. The chart illustrates
the environment of this package and inter-relationships
between external/internal interfaces.
FIGURE 5.13.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)
Storage and File Management (SFM)
Input/Output Control (IOC)
System Status and Control (SSC)
5.13.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 (5.13.2.2.1 and 5.13.2.2.2)
be described in the main functions under normal operation
and the more special functions performed under more
specific circumstances.
5.13.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)
5.13.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.
5.13.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
- Pilot Detect
- Relay Assistance
Otherwise the message will be directed to its proper
destinations into CAMPS according to the message type.
5.13.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.
5.13.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
5.13.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.
5.13.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.
5.13.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.
5.13.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̲
5.13.2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
During initialization of THP the following functions
will be performed:
- Initialize THP memory
- Reset Timer Table
If SSC in the initialization parameters for the channel
has specified, that the channel shall be opened the
following functions will be performed
- Set incoming Channel open
- Send Incoming Channel opening ASM
5.13.2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
A Close down and an ordered switchover will be equally
handled by THP. The following functions will be performed
for each channel:
- If a message is being transmitted, it will be preempted
- Set incoming and outgoing channel closed
- Send incoming channel close ASM
- Report to SSC that the channel is closed.
5.13.2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
During a Restart THP will perform the initialization
described in section 5.13.2.2.2.1.1 and the Recovery
procedure in section 5.13.2.2.2.2 if applicable.
5.13.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̲
5.13.2.2.2.2.1 C̲h̲e̲c̲k̲-̲P̲o̲i̲n̲t̲i̲n̲g̲
THP will perform the following check-pointing:
a) Incoming Message
After reception of a message it will be disk check-pointed.
When the message has passed the ACP127-analysis,
it will be standby check-pointed.
b) Outgoing Message
After ACP127 conversion, the message will be standby
check-pointed. When the message has been transmitted
and acknowledge received (if required) the message
will be disk check-pointed.
5.13.2.2.2.2.2 R̲e̲c̲o̲v̲e̲r̲y̲
Two types of Recovery exists for THP. One Recovery
function after start-up based upon stand-by checkpoints,
and one Recovery function after start-up based upon
disk checkpoints.
a) Standby Checkpoints.
The first message retransmitted on each external
channel will be preceded by a suspected duplicate
Pilot.
b) Disk Checkpoints.
All messages marked for recovery, will be assigned
a suspected duplicate Pilot before transmission.
5.13.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 provide the following error handling:
a) Program errors.
The error will be reported to SSC and the processing
stopped.
b) Data error.
The error will be analyzed; depending upon the
result, the processing will either be stopped or
continued. If the processing continues, the error
will be forwarded to a special Data Error Queue
served by SSC; by "continue" is meant continue
with the next message.
SSC will forward the error report to printout at
the operator position. This report might result
in a reprogramming of the invalid module that caused
the error. The message itself had been dismantled
and thus no more available in the erroneous version;
if a previous error-free version of the message
is available, this can be re-entered.
The Data errors associated to garble detect during
reception procedures and ACP127-analysis is not
included in the description above, because that
type of error handling is considered part of the
normal flow.
5.13.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)
5.13.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 message in ACP127 format
Incoming Message in E1 format
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
5.13.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 different).
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 either be automatically punched or
sent to an MSO position for re-assignment with a notification.
Messages having been "cleared" will as outgoing be
considered unclassified, and as incoming 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.
5.13.2.3 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
5.13.2.3.1 T̲i̲m̲i̲n̲g̲
5.13.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.
Through-put time for an incoming plaindress message
in average figures:
CPU access time 40 ms
Number of Monitor calls to CSF: 2 read access
5 write access
Number of Monitor call to TMP: 3
(Where the information is stored
on disk.)
Throughput time for an outgoing
Plaindress message
CPU access time: 40 ms
Number of Monitor calls to CSF: 3 read access
6 write access
Number of Monitor calls to TMP: 14
Where the information is stored
on disk
5.13.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.
5.13.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.
5.13.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
5.13.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.
5.13.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)
5.13.3 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲
5.13.3.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲
5.13.3.2 S̲o̲f̲t̲w̲a̲r̲e̲
5.13.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
5.13.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.
5.13.3.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
5.13.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̲
5.13.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 5.13.2.1-1 for overview.
5.13.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.
5.13.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.
5.13.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.
5.13.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
5.13.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
5.13.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
5.13.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.)
5.13.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
