Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Private network traffic

Private network traffic

Services →

Private network traffic is the traffic sent to or received from a Next Generation Network for processing according to enterprise-specific rules, enabling closed user groups and enterprise communications.

Introduced
Rel-8
Where
Services › IMS
Specifications
2 specs
Private network traffic Description Purpose What changed Neighbours Specifications

Description

Private network traffic refers to traffic that is sent to or received from a Next Generation Network (NGN) for processing according to an agreed set of rules specific to an enterprise or a community of closely related enterprises. In the context of the IP Multimedia CN Subsystem (IM CN), this type of traffic is normally confined within a single enterprise, but it can also exist between two different enterprises if not precluded by regulatory requirements. The concept was introduced in 3GPP Release 8 and has been maintained through subsequent releases with a significant wording change in Release 17 to align with NGN terminology.

The architecture supporting private network traffic involves the IM CN subsystem, which includes core network elements such as Call Session Control Functions (CSCFs), Home Subscriber Servers (HSSs), and Application Servers (ASs). These elements process private network traffic according to enterprise-specific rules, which may include routing policies, access control, and service invocation. The traffic is typically identified by specific identifiers or tags that allow the network to distinguish it from public traffic. For example, a Private User Identity or a specific service profile may be used to mark traffic as private.

How it works: When a user equipment (UE) initiates a session, the network determines whether the traffic is private based on subscription data and enterprise agreements. The CSCF, acting as the central control element, applies the agreed rules to route the traffic appropriately. This may involve dedicated bearers, specific QoS parameters, or even dedicated network slices. The rules are often stored in the HSS and enforced by the CSCF and other nodes. Private network traffic can be exchanged between UEs within the same enterprise or between UEs of different enterprises, provided that inter-enterprise agreements and regulatory constraints allow it.

Key components include the enterprise's own network infrastructure (e.g., a private IP network or a dedicated NGN), the 3GPP network elements that handle the traffic, and the interfaces between them. The IM CN subsystem provides the session control, while the transport layer (e.g., IP) carries the actual data. Security mechanisms such as IPsec and TLS may be used to protect private traffic. The concept is closely related to enterprise communications, closed user groups (CUGs), and network slicing, as private network traffic can be carried over dedicated slices.

In later releases, particularly from Release 17 onwards, the definition was updated to include traffic sent to or received from an NGN, reflecting the evolution towards 5G and the integration of NGN concepts. This change acknowledges that private network traffic may traverse not only the IM CN subsystem but also other NGN components. The term remains relevant for enterprises seeking secure, isolated communication services within a public land mobile network (PLMN).

Purpose & Motivation

Private network traffic exists to enable enterprises to use 3GPP networks for their internal communications while maintaining control over routing, security, and service quality. Before its introduction, enterprises relied on private branch exchanges (PBXs) or leased lines, which lacked mobility and integration with mobile networks. The IM CN subsystem provided a standardized way to deliver IP-based multimedia services, but public traffic handling did not cater to enterprise-specific rules. Private network traffic fills this gap by allowing enterprises to define and enforce their own policies within the operator's network.

The concept addresses the need for closed user groups and enterprise-specific services, such as corporate VPNs, internal conferencing, and unified communications. It also supports regulatory requirements by allowing traffic to be confined within national boundaries or specific enterprises. The evolution to include NGN reflects the convergence of fixed and mobile networks, enabling enterprises to extend their private networks across different access technologies.

By defining private network traffic, 3GPP provides a framework for operators to offer enterprise services that are secure, reliable, and customizable. This fosters new business models and revenue streams for operators while meeting the communication needs of enterprises.

What changed in its specifications

The latest release-to-release comparison of specifications that define Private network traffic. Each summary describes the whole specification, not only this term.

TS 24.229Rel-18 → Rel-19

Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.

Full comparison in TS 24.229 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition introduced: traffic sent to the IM CN subsystem for processing according to enterprise-specific rules. Private network traffic is normally within a single enterprise but can exist between enterprises if not precluded by regulatory reasons.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8, with only minor formatting differences.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Wording changed significantly: now defined as 'traffic sent to or received from an NGN for processing according to an agreed set of rules specific to an enterprise or a community of closely related enterprises'. This reflects the integration of NGN concepts and broadens the scope beyond IM CN subsystem.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-17.

Defining Specifications

3GPP specifications that define or reference Private network traffic, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.519 vj00 NGN Business Communication Requirements Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read