Modify Bearer Command (MBC) to PGW

1. MBC is sent on S2b interface by the ePDG to the PGW as part of the HSS Initiated Subscribed QoS Modification procedure.

2. It is done as part of 3GPP-AAA or ePDG initiated Re-authorization procedure.

3. In Authorization Authenticate Answer message, if result is DIAMETER_SUCCESS, AAA sends APN-Configuration AVP which will contain AMBR and EPS-Subscribed-QoS Profile.

4. If ambr or QoS value is changed, then MBC is sent to PGW, to start Update Bearer Request procedure.

Modify Bearer Failure Indication from PGW (MBC) to PGW

1. MBC is sent on S2b interface by the ePDG to the PGW as part of the HSS Initiated Subscribed QoS Modification procedure.

2. It is done as part of 3GPP-AAA or ePDG initiated Re-authorization procedure.

3. In Authorization Authenticate Answer message, if result is DIAMETER_SUCCESS, AAA sends APN-Configuration AVP which will contain AMBR and EPS-Subscribed-QoS Profile.

4. If ambr or QoS value is changed, then MBC is sent to PGW, to start Update Bearer Request procedure.

5. If PGW is not able to update AMBR or QoS (may be due to PCC infra), then it will send Modify Bearer Failure Indication to ePDG.

6. There is no action defined if ePDG receives Modify Bearer Failure Indication.

Scope and Assumptions

• MBC is sent only for default bearer update for apn-ambr or qci or arp update.

• This feature is enabled by default.

• There is no failure handling needed for Modify Bearer Failure Indication received if PGW is not able to update QoS profile.

• There is no change required to current implementation of Update Bearer Request and Update Bearer Response procedure handling on ePDG.

• There is no change required to current implementation of RAR/RAA and AAR/AAA message handling on ePDG.

• No SR / ICSR changes is required, as the final outcome for this feature is Update Beare Req/Rsp, which is already supported.

As part of ePDG Modify Bearer Command Support feature below show commands output used: show egtpc statistics interfae epdg-egress