OctetView
0x00000…00100 (0, 0, 0) Sector 00164130303136 ┆ A0016A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fff0ffff ┆ @ p |x p ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x01, d01=0x73, d02=0x41, ptr=(62,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x01, d01=0x74, d02=0x41, ptr=(67,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x01, d01=0x75, d02=0x41, ptr=(39,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x01, d01=0x76, d02=0x41, ptr=(59,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x01, d01=0x77, d02=0x41, ptr=(57,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x01, d01=0x93, d02=0x41, ptr=(65,0, 0), d05=0x00}
0x00324…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 ┆ ┆
0x00340…00360 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 ┆ ┆
[…0x4…]
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 24 ┆ $┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 d N N ~<) 0u &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' 8 X% % PO P ; wA C h x h V W O 7 : # L 0177A h g | {C < ; 7 c b b* ( R 9 : 8 Q yr ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x1…]
0x01200…01300 (1, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0xb…]
0x02400…02500 (2, 0, 4) Sector 0205ff00017341 ┆ sA 1 - Transaction ID = LOT030 241756ZAUG. - The message is stored in HDB under key = Above transaction ID LOT030 241756Z AUG. - Transaction is logged at initiation and term┆
0x02500…02600 (2, 0, 5) Sector 0206ff00017341 ┆ sAination. Step 7 The message is presented to the designated release position at terminal position 2 with Terminal Designator RET. If release is granted the message will receive a new identification: RXYYY 0056 2361811, where RXYYY Relea┆
0x02600…02700 (2, 0, 6) Sector 0207ff00017341 ┆ sAse position code (RI). 0056 a release serial number unique for the 236,18,11 Time of release granted in Julian Date Hr, Min. - Transaction ID=RET077 241806 Z AUG - The new message identification code will be added as a retri┆
0x02700…02800 (2, 0, 7) Sector 0108ff00017341 ┆ sAeval key to the message stored in the HDB during step 6 - Transaction is logged at termination. Step 8 The converted message is transmitted to external channel CHO with ID in message header equal to transaction ID. - Transaction ID = CHO ┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x25…]
0x04e00…04f00 (4, 0, 14) Sector 040fff00017341 ┆ sAy, and for each week of the last current month. The statistical information include: total number of messages by precedence level, number of messages by security classification category, number of messages by special handling category. A special s┆
0x04f00…05000 (4, 0, 15) Sector 0400f500017341 ┆ u sAtatistic is compiled for messages rejected for manual editing including: total number of rejected messages, transmission identifications, routing indicator of station or origin, time of receipt, time(s) of retry, reason(s) for rejection. al - Log┆
0x05000…05100 (5, 0, 0) WangDocumentBody
[…0x4…]
0x05500…05600 (5, 0, 5) Sector 0506c500019341 ┆ E Aisor. Dato messages shall (on detection of special handling designator D) be sent to the MDCO, inless detection of format lines 7 (PLA) and 12b (SIC) provide for automatic distribution. arters. ch message consist of a number of format lines. ┆
0x05600…05700 (5, 0, 6) Sector 0507ff00019341 ┆ A 1 3.2.2.3.3 Distribution of Service Messages All service messages (also abbreviated) shall always be directed to the supervisor except those related to channel control as specifie┆
0x05700…05800 (5, 0, 7) Sector 0408ff00019341 ┆ Ad in section 3.3.1 and 3.3.2. 3.2.2.4 Procedures Related to Receipt of FLASH Messages If messages received by a CAMPS has the precedence FLASH and format line 4 of the message does not contain an inhibit receipt flag (ZGC) a service message as ┆
0x05800…05900 (5, 0, 8) WangDocumentBody
[…0x217…]
0x27000…27100 (39, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(39,0, 1), len=0xff, h3=41017541}, f00=»0175A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»gj «, f04=»fra 3.2.3 «, f05=11-09-80 10:56, f06=» 3 «, f07=»20 «, f08=» 4889 «, f09=18-09-80 14:28, f10=» «, f11=»03 «, f12=» 37 «, f13=18-09-80 14:45, f14=18-09-80 14:46, f15=»0016A «, f16=» 35 «, f17=» 4 «, f18=»52 «, f19=» 668 «, f20=» 6201 «, f21=» «, f22=» «, f99=210010000120056610a10a80aaca1505000000000000003703cc00df}
0x27100…27200 (39, 0, 1) WangDocumentBody
[…0x22…]
0x29400…29500 (41, 0, 4) Sector 0000fe00017641 ┆ ~ vAher sites and loaded (e.g. floppy disk). p) It is acceptable that the media above are loaded/interfaced on the same drives/via the same units as used for mounting offline storage for retrieval and as used for software input at initialization. .┆
0x29500…29600 (41, 0, 5) Sector 2906ff00017641 ┆) vAe processing of the retrieval implicit in retrieve and distribute is similar and with the same restrictions as normal retrievals. 3.2.4.4 Reports 3.2.4.4.l. General Reports shall be produced by the system to draw the attention of the superviso┆
0x29600…29700 (41, 0, 6) Sector 2907ff00017641 ┆) vAry staff to specific events as specified below. Each report shall as specified be printed out or stored in the outstanding report file. Reports for which printout is specified shall be queued for printout at report teleprinter. Printout of rep┆
0x29700…29800 (41, 0, 7) Sector 28088e00017641 ┆( vAorts above shall be preceded by a "BELL". Reports for which storage have been specified are written to the outstanding report file. icer shall be able to modify the message in order to correct the group count. The message servicer shall after ┆
0x29800…29900 (41, 0, 8) WangDocumentBody
[…0xf7…]
0x39000…39100 (57, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(57,0, 1), len=0xff, h3=41017741}, f00=»0177A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»GJ «, f04=»fra 3.2.5 «, f05=11-09-80 11:12, f06=» 3 «, f07=»48 «, f08=» 3371 «, f09=17-09-80 19:18, f10=» «, f11=»03 «, f12=» 48 «, f13=17-09-80 19:43, f14=17-09-80 19:51, f15=»0016A «, f16=» 34 «, f17=» 4 «, f18=»50 «, f19=» 536 «, f20=» 4666 «, f21=» «, f22=» «, f99=030010000120056610a10a80aaca1505000000000000003703aa00df}
0x39100…39200 (57, 0, 1) WangDocumentBody
[…0x1e…]
0x3b000…3b100 (59, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(59,0, 1), len=0xff, h3=41017641}, f00=»0176A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»GJ «, f04=»fra 3.2.4 «, f05=11-09-80 11:05, f06=» 1 «, f07=»22 «, f08=» 2238 «, f09=18-09-80 20:45, f10=» «, f11=»02 «, f12=» 18 «, f13=18-09-80 14:48, f14=18-09-80 20:47, f15=»0016A «, f16=» 39 «, f17=» 5 «, f18=»18 «, f19=» 620 «, f20=» 7413 «, f21=» «, f22=» 0 «, f99=930010000120056610a10a80aaca1505000000000000003703c400df}
0x3b100…3b200 (59, 0, 1) WangDocumentBody
[…0x36…]
0x3e800…3e900 (62, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(62,0, 9), len=0xff, h3=41017341}, f00=»0173A «, f01=»CPS/SYS/001 - issue II «, f02=»am] «, f03=»gj «, f04=» «, f05=11-09-80 10:15, f06=» 5 «, f07=»38 «, f08=» 10971 «, f09=13-10-80 13:19, f10=» «, f11=»14 «, f12=» 373 «, f13=19-09-80 09:09, f14=13-10-80 13:41, f15=»0016A «, f16=» 45 «, f17=» 8 «, f18=»48 «, f19=» 748 «, f20=» 14894 «, f21=» «, f22=» «, f99=800010000120056610a10a80aaca1505000000000000003703e600df}
0x3e900…3ea00 (62, 0, 9) WangDocumentBody
[…0x6…]
0x3f000…3f100 (63, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(63,0, 1), len=0xff, h3=41017341}, f00=»0173A «, f01=»CPS/SYS/001 - issue II «, f02=»am] «, f03=»gj «, f04=» «, f05=11-09-80 10:15, f06=» 5 «, f07=»38 «, f08=» 10971 «, f09=13-10-80 13:19, f10=» «, f11=»14 «, f12=» 373 «, f13=19-09-80 09:09, f14=13-10-80 13:33, f15=»0016A «, f16=» 45 «, f17=» 8 «, f18=»48 «, f19=» 748 «, f20=» 14894 «, f21=» «, f22=» «, f99=800010000120056610a10a80aaca1505000000000000003703e600df}
0x3f100…3f200 (63, 0, 1) Sector 3f022d00017341 ┆? - sA ? ? > > = = ent nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : : : : : : ┆
0x3f200…3f300 (63, 0, 2) Sector 3f039700017341 ┆? sA 1 CPS/210/SYS/0001 800919 CAMPS SYSTEM REQUIREMENTS CAMPS ~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00017341 ┆? sA 1 1 TABLE OF CONTENTS 1 SCOPE ........................................ 1-1 2 APPLICABLE DOCUMENTS .........┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00017341 ┆? sA................ 2-3a 2.1 APPLICABLE DOCUMENTS ..................... 2 2.2 REFERENCE DOCUMENTS ...................... 3 2.3 TERMS .................................... 3 3 REQUIREMENTS ................................. 4-3┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00017341 ┆? sA48 3.1 SYSTEM DEFINITION ........................ 7 3.1.1 General Description .................... 8 3.1.1.1 Connectivity of a CAMPS Site ....... 8 3.1.1.2 Logical Addressing Scheme .......... 14 3.1.1.3 Functional Capa┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00017341 ┆? sAbilities ............ 20 3.1.2 Message Flow ......................... 30 3.2 FUNCTIONAL REQUIREMENTS .................. 39 3.2.1 Outgoing Messages .................... 42 3.2.1.1 Message Types and their Flow ┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00017341 ┆> sA through the CAMPS System ......... 42 3.2.1.2 Operational Messages ............ 47 3.2.1.3 Service Message .................. 61 3.2.1.4 Entry of Complete Messages ....... 64 3.2.1.5 ACP 127 Conversion .............┆
0x3f800…3f900 (63, 0, 8) WangDocumentBody
[…0x17…]
0x41000…41100 (65, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(65,0, 1), len=0xff, h3=41019341}, f00=»0193A «, f01=»CPS/210/SYS/0001 «, f02=»am] «, f03=»gj «, f04=»fra 3.2.2 «, f05=16-09-80 14:11, f06=» 1 «, f07=»28 «, f08=» 5709 «, f09=18-09-80 18:22, f10=» «, f11=»01 «, f12=» 13 «, f13=18-09-80 18:48, f14=18-09-80 18:55, f15=»0016A «, f16=» 14 «, f17=» 1 «, f18=»38 «, f19=» 148 «, f20=» 5888 «, f21=» «, f22=» «, f99=100010000120056610a10a80aaca15050000000000000037033500df}
0x41100…41200 (65, 0, 1) WangDocumentBody
[…0x26…]
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41017441}, f00=»0174A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»gj «, f04=»fra 3.2 «, f05=11-09-80 10:45, f06=» 6 «, f07=»37 «, f08=» 11015 «, f09=18-09-80 19:15, f10=» «, f11=»03 «, f12=» 30 «, f13=18-09-80 19:29, f14=18-09-80 19:35, f15=»0016A «, f16=» 40 «, f17=» 6 «, f18=»46 «, f19=» 608 «, f20=» 11131 «, f21=» «, f22=» «, f99=810010000120056610a10a80aaca1505000000000000003003c000df}
0x43900…43a00 (67, 0, 9) WangDocumentBody
[…0x6…]
0x44000…44100 (68, 0, 0) Sector 4401ff41017441 ┆D A tA0174A CPS/SYS/001 issue II am] gj fra 3.2 11 09 80 10 45 6 37 11015 18 09 80 19 15 03 30 18 09 80 18 59 18 09 80 19 18 0016A 40 6 46 608 11131 0 f ! *J 0 @ _┆
0x44100…44200 (68, 0, 1) Sector 44022800017441 ┆D ( tA D D C C C B B B B B A A A ? < < < ; 4 UMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / / / / / ┆
0x44200…44300 (68, 0, 2) Sector 44039700017441 ┆D tA 1 CPS/210/SYS/0001 800919 CAMPS SYSTEM REQUIREMENTS CAMPS ~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44300…44400 (68, 0, 3) Sector 4404ff00017441 ┆D tA 1 3.2 Functional Requirements The following section will exhaustively specify the functional requirements to CAMPS. Section 3.2.1 and 3.2.2 defines all functional capabilities rel┆
0x44400…44500 (68, 0, 4) Sector 4405ff00017441 ┆D tAated to processing of outgoing and incoming messages respectively. The sequence in which the functional capabilities are presented are as they appear during message processing. Section 3.2.3 specifies all functional capabilities related to termina┆
0x44500…44600 (68, 0, 5) Sector 4406ff00017441 ┆D tAls and the associated equipment. The section has been structured in such a way, that it presents the functional capabilities seen from a user's point of view. Section 3.2.4 defines all required capabilities for supervisory control commands, messag┆
0x44600…44700 (68, 0, 6) Sector 4407ff00017441 ┆D tAe service, message distribution control, system status and alarm, engineering functions and software maintenance. The Section is not presented from an operational point of view, but more in terms of functional capabilities. Section 3.2.5 specifie┆
0x44700…44800 (68, 0, 7) Sector 4308ff00017441 ┆C tAs the events for which log entries shall be made and the information associated with the log entries. Section 3.2.6 defines the required statistical reports related to channel traffic and transactions at terminals. Section 3.2.7 specifies storag┆
0x44800…44900 (68, 0, 8) Sector 4409ff41017441 ┆D A tA0174A CPS/SYS/001 issue II am] gj fra 3.2 11 09 80 10 45 6 37 11015 18 09 80 17 50 04 67 18 09 80 15 46 18 09 80 17 54 0016A 40 6 43 604 11101 0 f ! *J 0 @ _┆
0x44900…44a00 (68, 0, 9) Sector 440a2800017441 ┆D ( tA D D D C C C C B B B < < < < ; ; 4 UMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / / / / / ┆
0x44a00…44b00 (68, 0, 10) Sector 440b9700017441 ┆D tA 1 CPS/210/SYS/0001 800919 CAMPS SYSTEM REQUIREMENTS CAMPS ~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00017441 ┆D tA 1 3.2 Functional Requirements The following section will exhaustively specify the functional requirements to CAMPS. Section 3.2.1 and 3.2.2 defines all functional capabilities rel┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00017441 ┆D tAated to processing of outgoing and incoming messages respectively. The sequence in which the functional capabilities are presented are as they appear during message processing. Section 3.2.3 specifies all functional capabilities related to termina┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00017441 ┆D tAls and the associated equipment. The section has been structured in such a way, that it presents the functional capabilities seen from a user's point of view. Section 3.2.4 defines all required capabilities for supervisory control commands, messag┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00017441 ┆D tAe service, message distribution control, system status and alarm, engineering functions and software maintenance. The Section is not presented from an operational point of view, but more in terms of functional capabilities. Section 3.2.5 specifie┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00017441 ┆D tAs the events for which log entries shall be made and the information associated with the log entries. Section 3.2.6 defines the required statistical reports related to channel traffic and transactions at terminals. Section 3.2.7 specifies storag┆
0x45000…45100 (69, 0, 0) Sector 4501ff00017341 ┆E sA4 Entry of Complete Messages ....... 59 3.2.1.5 ACP 127 Conversion ............... 60 3.2.1.6 Transmission ..................... 71 3.2.2 Incoming Messages .................... 76 3.2.2.1 Message Reception Procedures ...┆
0x45100…45200 (69, 0, 1) Sector 4502e000017341 ┆E ` sA.. 76 3.2.2.2 ACP 127 Analysis ................. 79 3.2.2.3 Message Distribution ............. 85 3.2.2.4 Procedures Related to Receipt of Flash Messages ................ 89 2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x45200…45300 (69, 0, 2) Sector 4503ff00017341 ┆E sA 1 3.2.3 Terminal Functions and Characteristics ...................... 91 3.2.3.1 Equipment and Functions allocatable to a Terminal ┆
0x45300…45400 (69, 0, 3) Sector 4504ff00017341 ┆E sA Position ......................... 93 3.2.3.2 Terminal Access Control .......... 97 3.2.3.3 Functional Capabilities of Terminal Procedures .............. 101 3.2.3.4 Precedence and Queueing .....┆
0x45400…45500 (69, 0, 4) Sector 4505ff00017341 ┆E sA..... 110 3.2.3.5 Terminal Modes ................... 113 3.2.3.6 Status Information Available from Terminal Positions .......... 120 3.2.3.7 Presentation of Information at Terminal Positions┆
0x45500…45600 (69, 0, 5) Sector 4506ff00017341 ┆E sA ............... 122 3.2.4 Supervisory Function ................. 131 3.2.4.1 Supervisor Functions ............. 134 3.2.4.2 Message Service .................. 152 3.2.4.3 Message Distribution Control ..... 156 3.2.4.4 ┆
0x45600…45700 (69, 0, 6) Sector 4507ff00017341 ┆E sA Reports .......................... 160 3.2.4.5 Engineering Functions ............ 164 3.2.5 Logging .............................. 168 3.2.5.1 Categories of Transactions to be Logged ........................ 1┆
0x45700…45800 (69, 0, 7) Sector 4300ff00017341 ┆C sA68 3.2.5.2 Logging Events ................... 168 3.2.5.3 Storage of Log Records ........... 169 3.2.5.4 Print of Log Records ............. 169 3.2.5.5 Tracing (Computer Analysis) of Log Information .......┆
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41017341}, f00=»0173A «, f01=»CPS/SYS/001 - issue II «, f02=»am] «, f03=»gj «, f04=» «, f05=11-09-80 10:15, f06=» 5 «, f07=»38 «, f08=» 10971 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=17-09-80 17:43, f14=17-09-80 18:23, f15=»0016A «, f16=» 46 «, f17=» 5 «, f18=»38 «, f19=» 964 «, f20=» 10971 «, f21=» «, f22=»( «, f99=020010000120056610a10a80aaca1505000000000000003703e900df}
0x45900…45a00 (69, 0, 9) Sector 450a2e00017341 ┆E . sA E E E C @ ? ? > > = = = = ent nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : : : : : ┆
0x45a00…45b00 (69, 0, 10) Sector 450b9700017341 ┆E sA 1 CPS/210/SYS/0001 800919 CAMPS SYSTEM REQUIREMENTS CAMPS ~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00017341 ┆E sA 1 1 TABLE OF CONTENTS 1 SCOPE ........................................ 1 2 APPLICABLE DOCUMENTS ...........┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00017341 ┆E sA.............. 2 3 REQUIREMENTS ................................. 3 3.1 SYSTEM DEFINITION ........................ 6 3.1.1 Connectivity of a CAMPS Site ......... 7 3.1.2 Logical Addressing Scheme ............ 12 3.1.3┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00017341 ┆E sA Functional Capabilities .............. 18 3.1.3.1 Handling of Messages ............. 18 3.1.3.2 System Supervision ............... 23 3.1.3.3 Storage and Retrieval ............ 25 3.1.3.4 Logging .......................┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00017341 ┆E sA... 25 3.1.3.5 Statistics ....................... 25 3.1.3.6 Security ......................... 26 3.1.4 Message Flow ......................... 29 3.2 FUNCTIONAL REQUIREMENTS .................. 37 3.2.1 Outgoing Mess┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00017341 ┆E sAages .................... 40 3.2.1.1 Message Types and their Flow through the CAMPS System ......... 40 3.2.1.2 Operational Messages ............ 45 3.2.1.3 Service Message .................. 57 3.2.1.┆
0x46000…46100 (70, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(70,0, 1), len=0xff, h3=41017441}, f00=»0174A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»gj «, f04=»fra 3.2 «, f05=11-09-80 10:45, f06=» 6 «, f07=»37 «, f08=» 11015 «, f09=18-09-80 15:43, f10=» «, f11=»02 «, f12=» 19 «, f13=18-09-80 15:46, f14=18-09-80 16:23, f15=»0016A «, f16=» 40 «, f17=» 6 «, f18=»39 «, f19=» 760 «, f20=» 11034 «, f21=» «, f22=» 0 «, f99=020010000120056610a10a80aaca1505000000000000003003c000df}
0x46100…46200 (70, 0, 1) Sector 46022800017441 ┆F ( tA F F D D D C C < < < < < < ; 4 4 UMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / / / / / ┆
0x46200…46300 (70, 0, 2) Sector 46039700017441 ┆F tA 1 CPS/210/SYS/0001 800919 CAMPS SYSTEM REQUIREMENTS CAMPS ~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46300…46400 (70, 0, 3) Sector 4604ff00017441 ┆F tA 1 3.2. Functional Requirements The following section will exhaustively specify the functional requirements to CAMPS. Section 3.2.1 and 3.2.2 defines all functional capabilities re┆
0x46400…46500 (70, 0, 4) Sector 4605ff00017441 ┆F tAlated to processing of outgoing and incoming messages respectively. The sequence in which the functional capabilities are presented are as they appear during message processing. Section 3.2.3 specifies all functional capabilities related to termin┆
0x46500…46600 (70, 0, 5) Sector 4606ff00017441 ┆F tAals and the associated equipment. The section has been structured in such a way, that it presents the functional capabilities seen from a user's point of view. Section 3.2.4 defines all required capabilities for supervisory control commands, messa┆
0x46600…46700 (70, 0, 6) Sector 4607ff00017441 ┆F tAge service, message distribution control, system status and alarm, engineering functions and software maintenance. The Section is not presented from an operational point of view, but more in terms of functional capabilities. Section 3.2.5 specifi┆
0x46700…46800 (70, 0, 7) Sector 4408ff00017441 ┆D tAes the events for which log entries shall be made and the information associated with the log entries. Section 3.2.6 defines the required statistical reports related to channel traffic and transactions at terminals. Section 3.2.7 specifies stora┆
0x46800…46900 (70, 0, 8) Sector 4609ff00017841 ┆F xAange of channel sequence numbers a) When no transmission has been received on an incoming message channel from TRC within a period set by the supervisor CAMPS shall transmit a self-addressed channel check message on the corresponding "send" channe┆
0x46900…46a00 (70, 0, 9) Sector 460aff00017841 ┆F xAl. Format of channel-check message: VZCCABC456 UU (2CR) (1LF) 00 RXDB (2CR) (1LF) DE RXDB 0021103 (2CR) (1LF) ZNR UUUUU (2CR) (1LF) CHANNEL CHECK (2CR) (8LF) NN┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00017841 ┆F xANN (12 LTRS) The precedence shall be immediate as indicated. The message shall be expected within a period as set by the supervisor. In case the message is not received in time the supervisor shall be warned via a repor┆
0x46b00…46c00 (70, 0, 11) Sector 460c8b00017841 ┆F xAt. b) The system shall recognize the following abbreviated service message when received on any incoming message channel: e.g. m the automatic answer back device. 3- In the process of conversion from IA No. 2 to IA No. 5, the occurrence of ┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00017841 ┆F xA 1 (LI) (2CR) (1LF) RR RXFB (2CR) (1LF) DE RXFP 012002 (2CR) (1LF) ZNR UUUUU (2CR) (1LF) ZID FAA16┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00017841 ┆F xA4 (2CR) (8LF) NNNN (12 LTRS) A warning shall be forwarded to the supervisor in case the serial number information (F-A-A 164 in example above) does not correspond to the serial number of the previous messa┆
0x46e00…46f00 (70, 0, 14) Sector 460fe000017841 ┆F ` xAge received on that channel. If on channels specified by the supervisor the message does not arrive within a period starting at 23,45 hours and ending at 00,15 hours (GMT) a warning shall be sent to the supervisor. n the third column of the table┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00017841 ┆F xA 1 1 TABLE OF CONTENTS Section 3.4 and 3.4.1 3.4 Characteristics .......................... 3.4.1 Pe┆
0x47000…47100 (71, 0, 0) Sector 4701ee00017841 ┆G n xAom IA No. 5 to IA No. 2, every occurrence of SI and of SO shall be translated to letter shift and figure shift respectively. On channels not specified for this to occur, the SO and SI characters shall be translated into combination all provide the f┆
0x47100…47200 (71, 0, 1) Sector 4702ff00017841 ┆G xA 1 No. 32 in IA No. 2. In addition, the equipment shall determine, from an inspection of the code combination of each IA No. 5 character presented to the converter, whether a case┆
0x47200…47300 (71, 0, 2) Sector 4703ff00017841 ┆G xA shift is required in translating into the IA No. 2, and insert the appropriate case shift code combination into the character stream to ensure selection of the correct case by an IA No. 2 telegraph machine. 6- The process of conversion from IA N┆
0x47300…47400 (71, 0, 3) Sector 4704ff00017841 ┆G xAo. 5 to IA No. 2 shall ensure that all those column/row combinations not included in the second and third columns of the table are translated into IA No. 2 combination No. 32 IA No. 2 combination No. 32 shall be translated into IA No. 5 combination ┆
0x47400…47500 (71, 0, 4) Sector 47051500017841 ┆G xA0/0 (NUL). rder device rm to the security requirements specified in section 3.4.5.1. 3.3.1.2 Channel Protocol a) CAMPS shall interface to NICS TARE as a Medium Speed User Terminal (MSUT). b) Communication channels between CAMPS and NICS T┆
0x47500…47600 (71, 0, 5) Sector 47069f00017841 ┆G xA 1 TABLE 3.3.2.1-3 Equivalents for transmission between ITA No. 2 and ITA No. 5 e of "Quotation Mark", "Apostrophe" and "Upward Arrow". However, these characters take on the si┆
0x47600…47700 (71, 0, 6) Sector 4707ff00017841 ┆G xA 1 3.3.2.2 Functional Servicing No channel protocols shall be employed on the TRC/CAMPS interface CAMPS shall support message transmission and reception of messages in ACP 127 fo┆
0x47700…47800 (71, 0, 7) Sector 4608ff00017841 ┆F xArmat as described in section 3.2.1 and 3.2.2. Any message related to maintaining communication between stations shall be handled by operational procedures performed by the supervisor except for the following cases. - Channel check from TRC - Ch┆
0x47800…47900 (71, 0, 8) Sector 47096300017841 ┆G c xA 1 TABLE 3.3.2.1.-2 shall be warned via a report. ┆
0x47900…47a00 (71, 0, 9) Sector 470aff00017841 ┆G xA 1 c3) The equivalents between IA No. 2 and IA No. 5 codes are given in table 3.3.1.2.3. In examining table 3.3.1.2.3 the following are worth noting: 1- For translation from IA N┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00017841 ┆G xAo. 2 to IA No. 5 the system shall be provided with facilities to enable the supervisor to condition each outgoing channel so that bit 6 in columns 4, 5, 6 and 6 of the IA No. 5 code table is preset to either 0 or 1 to cater for translation to either┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00017841 ┆G xA upper, or lower case characters. 2- In IA No. 2 "who are you", when transmitted to a receiving teleprinter, initiates a reply from the automatic answer back device. 3- In the process of conversion from IA No. 2 to IA No. 5, the occurrence of ┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00017841 ┆G xAcombination No. 29 (letters) shall cause conversion of all subsequent IA No. 2 characters corresponding to the combinations in the first column of the table to the characters corresponding to the column/row combination shown in the second column of┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00017841 ┆G xA the table. This shall continue until the occurrence of IA No. 2 combination No. 30 (figures). Every occurrence of combination No. 29 (letters) shall be translated into the column/row combination 0/15 (SI). 4- Similarly, the detection of the occu┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00017841 ┆G xArrence of combination No. 30 (figures) shall result in conversion of all subsequent characters corresponding to the combinations in the first column to the characters corresponding to the column/row combination shown in the third column of the table┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00017841 ┆G xA. This shall continue until the occurrence of IA No. 2 combination No. 29 (letters). Every occurrence of combination No. 30 (figures) shall be translated into the column/row combination 0/14 (SO). 5- On specified input channels, in translating fr┆
0x48000…48100 (72, 0, 0) Sector 4801ff00017841 ┆H xA. Synchronization and upstart of the cryptoes are handled manually. b) The connection between CAMPS and TRC shall operate at 50 and 75 baud asynchronously. c) The interface shall employ the IA No. 2 alphabet. The interface shall provide the f┆
0x48100…48200 (72, 0, 1) Sector 4802ff00017841 ┆H xAunctional capability to convert IA No. 5 to IA No. 2 and vice versa. The requirements related to this conversion are described below. c1) The structure of the codes of IA No. 2 is presented in table 3.3.2.1-1. The description given in this docu┆
0x48200…48300 (72, 0, 2) Sector 4803ff00017841 ┆H xAment of the formats to be provided does not always take account of the "case shift" characters used with IA No. 2: Whenever appropriate, these characters shall be generated and/or recognized by the system. c2) In examining table 3.3.2.1-2 the foll┆
0x48300…48400 (72, 0, 3) Sector 4804ff00017841 ┆H xAowing points are worth noting: 1- The use of national characters is prohibited for NATO use. 2- Positions 1/1, 1/2, 1/3 and 1/4 have the significance respectively of: - Start reader device - Start recorder device - Stop reader device┆
0x48400…48500 (72, 0, 4) Sector 48052100017841 ┆H ! xA - Stop recorder device rm to the security requirements specified in section 3.4.5.1. 3.3.1.2 Channel Protocol a) CAMPS shall interface to NICS TARE as a Medium Speed User Terminal (MSUT). b) Communication channels between CAMPS and NICS T┆
0x48500…48600 (72, 0, 5) Sector 4806ff00017841 ┆H xA 1 3- The graphics in positions 2/2, 2/7 and 5/14 have respectively the significance of "Quotation Mark", "Apostrophe" and "Upward Arrow". However, these characters take on the si┆
0x48600…48700 (72, 0, 6) Sector 48078d00017841 ┆H xAgnificance of the diacritical signs "Diaeresis", "Acute Accent" and "Circumflex Accent" when they follow the "Backspace character. 2.2. Any message related to maintaining communication between stations shall be handled by operational procedure┆
0x48700…48800 (72, 0, 7) Sector 47087f00017841 ┆G xA 1 TABLE 3.3.2.1-1 International Alphabet No. 2 nce numbers a) NICS TARE shall send channel continuously messages to the CAMPS. Channel continuously messages shall be expe┆
0x48800…48900 (72, 0, 8) Sector 48098300017841 ┆H xActed with a periodicity set by the supervisor. In case this does not happen the supervisor shall be warned via a report. ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00017841 ┆H xA 1 Format of channel-check message is: VZCZCABC456 UU (2CR) (1LF) 00 RXDB (2CR) (1LF) DE RXDB 0021103 (2CR) (1LF) ZNR UUUUU ┆
0x48a00…48b00 (72, 0, 10) Sector 480bff00017841 ┆H xA (2CR) (1LF) CHANNEL CHECK (2CR) (8LF) NNNN (12 LTRS) b) The system shall recognize the following abbreviated service message when received on any incoming message channel: e.g. (LI) ┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00017841 ┆H xA (2CR) (1LF) RR RXFB (2CR) (1LF) DE RXFP 0120002 (2CR) (1LF) ZNR UUUUU (2CR) (1LF) ZID FAA164 (2CR) (8LF) NNNN (12 LTRS) A warni┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00017841 ┆H xAng shall be forwarded to the supervisor in case the serial number information (F-A-A 164 in example above) does not correspond to the serial number of the previous message received on that channel. If on channels specified by the supervisor the a┆
0x48d00…48e00 (72, 0, 13) Sector 480ea700017841 ┆H ' xAbbreviated service message does not arrive within a period starting at 23,45 hours and ending at 00,15 hours (GMT) a warning shall be sent to the supervisor. ion addresses all the external interfaces and related requirements. The interfaces dis┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00017841 ┆H xA 1 3.3.2 TRC/CAMPS Interface This section addresses all requirements related to the TRC/CAMPS interface. 3.3.2.1 Electrical Interface a) CAMPS interfaces to TRC via lowspeed c┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00017841 ┆H xArypto devices, i.e. NATO's BID 610 or Kw 7. The interface to these devices is identical to the electrical interface to the NATO supplied low speed teleprinters, i.e. a current loop interface. The interface support character-by-character transmission┆
0x49000…49100 (73, 0, 0) Sector 4901ff00017841 ┆I xArements related to the NICS TARE/CAMPS interface. 3.3.1.1 Electrical Interface CAMPS shall provide capabilities to interface - a colocated NICS TARE or - a remote NICS TARE a) The electrical interface between a CAMPS and a local NICS TARE ┆
0x49100…49200 (73, 0, 1) Sector 4902ff00017841 ┆I xAsystem shall be in accordance with the CCITT recommendation V24/V28 inclusive the V28 modifications specified in annex 3C, Appendix 2, of the IFB 78 - 31 PD/CPIB. b) The electrical interface between CAMPS and remote NICS TARE systems shall be in a┆
0x49200…49300 (73, 0, 2) Sector 49033800017841 ┆I 8 xAccordance with the CCITT recommendation V24/V28. - RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x49300…49400 (73, 0, 3) Sector 4904ff00017841 ┆I xA 1 c) The connections between CAMPS and NICS TARE shall operate at the following speeds - 2400 bit/sec. (colocated NICS TARE) - 600 bit/sec. (remote NICS TARE) d) All electri┆
0x49400…49500 (73, 0, 4) Sector 4905ff00017841 ┆I xAcal connections shall conform to the security requirements specified in section 3.4.5.1. 3.3.1.2 Channel Protocol a) CAMPS shall interface to NICS TARE as a Medium Speed User Terminal (MSUT). b) Communication channels between CAMPS and NICS T┆
0x49500…49600 (73, 0, 5) Sector 4906ff00017841 ┆I xAARE shall be synchronous full duplex. c) The protocol employed for the CAMPS/NICS TARE interface shall be the TARE EDC protocol for full-duplex synchronous channels as specified in doc. no. 177000-600 Revision F, 29 June 1979. 3.3.1.3 Functiona┆
0x49600…49700 (73, 0, 6) Sector 4907ff00017841 ┆I xAl Servicing CAMPS shall support message transmission and reception of messages in ACP 127 format as described in section 3.2.1 and 3.2.2. Any message related to maintaining communication between stations shall be handled by operational procedure┆
0x49700…49800 (73, 0, 7) Sector 4808ff00017841 ┆H xAs performed by the supervisor except for the following cases. - channel check from NICS TARE - change of channel sequence numbers a) NICS TARE shall send channel continuously messages to the CAMPS. Channel continuously messages shall be expe┆
0x49800…49900 (73, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(73,0, 9), len=0xff, h3=41017841}, f00=»0178A «, f01=»CPS/SYS/001 issue II «, f02=»am] «, f03=»GJ «, f04=»fra 3.3 «, f05=11-09-80 11:59, f06=» «, f07=»27 «, f08=» 384 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=11-09-80 16:01, f15=»0016A «, f16=» 37 «, f17=» «, f18=»27 «, f19=» 572 «, f20=» 384 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca1505000000000000003703ae00df}
0x49900…49a00 (73, 0, 9) Sector 490a2500017841 ┆I % xA I I I H H H H G G G G G F F E E E E D D C C C C B B B A A A A @ @ @ @ ? DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : ┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00017841 ┆I xA 1 1 TABLE OF CONTENTS Section 3.3 3.3 External Interfaces ................... 3.3.1 NICS-TARE/CAMPS Inter┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00017841 ┆I xAface ......... 3.3.1.1 Electrical Interface .......... 3.3.1.2 Channel Protocol .............. 3.3.1.3 Functional Servicing ........... 3.3.2 TRC/CAMPS Interface ............... 3.3.2.1 Electrical Interface .......... 3.3┆
0x49c00…49d00 (73, 0, 12) Sector 490d3100017841 ┆I 1 xA.2.2 Functional Servicing .......... :^=~ B;/IMC'!e=6 *(=~ RN/C}/:]=2#<:b= Rc/! <6 Ch/! <6 M)(:^=~ Bt/I:\=2#<C /:]=2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00017841 ┆I xA 1 1 3.3 EXTERNAL INTERFACES This section addresses all the external interfaces and related requirements. The interfaces dis┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00017841 ┆I xAcussed are - NICS TARE and TRC The system requirements contain all the functional requirements related to the interfaces. All detailed requirements necessary to form a firm baseline for the design activities are included in the interface contr┆
0x49f00…4a000 (73, 0, 15) Sector 4900ff00017841 ┆I xAol documents allocated to each external interface. The ACE CCIS and SCARS II interface specifications will not be included until an agreement on the interfaces have taken place. 3.3.1 NICS TARE/CAMPS Interface This section addresses all requi┆
0x4a000…4a100 (74, 0, 0) Sector 00000000000000 ┆ ┆
[…0x2f…]
