Description
The Procedure Transaction Identity (PTI) is a fundamental element in 3GPP signaling protocols, particularly within the Non-Access Stratum (NAS) and certain Access Stratum (AS) procedures. It serves as a local identifier, assigned at the initiation of a transaction, to uniquely tag all subsequent messages exchanged for that specific procedure between two peer entities, such as a User Equipment (UE) and the core network. This allows multiple, simultaneous signaling transactions (e.g., multiple session management or mobility management procedures) to be processed in parallel without confusion. The PTI is included in the protocol header of relevant messages, enabling the receiving entity to correctly associate an incoming message with the appropriate ongoing procedure context and state machine.
Architecturally, the PTI operates within the control plane protocols defined in specifications like 24.301 (NAS for EPS) and 24.501 (NAS for 5GS). It is a critical component for session management procedures, such as the Protocol Data Unit (PDU) Session Establishment or Modification. When a UE initiates a procedure, it selects an unused PTI value and includes it in the initial request message. The network echoes this same PTI in its response messages. This pairing ensures that even if messages from different transactions arrive out of order or interleaved, each entity can demultiplex them correctly. The PTI value space is managed locally by the entity initiating the transaction; it is not a globally unique identifier but is unique for the duration of the transaction between the two communicating peers.
The role of the PTI extends to ensuring reliable signaling and preventing state corruption. By providing a clear correlation tag, it supports complex procedures that involve multiple message exchanges, such as handovers or quality-of-service (QoS) negotiations. In the radio access network, specifications like 36.321 (LTE MAC) also utilize similar transaction identity concepts for certain MAC layer procedures, highlighting its importance across different protocol layers. Without a mechanism like the PTI, managing concurrent signaling would require more complex sequencing or serialization, increasing latency and the risk of errors. Its simplicity and effectiveness make it a cornerstone of 3GPP's robust signaling architecture.
Purpose & Motivation
The PTI was introduced to solve the fundamental problem of managing multiple, simultaneous signaling transactions between network entities. In early mobile systems, signaling procedures were often simpler or more serialized, but as networks evolved to support complex services, concurrent procedures became necessary. For instance, a UE might need to activate a data session while simultaneously performing a location update or receiving a SMS. Without a transaction identifier, correlating request and response messages in such scenarios would be error-prone, leading to protocol failures or misapplied operations.
Its creation was motivated by the need for efficient and reliable state machine management within connection-oriented signaling protocols. Prior approaches might have relied on implicit sequencing or dedicated physical channels, which were not scalable for packet-switched, IP-based core networks like those defined from 3GPP Release 8 (EPS) onward. The PTI provides a lightweight, in-band solution that adds minimal overhead to messages while enabling clear transaction isolation. This is particularly critical in the NAS layer, where the UE and core network must maintain synchronized views of multiple ongoing procedures, such as PDU session management, bearer resource allocation, and mobility management events.
Historically, the concept draws from transaction identifiers used in other telecommunication and data networking protocols. Its standardization within 3GPP ensured interoperability across vendors and network deployments. By addressing the limitation of ambiguous message association, the PTI enhances network reliability, supports advanced features like network slicing and QoS flows, and underpins the seamless user experience expected in modern 4G and 5G networks. It solves the problem of concurrency in signaling, which is a prerequisite for the high-performance, multi-service capabilities of contemporary mobile systems.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (609 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the PTI (Procedure Transaction Identity) function was newly introduced to support QoS differentiation within the WLCP bearer procedures, specifically for bearer setup, modification, and release. This included enhanced abnormal case handling and TFT checking with error handling for these WLCP procedures. Furthermore, the update enabled the association of a unique user plane identity per WLCP bearer.
- WLCP bearer setup procedure for QoS differentiation TS 24.244CR0046
- WLCP bearer modification procedure for QoS differentiation TS 24.244CR0047
- WLCP bearer release procedure for Qos differentiation TS 24.244CR0048
- Abnormal case handling for WLCP bearer procedures TS 24.244CR0049
- TFT checking and error handling in WLCP bearer setup and modify procedures TS 24.244CR0051
- User plane identity per WLCP bearer TS 24.244CR0053
+ 128 more changes
In Release 16, the PTI function was updated to support new procedures including the UE-requested V2X policy provisioning procedure, the service request procedure for UE attached for access to RLOS, and the PDU session establishment procedure to support MA PDU sessions. It was also adapted for the service gap control in 5GS via the UCU procedure and for the slice-specific authentication and authorization procedure. These enhancements integrated PTI into the management of these new 5G system capabilities and service scenarios.
- Adds UE Radio Capability ID in signalling procedures TS 23.401CR3503
- PDN connectivity procedure for RLOS attached UEs TS 24.301CR3163
- Service request procedure for UE attached for access to RLOS TS 24.301CR3219
- Types of EMM procedures for RLOS TS 24.301CR3269
- Support of UE paging probability for WUS-procedure part TS 24.301CR3304
- UE radio capability ID assignment via GUTI reallocation procedure TS 24.301CR3328
+ 95 more changes
In Release 17, the PTI function was extended to support new Multi-USIM (MUSIM) procedures, specifically for a "Leaving" procedure initiated via a Service Request to remove paging restrictions in both EPS and 5GS. This included ensuring the UE does not initiate this Service Request-based Leaving procedure when an Emergency service is ongoing. Furthermore, the updates applied to MUSIM UEs using control plane CIoT EPS and 5GS optimizations for the same paging restriction removal purpose.
- Introduction of Leaving procedure - SR based TS 23.401CR3625
- Using Service Request procedure for removing paging restrictions in EPS for a Multi-USIM UE TS 24.301CR3517
- The MUSIM capable UE shall not initiate Service Request procedure for Leaving the network if Emergency service is ongoing TS 24.301CR3521
- Leaving procedure and Reject Paging Indication for Multi-USIM UEs in EPS TS 24.301CR3534
- Introducing IMSI Offset to Attach and TAU procedures for MUSIM handling in EPS TS 24.301CR3527
- Using Service Request procedure for removing paging restrictions in EPS for MUSIM UE that uses the control plane CIoT EPS optimization TS 24.301CR3564
+ 169 more changes
In Release 18, the PTI function was extended to manage new procedure rejections and authorizations, specifically for rejecting PDN connectivity procedures due to lack of UE support for SDNAEPC and for authorizing A2X direct C2 communication within EPS procedures. It also gained functionality to transport messages for network-requested UE policy management procedures in EPS. Furthermore, the PTI scope was updated to handle the abortion of registration procedures when a selected non-3GPP interworking function is incompatible with the allowed NSSAI.
- Indicating the capability of supporting SDNAEPC during the PDN connectivity procedure TS 24.301CR3851
- Rejecting PDN connectivity procedure due to SDNAEPC is not supported by the UE TS 24.301CR3852
- Exchanging the SDNAEPC EAP message in ESM procedures TS 24.301CR3853
- Include DN-specific identity in PDN CONNECTIVITY REQUEST TS 24.301CR3861
- Authorization of A2X direct C2 communication in EPS - additional procedures TS 24.301CR3891
- URSP provisioning in EPS - procedures TS 24.301CR3897
+ 115 more changes
In Release 19, the PTI function was enhanced to support new Store and Forward (S&F) satellite operation procedures, including updates to the Attach, Service Request, and Tracking Area Update (TAU) procedures. Specifically, new S&F-related information elements, such as the S&F configuration IE and the S&F monitoring list, were integrated into these NAS procedures. Furthermore, procedures were updated to handle S&F-specific scenarios, such as rejecting NAS procedures for UEs not supporting S&F and resolving timers like the S&F wait timer during attach and service request.
- Procedures for Store and Forward Satellite Operations TS 23.401CR3824
- Procedure updates for S&F TS 23.401CR3861
- Update EMM procedures to support the storage of the information TS 24.301CR4159
- Update procedures to consider satellite E-UTRAN in the IE TS 24.301CR4160
- Addition of S&F configuration IE in Service Request procedure TS 24.301CR4236
- RAT restriction during service request procedure TS 24.301CR4269
+ 72 more changes
Explore further
Broader topics and technologies where PTI plays a role.
Defining Specifications
3GPP specifications that define or reference PTI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vj50 | Evolved Packet System (EPS) Stage 2 Description | Rel-19 |
| TS 24.244 vj00 | Wireless LAN Control Plane Protocol | Rel-19 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 |
| TS 29.274 vj50 | GTPv2-C Control Plane Protocol Specification | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |
| TS 36.213 vj10 | LTE Physical Layer Procedures | Rel-19 |
| TS 36.321 vj00 | E-UTRA MAC Protocol Specification | Rel-19 |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 |