Main Content

AUTOSAR Communication

Configure communication ports and interfaces

The communication interface of an AUTOSAR software-component consists of well-defined ports. An AUTOSAR component communicates through its ports with other AUTOSAR software components or Basic Software (BSW) services. A port provides information to, or requires information from, its communication partners. Each port owned by the component maps to a communication interface, based on the component functional requirements, for example:

  • Sender-receiver (S-R) interface, for message passing

  • Client-server (C-S) interface, for function invocation

  • Mode-switch (M-S) interface, for managing mode-based execution

  • Nonvolatile (NV) data interface, for port-based access to NV data

  • Parameter interface, for port-based access to parameter data

  • Trigger interface, for managing trigger-based execution

To configure AUTOSAR communication for a component port, you create an AUTOSAR interface, map the port to the interface, and map Simulink® elements, such as a root inport or outport, to the AUTOSAR port, as required by the type of interface. Use the AUTOSAR Dictionary and the Code Mappings editor or equivalent AUTOSAR property and map functions.


Signal InvalidationControl AUTOSAR root outport data element invalidation


getFunctionGet AUTOSAR mapping information for Simulink entry-point function
getFunctionCallerGet AUTOSAR mapping information for Simulink function-caller block
getInportGet AUTOSAR mapping information for Simulink inport
getOutportGet AUTOSAR mapping information for Simulink outport
mapFunctionMap Simulink entry-point function to AUTOSAR runnable and software address methods
mapFunctionCallerMap Simulink function-caller block to AUTOSAR client port and operation
mapInportMap Simulink inport to AUTOSAR port
mapOutportMap Simulink outport to AUTOSAR port
overflowedDetermine when a message queue overflows