用語(terms)

No.	term	Description	Doc.	Qiita
1	2’s complement	method of signed number representation	875	50
2	2oo2	two out of two	885	38
3	2oo2D	two out of two with diagnostics	885	38
4	2oo3	two out of three	885	38
5	AA	AUTOSAR Adaptive Application	723	6
6	ABI	Application Binary Interface	709	10
7	Access Control Decision	The Access Control Decision is a Boolean value indicating if the requested operation is permitted or not. It is based on the identity of the caller and the Access Control	899	54
8	Access Control Decision	The access control decision is a Boolean value indicating if the requested operation is permitted or not. It is based on the identity of the caller and the Access Control Policy.	706	14
9	Access control Policy	Access Control Policies are bound to the targets of calls (i.e. Service interfaces) and are used to express what Identity Information are necessary to access those interfaces.	899	54
10	Access Control Policy	Access Control Policies are used to define constraints that have to be met in order to access specific objects (e.g. Service Interfaces).	706	14
11	ACL	Access Control List	883	17
12	ACL	Access Control List	1027	29
13	AD	Automated Driving	885	38
14	AD	Automated Driving	911	47
15	AD	Automated Driving	912	49
16	AD	Automated Driving	913	45
17	Adaptive Application	An adaptive application is a part of application SW in the architecture of Adaptive AUTOSAR. An adaptive application runs on top of ARA and accesses AUTOSAR functional clusters through ARA.	883	17
18	Adaptive Application	Refers to the Adaptive Application defined in [1].	853	24
19	Adaptive Application	See [1, AUTOSAR Glossary]	983	40
20	Adaptive Application	see [2] AUTOSAR Glossary	719	33
21	Adaptive Application	see [4] AUTOSAR Glossary	718	31
22	Adaptive Application Identifier	A referrer to AAID, i.e. AUTOSAR Process, pointing to exactly one AAID.	706	14
23	Adaptive Application Identity (AAID)	The modelled identity of an Adaptive Application is represented by the AUTOSAR Process.	706	14
24	AP	Adaptive Platform	782	16
25	Adaptive Platform	Refers to the AUTOSAR Adaptive Platform defined in [1].	853	24
26	Adaptive Platform Foundation	Refers to the Adaptive Platform Foundation defined in [1].	853	24
27	Adaptive Platform Foundation	see [2] AUTOSAR Glossary	719	33
28	Adaptive Platform Foundation	see [4] AUTOSAR Glossary	718	31
29	Adaptive Platform Services	Adaptive Platform Services are located below the ARA. They provide platform standard services of Adaptive AUTOSAR.	883	17
30	ADAS	Advanced Driver Assistance System	885	38
31	ADAS	Autonomous Driving and Assistance System	884	41
32	ADI	Automated Driving Interfaces	911	47
33	ADI	Automated Driving Interfaces	912	49
34	ADI	Automated Driving Interfaces	913	45
35	ADS	Automated Driving Systems	885	38
36	AE	Authenticated Encryption	883	17
37	AEAD	Authenticated Encryption with Associated Data - Encryption scheme which simultaneously provides confidentiality and authenticity of data as well as additional authenticated but not encrypted data.	883	17
38	AEB	Autonomous Emergency Braking	911	47
39	AEB	Autonomous Emergency Braking	912	49
40	AEB	Autonomous Emergency Braking	913	45
41	AES	Advanced Encryption Standard	713	53
42	AES	Advanced Encryption Standard - A block cipher for the symmetric encryption of electronic data.	883	17
43	Aging	Unlearning/deleting of a no longer failed event/DTC after a defined number of operation cycles from event memory.	723	6
44	AH	Autenticating Header protocol	930	32
45	Alive Supervision	Mechanism to check the timing constraints of cyclic Supervised Entityes to be within the configured min and max limits.	852	18
46	Alive Supervision	Mechanism to check the timing constraints of cyclic Supervised Entitys to be within the configured min and max limits.	851	30
47	Allocator	A language specific object responsible for (de-)allocation, (de-)initialization and ultimately limit impositions in memory/storage. C++ allocators must satisfy the requirements for an Allocator in ISO/IEC 14882 (version according to [RS_AP_00114]).	994	35
48	AP	AUTOSAR Adaptive Platform	709	10
49	AP	AUTOSAR Adaptive Platform	723	6
50	API	Abstract Programming Interface	883	17
51	API	Application Programming Interface	709	10
52	API	Application Programming Interface	898	46
53	API	Application Programming Interface	983	40
54	Application	see [2] AUTOSAR Glossary	719	33
55	Application	see [2] AUTOSAR Glossary	852	18
56	Application	see [4] AUTOSAR Glossary	718	31
57	Application Error	Errors returned by UCM	888	43
58	Application ID	Application ID is a unique identifier of an Adaptive Application. In the meta-model an Adaptive Application is represented by Process.	899	54
59	Application process	An executable instance (process) that is running on a Machine	853	28
60	ARA	AUTOSAR Run-time for Applications	884	41
61	ARA	Autosar Runtime Environment for Adaptive Applications	883	17
62	ara::com	Communication middleware for the AUTOSAR Adaptive Platform	851	30
63	ara::com	Communication middleware for the AUTOSAR Adaptive Platform	852	18
64	ARTI	AUTOSAR Run Time Interface	915	56
65	ARXML	AUTOSAR XML	713	53
66	ARXML	AUTOSAR XML is the standardized exchange format for AUTOSAR configuration.	709	10
67	ASIL	Automotive Safety Integrity Level	885	38
68	ASIL capability	Capability of an item or an element to meet assumed safety requirements assigned with a given ASIL	885	38
69	ASN.1	Abstract Syntax Notation One, as defined in the ASN.1 standards	883	17
70	Asymmetric Key	An asymmetric key describes a pair of two keys (public and private key). A cipher text created by one key cannot be decrypted with this key. Encryption is only possible with the other key of this pair.	883	17
71	ATP	AUTOSAR Template Profile	713	53
72	AUTOSAR	Adaptive Platform	see [6] AUTOSAR Glossary	851
73	AUTOSAR Adaptive Platform	see [2] AUTOSAR Glossary	719	33
74	AUTOSAR Adaptive Platform	see [2] AUTOSAR Glossary	852	18
75	AUTOSAR Adaptive Platform	see [4] AUTOSAR Glossary	718	31
76	AUTOSAR Resource	The term AUTOSAR Resource covers interfaces that are under the scope of IAM, i.e. Service Interfaces.	899	54
77	Backend	Backend is a server hosting Software Packages	887	42
78	Backend	Backend is a server hosting Software Packages	888	43
79	BER	Basic Encoding Rules	883	17
80	Binding	This typically describes the realization of some abstract concept with a specific implementation or technology. In AUTOSAR, for instance, we have an abstract data type and interface model described in the methodology. Mapping it to a concrete programming language is called language binding. In the AUTOSAR Adaptive Platform for instance we do have a C++ language binding. In this explanatory document we typically use the tech term binding to refer to the implementation of the abstract (technology independent) ara::com API to a concrete communication transport technology like for instance sockets, pipes, shared memory, ...	846	23
81	BLOB	Binary Large Object - A Binary Large OBject (BLOB) is a collection of binary data stored as a single entity.	883	17
82	Block Cipher	A symmetric encryption that encrypts plaintext blocks of fixed length.	883	17
83	BOM	Byte Order Mark	717	27
84	Boot options	Boot Manager Configuration	888	43
85	Bus communication	Communication on the physical medium	898	46
86	CA	Certificate Authority	1027	29
87	CA	Certificate Authority or Certification Authority is an entity that issues digital certificates.	883	17
88	Callable	In the context of C++ a Callable is defined as: A Callable type is a type for which the INVOKE operation (used by, e.g., std::function, std::bind, and std::thread::thread) is applicable. This operation may be performe	846	23
89	Car2X	Car-to-X-Communication is the generic term for various communication technologies in automotive, including car-to-car (C2C) and car-to-infrastructure (C2I) communication. The information is either transmitted directly between vehicles via IEEE 802.11p, between car and roadside infrastructure or by using existing mobile networks.	913	45
90	CBC	Cipher Block Chaining Mode - A mode of operation for symmetric ciphers (e.g. AES) that supports encryption.	883	17
91	CBC-MAC	Cipher Block Chaining Message Authentication Mode - A mode of operation for symmetric ciphers (e.g. AES) that supports authentication.	883	17
92	CBV	Control Bit Vector	898	46
93	CCA	Common Cause Failure Analysis	885	38
94	CCM	Counter Mode with CBC-MAC - An AEAD operation mode (encryption and authentication) for AES.	883	17
95	certificate serial number	An integer value, unique within the issuing authority, which is unambiguously associated with a certificate issued by that authority.	883	17
96	certification path	An ordered list of one or more public-key certificates, starting with a public-key certificate signed by the trust anchor, and ending with the public key certificate to be validated. All intermediate public-key certificates, if any, are CA-certificates in which the subject of the preceding certificate is the issuer of the following certificate.	883	17
97	Channel	An abstraction of a network specific communication channel. In CAN networks a Channel can be identified via CAN identifier. In Ethernet networks a Channel might be defined by the quadruple Src-IP, Src-Port, Target-IP, Target-Port.	723	6
98	Checkpoint	A point in the control flow of a Supervised Entity where the activity is reported.	851	30
99	Checkpoint	A point in the control flow of a Supervised Entity where the activity is reported.	852	18
100	Checksum	A value used to verify the integrity of a data stored or transmitted	885	38
101	Ciphertext	A ciphertext is an encrypted text, which is the result of encryption performed on plaintext.	883	17
102	CP	Classic Platform	782	16
103	CM	AUTOSAR Adaptive Communication Management	852	18
104	CM	Communication Management	717	27
105	CM	Communication Management	898	46
106	CMAC	Cipher-based Message Authentication Code - A mode of operation for symmetric ciphers (e.g. AES) that supports authentication and is similar but advanced to CBC-MAC.	883	17
107	CMP	X.509 Certificate Management Provider.	883	17
108	CO	Cryptographic Object	883	17
109	COM	Communication Management	709	10
110	com	Communication Management	862	39
111	Communication Management	A Functional Cluster within the Adaptive PlatformFoundation	720	22
112	Communication Management	see [4] AUTOSAR Communication Management	888	43
113	Communication Management[1]	A Functional Cluster within the Adaptive Platform Foundation	908	44
114	Companion Process	A type of Reporting Process that is associated with Non-reporting Process and used to determine when functionality expected from Non-reporting Process is available. Whenever functional dependencies on Non-reporting Processes exist, the integrator can configure proxy Execution Dependencies on the Companion Process and make the Companion Process kRunning reporting conditional on monitored Non-reporting Process.	721	21
115	Context Switching Time	The time consumed by the CPU in switching from one process or thread to another	885	38
116	core	Adaptive Platform Core	862	39
117	COUID	Cryptographic Object Unique Identifier	883	17
118	CP	AUTOSAR Classic Platform	709	10
119	CP	AUTOSAR Classic Platform	723	6
120	CP Gateway	TR Glossary ([4]) defines: A gateway is functionality within an ECU that performs a frame or signal mapping function between two communication systems. Communication system in this context means e.g. a CAN system or one channel of a FlexRay system. For clarity we use the term CP Gateway instead.	709	10
121	CRL	Certificate Revocation Lists is a list of digital certificates that have been revoked before their expiration date was reached. This list contains all the serial numbers of the revoked certificates and the revoked data.	883	17
122	crypto	Cryptography	862	39
123	Crypto Provider	A structural element that organizes cryptographic primitives.	883	17
124	CryptoAPI	The set of all interfaces that are provided by FC Crypto to consumers.	883	17
125	Cryptographic primitives	Well-established, low-level cryptographic algorithms that are frequently used to build cryptographic protocols for computer security systems.	883	17
126	CSR	Certificate Signing Request	883	17
127	CTL	Certificate Trust List is a list of digital certificates that are explicitly trusted in this environment. This list contains all the serial numbers of the explicitly trusted certificates.	883	17
128	CTM	Counter Mode	713	53
129	ctor	C++ constructor	846	23
130	Current Offset of the Offset TimeBase given as function parameter TOStop	Current Offset of the Offset Time Base given as function parameter.	880	55
131	cvalue expression	An expression that should not undergo further conversions, either implicitly or explicitly, is called a cvalue expression.	839	36
132	CWU	Car Wakeup	898	46
133	Cybersecurity	A set of techniques used to protect the integrity of networks, programs and data from attack, damage or unauthorized access. ->Security	885	38
134	D-PDU	API Diagnostic Protocol Data Unit Application Programming Interface	888	43
135	Daisy chaining	Chaining multiple instances of Health Monitoring	851	30
136	Daisy chaining	Chaining multiple instances of Health Monitoring	852	18
137	Data Determinism	The results of a calculation only depend on the input data and are reproducible, assuming a given initial internal state.	720	22
138	Data Determinism	The results of a calculation only depend on the input data and are reproducible, assuming a given initial internal state.	721	21
139	Data ID	A unique identifier of an instance of data transmitted.	716	26
140	Data integrity	Data integrity is the maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle and is a critical aspect to the design, implementation and usage of any system which stores, processes, or retrieves data.[27]	885	38
141	Dataflow Anomaly	The state of a variable at a point in a program can be described using the following terms: Undefined (U): The value of the variable is indeterminate. Referenced (R): The variable is used in some way (e.g. in an expression). Defined (D): The variable is explicitly initialized or assigned a value. Given the above, the following dataflow anomalies can be defined: UR dataflow anomaly: Variable not assigned a value before the specified use (this may result in undefined behavior). DU dataflow anomaly: Variable is assigned a value that is never subsequently used. DD dataflow anomaly: Variable is assigned a value twice with no intermediate use.	839	36
142	DB	Database	930	32
143	Dcm	Diagnostic Communication Manager (Module of the AUTOSAR Classic Platform)	723	6
144	DDID	Dynamically Defined Data Identifier according to ISO 14229-1[1].	723	6
145	DDS	Data Distribution Service	713	53
146	DDS	Data Distribution Service	1027	29
147	DDS	Data Distribution Servicev	717	27
148	Dead Code	Dead code (also known as redundant code) consists of evaluated expressions whose removal would not affect the output program.	839	36
149	Deadline	End Checkpoint A Checkpoint for which Deadline Supervision is configured and which is a ending point for a particular Transition. It is possible that a Checkpoint is both a Deadline Start Checkpoint and Deadline End Checkpoint - if Deadline Supervision is chained.	852	18
150	Deadline Start Checkpoint	A Checkpoint for which Deadline Supervision is configured and which is a starting point for a particular Transition.	852	18
151	Deadline Supervision	Mechanism to check that the timing constraints for execution of the transition from a Deadline Start Checkpoint to a corresponding Deadline End Checkpoint are within the configured min and max limits.	851	30
152	Deadline Supervision	Mechanism to check that the timing constraints for execution of the transition from a Deadline Start Checkpoint to a corresponding Deadline End Checkpoint are within the configured min and max limits.	852	18
153	Dependencies	–	712	51
154	DER	Distinguished Encoding Rules as defined in [2]	883	17
155	DES	Data Encryption Standard	713	53
156	Deterministic Random Numbers	A set of random numbers that follows a known sequence and thus the same set can be distributed (one at a time) to deterministic workers. Note that this does not mean that randomness is compromised as that relates to predictability of the sequence by an observer and not to the fact that the set is predefined.	721	21
157	DeterministicClient	Adaptive Application interface to Execution Management to support control of the process-internal cycle, a deterministic worker pool, activation time stamps and random numbers.	720	22
158	DeterministicClient	Adaptive Application interface to Execution Management to support control of the process-internal cycle, a deterministic worker pool, activation time stamps and random numbers.	721	21
159	DeterministicSyncMaster	A synchronization control point that receives the synchronization requests through a dedicated communication channel, for example ara::com, and sends the calculated cycle information for the next execution cycle to the connected DeterministicClients in the same domain.	721	21
160	DEXT	AUTOSAR Diagnostic Extract[3], describing diagnostic configuration of an ECU	723	6
161	DFA	Dependent Failure Analysis	885	38
162	DH	Diffie-Hellman (key exchange method)	883	17
163	diag	Diagnostics	862	39
164	Diagnostic Client	A Diagnostic Client is a diagnostic service requester, i.e. sends a UDS request to the Diagnostic Server. Usually the Diagnostic Client is an external tester equipment but can also be another vehicle internal ECU.	723	6
165	Diagnostic Communication Management	Diagnostic Communication Management is the part of the Diagnostic Management which belongs to tester communication and the processing of UDS services.	723	6
166	Diagnostic Conversation	Diagnostic Conversation represents a conversation between Diagnostic Client (Tester) and Diagnostic Server.	723	6
167	Diagnostic Event Management	Diagnostic Event Management is the part of the Diagnostic Management which belongs to processing and storing of diagnostic events and associated data.	723	6
168	Diagnostic Management	Diagnostic Management is a placeholder for the complete functionality of diagnostic communication and event handling.	723	6
169	Diagnostic Management [6]	A Functional Cluster within the Adaptive Platform Services	908	44
170	Diagnostic Server instance	Diagnostic Server (DM) is intended to support an own Diagnostic Server instance per installed SoftwareCluster, see section 7.5 for a detailed description. Each of those Server instances has and manages its own resources and is responsible for dispatching and processing of diagnostic services.	723	6
171	Diagnostic Service instance	A diagnostic service instance implements a concrete use of a diagnostic service in a given context. It refers to a DiagnosticServiceClass and the DiagnosticAccessPermission , see 7.5.1.5.3 for a detailed description.	723	6
172	Diamond Problem	The “diamond problem” is an ambiguity that arises when two classes B and C inherit from A, and class D inherits from both B and C. If there is a method provided by class A, that is overriden in both B and C and D does not override it, then there is an ambiguity which version of the method does D actually inherit. See: Wikipedia.org for more details.	839	36
173	DID	Data Identifier according to ISO 14229-1[1]. This 16 bit value uniquely defines one ore more data elements (parameters) that can are used in diagnostics to read, write or control data.	723	6
174	Displacement	In case of an Event memory overflow: Replacing the most insignificant stored event memory entry by a reported event which needs to be stored and is more significant.	723	6
175	Distinguished name	is originally defined in X.501 [4] as a representation of a directory name, defined as a construct that identifies a particular object from among a set of all objects.	883	17
176	DLT	Diagnostics Log and Trace - a GENIVI Log and Trace daemon implementation of the LT protocol	853	28
177	DM	AUTOSAR Adaptive Diagnostic Management	723	6
178	DM	AUTOSAR Adaptive Diagnostic Management	852	18
179	DM	AUTOSAR Adaptive Diagnostic Management	888	43
180	DM	Diagnostic Manager	709	10
181	DM	Diagnostic Manager	713	53
182	DMR	Dual Modular Redundancy	885	38
183	DoIP	Diagnostics over Internet Protocol	982	37
184	DoIP	Diagnostics over Internet Protocol (Communication protocol of automotive electronics according to ISO-13400[5])	723	6
185	DoIP	Diagnostics over IP	709	10
186	DST	Daylight Saving Time, also know as Day Light Saving (abbreviated DLS), is the practice of advancing clocks during summer months so that evening daylight lasts longer, while sacrificing normal sunrise times. Typically, regions that use daylight saving time adjust clocks forward one hour close to the start of spring and adjust them backward in the autumn to standard time.	880	55
187	DTC	Diagnostic Trouble Code	709	10
188	DTC	Diagnostic Trouble Code	713	53
189	DTC	Diagnostic Trouble Code according to ISO 14229-1[1]	723	6
190	DTC group	Uniquely identifies a set of DTCs. A DTC group is mapped to the range of valid DTCs. By providing a group of DTCs it is expressed that a certain operation is requested on all DTCs of that group. The DTC group definition is provided by ISO 14229-1[1] and OEM/supplier-specific.	723	6
191	DTCStatusAvailabilityMask	The DTCStatusAvailabilityMask - byte is used in UDS responses to requests for certain sub-functions of service 0x19. It express which of the UDS DTC status bits are supported by the DM for masking purposes.	723	6
192	DTLS	Datagram Transport Layer Security	717	27
193	dtor	C++ destructor	846	23
194	E/E system	Electric and Electronic system	709	10
195	E2E	AUTOSAR End to End communication protection mechanism	851	30
196	E2E	End-to-end communication protection	717	27
197	ECB	Electronic Code Book	713	53
198	ECC	Elliptic Curve Cryptography	713	53
199	ECC	Elliptic Curve Cryptography - Public-key cryptography based on the structure of elliptic curves.	883	17
200	ECC	Error Correction Code	885	38
201	ECDH	Elliptic Curve Diffie-Hellman - An ECC based DH key exchange with perfect forward secrecy.	883	17
202	ECDSA	Elliptic Curve Digital Signature Algorithm	713	53
203	ECDSA	Elliptic Curve Digital Signature Algorithm - An ECC based signature scheme.	883	17
204	ECIES	Elliptic Curve Integrated Encryption Scheme	713	53
205	ECIES	Elliptic Curve Integrated Encryption Scheme - An ECC based encryption scheme.	883	17
206	ECU	AUTOSAR TR Glossary ([4]) defines: ECU = Electronic Control Unit.For clarity we use the terms ECU-HW and ECU-Instance instead.	709	10
207	ECU	Electronic control unit	723	6
208	ECU	Electronic Control Unit	883	17
209	ECU	Electronic Control Unit	930	32
210	ECU	Electronic Control Unit	968	52
211	ECU-HW	We consider an Electronic Control Unit as a container for any combination of AP and CP stacks.For this document the term ECU-HW is typically abstracted/independent from physical or virtual realization - if issues like ECUHousing containing multiple physical ECU-HW, or physical ECU-HW providing multiple virtual ECU-HWs are of importance this is explicitly mentioned.	709	10
212	EDDSA	Edwards-Curve Digital Signature Algorithm	713	53
213	EDR	Extended Data Record	723	6
214	Element	Refers to either a key-value pair of a Key-Value Storage or a file of a File Storage. Used in the specification where something applies to all kinds of storage elements.	853	24
215	EM	Execution Management	898	46
216	Enable Conditions	The criteria / conditions under which the test results from the monitors in the AA’s are valid and shall be processed by DM. Configuration is done per event.	723	6
217	ESP	Encapsulating Security Payload protocol	930	32
218	Event	An event (also diagnostic event) uniquely identifies a fault path of the system. An application monitors the system and reports events to the DM.	723	6
219	Event memory	The DM stores information about events in the event memory. There can be multiple event memories, each keeping information independently from each other. Examples of the event memory is the UDS primary event memory or the up to 256 user-defined event memories.	723	6
220	Event memory overflow	An event memory overflow occurs, if this specific event memory is full and the next event occurs to be stored in this event memory.	723	6
221	Event status	Bit-packed status information based on Event level. Contains the following bits: Nr. Definition: • 0 testFailed • 1 testFailedThisOperationCycle • 6 testNotCompletedThisOperationCycle Compare UDS DTC status bit	723	6
222	exec	Execution Management	862	39
223	Executable	Part of an Application. It consists of executable code (with exactly one entry point) created at integation time that can be deployed and installed on a Machine. An Application may consist of one or more Executables, each of which can be deployed to different Machines.process	721	21
224	Executable	see [2] AUTOSAR Glossary	719	33
225	Executable	see [2] AUTOSAR Glossary	852	18
226	Execution Dependency	Dependencies between Executable instances can be configured to define a sequence for starting and terminating them.	720	22
227	Execution Dependency	Dependencies between Modelled Process instances can be configured to define a sequence for starting and terminating them.	721	21
228	Execution Management	A Functional Cluster. See [2, EXP_SWArchitecture] for an overview.	983	40
229	Execution Management	Functional cluster Execution Management	723	6
230	Execution Management	see [2] AUTOSAR Execution Management	888	43
231	Execution Management	The element of the Adaptive Platform responsible for the ordered startup and shutdown of the Adaptive Platform and the Application.	852	18
232	Execution Management	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	718	31
233	Execution Management	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	719	33
234	Execution Management	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	720	22
235	Execution Management	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	721	21
236	Execution Management	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	909	48
237	Execution Management [3]	The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.	908	44
238	Execution Manifest	Manifest file to configure execution of an Adaptive Application.	908	44
239	Execution Manifest	Manifest file to configure execution of an Adaptive Application. An Execution Manifest is created at integration time and deployed onto a Machine together with the Executable to which it is attached. It supports the integration of the Executable code and describes the configuration properties (startup parameters, resource group assignment etc.) of each process, i.e. started instance of that Executable.	720	22
240	Execution Manifest	Manifest file to configure execution of an Adaptive Application. An Execution Manifest is created at integration time and deployed onto a Machine together with the Executable to which it is attached. It supports the integration of the Executable code and describes the configuration properties (startup parameters, resource group assignment etc.) of each process, i.e. started instance of that Executable.	721	21
241	Execution Manifest	Refers to the Execution Manifest defined in [1].	853	24
242	ExecutionClient	Adaptive Application interface to Execution Management.	720	22
243	ExecutionClient	Adaptive Application interface to Execution Management.	721	21
244	Exernally Requested	A Network Management Message associated to that channel/network/PNC/VLAN has been received. In case of PNC associated means the bit corresponding to this PNC had the value 1.	898	46
245	Explicit Operation Abortion	Immediate abortion of an API call, which is initiated by calling ara::core::Abort, usually as a consequence of the detection of a Violation.	903	9
246	Extended Data Records	Contains statistical data for a DTC. Extended data records are assigned to DTCs and maintained and stored by the DM.	723	6
247	Extended precision format	The IEEE Standard for Floating-Point Arithmetic (IEEE 754) specifies extended precision formats, that are recommended for allowing a greater precision format than that provided by the basic formats. For an extended format the exponent range must be as great as that of the next wider basic format. For instance, 64-bit extended precision binary number must have an “exponent max” of at least 16383, which is equal to “exponent max” of 128- bit binary floating-point. The 80-bit extended format meets this requirement.	839	36
248	Fail-safe reaction	(Sometimes also called "limp home mode"): Reaction to avoid or minimize harm or damage in case of a failure.	723	6
249	FC	Crypto Functional cluster Cryptography. This is the AUTOSAR cluster, which provides all important functionality related to cryptograhic, key management, and certificate handling needs.	883	17
250	FDC	Fault Detection Counter according to 14229-1[1]. Has always the value range from -128 = FDCmin = "FinallyHealed" to +127 = FDCmax = "FinallyDefective"	723	6
251	File	A binary or text file to be stored in a File Storage.	853	24
252	File Name	The file name uniquely identifies a file within a File Storage.	853	24
253	File Storage	A set of files that are stored persistently.	853	24
254	FO	Foundation	782	16
255	Foundation	see [2] AUTOSAR Glossary	719	33
256	FQDN	Fully-Qualified Domain Name	713	53
257	FS	File Storage	853	24
258	FSR	Functional Safety Requirement	885	38
259	Full Determinism	Combination of Time and Data Determinism.	720	22
260	Full Determinism	Combination of Time and Data Determinism. Communication Management	721	21
261	FULL_COM	Communication over the network is possible/allowed, the network is up.	898	46
262	Fully qualified service ID	A fully qualified name of a service used as a system-wide unique identifier, e.g. ’com.someOEM.adas.collisionwarner’.	716	26
263	Function Group	A Function Group is a set of coherent Modelled Processes which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. Modelled Processes can belong to more than one Function Group State (but at exactly one Function Group). "MachineFG" is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.	908	44
264	Function Group	A Function Group is a set of coherent Modelled Processes which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. Modelled Processes can belong to more than one Function Group State (but at exactly one Function Group). "MachineState" is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.	909	48
265	Function Group	A Function Group is a set of coherent Modelled Processes, which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. processes can belong to more than one Function Group State (but at exactly one Function Group). MachineFG is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.	720	22
266	Function Group	A Function Group is a set of coherent Processes, which need to be controlled consistently. Depending on the state of the Function Group, Processes are started or terminated.	852	18
267	Function Group	A Function Group is a set of coherent Processs, which need to be controlled consistently. Depending on the state of the Function Group, Processes are started or terminated.	851	30
268	Function Group	A set of modeled Processes. See Section 12.2 for details.	982	37
269	Function Group	see [3] AUTOSAR State Management	888	43
270	Function Group State	The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States are configured in the Execution Manifest.	721	21
271	Function Group State	The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in Machine Manifest.	720	22
272	Function Group State	The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in the Machine Manifest [3].	909	48
273	Function Group State	The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in the Machine Manifest [8].	908	44
274	Function Group State	The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are deployed as part of the Machine Manifest.	852	18
275	Functional Cluster	see [2] AUTOSAR Glossary	719	33
276	Functional Cluster	see [4] AUTOSAR Glossary	718	31
277	Functional Cluster	A logical group of functionality within the AUTOSAR Adaptive Platform. Functional Clusters are the second level of abstraction in the building block view (cf. Chapter 9). They are also subject of the individual specification documents that make up the AUTOSAR Adaptive Platform standard.	982	37
278	Functional Cluster	A logical group of functionality within the AUTOSAR Adaptive Platform. Functional Clusters are the subject of the individual specification documents that make up the AUTOSAR Adaptive Platform standard. See [2, EXP_SWArchitecture] for an overview of all Functional Clusters in the AUTOSAR Adaptive Platform.	983	40
279	Functional Cluster	Refers to the Functional Cluster defined in [1].	853	24
280	Functional Cluster	see [2] AUTOSAR Glossary	852	18
281	Functional Cluster	The SW functionality of ARA is divided into functional clusters. Functional clusters provide APIs and can communicate with each other.	883	17
282	Fundamental types	C++ built-in types defined in C++ Language Standard [3] in chapter 3.9.1, e.g. char, signed char, unsigned char, int, long long int, wchar_t, bool, float, double, void, std::nullptr_t, etc.	839	36
283	Fusion Unit	A fusion unit within ADI specification is an application executed on an AP processor which combines different sensor information into one environmental model. This includes sensor time synchronization, object tracking, false alarm reduction and accuracy improvement.	913	45
284	gamma	linear recurrent sequence	883	17
285	GCM	Galios/Counter Mode	713	53
286	GCM	Galois Counter Mode - An AEAD operation mode (encryption and authentication) for AES.	883	17
287	GID	Group identifier as used in DoIP	723	6
288	Global Supervision Status	Status that summarizes the Local Supervision Status of all Supervised Entitys of a software subsystem.	851	30
289	Global Supervision Status	Status that summarizes the Local Supervision Status of all Supervised Entities of a software subsystem.	852	18
290	glvalue	A glvalue is an expression whose evaluation determines the identity of an object, bit-field, or function.	839	36
291	GMAC	Galois MAC - A mode of operation for symmetric ciphers (e.g. AES) that supports authentication.	883	17
292	gPTP	Generalized Precision Time Protocol	880	55
293	Grant	During deployment of Adaptive Applications, each Intent requested in the design phase shall be acknowledged. Grant elements are available in the metamodel. Grants will support integrators to review Intents, but it’s not intended to allow partial acceptance of Intent.	706	14
294	Grant	The integrator acknowledges an Adaptive Application’s intent by transferring GrantDesigns to a Grant in deployment. Grant elements may be processed into access control lists forthe PDP implementation.	899	54
295	GroupOfAllDTCs	Identifies a special DTC group that contains all DTCs. This DTC group is identified by the DTC value 0xFFFFFF in 14229-1[1] and contains by default all DTCs of a fault memory. It is present by default in the DM and requires no configuration.	723	6
296	HAD	Highly Automated Driving	885	38
297	Has-a relationship	Composition relationship where one object is a part or member of another object with respect to the rules of ownership.	839	36
298	Health Channel	Channel providing information about the Health Status of a (sub)system. This might be the Global Supervision Status of an application, the result any test routine or the status reported by a (sub)system (e.g. voltage monitoring, OS kernel, ECU status, ...).	851	30
299	Health Channel	Channel providing information about the health status of a (sub)system. This might be the Global Supervision Status of an application, the result any test routine or the status reported by a (sub)system (e.g. voltage monitoring, OS kernel, ECU status, ...).	852	18
300	Health Channel Supervision	Check if the health indicators registered by the supervised software are within the tolerances/limits.	851	30
301	Health Monitoring	Supervision of the software behaviour for correct timing and sequence.	852	18
302	Health Monitoring	Supervision of the software behaviour for correct timing and sequence.	851	30
303	Health Status	A set of states that are relevant to the supervised software (e.g. the Global Supervision Status of an application, a Voltage State, an application state, the result of a RAM monitoring algorithm).	851	30
304	Health Status	A set of states that are relevant to the supervised software (e.g. the Global Supervision Status of an application, a Voltage State, an application state, the result of a RAM monitoring algorithm).	852	18
305	HIC++	High Integrity C++ Coding Standard.	839	36
306	HiL	Hardware in the Loop	911	47
307	HiL	Hardware in the Loop	912	49
308	HiL	Hardware in the Loop	913	45
309	HMAC	Hash-based Message Authentication Code	713	53
310	HMAC	Hashed Message Authentication Code	883	17
311	HSM	Hardware Security Module	885	38
312	HSM	Hardware Security Module - Hardware security module, used to store cryptographic credentials and secure run-time environment	883	17
313	HSM	Hardware Software Module	889	25
314	HTTP	Hypertext Transfer Protocol	876	34
315	HTTP	Hypertext Transport Protocol	713	53
316	HW	Hardware	709	10
317	I/O	Input/Output	968	52
318	iam	Identity and Access Management	862	39
319	IAM	Identity and Access Management	1027	29
320	ID	Identifier	709	10
321	ID	Identifier	713	53
322	Identity	Identity represents properties of an Adaptive Application the access control is decided / enforced upon.	899	54
323	Identity and Access Management (IAM)	A Adaptive Platform Service within the AUTOSAR Adaptive Platform	720	22
324	Identity and Access Management (IAM)	IAM is about managing access rights of an Adaptive Application to interfaces and resources of the Adaptive PlatformFoundation and Services.	899	54
325	idsm	Intrusion Detection System Manager	862	39
326	IETF	Internet Engineering Task Force	883	17
327	IKE	Internet Key Exchange	883	17
328	IKE	Internet Key Exchange protocol	930	32
329	Implicitly-defined copy assignment operator	Implicitly-defined copy assignment operator of a class type (class or struct) performs full member-wise copy assignment of the object’s bases and non-static data members, in their initialization order, using built-in assignment for the scalars and copy assignment operator for class types.	839	36
330	Implicitly-defined copy constructor	Implicitly-defined copy constructor of a class type (class or struct) performs full member-wise copy of the object’s bases and nonstatic data members, in their initialization order, using direct initialization.	839	36
331	Implicitly-defined default constructor	Implicitly-defined default constructor calls default constructors of its base classes and non-static data members. It has exactly the same effect as a user-defined constructor with empty body and empty initializer list.	839	36
332	Implicitly-defined destructor	Implicitly-defined destructor has an empty body. After the body of the destructor is executed, the destructors for all non-static nonvariant data members of the class are called, in reverse order of declaration. Then it calls destructors of all direct non-virtual base classes, in reverse order of construction, and then it calls the destructors of all virtual bases.	839	36
333	Implicitly-defined move assignment operator	Implicitly-defined move assignment operator of a class type (class or struct) performs full member-wise move assignment of the object’s direct bases and immediate non-static data members, in their initialization order, using built-in assignment for the scalars, member-wise move-assignment for arrays, and move assignment operator for class types (called non-virtually).	839	36
334	Implicitly-defined move constructor	Implicitly-defined move constructor of a class type (class or struct) performs full member-wise move of the object’s bases and non-static members, in their initialization order, using direct initialization with an xvalue argument.	839	36
335	Initial Process	A process with management rights, e.g. to determine exit status, for all processes within the AUTOSAR Adaptive Platform.	719	33
336	Instance Specifier	Crypto provider can have more than one instance. To distinguish between instances the spcific instance is addressed with an instance specifier. An instance specifier identifies one instance of a crypto provider.	883	17
337	Integrity	Persistency distinguishes data integrity, which is ensured by the configured redundancy, from structural integrity, i.e. the readability of the structure of a Key-Value Storage or File Storage.	853	24
338	integrity check	verification method proving there has not been any alteration of the artefact content	888	43
339	Intent	A Intent is a property of an Adaptive Application. Access to an AUTOSAR resource is granted if a requesting AA possesses all acknowledged intents that are necessary for that specific AUTOSAR Resource. Intents are assigned to Adaptive Applications within their Application Manifest by means of ComSpecs (e.g. ClientComSpec) and GrantDesigns (e.g. ComFieldGrantDesign).	899	54
340	Intent	An Intent is a property of an Adaptive Application Identity. Access to an AUTOSAR resource (e.g. Service interface) is granted only if a requesting AA possesses all acknowledged Intents that are mandatory for that specific resource. Intents are assigned to AAs within their Application Manifest.	706	14
341	Interface class	An interface class is a class which has following properties: if there are any, all member functions are public pure virtual if there are any, all data members are public static constexpr	839	36
342	Intermediate Identifier (IntID)	An identifier that enables the identification of running POSIX-processes and the mapping to modeled AUTOSAR Processes. The concrete nature of IntID depends on the mechanism that is used to authenticate running POSIX processes.	706	14
343	internal data element	A DiagnosticDataElement which is provided by the DM itself. See also 7.5.4.1.	723	6
344	Internal, External	Classifies if a DiagnosticDataElement is either managed internally inside DM or by an external adaptive applications, see 7.5.4.1 for the precise definition.	723	6
345	Internally Requested	At least one field NetworkRequestedState associated to that channel/network/PNC/VLAN is set to kFullCom.	898	46
346	Internally, Externally	Definition of the support type of a SID by the DM. Internally means processing is done by DM itself, Externally means an external service processor is used.	723	6
347	IP	Internet Protocol	709	10
348	IP	Internet Protocol	713	53
349	IP	Internet Protocol	717	27
350	IP	Internet Protocol	898	46
351	IP	Internet protocol	930	32
352	IPC	Inter Process Communication	846	23
353	IPC	Inter-Process Communication	883	17
354	IPC	Inter-Process Communication	900	20
355	IPsec	Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts the packets of data to provide secure encrypted communication between two computers over an Internet Protocol network.	883	17
356	IPsec	Internet Protocol Security protocol	930	32
357	Is-a relationship	Subsumption relationship between types. If one class B is a subclass of another class A (i.e. B is a more specialized concept than A), then B class specification implies A class specification and a B class object can be used for any expression that requires an A class object.	839	36
358	ISO	International Organization for Standardization	911	47
359	ISO	International Organization for Standardization	912	49
360	ISO	International Organization for Standardization	913	45
361	ISO	International Standardization Organization	713	53
362	IUT	Implementation Under Test	890	13
363	IV	Initialization Vector	883	17
364	Jitter	For a periodically occurring timing event, the jitter is defined as the maximum variation of its period with respect to a predefined standard period.	968	52
365	JSON	JavaScript Object Notation	709	10
366	JSON	JavaScript Object Notation	713	53
367	KDF	Key Derivation Function - A function to derive one or more keys from a secret value.	883	17
368	KEK	Key encryption key - A key that is used to encrypt another key for transportation or storage in an unsecure environment	883	17
369	Key	The key uniquely identifies a key-value pair within a Key- -Value Storage.	853	24
370	Key Material	public keys, private keys, seeds.	883	17
371	Key Slot	Secure storage of key material. Key slots define the access to the stored key material and grant the access only to authorized application or functional cluster.	883	17
372	Key Storage Provider	A structural element that organizes and manages cryptographic keys.	883	17
373	Key-Value Pair	A key with an associated value, to be stored in a Key-Value Storage together with the type of the value.	853	24
374	Key-Value Storage	A set of key-value pairs that are stored persistently.	853	24
375	KSP	Key Storage Provider	883	17
376	KVS	Key-Value Storage	853	24
377	L&T	Acronym for Log and Trace	853	28
378	LAN	Local Area Network	713	53
379	Latency	The latency of a timing event chain describes the time duration between the occurrence of the stimulus and the occurrence of the corresponding response.	968	52
380	LBAP	Language Binding for the Adaptive Platform	994	35
381	LIDAR	LIght Detection And Ranging	911	47
382	LIDAR	LIght Detection And Ranging	912	49
383	LIDAR	LIght Detection And Ranging	913	45
384	Local Supervision Status	Status that represents the current result of Alive Supervision, Deadline Supervision and Logical Supervision of a single Supervised Entity.	851	30
385	log	Log and Trace	862	39
386	Log and Trace	The official Functional Cluster name that manages the logging	853	28
387	Log severity level	Meta information about the severity of a passed logging information	853	28
388	Logging API	The main logging interface towards user applications as a library	853	28
389	Logging back-end	Implementation of the LT protocol, e.g. DLT	853	28
390	Logging Client	An external tool which can remotely interact with the Logging framework	853	28
391	logging context	Log message Log message, including message header(s)	853	28
392	Logging framework	Implementation of the software solution used for logging purposes	853	28
393	Logging instance	The class that enables the logging functionality and handles a single	853	28
394	Logical Network	A network in which devices can be addressed independent from the actual network technology.	898	46
395	Logical Supervision	Kind of online supervision of software that checks if the software ( Supervised Entity or set of Supervised Entities) is executed in the sequence defined by the programmer (by the developed code).	851	30
396	Logical Supervision	Kind of online supervision of software that checks if the software (Supervised Entity or set of Supervised Entities) is executed in the sequence defined by the programmer (by the developed code).	852	18
397	LT protocol	Original name of the protocol itself (Log and Trace), specified in the PRS document [1]	853	28
398	lvalue	An lvalue is a glvalue that is not an xvalue.	839	36
399	MAC	Media Access Control	713	53
400	MAC	Message Authentication Code	713	53
401	MAC	Message Authentication Code - A cryptographic function similar to a hash function. It takes a message of variable length and a secret key as input to generate a hash value, the MAC value. The MAC value is attached to the message to be sent. The receiver of the message can recalculate the MAC value to check if the message is authentic.	883	17
402	Machine	see [2] AUTOSAR Glossary	719	33
403	Machine	see [2] AUTOSAR Glossary	852	18
404	Machine	see [4] AUTOSAR Glossary	718	31
405	Machine Manifest	Manifest file to configure a Machine.	852	18
406	Machine Manifest	Manifest file to configure a Machine. The Machine Manifest holds all configuration information which cannot be assigned to a specific Executable or process.	720	22
407	Machine Manifest	Manifest file to configure a Machine. The Machine Manifest holds all configuration information which cannot be assigned to a specific Executable or process.	721	21
408	Machine Manifest	Manifest file to configure a Machine. The Machine Manifest holds all configuration information which cannot be assigned to a specific Executable or process.	908	44
409	Machine State	A state of Function Group "MachineFG" with some predefined states (Startup/Shutdown/Restart). This can term can refer to the current state ("The Machine State is ..."), to a specific state ("In Machine State Startup ..."), or to a set of states ("In Machine States Startup or Shutdown ...").	721	21
410	Machine State	A state of Function Group "MachineFG" with some predefined states (Startup/Shutdown/Restart). This can term can refer to the current state ("The Machine State is ..."), to a specific state("In Machine State Startup ..."), or to a set of states ("In Machine States Startup or Shutdown ...").	720	22
411	Machine State	The element of the State Management which characterize the current status of the machine. It defines a set of active Applications for any certain situation. The set of Machine States is machine specific and it will be deployed in the Machine Manifest. Machine States are mainly used to control machine lifecycle (startup/shut-down/restart) and platformlevel processes.	852	18
412	Machine State	The state of Function Group "MachineFG" with some predefined states (Startup/Shutdown/Restart).	908	44
413	Machine State	The state of Function Group "MachineState" with some predefined states (Startup/Shutdown/Restart).	909	48
414	MachineFG	see [2] AUTOSAR Execution Management	888	43
415	Manifest	see [2] AUTOSAR Glossary	852	18
416	Maximum interarrival time	Describes the maximum time interval between two consecutive event occurrences. In the more general case, this attribute is an array of the maximum latency between two, three, four, ... event occurrences.	968	52
417	MD	Message Digest	713	53
418	MDF	Module Description File	888	43
419	Memory Management Unit	Hardware element that handles virtual memory, memory translation and caching operations	885	38
420	MetaInfo	Meta-Information in the form of a key-value map, which is given from DM to external service processors.	723	6
421	MGF	Mask Generation Function - A cryptographic function similar to a hash function. It takes a variable length input and an output length l to generate an output of length l. If the input is unknown, the output appears random.	883	17
422	MiL	Model in the Loop	911	47
423	MiL	Model in the Loop	912	49
424	MiL	Model in the Loop	913	45
425	MIME	Multipurpose Internet Mail Extensions	876	34
426	Minimum interarrival time	Describes the minimum time interval between two consecutive event occurrences. In the more general case, this attribute is an array of the minimum latency between two, three, four, ... event occurrences.	968	52
427	MISRA	Motor Industry Software Reliability Association.	839	36
428	Mixed criticality	A system or partition contains, schedules and executes software components like AUTOSAR Adaptive Applications according to different ASIL Levels at the same time	885	38
429	Modelled Process	A Modelled Process is an instance of an Executable to be executed on a Machine and has a 1:1 association with the ARXML/Meta-Model element Modelled Process. This document also uses the term process (without the “modelled” prefix) to refer to the OS concept of a running process.	908	44
430	Modelled Process	A Modelled Process is an instance of an Executable to be executed on a Machine and has a 1:1 association with the ARXML/Meta-Model element Process. This document also uses the term process (without the "modelled" prefix) to refer to the OS concept of a running process.	721	21
431	Modelled Process	A Modelled Process is an instance of an Executable to be executed on a Machine.	720	22
432	Monitor	A monitor (also diagnostic monitor) is a piece of software running within an application, monitoring the correct functionality of a certain system part. The result of such a function check is reported to the DM in form of a diagnostic event.	723	6
433	MTU	Maximum Transmission Unit	713	53
434	MTU	Maximum Transmission Unit	898	46
435	MVCI	Modular Vehicle Communication Interface	888	43
436	n/a	not applicable	862	39
436	-	Operating System Interface	862	39
437	Network Handle	Network Handles are provided by Network Management. A handle represents a set of (partial) networks.	908	44
438	Network Management	A Functional Cluster within the Adaptive Platform Services. Part of Communication Management.	909	48
439	Network Management [5]	A Functional Cluster within the Adaptive Platform Services. Part of Communication Management.	908	44
440	NM	Network Management	709	10
441	NM	Network Management	713	53
442	nm	Network Management	862	39
443	NM	Network Management	898	46
444	NM cluster	Set of NM nodes coordinated with the use of the NM algorithm.	898	46
445	NM message	Refers to the payload transmitted in a packet. It contains the NM User Data, Partial Network Information as well as the Control Bit Vector and the Source Node Identifier.	898	46
446	NM Node	A node that supports network management. Please note that network node, node and NM node are used with the same meaning througout the document.	898	46
447	NM packet	Refers to an Ethernet Frame containing an IP as well as an UDP header in addition to a NM message. Please note that adaptive network management is currently only supported for Ethernet.	898	46
448	NO_COM	Communication over the network is impossible/disabled, the network is down.	898	46
449	Non-reporting Process	A type of Modelled Process with an associated Executable where reportingBehavior set to doesNotReportExecutionState ([TPS_MANI_01279]). A Non-reporting Process is not expected to report its Execution State to Execution Management.	721	21
450	Non-volatile Memory	In the context of DM, Non-volatile Memory refers to the persistent information over the shutdown of the DM process. This does not depend on HW details.	723	6
451	Nonce	A nonce is a random or semi-random number that is generated for cryptographic topics. A nonce can be used as an input to a hash algorithm so that the hash algorithm computes a hash value out of two inputs	883	17
452	NRC	Negative Response Code	890	13
453	NRC	Negative Response Code used by UDS in the diagnostic response to indicate the tester that a certain failure has occurred and the diagnostic request was not processed.	723	6
454	NTP	Network Time Protocol	880	55
455	NV	Non-Volatile	713	53
456	NV	Non-Volatile (memory)	709	10
457	NvM	Non-volatile Memory	885	38
458	OBD	On-Board Diagnostics"; Generally: A vehicles ability for self diagnosis and reporting to external test tools. Specifically here, the protocol is meant, as defined in SAE J1979, ISO 15031, ISO 27145 and others.	723	6
459	OCSP	Online Certificate Status Protocol - Internet protocol used to obtain revocation status of X.509 certificates.	883	17
460	ODR-use	An object is odr-used if its address is taken, or a reference is bound to it. A function is odr-used if a function call to it is made or its address is taken.	839	36
461	OEM	"Original Equipment Manufacturer", but in this document herein, it is used for "Vehicle Manufacturer".	723	6
462	OEM	Original Equipment Manufacturer	709	10
463	OEM	Original Equipment Manufacturer	911	47
464	OEM	Original Equipment Manufacturer	912	49
465	OEM	Original Equipment Manufacturer	913	45
466	One definition rule	The rule states that: There shall be one and only one definition of any variable, function, class type, enumeration type, or template in a translation unit. Some of these may have multiple declarations, but only one definition is allowed. There shall be one and only one definition of every noninline function or variable that is odr-used in the entire program. An inline function definition is required in every translation unit where it is odr-used. There shall be one and only one definition of a class in any translation unit where the class is used in a way that requires it to be complete. There can be more than one definition of any class, enumeration type, inline function with external linkage, class template, non-static function template, static data member of a class template, member function of a class template, partial template specialization in a program, as long as all of the following is true: – each definition consists of the same sequence of tokens (typically, appears in the same header file) – name lookup from within each definition finds the same entities (after overload-resolution), except that constants with internal or no linkage may refer to different objects as long as they are not ODR-used and have the same values in every definition. – overloaded operators, including conversion, allocation, and deallocation functions refer to the same function from each definition (unless referring to one defined within the definition) – the language linkage is the same (e.g. the include file isn’t inside an extern “C” block) – the three rules above apply to every default argument used in each definition – if the definition is for a class with an implicitlydeclared constructor, every translation unit where it is odr-used must call the same constructor for the base and members – if the definition is for a template, then all these requirements apply to both names at the point of definition and dependent names at the point of instantiation If all these requirements are satisfied, the program behaves as if there is only one definition in the entire program. Otherwise, the behavior is undefined.	839	36
467	Operating System	Software responsible for managing Processes on a Machine and for providing an interface to hardware resources.	718	31
468	Operating System	Software responsible for managing Processes on a Machine and for providing an interface to hardware resources.	719	33
469	Operating System	Software responsible for managing processes on a Machine and for providing an interface to hardware resources.	720	22
470	Operating System	Software responsible for managing processes on a Machine and for providing an interface to hardware resources.	721	21
471	Operating System Interface	A Functional Cluster within the Adaptive Platform Foundation.	718	31
472	Operation cycle	A new operation cycle is the start of a new monitoring cycle. This is reflected in a reset of the testFailedThisOperationCycle and testNotCompletedThisOperationCycle bits in the DTC status and optional notification to the monitor to restart the monitoring.	723	6
473	OS	Operating System	709	10
474	OS	Operating System	880	55
475	OS	Operating System	915	56
476	OSI	Open Simulation Interface	911	47
477	OSI	Open Simulation Interface	912	49
478	OSI	Open Simulation Interface	913	45
479	OSI	Operating System Interface	719	33
480	OTA Client	OTA Client is an Adaptive Application in communication with Backend Over The Air	888	43
481	Ownership	Ownership of a resource means that the resource’s lifetime is fully managed by the single class instance or tied with the class instance lifetime. See also: chapter 6.18.5	839	36
482	Pdelay	Propagation/path delay as given in IEEE 802.1AS	880	55
483	PdelayReq	Propagation / path delay request message	880	55
484	PdelayResp	Propagation / path delay response message	880	55
485	PdelayResp FollowUp	Propagation / path delay Follow-Up message	880	55
486	PDID	Periodic Data Identifier according to ISO 14229-1[2].	723	6
487	PDP	Policy Decision Point	900	20
488	PEM	Privacy-Enhanced Mail	883	17
489	PEP	Policy Enforcement Point	900	20
490	per	Persistency	862	39
491	Period	Describes the expected time interval between two consecutive event occurrences, neglecting variation (jitter).	968	52
492	Persistency	The functional cluster described in this document, which handles persistent data of AUTOSAR Adaptive Applications and other functional clusters in File Storages and Key-Value Storages.	853	24
493	Persistent Data	Data that is stored in the persistent memory that can be accessed by one Process. Persistency supports different mechanisms to access data in persistent memory. Concurrent access to the data by several Processes is not supported as the data is owned exclusively by one Process.	853	24
494	PHM	Platform Health Management	709	10
495	PHM	Platform Health Management	713	53
496	PHM	Platform Health Management	851	30
497	PHM	Platform Health Management	852	18
498	phm	Platform Health Management	862	39
499	Physical channel	A channel enabling communication using physical devices, such as I/O ports and cables.	898	46
500	PKCS	Public Key Cryptography Standard.	883	17
501	PKCS	Public Key Cryptography Standards	713	53
502	PKI	Public Key Infrastructure	889	25
503	PKI	Public Key Infrastructure - A system that issues, distributes, and checks digital certificates.	883	17
504	Plaintext	A plaintext is ordinary readable text before being encrypted into ciphertext or after being decrypted.	883	17
505	Platform Health Management	A Functional Cluster within the Adaptive Platform Foundation	720	22
506	Platform Health Management	A Functional Cluster within the Adaptive Platform FoundationRecovery Action	721	21
507	Platform Health Management	A Functional Cluster. See [2, EXP_SWArchitecture] for an overview.	983	40
508	Platform Health Management	Health Monitoring for the Adaptive Platform	852	18
509	Platform Health Management	Health Monitoring for the Adaptive Platform Process A Process is a loaded instance of an executable to be executed on a machine.	851	30
510	Platform Health Management [4]	A Functional Cluster within the Adaptive Platform Foundation	908	44
511	Platform Health Manager	The Platform Health Manager functional cluster performs health monitoring on the AUTOSAR Adaptive Platform	887	42
512	PMIC	Power Management Integrated Circuit	885	38
513	PN	Partial Network	898	46
514	PN communication	Communication during partial network operation	898	46
515	PNI	Partial Network Information	898	46
516	PNL	Partial Network Learning	898	46
517	POD Type	POD (Plain Old Data) type is the type that is compatible with types used in the C programming language, can be manipulated using C library functions, and can be exchanged with C libraries directly in its binary form.	839	36
518	Policy Decision Point	A PDP defines which item (process, application, function) can decide if a requested access to resources may be granted or not.	883	17
519	Policy Decision Point (PDP)	A PDP makes the access control decision. It determines if an Adaptive Application is allowed to perform the requested task by checking the Access Control Policy.	706	14
520	Policy Decision Point (PDP)	The PDP represents the logic in which the access control decision is made. It determines if the application is allowed to perform the requested task.	899	54
521	Policy Enforcement Point (PEP)	A PEP interrupts the control flow during requests from Adaptive Applications by requesting the Access Control Decision from a PDP and enforces this decision.	706	14
522	Policy Enforcement Point (PEP)	The PEP represents the logic in which the Access Control Decision is enforced. It communicates directly with the corresponding PDP to receive the Access Control Decision.	899	54
523	POSIX	Portable Operating System Interface	709	10
524	POSIX	Portable Operating System Interface	713	53
525	POSIX	Portable Operating System Interface	982	37
526	PowerMode	Vehicle basic status information retrieval of DoIP	723	6
527	Primary event memory	The primary event memory is used to store events and event related data. It is typically used by OEMs for after sales purposes, containing information to repair the vehicle.	723	6
528	Process	A process is a loaded instance of an Executable to be executed on a Machine.	852	18
529	Process	A process is a loaded instance of an Executable to be executed on a Machine.	909	48
530	process	A process refers to the OS concept of a running process. Attention: process is not equal to Modelled Process (see below). Hence each Modelled Process has at some time a related (OS) process but a process may not always have a related Modelled Process.	720	22
531	process	A process refers to the OS concept of a running process. Attention: process is not equal to Modelled Process (see below). Hence each Modelled Process has at some time a related (OS) process but a process may not always have a related Modelled Process.	908	44
532	Process	See [1, AUTOSAR Glossary].	983	40
533	Process	see [2] AUTOSAR Glossary	719	33
534	Process	see [4] AUTOSAR Glossary	718	31
535	Process State	Lifecycle state of a Modelled Process	720	22
536	Process State	Lifecycle state of a Modelled Process	721	21
537	prvalue	A prvalue is an expression whose evaluation initializes an object or a bit-field, or computes the value of the operand of an operator.	839	36
538	PSK	Pre-Shared Key	713	53
539	PTP	Precision Time Protocol	880	55
540	QM	Quality Management	885	38
541	QoS	Quality of Service	717	27
542	QoS	Quality of Service	1027	29
543	RA	Registration Authority	883	17
544	RADAR	RAdio Detection And Ranging	911	47
545	RADAR	RAdio Detection And Ranging	912	49
546	RADAR	RAdio Detection And Ranging	913	45
547	Random Number Generator	A program that generates random numbers or pseudo random numbers in a given range.	883	17
548	Rationale	A unique understanding of the term "manifest" is an immediate prerequisite forthe usage of a manifest. Since the term is so prominent on the AUTOSAR adaptive platform it is important to provide a proper definition.	712	51
549	RDF	Root Description File	888	43
550	Real-time application (RTA)	A real-time application is a program that guarantees response within defined time constraints. The latency must be less than a defined value, usually measured in seconds or milliseconds. Whether or not a given application program qualifies as an RTA depends on the worst-case execution time (WCET) - themaximum length of time a defined task requires on a given hardware platform.	839	36
551	Recovery Action	Actions defined by the integrator to control Adaptive Application error recovery.	720	22
552	Redundancy	Redundancy is used by Persistency to ensure the integrity of stored data. It can be configured to use replication of stored data, CRCs, or Hashes. Typically, only replication will allow to repair corrupted data.	853	24
553	Repeat Message	Request Bit Indication	898	46
554	Repeat Message Bit	set in the Control Bit Vector of a received NM message.	898	46
555	Reporting Process	A type of Modelled Process with an associated Executable where reportingBehavior is omitted ([TPS_MANI_01279]) or set to reportsExecutionState. A Reporting Process is expected to report its Execution State to Execution Management.	721	21
556	ResourceGroup	Configuration element to enable restrictions on resources uses by Adaptive Applications running in the group.	720	22
557	Response	End point of an event chain.	968	52
558	REST	Representational State Transfer	876	34
559	RNG	Random Number Generator	883	17
560	ROM	Read-Only Memory	713	53
561	RPC	Remote Procedure Call	717	27
562	RS	Requirement Specification	890	13
563	RSA	Cryptographic approach according to Rivest, Shamir, and Adleman	713	53
564	RSA	Rivest, Shamir, Adleman - RSA is an algorithm for public-key cryptography; It is named after its inventors Ronald L. Rivest, Adi Shamir and Leonard Adleman.	883	17
565	RT	Realtime	846	23
566	RTPS	Real Time Publish Subscribe Protocol	717	27
567	rvalue	An rvalue is an xvalue or a prvalue.	839	36
568	SA	Security Association	930	32
569	SA	SourceAddress of a UDS request	723	6
570	SAE	Society of Automotive Engineers	911	47
571	SAE	Society of Automotive Engineers	912	49
572	SAE	Society of Automotive Engineers	913	45
573	Salt	A salt is a random or semi-random number which is created for passwords. When a password is edited for a user/account also a salt is created for this user/account. A hash algorithm creates a hash value of password and salt. Salts increase the security against brute force password guessing attacks.	883	17
574	Scalar types	The following types are scalar types: integral types floating point types pointers and pointers to members enumerations std::nullptr_t	839	36
575	SD	Service Discovery	709	10
576	SD	Service Discovery	713	53
577	SDG	Special Data Group	713	53
578	SE	Supervised Entity	851	30
579	SE	Supervised Entity	852	18
580	SecOC	AUTOSAR Secure Onboard Communication	982	37
581	SecOC	Secure Onboard Communication	717	27
582	SecOC	Secure Onboard Communication	883	17
583	SecretSeed	A secret value that is used as an initial value to start encryption/decryption.	883	17
584	Self-terminating Process	A type of Modelled Process that has terminationBehavior configured to processIsSelfTerminating. This type of Modelled Process is allowed to self initiate termination procedure (i.e. just terminate with exit status EXIT_SUCCESS), or wait for Execution Management to initiate termination procedure via SIGTERM.	721	21
585	Service Instance	Manifest Manifest file to configure Service usage of an Adaptive Application.	721	21
586	Service Instance Manifest	Manifest file to configure Service usage of an AdaptiveApplication.	720	22
587	Service Interface	Refers to the Service Interface defined in [1].	853	24
588	SG	Safety Goal	885	38
589	SHA	Secure Hash Algorithm	713	53
590	SHA-1	Secure Hash Algorithm (version 1) - Hash functions family.	883	17
591	SHA-2	Secure Hash Algorithm (version 2) - Hash functions family with different hash value length.	883	17
592	SHA-3	Secure Hash Algorithm (version 3) - New hash function generation, faster and more secure as SHA-2.	883	17
593	SHE	Secure Hardware Extension	883	17
594	SHE	Secure Hardware Extension	889	25
595	SI	Service Interface	846	23
596	SID	Service Identifier, identifying a diagnostic service according to UDS, such as 0x14 ClearDiagnosticInformation	723	6
597	Single point of exit	Approach background: IEC 61508 [19], as one of methods for providing modular approach. ISO26262 part 6 [5] with the requirement for ASIL A-D. MISRA-C++ 2008 with the rule M6-6-5. AUTOSAR Coding Guidelines consider that the only reason for such an approach is improving robustness of resource handling, e.g. ensuring that resources are properly released in case of an early exit from the function. However, it is fully ensured by other rules existing in the document that: enforce usage of smart pointers and memory management objects for expressing lifetime semantics (A18-5-2) enforce allocate local objects on stack (A18-5-8) recommend usage of RAII (A15-1-4, A18-5-2) Single point of exit is considered to decrease code readability and will not bring any additional benefits for improving coding standards, thus it is not enforced by the AUTOSAR Coding Guidelines.	839	36
598	sm	State Management	862	39
599	SM	State Manager	890	13
600	Smart Sensor	A Smart Sensor within ADI specification is a sensor which interprets the raw / received data into object descriptions by internal processing. This includes both: sensors which perform processing over time (tracking / object list) and sensors which only provide single timeframe data (discrete / detection list).	913	45
601	Snapshot Record	Set of measurement values stored in the fault memory at a certain point of time during fault detection. It is used to gain environmental data information for occurred faults.	723	6
602	SOA	Service-Oriented Architecture	884	41
603	SoC	Service-Oriented Communication	717	27
604	SoC	System on a Chip	885	38
605	Software Cluster	See [1, AUTOSAR Glossary] and [2, EXP_SWArchitecture].	983	40
606	Software Package	Refers to the Software Package defined in [1].	853	24
607	SoftwareCluster	A SoftwareCluster groups all AUTOSAR artifacts which are relevant to deploy software on a machine. This includes the definition of applications, i.e. their executables, application manifests, communication and diagnostics. In the context of diagnostics a SoftwareCluster can be addressed individually by its own set of diagnostic addresses.	723	6
608	SOME/IP	Scalable service-Oriented MiddlewarE over IP	709	10
609	SOME/IP	Scalable service-Oriented MiddlewarE over IP	713	53
610	SOME/IP	Scalable service-Oriented MiddlewarE over IP	717	27
611	SOP	Start of Production	885	38
612	SourceAddress	A Source Address is used to encode client and server identifiers. In a UDS request the source address encodes the Diagnostic Client whereas the source address in a UDS response encodes the Diagnostic Server.	723	6
613	ST	System Test	890	13
614	Standard-Layout Class	A class that (C++ Language Standard [3], chapter 9): has no non-static data members of type non-standardlayout class (or array of such types) or reference has no virtual functions and no virtual base classes has the same access control for all non-static data members has no non-standard-layout base classes has at most one base class subobject of any given type has all non-static data members and bit-fields in the class and its base classes first declared in the same class has no element of the set M(X) of types as a base class where M(X) is defined as follows: – If X is a non-union class type, the set M(X) is empty if X has no (possibly inherited) non-static data members; otherwise, it consists of the type of the first non-static data member of X (where said member may be an anonymous union), X0, and the elements of M(X0). – If X is a union type, the set M(X) is the union of all M(Ui) and the set containing all Ui, where each Ui is the type of the i-th non-static data member of X. – If X is a non-class type, the set M(X) is empty.	839	36
615	State Management	A Functional Cluster. See [2, EXP_SWArchitecture] for an overview.	983	40
616	State Management	see [3] AUTOSAR State Management	888	43
617	State Management	The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.	720	22
618	State Management	The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.	908	44
619	State Management	The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.	909	48
620	State Management	The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.	721	21
620	Function Group	A Function Group is a set of Modelled Processes which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. Modelled Processes can belong to more than one Function Group State, but at exactly one Function Group (if a Modelled Process were allowed to be running at the same point in time in more than one Function Group then potential contradictions in the logic of the Function Group state transitions could cause errors, see Section 7.5.3). MachineFG is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.	721	21
621	State Management	The element of the Execution Management defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.	852	18
622	StateClient	State Management interface to Execution Management to support Function Group State and Machine State management.	721	21
623	StbM	Synchronized Time Base Manager	880	55
624	Stimulus	Start point of an event chain.	968	52
625	STL	Standard Template Library	983	40
626	Storage	Refers to either a Key-Value Storage or a File Storage. Used in the specification where something applies to all kinds of storages.	853	24
627	Stream Ciphe	r A symmetric encryption that calculates cipher text out of streaming plaintext and the status result of the encryption of previous streamed plaintext. For the first part of encryption a start value is needed as status result.	883	17
628	Supervised Entity	A whole or part of a software component type which is included in the supervision. A Supervised Entity denotes a collection of Checkpoints within the corresponding software component type. A software component type can include zero, one or more Supervised Entities. A Supervised Entity may be instantiated multiple times, in which case each instance is independently supervised.	852	18
629	Supervised Entity	A whole or part of a SwComponentType which is included in the supervision. A Supervised Entity denotes a collection of Checkpoints within the corresponding SwComponentType. A SwComponentType can include zero, one or more Supervised Entities. A Supervised Entity may be instantiated multiple times, in which case each instance is independently supervised.	851	30
630	Supervision Mode	State of a machine or Function Group in which Supervised Entity Instances are to be monitored with a specific set of configuration parameters. Supervision parameters differ from one mode to other as the behavior (timing or sequence) of Supervised Entity changes from one mode to other. Modes are mutually exclusive. A mode can be "Normal", "Degradation".	851	30
631	Supervision Mode	State of a machine or Function Group in which Supervised Entity instances are to be monitored with a specific set of configuration parameters. Supervision parameters differ from one mode to other as the behavior (timing or sequence) of Supervised entity changes from one mode to other. Modes are mutually exclusive. A mode can be "Normal", "Degradation".	852	18
632	Supporting Material	-	712	51
633	SW-C	Software Component	968	52
634	SWC	Software Component	709	10
635	SWC	Software Component	713	53
636	Symmetric Key	In a symmetric encryption the same key (symmetric key) is used to encrypt plaintext into cipher text and to decode cipher text into plain text. A symmetric key is also called secret key because it must be kept secret.	883	17
637	Sync	Time synchronization message (Sync)	880	55
638	Synchronization	Synchronization focuses on the occurrence of different timing events. Synchronization of timing events means that they shall occur simultaneously within a certain tolerance interval.	968	52
639	TA	TargetAddress of a UDS request	723	6
640	TargetAddress	A Target Address is used to encode client and server identifiers. In a UDS request the target address encodes the Diagnostic Server whereas the target address in a UDS response encodes the Diagnostic Client.	723	6
641	TBR	Time Base Resource	880	55
642	TCorrInt	OffsetCorrectionAdaptionInterval	880	55
643	TCP	Transmission Control Protocol	717	27
644	TCP	Transport Control Protocol	709	10
645	TD	Timing Description	968	52
646	Terms	Description	883	17
647	TG	Received value of the Global Time.	880	55
648	TGStart	Current time of the global Time Base Time Master.	880	55
649	TGStop	Current time of the Global Time Base Time Master.	880	55
651	Thread	See [1, AUTOSAR Glossary].	983	40
652	Thread	The smallest sequence of instructions the can be managed independently by a scheduler. Multiple Threads can be executed concurrently within one Process sharing resources suchas memory.	982	37
653	Time Determinism	The results of a calculation are guaranteed to be available before a given deadline.	720	22
654	Time Determinism	The results of a calculation are guaranteed to be available before a given deadline.	721	21
655	Timesync	Time Synchronization (Refers to the action of Synchronizing the Time by means of a time synchronization protocol/bus/messages).	880	55
656	Timing analysis	Timing analysis is a method of determining the timing behavior of the system. This includes consideration of timing relevant system behavior like task preemptions, interrupt handling, resource blocking, etc.	968	52
657	Timing constraint	A timing constraint may have two different interpretation alternatives. On the one hand, it may define a restriction for the timing behavior of the system (e.g. minimum (maximum) latency bound for a certain event sequence). In this case, a timing constraint is a requirement which the system shall fulfill. On the other hand, a timing constraint may define a guarantee for the timing behavior of the system. In this case, the system developer guarantees that the system has a certain behavior with respect to timing (e.g. a timing event is guaranteed to occur periodically with a certain maximum variation).	968	52
658	Timing description	The timing description of a system, subsystem or software component consists of events and event chains. The former one describes events that can be observed and the latter one describe their causal relationship.	968	52
659	Timing event	A timing event is the abstract representation of a specific system behavior – that can be observed at runtime – in the AUTOSAR specification. Timing events are used to define the scope for timing constraints. Depending on the specific scope, the view on the system, and the level of abstraction different types of events are defined.	968	52
660	Timing event chain	A timing event chain describes the causal order for a set of functionally dependent timing events. Each event chain has a well defined stimulus and response, which describe its start and end point. Furthermore, it can be hierarchically decomposed into an arbitrary number of sub-chains, so called ”event chain segments”.	968	52
661	Timing event occurrence	A timing event is said to ”occur”, when a specific system behavior – represented by the timing event – can be observed.	968	52
662	Timing information	Superordinate concept for timing properties and timing constraints.	968	52
663	Timing path	A timing path defines a sequence of communication or computation activities of the system, whose timing behavior shall be examined. Timing paths can be expressed by event chains.	968	52
664	Timing property	A timing property defines the state or value of a timing relevant aispect within the system. Thus, a property does not represent a constraint for the system, but a somehow gathered (e.g. measured, estimated or determined) or defined attribute of the system.	968	52
665	Timing requirement	A timing requirement defines a restriction on timing that shall be fulfilled to ensure proper operation of the system. Timing requirements can be expressed by using timing constraints.	968	52
666	Timing validation	Timing validation compares the result of timing analysis (see glossary entry for timing analysis) with the expected behavior defined by timing constraints (see glossary entry for timing constraints)	968	52
667	TLS	Transport Layer Security	713	53
668	TLS	Transport Layer Security	876	34
669	TLS	Transport Layer Security	982	37
670	TLS	Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network.	883	17
671	TLSync	Value of the local instance of the Time Base before the new value of the Global Time is applied.	880	55
672	TLV	Tag Length Value	709	10
673	TLV	Tag Length Value	713	53
674	TLV	Tag-Length-Value	717	27
675	Tming guarantee	see glossary entry for ”Timing constraint”.	968	52
676	TMR	Triple Modular Redundancy	885	38
677	TOStart	Current corrected time provided by the local instance of the associated Time Base.	880	55
678	TPM	The Trusted Platform Module is defined in [3] and is a secure cryptoprocessor.	883	17
679	TPM	Trusted Platform Module	889	25
680	Transport Protocol Handler	A subcomponent of DM implementing a particular Transport Protocol (either DoIP or any other proprietary UDS Transport Layer).	723	6
681	Transport Protocol Manager	Link between UDS Transport Layer and Application Layer.	723	6
682	Trivially Copyable Class	A class (C++ Language Standard [3], chapter 9): where each copy constructor, move constructor, copy assignment operator, move assigment operator is either deleted or trivial that has at least one non-deleted copy constructor, move constructor, copy assignment operator, or move assignment operator, and that has a trivial, non-deleted destructor	839	36
683	Trusted Platform	An execution platform supporting a continuous chain of trust from boot through to application supporting authentication (that all code executed is from the claimed source) and integrity validation (that prevents tampered code/data from being executed).	720	22
684	Trusted Platform	An execution platform supporting a continuous chain of trust from boot through to application. The trust chain ensures that all execution is both authenticated (that all code executed is from the claimed source) and subjected to integrity validation (that prevents tampered code/data from being executed).	721	21
685	TS	Time Synchronization	880	55
686	TSC	Technical Safety Concept	885	38
687	TSP	A bus specific Time Synchronization Provider.	880	55
688	TSR	Technical Safety Requirement	885	38
689	TSStart	Current corrected time provided by the local instance of the associated Time Base.	880	55
690	TSStop	Current corrected time provided by the local instance of the associated Time Base.	880	55
691	tsync	Time Synchronization	862	39
692	TTL	Time to Live	713	53
693	TTL	Time To Live	717	27
694	TV	Current value of the Virtual Local Time.	880	55
695	TVStart	Current time of the Virtual Local Time of the associated Time Base.	880	55
696	TVStop	Current time of the Virtual Local Time of the associated Time Base.	880	55
697	TVSync	Value of the Virtual Local Time	880	55
698	UCM	Update and Configuration Management	709	10
699	ucm	Update and Configuration Management	862	39
700	UCM	Update and Configuration Management	883	17
701	UCM	Update and Configuration Management	887	42
702	UCM	Update and Configuration Management	888	43
703	UCM Master	UCM Master is distributing packages and coordinating an update campaign in a vehicle	887	42
704	UCM Master	UCM Master is distributing packages and coordinating an update campaign in a vehicle	888	43
705	UDP	User datagram Protocol	709	10
706	UDP	User Datagram Protocol	717	27
707	UDP	User Datagram Protocol	898	46
708	UDS	Unified Diagnostic Services	713	53
709	UDS	Unified Diagnostic Services	723	6
710	UDS	Unified Diagnostic Services (UDS) is a diagnostic communication protocol used in electronic control units (ECUs) within automotive electronics, which is specified in the ISO 14229-1	709	10
711	UDS DTC status bit	UDS DTC status bit as defined in ISO 14229-1[1] Annex D.2; Each single bit position represents and documents a certain status information for the connected DTC. The following eight bits are defined: Nr: Definition: 0 testFailed 1 testFailedThisOperationCycle 2 pendingDTC 3 confirmedDTC 4 testNotCompletedSinceLastClear 5 testFailedSinceLastClear 6 testNotCompletedThisOperationCycle 7 warningIndicatorRequested All eight bits constitute the UDS DTC status byte. Compare Event status	723	6
712	UDS DTC status byte	Bit-packed DTC status information byte as defined in ISO 14229- 1[1], based on DTC level. Contains the UDS DTC status bits.	723	6
713	UDS service	A diagnostic service as defined in ISO 14229-1[1].	723	6
714	UID	Unique Identifier	883	17
715	UML	Unified Modeling Language	709	10
716	UML	Unified Modeling Language	713	53
717	UML	Unified Modeling Language	982	37
718	Undefined Function Group State	Any state of a Function Group, which is not modelled. A Function Group is in an Undefined Function Group State during state transition, if a state transition failed or if an Unexpected Termination or Unexpected Self-termination happened.	721	21
719	Unexpected Self-termination	The event consumed by Execution Management when a Modelled Process terminates without justified reason, for example: - termination without prior request where terminationBehavior is configured to processIsNotSelfTerminating. - termination before reporting kRunning. Please note that every Unexpected Self-termination is also an Unexpected Termination, so requirements for the later apply here as well.	721	21
720	Unexpected Termination	The event consumed by Execution Management when a Modelled Process terminates with exit status other than 0 (EXIT_SUCCESS). Any kind of unhandled signal will result in an Unexpected Termination and thus a non 0 exit status.	721	21
721	Unreachable Code	Unreachable code is code to which there is no syntactic (control flow) path, e.g. a function which is never called, either directly or indirectly.	839	36
722	Update And Configuration Management [7]	A Functional Cluster within the Adaptive Platform Services	908	44
723	URI	Uniform Resource Identifier	713	53
724	URI	Uniform Resource Identifier	1027	29
725	URL	Uniform Resource Locator	713	53
726	Use Case	Readers want to be able to fully grasp the meaning of the AUTOSAR specification	712	51
727	User-defined event memory	The user-defined event/fault memory is used by the UDS service 0x19 with subfunctions 0x17, 0x18 and 0x19. It behaves as the primary event memory but contains data independent from the primary fault memory. It is used to store information that are relevant for different purposes such as warranty or development.	723	6
728	USS	UltraSonic Sensor	911	47
729	USS	UltraSonic Sensor	912	49
730	USS	UltraSonic Sensor	913	45
731	UTC	Coordinated Universal Time	880	55
732	UUID	Universally Unique Identifier	709	10
733	UUID	Universally Unique Identifier	713	53
734	UUID	Universally Unique Identifier, a 128-bit number used to identify information in computer systems	903	9
735	V2X	Vehicle-to-X-Communication is the generic term for various communication technologies in automotive, including vehicle-tovehicle (V2V) and vehicle-to infrastructure (V2I) communication. The information is either transmitted directly between vehicles, between vehicle and roadside infrastructure or by using existing mobile networks	912	49
736	V2X	Vehicle-to-X-Communication is the generic term for various communication technologies in automotive, including vehicle-tovehicle (V2V) and vehicle-to-infrastructure (V2I) communication. The information is either transmitted directly between vehicles, between vehicle and roadside infrastructure or by using existing mobile networks.	911	47
737	Value	A value of a key-value pair stored in a Key-Value Storage.	853	24
738	VCI	Vehicle Communication Interface	888	43
739	Vehicle State Manager	see [1] AUTOSAR Glossary	888	43
740	VFB	Virtual Functional Bus	709	10
741	VFB	Virtual Functional Bus	968	52
742	VIN	Vehicle Identification Number according to ISO-3779	723	6
743	Virtual ECU	A virtual ECU is a logical, almost independent, integration package of an AUTOSAR Adaptive Platform which could be deployed in a well partitioned system, e.g. a virtual machine on top of a hypervisor	885	38
744	VLAN	Virtual Local Area Network	709	10
745	VLAN	Virtual Local Area Network	713	53
746	VSA	Variable Size Array	713	53
747	Watchdog	An external component that supervises execution of the AUTOSAR Adaptive Platform. See [2, EXP_SWArchitecture] for an overview	983	40
748	Watchdog	An external component that supervises execution of the AUTOSAR Adaptive Platform. See Section 7.2.3 for details.	982	37
749	Wdg	Watchdog	885	38
750	WET	Worst Case Execution Time	846	23
751	X.509	Standard for certificates	883	17
752	X.509 Provider	Domain SW for X.509 certificates parsing, verification, storage and search.	883	17
753	XiL	... in the Loop	911	47
754	XiL	... in the Loop	912	49
755	XiL	... in the Loop	913	45
756	XML	Extensible Markup Language	709	10
757	XSD	XML Schema Definition	709	10
758	xvalue	An xvalue refers to an object, usually near the end of its lifetime, so that its resources may be moved.	839	36
759	τroc	Rate for time offset elimination via Rate Adaption.	880	55
760	τrrc	Current rate for correcting the local instance of the Time Base.	880	55

以下の文書には用語定義がなかった。
|714|12|
|857|19|
|881|15|
|929|11|
|883|17|

Reference

Qiita 記事一覧

No: 時中のAUTOSAR 21-11 ()の中の数字。
cat, category：AP:Adaptive Platform(この一覧では全部）
doc. AUTOSAR Document Number.(AUTOSARが決めている文書番号）

No.	title	cat	doc
14	Explanation of Adaptive Platform Design https://qiita.com/kaizen_nagoya/items/6cc08ea21f8222a1be60	AP	706
10	Methodology for Adaptive Platform https://qiita.com/kaizen_nagoya/items/55afa93928fdd0fa859a	AP	709
51	Requirements on Manifest Specification https://qiita.com/kaizen_nagoya/items/8f703113ff94164ef194	AP	712
53	Specification of Manifest https://qiita.com/kaizen_nagoya/items/2bc108cad71bf6bf68ab	AP	713
12	General Requirements specific to Adaptive Platform https://qiita.com/kaizen_nagoya/items/0ac6ccd5a2c6e9b0b430	AP	714
26	Requirements on Communication Management https://qiita.com/kaizen_nagoya/items/0c74e65388f9e07a7cfb	AP	716
27	Specification of Communication Management https://qiita.com/kaizen_nagoya/items/cc8bad08c1602bf6c5cf	AP	717
31	Requirements on Operating System Interface https://qiita.com/kaizen_nagoya/items/3c78bf86a6af2035434b	AP	718
33	Specification of Operating System Interface https://qiita.com/kaizen_nagoya/items/35cd6499df87fea11c92	AP	719
22	Requirements on Execution Management https://qiita.com/kaizen_nagoya/items/4ac2b1e5342a5fdb67c6	AP	720
21	Specification of Execution Management https://qiita.com/kaizen_nagoya/items/9b6b3b571889eea87081	AP	721
6	Specification of Diagnostics https://qiita.com/kaizen_nagoya/items/ed65d04518231c2df96d	AP	723
16	Adaptive Platform Release Overview https://qiita.com/kaizen_nagoya/items/e622ba8f9011344bd04a	AP	782
36	Guidelines for the use of the C++14 language in critical and safety-related systems https://qiita.com/kaizen_nagoya/items/0f95db5caccc178474a8	AP	839
23	Explanation of ara::com API https://qiita.com/kaizen_nagoya/items/c4a9bd8801bdacd895f4	AP	846
30	Specification of Platform Health Management https://qiita.com/kaizen_nagoya/items/2703c294a4287a6dcfec	AP	851
18	Requirements on Platform Health Management https://qiita.com/kaizen_nagoya/items/63de140e7bfb8e5e5727	AP	852
28	Specification of Log and Trace, https://qiita.com/kaizen_nagoya/items/ad9b9f9c625ef399a3f7	AP	853
19	Requirements on Persistency https://qiita.com/kaizen_nagoya/items/8e211bd96f8c2097bc2f	AP	857
24	Specification of Persistency https://qiita.com/kaizen_nagoya/items/548a0b493419221bd76a	AP	858
39	Functional Cluster Shortnames, https://qiita.com/kaizen_nagoya/items/fabab393c4c1939c0fe8	AP	862
50	Specification of Platform Types for Adaptive Platform, https://qiita.com/kaizen_nagoya/items/7c4d76d69be4545e2c2a	AP	875
34	Specification of RESTful Communication https://qiita.com/kaizen_nagoya/items/a73e1397fa438cd687f6	AP	876
55	Specification of Time Synchronization https://qiita.com/kaizen_nagoya/items/9c5e22713d3e4f8cac08	AP	880
15	Requirements on Security Management for Adaptive Platform https://qiita.com/kaizen_nagoya/items/061d431867c23c96d720	AP	881
17	Specification of Cryptography https://qiita.com/kaizen_nagoya/items/7e58e73f15726cf419a8	AP	883
41	Design guidelines for using parallel processing technologies on Adaptive Platform https://qiita.com/kaizen_nagoya/items/6936a202f21592626a57	AP	884
38	Explanation of Safety Overview https://qiita.com/kaizen_nagoya/items/4a6f951701d53113117e	AP	885
42	Requirements on Update and Configuration Management https://qiita.com/kaizen_nagoya/items/fa7ea6891136ef54b5fb	AP	887
43	Specification of Update and Configuration Management https://qiita.com/kaizen_nagoya/items/2306d465f78f0f3e7146	AP	888
25	Requirements on Cryptography https://qiita.com/kaizen_nagoya/items/94fa600ea224cbc11dad	AP	889
13	System Tests of Adaptive Platform https://qiita.com/kaizen_nagoya/items/2cc07c418ad591f27dfe	AP	890
46	Specification of Network Management https://qiita.com/kaizen_nagoya/items/ed8e77462e9f5d9048e9	AP	898
54	Requirements on Identity and Access Management　https://qiita.com/kaizen_nagoya/items/3ed7e26481f6bce61f22	AP	899
20	Specification of Identity and Access Management https://qiita.com/kaizen_nagoya/items/23eee760e9ce0a8b324f	AP	900
9	Specification of Adaptive Platform Core https://qiita.com/kaizen_nagoya/items/0f024ee264e34e5298a3	AP	903
44	Specification of State Management https://qiita.com/kaizen_nagoya/items/0800a8b906b04172d855	AP	908
48	Requirements of State Management https://qiita.com/kaizen_nagoya/items/2bd613be97276955e93a	AP	909
47	Requirements on Automated Driving Interfaces https://qiita.com/kaizen_nagoya/items/6676a4bcc1aaf212f2f0	AP	911
49	Specification of Sensor Interfaces https://qiita.com/kaizen_nagoya/items/d7a0f4bae5a2a2da81df	AP	912
45	Explanation of Sensor Interfaces https://qiita.com/kaizen_nagoya/items/d6e8aa21d69f79361d4c	AP	913
56	Requirements on Debugging, Tracing and Profiling support of AUTOSAR Components https://qiita.com/kaizen_nagoya/items/ab83aaad7e81dc46ee52	AP	915
11	Guidelines for using Adaptive Platform interfaces https://qiita.com/kaizen_nagoya/items/b36df3471ea917d7cdeb	AP	929
32	Explanation of IPsec Implementation Guidelines, https://qiita.com/kaizen_nagoya/items/3aa7b7eda7b3be58d449	AP	930
52	Specification of Timing Extension for Adaptive Platform https://qiita.com/kaizen_nagoya/items/2d137544fa954612b5d4	AP	968
37	Explanation of Adaptive Platform Software Architecture https://qiita.com/kaizen_nagoya/items/ffa6c487e1fd838ff9a4	AP	982
40	Explanation of Adaptive Platform Software Architectural Decisions https://qiita.com/kaizen_nagoya/items/8b4a644f990dcd1d6ba9	AP	983
35	Specification of Language Binding for modeled AP data types https://qiita.com/kaizen_nagoya/items/b349673e404ff4a6ac02	AP	994
29	Integration of DDS Security https://qiita.com/kaizen_nagoya/items/41f74447e21a76fe0538	AP	1027

英日単語帳。

各文書では１００まで、ここでは1000まで記録。
日本語は仮訳。一部、単語分解前。１週間くらいで修正予定。

no.	count	word	日本語
1	66262	the	その
2	43681	of	の
3	26046	a	一つの
4	25286	to	に
5	16651	in	中に
6	16235	is	です
7	15927	and	と
8	13429	for	にとって
9	12978	ara	アラ
10	11239	autosar	autosar
11	10581	be	です
12	10358	service	奉仕
13	10042	c	c
14	9401	data	与件
15	9013	this	これ
16	8878	type	型
17	8716	shall	しなければならない
18	8523	draft	原案
19	8079	id	id
20	7071	by	に
21	6977	class	級
22	6798	document	文書
23	6763	sws_cm_	sws_cm_
24	6742	that	それ
25	6593	ap	ap
26	6544	specification	仕様
27	6458	interface	界面
28	6358	an	一つの
29	6302	value	値
30	6265	r	r
31	6200	platform	土台
32	6001	management	管理
33	5610	function	関数
34	5466	crypto	暗号
35	5443	or	または
36	5289	not	いいえ
37	5260	description	説明
38	5175	with	と
39	5136	atp	atp
40	5125	adaptive	適応
41	5076	instance	実例
42	4981	on	の上
43	4896	d	d
44	4776	sws_dm_	sws_dm_
45	4651	if	もし
46	4614	element	要素
47	4452	e	e
48	4449	are	です
49	4447	state	州
50	4426	as	なので
51	4304	event	行事
52	4299	software	ソフトウェア
53	4295	diagnostic	診断
54	4244	status	状態
55	4200	name	名前
56	4187	no	いいえ
57	4175	file	紙ばさみ
58	4165	error	誤り
59	4152	core	芯
60	4102	from	から
61	4101	application	応用
62	4068	x	x
63	3915	std	standard(短縮名)
64	3740	implementation	実装
65	3612	kind	親切
66	3609	time	時間
67	3605	return	戻る
68	3579	key	鍵
69	3535	communication	通信
70	3421	tags	札
71	3332	header	見出し
72	3303	rs_cm_	rs_cm_
73	3278	package	小包
74	3267	rest	残り
75	3252	it	それ
76	3252	note	覚書
77	3220	object	物
78	3173	process	処理する
79	3049	used	使用済み
80	3012	some	いくつかの
81	2907	attribute	属性
82	2887	use	使用する
83	2854	port	港
84	2792	prototype	ひな形
85	2746	tps_mani_	tps_mani_
86	2720	method	方法
87	2698	except	除く
88	2671	which	どれの
89	2646	defined	定義済み
90	2636	set	設定する
91	2618	rs_ap_	rs_ap_
92	2610	include	含む
93	2600	safety	安全性
94	2578	table	表
95	2569	system	系
96	2555	scope	範囲
97	2528	const	constant(短縮名)
98	2522	ip	ip
99	2517	h	h
100	2510	com	communication(短縮名)
101	2477	can	できる
102	2415	syntax	構文
103	2385	domain	領域
104	2295	configuration	構成
105	2289	base	基づく
106	2256	m	m
107	2256	message	伝言
108	2255	manifest	管理票
109	2246	code	符号
110	2246	design	設計
111	2245	symbol	像
112	2237	sws_core_	sws_core_
113	2223	execution	実行
114	2213	has	もつ
115	2185	sws_per_	sws_per_
116	2148	reference	参照
117	2129	see	見る
118	2126	only	だけ
119	2126	result	結果
120	2118	sws_adi_	sws_adi_
121	2115	sws_rest_	sws_rest_
122	2109	mapping	対応付け
123	2049	request	要求
124	2029	cluster	房
125	1989	all	すべて
126	1987	machine	機械
127	1973	group	班
128	1952	ar	AUTOSAR(短縮名)
129	1946	types	型
130	1936	storage	記録
131	1890	sws_crypt_	sws_crypt_
132	1880	_t	_t
133	1875	provided	提供した
134	1862	rs_adi_	rs_adi_
135	1836	case	場合
136	1814	client	顧客
137	1813	persistency	永続性
138	1802	required	必要
139	1779	cpp	c plus plus(短縮名)
140	1775	referrable	参照可能
141	1741	context	文脈
142	1741	sw	software(短縮名)
143	1717	server	奉仕者
144	1705	exception	例外
145	1702	update	更新
146	1701	one	1
147	1699	string	文字列
148	1695	step	段階
149	1692	diag	diag
150	1685	interfaces	界面
151	1668	information	情報
152	1638	according	によると
153	1616	specific	明確
154	1608	deployment	展開
155	1587	other	他の
156	1560	attr	attribute(短縮名)
157	1520	ref	reference(短縮名)
158	1514	field	分野
159	1513	using	使って
160	1512	support	対応
161	1504	operator	操作者
162	1496	will	意思
163	1471	at	で
164	1468	represents	表す
165	1461	non	非
166	1459	number	番号
167	1454	space	空間
168	1437	definition	意味
169	1436	release	開放
170	1425	void	空所
171	1424	ecu	ecu
172	1424	guidelines	指針
173	1423	access	接続
174	1400	call	電話
175	1390	tester	試験器
176	1379	may	かもしれない
177	1378	ucm	ucm
178	1373	any	どれか
179	1367	t	t
180	1366	template	雛形
181	1361	network	通信網
182	1352	get	得る
183	1340	sensor	感知器
184	1331	identifier	識別子
185	1324	constr_	constr_
186	1319	rs_crypto_	rs_crypto_
187	1316	b	b
188	1315	related	関連している
189	1311	sws_ucm_	sws_ucm_
190	1304	meta	超
191	1302	integer	整数
192	1297	parameters	引数
193	1292	health	健康
194	1269	int	integer(短縮名)
195	1267	positive	肯定的
196	1264	dds	dds
197	1258	figure	形
198	1255	rule	規則
199	1255	usage	利用方法
200	1234	point	点
201	1233	identifiable	識別可能
202	1228	templates	雛形
203	1224	level	水準
204	1224	uint	unsigned integer(短縮名)
205	1221	compliant	準拠
206	1217	rs_main_	rs_main_
207	1201	api	api
208	1198	functional	機能的
209	1191	mult	複数の
210	1190	log	記録
211	1188	size	大きさ
212	1180	requirements	要件
213	1177	same	同じ
214	1176	rs_diag_	rs_diag_
215	1168	also	また
216	1164	iso	iso
217	1162	trace	跡
218	1157	between	の間に
219	1151	uds	uds
220	1141	thread	より糸
221	1138	binding	縛り
222	1133	based	基づく
223	1122	provide	提供
224	1118	security	あんしん
225	1106	different	違う
226	1086	its	これは
227	1078	timing	時期
228	1077	defines	定義する
229	1075	array	配列
230	1075	version	版
231	1073	response	応答
232	1067	have	持つ
233	1063	s	s
234	1054	i	私
235	1053	check	検査する
236	1051	mode	状態
237	1038	memory	記憶装置
238	1032	cryp	暗号
239	1032	then	それから
240	1030	applications	応用
241	1027	should	したほうがいい
242	1027	sws_em_	sws_em_
243	1019	when	いつ
244	1018	k	k
245	1013	props	props
246	1011	g	g
247	1010	component	成分
248	1005	ogm	ogm
249	999	language	言語
250	975	example	例
251	975	processing	処理
252	974	define	定義
253	962	test	試験
254	958	elements	要素
255	956	end	終わり
256	955	category	分類
257	953	supervision	監督
258	943	default	既定値
259	941	operation	手術
260	940	vehicle	車両
261	932	read	読む
262	931	each	各
263	927	public	公衆
264	923	rs_mani_	rs_mani_
265	921	optional	選択肢
266	920	protocol	規約
267	917	abstract	概要
268	914	new	新着
269	907	configured	構成済み
270	898	autosar_tps_manifest	autosar_tps_manifest
271	898	called	呼ぶ
272	896	stream	流れ
273	895	errors	誤り
274	883	provider	提供者
275	871	TRUE	真
276	862	parameter	引数
277	858	multilanguage	多言語
278	851	events	行事
279	850	following	続く
280	847	does	する
281	846	within	以内に
282	844	uri	uri
283	835	values	値
284	834	handler	扱う者
285	834	role	役割
286	834	specified	指定
287	833	derived	派生
288	832	current	現在
289	823	model	模型
290	821	but	しかし
291	819	aggr	aggregate(短縮名)
292	815	structure	構造
293	809	vector	方向と長さ
294	808	enumeration	列挙
295	802	part	部
296	800	signal	信号
297	798	instances	実例
298	798	raw	生
299	798	semantics	意味
300	796	via	経由
301	794	standard	標準
302	793	been	その間
303	792	address	住所
304	792	member	要員
305	792	short	短い
306	791	f	f
307	790	per	あたり
308	786	start	始める
309	785	channel	溝
310	784	length	長さ
311	778	virtual	仮想
312	775	behavior	行動
313	775	there	そこの
314	773	app	application(短縮名)
315	773	control	制御
316	772	offset	補正
317	770	where	どこ
318	765	describes	説明する
319	758	allowed	許可した
320	756	received	受け取った
321	753	future	将来
322	750	change	変化する
323	747	provides	提供する
324	746	such	そのような
325	740	order	注文
326	738	executable	実行可能
327	737	transport	輸送
328	734	after	後
329	730	handling	取り扱い
330	730	systems	系
331	729	certificate	証明書
332	728	trigger	引き金
333	723	differences	違い
334	722	tables	票
335	721	means	意味
336	720	dtc	dtc
337	720	given	所与の
338	715	argument	口論
339	714	negative	否定
340	711	sequence	順序
341	703	messages	伝言
342	696	pointer	指示子
343	696	up	上
344	695	referenced	参照
345	693	supported	対応した
346	692	corresponding	よる
347	692	FALSE	偽
348	688	processes	過程
349	688	rationale	根拠
350	687	diagnostics	診断
351	684	was	だった
352	683	master	主人
353	677	handle	扱う
354	675	contains	含む
355	672	functions	関数
356	671	available	利用可能
357	671	out	外
358	668	rs_ucm_	rs_ucm_
359	667	section	節
360	662	constructor	構築子
361	662	down	下
362	661	bit	少し
363	655	over	以上
364	653	variable	変数
365	650	work	仕事
366	647	chapter	章
367	644	errc	errc
368	643	these	これらは
369	642	into	の中へ
370	638	more	もっと
371	636	exceptions	例外
372	632	dif	dif
373	632	user	利用者
374	631	byte	束
375	630	changed	かわった
376	629	returned	戻ってきた
377	628	transformation	変身
378	623	during	その間
379	621	algorithm	算法
380	621	bool	論理値
381	621	ip_	ip_
382	621	param	引数
383	620	without	それなしに
384	617	secure	安全
385	615	possible	可能
386	614	added	追加した
387	611	methodology	方法論
388	611	range	範囲
389	609	input	入力
390	609	material	材料
391	608	none	無し
392	606	blue	青
393	604	common	一般
394	604	dependencies	依存関係
395	603	specifier	指定子
396	597	architecture	建築
397	597	critical	致命的
398	596	xml	xml
399	593	cmapp	cmapp
400	589	send	送信
401	587	ability	能力
402	586	dm	dm
403	583	content	内容
404	583	ctx	ctx
405	581	diagudsnrcerror	diagudsnrcerror
406	580	two	2
407	571	explanation	説明
408	568	small	小さい
409	567	constraints	制約
410	566	clusters	房
411	566	than	よりも
412	564	internal	内部
413	562	diagudsnrc	diagudsnrc
414	561	confidential	信頼
415	560	resource	資源
416	558	global	広範囲
417	549	deterministic	決定論的
418	548	synchronization	同期
419	547	cryptography	暗号化
420	540	methods	方法
421	540	view	見る
422	536	packageable	パッケージ化可能
423	532	boolean	論理値
424	532	tests	試験
425	529	services	奉仕
426	527	collectable	収集可能
427	524	allocator	配置子
428	523	side	側
429	515	autosar_sws_communication	autosar_sws_communication
430	515	entity	実在物
431	513	do	行う
432	513	rs_per_	rs_per_
433	512	autosar_rs_cpp	autosar_rs_cpp
434	510	automated	自動化
435	510	recommended	おすすめ
436	510	safe	安全な
437	509	local	地域
438	506	startup	起動
439	505	n	n
440	502	translation	翻訳
441	499	block	塊
442	499	ipservice	ipservice
443	497	authentication	認証
444	495	subscription	購読
445	492	tcp	tcp
446	490	stereo	ステレオ
447	486	container	容器
448	484	autosar_sws_diagnostics	autosar_sws_diagnostics
449	483	multiple	多数
450	483	p	p
451	483	transfer	移行
452	480	whether	どうにか
453	479	module	部品
454	479	therefore	したがって
455	477	associated	関連する
456	477	back	戻る
457	477	payload	負荷
458	475	isignal	isignal
459	475	unique	個性的
460	471	reset	再設定
461	470	stack	山積み
462	469	alg	alg
463	469	before	前
464	467	declaration	宣言
465	467	list	一覧
466	466	cycle	サイクル
467	465	connection	繋がり
468	465	session	session
469	462	either	また
470	462	how	どうやって
471	462	requested	要求された
472	462	their	それらの
473	462	z	z
474	459	general	全般的
475	457	conditions	条件
476	454	discovery	発見
477	454	target	目標
478	453	both	両方とも
479	453	single	独身
480	452	needs	必要
481	451	create	作成
482	450	exec	exec
483	449	static	静的
484	448	objects	物
485	446	assignment	割り当て
486	446	described	説明された
487	446	existence	存在
488	445	contained	含まれています
489	444	offer	依頼
490	443	copy	複写
491	442	created	作成した
492	441	stored	保存
493	441	v	v
494	440	operating	操作
495	439	counter	計数器
496	438	applicable	該当する
497	438	specifies	指定する
498	436	move	動く
499	435	config	構成
500	434	transmission	伝送
501	433	autosar_tr_adaptive	autosar_tr_adaptive
502	433	modeling	模型化
503	433	struct	structure(短縮名)
504	430	format	書式
505	427	invalid	無効
506	423	supervised	監督
507	422	could	だろう
508	422	dtable	dtable
509	422	emoapp	emoapp
510	422	manager	管理者
511	422	references	参照
512	422	tr_ameth_	tr_ameth_
513	421	failed	失敗した
514	419	changes	変更
515	419	output	出力
516	417	heading	見出し
517	416	cases	場合
518	416	map	地図
519	416	overview	概要
520	415	private	個人的
521	415	re	再
522	414	signature	署名
523	408	condition	調子
524	407	enum	列挙型
525	407	ethernet	イーサネット
526	407	functionality	機能性
527	407	need	必要
528	407	proxy	プロキシー
529	405	allows	許可します
530	405	literal	リテラル
531	401	rs_some	rs_some
532	399	attributes	属性
533	399	triggering	トリガー
534	399	valid	有効
535	398	runtime	実行時
536	396	activation	活性化
537	396	source	源
538	395	returns	戻り値
539	394	please	お願いします
540	392	atpvariation	atpvariation
541	392	supporting	対応
542	392	synchronized	同期
543	391	rules	規則
544	389	purpose	目的
545	387	because	なぜなら
546	387	sws_ts_	sws_ts_
547	385	find	探す
548	383	initialization	初期化
549	382	notification	お知らせ
550	382	packages	小包
551	381	variant	変異体
552	380	first	最初
553	380	they	彼ら
554	378	constraint	制約
555	377	classic	古典
556	377	serialization	シリアル化
557	375	correction	修正
558	375	protected	保護
559	375	span	間隔
560	374	classes	級
561	373	custom	習慣
562	372	udp	udp
563	371	limit	制限
564	371	receive	受け取る
565	370	requirement	要件
566	370	transition	遷移
567	369	index	索引
568	368	slot	枠
569	366	standardized	標準化
570	366	sws_phm_	sws_phm_
571	365	about	約
572	365	ipv	ipv
573	365	like	お気に入り
574	363	node	節点
575	363	operations	操作
576	362	reply	返事
577	362	text	文章
578	361	bytes	束
579	361	make	作る
580	361	write	書きます
581	360	nm	network management(短縮名)
582	360	underlying	基礎となる
583	359	autosar_sws_cryptography	autosar_sws_cryptography
584	358	another	別
585	358	rport	rport
586	356	files	紙ばさみ
587	354	checks	検査
588	354	phm	phm
589	354	requests	要求
590	354	rs_em_	rs_em_
591	353	states	状態
592	352	alias	別名
593	351	shut	閉める
594	350	fields	田畑
595	350	symmetric	対称
596	347	deleted	削除
597	347	interaction	相互作用
598	347	main	主要
599	346	keys	鍵
600	345	history	歴史
601	345	sub	副（接頭語）
602	342	already	すでに
603	341	calls	呼び出し
604	341	maximum	最大
605	341	splitable	分割可能
606	340	properties	特徴
607	339	rs_phm_	rs_phm_
608	339	topic	話題
609	338	equal	同等
610	338	layer	層
611	337	primitive	原生的
612	337	serialized	シリアル化
613	336	arguments	引数
614	335	components	部品
615	335	notifier	通知者
616	335	timevalue	時間値
617	334	aggregation	集約
618	334	further	さらに遠く
619	333	y	y
620	332	size_t	size_t
621	331	might	そうかもしれない
622	331	respective	それぞれ
623	330	position	位置
624	328	delete	消去
625	328	environment	環境
626	328	remote	遠隔
627	328	way	仕方
628	327	generated	生成した
629	327	mapped	対応付けた
630	324	parent	親
631	324	shared	共有
632	324	specify	特定
633	323	library	図書館
634	323	resources	資力
635	323	several	いくつかの
636	323	so	それで
637	321	path	道
638	321	timeout	時間切れ
639	320	origin	元
640	319	driving	運転
641	318	mechanism	機構
642	318	subscribe	申し込む
643	317	additional	追加
644	317	rejected	拒否されました
645	317	verification	検証
646	316	monitor	監視
647	315	cannot	できません
648	315	collection	収集
649	315	dependency	依存
650	315	detection	検出
651	315	hardware	ハードウェア
652	315	rhs	rhs
653	315	running	実行中
654	314	least	少しでも
655	313	buffer	緩衝器
656	309	av	av
657	307	atptype	atptype
658	307	passed	合格した
659	306	active	活動的
660	306	connector	接続器
661	306	iterator	繰り返し
662	304	persistent	持続的
663	304	typed	入力した
664	303	hash	ハッシュ
665	303	tsync	tsync
666	300	printable	印刷可能
667	298	able	できる
668	298	prs_some	prs_some
669	298	well	良い
670	297	extension	拡大
671	297	print	印刷
672	296	encryption	暗号化
673	296	physical	物理的
674	295	reporting	報告
675	295	settings	設定
676	295	uploadable	アップロード可能
677	294	action	行動
678	294	constexpr	constexpr
679	294	policy	政策
680	293	conversation	会話
681	293	updated	更新しました
682	291	restful	安らかな
683	289	lhs	lhs
684	289	sending	送信
685	288	failure	失敗
686	288	implemented	実装
687	287	extensions	拡張機能
688	286	initial	最初の
689	286	throw	投げる
690	284	contain	含む
691	284	must	しなければならない
692	284	record	記録
693	284	sent	送信済
694	281	sws_sm_	sws_sm_
695	280	priority	優先度
696	279	groups	班
697	279	misra	ミスラ
698	279	particular	特に
699	278	criteria	基準
700	278	would	だろう
701	276	directly	直接
702	275	fibex	fibex
703	274	cipher	暗号
704	274	pattern	類型
705	274	uuid	uuid
706	273	currently	現在
707	273	exist	存在
708	273	feature	特徴
709	273	form	形
710	273	identical	同一
711	272	cryptographic	暗号
712	271	cancellation	取り消し
713	271	creation	作成
714	271	task	仕事
715	270	expression	表現
716	270	pdu	pdu
717	270	technology	技術
718	269	aggregated	集約
719	269	float	浮く
720	269	setting	設定
721	268	recovery	回復
722	268	started	始めた
723	268	u	u
724	267	clear	消す
725	267	ipdu	ipdu
726	267	protection	保護
727	266	direction	方向
728	266	executed	実行
729	265	accessor	飾り
730	265	identifies	識別します
731	264	processed	処理済み
732	264	rs_ts_	rs_ts_
733	264	seed	タネ
734	263	done	終わり
735	263	ensure	確認
736	263	explicit	明示的
737	263	reported	報告
738	263	tls	tls
739	262	details	詳細
740	262	expected	期待した
741	262	orientation	方向付け
742	261	external	外部の
743	261	initialized	初期化
744	261	otherwise	そうでなければ
745	260	considered	考慮
746	260	uds_transport	uds_transport
747	260	wait	待つ
748	260	while	その間
749	259	autosar_sws_adaptive	autosar_sws_adaptive
750	259	every	毎日
751	258	grant	許す
752	258	steps	手順
753	258	subclasses	部分分類
754	258	udstransport	udstransport
755	257	approach	接近
756	257	run	走る
757	256	actual	実際
758	255	allow	許可する
759	255	enable	有効
760	255	subelements	部分要素
761	254	existing	既存762
763	252	significant	重要
764	250	last	過去
765	250	pre	前（接頭辞）
766	250	representation	表現
767	249	skeleton	骨組み
768	249	sws_log_	sws_log_
769	249	vendor	提供者
770	247	major	選考科目
771	247	needed	必要
772	246	autosar_sws_restfulcommunication	autosar_sws_restfulcommunication
773	246	implement	埋め込む
774	246	place	場所
775	246	through	終えた
776	245	metainfo	metainfo
777	245	necessary	必要
778	245	unique_ptr	unique_ptr
779	244	assigned	割り当てられた
780	244	builder	構築者
781	244	relevant	関連する
782	243	development	発達
783	243	latest	最新
784	242	modeled	模型化
785	242	yet	まだ
786	241	identity	身元
787	241	refer	参照
788	240	_	_
789	240	enclosing	同封
790	240	however	でも
791	240	query	クエリ
792	239	binary	二進
793	239	glossary	用語集
794	239	ordered	順序付けた
795	238	max	最大
796	238	verify	確認
797	237	describe	説明
798	237	requires	必要
799	237	since	以来
800	236	minor	小さな
801	236	monitoring	監視
802	236	ts	ts
803	235	integrity	威厳
804	235	root	根
805	235	swc	software component(短縮名)
806	233	basic	基本
807	233	connected	接続してる
808	233	relation	関係
809	233	supports	対応
810	232	classifier	分類子
811	232	frame	枠
812	232	names	名前
813	232	promise	約束
814	232	satisfied	満足
815	230	comparison	比較
816	230	identification	身元
817	229	dynamic	動的
818	229	extended	拡張
819	229	io	io
820	229	strategy	戦略
821	228	below	下
822	227	reception	受信
823	227	stop	止まる
824	224	chain	鎖
825	224	declared	宣言
826	224	destructor	解体子
827	224	extract	抽出する
828	224	logging	記録
829	224	right	右
830	224	variation	変化
831	223	affected	影響を受ける
832	223	concrete	硬い
833	223	configure	構成、設定
834	223	multicast	多投影
835	222	final	最後の
836	222	parallel	平行
837	221	calling	呼び出し
838	221	empty	空
839	221	next	次
840	219	filter	濾紙
841	219	generic	汎用的
842	219	including	含む
843	219	itself	自体
844	219	perform	実行
845	218	always	いつも
846	218	fire	火
847	218	inside	中身
848	217	rate	比率
849	216	performed	実行
850	215	socket	ソケット
851	214	item	項目
852	213	vh	vh
853	212	applied	適用
854	212	containing	含む
855	212	operators	操作者
856	212	scale	規模
857	211	due	期限
858	211	region	領域
859	210	pair	対
860	210	random	無作為
861	210	restriction	制限
862	209	endpoint	終点
863	209	sdg	sdg
864	208	uptr	uptr
865	207	campaign	運動
866	207	prototypes	ひな形
867	207	registered	登録済み
868	207	split	裂く
869	207	thus	したがって
870	206	dependent	依存
871	206	integration	統合
872	205	documentation	文書化
873	205	mem	mem
874	205	most	多くの
875	204	being	であること
876	204	open	開いた
877	204	sample	例
878	203	coding	符号化
879	202	property	財産
880	201	atpuridef	atpuridef
881	201	report	報告する
882	200	ecus	ecus
883	200	pass	通過する
884	199	consumer	消費者
885	199	ipsec	ipsec
886	198	removed	削除した
887	197	autosar_sws_sensor	autosar_sws_sensor
888	197	cp	classic platform(短縮名)
889	197	volatile	揮発性
890	196	refers	参照
891	196	successful	成功
892	195	apis	apis
893	195	applies	適用されます
894	195	explicitly	明示的に
895	195	fails	失敗する
896	195	fn	fn
897	195	secret	秘密の
898	194	clients	濃きゃう
899	194	generation	世代
900	194	logical	論理的
901	194	take	取った
902	193	apply	申し込み
903	192	high	高い
904	191	depending	依存する
905	191	secoc	secoc
906	191	uses	使用
907	190	bits	binary digits(短縮名)
908	190	members	要員
909	190	unit	単位
910	190	updates	更新
911	189	smart	頭いい
912	188	compare	比較
913	188	redundancy	冗長性
914	188	validation	検証
915	187	cmservice	cmservice
916	187	da	da
917	187	forget	忘れる
918	187	instanceid	instanceid
919	187	providing	提供する
920	187	tps_timex_	tps_timex_
921	186	linear	線形
922	186	mechanisms	仕組み
923	185	minimum	最小
924	185	occurrence	発生
925	184	independent	独立
926	184	you	君
927	183	less	以下
928	183	ptr	ptr
929	183	subfunction	副機能
930	182	certain	特定
931	182	doip	doip
932	182	keyslot	keyslot
933	182	sws_lbap_	sws_lbap_
934	182	worker	労働者
935	181	daemon	守護神
936	181	os	os
937	181	undefined	未定義
938	180	real	本物
939	180	termination	終了
940	178	points	点
941	178	project	事業
942	178	sws_anm_	sws_anm_
943	178	timer	計時器
944	177	includes	含む
945	177	indicates	を示します
946	177	option	選択肢
947	177	routine	経路
948	177	stopoffer	stopoffer
949	177	terms	条項
950	176	aapapi	aapapi
951	176	def	def
952	176	dfor	dfor
953	175	add	追加
954	175	autosar_exp_swarchitecture	autosar_exp_swarchitecture
955	175	modelled	模型化
956	175	results	結果
957	174	mentioned	言及した
958	174	responsible	責任者
959	174	scheduling	予定
960	173	cstdint	cstdint
961	173	store	お店
962	172	brief	簡単に
963	172	we	私たち
964	171	match	合う
965	170	auto	自動
966	170	autosar_sws_execution	autosar_sws_execution
967	170	char	char
968	170	taken	とった
969	170	them	それら
970	169	allocation	割り当て
971	169	intended	意図した
972	169	load	負う
973	169	logger	記録器
974	169	participant	参加者
975	169	subject	主題
976	168	autosar_sws_persistency	autosar_sws_persistency
977	168	bus	乗合自動車
978	168	contents	内容
979	168	getter	得るもの
980	167	even	平
981	167	measurement	計測
982	167	successfully	正常に
983	166	definitions	定義
984	166	e_	e_
985	166	flags	旗
986	166	sync	同期
987	165	decryption	復号化
988	165	fully	完全に
989	165	those	それらの
990	165	triggered	引き金になった
991	164	debounce	debounce
992	164	don	don
993	164	known	既知
994	164	multi	複数の（接頭辞）
995	164	tb	tb
996	162	configurations	構成
997	162	crypt	crypt
998	161	ddsapp	ddsapp
999	161	identify	識別
1000	161	oriented	指向

文書履歴

ver. 0.01 初稿 20220508
ver. 0.02 説明、文書一覧追記 20220509 2000
ver. 0.03 単語帳追記 20220509 2100