《汽车以太网标准化之间的协调要求.pdf》由会员分享,可在线阅读,更多相关《汽车以太网标准化之间的协调要求.pdf(18页珍藏版)》请在三个皮匠报告上搜索。
1、Japan Automotive Software Platform and ArchitectureJASPAR,General incorporated associationRequirement of Harmonization among Automotive Ethernet StandardizationsJASPAR Next Generation High-Speed Network WG*Takumi Nomura,HondaYoshihiro Ito,Nagoya Institute of TechnologyTakeshi Tajima,AubassKatsuyuki
2、Akizuki,NECHideki Goto,Toyota IEEE SA Ethernet&IP Automotive Technology Day 2023 JASPAR All Rights Reserved.2NISSANTOYOTATSUSHOEstablished in September,2004,led by five board companies.Introduction:About JASPAR 2023 JASPAR All Rights Reserved.3Introduction:Next Generation High-Speed Network Working
3、GroupExecutive BoardAuditorAdministratorBoard MembersSteering CommitteeFunctionalSafetyWorking GroupsAUTOSARStandardizationCyber SecurityPromotion ConnectivityNext Generation High-Speed NetworkCyber Security TechnicOTA TechnicNext Generation High-Speed Network Working Group ActivitiesDefinition of f
4、unctional requirements and use cases for Automotive SDNDelving into TSN technical survey and defining Automotive TSN Profiles,and its verificationDefinition of requirements for Next Generation Automotive Networks which are IEEE standards of Optical/Electric 10Gb/s and Electric 10Mb/sDefinition of Au
5、tomotive hardware requirements for electric Multi-Gig Ethernet and MIPI/ASA SerDes 2023 JASPAR All Rights Reserved.4Introduction:2 Presentations From JASPARNext GenerationTechnology Study TeamHardware Team(Circuit Sub-Team,W/H Sub-Team)Next Generation Technology Study TeamNext Gen.Physical Layer Sub
6、-TeamNext Generation High-Speed NetworkWorking GroupSDN Study&Verification TeamTime SynchronizationStudy&Verification TeamNext Generation Technology Study TeamTSN Sub-TeamOSI REFERENCEMODEL LAYERS7APPLICATION6PRESENTATION5SESSION4TRANSPORT3NETWORK2DATA LINK1PHYSICALTeam Composition of Next Gen.High-
7、Speed Network WGAll layers are covered2 presentations from JASPARWG is composed by 4 teams and 4 sub-teamsAutomotive SDNAutomotive SDN Architecture for enabling SDVEthernet TSNRequirement of Harmonization amongAutomotive Ethernet Standardizations 2023 JASPAR All Rights Reserved.5Contents Background
8、JASPARContribution to IEEE 802.1DG Solution of the Non-Aligned Standards Recommend to AUTOSAR The Ideal of Automotive Profile 2023 JASPAR All Rights Reserved.6Background The Last Techday 2022 in Yokohama(1/2)ItemP802.1DG(D1.4)802.1AS(Standard)AVnuAUTOSARUse of BMCANot usedOptionalYes/Not usedNot use
9、dUse of Announce messageYesYesYes/Not usedNot usedUse of Signaling messageUndefinedYesYesNot usedUse of Pdelay messageYesYesYesMeasurement is optionalSync message format2-Step2-Step(2011)2-Step/1-Step(2020)2-Step2-StepMultiple time domainsYesNo(2011)Yes(2020)NoYes(non-Std.)Use of VLAN and priorityUn
10、definedNot usedNot usedOptional1stanalysis2ndanalysis JASPAR showed differences in functions existing profiles for time synchronization.The problems caused by these differences has also been analyzed.2023 JASPAR All Rights Reserved.7Background The Last Techday 2022 in Yokohama(2/2)1st analysis(BMCA,
11、announce message,signaling message)JASPAR has suggested additional modes(like static configuration)for IEEE P802.1DG to keep compatibility with existing AUTOSAR/AVnu solutions.ItemP802.1DG802.1ASAVnuAUTOSARUse of BMCANot usedOptionalYes/Not usedNot usedUse of Announce messageYesYesYes/Not usedNot us
12、edUse of Signaling messageUndefinedYesYesNot used 2nd analysis(Multiple time domains)JASPAR pointed out differences in frame formats between IEEE 802.1AS and AUTOSAR.ItemP802.1DG/802.1AS(2020)AUTOSARCase study(Assuming AUTOSAR migraded to AS-2020)versionPTP2.12.02.0-2.1Devices cannot distinguish AUT
13、OSAR profile and IEEE 802.1AS-2020 by“versionPTP.”domainNumber0.undefined/0.255(uint8)0.15(uint8)When“MessageCompliance”is TRUE,multiple domains can be operated based on AS-2020.0.15(unit8)-0.255(unit8)When“MessageCompliance”is FALSE,backward compatibility to existing AUTOSAR specifications should b
14、e considered.Is it better to keep 0.15 or change to 0.255?2023 JASPAR All Rights Reserved.8July 2022 “Hop”IEEE 802 Plenary in Montreal From our previous studies,JASPAR was concerned about the gPTP specification differences between IEEE P802.1DG and AUTOSAR.Therefore,JASPAR argued that coexistence sh
15、ould be ensured early on the premise so that both IEEE and AUTOSAR will become widespread.Although our consideration was almost recognized in IEEE P802.1DG,additional contributions were required.2023 JASPAR All Rights Reserved.9Nov.2022 “Step”IEEE 802 Plenary in Bangkok In response to a request in M
16、ontreal,JASPAR presented additional contributions to IEEE P802.1DG regarding the differences in specifications.*The results of the consideration were also introduced at Techday 2022 in Yokohama.JASPAR asked members of IEEE P802.1DG to analyze in detail and cooperate for the resolution of the differe
17、nces.However,JASPARs position of maintaining neutrality with AUTOSAR needed to be understood correctly by IEEE P802.1DG.2023 JASPAR All Rights Reserved.10March 2023“Jump”IEEE 802 Plenary in Atlanta JASPAR presented a revised proposal that does not use Announce Messages in principle since JASPAR thou
18、ght of the need to request to IEEE P802.1DG without any misunderstandings concretely.AUTOSAR significantly influences the automotive industry and is already in widespread use.Therefore,JASPAR had no choice but to propose revisions to the P802.1DG specification,although it is regrettable to IEEE P802
19、.1DG.2023 JASPAR All Rights Reserved.11May 2023 IEEE P802.1DG Draft 2.0P802.1DGThis PAR is valid until 31-Dec-2023.PAR Extension Request Date:PAR Extension Approval Date:Num ber of Previous Extensions Requested:01.Num ber of years that the extension is being requested:22.Why an Extension is Required
20、(include actions to com plete):The progress of IEEE P802.1DG has been delayed by change of Editor.Furthermore,reaching consensus in the automotive industry on the content of the document takes time.The project had multiple Task Group ballots and the draft is undergoing a significant revision to refl
21、ect a reduced scope.Actions to complete include subsequent Task Group balloting to reach technical completeness,followed by Working Group balloting and Standards Association balloting.3.1.What date did you begin w riting the first draft:28 Mar 20193.2.How m any people are actively w orking on the pr
22、oject:203.3.How m any tim es a year does the w orking group m eet?I n person:6Via teleconference:203.4.How m any tim es a year is a draft circulated to the w orking group:13.5.What percentage of the Draft is stable:40%3.6.How m any significant w ork revisions has the Draft been through:34.When w ill
23、/did initial Standards Association Balloting begin:Mar 2025When do you expect to subm it the proposed standard to RevCom:Dec 2025Has this docum ent already been adopted by another source?(if so please identify)NoFor an extension request,the information on the original PAR below is not open to modifi
24、cation.Type of Project:New IEEE Standard Project Request Type:Initiation/NewPAR Request Date:14 Nov 2018PAR Approval Date:08 Feb 2019PAR Expiration Date:31 Dec 2023PAR Status:Active1.1 Project Num ber:P802.1DG1.2 Type of Docum ent:Standard1.3 Life Cycle:Full Use2.1 Project Title:Time-Sensitive Netwo
25、rking Profile for Automotive In-Vehicle Ethernet Communications3.1 Working Group:Higher Layer LAN Protocols Working Group(C/LAN/MAN/802.1 WG)3.1.1 Contact I nform ation for Working Group Chair:Nam e:Glenn ParsonsEm ail Address:3.1.2 Contact I nform ation for Working Group Vice Chair:Nam e:Jessy Rouy
26、erEm ail Address:3.2 Society and Com m ittee:IEEE Computer Society/LAN/MAN Standards Committee(C/LAN/MAN)3.2.1 Contact I nform ation for Standards Com m ittee Chair:Nam e:Paul NikolichEm ail Address:p.nikolichieee.org3.2.2 Contact I nform ation for Standards Com m ittee Vice Chair:Nam e:James GilbEm
27、 ail Address:gilbieee.org3.2.3 Contact I nform ation for Standards Representative:Nam e:James GilbEm ail Address:gilbieee.org4.1 Type of Ballot:IndividualThere was a revolutionary change in the work on Draft 2.0 in IEEE P802.1DG.Time synchronization will be AUTOSAR compliant!?Sufficient time is need
28、ed to reach a consensus with the Automotive industry association.Time synchronization conforms to AUTOSAR.Strengthen cooperation with AUTOSAR and OPEN Alliance.2023 JASPAR All Rights Reserved.12July 2023 “Next Phase”IEEE 802 Plenary in Berlin At the IEEE 802 Plenary in July,discussions on AUTOSAR co
29、mpliance for time synchronization started.To entirely refer to AUTOSAR,JASPAR confirmed that specifications other than the need for Announce Messages,such as VLAN specifications,also comply with AUTOSAR.However,some participants still have deep-rooted concerns about AUTOSAR compliance,and further di
30、scussion and consensus building are necessary.2023 JASPAR All Rights Reserved.13May 2023 Recommend to AUTOSAROriginally speaking,AUTOSAR did wrong.There is no point in saying that AUTOSAR arbitrarily added specifications that IEEE does not have.JASPAR expressed concerns to AUTOSAR at the Last Open C
31、onference.2023 JASPAR All Rights Reserved.14July 2023 Recommend to AUTOSARJASPAR shared the actual situation of P802.1DG with AUTOSAR.JASPAR and P802.1DG dont want to have similar but different two time sync protocols from 802.1AS and AUTOSAR.Referring AUTOSAR_PRS_TimeSyncProtocol by P802.1DG may br
32、eak above bad double-standard situation.So now,what should the AUTOSAR PRS TimeSyncProtocol be in the future?and how?“We need more discussions with more partners.“2023 JASPAR All Rights Reserved.15Future The Ideal of AUTOSAR AUTOSAR R22-11 has a configuration which allows incompatible TLV with 802.1
33、AS2011.That is“MessageCompliance”.JASPAR concerns that AUTOSAR may update their time sync protocol version up to 2.1 with keeping existing incompatibility.https:/standards.ieee.org/wp-content/uploads/import/documents/tutorials/1588_tutorial.pdf JASPAR thinks AUTOSAR may have a unique SdoId when they
34、 update their protocol version up 2.1 in accordance with the SdoId policy defined in IEEE 1588-2019 if AUTOSAR wants to keep incompatibility with 802.1 AS in the future.2023 JASPAR All Rights Reserved.16Future The Ideal of IEEE P802.1DG Automotive ProfileOEMsSuppliersEasy to ReferStandardization cen
35、tered on IEEEReal StandardAutomotive Profile 2023 JASPAR All Rights Reserved.17From Now What We Should DoDeclaration JASPAR will continue to participate and contribute to the standardization of IEEE P802.1DG.We will work on AUTOSAR to be consistent with IEEE.To OEMs and SuppliersPlease participate in the IEEE P802.1DG discussion.JASPAR alone is too heavy a burden.Lets formulate the Ideal Automotive Profile together!2023 JASPAR All Rights Reserved.18Thank you for your kind listening.