top - download
⟦290830e5c⟧ Wang Wps File
Length: 20607 (0x507f)
Types: Wang Wps File
Notes: CAMPS SYS. DES. SPEC.
Names: »0430A «
Derivation
└─⟦c2ca659c9⟧ Bits:30006002 8" Wang WCS floppy, CR 0037A
└─ ⟦this⟧ »0430A «
WangText
!…0b……86…1
…02…
…02…
…02…
…02…CPS/SDS/001
…02…NJ/810115…02……02…
CAMPS
SYSTEM
DESIGN
DESCRIPTION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.12 MESSAGE DISTRIBUTION PACKAGE .........
5.12.1 Summary of Requirements ..........
5.12.1.1 Package Description ..........
5.12.1.1.1 General Description ......
5.12.1.1.2 Internal Interfaces ......
5.12.1.1.3 External Interfaces ......
5.12.1.1.4 Chart over Interfaces ....
5.12.1.2 Functions in Detail ..........
5.12.1.2.1 Functional Requirements ..
5.12.1.2.1.1 Distribution of
Incoming Messages ....
5.12.1.2.1.2 Distribution of
Outgoing Messages ....
5.12.1.2.1.3 Other Distribution
Subjects .............
5.12.1.2.1.4 Distribution Selection
5.12.1.2.1.5 Alternative distribu-
tion..................
5.12.1.2.2 Functional Flow ..........
5.12.1.2.3 Functional Components ....
5.12.1.2.4 Recovery .................
5.12.1.3 Package Control ..............
5.12.1.3.1 Parameter Control ........
5.12.1.3.2 Hardware Control .........
5.12.1.3.3 Error Handling ...........
5.12.1.4 Characteristics ..............
5.12.1.4.1 Performance ..............
5.12.1.4.2 Availability and
Maintainability ..........
5.12.1.4.3 Security .................
5.12.1.5 Design and Construction ......
5.12.1.6 Documentation ................
5.12.2 Environment ......................
5.12.2.1 External Interfaces ..........
5.12.2.2 Internal Interfaces ..........
5.12 M̲E̲S̲S̲A̲G̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.12.1 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
5.12.1.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
5.12.1.1.1 G̲e̲n̲e̲r̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The Message DISTRIBUTION Package (MDP) performs internal
distribution of incoming and outgoing messages, comments,
messages for coordination, messages for printing, messages
for release, release notifications and specified distribution
from the Message Service Function, the Message Distribution
Control Function and the Supervisor.
Internal distribution means selection of queues for
terminals, devices, or lines based on either Headquarters
and standard distributions lists (SDL) or on specification
of staff-cell designators (SCD).
The Message DISTRIBUTION Package receives messages
from the TRAFFIC HANDLING Package and from the TERMINAL
Package (Refer fig. 5.12.1).
From the TRAFFIC HANDLING Package incoming messages
are queued for distribution determination based on
SDL (1), outgoing messages are queued for local distribution
based on a manually generated SCD list (2).
From the TERMINAL Package manual distribution of comments,
messages for coordination, messages for printing, messages
for release, and release notifications are executed
by an SCD list, or a device/terminal designator (3),
and any problems in the distribution is referred to
the TERMINAL Package (MDCO) (4).
The message DISTRIBUTION Package selects queues as
a result of the distribution criteria (5).
If both the user and the terminal profile checks (security
classification and special handling designator) are
fulfilled the message or comment is sent to the active
terminal queue. If only the terminal profile check
is fulfilled or the terminal is signed off, the message
or comment is sent to the passive terminal queue. If
the profile check fails on a passive terminal queue
the message or comment is sent to te MCDO.
When a terminal is signed on an active terminal queue
is created from the passive terminal queue. The active
terminal queue will contain all the messages the user
can access at the terminal position. When a terminal
is signed off the messages from the active terminal
queue will be transferred to the passive terminal queue.
However, Flash and Immediate messages will be sent
to the MDCO for alternative distribution. Immediate
messages will not be sent until ten minutes after the
terminal has been signed off.
When a device has been closed by the supervisor
no messages are sent to device queues. When
a device has been opened by the supervisor,
message is checked against the device profile;
if the match is fulfilled the message will
be sent to the device queue. If the match fails
the message will be sent to MDCO.
For encrypted messages and messages with special handling
instructions (exclusive or crypto security) a terminal
is specified by supervisor for automatic distribution.
5.12.1.1.2 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Distribution Package interfaces with following
other packages:
Traffic Handling Package (THP)
Terminal Package (TEP)
Storage and File Management (SFM)
SS & C (SSC)
Statistics (STP)
Table management (TMP)
5.12.1.1.3 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Via Traffic Handling Package and I/O Control Package.
CCIS
SCARS
Via terminal package and I/O control package
PTP
5.12.1.1.4 C̲h̲a̲r̲t̲ ̲o̲v̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Figure 5.12.1 shows the main interfaces to the MDP.
Figure 5.12.1…01…I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲ ̲F̲O̲R̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲
5.12.1.2 F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲i̲n̲ ̲D̲e̲t̲a̲i̲l̲
5.12.1.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Refer to Fig. 5.12.1 for events.
5.12.1.2.1.1 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Incoming messages are queued by the Traffic Handling
Package to the message DISTRIBUTION Package for internal
distribution. The internal distribution is based on:
a) Distribution within Headquarters. A CAMPS site
may serve up to 8 allocated headquarters. For the
HQs, the MDP generates a nominal distribution list
based on standard distribution lists for each HQ
using the SICs and distribution type indicator
of the message (peace, crisis, or exercise).
b) Distribution of special message categories:
- Encrypted messages
- Special handling messages of category exclusive
or crypto security.
For each of these messages, the nominal distribution
list contains one supervisor specified terminal
designator.
Data messages will be sent to the MDCO, unless
detection of headquarters indication (PLA) and
SICs provides for automatic distribution.
After generation of the nominal distribution list,
the incoming messages are either distributed to
staff cells and devices or queued for support by
the MDCO (see 4 and 5).
c) Incoming Messages are deffered to the MDCO for
the following reasons:
- Missing SICs
- Internal Handling Instructions
- Special Handling Designators
(except exclusive and crypto security)
- Supervisor parameters for distribution i.e.,
1) All incoming messages
2) All incoming messages of specified classification
3) All incoming messages except those of specified
classification
4) All incoming messages containing a SIC from
a table of up to 5 SICs.
A notification explaining the reason for MDCO assistance
and the Distribution List (staff cells and terminals)
as complete as possible based on the available information
are passed on to the MDCO.
5.12.1.2.1.2 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
After release and Station Serial Number assignment
outgoing messages are queued by Traffic Handling for
the MDP for internal distribution. The distribution
is specified as staff cells. The MDP distributes to
the specified staff cells (see 5) or in case of incorrectly
specified staff cell list for the MDCO (see 4).
5.12.1.2.1.3 O̲t̲h̲e̲r̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲S̲u̲b̲j̲e̲c̲t̲s̲
The MDP distributes to specified staff cells or device/terminal
positions.
From the Terminal Handling Package the following objects
are received for local distribution (refer figure 5.12.1):
a) Distribution of messages retrieved by the Supervisor
and specified for distribution to staff cells.
(3a)
b) Distribution of incoming messages to specified
staff cells from a Message Service position (3b).
The messages may be garble encrypted. Non printable
characters (TBD) are not included in the messages.
A comment by the message servicer may be attached
to the message.
c) Messages which have been deferred to the MDCO due
to an incomplete set of distribution instructions
or other (see 4) are returned to the MDP together
with an updated list of staff cells for distribution.
(3c)
d) Distribution of messages for release (3d).
When requested by the drafter the message will
be sent to the release position to which the drafter's
terminal position is associated. (Including messages
from CCIS and SCARS).
e) Distribution of release notifications (3f).
Upon release of a message, the releasing officer
may add comments to the automatic generated notification.
This release notification is distributed by the
MDP to the message drafter. If the terminal is
unavailable the notification is sent to MDCO. (See
5).
f) Distribution of messages for coordination (3f).
Messages in preparation may be sent for coordination.
The preparation terminal queues the message for
the MDP together with an indication of the coordinating
staff cell. The MDP distributes to the coordination
staff cell designator (see 5).
If a message for coordination cannot be distributed
to a specified staff cell, a notification (comment)
is generated and returned to the drafter by this
package. For SCARS and CCIS this procedure will
not be performed.
g) Distribution of comments (3g).
Any terminal position may generate comments. They
are queued for the MDP together with a list of
staff cells for distribution. The MDP distributes
the comment (see 5).
h) Distribution of messages for printing (3h).
If user activates the print-function, the message
is queued to the associated printer.
5.12.1.2.1.4 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲L̲i̲s̲t̲ ̲a̲n̲d̲ ̲Q̲u̲e̲u̲e̲i̲n̲g̲
The MDP distributes the subjects as described in 5.12.1.2.1.1,
5.12.1.2.1.2 and 5.12.1.2.1.3 by queues.
The queues may lead to:
CCIS (5a)
SCARS (5b)
Any Point to Point connection (5c)
Papertape punch (5d)
A coordination terminal (5e)
A reception position (presentation terminal) (5f)
A release terminal (5g)
Distribution to the queues is performed by means of
the distribution list with possible modifications by
the MDCO.
If both user and terminal profile checks are fulfilled
the message is sent to the active terminal queue. If
only the terminal profile check is fulfilled or the
terminal is signed off, the message is sent to the
passive terminal queue, however, Flash messages are
sent to the MDCO for alternative distribution. If the
terminal is signed off Immediate messages are also
sent to the MDCO.
Any queue leading to a terminal position not having
security classification or allowed special handling
categories to receive will not be used. For each of
these queues, the subject will be queued for the MDCO
for selection of an alternative (6).
5.12.1.2.1.5 A̲l̲t̲e̲r̲n̲a̲t̲i̲v̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The MDP will queue messages and comments for which
the passive terminal queue was not accessible to the
MDCO for selection of alternative queue (6). The MDCO
selects this alternative queue and returns the subject
to the MDP (3c).
The supervisor can also specify that Flash and Immediate
messages and comments shall be automatically distributed
to a Duty officer terminal position in each HQ during
Quiet Hours. For Immediate message a copy is also queued
to the receipient's passive terminal queues. Messages
for coordination are not queued, but the originator
is notified that the message was not delivered.
5.12.1.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲F̲l̲o̲w̲
Following references are to points in figure 5.12.1.2.2-1:
1) A pointer to the next message waiting for distribution
is fetched from the Message Distribution Queues
(MDQ) together with a transaction code.
2) Information for distribution determination is to
be found in the associated MCB.
3) An incoming message is selected for special treatment
as referenced in point 4) or 5) if it carries any
of those characteristics.
4) CODRESS messages and messages containing special
handling instructions Exclusive or Crypto Security
will be sent to a terminal specified by supervisor
(PTP).
5) Other incoming messages are queued for MDCO in
case:
- Specified by supervisor parameters
- Special handling instructions
(not = exclusive or Crypto Security)
- Internal handling instructions
- Contained in list of special 5 SICs
- Data message will be sent to the MDCO unless
detection of format line 7 (PLA) and 12b SIC
provide for automatic distribution
6) The message is found valid for automatic distribution.
7) Which implies generation of a Distribution List.
8) MDCO may output any message on the PTP. This procedure
will then be considered the final distribution.
9) A message reentered from MDCO (or Message Service)
for local distribution. Together with the message
is entered a Distribution List.
10) The distribution selections are checked against
the terminal profile and control tables.
E.g.- Missing SICs
- Illegal SCDs or SICs
- Terminal classification
If a check was unsuccessful the SCDs associated
to that terminal are flagged as undeliverable,
and procedures as referenced under 11) or 12) are
performed.
11) A note is returned to the drafter if the message
was sent for coordination.
12) Other message types are queued back to MDCO for
alternative distribution. That includes all undeliverable
message types bound for SCARS or CCIS.
13) Message distribution by placing a pointer to the
message and a transaction code in the terminal
queues. For SCARS and CCIS in special queues.
Figure 5.12.1.2.2-1…01…Interfaces and Functional Flow
14) Information for statistics is queued to the STP.
15) If a terminal gets unavailable (SIGN-OFF) while
a message is waiting for print-out in the active
terminal queue, the message is queued to the passive
terminal queue, except Flash and Immediate messages
which are sent to MDCO.
16) During Quiet Hours the supervisor can also specify
that Flash and Immediate messages and comments
shall be automatically redistributed to a Duty
officer terminal position.
5.12.1.2.3 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
The main functional components of the MDP are shown
in fig. 5.12.1.2.3-1.
Decision-tables (fig. 5.12.1.2.3-2 to 5.12.1.2.3-8)
are explaining the distribution mechanisms for all
possible message types.
5.12.1.2.4 R̲e̲c̲o̲v̲e̲r̲y̲
No recovery actions are performed by this package.
8 stk. figurer inds`ttes her: 5.12.1.2.3-1 til -8
5.12.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
5.12.1.3.1 P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
The MDP obtains parameters for distribution list generation
from the Table Management Package. These parameters
are:
- SIC tables (one per HQ) generating the corresponding
SDLs.
- SDL tables generating SCDs based on exercise traffic,
normal traffic, or traffic during crises.
- SCD table generating queued designator and number
of printed copies.
- Queue designator for distribution of incoming encrypted
message.
- Queue designator for Data Message (should be MDCO).
- Supervisor selection of MDCO assistance
- Duty officer terminal designator for alternative
distribution of Flash and Immediate messages
at quiet hours
5.12.1.3.2 H̲a̲r̲d̲w̲a̲r̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
N/A.
5.12.1.3.3 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Errors not handled (TBD) by the MDP are returned to
the SS&C system.
5.12.1.4 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
5.12.1.4.1 P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲
a) T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The MDP shall support following throughput (in
busy minute, busy hour, 24 hour period).
- 30, 600, 3000 incoming messages
- 6, 180, 900 outgoing messages
- 12, 360, 1800 messages for coordination
- 6, 180, 900 messages for release
- 6, 180, 900 release notifications with
release confirmed.
In addition to this is the load from release refusals,
to and from MDCO.
b) S̲t̲o̲r̲a̲g̲e̲
N/A.
c) C̲o̲n̲n̲e̲c̲t̲i̲v̲i̲t̲y̲
(Ref. CPS/210/SYS/0001 Fig. 3.4.1.7.1)
d) T̲i̲m̲i̲n̲g̲
TBD (see CPS/210/SYS/0001, section 3.4.1.6.2 for
overall requirements)
5.12.1.4.2 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲
N/A.
5.12.1.4.3 S̲e̲c̲u̲r̲i̲t̲y̲
Before sending a message or comment to a terminal queue
there will be a security control between the classification
of the message and the active terminal profile. If
no match in the classifications is found, the message
will be checked against the terminal profile. If no
match is found this time the message will be returned
to either MDCO or drafter (see functional flow).
5.12.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.12.1.6 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
(Ref. 2.6).
5.12.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲
5.12.2.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N/A.
5.12.2.2 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
a) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
1) Incoming messages. Traffic Handling queues
incoming messages for the MDP. The message
contains format lines 5 - 13 without routing
indicators. For CODRESS and Data messages
no conversion is performed (lines 1-4 kept
as received). Together with the message, extract
of message information is queued in a separate
field: (MCB).
The following information is needed:
- Message Classification
- Special handling instructions
- Action and Info precedence
- Message Type
- Headquarters indication
- SIC list
- Indication of internal handling instructions
- Indication of exercise
2) Outgoing messages. Traffic Handling queues
after release outgoing messages (plaindress
only) for the MDP for local distribution.
The message contains format lines 5 - 13 without
routing indicators. Together with the message,
extract of message information is queued in
a separate field (MCB).
The following information is needed:
- Message Classification
- Special handling instructions
- Precedence
- Message Type
- Distribution Information
3) The Traffic Handling Package is interfaced
again with messages to be locally distributed
at SCARS/CCIS. The THP performs the conversion
to special SCARS/CCIS format.
b) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲
1) The MDP receives various subjects for distribution
as specified from the Terminal Package. E.g.
messages for coordination, comments, messages
for printing, messages for release, and release
notifications. The subject is queued for distribution
together with a transaction code and a distribution
list containing:
- Classification
- Special handling instructions
- Action Precedence
- Info Precedence
- List of action SCD's
- List of info SCD's
2) Automatic distribution of encrypted messages
to the supervisor specified terminal (PTP).
c) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲F̲i̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The MDP accesses the storage and File Management
package via the IO control for message and file
access.
- Update of the MCB with distribution information.
- Creation and update of a distribution list.
d) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲S̲ ̲&̲ ̲C̲ ̲S̲y̲s̲t̲e̲m̲
The MDP is initialized by the SS & C System. Restart
and close down is also performed by the
SS & C System
Irrecoverable errors are returned to the SS & C
System.
e) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The MDP synchronizes with TMP for updating of tables
and parameters as referenced under 5.12.1.3.1.
f) I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
The MDP will specify information to statistics
of message distributions and MDCO invocations.
