Search

Scope: Core (OPC-10000-*) All specs

31 result(s) for Software Package

OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.14 Software Package

Software Package single file that contains the data for the software update in a device specific format Note 1 to entry: This document defines a package format to combine multiple ... files into one Software Package
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.17 Pending Version

Pending Version version information for a Software Package that was transferred before and is ready to be installed
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.8 Update of individual parts of a software

software of components. This is realized with the AddIn model ( 8.3.11 ). If a Software Package becomes very large and only parts of it can be replaced, the Server maintains ... individual files of the Software Package independently. When all desired files are on the Server , the installation can be started for the set of files. Here the FileSystem option
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.11 Selecting the correct version to install

correct version to install An update client selects the correct version of the Software Package to install. The rules behind this decision can be complex and can include e.g., dependency
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.15 Standard package format for transfer from the device (prototype / backup)

backup) If a working device is used as the prototype for other devices the Software Package of an application or configuration can be uploaded. Therefore, an embedded device should ... able to create a Software Package and upload it using the SoftwareUpdate AddIn . This package can also be used for backup
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.20 Prove integrity and authenticity of a Software Package

Prove integrity and authenticity of a Software Package An Update Client verifies the integrity and authenticity of the files within the Software Package
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.3 Direct-Loading option

Client can decide if an update is required and which version to install. The Software Package is transferred using the TemporaryFileTransferType ( OPC 10000-5 ). This includes the installation itself ... that the installation option is not used. Note that if the Software Package is installed during the transfer, the server cannot verify the integrity of the complete Software Package before
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.4 Cached-Loading option

Loading option The Cached-Loading option provides a model where the transfer of the Software Package and its installation are separate steps. To support the Cached-Loading model the Server ... Client can ensure to install the desired version after the transfer of the Software Package . With the Fallback Version the Client can install an alternative version. Software Packages are transferred
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.5 FileSystem option

FileSystem option The Cached-Loading option with a self-contained Software Package and concrete definition of the version information can be too restrictive for some devices. E.g., if new software
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.6 Installation option

Installation option Using the Cached-Loading option or the FileSystem option, a transferred Software Package or file is installed explicitly (compared to the implicit installation of Direct-Loading ). Therefore ... InstallationStateMachineType shall be used (see 8.4.9 ). It can either be used to install a Software Package ( Cached-Loading ) or a list of files from the FileSystem (File System based Loading
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.5 Software Update Client

Cached-Loading the Client can check CurrentVersion and PendingVersion Objects to determine if the Software Package is already transferred. With the FileSystem based Loading the Client can browse the FileSystem ... because for Cached-Loading and File System based Loading this depends on the actual software that should be installed (with Direct-Loading the server has no information about
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.7 Security considerations

companion specifications. It is necessary that the authenticity (integrity and source) of the Software Package is verified. These aspects can be implemented by the device in a vendor specific ... verify a digital signature of the Software Package . These mechanisms are out of scope of this specification
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.1.8 UpdateStatus

DirectLoadingType ( 8.4.4 ) and FileSystemLoadingType ( 8.4.6 ) it can be used during the transfer of the Software Package
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.1.13 VendorErrorCode

DirectLoadingType ( 8.4.4 ) and FileSystemLoadingType ( 8.4.6 ) it can be used during the transfer of the Software Package
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.3.1 Overview

Overview The PackageLoadingType provides information about the Current Version and allows transfer of a Software Package to and from the Server . The PackageLoadingType is illustrated in Figure 43 and formally ... HasSubtype ObjectType 1:DirectLoadingType 0:HasSubtype ObjectType 1:CachedLoadingType Conformance Units DI SU Software Update
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.3.3.1 General

used to create temporary files for download and upload of the Software Package . See 8.7 for the definition of a standard packaging format. In the TemporaryFileTransferType type the GenerateFileForRead ... device. Bad_NotSupported If the device does not support to upload / download of the Software Package . For all errors that occur during the file transfer the ErrorMessage Variable should provide
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.3.3.3 Transfer from the device

Transfer from the device The FileTransfer Object can optionally support the transfer of a Software Package from the device to the Client . If this transfer is not supported, the Server
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.3.5 WriteBlockSize

bytes) that a Client shall write to the file. The client shall write the Software Package in chunks of this size to the FileType object (the last Block
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.4.1 Overview

Overview The DirectLoadingType provides information about the Current Version and allows transfer of a Software Package to and from the Server . Transfer of the Software Package to the Server also
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.5.3 PendingVersion

PendingVersion The PendingVersion Object describes an already transferred new Software Package that is ready to be installed. If there is no Software Package available, the values should be empty
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.5.5 GetUpdateBehavior Method

Method Result Codes (defined in Call Service) Result Code Description Bad_NotFound If the Software Package , identified by the parameters, does not exist. Table 84 - GetUpdateBehavior Method AddressSpace definition Attribute
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.7.8 Hash

read by a Client to get the hash of a previously transferred Software Package . The hash value is calculated by the Server with the SHA-256 algorithm
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.9.4 InstallSoftwarePackage Method

InstallSoftwarePackage Method With this Method the Client requests the installation of a Software Package . The package can be either the previously transferred Pending Version or the alternative Fallback Version ... Before installation the Server can compare the hash against the calculated hash of the Software Package . This mechanism can be used if there is a risk that the Software Package
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.1 Overview

Overview The Software Package file format describes a standard format to share files for the software update. This enables Update Clients to use software from different vendors (i.e., it supports ... package, compatibility with the device, storage of the deployment and of supplementary files). The Software Package is shared as a single ZIP file with all the content described in this
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.2 Folder structure

Folder structure On the root level, the Software Package can have the following folders: The optional CONTENT folder holds the files or folders that are transferred to the device ... content of this folder is defined by the author of the Software Package . For Cached-Loading and Direct-Loading , this folder can contain a single file that shall be transferred
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

Package metadata The package metadata file describes the identity of the Software Package , the target for the installation, the compatibility to the device and optionally the usage of individual files ... within the Software Package . The package_metadata.json is stored in the META folder. The JSON schema for the package_metadata.json file associated with this version of the specification can be found here
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.4 Package signature

signature To prove authenticity and integrity the Software Packages can be signed. Initially the Software Package should be signed by the author (e.g., the manufacturer signs a firmware ... Additional signatures can be added by machine builders or plant operators to approve a Software Package for use in a specific plant. With this in place the Update Client
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.5 Solution packages

shall be installed (could be verified using a signature at the Solution Package ). A combination of several Software Packages shall be installed to a device as a single file ... numbers shall be installed first). True Targets[] 2:PackageTarget List of targets for the Software Package with at least one element. False Table 137 - Assignment definition Attribute Value BrowseName
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

A.1 NodeSet and Supplementary Files for DI Information Model

reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/DI/&i=2 The NamespaceUri for the package_metadata.json with structures and enumerations used for Software Package files is: http://opcfoundation.org/UA/DI/PackageMetadata/ Note: This namespace and the contained types typically
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

B.3.1 Simple example using Cached-Loading

memory is limited and the installation can be done during the transfer of the Software Package , the Direct-Loading model is another simple option. First the client determines what version ... Properties of CurrentVersion of the Loading object. Then the client can transfer the Software Package to the device using the Loading.FileTransfer object. At the end of the transfer the server
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

Agreement of Use

container format for Software Packages of the software update Added new subsection for the Software Package file format. 10221 Feature Missing information whether unsigned software packages are supported Added ... indication Added new IAssetLocationIndication Interface . 9029 Feature Missing method to remove a previously transferred software package Clear method added 10254 Errata Some terms are lower case in the definition