top - download
⟦637293074⟧ Wang Wps File
Length: 60502 (0xec56)
Types: Wang Wps File
Notes: FIX/1000/PSP/038
Names: »5206A «
Derivation
└─⟦c5670ecfe⟧ Bits:30006140 8" Wang WCS floppy, CR 0516A
└─ ⟦this⟧ »5206A «
WangText
…1e……00……00……00……00…K…02……00……00…K
K…05…K…07…J…02…I…0c…I…07…H…00…H…07…F…08…F…00…E…0b…E…07…D…0f……86…1 …02… …02… …02…
…0f…
5206A/rt …02…FIX/1000/PSP/0038
…02…APE/850529…02……02…
FIKS SYSTEM SPECIFICATION
…02……02…FK7809
FIKS System Specification
FIX/1000/PSP/0038
Allan Petersen
Ole Eskedal
AMC (6), APE, REV, LU, Library (4)
…0f… ILS Manager 850529
S/W Manager 850529
1
850529
Conf. Manager 850529…0e…
5206Art…02…FIX/1000/PSP/0038
…02…APE/850529…02……02…ii
FIKS System Specification
…02……02…FK 7809
850529 All Issue one of Document
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ..........................................
1
1.2 ABBREVIATIONS ..............................
2
2 APPLICABLE DOCUMENTS ...........................
8
3 NETWORK AND SYSTEMS OVERVIEW ...................
10
3.1 Message Entry and Distribution Equipment
(MEDE) Functions ...........................
11
3.2 Node Functions .............................
13
3.3 SYSTEM CONTROL CENTER (SCC) FUNCTIONS ......
15
3.4 Overview of FIKS Software ..................
17
3.4.1 Operational Software ...................
19
3.4.1.2 Executive Software Extensions ......
22
3.4.1.2.1 Memory Layout ..................
22
3.4.1.2.1.1 Message Transition Control .
24
3.4.1.2.1.2 Queue Access Management ....
28
3.4.1.2.1.3 Shared Memory Access .......
30
3.5 CONFIGURATIONS SUMMARY .....................
33
3.6 MESSAGE FORMAT SUMMARY .....................
41
3.6.1 Narrative Messages .....................
42
3.6.2 Control messages .......................
45
4 FIKS SOFTWARE SYSTEM ...........................
46
4.1 NODE/MEDE APPLICATION SOFTWARE .............
46
4.1.1 Overview ...............................
46
4.1.1.1 System Block Diagram ...............
46
4.1.1.2 Inbound Message Processing .........
46a
4.1.1.2.1 Nodal Message Switching ......
46a
4.1.1.2.2 Inbound Message Distribution .
52
4.1.1.2.2.1 Special Handling .........
53
4.1.1.2.2.2 Delivery of Narrative
Messages to the MEDE .....
53
4.1.1.2.2.3 Delivery of Intercepted
Messages .................
54
4.1.1.2.2.4 Control Messages .........
54
4.1.1.2.3 Message Storage in the
Historical Data Base .........
55
4.1.1.2.4 Message Deletion from the
Historical Data Base .........
56
4.1.1.2.5 Delivery of Messages to
MEDE Terminals ...............
57
4.1.1.2.5.1 Printing Narrative
Messages .................
58
4.1.1.2.5.2 Printing Coordination and
Release Remarks ..........
59
4.1.1.2.5.3 Printing Message Log
Entries ..................
60
4.1.1.3 Message Origination ..............
61
4.1.1.3.1 Message Terminal Logon .......
61
4.1.1.3.2 Message Preparation ..........
62
4.1.1.3.3 Message Coordination .........
63
4.1.1.3.4 Message Editing ..............
63
4.1.1.3.5 Deletion of Preparation
Files ........................
63
4.1.1.3.6 Message Release ..............
63
4.1.1.3.7 Storage of Released Messages
65
4.1.1.3.8 Retrieval from the Histo-
rical Data Base ..............
65
4.1.1.3.9 Display of Retrieved Messages
67
4.1.1.3.10 Message Readdressal ........
67
4.1.1.3.11 Outbound Nodal
Switching ..................
68
4.1.1.3.11.1
Outbound Trunk Queuing .....
68
4.1.1.3.11.2
Outbound Packet
Transmission ...............
69
4.1.1.3.12 Message Terminal Logoff ....
70
4.1.2 Nodal Switch Subsystem ...............
71
4.1.2.1 Introduction .....................
71
4.1.2.2 Functional Capabilities ..........
73
4.1.2.2.1 Overview .....................
73
4.1.2.2.2 Transmission Between Nodes ...
75
4.1.2.2.2.1 The Error Free
Transmission .............
75
4.1.2.2.2.2 Close Trunk ..............
76
4.1.2.2.2.3 Open Trunk ...............
76
4.1.2.2.2.4 Transient Trunk Failure ..
77
4.1.2.2.2.5 Permanent Trunk Failure ..
78
4.1.2.2.2.6 Node Failure .............
81
4.1.2.2.3 Multiaddressing ..............
82
4.1.2.2.4 Traffic Control ..............
85
4.1.2.2.4.1 Routing Control ..........
85
4.1.2.2.4.2 Congestion Control .......
89
4.1.2.2.4.3 Priority Control .........
90
4.1.2.2.5 The NSS in the System
Control Centers ..............
91
4.1.2.3 Interface Description ............
92
4.1.2.3.1 Overview .....................
92
4.1.2.3.2 The Trunks ...................
96
4.1.2.3.3 NPDN Call-up and Close-down .. 101
4.1.2.4 The Modules ...................... 104
4.1.2.4.1 Overview ..................... 104
4.1.2.4.2 The Coroutine Monitor ........ 106
4.1.2.4.3 Initialization ............... 108
4.1.2.4.3.1 Node Start ............... 110
4.1.2.4.3.2 Node Restart ............. 111
4.1.2.4.4 The Packet Handler Module .... 112
4.1.2.4.4.1 General Packet Handling .. 112
4.1.2.4.4.1.1 Introduction ......... 112
4.1.2.4.4.1.2 Protocols ............ 113
4.1.2.4.4.1.2.1 The Application
Interface ........ 113
4.1.2.4.4.1.2.2 The LTUX Protocol 113
4.1.2.4.4.1.2.3 The X.75 Level
3 Protocol ....... 114
4.1.2.4.4.2 Inbound Packet Handling .. 115
4.1.2.4.4.2.1 Functions ............ 115
4.1.2.4.4.3 Outbound Packet Handling . 116
4.1.2.4.4.4 Packet - I/O ............. 117
4.1.2.4.5 The Transport Station Module . 118
4.1.2.4.5.1 General Message Handling . 118
4.1.2.4.5.1.1 Introduction ......... 118
4.1.2.4.5.1.2 Protocol ............. 118
4.1.2.4.5.1.3 Types of Messages .... 121
4.1.2.4.5.2 Inbound Message Transport 122
4.1.2.4.5.3 Outbound Message Transport 124
4.1.2.4.5.3.1 Message Routing ...... 128
4.1.2.4.6 The Monitoring Module ........ 132
4.1.2.4.6.1 Introduction ............. 132
4.1.2.4.6.2 Messages Generated ....... 134
4.1.2.4.6.3 LTUX Supervision ......... 135
4.1.2.4.6.4 Neighbour Node Supervision 136
4.1.2.4.6.5 Functions ................ 137
4.1.2.4.7 The Control Module ........... 139
4.1.2.4.7.1 Introduction ............. 139
4.1.2.4.7.2 Messages Received ........ 139
4.1.2.4.7.3 Functions ................ 140
4.1.2.4.8 The Event Module ............. 141
4.1.2.4.8.1 Introduction ............. 141
4.1.2.4.8.2 Functions ................ 142
4.1.2.4.9 The Starting Module .......... 142
4.1.2.4.9.1 Start/Restart ............ 142
4.1.2.4.9.2 Functions ................ 143
4.1.3 MDS Subsystem Overview ............... 144
4.1.3.1 Functions ........................ 144
4.1.3.1.1 Distribution Management ...... 144
4.1.3.1.2 Terminal Service ............. 145
4.1.3.2 Subsystem Block Diagram .......... 145
4.1.3.2.1 Distribution Management ...... 147
4.1.3.2.1.1 Entering Message
into the HDB ............. 150
4.1.3.2.1.2 Outbound Distribution .... 150 4.1.3.2.1.3 Inbound
Delivery
.........
150
4.1.3.2.1.3.1 Inbound Delivery of
Non SH Message ....... 152
4.1.3.2.1.3.2 Inbound Delivery
of SH Message ........ 152
4.1.3.2.1.3.3 Release of the
Queue Entry .......... 154
4.1.3.2.1.4 Inbound Delivery of
Control Messages ......... 154
4.1.3.2.1.5 Inbound Delivery of
Orbiting Messages ........ 156
4.1.3.2.2 Terminal Service ............. 158
4.1.3.2.2.1 Service of Printers ...... 158
4.1.3.2.2.2 Events Supported by PIP .. 159
4.1.3.2.2.3 Buffers in PIP ........... 161
4.1.3.2.2.4 Files used in PIP ........ 161
4.1.3.2.2.5 Printing of Narrative
Messages ................. 161
4.1.3.2.2.6 Coordination Remarks ..... 162
4.1.3.2.2.7 Remarks .................. 162
4.1.3.2.2.8 Printout of Special
Handling Messages ........ 163
4.1.3.2.2.9 Print Request from
a Teleprinter ............ 163
4.1.3.2.2.10 Log On/Off of Terminals . 163
4.1.3.2.2.11 Message Journal ......... 164
4.1.3.2.2.12 Transaction Log ......... 164
4.1.3.2.2.13 Message Log Reports ..... 164
4.1.3.3 Design Overview .................. 164
4.1.3.3.1 Queues ....................... 165
4.1.3.3.1.1 Format of MDS Input Queue 165
4.1.3.3.1.2 Format of PIP Input Queue 165
4.1.3.3.2 Files ...................... 166
4.1.3.4 Visual Table of Contents ......... 166
4.1.3.5 Subsystem Overview HIPO Diagram .. 168
4.1.3.5.1 The Distribution Management,
MDS .......................... 168
4.1.3.5.1.1 Contents of the
Input Queue .............. 169
4.1.3.5.1.2 Delivery of Control
Messages ................. 169
4.1.3.5.1.3 Storage on the HDB ....... 170
4.1.3.5.1.4 Outbound Distributions ... 170
4.1.3.5.1.5 Inbound Delivery ......... 170
4.1.3.5.1.5.1 Enqueuing of Non-SH
Messages ............. 171
4.1.3.5.1.5.2 Enqueuing of
SH-Messages .......... 171
4.1.3.5.2 Printer Service .............. 171
4.1.3.5.2.1 Buffer in PIP ............ 172
4.1.3.5.2.2 Supervision of the Usage
of Printers .............. 172
4.1.3.5.2.3 Service of the PIP
Input Queue .............. 172
4.1.3.5.2.4 Printing of Narrative
Messages on ROP's and
Teleprinters in RX-Mode .. 173
4.1.3.5.2.5 Printing of Special
Handling Messages ........ 173
4.1.3.5.2.6 Print Request from a
Teleprinter in RX/TX-Mode 174
4.1.3.5.2.7 Print of Coordination
Remarks .................. 174
4.1.3.5.2.8 Print of Remarks ......... 174
4.1.3.5.2.9 Message Log Reports ...... 175
4.1.3.5.2.10 Entries into Message
Log Report .............. 175
4.1.4 Storage and Retrieval Subsystem ...... 176
4.1.4.1 Functions ........................ 176
4.1.4.2 Subsystem Block Diagram .......... 177
4.1.4.3 Design Overview .................. 180
4.1.4.3.1 Design Assumptions ........... 180
4.1.4.3.2 Design Discussion ............ 181
4.1.4.3.2.1 HDB Structure ............ 181
4.1.4.3.2.2 HDB Layout ............... 184
4.1.4.3.2.3 SRS Structure ............ 185
4.1.4.3.2.3.1 Message Storage and
Deletion ............. 186
4.1.4.3.2.3.2 Message Retrieval .... 191
4.1.4.3.2.3.3 Test - HDB Procedure . 198
4.1.4.3.2.3.4 SRS Recovery ......... 199
4.1.4.3.2.4 SRS Layout ............... 199
4.1.4.4 Subsystem Overview HIPO Diagram .. 201
4.1.5 Message Entry Subsystem Overview ..... 204
4.1.5.1 Functions ........................ 204
4.1.5.2 Subsystem Block Diagram .......... 208
4.1.5.3 Design Overview .................. 226
4.1.5.3.1 Queues Accessed .............. 239
4.1.5.3.2 Disk File Access ............. 241
4.1.5.4 Visual Table of Contents ......... 244
4.1.5.5 Subsystem overview HIPO Diagram .. 244
4.1.6 Supervisory Functions Subsystem ...... 248
4.1.6.1 Functions ........................ 248
4.1.6.2 Subsystem Block Diagram .......... 249
4.1.6.3 DESIGN OVERVIEW .................. 257
4.1.6.3.1 Interfaces ................... 260
4.1.6.3.2 Supervisory Functions
Subsystem Queues ............. 262
4.1.6.4 Visual Table of Contents ......... 265
4.2 SYSTEM CONTROL CENTER (SCC) .............. 270
4.2.1 SCC System Overview (on-line SCC) .... 272
4.2.1.1 SCC Hardware Overview ............ 273
4.2.1.2 SCC Software Overview ............ 274
4.2.1.3 SCC External Interfaces .......... 278
4.2.1.3.1 SCC - Collocated N/M Interface 278
4.2.1.3.1.1 Hardware I/F ............. 278
4.2.1.3.1.2 Software I/F ............. 280
4.2.1.3.2 SCC - NICS-TARE Interface .... 293
4.2.1.4 Geographical Back-up ............. 295
4.2.1.4.1 Active SCC Functions ......... 297
4.2.1.4.2 Stand-by SCC Functions ....... 297
4.2.1.4.3 Controlled Switchover ........ 298
4.2.1.4.4 Emergency Switchover ......... 298
4.2.1.4.5 Start-up ..................... 298
4.2.1.4.6 Narrative Message Service
Control ...................... 299
4.2.1.5 Control Message Characteristics .. 300
4.2.1.5.1 Format ....................... 300
4.2.1.5.2 Precedence ................... 304
4.2.1.5.3 Control Message Creation ..... 305
4.2.1.5.4 Creation at NODE/MEDEs ....... 305
4.2.1.5.5 Creation at SCC's ............ 306
4.2.1.5.6 Control Message Flow ......... 306
4.2.1.6 Restart/Recovery ................. 308
4.2.1.7 Executive Software ............... 308
4.2.1.7.1 Interactive Terminal Monitor . 309
4.2.1.7.2 MTCB Monitor ................. 310
4.2.1.7.3 QACCESS (at the SCC) ......... 310
4.2.1.7.4 TV-Monitor Handler ........... 310
4.2.1.8 SCC Off-line Function ............ 312
4.2.1.8.1 Off-line Statistic ........... 312
4.2.1.8.2 File Initialization .......... 312
4.2.1.8.3 FIKS System Generation ....... 313
4.2.1.8.4 Off-line Diagnostic .......... 313
4.2.2 Network Supervision and Control
Subsystem ............................ 314
4.2.2.1 Function ......................... 314
4.2.2.2 Subsystem Block Diagram .......... 315
4.2.2.3 Design Overview .................. 321
4.2.2.3.1 Incoming Control Message
Processing ................... 322
4.2.2.3.2 Network Commanding ........... 323
4.2.2.3.3 Routing Table Calculation .... 323
4.2.2.3.4 File Handling ................ 328
4.2.2.3.5 SCC Control .................. 329
4.2.2.3.6 Restart/Recovery ............. 329
4.2.2.3.7 Queues ....................... 330
4.2.2.3.8 Files ....................... 331
4.2.2.4 Visual Table of Contents ......... 333
4.2.2.5 Subsystem Overview HIPO Diagram .. 333
4.2.3 Network Statistic Subsystem .......... 337
4.2.3.1 Functions ........................ 337
4.2.3.2 Subsystem Block Diagram .......... 337
4.2.3.3 Design Overview .................. 339
4.2.3.4 Visual Table of Contents ......... 343
4.2.3.5 Subsystem Overview HIPO Diagram .. 345
4.2.4 Message Service Subsystem (MSS) ...... 349
4.2.4.1 Functions ........................ 349
4.2.4.2 Subsystem Block Diagram .......... 350
4.2.4.3 Design Overview .................. 360
4.2.4.3.1 Queues ....................... 363
4.2.4.3.2 Files ........................ 363
4.2.4.4 HIPO Overview .................... 363
4.2.5 NICS-TARE Communication Subsystem NTS) .
368
4.2.5.1 Functional Summary .................
368
4.2.5.2 Subsystem Block Diagram ............
369
4.2.5.3 Design Overview ....................
371
4.2.5.3.1 IOMP Submodule .................
373
4.2.5.3.1.1 Outbound Message Processing.
373
4.2.5.3.1.2 Inbound Message Processing .
374
4.2.5.3.1.3 Channel Control ............
374
4.2.5.3.2 EDC Submodule ..................
376
4.2.5.3.2.1 EDC Output Channel .........
376
4.2.5.3.2.2 EDC Input Channel ..........
377
4.2.5.3.3 LTU-Driver Submodule (DLTU) ....
379
4.2.5.3.3.1 DLTU Output Channel ........
379
4.2.5.3.3.2 DLTU Input Channel .........
379
4.2.5.3.4 Queues .........................
380
4.2.5.3.5 Files ..........................
380
4.2.5.5 Subsystem Overview HIPO Diagram ....
382
4.2.6 Inter SCC Handshaking Subsystem (ISH) ..
385
4.2.6.1 Function ...........................
385
4.2.6.3 Design Overview ....................
396
4.2.6.3.1 Files ..........................
404
4.2.6.3.2 Queues .........................
404
4.2.6.4 Visual Table of Contents ...........
406
4.2.6.5 Subsystem Overview HIPO Diagram ....
408
4.3 EXECUTIVE SOFTWARE .........................
412
4.3.1 QACCESS Monitor ...................... 413
4.3.1.1 Functional Capabilities .......... 413
4.3.1.1.1 Queue Procedures ............. 413
4.3.1.1.2 QUEUE Structure .............. 417
4.3.1.2 QACCESS Environment
(Block Diagram) .................. 419
4.3.1.3 Design Overview .................. 421
4.3.1.3.1 Queue Data Area .............. 423
4.3.2 MTCB Monitor ......................... 424
4.3.2.1 Functional Capabilities .......... 424
4.3.2.2 MTCB Procedures .................. 425
4.3.3 The Interactive Terminal Monitor ..... 429
4.3.3.1 Function ......................... 429
4.3.3.2 Subsystem Block Diagram .......... 431
4.3.3.3 Design Overview .................. 435
4.3.3.3.1 Process Start Module (PSM) ... 438
4.3.3.3.2 Terminal Command Module (TCM) 440
4.3.3.3.3 Terminal I/O Module .......... 442
4.3.3.3.4 Error Module (EM) ............ 443
4.3.3.3.5 VDU Handler Module (VDUH) .... 444
4.3.3.3.6 Interactive Terminals ........ 444
4.3.3.3.7 Terminal Operators ........... 445
4.3.3.4 Visual Table of Contents ......... 446
4.3.3.5 Subsystem Overview HIPO Diagrams . 448
4.3.4 Dual NODE/MEDE Design ...................
452
4.3.4.1 Design Overview ...................
453
4.3.4.2 Watchdog ..........................
455
4.3.4.3 ESP System ........................
460
4.3.4.4 System Initialization .............
462
4.3.4.5 Background Processing .............
466
4.3.4.6 Error Handling ....................
469
4.3.4.7 Checkpointing .....................
472
4.3.4.8 Dual Disk Operations ..............
474
4.3.4.9 Switchover of Branches ............
479
4.3.4.10 System Utilities ..................
481
4.3.4.11 System Offline Status .............
482
5 FIKS TDX-SYSTEM .............................. 483
5.1 INTERACTIVE TERMINAL SUPPORT.............. 490
5.1.1 LTUX-VDU ............................. 490
5.1.2 LTUX-TELE ............................ 493
5.2 MESSAGE CRYPTO AND TRANSFER SUBSYSTEM..... 494
5.3 DATA USER SWITCH SUBSYSTEM ............... 501
5.3.1 Components ........................... 502
5.3.2 Data User Routes ..................... 503
5.3.3 Data User Protocols .................. 503
5.3.4 Dedicated FIKS Protocols ............. 508
5.3.5 Data Flow Through the Protocols ...... 510
5.3.6 Message Traffic on Trunks ............ 513
5.3.7 The Data User Route Records .......... 514
5.3.8 Data User Protocols, Detailed Desc. .. 518
5.3.8.1 Data User Plug Protocol .......... 518
5.3.8.2 Data User Routing Protocol ....... 524
5.3.8.3 LDBM Protocols, Introduction ..... 530
5.3.8.4 Message Traffic Handling ......... 545
5.3.8.5 Data User Traffic Handling ....... 546
5.3.8.6 Trunk Electrical level
Protocol V 24 .................... 547
5.3.8.7 Trunk Electrical Level
Protocol X 21 .................... 547
5.3.9 Data User Delays ..................... 547
5.4 SCC SPECIFIC LTUXS ....................... 557
5.4.1 LTUX-TRANS ........................... 558
5.4.2 LTUX-AUDIO/DISPLAY.................... 561
5.5 TDX-SYSTEM INITIALIZATION ................ 563
5.5.1 Start ................................ 565
5.5.2 Switchover/Restart .................. 566
5.5.3 Black Reconfiguration ................ 567
5.5.4 NPDN - Call-Up ....................... 568
5.5.5 NPDN Close-Down ...................... 569
1 S̲C̲O̲P̲E̲
This document describes the logical structure and use
of the application and executive software that supports
the FIKS network functions. Summarized also are the
hardware and firmware components that comprise network
nodal system configurations.
The functions to be performed are described as being
supported by software subsystems. Subsystems in turn
are composed of logical program units referred to as
modules.
The design presented herein is as it was when the FIKS
System was delivered to the customer. The document
is intended to be an overview of and an introduction
to the FIKS System. For detailed design specifications
refer to the product specification listed in section
2.
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
ACK = acknowledgement
ACP = allied communications protocol
ADDR = address
ADP = automatic data processing
ACL = access control list
AIG = address indicator group
ALF = accountability log file
AMC = air material command
ANO = address number
ASCII = american standard code for information
interchange
ASM = abbreviated service message
ASR = automatic send receive
ATOM = atomal
BID = block identification
BID-1000 = cryptographic equipment
BG = background
CCIE = communication channel I/F equipment
CCITT = committ} consultatif international
telegraphique et telephonique
CHODDEN = chief of defense, denmark
CMD = cartridge module drive
COMCENTER = communication center
COMSEC = communications security
CONF = confidential
CPU = central processing unit
CR = carriage return
CR A/S = christian rovsing a/s
CRYPTO = cryptographic
CRYS = crypto security
CTS = cosmis top secret
CPEI = computer program end item
CHECKP = checkpoint
CIP = collocated interface process
CWD = CIP watchdog
CPM = CIP protocol machine
CQ = conversion queue
DCE = data circuit terminating equipment
DEE = data encrytion equipment
DEMUX = demultiplexer
DMA = direct memory addressing
DOLCE = digital online crypto equipment
DQM = delivery queuer module
DTE = data terminal equipment
DTG = date/time group
DTGF = date/time group file
EDC = error detection and correction
EOT = end of transmission
ESP = error switchover proces
EXCL = exclusive
FDX = full duplex
FIFO = first in - first out
FIKS = forsvarets integrerede kommunikationssystem
FMS = file management subsystem
FMP = file management processor
FSS = fiks software system
FTR = fortroligt
FXS = fiks executive software
GR = groups
HDB = historical data base
HDLC = high level data link control
HDX = half duplex
HEM = hemmeligt
HIPO = hierarchy plus input-process-output
ID = identification
INT DIST = internal distribution
IMF = inbound message file
I/O = input/output
IOS = input/output system
ITA = international telegraph alphabet
ITM = interactive terminal monitor
KSR = keyboard send and receive
LF = line feed
LITSYNC = litton synchronous line protocol
LP = line printer
LTU = line termination unit
LCFH = LTUX configuration file handler
MBC = main bus controller
MDS = message distribribution subsystem
MEDE = message entry and distribution
equipment
MEM = memory
MES = message entry subsystem
MJF = message journal file
MMD = mini module drive
MOM = minutes of meeting
MR = message reference
MRF = message retrieval file
MSG = message
MSUT = medium speed user terminal
MTCB = message transition control block
MUX = multiplexer
MTF = message text files
MLF = message log file
NA = not applicable
NAK = not acknowledgement
NBS = national bureau of standards
(US)
NC = nato confidential
NH = normal handling
NICS = nato integrated communications
system
NODE = fiks node processor
NPDN = nordic public data network
NR = nato restricted
NS = nato secret
NSC = network supervision and control
NU = nato unclassified
NT = nics tare
OJT = on the job training
OMF = outbound message file
OMNI = omnicoder crypto equipment
OPR = operator
ORIG = originator
OLD = online diagnostic
PDB = preparation data base
PIP = printer interface process
PQM = printer queuer module
PROM = programmable read only memory
PSH = previledged service handling
module
PSM = process start module
PSU = power supply unit
PTP = paper tape punch
PTR = paper tape reader
PSP = product specification
Q = queue
RAM = random access memory
RDF = routing directory file
REST = restricted
RI = routing indicator
ROM = read only memory
ROP = receive only printer
RRM = restart recovery module
RR = receiver ready packet
SCC = system control center
SCM = system conroller and memory
SDM = special delivery module
SECR = secret
SFS = supervisory functions subsystem
SH = special handling
SHD = special handling designator
SIC = subject indicator code
SMD = storage module drive
SMF = simplified message format
SOT = start of transmission
SPECAT = special category
SPX = simplex
SRS = storage subsystem
STANAG = standard nato agreement
SYN = synchronization character
SRR = retrieval subsystem
SPS = system product specification
SGP = system generation procedure
SCCLDD = software configuration control
library description document
SCCP = software configuration control
procedure
SIP = SCC interface process
SPM = SIP protocol machine
SWD = SIP watchdog
TARE = (nics) telegraph automatic relay
equipment
TBI = to be inserted
TBD = to be defined
TBS = to be supplied
TCB = terminal control block
TCM = terminal command module
TDX = time divisioned multiplexing
TEF = temporary edit file
TI = transmission identification
TIOM = terminal I/O module
TMF = text mask file
TMC = terminal monitor system
TOR = time of receipt
TOSCA = tote system computer assisted
TP = teleprinter
TRF = temporary remarks file
TSEC = topsecret
TSN = transmission serial number
TTJ = til tjenestebrug
TTY = teletype
UKL = uklassificeret
UNCL = unclassified
USP = user security profile
VDU = visual display unit
V24/V28 = v-series CCITT recommendations
definition of interchange circuits
between DTE and DCE
VDD = version description document
WD = Watchdog
X21/X25 = packet switching CCITT recommendations
YHM = yderst hemmeligt
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
FIX/1200/PSP/0042 FIKS
File
Generators
PSP
FIX/1000/PSP/0038 FIKS
System
PSP
FIX/1256/PSP/0039 CONV
̲DTG
Monitor
PSP
FIX/1161/PSP/0044 DOT
Subsystem
PSP
FIX/1161/PSP/0045 DRP
Subsystem
PSP
FIX/1105/PSP/0046 ESP
System
PSP
FIX/1161/PSP/0047 EVA
Subsystem
PSP
FIX/1256/PSP/0049 GET
̲DTG
Monitor
PSP
FIX/1256/PSP/0050 GETUSP
Monitor
PSP
FIX/1161/PSP/0051 HSP
Subsystem
PSP
FIX/1256/PSP/0056 LOG
̲ACT
Monitor
PSP
FIX/1256/PSP/0057 LOG
̲JOUR
Monitor
PSP
FIX/1164/PSP/0059 MAS
Subsystem
PSP
FIX/1266/PSP/0063 MIOMON
Monitor
PSP
FIX/1164/PSP/0065 MSA
Subsystem
PSP
FIX/1161/PSP/0068 NED
Subsystem
PSP
FIX/1162/PSP/0069 NES
Subsystem
PSP
FIX/1161/PSP/0070 NIP
Subsystem
PSP
FIX/1161/PSP/0071 NOP
Subsystem
PSP
FIX/1200/PSP/0072 OLD
SUBSYSTEM
PSP
FIX/1200/PSP/0076 PSM
Procedure
PSP
FIX/1200/PSP/0077 PURGE
Procedure
PSP
FIX/1256/PSP/0078 QACCESS
Monitor
PSP
FIX/1256/PSP/0081 RDF
Monitor
PSP
FIX/1200/PSP/0084 RECOVM
Procedure
PSP
FIX/1200/PSP/0085 RESPDB
Procedure
PSP
FIX/1100/PSP/0086 RIA
Subsystem
PSP
FIX/1266/PSP/0087 RITA
Monitor
PSP
FIX/1155/PSP/0088 SAF
Subsystem
PSP
FIX/1266/PSP/0089 SCCM
Subsystem
PSP
FIX/1160/PSP/0091 ISH
Subsystem
PSP
FIX/1155/PSP/0093 SFS
Submodule
PSP
FIX/1161/PSP/0094 SOP
Subsystem
PSP
FIX/1161/PSP/0095 SPU Subsystem PSP
FIX/1200/PSP/0098 SYSCHP Procedure PSP
FIX/1161/PSP/0103 TUP Subsystem PSP
FIX/1266/PSP/0106 STAMON Monitor PSP
FIX/1200/PSP/0108 DTX SUBSYSTEM PSP
FIX/3232/PSP/0022 LTUX-TELE appl. F/W PSP
FIX/3232/PSP/0023 LTUX-AUDIO/DISPLAY F/W PSP
FIX/3232/PSP/0026 LTUX-SYNC appl. F/W PSP
FIX/3232/PSP/0027 LTUX-TRANS PSP
FIX/3232/PSP/0028 FIKS watchdog F/W PSP
FIX/3232/PSP/0030 LTUX-VDU PSP
FIX/3232/PSP/0032 LTUX-TRUNK PSP
FIX/3232/PSP/0034 TDX-Device Config. PSP
FIX/3232/PSP/0035 LTUX-ASYNC PSP
FIX/3232/PSP/0036 LTUX-FLYPEP/TERMINAL PSP
FIX/3232/PSP/0037 LTUX-FLYPEP/COMPUTER PSP
FIX/1152/PSP/0062 MDS SUBSYSTEM PSP
FIX/1152/PSP/0075 PIP SUBSYSTEM PSP
FIX/1200/PSP/0083 RECMES PROCEDURE PSP
FIX/1153/PSP/0096 SRR SUBSYSTEM PSP
FIX/1153/PSP/0097 SRS SUBSYSTEM PSP
FIX/1200/PSP/0104 T26 SUBSYSTEM PSP
FIX/1100/PSP/0041 CHECKPOINT SUBSYSTEM PSP
FIX/1164/PSP/0053 INTERCEPT SUBSYSTEM PSP
FIX/1164/PSP/0058 MAC SUBSYSTEM PSP
FIX/1164/PSP/0064 MPC SUBSYSTEM PSP
FIX/1000/PSP/0105 TIMER SUBSYSTEM PSP
FIX/1164/PSP/0060 MES SUBSYSTEM PSP
FIX/1256/PSP/0066 MTCB MONITOR PSP
FIX/1153/PSP/0097 SRS SUBSYSTEM PSP
FIX/1151/PSP/0099 TEP SUBSYSTEM PSP
FIX/1161/PSP/0043 DOI SUBSYSTEM PSP
FIX/1364/PSP/0101 TEPINT BACKG. I/F SUBMOD.
FIX/1164/PSP/0100 TEPINT SUBSYSTEM PSP
FIX/1266/PSP/0074 PACKMON MONITOR PSP
FIX/3232/PSP/0033 LTUX-CRYPTO/RED & BLACK PSP
FIX/1200/PSP/0082 RDF-INIT PROCEDURE PSP
FIX/1161/PSP/0080 ROUTING CTRL PROCESS PSP
FIX/1200/PSP/0079 Q-INIT PROCEDURE PSP
FIX/1200/PSP/0054 JOURNAL PROCEDURE PSP
FIX/1200/PSP/0067 MTCB INIT PROCEDURE PSP
FIX/1256/PSP/0055 LCFH MONITOR PSP
FIX/1256/PSP/0040 APPVDU MONITOR PSP
FIX/1256/PSP/0092 SEND REPORT MONITOR PSP
FIX/1256/PSP/0073 OVERLAY MONITOR PSP
FIX/1200/PSP/0102 TEST HDB MONITOR PSP
FIX/1256/PSP/0048 FILL MTCB MONITOR PSP
FIX/1256/PSP/0052 INTASC MONITOR PSP
FIX/1154/PSP/0107 NODAL SWITCH SUBSYSTEM PSP
3 N̲E̲T̲W̲O̲R̲K̲ ̲A̲N̲D̲ ̲S̲Y̲S̲T̲E̲M̲S̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
Three functional areas are supported:
1) Message entry, storage and distribution;
2) Message routing and data switching;
3) System supervision and control.
These areas are summarized below in the context of
the software and firmware that are designed to support
their performance.
3.1 M̲E̲S̲S̲A̲G̲E̲ ̲E̲N̲T̲R̲Y̲ ̲A̲N̲D̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲ ̲(̲M̲E̲D̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲)
The MEDE supports up to 30 data terminals that are
used for entry and reception of messages.
Message preparation is interactive with prompts from
the MEDE; format errors are detected, addressees validated,
and errors annotated. Messages are prepared in a simplified
message format and clear text. After validation, messages
are available for further editing and coordination
before release.
Released messages are analyzed for routing. Messages
are queued by precedence (Flash, Rush, Immediate, Priority,
Quick and Routine) for network routing and for distribution
to local addressees.
Outgoing and incoming messages, excluding Special Handling
messages, are stored at the long term storage at the
MEDE. Special Handling messages are purged from temporary
file storage after release. Retrieval of messages from
the long term storage by authorized users is provided.
Messages will be retrieved by message identification,
SIC codes, and date/time identification.
Supervisory functions are supported that include report
reception, status checking, system control, equipment
test and diagnostics, and special security handling
of messages.
To perform these functions, the MEDE is comprised of
several software subsystems. Collectively, these subsystems
communicate with the Node software processes to support
the network function of message routing.
Figure 3.1-1 illustrates the logical structure.
3.2 N̲O̲D̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
Message routing and data switching is provided by the
Node equipment, and its associated software and firmware.
Routing of messages that are inbound to the Node requires
examination of a header that precedes the message text.
This message header, created by the originating terminal
operator, provides routing indicators and precedence
specifiers for the message that enable the Node to
direct the message either locally to the MEDE, to neighboring
Nodes, or to both the MEDE and neighboring Nodes.
Selection of neighboring Nodes to receive outbound
messages is accomplished by using an adaptive routing
algorithm that helps determine the route with minimum
expected delay. The Node requests that the Line Termination
Subsystem (firmware) encrypts the message prior to
its transmission outbound to other Nodes.
Data traffic that is switched from one external system
user to another external user is relayed at the Node
in a transparent manner, using microprocessor firmware.
Figure 3.2-1 provides a schematic of the network whose
traffic is controlled by the 8 Nodes. Each trunk line
is indicated by a two-headed arrow, indicating full-duplex
transmission between Nodes, whose identifiers are enclosed
in circles.
3.3 S̲Y̲S̲T̲E̲M̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲C̲E̲N̲T̲E̲R̲ ̲(̲S̲C̲C̲)̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
Centralized system supervision and control of the network
is provided by SCC equipment and associated software.
Network control functions include notices to Nodes
rerouting of message traffic, modifications to the
network routing plan and reconfiguration of the network.
Network supervision functions provided by SCC software
subsystems include the monitoring of Node and MEDE
equipment configurations, trunks, and operational states.
Awareness is maintained of malfunctions of network
equipment that affect network operation.
Network service functions provided by the SCC include
the maintenance of an interface connection to the NICS-TARE
network. Messages whose origination or delivery by
a MEDE, or by Naval Radio Sites, that require translation
of header information between the FIKS Simplified Message
Format and the ACP-127 format, receive this service
at the SCC.
Figure 3.3-1 provides a general view of the FIKS Network.
It indicates that there are two SCCs, each connected
to a MEDE (referred to later as the "collocated MEDE").
One SCC functions as a backup to the active SCC. The
network itself is designed to function even if both
SCCs are inactive.
3.4 O̲V̲E̲R̲V̲I̲E̲W̲ ̲O̲F̲ ̲F̲I̲K̲S̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲
Software and firmware is provided that support a common
nodal network for the exchange of narrative messages
and for the real-time transfer of data traffic.
Message exchange is supported by software subsystems
that provide interactive message entry, and automatic
distribution of messaages to terminals connected to
any FIKS Node-MEDE or to the NICS network.
Transmission of messages between network nodes is supported
by a network - independent file transfer protocol.
A modified form of the CCITT X.25 packet-switching
protocol is employed to maintain the functions of multiplexing
circuits into a network connection.
Distributed microprocessor firmware, that executes
simultaneously with and independent of other FIKS programs,
switches data streams between external user systems.
External data streams enter the FIKS network at nodal
points either on demand or on dedicated circuits. Data
traffic is multiplexed with narrative message traffic,
receiving highest priority service between network
nodes.
Firmware microprograms, that control message encryption
and decryption, are provided. Microprograms are resident
in Line Termination Subsystems, that control communication
with MEDE terminals and with Node trunk lines.
Operational availability is supported by software that
maintains, in the case of network nodes, dualredundant
"warm standby" configurations. Malfunctions, detected
in active system components that are unrecoverable,
result in the automatic transfer of control to standby
systems, which resume operation. Recovery is supported
by storing, checkpoint records of active system status.
These are then processed of the standby system, when
this becomes active.
System Control Center availability is maintained by
supporting active and standby configurations. The standby
SCC functions as a "remote backup" system, transmitting
periodic status messages to the active SCC. Switchover
of network control to the standby is under manual control
of the SCC supervisory terminal operator.
Figure 3.4-1 illustrates the concept developed to ensure
awareness of the operational availability of the Network.
3.4.1 O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
Figure 3.4.1-1 summarizes the software support that
is provided for the FIKS Network. Executive functions
that are needed to operate a System Control Center
(SCC), a Node/MEDE (N,M) a Node or a MEDE are typical
of most communication control programs, but with several
important variations.
3.4.1.1 E̲x̲e̲c̲u̲t̲i̲v̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The function of p̲r̲o̲c̲e̲s̲s̲ ̲c̲o̲n̲t̲r̲o̲l is used to allocate
CPU time to processes as a function not only of their
priority, but also of their application characteristics.
The processing is distributed on two CPUs.
Each CPU is equipped with its own process scheduling
algorithm that may be modified, if necessary, to provide
improvements in response to workloads whose input levels
change significantly from their original estimates.
This is a standard feature of the Advanced Multiprocessor
Operating System (AMOS) that includes the Kernel, Input
Output System, File Management System and Critical
Region Monitor, which are listed in Figure 3.4.1-1.
The f̲i̲l̲e̲ ̲m̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ function exhibits also a departure
from the traditional approach found in recent commumnication
network implementations. It recognizes that a primary
design goal is to minimize the elapsed time for disk
file operations, while supporting dynamic file creation,
extension and deletion for multiple interactive terminal
users and for real-time network traffic. It meets these
objectives in part by isolating, in a separate computer
system, disk file operations from execution of FIKS
application processes.
The File Management Supervisor treats the MMD9730 disk
unit as two logical devices. This allows data transfer
from the fixed-head portion of the disk to occur simultaneously
with moving-head seek operations.
Disk operations are dualized on two separate disk units.
This is accomplished by duplicating the logical file
structure and control on each of two configured disk
units. Disk dualization is supported by the Input/Output
System and the File Management System in a manner that
is transparent to application programs. Error status
returns are reported by application software to the
Error Switchover Process.
The file management function further reduces the potential
for bottlenecks to throughput by providing multiple,
logical data channels between the File Processor (FP)
and the FIKS application, or User Processor (UPs).
These channels, referred to as "DMA ports", transfer
commands and data concurrently between the FP and UP.
The FP services each transfer in a sequence whose priority
is specified for each port. The number of ports in
concurrent use is a system parameter.
The f̲a̲u̲l̲t̲ ̲d̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲e̲r̲r̲o̲r̲ ̲r̲e̲c̲o̲v̲e̲r̲y̲ function provides
on-line test and diagnostics concurrently with the
real-time functions performed by applications processes.
It attempts also to recover from CPU and other processors'
execution faults. If the fault is unrecoverable the
Watchdog is notified at the condition. The Watchdog
is otherwise notified periodically, that the system's
processor are executing normally. Finally this function
provides for recovery from system failure by recording
the occurrence of significant events that indicate
message and terminal status. These checkpoint records
are available to the standby processor during its restart
and recovery procedure.
T̲h̲e̲ ̲s̲t̲a̲r̲t̲u̲p̲ ̲a̲n̲d̲ ̲r̲e̲s̲t̲a̲r̲t̲ ̲f̲u̲n̲c̲t̲i̲o̲n̲ completes system initialization
that is unique to a specific FIKS configuration. The
system restart function is executed after a switchover
from an active to standby Node/MEDE configuration branch.
It performs the actions required to initiate the cooperative
execution of an operational set of User and File Processors.
3.4.1.2 E̲x̲e̲c̲u̲t̲i̲v̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲E̲x̲t̲e̲n̲s̲i̲o̲n̲s̲
Figure 3.4.1-1 indicates that the executive software
has been extended to support the FIKS application.
These extensions can be categorized as:
o S̲t̲a̲n̲d̲a̲r̲d̲ ̲C̲R̲8̲0̲ ̲s̲o̲f̲t̲w̲a̲r̲e̲ ̲f̲a̲c̲i̲l̲i̲t̲i̲e̲s̲,̲ which support
the management and use of logical files in any
AMOS environment;
o D̲e̲v̲i̲c̲e̲ ̲d̲r̲i̲v̲e̲r̲ ̲s̲o̲f̲t̲w̲a̲r̲e̲, developed specifically
to communicate with the terminals and lines required
of FIKS;
o Q̲u̲e̲u̲e̲ ̲a̲n̲d̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲c̲o̲n̲t̲r̲o̲l̲ ̲m̲o̲n̲i̲t̲o̲r̲s̲, which support
the concurrent flow of messages and reports through
a Node/MEDE or SCC system.
The standard software facilities are described in the
documents that were referenced in section 2, pertaining
to the I/O System, the File System and the CR80 TDX
Driver. The way that device drivers interface as software
processes to the I/O System is described in that System's
product specification.
The queue and message control monitors are unique to
the FIKS application. They are designed to interact
as necessary to manage the shared use of primary and
secondary disk memory. They recognize that FIKS subsystems
are designed to execute as queue-driven, independent
groups of software processes.
3.4.1.2.1 M̲e̲m̲o̲r̲y̲ ̲L̲a̲y̲o̲u̲t̲
Each program is allocated, at system startup time,
a contiguous data space large enough to contain its
I/O buffers and file descriptions, and other data local
to execution of the program. This results in identifying,
to the AMOS Kernel, the program and its data space
as a "process", as illustrated in Figure 3.4.1.2.1-1.
Processes in FIKS may execute the same program reentrantly,
but may not share the same process data space.
3.4.1.2.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲i̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
Memory data space that is not dedicated to local processes,
or for global reference to subsystem queues or system
data, is available for allocation during system operation.
This space is designed to be used to record the status
of messages and reports as they flow through subsystem
interfaces.
Figure 3.4.1.2.1.1-1 illustrates use of Message Transition
Control Blocks (MTCBs) to maintain system-wide awareness
of the status of messages and reports. Awareness of
message status is maintained by recording in the MTCB
the indicators listed below.
a. The message is now being served by one (or more)
specific subsystem processes.
b. The message is located on an inbound file or preparation
file, or it is stored in the Historical Data Base
at a specific address.
c. The message requires optional special security
handling.
d. The message's precedence and length, in number
of bytes, is recorded:
e. The message's security classification is recorded,
if it is being delivered to a local MEDE terminal.
In addition to these common status indicators, the
MTCB is designed to record information needed for specific
subsystem use. This includes, for example, routing
information for message switching and distribution,
and the time of day the message was enqueued for entry
into the Historical Data Base.
To control the use of Message Transition Contol Blocks,
an MTCB Monitor is used as shown in Figure 3.4.1.2.1.1-2.
It allocates fixed-length blocks from a memory pool,
assigning each block a number ("MTCB index") that is
used in queue references to messsages and reports.
It provides also as an option the creation, and subsequent
deletion, of disk files for use by multiple processes.
It ensures that a file is not deleted until the last
process that references the file's MTCB completes processing.
Section 4.3.2 describes the MTCB Monitor in more detail.
3.4.1.2.1.2 Q̲u̲e̲u̲e̲ ̲A̲c̲c̲e̲s̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
Processes that require a message or report to be delivered
to a subsystem or terminal interface request the QACCESS
monitor to perform the service. Figure 3.4.1.2.1.2-1
provides an overview of the general queue structure,
and its memory management.
An entry in a queue is an index number that references
an MTCB.
Queue server processes call QACCESS to read or remove
queue entries, by FIFO precedence, or by position in
the queue.
Some interfaces are configured with one queue for each
level of message precedence. QACCESS can be requested
to enter and retrieve entries from a single logical
queue that represents the group of precedence queues
assigned to an interface.
Other queue management services are provided by QACCESS,
including the numbering and reorganizing of queues,
as well as returning data to the requestor about the
lengths of queues.
3.4.1.2.1.3 S̲h̲a̲r̲e̲d̲ ̲M̲e̲m̲o̲r̲y̲ ̲A̲c̲c̲e̲s̲s̲
The executive software has been extended to control
multiple processes that access concurrently shared,
"critical" regions. Processes that require such access
are considered to be in one of the states shown in
Figure 3.4.1.2.1.3-1.
Critical regions are addressed by symbolic name. Memory
locations within a critical region also are addressed
symbolically, the result being an offset value relative
to the origin of the region. The memory area contained
within a region is referred to as the "variable space",
or VS.
Note that the states shown in the figure apply only
to the relation between a single region and a process.
The process may interact with several other regions
at the same time.
The meaning of the states are:
R̲e̲g̲i̲o̲n̲ ̲l̲e̲f̲t̲:̲
In this state the process has no access to the VS of
the region. A process will initially be in this state.
R̲e̲g̲i̲o̲n̲ ̲e̲n̲t̲e̲r̲e̲d̲:̲
In this state the process has access to all the variables
of the VS. Only a single process can be in this state
(in relation to a specific region) at any one time.
W̲a̲i̲t̲i̲n̲g̲ ̲t̲o̲ ̲e̲n̲t̲e̲r̲ ̲r̲e̲g̲i̲o̲n̲
The process is suspended until no other process is
in the 'region entered' state.
W̲a̲i̲t̲i̲n̲g̲ ̲t̲o̲-̲e̲n̲t̲e̲r̲ ̲r̲e̲g̲i̲o̲n̲
The process is suspended until a process leaves the
region.
The purpose of this state is to be able to wait until
the variables of the VS fullfills a wanted condition.
The transitions between the states occur at the following
events:
1: The current process calls ENTER-REGION and the
region already contains a process in the 'region
entered' state.
2: The current process calls ENTER-REGION and no process
is in the 'region - entered' state.
3: Another process (which was in the 'region entered'
state) calls LEAVE - REGION or WAIT-REGION, and
the current process is at the head of the queue
of processes waiting to enter the region and no
processes w̲e̲r̲e̲ in the state 'waiting to re-enter
region'.
4: The process calls LEAVE-REGION.
5: The current process calls WAIT-REGION.
6: Another process calls LEAVE-REGION or WAIT-REGION
and the current process is at the head of the queue
of processes waiting to re-enter the region.
The normal use of critical regions is
o to enter a region
o modify and/or inspect the variables in VS
o if the variables inspected must fullfill a
certain condition (which they do not) before
processing can continue, the process may call
WAIT-REGION. This causes the process to be
delayed until at least one other process has
been in the 'region entered' state.
o And finally to leave the region.
A region need not control a VS. If it does not, the
critical region serves as a simple synchronization
element.
3.5 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲S̲ ̲S̲U̲M̲M̲A̲R̲Y̲
Figure 3.5-1 and 3.5-2 illustrate the system configurations
that comprise Node/MEDE mainframes and SCC components,
respectively. Both system types are configured as dual
processors. Multiprocessisng is employed to execute,
with the 2 CPUs, two mixes of software processes: real-time
dependent processes and background processes.
Multicomputing is employed at the Node/MEDEs to effect
dual-redundant operation using a "warm standby" recovery
method that depends on checkpoint records of active
system status. Dual operation is assisted by the use
of the Watchdog.
SCCs are not configured redundantly, depending instead
on switchover from an Active SCC to a geographically
remote Backup SCC to effect recovery from malfunctions.
Node/MEDE configurations are equipped with data encryption/decryption
devices, referred to as "BID 1000 KS" on Figure 3.5-1.
Both the Node/MEDE and the SCC are configured with
a Line Termination Subsystem. This is a distributed
set of microprocessors that are controlled by firmware
that is programmed to service a number of applications
and protocols. Each microprocessor line termination
unit appears to the system's TDX host as a single device,
referred to as an LTUX.
The LTUX types that are configured are summarizes below.
L̲T̲U̲X̲ ̲T̲y̲p̲e̲ F̲u̲n̲c̲t̲i̲o̲n̲
a. 9600 Baud Internodal trunk interface.
b. X21 call up Trunk LTU modified for
use in NPDN connections
c. Synchronous V24/V28 Data user trunk interface
d. Asynchronous ASCII Data and terminal users
e. Asynchronous Baudot Teleprinter interface
f. 32K bps BID1000 Cryptographic synchronizer
interface
L̲T̲U̲X̲ ̲T̲y̲p̲e̲ F̲u̲n̲c̲t̲i̲o̲n̲
g. Internal SCC-Node/MEDE Interface
h. 4/2 asynchronous V24 Interface to clusters of
VDUs that include a receive
only printer.
3.6 M̲E̲S̲S̲A̲G̲E̲ ̲F̲O̲R̲M̲A̲T̲ ̲S̲U̲M̲M̲A̲R̲Y̲
The network supports two message types. One type, the
narrative message, is created by interactive terminal
users or originates from sources external to the network.
External sources include the NATO Integrated Communications
System and the Danish Navy, as mentioned in section
3.3.
The second message type is the control message. It
is used by network elements (Node, MEDE, SCC) for inter-
communication of status and control information.
These two message types are described below.
3.6.1 N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
A narrative message consists of two parts.
The visible part is that which is printed at an addressee's
terminal. The second part if the binary information
that is used to route the message between Nodes and
to control its distribution, using address numbers
at MEDEs.
The visible part consists of a Standard Message Format
(SMF) header, followed by text. Both parts are of variable
length. The visible part is stored and trans-
mitted in ASCII.
The variable-length header gives information about
precedence, origination DTG and message ID. It identifies
the originator and other addressees.
The text is the information that the originator wants
to transmit to the addressees. This includes the classification
of the informatdion and, optionally, Subject Indicator
Codes (SICs), as well as the free-form information
text itself.
The text has a minimum length equal to the length of
the classification information and a maximum length
restricted only by the limitations on size of a narrative
message.
The binary information concists of a fixed, formatted
part in front of the header called the binary header
and a variable formatted part following the text called
the address list. The binary information is, as the
name indicates, recorded in binary and is not printable.
The binary header holds information about classification,
special category, action and info precedence, release
time and a routing mask. It has further references
to Message ID, SICs and the address list to facilitate
access to these quantities.
The address list consists of coded address numbers
and AIG's for originator, destination and info addressees.
There is a one-to-one correspondance between SMF header
addresses and the addresses that are encoded in the
address list. The total length of a narrative message
is at most 9000 bytes.
Figure 3.6.1-1 illustrates the four parts of a FIKS
narrative message.
Binary Header: Node-to-node Serial No.
Message Type
Action, Info precedence
Orbit Count
Routing Mask
Message length
Message classification
Special Category
Address List Offset
Header Length
Release Time of message
Message Id Reference
SIC reference
Header : Message Id
FM designator
To addresses
INFO addresses
Text : Classification
Up to 3 SICs
Free-format, printable
character strings
Address List : Coded FM, TO, INFO
addresses (ANOs, AIGs)
FIKS NARRATIVE MESSAGE…01…Figure 3.6.1-1
3.6.2 C̲o̲n̲t̲r̲o̲l̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Control messages are defined as a set of messages exchanged
between the Supervisory Function Subsystem (SFS), the
Nodal Switch Subsystem (NSS) and the System Control
Center SCC for the purpose of network control and supervision.
Control messages are characterized by:
- They are only stored on disc temporarily i.e. for
the time of transmission through the network and
for the time of processing.
- They have no message-id and classification
- The receiver is always either the SFS, NSS or the
SCC.
- They may have any precedence including superflash.
(superflash has precedence over flash).
- Messages which are orbiting will be lost.
Control messages consist of three parts. The routing
header, the control message header and the control
information. The routing header contains information
needed for its routing through the network.
The routing header includes:
- serial No.
- message type
- precedence
- routing mask
- orbit count
- byte count.
The control message header includes information neeeded
by the receiving subsystem to identify the message.
This include:
- control record type identifier
- category identifier
- Sender-identification
- Day-time-group
The control information part contain the actual data
to be received.
4 F̲I̲K̲S̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲Y̲S̲T̲E̲M̲
The functions summarized in section 3, that support
the operation of the network, are designed to be implemented
as collections of software subsystems. Each subsystem
consists of one or more modules of program code and
associated data.
This section deals with the subsystem, their functions
and their place in the FIKS System.
4.1 N̲O̲D̲E̲/̲M̲E̲D̲E̲ ̲A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲
4.1.1 O̲v̲e̲r̲v̲i̲e̲w̲
Care has been taken to ensure that the subsystems comprising
the Node/MEDE are separable into subsystems that provide
Node functions and those that provide MEDE functions.
The visual table of contents is shown in Figure 4.1.1-1.
4.1.1.1 S̲y̲s̲t̲e̲m̲ ̲B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
The block diagram shown in Figure 4.1.1-2 illustrates
the sequence of operations that occur as messages are
inbound to the Node, and as messages are originated
by the MEDE for outbound transmission from the Node.
The diagram shows the logical relationship of the Nodal
Switch Subsystem (NSS), the three MEDE subsystems Message
Distribution (MDS), Storage and Retrieval (SRS) and
Message Entry (MES), and the Supervisory Functions
Subsystem (SFS).
Although all executive subsystems may be involved in
the processes depicted, only the three data management
subsystems are shown to emphasize the flow of data
as well as control.
