Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

RAG

Retrieval Augmented Generation

Services →

RAG is a Rel-20 AI technique that enhances generative models by retrieving relevant external data to ground their outputs in accurate, up-to-date information for 3GPP services.

Introduced
Rel-20
Where
Services
Specifications
1 specs
RAG Description Purpose Neighbours Specifications

Description

Retrieval Augmented Generation (RAG) is a technique introduced in 3GPP Release 20 and studied in specification 22.870. It combines information retrieval systems with generative artificial intelligence models to produce more accurate, contextually grounded, and verifiable outputs. Rather than relying solely on the parametric knowledge embedded in a large language model (LLM) during training, RAG dynamically fetches relevant documents, records, or data from external knowledge sources at inference time and presents them to the model as additional context for generation.

The architecture of a RAG system typically comprises three principal components. First, a retrieval subsystem maintains an indexed corpus of domain-specific data — for telecommunications this could include 3GPP specifications, network configuration repositories, performance counter databases, alarm histories, or subscriber policy documents. The corpus is encoded into vector embeddings stored in a vector database, allowing semantic similarity search rather than mere keyword matching. Second, a query processing stage transforms the user or application request into a retrieval query, optionally rewriting or expanding it to improve recall. Third, the generation stage receives both the original query and the retrieved passages, and the generative model synthesizes a response that cites or incorporates the retrieved evidence.

In the 3GPP context studied under 22.870, RAG is positioned as an enabler for AI/ML-based services within the 5G-Advanced and 6G ecosystem. Potential use cases include network operations assistance (for example, an operator asking a natural-language question about why a particular cell is underperforming, with the system retrieving relevant KPIs and configuration data), automated customer support for network slicing or QoS inquiries, and intelligent management of network data analytics. The retrieval layer ensures the AI's answers reflect the actual state of the network and current standards rather than stale training data.

Integration with 3GPP architecture implies that the retrieval corpus and generative inference functions may be hosted as Application Functions (AFs) or as part of the Network Data Analytics Function (NWDAF) ecosystem, exposing capabilities through service-based interfaces. Data governance, privacy, and security are important considerations: retrieved documents may contain sensitive subscriber or network data, so access control, anonymization, and auditability must be enforced. The specification work also considers how RAG services can be discovered and invoked via the 5G Service Based Architecture, and how their quality (retrieval accuracy, generation faithfulness) can be monitored.

RAG matters because pure generative models are prone to hallucination and are frozen at training time, which is unacceptable in a standards-driven, safety-critical domain such as telecommunications. By grounding generation in authoritative retrieved sources, RAG improves factual accuracy, traceability, and updateability. It allows operators to leverage new standards, live telemetry, and proprietary knowledge without retraining the underlying model, making AI assistance practical and trustworthy for network operations and service management.

Purpose & Motivation

RAG exists to overcome two fundamental limitations of standalone generative AI: knowledge staleness and hallucination. Large language models encode only what they learned during training, which becomes outdated quickly in a fast-moving domain like telecommunications where specifications evolve with every 3GPP release and network conditions change continuously. RAG addresses this by fetching current, authoritative information at query time so that answers reflect reality rather than training-time snapshots.

A second motivation is trust and verifiability. Network operations, fault diagnosis, and subscriber-facing services require answers that can be traced to source documents and audited. Pure generation offers no provenance, which is unacceptable for regulated telecom environments. RAG provides citations and retrieval evidence, making AI outputs auditable and easier to validate against 3GPP specifications and operator data.

Historically, retrieval-based question answering and knowledge management systems preceded RAG, but they could not produce fluent, synthesized responses. Conversely, generative models produced fluent responses without factual grounding. Release 20 work in 22.870 represents 3GPP's recognition that combining these paradigms is essential for trustworthy AI-native telecom services, particularly as the industry moves toward autonomous networks and intent-based management.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-20 Initial

Initial introduction of Retrieval Augmented Generation as a studied concept in 3GPP, documented in specification 22.870. It establishes use cases, architectural considerations, and service requirements for grounding generative AI in retrieved telecom data.

Defining Specifications

3GPP specifications that define or reference RAG, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.870 vk00 Study on 6G Use Cases and Service Requirements Rel-20 read