open OSS — Operations for AI-RAN

01 / ABOUT

WHY OPEN OSS

serious lab work.
made accessible.

open OSS is an independent radio research and development project creating an evidence-led operations layer for private 5G, Open5GS and AI-RAN experiments.

The project begins with what the network actually exposes—live telemetry, information APIs, logs and process state. It keeps unknowns visible, connects evidence to operational decisions and leaves authority with the engineer. The aim is simple: make advanced 5G experimentation easier to understand, validate and share without lowering the technical standard.

01ProjectRAYDEO R&D

02FoundationOPEN5GS

03Radio pathsrsRAN + SDR

04MethodEVIDENCE FIRST

05DirectionOPEN AI-RAN LAB

01 / ACCESS

Lower the barrier.

Give engineers, researchers and learners a credible route into end-to-end private 5G and AI-RAN experimentation.

02 / EVIDENCE

Preserve the truth.

Separate measured state from inference, keep provenance visible and never manufacture a network measurement.

03 / AUTHORITY

Keep humans in control.

Use intelligence to explain and propose while policy, approval and outcome verification remain explicit.

02 / PLATFORM

An open 5G LAB

from live core state
to defensible decisions.

Built through real integration and repeated testing, open OSS gives engineers a coherent path from observation to evidence, and from evidence to carefully governed action. The interface stays calm while the network stays visible.

OBSERVEsee the network.

live topology, functions, gNBs, UEs, sessions, logs and KPIs.

UNDERSTANDpreserve context.

relate a condition to its cell, subscriber, slice, policy, maintenance state and source evidence.

DECIDEinspectable reasoning.

AI-assisted conclusions retain priorities, confidence, evidence links and explicit unknowns.

CONTROLkeep authority deliberate.

simulation, approval, guarded execution, verification and audit remain distinct operator decisions.

open | oss

click to enlarge

03 / CAPABILITIES

ONE SYSTEM · FOUR RESPONSIBILITIES

everything needed to
operate the lab.

01

live operations

a single operational surface for network state, core functions, inventory and current service conditions.

Overview
11 core functions
Network + cells
Live logs

02

service context

the relationships behind a condition remain visible—from signalling and sessions to policy and slice context.

Signalling
Subscribers
Sessions + DNN
Slices + policy

03

assurance

operational changes become inspectable cases supported by scoped measurements and correlated evidence.

KPI Studio
Alarm Intelligence
Threshold profiles
Maintenance

04

controlled action

recommendations, approvals and lab changes are separated so authority never becomes implicit.

AI Operator
Decision evidence
Change planner
Guarded Safe OAM

04 / INTELLIGENCE

AI OPERATOR · SUPERVISED

ask naturally.
get answers from evidence.

ready

AI OPERATOR / LIVESUPERVISED

OPERATOR

Hey, how is the network performing today?

EVIDENCE READY

The core is healthy and all 11 discovered functions are running. One registered-UE threshold incident requires review. Radio performance remains UNKNOWN until real RAN measurements are exposed.

OPEN INCIDENTVIEW KPIEXPORT EVIDENCE

01 PRIORITY03 SOURCES00 ACTIONS EXECUTED

01observe

collect the current state

02explain

build an evidence-backed case

03recommend

rank bounded responses

04authorise

apply policy and approval

05verify

measure and retain outcome

05 / ARCHITECTURE

A CONTROLLED DECISION SYSTEM

One contract.
Explicit boundaries.

CURRENT VALIDATED DATA PATH

01 / SOURCEOpen5GS

metrics · information API · logs · processes

02 / ADAPTERopen OSS Agent

discovery · normalisation · REST · live streams

03 / OPERATIONSopen OSS

context · assurance · intelligence · authority

raydeo | terminal hosts and presents the 5G lab. open OSS connects directly to the Agent; the application never invents a missing network interface.

01 / EVIDENCE

evidence plane

Health, inventory, signalling, logs and measurements with source provenance and time-aligned scope.

02 / OPERATIONS

context plane

Assurance, thresholds, alarms, maintenance and subscriber relationships turn observations into cases.

03 / REASONING

decision plane

Advisor and AI Operator interpret evidence, preserve unknowns and produce inspectable proposals.

04 / AUTHORITY

control plane

Policy, operator approval, guarded Safe OAM, audit and outcome verification bound every change.

06 / EVIDENCE

TRUTH BEFORE AUTOMATION

evidence that survives
the live moment.

operational work is only defensible when another engineer can understand what happened, which source reported it, what the operator decided and how the outcome was measured.

01

source provenance

each observation remains attached to its real source, scope and collection time.

02

honest availability

when a platform does not expose a measurement, open OSS reports NOT EXPOSED rather than creating a substitute value.

03

refresh-safe work

selections, cases and operator input are protected while live state continues to refresh.

04

portable evidence

Iincident, KPI and decision evidence can be retained and exported for review outside the live workspace.

PRIVACY-AWARE OPERATIONS

useful subscriber context without casual exposure.

the Subscribers workspace masks SUPI, SUCI and assigned addresses, uses stable opaque references and still preserves the operational relationships needed to inspect registration, connection, cell, session, DNN and slice state.

Masked identities
Stable references
Refresh-safe selection
Controlled CSV export

BUILD RECORD

JULY 2026 · VALIDATED ITERATION

v0.3Live core

real Open5GS discovery and 11-function topology

PASS

v0.8Assurance

complete inventory, history and operational events

PASS

v0.13Scoped KPI

network, cell, slice, DNN and UE observations

PASS

v0.21Incidents

evidence-backed threshold and alarm workflow

PASS

v0.26Subscribers

privacy-aware subscriber and session context

PASS

v0.29AI Operator

supervised priorities, evidence and proposals

PASS

v0.32Conversation

natural questions grounded in live network truth

PASS

07 / RESEARCH

AI-RAN RESEARCH

challenge the network
before reality does.

CURRENT FOCUS

AI-for-RAN

Use AI to improve assurance, optimisation, operational efficiency and fault understanding.

ACTIVE

SHARED COMPUTE

AI-and-RAN

Study orchestration where AI and RAN workloads share infrastructure and resources.

RESEARCH PATH

EDGE WORKLOADS

AI-on-RAN

Explore AI applications hosted close to users and real-time radio data.

RESEARCH PATH

R&D

private 5G network.

srsRAN gNBLibreSDR B210Open5GSReal UE

Standards position

O1, R1, A1 and E2 are valid future integration paths where the required O-RAN components exist.

AI-RAN Alliance O-RAN Alliance Open5GS srsRAN

08 / DOCUMENTATION

LAB DOCUMENTATION

Connect the lab.
Keep every boundary visible.

real handset → real RF → real gNB → real 5G core → real evidence → AI operator

END-TO-END NETWORK / PHYSICAL LAB TARGET SOFTWARE VALIDATED · RADIO PATH FINAL VALIDATION PENDING

01 / DEVICE Real UE programmable USIM · specific 5G SA UE

02 / AIR NR radio Isolated or authorised spectrum · matched band

03 / RF LibreSDR B210 USB 3.0 · UHD/B200-compatible path · reference clock

04 / RAN srsRAN gNB Linux host · CU/DU · PHY/MAC/RLC · scheduler

05 / 5GC Open5GS Docker · AMF/SMF/UPF · subscriber and session state

06 / EVIDENCE open OSS Agent Processes · logs · metrics · infoAPI · REST/SSE

07 / OPERATIONS open OSS Assurance · KPI · alarms · evidence · AI Operator

N2 / NGAP srsRAN gNB → Open5GS AMF

SCTP · PORT 38412 · CONTROL PLANE

N3 / GTP-U srsRAN gNB → Open5GS UPF

UDP · PORT 2152 · USER PLANE

OBSERVABILITY Open5GS → open OSS Agent

DOCKER · LOGS · METRICS · INFO API

OPERATIONS API Agent → open OSS

REST + SSE · 127.0.0.1:4780/API/V1

The exact telemetry path

Open5GS in Docker → open OSS Agent → open OSS. raydeo | terminal hosts and presents the 5G Lab, but it is not an additional telemetry proxy. srsRAN connects directly to Open5GS over N2 and N3. Direct scheduler, PHY, MAC or RLC control requires a dedicated srsRAN adapter or an O-RAN RIC path;

DAILY STARTUP / DEPENDENCY ORDER

start from the core and move outward.

Keep Docker and the Raydeo 5G Lab running before the Agent. Start the gNB after the core, attach the UE after the gNB has reached the AMF, and open open OSS once evidence is available.

01
Start Docker Desktop
Confirm the Docker engine is healthy before raydeo | terminal tries to present or manage the lab.

HOST
02
Open raydeo | terminal and load the 5G Lab
Open the Open5GS lab, start its core node and keep raydeo | terminal available as the lab envelope.

LAB
03
Confirm the Open5GS container
The Agent discovers the running core container whose name contains raydeo-5gs-core.

DOCKER
04
Start the open OSS Agent
Run it on the Docker host, not inside the core container. Verify health and capabilities on port 4780.

REST + SSE
05
Start srsRAN gNB
Confirm N2 reaches the AMF and wait for an AMF connection before troubleshooting the RF path.

N2 + N3
06
Attach the real UE
Use a provisioned test USIM, aligned PLMN/TAC/slice/DNN and a legal isolated radio setup.

5G SA
07
Start open OSS and validate Settings
Set the Agent URL to http://127.0.0.1:4780/api/v1, select Validate API, then open Overview.

OPERATIONS

01 / COREConfirm Open5GS is running

docker ps --filter "name=raydeo-5gs-core" \
  --format '{{.Names}}\t{{.Status}}'

02 / AGENTInstall, inspect and start

cd <OPEN_OSS_RELEASE>/open-oss-agent
npm install
npm run check
npm run discover
npm start

03 / APIVerify health and capabilities

curl -s http://127.0.0.1:4780/api/v1/health \
  | python3 -m json.tool
curl -s http://127.0.0.1:4780/api/v1/capabilities \
  | python3 -m json.tool

04 / OPEN OSSInstall, check and start

cd <OPEN_OSS_RELEASE>/open-oss-main-layout
npm install
npm run check
npm start

05 / EVENTSWatch assurance events

curl -N http://127.0.0.1:4780/api/v1/events/stream

06 / LOGSWatch the AMF stream

curl -N http://127.0.0.1:4780/api/v1/logs/amf/stream

Remote access

The Agent binds to 127.0.0.1 by default. For a separate open OSS machine, use a strong token, TLS reverse proxy and restricted origin. Never expose the development API directly to the public internet.

SRSRAN PROJECT / OPEN5GS / LIBRESDR

add real radio at the core boundary.

srsRAN Project supplies the gNB. It connects to the Open5GS AMF over N2/NGAP and the UPF over N3/GTP-U. Once Open5GS sees the gNB, UE and PDU session, the existing Agent can expose that core-side evidence to open OSS.

N2 / NGAPgNB → AMFSCTP · 38412

N3 / GTP-UgNB → UPFUDP · 2152

RFgNB → LibreSDRUHD · TYPE=B200

DEVICEReal UE

→

RFLibreSDR

→

RANsrsRAN gNB

→

5GC + OSSOpen5GS → OSS

01

Choose a routable topology

Native Linux is the cleanest radio host. It must reach the AMF N2 address and UPF N3 address. Docker Desktop introduces a VM boundary, so never assume internal container addresses are reachable externally.

02

Align network identity

Match PLMN, TAC, S-NSSAI and DNN between srsRAN, Open5GS and the test USIM. Add the UE credentials to Open5GS before attachment.

03

Connect and clock RF

Connect LibreSDR over USB 3.0, confirm UHD discovery and use a suitable external clock where the lab requires it. Set band, ARFCN and sample rate for the authorised test setup.

04

Start in dependency order

Start Open5GS first, then the gNB, then the UE. Confirm the gNB reports an AMF connection before diagnosing UE registration.

GNB CONFIGURATION TEMPLATEReplace every angle-bracket value

cu_cp:
  amf:
    addr: <OPEN5GS_AMF_NGAP_IP>
    port: 38412
    bind_addr: <GNB_N2_IP>
    supported_tracking_areas:
      - tac: <TAC>
        plmn_list:
          - plmn: "<MCCMNC>"
            tai_slice_support_list:
              - sst: 1

ru_sdr:
  device_driver: uhd
  device_args: type=b200

START + CORE-SIDE VERIFYPaths vary with the srsRAN build

sudo ./build/apps/gnb/gnb \
  -c configs/<your-gnb-config>.yml

curl -s http://127.0.0.1:4780/api/v1/gnbs \
  | python3 -m json.tool
curl -s http://127.0.0.1:4780/api/v1/ues \
  | python3 -m json.tool

Current boundary

open OSS currently sees radio state through Open5GS evidence. It digests srsRAN scheduler, PHY, MAC and RLC telemetry.

REAL HANDSET / TEST USIM

make every identity agree before touching RF.

The handset, programmed test USIM, srsRAN cell and Open5GS subscriber record are one system. Most failed first attachments are identity, routing or radio configuration mismatches—not an OSS problem.

01

provision the test USIM

Program the lab IMSI/SUPI, AMF, K and OP or OPc. Use test credentials only and store them outside screenshots, repositories and exported evidence.

02

add the subscriber

Create the matching subscriber in Open5GS. Align APN/DNN, IPv4 session type, S-NSSAI and any AMBR settings used by the lab.

03

configure the handset

Insert the test USIM in slot 1, enable 5G SA and roaming, add the matching APN, disable VoLTE/VoNR if it blocks testing, then use NR-only or manual carrier selection.

04

Attach and observe

Start the gNB first. Ask the handset to find the lab carrier, then watch AMF registration, SMF session creation and UPF address allocation in order.

RF and SIM safety

Operate only in licensed or properly isolated test spectrum, with suitable attenuation or shielding. A programmable test USIM and known lab credentials are required; do not repurpose a consumer operator SIM.

END-TO-END ACCEPTANCE

prove the chain one boundary at a time.

Do not begin with dashboards. Establish transport, registration and session evidence first; then confirm the Agent preserves it and open OSS presents it without inventing unavailable radio measurements.

OPEN5GS INFO API + AGENTInspect real gNB, UE and PDU evidence

curl -s http://<AMF_IP>:9090/gnb-info
curl -s http://<AMF_IP>:9090/ue-info
curl -s http://<SMF_IP>:9090/pdu-info

curl -s http://127.0.0.1:4780/api/v1/gnbs
curl -s http://127.0.0.1:4780/api/v1/ues
curl -s http://127.0.0.1:4780/api/v1/sessions

01gNB N2 association reaches the AMFTRANSPORT
02UE registration completes in the AMFCONTROL
03PDU session activates and an address is allocatedUSER PLANE
04Agent exposes gNB, UE and session evidenceADAPTER
05open OSS shows signalling and relationshipsOPERATIONS
06AI Operator explains from evidence and preserves unknownsAUTHORITY

Evidence rule

A missing RF metric remains NOT EXPOSED. Core-side registration or session state is not a substitute for RSRP, SINR, BLER, PRB use or scheduler telemetry.

srsRAN real COTS UE guide srsRAN gNB configuration Open5GS gNB / UE / PDU infoAPI Open5GS metrics reference

09 / MEMBERS

OPEN OSS MEMBERSHIP

help build
what comes next.

Join the early open OSS community, membership is free during the validation phase and is for people interested in practical 5G, Open5GS, srsRAN, assurance and accountable AI-RAN research.

01Receive meaningful project and release updates
02Hear about validation and early-access opportunities
03Share the areas where you want to contribute or learn

Become an open OSS member

Tell us where your interests meet the project.

FREE / VALIDATION PHASE

Full name

Email address

Organisation / optional

Primary interest

How would you like to be involved?

A short note / optional

You will receive an email acknowledging your registration. No payment or account password is required.

build an AI-RANresearch laboratory

serious lab work.made accessible.

Lower the barrier.

Preserve the truth.

Keep humans in control.

from live core stateto defensible decisions.

everything needed tooperate the lab.

live operations

service context

assurance

controlled action

ask naturally.get answers from evidence.

One contract.Explicit boundaries.

evidence plane

context plane

decision plane

control plane

evidence that survivesthe live moment.

source provenance

honest availability

refresh-safe work

portable evidence

useful subscriber context without casual exposure.

challenge the networkbefore reality does.

AI-for-RAN

AI-and-RAN

AI-on-RAN

private 5G network.

Connect the lab.Keep every boundary visible.

start from the core and move outward.

add real radio at the core boundary.

Choose a routable topology

Align network identity

Connect and clock RF

Start in dependency order

make every identity agree before touching RF.

provision the test USIM

add the subscriber

configure the handset

Attach and observe

prove the chain one boundary at a time.

help buildwhat comes next.

Become an open OSS member

Build. Validate.Prepare for release.

build an AI-RAN
research laboratory

serious lab work.
made accessible.

from live core state
to defensible decisions.

everything needed to
operate the lab.

ask naturally.
get answers from evidence.

One contract.
Explicit boundaries.

evidence that survives
the live moment.

challenge the network
before reality does.

Connect the lab.
Keep every boundary visible.

help build
what comes next.

Build. Validate.
Prepare for release.