gsm prd ba.50 v5.0 technology neutral agreements handbook

GSM Association Confidential

ConfidentialOfficial Document BA.50

Technology Neutral Agreements Handbook

Version 5.0

10 May 2012

This is a Non Binding Permanent Reference Document of the GSMA

Security Classification: This document contains GSMA Confidential InformationAccess to and distribution of this document is restricted to the persons listed under the heading Security Classification Category. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those listed under Security Classification Category without the prior written approval of the Association. The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice.

Security Classification – CONFIDENTIAL GSMA Material Can be distributed to: Confidential GSMA Full MembersConfidential GSMA Associate MembersConfidential GSMA Rapporteur MembersConfidential GSMA Parent Company Members

Copyright NoticeCopyright © 2023 GSM Association

Antitrust NoticeThe information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.

V4.9 of 34

Table of Contents

Technology Neutral Agreements Handbook 1Version 5.0 110 May 2012 11 Introduction 32 Documents for establishment of International Roaming 3

2.1 Direct Roaming Agreements, current 32.2 Roaming Hub Agreement documents 32.3 Interworking services documents 42.3.1 Based on roaming agreements 42.4 Launch, modifications or termination letter templates 42.4.1 Launch letter templates 42.4.2 Template letters for modifications to the Agreement documents 42.4.3 Termination of a service or of the whole Agreement 52.5 Archived Roaming Agreement documents 5

3 Which Document to use? 54 Case by Case 6Annex 1 Commercial Launch Letter GSM 9Annex 2 Commercial Launch Letter CAMEL 10Annex 3 Pre-commercial Launch Letter GPRS 11Annex 4 Commercial Launch Letter GPRS 12Annex 5 Pre-commercial Launch Letter MMS Interworking 13Annex 6 Commercial Launch Letter MMS Interworking 14Annex 7 Commercial Launch Letter SMS Interworking 15Annex 8 Commercial Launch Letter 3G (new) 16Annex 9 Commercial Launch Letter 3G (extension of existing Roaming Agreement)

17Annex 10 Commercial Launch Letter Video Telephony 18Annex 11 Template for Party Replacement and / or amendments to Articles or

Annexes. 19INTERNATIONAL ROAMING AGREEMENT 19Annex 12 Launch Letter Network Extensions 22Annex 13 Confirmation of effective starting date for NRTRDE 23Annex 14 Template Letter for Confirmation of End of Service 24Annex 15 Template Letter for Notification of Exchange Rate Calculation Principle 25Annex 16 Commercial Launch Letter LTE (extension of existing Roaming Agreement)

26Annex 17 Template Letter for Confirmation of End of Agreement 27Annex 18 AA.13 C.7 text when HUR is used: 28Document Management 30

Document History 30Other Information 31



1 Introduction This Handbook has been developed in order to provide a clear guide to Members’ roaming experts on how to use the different documents related to the signature of an Agreement for International Roaming.

During the last years roaming has evolved as new technologies, like GPRS, 3G, LTE, or new features have appeared in the market. This has made the signature and maintenance of roaming partnerships more and more complicated for members of the GSM Association.

This process has led to the situation in which there are several versions of the roaming agreements in use by operators. Furthermore, operators may have signed up to a variety of different addenda e.g. the GPRS addendum or the SMS Interworking addendum for the launch of the different services.

At the end of 2002, it was decided that roaming agreements should be based on a technology neutral core agreement to avoid to sign new agreements whenever new technologies become available. In 2008 this handbook was updated with the option of setting up roaming services via a Roaming Hub..

2 Documents for establishment of International Roaming

Direct Roaming Agreements, current

AA.12 3.13.0 and later versions: Technology Neutral International Roaming Agreement

AA.13 3.10.0 and later versions: Technology Neutral International Roaming Agreement - Common Annexes.

Operators have been including Annexes to bilaterally signed AA.13 Common Annexes in order to confirm bilaterally agreed services. A clear example of such usage is for agreement and launch of a network extension. The diverse content and numbering of these Annexes causes confusion and standardised versions have been made available and should be used.

In case an operator wants to add an Annex to the AA13 Annexes they need to make sure that there is no gap in the numbering of the Annexes. For example, if an operator decides to add an Annex C.10, there needs to be an Annex 8 and 9 even if they are blank.

AA.14 3.13.0 and later versions: International Roaming Agreement -Individual Annexes

BA.19/BA.29 see the current applicable version at GSMA Infocentre: Individual Operator information in RAEX format

In order to automate the exchange of Individual Operator information, the standardized RAEX format was introduced. To facilitate the distribution of multiple Inter-Operator Tariffs (e.g. an individual IOT per roaming partner) the Individual Operator information was divided in BA.19 (standard information for all roaming partners) and BA.29 (possibility to include different IOT per roaming partner).

of 34



Roaming Hub Agreement documents

AA.73 Template Roaming Hub Agreement contains a template for the Roaming Hub Agreement between Roaming Hub Provider and a Client Operator.

AA.74 Template Roaming Hub-to-Hub Agreement contains a template Agreement for the connection between Roaming Hub Providers.

Interworking services documents

2.3.1 Based on roaming agreements

Interworking services can be launched based on the infrastructure established for roaming services and as such by using an addendum linked to the general conditions and procedures for International Roaming Services.

AA.19 Addendum to the International Roaming Agreement for SMS Interworking

AA.40 Addendum to the International Roaming Agreement: Multimedia Messaging Services Interworking.

2.3.2 Independent Interworking Services Agreements

AA.60 Template Agreement for Interworking Services. Each Service has its own Service Schedule template:

AA.61 Voice Messaging Service Schedule to AA.60

AA.62 Video Share Service Schedule to AA.60

AA.63 SMS Service Schedule to AA.60

AA.64 MMS Service Schedule to AA.60

AA.65 Instant Messaging Service Schedule to AA.60

2.4 Launch, modifications or termination letter templates

As help for the GSMA members, BARG have prepared the template letters for confirmation of launches of services, modifications to the agreements or termination of services or agreements. These templates are included as annexes at the end of this BA50.

2.4.1 Launch letter templates

Launch letters are used to confirm the successful finalization of tests (if required) and the agreed date for start of the service. Examples of usage would be:

Launch of CAMEL

Launch of Data Services (GPRS, 3G, LTE etc)

Launch of Interworking services

Confirmation of NRTRDE launch date

2.4.2 Template letters for modifications to the Agreement documents

In case there is a need to modify certain conditions or procedures of the Roaming Agreement and a written and signed confirmation of these changes is required at the same time that a clear link to the original signed documents should be assured, GSMA members may use the template created for this in this handbook. This template may be used for:

of 34



One of the signing Parties of the Agreement has been taken over by another party which will take over the responsibilities of the Agreement with the other signing Party.

A new Annex for confirmation of a new service has been added to the signed Agreement.

2.4.3 Termination of a service or of the whole Agreement

In case the signing parties of an Agreement agree to terminate a service or the overall Agreement, a written and signed confirmation will be required. Templates for these cases are included in this handbook and can be used for example when:

Termination of a network extension

Termination of the whole agreement due to insolvency of one of the Parties

Termination of the whole agreement due to migration of the roaming relation to a roaming hub

Termination of interworking services due to migration of the service to a hub.

Archived Roaming Agreement documents

The general recommendation is not to use the following documents, but to update the Roaming Agreement documents to the latest available versions.

AA.31 3.1.2: Addendum to the International Roaming Agreement (GPRS and/or 3GSM Roaming Addendum): the introduction of this service is covered by the technology neutral AA12 and AA13.

AA.43 WLAN, this Addendum was created to launch WLAN services based on the general conditions of the International Roaming Agreement. The experience learned that the usage has been very limited and that the feature of WIFI roaming services have changed over time, so that the addendum became obsolete.

AA13 C.7 Fraud Prevention HUR / AA73 Fraud Prevention HUR

As per 1 October 2008 all GSMA members should use Near Real Time Roaming Data Exchange (NRTRDE) for combating fraud, though not all operators have complied with this rule. In 2012 all references to HUR have been deleted of the latest versions of the corresponding GSMA PRDs, but operators who are forced to refer to the HUR obligations and procedures can prepare a corresponding annex (AA.13 C.7) based on the text included in the respective annex of this handbook.

3 Which Document to use?In general, operators should always use the latest available templates available at the GSMA Infocentre when signing a new roaming agreement. Furthermore, the momentum of the introduction of a new technology or service (e.g. 3G, NRTRDE) may be used for updating the agreement documents to these latest technology neutral versions. The point of the new roaming agreement is to make the introduction of new services easier and to avoid addenda like the GPRS addendum or the 3GSM addendum (both of which were necessary where operators had signed a roaming agreement that catered only for 2G).

of 34



Some services such as SMS or MMS will need additional rules and regulations over and above those that are set out in the roaming agreement. For this reason, use of an addendum may still be necessary.

In case the operator decides to set up International Roaming Services via a roaming hub, the AA.73 contains a template which can be used as the basis for the Agreement with the Roaming Hub Provider. This template consists as well of a general body and Annexes.

It is important to note that the GSMA will only be updating and maintaining the latest version of the roaming agreement (now being the technology neutral agreement). As always, any changes in PRDs related to the core agreement (such as BA27) will apply to all versions of the agreements as the reference to these PRDs stays the same.

In case the Parties agree that some addenda to the International Roaming Agreement remain valid but now attached to the new versions of this IRA, they may include the following wording in AA.12 I. Introduction:

This bilateral agreement replaces the previous International Roaming Agreement initially signed on xx / xx / xx by and between <Party A> and < Party B>. The addenda AA.XX duly signed on xx / xx / xx and AA.XX duly signed on xx / xx / xx will continue as addenda to this new version of the International Roaming Agreement.

4 Case by Case The following section describes the different situations in which a change of roaming related agreement documents is required.

a) If you have a version of AA.12 including GPRS and 3GSM

A.1 And you are not implementing any new services: don’t change anything

A.2 And want to introduce SMS Interworking: What was done before: Sign AA.19Recommended: sign the latest version of the AA.60 and the AA.63 which contains the Service Schedule for SMS Interworking, or the technology neutral AA12 and AA13 + latest version of technology neutral AA.19.

A.3 And want to introduce MMS Interworking,What was done before: Sign AA.40Recommended: sign the latest version of the AA.60 and the AA.64 which contains the Service Schedule for MMS Interworking, or the technology neutral AA12 and AA13 + latest version of technology neutral AA.40.

A.4 And want to introduce LCS Interworking, WLAN or any other new serviceRecommended: sign the latest version of the technology neutral AA12 and AA13 + relevant addendum

b) If you have an older version of AA12 not including GPRS and 3 GSM

B.1 And you are not implementing any new services: don’t change anything

B.2 And you want to introduce GPRS or 3GSM:

of 34



What was done before: sign AA31Recommended: sign the latest version of the technology neutral AA12 and AA13

B.3 And you want to introduce SMS InterworkingWhat was done before: sign AA19 Recommended: sign the latest version of the AA.60 and the AA.63 which contains the Service Schedule for SMS Interworking, or the technology neutral AA12 and AA13 + latest version of technology neutral AA.19.

B.4 And want to introduce MMS Interworking What was done before: sign AA40 Recommended: sign the latest version of the AA.60 and the AA.64 which contains the Service Schedule for MMS Interworking, or the technology neutral AA12 and AA13 + latest version of technology neutral AA.40.

B.5 And want to introduce LCS Interworking, WLAN or any other new serviceRecommended: sign the latest version of the technology neutral AA12 and AA13 + relevant addendum

c) If you have any version of AA12 and for example SMS Interworking and want to introduce another service:

Recommended: replace the agreement you have with the latest versions of technology neutral AA12 and AA13 + the relevant Addendum

d) If you start a new roaming relationship

Recommended: sign the latest versions of technology neutral AA12 and AA13 and add adapted SMS IW, MMS IW, or new WLAN or LCS IW agreements.

e) If you have no roaming agreement signed yet but would like to launch SMS Interworking

Recommended: sign the latest version of the AA.60 and the AA.63 which contains the Service Schedule for SMS Interworking.

f) If you have no roaming agreement signed yet but would like to launch MMS Interworking

Recommended: sign the latest version of the AA.60 and the AA.64 which contains the Service Schedule for MMS Interworking.

g) If you have a signed roaming agreement and you assign the rights and obligations to another Party, or if you decide to replace existing Articles or Annexes and/or add new Annexes, you may use the template included in Annex 11 to keep a clear link to the originally signed documents.

h) If you enter into a Network Extension roaming relationship with a Host Operator in order to roam on the network of a Client Operator you should sign the latest version of the AA.13 C.11 Addendum and choose whether to sign a Network Extension Launch Letter (see BA.21 for more information).

i) NRTRDE InformationFor new Roaming Agreements or migration from HUR to NRTRDE after 1st October 2008:

of 34



To move from HUR to NRTRDE as stated within BA.20 Fraud Prevention Procedures, Operators should update Annex C7 of AA.13 version 3.14 or later. The update must be scheduled to coincide with the launch of NRTRDE,Operators who wish to confirm the launch date in writing could use the NRTRDE Launch Letter tabled as Annex 13 to this PRD BA.50.If you have already updated Annex C.7 of AA.13 to version 3.14 or later and are now unable to launch you must immediately inform your roaming partners and should confirm a later launch date in writing. You can do this by either amending Annex C7 of AA.13 or using the NRTRDE Launch Letter tabled as Annex 13 to this PRD BA.50.Please note to inform your roaming partner of your NRTRDE Agent, using AA.14/BA.19, I.7.2 and I.8.1.

j) If you need to confirm the end of a specific service with a roaming partner (e.g. network extension in a certain country) you may use the template letter for End of Service included Annex 14 of this PRD BA.50.

k) If you wish to start using a fixed exchange rate or stop using a fixed exchange rate please use Notification of a Fixed Exchange Rate Letter included in Annex 15 of this PRD BA.50.

l) In case one of the Parties of an Agreement document has to include text of the Agreement in another language than English the receiving Party may decide to include the following sentence before or at the pages where the non-English text is included: “In case differences are found between the original English text and the translated text as included here, the English text shall prevail”.

of 34



Annex 1 Commercial Launch Letter GSMDATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR GSM ROAMING AGREEMENT

This is to confirm that on the [DATE],

[PARTNER A] [PLMN A],

and

[PARTNER B] [PLMN B]

agree to launch GSM roaming on a [unilateral] / [bilateral] basis. The launch follows the successful completion of the applicable IREG and TADIG tests.

[This is a unilateral launch for the customers of [PARTNER A] as HPMN roaming on the network of [PARTNER B] as VPMN]

The commercial service is in accordance with the conditions set out in the International Roaming Agreement as signed by both Parties on [DATE].

Date: Date:

Place: Place:

........................................................... ...........................................................

For and on behalf of [PARTNER A] For and on behalf of [PARTNER B]

V4.9 of 34



Annex 2 Commercial Launch Letter CAMELDATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR CAMEL BASED ROAMING



and


agree to launch CAMEL based roaming on a [unilateral] / [bilateral] basis. The launch follows the successful completion of the applicable IREG and TADIG tests.


The commercial service is in accordance with the conditions set out in the

International Roaming Agreement as signed by both Parties on [DATE].

[Party A will charge Party B according to the CAMEL destination number (as

applicable)].

In the event that further service specific tests are required these shall be bilaterally agreed and executed in both the VPMN and the HPMN as necessary.

Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



Annex 3 Pre-commercial Launch Letter GPRS

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR PRE-COMMERCIAL GPRS ROAMING AGREEMENT



and


agree to launch pre-commercial GPRS roaming on a [unilateral] / [bilateral] basis. The Parties agree that until otherwise advised by one or both Parties, no GPRS charging data will be exchanged and that the Parties will not pay each other for the GPRS roaming traffic generated by their respective customers roaming on the other Party’s network.


Both Parties agree to make best endeavours to launch a commercial GPRS service as soon as possible. Once one or both Parties will be capable of producing GSMA standards compliant TAP files containing GPRS charging data and after the successful performance of the relevant TADIG tests, a new commercial letter will be signed and the charging of GPRS Roaming between the Parties will start from the date contained therein.

[The routing solution chosen by the Parties to enable GPRS Roaming is the HPMN Roaming Solution as defined in PRD IR34]

Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



V4.9 of 34



Annex 4 Commercial Launch Letter GPRS

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR GPRS ROAMING AGREEMENT



and


agree to launch GPRS roaming on a [unilateral] / [bilateral] basis after successful IREG and TADIG testing.



[The routing solution chosen by the Parties to enable GPRS Roaming is the HPMN Roaming Solution as defined in PRD IR34.]

Date: Date:

Place: Place:

........................................................... ...........................................................

V4.9 of 34




Annex 5 Pre-commercial Launch Letter MMS Interworking

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR PRE-COMMERCIAL MMS INTERWORKING AGREEMENT



and


agree to launch pre-commercial MMS interworking on a bilateral basis. The Parties agree that for the time being and until otherwise advised by one or both Parties, no MMS bulk data will be exchanged and that the Parties will not pay each other for the MMS interworking traffic generated by their respective customers sending MMS destined for the other party’s MMS Server/Relay.

Both Parties agree to make best endeavours to launch a commercial MMS interworking service as soon as possible. Once one or both Parties will be capable of producing bulk data compliant with the MMS Interworking Addendum and to the satisfaction of both Parties, a new commercial letter will be signed and the charging of MMS Interworking between the Parties will start from the date contained therein.

Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



Annex 6 Commercial Launch Letter MMS Interworking

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR MMS INTERWORKING AGREEMENT



and


agree to launch MMS interworking on a bilateral basis.

The commercial service is in accordance with the conditions set out in the International Roaming Agreement and MMS Addendum as signed by both Parties on [DATE].

Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



Annex 7 Commercial Launch Letter SMS Interworking

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR SMS INTERWORKING AGREEMENT



and


agree to launch SMS interworking on a bilateral basis.

The commercial service is in accordance with the conditions set out in the International Roaming Agreement and SMS Addendum as signed by both Parties on [DATE].

Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



Annex 8 Commercial Launch Letter 3G (new)DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR 3GSM ROAMING AGREEMENT



and


agree to launch 3GSM roaming on a [unilateral] / [bilateral] basis. The launch follows the successful completion of the applicable IREG and TADIG tests.


[Partner A] shall open its UTRAN to Customers of [Partner B] using [SIMs/USIMs only] / [SIMs and USIMs]

[Partner B] shall open its UTRAN to Customers of [Partner A] using [SIMs/USIMs only] / [SIMs and USIMs]

The commercial service is in accordance with the conditions set out in the International Roaming Agreement and/or AA.31 as modified and signed by both Parties.

Date: Date:

Place: Place:

............................ ............................

For and on behalf of For and on behalf of

V4.9 of 34



[PARTNER A] [PARTNER B]

Annex 9 Commercial Launch Letter 3G (extension of existing Roaming Agreement)

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR 3GSM ROAMING AGREEMENT



and


agree to extend the commercial roaming service to 3G roaming on a [unilateral] / [bilateral] basis. The launch follows the successful completion of the applicable IREG and TADIG tests.


[Partner A] shall open its UTRAN to Customers of [Partner B] using [SIMs/USIMs only] / [SIMs and USIMs]

[Partner B] shall open its UTRAN to Customers of [Partner A] using [SIMs/USIMs only] / [SIMs and USIMs]

The commercial service is in accordance with the conditions set out in the International Roaming Agreement and/or AA.31 as modified and signed by both Parties.

Date: Date:

Place: Place:

............................ ............................


V4.9 of 34




V4.9 of 34



Annex 10 Commercial Launch Letter Video Telephony

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR VIDEO TELEPHONY (Synchronous Circuit Switched 64kb p/s), COVERED BY THE 3G ROAMING AGREEMENT



and


agree to extend the commercial 3G roaming service with the video telephony service on a [unilateral] / [bilateral] basis, after successful specific testing and subsequent agreement on the launch date.



Date: Date:

Place: Place:

........................................................... ...........................................................


V4.9 of 34



Annex 11 Template for Party Replacement and / or amendments to Articles or Annexes.

Addendum to the

INTERNATIONAL ROAMING AGREEMENT

Between

<Operator A>

[as legal successor to (------),(in the event of sale or merger)

formerly known as (------)as applicable]

having its registered address:

…………………………………………………

(hereinafter referred to as "<Party A>")

and

<Operator B>,


formerly known as (------)as applicable]


……………………………………………….

(hereinafter referred to as "<Party B>")

And

<Operator C> [This Operator replaces <Party B>],


formerly known as (------) (as applicable]


……………………………………………….

(hereinafter referred to as "<Party C>")

V4.9 of 34



Pursuant to Article 18.1 of the General Terms and Conditions for International Roaming, the following amendments in this Addendum are made to the International Roaming Agreement signed by and between <Party A> on month, DD, YYYY and <Party B> on month, DD, YYYY (“IR Agreement”):

Now therefore the Parties agree as follows:

1. [In the case of Party Replacement]

1.1 <Party B> hereby assigns and transfer to <Party C> all rights and obligations under the IR Agreement.

1.2 The assignment contemplated hereby is effective as of the Effective Date (as such term is defined below) when the rights and obligations of <Party B> under the IR Agreement will terminate.

1.3 As and from the Effective Date, <Party C> will be fully liable and responsible for all obligations of <Party B> under the IR Agreement, including but not limited to, any and all arising in connection with events prior to the Effective Date as if <Party C> was a party to the IR agreement from the date the IR Agreement was signed.

1.4 <Party A> agrees that <Party B> transfers and <Party C> accepts all rights and obligations of <Party B> under the IR Agreement.

2. [In the case of replacing an Article of the AA.12]

Article X of the IR Agreement is hereby replaced by the following new Article:

“Insert new text / pages”

3. [In the case of inserting a new Annex to the AA.13]

The following Annex C.XX is hereby included in AA.13 of the IR Agreement and as of the Effective Date becomes an integral part of the IR Agreement.

“Insert text / pages”

4. [In the case of replacing an Annex of the AA.13]

Annex C.XX of the IR Agreement is hereby replaced and superseded by the following new Annex C.XX.

“Insert new text / pages”

5. All other terms and conditions of the IR Agreement remain unchanged and in full force and effect.

6. This Addendum shall come into force from

V4.9 of 34



[either] on month, DD, YYYY. (“Effective Date”)

[or] as of the date of last signature of this Addendum. (“Effective Date”).

For: <Party A> For: <Party B>

<Signing Authority Signature Party A><Signing Authority Signature Party B>

Signing Authority (print Name) Signing Authority (print Name)Date

Date

For: <Party C>

<Signing Authority Signature Party C>

Signing Authority (print Name)

Date

V4.9 of 34



Annex 12 Launch Letter Network ExtensionsCONFIRMATION OF EFFECTIVE STARTING DATE FOR UNILATERAL ROAMING – INVOLVING

A NETWORK EXTENSION(S)

Between:

Party A

Acting as Host Operator <TADIG Code/s> for <Client Operator name(s)> <TADIG Code/s>


(hereinafter referred to as "Host Operator")

and

Party B

Acting as HPMN Operator <TADIG Code/s>


(hereinafter referred to as "HPMN Operator")

This letter is to confirm that on the <DATE> the <Host Operator> and the <HPMN Operator> (hereinafter collectively referred to as the “Parties”) agree that the <Client Operator(s)> will open the Client Operator(s) Public Mobile Network(s) to the Customers of the HPMN Operator for the specific services indicated below (for example, Voice, GPRS, CAMEL etc) in order to make inbound roaming service available on a commercial basis to the Customers of <HPMN Operator> on the Public Mobile Network(s) of <Client Operator(s)> according to the conditions set out in the International Roaming Agreement and AA.13 COMMON ANNEX C.11 signed by the Parties.

For Host Operator For HPMN Operator

____________________ ___________________________

Signatory Signatory

Date:……………………. Date:…………………………….

V4.9 of 34



Annex 13 Confirmation of effective starting date for NRTRDE This is to confirm that on the [DATE],


and


agree to commence the NRTRDE process as stated in BA.20.

]

Date: Date:

Place: Place:

............................ ............................



V4.9 of 34



Annex 14 Template Letter for Confirmation of End of ServiceCONFIRMATION OF TERMINATION OF SERVICE XXXXXX



Having its registered address:

(Hereinafter referred to as “Party A”)

and



(Hereinafter referred to as “Party B”)

agree to end the availability of xx service for Roaming Customers on a [unilateral] / [bilateral] basis.

For Customers of PARTY A on the network of PARTY B.

For Customers of PARTY B on the network of PARTY A.

All other Services will be continued in accordance with the conditions set out in the International Roaming Agreement as signed by both Parties on [DATE].

Date: Date:

Place: Place:

........................................................... ...........................................................

For and on behalf of [PARTY A] For and on behalf of [PARTY B]

V4.9 of 34



Position Position

Annex 15 Template Letter for Notification of Exchange Rate Calculation Principle

NOTIFICATION OF EXCHANGE RATE CALCULATION PRINCIPLE

This is to confirm that on the 1st of [Month, Year],

[PMN A], Having its registered address:


Will start/stop use of XX.XXXX Fixed Exchange Rate to convert [currency] to [currency].

All other terms and conditions of the IR Agreement remain unchanged and in full force and effect.

Date:

Place: ........................................................... For and on behalf of Party A

Position

V4.9 of 34



Annex 16 Commercial Launch Letter LTE (extension of existing Roaming Agreement)

DATE

CONFIRMATION OF EFFECTIVE STARTING DATE FOR LTE ROAMING AGREEMENT



and


agree to extend the commercial roaming service to LTE roaming on a [unilateral] / [bilateral] basis. The launch follows the successful completion of the applicable IREG and TADIG tests.


[Partner A] shall support over its LTE network the following services for Customers of [Partner B] (Delete what is not available):

LTE as such (i.e. as radio / bearer technology)

VoLTE based Voice i.e. Voice over LTE implemented in line with the GSMA defined VoLTE architecture

VoLTE based SMS i.e. SMS over LTE implemented in line with the GSMA defined VoLTE architecture

[Partner B] shall support over its LTE network the following services for Customers of [Partner A] (Delete what is not available):

LTE as such (i.e. as radio / bearer technology)

VoLTE based Voice i.e. Voice over LTE implemented in line with the GSMA defined VoLTE architecture

VoLTE based SMS i.e. SMS over LTE implemented in line with the GSMA defined VoLTE architecture

The commercial service is in accordance with the conditions set out in the International Roaming Agreement as signed by both Parties.

Date: Date:

Place: Place:

............................ ............................



V4.9 of 34



Annex 17 Template Letter for Confirmation of End of AgreementCONFIRMATION OF TERMINATION OF AGREEMENT




and



(Hereinafter referred to as “Party B”)

Through this letter and taking into account the correspondent articles of the [International Roaming / Roaming Hubbing] Agreement, both Parties agree to terminate this Agreement as per the following effective date:

All Services based on this Agreement will be finalized by this date, while all other (payment, confidentiality) obligations will be terminated as stipulated in the Agreement.

Date: Date:

Place: Place:

........................................................... ...........................................................

For and on behalf of [PARTY A] For and on behalf of [PARTY B]

Position Position

V4.9 of 34



Annex 18 AA.13 C.7 text when HUR is used:1. General

The Parties shall implement fraud prevention procedures as specified by the GSM Association from time to time.

The VPMN Operator shall inform the HPMN Operator - according to the procedure further detailed below - if fraudulent use of the VPMN Operator's Services is suspected or detected. The HPMN Operator shall define the criteria for suspected fraud in relation to Circuit Switched (CS) Services, Packet Switched (PS) Services and Content Transactions. However, both Parties shall agree on possible restrictions within the VPMN Operator's specific implementation of fraud prevention procedures. The HPMN Operator's criteria for suspected fraud are defined in Annex I.7.1.

1.1 Fraud prevention procedure

The Parties agree to implement to the following fraud prevention procedure:

The VPMN Operator shall analyse all data related to CS Services, PS Services and Content Transactions from Roaming Subscribers every day. All IMSIs of Roaming Subscribers who meet the HPMN Operator's criteria for suspected fraud shall be identified. The VPMN Operator will compile the corresponding records and send a Report on Suspected Fraud by email to the HPMN Operator within 36 hours from the time of completion of the event which caused the SDR Threshold to be exceeded.

Email shall be the standard method of transmission unless agreed to otherwise by the two Parties, but in the event that email transmission is not possible the VPMN Operator shall be permitted to send the Report on Suspected Fraud by fax on an exceptional basis. For the avoidance of doubt, exceptional circumstances arise when either:

Access to email transmission by the VPMN is not possible.

The VPMN receives an indication (e.g. - delivery failure notification) that email delivery of the Report on Suspected Fraud to the HPMN was unsuccessful.

In these circumstances, the faxing of a Report on Suspected Fraud is permitted to ensure the HPMN receives the data within the agreed 36 hour period. The use of fax shall be strictly limited to the period during which email transmission is not possible and the VPMN shall revert to the use of email at the earliest possible opportunity. The VPMN will add a note to the fax informing the HPMN about the email transmission problem.

The VPMN will employ email delivery tracking functionality for email transmission of each Report on Suspected Fraud. Delivery notification logs and original emails shall be retained for 60 days to support analysis and processing of repudiation claims by the HPMN. Where a

V4.9 of 34



Report on Suspected Fraud is sent by fax, fax delivery confirmation shall similarly be retained for 60 days to support analysis and processing of repudiation claims by the HPMN.

Operators are advised to check if their own legislation authorises the transmission of emails for the purpose of serving as evidence in legal proceedings. If this is not the case, operators can bilaterally agree that the method of transmitting emails does provide sufficient evidence in legal proceedings.

The analysis may be based on partial call records. The Inter Operator Contact Point for combating fraudulent usage is defined in Annex I.7.1. Each Party will ensure that there is, at least during office hours, one English speaking person on duty.

1.2 Report on Suspected Fraud:

The Report on Suspected Fraud for call related data related to CS and PS Services and Content Transactions from Roaming Subscribers is a summary on suspected or detected fraudulent use of the VPMN Operator's Services. The implementation of the Report on Suspected Fraud, in terms of format and contents, shall be in accordance with FF.04 unless otherwise agreed between the Parties.

The report shall be produced in the standard format for each Roaming Subscriber who meets the HPMN Operator's criteria for suspected fraud.

Both Parties recognise that the information to be exchanged may be limited by the Data Protection regulations that are further detailed in Annex I.6.1.

In the event that one Party has a query concerning fraud, then the other Parties Inter Operator Contact Point for combating fraudulent use should be contacted.

Both Parties shall make their best efforts to implement interchange of TAP records via Electronic Data Transfer on a daily basis as early as possible.

1.3 Liability for non-compliance of Fraud Prevention Procedure

If the VPMN Operator does not send the Report on Suspected Fraud within the time scale defined in Article 1.1, the HPMN Operator is not obliged to pay any fraudulent CS, PS or Content Transaction made during the time period between the established dead-line and the date of receipt of the Report on Suspected Fraud for any IMSI that should have been detected and reported to the HPMN Operator by the VPMN Operator in the Report on Suspected Fraud according to Article 1.1. In every case this time period is limited to 30 days after the established dead-line.

Any claims made as a result of the late sending of Reports on Suspected Fraud shall be made in accordance with the provisions set out in BA.08.

V4.9 of 34



V4.9 of 34



Document Management

Document History

Version Date Brief Description of Change Approval Authority

Editor / Company

3.0.0 December 2003

New Non-Binding PRD

3.1.0 March 2004

As approved at BARG #63 Addition of launch letters (BARG Docs 63_070 to 63_076), and updated with CR 001 (BARG Doc 63_063) clarification use of AA13 annexes after C8, clarification versions AA12

3.1.1 April 2004 Addition of Launch Letters for 3G (BARG Docs 64_014 & 64_015)

3.2 February 2005

As approved at BARG #64 CR 004 to BA.50 (BARG Doc 65_049Rev1) Addition of Launch Letter for Video Telephony and AA12 reference clause to older version CR 005 to BA.50 (BARG Doc 65_053)

This document now conforms to AA.34 for use of 2-digit version control.

3.3 March 2006

As approved at BARG # 67 references to AA.27, AA.28 & AA.29 are deleted, since the TNA can be used for these agreements also. Editorial change: no references to specific versions of TNA

4.0 June 2006As approved by AGREE CR 003 introduces the procedure for SMS/MMS Interworking prior to Roaming (AGREE Doc 31_004)

4.1 March 2007Inclusion of template for adding new articles or amending annexes of the STIRA

4.2 September 2007 Change to template for adding new

articles or amending annexes in order to include to possible usage for Party Replacement. Addition of Launch Letter for Network Extensions CR's 006 & 007 (BARG Docs 70_038 & BARG Doc 70_040)

4.3 March 2008Addition of Launch Letter Annex 13 for the confirmation of early introduction of NRTRDE (BARG 71_029Rev1), clarification of standardized usage Annexes of AA.13 and addition of

V4.9 of 34



possibility of usage of AA.60 for SMS IW (BARG 71_030)

4.4 September 2008 To include a template letter for

confirmation of the end of a specific service (section Case by Case (Q) and Annex 14). Update to support operators who are now unable to meet the NRTRDE mandatory date 1 October 2008

4.5 October 2008 CR 012 to BA.50 To update the

section (P) on NRTRDE as 1 October 2008 passed (BARG Doc 72_059Rev1). CR 011 to BA.50 To change “subscriber” into “Customer” (BARG Doc 72_031)

BARG #72Marjolein Medendorp (Telefonica)

4.6 March 2009mCR 013 to BA.50 Review & Update (BARG Doc 73_069Rev1)

BARG #73Marjolein Medendorp (Telefonica)

4.7 October 2009 mCR 014 to BA.50 Fixed Exchange

Rate notification (BARG Doc 74_041Rev1) and editors correction to name of Annex 11

BARG #74Marjolein Medendorp (Telefónica)

4.8 March 2010mCR 015 to BA.50 Different languages in STIRA (BARG Doc 75_041)

BARG #75Marjolein Medendorp (Telefónica)

4.9 10 November 2011

mCR 016 to BA.50 Commercial Launch Letter for LTE (BARG Doc 78_030)

AGREEMarjolein Medendorp (Telefónica)

5.0 10 May 2012 MCR 014 Complete editorial review,

addition Annex 17 Letter for Termination of an Agreement, Annex 18 AA13 Annex C7 text in case HUR is used (BARG Doc 79_027)

BARG#79 & EMC #102

Marjolein Medendorp (Telefónica)

Other Information

Type DescriptionDocument Owner BARG - AGREEEditor / Company Marjolein Medendorp (Telefonica)

It is our intention to provide a quality product for your use. If you find any errors or omissions, please contact us with your comments. You may notify us at [email protected] Your comments or suggestions & questions are always welcome.

V4.9 of 34

mailto:[email protected]