1. N Group0/1: Yangfei WANG z3471101 Amrita Manayil z3479501 Thangappan Madavan V K z5012717 Peng Fu z3452815 Shuo Sun z3486412 Total Slides :19 In-Operation Network Planning

2. Traditional statical transport networks deal with limited network traffic. Statical networks can’t meet the uncertain network traffics surge. In-operation planning methods help to reconfigure networks automatically to meet uncertain network demands. Deals with Fault, Configuration, Accounting& Performance Managements. (FCAPS) Abstract

3. Traditional Network planning is a offline process Current transport and IP/MPLS layers are static and inflexible High Operational Expenditures (OPEX) Capacity over provisioning increases capital expenditures (CAPEX) Traditional Network Planning

4. Auto fashioned real time reconfiguration and reoptimization possible with light provisioning support Minimizes over provisioning and so reduces CAPEX In-Operation Network planning

5. Implementing In-Operation Planning Generalize MPLS Control planes for real time system recovery Add functional block between service and network layers North bound Interface - Entry point for planned configuration and Multiple Service Provision South bound Interface - Provisioning, Monitoring & Info retrieval

6. Traditional network planning In-operation network planning Traditional VS In-operation Planning

7. ABNO Controller - Network entrance point for NMS/OSS - Service layer entrance point for provisioning & Network coordination - Forward requests to PCE PCE - Serve path computation requests - PCE communication protocol (PCEP) carry path computation requests and PCE responses - Uses Border Gateway Protocol Link state (BGP-LS) to gather network topology and current network resources details ABNO Architecture

8. Process requests based on TE or Label switch path database (LSP - DB) Virtual Network Topology Manager (VNTM) co- ordinates virtual network topology The operations, administration & maintenance handler (OAM) responsible for for fault detection and correction. ABNO Architecture

9. Case I: Virtual Topology Reconfiguration Virtual topology reconfiguration after a failure disaster recovery Virtual topology reconfiguration includes management functional areas as follows:  Fault management  Configuration management  Accounting management  Performance management Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication

10. A multilayer network consisting of four OXCs in the optical layer and three routers in the IP layer. After Failure -Fast reroute -State update -Virtual topology reconfiguration Virtual Topology Reconfiguration Disaster Recovery Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication

11. Request from the NMS/OSS ABNO controller(1) PCE(2) Back-end PCE(3) Active solver(4) (PCRep) message (5) NO CHANGE New (virtual) layout Final approval(7) ABNO controller (6) New optimized layout (8) VNTM(9) provisioning manager (10)

13. A new lightpath is created between R1 and R2, and as a result R2-R3 can be rerouted. Virtual Topology Reconfiguration Disaster Recovery Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication

14. Virtual Topology Reconfiguration Disaster Recovery Steps involved: 1.Immediate action by the network to recover some of the traffic 2.Dissemination of the new network state 3.Root cause analysis to understand what failed and why 4.An operator-assisted planning process to come up with a disaster recovery plan 5.Execution of the plan, possibly in multiple steps 6.Reconvergence of the network after each step and in its final state 7.Reuse the resources for post-disaster priority connections. Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication

15. Routes and spectrum allocation is done considering the state of network resources. Re-routing is done to remove bottlenecks and congestion. Re-Optimization is used to improve network efficiency. Case II Study （ Re-Optimization ）

16. The width of the slot is a function of requested bit rate, FEC and modulation format. Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication

17. Case II Study （ Re-Optimization ） Router A Control Plane Router B PCReq PCE back-end PCE Result of Computation front-end PCE NMS/OSS ABNO Controller 1 2 3 4 5 6 Provisioning Manager 7 Flexi-grid core network PCE: Path Computation Element PCR: Pat Computation Reply ABNO: Application-Based Network Operations

18. References List Never Stand Still Faculty of EngineeringElectrical Engineering and Telecommunication 1.Velasco, L., Castro, A., King, D., Gerstel, O., Casellas, R., & Lopez, V. (2014). In-operation network planning. Communications Magazine, IEEE, 52(1), 52-60. 2. Jajszczyk, A. (2005). Automatically switched optical networks: benefits and requirements. Communications Magazine, IEEE, 43(2), S10-S15. 3. Ash, J., & Farrel, A. (2006). A path computation element (PCE)-based architecture. 4. Gredler, H., Medved, J., Previdi, S., Farrel, A., & Ray, S. (2013). North-bound distribution of link-state and TE information using BGP. ID draft-ietf-idr-lsdistribution-03.