Skip to content
KaldrivonR1Lab Synthetic reference workflow

SON to rApp Migration Workbench

Trace a SON function from its original contract through R1 services to an observed outcome.

Operators and vendors have publicly described moving SON functionality into Non-RT RIC and rApp environments; that motivates this topic. All cells, numbers, rules, approvals and outcomes in this application are fictional. Nothing here controls a live RAN.

About the author

Janos Korognai: 21 years in telecom pre-sales and solution architecture (OSS, network management, SMO, Non-RT RIC, rApps) for Tier-1 operators. This demo is an independent, hands-on project, not affiliated with any vendor.

Migration path at a glanceHow a SON function works once it moves into an rApp. Read left to right: the contract feeds the rApp, the rApp only talks R1, and the platform reaches the network for it.
Legacy SON contract rApp R1 services SMO / Non-RT RIC O1 to managed RAN functions; A1 to Near-RT RIC where relevant Simulated RAN
Start hereThree steps below: pick a SON function, choose how the run behaves, then step through the migration.
1

Pick a use case

2

Set scenario, mode and platform

Shared by every tab. Changing any of these restarts a Migration run in progress.
Mode
PCI design
View

3

Run it