In release 21.1,
the CLI command to configure zone code under a TAI-Object is extended to
configure multiple zone code values under the same TAI-Object. A maximum of 10
zone codes is configurable under each TAI-Object.
During the
configuration, the operator should be mindful of the following:
-
Zone codes can
be configured as single zone code per configuration line or multiple zone codes
per configuration line. It is recommended to enter multiple zone codes per
configuration line to reduce the configuration load time.
-
Duplicate zone
codes are not allowed under the same TAI-Object. However, duplicate zone code
can be configured in a different TAI-Object.
-
If multiple
zone codes are entered in a single line configuration - duplicate zone codes
and unique zone codes, only the duplicate zone codes will be rejected whereas
the unique zone codes are accepted.
-
If number of
zone codes entered in single configuration line is greater than 10, then only
10 minus the initial configured zone codes will be accepted and configured.
-
During the
configuration, if all the 10 slots are configured, the extra configured zone
code values are rejected with a suitable error.
-
If the zone
codes are configured when the subscribers are already attached, the currently
attached subscribers are not detached. Changes to the mapping of TAI to Zone
codes affect the processing of any incoming messages. So, if the mapping of TAI
to zone codes is changed after an initial attach, the next TAU message zone
code validation with a HSS/call-control-profile is processed with the newly
updated zone code configuration. The initial attach message for new subscribers
uses the updated zone code configuration.
The session
manager instance, as displayed in the log, must be reloaded to push the correct
configuration to the respective session manager after session manager recovery.
This will ensure that the configuration in the session manager and the SCT are
in sync.
Use the following
CLI commands to enable Access Restriction based on Regional Zone Codes:
configure
lte-policy
tai-mgmt-db database_name
tai-mgmt-obj object_name
[ no ] zone-code zonecode_value [ zonecode_value2 [...[ zonecode_value10 ] ] ]
end
Notes:
-
The
zone-code
command configures zone code values under a TAI object. In release 21.1, the
number of zone codes values configurable in a single line configuration is
extended to 10 values under a TAI-list. For example, zone-code 10 11 12 13 14 15
16 17 18 19
-
By default, the
zone-code
command is not enabled.
-
The
no
zone-code
<zonecode_value2>…<zonecode_value10>, removes
the selected zone code values entered from the TAI-list. For example, in the
following configuration:
no zone-code
10 11 12, only the zone code value 10 11 12 is removed from the existing
TAI-list, whereas the other zone code values remain configured in the TAI-list.
Example
Configuration
The following is an
example configuration to allow access to TAIs for PLMN with a specific value of
mcc/mnc, and a configuration to restrict access to specific TAI values for a
different PLMN.
config
operator-policy name Partner-1-policy
associate call-control-profile CCP1
#exit
operator-policy name Partner-2-policy
associate call-control-profile CCP2
#exit
lte-policy
subscriber-map sm1
precedence 100 match-criteria imsi mcc 111 mnc 222 operator-policy-name Partner-1-policy
precedence 101 match-criteria imsi mcc 111 mnc 333 operator-policy-name Partner-2-policy
exit
tai-mgmt-db TMD
tai-mgmt-obj OBJ1
zone-code 11 21
tai mcc 123 mnc 456 tac 1234
tai mcc 123 mnc 456 tac 1235
tai mcc 123 mnc 456 tac 1236
tai mcc 123 mnc 456 tac 1237
#exit
tai-mgmt-obj OBJ2
zone-code 12
tai mcc 123 mnc 456 tac 2234
tai mcc 123 mnc 456 tac 2235
tai mcc 123 mnc 456 tac 2236
#exit
tai-mgmt-obj OBJ3
zone-code 13 22
tai mcc 321 mnc 456 tac 1244
tai mcc 321 mnc 456 tac 1245
tai mcc 321 mnc 456 tac 1248
tai mcc 321 mnc 456 tac 1249
#exit
tai-mgmt-obj OBJ4
zone-code 23
tai mcc 321 mnc 456 tac 2244
tai mcc 321 mnc 456 tac 2245
tai mcc 321 mnc 456 tac 2247
tai mcc 321 mnc 456 tac 2248
#exit
#exit
#exit
call-control-profile CCP1
lte-zone-code allow zone-code-list 11 12 13
associate tai-mgmt-db TMD
#exit
call-control-profile CCP2
lte-zone-code restrict zone-code-list 21 22 23
associate tai-mgmt-db TMD
#exit
end
Configuration
Description
In the above
configurations, UEs are mapped to separate zone code numbers. Each zone code
can be associated to TAIs independent of each other.
From the example above, for
“allow” access:
UEs from PLMN –
with mcc = 111 and mnc = 222, operator policy = Partner-1-policy and
call-control-profile = CCP1 applies. With reference to CCP1, zone codes 11, 12
and 13 are allowed from the associated tai-mgmt-db = TMD. UEs from this PLMN
will be allowed with access to TAI values in tai-mgmt-obj = OBJ1, OBJ3 and OBJ2
(For example,
tai mcc 123 mnc
456 tac 1234).
From the above example, for
“restrict” access:
UEs from PLMN –
with mcc = 111 and mnc = 333, operator policy = Partner-2-policy and
call-control-profile = CCP2 applies. With reference to CCP2, zone codes 11, 12
and 13 are restricted from the associated tai-mgmt-db = TMD. UEs from this PLMN
will be restricted from access to TAI values in tai-mgmt-obj = OBJ1, OBJ3 and
OBJ2 (For example,
tai mcc 123 mnc
456 tac 1234).
Feedback