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

Glossary term · Services

Discovery Filter

ProSe Direct Discovery Filter

Services →

Discovery Filter is a container holding a ProSe Application Code or ProSe Restricted Code, optional ProSe Application Masks, and a Time To Live value, used by monitoring UEs to match ProSe Direct Discovery messages received over the PC5 interface.

Introduced
Rel-12
Where
Services
Specifications
2 specs
Discovery Filter Description Purpose What changed Neighbours Specifications

Description

The Discovery Filter is a fundamental data structure in the Proximity Services (ProSe) architecture defined by 3GPP. It is provisioned by the ProSe Function into the UE and serves as the matching criterion that a monitoring UE applies to discovery announcements received over the PC5 sidelink interface. Structurally, a Discovery Filter contains a ProSe Application Code (for open discovery) or a ProSe Restricted Code (for restricted discovery), zero or more ProSe Application Masks, and a Time To Live (TTL) value that bounds the validity of the filter. The mask mechanism allows partial matching, so a single filter can match a family of codes rather than one exact code, which is useful for group-based discovery scenarios.

In operation, the announcing UE transmits discovery messages containing ProSe Application Codes on the PC5 interface. The monitoring UE, which has been provisioned with one or more Discovery Filters, compares received codes against its filters. If a match is found (taking into account any masks), the monitoring UE reports the match to the ProSe Function or directly to the requesting application, depending on the discovery model (Model A or Model B). The TTL ensures stale filters are not used indefinitely; once expired, the UE must re-request filters from the ProSe Function.

The filter is delivered to the UE during the discovery authorization and provisioning procedure, typically via the PC3 reference point between the UE and the ProSe Function. The ProSe Function derives filters from the ProSe Application IDs and application-level discovery requests, applying policy from the ProSe Application Server. This separation of concerns means the UE never needs to understand application semantics — it only performs code matching.

Security is an important dimension: TS 33.303 specifies how discovery filters and the associated codes are protected, ensuring that only authorized UEs can monitor for particular application codes and that privacy of the announcing user is preserved. The ProSe Restricted Code variant, added in Rel-13, extends the concept to restricted discovery where monitoring requires explicit authorization from the announcing party.

The Discovery Filter remains a stable concept across Releases 12 through 19, with the definition text unchanged since Rel-13. Its longevity reflects the maturity of the ProSe discovery framework and its continued relevance in public safety, commercial proximity services, and sidelink-based applications.

Purpose & Motivation

The Discovery Filter exists to make ProSe Direct Discovery scalable and privacy-preserving. Without a filter mechanism, every monitoring UE would need to receive and process every discovery announcement on the PC5 interface, which is inefficient and exposes users to unwanted tracking. By provisioning targeted filters, the network ensures UEs only react to codes relevant to their applications and authorized relationships.

The mask capability addresses group discovery: a single filter can match a range of codes, reducing provisioning overhead when many devices share a common application context. The TTL value solves the problem of stale authorization — filters expire automatically, forcing re-authorization and preventing indefinite monitoring with outdated credentials.

The Rel-13 addition of ProSe Restricted Code support extended the filter concept from open discovery to restricted discovery, where the announcing UE controls who may monitor. This addressed privacy limitations of open discovery in commercial deployments, where users wanted finer control over discoverability.

What changed in its specifications

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

TS 23.303Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.303: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.303 →
TS 33.303Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 33.303: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 33.303 →

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-12 Initial

Initial definition introduced the Discovery Filter as a container of a ProSe Application code, zero or more ProSe Application Masks, and a Time To Live value, used by monitoring UEs to match ProSe Application Codes received on PC5 for Direct Discovery.

Definition extended to include ProSe Restricted code alongside ProSe Application code, reflecting the introduction of restricted discovery in Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Defining Specifications

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

SpecificationTitleRelease
TS 23.303 vj00 Proximity Services (ProSe) Stage 2 Rel-19 read
TS 33.303 vj00 ProSe Security Specification for EPS Rel-19 read