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

TSS&TP

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-May-1998
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jun-1998
Due Date
01-Jun-1998
Completion Date
01-Jun-1998
Mandate

Buy Standard

Standard
SIST ETS 300 403-6:1998
English language
87 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST ETS 300 403-6:1998
01-junij-1998

'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 3URWRNROGLJLWDOQHQDURþQLãNH

VLJQDOL]DFLMHãW '66 6LJQDOL]DFLMVNDRPUHåQDSODVW]DNUPLOMHQMHYRGRYQHJD

RVQRYQHJDNOLFDGHO=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: ETS 300 403-6 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.100.30 Omrežni sloj Network layer
SIST ETS 300 403-6:1998 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ETS 300 403-6:1998
---------------------- Page: 2 ----------------------
SIST ETS 300 403-6:1998
EUROPEAN ETS 300 403-6
TELECOMMUNICATION January 1997
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05093
ICS: 33.020
Key words: ISDN, DSS1, layer 3, testing, TSS&TP, network
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
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: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16

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 1997. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 403-6:1998
Page 2
ETS 300 403-6: January 1997

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 403-6:1998
Page 3
ETS 300 403-6: January 1997
Contents

Foreword .......................................................................................................................................................5

1 Scope ..................................................................................................................................................7

2 Normative references..........................................................................................................................7

3 Definitions............................................................................................................................................8

3.1 Definitions related to conformance testing...........................................................................8

3.2 Definitions related to ETS 300 403-1...................................................................................8

4 Abbreviations.......................................................................................................................................9

5 Test Suite Structure (TSS) ................................................................................................................10

6 Test purposes (TP) ...........................................................................................................................11

6.1 Introduction ........................................................................................................................11

6.1.1 TP naming convention...................................................................................11

6.1.2 Source of TP definition..................................................................................12

6.1.3 TP structure...................................................................................................12

6.1.4 Test strategy..................................................................................................12

6.1.5 Test of call states ..........................................................................................12

6.1.6 Test of point-to-multipoint configurations ......................................................13

6.1.7 Test of inopportune and syntactically invalid behaviour ................................13

6.2 TPs for the basic call control, layer 3, network ..................................................................13

6.2.1 Null call state N00 .........................................................................................13

6.2.1.1 Valid.....................................................................................13

6.2.1.1.1 Outgoing call.........................................13
6.2.1.1.2 Incoming call - point-to-point
configuration .........................................17
6.2.1.1.3 Incoming call - point-to-multipoint
configuration .........................................19
6.2.1.1.4 Call rearrangement ...............................20

6.2.1.2 Inopportune..........................................................................21

6.2.1.3 Syntactically invalid..............................................................22

6.2.2 Overlap Sending call state N02.....................................................................23

6.2.2.1 Valid.....................................................................................23

6.2.2.2 Inopportune..........................................................................25

6.2.2.3 Syntactically invalid..............................................................26

6.2.3 Outgoing Call Proceeding call state N03.......................................................27

6.2.3.1 Valid.....................................................................................27

6.2.3.2 Inopportune..........................................................................28

6.2.3.3 Syntactically invalid..............................................................29

6.2.4 Call Delivered call state N04 .........................................................................30

6.2.4.1 Valid.....................................................................................30

6.2.4.2 Inopportune..........................................................................31

6.2.4.3 Syntactically invalid..............................................................32

6.2.5 Call Present call state N06 ............................................................................33

6.2.5.1 Valid.....................................................................................33

6.2.5.1.1 Point-to-point configuration...................33
6.2.5.1.2 Point-to-multipoint configuration ...........37

6.2.5.2 Inopportune..........................................................................38

6.2.5.3 Syntactically invalid..............................................................39

6.2.6 Call Received call state N07 .........................................................................40

6.2.6.1 Valid.....................................................................................40

6.2.6.1.1 Point-to-point configuration...................40
6.2.6.1.2 Point-to-multipoint configuration ...........41
---------------------- Page: 5 ----------------------
SIST ETS 300 403-6:1998
Page 4
ETS 300 403-6: January 1997

6.2.6.2 Inopportune......................................................................... 43

6.2.6.3 Syntactically invalid ............................................................. 45

6.2.7 Incoming Call Proceeding call state N09...................................................... 46

6.2.7.1 Valid .................................................................................... 46

6.2.7.1.1 Point-to-point configuration .................. 46
6.2.7.1.2 Point-to-multipoint configuration........... 47

6.2.7.2 Inopportune......................................................................... 48

6.2.7.3 Syntactically invalid ............................................................. 51

6.2.8 Active call state N10 (Incoming call)............................................................. 52

6.2.8.1 Valid .................................................................................... 52

6.2.8.2 Inopportune......................................................................... 54

6.2.8.3 Syntactically invalid ............................................................. 55

6.2.9 Active call state N10 (Outgoing call)............................................................. 56

6.2.9.1 Valid .................................................................................... 56

6.2.9.2 Inopportune......................................................................... 58

6.2.9.3 Syntactically invalid ............................................................. 59

6.2.10 Disconnect Indication call state N12 (Incoming call) .................................... 60

6.2.10.1 Valid .................................................................................... 60

6.2.10.2 Inopportune......................................................................... 60

6.2.10.3 Syntactically invalid ............................................................. 61

6.2.11 Disconnect Indication call state N12 (Outgoing call) .................................... 62

6.2.11.1 Valid .................................................................................... 62

6.2.11.2 Inopportune......................................................................... 63

6.2.11.3 Syntactically invalid ............................................................. 64

6.2.12 Release Request call state N19 (Incoming call)........................................... 64

6.2.12.1 Valid .................................................................................... 64

6.2.12.2 Inopportune......................................................................... 65

6.2.12.3 Syntactically invalid ............................................................. 66

6.2.13 Release Request call state N19 (Outgoing call)........................................... 66

6.2.13.1 Valid .................................................................................... 66

6.2.13.2 Inopportune......................................................................... 67

6.2.13.3 Syntactically invalid ............................................................. 68

6.2.14 Call Abort call state N22 ............................................................................... 69

6.2.15 Overlap Receiving call state N25.................................................................. 70

6.2.15.1 Valid .................................................................................... 70

6.2.15.1.1 Point-to-point configuration .................. 70
6.2.15.1.2 Point-to-multipoint configuration........... 71

6.2.15.2 Inopportune......................................................................... 74

6.2.15.3 Syntactically invalid ............................................................. 76

6.2.16 Restart Null call state R00 (Incoming call).................................................... 77

6.2.16.1 Valid .................................................................................... 77

6.2.16.2 Inopportune......................................................................... 78

6.2.16.3 Syntactically invalid ............................................................. 78

6.2.17 Restart null call state R00 (Outgoing call) .................................................... 79

6.2.17.1 Valid .................................................................................... 79

6.2.17.2 Inopportune......................................................................... 80

6.2.17.3 Syntactically invalid ............................................................. 81

6.2.18 Restart Request call state R01..................................................................... 82

6.2.18.1 Valid .................................................................................... 82

6.2.18.2 Inopportune......................................................................... 82

6.2.18.3 Syntactically invalid ............................................................. 83

6.2.19 Message segmentation procedure ............................................................... 84

6.2.19.1 Valid .................................................................................... 84

6.2.19.2 Inopportune......................................................................... 85

6.2.19.3 Syntactically invalid ............................................................. 85

7 Compliance....................................................................................................................................... 86

8 Requirements for a comprehensive testing service ......................................................................... 86

History......................................................................................................................................................... 87

---------------------- Page: 6 ----------------------
SIST ETS 300 403-6:1998
Page 5
ETS 300 403-6: January 1997
Foreword

This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and

Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).

This ETS is part 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one

(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) signalling network layer

for circuit-mode basic call control, as described 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: "TSS&TP specification for the network";
Part 7: "ATS and partial PIXIT proforma specification for the network".
Transposition dates
Date of adoption: 20 December 1996
Date of latest announcement of this ETS (doa): 30 April 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 October 1997
Date of withdrawal of any conflicting National Standard (dow): 31 October 1997
---------------------- Page: 7 ----------------------
SIST ETS 300 403-6:1998
Page 6
ETS 300 403-6: January 1997
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 403-6:1998
Page 7
ETS 300 403-6: January 1997
1 Scope

This sixth part of ETS 300 403 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), ETS 300 403-1 [1] and ETS 300 403-2 [2].

A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol Implementation

eXtra Information for Testing (PIXIT) proforma based on this ETS. 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 ETS 300 403-1 [1] and ETS 300 403-2 [2].

2 Normative references

This ETS incorporates by dated and undated reference, provisions from other publications. These

normative references are cited at the appropriate places in the text and the publications are listed

hereafter. For dated references, subsequent amendments to or revisions 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 403-1 (1995): "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: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[5] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[6] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[7] CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".
[8] ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".
[9] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
---------------------- Page: 9 ----------------------
SIST ETS 300 403-6:1998
Page 8
ETS 300 403-6: January 1997
3 Definitions

For the purposes of this ETS, the following definitions apply, in addition to those given in

ETS 300 403-1 [1]:
3.1 Definitions related to conformance testing
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: A 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: A 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.2 Definitions related to ETS 300 403-1

Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [8], definition 308.

ISDN number: A number conforming to the numbering and structure specified in CCITT

Recommendation E.164 [7].

network: The 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): The DSS1 protocol entity at the Network side of the user-network interface where a

coincident S and T reference point applies.

network (T): The DSS1 protocol entity at the Network side of the user-network interface where a

T reference point applies (user is the private ISDN).
---------------------- Page: 10 ----------------------
SIST ETS 300 403-6:1998
Page 9
ETS 300 403-6: January 1997
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CES Connection Endpoint Suffix
CR Call Reference
DSS1 Digital Subscriber Signalling System No. one
I Inopportune stimulus
ISDN Integrated Services Digital Network
IUT Implementation Under Test
N00 Null call state
N01 Call Initiated 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
N08 Connect Request call state
N09 Incoming Call Proceeding call state
N10 Active call state
N11 Disconnect Request call state
N12 Disconnect Indication call state
N15 Suspend Request call state
N17 Resume Request 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
R02 Restart call state
S Syntactically invalid stimulus
SEG message Segmentation procedure
TP Test Purpose
TSS Test Suite Structure
V Valid stimulus
---------------------- Page: 11 ----------------------
SIST ETS 300 403-6:1998
Page 10
ETS 300 403-6: January 1997
5 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
• 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
---------------------- Page: 12 ----------------------
SIST ETS 300 403-6:1998
Page 11
ETS 300 403-6: January 1997
• 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
6 Test Purposes (TP)
6.1 Introduction
For each test requirement, a TP is defined.
6.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).
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)
---------------------- Page: 13 ----------------------
SIST ETS 300 403-6:1998
Page 12
ETS 300 403-6: January 1997
6.1.2 Source of TP definition
The TPs are based on ETS 300 403-1 [1] and ETS 300 403-2 [2].
6.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
see table 1
Header tab
subclause 2.3.4
Stimulus Ensure that the IUT in the
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
SETUP, FACILITY, CONNECT,
Message
structure message etc. (see note 2)
a) with a Bearer capability, Facility, etc.
information element
b) indicating in the
and back to a) or b)

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.
6.1.4 Test strategy

As the base standard ETS 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.
6.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 ETS 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.
---------------------- Page: 14 ----------------------
SIST ETS 300 403-6:1998
Page 13
ETS 300 403-6: January 1997
6.1.6 Test of point-to-multipoint configurations

In subclauses 6.2.1, 6.2.5, 6.2.6, 6.2.7 and 6.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.

6.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 ETS 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 ETS 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.
6.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.
6.2.1 Null call state N00
6.2.1.1 Valid
6.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 th
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.