name: N32-f
full_form: User 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-f interface, also known as the User Plane Connection, refers to a specific communication path between two Security Edge Protection Proxies (SEPPs) in the context of the 5G system's security architecture. This interface is used for exchanging user plane data and is susceptible to errors that need to be detected and handled through appropriate procedures.
explanation: N32-f is classified as an Interface because it represents a communication link between SEPPs, facilitating the exchange of user plane messages. The context provided highlights its role in error detection and handling, emphasizing its importance in maintaining secure and reliable data transmission within the 5G system.
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,B-Protocol,I-Protocol,O,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,O,O,O,O,O,O,O,O,O,O