ISO/IEC 10168-4:1996

INTERNATIONAL ISO/IEC
STANDARD
10168-4
First edition
1996-12-15
Information technology - Open Systems
Interconnection - Conformance test suite
for the Session protocol -
Part 4:
Test management protocol specification
Technologies de /‘information - lnterconnexion de systemes ouverts -
Suite de tests de conformitk pour le protocole de session -
Partie 4: Spkifica tion du pro tocole de gestion de tests
Reference number
ISO/lEC 10168-4:1996(E)

---------------------- Page: 1 ----------------------
ISOAEC 10168-4 : 1996 (E)
Contents
Page
. . .
III
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
1
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Normative references
3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3.1 Reference model definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3.2 Conformance testing methodology and framework definitions . . . . . . . . . . . . . . . . . . . . . 1
3.3 Session test management protocol definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4 Symbols and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.*. 2
6 Service assumed from the Session IUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 3
6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6.2 Use of parameters by service primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7 Definition of the SL-TMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.1 General procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.2 Implicit reaction . 3
7.3 Explicit reaction . 3
7.3.1 Definition of SL-TMPDU sent by LT . 3
7.3.2 General procedure for executing the reactions memorized in the FIFO
queue . 4
7.3.2.1 Use of this general procedure . 4
4
7.3.2.2 Execution of this general procedure .
7.3.3 Processing a valid explicit reaction . 4
7.3.3.1 Processing an “Absorption of SP” reaction . 5
7.3.3.2 Processing an “execute the reactions memorized in the FIFO queue”
reaction . 5
7.3.3.3 Processing a “Purge reactions memorized in the FIFO queue” reaction 6
7.3.3.4 Processing any other reaction . 6
7.3.4 Building a reaction . 6
7.3.4.1 Building parameters . 7
7
7.3.4.2 Building User-Data .
7.4 Service Violation . 8
7.5 Protection against connection rejection by session . 8
8 Coding rules . 9
8.1 PDU sent by LT . 9
8.1.1 Coding of REACTION parameter . 10
8.1.2 Coding of RES-PAR-VAL parameter . 11
..................................................................... 12
8.2 Coding of the RP-SL-TMPDU
................................................. 12
8.2.1 Coding of the RECEIVED-SP parameter
8.2.2 Coding of RECEIVED-PAR parameter . 12
0 ISO/IEC 1996
All rights reserved. Unless otherwise specified, no part of this publication may be
reproduced or utilized in any form or by any means, electronic or mechanical, including
photocopying and microfilm, without permission in writing from the publisher.
ISO/IEC copyright Office . Case Postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland

---------------------- Page: 2 ----------------------
0 ISOAEC ISOAEC 10168-4 : 1996 (E)
Foreword
for Standardization) and IEC (the
IS0 (The International Organization
International Electrotechnical Commission) form the specialized system for
worldwide standardization. National bodies that are members of IS0 or IEC
participate in the development of International Standards through technical
committee established by the respective organization to deal with particular fields
of technical activity. IS0 and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non-
governmental, in liaison with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISOAEC JTC 1. Draft International Standards adopted by
the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the
national bodies casting a vote.
International Standard ISOAEC 10168 was prepared by Joint Technical
Committee ISOAEC JTC 1, Information technology, Subcommittee SC 21, Open
systems interconnection, data management and open distributed processing.
ISO/IEC 10168 consists of the following parts, under the general title information
Open Systems Interconnection - Conformance test suite for the
technology -
Session protocol:
- Part I: Test suite structure and test purposes
- Parf 4: Test management protocol specification

---------------------- Page: 3 ----------------------
ISOAEC 10168-4 : 1996 (E) 0 ISOAEC
Introduction
This part of ISO/IEC 10168, a multipart International Standard, specifies a Test
Management Protocol together with an Upper Tester for the Coordinated test
method as applied to ISO/IEC 83274, the Session protocol, versions 1 and 2,
except for the symmetric synchronize and the data separation functional units.
A fundamental objective of the related standardized conformance test suites is to
establish uniform conformance testing and unambiguous evaluation procedures
for checking the ability of a Session protocol implementation to operate
according to ISO/IEC 8327.
The standardization of these test suites should lead to comparability and wide
acceptance of test results produced by different test laboratories, and therefore
minimize repeated conformance testing of the same Session protocol
implementation.
The conformance test suites based on this part of ISO/IEC 10168 are designed
for use by :
which provide a conformance
test laboratories testing service for the
a)
Session protocol
test realizers which provide a means of testing to be used by such test
W
labo ratories ;
The purpose of conformance testing is to increase the probability that different
implementations are able to interwork, although conformance testing alone
cannot give a guarantee of interworking. Conformance testing increases the
confidence that each implementation conforms to the protocol specification by
establishing that it has the required capabilities and that its behaviour conforms
to the protocol specification in representative instances of communication.
IV

---------------------- Page: 4 ----------------------
INTERNATIONAL STANDARD 0 ISOAEC ISO/IEC 10168-4 : 1996 (E)
Information technology - Open Systems Interconnection -
Conformance test suite for the Session protocol -
Part 4:
Test management protocol specification
ISO/IEC 9646-2 : 1994, Information technology - Open
1 Scope
testing
Systems Interconnection - Conformance
This part of ISO/IEC 10168 defines :
methodology and framework - Part 2: Abstract Test Suite
specification.
a) procedures for a single protocol for the transfer
of data and control information from one test
3 Definitions
management entity (the Lower Tester) to a peer
test management entity (the Upper Tester);
3.1 Reference model definitions
b) the structure and encoding of the test
For the purposes of this part of ISO/IEC 10168, the
management protocol data units used to operate
following definitions are taken from ISO/IEC 7498-l :
the test management protocol.
a) Service primitive,
These procedures are defined in term of :
b) Session service,
the service primitives sent and received by the
a)
Upper Tester ;
c) Session connection,
b) the Session Layer - Test Management Protocol
d) Session service data unit,
Data Unit sent and received by the Upper Tester.
Protocol data unit.
e)
2 Normative references
3.2 Conformance testing methodology and
The following standards contain provisions which, through
framework definitions
reference in this text, constitute provisions of this part of
For the purposes of this part of ISO/IEC 10168, the
ISO/IEC 10168. At the time of publication, the editions
following definitions are taken from ISO/IEC 9646-l :
indicated were valid. All standards are subject to revision,
and parties to agreements based on this part of ISO/IEC
a) Upper tester,
10168 are encouraged to investigate the possibility of
applying the most recent editions of the standards indicated
b) Lower tester,
below. Members of IEC and IS0 maintain registers of
c) Test coordination procedures,
currently valid International Standards.
d) Test management protocol,
ISO/IEC 7498-l : 1994, Information technology - Open
Systems Interconnection - Basic Reference Model: The
e) Coordinated test method, u.
Basic Model.
Implementation under test,
0
ISO/IEC 7498-3 : 1989, lnformation processing systems -
g) System under test,
Open Systems interconnection - Basic Reference Model -
Part 3: Naming and addressing.
h) Point of control and observation,
ISO/IEC 8326 : 1996, Information technology - Open
Verdict.
9
Systems interconnection - Session service definition.
3.3 Session test management protocol definitions
lSO/I EC 8327-l : 1996, lnformation technology - Open
,
Systems Interconnection - Connection-oriented Session
For the purposes of this part of ISO/IEC 10168, the
protocol: Protocol specification.
following definitions are also used :
ISO/IEC 8348 : 1993, Information technology - Open
3.3.1 TLV : an encoding technique in which a parameter is
b
1
Systems Interconnection - Network Service Definition.
encoded by a type, a length and a value.
ISO/I EC 10731 : 1994, Information technology - Open
3.3.2Session layer test management protocol : the test
Systems Interconnection - Basic Reference Model -
management protocol used to test session entities.
Conventions for the definition of OS/ services.
3.3.3Session layer test management protocol data unit :
ISO/IEC 9646-l : 1994, Information technology - Open
a protocol data unit of the above defined protocol.
Systems Interconnection - Conformance testing
methodology and framework - Part I: General concepts. 3.3.4Repot-t test management protocol data unit: a
protocol data unit sent by the upper tester to report to the
lower tester the service primitive and associated received
by the UT.
1

---------------------- Page: 5 ----------------------
ISOAEC 10168-4 : 1996 (E) 0 ISO/lEC
SL-TMPDU explicitly designates the service
4 Symbols and abbreviations
primitive(s) to be issued.
The following abbreviations are used :
The SL-TMPDU also indicates the parameters to
ADDREF Additional reference information
be used in the service primitive.
CDADDPI Called Session Address Part 1
The SL-TMPDU also indicates what user data is
to be included in the service primitive (if
CDADDP2 Called Session Address Part 2
relevant). The user data forms an SL-TMPDU
sent by the UT to the LT.
CDADDP3 Called Session Address Part 3
CDSSREF Called SS user reference
CGADDPI Calling Session Address Part 1
CGADDP2 Calling Session Address Part 2
CGADDP3 Calling Session Address Part 3
CGSSREF Calling SS user reference
SL-TMPDU
COMREF Common reference
< ------------- >
CS Coordinated Single Layer test method
UPPER
ISERNUM Initial Serial Number
TESTER
TOKSET Initial Token Assignment
LOWER
LT Lower Tester
TESTER
New Activity identifier
NACTID
Old Activity identifier
OACTI D
-------------
PC0 Point of Control and Observation
REASON Reason
PC0
RESULT Result
RP-SL-TMPDU Report SL-TMPDU
TRANSPORT SERVICE
RSTYPE Resynchronization type
SERNUM Serial number
SL-TM P Session Layer Test Management Protocol of Test Management Protocol
Figure l- Description
SL-TMPDU Session Layer Test Management Protocol
Data Unit
SP Service Primitive
Additionally the expected reaction may be delayed : the
SQOS Session quality of service
upper tester maintains one FIFO queue of delayed
reactions associated with each existing connection and on
SYNCTYPE Synchronization type
receipt of a particular stimulus the UT shall issue in turn all
service primitives held in the queue associated with the
TLV Type, Length, Value
connection.
TMP Test Management Protocol
The UT shall be able to hold at least five reactions in each
TOKITEM Tokens (give/please)
FIFO queue.
USEREQ Functional Units
The TMP definition also defines the reaction expected from
the UT on receipt of a service primitive which cannot
UT Upper Tester
contain user data and cannot therefore carry any SL-
TMPDU (this is called implicit reaction).
5 Overview
The SL-TMP is based on the principle of parameterized
NOTES
echo : an SL-TMPDU is included in the user data parameter
of any SPDU which may contain user data.
I- The maximum length of the user data parameter of the
EXPEDITED DATA SPDU is only 14 bytes. That means that not all
This is used to dictate the behaviour of the SUT.
types of SL-TMPDUs can be included in the user data parameter of
the EXPEDITED DATA SPDU.
The echo is parameterized in the sense that :
%- Most of the primitives that “may not contain user data’” in
- The expected reaction is determined by the
Session version 1, may contain user data in Session version 2.
received SL-TMPDU. The expected reaction is in
However the implicit reaction that was used with version 1 for such
general to issue a service primitive: therefore the
primitives is still valid.
2

---------------------- Page: 6 ----------------------
0 ISOAEC ISOAEC 10168-4 : 1996 (E)
- the definition of the SL-TMPDU (see 7.3.1),
6 Service assumed from the Session IUT
- the coding of the SL-TMPDU (see 8.1).
6.1 General
b) then, if the SL-TMPDU is valid apply the
The service assumed is the service described in ISO/IEC
procedure defined in 7.3.3 (processing a valid
8326.
explicit reaction), otherwise apply the procedure
defined in 7.2 (implicit reaction).
6.2 Use of parameters by service primitives
Since the description of the SL-TMP makes reference to
7.3.1 Definition of SL-TMPDU sent by LT
parameters of service primitives, Table 1 summarizes which
parameters are supplied in the TMP for use by the UT.
There is only one SL-TMPDU sent by the LT and received
Parameters which are not given in the table for a specific
by the UT. This SL-TMPDU has the following parameters:
primitive are derived locally by the UT.
REACT/ON : This parameter indicates the name of the
service primitive(s) that the UT shall build.
7 Definition of the SL-TMP
DELAY : The value YES indicates that the service
7.1 General procedures
primitive(s) built according to REACTION is to be stored in
the FIFO queue associated with the connection.
a) On receipt of a service primitive which does not contain
user data the UT shall apply the procedures defined in 7.2
The value NO indicates that the SP(s) is to be passed
(implicit reaction).
immediately to the session entity.
b) On receipt of a service primitive which contains user data
RES-DAT-TYP: This parameter indicates how to build the
the UT shall apply the procedures defined in 7.3 (explicit
user data of the SP designed by the REACTION
reaction).
parameter :
c) Additionally the UT shall follow the rules given in 7.4 and
- NO means no user data,
7.5.
ECHO means echo the received user data (i.e.
the received SL-TMPDU),
7.2 Implicit reaction
REPORT means that a RP-SL-TMPDU shall be
When receiving a session service primitive which does not
built by the UT, which contains the name and
contain user data, the UT shall apply one of the following :
parameters of the received SP, and put as user
if the service primitive is an S-P-ABORT-
data of the SP built according to REACTION.
Indication or an negative S-CONNECT-Confirm
RES-PAR-VAL : This parameter consists of a series of TLV
with a result different from “by user”, destroy the
encoded fields, each of which corresponds to a parameter
FIFO queue associated with the connection ; or
of the SP to be built in accordance to the REACTION
parameter.
if the service primitive is either an S-P-
EXCEPTION-REPORT-Indication, S-TOKEN-
DATA : Contains transparent user data, up to the end of the
PLEASE-Indication, an S-ACTIVITY-
data field of the received SP.
INTERRUPT-Confirm or S-ACTIVITY-DISCARD-
Table 3 in 8.1 .I defines the possible values of the
Confirm, absorb the service primitive (i.e. do
REACTION parameter.
nothing) ; or
The following additional rules apply to the received SL-
if the service primitive is either a S-TOKEN-
TMPDU:
GIVE-Indication, S-CONTROL-GIVE-Indication,
S-ACTIVITY-INTERRUPT-Indication or S-
a) If REACTION is “Absorption of SP” or “Purge
ACTIVITY-DISCARD-Indication, the
apply
reactions memorized in FIFO”, all other
procedure defined in 7.3.2 (general procedure for
parameters have no significance and may take
executing the reactions memorized in the FIFO
any value.
queue).
b) If REACTION is “Execute reactions memorized in
if the service primitive is none of the above and
FIFO” the DELAY parameter shall be set to NO
the connection is still open :
and all other parameters have no significance
and may take any value.
i) destroy the FIFO queue associated with the
connection;
If REACTION is “Build S-DATA-Request and S-
C)
TOKEN-GIVE-Request” or “Build S-TYPED-
ii) issue an S-U-ABORT-Request service
DATA-Request and S-TOKEN-GIVE-Request” or
primitive without user data.
“Build S- EXPEDITED-Request and S-TOKEN-
GIVE-Request”, the RES-PAR-VAL parameter
7.3 Explicit reaction
may take any value and the token(s) to be used
After receiving a service primitive containing user data the
when building the S-TOKEN-GIVE- Request are
UT shall :
all available tokens.
check if the received user data represent a valid
a)
d) lf REACTION is “Build S-U-ABORT-Request and
SL-TMPDU sent by the LT. This checking is
S-CONNECT-Request” the RES-PAR-VAL
made in accordance to:
applies only to the S-CONNECT-Request
primitive and shall follow rule f) below for that SP.
3

---------------------- Page: 7 ----------------------
ISOAEC 10168-4 : 1996 (E) 0 ISOAEC
e) If REACTION is “Build S-CONNECT-Response
b) Otherwise the UT shall remove the SP at the
and S-TOKEN-PLEASE-Request” the RES-PAR- head of the FIFO queue and pass the SP to the
VAL applies first to the S-CONNECT-Response session service and :
primitive and then to the TOKEN-PLEASE-
if the service primitive was an S-CONNECT-
1)
Request service primitive and shall follow rule f)
Request, a new FIFO queue is created for the
below for each of them in turn. The RES-DAT-
new connection, the remaining content of the
TYP parameter applies to the expected S-
old FIFO queue is moved to the new FIFO
CONNECT-Response primitive, while the
queue, and the UT shall continue to execute
expected S-TOKEN-PLEASE-Request primitive
the procedure from 7.3.2.2 a) above for the
will contain no user data.
new connection; or
Otherwise the RES-PAR-VAL parameter shall
f )
if the service primitive passed to the session
2)
contain one field, TLV encoded, for each
service terminates the current connection (i.e.
parameter associated with the SP designated by
S-U-ABORT-Request or S-CONNECT-
REACTION and determined as follows :
Response with negative RESULT parameter
i) the name of the SP is used to determine the or S-RELEASE-Response and no S-
entry in table 1 to be used ; RELEASE-Confirm is still awaited) then :
ii) the entry gives the list of associated a) the UT shall test the head of the FIFO
parameters and the following rules apply to queue and,
this list:
b) if the head of the queue is an S-
- all parameters given in the list shall CONNECT-Request, then the UT shall
always be present unless the parameter is remove the S-CONNECT-Request from
conditional in ISO/IEC 8326. When the the head of the queue and pass it to the
parameter is conditional in ISO/IEC 8326, session service, create a new FIFO queue
it shall be omitted if its presence would associated with the new connection, move
cause the test responder to violate the the content of the old queue to the new
service specification, queue and destroy the old queue, and
then continue to execute the procedure
- they shall always be in the same order as
from 7.3.2.2 a) above; or
in the list,
c) othewise (the head does not content an
- for a given parameter the length shall be
S-CONNECT-Request primitive) the UT
as specified by table 4,
shall destroy the FIFO queue and
terminate the procedure.
- RES-PAR-VAL shall not include any extra
parameter, even with a null length.
if the service primitive passed to the session
3)
service does not belong to the categories
7.3.2 General procedure for executing the
defined in 1) and 2) above, the UT shall
in
reactions memorized in the FIFO queue continue to execute the procedure
7.3.2.2 a) above.
7.3.2.1 Use of this general procedure
7.3.3 Processing a valid explicit reaction
This general procedure is used in three cases :
When processing this reaction the UT shall do one of the
-
a) An S-TOKEN-GIVE-Indication, S-CONTROL-
following :
GIVE-Indication, S-ACTIVITY-INTERRUPT-
if the REACTION parameter of the received SL-
Indication or S-ACTIVITY-DISCARD-Indication is a)
TMPDU is “Absorption of SP” the UT shall follow
received (see 7.2 c) ; or
the procedure defined in 7.3.3.1 below; or
b) An “Execute reactions memorized in FIFO
b) if the REACTION parameter of the received SL-
queue” reaction is received, contained in a
TMPDU is “Execute reactions memorized in
service primitive which does not terminate the
FIFO” the UT shall follow the procedure defined
connection (see 7.3.3.2 b) ; or
in 7.3.3.2 below ; or
c) An “Execute reactions memorized in FIFO
if the REACTION parameter of the received SL-
queue” reaction is received, contained in a
C)
TMPDU is “Purge reactions memorized in FIFO”
service primitive which terminates the connection
the UT shall follow the procedure defined in
(see 7.3.3.2 c).
7.3.3.3 below ; or
NOTE - In cases a) and b) the procedure is entered from the
beginning, while in case c) the procedure is entered from
d) otherwise the UT shall follow the procedure
7.3.2.2.b)2)a) (since the current session connection does not exist
defined in 7.3.3.4 below.
any more).
7.3.2.2 Execution of this general procedure
When executing this procedure :
a) If the FIFO queue associated with the connection
is empty the UT shall terminate the procedure.
4

---------------------- Page: 8 ----------------------
ISO/IEC 10168-4 : 1996 (E)
0 ISOAEC
SERVICE PRIMITIVE NAME PARAMETERS SUPPLIED IN THE TMP
CGSSREF COMREF ADDREF
S-CONNECT-Request
ISERNUM TOKSET
USEREQ
CGADDPI CGADDP2 CGADDP3
CDADDPI CDADDP2 CDADDP3
SQOS
CDSSREF COMREF ADDREF
S-CONNECT-Response
ISERNUM TOKSET
USEREQ
CDADDPI CDADDP2 CDADDP3
SQOS RESULT
S-RELEASE-Request
RESULT
S-RELEASE-Response
S-U-ABORT-Request
S-DATA-Request
TOKITEM
S-TOKEN-GIVE-Request
S-TOKEN-PLEASE-Request-Request TOKITEM
S-EXPEDITED-DATA-Request
S-TYPED-DATA-Request
SYNCTYPE
S-MINOR-Request
S-MINOR-Response SERNUM
S-MAJOR-Request
S-MAJOR-Response
TOKSET RSTYPE SERNUM
S-RESYNC-Request
TOKSET SERNUM
S-RESYNC-Response
S-CAPABILITY-DATA-Request
S-CAPABILITY-DATA-Response
REASON
S-U-EXCEPTION-REPORT-Request
S-CONTROL-GIVE-Request
NACTI D
S-ACTIVITY-START-Request
CDSSREF CGSSREF COMREF
S-ACTIVITY-RESUME-Request
ADDREF
OACTI D
SERNUM
NACTID
S-ACTIVITY-END-Request
S-ACTIVITY-END-Response
REASON
S-ACTIVITY-INTERRUPT-Request
S-ACTIVITY-INTERRUPT-Response
REASON
S-ACTIVITY-DISCARD-Request
S-ACTIVITY-DISCARD-Response
Table 1 - Use of Parameters by primitives
“execute the reactions
7.3.3.1 Processing an “Absorption of SP” reaction 7.3.3.2 Processing an
memorized in the FIFO queue” reaction
When processing this reaction for a given received service
primitive on a given connection, the UT shall do one of the
When processing this reaction for a given received service
following :
primitive on a given connection, the UT shall do one of the
following :
if the received SP terminates the current
a)
connection (i.e. S-CONNECT-Confirm negative,
if the received SP is an S-CONNECT Indication,
a)
S-U-ABORT-Indication, S-P-ABORT-Indication or
the UT creates an empty FIFO queue for this
S-RELEASE-Confirm and no collision of release),
new connection ; or
the UT shall destroy the FIFO queue ; or
b) if the received service primitive terminates the
b) if the received SP is an S-CONNECT-Indication,
current connection (i.e. S-CONNECT-Response
the UT creates an empty FIFO queue for this
negative, S-U-ABORT-Indication, S-P-ABORT-
new connection ; or
Indication or S-RELEASE-Confirm and no
collision of release), the UT shall execute the
if the received SP does not belong to one of the
C)
procedure defined in 7.3.2.2 b)2)a); or
categories defined in a) or b) above, the UT
simply absorbs the SP (i.e. do nothing).
if the received SP does not belong to one of the
C)
categories defined in a) and b) above, the UT
shall execu%e %he procedure defined in 73.2
(general procedure for executing the reactions
memorized in the FIFO queue).
5

---------------------- Page: 9 ----------------------
0 ISOAEC
lSO/IEC 10168-4 : 1996 (E)
FIFO queue is created for this connection, the
7.3.3.3 Processing a “Purge reactions memorized
content of the queue associated with the
in the FIFO queue” reaction
current connection is moved to newly created
When processing this reaction for a given received service
FIFO queue and the old queue is destroyed ;
primitive on a given connection, the UT shall do one of the
b) if the received SP is an S-CONNECT-Indication,
following :
the UT shall create an empty FIFO queue
if the received service primitive terminates the
associated with that connection and then apply
a)
current connection (i.e. S-CONNECT-Confirm
the procedure defined in 7.3.3.4.2 c) below; or
negative, S-U-ABORT-Indication, S-P-ABORT-
otherwise (the received SP does not belong to
a
Indication or S-RELEASE-Confirm and no
one of the categories defined in a) and b), the UT
collision of release), the UT shall destroy the
shall :
FIFO queue associated with the connection (i.e.
remove the conten% of the queue and the queue
if the REACTION is such that it will terminate
1)
itself) ; or
the current connection, the responding
service primitive is built according to 7.3.4
b) otherwise, the UT shall remove the content of the
and passed to the session service and the
queue (the memorized reactions) and leave the
FIFO queue is destroyed ; or
queue empty.
if the REACTION is “Build an S-U-ABORT-
2)
7.3.3.4 Processing any other reaction Request and then an S-CONNECT-Request”,
an S-U-ABORT-Req
...