 which a network trouble gets handled. The below list shows some sample scenarios on network trouble handling: Customer raises an issue that needs to be handled in the network: When the customer has an issue with a subscribed service; he/she contacts a customer care number to report the problem. The customer care representative tries to resolve the service problem based on available data. In case the service prob- lem cannot be resolved using the operations of the executive, then a trouble ticket is raised to track and resolve the issue. The ticket is then forwarded to the appropriate team (service operators, network operators, application devel- opers, etc.) for analysis and resolution. Service team identifies a trouble condition: When certain parameters like the quality of service deteriorates, the service team isolates the issue and asks the network operations team to resolve the issue or forward the request to the appropriate team in clearing the trouble condition. A ticket may be raised to track the issue. Network monitoring/maintenance professional raises a ticket: During the network monitoring operation, the network professional might encounter a trouble log that could require manual intervention from the site where the equipment is deployed to fix. The monitoring professional can raise a trouble ticket and assign the same to the concerned network operator for resolution of trouble. Alternatively, the network monitoring professional could issues commands to the network elements or take necessary action to resolve the issue when the trouble condition is easy to resolve and does not require par- ticipation from other teams. NMS takes necessary action for a trouble condition: It is possible to program the NMS to take a predefined action when a specific event log is received generated for a network trouble condition. The action taken by the NMS NMS Functions could be to fix the problem by issuing necessary commands to the network elements or to generate a trouble ticket and forward it to the concerned net- wor