top - download
⟦d6cecf308⟧ Wang Wps File
Length: 37371 (0x91fb)
Types: Wang Wps File
Notes: Proposal
Names: »2894A «
Derivation
└─⟦3b8d69e90⟧ Bits:30005794 8" Wang WCS Floppy ( A0306A )
└─ ⟦this⟧ »2894A «
WangText
…1c……00……00……00……00…5…0a……00……00…5…0b…5…0c…5…0e…5…01…5
5…05…4…09…4…0d…4…02…4 4…05…3…09…3…0b……86…1 …02… …02… …02…
…02…
…02…APE/830425…02……02…#
FIKS-CCIS LINK
…02……02…FIKS
ENCLOSURE 3 TO CONTRACT 7Y3010
FIKS-FODCCIS-INTERFACE
Technical Specification
Enclosure 3.
LIST OF CONTENTS Page
1. SCOPE
2. DOCUMENTATION
3. SYSTEM CONCEPT
3.1 System/I/F Descriptions
3.2 Proposed Solution
4. H/W SPECIFICATION
5. SOFTWARE SPECIFICATION/DEVELOPMENT
6. FACTORY TEST, INSTALLATION & CHECKOUT
Enclosure 3.
1. S̲C̲O̲P̲E̲
This document provides a proposal for an interface between FIKS and CCIS.
The interface shall act as a batch oriented message port between CCIS and FIKS. Thus messages
are prepared in the CCIS computer and transmitted to FIKS. FIKS validates the messages. Upon
successful validation, the messages are automatically released for automatic FIKS distribution.
Too, messages may be prepared in FIKS and forwarded to CCIS.
This proposal covers all the S/W and H/W needed on the FIKS side.
Enclosure 3.
2. D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
The following documents are required to establish a firm baseline for the interfaces
1. CCITT Orange Book
Volume VIII.2
Public Data Networks - X.25
Geneva 1977
2. Royal Danish Air Force
Interface Definition for the FIKS
to CCIS Link.
April 1982
Logica Job No. 42.3607
3. FIKS DATA I/F Reference
FIX/0100/MAN/0004, Issue 2
Enclosure 3.
3. S̲Y̲S̲T̲E̲M̲ ̲C̲O̲N̲C̲E̲P̲T̲
An overview of the system concept is given on figure 3-1.
Fig. 3-1
On the FIKS side the interface is implemented as add-on to the existing FIKS baseline.
Enclosure 3.
3.1 S̲y̲s̲t̲e̲m̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
As described in the document:
Royal Danish Air Force
Interface Definition for
the FIKS - CCIS Link
Logica Job No. 42.3607
(Including Document Change Notice
done by CR A/S april 1983).
3.2 An outline is given on figure 3-2.
To handle level 1+2 of the CCIS-FIKS link a LTUX-M is used. The information field of the
HDLC frames are transferred in/out the CR80 computer via the Red TDX-bus.
A CCIS-node process is dealing with level 3+4 of CCIS-FIKS Link. Incoming CCIS-data frames
are stored in the FIKS Preparation Database to form a complete message. The process splits
an outgoing FIKS message into data frames and sends these via the TDX-system to the LTUX.
Ack's, nack's and keep alive traffic are send to CCIS.
When no traffic on the channel, each end is sending interframe time fill (frame flag 01111110).
Incoming CCIS-message are handed over to the CCIS-terminal process, where they are checked
for syntax errors before they are automatic released to the FIKS network. In case of failure
in the checking, they are enqueued into the supervisor distribution queue. A checkout of
outgoing FIKS messages is done in the same way, when they passes this process.
The control functions for the CCIS-FIKS link are implemented by an extention of the existing
SAF-process. I.e. open/close of the link.
Exchanging of messages between the FIKS-modules will be done by use of existing procedures
(MTCB's, queues). To do this it will be necessary to add new queues in the FIKS system.
Security handling will be performed similarily to other FIKS terminals
Enclosure 3
A special supervisory procedure, OPC, will be used to open the FIKS-CCIS connection. A special
supervisory procedure, CLC, will be used to close the FIKS-CCIS connection.
A new concept: A CCIS-terminal with one or more specific ANO's must be introduced, so that
the FIKS network is able to recognize a message with a CCIS-
system as destination.
A standard set of FIKS terminal queues will be allocated for use of the CCIS-FIKS link in
this way:
The printer queues Z, Y, O, P, M, R will act as CCIS output queues (messages towards CCIS).
The messages will be placed in this queues until they can be trans-
mitted to CCIS. The queues are served in order of precedence. In this way it will be possible
to monitor and supervise the CCIS-queues by using the following standard FIKS supervisory
functions.
DOT Display and update ANO
DOI Display ano index
DQS: Display Queue Status
RRT: Reroute Terminal Traffic
RET: Reestablish Terminal Traffic
RDT: Retrieve and Distribute
ROQ: Reorganize Queue
REQ: Relocate Queue
DDT: Distribute from Supervisor Queue
DSM: Distribution mode
DAL: Display alarm texts (new alarm texts as for trunks)
At SWITCHOVER at the FIKS Node/MEDE all messages in transition via the CCIS-FIKS link will
be recovered. If the link was open before switchover then the link will be opened after.
Messages to/from CCIS will be handled as other messages in the FIKS-system concerning journalizing,
statistics and storage on HDB.
Figure 3-2
Enclosure 3.
H̲A̲R̲D̲W̲A̲R̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The proposed solution is implemented by adding the
following H/W to a standard N/M baseline
o One CCIS-LTUX per interface
o Two 16K memory RAM per CCIS interface (one for
each computer branch)
o Crates, fans, power supply have to be added as
existing N/M does not provide vacant resources.
S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The proposed solution is implemented by adding the
following S/W and F/W to a standard N/M baseline:
o X.25 firmware (standard firmware)
o CCIS-Node process (new process)
o CCIS-Terminal process (new process)
o CCIS-Control module (extended SAF process)
o Various update of existing FIKS Modules to reflect
introducing of new elements.
T̲e̲s̲t̲ ̲s̲o̲f̲t̲w̲a̲r̲e̲
o CCIS-simulator for acceptance test only.
The test software will not be maintained by CR.
Enclosure 3.
M̲O̲D̲U̲L̲E̲ ̲I̲N̲T̲E̲G̲R̲A̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲,̲ ̲A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲
The development phase will end in a Factory Test where the interface will be tested against
an CCIS simulator. This test may run on a system similar to a dualized N/M acting as 2 single
branches where one branch is the FIKS test object and the other branchs is the CCIS simulator.
The test will verify all protocol levels.
BILAG 1 TIL KONTRAKT 7Y3010
FIKS - FODCCIS INTERFACE
K̲o̲n̲t̲r̲a̲k̲t̲e̲n̲s̲ ̲o̲m̲f̲a̲n̲g̲.
Bilag 1.
K̲O̲N̲T̲R̲A̲K̲T̲E̲N̲S̲ ̲O̲M̲F̲A̲N̲G̲
T̲o̲t̲a̲l̲ ̲p̲r̲i̲s̲
Den totale pris for dette tilbud er excl. optioner: D.Kr. 1.230.190,00.
D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲ ̲a̲f̲ ̲L̲i̲n̲e̲-̲I̲t̲e̲m̲s̲
Ing. Senior Management Pris
Ing. (senior ing)
--------------------------------------------------------------------
1. System design 2 1 2/3 237.599,67
I/F control do-
cumentation
2. S/W +F/W coding 2 2/3 208.108,66
+standard S/W
3. Module integra- 4 1 2/3 351.047,67
tion test. Ac-
ceptance test
4. H/W+standard F/W 433.434,00
-------------
Total 1.230.190,00
============
Bilag 1.
O̲v̲e̲r̲s̲i̲g̲t̲ ̲o̲v̲e̲r̲ ̲H̲/̲W̲ ̲p̲r̲i̲s̲e̲r̲:̲
L̲T̲U̲X̲-̲C̲C̲I̲S̲
U̲n̲i̲t̲ ̲P̲r̲i̲c̲e̲
Dkr.
Standard LTUX-M-FE 22,141.-
Standard LTUX-M-CPU 23,157.-
Additional Memory M-FE 3,250.-
Additional Memory M-CPU 5,250.-
Total Unit price LTUX-CCIS ̲5̲3̲,̲7̲9̲8̲.̲-̲
H̲a̲r̲d̲w̲a̲r̲e̲ ̲M̲a̲t̲r̲i̲x̲
Module Name Qty Unit Price Price
LTUX-CCIS 3 53,798 161,394
LTUX-Back Panel 3 1,386 4,158
16K RAM 6 35,147 210,882
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
Total 376,434
Integration Costs in test facility 12,000
T̲o̲t̲a̲l̲ ̲H̲/̲W̲ ̲C̲o̲s̲t̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲8̲8̲,̲4̲3̲4̲
S̲t̲a̲n̲d̲a̲r̲d̲ ̲F̲/̲W̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲4̲5̲,̲0̲0̲0̲
Total H/W + Standard F/W 433,434
Bilag 1.
L̲e̲v̲e̲r̲i̲n̲g̲s̲t̲i̲d̲e̲r̲
For de enkelte line items er her angivet seneste leveringsdato i antal m>neder efter underskrivelse
af kontrakt.
Line item 1 (System design) 10 mdr.
Line item 2 (Coding) 14 mdr.
Line item 3 (Acceptance test) 16 mdr.
Line item 4 (H/W) 10 mdr.
B̲I̲D̲D̲I̲N̲G̲ ̲P̲R̲O̲V̲I̲S̲I̲O̲N̲S̲
V̲a̲l̲i̲d̲i̲t̲y̲
Above costs are under assumption that:
1. Vacant resources in form of crates, fans, power supplies etc. are available.
2. The CCIS-FIKS is not to be installed on a SCC colocated Node/MEDE.
(This limitation is because of marginal decrease in spare program memory. A proposal
which include the CR80 X-AMOS system software can be given).
3. The load originating from the CCIS-system must not increase the load in the FIKS network
substantial i.e. less than 10% (200 signals of 1000 char. per hour, total input and output
per site).
4. Acceptance of this proposal is done by letter of intent before 1st April. Final contract
must be signed before 1st May.
ENCLOSURE 4 TO CONTRACT 7Y3010
FIKS - FODCCIS INTERFACE
Option: Final Integration
Enclosure 4.
S̲C̲O̲P̲E̲
The final integration test depends on the completion of the FOD-CCIS system.
When FOD-CCIS is ready the FIKS-FODCCIS interface is integrated in the FIKS system, subject
to notification by NMC to CR 2 months in advance.
T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The test must be specified as a functional test verifying the proper operation of the interface
as seen from the users point of view.
I̲N̲S̲T̲A̲L̲L̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲C̲H̲E̲C̲K̲O̲U̲T̲
1 manmonth engineer at current price per interface.
The price of a manmonth will be the current list price at CR at the time of integration.
This price must not be different from the price used for other customers.
A̲p̲p̲e̲n̲d̲i̲x̲ ̲A̲:̲ ̲ ̲L̲i̲n̲k̲ ̲L̲e̲v̲e̲l̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
The link level protocol for the FIKS to CCIS link will be an implementation of an HDLC protocol,
specifically level 2 of X25. The details of this protocol are contained in the 1980 CCITT
Recommendations
(Yellow Book).
i) As it is desirable to use the most up to date level 2 of X25 interface at the CCIS LAPB
will be used for the FIKS link. LAPB is compatible with the International Standards Organisations
(ISO) recommendations for HDLC protocols.
The FIKS implementation will act as the DCE.
The FOD-CCIS implementation will act as the DTE.
ii) Frame Format
A link level HDLC frame consists of a header and trailer enveloping an information field.
The length of the information field for the FIKS to CCIS link will be 256 Bytes:
Information 256 bytes
Flag Control 16 bit CRC
Address Flag
Total Length of Frame = 262 bytes
When a message is transmitted across the FIKS CCIS link it is divided into a set of 256 byte
units. These units are the information fields in a set of HDLC frames:
M E S S A G E
256 bytes
Frame 1
Frame 2
The information field in the HDLC frames contains no
'packet like' structure e.g. numbering.
iii) Command and Response Frames
The frame types that can be used in a LAPB implementation
of level 2 of X25 are defined in
'Yellow Book' (CCITT Recommendations 1980) but they
are also listed here for completeness.
Command and Response frames set by DTE and DCE:
F̲o̲r̲m̲a̲t̲ C̲o̲m̲m̲a̲n̲d̲ R̲e̲s̲p̲o̲n̲s̲e̲
Information I information
Supervisory RR RR receiver ready
RNR RNR receiver not ready
REJ REJ reject
Message Acknowledge
Control message, used for flow control, passed back
to the sending site when a message has been received
successfully. This message is used to acknowledge both
narrative messages, link authorisation control messages
and keep alive traffic.
Message Non Acknowledge
Control message, used for flow control, passed back
to the sending site when a message has not been received
successfully. This message is used to non-acknowledge
both narrative messages and link authorisation control
messages.
C̲C̲I̲S̲ ̲t̲o̲ ̲F̲I̲K̲S̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲
A message sent from the CCIS to FIKS will be in the
format defined in Appendix C.
When a message is received by FIKS it will be written
to the CCIS preparation database at the FIKS Node/Mede.
Only ten messages can be within the FIKS CCIS PDB (Preparation
Database) at any one time, this database will have
a length of ten Kbytes. When a message has been written
to disc, it is acknowledged and then automatically
released for delivery by the network.
Message ACK's and NACK's (flow control) have the highest
precedence of any message for transmission to FIKS.
They are therefore transmitted before narrative messages,
or link authorisation messages, these are transmitted
to FIKS on a first in first out basis. No account is
taken of the precedence of a narrative message.
If the message is not received successfully or the
PDB is full then a Message NACK (section 4.2.7) is
sent back to the CCIS. If an overlength message is
received by FIKS then a Message NACK is also transmitted
back to the CCIS and the part of the message already
received is discarded and any subsequent data for this
message ignored, processing restarts when the next
start of message is detected. An overlength message
will only occur if there is a fault on the line.
F̲o̲r̲m̲a̲t̲ C̲o̲m̲m̲a̲n̲d̲ ̲ R̲e̲s̲p̲o̲n̲s̲e̲
Unnumbered DM disconnected
SABM set async. balanced
mode
DISC disconnect
UA unnumbered ack.
CMDR command reject
iv) System Parameters
The CCITT recommendation for level 2 of X25 lays down
four parameters that have to be defined for each implementation:
(a) Maximum number of outstanding frames (N1)
This parameter is the number of sequentially
numbered information frames that the DTE or
DCE may have outstanding (i.e. unacknowledged)
at any given time. For this link it will have
the v̲a̲l̲u̲e̲ ̲7̲.
(b) Number of retransmissions (N2)
This parameter is the maximum number of transmissions
and retransmissions of a frame that can occur
following the expiry of the primary timer T1.
For this link it will have the value 2.
(c) Primary timer (T1)
If this timer expires then retransmission of
a frame may be initiated according to the procedures
described in level 2 of X25. For this link it
will be set to 5 seconds.
(d) Secondary timer (T2)
This timer is the period which effectively defines
the time for 'receiver busy'. The DTE will not
delay an acknowledge or response frame for a
command by more than the value of T2 less than
T1. The DCE will not delay the response or acknowledge
frame for a command by more than T2. For this
link the timer T2 will be set to half a second.
A̲D̲D̲R̲E̲S̲S̲I̲N̲G̲
A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲R̲e̲q̲u̲i̲r̲e̲d̲ ̲b̲y̲ ̲t̲h̲e̲ ̲C̲C̲I̲S̲
As a CCIS interfaces messages to FIKS which contain
correct addressing information then the CCIS must have
access to the information contained in the FIKS addressing
database. Each CCIS must also know its own FIKS address
at the colocated Mede. The CCIS requires this information
to construct the address list and the plain text addresses
contained in the Binary and Signal Headers. The data
held by the CCIS will be for ANO's and AIG's. An ANO
defines the relationship between a Mede addressees
identity eg. K001 and a plain text address. The plain
text address can be in English or Danish as messages
can be prepared in either language. An AIG contains
from 1 to 275 FIKS ANO's. The ANO's can be national
Danish and/or NATO. NATO addressees are always in English
even if the message is prepared in Danish. There is
a maximum of one hundred AIG's in the FIKS system,
the CCIS must also be able to reference up to 500 of
the FIKS ANO's.
The CCIS will have to be regenerated if this data has
to be updated to be kept consistent with the data held
by FIKS. It will require strict operational procedures
to ensure that the two systems are kept in line.
A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲h̲e̲l̲d̲ ̲b̲y̲ ̲F̲I̲K̲S̲
The Medes in the FIKS system connected to CCIS computers
each have at least on ANO which refers to the CCIS
link at that Mede. The software in the Medes must be
able to recognise a particular ANO as being the CCIS
link and therefore deliver messages to the CCIS. The
update mechanism must therefore be able to allocate
to a terminal identity (derived from an ANO) the attribute
of being the CCIS interface if the Mede identity is
valid.
A̲p̲p̲e̲n̲d̲i̲x̲ ̲B̲:̲ ̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Each control message that is passed between the two
systems has the same format. Each control message consists
of four parts:
i) Start of Message indicator, a string of four
ASCII characters packed into two words: "ZCZC"
ii) Binary Header, eighteen bytes of binary information:
1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲ bit
no.
Reserved for FIKS (NSS)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
5 0 1 0 7 0
NSS (res) Type Precedence
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
9 0 5 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲r̲b̲i̲t̲ ̲ ̲
Routing
25 Mask 10
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 Byte Count 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
7 0 7 0
Category Rec. Type
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
7 0 7 0
Spare Sender Id.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 LSW 0
D.T.G.
----------------------------------------
31 16
MSW
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Bit no. 0 is Least Significant Bit (LSB)
All the fields in the binary header are defined below,
in sequence, starting with the word reserved for the
FIKS NSS software:
- Word of 16 bits reserved for use by the FIKS
switching software. Will always be set to binbary
zero.
- Field of six bits reserved for use by the FIKS
switching software. Will always be set to binary
zero.
- Type, a binary value held in two bits that defines
the type of control message:
V̲a̲l̲u̲e̲ D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
2 control message
- Precedence, a binary value held in a byte. For
CCIS-FIKS control messages this always takes
the value zero (Superflash message, the highest
priority).
- Orbit Count, not used in CCIS-FIKS control messages.
This is a binary value held in six bits and
will be zero.
- Routing Mask, not used in CCIS-FIKS control
messages. This is a binary field of 26 bits
and all the bits will be set to zero.
- Byte Count, a binary value held in a word that
gives the size of the entire control message
i.e. Binary Header + Parameter Information.
The length, in bytes, is always even.
- Category, a binary value held in a byte, defining
the categogy of control message
V̲a̲l̲u̲e̲ D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
16 CCIS-FIKS control message
- Control Record Type, used in CCIS-FIKS control
messages. This is a binary value held in a byte.
V̲a̲l̲u̲e̲ D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
1 Message ACK
2 Message NACK
3 Open Link Request
4 Open Link Agreement
5 Open Link Rejection
6 Close Link
7 Keep Alive
- Sender Identity, a binary value held in a word:
V̲a̲l̲u̲e̲ D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
1 Mede A
2 Mede B
5 Mede E
6 Mede F
8 Mede H
11 Mede K
12 Mede L
14 Mede N
33 CCIS connected to Mede A
34 CCIS connected to Mede B
37 CCIS connected to Mede E
38 CCIS connected to Mede F
40 CCIS connected to Mede H
43 CCIS connected to Mede K
44 CCIS connected to Mede L
46 CCIS connected to Mede N
- Date and Time, date and time of generation held
as a long integer (32 bits) and is a binary
value of the number of seconds since 1st Jan.
1980 00h00.
iii) Up to thirty words of parameter information.
Although the sets of parameter information are
still to be defined they will be a set of ASCII
character strings terminated by an "LF" character
(ASII code decimal 10). The character strings
will always be even number of bytes in length.
If a pad character is required then it will
be a space character (ASCII code decimal 32).
iv) End of Message indicator, a string of four ASCII
characters packed into two words: "NNNN".
v) As the start of message and end of message character
string can appear in the binary sections (routing
mask and DTG) both the EOM and the byte count
is used to indicate the physical end of the
message in both the FIKS and CCIS.
A̲p̲p̲e̲n̲d̲i̲x̲ ̲C̲:̲ ̲ ̲N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲C̲C̲I̲S̲
A message held by FIKS on a PDB consists of four parts:
i) Binary Header
ii) Signal Header
iii) Signal Text ref. Appendix E
iv) Address List
The visible part, that seen by an operator, consists
of the Signal Header and Signal Text. Both parts have
variable length and are transmitted across the network
as ASCII character codes.
The Signal Header gives information about precedence,
origination DTG, message id, and it identifies the
originator and other addressees to the addressee. The
Signal Header has a length of at least 117 bytes and
a typical length of 150 bytes. This includes the classification
of the information and optionally subject indicator
codes (SIC's).
The Signal Text is the information that the originator
wishes to transmit to the addressees.
The Binary Header information consists of a fixed formatted
part at the front of the message and contains information
relating to classification, and routing. The CCIS will
interface a complete binary header to FIKS so that
FIKS can release the message to the network.
The Address List, at the end of a PDB message, consists
of coded address numbers and AIGs for the originator
and destination addressees.
The message passed from the CCIS to FIKS can be split
up into five parts, these are numbered (i) to (v) and
are described below.
i) Start of Message indicator, a string of four
ASCII characters packed into two words: "ZCZC"…86…1
…02… …02… …02… …02… …02…
ii) Binary Header information, twenty six bytes
long. The format is defined below:
1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲ ̲ bit no.
Reserved for FIKS (NSS)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
5 0 1 0 7 0
NSS (res) Type Action Prec
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
5 Orbit 0
9 Routing 0 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Mask
25 10
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Length
15 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Class Specat
7 0 7 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Address list Offset
15 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Readdress Info Prec
7 Switch 0 7 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Signal Header Length
15 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 LSW 0
Release Time
---------------------------------
31 MSW 16
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 MSG ID Reference 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 SIC Reference 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
All the fields in the binary Leader are defined below,
in sequence, starting with the word reserved for the
FIKS NSS software:
L̲e̲n̲g̲t̲h̲ D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
1 word Reserved for use by the FIKS
switching software. Will always
be set to binary zero.
1 byte Action Precedence. Message Priority
for 'TO' addressees. Routing through
the network is performed using this
priority.
C̲o̲d̲e̲ V̲a̲l̲u̲e̲ (6 lowest)
R 6 Routine
M 5 Quick
P 4 Priority
O 3 Immediate
Y 2 Rush
Z 1 Flash
2 bits Type, binary value always set to zero.
6 bits Reserved for use by the FIKS
switching software. Always set
to binary zero.
6 bits Orbit Count, binary field used by the
FIKS routing software, it will be set
by the CCIS to binary zero.
26 bits Routing Mask, binary field used by
the
FIKS routing software, it will be set
by the CCIS to binary zero.
1 word Length, a binary value which is the
length of the Binary Header + Signal
+ Address List in bytes, always even.
1 byte Special Category code (zero is not
special category)
C̲o̲d̲e̲ V̲a̲l̲u̲e̲ P̲l̲a̲i̲n̲ ̲T̲e̲x̲t̲
ATOM 1 ATOMAL
CRYS 2 CRYPTO SECURITY
EXCL 3 EXCLUSIVE
1 byte Class. The security classification
of the message.
C̲o̲d̲e̲ V̲a̲l̲u̲e̲ P̲l̲a̲i̲n̲ ̲T̲e̲x̲t̲
UKL 0 UKLASSIFICERET
UNCL 1 UNCLASSIFIED
NU 2 NATO UNCLASSIFIED
TTJ 3 TIL TJENESTEBRUG
REST 4 RESTRICTED
NR 5 NATO RESTRICTED
FTR 6 FORTROLIGT
CONF 7 CONFIDENTIAL
NC 8 NATO CONFIDENTIAL
HEM 9 HEMMELIGT
SECR 10 SECRET
NS 11 NATO SECRET
YHM 12 YDERST HEMMELIGT
TSEC 13 TOP SECRET
CTS 14 COSMIC TOP SECRET
1 word Address List Offset. A binary value
which is the length of the Binary
Header + Signal. The length is in bytes
and is always even.
1 byte Information Precedence. Message priority
for 'INFO' addressees. Queuing for
info
addressees is performed using this
priority. Codes as for Action Precedence.
Must be less than or even to action
precedence.
1 byte Readdress switch, used by FIKS software.
Set by CCIS to binary zero.
1 word Signal Header Length. The sum of the
lengths of the records that make up
the Signal Header. The last line of
the Signal Header is line 8 (class
+ specat) or if present line 9 (SIC's).
32 bits Release Time. Always set to binary
zero. This field is set up by FIKS
when the message is released for distribution
by the network.
1 word MSG ID reference. A binary value which
is the number of bytes counted from
the first byte in the Binary Header
to and including the byte before the
MSG-ID (the byte before the Mede-id
in MSG-ID).
1 word SIC reference. A binary value which
is the number of bytes counted from
the first byte in the Binary Header
to start of "SIC-line" (Line 9). ST-character
is not included. If no SIC's present
then the value is zero.
iii) The Signal Header and Text are passed to FIKS
as an ASCII character string. Two 8 bit byte
character codes are packed into one 16 bit word.
The least significant byte of the word (bits
0-7) contains the first character of the pair.
Byte 1 Byte 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
15 8 7 0 bit
Every line of the Signal Header and Text is
preceded by a word which contains a start of
line indicator (ASCII code decimal 30) and a
byte count for the line. The count (max 70.)
does not include the byte count and is up to
and including the "LF" character at the end
of the line. A line of text never contains a
"CR" character (ASCII code decimal 13) before
the "LF". The "CR" character is inserted by
the FIKS asynchronous interface when a line
of text is sent to a printer.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SOL COUNT TEXT
LF
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
-------- Count -----------------
- Line 1 Always Present: (Ref. E.3.1)
Field A - Action Precedence 1 character + space
Field B - Info Precedence 1 character + space
Field C - Date and Time
2 digits day of month )
2 digits hour of day )
2 digits minutes of hour )
1 character "Z" - GMT ) 14 chars
Space 1 character )
3 character month name )
Space 1 character )
2 digit year )
5 space characters
6 character string "MSG ID"
1 space character
Field D - 3 character 'terminal identity':
1 character Mede id.
1 character Comcenter
id.
1 character Terminal
id.
This three character
'terminal identity' will
be
the FIKS id. of the connected
CCIS computer.
3 digit cyclic sequence no. (001-999)
Fields A and B are optional either A or B must
be present. Fields C and D are mandatory.
- Line 2 Always present. From Address.
7 character string "FM....."
Variable length (max 62 bytes) text field, name
of originating addressee (Danish or English)
derived from the ANO.
- Lines 3, 4, 6 one of these lines must be present
- Lines 3, 4, 5, 6 these lines may occur multiple
times
several 'to'
or 'info' addresses,
or 'aig' with
several 'xmt's'
- Line 5 may occur multiple times whenever line
4
has been present
a) Line 3 To Address
7 character string "TO.....". Variable
length (max 62 bytes) plain text field,
name of destination addressee (Danish
or English) derived from the ANO.
b) Line 4 To AIG
7 character string "TO.....". Seven
character string identifying the AIG,
it has the format AIGnnnn where nnnn
is the range 1600-1699 and is defined.
c) Line 5 Omit Address
7 character string "XMT...." 20 character
long plain text field, name of the
addressee (Danish or English) derived
from the ANO, to which the message
should not be delivered i.e. omit address
from AIG. XMT lines occur immediately
after the TO AIG line to which they
refer.
d) Line 6 Info Address
7 character string "INFO...". Variable
length (max 62 bytes) plain text field,
name of the addressee (Danish or English)
derived from the ANO to which the message
is delivered (for information).
- Line 7 Mandatory: Separator
2 character string: "BT"
- Line 8 Mandatory: Classification
35 character long string:
Security Classification *
3 space characters
Optional:
31 character long string:
Special Category *
* Each string is composed of a set of letters
separated by space characters.
- Line 9 Optional: SIC (Subject Indicator Codes)
Five character string: "SIC.."
Up to 3 sets of 3 character SIC-codes, separated
by "/" characters
e.g. SIC AAA/BBB/CCC
- Line 10 Optional: Message Text
May occur multiple times
- Line 11 Mandatory: Separator
2 character string: "BT"
- Line 12 Optional: Internal Distribution
10 character string: "INT DIST.."
Variable length string (maximum 59 characters)
of information relating to the internal distribution
of the message. This line may occur multiple
times.
- Line 13 Mandatory: "Make even line"
Empty line (i.e. no character) or containing
a space character (decimal value 32) to make
the size of the message to an even number of
bytes.
iv) The fourth part of the message sent from the
CCIS to FIKS is the Address List. One word in
the Address List, which is binary information,
is present for each addressee contained in the
Signal Header, therefore the length of the Address
field is variable.
Each word is split into three parts:
Code (bits 13-15) value 0 - 7
Mede id (bits 8-12) value 0 - 31
Number (bits 0-7) value 0 - 255
C̲o̲d̲e̲
0 To Address
1 Info Address
2 Negative To Address
3 Negative Info Address
4 To Address AIG
5 AIG XMT
6 From Address
7 Spare
M̲e̲d̲e̲ i̲d̲
0 For AIGs
1 A
2 B
3 C Spare
4 D Spare
5 E
6 F
7 G Spare
8 H
9 I Spare
10 J Spare
11 K
12 L
13 M Spare
14 N
15 O Spare
16 P SCC P
17 Q SCC Q
18 R Spare
19 S SCC SIP for P
20 T NATO
21 U NATO
22 V NATO
23 W NATO
24 X NATO
25 Y Spare
26 Z SCC SIP for Q
27-31 Not to be used.
For AIGs the Mede id is zero.
The Number field for Medes is 0-99
The Number field for NATO is 0-255
The Number field for AIGs is 0-99
For AIGs this number represents the converted AIG
(there is a maximum of 100 AIGs in the range 1600-1699,
converted to 0-99).
Intentionally left blank
An example of an Address List is given below:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
CODE MEDE NUMBER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FM A033 6 1 33
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TO F008 0 6 08
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TO AIG1602 4 0 02
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
XMT X139 5 24 139
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
XMT A012 5 1 12
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
INFO B007 1 2 07
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
v) The Address List, and therefore
the whole message is terminated
by a string of four ASCII characters
packed into two words: "NNNN".
A̲p̲p̲e̲n̲d̲i̲x̲ ̲D̲:̲ ̲ ̲N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲r̲o̲m̲ ̲F̲I̲K̲S̲
A narrative message for transmission from FIKS to the
CCIS consists of five parts and it has basically the
same format as a narrative message transmitted from
the CCIS to FIKS, as defined in Appendix C.
i) Start of Message indicator, a string of four
ASCII characters packed into two words: "ZCZC"
ii) Binary Header information, twenty six bytes long.
The value held in the orbit count field depends
on the route the message has taken through the
FIKS network.
iii) Signal Header and Signal Text. Each line of the
signal is preceded by a sixteen bit word which
holds a start of line indicator and a byte count.
Each line will be terminated by a "LF" character
and will never contain a "CR" character.
The Signal received from FIKS will contain two
lines (ref. Appendix E.3 line 14 + 15) which
will never be present in a message sent from
the CCIS. These two lines, which define acceptance
and retrieval time have the same format and this
is defined below:
2 digits day of month
2 digits hour of day
2 digits minute of hour
1 character "Z" -GMT
Space 1 character
3 character month name
Space 1 character
2 digit year
Acceptance time is an ASCII representation of
the release time contained in the binary header.
It is the time at which the message was accepted
for distribution by the network at the originating
Node/Mede. Retrieval time is the time that the
message was stored on the Historical Database
at the Node/Mede colocated to the destination
CCIS computer.
These lines will occur as the last lines in the
signal text.
iv) Address List, binary information of variable
length.
v) End of Message indicator, a string of four ASCII
characters packed into two words: "NNNN"
The maximum size of a message sent from FIKS to the
CCIS will be 9000 bytes and the maximum line length
will be 69 printable characters.
These lines will occur as the last lines in the signal
text.
iv) Address List, binary information of variable
length.
v) End of Message indicator, a string of four ASCII
characters packed into two words: "NNNN"
The maximum size of a message sent from FIKS to the
CCIS will be 9000 bytes and the maximum line length
will be 69 printable characters.
