SIST EN 301 931-3 V1.1.2:2005

• Abstract:

  Core INAP CS3 shall comprise the CAMEL phase 1, 2, and 3 (release 1999); ensuring a unique IN Network infrastructure for fixed network and mobile applications suitable for implementation in Europe. This shall contain the CAMEL Application Part (CAP) for specification for Phase 3 to support GSM The first release is has the following main topics: Multiple Point of Control, Enhanced CPH capabilities; Enhanced Charging; Number Portability, IN Support for H.323 and SIP/SDP architecture SPAR Phase 1 requirements. CAMEL Phase 3 Release 1999.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.40 - Data communication networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI EN 301 931-3 V1.1.2 (2001-09) - Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 3: SCF-SRF interface

SIST EN 301 931-3 V1.1.2:2005 is the Slovenian adoption of ETSI EN 301 931-3 V1.1.2, published by SIST. It specifies the Intelligent Network Application Protocol (INAP) for Intelligent Network (IN) Capability Set 3 (CS3), focused on the Service Control Function-Service Resource Function (SCF-SRF) interface.

This part is for engineers and operators who need to implement, test, or integrate SCF and SRF behavior in fixed or mobile network services. It defines the interface procedures, state models, parameters, errors, and ASN.1 definitions used for user interaction, script control, and specialized resource control.

What does SIST EN 301 931-3 V1.1.2:2005 specify?

SIST EN 301 931-3 V1.1.2:2005 specifies the SCF-SRF interface for IN CS3 and the SCF/SRF functional aspects that matter to that interface. Clause 4 frames the SCF-SRF relationship, while clause 13 sets out the TCAP services assumed by the protocol.

The document is part 3 of a multi-part deliverable for IN CS3. It relies on EN 301 931-1 for referenced documents, definitions, and abbreviations, and it points to EN 301 931-2 for other SCF-SRF scenarios outside this part.

Clause	What it covers
4	Relationships between SRF-CCF and SCF-SRF
5	SCF FE Model
6	SRF FE Model
7	SRF application entity procedures
8	SCF Application Entity procedure
9	Detailed operation procedure
10	Parameters
11	Error procedures
12	ASN.1 Definition
13	Services assumed from TCAP

Clause 4 also makes a practical boundary clear: the SRF-CCF relationship is not defined here, and no call model is specified for it. That matters when a bearer connection is released or managed outside the SCF-SRF exchange.

What are the key requirements of SIST EN 301 931-3 V1.1.2:2005?

SCF and SRF roles are separated, but tightly coordinated

Clause 5 states that the SCF executes service logic and interacts with the SSF to establish end user interaction. The SRF manages specialized resources for that interaction under SCF control.

In practice, this means service logic stays in the SCF, while prompts, recording, announcement playback, digit collection, and similar functions are handled by the SRF. Implementers need to keep control decisions and resource execution distinct.

The SRF is modeled as control, function, and data parts

Clause 6 presents the SRF as a conceptual model with a Functional Entity Access Manager (FEAM), an SRF Resource Manager, and resources. The SRF is divided into a Resource Control Part (RCP), a Resource Function Part (RFP), and a Data Part (DP).

This matters because RCP handles service logic and admission decisions, RFP holds the actual resource functions, and DP contains stored material such as recorded voice, sound, image, and text. A real implementation can be organized differently, but it still has to support these roles.

SRF and SCF state handling is explicit

Clause 7 defines the SRF management finite state model (SRME FSM) and the SRF call state model (SRSM). The SRSM has the states Idle, Connected, and User interaction.

The SRSM processes received operations in order. If a Cancel is received during user interaction for PlayAnnouncement, PromptAndCollectUserInformation, or PromptAndReceiveMessage, it is executed immediately; other operations are queued. That affects how a stack must serialize concurrent requests.

User interaction is restricted by call segment and leg structure

Clause 7 also limits what can run in a Call Segment Association. Only one User Interaction is allowed per Call Segment, and some operations are only accepted when one joined leg exists.

In practice, PromptAndCollectUserInformation, PromptAndReceiveMessage, ScriptRun, ScriptInformation, and ScriptClose require a single joined leg. If several legs are connected in a Call Segment, only PlayAnnouncement is allowed in that configuration. This avoids sending interactive prompts to an ambiguous target.

The document defines the main operation set and how to use it

Clause 9 gives the procedures for ActivityTest, AssistRequestInstructions, Cancel, ConnectToResource, DisconnectForwardConnection, DisconnectForwardConnectionWithArgument, EstablishTemporaryConnection, PlayAnnouncement, PromptAndCollectUserInformation, PromptAndReceiveMessage, ReportUTSI, RequestReportUTSI, SendSTUI, ScriptClose, ScriptEvent, ScriptInformation, ScriptRun, SpecializedResourceReport, and SRFCallGap.

These are the building blocks for direct control, assisted control, script execution, reporting, and call gapping. For implementers, the important point is not just the operation names, but that each one has defined invoking and responding behavior plus normal and error procedures.

Parameters define the exact behavior of collection, recording, and announcements

Clause 10 defines parameters such as CollectedDigits, InformationToRecord, InformationToSend, SRFgapCriteria, CorrelationID, LegID, MailBoxID, ReceivedStatus, and UIScriptId. These parameters control what the SRF collects, records, plays, reports, and routes.

In practice, CollectedDigits sets digit limits, reply digits, timers, and error treatment. InformationToRecord controls recording time, stop and cancel digits, replay handling, and message identity. InformationToSend covers inband announcements, tone, display information, and SDSSinformation, so the same protocol can support voice, text, and display-oriented interaction.

Errors are part of the interface contract

Clause 11 defines operation-related errors such as Cancelled, ImproperCallerResponse, MissingParameter, ParameterOutOfRange, SystemFailure, TaskRefused, UnavailableResource, UnexpectedComponentSequence, UnexpectedDataValue, UnexpectedParameter, UnknownLegID, and UnknownSubscriber.

These errors are not just fault codes. They tell the receiving side how to recover, whether to retry, whether to change service logic, and whether the current state stays the same. That is important for interoperability testing and for stable service behavior under abnormal conditions.

ASN.1 and TCAP handling are part of the protocol definition

Clause 12 provides the ASN.1 types, operation definitions, packages, contracts, and application contexts used on the interface. Clause 13 describes the dialogue and component services assumed from TCAP.

For implementers, this is the encoding and transaction layer of the standard. It is the part used to build actual protocol stacks, encode arguments and results, and map INAP operations onto TCAP dialogues and components.

What terms does SIST EN 301 931-3 V1.1.2:2005 define?

• Service Control Function (SCF) - The network function that executes service logic and sends instructions to the SRF.
• Specialized Resource Function (SRF) - The function that provides and controls specialized resources used for end user interaction.
• Service Switching and Call Control Function (SSF) - The function that controls switching and call control for the bearer connection and supports SCF-SRF routing through the network.
• Resource Control Part (RCP) - The SRF block that contains service logic and decides whether a requested specialized resource function is admitted or rejected.
• Resource Function Part (RFP) - The SRF block that contains the resource-function pairs used during service execution.
• Data Part (DP) - The SRF block that contains the database manager and stored data such as voice, sound, image, and text.
• SRSM - The SRF call state model that governs Idle, Connected, and User interaction behavior.
• SRME FSM - The SRF management finite state model that handles SRF management operations such as sRFCallGap.

Who uses SIST EN 301 931-3 V1.1.2:2005?

SIST EN 301 931-3 V1.1.2:2005 is used by INAP and CAMEL implementers, network architects, switch and intelligent peripheral engineers, and operators running fixed or mobile service platforms. It is relevant to systems that must coordinate SCF, SRF, and SSF behavior for services such as user interaction, call gapping, recording, and announcement playback.

It also matters to test labs and quality teams validating interoperability, error handling, ASN.1 encoding, and TCAP dialogue behavior. The scope ties the standard to CS3 services used in Europe and to CAMEL phase 1, 2, and 3, so it is a practical reference for service platforms that interwork with GSM and with H.323 or SIP/SDP-based architectures.

Which standards are used with SIST EN 301 931-3 V1.1.2:2005?

Standard	What it contributes
EN 301 931-1	Supplies the referenced documents, definitions, and abbreviations used throughout the series.
EN 301 931-2	Covers other SCF-SRF scenarios and SCF FSM material that this part does not develop in detail.
TCAP	Provides the dialogue and component services assumed for message handling between network entities.

What does the SIST EN 301 931-3 V1.1.2:2005 document contain?

The document contains a conceptual SRF model, SRF and SCF state diagrams, and example connection, interaction, and disconnection procedures. It includes detailed operation clauses for each SCF-SRF message, with normal and error handling for both invoking and responding entities.

It also contains tables and definitions for errors, parameters, and operation-specific timers. The ASN.1 section defines the data types, operations, packages, contracts, and application contexts needed to encode the protocol.

Several figures illustrate the physical scenarios, including relay, direct, assist, and hand-off arrangements, and later examples map complete user interaction sequences to protocol flows. That makes the standard useful not only for implementation, but also for protocol design reviews, interoperability tests, and troubleshooting of message exchanges.

SLOVENSKI STANDARD
01-januar-2005
Inteligentno omrežje (IN) – Tretji nabor zmožnosti inteligentnega omrežja (CS3) –
Aplikacijski protokol inteligentnega omrežja (INAP) – Specifikacija protokola – 3.
del: Vmesnik SCF-SRF
Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network
Application Protocol (INAP); Protocol specification; Part 3: SCF-SRF interface
Ta slovenski standard je istoveten z: EN 301 931-3 Version 1.1.2
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Intelligent Network (IN);
Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP);
Protocol specification;
Part 3: SCF-SRF interface
2 ETSI EN 301 931-3 V1.1.2 (2001-09)
Reference
DEN/SPAN-03063/1-3
Keywords
CS3, CTM, IN, INAP, protocol, UPT
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
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:
[e-mail]
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 2001.
All rights reserved.
ETSI
3 ETSI EN 301 931-3 V1.1.2 (2001-09)
Contents
Intellectual Property Rights .9
Foreword.9
1 Scope.10
2 References.10
3 Definitions and abbreviations.10
3.1 Definitions . 10
3.2 Abbreviations. 10
4 Relationships .10
4.1 SRF-CCF relationship . 10
4.2 SCF-SRF relationship. 10
5 SCF FE Model.10
6 SRF FE Model.11
6.1 Resource Control Part (RCP). 12
6.1.1 SRF Resource Manager. 12
6.1.2 Transaction Module . 12
6.1.3 User Interaction-scripts (UI-Script) . 12
6.1.4 Resource Logic Library. 12
6.1.5 Resource Logic Instances. 12
6.2 Resource Function Part (RFP). 12
6.3 Data Part (DP). 12
7 SRF application entity procedures.13
7.1 The SRF management finite state model (SRME FSM). 13
7.2 The SRF call State Model: SRSM. 14
7.2.1 State 1: "Idle". 15
7.2.2 State 2: "Connected" . 16
7.2.3 State 3: "User interaction". 17
7.3 Example SRF control procedures. 18
7.3.1 SRF connect procedures. 19
7.3.1.1 SRF connect physical procedures. 19
7.3.1.1.1 SSF relay . 22
7.3.1.1.2 Direct Path SCP to IP . 22
7.3.1.1.3 Assist with relay. 23
7.3.1.1.4 Assist without relay. 23
7.3.1.1.5 Hand-off . 24
7.3.2 SRF end user interaction procedures. 24
7.3.2.1 (PA/P&C/P&R). 26
7.3.2.2 User Interaction Script. 27
7.3.3 SRF disconnection procedures. 27
7.3.3.1 SRF initiated disconnect . 29
7.3.3.2 SCF Initiated Disconnect . 29
7.3.4 Call-Unrelated Interaction . 30
7.3.5 Examples Illustrating Complete User Interaction Sequences . 31
7.3.5.1 SSP with integrated SRF. 31
7.3.5.2 SSP relays messages between SCP and IP. 32
7.3.5.3 Direct SCP-IP information transfer . 34
7.3.5.4 SSP assist(relay SSP). 35
7.3.5.5 Message sequences for service assist. 36
7.3.5.6 Message sequences for hand-off. 37
7.3.6 Example illustrating the use of SDSS . 38
8 SCF Application Entity procedure.39
8.1 The SCF Management state model for SRF. 39
ETSI
4 ETSI EN 301 931-3 V1.1.2 (2001-09)
8.1.1 The Activity Test FSM. 40
8.1.1.1 State M1: "Activity test idle" . 40
8.1.1.2 State M2: "Waiting for activity test response" .40
8.1.2 The Call GAP FSM. 40
8.1.2.1 State M1: "idle". 41
8.1.2.2 State M3: "Call GAP Active". 41
8.2 The SCF Call State Model (SCSM): FSM for specialized resource. 41
8.2.1 State R1: "SRF Control Idle". 42
8.2.2 State R2: "Controlling SRF". 42
9 Detailed Operation procedure .44
9.1 ActivityTest procedure . 44
9.1.1 General description . 44
9.1.2 Parameters. 44
9.1.2.1 Argument Parameters . 44
9.1.3 Invoking entity (SCF) . 44
9.1.3.1 Normal procedure. 44
9.1.3.2 Error handling . 44
9.1.4 Responding entity (SRF) . 44
9.1.4.1 Normal procedure. 44
9.1.4.2 Error handling . 44
9.2 AssistRequestInstructions procedure. 45
9.2.1 General description . 45
9.2.2 Parameters. 45
9.2.2.1 Argument Parameters . 45
9.2.3 Invoking entity (SRF) . 45
9.2.3.1 Normal procedure. 45
9.2.3.2 Error handling . 45
9.2.4 Responding entity (SCF). 45
9.2.4.1 Normal procedure. 45
9.2.4.2 Error handling . 46
9.3 Cancel procedure. 46
9.3.1 General description . 46
9.3.2 Parameters. 46
9.3.2.1 Argument Parameters . 46
9.3.3 Invoking entity (SCF) . 47
9.3.3.1 Normal procedure. 47
9.3.3.2 Error handling . 47
9.3.4 Responding entity (SRF) . 47
9.3.4.1 Normal procedure. 47
9.3.4.2 Error handling . 47
9.3.5 Responding entity (SSF) . 47
9.4 ConnectToResource procedure . 47
9.5 DisconnectForwardConnection procedure. 47
9.6 DisconnectForwardConnectionWithArgument procedure. 48
9.7 EstablishTemporaryConnection procedure. 48
9.8 PlayAnnouncement procedure . 48
9.8.1 General description . 48
9.8.2 Parameters. 48
9.8.2.1 Argument Parameters . 48
9.8.3 Invoking entity (SCF) . 49
9.8.3.1 Normal procedure. 49
9.8.3.2 Error handling . 49
9.8.4 Responding entity (SRF) . 49
9.8.4.1 Normal procedure. 49
9.8.4.2 Error handling . 50
9.9 PromptAndCollectUserInformation procedure . 50
9.9.1 General description . 50
9.9.2 Parameters. 50
9.9.2.1 Argument Parameters . 50
9.9.2.2 Result Parameters. 51
9.9.3 Invoking entity (SCF) . 51
ETSI
5 ETSI EN 301 931-3 V1.1.2 (2001-09)
9.9.3.1 Normal procedure. 51
9.9.3.2 Error handling . 51
9.9.4 Responding entity (SRF) . 52
9.9.4.1 Normal procedure. 52
9.9.4.2 Error handling . 53
9.10 PromptAndReceiveMessage procedure. 53
9.10.1 General description . 53
9.10.2 Parameters. 53
9.10.2.1 Argument Parameters . 53
9.10.2.2 Result Parameters. 54
9.10.3 Invoking entity (SCF) . 54
9.10.3.1 Normal procedure. 54
9.10.3.2 Error handling . 54
9.10.4 Responding entity (SRF) . 55
9.10.4.1 Normal procedure. 55
9.10.4.2 Error handling . 55
9.11 ReportUTSI procedure . 55
9.12 RequestReportUTSI procedure . 55
9.13 SendSTUI procedure . 56
9.14 ScriptClose procedure. 56
9.14.1 General description . 56
9.14.2 Parameters. 56
9.14.2.1 Argument Parameters . 56
9.14.3 Invoking entity (SCF) . 56
9.14.3.1 Normal procedure. 56
9.14.3.2 Error handling . 56
9.14.4 Responding entity (SRF) . 57
9.14.4.1 Normal procedure. 57
9.14.4.2 Error handling . 57
9.15 ScriptEvent procedure . 57
9.15.1 General Description . 57
9.15.2 Parameters. 57
9.15.2.1 Argument Parameters . 57
9.15.3 Invoking entity (SRF) . 58
9.15.3.1 Normal procedure. 58
9.15.3.2 Error handling . 58
9.15.4 Responding entity (SCF). 59
9.15.4.1 Normal procedure. 59
9.15.4.2 Error handling . 59
9.16 ScriptInformation procedure. 59
9.16.1 General description . 59
9.16.2 Parameters. 59
9.16.2.1 Argument Parameters . 59
9.16.3 Invoking entity (SCF) . 60
9.16.3.1 Normal procedure. 60
9.16.3.2 Error handling . 60
9.16.4 Responding entity (controlling SRF) . 60
9.16.4.1 Normal procedure. 60
9.16.4.2 Error Handling. 60
9.17 ScriptRun procedure. 60
9.17.1 General description . 60
9.17.2 Parameters. 61
9.17.2.1 Argument Parameters . 61
9.17.3 Invoking entity (SCF) . 61
9.17.3.1 Normal procedure. 61
9.17.3.2 Error handling . 61
9.17.4 Responding entity (SRF) . 61
9.17.4.1 Normal procedure. 61
9.17.4.2 Error handling . 62
9.18 SpecializedResourceReport procedure . 62
9.18.1 General description . 62
9.18.2 Parameters. 62
ETSI
6 ETSI EN 301 931-3 V1.1.2 (2001-09)
9.18.2.1 Argument Parameters . 62
9.18.3 Invoking entity (SRF) . 62
9.18.3.1 Normal procedure. 62
9.18.3.2 Error handling . 62
9.18.4 Responding entity (SCF). 63
9.18.4.1 Normal procedure. 63
9.18.4.2 Error handling . 63
9.19 SRFCallGap procedure. 63
9.19.1 General description . 63
9.19.2 Parameters. 63
9.19.2.1 Argument Parameters . 63
9.19.3 Invoking entity (SRF) . 64
9.19.3.1 Normal procedure. 64
9.19.3.2 Error handling . 64
9.19.4 Responding entity (SCF). 64
9.19.4.1 Normal procedure. 64
9.19.4.2 Error handling . 65
10 Parameters.65
10.1 CallSegmentID. 65
10.2 CallSegmentToCancel. 65
10.3 CollectedInfo . 65
10.4 ControlType. 67
10.5 Digits. 67
10.6 CorrelationID. 68
10.7 DisconnectFromIPForbidden . 68
10.8 GapIndicators. 68
10.9 InformationToRecord. 68
10.10 InformationToSend . 69
10.11 LastEventIndicator . 70
10.12 LegID . 70
10.13 Media. 70
10.14 MailBoxID. 70
10.15 ReceivedStatus. 70
10.16 RecordedMessageID. 70
10.17 RecordedMessageUnits . 71
10.18 RequestAnnouncementComplete . 71
10.19 SRFgapCriteria . 71
10.20 SubscriberID. 71
10.21 UIScriptId. 71
10.22 UIScriptResultInfo . 71
10.23 UIScriptSpecificInfo. 71
11 Error procedures .72
11.1 Operation related error procedures. 72
11.1.1 Cancelled. 72
11.1.1.1 Operations SCF->SRF . 72
11.1.1.1.1 Procedures at invoking entity (SCF) . 72
11.1.1.1.2 Procedures at responding entity (SRF) . 73
11.1.2 ImproperCallerResponse. 73
11.1.2.1 Operations SCF->SRF . 73
11.1.2.1.1 Procedures at invoking entity (SCF) . 73
11.1.2.1.2 Procedures at responding entity (SRF) . 73
11.1.3 MissingCustomerRecord. 74
11.1.3.1 Operations SCF->SRF . 74
11.1.3.2 Operations SRF->SCF . 74
11.1.3.2.1 Procedures at invoking entity (SRF) . 74
11.1.3.2.2 Procedures at responding entity (SCF) . 74
11.1.4 MissingParameter . 74
11.1.4.1 Operations SCF->SRF . 74
11.1.4.1.1 Procedures at invoking entity (SCF) . 74
11.1.4.1.2 Procedures at responding entity (SRF) . 75
ETSI
7 ETSI EN 301 931-3 V1.1.2 (2001-09)
11.1.4.2 Operations SRF->SCF . 75
11.1.4.2.1 Procedures at invoking entity (SRF) . 75
11.1.4.2.2 Procedures at responding entity (SCF) . 75
11.1.5 ParameterOutOfRange . 75
11.1.5.1 Operations SCF->SRF . 75
11.1.6 SystemFailure. 76
11.1.6.1 Operations SCF->SRF . 76
11.1.6.2 Operations SRF->SCF . 76
11.1.7 TaskRefused . 76
11.1.7.1 Operations SCF->SRF . 76
11.1.7.2 Operations SCF->SRF . 76
11.1.7.3 Operations SRF->SCF . 76
11.1.8 UnavailableResource. 76
11.1.8.1 Operations SCF->SRF . 76
11.1.8.2 Operations SCF->SRF . 76
11.1.8.2.1 Procedures at invoking entity (SCF) . 76
11.1.8.2.2 Procedures at responding entity (SRF) . 77
11.1.9 UnexpectedComponentSequence. 77
11.1.9.1 Operations SCF->SRF . 77
11.1.9.2 Operations SRF->SCF . 77
11.1.10 UnexpectedDataValue. 77
11.1.10.1 Operations SCF->SRF . 77
11.1.10.2 Operations SCF->SRF . 78
11.1.10.3 Operations SRF->SCF . 78
11.1.11 UnexpectedParameter . 78
11.1.11.1 Operations SCF->SRF . 78
11.1.11.2 Operations SRF->SCF . 78
11.1.12 UnknownLegID . 78
11.1.12.1 Operations SCF->SRF . 78
11.1.13 UnknownSubscriber. 78
11.1.13.1 Operations SCF->SRF . 78
11.1.14 Expiration of TSRF. 79
11.1.14.1 General Description. 79
11.1.14.1.1 Error description . 79
11.1.14.2 Procedures SRF->SCF. 79
11.1.14.2.1 Procedures at the invoking entity (SRF). 79
11.1.14.2.2 Procedures at the responding entity (SCF). 79
12 ASN.1 Definition.79
12.1 IN CS-3 Types . 79
12.1.1 Data Types. 79
12.1.2 Classes.
...