The A1 interface enables the Non-RT RIC to provide long-term, declarative policies to the Near-RT RIC, guiding its near-real-time optimization decisions without dictating specific actions. It carries three primary information types: policy guidance (high-level directives like energy-saving targets), enrichment data (contextual information from the SMO that the Near-RT RIC cannot derive locally), and AI/ML model management (deploying, updating, and monitoring machine learning models used by xApps).
Glossary
A1 Interface

What is the A1 Interface?
The A1 interface is the standardized open interface in the O-RAN architecture that connects the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) to the Near-Real-Time RIC (Near-RT RIC) for policy-based guidance, enrichment information, and AI/ML model management.
Unlike the real-time E2 interface, A1 operates on a slower control loop (>1 second), focusing on intent-driven governance rather than instantaneous resource allocation. It uses a RESTful API-based protocol, allowing rApps in the Non-RT RIC to declaratively state desired outcomes, which the Near-RT RIC translates into executable E2 control actions. This separation of concerns enables centralized policy orchestration while preserving distributed, low-latency execution.
Core Functions of the A1 Interface
The A1 interface is the standardized northbound link enabling the Non-RT RIC to provide declarative policies, enrichment information, and AI/ML model management directives to the Near-RT RIC for long-term network optimization.
Policy-Based Guidance Delivery
The primary function of A1 is to transport declarative policies from the Non-RT RIC to the Near-RT RIC. Unlike imperative E2 commands, A1 policies specify high-level goals—such as 'maximize energy efficiency while maintaining voice QoE above threshold'—leaving the Near-RT RIC to determine the specific radio resource management actions. This separation of concerns enables hierarchical optimization where long-term business objectives constrain near-real-time control loops.
Enrichment Information Provisioning
The A1 interface supplies the Near-RT RIC with contextual enrichment data that is not directly observable from the RAN. This includes:
- UE mobility predictions derived from historical trajectory analysis
- Per-cell traffic forecasts generated by time-series models in the Non-RT RIC
- Spectrum availability maps for dynamic sharing scenarios
- Weather and event data correlated with demand spikes This enrichment allows xApps to make more informed decisions by augmenting real-time E2 telemetry with predictive intelligence.
AI/ML Model Management
A1 serves as the conduit for end-to-end model lifecycle operations between the Non-RT RIC and Near-RT RIC. Key capabilities include:
- Model deployment: Pushing trained inference models to the Near-RT RIC for execution by xApps
- Model selection: Directing which model version an xApp should use based on performance monitoring
- Model performance feedback: Receiving inference accuracy metrics back from the Near-RT RIC
- Fallback triggers: Instructing the Near-RT RIC to revert to a baseline model when model drift is detected This closed-loop model management ensures continuous adaptation to changing network conditions.
Intent Translation Interface
The A1 interface carries the output of the Intent Translation Engine within the Non-RT RIC. High-level business intents expressed in natural language or structured templates are decomposed into machine-executable policies. For example, an intent like 'guarantee gold-tier slice performance during business hours' is translated into specific KPI targets and resource allocation constraints transmitted over A1. This bridges the gap between operator business objectives and automated network control.
Monitoring and Assurance Feedback
A1 supports a bidirectional feedback loop for policy assurance. The Near-RT RIC reports:
- Policy compliance status: Whether current RAN conditions satisfy declared policy targets
- Anomaly notifications: Alerts when unexpected behavior prevents policy fulfillment
- Performance summaries: Aggregated KPI reports for long-term trend analysis This feedback enables the Non-RT RIC to adjust policies, retrain models, or trigger operator alerts when the network diverges from intended operational states.
Coordination with O1 and SMO
While A1 handles the policy and enrichment plane, it operates in concert with the O1 interface for FCAPS management. The Service Management and Orchestration (SMO) framework uses O1 for fault, configuration, and performance management of RIC components, while A1 focuses exclusively on the optimization logic. This separation ensures that management traffic does not interfere with time-sensitive policy delivery. The SMO orchestrates both interfaces to maintain a unified operational view.
Frequently Asked Questions
Essential questions and answers about the A1 Interface, the standardized open interface enabling policy-based guidance and AI/ML model management between the Non-Real-Time RIC and the Near-Real-Time RIC in O-RAN architectures.
The A1 Interface is the standardized open interface between the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) and the Near-Real-Time RIC (Near-RT RIC) within the O-RAN architecture. It enables the Non-RT RIC to provide policy-based guidance, enrichment information, and AI/ML model management to the Near-RT RIC for network optimization. Operating on a timescale greater than 1 second, the A1 interface facilitates the exchange of declarative policies, performance data, and machine learning models. It uses a RESTful API based on the OpenAPI (Swagger) specification, with JSON as the data format, ensuring interoperability between multi-vendor RIC implementations. The interface supports four primary service operations: policy management, enrichment information provisioning, AI/ML model management, and data reporting.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The A1 interface operates within a broader O-RAN architecture. These related concepts define the functions, platforms, and policies that interact directly with this standardized policy and enrichment conduit.
Non-Real-Time RAN Intelligent Controller (Non-RT RIC)
The logical function that terminates the A1 interface on the management side. It hosts rApps that leverage AI/ML analytics to generate long-term policy guidance, enrichment information, and AI model management directives. The Non-RT RIC operates on time scales greater than 1 second and is the primary consumer of the A1 interface for communicating intent to the Near-RT RIC.
Near-Real-Time RAN Intelligent Controller (Near-RT RIC)
The logical function that terminates the A1 interface on the network side. It receives policy-based guidance and enrichment data from the Non-RT RIC and executes fine-grained control loops via the E2 interface. The Near-RT RIC hosts xApps and must process A1 messages to adjust its optimization strategies within a 10ms to 1s latency budget.
A1 Policy Types
The A1 interface supports distinct policy categories that govern Near-RT RIC behavior:
- Declarative policies: Specify desired outcomes without dictating implementation
- Imperative policies: Provide explicit configuration directives
- Enrichment policies: Deliver contextual data to improve xApp decision-making
- AI/ML management policies: Control model lifecycle, including deployment, monitoring, and rollback
Service Management and Orchestration (SMO)
The unified management framework that integrates the Non-RT RIC and provides the A1 interface termination point. The SMO handles:
- A1 policy lifecycle management
- AI/ML workflow orchestration
- FCAPS management via the O1 interface
- Data collection and distribution for rApp consumption
Intent Translation Engine
A critical component of the Non-RT RIC that converts high-level business intents expressed in natural language into machine-executable A1 policies. This engine:
- Parses operator goals (e.g., 'maximize energy efficiency while maintaining voice quality')
- Translates them into declarative A1 policy objects
- Continuously validates policy compliance against observed network state

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us