SIST EN 301 140-5:2001

• Abstract:

  Core INAP for CS2 shall also reflect the Distributed Functional Plane (DFP), e.g. including the specification of BCSM, DP processing rules, FE modelling. The intention of this part of Core INAP for CS2 is, to endorse ITU-T Recommendation Q.1224 and to identify exceptions from Q.1224 which are valid for Core INAP for CS2. The service drivers and network aspects which are considered in order to determine the exceptions from Q.1224 are the same as described in the scope of part 1 for th eprotocol specification of core INAP for CS2, i.e. CTM, UPT, CTN, GVNS, Call Party Handling (CPH), Interworking of INAP with ISUP/DSS1. Specification of this part shall be done in close co-operation with NA 6 since modelling aspects are to be considered.

• Status: Published
• Publication Date: 31-Aug-2001
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Sep-2001
• Due Date: 01-Sep-2001
• Completion Date: 01-Sep-2001
• Ref Project: 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]

SIST EN 301 140-5:2001 is the Slovenski standard for Intelligent Network (IN) Intelligent Network Application Protocol (INAP) Capability Set 2 (CS2), Part 5: Distributed Functional Plane (DFP), based on ITU-T Recommendation Q.1224 (1997) and modified for Core INAP for CS2. It specifies the DFP model and the CS2 call-processing view that implementers use to align SSF/CCF behavior with IN service logic.

This part is aimed at people designing or validating INAP CS2 switching behavior, especially where call models, detection points, and service control need to match the DFP.

What does SIST EN 301 140-5:2001 specify?

SIST EN 301 140-5:2001 specifies the DFP for Core INAP CS2 and endorses the overall structure of ITU-T Recommendation Q.1224, while identifying exceptions valid for Core INAP CS2. In practice, it tells an implementer how the CS2 call models, functional entities, and information flows are organized and which Q.1224 capabilities are not part of ETSI Core INAP CS2.

The scope covers end-user access to call and service processing, service invocation and control, end-user interaction with service control, service management, Call Party Handling, interworking, security, Out-Channel Call Related User Interaction, Out-Channel Call Unrelated User Interaction, wireless Access, and Feature Interactions.

Annex	What it covers
Annex A	Applicability of annexes and appendixes of ITU-T Recommendation Q.1224
Annex B	Charging scenarios supported by core INAP
Annex C	Implicit disarming rules

The document is organized into clauses on SSF/CCF, SRF, SCF, SDF, CUSF, SMF, mapping of the global functional plane to the distributed functional plane, information flow diagrams and distributed service logic, and relationships between functional entities.

What are the key requirements of SIST EN 301 140-5:2001?

SIST EN 301 140-5:2001 follows Q.1224 for the DFP model, but it defines several CS2-specific exclusions and modeling choices that matter to switch behavior and interoperability.

Core model and exclusions

The standard endorses the BCSM-based SSF/CCF model and the originating and terminating call halves, including Basic Call Manager behavior, PICs, resume points, and detection points. It explicitly excludes the Hybrid Approach for the Connection View State, Trigger Detection Point-Notification for the SSF/CCF-SCF interface, and DP-specific INAP operations.

That matters because an implementation must not rely on those excluded capabilities when claiming ETSI Core INAP CS2 support.

Detection points and trigger handling

SIST EN 301 140-5:2001 states that only DP generic INAP operations are supported, and it defines DP criteria such as trigger assigned, class of service, specific B-channel identifier, digit strings, feature codes, prefixes, access codes, calling and called party number strings, nature of address, bearer capability, feature activation or indication, facility information, cause, and specific value of USI Service Indicator.

In practice, these criteria determine when the SSF reports a detection point to the SCF, so they drive service triggers, routing decisions, and how much call information is available before analysis is complete.

Call model behavior

The document defines detailed originating and terminating BCSM paths, including O_Null, Collect_Information, Analyse_Information, Select_Route, Send_Call, O_Alerting, O_Active, O_Suspended, and the matching terminating states such as T_Null, Select_Facility, Present_Call, T_Alerting, T_Active, and T_Suspended. It also explains the events that move the call between these points, such as call acceptance, busy, no answer, suspension, re-answer, and disconnect.

This matters because implementers must align signaling, timers, and state transitions with the model used by IN service logic.

Information flows and exceptions

The standard describes what information is available at each PIC and how the originating and terminating BCSMs exchange indications inside one switch. It also defines exception handling, where the SSF/CCF closes relationships, reports errors to the SCF when needed, and releases resources cleanly.

That gives a practical rule for failure handling: resources and call-control relationships must be recovered consistently, even when a call aborts or a service interaction fails.

What terms does SIST EN 301 140-5:2001 define?

• DFP - Distributed Functional Plane - the architectural view that distributes IN functions across network entities.
• BCSM - Basic Call State Model - the call-state model used to describe originating and terminating call handling.
• SSF/CCF - Service Switching Function / Call Control Function - the switching-side functions that detect events and control call progress.
• SCF - Service Control Function - the function that provides service logic decisions to the switch.
• PIC - Point in Call - a stable step in the call model where specific information and actions apply.
• DP - Detection Point - a place where the switch can report an event or trigger service logic.
• IN-SM - IN-switching manager - the switching manager model used in the DFP description.
• CUSF - Call Unrelated Service Function - the functional model for service handling that is not tied to a call.

Who uses SIST EN 301 140-5:2001?

Telecom switch vendors, INAP implementers, and network architects use SIST EN 301 140-5:2001 to design CS2 call control and service-trigger behavior. Test engineers and conformance teams use it to verify BCSM transitions, detection points, and signaling effects at originating and terminating call legs. Service providers and quality managers use it to check whether a network supports the intended IN CS2 service behavior, including call handling, interaction, and charging-related scenarios.

What changed in SIST EN 301 140-5:2001 from the previous edition?

SIST EN 301 140-5:2001 is based on ITU-T Recommendation Q.1224 (1997), modified. The foreword says it provides major modifications and further requirements to that base document, and the scope identifies CS2-specific exceptions to Q.1224.

Which standards are used with SIST EN 301 140-5:2001?

SIST EN 301 140-5:2001 references EN 301 140-1 for Core INAP CS2 protocol specification and the list of abbreviations, and EN 300 403-1 for DSS1 protocol and call-state references. It also relies on ITU-T Q.1204 and Q.1214 for the DFP architecture and CS1 DFP background, ITU-T Q.1228 for the IN CS2 interface, and ITU-T Q.1224 as the base DFP recommendation.

Other named references support specific call-data and numbering concepts: ITU-T Q.762 and Q.763 for ISUP message and parameter definitions, ITU-T Q.932 for DSS1 supplementary-service procedures, ITU-T E.164 for numbering, and ES 201 296 for ISUP charging aspects.

What does the SIST EN 301 140-5:2001 document contain?

SIST EN 301 140-5:2001 contains detailed model descriptions, transition diagrams, tables of BCSM transitions, and the signaling indications that connect user-side and network-side behavior. It also includes clause-by-clause descriptions of originating and terminating call handling, detection point criteria, trigger precedence, and relationships between functional entities.

Annex B adds charging scenarios supported by core INAP, including the framework for charging operations and interworking with other charge-determination points. Annex C gives implicit disarming rules, which are relevant when trigger state must be cleared during call processing.

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
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.ForthepurposesofINCS2,thisparameteridentifiesthecallascircuit-mode/speech,circuit-mode/3,1kHzaudio,circuit-mode/unrestricteddigitalinformation(64kbps),orcircuit-mode/restricteddigitalinformation.-GenericNumber-seeITU-TRecommendationQ.762[3]Genericnumberparameter.MorethanonegenericnumberparametermaybepresentwithinagivenIAM.SIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)12-Genericname-seeITU-TRecommendationQ.1290[8].-Carrierselection-seeITU-TRecommendationQ.1290[8].-Genericdigits-seeITU-TRecommendationQ.762[3].Maycontainatravellingclassmark(networkoperatorspecific).-OtherparametersmaybeincludedintheIAM.Theseparametersmaybeincludedbecauseoffeaturesprovidedbyotherswitchesintheconnection(e.g.informationrelatingtothecallbeingforwarded).-Anyinformationrelatingtoswitch-basedfeaturesthathavealreadybeeninvokedforthecallwillalsobeavailable.Exitevent:-Indicationofdesiretoplaceoutgoingcall(e.g.off-hook,EN300403-1[2]SETUPmessage,ISDN-UPIAMmessage)(DP:Origination_Attempt).-ThefollowingexceptionexiteventsareapplicabletotheO_NullPIC.ForthisPIC,ifthecallencountersoneoftheseexceptionsduringO_NullPICprocessing,theexceptioneventisnotvisiblebecausethereisnocorrespondingDP.-TheO_Abandonoccurswhenthecallingpartydisconnects.Forexample,thiseventcanresultfromoneofthefollowing:-theSSF/CCFreceivesanon-hookindicationfromacallerservedbyanon-ISDNline,followingswitchhookflashtiming;-theSSF/CCFreceivesacallclearingmessagefromacallerservedbyanISDNinterface;-theSSF/CCFreceivesadisconnectindicationfromaconventionaltrunkorprivatefacilitytrunk;-SSFreceivesaReleaseMessagefromanSS7trunk.CorrespondingEN300403-1[2]callstate:O_Null4.2.2.1.2Authorize_Origination_AttemptEntryevent:Anindicationisavailablethattheoriginatingterminalneedstobeauthorized.(DP:Origination_Attempt).Functions:-Theoriginatingterminalrightsshouldbecheckedusingthecallingparty'sidentityandserviceprofile.Theauthority/abilityofthepartytoplacethecallwithgivenproperties(e.g.bearercapability,linerestrictions)isverified.Thetypesofauthorizationtobeperformedmayvaryfordifferenttypesoforiginatingresources(e.g.forlinesvs.trunks).-OtherfeatureswhichmightberequiredduringthisPICarenotdescribedintheINCS2BSCM.Informationavailable:AfterdetectingtheOrigination_Attempt_Authorizedevent,itisassumedthattheSSPhasthesameinformationavailableassociatedwiththeoriginatingcallportionasitdidafterdetectingtheOrigination_AttempteventintheO_NullPIC.IftheSSPdeterminesthattheoriginationisdenied,thecauseofthefailedauthorizationisalsoknown.Exitevent:-Anindicationisreceivedthattheauthorizationissuccessful.TheO_BCSMmovestotheCollect_InformationPIC(DP:Origination_Attempt_Authorized).-Adisconnectionindicationisreceivedfromtheoriginatingparty(DP:O_Abandon).-Anindicationisreceivedthatthecalloriginationisdenied.TheO_BCSMmovestotheO_ExceptionPIC.SIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)134.2.2.1.3Collect_InformationEntryevent:Authority/abilitytoplaceoutgoingcallverified.(DP:Origination_Attempt_Authorized).Functions:-Initialinformationpackage/diallingstring(e.g.servicecodes,prefixes,dialledaddressdigits)beingcollectedfromoriginatingparty.Informationbeingexaminedaccordingtodiallingplantodetermineendofcollection.Nofurtheractionmayberequiredifanenblocsignallingmethodisinuse(e.g.anISDNuserusingenblocsignalling,anincomingSS7trunk).-TheSSF/CCFshallbeabletosupportsubsequentdigitcollectionaccordingtotriggercriteriaassignedbeforesendingthequery.Forexampleifafeaturecode(e.g.*64)isentered,theSSF/CCFmay:-collectdigitsaccordingtothenormaldiallingplan;or-collectavariablenumberofdigits.Informationavailable:AftertheSSF/CCFdeterminesthatinformationcollectioniscomplete,itisassumedthattheSSF/CCFhasthefollowinginformationavailableassociatedwiththeoriginatingcallportion:-CallingPartyNumber,CallingPartyBGID,ClassofService,BearerCapability,CallingFacilityGroup,CallingFacilityGroupMember,ServiceProfileIdentifier,otherfeature-relatedinformation,FacilityInformation.ThisinformationisavailableforeachaccesstypeundertheconditionsdefinedintheO_NullPIC.-CollectedInformation-Asdescribedbelow.Fromanon-ISDNlineorDSS1interface,thecollectedinformationconsistsofoneormoreofthefollowing:-AccessCodeswithinaCustomizedDiallingPlan(CDP)-seeITU-TRecommendationQ.1290[8].TheCustomizedDiallingPlan(CDP)inforcemayspecifythatafteragivenaccesscodeisdialled,moredigitsaretobecollectedaccordingtothe"normaldiallingplan,"i.e.thediallingplaninforce.Inthiscase,AccessCodeandCollectedAddressInformationareknown.IftheCDPinforcespecifiesthatafteragivenaccesscodeisdialled,avariablenumberofdigitsaretobecollected,thenAccessCodeandCollectedDigitsareknown.-FeatureCode-seeITU-TRecommendationQ.762[3]FeatureCodeSignallingInformationwherethisparameterisdefinedfornationaluseonly.Ifthenumberingplaninforcespecifiesthatafteragivenfeaturecodeisdialled,moredigitsaretobecollectedaccordingtothe"normaldiallingplan",thenFeatureCodeandCollectedAddressInformationareknown.Ifthediallingplaninforcespecifiesthatafteragivenfeaturecodeisdialled,avariablenumberofdigitsaretobecollected,thenFeatureCodeandCollectedDigitsareknown.Theserviceassociatedwiththefeaturecodeisdependentupontheusersserviceprofile.-FacilityCode-seeITU-TRecommendationQ.1290[8].Thisinformationmaybeprovidedifandwhenfacilityselectiveservicesignallingissupported.-FeatureActivation-seeITU-TRecommendationQ.932[5]FeatureActivationinformationelement.IftheCDPinforcespecifiesthatafteragivenfeatureactivatorisreceived,moredigitsaretobecollectedaccordingtothenumberingplan,thenFeatureActivationIndicatorandCollectedAddressInformationareknown.IftheCDPinforcespecifiesthatafteragivenfeatureactivatorisreceived,avariablenumberofdigitsaretobecollected,thenFeatureActivationIndicatorandCollectedDigitsareknown.-Prefix-seeITU-TRecommendationQ.1290[8].-CarrierAccessCode/CarrierIdentificationCode-seeITU-TRecommendationQ.1290[8].ThecallermaydialaCarrierAccessCode(CAC)(e.g.a10XXXor101XXXXforuseonthiscall).WhenthecallerisservedbyanISDNinterface,aCarrierIdentificationCode,i.e.XXXorXXXX,maybereceivedbytheSSF/CCFwithinthetransitnetworkselectioninformationelementoftheISDNSETUPmessage.-CollectedAddressInformation-seeITU-TRecommendationQ.1290[8].Availableasperthenumberingplan.-NumberingPlanIndicator-seeITU-TRecommendationQ.762[3]NumberingPlanIndicatorsignallinginformation.SIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)14-CollectedDigits-seeITU-TRecommendationQ.1290[8].ThenumberingplaninforcemayspecifythatafteragivenFeatureActivation,FeatureCode,orAccessCodewithinaCDPisdialled,avariablenumberofdigitsaretobecollectedusingnormalinter-digittiming.Inthiscase,thesecollecteddigitsarealsoknownatthistime.Fromaconventionaltrunkinterface,theCollectedInformationconsistsofoneormoreofthefollowing:-CollectedAddressInformation-asdefinedabovefornon-ISDNlineorDSS1interface.-CarrierIdentificationCode-seeITU-TRecommendationQ.1290[8].ThisisknownifMFsignallingisusedontheoriginatingtrunk(networkoperatorspecific).-NumberingPlanIndicator-seeITU-TRecommendationQ.762[3]NumberingPlanIndicatorsignallinginformation.TheaddressreceivedisexpectedtoconformtoITU-TRecommendationE.164[13].-Prefix-asdefinedabovefornon-ISDNlineorDSS1interface.-CarrierSelection-seeITU-TRecommendationQ.1290[8].ThisinformationisonlyprovidedwhenMFsignallingisusedontheoriginatingtrunk(networkoperatorspecific).-OriginatingLineInformation-seeITU-TRecommendationQ.1290[8].ThisinformationisonlyknownwhenMFsignallingisusedontheoriginatingtrunk(networkoperatorspecific).Inthiscase,theOriginatingLineInformationissentduringthesecondstageofoverlapoutpulsing.FromanSS7trunkinterface,theCollectedInformationconsistsoftheinformationprovidedintheISDNUserPartcalledpartynumberandtransitnetworkselectionparameters,andpossiblyaTravellingClassMarkandotherfeature-relatedinformationasdescribedaboveforcontentsoftheISDNUserPartIAMfeaturerelatedinformation.Fromaprivate-facilitytrunk,thecollectedinformationconsistsofoneormoreofthefollowing:-AccessCodewithinaCDP-asdefinedaboveforanon-ISDNline;-FeatureCode-asdefinedaboveforanon-ISDNline;-FacilityCode-asdefinedaboveforanon-ISDNline;-CollectedAddressInformation-asdefinedaboveforanon-ISDNline;-NumberingPlanIndicator-asdefinedaboveforanon-ISDNline;-Prefix-asdefinedaboveforanon-ISDNline;-CarrierAccessCode-asdefinedaboveforanon-ISDNline;-TravellingClassMark-ifprovidedinthegenericdigitsparameteroftheIAM(seeITU-TRecommendationQ.1290[8]);-FacilityRestrictionLevel-seeITU-TRecommendationQ.1290[8].Exitevents:-Availabilityofcompleteinitialinformationpackage/diallingstringfromoriginatingparty.(Thiseventmayhavealreadyoccurredinthecaseofenblocsignalling,inwhichcasethewaitingdurationinthisPICiszero.)(DP:Collected_Info).-ThefollowingexceptionexiteventsareapplicabletothisPIC:CollectTimeout,CollectInfoFailure,InvalidInformationandO_Abandon:-TheCollectTimeouteventisdetectedwhenenoughinformationtoprocessthecallwasnotreceivedbytheSSF/CCFbeforeanormalinterdigittimerexpires.ForanSS7trunk,thiseventcorrespondstotheIAMnotcontainingtheinformationnecessarytoprocessthecall.Inthiscasetheremaybenotiminginvolved(timingmaybeinvolvedforISUPoverlapsending).-TheCollectInfoFailureeventisdetectedwhentheSSF/CCFisunabletoperformtheinformationcollectionduetoalackofswitchresources(e.g.nodigitreceiversareavailable).SIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)15-TheInvalidinformationeventoccurswhentheinformationreceivedfromthecallerisnotvalid,forinstancetheinformationreceivedviolatesthediallingplaninforce.-O_Abandonevent,asdescribedintheO_NullPIC.Inthiscase,theeventisvisiblebecausethereisacorrespondingDP.Comment:Somedigitanalysisisrequiredtodeterminetheendofdialling.However,itisassumedthatthisanalysismaybemodelledasseparablefromtherestofdigitanalysis,whichoccursintheAnalyse_InformationPIC.Thereisnointentiontospecifyanimplementation.However,aswitchshouldexternallypresenttheseparableviewdescribedforclosednumberingplans(seenote1).InthecaseofISDNenblocsending,thereceiptofaSETUPmessagedetectedattheOrigination_Attempt_AuthorizedDPcausestheBCSMtopassthroughtheCollect_InformationPICtotheCollected_InformationDP,withoutfurtherprocessingintheAuthorized_Origination_AttemptPIC.NotethattheBCSMtransitionstoCollected_InformationDPwhentheinitialinformationpackage/diallingstringisreceivedfromthecallingparty-thisoccurswhenenoughinformationisreceivedtoproceedwithcallprocessing(e.g.asinthecaseofISDNoverlapsendingofMFoutpulsing).Specifically,forthedigitbydigitcollectioncase,iftheCollected_InformationDPisarmedasaTriggerdetectionPoint-Request(TDP-R),theSSFsendsaninitiallingDPrequest(i.e.InitialDPinformationflow)totheSCFwhenenoughisreceivedtodetermineiftheTDPcriteriaismet.ItsuspendsBCSMprocessingbutwillcollectfurtherdigits.Itisnetworkoperatorspecifictodeterminewhencompleteinformationisavailable(seenote2).NOTE1:ThisseparableviewisprovidedbysupportingdistinctDPs.TheCollected_InformationDPisusedafterdigitcollectionandtheAnalysed_InformationDPisusedaftertherestofthedigitanalysis.NOTE2:Insomenetworks,itmaybenotpossiblefortheCCF/SSFtodeterminewhenthecallednumberinformationiscomplete.Therefore,TDPcriteriaforCollected_InformationDPmaybemetinsuchnetworksbeforethecallednumberinformationiscomplete.CorrespondingEN300403-1[2]callstate:1.CallInitiatedand(optionally)2.OverlapSending.4.2.2.1.4Analyse_InformationEntryevent:Availabilityofcompleteinitialinformationpackage/diallingstringfromoriginatingparty(DP:collected_Information)orroutebusyeventreportedfromtheSelectRoutePIC.Function:Informationbeinganalysedand/ortranslatedaccordingtodiallingplantodetermineroutingaddressandcalltype(e.g.localexchangecall,transitexchangecall,internationalexchangecall).ThefollowingprovidesdetailsastowhenthenextRouteshouldbetriedundereachcondition.ParametersReceived:DestinationRoutingAddressResult:BusyorNoAnswerProcessingOrder:CDPNNoalternativeroutecanbeselectedbasedonasecondCDPN.ParametersReceived:RouteList,DestinationRoutingAddressResult:Norouteoutoflocalswitch(busy)ProcessingOrder:Route1,CDPNRoute2,CDPNRoute3,CDPNSIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)16ParametersReceived:RouteList,DestinationRoutingAddressResult:RoutebusyisfoundtobeataswitchotherthanlocalswitchProcesingOrder:Route1,CDPNNootherroutesneedbetriedsincethelocalrouteissuccessful,butabusyconditionwasencounteredelsewhere.ParametersReceived:RouteList,DestinationRoutingAddressResult:NoanswerreceivedProcessingOrder:Route1,CDPNNootherroutesneedbetriedsincetherouteissuccessful,butanoanswerconditionwasencountered.OnlyaftertheappropriateRouteshavebeentriedwillthecallmoveontotheO_Called_Party_BusyDP,O_No_AnswerDP,orRoute_Select_FailureDPasappropriate.OneoftheresultsofprocessinginthisPICisdeterminationofroutingaddress:i)calledpartynumberonly(calledpartynumberisservedbytheSSF);ii)calledpartynumberandrouteindex,wheretherouteindexisapointertoatrunkgrouptorouteanoutgoingcallattempton(calledpartynumberisservedbyanotherSSF);iii)calledpartynumberandrouteindex,wheretherouteindexisapointertoalistoftrunkgroupstorouteanoutgoingcallattempton(calledpartynumberisservedbyanotherSSF).Informationavailable:AftertheSSF/CCFdeterminestheinformationhasbeenanalysed,itisassumedthattheSSF/CCFhasthefollowinginformationavailableassociatedwiththeoriginatingcallportion:-CallingPartyNumber,CallingPartyBGID,ClassofService,BearerCapability,CallingFacilityGroup,CallingFacilityGroupMember,ServiceProfileIdentifier,FacilityInformationandotherfeature-relatedinformationThisinformationisavailableforeachaccesstypeundertheconditionsdefinedintheO_NullPIC.-AnalysisResults(oftheCollectedInformation)-asdescribedbelow.Fromanon-ISDNlineorDSS1interface,thisconsistsofoneormoreofthefollowing:-CalledPartyNumber-asperdiallingplan.-NumberingPlanIndicator-seeITU-TRecommendationQ.762[3]NumberingPlanIndicatorsignallinginformation.-TypeOfCall-seeITU-TRecommendationQ.1290[8].-Carrier-seeITU-TRecommendationQ.1290[8].-CarrierIdentificationCode-seeITU-TRecommendationQ.1290[8].AvailableforInternetworkcarriercalls.-CarrierSelection-seeITU-TRecommendationQ.1290[8].AvailableforInterServingAreaIDcarriercalls.SeeITU-TRecommendationQ.1218[9].-RouteList-seeITU-TRecommendationQ.1290[8].-CollectedInformation-AccessCodewithinaCDP,FeatureCode,FeatureActivation,Prefix,CarrierAccessCode/CarrierIdentificationCode,CollectedAddressInformation/Digits-asdescribedundertheCollect_InformationPIC.FromaconventionalorSS7trunkinterface,thisconsistsofoneormoreofthefollowing:-CalledPartyNumberandNumberingPlanIndicator(asdefinedabovefornon-ISDNlineorDSS1interface).-CarrierIdentification-availableforInterServingAreaIDcarriercalls.SeeITU-TRecommendationQ.1218[9].SIST EN 301 140-5:2001

ETSIETSIEN301140-5V1.1.3(1999-11)17-CarrierSelection-seeITU-TRecommendationQ.1290[8].AvailableforInterServingAreaIDcarriercalls.SeeITU-TRecommendationQ.1218[9].-OriginatingLineInformation-seeITU-TRecommendationQ.1290[8].AvailableforInterServingAreaIDcarriercalls.SeeITU-TRecommendationQ.1218[9].-RouteIndex-seeITU-TRecommendationQ.1290[8].AvailableifthiscalldoesnotterminateonthisSSF/CCF.-CollectedInformation-CollectedAddressInformation,Prefix,CarrierIdentificationCode,FeatureCode,FacilityCode-seedescriptionundertheCollect_InformationPIC
...