7.7.1 Cause
29.0603GPPGeneral Packet Radio Service (GPRS)GPRS Tunnelling Protocol (GTP) across the Gn and Gp interfaceRelease 17TS
In a request, the Cause Value indicates the reason for the request. The Cause shall be included in the request message.
In a response, the Cause Value indicates the acceptance or the rejection of the corresponding request. In addition, the Cause Value may indicate what was the reason for the corresponding request. The Cause value shall be included in the response message.
Cause values are shared with the GTP’ protocol specified in 3GPP TS 32.295 [33].
The listed cause values for rejection response message descriptions in clauses 7.2, 7.3, 7.4, 7.5, 7.5A and 7.5B are not meant to be an exhaustive list. Therefore a GTPv1 node shall use the most appropriate matching rejection response cause value that is listed in Table 38.
"Request accepted" is returned when a GSN has accepted a control plane request.
"Non-existent" indicates a non-existent or an inactive PDP context.
"New PDP type due to network preference" indicates that the MS has requested PDP type IPv4v6 and only IPv4 or IPv6 address is allowed for the PDN based on GGSN operator policy, as specified in clause 9.2.1 in 3GPP TS 23.060 [4].
"New PDP type due to single address bearer only" indicates that the MS has requested PDP type IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Common Flags IE is set to 0 or the Common Flags IE is absent, or only single IP version addressing is possible in the PDN, as specified in clause 9.2.1 in 3GPP TS 23.060 [4].
"IMSI/IMEI not known" indicates a non-existent MM context.
"MS is GPRS Detached" indicates an idle MM context.
"MS is not GPRS Responding" and "MS Refuses" may be used by SGSN to reject a Network-Requested PDP Context Activation.
"Version not supported" is returned when the recipient does not recognise the version number in the request message.
"Request IMSI", "Request IMEI", "Request IMSI and IMEI" and "No identity needed" are used by GGSN to notify SGSN what to do.
"No resources available" is a generic temporary error condition indicating that some kind of resource is used up for that moment excluding the conditions all dynamic PDP addresses are occupied and no memory is available.
"All dynamic PDP addresses occupied" indicates that the GSN does not have a free dynamic PDP address to allocate any longer.
"No memory available" indicates that the GSN does not have enough memory to use.
"Service not supported" is a generic error indicated that the GSN do not support the requested service.
"User authentication failed" indicates that the external packet network has rejected the user’s service request. The use of the cause code is defined in 3GPP TS 24.008 [5].
"System failure" is a generic permanent error condition.
"Roaming restriction" indicates that the SGSN cannot activate the requested PDP context because of the roaming restrictions.
"P-TMSI Signature mismatch" is returned if either:
– the P-TMSI Signature stored in the old SGSN does not match the value sent by the MS via the new SGSN; or
– the MS does not provide the P-TMSI Signature to the new SGSN while the old SGSN has stored the P-TMSI Signature for that MS.
"Semantic error in the TFT operation", "Syntactic error in the TFT operation", "Semantic errors in packet filter(s)" and "Syntactic errors in packet filters(s)" and "PDP context without TFT already activated" are indications of abnormal cases involving TFTs. The abnormal TFT cases and the use of the cause codes are defined in 3GPP TS 24.008 [5].
"Invalid message format", "Mandatory IE incorrect", "Mandatory IE missing" and "Optional IE incorrect" are indications of protocol errors described in the clause Error handling.
"GPRS connection suspended" indicates that the GPRS activities of the mobile station are suspended.
"Authentication failure" indicates that the user authentication failed in the new SGSN.
"Context not found" indicates that the PDP Context referenced in an Active Secondary Context Request message was not found in the receiving GGSN.
"Relocation failure" indicates that the SRNS relocation failed in the new SGSN side.
"Relocation failure due to NAS message redirection" is used by the new SGSN to indicate to the old SGSN that the RAU procedure is not successful due to NAS message redirection as described in 3GPP TS 23.060 [4].
"Unknown mandatory extension header" signals in a response message that the corresponding request included an extension header for which comprehension was required but unknown to the receiving end.
"APN Restriction type incompatibility with currently active PDP Contexts" conveys to an SGSN that a PDP Context was not allowed to be created or moved by the GGSN because if it had been created or moved, the rules for PDP Context coexistence as described in 3GPP TS 23.060 [4], clause 15.4, would have been broken.
"MS MBMS Capabilities Insufficient" is used by the SGSN to notify the GGSN that the MS MBMS Bearer Capabilities are less than the Required MBMS Bearer Capabilities.
"MBMS Bearer Context Superseded" indicates that the SGSN has already established an MBMS bearer plane with another GGSN.
"Invalid Correlation-ID" indicates that the Correlation-ID was already in use in the SGSN.
"Bearer Control Mode violation" indicates that a request is violating the current Bearer Control Mode.
"Collision with network initiated request" indicates that the UE-initiated request was rejected since the network has requested a secondary PDP context activation for the same service using a network-initiated procedure.
"APN Congestion" indicates that the GGSN has detected congestion for the requested APN and performs overload control for that APN which does not allow the PDP Context to be created.
"Bearer handling not supported" indicates that the request was rejected because the respective procedure (MS initiated Secondary PDP Context Activation procedure or the PDP Context Modification procedure), which is related to an established PDP context for LIPA or for SIPTO at the local network, is not supported.
"PDP address inactivity timer expires" is used by the GGSN in Delete PDP Context Request(s) to indicate that all the PDP context(s) that share the same emergency PDP address are deleted upon the inactivity timer expiry as specified in 3GPP TS 23.203 [39].
"Reactivation Requested" is used by the GGSN while tearing down all the PDP Context(s) associated with same PDN connection. It indicates that the GGSN is requesting UE to re-initiate the PDP Context Activation procedure for the corresponding APN.
"Network failure" is used by the SGSN in the Delete PDP Context Request to indicate that the message is sent due to a network problem.
"QoS parameter mismatch" is used by the SGSN in the Delete PDP Context Request to indicate that the PDP can not be established due to a QoS parameter mismatch.
"Target access restricted for the subscriber" is used by the MME/SGSN in the Context Response message to indicate that the target access is prohibited for the subscriber, based on the subscription profile.
"UE is temporarily not reachable due to power saving" is used by the SGSN in the Initiate PDP Context Activation Response and Update PDP Context Response message to reject the corresponding network initiated procedures for a Delay Tolerant PDN connection and to request the GGSN to hold the network initiated procedure until it receives the subsequent Update PDP Context Request message with the UASI flag indicating that the UE is available for end to end signalling.
Figure 9: Cause information element
Table 38: Cause Values
|
Cause |
Value (Decimal) |
|||
|---|---|---|---|---|
|
Request IMSI |
0 |
|||
|
Request IMEI |
1 |
|||
|
request |
Request IMSI and IMEI |
2 |
||
|
No identity needed |
3 |
|||
|
MS Refuses |
4 |
|||
|
MS is not GPRS Responding |
5 |
|||
|
Reactivation Requested |
6 |
|||
|
PDP address inactivity timer expires |
7 |
|||
|
Network Failure |
8 |
|||
|
QoS parameter mismatch |
9 |
|||
|
For future use |
10-48 |
|||
|
Cause values reserved for GPRS charging protocol use (see GTP’ in 3GPP TS 32.295 [33]) |
49-63 |
|||
|
For future use |
64-127 |
|||
|
acc |
Request accepted |
128 |
||
|
New PDP type due to network preference |
129 |
|||
|
New PDP type due to single address bearer only |
130 |
|||
|
For future use |
131-176 |
|||
|
Cause values reserved for GPRS charging protocol use (see GTP’ in 3GPP TS 32.295 [33]) |
177-191 |
|||
|
Non-existent |
192 |
|||
|
Invalid message format |
193 |
|||
|
response |
rej |
IMSI/IMEI not known |
194 |
|
|
MS is GPRS Detached |
195 |
|||
|
MS is not GPRS Responding |
196 |
|||
|
MS Refuses |
197 |
|||
|
Version not supported |
198 |
|||
|
No resources available |
199 |
|||
|
Service not supported |
200 |
|||
|
Mandatory IE incorrect |
201 |
|||
|
Mandatory IE missing |
202 |
|||
|
Optional IE incorrect |
203 |
|||
|
System failure |
204 |
|||
|
Roaming restriction |
205 |
|||
|
P-TMSI Signature mismatch |
206 |
|||
|
GPRS connection suspended |
207 |
|||
|
Authentication failure |
208 |
|||
|
User authentication failed |
209 |
|||
|
Context not found |
210 |
|||
|
All dynamic PDP addresses are occupied |
211 |
|||
|
No memory is available |
212 |
|||
|
Relocation failure |
213 |
|||
|
Unknown mandatory extension header |
214 |
|||
|
Semantic error in the TFT operation |
215 |
|||
|
Syntactic error in the TFT operation |
216 |
|||
|
Semantic errors in packet filter(s) |
217 |
|||
|
Syntactic errors in packet filter(s) |
218 |
|||
|
Missing or unknown APN |
219 |
|||
|
Unknown PDP address or PDP type |
220 |
|||
|
PDP context without TFT already activated |
221 |
|||
|
APN access denied – no subscription |
222 |
|||
|
APN Restriction type incompatibility with currently active PDP Contexts |
223 |
|||
|
MS MBMS Capabilities Insufficient |
224 |
|||
|
Invalid Correlation-ID |
225 |
|||
|
MBMS Bearer Context Superseded |
226 |
|||
|
Bearer Control Mode violation |
227 |
|||
|
Collision with network initiated request |
228 |
|||
|
APN Congestion |
229 |
|||
|
Bearer handling not supported |
230 |
|||
|
"Target access restricted for the subscriber" |
231 |
|||
|
UE is temporarily not reachable due to power saving |
232 |
|||
|
Relocation failure due to NAS message redirection |
233 |
|||
|
For future use |
234-240 |
|||
|
Cause values reserved for GPRS charging protocol use (see GTP’ in 3GPP TS 32.295 [33]) |
241-255 |
|||
|
NOTE: With this coding, bits 8 and 7 of the Cause Value respectively indicate whether the message was a request or a response, and whether the request was accepted or rejected. |
||||
Table 39: Use of the Cause Values
|
Cause 8 |
value bits 7 |
Result |
|
0 |
0 |
Request |
|
0 |
1 |
For future use (note) |
|
1 |
0 |
Acceptance |
|
1 |
1 |
Rejection |
|
NOTE: The value "01" is for future use and shall not be sent. If received in a response, it shall be treated as a rejection. |
||