7.2.15 Update Bearer Request

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

The direction of this message shall be from PGW to SGW and/or from SGW to MME/S4-SGSN, and/or from PGW to TWAN/ePDG (see Table 6.1-1).

For GTP based S5/S8, the Update Bearer Request shall be sent by the PGW to the SGW and forwarded to the MME as part of the following procedures:

– PGW Initiated Bearer Modification with Bearer QoS Update

– HSS Initiated Subscribed QoS Modification

– PGW Initiated Bearer Modification without Bearer QoS Update

– UE Request Bearer Resource Modification procedure (see 3GPP TS 24.301 [23])

– UE requested bearer resource allocation procedure (see 3GPP TS 24.301 [23])

– P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])

The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of the following procedures:

– PGW Initiated EPS Bearer Modification

– Execution part of MS-Initiated EPS Bearer Modification

– SGSN-Initiated EPS Bearer Modification Procedure using S4

– P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])

The message shall also be sent on the S2a/S2b interface by the PGW to the TWAN/ePDG as part of the following procedures:

– PGW Initiated Bearer Modification

– HSS Initiated Subscribed QoS Modification

– P-CSCF restoration for WLAN access (see 3GPP TS 23.380 [61])

For PMIP based S5/S8, the Update Bearer Request shall be sent on the S11 interface by the SGW to the MME and on the S4 interface by the SGW to the SGSN.

The message shall also be sent on the S5/S8 or S2a/S2b interface by the PGW to the SGW or to the TWAN/ePDG and on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure or the UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161 [71].

Table 7.2.15-1 specifies the presence requirements and the conditions of the IEs in the message.

Table 7.2.15-1: Information Elements in an Update Bearer Request

Information elements

P

Condition / Comment

IE Type

Ins.

Bearer Contexts

M

This IE shall contain contexts related to bearers that need QoS/TFT modification. Several IEs with this type and instance values shall be included as necessary to represent a list of Bearers.

If there is no QoS/TFT modification, only one IE with this type and instance value shall be included.

Bearer Context

0

Procedure Transaction Id (PTI)

C

If the request corresponds to UE requested bearer resource modification procedure or the UE requested bearer resource allocation procedure for an E-UTRAN (see NOTE 1) or MS initiated EPS bearer modification procedure, this IE shall be included.

PTI shall be the same as the one used in the corresponding Bearer Resource Command

PTI

0

Protocol Configuration Options (PCO)

C

The PGW shall include the Protocol Configuration Options (PCO) IE on the S5/S8 interface, if available and if ePCO is not supported by the UE or the network. The PCO IE shall carry a P-CSCF address list only when the UE is required to perform an IMS registration, e.g during the P-CSCF restoration procedure as defined in clause 5 of 3GPP TS 23.380 [61].

If SGW receives this IE, SGW shall forward it to SGSN/MME on the S4/S11 interface.

PCO

0

CO

The PGW shall include the Prococol Configuration Options (PCO) IE on the S2a interface, including the list of available P-CSCF addresses, as part of the P-CSCF restoration extension procedure for the TWAN access, as specified in 3GPP TS 23.380 [61].

Aggregate Maximum Bit Rate (APN-AMBR)

M

APN-AMBR

AMBR

0

Change Reporting Action

C

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field If the location Change Reporting mechanism is to be started or stopped for this subscriber in the SGSN/MME.

Change Reporting Action

0

CSG Information Reporting Action

CO

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field if the CSG Info reporting mechanism is to be started or stopped for this subscriber in the SGSN/MME.

CSG Information Reporting Action

0

H(e)NB Information Reporting

CO

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field if H(e)NB information reporting is to be started or stopped for the PDN connection in the SGSN/MME.

H(e)NB Information Reporting

0

Indication flags

CO

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

Applicable flags are:

  • Retrieve Location Indication: This flag shall be set to 1 on the S5/S8, S4/S11, S2a and S2b interfaces in the PGW Initiated Bearer Modification procedure if the location information is requested.
  • Associate OCI with PGW node’s identity: The PGW shall set this flag to 1 on the S5/S8 interface or S2a/S2b interface if it has included the "PGW’s Overload Control Information" and if this information is to be associated with the node identity (i.e. FQDN or the IP address received from the HSS or DNS during the PGW selection) of the serving PGW. The SGW shall set this flag on the S11/S4 interface if it supports the overload control feature and if the flag is set on the S5/S8 interface.
  • Associate OCI with SGW node’s identity: The SGW shall set this flag to 1 on the S11/S4 interface if it has included the "SGW’s Overload Control Information" and if this information is to be associated with the node identity (i.e. FQDN or the IP address received from the DNS during the SGW selection) of the serving SGW.

Indication

0

PGW-FQ-CSID

C

This IE shall be included by PGW on the S5/S8 and S2a/S2b interfaces, and when received from S5/S8 be forwarded by SGW on S11 according to the requirements in 3GPP TS 23.007 [17].

FQ-CSID

0

SGW-FQ-CSID

C

This IE shall be included by SGW on S11 according to the requirements in 3GPP TS 23.007 [17].

FQ-CSID

1

Presence Reporting Area Action

CO

This IE shall be included on the S5/S8 and S11/S4 interfaces with the appropriate Action field if reporting changes of UE presence in Presence Routing Area(s) is to be started, stopped or modified for this subscriber in the MME/SGSN.

Several IEs with the same type and instance value may be included as necessary to represent a list of Presence Reporting Area Actions. One IE shall be included for each Presence Reporting Area to be started, stopped or modified.

Presence Reporting Area Action

0

PGW’s node level Load Control Information

O

The PGW may include this IE on the S5/S8 or S2a/S2b interface, providing its node level load information, if the load 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 network, ePDG/TWAN for non-3GPP access network, belongs (see clause 12.2.6).

Load Control Information

0

CO

If the SGW receives this IE and if it supports the load control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface.

PGW’s APN level Load Control Information

O

The PGW may include this IE on the S5/S8 or S2a/S2b interface, providing APN level load information, if the APN level load 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 network, ePDG/TWAN for non-3GPP access based network, belongs (see clause 12.2.6).

When present, the PGW shall provide one or more instances of this IE, up to maximum of 10, with the same type and instance value, each representing the load information for a list of APN(s).

See NOTE 2, NOTE 4.

Load Control Information

1

CO

If the SGW receives this IE and if it supports APN level load control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface.

SGW’s node level Load Control Information

O

The SGW may include this IE, over the S11/S4 interface if the load control feature is supported by the SGW and is activated in the network (see clause 12.2.6).

When present, the SGW shall provide only one instance of this IE, representing its node level load information.

Load Control Information

2

PGW’s Overload Control Information

O

During an overload condition, the PGW may include this IE on the S5/S8 or S2a/S2b interface, 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, ePDG/TWAN for non-3GPP access based network, belongs (see clause 12.3.11).

When present, the PGW shall provide

  • node level overload control, in one instance of this IE; and/or
  • APN level overload control, in one or more instances of this IE, up to maximum of 10, with the same type and instance value, each representing the overload information for a list of APN(s).

See NOTE 3, NOTE 5.

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

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 a NBIFOM Container IE from the PGW, the SGW shall forward it to the MME/S4-SGSN on the S11/S4 interface.

Private Extension

O

This IE may be sent on the S5/S8, S4/S11 and S2a/S2b interfaces.

Private Extension

VS

NOTE 1: This message refers to the UE requested bearer resource allocation procedure and UE requested bearer resource modification procedures defined in 3GPP TS 24.301 [23], both are specified in 3GPP TS 23.401 [3] in the clause "UE requested bearer resource modification".

NOTE 2: The receiver, not supporting the APN level load control feature, shall ignore all the occurrence(s) of this IE, i.e. "Load Control Information" IE with instance number "1". The receiver, supporting the APN level load control feature and supporting the APN level load information for the maximum of 10 APNs, shall handle the APN level load information for the first 10 APNs and ignore any more APN level load information.

NOTE 3: 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 4: The APN level load information, provided within and across different instances of the "PGW’s APN level Load Control Information" IE(s) shall be limited to 10 different APNs.

NOTE 5: 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.

NOTE: In the case that the procedure was initiated by a UE Requested Bearer Resource Modification Procedure or UE Requested Bearer Resource Allocation Procedure for an E-UTRAN or MS initiated EPS bearer modification procedure, then there will be only one instance of the Bearer Contexts IE in the Update Bearer Request.

Table 7.2.15-2: Bearer Context within Update Bearer Request

Octet 1

Bearer Context IE Type = 93 (decimal)

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

EPS Bearer ID

M

EBI

0

TFT

C

This IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces if message relates to Bearer Modification and TFT change.

Bearer TFT

0

Bearer Level QoS

C

This IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces if QoS modification is requested

Bearer QoS

0

Bearer Flags

O

Applicable flags:

  • PPC (Prohibit Payload Compression): this flag may be set on the S5/S8 and S4 interfaces.
  • vSRVCC indicator: This IE may be included by the PGW on the S5/S8 interface according to 3GPP TS 23.216 [43]. When received from S5/S8, SGW shall forward on the S11 interface.

Bearer Flags

0

Protocol Configuration Options (PCO)

CO

PGW shall include Protocol Configuration Options (PCO) IE on the S5/S8 interface, if available and if ePCO is not supported by the UE or the network. The PCO IE shall carry a P-CSCF address list only when the UE is required to perform an IMS registration, e.g during the P-CSCF restoration procedure as defined in clause 5.1 of 3GPP TS 23.380 [61].

This bearer level IE takes precedence over the PCO IE in the message body if they both exist.

If the SGW receives this IE, the SGW shall forward it to the SGSN/MME on the S4/S11 interface.

PCO

0

CO

The PGW shall include the Prococol Configuration Options (PCO) IE on the S2a interface, including the list of available P-CSCF addresses, as part of the P-CSCF restoration extension procedure for the TWAN access, as specified in 3GPP TS 23.380 [61].

This bearer level IE takes precedence over the PCO IE in the message body if they both exist.

Additional Protocol Configuration Options (APCO)

CO

The PGW shall include the Additional Prococol Configuration Options (APCO) IE on the S2b interface, including the list of available P-CSCF addresses, as part of the P-CSCF restoration extension procedure for the untrusted WLAN access, as specified in 3GPP TS 23.380 [61].

Additional Protocol Configuration Options (APCO)

0

Extended Protocol Configuration Options (ePCO)

CO

The PGW shall include Extended Protocol Configuration Options (ePCO) IE on the S5/S8 interface, if available and if the UE and the network support ePCO. The ePCO IE shall carry a P-CSCF address list only when the UE is required to perform an IMS registration, e.g during the P-CSCF restoration procedure as defined in clause 5.1 of 3GPP TS 23.380 [61].

If the SGW receives this IE, the SGW shall forward it to the MME on the S11 interface.

ePCO

0

Maximum Packet Loss Rate

O

This IE may be included on the S5/S8 interfaces if the PGW needs to send Maximum Packet Loss Rate as specified in clause 5.4.2.1 of 3GPP TS 23.401 [3]. This IE is only applicable for QCI 1.

Maximum Packet Loss Rate

0

CO

If the SGW receives this IE, it shall forward it to the MME on the S11 interface

Table 7.2.15-3: Load Control Information within Update Bearer Request

Octet 1

Load Control Information IE Type = 181 (decimal)

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

Load Control Sequence Number

M

See clause 12.2.5.1.2.1 for the description and use of this parameter.

Sequence Number

0

Load Metric

M

See clauses 12.2.5.1.2.2 and 12.2.5.1.2.3 for the description and use of this parameter.

Metric

0

List of APN and Relative Capacity

CO

The IE shall (only) be present in the "PGW’s APN level Load Control Information" IE.

For indicating the APN level load, 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) & its respective "Relative Capacity" (sharing the same "Load Metric").

See clause 12.2.5.1.2.3 for the description and use of this parameter.

See NOTE 1.

APN and Relative Capacity

0

NOTE 1: If more than 10 occurrences of "APN and Relative Capacity" IE are received within one instance of the Load Control Information IE, the receiver shall treat it as a protocol error and ignore the entire Load Control Information IE instance.

Table 7.2.15-4: Overload Control Information within Update Bearer Request

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.