Ethernet-Based Communication in AUTOSAR:

Hеllo Rеadеrs, 👋😍
My name is Nagaraj B H, and I'm working at "Luxoft India '' as a Junior Software Engineer. Luxoft has given me several opportunities to work on numerous projects, which has stimulated me to discuss the crucial strategies concerned in developing a Ethernet protocol. Here we will speak the in-detail Ethernet communication in AUTOSAR
Ethernet-Based Communication in AUTOSAR:

The Autosar Ethernet stack contains various modules that complement its functions. Now let's understand the functionality of each module of Ethernet communication stack one by one

COM:It is the top module of the Autosar BSW service layers and especially the Ethernet network stack. The functionality of the COM module is the same as all other stacks such as CAN, Flexray and LIN. because the COM module is a protocol-independent module and works the same regardless of the underlying communication protocol virus.
The function of the COM module is to provide the application module with access to the PDU and signal/group signal to perform its task. An application should call the Autosar API from the COM module to receive or send a signal/PDU, and should not directly call lower-level modules. All PDU and signal configuration is done in the COM module.

PDUR: Abstract is a PDU router, as the name suggests, the function of this module is to direct the PDU from the source module to the correct destination. PduR is the second most popular module in the Autosar Com stack for all communication protocol stacks such as Ethernet, Flexray, CAN, etc.
The routing table resides in this module and is a configurable parameter. Using a configuration tool such as Ebtresos, the current PDU Davinci Configurator routing path is configured as needed. It communicates with Autosar COM and DCM upper-layer modules and Autosar DoIP and SoAD lower-layer modules.

DOIP: DoIP is short for Diagnostics over IP. because there is no transport protocol module between DCM and SoAD. The new ISO standard ISO 13 00 is designed to implement IP diagnostics along with other security features of the Autosar Ethernet stack.
Features of the DoIP module :
Vehicle Identification and Notification: It is necessary to identify who is participating in DoIP communication Enable.
Routing: Allows you to enable or disable individual diagnostic messages (e.g. UDS and OBD) and also handle individual testers differently.
Node Information: Provides general information about an individual DoIP unit. It is typically used by testers to obtain information relevant to the current DoIP protocol of individual DoIP entities.

SOAD: The paradigm on which the family of protocols TCP/IP is based is the use of points. A socket is uniquely identified by the IP address and port combination of the remote and local endpoints. Through a socket, packet-oriented UDP and connection-oriented TCP user data is sent from the TCP/IP network to the application or vice versa.
The function of the Socket Adapter Module (SoAd) is to convert socket-based communication to PDU-based communication and vice versa. It provides a familiar PDU interface to higher-level modules, fully integrating the Ethernet stack with the AUTOSAR architecture.

TCP/IP: The TCP/IP stack (TCP IP) resides between the Socket Adapter (SoAd) and Ethernet Interface (EthIf) modules. And the functionality of Autosari TCP/IP module and standard TCP/IP module is the same. from any IP address. It contains several modules that perform different functions. IP address configuration is done in this module, but IP allocation and assignment can be done dynamically using DHCP. The TCP/IP module contains the following modules:
Address Resolution Protocol (ARP)
Internet Protocol (IP)
Dynamic Host Configuration Protocol (DHCP)
Internet Control Message Protocol (ICMP)
User Datagram Protocol (UDP)
Transmission Control Protocol (TCP)

EthIf: In the AUTOSAR layered software architecture, the Ethernet interface belongs to the ECU abstraction layer, or more precisely, to the communication hardware abstraction in the communication surface. This shows the basic functionality of an Ethernet interface like all other interface modules, such as the CANif, FrIf and EthIf modules, they provide the upper layers with a hardware-independent interface to the Ethernet communication system.
This interface must be uniform across all Ethernet controllers. Thus, the upper layers (TCP/IP, EthSM, CDD, V2x modules) access the underlying bus system in a unified way. The Ethernet interface does not use the Ethernet hardware directly, but sends and receives data from the Ethernet controller module.

Eth Driver: In AUTOSAR, the Ethernet controller belongs to the microcontroller abstraction layer, or more precisely, to the communication drivers. Provide a hardware-independent interface to the upper layer for multiple controllers of the same type. And it allows the upper layers to use Ethernet controllers permanently.
The interface has a uniform user interface name and type. Provide functions to initialize, configure, and communicate with an Ethernet controller. Each Ethernet controller requires a different Ethernet controller. However, the same type of Ethernet controller can also be controlled by a single Ethernet controller of this type.

Eth Transceiver Driver :
In AUTOSAR, the Ethernet transmitter driver belongs to the microcontroller abstraction layer, or more precisely, to the communication drivers.
Provides hardware independent interface to the upper layer for the same type of multiple transceivers.And with that upper layers can access Ethernet transceivers with uniform manners.
Provide functions to initialize and configure Ethernet transmitters. Each Ethernet transmitter requires a different Ethernet controller. However, Ethernet transmitters of the same type can be controlled by a single Ethernet transmitter driver of that type.