a ugeco brand
Open RAN, 5G core and spectrum engineering that ships.
telecogeco takes on the work between a standards document and a network that carries traffic: integrating radios with open DUs, connecting spectrum access systems, evaluating cores, building the test rigs that keep it honest, and putting intelligence on top through a RIC. The reference work is open source in ugeco's open-source org, so you can check it before you call us.
- Non-RT RIC · es-rAppthe rApp sets the policy
- SMOover R1
- OCUDU · O-DU and O-CUover O1
- Open M-PlaneNETCONF, o-ran-uplane-conf
- O-RU · ruAppthe carrier sleeps; a local wake on PRACH
- telecogecoTwinPM data comes back to the rApp and the twin
- 2
- whitepapers published
- 4
- blog posts
- 167
- minutes of reading
- Apache-2.0
- source licence
Services
Feature development, integration and assurance for open telecom stacks.
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.
CBRS · SAS · Domain Proxy
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.
SAS certification with OpenSAS
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.
O-RU · eCPRI · WG4 M-Plane
OCUDU integration with the M-Plane
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.
Open M-Plane integration with an 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.
Radio bring-up, split 7.2 or split 8
Fronthaul timing, C/U-plane checks, and custom radio drivers when a software-defined radio does not speak eCPRI.
O-DU · O-CU · 5GC · N2/N3 · SBI
Network core evaluation
Put a candidate core through registration, session, mobility, failover and throughput on a documented rig, and report what it does on that rig.
System integration
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.
Setup audit
A short, fixed-scope review of an existing deployment or lab: configuration, timing, security posture, observability and the gaps that will bite next quarter.
SMO · Non-RT RIC · O1/A1/E2
Integrate a RIC
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.
Write rApps
Energy saving, coverage guardrails, KPI-driven policy. A closed loop from an rApp to a radio is published in ugeco's open-source org; we can build yours.
CI · lab · scale rigs
Load testing
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: simulation, real RF, scale.
Regression suite development
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.
Conformance preparation
O-RAN and 3GPP subsets run in your lab before the OTIC visit, so the certification run starts from passing evidence rather than first findings.
If the work sits anywhere between a SIM card and a data network, from a YANG model to a scheduler patch, describe it in an email and we will tell you plainly whether it is something we can do well.
How we work
Scope first. Build second. Prove it, then hand over.
Five steps, each with a written output. Open a step to read what it delivers.
01 · Scope · A short, fixed-scope look at what you have
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.
Proof
Working software, published.
Two whitepapers, each about a system you can run. The code behind them is open source under Apache-2.0.
The Autonomous AI-RU
An open closed loop from a Non-RT RIC energy-saving rApp, over R1 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 the whitepaper
telecogecoTwin: a physics twin you can ask what if
How 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 the whitepaperWriting
What we learn, written down.
What it takes to build a 5G network
A plain-language explainer of how private and public 5G networks are built: cells, MIMO, handover, and how many radios, basebands and cores a network needs.
Read the post
Spectrum control, hop by hop
How a CBRS grant is issued by a SAS, carried by a Domain Proxy, turned into carrier configuration in the DU and CU, 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 the post
Testing a 5G network, end to end
A 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 the postAbout
telecogeco is a ugeco brand.
ugeco is an AI-first product and services company. telecogeco is its telecom brand: the people, the lab and the open-source work that deal with radios, cores and spectrum. The two share one rule, which is that a claim is worth exactly as much as the working system behind it.
Contact
Have a network, a radio or a spec that needs to work together?
Write to us with what you have and what it should do. We reply with questions.