Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10164-7-95 (2004): Software Management Function in OSI Systems Management
Technical Requirements and Implementation Guidelines for Software Lifecycle Operations in Open Systems Interconnection
Scope and Applicability
IEC 10164-7-95 (originally published as ISO/IEC 10164-7:1995, confirmed in 2004) defines the Software Management Function (SWM) within the OSI Systems Management framework. This standard specifies a set of management services and protocols that enable the administration of software assets across distributed open systems. It covers the entire software lifecycle—installation, loading, activation, deactivation, updating, and removal—on managed nodes.
The standard is applicable to any OSI-compliant network management environment that uses Common Management Information Protocol (CMIP) and the Guidelines for the Definition of Managed Objects (GDMO). It is particularly relevant for telecommunications, industrial automation, and enterprise network operations where centralized software management is required.
Tip: IEC 10164-7-95 is identical to ITU-T Recommendation X.744. When implementing, always refer to the latest corrigenda and amendments (e.g., 2004 confirmation) to ensure consistency with current OSI profiles.
Technical Requirements and Functional Model
Software Management Model
The standard defines a management information model comprising managed object classes that represent software items and their states. The core object classes include:
- SoftwareManagement – the system-level manager responsible for software-related operations.
- Software – a generic class representing a software product.
- SoftwareVersion – a specific version of a Software instance.
- SoftwareElement – a deployable unit (e.g., a file, module, or patch).
- SoftwareConfiguration – a set of elements that together form a consistent install.
Operations and Notifications
The standard specifies the following major operations (actions) that can be performed on managed objects:
| Operation | Description | Target Object Class |
|---|---|---|
| loadSoftware | Transfer a software element to a managed node (loading into memory or staging area). | SoftwareElement |
| installSoftware | Make a transferred element ready for execution (install image to production area). | SoftwareElement, SoftwareVersion |
| startSoftware | Activate an installed software item (e.g., start a process). | SoftwareVersion, SoftwareConfiguration |
| stopSoftware | Deactivate a running software item. | SoftwareVersion, SoftwareConfiguration |
| updateSoftware | Replace an existing software version with a new one (including migration of data). | SoftwareVersion |
| removeSoftware | Delete a software item from the managed node. | SoftwareElement, SoftwareVersion |
| dumpSoftware | Upload the current software image or state from the managed node for backup or audit. | SoftwareElement |
These operations are invoked via CMIP M-ACTION requests. The standard also defines the following notifications:
- softwareLoadReport – reports the outcome of a loadSoftware action.
- softwareInstallReport – outcome of installSoftware.
- softwareChangeReport – indicates any unsolicited change in software state (e.g., version change).
- softwareErrorReport – alerts management to a software-related fault.
Important: The exact behavior of operations depends on the underlying platform and management agent implementation. Pay special attention to the recovery semantics defined in the standard—many operations can be either atomic or best-effort. Conformance testing should verify both success and failure scenarios.
Implementation Highlights
Implementations of IEC 10164-7-95 typically rely on GDMO templates to define the managed objects and their attributes, operations, and notifications. Below is a summary of key attributes for the SoftwareVersion class:
| Attribute | Type | Description |
|---|---|---|
| softwareId | GraphicString | Unique identifier of the software product. |
| version | GraphicString | Version string (e.g., “3.1.2”). |
| installDate | GeneralizedTime | Date/time of last installation. |
| operationalState | ENUM | One of {disabled, enabled, active, unknown}. |
| fileChecksum | OctetString | Integrity checksum of the installed files. |
| licenseType | GraphicString | License model indicator (e.g., “perpetual”, “subscription”). |
When mapping to CMIP, each action is represented by a specific action name (e.g., “loadSoftware”) and carries an action info argument containing parameters such as source location, target directory, and timeout. The action reply may include a status code and error details.
Best Practice: Use a staged software management approach: load → install → start. Always validate checksums after load and before install to prevent corruption. The standard allows for a force parameter in actions; use it only when backward compatibility or emergency updates are required.
Compliance and Interoperability Considerations
Conformance to IEC 10164-7-95 requires adherence to the following:
- Definition of managed objects using GDMO as specified in the standard’s MIB (Management Information Base).
- Support for mandatory operations: loadSoftware, installSoftware, startSoftware, stopSoftware, and removeSoftware. Additional operations are conditional or optional.
- Implementation of the required notifications: softwareLoadReport, softwareInstallReport, and softwareChangeReport.
- Compliance with the OSI Systems Management framework, including CMIP as the communication protocol and Systems Management Function (SMF) interaction rules.
Interoperability testing should focus on action parameters, notification structure, and error handling. The standard includes protocol conformance statements (PCS) and implementation conformance statements (ICS) that must be filled by the vendor. A product claiming conformance must declare which operations and notifications are supported via their ICS.
Caution: Some implementations may deviate from the standard by adding proprietary attributes or operations. While this can increase functionality, it may break interoperability. Always ensure that mandatory elements are fully supported before deploying in a multi-vendor environment.
As of 2026, IEC 10164-7-95 remains a reference for OSI software management, although newer paradigms (e.g., NETCONF/YANG, RESTful management) have gained broader adoption. However, in legacy telecommunication and military systems, this standard is still widely used and maintained.
Q: What is the main purpose of IEC 10164-7-95?
A: It standardizes software management operations (load, install, start, stop, update, remove) in OSI systems management, enabling centralized control of software lifecycle on managed nodes using CMIP/GDMO.
A: It standardizes software management operations (load, install, start, stop, update, remove) in OSI systems management, enabling centralized control of software lifecycle on managed nodes using CMIP/GDMO.
Q: How does IEC 10164-7-95 relate to ISO/IEC 10164-7?
A: IEC 10164-7-95 is the International Electrotechnical Commission designation for the same standard, which is published jointly with ISO as ISO/IEC 10164-7:1995 (confirmed in 2004). The two are technically identical.
A: IEC 10164-7-95 is the International Electrotechnical Commission designation for the same standard, which is published jointly with ISO as ISO/IEC 10164-7:1995 (confirmed in 2004). The two are technically identical.
Q: What are the mandatory operations in a conforming implementation?
A: loadSoftware, installSoftware, startSoftware, stopSoftware, and removeSoftware are mandatory. updateSoftware and dumpSoftware are optional.
A: loadSoftware, installSoftware, startSoftware, stopSoftware, and removeSoftware are mandatory. updateSoftware and dumpSoftware are optional.
Q: Can IEC 10164-7-95 be used with modern management protocols like SNMP?
A: Not directly. The standard is tightly coupled with CMIP and GDMO. To use with SNMP, a mapping must be defined (some organizations have developed MIB modules based on the SWM concepts). However, the standard’s semantics are protocol-independent; newer implementations may adapt the model using YANG or SMI.
A: Not directly. The standard is tightly coupled with CMIP and GDMO. To use with SNMP, a mapping must be defined (some organizations have developed MIB modules based on the SWM concepts). However, the standard’s semantics are protocol-independent; newer implementations may adapt the model using YANG or SMI.
Last updated: 2026