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

Glossary term · Security

DUSK

Discovery User Scrambling Key

Security →

DUSK is a cryptographic key used to scramble and secure discovery messages in Proximity Services, ensuring only authorized devices can decode the information to protect privacy and prevent unauthorized tracking.

Introduced
Rel-13
Where
Services
Specifications
8 specs
Also in
Security
DUSK Description Purpose What changed Neighbours Specifications

Description

The Discovery User Scrambling Key (DUSK) is a fundamental security component within the 3GPP Proximity Services (ProSe) architecture, specifically for the Direct Discovery function. It is a symmetric cryptographic key derived from a root key, the ProSe Key (PK), which is itself provisioned by the ProSe Function in the network. The primary role of DUSK is to provide confidentiality and integrity for the ProSe Application Code, which is the identifier broadcast by a device to announce its presence and services to other nearby devices. The scrambling process involves applying the DUSK to the ProSe Application Code using a cryptographic algorithm before it is transmitted over the PC5 reference point (the direct device-to-device interface). This transforms the code into a scrambled, unintelligible string for any eavesdropper.

Upon receiving a scrambled discovery message, an authorized discovering device, which must also have the corresponding DUSK (obtained through network provisioning for restricted discovery or derived for open discovery), applies the descrambling process. This process reverses the scrambling to recover the original ProSe Application Code. The possession of the correct DUSK serves as proof of authorization to discover that specific service. The key management for DUSK is handled by the ProSe Function, which securely delivers the key or the necessary key derivation material to the UE over the LTE-Uu or NR-Uu interface, ensuring it never traverses the insecure PC5 air interface directly.

Architecturally, DUSK operates within the ProSe protocol stack, interfacing with the ProSe application layer and the security sublayer. Its generation and lifecycle are tied to the ProSe subscription and the specific ProSe Application ID. The use of DUSK is crucial for different discovery models: in Open Discovery, a common DUSK may be used, while in Restricted Discovery, unique or group-specific DUSKs ensure that discovery is limited to a pre-authorized set of devices. This mechanism effectively separates the broadcast identifier from the user's permanent identity, adding a vital layer of privacy.

Purpose & Motivation

DUSK was introduced to address critical security and privacy challenges inherent in device-to-device discovery, a cornerstone of Proximity Services (ProSe) standardized from 3GPP Release 12 onwards. Without such a mechanism, devices broadcasting discovery codes in the clear would be vulnerable to privacy invasion, as malicious actors could track a user's location and associations over time by monitoring these persistent identifiers. Furthermore, spoofing attacks would be trivial, allowing any device to impersonate a legitimate service.

The creation of DUSK was motivated by the need to enable trusted discovery in commercial and public safety scenarios. Previous ad-hoc discovery methods, like Bluetooth device names, offered no standardized security. DUSK provides a standardized, network-assisted security framework that allows for both open and restricted discovery models. It solves the problem of how to publicly announce a service while controlling who can understand the announcement, thereby enabling new use cases like social networking, local advertising, and public safety team communication without compromising user privacy or network security.

What changed in its specifications

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

TS 24.334Rel-18 → Rel-19

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

Full comparison in TS 24.334 →
TS 24.554Rel-18 → Rel-19

Rel-19 adds multi-hop NR sidelink UE-to-network relay with new direct link establishment procedures and discovery IEs. It extends 5G ProSe to SNPNs, adding SNPN identification, authorisation checks, and PC5 relay indications. It also adds multi-hop relay configuration over PC5 and charging-related abbreviations and content type values.

Full comparison in TS 24.554 →

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

Introduced as part of the enhanced ProSe framework. Defined the derivation of DUSK from the ProSe Key (PK) and its application for scrambling ProSe Application Codes and ProSe Application Identities. Established the security procedures for both Model A (Announcement) and Model B (Solicitation/Response) discovery, integrating DUSK with the ProSe protocol architecture specified in TS 24.334 and security specs like TS 33.303.

Defining Specifications

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

SpecificationTitleRelease
TS 24.334 vj00 ProSe Protocols and Procedures Rel-19 read
TS 24.514 vj30 Ranging & Sidelink Positioning in 5GS Rel-19 read
TS 24.554 vk10 5G ProSe Protocols and Procedures Rel-20 read
TS 24.555 vk10 5G ProSe UE Policy Specification Rel-20 read
TS 29.345 vj00 Diameter-based PC6/PC7 interfaces for ProSe Rel-19 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 33.503 vk00 5G ProSe Security Specification Rel-20 read
TS 33.843 vf10 Security Study for ProSe UE-to-Network Relay Rel-15 read