GSM Association Non-confidential

Official Document TD.107 - Single IMSI Provisioning Interface

Single IMSI Provisioning Interface

Version 1.0
27 November 2013

This is a Binding Permanent Reference Document of the GSMA

Security Classification: Non-confidential

Access to and distribution of this document is restricted to the persons permitted by the security classification. 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 permitted
under the security classification without the prior written approval of the Association.

Copyright Notice
Copyright © 2013 GSM Association

Disclaimer
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.

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

V1.0 Page 1 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Table of Contents
1 Introduction 4
1.1 Overview 4
1.2 Scope 4
1.3 Definitions 4
1.4 Abbreviations 4
1.5 References 4
1.6 Conventions 5
2 Assumptions 5
3 Processes with interaction between DSP and ARP 5
3.1 Single IMSI 5
3.1.1 Relationship between DSP and ARP 5
3.1.2 Service Activation by the Customer 5
3.1.3 Customer Service query responsibilities 8
3.1.4 Customer is issued a bill 8
3.1.5 Customer Changes Signalling Status (Customer Changes Billing Basis) 9
3.1.6 Bill-shock measures 10
3.1.7 Fraud Management and Prevention 10
3.1.8 Service DeActivation initiated by the Customer 13
3.1.9 Service DeActivation initiated by the ARP 14
3.1.10 Service DeActivation initiated by the DSP 15
3.1.11 Suspension and Termination of contract between DSP and ARP 15
4 Operation Description 16
4.1 Single IMSI 16
4.1.1 AcK 16
4.1.2 PreProvisioningRequest 16
4.1.3 PreProvisioningRequestAcknowledgement 17
4.1.4 ProvisioningRequest 17
4.1.5 ProvisioningCompletion 18
4.1.6 PreProvisioningCompletion 19
4.1.7 ReProvisioningRequest 20
4.1.8 ReProvisioningCompletion 20
4.1.9 ReProvisioningNotification 21
4.1.10 ReProvisioningAcknowledgement 22
4.1.11 SuspendRoaming 23
4.1.12 RoamingSuspended 23
4.1.13 UnSuspendRoaming 24
4.1.14 RoamingUnSuspended 25
4.1.15 DeProvisioningRequest 25
4.1.16 DeProvisioningAckowledgement 26
4.1.17 DeProvisioningCompletion 27
5 Parameters Definitions 29
6 Testing Procedure 48

V1.0 Page 2 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

7 Release Management 48
8 Security 48
Document Management 49
Document History 49
Other Information 49

V1.0 Page 3 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

1 Introduction

1.1 Overview
This document defines the requirements for the Single IMSI Provisioning Interface (SI-IF7)
between the DSP and ARP.

1.2 Scope
The scope of the document is to define the requirements for the OMA API definitions.

1.3 Definitions
Term Description
All call events defined for the applicable format (for example TAP,
Calls
NRTRDE)

1.4 Abbreviations
Term Description
API Application Protocol Interface
ARP Alternative Roaming Provider
CRM Client Relationship Management
DSP Domestic Service Provider
ICCID Integrated Circuit Card Identifier
IMSI International Mobile Subscriber Identity
LBO Local BreakOut
MNP Mobile Number Portability
MSISDN Mobile Station International Subscriber Directory Number
REST REpresentational State Transfer
SOAP Simple Object Access Protocol
UICC Universal Integrated Circuit Card

1.5 References
Ref Doc Number Title
Regulation (EU) No 531/2012 of the European Parliament and the Council
[1] 531/2012 of 13 June 2012 on roaming on public mobile communications networks
within the Union

Regulations, Commission Implementing Regulation (EU) No 1203/2012 of

[2] 1203/2012 14 December 2012 on the separate sale of regulated roaming services
within the Union
ROAMING REGULATION - CHOICE OF DECOUPLING METHOD: A
[3] BoR (12) 68 consultation to assist BEREC in preparing advice to the Commission on its
forthcoming Implementing Act, June 2012, 72 pages.
ROAMING REGULATION - CHOICE OF DECOUPLING METHOD, BEREC
[4] BoR (12) 109
opinion on article 5 implementing act, 27 Sept 2012, 7 pages

V1.0 Page 4 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Ref Doc Number Title

[5] High Level Technical specifications. V1.0
[6] Processes v1.0
“Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner,
[7] RFC 2119
March 1997. Available at http://www.ietf.org/rfc/rfc2119.txt

1.6 Conventions
The key words “must”, “must not”, “required”, “shall”, “shall not”, “should”, “should not”,
“recommended”, “may”, and “optional” in this document are to be interpreted as described in
RFC 2119 [7].

2 Assumptions
It is possible that an individual subscriber may hold a roaming contract with more than one
ARP for Single IMSI service at any one time. However, a subscriber can only have one
active ARP subscription at any time.

It is possible that an ARP would like to activate more than one subscription at a time. It is
assumed that the ARP will send one activation request for each subscription separately.

In case of a batch activation request, it is possible that the DSP is not able to activate all of
them within 1 working day. A maximum number of requests that can be activated within the
standard timescale will be defined.

All messages are acknowledged with an implicit synchronous acknowledgement message.

This message is not shown in diagrams but is described in 4.1.1.

IF7 APIs can be implemented using either the REST or SOAP protocols. The choice of the
one that will be used to connect a DSP with an ARP is a DSP option.
This means the ARP may have to implement both protocols in order to be able to connect to
two or more DSPs (if they are not using the same option).

Red arrows on the following diagrams indicate the interactions that are in scope of this
specification. Black arrows are out of the scope of SI-IF7.

3 Processes with interaction between DSP and ARP

For a detailed process description refer to [6][5].

3.1 Single IMSI

3.1.1 Relationship between DSP and ARP

This process is out of scope of this document because it doesn’t require interactions
between DSP and ARP.

3.1.2 Service Activation by the Customer

The Activation Process could include a verification phase performed by DSP in order to
understand whether the customer is eligible or not for an ARP Subscription. This verification
is out of the scope of this document and can be different from one country to another,
depending on local regulation enforcement.

V1.0 Page 5 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Scenario 1 - Activation: Activation with swap between two ARPs

This process applies when a customer requires an ARP subscription having another one
active and the Donor ARP can’t stop the process

Figure 1: Activation: Activation with swap between two ARPs

Scenario 2 - Change from Domestic Service Provider to Alternative Roaming Provider

V1.0 Page 6 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

This process applies when a customer requires an ARP subscription without having another
one active.

Figure 2: Change from Domestic Service Provider to Alternative Roaming Provider

Scenario 3 - Activation: Change from Alternative Roaming Provider to Domestic Service

Provider
This process applies when a customer wants to migrate back from an ARP subscription to a
DSP offer.

V1.0 Page 7 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

This scenario is equivalent to a De-Activation.

Figure 3: Activation: Change from Alternative Roaming Provider to Domestic Service

Provider

3.1.3 Customer Service query responsibilities

This process is out of scope of the document because it doesn’t require interactions
between DSP and ARP.

3.1.4 Customer is issued a bill

This process is out of scope of this document because it doesn’t require interactions
between DSP and ARP.

V1.0 Page 8 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

3.1.5 Customer Changes Signalling Status (Customer Changes Billing

Basis)
Scenario 1 – Change of Subscriber Contract at the ARP.

This process applies when an ARP customer wants to change its charge method
(prepaid/postpaid).

Figure 4: Change of Subscriber Contract at the ARP

Scenario 2 – Change of Billing Interface used for a subscriber from DSP to ARP
This process applies when DSP changes the billing interface for an ARP customer.

V1.0 Page 9 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Figure 5: Change of Billing Interface used for a subscriber from DSP to ARP

3.1.6 Bill-shock measures

This process is out of scope of this document because it doesn’t require interactions
between DSP and ARP.

3.1.7 Fraud Management and Prevention

Scenario 1 – Process Flow with NRTRDE

V1.0 Page 10 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Figure 6: Process Flow with NRTRDE

Scenario 2 – Process Flow with OnLine Interface

V1.0 Page 11 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Figure 7: Process Flow with OnLine Interface

V1.0 Page 12 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

3.1.8 Service DeActivation initiated by the Customer

Figure 8: Service DeActivation initiated by the Customer

V1.0 Page 13 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

3.1.9 Service DeActivation initiated by the ARP

Figure 9: Service DeActivation initiated by the ARP

V1.0 Page 14 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

3.1.10 Service DeActivation initiated by the DSP

Figure 10: Service DeActivation initiated by the DSP

3.1.10.1 Customer ports out via MNP during Single IMSI ARP contract
The MNP opt-out process implies that DSP will deactivate the ARP subscription during the
MNP procedure.
This means that the “Service DeActivation initiated by DSP” process, described in 3.1.10
will be used.
3.1.10.2 Customer changes MSISDN and/or IMSI during Single IMSI ARP contract
The change of MSIDN/IMSI implies that DSP will deactivate the ARP subscription during the
change procedure.
This means that the “Service DeActivation initiated by DSP” process, described in 3.1.10
will be used.
The Customer will start a new Activation Process in order to set up a new subscription with
new identifier.

3.1.11 Suspension and Termination of contract between DSP and ARP

DSP and ARP can decide to suspend or deactivate their agreement, or one of the parties
could decide unilaterally to do it under conditions defined by the bilateral agreement.
If such a situation occurs, all customer subscriptions will be deactivated and roaming
service will fall back to being provided by the DSP.

V1.0 Page 15 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

A message, similar to the DeProvisioningAnnouncement should be sent by the ARP to all

customers affected to inform them of the deactivation of their ARP contract.

4 Operation Description

4.1 Single IMSI

4.1.1 AcK
This is the synchronous acknowledge.

4.1.2 PreProvisioningRequest
This service is used by ARP to ask DSP to activate an ARP subscription.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
ARP TADIG Code of the ARP requesting the PreProvisioning operation
User Identifier Array of parameters that identify the User (MSISDN, IMSI, ICCID)
ARP Signalling Status Code that identifies the proposed signalling type of the ARP
Subscription (OnLine/OffLine)
Authorization Information Array of parameters used to transfer any information useful for
Authorization Process
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 1: PreProvisioningRequest

Processes:
Service Activation by the customer – Scenario 1
Service Activation by the customer – Scenario 2

V1.0 Page 16 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

4.1.3 PreProvisioningRequestAcknowledgement
This service is used by DSP to confirm to ARP that the PreProvisioningRequest has been
taken on.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the customer subscription
Request Arrival Time Date and Time of when the provisioning request arrived to DSP
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 2: PreProvisioningRequestAcknowledgement

Processes:
Service Activation by the customer – Scenario 1
Service Activation by the customer – Scenario 2

4.1.4 ProvisioningRequest
This service is used by ARP to confirm to DSP that internal activities have been concluded
and the activation can start on DSP side.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.

V1.0 Page 17 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

For example, all messages exchanged for the same Activation

Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 3: ProvisioningRequest

Processes:
Service Activation by the customer – Scenario 1
Service Activation by the customer – Scenario 2

4.1.5 ProvisioningCompletion
This service is used by DSP to notify the result of an activation request of an ARP
subscription.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Provisioning Start Time Date and Time of when the provisioning procedure started
Provisioning End Time Date and Time of when the provisioning procedure ended
Subscription Id Unique Code that identifies the ARP Subscription
Notification Code Identification code of the result of the activation
Notification Description Description of the result
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary

V1.0 Page 18 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

according to the context

Table 4: ProvisioningCompletion

Processes:
Service Activation by the customer – Scenario 1
Service Activation by the customer – Scenario 2

4.1.6 PreProvisioningCompletion
This service is used by DSP to notify ARP if the customer can be provisioned or not

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
InterfaceProvider Array of parameters that identify the provider for each interface
(IF1, IF2, IF3 …)
Subscription Id Unique Code that identifies the ARP Subscription
User Identifier Array of parameters that identify the User (MSISDN, IMSI, ICCID)
Notification Code Identification code of the result of the activation
Notification Description Description of the result
ARP Signalling Status Code that Identifies the Signalling (OnLine/OffLine) to be used by
ARP
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 5: PreProvisioningCompletion

Processes:
Service Activation by the customer – Scenario 1
Service Activation by the customer – Scenario 2

V1.0 Page 19 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

4.1.7 ReProvisioningRequest
This service is used by ARP to request to DSP to change the customer charge type at ARP
(online/offline).

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
OLD ARP Signalling Status Code that Identifies the OLD Signalling Status of the ARP
Subscription (OnLine/OffLine)
NEW ARP Signalling Status Code that Identifies the NEW Signalling Status of the ARP
Subscription (OnLine/OffLine)
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 6: ReProvisioningRequest

Processes:
Customer changes Signalling Status

4.1.8 ReProvisioningCompletion
This service is used by DSP to confirm to ARP that the customer charge type at ARP
(online/offline) has been changed.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
InterfaceProvider Array of parameters that identify the provider for each interface (IF1,
IF2, IF3 …)
Subscription Id Unique Code that identifies the ARP Subscription

V1.0 Page 20 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Change Start Time Date and Time of when the change procedure started
Change End Time Date and Time of when the change procedure ended
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
ARP Signalling Status Code that Identifies the Signalling (OnLine/OffLine) to be used by
ARP
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 7: ReProvisioningCompletion

Processes:
Customer changes Signalling Status

4.1.9 ReProvisioningNotification
This service is used by DSP to inform ARP that a ReProvisioning process has been started.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Change Type Field that describes the Change Type: From Online to Offline or from
Offline to Online
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,

V1.0 Page 21 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 8: ReProvisioningNotification

Processes:
Customer changes Signalling Status

4.1.10 ReProvisioningAcknowledgement
This service is used by DSP to confirm to ARP that the ReProvisioningRequest has been
taken on or used by ARP to confirm to DSP that the ReProvisioningNotification has been
received.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Arrival Timestamp Date and Time of when the ReprovisioningRequest or the
ReProvisioningNotification has been received, depending on
involved scenario
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 9: ReProvisioningAcknowledgement

Processes:
Customer changes Signalling Status

V1.0 Page 22 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

4.1.11 SuspendRoaming
This service is used by ARP to ask DSP the suspension of the roaming service within a
Fraud Management Process.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 10: SuspendRoaming

Processes:
Fraud Management and Prevention – Scenario 1
Fraud Management and Prevention – Scenario 2

4.1.12 RoamingSuspended
This service is used by DSP to notify ARP about the suspension of the roaming service.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Notification Code Identification code of the result of the activation
Notification Description Description of the result
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged

V1.0 Page 23 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

between ARP and DSP and related to the same process.

For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 11: RoamingSuspended

Processes:
Fraud Management and Prevention – Scenario 1
Fraud Management and Prevention – Scenario 2

4.1.13 UnSuspendRoaming
This service is used by ARP to ask DSP the unsuspension of the roaming service within a
Fraud Management Process.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 12: UnSuspendRoaming

Processes:

V1.0 Page 24 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Fraud Management and Prevention – Scenario 1

4.1.14 RoamingUnSuspended
This service is used by DSP to notify ARP about the unsuspension of the roaming service.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Notification Code Identification code of the result of the activation
Notification Description Description of the result
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 13: RoamingUnSuspended

Processes:
Fraud Management and Prevention – Scenario 1

4.1.15 DeProvisioningRequest
This service is used by ARP to ask DSP to cancel an ARP subscription.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Deactivation Reason Identification of the reason why the subscription should be
deactivated.
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the

V1.0 Page 25 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

process is started by DSP) and identifies all messages exchanged

between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 14: DeProvisioningRequest

Processes:
Service DeActivation initiated by of the customer
Service DeActivation initiated by ARP

4.1.16 DeProvisioningAckowledgement
This service is used by DSP to confirm to ARP that the DeprovisioningRequest has been
taken on.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Notification Code Identification code of the result of the deactivation
Notification Description Description of the result
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary

V1.0 Page 26 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

according to the context

Table 15: DeProvisioningAckowledgement

Processes:
Service DeActivation initiated by of the customer
Service DeActivation initiated by ARP

4.1.17 DeProvisioningCompletion
This service is used by DSP to notify the result of a cancellation request of an ARP
subscription, either positive or negative.

Parameters Explanation
SENDER TADIG Code of the message Sender
RECEIVER TADIG Code of the message Receiver
Subscription Id Unique Code that identifies the ARP Subscription
Deactivation Start Time Date and Time of when the deprovisioning procedure started
Deactivation End Time Date and Time of when the deprovisioning procedure ended
Deactivation Reason Identification of the reason why the subscription has been
deactivated
Notification Code Identification code of the result of the deactivation
Notification Description Description of the result
Transaction Id Unique Code that identifies all messages exchanged within the
same process.
The code is generated by ARP (or DSP in specific cases, when the
process is started by DSP) and identifies all messages exchanged
between ARP and DSP and related to the same process.
For example, all messages exchanged for the same Activation
Process for a specific subscription
(PreProvisioningRequest,
PreProvisioningAcknowledgement,
PreProvisioningCompletion,
ProvisioningRequest,
ProvisioningCompletion)
will contain the same TransactionId
Bilateral Information Optional field bilaterally agreed that is beyond the scope of SI-IF7.
This content is defined by bilateral agreement and may vary
according to the context

Table 16: DeProvisioningCompletion

Processes:
Service DeActivation initiated by Customer
Service DeActivation initiated by ARP
Service DeActivation initiated by DSP

V1.0 Page 27 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Service Activation by the customer – Scenario 1

Service Activation by the customer – Scenario 3
Customer ports out via MNP during Single IMSI ARP contract

V1.0 Page 28 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

5 Parameters Definitions
SERVICE PARAMETERS
PreProvisioningReq Name Type/Values Optional Description
uest
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
ARP Text – 5 Characters NO TADIG Code of the ARP requesting
the PreProvisioning operation
UserIdentifier Text NO Array of parameters used to
communicate UserId.

Each parameter is documented with

the sintax “[UserIsType=UserId]”
where:

UserIdType can have one of the

values:
MSISDN
IMSI
ICCID

MSISDN will be in international

format

Example:
[MSISDN=393351234567]
[IMSI=222011234567890]

ARP Signalling Status OnLine YES Signalling status of ARP

OffLine subscription

TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of

ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912

V1.0 Page 29 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

AuthorizationInformation Text YES Array of Values.

Each parameter is documented with
the sintax “[Name=Value]”

Parameters needed for this field are

defined by National Regulator

Example:
[AuthorizationCode-00AFGH67]

[FirstName=Francesco][LastName=
Donato][DateOfBirth=21061970]
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
PreProvisioningReq Name Type/Values Optional Description
uestAcknowledgeme
nt SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
RequestArrivalTimestamp Date 
NO
The date is specified in the following form

YYYY-MM-DDThh:mm:ss[+/-]hh:mm

where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00

V1.0 Page 30 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of

DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
Name Type/Values Optional Description
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
ProvisioningRequest Example:
ITASIITA011234567891234567891
2
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
Name Type/Values Optional Description
SENDER Text – 5 Characters NO TADIG Code of the Sender
ProvisioningComplet
ion RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG

V1.0 Page 31 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Code and a unique code generated

by DSP
Example:
ITASIITA011234567891234567891
2
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
Provisioning Start Timestamp Date NO

The date is specified in the following form

YYYY-MM-DDThh:mm:ss[+/-]hh:mm

where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00

V1.0 Page 32 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Provisioning End Timestamp Date NO

The date is specified in the following form

YYYY-MM-DDThh:mm:ss[+/-]hh:mm

where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00

Notification Code 0: Activated NO This field will be populated

1: Not Activated – Generic accordingly with local privacy
regulation.
2: Not Activated – DSP has not yet sent a
PreProvisioningCompletion
In case the sender has privacy
3: Not Activated – DSP has sent a restrictions for sending this
PreProvisioningCompletion(NOK) information “generic” codes must
4: Not Activated – invalid Transaction ID be used
5: Not Activated – valid Transaction ID but the MSISDN does
not match with what was sent in the
PreProvisioningRequest
100-199: reserved for local use
200-500: reserved for bilateral agreements

Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content

V1.0 Page 33 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

PreProvisioningCom Name Type/Values Optional Description

pletion
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
InterfaceProvider Text YES Array of parameters that identify the
provider for each interface (IF1, IF2,
IF3 …)

It will be populated only in case

Notification Code=0

Each parameter is documented with

the sintax “[Interface=Value]”
where:

Interface can be one of the values:

IF1, IF2, IF3, IF4, IF5, IF6, IF7, IF8,
IF9
and Value is the TADIG Code of
the MNO/MVNO providing the
interface

When an Interface is missing

within the array it is intended that
it is provided by the SENDER

Example:

[IF1=ITASI][IF2=ITA01]
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP

Example:
ITASIITA011234567891234567891
2
UserIdentifier Text YES Array of parameters used to
communicate UserId.

V1.0 Page 34 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Each parameter is documented with

the sintax “[Name=Value]” where:

Name can be one of the values:

MSISDN
IMSI
ICCID

MSISDN will be in international

format

Example:

[MSISDN=393351234567]

[IMSI=22011234567890]
Notification Code 0: Activable NO This field will be populated
1: No Active Agreement accordingly with local privacy
regulation.
2: Not authorized - Generic
3: Not authorized – Not customer of this DSP
In case the sender has privacy
4: Not authorized – Incorrect Authorization Method restrictions for sending this
5: Not authorized – Incorrect Authorization Credentials information “generic” codes must
6: Not eligible - Generic be used
7: Not eligible – Recipient ARP doesn’t have an agreement
with DSP
8: Not eligible – Customer not controlled by DSP
9: Not eligible – Subscriber’s domestic service has been
suspended
10: Not eligible – Subscriber’s roaming service has been
suspended
11: Not eligible – Subscriber has no contract to receive
roaming service
12: Not eligible – The service requestor is not the legal
responsible party
13: Not eligible - There is another ongoing provisioning or de-
provisioning request for this UserId
14: Not eligible - Request is based on non-primary UserId for

V1.0 Page 35 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

the subscription
15: Not eligible – Customer requested MNP
100-199: reserved for local use
200-500: reserved for bilateral agreements
Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code
ARPSignallingStatus OnLine NO Signalling Status of ARP
OffLine subscription after the
ReProvisioning
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
ReProvisioningRequ Name Type/Values Optional Description
est
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
OLD ARP Signalling Status OnLine NO Old Signalling Status of ARP
OffLine subscription

NEW ARP Signalling Status OnLine NO New Signalling Status of ARP

OffLine subscription

Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912

V1.0 Page 36 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

ReProvisioningCom Name Type/Values Optional Description

pletion
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
InterfaceProvider Text YES Array of parameters that identify the
provider for each interface (IF1, IF2,
IF3 …)

It will be populated only in case

Notification Code=0

Each parameter is documented with

the sintax “[Interface=Value]”
where:

Interface can be one of the values:

IF1, IF2, IF3, IF4, IF5, IF6, IF7, IF8,
IF9
and Value is the TADIG Code of
the MNO/MVNO providing the
interface.

When an Interface is missing

within the array, it is intended
that it is provided by the
SENDER

Example:

[IF1=ITASI][IF2=ITA01]
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2

V1.0 Page 37 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Change Start Timestamp Date NO

The date is specified in the following form

YYYY-MM-DDThh:mm:ss[+/-]hh:mm

where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00
Change End Timestamp Date NO

The date is specified in the following form

YYYY-MM-DDThh:mm:ss[+/-]hh:mm

where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second

V1.0 Page 38 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00
ARPSignallingStatus OnLine NO Signalling Status of ARP
OffLine subscription after the
ReProvisioning

In case the ReProvisioning is

unsuccessful, the
ARPSignallingStatus will be
populated with the old value.
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
ReProvisioningNotifi Name Type/Values Optional Description
cation
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
ChangeType 1: From OnLine to OffLine NO
2: From OffLine to OnLine 

Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912

V1.0 Page 39 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

ReProvisioningAckn Name Type/Values Optional Description

owledgement
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Arrival Timestamp Date NO Date and Time of when the

ReprovisioningRequest or the
ReProvisioningNotification has
The date is specified in the following form "YYYY-MM-
been received, depending on
DDThh:mm:ss[+/-]hh:mm" where: involved scenario

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00

Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
DeProvisioningRequ Name Type/Values Optional Description
est
SENDER Text – 5 Characters NO TADIG Code of the Sender

V1.0 Page 40 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

RECEIVER Text – 5 Characters NO TADIG Code of the Receiver

SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Deactivation Reason 1 digit, encoded as: NO In case the Deactivation has been
requested for Fraud Management
reason (i.e. Code Value 4), the DSP
0: request by customer should treat the request as a priority
1: MNP port out and process it as soon as possible,
2: swap to another ARP Optionally, DSP and ARP can
3: customer deactivation by DSP agree bilaterally on a specific Fraud
Suspension Code
4: fraud management
5: termination of contract with the subscriber – bill payer
initiated
6: termination of contract with the customer – operator
initiated
7: Change in subscriber primary identifier
8: Subscription modification incompatible with ARP contract
10: Generic
50-99: Reserved for bilateral agreements
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Unique Identifier of the Activate
request.
Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Must be the same code provided
within the corresponding
PreProvisioningRequest request
Example:
ITA0112345678912345678912
Name Type/Values Optional Description
DeProvisioningAcko
SENDER Text – 5 Characters NO TADIG Code of the Sender
wledgement
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver

V1.0 Page 41 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of

DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2

Notification Code 0: Deprovisionable NO

1: Not Deprovisionable – Not authorized - Generic
2: Not Deprovisionable – Not authorized – Not customer of this
DSP
3: Not Deprovisionable – Not eligible - Generic
4: Not Deprovisionable – Not Eligible - There is another
ongoing provisioning or de-provisioning request for this UserId
100-199: Local
200-500: reserved for bilateral agreements
Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
DeProvisioningCom Name Type/Values Optional Description
pletion
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2

When the message is exchanged

within an “Activation with swap
between two ARPs” process, the

V1.0 Page 42 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

SubscriptionId contains the OLD

Code

Deactivation Reason 0: request by customer YES In case the Deactivation has been
1: MNP port out requested for Fraud Management
reason (i.e. Code Value 4), the DSP
2: swap to another ARP should treat the request as a priority
3: customer deactivation by DSP and process it as soon as possible.
4: fraud management Optionally, DSP and ARP can
agree bilaterally on a specific Fraud
5: termination of contract with the subscriber – bill payer Suspension Code.
initiated
6: termination of contract with the customer – operator
initiated In case the
DeProvisioningCompletion is sent
7: Change in subscriber primary identifier as part of a process that doesn’t
8: Subscription modification incompatible with ARP contract contain a DeProvisioningRequest
10: Generic sent by ARP (Service Deactivation
Initiated by the DSP or Swap to
50-99: Reserved for bilateral agreements another ARP, or MNP port-out,
Change of UserId, etc.) this field
must be populated.
DeProvisioning Start Timestamp Date NO

The date is specified in the following form "YYYY-MM-

DDThh:mm:ss[+/-]hh:mm" where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00
DeProvisioning End Timestamp Date NO

The date is specified in the following form "YYYY-MM-

V1.0 Page 43 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

DDThh:mm:ss[+/-]hh:mm" where:

 YYYY indicates the year

 MM indicates the month
 DD indicates the day
 T indicates the start of the required time section
 hh indicates the hour
 mm indicates the minute
 ss indicates the second
 [+/-]hh:mm indicates time zones

Example:
2013-05-01T19:50:00+01:00
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code usually generated by ARP,
except for the process “Service
Deactivation Initiated by DSP”
where the parameter is generated
by DSP.

Example:
ITA0112345678912345678912
When the message is exchanged
within an “Activation with swap
between two ARPs” process, the
TransactionId contains the NEW
ARP TADIG CODE, even if the
message is sent from DSP to the
OLD ARP to communicate the
swap.
Notification Code 0: Deprovisioned NO
1: Not Deprovisioned – Not authorized - Generic
2: Not Deprovisioned – Not authorized – Not customer of this
DSP
3: Not Deprovisioned – Not eligible - Generic
4: Not Deprovisioned – NotEligible - There is another ongoing
provisioning or de-provisioning request for this UserId
100-199: Local

V1.0 Page 44 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

200-500: reserved for bilateral agreements

Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
SuspendRoaming Name Type/Values Optional Description
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
RoamingSuspended Name Type/Values Optional Description
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Notification Code 0: Suspended NO
1: Not Suspended – Generic
2: Not Suspended – invalid Transaction ID
3: Not Suspended – Invalid SubscriptionId
100-199: reserved for local use

V1.0 Page 45 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

200-500: reserved for bilateral agreements

Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code

Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
UnSuspendRoaming Name Type/Values Optional Description
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO Obtained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2
Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content

TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of

ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912
RoamingUnSuspend Name Type/Values Optional Description
ed
SENDER Text – 5 Characters NO TADIG Code of the Sender
RECEIVER Text – 5 Characters NO TADIG Code of the Receiver
SubscriptionId Text [30 alphanumeric digits] NO btained by the concatenation of
DSP TADIG CODE, ARP TADIG
Code and a unique code generated
by DSP
Example:
ITASIITA011234567891234567891
2

V1.0 Page 46 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Notification Code 0: ReActivated NO

1: Not ReActivated – Generic
2: Not ReActivated – invalid Transaction ID

3: Not ReActivated – Invalid SubscriptionId

100-199: reserved for local use
200-500: reserved for bilateral agreements
Notification Description Text [max 80 alphanumeric digits] YES Free text description of the
Notification Code

Bilateral Information Text [max 80 alphanumeric digits] YES Bilaterally agreed content
TransactionId Text [25 alphanumeric digits] NO Obtained by the concatenation of
ARP TADIG Code and a unique
code generated by ARP
Example:
ITA0112345678912345678912

Table 17: Parameter Definition

V1.0 Page 47 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

6 Testing Procedure
TBD

7 Release Management
TBD

8 Security
Security requirements between DSP and ARP are subject to further study and will be
included in a separate document.

V1.0 Page 48 of 49
GSM Association Non-confidential
Official Document TD.107 - Single IMSI Provisioning Interface

Document Management

Document History

Version Date Brief Description of Change Approval Editor /

Authority Company
th New PRD TADIG
26 Nov Francesco Donato
1.0 Created by the BEREC Stakeholder eVote
2013 (Telecom Italia)
Forum Billing & Provisioning Subgroup PSMC #118

Other Information
Type Description
Document Owner TADIG
Editor / Company Francesco Donato (Telecom Italia)

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.

V1.0 Page 49 of 49