name: NSSAA
full_form: Network Slice Specific Authentication and Authorization
context: message to confirm the PC5 link security establishment to the AMF. AMF may trigger the NSSAA procedure upon receiving this message illustrated in Figure 6.24.2.2-1. 11. The relay sends a DCA message including indication for NSSAA status (e.g., pending, required, successful) and S-NSSAI to Remote UE. In case of failure indication in message 8, the relay sends a reject message to the Remote UE including the failure cause. 12. If NSSAA is required, an NSSAA procedure for Remote UE via Relay may be triggered by Relay as illustrated in Figure 6.24.2.2-1. 13. Upon successful completion of the NSSAA procedure, the relay sends a PC5 message (e.g., a PC5 Link Modification Request) that includes a successful NSSAA indication, the authorized S-NSSAI. If the NSSAA procedure fails, the relay may release the PC5 link indicating the failure cause. In the above procedure, the NSSAA procedure is triggered after the relay sends the DCA message to the Remote UE. Alternatively, the NSSAA procedure may be
description: Network Slice Specific Authentication and Authorization (NSSAA) is a procedure that involves authentication and authorization of network slices for user equipment (UE) in the 5G core network. It ensures secure access to specific network resources based on the UE's identity and permissions.
explanation: The context describes NSSAA as a triggered procedure upon receiving a message, involving steps such as sending DCA messages with NSSAA status indications, triggering NSSAA procedures for Remote UEs via Relay, and handling successful or failed completions of the NSSAA procedure. This sequential operation aligns with the definition of a Procedure in the 3GPP specification context.
section_title: 6.24.2.1	PC5 link establishment with L3 UE-to-Network relay to use an S-NSSAI subject to NSSAA
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,B-Network Function,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-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Network Function,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O