PortIn
Syniverse
The Mobile Number Portability platform used by UK MNOs and MVNOs to initiate the porting process. is used as an MNP
Mobile Number Portability. An implementation or standard that enables mobile phone users to retain their phone number when transferring from one mobile network operator to another. (Mobile Number Portability) interface by UK MNOs (Mobile Network
In the context of CMP, the infrastructure on which usage of registered customers will be measured – this could be a mobile phone network, broadband network or other non-telecommunications network. Operators) to initiate the porting
The process of transferring a subscriber between service provider networks while ensuring they retain their existing mobile telephone number. process.
The PortIn web service
XML- or JSON-based information exchange systems that use the Internet for direct application-to-application interaction. These systems can include programs, objects, messages, or documents. enables an external client system to retrieve the PAC
The Porting Authorisation Code, or PAC, is supplied by Syniverse (UK only) when subscribers choose to keep their mobile number when moving to another operator. The subscriber provides this code to the new network provider to initiate the process of porting their phone number. from Syniverse, and then close the PAC with Syniverse.
As part of this process, a non-network number change may be required to get the Port In Number into Non-Managed Serial Number 4 field as per current CMP GUI
Now called AgentView; the graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. process.
The Error On Invalid Port Date flag is used when sending the request to Syniverse to decide whether Syniverse is to throw an error or substitute in the next available port date and return it.
This web service accepts a PAC code, a Port In number, a Subscription
A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription Number and a Port Date.
PortIn Request
The PortIn tag instructs the Porting Service to create a Port In. This tag contains the following elements:
|
Element Name |
Content Type |
Description |
Required? |
|---|---|---|---|
|
ExternalReference |
String69 |
The client may use this identifier to correlate the request and the response. |
Optional |
|
PortDetails |
Container |
See PortDetails Request Container for details. |
Mandatory |
PortDetails Request Container
The PortDetails request container has the following elements:
|
Element Name |
Content Type |
Description |
Required? |
|---|---|---|---|
|
SubscriptionNumber |
Integer8 |
Indicates the unique system generated subscription number. |
Mandatory |
|
PACCode |
String9 |
The unique PAC (Port Authorisation Code) retrieved from Syniverse. This is created if the customer wishes to port out to another network. |
Mandatory |
|
PortInNumber |
String25 |
This is the new number to be ported in. |
Mandatory |
|
PortDate |
date |
The date on which the number is to be ported in. |
Mandatory |
|
UseSuggestedDateOnConflict |
Boolean |
The useSuggestedDateOnConflict is passed to Syniverse.
|
Optional |
PortIn Response
The PortIn response is the response to the PortIn request. This contains the following elements:
|
Element Name |
Content Type |
Description |
Required? |
|---|---|---|---|
|
ExternalReference |
String69 |
Returned unmodified in the response. The client may use this identifier to correlate the request and the response. |
Optional |
|
PortDate |
date |
The date on which the portin will occur. See useSuggestedDateOnConflict flag in PortDetailsRequest Container.
|
Mandatory |