IFAST DOCUMENT IRMG Version 1.0 

 

I N T E R N A T I O N A L

R O A M I N G

MOBILE IDENTIFICATION NUMBER (M I N)

(IRM)

 

 

A S S I G N M E N T      G U I D E L I N E S

A N D

P R O C E D U R E S

 

 

Version: 1.0

May, 1999

 

TABLE OF CONTENTS

1 PURPOSE AND SCOPE 

2 IRM FORMAT AND FUNCTION 

3 ASSUMPTIONS AND CONSTRAINTS 

4 ASSIGNMENT PRINCIPLES 

5 CRITERIA FOR IRM Network Code ASSIGNMENT 

6 RESPONSIBILITIES OF IRM Network Code APPLICANTS AND ASSIGNEES 

7 GRANDFATHERING 

8 MIN RETURN AND RECLAMATION PROCEDURES 

9 MAINTENANCE OF GUIDELINES 

11 CONFLICT RESOLUTION 

10 APPEALS PROCESS 

 

 


1 PURPOSE AND SCOPE

This document contains the guidelines and procedures for the assignment and use of International Roaming Mobile Identification Numbers (MINs) (IRM) for use in Advanced Mobile Phone Service (AMPS) based mobile systems. The use of IRMs has been determined to be a temporary solution for international roaming into AMPS systems, the long term solution being the use of the International Mobile Station Identifier, a 15 digit identifier defined in ITU Recommendation E.212.

Traditionally, the MIN is a 10 digit number that has been identical to the Mobile Directory Number (MDN) and is defined in ANSI/EIA/TIA - 553. This has resulted in conflicts with MINs in various other countries hindering international AMPS based roaming. There has been no centralized administration for MINs and their formats. TSB-29, by listing all known MINs assignments (NANP and Non-NANP) has provided a limited source for assignment coordination. IFAST, has agreed to assume an active role in addressing this problem by administering IRMs in full coordination with TSB-29 and the CTIA MIN Block Identifier (MBI) Assignment Guidelines.

1.1 The IRM administrator manages and coordinates the assignment of the IRMs.

1.2 These guidelines were developed by the consensus of representatives of entities within the AMPS based wireless sector and international wireless networks in which intersystem operations for roaming and handoff are based on versions of EIA/TIA Interim Standard 41, as represented at the International Forum on AMPS Standards Technology (IFAST).

1.3 These guidelines apply internationally among carriers using AMPS based mobile systems and/or to carriers roaming into AMPS based systems from other wireless network technologies. These guidelines do not supersede the regulations, procedures or requirements of the FCC or any other appropriate legal or regulatory authority.

1.4 Additional information may be found on the IFAST web site; www.ifast.org

 

table of contents


2 IRM FORMAT AND FUNCTION

2.1 The MDN-based format of the MIN in the NANP serving area is:

 

NPA NXX XXXX

10 digits

Where

Identifies

NPA

the area code of the mobile's home system

NXX

the central office code

XXXX

the mobile 'line' number

2.2 The International Roaming MIN (IRM) is a valid MIN constrained to having the first digit a "0" or "1". MIN blocks of the format 0XX-XXX and 1XX-XXX should be excluded from assignment by the CTIA MIN Block Identifier (MBI) Administrator.

2.3 MIN Blocks of the format 0XX-XXX and 1XX-XXX (200,000 blocks) are reserved to be assigned by the International Forum on AMPS Standards Technology (IFAST), although some of these MINs have been assigned for specific services in the North American Numbering Plan Area in the past. These past service assignments will continue to be valid in the North American Numbering Plan Area, and should be documented.

2.4 This format avails 200,000 IRMs

2.5 The first four digits of each IRM are assigned by the IRM administrator. The three digits following the most significant digit containing the value 0, or 1 is called the Network Code. The following six digits are assigned by the recipient of the IRM.

 

table of contents


3 ASSUMPTIONS AND CONSTRAINTS

These guidelines are based on the following assumptions and constraints:

3.1 These guidelines and procedures should provide the greatest latitude to those providing AMPS based mobile systems, as well as other wireless technologies carriers providing roaming into AMPS based systems, while permitting the effective and efficient management of a finite resource.

3.2 The function of the IRM administrator will be performed by a person(s) or organization so agreed to by the IFAST. The IFAST management is responsible for IRM assignaments if such a body is not agreed to.

3.3 These guidelines do not describe the method by which IRMs are transmitted across and processed by networks. Network interworking arrangements are contained in other standards, documents, or business agreements.

3.4 Participation by all international carriers engaged in providing public correspondence based on wireless medium is strictly voluntary.

 

table of contents


4 ASSIGNMENT PRINCIPLES

The assignment principles defined below allow all international wireless carriers the greatest possible latitude in providing seamless international roaming capabilities in AMPS based systems.

4.1 IRMs are to be assigned, to any wireless carrier meeting the criteria specified in Section 5 of these guideline, to provide roaming in AMPS based networks.

4.2 Upon approval of the application, the IRM adinistrator will initially assign one IRM (country code/network). An applicant must provide customer forecasts to the IRM administrator when more than one code is requested.

4.3 IRMs shall be assigned to permit the most effective and efficient use of a finite resource in order to maximize the existing allocated resource inventory and to defer, as long as practical, the need to request additional MIN resources.

4.4 The IRM administrator will:

Assign IRMs in a fair, timely and impartial manner to any applicant that meets the criteria for assignment (Section 6).

Assign IRMs on a first come, first served basis from the available pool.

Make all assignments based on the procedures in these guidelines.

Treat sensitive information received from applicants as proprietary and confidential, and not to be shared with non-administrator personnel.

4.5 Information that is requested of applicants in support of an IRM application shall be uniform and kept to a minimum.

4.6 Assigned IRMs should be deployed as soon as possible, but no later than twelve months after assignment. If the assignee can demonstrate that an assigned IRM has not been deployed solely due to delays beyond its control, the time period can be extended for up to 90 days. At the discretion of the administrator, three additional 90-day extensions may be granted.

4.7 Any IRMs assigned to meet the purpose of a "reserve" may be held by the applicant for a period not to exceed 3 years from the date of original assignment at which time the IRM Administrator may reclaim any unused reserve IRMs

4.8 An entity which is denied an IRM assignment or extension under these guidelines has the right to appeal that decision (Section 10).

4.9 There may be an administrative fee associated with an application for an IRM Network Code.

4.10 As required, applicants for IRMs must comply with all applicable regulations.

 

table of contents


5 CRITERIA FOR IRM Network Code ASSIGNMENT

5.1 The assignment criteria in the following paragraphs should be considered by a potential IRM applicant before submitting an IRM application and will be used by the IFAST in reviewing and processing an IRM application.

5.2 International Roaming MINs Network Codes will be assigned to all AMPS based cellular networks that are located in countries which are outside of the North American Numbering Plan area countries and have desire to provide roaming with countries included in NANP. All international wireless networks outside of the NANP area countries, including Global Mobile Satellite Service networks (which are based on intersystem operations for roaming which are not compatible with roaming protocol specified in all versions of the EIA/TIA/ANSI 41 standards, and have desire to provide roaming in AMPS based networks throughout the world with mutimode handsets and appropriate protocol conversion functions for mobility management signaling messages) are eligible for the assignment of IRMs.

 

table of contents


6 RESPONSIBILITIES OF IRM Network Code APPLICANTS AND ASSIGNEES

Entities requesting IRMs assignments and entities already assigned one or more IRMs shall comply with the following:

6.1 IRM Netwok Code applicants and assignees must meet all conditions specified in these guidelines. Copies of the guidelines may be obtained from the IRM network Code administrator.

6.2 Applicants must apply in writing to the IRM Network Code assignment administrator once their petition has been approved by the IFAST Forum.

 

table of contents


7 GRANDFATHERING

These guidelines make no attempt to "Grandfather" any previous assignments of MINs or IRM allocations. Use of all assigned resources on a going forward basis shall be consistent with these guidelines.

 

table of contents


8 MIN RETURN AND RECLAMATION PROCEDURES

8.1 The IFAST will track and monitor IRM assignments and assignment procedures to ensure that all assignments of IRMs are being used in an efficient and effective manner. Ongoing Administrator procedures that foster conservation shall include, but not be limited to, the following:

  1. An active reclamation program to reclaim unused or misused IRMs.

  2. Strict conformance with these guidelines by those assigning IRMs.

  3. Appropriate and timely recommended changes to these guidelines, if they are found to result in inefficient use or assignment of IRMs.

  4. Periodic specific and random audits of assignments and assignment procedures.

  5. An IRM Network Code recovered or returned to the administrator for reassignment will remain dormant for a period of not less than one year, from the date of return to the IRM Network Code pool, before reassignment.

8.2 Reserved IRMs may be held by the applicant for a period not to exceed 3 years from the date of original assignement at which time the IRM Administrator may reclaim the IRMs

 

table of contents


9 MAINTENANCE OF GUIDELINES

It may be necessary to modify the guidelines periodically to meet changing and unforeseen circumstances. The need for guidelines modification may be identified by the administrator, any entity in the international wireless telecommunications sector or the IFAST Forum. When need for modification is identified by other than the forum, the identifying entity will submit the modification issue to the forum. The forum will coordinate the modification process. Questions or concerns regarding the maintenance of the guidelines may be directed to:

IFAST Management

Attn: IRM Administrator

c/o CTIA

1250 Conecticut Ave N.W.

Suite 800

Washington, DC 20036

 

table of contents


11 CONFLICT RESOLUTION

11.1 Every attempt wll be made at the time of allocation to avoid conflicts with existing IRMs. Organizatons requesting specific IRMs should first seek the IRM availability by checking the listings found on the IFAST web site, www.ifast.org.

11.2 If a conflict, at some later point, is determined to exisit, the following process should be followed:

  • Notify the IFAST management in writing

  • Contact the organization(s) with whom the conflict exists and attempt a resolution. Then notify the IFAST management in writing.

  • If resolution cannot be achieved, the issue may be brought before the IFAST for a recommended solution.

 

table of contents


10 APPEALS PROCESS

Disagreements may arise between the IRM Network Code Administrator and IRM Network Code applicants or assignees in the context of the administration and management of these guidelines. In all cases, the IRM Administrator and IRM applicants/assignees will make reasonable, good faith efforts to resolve such disagreements among themselves, consistent with the guidelines, prior to pursuing any appeal. Appeals may include, but are not limited to, one or more of the following options:

The IRM applicant/assignee will have the opportunity to resubmit the matter to the IFAST for reconsideration with or without additional input.

Guidelines interpretation/clarification questions may be referred to the appropriate wireless industry forum for rsolution. Unless otherwise mutually agreed to by the parties, these questions will be submitted in a generic manner protecting the identity of the appellant.

The applicant/assignee may pursue the disagreement with the appropriate governmental/regulatory body.

Reports on any resolution resulting from the above options, the content of which will be mutually agreed upon by the involved parties, will be kept on file by the administrator. At minimum, the report will contain the final disposition of the appeal; e.g., whether or not an IRM was assigned.

 

table of contents