Number Analysis [Huawei version] Posted: September 24, 2010 in Telecommunication
0 1. MOBILE CALLER
DNSRVIDX
When HLR returns forwarding number or SCP forwards, they will query user attribute table and caller attribute processing table
CLICRTANA
CLICRTPRO
NONDCDIALANA
Check for NDC in the called party number. If there is no NDC, then automatically add the NDC number according to NONDCDIALANA
CLDPREANA
Query this table for the called party number and the called party number / original called party number / redirecting number from CAP interface after mobile initial forwarding
IMSIBITANA
Query this table according to calling IMSI when mobile originated and query this table according to called IMSI after forwarding According to IMSI of calling users,
This table is used to make processing of numbers (such as changing numbers, chaning routing source codes, and so on) according to IMSI of calling users.
2. PSTN CALLER
TG
The input condition is the trunk group number. The output condition is the trunk group attribute and other attributes of a call, such as whether there is need of c alling party numbers and original party numbers, whether connection can be made without these numbers, and so on. The call barring group is included.
CLRDSG
You can use the call barring group number, calling party number and calling party number attribute (national, international, user, and unknown) to query CLRDSG to bar calls.
(1) Direct call barring (select Reject call). Using this function, you can bar calls entering the trunk group and the office.
(2) Call barring with caller number discrimination (select Caller Number Discrimination). With this function, calls are barred if caller numbers are not in the number length scope configured in this table.
CLDPREANA
This table is used to change the called party number before number analysis for the sake of
later number analysis.
A. Process the changing of particular numbers in condition of intelligence, roaming number
and forwarding. For example, the retrieval of MSRN and forwarding number from MAP
generally adopt international format such as CC+NDC (or AREA CODE)+SN. But sometimes
the format is not standard, such as without CC, so this table is used to add the country code.
B. Avoid using function of changing incoming numbers.
C. Avoid using call barring function of this table.
D. Avoid using this table to change the PSTN incoming numbers, use INNUMPREPRO.
3. INCOMING NUMBER PROCESSING
The purpose of incoming number pretreatment data configuration is to normalize called numbers of incoming calls from trunks and MO calls, MSRNs or forwarded -to numbers transmitted by MAP signaling, and called numbers changed in IN procedure. The format of input numbers can meet the relevant internal specifications of the MSOFTX so as to facilitate the unified number analysis of the system.
INNUMPREPRO
Start point of number reanalysis (after HLR returns roaming number / forwarding number or SCP forwarding / changing number, then the number analysis start again from here
INCLRIDX
These tables are used to change numbers according to called party numbers/calling party number/original party number. If an incoming number cannot meet demand of the Analysis Table of Called, you can use the INNUMPREPRO to change the number. It can also be used to identify particular calls and make particular processings to these particular calls.
INORICLDIDX
4. CALLED NUMBER ANALYSIS
CNACLD
The called prefix is the center of number analysis. The number analysis can judge a call (mobile local office call, delivery of paging, or outgoing routing processing). By the number analysis, you can trigger the intelligence and announcement.
MSOFTX3000 makes different processing of analysis and routing according to called number types in CNACLD Table: If it is MSISDN, then MSOFTX fetches roaming numbers according to called numbers. Then the fetched roaming number or the forwarding number is used by MSOFTX as prefix of calls from MAP to make the number analysis. If it is MSRN and the service attribute is not mobile local office,
called number PSTN or unknown number, then the outgoing routing process starts. According to the routing code and routing source code got through analysis, the query process is initiated to the database to find an outgoing circuit. If it is MSRN and the service attribute is mobile local office or a handover number, then the query process is initiated to VDB. The routing process starts and the paging is initiated to mobiles users.
Query CNACLD according to DN set and B number. The number type and call type are analyzed, and following processing is based on these two t ypes. A series of flags will be returned, including the flags of enhance route, particular processing of calling party number, particular processing of prefix, and so on. After check these flags, the calls are processed, namely analysis of the call type according to number analysis.
SUPERRT
By query SUPERRT, you can change routing codes according to different calltypes such as different forwarding, so as to realize make different calls go to different routes.
CALLPRICHK
The table is used to check dialing of numbers, for example to disconnect some numbers dialed by users and play the announcement of Unallocated Number. You can use dialing call barring function in this table, but do not use CLD PREANA or the INNUMPREPRO. In addition, this table can realize the call barring with discrimination of different call types.
SRVCHK
Check whether a calling subscriber is authorized to make the corresponding calls. You
can set the service check type, check mode, and conversation duration restriction. The below functions can be realized, depending on the combination of Check Type and Check Mode:
1.Check relative services in the original mode.
2.Relative services are not checked. (If the service is ODB_BAOC, calls still can be made.)
3.If a user has the attribute, then calls will be disconnected.
4.If a user has not the attribute, then calls will be disconnected.
CLICRTPRO
Query the Caller Feature Table CLICRTANA. If the query fails, then query the Caller Number Analysis Table CNACLR.
CLICRTANA
CNACLR
Help to normalize the calling numbers of incoming calls from trunks, or to conduct various processing over different calling parties who dial the same call prefix (for
example, to select different routes according to calling features). Calling number analysis is used to process information such as calling numbers. Calling subscriber attribute analysis is used for special processing when the caller has some special service attributes (for example,
whether the subscriber has subscribed to forwarding and service barring services). Calling subscriber attribute processing is used to map a subscriber_s special service attributes respectively to a series of calling feature index. This index corresponds to the calling feature index in the calling feature analysis table. The MSOFTX3000 searches the calling feature analysis table through this index and performs special follow-up processing of calls in the call subscriber attribute analysis.
PFXPRO
IF GO TO:
1. PSTN or MSRN Other Office
OUTNUMPREPRO
In the MSOFTX3000 system, if the called number is found to be PSTN, the outgoing number is pre-processed and then sent to the peer office. At this stage, the system orderly queries OUTNUMPREPRO, OUTCLRIDX, and OUTORICLDIDX, and decides the change of the caller number, called number, and original called number.
OUTCLRIDX
Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers, making the format of the outgoing number conformant with inter-office number transfer specifications
OUTORICLDIDX
OUTCLRIDX is used to convert the transmitted calling/called numbers and original called numbers or re-designate their formats according to calling number prefixes and their related
attributes. OUTORICLDIDX is used to convert calling/called numbers and original called numbers or re-designate their formats according to original called prefixes and their
related attributes. OUTNUMPREPRO data are used to convert calling/called numbers and original called numbers or re-designate their formats according to call sources, outgoing trunks, called prefixes and related attributes.
RTANA
1. MOBILE CALLER
DNSRVIDX
When HLR returns forwarding number or SCP forwards, they will query user attribute table and caller attribute processing table
CLICRTANA
CLICRTPRO
NONDCDIALANA
Check for NDC in the called party number. If there is no NDC, then automatically add the NDC number according to NONDCDIALANA
CLDPREANA
Query this table for the called party number and the called party number / original called party number / redirecting number from CAP interface after mobile initial forwarding
IMSIBITANA
Query this table according to calling IMSI when mobile originated and query this table according to called IMSI after forwarding According to IMSI of calling users, This table is used to make processing of numbers (such as changing numbers, chaning routing source codes, and so on) according to IMSI of calling users.
2. PSTN CALLER
TG
The input condition is the trunk group number. The output condition is the trunk group attribute and other attributes of a call, such as whether there is need of c alling party numbers and original party numbers, whether connection can be made without these numbers, and so on. The call barring group is included.
CLRDSG
You can use the call barring group number, calling party number and calling party number attribute (national, international, user,and unknown) to query CLRDSG to bar calls.
(1) Direct call barring (select Reject call). Using this function, you can bar calls entering the trunk group and the office.
(2) Call barring with caller number discrimination (select Caller Number Discrimination). With this function, calls are barred if caller numbers are not in the number length scope configured in this table.
CLDPREANA
This table is used to change the called party number before number analysis for the sake of later number analysis.
A. Process the changing of particular numbers in condition of intelligence, roaming number and forwarding. For example, the retrieval of MSRN and forwarding number from MAP generally adopt international format such as CC+NDC (or AREA CODE)+SN. But sometimes the format is not standard, such as without CC, so this table is used to add the country code.
B. Avoid using function of changing incoming numbers.
C. Avoid using call barring function of this table.
D. Avoid using this table to change the PSTN incoming numbers, use INNUMPREPRO.
3. INCOMING NUMBER PROCESSING
The purpose of incoming number pretreatment data configuration is to normalize called numbers of incoming calls from trunks and MO calls, MSRNs or forwarded -to numbers transmitted by MAP signaling, and called numbers changed in IN procedure. The format of input numbers can meet the relevant internal specifications of the MSOFTX so as to facilitate the unified number analysis of the system.
INNUMPREPRO
Start point of number reanalysis (after HLR returns roaming number / forwarding number or SCP forwarding / changing number, then the number analysis start again from here
INCLRIDX
These tables are used to change numbers according to called party numbers/calling party number/original party number. If an incoming number cannot meet demand of the Analysis Table of Called, you can use the INNUMPREPRO to change the number. It can also be used to identify particular calls and make particular processings to these particular calls.
INORICLDIDX
4. CALLED NUMBER ANALYSIS
CNACLD
The called prefix is the center of number analysis. The number analysis can judge a call (mobile local office call, delivery of paging, or outgoing routing processing). By the number analysis, you can trigger the intelligence and announcement.
MSOFTX3000 makes different processing of analysis and routing according to called number types in CNACLD Table: If it is MSISDN, then MSOFTX fetches roaming numbers according to callednumbers. Then the fetched roaming number or the forwarding number is used by MSOFTX as prefix of calls from MAP to make the number analysis. If it is MSRN and the service attribute is not mobile local office, called number PSTN or unknown number, then the outgoing routing process starts. According to the routing code and routing source code got through analysis, the query process is initiated to the database to find an outgoing circuit. If it is MSRN and the service attribute is mobile local office or a handover number, then the query process is initiated to VDB.The routing process starts and the paging is initiated to mobiles users.
Query CNACLD according to DN set and B number. The number type and call type are analyzed, and following processing is based on these two t ypes. A series of flags will be returned, including the flags of enhance route, particular processing of calling party number, particular processing of prefix, and so on.After check these flags, the calls are processed, namely analysis of the call type according to number analysis.
SUPERRT
By query SUPERRT, you can change routing codes according to different call types such as different forwarding, so as to realize make different calls go to different routes.
CALLPRICHK
The table is used to check dialing of numbers, for example to disconnect some numbers dialed by users and play the announcement of Unallocated Number. You can use dialing call barring function in this table, but do not use CLDPREANA or the INNUMPREPRO. In addition, this table can realize the call barring with discrimination of different call types.
SRVCHK
Check whether a calling subscriber is authorized to make the corresponding calls. You can set the service check type, check mode, and conversation duration restriction. The below functions can be realized, depending on the combination of Check Type and Check Mode:
1.Check relative services in the original mode.
2.Relative services are not checked. (If the service is ODB_BAOC, calls still can be made.)
3.If a user has the attribute, then calls will be disconnected.
4.If a user has not the attribute, then calls will be disconnected.
CLICRTPRO
Query the Caller Feature Table CLICRTANA. If the query fails, then query the Caller Number Analysis Table CNACLR.
CLICRTANA
CNACLR
Help to normalize the calling numbers of incoming calls from trunks, or to conduct various processing over different calling parties who dial the same call prefix (for example, to select different routes according to calling features). Calling number analysis is used to process information such as calling numbers. Calling subscriber attribute analysis is used for special processing when the caller has some special service attributes (for example, whether the subscriber has subscribed to forwarding and service barring services). Calling subscriber attribute processing isused to map a subscriber_s special service attributes respectively to a series o f calling feature index. This index corresponds to thecalling feature index in the calling feature analysis table. The MSOFTX3000 searches the calling feature analysis table through this index and performs special follow-up processing of calls in the call subscriber attribute analysis.
PFXPRO
IF GO TO:
1. PSTN or MSRN Other Office
OUTNUMPREPRO
In the MSOFTX3000 system, if the called number is found to be PSTN, the outgoing number is pre-processed and then sent to the peer office. At this stage, the system
orderly queries OUTNUMPREPRO, OUTCLRIDX, and OUTORICLDIDX, and decides the change of the caller number, called number, and original called number.
OUTCLRIDX
Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers, making the format of the outgoing number conformant with inter-office number transfer specifications
OUTORICLDIDX
OUTCLRIDX is used to convert the transmitted calling/called numbers and original called numbers or re-designate their formats according to calling number prefixes and their related attributes. OUTORICLDIDX is used to convert calling/called numbers and original called numbers or re-designate their formats according to original called prefixes and their related attributes. OUTNUMPREPRO data are used to convert calling/called numbers and original called numbers or re-designate their formats according to call sources, outgoing trunks, called prefixes and related attributes.
RTANA
TRUNK GROUP BEARER Fill in the outgoing signaling with numbers after change
TGLD
TGLDIDX
Outgoing Routing One can also convert numbers on certain trunk group s after trunk routing, by configuring trunk group bearer data. But because that outgoing number preprocessing is more powerful than trunk group bearer data configuration, it is recommended to use outgoing number preprocessing.
AIDNUMPRO
PSTN
OUTGOING
2.
Local MSRN
CLIPRO
If the roaming number is of local office, then the process of query to VD B is initiated. After VDB responds to the query, the process of fetching data of called users is initiated to MAP. Then, MAP delivers paging messages. When the called user responds to the paging, the connection process is finished. After the system receives response of the paging from the called user, it will send a SET UP message to the called user. Before sending this message, query the Caller Number Display Configuration Processing Table CLIPRO, and check whether to change the caller number.
CLCRPRO
Send Paging
AIDNUMPRO
Before sending the put-through message to the caller, the system queries the Auxiliarly Number Processing Table, and checks whether to change the connected number.
MOBILE TERMINATING
3.
MSISDN
GT Code Change
Table (SCCPGT)
Fetch MSRN from HLR
MAPIFNP
According to analysis result, the number type is MSISDN, so the process of fetching roaming number is initiated to MAP. After MAP returns the roaming number, the incoming number pre-processing process INNUMPREPRO starts again. CALL_FROM of this moment is equal to FROM_MAP.
The number analysis process starts again, and the number is found to be a roaming number through
the analysis. If the roaming number is of other office, then an outgoing call is initiated according to therouting code in the number analysis result. The specific process is the same as that of common outgoing calls. numbers after change
Fill in the outgoing signaling with
TGLD
TGLDIDX
Outgoing Routing
One can also convert numbers on certain trunk groups after trunk routing, by configuring trunk group bearer data. But because that outgoing number preprocessing is more powerful than trunk group bearer data configuration, it is recommended to use outgoing number preprocessing.
AIDNUMPRO
PSTN
OUTGOING
2.
Local MSRN
CLIPRO
If the roaming number is of local office, then the process of query to VDB is initiated. After VDB responds to the query, the process of fetching data of called users is initiated to MAP. Then, MAP delivers paging messages. When the called user responds to the paging, the connection process is finished.
After the system receives response of the paging from the called user, it will send a SETUP message to the called user. Before sending this message, query the Caller
Number Display Configuration Processing Table CLIPRO, and check whether to change the caller number.
CLCRPRO
Send Paging
AIDNUMPRO
Before sending the put-through message to the caller, the system queries the Auxiliarly Number Processing Table, and checks whether to change the connected number.
MOBILE
TERMINATING
3.
MSISDN
GT Code Change
Table (SCCPGT)
Fetch MSRN from HLR
MAPIFNP
According to analysis result, the number type is MSISDN, so the process of fetching roamingnumber is initiated to MAP. After MAP returns the roaming number, the incoming number pre-processing process INNUMPREPRO starts again. CALL_FROM of this moment is equal to FROM_MAP.
The number analysis process starts again, and the number is found to be a roaming number throughthe analysis. If the roaming number is of other office, then an outgoing call is initiated according to the routing code in the number analysis result. The specific process is the same as that of common outgoing calls.
