Scribd
Upload
153 views3 pages

Location Update Scenario

The document describes location update scenarios for an HLR database. It provides instructions for marking GT ranges as blocked or allowed, setting BAOC, and enabling or disabling Camel trigger capabilities using database tables. Expected results are described for different configurations, such as the HLR rejecting or accepting updates with causes like PLMN not allowed or BAOC. Tables like VLR_WHITELIST, VLR_BLACKLIST, IMSI_Acceptance and ocsi_plmn are used to configure these settings.

Uploaded by

masanjaya
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
153 views3 pages

Location Update Scenario

The document describes location update scenarios for an HLR database. It provides instructions for marking GT ranges as blocked or allowed, setting BAOC, and enabling or disabling Camel trigger capabilities using database tables. Expected results are described for different configurations, such as the HLR rejecting or accepting updates with causes like PLMN not allowed or BAOC. Tables like VLR_WHITELIST, VLR_BLACKLIST, IMSI_Acceptance and ocsi_plmn are used to configure these settings.

Uploaded by

masanjaya
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

/* log. 20120713 : first creation. */ Location update scenario : number 1.

HLRDB Setting GT range is marked as blocked GT range is marked as BAOC VLR Camel Capable Either yes or no Either yes or no Expected Result HLR rejects UL with cause PLMN not allowed HLR accepts UL with BAOC Customer tries to unblock BAOC --> rejects HLR accepts UL with Camel trigger HLR accepts UL with BAOC Customer tries to unblock BAOC --> rejects

2.

3. 4.

GT as GT as

is marked open is marked open

Yes No

I.

GT range is marked as blocked. To set GT range as blocked or not , its in table vlr_whitelist and vlr_blacklist in hlrdb. To set blocked, remove any vlr prefix from table VLR_WHITELIST and add vlr prefix into table VLR_BLACKLIST. To set open , add vlr prefix into table VLR_WHITELIST. The priority of VLR_WHITELIST is HIGHER than VLR_BLACKLIST. If theres same vlr prefix in both table, the rules-to-obey will base on tabel VLR_WHITELIST Table VLR_WHITELIST and VLR_BLACKLIST consist of column : VLR_number whitelist_reason imsi_prefix prefix of vlr number reason or name of operators vlr prefix of specific imsi.

To set reject value , fill table IMSI_Acceptance. Columns of table IMSI_ACCEPTANCE are : Column IMSIPrefix Column VLRPrefix Column user_error_id : prefix of IMSI : prefix of vlr number : error id of MAP standards User-Error, the value is usually 8 for MAPUE_ROAMING_NOT_ALLOWED. Another value to set is 1 (unknown subscriber) and 34 (system failure). the complete list is :

MAPUE_UNKNOWN_SUBSCRIBER = 1, MAPUE_UNIDENTIFIED_SUBSCRIBER = 5, MAPUE_ABSENT_SUBSCRIBER_SM = 6, MAPUE_ROAMING_NOT_ALLOWED = 8, MAPUE_ILLEGAL_SUBSCRIBER = 9, MAPUE_BEARER_SERVICE_NOT_PROVISIONED = 10, MAPUE_TELESERVICE_NOT_PROVISIONED = 11, MAPUE_ILLEGAL_EQUIPMENT = 12, MAPUE_CALL_BARRED = 13, MAPUE_ILLEGAL_SS_OPERATION = 16, MAPUE_SS_ERRORSTATUS = 17, MAPUE_SS_NOT_AVAILABLE = 18, MAPUE_SS_SUBSCRIPTION_VIOLATION = 19, MAPUE_SS_INCOMPATIBILITY = 20, MAPUE_FACILITY_NOT_SUPPORTED = 21, MAPUE_PW_REGISTRATION_FAILURE = 23, MAPUE_ABSENT_SUBSCRIBER = 27, MAPUE_SUBSCRIBER_BUSY_FOR_MT_SMS = 31, MAPUE_SM_DELIVERY_FAILURE = 32, MAPUE_MESSAGE_WAITING_LIST_FULL = 33, MAPUE_SYSTEM_FAILURE = 34, MAPUE_DATA_MISSING = 35, MAPUE_UNEXPECTED_DATA_VALUE = 36, MAPUE_RESOURCE_LIMITATION = 37, MAPUE_NEGATIVE_PW_CHECK = 38, MAPUE_NUMBER_OF_PW_ATTEMPTS_VIOLATION = 43, MAPUE_OR_NOT_ALLOWED = 48, MAPUE_ATI_NOT_ALLOWED = 49, MAPUE_ATSI_NOT_ALLOWED = 60, MAPUE_INFORMATION_NOT_AVAILABLE = 62, MAPUE_UNKNOWN_ALPHABET = 71, MAPUE_USSD_BUSY = 72 Column roam_not_allow_cause : reason-cause id of MAP standard why roaming is not allowed. The value is between 0 (plmn Roaming Not Allowed) and 1 (operator determined barring). The usual value is 0 (plmn roaming not allowed)

Examples of inserting into table : Insert into imsi_Acceptance values ( 20408 , 91984 , 8 , 0 );

II.

GT range is marked as BAOC, with or without camel capability insert a row in table ocsi_plmn. To set BAOC , set column FALLBACKOPTION with value 1.

III.

GT range is marked as open, with camel capability insert a row in table ocsi_plmn. To set no BAOC , set column FALLBACKOPTION with value 0. GT range is marked as open, with no camel capability remove the row with vlr prefix (GT) from the table ocsi_plmn.

IV.

The current setting checking step is : 1. Checking whether the VLR prefix is blocked or not. (table vlr_whitelist and vlr_blacklist) 2. Checking BAOC condition, is the column fallbackoption in table ocsi_plmn is 0 or 1. 3. Checking camel capability, is the vlr prefix exist in table ocsi_plmn or not. From step #2 , if vlr prefix is not exist in table ocsi_plmn , then it will be automatically set as BAOC and no camel support.

You might also like