7.2.5 Bearer Resource Command

29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 16Stage 3TS

A Bearer Resource Command message shall be sent from a MME to a SGW and forwarded to PGW as a part of the UE requested bearer resource allocation procedure or UE requested bearer resource modification procedure (which is used also for a dedicated bearer deactivation or dedicated bearer activation), as specified by 3GPP TS 24.301 [23].

The message shall also be sent on the S4 interface by a SGSN to a SGW and on the S5/S8 interface by a SGW to a PGW as part of the MS initiated PDP Context modification procedure, or secondary PDP context activation procedure.

The message shall also be sent on the S11/S4 interface by an MME/S4-SGSN to a SGW and on the S5/S8 or S2a/S2b interface by a SGW or a TWAN/ePDG to a PGW 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.5-1 specifies the presence of the IEs in the message.

Table 7.2.5-1: Information Elements in a Bearer Resource Command

Information elements

P

Condition / Comment

IE Type

Ins.

Linked EPS Bearer ID (LBI)

M

EBI

0

Procedure Transaction Id (PTI)

M

PTI

0

Flow Quality of Service (Flow QoS)

C

This IE shall be included on the S4/S11 interface if the "Requested New QoS"/"Required QoS" is included in the corresponding NAS message (see clause 9.5.10 and clause 9.5.4 in 3GPP TS 24.008 [5]) or the "Required traffic flow QoS" is included in the corresponding NAS message (see clause 8.3.8 and clause 8.3.10 in 3GPP TS 24.301 [23]).

If SGW receives this IE, SGW shall forward it to PGW across S5/S8 interface.

Flow QoS

0

Traffic Aggregate Description (TAD)

M

The TAD consists of the description of the packet filter(s) for a traffic flow aggregate.

MME shall include this IE over S11 interface.

TAD

0

CO

If S4-SGSN receives this IE from the UE, it shall include it over S4 interface.

CO

If SGW receives this IE, the SGW shall forward it to PGW over S5/S8 interface. See NOTE 2.

RAT Type

C

This IE shall be included for MS initiated PDP Context modification procedure and Secondary PDP context activation procedure.

RAT Type

0

Serving Network

O

This IE may be included in the MS initiated PDP Context modification procedure.

See NOTE 3.

Serving Network

0

User Location Information (ULI)

O

This IE may be included in the MS initiated PDP Context modification procedure.

See NOTE 3.

ULI

0

EPS Bearer ID

C

This IE indicates the EPS Bearer that needs to be modified. It shall be included for MS initiated PDP Context modification procedure. For EUTRAN this IE shall be present if it is triggered by the NAS Bearer Resource Modification Request message and its value shall be set to the value of the "EPS bearer identity for packet filter" IE received in that NAS message.

EBI

1

Indication Flags

CO

This IE shall be included if any one of the applicable flags is set to 1.

Applicable flags:

  • Change Reporting Support Indication: this flag may be set to 1 in the MS initiated PDP Context modification procedure if the SGSN/MME supports location Info Change Reporting and if the SGSN/MME’s operator policy permits reporting of location change to the operator of the PGW with which the session is established.
  • Direct Tunnel Flag: this flag shall be set to 1 on the S4 interface, if Direct Tunnel is used in the MS initiated PDP Context Modification procedure.

Indication

0

S4-U SGSN F-TEID

C

This IE shall be included on the S4 interface when direct tunnel is not established in the MS initiated PDP Context modification procedure See NOTE 1

F-TEID

0

S12 RNC F-TEID

C

This IE shall be included on the S4 interface when direct tunnel flag is set to 1 in the MS initiated PDP Context modification procedure. See NOTE 1

F-TEID

1

Protocol Configuration Options (PCO)

O

If the UE includes the PCO IE, then the MME/SGSN shall copy the content of this IE transparently from the PCO IE included by the UE.

If the SGW receives PCO from the MME/SGSN, the SGW shall forward it to the PGW.

PCO

0

Signalling Priority Indication

CO

The SGSN/MME shall include this IE on the S4/S11 interface if the UE indicates low access priority during the procedure.

The SGW shall forward this IE on the S5/S8 interfaces if received from the MME/SGSN.

Signalling Priority Indication

0

MME/S4-SGSN’s Overload Control Information

O

During an overload condition, the MME/S4-SGSN may include this IE on the S11/S4 interface if the overload control feature is supported by the MME/S4-SGSN and is activated for the PLMN to which the PGW belongs (see clause 12.3.11).

When present, the MME/S4-SGSN shall provide only one instance of this IE, representing its overload information.

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 PGW on the S5/S8 interface.

SGW’s Overload Control Information

O

During an overload condition, the SGW may include this IE over the S5/S8 interface if the overload control feature is supported by the SGW and is activated for the PLMN to which the PGW belongs (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

NBIFOM Container

CO

This IE shall be included on the S11/S4 or S2a/S2b interfaces if the MME/S4-SGSN or the TWAN/ePDG receives an NBIFOM Container from the UE as specified in 3GPP TS 24.161 73]. The Container Type shall be set to 4.

F-Container

0

CO

If the SGW receives an NBIFOM Container IE from the MME/S4-SGSN, the SGW shall forward it to the PGW on the S5/S8 interface.

Extended Protocol Configuration Options (ePCO)

O

If the UE includes the ePCO IE, then the MME shall copy the content of this IE transparently from the ePCO IE included by the UE.

If the SGW receives ePCO from the MME, the SGW shall forward it to the PGW.

ePCO

0

Sender F-TEID for Control Plane

CO

The SGW shall include this IE on the S5/S8 interfaces and set it to the last value sent to the PGW.

If the Sender F-TEID for Control Plane is received, the PGW shall only handle the Bearer Resource Command message if the Sender F-TEID for Control Plane in this message is the same as the last Sender F-TEID for Control Plane received on the given interface.

F-TEID

2

Private Extension

O

Private Extension

VS

NOTE 1: The conditional S4-U SGSN F-TEID and S12 RNC F-TEID IE are redundant (as the IEs will be included in Update Bearer Response message in the MS initiated PDP Context modification procedure). The receiver may ignore it.

NOTE 2: In the secondary PDP context activation procedure, if the Bearer Resource Command message without TAD IE is received, the PGW shall reject the message with cause "UE context without TFT already activated".

NOTE 3: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator for supporting UEs, or that of the allocated Core Network Operator for non-supporting UEs. As an exception, based on inter-operator roaming/sharing agreement, if the information on whether the UE is a supporting or non-supporting UE is available, the PLMN ID that is communicated to the HPLMN for non-supporting UEs shall be the Common PLMN ID.
In shared networks, when the MME/S4-SGSN and PGW pertain to the same PLMN, the Primary PLMN ID shall be communicated in the ECGI to the PGW, and the Common PLMN ID shall be communicated in SAI/CGI to the PGW, for both supporting and non-supporting UEs. The Core Network Operator PLMN ID (selected by the UE for supporting UEs or allocated by the network for non-supporting UEs) shall be communicated in the TAI, RAI, UCI and the Serving Network.
See clause 4.4 of 3GPP TS 23.251 [55].

NOTE: Depending on the protocol type on the S5/S8 interface, the SGW or the PGW will determine if the UE is requesting an Allocation/Modification operation of bearer resources for a traffic flow aggregate based on the TFT operation code and the packet filter ID value in the Traffic Aggregate (TAD) IE and/or the presence of the EPS Bearer ID IE.

Table 7.2.5-2: Overload Control Information within Bearer Resource Command

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 clause 12.3.5.1.2.3 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