namespace ara::com::runtime

The namespace ara::com::runtime provides central runtime services for resolving communication endpoints in communication management AUTOSAR_AP_SWS_CommunicationManagement p. 39. Its core function ResolveInstanceIDs translates abstract model identifiers of type ara::core::InstanceSpecifier into concrete ara::com::InstanceIdentifierContainer usable for proxies and skeletons [SWS_CM_00118]. If mapping of a formally valid identifier fails in deployment, the exception-safe function returns the error code ComErrc::kInstanceIDNotResolvable within a ara::core::Result. Callers must therefore evaluate the result object prior to service instantiation.

more ›

Context

The namespace ara::com::runtime provides central runtime functionalities for communication management (ara::com) of the AUTOSAR Adaptive Platform AUTOSAR_AP_SWS_CommunicationManagement p. 39. Its primary functional responsibility lies in decoupling the abstract software architecture from the concrete communication infrastructure at runtime. While applications and software components are bound to ports in their interfaces via abstract model identifiers (ara::core::InstanceSpecifier), the communication middleware requires concrete addressing and instantiation data in the form of ara::com::InstanceIdentifier objects to establish connections [SWS_CM_00118].

The function ResolveInstanceIDs declared in header ara/com/runtime.h forms the bridge between these two abstraction levels [SWS_CM_00118]. It accepts a ara::core::InstanceSpecifier and transforms it into a ara::com::InstanceIdentifierContainer AUTOSAR_AP_SWS_CommunicationManagement p. 40. Interpretation: The concrete mapping is likely based internally on the manifest and deployment configurations stored in the execution context, keeping application code portable and free of hard-wired network or protocol addresses. Question Q-8fab6de1c39a065a (open)

Context diagram: Classification of ara::com::runtime between application architecture and communication deployment. Sources: [SWS_CM_00118], AUTOSAR_AP_SWS_CommunicationManagement p. 39.

Usage Path

Typical use of namespace ara::com::runtime occurs during the initialization and startup phase of an adaptive application before communication relationships are established via service proxies or service skeletons AUTOSAR_AP_SWS_CommunicationManagement p. 41. A service consumer or provider thereby traverses a deterministic resolution path:

• Determine specifier: The application instantiates or references the identifier of type ara::core::InstanceSpecifier defined for the respective communication port.
• Resolve instances: The identifier is passed to the function ara::com::runtime::ResolveInstanceIDs [SWS_CM_00118].
• Check result: The call returns an object of type ara::core::Result<ara::com::InstanceIdentifierContainer>, which is checked for successful execution or error states [SWS_CM_00118].
• Process container: On success, the ara::com::InstanceIdentifierContainer contains a number of instance identifiers that is proportional to the number of matches found in the deployment [SWS_CM_00118]. The application can specifically select one instance or iterate over all available instances.
• Instantiate proxy or skeleton: The resolved ara::com::InstanceIdentifier objects are subsequently used to create concrete proxy or skeleton instances AUTOSAR_AP_SWS_CommunicationManagement p. 42.

Sequence diagram: Call and processing flow of instance resolution via ResolveInstanceIDs. Sources: [SWS_CM_00118], AUTOSAR_AP_SWS_CommunicationManagement p. 41.

Error Scenarios

The interfaces in namespace ara::com::runtime follow the platform-wide paradigm of robust, exception-free error handling. According to the specification, ResolveInstanceIDs is declared as noexcept and has the exception safety level exception safe [SWS_CM_00118]. Errors are therefore never signaled via C++ exceptions, but are entirely transported via the error monad ara::core::Result AUTOSAR_AP_SWS_CommunicationManagement p. 47.

The central specified error scenario concerns the error code ComErrc::kInstanceIDNotResolvable [SWS_CM_00118]. This error occurs when the passed ara::core::InstanceSpecifier is formally valid but cannot be mapped to any existing ara::com::InstanceIdentifier in the current system configuration or manifest [SWS_CM_00118]. In practice, this indicates discrepancies between modeling and deployment, such as when a service provider on another machine was not deployed or the binding is missing in the manifest. Rollback semantics (rollback_semantics) apply to this error: no partial states are created or resources bound, allowing the caller to verify the configuration or transition to a defined error state [SWS_CM_00118].