You are on page 1of 86

ETSI TS 123 066 V5.3.

0 (2003-12)
Technical Specification

Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
Support of GSM Mobile Number Portability (MNP);
Stage 2
(3GPP TS 23.066 version 5.3.0 Release 5)

R

GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS 

3GPP TS 23.066 version 5.3.0 Release 5 1 ETSI TS 123 066 V5.3.0 (2003-12)

Reference
RTS/TSGN-0423066v530

Keywords
GSM, UMTS

ETSI

650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice

Individual copies of the present document can be downloaded from:
http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp

If you find errors in the present document, send your comment to:
editor@etsi.org

Copyright Notification

No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

ETSI

3GPP TS 23.066 version 5.3.0 Release 5 2 ETSI TS 123 066 V5.3.0 (2003-12)

Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp .

ETSI

3GPP TS 23.066 version 5.3.0 Release 5 3 ETSI TS 123 066 V5.3.0 (2003-12)

Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Foreword.............................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions and abbreviations...................................................................................................................7
3.1 Definitions..........................................................................................................................................................7
3.2 Abbreviations .....................................................................................................................................................8
4 General .....................................................................................................................................................9
4.1 Overview ............................................................................................................................................................9
4.2 Compatibility....................................................................................................................................................10
4.3 Common Functionality of the MNP-SRF.........................................................................................................11
5 Common Architecture for call setup ......................................................................................................14
6 Functional requirements of network entities ..........................................................................................16
6.1 Procedure MNP_MT_GMSC_Set_MNP_Parameters......................................................................................16
6.2 Procedure MNP_MT_GMSC_Check_MNP_Indicators ..................................................................................17
6.3 Procedure MNP_SRF_Check_MNP_Indicator ................................................................................................18

Annex A (normative): IN Call-Related Technical Realisation.........................................................19
A.1 Architecture............................................................................................................................................19
A.1.1 Network Options ..............................................................................................................................................19
A.1.2 No NP Query required – Number is not subject for portability........................................................................19
A.1.3 NP Query in Number Range Holder Network..................................................................................................20
A.1.3.1 TQoD – Number is not ported ....................................................................................................................20
A.1.3.2 TQoD – Number is ported ..........................................................................................................................21
A.1.3.3 QoHR – Number is ported ..........................................................................................................................22
A.1.4 NP Query in Originating Network ...................................................................................................................23
A.1.4.1 OQoD – Number is not ported....................................................................................................................23
A.1.4.2 OQoD – Number is ported..........................................................................................................................24
A.1.4.3 IN-Query for CAMEL pre-paid service......................................................................................................25
A.2 Information flows...................................................................................................................................27
A.3 Functional requirements of network entities ..........................................................................................33
A.3.1 Functional requirement of GMSC ....................................................................................................................33
A.3.1.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR ..................................................................33
A.3.1.2 Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD...................................................................35
A.3.2 Functional requirement of MSC .......................................................................................................................36
A.3.2.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD ..................................................................36
A.3.3 Functional requirement of NPDB.....................................................................................................................38
A.3.3.1 Process IN_QUERY_NPDB.......................................................................................................................38
A.4 Contents of messages .............................................................................................................................39
A.4.1 Messages on the ISUP interface .......................................................................................................................39
A.4.1.1 IAM for ETSI ISUP interface .....................................................................................................................39
A.4.1.2 IAM for ANSI ISUP interface ....................................................................................................................39
A.4.2 Messages on the MSC - NPDB interface .........................................................................................................39
A.4.2.1 INITIAL DP................................................................................................................................................39
A.4.2.2 INITIAL DP negative response ..................................................................................................................40
A.4.2.3 CONNECT .................................................................................................................................................40
A.4.2.4 CONTINUE................................................................................................................................................40
A.4.2.5 RELEASE CALL .......................................................................................................................................40
A.4.2.6 ProvideInstruction:Start ..............................................................................................................................40

ETSI

......................1 Procedure MNP_SRF_MATF_Call_Related ...........................59 C.6...............................51 B.......................................................5 Call to a Ported Number – Indirect Routeing with Reference to Subscription Network ...............3...........................................................................................................80 C.......................3.......................................0 Release 5 4 ETSI TS 123 066 V5..............................45 B..Indirect Routeing........................................80 C.................................46 B.50 B.....81 C.......54 B.....................72 C............................2 Process SRI_NPLR ...........................................................61 C.....................................4.....2.........................................................................3 ANSI Mapping direction: ISUP to MAP.......4.............................................2 Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing ..............................61 C..................................................6.......................0 (2003-12) A.....................................................................................10 Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay........................6...2 Functional Requirements of Network Entities ........4...............60 C....................................68 C....................................................................................................................................6 MNP Info Query ..............................................................................3........1 Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing ......................42 B.42 B.........................................................................................................................2................46 B.3.........73 C....................2 Delivery of SMS to a Non-ported Number .............................2..........79 C.74 C................................................................................................84 History ..5..............................................................................................................56 B................3 Delivery of SMS to a Ported Number – Indirect Routeing..........................55 B......3...........4.................2.............................................6 SOR for a Ported Number – Indirect Routeing ..........................................................................71 C...............44 B.........49 B...........................................................57 B............6..................................1 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay.........2 Network Architecture ...........44 B......69 C..................2 Signalling Scenarios ............................1 Send Routeing Info.....................70 C..........41 Annex B (normative): Handling of Non-Call Related Signalling ............1 Handling of Non-call Related Signalling ............3...........................................5.......3...................2 ETSI Mapping direction: MAP to ISUP...........................1...........................81 Annex D: Void ........................................................................................42 B........................8 Any Time Interrogation for a Ported Number – Direct Routeing.....................................................4 Signalling Scenarios (informative)..........................4......................................................2.3 Procedure MNP_SRF_MATF_Info_Request........................7 Any Time Interrogation for a Ported Number – Indirect Routeing ..................46 B..................4 Call to a Ported Number – Indirect Routeing ..............066 version 5...2........................4 Information Flows .......................................................85 ETSI ................................................................................................................................60 C...................60 C........................................................................4 Process ATI_NPLR................................80 C...................2 Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing...........1 ETSI Mapping direction: ISUP to MAP....................................................................................................................................................................................4......................Direct Routeing ...........................49 B...........................................67 C.......................................51 B................................................................................1 Procedure MNP_SRF_Non_Call_Related .....................3 Functional Requirements of Network Entities ...............4.....................................................................................4 Delivery of SMS to a Ported Number – Direct Routeing ...........................Call Related Signalling...........................................................Direct Routeing – MNP-SRF acts as Higher-level Relay ...................................................4 ANSI Mapping direction: MAP to ISUP..........................58 Annex C (normative): MNP Signalling Relay Function ..................5 International SOR for a Non-ported Number ...80 C...........3...............................5 Contents of the messages ..................................................7 MNP Info Query ........................................Direct Routeing...........53 B....................3.2........................1.............2 Send Routeing Info ack ..............................4.......................................3GPP TS 23............................................4..................3 Non-call Related Signalling Message for a Ported Number ..........6 Handling of MAP to ISUP mapping (informative) .........................................................................66 C......................................................................................................................................3..9 CCBS where the Busy Subscriber is a Ported Subscriber .....................42 B..................................................................1 Handling of Call Related Signalling...............................1 Routeing Conventions ........................59 C.4........................................................Indirect Routeing ..............7 ConnectionControl:Connect .............................................................................3 Call Scenarios.........................2..3 Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network ≠Subscription Network– Direct Routeing ...83 Annex E (informative): Change history ............80 C.........................1 Call to a Non-Ported Number or Number Ported into the Network ....................4...................................

technical enhancements.y.3. corrections. updates.0 (2003-12) Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). i.z where: x the first digit: 1 presented to TSG for information. it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x. z the third digit is incremented when editorial only changes have been incorporated in the document. 3 or greater indicates TSG approved document under change control.0 Release 5 5 ETSI TS 123 066 V5. ETSI . y the second digit is incremented for all changes of substance. Should the TSG modify the contents of the present document. 2 presented to TSG for approval.e. etc.066 version 5. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval.3GPP TS 23.3.

ISDN User Part (ISUP) version 4 for the international interface. edition number. ETSI . Enhancements for the support of Number Portability". Version 2. a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.769. Intelligent Network Capability Set 1 (CS1).7. or combination of options. taking into account the regulatory and architectural constraints that may prevail. The present document does not specify the porting process. service providers. Technical realisation". switch and database manufacturers and national regulators. constitute provisions of the present document. Core Intelligent Network Application Protocol (INAP). • References are either specific (identified by date of publication. [3] 3GPP TS 23. Signalling System No. is used. Stage 1".1: "Integrated Services Digital Network (ISDN). Normative Annex A of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology.0.3.730 modified]". [7] ETSI EN 300 356-2 V4. 7 – Signalling Connection Control Part (SCCP) [connectionless services] to support international interconnection". Normative Annex C of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using Signalling Relay technology.) or non-specific.0 (2003-12) 1 Scope The present document describes several alternatives for the realisation of Mobile Number Portability. The network operator may choose the solution to be used in his network.1. 2 References The following documents contain provisions which. Service description. [4] ETSI ETS 300 009 (1991): "Integrated Services Digital Network (ISDN). Normative Annex A and Normative Annex C describe alternative solutions.018: "Basic call handling.3. It is left to operator and implementation decisions which option. [2] 3GPP TS 22. etc. ISDN User Part (ISUP). In the case of a reference to a 3GPP document (including a GSM document). subsequent revisions do not apply. [8} CTIA report on Wireless Number Portability. [6] ITU-T Recommendation Q.0 Release 5 6 ETSI TS 123 066 V5. through reference in this text. [1] 3GPP TS 21. the latest version applies. The possible implications of these options on internal node functions and on signalling performance are not covered in the present document. • For a non-specific reference. Part 1: protocol specification".066 version 5.905: "3G Vocabulary". version number.0. • For a specific reference. [5] ETSI ETS 300 374-1: "Intelligent Network (IN). Normative Annex B of the present document describes the technical realisation of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using Signalling Relay technology. CCITT Signalling System No. The present document includes information applicable to network operators.066: "Support of Mobile Number Portability (MNP).3GPP TS 23. Part 2: ISDN supplementary services [ITU-T Recommendation Q.

3GPP TS 23. mobile number portability information: an information set relevant to Mobile Number Portability for a mobile subscriber. 7 (SS7) Message Transfer Part (MTP). American National Standards for Telecommunications – Signaling System Number 7 – NumberPortability Call Completion to a Portable Number. April 1999. June 2.0 Release 5 7 ETSI TS 123 066 V5.660 – 1998. generic IMSI MSISDN. [13] American National Standard for Telecommunications . [10] ANSI T1.1 Definitions For the purposes of the present document. Number Portability Database and Global Title Translation. 3 Definitions and abbreviations 3. Number Portability Administration Center. Additional regulatory constraints apply in North America. 1997.ANSI T1. Version 2. ISDN User Part (ISUP).Service Management System (NPAC-SMS).078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 – Stage 2".e. It may contain one or more of Routeing Number.0.3. network operator: GSM PLMN operator non-call related signalling message: all signalling messages where the MSISDN is used to route the message on SCCP level except MAP SRI without OR parameter set (i. [12] American National Standard for Telecommunications – Signalling System Number 7 (SS7) - ISDN User Part (ISUP) .112.2: "Integrated Services Digital Network (ISDN).066 version 5. American National Standards for Telecommunication – Signalling System No. [17] North American Numbering Council (NANC) Functional Requirement Specification.111-1996.0 (2003-12) [9] ANSI T1. Enhancements for support of Number Portability (NP)".0.7.113-1995. CCBS_Request etc) North American GSM Number portability: the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America.096: "Mobile Name Identification Supplementary Service – Stage 2". Signalling System No. SRI_SMS. 7 (SS7) Signalling Connection Control Part (SCCP). [14] ETSI EN 302 097 V1. 1995. [15] TI .3. Send_IMSI. This may or may not be the number range holder network interrogating network entity: entity that submits a non-call related signalling message to interrogate the HLR interrogating network: network in which the interrogating network entity resides mobile number portability: ability for a mobile subscriber to change mobile network subscription within the same country whilst retaining his/her original MSISDN(s). SRI for SOR. American National Standards for Telecommunication – Signalling System No.Signalling System Number 7 (SS7) – Transaction Capabilities Application Part (TCAP) .ANSI T1.Technical Requirements No. Note: Translation Types 10 and 14 will be published in the next revision of ANSI T1.114-1996.112-1996. 3. [11] ANSI T1. donor network: subscription network from which a number is ported in the porting process. the following terms and definitions apply. number portability database: operational database (used in real time at call set-up) which provides portability information ETSI . Version 1. May 25.and Number Portability Status. [16] 3GPP TS 23. [18] 3GPP TS 23.

3.0 (2003-12) number portability location register: internal MAP application terminating function (MATF) in the MNP-SRF network entity with an (unspecified) interface with a NPDB number portability status: information indicating the status of number portability for a mobile subscriber. It may be one of: own number ported out. This network becomes the subscription network when the porting process is complete routeing number: routeing number is the data stored against the ported number or the non-ported number in the Number Portability Database.2 Abbreviations For the purposes of the present document. The Service Key value for Mobile Number Portability is administered in the MSC.164 number that can be ported between networks in one nation ported number: portable number that has undergone the porting process ported subscriber: subscriber of a ported number porting process: description of the transfer of a number between network operators recipient network: network that receives the number in the porting process.3GPP TS 23.in North America. The recipient network becomes the ”subscription network” after the completion of the porting process.3. 3. and is passed transparently to the entity holding the Number Portability Database service provider: entity that offers service subscriptions to individual subscribers and contracts with a network operator to implement services for a specific MSISDN. foreign number ported to a foreign network.0 Release 5 8 ETSI TS 123 066 V5. a PSTN or an ISDN network portable number: E. The routeing number points to Subscription Network or Recipient Network service key: service Key can identify to the entity holding the Number Portability Database that the service logic for Mobile Number Portability should apply. A service provider may contract with more than one network operator service provider portability: transfer of numbers between two unique Service Providers subscription network: network with which the customer’s Service Provider has a contract to implement the customer’s services for a specific MSISDN NOTE: The term “recipient network” is used during the porting process. foreign number not known to be ported number range holder network: network to which the number range containing the ported number has been allocated originating network: network where the calling party is located portability domain: set of GSM PLMNs in a country between which MSISDNs may be ported or a set of North American GSM Mobile networks and other subscription networks within a regulated geographical area within North America portability network: a PLMN or .066 version 5. the following abbreviations apply: CCBS Call Completion on Busy Subscriber CCF Call Completion Function CdPA Called Party Address CgPA Calling Party Address CNAP Calling Name Presentation CNDB Calling Name Database CRMNP Call Related Mobile Number Portability FCI Forward Call Indicator GAP Generic Address Parameter GMSC Gateway MSC GMSCB The GMSC in HPLMNB GTT Global Title Translation HLR Home Location Register HPLMNB The subscription network of the B subscriber ETSI . own number not ported out. foreign number ported in.

add an entry in the Number Portability Database.066 version 5. 4 General 4. by operators of other national UMTS or GSM networks as follows: a) if the number range holder network is identical with the donor network: add an entry in the HLR.3. as an option.1 Overview Mobile Number Portability (MNP) is the ability for a UMTS or GSM mobile subscriber to change the subscription network within a portability domain whilst retaining her original MSISDN or MSISDNs. ETSI . North American GSM Number Portability (NAGNP) is the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America. donor network.3GPP TS 23. recipient network and. As part of the porting process administrative actions have to be performed by the network operators of the number range holder network. Recipient network: add an entry in the Number Portability Database. Other networks in the portability add an entry in the Number Portability Database (if direct routeing is domain: used).0 Release 5 9 ETSI TS 123 066 V5.905: "3G Vocabulary". Donor network: delete the entry related to the ported MSISDNs in the HLR.0 (2003-12) IAM Initial Address Message IDP Initial Detection Point IE Information Element INE Interrogating Network Entity IF Information Flow IPLMN Interrogating PLMN MATF MAP application Terminating Function MNP Mobile Number Portability MNP-SRF Signalling Relay Function for support of MNP MSA Mobile Station of the A subscriber MSB Mobile Station of the B subscriber MSC Mobile-services Switching Centre MSISDN Mobile Station International ISDN Number MSRN Mobile Station Roaming Number NANP North American Numbering Plan NAGNP North American GSM Number Portability NPDB Number Portability Database NPLMN The number range holder network of the B subscriber NPLR Number Portability Location Register OQoD Originating call Query on Digit Analysis PLMN Public Land Mobile Network QoHR Query on HLR Release RN Routeing Number SMS Short Message Service SOR Support of Optimal Routeing SRI Send Routeing Information STP Signalling Transfer Point TQoD Terminating call Query on Digit Analysis TT Translation Type VMSC The Visited MSC VMSCB The VMSC of the B subscriber Further GSM related abbreviations are given in 3GPP TS 21.3.

all the portability networks and transit networks affected must fulfil the following requirements: 1. The present document does not specify the porting process. Termination of a subscription for a ported number results in the deletion of any entry in an HLR and NPDB of that number. IN. Other networks in the portability update the Number Portability Database (if an entry for the ported domain: MSISDN exists). In general. Within a portability domain the method how to convey the Routeing Number in the IAM between two portability networks shall be agreed upon by the two network operators involved (for an ITU-T ISUP solution see [6] and for an ANSI ISUP solution see [8] and [9]). In these cases. For messages that do not cross network boundaries the SCCP addressing mechanism is a choice of the network operator.g. It specifies the functionality needed to set-up calls to both ported and non ported subscribers including the functionality needed to query an NPDB for MNP information (in order to be able to charge correctly for CAMEL pre-paid calls and SMS) (Normative Annex A and Normative Annex C). add an entry in the Number Portability Database. Note that the order of sequence for the administrative actions to be performed both within a network and by different network operators is significant with respect to prevention of disruption in service to the mobile subscriber and prevention of looping calls between networks during the porting process. The subscription network must be able to generate the SRI ack to allow the onward routeing of the call from the number range holder network to the subscription network.3. delete any entry related to the ported MSISDN in the Number Portability Database. Number range holder network: update the Number Portability Database Donor network: delete (or update) the entry in the Number Portability Database.0 Release 5 10 ETSI TS 123 066 V5.e. 2. If a call fails because databases are not correctly synchronised. The SCCP interfaces between networks in a portability domain must be agreed. In the rest of the possible architectures for MNP. network architectures used within one portability network (e. ETSI . SRI for national calls) to the subscription network.g. MNP-SRF) are regarded as operator dependent. the network entity that detects the inconsistency will raise an MNP specific alarm to the operation and maintenance subsystem. delete the entry related to the ported MSISDNs in the HLR. c) if the number range holder network is different from both the recipient and the donor network: Recipient network: add an entry in the HLR. natures of address and translation types for call-related MAP messages).3. number lengths. If this solution is selected by at least one network operator within a portability domain. IN-based and MNP-SRF (call-related) solutions are compatible and may coexist in the same portability domain.3GPP TS 23. and the functionality needed to relay non-call related signalling messages to the HLR in the subscription network (Normative Annex B) . no interworking problems have been identified. delete the entry related to the ported MSISDNs in the HLR. This refers to the SCCP addressing mechanism being used (e.066 version 5.0 (2003-12) b) if the number range holder network is identical with the recipient network: Recipient network: add an entry in the HLR.2 Compatibility The IAM sent to the subscription network may contain additional routeing information. 4. Donor network: delete any entry related to the ported MSISDN in the Number Portability Database. The only restriction refers to the case where the number range holder network relays call-related MAP messages (i. Other networks in the portability delete any entry related to the ported MSISDN in the Number domain: Portability Database.

However.112-1996 SCCP recommendations for North America. on the type of message (call-related. or terminate the dialogue and response to the INE. indirect routeing or indirect routeing with reference to the Subscription network. SCCP messages sent to an HLR may be relayed by an MNP-SRF. It should be noted that the use of the SCCP hop counter requires the use of non segmented SCCP XUDT messages as defined in ITU-T 1996 SCCP recommendations or in the ANSI T1. In order to guard against the possibility that the porting data for an MSISDN is inconsistent between PLMNs in a porting domain. It shows the SCCP routeing principle for mobile number portability within a network. indirect routeing can interwork successfully with direct routeing if the routeing number is transferred in the IAM or if dedicated traffic connections are used. 4.3. Therefore Normative Annex A of the present document does not mention the MNP-SRF. Note that call related messages in the IN-based solution are not routed to the MNP-SRF. the MNP-SRF may modify the SCCP called party address and route the message to a different HLR or to the subscription network.3.3GPP TS 23.3 Common Functionality of the MNP-SRF In a PLMN that supports mobile number portability. the usage of the IN-based solution for the call-related messages should allow operators to have the routeing of the non call-related messages determined in the same database.0 Release 5 11 ETSI TS 123 066 V5. ETSI .0 (2003-12) In order to avoid loops and incompatibility situations. reference [11]. See [7] for the description of the access of the MNP- SRF (node with relay capability) to the NPDB (external database). all the networks within a portability domain shall use the same routeing convention either direct routeing. the SCCP hop counter may be used to prevent indefinite looping of messages between PLMNs. The MNP-SRF would then decrement the SCCP hop counter for every message that is relayed. Depending on the implemented solution (IN-based or MNP-SRF-based).066 version 5. non-call- related or MNP information request) and on the porting status of the called subscriber. Figure 1 shows the general steering functionality for SCCP message routeing. As an alternative.

3.3. The test “MNP info-request” is a test on the SCCP Translation Type if a dedicated Translation Type value for MNP information request messages is used in the network.3GPP TS 23. Note that in networks which support the IN-based solution for call related signalling. a distinction on SCCP level for call related and non-call related messages is needed and that the MNP-SRF does not require to include MATF’s since call related messages and MNP information request messages are not terminated at the MNP-SRF. ETSI .0 Release 5 12 ETSI TS 123 066 V5. MNP_SRF_Non_Call_Related and MNP_SRF_MATF_Info_Request are described in Normative Annex C and Normative Annex B of the present document. The handling of SCCP messages in the MNP-SRF in networks which do not make use of a dedicated Translation Type value for MNP information request messages is for further study.066 version 5.0 (2003-12) Process SCCP_Steering_Function 1(1) general Steering Function for SCCP routeing Idle SCCP message OPTION IN-based MNP-SRF-based call related no yes SCCP SCCP SCCP to HLR to MNP-SRF to MNP-SRF message message message Idle Idle Idle Figure 1: Steering Function for SCCP Message routeing Figure 2 shows the process MNP_SRF in the MNP-SRF. The procedures MNP_SRF_MATF_Call_Related.

3.3GPP TS 23.0 (2003-12) The test "call-related" is a test on the SCCP Translation Type if a dedicated Translation Type value for call related messages is used in the network.066 version 5.3.0 Release 5 13 ETSI TS 123 066 V5. Process MNP_SRF 1(1) Process in the MNP_SRF to relay SCCP messages IDLE SCCP message MNP info request yes no see Annex C MNP_SRF_MATF _Info_Request IDLE call-related no yes MNP_SRF_MATF see Normative Annex C _Call_Related terminate? yes no MNP_SRF_Non_ see Annex B IDLE Call_Related terminate? yes SCCP no message IDLE SCCP IDLE message IDLE Figure 2: Process MNP_SRF ETSI . The handling of SCCP messages in the MNP-SRF in networks which do not make use of a dedicated Translation Type value for call related messages is for further study.

The following action in the different networks can be identified: 1. calls are routed from the originating network to the number range holder network. 3. Indirect Routeing of calls is a PLMN option which allows to route calls from the PLMN supporting this option via the number range holder network to the ported subscriber's subscription network. The architecture for non-call related signalling is described in Normative Annex B of the present document. If the call is originated outside the portability domain.3. Indirect Routeing of calls with reference to the subscription network is a PLMN option for PLMN operators having chosen the MNP-SRF solution for call related signalling described in Normative Annex C.066 version 5.0 Release 5 14 ETSI TS 123 066 V5. If all PLMNs within a portability domain support this option. The number range holder network obtains onward routeing information from the subscription network and routes the call onward to the ported subscriber's subscription network. If the call is originated in another national network and the other national network does not support originating call query (i. the IAM (1) is received by the number range holder network. Direct Routeing of calls is a PLMN option that allows to route calls directly from the PLMN supporting this option to the ported subscriber's subscription network.e. SRI (4) Number range Subscription holder network SRI ack (5) network IAM(1) IAM (8) IAM (6) IAM (3) IAM (2) IAM (7) Other national Portability domain network Figure 3: General architecture of a portability domain for routeing of calls The following routeing conventions are identified: 1.0 (2003-12) 5 Common Architecture for call setup Figure 3 shows the general architecture of a portability domain for routeing of calls.3GPP TS 23. The more detailed architecture within the networks depends on the chosen solution (IN-based or MNP/SRF-based) and options and is described in Normative Annex A and Normative Annex C of the present document. 2a. 2.3. the IAM (2) is received by the number range holder network. Indirect Routeing of calls is applicable). ETSI .

066 version 5. and the number range holder network supports the IN solution described in Normative Annex A of the present document or the MNP-SRF/MATF solution with the option 'MATF inside number range holder network' described in Normative Annex C of the present document. If the routeing number is not used in the IAM sent from the national originating network to the subscription network. and the number range holder network supports the MNP-SRF/MATF solution with the option 'MATF in subscription network' described in Normative Annex C of the present document (i. Direct Routeing of calls is applicable). If the call is originated in the subscription network and the subscription network does not support originating call query (i. The subscription network returns SRI ack (5) containing the routeing number. all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. 3b. the number range holder network sends SRI (4) to the subscription network. If the routeing number is not used in the IAM sent from the number range holder network to the subscription network. 3c.3. 4a. If the call is routed via the number range holder network. it sends an IAM (8) containing the MSRN to the visited network of the called subscriber. The number range holder network then sends IAM (6) containing the routeing number to the subscription network. If the call is routed via the number range holder network. it sends an IAM (8) containing the MSRN to the visited network of the called subscriber.0 (2003-12) 2b.e. If the call is originated in the subscription network and the subscription network supports originating call query (i. If the call is originated in another national network and the other national network supports originating call query (i. Direct Routeing of calls is applicable).e. Indirect Routeing of calls is applicable). ETSI .3GPP TS 23.3. If the subscription network receives IAM (6 or 7) containing the routeing number.e. the IAM (7) containing the routeing number is sent to the subscription network. 3a. the IAM (3) is received by the number range holder network.e.0 Release 5 15 ETSI TS 123 066 V5. all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. the number range holder network sends IAM (6) containing the routeing number to the subscription network. 4b. Indirect Routeing of calls with reference to the subscription network is applicable).

0 (2003-12) 6 Functional requirements of network entities 6. It is called from the process MT_GMSC defined in 3G TS 23.3.3.066 version 5.0 Release 5 16 ETSI TS 123 066 V5. Procedure MNP_MT_GMSC_Set_MNP_Parameters 1(1) No IAM parameters indicate that NPDB query has been done Yes Mark NPDB query done Figure 4: Procedure MNP_MT_GMSC_Set_MNP_Parameters ETSI .3GPP TS 23.1 Procedure MNP_MT_GMSC_Set_MNP_Parameters The procedure MNP_MT_GMSC_Set_MNP_Parameters is shown in figure 4.018 [3].

It is called from the process MT_GMSC defined in 3G TS 23.2 Procedure MNP_MT_GMSC_Check_MNP_Indicators The procedure MNP_MT_GMSC_Check_MNP_Indicators is shown in figure 5.3GPP TS 23.018 [3].0 (2003-12) 6.066 version 5.0 Release 5 17 ETSI TS 123 066 V5.3.3. Procedure MNP_MT_GMSC_Check_MNP_Indicators 1(1) NPDB query check supported OPTION Yes No NPDB query is No marked done Yes Result:= Result:= Fail Routeing number Figure 5: Procedure MNP_MT_GMSC_Check_MNP_Indicators ETSI .

3 Procedure MNP_SRF_Check_MNP_Indicator The procedure MNP_SRF_Check_MNP_Indicator is shown in figure 6.066 version 5. Procedure MNP_SRF_Check_MNP_Indicator 1(1) Check NPDB query in MNP-SRF? yes no previous NPDB query is done? no yes set: terminate Figure 6: Procedure MNP_SRF_Check_MNP_Indicator ETSI .3GPP TS 23. It is called from the procedures MNP_SRF_Non_Call_Related and MNP_SRF_MATF_Call_Related.0 (2003-12) 6.3.3.0 Release 5 18 ETSI TS 123 066 V5.

An IN-based solution for querying the NPDB may also be used by the gsmSCF in order to be able to apply different charging tariffs for CAMEL pre-paid subscribers’ calls or short messages established/sent when roaming in their home PLMN and directed to ported and non-ported mobile subscribers.3. This can be for several reasons like for example: . ANSI IN Query.2 shows the architecture for a call to a number that is not subject for portability. In a GSM network which supports the IN-based approach for call related MNP. ETSI Core INAP ii.1 Network Options There are two IN-based solutions for querying the NPDB :- i.3GPP TS 23. ETSI . Terminating call Query on Digit Analysis (TQoD). the national regulator has stipulated some number series as being non-portable or. Note that for different number ranges different options may be chosen. it is a network operator decision. Query on HLR Release (QoHR). The interworking between the CCF and the SSF for MNP is for further study. Originating call Query on Digit Analysis (OQoD).0 Release 5 19 ETSI TS 123 066 V5.1 Architecture A. each GMSC shall support at least one of these options.3. In a GSM network that supports the IN-based approach for call related MNP. depending on whether or not the called and the calling subscriber subscribe to the same PLMN. The following network operator options are defined for the MT calls in the GMSC: .2 No NP Query required – Number is not subject for portability Figure A. The following network operator option is defined for MO calls in VMSCA and for forwarded calls in the GMSC and VMSCB: . . …… A. taking into account the regulatory and architectural constraints that may prevail. whether or not VMSCs and GMSCs support this option. . in an initial phase only a limited amount of subscribers might port in certain number blocks and some operators might want to treat the call routeing according to traditional routeing plans without any change.0 (2003-12) Annex A (normative): IN Call-Related Technical Realisation A.1.1.1.066 version 5. The use of OQoD in transit switches in a PLMN while avoiding multiple database interrogations is for further study.

2: Call to a non-ported number. it requests routeing information by submitting a MAP SRI to the HLRB including the MSISDN in the request. 3 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered.3.3.1.066 version 5. 6 GMSCB uses the MSRN to route the call to VMSCB.1 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions.1.0 (2003-12) (Inter)national Number range holder/ Visited network Originating network subscription network HLRB 4 2 5 3 Originating 1 GMSCB 6 VMSCB/ Exchange VLRB Figure A.1 TQoD – Number is not ported Figure A. A. 4 The MSC/VLRB returns an MSRN back to the HLRB.0 Release 5 20 ETSI TS 123 066 V5. The call is routed to the Number range holder network being the Subscription network.3 NP Query in Number Range Holder Network A.3. no NP query required 1 From an Originating Exchange a call is set up to MSISDN. ETSI .1.1.3GPP TS 23. 5 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN.3. 2 When GMSCB receives the ISUP IAM.

3GPP TS 23. Note that the NPDB may be outside the number range holder network if a shared NPDB is used.3. it will send a database query to the NPDB as a result of analysis of the received MSISDN.1: Call to a non-ported number using TQoD procedure 1 From an Originating Exchange a call is set up to MSISDN.0 Release 5 21 ETSI TS 123 066 V5.066 version 5.3. The MSISDN is included in the query to the NPDB. 7 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. including the MSISDN in the request. The call is routed to the Number range holder network being the Subscription network.3.3. 6 The MSC/VLRB returns an MSRN back to the HLRB.1. 4 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB. 3 The NPDB detects that the MSISDN is not ported and responds back to the GMSCB to continue the normal call setup procedure for MT calls.2 TQoD – Number is ported Figure A. 2 When GMSCB receives the ISUP IAM.2 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. 5 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber owning the MSISDN currently is registered.1. A. 8 GMSCB uses the MSRN to route the call to VMSCB.0 (2003-12) (Inter)national Number range holder/ subscription network Visited network Originating network HLRB NPDB 6 4 2 5 3 7 Originating 1 GMSCB 8 VMSCB/ Exchange VLRB Figure A.3.1. ETSI .

5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB.0 (2003-12) (Inter)national Number range holder Subscription network Visited network Originating network network HLRB NPDB 7 5 2 6 3 8 Originating 1 GMSCA 4 GMSCB 9 VMSCB/ Exchange VLRB Figure A.066 version 5. 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. The capability to route messages to the correct HLR is required.3. The call is routed to the Number range holder network. 2 When GMSCA receives the ISUP IAM.3GPP TS 23. it will send a database query. Note that the NPDB may be outside the number range holder network if a shared NPDB is used. 3 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network.1.1.0 Release 5 22 ETSI TS 123 066 V5.1.3 QoHR – Number is ported Figure A. including the MSISDN in the request.3.3. including the MSISDN. 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 7 The MSC/VLRB returns an MSRN back to the HLRB.3. 9 GMSCB uses the MSRN to route the call to VMSCB. also the MSISDN is included in IAM. to the NPDB as a result of analysis of the received MSISDN.2: Call to a ported number using TQoD procedure 1 From an Originating Exchange a call is set up to MSISDN.3 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. 4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message. ETSI .3. A.

3GPP TS 23. 9 The MSC/VLRB returns an MSRN back to the HLRB. including the MSISDN in the query. 2 When GMSCA receives the ISUP IAM. The call is routed to the Number range holder network.1.066 version 5. A.1. this will trigger the sending of a database query to the NPDB.4 NP Query in Originating Network A.3. 4 When GMSCA receives the error indication form the HLRA. including the MSISDN in the request. The capability to route messages to the correct HLR is required. Note that the NPDB may be outside the number range holder network if a shared NPDB is used. ETSI . 10 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN.4. 3 The HLRA returns a MAP SRI ack with an “Unknown Subscriber” error since no record was found for the subscriber in the HLRA.1. 11 GMSCB uses the MSRN to route the call to VMSCB. 8 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 6 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message.3. it requests routeing information by submitting a MAP SRI to the HLRA including the MSISDN in the request.0 Release 5 23 ETSI TS 123 066 V5. 5 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network. also the MSISDN is included in IAM.1 OQoD – Number is not ported Figure A.3: Call to a ported number using QoHR procedure 1 From an Originating Exchange a call is set up to MSISDN.1 shows the architecture for a call where already the Originating network has the knowledge whether the MSISDN is ported or not and can route the call directly to the Subscription network that in this case is the same as the Number range holder network.3. 7 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB.0 (2003-12) (Inter)national Number range holder Subscription network Visited network Originating network network HLRA HLRB NPDB 9 2 7 4 8 3 10 5 Originating 1 GMSCA 6 GMSCB 11 VMSCB/ Exchange VLRB Figure A.4.1.

3GPP TS 23.066 version 5.3.0 Release 5 24 ETSI TS 123 066 V5.3.0 (2003-12)

National Originating Number range holder/ Visited network
network Subscription network

HLRB
NPDB
7
5
2

6
8
3

1 VMSCA 4 GMSCB 9 VMSCB/
VLRB

Figure A.1.4.1: Call to a non-ported number using OQoD procedure

1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called
subscriber.

2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of
analysis of the received MSISDN, including the MSISDN in the query.

3 The NPDB detects that the MSISDN is not ported and responds back to the VMSCA to continue the normal call
setup procedure for MO calls. Depending on database configuration option, the NPDB could either return a
Routeing Number on not ported calls, as done for ported calls, or the call is further routed using the MSISDN
number only towards the Number range holder network.

4 The call is routed to the Number range holder/Subscription network based on the MSISDN or Routeing Number
carried in ISUP IAM message.

5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in
the request.

6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered.

7 The MSC/VLRB returns an MSRN back to the HLRB.

8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN.

9 GMSCB uses the MSRN to route the call to VMSCB.

Note that the NPDB may be outside the national originating network if a shared NPDB is used.

A.1.4.2 OQoD – Number is ported
Figure A.1.4.2 shows the architecture for a call where already the Originating network has the knowledge that the
MSISDN is ported and can route the call directly to the Subscription network without involving the Number range
holder network.

ETSI

3GPP TS 23.066 version 5.3.0 Release 5 25 ETSI TS 123 066 V5.3.0 (2003-12)

National Subscription network
Originating network Visited network

HLRB

NPDB
7
5

2
6
8
3

1 VMSCA 4 GMSCB 9 VMSCB/
VLRB

Figure A.1.4.2: Call to a ported number using OQoD procedure

1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called
subscriber.

2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of
analysis of the received MSISDN including the MSISDN in the query.

3 The NPDB detects that the MSISDN is ported and responds back to the VMSCA with a Routeing Number
pointing out the Subscription network.

4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message;
also the MSISDN is included in IAM.

5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in
the request. The capability to route messages to the correct HLR is required.

6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered.

7 The MSC/VLRB returns an MSRN back to the HLRB.

8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN.

9 GMSCB uses the MSRN to route the call to VMSCB.

Note that the NPDB may be outside the national originating network if a shared NPDB is used.

A.1.4.3 IN-Query for CAMEL pre-paid service
Figure A.1.4.3 shows the architecture for a call or MO-Short-Message originated by a CAMEL pre-paid subscriber
while roaming in the Home PLMN where the gsmSCF needs to know whether or not calling and called subscriber
subscribe to the same PLMN in order to apply the correct charging tariff.

ETSI

3GPP TS 23.066 version 5.3.0 Release 5 26 ETSI TS 123 066 V5.3.0 (2003-12)

National
Originating network

NPDB
3 4

gsmSCF

2 5

1 VMSCA 6

Figure A.1.4.3: IN-Query for pre-paid service

1 A call or short message is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of
the called subscriber.

2 When VMSCA receives the call setup indication, it will send a CAP IDP message to the gsmSCF. The IDP
contains the called party’s MSISDN.

3 If the calling subscriber roams in her Home PLMN and the called subscriber’s MSISDN indicates that the called
subscriber subscribes to a PLMN within the calling subscriber’s Home Country, the gsmSCF queries the NPDB
based on the called party’s MSISDN.
Otherwise the tariff to be applied does not depend on the called subscriber’s porting status and enough
information to apply the correct tariff is available; go to 5.

4 The NPDB returns a routing number to the gsmSCF pointing out the called subscriber’s subscription network.
Based on this information the gsmSCF applies the appropriate tariff for pre-paid subscriber A.

5 The gsmSCF returns CAP AC and CAP CUE messages to the VMSCA.

6 The call or short message is set up.

Note that the NPDB and gsmSCF may be integrated within one physical entity.

ETSI

3GPP TS 23.066 version 5.3.0 Release 5 27 ETSI TS 123 066 V5.3.0 (2003-12)

A.2 Information flows
In the following figures the NPDB is shown as belonging to the Number range holder network or to the national
originating network. However, the NPDB may be shared within one portability domain i.e. nation-wide.

Figure A.2.1 shows the information flow for successful QoHR.

Number range holder network subscription network visited network
GMSC HLR NPDB GMSC HLR VLR VMSC
IAM
---- 
SRI
--- 
neg.
result
----
"query"
------------------------ 
"routing"
------------------------
IAM


--------------------------------------------

SRI
---- 
PRN
---- 
PRN
ack
----
SRI
ack
----
IAM
-------------------------------------------- 
Figure A.2.1

ETSI

3.2 shows the information flow for unsuccessful QoHR (unallocated number).066 version 5.  negative result ---------------- "query" -------------------------------------------------------------. Number range holder network GMSC HLR NPDB IAM ----------------.0 (2003-12) Figure A.2.2.3.  SRI ---------------.0 Release 5 28 ETSI TS 123 066 V5.3GPP TS 23.  "result" -------------------------------------------------------------- REL ---------------- Figure A.2 ETSI .

 "routing" ------------------------ IAM  -------------------------------------------- SRI ---.2.3GPP TS 23.066 version 5.  PRN ---.2.3. Number range holder network subscription network visited network GMSC HLR NPDB GMSC HLR VLR VMSC IAM ---.3 shows the information flow for successful TQoD.3.0 (2003-12) Figure A.  "query" -----------------------.3 ETSI .0 Release 5 29 ETSI TS 123 066 V5.  PRN ack ---- SRI ack ---- IAM -------------------------------------------.  Figure A.

2. Number range holder network visited network GMSC HLR NPDB VLR VMSC IAM ------.3GPP TS 23.2.0 Release 5 30 ETSI TS 123 066 V5.3.4 ETSI .3.  PRN ------------------------------------ PRN ack ------------------------------------ SRI ack ------- IAM -------------------------------------------------------------------------------------------.  Figure A.0 (2003-12) Figure A.066 version 5.  "query" ----------------------------------- "result" ----------------------------------- SRI ------.4 shows the information flow for unsuccessful TQoD (number not ported).

0 (2003-12) Figure A.  PRN ack ----- SRI ack ----- IAM ----------------------------------------------------.5 shows the information flow for successful OQoD (number ported).3.  "query" -----.2.  SRI ----.3.0 Release 5 31 ETSI TS 123 066 V5.  "routin g" ----- IAM ---------------------------.2.3GPP TS 23.  PRN ----.  Figure A.066 version 5.5 ETSI . National originating network A subscription network B visited network B VMSC NPDB GMSC HLR VLR VMSC Set-up ----.

0 Release 5 32 ETSI TS 123 066 V5. originating network Number range holder network VMSCA NPDB GMSC Set-up ---------------.  "query" ---------------.  "routing" ---------------- IAM ---------------------------------------------------------------.3GPP TS 23.2.3.2.2.3 and A.2.2.2.0 (2003-12) Figure A.3.066 version 5.1. A.2.6 shows the information flow for unsuccessful OQoD (number not ported in).6 ETSI .  continue as shown in figures A.4 Figure A. A.

1 Functional requirement of GMSC A.066 version 5.0 (2003-12) A.3. ETSI .3GPP TS 23. The query to NPDB contains the service key for MNP query and the called party’s MSISDN.3.3.3 Functional requirements of network entities A. It is called from the procedure Obtain_Routeing_Address defined in 3G TS 23. it does not duplicate the information in the SDL diagrams.018 [3].3.1.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR The procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is shown in figure A.3. The text in this clause is a supplement to the definition in the SDL diagrams.1.0 Release 5 33 ETSI TS 123 066 V5.

1.0 Release 5 34 ETSI TS 123 066 V5.3.1: Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR ETSI .0 (2003-12) Procedure MOBILE_NUMBER_PORTABILITY_QoHR 1(1) Procedure in the GMSC Signals to/from the to handle Query on HLR Release right are to/from the NPDB for Mobile Number Portability QoHR yes no NPDB query is marked done yes no called party number within porting out number range no yes Result := "query" not ported Wait negative Response Abort "result" "routing" Result := Result := not ported Number ported Figure A.3GPP TS 23.3.066 version 5.3.

The "query" to NPDB contains the service key for MNP query and the called party’s MSISDN.1. it does not duplicate the information in the SDL diagrams.3.3.0 Release 5 35 ETSI TS 123 066 V5.066 version 5.2 Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD The procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD is shown in figure A.0 (2003-12) A.3.018 [3]. Procedure MOBILE_NUMBER_PORTABILITY_TQoD 1(1) Procedure in the GMSC to handle Terminating call Query on Digit Analysis for Mobile Number Portability Signals to/from the right are to/from the NPDB OR false true TQoD yes no NPDB query is marked done yes no called party number within porting out number range no yes Result := IDP not ported NPDB Query Wait negative Abort Continue Connect Response Result := Result := not ported Number ported Figure A. The text in this clause is a supplement to the definition in the SDL diagrams.2: Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD ETSI .3.1. It is called from the procedure Obtain_Routeing_Address defined in 3G TS 23.1.2.3GPP TS 23.3.

ETSI .066 version 5. The MSC may recognise own numbers as not being within the ported number range.3. the MSC will not in general know whether the number is portable. The test “called party number is a portable national MSISDN” takes the “yes” exit if the number is a foreign national MSISDN or an own portable MSISDN.2.2. It is called from the procedure Outgoing_Call_Setup_MSC and from the process MT_CF_MSC defined in 3G TS 23.0 (2003-12) A.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD The procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is shown in figure A.3.3GPP TS 23.3.018 [3].3.0 Release 5 36 ETSI TS 123 066 V5.3. it does not duplicate the information in the SDL diagrams.2 Functional requirement of MSC A. The "query" to NPDB contains the service key for MNP query and the called party’s MSISDN. For foreign numbers however. The text in this clause is a supplement to the definition in the SDL diagrams.1.

3.3.0 (2003-12) Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD 1(1) Procedure in the MSC Signals to/from the right to handle Originating call are to/from the NPDB Query on Digit Analysis for Mobile Number Portability OQoD no yes called party number is a portable national MSISDN no yes “query” Wait negative Abort “result” “routing” Response set routeing for IAM number Figure A.2.0 Release 5 37 ETSI TS 123 066 V5.066 version 5.1: Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD ETSI .3GPP TS 23.3.

0 Release 5 38 ETSI TS 123 066 V5.3.1: Process IN_QUERY_NPDB ETSI .3 Functional requirement of NPDB A.1.3.3GPP TS 23.3.066 version 5.3.0 (2003-12) A.3.3. Process IN_QUERY_NPDB 1(1) Process in the NPDB Signals to/from the left to handle NPDB queries are to/from the MSC Idle service key indicates “query” NPDB query Syntax check on CdPA no correct? yes Set error type Check Called Party Address Portability Status Number not ported Number ported Send RN on Number Not Ported in OQoD no yes set: Routeing number negative “result” “routing” Response Idle Figure A.3.3.3.1 Process IN_QUERY_NPDB The process IN_QUERY_NPDB is shown in figure A.

A.2.0 Release 5 39 ETSI TS 123 066 V5.2 IAM for ANSI ISUP interface This message is specified in [8] and [9]. "routing". On the MSC . An optional element may be present or absent.NPDB interface A.1 INITIAL DP This message is specified in [5].2 Messages on the MSC . Messages in the MSC – NPDB interface are mapped into ETSI Core INAP or ANSI IN Query messages according to the protocols on this interface. at the discretion of the application at the sending entity. The ways in which this may be coded are shown in [14].3. conditional © or optional (O). A mandatory information element shall always be present. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. This is listed in the following table: Messages in MSC-NPDB INAP messages ANSI IN Query messages interface "query" INITIAL DP ProvideInstruction:Start "routing" CONNECT ConnectionControl:Connect CONTINUE "result" CONTINUE ConnectionControl:Connect RELEASE CALL In the tables that follow. The ways in which this may be coded are shown in [8] and [9].4.3GPP TS 23.1.4.4 Contents of messages This clause specifies the content of the following messages: On the ISUP interface: IAM. "result". A.1 Messages on the ISUP interface A. A conditional information element shall be present if certain conditions are fulfilled. A.NPDB interface: "query". if those conditions are not fulfilled it shall be absent.066 version 5. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber.3.4.4. The following information elements are required: Information element name Required Description Service Key M Identifies the requested IN service (MNP query) Called Party Number M The possibly ported MSISDN ETSI .0 (2003-12) A. information elements are shown as mandatory (M).1.1 IAM for ETSI ISUP interface This message is specified in [14].4.

2.4 CONTINUE This message is specified in [5].6 or 10 ANI digits 1 Digits (LATA) M 6 LATA ID 1 Originating Station Type M 1 Binary value of ANI II digits Note: * = Value specific for number portability 1 = This mandatory parameter is required for the message but the content is not essential for number portability.2.4.3GPP TS 23.2. missing parameter. The negative response information element can take the following values: 1.3 CONNECT This message is specified in [5]. It shall be ensured that the information in the Connect message shall be aligned with the coding supported in the ISUP signalling.2.4. ETSI .0 (2003-12) A.066 version 5. A. system failure.6 ProvideInstruction:Start Parameter Type Number of Octets Contents Package Type Identifier M 1 Query with Permission Component Type Identifier M 1 Invoke (last) Operation Code Identifier M 1 National TCAP Operation Code M 2 provideInstruction:Start (reply required) Service Key M 11* 10 digit called party number digits 1 Digits (calling party number) M 6-9 3.4.4.3. This message does not contain any information element.3.4. unexpected parameter. 2. unexpected data value.5 RELEASE CALL This message is specified in [5]. A. 3. A. 4.0 Release 5 40 ETSI TS 123 066 V5.2.2 INITIAL DP negative response This message is specified in [5]. The following information elements are required: Information element name Required Description Cause M Indicates the reason for releasing the call A.

066 version 5.3.7 ConnectionControl:Connect Parameter Type Number of Contents Octets Package Type Identifier M 1 Response Component Type Identifier M 1 Invoke (last) Operation Code Identifier M 1 National TCAP Operation Code M 2 connectionControl:Connect (no reply required) 1 Digits (Carrier) M 6 3 or 4 digit CIC Digits (Routing Number) M 9* 10 digit RN or Dialed Number 1 Billing Indicators M 4 Unspecified Note: * = Value specific for number portability 1 = This mandatory parameter is required for the message but the content is not essential for number portability.3.4.0 (2003-12) A.2.3GPP TS 23.0 Release 5 41 ETSI TS 123 066 V5. ETSI .

4) is routed to the number range holder network.1 are relayed by an MNP-Signalling Relay Function (MNP-SRF).2 Network Architecture In a PLMN that supports MNP. B.066 version 5.3. the message (2.1. If a non-call related signalling message is originated in a network inside the portability domain and this network does not support direct routeing. For further details see clause 4. this message (3) is routed to the subscription network.1. The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. ETSI . The MNP-SRF provides re-routeing capability for signalling messages addressed using the MSISDN. non-call related signalling messages as mentioned in section B. The number range holder network routes the message (5) onward to the subscription network.3.1. The number range holder network routes the message (5) onward to the subscription network.3.0 (2003-12) Annex B (normative): Handling of Non-Call Related Signalling B.1.3GPP TS 23.1 Routeing Conventions Figure B. this message (1) is received by the number range holder network.1: Routeing of non-call related signalling messages in a number portability environment If a non-call related signalling message is originated outside the portability domain. This is referred to as indirect routeing.1 illustrates the routeing of non-call related signalling messages between networks in a number portability environment.1 Handling of Non-call Related Signalling B. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further.1. Number Range Holder Subscription Network Network Message (5) Message (1) Message (4) Message (2) Message (3) Other network Portability domain Figure B. If a non-call related signalling message is originated in a network inside the portability domain and this network supports direct routeing.0 Release 5 42 ETSI TS 123 066 V5.

In case 1 the MNP-SRF relays the message to the subscription network.0 (2003-12) From the perspective of the PLMN in which the MNP-SRF resides. All other messages are routed to the number range holder network. 2 An own number not ported out. 3 A foreign number ported in. 2 and 3 are applicable: In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e.0 Release 5 43 ETSI TS 123 066 V5. 4 A foreign number ported to a foreign network.1).1. When a PLMN supports direct routeing (clause B.066 version 5.3.3.g. When a PLMN does not support direct routeing.g. ETSI . HLR and Calling Name Database. only cases 1. HLR and Calling Name Database. all non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by a PLMN in the portability domain and all non-call related signalling messages which are relayed towards the network. 5 A foreign number not known to be ported.3GPP TS 23. 4 and 5 the MNP-SRF relays the message to subscription network. In case 1. the MSISDN in the CdPA represents either: 1 An own number ported out. In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e. For this routeing convention. are routed to the PLMN’s MNP-SRF for treatment. only non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by the PLMN itself and all non-call related signalling messages which are relayed towards the network are routed to the PLMN’s MNP-SRF for treatment.

1 Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing Figure B. MNP-SRF operation is triggered.2 Signalling Scenarios B.3GPP TS 23. ETSI .3. Interrogating Number Range Holder Network Network = Subscription Network HLRB SCCP CdPA = HLRB address MNP SRFB NPDB INE 1 SCCP CdPA = MSISDN.066 version 5. When MNP-SRFB receives the message. e.0 (2003-12) B.1 shows an example where the MNP-SRF function then re-routes the message to HLRB.2.3. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information that may be retrieved from an NP database. Figure B. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message.1: MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain NOTE: that the TT may have a different value.g.2. The Interrogating Network Entity (INE) submits a non-call related signalling message.0 Release 5 44 ETSI TS 123 066 V5.2.2. TT=0 ) Figure B.1 shows the MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain.

ETSI . Figure B.066 version 5.2. If the interrogating network is the subscription network.2 Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing Figure B.e. i. MNP-SRFA and MNP-SRFB coincide.2. e. MNP-SRF operation is triggered.2 shows the MNP-SRF operation for routeing a non-call related signalling message for a ported or non- ported number where the interrogating network supports direct routeing. NOTE 2: the CdPA may have different values in the GT address and the nature of address fields. MNP-SRF operation is triggered. Interrogating Network Subscription Network HLRB SCCP CdPA = HLRB address 2 SCCP CdPA = RN (+ MSISDN). The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network.2. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database.3GPP TS 23. the signalling message passes the MNP-SRF only once.3. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. When MNP-SRFB receives the message. When MNP-SRFA receives the message.2.2: MNP-SRF operation for routeing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routeing NOTE 1: the TT may have a different value. TT=0 ) MNP MNP NPDB SRFA SRFB NPDB INE 1 SCCP CdPA = MSISDN.0 Release 5 45 ETSI TS 123 066 V5. The Interrogating Network Entity (INE) submits a non-call related signalling message.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message . TT=0 ) Figure B.3.2 shows an example where the MNP-SRF function then re-routes the message to HLRB.0 (2003-12) B.

via the number range holder network) a non-call related signalling message for a ported subscriber NOTE 1: the TT may have a different value. ETSI .3.1 Procedure MNP_SRF_Non_Call_Related Figure B. In this case the message is relayed to the subscription network.3 Non-call Related Signalling Message for a Ported Number .3. NOTE 2: the CdPA may have different values in the GT address and the nature of address fields.2. The Interrogating Network Entity (INE) submits a non-call related signalling message.1 shows the procedure MNP_SRF_Non_Call_Related. MNP-SRF operation is triggered. via the number range holder network) a non- call related signalling message for a ported subscriber. It is called from the process MNP_SRF (see chapter 4.3 shows an example where the MNP-SRF function then re-routes the message to HLRB.0 Release 5 46 ETSI TS 123 066 V5. The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. e. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message.2. TT=0 Figure B.e.3GPP TS 23.g. The check “CdPA contains own number ported out?” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF is located in and which are ported to other networks.3: MNP-SRF operation for indirectly routeing (i. Figure B.e.3.0 (2003-12) B.066 version 5. When MNP-SRFA receives the message.Indirect Routeing Figure B. B.2.3).3.3 Functional Requirements of Network Entities B. MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database. This procedure handles non-call related signalling messages.3 shows the MNP-SRF operation for indirectly routeing (i. When MNP-SRFB receives the message.2. Interrogating Number Range Holder Network Subscription Network Network HLRB SCCPCdPA = HLRB address )2 SCCPCdPA = RN (+ MSISDN). TT=0 MNP MNP NPDB SRFA SRFB NPDB INE )1 SCCPCdPA = MSISDN. This message is routed on MSISDN global title to MNP-SRFA in the number range holder network.

3. In this case the message is relayed to the subscription network.0 (2003-12) The check “CdPA contains own number not ported out?” identifies all mobile numbers from the number ranges allocated to the network the MNP-SRF is located in and which are still served by the network the MNP-SRF is located in. The check “CdPA contains foreign number ported to a foreign network?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are not served by the MNP-SRF is located in and not served by the network the number range is allocated to. ETSI .3.e. i.e. i. In this case the message is relayed to the HLR in the network. In this case the message is relayed to the HLR in the network. In this case the message is relayed to the number range holder network. i. The remaining numbers “CdPA contains number not known to be ported ?” are mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are also not served by the network the MNP- SRF is located in.066 version 5. the numbers are ported in. the numbers are not ported out.0 Release 5 47 ETSI TS 123 066 V5.e.3GPP TS 23. The check “CdPA contains foreign number ported in?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are served by the network the MNP-SRF is located in. the numbers are ported to a foreign network.

1: Procedure MNP_SRF_Non_Call_Related ETSI .0 Release 5 48 ETSI TS 123 066 V5.3.066 version 5.3GPP TS 23.0 (2003-12) Procedure MNP_SRF_Non_Call_Related Procedure in MNP_SRF to handle the Signalling Procedure Function of Mobile Relay MNP_SRF_Non_Call_Related FPAR IN/OUT Called Number Portability for Non Call Address Messages Related CdPA contains own Yes number not ported out? No CdPA contains foreign Yes number ported in? No MNP_SRF_Check_ MNP_Indicator terminate? Yes No CdPA contains own number ported out? es No CdPA contains foreign number ported to a 3rd Yes network CdPA contains a foreign number not known to be No ported! The use of a routeing number is a matter for CdPA := CdPA := CdPA := CdPA := agreement within a Routing Number Routing Number Routing Number Subscriber Database portability cluster (+ MSISDN) (+ MSISDN) (+ MSISDN) Address Figure B.3.3.

HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. 4. MNP-SRF operation is triggered. 2.4. When MNP-SRFB receives the message.4 Signalling Scenarios (informative) This (informative) chapter contains examples of signalling scenarios. ETSI .0 (2003-12) B. The MNP-SRF function then populates the CdPA with an HLRB address. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface.3GPP TS 23. The SMS-GMSC generates a routeing enquiry for SM delivery. B. TT=0 2 CgPA = SMS-GMSCA address SMS- SMSC 1 5 VMSCB 6 MSB GMSCA Forward_SM Forward_SM (VMSCB address) (MSISDN) Figure B.0 Release 5 49 ETSI TS 123 066 V5.3.4.3. VMSCB further delivers the message to MSB.1 shows the MNP-SRF operation for delivering an SMS message to a non-ported number. After modifying the CdPA.1: SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network 1. National Interrogating Network Visited Network = Subscription Network HLRB SRI_for_SM (MSISDN) CdPA = HLRB address 3 CgPA = SMS-GMSCA address SRI_for_SM ack (VMSCB address) MNP 4 CdPA = SMS-GMSCA address SRFB CgPA = HLRB address SRI_for_SM (MSISDN) CdPA = MSISDN. 5.4. The MAP SRI_for_SM message is routed to the network’s MNP-SRF. 6. 3.066 version 5. the message is routed to HLRB. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message.1 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay Figure B.

TT=0 2 5 CdPA = SMS-GMSCA address CgPA = SMS-GMSCA address CgPA = MNP-SRFB address SMS- SMSC 1 6 VMSCB 7 MSB GMSCA Forward_SM Forward_SM (VMSCB address) (MSISDN) Figure B. The MNP- SRF function then initiates a new dialogue and routes the message to HLRB.0 (2003-12) B.4. the reader is referred to [7]. ETSI .3.2 shows the MNP-SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. MNP-SRFB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC to the SMS-GMSCA.0 Release 5 50 ETSI TS 123 066 V5.3GPP TS 23. 3. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface.2: SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network 1.066 version 5. 4. The MAP SRI_for_SM message is routed to the network’s MNP-SRF.g. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message.4. For further details of the higher level relay function (e. 6. The MNP-SRF functionality analyses the MSISDN in the TCAP portion of the message and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database.3. 7. TC relay).2 Delivery of SMS to a Non-ported Number . National Interrogating Network Visited Network = Subscription Network HLRB SRI_for_SM (MSISDN) SRI_for_SM ack (VMSCB address) CdPA = HLRB address 3 4 CdPA = MNP-SRFB address CgPA = MNP-SRFB address CgPA = HLRB address MNP SRFB SRI_for_SM (MSISDN) SRI_for_SM ack (VMSCB address) CdPA = MSISDN. 5.Direct Routeing – MNP-SRF acts as Higher-level Relay Figure B. When MNP-SRFB receives the message it terminates the TCAP dialogue and an MNP-SRF operation is triggered. VMSCB further delivers the message to MSB. The SMS-GMSC generates a routeing enquiry for SM delivery.4. 2.

7.3. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. TT=0 CgPA = SMS-GMSCA address SMS- SMSC 1 6 VMSCB 7 MSB GMSCA Forward_SM Forward_SM (VMSCB address) (MSISDN) Figure B. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address.3: SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing 1. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. After modifying the CdPA. When MNP-SRFB’ receives the message. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF(s). Number Range Subscription (Inter-)national Interrogating Network Visited Network Holder Network Network SRI_for_SM ack (VMSCB address) CdPA = SMS-GMSCA address CgPA = HLRB address 5 HLRB SRI_for_SM (MSISDN) 4 CdPA = HLRB address SRI_for_SM (MSISDN) CgPA = SMS-GMSCA address CdPA = RN (+MSISDN) CgPA = SMS-GMSCA address MNP MNP 3 SRFB’ SRFB SRI_for_SMS (MSISDN) 2 CdPA = MSISDN. the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN.4. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface.3 Delivery of SMS to a Ported Number – Indirect Routeing Figure B.0 (2003-12) B.066 version 5. 2. 3. the message is routed to MNP-SRFB in the subscription network. ETSI .g. The MAP SRI_for_SM message is routed to the number range holder network’s MNP-SRF. The SMS-GMSC generates a routeing enquiry for SM delivery. VMSCB further delivers the message to MSB.4.4. If the MNP- SRF(s) use(s) a higher-level relay function (e. the reader is referred to [7].0 Release 5 51 ETSI TS 123 066 V5. For further details of the signalling relay functions.4.3.4. 4.4 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routeing. MNP-SRF operation is triggered. the message is routed to HLRB.4 Delivery of SMS to a Ported Number – Direct Routeing Figure B. When MNP-SRFB receives the message. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. MNP-SRF operation is triggered.3 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing.2. After modifying the CdPA.3GPP TS 23. then the response message will go via the MNP-SRF as shown in B. 6. 5. As the message is non-call related. TC-relay).4. B.

After modifying the CdPA.3GPP TS 23. When MNP-SRFA receives the message.0 (2003-12) The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. 2. Subscription National Interrogating Network Visited Network Network HLRB SRI_for_SM (MSISDN) 4 CdPA = HLRB address SRI_for_SM (MSISDN) CgPA = SMS-GMSCA address CdPA = RN (+MSISDN).2. If the MNP- SRFs use a higher-level relay function (e. After modifying the CdPA. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface.4. VMSCB further delivers the message to MSB.0 Release 5 52 ETSI TS 123 066 V5. ETSI . the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC.g. MNP-SRF operation is triggered. When MNP-SRFB receives the message. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. 4. then the response message will go via the MNP-SRF as shown in B. For further details of the signalling relay functions. The SMS-GMSC generates a routeing enquiry for SM delivery. 3. The MNP-SRF function then populates the CdPA with an HLRB address.3. MNP-SRF operation is triggered. the message is routed to HLRB.3. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. 5. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. the reader is referred to [7]. As the message is non-call related.066 version 5. TT=0 CgPA = SMS-GMSCA address MNP MNP 3 SRFA SRFB SRI_for_SM (MSISDN) 5 CdPA = MSISDN. The MAP SRI_for_SM message is routed to the network’s MNP-SRF.4: SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routeing 1. TC-relay). TT=0 2 SRI_for_SM ack (VMSCB address) CgPA = SMS-GMSCA address CdPA = SMS-GMSCA address CgPA = HLRB address SMS- SMSC 1 6 VMSCB 7 MSB GMSCA Forward_SM Forward_SM (VMSCB address) (MSISDN) Figure B. the message is routed to MNP-SRFB in the subscription network. 6.4. 7.

3.0 (2003-12) B. The MNP-SRF function then populates the CdPA with an HLRB address.066 version 5. 3. When HLRB receives the SRI. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. it requests routeing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialled MSISDN. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF.3GPP TS 23.4. When MNP-SRFB receives the message. If the MNP-SRF uses a higher-level relay function (e. Within the number range holder network. MSISDN) CdPA = GMSCA address 5 4 CdPA = HLRB address CgPA = HLRB address CgPA = GMSCA address MNP SRFB SRI (OR. 5. the reader is referred to [7]. International Originating/Interrogating Subscription Network Visited Network Network = Number Range Holder Network HLRB SRI ack (MSRN) SRI (OR.3. When GMSCA receives the ISUP IAM. MSA originates a call to MSISDN. TT=0 CgPA = GMSCA address 3 MSA 1 VMSCA 2 GMSCA 6 VMSCB 7 MSB IAM (MSISDN) IAM (MSRN) Figure B. GMSCA uses the MSRN to route the call to VMSCB. the message is routed to the network’s MNP-SRF. then the response message will go via the MNP-SRF as shown in B.4.2. 7.4. ETSI . For further details of the signalling relay functions. 4. 2.4. the message is routed to HLRB. VMSCA routes the call to the originating network’s GMSCA. 6.0 Release 5 53 ETSI TS 123 066 V5.5: SRF operation for optimally routeing an international call to a non-ported number 1. TC-relay). VMSCB further establishes a traffic channel to MSB. MNP-SRF operation is triggered. it responds to the GMSCA by sending back an SRI ack with a MSRN. MSISDN) CdPA = MSISDN. After modifying the CdPA.5 International SOR for a Non-ported Number Figure B.g.5 shows the MNP-SRF operation for optimally routeing an international call to a non-ported number.

2.g. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. MSISDN) 3 CdPA = MSISDN. After modifying the CdPA. TT=0 CgPA = GMSCA address MNP MNP 4 SRFB’ SRFB SRI (SOR. When MNP-SRFB receives the message. For further details of the signalling relay functions.6 shows the MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing. If the MNP- SRFs use a higher-level relay function (e. When MNP-SRFB’ receives the message. When GMSCA receives the ISUP IAM.4. it requests routeing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialled MSISDN. the message is routed to the network’s MNP-SRF. VMSCA routes the call to the network’s GMSCA. TC-relay). 8. MSA originates a call to MSISDN.0 Release 5 54 ETSI TS 123 066 V5. 4. MSISDN) 5 CdPA = HLRB address SRI (SOR.3. TT=0 CgPA = GMSCA address MSA 1 VMSCB 2 GMSCA 7 VMSCB 8 MSB IAM (MSISDN) IAM (MSRN) Figure B.4. 3.066 version 5. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database.4. the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. then the response message will go via the MNP-SRF as shown in B. 7. 6. MNP-SRF operation is triggered. MSISDN) CgPA = GMSCA address CdPA = RN (+MSISDN). As the message is non-call related.0 (2003-12) B.4. the message is routed to HLRB. Within the number range holder network. International Originating/Interrogating Number Range Subscription Visited Network Network Holder Network Network SRI ack (MSRN) CdPA = GMSCA address CgPA = HLRB address6 HLRB SRI (SOR. the message is routed to MNP-SRFB in the subscription network.3GPP TS 23. ETSI . the reader is referred to [7]. When HLRB receives the SRI. 2. The MNP-SRF function then populates the CdPA with an HLRB address. it responds to the GMSCA by sending back an SRI ack with a MSRN.6: MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing 1. After modifying the CdPA. VMSCB further establishes a traffic channel to MSB. GMSCA uses the MSRN to route the call to VMSCB.6 SOR for a Ported Number – Indirect Routeing Figure B. 5. MNP-SRF operation is triggered.3. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database.

7 Any Time Interrogation for a Ported Number – Indirect Routeing Figure B. When MNP-SRFB receives the message. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs.4. the message is routed to HLRB. Subscription Network Number Range Holder Network ATI ack CdPA = gsmSCF address CgPA = HLRB address HLRB 4 ATI (MSISDN) 3 CdPA = HLRB address CgPA = gsmSCF address gsmSCF MNP MNP 2 SRFB SRFB’ ATI (MSISDN) CdPA = RN (+MSISDN).0 (2003-12) B. TT=0 CgPA = gsmSCF address Figure B.4.4. 4. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database.3. TT=0 CgPA = gsmSCF address 1 ATI (MSISDN) CdPA = MSISDN. The gsmSCF generates an Any_Time_Interrogation (ATI) message. 2. TC-relay). After modifying the CdPA.0 Release 5 55 ETSI TS 123 066 V5. As the message is non-call related. ETSI . the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. When MNP-SRFB’ receives the message. After modifying the CdPA.7: MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network does not support direct routeing 1. MNP-SRF operation is triggered. If the MNP- SRFs use a higher-level relay function (e. The message is routed to the number range holder network’s MNP-SRF. MNP-SRF operation is triggered.7 shows the MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network does not support direct routeing. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. the reader is referred to [7].066 version 5. 3. HLRB responds to the ATI by sending back an ATI ack with the requested information. For further details of the signalling relay functions.4.g.3.2. then the response message will go via the MNP-SRF as shown in B.3GPP TS 23. The MNP-SRF function then populates the CdPA with an HLRB address. the message is routed to MNP-SRFB in the subscription network.

The MNP-SRF function then populates the CdPA with an HLRB address. TC-relay). The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. 3.3. The message is routed to the network’s MNP-SRF.0 (2003-12) B.4.4.8: MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network supports direct routeing 1. If the MNP-SRF uses a higher-level relay function (e.4. then the response message will go via the MNP-SRF as shown in B. the message is routed to HLRB.0 Release 5 56 ETSI TS 123 066 V5. Subscription Network ATI ack CdPA = gsmSCF address CgPA = HLRB address HLRB 3 ATI (MSISDN) ATI (MSISDN) 2 CdPA = HLRB address CdPA = MSISDN.8 shows the MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network supports direct routeing. After modifying the CdPA.g. HLRB responds to the ATI by sending back an ATI ack with the requested information.3GPP TS 23.066 version 5. The gsmSCF generates an Any_Time_Interrogation (ATI) message.4. ETSI .3. For further details of the signalling relay functions. the reader is referred to [7].8 Any Time Interrogation for a Ported Number – Direct Routeing Figure B.2. When MNP-SRFB receives the message. TT=0 CgPA = gsmSCF address CgPA = gsmSCF address gsmSCF MNP 1 SRFB Figure B. 2. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF. MNP-SRF operation is triggered.

4. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs.4.2. VLRA/VMSCA sends a Register_CC_Entry to HLRA using the HLRA address as CdPA on SCCP. The HLRA sends a CCBS Request message to the networks MNP-SRFA.9: MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing 1.3. As the message is non-call related. ETSI . 2.3GPP TS 23. HLRB can now respond to HLRA by sending back a CCBS ack message.9 shows the MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing.0 (2003-12) B. 6. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. the message is routed to HLRB. TT=17 5 CdPA = HLRB address CgPA = HLRA address CgPA = HLRA address 2 MNP 4 MNP SRFA SRFB CCBS Request (MSISDN) CdPA = RN (+MSISDN).3. If the MNP- SRFs use a higher-level relay function (e.Direct Routeing Figure B.4. the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. The MNP-SRF function then populates the CdPA with an HLRB address.4. Network Subscription Subscription Network visited by B visited by A Network of A Network of B CCBS Requestack CdPA = HLRA address CgPA = HLRB address 6 HLRA HLRB Register_CC_Entry CdPA = HLR address CCBS Request (MSISDN) CCBS Request (MSISDN) CgPA = VLRA address 3 CdPA = MSISDN. When MNP-SRFB receives the message. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database.g.4. TT=17 CgPA = HLRA address VLRA/ 1 VMSCB MSB VMSCA Release (cause = subscriber busy) busy Figure B. After modifying the CdPA.066 version 5. MNP-SRF operation is triggered. MNP-SRF operation is triggered. TC-relay).0 Release 5 57 ETSI TS 123 066 V5. 3. For further details of the signalling relay functions. When MNP-SRFA receives the message.9 CCBS where the Busy Subscriber is a Ported Subscriber . then the response message will go via the MNP-SRF as shown in B. 5. The VMSCA receives a ISUP Release message with cause value ‘subscriber busy’ from VMSCB. the reader is referred to [7]. After modifying the CdPA. the message is routed to MNP-SRFB in the subscription network.

After modifying the CdPA.10 Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay Figure B. An incoming call ( an Initial Address message with Generic Name parameter set to “presentation allowed” is received at a MSC. The MNP-SRF function then populates the CdPA with an CNDB address.10: SRF operation for delivering an CNAP message to the CNDB 1. The Query With Permission message is routed to the network’s MNP-SRF. The MSC inteerogates the VLR to determine if the called party is subscribed to the CNAP service. 4. National Interrogating Network = Subscription Network CNDB Query with Permission (MSISDN) CdPA = CNDB address 3 CgPA = MSCA address MNP Query with Permission ack (Calling Name) 4 CdPA = MSCA address SRFB CgPA = CNDB address Query with Permission (MSISDN) CdPA = MSISDN. When MNP-SRFB receives the message. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies which CNDB the MSISDN is populated using information which may be retrieved from an NP database. 3.066 version 5. 2.0 Release 5 58 ETSI TS 123 066 V5. The MSC can now deliver the Calling Name to the terminating subscriber .4. the message is routed to CNDB. ETSI .3GPP TS 23. CNDB responds to the routeing enquiry by sending back a Query With Permission ack with the address of the MSC.4.4. TT=5 2 CgPA = MSCA address 1 MSCA Figure B.3.3.0 (2003-12) B. The MSC generates a TCAP message ”Query With Permission”. MNP-SRF operation is triggered.10 shows the MNP-SRF operation for delivering an CNAP message to an ANSI Calling Name Database. The VLR Response indicates that the called party is subscribed to CNAP.

ETSI . 5. An own number ported out. b. all incoming calls and calls originated in the network for which the called party number is within the ranges owned by any network in the portability domain.0 Release 5 59 ETSI TS 123 066 V5. A foreign number ported to a foreign network. In cases 2 and 3. 2. In a PLMN supporting MNP with indirect routeing using signalling relay. If indirect routeing of calls with reference to the subscription network is used. the message is relayed to the MNP-SRF in the subscription network. the INE sends an MNP Information Request (ATI) such that it will be handled by the MNP-SRF in the Number Range Holder Network. the CdPA represents one of: 1. the gateway MSCs will send SRI such that it will be handled by the MNP-SRF in that network.066 version 5. 4.3GPP TS 23. the reader is referred to [7]. In a PLMN supporting MNP with direct routeing using signalling relay. a. From the perspective of the PLMN in which the MNP-SRF resides. an SRI response is sent. the INE sends an MNP Information request (ATI) such that it will be handled by the MNP-SRF in the network. A foreign number ported in. The use of an NPLR in the subscription network can only be by agreement within the number portability domain. The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. the MNP-SRF relays the message to the HLR. In case 4.1 Handling of Call Related Signalling The MAP messages affected by MNP are the MAP_SEND_ROUTING_INFORMATION (SRI) message without OR parameter set sent to the HLR and the MAP_ANY_TIME_INTERROGATION (ATI) message with parameter MNP- requestedInfo present terminated in the MNP-SRF. the MNP-SRF may perform one of the following depending on agreements within the number portability domain. containing the necessary routeing information to route the call to the subscription network. In a PLMN supporting MNP with indirect routeing. all incoming calls and calls originating in the network.3. An SRI response is sent containing the necessary routeing information to route the call to the subscription network. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further. for which the called party number is within the range owned by the network.Call Related Signalling C. For further details of the signalling relay function. A foreign number not known to be ported. This is performed by an internal MAP Application Termination Function (MATF) known as the Number Portability Location Register (NPLR). For SRI: In case 1.3. 3. whose NPLR provides the necessary routeing information in an SRI response. In a PLMN supporting MNP with direct routeing. Cases 4 and 5 are applicable only for direct routeing. An own number not ported out. where the called party number is within the ranges owned by any network in the portability domain.0 (2003-12) Annex C (normative): MNP Signalling Relay Function . the gateway MSCs will send an SRI such that it will be handled by the MNP-SRF in that network.

C.066 version 5. The remaining cases “own number ported out” are mobile numbers allocated to the network the MNP-SRF/MATF is located in and which are served by other networks. If the GMSC is not in the database own network then the enquiry has been routed from the number range holder network. an SRI response is sent. This procedure handles call-related signalling messages. C. The check “message has been relayed” identifies all call related signalling messages which are relayed from the number range holder network towards the subscription network in the case of Indirect Routeing with reference to subscription network implementation. the number is ported between two other networks. In this case the call is sent to the SRF_MATF procedure for handling.0 (2003-12) In case 5.3. The check “unknown subscriber” identifies a subscriber without any associated available information. These messages only refer to numbers ported into the network. the user error “unknown subscriber” shall be used.0 Release 5 60 ETSI TS 123 066 V5. i.2.e. the number is ported out to another network.1 Procedure MNP_SRF_MATF_Call_Related Figure C. The database query uses the MSISDN received at the application level in the SRI. In this case the call related message is sent to the SRF_MATF procedure for handling. i. In this case the call related message is relayed to the HLR in the network. The check “own number not ported out” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF/MATF is located in and which are not ported to other networks. If the GMSC is in the database own network then a routeing number is provided to route to the number range holder network. In this case the call is relayed to the MATF in the subscription network if this option is the one used by the operator. If an error must be set as a result of the check “terminate”. A response is sent to the INE containing MNP information or an error is returned.2. rather then the CdPA of the SCCP level.2 Functional Requirements of Network Entities C.e. or sent to the SRF_MATF procedure for handling if not.2 Process SRI_NPLR Figure C.3.2. containing the necessary routeing information to route the call to the number range holder network. In this case the call related message is relayed to the HLR in the network.2.3).2 shows the process SRI_NPLR. If version 3 or higher of the MAP protocol is in use. For ATI: In all cases the MNP information request (ATI) is sent to the MNP_SRF_MATF_Info_Request procedure/ MAP Application Termination Function (MATF) for handling. then the diagnostic “NPDB mismatch” may be used. so the call should fail. It is called from the process MNP_SRF (see clause 4. The check “foreign number ported to foreign network” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are not served by the network the MNP-SRF is located in and not served by the network the number range is allocated to.2 shows the procedure MNP_SRF_MATF_Call_Related.2. ETSI . The check “foreign number ported in” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are served by the network the MNP-SRF/MATF is located in. The check “foreign number not known to be ported” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are also not served by the network the MNP-SRF/MATF is located in.3GPP TS 23.

0 (2003-12) The check “HPLMN MSISDN Range” identifies if the MSISDN received in the SRI exists in a MSISDN Range owned by the HPLMN.066 version 5.3 Procedure MNP_SRF_MATF_Info_Request Figure C.3. C. ETSI .3GPP TS 23.2 shows the process ATI_NPLR.4 Process ATI_NPLR Figure C.3. This procedure handles an information request signalling message to provide MNP information for a subscriber. The database query uses the MSISDN received at the application level in the ATI.2. The check “HPLMN RN Range” identifies if the Routeing Number assigned to the MSISDN within the SRI_NPLR is assigned to the HPLMN. C. rather than the CdPA of the SCCP level.1 shows the procedure MNP_SRF_MATF_Info_Request.0 Release 5 61 ETSI TS 123 066 V5.3. It is called from the process MNP_SRF (see clause 4.2.3). This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the RN+MSISDN.2.3. This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the MSISDN.2.

066 version 5. terminate ported out Indirect Routeing with Reference to Subscription Network OPTION no Indirect Routeing with Reference yes MATF to Subscription Network OPTION no yes MATF routeing SCCP error error handling set: CdPA:= RN set: terminate + MSISDN terminate Figure C. not ported out yes no foreign number.0 (2003-12) Procedure MNP_SRF_MATF_Call_Related 1(1) Procedure in the MNP- SRF for call related signalling no Query message has Database been relayed yes own number.0 Release 5 62 ETSI TS 123 066 V5.3. ported to other foreign yes network no CdPA := MATF HLR address set: must be own number.2: Procedure MNP_SRF_MATF_Call_Related ETSI .3. ported in yes no foreign number. not known to be ported yes no foreign number.2.3GPP TS 23.

3.066 version 5.0 (2003-12) Procedure MATF 1(1) this includes passing perform the operation (SRI) TCAP handling to the application Figure C.1: Procedure MATF ETSI .3GPP TS 23.2.2.0 Release 5 63 ETSI TS 123 066 V5.3.

no Ported in GSMC in own no yes network yes MNP_SRF_Check_ MNP_Indicator yes terminate no unknown Check HPLMN subscriber Check HPLMN no RN RANGE yes MSISDN RANGE OPTION RN in HPLMN OPTION DN in HPLMN RN Ranges MSISDN Range yes no no yes yes yes no no Set: error omit routeing OPTION number Unknown Subscriber yes no pointing to subscription Set: RN Set: Set: RN pointing to number network (+MSISDN) MSISDN (+MSISDN) range owner network Set: error SRI ack to MAP process Figure C.0 Release 5 64 ETSI TS 123 066 V5.2.0 (2003-12) Process SRI_NPLR 1(1) Process in the NPLR to handle an incoming SRI IDLE SRI from MAP process yes data missing no unexpected yes data no Query Database Foreign number.066 version 5.3GPP TS 23.3.3.2.2: Process SRI_NPLR ETSI .

3.0 Release 5 65 ETSI TS 123 066 V5.1: Procedure MATF_Info_Request ETSI .3GPP TS 23.3.3.0 (2003-12) Procedure MNP_SRF_MATF_Info_Request 1(1) this includes passing perform the operation (ATI) TCAP handling to the application Figure C.066 version 5.2.

3GPP TS 23. The message flows for the following scenarios are based on the use of an SCCP relay function in MNP-SRF(s).0 (2003-12) Process ATI_NPLR 1(1) Process in the NPLR to handle an incoming ATI Idle ATI From MAP process ATI no accepted? yes Unexpected yes data no data missing yes no Query Database MSISDN no known? yes Set error Set error:= Unknown Set MNP subscriber information See 3G TS 23.078 ATI negative ATI negative ATI Ack Response To MAP process Response Idle Figure C.3 Call Scenarios The notation TT=SRI in diagrams in this section assumes that SRI=CRMNP for ETSI and SRI = Translation Type 14 for ANSI.2.3. The message flows for the higher level relay function (e.g.0 Release 5 66 ETSI TS 123 066 V5.3. ETSI . The use of other translation types is for further study.066 version 5.2: Process ATI_NPLR C.3.

3. From an Originating Exchange a call is set up to MSISDN.0 Release 5 67 ETSI TS 123 066 V5. ETSI .0 (2003-12) TC relay) in MNP-SRF are not covered here.3. When the MNP_SRF/MATF receives the message. Originating Subscription Network or number Network range holder Network if non-ported Visited Network HLRB SRI (MSISDN) CdPA = HLRB address 3 CgPA = GMSCB address SRI ack (MSRN) MNP_SRF/ NPDB MATF 4 CdPA = GMSCB address CgPA = HLRB address SRI (MSISDN) CdPA = MSISDN. if the number is non-ported.1: Call to a non-ported number 1. but the principle can be found in B. 2. The TT on SCCP may be set to ‘SRI’. C. The MNP_SRF/MATF function then replaces the CdPA by an HLRB address. When HLRB receives the SRI. 4.1 Call to a Non-Ported Number or Number Ported into the Network Figure C.3. After modifying the CdPA. GMSCB uses the MSRN to route the call to VMSCB.3.3GPP TS 23. it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF. the reader is referred to [7]. it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. For further details of the signalling relay function.3.4. 5.018 [3]). The call is routed to the subscription network being the number range holder network. the message is routed to HLRB.066 version 5. When GMSCB receives the ISUP IAM.2. 3. TT=SRI 2 CgPA = GMSCB address IAM ((RN+)MSISDN) IAM (MSRN) Originating Exchange 1 GMSCB 5 VMSCB 6 MSB Figure C. the MNP_SRF/MATF analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported.1 shows the signalling involved for a call to a non-ported number or number ported into the network (see 3G TS 23.

ETSI .2 Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing Figure C. VMSCA routes the call to the network’s GMSCA. The TT on SCCP may be set to ‘SRI’.3. When HLRA receives the SRI.066 version 5. it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. After modifying the CdPA. TT=SRI 3 CgPA = GMSCA address IAM (MSISDN) IAM (MSRN) MSA 1 VMSCA 2 GMSCA 6 Figure C. 4. The MNP_SRF/MATF function then replaces the CdPA by an HLRA address. 6.2: Call to a ported number via direct routeing where the call is originated in the subscription network 1. 3. MSA originates a call to MSISDN.3. 5. When the MNP_SRF/MATF receives the message. GMSCA uses the MSRN to route the call to VMSCB. it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF.3.3GPP TS 23. When GMSCA receives the ISUP IAM.3. it responds to the GMSCA by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. 2. the message is routed to HLRA.3.0 (2003-12) C.2 shows the signalling involved for a call to a ported number via direct routeing where the call is originated in the subscription network.0 Release 5 68 ETSI TS 123 066 V5. Originating Network = Subscription Network HLRA SRI (MSISDN) CdPA = HLRA address 4 CgPA = GMSCA address SRI ack (MSRN) MNP_SRF/ NPDB MATF 5 CdPA = GMSCA address CgPA = HLRA address SRI (MSISDN) CdPA = MSISDN.

Depending on the interconnect agreement. As the message is a SRI message. the MNP_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN.066 version 5. The TT on SCCP may be set to ‘SRI’.3.3: National mobile originated call to a ported number via direct routeing 1. 5.0 (2003-12) C.3GPP TS 23. Originating Network MNP_SRF/ NPDB MATF SRI (MSISDN) SRI ack (RN + MSISDN) CdPA = MSISDN.3.3.3.3. 4. VMSCA routes the call to the network’s GMSCA. 2. a foreign number is not known to be ported or a foreign number is ported to other foreign network. The scenario describes signalling in the originating network using direct routeing in the cases when an own number is ported out.3 Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network ≠Subscription Network– Direct Routeing Figure C. it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF.3 shows the signalling involved for a national mobile originated call to a number not Subscribed in the originating network via direct routeing. it analyses the MSISDN in the CdPA and identifies the MSISDN as not known to be ported or being ported to another network. TT=SRI 3 4 CdPA = GMSCA address CgPA = GMSCA address CgPA = MNP_SRF address IAM (MSISDN) IAM ((RN +) MSISDN) MSA 1 VMSCA 2 GMSCA 5 Figure C.0 Release 5 69 ETSI TS 123 066 V5. For the case the number is not known to be ported the routeing number may be omitted. 3. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network. ETSI . When GMSCA receives the ISUP IAM. When the MNP_SRF/MATF receives the message. the RN will be added in the IAM or not. MSA originates a call to MSISDN.

The TT on SCCP may be set to ‘SRI’.3. 4. 3. When the MNP_SRF/MATF receives the message. GMSCA uses the RN + MSISDN to route the call to GMSCB in the subscription network.4 shows the signalling involved for a call to a ported number via indirect routeing. ETSI . 2. the RN will be added in the IAM or not. As the message is an SRI message.4: Call to a ported number via indirect routeing 1. it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. Originating Network Number Range Holder Network MNP_SRF/ NPDB MATF SRI (MSISDN) SRI ack (RN + MSISDN) CdPA = MSISDN. From an Originating Exchange a call is set up to MSISDN.3. it requests routeing information by submitting a MAP SRI to MNP_SRF/MATF.066 version 5.0 Release 5 70 ETSI TS 123 066 V5. the MNP_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN. The call is routed to the number range holder network.3.4 Call to a Ported Number – Indirect Routeing Figure C.3. When GMSCA in the number range holder network receives the ISUP IAM.3. Depending on the interconnect agreement.0 (2003-12) C. TT=SRI2 3 CdPA = GMSCA address CgPA = GMSCA address CgPA = MNP_SRF address IAM (MSISDN) IAM ((RN +) MSISDN) Originating GMSCA Exchange 1 4 Figure C.3GPP TS 23.

3.066 version 5. the message is routed to HLRB. From an Originating Exchange a call is set up to MSISDN. 8.3GPP TS 23. When MNP_SRF/MATF in the subscription network receives the SRI. 6.3.3. The TT on SCCP may be set to ‘SRI’. except those for which subscription information is held in the subscription networks HLR. 7. When MNP_SRF/MATF receives the message. In this scenario the routeing depends always on the number range holder and the subscription network. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network. TT=SRI 2 CdPA = MSISDN. (Inter) national Originating Number Range Subscription Network Holder Network Network MNP_SRF/ NPDB MATF HLRB 3 SRI (MSISDN) SRI (MSISDN) CdPA = HLRB address 7 CdPA = RN + MSISDN. As the message is a SRI message. When GMSCA in the number range holder network receives the ISUP IAM. The MNP_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. The TT on SCCP may be set to ‘SRI’. TT=SRI 6 CgPA = MNP_SRF address CgPA = GMSCB address CgPA = GMSCA address 4 IAM (MSISDN IAM ((RN +) MSISDN) IAM (MSRN) Originating Exchange 1 GMSCA 5 GMSCB 9 Figure C. When GMSCB in the subscription network receives the ISUP IAM. When HLRB receives the SRI.5: National or international originated call to a ported number where indirect routeing with reference to the subscription network is used 1. When MNP_SRF/MATF receives the message.0 Release 5 71 ETSI TS 123 066 V5.0 (2003-12) C. 3. 5. Depending on the interconnect agreement. The MNP_SRF/MATF function then replaces the CdPA by an HLRB address which information may be retrieved from a database. 4.5 shows the signalling involved for a call to a ported number where indirect routeing with reference to the subscription network is used. ETSI . it requests routeing information by submitting a MAP SRI to MNP_SRF/MATF. The MNP_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. NOTE: The MNP_SRF/MATF in this scenario has only information about all ported numbers to one subscription network. it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF.3.5 Call to a Ported Number – Indirect Routeing with Reference to Subscription Network Figure C. it responds to the GMSCA in the number range holder network by sending a SRI ack with a RN + MSISDN. the message is routed to the subscription network. MNP_SRF/MATF operation is triggered. MNP_SRF/MATF operation is triggered. After modifying the CdPA. 9. TT=SRI CgPA = GMSCB address CgPA = GMSCA address SRI ack (MSRN) MNP_SRF/ NPDB MATF 8 CdPA = GMSCB address CgPA = HLRB address SRI ack (RN + MSISDN) SRI (MSISDN) SRI (MSISDN) CdPA = GMSCA address CdPA = MSISDN. the RN will be added in the IAM or not. the MNP_SRF/MATF function relays the message to the subscription network by adding a routeing number to the CdPA which information may be retrieved from a database. it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. After modifying the CdPA. 2. GMSCB uses the MSRN to route the call to VMSCB. The call is routed to the number range holder network.3.

3. the INE always sends the MNP information request.066 version 5. The INE may query the MNP information for the called party number or the calling party number.0 Release 5 72 ETSI TS 123 066 V5.6: MNP-SRF operation for providing MNP Information where direct routeing applies In a PLMN using a MNP-SRF based MNP solution supporting direct routeing. MNP information for ‘own numbers ported out’ and ‘foreign numbers ported in’. ETSI . to the MNP-SRF in that network. operators should ensure that the NPDB contains.3GPP TS 23.3.Direct Routeing Interrogating Network MNP NPDB SRFA ATI ack (MNP Info) SCCP CdPA = INE ATI (MSISDN) INE SCCP CdPA = MSISDN.3. containing the CdPA. TT=MNPInfoRequest Figure C.6 MNP Info Query . In order to provide enough information for a CAMEL SCP to charge correctly for CAMEL Pre-Paid Calls and SMS to national MSISDNs originated in the HPLMN.3.078 [18]).0 (2003-12) C. The INE requesting MNP information may be a gsmSCF for prepaid services (see 3GPP TS 23. at least.

3.066 version 5. which triggers MNP-SRF operation.3.3.7: MNP-SRF operation for Providing MNP information where indirect routeing applies The Interrogating Network Entity (INE) submits a MNP Information request message to the MNP-SRFB.078 [18]). The MNP-SRF functionality analyses the MSISDN in the application level and queries an MNP database to get the MNP information. ETSI . TT=MNPInfoRequest Figure C.Indirect Routeing Interrogating Number Range Holder Network Network MNP SRFB NPDB ATI ack (MNP info) SCCP CgPA = MNP SRFB address CdPA = INE address 2 1 INE ATI (MSISDN) SCCP CdPA = MSISDN.0 Release 5 73 ETSI TS 123 066 V5.7 MNP Info Query .3GPP TS 23.0 (2003-12) C.3. The INE may query the MNP information for the called party number or the calling party number. The INE requesting MNP information may be a gsmSCF for prepaid services (see 3GPP TS 23.

3. Visited Originating Network Subscription Network Network GMSCB MNP_SRFB/MATF HLRB VMSCB IAM ((RN+ )MSISDN) SRI (MSISDN) CdPA = MSISDN.0 (2003-12) C.3.1.3.1: Successful delivery of a call to a non-ported subscriber or number ported into the network ETSI . The figure is related to figure C.066 version 5.4.1 shows the information flow for a successful delivery of a call to a non-ported number or number ported into the network.0 Release 5 74 ETSI TS 123 066 V5.4.3GPP TS 23.4 Information Flows Figure C. TT=SRI SRI (MSISDN) CdPA = HLRB address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.

0 (2003-12) Figure C.2 shows the signalling involved for a call to a ported number via direct routeing where the call is originated in the subscription network.4. Visited National Originating Network = Subscription Network Network VMSCA GMSCA MNP_SRFA/MATF HLRA VMSCB IAM (MSISDN) SRI (MSISDN) CdPA = MSISDN.3. The figure is related to figure C.2.0 Release 5 75 ETSI TS 123 066 V5.3GPP TS 23. TT=SRI SRI (MSISDN) CdPA = HLRA address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.066 version 5.4.2: Successful delivery of a call to a ported number via direct routeing where the call is originated in the subscription network ETSI .3.3.

4.3. National Originating Network Subscription Network Visited Network GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB IAM (MSISDN) SRI (MSISDN) CdPA = MSISDN.4.0 Release 5 76 ETSI TS 123 066 V5. TT=SRI SRI ack (RN + MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN. The figure is related to figure C.3.0 (2003-12) Figure C.3.3 shows the signalling involved for a national mobile originated call to a ported number via direct routeing.3GPP TS 23.3. TT=SRI SRI (MSISDN) CdPA = HLRB address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.066 version 5.3: Successful delivery of a national mobile originated call to a ported number via direct routeing ETSI .

3. TT=SRI SRI (MSISDN) CdPA = HLRB address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.3. TT=SRI SRI ack ((RN +) MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN.066 version 5. Number Range Holder Network National Originating Network Visited Network GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB IAM (MSISDN) SRI (MSISDN) CdPA = MSISDN.4 shows the signalling involved for a national mobile originated call to a not known to be ported number via direct routeing.3. The figure is related to figure C.4.0 Release 5 77 ETSI TS 123 066 V5.4.4: Successful delivery of a national mobile originated call to a not known to be ported number via direct routeing ETSI .0 (2003-12) Figure C.3GPP TS 23.3.

4.4.3.3GPP TS 23. TT=SRI SRI (MSISDN) CdPA = HLRB address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.5: Successful delivery of a call to a ported number via indirect routeing ETSI . TT=SRI SRI ack (RN + MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN. Originating Network Number Range Holder Network Subscription Network Visited Network GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB IAM(MSISDN) SRI (MSISDN) CdPA = MSISDN.4. The figure is related to figure C.0 Release 5 78 ETSI TS 123 066 V5.5 shows the signalling involved for a call to a ported number via indirect routeing.066 version 5.3.3.0 (2003-12) Figure C.

4. TT=SRI SRI (MSISDN) CdPA = HLRB address PRN PRN ack (MSRN) SRI ack (MSRN) IAM (MSRN) Figure C.066 version 5. The contents of the messages used on the gsmSCF – MNP-SRF interface are specified in 3G TS 23.078 [19].3GPP TS 23.6 shows the signalling involved for a call to a ported number where indirect routeing with reference to the subscription network is used. The gsmSCF may transit the information received from NPLR to the gateway MSC with the CAP Connect message in order to avoid a subsequent SRI message. Number Range Holder Network Subscription Network Visited Network GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB IAM (MSISDN ) SRI (MSISDN) CdPA = MSISDN.5.5. ETSI .0 Release 5 79 ETSI TS 123 066 V5. When the message is sent from the NPLR to the gsmSCF. The figure is related to figure C.0 (2003-12) Figure C.3.3.2.5 Contents of the messages This clause contains detailed description of the messages shown in this part B of the specification.4.6: Successful delivery for a call to a ported number where indirect routeing with reference to the subscription network is used C. TT=SRI SRI (MSISDN) CdPA = RN + MSISDN. TT=SRI SRI ack (RN + MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN. the MNP specific information are defined as in clause C.3.

If concatenate addressing is used.0 (2003-12) C. the following MNP specific information is defined: Information element name Required Description Imsi M The IMSI returned by an NPLR is a generic IMSI. i.e. it also contains the MSISDN in addition to the Routeing Number. it is not tied necessarily to the Subscriber. 4. Msisdn C MSISDN of the B subscriber. If the routeing number is omitted. MAP version 3 can also support concatenate addressing. MNP Indicator U Indicates the number portability status of the subscriber. This information element shall be present if MSRN contains the routeing number to reach the subscription network for B subscriber and the MSISDN is not contained in the MSRN information element.5. 2. The following sections describe possible interworking scenarios.6 Handling of MAP to ISUP mapping (informative) Different configurations can be possible within a portability domain depending on the versions of MAP and ISUP protocols being used. If MSISDN parameter is present in the SRIack. the Routeing Number may be omitted as an operator option.In the case of a number which is not known to be ported.6. C.018 [3]. this parameter contains only the MSISDN. the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [6]): 1. CdPN parameter includes the Routeing Number and CDN parameter includes the MSISDN. when a Routeing Number is returned. CdPN parameter includes only the MSISDN. the method to transport the routeing number in the IAM depends on the interfaces agreed by the operators in the portability domain. In all cases. CdPN parameter includes both RN and MSISDN concatenated. it is included in the MSRN parameter of the SRIack.3.1 ETSI Mapping direction: ISUP to MAP The GMSC always constructs the Send Routeing Info message using the MSISDN.1 Send Routeing Info The contents of this message are specified in 3G TS 23. In the case that the message is sent from the NPLR to the GMSC. C. 3. Regardless of how MAP is established.6. In all cases.2 Send Routeing Info ack The contents of this message are specified in 3G TS 23.018 [3]. this parameter contains a Routeing Number that points to Subscription Network.0 Release 5 80 ETSI TS 123 066 V5.3. MAP versions 1 and 2 only support concatenate addressing for MNP. C. CdPN parameter includes the MSISDN and NRN parameter includes the Routeing Number.066 version 5. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. ETSI .5. this means that separate addressing is used in MAP.2 ETSI Mapping direction: MAP to ISUP In MAP SRIack messages from NPLR. C. MCC and MNC values in this IMSI shall point to the Subscription Network of the B Subscriber Msrn C When returned from the NPLR. this is only possible if MAP version 3 is used.3GPP TS 23.

this means that separate addressing is used in MAP.3GPP TS 23.6. MAP versions 1 and 2 only support concatenate addressing for MNP.4 ANSI Mapping direction: MAP to ISUP In MAP SRIack messages from NPLR.3. If MSISDN parameter is present in the SRI Ack. Regardless of how MAP is established. it is included in the MSRN parameter of the SRI Ack. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. MAP version 3 can also support concatenate addressing. In all cases. this is only possible if MAP version 3 is used. the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [8] and [9]): MAP Parameters SRI Ack ISUP Parameters IAM IMSI Subscriber IMSI CdPN MSRN MSRN MSRN MAPS TO GAP N/A MSISDN Not Present FCI Bit M Indicator 1 MNP Indicator Not Present MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN Dialled DN MSRN Dialled DN MAPS TO GAP N/A MSISDN Not Present FCI Bit M Indicator 1 MNP Indicator NotKnownToBePorte d MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN RN MSRN RN MAPS TO GAP Dialled DN MSISDN Dialled DN FCI Bit M Indicator 1 MNP Indicator OwnNumber PortedOut ETSI .0 Release 5 81 ETSI TS 123 066 V5.6. C. The IAM message is specified for ANSI ISUP implementation in [8] and [9].0 (2003-12) C.066 version 5.3 ANSI Mapping direction: ISUP to MAP The GMSC always constructs the Send Routeing Info message using the MSISDN. when a Routeing Number is returned.3.

0 (2003-12) MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN RN MSRN RN MAPS TO GAP Dialled DN MSISDN Dialled DN FCI Bit M Indicator 1 MNP Indicator Foreign Number PortedToForeign Network In all cases.3.3GPP TS 23.0 Release 5 82 ETSI TS 123 066 V5.066 version 5. ETSI .3. the method to transport the routing number in the IAM depends on the interfaces agreed by the operators in the portability domain.

0 Release 5 83 ETSI TS 123 066 V5.066 version 5.0 (2003-12) Annex D: Void ETSI .3.3GPP TS 23.3.

2.0 Result of Public Enquiry 9953 Mar 2000 #07 23.1.0 023r1 Rel-5 5.1.0.0.1 Rel-5 5.066 5.3.0 Editorial cleanup Mar 2000 #07 23.0 026r1 Rel-5 5.066 5.1.0 Clarification of NPDB error detection and MNP Mar 2000 specific call handling #08 23.0 Detection of database synchronisation errors in Mar 2000 SRF #07 23.0 Incorrect CAMEL pre-paid charging in MNP Sep 2003 networks CN#22 23.4.0 Alignment of IN interface with Fixed Networks Mar 2000 #07 23.066 3.066 5.66 7.3.1.2 Delivery of SMS to a Oct 1999 Non-ported Number .0 Release 4 after CN#11 Mar 2001 #16 23.0 IN-based solution for correct charging of calls to Jun 2003 ported or non-ported subscribers originated by pre-paid subscribers #21 23.0 Harmonisation of terminology interrogating Oct 1999 #05 23.2.2.066 3.0 Clarification of NPLR functionality in not known to Oct 1999 be ported case #07 23.066 4.066 3.0.0.066 3.2.066 3.0 015r1 R99 3.0 027 Rel-5 5.066 version 5.1.3.0 003 3.1.0 Rel-4 4.0 Incorrect implementation of CR 023r1 Dec 2003 CN#22 23.0.0 002 3.0 001 3.0 009r3 R99 3.1.3.0 007r1 R99 3.066 3.066 5.0 028r1 Rel-5 5.0 008r4 R99 3.0 North American Service Provider Number Jun 2000 Portability impacts for Mobile Number Portability #11 23.2.2.1.0 012r2 R99 3.0 MNP correction for prepaid charging Dec 2003 ETSI .Direct Routeing – MNP- SRF acts as Higher-level Relay #05 23.3.2.066 3.0 (2003-12) Annex E (informative): Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment #03 GSM 03.0.0 Release 5 after CN#16 Jun 2002 #20 23.0.0 Proposed changes to B.0 Release 5 84 ETSI TS 123 066 V5.0 Transferred to 3GPP CN2 Aug 1999 23.1.0.066 3.0 #05 23.066 3.0 Rel-4 4.1.1 References updated Mar 2002 #16 23.066 3.2.0.1.3GPP TS 23.0 019r2 R99 3.3.0.066 3.2.066 4.

1.0 June 2003 Publication V5.0.3.0 December 2003 Publication ETSI .0 Release 5 85 ETSI TS 123 066 V5.066 version 5.3GPP TS 23.0 September 2003 Publication V5.0 June 2002 Publication V5.2.0 (2003-12) History Document history V5.3.3.