top - download
⟦5d4f9e9c9⟧ Wang Wps File
Length: 27424 (0x6b20)
Types: Wang Wps File
Notes: CPS/SDS/001 ISSUE 1
Names: »0686A «
Derivation
└─⟦6472223e8⟧ Bits:30006010 8" Wang WCS floppy, CR 0045A
└─ ⟦this⟧ »0686A «
WangText
6…09…6…0d…6…0f…6…00…6…05…5…86…1
…02…
…02…
…02…
…02…CPS/SDS/001
…02…KNB/810227…02……02…
CAMPS
SYSTEM
DESIGN
SPECIFICATION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.11 TRAFFIC HANDLING PACKAGE .................
513
5.11.1 Summary of Requirements ..............
513
5.11.1.1 Package Description ..............
513
5.11.1.1.1 General Description ..........
513
5.11.1.1.2 Internal Interfaces ..........
513
5.11.1.1.3 External Interfaces ..........
514
5.11.1.1.4 Chart over Interfaces ........
514
5.11.1.2 Package Functions ................
516
5.11.1.2.1 Functional Groups ............
516
5.11.1.2.1.1 Traffic Out Group ........
516
5.11.1.2.1.2 Traffic In Group .........
517
5.11.1.2.2 Functional Flow ..............
532
5.11.1.2.2.1 Incoming Traffic .........
532
5.11.1.2.2.2 Outgoing Traffic .........
533
5.11.1.2.3 Functional Requirements ......
534
5.11.1.2.3.1 Released Message .........
535
5.11.1.2.3.2 Service Message ..........
535
5.11.1.2.3.3 Channel Check ............
535
5.11.1.2.3.4 Routing ..................
536
5.11.1.2.3.5 ACP127-Formatting ........
537
5.11.1.2.3.6 Clean-Up .................
537
5.11.1.2.3.7 Incoming Messages ........
538
5.11.1.2.3.8 ACP127-Analysis ..........
538
5.11.1.2.3.9 Special Messages .........
539
5.11.1.2.3.10 Relaying .................
541
5.11.1.2.3.11 Special Formats CCIS/SCARS
541
5.11.1.2.4 Recovery Functions ...........
542
5.11.1.3 Package Control ..................
544
5.11.1.3.1 Control Parameters ...........
544
5.11.1.3.1.1 Message Processing .......
544
5.11.1.3.1.2 External Connection ......
545
5.11.1.3.2 Hardware Control .............
545
5.11.1.3.3 Error Reporting Mechanisms ...
545
5.11.1.4 Characteristics ..................
545
5.11.1.4.1 Performance ..................
545
5.11.1.4.1.1 Throughput ...............
545
5.11.1.4.1.2 Storage ..................
546
5.11.1.4.1.3 Connectivity .............
546
5.11.1.4.1.4 Timing ...................
546
5.11.1.4.2 Availability and
Maintainability ..............
546
5.11.1.4.3 Security .....................
546
5.11.1.5 Design and Construction ..........
547
5.11.1.6 Documentation ....................
547
5.11.2 Environment ..........................
547
5.11.2.1 External Interfaces ..............
547
5.11.2.2 Internal Interfaces ..............
547
5.11.2.2.1 MDP ..........................
547
5.11.2.2.2 TEP ..........................
548
5.11.2.2.3 SAR ..........................
548
5.11.2.2.4 SFM ..........................
548
5.11.2.2.5 LOG ..........................
549
5.11.2.2.6 STP ..........................
549
5.11.2.2.7 IOC ..........................
549
5.11.2.2.8 CSF ..........................
550
5.11.2.2.9 TMP ..........................
550
5.11.2.2.10 SSC ..........................
551
5.11 T̲R̲A̲F̲F̲I̲C̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.11.1 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
5.11.1.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
5.11.1.1.1 G̲e̲n̲e̲r̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The Traffic Handling Package performs routing and analysis
of messages.
Incoming messages are received via external channels
(NICS TARE, TRC, SCARS, CCIS) and after ACP127-analysis
queued for local distribution in CAMPS.
Outgoing messages are fetched from various queues,
converted into ACP127-format (special format SCARS
and CCIS) and queued for transmission in accordance
with Routing Indicators related to the messages.
5.11.1.1.2 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Traffic Handling Package interfaces with following
other packages.
Message Distribution (MDP)
Terminal (TEP)
Storage and Retrieval (SAR)
Storage and File Management (SFM)
Log and Accountability (LOG)
Statistics (STP)
I/O Control (IOC)
CAMPS System Functions (CSF)
Table management (TMP)
SS&C.
5.11.1.1.3 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The following externals are interfaced via I/O Control
from this package:
NICS TARE
TRC/Point to Point
CCIS
SCARS
5.11.1.1.4 C̲h̲a̲r̲t̲ ̲o̲v̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The chart shows the basic functional components and
where the interfaces to other packages and externals
are.
FIGURE 5.11.1.1-4
5.11.1.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The functions of this package will be described under
the following subdivision:
a) Functional Groups
b) Functional Flow
c) Functional Requirements
d) Recovery Functions
5.11.1.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲G̲r̲o̲u̲p̲s̲
The functions of this package can be grouped into
- Traffic Out Group
- Traffic In Group
The main functional components associated to these
groups are shown in figures 5.11.1.2.1-1 and 5.11.1.2.1-2.
Decision-tables explaining the logic performed by some
of these functional components are shown in figures
5.11.1.2.1-1a to 5.11.1.2.1-1e (Outgoing traffic) and
figures 5.11.1.2.1-2a to 5.11.1.2.1-2f (Incoming traffic).
The upper part of the decision-tables express the condition
(rule) under which the actions in the lower part is
to be executed ( Y = yes, N = no).
5.11.1.2.1.1 T̲r̲a̲f̲f̲i̲c̲ ̲O̲u̲t̲ ̲G̲r̲o̲u̲p̲
The activities of the Traffic Out Group are:
Conversion and routing of released messages
Routing of complete entered messages (e.g. via PTR/TP)
Routing of service messages entered by supervisor
Conversion of messages for distribution to SCARS and
CCIS
Generation of automatic channel check messages and
other special messages (ASM)
Formatting of messages for transmission and final procedures
related to completion of transmission
Message Service invocation for RI assignment, Operating
Signals assignment and Group Count verification
5.11.1.2.1.2 T̲r̲a̲f̲f̲i̲c̲ ̲I̲n̲ ̲G̲r̲o̲u̲p̲
The activities of the Traffic In Group are as described
below:
Incoming messages are received via external channels
(NICS TARE, TRC, SCARS, and CCIS)
ACP127-analysis of all incoming messages with resulting
message type determination and conversion of message
into CAMPS Internal Message Format
Messages are received from SCARS/CCIS for local distribution
at CAMPS or to be rerouted as an outgoing message
From CCIS is also received VDU pages which are also
updated in a special database
Service Messages which are not of any special type
are queued for Supervisor. The special types are, requests
for acknowledge and acknowledge messages. (channel
check and flash messages)
All other message types are queued for distribution
Message Service invocation for correction of garbled
messages and by detect of messages containing a pilot.
her inds`ttes 13 sider figurer
FIGURE 5.11.1.2.2-1
FIGURE 5.11.1.2.2-2
5.11.1.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲F̲l̲o̲w̲
5.11.1.2.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲
The following points are references to figure 5.11.1.2.2-1:
1) Incoming message or error report received from
NICS TARE, TRC, SCARS or CCIS
2) If error message, report to Supervisor
3) If message, queue incoming message for
ACP127-analysis
4) A VDU-page is received (from CCIS)
5) The special database of VDU-pages is updated by
TMP
6) ACP127-analysis of incoming message
7) If invalid format report to supervisor
8) If garble characteristics queue message for correction
by Message Service
9) Message returned from Message Service
10) Log incoming message
11) Store incoming message with channel key
12) Update MCB with analysis results
13) If outgoing released message from CCIS or SCARS,
queue message for automatic release
14) If message type is not equal to Service Messsage,
queue message for Distribution
15) If message type is equal to Service Message or
precedence equal to flash, then queue message as
a special message.
16) Special message actions are:
a) handling of acknowledge messages
b) handling of request messages
(channel check and flash messages)
c) handling of service messages
17) If acknowledge message (time-out List) then stop
time-out
18) If Request message, then create Acknowledge message
and queue message for routing
19) Else queue Service Message to be printed at Supervisor
Position
5.11.1.2.2.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲
The following points are references to figure 5.11.1.2.2-2:
1) Released message from Release Officer
2) Complete entered message from supervisor or special
device
3) Station Serial Number and DTG assignment
4) Update of MCB with next SSN + time
5) Store outgoing message with release-key
6) Queue message for Local distribution
7) Message queued for routing
8) Service and special messages for routing
a) Service Message from Supervisor
b) Request Message (channel check, etc.) created
by this package
c) Acknowledge Message created by this package
as response to a received Request Message.
9) Routing of outgoing message
10) If unrecognized or missing RIs queue message for
RI-assignment by Message service
11) Return from RI-assignment
12) If channel security/availability do no match with
classification/RIs report to Supervisor
13) Queue message for final formatting
14) ACP127-formatting by separating the message into
segments/creating a contiguous file for transmission
and conversion into full ACP127-format.
15) Messages to be locally distributed at SCARS/CCIS
are received from MDP
16) Buffer a message as required of specific protocols
in short time storage
17) If specified by supervisor parameters, output message
on PTP
18) Else activate a protocol for transmission via a
channel queue
19) Response from protocol
20) If channel error, report to supervisor
21) Log outgoing message with time for start of transmission
22) If message was a Request Message start time-out
5.11.1.2.3 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Refer to figure 5.11.1.1-4 for details.
5.11.1.2.3.1 R̲e̲l̲e̲a̲s̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
The activities related to release of a message are:
Next Station Serial Number (SSN) and DTG is selected
MCB is updated with SSN + time
Message is queued for local distribution
Conversion to ACP127-format is performed on messages
which are not entered as complete messages
Store message with release-key
Queue outgoing released message for Routing
5.11.1.2.3.2 S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲
Service messages are prepared by Supervisor
Illegal RIs will be corrected by supervisor himself
Service Messages will be prepared validated and converted
into ACP127-format before they are queued to THP for
routing
5.11.1.2.3.3 C̲h̲a̲n̲n̲e̲l̲ ̲C̲h̲e̲c̲k̲
Automatic Channel Check messages are generated by this
package if so indicated by Supervisor Control parameters.
5.11.1.2.3.4 R̲o̲u̲t̲i̲n̲g̲
All outgoing messages are passed through Routing.
Message Type has been determined, and MCB is updated
with all possible information about the message i.e.
- message type
- classification
- precedence
- number of lines, etc.
The activities related to Routing are:
Get RIs related to PLAs
Check RIs and AIGs
Queue message to RI-assignment by Message Service Operator
in case of:
- Missing or illegal RI
- "x" for PLA
- T-instruction
- Missing operating Signals
Also queue encrypted message to Message Service for
Group Count Verification.
Create a Routing List
- Convert AIGs to RIs
- Exempt RIs from List
- Remove duplicate RIs from List
Select external channel according to RIs on Routing
List
- Check for channel security
- Check for channel availability
- Correct RIs if possible
If channel allocating failed then:
- RI-assignment by Message Service
- Warning Report
- Security Report
5.11.1.2.3.5 A̲C̲P̲1̲2̲7̲-̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
The activities related to ACP127-formatting are:
Separate message into segments of 20 lines, and sections
of 5 segments (long message)
Select RIs from Routing List and build up RI-line
Insert ZEN if multiple routes
Insert formal parameters like "NNNN"
Store formatted message temporarily and put pointer
to message into an Outgoing Message Queue for transmission
Prepare Routing List for multiple transmission in case
of:
- Long message
- Limit on RIs
If multiple routes, create separate transmission copies
from Routing List.
5.11.1.2.3.6 C̲l̲e̲a̲n̲ ̲U̲p̲
Receives information from applications related to specific
protocols about the transmission.
The information can be an acknowledge indicating that
a message has been sent (time for transmission) or
an error.
The activities performed are:
Log outgoing message with ack-time
Deliver information for statistics
Start time-out process in case of flash or channel
check ack-request
5.11.1.2.3.7 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲s̲
From external channels (NICS TARE, TRC, SCARS and CCIS)
are received complete messages and error reports created
by applications related to specific protocols.
Received messages are passed on to ACP127-analysis
Two types of errors shall be recognized
- Errors related to channels
- Errors related to messages
Errors on channels are:
- Improper channel serial number
- Missing channel serial number
- more than 100 char. after EOM
- Halted message
Errors of messages are:
- Terminated message
- Too long message
- more than 140 identical characters
The errors are mapped into channel and warning reports.
The logic of separation of errors do not reflect these
reports, but the requirements of the following ACP127-analysis,
i.e. whether the error type is an element of a possible
"garble" characteristic or not.
5.11.1.2.3.8 A̲C̲P̲1̲2̲7̲-̲A̲n̲a̲l̲y̲s̲i̲s̲
Incoming messages for ACP127-analysis are received
in full ACP127-format from NICS TARE, TRC and in an
ACP127-envelope from CCIS/SCARS.
Messages received from CCIS/SCARS are selected for
detection of local format types. (Ref. Special Formats
CCIS/SCARS 5.11.1.2.3.12).
Message is validated and sent for correction by Message
Service if Garble characteristics.
The message is analyzed line by line and the MCB is
updated with analysis-results such as:
- Incoming channel number
- Message type
- Classification
- Number of bytes
- Number of lines
During the ACP127-analysis fields of CAMPS Internal
Message Format are added to the message.
Incoming message is stored with channel-key
Information for Log and Statistics is delivered
Destination is selected as follows:
Distribution = Incoming message
Release = Outgoing message
Routing = Relay (T-instruction)
Special Message = Service + Flash messages
5.11.1.2.3.9 S̲p̲e̲c̲i̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Special messages are messages for which special treatment
is performed within this package. I.e. all service
messages and messages for which automatic acknowledgement
are required (flash).
The activities related to special messages are:
If Acknowledge message on previous transmitted message
with acknowledge-request, then stop time-out process.
If Request message, then create acknowledge message.
Request messages are incoming channel checks and flash
messages without a ZGC-notification.
Else queue Service Message to be printed at Supervisor
Position
Also create automatic Service Message in case of receipt
of 140 identical consecutive characters if so identicated
by supervisor control parameters.
AUTOMATIC RELAYING OR DISTRIBUTION
5.11.1.2.3.10 R̲e̲l̲a̲y̲i̲n̲g̲/̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The rules under which relaying is performed are as
stated shown in the table of automatic Relaying or
Distribution. (Fig. 5.11.1.2.3-1).
5.11.1.2.3.12 S̲p̲e̲c̲i̲a̲l̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲C̲C̲I̲S̲/̲S̲C̲A̲R̲S̲
Messages between CAMPS and CCIS or SCARS are exchanged
in a special message format.
Messages received from CCIS/SCARS are marked with a
type
a) Released message
b) Message for Release
c) Message for Coordination
d) Comment
e) VDU-page
The messages are analysed as normal messages and converted
into the internal message format, finally the routes
in CAMPS are as follow:
ad a) Routing for outgoing
MDP for local distribution
ad b) Release and routing for outgoing
MDP for local distribution
ad c) MDP for local distribution for coordination
ad d) MDP for distribution of comment
ad e) Special data base is updated with VDU-page
(max. 300), and else the same treatment as
a comment.
Requests for VDU-pages are exchanged between CAMPS
and CCIS/SCARS in form of comments (to supervisor).
Exchange of Service Messages is also in form of comments.
- The outgoing message types for CCIS and SCARS are:
a) Incoming message for relaying
b) Message for Local distribution
c) Message for coordination
d) Comment
e) VDU-page
The messages are converted into a special format (ACP127
envelope) before transmission. The routes for the messages
were:
ad a) An incoming message was bound for CCIS/SCARS
(RIs). After analysis queued for routing and
now a normal outgoing message.
ad b-e) All other message types were sent to MDP to
be distributed. SCDs for CCIS/SCARS were on
the distribution list, and MDP had sent a copy
for local distribution, coordination, a comment
or a VDU-page.
CCIS and SCARS are like "external terminals" in relation
to MDP.
5.11.1.2.4 R̲e̲c̲o̲v̲e̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The recovery functions for this Package is based on
checkpointing performed by CSF at predefined stages
of the message. These are:
A fully received message
A message that has passed analysis
A message that has been released
A message that has passed routing
A message that has been transmitted and an acknowledge
is received
The automatic check point mechanism is triggered when
placing a reference to the message in a queue after
above mentioned stages. If a system break-down occurs
during one of the processes, the effect will be that
the queues before the event are reestablished and the
process will be repeated. Other cases where this package
has to perform some recovery activities are:
a) Failure on an external channel
b) Failure on a group of external channels
c) Flash messages and generation of automatic acknowledge
messages
ad a) Failures on an external channel will be
handled in the same manner as a controlled
closedown of a channel.
The remaining messages queued for transmisson
will be queued back for a new RI-assingment.
(If no alternatives can be found then the
Message Service procedure).
ad b) The same as under point a). Some logic
has to be included in the applications
in order to spread the traffic on the available
channels.
In case a group of channels gets available
after a failure, the routing process will
direct the passing messages towards these
"empty" channel-queues.
ad c) No action is performed for incoming messages.
The incoming message will be transmitted
to CAMPS again and treated in the normal
way. (Including generating of an acknowledge
message).
The messages queued for transmission after
a break-down, are the messages that were
awaiting acknowledgement for successful
transmission. These messages are stamped
as possible duplicates (ZFH in FL5) before
a ready signal is given to the SSC. (If
applicable).
An acknowledge for a flash-message could
by this procedure therefore be received
twice. The first acknowledge will stop
the time-out, the second will then be directed
to supervisor, who will recognize the type.
5.11.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
5.11.1.3.1 C̲o̲n̲t̲r̲o̲l̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
The following supervisor control parameters are used
by this package.
a) Message Processing
b) External Connection
5.11.1.3.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
PLA Table
AIG Table
Table of RIs recognized by CAMPS
Table of RIs for this CAMPS
Table of channels
ACP127-parameters
5.11.1.3.1.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
Channel Classification and availability
If a channel check message shall be received daily
between 2345 and 0015
If periodicity for receiving channel check messages
from TRC shall be 30, 60, or [ minutes.
If a service message shall be automatic generated in
case of 140 identical characters have been received.
Allowed delay without preemption.
Time-out limit for receipt of Flash acknowledge.
5.11.1.3.2 H̲a̲r̲d̲w̲a̲r̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
Not applicable.
5.11.1.3.3 E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲M̲e̲c̲h̲a̲n̲i̲s̲m̲s̲
Errors are reported to Supervisor via Channel, Warning,
and Security Reports. Errors that do not fit into these
reports are handled by SSC.
5.11.1.4 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
5.11.1.4.1 P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲
5.11.1.4.1.1 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
a) Message Traffic Throughput
(Ref. CPS/210/SYS/001 3.4.1.2.1 k - p)
b) NICS TARE
(Ref. CPS/210/SYS/001 3.4.1.2.5)
c) TRC
(Ref. CPS/210/SYS/001 3.4.1.2.6)
d) ACE ACCIS
(Ref. CPS/210/SYS/001 3.4.1.2.7)
5.11.1.4.1.2 S̲t̲o̲r̲a̲g̲e̲
Not Applicable.
5.11.1.4.1.3 C̲o̲n̲n̲e̲c̲t̲i̲v̲i̲t̲y̲
(Ref. CPS/210/SYS/001 3.4.1.7)
5.11.1.4.1.4 T̲i̲m̲i̲n̲g̲
(Ref. CPS/210/SYS/001 3.4.1.6.2)
5.11.1.4.2 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲&̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲
a) External Channels and circuits
(ref. CPS/210/SYS/001 3.4.4.4.5)
b) Individual Channels
(ref. CPS/210/SYS/001 3.4.4.4.6)
c) Group of Channels
(ref. CPS/210/SYS/001 3.4.4.4.7)
d) All Channels
(ref. CPS/210/SYS/001 3.4.4.4.8)
5.11.1.4.3 S̲e̲c̲u̲r̲i̲t̲y̲
Before forwarding a message to transmission the classification
of the external channel is compared with the classification
of the message.
RIs are selected in accordance with classification
channel/message.
If no match in classification is found, the message
may be transmitted on a channel with higher classification.
In case no RI with higher classification exists, a
warning or security report is generated and the message
is queued for RI-assignment.
5.11.1.5 D̲e̲s̲i̲g̲n̲ ̲a̲n̲d̲ ̲C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
(Ref. 2.5).
5.11.1.6 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
(Ref. 2.6).
5.11.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲
5.11.2.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
This package has no direct external interfaces.
(Ref. 5.11.1.1.3).
5.11.2.2 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
5.11.2.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲D̲P̲)̲
Incoming messages for distribution
Outgoing messages for local distribution
Messages for distribution at CCIS/SCARS
5.11.2.2.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲T̲E̲P̲)̲
Supervisor Reports:
- Security Reports
- Warning Reports
- Channel Reports
Outgoing Service Messages entered by the Supervisor:
Incoming Service Messages to be printed at Supervisor
position.
Message Service Procedures:
- RI assignment (incl. T-instruction)
- Operating Signals assignment
- Group Count Verification
- Garbled messages
Rerun of previous complete outgoing message, entered
by supervisor.
Entering of complete messages from special devices
(e.g. PTR).
Released outgoing messages via a release-queue.
Punch of outgoing messages on the PTP.
5.11.2.2.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲S̲A̲R̲)̲
Storage of outgoing message with release-key/channel
key
Storage of incoming message with channel-key
5.11.2.2.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲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̲)̲
Short time storage of incoming message
Short time storage for ACP127-formatting
Facilities to update of MCB
Facilities to create and update a Routing List related
to a message
Update of released message with Station Serial Number
+ time for release
Automatic delete of Cosmic Top Secret Message if indicated
by Special Handling Instruction
5.11.2.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲L̲o̲g̲ ̲a̲n̲d̲ ̲A̲c̲c̲o̲u̲n̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲(̲L̲O̲G̲)̲
This interface is via CSF.
Log outgoing messages
Log incoming messages
Log channel discontinuity
Log invalid messages
5.11.2.2.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲S̲T̲P̲)̲
This interface is via CSF
Statistics incoming messages
Statistics outgoing messages
Statistics rejected messages
Statistics channel availability
5.11.2.2.7 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲I̲/̲O̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲I̲O̲C̲)̲
The main purpose of this interface is to achieve access
to the externals referenced under 5.11.1.1.3.
More specific interfaces to the EDC and X25 protocols
are:
- outgoing formatted message is delivered into an outgoing
message queue.
I.e. the message will be formatted as required of the
specific protocol type and a pointer to the message
is placed in the queue.
When a message has been sent, a response has to be
delivered back.
A response can be:
- Message-ID and time for start of transmission
- Message-ID and a code for premature termination
- Error-code for channel unavailability etc.
This package expects to receive messages arriving to
CAMPS via an incoming message queue. It also expects
to receive error-reports as defined under 5.11.1.2.3.8
(Incoming messages and errors).
The type of error can be related to a message or to
a channel and may be passed on to this package as a
"message".
5.11.2.2.8 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲(̲C̲S̲F̲)̲
Time-out facilities for automatic channel check and
flash acknowledge messages. (Start time-out, stop time-out).
5.11.2.2.9 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲(̲T̲M̲P̲)̲
Coordination of table and parameter updates of the
following control functions. (Ref. 5.11.1.3).
Message Processing Control.
External Connection Control.
Arrangement about special "database" with VDU pages
updated by CCIS.
5.11.2.2.10 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲S̲&̲C̲
Coordination of close for input on external channels
Ordered close-down in two modes
a) total close down
b) partial close down
Start up in initial or recovery mode.
