top - download
⟦562c94524⟧ Wang Wps File
Length: 21183 (0x52bf)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN44.08«
Derivation
└─⟦4bc3ed402⟧ Bits:30006259 8" Wang WCS floppy, CR 0166A
└─ ⟦this⟧ »~ORPHAN44.08«
WangText
…00……00……00……00……00…,…0a……00……00…,…0b…,…0e…,…02…+…0b…+
*…0b…*…01…*…02…)…09…)…0f…)…06…(…0e…( '…0b…'…02…'…05…&…0b…&…0e…&…05…%…0a…%…01…% $…0b…$…01…$
#…0a…#…0c…#…02…# "…0a…"…0c…"
"…05…!…0c…!…00…!…05… …09… …0e…
…1f……0a……1f… …1f……06……1e……0a……86…1 …02… …02… …02… …02…
CHAPTER 2
Page #
DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982
LIST OF CONTENTS Page
2. REQUIREMENTS ANALYSIS AND COMPLIANCE STATEMENTS
1
2.1 Introduction
1
2.2 Require Analysis 1
2.2.1 Overall System Requirements
1
2.2.1.1 Backbone Network
2
2.2.1.2 Hosts
3
2.2.1.3 Gateway 3
2.2.1.4 Access Network
3
2.2.1.5 Growth Requirements
4
2.3 Compliance Statements
5…86…1 …02… …02… …02… …02…
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE :
REQUIREMENT DESCRIPTION:
IS REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
NO
IS CUSTOM DEVELOPMENT REQUIRED? YES NO
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELYAFFECT (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK REQUIREMENT(S).
IF SO, PLEASE ELABORATE!
The response must clearly distinguish between existing functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
2. R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲ ̲A̲N̲D̲ ̲C̲O̲M̲P̲L̲I̲A̲N̲C̲E̲ ̲S̲T̲A̲T̲E̲M̲E̲N̲T̲S̲
2.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The scope of this section is to demonstrate an understanding,
at the strategic and implementation level, of ir Canada's
requirements.
The understanding is made visible in the form of commitments
given to questions in part 8 of the RFQ.
In section 2.2, an analysis of the requirements is
presented. This analysis has two major parts. The first
part is a a conceptual and component level and is in
tune with part 7 of the RFQ. The second part is at
a functional level and is in tune with part 6 of the
RFQ.
In section 2.3, specific answers to questions in part
8 of the RFQ are presented.
2.2 R̲e̲q̲u̲i̲e̲d̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
2.2.1 O̲v̲e̲r̲a̲l̲l̲ ̲S̲y̲s̲t̲e̲m̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The network concept as enunciated in the RFQ is in
line with one major trend in the telecommunication
industry. The trend is that there is a migration of
intelligence or synonymously computing powerfrom the
traditional Data Processing sites to the "Network".
At the second level, the inclusion of host access facilities
and terminal access facilities as part of the concept
network supports the above mentioned trend. It also
provides a unique pportunity to simplify the network
access procedures from the end user's point of view.
The concept of network also represents a structured
approach to solving the problem of migrating from the
existing environment to the common data network envionment.
This is seen in the requirement for a gateway. Such
a gateway approach in the context of a generalised,
inter-networking method is utilized for supporting
interfaces to external networks, and solving future
migrationary problems within theIBM and Univac environments.
The requirements for the concept network in the 1986-1991
time frame indicate a need for integrating different
types of traffic originating from a variety of users
and devices. Fulfillment of this need necessitates
prmarily:…86…1 …02… …02… …02… …02…
- a network access procedure that homogenises user
differences and recognises a complex priority scheme;
- a switching architecture that distinguishes traffic
types and respondsby dynamically allocating needed
bandwidth and control resources.
The prime concerns mentioned above warrant the use
of a simple data transport technology like DATAGRAMS
with additional end to end stream oriented transport
facilities like virtua connections.
2.2.1.1 B̲a̲c̲k̲b̲o̲n̲e̲ ̲N̲e̲t̲w̲o̲r̲k̲
The backbone network is conceived as a value added
network to be seen in the context of current private
network technology. Provision for services like the
Electronic Mail Network management are interprete as
value added items in the above context. The generic
elements of the backbone network are seen as:
- Nodes
- Hosts
- Gateways.
The nodes are conceived as high availability pure entities
throughout the network and are required to behave in
n amalgamated manner. The required behaviour of the
node is an amalgam of a network controller, a packet
switch, network management aid, network list centre
and a host/terminal interface unit.
The nodes are networked as a fully connected mesh.
Th connectivity is accomplished via high speed (156
kb/ps) inter-nodal trunks. As a switch, the node is
required to switch through 600 packets/second. As an
interface the node is expected to channel attach to
a main frame and behave as an orthodox meber of the
main frame determined architecture. As a terminal interface,
the node is expected to support up to 30 access lines
and support interfaces to concentrators, multiplexors
and stand alone terminals.
As a component of the backbone network the node is
configured as a fully redundant unit with a line switching
subsystem to effect a switchover from a catastrophically
failed active part.
2.2.1.2 H̲o̲s̲t̲s̲
Within the scope of the network are included certain
"Hosts" that provide administrative functions for network
management, electronic mail services.
The conceptio of network management host based services
coexisting with traditional host based application
services necessitates adherence to OSI principles of
niewing applications in a network context.
2.2.1.3 G̲a̲t̲e̲w̲a̲y̲
Recognition of the need that migrationinto an independent
data network from the existing network raises the requirement
for a gateway. The gateway approach itself is a principle
tenet of various inter-networking approaches that are
evolving. In the context of coexisting with external
ntworks such as SITA, ARINC a gateway based on emergency
international standards such as X75 is needed.
2.2.1.4 A̲c̲c̲e̲s̲s̲ ̲N̲e̲t̲w̲o̲r̲k̲
The strategic requirment for the terminal access network
is that future trends in high function terminals, future
trens in DTE standardisation, future trends in main
frame vendors' adoptation of OSI model must be exploited.
Concurrent with the above requirements is a need to
exploit communication cost-saving mechanisms at the
local access level, such as concentrtors and multiplexors.
Consequent to meeting the above needs, a formalised
requirement arises for a new store and forward concentrator
with:
- an X25 protocol on access lines connecting store
and forward concentrators to node;
- full duplex t obviate performance constraints;
- speed conversion, code conversion, protocol conversion
to exploit variety of offerings from the market
place;
- configuration requirements of 2.4 kb/ps linking
remote (remote to the concentrator) terminals,
2 terminals per remote line, remote line utilization
of 25%.…86…1 …02… …02… …02… …02…
The stategic needs for the host access network are:
- freedom to choose a host system based on available
application programs and productivity aids in support
of airline operatins;
- an ability to exploit inevitable developments on
price performance of raw computing power.
The above needs give rise to the requirements for:
- standard consistent interfaces;
- an architectural compatibility with major discernible
arhitectures like: IMB's SNA, Univac's DCA, and
Honeywell's DSA.
2.2.1.5 G̲r̲o̲w̲t̲h̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
In tune with the strategic requirements and in recognition
of the time involved in meeting the strategic requirements,
there is a need for equipment thatfacilitates an orderly
growth.
The growth is perceived both in terms of increased
number of terminal users and hosts and in terms of
a more than proportionate increase in data traffic.
The sizing of this requirement results in:
- support for minimum of 8 hosts in 3 centers;
- support for 12000 CRT's and 4500 printers;
- transaction volumes in the range of 540,000-900,000/hr.
The above requirements, coupled with a requirement
for minimum level of performance as perceived by a
terinal user, result in a given set of response time.…86…1
…02… …02… …02… …02…
2.3 C̲o̲m̲p̲l̲i̲a̲n̲c̲e̲ ̲S̲t̲a̲t̲e̲m̲e̲n̲t̲s̲…86…1 …02… …02… …02… …02…
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE : ̲ ̲ ̲ ̲ ̲R̲.̲1̲.̲1̲.̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
REQUIREMENT DESCRIPTION: ̲ ̲ ̲ ̲ ̲T̲y̲p̲e̲ ̲A̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
S REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
IS CUSTOM DEVELOPMENT REQUIRED? YES
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELY AFFCT (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK REQUIREMENT(S).
IF SO, PLEASE ELABORATE!
The response must clearly distinguish between existing functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
The Datagram Service (DGS) provided by the Network
Switching Software (NSS) og ACDN is ideally suited
to support the Type A traffic. The service provides
a direct interface to the underlying datagram technology
which is used to implement the ACN. This service is
described in more detail in 6.5.
The structure of the ACDN software is such that load
sharing, to exploit the system resources, can be tailored
by suitable parameterised software packaging. The software
is logically built as "hrizontal" layers. Each layer
consists of a number of Tasks performing similar functions.
Now, for optimal functionality, the software is also
partitioned "vertically" into Processes. This results
in parallel Processes (multiserver structure) with
ttal capability to provide the necessary services in
each node. The operating system provides efficient
means of scheduling and communicating in both the Process
environment and the Task environment.…86…1 …02… …02…
…02… …02…
Thus, load sharing within the node software is total.
As for the internode lines, the primary aim of the
datagram technology is to optimize the transmission
resources by "loadsharng" them between the network
users. The datagram sublayer of the NSS uses a split-routing
technique to spread the outgoing traffic from a node
to the next node on Multiple Link Groups (MLG). Each
MLG consists of a number of Logical Links (LL). The
ink level software which controls the LL's again may
share load between multiple physical trunks by using
Multi Link Procedures (MLP).
On the access lines to hosts, the load sharing is achieved
by invoking the relevant Host Access Software (HAS)
unctions, such that the incoming traffic is shared
between a specified number of host-applications.
The NSS provides eight levels of priorities. These
levels can be supplemented by invoking Process-priorities
provided by the operating system.
Te Type A traffic will be carried through the network
by the datagrams in the ACDN transport system. The
ACDN transport network is functionally isolated and
therefore will not have any bearing on the interface
protocols used to communicate with host or terminals.
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE : ̲ ̲ ̲ ̲R̲.̲ ̲1̲.̲1̲.̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
REQUIREMENT DESCRIPTION: ̲ ̲ ̲ ̲T̲y̲p̲e̲ ̲B̲ ̲t̲r̲a̲f̲f̲i̲c̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
IS REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
IS CUSTOM DEVELOPMENT REQUIRED? NO
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELY AFFCT (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK REQUIREMENT(S).
IF SO, PLEASE ELABORATE!
The response must clearly distinguish between existing functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
The Type B traffic will be supported by the Virtual
Transport Connection services (VTCS) provided by the
Network Switching Software (NSS) in the ACDN. This
service provides a stream oriented data transport service
with end-to-end guarantee. The ervice is defined in
more detail in 6.5.
A connection in this context is a logical relationship
between a pair of network users - there does not exist
a unique physical path between these users. This is
due to the underlying datagram technology tat is used
to support the service. This means that a connection
servicing a given pair of ACDN users (devices) has
survivability in spite of numerous topological changes
that may occur in the physical linkage of the ACDN.
The actual interface to he ACDN users or devices is
provided by the Host Access Software (HAS) and the
Terminal Access Software (TAS) which reside in ACDN
node. These, in turn, communicate with each other via
the above mentioned connection services.
The Network Switching Software (NSS) will receive requests
for connection establishment from HAS and TAS. A request
will contain the appropriate network addresses. The
responsibilty of translating the user or device oriented
addresses to the corresponding ACDN network-addresses
lie with HAS and TAS. For predefined "well-known" users
or devices, this translation may be performed solely
by HAS or TAS. In more dynamic environmnt of users,
the translation is performed by HAS or TAS in co-ordination
with the Network Control Centre (NCC).
The NSS provides facilities for multiple connection
to the same user or device. The multiple connections
will be resolved as simultaneus user-to-user sessions
in HAS and TAS to provide services that share the same
device. In this sense, HAS and TAS will consider a
particular physical device to house a number of logical
devices, each having the capability of establishing
and maintining logically independent sessions.
The overhead incurred in sharing devices is limited
to that required for managing and mapping the logical
device structure on to the physical device. The response
times for individual logical-device-sessions ill be
affected solely by the strategy employed to map the
responses onto a physical device and not by the internal
communication facilities provided within the ACDN.
The NSS bases the connection services on the end-to-end
protocol employed in it Data Transmission Environment.
The protocol is based on ECMA-72, a standard produced
by the European Computer Manufacturers Association.
This standard is very similar to the one considered
for standardization by International Standards Organizatin
(ISO).…86…1 …02… …02… …02… …02…
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE : 1̲.̲1̲.̲3̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
REQUIREMENT DESCRIPTION: T̲y̲p̲e̲ ̲B̲ ̲-̲ ̲A̲s̲s̲u̲r̲e̲d̲ ̲I̲n̲d̲i̲r̲e̲c̲t̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
̲ ̲ ̲ ̲ ̲ ̲
S REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
IS CUSTOM DEVELOPMENT REQUIRED? YES
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT: 36 manmonths
(includes entire
EMH)
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELY AFFECT (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK
REQUIREMENT(S). IF SO, PLEASE ELABORATE! NO
The response must clearly distinguish between exiting functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
1. The EMH will provide for store and forward message
switching as required.
2. The messages may be retrieved for as long as they resideon
the long term storage. The long term storage is implemented
as wrap-around files sufficiently sized for 8 hours
of peak traffic (200 Mbytes).
3. The EMH has interface to the following terminals, hosts
and external networks:
Terminals:
- Diect connected teleprinters (TTY)
- Concentrator Switched terminals (CRTs, printers)
Hosts:
- RES
- VIA
- SUPPH
External networks:
- SITA
- ARINC
- CNT
- TELEX
4. Messages formatted according to ATA/IATA or Telex formats
will be supported fully including mnemonic addressing
for Telex. ATA/IATA routing indicators from 7 to 11
characters will be supported as specified - including
the special coding for VIA.
5. Functional equivalence of existing PMS services is
provided concerning:
- Device handling
- Delivery control
- Alarmsupervision
- Repair function
- Table handling
- Priority delivery
- Retrieval functions
6. The capability limits of the PMS traffic is determined
by the disc size (300 Mbyte) which is sufficient for
8 busy hour traffic. The software is able o handle
up to 600 Mbyte disc devices without any change.
The proposed EMH includes support for normal magnetic
tapes for long term storage.
However, in view of the anticipated large volumes of
type B traffic and limited storage capacity of a nrmal
magnetic tape alternative means for long term storage
is recommended. - One approach is to use High Density
Digital Tape Recorders which allow for 2750 Mbytes
to be stored on one tape of 14 channels. Christian
Rovsing has implemented a numbe of archiving systems
using this advanced technology.
7. For each output device (i.e. terminal Host channel,
external network line) there is allocated a priority
output queue of 6 precedence levels including those
of ATA/IATA. No hard limit is pu on the queue size,
however a queue threshold may be specified by the supervisor.…86…1
…02… …02… …02… …02…
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE : ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲.̲1̲.̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
REQUIREMENT DESCRIPTION: ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲H̲o̲s̲t̲ ̲t̲o̲ ̲H̲o̲s̲t̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
S REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
IS CUSTOM DEVELOPMENT REQUIRED? NO
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELY AFFET (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK REQUIREMENT(S).
IF SO, PLEASE ELABORATE!
The response must clearly distinguish between existing functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
The fundamental view of HOSTS by the ACDN is that they
participate in the network and utilize its transport
facilities to transfer data amongst themselves.
The features that the network has to support bulk data
flow between the hosts are:
- taffic type determination based on the parameters
present during session establishment
- a priority allocation procedure at the session-conversation
level
- a mechanism to gain necessary bandwidth at the
data transmission level by dynamically conrolling
the flow control parameters and invoking the facility
for multiplexing one session over multiple virtual
transport and real transport paths
- an operator controlled facility for allocating
necessary resources to particular sessions
When osts are collocated and are front ended by collocated
dedicated CR80 based front end processors the high
speed interprocessor bus on the CR80 and the supporting
Basic Transport Station facilities can be utilized.…86…1
…02… …02… …02… …02…
The addressing method utilized in the identification
of end points in a host to host transfer is part of
an overall resource addressing scheme.
The applications at the end point qualify as logical
units under SNA, DCA and DSA.
It is feasible to implement a mainframe vendor independent
file transfer protocol. However, it is not part of
current proposal.
The protocol employed and currently supported is the
HASP for IBM nd NTR for Univac with the necessary cross
emulation facilities.…86…1 …02… …02… …02… …02…
RESPONSES TO AIR CANADA REQUIREMENTS
REQUIREMENT REFERENCE : ̲ ̲ ̲ ̲ ̲ ̲ ̲R̲.̲1̲.̲1̲.̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
REQUIREMENT DESCRIPTION: ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲e̲w̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲G̲r̲o̲w̲t̲h̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
S REQUIREMENT SATISFIED BY THIS PROPOSAL? YES
IS CUSTOM DEVELOPMENT REQUIRED? YES
ESTIMATED EFFORT REQUIRED FOR CUSTOM DEVELOPMENT
DOES THIS REQUIREMENT AND/OR YOUR SOLUTION TO THIS REQUIREMENT
ADVERSELY AFFCT (IMMEDIATE OR LONG TERM) ANY OTHER NETWORK REQUIREMENT(S).
IF SO, PLEASE ELABORATE!
The response must clearly distinguish between existing functionality
and custom development.
DESCRIBE IN DETAIL HOW ITEM IS OR WILL BE SATISFIED:
