Skip to content

Docs

6G-JEV (RANIntent v1)

RANIntent v1: an O-RAN intent-interpretation benchmark from UTS with 16 telemetry conditions, where an interpreter returns one A1 policy with 9 fields; 300 test and 60 dev cases per condition.
Format
Docs
Reading time
2 min
Published by
Community
Author
UTSCybeR
Last verified
Oct 2026

Highlights

  • 16 configs: 3, 7, 21 or 57 cells crossed with fresh, stale, noisy and contradictory telemetry; each has 300 test and 60 dev cases.
  • Interpreter output is one A1 policy of type 20001 with 9 fields, from action values such as prioritise and cap_share to class, scope and priority.
  • 150 test cases per condition are state-dependent: the scope is most_loaded_cells or worst_edge_cells and the telemetry picks the target cluster.
  • Paper: arXiv 2609.23136, Intent Interpretation at RIC Timescales, by Delong Li and colleagues at the University of Technology Sydney.
  • Scores cover target_cluster accuracy, actuated-field match, full-policy match, schema validity and unsafe policies; CC BY 4.0.

Quickstart

python
from datasets import load_dataset
ds = load_dataset("OniReimu/6G-JEV", "c21_fresh")

Watch out

Card reviewed 2026-10-17; the dataset accompanies the authors' own paper (arXiv 2609.23136) and its comparisons of Jev decision models against large language models are their reported results, not independent evaluations. Dev cases are only for prompt checks, and telemetry token counts grow steeply with cell count.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai