{'fraction_non_alphanumeric': 0.018335684062059238, 'fraction_numerical': 0.0, 'mean_word_length': 5.283185840707965, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
An analysis of the AUTOSAR OS timing protection mechanism

The in-vehicle embedded system market is evolving toward a large improvement of the industrialization of the embedded software. One of the technical consequences of this evolution is the mandatory integration of protection mechanisms in the embedded operating system kernels to support the design of multi-suppliers multi-critical component-based embedded software. In this paper, we evaluate such a mechanism: the timing protection mechanism proposed in the AUTOSAR OS standard. This evaluation shows that the present version of the mechanism is not fully adapted to multi-critical systems because it does not handle soft/non real-time applications.