SIST EN 300 359-5 V1.3.6:2005

• Abstract:

  Produce a new edition of the network side TSS&TP that incorporates changes necessitated by the maintenance work of STF122 on the ATS part Supporting Members: MATAV, PTA, Viag Interkom, Nokia, Acacia, BT

• Status: Published
• Publication Date: 31-Mar-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-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Ref Project: ETSI EN 300 359-5 V1.3.6 (2000-06) - Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network

SIST EN 300 359-5 V1.3.6:2005 is the Slovenian adoption of the ETSI European Standard for the Integrated Services Digital Network (ISDN) Completion of Calls to Busy Subscriber (CCBS) supplementary service using the Digital Subscriber Signalling System No. one (DSS1) protocol. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side, so it tells test teams what to check at the T reference point, or at coincident S and T reference points, against EN 300 359-1.

This part is aimed at conformance testing of network implementations. In practice, it is the document that turns the CCBS protocol specification into a structured set of test purposes for network-side verification.

What does SIST EN 300 359-5 V1.3.6:2005 specify?

SIST EN 300 359-5 V1.3.6:2005 specifies the network-side TSS&TP for CCBS over DSS1 in pan-European ISDN. Clause 1 limits the scope to implementations conforming to the stage three standard in EN 300 359-1, and it points to the related user-side parts and the network-side ATS/PIXIT part in the same series.

The document is organized into:

• clause 1, scope
• clause 2, references
• clause 3, definitions and abbreviations
• clause 4, Test Suite Structure
• clause 5, Test Purposes
• clause 6, compliance
• clause 7, requirements for a comprehensive testing service
• Annex A, change record

Clause 4 shows the test groups by network side and by function. Clause 5 then gives the individual test purposes, grouped by CCBS procedure, state, and reference point.

What are the key requirements of SIST EN 300 359-5 V1.3.6:2005?

The main requirement is not a product design rule but a testing structure: SIST EN 300 359-5 V1.3.6:2005 defines the test purposes that an Abstract Test Suite (ATS) uses to assess network conformance. Clause 5 says each TP is defined for a specific requirement, and the TP naming convention links the supplementary service, the implementation type, the test group, and a sequential number. That matters because the identifier tells a test engineer exactly which CCBS behavior is under test.

How the test purposes are organized

Clause 4 groups the network tests into Network (S/T) and Network (T), and then into Network A, Network B, and GFP cases. The Network (S/T) part covers activation, deactivation, interrogation, invocation and operation, retention, and timers. The Network (T) part covers the originating side and destination side procedures in a private network context. In practice, this split tells a lab whether it is testing the public ISDN interface or the private-network bearer-related and bearer-independent procedures.

What the network-side CCBS tests check

The TPs cover the key CCBS call flows and error handling. They check FACILITY message exchanges for activation, deactivation, interrogation, remote user free, call establishment, status request, suspension, resumption, and erasure of retained call information. Many TPs also check the returned error or result components, such as invalid references, not subscribed, busy again, or denial conditions. For a tester, this means the document is not just about message presence - it specifies the expected network reaction, state change, or no-action behavior in each case.

How timers and states are tested

Clause 5 includes timer-based TPs for CCBS timers and retention timing. Examples include expiry handling for the CCBS timers and the retention timer, with expected erase actions or state transitions. The tests are written against call states such as N00, N03, N12, N31, and others listed in the abbreviations. In practice, this means the implementation must behave correctly not only on message receipt, but also when a timer expires while the service is active.

What the Network B procedures add

The Network B tests cover the non-served user side and the “status request procedures for existing services” option. Depending on whether that option is supported, the network either reserves a B-channel and sends a StatusRequest, or reserves a B-channel without sending a message, then reacts to compatibleAndFree, compatibleAndBusy, or incompatible results. This is important because it checks channel reservation logic and the effect of user B subscription options on the CCBS flow.

How malformed or unsuitable messages are handled

The GFP tests in clause 5 cover invalid protocol profiles, missing Facility information elements, wrong message types with dummy call references, and incorrect CCBSReference types. The expected behavior is usually to ignore the message or return a STATUS with an appropriate cause. That matters because a conforming network must reject or ignore out-of-context signaling cleanly instead of entering an unsafe call state.

What compliance means here

Clause 6 says a compliant ATS must correspond to the specified test purposes, use an appropriate subset of the test suite structure, keep the same naming conventions, preserve the link to the PICS proforma for deselection, and comply with ISO/IEC 9646-2. Clause 7 adds that any organization claiming a comprehensive testing service for network equipment claiming conformance to EN 300 359-1 shall use the Remote test method from ISO/IEC 9646-2. In practice, clause 6 governs how test cases are built, and clause 7 states the minimum test method expectation for full-service testing.

What terms does SIST EN 300 359-5 V1.3.6:2005 define?

• CCBS - Completion of Calls to Busy Subscriber, the supplementary service that this part tests.
• DSS1 - Digital Subscriber Signalling System No. one, the signaling protocol used for the ISDN user-network interface.
• ATS - Abstract Test Suite, the set of abstract test cases used for conformance testing.
• IUT - Implementation Under Test, the network implementation being checked.
• PICS - Protocol Implementation Conformance Statement, the declaration used to select applicable tests.
• PIXIT - Protocol Implementation eXtra Information for Testing, the extra implementation data needed to parameterize tests.
• TP - Test Purpose, a single conformance objective written from the protocol requirements.
• network (T) - the DSS1 protocol entity at the network side where a T reference point applies, used here for private-ISDN testing.

Who uses SIST EN 300 359-5 V1.3.6:2005?

This standard is used by conformance test labs, telecom equipment vendors, network operators, and quality engineers working on ISDN CCBS implementations. They use it to derive ATS cases, choose tests from the PICS, verify network-side signaling, and check timer and state behavior at the T or coincident S/T reference point. It is especially relevant where a private network must handle both bearer-related and bearer-independent transport procedures.

What changed in SIST EN 300 359-5 V1.3.6:2005 from the previous edition?

The change record states that this edition corrects the ATS. It also records conversion to the EN layout, replacement of references to ETS 300 102 with EN 300 403, and replacement of non-specific references so they point to the latest version of the basic standards. The scope also identifies this as a new edition of the network-side TSS&TP incorporating maintenance changes to the ATS part.

Which standards are used with SIST EN 300 359-5 V1.3.6:2005?

Standard	What it contributes
EN 300 359-1	The base CCBS protocol specification that the test purposes are derived from.
EN 300 359-2	The Protocol Implementation Conformance Statement (PICS) proforma used for test selection.
ISO/IEC 9646-1	General conformance testing concepts and core terms.
ISO/IEC 9646-2	Abstract test suite specification and ATS compliance rules.
ISO/IEC 9646-3	Tree and Tabular Combined Notation (TTCN) and related test notation.
EN 300 196-1	Generic functional protocol support, including invoke and return component handling.
EN 300 403-1	Basic call control and call reference definitions.
ITU-T Recommendation I.411	ISDN user-network reference configurations and T/S point context.
ITU-T Recommendation I.112	ISDN vocabulary and the definition of ISDN.
ITU-T Recommendation E.164	The international numbering plan used for ISDN numbers.
ITU-T Recommendation I.210	The definition of supplementary services and how they are described.

What does the SIST EN 300 359-5 V1.3.6:2005 document contain?

The document contains the TSS figure, the TP naming convention, and the TP structure used to write individual conformance tests. It also contains network-side TP sets for activation, deactivation, interrogation, call setup, status requests, retention, timers, and invalid-message handling. Table 1 explains the identifier scheme, Table 2 explains the contents of one TP, and the figure in clause 4 shows how the groups are arranged. Annex A contains the change record for this edition.

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±'RSROQLOQDVWRULWHY
GRNRQþDQMHNOLFDQMD]DVHGHQHJDQDURþQLND&&%6±3URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66±GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQL
SUHVNXãDQMD766 73±6SHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber
(CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the
network
Ta slovenski standard je istoveten z: EN 300 359-5 Version 1.3.6
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)
Integrated Services Digital Network (ISDN);
Completion of Calls to Busy Subscriber (CCBS)
supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network
2 ETSI EN 300 359-5 V1.3.6 (2000-06)
Reference
REN/SPS-05169-5
Keywords
ISDN, DSS1, supplementary service, CCBS,
TSS&TP, network
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - 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
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document 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.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
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 359-5 V1.3.6 (2000-06)
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 300 359-1.6
3.2 Abbreviations .7
4 Test Suite Structure (TSS) .8
5 Test Purposes (TP).8
5.1 Introduction .8
5.1.1 TP naming convention .8
5.1.2 Source of TP definition.8
5.1.3 TP structure.9
5.1.4 Test strategy.9
5.2 Network TPs for CCBS.9
5.2.1 Network (S/T).9
5.2.1.1 Network A.10
5.2.1.1.1 Activation .10
5.2.1.1.2 Deactivation.11
5.2.1.1.3 Interrogation .12
5.2.1.1.4 Invocation and operation .12
5.2.1.1.5 Retention .16
5.2.1.1.6 Timers.17
5.2.1.2 Network B .18
5.2.1.2.1 ExistingServiceNoStatusReq .18
5.2.1.2.2 ExistingServiceWithStatusReq.18
5.2.1.2.3 NotExistingService.19
5.2.1.3 GFP .20
5.2.2 Network (T) .20
5.2.2.1 Originating side.20
5.2.2.1.1 General .20
5.2.2.1.2 Timers.23
5.2.2.1.3 GFP.23
5.2.2.2 Destination side.24
5.2.2.2.1 General .24
5.2.2.2.2 Timers.25
5.2.2.2.3 GFP.25
6 Compliance .26
7 Requirements for a comprehensive testing service.26
Annex A (informative): Change record.27
A.1 Changes with respect to EN 300 359-5 V1.2.27
A.2 Changes with respect to the previous ETS 300 359-5 .27
History.28
ETSI
4 ETSI EN 300 359-5 V1.3.6 (2000-06)
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 ETSI 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 ETSI 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 5 of a multi-part EN covering the Integrated Services Digital Network (ISDN);
Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol, as described below:
Part 1: "Protocol specification";
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: 19 May 2000
Date of latest announcement of this EN (doa): 31 August 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2001
Date of withdrawal of any conflicting National Standard (dow): 28 February 2001
ETSI
5 ETSI EN 300 359-5 V1.3.6 (2000-06)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Network side of the
T reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) of
implementations conforming to the stage three standard for the Completion of Calls to Busy Subscriber (CCBS)
supplementary service for the pan-European Integrated Services Digital Network (ISDN) by means of the Digital
Subscriber Signalling System No. one (DSS1) protocol, EN 300 359-1 [1].
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 359-1 [1].
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] ETSI EN 300 359-1 (V1.2): "Integrated Services Digital Network (ISDN); Completion of Calls to
Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 1: Protocol specification".
[2] ETSI EN 300 359-2 (V1.2): "Integrated Services Digital Network (ISDN); Completion of Calls to
Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma
specification".
[3] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract test suite specification".
[5] ISO/IEC 9646-3 (1998): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[6] ETSI EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for
the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 1: Protocol specification".
[7] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[8] ETSI EN 300 403-1: "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]".
[9] ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".
[10] ITU-T Recommendation E.164 (1997): "The international public telecommunication numbering
plan".
ETSI
6 ETSI EN 300 359-5 V1.3.6 (2000-06)
[11] ITU-T Recommendation I.210 (1993): "Principles of telecommunication services supported by an
ISDN and the means to describe them".
[12] ETSI EN 300 359-5 (V1.2): "Integrated Services Digital Network (ISDN); Completion of Calls to
Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the
network".
[13] ETSI ETS 300 359-5: "Integrated Services Digital Network (ISDN); Completion of Calls to Busy
Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply.
3.1.1 Definitions related to conformance testing
abstract test case: refer to ISO/IEC 9646-1 [3]
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [3]
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [3]
implicit send event: refer to ISO/IEC 9646-3 [5]
lower tester: refer to ISO/IEC 9646-1 [3]
point of control and observation: refer to ISO/IEC 9646-1 [3]
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [3]
PICS proforma: refer to ISO/IEC 9646-1 [3]
Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [3]
PIXIT proforma: refer to ISO/IEC 9646-1 [3]
system under test: refer to ISO/IEC 9646-1 [3]
Test Purpose (TP): refer to ISO/IEC 9646-1 [3]
3.1.2 Definitions related to EN 300 359-1
Call Reference (CR): see EN 300 403-1 [8], subclause 4.3
component: see EN 300 196-1 [6], subclause 11.2.2.1
Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [9], definition 308
ISDN number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [10]
invoke component: see EN 300 196-1 [6], subclause 11.2.2.1
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
ETSI
7 ETSI EN 300 359-5 V1.3.6 (2000-06)
network (T): DSS1 protocol entity at the Network side of the user-network interface where a T reference point applies
(Network connected to Private ISDN)
return error component: see EN 300 196-1 [6], subclause 11.2.2.1
return result component: see EN 300 196-1 [6], subclause 11.2.2.1
served user: served user is the user who invokes the CCBS supplementary service
service; telecommunication service: see ITU-T Recommendation I.112 [9], definition 201
supplementary service: see ITU-T Recommendation I.210 [11], subclause 2.4
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CCBS Completion of Calls to Busy Subscriber
CR Call Reference
CR1 normal (bearer related) CR
CR2 CR used for bearer independent transport mechanism
DSS1 Digital Subscriber Signalling System No. one
GFP Generic Functional Protocol
ISDN Integrated Services Digital Network
IUT Implementation Under Test
N00 Null call state
N01 Call Initiated 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
N12 Disconnect Indication call state
N31 Bearer Independent Transport call state
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
UI Unnumbered Information
ETSI
8 ETSI EN 300 359-5 V1.3.6 (2000-06)
4 Test Suite Structure (TSS)
CCBS - Network
Network (S/T) Network (T)
Network A Network B GFP Originating Destination
(10) side side
General Timers GFP General Timers GFP
(11) (12) (13) (14) (15) (16)
ExistingServiceNoStatusReq ExistingServiceWithStatusReq NotExistingService
(07) (08) (09)
Activation Deactivation Interrogation Invocation and Retention Timers
(01) (02) (03) operation (05) (06)
(04)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
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 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual supplementary service and whether it applies to the network or the user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "CCBS"
= type of IUT: U User
NNetwork
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
5.1.2 Source of TP definition
The TPs are based on EN 300 359-1 [1].
ETSI
9 ETSI EN 300 359-5 V1.3.6 (2000-06)
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 and this is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. use a TP as an example to fully understand the table.
Table 2: Structure of a single TP
TP part Text Example
Header tab seetable1
tab subclause 0.0.0
tab valid, invalid, inopportune
CR. mandatory, optional, conditional
Stimulus Ensure that the IUT in the
N10, N12, etc.
and CCBS Idle state
see below for message structure receiving a XXXX message
or to request a .
Reaction sends, saves, does, etc.
using en-bloc sending, .
if the action is sending
see below for message structure
, etc.
and enters
and/or and remains in the same state(s)
or and enters state
Message SETUP, FACILITY, CONNECT, .
structure message containing a
a)
Bearer capability, Facility, .
information element with
b) a
encoded as or including
and back to a or b,
NOTE: 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.
5.1.4 Test strategy
As the base standard EN 300 359-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 EN 300 359-2 [2]. 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.2 Network TPs for CCBS
5.2.1 Network (S/T)
NOTE 1: All FACILITY messages in TPs associated with clause 9, use the dummy call reference as specified in
subclauses 8.3.2.2 and 8.3.2.4 of EN 300 196-1 [6] (bearer independent connectionless transport
mechanism). Unless stated otherwise, FACILITY messages are sent/received using point-to-point data
link (I frame) and the IUT is configured so that it "knows" that a point-to-point configuration exists at the
user's access.
NOTE 2: Although the sending or receiving of a message using the dummy call reference is independent of any
particular call state, in the following TPs call state N12 is used to show that the IUT has just begun
clearing of a call and call state N00 is used to indicate that Layer 2 is active and capable of carrying
bearer independent messages.
ETSI
10 ETSI EN 300 359-5 V1.3.6 (2000-06)
5.2.1.1 Network A
5.2.1.1.1 Activation
CCBS_N01_001 subclause 9.1.1 valid mandatory
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state for
CCBS, on receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke
component including the CallLinkageID, sends a FACILITY message containing a Facility information element with a
CCBSRequest return result component including the CCBSReference and recallMode and remains in call state N12.
CCBS_N01_002 subclause 9.1.2 inopportune optional
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID from a user who has not subscribed to CCBS, sends a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "notSubscribed" and remains in
call state N12.
Selection:IUT provides Call Information Retention procedures even though CCBS not subscribed.
CCBS_N01_003 subclause 9.1.2 inopportune mandatory
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state for
CCBS, on receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke
component including an invalid CallLinkageID, sends a FACILITY message containing a Facility information element
with a CCBSRequest return error component indicating "invalidCallLinkageID" and remains in call state N12.
CCBS_N01_004 subclause 9.1.2 inopportune optional
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID even though the attempted call failed for a reason other than the called user was busy,
sends a FACILITY message containing a Facility information element with a CCBSRequest return error component
indicating "callFailureReasonNotBusy" and remains in call state N12.
Selection:IUT provides Call Information Retention procedures for service other than CCBS.
CCBS_N01_005 subclause 9.1.2 inopportune optional
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID but user A's CCBS queue is full, sends a FACILITY message containing a Facility
information element with a CCBSRequest return error component indicating "outgoingCCBSQueueFull" and remains in
call state N12.
Selection:IUT provides Call Information Retention procedures for service other than CCBS OR IUT provides Call
Information Retention procedures for CCBS even when user A's CCBS queue is full.
CCBS_N01_006 subclause 9.1.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSRequest invoke component including the CallLinkageID (but the served user
has already activated the CCBS supplementary service for the call identified by the CallLinkageID), sends a FACILITY
message containing a Facility information element with a CCBSRequest return error component indicating
"cCBSIsAlreadyActivated" and remains in call state N00.
ETSI
11 ETSI EN 300 359-5 V1.3.6 (2000-06)
CCBS_N01_007 subclause 9.1.2 inopportune optional
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID but the served user has already activated CCBS supplementary service for an identical call
(in Null call state N00 and CCBS Activated state), sends a FACILITY message containing a Facility information
element with a CCBSRequest return error component indicating "cCBSIsAlreadyActivated" and remains in call state
N12.
Selection:IUT supports option to "Check for identical calls". PICS: MC 8.
CCBS_N01_008 subclause 9.1.2 inopportune mandatory
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state for
CCBS, on receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke
component including the CallLinkageID, but interactions between CCBS supplementary service and the call identified
by the CallLinkageID are invalid, sends a FACILITY message containing a Facility information element with a
CCBSRequest return error component indicating "supplementaryServiceInteractionNotAllowed" and remains in
call state N12.
CCBS_N01_009 subclause 9.1.2 inopportune optional
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID, but CCBS is not available to the destination, sends a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "longTermDenial" and remains in
call state N12.
Selection: The IUT supports Call Information Retention procedure when "CCBS is not available to the destination".
CCBS_N01_010 subclause 9.1.2 inopportune mandatory
Ensure that the IUT in the Disconnect Indication call state N12 and CCBS Idle state and Retention Active state, on
receipt of a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the CallLinkageID, but CCBS is not available to the destination at this time, sends a FACILITY message
containing a Facility information element with a CCBSRequest return error component indicating "shortTermDenial"
and remains in call state N12.
5.2.1.1.2 Deactivation
CCBS_N02_001 subclauses 9.2.1, 9.4.4.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSDeactivate invoke component including the correct CCBSReference
parameter, sends a FACILITY message containing a Facility information element with a CCBSDeactivate return result
component with cCBSEraseReason indicating "normal-unspecified" and a FACILITY message containing a Facility
information element with a CCBSErase invoke component and enters the CCBS Idle state.
CCBS_N02_002 subclause 9.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSDeactivate invoke component including an invalid CCBSReference, sends a
FACILITY message containing a Facility information element with a CCBSDeactivate return error component
indicating "invalidCCBSReference" and remains in the same state.
CCBS_N02_003 subclause 9.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Idle state, on receipt of a FACILITY message containing a
Facility information element with a CCBSDeactivate invoke component when the user has not subscribed to the
supplementary service, sends a FACILITY message containing a Facility information element with a CCBSDeactivate
return error component indicating "invalidCCBSReference".
ETSI
12 ETSI EN 300 359-5 V1.3.6 (2000-06)
5.2.1.1.3 Interrogation
CCBS_N03_001 subclause 9.3.1.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSInterrogate invoke component without a CCBSReference parameter, sends a
FACILITY message containing a Facility information element with a CCBSInterrogate return result component
including the correct value for the recallMode parameter, and in the CallDetails parameter a list of all currently active
CCBS requests giving for each the CCBSReference, addressOfB, q931InfoElement and if available, the
subAddressOfA.
CCBS_N03_002 subclause 9.3.1.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Idle state, on receipt of a FACILITY message containing a
Facility information element with a CCBSInterrogate invoke component without a CCBSReference parameter and no
CCBS requests exist, sends a FACILITY message containing a Facility information element with a CCBSInterrogate
return result component including the correct value for the recallMode parameter, and no CallDetails parameter.
CCBS_N03_003 subclause 9.3.1.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Idle state, on receipt of a FACILITY message containing a
Facility information element with a CCBSInterrogate invoke component without a CCBSReference parameter but the
user has not subscribed to CCBS, sends a FACILITY message containing a Facility information element with a
CCBSRequest return error component indicating "notSubscribed".
CCBS_N03_004 subclause 9.3.2.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSInterrogate invoke component including a valid cCBSReference parameter,
sends a FACILITY message containing a Facility information element with a CCBSInterrogate return result component
including the recallMode and in the callDetails parameter, addressOfB, q931InfoElement, cCBSReference and if
available, the subAddressOfA.
CCBS_N03_005 subclause 9.3.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Idle state, on receipt of a FACILITY message containing a
Facility information element with a CCBSInterrogate invoke component including a CCBSReference parameter but the
user has not subscribed to CCBS, sends a FACILITY message containing a Facility information element with a
CCBSRequest return error component indicating "notSubscribed".
CCBS_N03_006 subclause 9.3.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a FACILITY message containing
a Facility information element with a CCBSInterrogate invoke component including an invalid CCBSReference
parameter, sends a FACILITY message containing a Facility information element with a CCBSRequest return error
component indicating "invalidCCBSReference".
5.2.1.1.4 Invocation and operation
CCBS_N04_001 subclause 9.4.1.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, having checked that the user is neither busy
nor CCBS busy, in order to indicate that it is prepared for establishment of the requested call, sends a FACILITY
message containing a Facility information element with a CCBSRemoteUserFree invoke component including the
recallMode, cCBSReference, addressOfB and q931InfoElement.
CCBS_N04_002 subclause 9.4.1.1 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, and a multipoint configuration exists, having
checked that the user is neither busy nor CCBS busy, in order to indicate that it is prepared for establishment of the
requested call, sends a FACILITY message (UI frame) containing a Facility information element with a
CCBSRemoteUserFree invoke component including the recallMode, cCBSReference, addressOfB and
q931InfoElement.
ETSI
13 ETSI EN 300 359-5 V1.3.6 (2000-06)
CCBS_N04_003 subclause 9.4.1.2 valid mandatory
Ensure that the IUT in the Null call state N00 and CCBS Free state, (after sending a FACILITY message containing a
Facility information element with a CCBSRemoteUserFree invoke component) on receipt of a FACILITY message with
a CCBSRemoteUserFree reject component, takes no action and remains in the same states.
CCBS_N04_004 subclause 9.4.2.1 valid optional
Ensure that the IUT in the Null call state N00 and CCBS Free state, if the specific recall option applies, on receipt of a
SETUP message containing Bearer capability information element(s) from the original call and a Facility information
element with a CCBSCall invoke component including the CCBSReference from the previously sent
CCBSRemoteUserFree invoke component, continues en-bloc basic call procedures using the retained call information
and moves to call state N01.
Selection:Specific recall option supported. PICS: MC 7.2.
CCBS_N04_005 subclause 9.4.2.1 valid optional
Ensure that the IUT in the Null call state N00 and CCBS Free state, if the global recall option applies and a multipoint
configuration exists, on receipt of a SETUP message containing Bearer capability information element(s) from the
original call and a Facility information element with a CCBSCall invoke component including the CCBSReference from
the previously sent CCBSRemoteUserFree invoke component, continues basic call procedures and sends a FACILITY
message (UI frame) containing a Facility information element with a CCBSStopAlerting invoke component including
the CCBSReference and moves to call state N01.
Selection:Global recall option supported. PICS: MC 7.1.
CCBS_N04_006 subclause 9.4.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Free state, on receipt of a SETUP message containing Bearer
capability information element(s) from the original call and containing a Facility information element with a CCBSCall
invoke component including an invalid CCBSReference value, sends a RELEASE COMPLETE message containing a
Facility information element with a CCBSCall return error component indicating "invalidCCBSReference" and moves to
call state N00.
CCBS_N04_007 subclause 9.4.2.2 inopportune mandatory
Ensure that the IUT in the Null call state N00 and CCBS Activated state, on receipt of a SETUP message containing
Bearer capability information element(s) from the original call and containing a Facility information element with a
CCBSCall invoke component before having sent a cCBSRemoteUserFree invoke component for this user's
CCBSReference, sends a RELEASE COMPLETE message containing a Facility information element with a CCBSCall
return error component indicating "notReadyForCall" and moves to call state N00.
CCBS_N04_008 subclause 9.4.2.2 inopportune optional
Ensure that the IUT in the Null call state N00 and CCBS Free state, on receipt of a SETUP message containing Bearer
capability information element(s) from the original call and containing a Facility information element with a CCBSCall
invoke component when no B-channels can be selected, sends a RELEASE COMPLETE cause #34 or #44 and moves to
call state N00.
Selection:IUT supports specific recall option. PICS: MC 7.2.
CCBS_N04_009 subclause 9.4.2.2 inopportune optional
Ensure that the IUT in the Null call state N00 and CCBS Free state, where a multipoint configuration exists and the
global recall option applies, on receipt of a SETUP message containing Bearer capability information element(s) from
the original call and containing a Facility information element with a CCBSCall invoke component when no B-channels
can be selected, sends a FACILITY message (UI frame) containing a Facility information element with a
CCBSStopAlerting invoke component including the same CCBSReference value and a RELEASE COMPLETE cause
#34 or #44 and moves to call state N00.
Selection:Global recall option supported. PICS: MC 7.1.
ETSI
14 ETSI EN 300 359-5 V1.3.6 (2000-06)
CCBS_N04_010 subclause 9.4.2.2 inopportune optional
Ensure that the IUT in the Null call state N00 and CCBS Free state, where a multipoint configuration exists and the
global recall option applies, on receipt of more than one SETUP message containing Bearer capability information
element(s) from the original call and containing a Facility information element with a CCBSCall invoke component,
continues basic call procedures for the first SETUP message and sends a RELEASE COMPLETE message containing a
Facility information element with a CCBSCall return error component indicating "alreadyAccepted" in response to the
other SETUP messages and moves to call state N01.
Selection:Global recall option supported. PICS: MC 7.1.
CCBS_N04_011 subclauses 9.4.3.1, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing call proceeding call state N03 and CCBS Call Init state, to indicate that user B has
responded to the call with an ALERTING message, sends an ALERTING message followed by a FACILITY message
containing a Facility information element with a cCBSErase invoke indicating cCBSEraseReason "normal-unspecified"
and enters the call state N04.
CCBS_N04_012 subclauses 9.4.3.1, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing call proceeding call state N03 and CCBS Call Init state, to indicate that user B has
responded to the call with a CONNECT message, sends a CONNECT message followed by a FACILITY message
containing a Facility information element with a cCBSErase invoke indicating cCBSEraseReason "normal-unspecified"
and enters the call state N10.
CCBS_N04_013 subclauses 9.4.3.2, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing Call Proceeding call state N03 and CCBS Call Init state, if it is not able to establish
the call because the called user is busy again, sends a DISCONNECT message not containing a Facility information
element with a cCBSErase invoke component and enters the call state N12 or N00.
Selection:"CCBS request retention" option supported. PICS: MC 6.
CCBS_N04_014 subclauses 9.4.3.2, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing Call Proceeding call state N03 and CCBS Call Init state, if it is not able to establish
the call because the called user is busy again, sends a DISCONNECT message containing a Facility information element
with a CallInfoRetain invoke component including a CallLinkageID; and sends a FACILITY message containing a
Facility information element with a CCBSErase invoke component including CCBSEraseReason encoded as
"basic-call-failed"; and enters call state N12.
Selection:"CCBS request retention" option NOT supported. PICS: NOT MC 6.
CCBS_N04_015 subclauses 9.4.3.2, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing Call Proceeding call state N03 and CCBS Call Init state, where a multipoint
configuration exists, if it is not able to establish the call because the called user is busy again, sends a DISCONNECT
message containing a Facility information element with a CallInfoRetain invoke component including a CallLinkageID,
and sends a FACILITY message (UI frame) containing a Facility information element with a CCBSErase invoke
component including CCBSEraseReason encoded as "basic-call-failed"; and enters call state N12.
Selection:"CCBS request retention" option NOT supported. PICS: NOT MC 6.
CCBS_N04_016 subclauses 9.4.3.2, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing Call Proceeding call state N03 and CCBS Call Init state, if it is not able to establish
the call for any reason other than the called user is busy, sends a DISCONNECT message; and sends a FACILITY
message containing a Facility information element with a CCBSErase invoke component including CCBSEraseReason
encoded as "basic-call-failed"; and enters call state N12.
Selection:"CCBS request retention" option supported. PICS: MC 6.
ETSI
15 ETSI EN 300 359-5 V1.3.6 (2000-06)
CCBS_N04_017 subclauses 9.4.3.2, 9.4.4.1 valid optional
Ensure that the IUT in the Outgoing Call Proceeding call state N03 and CCBS Call Init state, where a multipoint
configuration exists, if it is not able to establish the call for any reason other than the called user is busy, sends a
DISCONNECT message; and sends a FACILITY message (UI frame) containing a Facility information element with a
CCBSErase invoke component including CCBSEraseReason encoded as "basic-call-failed"; and enters call state N12.
Selection:"CCBS request retention" option supported. PICS: MC 6.
NOTE 1: The above two TPs are now repeated but with the "CCBS request retention" option NOT supported. This
is to demonstrate that the deactivation of the CCBS supplementary service under these circumstances is
independent of this option.
CCBS_N04_018 subclauses 9.4.3.2, 9.4.4.1 valid optiona
...