OctetView
0x00000…00100 (0, 0, 0) Sector 01394130313339 ┆ 9A0139A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff0000ffffffff ┆ | x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x17, d01=0x77, d02=0x41, ptr=(69,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x17, d01=0x79, d02=0x41, ptr=(47,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x19, d01=0x95, d02=0x41, ptr=(73,0, 8), d05=0x00}
0x00312…00320 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
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 12 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 01394130313339 ┆ 9A0139A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' V X% % PO P ; A": C f x f V WI O 8 :]H ]KV h 1995A f < {C < { ; 8 ` i I b bJ ] Q 8 9 : V & 1777A1995A ]J]K NIL ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) Sector 0101a400199541 ┆ $ A ITS stores the log information in a THP LOG RECORD and sends a record pointer to TCS, which takes care of the communication with LOG PACKAGE. e) ITS to OAS NO INIT R2 C D FIELD ID R3 C D Value to be added to record length R7 R Pointer to Tran┆
0x01100…01200 (1, 0, 1) Sector 00004000199541 ┆ @ A - Incoming Message for OCR Analysis (ref.ICD 009 sec. e field list for the incoming transport of the running subprocess. If the init switch has been set to TRUE the field list is initialized: - No. of fields is set to NO OF INP FIELDS - FIL┆
0x01200…01300 (1, 0, 2) Sector 00008600177941 ┆ yANOWN PLA)( ) LOCATE PLA REF(PLA REF, REF AIG)(REC POINTER) REC POINTER = ZERO? DELETE PLA RI(REC POINTER)( ) RETURN escription Error-Codes: MISSING PLA UNKNOWN PLA c) Update Address procedure ref. 4.2.1.6.21 for descriptio┆
0x01300…01400 (1, 0, 3) Sector 00000000000000 ┆ ┆
[…0x4…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x35…]
0x04e00…04f00 (4, 0, 14) Sector 040fff00177741 ┆ wA NO OF RI: INTEGER 4.2.2.4.14.5 Module Design The relevant pre-selected RIs (PLA RI.Selected RI) are collected for a search in the RI-table. A routing list containing record-numbers of the PLA RI Field is built-up consecutively. The result of┆
0x04f00…05000 (4, 0, 15) Sector 0208ff00177741 ┆ wA the RI-table search is then compared with the pre-selected RI via the routing-list in order to detect non-valid RIs (plus classification check RI/message). The circuits derived from the RI-records are then used as key for a circuit-table search. ┆
0x05000…05100 (5, 0, 0) WangDocumentBody
[…0x174…]
0x1c500…1c600 (28, 0, 5) Sector 1c06a500177941 ┆ % yA10.1.6) Local PLA table (DBD/001 6.6) PLA table (DBD/001 6.5 FL Analysis data (4.2.1.5.8) TMP Data (4.2.1.5.2) QEL Data (4.2.1.5.3) HEADER. MAINTYPE c) Local Data PLA REF: INTEGER ADS OFFSET: INTEGER PLA COUNT: I┆
0x1c600…1c700 (28, 0, 6) Sector 1c07ff00177941 ┆ yA 1 b) External Data ADMINISTRATION.NUMBER OF XMT ADD (m) "-" .NUMBER OF READD XMT ADD (m) "-" .GROUP XMT OFFSET (m) "-" .GROUP READD XMT OFFSET (m) ADDRESS ┆
0x1c700…1c800 (28, 0, 7) Sector 0108ff00177941 ┆ yAFIELD RECORD (m) PLA RI.DYNAMIC COUNT (m) PLA RI DYNAMIC RECORD (D) READDRESSAL DETECTED SEND FOR CONVERSION QEL HEADER. MAINTYPE HQ MASK (m) c) Local Data None 4.2.1.4.21.5 Module Design Having detected the startsequence XMT (┆
0x1c800…1c900 (28, 0, 8) WangDocumentBody
[…0x12f…]
0x2f800…2f900 (47, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(47,0, 9), len=0xff, h3=41177941}, f00=»1779A «, f01=»CPS/SDS/033 «, f02=»rt «, f03=»KNB «, f04=»fra 4.2.1.4.8 «, f05=02-03-82 09:25, f06=» 14 «, f07=»56 «, f08=» 67804 «, f09=15-06-83 10:14, f10=» «, f11=»00 «, f12=» 10 «, f13=15-06-83 10:16, f14=24-06-83 14:27, f15=»0139A «, f16=» 94 «, f17=» 24 «, f18=»24 «, f19=» 996 «, f20=» 77009 «, f21=» «, f22=» 0 «, f99=530010000110062710110290aaca15050000000000000137033d01df}
0x2f900…2fa00 (47, 0, 9) WangDocumentBody
[…0x156…]
0x45000…45100 (69, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(69,0, 1), len=0xff, h3=41177741}, f00=»1777A «, f01=»CPS/SDS/033 «, f02=»bel/vhn «, f03=»KNB «, f04=»Fra 4.2.2 «, f05=02-03-82 09:21, f06=» 8 «, f07=»15 «, f08=» 49174 «, f09=21-06-83 15:53, f10=» «, f11=»08 «, f12=» 132 «, f13=19-10-84 12:17, f14=25-10-84 10:52, f15=»0139A «, f16=»102 «, f17=» 17 «, f18=»50 «, f19=» 1144 «, f20=» 68202 «, f21=» «, f22=» p «, f99=970010000110062710110280aaca15050000000000000137038601df}
0x45100…45200 (69, 0, 1) WangDocumentBody
[…0x46…]
0x49800…49900 (73, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(73,0, 9), len=0xff, h3=41199541}, f00=»1995A «, f01=»CPS/SDS/033 «, f02=»bko «, f03=»BLP «, f04=»Fra 4.2.5 «, f05=13-04-82 08:44, f06=» 7 «, f07=»41 «, f08=» 34279 «, f09=19-10-84 13:45, f10=» «, f11=»00 «, f12=» 31 «, f13=19-10-84 13:23, f14=25-10-84 10:53, f15=»0139A «, f16=»104 «, f17=» 26 «, f18=»24 «, f19=» 1388 «, f20=» 79259 «, f21=» «, f22=» 0 «, f99=130000000110052710110280aaca1505000000000000014203c001df}
0x49900…49a00 (73, 0, 9) WangDocumentBody
[…0x6…]
0x4a000…4a100 (74, 0, 0) Sector 4a01ff41199541 ┆J A A1995A CPS/SDS/033 bk BLP Fra 4.2.5 13 04 82 08 44 7 41 34279 04 09 84 11 56 02 17 04 09 84 11 59 04 09 84 13 03 0139A 104 25 13 1420 78894 p ' *J B B _┆
0x4a100…4a200 (74, 0, 1) Sector 4a026800199541 ┆J h A J J I I I I H H H G G F F F E D C C C B B A A A A @ @ @ @ @ ? ? ? ? ? > > > > = = = = < < < < ; ; ; ; : : : : : 9 9 9 8 8 8 8 8 7 7 7 7 6 6 6 6 5 5 5 5 4 4 4 4 4 3 3 3 3 3 2 2 2 1 1 1 1 1 0 0 0 TISTIKIKvn: Operat]r: Forfrf┆
0x4a200…4a300 (74, 0, 2) Sector 4a03af00199541 ┆J / A 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00199541 ┆J A 1 4.2.5 INCOMING TRANSPORT SUBPACKAGE 4.2.5.1 Functional Specification The Incoming Transport Subpackage (ITS) supplies the modules for handling of the incoming traffic of message┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00199541 ┆J As. The ITS receives the message lines through the IOC and stores them into the External Message Format (EMF). When a complete message has been received, it is forwarded to the Analysis Process through the Analysis Queue (ANQ or OAQ). The ITS sup┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00199541 ┆J Aports the following types of incoming transport subprocesses: - TRC/POINT TO POINT - NICS TARE - SCARS/CCIS - PTR. - OCR Messages from the first four types of subprocesses are forwarded to the Analysis Process (AAS) contained in THP and┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00199541 ┆J A described in this document. Messages from the OCR are forwarded to the Analysis Process contained in TEP. Each transport subprocess has its own ITS-function which is running independent of the other subprocesses (Ref.section 4.2.3). The funct┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00199541 ┆I Aional components of the ITS are divided into the following main groups: - Incoming Traffic Control - Incoming Message Handling - Error Handling - Message Line Detection The functional components mentioned above are described in the follow┆
0x4a800…4a900 (74, 0, 8) Sector 4a09ff00199541 ┆J A 1 4.2.5.1.2.2 Message Start The detection of a message start initiates creation of a new CIF containing the fields of the External Message Format. Also the error checking and detec┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00199541 ┆J Ation of message format lines are initiated. a) TRC/POINT TO POINT A new message is started when one of the following sequences are detected in the LTUX: VZCZC or ZCZC. If the channel is closed a report is forwarded to the supervisor. ┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00199541 ┆J AIf the channel is open the timer function related to the supervision of the incoming traffic is cancelled. The timer is located in the local timer table and controls the transmission of "Self Addressed Channel Check Message". b) NICS TARE A new┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00199541 ┆J A message is started when the start of message (SOM) block is received from IOC, i.e. the next line received is considered as format line 1. If the channel is closed a report is forwarded to the supervisor. If the channel is open the timer func┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00199541 ┆J Ation related to the supervision of the incoming traffic is cancelled. c) SCARS/CCIS A new message is started when the start of message block (SOM) is received from IOC. The SOM contains the message type and precedence of the message. These para┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00199541 ┆J Ameters are stored in the ACP127 Parameter Field of the External Message Format. When a message start is detected the timer function related to supervision of the incoming traffic is cancelled. If the message type is equal to 'E' (Transaction A┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0f9a00199541 ┆J Acknowledgement) no CIF is created. In this case an operation is transferred to Transport Control (TCS), and the timer function (above) is updated. ITS-function which is running independent of the other subprocesses (Ref.section 4.2.3). The funct┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00199541 ┆J A 1 d) PTR A new message is detected when one of the following sequences are detected in the LTUX: VZCZC or ZCZC e) OCR A new message is started when the Start of Message B┆
0x4b000…4b100 (75, 0, 0) Sector 4b013e00199541 ┆K > Aing sections and depicted in figure 4.2.5-1 to 4.2.5-5. o M *y= "(= q#p! =6 M] : =V V I: =~ B 3: = R 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x4b100…4b200 (75, 0, 1) Sector 4b026700199541 ┆K g A 1 Figure 4.2.5-1 to 4.2.5-4 Mo Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00199541 ┆K A 1 4.2.5.1.1 Incoming Traffic Control The Incoming Traffic Control takes care of the functions which shall be executed when an operation is received from the Transport Control (TCS) ┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00199541 ┆K Awithin the subprocess. The following functions are included: a) Start Up This operation will make the Incoming Transport initiate transfer of message lines from IOC. b) Stop Transport The transfer of message lines from the IOC is immedia┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00199541 ┆K Ately stopped. No message lines are received before a start up operation has been received. c) Close Down Two Close Down functions exist: 1) Init Close Down makes the Incoming Transport finish the message in progress, but no new message t┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00199541 ┆K Aransfer is initiated. 2) Final Close Down works as a stop Transport. 4.2.5.1.2 Incoming Message Handling The Message Handling contains the functions which are related to the basic flow control of messages through the Incoming Transport. 4.┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00199541 ┆K A2.5.1.2.1 Buffer Control This component includes the control logic for handling of buffers assigned for reception of messages from IOC and storage of a message in the External Message Format. The structure of these functions is described in sectio┆
0x4b700…4b800 (75, 0, 7) Sector 4a081100199541 ┆J An 4.2.5.3. ┆
0x4b800…4b900 (75, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(75,0, 9), len=0xff, h3=41199541}, f00=»1995A «, f01=»CPS/SDS/033 «, f02=»bk «, f03=»BLP «, f04=»Fra 4.2.5 «, f05=13-04-82 08:44, f06=» 7 «, f07=»41 «, f08=» 34279 «, f09=27-03-84 12:38, f10=» 13 «, f11=»52 «, f12=» 41318 «, f13=30-03-84 11:10, f14=03-04-84 11:31, f15=»0139A «, f16=»104 «, f17=» 24 «, f18=»28 «, f19=» 1508 «, f20=» 78089 «, f21=» «, f22=» «, f99=020000000110052710110380aa8a3704000000000000014203c101df}
0x4b900…4ba00 (75, 0, 9) Sector 4b0a6800199541 ┆K h A K K K K J J J I I I H H H G G F F F E D C C C B B B B B A A A A A @ @ @ @ ? ? ? ? > > > > = = = = = < < < ; ; ; ; : : : : 9 9 9 9 9 8 8 8 8 7 7 7 7 6 6 6 6 6 5 5 5 5 5 4 4 4 4 3 3 3 3 2 2 2 1 1 1 1 0 0 0 TISTIKIKvn: Operat]r: Forfrf┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0baf00199541 ┆K / A 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00199541 ┆K A 1 4.2.5 INCOMING TRANSPORT SUBPACKAGE 4.2.5.1 Functional Specification The Incoming Transport Subpackage (ITS) supplies the modules for handling of the incoming traffic of message┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00199541 ┆K As. The ITS receives the message lines through the IOC and stores them into the External Message Format (EMF). When a complete message has been received, it is forwarded to the Analysis Process through the Analysis Queue (ANQ or OAQ). The ITS sup┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00199541 ┆K Aports the following types of incoming transport subprocesses: - TRC/POINT TO POINT - NICS TARE - SCARS/CCIS - PTR. - OCR Messages from the first four types of subprocesses are forwarded to the Analysis Process (AAS) contained in THP and┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0fff00199541 ┆K A described in this document. Messages from the OCR are forwarded to the Analysis Process contained in TEP. Each transport subprocess has its own ITS-function which is running independent of the other subprocesses (Ref.section 4.2.3). The funct┆
0x4bf00…4c000 (75, 0, 15) Sector 4b00ff00199541 ┆K Aional components of the ITS are divided into the following main groups: - Incoming Traffic Control - Incoming Message Handling - Error Handling - Message Line Detection The functional components mentioned above are described in the follow┆
0x4c000…4c100 (76, 0, 0) Sector 4c01ff00177941 ┆L yAodule Interface ......... 4.2.1.4.14.3 Module Components ........ 4.2.1.4.14.4 Data Description ......... 4.2.1.4.14.5 Module Design ............ 4.2.1.4.15 FLEF ANALYSIS MODULE ..... 4.2.1.4.┆
0x4c100…4c200 (76, 0, 1) Sector 4c02ff00177941 ┆L yA15.1 Functional Specification . 4.2.1.4.15.2 Module Interface ......... 4.2.1.4.15.3 Module Components ........ 4.2.1.4.15.4 Data Description ......... 4.2.1.4.15.5 Module Design ............ 4.┆
0x4c200…4c300 (76, 0, 2) Sector 4c03ff00177941 ┆L yA2.1.4.16 FL J Analysis Module ....... 4.2.1.4.16.1 Functional Specification . 4.2.1.4.16.2 Module Interface ......... 4.2.1.4.16.3 Module Components ........ 4.2.1.4.16.4 Data Description ......... ┆
0x4c300…4c400 (76, 0, 3) Sector 4c043a00177941 ┆L : yA 4.2.1.4.16.5 Module Design ........... or? Fra hvor? Dokument: Hvilken kommando? Hvilken side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00177941 ┆L yA 1 4.2.1.4.17 FL 2 Analysis Module ....... 4.2.1.4.17.1 Functional Specification . 4.2.1.4.17.┆
0x4c500…4c600 (76, 0, 5) Sector 4c06ff00177941 ┆L yA2 Module Interface ......... 4.2.1.4.17.3 Module Components ........ 4.2.1.4.17.4 Data Description ......... 4.2.1.4.17.5 Module Design ............ 4.2.1.4.18 FL3 Analysis Module ........ 4.2.┆
0x4c600…4c700 (76, 0, 6) Sector 4c07ff00177941 ┆L yA1.4.18.1 Functional Interface ..... 4.2.1.4.18.2 Module Interface ......... 4.2.1.4.18.3 Module Components ........ 4.2.1.4.18.4 Data Description ......... 4.2.1.4.18.5 Module Design ............ ┆
0x4c700…4c800 (76, 0, 7) Sector 3200ff00177941 ┆2 yA 4.2.1.4.19 FL4 Analysis Module ........ 4.2.1.4.19.1 Functional Specification . 4.2.1.4.19.2 Module Interface ......... 4.2.1.4.19.3 Module Components ........ 4.2.1.4.19.4 Data Description ......... ┆
0x4c800…4c900 (76, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(76,0, 9), len=0xff, h3=41177941}, f00=»1779A «, f01=»CPS/SDS/033 «, f02=»rt «, f03=»KNB «, f04=»fra 4.2.1.4.11 «, f05=02-03-82 09:25, f06=» 14 «, f07=»56 «, f08=» 67804 «, f09=31-03-82 14:10, f10=» 2 «, f11=»56 «, f12=» 2775 «, f13=01-04-82 11:23, f14=15-04-82 12:42, f15=»0139A «, f16=»111 «, f17=» 17 «, f18=»52 «, f19=» 1168 «, f20=» 70579 «, f21=» «, f22=» «, f99=020010000110066610110480aaca15050000000000000137037001df}
0x4c900…4ca00 (76, 0, 9) Sector 4c0a6f00177941 ┆L o yA L L L 2 2 1 1 1 1 0 0 0 0 0 / / / / / . . . . . . - - - - - , , , , , + + + + + + * * * * ) ) ) ) ) ( ( ( ( ( ' ' ' ' ' ' ' & & & & & % % % % % $ $ $ $ # # # # " " " " " ! ! ! ! ! ┆
0x4ca00…4cb00 (76, 0, 10) Sector 4c0ba900177941 ┆L ) yA 1 CPS/SDS/033 KNB/820301 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION CAMPS M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4cb00…4cc00 (76, 0, 11) Sector 4c0cff00177941 ┆L yA 1 1 4.2.1.4.11 FL1 Analysis Module .......... ┆
0x4cc00…4cd00 (76, 0, 12) Sector 4c0dff00177941 ┆L yA 4.2.1.4.11.1 Functional Specification . 4.2.1.4.11.2 Module Interface ......... 4.2.1.4.11.3 Module Components ........ 4.2.1.4.11.4 Data Description ......... 4.2.1.4.11.5 Module Design ..........┆
0x4cd00…4ce00 (76, 0, 13) Sector 4c0eff00177941 ┆L yA.. 4.2.1.4.12 FLC Analysis Module .......... 4.2.1.4.12.1 Functional Specification . 4.2.1.4.12.2 Module Interface ........ 4.2.1.4.12.3 Module Components ........ 4.2.1.4.12.4 Data Description┆
0x4ce00…4cf00 (76, 0, 14) Sector 4c0fff00177941 ┆L yA ......... 4.2.1.4.12.5 Module Design ............ 4.2.1.4.13 FLD1 Analysis Module ....... 4.2.1.4.13.1 Functional Specification . 4.2.1.4.13.2 Module Interface ......... 4.2.1.4.13.3 Module Co┆
0x4cf00…4d000 (76, 0, 15) Sector 4c00ff00177941 ┆L yAmponents ........ 4.2.1.4.13.4 Data Description ......... 4.2.1.4.13.5 Module Design ........... 4.2.1.4.14 FLD ANALYSIS MODULE .......... 4.2.1.4.14.1 Functional Specification . 4.2.1.4.14.2 M┆
