ETSIZSMworkonClosed- LoopAutomation

IETF106,Singapore,November2019ANIMAWG

LaurentCiavaglia

ETSIZSMISG• ZeroTouchNetworkandServiceManagement• CreatedDec.2017,renewedfor2-yearstermà Dec.2021• Objectives:

– Defineanend-to-endautomatednetworkandservicemanagementarchitecture– Supportbothlegacyandvirtualizednetworkinfrastructures– Collaboratewithrelevantopen-sourceprojects,standardizationbodiesandfora– Createafoundationfordiverseopensourcegroupstoproduceinteroperablesolutions

• Links:– ZSMTechnologyPage:http://www.etsi.org/zsm– ZSMWiki:https://zsmwiki.etsi.org/– ZSMOpenArea(Draftspecs):http://docbox.etsi.org/ISG/ZSM/Open– ZSMPortal(members’workingarea):http://portal.etsi.org/zsm

IETF106- ANIMA 2

ZSMframeworkreferencearchitectureZSMserviceakamanagementservice:Asetofofferedmanagementcapabilities.

Managementfunction: Logicalentityplayingtherolesofserviceconsumerand/orserviceproducer.

Integrationfabric:Amanagementfunction,playingtherolesofbothserviceconsumerandserviceproducer,thatenablesinteroperationandcommunicationbetweenmanagementfunctionswithinandacrossmanagementdomains.

Cross-domaindataservices:Servicesthatallowtosharedatawithauthorizedconsumersacrossdomains.

Managementdomain: Ascopeofmanagementdelineatedbyatechnological,business,administrativeorotherboundary.

E2Eservicemanagementdomain: AmanagementdomainspecializedtomanageE2Eservices.

(Source:ETSIGSZSM002)

ZSMarchitecture feature:Separationofconcerns inmanagement

ManagementDomain(akaNetworkManagementDomain)

• Scopeofmanagementdelineatedbye.g.technologicalororganizationalboundaries

• Managesresourcesandservicesbasedonthese

• Providesmanagementservicesanddecouplestheinnerdomaindetailsfromtheoutsideworld

• Canconsumemanagementservicesfromothermanage-mentdomains

E2EServiceManagementDomain

• ManagesE2Eservicesthatspanmultiplemanagementdomains

• Providesandconsumesmanagementservices

• Coordinatesbetweenmanagementdomains

ProvidedManagementServices

ProvidedManagementServices

ZSMarchitecture feature:Service-based

(Source:ETSIGSZSM002)

Domaindata collection• Eventnotification services• Performancemeasurements streaming service• Performancemeasurements collection service• Logcollection serviceDomainanalytics• Analyticsservices• Domaincondition detection service• Dataoptimization servicesDomainintelligence• AImodelmanagementservice• DeployedAImodelassessmentservice• AItrainingdatamanagementservice• Knowledgebaseservice• HealthissuereportingserviceDomainorchestration• Domainorchestration service• Feasibility checkservice• Managed services catalogue management service• Testingservice• Domaininventory information service• Domaininventory management service• Domaintopology information serviceDomaincontrol• Resource configuration management service• Resource lifecycle management services• Configuration data generation service

E2Eservicedata collection• E2Eperformance data reporting serviceE2Eserviceanalytics• Analyticsservices• E2Eservicequality management service• E2Eservicecondition detection serviceE2Eserviceintelligence• AImodel management service• Deployed AImodel assessment service• AItraining data management service• E2Eservicehealth issue reporting serviceE2Eserviceorchestration• E2Eserviceorchestration service• Feasibility checkservice• Managed services catalogue management service• E2Etesting service• E2Eservices inventory information service• E2Eservices inventory management service• E2Eservices topology information service

Dataservices• Datastore management service• Datapersistence services• Dataprocessing service

Integrationfabric services• Managementservices registration service• Managementservices discovery service• Managementcommunication service• Managementserviceinvocation routing service• Managementcapability exposure configuration

service

TheZSMarchitecture defines management services which canbe provided andconsumed by management functions.

(Therealization ofmanagement functions is outofscope.)

Theintegration fabric allows management services (MS)tointeroperateandcommunicate.

• MScommunicationà synchronous &asynchronous,e.g.event notifications andstreaming data

• MSregistration anddiscovery

• MSinvocation,including support forservicemeshes (direct invocation alsopossible)

• MSexposure management andaccess control

ZSMarchitecture feature:Integrationfabric

ZSMarchitecture feature:Enabling automation based onclosed loopsObserve

• Datacollectionservicesmonitorthemanagedentities(resourcesandservices),andprovideliveperformanceandfaultdatatosupportclosed-loopautomation.

Orient

• Analyticsservices providespecificinsightsbasedondatacollectedbydatacollectionservicesandonotherdata/knowledge.

Decide

• Intelligenceservices providespecificdecisionsandrecommendations,todriveclosed-loopautomation.

Act

• Orchestrationservices automateworkflowsandprocessestohandleinstantiationandlifecyclemanagementofthemanagedservices.

• Controlservices individuallysteerthestateofeachmanagedentity(resource,service).

ETSIGSZSM002

• Thespecification waspublished by ETSIinAugust2019andis publicly available here:https://www.etsi.org/deliver/etsi_gs/ZSM/001_099/002/01.01.01_60/gs_zsm002v010101p.pdf

V1.1.1(2019-08)

ETSI GS ZSM 002Zero-touch Network and Service Management (ZSM);Reference Architecture

3newWIsonClosed-LoopAutomationadoptedinJune2019ZSM009-1Closed-loopautomation:Enablers;Rapporteur:Ericsson

• Thisworkitemdescribeshowtoenableclosed-loopautomationbasedontheZSMarchitecturalframework.TheworkitemspecifieshowtoautomaticallydeployandconfigureclosedloopsinvolvingboththeE2Eservicemanagementdomainandthemanagementdomains.Closedloopsrunningwithinthemanagedentitiesareout-of-scope.Thespecificationwillinclude(i)meansforcoordination,delegation,escalation,etc.betweenclosedloops,(ii)theuseofpolicies,rules,intentsand/orotherformsofinputstosteertheirbehaviour,and(iii)interactionsbetweenclosedloopsandexternalentities.Thedeliverablewillspecifystage-2genericenablersandflexibleproceduresforclosed-loopautomation.

ZSM009-2Closed-loopautomation:Solution;Rapporteur:Huawei• ThisworkitemdescribesspecificationforsolutionsofparticularE2Eserviceandnetworkautomationusecases,based

primarilyonthegenericenablersandarchitecturalelementsforclosedloopsdefinedinZSM002,ZSM009-1.ThesolutionwillspecifyhowtheE2EmanagementloopinteractswithZSMconsumerswithspecificsfortheselectedusecases.TheWIwillmakerecommendationsonthepreferredoptionifmultiplesolutionsareavailable.

ZSM009-3Closed-loopautomation:Advancedtopics;Rapporteur:Nokia• Thisstudyinvestigatesadvancedtopicsrelatedtoclosed-loopoperationssuchaslearningandcognitivecapabilities

(e.g.basedondifferentdegreesofuseandintegrationofartificialintelligencetechnologies),waystosetandevaluatelevelsofoversight,autonomy,andoperationalconfidenceonthebehaviour oftheclosedloops.Thestudywilldocumentproblemstatementsandtechnicalchallenges,derivepotentialrequirements,captureandevaluatepotentialsolutionoptions,andproviderecommendationsforfurtherstandardizationactivities.

Completionbymid2020(target).

IETF106- ANIMA

ZSMcurrentactivitiesonClosedLoopAutomation

Overall:Twomaindrivers/areasofwork:• Multi-vendorclosedloopdesign• Closedloopsspanningmultipledomains

ZSM009-1• Requirementsrefinementforstage-2specificationoftheclosedloopenablers• Designandmodelingofclosedloopscomponentsbasedondisaggregatedview,asynchronousoperationsandenabling

multipleinputsandoutputsbetweentheclosedloopstages/functions.• Derivingthekeychallengesforinteroperabilityandcomposition,e.g.managebyescalation/delegation/coordination,

data-,event- andintent-driven,relationshipschemes(peer,hierarchical),etc.

ZSM009-2• ScenariosillustratingthenatureofexchangesbetweenCLstages,forusecasessuchasprovisioningofnewresources,

instantiationofback-upresources,dynamicmonitoringadaptation

ZSM009-3• InvestigatescaleofCLcapabilities(levelsofautomation)andintegrationofAItechnologiesinclosedloops

IETF106- ANIMA

“Black-box”closedloop(BB-CL)• AnabstractedviewoftheCL.TheCLisseenasone“integrated”element.• AimatfocusingtheCLmanagementtoits“external”behaviorvia“outer”interfaces.• Inputinterfaceconveys:

– Governanceinformationsuchasgoal(s),operatingconditionsandscope(escalation,boundaries,managedentities,datasources…)andlifecyclemanagement

– Coordinationinformationsuchascoordinationmessages(e.g.inform,recommend,enforce)– Knowledgeinformatione.g.fromotherCLs,otherentities

• Outputinterfaceconveys:– Governanceinformationsuchascapabilities,constraintsandrequirements,actionand

statusreports– Knowledgediscovered,produced– Actionse.g.onmanagedentities,forcoordinationpurpose,forescalation

• CL-Manager:– AlogicalfunctionresponsibleformanagingtheCLexternalinteractions– PurposeinthediagramistooutlinetheneedforsuchafunctioninadditiontotheotherCL

functions/steps• Remarks:

– Operatormaynotbeable,ormaynotneed,ormaynotwanttoknowabouttheCLinternals;andbeonlyinterestedintheoutcomeoftheCL(remainintheutilityenvelope).

– Granularityofcontrol?On/off,step-wise?à ataskfortheCLlifecycledesign/specification– Granularityofconfiguration?Utility-based,parameterstuningfordifferentsteps?à cf.

intent-/outcome-drivenaspect;andataskforthegovernancedesign/specification

Input Output

“CL-Agent”

11

“White-box”closedloop(WB-CL)• An(less)abstractedviewoftheCLwithvisibilityontheCLsteps.• AimatfocusingontheCLinternalbehaviorsmanagementvia“inner”interfaces.• SameexternalinterfacesasBB-CL.• Newfunctionstosupport:

– NeedtoprovideabilitytocomposeandadaptthestepsoftheCL

– NeedStepscapabilitydescriptionandpair-wisecharacteristicinformation

Input Output

“CL-Agent”

12

Informationanalysis

Decisionselection

Actionimplementation

Informationacquisition

K

(*)

(*):linksb/wCL-Managerandotherfunctionsnotshownforclarity

ZSMCLsandANIMAASAs

• Roughly,ZSMclosedloops==ANIMAautonomicserviceagents• ZSMwilldevelopspecificationsforclosed-loopautomation• CouldbeofinteresttoANIMAandwidercommunityon

– Enablers:genericcomponents,interactionspatterns,composition– Solutions:usecasesapplyingenablersandstandardsbasedcomponents– Advancedtopics:nextgenerationclosedloopdesignandoperationsandpotentialareasforfuturestandardization

IETF106- ANIMA 13