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 4000. Also, a system limit
of 16000 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. 16000 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 16000
TAI-Objects configured, the SCT memory usage is limited and the SCT does not go
in warn state.
-
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.
Important:
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 100 101 102
-
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.
Example:
configure
lte-policy
tai-mgmt-db tmd1
tai-mgmt-obj tmo1
tai mcc 123 mnc 456 tac 100 101 102
end
The scenarios 1
and 2 are applicable only when multiple TACs with same mcc and mnc are
configured in single line.
Feedback