Requirements on Function Inhibition Manager , No.81, AUTOSAR R21-11(230) CP

Requirements on Function Inhibition Manager , No.81, 2021-11

https://www.autosar.org/fileadmin/standards/classic/21-11/AUTOSAR_SRS_FunctionInhibitionManager.pdf


AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11, 200文書読んだ。2022年5月に全部到達。

https://qiita.com/kaizen_nagoya/items/4043e8414f850ce266a4

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 用語(terms)

|Term|Description|
|:--|:--|
|Activity state| The activity state is the status of a software component being executed. The activity state results from the permission state as a precondition and also physical enable conditions. It is not calculated by the FIM and not available as a status variable. It could only be derived from local information within a software component.
|API |Application Programming Interface
|BSW| Basic Software
|DEM| Diagnostic Event Manager
|ECU| Electronic Control Unit
|EOL |End Of Line
|ESD |Electro Static Disturbance
|ESP| Electronic Stability Program
|FID| Function Identifier
|FIM |Function Inhibition Manager
|Functionality |Functionality comprises User-visible and User-non-visible functional aspects of a system (AUTOSAR_Glossary.pdf [2]). In addition to that - in the FIM context - a functionality can be built up of the contents of one, several or parts of runnable entities with the same set of permission / inhibit conditions. By means of the FIM, the inhibition of these functionalities can be configured and even modified by calibration. Each functionality is represented by a unique function ID. A functionality is featured by a specific set of inhibit condition in contrast to runnable entities having specific scheduling conditions.
|HW |Hardware
|ID| Identification/Identifier
|ISO |International Standardization Organization
|IUMPR |In Use Monitoring Performance Ratio: The In-Use-Monitor Performance Ratio (IUMPR) indicates how often the OBD system monitors, particular components, compared to the amount of the vehicle operation. It is defined as the number of times a fault could have been found (=numerator) divided by the number of times the vehicle operation has been fulfilled (=denominator) as defined in the respective OBD regulations.
|MIL| Malfunction Indication Light
|Monitoring function |• Part of the Software Component. • Mechanism to monitor and finally to detect a fault of a certain sensor, actuator or could be a plausibility check • Reports states about events from internal processing of a SW-C or from further processing of return values of other basic software modules. • See also AUTOSAR_SWS_DEM
|NVRAM |Non volatile Memory
|OBD|Onboard Diagnostics
|OEM |Original Equipment Manufacturer
|OS |Operating System
|Permission state |The permission state contains the information whether a functionality, represented by its FID, can be executed or whether it shall not run. The state is controlled by the FIM based on reported events.
|RAM |Random Access Memory
|ROM |Read-only Memory
|RTE| Runtime Environment
|Runnable entity |A Runnable Entity is a part of an Atomic Software-Component which can be executed and scheduled independently from the other Runnable Entities of this Atomic Software-Component. It is described by a sequence of instructions that can be started by the RTE. Each runnable entity is associated with exactly one EntryPoint.
|SW-C| Software Components
|Xxx_|Placeholder for an API provider
## 英日単語帳
日本語は仮訳

T.B.D.

# 参考(reference)

[1] Standardization Template
AUTOSAR_TPS_StandardizationTemplate
[2] Glossary
AUTOSAR_TR_Glossary
[3] Requirements on AUTOSAR Features
AUTOSAR_RS_Features
[10] D1.5-General Architecture; ITEA/EAST-EEA, Version 1.0; chapter 3, page 72 et seq.
[20] D2.1-Embedded Basic Software Structure Requirements; ITEA/EAST-EEA, Version 1.0 or higher
[30] D2.2-Description of existing solutions; ITEA/EAST-EEA, Version 1.0 or higher.