user interface reference-volume 1 - higher intellect · composed of imsi analysis module, number...
TRANSCRIPT
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-1
4 Prefix
The prefix menu, as shown in Figure 4-1, includes data tables such as [DN pre-analysis], [DN analysis], [DN send analysis], [Number change], [Othersubscriber analysis], [Subscriber group], [Call barring service], [PBX group].
Figure 4-1 "Prefix" interface
4.1 DN Pre-analysis
Through number pre-analysis, the numbers entered through different channels arepreliminarily processed and sent to the number analysis system to make the analysis.Besides, abnormal call requests can be restricted. Number pre-analysis subsystem iscomposed of IMSI analysis module, number pre-analysis module and transfer incomingpre-analysis module. If the call is from the local exchange, calling number IMSI analysiswill be performed, then the number pre-analysis. If the call if from the trunk and istransfer incoming call, the transfer incoming analysis will be performed first, and thenthe number pre-analysis. In addition, IMSI analysis functions to trigger intelligentservices of calling party, and it is used only when the intelligent user (PPS user) isdistinguished with IMSI in numbering plan. Direct number pre-analysis will beperformed upon other calls. Among the three modules, analysis failure on any modulewill not influence the following procedure.
This menu is composed of [Call source], [Number preparation], [DN pre-analysis],[Caller info for DN pre-analysis], [Transfer incoming pre-analysis], [Org CLD fortransfer incoming], [IMSI bits analysis] and [IMSI segment analysis] with theinterface shown in Figure 4-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-2
Figure 4-2 "DN pre-analysis" interface
4.1.1 Call Source
I. Function
Call source refers to the subscriber or incoming trunk that originates calls with the samecall process attributes. Usually several subscribers or trunk groups belong to one callsource. Each call source has an integer code, which is called call source code. Thistable is used to set the relevant data of various call sources.
II. Access
----- Select menu [Prefix/DN pre-analysis/Call source].
The interfaces are as shown in Figure 4-3.
Figure 4-3 Call source table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-3
III. Interface description
The interface description is given in Table 4-1.
Table 4-1 Description of the call source table
Field name Meaning Value range Remarks
Call source codeThe number of a subscriber group with the same callattributes.
0 ~ 255 Required
Declaration Description of the call source code.Customizedcharacters
Optional
Number preparedThe digits of number received before the host beginsnumber analysis when a subscriber of this type ofcall source places a call.
0 ~9 Required
Number prefix setThe codes for classifying and combining subscribersbased on different understandings of called numbers(or call prefixes).
0~255 Required
Route selectionsource code
The classification number of a subscriber of this typeof call source in terms of his outgoing routing policy.
0 ~ 65535 Required
Failure source code
It is the code for classifying and combining callsources based on different processing methods forvarious call failures. Multiple call sources maycorrespond to the same failure source code, butsubscribers in one call source can only correspond toa unique failure source code. That means,subscribers in one call source should take the sameprocessing measures for call failures.
0~255 Required
Number preparationflag
Whether to change the called number when asubscriber of this type of call source is performingcalled number analysis.
Yes, No Required
Intelligent code areaindex
This item is mainly set for different areas using thesame MSC for the prepaid subscribers, with thepurpose of recognizing the callers from differentsources and therefore adding different area codeprefixes before the called number. index to “Prepaiduser number segment” to define the relevantattributes of the subscriber in this prepaid numbersegment.
0~255 Required
Area code The area code of the call source subscribers. 0~FFFFFF
Required. Thesegment here isBCD code, thus 0and 00 havedifferentmeanings.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-4
4.1.2 Number Preparation
I. Function
This table is used to classify the processing methods for called number change basedon different categories of call sources. If a subscriber of the private network callsanother subscriber of the private network, a short number is dialed; but when it is beingprocessed by the switch, this short number is restored to a standard number before itslogic number is consulted/queried.
This table is valid only when “number preparation” in [Call source table] is set as“YES”.
II. Access
----- Select menu [Prefix/DN pre-analysis/Number preparation].
The interface is as shown in Figure 4-4.
Figure 4-4 Number preparation table
III. Interface description
The interface description is given in table 4-2.
Table 4-2 Description of the number preparation table
Field Name Meaning Value range Remarks
Call source codeThe number of a subscriber group with the same callattributes.
0~255 Required
Number change indexThe classification index No. of number change methodcorresponds to “Number change index” in [Numberchange table].
0~255 Required
4.1.3 DN Pre-analysis
I. Function
The caller & called numbers and number attributes are changed through DN Pre-analysis Table and Caller Info For DN Pre-analysis Table, together with Number
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-5
Change Table. Number checking and inter-exchange call restriction functions areimplemented with these tables in combination with the Call Failure Processing Table.In addition, DN Pre-analysis Table also provides functions of call source code changeand number prefix set change.
II. Access
----- Select menu [Prefix/DN pre-analysis/DN pre-analysis].
The interface is as shown in Figure 4-5.
Figure 4-5 DN pre-analysis table
III. Interface description
The interface description is given in table 4-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-6
Table 4-3 Description of the DN pre-analysis table
Field Name Meaning Value range Remarks
Call source code
It indicates the call source. If the call is from thetrunk, the call source code is obtained from thetrunk group table. If the call is from BSC, thecall source code is obtained from the locationarea. Note that if the call is forwarded in, thecall source code may be changed in thetransfer incoming number pre-analysis.
0~65535.0~65534 arevalid values while 65535is an invalid value or nullvalue. The default isnull .(Same below)
Required
Called numberThe called number. Here the number prefix canbe configured. The system searches by meansof maximum prefix match.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF(24xF).
Required. At most24 wildcards “e”can beconfigured. Thewildcard can notinclude othercharacters.
Called subscribercategory
Called subscriber category. This field is anindex field. The system gets the value of thisfield by searching Called Number AnalysisTable. If it is not configured in Called NumberAnalysis Table, it must be configured asAll_type.
National toll PSTN;PLMN local; PLMNnational toll; PLMN othernet; IDD; Analogsubscriber; All TYPE
Required
Call source
It indicates where the number of pre-analysis isfrom. For example, select “Mobile subscriberside” for the number from BSC,“TUP/ISUP/R2/PRA Trunk side” for numberfrom trunk, “MAP side” for number from HLR,and “SCP side” for number from SCP. Select“Call Forward side” when forwarding occurslocally.
Mobile subscriber side;TUP trunk side; ISUPtrunk side;R2 trunk side;PRA side; MAP side;SCP side; Call Forwardside
Required
Caller infoindicator
It is one of the index fields of Caller Info for DNpre-analysis Table. If the caller information isnot necessary for a record, “Caller infoindicator” of the record is set to null. If the callerinformation is needed, “Caller info indicator”should be configured to the record.
0~255. 0~254 are validvalues while 255 is aninvalid value or nullvalue. The default valueis null. (same below).
Optional
Called numberchange flag
It indicates whether the called number shouldbe changed. If it is configured to “No”, thesystem will not change the called number. If it isconfigured to “Yes”, “Called number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-7
Field Name Meaning Value range Remarks
Caller numberchange flag
It indicates whether the caller number shouldbe changed. If it is configured to “No”, thesystem will not change the caller number. If it isconfigured to “Yes”, “Caller Number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes; No Required
Failure processflag
It indicates whether failure (mainlydisconnection) should be handled. If it isconfigured to “Yes”, the system will not changethe number. The line is disconnected and“Failure reason code” is returned. If it isconfigured to “No”, “Failure reason code” isinvalid. The system will change the numberaccording to the configured data.
Yes; No Required
Called numberchange index
It is the number change index value of thecalled number and is indexed to the NumberChange Table. When “Called number changeflag” is set to “Yes”, “Called number changeindex” should be configured, and correspondingrecords should be configured in the NumberChange Table.
0~65535 Required
Caller numberchange index
It is the number change index value of thecaller number and is indexed to the NumberChange Table. When “Caller number changeflag” is set to “Yes”, “Caller number changeindex” should be configured, and correspondingrecords should be configured in the NumberChange Table.
0~65535 Required
Failure reasoncode
The cause value returned in failure handling. Itis valid when “Failure process flag” is set to“Yes”.
Optional
New call sourcecode
New call source code. When “Failure processflag” is set to “No”, after this field is configured,the system will change the call source code ofthe caller number to the value configured in“New call source code” in number pre-analysis.If “New call source code” is configured to nullvalue, no modification will be made.
0~65535 Required
New dial numberset
New number prefix set. When “Failure processflag” is set to “No”, after this field is configured,the system will change the number prefix of thecalled number to the value configured in “Newdial number set” in number pre-analysis. If“New dial number set” is configured to nullvalue, no modification will be made.
0 ~255 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-8
Field Name Meaning Value range Remarks
Send tonemethod
The mode of sending signal tone. Required
Tone IDCorresponding to “Signal Tone Index” in Set ofSignal Tone Table to indicate the type of thesignal tone.
0 ~255 Optional
4.1.4 Caller Info For DN Pre-analysis
I. Function
The function of this table is quite similar to that of DN pre-analysis table. The onlydifference is that this table is indexed from “Caller info indicator” in DN pre-analysistable, for the purpose of making the process of number pre-analysis more flexible forthe calls to which caller information is required in the process.
II. Access
Select menu [Prefix/DN pre-analysis/Caller info for DN pre-analysis].
The interface is as shown in Figure 4-6.
Figure 4-6 Caller info for DN pre-analysis table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-9
III. Interface description
The interface description is given in table 4-4.
Table 4-4 Description of the DN pre-analysis table
Field Name Meaning Value range Remarks
Caller infoindicator
One of the index fields of this table, associatingDN pre-analysis table with this table.
0~255 Required
Caller numberIt is the caller telephone number. Here thenumber prefix can be configured. The systemsearches by means of maximum prefix match.
BCD code. The rangeis from 0 toFFFFFFFFFFFFFFFFFFFFFF(24xF).
Required. At most 24wildcards “e” can beconfigured. Thewildcard can notinclude othercharacters.
Callersubscribercategory
This field is an index field. The system getsthe value of this field by searching CalledNumber Analysis Table. If it is not configured inCalled Number Analysis Table, this field mustbe configured to All_type.
National tollPSTN;PLMN local;PLMN national toll;PLMN other net; IDD;Analog subscriber; AllTYPE
Required
Called numberchange flag
It indicates whether the called number shouldbe changed. If it is configured to “No”, thesystem will not change the called number. If it isconfigured to “Yes”, “Called number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes; No Required
Caller numberchange flag
It indicates whether the caller number shouldbe changed. If it is configured to “No”, thesystem will not change the caller number. If it isconfigured to “Yes”, “Caller Number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes; No Required
Failureprocess flag
It indicates whether failure (mainlydisconnection) should be processed. If it isconfigured to “Yes”, the system will not changethe number. The line is disconnected and“Failure reason code” is returned. If it isconfigured to “No”, “Failure reason code” isinvalid. The system will change the numberaccording to the configured data.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-10
Field Name Meaning Value range Remarks
Called numberchange index
It is the number change index value of thecalled number and is indexed to the NumberChange Table. When “Called number changeflag” is set to “Yes”, “Called number changeindex” should be configured, and correspondingrecords should be configured in NumberChange Table.
0~65535 Required
Caller numberchange index
It is the number change index value of thecaller number and is indexed to the NumberChange Table. When “Caller number changeflag” is set to “Yes”, “Caller number changeindex” should be configured, and correspondingrecords should be configured in NumberChange Table.
0~65535 Required
Failure reasoncode
The reason code returned in failure processing.It is valid when “Failure process flag” is set to“Yes”.
Optional
New callsource code
When “Failure process flag” is set to “No”, afterthis field is configured, the call source code ofthe caller number will be changed to the valueconfigured in “New call source code” during thepre-analysis process of the system. If “New callsource code” is configured to null value, nomodification will be made.
0~65535 Required
New dialnumber set
When “Failure process flag” is set to “No”, afterthis field is configured, the number prefix set ofthe called number will be changed to the valueconfigured in “New dial number set” during thepre-analysis process of the system. If “New dialnumber set” is configured to null value, nomodification will be made.
0 ~255 Required
Send tonemethod
The mode of sending signal tone. Required
Tone IDThe ID of signal tone type corresponding to“Signal Tone Index” in the Set of Signal ToneTable.
0 ~255 Optional
4.1.5 Transfer Incoming Pre-analysis
I. Function
When the original called number is got from the system input path, the transferincoming number pre-process should be performed, Including adding, deleting,changing and extracting the called number and original called number in forwarding.The number type and attributes should be able to be modified. Moreover, together
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-11
with call source, called information and original called information, the transfer incomingcall analysis can be performed, such as inter-exchange call restriction. Number pre-analysis will be performed after the transfer incoming pre-analysis, after that, theoriginal called number will be changed according to the data configured. TransferIncoming Pre-analysis Table, Org CLD For Transfer Incoming Table, Number ChangeTable and Call Failure Processing Table are used together for the pre-processing oftransfer incoming numbers.
II. Access
----- Select menu [Prefix/DN pre-analysis/Transfer incoming pre-analysis].
The interface is as shown in Figure 4-7.
Figure 4-7 Transfer incoming pre-analysis table
III. Interface description
The interface description is given in table 4-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-12
Table 4-5 Description of the transfer incoming pre-analysis table
Field Name Meaning Value range Remarks
Call source code
It indicates the call source. If the call isfrom the trunk, the call source code isobtained from the trunk group table. If thecall is from BSC, the call source code isobtained from the location area.
0~65535 Required
Called number
The called number. Here the numberprefix can be configured. The systemsearches by means of maximum prefixmatch.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF(24xF).
Required. At most24 wildcards “e” canbe configured. Thewildcard can notinclude othercharacters.
Called subscribercategory
Called subscriber category. This field isan index field. The system gets the valueof this field by searching Called NumberAnalysis Table. If it is not configured inCalled Number Analysis Table, it must beconfigured as All_type.
National toll PSTN;PLMNlocal; PLMN national toll;PLMN other net; IDD;Analog subscriber; All TYPE
Required
Org called infoindicator
It is one of the index fields of Org CLD forTransfer Incoming Table. If the originalcalled information is not required for arecord, set “Org called info indicator” inthis record to null. If the information isrequired, this field must be configured tothe record.
In 0~255, 0~254 are validvalues while 255 is aninvalid value or null value.The default is null value(same below).
Optional
Org callednumber changeflag
It indicates whether the original callednumber should be changed. If it isconfigured to “No”, the system will notchange the original called number. If it isconfigured to “Yes”, “Org Called changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured inNumber Change Table.
Yes; No Required
Failure processflag
It indicates whether failure (mainlydisconnection) should be handled. If it isconfigured to “Yes”, the system will notchange the number. The line isdisconnected and “Failure reason code” isreturned. If it is configured to “No”,“Failure reason code” is invalid. Thesystem will change the number accordingto the configured data.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-13
Field Name Meaning Value range Remarks
Org called changeindex
It is the number change index value of theoriginal called number and is indexed tothe Number Change Table. When “OrgCalled number change flag” is set to“Yes”, “Org Called number change index”should be configured, and correspondingrecords should be configured in theNumber Change Table.
0~65535 Required
Failure reasoncode
The reason code returned in failureprocessing. It is valid when “Failureprocess flag” is set to “Yes”.
Optional
New call sourcecode
New call source code. When “Failureprocess flag” is set to “No”, after this fieldis configured, the system will change thecall source code of the caller number tothe value configured in “New call sourcecode” in number pre-analysis. If “New callsource code” is configured to null value,no modification will be made.
0~65535 Required
4.1.6 Org CLD For Transfer Incoming
I. Function
The function of this table is quite similar to that of Transfer Incoming Pre-analysis Table.The only difference is that this table is indexed from “Org called info indicator” inTransfer Incoming Pre-analysis Table, for the purpose of making the process of numberpre-analysis more flexible for the calls to which called information is required in theprocess.
II. Access
----- Select menu [Prefix/DN pre-analysis/Org CLD for transfer incoming].
The interface is as shown in Figure 4-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-14
Figure 4-8 Org CLD for transfer incoming table
III. Interface description
The interface description is given in table 4-6.
Table 4-6 Org CLD for transfer incoming table
Field Name Meaning Value range Remarks
Org called infoindicator
It is one of the index fields of this tableand associates this table with Transferincoming pre-analysis table.
0~255 Required
Org callednumber
The telephone number of the originalcalled subscriber. Here the number prefixcan be configured. The system searchesby means of maximum prefix match.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF(24xF).
Required. Wildcard e canbe configured. At most 24wildcards “e” can beconfigured. The wildcardcan not include othercharacters.
Org calledsubscribercategory
Original called subscriber category. Thisfield is an index field. The system gets thevalue of this field by searching CalledNumber Analysis Table. If it is notconfigured in Called Number AnalysisTable, it must be configured to All_type.
National toll PSTN;PLMNlocal; PLMN national toll;PLMN other net; IDD;Analog subscriber; AllTYPE
Required
Org callednumberchange flag
It indicates whether the original callednumber should be changed. If it isconfigured to “No”, the system will notchange the original called number. If it isconfigured to “Yes”, “Org Called changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured inNumber Change Table.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-15
Field Name Meaning Value range Remarks
Failure processflag
It indicates whether failure (mainlydisconnection) should be handled. If it isconfigured to “Yes”, the system will notchange the number. The line isdisconnected and “Failure reason code” isreturned. If it is configured to “No”,“Failure reason code” is invalid. Thesystem will change the number accordingto the configured data.
Yes; No Required
Org calledchange index
It is the number change index value of theoriginal called number and is indexed tothe Number Change Table. When “OrgCalled number change flag” is set to“Yes”, “Org Called number change index”should be configured, and correspondingrecords should be configured in theNumber Change Table.
0~65535 Required
Failure reasoncode
The reason code returned in failureprocessing. It is valid when “Failureprocess flag” is set to “Yes”.
Optional
New callsource code
New call source code. When “Failureprocess flag” is set to “No”, after this fieldis configured, the system will change thecall source code of the caller number tothe value configured in “New call sourcecode” in number pre-analysis. If “New callsource code” is configured to null value,no modification will be made.
0~65535 Required
4.1.7 IMSI Bits Analysis
I. Function
Both analysis by bit and analysis by segment are provided through IMSI analysis. Thepurpose of IMSI analysis is to trigger caller intelligent services or call restrictions byIMSI. When triggering caller intelligent services, the outgoing OVERLAY of intelligentsubscriber can be implemented through modifying called number or route selectionsource code. Analysis by bit is provided in this table.
II. Access
----- Select menu [Prefix/DN pre-analysis/IMSI bits analysis].
The interface is as shown in Figure 4-9.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-16
Figure 4-9 IMSI bits analysis table
III. Interface description
The interface description is given in table 4-7.
Table 4-7 IMSI bits analysis table
Field Name Meaning Value range Remarks
IMSI IMSI Number (NOTE 1)BCD code. The range is from 0to FFFFFFFFFFFFFFFF(16xF).
Required
Subscribercategory
Caller category, used to distinguish ordinarysubscriber and IN subscriber.
Normal Subscriber; INSubscriber
Required
Called numberchange flag
It indicates whether the called number should bechanged. If it is configured to “No”, the system willnot change the called number. If it is configured to“Yes”, “Called number change index” should beconfigured. Moreover, “Number change index”and relevant information should be configured inNumber Change Table.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-17
Field Name Meaning Value range Remarks
Caller numberchange flag
It indicates whether the caller number should bechanged. If it is configured to “No”, the system willnot change the caller number. If it is configured to“Yes”, “Caller Number change index” should beconfigured. Moreover, “Number change index”and relevant information should be configured inNumber Change Table.
Yes; No Required
Failure processflag
It indicates whether failure (mainly disconnection)should be handled. If it is configured to “Yes”, thesystem will not change the number. The line isdisconnected and “Failure reason code” isreturned. If it is configured to “No”, “Failure reasoncode” is invalid. The system will change thenumber according to the configured data.
Yes; No Required
Called numberchange index
It is the number change index value of the callednumber and is indexed to the Number ChangeTable. When “Called number change flag” is set to“Yes”, “Called number change index” should beconfigured, and corresponding records should beconfigured in the Number Change Table.
0~65535 Required
Caller numberchange index
It is the number change index value of the callernumber and is indexed to the Number ChangeTable. When “Caller number change flag” is set to“Yes”, “Caller number change index” should beconfigured, and corresponding records should beconfigured in the Number Change Table.
0~65535 Required
Failure reasoncode
The reason code returned in failure processing. Itis valid when “Failure process flag” is set to “Yes”.
Optional
New routeselectionsource code
The route analysis is made according to the routeselection code and route selection source code inthe outgoing routing. The route selection code isthe same for the same called number. Differentroutes can be selected based on the change ofroute selection source code.
0~65535 Required
NOTE1: IMSI consists of flag bit and wildcard “e”. The position of the flag bit requires identification while that of thewildcard does not. Please note in IMSI configuration that if of the whole IMSI number contains 16 digits, all should beconfigured. If only 15 digits are contained of the whole IMSI number, the first 15 digits must be configured, and thelast digit will not be processed by the system. It is recommended to configure the last digit to “E”. “E” can also beconfigured on the flag bit on condition that: 1) The positions of MCC and MNC must be flag bit and can not beconfigured with “e”. 2) With the data grouped by MCC+MNC, the flag bits in the same group must be the same. If aflag bit of a specific datum is configured with “e”, the subsequent flag bit must also be “e”. 3) When 15-digit and 16-digit coexist, the bit after MCC+MNC in 15-digit IMSI number should be configured with certain datum instead of “e”as the flag bit. The last bit of IMSI number must be configured with “e”.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-18
4.1.8 IMSI Segment Analysis
I. Function
Both analysis by bit and analysis by segment are provided through IMSI analysis. Thepurpose of IMSI analysis is to trigger caller intelligent services or call restrictions byIMSI. When triggering caller intelligent services, the outgoing OVERLAY of intelligentsubscriber can be implemented through modifying called number or route selectionsource code. Analysis by segment is provided in this table.
II. Access
----- Select menu [Prefix/DN pre-analysis/IMSI segment analysis].
The interface is as shown in Figure 4-10.
Figure 4-10 IMSI segment analysis table
III. Interface description
The interface description is given in table 4-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-19
Table 4-8 IMSI segment analysis table
Field Name Meaning Value range Remarks
Start IMSIThe start IMSI number in IMSI numbersegment (NOTE1)
BCD code. The range is from 0 toFFFFFFFFFFFFFFFF (16xF).
Required
End IMSIThe end IMSI number in IMSI numbersegment.
BCD code. The range is from 0 toFFFFFFFFFFFFFFFF (16xF).
Required
Subscribercategory
Caller category, used to distinguish ordinarysubscriber and IN subscriber.
Normal Subscriber; IN Subscriber Required
Called numberchange flag
It indicates whether the called numbershould be changed. If it is configured to “No”,the system will not change the callednumber. If it is configured to “Yes”, “Callednumber change index” should be configured.Moreover, “Number change index” andrelevant information should be configured inNumber Change Table.
Yes; No Required
Caller numberchange flag
It indicates whether the caller number shouldbe changed. If it is configured to “No”, thesystem will not change the caller number. If itis configured to “Yes”, “Caller Numberchange index” should be configured.Moreover, “Number change index” andrelevant information should be configured inNumber Change Table.
Yes; No Required
Failure processflag
It indicates whether failure (mainlydisconnection) should be handled. If it isconfigured to “Yes”, the system will notchange the number. The line is disconnectedand “Failure reason code” is returned. If it isconfigured to “No”, “Failure reason code” isinvalid. The system will change the numberaccording to the configured data.
Yes; No Required
Called numberchange index
It is the number change index value of thecalled number and is indexed to the NumberChange Table. When “Called numberchange flag” is set to “Yes”, “Called numberchange index” should be configured, andcorresponding records should be configuredin the Number Change Table.
0~65535 Required
Caller numberchange index
It is the number change index value of thecaller number and is indexed to the NumberChange Table. When “Caller number changeflag” is set to “Yes”, “Caller number changeindex” should be configured, andcorresponding records should be configuredin the Number Change Table.
0~65535 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-20
Field Name Meaning Value range Remarks
Failure reasoncode
The reason code returned in failureprocessing. It is valid when “Failure processflag” is set to “Yes”.
Optional
New routeselection sourcecode
The route analysis is made according to theroute selection code and route selectionsource code in the outgoing routing. Theroute selection code is the same for thesame called number. Different routes can beselected based on the change of routeselection source code.
0~65535 Required
NOTE 1: There are two software parameters related to IMSI bits analysis table and IMSI segment analysis table.They are:Bit 0 of DB internal parameter 1: it is IMSI analysis mode parameter. 0 refers to IMSI segment analysis and 1 refers toIMSI bit analysis. Default value is 1.Bit 1 of DB internal parameter 1: it is the position updating mode parameter. 0 refers to setting OVERLAY flag throughIMSI analysis and 1 refers to setting OVERLAY flag through checking Prepaid user number segment table. Defaultvalue is 1.If IMSI segment analysis or IMSI bit analysis is selected and the two tables are configured, the position updatingmode should be set to Setting OVERLAY flag through IMSI analysis. Then the data in Prepaid user number segmenttable will be invalid, since the IN service triggered by IMSI analysis can not co-exist with that by Prepaid user numbersegment table.NOTE 2: in IMSI number segment, the start IMSI number should be smaller than the end IMSI number. The numbersin the segment should be complete and should not be configured with prefix. If MCC+MNC is of 5 digits, the completenumber should be of 15 digits. If MCC+MNC is of 6 digits, the complete number should be of 16 digits. The length ofthe field is of 16xBCD codes. If the complete number is of 15 digits, only 15 bits should be configured and the last bitshould be blank or filled with F. At present, 15-digit format is used.
4.2 DN Analysis
After the above number pre-analysis, the system will change the number preliminarily.In the number analysis stage, the system will continue to analyze the number so as tospecify the routing scheme.
This menu is composed of [Called number analysis], [Number prefix processing],[Caller number analysis], [Additional signaling], [Service change], [Call failureprocessing], [Call duration of special number], [HOT billing user MSISDNsegment], [Prepaid user number segment], [Release control mode] and[Emergency call observation] with the interface shown in Figure 4-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-21
Figure 4-11 "DN analysis" interface
4.2.1 Called Number Analysis
I. Function
This table is mainly used to determine, based on the called number, service attribute,category, route selection code, etc. and set some special processing methods of callingsome called numbers or prefixes, such as whether the caller number should beanalyzed, whether there is any special requirement for ringing, etc.
II. Access
----- Select menu [Prefix/DN analysis/Called number analysis].
The interfaces are as shown in Figure 4-12.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-22
Figure 4-12 Called number analysis table
III. Interface description
The interface description is given in Table 4-9.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-23
Table 4-9 Description of the called number analysis table
Field name Meaning Value range Remarks
Number prefix setThe code for classifying and combiningsubscribers based on different understandingsof called numbers (or call prefixes).
0~255 Required
Call prefix The first several digits of the called number. Note 1 Required
Service typeThe service category to which the prefixbelongs.
Required
Service property The attribute of the call. Required
Route choice codeThe code of route selection policy adopted tocall the prefix.
0~255 Required
Priority choice code The selection policy code of this call priority. 0~255 Required
Release controlselection code
The code of the call release control mode. 0~255 Required
Minimum numberlength
The number of digits received before callednumber analysis.
0~24 Required
Maximum numberlength
The maximum number of digits could beanalysis in this type of calls.
0~24 Required
Voice message flag Whether this type of calls are audiotex calls. Yes, No Required
Entertainmentphone flag
Whether this type of calls are entertainmentcalls.
Yes, No Required
Supplementarysignaling flag
If this type of call is outgoing, this field shouldbe set as “Yes”, and it is necessary to queryadditional signaling table to obtain somesupplementary signaling information.
Yes, No Required
Prefix processingflag
Whether the number prefix set to which thecalled number belongs needs specialprocessing while this type of call is beingprocessed.
Yes, No Required
CLI analysis flagWhether this type of call analyzes the callernumber.
Yes, No Required
Emergency callobservation flag
Whether the call should be traced andobserved if this type of call is emergent.
Yes, No Required
Ringing delay flagThe ringing of some calls (such as 119, 110,etc.) should be delayed before being sent out,so as to prevent misdial.
Yes, No Required
Inquire toll areacode or not
Whether Domestic toll zone number tableshould be queried so as to prevent dialing inbatch.
Yes, No Required
Called number type The type of the call. Required
Charge flag Whether to charge this type of numbers.No indication, Nocharge, charge
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-24
Field name Meaning Value range Remarks
Promptly choice out-route flag
Whether to immediately select outgoing routesfor this type of numbers.
Yes , No Required
GainSet the gain of the trunk board to processoutgoing calls.
Local gain, toll gain Required
Toll prefix lengthThis field shows the length of the toll prefix ifthe call is a toll call and the Domestic toll zonenumber table needs to be queried.
0~6 Required
Destination code forTraffic
Used in traffic statistics. One destination coderepresents the destination of one outgoing call.
0~65535 Optional
Call Barring ServiceIndex
Query Service Change Table and CallBarring Service Table with this index todetermine whether the called number is barredto some caller numbers.
Optional
Destination Code forCall
This field is the input of Outgoing TrunkNumber Format Table, and the called numberscan be further classified.
0~65535 Optional
Subscriber Category It defines the category of the subscriber.
If early ACMThe value YES indicates that ACM messagewill be returned earlier to the peer exchangethan the ACM message in normal flow.
Yes, No Required
Note 1: Valid number or character of less than 16 digits (0~9, b & c are valid fields, of which b stands for the key *,and c stands for the key #). e means invalid.
4.2.2 Number Prefix Processing
I. Function
This table sets different call processing methods, and different subscribers havedifferent requirements for call processing. The requirements include whether to changethe caller/called number, how to process failures, and types of sending signal tone, etc.The processing methods can be classified based on call sources, dial number sets andcalled numbers. Calls not listed in the table are processed in a normal way.
This table is valid only when “Prefix processing flag” in [Called number analysis table]is set as “Yes”.
II. Access
----- Select menu [Prefix/DN analysis/Number prefix processing].
The interfaces are as shown in Figure 4-13.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-25
Figure 4-13 Number prefix processing table
III. Interface description
The interface description is given in Table 4-10.
Table 4-10 Description of the prefix processing table
Field name Meaning Value range Remarks
Call source code
The number of a subscriber group with the same callattributes. For the call from the trunk, the code isobtained from Trunk Group Table; for the call fromBSC, it is specified through LAI and GCI Table. If thecall source code is changed in the number pre-analysisstage, this field is obtained from “New Call SourceCode” in the table related to the number pre-analysis.
0~255 Required
Number prefix setThe code for classifying and combining subscribersbased on different understandings of called numbers (orcall prefixes).
0 ~255 Required
Called numberThe called number corresponding to the relevantnumber prefix set.
Note 1 Required
Called numberchange flag
Whether to change the called number. Yes, No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-26
Field name Meaning Value range Remarks
Send voice flag
Whether to send signal tone directly to callingsubscribers after the called number is received.Disconnect after the tone is sent for a certain time.(Note 2)
Yes, No Required
Failure process flagWhether to query [Failure processing table] toprocess call failures when the called number isreceived.
Yes, No Required
Caller numberchange flag
Whether to change caller number. If “Yes” is filled here,the caller number will be changed in a moderepresented by the caller number change index.
Yes, No Required
New dial numberingset
Whether to reanalyze the number with another newnumber set.
0~255 Required
Called numberchange index
This field is valid when “Yes” is filled in “Called numberchange flag”, indicating the classification index numberof called number change method. It corresponds to the“Number change index” in Number change table.
0~255(Note 4) Optional
Re-analysis flagWhether to reanalyze the call after caller/called numberhas changed.
Yes, No Required
Signal tone index
This field is valid when “Send voice flag” is “Yes”,indicating the index of the signal tone sent to the callerand corresponding to “Signal tone index” in Setting ofSignal tone table.
0~64 Required
Fail reason codeThis field is valid when “Failure process flag” is “Yes”,indicating the cause for call failure and disconnection.
Required
Caller numberchange index
This field is valid when “Caller number change flag” is“Yes”, indicating the classification index number ofcaller number change method. It corresponds to“Number change index” in Number change table.
0 ~255 (Note 3) Optional
Note 1: Valid number or character of less than 16 digits (0~9, b & c are valid fields, of which b stands for the key *,and c stands for the key #). e means invalid.Note 2: If Yes is filled in [Send voice flag], then the tone is sent directly to the caller. In this case, [Failure processflag], [Called number change flag] and [Caller number change flag] are all invalid. If No is filled in [Send voiceflag] and Yes is filled in [Failure processing flag], then both [Called number change flag] and [Caller numberchange flag] are invalid.Note 3: 255 is invalid.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-27
4.2.3 Caller Number Analysis
I. Function
Usually caller number needs no analysis, but in special cases, caller number analysiscan change this caller's outgoing routing, charging mode, etc.
Call source attributes are defined on the call source code. Multiple call sources (localsubscribers or trunk subscribers) can share the same call source code, so they havethe same call attributes. If it is necessary to assign different call source attributes to aspecific calling subscriber, the caller number analysis table can be used to redefine newcall source attributes for it. E.g. calls from incoming trunk group 0 (call source code 0)may be from Office 66 or Office 88. Calls from Office 66 need to be processeddifferently from those from Office 88. That can be done through this table.
This table is valid only when “Caller number analysis flag” in Called number analysistable is set as “Yes”.
II. Access
----- Select menu [Prefix/DN analysis/Caller number analysis].
The interfaces are as shown in Figure 4-14.
Figure 4-14 Caller number analysis table
III. Interface description
The interface description is given in Table 4-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-28
Table 4-11 Description of the caller number analysis table
Field name Meaning Value range Remarks
Call source code
The number of a subscriber group with the samecall attributes. For the call from the trunk, the codeis obtained from Trunk Group Table; for the callfrom BSC, it is specified through LAI and GCITable. If the call source code is changed in thenumber pre-analysis stage, this field is obtainedfrom “New Call Source Code” in the table relatedto the number pre-analysis.
0~255 Required
Caller number Caller number to be analyzed.Number less than 8digits, of which the firstis not 0
Required
Called dial numberset
The number prefix set to which the number dialedby the caller belongs.
0~255 Required
Call prefix The first (several) digits of the called number. Note 1 Required
Route selectionsource code
The code of the route plan selected by callsoriginated by the caller.
0~65535 Required
Failure source code Note 2. 0~255 Required
Charging sourcecode
The code for classifying charged objects based oncharging attributes.
0~65535 Required
Caller categoryThe subscriber category to which this callerbelongs.
Required
Caller numberchange index
With this index, subscribers of this category canquery Number change table to obtain numberchange method when calling, if caller numberchange is necessary.
0~255 Required
Called numberchange index
With this index, subscribers of this category canquery Number change table to obtain numberchange method when calling, if called numberchange is necessary.
0~255 Required
Caller serviceproperty
Property (attribute) of this call. Required
Note 1: Valid number or character of less than 16 digits (0~9, b & c are valid fields, of which b stands for the key *,and c stands for the key #). e means invalid.Note 2: The code for combining and classifying call sources based on different methods for processing various callfailures. Multiple call sources may correspond to the same failure source code, but subscribers in one call source cancorrespond to a unique failure source code. That is, subscribers in one call source must adopt the same method toprocess call failures.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-29
4.2.4 Additional Signaling
I. Function
This table is usually used to set relevant parameters requiring signal cooperation of theremote exchange during connection.
This table is valid only when “Supplementary signaling flag” in [Called numberanalysis table] is set as “Yes”.
II. Access
----- Select menu [Prefix/DN analysis/Additional signaling].
The interfaces are as shown in Figure 4-15.
Figure 4-15 Additional signaling table
III. Interface description
The interface description is given in Table 4-12.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-30
Table 4-12 Description of the additional signaling table
Field name Meaning Value range Remarks
Call source code
The number of a subscriber group with the same callattributes. For the call from the trunk, the code is obtainedfrom Trunk Group Table; for the call from BSC, it isspecified through LAI and GCI Table. If the call sourcecode is changed in the number pre-analysis stage, thisfield is obtained from “New Call Source Code” in the tablerelated to the number pre-analysis.
0~255 Required
Number prefix setThe code for classifying and combining subscribers basedon different understandings of called numbers (or callprefixes).
0~255 Required
Call prefix The first (several) digits of the called number. Note 1 Required
Send CLI Requestor not
Whether to send caller number request to the remoteexchange automatically during compelled control.
Yes, No Required
Send CLI Requestposition
To set the start location to send caller number requestsignal during compelled control, i.e. from which bit to sendcaller number request signal.
0~15 Optional
Sending KC or not Not used.
Sending KC position Not used.
Send CLI or notWhether to send caller number to the remote exchangeautomatically during compelled control.
Yes, No Required
Translate CLI or notIndicating whether to translate the sent caller numberduring compelled control.
Yes, No Optional
Send original CLDor not
Forwarding may have taken place during the connection. Ifthis flag is set as “Yes”, then the called number beforeforwarding will be sent, i.e. the original called number.
Yes, No Required
Note 1: Valid number or character of less than 16 digits (0~9, b & c are valid fields, of which b stands for the key *,and c stands for the key #). e means invalid.
4.2.5 Service Change
I. Function
The calling subscriber is of a series of service attributes, which are specified in HLR.Whether to change the caller service attributes according to the called party isconfigured in this table, and to further obtain the service status in the call.
Similar to the Call Barring Service Table, this table functions to change the serviceattributes of the caller number when calling numbers of certain categories. Note thatonly part of the services in this table are involved in the Call Barring Service Table,basically for call restrictions.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-31
If the service attributes to be modified are concerned in both tables, the configuration ofthe two tables will both influence the final result. The system will first check theconfiguration in Service Change Table, then that of the Call Barring Table. The values ofcaller service attributes are changed according to modifications in the Service ChangeTable, while the call restriction attributes are set through the Call Barring Service Table.
To change the service attributes through this table, the “Call Barring of CLI” in the CallBarring Service Table should be configured.
II. Access
----- Select menu [Prefix/DN analysis/Service change].
The interface is shown in Figure 4-16.
Figure 4-16 Service change table
III. Interface description
The interface is explained in Table 4-13.
Table 4-13 Description of the release mode table
Field name Meaning Value range Remarks
Call source code
The number of a subscriber group with the same callattributes. For the call from the trunk, the code isobtained from Trunk Group Table; for the call fromBSC, it is specified through LAI and GCI Table. If thecall source code is changed in the number pre-analysisstage, this field is obtained from “New Call SourceCode” in the table related to the number pre-analysis.
0~255 Required
Service check indexObtained from Called Number Analysis Table. Thesame index can be defined for the called numbers ofthe same type.
Required
Service check flagThis flag indicates whether to check all the services ofthe caller.
True; False Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-32
Field name Meaning Value range Remarks
Service check type1, 2
It indicates whether to process the correspondingservice. If this field is not set (the corresponding servicetype is set to 0), the setting of the corresponding servicetype in the “Service check method” field is invalid.
1; 0 Required
Service checkmethod 1, 2
The service processing mode. 1 indicates to set thisservice, while 0 indicates to cancel this service.
1; 0 Required
4.2.6 Call Failure Processing
I. Function
This table specifies the method for processing failure to all designated call sources,including sending signal tone to caller, or re-call the called number after number change.Most call failures can be processed only after querying [Prefix processing table], andafter “Call failure processing flag” is set as “Yes”. However, there are a few exceptions,e.g., sending an announcement to subscribers owing fee. Even if “Call failureprocessing flag” is set as “No”, [call failure processing table] is still valid.
II. Access
----- Select menu [Prefix/DN analysis/Call failure processing].
The interfaces are as shown in Figure 4-17.
Figure 4-17 Call failure processing table
III. Interface description
The interface description is given in Table 4-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-33
Table 4-14 Description of the call failure processing table
Field name Meaning Value range Remarks
Fail reason code Call failure cause classification code. Required
Failure source code Note 1. 0~255 Required
Caller categoryThe category to which the callerbelongs.
Required
Roaming subscribercategory
The type of the roaming subscriber. Unused temporarily
Service property The service category of this call. Required
Processing typeThe processing method in case of callfailure.
Required
Signal tone indexSignal tone type in case of call failure,corresponding to “Signal tone index” in[Setting of Signal Tone Table].
0~64 Required
Sending answer signaling
Whether to send back ACM signal orANN/ANC signal in SS7 signalcooperation. If this item is set as “Yes”,then ACM is sent back.
Yes, No Required
Number change indexThe code of number change method,corresponding to “Number changeindex” in [Number change table].
0~255 Required
Note 1: the code for combining and classifying call sources based on different methods for processing various callfailures. Multiple call sources may correspond to the same failure source code, but subscribers in one call source cancorrespond to a unique failure source code. That is, subscribers in one call source must process call failures in thesame way. This field corresponds to Failure cause code in Call source table.
4.2.7 Call Duration of Special Number
I. Function
This table is used to control the call duration of some number segments.
II. Access
----- Select menu [Prefix/DN analysis/Call Duration of special number].
The interface is as shown in Figure 4-18.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-34
Figure 4-18 Call duration of special number table
III. Interface description
The interface description is given in Table 4-15.
Table 4-15 Description of the call failure processing table
Field name Meaning Remarks
Call PrefixThe number or number prefix of which the call duration iscontrolled.
Call duration(Second) The maximum call duration of the corresponding number. In the unit of second
4.2.8 HOT Billing User MSISDN Segment
I. Function
This table is used to define the segment of the mobile subscribers with the HOT-BILLING function.
II. Access
----- Select menu [Prefix/DN analysis/HOT billing user MSISDN segment].
The interface is as shown in Figure 4-19.
Figure 4-19 HOT Billing user MSISDN segment table
III. Interface description
The interface description is given in Table 4-16.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-35
Table 4-16 Description of the call failure processing table
Field name Meaning Remarks
First MSISDN Start MSISDN number of HOT BILLING. Required
Last MSISDN End MSISDN number of HOT BILLING. Required
4.2.9 Prepaid User Number Segment
I. Function
This table is mainly used to define some data related to the prepaid mobile subscribers.It is used in the case that the prepaid service is implemented in OVERLAY mode. Whenthe caller or called is detected as a prepaid user, it is necessary to add a prefix into thecalled number and select the outgoing route to GTSSP. From this table, the routeselection source code, route selection code and called number change index can beobtained.
II. Access
----- Select menu [Prefix/DN analysis/Prepaid user number segment].
The interfaces are as shown in Figure 4-20.
Figure 4-20 Prepaid user number segment table
III. Interface description
The interface description is given in Table 4-17.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-36
Table 4-17 Description of the prepaid user number segment table
Field name Meaning Value range Remarks
Intelligent code areaIndex
Different areas have different intelligent codearea indexes, chiefly to get the address of thecaller.
0~255 Required
Prefix of MISDNMaximum adaptation for the MSISDN numberof the prepaid subscriber.
Required
New route choicesource code
Codes for user groups (classifying users) basedon different understandings of the callednumbers (or the call prefixes).
0~255 Required
Caller number changeindex
The corresponding index after the callernumber change.
0~255 Required
New route choice code Route selection code when calling this prefix. 0~255 Required
Celled number changeindex
Corresponding index after the called numberchange.
0~255 Required
New CLD typeWhether numbers of this type are prepaidnumbers.
Prepaid number Required
New service type How prepaid subscribers realize it.OVERLAY accessservice
Required
New service attribute Service attribute of the prepaid subscriber. Required
4.2.10 Release Control Mode
I. Function
This table sets call release mode based on caller category and release mode selectioncode, corresponds to “Release mode selection mode” in [Called number analysistable], and includes such items as release mode selection code, caller category,release mode, etc.
II. Access
----- Select menu [Prefix/DN analysis/Release control mode].
The interface is shown in Figure 4-21.
Figure 4-21 Release control mode table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-37
III. Interface description
The interface is explained in Table 4-18.
Table 4-18 Description of the release mode table
Field name Meaning Value range Remarks
Release modeselection code
The code of call releasemode
0~255 Required
Caller categoryThe category of calloriginator
Required
Release mode Call release control modeMutual independence, Caller control,Called control, Mutual control
Required
4.2.11 Emergency Call Observation
I. Function
This table is set to observe the process of some important (emergent) calls. The callingprocess can be observed from multiple modules or maintenance consoles. This table isvalid only when the value of “Emergency call observation flag” in [Called numberanalysis table] is set as "Yes".
II. Access
----- Select menu [Prefix/DN analysis/Emergency call observation].
The interface is as shown in Figure 4-22.
Figure 4-22 Emergency call observation table
III. Interface description
The interface is explained in Table 4-19.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-38
Table 4-19 Description of the emergency call observation table
Field name Meaning Value range Remarks
Number prefix setCodes for user groups based on differentunderstandings of the called numbers (orcalled prefixes).
0~255 Required
Call prefixThe first several digits of the callednumber.
Note 1 Required
Sending module 1(2, 3)ID of the module to which this callinginformation is sent.
1~32 Required
Service consoleNumber of the service console to whichthis calling information is sent.
Special serviceconsole
Required
Note 1: 16-digit valid numbers or characters (0~9, b and c are effective fields; "b" stands for the * key and "c" standsfor the # key.
4.3 DN Send Analysis
Sending number processing subsystem changes various types of subscriber numbersas well as the number attributes sent to the system output path. The sending numberprocessing subsystem is divided into four sub-modules by the system output path,namely, bill number processing module, CLI presentation processing module, outgoingtrunk number processing module and other number processing module.
1) Bill number processing module processes the formats and sequences of the callernumber, called number and the third party number in the bill, and outputs to the bill.
2) CLI presentation processing module processes various number presentationdemands.
3) Outgoing trunk number processing module adapts to the demands of differentnumber formats in various signaling specifications. The output path is the trunk side.
4) Other number processing module is concerned with the numbers that are notcommonly used.
This menu is composed of [Outgoing trunk number format], [Caller info foroutgoing trunk], [CLI presentation], [CLD info for CLI presentation], [CDR numberformat], [Bill number check] and [Other number format] with the interface shown inFigure 4-23.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-39
Figure 4-23 "DN pre-analysis" interface
4.3.1 Outgoing Trunk Number Format
I. Function
Outgoing Trunk Number Format Table, Caller Info for Outgoing Trunk Table andNumber Change Table work together to change the outgoing trunk number. Theoutgoing trunk caller number can be changed according to the call source, callernumber, calling subscriber category (local network or other networks), called numberand outgoing office direction. Besides, the caller number sent from CAP signaling canalso be changed. For the outgoing of the called number, different changes can be madeto the format of called number according to different called prefixes, outgoing officedirections and call sources, as well as the roaming area of the called (local, national orinternational). Besides, the called numbers sent from MAP signaling and CAP signalingcan also be changed.
II. Access
----- Select menu [Prefix/DN send analysis/Outgoing trunk number format].
The interfaces are as shown in Figure 4-24.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-40
Figure 4-24 Outgoing trunk number format table
III. Interface description
The interface description is given in Table 4-20.
Table 4-20 Description of the outgoing trunk number format table
Field name Meaning Value range Remarks
Call sourcecode
It indicates the call source. If the call is from thetrunk, the call source code is obtained from thetrunk group table. If the call is from BSC, thecall source code is obtained from the locationarea. Note that if the call is forwarded in, thecall source code may be changed in thetransfer incoming number pre-analysis. Makesure that the call source code configured in thistable is up to date.
0 ~ 65535 Required
Called NumberThe called number. Here the number prefix canbe configured. The system searches by meansof maximum prefix match.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF (24xF).
Required. Wildcarde can be configured.At most 24 wildcardscan be configured.The wildcard can notinclude other
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-41
Field name Meaning Value range Remarks
characters.
CalledSubscriberCategory
Called subscriber category. This field is anindex field. The system gets the value of thisfield by searching Called Number AnalysisTable. If the number has been changed duringnumber pre-analysis, the changed numbershould be configured in the Called NumberAnalysis Table. If it is not configured in CalledNumber Analysis Table, it must be configuredas All_type.
National toll PSTN;PLMN local; PLMNnational toll; PLMN othernet; IDD; Analogsubscriber; All TYPE
Required
DestinationCode for Call
The value of this field is obtained by searchingCalled Number Analysis Table and is used tofurther classify the called number. Usually thisfield is not used. This field in Called NumberAnalysis Table can be configured as 0, andhere is configured as 0 accordingly.
0 ~65535 Required
Peer Office No.The office direction to the peer office. It is usedto differentiate different signaling or meet therequirements of different peer offices.
0 ~ 255 Required
Caller InfoIndicator
It is one of the index fields of Caller Info forDN Pre-analysis Table. If the callerinformation is not necessary for a record,“Caller info indicator” of the record is set to null.If the caller information is needed, “Caller infoindicator” should be configured to the record.
0 ~ 255 Optional
Called NumberChange flag
It indicates whether the called number shouldbe changed. If it is configured to “No”, thesystem will not change the called number. If itis configured to “Yes”, “Called number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes; No Required
Caller NumberChange flag
It indicates whether the caller number shouldbe changed. If it is configured to “No”, thesystem will not change the caller number. If it isconfigured to “Yes”, “Caller Number changeindex” should be configured. Moreover,“Number change index” and relevantinformation should be configured in NumberChange Table.
Yes, No Required
Called NumberChange Index
It is the number change index value of thecalled number and is indexed to the NumberChange Table. When “Called number changeflag” is set to “Yes”, “Called number changeindex” should be configured, andcorresponding records should be configured inthe Number Change Table.
0 ~ 65535 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-42
Field name Meaning Value range Remarks
Caller NumberChange Index
It is the number change index value of thecaller number and is indexed to the NumberChange Table. When “Caller number changeflag” is set to “Yes”, “Caller number changeindex” should be configured, andcorresponding records should be configured inthe Number Change Table.
0 ~ 65535 Required
Called FormatIt is the format of the called number when beingsent out.
SUB, NAT without prefix,NAT with prefix, INTwithout prefix, INT withprefix and Not assigned.If it is configured as Notassigned, the number willbe displayed in theoriginal format.
Required
Caller FormatIt is the format of the caller number when beingsent out.
SUB, NAT without prefix,NAT with prefix, INTwithout prefix, INT withprefix and Not assigned.If it is configured as Notassigned, the number willbe displayed in theoriginal format.
Required
4.3.2 Caller Info for Outgoing Trunk
I. Function
With the “Caller info Indicator” field as the index, make this table work together with[Outgoing Trunk Number Format Table] and [Number Change Table] to convert theoutgoing trunk number.
II. Access
----- Select menu [Prefix/DN send analysis/Caller info for outgoing trunk].
The interface is shown in Figure 4-25.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-43
Figure 4-25 Caller Info for outgoing trunk table
III. Interface description
The interface description is given in table 4-21.
Table 4-21 Description of the caller info for outgoing trunk table
Field Name Meaning Value range Remarks
Caller infoindicator
It is one of the index fields of this table andassociates this table with Outgoing TrunkNumber Format Table.
0~255 Required
Caller number
It is the telephone number of the callersubscriber. Here the number prefix can beconfigured. The system searches by meansof maximum prefix matching duringprocessing.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF (24xF).
Required. Wildcard ecan be configured. Atmost 24 wildcards canbe configured. Thewildcard can notinclude othercharacters.
Callersubscribercategory
Caller subscriber category. This field is anindex field. The system gets the value of thisfield by searching Called Number AnalysisTable. Therefore, the corresponding datashould be configured in Called NumberAnalysis Table. If the number is changed inthe number pre-analysis, the CalledNumber Analysis Table should be modifiedaccordingly. If the data is not configured inCalled Number Analysis Table, this fieldmust be set as “All_type”.
National toll PSTN;PLMN local; PLMNnational toll; PLMN othernet; IDD; Analogsubscriber; All_TYPE
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-44
Field Name Meaning Value range Remarks
Called numberchange flag
It is the flag indicating whether the callednumber should be changed. If it is configuredto “No”, the system does not change thecalled number. If it is set as “Yes”, “CalledNumber change index” should be configuredand “Number change index” andcorresponding information should beconfigured in Number Change Table.
Yes; No Required
Caller numberchange flag
It is the flag indicating whether the callernumber should be changed. If it is set as“No”, the system will not change the callernumber. If it is set as “Yes”, “Caller Numberchange index” should be configured and“Number change index” and correspondinginformation should be configured in NumberChange Table.
Yes; No Required
Called Numberchange index
It is the number change index value of thecalled number and is indexed to NumberChange Table. When “Called numberchange flag” is set as “Yes”, “Called Numberchange index” should be configured, andcorresponding items should be configured inNumber Change Table.
0 ~ 65535 Required
Caller Numberchange index
It is the number change index value of thecaller number and is indexed to NumberChange Table. When “Caller numberchange flag” is set as “Yes”, “Caller Numberchange index” should be configured, andcorresponding items should be configured inNumber Change Table.
0 ~ 65535 Required
Called FormatIt is the format of the called number whenthe call is outgoing.
SUB, NAT without prefix,NAT with prefix, INTwithout prefix, INT withprefix and Not assigned.If it is configured as “Notassigned”, the numberwill be displayed in theoriginal format.
Required
Caller FormatIt is the format of the caller number when thecall is outgoing.
SUB, NAT without prefix,NAT with prefix, INTwithout prefix, INT withprefix and Not assigned.If it is configured as “Notassigned”, the numberwill be displayed in theoriginal format.
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-45
4.3.3 CLI Presentation
I. Function
CLI Presentation Table, CLD Info for CLI Presentation Table and Number Change Tablework together to change the format of the caller number before this number is sent toBSC. The formats of different caller numbers can be changed according to different callsources, caller numbers and caller subscriber categories (home network and othernetworks). Caller numbers sent from CAP signaling can also be modified.
II. Access
----- Select menu [Prefix/DN send analysis/CLI presentation].
The interface is shown in Figure 4-26.
Figure 4-26 CLI presentation table
III. Interface description
The interface description is given in table 4-22.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-46
Table 4-22 Description of the CLI presentation table
Field Name Meaning Value range Remarks
Call source code
It indicates where the call is from. For the call fromthe trunk, the call source code is obtained from theTrunk Group Table; for the call from BSC, the callsource code is determined by the “location area”.Note that when the call is forwarded to the exchangeor the local exchange originates a call, first theforwarding incoming pre-analysis and number pre-analysis are performed. The call source code may bechanged in the former analysis, therefore, make surethat the call source code configured here is updated.
0 ~65535 Required
Caller number
It is the telephone number of the caller. Here thenumber prefix can be configured. The systemsearches by means of maximum prefix matchingduring processing.
BCD code. Therange is from 0 toFFFFFFFFFFFFFFFFFFFFFF (24xF).
Required.Wildcard e can beconfigured. Atmost 24 wildcardscan beconfigured. Thewildcard can notinclude othercharacters.
Caller subscribercategory
Caller subscriber category. This field is an indexfield. The system gets the value of this field bysearching Called Number Analysis Table.Therefore, the corresponding data should beconfigured in Called Number Analysis Table. If thenumber is changed in the number pre-analysis, theCalled Number Analysis Table should be modifiedaccordingly. If the data is not configured in CalledNumber Analysis Table, this field must beconfigured as “All_type”.
National toll PSTN;PLMN local; PLMNnational toll; PLMNother net; IDD;Analog subscriber;All_TYPE
Required
Called infoindicator
It is one of the index fields of CLD Info for CLIPresentation Table. If a record does not need thecalled information, set “Called info indicator” in thisrecord as vacant. If the record needs the calledinformation, “Called info indicator” must beconfigured for the record.
0 ~ 255 Optional
Caller numberchange flag
It is the flag indicating whether the caller numbershould be changed. If it is set as “No”, the system willnot change the caller number. If it is set as “Yes”,“Caller number change index” should be configured,and “Number change index” and correspondinginformation should be configured in Number ChangeTable.
Yes; No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-47
Field Name Meaning Value range Remarks
Caller numberchange index
It is the number change index value of the callernumber and is indexed to Number Change Table.When “Caller number change flag” is set as “Yes”,“Caller number change index” should be configured,and corresponding items should be configured inNumber Change Table.
0 ~ 65535 Required
Number Format The format of CLI presentation
SUB, NAT withoutprefix, NAT withprefix, INT withoutprefix, INT withprefix and Notassigned. If it isconfigured as “Notassigned”, thenumber will bedisplayed in theoriginal format.
Required
4.3.4 CLD Info for CLI Presentation
I. Function
With the “Called info Indicator” as the index, this table work together with CLIPresentation Table and Number Change Table to change the format of the callernumber before this number is sent to BSC.
II. Access
----- Select menu [Prefix/DN send analysis/CLD info for CLI presentation].
The interface is shown in Figure 4-27.
Figure 4-27 CLD Info for CLI presentation table
III. Interface description
The interface description is given in table 4-23.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-48
Table 4-23 Description of the CLD Info for CLI presentation table
Field Name Meaning Value range Remarks
Called infoindicator
It is one of the index fields of thistable and associates CLIPresentation Table with this table.
0 ~ 255 Required
Called number
The telephone number of the calledsubscriber. Here the number prefixcan be configured. The systemsearches by means of maximumprefix matching during processing.
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF (24xF).
Required. Wildcard e canbe configured. At most 24wildcards can beconfigured. The wildcardcan not include othercharacters.
Called subscribercategory
Called subscriber category. Thisfield is an index field. The systemgets the value of this field bysearching Called Number AnalysisTable. Therefore, the correspondingdata should be configured in CalledNumber Analysis Table. If thenumber is changed in the numberpre-analysis, the Called NumberAnalysis Table should beconfigured with the number afterchange. If the data is not configuredin Called Number Analysis Table,this field must be configured as“All_type”.
National toll PSTN; PLMNlocal; PLMN national toll;PLMN other net; IDD;Analog subscriber;All_TYPE
Required
Caller numberchange flag
It is the flag indicating whether thecaller number should be changed. Ifit is configured as “No”, the systemwill not change the caller number. Ifit is configured as “Yes”, “Callernumber change index” should beconfigured, and “Number changeindex” and correspondinginformation should be configured inNumber Change Table.
Yes; No Required
Caller numberchange index
It is the number change index valueof the caller number and is indexedto Number Change Table. When“Caller number change flag” is setas “Yes”, “Caller number changeindex” should be configured, andcorresponding items should beconfigured in Number ChangeTable.
0 ~ 65535 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-49
Field Name Meaning Value range Remarks
Number Format The format of the CLI presentation
SUB, NAT without prefix,NAT with prefix, INT withoutprefix, INT with prefix andNot assigned. If it isconfigured as “Notassigned”, the number willbe displayed in the originalformat.
Required
4.3.5 CDR Number Format
I. Function
The numbers in the bill that can be changed include caller number, called number, thirdparty number, roaming number and charging number; the number can be changedaccording to different number prefixes; the numbers in all types of bills can be changedand the length of the number in the bill can be controlled.
II. Access
----- Select menu [Prefix/DN send analysis/CDR number format].
The interface is shown in Figure 4-28.
Figure 4-28 CDR number format table
III. Interface description
The interface description is given in table 4-24.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-50
Table 4-24 Description of the CDR number format table
Field Name Meaning Value range Remarks
CDR TypeIt indicates the type of thebill.
NOTE1 Required
Number TypeIt indicates the type of thenumber.
Caller number, Called number,Third party number, MSRN,Charged party number
Required
Number Prefix
It is the prefix of thetelephone number of thesubscriber. The systemsearches by means ofmaximum prefix matchingduring processing
BCD code. The range is from 0 toFFFFFFFFFFFFFFFFFFFFFF(24xF).
Required. Wildcard e can beconfigured. At most 24wildcards can be configured.The wildcard can not includeother characters.
Number changeindex
It is the change index valueof the subscriber numberdisplayed on the bill and isindexed to Number ChangeTable.
0 ~ 65535 (65535 by default,which is an invalid value)
Required
Number FormatIt is the format of thenumber that will bedisplayed on the bill.
SUB, NAT without prefix, NATwith prefix, INT without prefix,INT with prefix and Not assigned.If it is configured as “Notassigned”, the number will bedisplayed in the original format.
Required
MAX Length ofNumber
It is the maximum length ofthe number. If the numberexceeds the maximumlength, the extra numberswill be discarded when thenumber is sent to BAU.
0 ~ 255 (255 by default, which isan invalid value)
Required
NOTE1: MOC (Mobile Originated Call), MTC (Mobile terminated Call), Roam (roaming bill), Transit (transit call),MT_SMS (Mobile Terminated Short Message Service), MO_SMS (Mobile Originated Short Message Service),CALL_ATTEMPT (call attempt bill), GATEWAY_OUTGOING (gateway outgoing bill), ISDN-MO (PRA caller bill),ISDN-MT (PRA called bill), CFW (call forwarding bill), MOI (interception bill), ALL TYPE (all bills)
4.3.6 Bill Number Check
I. Function
This table is used to process the illegal characters in bill numbers. For instance,suppose “+” is an illegal character and appears in a bill number, then it will besubstituted or erased through this table.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-51
II. Access
----- Select menu [Prefix/DN send analysis/Bill number check].
The interface is shown in Figure 4-29.
Figure 4-29 Bill number check table
III. Interface description
The interface description is given in table 4-25.
Table 4-25 Description of the bill number check table
Field Name Meaning Value range Remarks
NumberCategory
It indicates the type of the bill.Caller number, Called number,Third party number, MSRN,MSISDN
Required
Character
One of the index fields indicating the illegalcharacter that need to be checked. Whendetecting any character same as configuredin this field, the system will make relevantconversion.
Required
CharacterPosition
One of the index fields in this table,indicating the position of the illegalcharacter. When detecting any charactersame as configured in this field, the systemwill make relevant conversion.
Required.
ProcessingMethod
The processing method for the illegalcharacter.
NOTE1 Required
Replace numWhen “Processing Method” is set as“Replace char”, it will be used to replace thenumber containing the illegal character.
Required
Note: The types of processing methods may include “No action” i.e. to make no processing, “Del code after char” i.e.to delete all numbers after this character, “Del char and code after it” i.e. to delete this character together with allnumbers after it, “Alarm only” i.e. to give an alarm only, “Replace char and alarm” i.e. to delete this character and givean alarm, “Del code after char, alarm” i.e. to delete all numbers after this character and give an alarm, “Del char andcode after it, alarm” i.e. to delete this character together with all numbers after it and give an alarm.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-52
4.3.7 Other Number Format
I. Function
Other Number Format Table and Number Change Table work together for thenumber change upon number transmission in the following cases:
1) When the connected number display format is to be controlled.
The number type should be configured as “Connected Number” and the destinationshould be selected as required.
2) In case of forwarding, the format of the forwarded-to number carried when the callforwarding announcement is sent to the originating office is to be controlled.
The number type should be configured as “Redirection number” and the destination as“MAP”.
3) When the format of MSISDN carried when requesting MAP side for MSRN is to becontrolled.
The number type should be configured as “Called number” and the destination as“MAP”.
4) When the format of the number carried when reporting the call status to SCP is to becontrolled.
The number type should be configured as needed and the destination as “SCP”.
II. Access
----- Select menu [Prefix/DN send analysis/Other number format].
The interface is shown in Figure 4-30.
Figure 4-30 Other number format table
III. Interface description
The interface description is given in table 4-26.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-53
Table 4-26 Description of the other number format table
Field Name Meaning Value range Remarks
Number PrefixIt is the prefix of the telephone number of thesubscriber. The system searches by means ofmaximum prefix matching during processing
BCD code. The range isfrom 0 toFFFFFFFFFFFFFFFFFFFFFF (24xF).
Required
Number TypeIt indicates the type of the number to bechanged.
NOTE1 Required
Destination
It indicates the destination of this number. If thedestination of the forwarding number is theincoming trunk, the destination of original callednumber and forwarded-to number is theoutgoing trunk.
Required
Office Office direction number 0 ~ 255 Required
NumberChange Flag
It indicates whether to change the number. If itis configured as “No”, the system will notchange the number. If it is configured as “Yes”,“Number change index” should be configured,and “Number change index” and correspondinginformation should be configured in NumberChange Table.
Yes; No Required
NumberChange Index
It is the change index value of the number andis indexed to Number Change Table.
0 ~ 65535 (65535 bydefault, which is an invalidvalue)
Required
NumberFormat
It is the format of the number.
SUB, NAT without prefix,NAT with prefix, INT withoutprefix, INT with prefix andNot assigned. If it isconfigured as “Notassigned”, the number willbe displayed in the originalformat.
Required
NOTE1: Connected number, Redirecting number, Called number, Caller number, Generic number, Org called number,Redirection number, MRSN/HO, User define1, User define2.In one forwarding, A -> B -> C -> D, of which, A is Caller number and Generic number, B is Org called number, C isRedirecting number, and D is Redirection number, Called number and Connected number.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-54
4.4 Number Change
I. Function
Number change includes number attribute change, number insertion and deletion,number change, and number extraction in positive or inverted sequence according tospecified positions or specified characters.
II. Access
----- Select menu [Prefix/Number Change].
The interface is shown in Figure 4-31.
Figure 4-31 Number conversion table
III. Interface description
The interface is explained in Table 4-27.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-55
Table 4-27 Description of the number change table
Field name Meaning Value range Remarks
Number changeindex
Index sequence number of number change method. 0 ~512 Required
Change type Number change method. NOTE1 Required
Start position The start location of number change 0~255 Required
Change length
The length of the number to be changed. During thechange operation that needs the field, if the value of thefield is larger than that the actual changeable length or is avacant value, the system will handle it according to theactual changeable length.
0~255 Required
Specifiedcharacter
Specified character in the specified character change. Inthe specified character change, the field must not bevacant or the change will fail. If multiple characters in thenumber to be changed are the same as the value of thisfield, the system will only handle the first one.
BCD code Optional
New number first
In number change where change type is “insert” or“change”, if a new number and number of other sourcecoexist, then it's up to the field to decide whether theinsertion sequence is ”new number + number of othersource“ or ”number of other source + new number”. If“New Number First“ is set as “Yes”, the insertion sequencewould be ”new number + number of other source”; if ”NewNumber First“ is set as ”No”, the insertion sequence wouldbe “number of other source + new number”.
Yes. No Required
New numberThe new number used in number change when “ChangeType” is set as “Insert” or “Change”. Note that only a 14-digit number can be configured for this field.
From 0 toFFFFFFFFFFFFFFF (14 Fs)
Optional
Other numbersource
Numbers specified by other number source are numberstransmitted through programs.
Required
New number type
The type of the number after the change. The system willchange the number type according to this field valueregardless of whether the number change succeeds ornot.
Required
New numbernature of address
The nature of number after change. The system willchange number nature according to the value of the fieldregardless of whether the number change is successful ornot.
Required
NOTE1: The types of number change may include:
No change
Insert at x pos: To insert number at specified position.
Insert in the end: To insert to the end of the number.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-56
Insert after char: To insert number after a specified character.
Insert before char: To insert number before a specified character.
Del all: To delete all.
Del after & including x pos: To delete number after the specified position in a positivesequence.
Del after & including char: To delete number after the specified character in a positivesequence, including the specified character.
Del after & excluding char: To delete number after the specified character in a positivesequence, excluding the specified character.
Del before & including x pos: To delete number before the specified position in aninverted sequence.
Del before & including char: To delete number before the specified character in aninverted sequence, including the specified character.
Del before & excluding char: To delete number before the specified character in aninverted sequence, excluding the specified character.
Change all
Change after & including x pos: To change number after the specified position in apositive sequence.
Change after & including char: To change number after the specified character in apositive sequence, including the specified character.
Change after & excluding char: To change number after the specified character in apositive sequence, excluding the specified character.
Change before & including x pos: To change number before the specified position in aninverted sequence.
Change before & including char: To change number before the specified character in aninverted sequence, including the specified character.
Change before & excluding char: To change number before the specified character inan inverted sequence, excluding the specified character.
Get&Del after & including x pos: To get and delete number after the specified position ina positive sequence.
Get&Del after & including char: To get and delete number after the specified characterin a positive sequence, including the specified character.
Get&Del after & excluding char: To get and delete number after the specified characterin a positive sequence, excluding the specified character.
Get&Del before & including x pos: To get and delete number before the specifiedposition in an inverted sequence.
Get&Del before & including char: To get and delete number before the specifiedcharacter in an inverted sequence, including the specified character.
Get&Del before & excluding char: To get and delete number before the specifiedcharacter in an inverted sequence, excluding the specified character.
Get after & including x pos: To get but not delete number after the specified position in apositive sequence.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-57
Get after & including char: To get but not delete number after the specified character ina positive sequence, including the specified character.
Get after & excluding char: To get and not delete number after the specified character ina positive sequence, excluding the specified character.
Get before & including x pos: To get but not delete number before the specified positionin an inverted sequence.
Get before & including char: To get but not delete number before the specifiedcharacter in an inverted sequence, including the specified character.
Get before & excluding char: To get but not delete number before the specifiedcharacter in an inverted sequence, excluding the specified character.
Remarks:
Delete number in a positive sequence: If the start position but not the deletion length isspecified, delete all numbers after the start position; if both the start position and thedeletion length are specified, delete numbers of the specified length after the startposition.
Delete number in an inverted sequence: If the start position but not the deletion lengthis specified, delete all numbers before the start position; if both the start position andthe deletion length are specified, delete numbers of the specified length before the startposition.
Insertion: If position but not length is specified, insert number after the specifiedposition.
Change number in a positive sequence: If start position but not length is specified,change numbers after the start position into the specified ones; if both start position andlength are specified, change numbers of the specified length after the start position intothe specified ones.
Change number in an inverted sequence: If start position but not length is specified,change numbers before the start position into the specified ones; if both start positionand length are specified, change numbers of the specified length before the startposition into the specified ones.
Number can be extracted in positive and inverted sequences, and the number extractedcan also be saved.
Insert number at the specified character: insert the specified number after the specifiedcharacter according to the specified new number or other source of number change.
Delete number in a positive sequence according to the specified character: a) if changelength is specified, delete numbers of the specified length after this character; b) ifchange length is not specified, delete all numbers after the specified character. In bothcases, whether the specified character is to be deleted is determined by ”the characterincluded or not”.
Delete number in an inverted sequence according to the specified character: a) ifchange length is specified, delete numbers of the specified length before this character;b} if change length is not specified, delete all numbers before the specified character. Inboth cases, whether the specified character is to be deleted is determined by ”thecharacter included or not”.
Change number in a positive sequence according to the specified character: a) ifchange length is specified, change the numbers of the specified length after thespecified character according to the configured ”new number” or ”other source of
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-58
number change”; b) if change length is not specified, change all numbers after thespecified character according to the configured ”new number“ or ”other source ofnumber change”. In both cases, whether the specified character is to be changed isdetermined by ”the character included or not”;
Change number in an inverted sequence according to the specified character: a) ifchange length is specified, change numbers of the specified length before the specifiedcharacter according to the configured ”new number“ or ”other source of numberchange”; b) if change length is not specified, change all numbers before the specifiedcharacter according to the configured ”new number“ or ”other source of numberchange”. In both cases, whether the specified character is to be changed is determinedby ”the character included or not”;
Extract number in a positive sequence according to the specified character: a) Ifchange length is specified, extract numbers of the specified length after the specifiedcharacter; b) if change length is not specified, extract all numbers after the specifiedcharacter. In both cases, whether the specified character is to be extracted isdetermined by ”the character included or not”;
Extract number in an inverted sequence according to the specified character: a) ifchange length is specified, extract numbers of the specified length before this character;b) if change length is not specified, extract all numbers before the specified character.In both cases, whether the specified character is to be extracted is determined by ”thecharacter included or not”;
There are two kinds of number sources for number insertion and number change: ”NewNumber“ and ”Other Number Source”. The ruling sequence of them is controlledby ”New number first”. “Other Number Source“ includes ”Caller number”, ”Callednumber”, ”Org called number” and ”Special number”.
The parameters that should be configured in various change types are shown in thefollowing table.
SequenceNo.
Changetype
Specifiedcharacter
Newnumber
first
Startposition
Changelength
Newnumber
Othernumbersource
New numbernature ofaddress
1 No change
2Insert at xpos
3Insert inthe end
4Insert afterchar
5Insertbefore char
6 Del all
7Del after &including xpos
8Del after &includingchar
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-59
SequenceNo.
Changetype
Specifiedcharacter
Newnumber
first
Startposition
Changelength
Newnumber
Othernumbersource
New numbernature ofaddress
9Del after &excludingchar
10Del before& includingx pos
11Del before& includingchar
12
Del before&excludingchar
13 Change all
14
Changeafter &including xpos
15
Changeafter &includingchar
16
Changeafter &excludingchar
17
Changebefore &including xpos
18
Changebefore &includingchar
19
Changebefore &excludingchar
20
Get&Delafter &including xpos
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-60
SequenceNo.
Changetype
Specifiedcharacter
Newnumber
first
Startposition
Changelength
Newnumber
Othernumbersource
New numbernature ofaddress
21
Get&Delafter &includingchar
22
Get&Delafter &excludingchar
23
Get&Delbefore &including xpos
24
Get&Delbefore &includingchar
25
Get&Delbefore &excludingchar
26Get after &including xpos
27Get after &includingchar
28Get after &excludingchar
29Get before& includingx pos
30Get before& includingchar
31
Get before&excludingchar
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-61
4.5 Other Subscriber Analysis
Of other subscriber analysis, [ST subscriber data], [ST equipment data], [GTCIsubscriber data] and [CUG data] are not used; [Subscriber data index], [Numbersegment], [ISDN data] and [PRA user data] are related to PRA user dataconfiguration.
When PRA user is the calling party, the process of number analysis and table-query isas follows:
After the system has analyzed the SETUP message, it will make further analysis on themessage according to the PRA user access port number, called number that’s beendialed and number of the module where the called number exists; Firstly, obtain fromthe port number the device ID in calling; then assign the port number to USN (UserSequence Number), regard start USN as port number by default; infer from device IDthat user ID is PRA user; query the circuit state according to port number, allocate idle Bchannel time slots and occupy corresponding circuit; According to USN and user ID,query PRA User Data Table to get “Call Source Code”; according to “Call Source Code”,query Call Source Table to get “Number Prefix Set” and keep checking relativeinformation of the caller according to “Number Prefix Set”.
When PRA user is the called, the process of number analysis and table-query is asfollows:
After the system has analyzed the called number, it will query Number Segment Tablefrom the sent information to get “Subscriber Data Index”. Query Subscriber Data IndexTable according to Subscriber Data Index to get User Sequence Number (USN) andModule ID. Query PRA User Data Table by USN to get PRA user data, mainly theDevice ID. Query the circuit state, allocate idle B channel time slots and occupycorresponding circuit (set this circuit as standby). Send SETUP information to calledPRA user, call established.
4.5.1 Subscriber Data Index
I. Function
When this table is used to analyze called number, the system will obtain “SubscriberData Index” from Number Segment Table, and query this table to get “User SequenceNumber (USN)” and “Module ID”.
II. Access
----- Select menu [Prefix/Other subscriber analysis/Subscriber data index].
The interface is shown in Figure 4-32.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-62
Figure 4-32 Subscriber data index table
III. Interface description
The interface description is given in table 4-28.
Table 4-28 Description of the subscriber data index table
Field Name Meaning Value range Remarks
Subscriber Data IndexIndex field of this table, associating NumberSegment Table with this table.
0~255Required
Number statusNumber type. Configured as Ordinary subscribernumber.
Required
Module ID:For the PRA user, module ID where the user dataexists should be configured.
Required
User type For PRA user, configure the field as “PRA User”. Required
User sequencenumber/PBX group
It corresponds to “USN” field of PRA User DataTable; The system will query PRA User Data Tableby USN to obtain PRA user data.
Required
4.5.2 Number Segment
I. Function
This table is used to analyze called number. The system will query this table accordingto “Number Prefix Set” and “Called Number“ to get “Subscriber Data Index”, then furtherquery the Subscriber Data Index Table with this index.
II. Access
----- Select menu [Prefix/Other subscriber analysis/Number segment].
The interface is shown in Figure 4-33.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-63
Figure 4-33 Number segment table
III. Interface description
The interface description is given in table 4-29.
Table 4-29 Description of the number segment table
Field Name Meaning Value range Remarks
Number prefix setCodes for user groups based on differentunderstandings of the called numbers (or calledprefixes).
0~255 Required
First Number of NumberSegment
First number of number segment Required
Last Number of NumberSegment
Last number of number segment Required
Subscriber Data IndexIndex used to find user data in Subscriber DataIndex table
0~255 Required
4.5.3 ISDN Data
I. Function
This table describes ISDN user-related ISDN data, providing ISDN configurationparameters. It includes such fields as ISDN index, transfer capacity, transfer speed,direct access start position, etc.
II. Access
----- Select menu [Prefix/Other subscriber analysis/ISDN data].
The interface is shown in Figure 4-34.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-64
Figure 4-34 ISDN data table
III. Interface description
The interface description is given in table 4-30.
Table 4-30 Description of the ISDN data table
Field Name Meaning Value range Remarks
ISDN IndexIndex field of this table, associating PRA User DataTable with this table.
0~255 Required
TransferCapacity
Transfer capacity of the system, configured accordingto actual conditions.
Required
TransferSpeed
Transfer speed of the system, configured according toactual conditions.
Required
MAX BChannelNumber
Max number of B channels for one calling. Usually configuredas 30.
Required
Direct AccessStart Position
Direct access start position refers to number’s digitsintercepted in direct access service; numbers after thedirect access start position will be processed by theswitch.
NOTE1 Required
NOTE1: If the PRA interface opposite end of MSC accesses the PABX that has ISDN function, and this PABX’s userdemands reserved DDI service, then choose the item ”Direct Access” in the column ”VAS Authority”’ of PRA UserData Table. Besides, suppose the capacity of opposite end PABX is 3000 lines, MSC can set three 4-digit groups forit, e.g., 6547000~6549999.Therefore, internal extension number of PABX is 4-digit long, item ”Direct Access StartPosition“ in ISDN Data Table should be set as ”3”; when an MSC user calls a PABX user, the network will skip thefirst 3 digits and send the latter 4-digit numbers in the range of 7000~9999 to PABX, thus implementing the directaccess function of PABX extension phone.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-65
4.5.4 PRA User Data
I. Function
This table describes the data information of PRA user. It is used to query PRA user-related information when PRA user is a calling/called party.
II. Access
----- Select menu [Prefix/Other subscriber analysis/PRA user data].
The interface is shown in Figure 4-35.
Figure 4-35 PRA user data table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-66
III. Interface description
The interface description is given in table 4-31.
Table 4-31 Description of the PRA user data table
Field Name Meaning Value range Remarks
Module IDID of the module where the user numberexists, determined by user category anduser sequence number (USN).
0~255Required
User sequencenumber
It refers to the uniform logical usersequence number of the user category inthe module. It corresponds to Usersequence number in User Data IndexTable.
NOTE1 Required
User number Number of the user. Required
Device IDIt refers to the ID of the physicalequipment to which the user is connected.
NOTE2 Required
User category Category of the user.Required, usually configuredas ”common”.
User status Status of user (normal or defaulting). Required
Additional usercategory
It describes whether the user is a PBXuser.
Required, usually configuredas “ordinary subscriber”.
Operator categoryUsually configured as ”near-endoperator”.
Required
CENTREX flagIt describes whether it’s a CENTREXUser.
Required, configuredas ”No”.
CENTREX groupnumber
When ”CENTREX flag” is configuredas ”No”, it’s not necessary to configurethis field.
Call source code
Call source refers to the user who makesthe call or the incoming trunk. Usuallyseveral users or incoming trunks belongto the same call source, and each callsource has an integer number that’scalled “call source code”.
Required, usually configuredas “0”.
User group IDOf no use currently, may be notconfigured.
Callpickup/Operatorgroup
Of no use currently, may be notconfigured.
Outgoing call right Outgoing call right.
Required, usually configuredas all ”1”, except when acertain user’s outgoing callright needs to be restricted.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-67
Field Name Meaning Value range Remarks
Incoming call right Incoming call right.
Required, usually configuredas all ”1”, except when acertain user’s incoming callright needs to be restricted.
Number collectiondevice type
Type of number collection device.Required, usually configuredas “automatic”.
Call observationflag
It indicates whether call observation isperformed.
Required, usually configuredas ”No”.
Change sourcecode
May be not configured.
Called chargesource code
May be not configured.
VAS authorityIf this service is provided, choose it fromthe list.
Required
Outgoing calllimited password
Of no use currently, may be notconfigured.
ISDN data indexIt corresponds to ISDN Data Table,indicating the user’s ISDN-relatedproperties.
Required
NOTE1: One port has multiple logical users and each has different user properties (e.g., authority). Allocate a usersequence number (USN) to each logical user. USNs are arranged independently and they are not related to users ofother categories. As the default USN of PRA port equals port Device ID, when Device IDs of PRA are 0, 32, 64, 96,etc., its corresponding USNs are also 0, 32, 64, 96, etc. One USN, or 32 USNs by default, can be provided to a PRAport. For example: USN range of port 32 is 32~63. If more than 32 USNs are to be provided, add them after themaximum Device ID. The maximum PRA Device ID that can be configured for a module is 1024.NOTE2: All device IDs of PRA are exactly divisible by 32 such as 32, 64, 96, 128, 160, etc.
4.6 Subscriber Group
Of no use currently, this table needs no configuration.
4.7 Call Barring Service
I. Function
This table, just like the Service Change Table under the menu [DN analysis], is intendedto change the service properties when a calling subscriber calls the called subscriber ofa certain type. It involves part of the service attributes in the Service Change Table forcall restriction.
If the services to be changed involve these two tables, the configurations of them willaffect the final results as the system will first check the settings of Service ChangeTable and then the Call Barring Service Table. While changing the value of the caller
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-68
service attribute according to the settings of Service Change Table, the system willalso need to consider the settings of the Call Barring Service Table regarding the callrestriction attribute.
To make the settings of this table prevail, set the service attribute flag in the field“Service check type” of the Service Change Table as “0”. If none of the services areset through the Service Change Table, directly set “Service check flag” as “No”.
This table is in correspondence to the Caller Number Analysis Table. The system willfind the field “Call barring service index” in this table by querying the field “Call barringservice index” in Called Number Analysis Table. Setting the field “Call barring serviceof CLI” in this table as “1” mean that this service of the caller is valid, while setting it as“0” mean this service of the caller is invalid.
II. Access
----- Select menu [Prefix/Other subscriber analysis/Call barring service].
The interface is shown in Figure 4-36.
Figure 4-36 Call barring service table
III. Interface description
The interface description is given in table 4-32.
Table 4-32 Description of the call barring service table
Field Name Meaning Value range Remarks
Number prefix setCodes for user groups based on differentunderstandings of the called numbers (or calledprefixes).
0~255 Required
Call barring serviceindex
It corresponds to “Call barring service index“ in“Called number analysis table”, to decide whetherto prohibit the caller of certain service propertiesfrom dialing the called number.
Required
Call barringservice of CLI
It indicates whether to restrict the service of thecaller.
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 4-69
4.8 PBX Group
Of no use currently, it may be not configured.
4
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-1
5 Service
The [Service] menu is as shown in Figure 5-1.
Figure 5-1 "Service" menu interface
5.1 LAI and GCI
I. Function
This table is mainly used to set the data related to the cells of various location areas.
II. Access
----- Select menu [Service/LAI and GCI].
The interfaces are as shown in Figure 5-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-2
Figure 5-2 LAI and GCI table
III. Interface description
The interface description is given in Table 5-1.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-3
Table 5-1 Description of the LAI and GCI table
Field name Meaning Value range Remarks
GCI number Fill in LAI Id, GCI Id. Required
LAI and GCI name Fill in the name of the location area cell. Required
Location area MSCnumber
The MSC number corresponding to the local officeinformation.
Required
Location area VLRnumber
The VLR number corresponding to the local officeinformation.
Required
Roaming restrictedIf "Yes", refer to the Roaming Zone table and MAPFunction Process Configuration table forinformation about access restriction.
Yes, No Required
Incoming call barring Whether the incoming call is barred. Yes, No Required
Outgoing call limited Whether the outgoing call is limited. Yes, No Required
Location area category Whether the location area category is LAI or GCI. LAI, GCI Required
Location area typeIndicate whether the VLR the LAI and GC belongto is a local one or a neighboring one.
Local VLRZone,Neighbour VLRZone
Required
Immediate assignmentflag
Immediate assignment means "Assign afterreceiving CALL PROCEEDING" and Non-immediate assignment means "Assign afterreceiving ALERTING".
Immediate assignmentTCH, Not-immediateassignment
Required
Total BSC numberIf it is LAI, there might be multiple BSCs; if GCI,there must be one BSC.
1~255 Required
Subordinate BSCnetwork ID 1~10
Network identifier for the subordinate BSC. Note 1 Required
Subordinate BSC DPC1~10
The 14-digit DPC for the subordinate BSC. Required
Call source codeThe call source code for determining whether tooriginate a call, used for the call processing so asto distinguish the caller locations of various cells.
0~65535 Required
East-west longitude Geographical location of a cell.East longitude, Westlongitude
Optional
Degree Optional
Shunt Optional
Second Optional
South-north latitude Geographical location of a cell.South latitude, Northlatitude
Optional
Degree Optional
Shunt Optional
Second Optional
Office number The corresponding office direction number. OptionalNote 1: International, International standby, Domestic, Domestic standby.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-4
5.2 LAI and MSRN
I. Function
This table corresponds to MSRN segment table. When "LAI assign rule" is selected for"MSRN Assign Rule" in the MSRN segment table, MSRN is allocated by location area,therefore this table is used to configure the MSRN number segment corresponding todifferent location areas.
When "LAI assign rule" is selected for "MSRN Assign Rule" in the MSRN segment table,this LAI and MSRN table must be configured, otherwise VLR will fail to find thecorrespondence between the roaming number and the location area. If "No assign rule"is selected for "MSRN Assign Rule", this table can be left without configuration.
II. Access
----- Select menu [Service/LAI and MSRN].
The interfaces are as shown in Figure 5-3.
Figure 5-3 LAI and MSRN table
III. Interface description
The interface description is given in Table 5-2.
Table 5-2 Description of the LAI and MSRN table
Field name Meaning Value range Remarks
LAI number Fill in the LAI number. Required
MSRN Assign IndexCorresponding to MSRN Assign Index inMSRN segment table.
0~255 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-5
5.3 Neighbor Cell Configuration
I. Function
This table is mainly used to fulfill the configuration related to the neighbor cells. It isnecessary to configure this table during the handover between MSC offices.
II. Access
----- Select menu [Service/Neighbor cell configuration].
The interfaces are as shown in Figure 5-4.
Figure 5-4 Neighbor cell configuration table
III. Interface description
The interface description is given in Table 5-3.
Table 5-3 Description of the neighbor cell configuration table
Field name Meaning Value range Remarks
GCI number Fill in the GCI number. 0~255 Required
LAI and GCI name Fill in the name of the location area cell. 0~9 Required
Portfolio control flagWhether to control the traffic of the adjacentlocation area cell.
Yes, No Required
BCCH Frequency ofNeighbor 1~32
Fill in the numbers of various neighbor cells. Required
5.4 BSC
I. Function
This table is mainly used to configure data related to the BSC subordinate to the MSC.
II. Access
----- Select menu [Service/BSC].
The interfaces are as shown in Figure 5-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-6
Figure 5-5 BSC table
III. Interface description
The interface description is given in Table 5-4.
Table 5-4 Description of the BSC table
Field name Meaning Value range Remarks
Network identifier Network Id for the BSC. Note 1 Required
DPC The 14-digit signaling code for the BSC. Required
BSC name Define a name for the BSC. Required
Module search modeIn the case of multiple modules, it is used inpaging and handover. Select the A-interfacecircuit.
Cycle, Fixed Required
Module under MSC1~10
Fill in modules actually assigned by the A-interface under the MSC that the BSC belongs to.
0~31 Required
Route selection sourcecode
Corresponds to the "Route selection source code"in the Call Source Table. It is useless here.
0~255 Optional
Total BTS number Temporarily not used. Fill in 64 as fully configured. 0~255 Required
BSC status Describes the status of the BSC.Available,Unavailable, Notinstalled
Required
DTX flag Whether to support discontinuous transmission. Yes, No Required
Location area notunique
Describes the uniqueness of the location area. Ifthe BSC has two or more location areas, fill in with"Yes".
Yes, No Required
Location area identifier The location area Id included in the BSC. RequiredNote 1: International, International standby, Domestic, Domestic standby.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-7
5.5 IMSI GT Conversion
I. Function
When the location is updated, the GT code to the HLR can be obtained according to theIMSI. With this conversion table, the MCC+MNC in the IMSI can be converted into theCC+NDC.
II. Access
----- Select menu [Service/IMSI GT conversion].
The interface is as shown in Figure 5-6.
Figure 5-6 IMSI GT conversion table
III. Interface description
The interface description is given in Table 5-5.
Table 5-5 Description of theIMSI GT conversion table
Field name Meaning Value range Remarks
MCC+MNCCombination of mobile country code and mobilenetwork code.
Required
CC+NDCCombination of country code and nationaldestination code.
Required
Mobile network name Defines a name for the mobile network. Optional
5.6 UNKNOW Device Barring
I. Function
If "allow other unknown user access" is selected for "IMEI Control" field in MAPconfiguration Table, this table is used to determine whether user access is allowedwhen EIR returns IMEI as "Unknown" in CHECK IMEI process. And user access withIMSI number segment configured in this table is not allowed (usually configured ashome PLMN subscriber), while user access from other network is allowed.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-8
II. Access
----- Select menu [Service/Unknown device barring].
The interface is as shown in Figure 5-7.
Figure 5-7 UNKNOW Device Barring table
III. Interface description
The interface description is given in Table 5-6.
Table 5-6 Description of the UNKNOW Device Barring table
Field name Meaning Value range Remarks
Begin IMSISpecify the start IMSI number of the barred numbersegment.
Required
End IMSISpecify the end IMSI number of the barred numbersegment.
Required
5.7 LAI Roam Barring Table
I. Function
This table is used to restrict roaming in certain location areas of specified subscriber.IMSI groups are specified according to IMSI number segment in IMSI Group Table, andwill be further allocated into different IMSI Set in LAI Roam Barring Table. Together withthe configuration of the location areas LAI to be roam barred, the roaming function inthe specified location areas of certain IMSI can be implemented.
II. Access
-----Select menu [Service/LAI roam barring table].
The interface is as shown in Figure 5-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-9
Figure 5-8 LAI Roam Barring table
III. Interface description
The interface description is given in Table 5-7.
Table 5-7 Description of the LAI Roam Barring table
Field name Meaning Value range Remarks
LAIConfigure the location area where roam barring is to beperformed.
Required
IMSI Set1~IMSISet4
Group0~Group63 correspond to "IMSI Group Indes" inIMSI Group Table, used to select user IMSI to berestricted.
Required
5.8 IMSI Group Table
I. Function
Together with the LAI Roam Barring table, this table is used to restrict roaming functionin certain location areas. For detailed implementation method, refer to the functiondescription of LAI Roam Barring table.
II. Access
----- Select menu [Service/IMSI group table].
The interface is as shown in Figure 5-9.
Figure 5-9 IMSI Group table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-10
III. Interface description
The interface description is given in Table 5-8.
Table 5-8 Description of the IMSI Group table
Field name Meaning Value range Remarks
IMSI Group IndexGroup subscriber to have roam barring by IMSI numbersegment.
Required
Begin IMSI/End IMSIThe start and end IMSI of the number segment to berestricted.
Required
5.9 Country Access Code
I. Function
It is mainly used to set a table of the PLMN access code for the country so as todistinguish the mobile caller number (when displayed) from the fixed phone number.That is to say, "0" is not added before the mobile caller number.
II. Access
----- Select menu [Service/Country access code].
The interface is as shown in Figure 5-10.
Figure 5-10 Country access code table
III. Interface description
The interface description is given in Table 5-9.
Table 5-9 Description of the country access code table
Field name Meaning Value range Remarks
NDC Mobile services access code for the country. Number of less than six digits Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-11
5.10 GSM Service
I. Function
This table shows what types of services the MSC supports. When the service issupported by the user data but not supported by the MSC and when the location isupdated, the data in the VDB will suggest "not supported". The "Support" field is alldefaulted as "Yes".
II. Access
----- Select menu [Service/GSM service].
The interfaces are as shown in Figure 5-11.
Figure 5-11 GSM service table
III. Interface description
The interface description is given in Table 5-10.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-12
Table 5-10 Description of the GSM service table
Field name Meaning Value range Remarks
Service type Type of service the GSM provides.Telecom service, Bearer service,Supplementary service
Required
Service codeService code corresponding to differenttypes of services.
Related to the specific services Required
SupportWhether to provide the previouslymentioned service functions.
Yes, no Required
Informationtransfer capacity
Whether to provide various informationtransfer capacities.
Yes, no Required
Rate adaptationtype
Adaptive rate type. Required
Connect element Connect element supported. Required
Layer 2 protocol Provide various Layer 2 protocols. Required
Signal accessprotocol
Type of signal access protocol. Required
Supportcompression
Whether services support thecompression function.
Yes, no Required
5.11 IWF Channel
I. Function
This table must be configured if the IWF equipment is already configured. The channelID is filled in as actually required (configured) and the "Configuration status" is"Available".
II. Access
----- Select menu [Service/IWF channel].
The interface is as shown in Figure 5-12.
Figure 5-12 IWF channel table
III. Interface description
The interface description is given in Table 5-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-13
Table 5-11 Description of the IWF channel table
Field name Meaning Value range Remarks
Module ID Logical ID of the module. 0~255 Required
IWF channel identifier Logical ID of the IWF channel. 0~65535 Required
Configuration status Whether the IWF channel is available. Available, Unavailable Required
5.12 Roaming Subscriber Category
I. Function
This table shows various attributes of the IMSI relevant to the MSC.
II. Access
----- Select menu [Service/Roaming subscriber category].
The interface is as shown in Figure 5-13.
Figure 5-13 Roaming subscriber category
III. Interface description
The interface description is given in Table 5-12.
Table 5-12 Description of the roaming subscriber category
Field name Meaning Value range Remarks
IMSI International mobile station identity. Required
MS typeRelationship between this network and the network wherethe mobile station is located.
Note 1 Required
Note 1: Local MS, Domestic local net MS, International local net MS, National across net MS, International across netMS.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-14
5.13 Roaming Zone
I. Function
This table shows the zone code (ZC) assigned to the MSC. When "Support the roamingzone restricted?" in the [MAP function process configuration table] is set as "Yes",then all ZCs the MSC belongs to should be configured. This means that the MSC willexamine the ZC sent from the HLR by checking this table to see if the ZC is included inthis table. If the ZC is not in this table, then the roaming subscriber is restricted. (Thesubscriber is restricted when the location area of the roaming subscriber does notmatch the ZC.)
II. Access
----- Select menu [Service/Roaming zone].
The interface is as shown in Figure 5-14.
Figure 5-14 Roaming zone table
III. Interface description
The interface description is given in Table 5-13.
Table 5-13 Description of the roaming zone table
Field name Meaning Value range Remarks
Zone code Zone code of the MSC. Required
Name Name of the zone code. Optional
5.14 Setting of Signal Tone
I. Function
This table is concerned with the SPT board playback setting. It mainly sets theattributes relevant to signal tone, including signal tone code, playback mode andplayback times, etc.
II. Access
----- Select menu [Service/Setting of signal tone].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 5-15
The interfaces are as shown in Figure 5-15.
Figure 5-15 Setting of signal tone table
III. Interface description
The interface description is given in Table 5-14.
Table 5-14 Description of the setting of signal tone table
Field name Meaning Value range Remarks
Signal tone index Index of the signal tone type. 0 ~255 Required
Name of signal tone Name to define this signal tone.Character string of less than16 characters
Required
Playback modeSpecify the playback mode for thesignal tone.
Synchronous playback,Asynchronous playback
Required
Voice code 1~5Name of the voice text loaded onto thesignal tone board.
8-character string Required
Voice text description1~5
Languages the voice text is in, e.g.,English, dialects, etc.
Character string Optional
Max number ofplayback
Defines the maximum number ofplaybacks of the voice.
1, 2, 3 Required
5
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-1
6 Trunk
The trunk menu is shown in Figure 6-1, including [Time index], [Route description],[Office direction], [Trunk data], [Additional trunk], [Trunk circuit], [Trunk groupcall bearer index], [Trunk group bearer], [Module route analysis] and [Signalinglink].
Figure 6-1 "Trunk" interface
6.1 Time Index
I. Function
The table specifies time index value based on the time when the call is generated, andthe time index value generated participates in the route selection in the Route analysistable, thus different routes can be selected for different time segments and dynamicroute selection is achieved. For example, traffic can be diverted to other routes in thetraffic peak time of a day.
II. Access
----- Select the menu [Trunk/Time index].
The interface is shown in Figure 6-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-2
Figure 6-2 Time Index table
III. Interface
The interface is explained in Table 6-1.
Table 6-1 Description of the time index table
Field name Meaning Value range Remarks
Week The date when the call is generated. Monday through Sunday Required
Time See Note 1 1~24 Required
Time indexParticipate in route selection, serving as one ofthe key fields in Route Analysis Table.
0~255 Required
Note 1: this field stands for the time point separating two time segments. Its unit is set as "hour". Theprinciple for matching this column is that the recorded time must be matched with the time later than thetime when the call is generated. For example, Sunday is set with two records, and the values in the "time"field are 10 and 24 respectively. Then the time segments before 10 o'clock on Sunday match the TimeIndex corresponding to 10, the time segments after 10 o'clock on Sunday match the Time Indexcorresponding to 24.
6.2 Route Description
Route description includes the basic process of trunk routing, i.e., specifying the routenumber according to the destination and originating location of the call, then specifyingthe sub-route before the trunk group is located.
The menu item is composed of the four data tables: Route Analysis, Route, Subrouteand Subroute/Trunk Group. The interface is shown in Figure 6-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-3
Figure 6-3 Route description interface
6.2.1 Route Analysis
I. Function
This table specifies the outgoing route according to route selection code, routeselection source code, caller category, address information indicator, route identifierand time index.
II. Access
----- Select the menu [Trunk/Route description/Route analysis].
The interface is shown in Figure 6-4.
Figure 6-4 Route analysis table
III. Interface description
The interface is explained in Table 6-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-4
Table 6-2 Description of the route analysis table
Field name Meaning Value range Remarks
Route choice code
The code corresponds to the Route choicecode in Called Number Analysis Table,indicating the route selection strategy codeused to call the prefix.
0 ~255 Required
Route selectionsource code
The code corresponds to the Routeselection source code in Call Sourcetable, and is used to specify routesaccording to call source.
0~255 Required
Caller category The category of the caller.ordinary; priority; operator;data; test; all categories
Required
Address informationindication
The service attribute of the call adoptingsuch routing mode.
international toll; nationaltoll; local call; all categories
Required
Time indexThe time index number available from TimeIndex table.
0 ~255 Required
Route identifierThe route index available from successfulmatching based on the previous 5 key fields.
0~255 Required
Route nameName corresponding to the route number(identifier).
customized Optional
6.2.2 Route
I. Function
The table defines the type of the route, sub-routes included and sub-route selectionmode. One trunk route can be set with up to 6 sub-routes.
II. Access
-----Select menu [Trunk/Route information/Route].
The interfaces are shown in Figure 6-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-5
Figure 6-5 Route table
III. Interface description
The interfaces are explained in Table 6-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-6
Table 6-3 Description of the route table
Field name Meaning Value range Remarks
Route identifier Route index available from Route Analysis Table. 0~255 Required
Route name Title defined for the route.Less than 16 Englishcharacters
Optional
Route type The treatment method when routing fails. Note 1 Required
Subrouteselection mode
The method to select different subroutes.sequential Selection; routingon percentage (Note 2)
Required
Preferred thismodule
In trunk circuit selection, whether to select thecircuit of the module this call locates in priority.
Yes, No Required
Percent 1--5It is valid when subroute selection mode is set asrouting on percentage, indicating the percentageof traffic shared by the corresponding subroute.
0~100 Optional
1st --5th subrouteSubroute number, corresponding to "Subroutenumber" in the subroute table.
0~255 (Note 3) Optional
Note 1: Normal route: it means that when trunk circuit resource is unavailable for the time being so that routeselection fails, calls are rejected directly instead of any queuing.Queuing route: it means that when trunk circuit resource is unavailable for the time being so that when route selectionfails, apply the same processing as that for successful route selection and wait for idle circuit at the user side.Note 2: Sequential selection: select route in the sequence starting from direct subroute to the 2nd subroute and to the5th subroute, i.e. if the direct subroute is busy, select the 2nd subroute and so forth.Routing on percentage: within the threshold of 100%, the five types of subroutes (from direct subroute, the 2ndsubroute to the 5th subroute) are defined as five subroute groups. Select by sequence between subroute groups andselect by percentage in each subroute group.Note 3: 255 is an invalid value.
6.2.3 Subroute
I. Function
This table sets the corresponding office direction number of the subroute and theselection mode of trunk groups included in the subroute.
II. Access
----- Select menu [Trunk/Route information/Subroute].
The interfaces are shown in Figure 6-6.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-7
Figure 6-6 Subroute table
III. Interface description
The interfaces are explained in Table 6-4.
Table 6-4 Description of the subroute table
Field name Meaning Value range Remarks
Subroute identifier The number of the subroute. 0~255 Required
Name of the subroute The title of the subroute. English character Optional
Office directionOffice direction number this trunk groupcorresponds to.
0~255 Required
Trunk group selectionmode
The mode of selection trunk group belonging tothis subroute.
Note 1 Required
The 1st~the 8th searchmodule
It indicates the SM module on which thesubroute should be searched. The number ofmodule filled in [1st Search Module] is the firstmodule to be searched.
1~32, 255 (Note 2) Required
Note 1: Recycle: every time select the next group number after that of the last selected one.Minimum: always select the group with the smallest number.Maximum: always select the group with the largest number.Random: select a random group (of this subroute) in all groups.Note 2: 255 is an invalid value.
6.2.4 Subroute/Trunk Group
I. Function
This table configures the priority and availability of all trunk groups of a specificsubroute.
II. Access
----- Select menu [Trunk/Route information/Subroute/Trunk group].
The interface is shown in Figure 6-7.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-8
Figure 6-7 Subroute/trunk group table
III. Interface description
The interface is explained in Table 6-5.
Table 6-5 Description of the subroute/trunk group table
Field name Meaning Value range Remarks
Subroute identifierThe number of the subroute, corresponding to theSubroute identifier in Subroute table.
0~255 Required
Trunk group identifier The identifier of the trunk group. 0~255 Required
Priority Note 1. 0~255 Required
Usability Note 2. 0~255 Required
Name of the subroute Logical name defining the subroute identifier.User-definedcharacters
Optional
Note 1: when selecting a trunk group of a specific subroute, prefer the trunk group of higher priority. Only when thesetrunk groups are all busy should the trunk group of lower priority be selected. The top priority is enjoyed by 0 level and255 is an invalid value.Note 2: the description of the times a specific trunk group can be selected. In a specific subroute, the selection timesof the trunk group (initially it is the value of availability) will be reduced by 1 after being selected once until theselection times are reduced to zero. Then the trunk group will refuse any further selection. When the selection timesof all trunk groups in the corresponding subroute are reduced to zero, all the groups will be assigned again with newavailability value. The purpose of this value is to distribute the traffic into each group of a subroute according to thegiven rule. The priority and availability value of a specific trunk group here is set, compared with other trunk groupsunder the same route.For the subroute of inter-module speech channel, this field can be left blank or filled in with 255 (it means invalid).
6.3 Office Direction
I. Function
The table configures the related attributes of the opposite office directly and physicallyconnected with this GMSC, which include office direction No., level, type, DPC ofopposite office etc.
II. Access
----- Select menu [Trunk/Office direction].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-9
The interfaces are shown in Figure 6-8.
Figure 6-8 Office direction table
III. Interface description
The interfaces are explained in Table 6-6.
Table 6-6 Description of the office direction table
Field name Meaning Value range Remarks
Office directionidentifier
It is the unified numbering of office directions. Whenthe local end is directly and physically connected toother switching equipment with a trunk line, the routeto this switching equipment is called office direction.
0~255 Required
Office name It stands for the titles of all office directions.Less than 16 charactersby subscribers' self-defined setting.
Optional
Peer office type The type of the opposite office.GMSC, TMSC, MSC,BSC, PSTN
Required
Peer office levelLevel of the opposite office compared to the localoffice.
Superior, peer andinferior.
Required
Peer officeproperty
The attributes of the opposite office. Note 1 Required
Destinationsignaling pointcode
It means the DPC of related office direction in SS7signaling network. (Note 2)
000000~FFFFFF
Number of hexadecimalsystem
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-10
Field name Meaning Value range Remarks
Network identifier SS7 signaling network ID. (Note 2)
International,international reserved,national and nationalreserved
Required
Signal controlnumber
It is used for ISUP multi-national signalingadaptation. As the index to the Multi-nationaladaptation signaling control table, this table needs nomodification after configuration based on the actualnational signaling, either does the value range.
Required
Note 1: SPC office, crossbar office, step-by-step office, voice mailbox, voice mailbox station, manual console, servicestation, public data network, STP and SCP.Note 2: the corresponding relation between the network ID and signaling point code bits is shown in Table 6-7.
Table 6-7 Table of comparisons between network ID and its corresponding numbers of signaling pointcode bits
Network ID DSP Code Type
International 14-bit signaling point code
International reserved 24-bit/14-bit signaling code
National 24-bit signaling point code
National reserved 14-bit signaling point code
6.4 Trunk Data
The "Trunk Data" mainly sets the various attributes of the trunk group.
This menu includes such menu items as [Trunk group], [CAS Data], [R2 datasignaling change], [Trunk CCS7 data], [A-interface circuit pool table], [PCMstruct], [Line signaling up-covert], [Line signaling down-covert], [RSD signalingup-convert], [RSD signaling down-convert] and [CAS timer]. Among the itemsabove, [Line signaling up-covert], [Line signaling down-covert], [RSD signalingup-convert], [RSD signaling down-convert] and [CAS timer] that are relevant to R2signaling data configuration are configured in accordance with the actual national R2signaling. And the data configured in these tables is not modified during operation, thusthe tables are not described here.
The interface is shown in Figure 6-9.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-11
Figure 6-9 Trunk data interface
6.4.1 Trunk Group
I. Function
The table defines some attributes of the trunk group.
II. Access
----- Select menu [Trunk/Trunk data/Trunk group].
The interfaces are shown in Figure 6-10.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-12
Figure 6-10 Trunk group table
III. Interface description
The interfaces are explained in Table 6-8.
Table 6-8 Description of the trunk group table
Field name Meaning Value range Remarks
Module IDLogic number of the module where the trunk group islocated.
1~32 Required
Trunk groupnumber
The number of the trunk group in the local office. 0~65535 Required
Trunk group nameTitle defined for a specific trunk group for naming,memorizing and distinguishing this trunk group fromother groups.
English charactersless than 16 bits
Optional
Call source codeAs an identifier of the incoming call that occupies thistrunk group circuit.
0~65535 Required
Office direction/peer module
The office direction number corresponding to theequipment that the trunk group is connected to or thenumber of AM module that the trunk group isconnected to (the trunk group is used for inter-module communication).
0~255 Required
Circuit type The type of trunk circuit in this group. Note 1 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-13
Field name Meaning Value range Remarks
Trunk groupdirection
It means this trunk serves as an incoming speechchannel or an outgoing speech channel. IfBidirectional Trunk is selected, this trunk can serveeither as an incoming speech channel or as anoutgoing speech channel.
Incoming trunk,outgoing trunk orbidirectional trunk
Note 2
Required
Circuit selectionmode
Set the selection mode of the trunk circuit of thistrunk group to avoid dual-seizure during the circuitselection by the two offices connected to this trunkgroup.
Note 3 Required
Additional trunkgroup
This field is for non-digital trunk. Unused
Number of thereserved circuit
The number of circuits retained for networkmanagement. For ordinary calls, when ordinary trunkcircuits are all busy, route selection will fail. Forpriority call, when ordinary trunk circuits are all busy,the retained circuits (if there is any) can be used.
0~9999Required
Recommendedvalue: 0
Connect to satellitechannel
If the satellite circuit is linked, there will be long timedelay. Then echo suppresser should be started.
Yes, No Required
Echo eliminatordirection
The mode of providing echo suppression. Note 4 Required
Signaling type There are two signaling modes: R2 and CCS7. R2, CCS7 Required
Incoming call rightCall-in authority is used to control the authority of theincoming trunk circuit. Only the call of permitted typecan pass through.
local office, local,local toll, nationaltoll, international toll
Required
Outgoing call rightCall-out authority is used to control the authority ofthe outgoing trunk circuit. Only the call of permittedtype can pass through.
local office, local,local toll, nationaltoll, international toll
Required
DOD2It indicates whether the trunk stops the second dialtone. This applies to the situation that the machine isthe user machine. It is used in a fixed network.
Yes. No Unused
Initial send tone ornot
It is used to send Boolean mode signal to the callervia the trunk circuit. It sends tone when theoccupation message is received and occupationacknowledgment is returned. It is used in the fixednetwork.
Yes, No Unused
Type of the initialtone
The type of the sent initial signal tone. Used in afixed network.
Unused
Abnormally sendtone or not
It indicates whether a tone will be sent whenconnection processing fails. If it is set as “YES”, ACMmessage will be sent to the opposite office and asignal tone will be played. Otherwise a disconnectionmessage will be returned. In R2 signaling, if allincoming trunk numbers have been collected and Bsignal is returned to outgoing trunk, thr latter willsend signal tone.
Yes, No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-14
Field name Meaning Value range Remarks
Charge sourcecode
It represents the code of incoming trunk chargingpacket that this trunk group belongs to.
Unused
Outgotrunk chargesource code
It represents the outgoing trunk charging packet thatthis trunk group belongs to.
Unused
Use peer officecharging pulse
Used in a fixed network. Unused
Charge complaint
If it is set to “YES”, it means the complaint bill will begenerated during the charging of this trunk groupincluding incoming trunk charging, outgoing trunkcharging. Used in a fixed network.
Unused
CAMA
It is only effective to outgoing trunk group. If it is setto “YES”, the upper level exchange connected withthe trunk group will make centralized charging, andrequest the local office to send the caller number.
Yes, No Required
Output trial call bill
If it is set to “YES”, it means any call attempt (so longas trunk is occupied, regardless whether theconnection succeeds, it is a call attempt) via thetrunk group will generate a ticket, including outgoingtrunk and incoming trunk.
Yes, No Required
Calling numberavailable or not
If it is set as “YES”, it indicates that as the outgoingtrunk, local exchange will not send caller numberwhen requested by the incoming trunk. If the localexchange serves as the incoming trunk, whether torequest caller number from the peer exchange isdetermined by "send CLI request flag" in CAS datatable.
Yes, No Required
Connecting withoutcaller number
It means whether the connection is allowed when thecaller number is unavailable during the call.
Yes, No Required
Minimum length ofcaller number
The minimum length of the caller number. If thelength is not reached, it means the caller number isnot obtained.
0~15 Optional
Caller numbersupplying mode
It means which parameter can be used forreplacement when the caller number is unavailableduring the call.
Trunk line ID,default number(Note 5)
Required
Recommendedvalue: Defaultnumber
Default callernumber
This field is effective when the Caller NumberProvision Mode is set as Default Number. Itindicates the value of the default caller number.
A number less than16 digits
Optional
A-interface circuitpool number
Index to A Interface Circuit Pool Table, to definerelevant attributes of A-interface circuit.
Conditional numberUsed in SOSM monitoring function for CP to inquirethe trunk group number of certain module.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-15
Note 1: DT, TUP, ISUP, ECI, ECR, ECT, V5TK, PRA, PHI, GOPT. Note that the circuittype of inter-module should be set to GOPT. As a virtual trunk group, there is no trunkcircuit in it.
Note 2: usually Bi-directional trunk is not used. The outgoing and incoming trunk shouldbe configured with one corresponding to the other. I.e., if the local exchange is set asoutgoing trunk, the trunk group of peer exchange should be set as incoming trunk. Foreach exchange, at least one outgoing trunk group and one incoming trunk group shouldbe configured.
Note 3: Minimum: select from the smallest circuit.
Maximum: select from the largest circuit.
Recycle: select the circuit next to the last selected one.
FIFO: form a queue of circuits available and select the circuit in a first-in-first-out
principle.
main/non-main control: select the circuit in first-in-first-out (for main control) /first-in-last-out (for non-main control) principle so as to minimize the chance of dual-seizure oftrunk circuits.
Random: select any circuit at random.
Note 4: not provided, provided E1 echo, provided HW echo, R2. If ECR bosrd is in use,it should be configured as Provided_E1_Echo, while if DT board is in use, it should beconfigured as Not_Provided.
Note 5: trunk line ID: composed of the MSC number of local office, the number of themodule the trunk located and the circuit No occupied by the call.
6.4.2 CAS Data
I. Function
Select the line signaling type and RSD signaling type used by R2 signaling through thistable.
II. Access
----- Select menu [Trunk/Trunk data/CAS data].
The interfaces are shown in Figure 6-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-16
Figure 6-11 CAS data table
III. Interface description
The interfaces are explained in Table 6-9.
Table 6-9 Description of the CAS data table
Field name Meaning Value range Remarks
Module IDThe logic number of the module where thetrunk group is located.
1~32 Required
Trunk group number The number of the trunk group. 0~65535 Required
Line signaling typeLine control type. It should be used incooperation with the opposite office.
Note 1
Required
Configured asDL_LINE_2BIT for R2signaling.
RSD signaling typeIt should be used in cooperation with theopposite office.
Note 2Required
Configured as MFC forR2 signaling.
Line signaling eventconvert idx
Index to Line signaling up-convert Talbe, todefine attributes relevant to line signaling.
0~7 Required
Line signaling cmdconvert index
Index to Line signaling down-convert Talbe,to define attributes relevant to line signaling.
0~7 Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-17
Field name Meaning Value range Remarks
RSD event convertindex
Index to RSD signaling up-convert Talbe, todefine attributes relevant to registersignaling.
0~7 Required
RSD commandconvert index
Index to RSD signaling down-convert Talbe,to define attributes relevant to registersignaling.
0~7 Required
Send CLI requestflag
It means whether the caller number shouldbe requested if it is not received during thecall.
Yes, No Required
Send CLI requestposition
It means in what position (which digit ofcalled number has been received) shouldsend the request of caller number.
0~31 Required
Receive CLI flagIt means whether caller number can beaccepted during the call.
Yes, No Required
Send CLI flagIt means whether caller number will be sentduring the call.
Yes, No Required
Send HES requestflag
Whether to send echo suppression request. Yes, No Required
Send circuit typerequest flag
Whether to send circuit type request. Yes, No Required
CAT requestposition
Separately request caller number, while 0indicates not to request separately.
If send CAT afterCLI req end
Whether to send caller type after sendingcaller number request.
Yes, No Required
If confirm whenhave CLI
Whether to comfirm caller number received. Yes, No Required
If CAT req beforeCLI req
Whether to request caller type beforerequesting caller number.
Yes, No Required
Fixed CLI lengthWhether the length of caller number is fixed."0" means it is not fixed.
Congestion NOCLI Whether to congest on no caller number. Yes, No Required
Send B group whencongestion
Whether to send B group signal whencongestion.
Yes, No Required
Note 1: DL_LINT_2BIT, DL_LINE_1BIT, DL_PULSE, DL_NO5.Note 2: MFC, MFP, PULSE, NONE, DTMF, AT0_DIMF, AT0_PULSE, MFPS, RSDS.
6.4.3 R2 Data Signaling Change
This table is not used.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-18
6.4.4 Trunk CCS7 Data
I. Function
Some attributes of the trunk group about CCS7 signaling are set in the table. When[Signaling type] of a specific trunk group in the [Trunk group table] is CCS7 signaling,refer to this table.
II. Access
----- Select menu [Trunk/Trunk data/ Trunk CCS7 data].
The interfaces are shown in Figure 6-12.
Figure 6-12 Trunk CCS7 data table
III. Interface description
The interfaces are explained in Table 6-10.
Table 6-10 Description of the trunk CCS7 data table
Field name Meaning Value range Remarks
Module IDThe logic number of the module where thetrunk group is located.
1~32 Required
Trunk groupnumber
The number of the trunk group. 0~65535 Required
Continuity checkWhether the continuity check should beperformed.
Yes, NoRequired
Recommended value: No
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-19
Field name Meaning Value range Remarks
Time delay value
Time delay of the trunk group circuit. It isused in No. 7 signaling to determinewhether this trunk circuit meets therequirement of time delay in this call.
0~255 Required
Group to singlemessage timeout
Whether the group reset messageresented when timeout should bechanged to single circuit reset message.
Yes, No Required
Transfer capacity Transmission capability of ISDN call. Note 1 Required
Transmissionmode
Transmission mode of ISDN call. Note 2 Required
CIC change typeCIC change is mainly used for trunk self-loop test.
Decrease, increase,no change
Required
CIC change valueThis field is effective when [CIC changeType] is set as Increase or Decrease. Itindicates the change value of CIC.
0~211 Optional
ST modeWhether to add F after numbers beingsent to indicate the end of the number.
Required
Configure according toactual situations.
Max CLD lengthonce send
It indicates the maximum length of thecalled number in IAM message of ISUPsignaling system, which serves as theaddress signal.
Required
Configure according toactual situations.
Note 1: Speech service, Unrestricted digital info service, Restricted digital service, 3.1kHz audio service, Unlimiteddigital service with tone, Video service.Note 2: Packet mode, 64kbit/s, 128kbit/s, 384kbit/s, 1530kbit/s, 1920kbit/s, Multiple rate.
6.4.5 A-Interface Circuit Pool
I. Function
It is used for the A Interface to indicate capabilities with which trunks transmit variousservices. All circuit pool numbers of the Trunk group table should be listed in thistable.
II. Access
----- Select menu [Trunk/Trunk data/A-interface circuit pool].
The interface is shown in Figure 6-13.
Figure 6-13 A-interface circuit pool table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-20
III. Interface description
The interface is explained in Table 6-11.
Table 6-11 Description of the PCM structure table
Field name Meaning Value range Remarks
Circuit pool identifierThe Id of the circuit pool corresponding to theA-interface circuit pool identifier in the Trunkgroup table.
0~255 Required
GSM bearercapacity
GSM's bearing capability. Note 1Required(Recommended:all)
CIC change typeCIC is the circuit identification code in CCS7signaling used for the trunk self-loop.
Increase, Decrease,No transform
Required
CIC change value Value for CIC change. 0~211 RequiredNote 1: Full rate speech version 1, Full rate speech version 2, Full rate speech version 3, Half rate speech version 1,Half rate speech version 2, Half rate speech version 3, Full rate data, Half rate data.
6.4.6 PCM Struct
This table currently is not in use.
6.5 Additional Trunk
None of the tables under this menu are to be configured.
6.6 Trunk Circuit
I. Function
The table defines the attributes of the trunk circuit.
II. Access
------ Select menu [Trunk/Trunk circuit].
The interfaces are shown in Figure 6-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-21
Figure 6-14 Trunk circuit table
III. Interface description
The interfaces are explained in Table 6-12.
Table 6-12 Description of the trunk circuit table
Field name Meaning Value range Remarks
Module IDThe logic number of the module where the trunkgroup is located.
1~32 Required
Circuit sequencenumber
The number of the trunk circuit. 0~255 Required
State
The status of the trunk circuit. If this trunk circuit isused to transmit signaling, this field should be setto “Unavailable”. Then this circuit will not beoccupied during the call connection.
Unavailable, blocked,available
Required
Trunk groupidentifier
The number of the trunk group where the trunkcircuit locates.
0~65535 Required
CICCircuit identification code. It is a kind of coding forcircuits in CCS7 signaling. All circuits to one officedirection will have a unified coding.
0~4095 Required
Transmitting gainThe sending gain value of the trunk board whenthis trunk circuit is used for outgoing call.
0~255 Unused
Receiving gainThe receiving gain value of the trunk board whenthis trunk circuit is used for incoming call.
0~255 Unused
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-22
Field name Meaning Value range Remarks
Master control flag
It is used for selection of circuit control mode inCCS7 signaling. To avoid dual-seizure when twooffices are selecting outgoing trunk circuit, the“Main Control Flag” setting of the same circuit inthe two offices should be opposite to each other.
Yes, No Required
Call observation flagWhether the call should be observed. If Yes, thecall observation ticket will be generated. It is usedin a fixed network.
Yes, No Unused
V5 link identifierThe number of the link when it is used as a V5link.
0~255 Optional
Circuit project serialnumber
The unified numbering of the whole network. Thecircuit project number is mainly used in networkmanagement and test.
0 ~65535 Optional
6.7 Trunk Group Call Bearer Index
I. Function
This table defines the index required by searching the corresponding [Trunk groupbearer table].
II. Access
----- Select menu [Trunk/Trunk group call bearer index].
The interface is shown in Figure 6-15.
Figure 6-15 Trunk group call bearer index table
III. Interface description
The interface is explained in Table 6-13.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-23
Table 6-13 Description of the trunk group bearer table
Field name Meaning Value range Remarks
Module IDThe logic number of the module where the trunkgroup is located.
1~32 Required
Trunk groupidentifier
The number of the trunk group. 0~65535 Required
Call sourcecode
The codes of the subscribers after classificationby call attributes in respect of difference andsimilarity.
0~255 Required
Number prefixset
The code for classifying and combiningsubscribers based on different understandings ofcalled numbers (or call prefixes).
0~255 Required
Call prefixA section of called numbers intercepted from frontto back or all called numbers.
Numbers or characters suchas B and C less than 16digits.
Required
Call bearerindex
It corresponds to “Bearer Index Number” in TrunkGroup Bearer Table and is used to query TrunkGroup Bearer Table.
0~255 Required
6.8 Trunk Group Bearer
I. Function
This table is used to set trunk seizure point and number change mode.
II. Access
------ Select menu [Trunk/Trunk group bearer].
The interface is shown in Figure 6-16.
Figure 6-16 Trunk group bearer table
III. Interface description
The interface is explained in Table 6-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-24
Table 6-14 Description of the trunk group bearer table
Field name Meaning Value range Remarks
Module IDThe logical number of the module where the trunkgroup is located.
1~32 Required
Trunk bearer indexnumber
Index number of call bearer. 0~255 Required
Trunk occupationpoint
It indicates the digits of the called number that havebeen received when a trunk circuit of the group couldbe seized for transmission channel of the speechcircuit.
0~15 Required
Send calling numberchange index
This field corresponds to “Change Index Number” in theNumber Change Table, and is used to query the callernumber sending change mode.
0~255 (Note 1) Optional
Send called numberchange index
This field corresponds to “Change Index Number” inNumber Change Table, and is used to query the callednumber sending change mode.
0~255 (Note 1) Optional
Outgoing echoeliminator flag
Whether to assign echo suppression to the outgoingtrunk.
YES, NO Required
Note 1: 255 is an invalid value.
6.9 Module Route Analysis
I. Function
This table describes the route of the inter-module speech channel of this MSC system.
II. Access
----- Select menu [Trunk/Module route analysis].
The interface is shown in Figure 6-17.
Figure 6-17 Module route analysis table
III. Interface description
The interface is explained in Table 6-15.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-25
Table 6-15 Description of the module route analysis table
Field name Meaning Value range Remarks
Module IDThe logical number of SM with inter-modulespeech channel.
1~32 Required
Destinationmodule number
The number of the destination module, i.e. AMmodule number.
0Required
Recommended value: 0
Route identifierThe number of the route from the source moduleto the destination module.
0 ~255 Required
6.10 Signaling Link
I. Function
This table is set so that the signaling links can be evenly seized (occupied) during aninter-module call. The occupation probability of the signaling link of greater weight valueis smaller while that of the signaling link of less weight value is greater. The signalingcan therefore be connected through without difficulty, and chances of being blocked arereduced accordingly. In the MSC/VLR, only a detailed description of all modulesadjacent to AM (Module 0) is required in the table.
II. Access
----- Select menu [Trunk/Signaling link].
The interface is shown in Figure 6-18.
Figure 6-18 Signaling link table
III. Interface description
The interface is explained in Table 6-16.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 6-26
Table 6-16 Description of the signaling link table
Field name Meaning Value range Remarks
Adjacent modulenumber 1
Number of the first module of the two SM moduleswith signaling connection relationship.
0~32 Required
Adjacent modulenumber 2
No. of the second module of the two SM moduleswith signaling connection relationship.
1~32 Required
Link set 1Link set through which message goes fromadjacent module 1 to adjacent module 2.
0~255 Required
Link set 2Link set through which message goes fromadjacent module 2 to adjacent module 1.
0~255 Required
Weighted valueDescribes the importance of the connectionbetween two modules.
0~254 Required
In the MSC/VLR/SSP, this signaling table only gives the connection relationshipsbetween AM and various modules. Normally 255 is filled in the "Link set" field.
6
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-1
7 Signaling
The signaling menu is shown in Figure 7-1, including [CID module], [MTP DSP], [MTProute], [MTP link set], [MTP link], [SCCP DSP], [SCCP SSN], [GT] and [New GT].
Figure 7-1 "Signaling" interface
7.1 CIC Module
I. Function
This table is used to specify which module the CCS7 signaling trunk circuit (TUP/ISUP)belongs to according to DPC, NI and CIC.
II. Access
----- Select menu [Signaling/CIC module].
The interface is shown in Figure 7-2.
Figure 7-2 CIC module table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-2
III. Interface description
The interface is explained in Table 7-1.
Table 7-1 Description of the CIC module table
Field name Meaning Value range Remarks
Destination signalpoint code
Note 1000000 ~FFFFFF Number ofhexadecimal system
Required
Network identifier The network indicator of DSP.International, international reserved,national, national reserved
Required
First CIC CIC number of start circuit. 0~4095 Required
Last CIC Note 2 0~4095 Required
Module IDThe number of SM where thetrunk circuit locates.
1~32 Required
DSP nameThe name of the destinationsignaling point.
Not more than 16 English letters ornumbers
Optional
Note 1: here it refers to the DPC of the related office direction in CCS7 signaling network. This box should be filledwith hexadecimal numbers. For the national network (24-bit DPC), input the main signaling area code, the branchsignaling area code and DPC of hexadecimal system in a sequence from higher bit to lower bit. For the nationalstandby network (14-bit DPC), fill the first two bits with 0 to make it up to 16 bits, and input hexadecimal DPC in thesequence from higher bit to lower bit.Note 2: CIC of the end circuit. For different DPC or NI, the sections of the start circuit CIC and end circuit CIC do notinterfere with each other, and they can be overlapped. But one thing to be ensured is that the definition should be thesame as that of the peer exchange.
7.2 MTP DSP
I. Function
This table is used to configure attributes of all destination signaling points such as DPCcodes and their home network, as well as the route selection mode to this signalingpoint.
II. Access
------ Select menu [Signaling/MTP DSP].
The interfaces are shown in Figure 7-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-3
Figure 7-3 MTP DSP table
III. Interface description
The interface is explained in Table 7-2.
Table 7-2 Description of the MTP DSP table
Field name Meaning Value range Remarks
DSP index Note 1. 0~65535 Required
DSP name The name of the DSP.Not more than 16 Englishletters or numbers
Optional
International Note 2.000000 ~FFFFFF Number ofhexadecimal system
Required
Internationalstandby
Note 3.000000 ~FFFFFF Number ofhexadecimal system
Required
Domestic Note 4.000000 ~FFFFFF Number ofhexadecimal system
Required
Domestic standby Note 5.000000 ~FFFFFF Number ofhexadecimal system
Required
International netavail
It indicates whether the destination signalingpoint is in the international network. If thedestination signaling point is not in thenetwork, then all settings of this destinationsignaling point in the international networkare invalid.
Yes, No Required
Internationalstandby net avail
It indicates whether the destination signalingpoint is in the international reserved network.If the destination signaling point is not in thenetwork, then all settings of this destinationsignaling point in the international reservednetwork are invalid.
Yes, No Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-4
Field name Meaning Value range Remarks
Domestic netavail
It indicates whether the destination signalingpoint is in the national network. If thedestination signaling point is not in thenetwork, then all settings of this destinationsignaling point in the national network areinvalid.
Yes, No Required
Domestic standbynet avail
It indicates whether the destination signalingpoint is in the national standby network. Ifthe destination signaling point is not in thenetwork, then all settings of this destinationsignaling point in the national standbynetwork are invalid.
Yes, No Required
Signal transferPoint
It indicates whether the correspondingdestination signaling point is an signalingtransition point.
Yes, No Required
Neighbor flag
It indicates whether there is direct signalingroute between the corresponding destinationsignaling point and the signaling point of thelocal exchange.
Yes, No Required
Link set selection
It indicates how to accomplish the loadsharing of signaling service between themultiple signaling routes to a destinationsignaling point. The value of this field is loadsharing mode mask code of signaling routelevel. After this mask code is calculated withSLS, the actually selected signaling routecan be obtained.
Note 6 Required
Note 1: it indicates the index number when the corresponding destination signaling point is internally quoted. Theindex number corresponding to any DSP should be the only one which labels the DSP. The index value is for thetable item in the DSP table. It should appear in strict accordance with the sequence of 0~N-1 (N is the number ofDSP), otherwise it can not correctly correspond to DSPs in the background management, which will result in datadisorder between the foreground and the background, and possibly the abnormal operation of the signaling nodemachine (the switch).Note 2: this field indicates the DPC of the corresponding DSP in the international network. Whether the value of thisfield is meaningful depends on the setting of "Effective local coding 1" in [Intra-Office Information Table]. If the localsignaling point appears visible in the international network (International net avail is set to YES), then the value ofthis field is meaningful. 0 indicates invalid DPC value.Note 3: this field indicates the DPC of the corresponding DSP in the international standby network. Whether the valueof this field is meaningful depends on the setting of "Effective local coding 2" in [Intra-Office Information Table]. Ifthe local signaling point appears visible in the international standby network (International standby net availafterward is set to YES), then the value of this field is meaningful. 0 indicates invalid DPC value.Note 4: this field indicates the DPC of the corresponding DSP in the national network. Whether the value of this fieldis meaningful depends on the setting of "Effective local coding 3" in [Intra-Office Information Table]. If the localsignaling point appears visible in the national network (National net avail afterward is set to YES), then the value ofthis field is meaningful. 0 indicates invalid DPC value.Note 5: this field indicates the DPC of the corresponding DSP in the national standby network. Whether the value ofthis field is meaningful depends on the setting of "Effective local coding 4" in [Intra-Office Information Table]. If thelocal signaling point appears visible in the national standby network (National standby net avail afterward is set toYES), then the value of this field is meaningful. 0 indicates invalid DPC value.Note 6: link set selection 0 bit; link set selection 1 bit; link set selection 2 bit; and link set selection 3 bit.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-5
7.3 MTP Route
I. Function
This table is used to configure the signaling routes to respective destination signalingpoints.
II. Access
----- Select menu [Signaling/MTP route].
The interface is shown in Figure 7-4.
Figure 7-4 MTP route table
III. Interface description
The interface is described in Table 7-3.
Table 7-3 Description of the MTP route table
Field name Meaning Value range Remarks
DSP indexedIt indicates the DSP that this signaling route willgo to. This index corresponds to the “DSPindexed” in the above MTP link set table.
0~65535 Required
Link set identifierIt indicates the first section of link sets that thissignaling route will pass through to the DSP.The number will appear in MTP link set table.
0~65535 Required
Priority Note 1. Note 2Required
Recommendedvalue: 0
Route name The name of the route.User self-defines. EitherEnglish letters ornumbers will do
Optional
Note 1: it indicates the priority level of the signaling routes when they are available. When multiple signaling routes ofdifferent priority levels to this DSP are all available, those of higher priority level will be preferred to carry signalingservice, while those of lower priority level can carry signaling service only after the higher priority signaling routesbecome all unavailable.Note 2: 0~255. 0 is the highest priority level. 255 is the invalid priority level.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-6
7.4 MTP Link Set
I. Function
This table describes information of the signaling link set from local signaling point to theadjacent DSP, which includes the selection mode of signaling link.
II. Access
----- Select menu [Signaling/MTP link set].
The interface is shown in Figure 7-5.
Figure 7-5 MTP link set table
III. Interface description
The interface is described in Table 7-4.
Table 7-4 Description of the MTP link set table
Field name Meaning Value range Remarks
Link set identifier
It indicates the logic number of the link set inthe system. This number should be exclusivein the table to label this link set and canfunctions as the access index of this table.
0~65535
(Note 1)Required
Link set name The name of the link set.
Self-defined by subscribersthemselves and should not berepeated, with no more than 16English letters or numbers.
Optional
Neighboring DSPindexed
It indicates the DSP indexed that thissignaling link set is directly connected to inMTP DSP Table. The Adjacent Flag of thecorresponding DSP should be set to “YES”.
0~65535 Required
Link selection Note 2. Note 3 RequiredNote 1: The link set numbers should appear in strict accordance with the sequence of 0~N-1 (N is the number of thelink sets). Otherwise they can not correctly correspond to the actual link sets in the background management, whichmay result in data disorder between the foreground and the background, and probably the abnormal operation of thesignaling node machine (the switch).Note 2: It indicates how to accomplish load sharing of signaling service among the multiple signaling links of asignaling link set. The value of this field is the load sharing mode mask code of signaling link level. After this maskcode is calculated with SLS, the selected signaling link can be obtained.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-7
Note 3: link selection 0 bit; link selection 1 bit; link selection 2 bit; and link selection 3 bit.
7.5 MTP Link
I. Function
This table describes information of the signaling link from local signaling point to theadjacent signaling point.
II. Access
----- Select menu [Signaling/MTP link].
The interfaces are shown in Figure 7-6.
Figure 7-6 MTP link table
III. Interface description
The interfaces are described in Table 7-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-8
Table 7-5 Description of the MTP link table
Field name Meaning Value range Remarks
Module IDThe logic number of the SM that thesignaling link belongs to.
1~32 Required
Link identifier The number of the physical signaling link. 4~19, 24~39 Required
Link nameThe name of the link self-defined by theuser.
Not more than 16 Englishletters or numbers.
Optional
Trunk equipmentidentifier
It indicates the owner of the signaling datalink in CCS7 signaling link.
TUP, ISUP, ECT, ECI Required
CCS7 signalingequipment ID
It indicates the signaling terminalequipment used in CCS7 signaling link.
CCS7, LPN7Required
Recommendedvalue: LPN7
Circuit sequencenumber
Trunk time slot number used in CCS7signaling link.
0 ~65535 Required
Signaling link code Note 1 0 ~255 Required
Sending signalinglink code
Note 2 0 ~255 Required
Link set identifierIt indicates the signaling link set which thesignaling link is in. It corresponds to theLink Set Number in MTP Link Set Table.
0 ~65535 Required
Priority Note 30~255, 0 is the highest and255 invalid.
Required
Satellite circuitidentifier
It indicates whether a satellite circuit isused for this link.
Yes, NoUnused
Recommendedvalue: NO
Congestion startthreshold
It indicates when the occupationpercentage of the sending buffer of thesignaling link goes up to this setting value,the signaling link will enter the congestionstatus. Then the message to be sent maybe abandoned.
0 ~100Required
Recommendedvalue: 80
Congestion endthreshold
It means when the occupation percentageof the sending buffer of the signaling linkgoes down to this setting value aftercongestion occurred, the signaling link willstop sending congestion message.
0 ~100Required
Recommendedvalue: 70
Test code
It indicates a test byte used in sending thesignaling link test message. In the presentsystem, all test bytes of the signaling linktest message should be the repetition ofthis test byte.
0 ~FFRequired
Recommendedvalue: A5
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-9
Field name Meaning Value range Remarks
Test code lengthIt indicates the number of test codes usedin sending the signaling link test message.
1 ~15Required
Recommendedvalue: 10
Note 1: it indicates the logic number of the signaling link in the signaling link set. This number is a CCS7 signalingprotocol project number. All signaling links in a signaling link set should be uniformly numbered so that the twoexchanges connected by the signaling link could exercise overall management on the signaling links. In addition, thenumber of one signaling link should be identical in the two exchanges connected. This number should be exclusive inthe signaling link set so that this signal link can be identified.Note 2: this flag is mainly used for self-loop sending. In self-loop test environment, the value of this field should be thecode of another signaling link in the same signaling link set in self-looped test environment. But in real installationenvironment, the value of this field should be the same with that of the Signaling Link Code field.Note 3: it indicates the priority of the signaling link in the signaling link set. The available signaling links of higherpriority will be first used to carry service. Therefore it means the same as the Priority field in MTP Route in thisrespect.
7.6 SCCP DSP
I. Function
The table defines the remote destination signaling point having SCCP signalingrelationship (either associated or quasi-associated) with the home office.
The DSP in this table must be described in [MTP DSP table], but not all MTP DSPsdescribed in [MTP DSP table] need to be added to this table. For example, the MTPDSP of the peer PSTN office described in [MTP DSP table] doesn't have to be addedto this table, but the MTP DSPs describing the peer HLR office and the other MSCoffices on the peer end need to be added to this table.
II. Access
----- Select menu [Singling/SCCP DSP].
The interfaces are shown in Figure 7-7.
Figure 7-7 SCCP DSP table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-10
III. Interface description
The interface description is given in Table 7-6.
Table 7-6 Description of the SCCP DSP table
Field name Meaning Value range Remarks
Serial numberThe index of this table increasesprogressively from 0.
0~255 Required
DSP name Define the name of a corresponding DSP. customized characters Optional
Avail flag Indicating whether the record is valid. Yes, No Required
International DPCThe code of the DSP in the internationalnetwork. Fill 65535 if the DSP is not in theinternational network.
000000~FFFFFF hexadecimalnumber
Required
Internationalstandby DPC
The code of the DSP in the internationalstandby network. Fill 65535 if the DSP is notin the international standby network.
000000~FFFFFF hexadecimalnumber
Required
Domestic DPCThe code of the DSP in the domesticnetwork. Fill 65535 if the DSP is not in thedomestic network.
000000~FFFFFF hexadecimalnumber
Required
Domestic standbyDPC
The code of the DSP in the domesticstandby network. Fill 65535 if the DSP is notin the domestic standby network.
000000~FFFFFF hexadecimalnumber
Required
Standby DPCindex
Index value of the load-sharing signalingpoint to the current signaling point in thetable. 65535 for default.
0~65535 Required
7.7 SCCP SSN
I. Function
The table describes all subsystems of the home office and remote DSPs that haveSCCP relationship with the home office.
II. Access
----- Select menu [Signaling/SCCP SSN].
The interfaces are shown in Figure 7-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-11
Figure 7-8 SCCP SSN table
III. Interface description
The interface description is given in Table 7-7.
Table 7-7 Description of the SCCP SSN table
Field name Meaning Value range Remarks
Serial numberThe index of this table, usually increasingprogressively from 0.
0~799 Required
Subsystem name Customized name of a subsystem. Optional
Avail flag Indicating whether the record is effective. Yes, No Required
Network identifierThe corresponding network number of theDSP to which the subsystem belongs.
International; Internationalstandby; Domestic;Domestic standby
Required
SSNIdentifying the codes of various SCCPsubscribers in one node.
Note 1 Required
DPCThe signaling point code of the node towhich the subsystem belongs.
000000~FFFFFFhexadecimal number
Required
Related subsystem1(~5)
The code of the subsystem with the sameDPC and having signaling relationship withthe record subsystem. A maximum of 5subsystems can be defined. Set asUndefined if there is none.
Undefined, Note 1 Required
Standby subsystemindex
Indicating the index value of the standbysubsystem of the record subsystem. Set as65535 if there is no such index value.
0~65535 Required
Note 1: SCCP management, ISDN user part, OMAP, home location register (HLR), visiting location register (VLR),equipment identification register (EIR), authentication center (AUC), mobile switching center (MSC), CAP applicationpart (CAP), IN application part (INAP), gsmSCF_SSN, SGSN_SSN, GGSN_SSN.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-12
7.8 GT
I. Function
The table is used to translate GT into new addresses through various combinations ofDPC, SSN, OLD-GT, NEWGT, etc.
II. Access
----- Select menu [Signaling/GT].
The interfaces are shown in Figure 7-9.
Figure 7-9 GT table
III. Interface description
The interface description is given in Table 7-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-13
Table 7-8 Description of the GT table
Field name Meaning Value range Remarks
Serial numberThe index of this table, increasingprogressively from 0.
0~4095 Required
Declaration Describe the information. Optional
Avail flag Indicating whether the record is effective. Yes, No Required
Networkidentifier
Indicating what kind of signaling networkthe signaling point is located.
International;International standby;Domestic; Domesticstandby
Required
Translationresult
Indicating different combinations of thenew DPC, SSN and GT, which aretranslated from GT codes.
DPC, DPC+SSN,DPC+OLD_GT,DPC+NEWGT index
Required
GT code Type of GT expressions.10-type 1, 20-type 2, 30-type 3, 40-type 4
Required
Number planIt indicates the numbering mode of theaddress information.
Required,recommanded value:1-ISDN/Telephonynumber plan
Addressinformationindicator
Indicate the attributes of the addressinformation.
Required
Addressinformation
The content of GT code.Differ about various GTcode types
Required
SSNIdentifying the codes of various SCCPsubscribers in one node.
Note 2 Required
DPCThe signaling point code of the node towhich the subsystem belongs.
000000~FFFFFFhexadecimal number
Required
New GT codeindex
If the “Translation result” field isDPC+NEWGT, then the field is effective,indicating the newly translated GT index inthe New GT table.
0~65535, but 65535 isinvalid
Required
Note 1: 0-unknown, 1-ISDN/Telephon number plan, 2-generic numbering plan, 3-data numbering plan, 4-Telexnumbering plan, 5-maritime mobile number plan, 6-land mobile numbering plan, 7-ISDN/mobile numbering plan.Note 2: SCCP management, ISDN user part, operation & maintenance & administration part (OMAP), home locationregister (HLR), visiting location register (VLR), equipment identification register (EIR), authentication center (AUC),mobile switching center (MSC), CAP application part (CAP), IN application part (INAP), gsmSCF_SSN, SGSN_SSN,GGSN_SSN.Note that if the DPC in [SCCP SSN Table] and [GT Table] is not the local signaling point, it must be valid in [SCCPDSP Table], meanwhile, the sub-system in [GT Table] should also be valid in [SCCP SSN Table]. In addition, whenconfiguring [SCCP DSP Table], [SCCP SSN Table] and [GT Table], the configuration of signaling point (includingsignaling point code and network indentifier) should be consistent with that in [Intra-office information table],[Office direction table] and [MTP DSP Table].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 7-14
7.9 New GT
I. Function
The table defines the content of the new GT code translated from the home office GTcode.
II. Access
----- Select menu [Signaling/New GT].
The interface is shown in Figure 7-10.
Figure 7-10 New GT table
III. Interface description
The interface is described in Table 7-9.
Table 7-9 Description of the new GT table
Field name Meaning Value range Remarks
Serial numberIndex of the table, usually increasingprogressively from 0, and corresponding to“New GT Index” in Global Title Translation.
0~499 Required
Avail flag Indicating whether the record is effective. Yes, No Required
Length of new GT codeIndicating the length of the new GT code bytestored in the compressed BCD mode.
0~26 Required
New GT code The content of new GT code.Differs about different GTcode types
Required
7
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-1
8 Alarm
There are data configurations related to alarm on the [Alarm] menu, which are used bysubscribers to control alarms. The menu interface is as shown in Figure 8-1, and itincludes such menu operations as [Alarm parameter configuration], [Alarmenvironment variable], [Alarm information parameter], [Alarm informationexplanation], [Alarm masking], [Analog value configuration], and [Trafficstatistics monitor task].
Figure 8-1 "Alarm" menu interface
8.1 Alarm Parameter Configuration
I. Function
In data management console, control on alarms can be implemented throughmodification of the alarm data in the host, which is fulfilled through on-line modificationof the alarm parameter configuration table.
II. Access
----- Select menu [Alarm/Alarm parameter configuration].
The interfaces are as shown in Figure 8-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-2
Figure 8-2 Alarm parameter configuration table
III. Interface description
The interface description is given in Table 8-1.
Table 8-1 Description of the alarm parameter configuration table
Field name Meaning Value range Remarks
Alarm ID The number of alarm 0~65535 (Note 1) Required
Recovery alarmID
Note 2 0~65535 (Note 1) Required
Alarm nameThe alarm name corresponding to thealarm number
Customized, not more than 34characters
Optional
Sending BAM flag Whether the alarm should be sent to BAM Yes, No Required
Sending alarmbox flag
Whether the fault alarm and recoveryalarm operate the alarm box
Yes, No Required
Sending TMN flagWhether the alarm should be sent to NMcenter
Yes, No Required
Alarm level Note 3critical alarm, major alarm, minoralarm and warning
Required
TMN alarm level Note 4Event alarm, fault alarm, recoveryalarm and debug alarm
Required
TMN alarm classnumber
Information about alarm category that issent to the NM center
Power supply, environment,signaling, trunk, hardware,software and operation
Required
Alarm box alarmclass number
It is used to locate the indicators on thealarm box upon fault alarm/recovery alarm
Note 5 Required
Indication lightoperation
It indicates whether to turn on/off thecorresponding indicators on the alarm boxupon fault/recovery alarms (Note 6)
Yes, No Required
Note 1: 65535 is an invalid alarm number.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-3
(Note 2: The corresponding sequence numbers when fault alarm and recovery alarm occur in pairs. The fault alarmand recovery alarm should occur in pairs. That is to say, if an alarm is a fault alarm, there should be a correspondingrecovery alarm, and vice versa. This field is meaningless to event alarms. The function of this field is to accelerate thequery speed of the host and can not be modified.) need further confirmationNote 3: It indicates the severity of the alarm. If the alarm level is considered improper, it can be modified. If the alarmto be modified is a fault alarm or recovery alarm, the modification should be made in pairs to ensure that thecorresponding fault alarm and recovery alarm are of the same level.There are four alarm levels: critical alarm, major alarm, minor alarm and warning. Critical alarm is the highest andwarning is the lowest. Critical alarm is an overall fault alarm or event alarm that will cause the host to collapse such asMPU fault, NET board fault, clock board fault, etc. Major alarm is a board or line fault alarm or event alarm in part ofthe system, such as subscriber line board fault, digital trunk board fault, etc. Minor alarm is an ordinary fault alarm orevent alarm that tells whether the respective boards or lines are working normally. Warning is for fault alarm or eventalarm.Note 4: The severity of NM alarms. This field can be modified. The fault alarm and recovery alarm can be modified toevent alarm, but they must be modified in pairs. The original event alarm can not be modified to a fault alarm orrecovery alarm. When a fault alarm or recovery alarm is modified to an event alarm, the indicator(s) on the alarm boxwill not be turned on/off.Note 5: Communication between modules, control, network, node communication, signaling, clock, subscriber, trunk,power supply, environment, transmission, database, ticket, call identification, software operation, test alarm,miscellaneous.This field is valid only when "Sending to alarm box" is set to "Yes" and "Alarm category" is set as "Fault alarm" or"Recovery alarm". If the alarm category (class) number of alarm box is considered improper, this field can bemodified.Note 6: If this flag is set to "Yes", when the fault alarm related to an indicator on the alarm box occurs, this indicatorwill be on. When all fault alarms related to the indicator are recovered, this indicator will be off.
8.2 Alarm Environment Variable Configuration
I. Function
It is based on the alarm environment variable configuration table that environmentalarms occur. The setting of this table should depend on actual situation. After this tableis configured, the database in the host can be modified via online setting. When theswitch detects environment changes with an environment variable collector, the alarmmodule will search the Alarm Environment Variable Configuration table, find thecorresponding alarm number, and send the alarm.
II. Access
----- Select menu [Alarm/Alarm environment variable].
The interfaces are as shown in Figure 8-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-4
Figure 8-3 Alarm environment variable configuration table
III. Interface description
The interface description is given in Table 8-2.
Table 8-2 Description of the alarm environment variable configuration
Field Meaning Value range Remarks
Module ID The module in which the alarm is occurred. 1~32 Required
Equipment typeThe type of the device connected with alarmenvironment.
GALM, RSA_1, TSS Required
Board numberThe number of the device in the boards of the sametype.
0~44 Required
Line numberThe sequence number of the access line pairconnecting with the alarm switch when accessing thedevice.
0~15 Required
Effective levelvalue
Whether the level value of the access line should behigh level or low level when alarm is generated.
0: low level, 1: highlevel
Required
Failure alarmname
Note 1.Environment alarm 1~environment alarm 32
Required
Recovery alarmname
Note 1.Environment alarm 1~environment alarm 32
Required
Indicator positionThe location of the alarm indicator on alarm boxwhen alarm occurs.
Note 2 Required
Note 1: The number in the alarm title, plus 20, will be mapped to 21~52 of the "Alarm ID" field in the [Alarmparameter configuration] table, i.e. alarm sequence number. The real name of the environment alarm should befilled in the corresponding "Alarm ID" field of the [Alarm parameter configuration] table. The [Alarm parameterconfiguration] table also determines the level of environment alarm corresponding to the input line, i.e. alarmcategory. Here, environment alarms 1~ 18 can be regarded as fault or recovery alarms while environment alarms 19~32 can only be regarded as event alarms. The environment alarms 1~ 18 pair as follows: environment alarm 1matches environment alarm 2, environment alarm 3 matches environment alarm 4, …. environment alarm 17matches environment alarm 18.Note 2: Backup item, Theft alarm, Humidity, Temperature, Smoke, Fire alarm, Spacer, Battery, Secondary power
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-5
supply, Primary power supply, Total power supply.
8.3 Alarm Information Parameter
I. Function
This table is used to explain and display the fault alarm and recovery alarm at theterminal alarm console. It is generally set by system administrator and can not bemodified by user.
II. Access
----- Select menu [Alarm/Alarm information parameter].
The interface is as shown in Figure 8-4.
Figure 8-4 Alarm information parameter table
III. Interface description
The interface description is given in Table 8-3.
Table 8-3 Description of the alarm information parameter table
Field Meaning Value range Remarks
Alarm ID The number of alarms. 0~65535 (Note 1) Required
Recovery alarm ID Note 2. 0~65535 (Note 1) Required
Key field offsetaddress
The address of the field sent by the host to the terminalalarm console to distinguish different alarms, so thatfault alarm corresponds to recovery alarm.
0~255 (Note 3) Required
Key field byte lengthIt is used to indicate the field byte length of differentalarms.
0~255 (Note 3) Required
Maximum number ofthis alarm
The quantity of alarms that can be sent to the terminalalarm console.
Note 4 Required
Board number askey index
When the alarm is recovered, whether the boardnumber should be used as the index to search for thefault alarm records.
Yes, No Required
Note 1: 65535 is an invalid alarm number.Note 2: The fault alarm and recovery alarm should appear in pairs. That is to say, if the alarm is a fault alarm, thereshould be a corresponding recovery alarm, and vice versa. This field is meaningless to an event alarm. The functionof this field is to accelerate the query speed of the host and it can not be modified.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-6
Note 3: 255 is an invalid value.Note 4: If 0 is filled in, alarms of this category will not be sent to the terminal alarm console. If other figures are filled in,the quantity of alarms transmitted to the terminal is not limited.
8.4 Alarm Information Explanation
I. Function
This table is used to explain and display alarms at the terminal alarm console. All fieldsin this table are set by system administrator except for the [Alarm name] field that canbe modified by user.
II. Access
----- Select menu [Alarm/Alarm information explanation].
The interfaces are as shown in Figure 8-5.
Figure 8-5 Alarm information explanation table
III. Interface description
The interface description is given in Table 8-4.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-7
Table 8-4 Description of the alarm information explanation table
Field Meaning Value range Remarks
Alarm serial number Note 1 0~65535 Required
Alarm name The name corresponding to alarm IDCustomized , not more than34 characters
Optional
Detailed explanationDetailed description of the alarm fordisplay on the terminal alarm console
English character Optional
Parameterdescription
The types and meanings of theparameters of alarms that the host sendsto the background
It differs about differentalarm categories
Required
Number of theparameters
The total number of alarm parameters thatthe host transmits to the background
0~10 Required
Parameter length(1~10)
The number of bytes occupied by eachparameter
0~255 Required
Note 1: [Alarm serial number] of this table, [Alarm ID] of [Alarm parameter configuration table] and [Alarm ID] of[Alarm information parameter table] all have the same meaning.
8.5 Alarm Masking Table
I. Function
The alarm masking table is used to mask certain alarms.
II. Access
----- Select menu [Alarm/Alarm masking table].
The interface is as shown in Figure 8-6.
Figure 8-6 Alarm masking table
III. Interface description
The interface description is given in Table 8-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 8-8
Table 8-5 Description of the alarm masking table
Field name Meaning Value range Remarks
Module ID The module in which the alarm occurs 1~32 Required
Alarm serial number Logical number corresponding to the alarm 0~65535 Required
Alarm box categoryUsed to locate the fault alarm/recoveryalarm indicator in the alarm box
Note 1 Required
Network managecategory
Information of alarm category (class) sentto the NMC
Invalid, Power supply,Environment, Signaling,Trunk, Hardware, Software,run
Required
Alarm level Classification of alarm severityInvalid, Critical alarm,Major alarm, Minor alarm,Warning alarm
Required
Board type Indicates the type of board Note 2 Required
Board number 1Logical sequential number of the board inthis type of boards of the module
0~255 Required
Port ID Communication port number 0~65535 RequiredNote 1: Invalid, Communication between modules, Control, Network, Master node communication, Signaling, Clock,Trunk, Power supply, Environment, Transfer, Database system, Bill, Call identification, Software run, Test alarm, VLR,HLR, Miscellaneous.Note 2: GEMA, GNOD, LAP, GMPU, GALM, GNET, GCKS, GMEM, GDTM, GMC2, GOPT, GDTR, GSIG, iDT, TUP,ISUP, V5TK, PHI, PRA, EM4, MTK, NO7, LPN7, LPV5, LPHI, LPRA, TC, PWC, GDRV, GDTR, GSPT.
8.6 Analog Value Configuration Table
Temporarily not used.
8.7 Traffic Statistics Monitoring Table
Temporarily not used.
8
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-1
9 Charge
The [Charge] menu is related to data configuration for charging so as to control thefunction of charging users. The menu interface is shown in Figure 9-1, including [Localtariff], [Area toll tariff], [International toll tariff], [Default tariff], [Local HLR],[Charging case analysis], [Charging mode analysis], [Meter mode], [Additionalfee mode analysis], [Additional fee combination mode analysis], [Date categoryanalysis], [Week category analysis], [Charge point analysis], and [Meter rate].
Figure 9-1 "Charge" menu interface
9.1 Local Tariff Table
I. Function
This table applies to the local call charging case, mainly used to charge the caller whenmaking a local call.
II. Access
----- Select menu [Charge/Local tariff].
The interface is as shown in Figure 9-2.
Figure 9-2 Local tariff table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-2
III. Interface description
The interface is described in Table 9-1.
Table 9-1 Description of the charging point analysis table
Field name Meaning Value range Remarks
Call prefix Prefix to the called number. Required
Roaming type The roaming type of the caller.Local subscriber, Roamingsubscriber category
Required
Charge caseCharging type, used to further query the chargingmode and additional fee charging mode.
0~511 Required
9.2 Area Toll Tariff Table
I. Function
This table is used to determine the national toll call charging according to the toll areacode.
II. Access
----- Select menu [Charge/Area toll tariff].
The interface is as shown in Figure 9-3.
Figure 9-3 Area toll tariff table
III. Interface description
The interface is described in Table 9-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-3
Table 9-2 Description of the area toll tariff table
Field name Meaning Value range Remarks
Area code National toll call area code Required
Charging caseCharging type, used to further query the chargingmode and additional fee charging mode
0~511 Required
Area name City name of the corresponding toll area code Required
9.3 International Toll Tariff Table
I. Function
This table is used to determine the international toll call charging case according to thecountry code.
II. Access
----- Select menu [Charge/International toll tariff].
The interface is as shown in Figure 9-4.
Figure 9-4 International toll tariff table
III. Interface description
The interface is described in Table 9-3.
Table 9-3 Description of the international toll tariff table
Field name Meaning Value range Remarks
Country code Code for a country Required
Charging caseCharging type, used to further query the charging modeand additional fee charging mode
0~511 Required
Country name Name of the country corresponding to a country code Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-4
9.4 Default Tariff Table
I. Function
This table is used to determine the default tariff corresponding to the charging case.
II. Access
------ Select menu [Charge/Default tariff table].
The interface is as shown in Figure 9-5.
Figure 9-5 Default tariff table
III. Interface description
The interface is described in Table 9-4.
Table 9-4 Description of the international toll tariff table
Field
nameMeaning Value range Remarks
Tariff typeTariff types, classified according to differentcharging requirements
Default tariffs respectively for localusers, roaming users, national tollusers, international toll users
Required
Charge caseCharging type, used to further query thecharging mode and additional fee chargingmode (Note 1)
0~511 Required
Note 1: Make sure that all tariff types correspond to charging cases during the data configuration.
9.5 Local HLR Table
I. Function
This table is used to determine whether the subscriber is a local HLR user according tothe MSISDN number.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-5
II. Access
----- Select menu [Charge/Local HLR table].
The interface is as shown in Figure 9-6.
Figure 9-6 Local HLR table
III. Interface description
The interface is described in Table 9-5.
Table 9-5 Description of the local HLR table
Field name Meaning Remarks
HLR number &province code map
Local HLR table. If a user's MSISDN number is not mapped in this table,then the user is regarded as a roaming subscriber from outside.
Required
9.6 Charging Case Analysis Table
I. Function
This table is used to query the charging mode and additional fee charging modeaccording to the charging case.
II. Access
----- Select menu [Charge/Charging case analysis table].
The interface is as shown in Figure 9-7.
Figure 9-7 Charging case analysis table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-6
III. Interface description
The interface is in Table 9-6.
Table 9-6 Description of the charging case analysis table
Field name Meaning Remarks
Charging caseCharging type, used to further query the charging mode and additionalfee charging mode.
Required
Charging modeWith the help of date type, query the metering mode in [Chargingmode analysis table].
Required
Additional fee chargingmode
With the help of date type, query the additional fee combination modeand tariff discount in [Additional fee mode analysis table].
Required
Minimum time of chargingunit(s)
Normally 60 seconds. Required
9.7 Charging Mode Analysis Table
I. Function
With the help of charging mode and date type, as well as the current location, themetering mode and tariff discount can be queried.
II. Access
----- Select menu [Charge/Charging mode analysis table].
The interfaces are as shown in Figure 9-8.
Figure 9-8 Charging mode analysis table
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-7
III. Interface description
The interfaces are described in Table 9-7.
Table 9-7 Description of the charging mode analysis table
Field name Meaning Remarks
Charging modeCharging type, used to further query the metering mode and tariffdiscount
Required
Data typeThere are three types: "Working day", "Holiday eve" and "Holiday".Charging on holiday could differ from charging on a working day
Required
The 1st time zonehandover point
The end point of the 1st time zone; after this point, it is the 2nd timezone and the 2nd time zone metering mode and tariff discount shouldbe adopted. In case of tariff change, the network should inform theuser of this tariff handover
Required
The 1st time zonemetering mode
The metering mode adopted in the 1st time zone Required
The 1st time zonediscount
Tariff discount (%) Required
The 2nd time zonehandover point
The end point of the 2nd time zone; after this point, it is the 3rd timezone and the 3rd time zone metering mode and tariff discount shouldbe adopted. In case of tariff change, the network should inform theuser of this tariff handover
Required
2nd time zone meteringmode
The metering mode adopted in the 2nd time zone Required
The 2nd time discount Tariff discount (%) Required
The 3rd time zonehandover point
The end point of the 3rd time zone; after this point, it is the 1st timezone and the 1st time zone metering mode and tariff discount shouldbe adopted. In case of tariff change, the network should inform theuser of this tariff handover
Required
3rd time zone meteringmode
The metering mode adopted in the 3rd time zone Required
The 3rd time zonediscount
Tariff discount (%) Required
Detailed bill tariff (Min) Detailed bill tariff (Min) Required
9.8 Meter Mode Table
I. Function
This table describes a meter's pulse generation in a specified metering mode.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-8
II. Access
----- Select menu [Charge/Meter mode table].
The interface is as shown in Figure 9-9.
Figure 9-9 Metering mode table
III. Interface description
The interface is described in Table 9-8.
Table 9-8 Description of the metering mode table
Field name Meaning Remarks
Metering mode Metering mode ID Required
TA (second) PB pulses generated in the first TA seconds. Required
TB (second) PB pulses generated in the first TB seconds Required
PB (second)A single PB pulse counts as an AOC charging unit. Set the price of anAOC charging unit on the mobile phone (station)
Required
9.9 Additional Fee Mode Analysis Table
I. Function
This table is used to determine how to divide time zones in the case of a specific datetype, the additional fee charging mode as well as the discount in each time zone.
II. Access
----- Select menu [Charge/Additional fee mode analysis table].
The interfaces are as shown in Figure 9-10.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-9
Figure 9-10 Additional fee mode analysis
III. Interface description
The interfaces are described in Table 9-9.
Table 9-9 Description of the additional fee mode analysis
Field name Meaning Remarks
Additional feecharging mode
With the help of date type, the additional fee charging mode anddiscount can be queried
Required
Data typeThere are three types: "Working day", "Holiday eve" and "Holiday".Charging on holiday could differ from charging on a working day.
Required
The 1st time zonehandover point
The end point of the 1st time zone; after this point, it is the 2nd timezone and the 2nd time zone metering mode and tariff discount should beadopted. In case of tariff change, the network should inform the user ofthis tariff handover
Required
1st time zonecombination mode
Describe the different additional fee charging types in the case of thistime zone additional fee charging mode. Each combination has at mostfour types of additional fee charging and the total additional fee is thesum of the four additional fees
Required
The 1st time zonediscount
Tariff discount in this time zone (%) Required
The 2nd time zonehandover point
The end point of the 2nd time zone; after this point, it is the 3rd timezone and the 3rd time zone metering mode and tariff discount should beadopted. In case of tariff change, the network should inform the user ofthis tariff handover
Required
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-10
Field name Meaning Remarks
2nd time zonecombination mode
Describe the different additional fee charging types in the case of thistime zone additional fee charging mode. Each combination has at mostfour types of additional fee charging and the total additional fee is thesum of the four additional fees
Required
The 2nd time zonediscount
Tariff discount in this time zone (%) Required
The 3rd time zonehandover point
The end point of the 3rd time zone; after this point, it is the 1st time zoneand the 1st time zone metering mode and tariff discount should beadopted. In case of tariff change, the network should inform the user ofthis tariff handover
Required
3rd time zonecombination mode
Describe the different additional fee charging types in the case of thistime zone additional fee charging mode. Each combination has at mostfour types of additional fee charging and the total additional fee is thesum of the four additional fees
Required
The 3rd time zonediscount
Discount in this time zone (%) Required
9.10 Additional Fee Combination Mode Analysis Table
I. Function
This table is used to define the constituents of various additional fees in an additionalfee combination mode. The ultimate amount of additional fees is the sum of additionalfees of the same type.
II. Access
----- Select menu [Charge/Additional fee combination mode analysis table].
The interfaces are as shown in Figure 9-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-11
Figure 9-11 Additional fee combination mode
III. Interface description
The interfaces are described in Table 9-10.
Table 9-10 Description of the additional fee combination mode
Field name Meaning Remarks
Combination of additional fee Combination of various additional fees Required
Additional fee type 1 (~4)Two types: 1) Additional fee total metering number 2)Additional fee metering number per communication pulse
Required
Additional fee metering number1 (~4)
Metering numbers corresponding to additional fee types 1~4 Required
9.11 Date Category Analysis Table
I. Function
This table is used to define the date type of each day in a year.
II. Access
----- Select menu [Charge/Date category analysis table].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-12
The interface is as shown in Figure 9-12.
Figure 9-12 Date category analysis table
III. Interface description
The interface is described in Table 9-11.
Table 9-11 Description of the date category analysis table
Field name Meaning Remarks
Month Month Required
Day Date Required
Date type Indicate whether it is a "Working day", "Holiday eve" or "Holiday" Required
9.12 Week Category Analysis Table
I. Function
This table is used to define each day of a week as "Working day", "Holiday eve" or"Holiday".
II. Access
----- Select menu [Charge/Week category analysis table].
The interface is as shown in Figure 9-13.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-13
Figure 9-13 Week category analysis table
III. Interface description
The interface is described in Table 9-12.
Table 9-12 Description of the week category analysis table
Field name Meaning Remarks
Week Monday ~ Sunday Required
Date type Indicate whether it is "Working day", "Holiday eve" or "Holiday" RequiredNote: The default date type for every single day is "Working day". It is recommended that "Holiday" or "Holiday eve"be marked in [Week Category Analysis] and [Date Category Analysis]. If the date types obtained from these twotables are not the same, then follow this priority order: 1) "Holiday" 2) "Holiday eve" 3) "Working day". For example,suppose January 1 is Friday, and it is "Holiday" according to [Date Category Analysis] but "Holiday eve" accordingto [Week Category Analysis], then it counts as "Holiday".
9.13 Charge Point Analysis Table
I. Function
This table is used to control the start timing point (billing start point) of a call.
II. Access
----- Select menu [Charge/Charge point analysis table].
The interface is as shown in Figure 9-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-14
Figure 9-14 Charge point analysis table
III. Interface description
The interface is described in Table 9-13.
Table 9-13 Description of the charge point analysis table
Field name Meaning Remarks
Call source code The number of a subscriber group with the same call attributes. Required
Destination code Indicate whether it is "Working day", "Holiday eve" or "Holiday" Required
Billing start pointIndicate the billing start points: including "Caller off-hook", "Trunkoccupied", "Ringing" and "Called replying"
Required
Billing end pointIndicate the billing end points: including "Caller hanging up", "Calledhanging up", "Either party hanging up", "Second party hanging up" and"Controlling party hanging up"
Required
Ringing delay(s)When the billing start point is in the form of "Ringing", it indicates howmuch time (starting from ringing) is delayed before the billing reallystarts, and the default value is 255 seconds
Required
9.14 Meter Rate Table
I. Function
This table is used to define each metering table and the unit price (tariff) of a chargingpulse.
II. Access
----- Select menu [Charge/Meter rate table].
The interface is as shown in Figure 9-15.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 9-15
Figure 9-15 Meter rate table
III. Interface description
The interface is described in Table 9-14.
Table 9-14 Meter rate table
Field name Meaning Remarks
Charging metername
Only including trunk charging pulse, i.e., the charging pulse the switchreceives from the outgoing trunk
Required
Tariff Pulse unit price Required
9
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-1
10 Intelligence Service
The "Intelligence service" menu involves a special configuration related to IN-service asshown in Figure 10-1. It includes [Office TDP configuration], [TDP access code], [INservice key and serial number], [IN service constraint relation], [SCPconfiguration], [SSP specialized resource data], [SPT voice code], [SCP physicaladdress], [IN service caller number description], [SRM module resourcesearching], [SSP physical address], [SCP addressing], [Special number], [INservice attribute], [CAP edition consultation], [Tel number continue projectconfiguration] and [SCP address and ID].
Figure 10-1 "Intelligence service" menu interface
10.1 Office TDP Configuration Table
I. Function
This table is used to set time, standard and working mode of DP triggering andmeasuring.
II. Access
----- Select menu [Intelligence service/Office TDP configuration table].
The interface is as shown in Figure 10-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-2
Figure 10-2 Office TDP configuration table
III. Interface description
The interface is described in Table 10-1.
Table 10-1 Description of the office TDP configuration table
Field name Meaning Value range Remarks
DP numberAt which point TDP is triggered andmeasured
0~255Required
Recommended value: 3
DP standardnumber
By which TDP standard IN calls aremeasured and triggered
Note 1Required
Recommended value:access code
Standarddescriptionindex
Note 2 0~255 Required
Service keyindex
Service key index corresponding to the"Service key index" in [IN service key andserial number]
0~255 Required
R/N flag Note 3 Request, NoticeRequired
Recommended value:request
Auxiliary flag
It indicates whether the systen wirks ininitiative SSP mode or auxiliary SSP modewhen processing TDP triggering. Select“YES” for auxiliary SSP mode while “NO” forinitiative mode. Configuration should bebased on the actual networking, and usuallythis flag is set as “NO".
Yes, NoRequired
Recommended value:No
Mode ofaccess to SCP
Access to home SCP
Access to SCP withaccess code
Note 1: access code, attribute code, called number, specific trigger, specified number string, specified B Channel flag,attribute activation indication. Currently, only the "access code" standard is provided.Note 2: Index corresponding to the TDP standard described by the "DP standard number". As only the access code
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-3
standard is provided, this "Standard description index" just corresponds to the "Access code index" in [TDP accesscode].For instance, when the user dials 13800138000, the system will first trigger Intelligence service according to [OfficeTDP configuration table]. Then SSP will report DP3 to SCP. If the "DP standard number" in [Office TDPconfiguration table] is "Access code", the "Standard description index" refers to the "Access code index" in [TDPaccess code table]. Then the system will search whether there is a record with "Access code" as 13800138000according to the "Access code index". If the record exists, the recharging flow will be triggered according to theconfiguration in [TDP access code table]. Please note that 13800138000 is the Recharging Administration Numberin China, it is different in other nations.Note 3: Whether the system is in the "Request" (R) mode or in the "Notice" (N) mode when handling the TDP trigger.If it is in the R mode, the system will not go further until it receives a new command after triggering the TDP andsending such information as initial DP to the SCP. If it is in the N mode, the system will automatically move to the nextstep without waiting for the command from the SCP after triggering the TDP and sending the initial DP information tothe SCP.
10.2 TDP Access Code Table
I. Function
This table is used to set some attributes of the TDP access code.
II. Access
----- Select menu [Intelligence service/TDP access code table].
The interface is as shown in Figure 10-3.
Figure 10-3 TDP access code table
III. Interface description
The interface is described in Table 10-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-4
Table 10-2 Description of the TDP access code table
Field name Meaning Value range Remarks
Access code index
Sequence number of this record in thetable and key word to the table query.The numbers should be in the ascendingorder and unique in this table
0~255 Required
Access code Note 1 Number of less than 18 digits Required
Access code length Describe the length of the access code 1~18 Required
Database startposition
Note 2 1~11, 255 Note 3 Required
Length of databasefield
Intercepted number length 1~11, 255 Note 4 Required
Note 1: In the call number, it stands for the attribute code for the IN-service call. This IN-service key corresponds tothe "Service key" field in [IN service key and serial number]. When an intelligent call is originated, the system willintercept the called number from the very beginning (the intercepted length is specified in the "Access code length"field of this table), and compare this intercepted number with the access code. If they match each other, thecorresponding intelligent call is triggered; otherwise, this intelligent call will fail. For example, if the access code is13800138000, the access code length is 11, and the dialed number is 13800138000, then the system will decideaccordingly that the subscriber is making a mobile intelligent call with the access code of 13800138000.Note 2: A digit (position) of the subscriber's dialed number. The system intercepts from this digit (position) a numberof a certain length (the length is specified in the "Length of database field") to obtain a database number. With thisdatabase number as a clue, query [SCP configuration] table to determine which SCP to process the call. If 1 is filledin the field, it means the number is intercepted from the very beginning; if 2 is filled in the field, it means the number isintercepted from the second position (digit), and so on and so forth; if 255 is filled in the field, it means the number isnot intercepted. The intelligent call of the same Intelligence service can be sent to different SCPs for processing viathe setting of this field.Note 3: If 255 is filled in, it means the number is not intercepted and the default database should be used.Note 4: If 255 is filled in the "Database start position", this field should be filled in with 255, too.
10.3 IN Service Key and Serial Number Table
I. Function
This table is used to set the IN-service key value and the corresponding index number.
II. Access
----- Select menu [Intelligence service/IN service key and serial number table].
The interface is as shown in Figure 10-4.
Figure 10-4 IN service key and serial number
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-5
III. Interface description
The interface is explained in Table 10-3.
Table 10-3 Description of IN service key and serial number
Field name Meaning Value range Remarks
Service keyindex
An index value corresponding to the service key and akey word to the table query. The values should be inthe ascending order and unique in the table,corresponding to the "Service key index" field of the"Office TDP configuration table"
0~255 Required
Service keyA whole number (An integer) used to identify theservice type of an intelligent call
0~255 (Note 1)Required
Recommended value: 2Note 1: The currently provided service keys are 1 and 2. Service key 1 stands for prepaid service; while service key 2stands for the management process (e.g. value-charged, loss report, etc.). In this table, only Service key 2 is filled in.
10.4 IN Service Constraint Relation Table
This table is temporarily not used.
10.5 SCP Configuration Table
I. Function
The table defines which specific SCP each IN call is related to.
II. Access
----- Select menu [Intelligence service/SCP configuration table].
The interfaces are as shown in Figure 10-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-6
Figure 10-5 SCP configuration table
III. Interface description
The interface description is given in Table 10-4.
Table 10-4 Description of the SCP configuration table
Field name Meaning Value range Remarks
Service keyAn integer to indicate what kind ofservice a certain IN call is
0~255Required
Recommendedvalue: 1
Database numberThe corresponding database No. ofservice key
0~65535 ( Note 1) Required
SCP0(~15)
Indicating whether the IN service isrelated to SCP No. 0 (or 1...15). TheSCP number corresponds to “SCPNumber” in SCP Physical Address
None: unrelated to the SCP;have: related to the SCP; notinstalled: the SCP is not installed
Required
Note 1: If the "Database Start Position" field value in [TDP access code] is 255 (indicating that default database isused), fill 65535 in "Database Number"; If not (indicating that there is database No. in the access code), fill thecorresponding database No. in "Database Number".
10.6 SSP Specialized Resource Data Table
I. Function
This table is used to describe which modules have playback and number-receivingcapabilities of an IN service corresponding to the service key.
II. Access
----- Select menu [Intelligence service/SSP specialized resource data].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-7
The interface is as shown in Figure 10-6.
Figure 10-6 SSP specialized resource data
III. Interface description
The interface is described in Table 10-5.
Table 10-5 Description of the SSP specialized resource data table
Field name Meaning Value range Remarks
Service keyAn integer used to identify the service type ofan IN call
0~255Required
Recommended value: 1, 2
Module IDID of the module with the IN service functioncorresponding to the service key
0~255 (Note 1) Required
Note 1: When the module ID is 255, it means all modules have playback and number-receiving capabilities of thisservice.
10.7 SPT Voice Code Table
I. Function
When SPT board is used for voice-playing, make sure the voice chip has been installedon the board, with each piece of voice information corresponding to one recording codeand one voice-playing code on SPT board. If voice-playing is required during callprocess, system will search the SPT voice-playing code of the requested piece on SPTboard according to the voice code specified in service flow. Then SPT board will playthe corresponding voice information according to the SPT voice-playing code. IfCQ01SPT board is in use, configuration in this table is required, and the data shouldcome from the voice recorder. If CQ02SPT board is in use, no manual configuration isneeded, since the voice code has been set during dynamic voice data loading, and thecontents of the table can be queried.
II. Access
----- Select menu [Intelligence service/SPT voice code table].
The interface is as shown in Figure 10-7.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-8
Figure 10-7 SPT voice code table
III. Interface description
The interface is described in Table 10-6.
Table 10-6 Description of the SPT voice code table
Field name Meaning Value range Remarks
Record codeAccess code of this voice. It is used to identify thevoice to be played back between SCP and SSP
00000000~FFFFFFFF Required
Playback codeInternal code in the SPT board for this voice,according to which the SPT board plays back thevoice
0~65535 Required
Voice contentnotification
Describe the content of thisvoice Optional
10.8 SCP Physical Address Table
I. Function
The table is used to configure the physical address, the addressing mode of each SCPand other information.
II. Access
----- Select menu [Intelligence service/SCP physical address table].
The interfaces are as shown in Figure 10-8.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-9
Figure 10-8 SCP physical address table
III. Interface description
The interface description is given in Table 10-7.
Table 10-7 Description of the SCP physical address table
Field name Meaning Value range Remarks
SCP serialnumber
It specifies one number for one SCP. The numberincreases progressively from 0
0~255 Required
DPC flagIndicating whether there is DPC in the SCPphysical address. Select "No" if the SCP addressis in the GT format; Otherwise, select "Yes".
Yes, No Required
SSN flag
Indicating whether there is SSN in the SCPphysical address Select "No" if the SCP address isin the GT format; select "Yes" if the SCP addressis in the signalling point code format.
Yes, No Required
GT type
The type of GT. Select "without" if the SCPphysical address is in the signaling point codeformat; if it is in the GT format, select thecorresponding GT type, which is usually type 4
Without, GT type 1,GT type 2, GT type 3,GT type 4
Required
Route flag is notexisting
Indicating the SCP physical address format.Select "addressing by GT" if it is a GT format;select "addressing by DPC" if it is a signaling pointcode format
addressing by GT,addressing by DPC
Required
DPC address Note 10~224-1 hexadecimalnumber
Required
Net ID Network ID of the SCP physical address
1: international; 2:international standby;3: domestic; 4:domestic standby
Required
Recommendedvalue: 2
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-10
Field name Meaning Value range Remarks
SSNSSN is the subsystem number used to identifydifferent SCCP subscribers in one signaling node
Note 2
Required
Recommendedvalue: CAPapplication part(CAP)
GT length The byte length of GT content (Note 1) 0~26 Required
GT contentThe GT code if "GT Type" is set withcorresponding GT type (Note 1)
Differs about differentGT types
Required
Note 1: Fill DPC address of SCP in the "DPC Address" field if the SCP physical address is in the signaling point codeformat. The highest 8 bits are the main signaling area code, and values in "GT Length" field and "GT connect" fieldare invalid; if the SCP physical address is in the GT format, values in the "DPC Address" field are invalid, and theSCP physical address should be the value of the "GT content" field in this table.Note 2: SCCP management, ISDN user part, operation & maintenance & administration part (OMAP), CAPapplication part (CAP), home location register (HLR), mobile switching center (MSC).
10.9 IN Service Caller Number Description Table
Currently this table is not used.
10.10 SRM Module Resource Searching Table
I. Function
This table is used to configure the resources sharing mode in each module, so thatwhen the resource in a module is used up or unavailable, the resource in any othermodule can be used.
II. Access
----- Select menu [Intelligence service/SRM module resource searching table].
The interfaces are as shown in Figure 10-9.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-11
Figure 10-9 SRM module resource searching
III. Interface description
The interfaces are description in Table 10-8.
Table 10-8 Description of SRM module resource searching
Field name Meaning Value range Remarks
Module IDID of the module which needs to use theshared resources
1~160 Required
Resource ID Resource this module needs to use Note 1 Required
Configuration status Indicate whether this resource existsResource not existing,Resource available,Resource unavailable
Required
Search modeMode of searching for the resource invarious modules
Fixed search mode,rotational search mode(Note 2)
Required
The 1st searchmode
ID of the module to be searched 1~16, 255 (Note 3) Required
Search mode 2(~16) ID of the module to be searched 1~16, 255 (Note 3) OptionalNote 1: Usually each module is configured with 3 records in this table. The respective Resource ID are Start voicecode On SPT card, DIN and SRM free control block. And the configuration states are all set as resource available.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-12
Note 2: If the fixed search mode is selected, the search starts from the first search module every time; if the rotationalsearch mode is selected, the first time search starts from the first search module, the second time search starts fromthe second search module, the next time search starts from the third search module, and so on.Note 3: 255 is an invalid module ID. The system will stop searching when module ID 255 is found.
10.11 SSP Physical Address Table
I. Function
This table is used to configure the SSP physical address, addressing mode, etc. Makesure that the SCP physical address format should be the same with the SSP physicaladdress format; otherwise SSP can not communicate with SCP normally.
II. Access
----- Select menu [Intelligence service/SSP physical address table].
The interfaces are as shown in Figure 10-10.
Figure 10-10 SSP physical address table
III. Interface description
The interfaces are described in Table 10-9.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-13
Table 10-9 Description of the SSP physical address table
Field name Meaning Value range Remarks
SSP serialnumber
Assign a number to every SSP. It starts with0 and is in the ascending order.
0~255 Required
DPC flagIndicate whether DPC exists in the SSPaddress. If the SSP address format is a GTformat, select "No"; otherwise select "Yes"
Yes, NoRequired
Recommended value: No
SSN flag
SSN.Indicate whether SSN exists in the SSPaddress If the SSP address format is a GTformat, select "No"; if the SSP addressformat is a signalling point code format,select "Yes".
Yes, NoRequired
Recommended value:Yes
GT type
The type of GT. Select "without/none" if theSSP physical address is in the signalingpoint code format; if it is in the GT format,select the corresponding GT type, which isusually type 4
Without/none, GT type1, GT type 2, GT type3, GT type 4
Required
Route flag
Indicating the SSP physical address format.Select "GT Addressing" if it is GT format;select "DPC Addressing" if it is signalingpoint code format
addressing by GT,addressing by DPC
Required
Note 1
DPC address Note 10~224-1 hexadecimalnumber
Required
Network ID Network ID of the SSP physical address
1: international; 2:international standby;3: domestic; 4:domestic standby
Required
Recommended value: 3
SSNSSN is the subsystem number used toidentify different SCCP subscribers in onesignaling node
Required Recommendedvalue: CAP applicationpart (CAP)
GT length The byte length of GT content (Note1) 0~26 Required
GT contentThe GT code if "GT Type" is set with thecorresponding GT type (Note 1)
Differs about differentGT types
Required
Note 1: If the SSP physical address is in the signaling point code format, the DPC address of SSP should be filled inthe "DPC address" field. The highest 8 bits are the main signaling area code, and values in the "GT length" field and"GT content" field are invalid; if the SSP physical address is in the GT format, values in the "DPC address" field areinvalid, and the SSP physical address should be the value of the "GT content" field in this table.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-14
10.12 SCP Addressing Table
I. Function
The table is used to specify the SCP physical address, and this SCP controls the callsof subscribers in a specific IN service number segment.
II. Access
----- Select menu [Intelligence service/SCP addressing table].
The interfaces are as shown in Figure 10-11.
Figure 10-11 SCP addressing table
III. Interface description
The interfaces are description in Table 10-10.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-15
Table 10-10 Description of SCP addressing table
Field name Meaning Value range Remarks
First MSISDN, LastMSISDN
The number segment from the startMSISDN number to the end MSISDNnumber, which is specially allocated bytelecom operator to IN service users
ISDN number of mobilephone
Required
SCP addressThe GT format address of SCP bearingsubscribers of this number segment
Differs with different GTtypes
Required
Caller service key Caller service key of prepaid service1~255
NOTE1
Required
Recommendedvalue: 1
Called service key Called service key of prepaid service 1~255Required
Recommendedvalue: 1
Note1: Service Key is determined by SPC configuration. Usually it is set as 1 for PPS service.
10.13 Special Number Table
I. Function
The table stores special numbers that can be connected directly without reportinginformation to SCP, so as to realize special call service.
II. Access
----- Select menu [Intelligence service/Special number table].
The interface is as shown in Figure 10-12.
Figure 10-12 Special number table
III. Interface description
The interface is described in Table 10-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-16
Table 10-11 Description of the special number table
Field name Meaning Value range Remarks
Special number Special service number ISDN number Required
10.14 IN-service Attribute Table
I. Function
The table can strip called number prefixes and identify the current position of the callerto facilitate charging.
II. Access
----- Select menu [Intelligence service/IN service attribute table].
The interface is shown in Figure 10-13.
Figure 10-13 IN service attribute table
III. Interface description
The interface is described in Table 10-12.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-17
Table 10-12 Description of the IN service attribute table
Field name Meaning Value range Remarks
Number prefixPut before called number to identify callerposition to ensure correct charging
2~9, 20~99 Required
Subscriber attribute Specifying who is IN service subscriberCaller, called,unknown type
Required Recommendedvalue: unknown type.
Local call prefix
Select according to the caller's location. Ifthe caller is in the local network where theMSC is located, select "Yes"; if the caller isin the local network where the MSC is notlocated, select "No"
Yes, NoRequired
Recommended value:Yes
Length of prefix Prefix digits of the subscriber number 1~2 Required
Area codeThe toll area code for the local networkwhere the current caller is located, that is,the caller's current position
A number of lessthan 6 digits
Required
10.15 CAP Edition Consultation Table
I. Function
The table supports the on-line upgrading of the SCP CAP version.
II. Access
----- Select menu [Intelligence service/CAP edition consultation table].
The interface is as shown in Figure 10-14.
Figure 10-14 CAP edition consultation table
III. Interface description
The interface is described in Table 10-13.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-18
Table 10-13 Description of the CAP edition consultation table
Field name Meaning Value range Remarks
SCP numberCorresponding to the SCP number of therelated CAP version, usually starting from0
0~255 Required
SCP addressThe GT format physical address of therelated SCP
Differs about different GTcode formats
Required
CAP versionnumber
The CAP version supported by the SCP CAP Phase I, CAP Phase II Required
10.16 Tel. Number Continue Project Configuration Table
I. Function
This table is used to set the interval mode between numbers when voice informationsuch as telephone number is announced to the user by MSC/SSP. For instance,number 123456789 can be read as either 123/456/789, or 1234/5678/9.
II. Access
----- Select menu [Intelligence service /Tel. number continuum projectconfiguration table].
The interface is as shown in Figure 10-15.
Figure 10-15 Tel Number Continueum Project Configuration table
III. Interface description
The interface is explained described in Table 10-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 10-19
Table 10-14 Description of the Tel Number Continuum Project Configuration table
Field name Meaning Value range Remarks
Number of digits The digits of the number to be announced. Required
Group1~Group7Numbers should be grouped by continuous ones,and altogether 7 groups are allowed.
Required
10.17 SCP Address and ID Table
I. Function
This table is used to indicate the correspondence between the SCP address and theSCP ID.
II. Access
----- Select menu [Intelligence service/SCP address and ID table].
The interface is as shown in Figure 10-16.
Figure 10-16 SCP address and ID table
III. Interface description
The interface is described in Table 10-15.
Table 10-15 Description of the SCP address and ID table
Field name Meaning Value range Remarks
SCP addressGT code physical address corresponding tothe SCP
Differ about different GT codes Required
SCP flag Serial number corresponding to the SCP BCD code of 1~10 digits RequiredNote: configuration of this table is not required when only single SCP exists.
10
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-1
11 Operations
The Data Management System of the M900/M1800 MSC Terminal System provides the"Operations" function. As an operation tool for the tremendous database, it can easilyadd, modify and delete any data items in the switching system and terminal system, aswell as printing data and converting formats of the data between the two systems.
The "Operations" menu interface is shown in Figure 11-1.
Figure 11-1 "Operations" menu interface
11.1 Record Operations
I. Function
This table is used for operating the individual record in the data table files, including fouroperations: append, delete, copy and paste. All functions have their correspondingoperation shortcut keys and shortcut icons on the tool bar.
II. Access
----- Select menu [Operations/Record operations].
The interface is shown in Figure 11-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-2
Figure 11-2 Record operations menu interface
III. Interface description
The interface is described in Table 11-1.
Table 11-1 Record operation descriptions
Submenu name Function Shortcut key
Append Append one record with a default value behind the existing record <Ctrl+N>
DeleteDelete one selected record. It can be seen that the font of this recordbecomes dashed and its color turns gray
<Ctrl+T>
Copy Copy the selected record onto the clipboard <Ctrl+C>
Paste Copy the content on the clipboard onto the current record <Ctrl+V>
Note:
All these functions should be performed on the data table files, so only when a data table file in the maininterface is opened, can the above operations be valid.
11.2 Table Operations
This table is used for operating the data table files, including ten items: Commit,Rollback, Undo, Query, Query Release, Make Invisible, Sort, Locate to, Pack and BatchOperation. There are operation shortcut keys corresponding to all the functions, andtool buttons are also provided on the toll bar for some functions.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-3
Select the menu [Operations/Table operations] to display the interface as shown inFigure 11-3.
Figure 11-3 Table operations menu interface
11.2.1 Commit
I. Function
This operation is used to save all modified records without exiting from the currenttable.
II. Access
----- Select menu [Operations/Table operations/Commit].
----- Click the shortcut icon .
----- Use the shortcut key <Ctrl+W>.
Note:
In the description of "Access" in this chapter, the menu mode, shortcut icon mode and shortcut key mode(if available) will be given at the same time, following the symbol"--". It should be noted that therelationships between respective entering modes following the symbol"--" are in parallel, instead of that ofsequential procedures.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-4
11.2.2 Rollback
I. Function
This operation is to withdraw all the operations after the last data commitment.
II. Access
----- Select menu [Operations/Table operations/Rollback].
----- Click the shortcut icon .
----- Use the shortcut key <Ctrl+R>.
11.2.3 Undo
I. Function
This operation is to withdraw the operation performed just now.
II. Access
----- Select menu [Operations/Table operations/Undo].
----- Click the shortcut icon .
----- Use the shortcut key <Ctrl+U>.
11.2.4 Query
I. Function
This operation is used to query the records in the data table files according to the setconditions.
II. Access
----- Select menu [Operations/Table operations/Query].
----- Click the shortcut icon .
----- Use the shortcut key <Ctrl+Q>.
----- Double click the head of a field with the right button, i.e., the title bar of this field inthe current table.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-5
III. Interface description
Query conditions need to be set before the query. The setting dialog box is shown inFigure 11-4.
Figure 11-4 Query operation dialog box
The meaning of respective items in the query operation dialog box are described asfollows:
Query Fields: it is a pull-down list box and it includes all the fields of the table to bequeried by subscribers. The items to query can be selected with the cursor.
Condition: it is a pull-down list box and it includes six comparison operators, whichrespectively are " =", "!=" (not equal to), "<", ">", "<=" (less than or equal to), ">="(greater than or equal to). Subscribers can select any item with the mouse
Query Values: input values that satisfy the query conditions.
Append to List: put the field, condition and value into "Query by the followingconditions" box. It should be pointed out that the query conditions can come into effectonly when they are put into the "Query by the following conditions" box by using"Append to List".
And: it means that there are multiple query conditions and all the query conditions mustbe satisfied.
Or: it means that there are multiple query conditions and only one of them needs to besatisfied.
Clear All: clear the conditions in "Query by the following conditions" box and input newquery conditions again.
Delete: clear the conditions selected with the cursor in "Query by the followingconditions" box and input new query conditions again.
OK: start to query all the records that satisfy the conditions from the table.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-6
11.2.5 Query Release
I. Function
After the query result is obtained, perform this function to exit from the query table.
II. Access
----- Select menu [Operations/Table operations/Query release].
----- Use the shortcut key <Ctrl+F>.
11.2.6 Make Invisible
I. Function
This function is used to make the unnecessary fields (domain/item) temporarily invisible(masked) in the display table.
II. Access
----- Select menu [Operations/Table operations/Make invisible].
----- Click the shortcut icon .
----- Use the shortcut key <Ctrl+K>.
III. Interface description
The Make Invisible dialog box is shown in Figure 11-5.
Figure 11-5 "Select visible fields" dialog box
The content in Figure 11-5 means to mask the three fields of signal tone index, re-analysis and failure cause code in the [Prefix processing table]. Select the three fields(turn blue when selected) in "Visible fields" in the dialog box, then click the arrow key
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-7
pointing to the right. And these three fields can be seen to have moved into "Invisiblefields". And finally click <OK> button.
To recover the masked fields, also use the [Make invisible] dialog box, to perform thesimilar operations as above, but select the arrow key pointing to the left.
11.2.7 Sort
I. Function
Sort the records in the current table in the order from smaller index fields to larger ones.
II. Access
----- Select menu [Operations/Table operation/Sort].
-----Use the shortcut key <Ctrl+S>.
11.2.8 Locate To
I. Function
Use this function to locate the cursor to the nth record in the current table, namely thenth row of this table.
II. Access
----- Select menu [Operations/Table operations/Locate to].
-----Use the shortcut key <Ctrl+L>.
III. Interface description
The "Locate to" dialog box is shown in Figure 11-6.
Figure 11-6 "Locate to" operation record number input box
Input the sequence number of the record to be displayed, and then click <OK> button.This data table will display the located record and those following it.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-8
11.2.9 Pack
I. Function
This operation is used to compress the records.
The record will turn gray after being deleted. Too many gray records will influence thevisual effect, so table compression is necessary, that is, completely delete all the grayrecords from the data table to make the table neat and well-organized.
II. Access
----- Select menu [Operation/Table operation/Pack].
----- Use the shortcut key <Ctrl+P>.
11.2.10 Batch Operation
I. Function
Perform multiple operations on the current table on one time.
II. Access
----- Use the shortcut key <Ctrl+B>.
----- Double click the head of a field, i.e., the title bar of this field in the current table.
III. Interface description
The batch operation dialog box is shown in Figure 11-7.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-9
Figure 11-7 Batch operation parameter input dialog box
Input the parameters in "Operation Type" and select the function button for theoperation to be performed. Then the batch operation on the table will be accomplished.
Batch Add: it can add multiple records after the last record at one time.
Batch Modify: it can modify multiple records after the one on which the cursor currentlylocates at one time.
Batch Delete: it can delete multiple records after the one on which the cursor currentlylocates at one time.
As shown in Figure 11-7, in order to change call prefix in the called number analysistable to an ascending arithmetic progression (five records in all) sorted by 1, and routechoice code to an ascending arithmetic progression (five records in all) sorted by 1,first select these two fields successively in Field, fill in Record with 5 and Step with 1,then click the <Add to list> button, and finally click the <Batch modify> button and themodification is accomplished.
11.3 Block Operations
I. Function
The selected data block (successive multiple records) in the data table can be operatedat the same time. There are five operations: definition start, definition end, canceldefinition, copy definition and send definition. There are shortcut icons on the tool barrespectively corresponding to all functions.
II. Access
----- Select menu [Operations/Block operations].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-10
The interface is shown in Figure 11-8.
Figure 11-8 Block operations menu interface
III. Interface description
The interface is described in Table 11-2.
Table 11-2 Block operations description
Submenu name Function
Definition Start"Record block" refers to multiple consecutive records starting from a certain record in thetable. This menu item is used to define the start of a "Record block"
Definition End This menu item is used to define the end of a "Record block"
Cancel Definition Cancel the definition of a "Record block"
Copy Definition
Copy the content of the "Old record block" to the "New record block" starting from thecurrent record. Note that the "New record block" does not need to be defined. Just define an"Old record block", move the cursor to the "New record block" start record, and then enterthis menu item to complete the copying
Send Definition Send the data of the defined block to the switch
11.4 Batch Setting Operations
I. Function
This function is performed to send the non-adjacent multiple records in the current tableto the foreground switch at one time, and meanwhile convert the format of the records.There are three operations: Batch Setting Definition, Cancel Batch Setting and BatchSetting. All the functions have their corresponding operation shortcut keys.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-11
II. Access
----- Select menu [Operations/Batch setting operations].
The interface is shown in Figure 11-9.
Figure 11-9 Batch setting operations menu interface
III. Interface description
The interface is described in Table 11-3.
Table 11-3 Batch setting operation descriptions
Submenu name Function Shortcut key
Batch SettingDefinition
Select multiple non-consecutive records and define them respectively <Ctrl+M>
Cancel BatchSetting
Select one in the defined records with the cursor, then cancel itthrough"Cancel Batch Setting". This operation is the reversed one of "BatchSetting Definition".
<Ctrl+F2>
Batch SettingSend the multiple records defined to the foreground switch and converttheir format into DAT files at the same time.
F9
11.5 Format Conversions
I. Function
This function is performed to convert the database-formatted background data underthe directory CC08\BAM\DBF into the foreground data that can be loaded by the switch,and save them under the directory CC08\BAM\DLOAD, i.e., convert *.DBF files intodb_c.DAT and db_?.DAT. And in this file "?" includes all SM modules in the homeexchange and its value is 0, 1, 2.... There are three operations: Convert All, Update Alland Formatting Current Table.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-12
II. Access
----- Select menu [Operations/Format conversions].
The interface is shown in Figure 11-10.
Figure 11-10 Format conversions operation interface
III. Interface description
The interface is described in Table 11-4.
Table 11-4 Description of format conversions table
Submenu name Function
Convert All Convert all DBF files into DAT files
Update All Convert all DBF files modified after the last conversion into DAT files
Formatting Current Table Convert only the DBF files corresponding to the current table into DAT files
11.6 View Switch Data
I. Function
It is used to view data related to the current table in the foreground host.
As shown in Figure 11-11, input 1 as the module number, 6 as the number of records tobe viewed, and chick <OK> button. Then the current data table will display theconsecutive six records of Module 1, starting from the first row.
II. Access
------ Select menu [Operations/View switch data].
The interface is shown in Figure 11-11.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-13
Figure 11-11 View switch data operation interface
11.7 Set Data
I. Function
To make the modifications effective in MSC system, and send the modified records toall the modules through [Set data]. There are two operations: Set Table and SendRecord.
II. Access
----- Select menu [Operations/Set data].
The interface is shown in Figure 11-12.
Figure 11-12 "Set data" operation interface
III. Interface description
The interface is described in Table 11-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-14
Table 11-5 Set data table description
Submenu name Function
Set TableSend the data in the modified table to modules. Click the menu to pop up the dialog boxshown in Figure 11-13. Select the modules for the data to be sent to in the Module list
Send Record Send a single record in the table to modules
Figure 11-13 Module selection window
11.8 Operations Review
I. Function
Perform this function to view what operations have been performed historically on thedatabase and maintenance console, including two items: Operation Trace andMaintenance Trace.
II. Access
----- Select menu [Operations/Operations review].
The interface is shown in Figure 11-14.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-15
Figure 11-14 Operations review menu interface
III. Interface description
The interface is described in Table 11-6.
Table 11-6 Operation review descriptions
Submenu name Function
Operation TraceView the operations which are performed on the database and are recorded in thecurrent log file
Maintenance Trace View the operations performed on the maintenance console
11.9 Export
I. Function
Convert the table into *.TXT file format as shown in Figure 11-15.
II. Access
----- Select menu [Operations/Export].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 11-16
Figure 11-15 Export interface
11.10 MTP Set Record
I. Function
"MTP DSP" is a clue (guide) to the setting of MTP data alone. This setting is performedvia [Intra-office information table], [MTP DSP table], [MTP link set table], [MTProute table] and [MTP link table], which only has an impact on the adjusted or addedlinks, instead of the No.7 signaling link in normal transmission service. This function isespecially useful to the link modification when the system is upgraded.
When the clue (guide) to the "MTP single setting" starts working, a command is sent tothe host to check whether the background data are in conformity with the host data. Ifnot, a prompt window will pop up. In this case, it is recommended that the user shouldexit from the current operation and make the OMC data consistent with the host data by"Set table operation".
When the clue (guide) to the "MTP single setting" starts working, the MTP related dataare also checked, that is to say, the relativity and functionality of [Intra-officeinformation table], [MTP DSP table], [MTP link set table], [MTP route table] and[MTP link table] are examined. If an unreasonable record exists, the host will promptthe user.
II. Access
----- Select menu [Operations/MTP set record].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 12-1
12 Window
This chapter gives an introduction to the window operations to facilitate the operationsof the sub-windows.
The menu, as shown in Figure 12-1, includes [Tile horizontal], [Tile vertical],[Cascade], [Arrange icons], [Close], and [Close all].
Figure 12-1 "Window" menu interface
12.1 Tile Horizontal
I. Function
Perform this operation to change the size of all sub-windows already opened in thewindow and tile them horizontally. In this way, all the sub-windows will be displayed; buttoo many sub-windows will belittle each individual sub-window. Drag, with a mouse, thesub-window to change the size.
II. Access
----- Select menu [Window/Tile horizontal].
The interface is shown in Figure 12-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 12-2
Figure 12-2 Tile horizontal sub-windows diagram
12.2 Tile Vertical
I. Function
Perform this operation to change the size of all sub-windows already opened in thewindow and tile them vertically. In this way, all the sub-windows will be displayed; buttoo many sub-windows will belittle each individual sub-window. Drag, with a mouse, thesub-window to change the size.
II. Access
----- Select menu [Window/Tile vertical].
The interface is shown in Figure 12-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 12-3
Figure 12-3 Tile vertical sub-windows diagram
12.3 Cascade
I. Function
Perform this operation to change the size of all opened sub-windows and have themcascaded, leaving the title bar visible. However, only the content of the top sub-windowcan be displayed and most parts of the other sub-windows can not be seen. Double-click any title bar to maximize it.
II. Access
----- Select menu [Window/Cascade].
The interface is shown in Figure 12-4.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 12-4
Figure 12-4 Cascaded sub-windows diagram
12.4 Arrange Icons
I. Function
Perform this operation to arrange the icons (minimized sub-windows) in the mainwindow evenly. Note that only the icons of the minimized sub-windows are arrangedand the other sub-windows are not influenced.
II. Access
----- Select menu [Window/Arrange icons].
The interface is shown in Figure 12-5.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 12-5
Figure 12-5 "Arrange icons" diagram
12.5 Close All
I. Function
Perform this operation to close all the sub-windows (including minimized sub-windows)in the main window. After this, all the sub-menus under the main menu turn gray andbecome unavailable until a window is opened.
II. Access
----- Select menu [Window/Close all].
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 13-1
13 Help
The help menu includes two sub-menu items: [Contents F1] and [About]. Theinterface is shown in Figure 13-1.
Figure 13-1 "Help" menu interface
13.1 Contents
I. Function
The menu command is used to view the online help.
II. Access
----- Select menu [Help/Contents].
III. Interface description
The interface of the online help is shown in Figure 13-2.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 13-2
Figure 13-2 Online help system
13.2 About
I. Function
The menu command is used to view the software version information.
II. Access
----- Select menu [Help/About].
III. Interface description
The dialog box of the system software version information is shown in Figure 13-3.
User Interface Reference – Volume 1M900/M1800 MSC/VLR
Data ManagementRMN-MSC-DA
03A-1411-20010612-40 13-3
Figure 13-3 Software version information
11
How Are We Doing
Let us share your comments with respect to the contents, formats and wording of thismanual. Your feedback can be of great value in helping us improve our document. Pleaseuse a copy of these two pages for your comments, and fax to: +86-755-6540035Documentation Development Department.
1. Please rate the effectiveness of this document in the following areas:
Excellent Good Fair Poor
Ease of Use
Clarity
Completeness
Accuracy
Organization Structure
Appearance
Examples
Illustrations
Overall Satisfaction
2. Please check the ways you feel we could improve this document:
Improve the overview/introduction Make it more brief/concise
Improve the table of contents Add more step-by-step procedures
Improve the organization structure Add more troubleshooting info.
Include more figures Make it less technical
Add more examples Add more reference aids
Add more details Improve the index
Please provide details for the suggested improvement:
3. What did you like most about this document?
4. Feel free to write any comments below or on an attached sheet.
5. It is highly appreciated for any specific mistakes you have found (this page may be sent tous separately).
Mistake Suggested CorrectionPage &
Line No.
If we may contact you concerning your comments, please complete the following:
Name:______________________ Tel: _____________________________
Company:________________________________ Date:________________
Address:_______________________________________________________