1. Cloud Native Security Edge Protection Proxy (SEPP) User's Guide
  2. SEPP Response Codes

4 SEPP Response Codes

Following are the SEPP Response Codes:

  • N32c Handshake Response Codes
  • N32f Plane Message Forwarding Response Codes

N32c Handshake Response Codes

Request Response Code ResponseBody Reference Use Case Comment/Remarks Applicable Scope(PI-E)
Capability Exchange 200 OK SecNegotiateRspBody TS29573_N32_Handshake.yaml Handshake success Handshake Success   Yes
400 Bad Request Problem Details TS29573_N32_Handshake.yaml
  1. Invalid RequestBody
  2. Mandatory IE Missing
 Handshake fail   Yes
404 Not Found Problem Details 3gpp Spec 29500
  1. Incorrect API
     Yes
405 Method Not Allowed Problem Details 3gpp Spec 29500 When request method other than POST is used     Yes
411 Length Required Problem Details TS29573_N32_Handshake.yaml When Content Length header is not present in request.     No
413 Payload Too Large Problem Details TS29573_N32_Handshake.yaml When request entity is larger than limits defined by server.     No
415 Unsupported Media Type Problem Details TS29573_N32_Handshake.yaml When payload format is not in json. When "Content-Type:application/json" is not present.     Yes
429 Too Many Requests Problem Details TS29573_N32_Handshake.yaml Too many requests in a given amount of time ("rate limiting").     No
500 Internal Server Error Problem Details TS29573_N32_Handshake.yaml
  1. DB Access Fail during execution of handshake request in server side.
  2. Any other internal error in server during execution of handshake request.
     Yes
503 Service Unavailable null TS29573_N32_Handshake.yaml When sepp backend service is down.     Yes
501 Not Implemented Problem Details   When capability mismatch happens.     Yes
401 Unauthorized Problem Details   When request received for unknown peer sepp.     Yes
403 Forbidden Problem Details   When request received for disabled peer sepp.     Yes

N32f Plane Message Forwarding Response Codes

Pod Name Response Code ResponseBody Use Case Reference Comment Applicable Scope
cN32f-Sepp 200 OK Success Body Success TS29573_JOSEProtectedMessageForwarding.yaml     PI-E
404 Not Found Problem Details N32f Context Not Found 3gpp Spec 29500     PI-E
401 Unauthorised Problem Details Context Not Established 3gpp Spec 29500     PI-E
401 Unauthorised Problem Details Security Capability apart from TLS 3gpp Spec 29500     PI-E
400 Bad Request Problem Details 3GPP-target-sbi-apiroot/destination producer NF is absent TS29573_JOSEProtectedMessageForwarding.yaml     PI-E
503 Service Unavailable Problem Details Service Unavailable TS29573_JOSEProtectedMessageForwarding.yaml     PI-E
pN32f-Sepp 400 Bad Request Problem Details 3GPP-target-sbi-apiroot/destination producer NF is absent TS29573_JOSEProtectedMessageForwarding.yaml     PI-E
503 Service Unavailable Problem Details Service Unavailable TS29573_JOSEProtectedMessageForwarding.yaml     PI-E

Note:

All the Exceptions/Error response codes sent by the N32-EGW at consumer side and PLMN-EGW at Producer side will be same and we will be adding a Problem statement which contains the reason why it occured.