PSA

Product Specific Applications

Services
Introduced in Rel-8
A 3GPP concept for applications that are specific to a particular product or service offering, often with unique requirements. It is a broad categorization used in service requirements and architecture specifications to model and manage specialized application functions within the 5G system.

Description

Product Specific Applications (PSA) is a term used across numerous 3GPP specifications to denote application functions or services that are not generic but are tied to a specific commercial product, service bundle, or use case. It is not a single protocol or network function but a conceptual entity used in requirement and architectural modeling. PSAs represent the logical endpoint or source of service-specific traffic and signaling that the 5G System (5GS) must support. They are often discussed in the context of service-based architecture, network exposure, and quality of service (QoS) differentiation.

Architecturally, a PSA interacts with the 5G Core Network (5GC) through defined interfaces, primarily the Network Exposure Function (NEF) or directly with the User Plane Function (UPF) for traffic steering. The PSA can be an Application Function (AF) as defined in the 5GC architecture, but with the distinguishing characteristic of being product-specific. This means its communication with the network carries requirements unique to the product it enables, such as specific QoS parameters (e.g., latency, reliability), charging policies, or mobility restrictions. The 5GC uses the information provided by or about the PSA to apply appropriate network policies.

How it works involves the PSA (or an entity representing it, like an AF) providing session or service-related information to the 5GC. For example, a PSA for a real-time gaming service might request a guaranteed bit rate and low-latency QoS flow for its users via the NEF. The Policy Control Function (PCF) would then generate policies based on this request and the user's subscription, and the Session Management Function (SMF) would enforce them by configuring the UPF accordingly. The role of the PSA concept is to provide a formal model for these product-specific interactions, ensuring the network can be dynamically tailored to support a vast array of specialized services beyond basic connectivity, which is central to the 5G vision of network-as-a-service.

Purpose & Motivation

The concept of Product Specific Applications exists to address the need for the 3GPP system to support a diverse and ever-growing ecosystem of specialized services, each with unique network requirements. In early mobile networks, services were largely monolithic (e.g., voice, SMS, basic internet). As networks evolved, operators and third parties began offering differentiated products like streaming bundles, IoT solutions, and enterprise VPNs, which required the network to treat their traffic differently.

PSA provides a standardized way to model these bespoke services within the 3GPP architecture. It solves the problem of how to formally describe and integrate the requirements of a specific commercial product into the network's control and management planes. Before such modeling, enabling a new service often required proprietary integrations or broad, inefficient network configurations. The PSA concept, particularly as refined in the 5G service-based architecture, allows for dynamic, policy-driven network slicing and QoS management on a per-application or per-product basis. This enables operators to efficiently monetize their networks by offering tailored connectivity as a product feature.

Key Features

  • Represents application functions tied to specific commercial products or services
  • Interacts with 5G Core via Network Exposure Function (NEF) or as an Application Function (AF)
  • Can influence network policies for QoS, charging, and traffic routing
  • Enables dynamic service-specific network behavior
  • Central to the implementation of network slicing for vertical services
  • Used in requirement specifications to capture unique service needs

Evolution Across Releases

Rel-8 Initial

Initial conceptual use of PSA in the context of EPS and IMS, primarily in service requirement specifications (e.g., 22-series) to denote services with specific needs beyond default bearer services.

Defining Specifications

SpecificationTitle
TS 23.501 3GPP TS 23.501
TS 23.527 3GPP TS 23.527
TS 23.558 3GPP TS 23.558
TS 23.700 3GPP TS 23.700
TS 23.794 3GPP TS 23.794
TS 26.803 3GPP TS 26.803
TS 26.804 3GPP TS 26.804
TS 26.806 3GPP TS 26.806
TS 28.822 3GPP TS 28.822
TS 28.833 3GPP TS 28.833
TS 29.244 3GPP TS 29.244
TS 29.512 3GPP TS 29.512
TS 29.513 3GPP TS 29.513
TS 29.514 3GPP TS 29.514
TS 29.519 3GPP TS 29.519
TS 29.892 3GPP TS 29.892
TS 32.102 3GPP TR 32.102
TS 32.150 3GPP TR 32.150
TS 33.739 3GPP TR 33.739