Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
MME Enhancements for 17.4 ▀
Release Change Reference, StarOS Release 17 ▄
253
configure
context context_name
mme-service service_name
[no] legacy-tai-list-encoding
end
Notes:
By default, the TAI list value is encoded based on PLMN and TAC values of TAI entries.
The operator can use this command to configure the encoding of TAI list values to "010" irrespective of PLMN
and TAI values.
CSCus57109 - MME Not Incrementing any Paging Stats for DDN Without EBI
Feature Changes
Enabling Paging Statistics using Active Bearers
Previous Behavior: The Paging Statistics for paging requests were not accounted when the DDN from the SGW is
received without an EPS Bearer ID (EBI). The QCI values acquired using the EBI is primarily required for accounting
paging statistics. Since, the EBI field was made available only from release 10 onwards, the DDN was received from
SGW without the EBI and therefore, the Paging Statistics could not be accounted.
received without an EPS Bearer ID (EBI). The QCI values acquired using the EBI is primarily required for accounting
paging statistics. Since, the EBI field was made available only from release 10 onwards, the DDN was received from
SGW without the EBI and therefore, the Paging Statistics could not be accounted.
New Behavior: In case the DDN from SGW is received without EBI, the configuration is modified such that the QCI
values are taken from all available active bearers of the UE. The QCI values from these active bearers will be used to
account for Paging Statistics.
values are taken from all available active bearers of the UE. The QCI values from these active bearers will be used to
account for Paging Statistics.
CSCus68029 - Configurable wait time value for ISDA reqd for state/location
retrieval
Feature Changes
Configurable ISDA Guard Timer
Previous Behavior: The Insert Subscription Data Answer (ISDA) timer was hardcoded to a value of 25 seconds.
New Behavior: With this release, the operator can configure the ISDA guard timer to any value from 1 to 100 seconds.
Upon expiry of this wait timer, the MME sends the ISDA with the last-known location of the UE if the MME receives
the Insert Subscriber Data Response (ISDR) with both the location flags set (current and last-known locations). Only
when the ISDR is received with both flags set is the ISDA guard timer started. In situations where the MME receives
the ISDR with only the last-known location flag set, then the MME immediately sends the ISDA with location
information - no delay and this timer is not started even if configured.
Upon expiry of this wait timer, the MME sends the ISDA with the last-known location of the UE if the MME receives
the Insert Subscriber Data Response (ISDR) with both the location flags set (current and last-known locations). Only
when the ISDR is received with both flags set is the ISDA guard timer started. In situations where the MME receives
the ISDR with only the last-known location flag set, then the MME immediately sends the ISDA with location
information - no delay and this timer is not started even if configured.
Customer Impact: This timer is separate from the paging timer and configuration of the ISDA guard timer can reduce
the overall delay before sending the ISDA.
the overall delay before sending the ISDA.