Als ara::com-Dienst modellierte Schnittstelle; Methoden/Felder werden über generierte Proxies/Skeletons aufgerufen (Parameterrichtung IN/OUT).
User GuideAI-GENERATED
Used for transfer, processing, activation, and monitoring of software packages and software clusters in UCM.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 6e0698182e67ProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
Used for transfer, processing, activation, and monitoring of software packages and software clusters in UCM.
The service interface PackageManagement controls the transfer, processing, and activation of software packages on the AUTOSAR Adaptive Platform [SWS_UCM_00345], [SWS_UCM_00352]. It enables the block-by-block loading of packages, the extraction of software clusters, and their controlled activation in coordination with State Management [SWS_UCM_00346], [SWS_UCM_00352]. In addition, the service provides mechanisms for status monitoring as well as for rolling back and cleaning up session data [SWS_UCM_00353], [SWS_UCM_00361].
1. Role and system context of the service interface
The service interface PackageManagement forms the central interface of Update and Configuration Management (UCM) for managing, transferring, and installing software packages on the AUTOSAR Adaptive Platform [SWS_UCM_00343]. Here, the UCM instance typically acts as a service provider (skeleton), while higher-level update coordinators or diagnostic clients act as service consumers (proxies). For identification, the service provides the unique module instance identifier via the method GetId[SWS_UCM_00343]. During the activation process, UCM interacts closely with State Management, which must release the update session and perform verifications [SWS_UCM_00352].
2. Methods, events, and fields
All methods defined in the service interface operate with synchronous invocation semantics or request-response messages, since Fire & Forget false is specified for all methods [SWS_UCM_00345]. The state field CurrentStatus has a getter and a notifier, allowing clients to subscribe to UCM status changes in an event-driven manner or query them actively [SWS_UCM_00361]. In addition, GetProgress provides detailed progress information on the currently active state of the state machine [SWS_UCM_00360]. For querying the software inventory, GetSwPackages is available for listing available software packages [SWS_UCM_00359], GetSwClusterInfo for installed software clusters in state kPresent[SWS_UCM_00357], GetSwClusterManifestInfo for cluster manifest data [SWS_UCM_00358], and GetSwClusterChangeInfo for pending changes in the states kAdded, kUpdating, or kRemoved[SWS_UCM_00356]. Historical traceability of executed actions is provided via GetHistory with timestamp filters [SWS_UCM_00355].
3. Lifecycle, session flows, and state dependencies
A typical update sequence is divided into transfer, processing, activation, and completion. The package transfer is either initiated by TransferStart, which creates a TransferIdType and negotiates the block size [SWS_UCM_00345], or alternatively registered by RegisterSoftwarePackage by specifying a package URI [SWS_UCM_00344]. In the case of block-by-block transfer, the data blocks are continuously persisted via TransferData with a block counter specified [SWS_UCM_00346] and finalized with TransferExit[SWS_UCM_00347]. Subsequently, ProcessSwPackage extracts the software package [SWS_UCM_00349]. Ongoing processings can be cancelled using Cancel[SWS_UCM_00351] or interrupted and resumed with Suspend and Resume[SWS_UCM_00397], [SWS_UCM_00398]. Transfers that are no longer needed can be removed with DeleteTransfer[SWS_UCM_00348]. With Activate, the extracted software clusters are activated [SWS_UCM_00352], while Finish terminates the processing session and cleans up temporary data [SWS_UCM_00354]. If errors occur, RevertProcessedSwPackages allows rolling back processed packages [SWS_UCM_00350], and Rollback enables restoring the system state prior to package processing [SWS_UCM_00353].
The interface methods guard error conditions via specific application errors. In case of calls contrary to the context, methods like Activate, Cancel, Finish, ProcessSwPackage, TransferData, and TransferExit return the error kOperationNotPermitted[SWS_UCM_00346], [SWS_UCM_00347], [SWS_UCM_00349], [SWS_UCM_00352]. Invalid transfer IDs are rejected with kTransferIdInvalid[SWS_UCM_00346], [SWS_UCM_00348], while corrupted block sequences or memory bottlenecks lead to kBlockIncorrect, kBlockSizeIncorrect, kBlockInconsistent, or kMemoryInsufficient[SWS_UCM_00345], [SWS_UCM_00346]. Security and consistency checks raise errors such as kAuthenticationFailed, kPackageInconsistent, kPackageManifestInvalid, and kPackageVersionIncompatible[SWS_UCM_00346], [SWS_UCM_00349]. Removal of the core system is prevented with kSwclRemovalDenied[SWS_UCM_00349]. During activation, kDependencyMissing, kUpdateSessionRejected, or kVerificationFailed signal integration problems with dependencies or State Management [SWS_UCM_00352].
This guide was generated by an AI based on the AUTOSAR specification R25-11.
Mitglieder
ActivateThis method activates the Software Clusters extracted from the processed Software Packages.
CancelThis method aborts an ongoing processing of a Software Package.
This method finishes the processing for the current set of processed Software Packages. It does a cleanup of all data of the processing including the sources of the Software Packages.
This method returns a list pending changes to the set of SoftwareClusters on the adaptive platform. The returned list includes all SoftwareClusters that are to be added, updated or removed. The list of changes is extended in the course of processing Software Packages.
Start the transfer of a Software Package after having received a Vehicle Package. The size of the Software Package to be transferred to UCM must be provided. UCM will generate a Transfer ID for subsequent calls to TransferData, TransferExit, ProcessSwPackage, DeleteTransfer.
This method aborts an ongoing processing of a Software Package.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: b042c91a5838ProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
use
The service method Cancel of the service interface PackageManagement serves to prematurely abort the ongoing processing of a software package [SWS_UCM_00351]. As a call parameter, the identifier of the operation is passed as IN parameter id of type TransferIdType[SWS_UCM_00351]. Since Fire & Forget is set to false for this method, the method call occurs synchronously with acknowledgment or feedback to the caller [SWS_UCM_00351].
Error handling
If execution fails, the interface defines specific error codes (Application Errors) [SWS_UCM_00351]:
kTransferIdInvalid: The transmitted transfer ID is invalid [SWS_UCM_00351].
kOperationNotPermitted: The cancellation is not supported in the current context [SWS_UCM_00351].
Interaction and Concurrency
The method is closely related to package processing: A processing operation is typically initiated via ProcessSwPackage for an assigned TransferIdType id[SWS_UCM_00349]. Interpretation: Cancel is likely designed primarily to abort the package processing running through ProcessSwPackage[SWS_UCM_00349], [SWS_UCM_00351]. Question Q-a220345676f7046c (open) Callers must ensure that the transfer ID exists and the package is in a state that permits cancellation, in order to avoid the error kOperationNotPermitted[SWS_UCM_00351].
This text was generated by an AI and serves as guidance.
This method finishes the processing for the current set of processed Software Packages. It does a cleanup of all data of the processing including the sources of the Software Packages.
This method returns a list pending changes to the set of SoftwareClusters on the adaptive platform. The returned list includes all SoftwareClusters that are to be added, updated or removed. The list of changes is extended in the course of processing Software Packages.
registers a package that could already be in Machine’s file system or to be downloaded.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 0620dbe84c7eProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
use
The service method RegisterSoftwarePackage belongs to the service interface PackageManagement (version 1.0) and serves to register a software package in the system [SWS_UCM_00344]. The target package can already be located locally in the file system of the machine or be passed as a reference for a pending download.
The method has the following parameters:
uri (IN, UriString): Specifies the URI path referencing the software package to be registered [SWS_UCM_00344].
transferId (OUT, TransferIdType): Returns a unique identifier for the transfer operation upon successful registration [SWS_UCM_00344].
Call Semantics and Error Handling
The property Fire & Forget is set to false for this service [SWS_UCM_00344]. Callers therefore receive a direct acknowledgment about the result of the method processing. If the passed URI is syntactically invalid or references an invalid target, execution fails with the specific application error kInvalidUri[SWS_UCM_00344].
Interaction and Constraints
The method call typically constitutes the initial step in the package management sequence. As an interpretation, the returned transferId is likely used in further steps of package management to uniquely address the transfer or installation process. Question Q-fc2bc07c914858a2 (open) Since no concurrency guarantees are specified, the caller should await arrival of the result before initiating subsequent actions with the respective identifier.
This usage note was generated by an AI based on the specification AUTOSAR Adaptive R25-11.
service method TransferData [SWS_UCM_00346]Upstream: RS_UCM_00019 wording not yet imported, RS_UCM_00025 wording not yet imported
TransferData (IN TransferIdType id, IN ByteVectorType Management data, IN uint64_t blockCounter)
Block-wise transfer of a Software Package to UCM.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: fbad4e8e0243ProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The service method TransferData is used for the blockwise transfer of a software package to the Update and Configuration Management Manager (UCM) within the service interface PackageManagement ([SWS_UCM_00346]). Since the method is not defined as Fire & Forget, every call returns an acknowledgment or a specific application error.
The following input parameters must be passed for the call ([SWS_UCM_00346]):
id (TransferIdType): The transfer identification previously generated by the UCM.
data (ByteVectorType Management): The payload data block of the software package to be transferred.
blockCounter (uint64_t): The consecutive counter of the current data block.
Regarding sequence and interaction, the method requires a prior call of TransferStart ([SWS_UCM_00345]). Via TransferStart, the caller receives the valid transfer ID as well as the required block size blockSize and the obligation to specify the total package size. The data transfer must strictly adhere to these requirements; Interpretation: blockCounter is likely required to be incremented monotonically and without gaps by the caller, since receiving the same block number twice triggers the error kBlockIncorrect ([SWS_UCM_00346]). Question Q-61272c50c151f4db (open)
Error handling distinguishes between structural transfer errors, consistency issues, and package validation errors ([SWS_UCM_00346]):
Transfer and resources: If the session is invalid or the call context is incorrect, UCM responds with kTransferIdInvalid or kOperationNotPermitted. If a block exceeds the agreed size or the announced total size, kBlockSizeIncorrect or kSizeIncorrect follows. In case of insufficient memory or errors during persistence, kMemoryInsufficient or kTransferFailed is returned.
Integrity and compatibility: If data checks fail, kBlockInconsistent, kPackageInconsistent, or kAuthenticationFailed is reported. In addition, invalid manifests (kPackageManifestInvalid), incompatible versions (kPackageVersionIncompatible, kOldVersion), unsupported formats (kPackageFormatUnsupported), or the impermissible removal of core clusters (kSwclRemovalDenied) are rejected.
This usage note was generated automatically based on the AUTOSAR specification R25-11.
Start the transfer of a Software Package after having received a Vehicle Package. The size of the Software Package to be transferred to UCM must be provided. UCM will generate a Transfer ID for subsequent calls to TransferData, TransferExit, ProcessSwPackage, DeleteTransfer.
gemini-3.8-flash-low· 2026-10-13 · German original