SIST EN 301 003-3 V1.1.3:2005

• Abstract:

  Develop part 3 (TSS & TP for the user) of EN 301 003

• Status: Published
• Publication Date: 30-Jun-2005
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-2005
• Due Date: 01-Jul-2005
• Completion Date: 01-Jul-2005
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 003-3 V1.1.3 (1999-11) - Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

SIST EN 301 003-3 V1.1.3:2005 is the Slovenian adoption of ETSI EN 301 003-3 for the B-ISDN DSS2 protocol feature “Peak cell rate modification by the connection owner.” It specifies the user-side Test Suite Structure (TSS) and Test Purposes (TP) for conformance testing at the T reference point, or the coincident S and T reference point, against EN 301 003-1.

The document is written for test developers, implementers, and quality teams who need to build or assess an Abstract Test Suite (ATS) and related PICS-based test coverage. In practice, it tells you how the tests are grouped, what behaviors are covered, and how the implementation under test should react in normal and error cases.

What does SIST EN 301 003-3 V1.1.3:2005 specify?

SIST EN 301 003-3 V1.1.3:2005 specifies the user Test Suite Structure and Test Purposes for implementations of the DSS2 protocol feature “Peak cell rate modification by the connection owner” in B-ISDN. It applies to the user side at the T reference point, or at a coincident S/T reference point, for implementations conforming to EN 301 003-1.

The document is organized as a conformance-testing specification. It starts with scope and references, then defines terms and abbreviations, then gives the TSS, the TP set, compliance rules for ATS production, and the minimum method expected for a comprehensive testing service.

What are the key requirements of SIST EN 301 003-3 V1.1.3:2005?

The main requirement of SIST EN 301 003-3 V1.1.3:2005 is that tests shall be structured around the TSS in clause 4 and the TP set in clause 5. Figure 1 shows the test group structure, and Table 1 defines the TP naming pattern. This matters because test cases need stable identifiers and a clear link to the behavior being checked.

1) The TP set is built from EN 301 003-1 and EN 301 003-2

Clause 5.1.2 says the TPs are based on EN 301 003-1, and clause 5.1.3 says they were generated by analyzing the base standard together with the PICS specification EN 301 003-2. In practice, this means the test cases are not free-standing - they are tied to declared implementation features and to the conformance statements used to select or deselect tests.

2) The TPs focus on observable behavior

Clause 5.1.3 limits the TPs to externally observable conformance behavior and to situations likely to occur in real implementations. For a tester, that means the standard is aimed at what the implementation sends, receives, and how it changes call state, not internal design choices.

3) Call-state checking is part of the test logic

Clause 5.1.4 explains that many TPs end in a specific call state and that this state is confirmed using a STATUS ENQUIRY and STATUS exchange, with the call state reported in the Call state information element. This matters because a test does not end just when the right message is sent - it also has to verify that the implementation reached the expected state.

4) The user-side tests are split into requesting and responding roles

Clause 5.2 separates the tests into signaling procedures at the coincident S/T and T reference points, then into modification procedures at the requesting entity and at the responding entity. In practice, a test campaign needs coverage for both sides of the modification exchange, because the same feature behaves differently depending on whether the implementation initiates or answers the request.

5) The TPs cover normal behavior, timers, and error handling

For the requesting entity, clause 5.2.1.1 includes valid behavior, timer handling, and error conditions. For the responding entity, clause 5.2.1.2 uses the same three categories. This is important because conformance is not only about successful modification - it also checks timer expiry, malformed messages, unused call references, missing or invalid information elements, and the required response to each case.

6) Error behavior depends on message flags and information-element handling

Across the TP set, the reactions vary according to indicators such as MSG_flag, IE_flag, IE_AI, and Broadband report type. Practically, this means testers must pay attention to how the implementation handles message content, whether it clears the call, reports status, discards information, or ignores the message, because different combinations lead to different expected responses.

7) ATS compliance has explicit rules

Clause 6 says a compliant ATS shall consist of the full TP set or a permitted subset, use an appropriate subset of the TSS, keep the same naming conventions, preserve the mapping between TSS groups, TPs, and PICS entries, and comply with ISO/IEC 9646-2. This matters for labs because test selection and deselection must remain traceable to the published TP structure.

8) A comprehensive testing service must use the Remote test method

Clause 7 requires at least the Remote test method from ISO/IEC 9646-2 for any organization claiming a comprehensive testing service for equipment conforming to EN 301 003-1. For buyers and quality managers, that sets the baseline method expected from a full-service conformance lab.

What terms does SIST EN 301 003-3 V1.1.3:2005 define?

• Abstract Test Method (ATM) - The method used to apply and observe conformance tests from outside the implementation under test.
• Abstract Test Suite (ATS) - The collection of abstract test cases built from the defined TPs.
• Implementation Under Test (IUT) - The protocol implementation being examined for conformance.
• Protocol Implementation Conformance Statement (PICS) - The statement that records which features and options an implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Extra implementation information needed to execute and select tests correctly.
• Peak Cell Rate (PCR) - The cell-rate characteristic being modified by the connection owner.
• Test Purpose (TP) - A statement of the behavior that a test case is intended to check.
• Test Suite Structure (TSS) - The organization of the tests into groups and subgroups.

Who uses SIST EN 301 003-3 V1.1.3:2005?

SIST EN 301 003-3 V1.1.3:2005 is used by conformance test designers, protocol implementers, and certification or verification labs working on B-ISDN DSS2 user-side behavior. It is also relevant to quality managers and buyers who need to understand what a vendor test claim should cover for Peak cell rate modification by the connection owner.

The standard is especially relevant when preparing ATS material, selecting tests from a PICS, or checking whether a product supports the modification procedures at the requesting or responding entity. It is also useful for organizations that provide testing services for network equipment claiming conformance to EN 301 003-1.

Which standards are used with SIST EN 301 003-3 V1.1.3:2005?

• EN 301 003-1 - The base protocol specification for Peak cell rate modification by the connection owner; the TPs are derived from it.
• EN 301 003-2 - The PICS proforma specification used to relate test cases to declared implementation features.
• EN 300 443-1 - Provides the broader B-ISDN user-network interface layer 3 context and the call-state procedure used for confirming final states.
• ETS 300 406 - Gives the testing and specification methodology used when generating practical conformance tests.
• ISO/IEC 9646-1 - Supplies the general concepts for conformance testing terminology such as IUT, PICS, PIXIT, and TP.
• ISO/IEC 9646-2 - Defines ATS specification rules and the Remote test method.
• ITU-T Recommendation I.413 - Defines the B-ISDN user-network interface reference points used in the scope.
• ITU-T Recommendation Q.2963.1 - The underlying DSS2 connection modification behavior for Peak cell rate modification by the connection owner.

What does the SIST EN 301 003-3 V1.1.3:2005 document contain?

SIST EN 301 003-3 V1.1.3:2005 contains a TSS, a TP naming convention, and detailed TP sets for valid behavior, timers, and error conditions. Clause 4 includes the overall test suite structure in Figure 1, and clause 5 organizes the tests by requesting and responding entity.

The document also contains the rules for confirming call state during tests, including the use of STATUS ENQUIRY and STATUS exchanges. In addition, clause 6 gives ATS compliance rules, and clause 7 states the minimum Remote test method for a comprehensive testing service.

For implementers and testers, the practical value is in the concrete TP descriptions for message exchange and error handling at specific call states such as U0, U10, U11, and U13. That material tells a test team what to stimulate, what response to expect, and what state the implementation should end in.

SLOVENSKI STANDARD
01-julij-2005
âLURNRSDVRYQRGLJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL%,6'13URWRNRO
GLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66.DUDNWHULVWLNH]YH]H3ULODJDMDQMH
WHPHQVNHFHOLþQHKLWURVWLSULODVWQLNX]YH]HGHO=JUDGEDSUHVNXãDOQHJDQL]DLQ
QDPHQLSUHVNXãDQMD766 736SHFLILNDFLMD]DXSRUDEQLND
Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling
System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification
by the connection owner; Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
Ta slovenski standard je istoveten z: EN 301 003-3 Version 1.1.3
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Broadband Integrated Services Digital Network (B-ISDN);
Digital Subscriber Signalling System No. two (DSS2) protocol;
Connection characteristics;
Peak cell rate modification by the connection owner;
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
2 ETSI EN 301 003-3 V1.1.3 (1999-11)
Reference
DEN/SPS-05152-3 (9acr0ie0.PDF)
Keywords
ATM, B-ISDN, DSS2, ISDN, TSS&TP, user, UNI,
broadband
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.:[phone] Fax:[phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
[e-mail]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [e-mail]
Important notice
This ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.
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 1999.
All rights reserved.
ETSI
3 ETSI EN 301 003-3 V1.1.3 (1999-11)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope .5
2 References.5
3 Definitions and abbreviations .6
3.1 Definitions.6
3.1.1 Definitions related to conformance testing .6
3.1.2 Definitions related to EN 301 003-1.6
3.2 Abbreviations .6
4 Test Suite Structure (TSS) .7
5 Test Purposes (TP).7
5.1 Introduction .7
5.1.1 TP naming convention .7
5.1.2 Source of TP definition.7
5.1.3 Test strategy.8
5.1.4 Test of call states .8
5.2 TPs for the Peak cell rate modification, user.8
5.2.1 Signalling procedures at the coincident S /T and at the T reference points .8
B B B
5.2.1.1 Modification procedures at the requesting entity. .8
5.2.1.1.1 Valid behaviour (01).8
5.2.1.1.2 Timers (02).9
5.2.1.1.3 Handling of error conditions (03).9
5.2.1.2 Modification procedures at the responding entity .12
5.2.1.2.1 Valid behaviour (04).12
5.2.1.2.2 Timers (05).12
5.2.1.2.3 Handling of error conditions (06).12
6 Compliance.17
7 Requirements for a comprehensive testing service.17
Bibliography.18
History .19
ETSI
4 ETSI EN 301 003-3 V1.1.3 (1999-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. 2 (DSS2)
protocol specification for the B-ISDN Peak cell rate modification by the connection owner, as identified below:
Part 1: "Protocol specification [ITU-T Recommendation Q.2963.1 [8] (1996), modified]";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network".
National transposition dates
Date of adoption of this EN: 29 October 1999
Date of latest announcement of this EN (doa): 31 January 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 July 2000
Date of withdrawal of any conflicting National Standard (dow): 31 July 2000
ETSI
5 ETSI EN 301 003-3 V1.1.3 (1999-11)
1 Scope
This third part of EN 301 003 specifies the user Test Suite Structure and Test Purposes (TSS&TP) for the T reference
B
point or coincident S and T reference point (as defined in ITU-T Recommendation I.413 [5]) of implementations
B B
conforming to the standards for the signalling user-network layer 3 specification for Peak cell rate modification by the
connection owner of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the pan-European Broadband
Integrated Services Digital Network (B-ISDN), EN 301 003-1 [3].
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile conformance
testing specifications; Standardization methodology".
[2] EN 300 443-1 (V1.3): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3
specification for basic call/bearer control; Part 1: Protocol specification [ITU-T Recommendation
Q.2931 (1995), modified]".
[3] EN 301 003-1 (V1.1): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate
modification by the connection owner; Part 1: Protocol specification [ITU-T Recommendation
Q.2963.1 (1996), modified]".
[4] EN 301 003-2 (V1.1): "Broadband Integrated Services Digital Network (B-ISDN); Digital
Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate
modification by the connection owner; Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification".
[5] ITU-T Recommendation I.413 (1993): "B-ISDN user-network interface".
[6] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[8] ITU-T Recommendation Q.2963.1: "Digital Subscriber Signalling System No. 2 - Connection
modification: Peak cell rate modification by the connection owner".
ETSI
6 ETSI EN 301 003-3 V1.1.3 (1999-11)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 301 003-1 [3] and EN 300 443-1 [2]
and the following apply:
3.1.1 Definitions related to conformance testing
abstract test case: refer to ISO/IEC 9646-1 [6]
Abstract Test Method (ATM): refer to ISO/IEC 9646-1 [6]
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [6]
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [6]
lower tester: refer to ISO/IEC 9646-1 [6]
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [6]
PICS proforma: refer to ISO/IEC 9646-1 [6]
Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [6]
PIXIT proforma: refer to ISO/IEC 9646-1 [6]
Test Purpose (TP): refer to ISO/IEC 9646-1 [6]
3.1.2 Definitions related to EN 301 003-1
user: DSS2 protocol entity at the User side of the user-network interface where a T reference point or coincident S
B B
and T reference point applies
B
user (S /T ): DSS2 protocol entity at the User side of the user-network interface where a coincident S and T reference
B B B B
point applies
user (T ): DSS2 protocol entity at the User side of the user-network interface where a T reference point applies (user is
B B
a private ISDN)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CR Call Reference
IE_AI Information element action indicator
IE_flag Information element instruction indicator flag
IUT Implementation Under Test
PCR Peak Cell Rate
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
U0 Null link state
U1 Call Initiated link state
U10 Active link state
U12 Disconnect Indication call state
ETSI
7 ETSI EN 301 003-3 V1.1.3 (1999-11)
U13 Modify Requested call state
U3 Outgoing Call Proceeding link state
U4 Call Delivered link state
U6 Call Present link state
U7 Call Received link state
U8 Connect Request link state
U9 Incoming Call Proceeding link state
4 Test Suite Structure (TSS)
Signalling procedures at the coincident S /T and at the T reference points
B B B
Modification procedures at the requesting entity.
Valid behaviour. (01)
Handling of error conditions .(02)
Timers .(03)
Modification procedures at the responding entity.
Valid behaviour. (04)
Handling of error conditions .(05)
Timers .(06)
Figure 1: Test suite structure
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
5.1.1 TP naming convention
TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= layer + type of IUT: "MODU" for MODification, IUT = User
= group number: two character field representing the group reference
according to TSS
= sequential number: (01-99)
5.1.2 Source of TP definition
The TPs are based on EN 301 003-1 [3].
ETSI
8 ETSI EN 301 003-3 V1.1.3 (1999-11)
5.1.3 Test strategy
As the base standard EN 301 003-1 [3] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the PICS specification EN 301 003-2 [4].
The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and are
limited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [1]).
5.1.4 Test of call states
Many TPs include a reference to the IUT's final call state after the realization of the TP. In these cases the TP includes
the requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particular
call state shall be realized by following the procedures described in subclause 5.6.11 of EN 300 443-1 [2]. According to
these procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS message
indicating, in the fifth octet of the Call state information element, the current call state of the IUT. This exchange of
messages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state.
This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improve
the readability.
5.2 TPs for the Peak cell rate modification, user
All PICS items referred to in this subclause are as specified in EN 301 003-2 [4] unless indicated otherwise by another
numbered reference.
Unless specified:
- the messages indicated are valid and contain at least the mandatory information elements and possibly optional
information elements;
- the information elements indicated are valid and contain at least the mandatory parameters and possibly optional
parameters.
5.2.1 Signalling procedures at the coincident S /T and at the
B B
T reference points
B
NOTE: Unless otherwise specified, the connection defined by the requested ATM traffic descriptor is available
for use.
5.2.1.1 Modification procedures at the requesting entity.
Test purposes for EN 301 003-1 [3] subclause 9.1.
Selection:The IUT support the requirements for the modification requesting entity. PICS: R 2.1
5.2.1.1.1 Valid behaviour (01)
MODU_01_01
Ensure that the IUT in U10, in order to initiate a PCR modification request,
- sends a MODIFY REQUEST message and enters U13.
MODU_01_02
Ensure that the IUT in U13, on receipt of a MODIFY ACKNOWLEDGE message including a Broadband report type
information element indicating "modification confirmation",
- sends a CONNECTION AVAILABLE message and enters U10.
MODU_01_03
Ensure that the IUT in U13, on receipt of a MODIFY ACKNOWLEDGE message without Broadband report type
information element,
- sends no message and enters U10.
ETSI
9 ETSI EN 301 003-3 V1.1.3 (1999-11)
MODU_01_04
Ensure that the IUT in U13, on receipt of a MODIFY REJECT message,
- sends no message and enters U10.
MODU_01_05
Ensure that the IUT in U13, on receipt of a STATUS message (call state: 10, cause value: 97 or 101, diagnostic
""identifying of the MODIFY REQUEST message),
- sends no message and enters U10.
MODU_01_06
Ensure that the IUT in U13, on receipt of a STATUS message (call state: 10, cause value: 97 or 101, without diagnostic
""identifying of the MODIFY REQUEST message),
- sends a STATUS ENQUIRY message and remains in U13.
MODU_01_07
Ensure that the IUT in U13, (having sent a STATUS ENQUIRY message), on receipt of a STATUS message (call
state: 14),
- sends no message and remains in U13.
MODU_01_08
Ensure that the IUT in U13, (having sent a STATUS ENQUIRY message), on receipt of a STATUS message (call
state: 10),
- sends no message and enters U10.
MODU_01_09
Ensure that the IUT in U13, on receipt of a RELEASE message,
- enters U12.
MODU_01_10
Ensure that the IUT in U13, to indicate the receipt of a clearing indication,
- sends a RELEASE message and enters U11.
5.2.1.1.2 Timers (02)
MODU_02_01
Ensure that the IUT in U13, on expiry of timer T360,
- sends a RELEASE message (cause value: 102) and enters U11.
5.2.1.1.3 Handling of error conditions (03)
MODU_03_01
Ensure that the IUT in U13, on receipt of a MODIFY ACKNOWLEDGE m
...