SIST EN 301 931-2 V1.1.2:2005
(Main)Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 2: SCF-SSF interface
General Information
- 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
- 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
Overview
SIST EN 301 931-2 V1.1.2:2005 is a crucial European standard for telecommunications, detailing the Intelligent Network Application Protocol (INAP) as part of Intelligent Network (IN) Capability Set 3 (CS3). Developed by SIST, this standard specifies the SCF-SSF interface, which plays a fundamental role in enabling advanced call control and network services across both fixed and mobile networks. The scope of this standard includes the integration of CAMEL phases 1, 2, and 3 (Release 1999) to ensure interoperability in European telecommunications, supporting next-generation charging, numbering, and architecture needs.
Key Topics
- Intelligent Network Architecture (IN CS3): Covers the structure and capabilities of the third set of intelligent network functionalities, facilitating enhanced and flexible service provisioning.
- SCF-SSF Interface Specification: Defines the protocol interactions between the Service Control Function (SCF) and Service Switching Function (SSF), ensuring reliable service execution.
- CAMEL Application Part (CAP) Phase 3: Supports GSM mobile network applications by implementing advanced CAMEL Phase 3 features for greater service compatibility and expansion.
- Multiple Point of Control: Enables multiple logical points to control and manage service features within the telecom network.
- Enhanced Charging Procedures: Provides mechanisms for improved call charging and billing accuracy, essential for commercial telecom services.
- Number Portability Support: Ensures seamless number portability, a critical feature for customer retention and regulatory compliance.
- Next-Generation Signalling Support: Integrates support for H.323 and SIP/SDP architectures, facilitating VoIP and multimedia communications.
- Service Logic Processing: Outlines the interaction between the network’s service execution environment and call control mechanisms.
Applications
SIST EN 301 931-2 V1.1.2:2005 is widely utilized in the European telecommunications sector to boost the deployment and management of intelligent networks. Its applications include:
- Fixed and Mobile Network Integration: Enables the development and harmonization of services across both fixed-line and GSM networks.
- Service Provisioning and Customization: Supports telecom operators in designing, deploying, and customizing advanced value-added services such as prepaid billing, call filtering, and multimedia applications.
- Interoperability: Facilitates seamless interaction between network elements from different vendors, driving down integration costs and promoting a competitive supplier environment.
- Migration to Next-Generation Networks: Eases the transition from legacy TDM-based telephony to IP-based platforms by supporting modern signaling protocols.
- Regulatory Compliance: Ensures that number portability and enhanced charging features meet European regulatory requirements, safeguarding customer rights and market flexibility.
Related Standards
Implementers and stakeholders may reference the following standards to ensure complete compatibility and compliance:
- EN 301 931-1: INAP Protocol Specification - Part 1: Core Requirements
- GSM 09.78: Customized Applications for Mobile networks Enhanced Logic (CAMEL) Application Part (CAP)
- ETSI TS 129 212: IP Multimedia Subsystem (IMS) - Service Control
- ITU-T Recommendation Q.1214: INAP for the Intelligent Network CS3
- SIP (RFC 3261): Session Initiation Protocol for multimedia communications
- H.323 series: Packet-based multimedia communications systems
Practical Value
By adhering to SIST EN 301 931-2 V1.1.2:2005, network operators and equipment manufacturers are able to realize interoperable, robust, and scalable intelligent network services. This standard remains a key reference for those seeking to implement advanced call control, flexible charging, and seamless portability across Europe’s telecommunications infrastructure, bridging the gap between legacy networks and the demands of converged, next-generation services.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 931-2 V1.1.2:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 2: SCF-SSF interface". This standard covers: 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.
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.
SIST EN 301 931-2 V1.1.2:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.40 - Data communication networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 931-2 V1.1.2:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentno omrežje (IN) – Tretji nabor zmožnosti inteligentnega omrežja (CS3) – Aplikacijski protokol inteligentnega omrežja (INAP) – Specifikacija protokola – 2. del: Vmesnik SCF-SSFIntelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 2: SCF-SSF interface33.040.40Podatkovna komunikacijska omrežjaData communication networksICS:Ta slovenski standard je istoveten z:EN 301 931-2 Version 1.1.2SIST EN 301 931-2 V1.1.2:2005en01-januar-2005SIST EN 301 931-2 V1.1.2:2005SLOVENSKI
STANDARD
ETSIEN301931-2V1.1.2(2001-09)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkCapabilitySet3(CS3);IntelligentNetworkApplicationProtocol(INAP);Protocolspecification;Part2:SCF-SSFinterfaceSIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)2ReferenceDEN/SPAN-03063/1-2KeywordsCS3,CTM,IN,INAP,protocol,UPTETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)3ContentsIntellectualPropertyRights.20Foreword.201Scope.212References.213Definitionsandabbreviations.213.1Definitions.213.2Abbreviations.214Introduction.215Relationships.215.1SSF-CCFrelationship.215.2SSF-SCFrelationship.226CCF/SSFModel.226.1CCF/SSFFunctionalModelComponents.246.1.1BasicCallManager(BCM).256.1.2FeatureInteractionManager/CallManager(FIM/CM).256.1.3IN-SwitchingManager(IN-SM).256.1.4CCF/SSFModelcomponentsrelationships.266.1.4.1RelationshipbetweenSCFandIN-SM.266.1.4.2RelationshipbetweenIN-SMandFIM/CM.266.1.4.3RelationshipbetweenFIM/CMandBCM.266.1.4.4RelationshipbetweenFIM/CMandnon-INFM.266.1.5TypicalSequenceofModelActions.276.2CallControlFunction.286.2.1BasicCallControllerProcess.296.2.1.1Overview.296.2.1.2CreationanddeletionsofBCSMinstances.296.2.2SignallingTerminations.306.2.2.1Overview.306.2.2.2AbstractSignallingPrimitives.316.2.2.3SignallingTerminations.336.2.2.4SignallingConfigurations.336.2.3FSMforCallControlSignallingTermination.336.2.3.1Overview.336.2.3.2FSMstates.336.2.3.2.1Idle.336.2.3.2.2RequestedPath.346.2.3.2.3ProgressedPath.346.2.3.2.4AcknowledgedPath.356.2.3.2.5ConfirmedPath.356.2.3.3Examplemapping.366.2.4SignallingInterworking.366.2.4.1GeneralObjectives.366.3FunctionalInterfacebetweentheCCFandtheSSF.376.4Basiccallmanager(BCM).386.4.1BCSMModel.386.4.2BCSMdescription.396.4.2.1OriginatingBCSM.416.4.2.1.1O_Null.426.4.2.1.2Authorize_Origination_Attempt.426.4.2.1.3Collect_Information.436.4.2.1.4Analyse_Information.456.4.2.1.5SelectRoute.466.4.2.1.6Authorize_Call_Setup.47SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)46.4.2.1.7Send_Call.486.4.2.1.8O_Alerting.496.4.2.1.9O_Active.506.4.2.1.10O_Suspended.516.4.2.1.11O_Exception.526.4.2.2TerminatingBCSM.536.4.2.2.1T_Null.546.4.2.2.2Authorize_Termination_Attempt.556.4.2.2.3SelectFacility.556.4.2.2.4PresentCall.566.4.2.2.5T_Alerting.576.4.2.2.6T_Active.586.4.2.2.7T_Suspended.596.4.2.2.8T_Exception.596.4.3BCSMResumePointsandBCSMTransitionsintheINCS-3CallModel.616.4.3.1OriginatingBCSM:DetailedSetofO_BCSMTransitions.616.4.3.2TerminatingBCSM:DetailedSetofT_BCSMTransitions.656.4.4BCSMindicationsfortheCS-3CallModel.686.4.4.1User-O_BCSMAccessSignallingIndications(Category1).686.4.4.2T_BCSM-UserAccessSignallingIndications(Category2).706.4.4.3IntraLocalExchangeBCSMIndications(Category3).716.4.5MappingfromCausetoDP.756.4.5.1O_BCSM:MappingTablefromCausetoDP.756.4.5.2T_BCSM:MappingTablefromCausetoDP.786.4.6BCSMDetectionPoint.806.4.7DPCriteria.826.5Featureinteractionsmanager(FIM)/callmanager(CM).906.5.1DPHandling.916.5.1.1FIMmechanisms.926.5.1.1.1Servicelogicinstanceinteractionsconsiderations.936.5.1.2DPandEventDistributionandFiltering.966.5.1.2.1GeneralRules.976.5.1.2.2SinglePointofControl(SPC)Rules.976.5.1.2.3MultiplePointsofControl(MPC)Rules.986.5.1.3TDPandEDPProcessingScenariosforSinglePointofControl.1006.5.1.4ImplicitEDPDisarmingRules.1016.6IN-switchingmanager(IN-SM).1036.6.1IN-switchingstatemodel(IN-SSM).1036.6.2TheConnectionViewModel.1076.6.2.1ConnectionViewObjects.1086.6.2.1.1CallSegmentAssociationObject.1086.6.2.1.2CallSegmentObject.1096.6.2.1.3LegObject.1096.6.2.1.4ConnectionPointObject.1106.6.2.2RelationshipofBCSMtoConnectionViewCSStates.1106.6.3ConnectionViewStateTransitions.1116.6.3.1Introduction.1116.6.3.2SSME-Control.1116.6.3.2.1Introduction.1116.6.3.2.2TransitiontableforSSME-Control.1116.6.3.3CallSegmentAssociationConnectionView(CSACV)Transitions.1126.6.3.3.1Introduction.1126.6.3.3.2FunctionalProceduresforCallSegmentAssociation(CSA).1126.6.3.3.3TransitiondiagramforCallSegmentAssociation(CSA).1136.6.3.3.4TransitiontableforCallSegmentAssociation(CSA).1136.6.3.4CallSegmentConnectionView(CSCV)Transitions.1156.6.3.4.1Introduction.1156.6.3.4.2FunctionalProceduresforCallSegment(CS).1176.6.3.4.3CallSegmentConnectionView(CSCV)StateDescription.1266.6.3.5ExamplesofCVConfigurations,CompositeTransitions.1486.6.3.5.1ExamplesofCompositeTransitionsfromthe"Originating_Setup"CSCVstate.1486.6.3.5.2ExamplesofCompositeTransitionsfromthe"Stable_2_Party"CSCVstate.149SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)56.6.3.5.3ExamplesofCompositeTransitionsfromthe"Stable_Multi_Passive_Party"CSCVstateprovidedtheCShasonly2pendinglegs.1506.6.3.6OverviewofTransitionsofDPEventstotheCSCVstates.1516.7Out-ChannelCall-RelatedUserInteraction(OCCRUI).1596.7.1DescriptionoftheOCCRUIattheCCF/SSF"CallModel"level.1596.7.1.1Firstcase:theUSIinformationisconsideredasa"notificationpreviouslyrequestedbytheSCF".1596.7.1.2Secondcase:theUSIinformationisanadditionalandoptionalinformation.1606.7.1.3Synthesis.1607SCFModel.1617.1Introduction.1617.2SCFModelComponents.1617.2.1ServiceLogicProcessingprogramInstance(SLPI).1627.2.2FunctionalRoutineCategories.1627.2.2.1SLPImanagementfunctionalroutines.1627.2.2.2SLPIcommunicationfunctionalroutines.1627.2.2.3Timermanagementfunctionalroutines.1627.2.2.4Datamanagementinterfacefunctionalroutines.1627.2.2.5Asynchronouseventhandlingfunctionalroutines.1627.2.2.6Connectionmanagementfunctionalroutines.1627.2.2.7Specializedresourcemanagementfunctionalroutines.1627.2.2.8OAMfunctionalroutines.1638FSMforSSF.1638.1SSFmanagementfinitestatemodel(SSMEFSM).1658.2INSSFswitchingstatemodel(IN-SSM)FSM.1668.2.1FiniteStateModelforCallSegmentAssociation(CSA).1708.2.1.1Statea:Idle.1718.2.1.2Stateb:Active.1728.2.2FiniteStateModelforCallSegment.1758.2.2.1Statea:Idle.1808.2.2.2Statec:WaitingForInstructions.1818.2.2.3Stated:WaitingForEndOfUserInteraction(WFI).1828.2.2.4Statee:WaitingForEndOfTemporaryConnection(WFI).1838.2.2.5Statef:Monitoring.1848.2.2.6Stateh:WaitingForEndOfUserInteraction(Monitoring).1858.2.2.7Statei:WaitingForEndOfTemporaryConnection(Monitoring).1868.3AssistingSSFFSM.1878.3.1Stateaa:Idle.1888.3.2Stateab:WaitingForInstructions.1888.3.3Stateac:WaitingForEndOfUserInteraction.1898.4Handed-offSSFFSM.1908.4.1Stateha:Idle.1918.4.2Statehb:WaitingForInstructions.1918.4.3Statehc:WaitingForEndOfUserInteraction.1929FSMforSCF.1939.1RelationshipbetweentheSLPandtheinterSCFcallstatemodel.1939.2TheSCFFSMstructure.1939.3PartialSCFManagementEntity(SCME)StateTransitionDiagram.1949.3.1TheStatusReportFSM.1949.3.1.1StateM1:"StatusReportIidle".1959.3.1.2StateM2:"WaitingforSSFResourceStatusReport".1959.3.2TheServiceFilteringFSM.1959.3.2.1StateM3:"Servicefilteringidle".1969.3.2.2StateM4:"WaitingforSSFservicefilteringresponse".1969.3.3TheActivityTestFSM.1969.3.3.1StateM5:"Activitytestidle".1969.3.3.2StateM6:"Waitingforactivitytestresponse".1979.3.4TheManageTriggerDataFSM.1979.3.4.1StateM7:"ManageTriggerDataidle".1979.3.4.2StateM8:"WaitingforManageTriggerDataresponse".1979.3.5TheResourceControlObject.198SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)69.4SSF/SRFRelatedStates(SCSM-SSF/SRF).1989.4.1FiniteStateModelforSSF/SRFinterface.2009.4.1.1StateS1:"Idle".2009.4.1.2StateS2:"PreparingSSF/SRFInstructions".2019.4.1.2.1StateS2.1:"AssistRequestIdle".2029.4.1.2.2StateS2.2:"WaitingforAssistRequest".2029.4.2FiniteStateModelforCSA.2039.4.2.1StateI1:"SSFControlIdle".2049.4.2.2StateI2:"PreparingSSFInstructions".2049.4.3FiniteStateModelforCallSegment.2069.4.3.1StateC1:"CSControlIdle".2089.4.3.2StateC2:"PreparingCSInstructions".2089.4.3.2.1StateC2.1:"PreparingCSInstructions".2109.4.3.2.2StateC2.2:"WaitingforNotificationorRequest".2129.4.3.2.3StateC2.3:"Queuing".2149.4.3.3StateC3:"SuspendedandUserInteraction".2169.4.3.3.1StateC3.1:"DetermineMode".2179.4.3.3.2StateC3.2:"UserInteraction".2189.4.3.3.3StateC3.3:"EstablishingTemporaryConnection".2219.4.3.4StateC4:"NotSuspendedandUserInteraction".2239.4.3.4.1StateC4.1:"DetermineModeMonitoring".2249.4.3.4.2StateC4.2:"UserInteractionMonitoring".2259.4.3.4.3StateC4.3:"EstablishingTemporaryConnectionMonitoring".2279.4.4FiniteStateModelforAssistingSSF.2289.4.4.1StateA1:"AssistingSSFIdle".2309.4.4.2StateA2:"PreparingSSFInstructions".2309.4.4.3StateA3:"UserInteraction".2319.4.5FiniteStateModelforHanded-offSSF.2329.4.5.1StateH1:"Handed-offSSFIdle".2339.4.5.2StateH2:"PreparingSSFInstructions".2339.4.5.3StateH3:"UserInteraction".23410FSMforUSI.23510.1USIFSMforSSF.23510.2USIFSMforSCF.23611OperationProcedures.23711.1ActivateServiceFilteringprocedure.23711.1.1Generaldescription.23711.1.1.1Parameters.23711.1.1.1.1ArgumentParameters.23711.1.1.1.2ResultParameters.23811.1.2Invokingentity(SCF).23811.1.2.1Normalprocedure.23811.1.2.2Errorhandling.23911.1.3Respondingentity(SSF).23911.1.3.1Normalprocedure.23911.1.3.2Errorhandling.24011.2ActivityTestprocedure.24011.2.1Generaldescription.24011.2.1.1Parameters.24111.2.1.1.1ArgumentParameters.24111.2.1.1.2ResultParameters.24111.2.2Invokingentity(SCF).24111.2.2.1Normalprocedure.24111.2.2.2Errorhandling.24111.2.3Respondingentity(SSF).24111.2.3.1Normalprocedure.24111.2.3.2Errorhandling.24111.2.4Invokingentity(SSF).24211.2.4.1Normalprocedure.24211.2.4.2Errorhandling.242SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)711.2.5Respondingentity(SCF).24211.2.5.1Normalprocedure.24211.2.5.2Errorhandling.24211.3ApplyChargingprocedure.24211.3.1Generaldescription.24211.3.1.1Parameters.24311.3.1.1.1ArgumentParameters.24311.3.2Invokingentity(SCF).24311.3.2.1Normalprocedure.24311.3.2.2Errorhandling.24411.3.3Respondingentity(SSF).24411.3.3.1Normalprocedure.24411.3.3.2Errorhandling.24511.4ApplyChargingReportprocedure.24511.4.1Generaldescription.24511.4.1.1Parameters.24611.4.1.1.1ArgumentParameters.24611.4.2Invokingentity(SSF).24611.4.2.1Normalprocedure.24611.4.2.2Errorhandling.24811.4.3Respondingentity(SCF).24811.4.3.1Normalprocedure.24811.4.3.2Errorhandling.24811.5AssistRequestInstructionsprocedure.24811.5.1Generaldescription.24811.5.1.1Parameters.24911.5.1.1.1ArgumentParameters.24911.5.2Invokingentity(SSF).24911.5.2.1Normalprocedure.24911.5.2.2Errorhandling.24911.5.3Respondingentity(SCF).24911.5.3.1Normalprocedure.24911.5.3.2Errorhandling.25011.6CallGapprocedure.25011.6.1Generaldescription.25011.6.1.1Parameters.25011.6.1.1.1ArgumentParameters.25011.6.2Invokingentity(SCF).25111.6.2.1Normalprocedure.25111.6.2.2Errorhandling.25111.6.3Respondingentity(SSF).25111.6.3.1Normalprocedure.25111.6.3.2Errorhandling.25311.7CallInformationReportprocedure.25311.7.1Generaldescription.25311.7.1.1Parameters.25311.7.1.1.1ArgumentParameters.25311.7.2Invokingentity(SSF).25411.7.2.1Normalprocedure.25411.7.2.2Errorhandling.25411.7.3Respondingentity(SCF).25511.7.3.1Normalprocedure.25511.7.3.2Errorhandling.25511.8CallInformationRequestprocedure.25511.8.1Generaldescription.25511.8.1.1Parameters.25511.8.1.1.1ArgumentParameters.25511.8.2Invokingentity(SCF).25611.8.2.1Normalprocedure.25611.8.2.2Errorhandling.25611.8.3Respondingentity(SSF).25611.8.3.1Normalprocedure.256SIST EN 301 931-2 V1.1.2:2005
ETSIETSIEN301931-2V1.1.2(2001-09)811.8.3.2Errorhandling.25611.9Cancelprocedure.25711.9.1Generaldescription.25711.9.1.1Parameters.25711.9.1.1.1ArgumentParameters.
...