GPRS Session Management Cause Codes

Cause code berikut ada saat prosess Session Management (SM) antara MS/UE dengan SGSN. SM terjadi saat prosedur PDP context activation dan PDP context deactivation.

 SM berada di layer paling atas control plane untuk Gb dan Iu, seperti gambar berikut:

Control Plane MS - SGSN in A/Gb mode

Control Plane MS - SGSN in Iu mode

Berikut tabel cause code value untuk Session Management

Cause value	Cause	Description
	Causes related to nature of request
8	Operator Determined Barring	This cause code is used by the network to indicate that the requested service was rejected by the SGSN due to Operator Determined Barring.
24	MBMS bearer capabilities insufficient for the service	This cause code is used by the network to indicate that an MBMS context activation request was rejected by the network, because the MBMS bearer capabilities are insufficient for the MBMS service.
25	LLC or SNDCP failure (A/Gb mode only)	This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause "DM received " or " invalid XID response ", see 3GPP TS 44.065 [78])
26	Insufficient resources	This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request, PDP context modification request, or MBMS context activation request cannot be accepted due to insufficient resources.
27	Missing or unknown APN	This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required, or if the access point name could not be resolved.
28	Unknown PDP address or PDP type	This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised.
29	User authentication failed	This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.
30	Activation rejected by GGSN, Serving GW or PDN GW	This cause code is used by the network to indicate that the requested service was rejected by the GGSN, Serving GW or PDN GW.
31	Activation rejected, unspecified	This cause code is used by the network or by the MS to indicate that the requested service was rejected due to unspecified reasons.
32	Service option not supported	This cause code is used by the network when the MS requests a service which is not supported by the PLMN.
33	Requested service option not subscribed	This cause is sent when the MS requests a service option for which it has no subscription.
34	Service option temporarily out of order	This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service.
35	NSAPI already used	This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS.Never to be sent, but can be received from a R97/R98 network at PDP context activation
36	Regular deactivation	This cause code is used to indicate a regular MS or network initiated PDP context deactivation or a regular network initiated MBMS context deactivation.
37	QoS not accepted	This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the PDP Context Modification procedure.
38	Network failure	This cause code is used by the network to indicate that the requested service is rejected due to an error situation in the network.
39	Reactivation requested	This cause code is used by the network to request a PDP context reactivation (e.g. after a GGSN restart or after selection of a different GGSN by the network for Selected IP Traffic Offload).
40	Feature not supported	This cause code is used by the MS to indicate that the PDP context activation or the MBMS context activation initiated by the network is not supported by the MS.
41	semantic error in the TFT operation.	This cause code is used by the network or the MS to indicate that there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.
42	syntactical error in the TFT operation.	This cause code is used by the network or the MS to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.
43	unknown PDP context	This cause code is used by the network or the MS to indicate that the PDP context identified by the Linked TI IE in the secondary PDP context activation request or a network requested secondary PDP context activation is not active.
44	semantic errors in packet filter(s)	This cause code is used by the network or the MS to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.
45	syntactical error in packet filter(s)	This cause code is used by the network or the MS to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.
46	PDP context without TFT already activated	This cause code is used by the network or the MS to indicate that it has already activated a PDP context without TFT.
47	Multicast group membership time-out	This cause code is used by the network to indicate that the MBMS context is deactivated because the timer supervising the IGMP group membership interval (see RFC 3376 [107], subclause 8.4) or the MLD multicast listener interval (see RFC 2710 [108], subclause 7.4, and RFC 3810 [148], subclause 9.4) expired.
48	Request rejected, Bearer Control Mode violation	This cause code is used by the network or the MS to indicate that the requested service was rejected because of Bearer Control Mode violation.
50	PDP type IPv4 only allowed	This cause code is used by the network to indicate that only PDP type IPv4 is allowed for the requested PDN connectivity.
51	PDP type IPv6 only allowed	This cause code is used by the network to indicate that only PDP type IPv6 is allowed for the requested PDN connectivity.
52	single address bearers only allowed	This cause code is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed.
56	Collision with network initiated request.	This cause code is used by the network to indicate that the MS-initiated request was rejected since the network has requested a secondary PDP context activation for the same service using a network-initiated procedure.
60	Bearer handling not supported	This cause code is used by the network to indicate that the procedure requested by the MS was rejected because the bearer handling is not supported.
65	Maximum number of PDP contexts reached	This cause code is used by the network to indicate that the procedure requested by the MS was rejected as the network has reached the maximum number of simultaneously active PDP contexts for the MS.
66	Requested APN not supported in current RAT and PLMN combination	This cause code is used by the network to indicate that the procedure requested by the MS was rejected because the requested APN is not supported in the current RAT and PLMN.
112	APN restriction value incompatible with active PDP context.	This cause code is used by the network to indicate that the PDP context(s) or MBMS context(s) have an APN restriction value that is not allowed in combination with a currently active PDP context. Restriction values are defined in 3GPP TS 23.060 [74], subclause 15.4.
113	Multiple accesses to a PDN connection not allowed	This ESM cause is used by the network to indicate that multiple accesses to a PDN connection for NBIFOM is not allowed.
	Causes related to invalid messages
81	Invalid transaction identifier value.	This cause indicates that the equipment sending this cause has received a message with a transaction identifier which is not currently in use on the MS-network interface.
95	Semantically incorrect message.	This cause is used to report receipt of a message with semantically incorrect contents
96	Invalid mandatory information.	This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error
97	Message type non-existent or not implemented.	This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.
98	Message not compatible with protocol state.	This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state
99	Information element non-existent or not implemented.	This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.
100	Conditional IE error.	This cause indicates that the equipment sending this cause has received a message with conditional IE errors
101	Message not compatible with protocol state.	This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.
111	Protocol error, unspecified.	This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

Berikut beberapa contoh capture message saat proses Session Management:

1. Contoh session management saat deactivate PDP context request dengan cause value 36
2. Contoh session management saat Activate PDP context reject dengan cause value 38

Sumber: 

1. 3GPP TS 24.008 V14.0.0 (2016-06)
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface Layer 3 specification;
Core network protocols; Stage 3
(Release 14)

2. 3GPP TS 23.060 V12.5.0 (2014-06)
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS);
Service description;
Stage 2
(Release 12)