SAS domain proxy integration
Connect a radio estate to a Spectrum Access System through a domain proxy: registration, grant, heartbeat and relinquish flows, certificate handling and the failure paths that only show up under load.
telecogeco is the content-led telecom brand of ugeco: training and in-house products for the people who build open RAN, 5G core and spectrum systems. The engineering it teaches is the work ugeco delivers: integrating radios with open DUs, connecting spectrum access systems, evaluating cores, building the test rigs that keep it all honest, and putting intelligence on top through a RIC. The closed-loop demo is published in the ugeco open-source org, so you can check it before you call.
Working software, published
A closed loop from an energy-saving rApp on the Non-RT RIC, over O1 and the WG4 M-Plane, to a ruApp that decides inside the radio. Runs on a laptop.
Read the whitepaperA TR 38.901 physics twin behind a small HTTP service. Ask it what changes when you tilt an antenna or put a cell to sleep.
Read the whitepaperThe AI-RU closed loop, published in the ugeco open-source org as ocp-auRu.
github.com/ugeco-opensource/ocp-auRuWhere we work
Most telecom projects fail at the boundaries between boxes from different vendors, not inside them. That is the part we specialise in: the protocol seam, the timing domain, the management plane and the test that proves the two sides agree.
SAS proxy integration, OpenSAS certification
Open M-Plane on the RU, split 7.2 and split 8 bring-up
OCUDU with the M-Plane, system integration
core evaluation, load testing
integrate a RIC, write rApps
Services
Each engagement is scoped in writing before it starts, run by the engineers who do the work, and handed over with the rig, the scripts and the evidence. Where a piece can be open source, it is.
Connect a radio estate to a Spectrum Access System through a domain proxy: registration, grant, heartbeat and relinquish flows, certificate handling and the failure paths that only show up under load.
Stand up OpenSAS as the reference SAS, script the WInnForum test cases against your CBSD or proxy, and produce the evidence pack a certification lab expects.
Give an open DU and CU a working management plane: NETCONF client, YANG models, carrier configuration, alarms and supervision against a real or emulated O-RU.
Bring a radio unit onto the O-RAN management plane with Open M-Plane: call-home, get-config and edit-config, software management and the sync state a DU needs before a carrier goes live.
Fronthaul timing, C/U-plane checks, and custom radio drivers when a software-defined radio does not speak eCPRI.
Put a candidate core through registration, session, mobility, failover and throughput on a documented rig, and report what it does, not what the datasheet says.
Radios, DU and CU, core, timing and management from more than one vendor, wired into one working network with every seam captured and every version pinned.
A short, fixed-scope review of an existing deployment or lab: configuration, timing, security posture, observability and the gaps that will bite next quarter.
Control-plane rate, user-plane throughput and soak on N2, N3 and F1 with TRex, iperf3, PacketRusher and commercial rigs where they earn their cost. Results labelled by rung: simulator, real RF or scale.
A harness that runs on every merge: simulator in CI, a reserved bench for the radios, pcap assertions at the seams, and evidence attached to every failure.
O-RAN and 3GPP subsets run in your lab before the OTIC visit, so the certification run is a formality.
Connect a Non-RT or Near-RT RIC to your RAN over O1, A1 and E2, with the SMO plumbing and the policy path exercised end to end.
Energy saving, coverage guardrails, KPI-driven policy. ugeco built and published a closed loop from an rApp to a radio; we can build yours.
And more. If the work sits anywhere between a SIM card and a data network, from a YANG model to a scheduler patch, describe it to us and we will tell you plainly whether it is something we can do well.
How we work
A setup audit or an evaluation on a documented rig. We read the configs, capture the seams, run the procedures and write down what we find, including the things that are fine.
You get: a written report, the captures, and a scoped proposal if there is work to do.
The feature, the driver, the M-Plane client, the rApp. Delivered against acceptance criteria agreed up front: which procedures, on which rung, at which threshold.
You get: working code, the test that proves it, and a runbook your team can follow without us.
The harness that runs on every merge, the lab that provisions from code, and an engineer who already knows your network when the next release lands.
You get: a green pipeline you own, and someone to call.
Writing
Long reads for engineers learning telecom, and whitepapers on the proofs of concept telecogeco has built. Every card opens the complete piece on telecogeco.com. All writing from our brands
An open closed loop from a Non-RT RIC energy-saving rApp, over O1 and the WG4 M-Plane, to a ruApp that decides inside the radio. The demo, the physics twin, the rApp training and the ruApp, animated.
Read on telecogecoHow a TR 38.901 propagation model becomes a service that predicts coverage across a cluster of cells, calibrates to measurement data, and tells you what changes when you tilt an antenna or put a cell to sleep.
Read on telecogecoHow a CBRS grant is issued by a SAS, carried by a Domain Proxy, turned into carrier configuration in the CU/DU, and written into an O-RAN radio over M-Plane. A runnable lifecycle lab: register, get granted, get authorized, and watch what an incumbent detection or a grant termination actually does to the radio.
Read on telecogecoA working course for engineers who test RAN and core. Levels, types, techniques and tools, all mapped onto one system: a UE talking through an O-RU, O-DU and O-CU into a 5G core.
Read on telecogecoYou know AMF, SMF and UPF. This walks the other way, from a phone's first transmission through the radio unit and the gNB, and explains split 7.2 versus split 8, the four fronthaul planes, and what a radio driver actually does.
Read on telecogecoAbout
ugeco is an AI-first product and services company. telecogeco is its telecom brand: the lab and the open-source projects that deal with radios, cores and spectrum. The two share one rule: a claim is worth exactly as much as the working system behind it.
Provenance: the telecogeco open-source work is pre-existing, independently developed intellectual property maintained by ugeco, licensed Apache-2.0, with independent authorship stated in the README. The code stays open and free. Platform-specific work is scoped and paid.