# US 2025/0211485 A1 · Incremental platform migration for telecommunications systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0211485 A1
- Document ID: US20250211485A1
- Status: Published application
- Kind: A1
- Application number: 18/394,994
- Filed: 2023-12-22
- Published: 2025-06-26
- Earliest claimed: 2023-12-22
- Assignees: DISH Wireless L.L.C.
- Applicants: DISH Wireless L.L.C.
- Inventors: Kazi BASHIR; Mehdi ALASTI; Siddhartha CHENUMOLU
- Web page: https://patentgrep.com/patent/US20250211485A1

## CPC

- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Incremental platform migration for telecommunications systems is disclosed. Network Functions (NFs) and capacity on a new (target) platform are incrementally scaled up and NFs and capacity on a legacy (current) platform are scaled down until the migration to the target platform is completed. As such, if issues arise during migration, the legacy platform still retains capabilities while the issues with the target platform are addressed.

## Claims

### Claim 1

A platform migration system for a telecommunications network, comprising:
one or more servers of a legacy platform running a plurality of Network Functions (NFs);
one or more servers of a target platform;
one or more Network Repository Function (NRF) servers that provide an NRF through which the plurality of NFs of the legacy platform are registered in the telecommunications network; and
a configuration server configured to manage migration of one or more of the plurality of NFs of the legacy platform to the target platform using a migration policy, wherein
the configuration server provides one or more configuration files to the target platform,
the one or more servers of the target platform implement the migration policy using the one or more configuration files, setup one or more NFs, and allocate an initial capacity for the target platform,
the one or more servers of the legacy platform reduce a capacity of the legacy platform by a first increment, and
the NRF distributes service requests to the one or more NFs of the target platform and one or more corresponding NFs of the plurality of NFs of the legacy platform in accordance with the migration policy.

### Claim 2 (depends on 1)

The platform migration system of claim 1, wherein the one or more servers of the legacy platform reduce the capacity of the legacy platform by the first increment using auto-scaling of a platform for automating deployment, scaling, and management of containerized applications.

### Claim 3 (depends on 1)

The platform migration system of claim 1, wherein the one or more servers of the target platform are configured to allocate a next increment of capacity for the target platform in accordance with the migration policy and the one or more servers of the legacy platform are configured to deallocate a next increment of capacity for the legacy platform in accordance with the migration policy after the target platform and the legacy platform operate nominally for a predetermined period of time in accordance with the migration policy.

### Claim 4 (depends on 3)

The platform migration system of claim 3, wherein after completion of the platform migration, the NRF is configured to deregister the one or more corresponding NFs of the plurality of NFs of the legacy platform.

### Claim 5 (depends on 1)

The platform migration system of claim 1, wherein
the one or more servers of the legacy platform and the one or more servers of the target platform run their respective NFs as containerized NFs, and
the one or more configuration files are Yet Another Markup Language (YAML) files comprising configurations for NF services.

### Claim 6 (depends on 1)

The platform migration system of claim 1, wherein an amount of the initial capacity allocation of the target platform and an amount of the initial capacity reduction of the legacy platform are different.

### Claim 7 (depends on 1)

The platform migration system of claim 1, wherein the migration policy comprises load balancing for service requests for the one or more NFs of the target platform and the one or more corresponding NFs of the legacy platform, an indication of a preference to use the one or more NFs of the target platform while the target platform has sufficient capacity, or both.

### Claim 8 (depends on 7)

The platform migration system of claim 7, wherein the load balancing comprises distributing a load between the legacy platform and the target platform proportional to respective capacities of the legacy platform and the target platform using a weighted load balancing algorithm.

### Claim 9 (depends on 1)

The platform migration system of claim 1, wherein responsive to an NF of the one or more NFs of the target platform failing, the NRF is configured to:
deregister the failed NF; and
route service requests for the failed NF to a corresponding NF of the plurality of NFs of the legacy platform.

### Claim 10 (depends on 9)

The platform migration system of claim 9, wherein responsive to the failed NF of the target platform being restored, the NRF is configured to:
register the restored NF; and
route service requests to the restored NF and the corresponding NF of the legacy platform in accordance with the migration policy.

### Claim 11

A plurality of non-transitory computer-readable media storing a plurality of computer programs, the plurality of computer programs configured to cause a plurality of processors to:
configure a target platform in accordance with a migration policy in one or more configuration files;
setup one or more Network Functions (NFs) on the target platform;
allocate an initial increment of capacity to the target platform;
reduce a capacity of a legacy platform by an initial increment;
register the one or more NFs of the target platform with a Network Repository Function (NRF); and
distribute service requests, via the NRF, to the one or more NFs of the target platform and one or more corresponding NFs of the legacy platform in accordance with the migration policy.

### Claim 12 (depends on 11)

The plurality of non-transitory computer-readable media of claim 11, wherein one or more computer programs of the plurality of computer programs are configured reduce the capacity of the legacy platform by the initial increment using auto-scaling of a platform for automating deployment, scaling, and management of containerized applications.

### Claim 13 (depends on 11)

The plurality of non-transitory computer-readable media of claim 11, wherein one or more computer programs of the plurality of computer programs are further configured to cause the plurality of processors to:
allocate a next increment of capacity for the target platform in accordance with the migration policy and deallocate a next increment of capacity for the legacy platform in accordance with the migration policy after the target platform and the legacy platform operate nominally for a predetermined period of time in accordance with the migration policy.

### Claim 14 (depends on 13)

The plurality of non-transitory computer-readable media of claim 13, wherein after completion of the platform migration, one or more computer programs of the plurality of computer programs are further configured to cause the plurality of processors to:
deregister the one or more corresponding NFs of the legacy platform, by the NRF.

### Claim 15 (depends on 11)

The plurality of non-transitory computer-readable media of claim 11, wherein
the legacy platform and the target platform run respective NFs as containerized NFs, and
the one or more configuration files are Yet Another Markup Language (YAML) files comprising configurations for NF services.

### Claim 16 (depends on 11)

The plurality of non-transitory computer-readable media of claim 11, wherein
the migration policy comprises load balancing for service requests for the one or more NFs of the target platform and one or more corresponding NFs of the legacy platform, an indication of a preference to use the one or more NFs of the target platform while the target platform has sufficient capacity, or both, and
the load balancing comprises distributing a load between the legacy platform and the target platform proportional to respective capacities of the legacy platform and the target platform using a weighted load balancing algorithm.

### Claim 17 (depends on 11)

The plurality of non-transitory computer-readable media of claim 11, wherein responsive to an NF of the one or more NFs of the target platform failing, one or more computer programs of the plurality of computer programs are further configured to cause the plurality of processors to:
deregister the failed NF, by the NRF; and
route service requests for the failed NF to a corresponding NF of the plurality of NFs of the legacy platform, by the NRF.

### Claim 18 (depends on 15)

The plurality of non-transitory computer-readable media of claim 15, wherein responsive to the failed NF of the target platform being restored, one or more computer programs of the plurality of computer programs further are configured to cause the plurality of processors to:
register the restored NF, by the NRF; and
route service requests to the restored NF and the corresponding NF of the legacy platform in accordance with the migration policy, by the NRF.

### Claim 19

A computer-implemented method for performing platform migration for a telecommunications network, comprising:
configuring a target platform in accordance with a migration policy in one or more configuration files, by a plurality of computing systems;
setting up one or more Network Functions (NFs) on the target platform, by the plurality of computing systems;
allocating an initial increment of capacity to the target platform, by the plurality of computing systems;
reducing a capacity of a legacy platform by an initial increment, by the plurality of computing systems;
registering the one or more NFs of the target platform with a Network Repository Function (NRF), by the plurality of computing systems;
distributing service requests, via the NRF, to the one or more NFs of the target platform and one or more corresponding NFs of the legacy platform in accordance with the migration policy, by the plurality of computing systems;
allocating a next increment of capacity for the target platform in accordance with the migration policy and deallocating a next increment of capacity for the legacy platform in accordance with the migration policy after the target platform and the legacy platform operate nominally for a predetermined period of time in accordance with the migration policy, by the plurality of computing systems; and
after completion of the platform migration, deregistering the one or more corresponding NFs of the legacy platform via the NRF, by the plurality of computing systems.

### Claim 20 (depends on 19)

The computer-implemented method of claim 19, wherein
the migration policy comprises load balancing for service requests for the one or more NFs of the target platform and the one or more corresponding NFs of the legacy platform, an indication of a preference to use the one or more NFs of the target platform while the target platform has sufficient capacity, or both, and
the load balancing comprises distributing a load between the legacy platform and the target platform proportional to respective capacities of the legacy platform and the target platform using a weighted load balancing algorithm.
