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)

SIST EN 301 716 V7.3.1:2003 is the SIST publication of the ETSI European Standard for GSM Mobile Number Portability (MNP) technical realisation at Stage 2. It specifies how GSM networks route calls and selected signalling for ported and non-ported mobile numbers within a country, for network operators, service providers, switch and database manufacturers, and national regulators.

What does SIST EN 301 716 V7.3.1:2003 specify?

SIST EN 301 716 V7.3.1:2003 specifies several alternatives for realising MNP in digital cellular telecommunications system (Phase 2+) GSM networks. It focuses on call setup and on relaying non-call-related signalling to the correct HLR in the subscription network, while leaving the porting process itself outside its scope.

Clause 4 gives the general architecture and the compatibility rules. The normative annexes then split the technical realisation into call-related, non-call-related, and signalling-relay solutions.

Annex	What it covers
Annex A	IN call-related technical realisation
Annex B	Handling of non-call-related signalling
Annex C	MNP Signalling Relay Function for call-related signalling
Annex D	Status of Technical Specification GSM 03.66

What are the key requirements of SIST EN 301 716 V7.3.1:2003?

• Clause 4.1 describes the administrative actions needed when a number is ported. Depending on whether the number range holder network, donor network, and recipient network are the same or different, HLR and NPDB entries are added, deleted, or updated. In practice, this means operators must keep portability data synchronized in the right order to avoid service disruption and looping calls.

• Clause 4.1 also states that if call setup fails because databases are not synchronized, the detecting network entity raises an MNP-specific alarm to the operation and maintenance subsystem. That matters because portability problems become an operational fault, not just a routing error.

• Clause 4.2 requires all PLMNs in a portability domain to use the same routeing convention - direct routeing, indirect routeing, or indirect routeing with reference to the subscription network - to avoid loops and incompatibility. Where the number range holder network relays call-related MAP messages, the SCCP interfaces and the subscription network SRI ack behaviour must be agreed.

• Clause 4.3 defines the common MNP-SRF behaviour for SCCP message steering. The MNP-SRF may change the SCCP called party address, forward the message to another HLR or to the subscription network, or terminate the dialogue and respond to the interrogating network entity. The clause also notes that SCCP hop counter handling can be used to limit indefinite looping.

• Annex A defines the IN-based call-related options: Terminating call Query on Digit Analysis (TQoD), Query on HLR Release (QoHR), and Originating call Query on Digit Analysis (OQoD). Each GMSC shall support at least one of TQoD or QoHR in an IN-based GSM network, and OQoD is an operator choice for MO calls and forwarded calls.

• Annex A also defines the core message content for the IN solution. The IDP carries the MNP service key and the called party MSISDN, while INITIALDP negative response uses missing parameter or unexpected data value. In practice, implementers use these message rules to make the NPDB query and call continuation behave consistently.

• Annex B defines how non-call-related signalling is rerouted. It covers messages such as SRI for SM, Any Time Interrogation, and CCBS requests, and shows when the MNP-SRF relays a message to the HLR, to the subscription network, or to the number range holder network.

• Annex C defines the call-related signalling relay solution for MAP_SEND_ROUTING_INFORMATION without OR parameters. It also defines the NPLR behaviour for SRI responses, including when the routeing number is returned and when the call should fail.

What terms does SIST EN 301 716 V7.3.1:2003 define?

• Mobile Number Portability (MNP) - the ability for a mobile subscriber to change GSM subscription network within the same country and keep the original MSISDN(s).

• Number Portability Database (NPDB) - the operational database used in real time at call setup to provide portability information.

• MNP-Signalling Relay Function (MNP-SRF) - the network function that steers SCCP messages using MSISDN-based routeing information.

• Number Portability Location Register (NPLR) - the internal MAP application terminating function in the MNP-SRF that returns routeing information.

• Routeing number - the number stored against the ported number in the NPDB and used to direct traffic to the right network.

• Portability domain - the set of GSM PLMNs in a country between which MSISDNs may be ported.

Who uses SIST EN 301 716 V7.3.1:2003?

SIST EN 301 716 V7.3.1:2003 is used by GSM network operators, service providers, switch manufacturers, database manufacturers, and national regulators. They use it to design routeing behaviour, configure HLR and NPDB interactions, implement signalling relay, and verify that ported numbers are reached correctly.

What changed in SIST EN 301 716 V7.3.1:2003 from the previous edition?

SIST EN 301 716 V7.3.1:2003 is presented as an upgrade to Version 7.1.0. Annex D records later changes such as editorial clarifications, harmonised terminology, routeing convention clarifications, addition of the MNP indicator to the SRI ack, and clarification of NPLR behaviour for numbers not known to be ported.

Which standards are used with SIST EN 301 716 V7.3.1:2003?

• GSM01.04 - abbreviations and acronyms used in the document.
• ETS 300 009 - SCCP connectionless services for signalling interconnection.
• GSM02.66 - Stage 1 service description for MNP.
• GSM03.18 - basic call handling and the procedures that this standard extends.
• GSM09.02 - MAP specification used for the IDP, SRI and related signalling.
• ETS 300 374-1 - INAP CS1 protocol specification.
• EN 302 097 - ISUP enhancements for support of number portability.
• EN 300 356-2 - ISUP supplementary services used for ISUP coding alignment.

What does the SIST EN 301 716 V7.3.1:2003 document contain?

The document contains general architecture diagrams, routeing conventions, and signalling flow figures for call-related and non-call-related cases. It also includes SDL-style procedures for GMSC, MSC, NPDB and NPLR behaviour, plus message-content definitions for IAM, INITIALDP, CONNECT and CONTINUE. Annex B and Annex C give worked signalling scenarios for SMS delivery, ATI, CCBS, and several call routeing cases, which helps implementers check interoperability and test network behaviour.

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
...