{'fraction_non_alphanumeric': 0.019404915912031046, 'fraction_numerical': 0.00129366106080207, 'mean_word_length': 5.241935483870968, '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}}
Temporal data matching in component based real time systems

We consider embedded systems structured as a graph of communicating components [1]. In this model, we define a data matching property based upon the interactions of the data flow paths passing through common components. If a component uses inputs which indirectly depend on the same component output, these inputs have to depend on a same execution step of the producer component, even when several independent paths link these two components, and when the components have different timing characteristics (esp. different periods). We analyze the system architecture to detect situations that can cause data matching problems. Depending on the system needs, we propose several approaches to manage data matching.