7.2.6 Bearer Resource Failure Indication
29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS
A Bearer Resource Failure Indication shall be sent by the PGW to an SGW and forwarded to the MME to indicate failure of the UE requested bearer resource allocation procedure or UE requested bearer resource modification procedure, as specified by 3GPP TS 24.301 [23].
The message shall also be sent by a PGW to an SGW and forwarded to an SGSN as part of the failure of an MS initiated PDP Context modification procedure or secondary PDP context activation procedure.
The message shall also be sent on the S5/S8 or S2a/S2b interface by a PGW to a SGW or to a TWAN/ePDG and the S11/S4 interface by a SGW to an MME/S4-SGSN as part of the UE-initiated IP flow mobility procedure and the UE requested IP flow mapping procedure, as specified by 3GPP TS 23.161 [71].
Table 7.2.6-1 specifies the presence of the IEs in the message.
Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
– "Semantic error in the TAD operation".
– "Syntactic error in the TAD operation".
– "Semantic errors in packet filter(s)".
– "Syntactic errors in packet filter(s)".
– "Collision with network initiated request".
– "Service denied".
– "Bearer handling not supported".
– "UE context without TFT already activated".
Table 7.2.6-1: Information Elements in a Bearer Resource Failure Indication
Information elements |
P |
Condition / Comment |
IE Type |
Ins. |
Cause |
M |
Cause |
0 |
|
Linked EPS Bearer ID |
M |
See clause 6.1.1 "Presence requirements of Information Elements". |
EBI |
0 |
Procedure Transaction ID (PTI) |
M |
See clause 6.1.1 "Presence requirements of Information Elements". |
PTI |
0 |
Indication Flags |
CO |
This IE shall be included if any one of the applicable flags is set to 1. Applicable flags are:
|
Indication |
0 |
PGW’s Overload Control Information |
O |
During an overload condition, the PGW may include this IE on the S5/S8, if the overload control feature is supported by the PGW and is activated for the PLMN to which the access network node, i.e. MME/S4-SGSN for 3GPP access based network, belongs (see clause 12.3.11). When present, the PGW shall provide
See NOTE 1, NOTE 2. |
Overload Control Information |
0 |
CO |
If the SGW receives this IE and if it supports the overload control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface. |
|||
SGW’s Overload Control Information |
O |
During an overload condition, the SGW may include this IE over the S11/S4 interface if the overload control feature is supported by the SGW and is activated in the network (see clause 12.3.11). When present, the SGW shall provide only one instance of this IE, representing its overload information. |
Overload Control Information |
1 |
Recovery |
O |
Recovery |
0 |
|
NBIFOM Container |
CO |
This IE shall be included on the S5/S8 or S2a/S2b interfaces if the PGW needs to send NBIFOM information as specified in 3GPP TS 23.161 [71]. The Container Type shall be set to 4. |
F-Container |
0 |
CO |
If the SGW receives an NBIFOM Container IE from the PGW, the SGW shall forward it to the MME/S4-SGSN on the S11/S4 interface. |
|||
Private Extension |
O |
Private Extension |
VS |
|
NOTE 1: The receiver, supporting the APN level overload information for the maximum of 10 APNs, shall handle the APN level overload information for the first 10 APNs and ignore any more APN level overload information. NOTE 2: The APN level overload information, provided within and across different instances of the "PGW’s Overload Control Information" IE(s) shall be limited to 10 different APNs. |
Table 7.2.6-2: Overload Control Information within Bearer Resource Failure Indication
Octet 1 |
Overload Control Information IE Type = 180 (decimal) |
|||
Octets 2 and 3 |
Length = n |
|||
Octet 4 |
Spare and Instance fields |
|||
Information elements |
P |
Condition / Comment |
IE Type |
Ins. |
Overload Control Sequence Number |
M |
See clause 12.3.5.1.2.1 for the description and use of this parameter. |
Sequence Number |
0 |
Overload Reduction Metric |
M |
See clauses 12.3.5.1.2.3 and 12.3.5.1.2.4 for the description and use of this parameter. |
Metric |
0 |
Period of Validity |
M |
See clause 12.3.5.1.2.2 for the description and use of this parameter. This IE should be set to "0" if the "Overload Reduction Metric" is null. This IE shall be ignored by the receiver if the "Overload Reduction Metric" is null. |
EPC Timer |
0 |
List of Access Point Name (APN) |
CO |
The IE may (only) be present in the "PGW’s Overload Control Information" IE. For indicating the APN level overload, the PGW shall include one or more instances of this IE, up to maximum of 10, with the same type and instance value, representing a list of APN(s) (sharing the same "Overload Reduction Metric" and "Period of Validity"). See NOTE 1. |
APN |
0 |
NOTE 1: If more than 10 occurrences of APNs are received within one instance of the Overload Control Information IE, the receiver shall treat it as a protocol error and ignore the entire Overload Control Information IE instance. |