Core network integration
Design, integration and acceptance of 5G SA core, EPC and IMS, from first call to production cut-over.
Telecom engineering · Software · Germany
Nerdwerk started inside operators' core networks, where legacy, hardware-bound test tools couldn't keep up with software-defined 5G. So we built our own: Teuphon, a cloud-native platform that loads your 5G core and IMS like hundreds of thousands of real phones.
Professional services
Operators, vendors and system integrators bring us in when a core network has to be integrated, tested or migrated on a deadline. That field work is where our products come from.
Design, integration and acceptance of 5G SA core, EPC and IMS, from first call to production cut-over.
Functional, interoperability, load and regression testing, with test plans and automation that stay with your team.
Integration of mission-critical communication services for transport and public safety networks.
Experienced engineers for defined project scopes, on site or remote, managed against agreed deliverables.
How we build
Every Nerdwerk tool starts as a problem we hit on a customer project. We only package it once it has proven itself in a lab.
On integration projects we see where networks break: overload, misconfiguration, interop gaps between vendors.
We rebuild those conditions in a lab, script them and measure them, until the behaviour is repeatable.
What works becomes software: cloud-native, browser-based and transparent about every component inside it.
Product
Software that behaves like hundreds of thousands of phones, so operators can test their network before real customers do.
Emulates large numbers of phones and the radio sites they connect through, and sends their traffic into your real core network.
Prove capacity, stability and failover before a launch or upgrade, without touching live customers.
5G registration and data, voice and video calls (VoNR / ViNR) with supplementary services, and mission-critical push-to-talk (MCPTT).
Pure software on standard x86 or ARM64 servers in your own data centre, operated entirely from a web browser.
Measured in the Nerdwerk lab. Scale further by adding load agents: roughly one agent per 100,000–125,000 voice subscribers, with one manager for all agents.
Your 5G core and IMS under realistic load, across eight areas.
Maximum subscribers, busy-hour call attempts, messages/s and packets/s limits.
VoNR / ViNR set-up success, post-dial delay (P50 / P99), MOS and answer rate.
Registration, authentication, internet and IMS data sessions, QoS flows and slicing.
Hold and resume, call forwarding and barring, with IPsec signalling and SRTP media.
Signalling storms, mass re-attach after an outage, geo-redundancy and disaster recovery.
MCPTT registration, group affiliation, private and group calls, floor control.
Internal and external DoS situations, and how the core protects itself under overload.
Vendor acceptance and regression suites, sanity checks, and a REST API for CI pipelines.
Scenarios are plain configuration files. No programming required: edit the JSON directly and keep it in version control.
Attach, data, VoNR hold or forwarding, ViNR and more from the Scenario Library.
Edit the steps, targets and load in the JSON scenario file.
The scenario appears in the library, ready to run or to call from the REST API.
Live phones, sessions, messages/s and media per agent.
A one-page result with 3GPP TS 28.554 KPIs, plus PDF.
// the four sections of a scenario (simplified) "targets": AMF and P-CSCF addresses "subscribers": number ranges + SIM credentials "workload": target rate, max phones, duration "workflow": [ 5G_REGISTER, PDU_SESSION_ESTABLISH, WAIT "5s", DYNAMIC_FLOW // VoNR call ]
Current 3GPP reference-point support. Interfaces marked "project dependent" extend the same protocol engine and are delivered with customer projects.
| Interface | Status | Coverage |
|---|---|---|
| N1 / N2 | Ready | UE ↔ AMF and gNB ↔ AMF: registration, PDU session, handover and de-registration signalling |
| N3 / N9 | Ready | GTP-U user plane: uplink and downlink traffic, QoS flow / QFI classification |
| Gm | Ready | UE ↔ P-CSCF: IMS registration (SIP / IMS-AKA), VoNR and ViNR call set-up and control |
| Gx · Rx · S6a · Sh | Ready | Diameter, on the same core protocol engine |
| MC signalling | MCPTT ready · rest in development | UE ↔ MCX server: MCPTT group affiliation, floor control, private and group calls; MCData and MCVideo in development |
| N4 · N7 · N8 · N10 · N12 · N13 | Project dependent | 5G core internal interfaces (SMF, PCF, UDM, AUSF): full nodal simulation |
| Mw / ISC | Project dependent | Inter-CSCF and application-server interworking on the existing SIP / IMS stack |
Next on our roadmap: a digital twin of your 5G network, combining load, fault injection (Faultix chaos engine) and security testing. We're looking for operator and research partners for early pilots.
In development250,000+ subscribers validated in the lab. Need more? Add load agents.
Nothing to install, patch or license on the client. Open it from any laptop, on any operating system.
Plain JSON scenario files. New call flows are message templates, not new software.
Developed in Germany and deployed entirely inside your data centre. Licences are checked offline, with no licence server.
Contact
Whether it's an integration project, a Teuphon POC or a Twinstrike partnership, write to us and an engineer will reply, not a sales script.