SIST EN 301 931-4 V1.1.2:2005

• Abstract:

  This standard describes the SDLs of the protocol specification

• 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-4 V1.1.2 (2001-09) - Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 4: SDLs for SCF-SSF interface

SIST EN 301 931-4 V1.1.2:2005 is the Slovenian adoption of ETSI EN 301 931-4 V1.1.2 for Intelligent Network (IN) Capability Set 3 (CS3). It specifies the SDLs for the Intelligent Network Application Protocol (INAP) on the SCF-SSF interface, so it is mainly for engineers, implementers, test teams, and telecom architects working on INAP CS3 call control and service switching models.

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

SIST EN 301 931-4 V1.1.2:2005 is Part 4 of the INAP CS3 protocol specification. It specifies the SDL model for the SSF-SCF interface and gives an overview of how that model is arranged.

The document is organized into clauses 1 to 8, covering scope, references, definitions and abbreviations, an introduction to the INAP CS3 SDL model, Connection View State Transitions, the Basic Call Controller Process, modelling of the FIM and Multiple Point of Control, and the SDLs themselves.

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

SIST EN 301 931-4 V1.1.2:2005 defines the external behaviour of the SDL model and uses the internal structure mainly for modelling. That matters because the document tells implementers what the model must show at the interfaces, while leaving internal implementation structure open.

Scope and model limits

Clause 1 limits the document to the SSF-SCF interface in SDL form and an overview of the SDL model structure. Clause 4.1 adds that the model is intended to cover call party handling, signalling events, Detection Points, and SCF operations. It is not a full model of the SSF-SCF interface, so readers should use it as a behavioral model for call handling rather than as a complete implementation blueprint.

Clause 4.1 also states that the normative part is the dynamic behaviour at the external interfaces. The internal behaviour and structure are provided for modelling purposes only, which means the SDL processes are useful for simulation and analysis but do not impose a fixed internal implementation architecture.

How the SDL model is built

Clause 4.2 describes the information model and how its objects map into SDL processes and data structures. Call Segment Association manages creation of Call Segments and the dialogue with the SCF, while Call Segment is split across process types that handle the connection view and state handling.

The model uses separate process types for O-BCSM and T-BCSM, and the Leg and Connection Point concepts are represented as data structures. In practice, this helps readers understand how one call is broken into manageable objects for signalling, triggering, and call control.

Interfaces and file-level model view

The SDL model uses five interfaces: SigCon, IBI, INAP to the SCF, MGT, and SRF. The text explains that some are external or standardized, while others are internal to the model. For users, this means the SDLs can be read as a layered model with clear places for signalling, management, and service control interactions.

Clause 4.3 points to message sequence charts in attached files that show interworking after a SetupInd is received through SigCon. These examples are there to show how the model behaves during call establishment and triggering.

FIM and Multiple Point of Control

Clause 7.1 splits the Feature Interactions Manager (FIM) into a FIM Controller and a FIM Agent for modelling. The FIM Controller creates FIMAgent instances, and the FIMAgent handles TDP processing and the link between BCSMs and CSAID/legID pairs. This matters because it shows how feature interactions are handled per call in the model.

Clause 7.2 models Multiple Point of Control by chaining BCSMs. The BCP translates primitives where needed, and the chain lets the model represent more than one SSF-SCF control relationship on the same originating or terminating side. For readers, this means the SDLs support evaluation of multi-service call handling and trigger order.

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

SIST EN 301 931-4 V1.1.2:2005 relies on the definitions and abbreviations from EN 301 931-1, and several model terms are central to reading it.

• Feature Interactions Manager (FIM) - the modelling function that handles interactions between IN services.
• Call Segment Association (CSA) - the object that groups related Call Segments and manages dialogue with the SCF.
• Call Segment (CS) - the model object used to represent a call segment and its connection-view handling.
• Basic Call Controller Process (BCP) - the process that manages signalling to and from the BCSMs.
• Message Sequence Charts (MSC) - the attached charts that show process interworking after call setup.
• Multiple Point of Control (MPC) - the scenario where more than one SSF-SCF control relationship acts on the same BCSM.

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

SIST EN 301 931-4 V1.1.2:2005 is used by telecom protocol engineers, INAP implementers, and switch software teams who need the SDL behaviour of IN CS3. It is also relevant to conformance test authors, because the text says the Core INAP CS3 conformance test suite was automatically derived from the model. Teams doing service emulation or evaluation can use it as a simulation platform.

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

SIST EN 301 931-4 V1.1.2:2005 is part of the EN 301 931 series and depends on the companion parts named in the foreword and body of the document.

• EN 301 931-1 - provides the referenced documents, definitions, and abbreviations.
• EN 301 931-2 - provides the SCF behaviour, Connection View State Transitions, the Basic Call Controller Process, and ASN.1 data used by this part.
• EN 301 931-3 - provides ASN.1 definitions used for imported data structures.
• EN 301 140-1 - the ETSI Core INAP CS-2 basis named in the foreword.
• ITU-T Recommendation Q.1238 (1999) - the ITU-T IN CS3 basis named in the foreword.

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

The document contains the SDL model structure, the mapping from information model objects to SDL processes, and figures that explain the half-call and full-call views. It also includes example message sequence charts for call establishment and TDP triggering in single-point and multiple-point control cases.

The SDL diagrams themselves are supplied in the accompanying files, including the PDF and related model archive. The text also points to the external files used for the process interworking examples.

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 – 4.
del: Jezik SDL za vmesnik SCF-SSF
Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network
Application Protocol (INAP); Protocol specification; Part 4: SDLs for SCF-SSF interface
Ta slovenski standard je istoveten z: EN 301 931-4 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 4: SDLs for SCF-SSF interface

2 ETSI EN 301 931-4 V1.1.2 (2001-09)
Reference
DEN/SPAN-03063/1-4
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-4 V1.1.2 (2001-09)
Contents
Intellectual Property Rights .4
Foreword.4
1 Scope.5
2 References.5
3 Definitions and abbreviations.5
3.1 Definitions . 5
3.2 Abbreviations. 5
4 Introduction to the INAP CS3 SDL model .5
4.1 Scope of the CS-3 model . 5
4.2 The Information Model used in the CS-3 SDL model. 6
4.3 Example for the interworking of the SSF/CCF SDL processes. 11
5 Connection View State Transitions .11
6 Basic Call Controller Process.11
7 Modelling of the FIM and Multiple Point of Control .11
7.1 Overview of the FIM. 11
7.2 Approach to Multiple Point of Control. 12
8 SDLs .12
History .13
ETSI
4 ETSI EN 301 931-4 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 is part 4 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 1 to 3 define the Intelligent Network (IN) Application Protocol (INAP) for IN
Capability Set 3 (IN CS-3). The present document and parts 1 to 3 define the INAP for IN CS-3 based upon ETSI Core
INAP CS-2 (EN 301 140-1) and ITU-T IN CS3 Recommendation Q.1238 (1999).
The structure of the present document and parts 1 to 3 follows the ITU-T Recommendation Q.1238 rather than that
usual for an ETSI deliverable.
The SDL diagrams are contained in archive en_30193104v010102p0.zip which accompanies the present document.
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 May 2002
ETSI
5 ETSI EN 301 931-4 V1.1.2 (2001-09)
1 Scope
The present document is part 4 of the multi-part deliverable for IN Capability Set-3. The present document specifies the
protocol on the SSF-SCF interface in SDL, and provides an overview of the structure of the SDL model.
2 References
All documents referred to in the present document are identified in EN 301 931-1.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 301 931-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations and acronyms given in EN 301 931-1 apply.
4 Introduction to the INAP CS3 SDL model
4.1 Scope of the CS-3 model
The SDL model developed for CoreINAP CS-3 is based upon that produced for CS-2. However, there have been
extensive revisions to the internals of the CS-2 model:
- the CS-1 and CS-2 models have been combined;
- the InterfaceHandler process has been removed, replaced by the SSME-Control which only handles SSF-SCF
communication;
- the BCP has been added to manage all signalling to/from the BCSMs (previously passed through the
InterfaceHandler);
- as a consequence, the CS process is updated based on the DPs received from the BCSMs, not on the signalling;
- the Trigger Table has been re-designed, and effort has gone into using RemoteProcedures, refining data
structures and ensuring correct initialization and use of data structures, all with the objective of making the SDL
model simulate more efficiently;
- the FIMController and FIMAgent have been added to model Multiple Point of Control;
- functionality has been extended to model new behaviour in CS-3.
The normative information provided by the SDL diagrams is the dynamic behaviour at the external interfaces. The
internal behaviour and structure have been introduced for modelling purposes. No SDL specification of the SCF is
provided; the behaviour of the SCF is specified in clause 9 of EN 301 931-2.
The SDL model specifies precisely and unambiguously the external behaviour and the interworking between the
different functional entities: SSME, CSA, CS, SSF-FSM, BCSM. However, the internal behaviour is only for
information and the SDL model does not impose any requirements on the internal structure of an implementation. The
data structures used are imported from clause 14 of EN 301 931-2 and from clause 12 of EN 301 931-3 (ASN.1
definitions).
ETSI
6 ETSI EN 301 931-4 V1.1.2 (2001-09)
The SDLs are a full data model, and therefore can be used for simulation purposes. There are however, some limitations
with the SDL model. The model only concerns the SCF-SSF interface. The model s intended to cover call party
handling only, it is not a full model of the SCF-SSF interface. It is intended to illustrate the CSCV transitions on
signalling events, Detection Points and SCF operations. Where the model does go beyond CPH, in making reference to
charging operations etc., then these are not fully modelled, in particular if they have no impact on CPH and on CSCV
transitions.
The conformance test suite for Core INAP CS3 has been automatically derived from the model. The model can also be
used as a platform for service emulation etc.
4.2 The Information Model used in the CS-3 SDL model
Figure 1 shows the IN CS-3 information model. The various objects in the information model are defined in
clause 6.6.2.1 of EN 301 931-2. There are zero, one or many Call Segments in one Call Segment Association. There is a
one to one correspondence between Call Segment and Connection Point; a Call Segment contains 0 or
1 ControllingLeg, and 0 or more Passive Legs, and so on. There are two objects of type BCSM, the OriginatingBCSM
and the TerminatingBCSM.
Call Segment Association
0,m
Call Segment
1 0,m
Connection Point
Leg State Model
Passive Leg Controlling Leg
BCSM
0,1 0,1 0,1 0,1
11 1 1
Terminating BCSM Originating BCSM
Figure 1: IN CS-3 information model
Figure 2 shows the SDL model of CS3 SSF/CCF. The objects in the information model of figure 1 map to the SDL
model of figure 2 in the following way.
The Call Segment Association object is modelled by a process type in the SDL model. The CallSegmentAssociation
manages:
- the creation of CallSegments; and
- the dialogue with the SCF (via the SSME Controller and TCAP).
The Call Segment object is modelled using two process types in the SDL model: CallSegment and SSF-FSM.
ETSI
7 ETSI EN 301 931-4 V1.1.2 (2001-09)
The SSF-FSM process type corresponds with the FSM for Call Segment described in clause 8.2.2 of EN 301 931-2.
The process type CallSe
...