---
title: "3GPP TS 33.128: protocols and procedures"
chapter: "15"
---

# 3GPP TS 33.128: protocols and procedures

TS 33.128 is the Stage 3 protocol-and-procedure specification. Engineering teams need to understand its role, version dependencies, conformance, and security properties. This fieldbook intentionally does not reproduce wire-level tasking or collection procedures.

> **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 |
|---|---|---|
| **Stage 3** | Defines interoperable protocol behavior for Stage 2 functions | Use the normative specification under controlled access |
| **Procedure state** | Messages implement authorized lifecycle and delivery behavior | State machines reject impossible transitions |
| **Encoding/schema** | Structured objects support interoperability | Parsing success is not authorization |
| **Error behavior** | Peers can report bounded failures | Errors must not leak target or topology details |
| **Security association** | Peers authenticate and protect transport | Key lifecycle and endpoint authorization are separate |
| **Release compatibility** | Protocol edition aligns with architecture and requirements | Mixed releases need a tested profile |

## Apply it as a controlled workflow

1. Pin matching 33.126, 33.127, and 33.128 release versions.
2. Build an abstract state/conformance model without production target data.
3. Validate peer identity, authorization, replay resistance, and schema before state change.
4. Use synthetic fixtures for positive and negative interoperability tests.
5. Fuzz parsers and test resource exhaustion in isolated assurance environments.
6. Promote only signed, reviewed protocol implementations with rollback.

## Evidence to demand

- Conformance results identify exact release, options, and national profile.
- Malformed inputs cannot bypass authorization or exhaust privileged systems.
- Secrets and sensitive parameters are absent from ordinary logs and crash dumps.
- Protocol upgrade has dual-version, rollback, and reconciliation evidence.

## Failure to reason about

A protocol parser accepts a valid message after the related case was revoked because authorization was checked only when the session opened. Every state-changing procedure must evaluate current authorization, not just transport authentication.

## Feynman check

33.128 is the detailed grammar for approved machines. Knowing grammar does not grant permission to start the conversation.