1 / 19

Group0/1: Yangfei WANG z3471101

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

blaze-burris
Download Presentation

Group0/1: Yangfei WANG z3471101

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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. 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 Implementing In-Operation Planning

  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 includesmanagement functional areas as follows: • Fault management • Configuration management • Accounting management • Performance management after a failure Virtual topology reconfiguration disaster recovery

  10. Virtual Topology Reconfiguration Disaster Recovery 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

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

  12. Virtual Topology Reconfiguration Disaster Recovery A new lightpath is created between R1 and R2, and as a result R2-R3 can be rerouted .

  13. Virtual Topology Reconfiguration Disaster Recovery • Steps involved: • Immediate action by the network to recover some of the traffic • Dissemination of the new network state • Root cause analysis to understand what failed and why • An operator-assisted planning process to come up with a disaster • recovery plan • Execution of the plan, possibly in multiple steps • Reconvergence of the network after each step and in its final state • Reuse the resources for post-disaster priority connections.

  14. 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）

  15. Case II Study（Re-Optimization） The width of the slot is a function of requested bit rate, FEC and modulation format.

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

  17. 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. References List

  18. Thank you !

More Related