Running tests
Logs, PCAPs, and evidence
Retrieve and interpret execution artifacts: TTCN-3 engine logs, UE logs, MAC/NAS PCAPs, message sequence charts, and Wireshark setup.
7 min read
Every execution keeps four artifact classes. Together they are the evidence chain a certification body expects, and the input the AI Copilot reasons over.
Download artifacts
bashbash
aeon exec artifacts --id 4821 --list aeon exec artifacts --id 4821 --get ue.log --get ue_nas.pcap --out ./evidence/ aeon exec artifacts --id 4821 --all --out ./evidence/
Open PCAPs in Wireshark
bashbash
# NAS-5GS and MAC-NR dissectors ship with Wireshark 3.6+ wireshark ./evidence/ue_nas.pcap # useful display filters nas-5gs.mm.message_type == 0x41 # Registration Request nas-5gs.mm.message_type == 0x42 # Registration Accept nas-5gs.mm.message_type == 0x44 # Registration Reject mac-nr.rnti-type == 3 # C-RNTI
Artifact classes
| Artifact | Use |
|---|---|
| engine.log | TTCN-3 verdict trail — which alt branch matched and why |
| ue.log | Device-side layer logs (PHY/MAC/RRC/NAS) |
| *.pcap | Frame-level evidence for the report and for Wireshark |
| msc.json | Message sequence chart rendered in the portal |
| rf.csv | Per-slot RSRP/SINR/BLER samples from the lane |
Ask the Copilot first
bashbash
aeon copilot explain --exec 4821 aeon copilot explain --exec 4821 --focus "why did T3510 expire"
noteThe Copilot cites the 3GPP clause and the exact log line. Treat it as a first-pass triage engineer, then verify against the PCAP.
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.