What it is
AUTOSAR describes in-vehicle data exchange through two stacks that projects usually configure together. On a Classic microcontroller ECU, the communication stack carries signals and protocol data units (PDUs) between application software and the vehicle networks. On an Adaptive platform, Communication Management is the middleware applications use to offer and call services. SOME/IP (Scalable service-Oriented MiddlewarE over IP) is the foundation protocol for service messages and service discovery on IP, shared by both stacks.
In the Classic stack, COM packs and unpacks signals and signal groups into interaction-layer PDUs (I-PDUs). It applies transmission modes and reception monitoring so a receiver can detect missing or late data. The PDU Router forwards I-PDUs between upper modules and bus interfaces and can gateway whole PDUs. COM can gateway selected signals. In both cases the gateway leaves application meaning to the sender and receiver. Where the upper layer uses IP, the socket adaptor connects PDU communication to TCP or UDP sockets, and the SOME/IP transport protocol segments messages that do not fit in one datagram.
Communication Management exposes methods, events, and fields. A binding maps that API onto the network. SOME/IP is the common binding: discovery and subscription let one ECU find another and subscribe to events.
Who it applies to
Basic-software engineers integrate COM, the PDU Router, the socket adaptor, and SOME/IP transport on MCUs and on an HPC safety island. Network engineers set PDU layout, routing, and SOME/IP service identifiers so every node on a segment agrees. Middleware and application engineers on an application processor use Communication Management and rely on those identifiers. System architects place signal exchange, service interfaces, and gateways. Safety, diagnostics, and cybersecurity engineers meet the stack where monitoring, diagnostic routes, and secure channels share its paths.
What it covers
| Topic | Classic communication stack | Adaptive Communication Management |
|---|---|---|
| Application view | Signals, signal groups, and I-PDUs | Services, methods, events, and fields |
| Routing | PDU gateway in the PDU Router; signal gateway in COM | Binding from the service API onto the network |
| IP behaviour | Socket adaptor and SOME/IP transport | SOME/IP exchange, discovery, and subscription |
| Supervision | Transmission behaviour and reception monitoring | Service availability and subscription state |
| Protection hook | Selected PDUs can be authenticated by a separate mechanism | TLS or DTLS may protect the channel, as the release and binding allow |
Foundation protocol documents define the message structure, message kinds such as request, response, and notification, and how service discovery offers a service, finds it, and handles subscriptions. The vehicle service catalogue is an OEM or project design that has to stay inside those rules. TLS and DTLS versions follow the platform release and the binding in use.
How it fits with other documents
CAN, LIN, FlexRay, and Ethernet specifications sit below the PDU Router. Diagnostic messages use that router to reach the diagnostic manager, so a gateway configuration includes those routes together with application signals. End-to-end protection and secure on-board communication protect selected payloads; COM and the PDU Router still deliver the I-PDU. Adaptive secure-channel specifications attach TLS or DTLS to service communication. DDS is a separate service binding with its own discovery rules. Service-oriented API guidance describes the style these documents make normative. A zone controller usually runs PDU routing and a COM signal gateway, and may terminate or forward SOME/IP toward an HPC and body ECUs.
In practice
In the system extract, mark which data stays a signal, which data becomes a service, and which ECU gateways each path. Configure reception monitoring for signals a receiver must judge as fresh; extra timeouts surface as failed tests. List every PDU Router path, including signal-gateway routes and diagnostic routes on the same ECU. Freeze SOME/IP service and method identifiers, eventgroups, and serialization with the peer before integration. A mismatch appears as a failed offer, a missing subscription, or a payload the other side cannot decode. On an HPC, align the safety-island stack and the application-processor binding on every shared service. When a bench test fails, separate routing and sockets, then discovery and subscription, then payload contents.