Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 16
▀ MME Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
278
S1AP Statistics:
Transmitted S1AP Data:
...
S1AP Encode Failure: 0
Paging Dropped: 0
show mme-service enodeb-association full
The
show mme-service enodeb-association full
command now includes new output field to display
configured S1 paging rate limit:
S1 Paging Rate Limit : 150 per second
show session subsystem facility sessmgr instance
The
show session subsystem facility sessmgr instance
command now includes a new output field to
display path failure pacing queue statistics for the specified session manager instance:
0 Current MME EGTP path failure queued for ecm-idle sessions
0 Current MME EGTP path failure queued for ecm-connected sessions
0 Maximum MME EGTP path failure queued for ecm-idle sessions
0 Maximum MME EGTP path failure queued for ecm-connected sessions
CSCub29503 - MME: Sv Improvements - MSC selection using DNS
Feature Changes
MSC Selection using DNS
This feature requires that a valid SRVCC license key be installed. Contact your Cisco Account or Support representative
for information on how to obtain a license.
for information on how to obtain a license.
As defined in 3GPP TS 29.303, the MME now supports the DNS-based method of using the Sv interface. In the NAPTR
query response, the MME will analyze the “Service Parameter” of “x-3gpp-msc:x-sv”, and select a specific MSC from a
pool list provided in the DNS response. The provisioned weights and priorities on the DNS server are used to load share
proportionally between the MSC servers.
query response, the MME will analyze the “Service Parameter” of “x-3gpp-msc:x-sv”, and select a specific MSC from a
pool list provided in the DNS response. The provisioned weights and priorities on the DNS server are used to load share
proportionally between the MSC servers.
The DNS query FQDN will be based on RAC, LAC, MNC, MCC as follows:
rac<RAC>.lac<LAC>.rac.epc.mnc<MNC>. mcc<MCC>.3gppnetwork.org
MSC selection using DNS takes precedence over locally configured MSCs.
If DNS lookup fails, the MSC will be selected from local configuration.
Customer Impact: This feature provides flexibility to simplify SRVCC configuration.