top - download
⟦f9141b670⟧ Wang Wps File
Length: 82200 (0x14118)
Types: Wang Wps File
Notes: CPS/SDS/033
Names: »1777A «
Derivation
└─⟦82445de73⟧ Bits:30006087 8" Wang WCS floppy, CR 0139A
└─ ⟦this⟧ »1777A «
WangText
D…09…D…0f……1b……0d……1b… …1a……0a……1a……01……1a……07……19……0e……19……05……18……0b……18……0d……18……0e……18… …17……09……17……0f……17……05……16……08……16……09……16……00……16……02……16…
…15……09……15……0a……15……0d……15……01……15……02……15… …14……08……14……0d……14……01……14……02……14……05……13……0a……13……0f……13… …12……08……12……09……12……0c……12……0e……12……01……12… …12……06……11……86…1
…02…
…02…
…02…
…02…CPS/SDS/033
…02…KNB/831101…02……02…
TRAFFIC
HANDLING
DETAILED
DESIGN
SPECIFICATION…02……02…CAMPS
4.2.2 A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Conversion Subpackage receives messages for conversion
from the Terminal Package and from the Analysis Subpackage.
These messages are input to Conversion in the Internal
Message Format (IMF). After successful routing, messages
in the External Message Format (EMF) are formatted
out from the IMF and queued for transmission.
The transmission format is ACP 127 except for VDU-pages
Comments, and messages for CCIS.
The structure depicted in section 4.2.2.2 figures 4.2.2.2-1
to 4.2.2.2-3 also illustrates the functional capabilities
of the Conversion Subpackage.
The major functional Components of this subpackage
are:
- Init Conversion Functions
- Routing Functions
- Formatting Functions
- Finish Conversion Functions.
4.2.2.1.1 I̲n̲i̲t̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Init Conversion Functions are to prepare the received
information and data for further processing through
the routing and formatting procedures. The automatic
release of complete entered messages is also such function.
See fig. 4.2.2.2-1 for functional components.
4.2.2.1.1.1 Q̲E̲L̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲
The QEL Reception functions are to receive a Queue
Element from the Conversion Queue.
The QEL contains an information field containing at
least a maintype and subtype. This information is validated
in order to reject illegal Queue Elements. The final
function is to prepare the accepted QEL information
for further processing.
4.2.2.1.1.2 V̲i̲e̲w̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲
All legal QEL's input to the Conversion Queue are referring
a view (except SSC-commands). This view represents
a message in the Internal Message Format.
The function of View Reception is to read in the message
and in accordance with the message-type (QEL-MAINTYPE)
and the reason for its being in the Conversion Queue
(QEL ̲SUBTYPE), to perform a validation of the received
data-contents.
4.2.2.1.1.3 R̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲ ̲P̲r̲e̲p̲a̲r̲e̲
If the message received is for readdressal, the old
set of PLA and RI's are rearranged in order to fulfil
the normal routing and formatting functions without
any special exceptions.
4.2.2.1.1.4 P̲L̲A̲,̲ ̲R̲I̲ ̲P̲r̲e̲p̲a̲r̲e̲
Any type of Plaindress Message originated from Camps
(including messages for readdressal) shall have the
PLA-ref's (extracted during validation) formatted into
a PLA-RI-List similar to non Camps originated messages
in order to have equivalent processing further on through
the routing and formatting functions.
4.2.2.1.2 R̲o̲u̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The function of Routing is to select a circuit on which
the message may be transmitted after formatting.
See fig. 4.2.2.2-2 for functional components.
4.2.2.1.2.1 R̲e̲d̲u̲c̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲
The subjects for reduced routing are messages for relay,
messages for rerun and messages for rerouting.
The function is to extract the relevant RI's among
the full set of RI's to be used when formatting FL
2.
The RI's associated to a message for relay is recognized
via flags in the PLA ̲RI ̲List.
The RI's associated to rerun and rerouting is recognized
via a circuit-number extracted from the QEL-information.
The extracted RI's are collected into a new PLA ̲RI
̲List; the reason is that the message might be a subject
for RI-assignment later on; done this way the RI-assignment
will only include the relevant RI's.
4.2.2.1.2.2 S̲c̲a̲r̲s̲/̲C̲C̲I̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲
This function is not based upon RI's but upon the systemcodes
for CCIS and/or SCARS located in front of the Action
and/or Info SCD's (FL E/F) of a Comment or VDU-page.
The function is to determine if the message classification
fits with the circuit classification for SCARS/CCIS,
and if the associated channels are available, if not
the VDU-page or Comment will be rejected to the preparer
(not RI-assignment).
VDU-pages or Comments might go for RI-assignment if
the QEL-subtype indicates rerouting; in this case the
VDU-page or comment had been accepted for transmission
but was rejected due to a channel close. The preparer
is then not known to the conversion process and RI-assignment
is the final way out.
4.2.2.1.2.3 M̲S̲O̲ ̲R̲o̲u̲t̲i̲n̲g̲
The messages returned from a RI-assignment are subjects
for this function.
The assigned RI's are returned in a special list and
shall be transferred to the PLA ̲RI ̲List. Relay instructions
might have been assigned the message in order to route
it; also instructions for Clear or Punch of a message
might be assigned during RI-assignment procedures.
If a X-PLA has not been assigned any value, this is
considered as an indication for deletion of that PLA.
It is accepted that RI's instead of a valid RI has
been assigned "ZEN" if a PLA can be associated to the
RI.
This function will also validate the logical relationship
between RI's for FL2 and assigned Relay-instructions
and remove RI's originally intended for FL2 if these
are contained in a relay-instruction.
No update are performed before a successful routing
can be foreseen; done like this MSO can regret the
previous RI-assignments.
4.2.2.1.2.4 C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲
The complete routing functions are to select circuits
for transmission based upon a list of RI's.
These RI's might have been derived through FL 2 of
a complete entered message, assigned during Service
Message Prepare or assigned via RI-assignment procedures
(MSO). Anyway the message classification shall be compared
with the RI and circuit classification and the availability
of the pre-selected circuits shall be checked before
the message may continue for transmission, taking MSO-instructions
Clear or Punch in account.
4.2.2.1.2.5 S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲
The subjects for selective Routing are Camps originated
messages of Plaindress-type and SCARS/CCIS released
messages of Plaindress-type in E1-format entered to
Conversion first time (second time will be after RI-assignment
or for Rerun etc.).
The function is to select a RI for each PLA.
Up to 4 alternatives for select of an RI may exist
for each PLA.
The following principles for select of a RI will be
used:
a) The first RI with a classification higher than
or equal to the classification of the message will
be selected.
b) If the classification of the associated circuit
is lower than the classification of the RI a logical
error is found in the RI-table, and a warning will
be sent to the supervisor printer.
- the next RI will then be selected.
c) If the circuit referenced via the RI is disconnected
or no channels are available upon that circuit
(closed), the next RI will then be selected.
d) If no more RI's can be selected the message will
be rejected for RI-assignment with the last tested
RI (if any) as a suggestion.
e) If an X-PLA is located the message will be forwarded
for RI-assignment.
f) If a "ZEN" is associated to the PLA, no RI will
be selected.
4.2.2.1.2.6 R̲o̲u̲t̲i̲n̲g̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
This function is used by the previously described Routing
functions if the routing procedure could not be accomplished.
If the message rejected is a Camps originated ASM or
Abbreviated Plaindress service message, the preparer
of this message will himself be responsible for the
RI-assignment (the RI-validation was unsuccessful);
otherwise MSO shall receive the message for RI-assignment.
The function is then to create a RI-assignment List
containing RI's and PLA's plus informative Relay-instructions
(if any) to be presented for the MSO.
On return from RI-assignment, the MSO routing function
will accept the new assigned RI's.
4.2.2.1.3 F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The role of the Init Formatting functions is to point
out the next subject for transmission and create the
basic background via static parameters for the formatting.
Before the formatting for transmission is initiated,
Camps originated messages of Plaindress-type containing
either Local SCD's and/or Local PLA's will be sent
to MDP for local distribution. The formatting of such
messages may involve the address-field (FL 7 and 8)
(if a X-PLA has been deleted or MSO has assigned ZEN
to a PLA).
If the message has been flagged for RI-assignment,
the Init Formatting functions will be used to get the
SEND parameters.
a) S̲e̲n̲d̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The Send Parameters are the QEL Maintype and Subtype
plus additional information associated to a transmission.
The Send Parameters to be used for distribution
and for RI-assignment will also be assigned by
this function.
Also an indication of which fields the Finish Formatting
Function may write new data into will be initiated
by this function.
b) A̲C̲P̲ ̲1̲2̲7̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Because a formatting from the Internal Message
Format to the External Message Format can result
in several transmissions due to sectioning (too
long message), too many RI's (more than 200) and
multiple circuit-select, it is convenient to do
these one time things once for all.
These are:
- Calculate number of sections and set up of
pointers to the associated text-parts.
- Calculate number of circuits.
- Fetch global ACP-parameters for conversion
(separate RI's FL 2 into R and U; year, timezone
and ZGC-insertion),
- Find the 4 local RI's to be used when formatting
FL 3, (one per network associated to the circuit)
if not the message has already been assigned
one.
4.2.2.1.3.2 F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
For each selected circuit at least one message will
be formatted out from the received message (IMF). If
more messages are formatted per circuit the reason
is explained in section 4.2.2.1.3.1 b.
VDU-Pages and Comments for transmission are formatted
into SCARS/CCIS E1 Format; all other messages are formatted
into ACP127 Format (messages for CCIS partly). The
following functions are only relevant for messages
that shall be formatted into ACP127:
- Header Preamble Formatting
- Header Formatting
- Text preamble Formatting
a) H̲e̲a̲d̲e̲r̲ ̲P̲r̲e̲a̲m̲b̲l̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
The functions are to format the mandantory FL 2,
FL 3 and FL 4 of any message. If a message was
entered Camps precedence with a pilot, the lines
FLA, FLB and FLC will be formatted instead and
the static lines FL 1, FL 2, FL 3 and FL 4 will
be regenerated. The precedence of FL 2 will be
adjusted to the Info-precedence if no Action addresses
are associated to that transmission.
b) H̲e̲a̲d̲e̲r̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
All message-types except abbreviated service messages
will need some of the Header Formatting functions.
The functions are formatting of FL 5, FL 6, Fl
7, FL 8, FL 9 and FL 10. According to the message
type one, more or all functions might be used.
If the message is a Readdressal, the static set
of Addresses will be generated using the same functions.
Should the readdressed message be of type abbreviated
plaindress, the readdressal will have 2 subsequent
FL 5's in this example (no PLA/AIG).
The PLA's not represented via a RI of FL 2 will
be preceeded with ZEN (FL 7 and FL 8); otherwise
the RI of FL 2 will be inserted in front of the
PLA.
c) T̲e̲x̲t̲ ̲p̲r̲e̲a̲m̲b̲l̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
Messages originated from this Camps are subjects
for this formatting. The functions are formatting
of FL 12A, FL 12B, FL 12C, FL 12D and FL 12E. A
Service Message shall have formatted FL 12A and
FL 12B.
The full set of functions is used for Plaindress
Messages and Data Messages originated from Camps.
Plaindress and Plaindress Service Messages might
also have been sectioned, the section number is
then inserted as a FL 12C and the following FL
12D and FL 12E appended to each section.
d) S̲c̲a̲r̲s̲-̲C̲C̲I̲S̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
These functions are related to the formatting of
a VDU-page or a Comment bound for Scars or CCIS.
The functions provided are formatting of FLB, FLC,
FLD 1, FLD 2, FLE, FLF and FLJ of a scars/CCIS
Format E1.
4.2.2.1.3.3 F̲i̲n̲i̲s̲h̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
After a formatting to an External Message format the
message is ready for transmission.
First a new view shall be created containing the relevant
parts of the received message; then the new formatted
parts shall be written out in that view.
a) T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
Besides from delivering a message to a circuit-queue
for transmission, this function will also deliver
a message for distribution, for storage or for
RI-assignment. The contents to be contained in
the QEL have already been inserted from the Init
Formatting Function.
The functions are to send the QEL (containing a
message-view) to the predefined destination and
react upon unsuccessful delivery by examining the
error-code; if this indicates a queue-block (initiated
by the supervisor) the message will be returned
into the Conversion Queue for rerouting.
If the message is for RI-assignment second time
(answer request) the send function will be performed
by the Finish Conversion Function.
b) F̲l̲a̲s̲h̲ ̲N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
If a message of precedence flash has been delivered
to a queue where preemption has relevance, a Flash
Notification is generated and sent to some …86…1
…02… …02… …02… …02…
control-queue. That is a Channel Command Queue
or a Punch Command Queue of the Transport Subpackage
(not if NICs TARE) or to the common MSO queue if
the message went for RI-assignment.
4.2.2.1.4 F̲i̲n̲i̲s̲h̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The functions of Finish Conversion is to react upon
a Send Request with a Send Reply.
The Reply might be a message returned for further RI-assignment,
a rejected VDU-page or Comment or a positive acknowledgement.
4.2.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The ACP 127 Conversion Subpackage is implemented in
one process (Conversion Process) who serves one queue
(Conversion Queue).
The Conversion Queue (COQ) consists of 3 subqueues
from which the Conversion Process will reveice its
input:
- 1 = Command Subqueue
- 2 = Response subqueue
- 3 = Traffic Subqueue.
Input to the Conversion Process will be executed in
the order of subqueue organization; that is commands
are executed before messages.
a) C̲o̲m̲m̲a̲n̲d̲ ̲S̲u̲b̲q̲u̲e̲u̲e̲
The Command Subqueue will contain commands from
SSC for Close-down etc.
b) R̲e̲s̲p̲o̲n̲s̲e̲ ̲S̲u̲b̲q̲u̲e̲u̲e̲
The Response Subqueue is used for messages input
to Conversion with a Reply Request; that is the
originator of the message is waiting for an answer
after finished conversion.
c) T̲r̲a̲f̲f̲i̲c̲ ̲S̲u̲b̲q̲u̲e̲u̲e̲
The Traffic Subqueue is used for all other messages
input for conversion.
The structure of the Conversion Process is depicted
in figures 4.2.2.2-1 to 4.2.2.2-3.
These drawings illustrates the break-down of the Conversion
Process into modules.
A detailed description of each module will be given
in section 4.2.2.4.
figure 4.2.2.2-1 + -2 + -3
4.2.2.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The Data Flow and Control Logic of the Conversion Subpackage
is to a great extend equivalent to the outgoing message
flow of Camps.
The following description of this section will concentrate
on:
- message types
- message views
- message fields.
4.2.2.3.1 M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲s̲
The message-type of a message forwarded to conversion
can be recognized via the Maintype of the QEL-Info.
Also the function associated to that message-type can
be extracted from the QEL-Info. (Subtype).
The functions performed by the Conversion Process represented
via the QEL-Subtype are:
- For Conversion
- For Readdressal
- For Rerun
- For Rerouting
- For Relaying
- For RI-assignment.
The tables (fig. 4.2.2.3.1-1 to 4.2.2.3.1-6) of received
messages illustrates the message-types relevant for
that function. These tables also represent the validation
logic performed after receipt of a Queue Element from
the Conversion Queue.
The Flag Values of the QEL-INFO:
- Camps originated,
- Relay Instructions
- Pilot
- Readdressed
supply in combination the detailed information needed
for regeneration of a none Camps originated message
format. The tables previously referred also adds the
validation logic associated to these flag values.
Not illustrated via the tables is that the QEL INFO
also may contain instructions like:
- punch
- clear
- send for SCARS
- send for CCIS
- Circuit number (rerun ? reroute)
See CPS/ICD/009 for these details.
The tables 4.2.2.3.1-7 to 4.2.2.3.1-9 illustrates via
Maintype, Subtype and Flagvalues the message output
from conversion
- For RI-assignment
- For Distribution
- For Transmission (and punch)
Note that the SCARS/CCIS message types after a successful
routing will change maintype.
To complete the discussion of functions and flagvalues
associated to a message-type the following general
description might be helpful:
4.2.2.3.1.1 F̲o̲r̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
Ref. fig. 4.2.2.3.1-1
A message is received for conversion from the Internal
Message Format to an External Message Format (ACP 127
or SCARS/CCIS E1).
The non Camps originated message might as complete
have been input with relay-instructions, pilot and
have been readdressed.
4.2.2.3.1.2 F̲o̲r̲ ̲R̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲
Ref. fig. 4.2.2.3.1-2.
Plaindress and Plaindress Service Messages not already
readdressed are accepted for readdressal.
The present FL 5 to FL 9 shall be formatted into static
message-fields to be appended each normally converted
FL 5 to FL 9.
4.2.2.3.1.3 F̲o̲r̲ ̲R̲e̲r̲u̲n̲
Ref. fig. 4.2.2.3.1-3.
The message-types for Rerun are equivalent to the message-types
retrievable from a Supervisor position for that purpose.
In principle a rerun is applicable to messages previously
transmitted. Such message will be transmitted again
preceeded with a suspected duplicate pilot.
The circuit-number associated to the circuit upon which
the message previously had been transmitted is supplied
via the third QEL ̲INFO and forms the basis for generation
of a new PLA ̲RI ̲FIELD (Reduced Routing).
4.2.2.3.1.4 F̲o̲r̲ ̲R̲e̲r̲o̲u̲t̲i̲n̲g̲
See fig. 4.2.2.3.1-4.
This function is very similar to the Rerun; but the
reason is different.
A message had been successfully forwarded for transmission,
but the transmission could not be fulfilled due to
an error on the line or a command for close-down/stop
execution.
The message will in most cases end at the MSO-position
for RI-assignment. Note that Comments and VDU-pages
via the rerouting function is sent for RI-assignment
(but not is returned from RI-assignment).
4.2.2.3.1.5 F̲o̲r̲ ̲R̲e̲l̲a̲y̲i̲n̲g̲
See Fig. 4.2.2.3.1-5.
The messages for relaying are non Camps originated
messages incoming from TRC/Point-to-point or NICS ̲TARE
channels.
A relay-instruction recognized as Camps responsible
had been detected.
The function for the Conversion Process is as for Rerun
and Rerouting to generate a new PLA ̲RI ̲FIELD but this
time based upon RI's marked for Relay.
4.2.2.3.1.6 F̲r̲o̲m̲ ̲R̲I̲-̲a̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
See fig. 4.2.2.3.1-6
The RI's selected during RI-assignment Procedures at
the MSO-position is delivered in a special RI-assignment-field;
these RI's shall be moved to the PLA ̲RI ̲FIELD logically
correct.
4.2.2.3.1.7 F̲o̲r̲ ̲R̲I̲-̲a̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
See fig. 4.2.2.3.1-7.
Any message sent for conversion or another function
provided by the Conversion Subpackage may be rejected
for RI-assignment at a MSO position. A RI-assignment-field
for display based upon the PLA ̲RI field shall be generated.
4.2.2.3.1.8 F̲o̲r̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
See fig. 4.2.2.3.1-8
Camps originated Plaindress and Plaindress-Data Messages
(not readdressed) received for Conversion are sent
to MDP after the Routing Procedures for local distribution.
The messages might in the time between release and
local distribution have been for RI-assignment.
If the RI-assignment results in deletion of X ̲PLA or
ZEN of PLA's, these modifications are performed in
the address-field before leaving the Conversion Process.
4.2.2.3.1.9 F̲o̲r̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲a̲n̲d̲ ̲P̲u̲n̲c̲h̲
See fig. 4.2.2.3.1-9.
The Internal Message Format received is formatted into
an External Message Format.
VDU-pages and Comments are formatted into SCARS/CCIS
E1; all other message-types are formatted into ACP127.
A message with Special Handling Designator = Crypto
Security or with MSO-instruction for Punch attached
to it will be formatted as if it should be transmitted,
but finally sent for punch instead.
Note that encrypted messages will not be punched; neither
will VDU-pages and/or Comments.
figure 4.2.2.3.1-1 - -9
4.2.2.3.2 M̲e̲s̲s̲a̲g̲e̲ ̲V̲i̲e̲w̲s̲
The principles for processing of a message through
the Conversion Process is illustrated in figure 4.2.2.3.2-1.
In general the received QEL referencing a message is
used as a reference for creation of the first message-view;
the view then created is used as reference for creation
of the second view and so on; a new view is always
created out from its predecessor.
The numbers into fig. 4.2.2.3.2-1 are reference numbers
to the following description of the View Control Logic:
re 1) The received view may first be used for creation
of a view for distribution, for storage, for
RI-assignment or for transmission in mentioned
order.
After distribution or storage the view created
for this purpose is used for Transmission.
If a view has been created for RI-assignment,
no more views can be created.
re 2) The View received or the view created for distribution
is now used as reference for creation of a
view for transmission; if additional transmissions
are necessary each transmission-view will be
used as a reference to the next transmission.
re 3) Having finished the normal transmissions (if
any) some transmissions might be pending for
punch or to be cleared.
The choice is an either or; the same message
can not both be punched and cleared. If both
parameters might have been specified during
RI-assignment procedures the punch-instruction
will be completed and the clear-instruction
ignored.
re 4) If a message shall be punched the same principles
as described for transmission (re 3) are valid.
re 5) If a message shall be cleared this demands
creation of a CIF-version where the access-capabilities
are reduced to NATO UNCLASS.
re 6) Finally the received view will be saved and
dismantled.
figure 4.2.2.3.2-1
4.2.2.3.3 M̲e̲s̲s̲a̲g̲e̲ ̲F̲i̲e̲l̲d̲s̲
Each message view received has a number of message
fields associated to it that according to the message-type
is of interest during conversion.
As an example it is not necessary to read the text-part
of a message except for those that are subjects for
sectioning.
The tables depicted in fig. 4.2.2.3.3-1 to 4.2.2.3.3-9
illustrates the fields used during conversion for groups
of message-types under various functions; as well the
input as the output functions are depicted in each
table.
If no symbols have been assigned to a function, that
function has no relevance for that message type.
The following symbols are used:
- R = read field
- W = write new field
- I = Include from previous view
The asterix (*) plus a number depicted in some of the
tables, has the following meaning:
re 1) Write if X ̲PLA/UNKNOWN ̲PLA has been deleted
or ZEN has been inserted in the address-field.
re 2) If received from RI-assignment, do not write
but include received PLA ̲RI ̲Field.
re 3) Write only first transmission, include PLA
̲RI ̲Field from the previous view if more for
transmission.
re 4) If received with notification indicating automatic
release or For Readdressal, write new Administration
Field.
If done for transmission, write only first administration
field and include the remaining transmissions out
from previous views.
figure 4.2.2.3.3-1 - -9
4.2.2.4 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.2.4.1 C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Routing and Formatting of outgoing messages from the
Internal Message Format into an External message Format
ref. functional description 4.2.2.1.
4.2.2.4.1.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Ref. Interface description 4.2.1.7.
4.2.2.4.1.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Ref. fig. 4.2.2.4-1 for structure Conversion Module.
a) I̲n̲i̲t̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.2
b) R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.7
c) F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.23
d) F̲i̲n̲i̲s̲h̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.24
4.2.2.4.1.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Ref. Data Description 4.2.2.5
4.2.2.4.1.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
The Conversion Module is the main-module of the
ACP 127-Conversion Subpackage. In sequential order
the modules:
- Init Conversion
- Routing
- Formatting
- Finish Conversion
are called.
During this processing the wait-queue might be updated
from the main-queue to the command-subqueue.
The wait-queue indicates which queue/subqueue the next
QEL shall be received from (or waited for, if the queue/subqueue
is empty).
During normal processing the wait-queue will indicate
the main-queue.
If an abnormal situation occurs
- processing error
- data error
- SSC-command
the next QEL will be taken from the command-subqueue
(start-up).
figure 4.2.2.4-1
CONVERSION
PRE ̲INITIALIZATION
WAIT ̲QUEUE = MAIN
LOOP FOREVER :
INIT ̲CONVERSION
WAIT ̲QUEUE = COMMAND ?
ROUTING
WAIT ̲QUEUE = COMMAND ?
FORMATTING
FINISH ̲CONVERSION
END FOREVER LOOP
EXIT
4.2.2.4.2 I̲n̲i̲t̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The functions of the Init Conversion Module are:
- Reception of the next QEL from the Conversion Queue.
- Read of message-view associated to the QEL
- Automatic release of Camps originated Service Messages,
messages for readdressal and complete entered outgoing
messages from a normal PTR.
- Preparation of a message sent for readdressal
- Preparation of routing-list for Camps prepared
messages of Plaindress-type.
4.2.2.4.2.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) INIT ̲CONVERSION
b) INIT ̲CONVERSION (R6)
4.2.2.4.2.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Ref. fig. 4.2.2.4-2 for structure Init Conversion Module.
a) Q̲E̲L̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.3
b) V̲i̲e̲w̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
Ref 4.2.2.4.4
c) A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
The relevant data elements of the Administration
Field will be assigned the next SSN, DTG, Filing-time
and Time-Stamp for later use during the Formatting
Procedures.
Also the flag indicating automatic release will
be cleared ensuring that this procedure will not
be repeated on the same message.
d) R̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.5
c) P̲L̲A̲ ̲R̲I̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲M̲o̲d̲u̲l̲e̲
Ref. 4.2.2.4.6
4.2.2.4.2.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
Administration-Field (DBD/001 10.1.1)
QEL-Data ( 4.2.2.5.3)
View-Data ( 4.2.2.5.4)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
WAIT ̲QUEUE
RECEIVE ̲QEL ̲REF
RECEIVE ̲QEL ̲ATTRIBUTES
RECEIVE ̲QUEUE ̲REF
RECEIVE ̲VIEW ̲ATTRIBUTES
ADMINISTRATION.RELEASE ̲DTG (m)
ADMINISTRATION.FILE ̲TIME (m)
ADMINISTRATION.TIME ̲STAMP (m)
ADMINISTRATION.SSN (m)
FOR ̲RELEASE (m)
CONVERSION ̲ERROR (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
None.
4.2.2.4.2.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
The Init Conversion Module will start its processing
by activating the QEL-Reception Module from where it
will return with a new QEL from the Conversion Queue.
If this QEL is referencing a view, the view-reception
module is activated; on return the parameter "STOPPED"
might indicate that the view had been stopped by a
Supervisor Deletion; this results in a dismantle of
the QEL and a new start of the Init Conversion Module.
Having completed the View reception, the automatic
release procedure is performed if the Qel-info indicated
automatic release; this procedure assigns Release-DTG,
File-time. Time-Stamp and the next SSN to the administration-field.
A message received with subtype "For Readdressal" is
sent for Readdressal Prepare and a Camps originated
message of plaindress-type for PLA ̲RI (routing List)
preparation before the Init conversion procedures are
completed.
figure 4.2.2.4-2
I̲N̲I̲T̲ ̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲
STOPPED = FALSE
LOOP STOPPED:
QEL ̲RECEPTION
WAIT ̲QUEUE = COMMAND ?
VIEW ̲RECEPTION ( ) (CC)
CC = STOPPED ? STOPPED = TRUE
DISMANTLE ̲VIEW (RECEIVE ̲QEL ̲REF)(CC):ERROR
̲OK
ERROR? PROCESSING ̲ERROR(CC,DISMANTLE
̲STOPPED ̲
VIEW, NO ̲ACCEPT)( )
WAIT ̲QUEUE = COMMAND ?
FOR ̲RELEASE ? AUTOMATIC ̲RELEASE
WAIT ̲QUEUE = COMMAND ?
FOR ̲READDRESSAL ? READDRESSAL ̲PREPARE
CAMPS ORIGINATED
AND PLA ̲RI ̲PREPARE
PLAINDRESS ̲TYPE ?
EXIT LOOP
END STOPPED LOOP
RETURN
4.2.2.4.3 Q̲E̲L̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.3.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
- Input of a new Queue Element from the Conversion
Queue
- Detection of a QEL containing a command from SSC
for Close-Down
- Detection of non-relevant QEL forwarded to the
Conversion Process by mistake (Programming error)
- Validation of QEL ̲Information in relation to message-type
and function.
- Setup of guide-booleans for the following Input
Routing and Formatting processing.
4.2.2.4.3.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) QEL ̲RECEPTION
b) QEL ̲RECEPTION (R6)
4.2.2.4.3.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Ref. fig. 4.2.2.4-3 for structure QEL Reception Module.
a) P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.1.2 for description
b) D̲a̲t̲a̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.1.1 for description
c) V̲a̲l̲i̲d̲a̲t̲e̲ ̲Q̲E̲L̲-̲I̲n̲f̲o̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
- Validation of QEL.Header containing maintype
(=message-type), subtype (=function) and flags
associated to the message types.
- Validation of traffic-flags contained in the
QEL ̲HEADER.INF and supplementary data contained
in the QEL ̲INFO.
- Rejection of not recognized QEL and illegal
combinations of info-types.
Local Procedures:
- QEL from RI ̲Assignment
- QEL for Readdressal
- QEL for Rerouting
- QEL for Rerun
- QEL for Relaying
- QEL for Conversion
d) I̲n̲i̲t̲ ̲S̲u̲b̲j̲e̲c̲t̲s̲
Initialization of the following types of conversion-booleans:
- Send booleans
- Read booleans
- Function booleans
- Subject booleans
- Message Type booleans
e) C̲a̲m̲p̲s̲ ̲S̲u̲b̲j̲e̲c̲t̲s̲
Assignment of values to the pre-initialized booleans
in accordance with the contents of CAMPS originated
QEL/Message.
f) N̲o̲n̲ ̲C̲a̲m̲p̲s̲ ̲S̲u̲b̲j̲e̲c̲t̲s̲
Assignment of values to the pre-initialized booleans
in accordance with the contents of a Non Camps
QEL/Message.
4.2.2.4.3.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
QEL ̲DATA (4.2.2.5.3)
Routing-Data (4.2.2.5.5)
Formatting-Data (4.2.2.5.6)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
RECEIVE ̲SUBQUEUE (m)
WAIT ̲QUEUE (m)
RECEIVE ̲QEL ̲REF (m)
RECEIVE ̲QEL ̲ATTRIBUTES (m)
RECEIVE ̲QUEUE ̲REF (m)
SEND ̲FOR ̲STORAGE (m)
SEND ̲FOR ̲DISTRIBUTION (m)
SEND ̲FOR ̲CCIS (m)
SEND ̲FOR ̲SCARS (m)
SECTION ̲SUBJECT (m)
LOCAL ̲PLA ̲SUBJECT (m)
DATA ̲MSG ̲TYPE (m)
PLAINDRESS ̲TYPE (m)
ABBREVIATED ̲TYPE (m)
SERVICE ̲TYPE (m)
ENCRYPTED ̲TYPE (m)
SCARS ̲CCIS ̲TYPE (m)
CAMPS ̲ORIGINATED (m)
SUBDUP ̲PILOT (m)
READDRESSAL (m)
FOR ̲RELEASE (m)
SSC ̲COMMAND ̲OBJECT (m)
RELAY ̲INSTRUCTION (m)
CLEAR ̲INSTRUCTION (m)
PUNCH ̲INSTRUCTION (m)
READ ̲TEXT ̲PREAMBLE (m)
READ ̲ADMINISTRATION (m)
READ ̲ADDRESS (m)
READ ̲PLA ̲RI (m)
READ ̲PLA ̲LIST (m)
READ ̲RI ̲ASSIGNMENT (m)
READ ̲TEXT (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
VALID ̲QEL: BOOLEAN
4.2.2.4.3.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
The QEL ̲Reception Module is controlled by the Init
Conversion Module.
It will start its processing with the CSF-call "RECEIVE
̲FIRST ̲QEL" with a wait-indication; the queue (subqueue)
to be waited for is either the Mainqueue or the Command-subqueue.
The Command-Subqueue is selected for wait in case the
previous QEL contained a SSC-command or some error
did occur during processing of this.
The Conversion Program will go in a waiting point here
if the Conversion Queue is empty.
Having received a QEL, the QEL-Information related
to it is validated and formatted into a set-up of common
conversion variables.
The general flow through the remaining Input procedures
(which fields to be read), the routing procedure and
the formatting procedure is decided by this module.
In order to change the conversion Logic, this module
shall be examined first.
figure 4.2.2.4-3
Q̲E̲L̲ ̲R̲E̲C̲E̲P̲T̲I̲O̲N̲
WAIT = TRUE
RECEIVE ̲QUEUE ̲REF. MAIN ̲QUEUE = COQ
RECEIVE ̲QUEUE ̲REF. SUB ̲QUEUE = WAIT ̲QUEUE
RECEIVE ̲FIRST ̲QEL (WAIT,RECEIVE ̲QUEUE ̲REF,
RECEIVE ̲QEL ̲ATTRIBUTES)
(RECEIVE ̲QEL ̲REF,
RECEIVE ̲SUBQUEUE, CC) :ERROR ̲OK
ERROR ? PROCESSING ̲ERROR ̲(CC,RECEIVE ̲FIRST
̲QEL,
NO ̲ACCEPT)
( )
RECEIVE ̲SUBQUEUE = COMMAND ? SSC ̲COMMAND( )(COMMAND
̲TYPE)
VALIDATE QEL ̲INFO ( ) (CC)
CC = NOT ̲OK ? DATA ̲ERROR (QEL ̲ERROR) ( )
RETURN
SSC ̲COMMAND ( ) (COMMAND ̲TYPE)
EQUIVALENCE QEL ̲ATTRIBUTES = RECEIVE ̲QEL ̲ATTRIBUTES
MAINTYPE NE SSC ̲COMMAND ? COMMAND ̲TYPE = ILLEGAL ̲COMMAND
SUBTYPE NE CLOSE ̲DOWN ? COMMAND ̲TYPE = ILLEGAL ̲COMMAND
COMMAND ̲TYPE = CLOSE ̲DOWN
WAIT ̲QUEUE = COMMAND
RETURN
V̲A̲L̲I̲D̲A̲T̲E̲ ̲Q̲E̲L̲ ̲I̲N̲F̲O̲ ̲(̲ ̲)̲(̲C̲C̲)̲
CC = OK
USING RECEIVE ̲QEL ̲HEADER
CASE SUBTYPE OF:
FOR ̲CONVERSION? QEL ̲FOR ̲CONVERSION( )(CC)
FOR ̲RELAYING? QEL ̲FOR ̲RELAYING( )(CC)
FOR ̲RERUN? QEL ̲FOR ̲RERUN( )(CC)
FOR ̲REROUTING? QEL ̲FOR ̲REROUTING( )(CC)
FOR ̲READDRESSAL? QEL ̲FOR ̲READDRESSAL( )(CC)
FROM ̲RI ̲ASSIGNMENT? QEL ̲FROM ̲RI ̲ASSIGNMENT( )(CC))
CC = NOT ̲OK
END CASE SUBTYPE
CC = NOT ̲OK?
INIT ̲SUBJECTS
CASE ORIGINATOR OF:
NON ̲CAMPS? NON ̲CAMPS ̲SUBJECTS
CAMPS? CAMPS ̲SUBJECTS
END ORIGINATOR CASE
RETURN
Q̲E̲L̲ ̲F̲O̲R̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲(̲ ̲)̲(̲C̲C̲)̲
CC = OK
CASE ORIGINATOR OF:
NON ̲CAMPS? MAINTYPE GT ABB ̲SERVICE? CC = NOT ̲OK
MAINTYPE NE ABB ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
CAMPS? MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA,
PLAINDRESS ̲SERVICE,
ABB ̲PLAINDRESS ̲SERVICE,CC
= NOT ̲OK
ABB ̲SERVICE,
SC ̲VDU ̲PAGE OR
SC ̲COMMENT?
FLAG NE ZERO? CC = NOT ̲OK
END ORIGINATOR CASE
RETURN
Q̲E̲L̲ ̲F̲O̲R̲ ̲R̲E̲L̲A̲Y̲I̲N̲G̲ ̲(̲ ̲)̲ ̲(̲C̲C̲)̲
CC = OK
MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA,
PLAINDRESS ̲ENCRYPTED,
PLAINDRESS ̲SERVICE, CC = NOT ̲OK
ABB ̲PLAINDRESS,
ABB ̲PLAINDRESS ̲DATA,
CODRESS
ABB ̲PLAINDRESS ̲SERVICE
OR
ABB ̲SERVICE?
FLAG = CAMPS? CC = NOT ̲OK
MAINTYPE NE ABB ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
RETURN
Q̲E̲L̲ ̲F̲O̲R̲ ̲R̲E̲R̲U̲N̲ ̲(̲ ̲)̲ ̲(̲C̲C̲)̲
CC = OK
CASE ORIGINATOR OF:
NON ̲CAMPS? MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA,
PLAINDRESS ̲SERVICE,
ABB ̲PLAINDRESS, CC = NOT
̲OK
ABB ̲PLAINDRESS ̲DATA,
ABB ̲PLAINDRESS ̲SERVICE
OR ABB ̲SERVICE?
MAINTYPE NE ABB ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
CAMPS? MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA,
PLAINDRESS ̲SERVICE CC = NOT ̲OK
ABB ̲PLAINDRESS ̲SERVICE
OR ABB ̲SERVICE?
FLAG = PILOT? CC = NOT ̲OK
MAINTYPE = PLAINDRESS OR
PLAINDRESS ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
END ORIGINATOR CASE
INF GT CIRCUIT ̲MAX OR LT CIRCUIT ̲MIN? CC = NOT
̲OK
RETURN
Q̲E̲L̲ ̲F̲O̲R̲ ̲R̲E̲R̲O̲U̲T̲I̲N̲G̲ ( )(CC)
CC = OK
CASE ORIGINATOR OF:
NON ̲CAMPS? MAINTYPE NE PLAINDRESS
PLAINDRESS ̲DATA,
PLAINDRESS ̲SERVICE,
PLAINDRESS ̲ENCRYPTED, CC =
NOT ̲OK
ABB ̲PLAINDRESS,
ABB ̲PLAINDRESS ̲DATA,
CODRESS,
ABB ̲PLAINDRESS ̲SERVICE
OR ABB ̲SERVICE?
MAINTYPE NE ABB ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
CAMPS? MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA,
PLAINDRESS ̲SERVICE,
ABB ̲PLAINDRESS ̲SERVICE, CC =
NOT ̲OK
ABB ̲SERVICE,
SC ̲VDU ̲PAGE OR
SC ̲COMMENT?
FLAG = PILOT? CC = NOT ̲OK
MAINTYPE = PLAINDRESS OR
PLAINDRESS ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
END ORIGINATOR CASE
INF GT CIRCUIT ̲MAX OR LT CIRCUIT ̲MIN? CC = NOT ̲OK
RETURN
Q̲E̲L̲ ̲F̲O̲R̲ ̲R̲E̲A̲D̲D̲R̲E̲S̲S̲A̲L̲ ̲(̲ ̲)̲(̲C̲C̲)̲
CC = OK
MAINTYPE NE PLAINDRESS
OR PLAINDRESS ̲SERVICE? CC = NOT ̲OK
FLAG = READDRESSED? CC = NOT ̲OK
FLAG = CAMPS? FLAG = PILOT? CC = NOT ̲OK
RETURN
Q̲E̲L̲ ̲F̲R̲O̲M̲ ̲R̲I̲ ̲A̲S̲S̲I̲G̲N̲M̲E̲N̲T̲ ̲(̲ ̲)̲(̲C̲C̲)̲
CC = OK
CASE ORIGINATOR OF:
NON ̲CAMPS? MAINTYPE GT ABB ̲SERVICE? CC = NOT ̲OK
MAINTYPE NE ABB ̲SERVICE?
FLAG = READDRESSED? CC = NOT ̲OK
CAMPS? MAINTYPE NE PLAINDRESS,
PLAINDRESS ̲DATA
PLAINDRESS ̲SERVICE CC =
NOT ̲OK
ABB ̲PLAINDRESS ̲SERVICE
OR ABB ̲SERVICE?
FLAG = PILOT? CC = NOT ̲OK
FLAG NE READDRESSED?
MAINTYPE = PLAINDRESS
OR PLAINDRESS ̲SERVICE
CC = NOT ̲OK
END ORIGINATOR CASE
RETURN
I̲N̲I̲T̲ ̲S̲U̲B̲J̲E̲C̲T̲S̲
SEND ̲FOR = FALSE
READ ̲FOR = FALSE
WRITE ̲TYPE = FALSE
WRITE ̲INSTRUCTION = FALSE
WRITE SUBJECT = FALSE
CASE MAINTYPE OF:
PLAINDRESS: PLAINDRESS ̲TYPE = TRUE
PLAINDRESS ̲DATA: PLAINDRESS ̲TYPE = TRUE
DATA ̲TYPE = TRUE
PLAINDRESS ̲ENCRYPTED: PLAINDRESS ̲TYPE = TRUE
ENCRYPTED ̲TYPE = TRUE
PLAINDRESS ̲SERVICE: PLAINDRESS ̲TYPE = TRUE
SERVICE ̲TYPE = TRUE
SC ̲PLAINDRESS: PLAINDRESS ̲TYPE = TRUE
SC ̲TYPE = TRUE
SC ̲PLAINDRESS ̲DATA: PLAINDRESS ̲TYPE = TRUE
DATA ̲TYPE = TRUE
SC ̲TYPE = TRUE
SC ̲PLAINDRESS ̲ENCRYPTED: PLAINDRESS ̲TYPE = TRUE
ENCRYPTED ̲TYPE = TRUE
SC ̲TYPE = TRUE
SC ̲PLAINDRESS ̲SERVICE: PLAINDRESS ̲TYPE = TRUE
SERVICE ̲TYPE = TRUE
SC ̲TYPE = TRUE
continues
continued INIT ̲SUBJECTS
ABB ̲PLAINDRESS: ABBREVIATED ̲TYPE = TRUE
ABB ̲PLAINDRESS ̲DATA: ABBREVIATED ̲TYPE = TRUE
DATA ̲TYPE = TRUE
CODRESS: ABBREVIATED ̲TYPE = TRUE
ENCRYPTED ̲TYPE = TRUE
ABB ̲PLAINDRESS ̲SERVICE: ABBREVIATED ̲TYPE = TRUE
SERVICE ̲TYPE = TRUE
ABB ̲SERVICE: ASM ̲TYPE = TRUE
END MAINTYPE CASE
RETURN
N̲O̲N̲ ̲C̲A̲M̲P̲S̲ ̲S̲U̲B̲J̲E̲C̲T̲S̲
SEND ̲FOR ̲TRANSMISSION = TRUE
CAMPS ̲ORIGINATED = FALSE
CASE FLAG OF:
RELAY: RELAY ̲INSTRUCTIONS = TRUE
PILOT: PILOT ̲SUBJECT = TRUE
READDRESSED: READDRESSAL ̲SUBJECT = TRUE
END FLAG CASE
CASE MESSAGE ̲TYPE OF:
PLAINDRESS ̲TYPE: READ ̲ADMINISTRATION
READ ̲ADDRESS
READ ̲PLA ̲RI
ABBREIVATED ̲TYPE: READ ̲ADMINISTRATION
READ ̲PLA ̲RI
ASM ̲TYPE: READ ̲ADMINISTRATION
READ ̲PLA ̲RI
READ ̲TEXT
END MESSAGE ̲TYPE CASE
TFC ̲MASK = AUTOMATIC ̲RELEASE? FOR ̲RELEASE = TRUE
SEND ̲FOR ̲STORAGE = TRUE
CASE SUBTYPE OF:
FOR ̲READDRESSAL: READ ̲PLA ̲LIST = TRUE
FROM ̲RI ̲ASSIGNMENT: READ ̲RI ̲ASSIGNMENT = TRUE
TFC ̲MASK = PUNCH? PUNCH ̲INSTRUCTION
= TRUE
END SUBTYPE CASE
RETURN
C̲A̲M̲P̲S̲ ̲S̲U̲B̲J̲E̲C̲T̲S̲
SEND ̲FOR ̲TRANSMISSION = TRUE
CAMPS ̲ORIGINATED = TRUE
FLAG = RELAY? RELAY ̲INSTRUCTIONS = TRUE
CASE MAINTYPE OF:
PLAINDRESS: READ ̲ADMINISTRATION = TRUE
READ ̲ADDRESS = TRUE
READ ̲TEXT ̲PREAMBLE = TRUE
READ ̲PLA ̲LIST = TRUE
READ ̲TEXT = TRUE
LOCAL ̲PLA ̲SUBJECT = TRUE
SECTION ̲SUBJECT = TRUE
PLAINDRESS ̲DATA: READ ̲ADMINISTRATION = TRUE
READ ̲ADDRESS = TRUE
READ ̲TEXT ̲PREAMBLE = TRUE
READ ̲PLA ̲LIST = TRUE
LOCAL ̲PLA ̲SUBJECT = TRUE
PLAINDRESS ̲SERVICE: READ ̲ADMINISTRATION = TRUE
READ ̲ADDRESS = TRUE
READ ̲PLA ̲LIST = TRUE
READ ̲TEXT = TRUE
SECTION ̲SUBJECT = TRUE
ABB ̲PLAINDRESS ̲SERVICE: READ ̲ADMINISTRATION = TRUE
READ ̲PLA ̲RI = TRUE
ABB ̲SERVICE: READ ̲ADMINISTRATION = TRUE
READ ̲PLA ̲RI = TRUE
READ ̲TEXT = TRUE
SC ̲VDU ̲PAGE READ ̲ADMINISTRATION = TRUE
or : READ ̲TEXT = TRUE
SC ̲COMMENT TFC ̲MASK:
CCIS? FOR ̲CCIS = TRUE
SCARS? FOR ̲SCARS = TRUE
END MAINTYPE CASE
continues
continued CAMPS ̲SUBJECTS
CASE SUBTYPE OF:
FOR ̲CONVERSION: LOCAL ̲PLA ̲SUBJECT = FALSE?
SEND ̲FOR ̲DISTRIBUTION = TRUE
TFC ̲MASK = DISTRIBUTION
FOR ̲READDRESSAL: LOCAL ̲PLA ̲SUBJECT = FALSE
CLEAR TFC ̲MASK.DISTRIBUTION
READ ̲PLA ̲RI = TRUE
FROM ̲RI ̲ASSIGNMENT: READ ̲PLA ̲LIST = FALSE
READ ̲PLA ̲RI = TRUE
READ ̲RI ̲ASSIGNMENT = TRUE
TFC ̲MASK NE DISTRIBUTION?
LOCAL ̲PLA ̲SUBJECT
= FALSE
SEND ̲FOR ̲DISTRIBUTION = TRUE
TFC ̲MASK.PUNCH?
PUNCH ̲INSTRUCTION = TRUE
TFC ̲MASK.CLEAR?
CLEAR ̲INSTRUCTION = TRUE
OTHERWISE: READ ̲PLA ̲LIST = FALSE
READ ̲PLA ̲RI = TRUE
END SUBTYPE CASE
TFC ̲MASK = AUTO ̲RELEASE? FOR ̲RELEASE = TRUE
SEND ̲FOR ̲STORAGE = TRUE
RETURN
4.2.2.4.4 V̲i̲e̲w̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.4.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
- Input of message into the conversion-buffer
- Assignment of record-type-structure in accordance
with the field-list associated to the message-view.
- Rejection of messages with inconsistent contents.
4.2.2.4.4.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
I̲n̲p̲u̲t̲:̲
O̲u̲t̲p̲u̲t̲:̲ R5 = CC ; OK or stopped
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) VIEW ̲RECEPTION ( ) (CC)
b) VIEW ̲RECEPTION (R5, R6)
4.2.2.4.4.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
See fig. 4.2.2.4-4 for structure View Reception Module.
a) P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.1.2
The completion code = stopped is accepted as a
legal error-code after a OPEN ̲VIEW call to CSF
b) P̲r̲e̲p̲a̲r̲e̲ ̲F̲i̲e̲l̲d̲-̲L̲i̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Set-up of Field-groups, Field-offsets and length
of records to be read into the Conversion-buffer.
This set-up is in accordance with message-type,
function and originator-information.
Local procedure:
- prepare field.
c) D̲a̲t̲a̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.1.1 for description
4.2.2.4.4.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
View Data description (4.2.2.5.4)
Conversion-Buffer (4.2.2.5.1)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
FIELD ̲LIST (m)
RECEIVE ̲QEL ̲ATTRIBUTES
RECEIVE ̲QEL ̲REF (=VIEW ̲REFERENCE)
VIEW ̲ATTRIBUTES (m)
ADMINISTRATION ̲POINTER (m)
ADDRESS ̲POINTER (m)
TEXT ̲PREAMBLE ̲POINTER (m)
PLA ̲RI ̲POINTER (m)
RI ̲ASSIGNMENT ̲POINTER (m)
PLA ̲LIST ̲POINTER (m)
TEXT ̲POINTER (m)
START ̲CONVERSION ̲POINTER(m)
END ̲CONVERSION ̲POINTER (m)
READ ̲BOOLEANS
WRITE ̲BOOLEANS (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
None
4.2.2.4.4.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
The View Reception Module is controlled by the Init
Conversion Module from where it is called if the received
QEL was referencing a message-view. The view will be
opened via the CSF-call "OPEN ̲VIEW". If this did not
succeed the completion-code is analyzed by the Error
Processing Procedure, who will accept the error = STOPPED;
so will the View Reception Module with a report to
the Init Conversion Module.
Next the view-attributes are requested from CSF; these
are among other elements containing information about
the Field-Groups and the size of these referenced by
the View.
In accordance with this information and the QEL-Header
information a Field-List is generated for use in the
CSF call "READ ̲VIEW"; the data are then read into the
Conversion Buffer which with help of the Field-List
then is equivalenced to the type-declarations relevant
for the associated Field-Groups. Finally the View will
be closed and pointers set-up to start of the Field-Groups.
If a field pointed out via a read-boolean is empty
the message will be rejected via the Data Error Procedure.
figure 4.2.2.4-4
V̲I̲E̲W̲ ̲R̲E̲C̲E̲P̲T̲I̲O̲N̲ ( ) (CC)
EQUIVALENCE VIEW ̲REFERENCE = RECEIVE ̲QEL ̲REF
OPEN ̲VIEW (VIEW ̲REFERENCE) (CC): ERROR ̲OK
ERROR ? PROCESSING ̲ERROR (CC,OPEN ̲VIEW, STOPPED) (
)
STOPPED = TRUE
GET ̲VIEW ̲ATTRIBUTES (VIEW ̲ATTRIBUTES,VIEW ̲REFERENCE)
(CC) : ERROR ̲OK
ERROR ? PROCESSING ̲ERROR (CC,GET ̲VIEW ̲ATTRIBUTES,
NO ̲ACCEPT) ( )
PREPARE FIELD ̲LIST ( )(BUFFER SIZE, CC)
CC = NOT ̲OK?
DATA ̲ERROR(VIEW ̲ERROR)( )
STOPPED = TRUE
READ ̲VIEW (BUFFERSIZE, RECEIVE ̲FIELD ̲LIST
VIEW ̲REFERENCE, CONVERSION ̲BUFFER)
RECEIVE ̲FIELD ̲LIST, CC): ERROR ̲OK
ERROR ? PROCESSING ̲ERROR (CC, READ ̲VIEW, NO ̲ACCEPT)()
ASSIGN RECORD ̲STRUCTURE
CLOSE ̲VIEW (VIEW ̲REFERENCE)
(CC) : ERROR ̲OK
ERROR ? PROCESSING ̲ERROR (CC, CLOSE ̲VIEW, NO ̲ACCEPT)(
)
RETURN
P̲R̲E̲P̲A̲R̲E̲ ̲F̲I̲E̲L̲D̲ ̲L̲I̲S̲T̲ ( )(CC)
CC = OK
USING VIEW ̲ATTRIBUTES.FIELD ̲INFORMATION
FIELD ̲NO = ZERO
START ̲BUFFER ̲POINTER, FIELD ̲POINTER = CONVERSION ̲BUFFER
READ ̲TEXT ̲PREAMBLE? TEXT ̲PREAMBLE ̲POINTER = FIELD ̲POINTER
PREPARE ̲FIELD(TEXT ̲PREAMBLE)(CC)
CC = NOT ̲OK?
READ ̲ADDRESS? ADDRESS ̲POINTER = FIELD ̲POINTER
PREPARE ̲FIELD(ADDRESS)(CC)
CC = NOT ̲OK?
READ ̲ADMINISTRATION? ADMINISTRATION ̲POINTER = FIELD
̲POINTER
PREPARE ̲FIELD(ADMINISTRATION)(CC)
CC = NOT ̲OK
READ ̲PLA ̲RI? PLA ̲RI ̲POINTER = FIELD ̲POINTER
PREPARE ̲FIELD(PLA ̲RI)(CC)
CC = NOT ̲OK?
READ ̲RI ̲ASSIGNMENT RI ̲ASSIGNMENT ̲POINTER = FIELD
̲POINTER
PREPARE ̲FIELD(RI ̲ASSIGNMENT)(CC)
CC = NOT ̲OK?
READ ̲PLA ̲LIST? PLA ̲LIST ̲POINTER = FIELD ̲POINTER
PREPARE ̲FIELD(PLA ̲LIST)(CC)
CC = NOT ̲OK?
END ̲BUFFER ̲POINTER = FIELD ̲POINTER
BUFFERSIZE = END ̲BUFFER ̲POINTER - START ̲BUFFER ̲POINTER
RETURN
P̲R̲E̲P̲A̲R̲E̲ ̲F̲I̲E̲L̲D̲ (FIELD ̲GROUP ̲ID)(CC)
CC = OK
INCREMENT FIELD ̲NO
USING RECEIVE ̲FIELD ̲LIST(FIELD ̲NO)
FIELD ̲BYTE ̲ADDRESS = ZERO
FIELD ̲POINTER - START ̲BUFFER ̲POINTER) +
USED ̲LENGTH(FIELD ̲GROUP ̲ID)GT MAX ̲CONVERSION?
FIELD ̲RECORD ̲LENGTH = USED ̲LENGTH(FIELD ̲GROUP ̲ID)
FIELD ̲POINTER = FIELD ̲POINTER + USED ̲LENGTH(FIELD ̲GROUP
̲ID)
FIELD ̲RECORD ̲LENGTH = MAX ̲CONVERSION -
(FIELD ̲POINTER - CONVERSION ̲BUFFER)
FIELD ̲POINTER = CONVERSION ̲BUFFER + MAX ̲CONVERSION
RETURN
4.2.2.4.5 R̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.5.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Preparation of the static part of the PLA ̲RI ̲Field
to contain a subset of PLA ̲RI ̲Records derived from
the previous dynamic PLA ̲RI ̲Field of a message received
For Readdressal.
These static PLA ̲RI ̲Records shall be used when formatting
the second (static) set FL 7 - 8 of a readdressed message.
A message with the subtype "FOR READDRESSAL", is entered
to the Conversion Subpackage with a new set of addresses
appended the previous set of addresses (ADDRESS ̲FIELD);
but the PLA ̲RI ̲Field is not yet corresponding to these
addresses.
4.2.2.4.5.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) READDRESSAL ̲PREPARE
b) READDRESSAL ̲PREPARE (R6)
4.2.2.4.5.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Ref. fig. 4.2.2.4-5 for structure Readdressal Prepare
Module.
The module components are implemented in one procedure.
a) C̲a̲l̲c̲u̲l̲a̲t̲e̲ ̲A̲d̲d̲r̲e̲s̲s̲-̲s̲i̲z̲e̲
Delivers the size of the new dynamic set of addresses
to be used for new offsets of the static PLA ̲RI
̲Records.
b) C̲a̲l̲c̲u̲l̲a̲t̲e̲ ̲P̲L̲A̲ ̲L̲i̲s̲t̲-̲S̲i̲z̲e̲
Delivers the size necessary for generation of the
new dynamic PLA ̲RI ̲Records; this is done on basis
of the PLA ̲List-Size.
c) B̲u̲i̲l̲d̲ ̲s̲t̲a̲t̲i̲c̲ ̲P̲L̲A̲ ̲R̲I̲
Builds up the static PLA ̲RI records and leaves
an empty area for the dynamic PLA ̲RI ̲Records to
be assigned later by the PLA ̲RI Prepare Module.
4.2.2.4.5.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
ADMINISTRATION ̲FIELD (DBD/001 10.1.1)
ADDRESS ̲FIELD (DBD/001 10.1.3)
PLA/RI ̲FIELD (DBD/001 10.1.6)
PLA ̲LIST ̲FIELD (DBD/001 10.1.8)
CONVERSION ̲BUFFER (4.2.2.5.1)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
ADMINISTRATION ̲POINTER
ADMINISTRATION.GROUP ̲READD ̲TO ̲OFFSET
ADDRESS ̲POINTER
PLA ̲LIST ̲POINTER
PLA ̲RI ̲POINTER
PLA ̲RI ̲DYNAMIC ̲COUNT (m)
PLA ̲RI ̲STATIC ̲COUNT (m)
PLA ̲RI.DYNAMIC ̲RECORD (m)
PLA ̲RI.STATIC ̲RECORD (m)
WRITE ̲ADMINISTRATION (m)
SUBDUP ̲PILOT
READDRESSAL
RELAY ̲INSTRUCTION
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
DYNAMIC ̲ADDRESS ̲SIZE : INTEGER
RI ̲STATIC ̲POINTER : INTEGER
STATIC : INTEGER
AIG ̲OFFSET : INTEGER
4.2.2.4.5.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
A readdressal prepare starts with area calculations
for respectively the new dynamic address-field and
PLA ̲RI-Field parts; the dynamic address-part is equal
to the constant that shall be added to all previous
PLA ̲RI ̲offsets in order to match the static address-part.
Next the start-address for the new static PLA ̲RI ̲Records
is calculated and the actual build up of static PLA
̲RI ̲Records is started.
In order to minimize the size of the static PLA ̲RI
̲RECORDS the following records are n̲o̲t̲ transferred from
the dynamic to the static area:
- if bit RI ̲MASK.RELAY is set,
- if bit RI ̲MASK.SECONDARY ̲RI is set,
- additional records referencing to same AIG.
Finally the QEL ̲FLAGS contained in the Administration
̲field is adjusted to represent a readdressed message.
figure 4.2.2.4-5
R̲E̲A̲D̲D̲R̲E̲S̲S̲A̲L̲ ̲P̲R̲E̲P̲A̲R̲E̲
CALCULATE ADDRESS ̲SIZE ( ) (DYNAMIC ̲ADDRESS ̲SIZE)
RI ̲STATIC ̲COUNT = RI ̲DYNAMIC ̲COUNT
CALCULATE PLA ̲LIST ̲SIZE ( ) (RI ̲DYNAMIC ̲COUNT,
RI ̲STATIC ̲POINTER
BUILD STATIC PLA ̲RI (RI ̲STATIC ̲COUNT,
RI ̲STATIC ̲POINTER
DYNAMIC ̲ADDRESS ̲SIZE) ( )
USING RECEIVE ̲ATTRIBUTES ̲QEL ̲HEADER
SET QEL ̲FLAG.READDRESSAL
CLEAR QEL ̲FLAG.PILOT
CLEAR QEL ̲FLAG.RELAY ̲INSTRUCTION
RETURN
BUILD STATIC PLA ̲RI (RI ̲STATIC ̲COUNT,
RI ̲STATIC ̲POINTER,
DYNAMIC ̲ADDRESS ̲SIZE) ( )
STATIC = RI ̲STATIC ̲COUNT
AIG ̲OFFSET = ZERO
RI ̲DYNAMIC ̲POINTER = PLA ̲RI ̲POINTER +
PLA ̲ ̲RI ̲DESCRIPTOR.
LOOP STATIC:
RI ̲MASK = RELAY,
SECONDARY ̲RI or
IGNORE
PLA ̲MASK ̲REF ̲AIG ? AIG ̲OFFSET = PLA ̲OFFSET ?
PLA ̲REF = ZERO
PLA ̲OFFSET + DYNAMIC ̲ADDRESS ̲SIZE
PLA ̲RI ̲STATIC ̲RECORD = PLA ̲RI ̲DYNAMIC ̲RECORD
PLA ̲STATIC ̲POINTER + PLA ̲RI ̲RECORD ̲SIZE
DECREMENT RI ̲STATIC ̲COUNT
RI ̲DYNAMIC ̲POINTER + PLA ̲RI ̲RECORD ̲SIZE
END STATIC LOOP
RETURN
4.2.2.4.6 P̲L̲A̲ ̲R̲I̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.6.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The PLAs and AIGs entered during Message Preparation
at CAMPS are validated by TEP before the message is
released and sent for Conversion; the result of this
validation is a list of PLA ̲refs, some derived from
AIGs - if some PLAs were XMTed, the corresponding PLA
̲refs have been removed.
This validation result is written into a temporary
Field (PLA ̲List ̲Field) in order to increase the conversion
performance.
Due to buffer-limitations TEP could not arrange these
PLA refs into the PLA ̲RI ̲Field as required by the Conversion
Logic; so this function is left for the Conversion
Subpackage, which will arrange these PLA refs into
the PLA ̲RI ̲Field organization.
4.2.2.4.6.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Input:
Output: R5 = CC
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) PLA ̲RI ̲PREPARE ( ) (CC)
b) PLA ̲RI ̲PREPARE (R5, R6)
4.2.2.4.6.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Ref. fig. 4.2.2.4-6 for structure PLA ̲RI Prepare Module.
a) P̲r̲e̲p̲a̲r̲e̲ ̲P̲L̲A̲-̲L̲i̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Combines the delivered PLA ̲REF with a Plain Language
Address of the Address-field and builds up a PLA
̲RI ̲record.
b) P̲r̲e̲p̲a̲r̲e̲ ̲A̲I̲G̲ ̲L̲i̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Combines the delivered PLA ̲REF with an AIG of the
address ̲field and builds up a PLA ̲RI ̲record.
c) F̲i̲n̲i̲s̲h̲ ̲P̲L̲A̲ ̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Inserts one PLA ̲RI ̲record in the PLA ̲RI ̲field.
d) L̲o̲c̲a̲t̲e̲ ̲N̲e̲x̲t̲ ̲L̲i̲n̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.3.2 for description.
e) D̲a̲t̲a̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.1.1 for description.
4.2.2.4.6.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
Administration ̲field (DBD/001, 10.1.1)
Address ̲field (DBD/001 10.1.3)
PLA ̲RI ̲Field (DBD/001 10.1.6)
PLA ̲LIST field (DBD/001 10.1.8)
Conversion Buffer (4.2.2.5.1)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
ADMINISTRATION.NUMBER ̲OF ̲TO ̲ADD
ADMINISTRATION.NUMBER ̲OF ̲INFO ̲ADD
ADMINISTRATION.GROUP ̲TO ̲OFFSET
ADMINISTRATION.GROUP ̲INFO ̲OFFSET
PLA ̲LIST ̲COUNTERS (D)
PLA ̲LIST ̲POINTER (D)
PLA ̲LIST ̲RECORD (D)
PLA ̲RI ̲DYNAMIC ̲COUNT (m)
PLA ̲RI ̲DYNAMIC ̲RECORD (m)
ADDRESS ̲POINTER
PLA ̲RI ̲POINTER (m)
CONVERSION ̲ERROR (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
SUM ̲OF ̲PLA: INTEGER
LAST ̲PLA ̲POINTER: INTEGER
4.2.2.4.9.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
In principle the buffer area containing the PLA ̲List
shall be expanded in order to match the PLA ̲RI record
organization. The first job is then to spread out the
PLA ̲refs back-wards in order to avoid destruction of
the PLA ̲List contents at a too early point.
Now the assignment of offsets and flags can begin;
this is done via the pointers from the administration-field
to the address-field plus the counters derived from
the PLA ̲list.
The counters from the PLA ̲List will identify a PLA
̲ref as associated to a TO ̲PLA, TO ̲AIG, INFO ̲PLA or
INFO ̲AIG; the pointers to the address-field will identify
the size of TO and INFO groups. In combination this
facilitates assignment of offsets in the PLA ̲RI ̲field
to the respective address ̲records associated. If more
PLA-refs are associated to several AIGs it is, however,
not possible to determine which PLA-refs are associated
to which AIG; but this is not important to the routing
and formatting logic; but it is importance to group
these PLA-refs as associated to either a TO ̲AIG or
an INFO ̲AIG. The PLAs of the address-field are examined
for ZEN OR X-indications.
The flowgrams illustrate the principle flow.
Figure 4.2.2.4-6
P̲L̲A̲ ̲R̲I̲ ̲P̲R̲E̲P̲A̲R̲E̲
USING ADDRESS ̲POINTER
USING PLA ̲LIST ̲POINTER
SAVE PLA ̲LIST ̲COUNTERS
PLA ̲RI ̲DYNAMIC ̲COUNT = SUM OF PLA ̲LIST ̲RECORDS
FOR CONVERSION? PLA ̲RI ̲POINTER = PLA ̲LIST ̲POINTER
SETUP PLA ̲RI ̲POINTER
PLA ̲RI ̲POINTER + PLA ̲RI ̲DESCRIPTOR
PREPARE PLA ̲RI ̲RECORDS (PLA ̲RI ̲POINTER, PLA ̲LIST ̲POINTER)()
LOOP PLA ̲TYPES
BUILD PLA ̲RI (PLA ̲TYPE, NEXT ̲PLA ̲TYPE)()
END LOOP PLA ̲TYPES
RETURN
P̲R̲E̲P̲A̲R̲E̲ ̲P̲L̲A̲ ̲R̲I̲ ̲R̲E̲C̲O̲R̲D̲S̲ (PLA ̲RI ̲POINTER, PLA ̲LIST ̲POINTER)()
SETUP LAST ̲PLA ̲POINTER
SETUP LAST ̲PLA ̲RI ̲POINTER
SUM ̲OF ̲PLA = PLA ̲RI ̲DYNAMIC ̲COUNT
LOOP SUM ̲OF ̲PLA:
PLA ̲RI.PLA ̲REF = PLA ̲LIST.PLA ̲REF
PLA ̲RI.PLA ̲OFFSET, PLA ̲MASK, RI ̲MASK = ZERO
PLA ̲RI.PLA ̲RI. SELECTED ̲RI = SPACE
LAST ̲PLA ̲POINTER = PLA ̲LIST ̲POINTER? EXIT LOOP
DECREMENT LAST ̲PLA ̲POINTER
LAST ̲PLA ̲RI ̲POINTER - PLA ̲RI ̲RECORD ̲SIZE
END SUM ̲OF ̲PLA LOOP
RETURN
B̲U̲I̲L̲D̲ ̲P̲L̲A̲ ̲R̲I̲ (PLA ̲TYPE, NEXT ̲PLA ̲TYPE)()
LOOP PLA:
ADDRESS ̲POINTER = NEXT ̲ADDRESS ̲POINTER? EXIT LOOP
PLA ̲TYPE = AIG? PLA ̲MASK.REF ̲AIG
PLA ̲MASK.REF ̲PLA
PLA ̲RI.PLA ̲OFFSET = ADDRESS ̲POINTER
PLA ̲RI ̲POINTER + PLA ̲RI ̲RECORD ̲SIZE
ADDRESS ̲POINTER + ADDRESS ̲RECORD ̲SIZE
END LOOP PLA
LOOP NEXT ̲PLA:
PLA ̲RI ̲POINTER = NEXT ̲PLA ̲TYPE? EXIT LOOP
PLA ̲RI.PLA ̲OFFSET = ADDRESS ̲POINTER
PLA ̲RI ̲POINTER + PLA ̲RI ̲RECORD ̲SIZE
END LOOP NEXT ̲PLA
RETURN
4.2.2.4.7 R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.7.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The functions of the routing module are:
- routing of complete outgoing messages
- routing of user prepared messages in plaindress
- routing of supervisor prepared service messages
- routing of relayed messages
- routing of messages for rerun
- rerouting of messages not transmitted successfully
- routing of SCARS/CCIS messges in format E1
- routing of VDU-pages and Comments to SCARS/CCIS
- Invocation of MSO for RI-assignment
By routing is meant allocation of a Routing Indicator
(if not already allocated) which points to a circuit
for transmission.
4.2.2.4.7.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) ROUTING
b) ROUTING (R6)
4.2.2.4.7.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
See figure 4.2.2.4-10 for Routing Module Structure.
a) R̲e̲a̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲ ̲T̲a̲b̲l̲e̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Fetches the contents of the Circuit-table and the
connectivity table.
Ref. 4.2.2.6.4.7 for description.
b) R̲e̲d̲u̲c̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.8.
c) S̲C̲A̲R̲S̲ ̲C̲C̲I̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.9.
d) M̲S̲O̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.10.
e) C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.11.
f) S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.12.
g) R̲o̲u̲t̲i̲n̲g̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.13
h) E̲x̲e̲m̲p̲t̲ ̲D̲u̲p̲l̲i̲c̲a̲t̲e̲-̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Flags duplicate RIs in the PLA ̲RI ̲Field.
i) L̲o̲c̲a̲t̲e̲ ̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.2.5 for description.
4.2.2.4.7.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
QEL Data (4.2.2.5.3)
Routing Data (4.2.2.5.5)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
PLAINDRESS ̲TYPE
SCARS ̲CCIS ̲TYPE
RECEIVE ̲QEL ̲HEADER
PLA ̲RI ̲DYNAMIC ̲COUNT
PLA ̲RI.RI ̲MASK (m)
CIRCUIT ̲KEY (m)
CONNECTIVITY ̲RESULT (m)
CIRCUIT ̲RESULT (m)
ROUTING ̲LIST
CAMPS ̲ORIGINATOR
RELAY ̲INSTRUCTIONS
WRITE ̲ADMINISTRATION (m)
WRITE ̲PLA ̲RI (m)
HQ ̲MASK (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
ROUTING ̲CC = OK, NOT ̲OK
RELAY ̲ASSIGN ̲COUNT: INTEGER
4.2.2.4.7.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
Messages received for Rerouting, Rerun, or Relaying
are selected for the Reduced Routing Module and after
this treatment forwarded to the Completed Routing Module
- the PLA ̲RI ̲Field contains more RIs for FL2 than
necessary for this transmission:
SCARS ̲CCIS VDU pages or Comments are selected for the
SCARS ̲CCIS Routing Module which will route these messages
based on QEL information derived from a system code
associated to delivery-SCDs.
Messages returned from RI-assignment are selected for
the MSO-Routing module, which will build up the missing
elements of the PLA ̲RI ̲Field based on the RI-assignment-field
contents; after this the Completed Routing Module is
activated.
The Completed Routing Module will also be activated
for assignment of circuits for non CAMPS originated
messages (complete messages) in ACP127 format and Supervisor
prepared service messages containing RIs. Messages
entered for conversion without RIs will be assigned
RIs and circuits by the Selective Routing Module.
If a routing did not succeed this incident will be
reported back to the Routing Module which will then
activate the RI-assignment Module; this module will
build up a RI-assignment-Field to be presented for
the MSO during assignment.
Figure 4.2.2.4-7
R̲O̲U̲T̲I̲N̲G̲
ROUTING ̲CC = OK, ROUTING ̲COUNT = ZERO
FETCH ̲CIRCUIT ̲TABLE
SC ̲COMMENT, OR
SC ̲VDU ̲PAGE? SCARS ̲CCIS ̲ROUTING()(ROUTING
̲CC
CASE SUBTYPE OF:
FOR ̲REROUTING
FOR ̲RERUN, OR REDUCED ̲ROUTING
FOR ̲RELAYING?
COMPLETED ̲ROUTING()
(ROUTING ̲COUNT,
ROUTING ̲CC)
FROM ̲RI ̲ASSIGNMENT? MSO ̲ROUTING
COMPLETED ̲ROUTING()
(ROUTING ̲COUNT,
ROUTING ̲CC)
FOR ̲READDRESSAL? SELECTIVE ̲ROUTING ()
(ROUTING ̲COUNT,
ROUTING ̲CC)
FOR ̲CONVERSION SC ̲TYPE = TRUE?
CAMPS ̲ORIGINATED? PLAINDRESS
̲TYPE?
COMPLETED ̲ROUTING ()
(ROUTING ̲COUNT,
ROUTING ̲CC)
SELECTIVE ̲ROUTING ()
(ROUTING ̲COUNT,
ROUTING ̲CC)
END CASE SUBTYPE
ROUTING ̲CC = NOT ̲OK? RI ̲ASSIGNMENT
EXEMPT ̲DUPLICATE ̲RI (ROUTING ̲COUNT)()
RETURN
E̲X̲E̲M̲P̲T̲ ̲D̲U̲P̲L̲I̲C̲A̲T̲E̲ ̲R̲I̲ (ROUTING ̲COUNT)()
ROUTING ̲INDEX = ZERO
LOOP ROUTING ̲COUNT:
PLA ̲RI ̲RECORD = ROUTING ̲LIST (ROUTING ̲INDEX)
INCREMENT ROUTING ̲INDEX
RI ̲POINTER = PLA ̲RI.SELECTED ̲RI
PLA ̲RI.RI ̲MASK =
DUPLICATE ̲RI, CLEAR RI ̲MASK.MSO ̲IGNORE
SECONDARY ̲RI,
IGNORE, OR
MSO ̲IGNORE
PLA ̲RI.PLA ̲MASK = LOCAL ̲HQ?
CLEAR RI ̲MASK.MSO ̲INSERT
LOOP ROUTING ̲INDEX:
LOCATE ̲RI (RI ̲POINTER, AFTER)
(PLA ̲RI ̲INDEX)(CC)
CC = NOT ̲OK? EXIT LOOP
PLA ̲RI.RI ̲MASK(PLA ̲RI ̲INDEX) = DUPLICATE
END ROUTING ̲INDEX LOOP
ROUTING ̲INDEX GE ROUTING ̲COUNT? EXIT LOOP
END LOOP ROUTING ̲COUNT
RETURN
4.2.2.4.8 R̲e̲d̲u̲c̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.8.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The PLA ̲RI ̲Field might contain more RIs to be used
when formatting FL2 than necessary (or required) for
messages forwarded to the Conversion Subpackage for
relaying, rerouting, or rerun.
The function of the Reduced Routing Module is then
to exempt these RIs from the PLA ̲RI ̲Field.
If the message should be forwarded for RI-assignement,
it would not be possible to determine the routing
purpose otherwise.
4.2.2.4.8.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
a) REDUCED ̲ROUTING
b) REDUCED ̲ROUTING (R6)
4.2.2.4.8.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
Selfcontained.
4.2.2.4.8.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
QEL DATA (4.2.2.5.3)
PLA ̲RI ̲Field (DBD/001 10.1.6)
VIEW DATA (4.2.2.5.4)
Routing Data (4.2.2.5.5)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
PLA ̲RI ̲POINTER
PLA ̲RI ̲DYNAMIC ̲COUNT
PLA ̲RI.RI ̲MASK (m)
PLA ̲RI.CIRCUIT ̲NUMBER
PLA ̲RI ̲ROUTING ̲CODE
RECEIVE ̲QEL ̲ATTRIBUTE
WRITE ̲PLA ̲RI (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
ROUTING ̲COUNT INTEGER
4.2.2.4.8.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
A loop corresponding to the number of dynamic PLA ̲RI
̲records is set up. Each record is then examined in
order to exempt RIs not to be part of this transmission.
The following records are accepted:
- if no RI-selected is found
- if the selected RI is an secondary-RI (= FL2 of
an incoming message with pilot)
If a message is received for relaying then records
flagged for Relay are accepted. If a message is received
for Rerun or Rerouting the records with a circuit-number
matching to the circuit-number received via the QEL
̲INFO is accepted. Otherwise an ignore-flag will be
assigned in order to avoid transmission to that RI.
R̲E̲D̲U̲C̲E̲D̲ ̲R̲O̲U̲T̲I̲N̲G̲
REDUCED = PLA ̲RI ̲DYNAMIC ̲COUNT
NO ̲OF ̲PLA ̲RI = ZERO
LOOP REDUCED:
USING PLA ̲RI ̲RECORD (NO ̲OF ̲PLA ̲RI)
INCREMENT NO ̲OF ̲PLA ̲RI
PLA ̲RI.SELECTED ̲RI = SPACE?
PLA ̲RI.RI ̲MASK = SECONDARY ̲RI?
SELECT = TRUE
CASE SUBTYPE OF:
FOR ̲RELAYING? PLA ̲RI.RI ̲MASK=RELAY?
SELECT = FALSE
FOR ̲REROUTING, OR
FOR ̲RERUN PLA ̲RI.CIRCUIT ̲NO
= RECEIVE ̲QEL ̲INF
SELECT = FALSE
END CASE SUBTYPE
SELECT? PLA ̲RI.RI ̲MASK = ZERO
PLA ̲RI.RI ̲MASK = IGNORE
END LOOP REDUCED
WRITE ̲PLA ̲RI = TRUE
RETURN
4.2.2.4.9 S̲C̲A̲R̲S̲ ̲C̲C̲I̲S̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.9.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
VDU pages and Comments are forwarded to the Conversion
Subpackage for conversion into SCARS/CCIS Format E1.
Before these message-types will be formatted, the transmision-circuits
are examined for availability and a security check
shall be performed; this is the function of the SCARS-CCIS
Routing Module who also will setup the logical circuit
numbers to be used during Finish Formatting Procedures.
4.2.2.4.9.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Input:
Output: R5 = ROUTING ̲CC
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) SCARS ̲CCIS ̲ROUTING ()(ROUTING ̲CC)
b) SCARS ̲CCIS ̲ROUTING (R5, R6)
4.2.2.4.9.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
See figure 4.2.2.4-9 for structure SCARS ̲CCIS Routing
Module.
a) S̲e̲a̲r̲c̲h̲ ̲S̲C̲-̲C̲i̲r̲c̲u̲i̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Will find the logical circuit-number associated
to SCARS or/and CCIS.
b) C̲h̲e̲c̲k̲ ̲C̲i̲r̲c̲u̲i̲t̲-̲S̲t̲a̲t̲u̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Refer 4.2.2.6.2.1 for description.
c) R̲o̲u̲t̲i̲n̲g̲ ̲R̲e̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.14 for description.
4.2.2.4.9.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
TMP Data (4.2.2.5.2)
Routing Data (4.2.2.5.5)
Channel Tables (DBD/001 5.3.4)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
FOR ̲SCARS
FOR ̲CCIS
SCARS ̲CIRCUIT (m)
CCIS ̲CIRCUIT (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
None
4.2.2.4.9.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
This module is controlled from the Routing module from
where it is activated if the QEL ̲maintype equals VDU-page
or SC-Comment; the result of the routing is reported
back via the Routing-CC.
The information available are booleans indicating which
system(s) shall receive the message; this information
is used as secondary-key in a search into the Circuit-table;
since only one SCARS and one CCIS circuit-type exist
the profile returned by this search is unique.
The logical circuit number located is used as parameter
in a search into the connectivity table and the associated
circuit-classification in a comparison with the message
classification; these activities may result in respectively
and unavailability or classification mismatch which
later will cause a rejection of the message to either
the drafter or MSO.
Figure 4.2.2.4-9
S̲C̲A̲R̲S̲ ̲C̲C̲I̲S̲ ̲R̲O̲U̲T̲I̲N̲G̲()(ROUTING ̲CC)
FOR ̲SCARS SEARCH ̲SC ̲CIRCUIT(SCARS)(CIRCUIT ̲NO)
CHECK ̲CIRCUIT ̲STATUS(CIRCUIT ̲NO,
DUMMY ̲POINTER)
(ROUTING ̲CODE)
ROUTING ̲CODE NE OK? ROUTING ̲CC = NOT ̲OK
SCARS ̲CIRCUIT = CIRCUIT ̲NO
FOR ̲CCIS SEARCH ̲SC ̲CIRCUIT(SCARS)(CIRCUIT ̲NO)
CHECK ̲CIRCUIT ̲STATUS(CIRCUIT ̲NO,
DUMMY ̲POINTER)
(ROUTING ̲CODE)
ROUTING ̲CODE NE OK? ROUTING ̲CC = NOT ̲OK
CCIS ̲CIRCUIT = CIRCUIT ̲NO
RETURN
S̲E̲A̲R̲C̲H̲ ̲S̲C̲ ̲C̲I̲R̲C̲U̲I̲T̲(CIRCUIT ̲TYPE)(CIRCUIT ̲NO)
CIRCUIT ̲NO = ZERO
NO ̲OF ̲CIRC = ZERO
EQUIVALENCE (CIRCUIT ̲RESULT = RESULT ̲AREA ̲2)
LOOP MAX ̲CIRCUITS
INCREMENT NO ̲OF ̲CIRC
CIRCUIT ̲TYPE NE CIRCUIT ̲RESULT.CIRCUIT ̲TYPE(NO
̲OF ̲CIRC)?
CIRCUIT ̲NO = CIRCUIT ̲RESULT.CIRCUIT ̲NO(NO ̲OF ̲CIRC)
EXIT LOOP
END MAX ̲CIRCUITS LOOP
RETURN
4.2.2.4.10 M̲S̲O̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.10.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
When MSO reenters a message after RI-assignment, the
RI-assignments (and Relay-assignments) shall be transferred
to the PLA ̲RI ̲Field. The function of this module is
to update the PLA ̲RI ̲Field with the result of MSO assigned
RIs and Relay-instructions.
Another function is to detect MSO assigned "ZEN" and
delete-marked X-PLAs and adjust the address-field in
accordance with this.
The updates performed by this module will have no affect
in case more routing-errors are detected at a later
stage in the processing.
4.2.2.4.10.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
INPUT:
OUTPUT: R4 = Relay ̲Assignment-Count
R5 = Routing ̲CC
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) MSO ̲ROUTING ( ) (RELAY ̲ASSIGN ̲COUNT,CC)
b) MSO ̲ROUTING (R4, R5, R6)
4.2.2.4.10.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
a) L̲o̲c̲a̲t̲e̲ ̲P̲L̲A̲ ̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
- Selects record with possibility for Alternative
RI-assignments
b) A̲s̲s̲i̲g̲n̲ ̲A̲l̲t̲e̲r̲n̲a̲t̲i̲v̲e̲-̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
- Inserts new assigned RI in the PLA ̲RI ̲Records
- Reports detection of MSO assigned ZEN or initiated
deletion of an X ̲PLA.
c) U̲p̲d̲a̲t̲e̲ ̲A̲d̲d̲r̲e̲s̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
- Insert ZEN in front of a PLA of an address-record
(MSO-assigned)
- overwrites a detected X-PLA address record
with the contents of the following and updates
the offsets and line-numbers referenced via
the Administration-field accordingly.
d) M̲o̲v̲e̲ ̲R̲e̲l̲a̲y̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
- Transfers relay ̲instructions to/from an empty
area in case a new PLA ̲RI ̲record with a relay
̲ responsible RI shall be appended.
e) L̲o̲c̲a̲t̲e̲ ̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Refer 4.2.2.6.2.5 for description
Locates the record-number of the PLA ̲RI field corresponding
to a RI.
f) I̲n̲s̲e̲r̲t̲s̲ ̲R̲e̲l̲a̲y̲-̲R̲e̲s̲p̲o̲n̲s̲i̲b̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Inserts the Relay-responsible RI in front of the
PLA ̲RI ̲RECORDS in case this RI is not already among
the selected RIs.
g) C̲o̲m̲p̲a̲r̲e̲ ̲R̲I̲
Ref. 4.2.2.6.2.4 for description
4.2.2.4.10.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
View data (4.2.2.5.4)
Routing Data (4.2.2.5.5)
Administration Field (DBD/001 10.1.1)
Address Field (DBD/001 10.1.3)
PLA ̲RI-Field (DBD/001 10.1.6)
RI-Assignment Field (DBD/001 10.1.8)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
ADMINISTRATION.NUMBER ̲OF ̲TO ̲ADD (m)
ADMINISTRATION.NUMBER ̲OF ̲INFO ̲ADD(m)
ADMINISTRATION.GROUP ̲OF ̲INFO ̲ADD (m)
ADMINISTRATION.GROUP ̲INFO ̲OFFSET (m)
ADDRESS ̲RECORD (m)
RELAY ̲DYNAMIC ̲COUNT (m)
PLA ̲RI ̲DYNAMIC ̲COUNT (m)
PLA ̲RI ̲RECORD (m)
RI ̲ASSIGNMENT ̲DESCRIPTOR (d)
RI ̲ASSIGNMENT ̲RECORD (d)
RELAY ̲ASSIGNMENT ̲RECORD (d)
WRITE ̲ADMINISTRATION (m)
WRITE ̲ADDRESS (m)
HQ ̲MASK (m)
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
END ̲ADDRESS ̲POINTER: INTEGER
RELAY ̲ASSIGN ̲POINTER: INTEGER
PLA ̲RI ̲RELAY ̲POINTER: INTEGER
RI ̲RECORD ̲COUNT: INTEGER
RI ̲ASSIGNMENT ̲COUNT: INTEGER
RELAY ̲ASSIGN ̲COUNT: INTEGER
RELAY ̲INFO ̲COUNT: INTEGER
4.2.2.4.10.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
First the procedure "Check RI-assignment" will select
the possible subjects (records) changed during MSO
assignments; the RI-assignment records returned are
in correspondence with the number of records delivered
for RI-assignment and the same principles can be followed
for relocation, that is (not included in the RI assignment-list):
- if the PLA ̲RI-record has no selected RI
- if the selected RI is of secondary type
- if the Routing-Code equals "IGNORE"
Having located a PLA ̲RI-record that might have assigned
an alternative RI, it is examined whether this actually
has been done via a compare between the ASSIGN ̲RI (might
be unchanged) and the previously selected RI; if an
assignment had been performed the PLA ̲RI (the RI to
preceed the PLA in FL 7/8) is also changed accordingly.
If the "RI" assigned by MSO equals "ZEN" or "SPACE",
the address-record corresponding to the PLA ̲RI-record
is adjusted accordingly; if "ZEN" the ZEN is
inserted in front of the address-pla otherwise the
address-record is deleted.
A delete is performed by means of a flag in the RI-mask
of the PLA ̲RI ̲record and by insertion of "X/" in front
of the associated address ̲record.
Finally MSO might have assigned relay instructions;
the relay responsible RI is located in the PLA ̲RI ̲List;
if found as a selected RI no action is needed, otherwise
a new PLA ̲RI-record shall be inserted with this RI
as an selected RI. RIs located after the "T" are also
searched in the PLA ̲RI-list; if found as selected the
MSO ̲IGNORE is assigned that record indicating no transmission
via that RI; it is not removed in case additional invocation
for RI-assignment (MSO) is needed
The flowgrams illustrate the principle flow which has
been implemented in the structure described in module
components.
Figure 4.2.2.4-10
M̲S̲O̲ ̲R̲O̲U̲T̲I̲N̲G̲
USING RI ̲ASSIGNMENT ̲POINTER
USING PLA ̲RI ̲POINTER
USING END ̲ADDRESS ̲POINTER
RI ̲RECORDS = PLA ̲RI ̲DYNAMIC ̲COUNT
RI ̲ASSIGNMENTS = ZERO
CHECK ̲RI ̲ASSIGNMENTS
RI ̲ASSIGNMENT.RELAY ̲ASSIGN ̲COUNT = ZERO?
RELAY ̲RECORDS = RELAY ̲ASSIGN ̲COUNT
SETUP RELAY ̲ASSIGN ̲POINTER
SETUP PLA ̲RI ̲RELAY ̲POINTER
PLA ̲RI ̲RELAY ̲POINTER + INFO ̲RELAY ̲RECORD ̲SIZE
CHECK RELAY ̲ASSIGNMENTS
RETURN
C̲H̲E̲C̲K̲ ̲R̲I̲ ̲A̲S̲S̲I̲G̲N̲M̲E̲N̲T̲
LOOP RI ̲RECORDS:
RI ̲RECORD = PLA ̲RI ̲DYNAMIC ̲COUNT? EXIT LOOP
PLA ̲RI.SELECTED ̲RI = SPACE?
PLA ̲RI.RI ̲MASK = IGNORE?
PLA ̲RI.RI ̲MASK.SECONDARY ̲RI?
INCREMENT RI ̲ASSIGNMENTS
ASSIGN ALTERNATIVE-RI (RI ̲ASSIGNMENTS,
RI ̲RECORD)
(ASSIGN ̲CODE)
ASSIGN ̲CODE NE OK? ADJUST ADDRESSEE
(PLA ̲OFFSET,
ASSIGN ̲CODE,
END ̲ADDRESS ̲POINTER)
(END ̲ADDRESS ̲POINTER)
END RI ̲RECORD LOOP
Continues
A̲S̲S̲I̲G̲N̲ ̲A̲L̲T̲E̲R̲N̲A̲T̲I̲V̲E̲ ̲R̲I̲ (RI ̲ASSIGNMENTS,
RI ̲RECORD)
(ASSIGN ̲CODE)
ASSIGN ̲CODE = OK
ASSIGN ̲RI = SELECTED ̲RI?
SELECTED ̲RI = PLA ̲RI? PLA ̲RI = ASSIGN ̲RI
SELECTED ̲RI = ASSIGN ̲RI
ASSIGN ̲RI = "ZEN"? PLA ̲RI = SPACE?
SET PLA ̲MASK.ZEN
ASSIGN ̲CODE = ZEN
ASSIGN ̲RI NE SPACE?
PLA ̲MASK.X ̲PLA? PLA ̲RI.RI ̲MASK = IGNORE
ASSIGN ̲CODE = X ̲PLA
RETURN
C̲H̲E̲C̲K̲ ̲R̲E̲L̲A̲Y̲ ̲A̲S̲S̲I̲G̲N̲M̲E̲N̲T̲
SAVE RELAY ̲ASSIGNMENT ̲COUNT
LOOP RELAY ̲ASSIGNMENTS:
PLA ̲RI ̲RELAY ̲RECORD = RELAY ̲ASSIGN ̲RECORD
INCREMENT RELAY ̲DYNAMIC ̲COUNT
RELAY ̲RI = RELAY ̲RESPONSIBLE ̲RI
LOCATE ̲RI (RELAY ̲RI, AFTER)(PLA ̲RI ̲REC, CC)
FOUND = FALSE? INSERT RELAY ̲RESPONSIBLE (RELAY ̲RI)()
LOOP T ̲RELAYS:
NEXT ̲RELAY = RELAY ̲RESPONSIBLE ̲RI?
LOCATE ̲RI (RELAY ̲RI, AF)(PLA, RI ̲REC, CC)
FOUND? PLA ̲RI.RI ̲MASK = DUPLICATE ̲RI
RI ̲RECORDS = PLA ̲RI ̲DYNAMIC ̲COUNT? EXIT
END T ̲RELAYS LOOP
END RELAY ̲ASSIGNMENTS LOOP
RETURN
I̲N̲S̲E̲R̲T̲ ̲R̲E̲L̲A̲Y̲ ̲R̲E̲S̲P̲O̲N̲S̲I̲B̲L̲E̲ (RELAY ̲RI)()
SETUP LAST ̲WORD (PLA ̲RI ̲FIELD)
NEW ̲LAST ̲WORD = (LAST ̲WORD + PLA ̲RI ̲RECORD ̲SIZE)
SETUP FIRST ̲PLA ̲RI ̲POINTER
LOOP DOWN ̲WARDS
NEW ̲LAST ̲WORD = LAST ̲WORD
LAST ̲WORD ̲ADS = FIRST ̲PLA ̲POINTER? EXIT
DECREMENT NEW ̲LAST ̲WORD, LAST ̲WORD
END DOWN ̲WARDS LOOP
(PLA ̲REF, PLA ̲OFFSET, PLA ̲MASK, RI ̲MASK, ROUTING ̲CODE)=ZERO
PLA ̲RI = SPACE
SELECTED ̲RI = RELAY ̲RI
PLA ̲RI.RI ̲MASK = MSO ̲INSERT.
INCREMENT PLA ̲RI ̲DYNAMIC ̲COUNT
RETURN
4.2.2.4.11 C̲o̲m̲p̲l̲e̲t̲e̲d̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲M̲o̲d̲u̲l̲e̲
4.2.2.4.11.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The functions of the Completed Routing modules are:
- validation of RIs to be formatted into FL2 of complete
entered outgoing messages, supervisor prepared
ASM or abbreviated plaindress service messages,
MSO assigned RIs and other messages entered to
conversion with preselected RI (relaying, rerun,
and rerouting)
- allocation of circuits corresponding to the preselected
RIs
- check of classification RI/message and circuit/message
- check of circuit availability
4.2.2.4.11.2 M̲o̲d̲u̲l̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Input:
Output: R5 = Routing-cc
C̲a̲l̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) COMPLETED ̲ROUTING ()(ROUTING ̲CC)
b) COMPLETED ̲ROUTING (R5, R6)
4.2.2.4.11.3 M̲o̲d̲u̲l̲e̲ ̲C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲
See figure 4.2.2.4-11 for structure Completed Routing
Module
a) C̲o̲l̲l̲e̲c̲t̲ ̲R̲I̲ ̲K̲e̲y̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.4.2 for description.
b) S̲e̲a̲r̲c̲h̲ ̲R̲I̲ ̲T̲a̲b̲l̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Ref. 4.2.2.6.4.4 for description.
c) C̲h̲e̲c̲k̲ ̲R̲I̲-̲S̲t̲a̲t̲u̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Refer 4.2.2.6.2.2 for description.
d) C̲h̲e̲c̲k̲ ̲C̲i̲r̲c̲u̲i̲t̲ ̲S̲t̲a̲t̲u̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Refer 4.2.2.6.2.2 for description
e) U̲p̲d̲a̲t̲e̲ ̲P̲L̲A̲ ̲R̲I̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Refer 4.2.2.6.2.3 for description.
f) R̲o̲u̲t̲i̲n̲g̲ ̲R̲e̲p̲o̲r̲t̲ ̲M̲o̲d̲u̲l̲e̲
Refer 4.2.2.4.14 for description.
4.2.2.4.11.4 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) D̲a̲t̲a̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
Routing Data (4.2.2.5.5)
Formatting Data (4.2.2.5.6)
TMP ̲Data (4.2.2.5.2)
PLA ̲RI ̲Field (DBD/001 10.1.6)
Channel Tables (DBD/001 5.3.4)
RI-Table (DBD/001 6.7)
b) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲
PLA ̲RI ̲RECORD (m)
PLA ̲RI ̲DYNAMIC ̲COUNT
RECEIVE ̲QEL ̲ATTRIBUTE
WRITE ̲PLA ̲RI (m)
ROUTING ̲LIST (m)
ADMINISTRATION.CLASS
RI ̲VALIDATION (m)
CLEAR ̲INSTRUCTION (m)
PUNCH ̲INSTRUCTION
c) L̲o̲c̲a̲l̲ ̲D̲a̲t̲a̲
NO ̲OF ̲PLA ̲RI: INTEGER
NO ̲OF ̲RI: INTEGER
4.2.2.4.14.5 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲i̲g̲n̲
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 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.
The result of the circuit-table-search is used for
detect of classification mismatch circuit/message and
a Circuit Availability Test. In principle a Routing
code caused by a previously failed test will not be
overwritten (i.e. the RI/Message classification check
failed - this will be reported to MSO even if the later
classification Check Circuit/Message should also fail)
For classification mismatch the MSO-instructions Punch
or Clear will be taken in consideration.
The operations described above will be repeated in
case the number of RI's exceeds the constant MAX ̲KEYS.…86…1
…02… …02… …02… …02… …02… …02…
Figure 4.2.2.4-11
C̲O̲M̲P̲L̲E̲T̲E̲D̲ ̲R̲O̲U̲T̲I̲N̲G̲ () (ROUTING ̲COUNT, ROUTING ̲CC)
NO ̲OF ̲PLA ̲RI = PLA ̲RI ̲DYNAMIC ̲COUNT
EQUIVALENCE (RI ̲KEY = KEY ̲AREA)
EQUIVALENCE (RI ̲RESULT = RESULT ̲AREA ̲1)
FINISH ̲RI = FALSE
NO ̲OF ̲RI = ZERO
RI ̲VALIDATION = FALSE
CIRCUIT ̲NO = ZERO
LOOP FINISH ̲RI:
COLLECT COMPLETE ̲RI (NO ̲OF ̲PLA ̲RI, NO ̲OF RI)
(NO ̲OF ̲RI; NO ̲OF ̲RI ̲KEYS)
NO ̲OF ̲RI = ZERO? ROUTING ̲CC = NOT ̲OK
NO ̲OF ̲RI ̲KEYS = ZERO? FINISH ̲RI = TRUE EXIT LOOP
SEARCH ̲RI ̲TABLE(NO ̲OF ̲RI ̲KEYS) ( )
continued
continued C̲O̲M̲P̲L̲E̲T̲E̲D̲ ̲R̲O̲U̲T̲I̲N̲G̲
LOOP NO ̲OF ̲RI ̲KEYS:
RI ̲KEY.KEY ̲IDENT. COUNT (NO ̲OF ̲RI ̲KEYS) NE ZERO?
RI ̲VALIDATION = TRUE
ROUTING ̲CODE = UNKNOWN ̲RI
RI ̲REC ̲POINTER = RI ̲KEY.KEY ̲IDENT.ADS(NO ̲OF ̲RI
̲KEYS)
CHECK ̲RI ̲CLASS (RI ̲REC ̲POINTER)
(CIRCUIT ̲NO, ROUTING ̲CODE)
ROUTING ̲CODE NE OK?
CHECK ̲CIRCUIT ̲STATUS (CIRCUIT ̲NO, RI ̲REC ̲POINTER)
(ROUTING ̲CODE)
USING PLA ̲RI ̲RECORD (NO ̲OF ̲RI)
PLA ̲RI.ROUTING ̲CODE = ROUTING ̲CODE
ROUTING ̲CODE NE OK? ROUTING ̲CC = NOT ̲OK
PLA ̲RI.CIRCUIT = CIRCUIT ̲NO
END LOOP NO ̲OF ̲RI-KEYS
END FINISH ̲RI LOOP
ROUTING ̲COUNT = NO ̲OF ̲RI
RETURN
