Configure AUTOSAR Adaptive Service Instance Identifier

R2026b

In AUTOSAR Adaptive service-oriented architectures, each service has two distinct identifiers:

  • Service Interface Identifier (Service ID) — Identifies the type of service, that is, what functionality the service provides (for example, a lane guidance interface).

  • Service Instance Identifier — Identifies a specific running instance of that service (for example, the lane guidance service on a particular electronic control unit (ECU)).

Together with service versioning, these identifiers enable software components to discover and communicate with the correct services at runtime.

For models using the service interface modeling pattern, configure the service instance identifier through the deployment specification in the Property Inspector. To do this:

  1. Create an AUTOSAR architecture model and add the adaptive software component model as a referenced component. For more information, see Configure AUTOSAR Adaptive Code Generation.

  2. In the architecture model toolstrip, on the Modeling tab, in the Platform section, select Adaptive Platform.

  3. In the Share section of the Modeling tab, select the network binding: DDS or SOME/IP.

  4. In the architecture canvas, click the service port on the component for which you want to configure the instance identifier.

  5. In the Property Inspector, expand the Parameters section, then expand the Deployment subsection. Set the Service Instance ID value for the port. If you leave the box empty, an automatic value is assigned.

    For DDS network binding, you can also configure the DDS Domain ID in this section. For SOME/IP network binding, you can configure the SOME/IP Eventgroup ID.

  6. Build the component model.

The build process generates a service instance manifest file (ServiceInstanceManifest.arxml) which describes service interface deployments, service instances, and service instance to port mapping for the adaptive component.

See Also

Topics