Private Information (SIP Privacy)

Description

Private information is a term used in 3GPP specifications (TS 24.196, TS 24.407, TS 24.607) to denote information that, according to IETF RFC 3323 and RFC 3325, is not permitted to be delivered to the remote end of a communication session. In essence, it refers to data that must be withheld from the far-end party to protect the privacy of the user or the network. This includes, for example, the user's identity (such as the SIP URI or telephone number) when the user has requested anonymity, as well as other sensitive parameters that should not be exposed to the remote endpoint.

The concept originates from the IETF's work on SIP privacy. RFC 3323 defines a privacy mechanism for SIP, introducing the Privacy header field, which allows a user to request that certain information be withheld. RFC 3325 specifies the use of the P-Asserted-Identity header and the Network Asserted Identity mechanism, which allows trusted network elements to assert a user's identity while still respecting privacy requests. In 3GPP, these mechanisms are adopted for IP multimedia subsystem (IMS) services, including MCPTT, MCVideo, and MCData, to ensure that users can control what information is revealed to the other party.

Architecturally, private information is handled at the SIP signaling level. When a user initiates a session with a privacy request, the SIP INVITE includes a Privacy header indicating which information should be withheld (e.g., id for identity, user for user-level privacy, header for header privacy). Network elements such as the P-CSCF, S-CSCF, and application servers (e.g., MCX AS) enforce these requests by removing or anonymizing the specified information before forwarding the message to the remote end. The P-Asserted-Identity header is used within the trusted network to convey the actual identity, but it is stripped or replaced before the message leaves the trust domain if privacy is requested.

In mission-critical services, private information handling is particularly important because users may need to conceal their identity in certain operations (e.g., undercover operations) while still being reachable and authorized. The MCX AS must therefore support privacy mechanisms and ensure that emergency calls, which may require identity disclosure for dispatch purposes, are handled appropriately. The specifications TS 24.196 (MCPTT), TS 24.407 (MCData), and TS 24.607 (MCVideo) define the precise procedures for handling private information in these contexts.

The term was introduced in Release 8, coinciding with the early deployment of IMS and the need for standardized privacy mechanisms. Its definition has remained unchanged through Release 19, indicating that the underlying IETF RFCs and the 3GPP adoption have been stable. The concept is closely tied to security and privacy requirements, and it is a key element in building trust in IP-based mission-critical communications.

Purpose & Motivation

Private information exists to address the fundamental need for privacy in IP-based communication. In traditional telephony, calling line identification (CLI) could be withheld, but the mechanisms were limited. With the advent of SIP and IMS, a more flexible and standardized approach was needed to allow users to control what identity and related information is revealed to the remote party. The IETF RFCs 3323 and 3325 provide this framework, and 3GPP adopted them to ensure that mission-critical users can benefit from the same privacy capabilities.

The motivation is particularly strong in public safety and government communications, where operational security may require that a user's identity or location not be disclosed to the other party. For example, an undercover officer may need to communicate with a dispatcher without revealing their identity to other users. Similarly, a user may wish to hide their phone number when making a call. Without a standardized privacy mechanism, such requirements would be difficult to meet consistently across vendors and networks.

Historically, the term was introduced in Release 8 as part of the IMS specifications. It has since been incorporated into mission-critical services specifications (MCPTT, MCVideo, MCData) as they were developed. The definition has remained stable, reflecting the maturity of the underlying IETF standards and the 3GPP profiles. The concept is a building block for security and privacy in 3GPP networks, and it continues to be relevant as new services are added.