ETSI EN 301 152-2 V1.2.2 (1998-09)

SLOVENSKI STANDARD
SIST EN 301 152-2:2000
01-januar-2000
Inteligentno omrežje (IN) - Razširitev prvega nabora zmožnosti inteligentnega
omrežja (CS1) - Aplikacijski del inteligentnega omrežja (INAP) - Uporabniške
aplikacije za izboljšano logiko mobilnega omrežja (CAMEL) - 2. del: Proforma
specifikacije izjave o skladnosti izvedbe protokola
Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent
Network Application Protocol (INAP); Customised Applications for Mobile network
Enhanced Logic (CAMEL); Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification
Ta slovenski standard je istoveten z: EN 301 152-2 Version 1.2.2
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
SIST EN 301 152-2:2000 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 301 152-2:2000

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

SIST EN 301 152-2:2000
EN 301 152-2 V1.2.2 (1998-09)
European Standard (Telecommunications series)
Intelligent Network (IN);
IN Capability Set 1 (CS1) extension;
Intelligent Network Application Protocol (INAP);
Customized Applications for
Mobile network EnhancedLogic (CAMEL);
Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification

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

SIST EN 301 152-2:2000
2 EN 301 152-2 V1.2.2 (1998-09)
Reference
DEN/SPS-03052-2 (ao0i0ipc.PDF)
Keywords
IN, INAP, ISDN, mobile, PICS
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16
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
Internet
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
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 1998.
All rights reserved.
ETSI

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

SIST EN 301 152-2:2000
3 EN 301 152-2 V1.2.2 (1998-09)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
2.1 Normative references. 6
2.2 Informative references . 7
3 Definitions, symbols and abbreviations.7
3.1 Definitions . 7
3.2 Abbreviations. 7
4 Conformance.8
Annex A (normative): PICS proforma for core INAP CS1 .9
A.1 Guidance for completing the PICS proforma.9
A.1.1 Purpose and structure. 9
A.1.2 Symbols, abbreviations and terms. 9
A.1.3 Instructions for completing the PICS proforma . 11
A.2 Identification of the implementation.12
A.2.1 Date of the statement . 12
A.2.2 Implementation Under Test (IUT) identification . 12
A.2.3 System Under Test (SUT) identification. 12
A.2.4 Product supplier. 12
A.2.5 Client . 13
A.2.6 PICS contact person. 13
A.3 Identification of the protocol .14
A.4 PICS proforma tables .14
A.4.1 Global statement of conformance . 14
A.4.2 Physical entities . 14
A.4.3 External interfaces . 15
A.4.4 Application contexts . 15
A.4.5 Operations. 16
A.4.6 Arguments, results and errors . 16
A.4.6.1 ActivateServiceFiltering. 16
A.4.6.2 ActivityTest. 16
A.4.6.3 ApplyCharging . 16
A.4.6.4 ApplyChargingReport . 17
A.4.6.5 AssistRequestInstructions. 17
A.4.6.6 CallGap . 17
A.4.6.7 CallInformationReport . 17
A.4.6.8 CallInformationRequest . 17
A.4.6.9 Cancel. 17
A.4.6.10 CollectInformation . 17
A.4.6.11 Connect . 18
A.4.6.12 ConnectToResource . 19
A.4.6.13 Continue . 19
A.4.6.14 DisconnectForwardConnection . 19
A.4.6.15 EstablishTemporaryConnection . 19
A.4.6.16 EventNotificationCharging. 19
A.4.6.17 EventReportBCSM . 20
A.4.6.18 FurnishChargingInformation . 20
A.4.6.19 InitialDP. 21
A.4.6.20 InitiateCallAttempt. 22
ETSI

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

SIST EN 301 152-2:2000
4 EN 301 152-2 V1.2.2 (1998-09)
A.4.6.21 PlayAnnouncement. 22
A.4.6.22 PromptAndCollectUserInformation . 22
A.4.6.23 ReleaseCall. 22
A.4.6.24 RequestNotificationChargingEvent. 22
A.4.6.25 RequestReportBCSMEvent. 23
A.4.6.26 ResetTimer . 24
A.4.6.27 SendChargingInformation . 24
A.4.6.28 ServiceFilteringResponse. 24
A.4.6.29 SpecializedResourceReport. 24
A.4.7 Timers. 25
A.4.8 Range constants . 27
A.4.9 Additional tables. 28
A.4.9.1 Error parameters. 28
A.4.9.2 Detection points . 28
A.4.9.3 SCCP Addressing. 29
History.30
ETSI

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

SIST EN 301 152-2:2000
5 EN 301 152-2 V1.2.2 (1998-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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge 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 Signalling
Protocols and Switching (SPS).
The present document is part 2 of a multi-part standard covering the IN Capability Set 1 (CS1) extension; Intelligent
Network Application Protocol (INAP); Customized Applications for Mobile network Enhanced Logic (CAMEL) as
described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification".
NOTE: Further parts of the present document may be identified later.
National transposition dates
Date of adoption of this EN: 18 September 1998
Date of latest announcement of this EN (doa): 31 December 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 1999
Date of withdrawal of any conflicting National Standard (dow): 30 June 1999
ETSI

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

SIST EN 301 152-2:2000
6 EN 301 152-2 V1.2.2 (1998-09)
1 Scope
This second part of EN 301 152 provides the Implementation Conformance Statement (ICS) proforma for the core
Intelligent Network Application Protocol (INAP) of Intelligent Network (IN) Capability Set 1 (CS1) defined in
ETS 300 374-1 [2] extended by the Intelligent Network Application Protocol (INAP) of Intelligent Network (IN)
Capability Set 1 (CS1) extension defined in EN 301 152-1 [1] in compliance with the relevant requirements, and in
accordance with the relevant guidance given in ISO/IEC 9646-7 [4].
ETS 300 374-2 [8] was taken as an editorial basis for the present document. Enhancements and modifications in respect
to EN 301 152-1 [1] are covered by appropriate updates of existing tables or by new tables. For the CAMEL capability
only a restricted subset of the protocol aspects of ETS 300 374-1 [2] is necessary. These restrictions are covered in the
present document too.
2 References
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case 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.
2.1 Normative references
[1] EN 301 152-1 (V1.2): "Intelligent Network (IN); IN Capability Set 1 (CS1) extension; Intelligent
Network Application Protocol (INAP); Customized Applications for Mobile network Enhanced
Logic (CAMEL); Part 1: Protocol specification".
[2] ETS 300 374-1 (1994): "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1);
Core Intelligent Network Application Protocol (INAP); Part 1: Protocol 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-7 (1995): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
[5] TS 101 044 (V5.5): "Digital cellular telecommunications system (Phase 2+); Customized
Applications for Mobile network Enhanced Logic (CAMEL) - Stage 2 (GSM 03.78 version
5.5.0)".
[6] TS 101 046 (V5.5): "Digital cellular telecommunications system (Phase 2+); Customized
Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP)
specification (GSM 09.78 version 5.5.0)".
[7] GTS GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing
and Identification GSM 03.03".
ETSI

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

SIST EN 301 152-2:2000
7 EN 301 152-2 V1.2.2 (1998-09)
2.2 Informative references
[8] ETS 300 374-2 (1996): "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1);
Core Intelligent Network Application Protocol (INAP); Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification for Service Switching Function (SSF),
Specialized Resource Function (SRF) and Service Control Function (SCF)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
- terms defined in EN 301 152-1 [1];
- terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-7 [4].
In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:
Implementation Conformance Statement (ICS): a statement made by the supplier of an implementation or system
claimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take several
forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.
ICS proforma: a document, in the form of a questionnaire, which when completed for an implementation or system
becomes an ICS.
Protocol ICS (PICS): an ICS for an implementation or system claimed to conform to a given protocol specification.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Application Context
ASE Application Service Element
BCSM Basic Call State Model
CS1 Capability Set 1
ICS Implementation Conformance Statement
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Intelligent Peripheral
IUT Implementation Under Test
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCF Service Control Function
SCP Service Control Point
SCS System Conformance Statement
SRF Specialized Resource Function
SSF Service Switching Function
SSP Service Switching Point
SUT System Under Test
Within the present document the terms gsmSSF and SSF and the terms gsmSCF and SCF respectively are used
synonymously.
ETSI

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

SIST EN 301 152-2:2000
8 EN 301 152-2 V1.2.2 (1998-09)
4 Conformance
If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be
technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and
ordering of the proforma items.
A PICS which conforms to the present document shall be a conforming PICS proforma completed in accordance with
the instructions for completion given in annex A, clause A.1.
ETSI

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

SIST EN 301 152-2:2000
9 EN 301 152-2 V1.2.2 (1998-09)
Annex A (normative):
PICS proforma for core INAP CS1
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users
of the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intended
purposes and may further publish the completed PICS.
A.1 Guidance for completing the PICS proforma
A.1.1 Purpose and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in EN 301 152-1 [1] may provide information about the implementation in a standardized manner.
The PICS proforma is subdivided into clauses for the following categories of information:
- instructions for completing the ICS proforma;
- identification of the implementation;
- identification of the protocol;
- PICS proforma tables;
- global statement of conformance;
- physical entities;
- external interfaces;
- application contexts;
- operations;
- arguments, results and errors;
- timers;
- range constants.
A.1.2 Symbols, abbreviations and terms
The PICS proforma contained in this annex is comprized of information in tabular form in accordance with the
guidelines presented in ISO/IEC 9646-7 [4].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is supported by the implementation?".
ETSI

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

SIST EN 301 152-2:2000
10 EN 301 152-2 V1.2.2 (1998-09)
Status column
The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, the capability cannot be used.
x prohibited (excluded) - there is a requirement not to use this capability in the given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which
identifies an unique group of related optional items and the logic of their selection which is defined
immediately following the table.
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying an unique conditional status
expression which is defined immediately following the table. For nested conditional expressions,
the syntax "IF . THEN (IF . THEN . ELSE.) ELSE ." is used to avoid ambiguities.
Reference column
Entries in the reference column refer to subclauses of EN 301 152-1 [1], except where explicitly stated otherwise. Since
EN 301 152-1 [1] is a delta document to ETS 300 374-1 [2], clauses which are missing in EN 301 152-1 [1] can be
found in ETS 300 374-1 [2].
NOTE: A reference indicates only the location of the most essential information about an item. All additional
requirements contained in EN 301 152-1 [1] have also to be taken into account when making a statement
about the conformance of that particular item.
Support column
The support column shall be filled in by the supplier of the implementation. The following common notations, defined in
ISO/IEC 9646-7 [4], are used for the support column:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
NOTE: As stated in ISO/IEC 9646-7 [4], support for a Protocol Data Unit (PDU) requires the ability to parse all
valid parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is
non-conformant. Support for a parameter on a PDU means that the semantics of that parameter are
supported.
If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able
to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall
enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in the
cell provided at the bottom of the table. It uses predicates defined in the System Conformance Statement (SCS), each of
which refers to a single profile and which takes the value TRUE if and only if that profile is to be used.
EXAMPLE: ?3: IF prof1 THEN Y ELSE N.
It is further possible to provide comments to an answer at the bottom of each table.
Values allowed column
The values allowed column contains the values or the ranges of values allowed.
Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the values or the
ranges of values supported by the implementation shall be indicated.
ETSI

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

SIST EN 301 152-2:2000
11 EN 301 152-2 V1.2.2 (1998-09)
References to items
For each possible item answer (answer in the support column) within the PICS proforma exists a unique reference, used,
for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/",
followed by the item number in the table. If there is more than one support column in a table, the columns shall be
discriminated by letters (a, b, etc.), respectively.
EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 6
of annex A.
A.1.3 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided using the notation
described in subclause A.1.2.
Optional items in EN 301 152-1 [1] are dealt with as follows:
- mandatory protocol items need to be supported by both operation invokers and responders;
- optional protocol items are optional for operation invokers, but mandatory for operation responders; they may be
mandatory also for the operation invokers if required by the CAMEL capability;
- network specific options are optional for both operation invokers and responders.
Table A.1 gives an overview of this rule tabular form.
Table A.1
Protocol item Invoke request Invoke indication
Mandatory m m
Optional o m
Network option o o
As a general rule, the ASN.1 "CHOICE" construct is indicated in the parameter tables:
- as an option (o.x) in the "Invoke request" column;
- as mandatory in the "Invoke indication" column.
When a (ASN.1) parameter which contains a "SIZE" field is not explicitly constrained in a table, then the complete size
field has to be supported.
ETSI

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

SIST EN 301 152-2:2000
12 EN 301 152-2 V1.2.2 (1998-09)
A.2 Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test
(SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration
options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
A.2.1 Date of the statement
.........................................................................................................................................................................................
A.2.2 Implementation Under Test (IUT) identification
IUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
IUT version:
.........................................................................................................................................................................................
A.2.3 System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
..............................
...