7.2.8 Modify Bearer Response

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

The Modify Bearer Response message shall be sent on the S11/S4 interfaces by the SGW to the MME/S4-SGSN, on the S5/S8 interfaces by the PGW to the SGW and on the S2b interface by the PGW to the ePDG as part of the procedures listed for the Modify Bearer Request (see clause 7.2.7).

If the MME has sent the counter for the RRC Cause "MO Exception data" in the Modify Bearer Resquest, the MME shall reset the counter value when receiving the Modify Bearer Response message.

If handling of default bearer fails, then Cause at the message level shall be a failure cause.

Possible Cause values are specified in Table 8.4-1. Message specific cause values are:

– "Request accepted".

– "Request accepted partially".

– "Context not found".

– "Service not supported".

Table 7.2.8-1: Information Elements in a Modify Bearer Response

Information elements

P

Condition / Comment

IE Type

Ins.

Cause

M

Cause

0

MSISDN

C

This IE shall be included on S5/S8 interfaces by the PGW if it is stored in its UE context and if this message is triggered due to TAU/RAU/HO with SGW relocation.

MSISDN

0

Linked EPS Bearer ID

C

This IE shall be sent on S5/S8 when the UE moves from a Gn/Gp SGSN to the S4 SGSN or MME to identify the default bearer the PGW selects for the PDN Connection.

This IE shall also be sent by SGW on S11, S4 during Gn/Gp SGSN to S4-SGSN/MME HO procedures to identify the default bearer the PGW selects for the PDN Connection.

EBI

0

APN Restriction

C

This IE denotes the restriction on the combination of types of APN for the APN associated with this EPS bearer Context. This IE shall be included over S5/S8 interfaces, and shall be forwarded over S11/S4 interfaces during:

  • Gn/Gp SGSN to MME/S4-SGSN handover procedures;
  • Gn/Gp SGSN to S4 SGSN/MME RAU/TAU procedures;
  • 5GS to EPS Idle mode mobility or handover procedures.

The target MME or SGSN determines the Maximum APN Restriction using the APN Restriction.

APN Restriction

0

Protocol Configuration Options (PCO)

C

If SGW receives this IE from PGW on GTP or PMIP based S5/S8, the SGW shall forward PCO to MME/S4-SGSN during Inter RAT handover from the UTRAN or from the GERAN to the E-UTRAN. See NOTE 2.

PCO

0

Bearer Contexts modified

C

EPS bearers corresponding to Bearer Contexts to be modified that were sent in Modify Bearer Request message. Several IEs with the same type and instance value may be included as necessary to represent a list of the Bearers which are modified.

Bearer Context

0

Bearer Contexts marked for removal

C

EPS bearers corresponding to Bearer Contexts to be removed sent in the Modify Bearer Request message. Shall be included if request message contained Bearer Contexts to be removed.

For each of those bearers an IE with the same type and instance value shall be included.

Bearer Context

1

Change Reporting Action

C

This IE shall be included 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 with the appropriate Action field if the location CSG Info change 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

Charging Gateway Name

C

When Charging Gateway Function (CGF) Address is configured, the PGW shall include this IE on the S5 interface during SGW relocation and when the UE moves from Gn/Gp SGSN to S4-SGSN/MME. See NOTE 1.

FQDN

0

Charging Gateway Address

C

When Charging Gateway Function (CGF) Address is configured, the PGW shall include this IE on the S5 interface during SGW relocation and when the UE moves from Gn/Gp SGSN to S4-SGSN/MME. See NOTE 1.

IP Address

0

PGW-FQ-CSID

C

This IE shall be included by PGW on S5/S8and shall 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

Recovery

C

This IE shall be included if contacting the peer for the first time.

Recovery

0

SGW LDN

O

This IE is optionally sent by the SGW to the MME/SGSN on the S11/S4 interfaces (see 3GPP TS 32.423 [44]), when communicating the LDN to the peer node for the first time.

Local Distinguished Name (LDN)

0

PGW LDN

O

This IE is optionally sent by the PGW to the SGW on the S5/S8 interfaces (see 3GPP TS 32.423 [44]), when communicating the LDN to the peer node for the first time.

Local Distinguished Name (LDN)Name

1

Indication Flags

CO

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

Applicable flags are:

  • Static IPv4 Address Flag: This flag shall be set to 1 on the S5/S8 interface in the TAU/RAU/Handover with SGW change procedure if the PDP/PDN IPv4 address is static as specified in 3GPP TS 32.251 [8]. See NOTE 3.
  • Static IPv6 Address Flag: This flag shall be set to 1 on the S5/S8 interface in the TAU/RAU/Handover with SGW change procedure if the PDP/PDN IPv6 address is static as specified in 3GPP TS 32.251 [8]. See NOTE 3.
  • PDN Pause Support Indication: this flag shall be set to 1 on the S5/S8 interface during the TAU/RAU/handover with SGW relocation procedures if the PGW supports the PGW Pause of Charging procedure.
  • PDN Pause Enable Indication: this flag shall be set to 1 on the S5/S8 interface during the TAU/RAU/handover with SGW relocation procedures if the PGW enables the new SGW to use the PGW Pause of Charging procedure for this PDN connection.
  • 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.
  • Delay Tolerant Connection Indication: the flag shall be set to 1 on the S5/S8 interface during a SGW relocation procedure and when the UE moves from Gn/Gp SGSN to S4-SGSN/MME if the PDN connection is "Delay Tolerant" (see clause 8.12). See NOTE 9.
  • Notify Start Pause of charging via User plane Support Indication: this flag shall be set to 1 on the S5/S8 interface during a SGW relocation procedure if PDN Pause Enable Indication is set to "1" and if the PGW-C and PGW-U support the Notify Start Pause of Charging via user plane feature as specified in clause 5.30 of 3GPP TS 29.244 [80].

Indication

0

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 a Presence Routing Area 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 5, NOTE 7.

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 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 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 6, NOTE 8.

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

PDN Connection Charging ID

CO

The PGW shall include this IE on the S5/S8 interface during a TAU/RAU/HO with SGW relocation procedure, if a PDN connection Charging ID has been allocated during the initial Attach or Initial PDN connection establishment procedure.

Charging ID

0

PGW Change Info

CO

This IE shall be included by the PGW on the S5/S8 interface if it supports the Restoration of PDN connections after an PGW-C/SMF Change procedure as specified in clause 31 of 3GPP TS 23.007 [17] and if the "Restoration of PDN connections after an PGW-C/SMF Change Support Indication" was set to 1 in the Modify Bearer Request message.

This IE may be included otherwise to change the PGW Change Info.

The SGW shall transparently forward this IE over the S11 interface.

PGW Change Info

0

Private Extension

O

Private Extension

VS

NOTE 1: Both Charging Gateway Name and Charging Gateway Address shall not be included at the same time. When both are available, the operator configures a preferred value.

NOTE 2: If MME receives the IE, but no NAS message is sent, MME discards the IE.

NOTE 3: Static IPv4/IPv6 Address Flag is used by SGW to provide dynamic IPv4/v6 address flag information as specified in 3GPP TS 32.251 [8].

NOTE 4: The conditions of presence of the IEs in the Modify Bearer Response for the MME and S4-SGSN triggered Serving GW relocation (see clause 5.10.4 of 3GPP TS 23.401 [3] and clause 9.2.2.4 of 3GPP TS 23.060 [35]) are identical to those specified respectively for X2 handover with SGW relocation and for Enhanced Serving RNS Relocation with SGW relocation.

NOTE 5: 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 6: 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 7: 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 8: 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 9: The SGW may use the DTCI during a Network Triggered Service Restoration procedure as specified in the clause 25.2.1 of 3GPP TS 23.007 [17].

Table 7.2.8-2: Bearer Context modified within Modify Bearer Response

Octets 1

Bearer Context IE Type = 93 (decimal)

Octets 2 and 3

Length = n

Octets 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

EPS Bearer ID

M

EBI

0

Cause

M

This IE shall indicate if the bearer handling was successful, and if not, gives information on the reason.

Cause

0

S1-U SGW F-TEID

C

This IE shall be used on the S11 interface, if the S1 interface is used, i.e. if the S11-U Tunnel flag was not set in the Modify Bearer Request. If the ‘Change F-TEID support Indication’ flag was set to 1 in the Modify Bearer Request and the SGW needs to change the F-TEID, the SGW shall include the new GTP-U F-TEID value. Otherwise, the SGW shall return the currently allocated GTP-U F-TEID value. See NOTE 1

F-TEID

0

S12 SGW F-TEID

C

This IE shall be included on the S4 interface if the S12 interface is being used. If the ‘Change F-TEID support Indication’ flag was set to 1 in the Modify Bearer Request and the SGW needs to change the F-TEID, the SGW shall include the new GTP-U F-TEID value. Otherwise, the SGW shall return the currently allocated GTP-U F-TEID value. See NOTE 1

F-TEID

1

S4-U SGW F-TEID

C

This IE shall be present if used on the S4 interface if the S4-U interface is being used. If the ‘Change F-TEID support Indication’ flag was set to 1 in the Modify Bearer Request and the SGW needs to change the F-TEID, the SGW shall include the new GTP-U F-TEID value. Otherwise, the SGW shall return the currently allocated GTP-U F-TEID value. See NOTE 1

F-TEID

2

Charging ID

C

This IE shall be present on the S5/S8 interface if this message is triggered due to one of the following procedures:

  • TAU/RAU/HO with SGW relocation
  • TAU/RAU/HO from Gn/Gp SGSN to MME/S4-SGSN

Charging ID

0

O

If S5/S8 interface is GTP, this IE may be sent on the S4 interface, in order to support CAMEL charging at the SGSN, for the following procedures:

  • inter-SGSN RAU/Handover/SRNS Relocation without SGW change.
  • inter-SGSN Handover/SRNS Relocation with SGW change.

Bearer Flags

CO

Applicable flags are:

  • PPC (Prohibit Payload Compression): This flag shall be sent on the S5/S8 and the S4 interfaces at S4-SGSN relocation.

Bearer Flags

0

S11-U SGW F-TEID

C

This IE shall be present on the S11 interface if S11-U is being used, i.e. if the S11-U Tunnel flag was set in the Modify Bearer Request. If the ‘Change F-TEID support Indication’ flag was set to 1 in the Modify Bearer Request and the SGW needs to change the F-TEID, the SGW shall include the new GTP-U F-TEID value. Otherwise, the SGW shall return the currently allocated GTP-U F-TEID value.

F-TEID

3

NOTE 1: The SGW shall use the same F-TEID IP address and TEID values for S1-U, S11-U, S4-U and S12 interfaces; as an exception, when separate IP address spaces are used for S11-U and S1-U, for Control Plane CIoT EPS Optimization, a different IP address and TEID may be used for the S11-U F-TEID.The SGW shall not change its F-TEID for a given interface during the Handover, Service Request, E-UTRAN Initial Attach, Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, UE Requested PDN connectivity, PDP Context Activation, Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN and E-UTRAN Initiated E-RAB modification procedures.
During Handover and Service Request the target eNodeB/RNC/SGSN may use a different IP type than the one used by the source eNodeB/RNC/SGSN. In order to support such a scenario, the SGW F-TEID should contain both an IPv4 address and an IPv6 address (see also clause 8.22 "F-TEID").

Table 7.2.8-3: Bearer Context marked for removal within Modify Bearer Response

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

Cause

M

This IE shall indicate if the bearer handling was successful, and if not, gives information on the reason.

Cause

0

Table 7.2.8-4: Load Control Information within Modify Bearer Response

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.8-5: Overload Control Information within Modify Bearer Response

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.

Table 7.2.8-6: PGW Change Info within Modify Bearer Response

Octet 1

PGW Change Info IE Type = 214 (decimal)

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

PGW Set FQDN

C

When present, this IE shall contain the PGW Set FQDN of the PGW-C/SMF set to which the PGW-C/SMF belongs.

(NOTE)

PGW FQDN

0

Alternative PGW-C/SMF IP Address

C

When present, this IE shall contain alternative PGW-C/SMF IP addresses within the PGW-C/SMF set to which the PGW-C/SMF belongs.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF IP Addresses.

(NOTE)

IP Address

0

Alternative PGW-C/SMF FQDN

C

When present, this IE shall contain alternative PGW-C/SMF FQDN within the PGW-C/SMF set to which the PGW-C/SMF belongs.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF FQDNs.

(NOTE)

PGW FQDN

1

Group Id

O

When present, this IE shall identify the group to which the PDN connection pertains (see clause 31.6 of 3GPP TS 23.007 [17]).

The MME shall replace any earlier value associated to the PDN connection with the new value.

Group Id

0

NOTE: Either the PGW Set FQDN IE, the Alternative PGW-C/SMF IP Address IE, or the Alternative PGW-C/SMF FQDN IE shall be present.