SIST EN 301 464 V1.1.1:2005

• Abstract:

  Description of interactions between ISDN NNI signalling and INAP CS2

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• 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 464 V1.1.1 (2000-12) - Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 interactions with the Intelligent Network Application Part (INAP); Part 1: Protocol specification [ITU-T Recommendation Q.1601 (1999), modified]

SIST EN 301 464 V1.1.1:2005 is the Slovenian adoption of ETSI EN 301 464 for Integrated Services Digital Network (ISDN) signalling. It specifies how Signalling System No.7 (SS7) ISDN User Part (ISUP) version 4 interacts with the Intelligent Network Application Part (INAP), with the focus on ISDN NNI signalling and INAP Capability Set 2 (CS2). In practice, it tells network operators and switch vendors how to map messages, control calls, and handle supplementary services when an IN service is triggered.

What does SIST EN 301 464 V1.1.1:2005 specify?

SIST EN 301 464 V1.1.1:2005 specifies the interaction between ISUP and INAP in an ISDN environment. It defines procedures for supporting IN services, adds ISUP protocol elements for IN-specific needs, and allows stepwise upgrading of ISUP functionality when the affected exchanges support it.

The document focuses on the case where the Service Switching Point (SSP) is at transitlevel. That matters because it can limit how some ISDN supplementary services behave. The standard also leaves DSS1 enhancements to other documents and points readers to the related interworking recommendations for other signalling systems.

The document is organized as a modified version of ITU-T Recommendation Q.1601, with updated references, protocol procedures, service-impact clauses, and an informative mapping annex.

• Clauses 1 and 2 cover scope and references.
• Clause 10 covers call-control procedures and message and parameter mappings.
• Clause 12 covers supplementary-service impacts and actions in the services switching point.
• Appendix I is integral to the document.
• Appendix II is informative and describes a network option.
• Appendix III is informative.
• Annex ZA is informative and maps the INAP callingPartyNumber parameter.

What are the key requirements of SIST EN 301 464 V1.1.1:2005?

SIST EN 301 464 V1.1.1:2005 is mainly about how an IN call is detected, how control is transferred between network functions, and how ISUP and INAP parameters are mapped. For implementers, the key point is that the standard is not only descriptive - it tells you which message carries which data and how the call should proceed.

Call setup, control transfer, and release

When an IAM arrives and the SSP recognizes an IN call, the SSP sends an InitialDP operation or a DP-specific operation to the SCF. If the IAM was segmented, the SSP waits for the remaining call-set-up information. In practice, exchanges must support trigger detection and be able to hold partial call data until the call can be completed.

For network-initiated suspend and resume, the SSF starts timer TSUS and waits for a RES or REL message. That means implementations need timer handling and release logic that matches the serviceInteractionIndicatorsTwoparameter behavior.

Mapping between INAP and ISUP

The standard defines mappings from InitiateCallAttempt to IAM and from Connect to IAM. DestinationRoutingAddress drives the called party number, while other fields such as carrier, locationNumber, bearerCapability, and serviceInteractionIndicatorsTwo map to specific ISUP parameters. This is the practical core of interworking: the IN side shapes the outgoing ISUP call set-up.

The document also states how optional parameters are treated and how default IAM indicators and TMR are set when needed. That matters because a missing INAP field can still require a valid ISUP default on the outgoing call.

Event reporting and digit collection

In the "notifyAndContinue" mode, the event is reported and normal call handling continues. In the "interrupted" mode, the SSF reports the event and waits for instructions from the SCF. For operators, that defines whether the call proceeds automatically or pauses for service logic.

When the SCP asks to collect further digits, the SSP collects the specified number and then sends EventReportBCSM or CollectedInformation. The collected digits are also used when constructing the called IN number parameter. That affects routing, charging, and any later service decision.

Supplementary services and optional network behavior

Table 19 identifies supplementary services that can be affected by IN services, including reverse charging. The standard also says that when "acceptCCSRequest" is indicated by the IN service logic, diagnostic fields and the CCNR Possible Indicator are passed transparently. In practice, supplementary-service handling must preserve these indicators across the network.

Annex ZA defines an optional national feature for the INAP callingPartyNumber parameter. Depending on the ScreeningIndicator, the outgoing ISUP may use CallingPartyNumber or GenericNumber. That option is only relevant where the network operators have a bilateral agreement.

What terms does SIST EN 301 464 V1.1.1:2005 define?

• Integrated Services Digital Network (ISDN) - the digital network environment in which the call control and supplementary services operate.
• Signalling System No.7 (SS7) - the signalling system used to carry the call-control and service-control messages.
• ISDN User Part (ISUP) - the SS7 part used for ISDN call signalling.
• Intelligent Network Application Part (INAP) - the protocol used to invoke and control IN services.
• Service Switching Point (SSP) - the switching node that detects the IN trigger and applies call-control actions.
• Service Switching Function (SSF) - the function that reports events to the SCF and follows the instructions returned.
• Service Control Function (SCF) - the control function that receives reports and issues IN service decisions.

Who uses SIST EN 301 464 V1.1.1:2005?

SIST EN 301 464 V1.1.1:2005 is used by telecom network operators, switch vendors, and IN platform implementers who need ISUP and INAP to work together on ISDN NNI signalling. It is also relevant for test labs and interoperability teams that verify message mapping, trigger handling, and supplementary-service behavior.

Typical users include:

• ISDN and SS7 network engineers
• exchange and softswitch vendors
• IN service designers
• SCF and SSP implementers
• interoperability and conformance test teams
• operators handling bilateral agreements for the Annex ZA network option

What changed in SIST EN 301 464 V1.1.1:2005 from the previous edition?

SIST EN 301 464 V1.1.1:2005 modifies ITU-T Recommendation Q.1601 (1999). The listed changes replace clauses 1 and 2 with the EN scope and references, update the reference list to ETSI and ITU-T companion parts, revise several call-control tables and subclauses in clause 10, update supplementary-service actions in clause 12, and add informative Annex ZA for calling party number mapping.

Which standards are used with SIST EN 301 464 V1.1.1:2005?

Reference	What it contributes
EN 301 140-5	INAP CS2 Distributed Functional Plane for the service model.
EN 300 356-1	ISUP version 4 basic services and related call control.
EN 300 356-3	CLIP supplementary service.
EN 300 356-4	CLIR supplementary service.
EN 300 356-5	COLP supplementary service.
EN 300 356-6	COLR supplementary service.
EN 300 356-10	SUB supplementary service.
EN 300 356-11	MCID supplementary service.
EN 300 356-14	ECT supplementary service.
EN 300 356-15	Diversion supplementary services.
EN 301 140-1	INAP CS2 protocol specification.
EN 300 403-1	DSS1 protocol for circuit-mode basic call control.

What does the SIST EN 301 464 V1.1.1:2005 document contain?

The document is table-heavy and procedure-driven. It contains call-control text for successful setup, normal release, suspend/resume, digit collection, user interactive dialogue, call gapping, service filtering, Continue, and Connect. It also contains parameter-mapping tables for IAM and INAP operations, including InitiateCallAttempt, Connect, SUS, RES, and EventReportBCSM-related flows.

It adds service-impact notes for supplementary services and transparency handling for specific indicators and diagnostics. Annex ZA provides the optional calling-party-number mapping logic for a national network option.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 interactions with the Intelligent Network Application Part (INAP); Part 1: Protocol specification [ITU-T Recommendation Q.1601 (1999), modified]33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 464 Version 1.1.1SIST EN 301 464 V1.1.1:2005en01-januar-2005SIST EN 301 464 V1.1.1:2005SLOVENSKI
STANDARD
ETSIEN301464V1.1.1(2000-12)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7(SS7);ISDNUserPart(ISUP)version4interactionswiththeIntelligentNetworkApplicationPart(INAP);Part1:Protocolspecification[ITU-TRecommendationQ.1601(1999),modified]SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-12)2ReferenceDEN/SPAN-01035KeywordsISDN,SS7,ISUP,IN,INAP,CS2ETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°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:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-12)3IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).NationaltranspositiondatesDateofadoptionofthisEN:8December2000DateoflatestannouncementofthisEN(doa):31March2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30September2001DateofwithdrawalofanyconflictingNationalStandard(dow):30September2001EndorsementnoticeTheelementsofITU-TRecommendationQ.1601(1999)apply,withthefollowingmodifications:NOTE:Newormodifiedtextisindicatedusingsidebars.Inaddition,underliningand/orstrike-outareusedtohighlightdetailedmodificationswherenecessary.SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-12)4ModificationstoITU-TRecommendationQ.1601Replaceclauses1and2(ScopeandReferences)withthefollowing:1ScopeThepresentdocumentspecifiestheinteractionbetweentheISUPandINAP.TheinteractionbetweenothersignallingsystemsandINAPcanbefoundbyconsultingtherelevantinterworkingrecommendationtotheISUPincombinationwiththeISUP/INAPinteractionrecommendation.ThepresentdocumentspecifiesproceduresinordertoprovideinteractionbetweenISUPandINAP,i.e.tosupportINservicesinanISDNenvironment.InadditionnewprotocolelementsfortheISUParedefinedinordertosatisfyINspecificrequirements.BasedontheprotocolinherentcompatibilitymechanismastepwiseupgradeoftheISUPfunctionalityispossible.However,thenewfunctionisonlyavailableforanINcall,ifsupportedinanyoftheaffectedexchanges.ThepresentdocumentonlyconsidersthecasewheretheSSPislocatedatatransitlevel.AsaconsequencethiscouldleadtolimitationsforISDNsupplementaryservices.ThepresentdocumentdoesnotspecifyenhancementstotheDSS1protocol,whichmaybeneededduetoadditionalISUPfunctionsorINrequirements,respectively.Themainsubjectsofthepresentdocumentarethefollowing:-descriptionofspecificcallcontrolfunctionsforINcalls;-impactsontheISUPbasiccallandtheISDNsupplementaryservicesforINcalls;-enhancementoftheISUPprotocolduetoINspecificrequirements.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301140-5:"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part5:DistributedFunctionalPlane(DFP)[ITU-TRecommendationQ.1224(1997),modified]".[2]ETSIEN300356-1:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part1:Basicservices[ITU-TRecommendationsQ.761toQ.764(2000)modified]".[3]ETSIEN300356-3:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part3:CallingLineIdentificationPresentation(CLIP)supplementaryservice[ITU-TRecommendationQ.731,clause3(1993)modified]".SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-12)5[4]ETSIEN300356-4:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part4:CallingLineIdentificationRestriction(CLIR)supplementaryservice[ITU-TRecommendationQ.731,clause4(1993)modified]".[5]ETSIEN300356-5:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part5:ConnectedLineIdentificationPresentation(COLP)supplementaryservice[ITU-TRecommendationQ.731,clause5(1993)modified]".[6]ETSIEN300356-6:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part6:ConnectedLineIdentificationRestriction(COLR)supplementaryservice[ITU-TRecommendationQ.731,clause6(1993)modified]".[7]ETSIEN300356-10:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part10:Subaddressing(SUB)supplementaryservice[ITU-TRecommendationQ.731,clause8(1992)modified]".[8]ETSIEN300356-11:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part11:MaliciousCallIdentification(MCID)supplementaryservice[ITU-TRecommendationQ.731,clause7(1997)modified]".[9]ETSIEN300356-14:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part14:ExplicitCallTransfer(ECT)supplementaryservice[ITU-TRecommendationQ.732,clause7(1996)andimplementorsguide(1998)modified]".[10]ETSIEN300356-15:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part15:Diversionsupplementaryservices[ITU-TRecommendationQ.732,clauses2to5(2000)modified]".[11]ETSIEN301140-1:"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part1:Protocolspecification".[12]ETSIEN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".ThroughoutthetextofITU-TRecommendationQ.1601Replacereferencesasshownbelow.ReferenceinITU-TRecommendationQ.1601ModifiedreferenceITU-TRecommendationQ.1224ITU-TRecommendationQ.1224asmodifiedbyEN301140-5[1]ITU-TRecommendationQ.1228EN301140-1[11]ITU-TRecommendationQ.731ITU-TRecommendationQ.731asmodifiedbyEN300356,parts3,4,5,6,10and11[3]to[8]ITU-TRecommendationQ.732ITU-TRecommendationQ.732asmodifiedbyEN300356,parts14[9]and15[10]ITU-TRecommendationQ.763ITU-TRecommendationQ.763asmodifiedbyEN300356-1[2]ITU-TRecommendationQ.764ITU-TRecommendationQ.764asmodifiedbyEN300356-1[2]ITU-TRecommendationQ.931ITU-TRecommendationQ.931asmodifiedbyEN300403-1[12]SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-12)6Table2Amendthetableasshown:OperationInfluenceonISUPcallhandlingReferenceAnalyseInformattionForfurtherstudy(Note)CancelStatusReportRequestForfurtherstudy(Note)HoldCallInNetworkForfurtherstudy(Note)RequestCurrentStatusReportForfurtherstudy(Note)RequestEveryStatusChangeReportForfurtherstudy(Note)RequestFirstStatusMatchReportForfurtherstudy(Note)SelectFacilityForfurtherstudy(Note)SelectRouteForfurtherstudy(Note)Subclause10.1.1.1,Successfulcallset-upModifythefirstsentenceasfollows:"IfanIAMisreceivedinaSSPandthecallisrecognisedasINcall,i.e.bydetectingaDPasTDP-R(seesubclause10.1.3DetectionPointprocessing),anInitialDPoperationoraDPspecificoperationforaTDP-RissentfromtheSSFtotheSCF.IftheIAMhadbeensegmentedtheremainderofthecallset-upinformationisawaited(seesubclause10.1.1.1.7Simplesegmentation).Themappingofparametersisshowninthetablebelow."Table4Amendthetableasshown:ISUPmessageINAPoperationIAM(Note1)InitialDPCallingpartysubaddressIEcontainedinaccesstransportcallingPartySubaddressTable5Amendthetableasshown:INAPoperationISUPmessageConnect(Note1)IAMcallingPartyNumber(Note4)(seealsoAnnexZA)locationNumberLocationnumber(Note7)Table5,note3Replacereferenceto"[5],subclause3.3.16"with"[11],subclause18.29".SIST EN 301 464 V1.1.1:2005

ETSIETSIEN301464V1.1.1(2000-
...