ETSI EN 301 140-5 V1.1.3 (1999-11)

Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 5: Distributed Functional Plane (DFP) [ITU-T Recommendation Q.1224 (1997), modified]

DEN/SPS-03038-5

Inteligentno omrežje (IN) - Drugi nabor zmožnosti inteligentnega omrežja (CS2) - Aplikacijski protokol inteligentnega omrežja (INAP) - 5. del: Porazdeljena funkcijska ravnina (DFP) - (preoblikovano priporočilo ITU-T Q.1224 (1997))

General Information

• Status: Published
• Publication Date: 09-Nov-1999
• Technical Committee: SPS 3 4 - Intelligent Network
• Current Stage: 12 - Completion
• Due Date: 19-Nov-1999
• Completion Date: 10-Nov-1999
• Ref Project: SIST EN 301 140-5:2001 - Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 5: Distributed Functional Plane (DFP) [ITU-T Recommendation Q.1224 (1997), modified]

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.D]GHOMHQDIntelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 5: Distributed Functional Plane (DFP) [ITU-T Recommendation Q.1224 (1997), modified]33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 140-5 Version 1.1.3SIST EN 301 140-5:2001en01-september-2001SIST EN 301 140-5:2001SLOVENSKI
STANDARD



SIST EN 301 140-5:2001



ETSIEN301140-5V1.1.3(1999-11)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part5:DistributedFunctionalPlane(DFP)[ITU-TRecommendationQ.1224(1997),modified]SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)2ReferenceDEN/SPS-03038-5(ak190ie0.PDF)KeywordsIN,CS2,INAPETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/[e-mail]ETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]Ideliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshouldbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute1999.Allrightsreserved.SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.73Abbreviations.84SSF/CCFmodel.84.1General.84.2Basiccallmanager(BCM).84.2.1BCSM.84.2.2CS2BCSMdescription.84.2.2.1OriginatingBCSMforINCS2.94.2.2.1.1O_Null.104.2.2.1.2Authorize_Origination_Attempt.124.2.2.1.3Collect_Information.134.2.2.1.4Analyse_Information.154.2.2.1.5SelectRoute.174.2.2.1.6Authorize_Call_Setup.194.2.2.1.7Send_Call.194.2.2.1.8O_Alerting.214.2.2.1.9O_Active.224.2.2.1.10O_Suspended.234.2.2.1.11O_Exception.244.2.2.2TerminatingBCSMforINCS2.244.2.2.2.1T_Null.264.2.2.2.2Authorize_Termination_Attempt.264.2.2.2.3SelectFacility.274.2.2.2.4PresentCall.274.2.2.2.5T_Alerting.284.2.2.2.6T_Active.294.2.2.2.7T_Suspended.304.2.2.2.8T_Exception.304.2.3BCSMResumePointsandBCSMTransitionsintheINCS2CallModel.314.2.4BCSMindicationsfortheCS2CallModel.374.2.4.1User-O_BCSMAccessSignallingIndications(Category1).374.2.4.2T_BCSM-UserAccessSignallingIndications(Category2).404.2.4.3IntraLocalExchangeBCSMIndications(Category3).414.2.5BCSMdetectionpoints.444.2.6DPCriteria.444.2.7Triggertypesandtriggerprecedence.514.2.8DPprocessing.514.2.9Out-ChannelCall-RelatedUserInteraction(OCCRUI).524.3IN-switchingmanager(IN-SM).524.3.1IN-switchingstatemodel(IN-SSM).524.3.2IN-SMcorecapabilitiesforCallPartyHandling.524.3.3TheConnectionViewState(CVS)Approach.524.3.4Thehybridapproach.524.3.5IN-SSMEDPs.534.3.6SSFresourcecontrol.534.3.6.1SSFResourceControlforannouncementsanddigitcollection.534.4Featureinteractionsmanager(FIM)/callmanager(CM).534.5RelationshipofSSF/CCFmodelcomponents.534.6RelationshipofSSF/CCFtoSCF.53SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)45SpecializedResourceFunction(SRF)model.536ServiceControlFunction(SCF)model.537ServiceDataFunction(SDF)model.538CallUnrelatedServiceFunction(CUSF)model.538.1General.538.2Basicnon-callmanager(BNCM).548.2.1BCUSM.548.2.2BCUSMdescriptionforCS2.548.2.3TransitionforBCUSM.548.2.4BCUSMDPcriteria.548.2.5Call-UnrelatedUserInteraction(CUUI).548.2.5.1Firstcase:theCUUIinformationisconsideredasa"notificationpreviouslyrequestedbytheSCF".558.2.5.2Secondcase:theCUUIinformationisadditional,optionalinformation.558.2.5.3Synthesis.568.3DescriptionofRelationshipModel.569ServiceManagementFunction(SMF)Model.5610Mappingoftheglobalfunctionalplanetothedistributedfunctionalplane.5611Informationflowdiagramsanddistributedservicelogic.5712RelationshipsbetweenFEs.57AnnexA(normative):ApplicabilityofannexesandappendixesofITU-TRecommendationQ.1224.58AnnexB(informative):ChargingscenariossupportedbycoreINAP.59B.1Introduction.59B.2Terminology.59B.3Chargingscenarios.60B.3.1ScenarioA:ApplicationoftheBasicNetworkChargingFunction(BNCF).60B.3.2ScenarioB:INchargingcompletelyintheIN.61B.4On-lineChargeInformationprovisiontotheuseraccess(ONC).62B.5FrameworkforthechargingoperationsinINAP.63B.6Interworkingwithotherchargedeterminationpoints.64AnnexC(informative):ImplicitDisarmingrules.66Bibliography.69History.71SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeSignallingProtocolsandSwitching(SPS).ThepresentdocumentisbasedonITU-TRecommendationQ.1224[6].Itprovidesmajormodificationsandfurtherrequirementstothisbasedocument.Thepresentdocumentispart5ofamulti-partstandardcoveringIntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2)asdescribedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforServiceSwitchingFunction(SSF)";Part4:"AbstractTestSuite(ATS)specificationandPartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaforServiceSwitchingFunction(SSF)";Part5:"DistributedFunctionalPlane(DFP)[ITU-TRecommendationQ.1224(1997),modified]".NationaltranspositiondatesDateofadoptionofthisEN:5November1999DateoflatestannouncementofthisEN(doa):29February2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2000DateofwithdrawalofanyconflictingNationalStandard(dow):31August2000SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)61ScopeThepresentdocumentisbasedonITU-TRecommendationQ.1224[6].Itprovidesmajormodificationsandfurtherrequirementstothisbasedocument.ThescopeoftheINDistributedFunctionalPlane(DFP)architectureforINcapabilityset2(CS2)isdrivenbytheservicerequirementsofdesiredINCS2services,andconstrainedbythecapabilitiesoftheembeddedbaseofevolvablenetworktechnology.ThescopeoffunctionalityrequiredtosupportdesiredINCS2servicesincludesfunctionalitytoprovide:-enduseraccesstocall/serviceprocessing;-serviceinvocationandcontrol;-enduserinteractionwithservicecontrol;-servicemanagement;-CallPartyHandling;-internetworking;-security;-Out-ChannelCallRelatedUserInteraction;-Out-ChannelCallUnrelatedUserInteraction;-wirelessAccess;and-FeatureInteractions.Thescopeofeachoftheseaspectsisaddressedinclause2ofITU-TRecommendationQ.1224[6]andisendorsedbythepresentdocument.ThepresentdocumentfollowsthesamedocumentstructureasITU-TRecommendationQ.1224[6]forclause4onwardsandreferstotextinITU-TRecommendationQ.1224[6]whenthereisnodifferenceinthepresentdocumentcomparedtoITU-TRecommendationQ.1224[6].Iftherearechangestherelatedtextisincludedintherelevantclause.Clause1(General),clause2(ScopeofINdistributedfunctionalplaneforcapabilityset2)andclause3(DistributedfunctionalmodelforINCS2)inITU-TRecommendationQ.1224[6]areendorsedbythepresentdocument.ThefollowingcapabilitiessupportedinITU-TRecommendationQ.1224[6]areexcludedfromthepresentdocument:-TheHybridApproachfortheConnectionViewState;-TriggerDetectionPoint-NotificationfortheSSF/CCF-SCFinterface;-DPspecificINAPoperationsOnlyDPgenericINAPoperationsaresupportedbyETSICoreINAPCS2whichmeansthatfollowingDPspecificoperationssupportedinITU-TINCS2arenotpartofETSIINCS2:AnalysedInformation,AnalyseInformation,AuthorizeTermination,CollectedInformation,FacilitySelectedAndAvailable,OAbandon,OAnswer,OCalledPartyBusy,ODisconnect,OMidCall,ONoAnswer,OriginationAttempt,OriginationAttemptAuthorized,OSuspended,RouteSelectFailure,SelectFacility,SelectRoute,TAnswer,TBusy,TDisconnect,TMidCall,TNoAnswer,TerminationAttempt,TermAttemptAuthorizedandTsuspended.Supportedinformationflowsareinsubclause4.1.5ofEN301140-1[10].SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)72ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.•Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.•Foraspecificreference,subsequentrevisionsdonotapply.•Foranon-specificreference,thelatestversionapplies.•Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]EN300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".[2]EN300403-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[3]ITU-TRecommendationQ.762:"SignallingSystemNo.7;ISDNuserpartgeneralfunctionsofmessagesandsignals".[4]ITU-TRecommendationQ.763:"SignallingSystemNo.7;ISDNuserpartformatsandcodes".[5]ITU-TRecommendationQ.932:"DigitalSubscriberSignallingSystemNo.1(DSS1);GenericproceduresforthecontrolofISDNsupplementaryservices".[6]ITU-TRecommendationQ.1224:"DistributedfunctionalplaneforIntelligentNetworkCapabilitySet2".[7]ITU-TRecommendationQ.1228:"InterfaceITU-TRecommendationforintelligentnetworkCS2".[8]ITU-TRecommendationQ.1290:"Glossaryoftermsusedinthedefinitionofintelligentnetworks".[9]ITU-TRecommendationQ.1218:"InterfaceRecommendationforintelligentnetworkCS-1".[10]EN301140-1:"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part1:Protocolspecification".[11]ITU-TRecommendationQ.1204:"Intelligentnetworkdistributedfunctionalplanearchitecture".[12]ITU-TRecommendationQ.1214:"DistributedfunctionalplaneforintelligentnetworkCS1".[13]ITU-TRecommendationE.164:"Theinternationalpublictelecommunicationnumberingplan".[14]ES201296:"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP);Signallingaspectsofcharging".SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)83AbbreviationsForthepurposesofthepresentdocument,theabbreviationsgiveninEN301140-1[10]andthefollowingapply:BRIBasicRateInterface(2x64kbit/s+1x16kbit/s)CPConnectionPointCPGCallProgressmessageDFPDistributedFunctionalPlaneDPDetectionPointIFInformationFlowPICPointinCallSIBServiceIndependentBuildingBoxSPIDServiceProfileIDentifier4SSF/CCFmodel4.1GeneralTextinsubclause4.1inITU-TRecommendationQ.1224[6]shallbefollowed.4.2Basiccallmanager(BCM)Textinsubclause4.2inITU-TRecommendationQ.1224[6]shallbefollowed.4.2.1BCSMTextinsubclause4.2.1inITU-TRecommendationQ.1224[6]shallbefollowed.4.2.2CS2BCSMdescriptionTheBCSMforINCS2describedinthissubclauseisbasedontheoverallBCSMinannexAofITU-TRecommendationQ.1204[11]andITU-TRecommendationQ.1214[12],refinedasapplicabletoINCS2.Itreflectsthefunctionalseparationbetweentheoriginatingandterminatingportionsofcallsasillustratedinfigures4.1and4.2.ThesefiguresshowanoriginatinghalfBCSMandaterminatinghalfBCSM,eachofwhichismanagedbyafunctionallyseparateBCMintheSSF/CCF.ThedescriptionisastartingpointtoidentifytheaspectsoftheBCSMthatarevisibletoINservicelogicinstances,andthenatureoftheinformationflowsbetweentheSSF/CCFandSCF(seeclause12).Inthefollowingdescriptions,thePICsarerelatedatahighleveltoEN300403-1[2]ISDNcallstates.ThisisnotintendedtobeadetailedformaldefinitionoftherelationbetweenthePICsandEN300403-1[2]ISDNcallstates,butisintendedasapointofreferencetouseinunderstandingthePICs.Inparticular,thereareanumberofpossiblewaysinwhichtheEN300403-1[2]callstatesmaybetraversedincertainsituationswhicharenotconsideredbelow.ToenableindependencebetweenservicesofferedduringonecallsessionwhenthePICsmaybetraversedseveraltimes,itisnecessary-ateachPIC-tomaintainavailableaspecificsetofdatauntilthecalling(controlling)userreleasesandtoensurethatsoftwareresourcesarereturnedtoacoherentstatuswhencallprocessingpassesthroughthePICs.ForeachPIC,aninitiallistofBCSMinformationthatshallbemaintained,ifavailable,isgiven.InformationthatisavailableatallPICsisgivenatthebeginningoftheO-andT-BCSMdescriptions.TheinformationthatissenttotheSCFatagiventriggerdetectionpointisasubsetoftheinformationdescribedhere.OtherinformationmaybeavailableatagivenPICthatisnotusedbyprocessingatthePICorisonlyusedbyunderlyingcallprocessing.InordertomaintainuniquenessofDPnamesbetweentheoriginatingandterminatinghalfBCSMs,"O"and"T"isprefixedtocertainoriginatingandterminatingDPnames,respectively.SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)9Foreaseofreference,theDPsassociatedwiththeBCSMtransitionimpliedbyeachentryandexiteventforeachPICarelistedalongwiththePICdescriptions.ThesemanticsforAbandonandDisconnectDPneedsfurtherclarification.SomemisalignmentsinsidePart1andbetweenPart1andPart5havebeendetected.ItisalsoallowedtoreportDisconnectDPduringtheWfEoU(WFI),andWfEoTC(WFI)userinteractionsstates.4.2.2.1OriginatingBCSMforINCS2TheoriginatinghalfoftheBCSMcorrespondstothatportionoftheBCSMassociatedwiththeoriginatingparty(seefigure4.1).Analyse_InformationO_AbandonO_NullAuthorize_Origination_AttemptO_ExceptionCollect_InformationOrigination_Attempt_AuthorizedRoute_Select_FailureCollected_Informationcollect_timeout,invalid_information,collect_info_failureinvalid_informationAnalysed_Informationroute_busyOrigination_Attemptorigination_deniedSelect_RouteAuthorize_Call_Setupauthorization_route_failureSend_Callroute_failureO_Re-answerO_AnswerO_Mid_CallO_No_AnswerO_Called_Party_BusyO_ActiveO_SuspendedO_active_failureO_suspend_failurereconnectO_SuspendO_Mid_CallO_AlertingCallingPartyCalledPartyO_Term_SeizedO_Mid_CallO_Mid_CallO_DisconnectFigure4.1:OriginatingBCSMforCS2SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)10ThefollowinginformationisavailableatallPICsintheO-BCSM:-CallingPartyCategory-seeITU-TRecommendationQ.762[3]CallingParty'sCategorysignallinginformation.-SRF/SSFcapabilities-seeITU-TRecommendationQ.1290[8].Usedtodecideifanassistofhand-offprocedureistobeused.-CallGappingEncountered-seeITU-TRecommendationQ.1290[8].-TerminalType-seeITU-TRecommendationQ.1290[8].TheSCFusesthistodeterminethemostappropriateformofuser-interactiontouse(e.g.in-bandannouncements).Thisinformationisonlyavailableatoriginatingorterminatinglocalexchanges.-LocationNumber-seeITU-TRecommendationQ.762[3]LocationNumbersignallinginformation.Usedifthecallingpartyisamobilesubscriber.-ISDNAccessRelatedInformation:-SeeITU-TRecommendationQ.762[3]AccessTransportParameter.-OriginalCalledPartyID-seeITU-TRecommendationQ.762[3]OriginalCalledPartyNumberelement.ThisIDreferstothecasewherethecallisdiverted.-RedirectingPartyID-seeITU-TRecommendationQ.762[3]RedirectingPartyIDelement.ThisIDreferstothecasewherethecallisdiverted.-RedirectionInformation-seeITU-TRecommendationQ.762[3]RedirectionInformationelement.Thisinformationreferstothecasewherethecallisdiverted.-AdditionalCallingPartyNumber-seeITU-TRecommendationQ.762[3]GenericNumberelement.-ForwardGVNS-seeITU-TRecommendationQ.762[3]ForwardGVNSelement.-ThedescriptionforeachofthePICsintheoriginatinghalfoftheBCSMaredescribedbelow:NOTE:SeeBCSMIndicationsofsubclause4.2.4formoreinformationconcerningPICs.4.2.2.1.1O_NullEntryevent:Disconnectandclearingofapreviouscall(DPs:O_DisconnectandO_Abandon),ordefaulthandlingofexceptionsbySSF/CCFcompleted.Functions:Interface(line/trunk)isidled(nocallexists,nocallreferenceexists,etc.).Supervisionisbeingprovided.Informationavailable:AfterdetectingtheOriginationAttemptevent,itisassumedthattheSSF/CCFhasthefollowinginformationavailableassociatedwiththeoriginatingcallportion,withrestrictionsasnoted.IftheSSF/CCFdeterminesthattheoriginationisdenied,thecauseofthefailedauthorizationisalsoknown.-BearerCapability-seeITU-TRecommendationQ.762[3]UserServiceInformationandEN300403-1[2]BearerCapabilityinformationelement.-CallingPartyNumber-seeITU-TRecommendationQ.762[3]CallingPartyNumbersignallinginformation.ThisinformationisavailableattheSSF/CCFforanon-ISDNlineandmaybeavailableforSS7trunks,butisnotavailablefromtrunkssupportedbyconventionalsignallingorprivate-facilitytrunks.ForaDSS1interface,thisisdeterminedbytheinformationprovidedintheSETUPmessageorbythedefaultnumberassignedtothecaller(seeISDNSETUPinformationbelow).-SRFAvailable-seeITU-TRecommendationQ.1290[8].-ServiceProfileIdentifier(SPID)-seeITU-TRecommendationQ.932[5],annexA.ThisinformationmaybeavailableattheSSF/CCFifthecallingpartyisservedbyaBRIinterfaceonthisSSF/CCF.-CalledPartyNumber-seeITU-TRecommendationQ.762[3]Calledpartynumbersignallinginformation.Usedtoidentifythecalledpartyintheforwarddirection.AvailableonlyfortrunksorISDNlines.-Transitnetworkselection-seeITU-TRecommendationQ.763[4]Transitnetworkselectionparameter.Thisparameter,ifpresent,identifiestheCarrierIdentificationCodeandtheCircuitCode.SIST EN 301 140-5:2001



ETSIETSIEN301140-5V1.1.3(1999-11)11-ClassofService-seeITU-TRecommendationQ.1290[8].-CallingPartyBusinessGroupID(BGID)-seeITU-TRecommendationQ.1290[8]BusinessGroupID.Thisinformationisavailableforanon-ISDNline,ISDNinterface,private-facilitytrunkgroup,orpossiblyanSS7trunkwhenthecallerisamemberofaBusinessGroup.-CallingFacilityGroup-seeITU-TRecommendationQ.1290[8].AvailableonconventionalorSS7trunks.-CallingFacilityGroupMember-seeITU-TRecommendationQ.1290[8].AvailableonconventionalorSS7trunks.-TravellingClassMark-seeITU-TRecommendationQ.1290[8].-FeatureCode-seeITU-TRecommendationQ.762[3]FeatureCodeSignallingInformationwherethisparameterisdefinedfornationaluseonly.Available,ifused,forapartyservedbyanISDNinterfaceusingenblocsendingorforanSS7trunk.-AccessCode-seeITU-TRecommendationQ.1290[8].Available,ifused,forapartyservedbyanISDNinterfaceusingenblocsending.-OperatorServicesInformation-seeITU-TRecommendationQ.1290[8].ThisinformationelementisnotincludedinaSETUPmessagecontainingthekeypadinformationelement.-ISDNSETUPfeature-relatedinformation-seeEN300403-1[2].TheSSF/CCFreceivesaSETUPmessagefromaDSS1interfaceandthisSETUPmessagecanalsocontainthefollowinginformation:-ProgressIndicator-seeEN300403-1[2]Progressindicatorinformationelement.-KeypadFacility-seeEN300403-1[2]Keypadfacilityinformationelement.ThisinformationelementisnotexpectedinaSETUPmessagealsocontainingtheCalledpartynumber,Calledpartynumbersubaddress,Transitnetworkselection,orOperatorservicesinformationelements.-Featureactivation-seeITU-TRecommendationQ.932[5]Featureactivationinformationelement.-Callingpartynumber-seeEN300403-1[2]Callingpartynumberinformationelement.TheCalledpartynumberinformationelementissentwhenenblocsendingisusedandtheKeypadinformationelementisnotpresent.WhenthetypeofnumberandnumberingplanidentificationfieldwithintheCalledpartynumberinformationelementissetto"unknown,"theSSF/CCFtreatsthestringasifithasbeenreceivedwithinaKeypadinformationelement.Inthiscase,itisnotexpectedtobesentwiththetransitnetworkselectionorOperatorservicesinformationelements.-FacilityInformation-seeEN300403-1[2]Facilityinformationelement.ThisinformationelementmayidentifyUSIInformationorFacilityInformation.-Otherinformation,asdefinedbyITU-TRecommendationQ.932[5],GenericProceduresfortheControlofISDNSupplementaryServices,canbeincluded.SomeofthisinformationmaybeofinteresttotheSCF.-ISDNUserPartIAMfeaturerelatedinformation.TheIAMcanalsocontainthefollowinginformation(seeITU-TRecommendationsQ.762[3]and/orQ.763[4]):-Natureofconnectionindicators-seeITU-TRecommendationQ.763[4]NatureofConnectionIndicatorsparameter.-Forwardcallindicators-seeITU-TRecommendationQ.763[4]ForwardCallIndicatorsparameter.Thecaller'saccessisidentifiedasISDNornon-ISDN,andanindicationisgivenofwhetheranend-to-endSS7supportedconnectionisrequired.-Userserviceinformation-seeITU-TRecommendationQ.762[3].UserServiceInformationparameter.ForthepurposesofINCS
...