Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 16
▀ MME Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
270
CSCtt33631 - session disconnect-reason - mme-regional-zone-code needs to
be removed
Performance Indicator Changes
System Schema
The system disconnect reason disc-reason-484: mme-regional-zone-code(484) has been deprecated in this release as it
was duplicated by disc-reason-492: mme-zone-code-validation-failed.
was duplicated by disc-reason-492: mme-zone-code-validation-failed.
This disconnect reason (484) is now reused for tracking non-3gpp-access disconnects. Refer to CSCzn16621,
CSCzn16622 in this document for more information.
CSCzn16622 in this document for more information.
CSCtt40129 - MME(LI)-Support for Request Type TLV in TYPE x14 IRI event
Feature Changes
Request Type TLV Support in Lawful Intercept
Lawful Intercept has been enhanced to send the Request Type TLV. When a PDN connectivity is requested from the
mobile to allow multiple PDN connections, a UE requested PDN connectivity event is generated by the MME. The
purpose of the Request type information element is to indicate whether the MS requests to establish a new connectivity
to a PDN or keep the connection(s) to which it has connected via non-3GPP access.
mobile to allow multiple PDN connections, a UE requested PDN connectivity event is generated by the MME. The
purpose of the Request type information element is to indicate whether the MS requests to establish a new connectivity
to a PDN or keep the connection(s) to which it has connected via non-3GPP access.
CSCtt61742 - MME should support configuration to distinguish between
HENBGW and eNBs
Feature Changes
Configuration Support for Differentiation Between HeNB-GW and eNodeBs
The MME now can be configured to distinguish the Home eNodeB Gateway (HeNB-GW) from other eNodeBs. This is
required to support S1 HANDOVERs to Home eNodeBs connected via a HeNB-GW.
required to support S1 HANDOVERs to Home eNodeBs connected via a HeNB-GW.
As per 3GPP TS 36.300, section 4.6.2, the TAI used in a HeNB-GW should not be reused in another HeNB-GW. The
global eNodeB id of the HeNB-GW can now be configured in the lte-policy.
global eNodeB id of the HeNB-GW can now be configured in the lte-policy.
In case of S1-based handovers to Home eNodeBs served by a HeNB-GW, the lookup at MME for the target eNodeB
based on global ENB id will fail, as MME is aware of only the HeNB-GW. In those cases additional lookup needs to be
done based on TAI to find the HeNB-GW serving the Home eNodeB.
based on global ENB id will fail, as MME is aware of only the HeNB-GW. In those cases additional lookup needs to be
done based on TAI to find the HeNB-GW serving the Home eNodeB.
Customer Impact: This feature allows operators to configure the global eNodeB ids of HeNB-GWs in the mme-
service. The MME uses this information to perform HeNB-GW related functions.
service. The MME uses this information to perform HeNB-GW related functions.
Command Changes
mme henbgw mgmt-db