top - download
⟦abb5b12e7⟧ Wang Wps File
Length: 13769 (0x35c9)
Types: Wang Wps File
Notes: FIX/1161/PSP/0070
Names: »2934A «
Derivation
└─⟦5f5ac081b⟧ Bits:30006138 8" Wang WCS floppy, CR 0236A
└─ ⟦this⟧ »2934A «
WangText
…00……00……00……00……00…F…0a……00……00…F…0b…F…0e…F…01…F E…08…E…86…1 …02… …02… …02…
…02…FIX/1161/PSP/0070
…02…HFJ/821209…02……02…
NIP SUBSYSTEM PSP
…02……02…FK 7809
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 eah control message, the NIP contrains an 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̲i̲v̲i̲a̲t̲i̲o̲n̲s̲
Please refer to FIKS DATA INTERFACE, FIX/0100/MAN/0004.
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 Request 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 a SCC operator command, the 24 hour statistics record is generated
at the SCC and set 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'c
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 desplayed 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 varoius NSC modules for checkout of current status and update
as necessary.
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 (statistics, 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̲
3.2.1 A̲:̲ ̲ ̲M̲o̲d̲u̲l̲e̲s̲
The NIP module has the following interfaces:
o EVA Event registration and distribution
o RCP Routing Control Processing
o TUP Table Update Processing
o ISHRTC ISH Timer Process
o 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:
o FNC FIKS Network Configuration
o FST FIKS Status
o 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 and FIX/1200/PSP/0079.
The queues involved in the NSC processing are:
o CM Control Message Queue
o NS Network Statistics 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:
o T̲U̲P̲ ̲r̲e̲q̲u̲e̲u̲e̲:
All control messages received from the network, which contain RDF or USP updates, are
requeued into the TUP queue.
o 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 successfull) result in an Event Pseudo Message
(EMP) to be queues 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̲
o NIP updates the FST in coordination with the contents of the received control messages.
o NIP updates the FRD by receipt of control messages, reporting trunk open, close,
and(or failure changes.
F̲i̲g̲u̲r̲e̲ ̲3̲.̲2̲.̲3̲-̲1̲,̲ ̲S̲T̲R̲Q̲ ̲D̲a̲t̲a̲ ̲F̲l̲o̲w̲
The STRQ overlog 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̲r̲ ̲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̲w̲
The NIP module contrains 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 Messages (EMP's) to be queues 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, 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
requeues to NS are:
o NODE statistics
o MEDE statistics
o SIP statistics
o NODE status (with changes)
o 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, en outstnading 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 folloving polling cycle times are valid:
o every 9 minutes, NODE status is requested from each NODE.
o 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:
o The two SCC's
o The eight MEDE's
o The ten NODE's
o 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̲e̲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 lverlay.
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̲I̲C̲S̲-̲T̲A̲R̲E̲ ̲L̲i̲n̲k̲ ̲S̲t̲a̲t̲u̲s̲ ̲C̲h̲a̲n̲g̲e̲ ̲(̲N̲T̲L̲S̲)̲
Not used, CASE 1 - overlay
3.3.4.1.2.1.13 A̲N̲O̲ ̲U̲P̲D̲A̲T̲E̲ ̲A̲T̲ ̲A̲C̲T̲I̲V̲E̲ ̲S̲C̲C̲ ̲(̲A̲N̲O̲C̲)̲
o READ MTCB
o 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̲)̲
o READ MTCB
o 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̲
o UPDATE TABLE: FST, MST
PAR: MES, MDW
o 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̲
o UPDATE TABLE: FST, MST
PAR: MES, MDS
o 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̲
o UPDATE TABLE: FST, MST
PAR: MD0/MD1, MDD
o 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 (EMP'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 treshold 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 reaches
zero, it is time to request NODE status.
After reaching zero, the counters are preset to a value corresponding to the following polling
timer:
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̲s̲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.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 occured, and
the last 2 digits are a serial error location inside the individual overlays.
The first 2 digits are os 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.
…86…W …02… …02… …02… …02… …02… …02…
6. N̲O̲T̲E̲S̲
N/A.
7. A̲P̲P̲E̲N̲D̲I̲C̲E̲S̲
