> LTE TAI Management Object Configuration Mode Commands
> The LTE TAI Management Object Configuration Mode is used to create and manage the LTE Tracking Area Identifiers for the TAI database.
> end
> Exits the current configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Use this command to return to the Exec mode.
> exit
> Exits the current mode and returns to the parent configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Use this command to return to the parent configuration mode.
> lai
> Configures a Location Area Identifier (LAI) for this TAI management object.
> Product
> MME
> Privilege
> Administrator
> Syntax
> lai mcc number mnc number lac area_code
> no lai
> no
> Removes a configured LAI from the TAI management object.
> mcc number
> Specifies the mobile country code (MCC) portion of a PLMN identifier as an integer from 100 through 999.
> mnc number
> Specifies the mobile network code (MNC) portion of a PLMN identifier as a 2- or 3-digit integer from 00 through 999.
> lac area_code
> Specifies the Location Area Code portion of the TAI as an integer from 1 through 65535.
> Usage
> Use this command to configure an LAI for this management object.
> Example
> The following command adds an LAI to this management object with an MCC of 111, an MNC of 22, and a LAC of 101:
> lai mcc 122 mnc 22 lac 101
> sgw-address
> Configures an IP address for a Serving Gateway (S-GW), a supported S5/S8 protocol type, and selection weight used in a pool for S-GW selection.
> Product
> MME
> Privilege
> Administrator
> Syntax
> sgw-address ipv4_or_ipv6_address s5-s8-protocol { both | gtp | pmip } weight number
> no sgw-address ipv4_or_ipv6_address s5-s8-protocol { both | gtp | pmip }
> no sgw-address ipv4_or_ipv6_address s5-s8-protocol { both | gtp | pmip }
> Removes the configured S-GW address from this TAI management object.
> ipv4_or_ipv6_address
> Specifies the IP address of the S-GW in the selection pool in IPv4 dotted-decimal or IPv6 colon-separated notation.
> Up to 32 S-GW addresses can be configured per TAI management object.
> s5-s8-protocol { both | gtp | pmip }
> Specifies the S5/S8 interface type found between the configured S-GW and the P-GW.
> both: Specifies that both the GTP and PMIP protocols are supported over the S5/S8 interface.
> gtp: Specifies that the GTP protocol is supported over the S5/S8 interface.
> pmip: Specifies that the PMIP protocol is supported over the S5/S8 interface.
> weight number
> Specifies the priority or weight of the S-GW address used during weighted round-robin selection within this TAI management object. number must be an integer from 1 through 100.
> Usage
> Use this command to configure a pool of S-GW addresses used for S-GW selection.
> Example
> The following command configures an S-GW with an IPv4 address of 10.2.3.4, a supported S5/S8 protocol type of GTP, and a selection weight of 3:
> sgw-address 10.2.3.4 s5-s8-protocol gtp weight 3
> tai
> Configures a Tracking Area Identifier (TAI) for this TAI management object.
> Product
> MME
> Privilege
> Administrator
> Syntax
> [ no ] tai mcc number mnc number { tac value } +
> no
> Removes a configured TAI from the TAI management object.
> mcc number
> Specifies the mobile country code (MCC) portion of a PLMN identifier as an integer from 100 through 999.
> mnc number
> Specifies the mobile network code (MNC) portion of a PLMN identifier as a 2- or 3-digit integer from 00 through 999.
> tac value +
> Specifies the Tracking Area Code portion of the TAI as an integer from 1 through 65535. Up to 16 TAC values can be entered on a single line.
> Usage
> Use this command to configure one or more TAIs for this management object. Up to 16 TAIs can be configured per management object.
> Example
> The following command adds a TAI to this management object with an MCC of 111, an MNC of 22, and a TAC value of 1001:
> tai mcc 122 mnc 22 tac 1001
> timezone
> Configures the timezone to be used for the UE timezone in S11 and Non-Access Stratum (NAS) messages.
> Product
> MME
> Privilege
> Administrator
> Syntax
> timezone { + | - } hours value [ minutes { 0 | 15 | 30 | 45 } ]
> no timezone
> Removes the timezone configuration from the management object.
> + | -
> Specifies the offset direction from Coordinated Universal Time (UTC).
> hours value
> Specifies the offset from UTC in hours as an integer from 0 through 14.
> minutes { 0 | 15 | 30 | 45 }
> Optionally specifies the offset minutes added to the hours value.
> Usage
> Use this command to configure the time one to be used for the UE timezone in S11 and NAS messages.
> Important: Time zone configurations at the TAI Management Object level take precedence over time zone configurations at the TAI Management Database level. If neither is configured, the system defaults to the MME time zone.
> Example
> The following command sets the time zone mapping for this management object to plus-3 hours and 15 minutes from UTC:
> timezone + hours 3 minutes 15
> zone-code
> Configures a zone code for the management object.
> Product
> MME
> Privilege
> Administrator
> Syntax
> zone-code zc_id
> no zone-code
> no
> Removes the configured zone-code from the management object.
> zc_id
> Identifies the zone code configuration instance as an integer from 1 through 65535.
> Usage
> Important: While there is no limit to the number of zone codes that can be created, only 10 LACs per zone code can be defined.
> Use this command to define zone code restrictions. Regional subscription data at the home subscriber service (HSS) is used to determine the regional subscription area in which the subscriber is allowed to roam. The regional subscription data consists of a list of zone codes which are comprised of one or more location areas (identified by a LAC) into which the subscriber is allowed to roam. Regional subscription data, if present in the Insert-Subscriber-Data-Request (IDR) and the Update-Location-Answer (ULA) from the HSS, defines the subscriber's subscription area for the addressed MME. It contains the complete list (up to 10 zone codes) that apply to a subscriber in the currently visited PLMN. During the Location Update procedure, the zone code list is received in the ULA from the HSS. The zone code list is validated against the configured values in this command. If matched, the Location Update procedure is allowed to proceed. If not matched, the response is that the Network Node Area is restricted and the Location Update procedure fails.
> Example
> The following command sets the zone code for this management object to 1:
> zone-code 1

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883