Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
MME Changes in Release 15.0
MME Enhancements for 15.0 MR6 ▀
Cisco ASR 5x00 Release Change Reference ▄
283
Customer Impact: Support for this cause code will assist customers to debug the reject cause for bearer allocation
failures.
failures.
Performance Indicator Changes
MME Schema
Use of the “EPS QoS Not Accepted” reject cause code for bearer allocation failures, is tracked as a bulk statistic in the
MME schema:
MME schema:
esm-msgtx-brralloc-rej-eps-qos-not-accepted
show mme-service statistics
Use of the “EPS QoS Not Accepted” reject cause code for bearer allocation failures, is tracked with the following new
output counter generated by the
output counter generated by the
show mme-service statistics
command:
EPS QoS Not Accepted
CSCur13994, CSCur89572 - ’State/Location Information Retrieval’ flag support
in Feature-list AVP
Feature Changes
State/Location Information Retrieval’ Flag
With this release, the MME now sends the “State/Location-Information-Retrieval” flag set in the Feature-List AVP of
the Update Location Request (ULR) message over the S6a interface to the HSS at the time the UE attaches. With the
“State/Location-Information-Retrieval” flag set, the HSS knows to set the “EPS User State Request”, “EPS Location
Information Request” and “Current Location Request” bits in the IDR-Flags AVP in IDR messages towards the MME.
This subscriber data provides the UE’s current location information needed in multiple service scenarios, such as
VoLTE services on the IMS side.
the Update Location Request (ULR) message over the S6a interface to the HSS at the time the UE attaches. With the
“State/Location-Information-Retrieval” flag set, the HSS knows to set the “EPS User State Request”, “EPS Location
Information Request” and “Current Location Request” bits in the IDR-Flags AVP in IDR messages towards the MME.
This subscriber data provides the UE’s current location information needed in multiple service scenarios, such as
VoLTE services on the IMS side.
MME behavior for IDR-initiated Paging: Upon receipt of an IDR message with the “Current Location Request” bit
set in the IDR-Flags AVP, the MME behavior complies with Feature-List AVP, IDR-Flags AVP, and EPS-Location-
Information AVP sections as specified in 3GPP TS 29.272 v11.9.0. So when the IDR messages are received with “EPS
Location Information Request” and “Current Location Request” bits set in IDR-Flags AVP, the MME sends the UE's
current location information or the UE's last known location information in the “EPS-Location-Information” AVP of the
IDA message
set in the IDR-Flags AVP, the MME behavior complies with Feature-List AVP, IDR-Flags AVP, and EPS-Location-
Information AVP sections as specified in 3GPP TS 29.272 v11.9.0. So when the IDR messages are received with “EPS
Location Information Request” and “Current Location Request” bits set in IDR-Flags AVP, the MME sends the UE's
current location information or the UE's last known location information in the “EPS-Location-Information” AVP of the
IDA message
If IDR is received with “EPS Location Information Request” and “Current Location Request” flags set in IDR-Flags
AVP, the the MME's IDA response depends on whether :
AVP, the the MME's IDA response depends on whether :
the UE is in connected mode with Location Reporting active making location information available, then the
MME sends the IDA message without “Current-Location-Retrieved” AVP in “EPS-Location-Information”
AVP.
AVP.
the UE is in connected mode without Location Reporting active so location information is not available, then the
MME sends a Location-Reporting-Control message to the eNB to get the ECGI and the TAI.