MOBILE NUMBER PORTABILITY IN SWITZERLAND (NETWORK-NETWORK-INTERFACE SPECIFICATION)

Transcription

1 Page 1 of 18 MOBILE NUMBER PORTABILITY IN SWITZERLAND (NETWORK-NETWORK-INTERFACE SPECIFICATION) AUTHOR Document Release History OSCAR FURRER Version No. Release Date Purpose Draft December 1998 First draft of work items Draft January 1999 More details added to version 1.0, sections added for clarification Draft January 1999 Content added to sections 3,4,5,6,7 and 8 Draft February 1999 Draft February 1999 Draft March 1999 Draft April 1999 Draft May 1999 Draft June 1999 Draft February 2000 Version February 2000 Version April 2000 Version 3.0 November 2002 Adaptation to ETSI spec. and content added to section 5,6 and 7 Content added to section 3 and 8 Update references to the latest MNP ETSI s specifications. Review and adding of statements Modifications in section 8 Clarifications of some sentences throughout the draft. In chapter 7, section 7.13 added. Adding of reference [1] and [2]. Update of the statement in section 4.2 Updates throughout the document Add section 5 on subsequent porting Changes in section 4.2 (S-NPRN) Add section 4.3 Update section 5 Update section 9 Update in sections 4.2, 4.3, 5 and 9 Update section 4 and 8 Remove section 5 Document updated according to new NPRN format MNP Technical Realisation Version November 2002

2 Page 2 of REFERENCES DEFINITIONS AND ABBREVIATIONS DEFINITIONS ABBREVIATIONS INTRODUCTION FOREWORD PURPOSE SCOPE SERVICE DESCRIPTION GENERAL STATEMENTS STATEMENTS SPECIFYING THE MINIMUM MANDATORY SCOPE GENERAL RULES FOR NPRN USAGE MNP SIGNALLING RELAY FUNCTION (MNP-SRF) MNP-SRF PRINCIPLES HANDLING OF NON-CALL RELATED SIGNALLING NON-CALL RELATED SIGNALLING SCENARIOS HANDLING OF CALL RELATED SIGNALLING CALL RELATED SIGNALLING SCENARIOS NON - CALL RELATED SERVICES LOCATION UPDATE SHORT MESSAGE SERVICE (SMS) COMPLETION OF CALLS TO BUSY SUBSCRIBER (CCBS) Subscriber B is a ported Subscriber Indirect Routing CUSTOMISED APPLICATIONS FOR MOBILE NETWORK ENHANCED LOGIC (CAMEL) MAP REQUESTS RELATED TO SUPPLEMENTARY SERVICES WHEN ROAMING SUPPORT OF OPTIMAL ROUTING (SOR) MULTIPLE SUBSCRIBER PROFILE (MSP) CALL RELATED SERVICES MOBILE ORIGINATING CALL SUPPLEMENTARY SERVICES - OVERVIEW, IMPACT ANALYSIS LAWFUL INTERCEPTION ISSUES EMERGENCY CALLS ROAMING CIRCUIT SWITCHED DATA GPRS DATA AND FAX SUPPORT OF PRIVATE NUMBERING PLAN (SPNP) ENHANCED MULTI-LEVEL PRIORITY AND PRE-EMPTION (EMLPP) MULTIPLE SUBSCRIBER PROFILE (MSP) ECHO CANCELLATION CONCATENATED NUMBERS MNP NETWORK-NETWORK INTERFACE (NNI) REQUIREMENTS GENERAL Non-call related Services Call related Services MNP NNI FOR NON-CALL RELATED SERVICES MAP messages to be handled SCCP Addressing SCCP Number Plan for Signal Relaying SCCP hop counter MNP NNI FOR CALL RELATED SERVICES E.164 Number Plan for relaying User Part messages ISUP hop counter Release Cause value...18

3 Page 3 of REFERENCES [1] Fernmeldegesetz / 30 April 1997 [2] Verordnung der ComCom betreffend FMG incl. Annex 1 / 17 Nov 1997 [3] GSM Version Release 1998: Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); Service description; Stage 1 [4] GSM Version Release : Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2; Part 1 [5] GSM Version Release : Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); IN Call-Related; Technical Realisation; Stage 2; Part 2 [6] GSM Version Release : Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); Handling of Non-Call Related Signalling; Technical Realisation; Stage 2; Part 3 [7] GSM Version Release : Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); MNP Signalling Relay Function Call Related; Technical Realisation; Stage 2; Part 4 [8] GSM Version Release 1997: Digital cellular telecommunications system (Phase 2+); Technical realisation of Completion of Calls to Busy Subscriber (CCBS); Stage 2 [9] GSM Version 5.2.0: Digital cellular telecommunications system (Phase 2+); Multiple Subscriber Profile (MSP); Service description; Stage 1 [10] GSM Version 5.2.0: Digital cellular telecommunications system (Phase 2+); Support of Private Numbering Plan (SPNP); Service description; Stage 1 [11] GSM Version 5.0.1: Digital cellular telecommunications system (Phase 2+); enhanced Multi-Level Precedence and Pre-emption service (emlpp); Service description; Stage 1 [12] GSM version Release 1996: Digital cellular telecommunications system (Phase 2+); Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2 [13] ITU-T Recommendation Q.713 (07/96); Series Q: Switching and Signalling; Specifications of signalling system no. 7 Signalling Connection Control Part (SCCP) [14] GSM version 5.9.0: Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification 2. DEFINITIONS AND ABBREVIATIONS 2.1 Definitions For the purpose of this specification, definitions listed in [3] section 3.1 apply. 2.2 Abbreviations Abbreviations used in this specification are listed in [3] section 3.2 or explained in the text.

4 Page 4 of INTRODUCTION 3.1 Foreword This Network-Network-Interface Specification (NNI) is based on the FMG [1], the ComCom-regulation [2] and ETSI Specifications on MNP (Reference: [3], [4], [5], [6], [7]). The ETSI specification describes several solutions to implement MNP in a portability cluster. The conditions presented in Annex 1 to the ComCom regulation [2] impose the implementation of MNP in Switzerland. As consequence in the ETSI specifications there will be sections that are: mandatory to be supported by a mobile network; up to the mobile network to be supported; not part of the solution for MNP implementation in Switzerland; The actual realisation of the functional entities in to the network as is a matter of the mobile networks to determine. The network-network interface (NNI) must be consistent but also at the same time be independent of the technical realisation chosen to support the call related functions for MNP by the mobile networks. Therefore, the MNP NNI requirements are mandatory for the mobile network. 3.2 Purpose This document shall be the basis for the NNI technical realisation of the Mobile Number Portability (MNP) in Switzerland. 3.3 Scope This document describes MNP between networks using GSM 900 and GSM 1800 based technologies. This document does not include details about billing, administration, CDR production and the porting process. Neither are IMSI based transactions included as IMSIs are not ported between operators and always allocated by the recipient network. Section 4.1 of this document gives a brief description of the MNP service and is included for information. Section 4.2 specifies the minimum mandatory scope for the MNP. Section 5 specifies the detailed call routing scenarios and actions to be performed by the networks in case of subsequent porting. Section 6 gives an overview of the MNP Signalling Relay Function (MNP-SRF) and is included for information. This section allows a better understanding of the impact on the implementation caused by the statements presented in section 4.2. It is obvious that the technical implementation is up to the mobile network as long as the NNI requirements are respected. Sections 7 and 8 describe the service interaction with MNP. These sections are included for information. In these sections we also present the solution with MNP-SRF. It is obvious that the technical implementation is up to the mobile network as long as the NNI requirements are respected. Section 9 specifies the MNP Network-Network Interfaces (MNP NNI) requirements and is mandatory.

5 Page 5 of SERVICE DESCRIPTION 4.1 General statements MNP is the ability for a mobile subscriber to change network operator whilst retaining the original directory number. MNP is not service portability, i.e. if a service supported in the number range owner network is not available in the recipient network then number-porting mechanisms will not provide that service for the ported subscriber. NNI should not exclude the support of any services of the recipient network. However the ability of the recipient network to provide the same services to an imported subscriber as the ones provided to a non-ported subscriber depends only on its own MNP implementation. Number porting involving GSM subscriptions does not include porting the IMSI. When porting to a GSM subscription the recipient network provides a new SIM and IMSI. 4.2 Statements specifying the minimum mandatory scope 1. After initial porting, the number range holder network when receiving: a non-call related message with CdPA at SCCP layer corresponding to an exported MSISDN, shall add the Number Portability Routing Number (NPRN) as defined in section 9. a call related message with CdPN at ISUP layer corresponding to an exported MSISDN, shall add the NPRN as defined in section 9. This shall serve to route calls and non-call related signalling messages for ported numbers into the recipient network. 2. A network belonging to the portability cluster shall support as a minimum one of the following routing conventions: Direct routing of calls is a PLMN option which allows the PLMN to route calls directly from the PLMN supporting this option to the ported subscriber's subscription network. Indirect routing of calls is a PLMN option which allows the PLMN to route calls from the PLMN supporting this option via the number range owner network to the ported subscriber's subscription network. 3. In response to an optimal routing request, the recipient network can decide how to route the call as long as the contractual conditions agreed between the recipient network and the interrogating network are followed. 4.3 General rules for NPRN usage Rule 1: Rule 2: Rule 3: A PLMN is allowed to add a NPRN in front of the MSISDN only if the NPRN does not belong to the number range holder of the MSISDN. A PLMN is not allowed to add a NPRN in front of an MSISDN if both NPRN and MSISDN belongs to the same PLMN. A PLMN is not allowed to remove or modify an NPRN.

6 Page 6 of MNP SIGNALLING RELAY FUNCTION (MNP-SRF) This section explains a possible concept and principles of introducing functionality that will allow the mobile networks to implement the MNP service in Switzerland. This functionality is called MNP Signalling Relay Function (MNP-SRF). The exact implementation of the functionality as described in this section is a matter for each network to decide in order to meet the NNI (Network-Network Interface) MNP requirements. 5.1 MNP-SRF principles In a PLMN that supports mobile number portability, SCCP messages sent to an HLR may be relayed by an MNP-SRF. Depending on the type of message (call-related or non-callrelated) and on the porting status of the called subscriber the MNP-SRF may modify the SCCP called party address and route the message to a different HLR, to the NPDB (Number Portability Database) or to the subscription network. 5.2 Handling of Non-call Related Signalling Reference: [6] section 1 A PLMN shall support indirect routing, however it can also provide direct routing. 5.3 Non-call Related Signalling Scenarios Reference: [6] section 2 Section 2.1: Indirect routing to non-ported numbers shall be supported by a mobile network. Section 2.2: Direct routing to ported/non-ported numbers is up to the mobile network to be supported. Section 2.3: Indirect routing for ported numbers shall be supported by a mobile network. 5.4 Handling of Call Related Signalling Reference: [4] section 5 A PLMN shall support indirect routing (routing convention 2), however it can also provide direct routing (routing convention 1). The indirect routing with reference to the subscription network (routing convention 3) is not mandatory in Switzerland. A subscription network that receives a MAP SRI message (SRI(4)) from the number range owner network is therefore not obliged to respond with a SRI ack (SRI(5)). Reference: [7] section 1 As mentioned before the indirect routing with reference to the subscription network is not mandatory in Switzerland. 5.5 Call Related Signalling Scenarios Reference: [7] section 3 Section 3.1: Call to non-ported/ported numbers shall be supported by a mobile network. Section 3.2: Call to ported-in numbers in own network with direct routing is up to the mobile network to be supported. Section 3.3: Call to ported or not known to be ported numbers in other network with direct routing is up to the mobile network to be supported. Section 3.4: Call to ported numbers indirect-routing shall be supported by a mobile network. Section 3.5: Call to ported numbers with indirect routing and reference to the subscription network is not part of the solution for MNP implementation in Switzerland.

7 Page 7 of NON - CALL RELATED SERVICES This section describes effects or differences in the handling of individual non-call related services between ported and non-ported subscribers. 6.1 Location Update The location update procedure is not affected by MNP. When a subscriber registers in a new VLR, this VLR will request the subscriber s profile to the correct HLR (MAP_UPDATE_LOCATION). The HLR is identified based on the subscriber s IMSI. As specified in section 4 the number portability doesn t apply to the IMSI number. The IMSI will consequently always point to the correct HLR. All requests routed based on the IMSI are not affected by MNP. 6.2 Short Message Service (SMS) Reference: [6] Annex 1 and Annex 2: SMS to non-ported numbers with direct routing. Either solution can be adopted by the mobile network. Annex 3: SMS to ported numbers with indirect routing shall be supported by a mobile network. Annex 4: SMS to ported numbers with direct routing is up to the mobile network to be supported. 6.3 Completion of Calls to Busy Subscriber (CCBS) The CCBS service allows a calling subscriber A, encountering a busy (NDUB) destination B, to be notified when destination B becomes idle and to have the network automatically generate a CCBS call to destination B, if subscriber A desires. The ETSI specifications only describe the CCBS request to a ported subscriber with direct routing to the subscription network: Reference: [6] Annex 9: CCBS where Busy Subscriber is ported with direct routing is up to the mobile network to be supported. Section of this document (see below) shall be supported by a mobile network. Also the Subscriber A might be a ported Subscriber. In this case the Register_CC_Entry MAP message is send with the HLR address in the CdPA field at the SCCP layer. This HLR address will point to the correct HLR for a ported number as for a non-ported number Subscriber B is a ported Subscriber Indirect Routing This section describes the routing of a CCBS Request to the correct subscription network in the case were the Subscriber B is a ported Subscriber (see Figure 1).

8 Page 8 of 18 (Inter-)National Interrogating Network Subscription Network of A HLRA Number Range Owner Network of B CCBS Request ack CdPA = HLRA address CgPA = HLRC address 7 Subscription Network of B HLRC International Visited Network Register_CC_Entry CdPA = HLRA address CgPA = VLRA address 3 CCBS Request (MSISDN) CdPA = MSISDN, TT=17 CgPA = HLRA address 4 MNP SRFB 5 MNP SRFC CCBS Request (MSISDN) CdPA = RN+MSISDN, TT=17 CgPA = HLRA address 6 CCBS Request (MSISDN) CdPA = HLRC address CgPA = HLRA address VLRA 2 CCBS Request VMSCA 1 Release (cause = subscriber busy) VMSCB busy MSB Figure 1 Routing of CCBS Request Subscriber B is a ported Subscriber Indirect Routing 1. The VMSCA receives an ISUP Release message with cause value subscriber busy from VMSCB; 2. A CCBS Request message is sent to VLRA; 3. VLRA sends a CCBS Request to HLRA using the HLRA address as CdPA on SCCP; 4. The HLRA sends a CCBS Request message to the networks MNP-SRFB; 5. When SCCP in MNP-SRFB receives the message, MNP-SRF operation is triggered. 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. As the message is non-call related, the MNP-SRF function then populates the CdPA a concatenation of a routing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFC in the subscription network; 6. When MNP-SRFC receives the message, 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 which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRC address. After modifying the CdPA, the message is routed to HLRC; 7. HLRC can now respond to HLRA by sending back a CCBS ack message; 6.4 Customised Applications for Mobile network Enhanced Logic (CAMEL) Reference: [12] The CAMEL feature is applicable to mobile originated and mobile terminated call-related activities. Each subscriber that has access to a specific service possesses an Originating CAMEL Subscription Information (O-CSI) in his profile stored in his HLR. This O-CSI identifies the service and the Global Title of the concerned GSM Service Control Function (gsmscf). The O-CSI is sent to the VLR in case of Location Update or if the O-CSI is updated. In this way the ported status of a MSISDN number will not affect the interactions between the IPLMN/VPLMN and the gsmscf. The gsmscf can initiate an interrogation to a subscriber. This interrogation is the so called Any Time Interrogation and is routed based on the MSISDN (see section in [12]). The interrogation to a ported subscriber is treated in the ETSI specifications: Reference: [6]

9 Page 9 of 18 Annex 7: Any time interrogation to a ported number with indirect routing shall be supported by a mobile network. Annex 8: Any time interrogation to ported number with direct routing is up to the mobile network to be supported. 6.5 MAP requests related to Supplementary services when roaming These requests are routed based on IMSI. The request will be therefore routed to the correct HLR for non-ported or ported numbers. 6.6 Support of Optimal Routing (SOR) Reference: [6] Annex 6 shall be supported by a mobile network. 6.7 Multiple Subscriber Profile (MSP) See section 8.11.

10 Page 10 of CALL RELATED SERVICES This section describes effects or differences in the handling of individual call related services between ported and non-ported subscribers. 7.1 Mobile Originating call The establishment of a call from a ported subscriber to a non-ported subscriber is based on the MSISDN of the Called Party, which is a non-ported number. In this case the mobile originated call will not be affected by MNP. 7.2 Supplementary services - Overview, impact analysis In general, if SOR (Support of optimal Routing) is not applied, services based on circuit switched calls are under the control of the originating and/or recipient network because calls to ported subscribers are always routed trough the recipient network. Supplementary service information is downloaded from the HLR to the VLR and this will not be affected by MNP. Calling line identification presentation (CLIP) No impact (stated in [3]). The ported number is stored in the HLR of the recipient network and will be downloaded to the VLR of the visited network. Hence, the ported number is provided as the line identity of the subscriber during mobile originated calls. Calling line identification restriction (CLIR) No impact (stated in [3]). The CLIR supplementary service is related to a mobile originated call, consequently there is no impact for this supplementary service. Connected line identification presentation (COLP) No impact (stated in [3]). The information about the connected line identity is send at the end of the call set-up phase, in other terms it belongs to the call set-up phase. Consequently there is no impact for this supplementary service. Connected line identification restriction (COLR) No impact (stated in [3]). See comment on COLP. Call Forwarding Unconditional (CFU) No impact (stated in [3]). The request on forwarding is generated by the called mobile station and is send to the location registers of the recipient network which gives the new subscribers profile. This supplementary service can be considered as being mobile originate and consequently there is no impact for this supplementary service. Call Forwarding on mobile subscriber Busy (CFB) No impact (stated in [3]). See comment on CFU. Call Forwarding on No Reply (CFNRy) No impact (stated in [3]). Call Forwarding on mobile subscriber Not Reachable (CFNRc) See comment on CFU. No impact (stated in [3]). See comment on CFU. Call Waiting (CW) No impact (stated in [3]).

11 Page 11 of 18 The CW supplementary service involves the visited MSC and the called mobile station. The second call establishment follows the rules described in the sections on mobile terminating calls. Consequently there will be no impact on this supplementary service. Multiparty services (MPTY) No impact (stated in [3]). The MPTY supplementary service can be considered as being mobile originating service and consequently there is no impact on this supplementary service. Closed User Group No impact (stated in [3]). This supplementary service in general accepts all incoming calls and allows only the outgoing calls towards the group. It can be considered as being a mobile originating service and consequently there is no impact on this supplementary service. Advice of Charge services No impact (stated in [3]). This supplementary service can be considered as being mobile originate and consequently there will be no impact on it. Barring of All Outgoing Calls (BAOC) No impact (stated in [3]). Barring of outgoing calls can be considered as being a mobile originating service and therefore is not affected. Barring of Outgoing International Calls (BOIC) No impact (stated in [3]). Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOICexHC) Barring of outgoing international calls can be considered as being a mobile originating service and therefore is not affected. No impact (stated in [3]). See comments on BAOC and BOIC. Barring of All Incoming Calls (BAIC) No impact (stated in [3]). Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam) Barring of incoming calls will require that the HLR of the recipient network can apply the appropriate barring at call setup. The result of the barr (e.g. an announcement) is unaffected by MNP. No impact (stated in [3]). See comments on BAOC and BOIC. Explicit Call Transfer (ECT) No impact (stated in [3]). The ECT supplementary service enables the served mobile subscriber (subscriber A) who has two calls, each of which can be an incoming or outgoing call, to connect the other parties in the two calls and release the served mobile subscribers own connection. This can be considered as being mobile originate and therefore should not be affected. Table 1 Supplementary services, impact overview

12 Page 12 of Lawful Interception Issues Requirements regarding call tracing- and monitoring-functionalities are limited to the recipient network. The recipient network has to provide necessary features to trace/monitor its subscribers according to legal requirements. 7.4 Emergency calls When a subscriber makes a mobile originated emergency call, there will be no differences in the treatment of this call whether it is originated from a ported or a non-ported number. But emergency centers have to be aware that the A number does not any longer identify the subscription network. 7.5 Roaming Calls to a ported subscriber, roaming in a network that is not the subscription network, can be compared to the terminating call where the visited PLMN is the network in which the subscriber is roaming. Mobile originated calls are not affected by MNP. 7.6 Circuit Switched Data 7.7 GPRS Mobile originated will not be affected. Mobile terminated calls the involved networks shall provide transparent circuits. According to GSM at least three different addressing schemes exist: E.164 number X.121 address for X.25 CONS IP version 4 and 6 address for Internet CLNS Address(es) may be assigned temporarily or permanently. Impact on number portability: for further study. 7.8 Data and Fax MSISDNs for data and fax may be handled like MSISDNs for telephony (assumed that the recipient network supports data and fax). A subscriber may decide that he only wants his telephony service to be ported, e.g. because he does not subscribe for data and/or fax any longer. In this case the MSISDN(s) return to the number range owner network for further use. No additional MSISDN will be provided by the number range holder after porting took place to another subscriber network. The subscriber will therefore be obliged to get additional MSISDN out of the number-range of its actual subscriber network. 7.9 Support of Private Numbering Plan (SPNP) Reference: [10] The subscriber can be registered to up to 8 PNPs. The PNP itself is owned by the HPLMN. After porting the PNP generally will not be available for a single subscriber. A group of subscribers may agree with the recipient network that an equivalent PNP is designed.

13 Page 13 of enhanced Multi-Level Priority and Pre-emption (emlpp) Reference: [11] This service is subscription related and may or may not be supported by the recipient network. No impact on Mobile Number Portability Multiple Subscriber Profile (MSP) Reference: [9] MSP enables a mobile subscriber to have up to four profiles associated with a single SIM and a single IMSI. For each profile different MSISDNs are assigned. The number of profiles supported by the recipient network and by the donor network may differ: 1. If the recipient network supports MSP and if the supported number of profiles in the recipient network is at least as big as the supported number in the donor network then the all of the subscriber profiles can be ported. 2. If the recipient network supports MSP and if the supported number of profiles in the recipient network is smaller as the supported number in the donor network then at least a part of the subscriber profiles can be ported. 3. If the recipient network does not support MSP then only one of the subscriber profiles can be ported. In cases 2 and 3 the now unused MSISDNs return to the number range owner network for further use Echo cancellation Echo cancellation has basically to take place in the recipient network. If possible, Echo Cancellation devices in the number range owner network shall therefore not be activated for NP-calls, although no harmful quality degradation is expected by multiple echo cancellars working in series Concatenated numbers A call to a ported concatenated number will be handled like a terminated call to a ported number. A call to the following voice mail number 0860 AB will be routed to the number range AB holder network. The number range holder network will identify the CdPN as being an out-ported number and will add the routing number (S-)NPRN 860 AB Finally the call will be routed to the recipient network.

14 Page 14 of MNP NETWORK-NETWORK INTERFACE (NNI) REQUIREMENTS This section defines the mandatory MNP requirements for the Network-Network Interface (NNI). 8.1 General Non-call related Services When a service request is routed to the number range holder network, this network must relay the request to the correct recipient network, by including the NPRN in the SCCP address. The addressing required to determine a ported number will be derived from the MSISDN in the CdPA at the SCCP layer. To support this requirement a MNP NNI is required between the mobile networks (see section 9.2). The MNP NNI may be a direct or indirect interconnection, therefore both the concerned mobile networks and transit networks must support the mandatory requirements of the NNI, see Figure 10. Incoming service request to ported subscriber Number range holder network MNP Interfaces Recipient network Transit Network Figure 2 Network-Network Interfaces (NNI) Non-call related Services Call related Services When a call to a ported number is routed to the Number range holder network, this network must add the NPRN to the called party number (CdPN) before the call is conveyed to the recipient network. The addressing required to determine a ported number will be derived from the MSISDN dialled by the calling party. To support this requirement a MNP NNI is required between the mobile networks (see section 9.3). The MNP NNI may be a direct or indirect interconnection, therefore both the concerned mobile networks and transit networks must support the mandatory requirements of the NNI, see Figure 11.

15 Page 15 of 18 Incoming call to ported subscriber Number range holder network MNP Interfaces Recipient network Transit Network Figure 3 Network-Network Interfaces (NNI) Call related Services 8.2 MNP NNI for Non-call related Services For the MNP NNI between the mobile networks, the signalling system for non-call related messages shall be based on the Mobile Application Part (MAP) using the services offered by the Transaction Capabilities (TC) and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No.7 (see Figure 12). MAP TCAP SCCP MTP MAP TCAP SCCP MTP Figure 4 NNI at SCCP layer MAP messages to be handled The operations to be handled by the mobile networks are basically all signalling messages where the MSISDN is used to route the message at SCCP layer except MAP SRI without OR parameter set. Version differences of MAP operation shall be handled by MAP version negotiation mechanisms SCCP Addressing MAP operations are routed on Global Title on the SCCP layer. A Routing Number (NPRN) is required to relay the signal to the recipient network. The SCCP Called Party Address is the modified field. A standard signalling NPRN plan is required for MNP NNI on SCCP layer to allow signal relay (see following section). Where MNP NNI is achieved through transit networks, the transit networks are required to support the signalling NPRN plan. The addressing of SCCP messages is as follow (please refer to [13] and [14] for details on SCCP parameters):

16 Page 16 of 18 Protocol Layer Field Number MAP MSISDN 41 NDC SN or NDC SN SCCP CdPA Address Indicator RI=0(Route on GT), GTI=0100, SSNI=1, PCI=0 SCCP CdPA SSN=6 (HLR) TT=0, NPI=0001 (E164), NAI=National/International, GT=41+NPRN+NDC+SN SCCP CgPA Originating Node Address Table 2 MNP NNI SCCP Addressing Responses to the relayed operations are addressed in the standard way using the received calling party address SCCP Number Plan for Signal Relaying The modified SCCP Address is defined as follows: CC NPRN N(S)N Digit Name Value CC Country Code 41 NPRN MNP Routing Number NPRN defined as follows: = Swisscom Mobile = Orange = TDC Switzerland AG N(S)N = NDC+SN National (Significant) Number = National Destination Code + Subscriber Number Table 3 MNP NNI SCCP Called Party Address (International) format Where NDC is defined as follows: 79 = Swisscom Mobile 78 = Orange 76 = TDC Switzerland AG and SN is any digits (not starting with 0). The number range holder network shall ensure that the above addressing format is provided at MNP NNI. The national format of the modified SCCP address is defined as follows: NPRN N(S)N Digit Name Value NPRN Routing Number NPRN defined as follows: = Swisscom Mobile = Orange = TDC Switzerland AG N(S)N = NDC+SN National (Significant) Number = National Destination Code + Subscriber Number Table 4 MNP NNI SCCP Called Party Address (National) format Where NDC is defined as follows: 79 = Swisscom Mobile 78 = Orange 76 = TDC Switzerland AG and SN is any digits (not starting with 0).

17 Page 17 of SCCP hop counter It has not been decided to introduce the SCCP hop counter for the first January Nevertheless, this issue should be studied by the operators and introduced as soon as possible. ETSI recommends to use this SCCP hop counter to prevent circular routing of non-call related messages. We have already defined some conditions to prevent circular routing, but the SCCP hop counter would be the last level to secure the network against circular routing. 8.3 MNP NNI for Call related Services For the MNP NNI between the mobile networks, the call-related signalling system shall be based on the User Part (ISUP is used in Switzerland). A standard signalling NPRN plan is required for MNP NNI on the User Part level to allow the routing of calls to the correct PLMN (see following section). Where MNP NNI is achieved through transit networks, the transit networks are required to support the NPRN plan. UP MTP UP MTP Figure 5 NNI at User Part layer E.164 Number Plan for relaying User Part messages The CdPN is the modified field and includes both NPRN and MSISDN concatenated. Modified CdPN is defined as follows: CC NPRN N(S)N Digit Name Value CC Country Code 41 NPRN MNP Routing Number NPRN defined as follows: = Swisscom Mobile = Orange = TDC Switzerland AG N(S)N = NDC+SN National (Significant) Number = National Destination Code + Subscriber Number Table 5 MNP NNI E.164 Number (International) format Where NDC is defined as follows: 79 = Swisscom Mobile 78 = Orange 76 = TDC Switzerland AG and SN is any digits (not starting with 0). The Number range holder network shall ensure that the above addressing format is provided at MNP NNI.

18 Page 18 of 18 The national format of the modified E.164 Number is defined as follows: NPRN N(S)N Digit Name Value NPRN Routing Number NPRN defined as follows: = Swisscom Mobile = Orange = TDC Switzerland AG N(S)N = NDC+SN National (Significant) Number = National Destination Code + Subscriber Number Table 6 MNP NNI E.164 Number (National) format Where NDC is defined as follows: 79 = Swisscom Mobile 78 = Orange 76 = TDC Switzerland AG and SN is any digits (not starting with 0) ISUP hop counter It has not been decided to introduce the ISUP hop counter for the first January Nevertheless, this issue should be studied by the operators and introduced as soon as possible. The ISUP hop counter prevents circular routing of calls. We have already defined some conditions to prevent circular routing, but the ISUP hop counter would be the last level to secure the network against circular routing of calls Release Cause value In case a network rejects a call, it will reject it with cause value 1 (unallocated number).