통신/RFC
[RFC7296] Private Notify Message - Error Types / Private Notify Message - Status Types
2022. 7. 6. 01:00반응형
Private Notify Message - Error Types
24502
Table 9.2.4.2-1: Private Error Types
Notify Message | Value (in decimal) |
Descriptions |
CONGESTION | 15500 | This error type is used to indicate that the requested service was rejected because of congestion in the network. |
NO_RESOURCES_OVER_N3GPP | 15501 | This error type is used by the UE to indicate the failure of reserving the QoS resources over non-3GPP access for the QoS flows associated with the child SA. |
23502
Table 8.1.2.2-1: Private Error Types
Notify Message | Value (in decimal) |
Descriptions |
PDN_CONNECTION_REJECTION | 8192 | With an IP address information in Notification Data field: The PDN connection corresponding to the IP address information has been rejected. Without Notification Data field: The PDN connection corresponding to the requested APN has been rejected. No additional PDN connections to the given APN can be established. If the rejected PDN connection is the first PDN connection for the given APN, this APN is not allowed for the UE. |
MAX_CONNECTION_REACHED | 8193 | The PDN connection has been rejected. No additional PDN connections can be established for the UE due to the network policies or capabilities. The maximum number of PDN connections per UE allowed to be established simultaneously is limited by the number of EPS bearer identities (see clause 11.2.3.1.5 of 3GPP TS 24.007 [48]) or by the number of PDU session IDs (see clause 11.2.3.1b of 3GPP TS 24.007 [48]). |
SEMANTIC_ERROR_IN_THE_TFT_OPERATION | 8241 | This error type is used to indicate that the requested service was rejected due to a semantic error in the TFT operation included in the request. |
SYNTACTICAL_ERROR_IN_THE_TFT_OPERATION | 8242 | This error type is used to indicate that the requested service was rejected due to a syntactical error in the TFT operation included in the request. |
SEMANTIC_ERRORS_IN_PACKET_FILTERS | 8244 | This error type is used to indicate that the requested service was rejected due to a semantic error in the packet filter(s) included in the request. |
SYNTACTICAL_ERRORS_IN_PACKET_FILTERS | 8245 | This error type is used to indicate that the requested service was rejected due to a syntactical error in the packet filter(s) included in the request. |
NON_3GPP_ACCESS_TO_EPC_NOT_ALLOWED | 9000 | Corresponds to: - DIAMETER_ERROR_USER_NO_NON_3GPP_SUBSCRIPTION Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the UE is not allowed to use non-3GPP access to EPC. |
USER_UNKNOWN | 9001 | Corresponds to: - DIAMETER_ERROR_USER_UNKNOWN Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the user identified by the IMSI is unknown. |
NO_APN_SUBSCRIPTION | 9002 | Corresponds to: - DIAMETER_ERROR_USER_NO_APN_SUBSCRIPTION Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the requested APN is not included in the user's profile, and therefore is not authorized for that user.. |
AUTHORIZATION_REJECTED | 9003 | Corresponds to: - DIAMETER_AUTHORIZATION_REJECTED Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the user is barred from using the non-3GPP access or the subscribed APN. |
ILLEGAL_ME | 9006 | Corresponds to: - DIAMETER_ERROR_ILLEGAL_EQUIPMENT Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the ME used is not accepted by the network. |
NETWORK_FAILURE | 10500 | Corresponds to: - DIAMETER_ERROR_UNABLE_TO_COMPLY Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the network has determined that the requested procedure cannot be completed successfully due to network failure. |
RAT_TYPE_NOT_ALLOWED | 11001 | Corresponds to: - DIAMETER_RAT_TYPE_NOT_ALLOWED Result code IE as specified in 3GPP TS 29.273 [17]; or - Other scenarios when the access type is restricted to the user. |
IMEI_NOT_ACCEPTED | 11005 | The emergency PDN connection request has been rejected since the network does not accept an emergency service request using an IMEI. |
PLMN_NOT_ALLOWED | 11011 | Corresponds to: - DIAMETER_ERROR_ROAMING_NOT_ALLOWED Result code IE as specified in 3GPP TS 29.273 [17]; - The ePDG performs PLMN filtering (based on roaming agreements) and rejects the request from the UE; or - Other scenarios when the UE requests service in a PLMN where the UE is not allowed to operate. |
UNAUTHENTICATED_ EMERGENCY_ NOT_SUPPORTED |
11055 | The emergency PDN connection request has been rejected due to authentication has failed or authentication cannot proceed at AAA server, and the ePDG does not support an emergency service request using an unauthenticated IMSI. |
Private Notify Message - Status Types
24302
Table 8.1.2.3-1: Private Status Types
Notify Message | Value (in decimal) |
Descriptions |
REACTIVATION_REQUESTED_CAUSE | 40961 | The IPsec tunnel associated to a PDN connection is released with a cause requesting the UE to reestablish the IPsec tunnel for the same PDN Connection after its release. |
BACKOFF_TIMER | 41041 | The value of the backoff timer is included in the BACKOFF_TIMER Notify payload as specified in clause 8.2.9.1. |
PDN_TYPE_IPv4_ONLY_ALLOWED | 41050 | This value is used by the network to indicate that only PDN type IPv4 is allowed for the requested PDN connectivity. |
PDN_TYPE_IPv6_ONLY_ALLOWED | 41051 | This value is used by the network to indicate that only PDN type IPv6 is allowed for the requested PDN connectivity. |
DEVICE_IDENTITY | 41101 | The device identity type and/or identity value are included in the DEVICE_IDENTITY Notify payload as specified in clause 8.2.9.2. |
EMERGENCY_SUPPORT | 41112 | This status when present indicates that the ePDG supports emergency service. The EMERGENCY_SUPPORT Notify payload is coded according to clause 8.2.9.7. |
EMERGENCY_CALL_NUMBERS | 41134 | Additional local emergency call numbers that the UE may use for detecting UE initiated emergency calls. The EMERGENCY_CALL_NUMBERS Notify payload is coded according to clause 8.2.9.8. |
NBIFOM_GENERIC_CONTAINER | 41288 | The NBIFOM parameters are included in the NBIFOM_GENERIC_CONTAINER Notify payload as specified in clause 8.2.9.3. |
P-CSCF_RESELECTION_SUPPORT | 41304 | This status when present indicates that the UE supports the P-CSCF restoration extension for untrusted WLAN |
PTI | 41501 | An INFORMATIONAL request message of an ePDG-initiated modification procedure is initiated by another INFORMATIONAL request message of an UE-initiated modification procedure. The PTI Notify payload is coded according to clause 8.2.9.5. |
IKEV2_MULTIPLE_BEARER_PDN_CONNECTIVITY | 42011 | This status when present indicates that the UE supports IKEv2 multiple bearer PDN connectivity. The IKEV2_MULTIPLE_BEARER_PDN_CONNECTIVITY Notify payload is coded according to clause 8.2.9.9. |
EPS_QOS | 42014 | This status when present indicates EPS QoS. The EPS_QOS Notify payload is coded according to clause 8.2.9.10. |
EXTENDED_EPS_QOS | 42015 | This status when present indicates extended EPS QoS. The EXTENDED_EPS_QOS Notify payload is coded according to clause 8.2.9.10A. |
TFT | 42017 | This status when present indicates TFT. The TFT Notify payload is coded according to clause 8.2.9.11. |
MODIFIED_BEARER | 42020 | This status when present indicates sender's ESP SPI. The MODIFIED_BEARER Notify payload is coded according to clause 8.2.9.12. |
APN_AMBR | 42094 | This status when present indicates APN-AMBR. The APN_AMBR Notify payload is coded according to clause 8.2.9.13. |
EXTENDED_APN_AMBR | 42095 | This status when present indicates extended APN-AMBR. The EXTENDED_APN_AMBR Notify payload is coded according to clause 8.2.9.14. |
N1_MODE_CAPABILITY | 51015 | This status when present indicates support of N1 mode or N1 mode capability is disabled. The N1_MODE_CAPABILITY Notify payload is coded according to clause 8.2.9.15. |
N1_MODE_INFORMATION | 51115 | This status when present indicates N1 mode information. The N1_MODE_INFORMATION Notify payload is coded according to clause 8.2.9.16. |
N1_MODE_S_NSSAI_PLMN_ID | 52216 | This status when present indicates the PLMN ID that the S-NSSAI relates to. The N1_MODE_S_NSSAI_PLMN_ID Notify payload is coded according to clause 8.2.9.17. |
24502
Table 9.2.4.3-1: Private Status Types
Notify Message | Value (in decimal) |
Descriptions |
5G_QOS_INFO | 55501 | This status when present indicates 5G_QOS_INFO Notify payload encoded according to clause 9.3.1.1 |
NAS_IP4_ADDRESS | 55502 | This status when present indicates NAS_IP4_ADDRESS Notify payload encoded according to clause 9.3.1.2. |
NAS_IP6_ADDRESS | 55503 | This status when present indicates NAS_IP6_ADDRESS Notify payload encoded according to clause 9.3.1.3. |
UP_IP4_ADDRESS | 55504 | This status when present indicates UP_IP4_ADDRESS Notify payload encoded according to clause 9.3.1.4. |
UP_IP6_ADDRESS | 55505 | This status when present indicates UP_IP6_ADDRESS Notify payload encoded according to clause 9.3.1.5. |
NAS_TCP_PORT | 55506 | This status when present indicates NAS_TCP_PORT Notify payload encoded according to clause 9.3.1.6. |
N3GPP_BACKOFF_TIMER | 55507 | This status when present indicates N3GPP_BACKOFF_TIMER Notify payload encoded according to clause 9.3.1.7. |
반응형
'통신 > RFC' 카테고리의 다른 글
RFC6356 (1) | 2024.02.13 |
---|---|
[RFC7296] Traffic Selector (0) | 2022.04.29 |
[RFC7296] RFC7296: INTERNAL_IP4_ADDRESS 및 INTERNAL_IP6_ADDRESS는 무엇을 의미할까? (0) | 2022.04.29 |
[RFC7296] IKEv2 IPsec SPI와 IKE SPI (0) | 2022.04.13 |
[RFC7296] IKEv2 정리 (Main) (0) | 2021.12.12 |