AUTOSAR
Release
Management
• Removed:
[RS_CRYPTO_02406]
• Updated:
[RS_CRYPTO_02201]
2019-11-28 19-11
AUTOSAR
Release
Management
• Removed:
[RS_CRYPTO_02114] [RS_CRYPTO_
02311] [RS_CRYPTO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRY

 Removed:
[RS_CRYPTO_02406]
• Updated:
[RS_CRYPTO_02201]
2019-11-28 19-11
AUTOSAR
Release
Management
• Removed:
[RS_CRYPTO_02114] [RS_CRYPTO_
02311] [RS_CRYPTO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]

AUTOSAR
Release
Management
• Removed:
[RS_CRYPTO_02114] [RS_CRYPTO_
02311] [RS_CRYPTO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[

:
[RS_CRYPTO_02114] [RS_CRYPTO_
02311] [RS_CRYPTO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [R

O_
02311] [RS_CRYPTO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_0

TO_02404]
• Updated:
[RS_CRYPTO_02009]
[RS_CRYPTO_02110]
2019-03-29 19-03
AUTOSAR
Release
Management
• Editorial changes and rephrasing
• Improved requirements description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_0

s description and
rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR

rationale (Updated :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management

 :
[RS_CRYPTO_02001]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requir

1]
[RS_CRYPTO_02002]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are correct

2]
[RS_CRYPTO_02003]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional re

3]
[RS_CRYPTO_02004]
[RS_CRYPTO_02005]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are add

5]
[RS_CRYPTO_02007]
[RS_CRYPTO_02009]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release

]
[RS_CRYPTO_02109] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release
Management
• Initial release
2 of 28 

] [RS_CRYPTO_
02116] [RS_CRYPTO_02202]
[RS_CRYPTO_02206])
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release
Management
• Initial release
2 of 28 Document ID 889: A

AUTOSAR
Release
Management
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release
Management
• Initial release
2 of 28 Document ID 889: AUTOSAR_AP_RS_Cryptography

ment
• Removed : [RS_CRYPTO_02303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release
Management
• Initial release
2 of 28 Document ID 889: AUTOSAR_AP_RS_Cryptography

303] and
[RS_CRYPTO_02402]
• Updated : [RS_CRYPTO_02006]
2018-03-29 18-03
AUTOSAR
Release
Management
• Existing requirements are corrected
• Additional requirements are added
2017-10-27 17-10
AUTOSAR
Release
Management
• Initial release
2 of 28 Document ID 889: AUTOSAR_AP_RS_Cryptography

 RS_EM_00110 and
RS_EM_00111.
• Added: [RS_EM_00014].
2018-03-29 18-03
AUTOSAR
Release
Management
• Removed: RS_EM_00006,
RS_EM_00007 and RS_EM_00012
• Minor changes and document clean up
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, document clean up
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
2 of 29 Document ID 720: AUTOSAR_AP_RS_ExecutionManagement

lowing requirements have been
revised: [RS_AP_00111], [RS_AP_
00113], [RS_AP_00114], [RS_AP_
00115], [RS_AP_00122], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125]
• Following requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_

evised: [RS_AP_00111], [RS_AP_
00113], [RS_AP_00114], [RS_AP_
00115], [RS_AP_00122], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125]
• Following requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID

00113], [RS_AP_00114], [RS_AP_
00115], [RS_AP_00122], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125]
• Following requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

00115], [RS_AP_00122], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125]
• Following requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125]
• Following requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

lowing requirements have been
deleted: [RS_AP_00117], [RS_AP_
00118]
• Following requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

ollowing requirements have been
added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

added: [RS_AP_00127], [RS_AP_
00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

00128], [RS_AP_00129], [RS_AP_
00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

00130], [RS_AP_00131], [RS_AP_
00132], [RS_AP_00134]
▽
2 of 42 Document ID 714: AUTOSAR_AP_RS_General

 now to
ISO/IEC 14882
• Description of [RS_AP_00115] revised
• Description of [RS_AP_00116], [RS_
AP_00117], [RS_AP_00118], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125] revised (in
general "all ara libraries" changed to "all
functional clusters").
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor fixes
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
3 of 4

[RS_AP_00115] revised
• Description of [RS_AP_00116], [RS_
AP_00117], [RS_AP_00118], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125] revised (in
general "all ara libraries" changed to "all
functional clusters").
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor fixes
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
3 of 42 Document ID 714: AUTOSAR_AP_RS_Genera

tion of [RS_AP_00116], [RS_
AP_00117], [RS_AP_00118], [RS_AP_
00120], [RS_AP_00121], [RS_AP_
00124], [RS_AP_00125] revised (in
general "all ara libraries" changed to "all
functional clusters").
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor fixes
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
3 of 42 Document ID 714: AUTOSAR_AP_RS_General

lease
Management
• Added: use case for [RS_OSI_00201]
and [RS_OSI_00202]
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed: RS_OSI_00102 and
RS_OSI_00105
• Added: [RS_OSI_00207],
[RS_OSI_00208].
2018-03-29 18-03
AUTOSAR
Release
Management
• Removed: RS_OSI_00101,
RS_OSI_00200 and RS_OSI_00205.
• Added: [RS_OSI_00103].
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, docum

Added: use case for [RS_OSI_00201]
and [RS_OSI_00202]
2018-10-31 18-10
AUTOSAR
Release
Management
• Removed: RS_OSI_00102 and
RS_OSI_00105
• Added: [RS_OSI_00207],
[RS_OSI_00208].
2018-03-29 18-03
AUTOSAR
Release
Management
• Removed: RS_OSI_00101,
RS_OSI_00200 and RS_OSI_00205.
• Added: [RS_OSI_00103].
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, document clean up
2017-0

RS_OSI_00102 and
RS_OSI_00105
• Added: [RS_OSI_00207],
[RS_OSI_00208].
2018-03-29 18-03
AUTOSAR
Release
Management
• Removed: RS_OSI_00101,
RS_OSI_00200 and RS_OSI_00205.
• Added: [RS_OSI_00103].
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, document clean up
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
2 of 21 Document ID 718: AUTOSAR_AP_RS_OperatingSyste

RS_OSI_00105
• Added: [RS_OSI_00207],
[RS_OSI_00208].
2018-03-29 18-03
AUTOSAR
Release
Management
• Removed: RS_OSI_00101,
RS_OSI_00200 and RS_OSI_00205.
• Added: [RS_OSI_00103].
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, document clean up
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
2 of 21 Document ID 718: AUTOSAR_AP_RS_OperatingSystemInterface

S_OSI_00200 and RS_OSI_00205.
• Added: [RS_OSI_00103].
2017-10-27 17-10
AUTOSAR
Release
Management
• Minor changes, document clean up
2017-03-31 17-03
AUTOSAR
Release
Management
• Initial release
2 of 21 Document ID 718: AUTOSAR_AP_RS_OperatingSystemInterface

neralFunctional_
WithInstanceSpecifier
[RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [R

l_
WithInstanceSpecifier
[RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [R

eSpecifier
[RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[R

_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [R

_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [R

S_AP_00177]
TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[

_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [

Functional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [

_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [

_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [

_AP_00115] [RS_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[

_AP_00116] [RS_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [

_AP_00119]
[RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [

_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [

_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [

_AP_00122] [RS_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[

_AP_00124] [RS_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [

_AP_00125]
[RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [

_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [

_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [

_AP_00129] [RS_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[

_AP_00130] [RS_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [

_AP_00134]
[RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [

_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [

_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [

_AP_00137] [RS_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[

_AP_00138] [RS_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [

_AP_00139]
[RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [

_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [

_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [

_AP_00142] [RS_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[

_AP_00143] [RS_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [

_AP_00144]
[RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
T

_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trac

_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of th

_AP_00147] [RS_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33

_AP_00148] [RS_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Documen

_AP_00149]
[RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTO

_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_Gene

_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00153] [RS_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00154] [RS_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00155]
[RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00158] [RS_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00159] [RS_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00160]
[RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00163] [RS_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00164] [RS_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00165]
[RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00169] [RS_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

_AP_00174] [RS_AP_00175]
[RS_AP_00176] [RS_AP_00178]
Table 5.1: Trace Groups of this document
33 of 42 Document ID 714: AUTOSAR_AP_RS_General

.
Requirement Description Satisfied by
[RS_SAF_10037] AUTOSAR shall provide mechanisms
to prevent unintended alteration of
data.
[RS_PER_00008]
[RS_SAF_10040] AUTOSAR shall support data
recovery mechanisms.
[RS_PER_00009]
Table 5.1: Requirements Tracing
17 of 24 Document ID 857: AUTOSAR_AP_RS_Persistency

prevent unintended alteration of
data.
[RS_PER_00008]
[RS_SAF_10040] AUTOSAR shall support data
recovery mechanisms.
[RS_PER_00009]
Table 5.1: Requirements Tracing
17 of 24 Document ID 857: AUTOSAR_AP_RS_Persistency

ded alteration of
data.
[RS_PER_00008]
[RS_SAF_10040] AUTOSAR shall support data
recovery mechanisms.
[RS_PER_00009]
Table 5.1: Requirements Tracing
17 of 24 Document ID 857: AUTOSAR_AP_RS_Persistency

hall support data
recovery mechanisms.
[RS_PER_00009]
Table 5.1: Requirements Tracing
17 of 24 Document ID 857: AUTOSAR_AP_RS_Persistency

.
Requirement Description Satisfied by
[RS_HM_09249] Health Monitoring shall support
building safety-related systems.
[RS_PHM_00114]
[RS_SAF_10005] AUTOSAR shall provide mechanisms
to support safe shutdown and
termination of application software
and embedded middleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition

pport
building safety-related systems.
[RS_PHM_00114]
[RS_SAF_10005] AUTOSAR shall provide mechanisms
to support safe shutdown and
termination of application software
and embedded middleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM

safety-related systems.
[RS_PHM_00114]
[RS_SAF_10005] AUTOSAR shall provide mechanisms
to support safe shutdown and
termination of application software
and embedded middleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM

tion software
and embedded middleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10030] AUTOSAR shall provide mechanisms
to support safe program execution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [R

nd embedded middleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10030] AUTOSAR shall provide mechanisms
to support safe program execution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Ta

dleware.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10030] AUTOSAR shall provide mechanisms
to support safe program execution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Table 5.1: Requir

M_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10006] AUTOSAR shall provide mechanisms
to support safe transition of states in
embedded middleware or service life
cycle.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10030] AUTOSAR shall provide mechanisms
to support safe program execution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Table 5.1: Requirements Tracing

M_00115] [RS_PHM_00116]
[RS_PHM_00117]
[RS_SAF_10030] AUTOSAR shall provide mechanisms
to support safe program execution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Table 5.1: Requirements Tracing
5.1 Not applicable requirements
[RS_PHM_NA]
Status: DRAFT
⌈These requirements are not applicable as they are not within the scope of this re-
lease.⌋
17 of 22 Document ID 852: 

ecution.
[RS_PHM_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Table 5.1: Requirements Tracing
5.1 Not applicable requirements
[RS_PHM_NA]
Status: DRAFT
⌈These requirements are not applicable as they are not within the scope of this re-
lease.⌋
17 of 22 Document ID 852: AUTOSAR_AP_RS_PlatformHealthManagement

M_00115] [RS_PHM_00116]
[RS_PHM_00118] [RS_PHM_00119]
Table 5.1: Requirements Tracing
5.1 Not applicable requirements
[RS_PHM_NA]
Status: DRAFT
⌈These requirements are not applicable as they are not within the scope of this re-
lease.⌋
17 of 22 Document ID 852: AUTOSAR_AP_RS_PlatformHealthManagement

.
Requirement Description Satisfied by
[RS_SAF_31301] E2E Protection with E2E T ransformer
and E2E Library
[RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO

 with E2E T ransformer
and E2E Library
[RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

sformer
and E2E Library
[RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

 Library
[RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

E_08538] [RS_E2E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

E_08544] [RS_E2E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

E_08545]
[RS_E2E_08546] [RS_E2E_08547]
[RS_SAF_31302] Allow integrators to configure safety
mechanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

hanisms to detect communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

ct communication
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

n
faults
[RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543]
Table 5.1: Requirements Tracing
14 of 28 Document ID 847: AUTOSAR_FO_RS_E2E

ent
AUTOSAR AP R25-11
△
Number Heading
[RS_CM_00413] Support of IEEE1722 Stream handling
Table A.2: Added Requirements in R24-11
A.2.2 Changed Requirements in R24-11
none
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_CM_00600] Creation of CommunicationGroups
[RS_CM_00601] Provide origin of information
Table A.3: Deleted Requirements in R24-11
A.3 Traceable item history of this 

 Requirements in R24-11
Number Heading
[RS_CM_00600] Creation of CommunicationGroups
[RS_CM_00601] Provide origin of information
Table A.3: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to
AUTOSAR Release R23-11
A.3.1 Added Requirements in R23-11
none
A.3.2 Changed Requirements in R23-11
Number Heading
[RS_CM_00600] Creation of CommunicationGroups
[

00600] Creation of CommunicationGroups
[RS_CM_00601] Provide origin of information
Table A.3: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to
AUTOSAR Release R23-11
A.3.1 Added Requirements in R23-11
none
A.3.2 Changed Requirements in R23-11
Number Heading
[RS_CM_00600] Creation of CommunicationGroups
[RS_CM_00601] Provide origin of information
Tab

ent
AUTOSAR AP R25-11
△
Number Heading
[RS_EM_00152] Execution Management shall support standardized trace points throughout
the state transitions.
Table A.1: Changed Requirements in R25-11
A.1.3 Deleted Requirements in R25-11
none
A.2 Traceable item history of this document according to AU-
TOSAR Release R24-11
A.2.1 Added Requirements in R24-11
none
A.2.2 Changed Requirements in R24-11

 Requirements in R24-11
Number Heading
[RS_EM_00002] Execution Management shall set-up one process for the execution of each
Modelled Process.
[RS_EM_00005] Execution Management shall support the configuration of OS resource
budgets for process and groups of processes.
[RS_EM_00008] Execution Management shall support the binding of all threads of a given
process to a specified set of pro

he execution of each
Modelled Process.
[RS_EM_00005] Execution Management shall support the configuration of OS resource
budgets for process and groups of processes.
[RS_EM_00008] Execution Management shall support the binding of all threads of a given
process to a specified set of processor cores.
[RS_EM_00009] Execution Management shall control the right to create child process for
eac

s for process and groups of processes.
[RS_EM_00008] Execution Management shall support the binding of all threads of a given
process to a specified set of processor cores.
[RS_EM_00009] Execution Management shall control the right to create child process for
each process it starts.
[RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of
processes.
[RS_EM_001

to a specified set of processor cores.
[RS_EM_00009] Execution Management shall control the right to create child process for
each process it starts.
[RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of
processes.
[RS_EM_00101] Execution Management shall support State Management functionality .
[RS_EM_00103] Execution Management shall support process lifec

ld process for
each process it starts.
[RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of
processes.
[RS_EM_00101] Execution Management shall support State Management functionality .
[RS_EM_00103] Execution Management shall support process lifecycle management.
[RS_EM_00150] Error Handling.
[RS_EM_00151] Execution Management shall be implemented at least

tiated graceful shutdown of
processes.
[RS_EM_00101] Execution Management shall support State Management functionality .
[RS_EM_00103] Execution Management shall support process lifecycle management.
[RS_EM_00150] Error Handling.
[RS_EM_00151] Execution Management shall be implemented at least according the highest
safety integrity level from any process that is supported on the platform

pport State Management functionality .
[RS_EM_00103] Execution Management shall support process lifecycle management.
[RS_EM_00150] Error Handling.
[RS_EM_00151] Execution Management shall be implemented at least according the highest
safety integrity level from any process that is supported on the platform.
[RS_EM_00152] Execution Management shall support standardized trace points throu

 support process lifecycle management.
[RS_EM_00150] Error Handling.
[RS_EM_00151] Execution Management shall be implemented at least according the highest
safety integrity level from any process that is supported on the platform.
[RS_EM_00152] Execution Management shall support standardized trace points throughout
the state transitions.
Table A.2: Changed Requirements in R24-11
21 of 29

agement.
[RS_EM_00150] Error Handling.
[RS_EM_00151] Execution Management shall be implemented at least according the highest
safety integrity level from any process that is supported on the platform.
[RS_EM_00152] Execution Management shall support standardized trace points throughout
the state transitions.
Table A.2: Changed Requirements in R24-11
21 of 29 Document ID 720: AUTOSAR_AP_R

 Requirements in R24-11
Number Heading
[RS_EM_00050] Execution Management shall perform Machine-wide coordination of
process.
[RS_EM_00051] Execution Management shall provide APIs to the process for configuring
external trigger conditions for its activities.
[RS_EM_00052] Execution Management shall provide APIs to the process for configuring
cyclic triggering of its activities.
[RS_EM_00

 Machine-wide coordination of
process.
[RS_EM_00051] Execution Management shall provide APIs to the process for configuring
external trigger conditions for its activities.
[RS_EM_00052] Execution Management shall provide APIs to the process for configuring
cyclic triggering of its activities.
[RS_EM_00053] Execution Management shall provide APIs to the process to support
deterministic re

trigger conditions for its activities.
[RS_EM_00052] Execution Management shall provide APIs to the process for configuring
cyclic triggering of its activities.
[RS_EM_00053] Execution Management shall provide APIs to the process to support
deterministic redundant execution of process.
[RS_EM_00113] Execution Management shall support time-triggered execution.
Table A.3: Deleted Requireme

g
cyclic triggering of its activities.
[RS_EM_00053] Execution Management shall provide APIs to the process to support
deterministic redundant execution of process.
[RS_EM_00113] Execution Management shall support time-triggered execution.
Table A.3: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to AU-
TOSAR Release R23-11
A.3.1 Added Requirements i

nistic redundant execution of process.
[RS_EM_00113] Execution Management shall support time-triggered execution.
Table A.3: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to AU-
TOSAR Release R23-11
A.3.1 Added Requirements in R23-11
Number Heading
[RS_EM_00152] Execution Management shall support standardized trace points
throughout the state transi

ent
AUTOSAR AP R25-11
△
Number Heading
[RS_EM_00006]
The Execution Management shall support the analysis of available and
required OS resource budgets for Executables and groups of Executables
during installation and run-time
[RS_EM_00007] The Execution Management shall support of the allocation of dedicated
resources for the Executable (e.g GPU)
[RS_EM_00008] The Execution Management sh

ables
during installation and run-time
[RS_EM_00007] The Execution Management shall support of the allocation of dedicated
resources for the Executable (e.g GPU)
[RS_EM_00008] The Execution Management shall support the binding of Executable threads
to a specified set of processor cores.
[RS_EM_00009] Only Execution Management shall start Executables
[RS_EM_00010] The Execution Management

ion Management shall start Executables
[RS_EM_00010] The Execution Management shall support multiple instantiation of
Executables
[RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of
Executable instances
[RS_EM_00012] Application Manifest shall support unambiguous identification of Executable
instances
[RS_EM_00013] Execution Management shall support confi

ceful shutdown of
Executable instances
[RS_EM_00012] Application Manifest shall support unambiguous identification of Executable
instances
[RS_EM_00013] Execution Management shall support configurable recovery actions
[RS_EM_00100] The Execution Management shall support the ordered startup and shutdown
of Executables
[RS_EM_00050] The Execution Management shall do a system-wide coordinat

identification of Executable
instances
[RS_EM_00013] Execution Management shall support configurable recovery actions
[RS_EM_00100] The Execution Management shall support the ordered startup and shutdown
of Executables
[RS_EM_00050] The Execution Management shall do a system-wide coordination of
activities.
[RS_EM_00051] The Execution Management shall provide functions to the Executable 

 support configurable recovery actions
[RS_EM_00100] The Execution Management shall support the ordered startup and shutdown
of Executables
[RS_EM_00050] The Execution Management shall do a system-wide coordination of
activities.
[RS_EM_00051] The Execution Management shall provide functions to the Executable for
configuring external trigger conditions for its activities
[RS_EM_00052] Th

orm
AUTOSAR AP R25-11
△
Number Heading
[RS_AP_00132] noexcept behavior of API functions
[RS_AP_00133] noexcept behavior of move and swap operations
[RS_AP_00134] noexcept behavior of class destructors
[RS_AP_00135] Avoidance of shared ownership
[RS_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Av

32] noexcept behavior of API functions
[RS_AP_00133] noexcept behavior of move and swap operations
[RS_AP_00134] noexcept behavior of class destructors
[RS_AP_00135] Avoidance of shared ownership
[RS_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_001

t behavior of move and swap operations
[RS_AP_00134] noexcept behavior of class destructors
[RS_AP_00135] Avoidance of shared ownership
[RS_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the A

noexcept behavior of class destructors
[RS_AP_00135] Avoidance of shared ownership
[RS_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created w

P_00135] Avoidance of shared ownership
[RS_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are 

S_AP_00140] Usage of "final specifier"
[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not
copyable, but at most movable.
[RS_AP

[RS_AP_00141] Usage of out parameters
[RS_AP_00144] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not
copyable, but at most movable.
[RS_AP_00149] Error handling for non-initial

4] Availability of a named constructor
[RS_AP_00145] Availability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not
copyable, but at most movable.
[RS_AP_00149] Error handling for non-initialized Functional Cluster
[RS_AP_00150] Provide only

ailability of special member functions
[RS_AP_00146] Classes whose construction requires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not
copyable, but at most movable.
[RS_AP_00149] Error handling for non-initialized Functional Cluster
[RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR
App

uires interaction by the ARA framework
[RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not
copyable, but at most movable.
[RS_AP_00149] Error handling for non-initialized Functional Cluster
[RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR
Applications and Functional Clusters
[RS_AP_00151] C++ Core Guidelines
[RS_AP_00155] A

are not
copyable, but at most movable.
[RS_AP_00149] Error handling for non-initialized Functional Cluster
[RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR
Applications and Functional Clusters
[RS_AP_00151] C++ Core Guidelines
[RS_AP_00155] Avoidance of cluster-specific initialization functions
[RS_AP_00156] Naming conventions for L&T Context ID
Table A.5: Ch

for non-initialized Functional Cluster
[RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR
Applications and Functional Clusters
[RS_AP_00151] C++ Core Guidelines
[RS_AP_00155] Avoidance of cluster-specific initialization functions
[RS_AP_00156] Naming conventions for L&T Context ID
Table A.5: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Nu

R
Applications and Functional Clusters
[RS_AP_00151] C++ Core Guidelines
[RS_AP_00155] Avoidance of cluster-specific initialization functions
[RS_AP_00156] Naming conventions for L&T Context ID
Table A.5: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_AP_00152] Faults inside constructor.
Table A.6: Deleted Requirements in R24-11
A.3 Change History 

ters
[RS_AP_00151] C++ Core Guidelines
[RS_AP_00155] Avoidance of cluster-specific initialization functions
[RS_AP_00156] Naming conventions for L&T Context ID
Table A.5: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_AP_00152] Faults inside constructor.
Table A.6: Deleted Requirements in R24-11
A.3 Change History of this document according to AUTO

ster-specific initialization functions
[RS_AP_00156] Naming conventions for L&T Context ID
Table A.5: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_AP_00152] Faults inside constructor.
Table A.6: Deleted Requirements in R24-11
A.3 Change History of this document according to AUTOSAR Re-
lease 23-11
A.3.1 Added Requirements in R23-11
none
37 of 42 

 Requirements in R24-11
Number Heading
[RS_AP_00152] Faults inside constructor.
Table A.6: Deleted Requirements in R24-11
A.3 Change History of this document according to AUTOSAR Re-
lease 23-11
A.3.1 Added Requirements in R23-11
none
37 of 42 Document ID 714: AUTOSAR_AP_RS_General

orm
AUTOSAR AP R25-11
△
Number Heading
[RS_AP_00131] Use of verbal forms to express requirement levels.
Table A.16: Deleted Requirements in 19-11
42 of 42 Document ID 714: AUTOSAR_AP_RS_General

ace
AUTOSAR AP R25-11
△
Number Heading
[RS_OSI_00211] The Operating System shall provide a mechanism to export low-level
scheduling and trace information to applications.
Table A.1: Changed Requirements in R25-11
A.1.3 Deleted Requirements in R25-11
none
A.2 Traceable item history of this document according to AU-
TOSAR Release R24-11
A.2.1 Added Requirements in R24-11
none
A.2.2 Changed

 Requirements in R24-11
Number Heading
[RS_OSI_00100] POSIX PSE51 Compliance
[RS_OSI_00103] The Operating System Interface shall support C++.
[RS_OSI_00104] The Operating System Interface shall support the reaction on
Process-external stimuli from devices.
[RS_OSI_00105] The Operating System Interface shall support the start of Execution
Management.
[RS_OSI_00201] The Operating System sh

[RS_OSI_00100] POSIX PSE51 Compliance
[RS_OSI_00103] The Operating System Interface shall support C++.
[RS_OSI_00104] The Operating System Interface shall support the reaction on
Process-external stimuli from devices.
[RS_OSI_00105] The Operating System Interface shall support the start of Execution
Management.
[RS_OSI_00201] The Operating System shall provide mechanisms for system memo

ng System Interface shall support C++.
[RS_OSI_00104] The Operating System Interface shall support the reaction on
Process-external stimuli from devices.
[RS_OSI_00105] The Operating System Interface shall support the start of Execution
Management.
[RS_OSI_00201] The Operating System shall provide mechanisms for system memory
budgeting.
[RS_OSI_00202] The Operating System shall provide m

Process-external stimuli from devices.
[RS_OSI_00105] The Operating System Interface shall support the start of Execution
Management.
[RS_OSI_00201] The Operating System shall provide mechanisms for system memory
budgeting.
[RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting.
[RS_OSI_00203] The Operating System should provide mechanisms for binding Process

ort the start of Execution
Management.
[RS_OSI_00201] The Operating System shall provide mechanisms for system memory
budgeting.
[RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting.
[RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to
CPU cores.
[RS_OSI_00204] The Operating System shall support authorized operating system 

echanisms for system memory
budgeting.
[RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting.
[RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to
CPU cores.
[RS_OSI_00204] The Operating System shall support authorized operating system object
access for the software entities which are allowed to do so.
[RS_OSI_00206] The Ope

ide mechanisms for CPU time budgeting.
[RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to
CPU cores.
[RS_OSI_00204] The Operating System shall support authorized operating system object
access for the software entities which are allowed to do so.
[RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of
applications.
[RS_

ms for binding Processes to
CPU cores.
[RS_OSI_00204] The Operating System shall support authorized operating system object
access for the software entities which are allowed to do so.
[RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of
applications.
[RS_OSI_00207] The Operating System shall provide the capability to share code and data in
an implicit

e entities which are allowed to do so.
[RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of
applications.
[RS_OSI_00207] The Operating System shall provide the capability to share code and data in
an implicit manner.
[RS_OSI_00208] The Operating System shall allow Processes to access only required
functionality .
▽
18 of 21 Document ID 718: AUTOSAR_AP_

support for isolation of
applications.
[RS_OSI_00207] The Operating System shall provide the capability to share code and data in
an implicit manner.
[RS_OSI_00208] The Operating System shall allow Processes to access only required
functionality .
▽
18 of 21 Document ID 718: AUTOSAR_AP_RS_OperatingSystemInterface

e code and data in
an implicit manner.
[RS_OSI_00208] The Operating System shall allow Processes to access only required
functionality .
▽
18 of 21 Document ID 718: AUTOSAR_AP_RS_OperatingSystemInterface

ace
AUTOSAR AP R25-11
△
Number Heading
[RS_OSI_00209] The Operating System shall support error handling including unrecoverable
errors.
[RS_OSI_00210] The Operating System shall provide a mechanism to observe scheduling of
CPU time to T ask, Process
[RS_OSI_00211] The Operating System shall provide a mechanism to export low-level
scheduling and trace information to applications.
Table A.

ndling including unrecoverable
errors.
[RS_OSI_00210] The Operating System shall provide a mechanism to observe scheduling of
CPU time to T ask, Process
[RS_OSI_00211] The Operating System shall provide a mechanism to export low-level
scheduling and trace information to applications.
Table A.2: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
none
A.3 Traceable item hi

 Requirements in R24-11
Number Heading
[RS_PHM_00107] Platform Health Management shall support multiple instantiation on
different platforms.
Table A.6: Changed Requirements in R24-11
A.3.3 Deleted Requirements in R24-11
Number Heading
[RS_PHM_00001] The Platform Health Management shall provide a standardized header
file structure for each service.
[RS_PHM_00002] The service header files

 Requirements in R24-11
Number Heading
[RS_PHM_00001] The Platform Health Management shall provide a standardized header
file structure for each service.
[RS_PHM_00002] The service header files shall define the namespace for the respective
service.
[RS_PHM_00003] The Platform Health Management shall define how language specific
data types are derived from modeled data types.
[RS_PHM_0010

eader
file structure for each service.
[RS_PHM_00002] The service header files shall define the namespace for the respective
service.
[RS_PHM_00003] The Platform Health Management shall define how language specific
data types are derived from modeled data types.
[RS_PHM_00102] Platform Health Management shall provide a standardized C++
interface for the reporting of Health Channel .
[RS_

 namespace for the respective
service.
[RS_PHM_00003] The Platform Health Management shall define how language specific
data types are derived from modeled data types.
[RS_PHM_00102] Platform Health Management shall provide a standardized C++
interface for the reporting of Health Channel .
[RS_PHM_00108]
Platform Health Management shall provide a standardized interface
between Platform H

s are derived from modeled data types.
[RS_PHM_00102] Platform Health Management shall provide a standardized C++
interface for the reporting of Health Channel .
[RS_PHM_00108]
Platform Health Management shall provide a standardized interface
between Platform Health Management components used in a daisy
chain.
[RS_PHM_00109] Platform Health Management shall provide the Daisy chaining
int

 for the reporting of Health Channel .
[RS_PHM_00108]
Platform Health Management shall provide a standardized interface
between Platform Health Management components used in a daisy
chain.
[RS_PHM_00109] Platform Health Management shall provide the Daisy chaining
interface over ara::com.
[RS_PHM_09255] Platform Health Management shall provide an interface to receive
Health Channel superv

ment components used in a daisy
chain.
[RS_PHM_00109] Platform Health Management shall provide the Daisy chaining
interface over ara::com.
[RS_PHM_09255] Platform Health Management shall provide an interface to receive
Health Channel supervision status
[RS_PHM_09257] Platform Health Management shall provide an interface to Supervised
Entities to report their health status.
Table A.7: Del

aisy chaining
interface over ara::com.
[RS_PHM_09255] Platform Health Management shall provide an interface to receive
Health Channel supervision status
[RS_PHM_09257] Platform Health Management shall provide an interface to Supervised
Entities to report their health status.
Table A.7: Deleted Requirements in R24-11
A.4 Traceable item history of this document according to
AUTOSAR Release

eive
Health Channel supervision status
[RS_PHM_09257] Platform Health Management shall provide an interface to Supervised
Entities to report their health status.
Table A.7: Deleted Requirements in R24-11
A.4 Traceable item history of this document according to
AUTOSAR Release R25-11
A.4.1 Added Requirements in R25-11
none
A.4.2 Changed Requirements in R25-11
none
21 of 22 Document ID 852

ion
AUTOSAR AP R25-11
△
Number Heading
[RS_SHWA_00014] Device Properties
[RS_SHWA_00015] Device Abstraction
[RS_SHWA_00016] Event-based Synchronization
[RS_SHWA_00017] Data Access
[RS_SHWA_00018] Environment Information
Table B.2: Added Requirements in R25-11
B.2.2 Changed Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_000

ding
[RS_SHWA_00014] Device Properties
[RS_SHWA_00015] Device Abstraction
[RS_SHWA_00016] Event-based Synchronization
[RS_SHWA_00017] Data Access
[RS_SHWA_00018] Environment Information
Table B.2: Added Requirements in R25-11
B.2.2 Changed Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Me

ies
[RS_SHWA_00015] Device Abstraction
[RS_SHWA_00016] Event-based Synchronization
[RS_SHWA_00017] Data Access
[RS_SHWA_00018] Environment Information
Table B.2: Added Requirements in R25-11
B.2.2 Changed Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integr

HWA_00016] Event-based Synchronization
[RS_SHWA_00017] Data Access
[RS_SHWA_00018] Environment Information
Table B.2: Added Requirements in R25-11
B.2.2 Changed Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resour

ronization
[RS_SHWA_00017] Data Access
[RS_SHWA_00018] Environment Information
Table B.2: Added Requirements in R25-11
B.2.2 Changed Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resources Clean Up
Table B.3: Chan

 Requirements in R25-11
Number Heading
[RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resources Clean Up
Table B.3: Changed Requirements in R25-11
B.2.3 Deleted Requirements in R25-11
none
17 of 17 Document ID 1087: AUTOSAR_AP_RS_SafeHardwareAccelerati

ions Execution on Hardware Accelerator
[RS_SHWA_00007] Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resources Clean Up
Table B.3: Changed Requirements in R25-11
B.2.3 Deleted Requirements in R25-11
none
17 of 17 Document ID 1087: AUTOSAR_AP_RS_SafeHardwareAcceleration

 Synchronous Errors Handling Mechanism
[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resources Clean Up
Table B.3: Changed Requirements in R25-11
B.2.3 Deleted Requirements in R25-11
none
17 of 17 Document ID 1087: AUTOSAR_AP_RS_SafeHardwareAcceleration

[RS_SHWA_00009] Data Integrity Support
[RS_SHWA_00010] Allocated Resources Clean Up
Table B.3: Changed Requirements in R25-11
B.2.3 Deleted Requirements in R25-11
none
17 of 17 Document ID 1087: AUTOSAR_AP_RS_SafeHardwareAcceleration

 Requirements in R22-11
Number Heading
[RS_SM_00101] State Management shall support diagnostic reset cause
Table A.7: Deleted Requirements in R22-11
A.4.4 Added Constraints in R22-11
none
A.4.5 Changed Constraints in R22-11
none
A.4.6 Deleted Constraints in R22-11
none
A.5 Traceable item history of this document according to
AUTOSAR Release R21-11
A.5.1 Added Requirements "in R21-11"
Num

equirements "in R21-11"
Number Heading
[RS_SM_00001] State Management shall coordinate and control multiple sets of
Adaptive Applications .
[RS_SM_00004] State Management shall provide standardized interfaces.
[RS_SM_00005] State Management internal states.
[RS_SM_00100] State Management shall support ECU reset
[RS_SM_00101] State Management shall support diagnostic reset cause
[RS_SM_00

ltiple sets of
Adaptive Applications .
[RS_SM_00004] State Management shall provide standardized interfaces.
[RS_SM_00005] State Management internal states.
[RS_SM_00100] State Management shall support ECU reset
[RS_SM_00101] State Management shall support diagnostic reset cause
[RS_SM_00200] State Management shall provide an interface between State
Management instances.
[RS_SM_00300] St

shall provide standardized interfaces.
[RS_SM_00005] State Management internal states.
[RS_SM_00100] State Management shall support ECU reset
[RS_SM_00101] State Management shall support diagnostic reset cause
[RS_SM_00200] State Management shall provide an interface between State
Management instances.
[RS_SM_00300] State Management shall support variant handling based on calibration
dat

005] State Management internal states.
[RS_SM_00100] State Management shall support ECU reset
[RS_SM_00101] State Management shall support diagnostic reset cause
[RS_SM_00200] State Management shall provide an interface between State
Management instances.
[RS_SM_00300] State Management shall support variant handling based on calibration
data.
[RS_SM_00400] State Management shall establis

t shall support diagnostic reset cause
[RS_SM_00200] State Management shall provide an interface between State
Management instances.
[RS_SM_00300] State Management shall support variant handling based on calibration
data.
[RS_SM_00400] State Management shall establish communication paths dynamically .
[RS_SM_00401] State Management shall control Adaptive Applications depending
on dynamic

ce between State
Management instances.
[RS_SM_00300] State Management shall support variant handling based on calibration
data.
[RS_SM_00400] State Management shall establish communication paths dynamically .
[RS_SM_00401] State Management shall control Adaptive Applications depending
on dynamic communication paths .
Table A.8: Added Requirements "in R21-11"
18 of 22 Document ID 909: AUT

nt handling based on calibration
data.
[RS_SM_00400] State Management shall establish communication paths dynamically .
[RS_SM_00401] State Management shall control Adaptive Applications depending
on dynamic communication paths .
Table A.8: Added Requirements "in R21-11"
18 of 22 Document ID 909: AUTOSAR_AP_RS_StateManagement

lish communication paths dynamically .
[RS_SM_00401] State Management shall control Adaptive Applications depending
on dynamic communication paths .
Table A.8: Added Requirements "in R21-11"
18 of 22 Document ID 909: AUTOSAR_AP_RS_StateManagement

d Requirements in 19-11
Number Heading
[RS_SM_00500] State Management shall support efficient resource usage.
Table A.11: Deleted Requirements in 19-11
A.7.4 Added Constraints in 19-11
none
A.7.5 Changed Constraints in 19-11
none
A.7.6 Deleted Constraints in 19-11
none
A.8 Traceable item history of this document according to
AUTOSAR Release R19-03
A.8.1 Added Requirements in 19-03
Number

d Requirements in 19-03
Number Heading
[RS_SM_00002] State Management shall support Component State change requests.
[RS_SM_00201] State Management shall provide the interface over ara::com.
Table A.14: Deleted Requirements in 19-03
A.8.4 Added Constraints in 19-03
none
A.8.5 Changed Constraints in 19-03
none
A.8.6 Deleted Constraints in 19-03
none
22 of 22 Document ID 909: AUTOSAR_AP_RS

pport Component State change requests.
[RS_SM_00201] State Management shall provide the interface over ara::com.
Table A.14: Deleted Requirements in 19-03
A.8.4 Added Constraints in 19-03
none
A.8.5 Changed Constraints in 19-03
none
A.8.6 Deleted Constraints in 19-03
none
22 of 22 Document ID 909: AUTOSAR_AP_RS_StateManagement

ics
AUTOSAR FO R25-11
△
Number Heading
[RS_Diag_04235] Client certificate validity
[RS_Diag_04236] Client certificate target identification
[RS_Diag_04237] Client certificate evaluation
[RS_Diag_04238] Logging certificate evaluation
Table A.4: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_Diag_04059] Configuration of timing parameters
[RS_Diag_042

iag_04235] Client certificate validity
[RS_Diag_04236] Client certificate target identification
[RS_Diag_04237] Client certificate evaluation
[RS_Diag_04238] Logging certificate evaluation
Table A.4: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_Diag_04059] Configuration of timing parameters
[RS_Diag_04222] Independence of clearing DTC status and 

ient certificate target identification
[RS_Diag_04237] Client certificate evaluation
[RS_Diag_04238] Logging certificate evaluation
Table A.4: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_Diag_04059] Configuration of timing parameters
[RS_Diag_04222] Independence of clearing DTC status and system degradation
Table A.5: Deleted Requirements in R24

g_04237] Client certificate evaluation
[RS_Diag_04238] Logging certificate evaluation
Table A.4: Changed Requirements in R24-11
A.2.3 Deleted Requirements in R24-11
Number Heading
[RS_Diag_04059] Configuration of timing parameters
[RS_Diag_04222] Independence of clearing DTC status and system degradation
Table A.5: Deleted Requirements in R24-11
A.3 Traceable item history of this documen

 Requirements in R24-11
Number Heading
[RS_Diag_04059] Configuration of timing parameters
[RS_Diag_04222] Independence of clearing DTC status and system degradation
Table A.5: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to
AUTOSAR Release R23-11
A.3.1 Added Requirements in R23-11
Number Heading
[RS_Diag_04270] Notify applications about the changes

59] Configuration of timing parameters
[RS_Diag_04222] Independence of clearing DTC status and system degradation
Table A.5: Deleted Requirements in R24-11
A.3 Traceable item history of this document according to
AUTOSAR Release R23-11
A.3.1 Added Requirements in R23-11
Number Heading
[RS_Diag_04270] Notify applications about the changes of enable conditions
[RS_Diag_04271] Support of T 

 Requirements in R23-11
Number Heading
[RS_Diag_04270] Notify applications about the changes of enable conditions
[RS_Diag_04271] Support of T ransmit Certificate
[RS_Diag_04272] Support of secure data coding
Table A.6: Added Requirements in R23-11
A.3.2 Changed Requirements in R23-11
none
A.3.3 Deleted Requirements in R23-11
none
75 of 75 Document ID 4: AUTOSAR_FO_RS_Diagnostics

about the changes of enable conditions
[RS_Diag_04271] Support of T ransmit Certificate
[RS_Diag_04272] Support of secure data coding
Table A.6: Added Requirements in R23-11
A.3.2 Changed Requirements in R23-11
none
A.3.3 Deleted Requirements in R23-11
none
75 of 75 Document ID 4: AUTOSAR_FO_RS_Diagnostics

4271] Support of T ransmit Certificate
[RS_Diag_04272] Support of secure data coding
Table A.6: Added Requirements in R23-11
A.3.2 Changed Requirements in R23-11
none
A.3.3 Deleted Requirements in R23-11
none
75 of 75 Document ID 4: AUTOSAR_FO_RS_Diagnostics

ing
AUTOSAR FO R25-11
△
Number Heading
[RS_HM_09253] Health Monitoring shall support mode-dependent behavior of Supervised
Entities.
[RS_HM_09254] Health Monitoring shall provide an interface to Supervised Entities to report
the currently reached Checkpoint.
[RS_HM_09257] Health Monitoring shall support a variable number of supervised entity
occurences at runtime
[RS_HM_09300] System Hea

ndent behavior of Supervised
Entities.
[RS_HM_09254] Health Monitoring shall provide an interface to Supervised Entities to report
the currently reached Checkpoint.
[RS_HM_09257] Health Monitoring shall support a variable number of supervised entity
occurences at runtime
[RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized
service events
[RS_HM_09301] SHM 

port
the currently reached Checkpoint.
[RS_HM_09257] Health Monitoring shall support a variable number of supervised entity
occurences at runtime
[RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized
service events
[RS_HM_09301] SHM shall receive relevant health information from local health monitors
[RS_HM_09302] Communication between SHM and local health 

upervised entity
occurences at runtime
[RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized
service events
[RS_HM_09301] SHM shall receive relevant health information from local health monitors
[RS_HM_09302] Communication between SHM and local health monitors shall be E2E
protected
[RS_HM_09303] SHM shall be platform agnostic
[RS_HM_09304] SHM shall determ

icators as standardized
service events
[RS_HM_09301] SHM shall receive relevant health information from local health monitors
[RS_HM_09302] Communication between SHM and local health monitors shall be E2E
protected
[RS_HM_09303] SHM shall be platform agnostic
[RS_HM_09304] SHM shall determine Health Indicators.
[RS_HM_09305] SHM should support redundancy concepts
[RS_HM_09306] SHM shall 

information from local health monitors
[RS_HM_09302] Communication between SHM and local health monitors shall be E2E
protected
[RS_HM_09303] SHM shall be platform agnostic
[RS_HM_09304] SHM shall determine Health Indicators.
[RS_HM_09305] SHM should support redundancy concepts
[RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be conf

health monitors shall be E2E
protected
[RS_HM_09303] SHM shall be platform agnostic
[RS_HM_09304] SHM shall determine Health Indicators.
[RS_HM_09305] SHM should support redundancy concepts
[RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be configurable within Abstract Platform Description information
[RS_HM_09308] Communication bet

_09303] SHM shall be platform agnostic
[RS_HM_09304] SHM shall determine Health Indicators.
[RS_HM_09305] SHM should support redundancy concepts
[RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be configurable within Abstract Platform Description information
[RS_HM_09308] Communication between SHM instances shall be E2E protected
[RS

SHM shall determine Health Indicators.
[RS_HM_09305] SHM should support redundancy concepts
[RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be configurable within Abstract Platform Description information
[RS_HM_09308] Communication between SHM instances shall be E2E protected
[RS_HM_09309] Cyclic communication between SHM and local

SHM should support redundancy concepts
[RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be configurable within Abstract Platform Description information
[RS_HM_09308] Communication between SHM instances shall be E2E protected
[RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used
for aliveness checks
[

ct with Non-AUTOSAR software platforms
[RS_HM_09307] SHM shall be configurable within Abstract Platform Description information
[RS_HM_09308] Communication between SHM instances shall be E2E protected
[RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used
for aliveness checks
[RS_HM_09310] Cyclic communication between SHM instances shall be used for aliven

tract Platform Description information
[RS_HM_09308] Communication between SHM instances shall be E2E protected
[RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used
for aliveness checks
[RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness
checks
Table A.2: Changed Requirements in R25-11
A.4.3 Deleted Requirements in R25-11

n SHM instances shall be E2E protected
[RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used
for aliveness checks
[RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness
checks
Table A.2: Changed Requirements in R25-11
A.4.3 Deleted Requirements in R25-11
none
29 of 29 Document ID 878: AUTOSAR_FO_RS_HealthMonitoring

ors shall be used
for aliveness checks
[RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness
checks
Table A.2: Changed Requirements in R25-11
A.4.3 Deleted Requirements in R25-11
none
29 of 29 Document ID 878: AUTOSAR_FO_RS_HealthMonitoring

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00029]
[RS_L T_00030]
[RS_L T_00031]
[RS_L T_00032]
[RS_L T_00033]
[RS_L T_00034]
[RS_L T_00035]
[RS_L T_00036]
[RS_L T_00037]
[RS_L T_00038]
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_0

Requirements on Log and T race
AUTOSAR FO R25-11
△
Number Heading
[RS_L T_00039]
[RS_L T_00040]
[RS_L T_00041] L T shall be a central software component for the log and trace functionality .
[RS_L T_00042] The Log and trace SW component shall be part of the system during
production phase.
[RS_L T_00043]
[RS_L T_00044]
[RS_L T_00045]
[RS_L T_00046]

ent
AUTOSAR FO R25-11
△
Number Heading
[RS_Nm_02537] The Nm Coordinator shall be able to abort the coordinated shutdown
[RS_Nm_02540] The Nm Control Bit Vector shall contain a PN shutdown request bit.
[RS_Nm_02541] Nm shall define a common layout of Nm messages.
[RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown
request bit if a least one PNC is released

able to abort the coordinated shutdown
[RS_Nm_02540] The Nm Control Bit Vector shall contain a PN shutdown request bit.
[RS_Nm_02541] Nm shall define a common layout of Nm messages.
[RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown
request bit if a least one PNC is released
[RS_Nm_02544] Nm shall forward the indication of a PN shutdown message
[RS_Nm_02

all contain a PN shutdown request bit.
[RS_Nm_02541] Nm shall define a common layout of Nm messages.
[RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown
request bit if a least one PNC is released
[RS_Nm_02544] Nm shall forward the indication of a PN shutdown message
[RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial
Network

define a common layout of Nm messages.
[RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown
request bit if a least one PNC is released
[RS_Nm_02544] Nm shall forward the indication of a PN shutdown message
[RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial
Networking Learning (optional)
[RS_Nm_02548]
<Bus>Nm shall be able to

est bit if a least one PNC is released
[RS_Nm_02544] Nm shall forward the indication of a PN shutdown message
[RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial
Networking Learning (optional)
[RS_Nm_02548]
<Bus>Nm shall be able to propagate and evaluate the need for synchronized
PNC shutdown in the role of a top-level PNC coordinator or intermediate
PNC co

he indication of a PN shutdown message
[RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial
Networking Learning (optional)
[RS_Nm_02548]
<Bus>Nm shall be able to propagate and evaluate the need for synchronized
PNC shutdown in the role of a top-level PNC coordinator or intermediate
PNC coordinator (optional)
[RS_Nm_02549] Nm shall offer interfaces to Request

Partial
Networking Learning (optional)
[RS_Nm_02548]
<Bus>Nm shall be able to propagate and evaluate the need for synchronized
PNC shutdown in the role of a top-level PNC coordinator or intermediate
PNC coordinator (optional)
[RS_Nm_02549] Nm shall offer interfaces to Request and indicate Repeat Message Request
(optional)
[RS_Nm_02562] Nm shall support channel-specific storage of IRA
[RS

ntermediate
PNC coordinator (optional)
[RS_Nm_02549] Nm shall offer interfaces to Request and indicate Repeat Message Request
(optional)
[RS_Nm_02562] Nm shall support channel-specific storage of IRA
[RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA
[RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA
[RS_Nm_02565] <Bus>

cate Repeat Message Request
(optional)
[RS_Nm_02562] Nm shall support channel-specific storage of IRA
[RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA
[RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA
[RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers
using dedicated APIs
[RS_Nm_02566] 

upport channel-specific storage of IRA
[RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA
[RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA
[RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers
using dedicated APIs
[RS_Nm_02566] Nm shall support channel-specific configuration for ERA
[RS_Nm_

ed partial network request status EIRA
[RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA
[RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers
using dedicated APIs
[RS_Nm_02566] Nm shall support channel-specific configuration for ERA
[RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels
Table A.

 external partial network requests ERA
[RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers
using dedicated APIs
[RS_Nm_02566] Nm shall support channel-specific configuration for ERA
[RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels
Table A.2: Changed Requirements in R22-11
A.1.3 Deleted Requirements in R22-11
Number Heading
[RS

 the upper layers
using dedicated APIs
[RS_Nm_02566] Nm shall support channel-specific configuration for ERA
[RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels
Table A.2: Changed Requirements in R22-11
A.1.3 Deleted Requirements in R22-11
Number Heading
[RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown
[RS_Nm_02545] <Bus>NM shall handle r

channel-specific configuration for ERA
[RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels
Table A.2: Changed Requirements in R22-11
A.1.3 Deleted Requirements in R22-11
Number Heading
[RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown
[RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown
Table A.3: Deleted Requirements 

 Requirements in R22-11
Number Heading
[RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown
[RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown
Table A.3: Deleted Requirements in R22-11
A.1.4 Added Constraints in R22-11
none
A.1.5 Changed Constraints in R22-11
none
37 of 39 Document ID 927: AUTOSAR_FO_RS_NetworkManagement

requests for synchronized PNC shutdown
[RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown
Table A.3: Deleted Requirements in R22-11
A.1.4 Added Constraints in R22-11
none
A.1.5 Changed Constraints in R22-11
none
37 of 39 Document ID 927: AUTOSAR_FO_RS_NetworkManagement

ion
AUTOSAR FO R25-11
△
Number Heading
[RS_TS_20036] The Timesync over CAN module shall use the time measurement and
synchronization protocol to transmit and receive an offset value
[RS_TS_20044] The Timesync over FlexRay module shall use the time measurement and
synchronization protocol to transmit and receive an offset value
[RS_TS_20063]
The Timesync over Ethernet module shall use the

o transmit and receive an offset value
[RS_TS_20044] The Timesync over FlexRay module shall use the time measurement and
synchronization protocol to transmit and receive an offset value
[RS_TS_20063]
The Timesync over Ethernet module shall use the Time Synchronization
protocol for Synchronized Time Bases to transmit and receive Offset Time
Bases
Table A.2: Deleted Requirements in R24-11

o transmit and receive an offset value
[RS_TS_20063]
The Timesync over Ethernet module shall use the Time Synchronization
protocol for Synchronized Time Bases to transmit and receive Offset Time
Bases
Table A.2: Deleted Requirements in R24-11
A.2 Change History of this document according to AUTOSAR Re-
lease R25-11
A.2.1 Added Requirements in R25-11
none
A.2.2 Changed Requirements in R25

 Requirements in R25-11
Number Heading
[RS_TS_00002] The Implementation of Time Synchronization shall maintain its own Time
Base independently of the acting role.
[RS_TS_00003] The TS shall initialize the Local Time Base with a configurable startup value
[RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time
Base with a configurable startup value.
[RS_T

Base independently of the acting role.
[RS_TS_00003] The TS shall initialize the Local Time Base with a configurable startup value
[RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time
Base with a configurable startup value.
[RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have
access to the Synchronized Time Base
[RS_T

Base with a configurable startup value
[RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time
Base with a configurable startup value.
[RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have
access to the Synchronized Time Base
[RS_TS_00006] The Implementation of Time Synchronization shall provide time information
to TSP mo

ase with a configurable startup value.
[RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have
access to the Synchronized Time Base
[RS_TS_00006] The Implementation of Time Synchronization shall provide time information
to TSP modules
[RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time
Base of a Time Slave, on reception of a 

e
access to the Synchronized Time Base
[RS_TS_00006] The Implementation of Time Synchronization shall provide time information
to TSP modules
[RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time
Base of a Time Slave, on reception of a Time Master value
[RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its
Time Bases based 

rovide time information
to TSP modules
[RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time
Base of a Time Slave, on reception of a Time Master value
[RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its
Time Bases based on a Time Base reference clock
[RS_TS_00009] The Implementation of Time Synchronization shall maintain 

e, on reception of a Time Master value
[RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its
Time Bases based on a Time Base reference clock
[RS_TS_00009] The Implementation of Time Synchronization shall maintain the
synchronization status of a Time Base
[RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master
side to set 

s based on a Time Base reference clock
[RS_TS_00009] The Implementation of Time Synchronization shall maintain the
synchronization status of a Time Base
[RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master
side to set the Global Time
[RS_TS_00011] The Implementation of Time Synchronization shall allow customers on
master side to trigger time transmissio

synchronization status of a Time Base
[RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master
side to set the Global Time
[RS_TS_00011] The Implementation of Time Synchronization shall allow customers on
master side to trigger time transmission by the TSP module
[RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read
User Da

 on master
side to set the Global Time
[RS_TS_00011] The Implementation of Time Synchronization shall allow customers on
master side to trigger time transmission by the TSP module
[RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read
User Data propagated via the TSP modules.
▽
46 of 49 Document ID 906: AUTOSAR_FO_RS_TimeSync

er time transmission by the TSP module
[RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read
User Data propagated via the TSP modules.
▽
46 of 49 Document ID 906: AUTOSAR_FO_RS_TimeSync

ion
AUTOSAR FO R25-11
△
Number Heading
[RS_TS_20059] The Timesync over Ethernet module shall access all communication ports
belonging to Time Synchronization
[RS_TS_20060] The Timesync over Ethernet module shall provide a Time Base after
reception of a valid protocol information
[RS_TS_20061] The Timesync over Ethernet module shall support means to protect the
Time Synchronization protoc

orts
belonging to Time Synchronization
[RS_TS_20060] The Timesync over Ethernet module shall provide a Time Base after
reception of a valid protocol information
[RS_TS_20061] The Timesync over Ethernet module shall support means to protect the
Time Synchronization protocol
[RS_TS_20062] The Timesync over Ethernet module shall support user specific data within
the time measurement and syn

eption of a valid protocol information
[RS_TS_20061] The Timesync over Ethernet module shall support means to protect the
Time Synchronization protocol
[RS_TS_20062] The Timesync over Ethernet module shall support user specific data within
the time measurement and synchronization protocol
[RS_TS_20066] The Timesync over Ethernet module shall support measuring the
peer-to-peer delay using

tect the
Time Synchronization protocol
[RS_TS_20062] The Timesync over Ethernet module shall support user specific data within
the time measurement and synchronization protocol
[RS_TS_20066] The Timesync over Ethernet module shall support measuring the
peer-to-peer delay using the IEEE 802.1AS peer-to-peer delay mechanism.
[RS_TS_20068] The Timesync over CAN module shall support classic 

asurement and synchronization protocol
[RS_TS_20066] The Timesync over Ethernet module shall support measuring the
peer-to-peer delay using the IEEE 802.1AS peer-to-peer delay mechanism.
[RS_TS_20068] The Timesync over CAN module shall support classic CAN and CAN FD
[RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus
protocol specific parameters
[RS_T

 802.1AS peer-to-peer delay mechanism.
[RS_TS_20068] The Timesync over CAN module shall support classic CAN and CAN FD
[RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus
protocol specific parameters
[RS_TS_20070] The Timesync over CAN module shall support hardware and software
timestamping
[RS_TS_20071] The Timesync over Ethernet module shall enable 

e shall support classic CAN and CAN FD
[RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus
protocol specific parameters
[RS_TS_20070] The Timesync over CAN module shall support hardware and software
timestamping
[RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on
peer-to-peer and multidrop topologies
[RS_TS_20072] The 

ss to bus
protocol specific parameters
[RS_TS_20070] The Timesync over CAN module shall support hardware and software
timestamping
[RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on
peer-to-peer and multidrop topologies
[RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time
Synchronization protocol
[RS_TS_20073] The Timesy

ort hardware and software
timestamping
[RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on
peer-to-peer and multidrop topologies
[RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time
Synchronization protocol
[RS_TS_20073] The Timesync over CAN module shall support means to secure the Time
Synchronization protocol
[RS_TS_20

peer-to-peer and multidrop topologies
[RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time
Synchronization protocol
[RS_TS_20073] The Timesync over CAN module shall support means to secure the Time
Synchronization protocol
[RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time
Synchronization protocol
[RS_TS_20075] Rate Ra

cure the Time
Synchronization protocol
[RS_TS_20073] The Timesync over CAN module shall support means to secure the Time
Synchronization protocol
[RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time
Synchronization protocol
[RS_TS_20075] Rate Ratio Calculation
Table A.3: Changed Requirements in R25-11
A.2.3 Deleted Requirements in R25-11
none
49 of 49 Doc

cure the Time
Synchronization protocol
[RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time
Synchronization protocol
[RS_TS_20075] Rate Ratio Calculation
Table A.3: Changed Requirements in R25-11
A.2.3 Deleted Requirements in R25-11
none
49 of 49 Document ID 906: AUTOSAR_FO_RS_TimeSync

cure the Time
Synchronization protocol
[RS_TS_20075] Rate Ratio Calculation
Table A.3: Changed Requirements in R25-11
A.2.3 Deleted Requirements in R25-11
none
49 of 49 Document ID 906: AUTOSAR_FO_RS_TimeSync

Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Header file name

onale: –
Dependencies: –
Use Case: –
⌋
[RS_AP_00116] Header file name ⌈
Description:
All Functional Clusters should provide a self-contained header file for each
public class. The header file name shall be derived from the class name.
All header file names shall have the extension .h.
Additional information:
• Scoped enums, non-member functions, and exceptions are not required to
have a 

Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Type names

to Adaptive
Platform
AUTOSAR AP R25-11
[RS_AP_00122] Type names ⌈
Description:
For all Functional Clusters: the name of their public types - classes, structs,
type aliases, and type template parameters
• shall be standardized in upper-camel case.
• underscores shall not be used. Except for fixed width integer types, postfix _t
shall not be used.
• capitalized acronyms shall be used as si

Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Return values / application errors

 return values
to output parameters.
⌋
[RS_AP_00119] Return values / application errors ⌈
Description:
All API function specifications shall give the exact list of standardized errors
(linked to the ErrorDomains which define them) that can originate from them,
and which situations can cause which of those errors. Furthermore, for return
values (especially integral, floating-point, enumer