top - download
⟦3a3c0cdf0⟧ Wang Wps File
Length: 39569 (0x9a91)
Types: Wang Wps File
Notes: AIR CANADA PROPOSAL
Names: »2035A «
Derivation
└─⟦4363da632⟧ Bits:30006256 8" Wang WCS floppy, CR 0156A
└─ ⟦this⟧ »2035A «
WangText
…00……00……00……00…<…0a……00……00…<…0b…<…06…;…02…:…0f…:…86…1 …02… …02… …02… …02…
CHAPTER 4
Page #
DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982
L̲I̲S̲T̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲ Page
4 NETWORK OPERATIONS AND INTERFACES ........... 5
4.1 Introduction ................................. 6
4.2 General Network Operation .................... 8
4.2.1 Network Management Overview .................. 8
4.2.1.1 Network Definition ........................... 8
4.2.1.2 Downline Loading.............................. 9
4.2.1.3 Statistics Processing ........................ 9
4.2.1.4 Charging and Billing ......................... 9
4.2.1.5 Query Language ............................... 9
4.2.1.6 Report Generation ............................ 10
4.2.1.7 Modelling .................................... 10
4.2.1.8 Program Development .......................... 10
4.2.1.9 SW Configuration Control ..................... 10
4.2.2 Network Supervision .......................... 11
4.2.2.1 Network Definition ........................... 11
4.2.2.2 Network Initialization ....................... 12
4.2.2.3 Transport Network Control..................... 12
4.2.2.4 External Resource Control .................... 12
4.2.2.5 Session Control .............................. 13
4.2.2.6 Recovery Procedures .......................... 13
4.2.3 Protected Message Switching Service .......... 14
4.2.3.1 Guaranteed Message Delivery ................. 14
4.2.3.2 Message Storage............................... 14
4.2.3.3 Automatic Routing of Messages ................ 15
4.2.3.4 Adaption to External Networks ................ 15
4.2.3.5 Repair of Faulty Messages .................... 15
4.2.3.6 Logging and Journalization of PMS Traffic..... 15
4.2.4 User Services ................................ 16
4.2.4.1 Sign-On ...................................... 16
4.2.4.2 User Communication ........................... 16
4.2.4.3 Handling fo PMS Traffic ...................... 16
4.2.4.4 Status Awareness ............................. 16
4.3 Operator Categories .......................... 17
4.3.1 Network Administrator ........................ 17
4.3.2 Network Supervisors .......................... 18
4.3.3 Local Office Manager ......................... 19
4.3.4 Field Technician/Engineer .................... 19
4.3.5 Network Users ................................ 19
4.4 Work Position Description .................... 20
4.4.1 Network Administrator Position ............... 20
4.4.2 Network Supervisor Position................... 20
4.4.3 Electronic Mail Operator Position............. 23
4.4.4 Engineering Position.......................... 24
L̲I̲S̲T̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲ Page
4.5 Security System.............................. 25
4.5.1 General Security Aspects..................... 25
4.5.2 Distribution of Security..................... 25
4.5.3 Sign-On Security System Procedure............ 27
4.5.4 Mainframe Access Services.................... 27
4.5.5 Test System Access........................... 29
4.5.6 Network Integrity............................ 29
4.6 Operations Command Summary................... 30
4.6.1 Local Initialization Subsystem Commands...... 35
4.7 Network Management........................... 36
4.7.1 Network Management Operation and Interfaces . 36
4.7.2 NMH Operators Positions...................... 37
4.7.3 Distribution of Network Management........... 37
4.7.4 Operator Categories.......................... 37
4.7.5 Network Management Applications.............. 38
4.7.5.1 Network Definition........................... 38
4.7.5.2 Down Line Loading............................ 40
4.7.5.3 Statistics and Billing....................... 40
4.7.5.4 Query Language and Report Generation......... 41
4.8 Network Control and Supervision.............. 42
4.8.1 Network Control Interfaces and Operations.... 42
4.8.2 NCC Operator positions....................... 43
4.8.3 Distribution of Network Control.............. 43
4.8.4 Operator Categories.......................... 43
4.8.5 Network Control Command and Functions........ 44
4.8.5.1 Network Definition........................... 44
4.8.5.2 Network Initialization....................... 45
4.8.5.3 Transport System Control..................... 47
4.8.5.3.1 Link Management.............................. 48
4.8.5.3.2 Virtual Circuit Management................... 49
4.8.5.3.3 Resource Utilisation Control................. 50
4.8.5.4 External Resource Management................. 52
4.8.5.4.1 ICC Control Commands......................... 53
4.8.5.4.2 Device Control Commands...................... 56
4.8.5.4.3 Synchronization of Network Appearances....... 58
4.8.5.4.3.1 Management of IBM Host................... 59
4.8.5.4.3.2 Management of Univac 1100 host........... 60
4.8.5.5 Conversation Control......................... 60
4.8.5.6 Session Control.............................. 62
4.8.6 Alarms and Event Handling.................... 63
4.8.6.1 Events....................................... 63
4.8.6.2 Presentation................................. 64
4.8.6.3 Actions to be taken due to Event occurance... 65
4.8.7 Administration............................... 65
4.8.8 Test Control................................. 67
4.8.9 Statistics and Report Generation............. 67
4.8.9.1 Statistics Commands.......................... 67
4.8.9.2 Report Generation Commands................... 69
LIST OF CONTENTS Page
4.8.10 Type B Traffic Control....................... 69
4.8.10.1 TDP Printer Commands......................... 69
4.8.10.2 Type B traffic delivery control.............. 70
4.8.11 User Services................................ 71
4.8.11.1 Sign-in Messages............................. 71
4.8.11.2 Broadcast Message Facility................... 71
4.9 Electronic Mail Host Operations ............. 74
4.9.1 Electronic Mail Host Operations and Interface 74
4.9.2 EMH Operator Positions....................... 74
4.9.3 Distribution of EMH Control.................. 75
4.9.4 Operator Categories ......................... 75
4.9.5 EMH Functions................................ 76
4.9.5.1 Direct Printer Traffic Delivery Handling..... 76
4.9.5.2 Protected Message Switching.................. 77
4.9.5.2.1 Guaranteed Automatic Delivery................
77
4.9.5.2.2 Longterm Storage of Messages for Retrieval...
78
4.9.5.2.3 Message Entry Handling.......................
79
4.9.5.2.4 Message Repair Functions.....................
81
4.9.5.2.5 Logging, Journalization and Statistics.......
82
4.9.5.3 EMH Supervisory Functions ................... 83
4.9.5.3.1 Table Handling ..............................
83
4.9.5.3.2 Delivery Control .............................
84
4.9.5.3.3 Alarm Supervision ............................
85
4.9.5.3.4 Storage Maintenance ..........................
85
4.9.5.4 Electronic Mail Services ..................... 85
4.9.6 Network Gateways ............................. 86
4.10 Nodal Site Operations and Interfaces......... 87
4.10.1 Nodal Control Operations..................... 87
4.10.2 Node Operator Position....................... 87
4.10.3 Operator Categories.......................... 87
4.11 Statistics and Accounting.................... 88
4.11.1 Statistics Collection........................ 88
4.11.2 Statistics Processing and Reports ........... 91
4.11.2.1 Traffic Statistics Report.................... 91
4.11.2.2 Service Availability Report................. 92
4.11.2.3 Host Status Report........................... 92
4.11.2.4 ARINC/SITA Report............................ 93
4.11.2.5 Terminal Routing Status Report............... 93
4.11.2.6 System Queue Status Report................... 93
4.11.2.7 Node Status Report........................... 94
4.11.2.8 Total Message Statistics Report.............. 94
4.11.2.9 Terminal Response Time Report................ 95
4.11.2.10 Terminal/Line Status Report..................
95
4.11.3 Billing Data................................. 96
4.12 User Services................................ 97
4.12.1 Sign-in/Sign-off............................. 97
4.12.2 User Status Awareness........................ 98
4.12.3 TDP Printer and Type B Traffic Controls...... 99
4.12.4 PMS Retrieval Command........................ 99
4.12.5 Terminal to Terminal Communication........... 101
L̲I̲S̲T̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲ Page
4.13 Testing ..................................... 102
4.13.1 Fault Detection and Isolation Aids........... 102
4.13.1.1 Test Functions............................... 103
4.13.1.2 Trace Facilities............................. 105
4.13.2 Test and Integration of New Facilities ...... 106
4.14 Recovery and Redundancy...................... 107
4.14.1 Redundancy .................................. 107
4.14.1.1 H/W Redundancy .............................. 107
4.14.1.1.1 Node Redundancy ............................. 107
4.14.1.1.2 EMH Redundancy .............................. 107
4.14.1.2 Checkpointing ............................... 108
4.14.1.2.1 Recovery/Restart ............................ 108
4.14.1.2.2 Recovery Level .............................. 108
4.14.1.3 Switching Redundant Elements ................ 110
4.14.1.3.1 PU Switchover ............................... 110
4.14.1.3.2 Mirrored Disc Handling ...................... 111
4.14.1.3.3 Supra Bus Switching ......................... 112
4.14.1.4 Geographical NCC Backup ..................... 112
4.14.2 Recovery .................................... 116
4.14.2.1 Node Failure ................................ 116
4.14.2.2 Host Access Synchronization upon Node
Failure ..................................... 117
4.14.2.3 Host Access Synchronization upon Host
Failure ..................................... 117
4.14.2.4 EMH Failure ................................. 118
4.14.2.5 NCC Failure ................................. 118
4.14.2.6 External Resource Failure ................... 118
4.14.2.7 Link Failure ................................ 119
4.14.2.8 Multiple Link Failure with Loss of
Connectivity ................................ 119
4. N̲E̲T̲W̲O̲R̲K̲ ̲O̲P̲E̲R̲A̲T̲I̲O̲N̲S̲ ̲A̲N̲D̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
The scope of this chapter is to present a comprehensive
view of the operations aspect of ACDN.
The description covers all major network operations
required for long term management and minute to minute
control and status awareness.
All applicable man machine interfaces are described
in this section, including network administration,
network supervision, field technician/engineering and
ordinary user type of interfaces. The term "user"
designates a terminal user subscribing on the application
services.
The proposed network as described in chapter 3 is organized
such as to conform with the principles of Open Systems
Interconnection (OSI). The interfaces to the various
ACDN host environments are provided as part of the
network interface environment of each mode.
The Host Access Services (HAS) provide the means for
mapping and synchronizing the actual ACDN network with
various host network appearances applicable for specific
vendor standards.
o Towards the IBM hosts the ACDN network will appear
as an SNA network hosted by a SNA defines System
Services Control Point (SSCP and PU TS) and a Cross
Domain Resource Manager. The SSCP in the ACDN is
responsible for making network components as such
ICC's and terminals as appropriate IBM SNA physical
units and logical units.
o Towards Univac hosts, the ACDN resource network
will appear as a DCA network.
4.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
This chapter is structured to provide an overview of
network operations and to provide an insight into the
extent of control that can be exercised by the various
categories of operational staff personnel and users.
Section 4.2 provides an overview of the basic facilities
available to operate the network.
Section 4.3 identifies the classes of operational staff
personnel and users that are recognized and states
the scope of authority associated with each operational
class.
Section 4.4 describes the basic types of operator work
positions that are available at the different ACDN
subsystems.
Section 4.5 outlines various system security aspects
and describes in detail tha provision for secured network
access.
Section 4.6 presents, in overview form, the complete
collection of operator (and user) commands that are
available, the different operator categories for supervising
(and using) the network and its services.
Section 4.7 describes the Network Management Operations
associated with the Network Management Host (NMH) subsystem.
Section 4.8 describes the Network Control and Supervision
function providing the means for overall network control
and detailed status awareness.
Section 4.9 describes the processing and operations
of type B traffic associated with the Electronic Mail
Host (EMH) subsystem.
Section 4.10 describes the network operations and interfaces
applicable for the Nodal Switching Processor (NSP)
subsystems.
Section 4.11 describes the statistics collection capability
of the various ACDN subsystems. Statistics required
for obtaining a true picture of network performance
as well as charging data collected for billing purpose,
are described in this section. Also the facilities
provided for producing various kinds of network management
and control reports as well as user status reports,
are specified herein.
Section 4.12 describes the standard services provided
to users at an ordinary ACDN terminal.
Section 4.13 specifies the test and trace facilities
that are provided in support of network operations.
Section 4.14 describes the recovery facilities available
in the various ACDN network subsystems. Redundant
subsystem components are described herein, as well
as degraded modes of operation.
4.2 G̲e̲n̲e̲r̲a̲l̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
This section describes the basic facilities used to
operate the network. These are:
o network management
o network supervision
o protected message services
o user services
An overview of the approach taken for these subjects
are given in the following subparagraphs. More detailed
descriptions are provided in later sections in chapter
4.
4.2.1 N̲e̲t̲w̲o̲r̲k̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
Network management is concerned with the long term
planning and evaluation of network operation.
The network management functions will be provided through
the Network Management Host (NMH) facilities. The
following basic elements of management will be provided
in the NMH.
o network definition
o downline loading
o statistics processing
o charging and billing
o query language
o report generation
o modelling
o program development
o SW configuration control
4.2.1.1 N̲e̲t̲w̲o̲r̲k̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲
Network definition will be facilitated through an interactive
application assisting a network administrator in producing
a consistent network definition. The network definition
capability as offered at the NMH is for 2 purposes.
1) initial network definition to be transferred to
the NCC.
2) Definition of network configurations to be applied
as input to various modelling programs executed
at the NMH subsystem.
4.2.1.2 D̲o̲w̲n̲l̲i̲n̲e̲ ̲L̲o̲a̲d̲i̲n̲g̲
Network definitions and software systems/components
may be downloaded from the NMH to the NCC subsystem.
However, the master network definitions will reside
with the NCC. The NCC keeps 3 versions of network
definitions: The current, the previous, and an under-update
version. Software components are kept in one copy
only at the NCC: the current version. Other software
component versions may be requested by the NCC to be
transferred from the NMH SW configuration system.
4.2.1.3 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
Statistics captured at various places in network components
will at regular intervals be transmitted to the NMH
for further handling. The statistics processing applications
of the NMH cover the following areas:
o terminal usage
o session statistic
o node performance
o link utilization
o misc. hosts statistics
4.2.1.4 C̲h̲a̲r̲g̲i̲n̲g̲ ̲a̲n̲d̲ ̲B̲i̲l̲l̲i̲n̲g̲
User billing data will be produced by an NMH application,
based on session statistics captured and transmitted
from the nodal switches.
4.2.1.5 Q̲u̲e̲r̲y̲ ̲L̲a̲n̲g̲u̲a̲g̲e̲
A query language facility will be provided at the NMH.
It is a highly efficient set of tools based on high
level language query statements entered interactively
from CRTs. The query language facilities are closely
related to the Data Base Management System implemented
by the file management system CRAM.
4.2.1.6 R̲e̲p̲o̲r̲t̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
A Report Generation application will be provided at
the NMH. The Report Generator will be a general purpose
tool facilitating easy to read report displays - or
hard copy reports based on raw statistics and outputs
from statistical analysis programs.
4.2.1.7 M̲o̲d̲e̲l̲l̲i̲n̲g̲
Network modelling can be performed by software resident
in the NMH. During preparation of proposal Christian
Rovsing has used simplified network models for estimation
of configuration. The final modelling tools to be
implemented, will provide mathematical models for evaluation
of overall network performance and change proposals.
4.2.1.8 P̲r̲o̲g̲r̲a̲m̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
A comprehensive program development environment will
be available on the NMH processor. The standard DAMOS
program development environment includes a comprehensive
set of programs and utilities in the categories: text
processors, compilers, conversion programs, and test
tools. For details, please refer to the CR80 minicomputer
handbook.
4.2.1.9 S̲W̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
A SW configuration control application will reside
on the NMH. This application controls an overall software
release library containing several versions of each
network software component. Requests for delivery
of software components (from the NCC) is directed to
and processed by the configuration control application.
4.2.2 N̲e̲t̲w̲o̲r̲k̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲i̲o̲n̲
Network supervision is the task of dynamic control
of the entire network operation.
The network control functions will be provided through
the Network Control Processer (NCC) facilities. All
network control functions will be provided globally
from the NCC. However, certain limited control functions
will also be available from other network components,
e.g. node. The following basic elements of control
is provided as part of the network supervision function:
o Network definition
o Network initialization
o Transport network control
o External resource control
o Session control
o Recovery procedures
4.2.2.1 N̲e̲t̲w̲o̲r̲k̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲
The global network definition table resides globally
at, the NCC. Basically, the same Network Definition
application as mentioned in 4.2.1.1 (NMH) will be available.
The definition application will run as a low priority
job without affecting network supervision services.
Three different definition files are maintained:
- old network definition
- current network definition
- under update network definition
The definition file specifies all network components
including transport network and external resource network
(hosts, concentrators, and terminals).
The interactive Network Definition application outputs
a new network definition table in the "under-update"
definition file
The current network definition file contains a copy
of the online network table. In case of catastrophic
failures occuring when using a new network definition
file, the NCC may reinitialize the network according
to the previous configuration (old). Minor errors
in the online network definition may be corrected through
resource control commands and/or online table update.
The network definition program will provide fill-in
formats and as far as possible guide the user through
the configuration process, the goal being that a complete
definition of a consistent network should not be a
time consuming job.
The configuration definition formats and the network
table is constructed in a hierarchical manner, and
with provisions for storing any equipment characteristics
that can be thought of today, this does not present
inclusion of new equipment types.
To assist supervisory and management staff in maintaining
network definitions, the definition application can
produce hierarchical, easy to read, network definition
report printouts, identifying topologies and component
characteristics.
4.2.2.2 N̲e̲t̲w̲o̲r̲k̲ ̲I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
The initilization includes several phases: NCC initialization,
nodal transport system initialization and external
resource initialization.
After local initilization of the NCC the rest of the
ACDN network is remotely loaded and initialized from
the NCC. This includes the nodal network itself, i.e.
nodes, and the external resource networks at each node.
4.2.2.3 T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲
The transport system, once initialized, is principally
controlled automatically and autonomously by the NCC
software. However, the network supervisor may intervene
at both the link level for manual changing of network
topology (routes), and at the virtual circuit level
to perform lower level trouble shooting.
4.2.2.4 E̲x̲t̲e̲r̲n̲a̲l̲ ̲R̲e̲s̲o̲u̲r̲c̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
The management of external resources is left to the
operator to the extent that he can perform reconfigurations
and initiate tests on failed resources. However, the
synchronization of reconfigurations with the hosts
are performed automatically by the NCC.
4.2.2.5 S̲e̲s̲s̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
Session control is the level where the network operator
bridges the gap between the standard ACDN conversations
and the different types of host supported sessions.
A similar procedure is provided for EMH to host application
sessions. The operator may perform session set-up and
take-down as a service on behalf of end user resources
which are not themselves able to establish sessions.
Conversation control is the level where the operator
gets a unified view of the data traffic currently ongoing
in ACDN. Through status displays, the operator is
able to monitor the load on the system. He may also,
but generally need not, intervene to adjust the resources
utilization of the different conversations.
4.2.2.6 R̲e̲c̲o̲v̲e̲r̲y̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
There are two levels of recovery in the network:
- Element level i.e. recovery on the network element
level (node, NCC, EMH).
- Network level (ref. section 4.14.2 ff.)
All PUs in the network elements - NODES, EMH, NCC are
backed up in a hot redundant configuration.
For the NHM only cold redundancy is provided. In case
of serious errors encountered by the system controlling
watch dog, an automatic switchover and subsequent recovery
procedure is initiated. This procedure may also be
forced manually by a SWITCHOVER command. The recovery
procedure in itself is automatic. It includes a complete
PU take-over and protocol recovery session. Furthermore,
a system clean-up procedure is included in order to
assure consistent files and data structures.
Another aspect in the recovery procedure is the online
inclusion of a repaired device in the configuration.
This is normally accomplished by the operator command:
- INCLUDE - device
This command includes the device into the configuration.
4.2.3 P̲r̲o̲t̲e̲c̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲w̲i̲t̲c̲h̲i̲n̲g̲ ̲S̲e̲r̲v̲i̲c̲e̲
The service provided for PMS traffic concerns narrative
messages in ATA/IATA format or TELEX formats between
the following sources/destinations:
o ACDN terminals
o ACDN HOSTS (RES, VIA)
o External networks
- SITA
- ARINC
- CNT/TELEX
The services provided are the following:
o Automatic delivery (guaranteed)
o Storage of messages for retrieval
o Automatic routing of messages
o Adaption to external networks
o Repair facility for messages
o Logging and journalization of delivered messages
These services are provided mainly by the Electronic
Mail Host (EMH) facilities.
4.2.3.1 G̲u̲a̲r̲a̲n̲t̲e̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
All incoming messages are stored and routed according
to the ATA/IATA routing indicators or telex numbers.
The messages are stored on dualized disc equipment
and enqueued for delivery to ACDN terminals /Subscribers
to PMS) or delivery to other networks.
End-to-end acknowledgement between the EMH and the
destination guarantees delivery within ACDN.
The messages are delivered according to the assigned
priority.
4.2.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲
All messages are stored on long term storage (min.
8 hours). The messages may be retrieved by originators
and destinations using time and input or output serial
numbers as retrieval keys.
Tape backup for messages and message catalogs is provided.
4.2.3.3 A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The routing of the messages takes place automatically
on basis of the ATA/IATA routing indicators (TX + telex
numbers for telex). The routing indicators are converted
to terminal designators, host designator or external
network designator by table lookup.
4.2.3.4 A̲d̲a̲p̲t̲i̲o̲n̲ ̲t̲o̲ ̲E̲x̲t̲e̲r̲n̲a̲l̲ ̲N̲e̲t̲w̲o̲r̲k̲s̲
The ACDN adapts fully to the protocols employed by
the external networks and special characteristics.
- One feature is the automatic address stripping when
delivering to the SITA/ARINC networks.
4.2.3.5 R̲e̲p̲a̲i̲r̲ ̲o̲f̲ ̲F̲a̲u̲l̲t̲y̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Faulty messages being entered from ACDN terminals are
simply rejected back to the originator with an indication
of the error.
Faulty messages from other networks are routed to an
intercept position for online editing (repair).
Five intercept positions are proposed at the EMH.
The intercept operator may edit the message and reenter
it for automatic delivery or he may print it out for
delivery by other means or he may purge the message
from the system.
4.2.3.6 L̲o̲g̲g̲i̲n̲g̲ ̲a̲n̲d̲ ̲J̲o̲u̲r̲n̲a̲l̲i̲z̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲M̲S̲ ̲T̲r̲a̲f̲f̲i̲c̲
For statistical and billing purposes the following
information is recorded per message:
- Input/output device designators
- Input/output date and time
- Message size
- Input/output sequence numbers
- Priority
The statistics are forwarded to the NMH at regular
intervals. - Each terminal may also retrieve a journal
over the ingoing/outgoing PMS traffic.
4.2.4 U̲s̲e̲r̲ ̲S̲e̲r̲v̲i̲c̲e̲s̲
User services are provided to facilitate ordinary end
users with:
o Sign-on capability
o User communication
o Handling fo PMS traffic
o Status awareness
4.2.4.1 S̲i̲g̲n̲-̲O̲n̲
End users may establish sessions to one or several
host application services. However, the user may only
communicate with one service at a time, but may switch
between different simultaneous sessions.
4.2.4.2 U̲s̲e̲r̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲
A flexible scheme for user communication is provided.
For example, a network operator may send a message
to a single user terminal or broadcast a message to
all - or a group of terminals. Also an end user can
send a message to the network supervisor, appearing
as an event.
Further end user to end user communication is supported.
As part of the sign-on facility, a user receives a
canned message defined by the network supervisor.
4.2.4.3 H̲a̲n̲d̲l̲i̲n̲g̲ ̲f̲o̲ ̲P̲M̲S̲ ̲T̲r̲a̲f̲f̲i̲c̲
Handling of protected type B traffic is available to
the end user. This is summarized in section 4.2.3.
4.2.4.4 S̲t̲a̲t̲u̲s̲ ̲A̲w̲a̲r̲e̲n̲e̲s̲s̲
Status awareness funcions are provided to ordinary
ACDN terminal users. These functions enable users to
receive status displays indicating the connection status
of their CRT and printer (incl. session status), the
overall status of the relevant network resources (like
host applications) and the status of PMS traffic which
has been sent or is queued for the user terminal.
4.3 O̲p̲e̲r̲a̲t̲o̲r̲ ̲C̲a̲t̲e̲g̲o̲r̲i̲e̲s̲
This section describes the different kinds of operators
by the functions they are allowed to perform.
The main groups of operators are the following:
- Network Administrators
- Network Supervisors
- Local Office Managers
- Field Technicians
- Network Users
Security levels are assigned to all network users and
operators. - The security level indicates the priviledges
concerning the update rights/access control to the
user security records which again provides the access
rights control to the network services.
The security level hierachy is generally as follows:
Level 4: Network administrators
Level 3: Network supervisors
Level 2: Local Office Managers
Level 1: Field Technicians
Level 0: Network users
4.3.1 N̲e̲t̲w̲o̲r̲k̲ ̲A̲d̲m̲i̲n̲i̲s̲t̲r̲a̲t̲o̲r̲
The responsibilities of the network administrators
are the following administrative tasks:
- Network Cost and Billing administration.
- Generation of statistical reports and network administrative
reports.
- Network subscriber management.
- Long term and short term network planning.
- Network software and hardware configuration control
and management.
4.3.2 N̲e̲t̲w̲o̲r̲k̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲s̲
The network supervisors are responsible for the daily
monitoring and control of the entire network. This
supervision is performed centralized from the NCC sites.
The network supervisors are responsible for the implementation
of the network management functions initiated by the
network administration (e.g. installation of terminals,
lines, subscribers, new software).
Further, the network supervisors are responsible for
the actions to be taken in case of anomalies. - These
actions can be taken centralized from the NCC or distributed
in cooperation with the local office managers or field
technicians.
Thus, the network supervisors handle the below listed
tasks:
Users - All subscribers, agencies, user
profiles may be controlled by the
network supervisor.
Equipment - All equipment, lines etc. is controlled,
installed, removed in the network
by the network supervisor.
Traffic - Centralized traffic flow control
is a responsibility of the Network
supervisors.
Supervisor - Periodic reports, statistics etc.
are forwarded to the network administration.
Anomalies - Emergency actions switch-over -
recovery, cold start, restart is
performed in order to optimize the
network operations.
Security - All attempts to violate the security
system are handled by the network
supervisors.
PMS Service - Network supervisors are responsible
for the following PMS services:
o Central message repair for
incoming msgs. - from other
networks.
o Message storage supervision and
backup to tape.
o Centralize PMS reports to network
management.
o PMS addressing table maintenance.
Online Table
Handling - All the network tables which define
the network topology, the equipment
characteristics and priviledged
functions and the user profiles
(capabilities, priviledges) are
maintained online by the network
supervisors.
Software - New versions of the network software
is installed by the network supervisors.
4.3.3 L̲o̲c̲a̲l̲ ̲O̲f̲f̲i̲c̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲
The local office manager has authority to add, change
or delete security records within his own office.
4.3.4 F̲i̲e̲l̲d̲ ̲T̲e̲c̲h̲n̲i̲c̲i̲a̲n̲/̲E̲n̲g̲i̲n̲e̲e̲r̲
The field technicians are responsible for maintenance,
installation and test of the site equipment. Special
priviledges of the field technicians are:
- local computer operations
- test mode operations
4.3.5 N̲e̲t̲w̲o̲r̲k̲ ̲U̲s̲e̲r̲s̲
The ordinary network users may use the user services
described in section 4.12.
4.4 W̲o̲r̲k̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
This section describes the different types of operator
work positions used for network management, supervision
and control. The overall suggested room layouts for
the various site locations are illustrated in section
9.
Four different types of work positions are proposed.
o network administrator position (NMH)
o network supervisor position (NCC)
o electronic mail operator position (EMH)
o general engineering position
4.4.1 N̲e̲t̲w̲o̲r̲k̲ ̲A̲d̲m̲i̲n̲i̲s̲t̲r̲a̲t̲o̲r̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The NMH is equipped with three identical operator
positions, each a standard VDU (formatted) with alpha-numeric
keyboard. These three positions share the NMH peripherals
disk, tape, and lineprinter.
These positions are intended for all network management
work and program development performed on the NMH as
specified in section 4.2.1.
4.4.2 N̲e̲t̲w̲o̲r̲k̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The NCC is equipped with four identical supervisor
positions, each with a high resolution colour graphics
display terminal (8001 Intercolour Terminals).
The most important features of the terminal are as
follows:
Screen dimension: 19 inches
Resolution: 480 hor. by
380 ver. points
Lines: 48
Characters/line: 80
Colors: 8
The graphics terminal is driven through a colour form
editing program with the following properties:
The Colour Form Editor (CFE) provides a form definition
facility (offline) and a number of interface routines
between the CR80 and an Intelligent Systems 8000 series
Intercolour Terminal.
The Colour Form Editor provides a feasible tool for
setting up and handling of multi-coloured fill-in forms,
and is primarily intended for use with application
programs building various kinds of definition files.
A field is the smallest unit which is handled by CFE.
CFE distinguishes between three kinds of fields:
o Text fields which constitute the fixed parts of
the forms, containing text and character sequences
that are unalterable by the application program
which utilizes the CFE.
o Message fields which are output only fields that
can be used by the application program to output
various kinds of information to the terminal operator.
o Data fields which primarily are input fields where
the terminal operator can fill in information,
but which also can be used as output fields by
the application program.
A field is identified by a field number. Within each
of the three field types, fields must be numbered consecutively.
A form is a set of related fields which are handled
in common by the application program. A form can be
set up upon the display and removed dynamically. More
than one form can be displayed simultaneously, but
at any time only the fields of one form are accessible,
i.e. only one form can be active at a time.
A suite is a collection of related forms which are
handled by one application program. A suite can for
instance consist of forms corresponding to each of
the selection possibilities in the initial menu.
A suite is identified by an alphanumeric suite name.
The display of the Intercolour Terminal which is used
with the Colour Form Editor contains 48 lines of 80
character positions. Each of the 3840 character positions
on the display has an assigned foreground and background
colour which can be selected from the 8 colours: black,
red, green, yellow, blue, magenta, cyan, and white.
The display is divided into three parts; the user area,
and the upper and lower system area:
The upper system area contains the name of the currently
active form and the date and time when it was set up.
The user area holds the active form and any other inactive
form that has not explicitly been removed. The position
of a form within the user area is determined at the
time of set-up. The form address specified by the application
program demanding the set-up consists of a line number
in the range 1;40 and a column number in the range
1;80 . The dynamic form position scheme allows the
same form to be displayed concurrently in several places
in the user area, although only one can be active and
accessible at any time. This can e.g. be useful if
the forms contain table structured data. Instead of
defining one form containing the whole table with a
lot of identical fields, one can define a form which
corresponds to one entry in the table, and then use
several instances of this form.
The lower system area is parted in the system message
line and the function key assignment area. The system
message line is a message field with a width of 80
characters which is always defined. It can be used
by the application program to display messages which
are not related to a specific form but rather to the
suite, or it can be used to display messages when switching
from one form to another.
The keyboard of the Intercolour Terminal contains 16
function keys. When a form is defined it must be specified
which function keys the application program wants to
receive while handling this form. The function key
displays reflects this assignment.
4.4.3 E̲l̲e̲c̲t̲r̲o̲n̲i̲c̲ ̲M̲a̲i̲l̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The Electronic Mail Operator Positions (Supervisor)
are equipped with a Standard VDU with alpha numeric
keyboard. There are 4 dedicated supervisor positions
and 1 spare, dedicated to engineering purposes. The
4 supervisor positions share one lineprinter for hard
copy output.
The EMH Supervisor VDU is used for the EMH Supervisory
procedures and for message repair.
The layout of the VDU is the following:
o upper screen - 3 first lines are reserved for alarm
display and queue status display. These lines
are protected for keyboard input.
o Lower screen - the lower lines of the screen are
used for interactive procedures.
The control processes are built up as screen menues
to be filled out and sent to the EMH.
The repair procedure is described in section 4.9.5.2.4
4.4.4 E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
An engineering position is included in the following
network subsystems: at each Nodal Switching Processor
and at the Electronic Mail Host subsystem. The Engineering
position consists of a standard VDU (formatted) with
alphanumeric keyboard and a hardcopy matrix printer.
These work positions are intended for local network
supervisor command entry/report printouts, and field
technician hardware and software fault isolation and
verification.
