name: DUSK
full_form: Discovery User Scrambling Key
context: The Remote UE does the following: 1. If DUCK available, set DUCK as key K. If DUCK is not available, then choose DUSK as K. If neither DUCK nor DUSK are available, the DCR message is not protected, and Steps 2-4 can be skipped. 2. Form Message = RSC || PRUK ID 3. Calculate Keystream = KDF (K, UTC-based counter, RSC) â see subclause 6.42.2.3. 4. Ciphertext = Message XOR Keystream The UE-to-network relay does the following to retrieve the protected fields of the received DCR message, e.g., RSC and PRUK ID: 1. If DUCK available, set DUCK as key K. If DUCK is not available, then choose DUSK as K. If neither DUCK nor DUSK are available, the DCR message is not protected and Steps 2-5 can be skipped. 2. Form Ciphertext = a part of protected (RSC || PRUK ID) in the received DCR message. 3. Calculate Keystream = KDF (K, UTC-based counter, RSC) â see subclause 6.42.2.3. 4. Obtain (RSC_Received || PRUK ID_Received) = MessageReceived = Ciphertext XOR Keystream 5. If RSC_Received equals RSC in Step
description: The Discovery User Scrambling Key (DUSK) is a key used for protecting the PRUK ID and RSC over the PC5 interface in the context of Remote UE to network relay communication. It serves as an alternative to DUCK when available, ensuring secure transmission of sensitive information.
explanation: The provided context from 3GPP TS 33.847 highlights the role of DUSK as a key for encryption and decryption processes between the Remote UE and the network relay. This usage aligns with the definition of a Parameter in telecommunications, which includes critical network attributes such as identifiers, timers, and keys.
section_title: 6.42.2.2	Protection of PRUK ID and RSC over the PC5 interface
biotag_Context: O,O,B-Device,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Parameter,B-Parameter,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Parameter,O,B-Parameter,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Message,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,B-Parameter,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O