OctetView
0x00000…00100 (0, 0, 0) Sector 10065631303036 ┆ V1006V ┆
[…0x1…]
0x00200…00300 (0, 0, 2) Sector ff00f0ffffffff ┆ p ~ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x12, d01=0x55, d02=0x56, ptr=(27,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x20, d01=0x60, d02=0x41, ptr=(29,0, 8), d05=0x00}
0x0030c…00320 20 60 41 20 00 00 20 69 41 1f 08 40 00 00 00 00 00 00 00 00 ┆ `A iA @ ┆
0x00320…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x5…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 B 8 7 Q? > 7 | W d O | T d N ~< v <)&4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; `A C g x g V Wb O B : 2060A g G < {C < { ; 9 c! c ck r 9 8 : t xk y# 2093A2087A1266V2069A2101 * * > ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
0x00800…00900 (0, 0, 8) Sector 0009ff41125556 ┆ A UV1255V Kapitel 3, CRAS TCA655 TC 04 19 82 12 34 01 42 19 04 82 15 45 1006V 75 01 1404 42 ' *J 7 + _┆
0x00900…00a00 (0, 0, 9) Sector 000a4b10125556 ┆ K UV ┆
0x00a00…00b00 (0, 0, 10) Sector 000bff52125556 ┆ R UV 1 CHAPTER 3 Page DOCUMENT III TECHNICAL PROPOSAL Oct. 8, 1981 Rev.:Mar. 1, 1982 LIST OF CONTENTS Page 3. PROPO┆
0x00b00…00c00 (0, 0, 11) Sector 000cff2a125556 ┆ * UVSED SOLUTION .............................. 3 3.1 Introduction ................................... 4 3.2 Proposed Technical Solution .................... 6 3.2.1 Scope of Air Canada Data Network ............┆
0x00c00…00d00 (0, 0, 12) Sector 000dff69125556 ┆ i UV... 6 3.2.2 Functional Overview ............................ 8 3.2.3 External Environments .......................... 11 3.2.4 Proposed Network Architecture .................. 14 3.2.4.1 Network Interface Environment┆
0x00d00…00e00 (0, 0, 13) Sector 000eff95125556 ┆ UV .................. 17 3.2.4.2 Communication User Environment ................. 18 3.2.4.3 Transmission Environment ....................... 22 3.2.4.4 Data Link Environment .......................... 23 3.2.4.5 Network Service En┆
0x00e00…00f00 (0, 0, 14) Sector 000fff3a125556 ┆ : UVvironment .................... 24 3.2.4.6 Network Architecture Realisations .............. 25 3.2.5 Deliverables ................................... 26 3.3 Proposed Nardware Equipment .................... 34 3.4 ┆
0x00f00…01000 (0, 0, 15) Sector 0100ff21125556 ┆ ! UV Proposed Software Packages ..................... 38 3.4.1 Access software ................................ 42 3.4.2 Nodal Switching Software ....................... 45 3.4.3 Network Control Software ......................┆
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x3…]
0x01400…01500 (1, 0, 4) Sector 0105ff33125556 ┆ 3 UV 1 3.8 Options ........................................ 74 3.8.1 Videotex ┆
0x01500…01600 (1, 0, 5) Sector 01063ea1125556 ┆ >! UV....................................... 76 Aq*w?+"w?*v?& k!d M >k! M >>0ME>e*w?Aq*w?+"w?*v?& k!d M >>0ME>e*w?AqI!y?6 >D!y?>Z'=*y?& > &w!y?4B =I M3{I`iC;=`iCh=UM > :5>_> M7>>/Mx>:4>_> M7>>/Mx>:6>_> M7>QIUM > :3>_> M7>>:Mx>:2>_┆
0x01600…01700 (1, 0, 6) Sector 0107ff37125556 ┆ 7 UV 1 3. PROPOSED SOLUTION To the extent that Air Canada is embarking on e┆
0x01700…01800 (1, 0, 7) Sector 0108ffc3125556 ┆ C UVstablishing a network base for the 1980s with the full knowledge of the positive impact this will have on Air Canada|s operations, services to the passengers and to the {irline industry|s commercial infrastructure, we have presented ┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x19f…]
0x1b800…1b900 (27, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(27,0, 9), len=0xff, h3=41125556}, f00=»1255V «, f01=»AIR CANADA DOC III CH. 3 «, f02=»TCA655 «, f03=»TC «, f04=»Anvendt t.overf]rsel «, f05=04-19-82 12:34, f06=» «, f07=»14 «, f08=» 132 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=16-07-82 10:56, f15=»1006V «, f16=» 75 «, f17=» «, f18=»14 «, f19=» 1404 «, f20=» 132 «, f21=» «, f22=» «, f99=100010000110062710130401aaca9405000000000000003703ac01df}
0x1b900…1ba00 (27, 0, 9) WangDocumentBody
[…0xd…]
0x1c700…1c800 (28, 0, 7) Sector 00000000000000 ┆ ┆
0x1c800…1c900 (28, 0, 8) WangDocumentBody
[…0xf…]
0x1d800…1d900 (29, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(29,0, 9), len=0xff, h3=41206041}, f00=»2060A «, f01=»AIR CANADA PROPOSAL «, f02=»ut «, f03=» «, f04=»DIVERSE «, f05=22-04-82 18:40, f06=» «, f07=»38 «, f08=» 3466 «, f09=16-07-82 11:42, f10=» «, f11=»01 «, f12=» 18 «, f13=27-04-82 20:58, f14=16-07-82 14:11, f15=»1006V «, f16=» 6 «, f17=» 1 «, f18=»39 «, f19=» 92 «, f20=» 6573 «, f21=» «, f22=» «, f99=600010000110056610110180aaca15050000000000000142031f00df}
0x1d900…1da00 (29, 0, 9) WangDocumentBody
[…0x6…]
0x1e000…1e100 (30, 0, 0) Sector 1e01ff00206041 ┆ `A Compliance Data 2.1 Requirements Analysis CSK 22 10 2.2 COMPLIANCE DATA 24 40 Input 24, ┆
0x1e100…1e200 (30, 0, 1) Sector 1e02ff00206041 ┆ `A evening Chapter 3 Proposed Solution FR x x x Chapter 4 Network IF's & Interfaces x 15 except EMS + NMS Chapter 5 Equipme┆
0x1e200…1e300 (30, 0, 2) Sector 1e034300206041 ┆ C `Ant Char. x 5 x x H/W monitor + ~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x1e300…1e400 (30, 0, 3) Sector 1e04ff00206041 ┆ `A 1 D N T C C F R E Y O O I A W P R R N F E R R I T P D R R S A E┆
0x1e400…1e500 (30, 0, 4) Sector 1e05ff00206041 ┆ `A E H COMMENT G C C E E T T D S - - 1 2 Honeywell Chapter 6 S/W Characteristics 6.1 Introduction MEC x ┆
0x1e500…1e600 (30, 0, 5) Sector 1e06ff00206041 ┆ `A x x 6.2 Stand. System S/W JH[? x - x coordinate ASM 6.3 Transport Mechanisms JH[? 3 " " 6.4 Data FLow & Netw. Tab MEC x x x inc┆
0x1e600…1e700 (30, 0, 6) Sector 1e07ff00206041 ┆ `Alude Uni- Univac/IBM? 6.5 Nodal Switch MEC x x x 6.6 Terminal Access CSK 23 translation 6.7 Host Access CSK 23 25 ┆
0x1e700…1e800 (30, 0, 7) Sector 1d08ff00206041 ┆ `Ax of some 100 p 6.8 Internal Network FE x x 6.9 External Network FE x x + X.75 gatew. 6.10Network Control JSL new activi┆
0x1e800…1e900 (30, 0, 8) Sector 1e09ff21204141 ┆ ! AAX adds, to a data processing environment, the capability of using low-cost and standardized terminals to interact with different data bases in a user-oriented way. Applications for VIDEOTEX are virtually inlimited. Here are a few examples: o Ne┆
0x1e900…1ea00 (30, 0, 9) Sector 1e0aff21204141 ┆ ! AAws Media - news briefings - weather forecasts - restaurant guides - going out o Travel and Tourist Information - time tables, local and global - information on destinations, domestic and foreign - local transportation schedules - ┆
0x1ea00…1eb00 (30, 0, 10) Sector 1e0bc021204141 ┆ @! AAlocal entertainment guides o Advertising o Banking - account inquiries - funds transfer - bill payments - product/service manuals - financial news service - calculations ic The projected internodal peak hour traffic is: ┆
0x1eb00…1ec00 (30, 0, 11) Sector 1e0cffa1204141 ┆ ! AA 1 The VIDEOTEX product has been delivered by Christian Rovsing to the Danish Tele Administrations implemented on the CR80 computer system. VIDEOTEX offers the following capabilitie┆
0x1ec00…1ed00 (30, 0, 12) Sector 1e0dffa1204141 ┆ ! AAs: - Retrieval of VIDEOTEX images in a CR80 database - Generation/modification of VIDEOTEX images - Maintenance of user catalogue - Provision for generation of users in user groups - Maintenance of password - Message service - Generation of ┆
0x1ed00…1ee00 (30, 0, 13) Sector 1e0effa1204141 ┆ ! AAprimary keywords User terminals acquire access to the CR VIDEOTEX system by means of call on the public telephone network. This facility could be useful as it could provide a means of establishing a "public" entry point to ACDN value added service┆
0x1ee00…1ef00 (30, 0, 14) Sector 1e0fffa1204141 ┆ ! AAs. The user of this could be a subscriber external to the ACDN who could dial this service. A normal television set modified with low-cost circuit board as a terminal and provided with a low-cost modem is what that subscriber needs to use in this ┆
0x1ef00…1f000 (30, 0, 15) Sector 1c08ffa1204141 ┆ ! AAfacility. A logon image is presented to the user when he has acquired access to the system. The user has to key in his user number and associated password. The user may choose individual VIDEOTEX applications once the authentication has been succe┆
0x1f000…1f100 (31, 0, 0) Sector 1f01ffc2204141 ┆ B AAressed-coding transfer chips, by which voice channels can be as narrow as 240 o bps, the Air Canada Data Network Equipment is well suited to include such types of traffic too. This is indicated as a Common Branch Exchange and as an automated office┆
0x1f100…1f200 (31, 0, 1) Sector 1f02ffc2204141 ┆ B AA processor with a local network. Videotex and Telefax might also be attachable, directly or through other public networks. These examples were intended to illustrate the residence of the CR80 System Approach: The system is balanced, i.e. it do┆
0x1f200…1f300 (31, 0, 2) Sector 1f0341c2204141 ┆ AB AAes not create inhibiting bottlenecks, when growth occurs. 3.6.3 Block Diagrams This section presents the year by year block diagrams which constitute both the baseline but also the projected growth. Only major network elements have bee┆
0x1f300…1f400 (31, 0, 3) Sector 1f04ff2a204141 ┆ * AA 1 Presently foreseen are the needs for encryption facilities. Such implementations will benefit from our significant experience in this field. Soon to come may be the need for fur┆
0x1f400…1f500 (31, 0, 4) Sector 1f05ff2a204141 ┆ * AAther Host Access Subsystems which are part of the Host-Access Network. The CR80 system concept is well suited for such applications, as shown with the UNIVAC and IBM host Example offered, and we look forward to supplying parts of the Host Access N┆
0x1f500…1f600 (31, 0, 5) Sector 1f06a72a204141 ┆ '* AAetwork as amendments to the backbone Network. For future efficient interconnections of the ACDN and public data networks, the X.75 Gateway may be of interest. 2 2 2 Internodal Trunks 3+2 2+3 ┆
0x1f600…1f700 (31, 0, 6) Sector 1f07ff21204141 ┆ ! AA 1 3.8.1 Videotex Christian Rovsing is in a position to offer Videotex as an added value service to the proposed ACDN. This product could be implemented as part of the proposed Elect┆
0x1f700…1f800 (31, 0, 7) Sector 1e08ff21204141 ┆ ! AAronic Mail Service. VIDEOTEX, also known as Viewdata, is a facility for retrieving information from computer data bases. The information is stored in "pages" in the VIDEOTEX system or may optionally be retrieved from external data bases. VIDEOTE┆
0x1f800…1f900 (31, 0, 8) Sector 1f09ff21204141 ┆ ! AA 1 3.7 Telecommunications Recently Christian Rovsing's maintenance subcontractor CNCP Telecommunications, responded to an Air Canada Request for Information (RFI). Their response to┆
0x1f900…1fa00 (31, 0, 9) Sector 1f0aff3a204141 ┆ : AA the RFI dated December 15, 1980 is included in its entirety in this proposal as Appendix E. Christian Rovsing feels this document provides Air Canada with sufficient details on CNCP's existing network services and offerings, as well as their pla┆
0x1fa00…1fb00 (31, 0, 10) Sector 1f0b713a204141 ┆ q: AAns for the future, to enable Air Canada to plan for a total solution to their communication requirements. volume to nodes generated by resources outside the node. b. Internodal Traffic The projected internodal peak hour traffic is: ┆
0x1fb00…1fc00 (31, 0, 11) Sector 1f0cffc2204141 ┆ B AA 1 3.8 Options o The hardware and software structures fully support openended growth beyond the projected backbone network expansion. Potential growth areas are: - Internodal Meg┆
0x1fc00…1fd00 (31, 0, 12) Sector 1f0dffc2204141 ┆ B AAabit Trunk Capacity (2Mbit(s) - Voice Switching through the ACDN - Internodal Megabit satellite links - Front End Processor connections to Host Access Network - Videotex - Telefax - Encryption The (Internodal) trunk capacity in the megabit┆
0x1fd00…1fe00 (31, 0, 13) Sector 1f0effc2204141 ┆ B AA range will be necessary both for the connection of the Passenger Management System and for the Host-to-Host links in the Host Access Network. The CR80 module, the STI, presently interfacing to the 16 Mbps SUPRA Bus and the 1.8 Mbps TDX bus, can b┆
0x1fe00…1ff00 (31, 0, 14) Sector 1f0fffc2204141 ┆ B AAe used as the interface to such megabit communication lines, together with the appropriate adapter. This also supports megabit satellite loops, when needed, since the STI can have at its disposal up to 1 Mega words; and large buffering capacity an┆
0x1ff00…20000 (31, 0, 15) Sector 1f00ffc2204141 ┆ B AAd a selective retransmission function are needed in order to provide efficient transmission over the long-delaying satellite hops. Either based upon conventional digitized voice transmission using standard 64 Kbps per channel or on the latest comp┆
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41206041}, f00=»2060A «, f01=»AIR CANADA PROPOSAL «, f02=»ut «, f03=» «, f04=»DIVERSE «, f05=22-04-82 18:40, f06=» «, f07=»38 «, f08=» 3466 «, f09=16-07-82 11:42, f10=» «, f11=»00 «, f12=» 8 «, f13=27-04-82 20:58, f14=16-07-82 11:42, f15=»1006V «, f16=» 6 «, f17=» 1 «, f18=»38 «, f19=» 92 «, f20=» 6563 «, f21=» «, f22=» «, f99=600010000110056610110180aaca15050000000000000142031f00df}
0x20100…20200 (32, 0, 1) Sector 20020600206041 ┆ `A DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / ┆
0x20200…20300 (32, 0, 2) Sector 2003f300206041 ┆ s `A 1 Page # APPENDIX D Apr. 23, 1982 J#.:!<2.=M2┆
0x20300…20400 (32, 0, 3) Sector 2004ff00206041 ┆ `A 1 D N T C C F R E Y O O I A W P R R N F E R R I T P D R R S A ┆
0x20400…20500 (32, 0, 4) Sector 2005ff00206041 ┆ `A E E H COMMENT G C C E E T T D S - - 1 2 DOC. I Business Guidelines Chapter 1 Price FR 24 5 input 23 ┆
0x20500…20600 (32, 0, 5) Sector 2006ff00206041 ┆ `A evening Chapter 2 Bidding Provisions KHJ 23 10 Chapter 3 Corporation Info ALF x x x Section 3.4 PIP FR 24 15 ┆
0x20600…20700 (32, 0, 6) Sector 2007ff00206041 ┆ `A SOW CVs OE 23 30 input 23, evening DOC. II Executive Summary ALF 24 15 copy all ┆
0x20700…20800 (32, 0, 7) Sector 1e00ff00206041 ┆ `A 26 morning EVERYBODY Review DOC. III Technical Proposal Chapter 1 Introduction CSK 22 2 Chapter 2 Req. Analysis and┆
0x20800…20900 (32, 0, 8) Sector 2009ff37204141 ┆ 7 AAmber of internodal trunks. c Access Lines YEAR ACCESS LINES IBM LINES T M W T M W 84 59 69 50 0 30 7 85 69 81 58 0 33 8 86 81 ┆
0x20900…20a00 (32, 0, 9) Sector 200ae637204141 ┆ f7 AA 95 68 0 34 9 87 89 104 74 0 38 9 88 98 115 82 0 42 10 89 107 126 90 0 46 11 90 118 139 99 0 50 13 91 130 153 109 0 55 14 While the individual no┆
0x20a00…20b00 (32, 0, 10) Sector 200bff37204141 ┆ 7 AA 1 3.6.3 Block Diagrams This section presents the year by year block diagrams which constitute both the baseline but also the projected growth. Only major network elements have bee┆
0x20b00…20c00 (32, 0, 11) Sector 200cd237204141 ┆ R7 AAn included: o Network Management Processor (NMP) o Nodal Control Processors (NCP) o Nodal Switching Processors (NSP) o Electronic Mail Processors (EMP) o Channel Units o the stated EMH failure rates. s┆
0x20c00…20d00 (32, 0, 12) Sector 200d612a204141 ┆ a* AA 1 Figure III 3.6-1 nd Projected Growth 3.6.1 Baseline Capacity The proposed baseline ACDN has been sized to handle the anticipated l985 load. The following summarizes the pr┆
0x20d00…20e00 (32, 0, 13) Sector 200e602a204141 ┆ `* AA 1 Figure III 3.6-2 Transactions/hour 575 549 918 Host Connections 2 2 2 Internodal Trunks 3+2 2+3 ┆
0x20e00…20f00 (32, 0, 14) Sector 200f6095204141 ┆ ` AA 1 Figure III 3.6-3 0 33 8 formance improvements of the bandwidth will be implemented by collecting up to three PMS transactions before the actual write ┆
0x20f00…21000 (32, 0, 15) Sector 1f08603a204141 ┆ `: AA 1 Figure III 3.6-4 The baseline ACDN configurations will be sized to handle the projected capacities. The projected volumes and required network capacity are summarized belo┆
0x21000…21100 (33, 0, 0) Sector 2101ff37204141 ┆! 7 AAw: a Transactions/sec. The projected peak hour transaction volume per sec. per node is: TRANSACTIONS/SEC YEAR TOR MTL WPG ┆
0x21100…21200 (33, 0, 1) Sector 2102ff37204141 ┆! 7 AA84 137.0 130.8 218.7 85 159.7 152.5 255.0 86 185.4 177.0 296.0 87 203.9 194.7 325.6 88 224.3 214.2 358.2 89 246.8 235.6 394.0 90 271.4 ┆
0x21200…21300 (33, 0, 2) Sector 2103ff37204141 ┆! 7 AA259.1 433.4 91 298.6 285.1 476.7 The above represents the total incoming transaction volume to nodes generated by resources outside the node. b. Internodal Traffic The projected internodal peak hour traffic is: ┆
0x21300…21400 (33, 0, 3) Sector 2104ff37204141 ┆! 7 AA KBPS INTERNODAL TRUNKS YEAR T-M T-W M-W T-M T-W M-W 84 28.4 81.8 79.6 .8 2.4 2.3 85 33.2 95.4 92.8 ┆
0x21400…21500 (33, 0, 4) Sector 2105ff37204141 ┆! 7 AA 1.0 2.8 2.7 86 38.5 110.7 107.7 1.1 3.2 3.1 87 42.3 121.8 118.5 1.2 3.6 3.5 88 46.6 133.9 130.3 1.4 3.9 3.8 89 51.2 147.3 143.3 1.5 4.3 4.2 90 56.4 162.1┆
0x21500…21600 (33, 0, 5) Sector 21065e37204141 ┆! ^7 AA 157.7 1.6 4.7 4.6 91 62.0 178.3 173.5 1.8 5.2 5.1 = 3.5 years MTTR subscriber = 28 min Availability subscriber = 99.9985% The RMA analysis implies that a s┆
0x21600…21700 (33, 0, 6) Sector 2107ff37204141 ┆! 7 AA 1 The projected internodal traffic has been derived using: 1. the projected transaction volume, 2. the projected length of transactions, type by type, 3. assuming a communicati┆
0x21700…21800 (33, 0, 7) Sector 2008ff37204141 ┆ 7 AAons header of 20 bytes plus trailer of 3 bytes, 4. assuming l0% network control, acknowledge traffic with average length corresponding to that of other traffic, 5. a trunk utilization of 75% has been used as baseline to establish the required nu┆
0x21800…21900 (33, 0, 8) Sector 2109ff00204141 ┆! AA 1 4. At most one group of two access lines per NSP without service. 5. All NSPs assumed worst case NSPs, i.e. with 36 access lines. 6. Only maximum configured nodes assumed┆
0x21900…21a00 (33, 0, 9) Sector 210aff00204141 ┆! AA, i.e. with NSPs). The results which apply to the network subject to the above assumptions are as presented below: MTBF ACDN = 8900 hours MTTR ACDN = l5 min Availability = 99.9972% While the individual no┆
0x21a00…21b00 (33, 0, 10) Sector 210bff00204141 ┆! AAde (maximum configuration) is MTBF node = 3.l years MTTR node = l5 min Availability = 99.999l% c Electronic Mail The RMA analysis results which apply to the Electronic Mail Host are: MTB FENH = ┆
0x21b00…21c00 (33, 0, 11) Sector 210cfe00204141 ┆! ~ AAl4 years MTTR EMH = 48 min Availability = 99.9995% To the above should be noted that it reflects the l99l EMH configuration and that the disks storages represent the major factor to the stated EMH failure rates. s┆
0x21c00…21d00 (33, 0, 12) Sector 210dff37204141 ┆! 7 AA 1 3.6 Baseline Capacity and Projected Growth 3.6.1 Baseline Capacity The proposed baseline ACDN has been sized to handle the anticipated l985 load. The following summarizes the pr┆
0x21d00…21e00 (33, 0, 13) Sector 210eff37204141 ┆! 7 AAoposed capacities by location: Toronto Montreal Winnipeg l000 Transactions/hour 575 549 918 Host Connections 2 2 2 Internodal Trunks 3+2 2+3 ┆
0x21e00…21f00 (33, 0, 14) Sector 210f8137204141 ┆! 7 AA 3+3 ICC Access Lines 69 81 58 RCCSH Access Lines 0 33 8 formance improvements of the bandwidth will be implemented by collecting up to three PMS transactions before the actual write ┆
0x21f00…22000 (33, 0, 15) Sector 2100ff37204141 ┆! 7 AA 1 3.6.2 Projected Growth The baseline ACDN configurations will be sized to handle the projected capacities. The projected volumes and required network capacity are summarized belo┆
0x22000…22100 (34, 0, 0) Sector 2201ff37204141 ┆" 7 AAntribution from three components: - delay caused by storage strategy - write to/retrieval from disk - switching to node/session handling The major contributor is the delay caused by the applied storage strategy. However, this delay will never ┆
0x22100…22200 (34, 0, 1) Sector 2202c337204141 ┆" C7 AAexceed the time taken to perform three consecutive PMS writes. This leads to an EMH transfer time which for the majority of all PMS transactions does not exceed: 200 msec. e storage The actual EMH equipment will be tailored to mee┆
0x22200…22300 (34, 0, 2) Sector 2203ff95204141 ┆" AA 1 3.5.4 Reliability and Availability o The proposed ACDN provides Air Canada with a highly resilient network. Surviveability has been increased by provision of geographical backed-┆
0x22300…22400 (34, 0, 3) Sector 2204ff95204141 ┆" AAup network control facilities. Protection against single point failures is offered in the form of a fault-tolerant computer architecture. The distributed architecture offered provides additional advantages in form of graceful degradation. It shoul┆
0x22400…22500 (34, 0, 4) Sector 2205ff95204141 ┆" AAd be noted that the results presented in this section represents an analysis which has been based on RMA requirements far more stringent than those presented in the RFP. a. Individual Subscriber The RMA analysis for the individual subscriber ha┆
0x22500…22600 (34, 0, 5) Sector 2206ff95204141 ┆" AAs assumed a dual host in order to isolate the effect of this element. MTBF subscriber = 3.5 years MTTR subscriber = 28 min Availability subscriber = 99.9985% The RMA analysis implies that a s┆
0x22600…22700 (34, 0, 6) Sector 2207ff95204141 ┆" AApecific subscriber every 3.5 years will be without service from the ACDN for a period of 28 min. b Network The following RMA requirements are stated as those which result in the network being considered up: 1. Network capable to provide full┆
0x22700…22800 (34, 0, 7) Sector 2108b195204141 ┆! 1 AA service to all connected subscribers (except 4, below). 2. Host connections assumed dualized to remove this factor. 3. Internodal trunks backed-up by rerouting. ized as that of the Nodal Switch Processors. The bandwidth to the fixed head┆
0x22800…22900 (34, 0, 8) Sector 2209ff52204141 ┆" R AA of the proposed disk is: 236 PMS trans/sec. The same rationale as that used for the CPU capacity has been used in deciding the design capacity of the disk which results in: 425,000 trans/peak-hour. The capacity of the fixed head storage┆
0x22900…22a00 (34, 0, 9) Sector 220aff21204141 ┆" ! AA of 900 Kbytes corresponds to: 30 sec of design capacity traffic while the moveable head surface of approximately 60 Mbytes corresponds to: 35 min. Main memory buffer capacity is used to increase the efficiency of CPUs and minimize the us┆
0x22a00…22b00 (34, 0, 10) Sector 220bff21204141 ┆" ! AAage of disk storage other than for write. Transactions which require PMS service by the ACDN are transmitted to the EMH. The EMH retains a copy of the message in a main memory buffer while a mirrored write operation is conducted to the fixed head ┆
0x22b00…22c00 (34, 0, 11) Sector 220cf721204141 ┆" w! AAportion of the disk storage. The successful storage to disk results in acknowledgement to the PMS requester and forwarding of the copy retained in memory to the transport network which takes responsibility for proper delivery. eristics┆
0x22c00…22d00 (34, 0, 12) Sector 220dff37204141 ┆" 7 AA 1 As a basis for the modelling activity it has been assumed that 90% of all original PMS transactions are handled this way. The buffer storage of an EMP supports storage of the traff┆
0x22d00…22e00 (34, 0, 13) Sector 220eff37204141 ┆" 7 AAic equivalent to several seconds (approx. 55 PMS transactions per EMP). The remaining 10% will be retrieved from the fixed head part of the disk storage. Retransmission of undelivered messages and retrieval from the moveable head part of the dis┆
0x22e00…22f00 (34, 0, 14) Sector 220fff37204141 ┆" 7 AAk storage (or from magnetic tape) has for sizing purposes been assumed to be 10% of the basic PMS traffic. Additional performance improvements of the bandwidth will be implemented by collecting up to three PMS transactions before the actual write ┆
0x22f00…23000 (34, 0, 15) Sector 2200ff37204141 ┆" 7 AAoperation is performed. The write operation to fixed head takes on average 8.3 msec, max. 16.7 msec. This, together with the applied write strategy leads to the high transfer rates predicted for the EMH. The EMH transfer time is determined by a co┆
0x23000…23100 (35, 0, 0) Sector 2301ff52204141 ┆# R AAn terms of traffic volume capacities and transfer time. The rationale for the design which implements this function is presented to provide the background required to evaluate the presented information. The EMH implements a design which balances t┆
0x23100…23200 (35, 0, 1) Sector 2302ff52204141 ┆# R AAhe performance of the utilized storage media: - high speed main memory - high speed fixed head disk storage - medium speed moveable head disk storage - low speed long term magnetic tape storage The actual EMH equipment will be tailored to mee┆
0x23200…23300 (35, 0, 2) Sector 2303ff52204141 ┆# R AAt projected type "B" traffic volumes. Below are the CPUs and disk paths required to fulfill the projected growth: 1 Year Peak hour 10 3 transactions CPU MDD 300Mb ┆
0x23300…23400 (35, 0, 3) Sector 2304ff52204141 ┆# R AA volumes disk disks to EMH all (Mbytes) req'd pro'd paths 85 38.9 87.5 156 1 2 1 1 86 42.8 96.5 172 1 2 1 1 87 47.2 106.2 189 2 2 1 1 88 51.8 116.6 208 2 2 1 2 89 57.2 128.9 228 2 2 1 2 90 62.6 141.1 251 2 2 1 2 91 69.1 155.5 27┆
0x23400…23500 (35, 0, 4) Sector 23051f52204141 ┆# R AA6 2 2 1 2 * mirrored 3.5.1.4 Internodal Trunk Utilization The utilization on the internodal trunks has been chosen as: 75 per cent This high utilization factor was decided upon taking the follow┆
0x23500…23600 (35, 0, 5) Sector 2306ff52204141 ┆# R AA 1 The bandwidth of one CPU, i.e. the maximum number of PMS transactions one CPU can handle in a given CPU is: 55 PMS trans/sec To allow for acknowledgement handling, fixed to m┆
0x23600…23700 (35, 0, 6) Sector 2307ff52204141 ┆# R AAoveable head operations, checkpointing, retention of undelivered transactions, manual recovery of garbled messages, the design capacity per CPU is decided as 50% of the bandwidth or 100,000 PMS trans/peak-hour. Each Electronic Mail Processor┆
0x23700…23800 (35, 0, 7) Sector 2208ff52204141 ┆" R AA (EMP) will be equipped with from 2 to 3 CPUs as required to support the allocated traffic load. The EMPs are each provided with 512 Kwords of memory; memory which is utilized as that of the Nodal Switch Processors. The bandwidth to the fixed head┆
0x23800…23900 (35, 0, 8) Sector 23094d00204141 ┆# M AA internal network control traffic is on average 200 bytes. ected 1991 transaction volume. Note, however, that this capacity may be increased by a factor of three to four by a cluster of four co-located nodes. form the basis f┆
0x23900…23a00 (35, 0, 9) Sector 230aff3f204141 ┆# ? AA 1 3.5.2 Gateway The Air Canada "Gateway" has been included as part of the Toronto node by provision of dedicated ACNC LTUs. The total bandwidth proposed between the existing ACNC ┆
0x23a00…23b00 (35, 0, 10) Sector 230bff3f204141 ┆# ? AAand the ACDN is: 48 Kbps. The bandwidth has been achieved by 5 LTUs each emulating 4 normal 2400 bps access lines which provide a transfer capacity of: 50K transactions per peak hour. This traffic corresponds to 10 per cent of the capaci┆
0x23b00…23c00 (35, 0, 11) Sector 230cff3f204141 ┆# ? AAty of a fully equipped NSP. The integration of the Gateway into the node leads to a migration plan which is capable of being adjusted to substantial variations in workloads. The proposed "Gateway" capability has its response time characteristics┆
0x23c00…23d00 (35, 0, 12) Sector 230dff3f204141 ┆# ? AA in common with other node elements. Thus, the major elements in end-to-end response time for transactions which are exchanged between the old and the new network are: 1 Access network delays 2 Nodal delays 3 Internodal trunk delay 4 Gateway ┆
0x23d00…23e00 (35, 0, 13) Sector 230eff3f204141 ┆# ? AAtrunk delay 5 ACNC delay 6 Host delays Elements 1,5 and 6 corresponds to the delays existing at present, while 2, 3, and 4 are additional delays. The gateway trunk will represent the major contribution in additional delay irrespective of selec┆
0x23e00…23f00 (35, 0, 14) Sector 230fb83f204141 ┆# 8? AAted trunk speed. Selection of e.g. 2400 bps would lead to additional response time of average 1.2 sec. (95%: 2.4 sec.) while 9600 bps leads to average .4 sec. (95%: .7 sec.). ffic for periods where an access line is temporarily out-of-service. ┆
0x23f00…24000 (35, 0, 15) Sector 2300ff52204141 ┆# R AA 1 3.5.3 EMH Modelling The EMH provides a central store-and-forward switching service of the ACDN. This section presents the results of the performance analysis of the proposed EMH i┆
0x24000…24100 (36, 0, 0) Sector 2401ff00204141 ┆$ AA 1 The aim is twofold. Firstly, to remove the subscriber's awareness of short variations in Air Canada s computing resources; secondly, to protect the internodal trunk network agains┆
0x24100…24200 (36, 0, 1) Sector 2402ff2a204141 ┆$ * AAt excessive load conditions caused by retransmissions and thus avoid influencing the service provided to other users. The following summarizes the memory mapping of the exemplified NSP: Programs - DAMOS 43K ┆
0x24200…24300 (36, 0, 2) Sector 2403ff2a204141 ┆$ * AA - Application 103K Data - DAMOS 93K - Application o tables 10K o 3000 CRT 48K SCBs, 2 each 72K o 1500 other sub's 24K SCB's, 1 eac┆
0x24300…24400 (36, 0, 3) Sector 2404a32a204141 ┆$ #* AAh 18K 172K - Buffers o 180 x 64 bytes 6K o 540 x 512 bytes 138K 144K 512K ssages and acknowledges the NCC in such cases. The SCS automatically issues a retrieval req┆
0x24400…24500 (36, 0, 4) Sector 2405ff00204141 ┆$ AA 1 3.5.1.4 Internodal Trunk Utilization The utilization on the internodal trunks has been chosen as: 75 per cent This high utilization factor was decided upon taking the follow┆
0x24500…24600 (36, 0, 5) Sector 2406ff00204141 ┆$ AAing into consideration: - minimize number of internodal trunks - evaluate additional delay caused by high utilization versus transmission and queueing delays on access lines - usage of trunk groups advantages due to the better service which r┆
0x24600…24700 (36, 0, 6) Sector 2407ff00204141 ┆$ AAesults from a multiserver environment. The effective data utilization has been estimated as: 81.5 per cent. This utilization factor excludes the ACDN communication header, internal end-to-end acknowledgements, network control traffic and doe┆
0x24700…24800 (36, 0, 7) Sector 2308ff00204141 ┆# AAs as such only include the data entering the ADCN. The communication header has for sizing purposes been set to 20 bytes and excludes a trailer of 3 bytes. This accounts for about half of lost bandwidth. Furthermore, it has been assumed that the┆
0x24800…24900 (36, 0, 8) Sector 2409ef3f204141 ┆$ o? AA The maximum capacity corresponds to more than the double of the projected 1991 transaction volume. Note, however, that this capacity may be increased by a factor of three to four by a cluster of four co-located nodes. form the basis f┆
0x24900…24a00 (36, 0, 9) Sector 240aff33204141 ┆$ 3 AA 1 3.5.1.3 Memory Utilization The buffer capabity required in order to support the designed transfer rate per Nodal Switch Processor is: 120 buffers. The basic assumption behi┆
0x24a00…24b00 (36, 0, 10) Sector 240bff33204141 ┆$ 3 AAnd this is that each buffer holds one transaction or that three buffers may hold one RCCSH interaction. Secondly, it reflects the traf- mix represented by: - 4 internodal trunks - 60 access lines together with a requirement that retransmiss┆
0x24b00…24c00 (36, 0, 11) Sector 240cff00204141 ┆$ AAion caused by "buffer unavailable" should be required for less than .1 per cent of all transactions. The above number of buffers excludes any buffers permanently allocated for input handling for the purpose of reducing input processing time. Furt┆
0x24c00…24d00 (36, 0, 12) Sector 240dff33204141 ┆$ 3 AAhermore, this capacity does not properly reflect the impacts of the proposed type "B" handling. The proposed buffer capacity has been sized to include this handling. The proposed NSPs are for all proposed ACDN nodes provided with buffer capacity i┆
0x24d00…24e00 (36, 0, 13) Sector 240eff33204141 ┆$ 3 AAn excess of the minimum required. Generally, all memory space which is not permanently allocated to programs, data, and tables is allocated as buffers. This leads to a buffer utilization of: 25 per cent for the typical NSP. The reason for┆
0x24e00…24f00 (36, 0, 14) Sector 240fff33204141 ┆$ 3 AA providing this additional memory capacity has been a trade-off of price versus the additional benefits derived: - Additional buffer capacity may be used to retain type "B" traffic for periods where an access line is temporarily out-of-service. ┆
0x24f00…25000 (36, 0, 15) Sector 24008733204141 ┆$ 3 AA- The additirnal nodal buffer capacity may be used to buffer transactions to applications which are temporarily out-of-service. plements these functions is presen- ted to provide the background required to evaluate the presented information. The m┆
0x25000…25100 (37, 0, 0) Sector 2501ff00204141 ┆% AAodelling presented covers the RFP requirements as well as the new Corporate Service Information Host in Dorval. 3.5.1.1 End-to-End Response Time The end-to-end response times expected for the different types of ACDN traffic are summarized below:┆
0x25100…25200 (37, 0, 1) Sector 2502ff00204141 ┆% AA Response TYPE A TYPE B RCCSH time (sec) Req. ACDN Req. ACDN Req. ACDN average - 1.2 - 2.1 - 6.0 85% 2.5 1.7 5 2.5 - 10.8 95% 5┆
0x25200…25300 (37, 0, 2) Sector 2503ff00204141 ┆% AA 2.7 - 3.5 - 17.4 Excluding the contributions from resources outside ACDN, i.e. terminal and host environments leads to the following ACDN round trip delays: Round Trip Type A Type B RCCSH (sec) average┆
0x25300…25400 (37, 0, 3) Sector 25048900204141 ┆% AA .2 .5 .7 85% .3 .6 .8 95% .5 .8 1.0 rack on undelivered PMS messages and acknowledges the NCC in such cases. The SCS automatically issues a retrieval req┆
0x25400…25500 (37, 0, 4) Sector 2505ff3f204141 ┆% ? AA 1 3.5.1.2 Processor Utilization and Capacity The processing time required to switch a transaction is: 15.4 msec. Thus, the switching capacity of a Nodal Switch Pro- cessor (N┆
0x25500…25600 (37, 0, 5) Sector 2506ff3f204141 ┆% ? AASP) equipped with four CPUs is: 200 packets/sec. The CPU utilization upon which the proposed ACDN configurations are based is: 61 per cent This utilization caters for the additonal handling required by the proposed ACDN virutal protoco┆
0x25600…25700 (37, 0, 6) Sector 2507ff3f204141 ┆% ? AAl handling, emulation, acknowledgements and network control. Furthermore, the choice of this low utilization factor reflects an intent to provide Air Canada with a net- work with built-in allowance for later increases in processing requirements. ┆
0x25700…25800 (37, 0, 7) Sector 2408ff3f204141 ┆$ ? AA Thus, the capacity of each NSP equipped with four equal CPUs is 100 incoming transactions/sec. whether received from a terminal or a host. This leads to a total maximum capacity of an ACDN node of: 1100-1200 incoming transactions/sec.┆
0x25800…25900 (37, 0, 8) Sector 2509ff95204141 ┆% AAwth capacity beyond the 1991 projected requirements. The results presented herein have been based on analytic distributions reflecting specific properties of the ACDN. Appendix D provides the modelling and analytical results which form the basis f┆
0x25900…25a00 (37, 0, 9) Sector 250aff3f204141 ┆% ? AAor the performance values presented in this section. The following constitute the common assumptions upon which the performance factors of the ACDN have been calculated: - Poisson arrival pattern - Service times exponentially distributed - All┆
0x25a00…25b00 (37, 0, 10) Sector 250bff95204141 ┆% AA servers equally loaded - All servers have same mean service time - First-in/First-out dispatching strategy - No items leave queue A conservative design policy has been adhered to in order to provide Air Canada with a sound baseline network imp┆
0x25b00…25c00 (37, 0, 11) Sector 250cff95204141 ┆% AAlementation with built-in investment protection. No attempts have been made to achieve a minimal hardware solution which could only satisfy AIR CANADA's current needs and as such present a risk factor. The analysis and trade-offs presented in thi┆
0x25c00…25d00 (37, 0, 12) Sector 250dff95204141 ┆% AAs section will be further refined and detailed as part of the initial Functional Specification phase should Christian Rovsing be the selected contractor. This critical project activity must be conducted in close co-operation with Air Canada personn┆
0x25d00…25e00 (37, 0, 13) Sector 250e0a95204141 ┆% AAel. ic volumes account for 10% of all traffic of the ACDN; thus, only a minor increase results on the load of the transport network by a central solution, - a requirement for long term storage in the order of one to two months together with the vo┆
0x25e00…25f00 (37, 0, 14) Sector 250fff3f204141 ┆% ? AA 1 3.5.1 Node Modelling The nodes of the ACDN provide the termination of connected hosts and access lines to terminal concentra- tors. This section presents the results of the perfo┆
0x25f00…26000 (37, 0, 15) Sector 2500ff3f204141 ┆% ? AAr- mance analysis for the proposed nodes in terms of volume capacities and transfer times. The rationale for the design which implements these functions is presen- ted to provide the background required to evaluate the presented information. The m┆
0x26000…26100 (38, 0, 0) Sector 2601c6c2204141 ┆& FB AArives. PMS traffic is spooled to a fixed head disk, thus avoiding efficiency derating caused by disk head movements. A full track is copied at a time to the moveable part of the disk. co-ordinated with the local SCS and check-pointed to dis┆
0x26100…26200 (38, 0, 1) Sector 2602ff95204141 ┆& AA 1 Part of EMS is to provide accountability for messages in the sense that the EMN is responsible for proper PMS message delivery once acknowledged is received by EMH. A network ses┆
0x26200…26300 (38, 0, 2) Sector 2603ff95204141 ┆& AAsion is established between the EMS and the proper destinations. The network provides the same type of service to this type of connection as to other types. The System Control Software (SCS) plays an important role in providing this network servi┆
0x26300…26400 (38, 0, 3) Sector 2604ff95204141 ┆& AAce. The SCS enters the scene only where the node has been unable to deliver a PMS message, e.g. broken connection. The SCS keeps track on undelivered PMS messages and acknowledges the NCC in such cases. The SCS automatically issues a retrieval req┆
0x26400…26500 (38, 0, 4) Sector 2605ff95204141 ┆& AAuest to the EMH once the connection has been re-established. Facilities are included as part of the EMS which can support dedicated EMH operators in correction of faulty PMS messages via an interactive dialogue. These facilities are based on subse┆
0x26500…26600 (38, 0, 5) Sector 2606e495204141 ┆& d AAts of the FIKS implementation which provide similar services. Statistics collection for this special service is the responsibility of the Access Software, e.g. TAS Data are collected and retained as for other sessions. 4.4 Network Management Soft┆
0x26600…26700 (38, 0, 6) Sector 2607ff95204141 ┆& AA 1 3.5 Performance The results of the performance modelling are presented this section. It is shown how the proposed ACDN fulfills the performance requirements of the RFP. Important┆
0x26700…26800 (38, 0, 7) Sector 2508ff95204141 ┆% AA design rationales are presented. The data provided by Air Canada has been used as input to derive realistic configurations, both the baseline as projected 86 thru 91 configurations. Furthermore, it is shown how the proposed network provides a gro┆
0x26800…26900 (38, 0, 8) Sector 26090895204141 ┆& AA pdate and check-out to be performed on a network element operating independent of the live network. the NSS are: - virtual connection service, - permanent virtual connection services, - datagram service. The CCITT X.25 Recommendation is em┆
0x26900…26a00 (38, 0, 9) Sector 260affc2204141 ┆& B AA 1 3.4.5 Electronic Mail Software Package The Electronic Mail Software Package implements the protected message service (PMS) provided by the ACDN. A central PMS data base was deci┆
0x26a00…26b00 (38, 0, 10) Sector 260bffc2204141 ┆& B AAded to be the most feasible implementation. Several considerations were taken into account: - store-and-forward mechanisms where PMS messages were stored on each nodal disk leads to longer response times, - a solution was considered by which t┆
0x26b00…26c00 (38, 0, 11) Sector 260cffc2204141 ┆& B AAhe source node took PMS responsibility but this leads to a solution where disks became a critical node element, - a requirement for unmanned operation of nodes leads towards a central solution as disks are avoided for this purpose at the nodes, ┆
0x26c00…26d00 (38, 0, 12) Sector 260dffc2204141 ┆& B AA- a central EMH leads to one additional hop for PMS traffic due to the proposed network topology; however, with the proposed internodal trunk speed of 56 Kbps only a neglible additional delay is added to the all over PMS response time. - the PMS t┆
0x26d00…26e00 (38, 0, 13) Sector 260effc2204141 ┆& B AAraffic volumes account for 10% of all traffic of the ACDN; thus, only a minor increase results on the load of the transport network by a central solution, - a requirement for long term storage in the order of one to two months together with the vo┆
0x26e00…26f00 (38, 0, 14) Sector 260fffc2204141 ┆& B AAlumes of traffic considered leads to magnitic tape as the most feasible mass storage for this purpose; this implies manned operation or additional load of the transport network when long term storage file transfer takes place. The PMS data base ma┆
0x26f00…27000 (38, 0, 15) Sector 2600ffc2204141 ┆& B AAintenance is based on the same technique as employed on the store-and-forward message switching developed by Christian Rovsing on the FIKS program. The EMS employs "core-switching" of PMS transactions, which results in a reduced load on the disk d┆
0x27000…27100 (39, 0, 0) Sector 2701ff52204141 ┆' R AAto establish a connection with a participant of the network. The NCS is responsible for establishing this connection and in assigning the proper network resources. The connection creation is co-ordinated with the local SCS and check-pointed to dis┆
0x27100…27200 (39, 0, 1) Sector 2702ff52204141 ┆' R AAk, both at the NCC and at the SCS, whether node, NMH or EMH. Re-establishment of a lost connection caused by e.g. trunk failure is in the first hand the responsibility of the SCS. The SCS uses its locally stored session data in order to provide t┆
0x27200…27300 (39, 0, 2) Sector 27037552204141 ┆' uR AAhis service. Failing to re-establish this connection causes the SCS to inform the NCC operators via the NCS. n environment and with facilities which can assist these people in conducting a safe network operation. The facilities made available to┆
0x27300…27400 (39, 0, 3) Sector 2704ff95204141 ┆' AA 1 The implementation of a geographical back-up NCC is based on the implementation by Christian Rovsing on the Danish FIKS program. A special protocol ensures synchronization between ┆
0x27400…27500 (39, 0, 4) Sector 2705ff95204141 ┆' AAthe two NCC centers. The communication between the two NCCs is through the transport network of the ACDN. Included in this package is also various special test and trace facilities. These include provision for monitoring all traffic in and out o┆
0x27500…27600 (39, 0, 5) Sector 2706ff95204141 ┆' AAf a host, a node or an internodal trunk. They include a possibility of dumping memory of system elements and displaying all buffers. The test facilities provided as part of the ACDN is described as part of Chapter 4. 3.4.4 Network Management Soft┆
0x27600…27700 (39, 0, 6) Sector 2707ff95204141 ┆' AAware Package The Network Management Host functions are included in the Network Management Software Package system. It includes the functions necessary for administrating the network i.e. Subscriber, installation and Billing Management, Topology Pl┆
0x27700…27800 (39, 0, 7) Sector 2608ff95204141 ┆& AAanning, network simulation, statistics and charging information collection. Further application subsystems and functions can be programmed by users via local or remote terminals, by means of the Software Development Environment supplied. ┆
0x27800…27900 (39, 0, 8) Sector 27096d69204141 ┆' mi AA update and check-out to be performed on a network element operating independent of the live network. the NSS are: - virtual connection service, - permanent virtual connection services, - datagram service. The CCITT X.25 Recommendation is em┆
0x27900…27a00 (39, 0, 9) Sector 270aff52204141 ┆' R AA 1 The Global Network Definition (GND) is broken down by the NCS to reflect the local configurations and resources. Thus, the NCS maintains, based on the GND, a set of definitions fo┆
0x27a00…27b00 (39, 0, 10) Sector 270bff33204141 ┆' 3 AAr each of the network systems: nodes, NCC, NMH and EMH. A copy of the local definitions is stored on the disk associated with these systems. This copy is maintained only from the NCC in order to ensure network integrity. The network definitions┆
0x27b00…27c00 (39, 0, 11) Sector 270cff33204141 ┆' 3 AA may exist in three versions in the system: Current, previous and under update. However, only the former two exists in "static" situations while the "under update" version exist in those periods, where the NCS is down-line loading a new version. ┆
0x27c00…27d00 (39, 0, 12) Sector 270dff33204141 ┆' 3 AAFacilities are provided to the NCC operators to allow them activation of any of the three versions. The NCS activates the same version in all network systems to protect network integrity. Activation of new versions takes place under local control┆
0x27d00…27e00 (39, 0, 13) Sector 270eff33204141 ┆' 3 AA by the SCS. This software is responsible in protecting existing users which have retained their old network definitions; this includes implementation of a version update mechanism which leaves unaffected sessions undisturbed. Thus, the NCS/SCS le┆
0x27e00…27f00 (39, 0, 14) Sector 270fff52204141 ┆' R AAaves the users of the network basicly transparent to system upgrades. A provision for assigning time limits to the validity of given resources is provided. This provision covers whether the resource goes active at a certain time or if it is remove┆
0x27f00…28000 (39, 0, 15) Sector 2700ff33204141 ┆' 3 AAd after a certain time period (temporary resource). The NCS plays a key role in the establishment of sessions. Two separate classes of sessions are considered: external and internal. A network session must be established whenever a user wants ┆
0x28000…28100 (40, 0, 0) Sector 2801ff52204141 ┆( R AA 1 3.4.3 Network Control Software Package The Network Control Software (NCS) plays a key role in maintaining the integrity of the ACDN network. The capability to support a geographic┆
0x28100…28200 (40, 0, 1) Sector 2802ff52204141 ┆( R AAally remote back-up NCC provides added survivability to the network. The NCS consists of software components resident in the Nodal Control Center co-operating with the distributed System Control Software components of the nodes and other computer s┆
0x28200…28300 (40, 0, 2) Sector 2803ff52204141 ┆( R AAystems of the network. Probably the most important task of the NCC is to provide the operations people with an environment and with facilities which can assist these people in conducting a safe network operation. The facilities made available to┆
0x28300…28400 (40, 0, 3) Sector 2804ff52204141 ┆( R AA these people consist of colour monitors and operational procedures aimed at providing static and dynamic information of the system. The procedures made available to the operators are based on menu selection and provides the means for obtaining a ┆
0x28400…28500 (40, 0, 4) Sector 2805ff52204141 ┆( R AAfast and efficient usage of the network control and monitoring facilities implemented. Various graphical presentations are included from a complete network picture covering hosts, all major network elements as well as feasible terminal network pre┆
0x28500…28600 (40, 0, 5) Sector 2806ff52204141 ┆( R AAsentations to diagrams presenting resource utilizations. An important role played by the NCS is that of Definition, defining external as well as internal resources. The NCS enables the NMH/NCC operator to assign a unique logical name to any netwo┆
0x28600…28700 (40, 0, 6) Sector 2807ff52204141 ┆( R AArk resource. However, the allocation of the network logical identifier is assigned by the NCS and the operator can not modify this entity; this is part of the network integrity protection facilities. The NCS is provided with software facilities wh┆
0x28700…28800 (40, 0, 7) Sector 2708ff52204141 ┆' R AAich enables operators of the NCC and NMH to modify the Global Network Definition (GND) in a dialogue form. Facilities are provided which enables files e.g. like those of the GND to be transferred from the NCC to the NMH and thus enable configuration┆
0x28800…28900 (40, 0, 8) Sector 2809ff69204141 ┆( i AAof the ACDN. The transmission media proposed are 56 Kbps internodal trunks. The services provided by the NSS are: - virtual connection service, - permanent virtual connection services, - datagram service. The CCITT X.25 Recommendation is em┆
0x28900…28a00 (40, 0, 9) Sector 280aff69204141 ┆( i AAployed on all internodal trunks. Transport service users are assigned "ports" to access the transport network at a packet level. Permanent connections are established for system control purposes while virtual connections are used for low frequency┆
0x28a00…28b00 (40, 0, 10) Sector 280bff69204141 ┆( i AA traffic, i.e. interactive and batch type of traffic. Transaction type of traffic makes use of the datagram service. Several grades of service are offered to transport service users: - priority - end-to-end acknowledge or not. The routing imple┆
0x28b00…28c00 (40, 0, 11) Sector 280cff69204141 ┆( i AAmented by the NSS supports trunk groups. This includes the ability to have a given message simultaneously transmitted on several internodal trunks within the same group. The switching of data implemented by the NSS depends on the type of connection┆
0x28c00…28d00 (40, 0, 12) Sector 280dff69204141 ┆( i AA. Transactions are "moved" in memory by the Basic Datagram Service while other connections are served by the Basic Transport Service. This minimizes the delay through the NSP and thus results in a reduction of switching memory buffers. The data ┆
0x28d00…28e00 (40, 0, 13) Sector 280eff69204141 ┆( i AAlink service is implemented in firmware. The term firmware refers to software residing in the CR80 line terminating unit, the LTU, even though this is actually software which is downlineloaded at initialization by the NSP. The firmware includes a b┆
0x28e00…28f00 (40, 0, 14) Sector 280f2969204141 ┆( )i AAuffer manager and a line handler. g job-service may be implemented according to existing standards (ISO/TC97/SC16 N628 or later). Also, a Virtual Terminal Protocol is proposed for the ACDN. Several possibilities have been looked at. CCITT define┆
0x28f00…29000 (40, 0, 15) Sector 28006269204141 ┆( bi AA 1 Figure III 3.4-4 d these standards will be a so-called scroll-mode VT offering user selectable PAD-functions described by a set of parameters. However, this will not be suf┆
0x29000…29100 (41, 0, 0) Sector 2901ff3f204141 ┆) ? AAficient to cover the needs for the terminals to be supported in the backbone network. Consequently the design will be extended with functions necessary to cover the level of terminal service needed for VDU s like UTS 400 and IBM 3270 BSC, the line ┆
0x29100…29200 (41, 0, 1) Sector 2902ff3f204141 ┆) ? AAof services supported thus will be as described for the terminal class "formmode" described in ISO/TC97/SC16 N666 (ECMA/TC23/81/53). The Network Access Software plays a special role in this context. As illustrated in Figure III 3.4-1 they interfa┆
0x29200…29300 (41, 0, 2) Sector 2903ff3f204141 ┆) ? AAce the underlying transport network like the TAS software. The structure of this access software is very similar to the TAS as is the role. This explains the feasibility of integrating the access software and thus make better usage of the available┆
0x29300…29400 (41, 0, 3) Sector 2904ff3f204141 ┆) ? AA resources and mechanisms. The Internal Network Access Software Package implements the network function for interconnecting the old ACNC network and the new network. Operating a number of 2.4 or 9.6 Kbps, the Gateway acts against the ACNC as mul┆
0x29400…29500 (41, 0, 4) Sector 2905ff3f204141 ┆) ? AAtiple ICC's. Against the new data network the Gateway maps interactive-, printer-, and host-traffic into the virtual protocols for interactive terminals and file transfer, respectively. The External Network Access Software Package plays a similar┆
0x29500…29600 (41, 0, 5) Sector 29068169204141 ┆) i AA role in mapping external connections onto the internal. The following networks are interfaced: - ARINC - SITA - CNT services wanted. Apart from the two services mentioned it is the intention of Christian Rovsing to implement other necessary v┆
0x29600…29700 (41, 0, 6) Sector 2907ff69204141 ┆) i AA 1 3.4.2 Nodal Switching Software Package The Nodal Switching software implements the bridging between the software of the other packages, whether between entities of the TAS (suppor┆
0x29700…29800 (41, 0, 7) Sector 2808ff69204141 ┆( i AAting a given terminal type) and entities of the HAS (supporting given host type) or to a network provided service as implemented by e.g. EMS in form of protected message service. The NSS is also the software which directly interconnects the nodes ┆
0x29800…29900 (41, 0, 8) Sector 2909ff69204141 ┆) i AAnetwork, at least not as yet. Actual equipment protocols attached to the (ACDN), network must be mapped onto the virtual protocol supported by the network. Future equipment should be designed to work directly with the virtual protocols in the net┆
0x29900…29a00 (41, 0, 9) Sector 290aff69204141 ┆) i AAwork. By providing a baseline for future communication via the network, the virtual protocols are the vehicle for commonality in the ACDN. In the selection of the virtual protocols for the network, one must investigate carefully the trends of the┆
0x29a00…29b00 (41, 0, 10) Sector 290bff69204141 ┆) i AA related standards in the world today. The FTP and the ECMA VTP presently appear to be the most commonly adopted in Europe. Should this not be so for the Canadian environment, other virtual protocols may be selected for the ACDN. The File Transf┆
0x29b00…29c00 (41, 0, 11) Sector 290cff69204141 ┆) i AAer Protocol, FTP, represents a virtual network protocol for bulk transfers. The implementation in the backbone network, which is supposed to enable multihost access to remote facilities like printers and cardreaders will be the relevant parts of FT┆
0x29c00…29d00 (41, 0, 12) Sector 290d4f69204141 ┆) Oi AAP-B (80), also known as blue book (Data Comm. Protocols Unit, NPL, G3). xternal Network Access Software (ENAS) - Internal Network Access Software (INAS) An important role of these packages is to implement the virtual protocols required t┆
0x29d00…29e00 (41, 0, 13) Sector 290eff3f204141 ┆) ? AA 1 The line of services that is foreseen to be adopted in an initial implementation will be the Host-to-Host transfer of files at a low level, i.e. printer files, whereas at a later s┆
0x29e00…29f00 (41, 0, 14) Sector 290fff3f204141 ┆) ? AAtage a full implementation including job-service may be implemented according to existing standards (ISO/TC97/SC16 N628 or later). Also, a Virtual Terminal Protocol is proposed for the ACDN. Several possibilities have been looked at. CCITT define┆
0x29f00…2a000 (41, 0, 15) Sector 2900ff3f204141 ┆) ? AAs a low level virtual terminal standard by the three standards X.3, X.28 and X.29. Combined these standards will be a so-called scroll-mode VT offering user selectable PAD-functions described by a set of parameters. However, this will not be suf┆
0x2a000…2a100 (42, 0, 0) Sector 2a01ff3f204141 ┆* ? AAnnections. A Basic Datagram Service (BDS) will be implemented which exploits the CR80 hardware and provides the means by which high volume transaction oriented connections are supported. Fundamental to the BDS is that it only copies data to NSP mem┆
0x2a100…2a200 (42, 0, 1) Sector 2a02ff3f204141 ┆* ? AAory once. The Basic Services provides a queue driven environment within the normal DAMOS event driven environment. The File Management System and Terminal Management System are used to handle standard files and operator terminals, e.g. those of t┆
0x2a200…2a300 (42, 0, 2) Sector 2a03173f204141 ┆* ? AAhe NMH and NCC. e 1984-1985 may in 1986 be sublimated into the role of terminating new terminal equipment. The partitioning of the computer system into a specific PU configuration does not impact ACDN communications software. It provides an archi┆
0x2a300…2a400 (42, 0, 3) Sector 2a04703f204141 ┆* p? AA 1 Figure III 3.4-3 ACDN SOFTWARE processing resources fail. Furthermore, the redundant hardware design allows even major configuration changes to take place while the remaini┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff69204141 ┆* i AA 1 3.4.1 Access Software Packages To generalize the functionality of the interfaces, the network provides service to interactive terminals and supports bulk transfers. These servic┆
0x2a500…2a600 (42, 0, 5) Sector 2a06ff69204141 ┆* i AAes are provided by virtual protocols residing in the network. In general the choice of virtual protocols depends on the services wanted. Apart from the two services mentioned it is the intention of Christian Rovsing to implement other necessary v┆
0x2a600…2a700 (42, 0, 6) Sector 2a07ff69204141 ┆* i AAirtual protocols on request. For instance a standardized graphics protocol or a protocol covering the very high speed classes satellite-communication. The backbone network proposed provides the following: - Packet switching (CCITT's X.75) for i┆
0x2a700…2a800 (42, 0, 7) Sector 2908ff69204141 ┆) i AAnterfacing public networks to ACDN - Virtual File transfer, (NPL's File Transfer Protocol) - Virtual Terminal Interaction (ECMAs Virtual Terminal Protocol) A virtual protocol is one, which is not used by any actual equipment attached to the ┆
0x2a800…2a900 (42, 0, 8) Sector 2a09ff69204141 ┆* i AAseven-layer Open Systems Interconnection model presented. Figures 3.4-1 and 3.4-2 depicts this mapping. The application layer of the OSI model is represented by the packages implementing value added services to the network, i.e. - Network Contr┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0adb69204141 ┆* [i AAol Software - Network Management Software - Electronic Mail Software These services uses the lower layers implemente the remaining packages to make the services offered available to all users of the network. t not least, integration of this ca┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0ba869204141 ┆* (i AA 1 Figure III 3.4-1 ACDN SOFTWARE PACKAGES Fig. III 3.4-2 ACDN SOFTWARE STRUCTURE odes and EMH are configured to provide the high level of fault-tolerance characteristic┆
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cff3f204141 ┆* ? AA 1 The presentation and session layer of the OSI model is encompassed in the Network Interface Environment as implemented by the following software packages: - Host Access Software ┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0dff3f204141 ┆* ? AA (HAS) - Terminal Access Software (TAS) - External Network Access Software (ENAS) - Internal Network Access Software (INAS) An important role of these packages is to implement the virtual protocols required t┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff3f204141 ┆* ? AAo map any network user into a valid host end user. The transport and network layer of the OSI model are encompassed by the Nodal Switch Software (NSS) which furthermore includes the firmware implementing the data link layer. The CR80 DAMOS provi┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0fff3f204141 ┆* ? AAdes the operating system upon which the ACDN will be implemented. DAMOS provides all the general tools for management of the CR80 resources, CPUs and memory, processors (PUs) and devices. A resource allocation is implemented which ensures that no ┆
0x2af00…2b000 (42, 0, 15) Sector 2a00ff3f204141 ┆* ? AAprocess is capable of blocking all available resources managed by DAMOS. Data integrity and privacy is protected by kernelised mechanisms. The Basic Transport Service (BTS) provides the vechicle for implementing interactive and batch oriented co┆
0x2b000…2b100 (43, 0, 0) Sector 2b01ff95204141 ┆+ AAbusses, power supplies, and LTU's. To fully understand the CR80 fault tolerance concept, the Equipment Characteristics Chapter should be read. The CR80 architecture allows the open ended growth in the equipment and hence in processing power, whic┆
0x2b100…2b200 (43, 0, 1) Sector 2b02ff95204141 ┆+ AAh is so crucial in a dynamic transaction oriented environment. The great flexibility in the hardware configuration capabilities supports the graceful evolution of ACDN configurations. As an example, the Gateway equipment which is being used in th┆
0x2b200…2b300 (43, 0, 2) Sector 2b03ff95204141 ┆+ AAe transition phase 1984-1985 may in 1986 be sublimated into the role of terminating new terminal equipment. The partitioning of the computer system into a specific PU configuration does not impact ACDN communications software. It provides an archi┆
0x2b300…2b400 (43, 0, 3) Sector 2b04ff95204141 ┆+ AAtecture which by itself offers several levels of degraded service should one or more of the participating processing resources fail. Furthermore, the redundant hardware design allows even major configuration changes to take place while the remaini┆
0x2b400…2b500 (43, 0, 4) Sector 2b052795204141 ┆+ ' AAng system is fully operational. vice types are provided by the NSS to the Network Interface Environment: - datagram type of service - switched virtual connection - permanent virtual connection - priority - end-to-end acknowledge - end-to-en┆
0x2b500…2b600 (43, 0, 5) Sector 2b06ff69204141 ┆+ i AA 1 3.4 Proposed Software Packages This section presents an overview of the proposed software packages. The detailed description for each package is found in chapter 6. The software┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff69204141 ┆+ i AA proposed have been collected in a number of packages. The packages have been based upon func- tionality and a requirement of a "minimal" interface. The packages consist of components based on the same criteria. Furthermore, the software packages┆
0x2b700…2b800 (43, 0, 7) Sector 2a08ff69204141 ┆* i AA play an important role in providing visibility to the Air Canada's Technical Management during the implementation phase of the ACDN. Before embarking on a more detailed description of the individual packages being proposed, is a mapping onto the ┆
0x2b800…2b900 (43, 0, 8) Sector 2b09ff95204141 ┆+ AAresent ACNC network to the baseline ACDN network carrying and terminating all traffic. The External Networks termination and handling have been moved from the EMH for several reasons: - They present a communications environment and do as such lo┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0aff95204141 ┆+ AAgically belong to the terminal access type of software. - Apart from the fact that they today carry type "B" traffic only, there seems in our opinion not to be a reason for a termination at the EMH. - Last, but not least, integration of this ca┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0bff95204141 ┆+ AApability into the node allows termination of lines from these external networks at any of the proposed nodes. All critical elements of the ACDN, i.e. the NCC, nodes and EMH are configured to provide the high level of fault-tolerance characteristic┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0cff95204141 ┆+ AA of a CR80 configuration. The NMH is basically configured as a simple non-redundant processor reflecting the fact that this element is not critical to the operation and functioning of the proposed network. Co-located network elements are configur┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff95204141 ┆+ AAated as a complete CR80 system with all processors integrated by common high speed local area suprabusses. Regardless of the configuration, however, the basic processor, memory modules, and device controllers are the same. The detailed configuratio┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0eff95204141 ┆+ AAns are described in Chapter 5 of this document. The CR80 hardware configuration comprises a number of loadsharing CPU's, grouped together in processing units, PU's, with up to 5 CPU's per PU and up to 1 Mwords. Multiple PU's may be interconnecte┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0fdaa1204141 ┆+ Z! AAd by a group of 16Mbps suprabusses. Some PU's may be loadsharing equally, some may carry out special functions while still others may be standby units ready to be activated to substitute currently active PU's. ic on magnetic tapes. processor. Th┆
0x2bf00…2c000 (43, 0, 15) Sector 2b00ff95204141 ┆+ AA 1 The hardware is continuously monitored and controlled via a serial Configuration Control bus extending from a Watchdog to all switchable and/or monitored assemblies, such as CPUs, ┆
0x2c000…2c100 (44, 0, 0) Sector 2c01ffa1204141 ┆, ! AAgement Host and an Electronic Mail Host. The equipment used is based on the CR80 computer series, designed and manufactured by Christian Rovsing. The CR80 is configurable and satisfies the broad range of applications of the ACDN, present and futur┆
0x2c100…2c200 (44, 0, 1) Sector 2c02ffa1204141 ┆, ! AAe, providing a fault tolerant data-, packet-, and message switching network. An overview of the specific system configurations is shown in Figure III 3.3-1. It reflects the baseline network for 1985 and illustrates the presence of the generic net┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ffa1204141 ┆, ! AAwork elements positioned in accordance with the concept network provided by Air Canada. The proposed ACDN nodes, NMH and EMH have all been configured as selfcontained computer systems. The NCC facility has in the baseline network been integrated h┆
0x2c300…2c400 (44, 0, 3) Sector 2c04ffa1204141 ┆, ! AAardwarewise with the Toronto node and a back-up NCC facility is proposed as part of the Montreal node. Deviation from the concept network are found in the areas of the Air Canada Gateway to the existing ACNC and in the handling of the external net┆
0x2c400…2c500 (44, 0, 4) Sector 2c0528a1204141 ┆, (! AAworks, e.g. SITA, ARINC and CNT. vice types are provided by the NSS to the Network Interface Environment: - datagram type of service - switched virtual connection - permanent virtual connection - priority - end-to-end acknowledge - end-to-en┆
0x2c500…2c600 (44, 0, 5) Sector 2c067aa1204141 ┆, z! AA 1 Figure III 3.3-1 PROPOSED NODE NETWORK smitted between nodes on internodal trunk groups. The routing of data is handled by providing each message/packet with a routing hea┆
0x2c600…2c700 (44, 0, 6) Sector 2c07ff95204141 ┆, AA 1 Both of these have for various reasons been integrated into the nodes. The Gateway has been integrated into the node due to its commonality with the TAS package interfacing acces┆
0x2c700…2c800 (44, 0, 7) Sector 2b08ff95204141 ┆+ AAs lines to present types of Air Canada equipment but also caused by the fairly low amount of traffic anticipated on this network element. This integration leads to a more clean migration approach from the initial ACDN network co-existing with the p┆
0x2c800…2c900 (44, 0, 8) Sector 2c09ff95204141 ┆, AAservice, administrative billing and planning services and development capabilities. The network wide resource and control facilities are provided by the Network Control Software (NCS) of the NCC supported by the System Control Software (SCS) loca┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0aff95204141 ┆, AAted in the nodes. The SCS implements a local system wide resource management by centralized algorithms in the local Nodal Control Processor assisted by layer wide resource management entities in all of the Processor Units of a node. The protected ┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0bff95204141 ┆, AAmessage service is provided by the Electronic Mail Software (EMS) of the EMH, the administrative and planning services are provided by the Network Management Software (NMS) while the development capabilities is provided by standard development tools┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0cff95204141 ┆, AA, using the processor equipment of the NMH. The control software in form of NCS and SCS are special since neither support transmission of user data, instead they control the network respectively the local node configuration. The NCS uses permanen┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0dff95204141 ┆, AAtly allocated connections and resources in the network to control the remaining part of the network topology. The NCS uses the remaining software packages to distribute and retrieve configuration control information and statistics. The NCS plays an┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff95204141 ┆, AA active role in re-establishment of connections between users (sessions) when such a connection has been temporarily lost. The Electronic Nail Software (EMS) implements the protected message service (PMS). PMS is a store-and-forward service prov┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0ff195204141 ┆, q AAided by the network. Basically EMS maintains the PMS traffic database of the EMH. It ensures that undelivered messages are retained for later delivery. Furthermore, it maintains a long term storage of PMS traffic on magnetic tapes. processor. Th┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00ffa1204141 ┆, ! AA 1 3.3 Proposed Hardware Equipment A common computer architecture is used to implement all the computerized functions of the ACDN. This includes two NCCs, three nodes, a Network Mana┆
0x2d000…2d100 (45, 0, 0) Sector 2d013069204141 ┆- 0i AAer cost-effective computing environment. cation. The nodes provide the termination points to equipment of all external environments whether in the form of host data channels or communication lines to terminals and to other networks. This allows A┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff37204141 ┆- 7 AA 1 Communications Environment The Communications Environment provides in a sense the backbone services of the ACDN. It controls the interconnections between the users and provides t┆
0x2d200…2d300 (45, 0, 2) Sector 2d03ff37204141 ┆- 7 AAhe data transportation facilities. It is implemented by mutually interconnected Nodal Switch Software (NSS) executed in Nodal Switch Processors. The NSS implements a transport network by providing transport, network, data link, and physical link ser┆
0x2d300…2d400 (45, 0, 3) Sector 2d04ff37204141 ┆- 7 AAvices as presented in the model for Open Systems Interconnection. The NSS implements a bridge between the different entities of the various access software, HAS, TAS, INAS, ENAS. The NSS appears as a standard transport network to these higher lay┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff37204141 ┆- 7 AAers. The following essential service types are provided by the NSS to the Network Interface Environment: - datagram type of service - switched virtual connection - permanent virtual connection - priority - end-to-end acknowledge - end-to-en┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff37204141 ┆- 7 AAd non-acknowledge The transportation provided by NSS is carried out by means of data units in form of packets transmitted between nodes on internodal trunk groups. The routing of data is handled by providing each message/packet with a routing hea┆
0x2d600…2d700 (45, 0, 6) Sector 2d07aa37204141 ┆- *7 AAder and employment of an efficient routing strategy. Unrecoverable errors are handed over to network control/system control software through the layer managers. ty of terminal types: - CRTs - types 405, 406, 407, 408 - Flight Informatio┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff95204141 ┆, AA 1 Network Services Environment The Network Services Environment provides first of all global control facilities, secondary added application services in form of protected message ┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff69204141 ┆- i AAonments described in the previous section. It consists of the interfacing hardware and software required to support the integration to external elements; active in form of e.g. participating hosts providing services and co-operating with the netwo┆
0x2d900…2da00 (45, 0, 9) Sector 2d0aff69204141 ┆- i AArk, passive in form of e.g. attachments like the present Air Canada terminal equipment. The software which implements these capabilities are: - Host Access Software (HAS) - External Network Access Software (ENAS) - Ter┆
0x2da00…2db00 (45, 0, 10) Sector 2d0bff69204141 ┆- i AAminal Software (TAS) - Internal Network Access Software (INAS) The HAS implements access methods which operate at mainframe data channel speed while the TAS implements access methods which operate with communication line┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0cff69204141 ┆- i AAs. The network access software like the TAS, implements communication line access methods. However, the functionality between the TAS, ENAS and INAS has led to "integration" of these into a generalized TAS. An important role of the HAS and TAS so┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff69204141 ┆- i AAftware is to provide the services necessary to allow a user of the ACDN access to a participating host by making the user appear to the host system as a valid (host) end user. This transparency is implemented by transforming, where applicable, the ┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff69204141 ┆- i AAuser s data to a format more suited to the host. The HAS and TAS participates in establishing and maintaining connections between two users. Both are subdivided in entities. There will be one such entity for each type of host or terminal (inclus┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff69204141 ┆- i AAive external and internal networks). They share the nodal switch processing equipment. In summary, the application of a data channel connection allows an efficient high bandwidth connection to be established between ACDN and a host processor. Th┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff69204141 ┆- i AAe integration of external network interface hardware and software allows Air Canada to terminate external networks similar to the way terminal equipment is terminated. In all, the proposed ACDN provides Air Canada with means of achieving an all-ov┆
0x2e000…2e100 (46, 0, 0) Sector 2e01ff95204141 ┆. AAsystem made up of the NCP and NSPs at a location. The nodes provide the termination points to equipment of all external environments whether in the form of host data channels or communication lines to terminals and to other networks. This allows A┆
0x2e100…2e200 (46, 0, 1) Sector 2e02ff95204141 ┆. AAir Canada to terminate communication lines of the external networks a the "closest" node; thus, no particular node is designated as termination point of e.g. SITA or CNT trafic. The nodes are mutually interconnected by groups of 56 kbps internodal┆
0x2e200…2e300 (46, 0, 2) Sector 2e03ff95204141 ┆. AA trunk lines. These trunk lines are the physical transmission media used by the Communications Environment. The Network Service Environment is implemented on a number of processors each dedicated a specific set of services. A Network Control Ce┆
0x2e300…2e400 (46, 0, 3) Sector 2e04ff95204141 ┆. AAnter (NCC) implements the network control facilities to designated network operators called supervisors. The NCC is implemented hardwarewise as part of the NCP of the Toronto Node. A geographical back-up is likewise proposed as part of the Montrea┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff95204141 ┆. AAl node. This results in the increased survivability of the proposed network. A Network Management Host (NMH), which provides network administrative, planning and development facilities, is implemented by the same type of processor equipment as al┆
0x2e500…2e600 (46, 0, 5) Sector 2e06ff95204141 ┆. AAl other elements of the network. An Electronic Mail Host (EMH) implements the hardware required to provide protected message service (PMS). The EMH provides a centralized secondary storage for the PMS traffic in form of mirrored disk equipment, wh┆
0x2e600…2e700 (46, 0, 6) Sector 2e079495204141 ┆. AAile long term storage is provided in form of moveable disk packs and magnetic tape. The EMH as the NMH is co-located with the Toronto node. ts the following variety of terminal types: - CRTs - types 405, 406, 407, 408 - Flight Informatio┆
0x2e700…2e800 (46, 0, 7) Sector 2d08ff69204141 ┆- i AA 1 Network Interface Environment The Network Interface Environment is the outermost layer of the ACDN. It provides a direct physical and logical interface with the external envir┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff95204141 ┆. AAtware packages of the ACDN are defined and mapped onto the internal environments of the network architecture. The proposed Air Canada Data Network might be seen as basically three environments: - Network Interface Environment, - Communicatio┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0aff95204141 ┆. AAns Environment, and - Network Services Environment. The Communication Environment consists of the Data Transmission and the Data Link Environment of the general architecture. The Communications Environment establishes and maintains basically e┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff33204141 ┆. 3 AArror free communication paths between any two users. The communication environment implements the layers 1 to 5 in terms of the 7 layer OSI architecture. The Network Service Environment includes applications for network management and administra┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0cff33204141 ┆. 3 AAtion as well as a protected message service. These added value services are offered to users of the ACDN. The relation between the internal and the external environments is depicted in Figure III 3.2-7 "Proposed Network Architecture". This figu┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0d8133204141 ┆. 3 AAre and Figure III 3.2-8 provide the mapping of the hardware and software which constitute the basic elements of the ACDN. ocessor equipment. The proposed ACDN interfaces a Host Environment consisting of six hosts implementing the following applicat┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eae95204141 ┆. . AA 1 Figure III 3.2-8 Proposed Network Architecture Fig. 3.2-9 Hardware and Software Mapping (CGO) - Regional Carriers/ Corporate Services (RCCSH) IBM and U┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fff95204141 ┆. AA 1 Hardware Mapping The Network Interface Environment and the Communications Environment are implemented hardwarewise sharing the same processing equipment, Nodal Switch Processors ┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff95204141 ┆. AA(NSPs). These are co-located with host equipment on the following three locations: Toronto, Montreal and Winnipeg. The NSPs are controlled locally by a redundant Nodal Control Processor (NCP). The term node as used in this proposal refers to the ┆
0x2f000…2f100 (47, 0, 0) Sector 2f016900204141 ┆/ i AAlex access software occupying host resources and also the task of network monitoring and control. user of the backbone network is either a host application or a subscriber using a (terminal) device. An important function of the proposed network i┆
0x2f100…2f200 (47, 0, 1) Sector 2f02ff00204141 ┆/ AA 1 The network includes additional buffering capacity provided to avoid heavy retransmission activities lasting a short period of time resulting from host recovery. This added resili┆
0x2f200…2f300 (47, 0, 2) Sector 2f03ff00204141 ┆/ AAence implies protection of the service level of other network users. Retransmission caused by short outages may be avoided for a majority of transactions, resulting in a lower load for the transport network. The ACDN interconnects the External Net┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00204141 ┆/ AAworks Environment which consists of a number of national and international networks. This environment establishes paths between Air Canada resources of the Host and Terminal environment and external users and information providing sources, i.e. res┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00204141 ┆/ AAources which are not controlled by Air Canada. The External Networks Environment consists of the following data networks: - SITA - ARINC - CNT The Internal Network Environment covers the present network excluding those hosts and terminals ┆
0x2f500…2f600 (47, 0, 5) Sector 2f06ff00204141 ┆/ AAwhich are moved to the proposed network, i.e. - RES Host - ACNC and connected concentrators and terminals. This environment plays a major role in the proposed migration from the existing network to the new network as presented in this proposa┆
0x2f600…2f700 (47, 0, 6) Sector 2f077c00204141 ┆/ | AAl. It provides the means for enabling migration to take place without interrupting the services provided to users. sed network fully supports the following variety of terminal types: - CRTs - types 405, 406, 407, 408 - Flight Informatio┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff95204141 ┆. AA 1 3.2.5 Deliverables This section presents the ACDN deliverables in the context of the general network architecture presented in the previous section. The hardware elements and sof┆
0x2f800…2f900 (47, 0, 8) Sector 2f093121204141 ┆/ 1! AA system) - IBM 3270 compatible terminals Fig. III 3.2-7 AIR CANADA COMPUTING ENVIRONMENT etwork architecture. The generic ne┆
0x2f900…2fa00 (47, 0, 9) Sector 2f0aff00204141 ┆/ AA 1 The backbone network provides connectivity but also host transparency to the users of the terminal environment. The proposed network supports multiple applications running concurre┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00204141 ┆/ AAntly between a given user and relevant hosts. The network establishes and maintains the connection(s) between user and application(s) on behalf of the user. The communication management functions are kept transparent to the user where possible. ┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00204141 ┆/ AAThe Host environment consists of multiple multivendor processors which provide the majority of the Air Canada computer provided services. A major objective in the proposed network is to achieve an architecture well suited for allowance of existing ┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00204141 ┆/ AAand new hosts to be integrated into the Host Environment of the network without constraints with respect to selection of processor equipment. The proposed ACDN interfaces a Host Environment consisting of six hosts implementing the following applicat┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0eff00204141 ┆/ AAions: - Passenger Management (PMH) - Reservation, VIA (VIA) - Services Support Host (SUPP) - Operations (OPNS) - Cargo (CGO) - Regional Carriers/ Corporate Services (RCCSH) IBM and U┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00204141 ┆/ AAnivac mainframes with installed VTAM and CMS respectively, may be interfaced and supported as participatory members by the ACDN. Non IBM systems and IBM systems not supporting VTAM are interfaced and supported as attachments to ACDN at present. Thi┆
0x2ff00…30000 (47, 0, 15) Sector 2f00ff00204141 ┆/ AAs proposal includes an offer to develop a participatory interface to Honeywell DPS/08 computing facilities. The backbone network establishes and maintains connections between host applications and other users. It allows relieving the host of comp┆
0x30000…30100 (48, 0, 0) Sector 3001ff21204141 ┆0 ! AA 1 3.2.4 External Environments A user of the backbone network is either a host application or a subscriber using a (terminal) device. An important function of the proposed network i┆
0x30100…30200 (48, 0, 1) Sector 3002ff21204141 ┆0 ! AAs to establish and maintain connection between network users. The network must present a stable environment to the user which ensures data integrity and provides highly resilient services for data exchange between users. The term user as used in ┆
0x30200…30300 (48, 0, 2) Sector 3003ff21204141 ┆0 ! AAthis proposal covers both the requester of services and the provider of services. A requester may be a subscriber from his terminal while a provider may be an internal network service in the form of PMS or external in the form of a host application┆
0x30300…30400 (48, 0, 3) Sector 3004ff21204141 ┆0 ! AA, e.g. ticket reservation. A requestermay also be a host application, etc. A session describes the logical connection or the association between two users of the network. Privacy is important in a multiservice environment like the one proposed f┆
0x30400…30500 (48, 0, 4) Sector 3005ff21204141 ┆0 ! AAor Air Canada. The proposed network implements a high level of protection against unauthorized disclosure of data and information, based as it is on a hardware and operating system architecture derived from well recognized security principles and i┆
0x30500…30600 (48, 0, 5) Sector 3006ff21204141 ┆0 ! AAmplementations. Higher levels of software reflects the same discretionary access control and capability check-out philosophy as implemented by the proposed operating system. The Terminal Environment consists of a multitude of multivendor terminal┆
0x30600…30700 (48, 0, 6) Sector 3007ff21204141 ┆0 ! AA equipment which provide the immediate environment used by the subscribers of the Air Canada data services. The proposed network fully supports the following variety of terminal types: - CRTs - types 405, 406, 407, 408 - Flight Informatio┆
0x30700…30800 (48, 0, 7) Sector 2f08ff21204141 ┆/ ! AAn Displays (FIDs) - Printers - attached to CRT's - teletype model 40 - ticket printers - DI - AN - Extel - Other devices - ASTAC (self ticketing machines) - MAC (microcomputer based travel agent administrative┆
0x30800…30900 (48, 0, 8) Sector 3009db00204141 ┆0 [ AA 1 Fig. III 3.2-7 AIR CANADA COMPUTING ENVIRONMENT etwork architecture. The generic ne┆
0x30900…30a00 (48, 0, 9) Sector 300aff00204141 ┆0 AA 1 Flexibility in several dimensions - projected network expansion, - local area network capability, and - new equipment types is supported by the proposed network. The pro┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00204141 ┆0 AAjected network expansion is seen as an evolution progressing in small increments based on a continuous adaption to the connecting environments by means of standard expansion elements and modules. Support of local area includes a capability to incl┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00204141 ┆0 AAude the Christian Rovsing local area network, the X-net, at the travel agents facilities. This net provides a means for adding circuit switching to the packet switching facilities implemented by the proposed network. Addition of new equipment type┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00204141 ┆0 AAs is facilitated by the modular structure of the proposed hardware and software. Thus, addition of new equipment, whether hosts or terminals, can take place with a minimum of customizing and without interrupting the live network activities. The ┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00204141 ┆0 AAproposed backbone network is well suited to the dynamic environment in which Air Canada operates, an environment characterised by high volumes of transaction traffic. An architecture is proposed which essentially provides Air Canada with open ended┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00204141 ┆0 AA growth capability, an architecture which allows optimal allocation of services and terminations and which meet current and projected requirements for connectivity and transaction volumes; an architecture which enables Air Canada to make use of main┆
0x30f00…31000 (48, 0, 15) Sector 3000fa00204141 ┆0 z AAframe equipment best suited for a given purpose. The previous sections presented this general network architecture and is followed in subsequent subsections by a detailed mapping of the deliverables proposed for the Air Canada Data Network. an u┆
0x31000…31100 (49, 0, 0) Sector 31018433204141 ┆1 3 AA 1 Figure III 3.2-6 Network Architecture Realisations d on X-NET systems. The users of the architecture are connected either to a C-NET or an X-NET. An arbitrary group of C-┆
0x31100…31200 (49, 0, 1) Sector 3102ff00204141 ┆1 AA 1 3.2.3 Functional Overview The proposed network provides the means for integrating present as well as future computer and terminal facilities assigned to the following environments┆
0x31200…31300 (49, 0, 2) Sector 3103ff00204141 ┆1 AA: - Host Environment - External Network Environment - Internal Network Environment - Terminal Environment The users, host applications and terminal operators, uses a combination of the facilities implemented in the Host, Network, and Te┆
0x31300…31400 (49, 0, 3) Sector 3104ff33204141 ┆1 3 AArminal Environments together with those of the ACDN. The ACDN interconnects the external environments and provides a level of integration which makes the actual network topology and application allocation transparent to the user. This is illustrat┆
0x31400…31500 (49, 0, 4) Sector 3105ff00204141 ┆1 AAed in Figure III 3.2-7 "Air Canada Computing Environment". Each of these environments is described in more details in the next section. The remainder of section summarizes the services and capabilities of the ACDN. In addition to the packet s┆
0x31500…31600 (49, 0, 5) Sector 3106ff00204141 ┆1 AAwitch based services which implement interconnection between users, the network itself provides the following services: - Network Control - Network Management - Protected Message Service The network control services are provided to de┆
0x31600…31700 (49, 0, 6) Sector 3107ff00204141 ┆1 AAsignated personnel, network supervisors and field technicians. These services provide a centrally controlled environment which protects the integrity of the network and ensures consistent service to all users. The network management services cove┆
0x31700…31800 (49, 0, 7) Sector 3008da00204141 ┆0 Z AArs collection of statistical information for billing purposes, and the provision of facilities for planning and development. The protected message service provides acknowledged message transport between users. a LOGON is the creation of the capabi┆
0x31800…31900 (49, 0, 8) Sector 3109ff00204141 ┆1 AA 1 3.2.2.7 Network Architecture Realisations A number of system elements might be implemented by combining appropriate component parts of the network architecture. The generic ne┆
0x31900…31a00 (49, 0, 9) Sector 310aff00204141 ┆1 AAtwork elements presented in this section highlights the realisations feasible within the architecture. It is an attempt to provide the Air Canada Technical Management function with the perspectives of the proposed ACDN. Figure III 3.2-6 "Network ┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00204141 ┆1 AAArchitecture Realisations" illustrates how the internal environments may be combined to form the following elements: NCC - Nodal Control Center, which implements central network application NSH - Network Service Host, dedicated network eleme┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00204141 ┆1 AAnt, which implement network services; e.g. a NMH provides network administrative and planning services while an EMH provides a protected message service; These elements are participants in the network. Node - A generalized term used for an integr┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00204141 ┆1 AAated MIP, TIP and switching node, Switching Node - the switching nodes are configured to realise the CUE, DTrE, and DLE. Thus, it provides the basic transport services. HIP - the Host Interface P┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00204141 ┆1 AArocessor implements a host front-end capability combined with integration into the network by means of the switching node element of the HIP. The physical and logical interface towards the host is a channel which operates in accordance with the app┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00204141 ┆1 AAlicable mainframe vendor standards. TIP - the Terminal Interface Processor implements the interfaces to the various terminal devices to be attached to the network. The TIP is integrated with the switching node. MEDE - the Message Entry and Di┆
0x31f00…32000 (49, 0, 15) Sector 3100e300204141 ┆1 c AAstribution Environment are configured to realise the (remote) attachment functions of the NIE. The physical hardware configuration of the MEDE reflects the interfacing requirements of the various devices to be attached. essing structure allows an u┆
0x32000…32100 (50, 0, 0) Sector 3201ff00204141 ┆2 AAnlimited topological combination covering both longhaul networks, C-NETs based on CR 80 computers and local area networks based on X-NET systems. The users of the architecture are connected either to a C-NET or an X-NET. An arbitrary group of C-┆
0x32100…32200 (50, 0, 1) Sector 3202ff00204141 ┆2 AANETS forms a C-REGION. Similarly, an arbitrary group of X-NETS form an X-REGION. In a C-REGION, a longhaul region, groups of up to 16 neighbouring C-NETS may be interconnected by a highbandwidth channel (S-NET). Such a constellation is referred to┆
0x32200…32300 (50, 0, 2) Sector 3203ff00204141 ┆2 AA as a C-NODE. C-NODEs may be interconnected by leased lines or by employing the services of public data networks. In a X-REGION, a highbandwith local region, a number of X-NETS may be interconnected with other X-NETs via X-NODES. Up to 16 X-NETs ┆
0x32300…32400 (50, 0, 3) Sector 3204ff00204141 ┆2 AA(and one C-NET) can connect to the same X-NODE. Conversely, up to 16 X-NODEs can connect to the same X-NET. Figure III 3.2-4 illustrates the architectural topological possibilities. The C-NODE software is implemented by means of the following h┆
0x32400…32500 (50, 0, 4) Sector 3205ff00204141 ┆2 AAigh level structure. A C-NODE is a group of C-NETs, which operates under the control of a common operating system. To facilitate the management of system resources, each C-NET software is isolated and controlled separately. The co-ordination of the┆
0x32500…32600 (50, 0, 5) Sector 3206e000204141 ┆2 ` AA total resources at the C-NODE is facilitated via the central management part of the Network Services Environment, which stretches right across the C-NET boundaries. Figure III 3.2-5 illustrates this partitioning. the static and dynamic status ┆
0x32600…32700 (50, 0, 6) Sector 32077200204141 ┆2 r AA 1 Figure III 3.2-4 Topology Example above facilities is presented below. The NSE validates a user request to get connected to the network and use its services. Validating th┆
0x32700…32800 (50, 0, 7) Sector 31088100204141 ┆1 AA 1 Figure III 3.2-5 C-NODE Software partitioning he validation of the identification of the user. A result of a successful completion of a LOGON is the creation of the capabi┆
0x32800…32900 (50, 0, 8) Sector 3209ff00204141 ┆2 AAlities against which authorization is to be checked during subsequent network transactions. It is emphasised that this LOGON to the network is independent of and does not replace the LOGON procedure that may be required by an application program i┆
0x32900…32a00 (50, 0, 9) Sector 320aff00204141 ┆2 AAn a participatory host. Facilities needed to access and interrogate the status and availability of applications are provided by the NSE. These are realised by providing a set of emulated application programs. These application programs interrog┆
0x32a00…32b00 (50, 0, 10) Sector 320bff00204141 ┆2 AAate the responsible communication software resident in the participating host. Such interrogations provide the data needed by the NSE to validate connectivity requests by a network user. The NSE maintains the integrity of the network topology by ┆
0x32b00…32c00 (50, 0, 11) Sector 320c4600204141 ┆2 F AA - recognising link failure and implementing back-up routing c, - messages exchanged by the NSEs distributed in the various nodes and the Network Control Center for collecting statistical data, are assigned the lowest priority. the device c┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00204141 ┆2 AA 1 - recognising node failures and implementing recovery procedures - recognising overload on links and implementing back up routing - recognising catastrophic failures at t┆
0x32d00…32e00 (50, 0, 13) Sector 320eff00204141 ┆2 AAhe NIE level and removing the attachments or participants from the network. The NSE collects end user statistics primarily at the level of an end-user-to-end-user connection. The NSE initialises the statistics gathering at the NIE and CUE level w┆
0x32e00…32f00 (50, 0, 14) Sector 320f8100204141 ┆2 AAhen an end user protocol is initialised. The statistics are forwarded to the NSE once the end user exchange is terminated. DTrE's guaranteeing the sequence in the data flowing between the communicating SSPs. o The virtual connections may be "swit┆
0x32f00…33000 (50, 0, 15) Sector 3200ff00204141 ┆2 AA 1 3.2.2.6 Network Topology The proposed ACDN is a specific implementation of general network topologies supported by the network architecture. The addressing structure allows an u┆
0x33000…33100 (51, 0, 0) Sector 3301ff33204141 ┆3 3 AAystem users to access the transport network. o For certain pre-assigned attachments or participants, the DTrE provides permanent associations between the relevant SSPs. o DTrE maintain a bi-directional interface for each trunk interconnecting th┆
0x33100…33200 (51, 0, 1) Sector 33023633204141 ┆3 63 AAe network nodes with the Data Link Environment. evel of protocol within the network. The conversation is by definition at a level below the end-user-to-end-user protocol. Each end user must have a TAP assigned before a conversation can be opened. T┆
0x33200…33300 (51, 0, 2) Sector 3303ff00204141 ┆3 AA 1 3.2.2.4 Data Link Environment The Data Link Environment is the second inner environment of the transport network. The DLE provides the necessary functions to supports a Data Link┆
0x33300…33400 (51, 0, 3) Sector 3304b100204141 ┆3 1 AA Control procedure between two DTrE utilising conventional transmission media. The DLE is a homogeneous entity and supports the LAPB procedure defined as X.25 level 2. t the hosts. In the proposed ACDN there is only one conversation protocol. k┆
0x33400…33500 (51, 0, 4) Sector 3305ff00204141 ┆3 AA 1 3.2.2.5 Network Services Environment The Network Services Environment (NSE) provides the facilities required to support - connectivity of network users - participatory ┆
0x33500…33600 (51, 0, 5) Sector 3306ff00204141 ┆3 AAinterfaces - maintaining the integrity of the network configuration - collecting short term and long term statistics on network services utilisation - a set of commands to be used by ACDN operators to monitor the static and dynamic status ┆
0x33600…33700 (51, 0, 6) Sector 3307ff00204141 ┆3 AAof the network. The NSE is implemented in a distributed manner. The scope of the functions to support the above facilities is presented below. The NSE validates a user request to get connected to the network and use its services. Validating th┆
0x33700…33800 (51, 0, 7) Sector 3208ff00204141 ┆2 AAe request implies prior knowledge of the user by the NSE. An important part of the network LOGON is authentication, i.e. the validation of the identification of the user. A result of a successful completion of a LOGON is the creation of the capabi┆
0x33800…33900 (51, 0, 8) Sector 3309ff33204141 ┆3 3 AAources from the Network Services Environment. The TAP services provide the operational facilities necessary to sustain open conversations by: o Managing resources allocated to the active transport access paths. o Monitoring the operation┆
0x33900…33a00 (51, 0, 9) Sector 330aff33204141 ┆3 3 AA of the conversation protocols. o Supporting the hierarchical priority system with the following levels - messages generated by the network services environment to inform node or other network catastrophic failure conditions are given the hi┆
0x33a00…33b00 (51, 0, 10) Sector 330bff33204141 ┆3 3 AAghest priority, - messages generated by the NSE to change routing primitives at the nodes are given priority at the same level as protocol responses indicating the loss of integrity in the end-user-to-end- user protocol, - transport user ┆
0x33b00…33c00 (51, 0, 11) Sector 330cf333204141 ┆3 s3 AAtraffic, - interactive user traffic, - batch user traffic, - messages exchanged by the NSEs distributed in the various nodes and the Network Control Center for collecting statistical data, are assigned the lowest priority. the device c┆
0x33c00…33d00 (51, 0, 12) Sector 330dff33204141 ┆3 3 AA 1 3.2.2.3 Data Transmission Environment The Data Transmission Environment (DTrE) forms the outermost environment of the transport network. o The DTrE provides communication servic┆
0x33d00…33e00 (51, 0, 13) Sector 330eff33204141 ┆3 3 AAes to a pair of SSPs engaged in a conversation so that the total usage of the physical media connecting the two SSPs is maximized. This is achieved by utilizing the datagram technology as the basis for this environment. o The SSPs can request eit┆
0x33e00…33f00 (51, 0, 14) Sector 330fff33204141 ┆3 3 AAher a datagram service or a virtual connection service from the DTrE. The latter is achieved by the source and destination DTrE's guaranteeing the sequence in the data flowing between the communicating SSPs. o The virtual connections may be "swit┆
0x33f00…34000 (51, 0, 15) Sector 3300ff33204141 ┆3 3 AAched" or "permanent". o DTrE provides a number of logical channels for transmitting data. o Each logical channel supports traffic in both directions and is independent of the traffic on other channels. o DTrE assigns "ports" to communication s┆
0x34000…34100 (52, 0, 0) Sector 3401ff69204141 ┆4 i AA for implementing network resource control. The TAP has the following characteristics: - a finite fluctuating bandwidth - a finite predictable error rate - a unique identity recognisable throughout the network Two end users exchang┆
0x34100…34200 (52, 0, 1) Sector 3402ff69204141 ┆4 i AAe data through a "conversation" is the highest level of protocol within the network. The conversation is by definition at a level below the end-user-to-end-user protocol. Each end user must have a TAP assigned before a conversation can be opened. T┆
0x34200…34300 (52, 0, 2) Sector 3403ff69204141 ┆4 i AAhe conversation protocol ensures proper flow of user messages between the associated two TAPs and provides error recovery facilities to avoid loss of messages. Referring to Fig. III 3.2-3, "Network Protocols", end-user-to-end-user protocol is d┆
0x34300…34400 (52, 0, 3) Sector 3404fe69204141 ┆4 ~i AAetermined by the complex of the host facilities. There may be as many end user protocols as there are unique types of hosts and distinctly supported end user types amongst the hosts. In the proposed ACDN there is only one conversation protocol. k┆
0x34400…34500 (52, 0, 4) Sector 3405cf69204141 ┆4 Oi AA 1 Figure III 3.2-3 NETWORK PROTOCOLS o the OSI architecture. ingle terminal or a clu┆
0x34500…34600 (52, 0, 5) Sector 3406ff3f204141 ┆4 ? AA 1 The conversation is established between the Session Service Provider (SSP) entities of the CUE. The SSP is a software entity. The data areas and control functions of an SSP imple┆
0x34600…34700 (52, 0, 6) Sector 3407ff33204141 ┆4 3 AAment the following functions: o Accept and validate a user request for a communication service provided by the network. o Assign a Transport Access Port (TAP) under a unique identity. o Interrogate the end users and determine the basic con┆
0x34700…34800 (52, 0, 7) Sector 3308ff33204141 ┆3 3 AAversation parameters. o Based on the conversation parameters obtained from the user, allocate the resources to the TAP required to support a chosen traffic type and chosen conversation protocol characteristics. o Reserve and bind the TAP res┆
0x34800…34900 (52, 0, 8) Sector 3409ffc2204141 ┆4 B AAcols and data formats into protocol and data formats dictated by the communication user environment of the network. Virtual Service Providers (VSP) provide the presentation service entities which are responsible for mapping the end user protocol t┆
0x34900…34a00 (52, 0, 9) Sector 340affc2204141 ┆4 B AAo a network conversation protocol. VSPs are software entities which implement the following functions: o The sequence number on the data units handled by the end user protocol is mapped to the sequence number of the data units handled by the netw┆
0x34a00…34b00 (52, 0, 10) Sector 340bffc2204141 ┆4 B AAork conversation protocol. o The segmentation and/or blocking indicators in the end user protocol data unit are mapped into corresponding control indicators for the data units handled by the Session Service Providers (SSP) of the Communication ┆
0x34b00…34c00 (52, 0, 11) Sector 340cffc2204141 ┆4 B AAUser Environment. o The throughput control indicators in the end user protocol are mapped to the flow control indicators in the conversation protocol. o The presentation control indicators in the end user protocol are mapped to the device c┆
0x34c00…34d00 (52, 0, 12) Sector 340dffc2204141 ┆4 B AAontrol indicators in the conversation protocol. The NIE may provide a second level of translation or conversion of protocols, depending on whether a host facility is interfaced as an attachment or participant. The second level of conversion is ne┆
0x34d00…34e00 (52, 0, 13) Sector 340effc2204141 ┆4 B AAeded for participant interfacing. For these, the second level of translation converts protocols and data formats dictated by communication I/O software in the host to the protocols and data formats dictated by the communication user environment. ┆
0x34e00…34f00 (52, 0, 14) Sector 340fff69204141 ┆4 i AA 1 3.2.2.2 Communication User Environment The Communication User Environment (CUE) provides the necessary services to a network user in establishing and maintaining a conversation┆
0x34f00…35000 (52, 0, 15) Sector 3400ff69204141 ┆4 i AA with another user or logical unit in a host. The Transport Access Port (TAP) is a fundamental entity of the network. The TAP is the basis for providing a given number and type of communication channel to the network user. It provides the means┆
0x35000…35100 (53, 0, 0) Sector 3501ffc2204141 ┆5 B AA 1 The Data Link Environment consists of firmware entities to transport data over physical links and to support the necessary protocol facilities dictated by the attachment or partici┆
0x35100…35200 (53, 0, 1) Sector 3502ff21204141 ┆5 ! AApant interface. The Network Service Environment consists of entities to support complete network control as well as the provision of special services to users of the network. The various communication software products are designed in a structur┆
0x35200…35300 (53, 0, 2) Sector 3503ff00204141 ┆5 AAed manner conforming to the ISO reference model for Open System Interconnection (OSI). The proposed architecture is mapped on the OSI as follows: o presentation layer ... Network Interface Environment (NIE) o session layer ... Commun┆
0x35300…35400 (53, 0, 3) Sector 3504ff00204141 ┆5 AAication User Environment (CUE) o transport layer o network layer ... Data Transmission Environment (DTrE) o link layer o physical layer ... Data Link Environment (DLE) System Management functions and services: o network┆
0x35400…35500 (53, 0, 4) Sector 3505e8c2204141 ┆5 hB AA management o system management o layer management o service applications ... Network Services Environment (NSE) Figure III 3.2-2 illustrates how these ACDN environments are mapped onto the OSI architecture. ingle terminal or a clu┆
0x35500…35600 (53, 0, 5) Sector 350682c3204141 ┆5 C AA 1 Figure III 3.2-2 ACDN/OSI REFERENCE MODEL MAPPING es not play any role in providing and controlling the resources made available to the whole spectrum of ACDN users. b. Part┆
0x35600…35700 (53, 0, 6) Sector 3507ffc2204141 ┆5 B AA 1 3.2.2.1 Network Interface Environment The Network Interface Environment (NIE) as the outermost layer provides the necessary services to any user accessing an attachment or a parti┆
0x35700…35800 (53, 0, 7) Sector 3408ffc2204141 ┆4 B AAcipant. The NIE makes the user appear as a valid end user either as defined in the destination or through a mapping onto a virtual network protocol. The NIE provides this service by a conversion or translation of the end user message level proto┆
0x35800…35900 (53, 0, 8) Sector 3509ff00204141 ┆5 AA 1 3.2.2 Proposed Network Architecture This section presents the proposed Network Architecture. The layered structure of the internal environments of the network is presented and th┆
0x35900…35a00 (53, 0, 9) Sector 350aff00204141 ┆5 AAe basic services provided by these layers are described, in particular the services provided to the users in external environments . The hardware and software which constitute the deliverables to Air Canada are described in the subsequent section 3┆
0x35a00…35b00 (53, 0, 10) Sector 350bff00204141 ┆5 AA.2.5. In the context of the scope of the ACDN a set of interrelated "environments" can be identified as the component parts of the general network architecture, to which ACDN relates. Essential to the proposed architecture is that entities commu┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00204141 ┆5 AAnicate with corresponding remote entities in the same environment. Figure III 3.2-1 shows the environments and their relationship. The following five internal environments are the component parts of the general network architecture: - Netw┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00204141 ┆5 AAork Services Environment, - Network Interface Environment, - Communications User Environment, - Data Transmission Environment, - Data Link Environment, The Network Interface Environment provides the physical and logical interface wit┆
0x35d00…35e00 (53, 0, 13) Sector 350effc3204141 ┆5 C AAh attachments and participants to the external environment. It relieves the interconnected equipment of the burden of providing the appearance expected by either end of a connection. The Communication User Environment consists of entities that es┆
0x35e00…35f00 (53, 0, 14) Sector 350ff2c3204141 ┆5 rC AAtablish and maintain an orderly exchange of information between two users. The Data Transmission Environment consists of entities that provide the actual communication path through the ACDN to support the dialogue between two users. . Implement F┆
0x35f00…36000 (53, 0, 15) Sector 35007600204141 ┆5 v AA 1 Fig. III 3.2-1 PROPOSED ARCHITECTURE aintenance should execute at the level of application programs. k. Be Dynamic: Protocols should be flexible to change; new modules and┆
0x36000…36100 (54, 0, 0) Sector 36013f00204141 ┆6 ? AA functions should be easily added within the structure. rom the existing network environment to an enhanced network environment. When the above premises are mapped on to the available networking solutions from Christian Rovsing a primary r┆
0x36100…36200 (54, 0, 1) Sector 3602ff00204141 ┆6 AA 1 The general purpose computer facilities may include software for supporting remote terminals and associated communication procedures. ACDN, as conceived and presented in this prop┆
0x36200…36300 (54, 0, 2) Sector 3603ff00204141 ┆6 AAosal, excludes all such facilities in their entirety. However, the implied transparancy in the ACDN is such that any general purpose computing facility can be interfaced to ACDN. It is our conviction that in the 1980s there is no real need to dist┆
0x36300…36400 (54, 0, 3) Sector 3604ff00204141 ┆6 AAinguish between terminals and computing facilities, and as such we use the words synonymously. However, there is a distinction between the interfacing mechanisms which are attachments to the ACDN and those which are participants. This distinction┆
0x36400…36500 (54, 0, 4) Sector 3605ff00204141 ┆6 AA is as follows: a. Attachments to ACDN Any computing facility can be interfaced to the ACDN as an "attachment". Attachment implies that a computing facility, irrespective of the complexity and scope, behaves like a single terminal or a clu┆
0x36500…36600 (54, 0, 5) Sector 3606ff00204141 ┆6 AAster of terminals with predetermined characteristics. Attachment implies that a computing facility so interconnected does not play any role in providing and controlling the resources made available to the whole spectrum of ACDN users. b. Part┆
0x36600…36700 (54, 0, 6) Sector 3607ff00204141 ┆6 AAicipants in ACDN Any computing facility can be interfaced to ACDN as a "participant". Being a participant implies that application resources contained in that computing facility are made available to all ACDN users. The control functions in t┆
0x36700…36800 (54, 0, 7) Sector 3508e000204141 ┆5 ` AAhe ACDN monitor the status of the application resources in each participant and maintains the validity of the resource status on a network wide basis. Such a participant is also referred to as a "HOST" synonymously. in the reduced development eff┆
0x36800…36900 (54, 0, 8) Sector 3609ff00204141 ┆6 AAort by using an existing network product, a distributed application development should have a good performance to cost ratio. d. Support a Wide Range of Topologies: The architecture should support communication between users independent of the in┆
0x36900…36a00 (54, 0, 9) Sector 360aff00204141 ┆6 AAtervening data transport network. The interconnection structure of the computers and communication facilities should not affect the logical communication capabilities of the applications. e. Be Highly Available: The overall operation of the netwo┆
0x36a00…36b00 (54, 0, 10) Sector 360b6e00204141 ┆6 n AArk should not be adversely affected by the failure of a topologically noncritical node and/or channel. PRESENT AIR CANADA DATA NETWORKS ...... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00204141 ┆6 AA 1 f. Be Extensible: The architecture should allow for the incorporation of future technology changes in hardware and/or software: for the movement of functions across the hardware/s┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00204141 ┆6 AAoftware boundary, taking advantage of new technological innocations in both domains; and for the subsettability of functions to allow smaller, lower performance nodes. g. Be Easily Implementable: The architecture should be independent of the inte┆
0x36d00…36e00 (54, 0, 13) Sector 360eff00204141 ┆6 AArnal characteristics of the hosts and their operating systems and be easily and efficiently implemented on a wide variety of heterogeneous hardware and software. h. Use a Hierarchical Layered Structure: This will create a highly flexible structur┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00204141 ┆6 AAe with ease of layer replacement and modularity. i. Uniformly Address all Nodes: The topology should not restrict access. Nodes should be characterized only by the functions they perform, and not by their location in the network. j. Implement F┆
0x36f00…37000 (54, 0, 15) Sector 3600ff00204141 ┆6 AAunctions at the Highest Practical Efficient Level Within the Structure: Such functions as network control and maintenance should execute at the level of application programs. k. Be Dynamic: Protocols should be flexible to change; new modules and┆
0x37000…37100 (55, 0, 0) Sector 3701ff00204141 ┆7 AAnd coverage. ... a need to realise a stable migration from the existing network environment to an enhanced network environment. When the above premises are mapped on to the available networking solutions from Christian Rovsing a primary r┆
0x37100…37200 (55, 0, 1) Sector 37025300204141 ┆7 S AAationale for the proposed Air Canada Data Network (ACDN) is seen to evolve. duction The scope of this chapter is to convey to the Technical Management function in Air Canada, the underlying precepts of the solution proposed by Christian Rovsing t┆
0x37200…37300 (55, 0, 2) Sector 3703ff00204141 ┆7 AA 1 The solution to the Air Canada Data Network proposed herein, is based on a network architecture which has evolved over the last five years and is used in national as well as intern┆
0x37300…37400 (55, 0, 3) Sector 3704ff00204141 ┆7 AAational private networks, where high performance, reliability, security and flexibility were essential. The proposed network architecture has been designed to create a communication mechanism which supports a wide range of user applications, host ┆
0x37400…37500 (55, 0, 4) Sector 3705ff00204141 ┆7 AAcomputer systems and interconnect technologies. Specifically, the goals are the following: a. Create a Common User Interface: The application interface to the network should support a broad spectrum of application communication requirements and ┆
0x37500…37600 (55, 0, 5) Sector 3706ff00204141 ┆7 AAshould be common across the varied implementations. Within such a network environment, applications may be moved among the systems in the network, with the common interface hiding the internal characteristics and topology of the network. b. Suppor┆
0x37600…37700 (55, 0, 6) Sector 3707ff00204141 ┆7 AAt a Wide Range of Communication Facilities: The network should be adaptable to changes in communication technology and operate with a variety of communication channels using appropriate cost effective technology. Today this may be leased ground cir┆
0x37700…37800 (55, 0, 7) Sector 3608ff00204141 ┆6 AAcuits, in a few years it may be satellite channels. c. Be Cost Effective: The network should approach the efficiency and performance of a network designed specifically for a given application. In addition, factoring in the reduced development eff┆
0x37800…37900 (55, 0, 8) Sector 3709ff00204141 ┆7 AA, are presented,in section 3.5. Finally, section 3.6 discusses the projected growth capabilities of the network with respect to capacity and functionality, 3.7 describes the telecommunication support provided by CNCP, while 3.8 discusses potential┆
0x37900…37a00 (55, 0, 9) Sector 370a1600204141 ┆7 AA growth areas. 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x37a00…37b00 (55, 0, 10) Sector 370b8fa1204141 ┆7 ! AA 1 Figure III 3.1-1 PRESENT AIR CANADA DATA NETWORKS ...... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x37b00…37c00 (55, 0, 11) Sector 370cff00204141 ┆7 AA 1 3.2 Proposed Technical Solution 3.2.1 Scope of ACDN Air Canada Data Network (ACDN) is perceived as a transparent common communication service capable of interfacing a variety of ┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00204141 ┆7 AAterminals, terminal concentrators, and a variety of general purpose mini or mainframe based computing facilities. The computing facilities of Air Canada as they exist today, are presented in a generalized and simplified view in Figure III 3.1-1 "┆
0x37d00…37e00 (55, 0, 13) Sector 370eff00204141 ┆7 AAPresent Air Canada Data Networks". Each of the networks provides specific sets of services to the user. The discernible premises for the RFP are: ... a high degree of transparancy in the network necessitated by the diversity of users and s┆
0x37e00…37f00 (55, 0, 14) Sector 370fff00204141 ┆7 AAervices ... a need to interface to and permit access to application resources in UNIVAC, HONEYWELL, IBM mainframes. ... a need to provide network management and admini- stration facilities that can be exploited by the network maintenanc┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00204141 ┆7 AAe staff organization at the central and remote sites. ... a need to support new services like facsimile data transmission and digitised voice transmission. ... a need to coexist with external networks that provide complementary services a┆
0x38000…38100 (56, 0, 0) Sector 38018c00204141 ┆8 AA Subscriber services: By exploiting available standard software and firmware for host support and terminal devices support. .2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x38100…38200 (56, 0, 1) Sector 3802ff00204141 ┆8 AA 1 3.1 Introduction The scope of this chapter is to convey to the Technical Management function in Air Canada, the underlying precepts of the solution proposed by Christian Rovsing t┆
0x38200…38300 (56, 0, 2) Sector 3803ff00204141 ┆8 AAo meet the functional requirements contained in the Air Canada RFP. This chapter also serves to provide a high level breakdown of the proposed Air Canada Data Network including the associated rationale. The breakdown is covered in terms of hardwar┆
0x38300…38400 (56, 0, 3) Sector 3804ff00204141 ┆8 AAe and software architectures. The software is presented in terms of the 7-layer OSI reference model. Additionally, this chapter presents the predicted performance and response times. The proposed solution is presented in a broad context in secti┆
0x38400…38500 (56, 0, 4) Sector 3805ff00204141 ┆8 AAon 3.2. Subsection 3.2.1 provides the scope of the backbone network as perceived by Air Canada while subsection 3.2.2 presents the proposed network architecture by covering internal environments, network topology together with possible network rea┆
0x38500…38600 (56, 0, 5) Sector 3806ff00204141 ┆8 AAlizations. Subsection 3.2.3 gives a functional overview on the proposed Air Canada Data Network, while subsection 3.2.4 defines and presents the external "environments" to which the proposed Air Canada Data Network provides service. The deliverab┆
0x38600…38700 (56, 0, 6) Sector 3807ff00204141 ┆8 AAle hardware and software mapping on the environments of the architecture is provided in subsection 3.2.5. Section 3.3 provides the high-level break-down of the hardware. The software functional basis and structure is presented in section 3.4. T┆
0x38700…38800 (56, 0, 7) Sector 3708ff00204141 ┆7 AAhis section covers interfaces to the backbone network from users, i.e. from host computers, other networks, via the Gateway to the existing network, and to terminal equipment. Results of the performance analysis, i.e. response times and capacities┆
0x38800…38900 (56, 0, 8) Sector 3809ff00204141 ┆8 AA.2-3 Network Protocols ........................ 17 3.2-4 Topology Example ......................... 24 3.2-5 C-NODE Partitioning ...................... 25 3.2-6 Network Architecture Realizations ........ 27 3.2-7 Air Canada Computing Environ┆
0x38900…38a00 (56, 0, 9) Sector 380aff00204141 ┆8 AAment ......... 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00204141 ┆8 AAftware Structure .................. 45 3.4-3 ACDN Software ............................ 47 3.4-4 Network Interfaces Environment ........... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x38b00…38c00 (56, 0, 11) Sector 380c7b00204141 ┆8 { AA.. 74 3.6-3 Projected Growth Winnipeg ................ 75 3.6-4 Projected Growth, EMH .................... 76 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x38c00…38d00 (56, 0, 12) Sector 380dff00204141 ┆8 AA 1 3. PROPOSED SOLUTION To the full extent that Air Canada is embarking on establishing a network base for the 1980s with the knowledge of the positive impact this will have on Air ┆
0x38d00…38e00 (56, 0, 13) Sector 380eff00204141 ┆8 AACanadas operations, services to the passengers and to the airline industry's commercial infrastructure, we have presented in this chapter our solution in the context of a broad perspectiv over the trends in data communications industry in the 1980s.┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00204141 ┆8 AA The key themes behind our proposed solution are: High availability: Through fault tolerance and redundant hardware and through a unique network control philosophy. Granular Expandability: Through a scheme that exploits ┆
0x38f00…39000 (56, 0, 15) Sector 3800ff00204141 ┆8 AAmultiprocessing configuratons and distributed functions. Investment Protection: Through a networking scheme that supports heterogenous hosts, data transport services, terminal types and a networking scheme based on available standards.┆
0x39000…39100 (57, 0, 0) Sector 3901ff00204141 ┆9 AA3.4 Proposed Software Packages ..................... 44 3.4.1 Access Software Package......................... 48 3.4.2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x39100…39200 (57, 0, 1) Sector 3902ff00204141 ┆9 AA...... 52 3.4.4 Network Management Software Package............. 54 3.4.5 Electronic Mail Software Package................ 55 3.5 Performance .................................... 57 3.5.1 Node Modelling ..............┆
0x39200…39300 (57, 0, 2) Sector 3903ff00204141 ┆9 AA................... 58 3.5.1.1 End-to-End Response Time ....................... 58 3.5.1.2 Processor Utilization and Capacity.............. 59 3.5.1.3 Memory Utilization ............................. 60 3.5.1.4 Internodal Trunk ┆
0x39300…39400 (57, 0, 3) Sector 3904f000204141 ┆9 p AAUtilization ................... 62 3.5.2 Gateway ........................................ 63 3.5.3 EMH Modelling .................................. 64 3.5.4 Reliability and Availability ................... 67 ilket? ┆
0x39400…39500 (57, 0, 4) Sector 3905ff00204141 ┆9 AA 1 3.6 Baseline Capacity and Projected Growth ......... 69 3.6.1 Baseline Capacity .............................. 69 3.6.2 Projected Growth ......................┆
0x39500…39600 (57, 0, 5) Sector 3906ff00204141 ┆9 AA......... 70 3.6.3 Block Diagrams ................................. 72 3.7 Telecommunications ............................. 77 3.8 Options ........................................ 78 3.8.1 Videotex .................┆
0x39600…39700 (57, 0, 6) Sector 39076300204141 ┆9 c AA...................... 80 3.8.2 High Density Digital Tape Recordings ........... 83 20 04 82 08 55 7 10 11838 16 07 82 14 04 00 13 27 04 82 20 40 16 07 82 14 05 1006V 83 16 48 1448 34723 f *J B ? _┆
0x39700…39800 (57, 0, 7) Sector 3808ff00204141 ┆8 AA 1 LIST OF FIGURES 3.1-1 Present Air Canada Data Networks.......... 6 3.2-1 Proposed Architecture..................... 12 3.2-2 ACDN/081 Reference Model Mapping ......... 14 3┆
0x39800…39900 (57, 0, 8) Sector 3909ff41204141 ┆9 A AA2041A AIR CANADA PROPOSAL ba FR DOC. III Chapter 3 20 04 82 08 55 7 10 11838 16 07 82 14 04 00 13 27 04 82 20 40 16 07 82 14 05 1006V 83 16 48 1448 34723 f *J B ? _┆
0x39900…39a00 (57, 0, 9) Sector 390a5300204141 ┆9 S AAJ 9 9 9 9 8 8 7 7 7 6 6 5 5 5 5 5 4 4 4 3 3 3 2 2 2 2 1 1 1 0 0 0 / / / . . . - - , , , + + * * * * ) ) ( ( ' ' & & & % % $ $ $ # # # " " ! ! ! ! ┆
0x39a00…39b00 (57, 0, 10) Sector 390bfb00204141 ┆9 { AA 1 CHAPTER 3 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00204141 ┆9 AA 1 1 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00204141 ┆9 AA........ 4 3.1 Introduction ................................... 5 3.2 Proposed Technical Solution .................... 7 3.2.1 Scope of Air Canada Data Network ............... 7 3.2.2 Proposed Network Architect┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00204141 ┆9 AAure .................. 11 3.2.2.1 Network Interface Environment .................. 15 3.2.2.2 Communication User Environment ................. 16 3.2.2.3 Data Transmission Environment .................. 19 3.2.2.4 Data Link Envi┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00204141 ┆9 AAronment .......................... 20 3.2.2.5 Network Service Environment .................... 21 3.2.2.6 Network Topology................................ 23 3.2.2.7 Network Architecture Realisations .............. 26 3.2.3 Fu┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00204141 ┆9 AAnctional Overview ............................ 28 3.2.4 External Environments .......................... 31 3.2.5 Deliverables ................................... 34 3.3 Proposed Hardware Equipment .................... 40 ┆
0x3a000…3a100 (58, 0, 0) Sector 3a01ff00204141 ┆: AA, are presented,in section 3.5. Finally, section 3.6 discusses the projected growth capabilities of the network with respect to capacity and functionality, 3.7 describes the telecommunication support provided by CNCP, while 3.8 discusses potential┆
0x3a100…3a200 (58, 0, 1) Sector 3a021600204141 ┆: AA growth areas. 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x3a200…3a300 (58, 0, 2) Sector 3a038fa1204141 ┆: ! AA 1 Figure III 3.1-1 PRESENT AIR CANADA DATA NETWORKS ...... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x3a300…3a400 (58, 0, 3) Sector 3a04ff00204141 ┆: AA 1 3.2 Proposed Technical Solution 3.2.1 Scope of ACDN Air Canada Data Network (ACDN) is perceived as a transparent common communication service capable of interfacing a variety of ┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00204141 ┆: AAterminals, terminal concentrators, and a variety of general purpose mini or mainframe based computing facilities. The computing facilities of Air Canada as they exist today, are presented in a generalized and simplified view in Figure III 3.1-1 "┆
0x3a500…3a600 (58, 0, 5) Sector 3a06ff00204141 ┆: AAPresent Air Canada Data Networks". Each of the networks provides specific sets of services to the user. The discernible premises for the RFP are: ... a high degree of transparancy in the network necessitated by the diversity of users and s┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ff00204141 ┆: AAervices ... a need to interface to and permit access to application resources in UNIVAC, HONEYWELL, IBM mainframes. ... a need to provide network management and admini- stration facilities that can be exploited by the network maintenanc┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00204141 ┆9 AAe staff organization at the central and remote sites. ... a need to support new services like facsimile data transmission and digitised voice transmission. ... a need to coexist with external networks that provide complementary services a┆
0x3a800…3a900 (58, 0, 8) Sector 3a098c00204141 ┆: AA Subscriber services: By exploiting available standard software and firmware for host support and terminal devices support. .2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00204141 ┆: AA 1 3.1 Introduction The scope of this chapter is to convey to the Technical Management function in Air Canada, the underlying precepts of the solution proposed by Christian Rovsing t┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00204141 ┆: AAo meet the functional requirements contained in the Air Canada RFP. This chapter also serves to provide a high level breakdown of the proposed Air Canada Data Network including the associated rationale. The breakdown is covered in terms of hardwar┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00204141 ┆: AAe and software architectures. The software is presented in terms of the 7-layer OSI reference model. Additionally, this chapter presents the predicted performance and response times. The proposed solution is presented in a broad context in secti┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00204141 ┆: AAon 3.2. Subsection 3.2.1 provides the scope of the backbone network as perceived by Air Canada while subsection 3.2.2 presents the proposed network architecture by covering internal environments, network topology together with possible network rea┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00204141 ┆: AAlizations. Subsection 3.2.3 gives a functional overview on the proposed Air Canada Data Network, while subsection 3.2.4 defines and presents the external "environments" to which the proposed Air Canada Data Network provides service. The deliverab┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00204141 ┆: AAle hardware and software mapping on the environments of the architecture is provided in subsection 3.2.5. Section 3.3 provides the high-level break-down of the hardware. The software functional basis and structure is presented in section 3.4. T┆
0x3af00…3b000 (58, 0, 15) Sector 3a00ff00204141 ┆: AAhis section covers interfaces to the backbone network from users, i.e. from host computers, other networks, via the Gateway to the existing network, and to terminal equipment. Results of the performance analysis, i.e. response times and capacities┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00204141 ┆; AA.2-3 Network Protocols ........................ 17 3.2-4 Topology Example ......................... 24 3.2-5 C-NODE Partitioning ...................... 25 3.2-6 Network Architecture Realizations ........ 27 3.2-7 Air Canada Computing Environ┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00204141 ┆; AAment ......... 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00204141 ┆; AAftware Structure .................. 45 3.4-3 ACDN Software ............................ 47 3.4-4 Network Interfaces Environment ........... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x3b300…3b400 (59, 0, 3) Sector 3b047b00204141 ┆; { AA.. 74 3.6-3 Projected Growth Winnipeg ................ 75 3.6-4 Projected Growth, EMH .................... 76 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00204141 ┆; AA 1 3. PROPOSED SOLUTION To the full extent that Air Canada is embarking on establishing a network base for the 1980s with the knowledge of the positive impact this will have on Air ┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00204141 ┆; AACanadas operations, services to the passengers and to the airline industry's commercial infrastructure, we have presented in this chapter our solution in the context of a broad perspectiv over the trends in data communications industry in the 1980s.┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00204141 ┆; AA The key themes behind our proposed solution are: High availability: Through fault tolerance and redundant hardware and through a unique network control philosophy. Granular Expandability: Through a scheme that exploits ┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00204141 ┆: AAmultiprocessing configuratons and distributed functions. Investment Protection: Through a networking scheme that supports heterogenous hosts, data transport services, terminal types and a networking scheme based on available standards.┆
0x3b800…3b900 (59, 0, 8) Sector 3b09ff00204141 ┆; AA3.4 Proposed Software Packages ..................... 44 3.4.1 Access Software Package......................... 48 3.4.2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00204141 ┆; AA...... 52 3.4.4 Network Management Software Package............. 54 3.4.5 Electronic Mail Software Package................ 55 3.5 Performance .................................... 57 3.5.1 Node Modelling ..............┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00204141 ┆; AA................... 58 3.5.1.1 End-to-End Response Time ....................... 58 3.5.1.2 Processor Utilization and Capacity.............. 59 3.5.1.3 Memory Utilization ............................. 60 3.5.1.4 Internodal Trunk ┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cf000204141 ┆; p AAUtilization ................... 62 3.5.2 Gateway ........................................ 63 3.5.3 EMH Modelling .................................. 64 3.5.4 Reliability and Availability ................... 67 ilket? ┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00204141 ┆; AA 1 3.6 Baseline Capacity and Projected Growth ......... 69 3.6.1 Baseline Capacity .............................. 69 3.6.2 Projected Growth ......................┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00204141 ┆; AA......... 70 3.6.3 Block Diagrams ................................. 72 3.7 Telecommunications ............................. 77 3.8 Options ........................................ 78 3.8.1 Videotex .................┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0f6300204141 ┆; c AA...................... 80 3.8.2 High Density Digital Tape Recordings ........... 83 20 04 82 08 55 7 10 11838 27 04 82 20 08 11 270 27 04 82 20 40 16 07 82 10 58 1006V 83 16 48 1700 34710 f *J B ? _┆
0x3bf00…3c000 (59, 0, 15) Sector 3b00ff00204141 ┆; AA 1 LIST OF FIGURES 3.1-1 Present Air Canada Data Networks.......... 6 3.2-1 Proposed Architecture..................... 12 3.2-2 ACDN/081 Reference Model Mapping ......... 14 3┆
0x3c000…3c100 (60, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(60,0, 1), len=0xff, h3=41204141}, f00=»2041A «, f01=»AIR CANADA PROPOSAL «, f02=»ba «, f03=»FR «, f04=»DOC. III Chapter 3 «, f05=20-04-82 08:55, f06=» 7 «, f07=»10 «, f08=» 11838 «, f09=27-04-82 20:08, f10=» «, f11=»11 «, f12=» 270 «, f13=27-04-82 20:40, f14=16-07-82 10:58, f15=»1006V «, f16=» 83 «, f17=» 16 «, f18=»48 «, f19=» 1700 «, f20=» 34710 «, f21=» «, f22=» «, f99=020010000110056610110280aaca1505000000000000004203bf01df}
0x3c100…3c200 (60, 0, 1) Sector 3c025300204141 ┆< S AAJ < < ; ; ; : : : 9 9 8 8 8 7 7 7 7 6 6 6 5 5 5 5 4 4 4 3 3 3 3 2 2 1 1 1 1 0 / / / . . . - - - , , , + + * * ) ) ( ( ( ' ' & & & & % % $ $ $ $ # # # # # # " " " " ! ! ┆
0x3c200…3c300 (60, 0, 2) Sector 3c03fb00204141 ┆< { AA 1 CHAPTER 3 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00204141 ┆< AA 1 1 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00204141 ┆< AA........ 4 3.1 Introduction ................................... 5 3.2 Proposed Technical Solution .................... 7 3.2.1 Scope of Air Canada Data Network ............... 7 3.2.2 Proposed Network Architect┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00204141 ┆< AAure .................. 11 3.2.2.1 Network Interface Environment .................. 15 3.2.2.2 Communication User Environment ................. 16 3.2.2.3 Data Transmission Environment .................. 19 3.2.2.4 Data Link Envi┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00204141 ┆< AAronment .......................... 20 3.2.2.5 Network Service Environment .................... 21 3.2.2.6 Network Topology................................ 23 3.2.2.7 Network Architecture Realisations .............. 26 3.2.3 Fu┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00204141 ┆; AAnctional Overview ............................ 28 3.2.4 External Environments .......................... 31 3.2.5 Deliverables ................................... 34 3.3 Proposed Hardware Equipment .................... 40 ┆
0x3c800…3c900 (60, 0, 8) Sector 3c093f00204141 ┆< ? AA functions should be easily added within the structure. rom the existing network environment to an enhanced network environment. When the above premises are mapped on to the available networking solutions from Christian Rovsing a primary r┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00204141 ┆< AA 1 The general purpose computer facilities may include software for supporting remote terminals and associated communication procedures. ACDN, as conceived and presented in this prop┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00204141 ┆< AAosal, excludes all such facilities in their entirety. However, the implied transparancy in the ACDN is such that any general purpose computing facility can be interfaced to ACDN. It is our conviction that in the 1980s there is no real need to dist┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00204141 ┆< AAinguish between terminals and computing facilities, and as such we use the words synonymously. However, there is a distinction between the interfacing mechanisms which are attachments to the ACDN and those which are participants. This distinction┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00204141 ┆< AA is as follows: a. Attachments to ACDN Any computing facility can be interfaced to the ACDN as an "attachment". Attachment implies that a computing facility, irrespective of the complexity and scope, behaves like a single terminal or a clu┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00204141 ┆< AAster of terminals with predetermined characteristics. Attachment implies that a computing facility so interconnected does not play any role in providing and controlling the resources made available to the whole spectrum of ACDN users. b. Part┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00204141 ┆< AAicipants in ACDN Any computing facility can be interfaced to ACDN as a "participant". Being a participant implies that application resources contained in that computing facility are made available to all ACDN users. The control functions in t┆
0x3cf00…3d000 (60, 0, 15) Sector 3b08e000204141 ┆; ` AAhe ACDN monitor the status of the application resources in each participant and maintains the validity of the resource status on a network wide basis. Such a participant is also referred to as a "HOST" synonymously. in the reduced development eff┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00204141 ┆= AAort by using an existing network product, a distributed application development should have a good performance to cost ratio. d. Support a Wide Range of Topologies: The architecture should support communication between users independent of the in┆
0x3d100…3d200 (61, 0, 1) Sector 3d02ff00204141 ┆= AAtervening data transport network. The interconnection structure of the computers and communication facilities should not affect the logical communication capabilities of the applications. e. Be Highly Available: The overall operation of the netwo┆
0x3d200…3d300 (61, 0, 2) Sector 3d036e00204141 ┆= n AArk should not be adversely affected by the failure of a topologically noncritical node and/or channel. PRESENT AIR CANADA DATA NETWORKS ...... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00204141 ┆= AA 1 f. Be Extensible: The architecture should allow for the incorporation of future technology changes in hardware and/or software: for the movement of functions across the hardware/s┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00204141 ┆= AAoftware boundary, taking advantage of new technological innocations in both domains; and for the subsettability of functions to allow smaller, lower performance nodes. g. Be Easily Implementable: The architecture should be independent of the inte┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00204141 ┆= AArnal characteristics of the hosts and their operating systems and be easily and efficiently implemented on a wide variety of heterogeneous hardware and software. h. Use a Hierarchical Layered Structure: This will create a highly flexible structur┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00204141 ┆= AAe with ease of layer replacement and modularity. i. Uniformly Address all Nodes: The topology should not restrict access. Nodes should be characterized only by the functions they perform, and not by their location in the network. j. Implement F┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00204141 ┆< AAunctions at the Highest Practical Efficient Level Within the Structure: Such functions as network control and maintenance should execute at the level of application programs. k. Be Dynamic: Protocols should be flexible to change; new modules and┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00204141 ┆= AAnd coverage. ... a need to realise a stable migration from the existing network environment to an enhanced network environment. When the above premises are mapped on to the available networking solutions from Christian Rovsing a primary r┆
0x3d900…3da00 (61, 0, 9) Sector 3d0a5300204141 ┆= S AAationale for the proposed Air Canada Data Network (ACDN) is seen to evolve. duction The scope of this chapter is to convey to the Technical Management function in Air Canada, the underlying precepts of the solution proposed by Christian Rovsing t┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00204141 ┆= AA 1 The solution to the Air Canada Data Network proposed herein, is based on a network architecture which has evolved over the last five years and is used in national as well as intern┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00204141 ┆= AAational private networks, where high performance, reliability, security and flexibility were essential. The proposed network architecture has been designed to create a communication mechanism which supports a wide range of user applications, host ┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00204141 ┆= AAcomputer systems and interconnect technologies. Specifically, the goals are the following: a. Create a Common User Interface: The application interface to the network should support a broad spectrum of application communication requirements and ┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00204141 ┆= AAshould be common across the varied implementations. Within such a network environment, applications may be moved among the systems in the network, with the common interface hiding the internal characteristics and topology of the network. b. Suppor┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00204141 ┆= AAt a Wide Range of Communication Facilities: The network should be adaptable to changes in communication technology and operate with a variety of communication channels using appropriate cost effective technology. Today this may be leased ground cir┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00204141 ┆= AAcuits, in a few years it may be satellite channels. c. Be Cost Effective: The network should approach the efficiency and performance of a network designed specifically for a given application. In addition, factoring in the reduced development eff┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ff00204141 ┆> AA, are presented,in section 3.5. Finally, section 3.6 discusses the projected growth capabilities of the network with respect to capacity and functionality, 3.7 describes the telecommunication support provided by CNCP, while 3.8 discusses potential┆
0x3e100…3e200 (62, 0, 1) Sector 3e021600204141 ┆> AA growth areas. 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x3e200…3e300 (62, 0, 2) Sector 3e038fa1204141 ┆> ! AA 1 Figure III 3.1-1 PRESENT AIR CANADA DATA NETWORKS ...... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00204141 ┆> AA 1 3.2 Proposed Technical Solution 3.2.1 Scope of ACDN Air Canada Data Network (ACDN) is perceived as a transparent common communication service capable of interfacing a variety of ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00204141 ┆> AAterminals, terminal concentrators, and a variety of general purpose mini or mainframe based computing facilities. The computing facilities of Air Canada as they exist today, are presented in a generalized and simplified view in Figure III 3.1-1 "┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00204141 ┆> AAPresent Air Canada Data Networks". Each of the networks provides specific sets of services to the user. The discernible premises for the RFP are: ... a high degree of transparancy in the network necessitated by the diversity of users and s┆
0x3e600…3e700 (62, 0, 6) Sector 3e07ff00204141 ┆> AAervices ... a need to interface to and permit access to application resources in UNIVAC, HONEYWELL, IBM mainframes. ... a need to provide network management and admini- stration facilities that can be exploited by the network maintenanc┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00204141 ┆= AAe staff organization at the central and remote sites. ... a need to support new services like facsimile data transmission and digitised voice transmission. ... a need to coexist with external networks that provide complementary services a┆
0x3e800…3e900 (62, 0, 8) Sector 3e098c00204141 ┆> AA Subscriber services: By exploiting available standard software and firmware for host support and terminal devices support. .2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00204141 ┆> AA 1 3.1 Introduction The scope of this chapter is to convey to the Technical Management function in Air Canada, the underlying precepts of the solution proposed by Christian Rovsing t┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00204141 ┆> AAo meet the functional requirements contained in the Air Canada RFP. This chapter also serves to provide a high level breakdown of the proposed Air Canada Data Network including the associated rationale. The breakdown is covered in terms of hardwar┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0cff00204141 ┆> AAe and software architectures. The software is presented in terms of the 7-layer OSI reference model. Additionally, this chapter presents the predicted performance and response times. The proposed solution is presented in a broad context in secti┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00204141 ┆> AAon 3.2. Subsection 3.2.1 provides the scope of the backbone network as perceived by Air Canada while subsection 3.2.2 presents the proposed network architecture by covering internal environments, network topology together with possible network rea┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00204141 ┆> AAlizations. Subsection 3.2.3 gives a functional overview on the proposed Air Canada Data Network, while subsection 3.2.4 defines and presents the external "environments" to which the proposed Air Canada Data Network provides service. The deliverab┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00204141 ┆> AAle hardware and software mapping on the environments of the architecture is provided in subsection 3.2.5. Section 3.3 provides the high-level break-down of the hardware. The software functional basis and structure is presented in section 3.4. T┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00204141 ┆> AAhis section covers interfaces to the backbone network from users, i.e. from host computers, other networks, via the Gateway to the existing network, and to terminal equipment. Results of the performance analysis, i.e. response times and capacities┆
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00204141 ┆? AA.2-3 Network Protocols ........................ 17 3.2-4 Topology Example ......................... 24 3.2-5 C-NODE Partitioning ...................... 25 3.2-6 Network Architecture Realizations ........ 27 3.2-7 Air Canada Computing Environ┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00204141 ┆? AAment ......... 29 3.2-8 Proposed Network Architecture ............ 35 3.2-9 Hardware and Software Mapping ............ 35 3.3-1 Proposed Node Network .................... 41 3.4-1 ACDN Software Packages ................... 45 3.4-2 ACDN So┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00204141 ┆? AAftware Structure .................. 45 3.4-3 ACDN Software ............................ 47 3.4-4 Network Interfaces Environment ........... 51 3.6-1 Projected Growth Toronto ................. 73 3.6-2 Projected Growth Montreal ..............┆
0x3f300…3f400 (63, 0, 3) Sector 3f047b00204141 ┆? { AA.. 74 3.6-3 Projected Growth Winnipeg ................ 75 3.6-4 Projected Growth, EMH .................... 76 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00204141 ┆? AA 1 3. PROPOSED SOLUTION To the full extent that Air Canada is embarking on establishing a network base for the 1980s with the knowledge of the positive impact this will have on Air ┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00204141 ┆? AACanadas operations, services to the passengers and to the airline industry's commercial infrastructure, we have presented in this chapter our solution in the context of a broad perspectiv over the trends in data communications industry in the 1980s.┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00204141 ┆? AA The key themes behind our proposed solution are: High availability: Through fault tolerance and redundant hardware and through a unique network control philosophy. Granular Expandability: Through a scheme that exploits ┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00204141 ┆> AAmultiprocessing configuratons and distributed functions. Investment Protection: Through a networking scheme that supports heterogenous hosts, data transport services, terminal types and a networking scheme based on available standards.┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00204141 ┆? AA3.4 Proposed Software Packages ..................... 44 3.4.1 Access Software Package......................... 48 3.4.2 Nodal Switching Software Package................ 50 3.4.3 Network Control Software Package..........┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00204141 ┆? AA...... 52 3.4.4 Network Management Software Package............. 54 3.4.5 Electronic Mail Software Package................ 55 3.5 Performance .................................... 57 3.5.1 Node Modelling ..............┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bff00204141 ┆? AA................... 58 3.5.1.1 End-to-End Response Time ....................... 58 3.5.1.2 Processor Utilization and Capacity.............. 59 3.5.1.3 Memory Utilization ............................. 60 3.5.1.4 Internodal Trunk ┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cf000204141 ┆? p AAUtilization ................... 62 3.5.2 Gateway ........................................ 63 3.5.3 EMH Modelling .................................. 64 3.5.4 Reliability and Availability ................... 67 ilket? ┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00204141 ┆? AA 1 3.6 Baseline Capacity and Projected Growth ......... 69 3.6.1 Baseline Capacity .............................. 69 3.6.2 Projected Growth ......................┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00204141 ┆? AA......... 70 3.6.3 Block Diagrams ................................. 72 3.7 Telecommunications ............................. 77 3.8 Options ........................................ 78 3.8.1 Videotex .................┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0f6300204141 ┆? c AA...................... 80 3.8.2 High Density Digital Tape Recordings ........... 83 20 04 82 08 55 7 10 11838 27 04 82 20 08 11 270 27 04 82 20 40 29 04 82 10 41 1006V 83 16 48 1700 34710 f *J B ~ _┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00204141 ┆? AA 1 LIST OF FIGURES 3.1-1 Present Air Canada Data Networks.......... 6 3.2-1 Proposed Architecture..................... 12 3.2-2 ACDN/081 Reference Model Mapping ......... 14 3┆
0x40000…40100 (64, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(64,0, 1), len=0xff, h3=41204141}, f00=»2041A «, f01=»AIR CANADA PROPOSAL «, f02=»ba «, f03=»FR «, f04=»DOC. III Chapter 3 «, f05=20-04-82 08:55, f06=» 7 «, f07=»10 «, f08=» 11838 «, f09=27-04-82 20:08, f10=» «, f11=»11 «, f12=» 270 «, f13=27-04-82 20:40, f14=29-04-82 10:41, f15=»1006V «, f16=» 83 «, f17=» 16 «, f18=»48 «, f19=» 1700 «, f20=» 34710 «, f21=» «, f22=» «, f99=020010000110056610110280aaca1505000000000000004203bf01df}
0x40100…40200 (64, 0, 1) Sector 40025300204141 ┆@ S AAJ @ @ ? ? ? > > > = = < ; ; ; ; ; : : : 9 9 9 8 8 8 8 7 7 7 6 6 6 5 5 5 4 4 4 3 3 2 2 2 1 1 0 0 0 0 / / . . - - , , , + + * * * ) ) ) ( ( ' ' ' ' & & & & & & & % % % $ $ ┆
0x40200…40300 (64, 0, 2) Sector 4003fb00204141 ┆@ { AA 1 CHAPTER 3 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x40300…40400 (64, 0, 3) Sector 4004ff00204141 ┆@ AA 1 1 LIST OF CONTENTS Page 3. PROPOSED SOLUTION ......................┆
0x40400…40500 (64, 0, 4) Sector 4005ff00204141 ┆@ AA........ 4 3.1 Introduction ................................... 5 3.2 Proposed Technical Solution .................... 7 3.2.1 Scope of Air Canada Data Network ............... 7 3.2.2 Proposed Network Architect┆
0x40500…40600 (64, 0, 5) Sector 4006ff00204141 ┆@ AAure .................. 11 3.2.2.1 Network Interface Environment .................. 15 3.2.2.2 Communication User Environment ................. 16 3.2.2.3 Data Transmission Environment .................. 19 3.2.2.4 Data Link Envi┆
0x40600…40700 (64, 0, 6) Sector 4007ff00204141 ┆@ AAronment .......................... 20 3.2.2.5 Network Service Environment .................... 21 3.2.2.6 Network Topology................................ 23 3.2.2.7 Network Architecture Realisations .............. 26 3.2.3 Fu┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00204141 ┆? AAnctional Overview ............................ 28 3.2.4 External Environments .......................... 31 3.2.5 Deliverables ................................... 34 3.3 Proposed Hardware Equipment .................... 40 ┆
0x40800…40900 (64, 0, 8) Sector 00000000000000 ┆ ┆
[…0xc7…]
