top - download
⟦66aa42af8⟧ Wang Wps File
Length: 20416 (0x4fc0)
Types: Wang Wps File
Notes: CPS/210/SYS/0001
Names: »0594A «
Derivation
└─⟦69f081490⟧ Bits:30006004 8" Wang WCS floppy, CR 0039A
└─ ⟦this⟧ »0594A «
WangText
…00……00……00……00…C…0a……00……00…C…0b…B…09…B…00…B B…05…A…86…1 …02… …02… …02…
…02…CPS/210/SYS/0001
…02…831219…02……02…
CAMPS SYSTEM REQUIREMENTS
…02…ISSUE 3.14…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲2̲
3.2.2 Incoming Message......................
95
3.2.2.1 Message Reception Procedures......
95
3.2.2.2 ACP127 Analysis...................
95
3.2.2.2.1 Format Line Detection ........
99
3.2.2.2.2 Selection of Parameter........
100
3.2.2.2.3 Determination of Message Type
100
3.2.2.3 Message Distribution .............
100
3.2.2.3.1 Automatic Distribution .......
106
3.2.2.3.2 Distribution of Service
Messages .....................
108
3.2.2.3.3 Handling of
Codress/Plaindress Encrypted
Messages .....................
108
3.2.2.3.4 Handling of Data Messages ....
108
3.2.2.3.5 Handling of CLEAR Messages ...
108
3.2.2.4 Procedures Related to Receipt of
FLASH messages....................
108
3.2.2.5 Handling of Messages from SCARS/
ACCIS ............................
108
3.2.2.5.1 Messages from SCARS ..........
108
3.2.2.5.2 Messages from ACCIS ..........
108
3.2.2.5.3 Comments/VDU Display from
SCARS/ACCIS ..................
108
3.2.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) CAMPS shall support the following major functions
for incoming message handling.
1) Message Reception Procedures (Ref. section
3.2.2.1)
2) ACP 127 Analysis (Ref. section 3.2.2.2)
3) Message Distribution (Ref. section 3.2.2.3)
b) Other major functions shall act as support functions
to the message handling functions. These functions
are
1) Storage and Retrieval Functions.
2) Logging and Reporting Functions.
3) Terminal Handling Functions.
c) Figure 3.2.2-1 presents the functional relationships
for incoming message handling functions.
d) Message types applicable to incoming message handling
are those specified in section 3.2.1.1.
3.2.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
a) Each message received shall be uniquely identified
by a channel designator and a channel serial number.
This information shall be contained in "Format
Line 1" of ACP127 formatted messages.
b) Upon reception of a message CAMPS shall check the
channel serial number in "Format Line 1" to determine
whether it is in sequence.
1) In all cases, if the number is not present
or not equal to the number of the latest message
incremented by one a warning shall be printed
out at the supervisors position both indicating
the expected number and the received incorrect
number. A log entry shall be made (refer to
section 3.2.5.6.1.1.1 b)
2) If the number is less than or equal to the
number of the last received message, the message
shall be presented to the MSO. He can decide
to have the message sent for normal distribution.
On being sent for distribution, the message
shall be stored. …86…1 …02… …02… …02… …02…
3) If the number is greater than the number of
the last received message incremented by one
the message shall be handled as a valid message
and the "expected channel serial number" shall
be reset to the one received plus one.
4) If a message is received without a channel
serial number the "expected channel serial
number" shall be allocated to the message by
the system. The expected number for the next
message shall be equal to the allocated number
plus one. The occurence shall be signalled
to the supervisor as for incorrect serial number.
The message shall be presented to the MSO
who can decide to have the message sent for
normal distribution. On being sent for distribution,
the message shall be stored.
figur. ?
3.2.2.2 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
a) The format tolerances of CPS/ICD/0003 shall apply
to messages in ACP 127 format.
b) Certain departures from the ACP 127 format are
allowed.
c) Unacceptable departures such as
- no start of transmission function (VZCZC)
shall result in no acceptance of input.
d) The following set of conditions shall lead to immediate
insertion of termination sequence and queuing for
message service
1) Consecutive start of message (SOM) sequences.
2) Oversized messages.
3) Halted messages.
4) Consecutive identical characters
e) In the following cases the message shall be queued
for message service position.
1) Lines are too long.
2) Missing end-of-transmission sequence.
3) If one or more of the format lines 1, 2, 3,
4, 5, 7, 8, 11, 12a, 13, 15, and 16 are garbled.
4) If a mandatory line is not present, except
for format line 12b to 12d.
5) If a garble is found between the end of a recognisable
line and the beginning of a subsequent mandatory
line.
6) If a message contains a FL14 with corrections.
f) If accounting information in format line 10 is
garbled, then normal distribution shall apply.
If the group count (GR...) is garbled but recognisable,
then the message shall be sent to the dedicated
PTP.
g) If one of the format lines 12b, 12c, and 12d are
garbled, then the message shall be sent to MDCO.
h) The following consistency checks between format
lines shall be performed. If inconsistency between
the format lines the message shall be sent to Message
Service Position.
1) Misroute/mis-sent check.
Check RI in format line 2 to be consistent
with RI/PLA in format line 7/8.
2) Security check.
Check classification in format line 4 to be
consistent with classification in format line
12a.
3) Special handling check.
Check special handling designator in format
line 4 to be consistent with special category
warning in format line 12a.
i) The following consistency checks between format
lines shall be performed. If inconsistency between
format lines, the message shall be sent to MDCO.
Check simultaneous presence of SIC AAA in Fl 12b
and one of the following SPECAT WARNINGs in Fl
12a.
- ATOMAL
- Exclusive
- Crypto security
- For national eyes only
j) Messages with the standard end-of-transmission
sequence for preemption (ZPH) are dropped.
k) Detailed specification for handling of the above
cases are contained in CPS/ICD/0003.
l) Each message consists of a number of format lines.
Each format line present consists of one or more
physical lines (a physical line is characterised
by having an end-of-line character sequence).
m) The ITA no. 2 characters LS and FS as well as the
ITA no. 5 characters SI and S0 are not significant
for CAMPS internal message handling and can, therefore,
be deleted before analysis of all incoming messages.
n) The requirements specified in the subsequent sections
are related to the following analysis of ACP 127
formatted messages.
1) Detection of format line
2) Selection of parameters from format/physical
lines
3) Determination of message type.
3.2.2.2.1 F̲o̲r̲m̲a̲t̲ ̲L̲i̲n̲e̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
Detection of format lines shall be based on the character
sequences specified below:
FORMAT LINE DETECTION CRITERIA
1 "VZCZC" (SOTF)
2 Dual precedence prosign
3 "DE"
4 "ZNY" or "ZNR"
5 Precedence, datetime group
6 "FM"
7 "TO"
8 "INFO"
9 "XMT"
10 "GR"
11 "BT"
12a CLASSIFICATION/SPECAT
12b "SIC"
12c "EXER" or "OPER"
12d "PERSONAL" or "ADDRESSED"
13 "BT"
14 "C"
15 "H"
16 EOTF
3.2.2.2.2 S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
Each format line contains a number of parameters which
are mandatory or optional.
Figure 3.2.2.2.2-1 presents an overview of the parameters
applicable for each format line and physical line.
3.2.2.2.3 D̲e̲t̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲
Processing subsequent to ACP127 analysis depends on
message type.
The message type shall be determined from the format
lines existing in a message. Figure 3.2.2.2.2-1 presents
a specification of the formats lines contained in the
different message types.
3.2.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
a) Processing and distribution subsequent to ACP127
analysis depend on the message type.
b) Overleaf is presented an overview of how message
types are processed subsequent to message reception
and ACP127 analysis. (Refer to figure 3.2.2.3-1).
c) Fig. 3.2.2.3-2 provides an overview of incoming
message distribution. Details are given in CPS/ICD/0003.
d) In case routing indicators are detected in format
line 2 which are not relevant to CAMPS the message
shall be queued for message servicing for decision
on alternative routing.
e) The detection of a T-instruction in format line
4 shall lead to automatic relay if associated to
local RI except for RIs for SCARS and ACCIS.
f) In case of relevant routing indicators in format
line 2 the PLAs in format lines 7 & 8 (plus PLAs
in AIGs, any single addressee PLA and ZEN PLAs)
shall be compared to PLA's of the associated headquarters.
Incoming messages containing a local PLA preceded
by a ZEN shall be distributed normally.
g) ATOMAL, non encrypted messages are subject to automatic
distribution except for print, which shall always
be at a supervisor designated printer.
h) Relaying of messages to SCARS and ACCIS shall be
based on RIs in format line 2 or T-instructions
in format line 4.
Figure 3.2.2.2.1-1
Figure 3.2.2.2.1-1
Figure 3.2.2.2.1-1
Figure 3.2.2.2.1-1
…01…FIGURE 3.2.2.3-1…86…1 …02… …02… …02… …02…
FIGURE 3.2.2.3-2
i) Messages with Special Handling Designators shall
be treated as specified in figure 3.2.2.3-2.
j) Readdressed messages shall be subject to automatice
distribution.
k) Further, distribution is automatic apart from the
following cases.
1) Message is queued for message service for garble
correction. Having been corrected it is queued
for further automatic distribution.
2) Message is queued for message distribution
control for the following reasons:
- garbled SIC's
- missing SIC's
- internal handling instructions (ref. CPS/230/ICD/0003)
- special handling designators as specified
in figure 3.2.2.3-2
- supervisor directed (refer to section 3.2.4.1.1.3).
- incoming abbreviated plaindress messages
for distribution assignment
3) Having been processed by the MDCO the message
is queued for further automatic distribution.
3.2.2.3.1 A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
a) After successful analysis of the incoming message
and possible corrections (message servicing or
message distribution control) the message shall
be distributed locally within the addressed headquarters
as follows (fig. 3.2.2.3-1). The addressed headquarters
are deduced on the basis of PLA and/or RI.
Figure 3.2.2.3-2…01…TREATMENT OF MESSAGES WITH SPECIAL HANDLING DESIGNATORS
Automatic distribution within the addressed headquarters
is based on the SIC contained in FL 12a. Distribution
rules are shown on figure 3.2.2.3.1-1.
Automatic distribution shall cause messages to be:
1) queued to the terminals associated with SCD's
from the SDL's pointed to by the subject SIC's
of the message. Duplicate SCDs shall be ignored.
2) queued to the terminals associated with the
SCD's specified by the MDCO.
3) There will be a separate set of pointers to
the Normal, Exercise and Crisis distribution
SDLs. For exercise and crisis the SICs may
be the same as for normal distribution. The
criteria for selection of exercise is FL12c.
The SIC denoting the exercise nature shall
be ignored. Crisis distribution replaces normal
distribution by means of a supervisor procedure.
4) If a 3 letter SIC exists in the SIC table with
a non blank SDL number, which matches one of
the SICS in the message, then that SDL will
be used for distribution. When no 3 letter
SICs as specified above exists, then a 2 letter
SIC will be searched and used if available.
Figure 3.2.2.3.1-1…01…SIC Based Distribution Rules
b) Each copy shall be presented to the recipient in
format E1 with the following information.
1) Special Handling
2) Action Precedence
3) All Action Staff Cells for the Headquarters
4) All Info Staff Cells for the Headquarters
5) Format Lines 5 to 13 (as applicable) from the
message concerned.
6) The TO and FROM RIs (RIs from format line 2
and 3) will be displayed instead of the missing
PLAs for messages of type abbreviated plaindress
c) A message that during the automatic distribution
is destined to a terminal position to which the
message, for the time being, cannot be delivered
shall be sent to the Message Distribution Control
position. A message is considered non-deliverable
when
1) the classification of the message is higher
than that contained in the terminal profile
(refer section 3.2.3.1. d).
2) the special handling category of the message
is not included in the special handling category
of the terminal profile (refer to section 3.2.3.1.
d).
3) The terminal does not possess the functional
capability of receiving the message.
d) A message that during the automatic distribution
is destined to a terminal position at which the
message, for the time being, can not be presented,
shall be sent to the Message Distribution Control
position in case of precedence FLASH and IMMEDIATE.
In case of precedence IMMEDIATE, a copy shall
always be queued at the terminal as well. A message
is considered non-presentable when
1) The terminal is manned and the terminal position
is ATTENDED, but the classification of the
message is higher than that of the terminal/operator,
the special handling category of the message
is not specified for the terminal/operator,
or the functional capability of reception is
not specified for the terminal/operator.
2) The terminal is manned and the terminal position
is UNATTENDED.
3) The terminal is unmanned.
e) During Quiet Hours messages of FLASH or IMMEDIATE
precedence being non-presentable as referenced
in section d2 and d3 above shall be queued to the
supervisor assigned duty officer position (refer
3.2.4.1.1.3).
3.2.2.3.2 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
All service messages (also abbreviated) shall always
be directed to the supervisor except those related
to the automatic channel control as specified in CPS/ICD/004
and CPS/ICD/007.
3.2.2.3.3 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲C̲o̲d̲r̲e̲s̲s̲/̲P̲l̲a̲i̲n̲d̲r̲e̲s̲s̲ ̲E̲n̲c̲r̲y̲p̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
Presence of group count (GR) in FL10 (ACP 127 format)
indicates the codress/plaindress encrypted messages.
The above messages shall be routed to a dedicated PTP
for off-line decryption.
Decrypted messages will be entered via a dedicated
PTR. The decrypted message will contain FL1 (ACP 127
format) which indicates that local distribution is
required.
FL1 is the indicator which differentiates it from encrypted
outgoing messages. The decrypted message will contain
the same ACP 127 format lines as before decryption.
3.2.2.3.4 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲D̲a̲t̲a̲ ̲M̲e̲s̲s̲a̲g̲e̲
Data messages are detected by a special handling designator
in FL4 (ACP 127 format).
Data messages shall be distributed according to PLA
and SICs as for plaindress messages, refer figure 3.2.2.3-2.
Data messages will be treated as garbled if they contain
non-printable characters.
The non-printable characters will be displayed as the
sign (monkey tail) when the garbled message is presented
for the MSO.
Data messages with no EOLF in the text will be made
displayable.
3.2.2.3.5 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲C̲L̲E̲A̲R̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Messages with CLEAR classification on FL 12a shall
be treated as CONFIDENTIAL, unless the classification
in FL4 is higher than this.
3.2.2.4 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲R̲e̲c̲e̲i̲p̲t̲ ̲o̲f̲ ̲F̲L̲A̲S̲H̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
If messages received by a CAMPS has the precedence
FLASH and format line 4 of the message does not contain
an inhibit receipt flag (ZGC) a service message as
specified in section 3.2.1.6.4 shall be transmitted
to the originating station. Format and content of FLASH
receipt message is as specified in 3.2.1.6.4.
When a Flash receipt message is received, it is treated
as in section 3.2.1.6.4.
Routing based on:
1) RI in FL2 and/or T-instruction in FL4
2) PLA (SCD)
3) RI in FL2
4) PLA (or RI)
Figure 3.2.2.5-1
3.2.2.5 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲r̲o̲m̲ ̲S̲C̲A̲R̲S̲/̲A̲C̲C̲I̲S̲
3.2.2.5.1 M̲e̲s̲s̲a̲g̲e̲s̲ ̲F̲r̲o̲m̲ ̲S̲C̲A̲R̲S̲
Incoming messages are in ACP127 format.
If CAMPS RI in FL2 then local distribution.
CAMPS shall transmit incoming messages from SCARS,
if specified. The transmission is based on RIs in FL2
and not based on T-instructions. No check on the contents
of FL7/8 shall be performed for external RIs.
3.2.2.5.2 M̲e̲s̲s̲a̲g̲e̲s̲ ̲F̲r̲o̲m̲ ̲A̲C̲C̲I̲S̲
a) Incoming messages are in modified E1 format.
b) If CAMPS PLAs in address list then local distribution.
c) CAMPS has responsibility for coordination (if specified),
for release (if specified) and for transmission
of messages from ACCIS.
d) If coordination SCD (FL D4) is specified, then
the associated user takes over the responsibility
for the further processing of that message.
e) If release SCD (FL D3) is specified, then CAMPS
has the responsibility to release the message.
f) No coordination will be performed if a release
SCD (FL D3) has been detected.
g) If the specified SCD for coordination or release
is valid, then the message will be displayed in
SCARS/ACCIS format E1.
h) Any deviations concerning the message for coordination
or release is not reported automatically to ACCIS.
i) If the releasing officer releases the message,
then it will be converted from E1 to ACP127 format
and transmitted.
j) The release notification will be queued to the
releasing officer and will not be sent to ACCIS.
k) If the specified SCD is unknown, or leads to a
terminal without release capability, then the message
will be forwarded to the MDCO.
l) The message will be deleted after presentation
to the MDCO. The MDCO may print the message.
3.2.2.5.3 C̲o̲m̲m̲e̲n̲t̲s̲/̲V̲D̲U̲ ̲D̲i̲s̲p̲l̲a̲y̲s̲ ̲f̲r̲o̲m̲ ̲S̲C̲A̲R̲S̲/̲A̲C̲C̲I̲S̲
a) If an incoming comment/VDU Display contains an
unknown SCD or an unknown display name, then the
comment/VDU Display will be sent to the MDCO, who
can print the item. The item will be deleted after
presentation for the MDCO, who may report the event
to SCARS/ACCIS by a comment.
b) If the VDU Display contains a valid name, then
the Display database will be updated, and the VDU
Display will be queued for the specified SCD, if
any.
