SIST ETS 300 804-1 E1:2005

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Data Link Layer (DLL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

Conformance Test Specification (TTCN) for the protocol for layer 2 signalling between exchanges of private integrated services networks for the control of circuit-switched calls.

Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Vodovne osnovne storitve - Podatkovna povezovalna plast (DLL) - 1. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - Specifikacija

General Information

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• ICS: 35.100.20 - Data link layer
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Mandate: T-245
• Ref Project: ETSI ETS 300 804-1 ed.1 (1998-02) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Data Link Layer (DLL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 804-1 E1:2005
01-marec-2005
Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski
protokol - Vodovne osnovne storitve - Podatkovna povezovalna plast (DLL) - 1.
del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - Specifikacija
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit
mode basic services; Data Link Layer (DLL); Part 1: Test Suite Structure and Test
Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: ETS 300 804-1 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
35.100.20 Podatkovni povezovalni sloj Data link layer
SIST ETS 300 804-1 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 804-1 E1:2005

---------------------- Page: 2 ----------------------

SIST ETS 300 804-1 E1:2005
EUROPEAN ETS 300 804-1
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA-00108-1
ICS: 33.020
Key words: Circuit mode, layer 2, PINX, PISN, QSIG, testing, TSS & TP
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Circuit mode basic services;
Data Link Layer (DLL);
Part 1: Test Suite Structure and Test Purposes (TSS&TP)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 804-1 E1:2005
Page 2
ETS 300 804-1: February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 804-1 E1:2005
Page 3
ETS 300 804-1: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 ETS definitions.7
3.2 ISO definitions.8
3.3 Abbreviations .8
4 Test Suite Structure (TSS) .9
4.1 Overview .9
4.2 Test groups.9
4.2.1 Protocol group .9
4.2.2 Main test groups.9
4.2.2.1 Valid Behaviour Tests (BV).9
4.2.2.2 Inopportune Behaviour Tests (BO).9
4.2.2.3 Invalid Behaviour Tests (BI).9
5 Test Purposes (TPs) .10
5.1 Introduction .10
5.1.1 TP naming convention.10
5.1.2 Source of TP definition.10
5.2 PISN.11
5.2.1 Valid Behaviour (BV) .11
5.2.2 Inopportune Behaviour (BO) .16
5.2.3 Invalid Behaviour (BI) .25
5.2.4 Undefined TPs.28
History.29

---------------------- Page: 5 ----------------------

SIST ETS 300 804-1 E1:2005
Page 4
ETS 300 804-1: February 1998
Blank page

---------------------- Page: 6 ----------------------

SIST ETS 300 804-1 E1:2005
Page 5
ETS 300 804-1: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the standardizing Information
and Communication Systems Association (ECMA) on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
This ETS comprises two parts with the generic title "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Data Link Layer (DLL); Circuit mode basic services". The title of each
part is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS & TPs)";
Part 2: "Abstract Test Suite Specification (ATS)".
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 804-1 E1:2005
Page 6
ETS 300 804-1: February 1998
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 804-1 E1:2005
Page 7
ETS 300 804-1: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Test Suite Structure (TSS) and Test
Purposes (TPs) specification for the Data Link Layer (DLL) of the Private Integrated Services Network
(PISN), Inter-exchange signalling protocol.
The objective of this TSS and TPs specification is to provide conformance tests which give a high
probability of inter-operability of the Data Link Layer (DLL). The TSS and TPs specification covers the
procedures described in ETS 300 402-2 [1] annex ZA.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and
ISO/IEC 9646-2 [4]) is used as basis for the test methodology.
This TSS and TPs specification standard is applicable for use in symmetrical application between two
PINXs and is also applicable to equipment when used in certain scenarios that provide a continuous bit
stream channel between two PINXs, and will be referenced from the standard which specifies the
scenarios concerned.
TSS and TPs specifications for the Network Layer are provided in other parts of the PISN, Inter-exchange
signalling protocol standards.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited in the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments or revisions to of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 402-2 (1995): "Integrated Services Digital Network (ISDN) - Digital
Subscriber Signalling System No. one (DSS1) protocol - Data link layer - Part 2:
General protocol specification - [ITU-T Recommendation Q.921 (1993),
modified]".
[2] ETS 300 402-4: "Integrated Services Digital Network (ISDN) - Digital
Subscriber Signalling System No. one (DSS1) protocol - Data link layer - Part 4
“Protocol Information Conformance”.
[3] ISO/IEC 9646-1 (1994): "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 1: General Concepts".
[4] ISO/IEC 9646-2 (1994): "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 2: Abstract Test Suite Specification".
[5] ISO/IEC 7498-1 (1994): "Information Processing Systems - Open Systems
Interconnection - Basic Reference model: The basic model".
3 Definitions and abbreviations
3.1 ETS definitions
For the purposes of this ETS, the following definitions apply:
master: The Data Link entity that provides the functionality of the "network" as described in
ETS 300 402-2 [1] for a particular Data Link.
slave: The Data Link entity that provides the functionality of the "user" as described in
ETS 300 402-2 [1] for a particular Data Link.

---------------------- Page: 9 ----------------------

SIST ETS 300 804-1 E1:2005
Page 8
ETS 300 804-1: February 1998
3.2 ISO definitions
For the purposes of this ETS, the following definitions apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [3]
Data Link Layer (DLL): See ISO/IEC 7498-1 [5]
Implementation Under Test (IUT): See ISO/IEC 9646-1 [3]
Lower Tester (LT): See ISO/IEC 9646-1 [3]
Network Layer (NWK): See ISO/IEC 7498-1 [5]
Physical Layer (PHL): See ISO/IEC 7498-1 [5]
PICS proforma: See ISO/IEC 9646-1 [3]
PIXIT proforma: See ISO/IEC 9646-1 [3]
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [3]
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [3]
Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [3]
System Under Test (SUT): See ISO/IEC 9646-1 [3]
Upper Tester (UT): See ISO/IEC 9646-1 [3]
3.3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
DLL Data Link Layer
ETS European Telecommunication Standard
FSM Finite State Machine
ISO International Organisation for Standardisation
IUT Implementation Under Test
LT Lower Tester
MST Multi State Transition
NL Network Layer
PCO Point of Control and Observation
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statements
PIXIT Protocol Implementation eXtra Information for Testing
PISN Private Integrated Services Network
PINX Private Integrated services Network eXchange
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
UT Upper Tester

---------------------- Page: 10 ----------------------

SIST ETS 300 804-1 E1:2005
Page 9
ETS 300 804-1: February 1998
4 Test Suite Structure (TSS)
4.1 Overview
Figure 1 shows the Data Link Layer Test Suite Structure including its subgroups Valid Bahaviour (BV),
Inopportune Behaviour (BO) and Invalid Behaviour (BI).
PISN2---------|--BV---|--STATE
       |    |-- .
       |    |-- .
       |    |--STATE
       |
       |--BO---|--STATE
       |    |-- .
       |    |-- .
       |    |--STATE
       |
       |--BI---|--STATE
           |-- .
           |-- .
           |--STATE
Figure 1: Data Link Layer Test Suite Structure
4.2 Test groups
4.2.1 Protocol group
The test suite is structured as a tree with a first level defined as PISN2 representing the protocol group.
4.2.2 Main test groups
The second level of the test suite contains the subgroups BV, BO and BI.
4.2.2.1 Valid Behaviour Tests (BV)
A valid test is a test where the message sequence and the message content are considered as valid (no
MDL_ERR_IND shall be indicated).
4.2.2.2 Inopportune Behaviour Tests (BO)
This test sub group shall verify that the Implimentation Under Test (IUT) is capable of a valid reaction,
when an inopportune protocol event occurs. Such an event is syntactically correct but it occurs when it is
not expected (a MDL_ERR_IND is caused in the Finite State Machine (FSM) of the DLL entity).
4.2.2.3 Invalid Behaviour Tests (BI)
This test sub group shall verify that the IUT, after receipt of an invalid Protocol Data Unit (PDU), reacts in
conformity with the standard. PDU here, means syntactically invalid PDU and therefore a MDL_ERR_IND
may be generated in the FSM of the DLL entity.

---------------------- Page: 11 ----------------------

SIST ETS 300 804-1 E1:2005
Page 10
ETS 300 804-1: February 1998
5 Test Purposes (TPs)
5.1 Introduction
5.1.1 TP naming convention
The identifier of the TP is built according to figure 2.
Identifier: TP-
    = state (4-8)
   = sub-state (0-7)
  = sequential number (001-300) BV, Valid Behaviour Tests
(301-600) BO, Inopportune Behaviour Tests
(601-900) BI, Invalid Behaviour Tests
Figure 2: TP naming convention
5.1.2 Source of TP definition
The TPs were developed based on ETS 300 402-2 [1], including the state tables D-1 to D-3.
NOTE: The state tables D-1 to D-3 of ETS 300 402-2 [1] have been interpreted according to
ETS 300 402-2 [1] annex ZA .
The relevant part of ETS 300 402-4 [2] annex B specifying the Protocol Implementation Conformance
Statements (PICS) proforma for the Private Integrated Services Network (PISN) application is used for the
TP definition.

---------------------- Page: 12 ----------------------

SIST ETS 300 804-1 E1:2005
Page 11
ETS 300 804-1: February 1998
5.2 PISN
5.2.1 Valid Behaviour (BV)
Table 1: Valid Behaviour (BV)
TP40-001 Incoming link establishment procedure: Check that the IUT, after receipt of a correct
SABME/P = 1 in state S4.0, responds by sending UA/F = 1 and enters Multiple Frame
Operation state (i.e. state transition S4.0 to S7.0).
TP40-002 Incoming link establishment procedure: Check that the IUT, after receipt of a correct
SABME/P = 0 in state S4.0, responds by sending UA/F = 0 and enters Multiple Frame
Operation state (i.e. state transition S4.0 to S7.0).
TP40-003 Check that the IUT, after receipt of an unsolicited DM/F = 0 frame in state S4.0, initiates
the link establishment procedure by sending SABME/P = 1 and remains in state S4.0
after receipt of a Tester's response DM/F = 1 frame (no state transition).
TP40-004 Check that the IUT, after receipt of an unsolicited DM/F = 0 frame in state S4.0, initiates
the link establishment procedure by sending SABME/P = 1 and enters Multiple Frame
Operation state after receipt of a Tester's response UA/F = 1 frame (i.e. state transition
S4.0 to S7.0).
TP50-001 Check that the IUT, after receipt of a correct UA/F = 1 frame in state S5.0, enters
Multiple Frame Operation state (i.e. state transition S5.0 to S7.0).
TP50-002 Check that the IUT, after receipt of a correct DM/F = 1 frame in state S5.0, enters
TEI-assigned state (i.e. state transition S5.0 to S4.0).
TP50-003 Check that the IUT, after receipt of an opportune FRMR frame rejecting SABME in state
S5.0, ignores the received frame and discards its contents.
TP50-004 Check that the IUT, in state S5.0, after T200 time elapsed and no UA/F = 1 or DM/F = 1
frame received, repeats only N200 times the establishment request SABME/P = 1
frame.
TP50-005 Check that, in state S5.0, the IUT's re-transmission timer T200 is within the allowed
tolerance of its value.
TP51-001 Check that the IUT, after receipt of a correct UA/F = 1 frame in state S5.1, enters
Multiple Frame Operation state (i.e. state transition S5.1 to S7.0).
TP51-002 Check that the IUT, after receipt of a correct DM/F = 1 frame in state S5.1, enters
TEI-assigned state (i.e. state transition S5.1 to S4.0).
TP51-003 Check that the IUT, in state S5.1, preserves it I queue if it V(A) variable is equal to it
V(S) variable.
TP51-004 Check that the IUT, in state S5.1, discards it I queue if it V(A) variable is different of it
V(S) variable.
TP60-001 Check that the IUT, in state S6.0, after receipt of a DM/F = 1 frame enters TEI-assigned
state (i.e. state transition S6.0 to S4.0).
TP60-002 Check that the IUT, in state S6.0, after receipt of a UA/F = 1 frame enters TEI-assigned
state (i.e. state transition S6.0 to S4.0).
TP60-003 Check that the IUT, after receipt of an opportune FRMR frame rejecting DISC in state
S6.0, ignores the received frame and discards its contents.
TP60-004 Check that the IUT, in state S6.0, after T200 time elapsed and no UA/F = 1 or DM/F = 1
frame received, repeats only N200 times the disconnection request DISC/P = 1 frame.
TP60-005 Check that the IUT, in state S6.0, after T200 time elapsed and no UA/F = 1 or DM/F = 1
frame received, repeats the disconnection request DISC/P = 1 frame.
TP70-001 Check that the IUT, in state S7.0, accepts I-Frame/P = 0 acknowledgement by means of
RR/F = 0 frame.
TP70-002 Check that the IUT, in state S7.0, accepts I-Frame/P = 1 acknowledgement by means of
RR/F = 1 frame.
TP70-003 Check that the IUT, in state S7.0, manages properly the sequence numbering operation,
TP70-004 Check that the IUT manages properly I-Frame exchange in state S7.0.
TP70-005 Check that the IUT, after receipt of a RNR/P = 1 frame in state S7.0, responds with
RR/F = 1 and enters state S7.4.
TP70-006 Check that the IUT, after receipt of a RNR/P = 0 frame in state S7.0, enters state S7.4.
(continued)

---------------------- Page: 13 ----------------------

SIST ETS 300 804-1 E1:2005
Page 12
ETS 300 804-1: February 1998
Table 1 (continued): Valid Behaviour (BV)
TP70-007 Check that the IUT, after receipt of a RNR/F = 0 response frame in state S7.0, enters
state S7.4.
TP70-008 Check that the IUT, after receipt of a REJ/P = 1 frame in state S7.0, responds with RR/F
= 1 frame and re-transmits the appropriate I-Frame/P = 0.
TP70-009 Check that the IUT, after receipt of a REJ/P = 0 frame in state S7.0, re-transmits the
appropriate I-Frame/P = 0.
TP70-010 Check that the IUT, after receipt of a REJ/F = 0 frame in state S7.0, re-transmits the
appropriate I-Frame/P = 0.
TP70-011 Normal data link disconnection: Check that the IUT, after receipt of a DISC/P = 1 frame
in state S7.0, responds with UA/F = 1 frame and enters state S4.0.
TP70-012 Normal data link disconnection: Check that the IUT, after receipt of a DISC/P = 0 frame
in state S7.0, responds with UA/F = 0 frame and enters state S4.0.
TP70-013 Check that the IUT, in state S7.0, polls by sending RR/P = 1 frame or by re-transmitting
the unacknowledged I-Frame if it receives no acknowledgement of an I-Frame sent
before T200 time (I-Frame command loss).
TP70-014 Check that the IUT, after receipt of a RR/P = 1 simulating a link supervision procedure
during Multiple Frames Operation (S7.0), responds with RR/F = 1 frame.
TP70-015 Check that the IUT, after receipt of a RR/P = 0 frame in state S7.0, stops T200 timer if it
is running and starts or restarts T203 timer.
TP70-016 Check that the IUT, after inactivity (T203) in state S7.0, re-transmits N200 time RR/P = 1
frames on each expiration of T200 before to try to re-establish the data link by sending
SABME/P = 1.
TP70-017 Check that the IUT, in state S7.0, polls by sending RR/P = 1 frame or by re-transmitting
the unacknowledged I-Frame if it receives no acknowledgement of an I-Frame sent
before T200 time (RR response frame loss).
TP70-018 Check that the IUT's link supervision timer T203, in state S7.0, is within the allowed
tolerance of its value.
TP70-019 Check that the IUT, after receipt of a RR/P = 0 command frame in state S7.0, restarts
timer T200.
TP70-020 Check that the IUT, after receipt of a RR/P = 1 command frame in state S7.0, responds
with RR/F = 1 frame and restarts timer T200.
TP70-021 Check that the IUT, after receipt of a RR/F = 0 response frame in state S7.0, restarts
timer T200.
TP70-022 Check that the IUT, after receipt of a REJ/P = 0 frame in state S7.0, re-transmits the
appropriate I-Frames.
TP70-023 Check that the IUT, after receipt of a REJ/P = 1 frame in state S7.0, responds with RR/F
= 1 frame and re-transmits the appropriate I-Frames.
TP70-024 Check that the IUT, after receipt of a RNR/P = 0 command frame in state S7.0, restarts
timer T200.
TP70-025 Check that the IUT, after receipt of a RNR/P = 1 command frame in state S7.0,
responds with RR/F = 1 frame and restarts timer T200.
TP70-026 Check that the IUT, after receipt of a RNR/F = 0 response frame in state S7.0, restarts
timer T200.
TP70-027 Check that the IUT, after receipt of a I-Frame/P = 0 command frame in state S7.0,
responds with RR/F = 0 frame and restarts timer T200.
TP70-028 Check that the IUT, after receipt of a I-Frame/P = 1 command frame in state S7.0,
responds with RR/F = 1 frame and restarts timer T200.
TP70-029 Check that the IUT, after receipt of a REJ/F = 0 frame in state S7.0, re-transmits the
appropriate I-Frames.
TP70-030 Check that the IUT, in state S7.0, accepts simultaneous acknowledgement of more than
one I-Frame by receiving RR/F = 0 frame that acknowledges two I-Frames.
TP70-031 Check that the IUT, in state S7.0, sends a maximum number of k I-Frames if it receives
no acknowledgement.
(continued)

---------------------- Page: 14 ----------------------

SIST ETS 300 804-1 E1:2005
Page 13
ETS 300 804-1: February 1998
Table 1 (continued): Valid Behaviour (BV)
TP71-001 Check that the IUT, in state S7.1, leaves the REJ mode after receipt of a correct
I-Frame/P = 1 (state transition S7.1 to S7.0).
TP71-002 Check that the IUT, in state S7.1, leaves the REJ mode after receipt of a correct
I-Frame/P = 0 (state transition S7.1 to S7.0).
TP74-001 Check that the IUT, in state S7.4, re-transmits the appropriate I-Frames when its peer
leaves busy condition by sending RR/F = 1 in response of the IUT's RR/P = 1 polling.
TP74-002 Check that the IUT, after receipt of an I-Frame/P = 1 in state S7.4, responds by sending
RR/F = 1 frame and remains in the initial state.
TP74-003 Check that the IUT, in state S7.4, handles properly peer busy condition by not sending
any I-Frames.
TP74-004 Check that the IUT, after receipt of a REJ/P = 1 frame in state S7.4, responds with RR/F
= 1 frame and re-transmits the I-Frame rejected.
TP74-005 Check that the IUT, after receipt of a REJ/P = 0 frame in state S7.4, re-transmits the
I-Frame rejected.
TP74-006 Check that the IUT, after receipt of a REJ/F = 0 frame in state S7.4, re-transmits the
I-Frame rejected.
TP74-007 Check that the IUT, after receipt of a valid DISC/P = 1 frame in state S7.4, responds with
UA/F = 1 frame and enters TEI-assigned state (i.e. state transition S7.4 to S4.0).
TP74-008 Check that the IUT, after receipt of a valid DISC/P = 0 frame in state S7.4, responds with
UA/F = 0 frame and enters TEI-assigned state (i.e. state transition S7.4 to S4.0).
TP74-009 Check that the IUT, in state S7.4, polls with RR/P = 1 frame N200 times before it
initiates link re-establishment by sending SABME/P = 1.
TP74-010 Check that the IUT, after receipt of a correct RR/P = 1 frame in state S7.4, responds
with RR/F = 1 frame and enters state S7.0.
TP74-011 Check that the IUT, after receipt of a correct RR/F = 0 frame in state S7.4, enters state
S7.0.
TP74-012 Check that the IUT, after receipt of a correct RNR/P = 1 frame in state S7.4, responds
with RR/F = 1 frame and remains in the initial state S7.4.
TP74-013 Check that the IUT, after receipt of a correct RNR/P = 0 frame in state S7.4, remains in
the initial state S7.4.
TP74-014 Check that the IUT, after receipt of a correct RNR/F = 0 frame in state S7.4, remains in
the initial state S7.4.
TP74-015 Check that, in state S7.4, the IUT's re-transmission timer T200 is within the allowed
tolerance of its value.
TP74-016 Check that the IUT, after receipt of a RR/P = 0 command frame in state S7.4, restarts
timer T200.
TP74-017 Check that the IUT, after receipt of a RR/P = 1 command frame in state S7.4, responds
with RR/F = 1 frame and restarts timer T200.
TP74-018 Check that the IUT, after receipt of a RR/F = 0 command frame in state S7.4, restarts
timer T200.
TP74-019 Check that the IUT, after receipt of a REJ/P = 0 frame in state S7.4, re-transmits the
appropriate I-Frames according to the N(R) of the REJ/P = 0 received.
TP74-020 Check that the IUT, after receipt of a REJ/P = 1 frame in state S7.4, responds with RR/F
= 1 frame and re-transmits the appropriate I-Frames according to the N(R) of the REJ/P
= 0 received.
TP74-021 Check that the IUT, after receipt of a REJ/F = 0 in state S7.4, re-transmits the
appropriate I-Frames according to the N(R) of the REJ/P = 0 received.
TP74-022 Check that the IUT, after receipt of a RNR/P = 0 command frame in state S7.4, restarts
timer T200.
TP74-023 Check that the IUT, after receipt of a RNR/P = 1 command frame in state S7.4,
responds with RR/F = 1 frame and restarts timer T200.
TP74-024 Check that the IUT, after receipt of a RNR/F = 0 command frame in state S7.4, restarts
timer T200.
(continued)

---------------------- Page: 15 ----------------------

SIST ETS 300 804-1 E1:2005
Page 14
ETS 300 804-1: February 1998
Table 1 (continued): Valid Behaviour (BV)
TP74-025 Check that the IUT, after receipt of an I-Frame/P = 0 in state S7.4, responds with RR/F =
0 frame and remains in the initial state.
TP74-026 Check that the IUT, after receipt of an I-Frame/P = 1 in state S7.4, responds with RR/F =
1 frame and remains in the initial state.
TP75-001 Check that the IUT, after receipt of a correct I-Frame/P = 1 in state S7.5, responds with
RR/F = 1 frame, leaves the REJ mode and enters state S7.4 (i.e. state transition S7.5 to
S7.4).
TP75-002 Check that the IUT, after receipt of a correct I-Frame/P = 0 in state S7.5, responds with
RR/F = 0 frame, leaves the REJ mode and enters state S7.4 (i.e. state transition S7.5 to
S7.4).
TP80-001 Check that the IUT, after receipt of a valid DISC/P = 1 frame in state S8.0, responds with
UA/F = 1 frame and enters TEI-assigned state (i.e. state transition S8.0 to S4.0).
TP80-002 Check that the IUT, after receipt of a valid DISC/P = 0 frame in state S8.0, responds with
UA/F = 0 frame and enters TEI-assigned state (i.e. state transition S8.0 to S4.0).
TP80-003 Check that the IUT, after receipt of a valid REJ/F = 1 frame in state S8.0, re-transmits
the I-Frame rejected.
TP80-004 Check that the IUT, after receipt of a valid RNR/F = 1 frame, leaves state S8.0 and
enters state S7.4.
TP80-005 Check that the IUT, after receipt of an I-Frame/P = 0 in state S8.0, responds with RR/F =
0 frame and remains in the initial state.
TP80-006 Check that the IUT, after receipt of an I-Frame/P = 1 in state S8.0, responds with RR/F =
1 frame and remains in the initial state.
TP80-007 Check that the IUT, after receipt of a valid RR/P = 1 polling frame in state S8.0,
responds with RR/F = 1 frame.
TP80-008 Check that the IUT, after receipt of a valid RR/P = 0 command frame in state S8.0,
updates V(A) variable and remains in the initial state.
TP80-009 Check that the IUT, after receipt of a valid RR/F = 0 response frame in state S8.0,
updates V(A) variable and remains in the initial state.
TP80-010 Check that the IUT, after receipt of a valid RNR/P = 1 command frame in state S8.0,
responds with RR/F = 1 frame, updates V(A) variable and enters state S8.4.
TP80-011 Check that the IUT, after receipt of a valid RNR/P = 0 command frame in state S8.0,
updates V(A) variable and enters state S8.4.
TP80-012 Check that the IUT, after receipt of a valid RNR/F = 0 response frame in state S8.0,
updates V(A) variable and enters state S8.4.
TP80-013 Check that the IUT, after receipt of a valid REJ/P = 1 frame in state S8.0, responds with
RR/F = 1 frame and remains in the initial state.
TP80-014 Check that the IUT, after receipt of a valid REJ/P = 0 frame in state S8.0, remains in this
state and updates it V(A) variable (no state transition and no response sent).
TP80-015 Check that the IUT, after receipt of a valid REJ/F = 0 frame in state S8.0, remains in this
state and updates it V(A) variable (no state transition and no response sent).
TP81-001 Check that the IUT, after receipt of a correct I-Frame/P = 1 in state S8.1, responds with
an RR/F = 1 frame and leaves the REJ mode (state transition S8.1 to S8.0).
TP81-002 Check that the IUT, after receipt of a correct I-Frame/P = 0 in state S8.1, responds with
an RR/F = 0 frame and leaves the REJ mode (state transition S8.1 to S8.0).
TP84-001 Check that the IUT, after receipt of a valid DISC/P = 1 frame in state S8.4, responds with
UA/F = 1 frame and enters TEI-assigned state (i.e. state transition S8.4 to S4.0).
TP84-002 Check that the IUT, after receipt of a valid DISC/P = 0 frame in state S8.4, responds with
UA/F = 0 frame and enters TEI-assigned state (i.e. state transition S8.4 to S4.0).
TP84-003 Check that the IUT, after receipt of a valid RR/F = 1 frame in state S8.4, leaves Timer
Recovery state and enters Multiple Frame Operation state (i.e. state transition S8.4 to
S7.0).
TP84-004 Check the correct handling of peer busy sub-state. After receipt of RNR/F = 1 frame in
state S8.4, the IUT has to maintain the peer busy condition.
(continued)

------------
...