關于基于AUTOSAR的軟件定義汽車的管理技術NETCONF和YANG的架構思考.pdf

《關于基于AUTOSAR的軟件定義汽車的管理技術NETCONF和YANG的架構思考.pdf》由會員分享，可在線閱讀，更多相關《關于基于AUTOSAR的軟件定義汽車的管理技術NETCONF和YANG的架構思考.pdf（24頁珍藏版）》請在三個皮匠報告上搜索。

1、Architectural thoughts about management technologies NETCONF and YANG for AUTOSAR-based Software-defined VehiclesAUTOSAR AUTomotive Open System ARchitecture www.autosar.org IETF Internet Engineering Task ForceNETCONF a)Network Configuration Protocol b)IETF Working Group Network ConfigurationYANG Yet

2、-Another-Next-Generation =name of a management data modeling language 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2821.SDVs-under-DevOps

3、management of SDVs in operation dynamic management services?2.Model-based in-vehicle computing AUTOSAR software systems modeling framework for Model-based Systems Engineering(MBSE)AUTOSAR higher level management system3.Requirements viewpoint system context,actors,goals management architecture patte

4、rn manager-agent management technologies(NETCONF,YANG)4.Operational viewpoint management use cases5.Functional viewpoint service layering,information planes extended data model for AUTOSAR6.Logical viewpoint vision of a logical AUTOSAR management architecture7.Technical viewpoint out of scope(no dis

5、cussion of technical AUTOSAR system and soft-ware architectural aspects,would be subject of a follow-up presentation)8.SummaryWhats next?StorylineWalkthroughAUTOSAR AUTomotive Open System ARchitecture(www.autosar.org)DevOps Lifecycle model Development/OperationsMBSE Model-based Systems EngineeringNE

6、TCONF a)Network Configuration Protocol b)IETF Working Group Network ConfigurationSDV Software-defined VehicleYANG Yet-Another-Next-Generation =name of a management data modeling language 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as

7、well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28AUTOSAR SDV-under-DevOps in Operations and Management3AUTOSAR AUTomotive Open System ARchitecture DevOps Lifecycle model Development/OperationsSDV Software-defined Vehicle 2023 ETAS GmbH.All rights reserv

8、ed,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-284Software-defined AUTOSAR Vehicle computing systemDevOps lifecycle(6)typical,DevOps-lifecycle-phase-specificmanagement serv

9、icesAUTOSAR AUTomotive Open System ARchitectureDevOps Lifecycle model Development/OperationsFW/SW Firmware,SoftwareSDV Software-defined Vehicle(2)complementary management system(3)DevOps-lifecycle 8(here ETAS)(4)unfolded DevOps-lifecycle phases(6.1)during Devs(=static management)(6.2)during Ops(=dyn

10、amic management)(5)main actorsdynamic?(1)SDV in-vehicle information system 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-28initial Devsclos

11、e to zerolowmediumhighFrequency of management activitiesDevOps lifecycle phase over timeSDVSoftware-definedVehicleOps IDevs IIOps IIDevs IIIOps IIIPost-SoPPre-SoPHWVHard-wiredVehicleclose to zerolowmediumhighFrequency of management activitiesStart-of-Production(SoP)related lifecycle phase over time5

12、Time-dependent frequency of management activities over vehicle lifecycle phasesDynamic management?For SDVs?HWV Hard-wired Vehicle IoT Internet of ThingsMO Managed Object SDV Software-defined VehiclefM(t)Frequency of overall management activitiesfC(t)Frequency of lifecycle-related management operatio

13、nsfS(t)Frequency of management information retrieval¬ificationManagement activities fM(t)Categories:I)Managed object life-cycle operations fC(t)II)Managed object information retrieval¬ifications fS(t)Purpose:1.create object2.delete object3.modify or update object4.subscribe to notificationsby

14、manager1.retrieve(or read)information from agent by manager2.notify information to manager by agentbesides basic3.discovery and inventory ofactual capabilities and featuresManage-ment data:configuration data state data configuration data state data Temporality of dynamic management services(=managem

15、ent service rate).Also dependent whether managed object=1.unconstrained object or2.constrained object(like safety constrained).SDV x-axis:temporality with respect to1.addition of new features2.deletion of existing features3.hardening of continued features(in order to increase maturity level)(just th

16、ink about smart IoT devices)Static!Frequency of in-operation management services close to zero.fM(t)fC(t)fS(t)Example management activity:fC,Sec(t)Frequency of security management operations(e.g.,policy management security policy management update of security policy rules)fC,Sec(t)NOTE:sum,not shown

17、.NOTE:sum,=,+,not shown.2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Model-based Systems Engineering(MBSE)of Model-based in-Vehicle Comp

18、uting AUTOSAR Software systemsMatrix of Modeling Framework6 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-287Location of AUTOSAR system eng

19、ineering artefactsOverview Matrix Viewpoints vs Abstraction levelsAbstracted as E/E Reference ArchitectureOut of scope.ARXML AUTOSAR XML E/E Electrical&Electronic(in-vehicle architecture)XML Extensible Markup LanguageYANG Data modeling language Yet-Another-Next-GenerationGood news!That system archit

20、ecture(levels)are(almost)independent of AUTOSAR!Thus,applicable for all kind of distributedautomotive computing systems Engineering framework:Engineering methodology:=MBSE(Model-based Systems Engineering)MBSE modeling framework:=SPES(Software Platform Embedded Systems)see Model-Based Engineering of

21、Embedded Systems:The SPES 2020 Methodology,Springer,2014.System modeling languages:=SysML,UML Data modeling languages:=YANG,ARXMLthe usual AUTOSARprogram code abstraction levelDevOps anchoring 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distributi

22、on,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Requirements Viewpoint(I)for an SDV-under-DevOps capable AUTOSAR management architecture8AUTOSAR AUTomotive Open System ARchitecture DevOps Lifecycle model Development/OperationsSDV Software-defined

23、 Vehicle 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-289Basic ICT patternSystem context(standard management)(I.1)Requirements viewpointLe

24、gacy AUTOSAR system(as in-vehicle,distributed computingand communication system)Addition:Agent=resources,objects,entities technical components HW,SW resources physical,virtual;logicalAPI Programming Interface for user ApplicationsMPI Programming Interface for Management applicationsQoS Quality of Se

25、rviceICT Information&Communication TechnologiesAddition:Manager(vehicle locally or/and remotely operated)Addition:Management Programming Interface(MPI)Management architecture pattern take-aways:1.information planes:explicit separation between user and management plane!2.representation of management

26、information:explicit management data model!3.management actors and roles:management agents:and management manager!4.results in management plane interfaces:MPIs!5.manager-agent(s)communication:management protocol!2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction

27、,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2810Vehicle local,heterogeneous,distributed computing system with management plane System context(operations)(I.2)Requirements viewpointManagement ProgrammingInterfaces(MPI)MPIexter

28、nal=MPIManager-Gateway|AgentMPIinternal=MPIGateway-Agentrealtwin=datastoreat agent levelvirtualtwin=datastore at manager levelDigital twinTakeaway:digital twin=embedded,integral element ofmanagement architecture pattern!AP(AUTOSAR)Adaptive PlatformCP(AUTOSAR)Classical PlatformMPI Management Programm

29、ing Interface 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2811One-Manager-ToolSystem context(all DevOps)AP(AUTOSAR)Adaptive PlatformCP(AU

30、TOSAR)Classical PlatformMPI Management Programming Interface for planingOne manager,used for build for operation 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.Extern

31、al|ETAS-DAP|2023-07-2812Developers,operators,managers,as humans or/and machinesActors (I.4)Requirements viewpointLevel ofautomationVehicle driving controlVehicle managementL5fully automatedL4L3L2L1L0fully manualNOTE 1 The degree of automation in the vehicle control and management domains arebasicall

32、y orthogonal,are mutually inndependent.NOTE 2 References are e.g.,TM Forum Autonomous Networks Reference Architecture(2021),ETSI Zero-touch network and Service Management(2019).NOTE 3 Terminology:Assistance translates in Automation support.And Automation should not be confused with Autonomy(which wo

33、uld imply that humans grant machineactors intelligent independence beyond the human assigned constraints;autonomyrelates to a concept of freedom).DevelopersManagers/OperatorsLong-term goal maximal automation of vehiclemanagement already to be considered in system architecture from day#1!AI Artificia

34、l IntelligenceETSI European Telecommunications Standards Institute 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-28Paradigm-and technology-

35、driven architectural goals(non-exhaustive)Top goals&non-goals (I.5.1)Requirements viewpointThe above YANG goal may be generalizedto other non-ARXML data(like COVESAVSS application data model).AUTOSAR process extended byfrontend non-ARXML-to-ARXMLinformation converter.Management protocols:1.NETCONF i

36、s an established,mature,native protocol forprofessional management of distributed systems.2.RESTCONF=NETCONF variant for web-based management.3.CORECONF=NETCONF variant for constrained devices.all automotive use cases could be fully covered!AVB(IEEE)Audio Video BroadcastingCORECONF CoAP Management I

37、nterface (NETCONF-oriented Constrained Application ProtocolCOVESA Connected Vehicle Systems AllianceICT Information&Communication TechnologiesNETCONF a)Network Configuration Protocol b)IETF Working Group Network ConfigurationRESTCONF Representional State Transfer(REST)/HTTP variant of NETCONFTSN(IEE

38、E)Time-Sensitive NetworkingVSS Vehicle Signal Specification(by COVESA)13 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2814SDV-driven,in-se

39、rvice,dynamic management goals(examples,non-exhaustive)Goals&non-goals (I.5.2)Requirements viewpointLegacy AUTOSAR quadrant:pre-operation(static)managementManagement goals(some examples)for in-operation(dynamic)managementECU Electronic Control Unit=vehicle computerSDV Software-defined VehicleSoA Ser

40、vice-oriented ArchitectureV2X Vehicle-to-Everything(communication)2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Operational Viewpoint(II)

41、for an SDV-under-DevOps capable AUTOSAR management architecture15AUTOSAR AUTomotive Open System ARchitecture DevOps Lifecycle model Development/OperationsSDV Software-defined Vehicle 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well

42、 as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2817example use cases(non-exhaustive)DevOps-related management use cases (II.2)Operational viewpointQoS Quality of Service 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproductio

43、n,editing,distribution,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Functional viewpoint(III)Functional service layering versus technical AUTOSAR software layering Functional management architecture for vehicle local and/or remote management19 20

44、23 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2821over the distributed vehicle computing&communication system,incl.management planeService la

45、yering (III.1)Functional viewpoint1.Introduction and support of standard ICTcommunication technologies Internet Protocol(IETF)and Ethernet(IEEE)in AUTOSAR,in relation to their native ICT management information representation by(IETF,IEEE)YANG data models.2.Automotive TSN and the relation between IEE

46、E TSNYANG data models and AUTOSAR ARXML data models.3.Existing in-vehicle fully distributed management architectures(AUTOSAR)and the possible direction in centralizing specific management services,particular in IEEE 802.1 TSN and IEEE 1722 AVB communication context.IEEE/IETF YANG-based ARXML data mo

47、delsAUTOSAR-based ARXML data modelsAP-Manager:distributed in legacy AUTOSAR more centralization in future?MP-Manager:centralized!non-functional require-ments(NFR)?Availability?QoS?Security?NFRsSafety?vertical neighbour layers in service provider/service consumer relationshipsARXML AUTOSAR XMLAVB(IEE

48、E)Audio Video BroadcastingIEEE Institute of Electrical and Electronics EngineersIETF Internet Engineering Task ForceTSN(IEEE)Time-Sensitive Networking 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications

49、 for industrial property rights.External|ETAS-DAP|2023-07-2822YANG-to-ARXML integrationAUTOSAR system development process (III.2)Functional viewpointLegacy AUTOSAR1.system development process=unchanged!2.mature tool chain=unchanged!no revolution of process and development tools!no revolution of AUTO

50、SAR system architecture!similar for application data models,e.g.,COVESA VSS AUTOSAR extended:AUTOSAR concept Vehicle API mapping VSS-to-ARXMLAUTOSAR extended:standardized,open YANG data modelsAPI Application Programming InterfaceARXML AUTOSAR XMLAUTOSAR AUTomotive Open System ARchitectureCOVESA Conn

51、ected Vehicle Systems AllianceECU Electronic Control Unit(=vehicle computer)ETSI European Telecommunications Standards InstituteIEEE Institute of Electrical and Electronics EngineersIETF Internet Engineering Task ForceVSS Vehicle Signal Specification(by COVESA)XML Extensible Markup LanguageYANG Yet-

52、Another-Next-Generation =name of a management data modeling languageNOTE-The notion of AR-XML and YANG-XML intends to underline the common syntactical language baseline.2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the eve

53、nt of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Logical viewpoint(IV)Functional management architecture for vehicle local and/or remote management23 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as

54、in the event of applications for industrial property rights.External|ETAS-DAP|2023-07-2825Hybrid centralized/distributed management managersLogical AUTOSAR management architecture (IV.2)Logical viewpointCNC(IEEE)Centralized Network Configuration(Manager)=(centralized or distributed)Manager COM&RESCU

55、C(IEEE)Centralized User Configuration(Manager)=(centralized or distributed)Manager APPManager-Agent interfaces(MPI):management data transfer over a management protocolManagers:might be realized technically in a centralized or distributed manner(dependent on your logical-to-technical deployment model

56、)each manager is responsible for his service layer related objects manager APP and COM&RES are termed as User and Network managers in IEEE(e.g.,802.1,60802 and CUC/CNC forcentralized deployment variant)long-term goal:merged,single and centralized manager(in smallarea networks like in-vehicle distrib

57、uted computing systems)Agents:the two logical agents may be technically realized by a single one(even if thereare multiple managers)example shows two for the discussion of the combination of a centralizedmanager COM&RES and a distributed manager APPe.g.,as a first evolution path step from a fully di

58、stributed manager(like in legacyAUTOSAR).E.g.,IEEE 60802 follows a similar evolution strategy(for manager and agents)Take-aways:a single,common logical managementarchitecture may serve many technicaldeployment variants logical user and management plane architecture allows to discuss e.g.,dynamic est

59、ablishment/release of end-to-end communication services(like TSN streams inclusive entire QoS and resource management)Reminder!Exemplification indicates only a few example,important model elements(in order not to overload the illustration).2023 ETAS GmbH.All rights reserved,also regarding any dispos

60、al,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28SummaryWhats next?26 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the ev

61、ent of applications for industrial property rights.External|ETAS-DAP|2023-07-2827Model-based operation and management of SDVs=Model-based Systems Engineering!SummaryFrankly speaken,you might re-place AUTOSAR by any generalin-vehicle computing systems,whether for their operation or eventhe developmen

62、t.Model-based engineering:Model-based AUTOSAR softwareengineering impliesModel-based system engineering first(due to system-embedded software)Modeling languages:system&software:SysML,UMLinformation&data:YANG,ARXML,Conclusions:overlay managementarchitecture engineeredcandidate entry point(s)forYANG d

63、ata models identifiedcandidate managementprotocol NETCONF integrationvia manager-agent patternNext steps:follow the MBSEdevelopment path 2023 ETAS GmbH.All rights reserved,also regarding any disposal,exploitation,reproduction,editing,distribution,as well as in the event of applications for industrial property rights.Internal|ETAS-DAP|2023-07-28Thank you!Dr.Wolfgang Hauck(ETAS SDV.DAP,Reference Architecture)Dr.Albrecht Schwarz(ETAS SDV.DAP,Reference Architecture)2023 IEEE SA Ethernet&IP Automotive Technology Day(E&IPATD)