Understanding TC_6_1_1_1
Line-by-line walkthrough of test case TC_6_1_1_1 — purpose, preamble, expected message sequence, verdict criteria, and the three ways it commonly fails.
8 min read
TC_6_1_1_1 is the case everyone runs first: RRC connection establishment followed by initial registration. It is a good teaching case because it exercises PHY, MAC, RLC, PDCP, RRC, and NAS in one 15-second window.
Test purpose
Verify that the UE, on receiving a valid RRCSetup in response to an RRCSetupRequest with establishmentCause set for mobile-originated signalling, transmits a correctly formed RRCSetupComplete carrying an initial Registration Request, and completes registration.
Preamble
- Cell configured per the reference conditions for the band under test.
- UE in state 1 (switched off), USIM inserted with test credentials.
- Security context absent; no valid 5G-GUTI stored.
Expected sequence
1 UE -> SS : PRACH preamble
2 SS -> UE : Random Access Response
3 UE -> SS : RRCSetupRequest (establishmentCause=mo-Signalling)
4 SS -> UE : RRCSetup
5 UE -> SS : RRCSetupComplete { Registration Request (initial) }
6 SS -> UE : Authentication Request
7 UE -> SS : Authentication Response
8 SS -> UE : Security Mode Command
9 UE -> SS : Security Mode Complete
10 SS -> UE : Registration Accept (5G-GUTI assigned)
11 UE -> SS : Registration Complete
verdict: passThe three common failures
| Stops at | Verdict | Real cause |
|---|---|---|
| step 2 | inconc | PRACH power — rf.tx_gain too low |
| step 5 | fail | Malformed RRCSetupComplete or wrong establishmentCause |
| step 9 | fail | K_AMF derivation / capability replay mismatch |
Run it now
aeon exec run --case TC_6_1_1_1 --build rc3 --follow
noteThis case takes about 14 seconds on a healthy lane. If it takes 45, you have a timer expiry and a retry, not a slow lane.
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.