Documente Academic
Documente Profesional
Documente Cultură
www.huawei.com
Page 2
Contents
Principles and Functions of the MSC Pool
Page 3
BSS
BSS
The most typical difference between the MSC Pool network and the traditional network is that the topology between core network nodes and wireless network nodes changes from one-to-multiple tree topology in the traditional network to multiple-to-multiple mesh topology in the MSC Pool network. With the absence of the virtual MGW technology, all A interfaces and all Iu interfaces must interwork. Viewed from the access network side, the MSC Pool acts as an MSC server with an extra-large capacity.
Page 4
IP Backbone
MGW
BSS
The virtual MGW technology can be used to avoid the interworking of all A interfaces.-just for manage A interface
All rights reserved Page 5
NNSF component
2. Positive location update response
The NNSF detects a new location update request destined for the MSC Pool and routes the request to an MSC server in the MSC Pool according to a sharing algorithm.(focus that it is location update) The MSC server allocates an NRI for the user. Then, all in-pool service requests of the user are routed by the NNSF to the MSC server that possesses the NRI. The NNSF function can be provided by the BSC/RNC. In the softswitch networking of the separated architecture, the NNSF function can be provided by the MGW with the A/Iu interface unchanged.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 6
When the RNC detects a new location update request destined for the MSC Pool, the RNC routes the request to an MSS in the pool according to a sharing algorithm. The MSS allocates an NRI carried in the TMSI for the user. Then, all in-pool service requests of the user are routed by the RNC to the MSS that possesses the NRI.
RNC
Page 7
MGW-A
RNC
1. New location update request 2. Positive location update response
Page 8
28~24
User ID range
23-14
use NRI range
13~0
User ID range
CS/PS
Bit 31 and bit 32 indicate whether a TMSI is used by the CS domain or PS domain, that is, whether it is a TMSI or P-TMSI. Bit 29, namely, VLR-restart, is a counter used to ensure that different TMSIs are allocated by the MSC server or VLR on the mobile network for a user before and after the MSC server restarts. Bits 14 to 23 indicate the range of NRIs that can be used by the MSC Pool. One or multiple bits of these 10 bits can implement this function. At present, the 10 bits are temporarily used to indicate user IDs on the GSM network to enlarge the number of users that can be managed by the MSC server. The remaining bits, that is, bits 0 to 13 and bits 14 to 28, indicate the range of user IDs that are allocated for users by the MSC server or VLR.
Page 9
Page 10
Home MSC Server Remaining Unchanged in the Case of Roaming Within the MSC Pool
STP
HLR/SCP/SMSC
MSC
This function reduces the traffic on the C/D interface, enhances the MSC capacity gain, and decreases inter-office handovers.
. RNC RNC RNC
Page 11
The traffic peaks in different areas and different periods are balanced without considering the maximum traff load in each area, thus saving the total capacity.
. RNC RNC
Residential area
RNC
RNC
Business area
RNC
Page 12
If an MSC server in the MSC pool is faulty, another MSC server in the pool takes over the users of the faulty MSC server.
. RNC RNC RNC
If the user is the caller, the service recovers immediately; if the user is the callee, the service recovers after a location update.
If the user is the caller, the service recovers immediately. If the user is the callee, the service recovers after a periodical location update.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 13
Contents
Principles and Functions of the MSC Pool
Page 14
MSS
MSS
All MSC servers use the same signaling point for interworking with the BSC; thus, the BSC senses only one MSC server.
User distribution
User distribution
User distribution
A-Flex function
BSC1 BSC2 BSC3
The MGW implements the AFlex/Iu-Flex function, and the A/Iu interface is not changed. When the MGW is used in the 2G network, the number of BSCs that need to be upgrade is less. This makes the solution easy to implement. When the MGW is used in the 2G network, if the RNC supports the Iu-Flex function, you can disable the Flex proxy function of the MGW through software so that multiple networking modes can be supported.
Page 16
Simplified OM Solution
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 17
Page 18
Mc
Mc
MGW
MGW
BSC
BSC
The efficiency of using A interfaces decreases. For example: A company has 100 employees and 10 vehicles. The 10 vehicles are just enough for the company. If the company is divided into 10 branches, each of which has 10 employees and one vehicle, maybe some branches need more vehicles while the vehicles of others are idle.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 19
Every time an MSC server is added to the MSC Pool, the TDM circuits of the A interfaces of all MSC servers in the pool must be re-planned and adjusted.
MGW
Routine OM of the A interface circuits becomes more complicated after the MSC Pool is adopted.
BSC
To maintain a circuit, for example, to block a circuit, you must locate the MSC server that manages the circuit and then block the circuit on the MSC server; if the circuits to be blocked are managed by different MSC servers, you must block the circuits on their respective MSC servers.
Page 20
MGW
BLOCK
BSC
Page 21
Page 22
TDM circuits are shared among multiple virtual MGWs to prevent resource waste in the case of MSC server failures and to increase the efficiency of using the A interface circuits. The OM is simple when A interface circuits are managed by the MGW. Adjustment of A interface circuits is not required even if MSC servers are added to the MSC Pool.
BSC1
BSC2
BSC3
Page 23
Solution of Sharing TDM Circuits of the A Interfaces Optimized Solution for the Called Service Load-balancing Solution
Simplified OM Solution
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 24
MSC1
MSC2
GMSC-Server
The MS is called.
. RNC RNC RNC
If the user is the caller, the service recovers immediately; if the user is the callee, the service recovers after a location update.
MS
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 25
Solution to the Called Service in At the STP, specify the active route A-B to the MSC Pool MSC server 1 as a direct route.
At the STP, configure the route A-E-B to MSC server 1 with a low priority. HLR OPC:1A When MSC server 1 functions properly, the direct route, that is, the route with a high STP1 priority, is used for the signaling interworking between node A and node B. Standby route If MSC server 1 is faulty, the direct route fails. MAP/CAP signaling Active route Then, PRN messages are sent to node E along the low-priority route, and node E enables the multiple signaling point technology so that the signaling of the callee is terminated at node E. MSC-Server1 MSC-Server2 MSC-Server3 MSC-Server4 After receiving the PRN messages, MSC server 4 obtains the location information from Node B Node C Node D Node E the VLR and delivers paging based on the IMSI. After receiving the paging response, the MGW/BSC routes the paging response to an MSC server in the pool based on the loadMGW/BSC balancing algorithm. Then, the MSC server enables MSC virtual location update to The VLR on MSC server 4 backs up the basic update the MSC/VLR data on the HLR. VLR user data on all MSC servers in the pool. The first called service fails, and follow-up The functions of MSC server 4 can be provided by called services can be connected other MSC servers in the pool. successful.
Node A HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 26
Simplified OM Solution
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 27
Application Scenario
The user re-distribution solution is generally used in the following scenarios for user migration:
Routine maintenance, for example, important upgrade operations Fault clearance Pool adjustment, for example, adding or removing MSC servers
The user re-distribution solution is applicable to significant manual adjustment. The principle is as follows:
The OM center delivers the load re-distribution command to the MSC
server and specifies target MSC servers so that idle users can migrate to
the target MSC servers. Users migrate to target MSC servers through load sharing, thus completing the load adjustment among MSC servers.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 28
User Re-distribution
Migration of all users
MSC Server1 MSC Server2 Upgrade Rollback
IP bearer
Before upgrading one or multiple MSC servers in the pool, you must ensure that all users of the MSC server(s) migrate to other MSC servers in the pool. This prevents the upgrade from interrupting user services.
User re-distribution on the NMS is applicable to the following scenarios: 1. All the users of an MSC server migrate to other MSC servers in the MSC Pool. 2. A certain percentage of the users of an MSC server migrate to other MSC servers in the MSC Pool. 3. A certain number of the users of an MSC server migrate to other MSC servers in the MSC Pool.
4. The users from the specific BSC/RNC to an MSC server migrate to other MSC servers in the MSC Pool.
5. The users in specific areas of an MSC server migrate to other MSC servers in the MSC Pool. 6. The specified users (specified by the MSISDNs obtained through the IMSIs) of an MSC server migrate to other MSC servers in the MSC Pool.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 30
3 5
MSC-Server1 Node A
2 6
MSC-Server2 Node B
MGW/BSC
The key for MS uninstallation is that the NRI in the TMSI is refreshed to the NRI of the target MSC server. The MSC server number in the HLR is refreshed to the target MSC server number.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved
Simplified OM Solution
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 32
Page 33
IP bearer
BSC
BSC
Benefits for operation The load notification mechanism between MSC servers and MGWs does not involve wireless NEs. Load notification is implemented within the CN, and close coupling of CN nodes and RAN nodes is not required. In the previous, the BSC cannot adjust load distribution without manual intervention because the A interface between the MSC server and the BSC does not support load notification. This mechanism solves this problem.
Page 34
Solution of Sharing TDM Circuits of the A Interfaces Optimized Solution for the Called Service Load-balancing Solution
Simplified OM Solution
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 35
Page 36
Centralized MSC Pool Management Implemented by the MSC Pool Management Module of the M2000
Unified maintenance of MSC Pool parameters
MSC Pool parameters must be maintained in a unified manner over the entire network. Thus, the MSC Pool service model is established on the M2000 on the basis of thorough analysis on the service parameters. Then, maintenance of the MSC Pool parameters can be synchronized among all NEs in the pool.
Page 37
Page 38
Audience
Purpose
Familiarize with the MSC Pool source design principle Familiarize with the MSC Pool common structure of traffic network, signaling network and access network Learn MSC Pool billing principle Learn MSC Pool common migration principle
Scope
Page 39
Reference
GU CS HLD Template
MSOFTX3000 MSC Pool User Manual MSC Pool Network Planning Guide MSC Pool White Paper.doc
Page 40
Contents
Pool Area planning and Pubilc Attribute planning
Page 41
Contents
Page 42
Glossary
A-Flex/ Iu-Flex: A key technology used for implementing MSC Pool networking. As stipulated in 3GPP 23.236, A-Flex/ Iu-Flex enables one BSC or RNC to connect to multiple MSC servers. MSC Pool: A pool constituted by a group of MSC servers that serve multiple BSCs or RNCs. Pool Area: An area in the MSC Pool in which an MS can roam without changing the serving CN node. NRI: The Network Resource Identifier that uniquely identifies a CN node in a Pool Area. The NRI, consisting of 0 to 10 digits, is carried in the TMSI (in the CS domain) or the P-TMSI (in the PS domain). NNSF: An NAS Node Selection Function node used to choose CN nodes in an MSC Pool. Default MSC: The default MSC server used to transfer messages for obtaining subscriber information between MSC servers in the MSC Pool and MSC servers outside the MSC Pool. Virtual MGW: A technology that enables a physical MGW to connect to multiple MSC servers.
Page 43
The RAN of an MSC Pool should be a whole areaLAI coverage in an MSC Pool is continuous ). This planning can reduce handover times between MSC Servers and make the traffic balanced in an MSC Pool.
The subscriber capacity and service which can be provided should be the same for all the CN nodes in an MSC Pool.
Nnormally, CN nodes in an MSC Pool do not provide service for the BSC/RNC outside the MSC Pool.
Page 44
NRI Planning
POOL1 POOL2 POOL3 POOL4
Plan principles 1One NRI belongs to only one MSC Server in MSC Pool but one MSC server in MSC Pool could be configured more than one NRI.; 2The NRI value of each area in one MSC POOL should try to be unique but the length should be the same 3The length of NRI depends on the quantity of planning subscribers; 4The Null-NRI and the NRI should be planned on a uniform basis. The maximum or minimum value of the NRI in an NRI set within an MSC Pool can be selected as the Null-NRI. It is proposed that the NRI should be planned by Four-Color-Method in the whole network.
For exampleThe length of NRI is 6 bitsthe value could be 0~63NRI group 10~15 NRI group 216~31 NRI group 332~47 NRI group 448~63.
HUAWEI TECHNOLOGIES CO., LTD.
Page 45
Planning Principle:
MSC5 MSC6
In order to keep the signaling is balanced in MSC Pool, the MSC out of MSC Pool should connect to different default MSC
MSC2
MSC3
in MSC Pool.
Pool area
MSC1
In order to increase the resource usage, the MSC out of MSC Pool should connect to the location nearest MSC in
MSC4
In project, the handover target MSC is normally the default MSC in MSC Pool.
Page 47
The Non-broadcast LAI is a special LAIthe function of Non-broadcast LAI refers to MSC Pool White Paper. The Non-broadcast LAI is encoded together with ordinary NRI on a uniform basis, but it cannot be the same as any LAI already configured in the MSC Pool.
You can configure the Non-broadcast LAI according to the descending order or
ascending order based on actual configuration of the LAI.
Each MSC in an MSC Pool should be configured with a Non-broadcast LAI of the local office and an MSC maps a unique Non-broadcast LAI.
Each MSC in an MSC Pool should be configured with the Non-broadcast LAI of
all other offices in the same MSC Pool. Non-broadcast LAI is not configured in BSC or RNC.
Page 48
What is the planning principles of MSC Pool area? What is the NRI planning principles in a MSC Pool? Is the planning result of Default MSC and Handover Target different?
Page 49
Contents
Pool Area planning and Pubilc Attribute planning
Page 50
Contents
Page 51
The capacity of the nodes in the MSC Pool should be balanced. The nodes serve as the VMSC (not recommended to concurrently serve as the GMSC and TMSC). In addition, the nodes should provide the same services. The MSC Pool networking requires the IP-based Mc, Nc, and Nb interfaces. The MSC Server and MGW in the MSC Pool are connected in full mesh mode. It is recommended that the signaling connection between the MSS and the pure signaling NEs such as the SMC, SCP, and HLR in the MSC Pool is transferred through the STP, and the STP is directly connected to the MSS. Generally, the BICC signaling adopts the direct connection mode. It is recommended that the trunk signaling between the MSS in the MSC Pool and the TDM office outside the MSC Pool should be transferred through the independent TDM/IP interworking office. When an independent TDM/IP interworking office is unavailable, the signaling should be transferred through one pair of MSS in the MSC Pool. The trunk signaling to the PLMN/PSTN is transferred through the GMSC. It is recommended that the signaling of service NEs such as VMS, IVR, and CRBT with traffic is transferred through the GMSC or TMSC. There is signaling connection between BSC/RNC and all MSC Servers in the MSC Pool. The M3UA transfer mode is recommended for the BSSAP and RANAP. The centralized backup mode is recommended for VLR subscriber data backup.
Page 52
Page 53
Page 54
Sample Analysis
The networking is applicable to scenario where the IP-based reconstruction is implemented in the GMSC, with the following advantages: The maintenance and management are convenient. The capacity of each node in the MSC Pool must be the same. In this way, the load of each node in the MSC Pool is balanced. All signaling to external TDM offices is transferred through the independent IP-based GMSC. Each node in the MSC Pool features the unique function, consistent signaling route configuration, and clear signaling network architecture. These features facilitate the data planning and daily maintenance management. VLR subscriber data is in the centralized backup mode. The data configuration, operation, and maintenance are simplifie The network can be expanded and developed conveniently. The signaling to the HLR/SMSC/SCP is transferred through the STP. When a node is added to the MSC Pool, only the signaling link between the STP and the new node should be established. This decreases the complexity of the expansion project. The trunk signaling to external TDM office directions is transferred through the GMSC. When a node is added to the MSC Pool, only the IP signaling link between the GMSC and the new node should be established. This decreases the complexity of the engineering implementation. VLR subscriber data is in the centralized backup mode. When a node in the MSC Pool is added, the backup relation between nodes in the MSC Pool needs not to be redesigned. This simplifies the expansion workload.
The second solution can reduce MGW number while the traffic is very few between MSC Pool and other MSC.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 55
Page 56
Sample Analysis
In the scenario where the GMSC exists in the target network and the independent IP/TDM interworking office is not planned in the target network, it is recommended that one pair of MSS in the MSC Pool should be selected to concurrently function as the TDM/IP interworking office. The advantages are as follows:
The trunk signaling to external TDM office directions is transferred through the GMSC, without establishing the signaling link between the nodes in the MSC Pool and office directions outside the MSC Pool. This simplifies the data configuration and reduces the engineering implementation workload. The signaling from nodes in the MSC Pool to the GMSC is transferred through two MSC Servers, without establishing the signaling link between each node in the MSC Pool and the GMSC. This simplifies the data configuration and reduces the engineering implementation workload. When a node in the MSC Pool is added, a signaling link should not be established for office directions outside the MSC Pool.
With the increase of the MSC Pool capacity, the MSC Server concurrently functioning as the interworking office gradually becomes an independent IP/TDM interworking office. In the networking, the physical connections or data configurations of each NE are not changed greatly during the evolution. This eases the smooth network evolution.
Page 57
Page 58
Sample Analysis
In this scenario where the independent GMSC is unavailable in the target network, it is recommended that one pair of MSS in the MSC Pool concurrently functions as the GMSC/TMSC, to transfer the trunk signaling between other nodes in the MSC Pool, PSTN/PLMN, and external TDM office directions. Benefits:
Only two MSC servers in the MSC Pool are used to concurrently function as the GMSC, without exposing the networking architecture in the MSC Pool. The utilization ratio of the link to the PSTN/PLMN increases. When the number of nodes in the MSC Pool is expanded, the modification of the data configuration in the PSTN/PLMN is not required. Only two MSC Servers in the MSC Pool concurrently function as the TMSC to transfer the trunk signaling from the local network to other office directions. The data configurations are simplified and the engineering implementation load decreases. In the case of the expansion of the MSC Pool, the modification of data configurations in other office directions outside the MSC Pool is simplified. The functions of the nodes in the MSC Pool feature are relatively single, which facilitates the network evolution. Note:
The MSC Pool is not recommended in this scenario, because the data configuration and maintenance management are
more complicated, and the load of NEs in the MSC Pool is unbalanced. In addition, this networking is not according with the trend of the network evolution.
Page 59
Question
Page 60
Contents
Pool Area planning and Pubilc Attribute planning
Page 61
Contents
Page 62
MT Recovery Solution
In MSC Pool network, the MT recovery solution is not mandatory. Huawei provides two MT recovery solution for customer. The First MT recovery solution and the second MT recovery solution.
The first MT recovery solution and the second recovery solution are configured by software parameter in HUAWEI device. The different of network structure: The signaling link is not necessary between VLR and NNSF Node (MGW/BSC) while using the central backup in the first MT recovery solution.
The restriction of the first MT recovery solution: a. In 2G network, the NNSF node (BSC or MGW) can realize the first MT recovery solution. b. In 3G network, if MGW acts as the NNSF node can realize the first MT recovery solution.
c. In 3G network, if RNC acts as the NNSF node can realize the first MT recovery solution.
This is only available for HUAWEI R11 RNC.
Page 63
Central backup solution There is independent MSC Server in the central backup solution. This MSC Server backups all the MSC Servers user data information. Central backup MSC Server only processes the MT recovery service.
Chain backup solution There is no independent MSC Server in the chain backup solution. Every MSC Server in MSC Pool processes the self-service and the same time acts as the backup MSC Server of other MSC Server in the MSC Pool.
Page 64
The PRN message which should be sent to primary MSC Server must be sent to backup MSC Server. The ISUP message which should be sent to primary MSC Server
Page 65
For centralized backup mode, only one SPC need to be configured in active MSC Server. Also only one SPC need to be configured in backup MSC Server. The SPC of backup MSC Server is the assistant SPC and the priority is lower than the SPC of active MSC Server.
All rights reserved Page 66
For centralized backup mode, the configuration of active MSC Server is the same as above. For backup MSC Server, one SPC of MAP service need to be configured. The SPC of active MSC Server also need to be configured in backup MSC Server but only for VLR sub-system. The relationship of these two SPC need to be configured too.
ThinkingWhat problem will come out if the trunk signaling is through STP in this solution?
All rights reserved Page 67
When active MSC Server is down, only paging message and PRN message will be processed in backup MSC Server. If other messages (M3UA/MAP/CAP) are sent to backup while active MSC Server was down, the resource boards of backup MSC Server will become heavy.
All rights reserved Page 68
1SCCP Load-Sharing mode is recommend when STP supports SCCP Load-Sharing mode. 2Route Priority mode is recommended when STP does not support SCCP Load-sharing mode.
Page 70
Question
What is the difference between the first MT recovery solution and the second MT recovery solution? What is the reason of trunk signaling resend problem?
Please describe the signaling route design solution (SCCP Load Share and
Rout Priority Fist).
Page 71
Contents
Pool Area planning and Pubilc Attribute planning
Page 72
Contents
Page 73
MGWs in the MSC Pool must be connected over IP in the full mesh. It is recommended that the traffic from a node in the MSC Pool to a service NE (for example, VMS, IVR, and CRBT) should be transferred through the interworking office. It is recommended that the traffic from a node in the MSC Pool to a traditional MSC outside the MSC Pool should be transferred through the interworking office. It is recommended that the traffic from a node in the MSC Pool to the PSTN/PLMN should be transferred through the GMSC. For the traffic interconnection between a node in the MSC Pool and the TDM office direction outside the MSC Pool, the TDM circuit directly led out from the MGW inside the MSC Pool is not recommended, because the TDM resources between virtual MGWs cannot be shared. It is recommended that the traffic between the MGW in the MSC Pool and the TDM office direction outside the MSC Pool should be transferred through the independent IP/TDM interworking office. If the IP/TDM interworking office is not planned in the target network, it is recommended that only one pair of MGW in the MSC Pool should be used to establish the circuit with the TDM office direction outside the MSC Pool. The traffic between a node in the MSC Pool and the TDM office direction outside the MSC Pool should be transferred through one pair of MGWs.
Page 74
Pool MSC The traffic route form Pool to outside Internal call in MSC Pool; The call between MSS MS in same MSC Server; The call of MS in MSS different MSC Servers
Page 75
Analysis
The MSC Pool traffic networking is recommended, the benefits are as follows:
The MGW function in the MSC Pool is unique, which facilitates the planning of the MGW capacity and the load balance between MGWs. The TDM circuit needs not to be led out from the MGW in the MSC Pool. This reduces the complexity of the engineering implementation and daily maintenance management. The networking architecture is clear, which facilitates the network evolution and expansion.
Page 76
Non-IP GMSC
Page 77
Page 78
Page 79
Analysis
For the solution of all interworking office circuits configured in each interworking MGW, the traffic of Nb interface decreases. The redundancy protection capability is available in the interworking MGW. The limitations of this solution include the decrease of the trunk circuit utilization, and the complexity of the engineering implementation and management maintenance.
In the scenario where the node in the MSC Pool concurrently functions as the interworking office, the solution of one interworking office direction circuit configured in each interworking MGW is recommended.
Page 80
MGW1 V1 V2 V3 V4
MGW3
BSC1
GMSC1
GMSC2
BSC3
Page 81
Question
What is the trunk CIC resource management in MSC Pool network? What is the advantage and disadvantage when the MGW trunk CIC resource is arranged to only one MSC Server?
Page 82
Contents
Pool Area planning and Pubilc Attribute planning
Page 83
Contents
Page 84
The MSC Server in MSC Pool commutates with BSC use different SPC BB and CC. MGW communicates with MSC Server use different SPC DD and EE. MGW communicates with BSC use the same SPC AA. BSC communicates with MSC Server using the same DPC AA. This is the M3UA forwarding mode.
MGW will change the SPC into AA in down-link and will change the DPC into BB in up-link.
Page 86
MGW communicates with MSC Server using the same SPC AA.
BSC communicates with MSC Server using the DPC AA. All above is the M3UA agent mode.
Page 87
The M3UA forward mode is adopted when the RNC is IP based. This solution is adopted when the RNC is ATM based. The RNC should be configured more than two DPC when the RNC is ATM based as most RNC can support one DPC
MGW1 DD
EE AA
MGW2 NN
AA
MM
BSC1
BSC2
BSC3
RNC1
Pool Area
Page 88
Question
Please describe the influence what the M3UA forward mode to uplink message and downlink message. What is the design solution when the RNC is ATM based?
Page 89
Contents
Pool Area planning and Pubilc Attribute planning
Page 90
Contents
Page 91
Billing Principle
Billing system can not recognize the location of subscriber according to origination MSC ID, so the charge can not be confirmed. This is because of every MSC Server can server all LAI in MSC Pool.
There are two solutions, one is virtual MSC ID billing and another is LAI
billing.
Page 92
MGW
A
MGW
A
MGW
A
MGW
A
BSC
BSC
BSC
BSC
Local Area A
Local Area B
One physical MSC is divided into multi-virtual MSC, every virtual MSC is arranged one independent MSC ID. One virtual MSC ID belongs to one local area.
Page 93
LAI Billing
The system specifies the LAI in caller and callee CDRs outgoing from the local office. The local office allocates roaming numbers according to the LAI. The GMSC can map the location of the callee
according to the called roaming number to charge the subscriber. To implement the charging of the
Free Roaming to Same City for IN subscribers, the SCP uses the ATI procedure to obtain the location information of the caller and callee in the calling and called processes to implement the precision charging.
Requirements of peripheral NEs in the LAI charging are as follows: The BOSS should support the LAI-based charging. The SCP should support the ATI process of obtaining the location information. The HLR should support the PSI process of obtaining the location information from the MSC.
Page 94
Analysis
Charging Mode
Virtual MSC ID charging
Benefits
1.It does not have special requirements on peripheral NEs. 2. Mature applications are available in the existing networks.
Limitations
1. Many MSC IDs are required. 2. Data configurations are complicated. 3. The number of inter-office location updates or interoffice handovers increases in the case of roaming between different MSC servers in the MSC Pool. The traffic of C interface or D interface may increase.
LAI Charging
1. It reflects location information. The data configuration is simplified. 2. The benefits of the MSC Pool networking are not affected.
1. The current BOSS system should be reconstructed. 2. The SCP in the current network should support the ATI process. 3. The HLR in the current network should support the PSI process. 4. The MSC in the current network should support the ZC function. The ZC information should be added for the subscriber in the HLR.
Page 95
Question
What is the advantage and disadvantage of virtual MSC ID billing solution and LAI billing solution?
Page 96
Practices
HLR SCP SMSC Service Platform IVR VMS CRBT
The MSC pool refers to the topology. Two MSS and two MGW.
STP
Legacy VMSC
For this network, what is the key point of network design? What other solution could be considered?
MSS1
MSC POOL
MSS2
IP Bearer
TMSC
MGW1
MGW2
RNC1
RNC2
BSC2 Page 97
Page 98
FAQ
1The bandwidth resource requirement is not enough after the office is cutover. Analysis The traffic model is incorrect. The traffic model from sale engineer is incorrect. The traffic model is not converted into MSC Pool traffic model. The bandwidth result is incorrect The analysis of signaling route and traffic route is not correct, and the bandwidth combiner and bandwidth split are wrong. The traffic planning is not rational, there are many devious traffic between different MGW. The trunk data configuration is incorrect. The BICCTG data configuration is missing in VMSC and this occur large traffic between different MGW. There are more cases in following link: http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailProdu ctSimple&web_doc_id=SC0000523532&doc_type=123-2
Page 99
Uganda WARID
Latin American MILLICOM
Cote D'Ivoire MTN Nigeria MTN
Kenya Safaricom
Page 100
Thank you
www.huawei.com