Core Procedure of Number Analysis


Core procedure of number analysis is the major part of number analysis. The core procedure of number analysis can determine the subsequent processing of a call: obtaining the MSRN, sending a paging message, or routing out the call.

Figure 1 Flowchart

Detail:
NOTE: 
In the Figure 1, the mandatory tables for querying are highlighted by solid-line frames and the optional tables are highlighted by dotted-line frames. Pay attention to the following items:
  • The Call Authority Check table is mandatory and can be queried only once for each call. If the query result indicates that Processing type is set to Prohibit, the MSOFTX3000 releases the call.
  • The Called Number Barring Group table is queried only when bit 14 of P150 is set to 0. If the query result indicates call barring, the MSOFTX3000 releases the call.
  • If the query result of the Service Check table indicates that the service check fails, the MSOFTX3000 releases the call.
For easy understanding, the core procedure of number analysis is sub-divided into four procedures:
  • NCSI procedure involved after called number analysis failure If the MSOFTX3000 fails to query the Call Prefix table, it switches to query the Caller Number Analysis table and Caller Feature Analysis table and performs the subsequent processing accordingly.
    • If querying these two tables fails or the N-CSI DP2 is not configured in the Call Prefix table, the MSOFTX3000 releases the call.
    • If the N-CSI DP2 is configured in the Call Prefix table, the MSOFTX3000 triggers the N-CSI DP2 and switches to Number Processing in the CAMEL Event Reporting Flow.
  • Caller number analysis procedure The MSOFTX3000 queries the Caller Number Analysis table only when Caller number analysis flag is set to Yes in the Call Prefix table. Based on the query result, the MSOFTX3000 performs number change, route selection or release processing.
  • Call prefix processing procedure The MSOFTX3000 queries the Call Prefix Processing table only whenDN processing flag is set to Yes in the Call Prefix table. Based on the query result, the MSOFTX3000 performs number change, announcement playing, number re-analysis, or release processing.
    Number re-analysis is classified into direct number re-analysis and number re-analysis performed after pre-analysis of incoming numbers.
    • Direct number re-analysis: The MSOFTX3000 performs the core procedure of number analysis again.
    • Number re-analysis performed after pre-analysis of incoming numbers: The MSOFTX3000 performs both Public Number Preprocessing and the core procedure of number analysis again.
  • N-CSI DP2 triggering procedure As long as the number type is not MSRN and the caller does not subscribe to the OCSI, the MSOFTX3000 performs the N-CSI DP2 triggering procedure. In this procedure, the MSOFTX3000 queries the Caller Number Analysis table and Caller Feature Analysis table. Based on the query result, the MSOFTX3000 triggers the N-CSI DP2 and switches to Number Processing in the CAMEL Event Reporting Flow.
After the core procedure of number analysis is complete, the MSOFTX3000 performs the subsequent processing based on the query result as follows:
  • If the number type is MSISDN, the MSOFTX3000 switches to Number Processing in the SRI-REQ Flow.
  • If the number type is MSRN and the service attribute is PLMN local MSC, the MSOFTX3000 switches to Number Processing in the MTC Flow.
  • If the number type is PSTN, UNKNOWN, or MSRN with the service attribute rather than PLMN local MSC, the MSOFTX3000 switches to Outgoing Route Selection.

Detail:

Table Description

Table NameCommandInput ParameterOutput ParameterFunction Description
Call Prefix tableADD CNACLD
  • DN set
  • Call prefix
  • Service Category
  • Service attribute
  • Called number type
  • Route selection source name
  • DN processing flag
  • Caller number analysis flag
  • Enhanced route processing flag
  • Supplementary signaling flag
  • Service check name
Based on the called number and DN set, the MSOFTX3000 queries the Called Prefix table for the called number type and service attribute. At the same time, the MSOFTX3000 obtains a set of flags and determines whether to query other tables accordingly.
The Called Prefix table is mandatory during number analysis. As the core of the number analysis, the query result of the Called Prefix table determines the subsequent flow of table query.
Enhanced Route Processing tableADD SUPERRT
  • Call type
  • DN set
  • Call prefix
  • Called number maximum length
  • Route selection name
Based on the called number length or call type, the MSOFTX3000 queries the Enhanced Route Processing table for different outgoing routes, thus implementing flexible routing for the specified call prefixes.
This table is queried only when Enhanced route processing flag is set toYes.
Call Authority Check tableADD CALLPRICHK
  • Call source name
  • Call type
  • Call prefix
  • Calling number
  • Caller category
  • Caller roaming type
  • Original called number correlation processing name
  • Process type
Based on the caller number, call type, caller category and caller roaming type, the MSOFTX3000 queries the Call Authority Check table for the processing type to determine whether to continue the call, play an announcement, or restrict the call. For example, the MSOFTX3000 can implement flexible announcement playing according to the forwarding type in a forwarding call.
This table is mandatory and can be queried only once for each call.
Original Called Number Associated Processing tableADD PRICHKORICLDIDX
  • Original called number correlation processing name
  • Original called number
  • Original called roaming type
  • Process type
Based on the original called number and original called roaming type, the MSOFTX3000 queries the Original Called Number Associated Processing table for the processing type to determine whether to continue the forwarding call, play an announcement, or restrict the forwarding call.
This table is queried only when querying the Call Authority Check table is successful and Original called number correlation processing name is valid.
Auxiliary Signaling tableADD AUSSIG
  • Call prefix
  • DN set
  • Call source name
  • Request caller number
  • Sending DDD indicator
  • Send caller number
  • Send original called number
This table is used for a specific call prefix to solve the problem of caller number matching between two offices, for example, whether to request the caller number from the peer office, whether to send the caller number to the peer office, and whether to send the original called number to the peer office.
This table is queried only when Supplementary signaling flag is set toYes.
Called Number Barring Group tableADD CLDGRP
  • DN set
  • Called number
  • Group category
Based on the called barring group and calling barring group, the MSOFTX3000 queries the Called Number Barring Group table to determine whether to bar calls.
This table is queried only when bit 14 of P150 is set to 0.
Service Check tableADD SRVCHK
  • Call source name
  • Service check name
  • Service check type
  • Service check mode
This table is used to configure service check for calls, including checking whether the mandatory service attributes of callers are complete and whether invalid service attributes exist. Based on the check result, the MSOFTX3000 determines whether to restrict the calls.
This table is queried only when Service check name set in the Call Prefix table is valid.
Caller Feature Analysis tableADD CLICRTANA
  • Call source name
  • Caller feature
  • Caller category
  • Call originator
  • DN set
  • Call prefix
  • Route selection name
  • Route selection source name
  • New service property
  • Caller number change name
  • Called number change name
  • Failure source name
  • Processing type
This table is used to modify certain major attributes for a call based on the caller feature and caller category. For example, convert the calling and called numbers or modify the route selection source name and route selection name. Based on the different processing types in this table, the MSOFTX3000 can perform failure processing, trigger the N-CSI DP2, or select a route for the outgoing call.
In the core procedure of number analysis, the Caller Feature Analysis table and the Caller Number Analysis table are queried in the following scenarios: 
  • When Caller number analysis flagis set to Yesin the Call Prefix table, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to modify the call attributes and perform failure processing or outgoing route selection.
  • In the N-CSI DP2 triggering procedure, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to trigger the N-CSI DP2 based on the caller feature or caller number.
  • In the NCSI procedure involved after called number analysis failure, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to trigger the N-CSI DP2 based on the caller feature or caller number. The SCP then determines whether to send a Connect message containing the proper called number for number re-analysis.
Caller Number Analysis tableADD CNACLR
  • Call source name
  • Caller roaming type
  • Calling number
  • Call originator
  • DN set
  • Call prefix
  • Route selection name
  • Route selection source name
  • New service property
  • Caller number change name
  • Called number change name
  • Caller category
  • Failure source name
  • Processing type (values:Not to be processed,Failure processing,Trigger DP2 of N-CSI, andImmediate route selection)
This table is used to modify certain major attributes for a call based on the caller number and caller category. For example, convert the calling and called numbers or modify the route selection source name and route selection name. Based on the different processing types, the MSOFTX3000 can perform failure processing, trigger the N-CSI DP2, or select a route for the outgoing call.
In the core procedure of number analysis, the Caller Feature Analysis table together with the Caller Number Analysis table involve the following query points: 
  • When Caller number analysis flagis set to Yesin the Call Prefix table, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to modify the call attributes and performs failure processing or outgoing route selection.
  • In the N-CSI DP2 triggering procedure, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to trigger the N-CSI DP2 based on the caller feature or caller number.
  • In the NCSI procedure involved after called number analysis failure, the MSOFTX3000 queries the Caller Feature Analysis table and the Caller Number Analysis table to trigger the N-CSI DP2 based on the caller feature or caller number. The SCP then determines whether to send a Connect message containing the proper called number for number re-analysis.
Call Prefix Processing tableADD PFXPRO
  • Call source name
  • Call originator
  • DN set
  • Call prefix
  • New DN set
  • Called number change name
  • Caller number change name
  • Tone playing mode
  • Processing type
This table is used to perform special processing on certain call prefixes, including calling and called number change, tone playing, failure processing, number re-analysis after number change, and N-CSI DP2 triggering.
In the core procedure of number analysis, this table is queried only when DN processing flagis set to Yes in the Call Prefix table. In this case, it is used to implement functions except N-CSI DP2 triggering.
In the SRI-ACK number processing flow, this table is queried to trigger the N-CSI DP2.
N-CSI Configuration tableADD NCSICFG
  • Call source name
  • Caller prefix
  • DN set
  • Called prefix
  • SCP access mode
This table is used to trigger the N-CSI DP3 for the specified calling or called number.

Share this article :
Labels: ,
 
Copyright © 2011. Telecommunication and IT Today - All Rights Reserved
Proudly powered by http://telecomedu.blogspot.com