Information elements value tables
The MAG-c PCMD supports IEs for procedure IDs, results, success and failure causes, message marker IDs, SBI service IDs and operation messages, and reference points.
ProcedureIDs
The MAG-c PCMD supports procedure IDs with related causes and responses, for supported MAG-c gateway types.
The following table describes the procedure ID, name, start and end actions, and supported gateway types.
| ProcedureId | Name | Start of procedure | End of procedure (success) | End of procedure (failure) | Supported gateway type |
|---|---|---|---|---|---|
| 1 | MME-initiated Create Default Bearer | > Combined SGW-C + PGW‑C receives Create Session Request from MME |
> Procedure completes successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF, UDM, CHF) |
> A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 9 | MME-initiated Modify Bearer | > Combined SGW-C + PGW‑C receives Modify Bearer Request from MME | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, and so on) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 16 | MME-initiated Modify Default Bearer | > Combined SGW-C + PGW‑C receives Modify Bearer command from MME | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 20 | MME-initiated Delete Session | > Combined SGW-C + PGW‑C receives Delete Session Request from MME | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF, CHF, UDM) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 26 | SGW-initiated Downlink Data Notification to MME | > Combined SGW-C + PGW‑C sends Downlink Data Notification to MME | > MME responds with successful cause | > A failure is encountered in MME | Combined SGW‑C + PGW‑C |
| 32 | MME-initiated release of S1U | > Combined SGW-C + PGW‑C receives Release Access Bearer Request from MME | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW-U) | >A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 80 | Delete UE Administrative | > Combined SGW-C + PGW‑C deletes all
sessions for specific UE and may inform its peers if
applicable Triggered by delete from CLI, reattach or collision |
> Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF, UDM, CHF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 81 | Delete Session Administrative |
> Combined SGW-C + PGW‑C deletes session with one or several bearers but the UE persists if it has more sessions on the gateway. May inform peers if applicable. Triggered mainly by collision, unsuccessful call-flow or per-bearer delete from CLI |
> Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW-U, PCF, UDM, CHF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 85 | Sx Session Report | > Combined SGW-C + PGW‑C receives a PFCP Session Report Req from UPF | > Combined SGW‑C + PGW‑C acknowledges the PFCP Session Report Resp with a success cause and initiates the PFCP Session Modification to update or clean up the bearer | > A failure is encountered in Combined SGW-C + PGW-C | Combined SGW‑C + PGW‑C |
| 86 | PCF Initiated Modify Default Bearer | > Combined SGW-C + PGW‑C receives Npcf_SMPolicyControl_update | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 87 | PCF Initiated Delete Default Bearer | > Combined SGW-C + PGW-C receives Npcf_SMPolicyControl_update terminate | > Procedure is completed successfully in all involved peers (MME, combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF, UDM, CHF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 88 | Delete Session because of MME Path failure | > Combined SGW-C + PGW‑C detects MME Path failure | > Procedure is completed successfully, all involved peers (combined SGW‑C + PGW‑C, combined SGW‑U + PGW‑U, PCF, UDM, CHF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
| 89 | Delete Session because of UPF Path failure | > Combined SGW-C + PGW‑C detects UPF Path failure | > Procedure is completed successfully in all involved peers (combined SGW‑C + PGW‑C, PCF, UDM, CHF) | > A failure is encountered in any of the involved peers | Combined SGW‑C + PGW‑C |
The following table describes the 5G PCMD procedure IDs, names, start, and ending of a procedure.
| ProcedureId | Name | Start of procedure | End of procedure (success) | End of procedure (failure) |
|---|---|---|---|---|
| 101 | PDU Session Create | > SMF receives Nsmf_PDUSession_CreateSMContext service request from AMF | Procedure is completed successfully, in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 102 | UE-initiated PDU Session Release | > SMF receives Nsmf_PDUSession_UpdateSMContext service request from AMF, containing the N1 container for PDU Session Release Request | Session and subscriptions are deleted successfully in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 103 | AMF-initiated PDU Session Release without N1N2 signaling to the RAN | > SMF receives Nsmf_PDUSession_ReleaseSMContext Post request from AMF | Session and subscriptions are deleted successfully in all involved peers (AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 104 | AMF-initiated PDU Session Release with RAN signaling |
> SMF receives Nsmf_PDUSession_UpdateSMContext Post request from AMF. The release IE is included indicating that AMF wants to release the session. |
Session and subscriptions are deleted successfully in all involved peers (RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 105 | PCF-initiated PDU Session Release |
> SMF receives Npcf_SMPolicyControl_UpdateNotify Post request from PCF. The payload identifies the released session. |
Session and subscriptions are deleted successfully in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 106 | SMF-initiated PDU Session Release | > SMF initiates PDU session release | Session and subscriptions are deleted successfully in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 107 | UDM-initiated PDU Session Release | > SMF receives Nudm_SDM_Notification Request from UDM, indicating the subscription data of the session has been removed | Session and subscriptions are deleted successfully in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, UDM, CHF) | A failure is encountered in any of the involved peers |
| 109 | UE-triggered Service Request without AMF Change |
> SMF Receives Nsmf_PDUSession_UpdateSMContext Post request from AMF. The the value of upConnectionState is set to 'ACTIVATING' to indicate that request is about activating the UP. |
Procedure is completed successfully, in all involved peers (UE, RAN, AMF, SMF, UPF, PCF) | A failure is encountered in any of the involved peers |
| 110 | UE-triggered Service Request with AMF Change |
> SMF receives Nsmf_PDUSession_UpdateSMContext Post request from AMF. Value of upConnectionState is set to 'ACTIVATING' to indicate that request is about activating the user plane. New AMF-ID is received. |
Procedure is completed successfully, in all involved peers (UE, RAN, New AMF, SMF, UPF, PCF) | A failure is encountered in any of the involved peers |
| 111 | 5GC Network-initiated Service Request |
> SMF receives Data Notification from UPF. The session report message may contain also a Usage Report. |
Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF, PCF, CHF) | A failure is encountered in any of the involved peers |
| 112 | NR RAN Release |
> SMF receives Nsmf_PDUSession_UpdateSMContext Post request from AMF. The value of upConnectionState is set to 'DEACTIVATED' |
Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF) | A failure is encountered in any of the involved peers |
| 114 | SMF-initiated PDU Session Modification | > SMF initiates PDU session modification | Procedure is completed successfully, in all involved peers (UE, RAN, AMF, SMF, UPF, PCF, CHF) | A failure is encountered in any of the involved peers |
| 115 | PCF-initiated Session Modification | > SMF receives Npcf_SMPolicyControl Update Notify from PCF | Procedure is completed successfully, in all involved peers (UE, RAN, AMF, SMF, UPF, UDM, PCF, CHF) | A failure is encountered in any of the involved peers |
| 116 | UDM-initiated PDU Session Modification | > SMF receives Nudm_SDM Notification from UDM | Procedure is completed successfully, in all involved peers (UE, RAN, AMF, SMF, UPF, UDM, PCF, CHF) | A failure is encountered in any of the involved peers |
| 119 | Xn based handover | > SMF receives Nsmf_PDUSession_UpdateSMContext Request from AMF for the PDU session, with Path Switch Request Transfer in the N2 container | Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF, PCF) | A failure is encountered in any of the involved peers |
| 123 | N2-based handover with indirect forwarding with AMF change |
> SMF receives Nsmf_PDUSession_UpdateSMContext request from a new AMF. AMF ID of the new AMF is included in the message. The hoState is set to PREPARING. N2 container contains Handover Required Transfer IE, without Direct Forwarding Path Availability IE. |
Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF, PCF) | A failure is encountered in any of the involved peers |
| 124 | AMF Change in IDLE state | > SMF receives an Nsmf_PDUSession_Update SM Context request from the AMF with a new AMF ID | Procedure is completed successfully, in all involved peers (new AMF, SMF, PCF) | A failure is encountered in any of the involved peers |
| 127 | SMF received Error Indication Report | > SMF receives Error indication report from UPF | Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF) | A failure is encountered in any of the involved peers |
| 128 | SMF received User Plane Inactivity Report |
> SMF receives User plane Inactivity report from UPF. Session report message may contain also a Usage Report. |
Procedure is completed successfully, in all involved peers (RAN, AMF, SMF, UPF, CHF, PCF) | A failure is encountered in any of the involved peers |
| 129 | SMF received Data Usage Report (as only report in the session report message) | > SMF receives Usage Data Report from UPF as the only report type in the session report message | Procedure is completed successfully in all involved peers (SMF, UPF, CHF, PCF) | A failure is encountered in any of the involved peers |
UE-level procedures
Procedures that are related to a specific session of a UE include the session- and bearer-level characteristics, such as APN, UE IP, PDN type, and so on. There are also UE-level procedures that are relevant to all the sessions of a UE. In the UE-level procedures, some IEs are not reported, such as APNs, UE IP, and so on.
The following procedures are UE-level procedures that are relevant to all the sessions of
a UE:
- MME-initiated release of S1U
- Downlink data notification to the MME
- Delete UE administrative
Results
The MAG-c supports success and failure results IEs for PCMD.
| Result | Name |
|---|---|
| 1 | Normal |
| 2 | Failure |
Causes
The MAG-c supports success and failure causes IEs for PCMD.
Success causes
The following table lists the success causes.
| Cause | Name | Description | Protocol | Protocol value |
|---|---|---|---|---|
| 112 | GTP_CAUSE_SUCCESS | Request accepted | GTPv2 | 16 |
| 113 | GTP_CAUSE_PARTIAL_SUCCESS | Request accepted partially | GTPv2 | 17 |
| 114 | GTP_CAUSE_NEW_PDN_NWPREFS | New PDN type because of network preference | GTPv2 | 18 |
| 115 | GTP_CAUSE_NEW_PDN_SINGLE_ADDRESS_BEARER | New PDN type because of single address bearer only | GTPv2 | 19 |
| 150 | SBI_200_OK | HTTP/2 | 200 | |
| 151 | SBI_201_CREATED | HTTP/2 | 201 | |
| 152 | SBI_202_ACCEPTED | HTTP/2 | 202 | |
| 154 | SBI_204_NO_CONTENT | HTTP/2 | 204 | |
| 430 | PFCP_REQ_ACCEPTED | Request accepted (success) | PFCP | 1 |
Failure causes
The following table lists the failure causes.
| Cause | Name | Description | Protocol | Protocol value |
|---|---|---|---|---|
| 238 | GTP_CAUSE_RESERVED | Reserved | GTPv2 | 0 |
| 239 | GTP_CAUSE_PAGING | Paging | GTPv2 | 1 |
| 240 | GTP_CAUSE_LOCAL_DETACH | Local Detach | GTPv2 | 2 |
| 241 | GTP_CAUSE_COMPLETE_DETACH | Complete Detach | GTPv2 | 3 |
| 242 | GTP_CAUSE_RAT_3GPP2NON3GPP | RAT changed from 3GPP to non-3GPP | GTPv2 | 4 |
| 243 | GTP_CAUSE_ISR_DEACTIVATION | ISR deactivation | GTPv2 | 5 |
| 244 | GTP_CAUSE_ERR_IND_FROM_RNCENB | Error Indication received from RNC/eNodeB/S4-SGSN | GTPv2 | 6 |
| 245 | GTP_CAUSE_IMSI_DETACH | IMSI Detach Only | GTPv2 | 7 |
| 246 | GTP_CAUSE_REACTIVATION_REQUESTED | Reactivation Requested | GTPv2 | 8 |
| 247 | GTP_CAUSE_PDN_RECONN_DISALLOWED | PDN reconnection to this APN disallowed | GTPv2 | 9 |
| 248 | GTP_CAUSE_ACCESS_NON3GPP23GPP | Access changed from non-3GPP to 3GPP | GTPv2 | 10 |
| 249 | GTP_CAUSE_PDN_INACTIVE_TIMEOUT | PDN connection inactivity timer expires | GTPv2 | 11 |
| 250 | GTP_CAUSE_CONTEXT_NOT_FOUND | Context Not Found | GTPv2 | 64 |
| 251 | GTP_CAUSE_INVALID_MSG_FMT | Invalid Message Format | GTPv2 | 65 |
| 252 | GTP_CAUSE_VERSION_NOT_SUPPORTED | Version not supported by next peer | GTPv2 | 66 |
| 253 | GTP_CAUSE_INVALID_LENGTH | Invalid length | GTPv2 | 67 |
| 254 | GTP_CAUSE_SERVICE_NOT_SUPPORTED | Service not supported | GTPv2 | 68 |
| 255 | GTP_CAUSE_MANDAT_IE_INCORRECT | Mandatory IE incorrect | GTPv2 | 69 |
| 256 | GTP_CAUSE_MANDAT_IE_MISSING | Mandatory IE missing | GTPv2 | 70 |
| 257 | GTP_CAUSE_OPT_IE_INCORRECT | Optional IE incorrect | GTPv2 | 71 |
| 258 | GTP_CAUSE_SYSTEM_FAILURE | System failure | GTPv2 | 72 |
| 259 | GTP_CAUSE_NO_RESOURCES | No resources available | GTPv2 | 73 |
| 260 | GTP_CAUSE_SEMANTIC_ERR_TFT | Semantic error in the TFT operation | GTPv2 | 74 |
| 261 | GTP_CAUSE_SYNTAX_ERR_TFT | Syntactic error in the TFT operation | GTPv2 | 75 |
| 262 | GTP_CAUSE_SEMANTIC_ERR_PKTFILTER | Semantic errors in packet filters | GTPv2 | 76 |
| 263 | GTP_CAUSE_SYNTAX_ERR_PKTFILTER | Syntactic errors in packet filters | GTPv2 | 77 |
| 264 | GTP_CAUSE_MISSING_APN | Missing or unknown APN | GTPv2 | 78 |
| 266 | GTP_CAUSE_GREKEY_NOT_FOUND | GRE key not found | GTPv2 | 80 |
| 267 | GTP_CAUSE_RELOCATION_FAILURE | Relocation failure | GTPv2 | 81 |
| 268 | GTP_CAUSE_DENIED_RAT | Denied in RAT | GTPv2 | 82 |
| 269 | GTP_CAUSE_PREF_PDNTYPE_NOT_SUPPORT | Preferred PDN type not supported | GTPv2 | 83 |
| 270 | GTP_CAUSE_ALL_DYNAMIC_ADDR_OCCUPIED | All dynamic addresses are occupied | GTPv2 | 84 |
| 271 | GTP_CAUSE_UE_CXT_ACTIVATED_WITHOUT_TFT | UE context without TFT already activated | GTPv2 | 85 |
| 272 | GTP_CAUSE_PROTO_NOT_SUPPORTED | Protocol type not supported | GTPv2 | 86 |
| 273 | GTP_CAUSE_UE_NOT_RESPONDING | UE not responding | GTPv2 | 87 |
| 274 | GTP_CAUSE_UE_REFUSES | UE refuses | GTPv2 | 88 |
| 275 | GTP_CAUSE_SERVICE_DENIED | Service denied | GTPv2 | 89 |
| 276 | GTP_CAUSE_UNABLE_TO_PAGE_UE | Unable to page UE | GTPv2 | 90 |
| 277 | GTP_CAUSE_NO_MEM | No memory available | GTPv2 | 91 |
| 278 | GTP_CAUSE_USER_AUTH_FAILED | User authentication failed | GTPv2 | 92 |
| 279 | GTP_CAUSE_APN_ACCESS_DENIED | APN access denied - no subscription | GTPv2 | 93 |
| 280 | GTP_CAUSE_REQUEST_REJECTED | Request rejected (reason not specified) | GTPv2 | 94 |
| 281 | GTP_CAUSE_PTMSI_MISMATCH | P-TMSI Signature mismatch | GTPv2 | 95 |
| 282 | GTP_CAUSE_IMSI_NOT_KNOWN | IMSI/IMEI not known | GTPv2 | 96 |
| 283 | GTP_CAUSE_SEMANTIC_ERR_TAD | Semantic error in the TAD operation | GTPv2 | 97 |
| 284 | GTP_CAUSE_SYNTACTIC_ERR_TAD | Syntactic error in the TAD operation | GTPv2 | 98 |
| 285 | GTP_CAUSE_RESERVED_MSG_VAL | Used to indicate specific IE value validation failure cases. | GTPv2 | 99 |
| 286 | GTP_CAUSE_REM_PEER_NO_RESPONSE | Remote peer not responding, used for all types of peers without differentiation | GTPv2 | 100 |
| 289 | GTP_CAUSE_COLLISION_WITH_NW_REQS | Collision with network-initiated request | GTPv2 | 101 |
| 290 | GTP_CAUSE_UNABLE_TO_PAGE_DUE_TO_SUSPENSION | Unable to page UE because of Suspension | GTPv2 | 102 |
| 291 | GTP_CAUSE_CONDITIONAL_IE_MISSING | Conditional IE missing | GTPv2 | 103 |
| 292 | GTP_CAUSE_APN_RESTRICTION_INCOMPATIBLE | APN Restriction type Incompatible with currently active PDN connection | 104 | |
| 293 | GTP_CAUSE_INVALID_OVERALL_LEN_TRIG_PIGGY | Invalid overall length of the triggered response message and a piggybacked initial message | GTPv2 | 105 |
| 294 | GTP_CAUSE_DATA_FOWARDING_NOT_SUPPORTED | Data forwarding not supported | GTPv2 | 106 |
| 295 | GTP_CAUSE_INVALID_REPLY_REMOTE_PEER | Invalid reply from remote peer | GTPv2 | 107 |
| 296 | GTP_CAUSE_FALLBACK_TO_GTPV1 | Fallback to GTPv1 | GTPv2 | 108 |
| 297 | GTP_CAUSE_INVALID_PEER | Invalid peer | GTPv2 | 109 |
| 298 | GTP_CAUSE_HANDOVER_IN_PROGRESS | Temporarily rejected because of a handover procedure in progress | GTPv2 | 110 |
| 299 | GTP_CAUSE_MOD_BEYONG_S1U_BEARERS | Modifications not limited to S1-U bearers | GTPv2 | 111 |
| 300 | GTP_CAUSE_UE_REATTACHED | UE already re-attached | GTPv2 | 115 |
| 301 | GTP_CAUSE_MPDN_PER_APN_NOT_ALLOWED | Multiple PDN connections for a specific APN not allowed | GTPv2 | 116 |
| 302 | GTP_CAUSE_SGW_RECOVERY_IDLE | SGW/combined SGW/PGW indicates to the MME that Geo-redundancy fail-over just occurred. This is a proprietary definition. | GTPv2 | 254 |
| 303 | GTP_CAUSE_PGW_NOT_RESPONDING | For PGW Restart Notification (PRN) message to indicate the PGW down case. | GTPv2 | 12 |
| 409 | GTP_CAUSE_MME_REFUSE_VPLMN_PCY | The MME or the SGSN refuses because of VPLMN Policy | GTPv2 | 119 |
| 410 | GTP_CAUSE_UE_UNREACH_PWR_SAV | The UE is temporarily not reachable because of power saving | GTPv2 | 123 |
| 411 | GTP_CAUSE_UE_NO_AUTH_BY_OCS_AAA | The UE is not authorized by the Online Charging Server or the external AAA server | GTPv2 | 125 |
| 412 | GTP_CAUSE_REQ_REJECT_UE_CAPABILITY | The request was rejected because of UE Capability | GTPv2 | 127 |
| 422 | GTP_CAUSE_LATE_OVERLAP_REQ | Late Overlapping Request; see DIAMETER cause 420 | GTPv2 | 121 |
| 423 | GTP_CAUSE_TIMED_OUT_REQ | Timed Out Request; see DIAMETER cause 421 | GTPv2 | 122 |
| 424 | E_PCMD_CAUSE_GTP1_NETWORK_FAILURE | Sent by SGSN in the Delete PDP Context Request to indicate a network problem | GTPv1 | 8 |
| 431 | PFCP_CAUSE_REQ_REJECTED | Request Rejected (no specified reason) | PFCP | 64 |
| 432 | PFCP_CAUSE_CONTEXT_NOT_FOUND | Session Context not found | PFCP | 65 |
| 433 | PFCP_CAUSE_MANDATORY_IE_MISSING | Mandatory IE Missing | PFCP | 66 |
| 434 | PFCP_CAUSE_CONDITIONAL_IE_MISSING | Conditional IE Missing | PFCP | 67 |
| 435 | PFCP_CAUSE_INVALID_LENGTH | Invalid message length | PFCP | 68 |
| 436 | PFCP_CAUSE_MANDATORY_IE_INCORRECT | Mandatory IE Incorrect | PFCP | 69 |
| 501 | SBI_307_TMP_REDIRECT | — | HTTP | 307 |
| 502 | SBI_308_PERM_REDIRECT | — | HTTP | 308 |
| 503 | SBI_400_BAD_REQUEST_INVALID_API | — | HTTP | 400 |
| 504 | SBI_400_BAD_REQUEST_INVALID_MESSAGE_FORMAT | — | HTTP/2 | 400 |
| 505 | SBI_400_BAD_REQUEST_INVALID_QUERY_PARAM | — | HTTP/2 | 400 |
| 506 | SBI_400_BAD_REQUEST_MANDATORY_IE_INCORRECT | — | HTTP/2 | 400 |
| 507 | SBI_400_BAD_REQUEST_MANDATORY_IE_MISSING | — | HTTP/2 | 400 |
| 508 | SBI_400_BAD_REQUEST_MANDATORY_QUERY_PARAM_INCORRECT | — | HTTP/2 | 400 |
| 509 | SBI_400_BAD_REQUEST_MANDATORY_QUERY_PARAM_MISSING | — | HTTP/2 | 400 |
| 510 | SBI_400_BAD_REQUEST_OPTIONAL_IE_INCORRECT | — | HTTP/2 | 400 |
| 511 | SBI_400_BAD_REQUEST_OPTIONAL_QUERY_PARAM_INCORRECT | — | HTTP/2 | 400 |
| 512 | SBI_400_BAD_REQUEST_UNSPECIFIED_MSG_FAILURE | — | HTTP/2 | 400 |
| 513 | SBI_403_FORBIDDEN_DEFAULT_EPS_BEARER_INACTIVE | — | HTTP/2 | 403 |
| 514 | SBI_403_FORBIDDEN_DNN_DENIED | — | HTTP/2 | 403 |
| 515 | SBI_403_FORBIDDEN_DNN_NOT_SUPPORTED | — | HTTP/2 | 403 |
| 516 | SBI_403_FORBIDDEN_EBI_EXHAUSTED | — | HTTP/2 | 403 |
| 517 | SBI_403_FORBIDDEN_EBI_REJECTED_LOCAL_POLICY | — | HTTP/2 | 403 |
| 518 | SBI_403_FORBIDDEN_EBI_REJECTED_NO_N26 | — | HTTP/2 | 403 |
| 519 | SBI_403_FORBIDDEN_HO_TAU_IN_PROGRESS | — | HTTP/2 | 403 |
| 520 | SBI_403_FORBIDDEN_HOME_ROUTED_ROAMING_REQUIRED | — | HTTP/2 | 403 |
| 521 | SBI_403_FORBIDDEN_INTEGRITY_PROTECTED_MDR_NOT_ACCEPTABLE | — | HTTP/2 | 403 |
| 522 | SBI_403_FORBIDDEN_MODIFICATION_NOT_ALLOWED | — | HTTP/2 | 403 |
| 523 | SBI_403_FORBIDDEN_N1_SM_ERROR | — | HTTP/2 | 403 |
| 524 | SBI_403_FORBIDDEN_N2_SM_ERROR | — | HTTP/2 | 403 |
| 525 | SBI_403_FORBIDDEN_NO_EPS_5GS_CONTINUITY | — | HTTP/2 | 403 |
| 526 | SBI_403_FORBIDDEN_OUT_OF_LADN_SERVICE_AREA | — | HTTP/2 | 403 |
| 527 | SBI_403_FORBIDDEN_PDU_SESSION_ANCHOR_CHANGE | — | HTTP/2 | 403 |
| 528 | SBI_403_FORBIDDEN_PDUTYPE_DENIED | — | HTTP/2 | 403 |
| 529 | SBI_403_FORBIDDEN_PDUTYPE_NOT_SUPPORTED | — | HTTP/2 | 403 |
| 530 | SBI_403_FORBIDDEN_PRIORITIZED_SERVICES_ONLY | — | HTTP/2 | 403 |
| 531 | SBI_403_FORBIDDEN_REJECTED_BY_UE | — | HTTP/2 | 403 |
| 532 | SBI_403_FORBIDDEN_REJECTED_DUE_VPLMN_POLICY | — | HTTP/2 | 403 |
| 533 | SBI_403_FORBIDDEN_SNSSAI_DENIED | — | HTTP/2 | 403 |
| 534 | SBI_403_FORBIDDEN_SSC_DENIED | — | HTTP/2 | 403 |
| 535 | SBI_403_FORBIDDEN_SSC_NOT_SUPPORTED | — | HTTP/2 | 403 |
| 536 | SBI_403_FORBIDDEN_SUBSCRIPTION_DENIED | — | HTTP/2 | 403 |
| 537 | SBI_403_FORBIDDEN_TARGET_MME_CAPABILITY | — | HTTP/2 | 403 |
| 538 | SBI_403_FORBIDDEN_UE_NOT_RESPONDING | — | HTTP/2 | 403 |
| 539 | SBI_403_FORBIDDEN_UNABLE_TO_PAGE_UE | — | HTTP/2 | 403 |
| 540 | SBI_404_NOT_FOUND_CONTEXT_NOT_FOUND | — | HTTP/2 | 404 |
| 541 | SBI_404_NOT_FOUND_RESOURCE_URI_STRUCTURE_NOT_FOUND | — | HTTP/2 | 404 |
| 542 | SBI_404_NOT_FOUND_SUBSCRIPTION_NOT_FOUND | — | HTTP/2 | 404 |
| 543 | SBI_411_LENGTH_REQUIRED_INCORRECT_LENGTH | — | HTTP/2 | 411 |
| 544 | SBI_429_TOO_MANY_REQUESTS_NF_CONGESTION_RISK | — | HTTP/2 | 429 |
| 545 | SBI_500_INTERNAL_SERVER_ERROR_INSUFFICIENT_RESOURCES | — | HTTP/2 | 500 |
| 546 | SBI_500_INTERNAL_SERVER_ERROR_INSUFFICIENT_RESOURCES_SLICE | — | HTTP/2 | 500 |
| 547 | SBI_500_INTERNAL_SERVER_ERROR_INSUFFICIENT_RESOURCES_SLICE_DNN | — | HTTP/2 | 500 |
| 548 | SBI_500_INTERNAL_SERVER_ERROR_SYSTEM_FAILURE | — | HTTP/2 | 500 |
| 549 | SBI_500_INTERNAL_SERVER_ERROR_UNSPECIFIED_NF_FAILURE | — | HTTP/2 | 500 |
| 550 | SBI_503_SERVICE_UNAVAILABLE_DNN_CONGESTION | — | HTTP/2 | 503 |
| 551 | SBI_503_SERVICE_UNAVAILABLE_NF_CONGESTION | — | HTTP/2 | 503 |
| 552 | SBI_503_SERVICE_UNAVAILABLE_S_NSSAI_CONGESTION | — | HTTP/2 | 503 |
| 553 | SBI_504_GATEWAY_TIMEOUT_NETWORK_FAILURE | — | HTTP/2 | 504 |
| 554 | SBI_504_GATEWAY_TIMEOUT_PEER_NOT_RESPONDING | — | HTTP/2 | 504 |
| 555 | SBI_400_BAD_REQUEST_CHARGING_FAILED | — | HTTP/2 | 400 |
| 556 | SBI_403_FORBIDDEN_CHARGING_NOT_APPLICABLE | — | HTTP/2 | 403 |
| 557 | SBI_403_FORBIDDEN_END_USER_REQUEST_DENIED | — | HTTP/2 | 403 |
| 558 | SBI_403_FORBIDDEN_QUOTA_LIMIT_REACHED | — | HTTP/2 | 403 |
| 559 | SBI_403_FORBIDDEN_END_USER_REQUEST_REJECTED | — | HTTP/2 | 403 |
| 560 | SBI_404_NOT_FOUND_USER_UNKNOWN | — | HTTP/2 | 404 |
| 561 | N10_UNAUTHORIZED_ERROR | Error when building HTTP/2 Authorization Header | HTTP/2 | — |
| 562 | N10_EXTERNAL_ERROR | Various error cases when decoding N10 peer message | HTTP/2 | — |
| 563 | N10_INTERNAL_ERROR | Various error cases when sending HTTP/2 N10 peer message | HTTP/2 | — |
| 564 | N7_INTERNAL_ERROR | Various error cases when sending HTTP/2 N7 peer message | HTTP/2 | — |
| 565 | SBI_400_BAD_REQUEST | — | HTTP/2 | 400 |
| 566 | SBI_403_FORBIDDEN | — | HTTP/2 | 403 |
| 567 | SBI_404_NOT_FOUND | — | HTTP/2 | 404 |
| 568 | SBI_411_LENGTH_REQUIRED | — | HTTP/2 | 411 |
| 569 | SBI_429_TOO_MANY_REQUESTS | — | HTTP/2 | 429 |
| 570 | SBI_500_INTERNAL_SERVER_ERROR | — | HTTP/2 | 500 |
| 571 | SBI_503_SERVICE_UNAVAILABLE | — | HTTP/2 | 503 |
| 572 | SBI_504_GATEWAY_TIMEOUT | — | HTTP/2 | 504 |
| 573 | SBI_403_UE_IN_NON_ALLOWED_AREA | — | HTTP/2 | 573 |
Detailed causes
| Detailed cause ID | Description | Related event | Related cause |
|---|---|---|---|
| 1008 | Address Pool Missing/cfg | LTE_ADDR_POOL_NOT_PRESENT | GTP1_CAUSE_NO_RESOURCES |
| 1009 | Unsupported Auth Type | LTE_UNSUPP_AUTH_TYPE | GTP1_CAUSE_AUTH_FAILURE |
| 1010 | Invalid Authentication Key | LTE_INV_AUTH_KEY | GTP1_CAUSE_AUTH_FAILURE |
| 1011 | Invalid Authentication Type | LTE_INV_AUTH_TYPE | GTP1_CAUSE_AUTH_FAILURE |
| 1012 | Authentication Failed | LTE_AUTH_FAIL | GTP1_CAUSE_AUTH_FAILURE |
| 1013 | Failed | LTE_FAILED | GTP1_CAUSE_USER_AUTH_FAILURE |
| 1014 | UE Reattach | LTE_UE_REATTACH | GTP_CAUSE_SUCCESS |
| 1015 | User authentication failure | LTE_USER_AUTH_FAIL | GTP1_CAUSE_USER_AUTH_FAILURE |
| 1016 | Diameter (PCRF) disabled | LTE_DIAM_PCRF_DISABLED | GTP1_CAUSE_USER_AUTH_FAILURE |
| 1017 | ROL session establishment failure | LTE_ROL_SESS_FAILED | GTP1_CAUSE_USER_AUTH_FAILURE |
| 1018 | Addr Alloc Failed | LTE_ADDR_ALLOC_FAIL | GTP1_CAUSE_PDP_ADDR_NOT_AVAI |
| 1019 | Address Pool Exhausted | LTE_ADDR_POOL_EXHAUSTED | GTP1_CAUSE_PDP_ADDR_NOT_AVAI |
| 1020 | Address Pool Empty | LTE_ADDR_POOL_EMPTY | GTP1_CAUSE_PDP_ADDR_NOT_AVAI |
| 1021 | APN access denied | LTE_APN_ACCESS_DENIED | GTP1_CAUSE_APN_ACC_DENIED |
| 1022 | APN Selection Mode Mismatch | LTE_APN_SELECTION_MODE_MISMATCH | GTP1_CAUSE_APN_ACC_DENIED |
| 1023 | Session Termination because of Timeout | LTE_SESSION_TIMEOUT | GTP_CAUSE_PDN_INACTIVE_TIMEOUT |
| 1024 | Delete Session Idle Timeout | LTE_IDLE_TIMEOUT | GTP_CAUSE_PDN_INACTIVE_TIMEOUT |
| 1025 | UE Context Not Found | LTE_UE_CTXT_NOT_FOUND | GTP_CAUSE_CONTEXT_NOT_FOUND |
| 1026 | PDN Context Not Found | LTE_PDN_CTXT_NOT_FOUND | GTP_CAUSE_CONTEXT_NOT_FOUND |
| 1027 | Bearer Context Not Found | LTE_BEARER_CTXT_NOT_FOUND | GTP_CAUSE_CONTEXT_NOT_FOUND |
| 1028 | BCE PBU Prefixes Set Mismatch | LTE_BCE_PBU_PFX_SET_MISMATCH | GTP_CAUSE_CONTEXT_NOT_FOUND |
| 1029 | Unexpected IE | LTE_IE_UNEXPECTED | GTP_CAUSE_INVALID_MSG_FMT |
| 1030 | Proxy registration not enabled for the mobile node | LTE_PROXY_REG_NOT_ENABLED | GTP_CAUSE_SERVICE_NOT_SUPPORTED |
| 1031 | Not local mobility anchor for the mobile node | LTE_NOT_LMA_FOR_THIS_MN | GTP_CAUSE_SERVICE_NOT_SUPPORTED |
| 1032 | The mobile access gateway is not authorized to send proxy binding updates | LTE_MAG_NO_AUTH_FOR_PROXY_REG | GTP_CAUSE_SERVICE_NOT_SUPPORTED |
| 1033 | Service Not Supported | LTE_SERVICE_NOT_SUPPORTED | GTP_CAUSE_SERVICE_NOT_SUPPORTED |
| 1034 | Timestamp Mismatch | LTE_TIMESTAMP_MISMATCH | GTP_CAUSE_MANDAT_IE_INCORRECT |
| 1035 | Older Timestamp | LTE_TIMESTAMP_IN_PAST | GTP_CAUSE_MANDAT_IE_INCORRECT |
| 1036 | Invalid Mand/Cond IE | LTE_INV_REQ_IE | GTP_CAUSE_MANDAT_IE_INCORRECT |
| 1037 | Missing Home Net Pfx Option | LTE_MISSING_HOME_NET_PFX_OPT | GTP_CAUSE_MANDAT_IE_MISSING |
| 1038 | Missing UE ID Option | LTE_MISSING_MN_IDENTIFIER_OPT | GTP_CAUSE_MANDAT_IE_MISSING |
| 1039 | Missing Handoff Ind Option | LTE_MISSING_HANDOFF_INDICATOR_OPT | GTP_CAUSE_MANDAT_IE_MISSING |
| 1040 | Missing Access Tech Type Option | LTE_MISSING_ACCESS_TECH_TYPE_OPT | GTP_CAUSE_MANDAT_IE_MISSING |
| 1041 | Missing IE | LTE_MISSING_IE | GTP_CAUSE_MANDAT_IE_MISSING |
| 1042 | Addr Pool Invalid Mscp | LTE_ADDR_POOL_INVALID_MSCP | GTP_CAUSE_ALL_DYNAMIC_ADDR_OCCUPIED |
| 1043 | One of the Gateways is active or the MSCP group is active | LTE_BUSY | GTP_CAUSE_UE_NOT_RESPONDING |
| 1044 | Relinking Attributes failed - discarded | LTE_DISCARD | GTP_CAUSE_UE_REFUSES |
| 1045 | Unauthorized for Home Net Pfx | LTE_NO_AUTH_FOR_HOME_NET_PFX | GTP_CAUSE_USER_AUTH_FAILED |
| 1047 | MME No Resp | LTE_MME_NO_RESP | GTP_CAUSE_REM_PEER_NO_RESPONSE |
| 1048 | PGW No Resp | LTE_PGW_NO_RESP | GTP_CAUSE_REM_PEER_NO_RESPONSE |
| 1049 | SGW No Resp | LTE_SGW_NO_RESP | GTP_CAUSE_REM_PEER_NO_RESPONSE |
| 1050 | Disallowed RAT Type | LTE_DISALLOWED_RAT | GTP_CAUSE_DENIED_RAT |
| 1051 | Peer is considered to be down | LTE_PEER_DOWN | GTP_CAUSE_SUCCESS |
| 1052 | Multiple failed rules | RFC_MULTIPLE_FAILED_RULES | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1053 | Unknown Rule Name | RFC_UNK_RULE_NAME | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1054 | Rating group Error | RFC_RATING_GRP_ERR | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1055 | Service ID error | RFC_SERVICE_ID_ERR | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1056 | Gateway Malfunction | RFC_GW_MALFUNC | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1057 | Resource Limitation | RFC_RESOURCE_LIMIT | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1058 | Max number of Bearers reached | RFC_MAX_NR_BEARER_REACHED | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1059 | Unknown Bearer ID | RFC_UNK_BEARER_ID | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1060 | Missing Bearer ID | RFC_MISS_BEARER_ID | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1061 | Missing Flow Description | RFC_MISS_FLOW_DESCRIPTION | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1062 | Resource allocation Failure | RFC_RSRC_ALLOC_FAILURE | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1063 | Unsuccessful QoS validation | RFC_UNSUCC_QOS_VALIDATION | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1064 | Incorrect flow information | RFC_INCORRECT_FLOW_INFO | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1065 | PS to CS handover | RFC_PS2CS_HANDOVER | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1066 | TDF application identifier error | RFC_TDF_APPL_ID_ERR | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1067 | No IP-CAN bearer without traffic mapping information | RFC_NO_BEARER_BOUND | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1068 | Filter restrictions | RFC_FILTER_RESTRICTIONS | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1069 | AN gateway failed | RFC_ANGW_FAILED | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1070 | Missing redirect server address | RFC_MISS_REDIR_SERVR_ADDR | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1071 | End user service denied | RFC_CM_END_USER_SERVICE_DENIED | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1072 | Credit control not applicable | RFC_CM_CREDIT_CONTROL_NOT_APPLICABLE | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1073 | Authorization rejected | RFC_CM_AUTHORIZATION_REJECTED | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1074 | User unknown | RFC_CM_USER_UNKNOWN | DIAMETER_PCC_BEARER_EVENT/ DIAMETER_PCC_RULE_ EVENT |
| 1075 | Rating failed | RFC_CM_RATING_FAILED | — |
| 1076 | Diameter Internal Error | DIAMETER_INTERNAL_ERROR | — |
| 1077 | Diameter Fsm Error | DIAMETER_FSM_ERROR | — |
| 1078 | Diameter PCRF OOS | DIAMETER_PCRF_OOS | — |
| 1079 | Diameter PCRF Disabled | DIAMETER_PCRF_DISABLED | — |
| 1080 | Diameter Mem Error | DIAMETER_MEM_ERROR | — |
| 1081 | Diameter Tx Tmr Expiry | DIAMETER_TX_TMR_EXPIRY | — |
| 1082 | Diameter Gen EncodeError | DIAMETER_GEN_ENCODE_ERROR | — |
| 1083 | Diameter Gen Decode Error | DIAMETER_GEN_DECODE_ERROR | — |
| 1084 | Diameter AMS Error | DIAMETER_AMS_ERROR | — |
| 1085 | Diameter Session Gone | DIAMETER_SESSION_GONE | — |
| 1086 | Diameter Timer Error | DIAMETER_TIMER_ERROR | — |
| 1087 | LTE APN is shut | LTE_APN_IS_SHUT | GTP_CAUSE_APN_ACCESS_DENIED |
| 1088 | LTE is missing PCO IE | LTE_MISSING_PCO_IE | GTP_CAUSE_MANDAT_IE_MISSING |
| 1089 | GTP request is rejected because dual connectivity is disabled | LTE_DUAL_CONNECTIVITY_NOT_SUPPORTED | GTP_CAUSE_SERVICE_NOT_SUPPORTED |
| 1090 | Session is rejected because of Diameter Overload Indication Conveyance (DOIC) | DIAMETER_DOIC_DROP | GTP_CAUSE_NO_ RESOURCES |
| 1094 | Context not found | LTE_NOT_FOUND | HTTP_STATUS_404_CONTEXT_NOT_FOUND |
| 1095 | Local Area DN Session Release | LTE_LADN_PDU_SESS_REL | — |
| 1096 | Failure Sending Message | LTE_MSG_SEND_FAIL | — |
| 1097 | N2 Encoding Failure | LTE_N2_ENCODE_FAIL | — |
| 1098 | Encoding Failure | LTE_ENCODE_FAIL | — |
| 1099 | AMF Configuration Error | LTE_AMF_CFG_NF_FAIL | — |
| 1100 | PDU Session Rejected Only Allow IPv4 | LTE_PDU_ONLY_ALLOW_IPV4 | HTTP_STATUS_403_PDUTYPE_DENIED |
| 1101 | PDU Session Rejected Only Allow IPv6 | LTE_PDU_ONLY_ALLOW_IPV6 | HTTP_STATUS_403_PDUTYPE_DENIED |
| 1102 | SSC mode is not supported | LTE_UNSUPPORTED_SSCMODE | HTTP_STATUS_403_SSC_NOT_SUPPORTED |
| 1103 | Insufficient resource in slice | LTE_INSUFFICIENT_RES_SLICE | HTTP_STATUS_500_INSUFFIC_RESOURCES_SLICE |
| 1104 | PDU session type unknown | LTE_UNKNOWN_PDU_SESSTYPE | HTTP_STATUS_403_PDUTYPE_DENIED |
| 1105 | N2 PDU Setup Failure | LTE_N2_ESTB_FAIL | HTTP_STATUS_200_OK |
| 1106 | N1_T3591 and N1_T3592 timeout | LTE_N1_TIMER_TIMEOUT | — |
| 1107 | N2 Decoding Failure | LTE_N2_DECODING_FAILED |
HTTP_STATUS_500_UNSPECIFIED_NF_FAILURE / HTTP_STATUS_403_N2_SM_ERROR |
| 1108 | AMF reported 5G AN not responding | LTE_AN_NOT_RESPONDING | — |
| 1110 | UPF no response | LTE_PEER_REQ_TIMEOUT | — |
Message marker IDs and SBI service operation messages
| Message marker ID | Message interface, name, direction / service operation | Node | Protocol | Interface / SBI service |
|---|---|---|---|---|
| 0 | No_Message | N/A | N/A | N/A |
| 1 | Create_Session_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 2 | Create_Session_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 3 | Delete_Session_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 4 | Delete_Session_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 5 | Modify_Bearer_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 6 | Modify_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 7 | Resume_Notification | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 8 | Resume_Acknowledge | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 9 | Modify_Bearer_Command | SGW, PGW, combined SGW‑C + PGW‑C | GTPv2 | S11 |
| 10 | Modify_Bearer_Failure_Indication | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 11 | Delete_Bearer_Command | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 12 | Delete_Bearer_Failure_Indication | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 13 | Bearer_Resource_Command | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 14 | Bearer_Resource_Failure_Indication | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 15 | Downlink_Data_Notification_Failure_Indication | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 16 | Create_Bearer_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 17 | Create_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 18 | Update_Bearer_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 19 | Update_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 20 | Delete_Bearer_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 21 | Delete_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 22 | Suspend_Notification | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 23 | Suspend_Acknowledge | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 24 | Create_Indirect_Data_Forwarding_Tunnel_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 25 | Create_Indirect_Data_Forwarding_Tunnel_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 26 | Delete_Indirect_Data_Forwarding_Tunnel_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 27 | Delete_Indirect_Data_Forwarding_Tunnel_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 28 | Release_Access_Bearers_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 29 | Release_Access_Bearers_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 30 | Downlink_Data_Notification | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 31 | Downlink_Data_Notification_Acknowledge | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 32 | PGW_Restart_Notification | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 33 | PGW_Restart_Notification_Acknowledge | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 82 | Modify_Access_Bearer_Request | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 83 | Modify_Access_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 83 | Modify_Access_Bearer_Response | Combined SGW-C + PGW‑C | GTPv2 | S11 |
| 84 | PFCP Session Establishment Request | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 85 | PFCP Session Establishment Response | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 86 | PFCP Session Modification Request | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 87 | PFCP Session Modification Response | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 88 | PFCP Session Deletion Request | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 89 | PFCP Session Deletion Response | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 90 | PFCP Session Report Request | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 91 | PFCP Session Report Response | Combined SGW-C + PGW‑C | PFCP | Sx, N4 |
| 101 | Create SM Context Request | SMF | HTTP/2 | Nsmf_PDUSession |
| 102 | Create SM Context Response | SMF | HTTP/2 | Nsmf_PDUSession |
| 103 | Update SM Context Request | SMF | HTTP/2 | Nsmf_PDUSession |
| 104 | Update SM Context Response | SMF | HTTP/2 | Nsmf_PDUSession |
| 105 | Release SM Context Request | SMF | HTTP/2 | Nsmf_PDUSession |
| 106 | Release SM Context Response | SMF | HTTP/2 | Nsmf_PDUSession |
| 107 | SM Context Notify Request | SMF | HTTP/2 | Nsmf_PDUSession |
| 108 | SM Context Notify Response | SMF | HTTP/2 | Nsmf_PDUSession |
| 109 | N1N2MessageTransfer Request | SMF | HTTP/2 | Namf_Communication |
| 110 | N1N2MessageTransfer Response | SMF | HTTP/2 | Namf_Communication |
| 111 | N1N2Message Transfer Failure Notification Request | SMF | HTTP/2 | Namf_Communication |
| 112 | N1N2Message Transfer Failure Notification Response | SMF | HTTP/2 | Namf_Communication |
| 115 | Subscriber Data Management Get Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 116 | Subscriber Data Management Get Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 117 | Subscriber Data Management Subscribe Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 118 | Subscriber Data Management Subscribe Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 119 | Subscriber Data Management Unsubscribe Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 120 | Subscriber Data Management Unsubscribe Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 121 | Subscriber Data Change Notification Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 122 | Subscriber Data Change Notification Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_SubscriberDataManagement |
| 123 | UE Context Management Register Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_UEContextManagement |
| 124 | UE Context Management Register Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_UEContextManagement |
| 125 | UE Context Management Deregister Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_UEContextManagement |
| 126 | UE Context Management Deregister Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Nudm_UEContextManagement |
| 127 | SM Policy Control Get Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 128 | SM Policy Control Get Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 129 | SM Policy Control Delete Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 130 | SM Policy Control Delete Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 131 | SM Policy Control Update Notify Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 132 | SM Policy Control Update Notify Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 133 | SM Policy Control Update Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 134 | SM Policy Control Update Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 135 | Charging Data Request [Initial] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 136 | Charging Data Response [Initial] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 137 | Charging Data Request [Update] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 138 | Charging Data Response [Update] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 139 | Charging Data Request [Terminate] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 140 | Charging Data Response [Terminate] | SMF, combined SGW-C + PGW-C | HTTP/2 | Nchf_ConvergedCharging |
| 141 | SM Policy Control Delete Notify Request | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 142 | SM Policy Control Delete Notify Response | SMF, combined SGW-C + PGW-C | HTTP/2 | Npcf_SMPolicyControl |
| 143 | EBI Request | SMF | HTTP/2 | Namf_Communication |
| 144 | EBI Response | SMF | HTTP/2 | Namf_Communication |
Reference point and SBI services IDs
| Reference point ID / service ID | Reference point / SBI service name | Involved Nodes | Protocol |
|---|---|---|---|
| 0 | Unknown | N/A | N/A |
| 1 | S11 | Combined SGW-C + PGW-C, MME | GTPv2 |
| 15 | Combined Sxa/Sxb | Combined SGW-C + PGW-C, UPF | PFCP |
| 16 | N4 | SMF, UPF | PFCP |
| 17 | Nsmf_PDUSession | SMF, AMF | HTTP/2 |
| 19 | Namf_Communication | SMF, AMF | HTTP/2 |
| 22 | Nudm_SubscriberDataManagement | SMF, Combined SGW-C + PGW‑C, UDM | HTTP/2 |
| 23 | Nudm_UEContextManagement | SMF, Combined SGW-C + PGW‑C, UDM | HTTP/2 |
| 24 | Npcf_SMPolicyControl | SMF, Combined SGW-C + PGW‑C, PCF | HTTP/2 |
| 25 | Nchf_ConvergedCharging | SMF, Combined SGW-C + PGW‑C, CHF | HTTP/2 |
Direction_n IDs
| Direction ID | Direction |
|---|---|
| 0 | Ingress |
| 1 | Egress |