MME Changes in Release 21.2

Transcription

1 MME Changes in Release This chapter identifies features and functionality added to, modified for, or deprecated from the MME in the StarOS software release. The following identifies all of the MME enhancements included in this release: - new or modified features or behavior changes. For details, refer to the MME Administration Guide for this release. Command Changes - changes to any of the CLI command syntax. For details, refer to the ASR 5x00 Command Line Interface Reference for this release. Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or fields in new or modified schema and/or show command output. For detailed information on the show commands, refer to the Statistics and Counters Reference for this release. For detailed information on the counters and disconnect reasons, refer to the BulkstatStatistics_documentation.xls spreadsheet that is included as part of the software companion package for this release. This release includes enhancements that are applicable to multiple products. The following lists the various multi-product enhancements sections, some of which might include content applicable to your MME. AAA Changes CF Changes ECS Changes Firewall Changes GTPP Changes Lawful Intercept Changes NAT Changes SNMP MIB Changes System and Platform Changes MME changes for include: Authentication Frequency Range Updated, page 2 Release Change Reference, StarOS Release 1

2 Authentication Frequency Range Updated MME Changes in Release edrx Paging Time Window (PTW) Range Updated, page 3 New Statistics for Asynchronous ISD Request, page 4 PDN Connectivity Reject, page 5 Scaling of TAI-Objects and TAI Database, page 6 Authentication Frequency Range Updated Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Behavior Change MME ASR 5000, ASR 5500, VPC-SI Disabled CSCvd81209 Command Line Interface Reference MME Administration Guide Revision History Revision history details are not provided for features introduced before release Revision Details The frequency for all variants of the "authenticate" CLI command in the Call Control Profile Configuration Mode is changed. Release Release Date April 27, Release Change Reference, StarOS Release

3 MME Changes in Release The Authentication Frequency range for all variants of the authenticate CLI command in the Call Control Profile Configuration Mode is changed in this release. Previous Behavior: The frequency for all variants of the authenticate CLI command was an integer ranging from 1 to 16. New Behavior: The frequency range for all variants of the authenticate CLI command will be an integer ranging from 1 to 256. edrx Paging Time Window (PTW) Range Updated Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Behavior change 21.0 MME ASR 5500 Disabled CSCvd92746 Command Line Interface Reference, Modes C - D MME Administration Guide Revision History Revision history details are not provided for features introduced before release Revision Details New behavior change in this release. Release Release Date April 27, 2017 Release Change Reference, StarOS Release 3

4 MME Changes in Release The Extended Discontinuous Reception (edrx) feature allows the device to connect to a network on a need basis the device can remain inactive or in sleep mode for minutes, hours or even days, thus increasing the battery life of the device. The edrx command is used to configure the edrx parameters - paging time window, edrx cycle length, downlink buffer duration and packet count values. Previous Behavior: The edrx command in the Call Control Profile Configuration mode is used to configure Extended Discontinuous Reception (edrx) and its parameters on the MME. The Paging Time Window (PTW) and edrx cycle length can be specified by the user. The PTW value is an integer ranging from 0 to 20. New Behavior: The range of Paging Time Window (PTW) is changed in this release as per 3GPP TS V ( ). The PTW value will be an integer ranging from 0 to 15. The E-UTRAN edrx cycle value is also updated in this release as per 3GPP TS V ( ). The range remains the same as an integer value from 512 to Only new values are added within this range. New Statistics for Asynchronous ISD Request Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Fix 21.0 MME ASR 5500 Enabled CSCvb01378 MME Administration Guide Statistics and Counters Reference 4 Release Change Reference, StarOS Release

5 MME Changes in Release Revision History Revision history details are not provided for features introduced before release Revision Details New behavior change in this release. Release Release Date April 27, 2017 Previous Behavior: Asynchronous ISD request received resulted in a crash when the MME was already processing another asynchronous ISD request. Statistics to display Asynchronous ISDR Requests, Asynchronous ISDA, Asynchronous ISDA Dropped, ISDR Request with Current Location and ISDA with Cached Location are present in the output of the show hss-peer-service statistics all command. There was no counter to display the number of asynchronous ISD requests dropped. New Behavior: Asynchronous ISD request received will be dropped when the MME is already processing another asynchronous ISD request. A new counter "Asynchronous ISDR Dropped" is added to the show hss-peer-service statistics all command to peg the asynchronous ISD requests dropped. Customer Impact: The customer will be able to check the number of asynchronous ISD requests dropped during the call model execution. PDN Connectivity Reject Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Modified Functionality MME ASR 5500 Enabled CSCvb99159 Release Change Reference, StarOS Release 5

6 MME Changes in Release Related Documentation Revision History Revision history details are not provided for features introduced before release Revision Details New behavior change in this release. Release Release Date April 27, 2017 Previous Behavior: Consider the following scenario: A path failure is detected by the egtp and a path failure event is queued. Any attempt to send a Create Session Request (CSR) to the SGW is unsuccessful. If the CSR is sent after a DNS response, the PDN connectivity is not rejected and the bearer context is not destroyed. On receiving Service Request, MME tries to fill tunnel information in S1 setup message and this leads to a crash. To prevent the crash a PDN connectivity reject must be sent to the UE. When a path failure event is queued, a PDN connectivity reject is not sent to the UE if a CSR is not sent to the SGW. New Behavior: A PDN connectivity reject is sent for additional PDN connectivity in the above mentioned scenario. Scaling of TAI-Objects and TAI Database Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Modified Functionality MME 6 Release Change Reference, StarOS Release

7 MME Changes in Release Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation ASR 5000, ASR 5500, VPC-SI Enabled CSCvb67565 MME Administration Guide Revision History Revision history details are not provided for features introduced before release Revision Details Feature enhancement related to TAI-DB and TAI-Objects. Release Release Date April 27, 2017 With this enhancement, the following changes are effected in this release: Maximum number of TAI-DBs supported in MME is increased from 4 to 32. Maximum number of TAI-Objects per TAI-DB is increased from 500 to Also, a system limit of is imposed on the number of TAI-Objects. The following optimizations are implemented as part of this feature: Dynamic memory allocation for TAI-Object in TAI-DB so that memory is occupied only for the actual number of TAI-Objects configured in TAI-DB. Optimize the TAI (mcc-mnc-tac) look-up so that the latency is reduced while configuring new TAI in TAI-Object. For example, assume it is allowed to have only 4 TAI-DBs each with 4000 TAI-Objects or 16 TAI-DBs each with 1000 TAI-Objects or any other combination TAI-Objects can be distributed across up to 32 TAI-DBs in any possible way (with up to 4000 TAI-Objects per TAI-DB). Once this system limit is reached, additional TAI-Object cannot be configured. However, if the number of TAI-DBs is less than 32, additional TAI-DB (up to 32) can be configured without any TAI-Object. These additional TAI-DBs can have all configuration (Custom TAI List, timezone, network-name) except for TAI-Object (tai-mgmt-obj). With TAI-Objects configured, the SCT memory usage is limited and the SCT does not go in warn state. Release Change Reference, StarOS Release 7

8 MME Changes in Release The time required for TAI-DB configuration is reduced significantly. If multiple TACs with same MCC and MNC need to be configured, configuring them in single line will further reduce the configuration latency. The configuration time depends on the total number of session managers. So, it varies for different ASR 5500 and VPC platforms. However, there is significant reduction in configuration time. The CLI commands show lte-policy tai-mgmt-db <db name> and show lte-policy tai-mgmt-db name <db name> tai-mgmt-obj name <obj_name> do not freeze even when large number of TAI-Objects are configured. Significant changes were done in CLI module to optimize TAI look-up. Scenario 1: Upon detecting any duplicate TAC Previous Behavior : The TAI configuration does not accept the duplicate TAC and stops configuring the remaining TAC values. New Behavior : The CLI console displays an error message and skips the duplicate TAC value. It further continues to configure the remaining TAC values. Scenario 2: On attempting to remove TAC which was not configured earlier or present in some custom TAI list Previous Behavior : The TAI configuration does not accept the TAC which is not present / present in some custom TAI list, and stops removing the remaining TAC values. New Behavior : The CLI console displays an error message and skips the TAC which is not present / present in some custom TAI list. It then continues to remove the remaining TAC values. If TACs with same mcc and mnc are configured in multiple lines, all such TACs will be displayed in single line in the output of " show lte-policy tai-mgmt-db name <db_name> " and " show lte-policy tai-mgmt-db name <db_name> tai-mgmt-obj name <obj-name> " CLI commands. Example: configure lte-policy tai-mgmt-db tmd1 tai-mgmt-obj tmo1 tai mcc 123 mnc 456 tac 100 tai mcc 123 mnc 456 tac 101 tai mcc 123 mnc 456 tac 102 end show lte-policy tai-mgmt-db name tmd1 tai-mgmt-obj name tmo1 TAI Management Object tmo1 TAI mcc 123 mnc 456 tac If TACs with same mcc and mnc are configured in multiple lines and the configuration is saved using save configuration <url> CLI command, the configuration of all TACs with same mcc and mnc will be saved in single line. This can be seen using the show configuration url <config_file_path> CLI command. 8 Release Change Reference, StarOS Release

9 MME Changes in Release Example: configure lte-policy tai-mgmt-db tmd1 tai-mgmt-obj tmo1 tai mcc 123 mnc 456 tac end The scenarios 1 and 2 are applicable only when multiple TACs with same mcc and mnc are configured in single line. Limitations The following are the current limitations of this feature: Maximum number of TAI-DBs supported is 32. Maximum number of TAI-Objects that can be configured per TAI-DB is However, there is a system limit of on total number of TAI-Objects. The total number of TAI-Objects across all 32 TAI-DBs is limited to Release Change Reference, StarOS Release 9

10 MME Changes in Release 10 Release Change Reference, StarOS Release