180 likes | 292 Views
NOBEL WP5 leader telco May 28, 2004 A. Lord, A. Berntson, H.Haunstein. Workpackage 5 Transmission and Physical Aspects. Herbert Haunstein. Slides from NBG Meeting. NETWORK SCENARIO. AND SOLUTIONS. WP 5 - interaction with other WPs. REQUIREMENTS. Henning. Herbert. FOR MANAG.
E N D
NOBEL WP5 leader telcoMay 28, 2004A. Lord, A. Berntson, H.Haunstein Workpackage 5 Transmission and Physical Aspects Herbert Haunstein
NETWORK SCENARIO AND SOLUTIONS WP 5 - interaction with other WPs REQUIREMENTS Henning Herbert FOR MANAG. AND CONTROL WPG1 WPG2 WP3 WP3 NETWORK MANAGEMENT NETWORK SCENARIO REQUIREMENTS AND MAIN & CONTROL PLANE FOR WP4 Advanced Packet Advanced Packet AND SOLUTIONS BUILDING BLOCKS FOR MULTI - SERVICE NODES Burst Switching Burst Switching Network Management THE NETWORK SOLUTIONS and Control/Protocols WP1 WP6 Architectural aspects Marcello Dominic for end - to - end services Multi - service node ADAPTIVE architectures TRANSMISSION Anders B. / D. INTERFACES WP5 WP2 Transmission and Survivability, traffic engineering, techno - and physical aspects socio - economic studies and evaluations TECHNICAL SOLUTIONS & PHYSICAL CONSTRAINTS TECHNOLOGIES FOR COST - EFFECTIVE REQUIREMENTS & TECHNOLOGIES IMPLEMENTATION OF NETWORK SOLUTIONS FOR COST - EFFECTIVE AND RELATED EVALUATIONS IMPLEMENTATION OF NODES Olivier Bernd SPECIFICATIONS VALIDATION FROM VALIDATION FROM EXPERIMENTAL ACTIVITIES EXPERIMENTAL ACTIVITIES WP7 WP7 Enabling Technologies Enabling Technologies and Components and Components WPG3 NODE PROTOTYPES WP8 WP8 Integrated test bed and Integrated test bed and PROPOSALS FOR TEST - BED related experimental activities related experimental activities CONFIGURATIONS / EXPERIMENTS PROPOSALS FOR TEST - BED CONFIGURATIONS / EXPERIMENTS
WP5 Deliverable D13 – high-level work split • D13: Collection of simulation results • Define typical/critical paths (derived e.g. from network scenarios) • Point-to-point • Dynamic link • (define parameters, limits and measures) • 2. For typical links and paths analyse transmission limitations • Modulation formats (Acreo, Pirelli) • Optical equalisation (Acreo, Alcatel T-Systems, Pirelli) • Electrical equalisation (Acreo, Lucent, Alcatel) • Optical functions, OXC, OADM (Lucent, ICCS) • Power dynamics (Marconi, T-Systems) • Propagation (Pirelli, ICCS, FT) • AP: by end of May • Further specification of point 2 • Input on point #1 top/down (Anders/Ralph), generic ref. model (Alex) • Discussions on critical links (for D13) and reference networks (for D19) run in parallel. • WP4: Requirements on info exchange for physical constraint routing
WP5 Deliverable D19 – bullet items • D19: Get design rules out of D13 results • Reference networks and topology • Operator group (Andrew) • Communication with WP1 • Link topology/configuration? • Design rules • Starting from existing design rules? • Relation margin vs. failure probability • Max transparency, max node count, max distance, channel count etc • ONSR degradation + fixed penalty • Accurate penalty calculation • What are the design rules used for: • Network dimensioning: initial planning, network growth, • Control-plane light-path calculation (execution time important) • Evaluation of design rules
WP5 Deliverable D26 & D28 (plan ahead) D26 Network simulation ready for dynamic transparent optical network (M21) Lead editor: Siemens Develop flexible simulation package, which allows solving optimization at various levels of detail. Experimental verification of building blocks. Identify most critical (and time consuming) blocks. D28 Specifications for network elements and components to support experimental demonstration (M24) Lead editor: Lucent In order to support subsystem and component development for flexible optical networks, simulation results as well as experimental verification are combined to generate a set of key parameters, which can be used for optimization. Based on the simulation capabilities and details of component performance, revised specifications for improved subsystems (building blocks) will be provided.
WP5 meeting – schedule Organize the work towards Deliverable D13/(M12) • Define contributions from partners (now): done in principle • Send suggestions for critical/typical light paths (parameters) to Anders by end of May • Reference links derived from topology: Anders/Ralph • Generic reference model: Alex/Herbert • Agree on parameter range for simulations & metrics for comparisonQ / OSNR / Eye opening, June 18th • More details on TOC for D13 (working assumptions) by end of June • Discuss results and define further work mid of September • Final results by begin of November • First draft (D13) mid of November
WP leader meeting, Berlin, 17.5.04 Antonio: Introduction Reports from WPs • AM: WP1- Work on deliverable D6: define list of requirements for networks. • JL: WP2 list of questions to WP1, WP3, WP4?- Need internal report to align wording and activities- cheaper conference calls ? Check for appropriate tools. - Analyse Opex structure for backbone networks.- Del.12 should be fine, Prepare TOC for next D15, D17??? • GE: D4 preparation difficult. Collection of 100 pages available. Need input from Dominic. Escalation needed ? Contributions to the dictionary. WP interworking (e.g. on OBS from WP5)Request for a summary of the NOBEL vision, e.g. based on D6, dictionary, carrier group. AM: activities on new layer 2 functions, hybrid approaches. • MJ: D2 done: only through conference calls. Collected a set of requirements for management and control plane, for information exchange a document server required ! • HH: Finished deliverable D3 - with a f-2-f meeting in Nuremberg, did not send it around for review like WP4. Is this the procedure in future. It has become a summary on the state of the art expertise in this work package. The approach will be bottom-up w.r.t to defining worst case light paths. D13 will be a collection of simulations of various aspects. D19 will then draw conclusions on the networking capabilities that can be supported. Established contacts into other WPs by contact persons. • SH: D8 req. for optical I/Fs . What is the essence of this del. Best effort (pure IP), OBS node, Ethernet over SDH node. What distinguishes the core from the metro node ? • AI: Summary slides from Marc. NOC papers, started activities with partners, requests input from other work packages (4,5,6). • RM: Started work on del. Evolution of existing European testbeds to build a NOBEL testbed . Work on preparation of the second phase of NOBEL 4th call !! Nobel dictionary: Comprehensive document, can be used for training. Web site www.ist-nobel.org maintained by UPC, document server File server is ready. Does it also e-mail server. Proposal from Jesus Wiki ? Formal improvement for publication out of the NOBEL consortium ! – Shall be handled pragmatically.
WP1/2/4 meeting, Berlin, 18./19.5.04 Interaction WP4 - WP5 (Herbert) Current assumption in WP4: All control plane & management information comes out of the electronic domain Transparent light paths are not considered in last chapter of D2: During discussion brought up following items & related actions - Performance and QoS monitoring. WP4 provides requirements on these topics and poses them to WP5 and WP6 - Fault localization & fault management Still not clear, what info is needed at the CP from the TP. WP5 defines state-of-the-art on optical PM. WP4 provides requirements for fault localization as well.
WP1/2/4 meeting, Berlin, 18./19.5.04 Interaction WP1-WP5 Protection & restoration schemes discussed with WP1 Need to align with Dominic Schupke (will be back in office next week) Can Anders contribute here as well ?
Notes from WP5 lead editor telco • What are we doing to co-ordinate the D13 activities ? • Proposals for definition of reference networks by Alex, Alfons, Albert • transparency is needed for D19, it will drive to formulate questions to the D13 simulation activities • D13 has to support WP6, WP7 with requirements for future improvement of subsystems and components • Suggest to build a ‘matrix’ consisting of columns indicating the network scenario (Metro, LH, ULH, can also include different flavors) and the rows contain the functional descriptions like modulation formats, optical function, propagation, etc.) • Need to identify gaps, in order to support a full network optimization within D19
Notes from WP5 lead telco • Discussion to get agreement on the Berlin meeting outcome • Antonio’s summary for the WP1/2/4 meeting indicates 3 different time scales • WP5 will address more the medium/long term time scales, which includes transparency & flexibility in the optical domain • Concerns: • Since all work is driven by simulation, we need to be aware of the uncertainty of the results and conclusions thereof. • Therefore let us be very open in the discussion of concerns and pose questions to every contribution. • We need to cross check results between different groups as well as against literature. • Next steps: • Provide input for the D13 simulation collection
Domain B Domain A Domain C WP5 - Optically transparent WDM link • Objectives: • - (Static) optical transport • Circuit switching (add/drop) protection, restorationDefine ‚light paths‘ rulesfor network configuration • (equipment placement) • and re-routing Transport interface Receiver Electrical Domain Domain B Domain B Domain A Domain A Domain C Domain C Optical Domain Transport interface Transmitter Questions: - Network requirements Distances, fiber base, connectivity, number of wavelengths - Optical performance monitoring ? - Optical burst switching ?
WP5 – excerpt from D3 • Network structures: • - Generic • Specific (provided by carriers real network infrastructure) • Static for now ! • Can become dynamic • In second step.