ISO/IEC 8882-3:1991

Information technology - Telecommunications and information exchange between systems - X.25-DTE conformance testing - Part 3: Packet level conformance test suite

Technologies de l'information — Télécommunications et échange d'informations entre systèmes — Tests de conformité à X.25 des ETTD — Partie 3: Suite de tests de conformité pour le niveau paquet

General Information

• Status: Withdrawn
• Publication Date: 11-Dec-1991
• Withdrawal Date: 11-Dec-1991
• ICS: 35.100.30 - Network layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 21-Dec-1995
• Completion Date: 30-Oct-2025

Relations

• Revised: ISO/IEC 8882-3:1995 - Information technology - Telecommunications and information exchange between systems - X.25 DTE conformance testing - Part 3: Packet layer conformance test suite
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTER NATIONAL
ISO/IEC
STANDARD
First edition
1991-12-01
I n f o r ma t i o n te c h no Io g y - Te I eco m m u n i cations
and information exchange between systems -
X.25-DTE conformance testing -
Part 3:
Packet layer conformance test suite
Technologies de l'information - Télécommunications et échange d'informations
entre systèmes - Tests de conformité à X.25 des ETTD -
Partie 3: Suite de tests de conformité pour le niveau paquet
Reference number
ISO/IEC 8882-3 : 1991 (E)
ISO/IEC 8882-3 : 1991 (E)
Con tents Page
...
Foreword . 111
Introduction . iv
1 Scope . 1
2 Normative references . 1
3 Definitions . 2
3.1 Reference model definitions . 2
3.2 Conformance testing definitions . 2
3.3 X.25-DTE conformance testing definitions . 2
3.4 Additional definitions . 2
4 Abbreviations . 3
5 Conformance . 3
6 Test suite information . 3
6.1 Packet layer test suite structure . 3
6.2 Packet layer initialization . 4
6.3 DE-initiated actions . 6
6.4 Timer definitions . 6
6.5 Cause codes and diagnostic codes . 6
6.6 Data transfer states . 7
................................................................................ 7
6.7 Other user data fields
6.8 Transient states . 7
6.9 Relationship of PICS to test suite . 7
6.10 Relationship of PIXIT to test suite . 7
6.11 PIXIT proforma . 8
6.12 Acceptable unexpected responses . 23
6.13 Implicit send . 23
6.14 Basic interconnection tests . 23
7 TTCN abstract test suite . 25
8 Use of the PICS and PIXIT based abstract test selection rules . 550
8.1 Packet layer group selection based on service . 550
Annëk A Test summary tables . 678
O ISO/IEC 1991
All rights reserved . 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 .
ISOAEC Copyright Office 0 Case postale 56 0 CH-1211 Genève 20 0 Switzerland
Printed in Switzerland
ii
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardiz-
ation. National bodies that are members of IS0 or IEC participate in the development
of international Standards through technical committees 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, ISO/IEC JTC I. 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 Yo of the national. bodies
casting a vote.
international Standard ISO/IEC 8882-3 was prepared by Joint Technical Committee
ISO/IEC JTC I, Information technology.
ISO/IEC 8882 consists of the following parts, under the general title Information
technology - Telecommunications ana' in formation exchange between systems -
X.2.i-DTE conformance testing
- Part I : General principles
- Part 2: Data link layer test suite
- Part 3: Packet layer conformance test suite
Annex A forms an integral part of this part of ISO/IEC 8882.
iii
Introduction
This part of ISO/lEC 8882 specifies a set of tests to cvaluate Data Terminal Equipment (DTE) conformance to
International Standards IS0 7776 (X.25 LAPB) and/or IS0 8208 (X.25 Packet Layer). IS0 7776 and IS0 8208 allow
for a DTE to interface with a Data Circuit-Terminating Equipment (DCE) conforming to CCITï Recommendation
X.25 or to another DTE conforming to IS0 7776 and/or IS0 8208. IS0 8208 also allows for connection to Local Area
Networks.
CCITT Recommendation X.25 1980 and X.25 1984 are written from the perspective of a DCE and therefore do not
explicitly specify the DTE operation. Howcvcr, rccomincndcd operation of DES is included by implication because
of the need to communicate with X.25 DCEs. Tests within this part of ISO/IEC 8882 pertaining to X.25 1980 and X.25
1984 are based on the DTE operational characteristics implied by CCITT X.25.
This part of ISODEC 8882 presents thc packct inycr aspects for evaluating conïormance to IS0 8208 and follows the
procedures and guidclines de fincd in ISODEC 9646.
Where it is claimed that X.25 is used to provide the OS1 Network Layer Service, the conformance tests as defined in
this part of ISO/IEC 8882 can bc used to verify the implcrncntation ol' the necessary protocol elements.
The test suite is presented in an abstract form by means of the test case notation TTCN, as defined in ISO/IEC 9646-
3. This is an abstract set of tats not evcry test applies to cvery public network or every type of DTE.

ISOAEC 8882-3 : 1991 (E)
INTERNATIONAL STANDARD
Information technology - Telecommunications and
information exchange between systems - X.25-DTE
conformance testing -
Part 3:
Packet layer conformance test suite
of ISO/IEC 8882 are encouraged to investigate the
1 Scope
possibility of applying the most recent editions of the
standards indicated below. Members of IEC and IS0
This International Standard specifies a set of abstract
mainlain registers of currently valid International
tests for verifying that the implementation of X.25
Standards.
protocols, for use by Data Terminal Equipment (DTE),
conform to the requirements of International Standards
IS0 7498 : 1984, Information processing systems -
that specify those protocols.
Open Systems Interconnection - Basic Reference
This International Standard Model.
a) specilies a PIXIT proforma; IS0 7776 : 1986, Information processing systems -
Datu communicalions - High-level data link control
procedures - Description of the X.25 LAPB-compatible
b) describes the relationship of the PICS to the tesi
OTE data link procedures.
suite;
describes the relationship of the PIXIT to the ISO/IEC 8208 : 1990, Information technology -
c)
Daia communications - X.25 Packet layer Proiocol
test suite;
for Data Terminal Equipment.
d) specifies a set of abstract tcsts using TTCN
ISO/IEC 8208/Aind. 3 : 1991, Information technology
Graphical notation.
- Duiu cornununkations - X.25 Packet Layer Protocol
This part of ISO/IEC 8882 defines the testing of a DTE for Data Terminal Equipment
3: Conformance requirements.
operating at the packet layer designed to access a public Addendum
or private packet-switched network conforming io
CCITT Recommendation X.25 (1980, 1984) or another
ISO/IEC 8882-1 : -'), Information technology -
DTE conforming to IS0 820X.Thc spcci fication of test
ïklecornmunicnlions and information exchange between
cases in executable/inachinc proccssablc TTCN is
xysteiris - X.25 DE conformance testing
outside the scope of this part of ISO/IEC 8882.
Part I : General principles.
2 Normative references
ISO/IEC 0646-1 : 1991 'I, Information technology -
Oprn Syslerris ln~erconnccîion - Conformance testing
The following standards contain provisions which,
inelllodology und fruinework -
through reference in this text, constitute provisions of
Puri I : Generui concepts.
this part of ISO/IEC 8882. At the tiiiic of publicution, the
editions indicated wcrc valid. All slandards arc subjcct
to revision, and partics to agrccincnls bascd on this part
1) To bc published.
ISOAEC 8882-3 : 1991 (E)
d) ConTorinancc Testing
ISO/IEC 9646-2 : 1991 I), Informution technology -
Open Systems Interconnection - Confortnance iesling
e) Executable Test Suite
methodology and framework -
Part 2: Abstract tes1 suite specificution.
1) Postamble.
ISODEC DIS 9646-3 : 1991 I), lnformalion iechnology
g) Preamble
- Open Systems Interconneclion - Conformurice
testing methodology and framework -
h) Protocol Implementation Conformance
Part 3: Tree and tabular combined notation.
Statcmcnt
ISO/IEC 9646-4 : 1991 'I, Informalion technology -
Protocol Implcmentation eXua Information for
i)
Open Systems Interconnection - Conformance iesting
Testing
methodology and framework -
Part 4: Test realization.
j) Test Group
ISO/IEC 9646-5 : 1991 I), Informulion leclznology -
k) Tcst Step
Open Systems Interconneclion - Corforrnunce testing
methodology and framework -
1) Tcst Suitc
Part 5: Requirements on lest laborarorics und clienlsjor
the conformance assessment process.
3.3 X.75-DTE conformance testing definitions
CCITT Recommcndation X.25 (1 980), Interfuce
This part of ISO/IEC 8882 makes use of the following
between Daia Terminal Equipment (DE) and Datu
in ISOBEC 8882-1.
tcrms defined
Circuit-Terminating Equipment (DCE) for Terminuls
Operating in the Packet Mode on Public Datu Nelworks.
a) Impropcr PDU
CCITT Recommendation X.25 ( I984), Intufuce
b) Inopportune PDU
between Data Terminal Equipmenr (DYE) and Dnia
Circuit-Terminating Equi@rient (DCE) for Y7errriinul.s
c) Proper PDU
Operating in the Packel Mode and Conneclcd 10 Public
Data Networks by Dedicaled Circuit.
(i) Tcst Subgroup
3 Definitions
c) Test Selection
3.1 Reference model definitions
1) Tcstcr
This part of ISODEC 8882 makes usc of the following
g) Transient States.
term defined in IS0 7498.
3.4 Additional definitions
(N)-protocol-data-unit (N-PDU)
For thc purposcs of this part of ISOIIEC 8882, the
3.2 Conformance testing definitions
following definitions apply.
This part of ISO/IEC 8882 makes usc of thc following
3.4.1 proper packet
terms defined in ISO/IEC 9636.
A packct that is a propcr PDU.
a) Abstract Test Suitc
3.4.2 improper packet
b) Conforming Systcm or Implcmcntiition
A packct that is an imptopcr PDU.
c) Conformance Tcst Suite
3.4.3 inopportune packet
ISO/IEC 8882-3 : 1991 (E)
PIXIT Protocol Implementation extra Information for
A packet that is an inopportune PDU.
Testing
4 Abbreviations
PKT Packet
The following abbreviations are used in this part of IS@
PLG Packct Layer Group
IEC 8882:
RX Receivc
ADX Address
TST Tcster
ATS Abstract Test Sute
ETS Executable Test Suite TX Transmit
UDF User Data Ficld
FAC Facility
5 Conformance
IUT Implementation Under Test
The test realizer shall comply with the requirements of
LCI Logical Channel Identifier
ISO/lEC 9646-4. In particular, these concern the
realization of an ETS based on the ATS. Test
LEN Length
laboratorics running conformance test services for this
PCO Point of Control and Observation abstract test suite shall comply with ISODEC 9646-5.
6 Test suite information
PDU Protocol Data Unit
Packet layer test suite structure
PICS Protocol Implementation Conformance 6.1
Statement
The packet layer tests are grouped as shown in table 1.
Table 1 - Packet layer test groups
Test groups
Test groups Packet layer
Packet layer
test group #
test group #
jl - DXE Interrupt Ready State
1 rl - Packet Layer Rcady Slate 16
17 j2 - DXE Interrupt Sent State
2 r2 - DTE Restart Request State
fl - DXE Receive Ready State
3 r3 - DXE Restart Indication State 18
19 f2 - DXE Receive Not Ready State
4 pl - Ready Statc
20 gl - DTE Receive Ready State
5 p2 - DTE Call Request Statc
g2 - DTE Rcceive Not Ready State2
p3 - DXE Incoming Call Statc 21
Data Transfer
7 p4 - Data Transfer State 22
Timer Tests
8 p5 - Call Collision State 23
p6 - DTE Clear Request State 24 Address
p7 - DXE Clear Indication State 25 Facility
dl - Flow Control Ready State 26 Registration
Multiple Logical Channel Assignment
d2 - DTE Rcset Request State 27
d3 - DXE Reset Indication State 28 DTEDTE Tests
il - DTE Intcrrupt Ready Sute
i2 - DTE Intcrrupt Sent Statc
2) This group has becn deleted but die number has bccn retained for consistency.
ISOAEC 8882-3 : 1991 (E)
proccdurc upon completion of link layer initialization.
For each test group that tests a packct layer statc (PLG 1
through PLG28), the tcst cases spcciïicd arc catcgorizcd
into the following thrcc subgroups. Thc Tcstcr will accept either a Restart Confirmation or a
Rcsrart Rcquest as a valid response to its Restart
Subgroup 1 contains tcst casts in which thc Indication, as shown below in example EG-Wl.
Tester transmits a proper test packct, thcsc tcst Packct layer initialization always occurs once at the start
cases are identified with a onc hundred scrics of a tcst scssion. State initialization, on the other hand, is
test case identifier xx-lxx. perïormcd many times during a test session as part of
each test case. Packet layer initialization will also occur
Subgroup 2 contains tcst cascs in which the as part of state initialization when the previously
Tester transmits an improper test packct, these executed test case results in a Fail or Inconclusive
vcrdict, or thc previously executed test case is part of
test cases are identified with a two hundrcd
series test case identifier xx-2xx. PLG 1, 2, 3, 26 or in test groups in which the Restart
procedure is cxecuted as part of state initialization (PLG
Subgroup 3 contains tcst cascs in which thc
1,2,3 and 26).
Tester transmits an inopportune tcst packct,
these test cascs are idcntificd with a thrce Thc following arc examples of initialization of IS0 8208
hundred series tcst cilse idcntificr xx-3xx. ovcr IS0 7776 (LAPB). Any other examples of
initialization sequences using other underlying protocols
6.2 Packet layer initialization are not shown, but may be appropriate. For example,
normal state initialization steps in state rl (PLG 1) are as
with IS0 8208, 3.10, the DTE must shown in figure 1.
In accordance
transmit a Restart Request whcncvcr link laycr
initialization has completcd. However, DTEs dcvclopcd For those DTEs which disconnect the link upon receipt
in conformance with the 1980 and 1984 vcrsions of of a Restart Indication (or transmittal of a Restart
Recommendation X.25 arc not required to send B Rcsuirt Rcqucst) thc state initialization steps include link layer
Request at this time. To accoininodatc both DTE
initialization as shown in figure 2.
rcstart
implementations, the Tester initiatcs thc
Figure I
Test Casc Dynamic Behaviour
Reference: Example Tcst Stcp / Packct Laycr Initiali/.ation
Identifier: EG-001
Objective: An cxamplc test stcp illustrating Packct Laycr Initialization
Default Reference:
Extended Comments:
1) the Restart is scnt upon succcssful initialization of thc Data Link Laycr

ISO/IEC 8882-3 : 1991 (E)
Figure 2
Tcst Case Dynamic Behaviour
Exarnple Tcst Step / Packct Laycr Initiali~ation /Link Laycr Initialization
Reference:
Identifier: EG-002
Objective: An cxarnple tcst step illus~ating Pnckct Laycr Initialization that includes Data Link Layer
Initialization
Default Refercncc:
-
~~ ~~
Label Constraints V Comments
Behaviour Description
Reference
EGO02 [L,Dl
ÇTRT-D C E
L!RESTART S'I'ARI' 'I'D
S'I'RTC
L?RESïARTC STAR'I' '1'D
DISC-1 wait for disc
D?DISC CANCEL 'I'D
+LINK-INIT
F
L?TIM EO UT 'I' D
L?RESI'ARI' START 'I'D STR'I'-D'I'EA
D?DISC CANCEL 'I'D DISC-1
+LINKINIT
F TD expired
L?TIMEOUl TD
F TD expired
L?TIMEOUT TD
F
L?OTHERWISE CANCEL 'I'D
LINK - INIT
UA-DCE UA
D!UA send
SABM-1 wait for SABM
D?SABR
UA-DCE send UA
D!UA
L!RESTART START 'I'D Sï'R?'-DCE
S'I'R'I'C
L?RESTARTC CANCEL TD
L?RESTART CANCEL 'I'D STRT-DTEA
L?TIMEOU?' TD F
L?OTHERWISE CANCEL 'I'D F
Extended Comments:
L is the PCO at the Testcr (Packct Laycr) to Link Laycr interface.
D is the PCO at the Link Laycr to Physical intcrface.
This example uscs the Multi-laycr testing mcthod, the Packet Layer
Test Suite only uscs the Rcrnote Single-laycr tcsting incthod.
ISOAEC 8882-3 : 1991 (E)
6.3 DTE-initiated actions considcrs the round trip transit delay between
thc Tester and IUT, and the time necessary for
DTE-initiated actions specified by the test suite arc an IUT to respond to a received packet or
handled using the Implicit Scnd mechanism dcfincd in timer expiry;
ISO/IEC 9646-3. The ability of the IUT to pcrfonn these
actions, and its ability to execute the tests containing thc TO-R3 - is the minimum time that the IUT remains in
actions, is determined by the information providcd in thc
state R3. The duration is provided in PIXIT
PIXIT and the PICS.
question 1.22 and contained in
TO_DELAY-R3MIN;
6.4 Timer definitions
TO-P3 - is the minimum time that the IUT remains in
This part of ISO/JXC 8882 defines the following timcrs: state P3. The duration is provided in PIXIT
question 1.22 and contained in
TR
-the time required by the IUT to rcsumc testing TO_DELAY-P3_MIN,
after completion of the Restart proccdure. The
duration is providcd in PIXIT question 1.18a TO-P7 - is the minimum time that the IUT remains in
and contained in the test suite parameter state P7. The duration is provided in PIXIT
TR-DELAY; question 1.22 and contained in
TO-DELAYP7-MIN;
TC - the time required by the IUT to rcsumc tcsting
after completion of the Clear procedure. The TO-D3 - is the minimum time that the IUT remains in
in PIXIT question 1.18b
duration is provided state D3. The duration is provided in PIXIT
and contained in the test sutic paramctcr
question 1.22 and contained in
TC-DELAY;
TO-DELAY-D3_MIN;
TS - the time required by the IUT to resumc tcsting TO-J2 - is the minimum time that the IUT remains in
after cornpletion of the Reset proccdurc. Thc state 52. The duration is provided in PIXIT
duration is providcd in PIXIT qucstiori 1.18~
question 1.22 and contained in
and contained in the test suite paramctcr
TO-DEL AYJZMIN.
TS-DELAY;
6.5 Cause codes and diagnostic codes
TD - the time that the Tcstcr waits bcforc
determining that the IUT will not rcspond to a IS0 8208 requires the cause code to be O or 128 and the
Tester stimulus. For exainplc, how long the
diagnostic code to be present in the Restart, Clear or
Tester should wait bcfore assuming that thc Rcsct packet. Use of cause code O designates the use of
or failcd to respond
IUT has either discardcd standard diagnostic codes as specified in IS0 8208,
must be lcss than all othcr
to the stimulus. TD figurc 14-B. Usc of cause code 128 designates the use of
timers spccific to IS0 8208, i.e. T20 through codes.
DTE-spccific diagnostic
T28. The duration is calculatcd by the I'ormuln
contained in the PIXIT qucstion 1.23 (TD = 2 CCITT X.25 (1984) requires the cause code in the
* TD-RESPONSE + MAX(TO-R3, TO-P3, Restart, Clcar, or Rcset Request packets to be either O or
TO-P7, TO-D3, TOJ2) and containcd in the a value in the range of 128 through 255. The diagnostic
test suitc parameter TD-WAIT-TIME. codc ficid is not mandatory in the basic format of these
rcqucst packcts. However, when the extended format is
TD-RESP - is the maximum time that thc tcstcr should
uscd, the diagnostic codc field shall be present.
wait for an iinmcdiate rcsporisc from the IUT
to a tcstcr stimulus. The duration is providcd
CCITT X.25 (1980) requircs the cause code field in the
in PIXIT question 1.20 and conlaincd in
Rcst:ut, Clcar, or Rcsct Request packet to be set to O.
TD-RESPONSE;
Thc diagnostic codc ïicld is not mandatory in the request
packcts.
TDEL - is a tolerance uscd in tcsting timcrs T2O - T28
of the base slandnrd. Thc duration is providcd Any onc of scvcrril diagnostic codes may be generated by
in PIXIT qucstion 1.2 1 and conkiincd in thc the IUT, on a pcr tcst case basis, especially where
test suitc paramtcr TDELTA. Thc durulion multiple crror conditions are present in the same packet.
ISOAEC 8882-3 : 1991 (E)
data packets as required for window rotation tests.
In such instances any one of the possible diagnostic
The Tester will only send Receive Ready (RR)
codes shall be accepted.
packets during these tests.
6.6 Data transfer states
6.7 Other user data fields
A limited set of data uansfer tests (PLG20 and PLG22)
are included in this test suite to verify the IUT's ability to When necessary, the content of user data fields in the
perform the following: Call setup, Clearing and Interrupt packets shall be
provided to the Tester by the IUT provider in order to
send and/or receive valid data packets; successfully execute the Packet Layer Test Suite. In this
case, the IUT requires the Tester to transmit user data
manage window rotation; fields in accordance with higher layer protocols which
are operating above the packet layer.
detect improper data packers, and react
6.8 Transient states
accordingly;
It is recognized that for those DTEs that process packets
observe the remote busy condition.
sequentially, certain states are not observable.
Specifically, the testing of the DTE during the DXE
In order to facilitate the exchange of data packets during
(for example, r3 - RESTART
these tests, the IUT provider shall specify the contcnts of defined states
INDICATION, p3 - INCOMING CALL, p7 - CLEAR
the data packet user data field (UDF) for the Tester. The
INDICATION, and d3 - RESET INDICATION) may
UDF values are supplied by the IUT provider in the
in the testing of some other states @l - Packet
PIXIT. end up
Layer Ready, p4 - Data Transfer, dl - Flow Control
Ready). For example, to test the response to an error (1'3)
The following items should be considcrcd when
stittc, the Tester would send a RESTART INDICATION,
completing the PIXIT:
immcdiatcly followed by the error packet. The Tester is
cxpccting the DTE to discard the error packet, then send
a) The UDF content in data packets rcceivcd by the
Tester will not be verified. Consequently, the a RESTART REQUEST in response. However, the DTE
information is not requested in the PIXIT. gcnerally rcsponds immediately to the RESTART
INDICATION with a RESTART CONFIRMATION
NOTE - Receive-only IUTs are not expcçtcd to scnd data and processes the next packet from the packet layer state
packets during data transfer tcsts.
rl . This test suite contains tests for these transient states
only if they are observable. They are observable and
b) The start of data transfer (i.e. Testcr or IUT uansinits
tcslablc if the minimum duration of the state is at least
first) is based on the response in thc PIXIT.
twice TD-RESPONSE.
c) Depending on the test bcing pcrformcd, thc full list
6.9 Relationship of PICS to test suite
of UDFs specified in thc PIXIT may not be scnt.
Exchange of data packets conlaining UDFs spccificd
The Protocol Implcmentation Conformance Statement
in the list may terminate at any point. Subscqucnt
(PICS) defines the capabilities and options which have
tests will start with the entry in the UDF lis1 that is
bcen iinplcmented by the IUT, and also any features not
specified in the PIXIT (i.e. first entry or ncxt cnuy).
implemented. The PICS shall be provided by the IUT,
and its function is to ensure that the IUT implementation
d) If UDFcontentsarcspecificd in thc PIXIT, thcy will
will bc tcstcd for conformance against only relevant
be sent (in sequence) whcnevcr a data packcl inusl
rcquircincnts. Thc PICS proforma is defined in ISO/IEC
be sent, or in response to data packcls rcccivcd l'rom
X208lArnd. 3. Table 5 maps the PICS items to the test
the IUT.
cascs which thcy afïcct.
,NOTE - Q-bit, D-bit and M-bit settings in thcsc dota packets
6.10 Relationship of PIXIT to test suite
are based on information provided in iiic PIXIT. Kcccivc
Ready (RR) packets may also bc sent by thc Testcr and the IUT.
Thc PIXIT consis6 of a list of questions developed to
obtain thc charactcristics of the IUT which are necessary
It is also assumcd that thc IUT can scnd conçcculivc
e)
to succcssïully CXCCU~C thc conformance test suite. Table
ISO/IEC 8882-3 : 1991 (E)
An uppercase mnemonic cncloscd in parcnthcsis i.e.
6 describes thc relationship of thc PIXIT to tlic tcst suite.
(IUT-TX) indicates thc Tcst Suitc Pnrnmctcr that maps
The table lisis the question nuinbcrs spccificd in thc
to this PIXIT question. Valucs supplicd in the PIXIT will
PIXIT, and maps thcm to thc test cases which thcy affcct.
be directly mapped into the Tcst Suitc via thcir associated
Test Suite Parameter, thcrcforc all supplicd v' '1 I ucs must
6.11 PIXIT profornia
be in valid TTCN notation. A ficld that may contain any
valid value based on the protocol spccificatiori is
Information supplied by the IUT providcr in tablc 2 will
indicated by use of a ? in the PIXIT answcr. A I'icld
be used to configure the Testcr to cxccutc thc
which may or may not bc prcscnt is indicatcd by an * and
conformance test suite. Qucstions pcrtaining to
a field which is never prcscnt is indicatcd by a - . Rcfcr to
function@) not supported by the IUT should bc ignorcd,
the Test Suite Parametcr table Tor thc dccltircd iypc
since tests requiring the information will bc cliininatcd
(INTEGER, BITSTRING, HEXSTRING) of cach tcst
from the conformancc test suite by thc PICS. It may bc
suite parameter.
necessary to complete more than onc PIXIT in order to
represent the various configuration options of ii specific
JUT.
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
Table 2 - PIXIT PROFORMA
General Information
IUT Type
1.1 Indicate the protocol to be tested, select only one of the following;
a) IS08208 WO) yes J no
b) CCITT X.25 1984 (CCITT-84) yes J no
c) CCITT X.25 1980(CCITT-80) yes / no
State whether the IUT is capable of sending data and/or receiving data.
1.2
(IUT-TX) yes / no
a) sending
b) receiving (IUT-RX) yes / no
Logical Channel Configuration
1.3 Range of PVC Logical Channel Identifier(s) (must be less than or equal to PICS item LC7)
(LW to (HPV)
1.4 Range of SVC Logical Channel Identifier(s) (must be within the ranges specified in the
PICS items LC1 through LC6)
a) One-way incoming (LIC) to (HIC) Note 1
b) One-way outgoing (LOC) to (HOC) Note 1
C) Two-way (LTC) to (HTC) Note 1
1.5 Indicate a logical channel to be used by the Tester for Incoming Calls (to the IUT) or PVCs.
(LCI-UNDER-TE S T) Note 9
1.6 Indicate a logical channel to be used for logical channel unassigned testing.
(LUC)
1.7 How many Incoming virtual calls can be supported at the same time using the information
in PIXIT question 1.4 and PIXIT question 2.2a ?
(SIM-CALL-I N)
1.8 How many Outgoing virtual calls can be supported at the same time using the information
?
in PIXIT question 1.4 and PIXIT question 2.3a
(SIM-CALL-OUT)
ISO/IEC 8882-3 : 1991 (E)
PIXIT PROFORMA
Flow Control Information
1.9 Window sizes
Indicate the defüult window size to be used during test execution. This value is used
a)
for both transmit and receive windows (shall be in range of PICS items V2s and
V2r).
(DEF-W I N-S 2)
Indicate a nonstandard default window size to be used during test execution. This
b)
value is used for both transmit and receive windows.
(NS-DEF-W IN-S 2)
NOTE - the NS-DEF-WIN-SZ is a string of four hexidecimal digits representing the two octet facility
parameter field for both the transmit and rcceive nonstandard default window sizes.
Provide the integer value of the nonstandard default window size given in 1.9b
c)
above.
(NS-DEF-W I N-S 2-NUM)
‘i?f@ )Packet sizes
Indicate a nonstandard default packet size to be used during test em m. This value is
used for both transmit and receive picket sizes.
(NS-DEF-PKT-SZ)
NOTE - the NS-DEF-PKT-SZ is a string of four hcxidccimal digits representing the two octet facility
parameter field for both the transmit and rcccivc nonstandard default packet sizes.
1.1 1 Indicate maximum flow control packet size. (MAX-PKT-SZ)
1.12 Indicate the modulo to be used for testing. (SEQ-MODULO) 8 / 128 ___
ISO/IEC 8882-3 : 1991 (E)
PIXIT PROFORMA
IUT Behaviour
1.13 Does the IUT re-initialize at the Data Link Layer upon execution of an unexpected Restart
?
procedure
(DIS C-AT-DL) yes 1 no
a one for one exchange of Data packets when transmitting a window
1.14 Does the IUT require
or more of data?
(REPLY -REQUIRED) yes I no
1.15 Will the IUT send the first data packet?
(FIRST-D AT A-FROM-IUT) yes I no
yes 1 no
1.16 Will the IUT send more data packets than its send window size?
Will the IUT send at least three data packets more than its modulo size? yes I no
1.17
Timers
State the time required by the IUT to resume testing after completion of the following
1.18
procedures:
Note 3
a) Restart (TR-DELAY)
Note 3
b) Clear (TC-DELAY)
c) Reset (TS-DELAY) Note 3
1.19 Enter the values used by the IUT for the following timers:
Note 3
Note 3
Note 3
Note 3
Note 3
Note 3
Note 3
Note 3
ISO/IEC 8882-3 : 1991 (E)
PIXIT PROFORMA
i> (T28) Note 3
State the maximum time the tester should wait for an immediate response from the IUT to
1.20
a tester stimulus, see clause 6.4.
(TD-RES PONS E) Note 3
1.21 State the delta value to be added to timers used by the Tester, see clause 6.4.
(TDELTA) Note 3
1.22 For R3, P3, D3, P7,J2 gide the minimum and maximum time that the IUT remains in these
(TO-DELA Y-R3-M IN) Note 3,7
R3
(TO-DELAY-R3_MAX)
Note 3,7
P3 (TO-DEL A Y -P3-M I N)
(TO-DELAY-P3-M AX)
(TO-DEL A Y -D 3-M I N) Note 3,7
D3
(TOVDELAY-D3-MAX)
Note 3,7
P7 (TO-DELAY-P7-M IN)
(TO-DELAY-P7_MAX)
(TO-DELAY-J2-M I N) Note 3,7
(TO-DELA Y -J2-M AX)
1.23 The time that the tester will use in most test cases when waiting for a response from the IUT
will be a function of the following formula and assigned to the timer type TD.
(TD-WAIT-TIME) = 2 * TD-REPONSE +
the maximum value of (TO-DELAY-R3_MAX,
TO-DELAY-P3_MAX, TO-DELAYbD3-MAX,
TO-DELAY-P7_MAX, TO-DELAYdJ2-MAX )
ISOAEC 8882-3 : 199
PIXIT PROFORMA
Packet Specific Information
Call Setup Information
yes / no
Is the G$lling DTE address in an Incoming Call packet verified?
2.1
a)
yes, indicate an unacceptable address and address length which can be sent by
If
b)
the Tester.
(TST-ADDR-IN V)
(TST-ADDR-INVL)
Is the Called DTE address in an Incoming Call packet verified? yes / no
c)
an unacceptable address and address length which can be sent by
If yes, indicate
d)
the Tester.
(IUT-ADDR-INV)
(IUT-ADDR-INVL)
2.2 For each of the following packets indicate the value of the field and its length expected by
the IUT.
Called Address
Cri 11 i n E Add res s
a) Incoming Call
(TST-ADDR 1) (IUT-ADDR 1)
(TSTLADDR1-L) - (IUT-ADDR 1L)
b) Call Connected
(TST-ADDR2) (IUT-ADDR2) Note 4
(TS T-ADDR2-L) (IUT-ADDR2-L)
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
by the IUT
2.3 For each of the following prickets indicate the value of the field transmitted
Ca 11 in ri Address Called Address
a) Call Request
(IUT-ADDR5) (TST-ADDR5)
(IUT-ADDR 5-L) (TST-ADDR5-L)
b) Call Accepted
(IUT-ADDR6) (TST-ADDR6) Note 4
(IUT-ADDR6-L) (TST-ADDR6-L)
2.4 Specify a maximum length address supported by the IUT.
(IUT-ADDR-M AX)
(IUT-ADDR-M AXL)
2.5 Indicate the addresses and facilities and lengths to be used in the CCIïT - Specified DTE
facility for called rind calling address extension.
a) the address and length for the Address Field contained in the Incoming Call packet
only;
Calling Address Called Address
(TST-AF) (IUT-AF)
(IUT-AFL)
(TST-AF-L)
b) the facility length and contents of the Address Extension Facility Parameter, including
the use of address extension octet contained in the Incoming Call packet only;
(F-NONX25)
(F-NONX25-L)
NOTE - the F-NONX25 string of facilities includcs; facility marker ’OOOF’H, facility code ’CB’H, calling
address length, calling address, facility codc ’CY”, callcd addrcss Icnglh, and called address.
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
c) the facility length and contents of the Address Extension Facility Parameter, including
the use of address extension octet, contained in the Call Accept packet used in response
to the Incoming Call packet;
(FAEL)
NOTE - the F-AE string of facilitics includes; facility marker 'OOOF'H, facility code 'C9'H, called address
length, called address.
Facilities
2.6 a) Is the fast select facility always used? (FAST-SELECT) yes / no
If yes, the fast select facility must be included in the answers to question 2.7.
b) Does the IüT require more than one facility to be present in an Incoming Call packet?
yes 1 no Note 8
c) Does the IUT transmit more than one facility in a Call Request packet?
yes 1 no Note 8
d) Provide a string of 110 octets of facility infomiation to be sent to the IUT.
(FACS-110) Note 10
2.7 Provide the facilities, facility length rind user data to be used in each of the following
packets.
a) Incoming Call packet received by the IUT
(CALL-IND-F) Note 10
(CALL-IND-FL)
(CALL-IND-UD)
b Call Request packet transmitted by the IUT
(CALL-REQ-F) __ Note 10
ISOIIEC 8882-3 : 1991 (E)
PIXIT PROFORMA
(CALL-REQ-FL)
(CALL-REQ-UD)
c) Call Connected packet received by the IUT
(CALL-CONF) Note 10
(CALL-CON-FL)
(CALL-CON-UD)
d) Call Accept packet transmitted by the IUT
(CALL-ACC-F)
Note 10
(CALL-ACC-FL)
(CALL-ACC-UD)
e) Clear Indication packet received by the IUT
(CLR-IND-F) Note 10
( CLR-IND-FL)
(CLR-IND-UD)
f) Clear Request packet transmitted by the IUT
Note 10
Note 10
h) Clear Confirmation packet transmitted by the IUT
(CLCTX-F) Note 10
(CLCTX-FL)
2.8 a) Provide a number to be used for Basic CUG? (BCUG-NUM) __
b)
Provide a number to be used for extended CUG? (ECUG-NUM) -
c) Provide a number to be used for bilateral CUG? (BICUG-NUM) __
,
ISOAEC 8882-3 : 1991 (E)
I
I PIXIT PROFORMA
2.9 Indicate the default throughput class. (DEF-THRUPT) -
2.10 Indicate a throughput class that is different from the default throughput class.
(THRUPT) -
2.1 1 Indicate the Transit Delay value to be used.
(TRNS-DELAY-1) first octet
(TRNS-DELAY-2) second octet
2.12 Provide the Network User Identification facility length and facilities.
(ENUI)
(ENU1-L)
Data Packet Information
2.13 Specify the Q, D-bit, and M-Bit settings and data contents of the first nine data packets
O, a ? in the entry
which the IUT will received (default settings for Q,D and M-bits are
indicates that any user data is acceptable). If possible at least one data packet should contain
the full size of data.
(UD-O) Q= ,D= ,M=
(UD-1) Q= , D= , M=
(UD-2) Q= ,D= ,M=
(UD-3) Q= ,D= ,M= __
(UD-4) Q= ,D= ,M=
(UD-5) Q= , D= , M=
(UD-6) Q= ,D= ,M=
(UD-7) Q= , D= , M=
-
(UD-8) Q= , D= , M=
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
(UD-U) Q= ,D= ,M= Note 5
2.14 Specify a sequence of Data packets no greater than nine that contains a change of Q-bit
value, where the change generates an error when received by the IUT, and data content that
can be received by the IUT (default settings for D and M-bits is O, a ? in the entry indicates
that any user data is acceptable).
(UDQO)Q= ,D= ,M=
(UDQl) Q= , D= , M=
(UDQ2) Q= , D= , M=
(UDQ3)Q= ,D= ,M=
(UDQ4) Q= , D= , M=
(UDQS) Q= , D= , M=
(UDQ6) Q= , D= , M=
(UDQ7)Q= ,D= ,M=
(UDQS) Q= , D= , M=
2.15 Specify a sequence of Data packets no greater than nine that contains a change of Q-bit
value, where the change is acceptable to the IUT, and data content that can be received by
the IUT (default settings for D and M-bits is O, a ? in the entry indicates that any user data
is acceptable).
\
(UDQOA) Q= , D= , M=
(UDQlA) Q= , D= , M=
(UDQ2A)Q= ,D= ,M=
(UDQ3A)Q= ,D= ,M=
(UDQ4A) Q= , D= , M=
(UDQSA) Q= , D= , M=
(UDQ6A)Q= ,D= ,M=
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
(UDQ7A)Q= ,D= ,M=
(UDQ8A) Q= , D= , M=
2.16 Specify a sequence of Data packets no greater than nine after which a packet with an empty
data field may be processed by the IUT (defüult settings for Q, D and M-bits are O, a ? in
that any user data is acceptable).
the entry indicates
(UDEO)Q= ,D= ,M=
(UDEl)Q= ,D= ,M=
(UDE2)Q= ,D= ,M=
(UDE3)Q= ,D= ,M=
(UDE4)Q= ,D= ,M=
(UDES)Q= ,D= ,M=
(UDE6)Q= ,D= ,M=
(UDE7)Q= ,D= ,M=
(UDE8)Q= ,D= ,M=
2.17 Specify a sequence of Data packets no greater than nine that contains a change of M-bit
value and data content that can be received by the IUT (default settings for D and Q-bits
are O, a ? in the entry indicates that any user data is acceptable).
(UDMO) Q= ,D= ,M=
Q= ,D= ,M=
(UDM1)
(UDM2) Q= ,D= ,M=
(UDM3) Q= ,D= ,M=
(UDM4) Q= ,D= ,M=
(UDMS) Q= ,D= ,M=
(UDM6) Q= ,D= ,M=
(UDM7) Q= ,D= ,M=
ISO/IEC 8882-3 : 1991 (E)
PIXIT PROFORMA
(UDM8) Q= ,D= ,M=
Specify a partially full data packet with M-bit set which w uld otherwise (M-bit = O) be
2.18
acceptable to the IUT.
,M=
(UDMP)Q= ,D=
2.19 Specify the user data to be carried where the Tester is required to send a specific number
of data octets in order to test the IUT (a ? in the entry indicates that any user data is
acceptable).
(UD1) 1 octet -
(UD3) 3 octets
(UD16)16 octets
(UD17)17 octets
(UD32)32 octets
(UD1lO)llO octets
(UD128) 128 octets
(UD129)129 octets -
Note 6
(UDNS) -
ISOAEC 8882-3 : 1991 (E)
PIXIT PROFORMA
Miscellaneous Information
Provide Interrupt User Data (one octet for X.25 1980 and upto 32 octets for X.25 1984 and
2.20
IS0 8208) to be carried in Interrupt packets:
a) IUT transmits (Tester receives)
(UD-I-IUT)
b) IUT receives (Tester transmits)
(UD-I-T S T)
2.21 Registration Request/Confirmation Packets
Note 8
2.22 Implicit Sends
Indicate whether the IUT can or cannot support on demand the following Implicit Sends
used in this Test Suite.
a) cIUT!CALL> Call Request yes 1 no
yes I no
b) cIUT!DATA> Data
c) cIUT!INT> Interrupt yes I no
d) Restart Confirm yes/ no
e) cIUT!RESTART> Restart yes / no
0 Registrcltion yes 1 no
rsomc 8882-3 : 1991 (E)
PIXIT PROFORMA
NOTES
Specify a logical channel combination which will permit both Incoming Call and Call Request functions to be tested
1.
(preferably one two-way VC), if applicable.
2. Value should be indicated in hexadecimal.
3. All times are to be given in seconds.
4. The IUT will indicate here whether it accepts that the contents of this Field could be different from what was expected, as
a consequence of the use of the CLAMN facility.
UD-U is a universally repeatable data packet and will be uscd in test cases where more than nine data packets are required
5.
to be transmitted by the Tester (see test case 1’22-10.5 as an example).
6. A packet containing the number of octets equal to that of the Nonstandard Dcfault packet size, see PIXIT 1.10.
7. When TO-DELAY-xx-MIN is not greater than or equal to twice the value of TD-RESPONSE (PIXIT 1.20) the
applicable transient state is not testable.
8. All tests for facilities contained in PLG 25 and PLG 26 test for each facility indcpendcntly where other facilities are not
present. If a combination of facilities is required by the IUT the facility test cases for those facilities will be de-selected
from PLG 25 and PLG 26.
If a value is not provided a logical channel will be assigned by selecting the lowest channel in the first available logical
channel group choosen in the following order, Incoming, Twoway, PVC.
10 The facility information provided must be syntactically correct and acceptable to the IUT. Facilities may be repeated to
achieve the required length.
ISO/IEC 8882-3 : 1991 (E)
6.12 Acceptable unexpected responses In a DTE/DTE environment where the IUT is acting as a
DCE, diagnostic packets received by the Tester on
O indicating timer timeouts shall be
logical channel
In some test cases, particularly in the data transfer state
ignored.
(p4/dl), unexpected packets may be received from the
IUT which do not affect the outcome of the test case.
6.13 Implicit send
Such unexpected packets shall be accepted by the test
system without consequence to the IUT.
The use of the Implicit Send mechanism may be realized
through either manual operator intervention or
Table 3 identifies those packets which the test system
automated procedures. PIXIT question 2.22 lists the
shall accept depending on the state of the interfaces as
Implicit Sends used in this test suite.
perceived by the IUT. Note that RESTART REQUEST,
CLEAR REQUEST, and RESETREQUEST, which may
6.14 Basic interconnection tests
be sent at any time by the IUT are not considered to be
allowable unexpected responses during data transfer
A set of Basic Interconnection Tests (BITS) may be used
in state PI, where a
tests. Also note that when the NT is
to determine the interoperability between the Test
Call Request may be sent at anytime, an unsolicited Call
the Implementation Under Test prior to
Laboratory and
Request is not considered to be an acceptable
running the full test suite, reference ISO/iEC 9646-1,
it is hightly
unexpected response. This is because
6.1.2 . When these BITS are used they shall be selected
Call
unlikely, for reasons of timing, that the unsolicited
from the following list; this selection is based on answers
Request would arrive at a time when the tester would
given in the PICS and PIXIT proformas and the
consider it as a correct response to a previously issued
corresponding entries in the PICS and PIXIT cross
implicit send request (IUT!CALL), see ISO/IEC 9646-5.
reference tables, see clause 8.
Similarly, a REJECT packet requesting packet
retransmission is not accepted as an allowable
unexpected response.
The logical channel under test is derived fro
...