name: DCA
full_form: Direct Communication Accept
context: 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 triggered during the PC5 link establishment (e.g., NSSAA triggered after successful completion of DSMC procedure and before sending DCA to Remote UE). Upon successful NSSAA procedure, the relay sends a DCA message that includes a successful NSSAA indication and the authorized S-NSSAI. If the NSSAA fails, the relay may send a PC5 reject message indicating the failure cause. Upon successful NSSAA procedure, the relay may send a NAS message (e.g., PDU Session Modification, Establishment request, or Remote UE Report) to the SMF to provide connectivity to the Remote UE. The message may include the Remote UE User id and Remote UE addressing info (e.g., IP or MAC address) and other PDU Session parameters (e.g., S-NSSAI, DNN). The SMF receives the message from AMF which includes the Remote UE's
description: A Direct Communication Accept (DCA) message is a type of signaling data exchanged between network components, specifically used in the context of PC5 link establishment and NSSAA procedure. It indicates the acceptance of direct communication and may include additional information such as successful NSSAA indication and authorized S-NSSAI.
explanation: The DCA message is classified as a Message because it functions as a signaling mechanism to convey the acceptance of direct communication between network entities, as described in 3GPP TS 33.847.
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,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,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Network Function,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,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Device,O,O,O,B-Protocol,O,B-Protocol,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O
biotag_Description: O,B-Message,I-Message,I-Message,O,O,O,O,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,B-Network Function,O,O,O,O