Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
▀ MME Enhancements for 17.4
▄ Release Change Reference, StarOS Release 17
260
New Behavior: 1 byte for the length indicator is added in the ConcurrentWarningMessageIndicator IE of the Warning
Write Replace Request. So the Concurrent Warning message indicator is encoded in 5 bytes (per ITU ASN.1
specification) as:
Write Replace Request. So the Concurrent Warning message indicator is encoded in 5 bytes (per ITU ASN.1
specification) as:
00 8e 00 01 00
CSCuu67762 - Enforce license for MTC functionality
Feature Changes
License Control for MTC Functionality
Previous Behavior: The feature specific license was not enforced to use the commands and functionality related to the
optional MTC feature functionality on the MME.
optional MTC feature functionality on the MME.
New Behavior: With Release 17.4, the MTC Feature license is now enforced to use MTC functions and related
commands. Please speak with your Cisco Customer Representative if you have questions about the MTC Feature
license.
commands. Please speak with your Cisco Customer Representative if you have questions about the MTC Feature
license.
For information on the MTC functionality supported by the MME, refer to sections CSCuh04641, CSCum37443, and
CSCum37475 in the MME Enhancements for 17.0 in this document.
CSCum37475 in the MME Enhancements for 17.0 in this document.
CSCuu82559 - MME doesn't send Charging Characteristics in
EGTP_CREATE_SESSION_REQUEST
Feature Changes
Inclusion of Charging Characteristics IE
Previous Behavior: Earlier, after a handover occurs from GN/GP, the Charging Characteristics IE was not included in
the EGTP_CREATE_SESSION_REQUEST during the following scenarios:
the EGTP_CREATE_SESSION_REQUEST during the following scenarios:
When a subscriber moves from a 3G to a 4G network.
When MME sends a GTP_SGSN_CONTEXT_REQ_MSG message to SGSN, and when SGSN replies with
GTP_SGSN_CONTEXT_RES_MSG.
When MME sends a CREATE_SESSION_REQUEST without including Charging Characteristics IE.
When a 4G call is terminated.
When SGW generates CDR with default Charging Characteristics 0x800.
New Behavior: In this release, during GN/GP handovers, MME is modified to include SGSN Charging Characteristics
IE in the Create Session Request. The Charging Characteristics is included if:
IE in the Create Session Request. The Charging Characteristics is included if:
Peer-SGSN sends the Charging Characteristics or
MME has a local configuration to include the Charging Characteristics