At a glance
Handles number portability in and out with the clearing house and other operators.
Key data
Receives from
- Order capture
- Clearing house
Sends to
- Resource management
- Provisioning
- Billing
How it works
The main steps, end to end.
- 1Validate eligibility and customer details
- 2Send the port request
- 3Track responses and rejections
- 4Schedule and run the cutover
- 5Close the request and update routing
Core Capabilities
What the MNP module provides
Port-in Flow
- Subscriber requests to keep existing number when joining new network
- MNP module receives port-in request from Order Capture
- Submits porting request to the number portability clearing house
- Tracks porting status: Submitted → Approved → Scheduled → Completed
- Triggers service activation on successful port completion
Port-out Flow
- Subscriber requests to transfer number to another network
- Validates subscriber eligibility: account in good standing, no outstanding debt
- Submits port-out notification to number portability clearing house
- Suspends service and disconnects line on port-out completion
- Releases MSISDN to quarantine on successful port-out
Clearing House Integration
- Interfaces with the national number portability database/clearing house
- Submits porting authorisation codes and validates responses
- Receives porting schedule notifications and completion confirmations
- Handles rejection codes and retry logic per clearing house rules
Porting Schedule
- Port completion scheduled at a specific date and time
- Porting cutover window: typically midnight to early morning
- SOM executes provisioning tasks at scheduled port time
- Handles schedule changes requested by gaining/losing network
Status Tracking
- Full porting status visible in CRM for agent enquiries
- Subscriber notification at each porting milestone
- Failed porting retry workflow with clearing house
- Cancellation workflow if porting is abandoned before cut-over
MNP Reporting
- Tracks port-in and port-out volumes per period
- Measures porting success and failure rates
- Identifies porting cancellation reasons for process improvement
- Reports average porting duration from request to completion
Storage & Persistence
How and where MNP stores its data
Document Data Store
- Port-in request documents: MSISDN, subscriber, schedule, status
- Port-out notification documents: reason, clearing house response
- Clearing house submission and response audit records
- Porting cancellation records with reason and timestamp
Async Event Bus
- Port-in approved event — triggers service activation
- Port-out completed event — triggers disconnection and MSISDN release
- CRM status update events for agent visibility
- Porting schedule change notifications
External Clearing House
- Number portability database — external national system
- MSISDN routing tables updated on port completion
- Clearing house maintains authoritative porting state
Design Principles
Key architectural decisions behind the MNP module
Clearing House Abstraction
MNP encapsulates all clearing house communication behind a single internal interface. Changes to the clearing house protocol, API version or submission format are handled within MNP without impacting Order Capture, SOM or any other service.
Time-precision Cutover
Number portability requires cutover at a precise scheduled time. MNP coordinates with SOM to ensure provisioning tasks execute within the scheduled porting window — failures during this window trigger immediate retry before the window closes.
State Machine Integrity
Every porting request follows a strict state machine. Invalid transitions (e.g. completing a porting request that was cancelled) are rejected. This ensures the number portability database always reflects the true state of each porting request.
Flag customers likely to port out so retention can act first.
Detect fraudulent port-out requests used for SIM takeover.
More in 30 AI & ML use cases and AIOps for BSS.