MNP in Poland

In Poland, the regulatory body Urząd Komunikacji Elektronicznej (Office of Electronic Communications) relies on the PLI-CBD (Localization and Information Platform with the Central Database). Managing the porting process between the donor and recipient service providers is crucial. The MNP process is initiated when the recipient service provider creates and submits the Port- In request to PLI-CBD. As a result, the Port-Out request is sent to the Donor Service Provider (from which the phone number will be migrated). PLI-CBD handles the communication between the Port-In and Port-Out requests.

MNP Lifecycles

MNP-OUT

Pending The MNP-Out (Port-Out) process begins when the donor receives the Port-Out request from the regulator in the Pending state. At this stage, depending on whether the Port- Out was made with Power of Attorney or not, two possible flows are applicable:

1. Port-Out with Power of Attorney: alongside the Port-Out request is the contract termination request which might represent additional costs to the customer (due payments until contract ends).
2. Port-Out without Power of Attorney: The customer must contact the Donor offline in the following 21 days to request and negotiate the contract termination and, following that, to allow the Port-Out request to proceed. If no agreement for contract termination is reached, the customer can keep the current contract with the Donor with a new Phone Number and still port out the current requested Phone Number.

Pending During this state 1GLOBAL will perform typical validations and requests from the partner to accept or reject (typically, the partner shall accept by default for prepaid cases). If all validations pass, the request will transition to a Scheduled state or become Rejected due to a data mismatch. Scheduled The request will remain Scheduled for up to two days before the portability execution date when it will become Locked, and 1GLOBAL will start facilitating the communication with relevant entities like the PLI-CBD and all the required operations to complete the MNP process.

Special cases

• Cancellation requested During the Pending and Scheduled states; the customer may decide to cancel the portability request. This action can be performed either on the Donor’s or the Recipient’s side. (For example, the customer received a better offer from the donor and decided to stay). The regulator will typically validate the request and will approve or reject the cancellation reject. Approval will issue the cancellation, and rejection will result in transitioning the request back to the previous status, i.e., pending or scheduled.
• Reschedule During the Scheduled state, the customer may want to reschedule the request. Unlike Port-Out request cancelation, the request to reschedule can only be performed on the Donor’s side. Rescheduling cannot be made before the currently scheduled date or more than 30 days later. The regulator will validate and approve or reject the rescheduling request. If approved, the scheduled date will be revised; if rejected, it will remain intact.

Locked Two calendar days before the portability date, no further changes will be allowed. Completed On the processing date, 1GLOBAL will coordinate with the regulator and the other carrier to execute the number Port-Out.

MNP-IN

Draft State The customer initiates the MNP-IN (Port-In) with a request on the recipient’s side to port their number from the donor. At this point, the required customer information, as referenced in 2.1.1, was already submitted during contract creation, The Port-In request will contain the Mobile Number Portability Request information, as referenced in 2.1.2. The customer information is validated for correctness by the Partner. Then, the draft Port-In request is sent to 1GLOBAL to validate the customer, phone number, and porting information with PLI-CBD and the Donor.

Pending If the request is approved by the Donor, the regulator will inform 1GLOBAL to transition the request to the Pending state. In case there is a data mismatch or other rejection reason request, the request will get rejected and will transition to the Rejected state.

Scheduled If accepted, the request moves to a scheduled status for the given date approved date. Special cases

• Cancellation requested In Port-In (similar to Port-Out flow), the customer may decide to cancel the request during the Pending or Scheduled states, and this option must be available on both Donor’s and the Recipient’s end. The cancellation will be approved or rejected. Approval will issue the cancellation, and rejection will result in transitioning the request back to the previous status, i.e., pending or scheduled.
• Reschedule in Port-In flow, rescheduling option is not available on the recipient’s side,and user needs to submit any rescheduling request on the Donor’s side. In case of rescheduling, the Recipient will receive a new date, and the request will transition back to scheduled. In case the rescheduling request gets rejected, the port request will transition to scheduled for the same date.

Locked Two calendar days before the portability date, no further changes will be allowed.

Processing When the portability date is met, it goes to processing status, which consists of the de-provisioning of the phone number on the donor’s side and the provisioning on the recipient provider, in this case, 1GLOBAL and its Partner.

Finally, the request is marked as Completed, and the customer is notified. 1GLOBAL will facilitate the process of assigning the phone number to the customer’s subscription

Required Customer Data

Personal Account

• First Name
• Last Name
• Identity document:
  • For Polish Citizens: PESEL or ID Citizen Card
  • For Foreigners: Passport Number or Residence Card Number
• Address
• Email

Business Account

• Company Name
• NIP/REGON
• Business Address
• Billing Address ( if different from Business Address)

API endpoints

Endpoints were added as Mandatory and Optional. The reasoning for this clustering is explained as follows:

• Mandatory means they are part of the MNP core process and without them, it is not possible to go through the process from the start until the end.
• Optional means they are available to be considered by the Partner to enable specific business, customer service processes supporting the MNP process.

Endpoint	Required
List all service providers	Mandatory
Get phone-number-id from subscription	Mandatory
Create a new port order (Port-In)	Mandatory
Request cancelation of the Porting	Mandatory
Request reschedule of the Porting	Mandatory
List all Porting requests	Optional
Get a specific Porting	Optional
Get a MSISDN porting opt-in config	Optional