Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Application SWC NVBlock SWC Parameter SWC RTE BSW Sensor Actuator SWC Application SWC Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface • ModeSwitch Interface • Trigger Interface Application SWC NVBlock SWC Parameter SWC RTE BSW Sensor Actuator SWC Application SWC Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface • ModeSwitch Interface • Trigger Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface • ModeSwitch Interface • Trigger Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. CS Interface is used to call services or functions from another components. The component who owns the service is called Server and the caller is called Client. Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface • ModeSwitch Interface • Trigger Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. CS Interface is used to call services or functions from another components. The component who owns the service is called Server and the caller is called Client. NVData Interface it provides element level access (read only or read/write) to non-volatile data whenever we want to access the NVBlock. Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface • ModeSwitch Interface • Trigger Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. CS Interface is used to call services or functions from another components. The component who owns the service is called Server and the caller is called Client. NVData Interface it provides element level access (read only or read/write) to non-volatile data whenever we want to access the NVBlock. Parameter interface is used to exchange calibrations or constants data across components. Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. CS Interface is used to call services or functions from another components. The component who owns the service is called Server and the caller is called Client. NVData Interface it provides element level access (read only or read/write) to non-volatile data whenever we want to access the NVBlock. • ModeSwitch Interface Parameter interface is used to exchange calibrations or constants data across components. • Trigger Interface Mode switch interface is used to notify a software component with different states that the system can enter. Autosar Ports and Port Interfaces Ports: Autosar architecture describe Ports as the mode of communication between all Autosar modules. • • • Provider Port (P-Port) Receiver Port (R-Port) ProviderReceiver Port (PR-Port) Port Interface: The type of information that are communicated between ports are defined by the port interface. • Sender Receiver Interface • Client Server Interface • NVData Interface • Parameter Interface Application SWC NVBlock SWC Parameter SWC Sensor Actuator SWC Application SWC RTE BSW SR Interface is used to communicate data between components. Data can be any information in terms of primitive or complex types: arrays, structures, variables, etc. CS Interface is used to call services or functions from another components. The component who owns the service is called Server and the caller is called Client. NVData Interface it provides element level access (read only or read/write) to non-volatile data whenever we want to access the NVBlock. • ModeSwitch Interface Parameter interface is used to exchange calibrations or constants data across components. • Trigger Interface Mode switch interface is used to notify a software component with different states that the system can enter. Trigger interface allows software components to trigger the execution of other software components. Client Server Interfaces Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus SWC - 2 • 1:1 communication Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus SWC - 2 SWC - 4 R-Port Receiver Data: BeltStatus • • 1:1 communication 1:N communication Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus SWC - 3 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus SWC - 2 • • • 1:1 communication 1:N communication M:1 communication Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus SWC - 3 SWC - 2 SWC - 4 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus • • • • 1:1 communication 1:N communication M:1 communication M:N communication Sender Receiver Interface Sender Receiver interface is used to send or receive data between software components. This type of interface its an asynchronous communication SWC - 1 Sender P-Port Data: BeltStatus R-Port Receiver Data: BeltStatus SWC - 3 SWC - 2 SWC - 4 Sender P-Port Data: SeatbeltStatus_FL SeatbeltStatus_FR SeatbeltStatus_RL SeatbeltStatus_RR Provided Port Configuration Required Port Configuration R-Port Receiver Data: SeatbeltStatus_FL SeatbeltStatus_FR SeatbeltStatus_RL SeatbeltStatus_RR • • • • 1:1 communication 1:N communication M:1 communication M:N communication
