top - download
⟦2cb71028a⟧ Wang Wps File
Length: 8614 (0x21a6)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN73.08«
Derivation
└─⟦69f081490⟧ Bits:30006004 8" Wang WCS floppy, CR 0039A
└─ ⟦this⟧ »~ORPHAN73.08«
WangText
…1c… …1b……09……1b……0e……1b… …1a……86…1
…02…
…02…
…02…
…02…CPS/210/SYS/0001
…02…810804…02……02…
CAMPS
SYSTEM
REQUIREMENTS
…02…ISSUE
3.3…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
reated 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 terminls 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, messae 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 specifis 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 storae 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 ad 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 Operaional 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 Entr from OCR .............. 77
…02……02……02……02……02…3.2.1.4.2 Entry from PTR .............. 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 Serice
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 Selectin 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 Relate to the ZEN
Prosigns ....................
92
…02……02……02……02……02…3.2.1.6.4 Procedures Related to
FLASH Receipt ...............
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 ection 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 desribes 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 prepare 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 convrted 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 constitutedof 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
t 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.…86…1 …02…
…02… …02… …02…
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̲
Te 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 AMPS. 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 tet 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 folloing 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 n 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 eans 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 distribut
