name: N32-c
full_form: Control Plane Connection
context: Errors can occur on an active N32-c connection or on one or more N32-f connections between two SEPPs. When an error is detected, the SEPP shall map the error to an appropriate cause code. The SEPP shall create a signalling message to inform the peer SEPP, with cause code as one of its parameters. The SEPP shall use the N32-c connection to send the signalling message to the peer SEPP. If the old N32-c connection has been terminated, it uses a new N32-c connection instead. If the error occurred in the processing of the one or more N32-f message(s), the SEPP shall include the corresponding message ID (s), obtained from the metadata section of the N32-f message, as a parameter in the signalling message. This allows the peer SEPP to identify the source message(s) (HTTP Request or Response) on which the other SEPP found the error. NOTE: Local action taken by either SEPP is out of 3GPP scope.
description: The N32-c connection refers to a control plane interface between two Security Edge Protection Proxies (SEPPs) in the 5G system architecture. This interface is used for exchanging signalling messages, particularly for error detection and handling purposes. It enables the SEPPs to communicate with each other about errors that occur on active connections or during the processing of N32-f messages.
explanation: N32-c is classified as an Interface because it represents a communication pathway between two network functions (SEPPs) in the 5G system, specifically designed for control plane signalling. This interface plays a crucial role in ensuring the reliability and security of the SEPP-to-SEPP connection by facilitating error detection, reporting, and handling.
section_title: 13.2.2.3 Procedure for error detection and handling in SEPP
biotag_Context: O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,B-Interface,O,O,O,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,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Interface,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,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Organization,O
biotag_Description: O,B-Interface,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,O