File size: 2,274 Bytes
7b6d659 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 | import streamlit as st
st.markdown(
"""
# UE Capability Parser Documentation
## 1. Objective
Parse UE capability text exports (`.txt`) and build structured 3GPP-oriented output sheets.
## 2. When to use this tool
Use this page when you need to:
- identify LTE/UTRA/GERAN/NR band support
- inspect CA combinations and consistency
- infer release information
- optionally assess VoLTE support confidence
- optionally compare CA combinations to a benchmark list
## 3. Input files and accepted formats
- Required: one or multiple UE capability files (`.txt`)
- Optional benchmark file (when enabled): `.csv`, `.json`, or `.txt`
## 4. Required content in inputs
- UE files should contain decoded capability tree text (Actix/TEMS-like exports).
- Benchmark file should include normalized combos, typically one combo per line/row.
## 5. Step-by-step usage
1. Open `Apps > UE Capability Parser`.
2. Upload one or more UE capability `.txt` files.
3. Enable/disable `VoLTE assessment`.
4. Optionally enable `CA benchmark diff` and upload benchmark file.
5. Click `Process`.
6. Review sheet tabs and download the Excel report.
## 6. Outputs generated
Main output sheets include:
- `Summary`
- `Bands_LTE`, `Bands_UTRA`, `Bands_GERAN`, `Bands_NR`
- `CA_Combinations`, `CA_Assessment`
- `ENDC_MRDC`, `Features`
- `VoLTE_Assessment` (when enabled)
- `Release_Inference`
- `Benchmark_CA_Diff` (when benchmark provided)
- `Parse_Warnings`
## 7. Frequent errors and fixes
- Parsing fails on upload.
- Fix: verify file is plain text and not binary/empty.
- Missing expected sheets.
- Fix: input may not contain corresponding sections; check `Parse_Warnings`.
- Benchmark mismatch confusion.
- Fix: benchmark diff is informative and does not override parser interpretation.
## 8. Minimal reproducible example
- Input: `samples/ue_capability.txt`
- Action: upload file and click `Process`.
- Expected result: populated `Summary` + downloadable `UE_Capability_Parsed.xlsx`.
## 9. Known limitations
- Results depend on source text completeness.
- Inference quality decreases when capability sections are missing.
- Benchmark comparison quality depends on benchmark normalization.
## 10. Version and update date
- Documentation version: 1.0
- Last update: 2026-02-23
"""
)
|