Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 16
MME Enhancements for 16.5 ▀
Release Change Reference, StarOS Release 16 ▄
211
CSCus18004 - MME rounds down max bitrate in VoLTE leading to packet loss
Feature Changes
Rounding Up Some Assigned QoS Values
MME rounded down the MBR and GBR values for both Uplink and Downlink in some scenarios. This behavior has
been modified to support rounding up in place of rounding down - as described below.
been modified to support rounding up in place of rounding down - as described below.
Previous Behavior: MME rounded down the assigned QoS values if the requested QoS did not align in order of 8
(<576Kbit/s) or 64 (<8640Kbit/s) and in order of 100kbps(<16000Kbit/s), (<=128000Kbit/s)1Mbps and
(<256000Kbit/s) 2Mbps increments for extended values. For example, if the requested QoS value is 78Kbps the MME
rounded down the QoS to 72Kbps.
(<576Kbit/s) or 64 (<8640Kbit/s) and in order of 100kbps(<16000Kbit/s), (<=128000Kbit/s)1Mbps and
(<256000Kbit/s) 2Mbps increments for extended values. For example, if the requested QoS value is 78Kbps the MME
rounded down the QoS to 72Kbps.
New Behavior: MME rounds up the assigned QoS values if the requested QoS is not aligning in order of 8
(<576Kbit/s) or 64 (<8640Kbit/s) and in order of 100kbps(<16000Kbit/s), (<=128000Kbit/s)1Mbps and
(<256000Kbit/s)2Mbps increments for extended values. For example, if the requested QoS value is 78Kbps the MME
rounds up the QoS to 80Kbps.
(<576Kbit/s) or 64 (<8640Kbit/s) and in order of 100kbps(<16000Kbit/s), (<=128000Kbit/s)1Mbps and
(<256000Kbit/s)2Mbps increments for extended values. For example, if the requested QoS value is 78Kbps the MME
rounds up the QoS to 80Kbps.
During 4G to 3G (S3 to S4-SGSN) RAU, the MME does not send rounded QoS value to the SGSN. The SGSN is left to
make the decision to round up or round down.
make the decision to round up or round down.
CSCus82793 - MME Re-locate UE command to expand range from 0-65536
Feature Changes
Expanded ‘mme-group-id’ Range
MME uses configured values for IMSI, mme-group-id, mme-code, and m-tmsi to identify UEs to relocate.
Previous Behavior: The operator could configure a value for the ‘mme-group-id’ (as part of the
mme relocate-ue
command under the Execute mode) from the range 32678 to 65536.
New Behavior: The range has been exanded and the operator now can configure a value for the ‘mme-group-id’ (as
part of the
part of the
mme relocate-ue
command under the Execute mode) from the range 0 to 65536. This range now
matches the configurable range for MME group-id with the
mme-id
command in the MME service configuration mode.
Customer Impact: MME uses this configuration to relocate UEs using IMSI, mme-group-id, mme-code and m-tmsi.
Now the MME can relocate subscribers using GUTI-reolocate commands for group-ids less than 32768. This allows
inter-RAT HO as the GUTI Relocation command in the NAS message to the UE includes a broader range of MME
Group IDs as defined with the
Now the MME can relocate subscribers using GUTI-reolocate commands for group-ids less than 32768. This allows
inter-RAT HO as the GUTI Relocation command in the NAS message to the UE includes a broader range of MME
Group IDs as defined with the
mme relocate-ue
command in the Execute mode.
Command Changes
mme relocate-ue
The range of values for the
mme-group-id
keyword has been expanded from 32768 to 65535 to 0 to 65535. This
command is issued from the Execute mode:
mme relocate-ue imsi imsi_value new-guti mme-group-id mme_group_id mme-code
mme_code_value m-tmsi m-tmsi_value
mme_code_value m-tmsi m-tmsi_value