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

Glossary term · Interface

N7

Reference point between the SMF and the PCF

Interface →

N7 is the 3GPP reference point between the SMF and PCF, carrying session-level policy control that allows the SMF to obtain PCC rules for QoS, gating, charging, and traffic steering.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
1 specs
N7 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

N7 is the 3GPP reference point between the Session Management Function (SMF) and the Policy Control Function (PCF) in the 5G Core. It is the session-level policy control interface used to obtain, update, and release policy decisions that govern a PDU Session. In the service-based architecture introduced in Rel-15, N7 corresponds to the Npcf_SMPolicyControl service, which is exposed by the PCF and consumed by the SMF. Through this interface, the SMF can request policy decisions for a specific UE, PDU Session, network slice, DNN, and set of application requirements, and the PCF can return PCC rules that the SMF enforces by configuring the UPF and related network functions.

The operation of N7 begins when the SMF needs to establish or modify a PDU Session. The SMF creates a policy association with the PCF and provides session context such as subscriber identity, S-NSSAI, DNN, UE location or access information, and requested session parameters. The PCF evaluates this context against subscriber policy, slice policy, operator policy, and possibly application information supplied by an Application Function through the NEF. It then returns one or more PCC rules. These rules may define QoS parameters, packet flow detection criteria, gating decisions, charging characteristics, traffic steering instructions, and event reports that the SMF must provide to the PCF. The SMF translates these policy decisions into forwarding and QoS enforcement rules for the UPF via N4 and may coordinate with the AMF for access and mobility aspects.

N7 is not only an initial setup interface; it supports dynamic policy control during the lifetime of a session. The PCF can push updates when network conditions change, when a new application service is detected, when congestion occurs, or when subscriber profile changes. Conversely, the SMF can report events such as session establishment, modification, release, or changes in UE context. This bidirectional policy exchange allows the network to react to real-time conditions rather than relying on static configuration. For example, a policy rule may grant a higher priority QoS flow to a specific application, while another rule may steer traffic to a local edge UPF when the UE enters a particular area.

A key architectural benefit of N7 is the separation of policy decision-making from session execution. The SMF remains responsible for session management, UPF selection, and packet forwarding configuration, while the PCF remains responsible for centralized policy decisions. This separation makes the 5G Core more modular and supports network slicing, because each slice can have distinct policy requirements. The PCF can apply slice-specific rules, while the SMF enforces them in the appropriate UPF. In roaming scenarios, N7 can involve the home PCF and, depending on the roaming model, policy interactions with visited network functions, allowing the home operator to retain policy authority while the visited network provides transport and radio access.

N7 also supports charging and lawful intercept requirements. PCC rules can carry charging identifiers and gating states, enabling the SMF and charging function to apply the correct billing treatment. Event reporting allows the PCF to know when a session has changed or released, which is important for policy cleanup and charging correlation. Although N7 is a service-based interface implemented over HTTP/2 and JSON, its logical role is that of the policy control plane between session management and policy enforcement. It is essential for dynamic QoS, application-aware traffic handling, and slice-specific service delivery in 5G networks.

Purpose & Motivation

N7 exists to bring dynamic, centralized policy control into the 5G Core session management process. In earlier 4G EPC architectures, policy control was carried by the Gx interface between the PGW and PCRF, and the PCRF provided rules to the gateway. 5G replaced this with a service-based architecture where the SMF and PCF interact through N7. The motivation was to make policy control more modular, scalable, and suitable for network slicing, cloud-native deployment, and application-aware services. By exposing policy control as a service, the PCF can serve multiple SMFs and support more flexible event-driven updates.

The limitations of previous approaches were partly due to tightly coupled session and policy functions, less flexible service discovery, and difficulty supporting per-slice or per-application policies at scale. 4G policy control was effective for QoS and charging, but 5G introduced new requirements such as ultra-reliable low-latency communication, massive IoT, network slicing, and edge computing. These use cases require policies that can change quickly based on UE context, network load, slice selection, and application needs. N7 addresses this by allowing the SMF to request policy decisions for a specific session and receive PCC rules that can be enforced immediately in the UPF.

N7 also supports the separation of control responsibilities that is central to 5G. The SMF manages the session and user-plane configuration, while the PCF decides policy. This separation enables operators to update policy logic without changing session management code, and to deploy PCFs as centralized or distributed services. It also supports roaming and multi-tenant networks, where different slices or customers may have different policy requirements. In this sense, N7 is the mechanism that makes 5G policy control both dynamic and architecturally clean.

What changed in its specifications

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

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9
  • N7 counterpart in another generation: Gx
    “This reference point corresponds to the Gx which resides between the PCEF in the IP-Edge and the PCRF.” TS 23.203

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

The N7 reference point between the SMF and the PCF is defined for the first time in the 5G system architecture specification.

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read