SIST EN 300 403-6 V1.2.2:2005

Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 6: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

Produce a new edition of the network side TSS&TP that incorporates changes necessitated by the maintenance work of STF122 on the ATS part

Digitalno omrežje z integriranimi storitvami (ISDN) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – Signalizacijska omrežna plast za krmiljenje vodovnega osnovnega klica – 6. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – Specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• ICS: 35.100.30 - Network layer
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Mandate: T-234A
• Ref Project: ETSI EN 300 403-6 V1.2.2 (2000-02) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 6: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

Standards Content (Sample)

SLOVENSKI STANDARD
01-januar-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±3URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66±6LJQDOL]DFLMVNDRPUHåQDSODVW]DNUPLOMHQMHYRGRYQHJD
RVQRYQHJDNOLFD±GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQSUHVNXãDQMD
766 73±6SHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 6: Test
Suite Structure and Test Purposes (TSS&TP) specification for the network
Ta slovenski standard je istoveten z: EN 300 403-6 Version 1.2.2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.100.30 Omrežni sloj Network layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Signalling network layer for circuit-mode basic call control;
Part 6: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
2 ETSI EN 300 403-6 V1.2.2 (2000-02)
Reference
REN/SPAN-05157-6
Keywords
Basic, DSS1, ISDN, layer 3, network, testing,
TSS&TP
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 shall 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 2000.
All rights reserved.
ETSI
3 ETSI EN 300 403-6 V1.2.2 (2000-02)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
3 Definitions and abbreviations .7
3.1 Definitions.7
3.1.1 Definitions related to conformance testing .7
3.1.2 Definitions related to EN 300 403-1.7
3.2 Abbreviations .8
4 Test Suite Structure (TSS) .8
5 Test Purposes (TP).10
5.1 Introduction .10
5.1.1 TP naming convention .10
5.1.2 Source of TP definition.11
5.1.3 TP structure.11
5.1.4 Test strategy.12
5.1.5 Test of call states .12
5.1.6 Test of point-to-multipoint configurations.12
5.1.7 Test of inopportune and syntactically invalid behaviour .12
5.2 TPs for the basic call control, layer 3, network .12
5.2.1 Null call state N00 .12
5.2.1.1 Valid.12
5.2.1.1.1 Outgoing call .12
5.2.1.1.2 Incoming call - point-to-point configuration.17
5.2.1.1.3 Incoming call - point-to-multipoint configuration .18
5.2.1.1.4 Call rearrangement .20
5.2.1.2 Inopportune .21
5.2.1.3 Syntactically invalid .22
5.2.2 Overlap Sending call state N02.23
5.2.2.1 Valid.23
5.2.2.2 Inopportune .25
5.2.2.3 Syntactically invalid .26
5.2.3 Outgoing Call Proceeding call state N03.27
5.2.3.1 Valid.27
5.2.3.2 Inopportune .28
5.2.3.3 Syntactically invalid .29
5.2.4 Call Delivered call state N04 .30
5.2.4.1 Valid.30
5.2.4.2 Inopportune .31
5.2.4.3 Syntactically invalid .31
5.2.5 Call Present call state N06 .33
5.2.5.1 Valid.33
5.2.5.1.1 Point-to-point configuration .33
5.2.5.1.2 Point-to-multipoint configuration .37
5.2.5.2 Inopportune .39
5.2.5.3 Syntactically invalid .40
5.2.6 Call Received call state N07.40
5.2.6.1 Valid.40
5.2.6.1.1 Point-to-point configuration .40
5.2.6.1.2 Point-to-multipoint configuration .41
5.2.6.2 Inopportune .43
5.2.6.3 Syntactically invalid .45
5.2.7 Incoming Call Proceeding call state N09.46
ETSI
4 ETSI EN 300 403-6 V1.2.2 (2000-02)
5.2.7.1 Valid.46
5.2.7.1.1 Point-to-point configuration .46
5.2.7.1.2 Point-to-multipoint configuration .47
5.2.7.2 Inopportune .49
5.2.7.3 Syntactically invalid .51
5.2.8 Active call state N10 (Incoming call) .52
5.2.8.1 Valid.52
5.2.8.2 Inopportune .54
5.2.8.3 Syntactically invalid .55
5.2.9 Active call state N10 (Outgoing call).56
5.2.9.1 Valid.56
5.2.9.2 Inopportune .58
5.2.9.3 Syntactically invalid .60
5.2.10 Disconnect Indication call state N12 (Incoming call).61
5.2.10.1 Valid.61
5.2.10.2 Inopportune .61
5.2.10.3 Syntactically invalid .62
5.2.11 Disconnect Indication call state N12 (Outgoing call) .63
5.2.11.1 Valid.63
5.2.11.2 Inopportune .64
5.2.11.3 Syntactically invalid .64
5.2.12 Release Request call state N19 (Incoming call).65
5.2.12.1 Valid.65
5.2.12.2 Inopportune .66
5.2.12.3 Syntactically invalid .67
5.2.13 Release Request call state N19 (Outgoing call).67
5.2.13.1 Valid.67
5.2.13.2 Inopportune .68
5.2.13.3 Syntactically invalid .69
5.2.14 Call Abort call state N22 .70
5.2.15 Overlap Receiving call state N25.71
5.2.15.1 Valid.71
5.2.15.1.1 Point-to-point configuration .71
5.2.15.1.2 Point-to-multipoint configuration .72
5.2.15.2 Inopportune .75
5.2.15.3 Syntactically invalid .77
5.2.16 Restart Null call state R00 (Incoming call).78
5.2.16.1 Valid.78
5.2.16.2 Inopportune .79
5.2.16.3 Syntactically invalid .79
5.2.17 Restart null call state R00 (Outgoing call).81
5.2.17.1 Valid.81
5.2.17.2 Inopportune .82
5.2.17.3 Syntactically invalid .82
5.2.18 Restart Request call state R01.83
5.2.18.1 Valid.83
5.2.18.2 Inopportune .84
5.2.18.3 Syntactically invalid .84
5.2.19 Message segmentation procedure .86
5.2.19.1 Valid.86
5.2.19.2 Inopportune .86
5.2.19.3 Syntactically invalid .87
6 Compliance .87
7 Requirements for a comprehensive testing service.87
History.88
ETSI
5 ETSI EN 300 403-6 V1.2.2 (2000-02)
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 Services and
Protocols for Advanced Networks (SPAN).
The present document is part 6 of a multi-part EN covering the Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control, as
identified below:
Part 1: "Protocol specification [ITU-T Recommendation Q.931 (1993), modified]";
Part 2: "Specification and Description Language (SDL) diagrams";
Part 3: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 4: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 5: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user";
Part 6: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 7: "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: 28 January 2000
Date of latest announcement of this EN (doa): 30 April 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 October 2000
Date of withdrawal of any conflicting National Standard (dow): 31 October 2000
ETSI
6 ETSI EN 300 403-6 V1.2.2 (2000-02)
1 Scope
The present document specifies the network Test Suite Structure and Test Purposes (TSS&TP) for the T reference point
or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [9]) of implementations conforming
to the standards for the signalling network layer for circuit-mode basic call control of the Digital Subscriber Signalling
System No. one (DSS1) protocol for the pan-European Integrated Services Digital Network (ISDN), EN 300 403-1 [1]
and ETS 300 403-2 [2].
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. Other parts specify the TSS&TP and
the ATS and partial PIXIT proforma for the User side of the T reference point or coincident S and T reference point of
implementations conforming to EN 300 403-1 [1] and ETS 300 403-2 [2].
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] EN 300 403-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;
Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".
[2] ETS 300 403-2 (1995): "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call
control; Part 2: Specification and Description Language (SDL) diagrams".
[3] ETS 300 403-3 (1996): "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call
control; Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification".
[4] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
[5] ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract Test Suite specification".
[6] ISO/IEC 9646-3 (1997): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[7] ITU-T Recommendation E.164 (1997): "The international public telecommunication numbering
plan".
[8] ITU-T Recommendation I.112 (1993): "Vocabulary for terms for ISDNs".
[9] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
ETSI
7 ETSI EN 300 403-6 V1.2.2 (2000-02)
3 Definitions and abbreviations
3.1 Definitions
3.1.1 Definitions related to conformance testing
For the purposes of the present document, the following terms and definitions apply, in addition to those given in
EN 300 403-1 [1].
abstract test case: refer to ISO/IEC 9646-1 [4].
Abstract Test Method (ATM): refer to ISO/IEC 9646-1 [4].
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [4].
active test: test case where the IUT is required to send a particular message, but not in reaction to a received message.
This would usually involve the use of PIXIT information to see how this message can be generated and quite often is
specified in an ATS using an implicit send event.
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [4].
implicit send event: refer to ISO/IEC 9646-3 [6].
lower tester: refer to ISO/IEC 9646-1 [4].
passive test: test case where the IUT is required to respond to a protocol event (e.g. received message) with another
protocol event (sends message) and which normally does not require any special operator intervention such as is
associated with the implicit send event.
point of control and observation: refer to ISO/IEC 9646-1 [4].
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [4].
PICS proforma: refer to ISO/IEC 9646-1 [4].
Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [4].
PIXIT proforma: refer to ISO/IEC 9646-1 [4].
system under test: refer to ISO/IEC 9646-1 [4].
Test Purpose (TP): refer to ISO/IEC 9646-1 [4].
3.1.2 Definitions related to EN 300 403-1
Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [8], definition 308.
ISDN number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [7].
network: DSS1 protocol entity at the Network side of the user-network interface where a T reference point or
coincident S and T reference point applies.
network (S/T): DSS1 protocol entity at the Network side of the user-network interface where a coincident S and T
reference point applies.
network (T): DSS1 protocol entity at the Network side of the user-network interface where a T reference point applies
(user is the private ISDN).
ETSI
8 ETSI EN 300 403-6 V1.2.2 (2000-02)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CES Connection Endpoint Suffix
DSS1 Digital Subscriber Signalling System No. one
I Inopportune stimulus
ISDN Integrated Services Digital Network
IUT Implementation Under Test
N00 Null call state
N02 Overlap Sending call state
N03 Outgoing Call Proceeding call state
N04 Call Delivered call state
N06 Call Present call state
N07 Call Received call state
N09 Incoming Call Proceeding call state
N10 Active call state
N12 Disconnect Indication call state
N19 Release Request call state
N22 Call Abort call state
N25 Overlap Receiving call state
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
R00 Restart Null call state
R01 Restart Request call state
S Syntactically invalid stimulus
SEG message Segmentation procedure
TP Test Purpose
TSS Test Suite Structure
V Valid stimulus
4 Test Suite Structure (TSS)
• Null call state N00
• Valid
• Outgoing call
• Incoming call - point-to-point configuration
• Incoming call - point-to-multipoint configuration
• Call rearrangement
• Inopportune
• Syntactically invalid
• Overlap Sending call state N02
• Valid
• Inopportune
• Syntactically invalid
• Outgoing Call Proceeding call state N03
• Valid
• Inopportune
• Syntactically invalid
• Call Delivered call state N04
• Valid
• Inopportune
• Syntactically invalid
ETSI
9 ETSI EN 300 403-6 V1.2.2 (2000-02)
• Call Present call state N06
• Valid
• Point-to-point configuration
• Point-to-multipoint configuration
• Inopportune
• Syntactically invalid
• Call Received call state N07
• Valid
• Point-to-point configuration
• Point-to-multipoint configuration
• Inopportune
• Syntactically invalid
• Incoming Call Proceeding call state N09
• Valid
• Point-to-point configuration
• Point-to-multipoint configuration
• Inopportune
• Syntactically invalid
• Active call state N10 (Incoming call)
• Valid
• Inopportune
• Syntactically invalid
• Active call state N10 (Outgoing call)
• Valid
• Inopportune
• Syntactically invalid
• Disconnect Indication call state N12 (Incoming call)
• Valid
• Inopportune
• Syntactically invalid
• Disconnect Indication call state N12 (Outgoing call)
• Valid
• Inopportune
• Syntactically invalid
• Release Request call state N19 (Incoming call)
• Valid
• Inopportune
• Syntactically invalid
Figure 1 (sheet 1 of 2): Test suite structure
ETSI
10 ETSI EN 300 403-6 V1.2.2 (2000-02)
• Release Request call state N19 (Outgoing call)
• Valid
• Inopportune
• Syntactically invalid
• Call Abort call state N22
• Overlap Receiving call state N25
• Valid
• Point-to-point configuration
• Point-to-multipoint configuration
• Inopportune
• Syntactically invalid
• Restart Null call state R00 (Incoming call)
• Valid
• Inopportune
• Syntactically invalid
• Restart Null call state R00 (Outgoing call)
• Valid
• Inopportune
• Syntactically invalid
• Restart Request call state R01
• Valid
• Inopportune
• Syntactically invalid
• Message segmentation procedure
• Valid
• Inopportune
• Syntactically invalid
Figure 1 (sheet 2 of 2): 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 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 1).
ETSI
11 ETSI EN 300 403-6 V1.2.2 (2000-02)
Table 1: TP identifier naming convention scheme
Identifier: ___
= layer + type of IUT: e.g. "L3N" for layer 3, IUT = network
= call state: e.g. N10 for Active call state
= group: one character field representing the group reference
according to TSS
V: Valid stimulus
I: Inopportune stimulus
S: Syntactically invalid stimulus
= sequential number: (001-999)
5.1.2 Source of TP definition
The TPs are based on EN 300 403-1 [1] and ETS 300 403-2 [2].
5.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used which is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2.
Table 2: Structure of a single TP
TP part Text Example
Header tab seetable1
subclause 2.3.4
Ensure that the IUT in the
Stimulus
N00, N10, etc.
see below for message structure on receipt of a XXXX message (see
note 2)
or to request a.
Reaction sends, saves, does, etc.
using en bloc sending, etc.
if the action is sending
see below for message structure
, etc.
and remains in the same state
or and enters state
Message SETUP, FACILITY, CONNECT, etc.
message (see note 2)
structure
a) with a Bearer capability, Facility, etc.
information element
b) indicating in the
and back toa)orb)
NOTE 1: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one
TP to the next.
NOTE 2: All messages shall be considered as "valid and compatible" unless otherwise specified in the test
purpose.
ETSI
12 ETSI EN 300 403-6 V1.2.2 (2000-02)
5.1.4 Test strategy
As the base standard EN 300 403-1 [1] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the PICS specification ETS 300 403-3 [3]. The criteria applied include the
following:
- only the requirements from the point of view of the T or coincident S and T reference point are considered;
- whether or not a test case can be built from the TP is not considered.
5.1.5 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.8.10 of EN 300 403-1 [1]. According to
these procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS message
indicating, in the third 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.1.6 Test of point-to-multipoint configurations
In subclauses 5.2.1, 5.2.5, 5.2.6, 5.2.7 and 5.2.15 (call states Null N00, Call Present N06, Call Received N07, Incoming
Call Proceeding N09 and Overlap Receiving N25) a distinction is made between point-to-point and point-to-multipoint
configurations. In the case of a point-to-multipoint configuration several terminals may be attached to one basic access
interface. Each terminal will use a different Connection Endpoint Suffix (CES). To reflect this in the TPs the CES for
which a message is received or sent (e.g. ". on receipt of an ALERTING message for CES1.") is named explicitly
where this clarification is needed.
5.1.7 Test of inopportune and syntactically invalid behaviour
In the test groups for inopportune and syntactically invalid behaviour the procedures as described in subclause 5.8 of
EN 300 403-1 [1] are tested. This is done in each call state with one message for each of the described error cases.
Messages have been chosen that are, if they are received without the inopportune or erroneous coding, expected
messages in the call states under test.
Test purposes for inopportune behaviour that is described outside the subclause 5.8 of EN 300 403-1 [1] are found in
the valid test groups. This was done, as these procedures are seen more as a part of the basic call procedures than as a
part of the error handling procedures.
5.2 TPs for the basic call control, layer 3, network
All PICS items referred to in this subclause are as specified in ETS 300 403-3 [3] unless indicated otherwise by another
numbered reference.
5.2.1 Null call state N00
5.2.1.1 Valid
5.2.1.1.1 Outgoing call
L3N_N00_V_001 subclause 5.1.1
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message during an all channels busy condition,
sends a RELEASE COMPLETE message with a Cause information element indicating the cause value 34 "no
circuit/channel available" and remains in the Null call state N00.
ETSI
13 ETSI EN 300 403-6 V1.2.2 (2000-02)
L3N_N00_V_002 subclauses 5.1.2 a) and 5.1.3
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message without Called party number and
Sending complete information element and with the Channel identification information element indicating a B-channel
that is available and indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable", sends
SETUP ACKNOWLEDGE message with the Channel identification information element indicating the requested B-
channel and indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable" and enters the
Overlap Sending call state N02.
L3N_N00_V_003 subclauses 5.1.2 a) and 5.1.5.1
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with a Called party number information
element providing the complete called party information, with a Sending complete information element and with the
Channel identification information element indicating a B-channel that is available and indicating in the
preferred/exclusive bit "exclusive: only the indicated channel is acceptable", sends CALL PROCEEDING message with
the Channel identification information element indicating the requested B-channel and indicating in the
preferred/exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceeding
call state N03.
L3N_N00_V_004 subclause 5.1.2 a)
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with the Channel identification
information element indicating a B-channel that is not available and indicating in the preferred/exclusive bit "exclusive:
only the indicated channel is acceptable", sends a RELEASE COMPLETE message with a Cause information element
indicating the cause value 34 "no circuit/channel available" or 44 "requested circuit/channel not available" and remains
in the Null call state.
L3N_N00_V_005 subclause 5.1.2 a)
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with the Channel identification
information element indicating a B-channel that is not subscribed and indicating in the preferred/exclusive bit
"exclusive: only the indicated channel is acceptable", sends a RELEASE COMPLETE message with a Cause
information element indicating the cause value 82 "identified channel does not exist" and remains in the Null call state.
Selection:IUT is a primary rate access. PICS: R 6.2.
L3N_N00_V_006 subclauses 5.1.2 b) and 5.1.3
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message without Called party number and
Sending complete information element and with the Channel identification information element indicating a B-channel
that is available and indicating in the preferred/exclusive bit "indicated channel is preferred", sends a SETUP
ACKNOWLEDGE message with the Channel identification information element indicating the requested B-channel and
indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Overlap
Sending call state N02.
L3N_N00_V_007 subclauses 5.1.2 b) and 5.1.3
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message without Called party number and
Sending complete information element and with the Channel identification information element indicating a B-channel
that is not available and indicating in the preferred/exclusive bit "indicated channel is preferred", sends a SETUP
ACKNOWLEDGE message with the Channel identification information element indicating a B-channel that is available
and indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Overlap
Sending call state N02.
L3N_N00_V_008 subclauses 5.1.2 b) and 5.1.5.1
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with a Called party number information
element providing the complete called party information, with a Sending complete information element and with the
Channel identification information element indicating a B-channel that is available and indicating in the
preferred/exclusive bit "indicated channel is preferred", sends CALL PROCEEDING message with the Channel
identification information element indicating the requested B-channel and indicating in the preferred/exclusive bit
"exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceeding call state N03.
ETSI
14 ETSI EN 300 403-6 V1.2.2 (2000-02)
L3N_N00_V_009 subclauses 5.1.2 b) and 5.1.5.1
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with a Called party number information
element providing the complete called party information, with a Sending complete information element and with the
Channel identification information element indicating a B-channel that is not available and indicating in the
preferred/exclusive bit "indicated channel is preferred", sends CALL PROCEEDING message with the Channel
identification information element indicating a B-channel that is available and indicating in the preferred/exclusive bit
"exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceeding call state N03.
L3N_N00_V_010 subclause 5.1.2 b)
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with the Channel identification
information element indicating a B-channel and indicating in the preferred/exclusive bit "indicated channel is preferred",
when there is no channel available, sends a RELEASE COMPLETE message with a Cause information element
indicating the cause value 34 "no circuit/channel available" or 44 "requested circuit/channel not available" and remains
in the Null call state.
L3N_N00_V_011 subclauses 5.1.2 c) and 5.1.3
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message without Called party number and
Sending complete information element and with the Channel identification information element indicating in the Info
channel selection "any channel", sends a SETUP ACKNOWLEDGE message with the Channel identification
information element indicating a B-channel that is available and indicating in the preferred/exclusive bit "exclusive: only
the indicated channel is acceptable" and enters the Overlap Sending call state N02.
L3N_N00_V_012 subclauses 5.1.2 c) and 5.1.3
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message without Called party number and
Sending complete information element and without the Channel identification information element, sends a SETUP
ACKNOWLEDGE message with the Channel identification information element indicating a B-channel that is available
and indicating in the preferred/exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Overlap
Sending call state N02.
L3N_N00_V_013 subclauses 5.1.2 c) and 5.1.5.1
Ensure that the IUT in the Null call state N00, on receipt of a SETUP message with a Called party number information
element providing the complete called party information, with a Sending complete information element and with the
Channel identification information element indicating in the Info channel selection "any channel", sends CALL
PROCEEDING message with the Channel identification information element indicating a B-channel that is available
and indicating in the preferred/exclusive bit "exclusive: on
...