ETSI EN 300 359-3 V1.4.1 (2001-06)

Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

REN/SPAN-130201-3

Digitalno omrežje z integriranimi storitvami (ISDN) – Dopolnilna storitev: dokončanje klica do zasedenega naročnika (CCBS) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – Specifikacija za uporabnika

General Information

• Status: Published
• Publication Date: 11-Jun-2001
• Technical Committee: SPAN 13 - SPAN Peer-to-Peer Control Protocol (PTPCP)
• Current Stage: 12 - Completion
• Due Date: 15-Jun-2001
• Completion Date: 12-Jun-2001
• Ref Project: SIST EN 300 359-3 V1.4.1:2005 - Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 300 359-3 V1.4.1:2005
01-januar-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±'RSROQLOQDVWRULWHY
GRNRQþDQMHNOLFDGR]DVHGHQHJDQDURþQLND&&%6±3URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66±GHO=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQ
SUHVNXãDQMD766 73±6SHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber
(CCBS) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the
user
Ta slovenski standard je istoveten z: EN 300 359-3 Version 1.4.1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST EN 300 359-3 V1.4.1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 300 359-3 V1.4.1:2005

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

SIST EN 300 359-3 V1.4.1:2005
ETSI EN 300 359-3 V1.4.1 (2001-06)
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 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user

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

SIST EN 300 359-3 V1.4.1:2005
2 ETSI EN 300 359-3 V1.4.1 (2001-06)
Reference
REN/SPAN-130201-3
Keywords
ISDN, DSS1, supplementary service, CCBS,
testing, TSS&TP, user
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 2001.
All rights reserved.
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
3 ETSI EN 300 359-3 V1.4.1 (2001-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) .7
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 . 8
5.1.4 Test strategy . 9
5.2 User TPs for CCBS . 9
5.2.1 User (S/T). 9
5.2.1.1 User 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 . 13
5.2.1.1.5 Retention . 16
5.2.1.2 User B. 16
5.2.1.3 GFP. 16
5.2.2 User (T). 17
5.2.2.1 Originating side. 17
5.2.2.1.1 General . 17
5.2.2.1.2 GFP . 20
5.2.2.2 Destination side. 20
5.2.2.2.1 General . 20
5.2.2.2.2 GFP . 23
6 Compliance .25
7 Requirements for a comprehensive testing service.25
Annex A (informative): Changes with respect to the previous EN 300 359-3 V1.2.4.26
History .27
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
4 ETSI EN 300 359-3 V1.4.1 (2001-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 3 of a multi-part deliverable covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Completion of Calls to Busy
Subscriber (CCBS) supplementary service, 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".
The present version updates the references to the protocol specification.
National transposition dates
Date of adoption of this EN: 8 June 2001
Date of latest announcement of this EN (doa): 30 September 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 2002
Date of withdrawal of any conflicting National Standard (dow): 31 March 2002
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
5 ETSI EN 300 359-3 V1.4.1 (2001-06)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of the
T reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [6]) of
implementations conforming to the stage three standard of 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 Network 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, subsequent revisions do apply.
[1] ETSI EN 300 359-1 (V1.3.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.4): "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: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-2: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 2: Abstract test suite specification".
[5] 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".
[6] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[7] 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]".
[8] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[9] ITU-T Recommendation I.210: "Principles of the telecommunication services supported by an
ISDN and the means to describe them".
[10] ETSI ETS 300 196-3: "Integrated Services Digital Network (ISDN); Generic functional protocol
for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user".
[11] ETSI EN 300 406:"Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
6 ETSI EN 300 359-3 V1.4.1 (2001-06)
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]
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 Held auxiliary state: see EN 300 196-1 [5], clause 7.1.2
call reference: see EN 300 403-1 [7], clause 4.3
component: see EN 300 196-1 [5], clause 11.2.2.1
Idle auxiliary state: see EN 300 196-1 [5], clause 7.1.2
Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [8], definition 308
invoke component: see EN 300 196-1 [5], clause 11.2.2.1
return error component: see EN 300 196-1 [5], clause 11.2.2.1
return result component: see EN 300 196-1 [5], clause 11.2.2.1
served user: the served user is the user who invokes the CCBS supplementary service
service; telecommunication service: see ITU-T Recommendation I.112 [8], definition 201
supplementary service: see ITU-T Recommendation I.210 [9], clause 2.4
user: theDSS1protocol entityattheUser sideoftheuser-network interfacewhereaTreferencepointor coincidentS
and T reference point applies
user (S/T): the DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference
point applies
user (T):theDSS1protocol entityattheUser sideoftheuser-networkinterfacewhereaTreferencepointapplies
(User is the Private ISDN)
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
7 ETSI EN 300 359-3 V1.4.1 (2001-06)
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
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
U00 Nullcallstate
U01 Call Initiated call state
U03 Outgoing Call Proceeding call state
U04 Call Delivered call state
U06 Call Present call state
U07 Call Received call state
U08 Connect Request call state
U09 Incoming Call Proceeding call state
U10 Active call state
U12 Disconnect Indication call state
U25 Overlap Receiving call state
U31 Bearer Independent Transport call state
UI Unnumbered Information
4 Test Suite Structure (TSS)
CCBS - User
User (S/T) User (T)
User A User B GFP Originating Destination
(06) (07) side side
General GFP General GFP
(08) (09) (10) (11)
Activation Deactivation Interrogation Invocation and Retention
(01) (02) (03) operation (05)
(04)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
8 ETSI EN 300 359-3 V1.4.1 (2001-06)
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).
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
TheTPsarebased onEN 300 359-1[1].
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.
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
9 ETSI EN 300 359-3 V1.4.1 (2001-06)
Table 2: Structure of a single TP
TP part Text Example
Header tab seetable1
tab clause 0.0.0
Stimulus Ensure that the IUT in the
U10, U12, 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 call state(s)
or and enters call 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 TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and are
limited to conceivable situations to which a real implementation is likely to be faced (EN 300 406 [11]).
All test purposes are mandatory unless they have selection criteria. Optional test purposes (with selection criteria) are
applicable according to the configuration options of the IUT. The configuration option shall be covered by a PICS item.
5.2 UserTPsforCCBS
Unless specified:
- the messages indicated are valid and contain at least the mandatory information elements and possibly optional
information elements;
- the information elements indicated are valid and contain at least the mandatory parameters and possibly optional
parameters;
- all PICS items referred to in this clause are as specified in EN 300 359-2 [2] unless indicated otherwise by
another numbered reference.
5.2.1 User (S/T)
Selection:IUT supports coincident S and T reference point procedures. PICS: R 3.2.
NOTE: Unless stated otherwise, all FACILITY messages in TPs in this clause use the dummy call reference as
specified in clause 8.3.2.2 of EN 300 196-1 [5] (bearer independent connectionless transport mechanism).
Where an Unnumbered Information (UI) frame is specified for a FACILITY message, the message is sent
or received using broadcast procedures; otherwise point-to-point procedures are used.
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
10 ETSI EN 300 359-3 V1.4.1 (2001-06)
5.2.1.1 User A
5.2.1.1.1 Activation
CCBS_U01_001 clause 9.1.1
Ensure that the IUT in call state U12 and CCBS Idle state, having been informed that the network is performing the Call
Information Retention procedure, to activate the CCBS supplementary service,
sends a FACILITY message containing a Facility information element with a CCBSRequest invoke component
including the callLinkageID parameter and enters the CCBS Requested state before expiry of timer
T-RETENTION.
CCBS_U01_002 clause 9.1.1
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return result component including a recallMode parameter indicating
"specificRecall",
sends no message but retains the CCBSReference and enters CCBS Activated state.
CCBS_U01_003 clause 9.1.1
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return result component including a recallMode parameter indicating
"globalRecall",
sends no message, retains the cCBSReference parameter and enters CCBS Activated state; or
sends no message, releases the cCBSReference parameter and remains in the CCBS Requested state.
CCBS_U01_004 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "invalidCallLinkageID",
sends no message, releases the callLinkageID parameter and enters CCBS Idle state.
CCBS_U01_005 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "notSubscribed",
sends no message and enters the CCBS Idle state.
CCBS_U01_006 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "callFailureReasonNotBusy",
sends no message and enters the CCBS Idle state.
CCBS_U01_007 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "outgoingCCBSQueueFull",
sends no message and enters the CCBS Idle state.
CCBS_U01_008 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "cCBSIsAlreadyActivated",
sends no message and enters the CCBS Idle state.
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
11 ETSI EN 300 359-3 V1.4.1 (2001-06)
CCBS_U01_009 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating
"supplementaryServiceInteractionNotAllowed",
sends no message and enters the CCBS Idle state.
CCBS_U01_010 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "longTermDenial",
sends no message and enters the CCBS Idle state.
CCBS_U01_011 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest return error component indicating "shortTermDenial",
sends no message and enters the CCBS Idle state.
CCBS_U01_012 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on receipt of a FACILITY message containing a
Facility information element with a CCBSRequest reject component,
sends no message and enters the CCBS Idle state.
CCBS_U01_013 clause 9.1.2
Ensure that the IUT in call state U00 and CCBS Requested state, on expiry of timer T-ACTIVATE,
enters the CCBS Idle state.
5.2.1.1.2 Deactivation
CCBS_U02_001 clause 9.2.1
Ensure that the IUT in call state U00 and CCBS Activated state, to deactivate a CCBS request,
sends a FACILITY message containing a Facility information element with a CCBSDeactivate invoke
component including the cCBSReference parameter and enters the CCBS Deactivation Requested state.
CCBS_U02_002 clause 9.2.1
Ensure that the IUT in call state U00 and CCBS Activated state, to deactivate a number of CCBS requests,
sends one or more FACILITY messages containing one or more Facility information elements with one or more
CCBSDeactivate invoke components including the relevant cCBSReference parameters and enters the CCBS
Deactivation Requested state.
CCBS_U02_003 clause 9.2.1
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSDeactivate return result component,
sends no message, releases the cCBSReference parameter and enters the CCBS Idle state.
CCBS_U02_004 clause 9.2.2
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSDeactivate return error component indicating
"invalidCCBSReference",
sends no message, releases its knowledge of the CCBS request identified by the cCBSReference parameter and
enters CCBS Idle state.
ETSI

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

SIST EN 300 359-3 V1.4.1:2005
12 ETSI EN 300 359-3 V1.4.1 (2001-06)
CCBS_U02_005 clause 9.2.2
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSDeactivate reject component,
sends no message, retains knowledge of the CCBS request identified by the cCBSReference parameter and
enters the CCBS Idle state.
CCBS_U02_006 clause 9.2.2
Ensure that the IUT in call state U00 and CCBS Deactivation Requested state, on expiry of timer T-DEACTIVATE,
sends no message, releases its knowledge of the CCBS request identified by the cCBSReference parameter and
enters CCBS Idle state.
5.2.1.1.3 Interrogation
CCBS_U03_001 clause 9.3.1.1
Ensure that the IUT in call state U00 and CCBS Activated state, to perform an interrogation of all CCBS requests,
sends a FACILITY message containing a Facility information element with a CCBSInterrogate invoke
component without a cCBSReference parameter and including a partyNumberOfA parameter and enters the
CCBS Interrogation Requested state; or
sends a FACILITY message containing a Facility information element with a CCBSInterrogate invoke
component without a cCBSReference parameter and without a partyNumberOfA parameter and enters the CCBS
Interrogation Requested state.
CCBS_U03_002 clause 9.3.1.1
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSInterrogate return result component including the recallMode
parameter and a list in chronological order of the CCBS requests if any,
sends no message, discards details of those requests that are not compatible with its service compatibility
information and exits the CCBS Interrogation Requested state.
CCBS_U03_003 clause 9.3.1.2
Ensure that the IUT in call state U00 and CCBS Interrogation Requested state, on receipt of a FACILITY message
containing a Facility information element with a CCBSInterrogate return error component indicating "notSubscribed",
sends no message and rem
...