The number preprocessing in the MOC flow applies to both 2G MOCs and 3G MOCs. This flow enables the MSC to perform number change on calling and called numbers. In addition, this flow enables the MSC to trigger special services through the configuration of the Subscriber Service Attribute Index table and NP Service Prefix table. Figure 1 shows the flow of 2G/3G MOC number preprocessing.
Figure 1 Flowchart
NOTE:
Pay attention to the following items:The mandatory tables for querying are highlighted by solid-line frames and the optional tables are highlighted by dotted-line frames.
- Calling number normalization ia not recommended in countries or regions outside China.
- For details about calling number normalization, see Calling Number Normalization in the MOC.
Table Description
Table Name | Command | Input Parameter | Output Parameter | Function Description |
---|---|---|---|---|
2G LAI or GCI Information table or 3G LAI or SAI Information table | ADD LAIGCI ADD LAISAI |
|
| This table is used to configure a location area or cell where the subscriber resides. ADD LAIGCI is applicable to 2G networks and ADD LAISAI is applicable to 3G networks. |
Local Mobile Office Information table | SET INOFFMSC ADD INOFFMSC |
|
| Based on the mobile office information index, the MSOFTX3000 queries the Local Mobile Office Information table for the incoming information such as the mobile country code, area code, and local MSC number. The incoming information is used for the subsequent number analysis and normalization. |
Call Source table | ADD CALLSRC |
|
| Based on the call source name carried in the SETUP message, the MSOFTX3000 queries the Call Source table for the attribute related to the calling call source, which is used for the subsequent number analysis, route selection, and failure processing. |
Subscriber Service Attribute Index table | ADD DNSRVIDX |
|
| Based on the caller number, the MSOFTX3000 queries the Subscriber Service Attribute Index table for the service attribute. Thus, carriers can flexibly perform special processing for mobile subscribers based on these internal service attribute. |
Non-NDC Number Processing table | ADD NONDCDIALANA |
|
| Based on the calling and called numbers, the MSOFTX3000 queries the Non-NDC Number Processing table for the processing type and performs processing on the called number accordingly. |
Called Number Pre-analysis table | ADD CLDPREANA |
|
| Based on the information related to the call originator, the MSOFTX3000 queries the Called Number Pre-analysis table to perform called number change or failure processing. Generally, this table is used to change the called number before called number analysis. |
NP Service Prefix table | ADD NP |
|
| Based on the called number, the MSOFTX3000 queries the NP Service Prefix table for the attributes related to the NP service. |
Call Prefix table | ADD CNACLD |
|
| Based on the called number and DN set, the MSOFTX3000 queries the Call Prefix table for the called number type. |
IMSI Number Analysis table | ADD IMSIBITANA |
|
| Based on the calling IMSI, call category, and called number, the MSOFTX3000 queries the IMSI Number Analysis table. Based on the query result, the MSOFTX3000 performs failure processing, calling or called number change, or changes the route selection source name and service attribute. |
Subscriber Integrated Services Information table | ADD USRVPROC |
|
| Based on the function type, call originator, and caller category, the MSOFTX3000 queries the Subscriber Integrated Services Information table for the calling and called number change names, service attribute, whether to suppress the OCSI, and whether to cover the called number in the MOC CDR. |
Caller Feature Processing table | ADD CLICRTPRO |
|
| This table defines the mapping between service attributes and caller features. It is used to perform number change for calling and called numbers. |