Java licensing for telecommunications companies.

Telecommunications is one of the most Java-intensive industries in existence. The operational and business support systems that run a carrier — provisioning, billing, mediation, network management — are heavily Java-based, and they have been for decades. Combine that deep technical dependence with the enormous workforces telcos carry, and Oracle's employee-based Java metric produces some of the largest licensing exposures of any sector.

Why telcos face outsized Java costs

Two factors compound. First, telcos genuinely run a lot of Java — far more than most enterprises — so the probability of Oracle JDK being present somewhere in the estate is close to certain. Second, telcos employ very large numbers of people: network engineers, retail staff, call-centre agents, field technicians, installation crews and back-office teams, frequently numbering in the tens of thousands.

The Java SE Universal Subscription is priced on that second number. It does not matter that the Java footprint, however large in technical terms, is operated by a comparatively small group of OSS/BSS and network specialists. The metric counts the whole workforce. A carrier with 40,000 employees is licensed as a 40,000-employee organisation regardless of how its Java is actually used. For an industry that runs Java more intensively than almost any other, the metric manages to make the bill depend on the one thing — headcount — that has nothing to do with that intensity.

Java in OSS and BSS platforms

To understand telco Java exposure you have to understand where the Java lives. The carrier-grade systems that keep a network running and a business billing are overwhelmingly Java:

• Operational Support Systems (OSS). Network inventory, service provisioning, fault and performance management, and activation platforms are classic large-scale Java applications.
• Business Support Systems (BSS). Billing, charging, mediation, rating, customer relationship management and order management platforms typically run on Java back ends.
• Mediation and integration layers. The middleware that moves call-detail records and network events between systems is a heavy Java workload.
• Network management platforms. Element and network management systems from major equipment vendors frequently embed or require Java.
• Self-service and dealer portals. Customer and channel-facing platforms often sit on Java application servers.

The licensing risk is that this Java is spread across systems owned by different teams, supplied by different vendors, and built over many years. A complete map rarely exists. Yet a single Oracle JDK requiring a subscription — in any one of these platforms — obliges the entire employee count. Comprehensive discovery is the non-negotiable starting point.

The employee metric and telco headcount

Oracle's definition of "employee" is what makes the telco number so large. The Universal Subscription counts all full-time, part-time and temporary employees, plus agents, contractors, consultants and outsourcers who support internal operations. Telcos are structurally exposed to every one of those categories:

• Retail and call-centre staff — large populations that never touch a Java application but are fully counted.
• Field and installation technicians — often a substantial fraction of total headcount.
• Contractors and temporary staff — heavily used for network build-out and seasonal demand.
• Outsourced functions — call centres, field services and network operations are frequently outsourced, and outsourcer staff supporting internal operations can fall within the count.

The result is that a telco's countable figure is often close to its full operational scale — precisely the number that has the least to do with how much Java the OSS/BSS estate actually runs.

Outsourced network operations

Telecoms outsource more aggressively than most industries, and network operations in particular — managed services where a third party runs significant parts of the network — create a specific licensing question.

Two issues arise. First, the headcount question: do the outsourcer's staff who support the carrier's internal operations count toward the employee metric? Oracle's definition can pull them in, and the answer depends on the precise nature of the arrangement — which makes the contract scope worth real scrutiny rather than acceptance of Oracle's first figure. Second, the deployment question: when an outsourcer runs Java-based network management on the carrier's behalf, whose licensing responsibility is the Oracle JDK that the outsourcer installed? The answer should be written into the managed-services contract explicitly. Where it is not, the carrier is exposed to a liability created by a third party's choices — a genuinely avoidable risk that good contract drafting closes.

Embedded Java in network equipment

Network equipment — routers, switches, base stations, optical gear — and its associated element-management software frequently contains Java. As with embedded Java in any product, this is generally licensed through the equipment vendor's redistribution arrangement with Oracle: the Java embedded in a vendor's appliance or firmware is the vendor's licensed component.

The carrier's task is to draw the boundary clearly. Embedded Java inside vendor equipment is one thing; an Oracle JDK that the carrier itself installs on a management server, a jump host or an operations workstation to interact with that equipment is another — and the second is the carrier's exposure. For every major equipment vendor, confirm in writing that bundled and embedded Java is covered by the vendor's distribution rights, and separately inventory any Oracle JDK the carrier has installed itself.

A worked telco cost example

Consider a carrier with 35,000 employees — network, retail, call-centre, field and back-office staff combined. Its Java estate is substantial: a major BSS billing platform, several OSS systems and a mediation layer. The teams that operate this estate number perhaps 600 people.

Under the employee metric: 35,000 employees fall into the 30,000–39,999 band at roughly USD 5.70 per employee per month. That is approximately USD 199,500 per month, or about USD 2,394,000 per year. The carrier pays nearly USD 2.4 million annually to license Java for an estate operated by 600 specialists.

The alternative: migrate the OSS/BSS Java estate to free OpenJDK distributions and confirm that vendor-embedded Java carries no separate carrier obligation. Because the OSS/BSS platforms are server-side and centrally managed, the great majority of the estate is migratable. Across our 340-plus Java engagements — contributing to more than USD 180 million in client savings — telco clients have seen seven-figure annual reductions from exactly this move.

Audit exposure for telecoms

Telcos are high-value audit targets: large headcounts mean large potential claims, Java-dense estates mean Oracle JDK is genuinely likely to be present, and complex multi-vendor environments mean carriers rarely have complete self-knowledge. Common pressure points include:

• Download telemetry — Oracle JDK downloads logged against the carrier's accounts, a frequent soft-audit trigger.
• Legacy version sprawl — long-lived OSS/BSS systems running old Java 8 builds, many under post-2019 update terms requiring a subscription.
• Self-disclosure — soft-audit questionnaires answered without a verified inventory, routinely overstating exposure.

The defence is disciplined: a complete, evidence-based inventory of every Oracle JDK in the estate, an accurate read of which licence each build falls under, clear separation of vendor-embedded Java from carrier-installed Java, and careful handling of Oracle's questions. That preparation is what produces our 68 percent average claim reduction — see Java audit defence, backed by a money-back guarantee.

Migration without disrupting the network

The instinctive fear — that swapping the Java runtime under a carrier-grade system risks the network — overstates the difficulty. Free OpenJDK distributions (Eclipse Temurin, Amazon Corretto, Azul Zulu) are built from the same OpenJDK source as Oracle's JDK and are, for the overwhelming majority of workloads, a drop-in replacement. The telco-specific approach is about sequencing and assurance, not technical risk:

• Start with non-critical and back-office Java — fast, low-risk wins that build confidence.
• Engage OSS/BSS vendors early — confirm which OpenJDK distributions each platform vendor supports, so support contracts are preserved.
• Treat carrier-grade systems as controlled changes — full test coverage, performance validation and staged rollout for billing and provisioning platforms.
• Sequence around network and billing cycles — avoid bill-run windows and known high-demand periods.

See our migration planning steps and testing strategy for the detailed mechanics.

Frequently asked questions

Why is Java so expensive for telcos specifically?

Because telcos combine intensive Java use with very large workforces. The employee metric prices Java on headcount, so a big workforce produces a big bill regardless of how the Java estate is actually operated.

Do call-centre and retail staff count toward the metric?

Yes. The employee metric counts every employee — including retail, call-centre and field staff who never use Java. Usage is irrelevant to the calculation.

Do outsourced network operations affect our Java count?

They can. Outsourcer staff supporting internal operations may fall within Oracle's definition, and an outsourcer's Oracle JDK deployments can create carrier exposure. Both points should be addressed explicitly in the managed-services contract.

Is the Java in our network equipment our responsibility?

Embedded Java in vendor equipment is generally the vendor's, through their distribution arrangement — but confirm it in writing. Any Oracle JDK the carrier installs itself, on management servers or workstations, is the carrier's exposure.

Can we migrate carrier-grade OSS/BSS systems off Oracle Java?

Yes. Free OpenJDK is technically equivalent to Oracle's JDK. Carrier-grade systems need staged, well-tested migration and vendor support confirmation, but the runtime swap itself is low-risk.

Conclusion

Telecommunications carriers run more Java than almost any industry — and Oracle's employee metric ensures they pay for it on a basis that has nothing to do with that usage. The bill is set by a headcount that includes every retail assistant, call-centre agent and field technician, none of whom will ever launch a Java application. The route out is the same disciplined sequence that works elsewhere: inventory the OSS/BSS estate completely, separate vendor-embedded Java from carrier-installed Oracle JDK, scrutinise how outsourcers affect the count, and migrate the movable estate to free OpenJDK with proper testing. For a carrier, that work routinely converts a multi-million-dollar annual Java cost into something close to nothing — without touching the network.