Control Plane modeling for ASTN: guidelines and experimental activities

1. Control Plane modeling for ASTN: guidelines and experimental activities NOBEL WP4 Meeting – Dec 1st, 2004

2. Outline Objective: • Information Modeling (IM) definition related to Control Plane (CP) operation: CP_T & CP_C • Rigorous modeling and easy scalability CP operation relevant aspects: • State of the control plane network elements • Routing and signaling information • Switched connectivity establishment (SPC and SC) Reference standard: • ITU-T G.805: Generic functional architecture of transport networks • ITU-T M.3100: Generic Network Information Model • ITU-T G.8080: Architecture for the Automatic Switched Optical Network (ASON) Steps: • Study of internal functional blocks for a generic CP network element (CPE) • Layering according to switching capability of transport network element • Definition of IM fragment related to CP operation • Testbed implementation for IM validation

3. Layering & Partitioning Concepts - G.805 Specific Layer Network Client Server Specific Layer Network Client Server Specific Layer Network = subnetwork Layering view (Client/Server Association) Partitioning concept (applied to a signle layer network) Layer network Sublayer Sublayer Sublayer Layer network that is recursively partitioned subnetworks

4. Subnetwork point (SNP) - G.8080 CP = Connection Point TCP = Termination Connection Point SNC = Sub Network Connection SNP = Sub Network Point SNPP = Sub Network Point Pool CTP = Connection Termination Point TTP = Trail Termination Point TTP (M.3100) TTP (M.3100) TTP (M.3100) TTP (M.3100) TCP (G.805) TCP (G.805) TCP (G.805) TCP (G.805) Subnetwork Subnetwork SNP SNP SNP SNP SNP Link Connection SNP Link Connection SNC SNC SNC SNC Link Connection Link Connection CP (G.805) CP (G.805) CP (G.805) CP (G.805) CTP (M.3100) CTP (M.3100) CTP (M.3100) CTP (M.3100) Trail Trail

5. CP layering according to switching capability CPE CPE CPE Control Plane Modeling Transport Plane Modeling CPE Layer n+3 Layer m+1 Layer n+2 Layer n+1 Layer m Layer n CPE CPE CCI NNI CPE CPE

6. CPE layer-n functional components Client UNI UNI protocol Controller Call Controller UNI Port Connection Controller (CC) Routing Controller (RC) RDB NNI Port Link Resource Manager (LRM) LRM DB CPE NNI Protocol Controller NNI Termination & Adaptation Performer (TAP) Discovery Agent (DA) CPE CCI NE from G.8080 in black from SOON (our proposal) in blue

7. Reference interfaces: Inter-NNI Intra-NNI UNI CPE Layer n+1 CPE Layer n+1 Intra NNI E-NNI Inter NNI CPE Layer n CPE Layer n Intra NNI Inter NNI CPE Layer n-1 CPE Layer n-1 Intra NNI Domain A CPE CPE

8. Work in progress Extend the scope of the M.3100 Generic Information Model M.3100 IM fragments: • Network fragment • Managed element fragment • Termination Point fragment • Transmission fragment • Cross connection fragment • Functional Area fragment • M.3100 extension to Termination Point fragment related to SNP objects relevant for control information management • M.3100 additional fragments in order to take into account the switched connection set-up, routing and signaling processing

9. The CP modeling experiment activity • Verification of the ITU-T G.8080 Control Plane Element modeling. • Valuation of the scalability of the CP multilayer modeling by comparing the results obtained with a transport plane equivalent simulation based on a CP single layer approach. • Development of a NE independent CCI communication protocol able, at the same time, to support the layer specific constrains. • Study of the client-server network interaction via UNI for the creation and maintenance of switched connections. • Study of the Control Plane INTRA and INTER layers communication via NNI for supporting the routing and signalling processing.

10. The SOON Simulated Testbed In order to achieve the presented goals we need a testbed composed by: • a transport network with at least 2 layers provided with switching capability and more than 3 nodes per layer • a control plane compliant with the ITU-T G.8080 Recommendation • a set of data traffic generator device and a set of data traffic analyser Solution: Utilize a discrete-event network simulation tool that permits to easily implement the CP and provided with a large network element library for achieve a realistic implementation of a complex transport planes. Tool adopted: J-Sim* (www.j-sim.org)a Java-based freeware discrete-event simulator based on the Autonomous Component Architecture (ACA) *project partially supported by: NSF Next Generation Software program, DARPA/IPTO network modeling and simulation program, MURI/AFOSR, Cisco Systems, Inc., Ohio State University, and University of Illinois at Urbana-Champaign.

11. Tesbed Data CCI UNI NNI Bidirectional Connection Unidirectional Connection Screen shot taken by J-Sim Editor

12. Testbed CPE internal structure Screen shot taken by J-Sim Editor

13. Experimental activities work in progress • Determine a complete CCI, UNI and NNI message sets for achieving a layer independent CPE architecture. • Increase the number of network nodes and the number of layers in the simulated testbed for verifying the scalability of the CP modeling proposed. • Introduce the SOON Service Plane in the testbed. • Create an hybrid testbed able to combine the simulated CP with real network device.

14. Thank You!

15. The SOON project SP activities: • Dedicated functional blocks definition • IN concept application • Separation of the Service Provider from Network Provider • Standard interface development Customer CSI Service Plane X UNI SO-ASTN Management Plane Control Plane • CPModeling: • Vision of the TP through CP • Functional layering • Reference Point definition • CP network element modeling • Functional blocks definition • CCI standardization • UNI - NNI development NMI-A ASTN NMI-T CCI • MP Modeling: • IM extension for CP management • NMI-A standartization Transport Plane • Testbed: • Pisa Metro/Core DWDM Ring • Acreo Stockholm testbed • J-Sim based Simulated testbed