telecom-intelligence-model-v7-merged API & Inference Endpoint | FriendliAI
README
License: apache-2.0
What it does
The model reasons step-by-step over telecom operational data to:
Root cause analysis — diagnose KPI degradations from PM counter data across Ericsson, Huawei, Nokia, and ZTE RAN/Core nodes
5G NR deep knowledge — SSB beam management (P1/P2/P3/BFR), NR numerology (μ=0–4, SCS, slot duration, PRBs per bandwidth), CORESET/PDCCH blind decoding, BWP switching, PUCCH formats 0–4 (HARQ-ACK/SR/CSI), SIB1 contents, F1/E1 interface (CU/DU split), RRC_INACTIVE state (I-RNTI, RNA, Resume), SDAP layer (QoS flow→DRB mapping)
LTE RAN — RRC/ERAB/HO KPI chains with correct Ericsson pmRrcConnEstabSucc/pmErabEstabSuccInit/pmHoExeSuccLteIntraF formulas; inter-frequency HO (A2/A3/A4/A5 events, measurement gaps); LTE TA/TAU; eICIC/ABS (HetNet, CRE, FeICIC); S1 release causes; RSRP→SINR→CQI→MCS link adaptation chain with OLLA
5G Core NF attribution — names the exact failing NF (AMF, SMF, UPF, PCF, AUSF, UDM) and interface (N4/PFCP, N8, N11, N7, N10, NGAP) rather than vague "core network" answers; AMF overload scenarios, SMF/PFCP session failure RCA, UPF pod crash diagnosis
PRB utilisation — correct formula for all LTE bandwidths and 5G NR; differentiates congestion vs RF root cause
SON Energy Saving — binary ACTIVATE / DO NOT ACTIVATE decisions with threshold reasoning (PRB, UE count, neighbour overlap, NOC approval)
Multi-vendor counter normalisation — Ericsson pm*, Huawei L.* / VS.5G.*, Nokia RRC_CONN_*, ZTE LTE PM naming conventions; maps all to equivalent KPI formulas
TASK: Anomaly DetectionVENDOR: Ericsson | Cell: ENB042-CELL07 | Granularity: 15 minpmRrcConnEstabAtt=941, pmRrcConnEstabSucc=908pmErabEstabAttInit=941, pmErabEstabSuccInit=824pmHoExeAttLteIntraF=378, pmHoExeSuccLteIntraF=288Analyse for anomalies. Derive all KPIs showing your arithmetic, then state the verdict.
5G NR beam failure diagnosis:
text
After an antenna upgrade at a 5G NR cell, UEs near the cell edge show intermittentdisconnections. Logs show frequent BFR (Beam Failure Recovery) events.Explain the SSB beam management procedure (P1/P2/P3), what triggers BFR,and which PM counters to check.
5GC NF root cause:
text
SMF-PROD-03: PDU_Session_Estab_SR=58.3% (baseline 99.1%), N4_HeartbeatTimeout_Rate=22.1%(baseline 0%), N11_SR=99.8%, N7_SR=99.6%, SMF_CPU_Util=41%.Diagnose the root cause. Which NF is failing and on which interface?
Ericsson AMOS CLI:
text
TASK: AMOS CLI command generationVENDOR: Ericsson | Node: GNBDU-SITE-05Generate AMOS commands to:1. Lock all NRCellDU cells (administrativeState)2. Retrieve pmNrRrcConnEstabSucc and pmNrRrcConnEstabAtt for all cells3. Unlock NRCellDU=Cell-1
Limitations
Output quality depends on how explicitly vendor, counter names, and task type are stated in the prompt. The structured prompt format shown above consistently outperforms free-form questions.
The model was not trained on proprietary network configurations or live traffic data. It reasons from 3GPP specifications and publicly available vendor documentation.
Computed KPI values are arithmetic derivations from counter inputs provided in the prompt — the model does not connect to live network systems.
Recommended for augmenting, not replacing, experienced RF/Core network engineers.
Citation
bibtex
@misc{telecom-intelligence-v7, author = {mindfossil}, title = {Telecom Intelligence Model v7 — Qwen2.5-7B Fine-Tuned for Network Operations}, year = {2026}, publisher = {HuggingFace}, url = {https://huggingface.co/mindfossil/telecom-intelligence-model-v7-merged}}
LTE UL power control (P0, alpha, TPC)
PDCP lossless HO (SN Status Transfer + forwarding)