Скачать презентацию Mobilink NOC Dept By Faras Rafiq Ex- NOC Скачать презентацию Mobilink NOC Dept By Faras Rafiq Ex- NOC

9d00cbcc9b543fc4756f215d8c5ced11.ppt

  • Количество слайдов: 27

Mobilink NOC Dept. By Faras Rafiq Ex- NOC (NSS) Engineer Mobilink NOC Dept. By Faras Rafiq Ex- NOC (NSS) Engineer

Mobilink NOC Mobilink NOC

Telecom Companies in Pakistan u u u Telecommunication is one largest revenue generating industry Telecom Companies in Pakistan u u u Telecommunication is one largest revenue generating industry in Pakistan. Currently the following companies are operating in Pakistan Mobilink Ufone Warid Telenor World. Call Wateen PTCL China-Tel (Paktel)

Cost Comparison Services Mobile Sim Local Call Rates Local SMS MMS Cost in Australia Cost Comparison Services Mobile Sim Local Call Rates Local SMS MMS Cost in Australia (AUS$) $2 -4 Cost in Pakistan (AUS$) $0. 77 $0. 8/Min $0. 027/Min peak time, $ 0. 077/ HOUR at night $0. 25/SMS For $1. 15 you can get 1000 SMS $0. 5/MMS $0. 04/MMS Mobilink earns AUS $15 Million/day by only voucher recharge, where as Mobilink biggest customer is Post paid

History of Mobilink u u Mobilink is owned by Orascom Telecom (OT) which is History of Mobilink u u Mobilink is owned by Orascom Telecom (OT) which is an Egyptian based company, it also owns Mobi. Nil and Bangla. Link. Mobilink was established in 1999 and it is the largest Telecom Company in Pakistan. 35 Million+ subscribers by March 2008. (compared to 21. 4 Million population of Australiaon 9 Sep 2008 14: 35). 60 MSC’s, 650+ BSC’s and 7000+ Cell sites across Pakistan. How to Manage such a large network !!!!

History of Mobilink NOC u u A centralized OMCR (Radio Network) was established in History of Mobilink NOC u u A centralized OMCR (Radio Network) was established in 2000 in Lahore. Performed Fault and Configuration management for BSC’s and BTS only. During 2006 -2007 Mobilink faced a loss of US$ 60 Million due to Network Down time. In 2007, Mobilink decided to establish a complete NOC for end to end visibility which included Access, Core, TXN, IN and VAS.

Departmental Organization of Mobilink Departmental Organization of Mobilink

TMN Model TMN Model

Network Element The following Network Elements are monitored in Mobilink. Access side: u BSC’s Network Element The following Network Elements are monitored in Mobilink. Access side: u BSC’s (Alcatel, Motorola, Huawei) u BTS u Individual Cell Sites. Core Side: u MSC’s (Siemens, Alcatel, Huawei, Nokia) u HLS (Motrolla). u STP ( Tekelec) IN & Vas side: u IN Platforms (Siemens) u SGSN (Alcatel) u GGSN (Alcatel) u SMSC (Logica) u IVR’s u PRBT’s u USSD TXN side: u Optical Fiber and ATM nodes (Huawei) u

Element Management Following EMS’s are deployed in Mobilink Access Side: u Motorola OMC u Element Management Following EMS’s are deployed in Mobilink Access Side: u Motorola OMC u Alcatel OMC u Huawei OMC Core side: u Siemens SCR u Alcatel NMC u Huawei i. Manager u Net. Boss IN & Vas side u @comms u OMC-PS TXN side u Huawei i. Manager u

Network Management u u EMS provide Fault and Configuration capabilities for their respective NE’s. Network Management u u EMS provide Fault and Configuration capabilities for their respective NE’s. Alarm Types, Commands syntax and terminologies for hardware different for each vendor. Separate Teams and trainings required for each domain of elements. Mobilink opted for a NMS solution called Te. MIP (Telecommunication Management Information Platform) provided by HP. u One platform for all entities, translate all alarm types to standard format, convert generalized commands to individual EMS’s syntax. u A single Team required to handle problems from all types of Network Elements.

Service Management u u NOC engineers use Te. MIP (NMS) to perform Fault and Service Management u u NOC engineers use Te. MIP (NMS) to perform Fault and Configuration Management to provide services to the subscriber. Special software used to analyze the performance of individual NE’s and give their feed back to operations and planning departments. Create Weekly, Monthly downtime and response time reports for higher management to analyze and devise strategies for future expansions and improvements. That’s the reason NOC is given the name Eyes and Heart of a Network !!!

Business Management u u Managers and Specialists are responsible for proper functionality of NOC Business Management u u Managers and Specialists are responsible for proper functionality of NOC department. Analyze reports and identify areas of improvement and devise strategies to reduce network downtime. Take up issues with Operations and Planning department These are the people who decide investing on Capex (US$80 Million Te. MIP project) to reduce Opex.

Te. MIP NMS u u u u u In terms on FCAPS Te. MIP Te. MIP NMS u u u u u In terms on FCAPS Te. MIP provides F, C, P, S. Te. MIP provides the following functionality to NOC Engineer. Automatic Trouble Ticket creation. Tap Filter (Block unwanted alarms). Corrective Filter (User friendly format). Correlations (Handle complex scenarios). Transient Filters (Avoid Fluctuations). Outage Management (Planned Activity). Routine checks.

Te. MIP NMS u “ an engineer opined to the author that network management Te. MIP NMS u “ an engineer opined to the author that network management is best described as all aspects of devising and operating networks that no one knows how to automate” D. Comer. u On average 280, 000 alarms are received a day. These alarms are handled by 50 NOC engineers u Most of the alarms are fluctuations or straight forward and can be easily automated. u u Automated systems cannot match human decision making. For example Fiber break, Outage due to Power issues. A single 16 STM Fiber break will generate nearly 77, 500 alarms alone. The process can be automated but infeasible in terms of time, computational and resource cost.

Network Management Protocols SNMP (UDP Based) u Q 3 (TCP Based) u CORBA (TCP Network Management Protocols SNMP (UDP Based) u Q 3 (TCP Based) u CORBA (TCP Based) u

Architecture of Te. MIP Architecture of Te. MIP

OVSD Trouble Ticketing System OVSD Trouble Ticketing System

OVSD Trouble Ticketing System u u u All Trouble Tickets created are stored in OVSD Trouble Ticketing System u u u All Trouble Tickets created are stored in an oracle database. These trouble tickets are notified to the relevant persons by automatic E-mail or SMS. The on-site engineer accepts the T. T via e-mail or sms which indicates that the problem is under investigation. Any change in the status of the T. T is notified and once the issue is resolved the on-site engineer inform the reason via e-mail or sms and the T. T is closed. This T. T system is given the name OVSD.

Configuration Management u u u Te. MIP has the functionality to provide Configuration Management Configuration Management u u u Te. MIP has the functionality to provide Configuration Management without worrying about the underlying Network Element. Provides a standard GUI form with mandatory fields highlighted for particular tasks. Once a command is executed, it is converted into the syntax understood by the respective EMS.

Performance Management Performance Management

Performance Management u u Te. MIP provides statistical displays of T. T created for Performance Management u u Te. MIP provides statistical displays of T. T created for each type of problems in a day. It provides easy extractable Excel file for creating reports. It provides MAP’s to readily identify problems in the network All these features are used by Management (Managers, HOD’s, Directors, CTO) to determine in one look how a network is performing.

Alarm Text of SNMP Alarm u N 1_L 3 MTP: Signalling link failed (stopped), Alarm Text of SNMP Alarm u N 1_L 3 MTP: Signalling link failed (stopped), LINK=STK 1 BL 16, A ti. Inc. Trap. Cleared trap was received from 10. 14. 2. 30 at 274693740. DESCRIPTION: Trap issued by the INC to an OS with a severity value of 'cleared'. The objects contained in the variable binding list are scalar objects ( with index 0 ). VARIABLES: ti. Alarm. Date. Time=20080801182933+0600, ti. Alarm. Reporting. Object={ 1 3 6 1 4 1 231 7 99 4 1000 0 }, ti. Alarm. Faulty. Object={ 1 3 6 1 4 1 231 7 99 47 1000 99 9 1 1 8 78 49 95 76 51 77 84 80 }, ti. Alarm. Event. Type. Id=communications. Alarm, ti. Alarm. Severity=cleared, ti. Alarm. Error. ID=1179650, ti. Alarm. End. Key=true, ti. Alarm. Description=N 1_L 3 MTP: Signalling link failed(stopped), LINK=STK 1 BL 16, ti. Alarm. Sequence. Number=47066365, ti. Alarm. Source. Name=in 9 ce 1 -core 2, 1. 3. 6. 1. 4. 1. 231. 7 iso. org. dod. internet. private. enterprises. sni. siemens. Units

Countries where Te. MIP is used for Network Management France u Singapore u Peru Countries where Te. MIP is used for Network Management France u Singapore u Peru u Canada u Taiwan u China u UK u

References Mobilink NMS Ph 2 Functional Specifications v 1. 0 -S u http: //www. References Mobilink NMS Ph 2 Functional Specifications v 1. 0 -S u http: //www. mobilinkgsm. com u Price comparison figures taken from optus brochure u http: //www. abs. gov. au/ausstats/abs @. nsf/94713 ad 445 ff 1425 ca 2568200 0192 af 2/1647509 ef 7 e 25 faaca 2568 a 9 00154 b 63? opendocument u

THANK YOU for your time ANY Questions !!!!!!! THANK YOU for your time ANY Questions !!!!!!!