GN3 view on multi-d domain services and its implications on NOC - PowerPoint PPT Presentation

GN3 view on multi-d domain services and its implications on NOC implications on NOC Cs Cs Ann Harding (SWITCH) TF-NOC preparation me eeting Copenhagen, Denmark, 3.5.2010 connect • communicate • collaborate

Agenda Starting point for multi Starting point for multi domain services domain services Delivering Connectivit y Services Supporting Services Supporting Services s Blurring the bounda aries N t Network Management k M t t History Standards-based a pproaches Community-specific y p c needs connect • communicate • collaborate

The same, but different NOCs participating in the p p g GN3 multi-domain environment Di Diversity of it f organization, structure, and roles NOCs cope with similar issues, in very different ways for local scope ways for local scope Lack or partial or custom adoption of Operational Support Systems functions Support Systems functions connect • communicate • collaborate

Starting point GN2/GN3 results so far: Multi-domain services’ definition Multi-domain services definition Manual or semi manual service deliv very Multi-domain toolsets for – Topology modeling – Monitoring the physical/logic al infrastructure – Provisioning – Implementation of specific m multi-domain workflows – Developed as silos with no coher rent requirements from NOCs on operational support pp TF-NOC is an opportunity: To exchange expertise, best-practic ces, methodologies for optimizing internal processes in NOCs processes in NOCs To define standards’ based NOC bu usiness processes and OSS functions for the seamless adoption of multi-domain services connect • communicate • collaborate

Multidomain Services - S upporting Services Services What is a service anyway What is a service anyway y? y? More than infrastructu re Intra & Interdomain boun Intra & Interdomain boun daries of responsibility daries of responsibility My network is part of * *our* service How does this fit with t How does this fit with t the NOC mindset? the NOC mindset? One to many or many to many? The “overhead” of auto Th “ h d” f t omation - is it a myth? ti i it th? connect • communicate • collaborate

Blurring the boundaries Who delivers connectivity ser rvices? 90s answer - NOCs Now - it is complicated S Services being designed i b i d i d Wavelengths Bandwidth on Demand Bandwidth on Demand Monitoring Working together Security teams, AAI, deve elopers, vendors How do we be sure we do no t drop the ball? Research to the rescue! Research to the rescue! connect • communicate • collaborate

Network management evo olution 90’s Device management perspective – Network management meant device control and monitoring SNMP – Simple Network Manageme p g ent management management Protocol 2000’s Network Management means much w wider set of activities set of activities Emphasis on service provisioning an d network management, designing OSS/BSS to ools management software “Old” network management is only on g y ne part p networking networking design d i of the overall activity Multi-domain network services, user- - accessible composable services are subsets of Network Management in t subsets of Network Management in t the the modern sense Operations, planning of services, ma rket outreach, user support processes ca n also be mapped onto standardized NM be mapped onto standardized NM frameworks connect • communicate • collaborate

Network management sta andards GN3 Joint Research Activity 2 (J JRA2) analyzed NM related standards: standards: TeleManagementForum (eTOM, S SID, NGOSS/TNA, TAM, IPSphere) ITU-T (M and Y standards) ETSI-TISPAN (WG 8) IETF/IRTF DMTF MEF, OIF, OGF ITIL Some conclusions: S l i TMF appears to be the most releva ant: eTOM is fully adopted by ITU-T, ETSI TISPAN, SID is being increm mentally adopted by ITU-T – IPSphere covers some multi-domain i issues, but assumes existing OSS/BSS ITU-T NGN architecture can be us ed as a model for a multi-domain Network Management Architecture e by GN3 (GN3 NMA) connect • communicate • collaborate

Network management vie ews Network management is Network management is a very complex activity that a very complex activity that can be seen from differen nt perspectives: Business processes (e.g. p ( g TMF’s eTOM provides the ‘de p facto’ standard for busines ss process description and decomposition) Functional (application) vi F ti l ( li ti ) i ews that describe basic OSS th t d ib b i OSS components Information/Data models u Information/Data models u used in the OSS design and used in the OSS design and implementation Architectural principles (S ervice Oriented Architecture principles) (At least) TMF and ITU-T T are converging in their views i connect • communicate • collaborate

TMF views of Network Management TMF Framework connect • communicate • collaborate

GN3 environment Multi-domain Distinguished transport and servic ce stratum functions Based on ITU-T/TMF recommendat tions OSS functions in both strata of ea OSS functions in both strata of ea ach domain ach domain connect • communicate • collaborate

Multi-domain network ma anagement: the effect on NOC operat the effect on NOC operat ions ions NOCs typically deal with transport stratum with transport stratum functions NOC possible shift of focus: from device configurations/ monitoring to OSS monitoring to OSS operations The network exists to NOC provide services to provide services to users) Sound policy and security scheme it h Automated multi- domain services based domain services based on OSS functions connect • communicate • collaborate

A first step: the GN3 NMA s specification So far a business process view (eTOM Service and Resource processes mapped to the GN3 multi-domain case) Service Stratum: processes for the support of multi-domain services Transport Stratum: network manag ement processes connect • communicate • collaborate

A gradual approach Adopt a standards’ based inform mation/data model TMF SID DMTF CIM TMF SID, DMTF CIM… other? other? Supporting policies, context … Define a common subset of NO C OSS functions Starting from TMF recommendatio ons (TNA), existing OSSs, best practices….other? Engineer NOC OSS functions a g according to the TMF NG-OSS g TNA (SOA principles) Define business processes ado pted by a NOC based on eTOM Organization mapping Organization mapping Process workflows Specification of the OSS functions s involved in each one of business processes processes Define inter-OSS functions need ded by NOCs to support (a) business processes and (b) serv vices, in a multi-domain environment i t connect • communicate • collaborate

Directions GN3 ongoing work Standardized Information/ /Data model – Feedback from GN3 to o TF-NOC Synergies S i Specification of a minimum m set of OSS functions at the Transport Stratum Transport Stratum – So that NOCs participa ating in the multi-domain chain can support a minimum m common set of business processes – A proposed TF-NOC a agenda item in collaboration with GN3 JRA2 with GN3 JRA2 Specification of multi-dom main OSS functions? Others? Others? connect • communicate • collaborate

Contact points For GN3 work on a multi-dom main network management g architecture and OSS function ns: Afrodite Sevasti, <sevasti@ @grnet.gr> Pavle Vuletic, pavle.vuleti c@rcub.bg.ac.rs For GN3 work on multidomain n service design: Ann Harding ann.harding@ A H di h di @ @ @switch.ch it h h Brian Bach Mortensen <b rian@nordu.net> connect • communicate • collaborate