Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
MME Changes in Release 15.0
▀ MME Enhancements for October 31, 2014
▄ Cisco ASR 5x00 Release Change Reference
302
Performance Indicator Changes
show session subsystem facility mmedemux verbose
The following counter has been added to the output of the
show session subsystem facility mmedemux
verbose
command.
This counter tracks the number of incoming packets dropped by the MME Demux subsystem (at S1 interface, coming
from eNodeB) while waiting for all MME Managers to be activated (status = UP). The MME waits to start processing
traffic only after the expected number of MME Managers are UP after an MME restart.
from eNodeB) while waiting for all MME Managers to be activated (status = UP). The MME waits to start processing
traffic only after the expected number of MME Managers are UP after an MME restart.
Total number of packets dropped (Total MME Unavail)
CSCup67478 - Reset-Req delete all sessions and send wrong feature-list to
other HSSs
Feature Changes
HSS Reset Request Logic Enhancements
Previous Behavior: When a Reset Request without a username (User-ID) was received from an HSS, the MME sent
the Reset Request (including received Feature-List value) for all subscriber sessions irrespective of which HSS they
were attached to earlier.
the Reset Request (including received Feature-List value) for all subscriber sessions irrespective of which HSS they
were attached to earlier.
New Behavior: The MME now compares the received HSS's host name in the Reset-Request (RR) with all the local
diameter-hss session's bound-host names and then sends the RR only for those sessions which are bound to that HSS
host name.
diameter-hss session's bound-host names and then sends the RR only for those sessions which are bound to that HSS
host name.
This same change applies even if a RR is received with a User-ID, because the User-ID contains only the leading digits
of IMSI and multiple IMSIs can match to the same User-ID. In this case some matched IMSI sessions may be bound to
different HSS than the one which has sent the RR. So in this case also the RR is sent for those sessions which are bound
to the HSS.
of IMSI and multiple IMSIs can match to the same User-ID. In this case some matched IMSI sessions may be bound to
different HSS than the one which has sent the RR. So in this case also the RR is sent for those sessions which are bound
to the HSS.
CSCup71470 - Not interpreting RZC H6a AVP as a full hexadecimal value
Feature Changes
HSS Zone Code Format
Previous Behavior: The MME always interpreted the received zone-code as an ASCII string (coded in hexadecimal
representation) and converted it byte by byte to an integer value. For example, if the HSS sends the zone-code value as
3032, the MME converted this to 02 (ASCII value of 0 in Hex is 0x30, ASCII value of 2 in Hex is 0x32). As a result,
the MME accepted zone-codes only within the range of 0 to 99.
representation) and converted it byte by byte to an integer value. For example, if the HSS sends the zone-code value as
3032, the MME converted this to 02 (ASCII value of 0 in Hex is 0x30, ASCII value of 2 in Hex is 0x32). As a result,
the MME accepted zone-codes only within the range of 0 to 99.
New Behavior: By default, the MME now interprets the received zone-code value from HSS as a octet-string (2 bytes)
which is coded in full hexadecimal representation. The MME now converts the entire 2 byte octet string coded in
hexadecimal to integer value and it uses the same for validation for zone-code restriction feature. For example, if the
HSS sends the zone-code value as 3032, MME converts this to 12338 (which is the equivalent of 0x3032).
which is coded in full hexadecimal representation. The MME now converts the entire 2 byte octet string coded in
hexadecimal to integer value and it uses the same for validation for zone-code restriction feature. For example, if the
HSS sends the zone-code value as 3032, MME converts this to 12338 (which is the equivalent of 0x3032).