SIST EN 300 182-3 V1.3.2:2003

SLOVENSKI STANDARD
01-december-2003
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±'RSROQLOQDVWRULWHYREYHVWLOR
RFHQL$2&±3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW'66±GHO
=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQLSUHVNXãDQMD766 73±6SHFLILNDFLMD]D
XSRUDEQLND
Integrated Services Digital Network (ISDN); Advice of Charge (AOC) 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 182-3 Version 1.3.2
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);
Advice of Charge (AOC) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
2 ETSI EN 300 182-3 V1.3.2 (2000-05)
Reference
REN/SPS-05165-3
Keywords
AOC, DSS1, ISDN, supplementary service,
TSS&TP, user
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33493654716
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:
editor@etsi.fr
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 182-3 V1.3.2 (2000-05)
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 182-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.9
5.1.3 TP structure.9
5.1.4 Test strategy.9
5.2 User TPs for AOC .10
5.2.1 Subscription option dependent.10
5.2.1.1 Per-call basis .10
5.2.1.1.1 Activation .10
5.2.1.1.1.1 Normal .10
5.2.1.1.1.2 Exceptions.12
5.2.1.1.2 GFP.17
5.2.1.2 All calls .17
5.2.1.2.1 Activation .17
5.2.1.2.1.1 Transfer - call establishment phase .17
5.2.1.2.1.2 Exceptions.19
5.2.1.2.1.3 GFP.21
5.2.2 Subscription option independent.21
5.2.2.1 Independent of bearer.21
5.2.2.1.1 Normal.22
5.2.2.1.2 GFP.23
5.2.2.2 Transfer - active phase .24
5.2.2.3 Transfer - clearing phase.24
6 Compliance .30
7 Requirements for a comprehensive testing service.30
Annex A (informative): Changes with respect to the previous ETS 300 182-3 .31
History.32
ETSI
4 ETSI EN 300 182-3 V1.3.2 (2000-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 3 of a multi-part EN covering the Digital Subscriber Signalling System No. one (DSS1)
protocol specification for the Integrated Services Digital Network (ISDN) Advice of Charge (AOC) supplementary
service, as identified 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 basic call specifications.
National transposition dates
Date of adoption of this EN: 28 April 2000
Date of latest announcement of this EN (doa): 31 July 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 January 2001
Date of withdrawal of any conflicting National Standard (dow): 31 January 2001
ETSI
5 ETSI EN 300 182-3 V1.3.2 (2000-05)
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 [7]) of
implementations conforming to the stage three standard for the Advice of Charge (AOC) 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 182-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 182-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 182-1 (V1.2): "Integrated Services Digital Network (ISDN); Advice of Charge
(AOC) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 1: Protocol specification".
[2] ETSI EN 300 182-2 (V1.2): "Integrated Services Digital Network (ISDN); Advice of Charge
(AOC) 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 and terms for ISDNs".
[10] ITU-T Recommendation E.164 (1997): "The international public telecommunication numbering
plan".
ETSI
6 ETSI EN 300 182-3 V1.3.2 (2000-05)
[11] ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported by
an ISDN and the means to describe them".
[12] ETSI ETS 300 196-2: "Integrated Services Digital Network (ISDN); Generic functional protocol
for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".
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 182-1
call reference: 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
invoke component: see EN 300 196-1 [6], subclause 11.2.2.1
ISDN number: a number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [10]
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 AOC 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
ETSI
7 ETSI EN 300 182-3 V1.3.2 (2000-05)
user: DSS1 protocol entity at the User side of the user-network interface where a T reference point or coincident S and
T reference point applies
user (S/T): DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference
point applies
user (T): DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is
a Private ISDN)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOC Advice of Charge
ATM Abstract Test Method
ATS Abstract Test Suite
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 Null call state
U02 Overlap Sending 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
U19 Release Request call state
ETSI
8 ETSI EN 300 182-3 V1.3.2 (2000-05)
4 Test Suite Structure (TSS)
AOC - User
Subscription option Subscription option
dependent independent
Per-call basis All calls
Activation GFP
(03)
Normal Exceptions
(01) (02)
Activation Independent of bearer
Normal GFP
(07) (08)
Transfer - Call Exceptions GFP Transfer - Active Transfer - Clearing
Est (05) (06) (09) (10)
(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 test suite and whether it applies to the network or the user (see table 1).
ETSI
9 ETSI EN 300 182-3 V1.3.2 (2000-05)
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "AOC"
= 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 182-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.
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
U10 etc.
/ /AOC-S Idle,.
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 remains in the same state
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 182-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 182-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.
ETSI
10 ETSI EN 300 182-3 V1.3.2 (2000-05)
5.2 UserTPs forAOC
All PICS items referred to in this subclause are as specified in EN 300 182-2 [2] unless indicated otherwise by another
numbered reference.
5.2.1 Subscription option dependent
5.2.1.1 Per-call basis
Selection: IUT supports procedures related to the subscription option "AOC requested on a per-call basis" (this applies
to whole group). PICS: SC 1 or SC 2 or SC 3.
5.2.1.1.1 Activation
5.2.1.1.1.1 Normal
AOC_U01_001 subclause 9.1.1 valid optional
Ensure that the IUT in U00/AOC Idle state in order to activate the AOC-S supplementary service, sends a SETUP
message including a Facility information element coded as chargingRequest invoke component indicating AOC-S and
enters the U01/AOC Request state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_002 subclause 9.1.1 valid optional
Ensure that the IUT in U00/AOC Idle state in order to activate the AOC-D supplementary service, sends a SETUP
message including a Facility information element coded as chargingRequest invoke component indicating AOC-D and
enters the U01/AOC Request state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U01_003 subclause 9.1.1 valid optional
Ensure that the IUT in U00/AOC Idle state in order to activate the AOC-E supplementary service, sends a SETUP
message including a Facility information element coded as chargingRequest invoke component indicating AOC-E and
enters the U01/AOC Request state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U01_004 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", enters the
U02/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_005 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a CALL PROCEEDING message including a Facility
information element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", enters the
U03/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_006 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a PROGRESS message including a Facility information
element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", enters the U03/AOC
Active state.
Selection: AOC-S supported. PICS: MC 1.
ETSI
11 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U01_007 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of an ALERTING message including a Facility information
element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", accepts the provided
information, enters the U04/AOC Active state and sends no message.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_008 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", sends no message or
sends a CONNECT ACKNOWLEDGE containing no component related to the received component and enters the
U10/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_009 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a FACILITY message including a Facility information
element coded as chargingRequest return result component indicating "AOCSCurrencyInfoList", enters the U01/AOC
Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_010 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", enters the
U02/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_011 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a CALL PROCEEDING message including a Facility
information element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", enters the
U03/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_012 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a PROGRESS message including a Facility information
element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", enters the U03/AOC
Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_013 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of an ALERTING message including a Facility information
element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", enters the U04/AOC
Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_014 subclause 9.2.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", sends no message or
sends a CONNECT ACKNOWLEDGE containing no component related to the received component and enters the
U10/AOC Active state.
Selection: AOC-S supported. PICS: MC 1.
ETSI
12 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U01_015 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a FACILITY message including a Facility information
element coded as chargingRequest return result component indicating "AOCSSpecialArrInfo", enters the U01/AOC
Active state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U01_016 subclause 9.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element coded as chargingRequest return result component indicating "chargingInfoFollows", enters the
U02/AOC Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
AOC_U01_017 subclause 9.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a CALL PROCEEDING message including a Facility
information element coded as chargingRequest return result component indicating "chargingInfoFollows", enters the
U03/AOC Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
AOC_U01_018 subclause 9.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a PROGRESS message including a Facility information
element coded as chargingRequest return result component indicating "chargingInfoFollows", enters the U03/AOC
Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
AOC_U01_019 subclause 9.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of an ALERTING message including a Facility information
element coded as chargingRequest return result component indicating "chargingInfoFollows", enters the U04/AOC
Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
AOC_U01_020 subclause 9.1.1 valid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element coded as chargingRequest return result component indicating "chargingInfoFollows", sends no message or
sends a CONNECT ACKNOWLEDGE containing no component related to the received component and enters the
U10/AOC Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
AOC_U01_021 subclause 9.1.1 valid optional
Ensure that the IUT in U01/AOC Request state, on receipt of a FACILITY message including a Facility information
element coded as chargingRequest return result component indicating "chargingInfoFollows", enters the U01/AOC
Active state.
Selection: AOC-D supported OR AOC-E supported. PICS: MC 2 or MC 3.
5.2.1.1.1.2 Exceptions
AOC_U02_001 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element coded as chargingRequest return error component, continues normal call handling and enters
U02/AOC Idle state.
ETSI
13 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U02_002 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a CALL PROCEEDING message including a Facility
information element coded as chargingRequest return error component, continues normal call handling and enters
U03/AOC Idle state.
AOC_U02_003 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of a PROGRESS message including a Facility information
element coded as chargingRequest return error component, continues normal call handling and enters U03/AOC Idle
state.
AOC_U02_004 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of an ALERTING message including a Facility information
element coded as chargingRequest return error component, continues normal call handling and enters U04/AOC Idle
state.
AOC_U02_005 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element coded as chargingRequest return error component, continues normal call handling and enters U10/AOC Idle
state.
AOC_U02_006 subclause 9.1.2 c), d), e) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a FACILITY message including a Facility information
element coded as chargingRequest return error component, continues normal call handling and enters U01/AOC Idle
state.
AOC_U02_007 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element with a chargingRequest reject component, takes no protocol actions and enters U02/AOC Idle state.
AOC_U02_008 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a CALL PROCEEDING message including a Facility
information element with a chargingRequest reject component, takes no protocol actions and enters U03/AOC Idle state.
AOC_U02_009 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of a PROGRESS message including a Facility information
element with a chargingRequest reject component, takes no protocol actions and enters U03/AOC Idle state.
AOC_U02_010 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of an ALERTING message including a Facility information
element with a chargingRequest reject component, takes no protocol actions and enters U04/AOC Idle state.
AOC_U02_011 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element with a chargingRequest reject component, takes no protocol actions and enters U10/AOC Idle state.
AOC_U02_012 subclause 9.1.2 f) inopportune mandatory
Ensure that the IUT in U01/AOC Request state, on receipt of a FACILITY message including a Facility information
element with a chargingRequest reject component, takes no protocol actions and enters U01/AOC Idle state.
ETSI
14 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U02_013 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with an AOCSCurrency invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U02_014 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with an AOCSSpecialArr invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U02_015 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with an AOCDCurrency invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_016 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with an AOCDChargingUnit invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_017 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with an AOCECurrency invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_018 subclause 9.1.2 g) inopportune optional
Ensure that the IUT in U01/AOC Request state, after no response to a chargingRequest invoke component, on receipt of
a CALL PROCEEDING with AOCEChargingUnit invoke component, continues normal call handling and enters
U03/AOC Request state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_019 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U03/AOC Idle state, having received a chargingRequest return error component, on receipt of an
ALERTING with an AOCSCurrency invoke component, accepts the information, sends no message and enters
U04/AOC Idle state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U02_020 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U03/AOC Idle state, having received a chargingRequest return error component, on receipt of an
ALERTING with an AOCSSpecialArr invoke component, accepts the information, sends no message and enters
U04/AOC Idle state.
Selection: AOC-S supported. PICS: MC 1.
ETSI
15 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U02_021 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U03/AOC Idle state, having received a chargingRequest reject component, on receipt of an
ALERTING with an AOCSCurrency invoke component, accepts the information, sends no message and enters
U04/AOC Idle state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U02_022 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U03/AOC Idle state, having received a chargingRequest reject component, on receipt of an
ALERTING with an AOCSSpecialArr invoke component, accepts the information, sends no message and enters
U04/AOC Idle state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U02_023 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
FACILITY message containing a Facility information element with an AOCDCurrency invoke component, accepts the
information, sends no message and remains in U10/AOC Idle state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_024 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
FACILITY message containing a Facility information element with an AOCDChargingUnit invoke component, accepts
the information, sends no message and remains in U10/AOC Idle state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_025 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
FACILITY message containing a Facility information element with an AOCDCurrency invoke component, accepts the
information, sends no message and remains in U10/AOC Idle state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_026 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
FACILITY message containing a Facility information element with an AOCDChargingUnit invoke component, accepts
the information, sends no message and remains in U10/AOC Idle state.
Selection: AOC-D supported. PICS: MC 2.
AOC_U02_027 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
DISCONNECT message containing a Facility information element with an AOCECurrency invoke component, accepts
the information, returns a RELEASE message and enters U19/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_028 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
DISCONNECT message containing a Facility information element with an AOCEChargingUnit invoke component,
accepts the information, returns a RELEASE message and enters U19/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
ETSI
16 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U02_029 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
DISCONNECT message containing a Facility information element with an AOCECurrency invoke component, accepts
the information, returns a RELEASE message and enters U19/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_030 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
DISCONNECT message containing a Facility information element with an AOCEChargingUnit invoke component,
accepts the information, returns a RELEASE message and enters U19/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_031 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U11/AOC Idle state, having received a chargingRequest return error component, on receipt of a
RELEASE message containing a Facility information element with an AOCECurrency invoke component, accepts the
information, returns a RELEASE COMPLETE message and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_032 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U11/AOC Idle state, having received a chargingRequest return error component, on receipt of a
RELEASE message containing a Facility information element with an AOCEChargingUnit invoke component, accepts
the information, returns a RELEASE COMPLETE message and enters U00/AOC Idle state.
Selection:AOC-E supported. PICS: MC 3.
AOC_U02_033 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U11/AOC Idle state, having received a chargingRequest reject component, on receipt of a
RELEASE message containing a Facility information element with an AOCECurrency invoke component, accepts the
information, returns a RELEASE COMPLETE message and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_034 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U11/AOC Idle state, having received a chargingRequest reject component, on receipt of a
RELEASE message containing a Facility information element with an AOCEChargingUnit invoke component, accepts
the information, returns a RELEASE COMPLETE message and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_035 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
RELEASE COMPLETE message containing a Facility information element with an AOCECurrency invoke component,
accepts the information and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_036 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest return error component, on receipt of a
RELEASE COMPLETE message containing a Facility information element with an AOCEChargingUnit invoke
component, accepts the information and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
ETSI
17 ETSI EN 300 182-3 V1.3.2 (2000-05)
AOC_U02_037 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
RELEASE COMPLETE message containing a Facility information element with an AOCECurrency invoke component,
accepts the information and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
AOC_U02_038 subclause 9.1.2 h) inopportune optional
Ensure that the IUT in U10/AOC Idle state, having received a chargingRequest reject component, on receipt of a
RELEASE COMPLETE message containing a Facility information element with an AOCEChargingUnit invoke
component, accepts the information and enters U00/AOC Idle state.
Selection: AOC-E supported. PICS: MC 3.
5.2.1.1.2 GFP
Selection: IUT supports procedures related to the subscription option "AOC requested on a per-call basis" (this
applies to whole group). PICS: SC 1 or SC 2 or SC 3.
AOC_U03_001 subclause 9.2.1.1 & [6] subclauses 8.2.2.4, 8.4.1 invalid optional
Ensure that the IUT in U03/AOC Request state, on receipt of a CONNECT message including a Facility information
element with an invalid chargingRequest return result component, sends a FACILITY message containing a Facility
information element with a reject component, enters the U10 state and remains in the AOC Request state, or sends a
CONNECT ACKNOWLEDGE message containing a Facility information element with a reject component, enters the
U10 state and remains in the AOC Request state.
Selection: AOC-S supported. PICS: MC 1.
AOC_U03_002 subclause 9.2.1.1 & [6] subclauses 8.2.2.4, 8.4.1 invalid optional
Ensure that the IUT in U10/AOC Request state, on receipt of a FACILITY message including a Facility information
element with an invalid chargingRequest return result component, sends a FACILITY message containing a Facility
information element with a reject component and remains in the U10/AOC Request state.
Selection: AOC-S supported. PICS: MC 1.
5.2.1.2 All calls
5.2.1.2.1 Activation
5.2.1.2.1.1 Transfer - call establishment phase
AOC_U04_001 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Idle state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element with a correctly coded AOCSCurrency invoke component indicating "AOCSCurrencyInfoList",
accepts the provided information, sends no message and enters U02/AOC Idle state.
Selection:AOC-S supported. PICS: MC 1.
AOC_U04_002 subclause 9.2.1.1 valid optional
Ensure that the IUT in U01/AOC Idle state, on receipt of a SETUP ACKNOWLEDGE message including a Facility
information element with a
...