TELECOMMUNICATIONS INDUSTRY NETWORK CODE FOR LOCAL AND MOBILE NUMBER PORTABILITY IN NEW ZEALAND. Network Code

Transcription

1 TELECOMMUNICATIONS INDUSTRY NETWORK CODE FOR LOCAL AND MOBILE NUMBER PORTABILITY IN NEW ZEALAND Network Code Draft for Public Consultation 22 July 2004 Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 1 of 32

2 Table Of Contents Explanatory Statement 1 Purpose of this Code 1.1 Purpose Network Code Status Anticipated Benefits to Industry Introduction 2.1 Number Portability for Local and Mobile Numbers Industry Structure References Scope and Objectives 3.1 Scope Objectives The objectives of the Code are to: Conventions in this Code 4.1 Interpretations Definitions Assumptions 5.1 Number Allocation Network Solutions Multiple Porting of Numbers Commercial Arrangements Interconnection Standards The requirements of this Code shall: Change of Directory Number Business Rules 6.1 General Business Rules Carrier Responsibilities 7.1 Carrier Rules Compliance with Service Levels Equivalent Service (also see Section 13) Network Integrity Network Planning and Design Network Performance Non Participating Carriers Calls to 111 Emergency Services International Short Messaging Service (SMS) Interworking with MNP Carrier Relationships and Network Model 8.1 Carrier Relationships Network Model Points of Interconnection Donor and Originating Carrier Re-routeing 9.1 Rerouteing Responsibilities Rerouteing Rules Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 2 of 32

3 9.3 Call Diagrams Call Handling Rules 10.1 Call Handling Solution Figure Figure Figure Figure Technical Call Handover and Signalling 11.1 General Inter-Network Signalling Standards General Signalling Capabilities Definition of Signalling Terms Signalling for Calls to Ported Numbers Contents of the Initial Address Message (IAM) Signalling Message For calls to Ported Numbers: Calling Party CLI and CLIP/CLIR integrity is to be maintained viz: Contents of the IAM Signalling Message (2) CLI Information For calls originated by in-ported Numbers in the Host Carriers Network: Hand-Off Codes 12.1 HOC Allocation and Format HOC Forwarding HOC Trapping Equivalent Service 13.1 Definition Equivalent Service Criteria for LMNP Equivalent Service Compliance Operational and Support Manual for LMNP 14.1 Operational Procedures Fault Handling Process Implementation Initial Ported Number Migration Administrative Issues 15.1 Expiry revocation and amendment of the code Dispute Resolution Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 3 of 32

4 Explanatory Statement The Porting arrangements for Local and Mobile Numbers in New Zealand are defined in the following Telecommunications Access Codes produced by the Telecommunications Carriers Forum: Code for Local and Mobile Number Portability (LMNP Code) Network Code for Local and Mobile Number Portability (Network Code) The LMNP Code details the processes that enable Customers to Port their Numbers and sets out the rights and obligations of Parties to that Code in a number portability environment. These processes are based around an Industry Portability Management System which facilitates number portability between Service Providers but relies on Carrier s to configure and update their Networks and support systems to ensure calls to and from Ported Numbers are correctly routed. In a number portability environment there are changes required to the traditional way in which calls are routed from Originating Carriers to Terminating Carriers. This applies to local, national, fixed-to-mobile, mobile-to-fixed, mobile-to-mobile, incoming and outgoing international and other calls involving Local or Mobile Numbers. This Network Code is intended to guide participating Carriers in the development of their own Network solutions and specify the optional and mandatory requirements necessary between Networks. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 4 of 32

5 1 Purpose of this Code 1.1 Purpose The purpose of this Code is to provide a definitive specification of the Carriers Network requirements for Local and Mobile Number Portability. 1.2 Network Code Status This Code is a Telecommunications Access Code, under Schedule 2 of the Telecommunications Act The Code applies to all Carriers involved in the origination, carriage, handover and termination of calls to or from Ported Local and Mobile Numbers. 1.3 Anticipated Benefits to Industry This Code provides benefits to the industry by: a) Standardising industry practices in relation to the network aspects of LMNP,; b) Ensuring that all Carriers are able to meet their call routeing responsibilities so that calls to and from Customers with Ported Numbers are routed successfully; c) Ensuring service to the Customer is maintained by specifying Service Levels and d) Ensuring efficient and effective inter-carrier operational arrangements. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 5 of 32

6 2 Introduction 2.1 Number Portability for Local and Mobile Numbers In a number portability environment, there will be changes to the traditional ways calls are delivered from Originating Carriers to Terminating Carriers. This applies to local, long distance, mobile, international and other types of calls. This Code details these networking arrangements. This Code is predicated on the understanding that the existing allocation process for blocks of local (geographic) and mobile (non-geographic) numbers to Carriers by the NAD will continue. This Code defines the industry agreed call handling, technical interconnection arrangements, operational arrangements and business rules and processes based on a model of interconnected networks. 2.2 Industry Structure The supply of Local and Mobile Services is currently undertaken by a number of Carriers in New Zealand. In addition, new Carriers are able to obtain Local and Mobile Numbers and establish their own services. This Code for the implementation of number portability takes account of the future market place. 2.3 References Documents LMNP Code NAD Number Register and Number Allocation Rules ITU Documents: E.164 Supplement 2 (11/98) Q (03/93) Q (12/99) - Signalling system No. 7 - ISDN user part enhancements for the support of number portability Q.Sup3 (05/98) - Number portability - Scope and capability set 1 architecture Q.Sup4 (05/98) - Number portability - Call control for capability set 1 service provider portability (All call query and Onward routeing) Q.Sup5 (03/99) - Number portability - Capability set 2 requirements for service provider portability (Query on release and Dropback) Q.850 Addendum 1 (06/00) Websites Telecommunications Carrier Forum Number Administration Deed Commerce Commission ACIF Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 6 of 32

7 3 Scope and Objectives 3.1 Scope The Code sets out operational standards, procedures and processes between Carriers, for the origination, carriage, handover and termination of calls in an environment where Local and Mobile Numbers are being Ported The Code is applicable to all Carriers participating in LMNP and it is not intended to impact other parties who do not have obligations under this Code In the event of any inconsistency between this Code and such legislation or determinations of regulatory bodies, then such legislation or determinations will prevail The requirements of this Code are the default minimum industry standards and can be improved by Multilateral and Bilateral Agreements provided that the agreements do not impact on the ability of other Carriers to inter-work with parties to those arrangements in accordance with the minimum requirements. 3.2 Objectives The objectives of the Code are to: a) Set out procedures between Carriers to enable calls to and from Ported Numbers to be routed to or from the Host Carrier s Network, even though the relevant Number range containing the Number will still be held by the Donor Carrier; b) Set out competitively neutral and non-discriminatory principles for the implementation and operation of LMNP; and c) Set out procedures to ensure equivalent service. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 7 of 32

8 4 Conventions in this Code 4.1 Interpretations In the Code: DRAFT Sections, clauses and other headings are for ease of reference only and will be ignored in construing this Code Unless the context otherwise requires, references to sections, clauses and appendices are references to sections and clauses of, and appendices to, this Code Any reference in this Code to a statute, statutory instrument, regulation or order will be construed as a reference to such statute, statutory instrument, regulation or order as amended or re-enacted from time to time Any references to a party, is to a party of this Code (unless otherwise specifically provided) and will be deemed to include its successors and permitted assigns A reference to a person includes an individual, firm, company, corporation, unincorporated body of persons, state or government or agency thereof, and any other body or entity (in each case whether or not having separate legal personality) Any reference in this Code to any gender includes all genders and a reference to the singular includes the plural and vice versa If a period of time is specified and dates from a given day or the day of an act or event, it is to be calculated exclusive of that day; and A reference to a day is to be interpreted as the period of time commencing at midnight and ending 24 hours later. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 8 of 32

9 4.2 Definitions DRAFT In this Code, unless the context requires otherwise: Term Carrier Code Customer Donor Carrier Definition Means an entity that operates a public switched telephone network (or a functionally equivalent system) that originates, transits or terminates calls. The same person may be both a Carrier and a Service Provider. Means this document, including its appendices. Means a person who has a bona fide Billing Relationship with a Service Provider in respect of a Local or Mobile Service. Means the Carrier that has been allocated the Number by the NAD, or recognised by the NAD as having been allocated. [Enforcement Agency] An agent endorsed by the [TCF/MED/Commerce Commission], whose role is to monitor and, if necessary, measure Equivalent Service compliance in accordance with Section Note: The entity taking on this role has yet to be determined. Event Hand-off Code or HOC Host Carrier Industry Portability Management System or IPMS Local and Mobile Number Portability or LMNP Local Calling Area Local Number Local Number Portability or LNP Mobile Number Mobile Number Portability or MNP Mobile Service Means an instance of one of the agreed set of processes that can arise from a specific Customer action, for which a specific Process exists. Means a prefix code passed between Carriers used for call routeing. The HOC is in the form of 0119NT where N denotes a Carrier and T denotes the service to which the Ported Number relates. Also see Clause 12. Means the Carrier who provides Network access to the Customer with the Ported Number and is responsible for the routeing and terminating of calls to and from that Ported Number. Means the system described in the LMNP Code. Means Local Number Portability and Mobile Number Portability. Means that geographic area defined by the Donor Carrier within which Customers have access to a Local Service with a consistent set of attributes. Means an 8 digit number, in the form: area code + NXXXXXX where area code equals 3,4,6,7 or 9 and N equals digits 2 to 9 (excluding 50AB). Means, as defined in the Act, a service that enables an enduser of a fixed telephone network service to change providers of that service but to retain the same telephone number within a local calling area. Means a number in the form 02N + XXXXXXX where N equals 1,5,7 or 9 and other cellular numbers allocated by the NAD, or recognised by the NAD as having been allocated. Means, as defined in the Act, a service that enables an enduser of a cellular telephone network service to change providers of that service but to retain the same telephone number (including the same cellular network access code). Means the service associated with a Mobile Number. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 9 of 32

10 Term Definition Multilateral and Bilateral Means an agreement between a party who is obliged to Agreements comply with this Code and one or more parties (who may also be a party or parties to this Code). Network Means a system comprising telecommunication links to permit telecommunications. Number Means a Local Number, a Mobile Number or both, as the case requires. Numbering Administration Means the organisation established under the Numbering Deed or NAD Administration Deed dated 20 December 1998, or any such successor organisation or agreement that may be formed. Operational and Support Means a multilateral agreement between Carriers that covers Manual for LMNP operational issues that are not covered by the Network Code. Originating Carrier Means the Carrier on whose Network a call to a Ported Number originates. Other Carrier Means a Carrier that is a party to this Code, but is not involved in a given Port event as a Gaining Carrier, Losing Carrier, or Donor Carrier. Port or Porting Means a process, which achieves LMNP. Ported Number Means a Number that is currently hosted by any Carrier other than the Donor Carrier. Service Levels Means the service levels as prescribed in the Operational and Support Manual for LMNP. Service Provider or SP Means any person providing a Local or Mobile Service to a Customer who has the Billing Relationship with the Customer for that service. The same person may be both a Carrier and a Service Provider. The Act Means the Telecommunications Act 2001 Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 10 of 32

11 5 Assumptions In preparing and developing this Code, the following assumptions and general principles have been used. 5.1 Number Allocation Numbers will continue to be administered to Carriers by the NAD. 5.2 Network Solutions Each Carrier is able to implement the requirements of this Code within their Network in whatever way they wish provided they comply with this Code. 5.3 Multiple Porting of Numbers A Customer must be able to Port their Number more than once to different Carriers. That is, an initial Port from the Donor Carrier to a new Host Carrier may be followed at later dates by further separate Portings from that Host Carrier to other Host Carriers. 5.4 Commercial Arrangements The commercial arrangements for the handover of calls between Carriers are to be determined outside of this Code on a multilateral and bilateral basis. 5.5 Interconnection Standards Carriers will comply with the relevant national and international standards and recommendations when interconnecting to ensure successful Porting operation. 5.6 The requirements of this Code shall: a) Enable Carriers, as far as possible, to remain in control of their own Network call control processes. b) Concentrate on the information passed between Networks. Subject to the requirements for interoperability, solutions should be specified independent of specific technologies at the Network interface as far as possible. c) Not preclude the use of multiple solutions within a Network, nor the use of multiple or different solutions over time. d) Not require the Ported Customer to change their Number as a result of future changes in the Donor Network. e) Use a common set of interface standards for inter-network inter-operability (taking into consideration existing standards and developments). f) Focus on interconnect (inter-network, or inter-operability) standards rather than intra-network solutions g) Minimise network capacity usage. 5.7 Change of Directory Number Porting should not require Customers to change their directory Number, nor have to know, nor use any Number other than their directory Number. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 11 of 32

12 6 Business Rules 6.1 General Business Rules Non-discrimination In implementing this Code and facilitating Porting in accordance with it, all Carriers will act in a competitively neutral and non-discriminatory manner Privacy and Use of Information A Carrier which receives any type of information relating to the Porting of a Number may only use this information in accordance with Privacy Act 1993, the Telecommunications Privacy Code 2003, and this Code. If there is any inconsistency between this Code, the Privacy Act 1993, and the Telecommunications Privacy Code 2003, the Privacy Act and the Telecommunications Privacy Code prevail Subject to New Zealand Law In the event of any conflict or inconsistency between this Code and New Zealand law, New Zealand law prevails Good Faith All parties will act co-operatively and in good faith Multilateral and Bilateral Agreements Parties of this code will agree terms and conditions of a Multilateral Agreement. In order to ensure that standards and practices can be monitored and maintained, the Multilateral Agreement will set up all principles and procedures necessary. Meanwhile, parties to this Code may agree terms and conditions in their Bilateral Agreements, for the provision of all appropriate and relevant services and service information, that is required to facilitate and support the origination, carriage, handover and termination of calls in an efficient and expeditious manner. Parties will ensure to agree in their Bilateral Agreement to higher service levels and larger scope for standards and practices. If principles agreed in the Bilateral Agreement regarding this matter constitute a degradation of principles set up in the Multilateral Agreement, the Multilateral Agreement will prevail over the Bilateral Agreement. If a Bilateral Agreement between two parties is terminated, the Multilateral Agreement still prevails. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 12 of 32

13 7 Carrier Responsibilities DRAFT It will be the responsibility of each Carrier to ensure that they meet the required Service Levels. Each Carrier is free to determine how it handles calls, either within its own Network or with the assistance of another Carrier. Where this document refers to the responsibility of a Carrier, they can contract this out to a third party, however the primary responsibility under this Code remains with the Carrier. 7.1 Carrier Rules a) Each Carrier will make the necessary changes, additions or deletions to its Network to give effect to the instructions issued by the IPMS b) The routeing of calls to or from Ported Numbers, or the routeing of any calls between the Networks of any Carriers subject to this Code must comply with this Code to ensure calls are correctly routed; and c) Carriers will act in good faith to facilitate Porting. 7.2 Compliance with Service Levels Each party subject to this Code must comply with the Service Levels, including equivalent service (re section 7.3). The details of the Service Levels are in the Operational and Support Manual for LMNP. 7.3 Equivalent Service (also see Section 13) The Network solution adopted by Carriers must be capable of satisfying the requirements for equivalent service, which for the purposes of this Code is defined as: A service provided in relation to a Ported Number is an equivalent service, if (and only if) any differences, in quality, reliability, services or features, between it and a service provided in relation to a non-ported Number on the same Network: a) Will not be apparent to a customer; or b) If they are apparent to a customer - will not affect the customer s choice of Service Provider. In implementing this Code and operating in accordance with it, all parties to this Code are required to act in good faith to satisfy the requirements for equivalent service. These requirements can be relaxed or deferred subject to separate agreement for some transitional period for specific requirements. 7.4 Network Integrity Carriers are responsible for maintaining the integrity of their own Networks and there is an obligation on Carriers to work together to maintain this integrity. These requirements can be relaxed or deferred subject to separate agreement for some transitional period for specific requirements, for example, for network systems that are soon to expire and be replaced. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 13 of 32

14 7.5 Network Planning and Design It is the responsibility of each Carrier to undertake reasonable forward network planning and design in order to reasonably cater for the forecasted ported call volumes. The arrangements for forecasting volumes will be agreed outside this Code. Each Carrier may use its own standard procedures for the planning and design of their own network to meet this requirement. 7.6 Network Performance It is the responsibility of each Carrier to plan, design, and operate its porting solution in way that will meet reasonable industry standards of network performance. Each Carrier is free to use its own standard procedures in the planning, design, and operation of their own network to meet this requirement. 7.7 Non Participating Carriers To the extent that a Carrier offers Ported calls to or accepts Ported calls from a Non-participating Carrier, it shall use reasonable endeavours to ensure that the general technical and performance issues as described above are reflected in any Bilateral Agreement between the Carrier and the Non-participating Carrier. 7.8 Calls to 111 Emergency Services It is the responsibility of each Carrier to ensure that calls originating in their Network to the 111 Emergency Service are not adversely impacted by LMNP in accordance with clause International Short Messaging Service (SMS) Interworking with MNP SMS traffic destined for a New Zealand network from a foreign operator will be delivered to the national Network that has the initial roaming agreement with that foreign operator. All national network codes may be delivered to this national Network. It will be that national Networks responsibility to determine if the SMS will be terminated on their network, transit the SMS to an alternate national Network or prevent the SMS from being delivered. If a New Zealand network was to establish a roaming agreement with a foreign operator, where an agreement already exists with an alternate New Zealand Network, the foreign operator may be requested to route the SMS traffic to that additional New Zealand Network dependent on the NAD ownership of the number ranges of that additional Network. It is the responsibility of the additional Network, requesting changes to be made by the foreign operator, to notify the New Zealand Network which is currently receiving SMS traffic for that Network Code. The additional Network will advise, at least four weeks in advance, that a routeing change has been requested to that foreign operator and the date the foreign operator will make this routeing change. The routeing of SMS traffic between New Zealand networks can be established by Multilateral and Bilateral Agreements. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 14 of 32

15 8 Carrier Relationships and Network Model 8.1 Carrier Relationships Caller Customer with Ported Number Originating Network Rerouteing Transit Carrier (see note) Originating Carrier (See note) Bypass Carrier Host and Terminating Carrier Donor Network Rerouteing Donor Carrier (see note) Call routeing Note: Carrier may also provide Contracted Service Deliverer function 8.2 Network Model The following Carrier entities may exist in an environment where Numbers are Ported. Their relationships are shown in the diagram above. Note that any given Carrier may be a mix of more than one of the entities - eg a Host Carrier, is generally also a Terminating Carrier Originating Carrier Carrier which originates a call from a Customer connected to its Network Terminating Carrier Carrier which terminates a call to a Customer connected to its Network Transit Carrier Carrier which transits a call on behalf of the Originating Carrier between the Originating and Terminating Carriers Contracted Service Deliverer Entity which provides a contracted service that identifies the Terminating Carrier for calls to Ported Numbers. This service would typically be provided by an Originating Carrier or Donor Carrier and would typically be taken by a Bypass Carrier or Non-participating Carrier. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 15 of 32

16 8.2.5 Donor Carrier Carrier which has been allocated the Number by the NAD, or recognised by the NAD as having been allocated Host Carrier Carrier which provides Network access to the Customer with the Ported Number and is responsible for the routeing and originating of calls to or from that Ported Number Non-participating Carrier Carrier which is not participating in the Porting of Local or Mobile Numbers and which routes calls to Ported Numbers to the Donor Carrier or a Contracted Service Deliverer. An example would be an overseas carrier Bypass Carrier Carrier which provides a call bypass service for a customer, normally for national, international and land-to-mobile calls Previous Host Carrier Carrier which was the Host Carrier for a Ported Number before that Ported Number was Ported. When a Number is first Ported, the Previous Host Carrier is the Donor Carrier. 8.3 Points of Interconnection Interconnection between Carriers to support telephony-based services, normally takes place at a point of interconnection located on the trunk side of a Carrier s exchange. The interface will generally provide ITU No.7 functionality, using nonproprietary technical standards, including provision of CLI to identify outgoing calling lines within the Network The information flow across the point of interconnection shall provide and comply with the following: a) Compliance with industry standards and practices b) Compliance with requirements in relation to emergency service calls, c) Protection of the confidentiality of communications, d) Compliance with requirements for pre-selection, e) Compliance with the NAD numbering plan, f) Provision of calling line identification, g) Provision of number portability in accordance with TCF Codes. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 16 of 32

17 9 Donor and Originating Carrier Re-routeing 9.1 Rerouteing Responsibilities The Originating Carrier is responsible for routeing calls to Ported Numbers to the correct Terminating Carrier. Where there is a Bypass Carrier providing a call bypass service for the caller, the Bypass Carrier takes on this responsibility. When routeing calls to a Ported Number, the Originating Carrier or Bypass Carrier can either: a) Route the call directly to the Terminating Carrier (this assumes that the Originating Carrier has the capability within its network to identify the Terminating Carrier) b) Route the call to the Donor Carrier (this assumes that the Originating Carrier has a Bilateral Agreement with the Donor Carrier to transit calls through their Network) c) Route the call to a Contracted Service Deliverer (this assumes that the Originating Carrier has a Bilateral Agreement with the Contracted Service Deliverer to transit calls through their Network) For the purposes of this Code, option (a) above is termed Originating Carrier Rerouteing and option (b) is termed Donor Carrier Rerouteing. The Originating Carrier or Bypass Carrier may contract out this capability to a Contracted Service Deliverer option (c) who may in turn, utilise either Originating or Donor Carrier Rerouteing. 9.2 Rerouteing Rules a) A Carrier may wish to use a mixture of Originating and Donor Carrier Rerouteing depending on their capability and their Bilateral Agreements with other Carriers. b) A Non-participating Carrier will be required to agree bilaterally with a Carrier to continue to route calls to the Donor Carrier or the Terminating Carrier on their behalf. c) If agreed bilaterally, the Donor Carrier will ensure that they have the capability to transit all calls to the correct Terminating Carrier on behalf of other Carriers for Ported Numbers in their Number ranges. d) The query method used in a Carrier s Network is independent of the rerouteing method used by that Carrier. e) All Carriers using Originating Carrier Rerouteing will need to access the IPMS for call related information. This will include Bypass Carriers. Carriers using Donor Network Rerouteing will not need to access the IPMS provided they can identify calls to their out-ported Numbers. 9.3 Call Diagrams Figures 1 to 5 below are call model charts that illustrate the generality of Donor Carrier Rerouteing, Originating Carrier Rerouteing, hybrid routeing (Originating and Donor Rerouteing), 2 nd port routeing; Bypass Carrier routeing; and Bypass Carrier routeing where they provide the Contracted Service Deliverer function. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 17 of 32

18 In particular, these charts show: the point in the Network at which the fact that the Customer has ported is determined the inter-operability point between Networks (the point of interconnection ) the subsequent routeing of the call to the Ported Number Customer. Fig 1; Donor Network Re-Routeing (for the initial Port) Donor (also Orig) Bypass Host (also Orig; Term.) INTL (also Non- Part g; Orig) Orig. Transit Non-Part g (also Orig) Notes: = No. (B); ported from Donor to Host = Customer who dials B, or 0+B = NP call routeing = NP Point of Interconnect = where the Porting is identified Fig 2; Orig Network Re-Routeing (for the initial Port) Donor (also Orig). Bypass Host (also Orig; Term) INTL. (also Non- Partg; Orig) Orig. (also CSD) Transit Non-Part g (also Orig) Notes: = No. (B); ported from Donor to Host = Customer = dials B, or 0+B = NP call routeing = NP Point of Interconnect = where the Porting is identified Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 18 of 32

19 Fig 3; Hybrid Donor/Orig Network Re-Routeing (for the initial Port) Donor) (also Orig) Bypass Host (also Org; Term) INTL. (also Non- Part g; Orig) Orig. (also CSD) Transit Non-Part g (also Orig) Notes: = No.(B) ported from Donor to Host = Customer dials B, or 0+B = NP call routeing = NP Point of Interconnect = where the Porting is identified Fig 4; 2nd Port Scenario (Hybrid Donor/Orig Network Re- Routeing) Donor (also Orig) Old Host (also Orig) Bypass New Host (also Orig; Term) INTL (also Non- Part g; Orig) Orig (also CSD) Transit Non-Part g (also Orig) Notes: = No.(B) ported from Old to New Host = Customer who dials B, or 0+B = Donor NP routeing = Orig NP routeing = NP Point of Interconnect Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 19 of 32

20 Fig 5; Bypass Scenario (Donor or CSD Network Re-Routeing) (for the inital Port) Donor (also Orig) Bypass (CSD) Host Carr (also Orig; Term). INTL. (also Non- Part g; Orig) Orig. Transit Non-Part g (also Orig) Notes: = ported from Donor to Host = Customer dials 05XY+B = Donor routeing = CSD routeing = NP Point of Interconnect = where the Porting is identified Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 20 of 32

21 10 Call Handling Rules 10.1 Call Handling Solution Carriers that support LMNP will keep the following management information for each number within its allocated blocks: a) if the number is Ported; and b) the Host Carrier Originating Carriers have a responsibility to route calls to Ported Numbers to the Host Carrier, noting that Originating Carriers that do not support LMNP may utilise the Donor Carrier or a Contracted Service Deliverer to perform the routeing. In such cases, the determination of where a number is Ported or not (and any subsequent call routeing), is undertaken by the Donor or Contracted Service Deliverer). The logic diagrams below contain routeing rules which prevent the misrouteing of calls. Figure 6 Shows the routeing options available to a Carrier which supports LMNP. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 21 of 32

22 Figure 7 Shows the routeing options available to a Carrier which receives a call with a HOC where the Carrier can either terminate the call or route the call to the Host Carrier. Figure 8 Shows the routeing options available to a Carrier receiving a call with no HOC. This indicates that the Carrier handing over the call has not determined from information available to it, the Carrier with the Ported Number. Note that if a Donor Carrier receives a call to a Number that has Ported from its Network, and the call is received with no HOC, the Donor Carrier should route the call to either the Host Carrier, if this information is available or to a Contracted Service Deliverer. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 22 of 32

23 Figure 9 DRAFT Shows the routeing options available to a Carrier acting as a Contracted Service Deliver receiving a call with no HOC. In this case, the Carrier passing the call has contracted out its LMNP responsibilities in relation to the call. The Carrier receiving this call is the Contracted Service Deliverer who then determines the correct Host Carrier for the call and hands over the call to the Host Carrier with a HOC. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 23 of 32

24 11 Technical Call Handover and Signalling 11.1 General Inter-Network Signalling Standards Inter-network call control signalling aligns with the relevant ITU/ETSI No.7 signalling standards; noting that the current network interconnection signalling arrangements use these standards in the context of bilateral interconnection agreements General Signalling Capabilities Delivering calls to Ported Numbers In the context of the above standards, there are several alternative arrangements that can be used to determine the required routeing information and to deliver calls to ported numbers. This Code allows, without limitation, for the following alternative arrangements to be used. These arrangements may be used in combination with one another, or alone, depending on the specific call scenario and according to Bilateral Agreement between participating networks. a) Originating Network Rerouteing In this scenario, the network whose customer dials the ported number, determines the routeing required to directly route the call to the ported number (without routeing to the Donor network), and routes the call accordingly. Three alternative methods are available, without limitation, for achieving this. In each case the speech path established for the call does not traverse the donor network, although methods (ii) and (iii) make use of information held in the donor network in order to establish the call. (i) All Call Query (ACQ) Method (ii) Query On Release (QoR) Method (iii) Redirection Method b) Donor Network Rerouteing In this scenario, the network whose customer dials the ported number, routes the call to the Donor network. On receiving the call, the Donor network determines the required onward routeing to the host network, and routes the call accordingly c) Transit Network Routeing By bi-lateral agreement, A Transit network may act as an originating network and perform the originating network role of routeing calls to ported numbers on behalf of the actual originating network. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 24 of 32

25 Delivering calls from Ported Numbers In general, calls originated by Ported Numbers in the Host network use identical signalling procedures to calls originated by non-ported Numbers. However, there are some service consequences of call origination from Ported Numbers, and these are covered in section 11.6 below Other Inter-network Signalling Standards Some current interconnection network call control signalling agreements are based on the R2 MFC signalling standard. To the extent that this signalling standard does not support number portability, carriers using R2 MFC may be required to establish arrangements with other carriers for the handling of calls to ported numbers. Future network technologies and systems may offer alternative inter-network signalling standards that can support Number Portability, and this Code does not preclude these from being used in the future, by agreement between the parties. In cases where such standards are used, the general requirements of this Code are to apply. However, to the extent that the use of such standards conflict with this Code, the Code may need to be amended Definition of Signalling Terms In general, capitalised terminology in this section aligns with ITU No. 7 signalling standards The Customer Number terminology used in this section is: - A: the directory number of the customer originating a call, generally known as the Calling-Party-Number. In the context of porting, A may be: - the number of a customer calling a Ported Number; or - the number of the ported customer when they originate a call - B: the directory number of the customer to which a call is terminated, generally known as the Called-Party-Number. In the context of porting, B may be: - the number of a customer being called by a Ported Number; or - the number of the ported customer when a call terminates to them - C: a number that can be used by a Host Carrier to terminate a call to a Ported Number in their network. A C number is usually a number from the number range associated with the Host Carrier s switch Number Format The full form of the A, B, and C numbers as used in the inter-network signalling (as distinct from the numbers actually dialled by the calling customer), are generally in the form of the ITU E.164 NSN, and for the NZ PSTN and Mobile numbering regime, are: - PSTN Numbers: Area Code+ DN (eg; ; ; etc) - Mobile Numbers: Service Code+DN (eg; ; ; etc) Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 25 of 32

26 Network Routeing Numbers To enable the correct inter-network and onward routeing of calls that terminate to a Ported Number, Carriers may need to use, or choose to use, a Network Routeing Number (NRN) in the signalling. This NRN is generally used as the Called-Directory-Number as in 11.4 (1) below), although the exact structure and content of the NRN may vary between the two signalling standard alternatives. The possible structure and content options of an NRN are: - HOC+B; or - HOC+C; or - HOC (may be relevant in the case of the Industry standard with enhancements - see 11.4 below), or - B (if the Host Carrier agrees to this usage) Where the HOC is a Hand-Off Code as described in section 12; For example; the NRN used for routeing a call to a ported PSTN number could have the contents of the Called-Party-Number as: Signalling for Calls to Ported Numbers Contents of the Initial Address Message (IAM) Signalling Message (1) Calling-Party-Number; Called Party Number; and the NRN For calls delivered to a Host/Transit Carrier, terminating to Numbers ported to the Host Carrier: Current Industry Standard (as per current Interconnection Agreements): - Calling-Party-Number: = A - Called-Party-Number: = NRN (eg; HOC+B) (or optionally, HOC+C) Industry Standard with enhancements - Calling-Party-Number: = A - Called-Party-Number: = NRN (eg, HOC) - Called-Directory-Number: = B (or optionally, C) (2) CLI Information For calls to Ported Numbers: Calling Party CLI and CLIP/CLIR integrity is to be maintained viz: Calling-Party-Number: = A CLIP/CLIR: = as set by the customer Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 26 of 32

27 11.5 Signalling for Calls from Ported Numbers Contents of the IAM Signalling Message (1) Calling and Called Party Number In general, calls originated by Ported Numbers use identical signalling procedures to calls originated by non-ported numbers. However, there are some service consequences of call origination from Ported Numbers, and these are covered in section 11.6 below. (2) CLI Information For calls originated by in-ported Numbers in the Host Carriers Network: Calling-Party-Number: = A CLIP/CLIR: = as set by the Customer 11.6 General Number Integrity Issues Some services related to the handling of special calls between Carriers may be impacted by the implementation of LMNP. Examples of these are described below. It is expected that these issues will be resolved in the context of Multilateral and Bilateral Agreements between the affected Carriers Network Identity Porting means that the Calling Party Number and the Called Party Number will not necessarily uniquely identify the network to which the customer is connected. Some call scenarios (e.g. Operator Services) use these numbers to discriminate between networks, and this may no longer be possible for all calls. (Enhanced No.7 signalling can provide for the use of A Location Number (see below), and this may provide a method of carrying the Network Identity separately from the number.) Location Number (Geographic Identification) If a customer with a ported number changes geographic location (in addition to changing their network access point) the traditional linkage between the ported customer s number and the customer s geographic location may be broken. Geographic origin based routeing services (e.g. emergency calls and 0800PIZZA type calls) assume this linkage in their call routeing algorithm by using the leading digits of the Calling Party Number parameter in order to route calls to the correct answering point. (Where a ported customer s number no longer represents geographic location (to the required level of geographic granularity) originating calls from the ported number may include geographic location information in the address digits of the Location Number parameter included in the IAM used for call set-up) Misc CLI Services - eg; COLP (Connected-Line-Presentation), and DNIS (Dialled-Number-Information Service) These services rely on the integrity of the relevant customer number as it is carried in the signalling. If this number is other than the true number e.g. it has a NRN attached, then the service is compromised. (For further study) Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 27 of 32

28 12 Hand-Off Codes Carriers may agree bilaterally on the method of handing over calls between their Networks. The method may include the use of a separate routes for calls to Ported Numbers or the use of HOCs. If HOCs are to be used, this section will apply HOC Allocation and Format HOCs are codes used in Network and billing systems to identify certain characteristics of calls that are routed between Networks to Ported numbers. HOCs are allocated to eligible Service Providers according to rules specified by the NAD. Details of HOC allocations can be found in the NAD Number Register ( The HOC format is 011XNT where: a) X is currently digits 6 or 9 but may be any other digits allocated by the NAD b) N identifies the Host Carrier Network, and c) T identifies the service (LNP or MNP) These codes are used in the format 011XNTnnn~nnn, where nnn~nnn is the dialled number in National Significant Number (NSN) format. Should such information as calling line geographic identification be required in the T digit, then this will be agreed by the NAD and be the subject of Multilateral and Bilateral Agreements between Carriers HOC Forwarding The Host Carrier will be able to check inbound calls for the HOC and route accordingly. Calls that are determined by the Originating Carrier to be calls to Ported Numbers are to have a HOC added by the Originating Carrier and passed on to the Host Carrier (either directly or indirectly). If the Originating Carrier has an agreement to pass all calls to the Donor Carrier, based on the Numbers allocated to them by the NAD, they may be forwarded without a HOC attached. Attaching a HOC to a call indicates that the Originating Carrier has identified a call to a Ported Number and that the Originating Carrier is aware of the correct Host Carrier HOC Trapping In order to prevent recirculation of calls, which is possible if Carriers records do not match each other, the following approach must be followed: a) A Carrier may transit calls received with a HOC for a third-party Carrier, where this is covered by an agreement with the third party Carrier; b) Carriers will not change or remove the HOC on a transit call; c) Carriers receiving a call with their HOC to a Number for which they are not the Host Carrier (or have no agreement with a third-party to be the Host Carrier) will drop the call; and d) A Carrier may add a HOC and forward calls that have been received without a HOC attached, if this is a service being provided to a Carrier under a Bilateral Agreement. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 28 of 32

29 13 Equivalent Service 13.1 Definition A service provided in relation to a ported number is an equivalent service, if (and only if) any differences, in quality, reliability, services or features, between it and a service provided in relation to a non-ported number: a) will not be apparent to a customer or b) if they are apparent to a customer - will not affect the customer s choice of service provider. In accordance with this definition, the technical solution deployed by service providers must offer customers with ported numbers equivalent service to that offered to customers with non-ported numbers on the same network. The criteria listed or referred to in this code are those that must be used by participating Carriers to assess whether a technical solution it will deploy would constitute equivalent service in accordance with the definition above Equivalent Service Criteria for LMNP The technical solution deployed by Carriers participating in LMNP in New Zealand shall provide an equivalent service which must meet the following criteria: Criterion 1 Post dialling delay There may be an increase in post dialling delay for a call to a customer with a ported number compared to a similar call to a non ported number. This may vary with the routeing and call set up involved. The notion of a similar call requires that comparisons should involve the same call types (for example, long distance, local, calls from mobile phones, and calls from the same origin exchange made at the same time to ported and non-ported numbers at the same destination exchange). The respective post dial delay equivalent service criteria for Local and Mobile call scenarios are as follows: LNP equivalent service Increase of not more than 1 second compared with a similar call to a customer with a non-ported number in 99.9% of all call cases. MNP equivalent service Increase of not more than 3 seconds in 98% of all call cases and not more than 5 seconds in 99.9% of all call cases compared with a similar switched network calls to a customer with a non-ported number. Criterion 2 Call failure The rate of call failure because of congestion or malfunction for calls to ported numbers on either Local or Mobile networks must be no greater than 1 in 100 calls higher than for calls to non-ported numbers. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 29 of 32

30 Criterion 3 Services and features The local and mobile number portability solution deployed by a Carrier must not prevent customers with ported numbers from being offered the same services and features as those provided to customers on the recipient network without ported numbers. This requirement applies to both incoming and outgoing call services and to non-call related features. Criterion 4 End-to-end connectivity The technical solution deployed by any Carrier shall provide end-to-end connectivity by ensuring the successful completion of communications to and from Ported Numbers where such connectivity is provided in relation to non-ported numbers Equivalent Service Compliance Each Carrier has an obligation to provide LMNP equivalent service as defined in this Code. Each affected Carrier will be required to provide a one-off certification that its network complies with the equivalent service criteria based upon its design and implementation. However, the [Enforcement Agency] may require specific measurements to be undertaken by certain carriers and service providers when the [Enforcement Agency] considers this is necessary as part of an investigation by it following a complaint(s). Where a systematic problem is identified, the [Enforcement Agency] may require regular network testing. The [Enforcement Agency] reserves the right to conduct random audits of carriers documentation supporting their claims of compliance with the equivalent service criteria. Telecommunication Carriers Forum LMNP Network Code 22 July 2004 Page 30 of 32