4.2.23 Auxiliary Table Configuration
I. Description
Auxiliary tables are the supplement for main tables. In some special cases, if the information in main tables cannot meet the requirements, auxiliary tables can help to do number analysis so as to enhance number analysis capability.
The correspondence between the main and auxiliary tables in the system is listed below:
Table 4-1 Mapping between the main and auxiliary tables
II. Example
In an MSC, it is required that: 1) if the subscriber does not have a SIM with it and makes a emergency call, Only sending tone to the subscriber is needed. 2) If the subscriber has a SIM with it, connecting to the emergency center is needed
- Configurations in case 1
1) Set the corresponding software parameters as "dialing 112 without SIM allowed" (Set bit3 of ISUP test parameter 2 as 1).
2) System processing procedures: The system sets the caller number as MSC number. When recording the caller number since no caller number is available due to the reason that the subscriber does not have a SIM. From the call source and the caller number being MSC number, the system can judge that the call is a local call without SIM, so "Only announce" is conFigured in the [DN Pre-analysis Table].
The caller number have to be added for analysis with the information in [DN Pre-analysis] and [Caller Info for DN Pre-analysis] during the number pre-analysis. According to the value "0" in "Caller info indicator" in the table [DN Pre-analysis], it can be observed that the caller number is a local MSC number (The country code has been removed when the caller number is recorded.) in the table [Caller Info for DN Pre-analysis]. Therefore set send tone to the subscriber" for the call.
Data configurations are as follows:
Figure 4-60 [DN Pre-analysis] table configuration
Figure 4-61 [Caller Info for DN Pre-analysis] table configuration
Note: 90185195 is the local MSC number. Meanings of the above configurations are: if the caller number is 90185195 and the called is 112, send tone to the subscriber but do not put the call through. If a caller number rather than 90185195 dials 112, no action is needed to do in this table, referring to configuration in case 2).
To use the auxiliary table, first conFigure a valid "Caller info indicator" in the main table. 255 or blank in the field means that it is unnecessary to query the auxiliary table.
In addition, note that the contents of the operation fields (excluding blue fields in the tables) in the main and auxiliary tables are completely the same. Configuration principles: If the auxiliary table is not used, contents in the auxiliary table need not be conFigured. If "Caller info indicator" in the main table is valid, it is recommended not to conFigure the contents of the operation fields in the main table, instead, conFigure them in the auxiliary table.
- Configuration in case 2
For call with SIM, the number processing is implemented in a table different form the one for the case without a SIM card. For the call with a SIM card, number conversion is implemented according to the "call source code" in [Number Prefix Process] table. For the detailed configuration method, please refer to TP-008.
4.2.24 Use of Subscriber Category
I. Description
Numbers of the same type can be included into one category to reduce the data volume in tables [DN Pre-analysis], [CLI Presentation], [Outgoing Trunk Number Format] and [Other Number Format] table.
Before querying [DN Pre-analysis], [CLI Presentation], [Outgoing Trunk Number Format] and [Other Number Format], the subscriber category can be obtained from the table [Called Number Analysis] as an input.
II. Example
1) Implement call barring function in the [Number Pre-analysis] table.
Figure 4-62 Call between MSC1 and MSC2
Suppose roaming is permitted for subscribers of MSC1 and MSC2 in both networks. When a MSC2 subscriber roams to MSC1 and dials a PSTN number, which is routed to MSC2, MSC2 will connect the call to PSTN. Whereas if a MSC1 subscriber also dials a PSTN number, and the call is routed to MSC2, MSC2 will clear the call.
Configurations of the table [Called Number Analysis] are shown below:
Figure 4-63 [Called Number Analysis] table configuration
The subscriber category for local fixed calls is conFigured as "Local PSTN", and MSC1 subscriber is conFigured as "PLMN other net", MSC2 subscriber is conFigured as "PLMN local".
Configurations of the table [DN Pre-analysis] are shown below:
Figure 4-64 [DN Pre-analysis] table configuration
In this table, not all number segments of the local PSTN number are required to be conFigured, just conFigure the "Called subscriber category" as "Local PSTN". Because it is required to be associated with the caller, the "Caller info indicator" should be set as 0.
Configurations of the table [Caller Info for DN Pre-analysis] are shown below:
Figure 4-65 [Caller Info for DN Pre-analysis] configuration
In this table, not all MSC1 number segments are required to be conFigured, just conFigure the "Called subscriber category" as "PLMN other net" for failure processing. Likewise, not all MSC2 number segments are required to be conFigured, conFigure the "Called subscriber category" as "PLMN local" without failure processing.
2) Processing of other tables
The subscriber category item is also included in tables [CLI Presentation], [Outgoing Trunk Number Format] and [Other Number Format], its configuration method is the same as in the table [DN Pre-analysis].
4.2.25 Use of Destination Code for Call
I. Description
The purpose for adding [Destination Code for Call] is added in the [Called Number Analysis] Table so that:
Different called numbers can be divided into different groups by "Destination code for call", thus saving effort for configuring different called numbers in the [Outgoing Number Format] table.
"Destination code for call" is defined in the table [Called Number Analysis], and the destination code can be used as an index in the table [Outgoing Number Process] for the above purpose.
II. Example
Processing of scattered numbers
It is required that the local PSTN number sent out should be converted into national number format. And 654,653,651and 693 are the prefixes of the local PSTN number.
Figure 4-66 [Called Number Analysis] table configuration
In the table above, the "Destination code for call" of the local fixed number is set as 2.
Figure 4-67 [Outgoing Trunk Number Format] table configuration
ConFigure only one record in the above table. Specify the local PSTN number as the national number, thus no scattered called numbers are to be conFigured in the [Outgoing Trunk Number Format] table.
4.2.26 Playing Forwarding Tone
I. Description
When subscriber A dials subscriber B, and B forwards this call, an announcement will be played to notify subscriber A of the forwarding so that he can determine whether he would like to proceed with the call.
ConFigure the [Send Tone Method] in [DN Pre-analysis] table as "connect after announce", then the forwarding call will be continue after the forwarding tone is sent. .
II. Example
1) Send forwarding announcement tone after forwarding a call to the voice mailbox
Figure 4-68 [DN Pre-analysis] table configuration
To make it simple, key fields in the [DN Pre-analysis] table for explanation, while other fields are conFigured by default.
Suppose that the voice mailbox number is "139139139" and the call source is "Call Forward Side", in this case the forwarding occurs at the local MSC, "Send tone method" is set as "connect after announce", while "Tone ID" indicates and the send tone timeslot.
Note:
If the above table is conFigured by default, the caller can hear the forwarding announcement tone at MS side. If the caller is a subscriber of other MSC, software parameters should be set as well.
2) Send announcement for all forwarding
To send announcements for all forwarding, use the wildcard character to conFigure the called numbers.
4.2.27 Inter-MSC Call Barring
I. Description
Figure 4-69 Networking diagram
Suppose roaming is permitted for subscribers of MSC1 and MSC2 in both networks. When a MSC2 subscriber roams to MSC1 and dials a PSTN number, which is routed to MSC2, MSC2 will connect the call to PSTN. Whereas if a MSC1 subscriber also dials a PSTN number, and the call is routed to MSC2, MSC2 will clear the call.
By configuring [DN Pre-analysis] table, set the status calls that are not intended to be connected as failure.
II. Example
Configurations are shown below:
Figure 4-70 [DN Pre-analysis] table configuration
In the table [DN Pre-analysis], set the called number as a PSTN number, since the call barring function is associated with the caller, the [Caller Info Indicator] should be set as 0.
Figure 4-71 [Caller Info for DN Pre-analysis]
If the caller number is the access code of MSC1 (e.g., 135 ~ 139), set the "Failure process flag" as Yes, "Failure reason code" as "Limited call". Otherwise, no processing will be implemented for MSC2 subscribers (e.g., 130).
4.2.28 ODB (Operator Defined Barring)
I. Description
Flexible configuration of the ODB1~4 is done through the [Called Number Analysis] table and [Call Barring Service] table. Whether or not the subscriber supports the ODB services can be known by querying [Called Number Analysis] table and [Call Barring Service] table. If ODB services are supported (i.e. the corresponding flag in the [Call Barring Service] table is checked), the ODB applies to all the calling subscribers subscribed to the service.
The functions realized include but not limited to: national toll call barring, barring of outgoing calls except those to specified numbers, outgoing calls allowed except those to specified numbers.
Whether the subscriber enjoys ODB_PLMN2, ODB_PLMN3 and ODB_PLMN4 should be set in HLR. Which kind of ODB is applied is realized by the MSC.
Which type of calls to be barred ODB_PLMNx (x = 1, 2, 3, 4) is user-defined. The principle is that the ODB_PLMNx is correlated with the called number, so the call barring takes place if the subscriber dialing this number has subscribed to the ODB_PLMNx.
Which calls to be barred depends on the correlation between the ODB_PLMNx and the called number. The correlation is realized through the settings of "Call barring service index" in the [Called Number Analysis] table.
Assume that the ODB_PLMN3 is defined as barring of outgoing international toll calls for the subscriber who has subscribed to it. Any calling subscriber subscribed to ODB_PLMN3 service would be barred when dialing an international called prefix, if the "Call barring service index" of the international called prefix in the [Called Number Analysis] table is set as certain value (e.g. 3. "3" should be checked for the ODB_PLMN3 in the [Call Barring Service] table). The user-defined feature of the ODB_PLMNx service is realized through the user-defined correlation between ODB_PLMNx and the called subscriber.
In addition, configuration of [MAP Configuration] table is needed to provide the user-defined feature of the ODB, indicating that the MSC supports this function.
II. Example
Case 1:
An office requests that ODB_PLMN2 be defined as CIS barring, ODB_PLMN3 as international call barring, and ODB_PLMN4 as national toll call barring.
810373XXXXXXX is the CIS number prefix, 8362 the national toll PSTN number prefix and 81086 the national prefix of China (China is taken as the example here).
The data configuration should be made as shown in Figure 4-72.
Figure 4-72 Configuring the called number analysis table
The configuration of "Service index=2" is shown in Figure 4-73, indicating that the call will be restricted when any subscriber subscribed to the ODB_PLMN2 service dials the CIS number with the prefix of 810373.
Figure 4-73 Configuring call barring service table
The configuration of "Service index=3" is shown in Figure 4-74, indicating the call will be restricted when any subscriber subscribed to the ODB_PLMN3 service dials the international number with the prefix of 81086.
Figure 4-74 Configuring call barring service table
The configuration of "Service index=4" is shown in Figure 4-75 indicating the call will be restricted when any subscriber subscribed to the ODB_PLMN4 service dials the national toll number with the prefix of 8361.
Figure 4-75 Configuring call barring service table
For the configuration of "Service index" for numbers other than the above CIS numbers, international numbers and national toll numbers, refer to Figure 4-76. It indicates that any subscriber subscribed to ODB_PLMN2, ODB_PLMN3 or ODB_PLMN4 service will not be restricted when dialing other numbers except CIS numbers, international numbers and national toll numbers.
Figure 4-76 Configuring call barring service table
The MAP Configuration Table also should be conFigured. Checking an item indicates that this item will be supported by the MSC, as shown in Figure 4-77.
Figure 4-77 Configuring MAP configuration table
Case 2:
An office requests that a subscriber who has subscribed to the ODB_PLMN4 service not be able to call numbers other than "+7-902-185XXXX".
The data should be conFigured as shown in Figure 4-78.
Figure 4-78 Configuring the call barring service table
The configuration of "Service index=1" is shown in Figure 4-79, indicating that a subscriber having subscribed to the ODB_PLMN4 service will not be restricted when dialing any number with the prefix of 902185.
Figure 4-79 Configuring the call barring service table
For the configuration of "Service index" for numbers except those with the prefix of 902185, refer to Figure 4-80. It indicates that any subscriber having subscribed to the ODB_PLMN4 service will be restricted when dialing the numbers except those with the prefix of 902185.
Figure 4-80 Configuring the call barring service table
In addition, the MAP Configuration Table should be conFigured. Checking an item indicates that this item will be supported by the MSC. The configuration is shown in Figure 4-81.
Figure 4-81 Configuring the MAP Configuration Table
4.2.29 Defaulting Subscribers Make Calls
I. Description
[Call Barring Service] table can be used to implement this service. For example, a subscriber has BAOC and ODB_BAOC services, but dialing 1860 is allowed. That is, when he dials 1860, BAOC and ODB_BAOC is not applicable.
Configuration method:
ConFigure the called prefix as 1860 in the [Called Number Analysis] table, and then conFigure an index to "Call barring service index" in "Call barring service", e.g. 1. Do not select services BAOC and ODB_BAOC in "Call barring service", which indicates that even if a calling subscriber has these two services, they will not be implemented.
II. Example
[Called Number Analysis] table is conFigured as the following:
Figure 4-82 Configuring [Called Number Analysis] table
[Call Barring Service] table is conFigured as the following:
Figure 4-83 Configuring [Call Barring Service] table
4.2.30 Outgoing by Overlay according to MSISDN Number Segment
I. Description
Overlay is used for the local MSC when it is a VMSC without SSP function. When the caller or called party is a prepaid subscriber (PPS), the called number will be added with a prepaid flag (prefix), which indicates that the number should be processed in SSP. The precondition of this intelligent calling mode is that the operator uses the number segment to specify which subscribes are intelligent ones. Thus, via MSISDN number segment, VMSC can identify intelligent subscribers.
If both caller and called are PPS, the caller enjoys higher priority.
To trigger the Overlay function, some MSC parameters should be set:
1) funcctrl.dbf table (Remarks: under the directory \omc\msc\bam\dbf, not visible in data management console).
For the Overlay service, the value is 0000006020900000, i.e. the corresponding locations must be 6, 2, and 9.
2) Software parameter settings: bit 11 and bit 10 of "call internal parameter 3" should be set as 00 or 01, and bit 15~bit 12 of "call internal parameter 4" = 1001.
Overlay service flow is described as the following:
1) The caller is an Overlay intelligent subscriber
During the subscriber location update, the table [Prepaid User Number Segment] is queried to check whether the subscriber is a prepaid subscriber, and this flag is stored in VLR.
Query procedures:
With LAI or GCI number carried during location update, query the table [LAI and GCI] to get "call source code".
With "call source code", query the table [Call Source] to get the "intelligent code area index".
Using the "intelligent code area index" and this subscriber’s MSISDN, query the table [Prepaid User Number Segment].
Successful query indicates that the subscriber is the Overlay intelligent subscriber, otherwise, it is not.
"Intelligent code area index" is set for areas using the same MSC to distinguish the callers from different call sources. The area code prefixes added in front of the called numbers are also different.
When PPS caller originates calls, the [Prepaid User Number Segment] table will be queried again and the related natures can be obtained. Then Overlay flag will be
added before the called number. Then, after routing, caller and called numbers will be processed by SSP.
Therefore, configuring the table [Prepaid User Number Segment] plays two roles when the caller is an Overlay intelligent subscriber. One is to recognize whether the caller is an Overlay intelligent subscriber, and to be used during location update. The other is to add a prefix in front of the called number during calling, and to make an outgoing call.
2) The called is an Overlay intelligent subscriber
For the called and caller subscribers, the recognition mechanisms of Overlay intelligent subscriber are different. For the latter, it is conFigured through the table [Prepaid User Number Segment], and the flag is stored in VLR. For the former, it is done through configuring the field "Called number category" of the related called number as "prepaid subscriber" in the table [Called Number Analysis].
During calling, similar to the case when the caller is a prepaid subscriber, the [Prepaid User Number Segment] table is also queried, with a prefix added to the called number. And the outgoing route to SSP can be selected.
Therefore, if the caller is an Overlay intelligent subscriber, the following tables should be conFigured [LAI and GCI], [Call Source], [Prepaid User Number Segment] and [Number Change] should be conFigured.
If the called is an Overlay intelligent subscriber, the tables [LAI and GCI], [Call Source], [Called Number Analysis], [Prepaid User Number Segment] and [Number Change] should be conFigured. MSISDN of prepaid subscribers should be conFigured at two tables: one is the table [Prepaid User Number Segment], and the other is the table [Called Number Analysis]. The former is for the case that both caller and called are prepaid subscribers, and the latter is for the case that only the called is a prepaid subscriber.
II. Example
Requirements for Overlay intelligent calls in an MSC:
For PPS calls, add the prefix ‘8B0101’ to the called number for outgoing via overlay. But when a common subscriber calls a PPS, the specified E1 must be selected.
Solutions: When a PPS calls a PPS, use the table [Prepaid Use Number Segment] for routing. When a common subscriber calls a PPS, do not use the table [Prepaid User Number Segment] for routing, and conFigure tables as the following:
1) ConFigure the Overlay number segment in the table [Called Number Analysis], and then conFigure the number category as "unknown" or "PSTN" (it cannot be conFigured as MSISDN or prepaid number).
2) Process the number prefix. Change the called number in the table [Number Prefix Process], and add the prefix 8B0101 for direct routing.
