-1- Elias Athanasopoulos, ICS-FORTH Software Modeling WP3 Software Modelling WISDOM Simulator Elias Athanasopoulos*, Antonis Krithinakis, George Kopidakis (FORTH) contact: Brussels, June 2008

-2- Elias Athanasopoulos, ICS-FORTH Software Modeling Initial Goals - Develop a modular software platform - Model optical components and examine their behaviour - Simulate constructs based on combinations of different components - Model everything under time constraints - Build a platform for SAPI development

-3- Elias Athanasopoulos, ICS-FORTH Software Modeling Initial Version Main Engine WSimulator() WNetworkFlow() WModule() SAPI

-4- Elias Athanasopoulos, ICS-FORTH Software Modeling Provided Functionality SOAMZI() A: C: B: Y: Optical pattern matching, proposed by Rod Webb (UCC). SOA 1 SOA 2 A B C Bandpass filter C

-5- Elias Athanasopoulos, ICS-FORTH Software Modeling Closer Look

-6- Elias Athanasopoulos, ICS-FORTH Software Modeling Limitations Ability to simulate only the SOA-MZI device Not user-friendly, scripting (Ruby) is needed Not easy expandable for simulation of multiple devices No support for real-traffic

-7- Elias Athanasopoulos, ICS-FORTH Software Modeling Major Action Point from 1st Annual Review Simulate more complex optical circuits

-8- Elias Athanasopoulos, ICS-FORTH Software Modeling Issues What are the fundamental operations of a SOA? Do we need extra components, other than SOAs? Do we need this level of granularity? Is it the SOA or the SOA-MZI more suitable to serve as the fundamental building block? If it is the SOA-MZI, which are the basic low-level operations?

-9- Elias Athanasopoulos, ICS-FORTH Software Modeling New Features Ability to place multiple devices (scalability) User-friendliness More complex circuits (optical CRC) Real-traffic support Ability to simulate scenarios of the final demonstrator

-10- Elias Athanasopoulos, ICS-FORTH Software Modeling Current Look

-11- Elias Athanasopoulos, ICS-FORTH Software Modeling Current Look

-12- Elias Athanasopoulos, ICS-FORTH Software Modeling Further Steps Paper submission to: -HotNets 2008 (deadline: mid July) -INFOCOM 2008 (deadline: mid August) -(Focus in WISDOM simulator’s architecture)

-13- Elias Athanasopoulos, ICS-FORTH Software Modeling 5 Mins of Demo Time

-14- Elias Athanasopoulos, ICS-FORTH Software Modeling Thank you! Elias Athanasopoulos ICS-FORTH

-15- Elias Athanasopoulos, ICS-FORTH Software Modeling Backup Slides

-16- Elias Athanasopoulos, ICS-FORTH Software Modeling Different Perspective Try to simulate more complex optical circuits Try to develop abstract entities, which will serve as fundamental building components Have the ability to build any optical circuit and stress it over time

-17- Elias Athanasopoulos, ICS-FORTH Software Modeling The Proposed Scheme Introduction of the following fundamental components: Network flows Connectors SOAs What we essentially want to do is: Build the SOA-MZI module, by using only the logic of SOAs

-18- Elias Athanasopoulos, ICS-FORTH Software Modeling sim = WSimulator.new() SOA1 = WSOAModule.new(:operation,"SOA1") SOA2 = WSOAModule.new(:operation,"SOA2") A = FlowtoSOAConnector.new(WNetworkFlow.new("SpecificSeqFlow", "1010")) C = FlowtoSOAConnector.new(WNetworkFlow.new(”InitToOneFlow”, nil)) B = FlowtoSOAConnector.new(WNetworkFlow.new("RandomFlow", nil)) OutputConnector = GenericConnector.new(:output) SOA1.setPins(A, C, OutputConnector) SOA2.setPins(C, B, OutputConnector) sim.AttachModule(SOA1) sim.AttachModule(SOA2) sim.Run() SOA-MZI

-19- Elias Athanasopoulos, ICS-FORTH Software Modeling But… We still have no deep knowledge of how SOAs are used to produce complex circuits Essentialy, we know: Digital Gates (AND, OR, etc.)  Digital Circuits But, we don’t know: SOAs  Optical Circutis

-20- Elias Athanasopoulos, ICS-FORTH Software Modeling