top - download
⟦0cbb45507⟧ Wang Wps File
Length: 87442 (0x15592)
Types: Wang Wps File
Notes: CPS/SDS/010
Names: »1029A «
Derivation
└─⟦2b76602a5⟧ Bits:30006036 8" Wang WCS floppy, CR 0060A
└─ ⟦this⟧ »1029A «
WangText
…00……00……00……00……00…D…0a……00……00…D…0b…D…05…0…0f…+…09……1d…
…1c……0d……1c……05……1b……0e……1b……01……1b… …1a……08……1a……0b……1a……0e……1a…
…19……08……19……0c……19……02……19……06……18……0a……18……0b……18……00……18……06……17……0b……17……00……17……05……16……09……16……0e……16…
…15……08……15……0d……15… …15……06……14……0b……14……00……14… …14……07……13……0c……13……00……13… …12……08……12……09……12……0e……12……86…1 …02… …02… …02…
…02…CPS/SDS/010
…02…KNB/810801…02……02…
TRAFFIC HANDLING
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ..........................................
11
1.1 PURPOSE AND SCOPE..............................
11
1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES....
11
1.2.1 Applicable Documents.......................
12
1.2.2 Project References.........................
14
1.3 TERMS AND ABBREVIATIONS........................
15
1.3.1 Terms......................................
15
1.3.2 Abbreviations..............................
18
2 SUMMARY OF REQUIREMENTS............................
20
2.1 Package Description............................
20
2.2 Package Functions..............................
22
2.2.1 Main Functions.............................
22
2.2.1.1 Reception Procedures...................
23
2.2.1.2 ACP 127 Analysis.......................
23
2.2.1.3 Routing................................
24
2.2.1.4 ACP 127 Conversion.....................
25
2.2.1.5 Transmission Procedures................
25
2.2.1.6 Transmission Control Procedures........
26
2.2.2 Functional Responsibilities................
26
2.2.2.1 Initialization, Close Down and Restart.
26
2.2.2.1.1 Initialization ......................
27
2.2.2.1.2 Close Down ..........................
27
2.2.2.1.3 Restart .............................
27
2.2.2.2 Check Pointing and Recovery............
28
2.2.2.2.1 Checkpointing ......................
28
2.2.2.2.2 Recovery ...........................
28
2.2.2.3 Error Detection and Error Handling.....
29
2.2.2.4 Integrity of Operation.................
30
2.2.2.5 Data Collection........................
30
2.2.2.6 Security...............................
31
2.3 CHARACTERISTICS................................
32
2.3.1 Timing.....................................
32
2.3.1.1 Throughput Time .........................
32
2.3.1.2 Response Time ...........................
34
2.3.1.3 Priorities Imposed by Input .............
34
2.3.2 Throughput.................................
35
2.3.3 Flexibility................................
35
2.3.4 Accuracy and Validity......................
36
3 ENVIRONMENT........................................
37
3.1 EQUIPMENT......................................
37
3.2 SOFTWARE.......................................
37
3.2.1 System Software............................
37
3.2.2 Development Support Software...............
37
3.3 INTERFACES.....................................
37
3.3.1 External Interfaces........................
37
3.3.2 Package Interfaces.........................
38
3.3.2.1 Interface MDP ...........................
38
3.3.2.2 Interface TEP ...........................
38
3.3.2.3 Interface SAR ...........................
39
3.3.2.4 Interface LOG ...........................
39
3.3.2.5 Interface STP ...........................
39
3.3.2.6 Interface TMP ...........................
39
3.3.2.7 Interface SSC ...........................
40
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES.........
40
4 PACKAGE DESIGN.....................................
41
4.1 PACKAGE OVERVIEW...............................
41
4.1.1 Functional Specification...................
43
4.1.1.1 ACP127 Analysis Functions..............
43
4.1.1.2 ACP127 Conversion Functions............
46
4.1.1.3 Transport Functions....................
49
4.1.1.3.1 NICS TARE Transport .................
55
4.1.1.3.2 TRC/Point-to-Point Transport ........
57
4.1.1.3.3 SCARS/CCIS Transport ................
57
4.1.1.3.4 PTR Transport .......................
58
4.1.1.3.5 PTP Transport .......................
58
4.1.1.4 Common Functions.......................
59
4.1.2 Software Structure.........................
60
4.1.2.1 Channel and Circuit Queues.............
60
4.1.2.2 Transport Process Structure............
63
4.1.2.3 ACP127 Conversion......................
64
4.1.2.4 ACP127 Analysis........................
65
4.1.2.5 CIF Profile Assignment.................
66
4.1.3 Data Flow and Control Logic................
67
4.1.3.1 Data Flow..............................
67
4.1.3.2 Message View Flow......................
76
4.1.3.3 Semaphore Logic........................
82
4.1.3.3.1 NICS TARE, TRC/Point-to-Point .......
82
4.1.3.3.2 SCARS/CCIS Transport ................
83
4.1.3.3.3 PTR Transport .......................
84
4.1.3.3.4 PTP Transport .......................
84
4.1.4 Common Data Elements.......................
89
4.1.5 External Data Elements.....................
90
4.1.6 Interfaces.................................
93
4.1.6.1 External Interfaces....................
93
4.1.6.2 Package Interfaces.....................
93
4.1.6.2.1 Interface MDP......................
94
4.1.6.2.2 Interface TEP......................
94
4.1.6.2.3 Interface SAR......................
96
4.1.6.2.4 Interface Log......................
96
4.1.6.2.5 Interface STP......................
96
4.1.6.3 Subpackage Interfaces..................
97
4.2.1 ACP127 Analysis Subpackage.................
99
4.2.1.1 Functional Specification...............
99
4.2.1.1.1 Common Functions...................
99
4.2.1.1.2 Incoming Analysis Functions........
100
4.2.1.1.3 Complete Analysis Functions........
103
4.2.1.1.4 PTR Analysis Functions.............
103
4.2.1.2 Software Specification.................
110
4.2.1.2.1 ACP127 Analysis Module.............
110
4.2.1.2.2 Level 1 Modules....................
111
4.2.1.2.2.1 Incoming Analysis Module (2.0)
.. 111
4.2.1.2.2.2 Complete Analysis Module ........
112
4.2.1.2.2.3 PTR Analysis Module (4.0) .......
112
4.2.1.2.3 Level 2 Modules....................
113
4.2.1.2.3.1 Initiate Incoming Analysis (2.1)
Initiate Complete Analysis (3.1)
Initiate PTR Analysis (4.1) .....
113
4.2.1.2.3.2 Reception Error Handling (2.2)
Complete Error Handling (3.2)
PTR Error Handling (4.2) ........
114
4.2.1.2.3.3 E1 Analysis Control Module (2.3)
114
4.2.1.2.3.4 ACP127 Control Module (2.4) .....
115
4.2.1.2.3.5 Flash Acknowledge Module (2.5)
.. 117
4.2.1.2.3.6 Log, STP and SAR Module (2.6)
... 117
4.2.1.2.3.7 Internal Format Conversion
Module (2.7) ....................
118
4.2.1.2.3.8 Finish Incoming Analysis (2.8)
Finish Complete Analysis (3.3)
Finish PTR Analysis (4.3) .......
119
4.2.1.2.4 Level 3 Modules .....................
119
4.2.1.2.4.1 Message Type Determination
Module ..........................
119
4.2.1.2.4.2 Relaying Module (2.4.2.3) .......
120
4.2.1.2.4.3 Pilot Detect Module (2.4.2.2)
... 120
4.2.1.3 Data Flow and Control Logic............
122
4.2.1.4 Subpackage Data........................
159
4.2.1.4.1 Analysis Guide Tables..............
159
4.2.1.4.2 Analysis Buffer....................
166
4.2.1.4.3 Error List.........................
166
4.2.1.4.4 RI-List............................
167
4.2.1.4.5 HQ/SIC List........................
167
4.2.1.4.6 PLA List...........................
168
4.2.1.4.7 Operating Signals List.............
169
4.2.1.5 Interfaces.............................
169
4.2.1.5.1 Application Interface..............
171
4.2.1.5.1.1 Interface MDP AAS to MDP ........
171
4.2.1.5.1.2 Interface TEP AAS to TEP ........
171
4.2.1.5.1.3 Interface TRS AAS to TRS ........
172
4.2.1.5.1.4 Interface ACS AAS to ACS ........
173
4.2.1.5.1.5 Interface Log ...................
174
4.2.1.5.1.6 Interface STP ...................
174
4.2.1.5.1.7 Interface SAR ...................
174
4.2.2 ACP127 Conversion Subpackage...............
175
4.2.2.1 Functional Specification...............
175
4.2.2.1.1 Routing Functions..................
175
4.2.2.1.2 ACP127 Formatting Functions........
178
4.2.2.1.3 Traffic Separation Functions.......
179
4.2.2.2 Software Specification.................
185
4.2.2.2.1 ACP127 Conversion Module...........
185
4.2.2.2.2 Routing Module.....................
186
4.2.2.2.2.1 Rerouting Module (2.1) ..........
187
4.2.2.2.2.2 E1 Routing (2.2) ................
187
4.2.2.2.2.3 Completed Routing Module (2.3)
.. 187
4.2.2.2.2.4 Selective Routing Module (2.4)
.. 188
4.2.2.2.3 ACP127 Formatting Module...........
188
4.2.2.2.4 Section Separation Module..........
189
4.2.2.2.5 Route Separation Module............
190
4.2.2.3 Data Flow and Control Logic............
192
4.2.2.4 Subpackage Data........................
221
4.2.2.4.1 Routing Lists......................
221
4.2.2.4.2 Conversion Buffers.................
223
4.2.2.4.3 Conversion Lists...................
223
4.2.2.5 Interfaces.............................
225
4.2.2.5.1 Application Interfaces.............
225
4.2.2.5.1.1 Interface MDP ...................
227
4.2.2.5.1.2 Interface TEP ...................
227
4.2.2.5.1.3 Interface TRS ...................
228
4.2.2.5.1.4 Interface AAS ...................
228
4.2.3 Incoming Transport Subpackage..............
229
4.2.3.1 Functional Specification...............
229
4.2.3.1.1 Incoming Transport, TRC,
Point-to-Point.....................
229
4.2.3.1.1.1 Initial Transport..............
230
4.2.3.1.1.2 Error Control..................
230
4.2.3.1.1.3 Message Characteristics........
233
4.2.3.1.1.4 Message Division...............
235
4.2.3.1.2 Incoming Transport, NICS TARE......
236
4.2.3.1.3 Incoming Transport, SCARS/CCIS.....
236
4.2.3.1.3.1 Error Control..................
236
4.2.3.1.3.2 Message Characteristics........
237
4.2.3.1.3.3 Message Division...............
238
4.2.3.1.4 Incoming Transport, PTR............
239
4.2.3.1.4.1 Error Control..................
239
4.2.3.1.4.2 Message Division...............
239
4.2.3.1.5 MSO Transport......................
240
4.2.3.2 Software Structure.....................
247
4.2.3.2.1 Incoming Transport Module..........
247
4.2.3.2.2 Initial Transport Module...........
248
4.2.3.2.3 Error Control Module...............
248
4.2.3.2.4 Message Characteristics Module.....
249
4.2.3.2.5 Message Division Module............
249
4.2.3.2.6 Other Modules......................
250
4.2.3.3 Data Flow and Control Logic............
250
4.2.3.4 Subpackage Data........................
257
4.2.3.4.1 Transport Buffers..................
257
4.2.3.4.2 Pointer Buffer.....................
257
4.2.3.5 Interface Incoming Transport...........
257
4.2.3.5.1 Interface OTS......................
258
4.2.3.5.2 Interface TCS......................
258
4.2.3.5.3 Interface AAS......................
258
4.2.3.5.4 Interface TEP......................
259
4.2.3.5.5 Interface LOG......................
259
4.2.4 Transport Control Subpackage...............
261
4.2.4.1 Functional Specification...............
261
4.2.4.1.1 Transport Control, TRC,
Point-to-Point.....................
261
4.2.4.1.1.1 Timeout Control................
262
4.2.4.1.1.2 Command Control................
263
4.2.4.1.2 Transport Control, NICS TARE.......
267
4.2.4.1.2.1 Timeout Control................
267
4.2.4.1.2.2 Command Control................
268
4.2.4.1.3 Transport Control, SCARS/CCIS......
268
4.2.4.1.3.1 Timeout Control................
268
4.2.4.1.3.2 Command Control................
269
4.2.4.1.4 Transport Control, PTR.............
269
4.2.4.1.4.1 Command Control................
269
4.2.4.1.5 Transport Control, PTP ............
270
4.2.4.1.5.1 Command Control................
270
4.2.4.2 Software Specification.................
277
4.2.4.2.1 Transport Control Module...........
277
4.2.4.2.2 Timeout Control Module.............
278
4.2.4.2.3 Command Control Module.............
279
4.2.4.2.4 Other Modules......................
280
4.2.4.3 Data Flow and Control Logic............
283
4.2.4.4 Subpackage Data........................
295
4.2.4.4.1 Transaction Acknowledgement
Buffer.............................
295
4.2.4.5 Interface Transport Control............
295
4.2.4.5.1 Interface OTS......................
296
4.2.4.5.2 Interface ITS......................
296
4.2.4.5.3 Interface AAS......................
296
4.2.4.5.4 Interface ACS......................
297
4.2.4.5.5 Interface TEP......................
297
4.2.4.5.6 Interface SSC......................
297
4.2.4.5.7 Interface LOG......................
298
4.2.4.5.8 Interface STP......................
298
4.2.5 Outgoing Transport Subpackage..............
300
4.2.5.1 Functional Specification...............
300
4.2.5.1.1 Outgoing Transport, TRC,
Point-to-Point.....................
300
4.2.5.1.1.1 Message Assembly...............
301
4.2.5.1.1.2 Message Formatting.............
302
4.2.5.1.1.3 Final Transport................
303
4.2.5.1.1.4 Channel Close Down.............
305
4.2.5.1.2 Outgoing Transport, NICS TARE......
306
4.2.5.1.2.1 Final Transport................
306
4.2.5.1.3 Outgoing Transport, SCARS/CCIS.....
306
4.2.5.1.3.1 Message Assembly...............
307
4.2.5.1.3.2 Final Transport................
307
4.2.5.1.4 Outgoing Transport, PTR............
308
4.2.5.1.4.1 Message Assembly...............
308
4.2.5.1.4.2 Message Formatting.............
309
4.2.5.1.4.3 Final Transport................
309
4.2.5.2 Software Structure.....................
315
4.2.5.2.1 Outgoing Transport Module..........
315
4.2.5.2.2 Message Assembly Module............
316
4.2.5.2.3 Message Formatting Module..........
317
4.2.5.2.4 Final Transport Module.............
317
4.2.5.2.5 Channel Close Down Module..........
318
4.2.5.2.6 Other Modules......................
318
4.2.5.3 Data Flow and Control Logic............
318
4.2.5.4 Subpackage Data........................
325
4.2.5.4.1 Transport Buffers..................
325
4.2.5.4.2 Page Buffer........................
325
4.2.5.4.3 Pointer Buffer.....................
325
4.2.5.5 Interface Outgoing Transport...........
326
4.2.5.5.1 Interface ITS......................
326
4.2.5.5.2 Interface TCS......................
326
4.2.5.5.3 Interface AAS......................
327
4.2.5.5.4 Interface ACS......................
327
4.2.5.5.5 Interface TEP......................
327
4.2.5.5.6 Interface SAR......................
328
4.3 MEMORY LAYOUT..................................
330
4.3.1 Analysis Process...........................
331
4.3.2 Conversion Process.........................
332
4.3.3 Transport Process NICS TARE................
333
4.3.4 Transport Process TRC/Point-to-Point.......
334
4.3.5 Transport Process SCARS/CCIS...............
335
4.3.6 Transport Process PTP......................
336
4.3.7 Transport Process PTR......................
337
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
The package specification for the Traffic Handling
Package (CPS/SDS/010) is written to fulfil the following
objectives:
a) To provide detailed definition of the package functions
and software architecture.
b) To provide user operational and development personnel
details of the ongoing analysis.
c) To define in detail the interfaces with other packages
and to describe their facilities.
The Traffic Handling Package provides the functions
for transport, ACP127-analysis, Routing and ACP127-conversion
of messages.
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲d̲o̲c̲u̲m̲e̲n̲t̲s̲
The following documents are applicable to the Traffic
Handling Package Design Specification.
Contract Document
Contract No. CE 80-9009-INF
CAMPS System Requirements
CPS/210/SYS/0001
User Procedure,
doc. no. CPS/230/ICD/0001
Supervisor Commands and Procedures
CPS/230/ICD/0002
ACP127 NATO Supp. 3 Procedures
CPS/230/ICD/0003
NICS/TARE
CPS/ICD/004
SCARS II
CPS/ICD/005
ACE CCIS
CPS/ICD/006
TRC, Point-to-Point Connection
CPS/ICD/007
CAMPS System Design Specification,
doc. no. CPS/SDS/001.
CAMPS Data Base Design Document,
doc. no. CPS/DBD/001
CAMPS Software Interface Control Document,
doc. no. CPS/ICD/009
Camps System Functions
CPS/SDS/002
Message Management
CPS/SDS/003
System Status and Control
CPS/SDS/004
Table Management
CPS/SDS/005
Input / Output Control
CPS/SDS/006
Storage and Retrieval
CPS/SDS/007
Statistics
CPS/SDS/008
Logging
CPS/SDS/009
Message Distribution Package
CPS/SDS/011
Terminal Package
CPS/SDS/012
VDU Supervisor Package
CPS/SDS/023
Supervisor Printer Package
CPS/SDS/024
VDU MDCO Package
CPS/SDS/025
VDU MSO Package
CPS/SDS/026
VDU User Package
CPS/SDS/027
OCR Package
CPS/SDS/028
Printer Package
CPS/SDS/029
1.2.2 P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
The following documents are listed for reference purposes
only. The listing does not constitute the contents
of the documents as Systen Requirements but is intended
to serve the Contractor in providing supplementary
information in cases of interpretation of the requirements
specifically stated in System Requirements Specification:
ACP131, Jul. 74
ACP117, SEPT. 1977, ACP117 Supp. 16. Dec. 79
ACP121, Supp. 17. Jan. 1970, 121E Jul. 1970
ACP100, NATO SUPP, 1E May 1978
ACP127, NATO SUPP. 3 May 1973, 127 (E) OCT 74
NASIS-APP.3 JAN 1978
ADatP-3 JAN 1975
1.3 I̲T̲E̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 T̲e̲r̲m̲s̲
Channel designator Identification of an external
channel.
Checkpoint Point from which restart/recovery
can take place.
Circuit CAMPS to node connection
for the appropriate Network.
A circuit may consist of
one or more channels.
Close-down Action taken to bring processing
within the system or a part
thereof to a stop - can be
either an ordered sequence
of steps or an abrupt termination.
External Channel A channel in a telegraph
circuit or non telegraph
circuit.
Initialization The definition in the CPS/SDS/001
and subsequent documents
is described as follows:
Brings the system from cold
or dead start into operational
use. No recovery actions
are included.
Message Distribution Denotes the total group of
Control Function commands/procedures which
may be performed from a VDU
with Message Distribution
Control capability.
Message Service Denotes the total group of
Function commands/procedures which
may be performed from a VDU
with Message Service capability
Message View A subset of fields within
a message.
Non Telegraph CCIS and SCARS
Circuit
Plain Language The PLA representing a
Address Headquarter
Process Execution of a specific program
operating on a specific set
of data.The active components
of the system to which security
and process control as well
as resource management is
applied.
Queue Process communication tool
within CSF.
Queue Element The elements which can be
in a queue.
Queue Monitor The part of CSF supplying
Queue facilities.
Restart Reestablishes the dynamic
behaviour of the system based
upon recovered data.
Recovery Reestablishes continuity
in memory and file contents.
Sub queue Part of a Main Queue
Supervisor Person located at supervisor
terminals in CAMPS central
equipment room
Supervisor's Person with responsibility
for
Assistant special Message Service
Stand-alone device Medium speed teleprinter,
low speed teleprinter (PTP,PTR,
ROP) OCR, PTR, and PTP.
Start up Includes all aspects of initialization,
recovery and restart.
Switchover Relates to a dualized configuration
containing an active and
a stand-by device into active
state and the other active
device off-line.
System Parameter A simple variable, holding
part of the system state,
and controlled by TMP.
Telegraph circuit NICS TARE, Point-to-Point
and TRC.
Terminal VDU, Medium Speed Teleprinter,
Low Speed Teleprinter, Line
Printer, PTP/PTR and OCR.
Terminal Position VDU and associated (shared)
ROP.
User a) Person with responsibility
for input and output
of messages.
b) Person located at the
user terminals in the
staff cells.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
AAS ACP127 Analysis Subpackage
ACP127 ALLIED Communication Procedures No. 127
ACS ACP127 Conversion Subpackage
AIG Address Indicator Group
ANQ Analysis Queue
ASM Abbreviated Service Message
CAMPS Computer Aided Message Processing System
CCQ Channel Command Queue
CCIS Command & Control Information System
CIF CAMPS Information Field
CIQ Circuit Queue
COQ Conversion Queue
CPS CAMPS
CSF CAMPS System Functions
CTS Cosmic Top Secret
DTG Data Time Group
EOLF End of Line Feed
EOPF End of Page Function
EOTF End of Transmission Function
FIFO First In, First Out
FL Format Line
HQ Headquarters
ICD Interface Control Document
IOC Input/Output Control Package
ITS Incoming Transport Subpackage
LOG Log and Accountability Package
MCQ MDCO Queue
MDCO Message Distribution Control
MDP Message Distribution Package
MSO Message Service Operator
MSQ Message Service Queue
NA Not Applicable
NICS Nato Integrated Communication System
OTS Outgoing Transport Subpackage
PLA Plain Language Address
PLA# Plain Language Address Reference Number
PTP Paper Tape Puncher
PTR Paper Tape Reader
P-to-P Point-to-Point
QEL Queue Element
SAR Storage and Retrieval
SCARS Status Control and Reporting System
SCD Staff Cell Designator
SDS System Design Specification
SFM Storage and File Management Package
SIC Subject Indicator Code
SOTF Start of Transmission Function
SRS System Requirements Specification
SSC System Status and Control
SSN Station Serial Number
STP Statistic Package
SVC Service Message
TARE Telegraph Automatic Relay Equipment
TCS Transport Control Subpackage
TD Terminal Designator
TEP Terminal Package
THP Traffic Handling Package
TI Transmission Identification
TMP Table Management Package
TOC Time of Occurrence
TRS Transport Subpackage
TSN Transmission Serial Number
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The Traffic Handling Package provides the functions
for Transport, ACP127-analysis, Routing and ACP127
-conversion of messages.
Incoming messages are received via external channels
(NICS TARE, TRC/Point-to-Point, SCARS and CCIS) and
transported to analysis for subsequent internal distribution.
Outgoing messages are received from other Packages
for routing, conversion and transport to transmission
via above mentioned external channels.
The functions for handling of complete messages related
to PTR/PTP are also provided within this Package.
The Interfaces of the Traffic Handling Package are
as depicted in figure 2.1-1. The chart illustrates
the environment of this package and inter-relationships
between external/internal interfaces.
FIGURE 2.1-1…01…TRAFFIC HANDLING PACKAGE
a) E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
NICS TARE
TRC/Point-to-Point
SCARS
CCIS
PTR
PTP
Low speed Teleprinters operating as PTR or PTP.
b) I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Message Distribution Package (MDP)
Terminal Package (TEP)
Log Package (LOG)
Statistics Package (STP)
Storage and Retrieval (SAR)
Table Management (TMP)
CAMPS System Functions (CSF)
Storage and File Management (SFM)
Input/Output Control (IOC)
System Status and Control (SSC)
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
The functions performed by this package will in the
following two sections (2.2.1 and 2.2.2) be described
in the main functions under normal operation and the
more special functions performed under more specific
circumstances.
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The main functions performed during normal operation
are:
a) Reception Procedures
b) ACP127-analysis
c) Routing
d) ACP127-conversion
e) Transmission Procedures
f) Transmission Control Procedures
The terms used under a, e and f are corresponding to
- Incoming Transport (a)
- Outgoing Transport (e)
- Transport Control (f)
2.2.1.1 R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions associated to Reception Procedures are:
- Assembling of format-lines into messages in ACP127-format
or SCARS/CCIS E1-format
- Channel Discontinuity Procedures
- Tolerance Control for detection of garble characteristics.
The received messages are considered as incoming from
the external networks NICS TARE, TRC, Point-to-points
and the external systems SCARS and CCIS.
Under reception procedures are also considered input
via the dedicated PTR or Low Speed Teleprinters operating
like PTR's. These messages are entered into complete
ACP127-format and mainly considered as outgoing messages.
The messages described are always directed for ACP127-analysis.
2.2.1.2 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
The functions of ACP127-analysis are:
- Handling of errors detected during Reception Procedures
involving a message.
- Format-Line detect and control
- Message Type Determination
- Relaying
- ASM-Handling
- Handling of messages received in SCARS/CCIS E1-format
- Flash acknowledge
- Consistency Control
- Internal Format Conversion
After ACP127-analysis a message might be directed to
a message service position for:
- Garble Correction
- Pilot Detect
- Relay Assistance
Otherwise the message will be directed to its proper
destinations into CAMPS according to the message type.
2.2.1.3 R̲o̲u̲t̲i̲n̲g̲
The functions of routing are:
- Select of Routing Indicators related to PLA's or
AIG's (entered during Message Prepare) in accordance
with message classification.
- Circuit allocation in accordance with channel availability
and classification on basis of related Routing
Indicator.
- Message Service Invocation for RI-assignment in
case above described functions fail.
- Automatic release of complete entered messages.
During Routing the PTP will be selected as "circuit"
for plaindress messages of type Crypto Security and
in accordance with MSO-decision where no RI with proper
classification can be found.
Local PLA's will also be detected.
2.2.1.4 A̲C̲P̲1̲2̲7̲-̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
The messages received for ACP127-conversion are messages
that have been routed.
The functions of ACP127-conversion are:
- Formattting of FL2 and FL3 of complete entered
messsages.
- Formatting of Supervisor prepared Service Messages
- Conversion and formatting of user prepared messages
into complete ACP127-format.
- Separation into sections if applicable for that
message
- Preparation of separate transmissions in case multiple
routes or limit exceeded on RI's.
- Insert of ZEN in front of PLA's where multiple
routes are applicable.
The messages are after conversion forwarded to transmission
upon a channel indicated via the circuit selected under
Routing. A message containing Local PLA's will, however,
be directed for local distribution
2.2.1.5 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of Transmission Procedures are:
- Formatting of FL1
- Formatting of Pilots upon automatic or Supervisor
intiated retransmissions (reruns)
- Preemption for transmission of flash message where
applicable.
- Delivery of format-lines for transmission including
insert of formal parameters.
To the Transmission Procedures are also considered
the functions for punch on a PTP; the first two functions
described are then a bit different, but still relevant.
A transmitted message will after successful transmission
be taken care of by the Transmission Control Procedures,
if the message shall be acknowledged.
2.2.1.6 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The functions of the Transmission Control are:
- Automatically Generation of ASMs of the type channel
continuity, channel number reset etc. upon timer-event.
- Time-out control and initialization of retransmissions
or supervisor reports upon that event.
- Generation of flash acknowledge ASM, Identical
Character ASM etc. upon request via a command.
- Initiate channel open and close (via command) by
generation of an ASM or at receipt of such ASM.
2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
The more special functional responsibilities provided
by the THP, will in the following sections be specified.
2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
During initialization of THP the following functions
will be performed:
- Initialize THP memory
- Reset Timer Table
If SSC in the initialization parameters for the channel
has specified, that the channel shall be opened the
following functions will be performed
- Set incoming Channel open
- Send Incoming Channel opening ASM
2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
A Close down and an ordered switchover will be equally
handled by THP. The following functions will be performed
for each channel:
- If a message is being transmitted, it will be preempted
- Set incoming and outgoing channel closed
- Send incoming channel close ASM
- Report to SSC that the channel is closed.
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
During a Restart THP will perform the initialization
described in section 2.2.2.1.1 and the Recovery procedure
in section 2.2.2.2 if applicable.
2.2.2.2 C̲h̲e̲c̲k̲-̲P̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
2.2.2.2.1 C̲h̲e̲c̲k̲-̲P̲o̲i̲n̲t̲i̲n̲g̲
THP will perform the following check-pointing:
a) Incoming Message
After reception of a message it will be disk check-pointed.
When the message has passed the ACP127-analysis,
it will be standby check-pointed.
b) Outgoing Message
After ACP127 conversion, the message will be standby
check-pointed. When the message has been transmitted
and acknowledge received (if required) the message
will be disk check-pointed.
2.2.2.2.2 R̲e̲c̲o̲v̲e̲r̲y̲
Two types of Recovery exists for THP. One Recovery
function after start-up based upon stand-by checkpoints,
and one Recovery function after start-up based upon
disk checkpoints.
a) Standby Checkpoints.
The first message retransmitted on each external
channel will be preceded by a suspected duplicate
Pilot.
b) Disk Checkpoints.
All messages marked for recovery, will be assigned
a suspected duplicate Pilot before transmission.
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
THP will provide the following error handling:
a) Program errors.
The error will be reported to SSC and the processing
stopped.
b) Data error.
The error will be analyzed; depending upon the
result, the processing will either be stopped or
continued. If the processing continues, the error
will be forwarded to a special Data Error Queue
served by SSC; by "continue" is meant continue
with the next message.
SSC will forward the error report to printout at
the operator position. This report might result
in a reprogramming of the invalid module that caused
the error. The message itself had been dismantled
and thus no more available in the erroneous version;
if a previous error-free version of the message
is available, this can be re-entered.
The Data errors associated to garble detect during
reception procedures and ACP127-analysis is not
included in the description above, because that
type of error handling is considered part of the
normal flow.
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
For an incoming Message, THP will validate all Format
lines and adjust acceptable deviations of an ACP127
- or SCARS/CCIS E1 - formatted message in order to
ensure the integrity of future operations.
For user prepared outgoing messages all data are assumed
having been validated during preparation.
For complete messages entered from a PTR, and service
messages entered by the Supervisor certain transactions
will be validated. (e.g. routing indicators)
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
The following Data Collection will be provided by THP
- Collection of Statistics
- Collection of Retrieval keys
- Collection of Log information
- Reports to Supervisor
THP will collect statistics on the following objects:
- Incoming message
- Invalid incoming message
- Outgoing message
- Channel open/close
THP will collect Retrieval keys on the following objects:
Incoming message in ACP127 format
Incoming Message in E1 format
THP will collect log information on the following objects
Incoming message
Invalid incoming message
Outgoing message
Channel discontinuity
PTP
THP will generate the following Supervisor Reports:
a) Security Reports:
- Circuit classification too low upon circuit
XX
b) Warning Reports:
- No available channels upon circuit XX
c) Channel Reports:
- Discontinuity in TSN of incoming message
- Missing TSN of incoming message
- Halted message condition
- A message has been prematurely terminated
- 100 characters have been received on a channel
after EOTF but without detection of VZXZC
- Oversized incoming message
- More than 140 identical consecutive characters
except for text part in data message.
- Time out on flash receipt
- Outgoing channel opening/closing
- Incoming test message garbled
- Selfaddressed channel check time out
- Outgoing channel test not successful
- No channel number reset ASM received
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
When an incoming message is received on a circuit it
will automatically be assigned an access classification
(Queue Profile) equal to the circuit classification.
THP will during the analysis of the message identify
the message classification, and change the access attributes
in accordance with the classification of the message
(if different).
For an outgoing message the RIs are selected in accordance
with the message classifications; before forwarding
the message to transmission, the classification of
the circuit will be compared with the messsage classification.
If no RI and circuit with proper classification exists,
the message will either be automatically punched or
sent to an MSO position for re-assignment with a notification.
Messages having been "cleared" will as outgoing be
considered unclassified, and as incoming confidential.
The considered classifications will be the ones used
during the processing of the message in accordance
with access control through CAMPS; the originally assigned
classification will remain unchanged. THP will in accordance
with this procedure change the classification attributes.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
2.3.1.1 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲ ̲T̲i̲m̲e̲
The throughput time is for an incoming message from
the time where EOTF is detected until the time where
the message is delivered to either MDP, TEP or punched
at a PTP. The throughput time is for an outgoing message
from the time where the message is queued to ACP127-conversion
until the time for start of transmission.
Through-put time for an incoming plaindress message
in average figures:
CPU access time 40 ms
Number of Monitor calls to CSF: 2 read access
5 write access
Number of Monitor call to TMP: 3
(Where the information is stored
on disk.)
Throughput time for an outgoing
Plaindress message
CPU access time: 40 ms
Number of Monitor calls to CSF: 3 read access
6 write access
Number of Monitor calls to TMP: 14
Where the information is stored
on disk
2.3.1.2 R̲e̲s̲p̲o̲n̲s̲e̲ ̲T̲i̲m̲e̲
Response time for THP is only applicable for messages
returned after MSO assistance. The MSO will after finished
analysis or conversion receive a response from THP.
Response time for the incoming MSO
CPU access time: 20 ms
Number of monitor calls to CSF: 1 read access
1 write access
Number of monitor calls to TMP: 3
(Where the information is
stored on disk
Response time for the outgoing MSO
CPU access time: 20 ms
Number of monitor calls to CSF: 2 read access
3 write access
Number of monitor calls to TMP: 14
Where the information is stored
on disk.
2.3.1.3 P̲r̲i̲o̲r̲i̲t̲i̲e̲s̲ ̲i̲m̲p̲o̲s̲e̲d̲ ̲b̲y̲ ̲I̲n̲p̲u̲t̲
The THP will process incoming messages in the sequence
of arrival independent of the message precedence, except
for precedence flash.
Outgoing messages will be processed after the same
principles during conversion, but be transmitted by
precedence.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The THP shall support the following throughput (in
busy minute, busy hour, 24 hour period)
30,530…0e…x)…0f…,3000 Incoming messages for analysis
6,250…0e…xx)…0f…,900 Outgoing messages for conversion
x) incl. 15 comments but not 150 VDU-pages
xx) incl. VDU-pages and 15 comments
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
In general the software structure of THP has been built
up after structured methods, which in itself makes
the package flexible to maintain and makes it easy
to incorporate new software.
However, the structure of the ACP127-analysis shall
be emphazised. The logic related to that processing
is of very complex nature, where future changes to
requirements have been foreseen by developing an analysis
guide table; this table can be maintained off-line.
The ACP127-conversion software can be expanded to convert
any message format.
The transport software has been structured in a manner
where only the top level software shall be changed
in order to create a new transport process type.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲ ̲a̲n̲d̲ ̲V̲a̲l̲i̲d̲i̲t̲y̲
THP has no requirements to accuracy for incoming messages.
Any piece of data will be accepted; should a piece
of data, however, turn out not to be one of the acceptable
formatted message types, it is the responsibility of
THP to reject such data (e.g. garble correction).
Messages sent to ACP127-conversion as outgoing from
a release position has to be accurate; no check for
validity will be performed for such messages because
they are expected to be proper validated by TEP before
the release. Abbreviated and normal service messages
entered from a supervisor position will be accepted
with certain erroneous data-elements for ACP127-conversion
(e.g. routing indicators)
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The system software used by this package is the software
included in the following packages:
- SFM
- CSF
- IOC
- SSC
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The software used for development of this package is
the software supported by the Support Software Package.
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Traffic Handling package interfaces via IOC the
following externals:
a) N̲I̲C̲S̲ ̲T̲A̲R̲E̲
Ref. CPS/230/ICD/0004
b) S̲C̲A̲R̲S̲
Ref. CPS/230/ICD/0005
c) C̲C̲I̲S̲
Ref. CPS/230/ICD/0006
d) T̲R̲C̲/̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
Ref. CPS/230/ICD/0007
e) P̲T̲R̲
f) P̲T̲P̲
g) L̲o̲w̲ ̲S̲p̲e̲e̲d̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
In the following the package interfaces with other
application packages and SSC will be identified (except
system-interfaces to SFM, CSF and IOC)
Ref. figure 2.1.1 for overview.
3.3.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲
- Incoming messages for local distribution
- Outgoing messages for local distribution.
3.3.2.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
a) T̲E̲P̲ ̲t̲o̲ ̲T̲H̲P̲
- Outgoing released messages for routing and
conversion
- Supervisor prepared service messages for conversion.
- Supervisor initiated rerun.
- Supervisor initiated channel control
- Comments and VDU-pages for distribution to
SCARS/CCIS
- Reenterings from message service
- Supervisor initiated readdressal
b) T̲H̲P̲ ̲t̲o̲ ̲T̲E̲P̲
- Incoming service messages to be printed at
a supervisor position.
- Incoming messages from SCARS/CCIS to be presented
at a terminal position
- Reports to be printed at a Supervisor position
- Message service invocation for:
Garble Correction
Pilot Detect
Relay Assistance
RI-assignment
Too low TSN.
3.3.2.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲A̲R̲
Delivery of retrieval-keys associated to incoming and
outgoing messages before conversion to internal format
respectively after conversion to external format.
3.3.2.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲O̲G̲
- Incoming message logs
- Outgoing message logs
- Channel Discontinuity log
3.3.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲T̲P̲
- Statistics incoming message
- Statistics outgoing message
- Statistics channel availability
3.3.2.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲M̲P̲
The following parameters and tables controlled by TMP
are used by this package:
- AIG-table
- PLA-tables
- RI-tables
- Circuit table
- Channel Profiles
- ACP127 parameters
- Channel Sequence Numbers
3.3.2.7 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲S̲C̲
SSC interfaces THP for close-down and start-up of each
channel. The modes of start-up or close-down can differ
upon the situation (switch-over, partly close-down,
total close-down etc.)
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
The functions maintained by other packages are the
functions related to the operating system.
a) C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲S̲C̲F̲)̲
- Checkpointing
- Control of access rights related to queues
- Timer functions
b) 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̲)̲
- Access and access control to files (messages)
Automatic delete of CTS and atomal messages.
c) I̲n̲p̲u̲t̲/̲O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲I̲O̲C̲)̲
- Access to external channels and devices
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
In overview the Traffic Handling Package consists of
3 main areas with completely different functional capabilities:
- ACP127 analysis
- ACP127 conversion
- Transport
The transport functions consist of 3 subjunctions:
- Outgoing Transport
- Transport Control
- Incoming Transport
As shown in figure 4.1-1 the Traffic Handling Package
has been separated into the following subpackages:
1) ACP127 Analysis Subpackage
2) ACP127 Conversion Subpackage
3) Incoming Transport Subpackage
4) Transport Control Subpackage
5) Outgoing Transport Subpackage
Figure 4.1-1 also illustrates how these subpackages
relate to processes and coroutines.
FIGURE 4.1-1…01…PACKAGE OVERVIEW
4.1.1 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
In the following the functions associated to the groups
specified in package overview, will be identified.
- ACP127 Analysis Functions
- ACP127 Conversion Functions
- Transport Functions
The Transport Functions will be described separately
for:
- NICS TARE Transports
- TRC/Point-to-point Transports
- SCARS/CCIS Transports
- PTR Transport
- PTP Transport
At last the common functions identified between the
subpackages will be specified.
4.1.1.1 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The main functions associated to ACP127-analysis are
as depicted in figure 4.1.1.1-1.
Messages to be analysed are received as:
1) Incoming messages via NICS TARE, TRC/Point-to-point
or SCARS/CCIS.
2) Complete outgoing messages via low speed teleprinters
(operating as PTR's)
3) Complete outgoing or incoming messages entered
via the dedicated PTR.
The above described types received for analysis, forms
3 analysis types with individual and common functions
as well.
A separate description of individual and common functions
between the analysis-types will be specified in section
4.2.1.
In general the function of ACP127 analysis are:
a) Initiate the analysis corresponding to the type
(incoming, complete or PTR analysis)
- set up analysis guide table
- determine message type.
b) Error Handling
- errors during transport
- unknown message type
c) Format line detection and control of incoming messages
received into SCARS/CCIS E1 format.
- Garble and E1-pilot detect
- Handling of Comments, VDU pages, messages for
coordination, messages for release and released
messages.
d) Format line detection and control of messages in
ACP127 format plus messages in SCARS/CCIS E1 format
from FL5.
- Garble, Pilot, readdressal and relay detect.
- Relaying and handling of incoming ASM's.
e) Flash acknowledge procedures for incoming messages.
f) Internal format conversion, e.g. conversion to
E1-format for incoming messages.
g) Log, statistics and retrieval keys for incoming
messages.
h) Determine to where the message shall be directed
after analysis.
FIGURE 4.1.1.1-1…01…FUNCTIONAL BREAK-DOWN…01…ACP127-ANALYSIS
4.1.1.2 A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The main functions associated to the ACP127-conversion
are as depicted in figure 4.1.1.1-2.
a) R̲o̲u̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲c̲i̲r̲c̲u̲i̲t̲ ̲a̲l̲l̲o̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲o̲u̲t̲g̲o̲i̲n̲g̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
1) Circuit allocation of previously converted
messages.
2) Circuit allocation of comments and VDU-pages
forwarded to conversion in complete SCARS/CCIS
E1-format.
3) Circuit allocation based upon RIs FL2 of complete
entered messages.
4) RI assignment and circuit allocation of messages
entered without FL 2.
5) Message Service Invocation for RI assignment.
6) Automatic release of complete entered messages.
b) A̲C̲P̲1̲2̲7̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ of Format Lines 3, 4 and 5 (+
FL 10 of complete entered encrypted messages.
1) Formatting supervisor prepared ASM
2) Formatting supervisor prepared Service Message.
3) Formatting of new FL3 of messages entered in
complete ACP127-format.
4) Formatting FL 3 - 5 of user prepared Plaindress
and Data Messages
5) Formatting FL 3 - 5 of Plaindress messages
received from SCARS/CCIS in E1-format as released.
c) T̲r̲a̲f̲f̲i̲c̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ based upon section separation
of long messages and route separations of messages
applicable for multiple transmissions.
S̲e̲c̲t̲i̲o̲n̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
1) Formatting FL12 - 12D of user prepared plaindress
and data messages.
2) Formatting FL12A - 12B of supervisor prepared
Service Messages.
3) Section Separations of user prepared plaindress
and supervisor prepared service message.
R̲o̲u̲t̲e̲ ̲S̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
4) Formatting FL2 of all messages in ACP127 format.
5) Separate transmissions where the RIs of FL2
exceeds 200.
6) Formatting FL 6 - 9 of user prepared plaindress
and data-messages plus SCARS/CCIS released
messages in plaindress.
7) Formatting of a readdressal initiated by supervisor.
8) Insert of ZEN and RI's in front of PLA's FL
7 - 8 of each transmission in user prepared
messages.
9) Forwarding the messages to transmission, local
distribution or punch in accordance with rules
specified elsewhere.
FIGURE 4.1.1.1-2…01…FUNCTIONAL BREAK-DOWN…01…ACP127 CONVERSION
4.1.1.3 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
In principle the transport functions form is a circle
around the ACP127 analysis and the ACP127- conversion
functions.
Example:
Complete entered message via a PTR
1) The message is transported to ACP127 analysis.
2) After analysis the message is directed for ACP127
conversion.
3) Having converted the message it is again delivered
to transport for transmission to maybe NICS TARE.
In order to make the transport functions more simple
to overview, 3 subpackages have been identified all
containing functions that cross the transport-types.
These functions are detailed described in sections
4.2.3, 4.2.4 and 4.2.5.
The functional relationship is as follows:
I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
NICS TARE, TRC/Point-to-point, SCARS, CCIS and PTR
FIGURE 4.1.1.1-3…01…NICS TARE…01…FUNCTIONAL BREAK DOWN
FIGURE 4.1.1.1-5…01…SCARS/CCIS…01…FUNCTIONAL BREAK DOWN
FIGURE 4.1.1.1-4…01…TRC, Point-to-Point…01…FUNCTIONAL BREAKDOWN
FIGURE 4.1.1.1-6…01…PTR…01…FUNCTIONAL BREAK DOWN
FIGURE 4.1.1.1-7…01…PTP…01…FUNCTIONAL BREAK DOWN
T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
NICS TARE, TRC/Point-to-point, SCARS, CCIS, PTR and
PTP.
O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
NICS TARE, TRC/Point-to-point, SCARS, CCIS and PTP.
In order to provide a specification related to the
network associated transport types, the following description
and the functional break-down depicted in figures 4.1.1.1-3
to 4.1.1.1-7 will apply this.
4.1.1.3.1 N̲I̲C̲S̲ ̲T̲A̲R̲E̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
1) Reception of data-frames from IOC
2) Analysis FL1, channel discontinuity procedures
(if required)
3) Garble characteristics detect and reporting
4) Format-Line detection FL2, FL3, FL4, FL6, FL10
and FL11.
5) Correction of acceptable deviations FL1, FL2
and FL4 (SOTF, Precedence, classification and
special handling)
6) Separate the message into message field groups.
7) Remove page sequences from the text part of
any message except DATA messages.
8) Build-up information concerning the received
message to be transferred with the message
view to ACP127 analysis.
9) Error reporting to supervisor or SSC of error
types not involving a message.
b) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
1) Timeout procedures flash acknowledge
2) Procedures related to channel continuity
3) Channel Open/Close procedures
4) Channel reports to supervisor
5) Automatic generation of the following ASM-types
initiated via a command or time-out:
- channel continuity
- channel number reset
- flash acknowledge
- channel open
- channel close
- channel test
- channel test reply
6) Outgoing message log and statistics
c) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
1) Generation of FL1
2) Generation of Pilot for retransmission
3) Forward data frames to IOC for transmission
4) Insert format parameters during transport like:
- page identifications
- "BT"
- "NNNN" (EOTF)
5) Delivery of retrieval keys associated with
an outgoing message.
4.1.1.3.2 T̲R̲C̲/̲P̲o̲i̲n̲t̲-̲t̲o̲-̲p̲o̲i̲n̲t̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
as specified for NICS TARE (1 - 9)
b) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
as specified for NICS TARE (1 - 5)
5) no channel continuity ASM but generation of
a selfaddressed channel check and identical
character ASM
6) Initiate preemption for outgoing messages with
precedence flash.
c) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
as specified for NICS TARE except from preemption
(1 - 5)
4.1.1.3.3 S̲c̲a̲r̲s̲/̲C̲C̲I̲S̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
a) I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
As specified for NICS TARE (1 - 9)
10) Format Line detection of "MSGID" of comments
and VDU-pages.
11) Build-up information based on message-type
received in a message-control field, in order
to distinguish between ACP127 and E1 formats.
12) Handling of incoming acknowledge messages and
initiate transmission of acknowledge messages.
13) Recognize channel Number Reset.
b) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
As specified for NICS TARE (1 - 5)
6) Initiate preemption
7) Control number of retransmissions
c) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
As specified for NICS TARE except that preemption
will be performed (1 - 5)
6) Generation of FL1 of messages in E1-format
7) Generation of Pilot in E1-format
4.1.1.3.4 P̲T̲R̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
This transport is considered an incoming transport
with the same functional capabilities as for NICS TARE
except point 2, which will not be performed at all.
Point 3 and 9 will be performed to some extent in respect
of the special error-types that might occur on such
a device (e.g. paper-out might be confused with a halted
message condition and will here be viewed as a not
successful input, which will be manually repeated).
The purpose of the specified transport control is to
serve supervisor and SSC-commands (e.g. the low speed
teleprinter operating as a PTR shall be changed to
operate as a PTP or printer)
4.1.1.3.5 P̲T̲P̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
This transport is considered an outgoing transport
with the same functional capabilities as specified
for NICS TARE.
Point 1 and 2 concerning generation of FL1 and Pilots
is, however, not applicable as described.
FL1 will be replaced with a visual formatted sequence-number
preceded by 20 cm of blank tape, a visual formatted
sequence number and 30 cm of blank tape.
A "pilot" will be visible in a similar manner in case
of "repunch" (after switch-over or paper-out etc.)
The transport control receives commands from SSC and
supervisor similar as described for the PTR. It also
initiates preemption on arrival of messages with precedence
flash for punch.
4.1.1.4 C̲o̲m̲m̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The common functions identified are mainly within a
subpackage. These common functions will therefore be
described under subpackage specification for that subpackage.
The remaining common function between the subpackages
of THP can be located at a very low level (identified
in sections 4.2.1 to 4.2.5)
a) C̲r̲e̲a̲t̲e̲ ̲H̲Q̲/̲S̲I̲C̲-̲L̲i̲s̲t̲
Common to analysis and conversion.
Will be developed under analysis.
b) C̲h̲e̲c̲k̲ ̲c̲i̲r̲c̲u̲i̲t̲ ̲c̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲a̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲
Common to conversion and analysis. Will be developed
under conversion.
c) A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲L̲1̲
Format-Line detect used by analysis-subpackage.
Incoming transport subpackage will develop the
analysis for channel discontinuity.
d) A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲L̲2̲,̲ ̲F̲L̲3̲,̲ ̲F̲L̲4̲,̲ ̲F̲L̲6̲,̲ ̲F̲L̲ ̲1̲0̲
Format-line detect used by incoming transport subpackage.
Analysis subpackage will develop the analysis modules.
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The external environment for THP consists of circuits
and channels. A circuit is a group of similar channels.
Figure 4.1.2-2 shows the software and queue structure
for THP. Figure 4.1.2-1 shows the general software
and queue structure for a circuit. Each channel is
managed by a transport process. Messages to be transmitted
on a circuit is sent to a circuit queue, which is shared
by the transport processes belonging to the circuit.
Each transport process has further a private command
queue where it can receive commands from SSC, timer
events etc. The number of channels may be up to 32.
4.1.2.1 C̲h̲a̲n̲n̲e̲l̲ ̲a̲n̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲ ̲Q̲u̲e̲u̲e̲s̲
a) C̲i̲r̲c̲u̲i̲t̲ ̲Q̲u̲e̲u̲e̲
A circuit queue has 6 subqueues corresponding to
6 precedence levels. It is shared by the transport
processes of the circuit. If the circuit consists
of a single channel, there is flash preemption.
If there is more than one channel, flash preemption
will not take place.
Messages are sent to the circuit queue by ACP127
conversion. When a flash message is sent to a single-channel
circuit, a flash notification will be sent to the
channel command queue.
FIGURE 4.1.2-2…01…TRAFFIC HANDLING PROCESS STRUCTURE
Circuit queue profile:
- classification = circuit classification
- special handling = all categories.
b) C̲h̲a̲n̲n̲e̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲ ̲Q̲u̲e̲u̲e̲
Has one subqueue.
The following examples of events are sent to the
queue:
From TEMCO: Channel Commands, e.g. open and close.
From ACP127 Analysis: Channel Check received.
From ACP127 Conversion: Flash Notification
From TIMER: Timer Event
A timer event will be received once every minute. The
transport process will use this to control a number
of internal timeout functions.
Channel Queue Profile: Zero in all fields.
4.1.2.2 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The structure and major environment of Transport Process
is shown below.
FIGURE 2.3…01…STRUCTURE AND ENVIRONMENT OF CHANNEL PROCESS
The transport process consists of 3 coroutines:
a) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲O̲u̲t̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
Waits in semaphore S for item to transmit. The
item may come from circuit queue or from transport
control coroutine. Transport out will then read
the item and transmit it.
The coroutine uses the CSF function INIT RECEIVE
to direct queue elements from circuit queue to
semaphore S.
b) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲I̲n̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
Reads messages from channel and then writes to
CIFs. The CIFs are sent to the ACP127 Analysis
queue.
c) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
Is responsible for the management functions associated
with a channel. May generate acknowledge, channel
check messages etc. The transmission of those items
is however done by transport Out Coroutine.
The coroutine shall request a timer event for every
minute.
4.1.2.3 A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
a) A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲s̲s̲
Is a single process responsible for ACP127 conversion
of all outgoing messages. The process receives
messages from the conversion queue, converts them
and sends them to appropriate circuit queue.
If, for performance reasons, there is a need to
overlap conversion CPU usage, table access and
message I/O, the process can be structured into
two similar coroutines. It can then convert two
messages in parallel.
b) C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲Q̲u̲e̲u̲e̲
Has a single structure, so messages are processed
in sequence irrespective of precedence.
Has three subqueues, two for messages for conversion
(one for flash and one for non-flash) and one for
messages returned from MSO and commands from SSC.
The latter has highest priority. It serves the
purpose of immediate entry of the messages for
repeated routing assignment after MSO intervention.
Queue Profile for subqueues and for conversion
process shall be with maximum capabilities.
4.1.2.4 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
a) A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲P̲r̲o̲c̲e̲s̲s̲
A single process responsible for ACP127 analysis
of all incoming and complete messages. The process
receives messages in the analysis queue, converts
them to external format, if applicable for that
message type, possibly with help from MSO, and
sends them to appropriate destination queues.
As described for ACP127 Conversion, the process
can for performance reasons be structured into
two coroutines.
b) A̲n̲a̲l̲y̲s̲i̲s̲ ̲Q̲u̲e̲u̲e̲
Has three subqueues, two for incoming messages
from a transport process (flash/non-flash), and
one for messages returned from MSO and commands
from SSC. The latter has highest precedence. It
serves the purpose of immediate entry of the message
for repeated analysis after MSO intervention.
Queue Profile of both subqueues shall be the highest
possible.
4.1.2.5 C̲I̲F̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
The profile of a CIF consists of security classification,
special handling categories, exercise indicator and
message type indicator. For incoming messages, the
profile must be generated by THP. The following sequence
applies:
a) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲
The transport process does not always detect the
actual profile for an incoming message. Instead
it must define the profile as the worst case. So
it shall set the CIF profile to the profile of
the channel.
b) A̲C̲P̲ ̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲P̲r̲o̲c̲e̲s̲s̲
The ACP127 analysis will, if possible, detect the
actual profile of the message, possibly with help
from MSO. It will then update the profile via a
CSF-call.
4.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The following sections
- Data Flow
- Message View Flow
- Semaphore Logic
will give an overview description of the Data Flow
and Control Logic of the Traffic Handling Package.
4.1.3.1 D̲a̲t̲a̲ ̲F̲l̲o̲w̲
The HIPO-diagrams following this section (figures 4.1.3.1-1
to 4.1.3.1-7) illustrate in overview the Data Flow
provided by this Package. The ACP127 analysis will
be illustrated and described in 3 independent flows
in accordance with the functional capabilities.
1) I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Receives data frames (Lines) via external channels
and the PTR. These lines are collected to form
messages in ACP127 format or SCARS/CCIS E1 format.
2) I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Receives incoming messages for analysis; that is
messages delivered to analysis by an Incoming Transport
Process serving an external channel. These messages
are mainly in ACP127 format, but can also be in
SCARS/CCIS E1 format.
After analysis the messages are directed to their
proper destinations at CAMPS in accordance with
the message type (see diagram 4.1.3.1-2 for further
details).
3) C̲o̲m̲p̲l̲e̲t̲e̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Receives outgoing messages entered via a normal
PTR in complete ACP127-format for analysis. After
analysis encrypted messages are directed to message
service for Group Count Verification before conversion
and transmission. Other message types are directed
to ACP127-conversion.
4) P̲T̲R̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Receives off-line decrypted and encrypted messages
in complete ACP127-format entered via the dedicated
PTR. Decrypted messages are directed to local distribution
after analysis and conversion to the internal E1-format.
Encrypted messages are directed to ACP127-conversion
and following transmission.
5) A̲C̲P̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
Receives messages in various formats and message
types. Provides routing, ACP127 formatting, and
separation of the message into multiple transmissions
if required in relation to sections and routes.
Also it will direct messages to be locally distributed
into the internal E1 format or to be punched at
the dedicated PTP (ACP127 format) if applicable.
Otherwise it will direct the converted messages
to a circuit queue.
6) T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
Receives commands from the ACP127 analysis Process
and others that will initiate automatic generation
of an ASM (e.g. channel test channel close, channel
open and flash acknowledge).
Also it will control timer events and if required
initiate retransmissions and automatic generation
of timer depending ASMs like Channel Continuity.
7) O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Receives messages from a circuit queue, separates
the message into data frames relevant to the serving
channel/network type (that is NICS TARE, TRC/Point-to-point
or SCARS/CCIS).
It also receives supervisor initiated reruns for
retransmission. The transport process serving a
PTP queue is functionally also viewed as an outgoing
Transport Process.
4.1.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲V̲i̲e̲w̲ ̲F̲l̲o̲w̲
As an introduction to the HIPO and other diagrams shown
in sections 4.2.1 to 4.2.5 this section will define
the terms used in accordance with message views in
ACP127 format.
a) Diagram "R̲e̲c̲e̲i̲v̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲" (figure 4.1.3.2-1) illustrates
first the maximum model of a received message and
the possible fields it might be separated into
by an Incoming Transport Process. This is done
on basis of the format-line detection parameters:
"DE", "FM" and "BT". Following this rule, the various
message types will be separated into the Field
Groups as illustrated on that figure.
The terms: Head 1, Head 2, Head 3
Text 1, Text 2 and Text 3
is used for convenience and documentation purposes;
they will most probably later be replaced with
a number defining the Field Group.
The purpose of this separation method is:
- to increase performance
- to reduce storage
- to secure the analysis
Examples:
1) Because the text-part of the message has been
separated into a testfield (and the page-identifications
removed) at reception, it will not be necessary
for the analysis to go through more than the
4 lines of text (increases performance).
2) Relaying of a message can be done quickly by
forming a new message view with the same contents
as the received except a new head1-field containing
FL2 (reduces storage)
3) The pattern of Field Groups (plus some other
information) makes it possible to start an
ACP127 analysis with a message type determination
(secure analysis).
b) Diagram "̲G̲e̲n̲e̲r̲a̲l̲ ̲V̲i̲e̲w̲ ̲A̲C̲P̲1̲2̲7̲-̲a̲n̲a̲l̲y̲s̲i̲s̲ (figure 4.1.3.2-2)
illustrates the manipulations that might be performed
on a message in ACP127 format. The essence is,
that an information field is updated and some internal
lists are added to the message view for various
purposes (other field groups).
c) Diagram "G̲e̲n̲e̲r̲a̲l̲ ̲V̲i̲e̲w̲ ̲A̲C̲P̲ ̲1̲2̲7̲-̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲" (figure
4.1.3.2-3) illustrates how the information field
and the internal fields (lists) are used in order
to create message views in ACP127 format.
d) Diagram "̲T̲r̲a̲n̲s̲m̲i̲t̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲"̲ (figure 4.1.3.2-4)
illustrates first a maximum model of a converted
message. The remaining part illustrates the message
views that are created by ACP127-conversion and
an outgoing transport process in common for that
particular message type.
FIGURE 4.1.3.2-1…01…RECEIVED MESSAGE
…01…FIGURE 4.1.3.2-2…01…GENERAL VIEW ACP127-ANALYSIS
FIGURE 4.1.3.2…01…GENERAL VIEW ACP127 - CONVERSION
FIGURE 4.1.3.2-4…01…TRANSMITTED MESSAGE
4.1.3.3 S̲e̲m̲a̲p̲h̲o̲r̲e̲ ̲L̲o̲g̲i̲c̲
Semaphores are used by a Transport Process in order
to synchronize the Incoming Transport Coroutine (ITC),
the Transport Control Coroutine (TCC) and the Outgoing
Transport Coroutine (OTC).
In the following the logic involved for use of the
semaphores will be explained with references to the
Network or Device served by the Transport Process.
4.1.3.3.1 N̲I̲C̲S̲ ̲T̲A̲R̲E̲,̲ ̲T̲R̲C̲/̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲
Ref. figure 4.1.3.3-1 for overview. One semaphore is
defined to synchronize the activities between OTC and
TCC.
1) A message arrives to a circuit queue. This event
is signalled to the semaphore by incrementing a
counter plus sorting a pointer into a semaphore-list
on precedence-basis.
2) The OTC will take a pointer to a message from that
list and decrement the counter.
3) If the message transported out was of precedence
flash, the Timer-List will be updated with that
event (see layout common data).
4) Once per minute a timer-command will be given through
the channel Command Queue to TCC. TCC will decrement
the timer-value for flash acknowledge.
5) If the time-out value is reached, it will place
a pointer to the message with a notification for
retransmission first into the semaphore pointer
list by means of a call to the Coroutine Monitor.
6) The OTC will then as next take the message for
retransmission, create a suspected duplicate pilot
and transport the message out for transmission.
7) Similar principles as 5) and 6) are used for transport
of automatically generated ASMs (e.g. channel number
reset, channel open and channel close).
4.1.3.3.2 S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Ref. figure 4.1.3.3-2 for overview. Two semaphores
are defined. Semaphore (S2) has the same mission as
the semaphore described under section 4.1.3.3.1 (NICS
TARE). The purpose of Semaphore (S1) is to control
Transaction Acknowledgement.
a) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
1) OTC takes a message from the S2-pointer-list,
transports it out for transmission and updates
the timer-list.
2) OTC then waits for acknowledgement received
signal via semaphore S1.
3) TCC receives timer event that decrements the
time-out value for transaction acknowledgement.
4) If time-out, TCC inserts a pointer to the message
with notification for retransmission in the
S2 pointer list and releases the semaphore
S1.
5) OTC will then return to S2 and in this case
initiate a retransmission with a suspected
duplicate pilot, whereafter it will wait upon
another release of S1.
6) ITC receives a Transaction Acknowledgement
and releases S1.
b) I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
1) ITC receives a message and reports this event
to TCC via the Channel Command Queue.
2) TCC generates the Transaction Acknowledgement
and inserts pointer via the S2 pointer list
(plus releases the semaphore S1).
3) OTC will as next transport the Transaction
acknowledgement for transmission.
4.1.3.3.3 P̲T̲R̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Ref. figure 4.1.3.3-3 for overview. No semaphores are
defined.
4.1.3.3.4 P̲T̲P̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲
Ref. figure 4.1.3.3-4 for overview. One semaphore is
defined. The purpose of this semaphore is similar to
the NICS TARE semaphore, but the function related to
the use of it is of smaller size.
That is repeat of punch in case "paper-out" and procedures
associated with start-up, close-down and preemption.
FIGURE 4.1.3.3-1…01…NICS TARE AND TRC/POINT-TO-POINT
TRANSPORT PROCESS
FIGURE 4.1.3.3-2…01…SCARS and CCIS TRANSPORT PROCESS
FIGURE 4.1.3.3-3…01…PTR TRANSPORT PROCESS
FIGURE 4.1.3.3-4…01…PTP TRANSPORT PROCESS
4.1.4 C̲o̲m̲m̲o̲n̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
The common Data Elements of this Package is isolated
to the Transport Process.
As described in section 4.1.3.3 (semaphore Logic) the
coroutines Outgoing Transport, Transport Control and
Incoming Transport in common uses a Timer-table.
L̲a̲y̲o̲u̲t̲ ̲T̲i̲m̲e̲r̲ ̲T̲a̲b̲l̲e̲:̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Time-out Retransmissions View-ID
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length: 2 Integers
Size: 32 x 25 records
Total: 3.200 Bytes
T̲i̲m̲e̲-̲O̲u̲t̲ ̲V̲a̲l̲u̲e̲ ̲(̲h̲a̲l̲f̲ ̲I̲n̲t̲e̲g̲e̲r̲)̲
The time in minutes left for time-out.
R̲e̲t̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲s̲ ̲(̲h̲a̲l̲f̲ ̲I̲n̲t̲e̲g̲e̲r̲)̲
A decremented value indicating the maximum number of
retransmissions allowed.
V̲i̲e̲w̲ ̲I̲d̲.̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲
A reference to the message view waiting for acknowledgement.
R̲e̲c̲o̲r̲d̲ ̲O̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲:̲
1) Selfaddressed Channel Check
2) Transmit Channel Number Reset
3) Receive Channel Number Reset
4) Transaction Acknowledgement
5-25) Flash Acknowledgement
For the channels where preemption is applicable, a
flag set by the Transport Control (initiated via a
command to a channel command queue) will be defined
somewhere in this common area.
4.1.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
C̲h̲a̲n̲n̲e̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲s̲ ̲a̲n̲d̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
The channel profiles and the parameters needed to determine
periods and size of timer events, are as well common
to the Traffic Handling Subpackages as external data
elements in relation to the Terminal Package. See figure
4.1.5-1 and 4.1.5-2 for details.
R̲o̲u̲t̲i̲n̲g̲,̲ ̲P̲L̲A̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲L̲i̲s̲t̲s̲
These lists defined as Field-Groups into the Internal
Message Format are the means by which results of a
validation is transferred between THP and TEP and visa
versa. The reason is to avoid unnecessary table accesses.
See section 4.2.1.4 for layout and supplementary details.
I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲f̲i̲e̲l̲d̲s̲
Other external Data elements are transferred to other
packages by means of information fields associated
to the message (CIF and View). That is SICs, message
type etc.
FIGURE 4.1.5-2…01…CHANNEL PARAMETERS
FIGURE 4.1.5-1…01…CHANNEL PROFILE
4.1.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The external and Internal Interfaces of the Traffic
Handling Package are as described in the following
and as illustrated in figure 4.1.6-1.
4.1.6.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N̲I̲C̲S̲ ̲T̲A̲R̲E̲
Ref. CPS/230/ICD/0004
S̲C̲A̲R̲S̲
Ref. CPS/230/ICD/0005
C̲C̲I̲S̲
Ref. CPS/230/ICD/0006
P̲T̲R̲
P̲T̲P̲
L̲O̲W̲ ̲S̲P̲E̲E̲D̲ ̲T̲E̲L̲E̲P̲R̲I̲N̲T̲E̲R̲S̲
4.1.6.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The following application Packages are interfaced from/to
Traffic Handling Package:
- Message Distribution (MDP)
- Terminal Package (TEP)
- Storage and Retrieval (SAR)
- Log (LOG)
- Statistics (STP)
The following processes of THP interface each other
and above mentioned packages:
- ACP127 Analysis (AAS)
- ACP127 Conversion (ACS)
- NICS TARE Transport (NT-TRS)
- TRC/Point-to-Point Transport (TP-TRS)
- SCARS/CCIS Transport (SC-TRS)
- PTP Transport (PTP-TRS)
- PTR Transport (PTR-TRS)
4.1.6.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲
a) A̲A̲S̲ ̲t̲o̲ ̲T̲E̲P
Incoming message for local distribution
b) A̲C̲S̲ ̲t̲o̲ ̲M̲D̲P̲
Outgoing message containing local PLA for local
distribution as incoming.
4.1.6.2.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲
a) A̲A̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲
1) Incoming message service assistance
- Garble Correction
- Pilot Detect
- Relay Assistance
2) Abbreviated and normal Service messages to
Supervisor Printer.
3) Comments and VDU-pages to be presented at a
Terminal Position.
4) Message for coordination to be presented at
a Terminal Position and transferred to the
related prepare-queue.
5) Message for Release to be presented at a Release-Position.
6) Message for alternative distribution to MDCO
in case of unsuccessful delivery.
b) A̲C̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲
1) Outgoing Message Service for RI-assignment.
c) N̲T̲-̲T̲A̲S̲/̲T̲P̲-̲T̲R̲S̲/̲S̲C̲-̲T̲R̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲
1) Not expected ASMs to Supervisor printer (e.g.
flash acknowledge)
2) Channel Reports to Supervisor Printer.
d) T̲E̲P̲ ̲t̲o̲ ̲A̲A̲S̲:̲
1) Messages reentered for analysis from an Incoming
Message Service Position.
2) Messages entered as readdressal from a Supervisor
Position.
e) T̲E̲P̲ ̲t̲o̲ ̲A̲C̲S̲:̲
1) User prepared Plaindress and Data Messages
for RI-assignment and conversion.
2) Supervisor prepared ASM and Service Messages
for RI-validation and conversion.
3) User prepared SCARS/CCIS comments and VDU-pages.
4) Outgoing Message Service reentering message
after RI-assignment. The re-entered message
may indicate that the functions CLEAR, PUNCH
and/or Relay Assignment had been performed
during RI-assignment.
5) Supervisor initiated readdressed and rerun.
f) T̲E̲P̲ ̲t̲o̲ ̲N̲T̲-̲T̲R̲S̲,̲ ̲T̲P̲-̲T̲R̲S̲,̲ ̲S̲C̲-̲T̲R̲S̲
1) Supervisor command channel open/close
4.1.6.2.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲A̲R̲
a) A̲A̲S̲ ̲t̲o̲ ̲S̲A̲R̲:̲
1) Retrieval keys incoming message after analysis
(ACP127 format)
2) Retrieval keys incoming message after analysis
and conversion to E1 format.
b) N̲T̲-̲T̲R̲S̲,̲ ̲T̲P̲-̲T̲R̲S̲,̲ ̲S̲C̲-̲T̲R̲S̲ ̲t̲o̲ ̲S̲A̲R̲:̲
1) Retrieval keys outgoing message for which acknowledge
has been received (if required)
4.1.6.2.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲L̲o̲g̲
a) A̲A̲S̲ ̲t̲o̲ ̲L̲O̲G̲:̲
1) Invalid incoming message Log.
2) Incoming message Log.
b) N̲T̲-̲T̲R̲S̲,̲ ̲T̲P̲-̲T̲R̲S̲,̲ ̲S̲C̲-̲T̲R̲S̲ ̲t̲o̲ ̲L̲o̲g̲:̲
1) Outgoing message Log
2) Channel discontinuity Log
c) P̲T̲P̲-̲T̲R̲S̲ ̲t̲o̲ ̲L̲O̲G̲
1) PTP-LOG
4.1.6.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲T̲P̲
a) A̲A̲S̲ ̲t̲o̲ ̲S̲T̲P̲:̲
1) Statistics invalid incoming message
2) Statistics incoming message
b) N̲T̲-̲T̲R̲S̲,̲ ̲T̲P̲-̲T̲R̲S̲,̲ ̲S̲C̲-̲T̲R̲S̲ ̲t̲o̲ ̲S̲T̲P̲:̲
1) Statistics Outgoing Message
2) Statistics Channel open/close.
4.1.6.3 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
These interfaces are identified on figure 4.1.6-1 and
specified in detail in sections 4.2.1.5, 4.2.2.5, 4.2.3.5,
4.2.4.5 and 4.2.5.5 under subpackage interface.
FIGURE 4.1.6-1…01…INTERFACES TRAFFIC HANDLING
4.2.1 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The ACP127 Analysis Subpackage receives messages for
analysis from the Transport Subpackage.
Depending on the originator of the message the analysis
is subdivided into three parts:
- Incoming analysis
- Complete analysis
- PTR analysis
Independent of the analysis type are the common functions:
- Format Line Control and Internal Format Conversion.
The functional Break-down depicted in figures 4.2.1.1-1
to 4.2.1.1-5 describes how the functions are interrelated
to each other.
4.2.1.1.1 C̲o̲m̲m̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The functions depicted in figures 4.2.1.1-3 and 4.2.1.1-4
are the common functions, which are:
a) Format Line control of message types in ACP127-format.
b) Detect of Garble characteristics based on Format
Line Control.
c) Detect of inconsistency between logically related
parameters
d) Detect of errors and acceptable deviations into
each format-line
e) Detect of pilot
f) Detect of readdressed messages
g) Create an error-list to be presented together with
the erroneous message in case of garble correction
h) Create a Routing-list to be used for routing-purposes
by the ACP127 conversion subpackage for outgoing
messages.
i) Create a list of addresses without RIs in front
of the PLAs to used when presenting the message
in format E1.
j) Create a list of HQ/SICs to be used by Message
Distribution Package for distribution of an incoming
message.
4.2.1.1.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The message originators for incoming analysis are NICS
TARE, TRC/Point-to-Point, SCARS or CCIS.
Besides the common functions described in section 4.2.1.1.1
the following functions as depicted in figures 4.2.1.1-1,
4.2.1.1-2 and 4.2.1.1-5 are provided in this analysis:
a) Reception Error Handling based upon information
received from the Transport Subpackage.
That is:
- 140 identical characters
- halted message
- preempted message
- oversized message
- too long line
- expected TSN too low
b) Format Line Control of messages received in SCARS/CCIS
E1 format
- detect of E1 pilot
- detect of garble characteristics
- detect of acceptable deviations and errors
associated to the E1 Format lines.
c) Handling of message types in E1 format received
from SCARS or CCIS
- Already released message
- message for release (CCIS only)
- message for coordination (CCIS only)
- comments
- VDU-pages
d) Handling of received abbreviated service messages
- channel number reset
- channel check
- channel continuity
- channel test
- channel test reply
- channel open
- channel close
- flash acknowledge
e) Initiate automatic generation of ASM in case of:
- receipt of messages with precedence flash (Flash
Acknowledge)
- receipt of messages with 140 consequtive characters
(identical character ASM)
- receipt of channel test
(channel test reply ASM)
d) Relaying of messages containing relay instructions.
e) Log, statistics and retrieval keys
- invalid message log
- incoming message log
- statistics incoming message
- retrieval keys incoming message
f) Final route determination:
- Encrypted messages to the dedicated PTP
- Service messages and not recognized ASM types
to the supervisor position.
- Plaindress and Data Messages to message distribution
for distribution to terminal positions
- Released message from SCARS or CCIS to the
ACP127 conversion subpackage for processing
as an outgoing message.
- Comments and VDU-pages from SCARS or CCIS to
a terminal position indicated by a SCD in FL
D1 or FL D2.
- Message for coordination to a terminal prepare
position indicated by an SCD in FL D4. This
procedure will be executed so that the receiver
of the message takes the responsibility (becomes
the originator).
- Message to be released by CAMPS. This function
will be executed by directing the message to
a release position based upon the SCD in FL
D3. The releaser takes responsibility for the
message by becoming the message originator.
- Illegal messages (garbled or with format line
errors) to the incoming message service position
for garble correction.
- Messages preceded with a pilot and messages
with too low TSN to the incoming MSO.
- Garbled messages of precedence flash or immediate
that are not too garbled to be converted into
the internal E1 format to MDP for distribution
decision.
- Unsuccessful deliveries to above mentioned
positions to the MDCO for alternative decision.
g) In case MSO invocation had been needed the MSO
first involved will be activated for further corrections.
4.2.1.1.3 C̲o̲m̲p̲l̲e̲t̲e̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The message originators of complete messages are the
low speed teleprinters operating as PTR's.
Besides the common functions described in section 4.2.1.1.1
the main functions are as depicted in figure 4.2.1.1-1.
The complete entered message types are always considered
outgoing and will therefore after a successful analysis
be queued to the ACP127 conversion subpackage for onward
processing.
There are no special individual functions to be detailed
described; however, it shall be emphasized that the
complete analysis compared with the incoming analysis
do not perform:
- relaying
- ASM-handling
- flash acknowledge
- log, statistics and retrieval-keys
4.2.1.1.4 P̲T̲R̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The originator of a message for PTR analysis is the
dedicated PTR. Besides the common functions described
in section 4.2.1.1.1 the main functions are as depicted
in figure 4.2.1.1-1.
The messages received from the dedicated PTR are, depending
on whether FL1 is present or not, considered respectively
incoming or outgoing.
The incoming message is considered a codress message
that has been off-line decrypted and now is entered
in plaindress still containing FL10 with the group
count and is bound for internal distribution after
analysis. Retrieval keys will be delivered as if the
message had been incoming
The outgoing message is considered a plaindress message
that has been punched at the PTP, off-line encrypted
and now entered in codress or encrypted plaindress
for analysis, conversion and finally transmission.
The PTR analysis is dedicated above described message
types.
FIGURE 4.2.1.1-1…01…FUNCTIONAL BREAK-DOWN…01…ACP127-ANALYSIS
FIGURE 4.2.1.1-2…01…FUNCTIONAL BREAK-DOWN…01…E1 ANALYSIS CONTROL
FIGURE 4.2.1.1-3…01…FUNCTIONAL BREAK-DOWN…01…ACP127-ANALYSIS CONTROL
FIGURE 4.2.1.1-4…01…FUNCTIONAL BREAK-DOWN…01…INTERNAL FORMAT CONVERSION
FIGURE 4.2.1.1-5…01…FUNCTIONAL BREAK-DOWN…01…ASM HANDLING
