Configure AUTOSAR Adaptive Service Interface 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, the service interface identifier and service versioning are configured through the deployment specification in the Property Inspector. To configure these:

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 service interface identifier.

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

   • For SOME/IP network binding, you can also configure the Major Version and Minor Version in this section.

   • For DDS network binding, use the set function to configure the Major Version and Minor Version.

     apiObj = autosar.api.getAUTOSARProperties("softwareComponentModelName");
     interfacePath = [get(apiObj,"XmlOptions","InterfacePackage")'/'portName];
     set(apiObj,interfacePath,"MajorVersion",4);
     set(apiObj,interfacePath,"MinorVersion",2)

6. Build the component model. The build process writes the specified service interface identifier to the SERVICE-INTERFACE-ID field and service versioning to the SERVICE-INTERFACE-VERSION field in the generated ServiceInstanceManifest.arxml.

For DDS network binding, service versioning (major and minor version) is also encoded in the DDS USER_DATA QoS field and used for service version compatibility checking at runtime. The major version must match exactly, and the provided service's minor version must be greater than or equal to the consumer's minor version.