name: CP-PRUK
full_form: Control Plane ProSe Remote User Key
context: 8. On successful authentication, the AUSF of the 5G ProSe Remote UE and the 5G ProSe Remote UE shall generate CP-PRUK as specified in clause A.2 and CP-PRUK ID. The CP-PRUK ID is in NAI format as specified in clause 2.2 of IETF RFC 7542 [14], i.e. username@realm. The username part includes the Routing Indicator from step 5 and the CP-PRUK ID*, and the realm part includes Home Network Identifier. The CP-PRUK ID* is specified in clause A.3. 9a. The AUSF of the 5G ProSe Remote UE shall select the PAnF (Prose Anchor Function) based on CP-PRUK ID and send the SUPI, RSC, CP-PRUK and CP-PRUK ID in Npanf_ProseKey_Register Request message to the PAnF. NOTE 1: The PAnF is selected based on the Routing Indicator in the CP-PRUK ID. 9b. The PAnF shall store the Prose context info (i.e. SUPI, RSC, CP-PRUK, CP-PRUK ID) for the 5G ProSe Remote UE and send Npanf_ProseKey_Register Response message to the AUSF. 10a. The AUSF of the 5G ProSe Remote UE shall select the PAnF based on CP-PRUK ID and send
description: Control Plane ProSe Remote User Key (CP-PRUK) is a parameter used in the security establishment process for 5G ProSe UE-to-Network relay communication over Control Plane. It is generated by the AUSF and the 5G ProSe Remote UE upon successful authentication, and is used to identify the user and establish a secure connection.
explanation: The context describes CP-PRUK as a key generated during the security establishment process, which is used for identification and secure connection purposes. This indicates that CP-PRUK is a critical network attribute, making it a Parameter.
section_title: 6.3.3.3.2	PC5 security establishment for 5G ProSe UE-to-Network relay communication over Control Plane
biotag_Context: O,O,O,O,O,B-Network Function,O,O,B-Technology,B-Service,O,B-Device,O,O,B-Technology,B-Service,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network,I-Network,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,O,O,O,O,O,B-Parameter,B-Parameter,O,O,O,O,O,B-Parameter,O,B-Parameter,B-Parameter,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,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,O,O,B-Parameter,B-Parameter,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Service,B-Interface,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Technology,B-Service,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O