Description
The Processing Cross-check Organization (PCO) is a conceptual and architectural framework defined within 3GPP specifications to ensure the integrity and correctness of processing functions, with a primary application in Lawful Interception (LI) systems. It operates by establishing mechanisms to verify that the processing of intercepted communication content and associated interception-related information (IRI) is performed accurately and without corruption or unauthorized modification. This involves cross-checking the output of processing functions against expected results or through redundant processing paths to detect errors or inconsistencies.
Architecturally, the PCO framework interfaces with key LI functional entities such as the Intercepting Control Element (ICE), which performs the actual interception within the network, and the Delivery Functions (DF2 and DF3), which handle the transport of intercepted data to the Law Enforcement Monitoring Facility (LEMF). The PCO may employ techniques like checksums, sequence numbers, cryptographic integrity protection, or comparison with duplicate processing streams to validate that data has been processed correctly from the point of interception through to delivery.
Its role in the network is primarily one of assurance and compliance. By providing a verifiable trail and validation of processing steps, the PCO helps network operators and authorities demonstrate that intercepted data is a true and accurate representation of the target's communications, which is a fundamental legal requirement for lawful interception. It addresses risks related to software bugs, hardware faults, or malicious tampering within the interception infrastructure.
Purpose & Motivation
The PCO was introduced to address the critical need for verifiable accuracy and reliability in lawful interception systems. As telecommunications networks became more complex and digital, ensuring that intercepted data remained intact and unaltered during processing became a significant technical and legal challenge. Legal frameworks worldwide mandate that intercepted evidence must be authentic and reliable to be admissible in court, necessitating technical mechanisms to prove the integrity of the interception process.
Prior to formalized concepts like PCO, reliance was placed on less systematic methods of ensuring processing integrity, which could be insufficient for rigorous legal scrutiny. The creation of the PCO framework within 3GPP standards provided a structured, standardized approach to this problem. It defines specific requirements and potential methods for cross-verification, enabling equipment vendors and network operators to implement solutions that meet stringent compliance demands. Its development was motivated by the evolving regulatory landscape and the need for international technical standards to support lawful interception across different jurisdictions and network technologies.
What changed in its specifications
The latest release-to-release comparison of specifications that define PCO. Each summary describes the whole specification, not only this term.
Rel-19 added IMS disaster prevention and restoration enhancements to TS 23.380, including detection of EPC/5GC NF failures, restoration of IMS sessions, and PCRF/PCF bypass procedures.
Full comparison in TS 23.380 →Rel-19 adds MPQUIC-IP and MPQUIC-E steering, an ATSSS status parameter, non-3GPP access path switching, and ATSSS rule provisioning with MPQUIC-IP signalling over EPC-connected 3GPP access.
Full comparison in TS 24.193 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (17 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- EDC related PCO parameters usage TS 24.501CR3848
- PVS PCO parameter providing TS 24.501CR3382
- Correction of PCO related terminology TS 24.501CR3434
- Delete the PCO parameters after handover between 3GPP and non-3GPP access TS 24.501CR3737
- UE is allowed to use PCO IE after inter-system change from N1 mode to S1 mode TS 24.501CR4027
- QoS error checks for unstructured PDU session type in PCO TS 24.501CR4322
+ 2 more changes
- Resolving the EN related to the inclusion of SDNAEPC support indicator in the PCO or the ePCO TS 24.301CR3871
- Remove description on inclusion of ATSSS response in (e)PCO TS 24.301CR3890
- Cleanup of PCO parameters naming TS 24.301CR3889
- QoS error checks for unstructured PDU session type in PCO TS 24.501CR4462
- UE handling on PCO or EPCO syntactical errors in QoS operations TS 24.501CR4879
Defining Specifications
3GPP specifications that define or reference PCO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.380 vk00 | IMS Restoration Procedures | Rel-20 read |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 read |
| TR 23.981 vj00 | IPv4 IMS Interworking and Migration Study | Rel-19 read |
| TS 24.193 vk10 | ATSSS Stage 3 Procedures | Rel-20 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.244 vj00 | Wireless LAN Control Plane Protocol | Rel-19 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TR 26.996 vj10 | Immersive Audio for Split Rendering Performance | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.274 vk00 | GTPv2-C Control Plane Protocol | Rel-20 read |
| TS 29.806 vc10 | P-CSCF Restoration Analysis & Solutions | Rel-12 read |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 read |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TR 38.859 vi10 | Technical Report | Rel-18 read |