SNIP_CLASSIC_COMSTACK_SECTION_7_1_I_PDU_handling

7.1 I-PDU handling [SWS_PduR_00160] Upstream requirements: SRS_GTW_06049 ⌈The PDU Router module shall transfer an I-PDU without modification in a consistent manner from the source module to the destination module(s).⌋ An I-PDU is identified by the I-PDU ID and/or the symbolic name (i.e. the Symbolic NameValue of the container of the I-PDU [6, Specification of ECU Configuration]). For post-build the I-PDU ID is required because the I-PDU must be identified after the PDU Router module is compiled. If the PDU Router module is pre-compile (i.e. in source code) the symbolic names may be used, see [6, Specification of ECU Configuration]. Each BSW module that handles I-PDUs and provides an API for I-PDUs must contain a list of I-PDU IDs [6]. This means that each called module will have a look-up table identifying the I-PDU. Example: The Com module calls PduR_ComTransmit (here the PDU Router module configuration contains the I-PDU ID), the PDU Router module will call CanIf_Transmit (here the CanIf module configuration contains the I-PDU ID), the CanIf will call PduR_CanIfTxConfirmation (here the PDU Router module configuration contains the I-PDU ID), and PDU Router module will call Com_TxConfirmation (here the Com module configuration contains the I-PDU ID). The example is illustrated in the following Figure 7.1 (only I-PDU ID is shown as parameter): Figure 7.1: I-PDU ID Example [SWS_PduR_00161] Upstream requirements: SRS_GTW_06003 ⌈The PDU Router module shall identify a routing path uniquely by the combination of source module I-PDU ID (located in the PDU Router configuration) and destination I-PDU IDs (located in the called destination module configurations).⌋ [SWS_PduR_00766] Upstream requirements: SRS_GTW_06003 ⌈The PDU Router module shall convert the I-PDU ID to the destination module(s) for both Transmit path and TxConfirmation/RxIndication path.⌋ Example: The Com module transmits an I-PDU to CanIf and LinIf. The PduR_Com Transmit is called. The PDU Router module will convert the source I-PDU ID (PDU Router module configuration) to one I-PDU ID for LinIf (LinIf module configuration) and one I-PDU ID for CanIf (CanIf module configuration). The PduInfoType value received from the Com module is copied to the CanIf and LinIf modules without change. Example: The LinIf will call PduR_LinIfTxConfirmation with an I-PDU ID and, dependent on the success of the transmission, with a result E_OK (successful transmission) or E_NOT_OK (not successful transmission). Then the PDU Router module will convert this I-PDU ID and forward the call to Com using Com_TxConfirmation with the converted I-PDU ID and the received result. [SWS_PduR_00162] Upstream requirements: SRS_GTW_06003 ⌈The PDU Router module shall only route I-PDUs according to the routing paths given in the configuration.⌋ [SWS_PduR_00828] Upstream requirements: SRS_GTW_06104, SRS_GTW_06105 ⌈PduR generator (validation) shall deny configurations where I-PDUs with different MetaDataTypes are connected by a routing path.⌋ [SWS_PduR_CONSTR_00920] Status: DRAFT ⌈The PDU Router shall reject the configuration if an I-PDU owned by the Dds module is routed to/from a module that is not SoAd or Com (see PduRRoutingPath)⌋