---
title: 'NetGPT: Generative AI in Networked Systems'
url: https://www.emergentmind.com/topics/netgpt
type: topic
---

# NetGPT: Generative AI in Networked Systems

NetGPT is a designation used in several arXiv research lines at the intersection of generative pretrained models and networked systems. In wireless communications, it denotes AI-native network architectures that combine edge and cloud large language models, a broader family of foundation models for wireless systems, and later agentic frameworks for collaborative reasoning in xG networks [2307.06148][2311.13106][2602.00766]. The same designation has also been used for a generative pretrained transformer for network traffic understanding and generation [2304.09513], and for a large graph model for short-video propagation influence rating [2503.23746]. Across these uses, the common emphasis is on coupling pretrained generative models with structured network state, resource constraints, or graph-structured observations.

## 1. Terminological scope and conceptual lineage

In the wireless-communications literature, NetGPT is explicitly defined as “Network Generative Pre-trained Transformer,” namely a class of foundation models for wireless communications rather than a single monolithic model. “Ten issues of NetGPT” states that NetGPT is a *family* of transformers of various sizes and specializations tailored to domains such as RAN, CN, OAM, and UE, and organizes this family into a three-layer hierarchy: NetGPT-L0, NetGPT-L1, and NetGPT-L2 [2311.13106]. This directly counters a common misconception that NetGPT refers to one fixed architecture.

The surveyed literature also uses the same name for distinct technical artifacts. In 2023, one line presented NetGPT as a native-AI network architecture for cloud-edge personalized generative services [2307.06148]. A later xG-oriented line proposed an agentic NetGPT core with domain-specialized agents and agentic reinforcement learning [2602.00766]. Outside wireless control and orchestration, another work used NetGPT for a GPT-based pretrained model over network traffic byte streams [2304.09513], while a separate line used NetGPT for a large graph model operating on a cross-platform short-video propagation graph [2503.23746].

| Usage of “NetGPT” | Domain | Representative work |
|---|---|---|
| Network foundation-model family | Wireless communications | [2311.13106] |
| Cloud-edge personalized generative architecture | AI-native network architecture | [2307.06148] |
| Agentic collaborative reasoning framework | xG wireless networks | [2602.00766] |
| Generative pretrained transformer for traffic | Network traffic modeling | [2304.09513] |
| Large graph model | Short-video propagation analysis | [2503.23746] |

A plausible implication is that “NetGPT” functions more as a research motif than as a single stable specification: the term consistently signals the transplantation of GPT-like or LLM-like mechanisms into network-centric problem domains, but the underlying objects differ substantially.

## 2. Cloud-edge NetGPT for personalized generative services

“NetGPT: A Native-AI Network Architecture Beyond Provisioning Personalized Generative Services” proposes a collaborative cloud-edge methodology in which an edge LLM and a cloud LLM are orchestrated according to computing capacity and personalization requirements [2307.06148]. The edge tier is deployed on a base-station or edge server and uses GPT-2-base (approximately \(0.1\) B parameters). Its responsibilities are prompt enhancement or completion through location and personalized information, preliminary de-duplication and buffering of requests, and local inference for trend prediction and intent inference as by-products. The cloud tier is deployed in centralized data centers and uses a fine-tuned LLaMA-7B model (approximately \(6.7\) B parameters) for final generative response and heavy-weight inference and RLHF loops. An orchestration module maintains a resource database, latency/performance profiles of each LLM, and user profiles with location metadata, and performs resource allocation, workflow mapping, and offloading decisions.

The service pipeline begins with a concise prompt \(P_{\mathrm{con}}\) from the user. At the edge, the model computes a comprehensive prompt
$$
P_{\mathrm{com}} = LLM^{\mathrm{edge}}_{\theta}(P_{\mathrm{con}}; I_{\mathrm{personalized}})
$$
where \(I_{\mathrm{personalized}}\) includes base-station location from the 5G AMF and venue or facility metadata. The paper reports \(P_{\mathrm{com}}\) at roughly \(95\) bytes versus \(12\) bytes for the concise prompt [2307.06148]. The logical workflow comprises request arrival, buffering and de-duplication, edge inference, optional early return if local confidence exceeds \(\tau_{\mathrm{local}}\), cloud inference otherwise, post-processing, delivery, a feedback loop, and continuous orchestration updates based on latency, accuracy, and throughput.

The same work also formalizes cloud-edge resource orchestration as a binary decision problem over requests \(x_i \in \{0,1\}\), minimizing expected latency plus resource cost subject to edge and cloud CPU/GPU capacity and throughput constraints [2307.06148]. This formulation anchors NetGPT not merely as an LLM deployment pattern but as an architecture-level proposal for integrating communication and computing resources in AI-native networks.

## 3. Agentic NetGPT and collaborative reasoning in xG networks

“Communications-Incentivized Collaborative Reasoning in NetGPT through Agentic Reinforcement Learning” re-specifies NetGPT as a unified agentic framework for AI-native xG networks [2602.00766]. Its NetGPT Core is built on a standard LLM backbone such as LLaMA-3 Instruct and extends it with an Intent Interpreter, a Reasoning Module, and a Coordination Controller. The Core maintains a protocol-agnostic Agent Registry containing agent cards with supported actions, endpoint metadata such as latency, cost, and load, and identity and capability descriptors mapped from A2A, ACP, and ANP via adapters. Domain-specialized agents live in the user, control, or compute plane, or on an edge node, and comprise a Perception Interface, a Local Reasoner or Toolbox, and a Communication Adapter. A shared infrastructure layer exposes knowledge bases, data lakes, registry services, and persistent memories to both Core and agents.

The communication protocol is explicitly agentic. Supported protocols are A2A, ACP, and ANP via a thin adapter. Invocation messages use an `<action ...>` envelope, while agent replies use an `<ans ...>` envelope. A central masking rule states that only tokens between `<ans>` and `</ans>` are unmasked and fed back into the Core’s reasoning loop; all other tokens are masked out for policy-gradient updates [2602.00766]. Under the paper’s Markov decision process, the state is
$$
s_t = \{h_t, O_t^{\mathrm{ext}}\},
$$
where \(h_t\) is the decoder hidden state and \(O_t^{\mathrm{ext}}\) is the partial external observation returned by agents. The action space includes ordinary token emission and invocation actions:
$$
A = V \cup \{\mathrm{invoke}(a)\mid a \text{ supports current sub-task}\}.
$$

The collaboration objective is explicitly multi-objective:
$$
R = \alpha \cdot Q(\mathrm{task}) + \beta \cdot E(\mathrm{coord}) - \gamma \cdot C(\mathrm{resources}),
$$
with \(Q(\mathrm{task}) \in [0,1]\), \(E(\mathrm{coord}) \in [0,1]\), and \(C(\mathrm{resources}) \ge 0\) [2602.00766]. The decision mechanism compares the maximum internal-token probability with the maximum invocation probability, selecting an invocation when \(p_{\mathrm{invoke\_max}} > \tau\), where \(\tau\) is learned by an auxiliary head on a held-out validation set of “should-invoke” versus “should-reason-internally” labels. This formulation makes collaboration endogenous to the decoder policy rather than a purely external scheduler.

This suggests a broadening of NetGPT from earlier cloud-edge synergy toward explicit multi-agent delegation and partially observable coordination, although the surveyed papers present these as separate formulations rather than as a single standardized lineage.

## 4. Training and optimization paradigms

A recurring technical theme is parameter-efficient adaptation. In the cloud-edge architecture, low-rank adaptation is used for fine-tuning open-source LLMs. For a pretrained weight matrix \(W \in \mathbb{R}^{d_{\mathrm{in}} \times d_{\mathrm{out}}}\), the update is
$$
\Delta W = AB,\qquad W' = W + \alpha AB,
$$
with \(A \in \mathbb{R}^{d_{\mathrm{in}} \times r}\), \(B \in \mathbb{R}^{r \times d_{\mathrm{out}}}\), and \(r \ll \min(d_{\mathrm{in}}, d_{\mathrm{out}})\) [2307.06148]. For LLaMA-7B, the paper reports VRAM reduction from \(112\) GB to approximately \(28\) GB and storage of fine-tuned parameters from approximately \(12.5\) GB to approximately \(50\) MB for \(r=8\) and \(\alpha=16\).

The agentic xG framework adopts a two-phase end-to-end loop consisting of supervised fine-tuning followed by agentic reinforcement learning [2602.00766]. Phase 1 minimizes
$$
L_{\mathrm{SFT}} = -\sum_i \log \pi_{\theta}(\mathrm{target}_i \mid \mathrm{prompt}_i),
$$
over direct Q-A samples and action-driven dialogues with annotated `<action>...</action>` spans. Phase 2 performs rollouts in a simulated or real network environment, routes `invoke(a)` steps to concrete agents, computes multi-objective rewards, adds entropy-guided exploration, and applies a masked policy gradient. The paper gives \(\alpha_{\mathrm{SFT}} = 10^{-5}\), \(\alpha_{\mathrm{RL}} = 3 \times 10^{-6}\), \(\beta_{\mathrm{entropy}} = 0.01\), reward weights \(\alpha = 1.0\), \(\beta = 0.5\), \(\gamma = 0.3\), and an annealing schedule for \(\beta_{\mathrm{entropy}}\) down to \(0.001\) [2602.00766].

A separate optimization line, “Optimizing NetGPT via Routing-Based Synergy and Reinforcement Learning,” formalizes cloud-edge routing as a threshold policy over a router score \(s_{ik} = g_{\psi}(x_i, H_{ik}, u_{ik})\) and a fallback threshold \(\tau(S_{ik})\) that depends on network state \(S_{ik} = (\mathrm{RTT}_{ik}, \mathrm{BW}_{ik})\) [2511.22217]. Under assumptions that \(\Delta C(s) > 0\) and that the benefit-cost ratio \(\rho(s)=\Delta Q(s)/\Delta C(s)\) is continuous and strictly decreasing, the utility \(J(\tau)=Q(\tau)-\lambda C(\tau)\) is maximized at the unique threshold \(\tau^\*\) satisfying
$$
\Delta Q(\tau^\*) = \lambda \cdot \Delta C(\tau^\*).
$$
The paper derives monotone comparative statics: \(\tau^\*\) increases with bandwidth and decreases with RTT. It then gives two deployable parameterizations, FuncDyn and PolicyNet, and couples them with an SFT-anchored RL scheme whose composite objective combines a reverse-KL trust region against the old policy with a forward-KL realignment toward the SFT prior [2511.22217]. In that formulation, the forward-KL term is explicitly intended to preserve schema correctness and prevent catastrophic forgetting of the tool-calling format.

## 5. Empirical evaluation in AI-native networking

The empirical literature on wireless NetGPT evaluates latency, coordination, cost, quality, and personalization under different formulations. The 2023 cloud-edge paper reports a numerical comparison for \(10{,}000\) concise prompts at \(1\) Gbps and batch \(=100\) [2307.06148]. In that table, cloud-only yields end-to-end latency \(20.19\) s with \(12.55\) GB cloud VRAM and \(12\) bytes transferred per request; LLM Offload yields \(0.55\) s latency with \(28\) GB edge VRAM; LLM Splitting (\(1/4\)) yields \(1.22\) s latency with approximately \(131{,}064\) bytes transferred; and NetGPT (Synergy) yields \(3.35\) s latency, \(1.65\) GB edge VRAM, \(0.05\) GB edge storage, and \(31\) bytes transferred per request. The same paper interprets these numbers as reducing edge VRAM and storage by more than \(90\%\) versus LLM Offload and reducing latency by approximately \(6\times\) versus cloud-only, while Fig. D reports \(8\)–\(12\%\) higher BLEU/ROUGE for personalized tasks than cloud-only [2307.06148].

The 2026 agentic paper evaluates task accuracy \(Q(\mathrm{task})\), coordination efficiency \(E(\mathrm{coord})\), latency or SLA violation rate, and a composite score \(\alpha Q + \beta E - \gamma C\) on TeleQnA and TeleLogs [2602.00766]. Its reported “numbers illustrative” are: Pure Prompting with \(Q=0.62\), \(E=0.40\), Composite \(=0.55\); SFT Only with \(Q=0.78\), \(E=0.55\), Composite \(=0.72\); and NetGPT + Agentic RL with \(Q=0.89\), \(E=0.72\), Composite \(=0.86\). The paper summarizes this as an \(11\%\) absolute gain in accuracy over SFT, \(31\%\) fewer unnecessary agent calls versus SFT-only, and a \(24\%\) reduction in average end-to-end latency [2602.00766].

The 2025 routing-and-RL paper evaluates GOOD, MID, and BAD link regimes with RTT and bandwidth sampled from \([20,40]\) ms and \([120,200]\) Mbps, \([40,80]\) ms and \([30,80]\) Mbps, and \([80,130]\) ms and \([5,15]\) Mbps, respectively, under a Gauss-Markov model [2511.22217]. Its reported findings are qualitative but precise: dynamic controllers such as FuncDyn and PolicyNet dominate fixed-threshold and learned static routers on the quality-cost frontier; dynamic thresholds adapt smoothly under regime switches; empirical frontiers \(Q(\tau)\) versus \(C(\tau)\) are smooth and diminishing-returns; scanning \(J(\tau)\) shows a unique unimodal peak \(\tau^\*\) that falls as the network degrades or as cost-sensitivity \(\lambda\) increases; and PPO with SFT anchoring improves reward and reduces offload rate without spuriously violating JSON schema, whereas PPO without SFT anchoring is unstable [2511.22217].

These results are not directly commensurate because the tasks, metrics, and experimental environments differ. What they jointly establish is that NetGPT research in networking has moved from static cloud-edge partitioning toward adaptive routing, policy learning, and collaboration-aware utility optimization.

## 6. Non-wireless uses of the name: traffic pretraining and large-graph reasoning

One distinct usage appears in “NetGPT: Generative Pretrained Transformer for Network Traffic,” which presents a GPT-2-Base model for traffic understanding and generation [2304.09513]. The backbone has \(12\) Transformer layers, hidden size \(768\), \(12\) causal self-attention heads, and feed-forward inner dimension \(3072\). Input representation is a uniform multi-pattern encoding in which each raw byte is converted to a two-digit ASCII hex string and tokenized with WordPiece; the model uses special tokens `[cls]` and `[pck]`, adds segment embeddings for flow-level fine-tuning, and remains strictly autoregressive. Fine-tuning employs header-field shuffling, packet segmentation across up to the first three packets of a flow, and prompt-based task labels that recast classification and generation as conditional generation. On five datasets totaling approximately \(113\) GB raw PCAP, the paper reports packet-level average Accuracy/Macro-F1 of \(0.9856/0.9856\) and flow-level average \(0.9460/0.9460\), outperforming ET-BERT and GPT-2 baselines; for traffic generation, the average Jensen-Shannon divergence across four test datasets is \(0.0406\) for NetGPT versus \(0.0417\) for GPT-2, with packet-length JSD on ISXW falling from \(0.0844\) to \(0.0492\) [2304.09513].

Another distinct usage appears in “Short-video Propagation Influence Rating: A New Real-world Dataset and A New Large Graph Model,” where NetGPT denotes a large graph model for the SPIR task [2503.23746]. Here the objective is to predict a short video’s long-term influence level \(y \in \{0,\dots,9\}\) within a cross-platform propagation graph. The XS-Video dataset comprises \(117{,}720\) videos, \(381{,}926\) samples, \(535\) topics, and approximately \(5.5 \times 10^6\) nodes with approximately \(1.67 \times 10^9\) edges. NetGPT combines a heterogeneous GNN encoder, an off-the-shelf LLM such as Qwen2-VL, and a three-stage training pipeline of Heterogeneous Graph Pretraining, Supervised Language Fine-tuning, and Task-oriented Predictor Fine-tuning. On the XS-Video test set, the reported performance is ACC \(= 0.6777\), MSE \(= 0.7169\), and MAE \(= 0.5457\), compared with RGCN at \(0.6313/0.7801/0.5844\) and Qwen2-VL at \(0.5884/1.6820/0.6629\) [2503.23746].

These non-wireless uses matter for terminology. A common misconception is that NetGPT names only a wireless-network control architecture. The literature surveyed here shows that it also names a byte-level traffic pretrained model and a graph-LLM hybrid for social propagation analysis.

## 7. Open issues, limitations, and research questions

“Ten issues of NetGPT” frames the principal unresolved questions for the wireless line of research [2311.13106]. It argues that dedicated AI models in wireless suffer from low generality, limited performance gain, complicated management and collaboration, and lack of multi-task processing capability. Against that background, the paper identifies ten issues spanning scenarios and requirements, theoretical gaps between NetGPT and LLMs, ultimate performance, collaboration mechanisms, distributed deployment, network architecture design, security and privacy, data governance, evaluation and SLA metrics, and full-lifecycle management and orchestration.

Several of these issues expose persistent technical tensions. The paper notes that communication data are continuous, high-dimensional tensors rather than ordinary text tokens, while outputs may be bit-level decisions, numeric predictions, or control commands rather than natural-language continuations [2311.13106]. It also highlights stringent 6G objectives, including approximately \(0.1\) ms real-time inference and ultra-reliability, and states that hallucination cannot be tolerated in mission-critical network decisions. On the systems side, it points to heterogeneous end-edge-cloud hardware, intermittent connectivity, the need for dynamic partitioning, and the absence of standardized model update interfaces. On the governance side, it identifies backdoor and poisoning risks, exposure of sensitive user data during inference, the need for differential privacy or encryption in model updates, and the requirement for unified data-governance frameworks and cross-vendor evaluation suites.

These concerns should not be read as rejections of NetGPT. Rather, they delimit the conditions under which NetGPT-style systems would need to operate if they are to move from conceptual architecture and controlled evaluation toward telecom-grade deployment. The open questions are therefore not peripheral; they define the boundary between current demonstrations and operational AI-native networks.

Source: https://www.emergentmind.com/topics/netgpt