Question: What happens when an error occurs in the processing of one or more N32-f messages between two SEPPs?
Option 1: The SEPP ignores the error and continues with the current connection.
Option 2: The SEPP sends a signalling message to the peer SEPP using a new N32-c connection, but does not include any information about the source message(s).
Option 3: The SEPP terminates all existing connections and establishes a new connection before sending an error report.
Option 4: The SEPP creates a signalling message with cause code and includes the corresponding message ID(s) from the metadata section of the N32-f message, to inform the peer SEPP about the source message(s).
Explanation: When an error occurs in the processing of one or more N32-f messages between two SEPPs, the SEPP creates a signalling message with cause code and includes the corresponding message ID(s) from the metadata section of the N32-f message. This allows the peer SEPP to identify the source message(s), such as HTTP Request or Response, on which the other SEPP found the error.