top - download
⟦8a6132857⟧ Wang Wps File
Length: 64393 (0xfb89)
Types: Wang Wps File
Notes: FIX/1161/PSP/0070
Names: »3320A «
Derivation
└─⟦7680f6628⟧ Bits:30006133 8" Wang WCS floppy, CR 0288A
└─ ⟦this⟧ »3320A «
WangText
E…06…D…09…D…00…C…08…C…00…C C…07…B…08…B…0b…B…0e…B…00…B A…08…A…0b…A…0e…A…01…A @…08…@…0b…@…0e…@…0f…@…01…@…05…?…08…?…0b…?…0e…?…00…? ?…06…>…0a…>…0d…>…0f…>…02…>…06…=…09…=…0d…=…00…=
=…06…<…09…<…0d…<…02…< ;…08…;…09…;…0d…;…86…1
…02…
…02…
…02…
3320A…02…FIX/1161/PSP/0070
…02…FMK/861217…02……02…#
FIKS NIP
SUBSYSTEM
PSP
…02…BLK/840315…02…
FIKS
FIKS NIP SUBSYSTEM PSP
FIX/1161/PSP/0070
FMK FIKS Programmer
J]rgen H]g
FMK (6) APE, JJJ, IA, SL, NMN, LU
…0e… FIKS PGM. Mgr. 861217
Docu. Config.Mgr.861217…0f…
1.1
861217
…0e…
3320A/ut/rt …02…FIX/1161/PSP/0070
…02…FMK/861217…02……02…ii
FIKS NIP SUBSYSTEM PSP
…02…BLK/840315…02… FIKS
1 840315 All First Issue of Document
1.1 861217 DCN1 Changed in accordance
with Order No. 06/86.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ......................................... 5
1.1 INTRODUCTION .............................. 5
1.2 ABBREVIATIONS ............................. 6
1.2.1 General Abbreviations ............... 6
1.2.2 Special Abbreviations ............... 7
2 APPLICABLE DOCUMENTS .......................... 9
3 MODULE SPECIFICATION .......................... 10
3.1 DETAILED FUNCTIONAL DESCRIPTION ........... 10
3.1.1 Monitoring of Network ................. 10
3.1.1.1 Event Reports ..................... 10
3.1.1.2 Polled Status ..................... 13
3.1.2 Network Info .......................... 14
3.1.3 Network Status Maintenance ............ 14
3.1.3.1 Status in Memory .................. 15
3.1.3.2 Status on Hardcopy ................ 16
3.2 INTERFACE DESCRIPTION ..................... 17
3.2.1 Modules ............................... 17
3.2.2 Block Diagram Control Flow ............ 18
3.2.2.1 Input Controls .................... 19
3.2.2.2 Requeue Controls .................. 20
3.2.2.3 Processing Controls ............... 22
3.2.2.4 Routing Controls .................. 23
3.2.3 NIP Data Flow ......................... 24
3.3 PROCESSING ................................ 26
3.3.1 Network Input Processing Module
(NIP) Overview ........................ 26
3.3.2 Timed Processing (STRQ) ............... 28
3.3.3 NSC Data .............................. 29
3.3.3.1 FIKS Network Configuration
Table (FNC) ....................... 29
3.3.3.2 FIKS Status Table (FST) ........... 29
3.3.3.3 FIKS Routing Delay Table (FRD) .... 29
3.3.3.4 FIKS Routing Table (FRT) .......... 30
3.3.4 Module Description .................... 31
3.3.4.1 Network Input Processing Module
(NIP) ............................. 31
3.3.4.1.1 Introduction .................. 31
3.3.4.1.2 Module Desription ............. 31
3.3.4.1.2.1 Process NIP Description ... 31
3.3.4.1.2.1.1 Not used, CASE 1 -
overlay ............... 31
3.3.4.1.2.1.2 24 HOUR MEDE STATISTICS
(MS24) Case 2 - overlay 32
3.3.4.1.2.1.3 SCC/SCC STATUS CHANGE
(SSSC) Case 3 - overlay 32
3.3.4.1.2.1.4 NODE STATISTICS (NOST)
Case 4 - overlay ....... 33
3.3.4.1.2.1.5 NODE HOURLY REPORT(NORP)
Case 5 - overlay ....... 33
3.3.4.1.2.1.6 NODE STATUS (NSTA) Case
6 - overlay & Case 61 -
overlay ...............
3.3.4.1.2.1.7 ON-LINE DIAGNOSTIC RE- 34
SULTS (ONDR) Case 7 -
overlay ............... 37
3.3.4.1.2.1.8 MEDE STATISTICS (MEST)
Case 8 - overlay ...... 38
3.3.4.1.2.1.9 MEDE HOURLY REPORT ....
(MERP) Case 9 - overlay 38
3.3.4.1.2.1.10 USP CHANGED AT MEDE
(USPC) Case 10-overlay 38
3.3.4.1.2.1.11 SIP STATISTICS (SIST)
Case 11 - overlay .... 38
3.3.4.1.2.1.12 AIG UPDATE AT ACTIVE
Main overlay ......... 38
3.3.4.1.2.1.13 ANO UPDATE AT ACTIVE
SCC (ANOC) ........... 39
3.3.4.1.2.1.14 SSP UPDATE AT ACTIVE
SCC (SSPC) Included in
Main overlay.......... 39
3.3.4.1.2.1.15 MEDE SWITCH IN/OVER
(MESQ) Case 15-overlay 39
3.3.4.1.2.1.16 MEDE STAND-BY AVAIL/
NONAV (MESA) Case 16-
overlay............... 39
3.3.4.1.2.1.17 MEDE DISK ON/OFF (MEDI)
Case 17-overlay....... 39
3.3.4.2 Timed Processing STRQ-overlay...... 40
3.3.4.2.1 Introduction................... 40
3.3.4.2.1.1 Overlay STRQ Description... 40
3.4 DATA DESCRIPTION .......................... 42
3.4.1 Data Outside the NIP Modul ............ 42
3.4.2 Interface Description ................. 42
3.4.3 FIKS Network Config. Table (FNC) ...... 42
3.4.3.1 FIKS Network Configuration Table
(FNC) ............................. 42
3.4.3.1.1 FNC Layout..................... 42
3.4.3.1.2 FNC Description ............... 46
3.4.3.2 FIKS Status Table (FST)............ 48
3.4.3.2.1 FST Layout..................... 48
3.4.3.2.2 FST Description ............... 55
3.4.3.3 FIKS Routing Delay Table (FRD) .... 65
3.4.3.3.1 FRD Layout .................... 65
3.4.3.3.2 FRD Description ............... 68
3.4.3.4 FIKS Routing Table (FRT) .......... 70
3.4.3.4.1 FRT Layout .................... 70
3.4.3.4.2 FRT Description ............... 73
3.4.3.5 Event Pseudo (MTCB) Message (EPM) 75
3.4.3.5.1 EPM Layout .................... 75
3.4.3.5.2 EPM Description ............... 77
3.5 STORAGE ALLOCATION ........................ 81
3.6 PERFORMANCE CHARACTERISTICS ............... 82
3.7 LIMITATIONS ............................... 83
3.8 ERROR CODES/ERROR LOCATIONS ............... 84
3.9 LISTING REFERENCES ........................ 86
4 QUALITY ASSURANCE ............................. 87
4.1 QUALIFICATION TESTS ....................... 87
5 PREPARATION FOR DELIVERY ...................... 88
6 NOTES ......................................... 89
7 APPENDICES .................................... 90 - 107
1. S̲C̲O̲P̲E̲
The aim of this document is to describe the NIP-process. The NIP-modules receives all incoming
control messages from FIKS to the SCC.
1.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The NIP-module consists of one process (NIP). NIP processes all control messages received
through the CM-queue. For each control message, the NIP contains associated handling overlay.
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.2.1 G̲e̲n̲e̲r̲a̲l̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
Please refer to FIKS DATA INTERFACE REFERENCE,
FIX/0100/MAN/0004.
1.2.2 S̲p̲e̲c̲i̲a̲l̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
ALFN Alphanumeric
BIN Binary
BMSK Bit Mask
BY Byte
CM Control Message Queue
DIG Digit (0-9)
DTG Day Time Group
EPM Event Pseudo (MTCB) Message
EVR Event Registration
FNC FIKS Network Configuration
FRD FIKS Routing Delay Table
FRT FIKS Routing Table
FST FIKS Status Table
HSP Hard Copy Status Processing
IC ISH Command Queue
IOS Input/Output System
IQ Intercept Queue
ITM Interactive Terminal Monitor
LET Letter (ASCII in tables)
MEDE Message Entry Distribution Equipment
MTCB Message Transition Control Block
NC Network Command Queue
NIP Network Input Processing
NOP Network Output Processing
NS Network Statistic Queue
OCP Operator Control Processing
OIP Operator Interface Processing
OU Output Queue
PCB Process Control Block
PDB Preparation Data Base
RCP Routing Control Processing
RDF Routing Directory File
REP Report Queue
ROP Receive Only Printer
SMF Simplified Message Format
SSS SCC/SCC Status Table
TC NICS-TARE Link Control Queue
THF Terminal Handling File
TIP Timed processing
TUP Table Update Process
W WORD
2. A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1. REQUIREMENTS SPECIFICATION
FIX/0000/SPC/0002
Vol. I - III,
2. FIKS SYSTEM DESIGN SPECIFICATION
FIX/1000/DSP/0001
3. FIKS SOFTWARE INTERFACE REFERENCE
FIX/0100/MAN/0003
4. FIKS DATA INTERFACE REFERENCE
FIX/0100/MAN/0004
5. SUPPORT SOFTWARE DESIGN SPEC.
FIX/1103/DSP/0009
6. CR 80 AMOS KERNEL
CSS/302/PSP/0008
7. CR 80 AMOS, I/O SYSTEM
CSS/006/PSP/0006
3. M̲O̲D̲U̲L̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
3.1 D̲e̲t̲a̲i̲l̲e̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
3.1.1 M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲ ̲o̲f̲ ̲N̲e̲t̲w̲o̲r̲k̲
The status of the FIKS Network is monitored by the SCC through:
- Event reports sent by the elements in the network (SCC, NODE, MEDE) when a reportable
event is detected.
- Polled status reports, sent to the SCC on request by the SCC.
3.1.1.1 E̲v̲e̲n̲t̲ ̲R̲e̲p̲o̲r̲t̲s̲
Event reports can be received from SCC, NODE and/or MEDE. An event report can be subdivided
into:
o REPORTS containing large amounts of data not directly related to an event in the network
(except for requests or timers).
o EVENTS which are sent to the SCC as a result of a specific event that occurred in the
network. An EVENT will usually only contain enough data to describe the event.
A: E̲v̲e̲n̲t̲ ̲r̲e̲p̲o̲r̲t̲s̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲S̲C̲C̲:̲
Reports:
o NICS-TARE and Conversion message statistics are, once per hour, sent form the narrative
message queue program module (CIP).
Events:
o Remote SCC status is sent to the collocated SCC as soon as a change in the remote
SCC status is detected.
o Remote SCC NICS-TARE link status is sent to the collocated SCC as soon as a change
in the remote NICS-TARE link status is detected.
o File update records will be sent to the stand-by SCC whenever the active SCC makes
changes in the ANO, AIG and SSP files.
B: E̲v̲e̲n̲t̲ ̲r̲e̲p̲o̲r̲t̲s̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲N̲O̲D̲E̲:̲
Reports:
o A statistical report message is sent to the SCC for each full hour.
An hourly report message is sent to the SCC for each full hour.
Events:
o Each time the NODE detects a change in the NODE status, the complete NODE status
is sent to the SCC, and it is then up to the SCC to detect which parameters are changed.
The NODE status contains:
- Neighbor NODE status
- Trunk status (open, closed, error, etc.)
- Crypto failure indication
- Orbit error indication
- Data User routing change.
C: E̲v̲e̲n̲t̲ ̲r̲e̲p̲o̲r̲t̲s̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲M̲E̲D̲E̲
Reports:
o A statistical report message is sent to the SCC for each full hour.
o An hourly report message is sent to the SCC for each full hour.
o An on-line diagnostic result message is sent to the SCC whenever requested by the
SCC.
Events:
o It is reported to the SCC, each time a change is made in an operator security profile
at the MEDE in question.
o A message is sent to the SCC each time the MEDE detects a change in the following
status parameters:
- MEDE switch in/over
- MEDE stand-by availability
- DISK status.
3.1.1.2 P̲o̲l̲l̲e̲d̲ ̲S̲t̲a̲t̲u̲s̲
Status will be requested from the NODE (NODE status) and from the MEDE (on-line diagnostics).
The polled status ensures that an SCC, after start-up as active, will register a correct
network status and perform correct routing control with a minimum of orbit errors.
3.1.2 N̲e̲t̲w̲o̲r̲k̲ ̲I̲n̲f̲o̲
A: I̲n̲f̲o̲ ̲f̲r̲o̲m̲ ̲N̲O̲D̲E̲
REQ:
o Requests for NODE status are sent by the NIP time processing module in order to facilitate
the polling function.
B: I̲n̲f̲o̲ ̲f̲r̲o̲m̲/̲t̲o̲ ̲M̲E̲D̲E̲
INFO:
o As response to an SCC operator command, the 24 hour statistics record is generated
at the SCC and sent to the MEDE for printout.
REQ:
o Requests for on-line diagnostics are sent by the NIP time processing module (STRQ)
in order to facilitate the polling function.
3.1.3 N̲e̲t̲w̲o̲r̲k̲ ̲S̲t̲a̲t̲u̲s̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The NIP maintains some network status in memory, some is stored on disk, and the rest of
the FIKS network status is sent to a hardcopy printer.
3.1.3.1 S̲t̲a̲t̲u̲s̲ ̲I̲n̲ ̲M̲e̲m̲o̲r̲y̲
The current state of:
o SCC's
o NICS-TARE links
o NODE's
o MEDE's
are maintained in memory using the network event reports and the polled status as input.
The status in memory (FIKS STATUS) is displayed to the operator at the following locations:
o Color-TV status display contains the "Network Status"
o Upper VDU screen contains the SCC queue status
o Audible alarm horn sounds whenever an alarm has entered the FIKS status.
The FIKS status is used by various NSC modules for checkout of current status and update
as necessary.
…86…W …02… …02… …02… …02…
3.1.3.2 S̲t̲a̲t̲u̲s̲ ̲O̲n̲ ̲H̲a̲r̲d̲c̲o̲p̲y̲
One queue is assigned to each of the three Receive Only Printers of the SCC.
LOG-queue:
All events identified by DTG, event text and parameters, are queued to the LOG-queue. The
events to be logged at the NSC are:
o All incoming control messages
o All operator commands
o Missing status, requested through polling
o Generation of new routing tables.
REP-queue:
All reports containing description data (statistis, diagnostics results, etc.) are sent to
the REP queue for printout of the complete contents.
The data which can be printed on the REP printer, include:
o NODE hourly report
o MEDE hourly report
o On-line diagnostics results.
3.2 I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The NIP module has the following interfaces:
3.2.1 A: M̲o̲d̲u̲l̲e̲s̲
EVA Event registration and distribution
RCP Routing Control Processing
TUP Table Update Processing
ISHRTC ISH Timer Process
NES Network Statistical Subsystem
B: D̲a̲t̲a̲ ̲(̲f̲i̲l̲e̲s̲/̲t̲a̲b̲l̲e̲s̲)̲
The NIP contains several data tables in memory, to which one or more program modules may
make accesses.
During access of the tables in memory, the NSC modules will, by themselves, govern on access
semaphore function as necessary.
The data tables/Files involved in the NIP processing are:
FNC: FIKS network Configuration
FST: FIKS Status
FRD: FIKS Routing Delay Table
For a detailed design overview of each data table/file, please refer to Chapter 3.3.3
C: Q̲u̲e̲u̲e̲s̲:̲
The queues involved in the NIP processing are FIKS standard message queues as described in
FIX/1256/PSP/0078, FIX/1200/PSP/0079.
The queues involved in the NIP processing are:
CM: Control Message Queue
NS: Network Statistics Queue
REP: Report Queue
EV: Event Queue
NC: Network Command Queue
3.2.2 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲l̲o̲w̲
The NIP processing includes the following controls:
3.2.2.1 I̲n̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
Control messages in the CM queue will make the NIP module start processing. See Figure 3.2.2.1-1.
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲2̲.̲1̲-̲1̲,̲ ̲I̲n̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
3.2.2.2 R̲e̲q̲u̲e̲u̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
After completed processing in the NIP, some control messages are "handed" over for other
to continue processing of the same message. See Figure 3.2.2.2-1.
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲2̲.̲2̲-̲1̲,̲ ̲R̲e̲q̲u̲e̲u̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
NIP will requeue received control messages as follows:
N̲S̲ ̲r̲e̲q̲u̲e̲u̲e̲:̲
All control messages, containing information to be processed by the NES subsystem, will,
after completed processing in NIP, be requeued in the NS queue.
The control messages affected are:
- NODE statistics
- MEDE statistics
- SIP statistics
- NODE status
- MEDE USP changed
R̲E̲P̲ ̲r̲e̲q̲u̲e̲u̲e̲:
All control messages received from the network, which contains data to be printed as
hardcopy, are requeued into the REP queue.
The messages involved are:
- NODE hourly report
- MEDE hourly report
- MEDE on-line diagnostics
(only when requested by operator).
T̲U̲P̲ ̲r̲e̲q̲u̲e̲u̲e̲:̲
All control messages received from the network, which contains RDF or USP updates, are
requeued into the TUP queue.
N̲C̲ ̲r̲e̲q̲u̲e̲u̲e̲:̲
Control messages, which are sent through NSC only for logging purposes, are requeued
directly into the NC queue by the NIP module.
Messages affected are:
- 24 hours MEDE statistics.
3.2.2.3 P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
All processing performed by the NIP will (if successful) result in an Event Pseudo Message
(EPM) to be queued in the EV queue. See Figure 3.2.2.3-1.
NIP EV
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲2̲.̲3̲-̲1̲,̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
The EPM contains all necessary parameters, which together with the changed data tables FST,
FRT, RDF, and THF, will enable the functions:
- Logging
- Color-TV display update
- Upper screen VDU update
- Alarm horn activation
- Network control message generation
3.2.2.4 R̲o̲u̲t̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
The NIP subsystems will, in case of completed changes in the Delay Table (FRD), sends a message
to the RCP module in order to initiate generation of a new Routing Table (FRT). See Figure
3.2.2.4-1.
NIP
RCP
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲2̲.̲4̲-̲1̲,̲ ̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲s̲
3.2.3. N̲I̲P̲ ̲D̲a̲t̲a̲ ̲F̲l̲o̲w̲
ANO
SSS AIG
SSP
TA
NIP
FST
CM
FRD
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲3̲-̲1̲,̲ ̲ ̲N̲I̲P̲ ̲D̲a̲t̲a̲ ̲F̲l̲o̲w̲
A: D̲a̲t̲a̲ ̲I̲n̲p̲u̲t̲s̲:̲
The NIP module receives input data from table SSS and the messages in the CM queue,
see Figure 3.2.3-1.
B: D̲a̲t̲a̲ ̲O̲u̲t̲p̲u̲t̲s̲:̲
NIP performs updates of ANO, AIG, TA and SSP entries when messages containing change
records are received from the active SCC.
NIP updates the FST in coordination with the contents of the received control messages.
NIP updates the FRD by reciept of control messages, reporting trunk open, close and/or
failure changes.
The STRQ overlay will, each time a timer event is received, update the polling state of the
FST file. In case of overdue status, an EPM describing the situation will be generated
3.3 P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
3.3.1 N̲e̲t̲w̲o̲r̲k̲ ̲I̲n̲p̲u̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲N̲I̲P̲)̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The NIP module contains one process (NIP) for all incoming control messages.
Each type of control message is handled by an associated NIP overlay.
T̲h̲e̲ ̲N̲I̲P̲ ̲o̲v̲e̲r̲l̲a̲y̲s̲ ̲c̲o̲v̲e̲r̲:̲
A) Generation of Event Pseudo Message (EPM's) to be queued in the EV queue.
B) Update of FST in accordance with the incoming messages.
C) Update of FRD if trunk status changes between open, closed, and/or failed states.
D) Activate TUP-module for updating of ANO, AIG, TA, and/or SSP tables if change records
are received (from active SCC).
E) Requeue of incoming control messages:
- TUP requeue table update control messages to TUP
- NC requeue of 24 hours MEDE statistics
- REP requeue of NODE and MEDE hourly reports and on-line MEDE diagnostics
- NS requeue of all messages to be recorded in
the statistics data file. The messages requeued to NS are:
NODE statistics
MEDE statistics
SIP statistics
NODE status (with changes)
USP update at MEDE.
For details, please refer to Chapter 3.3.4.1.
3.3.2 T̲i̲m̲e̲d̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲(̲S̲T̲R̲Q̲)̲
The STRQ overlay controls the polling of the network status. The polling sequence comprises
a regular generation and transmission of requests for NODE status and MEDE diagnostics.
Each time the STRQ sends a new request, an outstanding request counter is incremented.
Each time the NIP receives a requested control message, the outstanding request counter is
reset.
A separate counter for outstanding requests of NODE status and MEDE diagnostics is maintained
in the FST file (table).
Each time one of the counters is incremented, the counter value is compared with a threshold
value.
When the counter passes the threshold value, the event will be logged.
The following polling cycle times are valid:
every 9 minutes, NODE status is requested from each NODE.
every 1 1/2 minutes, MEDE diagnostics are requested from all MEDE's.
See Paragraph 3.3.4.2 for further details.
3.3.3 N̲S̲C̲ ̲D̲a̲t̲a̲
3.3.3.1 F̲I̲K̲S̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲N̲C̲)̲
The FNC table describes how all NODE/MEDE's are interconnected via the FIKS network.
See paragraph 3.4.3.1 for further details.
3.3.3.2 F̲I̲K̲S̲ ̲S̲t̲a̲t̲u̲s̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲S̲T̲)̲
The FST table describes the current state of:
The two SCC's
The eight MEDE's
The ten NODE's
All 8 possible trunks at each NODE.
See paragraph 3.4.3.2. for further details.
3.3.3.3 F̲I̲K̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲D̲e̲l̲a̲y̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲R̲D̲)̲
The FRD table specifies, for each NODE in the network, the experienced transmission delays
between that NODE and any of its neighbor NODE's.
See paragraph 3.4.3.3. for further details.
3.3.3.4 F̲I̲K̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲R̲T̲)̲
The FRT contains one entry for each NODE in the network. Each entry will specify a primary,
secondary, and tertiary neighbor NODE to queue in order to reach the destination NODE in
the shortest possible time.
See paragraph 3.4.3.4 for further details.
3.3.4 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
3.3.4.1 N̲e̲t̲w̲o̲r̲k̲ ̲I̲n̲p̲u̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲N̲I̲P̲)̲
3.3.4.1.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The NIP module consists of one process (NIP). NIP processes all control messages received
through the CM queue. For each control message, the NIP contains an associated handling
overlay.
3.3.4.1.2 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
3.3.4.1.2.1 P̲r̲o̲c̲e̲s̲s̲ ̲N̲I̲P̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The NIP reads messages (real MTCB's and Pseudo MTCB's) from the CM queue, identifies the
messages and calls one of the following overlays:
3.3.4.1.2.1.1 N̲o̲t̲ ̲u̲s̲e̲d̲,̲ ̲C̲A̲S̲E̲ ̲1̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
3.3.4.1.2.1.2 2̲4̲ ̲H̲O̲U̲R̲ ̲M̲E̲D̲E̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲ ̲(̲M̲S̲2̲4̲)̲ ̲C̲a̲s̲e̲ ̲2̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN THE NC QUEUE
GENERATE EPM: MST, ST24H
PAR: ID
3.3.4.1.2.1.3 S̲C̲C̲/̲S̲C̲C̲ ̲S̲T̲A̲T̲U̲S̲ ̲C̲H̲A̲N̲G̲E̲ ̲(̲S̲S̲S̲C̲)̲ ̲C̲a̲s̲e̲ ̲3̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ SCEUDO MTCB:
IF COMMAND STATUS RETURNED (CMDS)
GENERATE EPM: MSM,
SMCL/SMCA
IF COMMAND REQUESTED (CMDR)
UPDATE TABLE: FST, SSTC
PAR: SSS
GENERATE EPM: MSM, SMGO
IF NEW SCCC STATUS (SCCCC)
UPDATE TABLE: FST, STTC
PAR: SSS
GENERATE EPM: MSA, SSSC
PAR: SSCNT
IF NEW NTLC STATUS (NTLSCC)
UPDATE: FST, SSTC
PAR: NLS, NLC
GENERATE EPM: MSA, SSNC
PAR: SSCNT, NTEC
IF NEW SCCR STATUS (SCCRC)
UPDATE TABLE: FST,SSTR
PAR: SSS
GENERATE EPM: MSS, SSSR
PAR: SSCNT
CASE: NEW NTLR STATUS (NTLSRC)
UPDATE: FST, SSTR
PAR: NLS, NLC
GENERATE EPM: MSA, SSNR
PAR: SSCNT, NTEC
3.3.4.1.2.1.4 N̲O̲D̲E̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲ ̲(̲N̲O̲S̲T̲)̲ ̲C̲a̲s̲e̲ ̲4̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN NS QUEUE
GENERATE EPM: MMO, MONS
PAR: ID
3.3.4.1.2.1.5 N̲O̲D̲E̲ ̲H̲O̲U̲R̲L̲Y̲ ̲R̲E̲P̲O̲R̲T̲ ̲(̲N̲O̲R̲P̲)̲ ̲C̲a̲s̲e̲ ̲5̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN REP QUEUE
GENERATE EPM: MMO, MONR
PAR: ID
3.3.4.1.2.1.6 N̲O̲D̲E̲ ̲S̲T̲A̲T̲U̲S̲ ̲(̲N̲S̲T̲A̲)̲ ̲C̲a̲s̲e̲ ̲6̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲ ̲&̲ ̲C̲a̲s̲e̲ ̲6̲l̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
IF NODE STATUS IS A REQUESTED STATUS
THEN
RESET FST, NST (NOC) AND UPDATE FST, NST (NSR) ACCORDINGLY
IF FST, NST (NSR) CHANGES FROM SRAO TO SRRA/SRRO
THEN
GENERATE EPM: TRM, RMNB
PAR: ID
COMPARE DTG OF NEWLY RECEIVED NODE-STATUS WITH DTG
OF OLD NODE- STATUS STORED IN FST, NST (NLN)
IF THE NEWLY RECEIVED NODE STATUS IS OLDER THAN
STATUS IN FST, NST (NLN)
THEN
GO TO END
COMPARE CONTENTS OF NEWLY RECEIVED NODE-STATUS WITH CONTENTS OF NODE STATUS IN FST, NST
(NLN)
IF NO CHANGES
THEN
GO TO END
QUEUE NODE-STATUS MESSAGE IN THE NS QUEUE
FOR EACH OF THE DETECTED STATUS CHANGES CALL ONE
OF THE FOLLOWING OVERLAYS TO PROCESS THE CHANGED
PARAMETERS:
CHANGE IN: NEIGHBOR NODE STATUS ( NNCH Overlay)
FOR EACH NEIGHBOR NODE STATUS CHANGED
DO:
UPDATE: FST, TST (TNS)
GENERATE EPM: MNE, NENN
(ID, NID, PAR)
CHANGE IN ̲ DATA USER STATUS (DUSC Overlay)
FOR EACH DATA USER STATUS CHANGED
DO:
UPDATE: FST, NST (NDR)
GENERATE EPM: MNE, NEDU
(ID, DUSER, PAR)
CHANGE IN: CRYPTO FAILURE (CRYF Overlay)
UPDATE: FST, NST (NCF)
GENERATE EPM: MNE, NECF
(ID, PAR)
QUEUE MESSAGE IN NS QUEUE
CHANGE IN: ORBIT ERROR (ORBE Overlay)
UPDATE: FST, NST (NOE)
GENERATE EPM: MNE, NEOE
(ID, PAR)
CHANGE IN: TRUNK STATUS (TSCH Overlay)
FOR EACH TRUNK WHERE STATUS HAS CHANGED
DO:
UPDATE TABLE: FST, TST
PAR: TRS, TSC, TTS
IF TRUNK CHANGE IN THE FOLLOWING TRANSITIONS:
- OPEN TO CLOSE
- OPEN TO DISCONNECT
- DISCONNECT TO OPEN
THEN
QUEUE MESSAGE IN NS QUEUE
UPDATE FRD ACCORDINGLY AND SEND A MESSAGE TO RCP (UTCNT Overlay)
GENERATE EPM: MTE, TENE/DI/CL/OP
(ID, TRUNK, STATUS, PAR)
3.3.4.1.2.1.7 O̲N̲-̲L̲I̲N̲E̲ ̲D̲I̲A̲G̲N̲O̲S̲T̲I̲C̲ ̲R̲E̲S̲U̲L̲T̲S̲ ̲(̲O̲N̲D̲R̲)̲ ̲C̲A̲S̲E̲ ̲7̲ ̲-̲ ̲o̲v̲e̲r̲l̲a̲y̲
CHECK THE OPERATOR REQUEST BIT: FST, MST (MDS) AND JUMP ON CASE:
CASE: OPERATOR REQUESTED OLD
CLEAR REQUEST BIT IN FST, MST (MDS)
STORE MESSAGE CONTENTS IN FST, MST (MDR)
QUEUE MESSAGE IN REP QUEUE
GENERATE EPM: MMO, MOMD (ID)
FORCE NODE POLLING WHEN NEXT MEDE
POLLING IS PERFORMED
CASE: NO OPERATOR REQUEST
RESET FST, MST (MOC) AND UPDATE FST, MST
(MDS)
IF FST, MST (MDS) CHANGES FROM DSAO TO
DSRA
THEN
GENERATE EPM: TRM, RMMB (ID)
STORE MESSAGE CONTENTS IN FST, MST (MDR)
3.3.4.1.2.1.8 M̲E̲D̲E̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲ ̲(̲M̲E̲S̲T̲)̲ ̲C̲A̲S̲E̲ ̲8̲ ̲-̲ ̲O̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN NS QUEUE
GENERATE EPM: MMO, MOMS (ID)
3.3.4.1.2.1.9 M̲E̲D̲E̲ ̲H̲O̲U̲R̲L̲Y̲ ̲R̲E̲P̲O̲R̲T̲ ̲(̲M̲E̲R̲P̲)̲ ̲C̲a̲s̲e̲ ̲9̲ ̲-̲ ̲O̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN REP QUEUE AND NS QUEUE
GENERATE EPM: MMO, MOMR (ID)
3.3.4.1.2.1.10 U̲S̲P̲ ̲C̲H̲A̲N̲G̲E̲D̲ ̲A̲T̲ ̲M̲E̲D̲E̲ ̲(̲U̲S̲P̲C̲)̲ ̲C̲a̲s̲e̲ ̲1̲0̲ ̲-̲ ̲O̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN NS QUEUE
GENERATE EPM: MDB, DBUS (ID, USERC)
3.3.4.1.2.1.11 S̲I̲P̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲ ̲(̲S̲I̲S̲T̲)̲ ̲C̲a̲s̲e̲ ̲1̲1̲ ̲-̲ ̲O̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN NS QUEUE
GENERATE EPM: MMO, MOSS (ID)
3.3.4.1.2.1.12 A̲I̲G̲ ̲U̲P̲D̲A̲T̲E̲ ̲A̲T̲ ̲A̲C̲T̲I̲V̲E̲ ̲S̲C̲C̲ ̲(̲A̲I̲G̲C̲)̲ ̲i̲n̲c̲l̲u̲d̲e̲d̲ ̲i̲n̲ ̲M̲a̲i̲n̲ ̲O̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN TUP QUEUE
3.3.4.1.2.1.13 A̲N̲O̲ ̲a̲n̲d̲ ̲T̲A̲ ̲U̲P̲D̲A̲T̲E̲ ̲A̲T̲ ̲A̲C̲T̲I̲V̲E̲ ̲S̲C̲C̲ ̲(̲A̲N̲O̲C̲)̲ ̲I̲n̲c̲l̲u̲d̲e̲d̲ ̲i̲n̲ ̲M̲a̲i̲n̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN TUP QUEUE
3.3.4.1.2.1.14 S̲S̲P̲ ̲U̲P̲D̲A̲T̲E̲ ̲A̲T̲ ̲A̲C̲T̲I̲V̲E̲ ̲S̲C̲C̲ ̲(̲S̲S̲P̲C̲)̲ ̲I̲n̲c̲l̲u̲d̲e̲d̲ ̲i̲n̲ ̲M̲a̲i̲n̲ ̲o̲v̲e̲r̲l̲a̲y̲
READ MTCB
QUEUE MESSAGE IN TUP QUEUE
3.3.4.1.2.1.15 M̲E̲D̲E̲ ̲S̲W̲I̲T̲C̲H̲ ̲I̲N̲/̲O̲V̲E̲R̲ ̲(̲M̲E̲S̲W̲)̲ ̲C̲A̲S̲E̲ ̲1̲5̲-̲o̲v̲e̲r̲l̲a̲y̲
UPDATE TABLE: FST, MST
PAR: MES, MDW
GENERATE EPM: MME, MESW/SI (ID)
3.3.4.1.2.1.16 M̲E̲D̲E̲ ̲S̲T̲A̲N̲D̲-̲B̲Y̲ ̲A̲V̲A̲I̲L̲/̲N̲O̲N̲A̲V̲ ̲(̲M̲E̲S̲A̲)̲ ̲C̲A̲S̲E̲ ̲1̲6̲-̲o̲v̲e̲r̲l̲a̲y̲
UPDATE TABLE: FST, MST
PAR: MES, MDS
GENERATE EPM: MME, MEAV/NA (ID)
3.3.4.1.2.1.17 M̲E̲D̲E̲ ̲D̲I̲S̲K̲ ̲O̲N̲/̲O̲F̲F̲ ̲(̲M̲E̲D̲I̲)̲ ̲C̲A̲S̲E̲ ̲1̲7̲-̲o̲v̲e̲r̲l̲a̲y̲
UPDATE TABLE: FST, MST
PAR: MDO/MDI, MDD
GENERATE EPM: MME, MEDN/DF (ID, DISK)
3.3.4.2 T̲i̲m̲e̲d̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲S̲T̲R̲Q̲-̲o̲v̲e̲r̲l̲a̲y̲
3.3.4.2.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The STRQ sends out requests (EPM's) for NODE status and MEDE status (on-line diagnostics).
Each time a request is produced, an outstanding request counter in FST is incremented and
compared with a threshold value.
If the threshold value is reached, the condition results in a second EPM, identifying the
alerting event.
See also chapter 3.3.4.1.2.1.6 and 3.3.4.1.2.1.7 for a description of processing of the requested
status.
3.3.4.2.1.1 O̲v̲e̲r̲l̲a̲y̲ ̲S̲T̲R̲Q̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The STRQ will prepare to receive AMOS interrupts (messages) at regular intervals.
Each time an interrupt is received, two elapse time counters will be decremented. When one
counter reaches zero, it is time to request MEDE status and when the other counter reached
zero, it is time to request NODE status.
After reaching zero, the counters are preset to a value corresponding to the following polling
timer:
- NODE STATUS: every 9 minutes
- MEDE status: every 1 1/2 minutes
I̲N̲T̲E̲R̲R̲U̲P̲T̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲ ̲(̲M̲E̲D̲E̲ ̲S̲t̲a̲t̲u̲s̲/̲N̲O̲D̲E̲ ̲S̲t̲a̲t̲u̲s̲)̲
Decrement counters
If counter is zero
then:
- preset counter
- increment FST, MST/NST (MOC/NOC)
- compare counters with threshold values
and update FST, MST/NST (MDS/NSR) accordingly
- if threshold is reached,
then
generate EPM: TRM, RMMS/RMNS
Generate EPM: TSR, SRMS/SRNS
Reserve time interrupt (ISHRTC)
3.4. D̲A̲T̲A̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
3.4.1 D̲a̲t̲a̲ ̲O̲u̲t̲s̲i̲d̲e̲ ̲t̲h̲e̲ ̲N̲I̲P̲ ̲M̲o̲d̲u̲l̲e̲
Outside the NIP module, the following tables/files are accessed:
A: FIKS STATUS TABLE (FST)
For a description of FST, please refer to Chapter 3.4.3.2.
B: FIKS ROUTING DELAY TABLE (FRD)
For a description of FRD, please refer to Chapter 3.4.3.3.
3.4.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲D̲e̲c̲r̲i̲p̲t̲i̲o̲n̲
In most of the input control message processing, the NIP module has full read and write access
to the data items involved.
The access, where semaphore update control has to be included, are:
A: Delay Table updates can only be performed if update reservation is obtained using item
UPS in Table FRD.
B: Updates in FST must be made under semaphore protection using a semaphore bit in FST,
MST/NST (MDS/NSR).
3.4.3. F̲I̲K̲S̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲N̲C̲)̲
3.4.3.1.1 F̲N̲C̲ ̲L̲a̲y̲o̲u̲t̲
TABLE:
FIKS NETWORK CONFIGURATION (FNC)
TRUNK CONNECTION
TABLE
NODE A
(TCT)
TRUNK CONNECTION
TABLE
NODE B
(TCT)
TRUNK CONNECTION
TABLE
NODE E (/S)
(TCT)
(TCT)
TRUNK CONNECTION
TABLE
NODE Q
(TCT)
TABLE:
TRUNK CONNECTION TABLE (TCT)
15 0
TRUNK CONNECTION
TRUNK 0 (TCS)
TRUNK CONNECTION
TRUNK 1 (TCS)
TRUNK CONNECTION
TRUNK 2 (TCS)
TRUNK CONNECTION
TRUNK 3 (TCS)
TRUNK CONNECTION
TRUNK 4 (TCS)
TRUNK CONNECTION
TRUNK 5 (TCS)
TRUNK CONNECTION
TRUNK 6 (TCS)
TRUNK CONNECTION
TRUNK 7 (TCS)
DATA ITEM:
TRUNK CONNECTION STATUS (TCS)
15 0
SNO TNI
3.4.3.1.2 F̲N̲C̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Data Description for Data Item: ̲T̲C̲S̲ ̲
TRUNK CONNECTION STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
TNI To-NODE-ID (Binary-ID). BIN 2
BY
The item identifies the Node where to
the trunk in question is connected.
The value is obtained through the
index table using the ASCII Node-ID
as input.
SNO Trunk Serial Number. BIN 3
BI
The item identifies one trunk out of
more trunks connected between
two Node's.
IUS In-use Indicator. BIN 1
BI
1: Trunk connected (in use)
0: Trunk never connected.
SNI Serial Number Indicator. BIN 1
BI
the item identifies a multiple
trunk.
1: Multiple trunk. Use item SNO
for complete identification.
0: Only this trunk connects the
two Node's in question.
3.4.3.2 F̲I̲K̲S̲ ̲S̲t̲a̲t̲u̲s̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲S̲T̲)̲
3.4.3.2.1 F̲S̲T̲ ̲L̲a̲y̲o̲u̲t̲
FILE:
FIKS STATUS (FST)
FIKS NETWORK STATUS TABLE
(FNS)
COLLOCATED SCC STATUS TABLE (SST)
REMOTE SCC STATUS TABLE (SST)
N/M STATUS
NODE A
(NMS)
N/M STATUS
NODE B (NMS)
N (/M) STATUS
NODE P
(NMS)
N (/M) STATUS
NODE Q
(NMS)
TABLE:
N/M STATUS (NMS)
MEDE STATUS TABLE
(MST)
NODE STATUS TABLE
(NST)
TRUNK NO. 0
TRUNK STATUS (TST)
TRUNK NO. 6
TRUNK STATUS (TST)
TRUNK NO. 7
TRUNK STATUS (TST)
TABLE:
FIKS NETWORK STATUS (FNS)
15 0
RTR
TABLE:
SCC STATUS (SST)
15 0
SSS
NLS
NLC
TABLE:
MEDE STATUS (MST)
MES
MD0
MD1
MDS
MOC
MDR
MDW
MDS
MDD
TABLE:
NODE STATUS (NST)
NSR
NOC
NDO
NDR
NOE
NCF
NLN
TABLE:
TRUNK STATUS (TST)
…0e……0e…15 0…0f……0f…
TRS
TSC
TNS
TTS
TTU TTL
3.4.3.2.2 F̲S̲T̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Data Description for Table: F̲N̲S̲ ̲
FIKS NETWORK STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
RTR Retransmission Rate. . BIN 1
W
The item contains the retransmit value
issued at the last SRR command and
used for generation of NCM No. 6.
Data Description for Table: S̲S̲T̲ ̲
SST STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
SSS SCC State. BIN 1
W
The item defines all states the SCC
can enter:
STOF: Off-line
STST: Stand-by
STSA: Stand-by to active transition.
STSO: Stand-by to off-line transition.
STAC: Active
STAS: Active to stand-by transition
STUN: Unknown
NLS NICS-TARE Link Status BIN 1
W
LSOP: Open (without errors)
LSOC: Open to close transition
LSCL: Closed (with/without errors)
LSCO: Closed to open transition
LSER: Open with errors
NLC NICS-TARE Link Error Code. BIN 1
W
codes : N/A
Data Description for Table: M̲S̲T̲-̲1̲ ̲
MEDE STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
MES MEDE State BIN 1
W
ESSA: Stand-by available
ESSN: Stand-by not available
ESMF: MEDE failure
ESMO: MEDE off-line
MDI Disk Status
MD[ disk [ status BIN 1
W
MD1 disk 1 status BIN 1
W
DIOK: Disk on-line and OK.
DIOF: Disk off-line
MDS Diagnostic Request Status. BIN 1
W
DSRA: Request answered
DSRO: Request outstanding
DSAO: Outstanding request threshold
reached
MOC Outstanding Request Counter BIN 1
W
counter
Item counts the number of out-
standing requests.
MDR Diagnostics Results.
Contains results with oldest DTG.
See applicable control message in
Data I/F Ref. FIX/0100/MAN/0004.
Data Description for Table : M̲S̲T̲-̲2̲ ̲
MEDE STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
MDW DTG of last switchover in control
message. DTG 2
W
MDS DTG of last stand-by avail/un-
avail control message. DTG 2
W
MDD DTG of last disk on/off control
message. DTG 2
W
Data Description for Table : ̲N̲S̲T̲-̲1̲ ̲
NODE STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
NSR Node Status Request Status. BIN 1
W
The item describes the state of the
polling function of Node status.
SRRA: Request answered
SRRO: Request outstanding
SRAO: Outstanding request thres-
hold reached
NOC Outstanding Request Counter. BIN 1
W
counter
Item counts the number of out-
standing requests.
NDO Data User Open Status.
open/closed BMSK 2
W
Item defines by bit mask which
data users are open/closed.
DOBOP: Data user open bit BIT 1
BI
open = 1
closed = 0
NDR Data User Route Status.
primary/secondary BMSK 2
W
Item defines by bit mask which data
users are on prime/second route.
Data Description for Table : ̲N̲S̲T̲-̲2̲ ̲
NODE STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
DRBSE: Data user on second. BIT 1
BI
on secondary route = 1
on primary route = 0
NOE Orbit Error Counter.
counter BIN 1
W
Item specifies the number of orbit
errors reported in the last re-
ceived and valid Node status.
counter = 0: no orbit error
counter # 0: orbit errors
NCF Crypto Failure Counter.
counter BIN 1
W
Item specifies the number of crypto
errors detected and reported in
the last received and valid Node
status.
counter = 0: no crypto errors
counter # 0: crypto errors
Data Description for Table : ̲N̲S̲T̲-̲3̲ ̲
NODE STATUS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
NLN Last received valid Node status.
The contents of Node status control
messages received having an "older"
DTG than the one stored, will be
processed for changed items and
stored.
See applicable control message
in Data I/F Reference for details.
FIX/0100/MAN/0004, Chapter 10.
Data Description for Table : ̲T̲S̲T̲-̲1̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
TRS Trunk Status. BIN 1
W
RSDI: Trunk is disconnected
RSCL: Trunk is closed
RSCN: Closed to NPDN open transition
RSCO: Closed for normal open tran-
sition
RSON: Trunk open as NPDN
RSNC: NPDN open to closed tran-
sition
RSOP: Trunk open normal
RSPC: Normal open to closed transition
TSC Trunk Status Change Reason. BIN 1
W
SCNC: Never connected
SCAC: After command
TNS Neighbor Node Status. BIN 1
W
NSOK: Node is OK
NSER: Node fails to drive trunk
protocol correctly
Data Description for Table : ̲T̲S̲T̲-̲2̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
TTS Trunk Queue Threshold Status. BIN 1
W
TSOF: Threshold off.
Queue length below.
Lower threshold value.
TSON: Threshold on.
Queue length above.
Upper threshold value.
Trunk Queue Lower Threshold Value.
value BIN 1
BY
TTU Trunk Queue Upper Threshold Value.
value BIN 1
BY
3.4.3.3 F̲I̲K̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲D̲e̲l̲a̲y̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲R̲D̲)̲
3.4.3.3.1 F̲R̲D̲ ̲L̲a̲y̲o̲u̲t̲
TABLE:
FIKS ROUTING DELAY (FRD)
UPDATE STATUS
(UPS)
DELAY TABLE ENTRY
NODE A
(DTE)
DELAY TABLE ENTRY
NODE B
(DTE)
DELAY TABLE ENTRY
NODE E (/S)
(DTE)
DELAY TABLE ENTRY
NODE Q
(DTE)
ENTRY:
DELAY TABLE ENTRY (DTE)
15 0
TO NODE DELAY
NODE A (TND)
TO NODE DELAY
NODE B (TND)
TO NODE DELAY
NODE E (TND)
TO NODE DELAY
NODE F (TND)
TO NODE DELAY
NODE H (TND)
TO NODE DELAY
NODE K (/S) (TND)
TO NODE DELAY
NODE L (TND)
TO NODE DELAY
NODE N (TND)
TO NODE DELAY
NODE P (TND)
TO NODE DELAY
NODE Q (TND)
DATA ITEM:
TO NODE DELAY (TND)
15 14 13 0
ND
3.4.3.3.2. F̲R̲D̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Data Description for Data Item : ̲T̲N̲D̲ ̲
TO NODE DELAY
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
ND Node Delay. BIN 14
BI
The item represents the delay
experienced between Node of entry
(DTE) and Node of current (TND).
The value is assumed positive and
can rate 0 through 999.
DCU Delay Calculated Unuseable. BIN 1
BI
The item is used during routing
table calculations to indicate a
simulated trunk failure which will
make delay value infinite.
1: Simulated trunk failure.
0: Simulated trunk is OK.
DNU Delay Value no in Use BIN 1
BI
The item is used to indicate trunks
not in use and trunks with hard
errors.
1: Not in use/not trunk failure
0: Trunk in use and OK.
3.4.3.4 F̲I̲K̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲T̲a̲b̲l̲e̲ ̲(̲F̲R̲T̲)
3.4.3.4.1 F̲R̲T̲ ̲L̲a̲y̲o̲u̲t̲
L̲A̲Y̲O̲U̲T̲ ̲O̲F̲:̲ ̲F̲I̲K̲S̲ ̲R̲O̲U̲T̲I̲N̲G̲ ̲T̲A̲B̲L̲E̲ ̲(̲F̲R̲T̲)̲
UPDATE STATUS (UPS)
ROUTE TABLE ENTRY
NODE A (RTE)
ROUTE TABLE ENTRY
NODE B (RTE)
ROUTE TABLE ENTRY
NODE E(/S)
(RTE)
ROUTE TABLE ENTRY
NODE F
(RTE)
ROUTE TABLE ENTRY
NODE Q
(RTE)
LAYOUT OF
ENTRY:
ROUTE TABLE ENTRY (RTE)
…0e……0e…15 0…0f……0f…
QUEUE ROUTE
TO NODE A (QRO)
QUEUE ROUTE
TO NODE B (QRO)
QUEUE ROUTE
TO NODE E(/S) (QRO)
QUEUE ROUTE
TO ROUTE Q (QRO)
DATA ITEM:
QUEUE ROUTE (QRO)
SQC PQC
spare TQC
3.4.3.4.2 F̲R̲T̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Data Description for DATA ITEM: ̲Q̲R̲O̲ ̲
QUEUE ROUTE:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
PQC Primary Queue Code. ASCII 1
BY
Contains Primary Neighbor NODE-ID.
Values:
"A, B, E, F, H, K, L, N, P, Q"
NDUM: no route open
SQC Secondary Queue Code. ASCII 1
BY
Contains Secondary Neighbor NODE-ID.
Values: as for PQC
TQC Tertiary Queue Code. ASCII 1
BY
Contains Tertiary Neighbor NODE-ID.
Values: as for TQC
3.4.3.5 E̲v̲e̲n̲t̲ ̲P̲s̲e̲u̲d̲o̲ ̲(̲M̲T̲C̲B̲)̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲E̲P̲M̲)̲
3.4.3.5.1 E̲P̲M̲ ̲L̲a̲y̲o̲u̲t̲
TABLE:
EVENT PSEUDO MESSAGE (EPM)
MTH
EMI
PA0
PA1
PA2
PA3
DTL
DATA ITEM:
EVENT ID (EVI)
MTY SCA MCC
3.4.3.5.2 E̲P̲M̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Data Description for Table: E̲P̲M̲-̲1̲ ̲
EVENT PSEUDO MESSAGE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
MTH MTCB Header BIN 1
W
The item contains various parameters
to be used by the MTCB monitor. One
of the parameters defines whether it
is a real MTCB (with associated data
in a file) or a psudoe MTCB.
See FIX/0100/MAN/0004 (DATA I/F),
Chapter 7.1 for details.
EMI Event pseudo Message ID. BIN 1
W
The item gives a complete iden-
tification of the event.
See Data Item EVI for details.
PA] Parameter [. BIN 1
W
This item is available for each
event to carry a event parameter
as desired.
PA1 Parameter 1. BIN 1
W
Similar to PAR[
PA2 Parameter 2 BIN 1
W
Similar to PAR[
PA3 Parameter 3 BIN 1
W
Similar to PAR[
…86…1 …02… …02… …02…
…02… …02…
Data Description for Table: E̲P̲M̲-̲2̲ ̲
EVENT PSEUDO MESSAGE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
DTL DTG Log Time BIN 2
W
The item specifies the DTG valid
at the time of generation of the
Event Pseudo Message.
Data Description for Data Item: E̲V̲I̲ ̲
EVENT ID
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
MTY Message Type BIN 4
BI
The item is used to identify the
category of events to be logged at
the SCC.
TYME: Incoming control message
event.
TYCE: Operator command event.
TYNL: NICS-TARE link event.
TYTE: Timed event.
TYST: Statistical event.
SCA Sub-category. BIN 4
BI
This item is used to divide each
of the above message types into
sub-categories.
MCC Message/Command Code BIN
l
BY
This item identifies an event
within each of the above described
sub-categories.
3.5 S̲t̲o̲r̲a̲g̲e̲ ̲A̲l̲l̲o̲c̲a̲t̲i̲o̲n̲
No special provisions apply.
3.6 P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
N/A
3.7 L̲i̲m̲i̲t̲a̲t̲i̲o̲n̲s̲
None.
3.8 E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲/̲E̲R̲R̲O̲R̲ ̲L̲O̲C̲A̲T̲I̲O̲N̲S̲
The Error Codes encountered will be the general Monitor - and system - error codes.
The Error Locations are constructed in the following manner:
The first 2 digits in the HEX value indicates in which overlay the error has occurred, and
the last 2 digits are a serial error location inside the individual overlay.
The first 2 digits are as follows:
Main-overlay # 10
Case 0-overlay # 00
Case 1-overlay # 11
Case 2-overlay # 12
Case 3-overlay # 13
Case 4-overlay # 14
Case 5-overlay # 15
Case 6&61-overlay # 16
Case 7-overlay # 17
Case 8-overlay # 18
Case 9-overlay # 19
Case 10-overlay # 20
Case 11-overlay # 21
Case 15-overlay # 25
Case 16-overlay # 26
Case 17-overlay # 27
TSCH-overlay # 28
UTCNT-overlay # 29
ORBE-overlay # 30
CRYF-overlay # 31
DUSC-overlay # 32
STRQ-overlay # 33
NNCH-overlay # 08
Main-overlay
(call of procedure GET-CASE) # 07
All-overlays on return to Main # 34
3.9 L̲i̲s̲t̲i̲n̲g̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
Refer to SCCLDD and S/W library FIXLIB.
4 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
4.1 Q̲u̲a̲l̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲e̲s̲t̲s̲
Refer to System Tests S050, S060, S070, S080 and S090.
5 P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲S̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
Please refer to SCCLDD.
6 N̲O̲T̲E̲S̲
N/A
7 A̲P̲P̲E̲N̲D̲I̲C̲E̲S̲
A̲P̲P̲E̲N̲D̲I̲X̲ ̲A̲
E̲V̲E̲N̲T̲S̲ ̲P̲S̲E̲U̲D̲O̲ ̲M̲T̲C̲B̲ ̲(̲E̲P̲M̲)̲
EVENT PSEUDO MESSAGE
CASE: S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
MTH
TYME MST MCC
ID
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code. BIN 8 BI
S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲E̲v̲e̲n̲t̲s̲:̲
ST24H: 24 H statistical generated.
ID MEDE-ID of receiver MEDE ASCII 1 BY
EVENT PSEUDO MESSAGE
CASE: SCC Mode Control
MTH
TYME MSM MCC
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code. BIN 8 BI
S̲C̲C̲ ̲M̲o̲d̲e̲ ̲C̲h̲a̲n̲g̲e̲ ̲R̲e̲p̲o̲r̲t̲s̲:̲
SMCL: Mode Change Complete
SMCA: Mode Change Cancelled
SMGO: "Go Active" Directive
EVENT PSEUDO MESSAGE
CASE: S̲C̲C̲ ̲S̲t̲a̲t̲u̲s̲
MTH
TYME MSS MCC
SSCNT
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code BIN 8 BI
S̲C̲C̲ ̲o̲r̲ ̲N̲/̲T̲ ̲L̲i̲n̲k̲ ̲S̲t̲a̲t̲u̲s̲ ̲C̲h̲a̲n̲g̲e̲s̲:̲
SSSC: Collocated SCC Status Change
SSSR: Remote SCC Status Change
SSNC: Collocated N/T Link Status Change
SSNR: Remote N/T Link Status Change
SSCNT SCC/NTL Status. BIN 1 W
The item defines the new state of either
SCC or N/T Link. See item SSS and NLS in
Table SST for details.
EVENT PSEUDO MESSAGE
CASE: M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲ ̲R̲e̲p̲o̲r̲t̲s̲
MTH
TYME MMO MCC
ID
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code BIN 8 BI
T̲y̲p̲e̲ ̲o̲f̲ ̲R̲e̲p̲o̲r̲t̲ ̲R̲e̲c̲e̲i̲v̲e̲d̲
MONS: NODE Statistics
MONR: NODE Report (hour)
MOMS: MEDE Statistics
MOMR: MEDE Report (hour)
MOMD: MEDE Diagnostics
MOSS: SIP Statistics
EVENT PSEUDO MESSAGE
CASE: D̲a̲t̲a̲ ̲B̲a̲s̲e̲ ̲U̲p̲d̲a̲t̲e̲
MTH
TYME MDB MCC
ID
USERC
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code BIN 8 BI
D̲a̲t̲a̲ ̲C̲h̲a̲n̲g̲e̲d̲ ̲f̲r̲o̲m̲ ̲M̲E̲D̲E̲ ̲i̲n̲ ̲t̲h̲e̲ ̲N̲e̲t̲w̲o̲r̲k̲:̲
DBUS: USP updated at MEDE
DATA DESCRIPTION OF EPM: D̲a̲t̲a̲ ̲B̲a̲s̲e̲ ̲U̲p̲d̲a̲t̲e̲
ITEM: DESCRIPTION: TYPE: SIZE:
ID MEDE/NODE/ANO - ID ASCII 1 BY
The item designates MEDE and NODE-ID's
M̲C̲C̲:̲ ̲I̲D̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
DBUS: MEDE-ID of MEDE where USP was updated
DATA DESCRIPTION OF EPM: D̲a̲t̲a̲ ̲B̲a̲s̲e̲ ̲U̲p̲d̲a̲t̲e̲
ITEM DESCRIPTION: TYPE: SIZE:
USERC USER - ID ASCII 4 BY
The item identifies a user (operator)
who performed the update.
EVENT PSEUDO MESSAGE
CASE: M̲E̲D̲E̲ ̲E̲v̲e̲n̲t̲s̲
MTH
TYME MME MCC
ID
DISK
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code. BIN 8 BI
M̲E̲D̲E̲ ̲E̲v̲e̲n̲t̲ ̲C̲o̲d̲e̲:̲
MESW: Switchover
MESI: Switchin
MEAV: Stand-by available
MENA: MEDE Failure
MEDN: Disk on
MEDF: Disk off
DATA DESCRIPTION FOR EPM: M̲E̲D̲E̲ ̲E̲v̲e̲n̲t̲s̲
ITEM: DESCRIPTION: TYPE: SIZE:
ID MEDE -ID. ASCII 1 BY
Specifies the ID of the MEDE reporting the
event change.
DISK DISK Number. BIN 1 BY
For the values MEDN, MEDF (of MCC), this
item specifies how many disks are available
at the reporting MEDE after changed status.
EVENT PSEUDO MESSAGE
CASE: T̲r̲u̲n̲k̲ ̲E̲v̲e̲n̲t̲s̲
MTH
TYME MTE MCC
ID
TRUNK
STATUS
PAR
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCO Message/Command Code BIN 8 BI
T̲r̲u̲n̲k̲ ̲M̲o̲d̲e̲ ̲C̲h̲a̲n̲g̲e̲ ̲C̲o̲d̲e̲:̲
TEDI: Trunk disconnected
TECL: Trunk closed
TEOP: Trunk open
ID NODE - ID of reporting NODE ASCII 1 BY
Data Description for EPM: T̲r̲u̲n̲k̲ ̲E̲v̲e̲n̲t̲s̲ ̲-̲ ̲1̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
TRUNK Trunk Number. BIN 1
BY
The item gives the NODE local trunk
number (in binary) when a change has
occurred.
STATUS Trunk Status Change Code. BIN
l
W
The item amplifies the trunk mode change
code (item MCC) in the following way:
- For MCC = TEDI
TENC: Trunk never connected
TEHE: Disconnected after
hard error
- For MCC = TECL
TECM: Closed after command
- For MCC = TEOP
TENP: NPDN/Normal change
TETH: Threshold change
TESE: Soft errors
TERE: Retransmit rate exceeded.
Data Description for E̲P̲M̲: T̲r̲u̲n̲k̲ ̲E̲v̲e̲n̲t̲s̲ ̲-̲ ̲2̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
PAR Open Trunk Status After Change. BIN 1
W
The item specifies the status of
the open (and operational) trunk.
The item (only valid for MCC = TEOP)
is depending on the value of item
STATUS in the following way:
- For STATUS = TENP:
ON: Trunk open as NPDN
OFF: Trunk normal open
- For STATUS = TETH:
ON: Threshold exceeded
OFF: Queue below threshold
- For STATUS = TESE:
PAR specifies the number of soft
errors occurred since last report
from same trunk.
- For STATUS = TERE:
PAR specifies the number of times
the
transmission rate has been exceeded
since last report from same trunk.
EVENT PSEUDO MESSAGE
CASE: N̲O̲D̲E̲ ̲E̲v̲e̲n̲t̲s̲
MTH
TYME MNE MCC
ID
NID
DUSER
PAR
DTL
ITEM: DESCRIPTION: TYPE:
SIZE
MCC Message/Command Code
BIN
8
BI
N̲O̲D̲E̲ ̲R̲e̲p̲o̲r̲t̲e̲d̲ ̲E̲v̲e̲n̲t̲s̲:̲
NENN: Neighbor NODE status change
NEDU: Data user status change
NEOE. Orbit errors
NECF: Crypto failure
ID NODE - ID of Reporting NODE ASCII
1
BY
NID NODE - ID of Neighbor NODE to Reporting ASCII
1
BY
NODE. Only valid for MCC = NENN.
EVENT PSEUDO MESSAGE
CASE: T̲i̲m̲e̲d̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲q̲u̲e̲s̲t̲s̲
MTH
TYTE TSR MCC
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code. BIN 8 BI
S̲t̲a̲t̲u̲s̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲C̲o̲d̲e̲:̲
SRNS: NODE status request.
SRMS: MEDE status (OLD) request.
EVENT PSEUDO MESSAGE
CASE: R̲e̲q̲u̲e̲s̲t̲e̲d̲ ̲D̲a̲t̲a̲ ̲M̲i̲s̲s̲i̲n̲g̲
MTH
TYTE TRM MCC
ID
DTL
ITEM: DESCRIPTION: TYPE: SIZE:
MCC Message/Command Code BIN 8 BI
O̲v̲e̲r̲d̲u̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲C̲o̲d̲e̲:̲
RMNS: NODE status overdue (outstanding
request counter threshold
exceeded).
RMMS: MEDE status (OLD) overdue (out-
standing request counter thres-
hold exceeded).
DATA DESCRIPTION FOR EPM: R̲e̲q̲u̲e̲s̲t̲e̲d̲ ̲D̲a̲t̲a̲ ̲M̲i̲s̲s̲i̲n̲g̲
ITEM: DESCRIPTION: TYPE: SIZE
ID NODE/MEDE-ID. ASCII 1 BY
The item identifies the NODE or MEDE from where
status is missing.
Data Description for EPM: NODE Event-1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ITEM: DESCRIPTION: TYPE: SIZE:
================================================================
DUSER DATA USER ID at reporting NODE. BIN 1
W
Only valid for MCC = NEDU.
PAR NODE Event Parameter. BIN 1
W
The item specifies more about the
NODE event reported:
- For MCC = NENN:
OK: Neighbor NODE is OK.
ERROR: Neighbor NODE fails to
drive data link control
correctly.
- For MCC = NEDU:
PRIM: Data user is on primary
route
SEDC: Data user is on secon-
dary route
- For MCC = NEOE:
PAR counts the number of orbit
errors occurred since last
reported.
- For MCC = NECF:
PAR counts the number of
crypto failures detected
since last report.
