1 / 25

Achieving Seamless IP Optical Network Integration

Achieving Seamless IP Optical Network Integration. OIF Interoperability Update Amy Wang, Avici Systems. Agenda. Traditional optical network architecture OIF history OIF technical working groups OIF protocol implementation agreements and demonstration milestones OFC UNI/NNI demo highlight

luigi
Télécharger la présentation

Achieving Seamless IP Optical Network Integration

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. Achieving Seamless IP Optical Network Integration OIF Interoperability Update Amy Wang, Avici Systems

  2. Agenda • Traditional optical network architecture • OIF history • OIF technical working groups • OIF protocol implementation agreements and demonstration milestones • OFC UNI/NNI demo highlight • Conclusion

  3. Traditional Optical Network Architecture • Manual configuration - inefficient usage of the network resource and slow service turn up time • IP & transport networks managed separately - not cost effective nor efficient for planning or managing changes • Lack of open standards/ interoperability – does not allow carriers to leverage multiple vendors for best of breed solutions As a result, it is evident that carriers require solutions over unified control plane across IP and optical layer

  4. OIF History • Founded in 1998, OIF is an open forum focused on accelerating the deployment of next generation optical interworking networks • OIF provides a venue for equipment manufacturers, users, carriers and service providers to work together to • develop key specifications to ensure the interoperability of optical networks • resolve deployment issues

  5. OIF Technical Working Groups Carrier Working Group Carrier Requirements Carrier Requirements Architecture Interoperability Results and findings Physical Link Layer WG Signaling OAM&P Implementation Agreements Protocol WGs Implementation Agreements Interoperability Results and findings Interoperability Interoperability Results and findings

  6. Protocol Implementation Agreement and Demonstration Milestones • OIF UNI 1.0 • User Network Interface (UNI) 1.0 Signaling Specification • An interim UNI 1.0 public demo held at SuperComm 2001 proofed UNI interworking with over 25 vendors on control plane and data plane • NNI Implementation Agreement for OFC 2003 • Inter domain signaling • Inter domain OSPF/ISIS based routing

  7. OIF UNI/NNI Network Reference Model • UNI (User-Network Interface) - a signaling mechanismbetween clients and transport devices • NNI - communication and signaling method among optical domains in the optical core network (intra carrier, inter domain) UNI NNI NNI Transport domain Transport domain IP routers UNI UNI Transport domain NNI NNI NNI Transport domain Optical Core UNI NNI NNI IP routers UNI Transport domain UNI Transport domain Transport domain IP routers optical Connections IP Connections

  8. UNI/NNI Interoperability Trial Goals • Proof of concept of the OIF (Inter-domain) E-NNI concept • Validate the UNI/NNI interworking solution • Demonstrate maturity of UNI 1.0 Agreements

  9. OIF UNI/NNI Public Demonstration at OFC 2003 Core Domain 4 Core Domain 1 Core Domain 3 Core Domain 6 Core Domain 5 Core Domain 2

  10. UNI/NNI Interoperability Trial Assumptions • Interoperability agreement are based on • User Network Interface (UNI) 1.0 Signaling Specification (IA, OIF2001.125.7) • NNI Implementation Agreement Proposal for OFC 2003 (OIF2002.476) • Connections are established dynamically over • an UNI initiated interface (switched connections) or • an EMS/NMS initiated interface (soft permanent connections) • Explicit routing is provided by the first metro or core node initiating the network connection. • The test network topologies refer to clients and domains. Each domain could represent either an individual TNE (Transport Network Equipment) or a vendor domain containing multiple TNE devices • Testing was focused on control plane only

  11. Multi vendor Interoperability Timeline • 2002 NNI requirement and demo pre planning • Fall, 2002 NNI Implementation Agreement Proposal for OFC 2003; Interoperability team is formed • Jan 14, 03 Vendors Sign up commitment • March 8~16, 03 Interoperability testing and Pre-staging • March 15, 03 Carrier Observer Day • March 25~27, 03 Public Demonstration at OFC, Atlanta

  12. UNH Closed Door Testing

  13. Interoperability Participating Companies • Alcatel (UNI-C, UNI-N, E-NNI, NMS/EMS) • Avici (UNI-C) • Ciena (UNI-N, E-NNI) • Data Connection (UNI-C, UNI-N, E-NNI, NMS/EMS) • Elematics (UNI-N, E-NNI) • Mahi Networks (UNI-N, E-NNI, NMS/EMS) • NEC (UNI-C, UNI-N, E-NNI) • Motorola/Netplane (UNI-C, UNI-N, E-NNI, NMS/EMS) • Nortel (UNI-N, E-NNI) • Sycamore (UNI-N, E-NNI, NMS/EMS) • Tellabs (UNI-N, E-NNI, NMS/EMS) • Tellium (UNI-N, E-NNI, NMS/EMS)

  14. Test Methodology • Round robin approach - random vendor pairings /grouping • create diversity and fairness • maximize partner/interoperability exposure by exhaustive pairing • Testing Steps • Routing establishment among the network devices • Signaling are tested with UNI initiated and EMS/NMS initiated connections • Network build out are based on results from daily test progress

  15. Test Scheduling - Closed Door Event • Extensive test rotations • Partner definitions defined by technical manager • 2~3 hrs per test rotation • Allow vendor to have the opportunity to retest after fixes are provided • Daily technical meetings to provide feedback and address interoperability issues in timely manner • Final two days focused on network stability and robustness specific public demo setup

  16. Interoperability Outcomes (1) • Fixed implementation errors by the demo participants • Reached team consensus on specification clarification / consistent implementation alignment • Documented open issues in the Finding Report (OIF2003.035) for further discussion by OIF technical WGs • Specification clarification • Architectural questions/concerns for both UNI/NNI

  17. Interoperability Outcomes (2)

  18. OFC Demo

  19. Public Demonstration Highlights • OFC 2003 • First time ever in the industry to successfully demonstrate multi vendor UNI/NNI interoperability; demonstrated set up and removal of 15 LSPs across multi-domain network in real time; • Participated by 12 vendors with 15 types of product of real network equipment or simulated nodes • Network topology with 10 network client devices and over 30 simulated network elements in 12 domains • Signaling and routing information exchanges was captured and updated in the real time with display software to reflect dynamic connection establishment • Over 15 press interviews and group demo tours • OIF ribbon cutting ceremony covered at the front page of the OFC Daily • 11 UNI - NNI presentations were made at the OIF theater area • Positive feedbacks received from carrier spectators and general OFC audience

  20. OFC Booth – UNI/NNI Demo Area

  21. OFC Booth – Theater Area Presentations

  22. UNI/NNI Signaling Display

  23. NNI Routing Display

  24. Conclusion • What worked Well • Early planning and weekly technical team calls identifies interop issues ahead of time • Extensive test rotations at UNH closed door testing • Commitment from all interop participants • Next Steps • Accelerate OIF protocol development with discussion on the Interoperability Finding document (oif2003.035) • NNI spec • UNI 1.0 impact

  25. Thank You

More Related