Table of Contents
Ericsson’s architectural blueprint adds an agentic service experience layer
In sum – what we know:
- Agents as architecture – Ericsson’s new blueprint treats AI agents as a first-class OSS/BSS component, not a Gen-AI feature bolted onto existing operations.
- Intent fans out – A single natural-language objective like “reduce churn among high-value customers” generates catalog, charging, and provisioning changes across Experience, Revenue, and Network agents.
- AWS lock-in – The most developed tooling runs on Amazon Bedrock, which lowers the barrier for AWS operators but raises real lock-in concerns for everyone else.
Ericsson has put agentic AI at the center of its operations and business support stack, formalizing a new OSS/BSS architectural blueprint where AI agents are a first-class component rather than a bolted-on feature. The announcement extends the AI-native OSS/BSS portfolio the company introduced in 2025, but the framing is different this time. Where the earlier work was about embedding Gen-AI across operations, this is about agents that plan, reason, and act across both network operations and business processes.
The headline concept is what Ericsson calls an agentic AI service experience layer, layered over its existing OSS/BSS domains. The idea is to have AI agents orchestrate customer journeys, service lifecycles, and assurance in a unified way, rather than leaving each of those as a separate workflow stitched together by integration work. In practice, that means the framework is pitched as a bridge between AI-native networks and AI-native business operations — keeping RAN and core automation accountable to revenue and service experience goals instead of optimizing the network in isolation. It’s targeted squarely at CSP demands for faster service innovation and the ability to experiment with AI-driven experiences without ripping out legacy OSS/BSS.
The announcement lands alongside Nokia’s launch of its Autonomous Networks Agent Library for IP networks, which pushes the automation battleground out of the network layer and directly into OSS/BSS data ownership. Both vendors are racing to embed AI agents into the operational and business fabric.
Intent-driven operations and a multi-agent architecture
Intent-based automation has been Ericsson’s consistent message for a while, and the new framework leans on it hard. The pitch is that commercial teams can use natural language to define an offer or an outcome, and the system handles the rest. State an intent like “reduce churn among high-value customers,” and the framework is meant to generate consistent catalog entries, charging logic, and provisioning workflows from that single statement rather than having product, billing, and network teams build each piece by hand. Ericsson’s own OSS/BSS blogs already describe multi-agent AI doing this for product configuration, where agents interpret commercial intent, map it to technical product structures, validate feasibility, and write out consistent configurations across catalog, charging, and provisioning systems.
Under the hood, this runs as a multi-agent system. Ericsson describes specialized agents for data ingestion, reasoning, planning, simulation, and execution, coordinated by orchestration logic that ties their actions together. What’s new in the OSS/BSS framing is that some of these agents are exposed natively as domain-specific roles. There are Experience agents focused on customer journey and QoE, Revenue agents handling pricing, upsell, and margin optimization, and Network agents wired into EIAP and rApps for topology and resource changes. The intent is that a single stated objective can fan out across all three.
That also reshapes what the Telco Agentic AI Studio is for. When it launched in 2025 on Amazon Bedrock, the Studio was about building and accelerating AI applications for OSS/BSS. The new framework moves it away from basic app creation toward actively composing multi-agent, end-to-end service experiences — agents coordinating across marketing, charging, QoS, and support to satisfy an intent. It’s a meaningful shift in ambition, though it’s worth noting it’s also a natural extension of what the Studio was already doing rather than a clean break.
Ecosystem integration and the data pipeline
None of this works without good data, of course. The framework deeply integrates the Telco DataOps Platform as a real-time streaming data backbone for AI and automation. The point is to wire customer, service, and network data into a single pipeline so agents act on consistent data across the whole network-business stack. Ericsson’s June 2026 “From data to decisions” blog makes the case bluntly that agentic operations need disciplined pipelines that collect, clean, correlate, and contextualize data before agents act. Without that, an agent adjusting QoS based on predicted churn is acting on guesswork.
The framework also enforces closed-loop service experience management. Earlier closed loops were mostly about network performance, but here the loop extends to experience metrics. Agents directly observe KPIs like NPS, adjust service quality or offers in response, and then measure the resulting business impact. That’s the part that turns customer experience from something you watch into something you control.
Crucially, this isn’t a standalone island. The framework links continuously with the Intelligent Automation Platform (EIAP), which Ericsson expanded around late June 2026 to cover core network automation alongside RAN, plus new real-time data-streaming capabilities for Network Manager. It also folds in capabilities from Ericsson’s early 2026 Differentiated Support release, using agentic AI for automated multi-vendor ticket triage and root-cause analysis — the “hero” of the company’s Intelligent Support Services portfolio. And it interfaces with the “AI in RAN” subscription Ericsson launched earlier this month, which embeds telco-grade AI models directly into basebands and radios for spectral and energy efficiency without new hardware. Stitched together, these pieces are what let Ericsson claim it’s closing the loop between autonomous networks and autonomous operations.
This is also where the competitive contrast with operators gets interesting. Verizon has publicized using agentic AI across its 60,000-site vRAN for configuration, service assurance, and optimization, and has called for interoperability standards for agentic systems. That’s an in-house build. Ericsson’s framework offers a standardized, vendor-driven alternative — appealing to operators that don’t want to engineer their own agentic stack, though it comes with the usual tradeoff of leaning on a vendor’s roadmap and assumptions.
Cloud dependency and hyperscaler deployment
The framework relies heavily on AWS. The Telco Agentic AI Studio and the Gen-AI Lab are both built directly on Amazon Bedrock, with some rApp aaS solutions hosted as SaaS on the AWS Marketplace. The logic is straightforward enough. Hyperscaler AI platforms provide the elastic compute needed to scale agentic workloads, while Ericsson keeps operational telco data control and governance inside its Telco DataOps environment and within CSP boundaries. That split — hyperscaler for compute, telco platform for data — is the company’s answer to operators nervous about handing over their data.
Ericsson does present broad cloud-agnostic deployment options, and the more than 20 cloud-native AI applications from the 2025 portfolio could run on the Telco IT AI Engine or on hyperscaler platforms. But AWS is clearly positioned as the reference implementation for multi-agent workloads, and that’s where the most developed tooling lives.
That’s a double-edged sweetener. For operators already comfortable on AWS, having Bedrock as the proven path lowers the barrier to getting agents into production. For operators running private data centers or committed to a competing cloud, the heavy AWS dependency raises real lock-in questions — how much of the agentic layer genuinely runs elsewhere, and at what cost in capability. It’s a fair question to put to Ericsson, and one CSPs will want answered with specifics before they build a service experience strategy on top of it.
