IEC 62541-4:2020

Overview

IEC 62541-4:2020 (OPC Unified Architecture - Part 4: Services) defines the OPC UA Services: the abstract Remote Procedure Calls (RPCs) that OPC UA Clients invoke and OPC UA Servers implement. This third edition (2020) replaces the 2015 edition and provides a technical revision of the Service definitions used for all client–server interactions in OPC UA. The document describes Services at an abstract level (no specific transport mandated); concrete mappings (for example to XML Web Services) are specified in IEC 62541-6. Profile requirements that determine which Services are mandatory are defined in IEC 62541-7.

Key topics and technical requirements

• Abstract Service model: Defines request/response procedures, Service Sets (Discovery, SecureChannel, Session, NodeManagement, View, Attribute, Subscription, MonitoredItem, Method, Query, etc.), headers, and results.
• Security and Authorization: Guidance on SecureChannel and Session creation, user impersonation, and Authorization Services; added mechanisms for obtaining user access tokens and defending against user identity token attacks.
• Identity tokens: Adds JSON Web Tokens (JWTs) as a supported user token and introduces a new EncryptedSecret format for user identity tokens.
• Subscriptions and monitoring: Enhancements include ResendData to resend monitored-item data, support for durable Subscriptions (long-lived subscriptions across hours/days), and changes to Publish/Republish behavior.
• Discovery enhancements: New Register2 and FindServersOnNetwork Services to enable network-wide discovery with capability filters.
• Redundancy and reliability: Extended redundancy definitions and additional ServiceLevel sub-ranges to support high-availability server/client configurations.
• Session-less invocation: Introduces a model for invoking some Services without creating a full Session.
• Node management extension: Generic structure enabling multiple attributes to be passed to the AddNodes Service.
• Operational protections: New requirements to protect against token attacks and removal of software certificate definitions (to be re-introduced in a future edition).

Applications and who uses it

• OPC UA Server and Client developers use IEC 62541-4 to implement compliant Service behavior, request/response semantics, and security expectations.
• System integrators and automation engineers apply the Services model when designing reliable, discoverable, and secure industrial systems.
• Vendors of industrial IoT, SCADA, and IIoT platforms adopt the Services to ensure interoperability across devices and systems.
• Cybersecurity teams reference the document for secure channel/session practices, token management, and auditing requirements.
• Use cases include real-time data access, historical data read/write, device discovery, event monitoring, and multi-vendor interoperability in manufacturing, energy, and process industries.

Related standards

• IEC 62541-6 - OPC UA Mappings (concrete transport mappings such as XML Web Services)
• IEC 62541-7 - OPC UA Profiles (which Services are required for compliance)
• Refer to the broader IEC 62541 (OPC UA) series for additional parts (architecture, information model, security, etc.).