The Enea API Composition Engine (ACE) is a powerful new solution built on Enea’s highly scalable and reliable telecom framework, trusted by leading service providers worldwide.

Built for Flexibility

Enea ACE enables operators to quickly adapt to evolving requirements without the need for extensive development skills. Its GUI-based configurable logic allows for intuitive use case implementation, where:

• New use cases can easily be added to a system by GUI configuration.
• A rule-set can be configured to fetch data from multiple sources and based on the result apply mobile operatordefined logic.
• Rule-sets can interact with other rulesets (chained rules) and plugins.

This modular approach, combined with a rich selection of protocol adapters, ensures seamless integration with existing systems. Operators can modify deployment logic through configuration rather than developing code, accelerating time to market.

Our flexible architecture also enables the development and integration of new protocol adapters as needed. Furthermore, service providers can upload Open API-based specifications—such as CAMARA APIs—directly into the rules engine, providing an ideal starting point for further logic development.

For advanced or common use cases, Enea’s software engineers can extend functionality by developing software plugins, providing maximum adaptability in an ever-evolving telecom landscape.

Enea ACE in the API Ecosystem

“So, you’re an aggregator?”

That’s a question we’re often asked when people try to place Enea in the API exposure ecosystem. The answer is simple: No, we’re not.

Aggregators play a distinct role by acting as business and technology intermediaries. They manage commercial relationships between mobile operators and enterprises, route API requests, and often bundle additional services beyond pure API exposure—taking a share of the revenue in the process.

The Enea API Composition Engine (ACE) plays a very different role. As a middleware solution, ACE is designed to simplify and streamline southbound integration—the complex task of connecting standardized APIs (like CAMARA) to diverse, siloed, and sometimes legacy backend systems. This need exists regardless of whether a mobile operator exposes APIs directly or relies entirely on aggregators.

Here’s a simplified view of the API exposure ecosystem:

Enterprises – Providers of apps and digital services

• Deliver services via APIs.
• Often need access to multiple MNOs across markets.

Aggregators – Business and integration facilitators

• Manage contracts with MNOs and enterprises.
• Route requests to the appropriate operator.
• Add services such as security, billing, and analytics.
• Take a share of the API revenue.

Mobile Operators – Owners of network capabilities and data

• Must abstract backend complexity from enterprises.
• May interconnect with partner MNOs.
• Need integration flexibility beyond CAMARA, especially to support 2G/3G/4G and legacy systems that NEF doesn’t cover.

This is where Enea ACE excels. It equips mobile operators with the tools to efficiently expose APIs—across all generations of networks—through robust, flexible, and future-proof integration.

Enea ACE – Essential Supporting Capabilities

Beyond logic and flexibility, Enea ACE includes a suite of critical supporting functionalities, which can be extended over time based on customer needs:

• API Management: Authentication, CDR generation (billing), audit logging, and rate limiting.
• API Discovery: Empowers third-party developers to easily discover and use APIs.
• Usage Monitoring: Provides robust tracking to facilitate monetization strategies.
• Cross-Integration: Enables seamless integration with other cloud services to create business processes around APIs.
• Deployment Flexibility: The solution features a cloud-native architecture that leverages microservices, supporting deployment as VNF or CNF.
• Caching: Reduces load on backend systems by storing frequent requests.
• Operations & Maintenance (OAM): Robust tools for system administration including version handling of APIs.
• High Availability (HA): Geo-redundant architecture for maximum reliability.
• Observability & Troubleshooting: Advanced monitoring, testing, and diagnostics.

With its powerful combination of flexibility, scalability, and operational resilience, Enea ACE help operators streamline API exposure while ensuring high performance and reliability.

Conclusion

This was the last chapter of our white paper. You can download the full white paper below.

Middleware solutions are indispensable for realizing the potential of Open Gateway / CAMARA APIs. By addressing both technical and operational challenges, they enable mobile operators to unlock new revenue streams efficiently and sustainably.

With deep expertise in integration, AAA, and policy solutions, Enea is uniquely positioned to deliver carrier-grade middleware tailored for API use cases—including those based on CAMARA.

By partnering with Enea, operators can:

•  Achieve faster time-to-market at reduced costs.
• Leverage proven integration expertise.
• Maintain control while benefiting from shared development resources.
• Ensure carrier-grade performance, scalability, and reliability.