Portability / UK

Learn about mobile number portability in UK and its dedicated APIs


This feature does not concern IoT customers.

Introduction

An end user may want to change network operator, while keeping their MSISDN. This process is called a mobile number portability (MNP).

An MNP process involves different actors:

  • The end user is the subscriber which requests a portability from an operator to another.
  • The donor operator is the operator that the subscriber is leaving and which hosts the MSISDN at the beginning of the process.
  • The recipient is the operator towards which the subscriber is going to and which initiates the MNP process in order to let the subscriber keep their MSISDN on the recipient operator network (portability) or get a new one and automatically terminate its previous contract (switch).
  • Syniverse is the UK central system managing relationships between the operators during MNP processes.


Mobile number portability (MNP)

MNP process



A mobile number portability request is split into three steps:

  1. A subscriber requests their Porting Authorization Code (PAC) from their current operator and uses it to request a mobile number portability.
  2. The recipient operator submits the request to Syniverse. Syniverse can accept the request or reject it when the PAC does not match the MSISDN to port. While the request is not locked, the request can be canceled or postponed by the recipient. The day before the planned date, Syniverse notifies both recipient and donor that the portability will be executed: the request is now locked and modifications are prohibited.
  3. The mobile number portability is executed. The ported MSISDN is terminated on the donor operator side and is now used on the recipient operator side. All routing tables are updated for all UK network operators.

Please note that an end user can change network operator, while requiring a new MSISDN and request the termination of the contract with their current network operator. This process is called a switch. In this case, the end user must request a Service Termination Authorization Code (STAC), from their current operator.

As recipient operator

Overview

In this process, you are the recipient operator and 2 pre-requisites are necessary:

  • Your subscriber must provide as input their MSISDN and their associated PAC or STAC, depending on whether they want to keep their MSISDN or not. This information is communicated by their donor operator.
  • You must first activate the subscriber.

As soon as these requirements are met, you have two ways to request a mobile number portability:

  • Request for execution on a wished date.
  • Request for execution the day after the network attach of the subscriber's SIM card.


Mobile number portability


Mobile number portability process

Mobile number portability process as a recipient operator



Switch


Switch process

Switch process as a recipient operator



Lifecycle and statuses



Mobile number portability

Portability lifecycle

Portability lifecycle as a recipient operator



Switch

Portability lifecycle

Switch lifecycle as a recipient operator



StatusDescription
PENDINGPortability / switch request has been received
ATTACH_REQUESTEDA network attach notification has been requested
ATTACH_RECEIVEDThe SIM card has been successfully attached to the network
ATTACH_FAILEDThe SIM card never attached to the network before porting code expiration
VALIDATEDPortability / switch request has been validated by Syniverse
INVALIDATEDPortability / switch request has been rejected by the donor operator
LOCKEDPortability will be executed the next day, the request is locked
DONEPortability / switch has been successfully executed
CANCELINGYour cancellation request is in progress
CANCELEDYour cancellation request has been accepted and the portability / switch process has been canceled
ERRORThe portability / switch process was unable to complete successfully. Contact our support team, for more information.

As donor operator

Overview

When your subscriber wants to switch to another operator, they can request a PAC or a STAC to authorize the termination of their current contract. This information must be shared with your subscriber upon request in order for him to provide it to their new operator (recipient operator). In this scenario, you are the donor operator.

A PAC or a STAC can be used for 30 days, and after this, it will automatically expire.

From this point, you will have no more operations to do. This PAC or STAC will be used by the recipient operator to initiate the mobile number portability process or the switch. Finally, at the time requested by the recipient operator, Transatel will execute the portability and terminate the subscriber.



Mobile number portability


Mobile number portability process

Mobile number portability process as a donor operator



Switch


Switch process

Switch process as a recipient operator



Lifecycle and statuses



Mobile number portability

Portability lifecycle

Portability lifecycle as a recipient operator



Switch

Portability lifecycle

Switch lifecycle as a recipient operator



StatusDescription
CODE_PROVIDEDA valid PAC or STAC has been created
CODE_CANCELEDA PAC or STAC has been canceled
CODE_EXPIREDA PAC or STAC has expired
VALIDATEDRequest has been validated by Syniverse
LOCKEDPortability will be executed the next day, the request is locked
DONEPortability / switch has been successfully executed
ERRORThe portability / switch process was unable to complete successfully. Contact our support team, for more information.

Portability management

Request portability or switch

This operation starts a mobile number portability process when a PAC is provided or a switch process when a STAC is provided. Optionally, you can provide a wished portability date. This date must be between 3 and 59 working days from your request date and can not be on Sunday(s) or bank holiday(s).

As soon as the request is validated by Syniverse, a port in or switch validated event will let you know the actual execution date. This date can be different from your wished date. Please note that Syniverse very rarely rejects requests.

In case of rejection, you will be notified with a port in or switch invalidated event. This is the last event you will receive for this operation. If you want to fix your request, you must create a new one.

Finally, when the portability or switch request is successfully processed, you receive a port in or switch completed event.

If you do not provide a wished date, the port or switch will be triggered by the first network attach of the subscriber's SIM card. You will first receive a port in or switch network attach event. Once the SIM card is attached to the network (before the expiration of the PAC or the STAC), you will receive a network attach received event. Otherwise, a network attach failed event will be sent. This is the last event you will receive for this operation. If you want to fix your request, your end user must request a new PAC or STAC from their current network operator and you must start a new process.

Change the portability or switch date

This operation postpones the execution date of the portability or switch. It is not possible to choose a date prior to the current one or more than 59 working days after the request date. Once validated by Syniverse, a new validated date is returned.

Cancel a portability or switch request

This operation cancels a current portability or switch request. The cancellation is possible while the request is not locked. Please pay attention, although this is a synchronous operation, a canceled portability or switch event is generated.

Retrieve portability information

Using this operation, you can retrieve information about a mobile number portability process: status of the request, MSISDN, PAC or STAC and its expiration date, portability date and the donor/receiver operators.

Retrieve a PAC or STAC

With this operation, you can generate a PAC or STAC (or retrieve it if it has already been generated).

Cancel a PAC or STAC

This operation cancels a PAC or STAC while it is valid.