SIST ETS 300 497-6 E1:2003

SLOVENSKI STANDARD
01-december-2003
5DGLMVNDRSUHPDLQVLVWHPL5(6±'LJLWDOQHL]EROMãDQHEUH]YUYLþQH
WHOHNRPXQLNDFLMH'(&7±6NXSQLYPHVQLN&,±.QMLåQLFDSUHVNXãDOQLKSULPHURY
7&/±GHO=JUDGEDSUHVNXãDOQHJDQL]D766LQQDPHQLSUHVNXãDQMD73±
2PUHåQDSODVW1:.±3UHQRVQDUDGLMVND]DNOMXþLWHY37
Radio Equipment and Systems (RES); Digital Enhanced Cordless Telecommunications
(DECT); Common Interface (CI) Test Case Library (TCL);Part 6: Test Suite Structure
(TSS) and Test Purposes (TP) - Network (NWK) layer - Portable radio Termination (PT)
Ta slovenski standard je istoveten z: ETS 300 497-6 Edition 1
ICS:
33.060.20 Sprejemna in oddajna Receiving and transmitting
oprema equipment
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 497-6
TELECOMMUNICATION August 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-03026-6
ICS: 33.020, 33.060.50
Key words: DECT, TCL, TSS, TP
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL);
Part 6: Test Suite Structure (TSS) and Test Purposes (TP) -
Network (NWK) layer - Portable radio Termination (PT)
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 92 94 42 00 - Fax: +33 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 1996. All rights reserved.

Page 2
ETS 300 497-6: August 1996
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 3
ETS 300 497-6: August 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .10
3.1 DECT definitions.10
3.2 DECT abbreviations.10
3.3 ISO 9646 definitions.11
3.4 ISO 9646 abbreviations .11
4 Test Suite Structure (TSS) .12
4.1 TSS overview.12
4.2 Test groups.13
4.2.1 Protocol groups .13
4.2.1.1 Call Control (CC) .13
4.2.1.2 Mobility Management (MM) .13
4.2.1.3 Lower Layer Management Entity (LLME) .13
4.2.1.4 Link Control (LC) .13
4.2.1.5 Call Independent Supplementary Services (CISS).13
4.2.1.6 Connection Oriented Message Services (COMS).13
4.2.1.7 ConnectionLess Message Services (CLMS).13
4.2.2 Main test groups.13
4.2.2.1 Basic InTerconnection tests (IT).13
4.2.2.2 CApability tests (CA).13
4.2.2.3 Valid Behaviour tests (BV).13
4.2.2.4 Invalid Behaviour tests (BI).14
4.2.2.5 InOpportune Behaviour tests (BO) .14
4.2.2.6 TImer expiry and counter mismatch tests (TI).14
5 Test Purposes (TPs) .14
5.1 Introduction .14
5.1.1 TP definition conventions .14
5.1.2 References.15
5.1.3 TP naming conventions.15
5.2 CC.16
5.2.1 CC/IT.16
5.2.2 CC/CA .16
5.2.3 CC/BV .16
5.2.3.1 CC/BV/OC .17
5.2.3.2 CC/BV/IC .18
5.2.3.3 CC/BV/CI .19
5.2.3.4 CC/BV/CR.21
5.2.3.5 CC/BV/SC.22
5.2.3.6 CC/BV/PM .22
5.2.3.7 CC/BV/RS.23
5.2.4 CC/BO .24
5.2.5 CC/BI.24
5.2.6 CC/TI.25
5.3 MM.26
5.3.1 MM/IT .26
5.3.2 MM/CA .26
5.3.3 MM/BV.26
5.3.3.1 MM/BV/ID .27
5.3.3.2 MM/BV/AU.28
5.3.3.3 MM/BV/LO .29

Page 4
ETS 300 497-6: August 1996
5.3.3.4 MM/BV/AR . 31
5.3.3.5 MM/BV/KA. 32
5.3.3.6 MM/BV/PR . 32
5.3.3.7 MM/BV/CH . 33
5.3.4 MM/BO. 34
5.3.5 MM/BI . 34
5.3.6 MM/TI. 35
5.4 ME. 36
5.4.1 ME/BV. 36
5.4.2 ME/BO . 37
5.5 LC. 37
5.5.1 LC/BV . 37
5.5.1.1 LC/BV/LE . 38
5.5.1.2 LC/BV/LR . 38
5.5.1.3 LC/BV/LS . 39
5.5.1.4 LC/BV/LL. 39
5.5.2 LC/BI. 39
5.5.3 LC/TI. 40
5.6 IS. 40
5.6.1 IS/BV. 40
5.7 MO. 41
5.8 CL. 41
5.8.1 CL/BV . 41
Annex A (informative): Bibliography . 42
History. 43

Page 5
ETS 300 497-6: August 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Radio Equipment and
Systems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI).
The DECT Test Specification multipart ETS comprises nine parts, as follows:
Part 1: "Part 1: Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control
(MAC) layer".
Part 2: "Part 2: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio
Termination (PT)".
Part 3: "Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio
Termination (FT)".
Part 4: "Part 4: Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer".
Part 5: "Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer".
Part 6: "Part 6: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer -
Portable radio Termination (PT)".
Part 7: "Part 7: Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination
(PT)".
Part 8: "Part 8: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixed
radio Termination (FT)".
Part 9: "Part 9: Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".
Transposition dates
Date of adoption of this ETS: 16 August 1996
Date of latest announcement of this ETS (doa): 30 November 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 May 1997
Date of withdrawal of any conflicting National Standard (dow): 31 May 1997

Page 6
ETS 300 497-6: August 1996
Blank page
Page 7
ETS 300 497-6: August 1996
1 Scope
This European Telecommunication Standard (ETS) contains the test specification for the Digital
Enhanced Cordless Telecommunications (DECT) (ETS 300 175 [1] to [8]).
The objective of this test specification is to provide a basis for approval tests for DECT equipment giving a
high probability of air interface inter-operability between different manufacturer's DECT equipment. This
test specification defines the Test Suite Structure (TSS) and Test Purposes (TP) for testing of the Network
(NWK) layer at the Portable radio Termination (PT).
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [21]) as well as the ETSI
rules for conformance testing (ETS 300 406 [29]) are used as a basis for the test methodology.
Test specifications for the Physical Layer (PHL) are provided in other DECT standards.
2 Normative references
This ETS incorporates, by dated or 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 175-1 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 1: Overview".
[2] ETS 300 175-2 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 2: Physical
layer".
[3] ETS 300 175-3 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 3: Medium
access control layer".
[4] ETS 300 175-4 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 4: Data link
control layer".
[5] ETS 300 175-5 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 5: Network
layer".
[6] ETS 300 175-6 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 6: Identities
and addressing".
[7] ETS 300 175-7 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 7: Security
features".
[8] ETS 300 175-8 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 8: Speech
coding and transmission".
[9] ETS 300 175-9 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 9: Public
access profile".
[10] ETS 300 444: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Generic Access Profile (GAP)".

Page 8
ETS 300 497-6: August 1996
[11] ETS 300 370: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications/Global System for Mobile communications
(DECT/GSM) inter-working profile; Access and mapping (Protocol/procedure
description for 3,1 kHz speech service)".
[12] ETS 300 434: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT) and Integrated Services Digital Network
(ISDN) inter-working for end system configuration".
[13] ETS 300 331: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); DECT Authentication Module (DAM)".
[14] CCITT Recommendation G.726 (1991): "40, 32, 24, 16 kbit/s adaptive
differential pulse code modulation (ADPCM)".
[15.20] Reserved values.
[21] ISO/IEC 9646-1 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts". (See also CCITT Recommendation X.290 (1991)).
[22] ISO/IEC 9646-2 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 2:
Abstract test suite specification". (See also CCITT Recommendation X.291
(1991)).
[23] ISO/IEC 9646-3 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 3:
The tree and tabular combined notation". (See also CCITT Recommendation
X.292 (1992)).
[24] ISO/IEC 9646-4 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 4:
Test realisation". (See also CCITT Recommendation X.292 (1992)).
[25] ISO/IEC 9646-5 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 5:
Requirements on test laboratories and clients for the conformance assessment
process". (See also CCITT Recommendation X.292 (1992)).
[26] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".
[27] ISO/IEC 9646-7 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation conformance statement".
[28] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference model".
[29] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[30] 91/263/EEC: "Council Directive of 29 April 1991 on the approximation of the
laws of the Member states concerning telecommunications terminal equipment,
including the mutual recognition of their conformity. (Terminal Directive)".
[31.40] Reserved values.
[41] I-ETS 300 176: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Approval test specification".

Page 9
ETS 300 497-6: August 1996
[42] TBR 6: "Radio Equipment and Systems (RES); Digital European Cordless
Telecommunications (DECT); General terminal attachment requirements".
[43] TBR 10: "Radio Equipment and Systems (RES); Digital European Cordless
Telecommunications (DECT); General terminal attachment requirements:
Telephony applications".
[44] TBR 11 (1992): "Radio Equipment and Systems (RES); Attachment
requirements for terminal equipment for Digital European Cordless
Telecommunications (DECT) Public Access Profile (PAP) applications".
[45] ETS 300 323 (1994): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Public Access Profile (PAP) test
specification".
[46] ETS 300 476: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Protocol
Implementation Conformance Statement (PICS) proforma".
[47] ETS 300 497: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI) Test Case
Library (TCL)".
[48] ETS 300 474: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Generic Access Profile (GAP); Profile
requirement list and profile specific Implementation Conformance Statement
(ICS) proforma".
[49] ETS 300 494: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Generic Access Profile (GAP); Profile
Test Specification (PTS)".
[50] TBR 22: "Radio Equipment and Systems (RES); Attachment requirements for
terminal equipment for Digital Enhanced Cordless Telecommunications (DECT)
Generic Access Profile (GAP) applications".

Page 10
ETS 300 497-6: August 1996
3 Definitions and abbreviations
3.1 DECT definitions
For the purposes of this ETS, the definitions given in ISO/IEC 9646-1 [21], ISO/IEC 9646-2 [22],
ETS 300 175-1 [1], ETS 300 175-5 [5], ETS 300 175-6 [6] and ETS 300 175-7 [7] apply.
3.2 DECT abbreviations
For the purposes of this ETS the NWK layer abbreviations defined in ETS 300 175-5 [5] and the following
abbreviations apply:
AC Authentication Code
AR Access Rights
AU Authentication
CA CApability
CC Call Control
CCSM Call Control State Machine
CI Call Information
CH Ciphering
CR Call Release
CTS Conformance Testing Services
DECT Digital Enhanced Cordless Telecommunication
DLC Data Link Control layer
ETSI European Telecommunications Standards Institute
FT Fixed radio termination
GAP Generic Access Profile
IC Incoming Call
ID Identification
IPUI International Portable User Identity
IPEI International Portable Equipment Identity
KA Key Allocation
LC Link Control entity
LE Connection oriented Link Establishment
LL ConnectionLess Link control
LO Location
LR Connection oriented Link Release
LS Connection oriented Link Suspend and resume
MAC Medium Access Control layer
ME Management Entity
ML Connectionless Message Services
MM Mobility Management
MO Connection Oriented Message Services
NWK Network layer
OC Outgoing Call
PAP Public Access Profile
PARK Portable Access Rights Key
PM Packet Mode
PR Parameter Retrieval
PT Portable radio termination
RPN Radio Fixed Part Number
RS Call Related Supplementary Services
SC Service Change
UAK User Authentication Key
Page 11
ETS 300 497-6: August 1996
3.3 ISO 9646 definitions
For the purposes of this ETS the following ISO 9646 definitions apply:
Implementation Under Test (IUT)
System Under Test (SUT)
Abstract Test Suite (ATS)
Point of Control and Observation (PCO)
Protocol Implementation Conformance Statement (PICS)
Protocol Implementation eXtra Information for Testing (PIXIT)
Lower Tester (LT)
Upper Tester (UT)
3.4 ISO 9646 abbreviations
For the purposes of this ETS the following ISO 9646 abbreviations apply:
ATS Abstract Test Suite
ASP Abstract Service Primitive
BI Invalid Behaviour
BO InOpportune Behaviour
BV Valid Behaviour
CA CApability tests
ETS European Telecommunication Standard
ISO International Organisation for Standardisation
IUT Implementation Under Test
IWU InterWorking Unit
LT Lower Tester
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statements
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
Page 12
ETS 300 497-6: August 1996
4 Test Suite Structure (TSS)
4.1 TSS overview
IT
NWK CC
CA
BV OC
BO IC
BI CI
TI CR
SC
PM
RS
IT
MM
CA
ID
BV
BO AU
BI LO
AR
TI
KA
PR
CH
ME
BV
BO
LC BV
LE
BI
LR
LS
TI
LL
IS
BV
MO
ML BV
Figure 1: TSS
Page 13
ETS 300 497-6: August 1996
4.2 Test groups
4.2.1 Protocol groups
4.2.1.1 Call Control (CC)
Ref.: ETS 300 175-5 [5], subclause 5.2 and clause 9
4.2.1.2 Mobility Management (MM)
Ref.: ETS 300 175-5 [5], subclause 5.6 and clause 13
4.2.1.3 Lower Layer Management Entity (LLME)
Ref.: ETS 300 175-5 [5], clause 15
4.2.1.4 Link Control (LC)
Ref.: ETS 300 175-5 [5], subclause 5.7 and clause 14
4.2.1.5 Call Independent Supplementary Services (CISS)
Ref.: ETS 300 175-5 [5], subclauses 5.3 and 10.4.2.2
4.2.1.6 Connection Oriented Message Services (COMS)
Ref.: ETS 300 175-5 [5], subclause 5.4 and clause 11
4.2.1.7 ConnectionLess Message Services (CLMS)
Ref.: ETS 300 175-5 [5], subclause 5.5 and clause 12
4.2.2 Main test groups
4.2.2.1 Basic InTerconnection tests (IT)
IT tests provide limited testing of an IUT in order to establish that there is sufficient conformance for
possible interconnection without trying to perform thorough testing. In particular, only those test cases will
be executed which will assure the sufficient interconnection between the IUT of the NWK layer and the
test system exists, so that the rest of the test cases can then be put into execution.
4.2.2.2 CApability tests (CA)
CA tests provide limited testing that the observable capabilities of the IUT are in accordance with the static
conformance requirements and the additional capabilities claimed in the PICS/PIXIT. In particular, this test
group can be regarded as a set of spot checks for all the capabilities of the IUT stated in the PICS/PIXIT.
Scope of the test group is the observable capabilities of the IUT with respect to NWK layer connection,
call control, and the mobility management.
4.2.2.3 Valid Behaviour tests (BV)
BV group tests an IUT in response to valid behaviour of the test system. "Valid" means that a test event is
syntactically and contextually correct. All test cases in the valid behaviour group are intended to verify as
thoroughly as possible the various functions of the protocol.

Page 14
ETS 300 497-6: August 1996
4.2.2.4 Invalid Behaviour tests (BI)
BI group is intended to verify that the IUT is able to react properly in case an invalid protocol data unit
(message) occurring. Invalid PDU here means syntactically or semantically invalid test events generated
by the test system. A syntactically or semantically invalid test event regardless of the current state is not
allowed.
4.2.2.5 InOpportune Behaviour tests (BO)
BO test group is intended to verify that the IUT is able to react properly in case an inopportune test event
occurring. Such an event is syntactically correct, but occurs when it is not allowed.
4.2.2.6 TImer expiry and counter mismatch tests (TI)
Different timers and counters are defined to supervise the various state transitions. This test subgroup is
intended to verify that the IUT is reacting properly to an expiry of one of the timers or counters mismatch.
5 Test Purposes (TPs)
Each test case is allocated directly under a defined TP.
5.1 Introduction
5.1.1 TP definition conventions
The TPs are defined following particular rules as shown in the table 1.
Table 1: TP definition rules
TP Id according to Reference
the TP naming
conventions
Initial condition
Source reference Stimulus
Expected behaviour
TP Id: the TP Id is a unique identifier it shall be specified according to the TP naming
conventions defined in the subclause below.
Reference: the reference should contain the references of the subject to be validated by the
actual TP (specification reference, clause, paragraph).
Condition: the condition defines in which initial state the IUT has to be to apply the actual
TP.
Stimulus: the stimulus defines the test event to which the TP is related.
Expected behaviour: definition of the events that are expected from the IUT to conform to the base
specification.
Page 15
ETS 300 497-6: August 1996
5.1.2 References
This subclause defines the use of references given in the TPs. The structure provides the interrelationship
with:
- the source ETS giving the clause/subclause reference;
- the profile ETS giving the clause/subclause reference; and
- the cross reference to the output of the CTS 5 project (see annex A).
5.1.3 TP naming conventions
The identifier of the TP is built according to table 2:
Table 2: TP naming convention
TP/////
= type of radio termination PT Portable radio Termination
   = functional module CC Call Control
MM Mobility Management
ME Lower Layer Management Entity
LC Link Control Entity
IS Call Independent Supplementary Services
MO Connection Oriented Message Service
ML Connectionless Message Service
x      = Type of testing IT Basic Interconnection Tests
CA CApability Tests
BV Valid Behaviour Tests
BO Inopportune Behaviour Tests
BI Invalid Behaviour Tests
TI Timer expiry and counter mismatch tests
s = test subgroup OC Outgoing Call establishment
IC Incoming Call establishment
CI Call Information
CR Call Release
SC Service Change
PM Packet Mode
RS Call Related Supplementary services
ID Identification
AU Authentification
LO Location
AR Access Rights
KA Key Allocation
PR Parameter Retrieval
CH Ciphering
LE Connection oriented Link Establishment
LR Connection oriented Link Release
LS Connection oriented Link Suspend and
resume
LL ConnectionLess Link Control
  = sequential number (01-99) Test Purpose Number

Page 16
ETS 300 497-6: August 1996
5.2 CC
Test group objectives:
To check the behaviour of the CC module of the IUT.
Subgroups:
- IT;
- CA;
- BV;
- BO;
- BI;
- TI.
5.2.1 CC/IT
- TP/PT/CC/BV/OC-01.
5.2.2 CC/CA
- TP/PT/CC/BV/OC-01;
- TP/PT/CC/BV/IC-01.
5.2.3 CC/BV
Subgroups:
- OC;
- IC;
- CI;
- CR;
- SC;
- PM;
- RS.
Page 17
ETS 300 497-6: August 1996
5.2.3.1 CC/BV/OC
Test subgroup objectives:
To check the IUT's behaviours to setup an outgoing call.
Test purposes:
TP/PT/CC/BV/OC-01 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
N_106 ETS 300 444 [10], subclause 8.1, figure 1
ETS 300 323-1 [45], subclause 5.3.1.1
Initial state: T-00
Verify that the IUT is able to perform a CC-state transition from the T-00 state
to T-10 state via T-01 , T-02, T-03 and T-04 for an outgoing normal call set-up
using piecewise method to transfer dialling information in state T-02.
TP/PT/CC/BV/OC-02 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
New ETS 300 444 [10], subclause 8.1, figure 2
Initial state: T-00
Verify that the IUT is able to perform a CC-state transition from the T-00 state
to T-10 state via T-01 for an outgoing normal call set-up using piecewise
method to transfer dialling information in state T-10.
TP/PT/CC/BV/OC-03 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
N_129 ETS 300 444 [10], subclause 8.1, figure 3
ETS 300 323-1 [45], subclause 5.3.1.1
Initial state: T-00
Verify that the IUT is able to perform a CC-state transition from the T-00 state
to T-10 state via T-01 and T-02 for an outgoing normal call set-up using
piecewise method to transfer dialling information in states T-02 and T-10.
TP/PT/CC/BV/OC-04 Reference: ETS 300 175-5 [5], subclauses 9.3.1.4 and 9.3.1.5,
New ETS 300 444 [10], subclause 8.3, figure 9, table 11
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.1
Initial state: T-01
Verify that the IUT is able to connect the U-plane on receipt of the {CC-
SETUP-ACK} message with the information element < INDICATOR>> containing "in-band information or appropriate pattern now
available".
TP/PT/CC/BV/OC-05 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
N_101, 2, 3, ETS 300 323-1 [45], subclause 5.3.1.1
N_1050, 56, 59-70, DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.1
Initial state: T-00
Verify that the IUT is able to perform a CC-state transition from the T-00 state
to T-10 state via T-01 , T-02, T-03 and T-04 for an outgoing normal call set-up
using en-bloc method to transfer dialling information.
TP/PT/CC/BV/OC-06 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
N_150 ETS 300 323-1 [45], subclause 5.3.1.8
Initial state: T-00
Verify that the IUT is able, prior to subscription, to perform a CC-state
transition from the T-00 state to T-10 state for an outgoing emergency call
set-up.
TP/PT/CC/BV/OC-07 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.1
N_151, ETS 300 323-1 [45], subclause 5.3.1.8
N_1052, 53 DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.1
Initial state: T-00
Verify that the IUT is able, when it has subscription record in FT, to perform a
CC-state transition from the T-00 state to T-10 state for an outgoing
emergency call set-up.
Page 18
ETS 300 497-6: August 1996
5.2.3.2 CC/BV/IC
Test subgroup objectives:
To check the IUT's behaviours to setup an incoming call.
Test purposes:
TP/PT/CC/BV/IC-01 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.2
N_120 ETS 300 444 [10], subclause 8.11, figure 28
N_1094 (state T-07) ETS 300 323-1 [45], subclause 5.3.1.2
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.2
Initial state: T-00
Verify that the IUT is able to process an incoming call via the states T-06, T-
07 and T-08 to the state T-10. The information element <> is in the
{CC-INFO} message.
TP/PT/CC/BV/IC-02 Reference: ETS 300 175-5 [5], subclauses 9.1, 9.2, 9.3.2
N_1090 ETS 300 444 [10], subclause 8.11, figure 29
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.2
Initial state: T-00
Verify that the IUT is able to process an incoming call via the states T-06, T-
07 and T-08 to the state T-10. The information element <> is in the
{CC-SETUP} message.
TP/PT/CC/BV/IC-03 Reference: ETS 300 175-5 [5], subclauses 9.3.2.4
New ETS 300 444 [10], subclause 8.12 (future GAP)
Initial state: T-00
Verify that the IUT in case of incoming call, is able to connect the U-plane on
receipt of the {CC-SETUP} message with the information element
<> containing "in-band information or appropriate
pattern now available".
TP/PT/CC/BV/IC-04 Reference: ETS 300 175-5 [5], subclauses 9.3.2.4
New ETS 300 444 [10], subclause 8.14 (future GAP)
Initial state: T-00
Verify that the IUT in case of incoming call, is able to connect the U-plane on
receipt of a {CC-INFO} message with the information element < INDICATOR>> containing "in-band information or appropriate pattern now
available".
Page 19
ETS 300 497-6: August 1996
5.2.3.3 CC/BV/CI
Test subgroup objectives:
To check the IUT's behaviours for information transfer.
Test purposes:
TP/PT/CC/BV/CI-01 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_125 ETS 300 444 [10], subclause 8.13
N_1132
ETS 300 323-1 [45], subclause 5.3.1.7
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Verify that the IUT is able to alert the user of an incoming call, when the
information element <> is present in the {CC-SETUP} message.
TP/PT/CC/BV/CI-02 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_145
ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-02
Verify that the IUT, after the user has invoked pulse (decadic) dialling, sends
a {CC-INFO} message with a <> information element
containing keypad-info '12H' (goto pulse).
(feature N.23 in ETS 300 444 [10])
TP/PT/CC/BV/CI-03 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_148 ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-10
Verify that the IUT, after the user has invoked pulse (decadic) dialling, sends
a {CC-INFO} message with a <> information element
containing keypad-info '12H' (goto pulse).
(feature N.23 in ETS 300 444 [10])
TP/PT/CC/BV/CI-04 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_157 ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-02
Verify that the IUT, after the user has invoked dialling pause, sends a {CC-
INFO} message with a <> information element containing
keypad-info '05H' (dialling pause).
(feature N.7 in ETS 300 444 [10])
TP/PT/CC/BV/CI-05 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_158 ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-10
Verify that the IUT, after the user has invoked dialling pause, sends a {CC-
INFO} message with a <> information element containing
keypad-info '05H' (dialling pause).
(feature N.7 in ETS 300 444 [10])
TP/PT/CC/BV/CI-06 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_162 ETS 300 444 [10], subclause 8.10, table 20
N_1138
ETS 300 323-1 [45], subclause 5.3.1.7
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Initial state: T-02
Verify that the IUT, after the user has invoked DTMF dialling with defined tone
length, sends a {CC-INFO} message with a <> information
element containing keypad-info '14H' (goto DTMF, defined tone length).
(feature N.6 in ETS 300 444 [10])
(continued)
Page 20
ETS 300 497-6: August 1996
(concluded)
TP/PT/CC/BV/CI-07 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_163 ETS 300 444 [10], subclause 8.10, table 20
N_1138
ETS 300 323-1 [45], subclause 5.3.1.7
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Initial state: T-10
Verify that the IUT, after the user has invoked DTMF dialling with defined tone
length, sends a {CC-INFO} message with a <> information
element containing keypad-info '14H' (goto DTMF, defined tone length).
(feature N.6 in ETS 300 444 [10])
TP/PT/CC/BV/CI-08 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_165 ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-02
Verify that the IUT, after the user has invoked DTMF dialling with infinite tone
length, sends a {CC-INFO} message with a <> information
element containing keypad-info '16H' (goto DTMF, infinite tone length).
(feature N.22 in ETS 300 444 [10])
TP/PT/CC/BV/CI-09 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_166
ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-10
Verify that the IUT, after the user has invoked DTMF dialling with infinite tone
length, sends a {CC-INFO} message with a <> information
element containing keypad-info '16H' (goto DTMF, infinite tone length).
(feature N.22 in ETS 300 444 [10])
TP/PT/CC/BV/CI-10 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_170 ETS 300 444 [10], subclause 8.10, table 20
ETS 300 323-1 [45], subclause 5.3.1.7
Initial state: T-02
Verify that the IUT, after the user has invoked the sending of the basic digits
(0-9, star, hash mark), sends one or more {CC-INFO} messages with
<> information elements containing the basic digits.
(feature N.4 in ETS 300 444 [10])
TP/PT/CC/BV/CI-11 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
New ETS 300 444 [10], subclause 8.18, table 30 and 31
Verify that the IUT, after the user has invoked an internal call, performs either
one of the possible internal call setups, as described in ETS 300 444 [10],
subclause 8.18, table 30 and 31.
TP/PT/CC/BV/CI-12 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_168
ETS 300 444 [10], subclause 8.16, table 27
N_1130 ETS 300 323-1 [45], subclause 5.3.1.7
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Initial state: T-07
Verify that the IUT, on reception of <> information
elements, containing standard characters in {CC-INFO} messages, is able to
show these characters on the display.
TP/PT/CC/BV/CI-13 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_169 ETS 300 444 [10], subclause 8.16, table 27
N_1131
ETS 300 323-1 [45], subclause 5.3.1.7
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Initial state: T-07
Verify that the IUT, on reception of <> information
elements, containing control characters in {CC-INFO} messages, is able to
understand and react upon these characters.
TP/PT/CC/BV/CI-14 Reference: ETS 300 175-5 [5], subclause 9.3.1.5
N_306 ETS 300 444 [10], subclause 8.10, table 20
N_1143
ETS 300 323-1 [45], subclause 5.3.3.3
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.4
Initial state: T-10
Verify that the IUT, after invocation of 'register recall', is able to activate the
feature register recall in a {CC-INFO} message.

Page 21
ETS 300 497-6: August 1996
5.2.3.4 CC/BV/CR
Test subgroup objectives:
To check the IUT's behaviour to release an outgoing and incoming call.
Test purposes:
TP/PT/CC/BV/CR-01 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_1185 ETS 300 444 [10], subclause 8.3.2.4
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-02
Verify that the IUT is able to process a FT initiated normal release.
TP/PT/CC/BV/CR-02 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_112
ETS 300 444 [10], subclause 8.7
N_1168 ETS 300 323 [45], subclause 5.3.1.3
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-03
Verify that the IUT is able to process a FT initiated normal release.
TP/PT/CC/BV/CR-03 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_113 ETS 300 444 [10], subclause 8.7
N_1169
ETS 300 323 [45], subclause 5.3.1.3
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-04
Verify that the IUT is able to process a FT initiated normal release.
TP/PT/CC/BV/CR-04 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_124
ETS 300 444 [10], subclause 8.7
N_1172 ETS 300 323 [45], subclause 5.3.1.3
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-08
Verify that the IUT is able to process a FT initiated normal release.
TP/PT/CC/BV/CR-05 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_114 ETS 300 444 [10], subclause 8.7
N_1173
ETS 300 323 [45], subclause 5.3.1.3
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-10
Verify that the IUT is able to process a FT initiated normal release.
TP/PT/CC/BV/CR-06 Reference: ETS 300 175-5 [5], subclause 9.5.1
N_134 ETS 300 444 [10], subclause 8.7
ETS 300 323 [45], subclause 5.3.1.3
Initial state: T-10
Verify that the IUT is able to process an IUT initiated normal release.
TP/PT/CC/BV/CR-07 Reference: ETS 300 175-5 [5], subclause 9.5.2
N_107 ETS 300 444 [10], subclause 8.2.2.3
ETS 300 323 [45], subclause 5.3.1.4
Initial state: T-01
Verify that the IUT is able to process a FT initiated abnormal release.
TP/PT/CC/BV/CR-08 Reference: ETS 300 175-5 [5], subclause 9.5.2
N_108 ETS 300 444 [10], subclause 8.3.2.2
ETS 300 323 [45], subclause 5.3.1.4
Initial state: T-02
Verify that the IUT is able to process a FT initiated abnormal release.
TP/PT/CC/BV/CR-09 Reference: ETS 300 175-5 [5], subclause 9.5.2
N_111
ETS 300 444 [10], subclause 8.8
N_1178 ETS 300 323 [45], subclause 5.3.1.4
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-10
Verify that the IUT is able to process a FT initiated abnormal release.
(continued)
Page 22
ETS 300 497-6: August 1996
(concluded)
TP/PT/CC/BV/CR-10 Reference: ETS 300 175-5 [5], subclause 14.2.7
N_137 ETS 300 444 [10], subclause 8.9
ETS 300 323 [45], subclause 5.3.1.5
Initial state: T-10
Verify that the IUT is able to process a FT initiated partial release.
TP/PT/CC/BV/CR-11 Reference: ETS 300 175-5 [5], subclause 14.2.7
N_1184
ETS 300 444 [10], subclause 8.9
DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-10
Verify that the IUT is able to process an IUT initiated partial release.
TP/PT/CC/BV/CR-12 Reference: ETS 300 175-5 [5], subclause 14.2.7
N_1180 DEL. 2 Part 6.1 (see annex A), subclause 5.2.1.5
Initial state: T-19
Verify that the IUT, when a normal release procedure has been started, is
able to handle a {CC-INFO} message sent by the FT.
5.2.3.5 CC/BV/SC
There are no test purposes defined for this group in this ETS.
5.2.3.6 CC/BV/PM
There are no test purposes defined for this group in this ETS.

Page 23
ETS 300 497-6: August 1996
5.2.3.7 CC/BV/RS
Test
...