SlideShare a Scribd company logo
1 of 7
Code
5G PDU
In next page, I mentioned Failure Cause codes
and in coming pages, description for each
cause code is explained.
It can be used for Optimization , Maintenance , Monitoring
and Troubleshooting.
Cause Number Cause Value Cause Number Cause Value
#8 Operator Determined Barring #46 Out of LADN service area
#26 Insufficient resources #47 PTI mismatch
#27 Missing or unknown DNN #50 PDU session type IPv4 only allowed
#28 Unknown PDU session type #51 PDU session type IPv6 only allowed
#29 User authentication or authorization failed #54 PDU session does not exist
#31 Request rejected, unspecified #57 PDU session type IPv4v6 only allowed
#32 Service option not supported #58 PDU session type Unstructured only allowed
#33 Requested service option not subscribed #59 Unsupported 5QI value
#35 PTI already in use #61 PDU session type Ethernet only allowed
#36 Regular deactivation #67 Insufficient resources for specific slice and DNN
#37 5GS QoS not accepted #68 Not supported SSC mode
#38 Network failure #69 Insufficient resources for specific slice
#39 Reactivation requested #70 Missing or unknown DNN in a slice
#41 Semantic error in the TFT operation #81 Invalid PTI value
#42 Syntactical error in the TFT operation #82 Maximum data rate per UE for user-plane integrity protection is too low
#43 Invalid PDU session identity #83 Semantic error in the QoS operation
#44 Semantic errors in packet filter(s) #84 Syntactical error in the QoS operation
#45 Syntactical error in packet filter(s) #85 Invalid mapped EPS bearer identity
cause number Cause value Description
#8 Operator Determined Barring is used by the network to indicate that the requested service was rejected by the SMF due to Operator Determined Barring.
#26 Insufficient resources is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources.
#27 Missing or unknown DNN
is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not
included although required or if the DNN could not be resolved.
#28 Unknown PDU session type
is used by the network to indicate that the requested service was rejected by the external DN because the requested PDU
session type could not be recognized or is not allowed.
#29 User authentication or authorization failed
is used by the network to indicate that the requested service was rejected by the external DN due to a failed user
authentication, revoked by the external DN, or rejected by 5GCN due to a failed user authentication or authorization.
#31 Request rejected, unspecified
is used by the network or by the UE to indicate that the requested service or operation or the request for a resource was
rejected due to unspecified reasons.
#32 Service option not supported is used by the network when the UE requests a service which is not supported by the PLMN.
#33 Requested service option not subscribed is sent when the UE requests a service option for which it has no subscription.
#35 PTI already in use
is used by the network to indicate that the PTI included by the UE is already in use by another active UE requested procedure
for this UE.
#36 Regular deactivation is used to indicate a regular UE or network initiated release of PDU session resources.
#37 5GS QoS not accepted is used by the network if the new 5GS QoS that was indicated in the UE request cannot be accepted.
#38 Network failure is used by the network to indicate that the requested service was rejected due to an error situation in the network.
cause number Cause value Description
#39 Reactivation requested is used by the network to request a PDU session reactivation.
#41 Semantic error in the TFT operation is used by the UE to indicate a semantic error in the TFT operation included in the request.
#42 Syntactical error in the TFT operation is used by the UE to indicate a syntactical error in the TFT operation included in the request.
#43 Invalid PDU session identity
is used by the network or the UE to indicate that the PDU session identity value provided to it is not a valid value or the PDU session
identified by the PDU session identity IE in the request or the command is not active.
#44 Semantic errors in packet filter(s)
is used by the network or the UE to indicate that the requested service was rejected due to one or more semantic errors in packet
filter(s) of the QoS rule included in the request.
#45 Syntactical error in packet filter(s)
is used by the network or the UE to indicate that the requested service was rejected due to one or more syntactical errors in packet
filter(s) of the QoS rule included in the request.
#46 Out of LADN service area is used by the network to indicate the UE is out of the LADN service area.
#47 PTI mismatch is used by the network or UE to indicate that the PTI provided to it does not match any PTI in use.
#50 PDU session type IPv4 only allowed is used by the network to indicate that only PDU session type IPv4 is allowed for the requested IP connectivity.
#51 PDU session type IPv6 only allowed is used by the network to indicate that only PDU session type IPv6 is allowed for the requested IP connectivity.
#54 PDU session does not exist
is used by the network at handover of a PDU session between non-3GPP access and 3GPP access, or at interworking of a PDN
connection from non-3GPP access network connected to EPC or from E-UTRAN connected to EPC to a PDU session, to indicate that the
network does not have any information about the requested PDU session.
#57 PDU session type IPv4v6 only allowed is used by the network to indicate that only PDU session types IPv4, IPv6 or IPv4v6 are allowed for the requested IP connectivity.
cause number Cause value Description
#58 PDU session type Unstructured only allowed is used by the network to indicate that only PDU session type Unstructured is allowed for the requested DN connectivity.
#59 Unsupported 5QI value is used by the network if the 5QI indicated in the UE request cannot be supported.
#61 PDU session type Ethernet only allowed is used by the network to indicate that only PDU session type Ethernet is allowed for the requested DN connectivity.
#67 Insufficient resources for specific slice and DNN is by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice and DNN.
#68 Not supported SSC mode is used by the network to indicate that the requested SSC mode is not supported.
#69 Insufficient resources for specific slice
is used by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice or
maximum number of PDU sessions on a specific slice has been already reached.
#70 Missing or unknown DNN in a slice
is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not included
although required or if the DNN could not be resolved, in the slice.
#81 Invalid PTI value is used by the network or UE to indicate that the PTI provided to it is invalid for the specific 5GSM message.
#82
Maximum data rate per UE for user-plane
integrity protection is too low
is used by the network to indicate that the requested service cannot be provided because the maximum data rate per UE for user-
plane integrity protection is too low.
#83 Semantic error in the QoS operation
is used by the network or the UE to indicate that the requested service was rejected due to a semantic error in the QoS operation
included in the request.
#84 Syntactical error in the QoS operation
is used by the network or the UE to indicate that the requested service was rejected due to a syntactical error in the QoS operation
included in the request.
#85 Invalid mapped EPS bearer identity
is used by the network or the UE to indicate that the mapped EPS bearer identity value provided to it is not a valid value or the
mapped EPS bearer identified by the mapped EPS bearer identity does not exist.
5G PDU Cause Code

More Related Content

What's hot

dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.pptdokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
LibaBali
 
Lte attach-messaging
Lte attach-messagingLte attach-messaging
Lte attach-messaging
Praveen Kumar
 
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
ObeidAllah
 

What's hot (20)

3 lte mac_rrc(조봉열)
3 lte mac_rrc(조봉열)3 lte mac_rrc(조봉열)
3 lte mac_rrc(조봉열)
 
Cs fallback feature
Cs fallback featureCs fallback feature
Cs fallback feature
 
5G NR parameters
5G NR parameters5G NR parameters
5G NR parameters
 
395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptx395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptx
 
Pci planning-for-lte
Pci planning-for-ltePci planning-for-lte
Pci planning-for-lte
 
5G NR MIB and SIBs
5G NR MIB and SIBs5G NR MIB and SIBs
5G NR MIB and SIBs
 
TDM Traffic Migration into IP Backhaul
TDM Traffic Migration into IP BackhaulTDM Traffic Migration into IP Backhaul
TDM Traffic Migration into IP Backhaul
 
Irat handover basics
Irat handover basicsIrat handover basics
Irat handover basics
 
dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.pptdokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
dokumen.tips_ericsson-lte-throughput-troubleshooting-techniquesppt.ppt
 
Initial LTE call Setup Flow
Initial LTE call Setup FlowInitial LTE call Setup Flow
Initial LTE call Setup Flow
 
Lte attach-messaging
Lte attach-messagingLte attach-messaging
Lte attach-messaging
 
LTE network: How it all comes together architecture technical poster
LTE network: How it all comes together architecture technical posterLTE network: How it all comes together architecture technical poster
LTE network: How it all comes together architecture technical poster
 
3GPP SON Series: Minimization of Drive Testing (MDT)
3GPP SON Series: Minimization of Drive Testing (MDT)3GPP SON Series: Minimization of Drive Testing (MDT)
3GPP SON Series: Minimization of Drive Testing (MDT)
 
3GPP LTE introduction 2(RRC)
3GPP LTE introduction  2(RRC)3GPP LTE introduction  2(RRC)
3GPP LTE introduction 2(RRC)
 
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
287995345-Huawei-WCDMA-Radio-Parameters-Optimization-Cases.pdf
 
3GPP LTE Detailed explanation 4 (X2 Handover)
3GPP LTE Detailed explanation 4 (X2 Handover)3GPP LTE Detailed explanation 4 (X2 Handover)
3GPP LTE Detailed explanation 4 (X2 Handover)
 
Lte ho parameters trial_01262011
Lte ho parameters trial_01262011Lte ho parameters trial_01262011
Lte ho parameters trial_01262011
 
LTE RACH Procedure
LTE RACH ProcedureLTE RACH Procedure
LTE RACH Procedure
 
Chap 2. lte channel structure .eng
Chap 2. lte  channel structure .engChap 2. lte  channel structure .eng
Chap 2. lte channel structure .eng
 
MPLS Traffic Engineering
MPLS Traffic EngineeringMPLS Traffic Engineering
MPLS Traffic Engineering
 

Similar to 5G PDU Cause Code

6421 b Module-05
6421 b Module-056421 b Module-05
6421 b Module-05
Bibekananada Jena
 
Session 5 Tp 5
Session 5 Tp 5Session 5 Tp 5
Session 5 Tp 5
githe26200
 
Ccnav5.org ccna 3-v50_practice_final_exam_2014
Ccnav5.org ccna 3-v50_practice_final_exam_2014Ccnav5.org ccna 3-v50_practice_final_exam_2014
Ccnav5.org ccna 3-v50_practice_final_exam_2014
Đồng Quốc Vương
 

Similar to 5G PDU Cause Code (8)

Advanced Dos Detection (Icghc2016)
 Advanced Dos Detection (Icghc2016) Advanced Dos Detection (Icghc2016)
Advanced Dos Detection (Icghc2016)
 
6421 b Module-05
6421 b Module-056421 b Module-05
6421 b Module-05
 
Configuring the Device as a PPPoE Client on Huawei AR1200
Configuring the Device as a PPPoE Client on Huawei AR1200Configuring the Device as a PPPoE Client on Huawei AR1200
Configuring the Device as a PPPoE Client on Huawei AR1200
 
Method and apparatus for classifying remote procedure call transport traffic
Method and apparatus for classifying remote procedure call transport trafficMethod and apparatus for classifying remote procedure call transport traffic
Method and apparatus for classifying remote procedure call transport traffic
 
Session 5 Tp 5
Session 5 Tp 5Session 5 Tp 5
Session 5 Tp 5
 
Ession 5 Tp 5
Ession 5 Tp 5Ession 5 Tp 5
Ession 5 Tp 5
 
Ession 5 Tp 5
Ession 5 Tp 5Ession 5 Tp 5
Ession 5 Tp 5
 
Ccnav5.org ccna 3-v50_practice_final_exam_2014
Ccnav5.org ccna 3-v50_practice_final_exam_2014Ccnav5.org ccna 3-v50_practice_final_exam_2014
Ccnav5.org ccna 3-v50_practice_final_exam_2014
 

Recently uploaded

Recently uploaded (20)

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
Ransomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdfRansomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdf
 
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data DiscoveryTrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
 
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
 
A Beginners Guide to Building a RAG App Using Open Source Milvus
A Beginners Guide to Building a RAG App Using Open Source MilvusA Beginners Guide to Building a RAG App Using Open Source Milvus
A Beginners Guide to Building a RAG App Using Open Source Milvus
 
Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot ModelNavi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : UncertaintyArtificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
 
Manulife - Insurer Transformation Award 2024
Manulife - Insurer Transformation Award 2024Manulife - Insurer Transformation Award 2024
Manulife - Insurer Transformation Award 2024
 
Real Time Object Detection Using Open CV
Real Time Object Detection Using Open CVReal Time Object Detection Using Open CV
Real Time Object Detection Using Open CV
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWEREMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
 
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
 
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
 
GenAI Risks & Security Meetup 01052024.pdf
GenAI Risks & Security Meetup 01052024.pdfGenAI Risks & Security Meetup 01052024.pdf
GenAI Risks & Security Meetup 01052024.pdf
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
 
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu SubbuApidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
Apidays Singapore 2024 - Modernizing Securities Finance by Madhu Subbu
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 

5G PDU Cause Code

  • 2. In next page, I mentioned Failure Cause codes and in coming pages, description for each cause code is explained. It can be used for Optimization , Maintenance , Monitoring and Troubleshooting.
  • 3. Cause Number Cause Value Cause Number Cause Value #8 Operator Determined Barring #46 Out of LADN service area #26 Insufficient resources #47 PTI mismatch #27 Missing or unknown DNN #50 PDU session type IPv4 only allowed #28 Unknown PDU session type #51 PDU session type IPv6 only allowed #29 User authentication or authorization failed #54 PDU session does not exist #31 Request rejected, unspecified #57 PDU session type IPv4v6 only allowed #32 Service option not supported #58 PDU session type Unstructured only allowed #33 Requested service option not subscribed #59 Unsupported 5QI value #35 PTI already in use #61 PDU session type Ethernet only allowed #36 Regular deactivation #67 Insufficient resources for specific slice and DNN #37 5GS QoS not accepted #68 Not supported SSC mode #38 Network failure #69 Insufficient resources for specific slice #39 Reactivation requested #70 Missing or unknown DNN in a slice #41 Semantic error in the TFT operation #81 Invalid PTI value #42 Syntactical error in the TFT operation #82 Maximum data rate per UE for user-plane integrity protection is too low #43 Invalid PDU session identity #83 Semantic error in the QoS operation #44 Semantic errors in packet filter(s) #84 Syntactical error in the QoS operation #45 Syntactical error in packet filter(s) #85 Invalid mapped EPS bearer identity
  • 4. cause number Cause value Description #8 Operator Determined Barring is used by the network to indicate that the requested service was rejected by the SMF due to Operator Determined Barring. #26 Insufficient resources is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources. #27 Missing or unknown DNN is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not included although required or if the DNN could not be resolved. #28 Unknown PDU session type is used by the network to indicate that the requested service was rejected by the external DN because the requested PDU session type could not be recognized or is not allowed. #29 User authentication or authorization failed is used by the network to indicate that the requested service was rejected by the external DN due to a failed user authentication, revoked by the external DN, or rejected by 5GCN due to a failed user authentication or authorization. #31 Request rejected, unspecified is used by the network or by the UE to indicate that the requested service or operation or the request for a resource was rejected due to unspecified reasons. #32 Service option not supported is used by the network when the UE requests a service which is not supported by the PLMN. #33 Requested service option not subscribed is sent when the UE requests a service option for which it has no subscription. #35 PTI already in use is used by the network to indicate that the PTI included by the UE is already in use by another active UE requested procedure for this UE. #36 Regular deactivation is used to indicate a regular UE or network initiated release of PDU session resources. #37 5GS QoS not accepted is used by the network if the new 5GS QoS that was indicated in the UE request cannot be accepted. #38 Network failure is used by the network to indicate that the requested service was rejected due to an error situation in the network.
  • 5. cause number Cause value Description #39 Reactivation requested is used by the network to request a PDU session reactivation. #41 Semantic error in the TFT operation is used by the UE to indicate a semantic error in the TFT operation included in the request. #42 Syntactical error in the TFT operation is used by the UE to indicate a syntactical error in the TFT operation included in the request. #43 Invalid PDU session identity is used by the network or the UE to indicate that the PDU session identity value provided to it is not a valid value or the PDU session identified by the PDU session identity IE in the request or the command is not active. #44 Semantic errors in packet filter(s) is used by the network or the UE to indicate that the requested service was rejected due to one or more semantic errors in packet filter(s) of the QoS rule included in the request. #45 Syntactical error in packet filter(s) is used by the network or the UE to indicate that the requested service was rejected due to one or more syntactical errors in packet filter(s) of the QoS rule included in the request. #46 Out of LADN service area is used by the network to indicate the UE is out of the LADN service area. #47 PTI mismatch is used by the network or UE to indicate that the PTI provided to it does not match any PTI in use. #50 PDU session type IPv4 only allowed is used by the network to indicate that only PDU session type IPv4 is allowed for the requested IP connectivity. #51 PDU session type IPv6 only allowed is used by the network to indicate that only PDU session type IPv6 is allowed for the requested IP connectivity. #54 PDU session does not exist is used by the network at handover of a PDU session between non-3GPP access and 3GPP access, or at interworking of a PDN connection from non-3GPP access network connected to EPC or from E-UTRAN connected to EPC to a PDU session, to indicate that the network does not have any information about the requested PDU session. #57 PDU session type IPv4v6 only allowed is used by the network to indicate that only PDU session types IPv4, IPv6 or IPv4v6 are allowed for the requested IP connectivity.
  • 6. cause number Cause value Description #58 PDU session type Unstructured only allowed is used by the network to indicate that only PDU session type Unstructured is allowed for the requested DN connectivity. #59 Unsupported 5QI value is used by the network if the 5QI indicated in the UE request cannot be supported. #61 PDU session type Ethernet only allowed is used by the network to indicate that only PDU session type Ethernet is allowed for the requested DN connectivity. #67 Insufficient resources for specific slice and DNN is by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice and DNN. #68 Not supported SSC mode is used by the network to indicate that the requested SSC mode is not supported. #69 Insufficient resources for specific slice is used by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice or maximum number of PDU sessions on a specific slice has been already reached. #70 Missing or unknown DNN in a slice is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not included although required or if the DNN could not be resolved, in the slice. #81 Invalid PTI value is used by the network or UE to indicate that the PTI provided to it is invalid for the specific 5GSM message. #82 Maximum data rate per UE for user-plane integrity protection is too low is used by the network to indicate that the requested service cannot be provided because the maximum data rate per UE for user- plane integrity protection is too low. #83 Semantic error in the QoS operation is used by the network or the UE to indicate that the requested service was rejected due to a semantic error in the QoS operation included in the request. #84 Syntactical error in the QoS operation is used by the network or the UE to indicate that the requested service was rejected due to a syntactical error in the QoS operation included in the request. #85 Invalid mapped EPS bearer identity is used by the network or the UE to indicate that the mapped EPS bearer identity value provided to it is not a valid value or the mapped EPS bearer identified by the mapped EPS bearer identity does not exist.