The MME/S4-SGSN initiates session
management requests towards the SGW and PGW or mobility management requests
towards the source/target MME/S4-SGSN. If this operation is not successful,
there are several possible cause codes, which need to be mapped to the
appropriate cause codes over NAS to the UE.
Additionally, the MME/S4-SGSN initiates
session management requests towards the UE. If this operation is not
successful, there are several possible NAS cause codes which need to be mapped
to the appropriate GTP cause codes over S11/S4 interface towards the SGW.
The MME/S4-SGSN should map these cause
codes as defined in tables C.1 to C.5 unless specified otherwise in the tables.
Table C.1: Mapping from S11/S4 to NAS Cause values – Rejection indication from SGW
| Reject indication from SGW to MME/S4-SGSN over S11/S4 | NAS ESM Cause to UE (NOTE 1, NOTE 2, NOTE 3) | SM Cause to UE (NOTE 1, NOTE 2, NOTE 3) |
| #64 ""Context not found"" (during UE initiated PDN connectivity request for non-3GPP to 3GPP handover procedure) | #54 ""PDN connection does not exist"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #31 ""Activation rejected, unspecified"" |
| #64 ""Context not found"" (during all other procedures) | #30 ""Request rejected by Serving GW or PDN GW""#38 ""Network failure"" #43 ""Invalid EPS bearer identity"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" #43 ""Unknown PDP Context"" |
| #65 Invalid Message Format | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #66 ""Version not supported by next peer"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #67 ""Invalid length"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #68 "Service not supported" | #32 "Service option not supported" | #32 "Service option not supported" |
| #69 ""Mandatory IE incorrect"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #70 ""Mandatory IE missing"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #72 ""System Failure"" | #34 ""Service option temporarily out of order"" #38 ""Network Failure"" #30 ""Request rejected by Serving GW or PDN GW"" | #34 ""Service option temporarily out of order"" #38 ""Network failure"" #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" |
| #73 ""No Resources available"" | #34 ""Service option temporarily out of order"" #26 ""Insufficient resources"" | #34 ""Service option temporarily out of order"" #26 ""Insufficient resources"" |
| #76 "Semantic errors in packet filter(s)" | #44 "Semantic errors in packet filter(s)" | #44 "Semantic errors in packet filter(s)" |
| #77 "Syntactic errors in packet filter(s)" | #45 "Syntactical error in packet filter(s)" | #45 "Syntactical error in packet filter(s)" |
| #78 "Missing or unknown APN" | # 27 "Missing or unknown APN" | # 27 "Missing or unknown APN" |
| #80 ""GRE key not found"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network Failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #83 ""Preferred PDN type not supported"" | #32 ""Service option not supported"" #50 ""PDN type IPv4 only allowed"" #51 ""PDN type IPv6 only allowed"" | #32 ""Service option not supported"" #50 ""PDP type IPv4 only allowed"" #51 ""PDP type IPv6 only allowed"" |
| #84 "All dynamic addresses are occupied" | #26 "Insufficient resources" | #26 "Insufficient resources" |
| #85 "UE context without TFT already activated" | NA | #46 "PDP context without TFT already activated" |
| #86 ""Protocol type not supported"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network Failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #89 ""Service denied"" | #30 ""Request rejected by Serving GW or PDN GW"" #31 ""Request rejected, unspecified"" #38 ""Network failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #31 ""Activation rejected, unspecified"" #38 ""Network failure"" |
| #91 ""No memory available"" | #34 ""Service option temporarily out of order"" #26 ""Insufficient resources"" | #34 ""Service option temporarily out of order"" #26 ""Insufficient resources"" |
| #92 ""User authentication failed"" | #29 ""User authentication failed"" NOTE | #29 ""User authentication failed"" |
| #93 ""APN access denied – no subscription"" | #33 ""Requested service option not subscribed"" # 27 ""Missing or unknown APN"" | #33 ""Requested service option not subscribed"" # 27 ""Missing or unknown APN"" |
| #94 ""Request rejected (reason not specified)"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network Failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #97 "Semantic error in the TAD operation" | #41 "Semantic error in the TFT operation" | #41 "Semantic error in the TFT operation" |
| #98 "Syntactic error in the TAD operation" | #42 "Syntactical error in the TFT operation" | #42 "Syntactical error in the TFT operation" |
| #100 ""Remote peer not responding"" | #34 ""Service option temporarily out of order"" #38 ""Network Failure"" | #34 ""Service option temporarily out of order"" #38 ""Network failure"" |
| #101 "Collision with network initiated request" | #56 "Collision with network initiated request" | #56 "Collision with network initiated request" |
| #103 ""Conditional IE missing"" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network Failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #104 "APN Restriction type Incompatible with currently active PDN connection" | #112 "APN restriction value incompatible with active EPS bearer context" | #112 "APN restriction value incompatible with active PDP context" |
| #107 ""Invalid reply from remote peer"" | #30 ""Request rejected by Serving GW or PDN GW"" #31 ""Request rejected, unspecified"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #31 ""Activation rejected, unspecified"" |
| #112 ""Request rejected for a PMIPv6 reason (see 3GPP TS 29.275 [26])."" | #30 ""Request rejected by Serving GW or PDN GW"" #38 ""Network Failure"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #38 ""Network failure"" |
| #113 ""APN Congestion"" #120 ""GTP-C Entity Congestion"" | #26 ""Insufficient resources"" | #26 ""Insufficient resources"" |
| #114 "Bearer handling not supported" | #60 "Bearer handling not supported" | #60 "Bearer handling not supported" |
| #116 ""Multiple PDN connections for a given APN not allowed"" | #55 ""Multiple PDN connections for a given APN not allowed"" | #30 ""Activation rejected by GGSN, Serving GW or PDN GW"" #31 ""Activation rejected, unspecified"" |
| #126 "Multiple accesses to a PDN connection not allowed" | #113 "Multiple accesses to a PDN connection not allowed" | #113 "Multiple accesses to a PDN connection not allowed" |
- NOTE 1: See 3GPP TS 24.301 [23] and 3GPP TS 24.008 [5] for NAS ESM and SM causes respectively.
- NOTE 2: The MME/S4-SGSN may for certain GTP cause codes trigger a new GTP procedure instead of rejecting the NAS request.
- NOTE 3:When multiple NAS Cause values are defined for a given GTP cause value, any of those NAS Cause values may be sent to the UE based on implementation choice.
- NOTE 4: The MME may send in addition the EMM cause code set to #15 "No suitable cells in tracking area" to the UE, if the PDN connectivity request is rejected due to the ESM cause #29, which is mapped from the GTPv2 cause code #92 based on operator policies. See 3GPP TS 24.301 [23]. This enables a roamer to get service in a VPLMN even when being rejected via LTE access due to e.g. no credit authorisation from the OCS.
Table C.2: Mapping from S11/S4 to NAS Cause values – Acceptance indication from SGW
| Acceptance indication from SGW to MME/S4-SGN over S11/S4 | NAS ESM Cause to UE | SM Cause to UE |
| #18 ""New PDN type due to network preference"" | #50 ""PDN type IPv4 only allowed"" #51 ""PDN type IPv6 only allowed"" (NOTE 1) | #50 ""PDP type IPv4 only allowed"" #51 ""PDP type IPv6 only allowed"" (NOTE 1) |
| #19 "New PDN type due to single address bearer only" | #52 "single address bearers only allowed" | #52 "single address bearers only allowed" |
- NOTE 1: The actual NAS cause sent to the UE depends on the allocated IP address type.
Table C.3: Mapping from S11/S4 to NAS Cause values – Indication in request from SGW
| Indication in a request / initial message from SGW to MME/S4-SGSN over S11/S4 | NAS ESM Cause to UE | SM Cause to UE |
| #8 ""Reactivation Requested"" (NOTE 1) | Shall be mapped to: #39 ""Reactivation requested"" in the NAS bearer context deactivation procedure. For the last PDN connection in E-UTRAN, ""Reactivation requested"" shall be mapped to ""re-attach required"" in the NAS detach type IE. | Shall be mapped to: #39 ""Reactivation requested"" in the NAS bearer context deactivation procedure. |
| #9 ""PDN reconnection to this APN disallowed"" (NOTE 1) | Implementation specific NAS cause value indicating to the UE that the APN is not currently available. For the last PDN connection, NAS detach type IE should be set to ""re-attach not required"". | Implementation specific NAS cause value indicating to the UE that the APN is not currently available. |
- NOTE 1: In Delete Bearer Request during the PGW initiated bearer deactivation procedure for the default bearer.
Table C.4: Mapping from NAS to S11/S4 Cause values – Rejection indication from MME/S4-SGSN
| NAS ESM Cause from UE (NOTE 1) | SM Cause from UE (NOTE 1) | Reject indication from MME/S4-SGSN to SGW over S11/S4 (NOTE 2) |
| #26 ""Insufficient Resources"" | #26 ""Insufficient Resources"" | #73 ""No Resources available"" #88 ""UE refuses"" |
| #31 ""Request rejected, unspecified"" | #31 ""Activation rejected, unspecified"" | #94 ""Request rejected"" #88 ""UE refuses"" |
| #41 "Semantic error in the TFT operation" | #41 "Semantic error in the TFT operation" | #74 "Semantic error in the TFT operation" |
| #42 "Syntactical error in the TFT operation" | #42 "Syntactical error in the TFT operation" | #75 "Syntactical error in the TFT operation" |
| #43 ""Invalid EPS bearer identity"" | #43 ""Unknown PDP Context"" | #64 ""Context not found"" #88 ""UE refuses"" |
| #44 "Semantic errors in packet filter(s)" | #44 "Semantic errors in packet filter(s)" | #76 "Semantic errors in packet filter(s)" |
| #45 "Syntactical error in packet filter(s)" | #45 "Syntactical error in packet filter(s)" | #77 "Syntactical error in packet filter(s)" |
| #47 ""PTI mismatch"" | NA | #94 ""Request rejected"" #88 ""UE refuses"" |
| NA | #48 ""Request rejected, Bearer Control Mode violation"" | #94 ""Request rejected"" #88 ""UE refuses"" |
| #81 ""Invalid PTI value"" | NA | #94 ""Request rejected"" #88 ""UE refuses"" |
- NOTE 1: See 3GPP TS 24.301 [23] and 3GPP TS 24.008 [5] for NAS ESM and SM causes respectively.
- NOTE 2: When multiple GTPv2 Cause values are defined for a given NAS Cause value, any of those GTPv2 Cause values may be sent to the SGW based on implementation choice.
Table C.5: Mapping from S3/S16 to NAS Cause values
– Rejection indication from MME/S4-SGSN
| Reject indication from MME/S4-SGSN to MME/S4-SGSN over S3/S16 | NAS ESM Cause to UE (NOTE 1, NOTE 2) | SM Cause to UE (NOTE 1, NOTE 2) |
| #117 ""Target access restricted for the subscriber"" | #15 ""No suitable cells in tracking area"", or #13 ""Roaming not allowed in this tracking area"", or #12 ""Tracking area not allowed"" | #15 ""No suitable cells in tracking area"", or #13 ""Roaming not allowed in this tracking area"", or #12 ""Tracking area not allowed"" |
- NOTE 1: See 3GPP TS 24.301 [23] and 3GPP TS 24.008 [5] for NAS ESM and SM causes respectively.
- NOTE 2: When multiple NAS Cause values are defined for a given GTP cause value, any of those NAS Cause values may be sent to the UE based on implementation choice.
Reference:
3GPP TS 29.274 V17.3.0 (2021-09)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
3GPP Evolved Packet System (EPS);
Evolved General Packet Radio Service (GPRS)
Tunnelling Protocol for Control plane (GTPv2-C);
Stage 3;
(Release 17)
No comments:
Post a Comment