0 évaluation0% ont trouvé ce document utile (0 vote)
442 vues120 pages
This document contains information about BSS (Base Station Subsystem) planning and deployment including network connectivity diagrams, procedures for new BSC implementation, BSC splitting and re-parenting. It provides details on interfaces, trunk utilization and a new planning approach with recommendations. Specific topics covered include PMCL network diagrams, interfaces sheets with BSC information, BTS commissioning dates, and site connectivity/configuration details.
This document contains information about BSS (Base Station Subsystem) planning and deployment including network connectivity diagrams, procedures for new BSC implementation, BSC splitting and re-parenting. It provides details on interfaces, trunk utilization and a new planning approach with recommendations. Specific topics covered include PMCL network diagrams, interfaces sheets with BSC information, BTS commissioning dates, and site connectivity/configuration details.
This document contains information about BSS (Base Station Subsystem) planning and deployment including network connectivity diagrams, procedures for new BSC implementation, BSC splitting and re-parenting. It provides details on interfaces, trunk utilization and a new planning approach with recommendations. Specific topics covered include PMCL network diagrams, interfaces sheets with BSC information, BTS commissioning dates, and site connectivity/configuration details.
1- PMCL Network Connectivity Diagram (10 May) 2- New BSC Implementation Procedure 3- Newly commissioned BSC in the last 3 months (22 BSCs) 4- BSC movement outside MSC premises (concept & Advantages) 5- BSC Splitting Procedure 6- BSC re-parenting Procedure 7- Site re-parenting Procedure 8- MTL Reduction (Concept & advantages) 9- Trunk Utilization Handling (Solution methods) 10- New BSS Planning Approach (IMPORTANT RECOMMENDATION) 11- BSS planning information (10 May)
Network Connectivity Diagram
BSS planning team used to update the Network connectivity Diagram on a weekly basis
Objective: The objective of this document is to explain the network connectivity workbook that is produced on a per region basis by BSS Planning.
The BSS Connectivity has four parts, namely Network Block Diagram BSS Interfaces Information BTS Commissioning Dates BTS Connectivity & Configuration Information
Network Connectivity Diagram Description:
1 Network Connectivity Diagram
This shows the network elements in a region (MSCs, Transcoders and BSCs) as they are actually connected, the number of links on A and A ter interfaces and the type of these links, i.e. a microwave link, a PTCL leased line or a direct PCM cable connection.
For instance, for any BSC this diagram will show how many Transcoders that a BSC is connected to, how many A ter links are connected via each Transcoder and whether the link is a microwave, leased line or hardwired connection. I t will also show the corresponding MSC to which a Transcoder/ BSC is connected to, and the number of A-interfaces used.
I t also gives the number of TRXs, sites and busy MMSs for every BSC. I n the end it gives a summary of the total number of TRXs, sites and busy MMSs, A and A ter interfaces used in BSCs connected to each MSC as well as a grand total of all.
2 BSS I nterfaces Information
This sheet is the crux and gist of all the connectivity. I t shows almost everything related to the connectivity in a brief but concise table.
It provides us information about all the BSCs connected to a particular MSC in a region in addition to the following information:
- City that a particular BSC is located in. - Cabinet type of the BSC, like BSSC or In-Cell. - Number of cages in operation per BSC e.g dual-cage or single-cage - Number of MMSs each BSC is capable of getting equipped into itself (calculated using the number of MSIs equipped/ present in a particular BSC) - Number of MMSs in busy state, whether they be used for GSM or GPRS links - Number of free MMSs ready to be used - Number of A ter and A-interfaces connected to a particular BSC. - Number of sites connected to a BSC - Total number of TRXs being handled by the BSC - Peak busy interval RF traffic (in erlangs) per BSC.
We can also have some additional information in this diagram e.g. trunk utilization per BSC, which will give us the erlangs on A-interface.
3 BTS Commissioning Dates
As evident from the sheet title, this one gives the BTS commissioning dates for all the BTSs in the region. However, it is to be noted that the dates mentioned in this sheet are commissioning dates and not the "on-air" dates. In addition to it, the city names for sites are also mentioned besides each site.
4 BTS Connectivity & Configuration I nformation:
This is the most lengthy and base level informative sheet of the workbook. For any particular BSC in the region, this sheet will give us:
- Number and names of BTS sites connected to it - Site and Cells IDs of each site/ cell - Configuration of each site
It also tells us which sites are daisy-chained with others and wherever there is a sector split i.e., a sector of the same site is working as a separate site with a different site ID. It also tells us if a site is commissioned and locked.
Document Name Document Version # Prepared by Date of Issue New BSC Implementation/ Deployment Procedure Draft 1 Version 1 Muhammad Abid 13-11-2003 New BSC Implementation/ Deployment Procedure Version 1 Ahmed Bari 16-11-2003
1. DOCUMENT APPROVAL MATRIX
Approved by Designation Signature Date of Approval Ahmed Bari Manager BSS Planning & Deployment
Faisal Sattar Director Operations Support Saleem Aftab Director Operations & Maintenance
Anwer Qureshi Director NSS J afar Khalid HOD Planning and Systems Engineering
Marwan Hayek Chief Technical Officer
This page has been Intentionally left blank
2. OBJ ECTI VE:
The objective of this document is to outline the complete process and responsibilities for all involved, and that are to be followed strictly for a successful and timely implementation of a new PMCL BSC/ XCDR.
3. INTRODUCTION:
Major Network elements need to be installed and commissioned based on different requirements. These requirements may relate to RF, BSS or Transmission requirements as such.
For these Network Elements to be installed and commissioned successfully, a clear process needs to be defined that will be followed by all the relevant teams of PMCL at all times.
4. DETAI LED PROCEDURE:
PLANNING PHASE BSS Planning
- Regional BSS Manager/ Team Leader to write a short note of the summary of the project objectives that the new BSC is expected to achieve. This should include (but not limited to) the exact justification and requirement of a new BSC based on any number of reasons e.g.: - BSS capacity limitation (mms TRX traffic load etc.) - Transmission issues
- This report should also mention the preferable location of the BSC with the reasons of its choice (access issues, space issues, transmission plan changes, benefits of the new BSC location etc.) clearly mentioned taking into consideration O&M and Transmission feeback
- This plan will be submitted to the National Manager BSS Planning and Deployment for approval.
- This approval is not depends ONLY on the above mentioned reason, BUT ALSO on many aspects, first of all; using the available resources in the region as much as we can. Secondly, the equipment availability either it is on the stock or ordered already or even to be ordered. In addition to that the exact needs of it region. In a word, it should be based on the National level view.
J OI NT VI SI T - After the approval for the above plan has been granted, regional BSS will then coordinate with other teams like O&M, Motorola, Transmission and Production in order to clearly mention and identify any tasks that need to be carried out for the proper implementation of this plan. - This visit will clearly chalk out the task need to be carried out, responsible team/ person along with the time line for each task. - As per any issues that were highlighted in the joint visit, each team will start with the tasks assigned to each one of them.
PRODUCTI ON - All Production related issues, e.g. requirement of AC breakers, genset requirement, any modifications in the room, any relocation of air-conditioner etc. will be taken care of by Production on an a.s.a.p. basis. - BSC commissioning will not start unless the production will finish the main requirements that meet this commissioning (for example Stabilizer and AC breaker). New Genset is not considered as main requirement unless if there is no Genset on site. - 2 nd genset is recommended but not mandatory to put on the site for BSC commissioning.
TRANSMI SSI ON - Transmission Planning will have a detailed look at the Transmission plan for the new BSC and circulate any changes if necessary, to the BSS planning.
NEC I nstallation - It is to be noted that for BSC room to be ready for installation, tasks of BSS Planning and
essential Production tasks need to be completed and lie in the Critical Path. However, Transmission Planning does have time to implement the new transmission plan in parallel with the BSC installation.
DEPOLYMENT PHASE BSS Deployment
- Request BSC/ XCDR, DC power, Battery Backup, Micro Cell and the required MW links equipment from the Warehouse. - Ensuring the complete delivery of the required equipment on the site - Provide essentials (cables/ connectors etc.) to the O&M and request Abis/ Ater
NSS - Define SPC for the new BSC in the network. - Define DIUs connectivity ports as per BSS plan - Create the new BSC information on the relevant MSC including all of CI D- LAC - Create the DIU MTL as per submitted plan.
OAN - O&M will carry out all the cabling/cross- connection required for different interfaces of the new BSC as per BSS plan. - For any outage required for this connectivity during this preparation phase, O&M will generate ECRFs. - O&M should accompany anyone from any party during any activity at any operational site with reference to prior notice agreement (24 hours in advance in the main cities 2-3 days in advance for the remote cities)
DATAGEN - BSS Planning should provide Motorola with the complete plan including all the required - information used for database creation using the datagen. - OMCR will also provide the required Code Object 2 of the relevant BSC. - Motorola will prepare the datagen scripts of the new BSC and send it to OMCR/ BSS. - Motorola will prepare of modified scripts regarding to the external neighbors.
Installation & Commissioning - Motorola will be responsible for the I nstallation and commissioning of BSC, XCDR, DC Power equipment, Battery Bank, and Microcell at the BSC site. - Cabling through the BSC DDF at the BSC side - Cabling through the XCDR DDF at the MSC side.
CI C Testing - BSS deployment, NSS, OMCR and Motorola will ensure for OMAL connectivity of the new BSC. - OMCR will be responsible for CI C/ MTL equipage preparation as per the pre-defined connectivity standards of PMCL. Once OML of the BSC is working, OMCR will then download all the datagen, CIC/ MTL scripts on the new BSC. - One test micro sites will be equipped with the new BSC once it is working; calls will be testing to check for any no-audio calls. This testing will be completed for all the DIUs connected to it.
- After the success of all DI Us testing, the cutover will be executed on a separate night except if we are facing URGENT situation.
INTEGRATION PHASE Outage Approval - BSS planning will define the cutover time after ensuring the complete preparation activities - O&M will generate ECRF for this planned BSC Cutover activity to be approved by the CTO.
Announcement - Final Cutover plan of the new BSC should then be distributed among different teams by the BSS Manager/ Team Leader. This should also be communicated to the relevant regional Customer Services as well. - There should also be an implementation plan defining the tasks assigned to each department. An example of such a plan is described in Annexure -3.
Cutover night - BSS planning engineer should ensure the complete co-ordination between all of the involved parties during the cutover night and he has to refer to the management in case of any up-normal situation where he cant take a discussion (Fall back / No cutover discussion should be considered) - Final Traffic shifting of different links will then be done by O&M on the cutover night. This will also be accompanied by shifting of all the planned sites in the new BSC. - NSS must assign/nominate dedicated resource to ensure the UNBLOCK all of the DI U/CI C/MTL whereas it has to be ready before the cutover and to delete any previous unused cell ID came after this operation. - Motorola should be presented at the OMCR to ensure smooth operation and to solve any problem related to the database scripts especially for the external neighbors - Motorola and Optimization teams will then be responsible for the first drive tests to be conducted so as to confirm call connectivity in the new BSC and call handovers with the neighboring BSCs. - OMCR will also monitor stats for the BSC, cells in the new BSC as well as the cells in the neighboring BSCs. - New Cell IDs will also be communicated to Billing by OMCR/ NSS. Also an update of the new connectivity diagram for all the effected BSCs will be circulated by BSS team to all the relevant teams.
Acceptance - O&M is responsible of the acceptance of the new BSC/XCDR and MW links - CICs testing will ensure for the NSS/O&M that there is NO Audio call problem existing on this new BSC so it is not accepted neither from OMCR nor from NSS to change/modify any of the database related to these DIUs/CICs/MTLs. (please refer to appendix-1)
Annexure I: XCDR Standardisation
- 1 x MTL should be defined on TS:16 per A ter.
- 4 x XBL should be defined on TS:2 on A ter no. 1,3,5 &7. - 1 x OML should be defined on TS:1 of the first A ter only. - 1 x OPL should be defined on TS:3 of the first A ter only.
Calculation Active Trunks available After defining one MTL per each Ater; the remaining TS will be 30 CIC Accumulated 1st Ater 27 OML-XBL-OPL
108 108 2nd Ater 30 Nothing
120 228 3rd Ater 29 XBL
116 344 4th Ater 30 Nothing
120 464 5th Ater 29 XBL
116 580 6th Ater 30 Nothing
120 700 7th Ater 29 XBL
116 816 8th Ater 30 Nothing
120 936 9th Ater 30 Nothing
120 1056 10th Ater 30 Nothing
120 1176
Annexure II Flowchart
National BSS Manager Approval in Principle of the BSC plan Regional BSS Manager Layout of the Initial plan giving priamary objectives. justification of new BSC/ XCDR in the network Regional BSS Initiation of a project to commission a new BSC Regional BSS Joint visit of proposed site by representatives of all the relevant teams (BSS, Txn, Infra, O&M, Motorola) This visit should clearly chalk out the responsibilities of each team along with a defined time line. This plan should clearly state the exact requirement/ justification of a new BSC including basic details about its location, space, access, old and new boundaries, LAC changes, transmission issues etc. Infra Essential tasks for new BSC BSS Request and Deploy new links (if any required) as per new Txn Plan BSS Prepare BTS equipment reshuffle/ swap/ reduction if possibl e BSS Space Issue inside Room? Txn New Txn Plan required? BSS/ O&M/ NEC - New link installation - ECRF for any expected outages for traffic shifting to the new links (if possible) BSS/ O&M/ Motorola Equipment swap/ reshuffle/ reduction in coordination with Opimisation etc. BSC Room Ready for Installation No Yes Yes No Ye s No
BSS Complete BSS Planning - Request BSC equipment from the Warehouse - Request installation to Motorola - Request and receive SPC for the new BSC from NSS - Provide new CID, LAC Plan to Motorola - Provide essentials and request Abis/ Ater/ DIU connectivity for the new BSC/ XCDR to O&M. OMCR Provide Object Code-2 of the old BSC to Motorola. Motorola BSC, Rectifier, Battery Bank, Micro Cell installation and commissioning at site O&M - ECRF for required outage (if any) - Path connectivity from new BSC to MSC OMCR/ BSS - Preparing and testing of OML connectivity of the new BSC/ XCDR - Preparation of CIC/ MTL equipage as per pre-defined standard. OMCR - Upload of tested datagen from - Downloading tested datagen and CIC/ MTL scripts on BSC/ XCDR. Motorola Prepare Datagen of the new BSC as well as any modifications in scripts of the neighbouring BSCs BSS Test Calls at the test BTS site for all the CICs for any no- audio calls.
BSS/ O&M - Final cutover plan to be distributed to all the relevant teams including Customer Serivices of that region. - O&M to request ECRF for the planned activity. BSS/ O&M/ OMCR/ Motorola - Final traffic shifting of sites on the new links, (if required) Shifting of sites on the new BSC - Running of scripts on the neighbouring BSCs Motorola/ Optimisation/ OMCR - Drive testing to check call connectivity and handovers - Stats monitoring for the effected BSC(s) - Any Problems faced in the drive test should be immediately communicated to BSS/ NSS/ OMCR for resolution on piority basis. OMCR/ NSS - Communication of changed Cell IDs to Billing BSS - Update connectivity diagram of the region and circulate in relevant teams. NSS/ OMCR/ BSS Resolution of any problem faced Major Problems with regards new BSC cutover? Yes No Fallback to previous configuration
End of Document
Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 1 1 Newly Commissioned BSCs in PMCL Network
Objective Our objective is to deploy new BSCs nation wide to support 2004 new sites roll out that made us under a real pressure to support BSC capacity nation wide for new 100 sites in a month due to the serious competition with the other operator in Pakistan
Please find the main aspects that have been taken into consideration
1- BSC capacity is required for the upcoming project such as GPRS that needs extra resources from each BSC for PCU. Furthermore, Half rate implementation that needs also spare BSC capacity. In addition to that, DCS implementation that may need extra BSC resources if separate cell will be defined for DCS plus the existing defined GSM cell.
2- BSC capacity is required for the site expansion as it is required for the new sites
3- BSC capacity is a combination of mms connections, sites no., DRI no. and Erlang loadetc.
4- BSC boundaries is defined with Optimization to reduce the inter BSC HO aiming to improve PMCL network quality
5- BSC location is defined with complete co-operation with Transmission, Property and O&M to be outside the MSC premises to get the following advantages that have been understood now after many cases: Reducing the probability of getting the network outage if the nearest MW links from the MSC premises is getting down by having multiple routing of the Aters Improving the transmission network Immediate improvement of the Transmission network, by offloading some of the used E1 links capacity. Long term improvement of the Transmission network, by connecting the new sites that are coming up to the nearest BSC via the shortest MW links with a suitable capacity.
6- Standardization of the Ater connectivity and the CIC definition.
7- Deployment of SEPARETE Power Supply system for the new BSC even if it is co-located with a BTS & DDF
8- Installing a new DDF instead of connecting the cables directly from the top plan of the BSC.
9- Shifting the BSC from one MSC to a new MSC will be easier by shifting only the Ater to the new MSC (New Karachi MSC is a real example)
Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 4 4 North Situation on 10 May 2004 (3 NEW BSCs)
MMS MSC Side Busy S.No BSC Cabinet Type No. of Cages In Operation Avail BSC PCU BSC Free BSC - XCDR XCDR - MSC Number of Sites DRI No. Peak Load in BI (Erl) 1 Hot Shots BSSC 2 48 22 6 20 7 28 15 152 424 2 Blue Area BSSC 2 48 32 6 10 10 36 19 161 498 3 Sitara Market BSSC 2 48 21 0 27 8 32 13 147 418 4 I-10 BSSC 2 48 24 0 24 8 32 12 122 276 5 Faizabad BSSC 2 48 21 0 27 9 36 12 137 532 6 Satellite BSSC 2 48 24 0 24 6 24 17 198 456 7 Saddar BSSC 2 48 18 0 30 8 32 10 124 348 8 AWT BSSC 2 48 23 0 25 8 32 12 162 615 9 J helum BSSC 2 48 26 0 22 9 36 13 184 794 10 Mardan BSSC 1 24 11 0 13 3 12 7 81 237 11 Abbotabad BSSC 1 24 9 0 15 4 16 4 56 189 12 Northern Areas BSSC 2 48 21 0 27 10 40 8 116 451 13 Taxila BSSC 2 48 12 0 36 6 24 4 59 255 14 Gujar Khan BSSC 1 24 12 0 12 6 24 5 72 295 15 RMC Hahtnagri BSSC 2 48 28 0 20 7 28 18 239 669 16 City Tower BSSC 2 48 21 0 27 6 24 11 134 495 325 12 North 696 337 359 115 456 180 2144 6952 Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 5 NORTH REGION Please find the attached two tables that explain the situation on 20 February and today after getting 7 new BSCs in the north region
Newly Commissioned BSCs
1- BSC Faizabad (Commissioned 29-02-04)
This Dual cage BSC was planned for the following main reasons: - Offload BSCs of Satellite Town and Hot Shots in Rawalpindi and Islamabad Region. - Offloading these BSCs gave us a proper capacity to accommodate upcoming sites. - Also offloading of Hot Shots BSC gave us the possibility to re-parent some of the sites of BSC Blue Area to BSC Hot Shots then dismantling BSC Blue Area back from 4-Cage Configuration to standard 2-Cage Configuration.
2- BSC Abbottabad (Commissioned 17-03-04) This single cage BSC was planned for the following main reasons: - Offload BSC Northern Areas - Save on the leased line cost of upcoming sites in the area. - Cell Planning are working in 53 new sites in the northen area BSC project
Before commissioning this BSC, Only 3 Cell Sites were operational in this area (2 in Abbottabad and 1 in Thandiani). The fourth one has been ON AIR after getting this BSC in service.
3- BSC Gujar Khan (Commissioned 11-04-04) This single cage BSC was planned for the following main reasons: - Offload BSC Northern Areas - Make transmission plan for Gujar Khan and adjoining areas more viable from leased line point of view. - Save on the leased line cost of upcoming sites in the area. - Cell Planning are working in 53 new sites in the northen area BSC project
To start with, only Gujar Khan, Mandra and Rawat sites have been connected to this BSC. Other sites will be shifted to it as and when we get leased lines for them.
This BSC is now running with 6 Aters; two routed through PMCLs own microwave network, rest are using PTCL leased lines. Now we are in a position of foregoing at least two leased lines back to PTCL.
4- BSC Sitara Market (Commissioned 17-04-2004) This dual cage BSC was planned for the following main reasons:
- Offload BSC Blue Area and BSC Hot Shots - Take into account the future rollout plans of sites especially in Islamabad city where many sites are to be deployed this year.
This single cage BSC was planned for the following main reasons:
- make transmission plan for Taxila, Hasanabdal, Wah Cantt and other suburban areas more viable from leased line point of view. - Further offload BSC Northern Areas - save on the leased line cost of upcoming sites in the area.
To begin with, this BSC will be commissioned with Hasanabdal, Taxila and Hattar sites. Other sites will be added to it as and when we get leased lines for them.
6- BSC AWT-RWP (Commissioned 24-04-2004)
This dual cage BSC was planned for the following main reasons:
- Offload BSC Saddar - Take into consideration the future rollout plans of sites especially in Rawalpindi and Rawalpindi Cantt areas where many outdoor sites are to be deployed this year. - Make MMS available for future sites in this region
7- BSC I 10 - ISB (Commissioned 1-05-2004) This dualcage BSC was planned for the following main reasons:
- Offload BSC Faizabad - Take into consideration the future rollout plans of sites especially in Rawalpindi/ Islamabad areas where many outdoor sites are to be deployed this year. - Make MMS available for future sites in this region Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 7 7 Central Situation on 20 February 2004
Previously, BSC Multan was facing MMS constraint where it was zero so second BSC in Multan was a must. Moreover the trunk utilization for the BSC was around 78%, which has been improved after the split. BSC location at the Rashidabad site is a good place from TXN planning point of view as well. The new BSC will serve the North region of Multan which includes the roads leading to Lahore and Faisalabad. The 2 nd Multan BSC gives us a proper capacity for the upcoming new sites in the roll out.
2- BSC Muslim (Commissioned 06-03-2004)
The BSC has offloaded Lahore_BSC_1, the trunk utilization for both the BSCs has been improved considerably. Also from hardware mms connections - point of view we can now accommodate new sites in both the BSCs easily.
3- BSC Model Town (Commissioned 27-03-2004)
The BSC was planned to offload the BSC_Liberty & BSC_2 in MSC_3. And it can be seen that the Trunk Utilization of both these BSCs has been improved. Moreover we have more Free MMS in both the BSCs to deploy the new sites. BSC_Liberty is now been shifted to Liberty_Chowk site taking into consideration the standardization aspects.
4- BSC_Okara (Commissioned 01-04-2004)
A single cage BSC has been deployed currently having only one site. But according to the plan for 2004 we will have 3 more cities connected BSC_Okara, so for future requirements the deployment of this BSC was necessary to reduce the L.L. requirements of those 4 new cities.
5- BSC Regal (Commissioned 03-04-2004)
The BSC is a split part of BSC_Eden. Once again the deployment of new BSC has improved the Trunk Utilization of the both BSCs. Furthermore, it improves the transmission capacity by offloading some E1s plus connecting the new sites direct to the BSC location using direct link without routing it to multiple of sites. In addition to that, it gives us a proper capacity for the upcoming new sites in the roll out.
Faisalabad had previously two BSCs in the city which were almost over utilized and considering the growth of the network in the Central-2 region there would be some time when we had to face the hardware constraint in terms of MMS. Also we already having 8 Aters in BSC_Faisalabad & 7 Aters in BSC_Sahil. A new BSC has certainly offloaded both the BSCs and have given enough capacity from hardware point of view for new sites.
7- BSC_Khanewal (Commissioned 15-04-2004)
A single cage BSC has been deployed currently having only one site. But according to the plan for 2004 we will have 3 more cities connected BSC_Khanewal, so for future requirements the deployment of this BSC was necessary to reduce the L.L. requirements of those 4 new cities.
8- BSC Chouburji (Commissioned 17-04-2004)
The BSC is a split part of BSC_RAVI. Once again the deployment of new BSC has improved the Trunk Utilization of the both BSCs. Furthermore, it improves the transmission capacity by offloading some E1s plus connecting the new sites direct to the BSC location using direct link without routing it to multiple of sites. In addition to that, it gives us a proper capacity for the upcoming new sites in the roll out.
9- BSC Muzaffar_Garh (Commissioned 22-04-2004)
A single cage BSC has been commissioned. It will cater only one site in the beginning but will have 3 new cities connected to it in this year. The BSC is connected to MSC_7. BSC and site were locked after commissioning because of the city not commercia lly launched.
10- BSC Samanabad (Commissioned 24-04-2004)
Shifting of BSC Ravi outside Eden A dual cage BSC has been commissioned in order to shift traffic of BSC-Ravi from Eden Center to Samanabad. BSC Ravi has been decommissioned. The 2 nd advantage behind this shifting was to standardize the database for this BSC plus the other advantage of improving the transmission network
11- BSC Jhang (Commissioned 29-04-2004) A single cage BSC has been commissioned. In the beginning it will cater for 2 cell sites in Jhang City. Later on 5 new cities in the surrounding will be connected to it in this year. The BSC has been connected to MSC_7.
12- BSC K-Block DHA (Commissioned 1-05-2004)
The BSC is a split part of BSC_Defence. BSC K-Block was commissioned in order to share the load of old BSC Defence. It has improved the Trunk utilization. Before shifting, the trunk utilization for this BSC was exceeding the threshold; also we have already more than 1000 trunks in the BSC, so to cater the traffic load from the sites in this BSC, the split of the BSC is necessary.
Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 12 12 South Situation on 20 February 2004
Newly Commissioned BSCs in PMCL Network BSS Planning & Deployment 15 SOUTH REGION Please find the attached two tables that explain the situation on 20 February and today after getting 3 new BSCs in the south region
Newly Commissioned BSCs
1- BSC HINO (Commissioned 13-03-04) This BSC offloaded BSC_creek, by reducing the sites connected to creek from 39 sites to 13 sites then offloading another sites from Shanaz BSC to creek BSC to keep the proper loading over creek and chapple. Furthermore, improving the transmission network by offloading some E1 capacity The Trunk Utilization will be improved for both BSCs Creek & Shanaz.
2- BSC ATC (Commissioned 17-04-04) This BSC offloaded Anum, Premier and Chapple BSCs, which were having different BSC capacity constraints. In addition to that, the latest trunk utilization values for those BSCs are more than 90% (Ater Blocking was occurred at Chapple)
Now, the above mentioned BSC have almost the same loading with new capacity to support the upcoming new sites in Karachi plus good improvement in the trunk group utilization over all of those BSCs.
We got spared mms connections after swapping especially at Anum BSC where we were not having a single spare mms.
3- BSC Nacon (Commissioned 28-04-04) This BSC offloaded Chapple BSC, which was having different BSC capacity constraints. In addition to that, the latest trunk utilization value of Chapple BSC was more than 90% (Ater Blocking was occurred at Chapple)
By integrating this new BSC in our network, we have some more space availability to cater the upcoming sites in South.
Trunk Utilization for BSC Chapple has considerably been improved with the availability of spare mms. Movement of BSCs outside the MSC Locations
Introduction
Till mid of 2003, when the network size was small, all BSCs were kept at one location closer to RXCDR and MSC locations. This approach had its own advantages in terms of secure power source availabi lity, ease of O&M activities and BTS re-parenting.
However, with the increase in network size, this approach was no more valid and was creating troubles in terms of the following: Increase in outages due to microwave hub sites getting down. Huge cost of poor planned transmission network by having most of the MW links 16 E1 or even SDH 63 E1. Sometimes; 2 MW links were installed on the same route just to afford the required capacity. A lot of new sites and expansions were halted due to chock of the transmission routing
NIPA BSC in Karachi was the first real example of getting the BSC outside MSC premises and after that BSS planning has faced some objection from transmission where they preferred the old approach by installing any new BSC in the MSC premises. After more than two months of this objection, they realized the improvement of this project on the Transmission network Capacity and Design.
NIPA BSC spared 15 E1 over multiple MW links which is more than 60% of the current MW usage. Outage will be reduced as much as Aters are connected over multiple routing
Advantages for this approach:
To install the BSCs in a remote location we can get following advantages:
a) The TXN plan for the sites in a particular BSC is much more simplified than that for the BSCs, which are collocated with the MSC. This reduces the Microwave concentration at MSC location, which in turn improves the microwave frequency reuse.
b) Connecting the Aters between the remote BSc and its XCDR at MSC side using MULTIPLE routing over two, there sometimes four different routing to protect the area covered by this BSC from any service outage due to MW link outage taking into consideration 70% trunk utilization at the busy hour.
c) We can improve the E1 capacity of the existing microwave network using this approach. For the BSCs collocated with the MSC, the microwave connectivity is quite complex. For the sites, which are far away from the BSC, more than 6 hops are used for microwave connectivity. Using the approach of Remote BSCs we can have an average microwave connectivity consisting of 2 hops only in proper dimensioning.
d) With the growth of our network we are facing MW band interference on almost all the hub sites, so by adapting this approach we can minimize the possibility of interference, which will reduce our network down time.
e) By having a BSC in a remote location, it will be en easier practice to re- parent the BSC to another MSC simply by installing one hop from BSC to the new MSC location instead of having the BSC is located at one MSC location and its XCDR is located at another MSC location.
f) Moreover, having a complete power supply system starting from newly second GENSET to complete separate Power Supply System will protect the BSC from any major power failure.
g) By installing BSCs away from MSC, it will be easier to manage the space problem in the MSC vicinity and we can add more RXCDRs in our network. It was a clear example at EDEN Center in Lahore where there is no space available to install any BSC / RXCDR so that getting the BSC outside EDEN is a MUST and it is better to install the BSCs remotely for future planning prospective.
Current Network Situation to date:
Using this approach we have around 20 Dual cage BSCs outside MSCs premises in the main three cities 4 BSCs have been commissioned in ISB/RWP, 9 BSCs have been commissioned in Lahore and 7 BSCs have been commissioned in Karachi.
In addition to that, more than 20 BSCs have been commissioned in the remote cities plus the upgrade of single cage BSCs to Dual cage BSCs (Remote Cities in the soutrh region, Quetta, Sukkar and Hyderabad).
Due to the following steps taken in order to provide extra protection in terms of downtime and ease of O&M, there are no significant issues reported.
1. All BSCs have been secured by putting an additional Rectifier Power System. 2. All BSCs have planned to be equipped with 2 nd genset, a 1000 liter fuel tank and double ATS panel 3. A 27KVA dedicated Transformer for each BSC location 4. All BSCs have been equipped with 30KVA 3phase stabilizer 5. Location have been selected with no access issues for timely O&M 6. Multiple Ater routes have been provided (2 or 3) for the sake of redundancy. 7. Keeping all of those new BSC on the same standardization criteria (mms connectivity, Ater connectivity, Ater/4 DI Us, CIC no., Ater mapping and One MTL per each Ater. 8. Using new DDF to use it for any port MMS - connections instead of the direct connection from the top plan of the BSC.
Conclusion
This new approach of getting the BSC installed outside MSC premises has shown its advantage clearly in PMCL network and seems to be the best possible solution for any bigger network growing with a rapid pace (Attique) BSC Split Planning Procedure
1. Objective:
The objective of this document is to outline the complete process and responsibilities for all involved that are to be followed strictly for a successful and timely splitting of a BSC into two.
2. Introduction:
BSCs in a Cellular Network are sometimes required to be splitted because of a number of reasons e.g.:
- Excessive Erlang Loading of the BSC - Excessive Trunk Utilization of the BSC - New Sites being rolled out in the area being served by an existing BSC. - Existing BSC reaching its Physical/ Logical capacity Limits
For successful splitting of a BSC into two, a clear process needs to be defined that will be followed by all the relevant teams of PMCL at all times.
4. PLANNING ASPECTS INVOLVED IN BSC SPLITTING:
Following physical and logical capacities are associated with a Motorola BSC operating at GSR-6 Software version and whenever any of these parameters reaches a certain defined threshold planning for splitting the BSC must be initiated:
3.1 RTF Handling Capacity for the BSC operating at GSR-6 Software version is 384 RTFs. Weekly BSS Connectivity Updates prepared by Regional BSS Planning Teams contains the number of RTFs operational at each BSCs and Planning for the split must be initiated whenever operational RTFs limit reach 60% of the maximum allowable limit.
3.2 100 BTS Cell Sites and 250 GSM Cells can be operated for BSCs operating at GSR-6 software version. However BSS Planning must also consider the new Cell Sites being rolled out in the service area of a particular BSC and should plan the split even if the current operational Cell Sites in the service area of the BSC are less than 60% of the maximum allowable limit.
3.3 384 DRIs can be operated in a BSC operating at GSR-6 software version; however as the RTF Handling capacity of the BSC remains at 512 therefore 122 DRIs will not be having any RTFs.
3.4 RSL handling capacity of the BSC is 250. Normally a site operating at 5/5/5 (15 DRI s) will be requiring one RSL, since this is the physical limit of 2 Mbps E1 Link. Normally a redundant RSL is equipped whenever a number of operational RTFs exceed 15 as second E1 will be required to carry the traffic to the BSC.However RTF handling capacity for 1 RSL will be 24.
3.5 Maximum number of GPRS Links or GSLs that this BSC can handle is 12.
3.6 MMS handling capacity for the BSC is 128.This number of MMSs can only be operated in a 4 Cage BSC and 4 Cage operation of the BSC unless absolutely necessary should be avoided. A 2 Cage BSC handle 48 MMSs and planning for the split of a 2 Cage must be initiated whenever number of operational MMSs crosses 32.
3.7 250 Paths can be handled by a BSC operating at GSR-6. Normally one BSC Site operating at 5/5/5 requires only one Path to the BSC.However certain overloaded Sites can have two Paths.
3.8 LCFs Handling capacity of the BSC is 25. As one GPROC card can operate one LCF Function and one 2 Cage BSC has a maximum of 15 GPROCs, in our network therefore this number of LCFs can only be operated in 4 Cage BSC whose operation as already stated must be avoided.GPROC distribution for a 2 Cage BSC is normally as follows:
2 GPROCs for BSP/Redundant BSP Functionalities 1 GPROC for OMF Functionality 1 GPROC Slot for NVM Board 12 GPROCs are available for supporting LCF (MTL or RSL) Functionalities.
Now, each GPROC-2 Card can operate 2 MTLs if MTL functionalities are operated on that GPROC-2 Card. For (RSL) LCF functionality following planning rules applies for single GPROC-2:
2*Number of Sites+RTFs (in those sites) < 120
BSS Planning Engineers need to have a constant look at the MTL Utilization and RTF Handling Capacities for the GPROC-2 Cards and whenever MTL Utilization reaches more than 40% additional MTL Links should be planned which consequently requires more GPROC-2 Cards and if need be split of the BSC if all the GPROC-2 Slots are utilized.
3.9 Standardized BSCs in PMCL are operational on 8 Aters i.e. 936 active trunks this number can increase up to 1176 Trunks (10 A ter ). However when the number of operational Aters reaches 10 than Planning for the split must be initiated. TGRP stats issued from NSS Team give a clear indication about the operational status of Trunks associated with a BSC
3.10 If the BSC Signaling load is such that all the 16 MTLs are operating at more than 40% of Link Utilization then it becomes important to plan the split immediately because this overload factor can have harmful effects on BSCs operational performance.
3.11 If Busy Hour Call Attempts (BHCA) reaches more than 90,000 than again planning for the split becomes inevitable.
3.12 I t is to be noted that new BSCs must be planned BEFORE we reach the above mentioned capacities.
3.13 Often times, we also have to plan BSC splits if we reach at least 3 or more leased lines for a remote city and it becomes, financially feasible to put a BSC in that city instead of having more than 4 leased lines for that area.
4. BSC Site Selection Aspects
4.1 Efforts should be directed towards balancing the traffic of the BSCs involved from as many aspects as possible (e.g. MMS used, Traffic, TRX etc.) However we can also plan in a way to give lesser MMS used for a future BSC if we are foreseeing many sites in future rollout.
4.2 Site where BSC is to be located must preferably be the one that is also a transmission hub. This is done so as to ensure that we can get more than 2 Ater paths from the BSC to XCDR and thus provide redundant Ater connectivity. I n addition to that it will also ease pressure on BSC deployment as lesser number of new MW links will be required to be deployed.
4.3 I n selecting the BSC boundaries, care should be taken so that there are not many bad inter-BSC handover patches. Once, the sites for the future BSCs have been selected, it is always best to get it approved from Optimization. An example of BSC distribution is shown in Annexure 1.
4.4 Site for the new BSC should have enough room space for BSC cabinet, a rectifier, battery bank and a MW rack at least. It should be kept in mind that selected site does not have too much of room renovation required before BSC installation is to be done.
4.5 Selected BSC site should have permission and room to place 2 nd genset.
4.6 Site selected should have 24/7 access in order to help O&M team.
The objective of this document is to outline the complete process and responsibilities for all involved that are to be followed strictly for a successful and timely re-parenting of a BSC from one MSC to another.
2. Introduction:
BSCs in a Cellular Network are sometimes shifted from one MSC to another because of a number of reasons e.g:
- Exceeding processor load at existing MSC - Exceeding Subscriber number that an MSC can handle - New MSC commissioning
For successful shifting of a BSC from one MSC to another, a clear process needs to be defined that will be followed by all the relevant teams of PMCL at all times.
3. PREREQUISTES/ PRECAUTIONS FOR BSC SHIFTING:
Re-parenting of BSC from BSS side is a fairly simple process as it involves very few database changes at the BSC, Most of the database changes are made at the MSC.Only database change which is implemented at the BSC is to change the DPC (Destination Point Code) of the BSC.This parameter is basically changing the Parent ID (or MSC ID) of the BSC.However following things are to be ensured from BSS side before a BSC could be re-parented.
4.1 Laying of 2 Mbps (PCM) Cables from the XCDR to the E1s allocated for the new MSC.OAN Engineers must ensure that all the newly laid cables do not have any issue as for as Connectors jointing and soldering is concerned.
4.2 Since all the database changes are implemented at the MSC therefore NSS Team must ensure that database changes have been accurately made.
4.3 BSC Re-parenting activity must be initiated in the least traffic hours which are normally after Midnight usually.
4.4 BSS Engineer coordinating the re-parenting process MUST have an updated A ter / A-interface Connectivity Diagram of the BSC being shifted.BSS Engineer must also have the proposed DDF/Patch Panel Connectivity Diagram for the new MSC.
4.5 OMC-R should check the complete operational status of the BSC to be re-parented for any alarms and functional abnormalities. A BSC must not be shifted if it has majority of Signaling links down or the Operation and Maintenance Link (OML) is down with the OMC-R. If certain Cells or Sites are having Traffic Outage, then OMC-R must inform concerned OAN Engineers as well as note it down themselves, in order to avoid any confusion after BSC Re-parenting.
4.6 Optimization Engineering should also be taken into loop before proceeding ahead with the shifting process. 4. STEPS INVOLVED IN BSC RE-PARENTI NG:
4.1 Lock all the MTLs of the BSC both from the MSC and BSC side. (Any database/state change of the devices at the BSS end must be implemented by OMC-R).
4.2 Change the DPC of the BSC. (New DPC of the BSC will be the Originating Point Code (OPC) of the MSC to which the BSC is being shifted).
4.3 Start physical shifting of the E1s to new MSC. In order to have minimum Traffic Outage it is recommended that E1s carrying MTLs must be shifted in the beginning. Normally BSCs in PMCL Network have 32 E1 links and number of operational MTLs for 32 E1s is 8.Therfore these 8 E1s must be shifted first of all.
4.4 Once the E1s carrying MTLs have been shifted to the new MSC, unlock all the MTLs both from the BSC and MSC sides. BSS Engineer to confirm from both OMC-R and NSS that all the MTLs are in busy state. If so than shifting of other E1s can be initiated. If the MTLs are not in Busy/ Active state then shifting process must be halted and fault must be isolated and rectified. (Revert-Back options must be kept open at all stages of the shifting process).
4.5 I f all the MTLs are in Busy State then OMC-R should randomly check some of the Cells that if their status is Unbarred. I f Cells are in barred, state then NSS Team needs to verify Signaling Database at their end.
4.6 If all the Cells are in unbarred state then further shifting of the E1 Links can be carried out One by One. State of each E1 link must be confirmed as Busy before proceeding further.
4.7 Once all the MTLs are Busy and all the Cells are in unbarred state then OMC-R needs to change the value of the Location Update Timer to a suitable value so that all the Subscribers in the Service Area of that BSC can have a forced Location Update in the VLR of the new BSC.
Normally this value is set at 40 Decihours in PMCL Network which means MS sends Automatic Location Update Request after about 6 and Half hours to MSC.Changing this value to 1 will mean that every MS will send Location Update Request after 10 mins, in this manner all the MSs in that particular area will have Automatic Location Update in around 30 to 40 minutes. This small value of Location Update Timer (rr_t3212) will put a lot of Signaling load on Processors of BSC and MSC, therefore it has been recommended to carryout BSC re- parenting process in least Traffic hours. Another recommendation as for as changing the value of the Location Update Timer is concerned is to change the timer value on geographical area basis, particularly for large BSCs covering several cities.
4.8 Once all the E1s/MTLs/Cells are in normal state and value of Location Update Timer has been shifted to the normal value of 40 decihours, BSC must be given a Soft Reset in order to remove any issues which may arise as Parent Clock of the BSC has been changed. Reinitializing the BSC will resynchronize the BSC Clock with the new Parent MSC.
4.9 After the BSC has returned back to the Busy-state after restarting than all the Cells/ MTLs/ E1s must be checked before closing the activity.
4.10 NSS Planning must coordinate with OMC-R and Optimization for Stats Monitoring and Drive Testing after successful completion of the activity. 5. BSC RE-PARENTING IF MSCs ARE LOCATED AT DIFFERENT LOCATIONS
5.1 The above procedure outlines the details of BSC re-parenting when the two MSCs are located at the same location.
5.2 This procedure can be more cumbersome and time-consuming hectic if the two MSCs are located in two different locations, whether in the same city or in two different cities as it means that Transmission Planning will then have to give the new Transmission plan that may or may not include dependency of leased lines and deployment of new MW links.
5.3 These transmission media, we used to find immediate solution for it by reducing some of the inter-MSC connection keeping 70% utilization or even exceed it based on the urgency situation that we are facing
5.4 Rest of the plan will however, be the same as described in Paragraphs 4 and 5.
Finally, roughly speaking BSS planning in the north region has done around 15 BSC re-parenting since Alcatel MSC has been lunched and during Basant event and BSS planning in the center has done around 12 BSC re-parenting since FSD MSC has been launched and also during Basant event. Furthermore, BSS planning in the south region has done 3 BSC re-parenting since KHI Alcatel MSC has been launched. In total of more than 30 re-parenting during the last 5 months. BTS Site Re-parenting Procedure
1. Objective:
The objective of this document is to outline the complete process and responsibilities for all involved that are to be followed strictly for a successful and timely re-parenting of a BTS site from one BSC to another, whether within the same MSC or in another MSC.
2. Introduction:
BTSs in a Cellular Network are sometimes shifted from one BSC to another because of a number of reasons e.g:
- Site on the border with another BSC having excessive Inter-BSC Handovers (Optimization initiated) - If one BSC is reaching its traffic carrying limits while some neighboring BSC does not have much traffic, then shifting of a site (or a number of sites) can improve and balance Trunk Utilization and Erlang Load of the two BSCs. - Shifting to be carried out on request of Billing
For successful shifting of a BTS Site from one BSC to another, a clear process needs to be defined that will be followed by all the relevant teams of PMCL at all times.
3. PREREQUISTES/ PRECAUTIONS FOR BTS SI TE SHIFTING:
3.1 Following BSS Planning aspects must be considered for the BSC in which site is being shifted before actual shifting can take place.
RTF Handling capacity of the BSC must be considered and care must be taken that by shifting the site RTF handling capacity of the BSC will not be crossed. Number of paths (MMSs) on which the sites is currently operational and whether the BSC does have those number of paths available. Assign the site to be re-parented to a GPROC which meets the following Planning Criteria:
2*Number of sites + RTFs (In those sites) <120
3.2 I f the two BSCs are located in different locations, BSS Planning must request for the new Transmission plan of the site from Transmission Planning.
3.3 BSS Planning Engineer must ensure that new BSS Planning Database must be available with NSS and OMC-R teams at least 24 hours before the actual shifting of the site so as to allow them to have sufficient time to carefully implement the database.
3.4 Optimization Engineering must be kept in loop for the duration of re-parenting activity.
3.5 OMC-R must check any alarms or functional abnormalities at the site and inform concerned OAN Engineer and note it down with them so as to avoid any confusion after site re-parenting. 5. STEPS I NVOLVED I N BTS SI TE RE-PARENTI NG:
Following steps must be followed while shifting a BTS Site from BSC to another:
4.1 2 Mbps Abis pair from BTS site to BSC site must be thoroughly checked before proceeding ahead with the shifting.
4.2 Creation of the relevant database must be confirmed from OMC-R and NSS Teams.
4.3 Site re-parenting activity must be initiated in the least traffic hours.
4.4 OAN is responsible for the change in path of the site from one BSC to another.
4.5 Once the site has been shifted to the new BSC than Busy Status of the path (MMS) and Signaling Link (RSL) must be confirmed.
4.6 After the site has completely downloaded new database Busy-status of all the Transceivers of the site must be checked.
4.7 After checking the Busy-status of all Transceivers all the Cells associated with the BTS site must be checked for Unbarred Status and whether Calls are being initiated in the Cells.
4.8 As the re-parenting activity is initiated in the least Traffic hours therefore its always possible that Calls might not initiate for first two or three intervals in that particular site.Therfore OMC-R needs to constantly monitor statistics associated with Call Setup, Handover Success and Drop Calls and if there is any persistent abnormality must report it to concerned OAN/BSS Engineers.
4.9 Optimization team should then drive-test the relevant areas in order to make sure that the shifting exercise had been successful.
MTLs Reduction & Standardization
1. Objective As a part of BSS Planning process, an effort was made to standardize the number of MTLs (Message Transfer Links)/C7s.
2. Introduction: Before that there was no correlation b/w the number of MTL/BSC with the actual messaging load for that BSC. All the major BSCs in big cities were having 16 MTLs
Due to this large number, MTL utilization was very nominal. However on the other hand, major resources of these BSCs were being used for handling these high numbers of MTLs.
In addition to that, each un-used MTL is reducing the CIC defined by 4 CIC which means 32 CIC for those extra MTL that is equal one complete DIU is not used for a voice circuit as it is not performing any of the signaling tasks.
3. MTL Planning Criterion Following hardware and software limitations on BSS and NSS were kept in mind before going for MTL number standardization:
3.1 Before SR 9.0 release at Siemens switch, each C7 could handle 200mErlang of traffic. However with the implementation of SR 9.0 software release at Siemens switches and with addition of dedicated hardware SSNC (SS7 Signaling processor), each MTL can now handle up to 400mErlang.
3.2 On the BSS side, as per Motorolas recommendation, processor carrying MTL(s) on it must be running less or equal to 20% utilization.
3.3 Number of MTLs has a direct relationship with number of traffic circuits defined for a particular BSC.
4. MTL Planning Rules (One MTL/ each Ater) On the basis of above-mentioned criterion, the following rule was devised.
4.1 No of MTLs for a particular trunk group will be equal to no of Aters defined. e.g. If a BSC have 7 Aters, no of MTLs will be 7. Similarly a BSC having 8 Aters, number of MTLs will be 8 and so on.
4.2 The 2 raise to the power n crieterion for no of MTLs will no more be followed.
4.3 MTLs stats has to be checked on a weekly basis in just to keep tracking on it
4.4 Since, we have done this reduction; we didnt face any problem related to MTL no.
5. Achievement
This standardization resulted in the following: 5.1 Extra resources of BSC, which were earlier being consumed with 16 MTLs, were released.
5.2 Extera CIC that help us in some cases to improve the trunk utilization and to use it as a company assets to get more revenue.
5.3 These resources were then better utilized in handling more number of sites
5.4 This resulted in having more number of interfaces in terms of mms that could be configured with this MTL reduction
5.5 Switch resources in terms of Silt cards (signaling hardware) were released
METHODS TO IMPROVE TRUNK UTILIZATION
Introduction:
Keeping Trunk utilization for all BSCs including (Local and Remote ones) is BSS Planning KPI. Threshold set by management for this KPI is 70%.
BSS Planning steps to achieve this KPI:
During working on Business Plan for the year, working is done in terms of hardware and media requirements to obtain this KPI. The following calculations are considered: 1. No of RXCDR cabinets required for each BSC based on the traffic trends 2. No of Leased Lines required on quarterly basis for all remote BSCs for BSC- RXCDR connectivity 3. No of Microwave Links required for all BSCs within a city for Ater connectivity
All these calculations are made keeping in mind the Trunk Utilization threshold set by management which is 70%
Regular Monitoring and steps involved ensuring the KPI:
NSS is responsible to generate a report on daily basis telling the latest status of Trunk utilization. Whenever a BSC exceeds this figure for a certain amount of days one of the following measures are taken to keep it below the threshold.
a) The first approach that BSS planning has started with was auditing of the available resources that allow us to use more than 90 DIU were un-used, some of them were blocked due to maintenance issue and a lot of them were not connected as all
b) 4 DIUs for each Ater rule has been implemented on all of the BSC during the standardization plan (less than 10 BSCs are under progress)
c) improvement of the CIC defined no. by reducing the MTL from 16 to 8 on each BSC (One MTL per each Ater)
d) Defining the optimal CIC no. on each BSC based on its Aters/DIUs no. which had a very good impact on the network quality by reducing NO AUDIO call problem at least on the BSS part (Inter MSC connections are under NSS domain).
e) Additional DIUs can be added to a BSC. Exact requirement is calculated considering the Erlang Load of a BSC taking into accounts the future expectation based on the traffic trends.
f) Sometimes we have to face an H/W constraint in terms of DIUs at NSS end, and then we have to shift DIUs from one BSC to another just to keep both balanced in a proper limit.
g) Few sites can be reparented considering the optimal boundary of the BSCs. In this regard inter-BSC HOs and inter-MSC HOs are considered deeply. For that we need to consult Cell Optimization Team. This scenario is valid only in case the BSC and its surrounding BSCs, have an imbalanced load. Else, this approach will only be shifting the problem from one BSC to another.
h) If there is a scenario that in an area new sites are expected in near future and the existing BSC is already full to capacity then a new BSC is planned by splitting the area covered by the existing BSC. DIUs are calculated according to the expected Erlang Load for both the BSCs.
i) The standard defined for Aters can accommodate maximum 8 Aters for a BSC, so an optimal decision is taken to improve the Trunk Utilization for a BSC which has already 8 Ater links.
j) Based on the new approach, two XCDR will be connected to each BSC especially in the main cities just to have 16 Aters that can carry out 1400 Erl load taking into consideration that in GSR 6, BSC can support 2127 Erl load.
k) For BSCs in the remote areas, LLs are planned according to the requirement in a near future taking into consideration the cost of those leased line
New Planning Rules for New BSCs
1. Objective: This document explains new planning rules for the new BSCs in PMCL network taking into consideration the benefits of the new s/w release GSR.6
2. Introduction:
New BSCs are planned in the network to support the additional capacity required for the following reasons: Upcoming new TRX expansion Upcoming new sites in the area of this BSC based on the roll-out Upcoming project that needs extra capacity of the BSCs such as GPRS, Half Rate and DCS 1800 MHz Exceeding any of the BSC planning factors such as MMS ports, no. of supported cells, Erlang load, TRX capacityetc. Reducing the cost of the PTCL L.L. as Opex by installing one BSC in the remote cities that we will connect 3-5 new cities with more than 5 sites to it as per roll-out plan.
Due to the above mentioned reasons Mainly the upcoming new sites, GPRS, HR, DCS BSS planning done their best to implement more than 20 new BSCs in the last two months plus more than 15 new BSC during the future
3. BSC Planning Criterion based of Traffic Handling
Planning for new BSCs is done based on the maximum dimensioning of a BSC in terms of number of MMS, no of TRXs and max erlang load that a BSC can handle. Bottleneck in any of these 3 dimensions can become a cause of a new BSC to be planned.
BSC dimensioning is different for different manufacturers including Motorola, Ericsson, Siemens and Alcatel. Even for a particular vendor it is different for different hardware versions and software releases.
For Motorola BSC in GSR6 as per Motorola answer - the BSC dimensions are:
Dual Cage BSC No of TRX 384 Erlang load 2127 erlang MMS 48
Each BSC is to be connected with one or more RXCDR for definition of trunks towards the MSC.
The previous approach that BSS planning were using to deploy additional BSC aiming to get a suitable BSC capacity for the upcoming project as per above mentioned was No of Aters 8 No of DIUs 32 No of circuits 936 (as per the standard defined by BSS Planning) Which it will make dual cage BSC can support us with 650 Erl because on the XCDR connectivity
Now, with around 70 BSC in PMCL network, we should go for the next approach
Future Approach
However, in GSR6, this max load handling capacity of a dual cage BSC has gone up to 2000 erlangs. So with this increase in BSC traffic handling capacity, the old approach of 1 BSC connected to a single RXCDR is no more valid.
The most optimal approach now would be to connect one dual cage BSC with 2 dual cage RXCDR. With this configuration, each dual cage BSC would be having 16 Aters and 64 DIUs i.e. 1872 trunks. So keeping 70% Trunk Utilization as per management requirement the max erlang load which a BSC can support is 1300 Erl. so this configuration is more suited for GSR6 and will be adopted for future BSS expansions.
So our new planning approach will be Dual Cage BSC No of TRX 384 Roughly speaking, it can support around 28 sites 4/4/4 with 12 TRX/site = 336 TRX which is around 90% of the maxi TRX capacity Each site has 63 Erl/site, it total 1764 Erl in the RF part that will give us around 1250 Erl at 70 % Utilization
Erlang load 2127 Erlang 2 XCDR/BSC with 16 Aters and 1872 CIC that can support around 1300 Erl at 70 Utilization Additional XCDR is a MUST now to raise the BSC capacity to the above mentioned figure
MMS 48 16 MMS will be used for Ater then 32 MMS will remain for the sites connectivity
GPROC 16 4 are used as 2 for BSP, one for CSFP and one for Pool GPROC 6 will be used for MTLs (12 MTLs ONLY) The remaining 5 will be used for the sites (5-6 sites per each GPROC. Mobilink (An Orascom Telecom Company) MMS Dimenssioning I SB/ RWP MMS DI MENSI ONI NG_North Region MMS Dimensioning - Twin cities 8 10 9 7 8 8 6 8 - 6 - 6 - - - - 15 22 12 15 16 10 18 13 25 10 27 20 24 30 24 27 0 10 20 30 40 50 60 A W T B l u e
A r e a F a i z a b a d H o t
S h o t s I - 1 0 S a d d a r S a t e l l i t e S i t a r a
M a r k e t MMS Aters MMS PCU MMS Sites MMS Free MMS - Twin cities 6% 10% 5% 7% 6% 5% 6% 5% 50% AWT Blue Area Faizabad Hot Shots I-10 Saddar Satellite Sitara Market Free BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS DI MENSI ONI NG_North Region Peshawer MMS - Peshawar 22% 29% 49% Psh - City Tower Psh - RMC Hahtnagri Free MMS Dimensioning - Peshawar 6 7 15 21 27 20 0 10 20 30 40 50 60 P s h
-
C it y
T o w e r P s h
-
R M C
H a s h t n a g r i MMS Aters MMS Sites MMS Free BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS DI MENSI ONI NG_North Region REMOTE BSCs MMS Dimensioning - Remote BSCs 4 6 9 3 10 6 5 6 15 8 11 6 15 12 24 13 27 36 0 10 20 30 40 50 60 A b b o t a b a d G u j a r
K h a n J h e lu m M a r d a n N o r t h e r n
A r e a s T a x ila MMS Aters MMS Sites MMS Free MMS - Remote BSCs 5% 6% 13% 6% 11% 6% 53% Abbotabad Gujar Khan J helum Mardan Northern Areas Taxila Free BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning I SB/ RWP TRX DI MENSI ONI NG_North Region TRX - Twin Cities 6% 6% 5% 6% 4% 4% 7% 5% 57% AWT Blue Area Faizabad Hot Shots I-10 Saddar Satellite Sitara Market Free TRX Dimensioning - Twin Cities 162 161 137 152 122 124 198 147 183 184 208 193 223 221 147 198 0 50 100 150 200 250 300 350 400 A W T B l u e
A r e a F a i z a b a d H o t
S h o t s I - 1 0 S a d d a r S a t e l l i t e S i t a r a
M a r k e t TRX Free/ Spare BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX DI MENSI ONI NG_North Region Peshawer TRX - Peshawar 19% 35% 46% Psh - City Tower Psh - RMC Hahtnagri Free TRX Dimensioning - Peshawar 133 239 212 106 0 50 100 150 200 250 300 350 400 P s h
-
C it y
T o w e r P s h
-
R M C
H a h t n a g r i #
o f
T R X TRX Free/ Spare BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX DI MENSI ONI NG_North Region REMOTE BSCs TRX - Remote BSCs 0% 4% 9% 4% 6% 3% 74% Gujar Khan J helum Mardan Northern Areas Taxila Free TRX Dimensioning - Remote BSCs 56 72 184 81 116 59 289 273 161 264 229 286 0 50 100 150 200 250 300 350 400 A b b o t a b a d G u ja r
K h a n J h e lu m M a r d a n N o r t h e r n
A r e a s T a x ila #
o f
T R X TRX Free/ Spare BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) BSC Traffic Dimenssioning ISB/ RWP Based on the new s/w release GSR6, the maximum Traffic load for each Dual Cage BSC is 2127 Erl At 70% Utilization, will reach to 1300 Erl So that 2nd XCDR is a REQUIRED to reach to this Capacity Based on the actual situation, most of the BSC has ONLY 8 Ater/BSC (one XCDR for each BSC) This Capaicty is considered bacause of XCDR Capacity ONLY that has to be doubled BSC Traffic Capacity_North Region Trunk Utilisation - Twin Cities 44.53% 62.40% 35.17% 27.40% 51.55% 36.69% 46.57% 62.17% 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% 70.00% 80.00% 90.00% 100.00% AWT Blue Area Faizabad Hot Shots I-10 Saddar Satellite Sitara Market Traffic (Erlangs) - Twin Cities 615 498 532 424 276 348 456 418 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 A W T B l u e
A r e a F a i z a b a d H o t
S h o t s I - 1 0 S a d d a r S a t e l l i t e S i t a r a
M a r k e t T r a f f i c
( E r l a n g s ) Offered Traffic BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) BSC Traffic Dimenssioning BSC Traffic Capacity_North Region Peshawer Based on the new s/w release GSR6, the maximum Traffic load for each Dual Cage BSC is 2127 Erl At 70% Utilization, will reach to 1300 Erl So that 2nd XCDR is a REQUIRED to reach to this Capacity Based on the actual situation, most of the BSC has ONLY 8 Ater/BSC (one XCDR for each BSC) This Capaicty is considered bacause of XCDR Capacity ONLY that has to be doubled Trunk Utilisation - Peshawar 69.18% 66.75% 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% 70.00% 80.00% 90.00% 100.00% Psh - City Tower Psh - RMC Hahtnagri Traffic (Erlangs) - Peshawar 495 669 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 Psh - City Tower Psh - RMC Hahtnagri T r a f f i c
( E r l a n g s ) Offered Traffic BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) BSC Traffic Dimenssioning BSC Traffic Capacity_North Region REMOTE BSCs Based on the new s/w release GSR6, the maximum Traffic load for each Dual Cage BSC is 2127 Erl At 70% Utilization, will reach to 1300 Erl So that 2nd XCDR is a REQUIRED to reach to this Capacity Based on the actual situation, most of the BSC has ONLY 8 Ater/BSC (one XCDR for each BSC) This Capaicty is considered bacause of XCDR Capacity ONLY that has to be doubled Trunk Utilisation - Remote BSCs 41.56% 27.81% 65.15% 73.54% 37.55% 37.18% 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% 70.00% 80.00% 90.00% 100.00% Abbotabad Gujar Khan J helum Mardan Northern Areas Taxila Traffic (Erlangs) - Remote BSCs 189 295 794 237 451 255 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 Abbotabad Gujar Khan J helum Mardan Northern Areas Taxila T r a f f i c
( E r l a n g s ) Offered Traffic BSS Planning Deployment North Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning LAHORE B S C D e s c o n E d e n B S C _ 2 C h o u b u r j i D e f e n c e K _ b l k L i b e r t y M o d e l _ T o w n M u s l i m _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a T O T A L Used MMS for Aters 8 9 9 7 6 7 8 8 8 7 7 8 8 9 9 118 Used MMS for Sites 27 15 20 19 16 14 16 15 17 18 16 20 24 21 24 282 Total Used MMS 35 24 29 26 22 21 24 23 25 25 23 28 32 30 33 400 MMS Capacity per BSC 44 44 46 46 46 46 46 46 46 46 46 46 46 48 48 690 Total unused MMS 9 20 17 20 24 25 22 23 21 21 23 18 14 18 15 290 MMS Dimensioning_Center LAHORE 5% 3% 4% 4% 3% 3% 3% 3% 4% 4% 3% 4% 5% 4% 5% 43% Descon Eden BSC_2 Chouburji Defence K_blk Liberty Model_Town Muslim_Town Regal Samanabad Thokar Uet BSC_1 Shahdara Total unused MMS LAHORE 8 9 9 7 6 7 8 8 8 7 7 8 8 9 9 27 15 20 19 16 14 16 15 17 18 16 20 24 21 24 9 20 17 20 24 25 22 23 21 21 23 18 14 18 15 0 10 20 30 40 50 60 D e s c o n E d e n B S C _ 2 C h o u b u r ji D e f e n c e K _ b lk L ib e r t y M o d e l_ T o w n M u s lim _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a Used MMS for Aters Used MMS for Sites Total unused MMS BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS Dimensioning_Center FAISALABAD B S C F a i s a l a b a d S a h i l T r e a t Used MMS for Aters 8 9 9 Used MMS for Sites 27 15 20 Total Used MMS 35 24 29 MMS Capacity per BSC 46 44 46 Total unused MMS 11 20 17 T O T A L 26 62 88 136 46 FAISALABAD 8 9 9 27 15 20 11 20 17 0 5 10 15 20 25 30 35 40 45 50 F a is a la b a d S a h il T r e a t Used MMS for Aters Used MMS for Sites Total unused MMS FAISALABAD 26% 18% 22% 34% Faisalabad Sahil Treat Total unused MMS BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS Dimensioning_Center MULTAN B S C M u l t a n R a s h i d a b a d G u j r a n w a l a S h a h e e n a b a d Used MMS for Aters 5 5 7 5 Used MMS for Sites 20 16 18 9 Total Used MMS 25 21 25 14 MMS Capacity per BSC 48 46 48 46 Total unused MMS 23 25 23 32 GUJRANWALA 94 48 T O T A L T O T A L 10 36 46 12 27 39 94 B S C Used MMS for Aters Used MMS for Sites Total Used MMS MMS Capacity per Total unused MMS 55 MULTAN 5 5 20 16 23 25 0 10 20 30 40 50 60 M ultan R ashidabad UsedMMSfor Aters UsedMMSfor Sites Total unusedMMS MULTAN 27% 22% 51% Multan Rashidabad Total unusedMMS GUJRANWALA 7 5 18 9 23 32 0 10 20 30 40 50 60 G ujranw ala Shaheenabad UsedMMSfor Aters UsedMMSfor Sites Total unusedMMS GUJRANWALA 27% 15% 58% 1 BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS Dimensioning_Center MISCELLANIOUS B S C G u j r a t S i a l k o t S a h i w a l R a h i m
Y a r
K h a n S h e i k h u p u r a B a h a w a l p u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g M u z a f f a r
G a r h Used MMS for Aters 5 9 2 5 3 5 4 2 2 2 1 2 Used MMS for Sites 19 18 6 10 8 9 7 1 1 1 1 1 Total Used MMS 24 27 8 15 11 14 11 3 3 3 2 3 MMS Capacity per BSC 46 46 46 24 24 24 24 24 24 24 24 24 Total unused MMS 22 19 38 9 13 10 13 21 21 21 22 21 T O T A L 42 83 124 354 230 MISCELLANIOUS 5 9 2 5 3 5 4 2 2 2 1 2 19 18 6 10 8 9 7 1 1 1 1 1 22 19 38 9 13 10 13 21 21 21 22 21 0 5 10 15 20 25 30 35 40 45 50 G u jr a t S ia lk o t S a h iw a l R a h im Y a r K h a n S h e ik h u p u r a B a h a w a lp u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g M u z a f f a r
G a r h Used MMS for Aters Used MMS for Sites Total unused MMS MISCELLANIOUS 7% 8% 2% 4% 3% 4% 3% 1% 1% 1% 1% 1% 64% Gujrat Sialkot Sahiwal RahimYar Khan Sheikhupura Bahawalpur Sargodha Kasur Khanewal Okara Jhang Muzaffar Garh Total unused MMS BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning LAHORE B S C D e s c o n E d e n B S C _ 2 C h o u b u r j i D e f e n c e K _ b l k L i b e r t y M o d e l _ T o w n M u s l i m _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a T O T A L Busy TRX 257 149 176 178 130 117 178 141 184 156 132 203 255 108 243 2607 Free TRX 88 196 169 167 215 228 167 204 161 189 213 142 90 237 102 2568 TRX Dimensioning_Center LAHORE 257 149 176 178 130 117 178 141 184 156 132 203 255 108 243 88 196 169 167 215 228 167 204 161 189 213 142 90 237 102 0 50 100 150 200 250 300 350 400 D e s c o n E d e n B S C _ 2 C h o u b u r ji D e fe n c e K _ b lk L ib e r ty M o d e l_ T o w n M u s lim _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a Busy TRX Free TRX LAHORE 5% 3% 3% 3% 3% 2% 3% 3% 4% 3% 3% 4% 5% 2% 5% 49% Descon Eden BSC_2 Chouburji Defence K_blk Liberty Model_Town Muslim_Town Regal Samanabad Thokar Uet BSC_1 Shahdara Free TRX BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX Dimensioning_Center FAISALABAD B S C F a i s a l a b a d S a h i l T r e a t T O T A L Busy TRX 121 142 150 413 Free TRX 224 203 195 622 FAISALABAD 121 142 150 224 203 195 0 50 100 150 200 250 300 350 400 F a is a la b a d S a h il T r e a t Busy TRX Free TRX FAISALABAD 12% 14% 14% 60% Faisalabad Sahil Treat Free TRX BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX Dimensioning_Center MULTAN B S C M u l t a n R a s h i d a b a d T O T A L G u j r a n w a l a S h a h e e n a b a d T O T A L Busy TRX 171 149 320 189 106 295 Free TRX 174 196 370 156 239 395 Free TRX GUJRANWALA B S C Busy TRX MULTAN 171 149 174 196 0 50 100 150 200 250 300 350 400 M u lt a n R a s h id a b a d Busy TRX Free TRX MULTAN 25% 22% 53% Multan Rashidabad Free TRX GUJRANWALA 189 106 156 239 0 50 100 150 200 250 300 350 400 G u jr a n w a la S h a h e e n a b a d Busy TRX Free TRX GUJRANWALA 27% 15% 58% Gujranwala Shaheenabad Free TRX BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX Dimensioning_Center MISCELLANIOUS B S C G u j r a t S i a l k o t S a h i w a l R a h i m
Y a r
K h a n S h e i k h u p u r a B a h a w a l p u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g M u z a f f a r
G a r h T O T A L Busy TRX 127 144 45 110 86 103 85 33 12 15 12 12 784 Free TRX 218 201 300 65 89 72 90 142 163 160 163 163 1826 MISCELLANIOUS 127 144 45 110 86 103 85 33 12 15 12 12 218 201 300 65 89 72 90 142 163 160 163 163 0 50 100 150 200 250 300 350 400 G u jr a t S ia lk o t S a h iw a l R a h im
Y a r
K h a n S h e ik h u p u r a B a h a w a lp u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g M u z a f f a r G a r h Busy TRX Free TRX MISCELLANIOUS 4.9% 5.5% 1.7% 4.2% 3.3% 3.9% 3.3% 1.3% 0.5% 0.6% 0.5% 0.5% 70.0% Gujrat Sialkot Sahiwal Rahim Yar Khan Sheikhupura Bahawalpur Sargodha Kasur Khanewal Okara Jhang Muzaffar Garh Free TRX BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) BSC Traffic Capacity LAHORE B S C D e s c o n E d e n B S C _ 2 C h o u b u r j i D e f e n c e K _ b l k L i b e r t y M o d e l _ T o w n M u s l i m _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a T O T A L Erlang Carried 500 325 380 350 410 340 485 340 435 410 410 545 660 300 575 6465 Erlang Capacity 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 Based on the new s/w release GSR6, the maximum Traffic load for each Dual Cage BSC is 2127 Erl At 70% Utilization, will reach to 1400 Erl So that 2nd XCDR is a REQUIRED to reach to this Capacity Based on the actual situation, most of the BSC has ONLY 8 Ater/BSC (one XCDR for each BSC) This Capaicty is considered bacause of XCDR Capacity ONLY that has to be doubled BSC Traffic Capacity_Center Lahore 500 325 380 350 410 340 485 340 435 410 410 545 660 300 575 0 200 400 600 800 1000 1200 D e s c o n E d e n B S C _ 2 C h o u b u r ji D e f e n c e K _ b lk L ib e r t y M o d e l_ T o w n M u s lim _ T o w n R e g a l S a m a n a b a d T h o k a r U e t B S C _ 1 S h a h d a r a Erlang Carried BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) BSC Traffic Capacity BSC Traffic Capacity_Center FAISALABAD B S C F a i s a l a b a d S a h i l T r e a t T O T A L Erlang Carried 365 420 445 1230 Erlang Capacity 1200 1200 1200 Faisalabad 365 420 445 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 F a is a la b a d S a h il T r e a t Erlang Carried BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) BSC Traffic Capacity BSC Traffic Capacity_Center MULTAN B S C M u l t a n R a s h i d a b a d T O T A L G u j r a n w a l a S h a h e e n a b a d T O T A L Erlang Carried 420 375 795 550 380 930 Erlang Capacity 1200 1200 1200 1200 Erlang Capacity GUJRANWALA B S C Erlang Carried Multan 420 375 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 M u lt a n R a s h id a b a d Erlang Carried Gujranwala 550 380 0 200 400 600 800 1000 1200 G u jr a n w a la S h a h e e n a b a d Erlang Carried BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) BSC Traffic Capacity BSC Traffic Capacity_Center MISCELLANIOUS B S C G u j r a t S i a l k o t S a h i w a l R a h i m
Y a r
K h a n S h e i k h u p u r a B a h a w a l p u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g M u z a f f a r
G a r h T O T A L Erlang Carried 385 550 140 325 225 325 225 85 55 70 20 N/A 2405 Erlang Capacity 1200 1200 1200 600 600 600 600 600 600 600 600 N/A Miscellenious 385 550 140 325 225 325 225 85 55 70 20 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 G u jr a t S ia lk o t S a h iw a l R a h im
Y a r
K h a n S h e ik h u p u r a B a h a w a lp u r S a r g o d h a K a s u r K h a n e w a l O k a r a J h a n g Erlang Carried BSS Planning Deployment Center Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning KARACHI MMS DIMENSIONING_South Region MMS Dimensions 8 8 9 10 8 9 9 8 8 8 8 8 8 8 36 31 23 24 25 11 28 22 33 31 20 31 27 13 4 9 16 12 15 28 7 14 7 9 20 9 13 27 0 10 20 30 40 50 60 H a la r S h a d m a n A llia n c e P r e m ie r J a u h a r C h a p p le A n u m S h a h n a z N ip a C r e e k M e t r o v ille H in o A T C N a c o n Ater Sites Free MMS Dimensions 7% 6% 5% 5% 5% 3% 6% 5% 6% 6% 4% 6% 5% 3% 28% Halar Shadman Alliance Premier Jauhar Chapple Anum Shahnaz Nipa Creek Metroville Hino ATC Nacon FREE BSS Planning Deployment South Region Mobilink (An Orascom Telecom Company) MMS Dimenssioning MMS DIMENSIONING_South Region REMOTE Cities MMS Dimensions 9% 10% 20% 61% Quetta Sukkur Hyderabad FREE MMS_Remote Cities_South 7 4 6 11 23 35 32 19 8 0 10 20 30 40 50 60 Quetta Sukkur Hyderabad Remote City M M S
N o . Free MMS Sites_Busy Ater_Busy BSS Planning Deployment South Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning 384 TRX 90% KARACHI TRX DIMENSIONING_South Region TRX Dimensions 305 296 208 165 239 150 166 213 286 271 163 242 210 104 40 49 137 180 106 195 179 132 59 74 182 103 135 241 0 50 100 150 200 250 300 350 400 H a la r S h a d m a n A llia n c e P r e m ie r J a u h a r C h a p p le A n u m S h a h n a z N ip a C r e e k M e tr o v ille H in o A T C N a c o n TRX BUSY TRX FREE TRX Dimensions 7% 6% 4% 3% 5% 3% 3% 4% 6% 6% 3% 5% 4% 2% 39% Halar Shadman Alliance Premier Jauhar Chapple Anum Shahnaz Nipa Creek Metroville Hino ATC Nacon TRX FREE BSS Planning Deployment South Region Mobilink (An Orascom Telecom Company) TRX Dimenssioning TRX DIMENSIONING_South Region REMOTE CITIES TRX Dimenssioning_Remote Cities 86 108 191 259 237 154 0 50 100 150 200 250 300 350 400 Quetta Sukkur Hyderabad Remote Cities T R XTRX_Free TRX_BUSY TRX Dimenssioning 8% 10% 18% 64% Quetta Sukkur Hyderabad Free BSS Planning Deployment South Region Mobilink (An Orascom Telecom Company) BSC Traffic Dimenssioning Based on the new s/w release GSR6, the maximum Traffic load for each Dual Cage BSC is 2127 Erl At 70% Utilization, will reach to 1300 Erl So that 2nd XCDR is a REQUIRED to reach to this Capacity Based on the actual situation, most of the BSC has ONLY 8 Ater/BSC (one XCDR for each BSC) This Capaicty is considered bacause of XCDR Capacity ONLY that has to be doubled KARACHI BSC Traffic Capacity_South Region TRUNK UTILIZATION 73.00 80.22 60.02 61.74 80.46 51.77 47.14 65.81 83.89 70.25 56.14 54.70 74.29 31.62 0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 90.00 H a la r S h a d m a n A llia n c e P r e m ie r J a u h a r C h a p p le A n u m S h a h n a z N ip a C r e e k M e t r o v ille H in o A T C N a c o n %age TRUNK UTILIZATION % BSC ERLANG LOAD 686 751 548 522 733 459 429 596 785 640 525 513 697 297 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 H a la r S h a d m a n A llia n c e P r e m ie r J a u h a r C h a p p le A n u m S h a h n a z N ip a C r e e k M e t r o v ille H in o A T C N a c o n ERLANG LOAD BSS Planning Deployment South Region