International Roaming Guide
International Roaming Guide
International Roaming Guide
Guide
IFAST INTERNATIONAL R OAMING GUIDE
Disclaimer
This International Roaming Guide is informational in nature. It provides
guidance to service providers regarding issues related to, and aspects of,
International Roaming implementation. The information contained here
should not be construed as implementation mandates. Service Providers
should adapt the information to suit their unique telecommunications
environment.
Revision History
Revision Description Date
1.0 Initial Draft Release. 01/08/1999
4.1 Additional edits by Syed Zaeem Hosain of Aeris.net and David Crowe of Cellu - 05/02/2001
lar Networking Perspectives.
Revision
1.0 New version. Initial Release. 08/08/2001
1.3 Format revision and additional editing by Syed Zaeem Hosain of Aeris.net. 03/25/2003
1.4 Editing by Syed Zaeem Hosain of Aeris.net based on feedback from IFAST 10/21/2003
members.
Table of Contents
Table of Contents.......................................................................................................................... 3
1 Introduction............................................................................................................................ 6
1.1 International Roaming...................................................................................................... 6
1.2 Scope ............................................................................................................................... 7
1.3 Issue Categories .............................................................................................................. 7
1.4 Issue Subsections ............................................................................................................ 7
2 Numbering Issues.................................................................................................................. 8
2.1 International Roaming MIN (IRM) Assignment ................................................................ 8
2.1.1 Description...................................................................................................................8
2.1.2 Resolution ....................................................................................................................8
2.1.3 Recommendation .........................................................................................................9
2.2 MIN/MDN Separation ....................................................................................................... 9
2.2.1 Description...................................................................................................................9
2.2.2 Resolution .................................................................................................................. 10
2.2.3 Recommendation ....................................................................................................... 10
2.3 SID Assignment...............................................................................................................11
2.3.1 Description................................................................................................................. 11
2.3.2 Resolution .................................................................................................................. 11
2.3.3 Recommendation ....................................................................................................... 11
2.4 International TLDN ..........................................................................................................11
2.4.1 Description................................................................................................................. 11
2.4.2 Resolution .................................................................................................................. 12
2.4.3 Recommendation ....................................................................................................... 12
2.5 IMSI Implementation ...................................................................................................... 13
2.5.1 Description................................................................................................................. 13
2.5.2 Resolution .................................................................................................................. 13
2.5.3 Recommendation ....................................................................................................... 13
2.6 MSC Identity................................................................................................................... 14
2.6.1 Description................................................................................................................. 14
2.6.2 Resolution .................................................................................................................. 14
2.6.3 Recommendation ....................................................................................................... 14
2.7 DPC Assignment............................................................................................................ 15
2.7.1 Description................................................................................................................. 15
2.7.2 Resolution .................................................................................................................. 15
2.7.3 Recommendation ....................................................................................................... 16
3 Dialing Issues....................................................................................................................... 18
3.1 Uniform Dialing Plan ...................................................................................................... 18
3.1.1 Description................................................................................................................. 18
3.1.2 Resolution .................................................................................................................. 18
1 Introduction
At the IFAST-9 meeting, IFAST members recognized the need for a set of
recommendations and guidelines to help carriers—who were interested
in providing International Roaming to their subscribers—become more
knowledgeable about the issues/problems and the resolutions. The pri-
mary purpose of this document, the International Roaming Guide (IRG),
is therefore to provide, to all carriers using the ANSI-41 standard world-
wide, a description of some of the issues relating to International Roam-
ing. The lessons learned, along with input from carriers who have dealt
with these issues, may help other carriers benefit from the experiences,
and find common approaches or solutions to the challenges facing Inter-
national Roaming implementation.
1 For example, roaming between Canada and the United States of America.
1.2 Scope
This document describes some of the issues, challenges and concerns re-
lated to International Roaming and, where possible, suggest how carriers
can deal with them effectively. However, it is not intended to serve as a
standard or to provide a process for implementing International Roa m-
ing. Ideally, the need for this document will diminish as standards for
supporting International Roaming evolve and carriers implement them.
The issues covered in this IRG are classified into the following catego-
ries—new issues may be included in these categories, or new categories
may be created if deemed necessary:
l Numbering Issues.
l Dialing Issues.
l Fraud Issues.
l Billing Issues.
l Signaling Issues.
l Services Issues.
l Miscellaneous Issues.
2 Numbering Issues
2.1.1 Description
2.1.2 Resolution
When assigning IRM Network Identifiers, IFAST tries to ensure that these
numbers are not used by any other entity or applications that may con-
flict with International Roaming, and posts the latest assignments on its
Web site (www.ifast.org) for public access. However, IFAST does not
have the intent to enforce compliance; rather, it encourages carriers and
other interested entities to follow its guidelines with full cooperation, and
2.1.3 Recommendation
More than half of the IRM Network Identifiers have been assigned—at a
rate much faster than expected—and some numbering conflicts are al-
ready beginning to appear (although many have been resolved.) Carriers
must recognize that IRMs are a short-term solution to a long-term prob-
lem, and should try to define and implement other global standards—
such as International Mobile Subscriber Identity (IMSI) and Global Title
Translation (GTT)—for International Roaming.
2.2.1 Description
The separation of the MDN and MIN has been chosen as the method to
retain the ability to identify the home service provider of a wireless sub-
scriber while still enabling the MDN to be portable. All the wireless carri-
ers who roam must do MIN/MDN separation for WNP. Even non-
porting wireless service providers, whether they are outside the top 100
MSAs within the US or international, may have to separate the MIN and
the MDN to support roaming for porting wireless service providers in-
side the top 100 MSAs.
The potential roaming impacts are:
2.2.2 Resolution
l Update the billing systems to ensure that they consistently and cor-
rectly use either the MIN or MDN.
l Identify mobiles via the MDN and not the MIN to emergency ser-
vices or long distance companies.
l Allow roamer ports to use the MDN and not the MIN.
l Upgrade the databases and switches to support both the MDN and
the MIN.
The US wireless industry is currently implementing MIN/MDN separa-
tion through the creation of an MBI assignment authority.
2.2.3 Recommendation
It should be noted that the use of the IRM does not force MIN/MDN
separation, as it may still be possible to derive one number from the other
by deleting and prefixing digits. However, the use of the IRM may allow
an opportunity to introduce this separation while network changes are
being made. The advantages of implementing MIN/MDN separation are
important enough that IFAST recommends it highly.
2.3.1 Description
2.3.2 Resolution
IFAST is responsible for the management of the SID resource and posts
the assignments of SIDs, and all known SID conflicts, on its web site
(www.ifast.org). It is imperative that carriers and regulatory agencies co-
operate and comply with IFAST assignments, and report conflicts.
2.3.3 Recommendation
2.4.1 Description
2.4.2 Resolution
2.4.3 Recommendation
It is important to note that IS-41 Revision C was published with the Na-
ture of Number parameter incorrectly specified as Value 0 for Intern a-
tional and 1 for National. Carriers must ensure that only the ANSI-41D
encoding of this parameter field is used.
2.5.1 Description
2.5.2 Resolution
In the US, a special IMSI format (310+00+MIN, where 310 is the MCC, so-
called “MIN-based IMSI”) has been defined considering backward com-
patibility. Although the concept of the MIN-based IMSI is useful in other
countries, it is not universally possible to designate “00” as the
IMSI_11_12 (first two digits of MNC) for the MIN-based IMSI for all the
MCCs since the MNC numbering plan is a national matter. If this tech-
nique is not universally supported, when a mobile terminal with the
MIN-based IMSI sends a registration request to the HLR, the HLR may
not be able to recognize the ANSI-41 IMSI parameter and the registration
may fail. A list of MIN-based IMSIs should be shared among roaming
partners and programmed in their Mobile Switching Centers (MSC) to
solve this problem.
2.5.3 Recommendation
2.6.1 Description
The identity of the MSC/VLR is registered at the HLR during the location
registration procedure and used to send a message asking for the TLDN.
Three parameters, PC_SSN, MSCID, and MSCIN (MSCIdentification-
Number) are defined for this purpose in the ANSI-41. There were uncer-
tainty and confusion as to how these three parameters should be used
within an International Roaming environment.
2.6.2 Resolution
The PC/SSN should not be used for International Roaming because the
numbering plan of the PC/SSN is a national matter, while the MSCID in-
cludes the ma rket ID field, whose value is usually the SID, and the
MSCIN is an E.212 number (IMSI). The MSCID is a mandatory parameter
in the REGNOT and the MSCIN is optional. However, either the MSCID
or the MSCIN can be used to identify MSC for International Roaming.
Should MSCID be used, a lower layer signaling conversion function may
be required in cases where the lower layer protocol—e.g., Mobile Transfer
Point (MTP)—is different, by for example, maintaining a conversion table
between ANSI point code and ITU -T point code. This table must be de-
signed efficiently such as in the way of the cluster entry. If the MSCIN
were used, Signaling Connection Control Part (SCCP) GTT should also be
supported. The introduction of the SCCP GTT has a big impact on the
system, requiring extensive international coordination and therefore the
use of MSCIN should only be considered as a long-term solution.
2.6.3 Recommendation
The MSCID be used as the identity of MSC in short-term, and the MSCIN
for a long-term solution.
2.7.1 Description
2.7.2 Resolution
l Reduce the number of digits analyzed in SPs and STPs in the visited
network, thereby increasing routing analysis performance in each in-
volved node.
2.7.3 Recommendation
3 Dialing Issues
3.1.1 Description
l Directory Assistance.
l Emergency Calling.
Routing should be, if possible, to a service that can speak the preferred
language of the subscriber (as transmitted by ANSI-41).
3.1.2 Resolution
Being Revised.
3.1.3 Recommendation
Being Revised.
3.2.1 Description
3.2.2 Resolution
3.2.3 Recommendation
Being Revised.
3.3.1 Description
3.3.2 Resolution
l Use of the roamer port (works only with mobile-to-mobile calls, and
requires knowledge of the local roamer port number by callers).
l Redirection via ISUP or ANSI-41 solution by means of the Release-
To-Pivot capability, in accordance with the national and international
SS7 standards
l In-band signaling, as proposed for tandem-free operation
3.3.3 Recommendation
Being Revised.
4 Signaling Issues
4.1.1 Description
4.1.2 Resolution
Being Revised.
4.1.3 Recommendation
Being Revised.
Being Revised.
4.2.1 Description
Being Revised.
4.2.2 Resolution
Being Revised.
4.2.3 Recommendation
Being Revised.
Being Revised.
4.3.1 Description
Being Revised.
4.3.2 Resolution
Being Revised.
4.3.3 Recommendation
Being Revised.
5 Fraud Issues
5.1.1 Description
Fraud has been one of the major obstacles to International Roaming and is
an expanding problem in the wireless industry. It would be difficult to
grasp the full impact of fraud since operators do not consistently or uni-
formly track fraud losses. The Cellular Telecommunications Internet As-
sociation (CTIA) estimates fraud losses in North America in 1996 were
$900M, or about 3.6% of industry revenues. Although fraud losses have
been steadily declining, fraud still represents a serious threat globally.
Fraud has taken different forms and is continuously changing its nature.
There are generally three types of Fraud:
l Cloning Fraud – Changing the ESN after every call (tumbling) has
been largely replaced with cloning of the phones. Cloning fraud oc-
curs when the identity of the mobile phone is stolen. When the mo-
bile unit presents its identity to the network, a criminal scanning the
airwaves can steal the phone’s identification numbers, the ESN and
mobile number, and then program them into another phone. When
this cloned phone is used, the charges appear on the legitimate sub-
scriber’s bill.
l Subscription Fraud – Subscription Fraud is another type of wireless
fraud, which occurs when a criminal uses fraudulently obtained cus-
tomer information or a false identity to subscribe to wireless service
without any intention of paying for service. True name subscription
fraud occurs when a criminal steals a person’s identity. GSM opera-
tors in Europe have suffered significant subscription fraud losses for
years while enjoying protection against cloning fraud through the au-
thentication capabilities inherent in their digital technology. In addi-
tion to subscription fraud, operators are experiencing hacking into
their networks to obtain access to confidential information, such as
MIN/ESN combinations. Many operators are unaware of where their
weaknesses are and should perform external testing to determine
their vulnerabilities.
5.1.2 Resolution
5.1.3 Recommendation
6 Billing Issues
6.1.1 Description
In order to reap the financial rewards that International Roaming can de-
liver, an operator must have an efficient process in place for the exchange
of roamer billing records, validation or editing of those records, and sys-
tems for calculating and reporting financial positions with its roaming
partners. Other elements that are essential to inter-operator relationships
include record conversion to the appropriate billing record format,
wholesale and retail rating of records and ultimately financial settlement
with the exchange of funds with roaming partners. Managing hundreds
of roaming agreements with roaming partners in different countries and
time zones that are potentially utilizing different billing record formats
and operating on different settlement cycles poses a significant adminis-
trative problem for any operator interested in International Roaming.
6.1.2 Resolution
Being Revised.
6.1.3 Recommendation
Being Revised.
l Multiple market identifiers for one carrier via the use of Billing Iden-
tifiers (BIDs).
TAP was originally designed for the European community, and later its
use was expanded to other continents, when GSM was adopted in the
United States. At that time, operators received a license for regional mar-
kets—therefore intra-country roaming was established. For a number of
years, there were, at most, two to four providers in a country, therefore
operators built or purchased their own billing systems and did not out-
source to a billing vendor. Since operators had their own billing systems,
data clearinghouses were initially used only for file validation and rout-
ing.
dard and included the use of BIDs and the separation of air, toll and tax.
TAP 3 is expected to be in use industry-wide by March 31, 2000, and the
Rejects and Returns process by September 30, 2000. Although the stan-
dard for TAP 3 is frozen, not all operators will adopt it, as GSM allows for
bilateral agreement on use of a standard. Operators in countries that do
not utilize the new fields may agree to continue exchanging TAP 2 or
TAP 2+.
CIBER TAP
Rejects and Returns process in place. No Rejects and Returns process today.
On rejects, individual records or whole files can be If a file contains an error, the whole file is rejected.
rejected if failing edits. Individual records in the file are not rejected, a l-
though this is changing. Some operators are now
doing record-level rejecting, but there is no process
in place to return rejected records to the submitting
operator.
The industry settlement period is mid-month at the The industry settlement period is at the end of the
15th of the month. calendar month.
Uses 10-digit MIN to identify subscriber. Uses 15-digit IMSI to identify subscriber. Used
similar to an account number. MSISDN is the a c-
tual dialable number of the subscriber.
Able to separate air and toll charges and to specify Only 1 charge filed so separation of charges is not
multiple types of taxes. possible. In addition , there are not multiple tax
fields. (A new record has been defined to provide a
breakout of toll charges, but it is not currently be-
ing used and probably will not be used in the fu -
ture.)
All charges on records indicate an actual dollar All charges are in Special Drawing Rights (SDR)
amount. and require conversion to the country’s currency.
In addition, negative charges (credits) cannot be
handled.
Time duration fields on the records are reported in Time duration fields are reported in seconds only.
minutes and seconds.
US carriers rely heavily on SID/BID information in SID/BID does not exist. The PLMN or Operator
reporting and segmenting of their markets. code is the lowest level of distinction. Although
MSCID is on records and could be used as a dis-
tinction for reporting, the MSCIDs do not necessar-
ily denote geographic areas. Some operators set up
their MSCs by criteria other than geographical loca-
tion.
Time zones are indicated by a Time Zone Indicator. Time zones are indicated by a UTC Time Offset
(difference between local time and Greenwich
Mean Time).
6.2.2 Recommendation
6.3.2 Reporting
7 Services Issues
7.1.1 Description
7.1.2 Resolution
7.1.3 Recommendation
7.2.1 Description
The WIN capabilities that have been developed so far are “service inde-
pendent.” The following provides a list of potential services using WIN
capabilities:
l Prepaid Services.
l Wireless Group Conferencing Services.
7.2.2 Resolution
IP SCP To SN Pi External
C2 HLR CCF Networks
(PSPDN, PSTN,
SDF SDF ISDN)
SRF C3 C7 Ai
SCF
SCF To
HLR C4 SRF
Di
C5 C1 C6
CCAF
MSC
Pi
MS BTS BSC SSF
Um Abis A CCF
RTF RCF RACF Ai
RACF
MMF
Di
F
C B
HLRF
SDF SDF
H D MMF G To
SDF
VLR
SCF SCF
MMF
During call processing, when a trigger is armed and the condition is met,
the MSC will stop processing the call and launch a query to the WIN ser-
vice logic as defined in the WIN standards. The WIN service logic will
process the request and instruct the MSC to continue call processing ac-
cording to the instruction. The standards define a set of network capabili-
ties based on service drivers. Capabilities developed for these service
drivers can be used to develop other WIN services.
The following three standards packages have been or are being devel-
oped by the TIA (Telecommunications Industry Association) TR-45 Engi-
neering Committee:
l Package 1 (WIN Phase I): Defines the architecture, provides the first
batch of triggers and capabilities for basic call origination and call
termination, and supports services such as Calling Name Presenta-
tion, Incoming Call Screening and Voice Controlled services. The
standards documentation has been published as TIA/EIA/IS-771.
l Package 2 (WIN Phase II): Adds the second batch of triggers and ca-
pabilities, and supports Charging Services such as Prepaid,
Freephone, Premium Rate, and Advice of Charging. The standards
documentation has been recommended for publication as
TIA/EIA/IS-826 for Prepaid and 848 for other Charging Services.
l Package 3 (WIN Phase III): Adds the third batch of triggers and ca-
pabilities, and supports Location Based Services such as Location
Based Charging, Fleet and Asset Management, Location Based In-
formation Service, and Enhanced Calling Routing. The standard
documentation is currently being under development and is to be
published as TIA/EIA/IS-843.
To support the above packages for inter-systems operations, the TIA TR-
45 Engineering Committee has also completed and published the related
standards documentation as per ANSI-41 Revision D. WIN has impact to
many of the messages in IS-41D. The fields required vary depending on a
specific WIN feature.
7.2.3 Recommendation
l Service Control Point (SCP) in support of the HLR and/or the SIM.
WIN, in general, does not affect the mobile units. Some features (such as
Calling Name Presentation) may require display capabilities on the mo-
bile, but most features will not affect the handset.
MSCs and HLRs must be upgraded to allow the triggers to be
downloaded to the switch during the registration process. The HLR may
also act in the role of a SIM, so the SIM itself is optional. Flexible Service
Logic Programs (FSLP’s) will also be needed, but the interface between
the SIM and the FSLP is not standardized, and varies from vendor to
vendor. It is also possible to have several SIMs in the same network offer-
ing different services. Each company will need to determine its needs and
its engineering plans prior to installation. SIMs, or HLRs acting as SIMs,
are complicated systems in their own right, and should be studied well
before installation. Contacting vendors early for training is highly sug-
gested.
The main communications path for WIN and roaming partners is SS7.
WIN will work as long as SS7 connectivity exists, however, Global Title
Translation and use of the IMSI is highly suggested to simplify the long-
term support issues with roaming partners.
In general, WIN allows for a very quick reversal of the installation proc-
ess by simply changing the user profile in the HLR. Additionally, WIN
tends to reduce the need for new MSC and/or HLR loads since their ac-
tion is always the same. New services require only a new FSLP (and per-
haps a new SIM) to add this feature to the network.
8 Miscellaneous Issues
8.1.1 Description
8.1.2 Resolution
Being Revised.
8.1.3 Recommendation
Being Revised.
8.2.1 European and Asian GSM Carriers Roaming Into ANSI-41 markets
l The ANSI serving market may require that the GSM carrier become a
member of the CIBERNET net settlement program.
l While roaming in ANSI markets, roaming subscribers will be
charged for airtime on incoming calls.
l Choice of Law: Spell out specifically which state and national legal
system will be used to judge and interpret the roaming agreements.
l Liability: Do not make assumptions about fraud liabilities. Spell out
fraud notification procedures, response procedures, and ultimate fi-
nancial responsibilities in the case of fraud.
l Charges: Spell out in detail exactly what charges and taxes will be
imposed on roamers.
look very little like the E.164 number that would be required to reach it
internationally.
Successful call delivery will depend on the ability somewhere in the pro-
tocol conversion chain to recognize exactly where the roamer is, and ma-
nipulate the temporary number that is returned in response to a PRO-
VIDE_RN (GSM MAP) or ROUTEREQ (ANSI-41) message. In certain ar-
eas of the Americas, this will be a daunting task.
There are several fraud management tools available when roaming with
ANSI-41 carriers. Unfortunately, for the GSM carrier, they are signifi-
cantly different from those currently employed in their own environ-
ments.
8.2.3.1 Authentication
Authentication is available in many, but certainly not all ANSI markets.
Further complicating the issue of authentication is that the ANSI handset
being carried by the subscriber cannot be authenticated against his or her
home Authentication Center (AC). The authentication algorithms in use
in ANSI markets are not compatible.
There are methods available for the GSM carrier to authenticate handsets
roaming in ANSI markets through external ANSI authentication centers
or protocol converters that have ANSI authentication center capabilities
incorporated in to them.
8.2.4.1 Services
GSM Subscribers are used to receiving many special services and features
while roaming in a GSM network. In an ANSI-41 network, these features
may not be available. Most basic call controls features such as call ba r-
ring, caller identification, and call forwarding should be available in most
markets, but there are no guarantees.
One expected service that may not be available is SMS. Roaming SMS
termination is only beginning to be adopted by ANSI-41 carriers and mo-
bile origination while roaming is even rarer. GSM operators should con-
tact each of their roaming partners and determine features provided to
roamers.
9 Glossary
Billing Identifier BID A SID allocated for accounting purposes, and ad-
ministered by CIBERNET Corp.
Cellular Inter -carrier Billing Ex- CIBER Tape format for wireless billing records. Maintained
change Record by CIBERNET Corp.
Industry Association
Network Element
Base Station Controller BSC The ‘brains’ of a base station, controlling the radio
equipment in the BTS.
Subscriber Identification Module SIM “Smart Card” for a GSM phone (See UIM).
Numbering Term
International Mobile Subscriber IMSI Formerly called International Mobile Station Iden-
Identity tity. Based on the ITU -T E.212 numbering plan.
International Roaming MIN IRM A MIN beginning with the digit 0/1 that uniquely
identifies a mobile that does not have a DN , to avoid
conflict with NANP MINs.
MIN Block Identifier MBI A 6-digit code used to identify a block of MIN codes
within the NANP.
Mobile Country Code MCC A 3-digit number that is assigned to a single coun-
try. The first three digits of an E.212 IMSI.
Sub-system Number SSN Along with PC, identifies and SS7 network applica-
tion or a virtual SS7 network entity.
Temporary Local Directory Number TLDN A number used for routing calls from the Home
MSC to MSC-V.
Temporary Mobile Station Identity TMSI Used as a shorter, more private, mobile identifier.
Identifies the system that assigned it and not the
mobile directly.
Standards Document
Standards Organization
Standard Development Organiza- SDO The TIA and ATIS are examples of SDOs.
tion
Signaling Term
ISDN User Part ISUP SS7 call processing signaling between switches
Message Application Part MAP Protocol that interconnects wireless telephone sys-
tems (e.g., MSCs and HLRs)
Signaling Connection Control Part SCCP SS7 enhanced routing and identification layer
Signaling Point SP
Technical Term
Calling Party Pays CPP The calling party pays for calls to mobile, not the
mobile receiving the call
Time Division Multiple Access TDMA Modulation technique used by D-AMPS and GSM.
Wireless Intelligent Network WIN Protocol with similar goals as IN and AIN.
10 Contact Information
For more information on the IFAST, please contact the IFAST Secretariat:
Megan Hayes
ATIS
1200 G Street, NW, Suite 500
Washington, DC 20005, USA .
Tel: +1-202-662-8653
Fax: +1-202-393-5453
Email: mhayes@atis.org
For more information on IRMs, please contact the IRM Administrator:
David Crowe
Cellular Networking Perspectives
2636 Toronto Crescent NW
Calgary, AB, T2N 3W1, CANADA.
Tel: +1-403-289-6609
Fax: +1-403-289-6658
Email: David.Crowe@cnp-wireless.com
11.1 Introduction
1.1 As used in this Agreement, the terms below shall have the follow-
ing meanings:
Clearinghouse means that entity that provides for the exchange of CIBER
records and performs industry accepted CIBER edits, including edits to
verify Industry Negative File information.
CMRS means Commercial Mobile Radio Service.
ESN means the Electronic Serial Number that is encoded in a wireless
telephone set by the manufacturer and which is broadcast by such tele-
phone.
Home Carrier means a Party who is providing Service to its registered cus-
tomers in a geographic area where it holds a license or permit to construct
and operate a mobile wireless radiotelephone system and station.
Industry Negative File means the negative file maintained by the author-
ized Clearinghouses in accordance with approved CIBERNET Negative
File Guidelines.
Roamer means a customer of one Party who seeks Service within a geo-
graphic area served by the other Party.
Service means telecommunications service for the transmission and recep-
tion of voice and voice-related features provided by means of radio fre-
quencies that are or may be licensed, permitted or authorized now or in
the future by the Federal Communications Commission (or any successor
agency or other equivalent governmental agency in other countries), and
in respect of which service the user equipment is capable of and intended
for usage during routine movement, including halts at unspecified points,
at more than one location throughout a wide area public or private wire-
less network. Unless otherwise specifically agreed by the Parties, Service
shall include personal base station services but, by way of example and
without limitation, does not include fixed wireless services, two-way
messaging wireless services (NBPCS), video broadcasting wireless ser-
vices, television services (whether cable, broadcast or direct broadcast
satellite), broadcast radio services, interactive informational or transa c-
tional content services such as on -line content network services, Internet
based services, and air to ground communications services.
Serving Carrier means a Party who provides Service for registered cus-
tomers of another Party while such customers are in the geographic area
where the Serving Carrier, directly or through subsidiaries, provides Ser-
vice.
ARTICLE II
PROVISION OF SERVICE
2.1 Each Party shall provide, to any Authorized Roamer who so re-
quests, voice communication service and any and all other types of Ser-
vice that such Party provides to its own customers. Notwithstanding the
foregoing, the Serving Carrier shall not be required to modify or supple-
ment its system in any way to address any incompatibility in the tech-
nologies used by the Serving Carrier and the Home Carrier that may pre-
clude the provision of Service to an Authorized Roamer. Service shall be
provided in accordance with the Serving Carrier’s own ordinary re-
quirements, restrictions, practices, and tariffs, if applicable, and with the
terms and conditions of this Agreement.
may be made upon at least fifteen (15) days prior written notice to the
Serving Carrier. Such notice shall be in the form attached as Exhibit B to
this Agreement and shall include the requested effective date for the ad-
dition, deletion or change.
4.2 Each Party shall provide to each other Party a list of MINs (from
among those within the NPA/NXX combination(s) identified pursuant to
Section 4.1 hereof) and ESNs (of the telephones to which the other Party
is not authorized to provide Service pursuant to this Agreement), which
shall be entered into the Industry Negative File. The approved CIBER-
NET Negative File Guidelines, as amended from time to time, shall be the
governing criteria for the Parties. Thereafter, from time to time, as agreed
by the Parties, each Party shall notify each other Party of all additions to,
and deletions from, these lists for the customers of that particular Party.
Such notifications shall be made during normal business hours of the
Party being notified by facsimile or by telephone with a written confirma-
tion and shall be effective one (1) hour after receipt.
4.3 Each Party hereby agrees to indemnify each and all of the other
Parties, together with their partners and any and all of their officers, di-
rectors, employees, agents and/or affiliates, against, and hold them
harmless from, any and all claims, suits, demands, losses and expenses,
including reasonable attorneys' fees and disbursements, which may result
in any way whatsoever from the indemnified Party's denial of Roamer or
local Service to any NPA/NXX and MIN combination which has been
listed by the indemnifying Party as not being authorized to receive Ser-
vice; provided that (i) the person seeking indemnification (the “Indemni-
fied Person”) provides notice of such claim promptly after its discovery to
the Party from which indemnification is sought (the “Indemnifying Per-
son”) and in any event the Indemnifying Person will be released from any
obligation hereunder to the extent it is prejudiced by any delay in the de-
livery of such notice, (ii) the Indemnifying Person shall have the right to
assume the defense of such claim, (iii) the Indemnified Person shall pro-
vide such reasonable assistance and cooperation in the defense of such
claim as is requested by the Indemnifying Person, and (iv) the Indemni-
fied Person shall not settle or compromise any such claim without the
prior written consent of the Indemnifying Person.
4.4 Each Party, due to system limitations, may purge or delete num-
bers of its customers from the lists as referred to in Section 4.2 hereof, but
in all such cases, such purging or deletion must be done in accordance
with the approved CIBERNET Negative File Guidelines. If purging or de-
letion of numbers is done prior to the time periods established by such
Guidelines, or through procedures not otherwise set forth, in the ap-
proved CIBERNET Negative File Guidelines, the Party implementing the
purge or deletion will assume financial liability for any charges incurred
by those numbers. All purges or deletions made pursuant to this Section
4.4 shall be given through the Parties and shall be in the form mutually
agreed upon by the Parties and effective as of the time established by the
approved CIBERNET Negative File Guidelines (unless otherwise modi-
fied by mutual agreement of the Parties.)
4.5 Upon the implementation of wireless number portability in any
portion of either Party’s system, the Pa rties shall cooperate in establishing
an alternative method for exchanging ESN, MIN, and NPA/NXX infor-
mation required to permit roaming by the other Party’s customers in their
respective systems.
ARTICLE V
FRAUD
___________________________________________
___________________________________________
___________________________________________
___________________________________________
If to [B]: Carrier [B]
___________________________________________
___________________________________________
___________________________________________
___________________________________________
Each Party may change the names, addresses and numbers set forth
above by providing notice to the other Party as provided in Article XIII
below.
ARTICLE VI
BILLING
6.1 Each Home Carrier shall be responsible for billing to, and collect-
ing from, its own customers all charges that are incurred by such custom-
ers as a result of service provided to them as Authorized Roamers by the
Serving Carrier. The Home Carrier shall also be responsible for billing its
customers for, and remitting to, the Federal Government or other appli-
cable governmental authorities all federal excise tax or other applicable
taxes that may be due in connection with the service being billed by it to
its customers. While the Serving Carrier will be responsible for the com-
putation and remittance of all state and local taxes, each Home Carrier
shall be liable to the Serving Carrier for all such state and local taxes re-
mitted by the Serving Carrier, for Authorized Roamers regardless of
whether these amounts are paid to the Home Carrier by its customers.
6.5 Each Home Carrier may at its discretion perform any necessary
edits at its Clearinghouse on incollect or outcollect call records to ensure
compliance with the terms of this Agreement.
ARTICLE VII
SETTLEMENT
7.1 Each Party will settle its accounts with the other Parties on the ba-
sis of billing information received as described in this Article VII. In the
event both Parties use a net financial settlement procedure, the Parties
shall not submit a paper invoice but will make payments in accordance
with such net financial settlement procedures provided that the Parties
may submit call records for payment that relate to calls made more than
sixty (60) days from the date of the call if such call was the subject of a
dispute or investigation regarding fraudulent or unauthorized use.
7.3.2 The Parties shall send each other an invoice for Services
used under this Agreement within fifteen (15) days after the Close
of Billing.
8. Total charges
7.3.5 Each Party may offset the amount owed to the other Party
under this Agreement and a single payment of the balance to the
Party entitled to receive such balance shall be made.
8.1 Each Party shall, as Serving Carrier, provide for automatic call de-
livery for customers of the other Party who are Roamers in the Serving
Carrier’s system. To this end, each Party shall continuously provide the
hardware, software and transmission facilities required for such call de-
livery either directly between the systems of the Parties or indirectly
through a separate network of communications carriers. The hardware,
10.1 A Party will be in “Default” under this Agreement upon the oc-
currence of any of the following events:
10.2 All claims and disputes relating in any way to the performance,
interpretation, validity, or breach of this Agreement, including but not
limited to a claim based on or arising from an alleged tort, shall be re-
solved as provided in this Section 10.2. It is the intent of the Parties that
any disagreements be resolved amicably to the greatest extent possible.
10.2.1 If a disagreement cannot be resolved by the representa-
tives of the Parties with day-to-day responsibility for this Agree-
ment, such matter shall be referred to an executive officer of each of
the Parties. The executive officers shall conduct face-to-face negotia-
tions at a neutral location or such other location as shall be mutually
agreed upon. If these representatives are unable to resolve the dis-
pute within fifteen (15) business days after either Party requests the
involvement of the executive officers, then either Party may, but is
not required to, refer the matter to arbitration, as applicable in ac-
cordance with Sections 10.2.2.
10.2.2 If any claim, controversy or dispute of any kind or nature
whatsoever arises between the Parties and cannot be resolved in ac-
cordance with 10.2.1 then the dispute shall be resolved by arbitra-
tion. A single neutral arbitrator engaged in the practice of law, who
is knowledgeable about the matter in Dispute, shall conduct the ar-
bitration under the then current rules of the American Arbitration
Association.
10.3 Each party shall bear its own costs and attorneys' fees, and the
parties shall share equally the fees and expenses of the arbitrator. The ar-
bitrator shall not have authority to award punitive damages. The arbitra-
tor's decision and award shall be final and binding, and the parties
hereby waive all means of recourse to the courts of any other country.
The judgment upon the award rendered by the arbitrator may be entered
in any court having jurisdiction thereof.
ing in the area in which the assignor previously was licensed to provide
Service.
11.2 No person other than a Party to this Agreement shall acquire any
rights hereunder as a third party beneficiary or otherwise by virtue of this
Agreement.
ARTICLE XII
NO PARTNERSHIP OR AGENCY RELATIONSHIP IS CREATED
_________________________________
_________________________________
with a copy to: Carrier [A]
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
with a copy to: Carrier [B]
_________________________________
_________________________________
_________________________________
_________________________________
or such other address as any Party may from time to time furnish to the
other Party by a notice given in accordance with the terms of this Section.
All such notices and communications shall be deemed to have been duly
given at the time delivered by hand, if personally delivered; ten business
days after being deposited in the mail, if mailed; subject to confirmation
of receipt, on the date of receipt if received by 3:00 p.m., local time, on
any business day and otherwise on the next business day, if by facsimile;
and the next business day, if sent by overnight air delivery service.
ARTICLE XIV
CONFIDENTIALITY
14.1 Each Party shall, and shall cause each of its Affiliates and each of
its and their employees, agents, and contractors, to keep confidential and
not use for any purpose, except as contemplated by this Agreement, any
and all information and know-how provided to it by the other Party
which is identified in writing as confidential (“Confidential Informa-
tion”). Identification of information as confidential shall, in the case of in-
formation delivered in tangible form, appear on at least the face or first
page of such information and, in the case of information communicated
verbally, be given verbally contemporaneously with the delivery of the
information and confirmed in writing within five business days thereaf-
ter. Notwithstanding the foregoing, the following information shall be
treated as Confidential Information without any further identification as
such: (i) The terms, but not including the mere existence, of this Agree-
ment; and (ii) all information exchanged pursuant to Article IV.
and shall provide any reasonable assistance requested by the other Party
to maintain the confidentiality of the information.
14.3 The Parties agree that a Party will not have an adequate remedy at
law in the event of a disclosure or threatened disclosure of Confidential
Information in violation of this Article XIV. Accordingly, in such event, in
addition to any other remedies available at law or in equity, a Party shall
be entitled to specific enforcement of this Article XIV and to other injunc-
tive and equitable remedies against such breach without the posting of
any bond.
14.4 The obligations under this Article XIV shall survive the termina-
tion of this Agreement for a period of three years.
ARTICLE XV
MISCELLANEOUS
15.1 The Parties agree to comply with, conform to, and abide by all ap-
plicable and valid laws, regulations, rules and orders of all governmental
agencies and authorities, and agree th at this Agreement is subject to such
laws, regulations, rules and orders. All references in this Agreement to
such laws, regulations, rules and orders include any successor provision.
If any amendment to or replacement of the same materially alters the
benefits, rights, and duties of the Parties hereunder, the Parties agree to
negotiate in good faith an amendment to this Agreement to restore the re-
spective positions of the Parties to substantially the same point as existed
prior to such amendment or replacement.
15.2 The Parties agree to use their respective best, diligent, and good
faith efforts to fulfill all of their obligations under this Agreement. The
Parties recognize, however, that to effectuate all the purposes of this
Agreement, it may be necessary either to enter into future agreements or
to amend this Agreement, or both. In that event, the Parties agree to nego-
tiate with each other in good faith.
15.4 The headings in this Agreement are inserted for convenience and
identification only and are not intended to describe, interpret, define or
limit the scope, extent or intent of this Agreement or any provision
thereof.
15.5 This Agreement may be executed in counterparts, each of which
shall be deemed an original, but all of which together shall constitute one
and the same Agreement.
15.6 This Agreement shall be construed in accordance with the laws of
the state of New York, United States of America.
15.7 Neither Party shall be liable to the other Party for any special, in-
direct, consequential or punitive damages.
15.8 The Parties agree that they will not use the name, service marks or
trademarks of the other party or any of its Affiliates in any advertising,
publicity releases or sales presentations, without such Party’s written con-
sent. Neither Party is licensed hereunder to conduct business under any
logo, trademark, service or trade name (or any derivative thereof) of the
other Party.
Name: __________________________Name:________________________
Title: Title: _________________________
SCHEDULE 1
Affiliates of Carrier [A]
SCHEDULE 2
Affiliates of Carrier [B]
EXHIBIT A
SERVICE CHARGES
Toll Rates:
EXHIBIT B
Technical Data
METHODS AND PROCEDURES
By:____ _ ____________________
Title:___ _____________________
Issue Date:___________________
The effective date shall be:
_______________________ _____
12 Notes