Dual Version PortaSwitch is a solution for gradual migration to a newer software system version across several MRs using a two-system setup and customer batching. It allows service providers to gain access to the new features, secure their existing platform’s overall stability during an update, and carry out the update at a comfortable pace.
Dual Version PortaSwitch consists of two systems – source and target – that operate simultaneously.
The source system runs the current release (e.g., MR65).
The target system initially mirrors the source system and is then updated to a new release (i.e., MR65→MR80).
To eliminate human errors and ensure stable and correct processes of service configuration and data transfer, Dual Version PortaSwitch provides technical solutions that help migrate some of the existing customers to the new release. Customer migration is done in batches. Immediately after the migration of a given customer batch, the services for it can be run with minimum reconfiguration efforts.
The available technical solutions in Dual Version PortaSwitch address:
Customer data transfer.
Transparent routing of the calls to the system serving the customer.
Proxying RADIUS/Diameter requests to the system serving the customer.
Common API entry point.
Distribution of number porting requests across systems based on the customer record location
The target system starts as a full database copy of the source (production) system (e.g., MR72). The database snapshot of the production system is copied to the target system, where it is upgraded to the new software version (e.g., MR85). As a result, all configuration entities such as products, tariffs, and rates are cloned and ready-to-use on the target system.
The dedicated provisioning scenario configures interconnection between both the source and target systems, installs all required code modifications, and enables all components required to run Dual Version PortaSwitch, such as ESPF handlers, forwarding registry, etc.
Currently, the updates that “jump” over several release versions require obligatory checkpoints every 15 releases (currently MR55-6→MR70-6 or MR70-6→MR85-3).