top - download
⟦d5f396c09⟧ Wang Wps File
Length: 48898 (0xbf02)
Types: Wang Wps File
Notes: CPS/210/SYS/001
Names: »0593A «
Derivation
└─⟦69f081490⟧ Bits:30006004 8" Wang WCS floppy, CR 0039A
└─ ⟦this⟧ »0593A «
WangText
>…09…>…01…>…06…<…0d…<
<…06…<…07…;…08…;…0c…;…0d….…0a….…0f….…05……1c……01……1c……02……1b……08……86…1
…02…
…02… …02…
…02…CPS/210/SYS/0001
…02…831219…02……02…
CAMPS
SYSTEM
REQUIREMENTS
…02…ISSUE
3.14…02…CAMPS
3.2 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
The following section will exhaustively specify the
functional requirements to CAMPS.
Section 3.2.1 and 3.2.2 defines all functional capabilities
related to processing of outgoing and incoming messages
respectively. The sequence in which the functional
capabilities are presented are as they appear during
message processing.
Section 3.2.3 specifies all functional capabilities
related to terminals and the associated equipment.
The section has been structured in such a way, that
it presents the functional capabilities seen from a
user's point of view.
Section 3.2.4 defines all required capabilities for
supervisory control commands, message service, message
distribution control, system status and alarm, engineering
functions and software maintenance.
The Section is not presented from an operational point
of view, but more in terms of functional capabilities.
Section 3.2.5 specifies the events for which log entries
shall be made and the information associated with the
log entries.
Section 3.2.6 defines the required statistical reports
related to channel traffic and transactions at terminals.
Section 3.2.7 specifies storage and retrieval requirements
of incoming and outgoing messages.
Section 3.2.8 defines the requirements related to initialization,
error detection, and recovery.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲1̲
…02……02……02…3.2.1 Outgoing Messages ................... 55
…02……02……02……02…3.2.1.1 Message Types and their Flow
through the CAMPS System ........
55
3.2.1.1.1 General Structure of Messages
55
3.2.1.1.2 Message Types ................
56
3.2.1.1.3 Flow of Outgoing Messages ....
57
…02……02……02……02…3.2.1.2 Operational Messages ............ 60
…02……02……02……02……02…3.2.1.2.1 Message Preparation ......... 62
…02……02……02……02……02……02…3.2.1.2.1.1 New Message Preparation .. 62
3.2.1.2.1.1.1 Preparation of Message
Header ...............
63
3.2.1.2.1.1.2 Preparation of Message
Text .................
66
3.2.1.2.1.1.3 Correction of Header
and/or Text ..........
67
3.2.1.2.1.1.4 Append/Coordinate/Re-
lease/Defer ..........
67
…02……02……02……02……02……02…3.2.1.2.1.2 Message Editing ......... 68
…02……02……02……02……02……02…3.2.1.2.1.3 Append Message ........... 69
…02……02……02……02……02……02…3.2.1.2.1.4 Message Coordination .... 69
…02……02……02……02……02…3.2.1.2.2 Comments .................... 70
…02……02……02……02……02……02…3.2.1.2.2.1 New Comment Preparation .. 70
…02……02……02……02……02……02…3.2.1.2.2.2 Comment Editing ......... 71
…02……02……02……02……02……02…3.2.1.2.2.3 Comment Presentation .... 72
…02……02……02……02……02…3.2.1.2.3 Message Release ............. 72
…02……02……02……02……02…3.2.1.2.4 Local Distribution .......... 73
…02……02……02……02…3.2.1.3 Service Messages ................ 74
…02……02……02……02……02…3.2.1.3.1 Preparation ................. 74
…02……02……02……02……02……02…3.2.1.3.1.1 Initial Preparation ..... 75
…02……02……02……02……02……02…3.2.1.3.1.2 Editing ................. 75
…02……02……02……02…3.2.1.4 Entry of Complete Messages ...... 76
…02……02……02……02……02…3.2.1.4.1 Entry from OCR .............. 77
…02……02……02……02……02…3.2.1.4.2 Entry from PTR .............. 77
3.2.1.4.3 Entry of Codress/Plaindress
Encrypted Message ............
77
3.2.1.4.4 Messages to SCARS and ACCIS ..
77
…02……02……02……02…3.2.1.5 ACP127 Conversion ............... 77
…02……02……02……02……02…3.2.1.5.1 Conversion of Operational
Messages with Plain Text ....
78
…02……02……02……02……02…3.2.1.5.2 Conversion of Service
Messages ....................
89
…02……02……02……02……02…3.2.1.5.3 Conversion of Complete
Messages ....................
89
…02……02……02……02…3.2.1.6 Transmission .................... 90
…02……02……02……02……02…3.2.1.6.1 Channel Selection and
Identification ..............
90
…02……02……02……02……02…3.2.1.6.2 Procedures Related to
Premature Termination of a
Transmission ................
92
…02……02……02……02……02…3.2.1.6.3 Procedures Related to the ZEN
Prosigns ....................
92
…02……02……02……02……02…3.2.1.6.4 Procedures Related to
FLASH Receipt ...............
93
3.2.1.6.5 Handling of CRYPTO SECURITY ..
93
3.2.1.6.6 Procedures for Sending Auto-
matically Generated Abbrevi-
ated Service Message .........
93
3.2.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) This section describes the processing of outgoing
messages by CAMPS from the initial preparation
through all the stages until transmission.
b) The section is organized as follows:
c) Section 3.2.1.1 identifies the different types
of messages which the CAMPS system shall be able
to process and gives for each type an outline of
their functional flow through the system.
d) Section 3.2.1.2 describes how operational messages
are prepared by users, procedures associated with
their release and outlines the local distribution
required for outgoing operational messages.
e) Section 3.2.1.3 deals with service messages and
how they are prepared by the supervisor.
f) Section 3.2.1.4 describes how complete messages
are entered into the system and the involved system
processing.
g) Section 3.2.1.5 describes for each message type
the ACP127 conversion. All outgoing messages shall
be converted into the relevant ACP127 format before
transmission.
h) The processing of converted messages related to
transmission is described in section 3.2.1.6.
3.2.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲s̲ ̲a̲n̲d̲ ̲t̲h̲e̲i̲r̲ ̲F̲l̲o̲w̲ ̲t̲h̲r̲o̲u̲g̲h̲ ̲t̲h̲e̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
Messages are constituted of two parts, the message
header and the message text.
3.2.1.1.1 G̲e̲n̲e̲r̲a̲l̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲. The message header contains the
information which is necessary for the automatic
processing of the message from its origination
to its destination(s). After creation of the message
header each entry shall be validated with respect
to syntax. Validation of the semantic shall be
performed to a certain extent too.
b) M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲.̲ The message text (excluding introductory
text as specified in ICD/0003) contains no information
necessary for the automatic processing of the message
by CAMPS. Message text is treated as though it
is in free format by CAMPS. The only validation
being performed (no validation for data messages
and messages with encrypted text) is that text
lines do not exceed 69 characters.
3.2.1.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲s̲
The following three message types shall be recognized
by the CAMPS system:
- Operational Messages
- Service Messages
- Data Messages
a) O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. This type is the one which
may be originated or received by common users of
the CAMPS. Two types shall exist:
- Operational messages with plain text
- Operational messages with encrypted text
b) S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. Service messages are generated/handled
either automatically by CAMPS or by the supervisor.
The message text contains control information of
the message exchange between the CAMPS sites. Two
types shall exist:
- Service messages
- Abbreviated service messages
c) D̲a̲t̲a̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. The message text differs from the
other message types in the following way: the message
text comprises a datastream which may or may not
include End of Line Function.
Data Messages shall not be paged by CAMPS. Maximum
size is 12,000 characters.
3.2.1.1.3 F̲l̲o̲w̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The formal presentation of a message depends on
the stage of processing. Messages distributed
to or received from external circuits are in ACP
127 format. Messages inside a CAMPS system are
in internal formats.
b) Messages for transmission may at the originating
CAMPS be entered either as complete messages, i.e.
in ACP 127 format without format line 1, in OCR
input format, or by means of interactive procedures.
c) The processing of outgoing messages and how messages
are being entered depends on the message type.
This dependency is shown in fig. 3.2.1.1-1 and
fig. 3.2.1.1-2.
Fig. 3.2.1.1-1
Fig.3.2.1.1-2
3.2.1.2 O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The system shall support the functions for outgoing
messages listed below:
1) Message preparation
2) Message release
3) Local distribution of outgoing messages
4) ACP 127 conversion
5) Transmission of outgoing messages
b) Further, the following support functions described
elsewhere within this document shall be supported
by the CAMPS:
1) Storage and retrieval functions
2 Logging and reporting functions
3) Supervisory functions
4) Terminal handling functions
Fig. 3.2.1.2-1 illustrates the processing of operational
messages.
c) This section contains a description of how operational
messages with plain text shall be prepared by users
and further describes the processing of the message
performed by the system from preparation through
release and local distribution until the stage
where the ACP 127 conversion takes place.
Fig. 3.2.1.2-1
3.2.1.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Message preparation shall be supported by the following
procedures (ref. CPS/230/ICD/0001).
1) New message preparation
2) Message editing
3) Append message
4) Message coordination
3.2.1.2.1.1 N̲e̲w̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Associated formats: A, M
Two options exist for new message preparation
- Initial message preparation
- Selection of pre-defined message preparation
a) Initial message preparation, format A consists
of:
- a header part
- a text part
Format A assists the user in entering data during
the message preparation.
b) Predefined messages, format M, consist as format
A of:
- a header part
- a text part
The header part may be stored either with some
of the header information filled in or with no
header information filled in.
The text part may be stored either with a text
format or with free text format.
The system shall store up to 200 of these predefined
messages.
c) New message preparation shall be performed by means
of interactive procedures.
Initial message preparation consists of the following
steps.
- Preparation of message header
- Preparation of message text
- Edit of header and/or text
- Append a text of a message.
- Send the message for coordination or to the
release terminal where it may be released
- Defer the message for later processing
3.2.1.2.1.1.1 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲
a) Two types of message header exist:
1) Initial message header creation
2) Predefined message header creation
b) I̲n̲i̲t̲i̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲
Header creation involves separate input by the
drafter of each parameter and subsequent syntax
validation.
The parameters are listed below:
1) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory.
2) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
Parameter is optional.
3) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲,̲ ̲A̲c̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter is mandatory.
4) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲l̲e̲v̲e̲l̲,̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter is mandatory, if there are info addressees.
The precedence level for information addressees
may not be higher than the one specified for
action addressees. This shall be checked by
the system.
When precedence specified for action addressee(s)
is of type FLASH or IMMEDIATE and the precedence
for info addressee(s) is lower the procedure
in section 3.2.1.5.1.a shall apply.
5) A̲c̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types:
- PLA, i.e. Plain Language Address
- Reference Number (each PLA has o̲n̲e̲ associated
ref. number)
- AIG, Address Indicator Group (numerical
id.)
- Address Group (Each AIG has o̲n̲e̲ associated
Address Group, alpha id)
- "X" PLA
The system shall carry out a validation of
the parameters entered. If a PLA is not in
the system address tables, this fact shall
be displayed to the user, who may (after proper
validation) then insert the PLA again preceded
by an "X". The message will then be queued
for message service where the PLA is considered
for manual insertion of routing information.
6) I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types:
- PLA
- Reference Number
- AIG
- Address Group
- "X" PLA
"Either one ACTION or one INFO PLA is mandatory".
7) E̲x̲e̲m̲p̲t̲e̲d̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types:
PLA or
Reference number
The exempted addressees shall be deleted from
the specified AIG(s) by the system.
8) S̲u̲b̲j̲e̲c̲t̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲ ̲C̲o̲d̲e̲s̲ ̲(̲S̲I̲C̲)̲
Parameter(s) are (at least one) mandatory.
9) O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲
Parameter is mandatory. The "FROM" PLA shall
be entered.
10) O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
Parameter is mandatory. SCD of the originator
of message.
11) O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory. Name, rank, etc. of
the originator of message (max. 20 characters).
12) C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲,̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲(̲s̲)̲
Parameters are optional.
SCD's (staff cell designators) to which the
message shall be sent for coordination.
13) L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
Parameters are optional. SCDs addressees for
local distribution.
14) M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
Message handling instructions consisting of
a 3 letter group plus a parameter can be entered
in free format. The message handling instruction
entry string is limited to 50 characters to
allow conversion into format line 5 of ACP
127. No validation is performed.
15) I̲n̲t̲e̲r̲n̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲
Parameters are optional. Text will be incorporated
as inserted by drafter.
c) P̲r̲e̲d̲e̲f̲i̲n̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲
When a predefined message is selected the header
can be partly complete. The fields which require
user data entry shall be indicated. The lay out
and procedures will be the same as for format A.
3.2.1.2.1.1.2 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
a) Two types of message text preparation exist:
1) Entering of message text in free format
2) Entering of message text according to stored
predefined message text format information.
b) F̲r̲e̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
The text is entered by the drafter in free format,
and no validation shall be supported by the system,
except for that no line shall exceed 69 characters.
c) P̲r̲e̲d̲e̲f̲i̲n̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
When a predefined message is selected the text
part can be formatted
The text is entered by the drafter under supervision
of the system, prompting the drafter for parameters
in accordance with the predefined text format and
performing syntax validation of entered values
as far as type (numerical or alphabetic) and numbers
are concerned.
3.2.1.2.1.1.3 C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲H̲e̲a̲d̲e̲r̲ ̲a̲n̲d̲/̲o̲r̲ ̲T̲e̲x̲t̲
Editing procedures for correction of header and text
shall be supported by the system as a part of initial
message preparation (ref. CPS/230/ICD/0001).
3.2.1.2.1.1.4 A̲p̲p̲e̲n̲d̲/̲C̲o̲o̲r̲d̲i̲n̲a̲t̲e̲/̲R̲e̲l̲e̲a̲s̲e̲/̲D̲e̲f̲e̲r̲
The system will after correction has ended, ask the
user for an answer to the following questions:
- Append?
- Coordination?
- Release?
- Defer
If Append is specified then the user will have the
facility to append text of a message using Format O.
If coordination is specified the message will be sent
for coordination and the initial message preparation
procedure terminated.
If Release is specified the message will be sent to
the releasing officer requesting release and the initial
message preparation procedure terminated.
If Defer is specified the message will be deferred
and be available for subsequent editing.
3.2.1.2.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲E̲d̲i̲t̲i̲n̲g̲
a) Associated formats: C1
b) Message Editing shall be possible only from the
terminal position at which the initial message
preparation took place.
c) Message Editing shall apply to all messages under
preparation i.e. until message release.
d) Message editing shall be performed under supervision
of the system by means of interactive procedures.
e) The message which the operator wishes to edit
shall be identified to the system by means of the
item reference identity.
f) The system shall respond to a request for message
editing as follows.
1) Message available. Message editing procedure
shall be commenced.
2) Message available, but initial preparation
of message terminated by the suspend function.
The user shall be informed and the initial
message preparation commenced from the point
where it was interrupted.
3) Message not available, i.e. non existent, released,
awaiting release or not available from this
terminal position. The user shall be informed
accordingly.
g) The message editing shall consist of the following
steps (details given in CPS/ICD/0001):
1) Specification or change of local info-distribution
2) Specification of staff cells for coordination
3) Correction of header and/or text
4) Sending the message to coordination or to release
or defer it for later editing.
h) The last two steps are as specified for initial
message preparation.
i) S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲s̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
The system shall display the staff cells specified
for coordination during initial message preparation.
The operator shall then be allowed to exempt those
staff cells for which coordination shall not take
place.
3.2.1.2.1.3 A̲p̲p̲e̲n̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
a) Associated format: O
b) Append message shall apply only to messages retrievable
at the terminal position from which the append
message is requested.
c) Append message shall be performed under supervision
of the system by means of interactive procedures.
d) Append message shall enable the user to add a section
from the text of another message to message in
preparation.
e) After append message the system shall return to
the message preparation procedure from which it
was initiated.
3.2.1.2.1.4 M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
a) Asssociated format: B
b) Message coordination may be requested during initial
message preparation or message editing.
c) When message coordination is requested a copy of
the message shall be sent to the specified staff
cells within the CAMPS site. At the destination
the message shall be presented in format B. When
the second or later version of the same message,
due to subsequent requests for coordination, is
presented to a staff cell this shall be indicated
in the display by the word "REPEAT"!
d) Remarks to messages received at a terminal position
for coordination may be sent to the message drafter
via CAMPS by means of the comment procedures, directing
the message to the SCD of the originator.
3.2.1.2.2 C̲o̲m̲m̲e̲n̲t̲s̲
a) CAMPS shall support the preparation and distribution
of comments within a CAMPS site.
b) Comments may be used for internal exchange of information
or for sending answers to coordination requests.
c) The following procedures shall be supported by
the system with respect to comments.
1) New comment preparation
2) Comment editing
3) Comment presentation
3.2.1.2.2.1 N̲e̲w̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Associated format: G1
b) New comment preparation shall be performed by means
of interactive procedures.
c) New comment preparation shall involve specification
of the following parameters which except for the
text are validated with respect to syntax by the
system.
1) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory
2) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Parameter is optional
3) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲l̲e̲v̲e̲l̲
Parameter is mandatory
4) O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲
Parameter is mandatory. Staff Cell of the originator
of the comment.
5) O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory. Originators name, rank,
etc. (max. 20 characters).
6) S̲C̲D̲(̲s̲)̲
Parameter is mandatory.
Staff cell designator addressees.
7) T̲e̲x̲t̲: text in free format.
d) After specification of the parameter the system
shall support.
1) C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲s̲. Editing procedures as described
under new message preparation shall be supported.
2) S̲e̲n̲d̲/̲D̲e̲f̲e̲r̲.̲ If requested by the operator the
comment shall be sent to the designated staff
cells, otherwise the comment shall be deferred
and available for later comment editing.
3.2.1.2.2.2 C̲o̲m̲m̲e̲n̲t̲ ̲E̲d̲i̲t̲i̲n̲g̲
a) Associated format: G3
Comment editing shall be possible only from the
terminal position at which initial comment preparation
took place.
b) Comment Editing shall apply to comments under preparation,
i.e. not sent to the designated staff cells.
c) Comment Editing shall be performed under supervision
of the system by means of interactive procedures.
d) The comment to which the operator wishes to apply
the comment editing shall be identified to the
system by means of the item reference identity.
e) The system shall respond to a request for comment
editing as follows:
1) Comment available. Comment editing shall be
commenced.
2) Comment available, but new comment preparation
was terminated by the suspend function. The
user shall be informed and new comment preparation
shall be commenced from the point where it
was interrupted.
…86…1 …02… …02… …02… …02…
3) Comment not available, i.e. non existent, not
available from this terminal position. The
user shall be informed accordingly.
f) The comment editing shall support:
1) Correction procedures
2) Send/defer as for new comment preparation.
3.2.1.2.2.3 C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
a) Associated format: G2
b) When sending of a comment is requested, it shall
be presented at the destination in format G2.
3.2.1.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲
a) When requested by the drafter (via format A, C1)
the message shall be sent to the release position
to which the drafter is associated.
b) The release officer at the release position shall
decide whether the message shall be released or
not. This shall be supported by the system by means
of the message release procedure.
c) The message release procedure consists of the following
steps:
1) Presentation of message for which release is
requested
2) Request the release officer for a release decision
3) Entering of release officer's comment
d) P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
The presentation of the message shall be in accordance
with format D.
e) R̲e̲l̲e̲a̲s̲e̲ ̲D̲e̲c̲i̲s̲i̲o̲n̲
Authorization for release is given by the release
officer when he enters his personal password. The
released message shall be assigned a serial release
number together with the time of release. The message
shall then be accepted by the system for local
distribution and ACP127 Conversion.
Rejection of release may be of two types DEF or
NO, and is further detailed in the release officer's
comment.
f) R̲e̲l̲e̲a̲s̲e̲ ̲O̲f̲f̲i̲c̲e̲r̲'̲s̲ ̲C̲o̲m̲m̲e̲n̲t̲
The release officer has the option to comment on
his decision on release. If the decision for release
was DEF, this indicates that the release officer
wants the message to be resubmitted at a later
time without any changes. The release officer may
specify the time for resubmission here, as it is
the responsibility of the message drafter to resubmit
the message.
The message drafter shall be informed of the release
decision and the associated comment (if any) by
means of the notification of release procedure
(format F).
3.2.1.2.4 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
a) Local distribution means automatic distribution
by the CAMPS System of
1) Outgoing messages which have been released
2) Messages sent for coordination
3) Comments
4) Messages sent for release
b) Local distribution shall be based on Staff Cell
Designators (SCDs) entered during preparation,
except for a4) above, and shall consist of queuing
to the terminals specified in the SCD table. (Refer
section 3.2.4.1.1.3).
In case a 1) above local distribution shall additionally
be based on PLAs for local HQs specified during preparation
or at entry of complete messages. Distribution is
as for incoming messages (refer 3.2.2.3.1).
c) Messages sent for release shall be queued to the
release terminal specified in the drafters operator
profile.
d) Local distributed messages shall be presented at
their destination as specified in CPS/230/ICD/0001.
If the destination is a printer the requirements
in section 3.2.3.7.2 shall apply too.
ZEN PLAs as specified in 3.2.1.6.3 will be displayed
with ZEN in front of the PLA.
e) A message/comment, except a message sent for coordination
or release which cannot be delivered at a destined
terminal position shall be handled as described
in section 3.2.2.3.1 c) through e).
f) A message sent for coordination which cannot be
delivered or presented at a destined terminal position
shall not be queued for that terminal position.
The drafter shall be notified that the appropriate
Staff Cell was not reached.
g) A message sent for coordination is considered non-deliverable
or non-presentable when one of the conditions described
in section 3.2.2.3.1. c) respectively 3.2.2.3.1.
d) is fulfilled.
h) A message sent for release which cannot be delivered
at a release position shall not be queued. The
response text: "Release/Transmission request not
accepted - item deferred" (ref. CPS/230/ICD/0001,
App. B, msg. no. 34) is generated by the system
and displayed at the drafter's terminal.
i) A message sent for release is considered non-deliverable
when one of the conditions in 3.2.2.3.1 c) is fulfilled.
j) Messages with special handling designators shall
be treated as specified in figure 3.2.1.2.4-1.
k) Messages of type ATOMAL shall have normal local
distribution except for print which is to supervisor
designated printer.
3.2.1.3 S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The system shall assist the supervisor and supervisor
assistance in preparation of service messages.
b) Procedures which may be accessed are detailed in
ref. CPS/230/ICD/0002.
3.2.1.3.1…02…P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Service Message Preparation shall be supported
by the following procedures.
1) Initial Preparation
2) Editing
b) The supervisor/supervisor assistance shall be able
to request an ACP 127 conversion and the following
transmission for service messages prepared.
Figure 3.2.1.2.4-1…01…TREATMENT OF MESSAGES WITH SPECIAL HANDLING DESIGNATORS
3.2.1.3.1.1 I̲n̲i̲t̲i̲a̲l̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Initial preparation shall be performed under supervision
of the system by means of interactive procedures.
b) Initial preparation shall involve specification
of the following parameters, which, except for
the text parameter, shall be validated with respect
to syntax by the system.
The same parameters may be specified as listed in section
3.2.1.2.1.1.1 b and section 3.2.1.2.1.1.2 b (free format
text) except for:
- Addresses are inserted as RIs except for normal
plaindress service message
- SICs (SVC is automatically inserted)
- originator SCD/ID: There shall be no indication
of originator SCD or originator identification
- Coordination: There shall be no coordination.
- Local Distribution: There shall be no local distribution.
- Internal Handling: There shall be no internal
handling.
c) The supervisor shall specify:
1) type of message, i.e. abbreviated service message,
abbreviated or normal plaindress service message
at start of preparation.
2) if conversion shall be applied. If not the
service message shall be available for editing.
3.2.1.3.1.2 E̲d̲i̲t̲i̲n̲g̲
a) Editing shall be possible only from the terminal
position where initial preparation took place.
b) Editing shall apply to all service messages under
preparation, i.e. when no conversion has yet been
requested.
c) Editing shall be performed by means of interactive
procedures.
d) The service message to which the supervisor wishes
to apply editing shall be identified to the system
by means of the Item Reference Identity.
e) The system shall respond to a request for editing
as follows:
1) Message available. Editing shall be commenced.
2) Message not available, i.e. non existent, awaiting
conversion or converted.
f) The editing shall support
1) correction procedures
2) conversion/defer (as for initial preparation).
3.2.1.4…02…E̲n̲t̲r̲y̲ ̲o̲f̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) Entry of complete messages shall be accepted by
the system.
Complete messages may be entered as follows:
1) from Paper Tape Reader (PTR)
2) from Optical Character Reader (OCR)
b) The system shall support supervisor control of
complete message entry.
c) If a message entered via a PTR has not been properly
terminated with EOTF, a warning report shall be
forwarded to the supervisor and the message discarded.
3.2.1.4.1 E̲n̲t̲r̲y̲ ̲f̲r̲o̲m̲ ̲O̲C̲R̲
a) Messages shall be entered in a format which is
described below (b). All information necessary
for the conversion to ACP 127 format shall be available
except for the following parameters:
1) Channel designator and associated serial number
2) Release serial number and time of release
(For details on conversion refer to section 3.2.1.5).
b) F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲D̲a̲t̲a̲ ̲E̲n̲t̲e̲r̲e̲d̲ ̲f̲r̲o̲m̲ ̲O̲C̲R̲
Format A with modification to include a local distribution
line as per VDU generated messages, refer to section
3.2.1.2.4.
c) Messages entered from an OCR shall be subject to
the same validation checks as performed on messages
entered from user preparation terminals.
3.2.1.4.2 E̲n̲t̲r̲y̲ ̲f̲r̲o̲m̲ ̲N̲o̲n̲-̲d̲e̲d̲i̲c̲a̲t̲e̲d̲ ̲P̲T̲R̲
a) Outgoing messages shall be entered in full ACP
127 format with the following exception:
1) Format line 1 is missing (i.e. consist of VZCZC(CR)(CR)(LF))
and shall be inserted by CAMPS before transmission.
2) Release serial number and time of release shall
be present, but will be replaced at conversion
except for encrypted messages (For details
on conversion refer to section 3.2.1.5).
3.2.1.4.3 E̲n̲t̲r̲y̲ ̲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̲
Outgoing codress/plaindress encrypted messages will
be entered via the dedicated PTR in full ACP 127 format.
These messages will not contain format line 1, however,
the sequence "VZCZC(CR)(CR)(LF)" will be present as
a dummy line before FL2.
Incoming decrypted codress/plaindress messages for
local distribution will be entered via the dedicated
PTR in full ACP 127 format. These messages will contain
format line 1.
All messages will contain the group count prosign in
FL10 on entry to the system.
Outgoing messages and messages punched for off-line
decryption will always contain the group count in format
line 14.
3.2.1.4.4 M̲e̲s̲s̲a̲g̲e̲s̲ ̲t̲o̲ ̲S̲C̲A̲R̲S̲ ̲a̲n̲d̲ ̲A̲C̲C̲I̲S̲
Locally prepared messages to SCARS/ACCIS will be prepared
via format A and addressed by PLAs.
Locally prepared messages as well as relayed messages
will be transmitted to SCARS in ACP127 format and to
ACCIS in modified E1.
3.2.1.5…02…A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
The conversion of outgoing messages to ACP 127 format
shall be type dependent as shown in figure 3.2.1.1-1.
The different ACP 127 formats are explained in detail
in CPS/230/ICD/0003.
This ICD also contains details about outgoing message
conversion for operational messages with plain text
and service messages.
Figure 3.2.1.5-1 provides in a short form the details
of conversion for all types. Operational messages
with encrypted text are entered as complete messages
and shall except for certain checks and replacements
not be subject to conversion processing. Refer to
section 3.2.1.5.3 for details.
In case of operational messages with plain text and
service messages certain parameters for conversion
are not directly available. Refer to section 3.2.1.5.1
and 3.2.1.5.2 for details.
3.2.1.5.1…02…C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲w̲i̲t̲h̲ ̲P̲l̲a̲i̲n̲ ̲T̲e̲x̲t̲
The functional dependencies applicable at conversion
shall correspond to figure 3.2.1.5-2.
a) P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲a̲t̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
1) Parameters specified during preparation shall
be inserted directly as specified in figure
3.2.1.5-1 and CPS/230/ICD/0003.
2) Address parameters shall furthermore result
in selection of routing indicator(s), refer
to section 3.2.1.5.1b.
3) When precedence specified for action addressee(s)
is of type FLASH or IMMEDIATE and the precedence
for info addressee(s) is lower a separate transmission
shall be made for the INFO addressee(s) in
case where the INFO PLAs give rise to selection
of a separate channel to a separate destination,
i.e. either TARE, TRC/low speed TTY.
INFO PLAs are those PLAs extracted from the
user specified INFO addressees (PLAs and/or
all PLAs included in a specified AIG).
4) Operating signals entered as message handling
instructions shall be inserted in format lines
5.
5) All special handling designators in FL4 shall
be inserted as special category warnings in
FL12a.
6) The PLA in format line 7 or 8 shall not be
preceded with a RI for outgoing single addressed
messages.
7) The DE RI of format line 3 shall be selected
using the network code in the circuit table.
3.2.1.5-1
3.2.1.5-1 2 of 4
3.2.1.5-1 3 of 4
3.2.1.5-1 4 of 4
3.2.1.5-2
fig. 3.2.1.5-3
This page intentionally left blank
b) S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲s̲
1) Routing indicators shall be selected on basis
of PLA's as described in section 3.2.1.6.1
2) The applicable set of PLA's shall be derived
as follows (refer to fig. 3.2.1.5-3)
- to each Address Group is found the associated
AIG
- to each Reference Number is found the associated
PLA
- PLA's are extracted from AIG's
- EXEMPT specified PLA's shall not be included
- PLAs preceded by "ZEN" (refer to section
3.2.1.6.3) shall not be considered in the
RI selection procedure.
3) PLA's preceded by an "X" at preparation have
no routing indicators associated by the system:
After final conversion the message shall be
queued for routing indicator assignment.
c) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲l̲e̲d̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
ACP127 conversion shall further depend on supervisory
control via system tables.
1) Decision on conversion alternatives for all
messages converted at a CAMPS site is defined
in 3.2.4.1.1.3(b).
2) Decision on operating signals (format line
4) as depending on message precedence FLASH:
ZGC when no receipt wanted (refer to section
3.2.1.6).
d) H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲L̲o̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
G̲e̲n̲e̲r̲a̲l̲. Messages prepared on the system for transmission
shall be divided into "pages" of 20 lines if their
length exceed 20 counting from the "format line
5" of the ACP 127 format.
Those messages which exceed five "pages" in length
shall be divided into transmission sections.
1) R̲e̲l̲a̲t̲e̲d̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲.̲ The first page shall consist
of Format lines 1,2,3 and 4 and the succeeding
20 lines.
2) All other pages of the message shall consist
of not more than 20 lines.
3) From the second page onwards each page shall
be identified by the page number, the routing
indicator of the station of origin and the
station serial number in that order. When
the message text is transmitted in plain language
the security classification, the abbreviation
UNCLAS, or the word CLEAR shall also be included
as part of the page identification of second
and succeeding pages. Page identification
shall appear on a separate line, and shall
not be included in the line count as in 2)
above.
4) Machine functions used between pages shall
be 2 CR and 4 LF.
5) The number of pages of message text in any
transmission shall not exceed five, a page
consisting of part heading and part text shall
not count as a textual page.
6) Messages which exceed five pages of message
text shall be divided into transmission sections
as follows:
Each section shall include as first part of
the section, the full header plus format lines
12a, 12b, 12c (if applicable), followed by
the section number as a new physical line and
followed by format line 12d (if applicable)
and 12e, all in plain language.
At the last permissible line at the last permissable
page of a transmission section, the system
shall automatically separate the text and generate
additional sections as required by the length
of the text.
Each section shall be numbered, and the section
number shall be inserted in plain language
after the Exercise indicator (if used) on
line 12c. For example, when a message is divided
into two sections, the first section shall
be identified as SECTION 1 of 2, and the second
section as FINAL SECTION OF 2.
7) Each section shall bear a separate station
serial number, but the same date-time group
and filing time shall be used on all sections.
8) If paging/sectioning of a message, following
the paging/sectioning rules, will lead to a
page/section only containing format lines 13,
14, and 15 then the paging/sectioning shall
not be done and FL13, FL14, and FL15 shall
be part of the previous page/section.
e) S̲t̲o̲r̲a̲g̲e̲. Before issuing a message for the transmission
procedures (refer to section 3.2.1.6) the message
sections shall be stored. The sections shall be
stored separately.
3.2.1.5.2 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The functional dependencies applicable to conversion
shall correspond to figure 3.2.1.5-2.
Detailed conversion information is given in fig. 3.2.1.5-1.
a) P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲a̲t̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲.̲ Parameters
specified during preparation shall be inserted
directly as specified in fig. 3.2.1.5-1. The DE
RI of format line 3 of service message in plaindress
format shall be found in the same way as for operational
messages (ref. 3.2.1.5.1 a)8)).
b) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲n̲t̲r̲o̲l̲.̲ Section 3.2.1.5.1 c) shall
apply.
c) H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲L̲o̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲ The provisions of section
3.2.1.5.1 d) shall apply to standard service messages
only.
d) S̲t̲o̲r̲a̲g̲e̲.̲ The provisions of section 3.2.1.5.1 e)
shall apply.
3.2.1.5.3 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Messages entered under the provision of section 3.2.1.4
as complete, except messages from the OCR which except
for release are treated as VDU prepared messages, shall
be processed as follows:
a) Station serial number and time of release (format
line 3 and 5) shall be replaced with the time of
entry for "conversion" and the next serial No.
in a dedicated series.
b) Routing indicators of format line 2 shall be validated.
In case of a non successful validation the message
shall be queued for routing indicator assignment.
c) Channel designator and serial number shall be replaced
as part of the transmission procedures (refer to
section 3.2.1.6 below).
3.2.1.6 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
Following ACP 127 conversion as described in section
3.2.1.5 messages shall be subject to transmission procedures.
3.2.1.6.1 C̲h̲a̲n̲n̲e̲l̲ ̲S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) Where more than one output route is available,
the routing of outgoing messages shall be performed
according to routing tables associating specific
routing indicators with each output route. Separate
transmissions will be made on each output route
concerned.
b) For each transmission of an outgoing message, only
the routing indicators pertinent to that transmission
shall be present in "format line 2" on the ACP
127 format.
c) The maximum amount of routing indicators per message
shall be max. 200.
d) Where necessary separate transmissions shall be
made to include all RI's.
e) A table shall exist to indicate for each PLA selected
as in section 3.2.1.5.1.b, the RIs to be selected
in order of priority and classification. Max.
4 Routing Indicators shall exist at a given time.
The RI is organized in the PLA/RI conversion table
with the following priority:
Column 1: NICS TARE RI or SCARS RI or
ACCIS RI.
Columns 2, 3, and 4: RI related to other networks.
The first entry in the PLA/RI conversion table
has the highest priority and should be selected
if message classification allows.
If no RI fulfils classification requirements the
message shall be routed to the MSO who may then
choose to route it to the dedicated PTP or insert
CLEAR before entering the message for routing.
Each RI has an associated logical circuit and a
max. classification.
Messages with CLEAR designation shall be treated
as UNCLASSIFIED.
f) Each RI shall be associated to one external logical
circuit. If the circuit is not authorised to carry
messages of the assigned classification the next
RI in order of priority shall be selected. If
finally no circuit is found with proper classification
assignment a security report shall be generated.
No transmission shall take place for the message
for that circuit, but it shall be queued to the
message service position for RI assignment.
g) If a logical circuit is found which is authorised
but not available, the next routing indicator in
order of priority shall be selected and the associated
circuit analysed for authorization. No transmission
shall take place for the message for that circuit.
It shall be queued for message service (RI assignment
including insertion of T-instruction in FL4 of
ACP 127 format).
h) Messages with CLEAR designation shall only be entered
from Message Service Position. This will only be
done after rejection due to non availability of
approved circuit (and after consultation with the
originator).
i) As a result of Routing Indicator and circuit selection
separate messages may be transmitted via different
circuits corresponding to one prepared message.
Each of these messages shall contain all PLA's
in format lines 7,8, and 9 of format ACP 127, however,
PLA's reached via other channels (other routing
indicators) and local HQ PLAs shall for each separate
transmission be indicated by "ZEN/PLA" in format
lines 7 and 8 of ACP 127. The ZEN indication shall
not apply to messages entered via PTR and for PLAs
in AIGs.
j) To each outgoing channel shall be assigned a unique
channel designator and a security classification.
To each message shall be assigned, as the last
step before transmission, a channel serial No.
equal to the serial No. of the last transmitted
message plus one.
l) The supervisor shall have facilities for resetting
the serial number.
m) The channel designation and serial number are together
called the transmission identification.
n) Transmission identification shall be inserted in
format line 1 before transmission.
o) The supervisor shall be able to specify the channel
designator for each channel and he shall be able
to reset the sequence of channel serial number
to 001/0001. He shall be able to select whether
3 digits or 4 digits be used and whether the sequence
is reset at 24,00 hours to 001/0001 or reset only
by wrap around (i.e. 001 after 999 and 0001 after
9999). The supervisor shall also be able to update
security classification and special handling categories.
3.2.1.6.2 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲P̲r̲e̲m̲a̲t̲u̲r̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲o̲f̲
̲a̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
a) When during transmission preemption procedures
are invoked in accordance with precedence rules
the interrupted messages shall be terminated automatically
by the sequence.
b) 2 carriage returns, line feed, letter shift, ZPH,
space, ZPH, 2 carriage returns, 8 line feeds, NNNN,
12 letter shifts.
c) The CAMPS shall automatically retransmit the preempted
message.
d) Premature termination of a transmission will only
be performed by CAMPS at channels to TRC/Point-to-Point
connections, SCARS and ACCIS.
3.2.1.6.3 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲t̲h̲e̲ ̲Z̲E̲N̲ ̲P̲r̲o̲s̲i̲g̲n̲s̲
Refer to sections 3.2.1.5.1b and 3.2.1.6.1.
The ZEN prosign can be inserted in front of a PLA in
one of the following cases:
a) During preparation the user can enter ZEN in front
of a PLA.
b) During RI assignment the MSO can enter ZEN in front
of a PLA.
c) When a local PLA is specified in format A the system
will insert a ZEN in front of that PLA before transmission.
3.2.1.6.4 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲r̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲F̲L̲A̲S̲H̲ ̲R̲e̲c̲e̲i̲p̲t̲
a) For each transmission of an outgoing message with
precedence FLASH the system shall receive a receipt
message from the recipient stations in the format
of a service message as specified below. The receipt
message may be of either precedence FLASH or IMMEDIATE.
b) If the originating CAMPS does not require a receipt
message, it shall be possible for the supervisor
to direct the insertion of the operating signal
"ZGC" in the appropriate position of format line
4 through flagging whether ZGC to be inserted or
not.
c) If a receipt message is requested and it is not
received within a specified time period from the
end of an outgoing transmission of the precedence
FLASH message, a warning report shall be generated.
d) It shall be possible for the supervisor to vary
the time period involved from 2 minutes to 20 minutes
in increments of 2 minutes.
e) Format for FLASH message receipt is an abbreviated
service message of IMMEDIATE precedence with text
line containing the following sequence:
R (Space) Z (space) Station & Channel designation
of FLASH message transaction station (figure shift)
Serial Number.
3.2.1.6.5 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲C̲R̲Y̲P̲T̲O̲ ̲S̲E̲C̲U̲R̲I̲T̲Y̲
Messages of special handling type CRYPTO SECURITY shall
except when entered as complete messages from PTR be
queued to the dedicated PTP for encryption and shall
not be subject for local distribution.
3.2.1.6.6 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲f̲o̲r̲ ̲S̲e̲n̲d̲i̲n̲g̲ ̲A̲u̲t̲o̲m̲a̲t̲i̲c̲a̲l̲l̲y̲ ̲G̲e̲n̲e̲r̲a̲t̲e̲d̲
̲A̲b̲b̲r̲e̲v̲i̲a̲t̲e̲d̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲
The procedures for automatically generating/sending
abbreviated service messages are described in the ICDs
for each circuit, (CPS/ICD/004, CPS/ICD/005, CPS/ICD/006,
CPS/ICD/007).
The automatically generated ASM will be transmitted
immediately after the message currently being transmitted
(if any).
The DE RI of format line 3 for automatically generated
ASM shall be selected using the network code in the
circuit table.
The TO RI of format line 2 shall be the one specified
in the appropriate channel table.
