Orange has published work on intent-based orchestration for Open RAN, using a simulator it calls ib-ORAN to test how automated network management could run across open radio interfaces. The project, detailed on Orange.com, addresses a gap practitioners know well: open interfaces multiply the number of moving parts, and conventional, manually configured management does not scale to match.

The disclosure is a research milestone, not a deployment. No commercial network is running the ib-ORAN simulator's logic today, and Orange has not attached a rollout date to the work. What it offers instead is a testbed — evidence that intent-based principles can be applied to Open RAN environments before an operator commits capital to them.

What is intent-based orchestration?

Intent-based networking lets an operator state a desired outcome — say, maintain throughput on a busy cell — and lets the system work out the configuration. The ib-ORAN simulator models that loop for Open RAN architectures, where the radio unit, distributed unit and central unit may come from different vendors under the O-RAN Alliance's interface specifications.

For engineers, the practical change is this: orchestration moves from box-by-box parameter tuning toward policy-level control. The rapprochement between intent systems and the O-RAN RAN Intelligent Controller architecture is the standards context here. Orange's simulator work sits directly on that seam.

Why a simulator first?

Open RAN's multi-vendor promise carries an orchestration cost. Each added interface widens the attack surface for configuration errors and performance drift. Simulating intent workflows lets Orange measure how automated closed loops behave — how quickly they converge, how they handle conflicting intents — without touching live traffic.

That is a familiar pattern across the industry. Operators including Telefónica, Vodafone and Deutsche Telekom have run comparable Open RAN labs and trials before field deployments. Orange's contribution targets the orchestration layer specifically, the piece most operators identify as the hardest to industrialize.

What changes for practitioners?

Three things follow from this work if it matures into production tooling:

• Network operations teams would define service-level intents rather than device parameters.
• Multi-vendor RAN management could consolidate under a single orchestration domain.
• Verification of vendor compliance with intent policies becomes testable in software before procurement.

The commercial reality remains cautious. Vendor marketing around Open RAN has long emphasized flexibility; the orchestration burden that flexibility creates is the counterweight, and it is the problem Orange is probing.

What comes next?

Orange has not disclosed a timeline for moving ib-ORAN concepts beyond simulation, nor named partner vendors for the work. The operator's broader Open RAN program, however, continues to progress through its European market footprint, and intent-based orchestration is positioned as a prerequisite for scaling it — a signal worth tracking as Orange's next network announcements land.