518:
organization, administration and control of the AUTOSAR development partnership. Within this core, the executive board defines the overall strategy and roadmap. The
Steering Committee manages day-to-day non-technical operations and admission of partners, public relations and contractual issues. The chairman and Deputy of chairman, appointed for one year, represent the Steering Committee for that purpose. The AUTOSAR Spokesperson takes over the communication with the outside world.
538:
277:"Commercial off the Shelf" software and hardware components across product lines, promoting software reuse. By accelerating development and maintenance processes, AUTOSAR intends to improve the management of product and process complexity and risk, while optimizing the costs associated with scalable systems. Based on this principle, AUTOSAR aims to prepare for upcoming technologies.
29:
385:
interfaces of the application software must be mapped to these ports. The VFB handles communication within the individual ECU and between ECUs. From an application point of view, no detailed knowledge of lower-level technologies or dependencies is required. This supports hardware-independent development and usage of application software.
417:
Further, Car-2-X applications require interaction to vehicles and off-board systems. That means that the system has to provide secure on-board communication, support of cross-domain computing platforms, smartphone integration, integration of non-AUTOSAR systems, and so on. Also, cloud-based services
272:
The motivation behind AUTOSAR is to manage the increasing complexity of software and E/E systems as their functional scope expands. The initiative is designed to support flexibility in product modifications, upgrades, and updates, while leveraging scalable solutions within and across product lines.
409:
New use-cases required the development of the adaptive platform. One example is automated driving, in the context of which the driver temporarily and/or partially transfers responsibility for driving to the vehicle. This can require communication with traffic infrastructure (e.g. traffic signs and
400:
Standardization of functional interfaces across manufacturers and suppliers and standardization of the interfaces between the different software layers is seen as a basis for achieving the technical goals of AUTOSAR. Only by standardizing concrete interface contents in their physical and temporal
384:
One essential concept of the
Classic Platform is the Virtual Functional Bus (VFB). This virtual bus is an abstract set of RTEs that are not yet deployed to specific ECUs and decouples the applications from the infrastructure. It communicates via dedicated ports, which means that the communication
276:
The goals of AUTOSAR include addressing future vehicle requirements such as availability, safety, software upgrades, updates, and maintainability. AUTOSAR seeks to enhance scalability and flexibility for function integration and transfer. Additionally, the initiative aims to increase the use of
261:
AUTOSAR provides specifications for basic software modules, defines application interfaces, and builds a common development methodology based on a standardized exchange format. The basic software modules made available by the AUTOSAR layered software architecture can be used in vehicles from
517:
Core
Partners include the founding partners Bavarian Motor Works (BMW), Robert Bosch AG, Continental AG, Mercedes-Benz Group AG, Ford Motor Company, General Motors Holding LLC, Peugeot Citroën Automobiles S.A., Toyota Motor Corporation, and Volkswagen AG. These companies are responsible for
524:
Premium and
Development members contribute to work packages coordinated and monitored by the Project Leader Team established by the Core Partners. Associate partners are making use of the standard documents AUTOSAR has already released. Attendees are currently participating with Academic
207:
Since 2003, AUTOSAR has provided four major versions of the standardized automotive software architecture for its
Classic Platform and one release, along with the version of acceptance tests. The work on the AUTOSAR Classic Platform can be divided into three phases:
485:
The adaptive platform contains both specification and code. In comparison to the
Classic Platform, AUTOSAR develops an implementation to shorten the validation cycle and illustrate the underlying concepts. This implementation is available to all AUTOSAR partners.
323:
The purpose of the foundation standard is to enforce interoperability between the AUTOSAR platforms. The foundation contains common requirements and technical specifications (for example protocols) shared between the AUTOSAR platforms, and the common methodology.
235:
In 2016, work began on the
Adaptive Platform. An initial release (17-03) was published in early 2017, followed by release 17–10 in October 2017 and release 18–03 in March 2018. With release 18–10 in October 2018, the major development activities were published.
339:
ECU Configuration
Description: contains all basic software configuration information that is local to a specific ECU. Use this information to build the executable software, the code of the basic software modules and the code of the software components out of
252:
AUTOSAR aims to establish a global standard for software and methodology, enabling open E/E system architectures for future intelligent mobility. This vision focuses on ensuring high levels of dependability, particularly in terms of safety and security.
421:
To support dynamic deployment of customer applications and to provide an environment for applications that require high-end computing power AUTOSAR is currently standardizing the AUTOSAR Adaptive
Platform. Its core is an operating system based on the
418:
will require dedicated means for security, such as secure cloud interaction and emergency vehicle preemption. They will enable remote and distributed services, such as remote diagnostics, over the air (OTA) update, repair, and exchange handling.
145:
to different vehicle and platform variants, transferability of software, consideration of availability and safety requirements, cooperation between different partners, sustainable use of natural resources and maintainability during the
364:) and basic software (BSW). The application software layer is mostly hardware independent. Communication between software components and access to BSW happens via RTE, which represents the full interface for applications.
996:
231:
In 2013, the AUTOSAR consortium introduced a continuous working mode for the
Classic Platform to maintain the standard and provide selected improvements (including releases R4.2, and 1.0 of acceptance tests).
521:
Premium Partner Plus companies support the project leader team in the various technical, organizational and everyday processes. They also give new strategic inputs to the project leader round.
410:-lights), cloud servers (e.g. to access the latest traffic information or map data), or the use of microprocessors and high-performance computing hardware for parallel processing, e.g.,
1100:
665:
AUTOSAR takes part in various events every year. Furthermore the AUTOSAR Open Conference (AOC) is planned every year to network and give an overview over the newest achievements.
273:
Enhancing scalability and flexibility in the integration and transfer of functions is a key objective, aiming to improve the quality and reliability of software and E/E systems.
1530:
204:
also joined as a Core Partner. After Siemens VDO was acquired by Continental in February 2008, Siemens VDO is no longer independently represented as a Core Partner of AUTOSAR.
1074:
1459:
130:
manufacturers, suppliers and other companies from the electronics, semiconductor and software industries. Its purpose is to develop and establish an open and standardized
1126:
430:(namely PSE51). One of the key features of the Adaptive Platform is service-oriented communication since the Platform is based on the Service - Oriented Architecture.
966:
465:
Functional clusters in AUTOSAR Adaptive Platform have to have at least one instance per (virtual) machine while services may be distributed in the in-car network.
336:
ECU extract: contains the information from the System Configuration Description needed for a specific ECU (e.g. those signals where a specific ECU has access to).
388:
The Classic Platform also enables the integration of non-AUTOSAR systems such as GENIVI, now renamed COVESA, by using the Franca Interface Definition Language (
851:
333:
System Configuration Description includes all system information and the information agreed between different ECUs (e.g. definition of bus signals).
1222:
705:
1780:
883:
1438:
1754:
1660:
1104:
1634:
1810:
1537:
1707:
1078:
381:
Services are divided further, into functional groups representing the infrastructure for system, memory and communication services.
1022:
445:(APIs). The platform consists of functional clusters which are grouped in services and the AUTOSAR adaptive platform foundation.
695:
1318:
1130:
494:
AUTOSAR defined six different levels of membership. The contribution of partners varies depending on the type of partnership:
1960:
1946:
1927:
1501:
1389:
1269:
1198:
293:(mostly) with no explicit automotive job, but offers services needed to run the functional part of the upper software layer.
545:
974:
1733:
2012:
442:
311:
information exchange between the application software components and between the Basic Software and the applications.
1888:
185:
to develop and establish an open industry standard for the automotive electrical-electronic (E/E) architecture.
2017:
304:
262:
different manufacturers and electronic components from different suppliers, thereby reducing expenditures for
919:
858:
2002:
434:
221:(2007–2009): Expansion of the standard in terms of architecture and methodology (releases 3.0, 3.1, 4.0)
2007:
1374:
2016 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks Workshop (DSN-W)
1226:
426:
standard. The operating system can be used from the application via a subset of the POSIX according to
1788:
894:
427:
680:(A software process assessment framework required by or relating to some specifications of AUTOSAR)
623:
Vendors which provide related tools and software, e.g. for testing, diagnostics, development, etc.
411:
263:
1481:
1758:
683:
308:
135:
1664:
1609:
648:
314:
Application Layer: application software components that interact with the runtime environment.
1638:
437:
language. The communication protocol used for the in-vehicle networking is SOME/IP, based on
131:
1818:
461:
Do not constrain the final SW design of the architecture implementing the Adaptive Platform.
1344:
1711:
8:
361:
296:
290:
1955:
Staron, Miroslaw (2021). Automotive Software Architectures - An Introduction. Springer.
1026:
1507:
1413:
1395:
1275:
1204:
189:
1293:
1956:
1942:
1923:
1511:
1497:
1385:
1265:
1208:
1194:
1057:
830:
699:
612:
607:
592:
163:
147:
1279:
1686:
1489:
1399:
1377:
1322:
1257:
1190:
1186:
822:
791:
692:(Functional safety norm, required by or relating to some specifications of AUTOSAR)
677:
1562:
1177:
Stepanovic, Mia; Bjelica, Milan; Kastelan, Ivan; Velikic, Gordana (January 2020).
349:
The AUTOSAR classic platform is the standard for embedded real-time ECUs based on
1179:"Scalable approach to extending automotive software using AUTOSAR adaptive stack"
601:
586:
549:
357:
1493:
1460:"AUTOSAR proofs to be THE automotive software platform for intelligent mobility"
1152:
1369:
1249:
1178:
810:
733:
576:
458:
Describe behavior of software platform from application and network perspective
201:
167:
1370:"AUTOSAR for Connected and Autonomous Vehicles: The AUTOSAR Adaptive Platform"
1261:
826:
1996:
1587:
1061:
834:
215:(2004–2006): Fundamental development of the standard (releases 1.0, 2.0, 2.1)
178:
668:
A list of the events which are planned can be found on the AUTOSAR website.
269:
Based on this principle, AUTOSAR aims to prepare for upcoming technologies.
356:
The architecture distinguishes between three software layers that run on a
227:(2010–2013): Maintenance and selected improvements (releases 3.2, 4.1, 4.2)
1841:
1381:
940:
627:
142:
1248:
Chaaban, Khaled; Leserf, Patrick; Saudrais, Sebastien (September 2009).
568:
Selection of vendors, including RTOS, BSW, design tools, compiler, etc.
1982:
572:
389:
300:
193:
182:
171:
127:
1866:
1254:
2009 IEEE Conference on Emerging Technologies & Factory Automation
792:"Achievements and exploitation of the AUTOSAR development partnership"
401:
representation allows achieving the needed integration compatibility.
689:
636:
1482:"Progress on the AUTOSAR Adaptive Platform for Intelligent Vehicles"
126:
chitecture) is a global development partnership founded in 2003 by
1939:
Software Development with AUTOSAR (Softwareentwicklung mit AUTOSAR)
438:
1488:. Proceedings (in German). Wiesbaden: Springer Fachmedien: 67–75.
1183:
2020 IEEE International Conference on Consumer Electronics (ICCE)
597:
175:
1176:
773:
618:
433:
Adaptive AUTOSAR is developed and written using C++ which is an
1480:
Reichart, Günter; Asmus, Rinat (2021). Bertram, Torsten (ed.).
632:
367:
The BSW is divided in three major layers and complex drivers:
197:
1048:"AUTOSAR: The worldwide automotive standard for e/e systems",
811:"AUTOSAR — The Worldwide Automotive Standard for E/E Systems"
653:
COMASSO Organization provides an open source AUTOSAR platform
423:
1250:"Steer-By-Wire system development using AUTOSAR methodology"
1975:
789:
Fennel, H.; Helmut, S.; Bielefeld, J.; et al. (2006).
754:
710:
582:
350:
28:
239:
In December 2023, AUTOSAR R23-11 was virtually released.
159:
778:. Bruchsal: CreateSpace Independent Publishing Platform.
1986:
441:. Two types of interfaces are available: services and
395:
96:
1247:
1056:, Springer Fachmedien Wiesbaden: 9–10, October 2013,
788:
192:
joined as a Core Partner. In the following December
642:
852:"AUTOSAR: Shaping the future of a Global Standard"
790:
775:AUTOSAR Compendium - Part 1: Application & RTE
256:
1920:AUTOSAR Compendium: Part 1: Application & RTE
1994:
1363:
1361:
1936:
698:(Tools for ARXML/MBSE modelling, such as IBM's
455:Define clustering of requirements specification
1479:
1358:
619:AUTOSAR-related software vendors and partners
280:
200:followed. In November of the following year,
1376:. Toulouse, France: IEEE. pp. 215–217.
1367:
79:Carmine De Iesu (Project Lead Speaker, 2024)
1368:Furst, Simon; Bechter, Markus (June 2016).
525:collaboration and non-commercial projects.
452:Assemble functions of the adaptive platform
1185:. Las Vegas, NV, USA: IEEE. pp. 1–2.
353:. Its main deliverable is specifications.
27:
1734:"AUTOSAR Chairman handover Press Release"
374:Electronic control unit (ECU) abstraction
285:AUTOSAR uses a three-layer architecture:
77:Thomas Rüping (Deputy Chairperson, 2024)
1525:
1523:
1521:
47:Automotive, E/E, Software, Semiconductor
1937:Kindel, Olaf; Friedrich, Mario (2009).
1839:
964:
846:
844:
1995:
1917:
771:
728:
726:
696:List of requirements engineering tools
1518:
884:"Adaptive Platform_Release_17_10_EN"
841:
532:
468:Adaptive platform services include:
404:
360:: application, runtime environment (
242:
158:AUTOSAR was formed in July 2003 by
723:
472:Update and Configuration management
396:Standardized application interfaces
344:
16:Automotive development organization
13:
1911:
1840:cooperation, AUTOSAR development.
1439:"AUTOSAR for Intelligent Vehicles"
965:cooperation, AUTOSAR development.
893:. 20 December 2017. Archived from
660:
443:application programming interfaces
14:
2029:
1967:
1023:"AUTOSAR: Motivation & Goals"
303:which abstracts from the network
1256:. Mallorca: IEEE. pp. 1–8.
734:"Elektrobit Automotive: AUTOSAR"
643:Competitors or related consortia
536:
194:Peugeot Citroën Automobiles S.A.
63:Munich, Germany (Administration)
1881:
1859:
1833:
1803:
1773:
1747:
1726:
1700:
1679:
1653:
1627:
1602:
1580:
1555:
1473:
1452:
1431:
1406:
1337:
1311:
1286:
1241:
1215:
1170:
1145:
1119:
1093:
1067:
1041:
1015:
989:
958:
489:
257:Motivation and Goals of AUTOSAR
1941:. dpunkt.verlag. p. 300.
1755:"AUTOSAR: Project Leader Team"
1191:10.1109/ICCE46568.2020.9212328
1101:"AUTOSAR: Runtime Environment"
967:"AUTOSAR R20-11 Release Event"
933:
912:
876:
803:
782:
765:
747:
327:
1:
1889:"Generating ARXML and C code"
1661:"AUTOSAR: Steering Committee"
1319:"AUTOSAR: Technical Overview"
716:
318:
289:Basic Software: standardized
1531:"AUTOSAR: Basic Information"
7:
1494:10.1007/978-3-658-34752-9_6
1486:Automatisiertes Fahren 2020
671:
435:object-oriented programming
377:Microcontroller abstraction
10:
2034:
1635:"AUTOSAR: Executive Board"
920:"AUTOSAR_Release_18_03_EN"
755:"AUTOSAR official website"
528:
281:Released AUTOSAR Standards
202:General Motors Holding LLC
160:Bavarian Motor Works (BMW)
153:
1262:10.1109/ETFA.2009.5347123
1075:"AUTOSAR: Basic Software"
827:10.1007/s40111-013-0003-5
821:(9): 5–12. October 2013.
412:graphics processing units
307:for the inter- and intra-
247:
91:
83:
67:
59:
51:
43:
35:
26:
2013:Motor trade associations
1869:(Press release). AUTOSAR
997:"AUTOSAR Release R23-11"
264:research and development
198:Toyota Motor Corporation
136:electronic control units
1918:Scheid, Oliver (2015).
1867:"News & and Events"
1708:"AUTOSAR: Spokesperson"
1345:"Application Interface"
772:Scheid, Oliver (2015).
684:Electronic control unit
87:366 Companies (12/2023)
39:Development Partnership
1687:"Autopresse: Autonews"
1223:"AUTOSAR: Methodology"
649:Automotive Grade Linux
188:In November 2003, the
172:Mercedes-Benz Group AG
2018:Software architecture
1382:10.1109/DSN-W.2016.24
448:Functional clusters:
132:software architecture
1781:"Associate Partners"
1667:on 23 September 2015
550:adding missing items
498:Premium Partner Plus
75:(Chairperson, 2024)
73:Michael Niklas-Höret
2003:Automotive software
1983:AUTOSAR user groups
1821:on 28 November 2020
1791:on 28 November 2020
1761:on 19 December 2015
1743:. 21 November 2017.
1714:on 19 December 2015
1641:on 19 December 2015
1543:on 19 December 2015
1448:. 29 November 2017.
1414:"Adaptive Platform"
1325:on 19 December 2015
1229:on 19 December 2015
1133:on 19 December 2015
1127:"AUTOSAR: Software"
1107:on 19 December 2015
1081:on 19 December 2015
1029:on 19 December 2015
900:on 31 December 2021
864:on 19 December 2015
507:Development Partner
297:Runtime environment
141:The objectives are
23:
1563:"Current Partners"
1469:. 18 October 2017.
1294:"Classic Platform"
1003:. 29 November 2023
815:ATZextra Worldwide
548:; you can help by
478:Network Management
190:Ford Motor Company
21:
2008:Engine technology
1961:978-3-030-65938-7
1948:978-3-89864-563-8
1929:978-1-50275-152-2
1895:. 17 October 2017
1503:978-3-658-34752-9
1391:978-1-5090-3688-2
1271:978-1-4244-2727-7
1200:978-1-7281-5186-1
613:Tata Technologies
608:Vector Informatik
593:KPIT Technologies
566:
565:
504:Associate Partner
405:Adaptive platform
243:Concept and goals
164:Robert Bosch GmbH
148:product lifecycle
105:
104:
2025:
1979:
1978:
1976:Official website
1952:
1933:
1905:
1904:
1902:
1900:
1885:
1879:
1878:
1876:
1874:
1863:
1857:
1856:
1854:
1852:
1837:
1831:
1830:
1828:
1826:
1817:. Archived from
1807:
1801:
1800:
1798:
1796:
1787:. Archived from
1777:
1771:
1770:
1768:
1766:
1757:. Archived from
1751:
1745:
1744:
1738:
1730:
1724:
1723:
1721:
1719:
1710:. Archived from
1704:
1698:
1697:
1695:
1693:
1683:
1677:
1676:
1674:
1672:
1663:. Archived from
1657:
1651:
1650:
1648:
1646:
1637:. Archived from
1631:
1625:
1624:
1622:
1620:
1606:
1600:
1599:
1597:
1595:
1584:
1578:
1577:
1575:
1573:
1559:
1553:
1552:
1550:
1548:
1542:
1536:. Archived from
1535:
1527:
1516:
1515:
1477:
1471:
1470:
1464:
1456:
1450:
1449:
1443:
1435:
1429:
1428:
1426:
1424:
1410:
1404:
1403:
1365:
1356:
1355:
1353:
1351:
1341:
1335:
1334:
1332:
1330:
1321:. Archived from
1315:
1309:
1308:
1306:
1304:
1290:
1284:
1283:
1245:
1239:
1238:
1236:
1234:
1225:. Archived from
1219:
1213:
1212:
1174:
1168:
1167:
1165:
1163:
1149:
1143:
1142:
1140:
1138:
1129:. Archived from
1123:
1117:
1116:
1114:
1112:
1103:. Archived from
1097:
1091:
1090:
1088:
1086:
1077:. Archived from
1071:
1065:
1064:
1045:
1039:
1038:
1036:
1034:
1025:. Archived from
1019:
1013:
1012:
1010:
1008:
993:
987:
986:
984:
982:
977:on 16 April 2021
973:. Archived from
962:
956:
955:
953:
951:
937:
931:
930:
929:. 23 April 2018.
924:
916:
910:
909:
907:
905:
899:
888:
880:
874:
873:
871:
869:
863:
857:. Archived from
856:
848:
839:
838:
807:
801:
800:
797:Convergence 2006
794:
786:
780:
779:
769:
763:
762:
751:
745:
744:
742:
740:
730:
678:Automotive SPICE
561:
558:
540:
539:
533:
475:State Management
345:Classic Platform
291:software modules
101:
98:
31:
24:
20:
2033:
2032:
2028:
2027:
2026:
2024:
2023:
2022:
1993:
1992:
1974:
1973:
1970:
1949:
1930:
1922:. p. 406.
1914:
1912:Further reading
1909:
1908:
1898:
1896:
1887:
1886:
1882:
1872:
1870:
1865:
1864:
1860:
1850:
1848:
1846:www.autosar.org
1838:
1834:
1824:
1822:
1815:www.autosar.org
1809:
1808:
1804:
1794:
1792:
1785:www.autosar.org
1779:
1778:
1774:
1764:
1762:
1753:
1752:
1748:
1736:
1732:
1731:
1727:
1717:
1715:
1706:
1705:
1701:
1691:
1689:
1685:
1684:
1680:
1670:
1668:
1659:
1658:
1654:
1644:
1642:
1633:
1632:
1628:
1618:
1616:
1614:www.autosar.org
1610:"Core Partners"
1608:
1607:
1603:
1593:
1591:
1586:
1585:
1581:
1571:
1569:
1567:www.autosar.org
1561:
1560:
1556:
1546:
1544:
1540:
1533:
1529:
1528:
1519:
1504:
1478:
1474:
1462:
1458:
1457:
1453:
1441:
1437:
1436:
1432:
1422:
1420:
1418:www.autosar.org
1412:
1411:
1407:
1392:
1366:
1359:
1349:
1347:
1343:
1342:
1338:
1328:
1326:
1317:
1316:
1312:
1302:
1300:
1298:www.autosar.org
1292:
1291:
1287:
1272:
1246:
1242:
1232:
1230:
1221:
1220:
1216:
1201:
1175:
1171:
1161:
1159:
1157:www.autosar.org
1151:
1150:
1146:
1136:
1134:
1125:
1124:
1120:
1110:
1108:
1099:
1098:
1094:
1084:
1082:
1073:
1072:
1068:
1047:
1046:
1042:
1032:
1030:
1021:
1020:
1016:
1006:
1004:
995:
994:
990:
980:
978:
971:www.autosar.org
963:
959:
949:
947:
945:www.autosar.org
939:
938:
934:
922:
918:
917:
913:
903:
901:
897:
886:
882:
881:
877:
867:
865:
861:
854:
850:
849:
842:
809:
808:
804:
787:
783:
770:
766:
753:
752:
748:
738:
736:
732:
731:
724:
719:
674:
663:
661:AUTOSAR on site
656:GENIVI Alliance
645:
621:
602:Mentor Graphics
562:
556:
553:
537:
531:
501:Premium Partner
492:
407:
398:
358:microcontroller
347:
330:
321:
283:
259:
250:
245:
156:
134:for automotive
95:
74:
70:
17:
12:
11:
5:
2031:
2021:
2020:
2015:
2010:
2005:
1991:
1990:
1980:
1969:
1968:External links
1966:
1965:
1964:
1953:
1947:
1934:
1928:
1913:
1910:
1907:
1906:
1880:
1858:
1832:
1802:
1772:
1746:
1725:
1699:
1678:
1652:
1626:
1601:
1588:"Organization"
1579:
1554:
1517:
1502:
1472:
1451:
1430:
1405:
1390:
1357:
1336:
1310:
1285:
1270:
1240:
1214:
1199:
1169:
1144:
1118:
1092:
1066:
1040:
1014:
988:
957:
932:
911:
875:
840:
802:
781:
764:
761:. 5 June 2018.
746:
721:
720:
718:
715:
714:
713:
708:
703:
693:
687:
681:
673:
670:
662:
659:
658:
657:
654:
651:
644:
641:
640:
639:
630:
620:
617:
616:
615:
610:
605:
595:
590:
580:
577:Continental AG
564:
563:
543:
541:
530:
527:
515:
514:
511:
508:
505:
502:
499:
491:
488:
483:
482:
479:
476:
473:
463:
462:
459:
456:
453:
406:
403:
397:
394:
379:
378:
375:
372:
346:
343:
342:
341:
337:
334:
329:
326:
320:
317:
316:
315:
312:
294:
282:
279:
258:
255:
249:
246:
244:
241:
229:
228:
222:
216:
168:Continental AG
155:
152:
103:
102:
93:
89:
88:
85:
81:
80:
71:
68:
65:
64:
61:
57:
56:
53:
49:
48:
45:
41:
40:
37:
33:
32:
15:
9:
6:
4:
3:
2:
2030:
2019:
2016:
2014:
2011:
2009:
2006:
2004:
2001:
2000:
1998:
1988:
1984:
1981:
1977:
1972:
1971:
1962:
1958:
1954:
1950:
1944:
1940:
1935:
1931:
1925:
1921:
1916:
1915:
1894:
1890:
1884:
1868:
1862:
1847:
1843:
1836:
1820:
1816:
1812:
1806:
1790:
1786:
1782:
1776:
1760:
1756:
1750:
1742:
1735:
1729:
1713:
1709:
1703:
1688:
1682:
1666:
1662:
1656:
1640:
1636:
1630:
1615:
1611:
1605:
1589:
1583:
1568:
1564:
1558:
1539:
1532:
1526:
1524:
1522:
1513:
1509:
1505:
1499:
1495:
1491:
1487:
1483:
1476:
1468:
1461:
1455:
1447:
1440:
1434:
1419:
1415:
1409:
1401:
1397:
1393:
1387:
1383:
1379:
1375:
1371:
1364:
1362:
1346:
1340:
1324:
1320:
1314:
1299:
1295:
1289:
1281:
1277:
1273:
1267:
1263:
1259:
1255:
1251:
1244:
1228:
1224:
1218:
1210:
1206:
1202:
1196:
1192:
1188:
1184:
1180:
1173:
1158:
1154:
1148:
1132:
1128:
1122:
1106:
1102:
1096:
1080:
1076:
1070:
1063:
1059:
1055:
1051:
1044:
1028:
1024:
1018:
1002:
998:
992:
976:
972:
968:
961:
946:
942:
936:
928:
921:
915:
896:
892:
885:
879:
860:
853:
847:
845:
836:
832:
828:
824:
820:
816:
812:
806:
798:
793:
785:
777:
776:
768:
760:
756:
750:
735:
729:
727:
722:
712:
709:
707:
704:
701:
697:
694:
691:
688:
685:
682:
679:
676:
675:
669:
666:
655:
652:
650:
647:
646:
638:
634:
631:
629:
626:
625:
624:
614:
611:
609:
606:
603:
599:
596:
594:
591:
588:
584:
581:
578:
575:(now part of
574:
571:
570:
569:
560:
557:February 2021
551:
547:
544:This list is
542:
535:
534:
526:
522:
519:
512:
509:
506:
503:
500:
497:
496:
495:
487:
480:
477:
474:
471:
470:
469:
466:
460:
457:
454:
451:
450:
449:
446:
444:
440:
436:
431:
429:
425:
419:
415:
413:
402:
393:
391:
386:
382:
376:
373:
370:
369:
368:
365:
363:
359:
354:
352:
338:
335:
332:
331:
325:
313:
310:
306:
302:
298:
295:
292:
288:
287:
286:
278:
274:
270:
267:
265:
254:
240:
237:
233:
226:
223:
220:
217:
214:
211:
210:
209:
205:
203:
199:
195:
191:
186:
184:
183:Volkswagen AG
180:
177:
173:
169:
165:
161:
151:
149:
144:
139:
137:
133:
129:
125:
121:
117:
113:
109:
100:
94:
90:
86:
82:
78:
72:
66:
62:
58:
54:
50:
46:
42:
38:
34:
30:
25:
19:
1938:
1919:
1897:. Retrieved
1892:
1883:
1871:. Retrieved
1861:
1849:. Retrieved
1845:
1842:"Vendor IDs"
1835:
1823:. Retrieved
1819:the original
1814:
1805:
1793:. Retrieved
1789:the original
1784:
1775:
1763:. Retrieved
1759:the original
1749:
1740:
1728:
1716:. Retrieved
1712:the original
1702:
1690:. Retrieved
1681:
1669:. Retrieved
1665:the original
1655:
1643:. Retrieved
1639:the original
1629:
1617:. Retrieved
1613:
1604:
1592:. Retrieved
1582:
1570:. Retrieved
1566:
1557:
1545:. Retrieved
1538:the original
1485:
1475:
1466:
1454:
1445:
1433:
1421:. Retrieved
1417:
1408:
1373:
1348:. Retrieved
1339:
1327:. Retrieved
1323:the original
1313:
1301:. Retrieved
1297:
1288:
1253:
1243:
1231:. Retrieved
1227:the original
1217:
1182:
1172:
1160:. Retrieved
1156:
1153:"Foundation"
1147:
1135:. Retrieved
1131:the original
1121:
1109:. Retrieved
1105:the original
1095:
1083:. Retrieved
1079:the original
1069:
1053:
1049:
1043:
1031:. Retrieved
1027:the original
1017:
1005:. Retrieved
1000:
991:
979:. Retrieved
975:the original
970:
960:
948:. Retrieved
944:
935:
926:
914:
902:. Retrieved
895:the original
890:
878:
866:. Retrieved
859:the original
818:
814:
805:
796:
784:
774:
767:
758:
749:
737:. Retrieved
667:
664:
622:
600:(previously
567:
554:
523:
520:
516:
493:
490:Organization
484:
467:
464:
447:
432:
420:
416:
408:
399:
387:
383:
380:
366:
355:
348:
322:
284:
275:
271:
268:
260:
251:
238:
234:
230:
224:
218:
212:
206:
187:
157:
140:
123:
119:
115:
111:
107:
106:
76:
60:Headquarters
36:Company type
18:
1893:www.ibm.com
1851:25 February
1811:"Attendees"
1765:11 December
1718:11 December
1692:11 December
1671:11 December
1645:11 December
1547:11 December
1329:11 December
1233:11 December
1137:11 December
1111:11 December
1085:11 December
1033:11 December
868:11 December
739:11 December
628:dSPACE GmbH
481:Diagnostics
428:IEEE1003.13
328:Methodology
143:scalability
1997:Categories
1303:2 December
981:9 December
717:References
573:Elektrobit
546:incomplete
513:Subscriber
390:Franca IDL
319:Foundation
301:middleware
128:automotive
69:Key people
1590:. AUTOSAR
1512:240964305
1209:222221057
1062:2195-1454
941:"History"
835:2195-1470
690:ISO 26262
637:MathWorks
585:(part of
225:Phase III
138:(ECUs).
1899:10 April
1280:16258656
1050:ATZextra
700:Rhapsody
672:See also
510:Attendee
439:Ethernet
414:(GPUs).
371:Services
305:topology
219:Phase II
196:and the
114:omotive
44:Industry
1989:, etc.)
1987:COMASSO
1873:27 June
1741:AUTOSAR
1594:27 June
1467:AUTOSAR
1446:AUTOSAR
1400:1133757
1007:27 June
1001:AUTOSAR
927:AUTOSAR
891:AUTOSAR
759:AUTOSAR
598:Siemens
529:Vendors
299:(RTE):
213:Phase I
176:Siemens
154:History
108:AUTOSAR
97:autosar
92:Website
84:Members
52:Founded
22:AUTOSAR
1959:
1945:
1926:
1825:14 May
1795:14 May
1619:14 May
1572:14 May
1510:
1500:
1423:14 May
1398:
1388:
1350:14 May
1278:
1268:
1207:
1197:
1162:14 May
1060:
950:14 May
904:5 June
833:
633:MATLAB
248:Vision
122:ystem
1737:(PDF)
1541:(PDF)
1534:(PDF)
1508:S2CID
1463:(PDF)
1442:(PDF)
1396:S2CID
1276:S2CID
1205:S2CID
923:(PDF)
898:(PDF)
887:(PDF)
862:(PDF)
855:(PDF)
799:: 10.
706:MISRA
686:(ECU)
587:Bosch
424:POSIX
1957:ISBN
1943:ISBN
1924:ISBN
1901:2021
1875:2024
1853:2021
1827:2018
1797:2018
1767:2015
1720:2015
1694:2015
1673:2015
1647:2015
1621:2018
1596:2024
1574:2018
1549:2015
1498:ISBN
1425:2018
1386:ISBN
1352:2018
1331:2015
1305:2019
1266:ISBN
1235:2015
1195:ISBN
1164:2018
1139:2015
1113:2015
1087:2015
1058:ISSN
1035:2015
1009:2024
983:2020
952:2018
906:2018
870:2015
831:ISSN
741:2015
711:OSEK
583:ETAS
351:OSEK
181:and
118:pen
99:.org
55:2003
1490:doi
1378:doi
1258:doi
1187:doi
823:doi
635:by
552:.
392:).
362:RTE
340:it.
309:ECU
179:VDO
112:AUT
1999::
1891:.
1844:.
1813:.
1783:.
1739:.
1612:.
1565:.
1520:^
1506:.
1496:.
1484:.
1465:.
1444:.
1416:.
1394:.
1384:.
1372:.
1360:^
1296:.
1274:.
1264:.
1252:.
1203:.
1193:.
1181:.
1155:.
1054:18
1052:,
999:.
969:.
943:.
925:.
889:.
843:^
829:.
819:18
817:.
813:.
795:.
757:.
725:^
266:.
174:,
170:,
166:,
162:,
150:.
124:AR
1985:(
1963:.
1951:.
1932:.
1903:.
1877:.
1855:.
1829:.
1799:.
1769:.
1722:.
1696:.
1675:.
1649:.
1623:.
1598:.
1576:.
1551:.
1514:.
1492::
1427:.
1402:.
1380::
1354:.
1333:.
1307:.
1282:.
1260::
1237:.
1211:.
1189::
1166:.
1141:.
1115:.
1089:.
1037:.
1011:.
985:.
954:.
908:.
872:.
837:.
825::
743:.
702:)
604:)
589:)
579:)
559:)
555:(
120:S
116:O
110:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
