ETSI ETS 300 374-2 ed.1 (1996-02)

SLOVENSKI STANDARD
01-november-1997
Inteligentno omrežje (IN) - Prvi nabor zmožnosti (CS1) inteligentnega omrežja -
Jedrni uporabovni (aplikacijski) del inteligentnega omrežja (INAP) - 2. del:
Proformna specifikacija izjave o skladnosti izvedbe protokola (PICS) za funkcijo
komutacije storitev (SSF), funkcijo posebnih virov (SRF) in funkcijo krmiljenja
storitev (SCF)
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)
Ta slovenski standard je istoveten z: ETS 300 374-2 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 374-2
TELECOMMUNICATION February 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03015-2
ICS: 33.020, 33.080
IN, CS1, INAP, PICS
Key words:
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)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
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 374-2: February 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 374-2: February 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
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.14
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 .15
A.4.3 External interfaces .15
A.4.4 Application contexts.16
A.4.5 Operations .16
A.4.6 Arguments, results and errors .18
A.4.6.1 ActivateServiceFiltering.18
A.4.6.2 ActivityTest .20
A.4.6.3 ApplyCharging.21
A.4.6.4 ApplyChargingReport .22
A.4.6.5 AssistRequestInstructions.23
A.4.6.6 CallGap .24
A.4.6.7 CallInformationReport .26
A.4.6.8 CallInformationRequest.27
A.4.6.9 Cancel .28
A.4.6.10 CollectInformation .29
A.4.6.11 Connect .30
A.4.6.12 ConnectToResource .31
A.4.6.13 Continue .32
A.4.6.14 DisconnectForwardConnection .33
A.4.6.15 EstablishTemporaryConnection .33
A.4.6.16 EventNotificationCharging.34
A.4.6.17 EventReportBCSM .35
A.4.6.18 FurnishChargingInformation.36
A.4.6.19 InitialDP .37
A.4.6.20 InitiateCallAttempt .38

Page 4
ETS 300 374-2: February 1996
A.4.6.21 PlayAnnouncement. 40
A.4.6.22 PromptAndCollectUserInformation. 42
A.4.6.23 ReleaseCall . 44
A.4.6.24 RequestNotificationChargingEvent. 45
A.4.6.25 RequestReportBCSMEvent . 46
A.4.6.26 ResetTimer . 47
A.4.6.27 SendChargingInformation. 48
A.4.6.28 ServiceFilteringResponse. 49
A.4.6.29 SpecializedResourceReport . 49
A.4.7 Timers . 50
A.4.8 Range constants . 52
History. 55

Page 5
ETS 300 374-2: February 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 2 of a multi-part standard covering the Capability Set 1 (CS1) core Intelligent Network
Protocol (INAP) as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification";
Part 5: "Protocol specification for the SCF-SDF interface";
Part 6: "PICS proforma specification for the SCF-SDF interface".
NOTE: Further parts of this standard may be identified later.
Transposition dates
Date of adoption of this ETS: 1 March 1996
Date of latest announcement of this ETS (doa): 31 May 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1996
Date of withdrawal of any conflicting National Standard (dow): 30 November 1996

Page 6
ETS 300 374-2: February 1996
Blank page
Page 7
ETS 300 374-2: February 1996
1 Scope
This second part of ETS 300 374 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 [1] in compliance with the relevant requirements, and in accordance with
the relevant guidance given in ISO/IEC 9646-7 [3].
2 Normative references
This ETS incorporates by dated and 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 374-1 (1994): "Intelligent Network (IN); Intelligent Network Capability
Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1:
Protocol specification".
[2] ISO/IEC 9646-1: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[3] ISO/IEC 9646-7: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 374-1 [1];
- terms defined in ISO/IEC 9646-1 [2] and in ISO/IEC 9646-7 [3].
In particular, the following terms defined in ISO/IEC 9646-1 [2] 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.
Page 8
ETS 300 374-2: February 1996
3.2 Abbreviations
For the purposes of this ETS, 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
4 Conformance
If it claims to conform to this ETS, 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 this ETS shall be a conforming PICS proforma completed in accordance with
the instructions for completion given in clause A.1.

Page 9
ETS 300 374-2: February 1996
Annex A (normative): PICS proforma for core INAP CS1
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS 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 ETS 300 374-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 comprised of information in tabular form in accordance with
the guidelines presented in ISO/IEC 9646-7 [3].
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?".
Status column
The following notations, defined in ISO/IEC 9646-7 [3], 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.

Page 10
ETS 300 374-2: February 1996
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 ETS 300 374-1 [1], except where explicitly stated
otherwise.
NOTE: A reference indicates only the location of the most essential information about an item.
All additional requirements contained in ETS 300 374-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 [3], 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 [3], 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.

Page 11
ETS 300 374-2: February 1996
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 ETS 300 374-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;
- 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.

Page 12
ETS 300 374-2: February 1996
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:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Operating system:
........................................................................................................................................................................
A.2.4 Product supplier
Name:
........................................................................................................................................................................
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................

Page 13
ETS 300 374-2: February 1996
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.5 Client
Name:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................

Page 14
ETS 300 374-2: February 1996
A.2.6 PICS contact person
Name:
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
E-mail address:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
A.3 Identification of the protocol
This PICS proforma applies to the following standard:
ETS 300 374-1 (1994): "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core
Intelligent Network Application Protocol (INAP); Part 1: Protocol specification".
A.4 PICS proforma tables
An explicit answer shall be entered, in each of the support or supported column boxes provided, using the
notation described in subclause A.1.2.
A.4.1 Global statement of conformance
Are all mandatory capabilities implemented? (Yes/No) .
NOTE: Answering "No" to this question indicates non-conformance to the protocol
specification. Non-supported mandatory capabilities are to be identified in this PICS,
with an explanation of why the implementation is non-conforming, on pages attached
to the PICS proforma.
Page 15
ETS 300 374-2: February 1996
A.4.2 Physical entities
Table A.2: Physical entities
Item Name Reference Status Support
1 SCP 4.2 o.1
2 SSP 4.2 o.1
3 IP 4.2 o.1
o.1: Only one of these items shall be supported per completed PICS response.
Comments:
Table A.3: Capabilities
Item Name Reference Status Support
SSF-SRF-Relay-function 7.3.5 c301
2 Assisting-SSP-capability 7.3.5 (note) c302
NOTE: See ETS 300 374-1 [1], figure 25 cases c) and e).
c301: IF A.2/2 THEN o ELSE n/a -- SSP
c302: IF (A.2/2 AND A.3/1) THEN o ELSE n/a -- SSP AND SSF-SRF-Relay-function
Comments:
A.4.3 External interfaces
Table A.4: External interfaces
Item Name Reference Status Support
1 SCF-SSF (note) c401
2 SCF-SRF (note) c402
NOTE: It is assumed that the indicated external interfaces are between physical
entities.
c401: IF (A.2/1 OR A.2/2) THEN m ELSE n/a -- SCP OR SSP
c402: IF A.2/1 THEN o -- SCP
ELSE IF A.2/3 THEN m ELSE n/a -- IP
Comments:
Page 16
ETS 300 374-2: February 1996
A.4.4 Application contexts
Table A.5: Application contexts
Item Name Reference Initiator Responder
Status Support Status Support
1 Core-INAP-CS1-SSP-to-SCP-AC 6.5 c501 c502
2 Core-INAP-CS1-assist-handoff-SSP- 6.5 c503 c506
to-SCP-AC
3 Core-INAP-CS1-IP-to-SCP-AC 6.5 c505 c504
Core-INAP-CS1-SCP-to-SSP-AC 6.5 c506 c501
5 Core-INAP-CS1-SCP-to-SSP-traffic- 6.5 c506 c501
management-AC
6 Core-INAP-CS1-SCP-to-SSP-service- 6.5 c506 c501
management-AC
7 Core-INAP-CS1-SSP-to-SCP-service- 6.5 c501 c506
management-AC
c501: IF A.2/2 THEN m ELSE n/a -- SSP
c502: IF A.2/1 THEN m ELSE n/a -- SCP
c503: IF A.3/2 THEN m ELSE n/a -- Assisting-SSP-capability
c504: IF (A.2/1 AND A.4/2) THEN m ELSE n/a -- SCP AND SCF-SRF
c505: IF A.2/3 THEN m ELSE n/a -- IP
c506: IF A.2/1 THEN o ELSE n/a -- SCP
Comments:
A.4.5 Operations
Table A.6: Application Service Elements (ASEs)
Item Name Reference Invoke-Req Invoke-Ind
Status Support Status Support
1 initialDP 6.1, 6.4, 9.19 c601 c602
assistRequestInstructions 6.1, 6.4, 9.5 c603 c604
3 establishTemporaryConnection 6.1, 6.4, 9.15 c605 c606
disconnectForwardConnection 6.1, 6.4, 9.14 c607 c608
5 connectToResource 6.1, 6.4, 9.12 c607 c609
connect 6.1, 6.4, 9.11 c610 c606
7 releaseCall 6.1, 6.4, 9.23 c610 c608
eventReportBCSM 6.1, 6.4, 9.17 c606 c605
9 requestReportBCSMEvent 6.1, 6.4, 9.25 c605 c606
eventNotificationCharging 6.1, 6.4, 9.16 c622 c605
11 requestNotificationChargingEvent 6.1, 6.4, 9.24 c605 c622
collectInformation 6.1, 6.4, 9.10 c610 c606
13 continue 6.1, 6.4, 9.13 c610 c606
initiateCallAttempt 6.1, 6.4, 9.20 c611 c612
15 resetTimer 6.1, 6.4, 9.26 c613 c614
furnishChargingInformation 6.1, 6.4, 9.18 c607 c623
17 applyChargingReport 6.1, 6.4, 9.4 c623 c607
18 applyCharging 6.1, 6.4, 9.3 c607 c623
19 callGap 6.1, 6.4, 9.6 c615 c616
20 serviceFilteringResponse 6.1, 6.4, 9.28 c618 c617
21 activateServiceFiltering 6.1, 6.4, 9.1 c617 c618
22 callInformationReport 6.1, 6.4, 9.7 c606 c605
23 callInformationRequest 6.1, 6.4, 9.8 c605 c606
24 sendChargingInformation 6.1, 6.4, 9.27 c605 c622
25 specializedResourceReport 6.1, 6.4, 9.29 c619 c613
26 playAnnouncement 6.1, 6.4, 9.21 c613 c619
promptAndCollectUserInformation 6.1, 6.4, 9.22 c613 c619
28 cancel 6.1, 6.4, 9.9 c613 c614
activityTest 6.1, 6.4, 9.2 c613 c614
Page 17
ETS 300 374-2: February 1996
c601: IF A.5/1a THEN m ELSE n/a -- SSP-to-SCP-AC_Initiator
c602: IF A.5/1b THEN m ELSE n/a -- SSP-to-SCP-AC_Responder
c603: IF A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR A.5/3a THEN m ELSE n/a -- IP-to-SCP-AC_Initiator
c604: IF A.5/2b -- assist-handoff-SSP-to-SCP-AC_Responder
OR A.5/3b THEN m ELSE n/a -- IP-to-SCP-AC_Responder
c605: IF A.5/1b -- SSP-to-SCP-AC_Responder
OR A.5/4a THEN o ELSE n/a -- SCP-to-SSP-AC_Initiator
c606: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR A.5/4b THEN m ELSE n/a -- SCP-to-SSP-AC_Responder
c607: IF A.5/1b -- SSP-to-SCP-AC_Responder
OR A.5/2b -- assist-handoff-SSP-to-SCP-AC_Responder
OR A.5/4a THEN o ELSE n/a -- SCP-to-SSP-AC_Initiator
c608: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR A.5/4b THEN m ELSE n/a -- SCP-to-SSP-AC_Responder
c609: IF (A.5/1a AND A.3/1) -- SSP-to-SCP-AC_Initiator AND SSF-SRF-Relay-function
OR A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR (A.5/4b AND A.3/1) THEN m ELSE n/a -- SCP-to-SSP-AC_Responder AND SSF-SRF-Relay-function
c610: IF A.5/1b -- SSP-to-SCP-AC_Responder
OR A.5/4a THEN o.1 ELSE n/a -- SCP-to-SSP-AC_Initiator
c611: IF A.5/4a THEN m ELSE n/a -- SCP-to-SSP-AC_Initiator
c612: IF A.5/4b THEN m ELSE n/a -- SCP-to-SSP-AC_Responder
c613: IF A.5/1b -- SSP-to-SCP-AC_Responder
OR A.5/2b -- assist-handoff-SSP-to-SCP-AC_Responder
OR A.5/3b -- IP-to-SCP-AC_Responder
OR A.5/4a THEN o ELSE n/a -- SCP-to-SSP-AC_Initiator
c614: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR A.5/3a -- IP-to-SCP-AC_Initiator
OR 5/4b THEN m ELSE n/a -- SCP-to-SSP-AC_Responder
c615: IF A.5/1b -- SSP-to-SCP-AC_Responder
OR A.5/5a THEN m ELSE n/a -- SCP-to-SSP-traffic-management-AC_Initiator
c616: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR A.5/5b THEN m ELSE n/a -- SCP-to-SSP-traffic-management-AC_Responder
c617: IF A.5/6a -- SCP-to-SSP-service-management-AC_Initiator
OR A.5/7b THEN m ELSE n/a -- SSP-to-SCP-service-management-AC_Responder
c618: IF A.5/6b -- SCP-to-SSP-service-management-AC_Responder
OR A.5/7a THEN m ELSE n/a -- SSP-to-SCP-service-management-AC_Initiator
c619: IF (A.5/1a AND A.3/1) -- SSP-to-SCP-AC_Initiator AND SSF-SRF-Relay-function
OR A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR A.5/3a -- IP-to-SCP-AC_Initiator
OR (5/4b AND A.3/1) THEN m ELSE n/a -- SCP-to-SSP-AC_Responder AND SSF-SRF-Relay-function
c622: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR 5/4b THEN o ELSE n/a -- SCP-to-SSP-AC_Responder
c623: IF A.5/1a -- SSP-to-SCP-AC_Initiator
OR A.5/2a -- assist-handoff-SSP-to-SCP-AC_Initiator
OR 5/4b THEN o ELSE n/a -- SCP-to-SSP-AC_Responder
o.1: At least one of the options shall be supported.
Comments:
Page 18
ETS 300 374-2: February 1996
A.4.6 Arguments, results and errors
A.4.6.1 ActivateServiceFiltering
Table A.7: ActivateServiceFiltering invocation arguments
Item Name Reference Invoke-Request Invoke-Indication
Status Support Value Status Support Value
Allowed Supported Allowed Supported
1 filteredCallTreatment 6.3 c701 c702
2 sfBillingChargingCharacteristics 6.3 c703 c704
3 informationToSend 6.3 c705 c704
4 inbandInfo 6.3 c706 c707
messageID 6.3 c736 c709
31 31
6 elementaryMessageID 6.3 c710 0.2 -1 c711 0.2 -1
text 6.3 c710 c711
8 messageContent 6.3 c712 c713
attributes 6.3 c714 c715
10 elementaryMessageIDs 6.3 c710 c711
variableMessage 6.3 c710 c711
31 31
12 integer 6.3 c716 0.2 -1 c717 0.2 -1
number 6.3 c716 c717
14 time 6.3 c716 c717
date 6.3 c716 c717
16 price 6.3 c716 c717
numberOfRepetitions 6.3 c708 1.127 c709 1.127
15 15
18 duration 6.3 c708 0.2 -1 c709 0.2 -1
15 15
interval 6.3 c708 0.2 -1 c709 0.2 -1
20 tone 6.3 c706 c707
31 31
21 toneID 6.3 c718 0.2 -1 c719 0.2 -1
31 31
22 duration 6.3 c720 0.2 -1 c719 0.2 -1
23 displayInformation 6.3 c706 c707
24 maximumNumberOfCounters 6.3 c703 1.100 c704 1.100
25 releaseCause 6.3 c703 c704
26 filteringCharacteristics 6.3 c701 c702
27 interval 6.3 c722 -1.32 000 c723 -1.32 000
31 31
28 numberOfCalls 6.3 c722 0.2 -1 c723 0.2 -1
29 filteringTimeOut 6.3 c701 c702
duration 6.3 c724 -2.86 400 c725 -2.86 400
31 stopTime 6.3 c724 c725
(continued)
Table A.7 (concluded): ActivateServiceFiltering invocation arguments
Item Name Reference Invoke-Request Invoke-Indication
Status Support Value Status Support Value
Allowed Supported Allowed Supported
32 filteringCriteria 6.3 c701 c702
31 31
33 serviceKey 6.3 c726 0.2 -1 c727 0.2 -1
34 addressAndService 6.3 c726 c727
35 calledAddressValue 6.3 c728 c729
31 31
36 serviceKey 6.3 c728 0.2 -1 c729 0.2 -1
37 callingAddressValue 6.3 c730 c729
38 locationNumber 6.3 c730 c729
39 startTime 6.3 c731 c702
40 extensions 6.3 c731 c732
type 6.3 c733 c734
42 criticality 6.3 c735 0, 1 c734 0, 1
value 6.3 c733 c734
c701: IF A.6/21a THEN m ELSE n/a -- ActivateServiceFiltering-Invoker c719: IF A.7/20b THEN m ELSE n/a
c702: IF A.6/21b THEN m ELSE n/a -- ActivateServiceFiltering-Responder c720: IF A.7/20a THEN o ELSE n/a
c703: IF A.7/1a THEN m ELSE n/a c722: IF A.7/26a THEN o.4 ELSE n/a
c704: IF A.7/1b THEN m ELSE n/a c723: IF A.7/26b THEN m ELSE n/a
c705: IF A.7/1a THEN o ELSE n/a c724: IF A.7/29a THEN o.5 ELSE n/a
c706: IF A.7/3a THEN o.1 ELSE n/a c725: IF A.7/29b THEN m ELSE n/a
c707: IF A.7/3b THEN o.1 ELSE n/a c726: IF A.7/32a THEN o.6 ELSE n/a
c708: IF A.7/4a THEN o ELSE n/a c727: IF A.7/32b THEN o.6 ELSE n/a
c709: IF A.7/4b THEN m ELSE n/a c728: IF A.7/34a THEN m ELSE n/a
c710: IF A.7/5a THEN o.2 ELSE n/a c729: IF A.7/34b THEN m ELSE n/a
c711: IF A.7/5b THEN o.2 ELSE n/a c730: IF A.7/34a THEN o ELSE n/a
c712: IF A.7/7a THEN m ELSE n/a c731: IF A.6/21a THEN o ELSE n/a -- ActivateServiceFiltering-Invoker
c713: IF A.7/7b THEN m ELSE n/a c732: IF A.6/21b THEN o ELSE n/a -- ActivateServiceFiltering-Responder
c714: IF A.7/7a THEN o ELSE n/a c733: IF A.7/40a THEN m ELSE n/a
c715: IF A.7/7b THEN o ELSE n/a c734: IF A.7/40b THEN m ELSE n/a
c716: IF A.7/11a- THEN o.3 ELSE n/a c735: IF A.7/40a THEN o ELSE n/a
c717: IF A.7/11b THEN o.3 ELSE n/a c736: IF A.7/4a THEN m ELSE n/a
c718: IF A.7/20a THEN m ELSE n/a
o.1: At least one of the options shall be supported.
o.2: At least one of the options shall be supported; this deviates from the general rule as stated in A.1.3.
o.3: At least one of the options shall be supported.
o.4: At least one of the options shall be supported.
o.5: At least one of the options shall be supported.
o.6: At least one of the options shall be supported; this deviates from the general rule as stated in A.1.3.
Page 19
ETS 300 374-2: February 1996
Page 20
ETS 300 374-2: February 1996
Comments:
Table A.8: ActivateServiceFiltering errors
Item Name Reference Status Support
1 missingParameter 6.2 c801
2 parameterOutOfRange 6.2 c801
3 systemFailure 6.2 c801
4 taskRefused 6.2 c801
5 unexpectedComponentSequence 6.2 c801
6 unexpectedParameter 6.2 c801
c801: IF A.6/21a THEN m -- ActivateServiceFiltering-Invoker
ELSE IF A.6/21b THEN o ELSE n/a -- ActivateServiceFiltering-Responder
Comments:
A.4.6.2 ActivityTest
For the operation ActivityTest there are no invocation arguments, no result arguments and no errors.

A.4.6.3 ApplyCharging
Table A.9: ApplyCharging invocation arguments
Item Name Reference Invoke-Request Invoke-Indication
Status Support Value Status Support Value
Allowed Supported Allowed Supported
6.3 c901 c902
1 aChBillingCharacteristics
2 sendCalculationToSCPInvocation 6.3 c901 True c902 True
6.3 c903 c902
3 partyToCharge
4 sendingSideID 6.3 c904 '01'H, '02'H c905 '01'H, '02'H
6.3 c903 c906
5 extensions
6 type 6.3 c907 c908
7 criticality 6.3 c909 0, 1 c908 0, 1
8 value 6.3 c907 c908
c901: IF A.6/18a THEN m ELSE n/a -- ApplyCharging-Invoker c906: IF A.6/18b THEN o ELSE n/a -- ApplyCharging-Responder
c902: IF A.6/18b THEN m ELSE n/a -- ApplyCharging-Responder c907: IF A.9/5a THEN m ELSE n/a
c903: IF A.6/18a THEN o ELSE n/a -- ApplyCharging-Invoker c908: IF A.9/5b THEN m ELSE n/a
c904: IF A.9/3a THEN m ELSE n/a c909: IF A.9/5a THEN o ELSE n/a
c905: IF A.9/3b THEN m ELSE n/a
Comments:
Table A.10: ApplyCharging errors
Item Name Reference Status Support
1 missingParameter 6.2 c1001
unexpectedComponentSequence 6.2 c1001
3 unexpectedParameter 6.2 c1001
unexpectedDataValue 6.2 c1001
5 parameterOutOfRange 6.2 c1001
systemFailure 6.2 c1001
7 taskRefused 6.2 c1001
c1001:IF A.6/18b THEN o -- ApplyCharging-Responder
ELSE IF A.6/18a THEN m ELSE n/a -- ApplyCharging-Invoker
Page 21
ETS 300 374-2: February 1996
Page 22
ETS 300 374-2: February 1996
Comments:
A.4.6.4 ApplyChargingReport
Table A.11: ApplyChargingReport invocation arguments
Item Name Reference Invoke-Request Invoke-Indication
Status Support Value Status Support Value
Allowed Supported Allowed Supported
6.3 c1101 c1102
1 callResult
c1101:IF A.6/17a THEN m ELSE n/a -- ApplyChargingReport-Invoker
c1102:IF A.6/17b THEN m ELSE n/a -- ApplyChargingReport-Responder
Comments:
Table A.12: ApplyChargingReport errors
Item Name Reference Status Support
missingParameter 6.2 c1201
2 unexpectedComponentSequence 6.2 c1201
unexpectedParameter 6.2 c1201
4 unexpectedDataValue 6.2 c1201
parameterOutOfRange 6.2 c1201
6 systemFailure 6.2 c1201
taskRefused 6.2 c1201
c1201:IF A.6/17b THEN o -- ApplyChargingReport-Responder
ELSE IF A.6/17a THEN m ELSE n/a -- ApplyChargingReport-Invoker
Comments:
A.4.6.5 AssistRequestInstructions
Table A.13: AssistRequestInstructions invocation arguments
Item Name Reference Invoke-Request Invoke-Indication
Status Support Value Status Support Value
Allowed Supported Allowed Supported
6.3 c1301 c1303
1 correlationID
2 iPAvailable 6.3 c1302 c1304
6.3 c1302 c1304
3 iPSSPCapabilities
4 extensions 6.3 c1302 c1304
type 6.3 c1305 c1306
6 criticality 6.3 c1307 0, 1 c1306 0, 1
7 value 6.3 c1305 c1306
c1301:IF A.6/2a THEN m ELSE n/a -- AssistRequestInstructions-Invoker c1305:IF A.13/4a THEN m ELSE n/a
c1302:IF A.6/2a THEN o ELSE n/a -- AssistRequestInstructions-Invoker c1306:IF A.13/4b THEN m ELSE n/a
c1303:IF A.6/2b THEN m ELSE n/a -- AssistRequestInstructions-Responder c1307:IF A.13/4a THEN o ELSE n/a
c1304:IF A.6/2b THEN o ELSE n/a -- AssistRequestInstructions-Responder
Comments:
Table A.14: AssistRequestInstructions errors
Item Name Reference Status Support
1 missingCustomerRecord 6.2 c1401
missingParameter 6.2 c1401
3 taskRefused 6.2 c1401
4 unexpectedComponentSequence 6.2 c1401
5 unexpectedDataValue 6.2 c1401
6 unexpectedParameter 6.2 c1401
c1401:IF A.6/2b THEN o -- AssistRequestInstructions-Responder
ELSE
...