Legacy 3GPP TS 33.106, 33.107, and 33.108
The older 33.106/107/108 family remains important for legacy GSM, UMTS, EPS, and IMS deployments and for understanding historical handover. New designs should determine whether the modern 33.126/127/128 family applies, whether legacy coexistence is required, and how national profiles bridge them.
Safety boundary: this chapter teaches lawful, governed system design from public standards. It does not provide operational targeting, activation, decryption, surveillance-evasion, or covert collection instructions.
The mental model
| Concept | Plain meaning | Control that must travel with it |
|---|---|---|
| 33.106 | Legacy LI requirements | Do not use its title alone to claim modern 5G coverage |
| 33.107 | Legacy architecture and functions | Map actual supported network generation |
| 33.108 | Legacy handover interface | Coordinate with ETSI IP-delivery profiles |
| Coexistence | Old and new functions operate during migration | Prevent duplicate or missing handover |
| Semantic mapping | Equivalent concepts are related across families | Do not invent equivalence where meaning changed |
| Retirement | Legacy support is removed with receiver agreement | Inventory consumers and active legal obligations first |
Apply it as a controlled workflow
- Inventory network generations, services, and receiver profiles.
- Classify each legacy standard as required, transitional, or retired.
- Define one authority for task state across old and new paths.
- Use synthetic dual-path comparison and reconciliation.
- Cut over by bounded service cohort with rollback.
- Prove no active cases, dependencies, or legal retention duties remain before removal.
Evidence to demand
- The standards matrix distinguishes legacy and modern families.
- Dual delivery cannot create unexplained duplicates.
- Migration preserves correlation and evidence.
- Retired endpoints, keys, and privileges are actually removed.
Failure to reason about
A 5G core supports modern procedures while an IMS voice service still relies on legacy handover. Declaring the whole network “5G compliant” hides the mixed profile. Model capability by service, function, and release.
Feynman check
Old and new mobile roads can coexist. Draw which service uses which road, make one traffic controller authoritative, and retire the old road only after every traveler is accounted for.