SIST EN 301 931-1 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-1 V1.1.2 (2001-09) - Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 1: Common aspects

SIST EN 301 931-1 V1.1.2:2005 is the Slovenian adoption of ETSI EN 301 931-1 V1.1.2. It specifies the common aspects of Intelligent Network Application Protocol (INAP) for Intelligent Network Capability Set 3 (CS3), including shared protocol rules, data types, security information, and the lower-layer services used between functional entities. In practice, it is the common reference for engineers, operators, vendors, and testers working on IN CS3 interfaces in fixed and mobile network environments.

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

SIST EN 301 931-1 V1.1.2:2005 gives a brief introduction to IN CS-3 functional-entity modelling and the protocol aspects that are common to all interfaces. The standard focuses on the shared framework behind INAP rather than on one single service feature.

It covers:

• physical examples of interface interconnection
• services assumed from lower layers, such as TCAP
• IN security information
• common data types used across interfaces

The document is organized into clauses on scope, references, abbreviations, functional-entity scope, FE models, FE relationships, protocol realization, congestion control, protocol mechanisms, services from lower layers, error definitions, and common definitions.

Annex	What it covers
Annex A	Non-backward-compatible changes between IN CS2 and IN CS3
Annex B	Bibliography

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

SIST EN 301 931-1 V1.1.2:2005 describes the common architectural and protocol rules that let different IN CS3 functional entities work together. For implementers, the important point is that this part defines the shared behaviour, naming, and communication framework that the more specific parts build on.

IN CS3 service scope and access

Clause 4 frames IN CS-3 around end user access, call-related service control, end user interaction, service management, Call Party Handling (CPH), internetworking, security, out-channel user interaction, call-unrelated service control, and feature interactions. It states that access may come through analogue line interfaces, ISDN BRI and PRI, and traditional trunk and SS No. 7 interfaces. In practice, this tells a designer which network entry points and service categories the architecture is meant to support.

Functional entities and their roles

Clause 5 models the main Functional Entities (FE) used in the Distributed Functional Plane, including CCF/SSF, SRF, SCF, SDF, CCF/CUSF, and SMF. It also breaks each FE into internal components such as managers, data parts, and finite state machine structures. This matters because implementation and conformance work often depends on which FE owns a function, which FE stores data, and which FE controls interaction.

FE relationships and trusted-network use

Clause 6 summarizes the FE relationships, including SCF-SSF, SCF-SCF, SCF-SDF, SDF-SDF, CUSF-SCF, CUSF-SSF, and the management relationships from SMF. The text says most relationships are intended for trusted-network use, while only a limited set supports internetworking across networks. In practice, this affects interconnect design, security boundaries, and what may be transferred between operator domains.

Protocol realization and application contexts

Clause 7 explains how communication is realized through Application Entities (AEs), Application Process Instances (APIs), and Application Contexts. It also describes the use of Transaction Capabilities (TC), Single Association Control Function (SACF), and the encoding rules for abstract syntax and transfer syntax. For implementers, this is the part that turns the functional model into actual signaling sessions and message exchanges.

Congestion control

Clause 8 covers both lower-layer flow control and application-level flow control. It refers to SCCP flow control and to INAP procedures such as call gapping, and it says a denied request should produce a meaningful error to the running Service Logic Program (SLP). That means congestion handling is not only a transport issue - the service logic also has to behave predictably when traffic must be reduced.

Security mechanisms

Clause 9 defines generic IN interface security based on X.509 Authentication Framework and the Simple Public Key GSS-API Mechanism (SPKM). It also defines screening requirements for INAP application contexts and protocols, plus authentication procedures such as simple authentication, strong authentication, external procedures, and SPKM. In practice, this gives the security model for protected signaling and for filtering or transforming information on sensitive interfaces.

Lower-layer service assumptions

Clause 10 states what INAP assumes from TCAP and SCCP. It covers dialogue handling, component handling, message routing, return-on-error behaviour, and segmentation/reassembly for longer messages. For deployment, this tells you which signaling-layer features must already exist for the INAP exchange to work correctly.

Error handling and common definitions

Clause 11 lists the error types used by INAP operations, such as Cancelled, MissingParameter, ParameterOutOfRange, SystemFailure, TaskRefused, UnknownResource, and UnknownSubscriber. Clause 12 then collects the common object identifiers, data types, operation codes, error definitions, and common classes. These clauses are the reference point for implementation, interoperability testing, and troubleshooting.

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

SIST EN 301 931-1 V1.1.2:2005 uses a shared vocabulary so that the protocol, models, and interfaces mean the same thing across implementations.

• BCSM (Basic Call State Model) - the abstract call-processing model used to describe how a basic two-party call is handled and where IN logic can intervene.
• BCUSM (Basic Call Unrelated State Model) - the analogous model for processing that happens outside the context of a call.
• SCF (Service Control Function) - the functional entity that executes service logic and controls service behaviour.
• SSF (Service Switching Function) - the functional entity that detects triggers in call processing and interacts with the SCF.
• SRF (Specialized Resource Function) - the entity that provides resources such as voice interaction, messaging, or text-to-speech support.
• SDF (Service Data Function) - the entity that provides controlled access to service data.
• SMF (Service Management Function) - the management entity used to configure, test, monitor, and secure IN components.
• FEAM (Functional Entity Access Manager) - the internal access manager that handles message exchange between functional entities.

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

SIST EN 301 931-1 V1.1.2:2005 is used by telecom network engineers, protocol designers, equipment vendors, service providers, and test teams. They use it when defining INAP interfaces, mapping operations to signaling, setting up FE relationships, and checking security and congestion behaviour.

Quality managers and buyers also use it to confirm that a product or network element is aligned with IN CS3 common protocol rules. It is especially relevant for teams working on IN services such as charging, number portability, call party handling, user interaction, and internetworking between network domains.

What changed in SIST EN 301 931-1 V1.1.2:2005 from IN CS2 to IN CS3?

Annex A of SIST EN 301 931-1 V1.1.2:2005 lists the non-backward-compatible changes between IN CS2 and IN CS3. The main changes recorded there are:

• InitiateAssociation changes from a class 2 operation to a class 1 operation
• the tag used for the extensions parameter in MoveCallSegments changes
• the LegID parameter is removed from RequestedUTSI
• a new transition to Stable call CSCVS is introduced for Stable-2-Party and Stable-1-Party handling

For implementers, these changes matter because they affect encoding, state transitions, and compatibility with CS2 behaviour.

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

SIST EN 301 931-1 V1.1.2:2005 relies on several companion standards and references for the underlying signaling, management, security, and syntax rules.

• EN 301 931-2 / EN 301 931-3 - provide the detailed FE descriptions and interface-specific behaviour for SSF, SCF, and SRF.
• EN 301 140-1 - provides the detailed description of SDF and CUSF functional entities and related interfaces.
• TCAP / ETS 300 287-1 - supplies the Transaction Capabilities used for dialogue and component handling.
• SCCP / Q.711, Q.713, Q.715 - supplies signaling connection control, routing, return-on-error, and message transfer behaviour.
• Q.1231 and Q.1236 - provide the IN CS3 functional and management modelling background.
• M.3010 and M.3400 - provide the TMN management architecture and management-function framework used for service management.
• X.509, X.519, X.680, X.681, X.682, X.683 - provide authentication and ASN.1 notation, constraints, and parameterization for protocol definitions.
• Q.767 - is used as the alignment reference for signaling congestion control behaviour.

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

The document contains architecture figures, FE models, relationship summaries, protocol-realization rules, security mechanisms, and common definitions. It includes a table of minimum TC recommendations for different interfaces, figures for the IN CS-3 DFP architecture and the internal models of CCF/SSF, SRF, SCF, SDF, and CUSF, and detailed text on dialogue and component handling.

It also contains ASN.1 modules for object identifiers, common data types, operation codes, and error types. These parts are used in implementation and testing because they define the identifiers, encodings, and protocol elements that systems must exchange consistently.

Annex A gives a change list for CS2 to CS3 migration, which helps during upgrade planning and interoperability checks. Annex B provides the bibliography for further technical background.

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 – 1.
del: Skupni vidiki
Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network
Application Protocol (INAP); Protocol specification; Part 1: Common aspects
Ta slovenski standard je istoveten z: EN 301 931-1 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 1: Common aspects
2 ETSI EN 301 931-1 V1.1.2 (2001-09)
Reference
DEN/SPAN-03063/1-1
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-1 V1.1.2 (2001-09)
Contents
Intellectual Property Rights .8
Foreword.8
1 Scope.9
2 References.9
3 Abbreviations .12
4 Scope of IN Distributed Functional Plane for capability set 3 .15
4.1 End user access . 16
4.2 Call related service invocation and control. 16
4.3 End user interaction. 17
4.4 IN service management functionality. 17
4.5 Call Party Handling. 17
4.6 Internetworking. 17
4.7 Security. 17
4.8 Out-Channel User Interaction . 18
4.9 Call unrelated service invocation and control . 18
4.10 Feature Interactions. 18
4.11 Distributed Functional Model . 19
4.12 Communication model . 20
5 FE Models .20
5.1 Call Control Function/Service Switching Function (CCF/SSF) Models. 20
5.1.1 General. 20
5.1.2 CCF/SSF Components . 20
5.1.2.1 Basic Call Manager (BCM). 21
5.1.2.2 Feature Interaction Manager/Call Manager (FIM/CM). 21
5.1.2.3 IN - Switching Manager (IN-SM) . 22
5.1.3 CCF/SSF Trigger Information Objects. 24
5.1.4 SSF FSM Structure . 25
5.2 Specialized Resource Function (SRF) Models. 27
5.2.1 General. 27
5.2.2 SRF Components. 27
5.2.2.1 Functional Entity Access Manager (FEAM). 28
5.2.2.2 Resource Control Part (RCP) . 28
5.2.2.3 Resource Function Part (RFP). 28
5.2.2.4 Data Part (DP). 28
5.2.3 SRF Functional Resources. 28
5.2.4 SRF FSM Structure. 29
5.3 Service Control Function (SCF) Models . 30
5.3.1 General. 30
5.3.2 SCF Components. 30
5.3.2.1 Service Logic Execution Manager (SLEM). 31
5.3.2.1.1 General . 31
5.3.2.1.2 Service Logic Selection/Interaction Manager (SLSIM). 31
5.3.2.1.3 Service Logic Processing program Instance (SLPI) . 32
5.3.2.1.4 Resource manager . 32
5.3.2.1.5 Internetworking manager. 32
5.3.2.2 SCF data access manager. 33
5.3.2.2.1 General . 33
5.3.2.2.2 Service data object directory. 33
5.3.2.2.3 IN network-wide resource data . 33
5.3.2.3 Functional routine manager. 33
5.3.2.4 Functional Entity Access Manager (FEAM). 33
5.3.2.5 SLP manager. 33
5.3.2.6 Security manager. 34
ETSI
4 ETSI EN 301 931-1 V1.1.2 (2001-09)
5.3.3 The SCF FSM structure. 34
5.4 Service Data Function (SDF) Models. 35
5.4.1 General. 35
5.4.2 SDF Components. 36
5.4.2.1 SDF Data Manager . 36
5.4.2.2 Functional Entity Access Manager (FEAM). 36
5.4.2.3 Security Manager. 36
5.4.3 Data Types Handled by SDF . 37
5.4.4 SDF FSM Structure. 37
5.5 Call Control Function/Call Unrelated Service Function (CCF/CUSF) Models. 38
5.5.1 General. 38
5.5.2 CCF/CUSF Components . 38
5.5.2.1 Basic Non-Call Manager (BNCM). 39
5.5.2.2 IN - Non-Switching Manager (IN-NSM). 39
5.5.2.3 Feature Interaction Manager/Non-Call Manager (FIM/NCM). 39
5.5.3 Relationship of CCF/CUSF Model Components. 39
5.5.3.1 BNCM relationship to IN-NSM . 39
5.5.3.2 BNCM and IN-NSM relationships to FIM/NCM. 39
5.5.4 CUSF Trigger Information Objects. 40
5.5.5 CUSF FSM Structure. 41
5.6 Service Management Function (SMF) Models . 42
5.6.1 General. 42
5.6.2 SMF Components . 42
5.6.2.1 Configuration Manager. 42
5.6.2.2 Fault Manager . 42
5.6.2.3 Performance Manager. 42
5.6.2.4 Testing Manager. 43
5.6.2.5 Security Control Manager. 43
5.6.2.6 Security Access Manager. 43
5.6.2.7 Functional Entity Access Manager (FEAM). 43
6 Use of FE Relationships.43
6.1 SCF-SSF Relationship. 43
6.2 SCF-SCF Relationship . 44
6.3 SCF-IAF Relationships. 44
6.4 SRF-CCF Relationship. 44
6.5 SRF-SCF Relationship . 44
6.6 SCF-SDF Relationship . 44
6.7 SDF-SDF Relationship. 44
6.8 CUSF-SCF Relationship. 44
6.9 CUSF-SSF Relationship. 45
6.10 SMF-SCF Relationship. 45
6.11 SMF-SDF Relationship . 45
6.12 SMF-CCF/SSF Relationship. 45
6.13 SMF-SRF Relationship. 46
6.14 SMF-SMAF Relationship. 46
6.15 SMF - SCEF Relationship . 46
6.16 SMF-SMF Relationship. 46
6.17 SMF-CCF/CUSF Relationship. 47
7 Protocol Realization.47
7.1 Overview . 47
7.2 Application Contexts. 48
7.3 Abstract Syntax and Transfer Syntax . 48
7.4 SACF/MACF Rules . 48
7.4.1 Reflection of TCAP AC . 48
7.4.2 Sequential/Parallel execution of operations. 49
8 Congestion Control.49
8.1 Lower layer flow control . 49
8.2 Application level flow control. 50
9 Protocol mechanisms .50
ETSI
5 ETSI EN 301 931-1 V1.1.2 (2001-09)
9.1 Compatibility Mechanisms and extensibility rules. 50
9.1.1 Introduction . 50
9.1.2 Definition of INAP compatibility mechanisms. 51
9.1.2.1 Procedures for major additions to INAP. 51
9.1.2.2 Procedures for minor additions to INAP. 51
9.1.2.3 Procedures for inclusion of network specific additions to INAP. 51
9.2 IN Generic Interface Security . 51
9.2.1 Interface Security Requirements. 52
9.2.2 INAP screening requirements. 52
9.2.2.1 INAP Application Context Screening Requirements. 52
9.2.2.2 INAP Protocol Screening Requirements. 52
9.2.3 Security Procedures and Algorithms. 53
9.2.3.1 Authentication Procedures . 53
9.2.3.2 Three-Way Mutual Authentication. 54
9.2.3.3 Assignment of Credentials . 54
9.2.4 Mapping of Security Information Flow Definitions to Tokens. 54
9.2.5 Security FSM definitions. 54
10 Services assumed from Lower Layers .54
10.1 Services assumed from TCAP. 55
10.1.1 Common Procedures. 55
10.1.1.1 Normal Procedures . 55
10.1.1.2 Abnormal Procedures . 56
10.1.1.3 Dialogue Handling. 57
10.1.1.3.1 Dialogue Establishment. 57
10.1.1.3.2 Dialogue Continuation. 58
10.1.1.3.3 Dialogue Termination. 58
10.1.1.3.4 User Abort . 59
10.1.1.3.5 Provider Abort . 59
10.1.1.3.6 Mapping to TC Dialogue Primitives . 59
10.1.1.3.7 Default Mapping to TC Dialogue Parameters. 60
10.1.1.4 Component Handling. 61
10.1.1.4.1 Procedures for INAP Operations. 61
10.1.1.4.2 Mapping to TC Component Primitives. 63
10.1.1.4.3 Default Mapping to TC Component Parameters . 64
10.2 Services assumed from SCCP. 64
10.2.1 Normal Procedures. 65
10.2.2 Service Functions from SCCP . 65
10.2.2.1 SCCP Connectionless Services . 65
10.2.2.1.1 INAP Addressing . 65
10.2.2.1.2 Sequence Control . 66
10.2.2.1.3 Return on Error . 67
10.2.2.1.4 Segmentation/reassembly . 67
10.2.2.1.5 Congestion Control . 67
10.2.2.2 SCCP Connection Oriented Services. 67
10.2.2.3 SCCP Management. 67
11 Error Definitions.68
11.1 Void. 68
11.2 Cancelled . 68
11.2.1 Error description . 68
11.2.2 Parameter description. 68
11.2.3 Relevant interface . 68
11.3 CancelFailed . 68
11.3.1 Error description . 68
11.3.2 Parameter description. 68
11.3.3 Relevant interfaces. 68
11.4 Void. 69
11.5 Void. 69
11.6 Void. 69
11.7 ETCFailed. 69
11.7.1 Error description . 69
ETSI
6 ETSI EN 301 931-1 V1.1.2 (2001-09)
11.7.2 Parameter description. 69
11.7.3 Relevant interface . 69
11.8 Void. 69
11.9 ImproperCallerResponse . 69
11.9.1 Error description . 69
11.9.2 Parameter description. 69
11.9.3 Relevant interfaces. 69
11.10 MissingCustomerRecord . 69
11.10.1 Error description . 69
11.10.2 Parameter description. 70
11.10.3 Relevant interfaces. 70
11.11 MissingParameter. 70
11.11.1 Error description . 70
11.11.2 Parameter description. 70
11.11.3 Relevant interfaces. 70
11.12 Void. 70
11.13 ParameterOutOfRange. 70
11.13.1 Error description . 70
11.13.2 Parameter description. 70
11.13.3 Relevant interfaces. 70
11.14 Void. 71
11.15 RequestedInfoError . 71
11.15.1 Error description . 71
11.15.2 Parameter description. 71
11.15.3 Relevant interface . 71
11.16 Void. 71
11.17 Void. 71
11.18 Void. 71
11.19 Void. 71
11.20 Void. 71
11.21 Void. 71
11.22 SystemFailure . 71
11.22.1 Error description . 71
11.22.2 Parameter description. 72
11.22.3 Relevant interfaces. 72
11.23 TaskRefused. 72
11.23.1 Error description . 72
11.23.2 Parameter description. 72
11.23.3 Relevant interfaces. 72
11.24 Void. 72
11.25 UnavailableResource. 72
11.25.1 Error description . 72
11.25.2 Parameter description. 72
11.25.3 Relevant interface . 73
11.26 UnexpectedComponentSequence. 73
11.26.1 Error description . 73
11.26.2 Parameter description. 73
11.26.3 Relevant interfaces. 73
11.27 UnexpectedDataValue. 73
11.27.1 Error description . 73
11.27.2 Parameter description. 73
11.27.3 Relevant interfaces. 73
11.28 UnexpectedParameter. 73
11.28.1 Error description . 73
11.28.2 Parameter description. 73
11.28.3 Relevant interfaces. 74
11.29 UnknownLegID . 74
11.29.1 Error description . 74
11.29.2 Parameter description. 74
11.29.3 Relevant interfaces. 74
11.30 UnknownResource . 74
11.30.1 Error description . 74
ETSI
7 ETSI EN 301 931-1 V1.1.2 (2001-09)
11.30.2 Parameter description. 74
11.30.3 Relevant interface . 74
11.31 UnknownSubscriber . 74
11.31.1 Error description . 74
11.31.2 Parameter description. 74
11.31.3 Relevant interface . 74
12 Common Definitions.75
12.1 Object identifiers. 75
12.2 Common Data Types. 77
12.3 Operation codes. 77
12.4 Errors. 79
12.4.1 Error types . 79
12.4.2 Error codes . 81
12.5 Common classes. 81
Annex A (informative): List of non backward compatible changes between IN CS2 and IN
CS3 .85
A.1 InitiateAssociation operation has changed to a class 1 operation.85
A.2 Tag modification in the argument of the MoveCallSegments operation .85
A.3 Removal of the LegID parameter in the RequestedUTSI datatype .86
A.4 New transition to "Stable call" CSCVS (Stable-2-Party, Stable-1-Party).86
Annex B (informative): Bibliography.87
History .89
ETSI
8 ETSI EN 301 931-1 V1.1.2 (2001-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 describes the common aspects of IN including an overview of each FE. It also describes aspects
of the protocol that are common to all interfaces, including services assumed from lower layers, IN security information
and the common data types used on all the interfaces.
The present document is part 1 of a multi-part deliverable covering Intelligent Network (IN); Intelligent Network
Application Protocol (INAP); Capability Set 3 (CS3); Protocol specification, as identified below:
Part 1: "Common aspects";
Part 2: "SCF-SSF interface";
Part 3: "SCF-SRF interface";
Part 4: "SDLs for SCF-SSF interface".
The present document and parts 2 to 4 define the Intelligent Network (IN) Application Protocol (INAP) for IN
Capability Set-3 based upon ETSI Core INAP CS-2 (EN 301 140-1 [3]). This set of documents fully define SCF to SSF
interface (part 2) and SCF to SRF interface (part 3) as a subset of the ITU-T IN CS3 Recommendations Q.1238.1,
Q.1238.2 and Q.1238.3 (1999). For the other interfaces, the ETSI Core INAP CS2 series of EN 301 140-1 [3] apply.
In addition to the features supporting IN CS-1 and IN CS-2 functionalities, the present document and parts 2 to 4
provide:
• general extensions to the CS-2 INAP in support of IN CS-3 target services;
• protocol support for Call Party Handling capabilities;
• additional details on services assumed from lower layers and generic interface security;
• SDLs for SSF related procedure handling based upon ITU-T Recommendation Z.100 [55] object oriented
Specification and Description Language (SDL).
National transposition dates
Date of adoption of this EN: 31 August 2001
Date of latest announcement of this EN (doa): 30 November 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 May 2002
Date of withdrawal of any conflicting National Standard (dow): 31 M
...