SNIP_ADAPTIVE_PLATFORM_FIGURE_Figure_7_4_UPDATEANDCONFIGURATIONMANAGEMENT

Figure 7.4: State machines for transferring and processing state which, in combination, are representing the lifecycle of Software Packages . This diagram only represents the life cycle without storing a Software Package (usually referred to as streaming). A Software Package can be processed again if it is stored and reachable to UCM, and if it does not break the Old Version protection [SWS_UCM_00103] (it did not have successful activation). [SWS_UCM_00007] Data transfer at any time Upstream requirements: RS_UCM_00013, RS_UCM_00019, RS_UCM_00025 ⌈UCM shall provide support to transfer Software Packages at any time when UCM is running. T ransferring is decoupled from the UCM Package Management states.⌋ [SWS_UCM_00272] Transfer block size Upstream requirements: RS_UCM_00025 ⌈TransferStart shall return blockSize parameter to indicate the maximum block size (unit: bytes, as defined by MaxBlockSize) to be allowed to transfer in one TransferData method call.⌋ The block size should be aligned to flashing capability in case of Classic Platform capability for instance. [SWS_UCM_00088] Preparation of data transfer Upstream requirements: RS_UCM_00013, RS_UCM_00019, RS_UCM_00025 ⌈Data transfer shall be prepared with the method TransferStart or RegisterSoftwarePackage. In the preparation step the number of bytes to be transferred is provided by the client and UCM assigns an id for the Software Package to be trans-