SIST EN 301 716 V7.3.1:2003

• Abstract:

  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.

• 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)

Overview

SIST EN 301 716 V7.3.1:2003 specifies the Stage 2 technical realization for supporting Mobile Number Portability (MNP) within GSM networks in the same country. Developed in alignment with GSM 03.66 Version 7.3.1 Release 1998 and harmonized with EN 301 716, this European Standard addresses how mobile subscribers can retain their original telephone number (MSISDN) when moving between different GSM subscription networks domestically.

Mobile number portability is essential to promote user flexibility and competition among service providers, minimizing switching barriers and improving user satisfaction. This standard forms a critical part of modern GSM network operation, ensuring seamless call and messaging services for ported numbers across all participating networks within a country’s portability domain.

Key Topics

• Mobile Number Portability (MNP): Describes the ability for a GSM subscriber to change networks while keeping their original number.
• Portability Domain: Defines a set of GSM networks within a country between which numbers can be ported.
• Network Roles:
  • Recipient network: The destination network after porting.
  • Donor network: The original network from which the number is ported.
  • Number range holder network: The network that owns the initial block of numbers.
• Routeing Conventions: Outlines direct and indirect routing for handling calls to ported and non-ported numbers, including:
  • Direct routing (call directed to recipient network)
  • Indirect routing (call routed via number range holder)
• Signalling Scenarios: Detailed procedures for managing both call-related and non-call-related network signaling to ensure accurate message delivery to ported numbers.
• Supporting Network Elements: Defines the functional requirements for network components like the Number Portability Database (NPDB), Gateway MSC (GMSC), and Signalling Relay Function (MNP-SRF).

Applications

SIST EN 301 716 V7.3.1:2003 is crucial for:

• Network Operators: Enables compliant technical interworking and routing between GSM networks supporting mobile number portability, thus allowing subscribers to seamlessly switch networks without service disruption.
• Service Providers: Facilitates easier number retention for end users, supporting competitive service offerings and improving customer retention.
• System Integrators & Equipment Manufacturers: Provides the guidelines and technical frameworks required to develop, integrate, and maintain network elements, such as databases and switching systems, in line with MNP requirements.
• National Regulatory Authorities: Assures consistent implementation of MNP regulations, fostering a competitive telecom environment and protecting subscriber interests.

Typical use cases include:

• Seamless transfer of users between GSM networks while preserving their phone number and associated services.
• Ensuring accurate routing of calls and SMS to either non-ported or ported numbers via direct or indirect network routes.
• Maintaining synchronization of portability data to prevent service disruption or misrouted communications.

Related Standards

Relevant and referenced standards for effective implementation include:

• GSM 01.04: Abbreviations and acronyms for GSM systems
• GSM 02.66: Service description for support of MNP (Stage 1)
• GSM 03.18: Basic call handling, technical realization
• GSM 09.02: Mobile Application Part (MAP) specification
• ETS 300 374-1: Intelligent Network Application Protocol (INAP)
• EN 302 097 V1.1.2: ISDN User Part (ISUP) enhancements for number portability

SIST EN 301 716 V7.3.1:2003 is an authoritative resource for all stakeholders involved in the deployment and operation of MNP within GSM networks, supporting interoperability, regulatory compliance, and a superior customer experience across the mobile telecommunications sector.

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
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.IndirectRouteingofcallsisaPLMNoptionwhichallowstoroutecallsfromthePLMNsupportingthisoptionviathenumberrangeholdernetworktotheportedsubscriber'ssubscriptionnetwork.3.IndirectRouteingofcallswithreferencetothesubscriptionnetworkisaPLMNoptionforPLMNoperatorshavingchosentheMNP-SRFsolutionforcallrelatedsignallingdescribedinNormativeAnnexC.IfallPLMNswithinaportabilitydomainsupportthisoption,callsareroutedfromtheoriginatingnetworktothenumberrangeholdernetwork.Thenumberrangeholdernetworkobtainsonwardrouteinginformationfromthesubscriptionnetworkandroutesthecallonwardtotheportedsubscriber'ssubscriptionnetwork.Thefollowingactionsinthedifferentnetworkscanbeidentified:1.Ifthecallisoriginatedoutsidetheportabilitydomain,theIAM(1)isreceivedbythenumberrangeholdernetwork.2a.Ifthecallisoriginatedinanothernationalnetworkandtheothernationalnetworkdoesnotsupportoriginatingcallquery(i.e.IndirectRouteingofcallsisapplicable),theIAM(2)isreceivedbythenumberrangeholdernetwork.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)14(GSM03.66Version7.3.1Release1998)2b.Ifthecallisoriginatedinanothernationalnetworkandtheothernationalnetworksupportsoriginatingcallquery(i.e.DirectRouteingofcallsisapplicable),theIAM(7)containingtherouteingnumberissenttothesubscriptionnetwork.IftherouteingnumberisnotusedintheIAMsentfromthenationaloriginatingnetworktothesubscriptionnetwork,alltransitnetworksinvolvedarerequiredtolookupanNPDBinordertoretrieverouteinginformationtoroutethecalltothesubscriptionnetworkwithoutlooping.3a.Ifthecallisoriginatedinthesubscriptionnetworkandthesubscriptionnetworkdoesnotsupportoriginatingcallquery(i.e.IndirectRouteingofcallsisapplicable),theIAM(3)isreceivedbythenumberrangeholdernetwork.3b.Ifthecallisoriginatedinthesubscriptionnetworkandthesubscriptionnetworksupportsoriginatingcallquery(i.e.DirectRouteingofcallsisapplicable),itsendsanIAM(8)containingtheMSRNtothevisitednetworkofthecalledsubscriber.3c.IfthesubscriptionnetworkreceivesIAM(6or7)containingtherouteingnumber,itsendsanIAM(8)containingtheMSRNtothevisitednetworkofthecalledsubscriber.4a.Ifthecallisroutedviathenumberrangeholdernetwork,andthenumberrangeholdernetworksupportstheMNP-SRF/MATFsolutionwiththeoption'MATFinsubscriptionnetwork'describedinNormativeAnnexCofthepresentdocument(i.e.IndirectRouteingofcallswithreferencetothesubscriptionnetworkisapplicable),thenumberrangeholdernetworksendsSRI(4)tothesubscriptionnetwork.ThesubscriptionnetworkreturnsSRIack(5)containingtherouteingnumber.ThenumberrangeholdernetworkthensendsIAM(6)containingtherouteingnumbertothesubscriptionnetwork.IftherouteingnumberisnotusedintheIAMsentfromthenumberrangeholdernetworktothesubscriptionnetwork,alltransitnetworksinvolvedarerequiredtolookupanNPDBinordertoretrieverouteinginformationtoroutethecalltothesubscriptionnetworkwithoutlooping.4b.Ifthecallisroutedviathenumberrangeholdernetwork,andthenumberrangeholdernetworksupportstheINsolutiondescribedinNormativeAnnexAofthepresentdocumentortheMNP-SRF/MATFsolutionwiththeoption'MATFinsidenumberrangeholdernetwork'describedinNormativeAnnexCofthepresentdocument,thenumberrangeholdernetworksendsIAM(6)containingtherouteingnumbertothesubscriptionnetwork.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)15(GSM03.66Version7.3.1Release1998)AnnexA(normative):INCall-RelatedTechnicalRealisationA.1ArchitectureA.1.1NetworkOptionsThefollowingnetworkoperatoroptionsaredefinedfortheMTcallsintheGMSC:• TerminatingcallQueryonDigitAnalysis(TQoD);• QueryonHLRRelease(QoHR).InaGSMnetworkwhichsupportstheIN-basedapproachforcallrelatedMNP,eachGMSCshallsupportatleastoneoftheseoptions.ThefollowingnetworkoperatoroptionisdefinedforMOcallsinVMSCAandforforwardedcallsintheGMSCandVMSCB:• OriginatingcallQueryonDigitAnalysis(OQoD).InaGSMnetworkwhichsupportstheIN-basedapproachforcallrelatedMNP,itisanetworkoperatordecision,takingintoaccounttheregulatoryandarchitecturalconstraintsthatmayprevail,whetherornotVMSCsandGMSCssupportthisoption.TheuseofOQoDintransitswitchesinaPLMNwhileavoidingmultipledatabaseinterrogationsisforfurtherstudy.TheinterworkingbetweentheCCFandtheSSFforMNPisforfurtherstudy.Notethatfordifferentnumberrangesdifferentoptionsmaybechosen.A.1.2NoNPQueryrequired-NumberisnotsubjectforportabilityFigureA.1.2showsthearchitectureforacalltoanumberthatisnotsubjectforportability.Thiscanbeforseveralreasonslikeforexample:-thenationalregulatorhasstipulatedsomenumberseriesasbeingnon-portableor;-inaninitialphaseonlyalimitedamountofsubscribersmightportincertainnumberblocksandsomeoperatorsmightwanttotreatthecallrouteingaccordingtotraditionalrouteingplanswithoutanychange.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)16(GSM03.66Version7.3.1Release1998)Numberrangeowner/subscriptionnetworkHLRBGMSCBOriginatingExchangeVMSCB/VLRB123456(Inter)nationalOriginatingnetworkVisitednetworkFigureA.1.2:Calltoanon-portednumber,noNPqueryrequired1FromanOriginatingExchangeacallissetuptoMSISDN.ThecallisroutedtotheNumberrangeholdernetworkbeingtheSubscriptionnetwork;2WhenGMSCBreceivestheISUPIAM,itrequestsrouteinginformationbysubmittingaMAPSRItotheHLRBincludingtheMSISDNintherequest;3TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscribercurrentlyisregistered;4TheMSC/VLRBreturnsanMSRNbacktotheHLRB;5TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;6GMSCBusestheMSRNtoroutethecalltoVMSCB.A.1.3NPQueryinNumberRangeHolderNetworkA.1.3.1TQoD-NumberisnotportedFigureA.1.3.1showsthearchitectureforacallwheretheOriginatingnetworkhasnoknowledgewhethertheMSISDNisportedornotandusesthetraditionalrouteingplansforrouteingthecalltotheNumberrangeholdernetworkforfurtherrouteingdecisions.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)17(GSM03.66Version7.3.1Release1998)HLRBNPDB(Inter)nationalOriginatingnetworkVisitednetworkGMSCBVMSCB/VLRBOriginatingExchange1Numberrangeholder/subscriptionnetwork2345678FigureA.1.3.1:Calltoanon-portednumberusingTQoDprocedure1.FromanOriginatingExchangeacallissetuptoMSISDN.ThecallisroutedtotheNumberrangeholdernetworkbeingtheSubscriptionnetwork;2.WhenGMSCBreceivestheISUPIAM,itwillsendadatabasequerytotheNPDBasaresultofanalysisofthereceivedMSISDN.TheMSISDNisincludedinthequerytotheNPDB;3.TheNPDBdetectsthattheMSISDNisnotportedandrespondsbacktotheGMSCBtocontinuethenormalcallsetupprocedureforMTcalls;4.TheGMSCBrequestsrouteinginformationbysubmittingaMAPSRItotheHLRB,includingtheMSISDNintherequest;5.TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscriberowningtheMSISDNcurrentlyisregistered;6.TheMSC/VLRBreturnsanMSRNbacktotheHLRB;7.TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;8.GMSCBusestheMSRNtoroutethecalltoVMSCB.NotethattheNPDBmaybeoutsidethenumberrangeholdernetworkifasharedNPDBisused.A.1.3.2TQoD-NumberisportedFigureA.1.3.2showsthearchitectureforacallwheretheOriginatingnetworkhasnoknowledgewhethertheMSISDNisportedornotandusesthetraditionalrouteingplansforrouteingthecalltotheNumberrangeholdernetworkforfurtherrouteingdecisions.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)18(GSM03.66Version7.3.1Release1998)HLRBNPDBNumberrangeholdernetwork(Inter)nationalOriginatingnetworkVisitednetworkSubscriptionnetworkGMSCAVMSCB/VLRBOriginatingExchange1GMSCB23458679FigureA.1.3.2:CalltoaportednumberusingTQoDprocedure1FromanOriginatingExchangeacallissetuptoMSISDN.ThecallisroutedtotheNumberrangeholdernetwork;2WhenGMSCAreceivestheISUPIAM,itwillsendadatabasequery,includingtheMSISDN,totheNPDBasaresultofanalysisofthereceivedMSISDN;3TheNPDBdetectsthattheMSISDNisportedandrespondsbacktotheGMSCAwithaRouteingNumberpointingouttheSubscriptionnetwork;4ThecallisroutedtotheSubscriptionnetworkbasedontheRouteingNumbercarriedinISUPIAMmessage;alsotheMSISDNisincludedinIAM.5TheGMSCBrequestsrouteinginformationbysubmittingaMAPSRItotheHLRB,includingtheMSISDNintherequest.ThecapabilitytoroutemessagestothecorrectHLRisrequired.6TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscribercurrentlyisregistered;7TheMSC/VLRBreturnsanMSRNbacktotheHLRB;8TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;9GMSCBusestheMSRNtoroutethecalltoVMSCB.NotethattheNPDBmaybeoutsidethenumberrangeholdernetworkifasharedNPDBisused.A.1.3.3QoHR-NumberisportedFigureA.1.3.3showsthearchitectureforacallwheretheOriginatingnetworkhasnoknowledgewhethertheMSISDNisportedornotandusesthetraditionalrouteingplansforrouteingthecalltotheNumberrangeholdernetworkforfurtherrouteingdecisions.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)19(GSM03.66Version7.3.1Release1998)HLRBNPDBNumberrangeholdernetwork(Inter)nationalOriginatingnetworkVisitednetworkSubscriptionnetworkGMSCAVMSCB/VLRBOriginatingExchange1GMSCB2367108911HLRA45FigureA.1.3.3:CalltoaportednumberusingQoHRprocedure1.FromanOriginatingExchangeacallissetuptoMSISDN.Thecallisroutedtothenumberrangeholdernetwork;2.WhenGMSCAreceivestheISUPIAM,itrequestsrouteinginformationbysubmittingaMAPSRItotheHLRAincludingtheMSISDNintherequest;3.TheHLRAreturnsaMAPSRIackwithan"UnknownSubscriber"errorsincenorecordwasfoundforthesubscriberintheHLRA;4.WhenGMSCAreceivestheerrorindicationformtheHLRA,thiswilltriggerthesendingofadatabasequerytotheNPDB,includingtheMSISDNinthequery;5.TheNPDBdetectsthattheMSISDNisportedandrespondsbacktotheGMSCAwithaRouteingNumberpointingouttheSubscriptionnetwork;6.ThecallisroutedtotheSubscriptionnetworkbasedontheRouteingNumbercarriedinISUPIAMmessage;alsotheMSISDNisincludedinIAM.7.TheGMSCBrequestsrouteinginformationbysubmittingaMAPSRItotheHLRB,includingtheMSISDNintherequest.ThecapabilitytoroutemessagestothecorrectHLRisrequired.8.TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscribercurrentlyisregistered;9.TheMSC/VLRBreturnsanMSRNbacktotheHLRB;10.TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;11.GMSCBusestheMSRNtoroutethecalltoVMSCB.NotethattheNPDBmaybeoutsidethenumberrangeholdernetworkifasharedNPDBisused.A.1.4NPQueryinOriginatingNetworkA.1.4.1OQoD-NumberisnotportedFigureA.1.4.1showsthearchitectureforacallwherealreadytheOriginatingnetworkhastheknowledgewhethertheMSISDNisportedornotandcanroutethecalldirectlytotheSubscriptionnetworkthatinthiscaseisthesameastheNumberrangeholdernetwork.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)20(GSM03.66Version7.3.1Release1998)HLRBNPDBNationalOriginatingnetworkVisitednetworkVMSCAVMSCB/VLRB2356781GMSCB49Numberrangeholder/SubscriptionnetworkFigureA.1.4.1:Calltoanon-portednumberusingOQoDprocedure1AcallisinitiatedbyMobileSubscriberAtowardsMobileSubscriberB,usingMSISDNofthecalledsubscriber;2WhenVMSCAreceivesthecallsetupindication,itwillsendadatabasequerytotheNPDBasaresultofanalysisofthereceivedMSISDN,includingtheMSISDNinthequery;3TheNPDBdetectsthattheMSISDNisnotportedandrespondsbacktotheVMSCAtocontinuethenormalcallsetupprocedureforMOcalls.Dependingondatabaseconfigurationoption,theNPDBcouldeitherreturnaRouteingNumberonnotportedcalls,asdoneforportedcalls,orthecallisfurtherroutedusingtheMSISDNnumberonlytowardstheNumberrangeholdernetwork;4ThecallisroutedtotheNumberrangeholder/SubscriptionnetworkbasedontheMSISDNorRouteingNumbercarriedinISUPIAMmessage;5TheGMSCBrequestsrouteinginformationbysubmittingaMAPSRItotheHLRB,includingtheMSISDNintherequest;6TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscribercurrentlyisregistered;7TheMSC/VLRBreturnsanMSRNbacktotheHLRB;8TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;9GMSCBusestheMSRNtoroutethecalltoVMSCB.NotethattheNPDBmaybeoutsidethenationaloriginatingnetworkifasharedNPDBisused.A.1.4.2OQoD–NumberisportedFigureA.1.4.2showsthearchitectureforacallwherealreadytheOriginatingnetworkhastheknowledgethattheMSISDNisportedandcanroutethecalldirectlytotheSubscriptionnetworkwithoutinvolvingtheNumberrangeholdernetwork.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)21(GSM03.66Version7.3.1Release1998)HLRBNPDBNationalOriginatingnetworkVisitednetworkSubscriptionnetworkVMSCB/VLRBGMSCB23458679VMSCA1FigureA.1.4.2:CalltoaportednumberusingOQoDprocedure1AcallisinitiatedbyMobileSubscriberAtowardsMobileSubscriberB,usingMSISDNofthecalledsubscriber;2WhenVMSCAreceivesthecallsetupindication,itwillsendadatabasequerytotheNPDBasaresultofanalysisofthereceivedMSISDNincludingtheMSISDNinthequery;3TheNPDBdetectsthattheMSISDNisportedandrespondsbacktotheVMSCAwithaRouteingNumberpointingouttheSubscriptionnetwork;4ThecallisroutedtotheSubscriptionnetworkbasedontheRouteingNumbercarriedinISUPIAMmessage;alsotheMSISDNisincludedinIAM.5TheGMSCBrequestsrouteinginformationbysubmittingaMAPSRItotheHLRB,includingtheMSISDNintherequest.ThecapabilitytoroutemessagestothecorrectHLRisrequired.6TheHLRBrequestsanMSRNfromtheMSC/VLRBwherethemobilesubscribercurrentlyisregistered;7TheMSC/VLRBreturnsanMSRNbacktotheHLRB;8TheHLRBrespondstotheGMSCBbysendinganSRIackwithanMSRN;9GMSCBusestheMSRNtoroutethecalltoVMSCB.NotethattheNPDBmaybeoutsidethenationaloriginatingnetworkifasharedNPDBisused.SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)22(GSM03.66Version7.3.1Release1998)A.2InformationflowsInthefollowingfigurestheNPDBisshownasbelongingtothenumberrangeholdernetworkortothenationaloriginatingnetwork.However,theNPDBmaybesharedwithinoneportabilitydomaini.e.nation-wide.FigureA.2.1showstheinformationflowforsuccessfulQoHR.NumberrangeholdernetworksubscriptionnetworkvisitednetworkGMSCHLRNPDBGMSCHLRVLRVMSCIAM----SRI---neg.result----IDP------------------------CONNECT------------------------IAM--------------------------------------------SRI----PRN----PRNack----SRIack----IAM--------------------------------------------FigureA.2.1:InformationflowforsuccessfulQoHRSIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)23(GSM03.66Version7.3.1Release1998)FigureA.2.2showstheinformationflowforunsuccessfulQoHR(misdialledunallocatednumber).NumberrangeholdernetworkGMSCHLRNPDBIAM-----------------SRI----------------negativeresult----------------IDP--------------------------------------------------------------CONTINUE--------------------------------------------------------------REL----------------FigureA.2.2:InformationflowforunsuccessfulQoHR(misdialledunallocatednumber)SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)24(GSM03.66Version7.3.1Release1998)FigureA.2.3showstheinformationflowforsuccessfulTQoD.NumberrangeholdernetworksubscriptionnetworkvisitednetworkGMSCHLRNPDBGMSCHLRVLRVMSCIAM----IDP------------------------CONNECT------------------------IAM--------------------------------------------SRI----PRN----PRNack----SRIack----IAM--------------------------------------------FigureA.2.3:InformationflowforsuccessfulTQoDSIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)25(GSM03.66Version7.3.1Release1998)FigureA.2.4showstheinformationflowforunsuccessfulTQoD(numbernotported).NumberrangeholdernetworkvisitednetworkGMSCHLRNPDBVLRVMSCIAM-------IDP-----------------------------------CONTINUE-----------------------------------SRI-------PRN------------------------------------PRNack------------------------------------SRIack-------IAM--------------------------------------------------------------------------------------------FigureA.2.4:InformationflowforunsuccessfulTQoD(numbernotported)SIST EN 301 716 V7.3.1:2003

ETSIETSIEN301716V7.3.1(2000-10)26(GSM03.66Version7.3.1Release1998)FigureA.2.5showstheinformationflowforsuccessfulOQoD(numberported).Nationalorig
...