Description
A ProSe-enabled Network is the network-side counterpart to ProSe-capable UEs: it is a mobile network that supports ProSe Discovery and/or ProSe Communication. The definition is deliberately broad, covering networks that support only discovery, only communication, or both. This breadth reflects the phased rollout of ProSe capabilities, where an operator might first enable discovery-based services and later add direct communication, or support communication without network-assisted discovery.
Supporting ProSe Discovery means the network can assist UEs in discovering other ProSe-enabled UEs or services. This includes functions such as authorization of discovery, provisioning of discovery parameters, and — depending on the discovery model — direct assistance in matching or announcing discovery requests. Supporting ProSe Communication means the network can authorize and configure UEs to establish ProSe direct communication, including the radio parameters, security credentials, and policy needed for sidelink operation. The network does not necessarily carry the user-plane traffic of ProSe Communication; its role is typically control-plane enablement, authorization, and configuration, while the actual communication occurs directly between UEs over PC5.
The definition also carries an important interpretive convention: unless a specification explicitly states otherwise, any reference to 'the network' in the ProSe context refers to a ProSe-enabled Network. This convention avoids repetitive qualification throughout the specifications and establishes that ProSe procedures assume a network capable of supporting them. It matters for readers of the specifications because it means statements about network behavior in ProSe documents should be read as applying to networks that have implemented the relevant ProSe capabilities, not to all networks generically.
The concept is anchored in the ProSe requirements and architecture specifications. TS 22.278 defines ProSe service requirements, including the network's role in discovery and communication. TS 22.803 is the original ProSe feasibility study that established the architecture, use cases, and the division of responsibility between network and UE. TS 33.833 covers the security architecture for ProSe, defining how the network authorizes and secures ProSe operations. Together these specifications describe a network that acts as an enabler and policy point rather than as a data path for direct communication.
Operationally, a ProSe-enabled Network is what makes ProSe usable at scale. Without network authorization and provisioning, UEs would have no trusted basis for discovering each other or for establishing secured direct links. The network provides the identity, policy, and key management functions that underpin ProSe security, and it can control which UEs are permitted to use ProSe, under what conditions, and with what parameters. This control is essential for operators, who need to manage spectrum usage, roaming, and security policy for direct communication.
Purpose & Motivation
ProSe-enabled Network exists as a defined term to establish a clear boundary between networks that can support proximity services and those that cannot. ProSe is not a capability that every network implements; it requires specific authorization, provisioning, and security functions. By defining the term, 3GPP allows specifications to describe network behavior in ProSe procedures without repeatedly enumerating the required capabilities, and it gives operators and vendors a precise label for compliance.
The term also solves a documentation problem. ProSe specifications frequently refer to 'the network' when describing authorization, discovery assistance, and configuration. Without a convention that such references mean a ProSe-enabled Network, the specifications would be ambiguous — a reader could not tell whether a statement applied to any network or only to those supporting ProSe. The convention that unqualified 'network' means ProSe-enabled Network removes that ambiguity and makes the specifications readable.
Historically, the term was introduced in Release 12 alongside the rest of the ProSe framework, which was motivated by public safety requirements and by operator interest in proximity-based commercial services. The feasibility study in TS 22.803 established that ProSe would be an operator-controlled capability rather than an uncontrolled device-to-device free-for-all, and the ProSe-enabled Network concept is the expression of that principle: the network remains in control of authorization, policy, and security even when user traffic flows directly between devices.
What changed in its specifications
The latest release-to-release comparison of specifications that define ProSe-enabled Network. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 22.278: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 22.278 →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.
Wording revised: the definition was shortened to 'a network that supports ProSe Discovery and/or ProSe Communication,' dropping the sentence establishing the convention that unqualified 'network' refers to a ProSe-enabled Network. The core technical meaning — support for ProSe Discovery and/or Communication — is unchanged.
Defining Specifications
3GPP specifications that define or reference ProSe-enabled Network, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.278 vj00 | Evolved Packet System Service Requirements | Rel-19 read |
| TS 22.803 vc20 | Proximity Services Use Cases and Requirements | Rel-12 read |
| TS 33.833 vd00 | ProSe Security Study | Rel-13 read |