Building a PON is complex. Operating it is where the real work begins.
Selecting hardware, mastering OMCI, integrating ONUs from different vendors, migrating and meeting documentation requirements. We support you along this path with a modular stack and open interfaces. You do not buy a chassis in advance to fill later.
What do you need?
We start with the important operational questions: how does this impact my installed base? How do I migrate? Who helps?
Components & configuration
You choose the switch platform, computing capacity, PON module and management independently. The configurator turns your requirements into a proposal for a suitable implementation.
- OLT as a pluggable module
- Dimensioning and datasheets
Operations & migration
Network planning, deployment, day-to-day operation, GPON to XGS-PON migration and regulatory obligations
- GPON to XGS-PON without a break
- SBOM and CRA reporting process included
Interoperability & testing
ONUs from different vendors and generations are the most common reason PON integration takes time. The BISDN Lab in Berlin tests your devices against the stack.
- Your ONUs tested against the stack
- Testing in the BISDN Lab, including remotely
Support
From procurement to production, with direct access to the developers who built the stack. In German and English, from Berlin.
- Single point of contact
- Direct access to the developers
From planning to migration, without disruption.
Selecting an OLT is the beginning. Planning your deployment, rolling it out, operating it day to day and migrating from GPON to XGS-PON is the work that counts.
- Network planningWe design the split ratio, fibre budget and site locations together before hardware is ordered.
- DeploymentRemote OLTs up to 80 km from the headend, followed by up to another 20 km of PON. In sparsely populated areas, a small site with low power consumption and remote maintenance is sufficient.
- Day-to-day operationConfiguring network and services in a single flow. Joint PON and service visibility.
- Migration GPON to XGS-PONCombo modules carry both standards. The migration happens when you and your customers are ready.
- Regulatory evidenceAn SBOM, a documented vulnerability reporting process and patch delivery, designed to meet CRA obligations from December 2027.
GPON delivers 2.5 Gbit/s downstream, shared by up to 32 customers. XGS-PON delivers 10 Gbit/s at the same split ratio, four times more per customer and, unlike GPON, symmetrically. Because the PON module is pluggable, migration takes place port by port at the existing node. The fibre stays as it is.
Configuring the network and services separately is the most common source of errors in PON operations. A shared observability framework for PON and BNG shortens the search for the cause of alarms. The technician travels to make repairs, rather than to diagnose the problem.
Your installed base decides, not our datasheet
Different ONU vendors, generations and OMCI quirks: the BISDN Lab and testing as a service simplify the process.
Bring an ONU, leave with a test report. Vendors, carriers and distributors bring their setups. We integrate, test and document what works with the stack, including remotely.
Externally, the OLT behaves like one with built-in OMCI. Those who want to control the OMCI parameters themselves also get the vOMCI interfaces based on TR-451. Nightly test pipelines continuously check the curated components.
The lab does more than testing. It also provides system design and integration support until interoperability is achieved.
| ITU-T G.9807.1 | XGS-PON 10G met |
| ITU-T G.984 | GPON (Option) met |
| BBF TR-383 / 385 | PON NETCONF/YANG met |
| BBF TR-451 | vOMCI-Framework met |
One team across every layer, no portal.
Components, operations and interoperability are interdependent. The value comes from having one point of contact who brings them together, with direct access to the developers who wrote the stack.
From selection to operation. We accompany component selection, set the stack up in your environment and stay your point of contact once it runs. In German and English, from Berlin.
For operators and institutions this means: you don't have to commission the stack on your own, we advise and integrate. For hardware manufacturers and distributors: a white-label OLT on the BISDN stack, design, testing and integration from one source.
A test in the BISDN Lab with your own hardware tells you more than any data sheet. This is how most customers start. First demonstrate that your existing equipment works with the stack, then discuss system design and rollout.
Tell us where you stand.
Whether you need component selection, migration or a lab test, the first step is a conversation with a developer.