SIST EN 301 716 V7.3.1:2003

Digital cellular telecommunications system (Phase 2+) (GSM); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2 (GSM 03.66 version 7.3.1 Release 1998)

This GSM Technical Specification defines the stage two description of the Support of Mobile Number Portability between GSM networks in the same country. Upgrade to Version 7.1.0.

Digitalni celični telekomunikacijski sistem (faza 2+) – Podpora prenosljivosti mobilnih številk (MNP) – Tehnična realizacija – Stopnja 2 (GSM 03.66, različica 7.3.1, izdaja 1998)

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.50 - Global System for Mobile Communication (GSM)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI EN 301 716 V7.3.1 (2000-10) - Digital cellular telecommunications system (Phase 2+) (GSM); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2 (GSM 03.66 version 7.3.1 Release 1998)

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.UHQRVOMLYRVWLDigital cellular telecommunications system (Phase 2+) (GSM); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2 (GSM 03.66 version 7.3.1 Release 1998)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 301 716 Version 7.3.1SIST EN 301 716 V7.3.1:2003en01-december-2003SIST EN 301 716 V7.3.1:2003SLOVENSKI
STANDARD



SIST EN 301 716 V7.3.1:2003



ETSIEN301716V7.3.1(2000-10)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);SupportofMobileNumberPortability(MNP);TechnicalRealisation;Stage2(GSM03.66Version7.3.1Release1998)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)2(GSM03.66Version7.3.1Release1998)ReferenceDEN/SMG-030366Q7KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM),NumberPortabilityETSI650RoutedesLuciolesF-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 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)3(GSM03.66Version7.3.1Release1998)ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.84General.94.1Overview.94.2Compatibility.104.3CommonFunctionalityoftheMNP-SRF.105CommonArchitectureforcallsetup.13AnnexA(normative):INCall-RelatedTechnicalRealisation.15A.1Architecture.15A.1.1NetworkOptions.15A.1.2NoNPQueryrequired-Numberisnotsubjectforportability.15A.1.3NPQueryinNumberRangeHolderNetwork.16A.1.3.1TQoD-Numberisnotported.16A.1.3.2TQoD-Numberisported.17A.1.3.3QoHR-Numberisported.18A.1.4NPQueryinOriginatingNetwork.19A.1.4.1OQoD-Numberisnotported.19A.1.4.2OQoD–Numberisported.20A.2Informationflows.22A.3Functionalrequirementsofnetworkentities.28A.3.1FunctionalrequirementofGMSC.28A.3.1.1ProcedureMOBILE_NUMBER_PORTABILITY_IN_QoHR.28A.3.1.2ProcedureMOBILE_NUMBER_PORTABILITY_IN_TQoD.30A.3.2FunctionalrequirementofMSC.32A.3.2.1ProcedureMOBILE_NUMBER_PORTABILITY_IN_OQoD.32A.3.3FunctionalrequirementofNPDB.34A.3.3.1ProcessIDP_NPDB.34A.4Contentsofmessages.35A.4.1MessagesontheISUPinterface.35A.4.1.1IAM.35A.4.2MessagesontheMSC-NPDBinterface.35A.4.2.1INITIALDP.35A.4.2.2INITIALDPnegativeresponse.35A.4.2.3CONNECT.35A.4.2.4CONTINUE.35AnnexB(normative):HandlingofNon-CallRelatedSignalling.36B.1HandlingofNon-callRelatedSignalling.36B.1.1RouteingConventions.36B.1.2NetworkArchitecture.36B.2SignallingScenarios.38B.2.1Non-callRelatedSignallingMessageforaNon-portedNumber-IndirectRouteing.38B.2.2Non-callRelatedSignallingMessageforaPortedorNon-portedNumber-DirectRouteing.39B.2.3Non-callRelatedSignallingMessageforaPortedNumber-IndirectRouteing.40SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)4(GSM03.66Version7.3.1Release1998)B.3FunctionalRequirementsofNetworkEntities.41B.3.1ProcedureMNP_SRF_Non_Call_Related.41B.4SignallingScenarios(informative).43B.4.1DeliveryofSMStoaNon-portedNumber-DirectRouteing-MNP-SRFactsasSCCPRelay.43B.4.2DeliveryofSMStoaNon-portedNumber-DirectRouteing–MNP-SRFactsasHigher-levelRelay.44B.4.3DeliveryofSMStoaPortedNumber-IndirectRouteing.45B.4.4DeliveryofSMStoaPortedNumber–DirectRouteing.46B.4.5InternationalSORforaNon-portedNumber.47B.4.6SORforaPortedNumber-IndirectRouteing.48B.4.7AnyTimeInterrogationforaPortedNumber–IndirectRouteing.49B.4.8AnyTimeInterrogationforaPortedNumber–DirectRouteing.50B.4.9CCBSwheretheBusySubscriberisaPortedSubscriber–DirectRouteing.51AnnexC(normative):MNPSignallingRelayFunction-CallRelatedSignalling.52C.1HandlingofCallRelatedSignalling.52C.2FunctionalRequirementsofNetworkEntities.53C.2.1ProcedureMNP_SRF_MATF_Call_Related.53C.2.2ProcessSRI_NPLR.53C.3CallScenarios.57C.3.1CalltoaNon-PortedNumberorNumberPortedintotheNetwork.57C.3.2CalltoaPortedNumber–OriginatingNetwork=SubscriptionNetwork–DirectRouteing.58C.3.3MobileOriginatedCalltoaPortedornotknowntobePortedNumber–OriginatingNetwork≠≠≠≠SubscriptionNetwork–DirectRouteing.58C.3.4CalltoaPortedNumber–IndirectRouteing.59C.3.5CalltoaPortedNumber–IndirectRouteingwithReferencetoSubscriptionNetwork.60C.4InformationFlows.61C.5Contentsofthemessages.68C.5.1SendRouteingInfo.68C.5.2SendRouteingInfoack.68C.6HandlingofMAPtoISUPmapping(informative).68C.6.1Mappingdirection:ISUPtoMAP.68C.6.2Mappingdirection:MAPtoISUP.69AnnexD(informative):StatusofTechnicalSpecificationGSM03.66.70History.71SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)5(GSM03.66Version7.3.1Release1998)IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyETSITechnicalCommitteeSpecialMobileGroup(SMG).ThepresentdocumentspecifiesalternativesfortherealisationofMobileNumberPortabilitywithinthedigitalcellulartelecommunicationssystem.ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithinSMGandmaychangefollowingformalSMGapproval.ShouldSMGmodifythecontentsofthepresentdocumentitwillthenberepublishedbyETSIwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Version7.x.ywhere:7IndicatesGSMPhase2+Release1998;xtheseconddigitisincrementedfortechnicalenhancements,corrections,updates,etcythethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthespecification.NationaltranspositiondatesDateofadoptionofthepresentdocument:22September2000Dateoflatestannouncementofthepresentdocument(doa):31December2000DateoflatestpublicationofnewNationalStandardorendorsementofthepresentdocument(dop/e):30June2001DateofwithdrawalofanyconflictingNationalStandard(dow):30June2001SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)6(GSM03.66Version7.3.1Release1998)1ScopeThepresentdocumentdescribesseveralalternativesfortherealisationofMobileNumberPortability.Thepresentdocumentincludesinformationapplicabletonetworkoperators,serviceproviders,switchanddatabasemanufacturersandnationalregulators.Itislefttooperatorandimplementationdecisionswhichoption,orcombinationofoptions,isused,takingintoaccounttheregulatoryandarchitecturalconstraintsthatmayprevail.Thepossibleimplicationsoftheseoptionsoninternalnodefunctionsandonsignallingperformancearenotcoveredinthepresentdocument.NormativeAnnexAofthepresentdocumentdescribesthetechnicalrealisationofthehandlingofcallstoportedGSMmobilesubscribersusingINtechnology.NormativeAnnexCofthepresentdocumentdescribesthetechnicalrealisationofthehandlingofcallstoportedGSMmobilesubscribersusingSignallingRelaytechnology.NormativeAnnexAandNormativeAnnexCdescribealternativesolutions.Thenetworkoperatormaychoosethesolutiontobeusedinhisnetwork.NormativeAnnexBofthepresentdocumentdescribesthetechnicalrealisationofthehandlingofnon-callrelatedSCCPsignallingforportedGSMmobilesubscribersusingSignallingRelaytechnology.Thepresentdocumentdoesnotspecifytheportingprocess.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.• ForthisRelease1998document,referencestoGSMdocumentsareforRelease1998versions(version7.x.y).[1]GSM01.04(ETR350):"Digitalcellulartelecommunicationssystem(Phase2+);Abbreviationsandacronyms".[2]ETS300009(December1991):"IntegratedServicesDigitalNetwork(ISDN);CCITTSignallingSystemNo.7-SignallingConnectionControlPart(SCCP)[connectionlessservices]tosupportinternationalinterconnection".[3]GSM02.66:"Digitalcellulartelecommunicationssystem(Phase2+);SupportofMobileNumberPortability(MNP);Servicedescription.Stage1".[4]GSM03.18:"Digitalcellulartelecommunicationssystem(Phase2+);Basiccallhandling;Technicalrealisation".[5]GSM09.02(ETS300974):"Digitalcellulartelecommunicationssystem(Phase2+);MobileApplicationPart(MAP)specification".[6]ETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:protocolspecification".SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)7(GSM03.66Version7.3.1Release1998)[7]EN302097V1.1.2(1999):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP);EnhancementsforsupportofNumberPortability(NP)".[8]EN300356-2(V4.0.0):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version4fortheinternationalinterface;Part2:ISDNsupplemantaryservices[ITU-TRecommendationQ.730modified]".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:donornetwork:thesubscriptionnetworkfromwhichanumberisportedintheportingprocess.Thismayormaynotbethenumberrangeholdernetworkinterrogatingnetworkentity:theentitythatsubmitsanon-callrelatedsignallingmessagetointerrogatetheHLRinterrogatingnetwork:thenetworkinwhichtheinterrogatingnetworkentityresidesmobilenumberportability:theabilityforamobilesubscribertochangeGSMsubscriptionnetworkwithinthesamecountrywhilstretainingtheiroriginalMSISDN(s)networkoperator:aGSMPLMNoperatornon-callrelatedsignallingmessage:allsignallingmessageswheretheMSISDNisusedtoroutethemessageonSCCPlevelexceptMAPSRIwithoutORparameterset(i.e.SRI_SMS,SRIforSOR,Send_IMSI,CCBS_Requestetc)numberportabilitydatabase:anOperationaldatabase(usedinrealtimeatcallset-up)whichprovidesportabilityinformationnumberportabilitylocationregister:aninternalMAPapplicationterminatingfunction(MATF)intheMNP-SRFnetworkentitywithan(unspecified)interfacewithaNPDBnumberrangeholdernetwork:thenetworktowhichthenumberrangecontainingtheportednumberhasbeenallocatedoriginatingnetwork:thenetworkwherethecallingpartyislocatedportabilitydomain:asetofGSMPLMNsinacountrybetweenwhichMSISDNsmaybeportedportablenumber:anE.164numberthatcanbeportedbetweennetworksinonenationportednumber:aportablenumberthathasundergonetheportingprocessportedsubscriber:thesubscriberofaportednumberportingprocess:adescriptionofthetransferofanumberbetweennetworkoperatorsrecipientnetwork:thenetworkwhichreceivesthenumberintheportingprocess.Thisnetworkbecomesthesubscriptionnetworkwhentheportingprocessiscompleterouteingnumber:therouteingnumberisthedatastoredagainsttheportednumberintheNumberPortabilityDatabaseservicekey:theServiceKeycanidentifytotheentityholdingtheNumberPortabilityDatabasethattheservicelogicforMobileNumberPortabilityshouldapply.TheServiceKeyvalueforMobileNumberPortabilityisadministeredintheMSC,andispassedtransparentlytotheentityholdingtheNumberPortabilityDatabaseserviceprovider:anentitywhichoffersservicesubscriptionstoindividualsubscribersandcontractswithanetworkoperatortoimplementservicesforaspecificMSISDN.Aserviceprovidermaycontractwithmorethanonenetworkoperatorserviceproviderportability:thetransferofnumbersbetweentwouniqueServiceProvidersSIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)8(GSM03.66Version7.3.1Release1998)subscriptionnetwork:thenetworkwithwhichthecustomer'sServiceProviderhasacontracttoimplementthecustomer'sservicesforaspecificMSISDNNOTE:Theterm"recipientnetwork"isusedduringtheportingprocess.Therecipientnetworkbecomesthe"subscriptionnetwork"aftercompletionoftheportingprocess.3.2AbbreviationsAbbreviationsusedinthepresentdocumentarelistedinGSM01.04([1]).Forthepurposesofthepresentdocument,thefollowingabbreviationsapply:GMSCGatewayMSCGMSCBTheGMSCinHPLMNBHLRHomeLocationRegisterHPLMNBThesubscriptionnetworkoftheBsubscriberIDPInitialDetectionPointIEInformationElementIFInformationFlowINEInterrogatingNetworkEntityIPLMNInterrogatingPLMNMATFMAPapplicationTerminatingFunctionMNPMobileNumberPortabilityMNP-SRFSignallingRelayFunctionforsupportofMNPMSAMobileStationoftheAsubscriberMSBMobileStationoftheBsubscriberMSCMobileserviceSwitchingCentreNPDBNumberPortabilityDatabaseNPLMNThenumberrangeholdernetworkoftheBsubscriberNPLRNumberPortabilityLocationRegisterOQoDOriginatingcallQueryonDigitAnalysisPLMNPublicLandMobileNetworkQoHRQueryonHLRReleaseRNRoutingNumberSMSShortMessageServiceSORSupportofOptimalRouteingSRISendRouteingInformationTQoDTerminatingcallQueryonDigitAnalysisTTTranslationTypeVMSCTheVisitedMSCVMSCBTheVMSCoftheBsubscriberFurtherGSMrelatedabbreviationsaregiveninGSM01.04.SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)9(GSM03.66Version7.3.1Release1998)4General4.1OverviewMobileNumberPortability(MNP)istheabilityforamobilesubscribertochangetheGSMsubscriptionnetworkwithinaportabilitydomainwhilstretainingheroriginalMSISDNorMSISDNs.AspartoftheportingprocessadministrativeactionshavetobeperformedbytheGSMnetworkoperatorsofthenumberrangeholdernetwork,donornetwork,recipientnetworkand,asanoption,byoperatorsofothernationalGSMnetworksasfollows:a)ifthenumberrangeholdernetworkisidenticalwiththedonornetwork:Recipientnetwork:addanentryintheHLR;addanentryintheNumberPortabilityDatabase.Donornetwork:addanentryintheNumberPortabilityDatabase;deletetheentryrelatedtotheportedMSISDNsintheHLR.Othernetworksintheportabilitydomain:addanentryintheNumberPortabilityDatabase(ifdirectrouteingisused).b)ifthenumberrangeownernetworkisidenticalwiththerecipientnetwork:Recipientnetwork:addanentryintheHLR;deleteanyentryrelatedtotheportedMSISDNintheNumberPortabilityDatabase.Donornetwork:deleteanyentryrelatedtotheportedMSISDNintheNumberPortabilityDatabase;deletetheentryrelatedtotheportedMSISDNsintheHLR.Othernetworksintheportabilitydomain:deleteanyentryrelatedtotheportedMSISDNintheNumberPortabilityDatabase.c)ifthenumberrangeholdernetworkisdifferentfromboththerecipientandthedonornetwork:Recipientnetwork:addanentryintheHLR;addanentryintheNumberPortabilityDatabase.Numberrangeholdernetwork:updatetheNumberPortabilityDatabaseDonornetwork:delete(orupdate)theentryintheNumberPortabilityDatabase;deletetheentryrelatedtotheportedMSISDNsintheHLR.Othernetworksintheportabilitydomain:updatetheNumberPortabilityDatabase(ifanentryfortheportedMSISDNexists).Notethattheorderofsequencefortheadministrativeactionstobeperformedbothwithinanetworkandbydifferentnetworkoperatorsissignificantwithrespecttopreventionofdisruptioninservicetothemobilesubscriberandpreventionofloopingcallsbetweennetworksduringtheportingprocess.TerminationofasubscriptionforaportednumberresultsinthedeletionofanyentryinanHLRandNPDBofthatnumber.Ifacallfailsbecausedatabasesarenotcorrectlysynchronised,thenetworkentitywhichdetectstheinconsistencywillraiseanMNPspecificalarmtotheoperationandmaintenancesubsystem.Thepresentdocumentdoesnotspecifytheportingprocess;itspecifiesthefunctionalityneededtoset-upcallstobothportedandnonportedsubscribers(normativeannexAandnormativeannexC)andthefunctionalityneededtorelaynon-callrelatedsignallingmessagestotheHLRinthesubscriptionnetwork(normativeannexB).SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)10(GSM03.66Version7.3.1Release1998)4.2CompatibilityTheIAMsenttothesubscriptionnetworkmaycontainadditionalrouteinginformation.WithinaportabilitydomainthemethodhowtoconveytheRouteingNumberintheIAMbetween2PLMNsshallbeagreeduponbythe2networkoperatorsinvolved(seealso[7]).Ingeneral,IN-basedandMNP-SRF(call-related)solutionsarecompatibleandmaycoexistinthesameportabilitydomain.Theonlyrestrictionreferstothecasewherethenumberrangeholdernetworkrelayscall-relatedMAPmessages(i.e.SRIfornationalcalls)tothesubscriptionnetwork.Ifthissolutionisselectedbyatleastonenetworkoperatorwithinaportabilitydomain,allthePLMNsandtransitnetworksaffectedmustfulfilthefollowingrequirements:1.TheSCCPinterfacesbetweennetworksinaportabilitydomainmustbeagreed.ThisreferstotheSCCPaddressingmechanismbeingused(e.g.numberlengths,naturesofaddressandtranslationtypesforcall-relatedMAPmessages).FormessageswhichdonotcrossnetworkboundariestheSCCPaddressingmechanismisachoiceofthenetworkoperator.2.ThesubscriptionnetworkmustbeabletogeneratetheSRIacktoallowtheonwardrouteingofthecallfromthenumberrangeholdernetworktothesubscriptionnetwork.IntherestofthepossiblearchitecturesforMNP,nointerworkingproblemshavebeenidentified.Inthesecases,networkarchitecturesusedwithinonePLMN(e.g.IN,MNP-SRF)areregardedasoperatordependent.Inordertoavoidloopsandincompatibilitysituations,allthenetworkswithinaportabilitydomainshallusethesamerouteingconventioneitherdirectrouteing,indirectrouteingorindirectrouteingwithreferencetotheSubscriptionnetwork.Asanalternative,indirectrouteingcaninterworksuccessfullywithdirectrouteingiftherouteingnumberistransferredintheIAMorifdedicatedtrafficconnectionsareused.4.3CommonFunctionalityoftheMNP-SRFInaPLMNwhichsupportsmobilenumberportability,SCCPmessagessenttoanHLRmayberelayedbyanMNP-SRF.Dependingontheimplementedsolution(IN-basedorMNP-SRF-based),onthetypeofmessage(call-relatedornon-call-related)andontheportingstatusofthecalledsubscribertheMNP-SRFmaymodifytheSCCPcalledpartyaddressandroutethemessagetoadifferentHLRortothesubscriptionnetwork,orterminatethedialogueandresponsetotheINE.Figure1showsthegeneralsteeringfunctionalityforSCCPmessagerouteing.ItshowstheSCCProuteingprincipleformobilenumberportabilitywithinanetwork.NotethatcallrelatedmessagesintheIN-basedsolutionarenotroutedtotheMNP-SRF.ThereforeNormativeAnnexAofthepresentdocumentdoesnotmentiontheMNP-SRF.However,theusageoftheIN-basedsolutionforthecall-relatedmessagesshouldallowoperatorstohavetherouteingofthenoncall-relatedmessagesdeterminedinthesamedatabase.InordertoguardagainstthepossibilitythattheportingdataforanMSISDNisinconsistentbetweenPLMNsinaportingdomain,theSCCPhopcountermaybeusedtopreventindefiniteloopingofmessagesbetweenPLMNs.TheMNP-SRFwouldthendecrementtheSCCPhopcounterforeverymessagethatisrelayed.ItshouldbenotedthattheuseoftheSCCPhopcounterrequirestheuseofunsegmentedSCCPXUDTmessagesasdefinedinITU-T1996SCCPrecommendations.SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)11(GSM03.66Version7.3.1Release1998)generalSteeringFunctionforSCCProuteingProcessSCCP_Steering_Function1(1)IdleSCCPmessageOPTIONcallrelatedSCCPmessagetoHLRSCCPmessagetoMNP-SRFSCCPmessagetoMNP-SRF-MATFIdleIdleIdleIN-basedMNP-SRF-basedyesnoFigure1:SteeringFunctionforSCCPMessagerouteingFigure2showstheprocessMNP_SRFintheMNP-SRF.TheproceduresMNP_SRF_MATF_Call_RelatedandMNP_SRF_Non_Call_RelatedaredescribedinNormativeAnnexCandNormativeAnnexBofthepresentdocument.NotethatinnetworkswhichsupporttheIN-basedsolutionforcallrelatedsignalling,adistinctiononSCCPlevelforcallrelatedandnon-callrelatedmessagesisneededandthattheMNP-SRFdoesnotrequiretoincludeaMATFsincecallrelatedmessagesarenotroutedtotheMNP-SRF.Thetest"call-related"isatestontheSCCPTranslationTypeifadedicatedTranslationTypevalueforcallrelatedmessagesisusedinthenetwork.ThehandlingofSCCPmessagesintheMNP-SRFinnetworkswhichdonotmakeuseofadedicatedTranslationTypevalueforcallrelatedmessagesisforfurtherstudy.SIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)12(GSM03.66Version7.3.1Release1998)ProcessintheMNP_SRFtorelaySCCPmessagesProcessMNP_SRF1(1)IDLESCCPmessagecall-relatedMNP_SRF_MAT_Call_RelatedseeNormativeAnnexCterminateMAPdialogueterminatedatMATFIDLEMNP_SRF_Non_Call_RelatedseeNormativeAnnexBSCCPmessageSCCPmessageIDLEIDLEyesnoyesnoFigure2:ProcessMNP_SRFSIST EN 301 716 V7.3.1:2003



ETSIETSIEN301716V7.3.1(2000-10)13(GSM03.66Version7.3.1Release1998)5CommonArchitectureforcallsetupFigure3showsthegeneralarchitectureofaportabilitydomainforrouteingofcalls.Themoredetailedarchitecturewithinthenetworksdependsonthechosensolution(IN-basedorMNP/SRF-based)andoptionsandisdescribedinNormativeAnnexAandNormativeAnnexCofthepresentdocument.Thearchitecturefornon-callrelatedsignallingisdescribedinNormativeAnnexBofthepresentdocument.OthernationalnetworkIAM(6)IAM(7)IAM(3)IAM(1)NumberrangeholdernetworkSubscriptionnetworkSRI(4)SRIack(5)IAM(2)IAM(8)PortabilitydomainFigure3:GeneralarchitectureofaportabilitydomainforrouteingofcallsThefollowingrouteingconventionsareidentified:1.DirectRouteingofcallsisaPLMNoptionwhichallowstoroutecallsdirectlyfromthePLMNsupportingthisoptiontotheportedsubscriber'ssubscriptionnetwork.2.IndirectRouteingofcallsisaPLMNoptionwhichallowstoroutecallsfromthePLMNsupportingthisoptionviathenumberrangeholdernetworktotheportedsubscribe
...