Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Advice of Charge (AoC) supplementary services [ISO/IEC 15049 (1997), modified]; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

TSS&TP for Advice of charge.

Zasebno omrežje z integriranimi storitvami (PISN) – Signalizacijski protokol med centralami – Dopolnilna storitev: obvestilo o ceni (AoC) [ISO/IEC 15049 (1995), spremenjen] – 1. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – Specifikacija

General Information

Status
Published
Publication Date
31-Dec-2004
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005
Mandate

Buy Standard

Standard
EN 301 483-1 V1.2.2:2005
English language
17 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 301 483-1 V1.2.2:2005
01-januar-2005
Zasebno omrežje z integriranimi storitvami (PISN) – Signalizacijski protokol med
centralami – Dopolnilna storitev: obvestilo o ceni (AoC) [ISO/IEC 15049 (1995),
spremenjen] – 1. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP)
– Specifikacija
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Advice of
Charge (AoC) supplementary services [ISO/IEC 15049 (1997), modified]; Part 1: Test
Suite Structure and Test Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: EN 301 483-1 Version 1.2.2
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 301 483-1 V1.2.2:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 301 483-1 V1.2.2:2005

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

SIST EN 301 483-1 V1.2.2:2005
ETSI EN 301 483-1 V1.2.2 (2000-09)
European Standard (Telecommunications series)
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Advice of Charge (AoC) supplementary services
for the VPN "b" service entry point;
[ISO/IEC 15049 (1997), modified];
Part 1: Test Suite Structure and
Test Purposes (TSS&TP) specification

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

SIST EN 301 483-1 V1.2.2:2005
2 ETSI EN 301 483-1 V1.2.2 (2000-09)
Reference
DEN/SPAN-05192-2
Keywords
AOC, PISN, QSIG, supplementary service,
TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33 493654716
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

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

SIST EN 301 483-1 V1.2.2:2005
3 ETSI EN 301 483-1 V1.2.2 (2000-09)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope .5
2 References .5
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations .6
4 Test Suite Structure (TSS).7
5 Test Purposes (TP) .7
5.1 Introduction .7
5.1.1 TP naming convention.7
5.1.2 Source of TP definition.7
5.1.3 TP structure.8
5.1.4 Test strategy.8
5.2 TPs for SS-AOC signalling procedures.8
5.2.1 Actions at the Originating PINX.9
5.2.1.1 Normal procedures.9
5.2.1.2 Exceptional procedures .11
5.2.2 Actions at the Outgoing Gateway PINX.12
5.2.2.1 Normal procedures.12
5.2.2.2 Exceptional procedures .13
5.2.2.3 Additional procedures for Call Transfer .13
5.2.2.4 Additional procedures for Call Diversion. .14
5.2.3 Actions at the Terminating PINX .14
5.2.4 Interactions with Call Transfer .15
5.2.5 Interactions with Call Diversion .15
6 Compliance.16
7 Requirements for a comprehensive testing service .16
History .17
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
4 ETSI EN 301 483-1 V1.2.2 (2000-09)
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 1 of a multi-part EN covering the Private Integrated Services Network (PISN); Inter-
exchange signalling protocol; Advice of Charge (AoC) supplementary services [ISO/IEC 15049 (1997), modified]; as
identified below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 2: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma".
National transposition dates
Date of adoption of this EN: 1 September 2000
Date of latest announcement of this EN (doa): 31 December 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 2001
Date of withdrawal of any conflicting National Standard (dow): 30 June 2001
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
5 ETSI EN 301 483-1 V1.2.2 (2000-09)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Advice of charge
supplementary services of the Interexchange signalling protocol for Private Integrated Services Networks (PISN).
The objective of this TSS and TPs specification is to provide conformance tests which give a greater probability of
inter-operability. The TSS and TPs specification covers the procedures described in EN 301 264 [1].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [2], ISO/IEC 9646-2 [3] and
ISO/IEC 9646-3 [4]) is used as basis for the test methodology.
The Test Suite Structure and Test Purposes specified in the present document are only intended for VPN scenarios at
the "b" service entry point.
The VPN "b" service entry point is defined in EN 301 060-1 [5] and ETR 172 [6].
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.
[1] ETSI EN 301 264 (1998): "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Advice of Charge (AoC) supplementary services [ISO/IEC 15050 (1997), modified]".
[2] ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 1: General concepts".
[3] ISO/IEC 9646-2: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 2: Abstract test suite specification".
[4] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[5] ETSI EN 301 060-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry point
for Virtual Private Network (VPN) applications; Part 1: Protocol specification".
[6] ETSI ETR 172: "Business TeleCommunications (BTC); Virtual Private Networking (VPN);
Services and networking aspects; Standardization requirements and work items".
[7] ETSI ETS 300 239: "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Generic functional protocol for the support of supplementary services [ISO/IEC 11582
(1995), modified]".
[8] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[9] ETSI EN 300 172: "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Circuit-mode basic services [ISO/IEC 11572 (1996) modified]".
[10] ITU-T Recommendation I.210: "Principles of the telecommunication services supported by an
ISDN and the means to describe them".
[11] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
6 ETSI EN 301 483-1 V1.2.2 (2000-09)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [2].
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [2].
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [2].
PICS proforma: refer to ISO/IEC 9646-1 [2].
Test Purpose (TP): refer to ISO/IEC 9646-1 [2].
call independent signalling connection: see ETS 300 239 [7], definition 4.7.
call related: see ETS 300 239 [7], definition 4.9.
Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [8], definition 308.
invoke APDU: see ETS 300 239 [7], subclause 11.3.3.4.
originating PINX: see EN 300 172 [9], subclause 4.5.
outgoing Gateway PINX: see EN 300 172 [9], subclause 4.6.
reject APDU: see ETS 300 239 [7], subclause 11.3.3.4.
return error APDU: see ETS 300 239 [7], subclause 11.3.3.4.
return result APDU: see ETS 300 239 [7], subclause 11.3.3.4.
service; telecommunication service: see ITU-T Recommendation I.112 [8], definition 201.
supplementary service: see ITU-T Recommendation I.210 [10], subclause 2.4.
terminating PINX: see EN 300 172 [9], subclause 4.5.
Virtual Private Network (VPN): refer to EN 301 060-1 [5].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
APDU Application Protocol Data Unit
ATS Abstract Test Suite
IE Information Element
ISDN Integrated Services Digital Network
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
PINX Private Integrated Services Network eXchange
PISN Private Integrated Services Network
PSS1 Private Integrated Signalling System Number 1
sc call independent signalling connection
SS Supplementary services
TP Test Purpose
TSS Test Suite Structure
VPN Virtual Private Network
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
7 ETSI EN 301 483-1 V1.2.2 (2000-09)
4 Test Suite Structure (TSS)
SS-AOC signalling procedures at the VPN "b" service entry point Group
Actions at the Originating PINX
Normal procedures Orig01
Exceptional procedures Orig02
Actions at the Outgoing Gateway PINX
Normal procedures Ogw01
Exceptional procedures Ogw02
Additional procedures for Call Transfer Ogw03
Additional procedures for Call Diversion Ogw04
Actions at the Terminating PINX Term01
Interaction with Call Transfer Int01
Interaction with Call Diversion Int02
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: "AOC"
= group up to 8 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 301 264 [1].
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
8 ETSI EN 301 483-1 V1.2.2 (2000-09)
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 for SS-AOC
TP part Text Example
Header
tab seetable1
tab subclause 0.0.0
Stimulus Ensure that the IUT in the
or state 3 or AOC-Idle, etc.
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
andbacktoaorb,
Selection Selection criteria reference Support of SS-AOC in Originating PINX
PICS: A.1
NOTE 1: In order to use the same structure as for test group selection, the selection criteria is indicated at the
bottom of the test purpose
NOTE 2: 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 301 264 [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 Draft EN 301 264 [1].
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 (ETS 300 406 [11]).
All the test purposes are mandatory unless they have a 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 TPs for SS-AOC signalling procedures
All PICS items referred to in this subclause are as specified in EN 301 264 [1] unless indicated otherwise by another
numbered reference.
Unless specified:
- only the requirements from the point of view of the VPN "b" service entry point are considered. This implies
that the interactions with other networks are out of scope of this specification and causes that the corresponding
Test Purposes are not included in this specification;
- the messages indicated are valid and contain at least the mandatory information elements and possibly optional
information elements;
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
9 ETSI EN 301 483-1 V1.2.2 (2000-09)
- the information elements indicated are valid and contain at least the mandatory parameters and possibly
optional parameters.
The following wording convention was defined to make the test purposes more readable:
- when a message is to be sent or received on a call independent signalling connection, the message name shall be
followed by a '(sc)', e.g. CONNECT (sc) means that the CONNECT message is conveyed on a call independent
signalling connection.
All the test purposes are valid for both user and network side of the VPN b interface. In order to simplify the text and to
make the test purposes more readable, only the User side Call states (Ux) are indicated in the test purposes. For the
network side of the VPNb interface, the mapping table below indicates which network call state (Ny) corresponds to the
user call state used in the test purpose. Equivalent call state means there that the same message flow applies from the
IUT point of view (e.g.: IUT sends a SETUP message gives the call state U1 or N6).
User side call state equivalent network
side call state
U0x N0
U1x N6
U3x N9
U4x N7
U10x N10
EXAMPLE: Ensure that the IUT in the call state U1 …
is equivalent to the following network side test purpose:
Ensure that the IUT in the call state N6 …
5.2.1 Actions at the Originating PINX
Selection: IUT supports SS-AOC in Originating PINX. PICS: A1
5.2.1.1 Normal procedures
AOC_Orig01_001 subclause 6.6.1.1.1
Ensure that the IUT in the call state U0 and in the Aoc-Orig-Idle state, in order to invoke one or more AOC service with
the establishment of a new call,
sends a SETUP message including a Facility IE with a chargeRequest invoke APDU and enters the
Aoc-Orig-Wait1-Ack state.
AOC_Orig01_002 subclause 6.6.1.1.1
Ensure that the IUT in the call state U1 and in the Aoc-Orig-Wait1-Ack state, on receipt of a PROGRESS message
including a Facility IE with a chargeRequest return result APDU,
continues with normal call establishment and enters the Aoc-Orig-Active state.
AOC_Orig01_003 subclause 6.6.1.1.1
Ensure that the IUT in the call state U3 and in the Aoc-Orig-Wait1-Ack state, on receipt of an ALERTING message
including a Facility IE with a chargeRequest return result APDU,
continues with normal call establishment and enters the Aoc-Orig-Active state.
AOC_Orig01_004 subclause 6.6.1.1.1
Ensure that the IUT in the call state U3 or U4 and in the Aoc-Orig-Wait1-Ack state, on receipt of a CONNECT
message including a Facility IE with a chargeRequest return result APDU,
sends no message and enters the Aoc-Orig-Active state.
AOC_Orig01_005 subclause 6.6.1.1.1
Ensure that the IUT in the call state U10 and in the Aoc-Orig-Wait1-Ack state, on receipt of a FACILITY message
including a Facility IE with a chargeRequest return result APDU,
sends no message and enters the Aoc-Orig-Active state.
ETSI

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

SIST EN 301 483-1 V1.2.2:2005
10 ETSI EN 301 483-1 V1.2.2 (2000-09)
AOC_Orig01_006 subclause 6.6.1.1.2
Ensure that the IUT in the call state U10 and in the Aoc-Orig-Idle state, in order to invok
...

Questions, Comments and Discussion

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