name: UP-PRUK
full_form: User Plane Prose Remote User Key
context: UE-to-Network Relay may include the PC5 security policies to the 5G ProSe UE-to-Network Relay. 1a. The 5G ProSe Remote UE sends a UP-PRUK Request message to its 5G PKMF. The message indicates that the 5G ProSe Remote UE is requesting a UP-PRUK from the 5G PKMF. If the 5G ProSe Remote UE already has a UP-PRUK from this 5G PKMF, the message shall also contain the UP-PRUK ID of the UP-PRUK. UP-PRUK ID shall take the form of either the NAI format or the 64-bit string. If the UP-PRUK ID is in NAI format, i.e. username@realm, the realm part shall include Home Network Identifier (i.e. HPLMN ID). The username part shall include the 64-bit string. 1b. The 5G PKMF checks whether the 5G ProSe Remote UE is authorized to receive UE-to-Network Relay services. This is done by using the 5G ProSe Remote UE's identity associated with the key used to establish the secure connection between the 5G ProSe Remote UE and 5G PKMF in step 0b. If the 5G ProSe Remote UE is authorized to receive the service, the
description: A UP-PRUK Request message is a signaling data exchanged between network components, specifically between the 5G ProSe Remote UE and its 5G PKMF, to request a User Plane Prose Remote User Key (UP-PRUK) for secure communication in 5G ProSe UE-to-Network relay scenarios.
explanation: The text describes a 'UP-PRUK Request message' as data exchanged between network components (5G ProSe Remote UE and 5G PKMF) for the purpose of requesting a security key. This aligns with the definition of a Message as a unit of communication carrying information between entities.
section_title: 6.3.3.2.2	PC5 security establishment for 5G ProSe UE-to-Network relay communication over User Plane
biotag_Context: B-Interface,O,O,O,O,O,O,O,O,O,B-Technology,B-Service,B-Interface,O,O,O,B-Technology,B-Service,O,B-Device,O,O,B-Message,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Technology,B-Service,O,B-Device,O,O,O,B-Message,O,O,B-Technology,O,O,O,B-Technology,B-Service,O,B-Device,O,O,O,B-Message,O,O,B-Technology,O,O,O,O,O,O,O,B-Message,B-Parameter,O,O,O,B-Message,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Message,B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network,I-Network,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Network Function,O,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Technology,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Service,O,B-Device,O,B-Technology,B-Network Function,O,O,O,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,O,O,O
biotag_Description: O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Service,O,B-Device,O,O,B-Technology,O,O,O,O,B-Message,I-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,O,B-Technology,B-Service,B-Interface,O,O