ISO/IEC 10168-1:1997

Information technology - Open Systems Interconnection - Conformance test suite for the Session protocol - Part 1: Test suite structure and test purposes

Technologies de l'information — Interconnexion de systèmes ouverts — Suite de tests de conformité pour le protocole de session — Partie 1: Structure de la suite de tests et objets des tests

General Information

• Status: Withdrawn
• Publication Date: 03-Dec-1997
• Withdrawal Date: 03-Dec-1997
• ICS: 35.100.50 - Session layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 18-Dec-2003
• Completion Date: 30-Oct-2025

Standards Content (Sample)

INTERNATIONAL
lSO/IEC
STANDARD 10168-I
First edition
1997-I 2-l 5
Information technology - Open Systems
Interconnection -
Conformance test suite
for the Session protocol -
Part I:
Test suite structure and test purposes
Technologies de I’informa tion
- lnterconnexion de syst&mes ouverts -
Suite de tests de conformit pour le protocole de session -
Partie 7: Structure de la suite de tests et objets des tests
Reference number
ISO/lEC 10168-I :I 997(E)
ISOAEC 101684 :1997(E)
Contents
vii
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .“.
. . .
VIII
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Scope .
2 Normative references .
3 .
Definitions
3.1 . 1
Reference model definitions
3.2 .
Service conventions definitions
3.3 . 2
Transport service definitions
3.4 Session service definitions . 2
3.5 Session protocol definitions .
3.6 . 2
Conformance testing methodology and framework definitions.
3.7 Session test suite structure and test purposes definition. .
4 Abbreviations .
4.1 Data units .
4.2 Types of Session protocol data units .
4.3 Types of Session service primitives .
4.4 Other abbrevations .
..................................................................................... 4
5 Compliance
....................................................................... 4
6 Testing methodology
6.1 Introduction .
............... 4
6.2 Relation ship between the TSS & TP and abstract test suites.
6.3 Test selection .
6.4 Verdicts .
.................................................................................. 4
6.5 Test suite coverage
7 Test suite structure . 4
8 Naming conventions . IO
9 Precedence . IO
10 Basic interconnection tests (IT) . IO
11 Capability tests (CA) . IO
11.1 . 10
CA/Functional units (FUN)
11 .I .I CA/FUN/Kernel (KER) .
11.1.2 . 11
CA/FUN/Negotiated release (NGR)
11.1.3 CA/FUN/Half-duplex (HDU) . 11
11.1.4 11
CA/FUN/Duplex (DUP) .
11.1.5 . 11
CA/FUN/Expedited data (EXD)
0 ISO/IEC 1997
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 l Case Postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
ISOAEC 10168-l : 1997(E)
.............................................................
11.1.6 CA/FU N/Typed data (TY D)
.......................................................
11.1.7 CA/FUN/Capability data (CAD)
...................................................
11.1.8 CA/FUN/Minor synchronize (MIN)
..................................................
11.1.9 CA/FUN/Major synchronize (MAJ)
CA/FUN/Resynchronize (RES) .
11.1.10
.............................................................
11 .I .I 1 CA/FUN/Exceptions (EXC)
CA/FUN/Activity management (AM) .
11.1.12
.............................................................
11.2 CA/Tokens management (TKM)
..................................................
11.3 CA/Serial number management (SNM)
...............................................................
11.4 CA/Basic concatenation (BCO)
........................................................
11.5 CA/Extended concatenation (ECO)
............................................................................
11.6 CA/Segmenting (SEG)
......................................................................
11.7 CWransport reuse (TRR)
CA/Transport expedited (TEX) .
11.8
................................................................
11.9 CA/Unlimited user data (UNL)
...................................................................
11.10 CA/Version negotiation (VN)
............................................................
12 Valid behaviour tests (BV)
................................................................................
12.1 BWState-event (SE)
...............................................................
12.1 .I BV/SE/State STAOI (001)
............................................................ 15
12.1.2 BV/SE/State STAOI A (01 A)
............................................................ 15
BV/SE/State STAOI B (01 B)
12.1.3
............................................................
12.1.4 BV/SE/State STAOI C (01 C)
............................................................ 15
12.1.5 BV/SE/State STAOI D (01 D)
............................................................ 15
12.1.6 BV/SE/State STA02A (02A)
............................................................
12.1.7 BV/SE/State STA02B (028)
............................................................... 16
12.1.8 BV/SE/State STA03 (003)
............................................................ 16
12.1.9 BV/SE/State STA04A (04A)
............................................................
12.1.10 BV/SE/State STA04B (048)
............................................................ 16
12.1.11 BVlSElState STA05A (05A)
............................................................ 16
12.1 .I2 BV/SE/State STA05B (05B)
............................................................
12.1.13 BV/SE/State STA05C (05C)
............................................................... 16
12.1 .I4 BV/SE/State STAOG (006)
...............................................................
12.1.15 BV/SE/State STA08 (008)
...............................................................
12.1.16 BV/SE/State STAOS (009)
............................................................
12.1.17 BVlSElState STAI OA (1 OA)
............................................................
12.1.18 BV/SE/State STAI OB (1 OB)
............................................................
12.1.19 BVlSElState STAI 1 A (11 A)
............................................................
12.1.20 BV/SE/State STAI 1 B (11 B)
............................................................
12.1.21 BV/SE/State STAI 1 C (11 C)
............................................................
12.1.22 BV/SE/State STAI 5A (15A)
............................................................
12.1.23 BV/SE/State STAI 5B (15B)
............................................................
12.1.24 BV/SE/State STAI 5C (15C)
............................................................ 18
BV/SE/State STAI 5D (150)
12.1.25
...............................................................
12.1.26 BV/SE/State STAI 6 (016)
...............................................................
12.1.27 BVlSElState STAI 8 (018)
............................................................... 18
BV/SE/State STAI 9 (019)
12.1.28
. . .
III
ISOAEC 101684 :1997(E)
0 ISOAEC
.............................................................. 18
12.1.29 BVlSElState STA20 (020)
.............................................................. 18
12.1.30 BVlSElState STA21 (021)
BV/SE/State STA22 (022) . 18
12.1.31
BV/SE/State STA713 (713) . 18
12.1.32
12.2 BWParameter variation (PV) . 19
12.2.1 BV/PV/Kernel (KER) . 19
12.2.2 BV/PV/Negotiated release (NGR) . 19
12.2.3 BV/PV/Half-duplex (HDU) . 19
12.2.4 BV/PV/Duplex (DUP) . 19
12.2.5 BWPWExpedited DATA (EXD) . 19
12.2.6 BV/PV/Typed data (TY D) . 19
12.2.7 BWPWCapability data (CAD) . 19
12.2.8 BV/PV/Minor synchronize (MIN) . 19
12.2.9 BV/PV/Major synchronize (MAJ) . 19
12.2.10 BV/PV/Resynchronize (RES) . 19
12.2.11 BWPWExceptions (EXC) . 20
12.2.12 BVlPVlActivity management (AM) . 20
13 Invalid behaviour tests (BI) . 20
13.1 Bl/lnopportune behaviour tests (INOP) . 20
13.1.1 BI/INOP/State STAOI (001) . 20
13.1.2 BI/INOP/State STAOI A (01 A) . 20
13.1.3 BI/INOP/State STAOI B (01 B) . 20
13.1.4 BI/INOP/State STAOI C (01 C) . 20
13.1.5 BI/INOP/State STAOI D (01 D) . 20
13.1.6 BI/INOP/State STA02A (02A) . 21
13.1.7 BI/INOP/State STA02B (02B) 21
.........................................................
13.1.8 21
BI/INOP/State STA03 (003) .
13.1.9 BI/INOP/State STA04A (04A) . 21
13.1.10 BI/INOP/State STAOIQB (04B) . 21
13.1 .I 1 BI/INOP/State STAOSA (05A) . 21
13.1.12 BI/INOP/State STAOSB (05B) . 21
13.1.13 BI/INOP/State STA05C (05C) . 21
13.1.14 BI/INOP/State STAOG (006) . 21
13.1.15 BI/INOP/State STA08 (008) . 22
13.1.16 BI/INOP/State STAOS (009) . 22
13.1.17 BI/INOP/State STAI OA (1 OA) . 22
13.1.18 BI/INOP/State STAI OB (1 OB) . 22
13.1.19 BI/INOP/State STAI 1 A (11 A) . 22
13.1.20 BI/INOP/State STAI 1 B (11 B) . 22
13.1.21 BI/INOP/state STAI 1 C (11 C) . 22
13.1.22 BI/INOP/state STAI 5A (15A) . 22
13.1.23 BI/INOP/State STAI 5B (15B) . 23
13.1.24 BI/INOP/State STAI 5C (15C) . 23
13.1.25 BI/INOP/State STAI 5D (15D) . 23
13.1.26 BI/INOP/State STAI 6 (016) . 23
13.1.27
BI/INOP/State STAI 8 (018) . 23

ISOAEC 101684 :1997(E)
0 ISOAEC
............................................................ 23
BI/INOP/State STAI 9 (019)
13.1.28
............................................................ 23
13.1.29 BI/INOP/State STA20 (020)
............................................................ 23
13.1.30 BI/INOP/State STA21 (021)
............................................................ 23
13.1.31 BI/INOP/State STA22 (022)
.......................................................... 24
13.1.32 BI/INOP/State STA713 (713)
........................................................... 24
13.2 BVSyntactically invalid test (SYN)
...................................................................... 24
13.2.1 -BI/SYN/Kernel (KER)
...................................................
13.2.1.1 BI/SYN/KER/Invalid AA (AA)
...................................................
13.2.1.2 BI/SYN/KER/Invalid AB (AB)
..................................................
13.2.1.3 BI/SYN/KER/Invalid AC (AC)
BI/SYN/KER/Invalid CD0 (CDO) .
13.2.1.4
..................................................
13.2.1.5 BI/SYN/KER/Invalid CN (CN)
..................................................
13.2.1.6 BI/SYN/KER/Invalid DN (DN)
...................................................
13.2.1.7 BI/SYN/KER/lnvalid FN (FN)
..................................................
13.2.1.8 BI/SYN/KER/Invalid OA (OA)
...................................................
13.2.1.9 BI/SYN/KER/Invalid RF (RF)
.................................................. 26
13.2.2 BI/SYN/Negotiated release (NGR)
..................................................
13.2.2.1 BI/SYN/NGR/Invalid NF (NF)
..............................................................
13.2.3 BI/SYN/Half-duplex (HDU)
.................................................. 26
BI/SYN/HDU/Invalid DT (DT)
13.2.3.1
..................................................
13.2.3.2 BI/SYN/HDU/Invalid GT (GT)
................................................... 26
BI/SYN/HDU/Invalid PT (PT)
13.2.3.3
BI/SYN/Duplex (DUP) .
13.2.4
................................................... 26
BI/SYN/DUP/lnvalid DT (DT)
13.2.4.1
......................................................... 26
BVSY N/Expedited data (EXD)
13.2.5
................................................... 26
13.2.5.1 BI/SYN/EXD/lnvalid EX (EX)
............................................................... 26
BI/SY N/Typed data (TY D)
13.2.6
........................................................... 27
13.2.6.1 BlnYD/Invalid TD (TD)
......................................................... 27
13.2.7 BI/SYN/Capability data (CAD)
.................................................. 27
13.2.7.1 BI/SYN/CAD/Invalid CD (CD)
............................................. 27
13.2.7.2 BI/SYN/CAD/Invalid CDA (CDA)
.................................................... 27
13.2.8 BI/SYN/Minor synchronize (MIN)
................................................
13.2.8.1 BI/SYN/MIN/Invalid MIA (MIA)
................................................
13.2.8.2 BI/SYN/MIN/lnvalid MIP (MIP)
....................................................
13.2.9 BVSY N/Major synchronize (MAJ)
.............................................
13.2.9.1 BI/SY N/MAJ/Invalid MAA (MAA)
.............................................
13.2.9.2 BI/SYN/MAJ/Invalid MAP (MAP)
.................................................. 28
13.2.9.3 BI/SYN/MAJ/Invalid PR (PR)
......................................................... 28
13.2.10 BI/SYN/Resynchronize (RES)
..................................................
13.2.10.1 BI/SYN/RES/Invalid PR (PR)
BI/SYN/RES/Invalid RA (RA) . 28
13.2.10.2
.................................................. 28
13.2.10.3 BI/SYN/RES/Invalid RS (RS)
...............................................................
13.2.11 BVSY N/Exceptions (EXC)
BI/SYN/EXC/Invalid ED (ED) . 28
13.2.11.1
BI/SYN/EXC/Invalid ER (ER) . 29
13.2.11.2
BI/SYN/Activity management (AM) .
13.2.12
0 ISOAEC
ISOAEC 10168-1 z-1 997(E)
13.2.12.1 BI/SYN/AM/Invalid AD (AD) .
............................................... 29
13.2.12.2 BI/SYN/AM/lnvalid ADA (ADA)
.................................................... 29
13.2.12.3 BI/SYN/AM/Invalid AE (AE)
............................................... 29
13.2.12.4 BI/SYN/AM/Invalid AEA (AEA)
....................................................... 30
13.2.12.5 BI/SYN/AM/lnvalid Al (Al)
13.2.12.6 BI/SYN/AM/lnvalid AIA (AIA) . 30
13.2.12.7 BI/SYN/AM/lnvalid AR (AR) . 30
13.2.12.8 BI/SYN/AM/lnvalid AS (AS) . 30
13.2.12.9 BI/SYN/AM/InvaIid GTA (GTA) . 30
13.2.12.10 . 30
BI/SYN/AM/lnvalid GTC (GTC)
13.2.12.11 BI/SYN/AM/Invalid PR (PR) . 30
13.3 BI/Semantically invalid tests (SEM) . 30
13.3.1 . 31
BI/SEM/Negotiated functional units (FUN)
13.3.2 BI/SEM/Tokens management (TKM) . 31
13.3.3 BI/SEM/Serial numbers management (SNM) . 31
13.3.4 BI/SEM/Use of Transport expedited flow (TEX) . 31
13.3.5 BI/SEM/Basic concatenations (BCO) . 31
13.3.6 Bl/SEM/Extended concatenations (ECO) . 32
13.3.7 BI/SEM/Segmenting (SEG) . 32
13.3.8 BI/SEM/Unlimited user data (UNL) . 32
13.3.9 BI/SEM/Version negotiation (VN) . 32
Annexes
A Test identifier structure and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B Clause references to ISO/IEC 8327-l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
vi
@ ISOAEC
ISOAEC 10168-l :1997(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide
standardization as a whole. 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. PSO 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, ISO/IEC JTCI. 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 ISO/IEC 10168-I was prepared by Joint Technical
Committee ISO/IEC JTCI, Information technology, Subcommittee SC21, @en
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
-
Part 4: Test management protocol specification
Annex A forms an integral part of this part of ISO/IEC 10168. Annex B is for
information only.
vii
ISOAEC 10168-l :1997(E) 0 ISOAEC
Introduction
This part of ISO/IEC 10168, a multipart International Standard, specifies a test suite
structure and a set of test purposes for use by test suite specifiers as the basis for
all standardized conformance test suites needed to evaluate conformance to
ISO/IEC 8327-1, the Session protocol.
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/I EC 8327- 1.
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:
test laboratories which provide a
conformance testing service for the
a)
Session protocol;
test real izers which provide a means of testing to be used such test
b) bY
laborato ries;
implementors of the Session protocol.
C>
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”
. . .
VIII
INTERNATIONAL STANDARD 0 ISOAEC lSO/IEC 10168=1:1997(E)
Information technology - Open Systems Interconnection -
Conformance test suite for the Session protocol -
Part 1 :
Test suite structure and test purposes
ISO/I EC 8327- 1: 1996, lnforma tion technology - Open
Interconnection - Connection-oriented Session
Systems
1 Scope
protocol: Protocol specification.
This part of lSO/IEC 10168 specifies a test suite structure
ISO/IEC 8327-2: 1996, Information technology - Open
and test purposes for the Session protocol, as defined in
Basic connection-oriented
Systems Interconnection -
ISO/IEC 8327-l except for the symmetric synchronize and
Session protocol: Protocol implementation Conformance
for the data separation functional units.
Statement (PICS) proforma.
This part of lSO/IEC 10168 does not specify how the
ISO/I EC 9646-l : 1994, Information technology - Open
conformance tests are to be realized or used, nor how the
Systems Interconnection - Conformance testing
test results are to be presented or used.
methodology and framework - Part I: General concepts.
This part of lSO/IEC 10168 applies to conformance test
PSOII EC 9646-2: 1995, Information technology - Open
suites for testing Session protocol implementations which
Systems Interconnection - Conformance testing
operate over a connection oriented Transport service (IS0
methodology and framework - Pall 2: Abstract Test Suite
8072) and which claim conformance to ISO/IEC 8327-l.
specification.
NOTE - The choice of test method may restrict the test purposes
which can be realised.
ISOII EC 10731: 1994, Information technology - Open
Systems Interconnection - Basic Reference Model -
This part of ISO/IEC 10168 does not include a general
Conventions for the definitjon of OS/ services.
assessment of performance, reliability or robustness of
relevant protocol implementations, nor an assessment of
3 Definitions
the design of the protocol itself.
For the purposes of this part of ISO/IEC 10168, the
2 Normative references
following definitions apply.
The following standards contain provisions which, through
Reference model definitions
3.1
reference in this text, constitute provisions of this part of
ISO/IEC 10168. At the time of publication, the editions This part of ISO/IEC 10168 uses the following terms defined
indicated were valid. All standards are subject to revision, in lSO/IEC 7498-l:
and parties to agreements based on this part of ISO/IEC
session-connection;
a)
10168 are encouraged to investigate the possibility of
applying the most recent editions of the standards indicated
session layer;
W
below. Members of IEC and IS0 maintain registers of
session-protocol-data-unit;
currently valid International Standards. c j
session-service;
d)
I SO/I EC 7498-l : 1994, Information technology - Open
Systems Interconnection - Basic Reference Model: The
session-service-access-point;
e)
5asic Model.
session-service-data-unit;
f j
I SO 7498-3: 1989’) Information processing systems - Open
Systems Interconnection - Basic Reference Model - transport Layer;
9)
Part”3 Naming and addressing.
transport-service;
I SO/I EC 8072: 1996, Information technology - Open
transport-service-access-point;
Systems Interconnection - Transport service definition.
concatenation;
k>
ISO/I EC 8326: 1996, Information technology - Open
Systems Interconnection - Session service definition.
segmenting.
1)
1 To be published.
ISOhEC 10168-l :I 997(E)
0 ISOAEC
negotiation;
3.2 Service conventions definitions
k)
selected parameter;
This part of ISOAEC 10168 uses the following terms defined
Ii
in ISOAEC 10731:
m) valid SPDU;
service-provider;
a>
invalid SPDU;
n)
b) service-user;
protocol error;
0)
primitive;
Ci
transparent (data);
P)
request (primitive);
d)
SPDU identifier (SI);
4)
indication (primitive);
ei
length indicator (LI);
r i
response (primitive);
f )
parameter field;
Si
g) confirm (primitive).
parameter identifier (PI);
3.3 Transport service definitions
PI unit;
Ui
This part of ISOAEC 10168 uses the following terms defined
parameter group identifier (PGI);
vi
in ISOAEC 8072:
PGI unit;
w)
calling transport service user;
ai
y) parameter value (PV);
called transport service user;
b)
local variable.
Zi
sending transport service user;
C)
3.6 Conformance testing methodology and
receiving transport service user.
di
framework definitions
3.4 Session service definitions
This part of ISOAEC 10168 uses the following terms defined
in ISOAEC 9646-l and ISOAEC 9646-2:
This part of ISO/IEC 10168 uses the following terms defined
in ISOAEC 8326:
basic interconnection testing;
ai
calling SS-user;
behaviour testing;
bi
b) called SS-user;
capabilities of an IUT;
Ci
sending SS-user;
Cl
capability testing;
di
receiving SS-user;
co
conformance testing;
e)
requestor; requesting SS-user;
ei
conformance test suite;
f i
acceptor; accepting SS-user;
dynamic conformance requirements;
9)
g) token;
implementation under test (IUT);
l-0
conditional (parameter);
hi
inopportune test event;
.
proposed parameter;
ii
lower tester;
I)
selected parameter.
.ii
PIGS proforma;
W
3.5 Session protocol definitions protocol implementation conformance statement
1)
(PIGS);
This part of ISO/IEC 10168 uses the following terms defined
in ISOAEC 8327-l: static conformance requirements;
m>
Session Protocol Machine (SPM); syntactically invalid test event;
n)
ai
system under test (SUT);
session-service-user (SS-user); o)
bi
transport-service-provider (TS provider); p) test group;
Ci
local matter; q) test purpose;
d)
test suite.
initiator;
e) 0
responder;
f i
3.7 Session test suite structure and test
purposes definition
sending SPM;
9)
receiving SPM; For the purposes of this part of ISOAEC 10168, the
hi
following definitions also apply.
owner (of a token);
ii
proposed parameter;
ji
ISO/IEC 10168-l :1997(E)
0 ISOAEC
S-ACTIVITY-INTERRUPT indication primitive
SACTlind
3.7.1 inopportune parameter: A parameter whose PGP
S-ACTIVITY-INTERRUPT request primitive
SACTI req
or PI current value is defined in ISO/IEC 8327-l) but which
S-ACTIVITY-INTERRUPT response primitive
SACTl rsp
occurs in a SPDU which is not allowed.
S-ACTIVITY-RESUME indication primitive
SACTRind
3.7.2 unknown parameter: A parameter whose PGl or PI
S-ACTIVITY-RESUME request primitive
SACTRreq
current value is not defined in ISO/IEC 8327-l.
S-ACTIVITY-START indication primitive
SACTSind
S-ACTIVITY-START request primitive
SACTSreq
3.7.3 mislaid parameter: A parameter which does not
S-CAPABILITY-DATA confirm primitive
SCDcnf
appear in the order defined in ISO/IEC 8327-l for a
S-CAPABILITY-DATA indications primitive
SCDind
particular SPDU.
S-CAPABILITY-DATA request primitive
SCDreq
S-CAPABILITY-DATA response primitive
SCDrsp
4 Abbreviations
S-CONTROL-GIVE indication primitive
SCGind
S-CONTROL-GIVE request primitive
SCGreq
4.1 Data units
S-CONNECT confirm primitive
SCONcnf
SCONind S-CONNECT indication primitive
SPDU Session Protocol Data Unit
SCONreq S-CONNECT request primitive
SSDU Session Service Data Unit
SCON rsp S-CONNECT response primitive
TSDU Transport Service Data Unit
SDTind S-DATA indication primitive
SDTreq S-DATA request primitive
4.2 Types of Session protocol data units
SEXind S-EXPEDITED-DATA indication primitive
ABORT ACCEPT SPDU
AA SEXreq S-EXPEDITED-DATA request primitive
AB ABORT SPDU
SGTind S-TOKEN-GIVE indication primitive
ACCEPT SPDU
AC S-TOKEN-GIVE request primitive
SGTreq
AD ACTIVITY DISCARD SPDU
SPABind S-P-ABORT Indication primitive
ADA ACTIVITY DISCARD ACK SPDU
SPERind S-P-EXCEPTION-REPORT indication
AE ACTIVITY END SPDU
primitive
AEA ACTIVITY END ACK SPDU S-TOKEN-PLEASE indication primitive
SPTind
Al ACTIVITY INTERRUPT SPDU
SPTreq S-TOKEN-PLEASE request primitive
AIA ACTIVITY INTERRUPT ACK SPDU
SRELcnf S-RELEASE confirm primitive
AR ACTIVITY RESUME SPDU S-RELEASE indication primitive
SRELind
AS ACTIVITY START SPDU
SRELreq S-RELEASE request primitive
CD CAPABILITY DATA SPDU S-RELEASE response primitive
SRELrsp
CDA CAPABILITY DATA ACK SPDU S-RESYNCHRONIZE confirm primitive
SRSYNcnf
CD0 CONNECT DATA OVERFLOW SPDU S-RESYNCHRONIZE indication primitive
SRSYNind
CN CONNECT SPDU S-RESYNCHRONIZE request primitive
SRSYNreq
DISCONNECT SPDU
DN SRSYNrsp S-RESYNCHRONIZE response primitive
DT DATATRASFERSPDU S-RESYNCHRONIZE confirm primitive
SRSYNcnf
EXCEPTION DATA SPDU
ED SRSYNind S-RESYNCHRONIZE indication primitive
EXCEPTION REPORT SPDU
ER SRSYNreq S-RESYNCHRONIZE request primitive
EXPEDITED SPDU
EX SRSYNrsp S-RESYNCHRONIZE response primitive
FINISH SPDU
FN SSYNMcnf S-SYNC-MAJOR confirm primitive
GIVE TOKENS SPDU
GT SSYNMind S-SYNC-MAJOR indication primitive
GIVE TOKENS ACK SPDU
GTA SSYNMreq S-SYNC-MAJOR request primitive
GIVE TOKENS CONFIRM SPDU
GTC SSYNMrsp S-SYNC-MAJOR response primitive
MAJOR SYNC ACK SPDU
MAA SSYNmcnf S-SYNC-MINOR confirm primitive
MAJOR SYNC POINT SPDU
MAP SSYNmind S-SYNC-MINOR indication primitive
MINOR SYNC ACK SPDU
MIA SSYNmreq S-SYNC-MINOR request primitive
MINOR SYNC POINT SPDU
MIP SSYNmrsp S-SYNC-MINOR response primitive
NOT FINISHED SPDU
NF STDind S-TYPED-DATA indication primitive
OVERFLOW ACCEPT SPDU
OA STDreq S-TYPED-DATA request primitive
PR PREPARE SPDU
SUABind S-U-ABORT indication primitive
PLEASE TOKENS SPDU
PT SUABreq S-U-ABORT request primitive
RA RESYNCHRONIZE ACK SPDU
SUERind S-U-EXCEPTION-REPORT indication
RF REFUSE SPDU
primitive
RESYNCHRONIZE SPDU
RS SUERreq S-U-EXCEPTION-REPORT request primitive
TD TYPED DATA SPDU
4.4 Other abbreviations
Types of Session service primitives
4.3
Activity management functional unit
ACT
V TY-DISCARD confirm primitive
SACTDcnf S-ACT Capability data exchange functional unit
CAD
S-ACT V TY-DISCARD indication primitive
SACTDind EXD Expedited data functional unit
TY-DISCARD request primitive
SACTDreq S-ACT V EXCEP Exception functional unit
V TY-DISCARD response primitive
SACTDrsp S-ACT FD Duplex functional unit
S-ACT V TY-END confirm primitive
SACTEcnf True if and only if the functional unit f has
Wfi
V TY-END indication primitive
SACTEind S-ACT been selected during the Session connection
S-ACT V TV-END request primitive
SACTEreq establishment phase.
SACTErsp S-ACT iV TY-END response primitive
HD Half duplex functional unit
S-ACT IV TY-INTERRUPT confirm primitive
SACTlcnf IUT Implementation Under Test

ISOAEC 10168~1:1997( E)
0 ISOAEC
LT Lower Tester 10168, providing this is in compliance with ISO/IEC 9646-2,
MA clause IO.
Major synchronize functional unit
NR Negotiated release functional unit
6.3 Test selection
OSI Open Systems Interconnection
PIGS Protocol Implementation Conformance
The structure of the test suite is organized to make possible
Statement
the selection of the appropriate test cases according to the
RESYN Resynchronize functional unit
contents of the PICS.
SY
Minor synchronize functional unit
TD
Typed data functional unit NOTE - If a PIGS shows that a mandatory feature is omitted, the
TIM test cases related to that feature are not executed; the
Disconnection and abort timer
conformance test report indicates clearly any such instances of
dk
Data token
non-conformance.
mi
Minor synchronize token
ma
Major/activity token
6.4 Verdicts
tr
Release token
True if and only if the token t is available
w i
Verdicts assigned by each abstract test case are
TSS & TP
Test suite structure and test purposes
determined on the basis of the IUT’s ability to behave in
TTCN
Tree and tabular combined notation
accordance with the requirements of the Session protocol,
and to support the capabilities and parameter values listed
5 Compliance
in the PICS. Conformance assessment is based on the
individual verdicts, the Session protocol standard, and the
A generic or abstract test suite which complies with this part
IUT’s PICS.
of ISO/IEC 10168 shall:
65 . Test suite coverage
a) consist of a set of test casescorresponding to the
set or a subset of the test purposes specified in
Test purposes are specified and structured according to
clauses 11 to 13;
ISO/IEC 9646-2, 10.2 (test group structure) and 10.3 (test
purposes) to obtain the appropriate coverage of possible
b) identify clearly the test purposes used;
state/event, parameter values, and valid/invalid variations.
c) cover all the relevant test purposes specified in
clauses 11 to 13, as appropriate to the coverage and
7 Test suite structure
test method chosen for that test suite;
The test suite for the Session protocol consists of test
d) use a test suite structure which is an appropriate
groups and test cases. Each test case has a narrowly
subset (or the whole) of the test suite structure
defined purpose. Within the test suite, nested test groups
specified in clause7;
are used to provide a logical ordering of the test cases. Test
groups may be nested to an arbitrary depth. They may be
e) name its test groups and test cases using the
naming conventions specified in clause 8 in such a used to aid planning, development, understanding or
way that the test group and test case names used in execution of a test suite.
clauses 11 to 13 are used whenever relevant;
The test suite consists of three main test groups:
f) maintain the relationships specified in clauses 11 to
a) Capability Tests, which are used to verify that the
13 between the chosen test purposes and the entries
capabilities of
observable Session protocol
in the PIGS proforma to be used for test case
implementations are valid with respect to the static
selection;
conformance requirements stated in ISO/IEC 8327-1,
clause 9, the Session protocol specification and with
g) comply with lSO/IEC 9646-2 .
respect to the PICS.
6 Testing methodology
b) Valid Behaviour Tests, which test the extent to
which the implementation
meets the dynamic
6.1 Introduction
conformance requirements specified in ISO/I EC 8327-
I, subclause 9.3.d and 9.3.e, the Session protocol
The testing methodology used in this part of ISO/IEC 10168
specification when the tester behaves in a valid
complies with the requirements of ISO/IEC 9646-2.
manner. These tests provide a detailed evaluation of
the features which are claimed to be supported in the
6.2 Relation ship between the TSS & TP and
PIGS.
abstract test suites
c) Invalid Behaviour Tests, which test the extent to
The test purposes in this part of ISO/IEC 10168 have been
which the implementation meets the dynamic
derived from llSO/IEC 8327-l, the Session protocol
conformance requirements specified in ISO/I EC 8327-
standard. This derivation has focused on identifying test
I, subclause 9.3.f, the Session protocol specification
purposes to test conformance aspects of the protocol.
when the sends tests events which violate at least one
However, no consideration has been given to any test
conformance requirement of ISO/IEC 8327-l. This
method, how such test purposes may be realized, or any
group of tests may be sub-divided into
practical or economic constraints may be placed upon
testing.
1) Syntactically Invalid Tests, where the tester sends
tests evens where the PDU syntax is not allowed by
It is intended that all test suites for the Session protocol
liSO/I EC 8327- 1.
shall include tests for all the test purposes in this part of
ISO/IEC 10168, however, an abstract test suite specifier
may subset the test purposes given in this part of ISO/IEC
ISOAEC 10168-I :I 997(E)
0 ISOAEC
2) Semantically Invalid Tests, where the tester sends
tests evens where semantics is not consistent with
that allowed by ISOAEC 8327-l.
3) Inopportune Tests, where the tester generates
test events which occur when they are not allowed to
by ISO/IEC 8327-l.
Each of these groups are further divided into a number of
lower level test groups. The structure of the Session test
suite is shown in figure 1 and the other figures reference
therein.
NOTE - The numbers shown in parentheses after each item in the
tree refer to the clauses of this part of ISO/IEC 10168 where the
test group and test purposes may be found.

ISOAEC 10168-I :I 997(E) 0 ISOAEC
-k--
Functional units (11 .I) _ dig 2
*
- - Token management (11.2)
+--
Serial number management (11.3)
+-- Basic concatenation (11.4)
+-- Capability - - - + - - Extended concatenation (11.5)
tests (11) +-- Segmenting (11.6)
+ - - Transport reuse (11.7)
+-- Transport expedited (11.8)
+ - - Unlimited user data (11.9)
+-- Version negotiation (11 .I 0)
I
Session Valid +-- State-event (12.1) _ fig 3
I
-- -+--
test behaviour --- i
suite tests (12) +-- Parameter variation (12.2) _ fig 4
I
B
-I--- Inopportune tests (13.1) _ fig.5
I
Invalid
I I
+-- behaviour ---+-- Syntactically invalid tests( 13.2) _ fig.6
I
tests (13)
I
+-- Semantically invalid tests (13.3) _ fig.7
Figure 1 - Session test suite structure
+--
Kernel (11 .I .I)
+--
Negotiated release (11.1.2)
+
- - Half-duplex (11 .I .3)
+--
Duplex (11.1.4)
+
- - Expedited data (11 .I 5)
+--
Typed data (11.1.6)
Functional units (11.1) - - - + - - Capability data (11.1.7)
+--
Minor synchronize (11 .I .8)
-I---
Major synchronize (11.1.9)
+--
Resynchronize (11.1.10)
+--
Exceptions (11.1~11)
-I-
- - Activity management (I 1. I. 12)
Figure 2 - Functional units capability tests
lSO/IEC 10168-I :I 997(E)
0 ISOAEC
+--
STAOI (12.1.1)
+--
STAOIA (12.1.2)
+--
STAOIB (12.1.3)
+-- STAOIC (12.1.4)
-I---
STAOID (12.15)
+--
STA02A (12.1.6)
+--
STA02B (12.1.7)
+--
STA03 (12.1.8)
+--
STA04A (12.1.9)
+--
STAO4B (12.1.10)
+--
STAO5A (12.1.11)
+
-- STA05B (12.1.12)
+--
STAOSC (12.1.13)
+
-- STAOG (12.1.14)
+--
STA08 (12.1.15)
+--
STAOS (12.1.16)
-- -+--
STA1OA(12.1.17)
State-event(12.1)
+-- STAIOB (12.1.18)
+-- STA11A(12.1.19)
+ -- STAIIB (12.1.20)
+-- STA11C(12.1.21)
+-- STAISA (12.1.22)
+ -- STA15B(12.1.23)
+-- STA15C (12.1.24)
+-- STA15D (12.1.25)
+-- STA16 (12.1.26)
+-- STA18 (12.1.27)
4--- STA19 (12.1.28)
+ -- STA20 (12.1.29)
+ -- STA21 (12.1.30)
-I---
STA22 (12.1.31)
+--
STA713(12.1.32)
Figure 3 - State-event valid behaviour tests

0 ISOIIEC
ISOAEC 10168=1:1997(E)
+--
Kernel (12.2.1)
+--
Negotiated release (12.2.2)
+--
Half-duplex (I 2.2.3)
+--
Duplex (12.2.4)
+--
Expedited data (12.2.5)
Parameter variation - - - * - - Typed data (12.2.6)
+--
Capability data (12.2.7)
(12.2)
+--
Minor synchronize (12.2.8)
+--
Major synchronize (12.2.9)
+--
Resynchronize (12.2.10)
*--
Exceptions (12.2.11)
*--
Activity management (12.2.12)
Figure 4 - Parameter variation valid behaviour tests
+-- STAOI (13.11)
+-- STAOIA (13.2)
+-- STAOIB (13.3)
+-- STAOIC (13.4)
+-- STAOID (13.1.5)
+-- STA02A (13.1.6)
-I- -- STA02B (13.1.7)
+-- STA03 ( 13.1.8)
+-- STA04A (13.1.9)
+ -- STA04B (13.1.10)
+-- STA05A (13.1.11)
+-- STA05B (13.1.12)
+ -- STAOSC (13.1.13)
+-- STAOG ( 13.1.14)
+-- STA08 ( 13.1.15)
Inopportune behaviour - - -+ - - STAOS ( 13.1.16)
+-- STAI OA (13.1.17)
tests (13.1)
+-- STAI OB (13.1.18)
+-- STAI IA (13.1.19)
+-- STAI 1 B (13.1.20)
+-- STAIIC (13.1.21)
-+--- STAI 5A (13.1.22)
+-- STA15B (13.1.23)
+-- STAI 5C (13.1.24)
+-- STAI 5D (13.1.25)
+-- STA16 (13.1.26)
+--
STA18 (13.1.27)
+-- STA19 (13.1.28)
+--
STA20 (13.1.29)
+--
STA21 (13.1.30)
+--
STA22 (13.1.31)
+--
STA713 (13.1.32)
Figure 5 - Inopportune behaviour tests
ISOAEC 101684 :1997(E)
0 ISOAEC
*---
Kernel (13.21)
+--
Negotiated release (13.2.2)
4---
Hal%-duplex (13.2.3)
+--
Duplex (13.2.4)
+--
Expedited data (13.25)
Syntactically invalid - - - + - - Typed data (13.2.6)
+--
tests (13.2) Capability data (13.2.7)
+
- - Minor synchronize (13.2.8)
+--
Major synchronize (13.2.9)
+--
Resynchronize (13.2. IO)
+--
Exceptions (13.2.11)
+--
Activity management (13.2.12)
Figure 6 - Syntactically invalid behaviour tests
-!---
Negotiated release (13.3.1)
* - - Tokens management
+
- - Serial number management (13.3
...