Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code: DatasetGenerationError
Exception: CastError
Message: Couldn't cast
chunk_id: string
id: string
path: string
section: string
spec: string
text: string
to
{'id': Value('string'), 'spec': Value('string'), 'text': Value('string')}
because column names don't match
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1827, in _prepare_split_single
for key, table in generator:
^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 613, in wrapped
for item in generator(*args, **kwargs):
~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 132, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
chunk_id: string
id: string
path: string
section: string
spec: string
text: string
to
{'id': Value('string'), 'spec': Value('string'), 'text': Value('string')}
because column names don't match
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1880, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
id string | spec string | text string |
|---|---|---|
350baa7a4cd56b0b0052 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
# O-RAN Security Focus Group (SFG)
## Study on Security for Non-RT-RIC
**This is a re-published version of the attached final specification.**
For this re-published version, the prior versions of the IPR Policy will apply, except that the previous requirement for Adopters (as... |
5934e8ad3e407ad5a515 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 1 Introduction
#### 1.3.2 SFG Specifications
[7] O-RAN Security Requirements Specifications, v01.00.05, O-RAN.SFG.O-RAN-Security-Requirements-Specifications-v01.00.05.
[8] O-RAN Threat Modelling and Remediation Analysis, v02.00.02, O-RAN.SFG.O-RAN-Threat-Model-v02.00.02.
... |
0715423dbb9a2cf5186f | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 1 Introduction
### 1.4 Definitions and Abbreviations
#### 1.4.1 Definitions
For the purposes of the present document, the terms and definitions provided in O-RAN.WG1.O-RAN-Architecture-Description-v06.00 apply:
**A1:** Interface between non-RT RIC and Near-RT RIC to enable... |
5c33b379f1e39c397697 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 1 Introduction
### 1.4 Definitions and Abbreviations
#### 1.4.2 Abbreviations and acronyms
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and the following apply:
**Table in section 1.4.2 Abbreviations and acronyms**
Columns: 1. Column ... |
fee6635904cdaa7876c3 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 2 Non-RT-RIC Assets
### 2.1 Architecture
The primary goal of non-RT RIC is to support non-real-time intelligent radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing AI/ML models to near-RT RIC and other RAN functions. The... |
66d4f4c43202e8de0eba | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 2 Non-RT-RIC Assets
### 2.2 Framework
- ASSET-C-11: Non-RT-RIC, see O-RAN.WG2.Non-RT-RIC-ARCH-TS-v01.00
### 2.3 Functions
The functions in the scope of this document include the rApps, R1 Termination, and A1 Termination. The other functions in the Non-RT RIC framework as s... |
ad7cdc9208c5210629b1 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 3 Threats
### 3.2 Threat Template
Template to present the threat characteristics:
**Table in section 3.2 Threat Template**
Columns: 1. Threat ID | 2. Column 2
- Threat title
- Threat description
- The threat type includes Spoofing, Tampering, Repudiation, Information discl... |
bb7d621643e6b3a7c79a | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 4 Threat Analysis
### 4.2 rApps Threats
rApps have the ability to manipulate behavior of a certain cell, a group of UEs, and a specific UE. A malfunctioning rApp could potentially be used to track or impact service for a certain UE-Id or degrade service in an area.
**Table... |
074d39d9a9b005735b0d | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 4 Threat Analysis
### 4.3 R1 Threats
The R1 interface facilitates inter-connection between rApps and Non-RT RIC framework supplied by different vendors, and provides a level of abstraction between rApps and Non-RT RIC framework/SMO that can be the consumers and or producers... |
6376c343b1f189635024 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 4 Threat Analysis
### 4.4 A1 Threats
The purpose of the A1 interface is to enable the Non-RT RIC function to provide policy-based guidance, ML model management and enrichment information to the Near-RT RIC function for RAN can optimization. The Non-RT RIC can provide enrich... |
ae7813887aa8ceceaf2f | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 4 Threat Analysis
### 4.5 Protocol Stack Threats
The A1 and R1 interfaces use the REST protocol stack shown in the figure below. The transport network layer is built on IP transport. TCP provides the communication service at the transport layer. HTTP is the application-leve... |
d4035f168da117a60836 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 5 Security Controls
Industry recommendations for strong security controls are provided from sources such as the OWASP Top 10 Proactive Controls [15], Cloud Security Alliance (CSA) Cloud Control Matrix (CCM) [17], ISO/IEC 27001:2013 Information Security Management System (IS... |
2d268f3d0339b9d4685a | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 6 Risk Assessment
### 6.1 Risk Assessment for Non-RT-RIC
**Table in section 6.1 Risk Assessment for Non-RT-RIC**
Columns: 1. Asset-Id | 2. Asset Name | 3. Threat-Id | 4. Threat Description (Brief) | 5. Impact/ Likelihood Raw Score | 6. Possible Security Controls | 7. Securi... |
1aa6aca497bf7578d62c | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 6 Risk Assessment
### 6.3 Risk Assessment for R1 Interface
**Table in section 6.3 Risk Assessment for R1 Interface**
Columns: 1. Asset-Id | 2. Asset Name | 3. Threat-Id | 4. Threat Description (Brief) | 5. Impact/Likelihood Score | 6. Security Controls | 7. Security Control... |
84b540e8b6053ca754aa | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 7 Recommendations
The Security Analysis presented in this technical report used the following process:
1. Asset identification -> 2. Threat identification -> 3. Threat analysis -> 4. Risk analysis -> 5. Recommend Security Controls
The Non-RT RIC Reference Architecture is ... |
b5e51c8485083fb1bd36 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## 1 Annex A (informative): xxxxx
# Annex ZZZ : O-RAN Adopter License Agreement
BY DOWNLOADING, USING OR OTHERWISE ACCESSING ANY O-RAN SPECIFICATION, ADOPTER AGREES TO THE TERMS OF THIS AGREEMENT.
This O-RAN Adopter License Agreement (the “Agreement”) is made by and between t... |
4d8f7afee66b9ce1e00e | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
# Annex ZZZ : O-RAN Adopter License Agreement
## Section 3: FRAND LICENSE
3.1 Members, Contributors and Academic Contributors and their Affiliates are prepared to grant based on a separate Patent License Agreement to each Adopter under Fair Reasonable And Non- Discriminatory (... |
52ae2d1f4f73a5b1da45 | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
# Annex ZZZ : O-RAN Adopter License Agreement
## Section 5: CONFIDENTIALITY
Adopter will use the same care and discretion to avoid disclosure, publication, and dissemination of O-RAN Specifications to third parties, as Adopter employs with its own confidential information, but... |
d88b0cbb5feb3dfb985a | O-RAN.SFG.Non-RT-RIC-Security-TR | # O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00
## Section 8: ASSIGNMENT
### Section 11: GENERAL
This Agreement is governed by the laws of Germany without regard to its conflict or choice of law provisions.
This Agreement constitutes the entire agreement between the parties as to its express subject matter and expressly su... |
60f64fe4621c5956b339 | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
# O-RAN Focus Group (Sustainability Focus Group)****Circular economy guidelines on network equipment
Copyright © 2022 by the O-RAN ALLIANCE e.V.
The copying or incorporation into any other work of part or all of the material available in this document in any form without the prior written permi... |
c9223a239650bd5e2f7d | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
# Introduction
Circular economy model reduces environmental impact supporting the reduction of material use, recycling, and recovering of product, product parts, components, and materials to circulate them in the value chain for as long as possible.
The present document identifies circular econ... |
85aa6e2227e9c810f11d | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 3 Definition of terms, symbols and abbreviations
### 3.1 Terms
For the purposes of the present document, the following terms apply:
**Circular economy** [ITU-T L.1020]: A circular economy is restorative and regenerative by design, and aims to keep products, components, and materials at their... |
5a9bd254ec8bd27bf78c | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
Based on ITU-T L.1023 recommendation, there is a three-step methodology to identify an information and communication technology (ICT) good's circularity in three dimensions via three circularity aspects: first, the ICT good durability, second, the ICT g... |
1fe0e4d8fe17f5111c8e | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
### 1. Product durability
**1.1. Software and data support:** Availability of software and firmware updates & upgrades (according to EN 45554).
- The most contributing variable to the circularity of the equipment: Software and firmware updates & upgrad... |
d723a9c949014cc741f8 | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
### 2. Recycle, repair, reuse, upgrade – Equipment level
**2.1. Fasteners and connectors:** Fasteners, connectors and tools used to disassemble parts that are likely to need replacement during the expected lifetime of the product are reusable/removable ... |
91f8657eb4ae002dcf48 | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
### 2.7. Material identification: Identification and marking of the materials contained in the equipment. The identification and marking of materials facilitate the subsequent recycling of the equipment. Materials identification according to ISO 11469.
... |
425b6feea6c88b74d7ac | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
### 3. Ability to Recycle, Repair, Reuse, upgrade - Manufacturer level
**3.1. Service offered by manufacturer:** Duration of Repair, Reuse, upgrade services (according to EN 45554).
- The most contributing variable to the circularity of the equipment: ... |
bc3af9850af6feca1fa4 | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## 4 Circular economy on network equipment
### 4.1 O-CU/O-DU
**Table 4.1-1 O-CU/O-DU priority definition based on circularity economy effect**
Columns: 1. Circularity aspects | 2. Circularity indicator | 3. Priority
- Product Durability is linked to Software and data support with priority 1.
- S... |
42aa1100bc9a4736bfb6 | O-RAN.SuFG.CE | # O-RAN.SuFG.CE-v01.00
## Annex A (informative): Reduction of environmental impact through circular economy
### A.1 Equipment lifecycle aspects to consider
**Image description:** Figure/caption: Reduction of environmental impact through circular economy. Equipment lifecycle aspects to consider...
Entities:
- Lifecycl... |
81700e6d971baff9503b | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
# O-RAN Test and Integration Focus Group****End-to-End System Testing Framework Specification
**This is a re-published version of the attached final specification.**
The copying or incorporation into any other work of part or all of the material available in this specification in any f... |
f12a6a03d111f834f09c | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
# Chapter 2 Introduction
This document defines the End to End (E2E) testing framework for comprehensive E2E testing and validation of the Open RAN (O-RAN) Systems ensuring robust interoperability and operate with high performance as intended in real-world deployments.
Figure 2-1 shows ... |
f59540ebda1b53b4c684 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
# Chapter 3 O-RAN Architecture and Deployment Scenarios
This chapter gives an overview of the O-RAN Logical Architecture, O-RAN network functions, open interfaces and a list of the most considered use cases driven O-RAN Deployment Scenarios which show how the O-RAN network functions are... |
040cb8254d2973c1daca | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.1 O-RAN Logical Architecture
Figure 3-2 shows the O-RAN logical architecture [3].
**Image description:** Figure/caption: Figure 3-2: Logical Architecture of O-RAN [3].
Entities:
- Service Management and Orchestration Framework (Purple box at top)
- Non-Real Time RIC (Green box i... |
88a63ebeff061761338f | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.1 O-RAN Logical Architecture (continued)
**Table 3-2: O-RAN Open Interfaces and WGs responsible for specification**
Columns: 1. O-RAN interfaces | 2. O-RAN WG(s) | 3. O-RAN WG focus
- A1, handled by WG2, specifies Control plane protocols for the logical interface between the Non-R... |
b44221d712bee3f28bc9 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.2 O-RAN Cloud Deployment Scenarios
3
4
5
This section gives a short introduction to each of the O-RAN Cloud Deployment Scenarios abstracted from inputs O-RAN Alliance have received from global operators which have gathered the most interest and are of either current or relative... |
7f4e7683c8b135880d91 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.2 O-RAN Cloud Deployment Scenarios
#### NR Standalone (SA)
1. **(SA) Scenario A** shows the near-RT RIC, O-CU, and O-DU network functions virtualized and co-located on the same Edge Cloud platform. The O-RU deployed at the Cell site is not virtualized.
2. **(SA) Scenario B** is si... |
9aa54c52da4ebe573240 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.2 O-RAN Cloud Deployment Scenarios
#### NR Non-Standalone (NSA)
The following listed (NSA) Cloud Deployment scenarios are similar to the (SA) Cloud Deployment scenarios above listed with the LTE network functions (O-CU, O-DU) co-located with the NR network functions (O-CU, O-DU).
... |
c58dc31e0cc2cb07a44f | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 3.2 O-RAN Cloud Deployment Scenarios
#### NR Non-Standalone (NSA) (continued)
1. Use Cases and Services Requirements (e.g. network slicing, bandwidth, latency, reliability etc.).
2. Network design considerations (e.g. transport capabilities such capacity, latency between Cell site, ... |
a7135f7019571cfaf205 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
# Chapter 4 O-RAN Deployment Blueprints
### 4.1 Introduction
This chapter provides the high-level definition of the O-RAN Deployment Blueprint template which contains the necessary descriptors to build the underlying O-RAN Deployment Blueprints.
The O-RAN Deployment Blueprint is define... |
5d2e4f2702bd1c9be4b6 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.2 System Profiles
The purpose of the System Profile is to describe the O-RAN Deployment Blueprint from the E2E system perspective.
A **System Profile** consists of **System Architecture information** and a set of **System Profile parameters**.
Figure 4-2 shows the scope of the S... |
9fd9ff81da367110d014 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.2 System Profiles (continued)
1. Services Requirements (e.g. eMBB, URLLC, mMTC, combinations of these)
2. Use Cases (e.g. 3GPP use cases such as VoLTE/VoNR, O-RAN RIC-enabled use cases such as Traffic Steering, QoE Optimization, Massive MIMO Beamforming Optimization, RAN Sharing a... |
2010027c3f4073f82687 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.3 Subsystem Instance Profiles
Each of the Subsystem in the Deployment Blueprint can be described with its **Subsystem Instance Profile**.
Figure 4-3 shows the scope of the Subsystem Instance Profile in relation to the O-RAN Deployment Blueprint.
**Image description:** Figure/cap... |
bd704b80360156f68652 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.3 Subsystem Instance Profiles
#### 4.3.1 Relationship between Subsystem Type and O-RAN network functions
**Image description:** Figure/caption: Figure 4-4: Relationship between Subsystem Type and O-RAN Network Functions
Entities:
- Subsystem Type (Box)
- O-RAN Network Functions (... |
2ce266088c513d77c8b0 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.3 Subsystem Instance Profiles
#### 4.3.1 Relationship between Subsystem Type and O-RAN network functions (continued)
**Table 4-3: Relationship of Subsystem Type to the O-RAN network functions (M>1, N=1)**
Columns: 1. Subsystem Type | 2. O-RAN network function | 3. Comments
- The H... |
ed0bfed19779c97d3e44 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 4.4 Subsystem Pair Interoperability Profiles
Each pair of Subsystem Instances and the Open Interface between them can be described in the O-RAN Deployment Blueprint with its Subsystem Pair Interoperability Profile.
Figure 4-5 shows the scope of the Subsystem Pair Interoperability P... |
ff94e2c10af37ed3c77c | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
# Chapter 5 O-RAN End-to-End (E2E) Testing Framework
This chapter describes the E2E testing methodology for the holistic testing and evaluation of the O-RAN Deployment Blueprints ensuring that these Blueprints can be robustly tested and optimized, ensuring consistent high quality and pe... |
13296388e1f297c1ffb7 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 5.1 Stages and Sequence of Testing
Figure 5-2 shows the stages and sequence of testing which can be performed on the O-RAN Deployment Blueprint
1. Perform Subsystem Testing on each of the Subsystems defined in the Blueprint
2. Perform Interoperability testing with pairs of Subsyste... |
368315f0a1fcaa200ae6 | O-RAN.TIFG.E2ETSTFWK.0 | # O-RAN.TIFG.E2ETSTFWK.0-v01.00
### 5.1 Stages and Sequence of Testing (continued)
Relationships or flows: The figure illustrates various interfaces connecting these entities:
- SMO connects to O-RU [NR], O-RU [LTE], O-DU [NR], O-DU [LTE], O-CU-CP/O-CU-UP [NR], and CU [LTE] via M-Plane (Hybrid) / O1 and O1 interfaces.... |
End of preview.
TelcoLLM ORANBench training data
Training inputs for a Qwen3-8B run against ORANBench. The code lives in git; this repo carries only the data, which is too large for it.
Generated 2026-09-03.
Contents
| path | size | what it is |
|---|---|---|
train_ready_v1/ |
162 MB | cleaned Product A and B, with true token counts -- the inputs to every mix |
replay/ |
19 MB | in-domain and general replay, already through the split firewall gate |
splits_v2/ |
0 MB | the document-family split every stage is checked against |
sft_set_v1/ |
86 MB | rendered SFT / RL / dev sets, document-disjoint |
cpt_mix_b_v1/ |
210 MB | the packed CPT mix for arm B -- what training reads directly |
Licensing — read before making this public
Everything here is derived from O-RAN specifications. Their terms are
distinct from ORANBench's MIT license, and a public download does not imply a
right to redistribute. AGENTS.md requires the applicable source-document
terms to be verified and documented before publishing derived data. This repo
is intended to be private: transfer between machines, not redistribution.
The replay slices carry their own, verified licences: IETF Trust §4.c, 3GPP
TDoc (free redistribution), CC0, CC-BY, CC-BY-SA, US/EU public domain
(GSMA/Telco-Common-Corpus), and ODC-By (HuggingFaceFW/fineweb-edu).
The evaluation firewall
ORANBench is not in this repo, deliberately. It was used only to exclude contamination during generation — 1,835 of 95,691 candidate MCQs (1.9%) — and never to train, tune or select. Do not add it here.
Product A carries no benchmark leakage: 0 verbatim benchmark questions across 54,409 passages, max TF-IDF cosine 0.6986 against the 1,500 benchmark rows, nothing at 0.80.
Provenance
Every directory ships the manifest.json it was produced with: input hashes,
code hash, seeds, tokenizer revision, and the counts each stage kept and
dropped. Those are the record; this card is a summary.
Usage
hf download Jun1801/telcollm-oran-training --repo-type dataset --local-dir data/hf
Then point configs/training/*.yaml at the downloaded paths, or move the
directories into place:
data/hf/train_ready_v1 -> data/derived/train_ready_v1
data/hf/replay -> data/derived/replay
data/hf/splits_v2 -> data/derived/splits_v2
data/hf/sft_set_v1 -> artifacts/sft_set/v1
data/hf/cpt_mix_b_v1 -> artifacts/cpt_mix/b_v1
The two control mixes (no_replay, raw_only) are not uploaded — they rebuild
deterministically from train_ready_v1 with scripts/build_cpt_mix.py, and a
rebuild was verified byte-identical.
- Downloads last month
- 73