для Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
MME Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
295
mme-service mme_svc_name
ho-resource-release-timeout timeout
[ default ] ho-resource-release-timeout
end
Notes:
This is the amount of time in milliseconds that the MME will hold on to bearers and E-RABs after an S1-based
handover has been initiated. When this timer expires, the source MME will send a UE Context Release to the
source eNodeB. Refer to 3GPP TS 23.401 Section 5.5.1.2.2 for additional information about the use of this
timer.
source eNodeB. Refer to 3GPP TS 23.401 Section 5.5.1.2.2 for additional information about the use of this
timer.
timeout
must be an integer from 500 through 15000.
Default: 5000 (5 seconds).
Performance Indicator Changes
show mme-service all
The following fields have been added to the output of the
show mme-service all
command to display the
configuration of the above commands:
PS-LTE Operation
SGW Address
HO Resource Release Timeout
CSCuh04641 - Timers for congestion conditions
Feature Changes
Congestion Control Enhancements
This feature requires that a valid MME Resliency license key be installed. Contact your Cisco Account or Support
representative for information on how to obtain a license.
representative for information on how to obtain a license.
With this StarOS release, the MME supports several of the 3GPP TS23.401 R10 machine type communications (MTC)
overload control mechanisms to be used in the handling of signaling bursts from machine-to-machine (M2M) devices.
This feature set allows the operator to handle the signaling storm MTC devices can bring to the network thus ensuring a
more robust network and more efficient resource utilization
overload control mechanisms to be used in the handling of signaling bursts from machine-to-machine (M2M) devices.
This feature set allows the operator to handle the signaling storm MTC devices can bring to the network thus ensuring a
more robust network and more efficient resource utilization
This feature enhances the MME product to support congestion control in better way so that MME can reject or drop
requests based on the low priority of the subscribers or based on the APN.
requests based on the low priority of the subscribers or based on the APN.
When there is congestion in the system, MME detects it based on the already existing congestion detection techniques.
Based on the level of congestion, the MME application running in session manager will apply the congestion action
profile configured for that congestion level.
Based on the level of congestion, the MME application running in session manager will apply the congestion action
profile configured for that congestion level.
Congestion Control for LAPI Subscribers: The current CLI configuration for congestion action profile has
been enhanced to take action (reject or drop) for MTC subscribers with Low Access Priority Indication (LAPI).