SIST EN IEC 62541-22:2026

SLOVENSKI STANDARD
01-maj-2026
Enotna arhitektura OPC - 22. del: Osnovni model omrežja (IEC 62541-22:2025)
OPC unified architecture - Part 22: Base network model (IEC 62541-22:2025)
OPC Unified Architecture – Teil 22: Basis-Netzwerk-Modelll (IEC 62541-22:2025)
Architecture unifiée OPC - Partie 22: Modèle de réseau de basel (IEC 62541-22:2025)
Ta slovenski standard je istoveten z: EN IEC 62541-22:2026
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN IEC 62541-22

NORME EUROPÉENNE
EUROPÄISCHE NORM February 2026
ICS 25.040
English Version
OPC unified architecture - Part 22: Base Network Model
(IEC 62541-22:2025)
Architecture unifiée OPC - Partie 22: Modèle de réseau de OPC Unified Architecture - Teil 22: Basis-Netzwerk-Modell
base (IEC 62541-22:2025)
(IEC 62541-22:2025)
This European Standard was approved by CENELEC on 2026-01-27. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2026 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62541-22:2026 E

European foreword
The text of document 65E/1047/CDV, future edition 1 of IEC 62541-22, prepared by SC 65E "Devices
and integration in enterprise systems" of IEC/TC 65 "Industrial-process measurement, control and
automation" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2027-02-28
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2029-02-28
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62541-22:2025 was approved by CENELEC as a European
Standard without any modification.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1  Where an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2  Up-to-date information on the latest versions of the European Standards listed in this annex is available
here: www.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 62541-1 - OPC Unified Architecture - Part 1: EN IEC 62541-1 -
Overview and concepts
IEC 62541-5 - OPC Unified architecture - Part 5: EN IEC 62541-5 -
Information Model
IEC 62541-8 - OPC unified architecture - Part 8: Data EN IEC 62541-8 -
access
IEEE 802.3 2022 IEEE Standard for Ethernet - -
IEEE 802.1Q 2018 IEEE Standard for Local and Metropolitan - -
Area Networks - Bridges and Bridged
Networks
IEEE Std 802.1Qcc 2018 EEE Standard for Local and Metropolitan - -
Area Networks-Bridges and Bridged
Networks - Amendment 31: Stream
Reservation Protocol (SRP)
Enhancements and Performance
Improvements
IETF RFC 2863 - The Interfaces Group MIB - -

IEC 62541-22 ®
Edition 1.0 2025-12
INTERNATIONAL
STANDARD
OPC unified architecture –
Part 22: Base Network Model
ICS 25.040  ISBN 978-2-8327-0877-4

IEC 62541-22:2025-12(en)
IEC 62541-22:2025 © IEC 2025
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 7
3 Terms, definitions and abbreviated terms . 7
3.1 Terms and definitions. 7
3.2 Abbreviated terms . 7
4 Concepts . 8
4.1 Type and Naming Conventions . 8
4.2 Usage of OPC UA Interfaces . 8
5 Base Network Model . 8
5.1 Overview . 8
5.2 OPC UA InterfaceTypes . 10
5.2.1 IIetfBaseNetworkInterfaceType Interface . 10
5.2.2 IIeeeBaseEthernetPortType Interface . 11
5.2.3 IIeeeAutoNegotiationStatusType Interface . 11
5.2.4 IBaseEthernetCapabilitiesType Interface . 12
5.2.5 IVlanIdType Interface . 12
5.2.6 ISrClassType Interface . 13
5.2.7 IIeeeBaseTsnStreamType Interface . 14
5.2.8 IIeeeBaseTsnTrafficSpecificationType Interface . 14
5.2.9 IIeeeBaseTsnStatusStreamType Interface . 15
5.2.10 IIeeeTsnInterfaceConfigurationType Interface . 16
5.2.11 IIeeeTsnInterfaceConfigurationTalkerType Interface . 16
5.2.12 IIeeeTsnInterfaceConfigurationListenerType Interface . 17
5.2.13 IIeeeTsnMacAddressType Interface . 17
5.2.14 IIeeeTsnVlanTagType Interface . 18
5.2.15 IPriorityMappingEntryType Interface . 18
5.3 DataTypes . 19
5.3.1 Enumeration DataTypes . 19
5.3.2 Structure DataTypes . 24
5.4 Instance Entry Points . 25
5.4.1 Resources Folder . 26
5.4.2 Communication Folder . 27
5.4.3 MappingTables Folder . 27
5.4.4 NetworkInterfaces Folder . 27
5.4.5 Streams Folder . 28
5.4.6 TalkerStreams Folder . 28
5.4.7 ListenerStreams Folder . 28
5.5 ObjectTypes . 29
5.5.1 IetfBaseNetworkInterfaceType . 29
5.5.2 PriorityMappingTableType . 31
5.6 ReferenceTypes . 34
5.6.1 UsesPriorityMappingTable ReferenceType . 34
5.6.2 HasLowerLayerInterface ReferenceType . 35
Annex A (informative) Modelling Examples . 36
A.1 Modelling Examples for Network Interfaces . 36
IEC 62541-22:2025 © IEC 2025
A.1.1 Virtual Network Interfaces . 36
A.1.2 Link Aggregation . 37
A.2 Modelling Examples for PriorityMappingEntries and
IetfBaseNetworkInterface . 37
A.3 Usage of BNM in other UA Specifications . 39
A.3.1 Usage of BNM for PubSub over TSN . 39
A.3.2 Usage of BNM in PROFINET Companion Spec . 39

Figure 1 – Scope of Base Network Model . 6
Figure 2 – Overview of Base Network Model . 9
Figure 3 – Instance Entry Points for Network Interfaces and Streams . 26
Figure 4 – IetfBaseNetworkInterfaceType . 29
Figure 5 – PriorityMappingTableType . 31
Figure A.1 – Modelling Example for virtual network interfaces . 36
Figure A.2 – Modelling example for link aggregation . 37
Figure A.3 – Modelling Example for PriorityMappingTableType and
IetfBaseNetworkInterface . 38
Figure A.4 – Possible Integration of BNM into PubSub . 39
Figure A.5 – Recommended Integration of BNM into Companion Spec exemplified by
PROFINET . 39

Table 1 – IIetfBaseNetworkInterfaceType definition . 10
Table 2 – IIetfBaseNetworkInterfaceType Attribute values for child Nodes . 10
Table 3 – IIeeeBaseEthernetPortType definition . 11
Table 4 – IIeeeBaseEthernetPortType Attribute values for child Nodes . 11
Table 5 – IIeeeAutoNegotiationStatusType definition . 12
Table 6 – IBaseEthernetCapabilitiesType definition . 12
Table 7 – IVlanIdType definition . 13
Table 8 – ISrClassType definition . 13
Table 9 – IIeeeBaseTsnStreamType definition . 14
Table 10 – IIeeeBaseTsnTrafficSpecificationType definition . 15
Table 11 – IIeeeBaseTsnStatusStreamType definition . 15
Table 12 – IIeeeTsnInterfaceConfigurationType definition . 16
Table 13 – IIeeeTsnInterfaceConfigurationTalkerType definition . 16
Table 14 – IIeeeTsnInterfaceConfigurationListenerType definition . 17
Table 15 – IIeeeTsnMacAddressType definition . 17
Table 16 – IIeeeTsnVlanTagType definition . 18
Table 17 – IPriorityMappingEntryType definition . 18
Table 18 – Duplex Values . 19
Table 19 – Duplex Definition . 19
Table 20 – InterfaceAdminStatus Values . 20
Table 21 – InterfaceAdminStatus Definition . 20
Table 22 – InterfaceOperStatus Values . 20
Table 23 – InterfaceOperStatus Definition. 21
Table 24 – NegotiationStatus Values . 21
IEC 62541-22:2025 © IEC 2025
Table 25 – NegotiationStatus Definition . 21
Table 26 – TsnFailureCode values . 22
Table 27 – TsnFailureCode Definition . 22
Table 28 – TsnStreamState Values . 23
Table 29 – TsnStreamState Definition . 23
Table 30 – TsnTalkerStatus Values . 23
Table 31 – TsnTalkerStatus Definition . 24
Table 32 – TsnListenerStatus Values . 24
Table 33 – TsnListenerStatus Definition . 24
Table 34 – PriorityMappingEntryType structure . 25
Table 35 – PriorityMappingEntryType Definition . 25
Table 36 – Resources definition . 26
Table 37 – Communication definition . 27
Table 38 – MappingTables definition . 27
Table 39 – NetworkInterfaces definition . 28
Table 40 – Streams definition . 28
Table 41 – TalkerStreams definition . 28
Table 42 – ListenerStreams definition . 29
Table 43 – IetfBaseNetworkInterfaceType definition. 30
Table 44 – IetfBaseNetworkInterfaceType Attribute values for child Nodes . 31
Table 45 – IetfBaseNetworkInterfaceType Additional References . 31
Table 46 – PriorityMappingTableType definition . 32
Table 47 – AddPriorityMappingEntry Method arguments . 33
Table 48 – AddPriorityMappingEntry Method result codes . 33
Table 49 – AddPriorityMappingEntry Method AddressSpace definition . 33
Table 50 – DeletePriorityMappingEntry Method arguments . 33
Table 51 – DeletePriorityMappingEntry Method result codes . 34
Table 52 – DeletePriorityMappingEntry Method AddressSpace definition . 34
Table 53 – UsesPriorityMappingTable definition. 34
Table 54 – HasLowerLayerInterface definition . 35

IEC 62541-22:2025 © IEC 2025
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
OPC unified architecture -
Part 22: Base Network Model
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC 62541-22 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/1047/CDV 65E/1104/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
IEC 62541-22:2025 © IEC 2025
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
Throughout this document and the other Parts of the series, certain document conventions are
used:
Italics are used to denote a defined term or definition that appears in the "Terms and definitions"
clause in one of the parts of the series.
Italics are also used to denote the name of a service input or output parameter or the name of
a structure or element of a structure that are usually defined in tables.
The italicized terms and names are also often written in camel-case (the practice of writing
compound words or phrases in which the elements are joined without spaces, with each
element's initial letter capitalized within the compound). For example, the defined term is
AddressSpace instead of Address Space. This makes it easier to understand that there is a
single definition for AddressSpace, not separate definitions for Address and Space.
A list of all parts in the IEC 62541 series, published under the general title OPC Unified
Architecture, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
– reconfirmed,
– withdrawn, or
– revised.
IEC 62541-22:2025 © IEC 2025
1 Scope
This part of IEC 62541 specifies an OPC UA Information Model for a basic set of network related
components used in other Information Models.
The initial version of this document defines parameter sets for TSN Talkers and Listeners as
well as network interfaces and ports as shown in Figure 1. A future version of this document is
expected to have a broader scope of other network technologies than Ethernet only.

Figure 1 – Scope of Base Network Model
IEC 62541-22:2025 © IEC 2025
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62541-1, OPC Unified Architecture - Part 1: Overview and Concepts
IEC 62541-5, OPC Unified Architecture - Part 5: Information Model
IEC 62541-8, OPC Unified Architecture - Part 8: Data Access
IEEE Std 802.3-2022, IEEE Standard for Ethernet
IEEE Std 802.1Q-2018, IEEE Standard for Local and Metropolitan Area Networks Bridges and
Bridged Networks
IEEE Std 802.1Qcc-2018, EEE Standard for Local and Metropolitan Area Networks-Bridges and
Bridged Networks - Amendment 31: Stream Reservation Protocol (SRP) Enhancements and
Performance Improvements
IETF RFC 2863, K. McCloghrie, "The Interfaces Group MIB", June 2000, available at
https://tools.ietf.org/html/rfc2863
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-1, IEC 62541-5
and IEC 62541-8 apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
– IEC Electropedia: available at https://www.electropedia.org/
– ISO Online browsing platform: available at https://www.iso.org/obp
3.2 Abbreviated terms
AVB Audio Video Bridging
BNM Base Network Model
CNC Centralized Network Configuration
CUC Centralized User Configuration
DSCP Differentiated services code point for packet classification purposes
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
MAU Medium Attachment Units
MIB Management Information Base
PCP Priority Code Point for classifying and managing network traffic
TSN Time Sensitive Networks
VLAN Virtual Local Area Network
YANG Yet Another Next Generation (Data modelling language for network management)
IEC 62541-22:2025 © IEC 2025
4 Concepts
4.1 Type and Naming Conventions
The BNM shall align its parameters to existing standards defined by IETF and the IEEE to allow
an effortless mapping against existing network technologies. Therefore, selected DataTypes
shall fit to the types used by the related managed objects of IEEE and IETF. BrowseNames of
Variables and parameter sets (UA interface) are preferably derived from standardized IETF /
IEEE YANG models. If no standardized YANG representation is available, MIB definitions are
chosen.
4.2 Usage of OPC UA Interfaces
The parameters of the BNM are grouped in the form of OPC UA Interfaces. Interfaces have
been chosen to define parameter sets independent of the implementation in future ObjectType
hierarchies. This allows these grouped parameters to be used in other Information Models
independent of ObjectType hierarchies that can be found in the BNM.
It is expected that a future version of the BNM will define a collection of network related
ObjectTypes.
5 Base Network Model
5.1 Overview
The Base Network Model defined in this document is shown in Figure 2.
IEC 62541-22:2025 © IEC 2025
Figure 2 – Overview of Base Network Model
IEC 62541-22:2025 © IEC 2025
5.2 OPC UA InterfaceTypes
5.2.1 IIetfBaseNetworkInterfaceType Interface
This OPC UA Interface defines the basis of an IETF network interface. The
IIetfBaseNetworkInterfaceType is formally defined in Table 1.
Table 1 – IIetfBaseNetworkInterfaceType definition
Attribute Value
BrowseName IIetfBaseNetworkInterfaceType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable AdminStatus InterfaceAdminStatus BaseDataVariableType Mandatory
HasComponent Variable OperStatus InterfaceOperStatus BaseDataVariableType Mandatory
HasComponent Variable PhysAddress String BaseDataVariableType Optional
HasComponent Variable Speed UInt64 AnalogUnitType Mandatory
Conformance Units
BNM Ethernet Base Info
AdminStatus of DataType InterfaceAdminStatus specifies the desired state of the network
interface. This Variable has the same read semantics as ifAdminStatus (ifAdminStatus is
defined in IETF RFC 2863). The InterfaceAdminStatus Enumeration is defined in 5.3.1.2.
OperStatus of DataType InterfaceOperStatus specifies the current operational state of the
network interface. This Variable has the same semantics as ifOperStatus (ifOperStatus is
defined in IETF RFC 2863). The InterfaceOperStatus Enumeration is defined in 5.3.1.3.
PhysAddress of DataType String specifies the network interface's address at its protocol sub-
layer. For example, for an 802.x network interface, this parameter normally contains a Media
Access Control (MAC) address. The network interface's media-specific modules must define
the bit and byte ordering and the format of the value of this object. For network interfaces that
do not have such an address (e.g., a serial line), this node is not present (ifPhysAddress is
defined in IETF RFC 2863).
Speed of DataType UInt64 specifies an estimate of the network interface's current bandwidth
in bits per second. For network interfaces that do not vary in bandwidth or for those where no
accurate estimation can be made, this value should contain the nominal bandwidth (ifSpeed,
ifHighSpeed are defined in IETF RFC 2863).
The component Variables of the IIetfBaseNetworkInterfaceType have the Attribute values
defined in Table 2.
Table 2 – IIetfBaseNetworkInterfaceType Attribute values for child Nodes
Source Path Value Attribute Description Attribute
NamespaceUri: -
Speed
http://www.opcfoundation.org/UA/units/un/cefact
EngineeringUnits
UnitId: 4337968
DisplayName: bit/s
Description: bit per second
IEC 62541-22:2025 © IEC 2025
5.2.2 IIeeeBaseEthernetPortType Interface
This OPC UA Interface defines capabilities of an Ethernet-based port. The
IIeeeBaseEthernetPortType is formally defined in Table 3.
Table 3 – IIeeeBaseEthernetPortType definition
Attribute Value
BrowseName IIeeeBaseEthernetPortType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable Speed UInt64 AnalogUnitType Mandatory
HasComponent Variable Duplex Duplex BaseDataVariableType Mandatory
HasComponent Variable MaxFrameLength UInt16 BaseDataVariableType Mandatory
Conformance Units
BNM Ethernet Base Info
Speed of DataType UInt64 specifies the configured, negotiated, or actual speed of an Ethernet
port in entities of 1 Mb/s (data rate). The default value is implementation-dependent (Ethernet
ports are defined in IEEE Std 802.3-2022).
Duplex of DataType Duplex represents the configured, negotiated, or actual duplex mode of an
Ethernet port ("aDuplexStatus is defined in IEEE Std 802.3-2022, 30.3.1.1.32, "). The Duplex
DataType is defined in 5.3.1.1.
MaxFrameLength of DataType UInt16 indicates the MAC frame length (including FCS bytes) at
which frames are dropped for being too long ("aMaxFrameLength" is defined in
IEEE Std 802.3-2022, 30.3.1.1.37,).
The component Variables of the IIeeeBaseEthernetPortType have the Attribute values defined
in Table 4.
Table 4 – IIeeeBaseEthernetPortType Attribute values for child Nodes
Source Path Value Attribute Description Attribute
NamespaceUri: -
Speed
http://www.opcfoundation.org/UA/units/un/cefact
EngineeringUnits
UnitId: 4534832
DisplayName: Mbit/s
Description: megabit per second

5.2.3 IIeeeAutoNegotiationStatusType Interface
This OPC UA Interface defines the auto negotiation status of an Ethernet-based port. The
IIeeeAutoNegotiationStatusType is formally defined in Table 5.
IEC 62541-22:2025 © IEC 2025
Table 5 – IIeeeAutoNegotiationStatusType definition
Attribute Value
BrowseName IIeeeAutoNegotiationStatusType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling
Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable NegotiationStatus NegotiationStatus BaseDataVariableType Mandatory
Conformance Units
BNM AutoNeg
NegotiationStatus of DataType NegotiationStatus specifies the status of the auto-negotiation
protocol (the auto-negotiation protocol is defined in IEEE Std 802.3-2022:…., 30.6.1.1.4,
"aAutoNegAutoConfig"). The NegotiationStatus DataType is defined in 5.3.1.4.
5.2.4 IBaseEthernetCapabilitiesType Interface
This OPC UA Interface defines if an Ethernet-based port is VLAN Tag capable. The
IBaseEthernetCapabilitiesType is formally defined in Table 6.
Table 6 – IBaseEthernetCapabilitiesType definition
Attribute Value
BrowseName IBaseEthernetCapabilitiesType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable VlanTagCapable Boolean BaseDataVariableType Mandatory
Conformance Units
BNM VLAN Capabilities
When VlanTagCapable is true, the network interface supports the ability to tag/untag frames
using a Customer VLAN Tag (C-TAG of clause 9) provided by the network (VLAN Tags are
defined in IEEE Std 802.1Qcc-2018, 46.2.3.7.1.).
5.2.5 IVlanIdType Interface
This OPC UA Interface specifies a VLAN Id associated with a network interface. The
IVlanIdType is formally defined in Table 7.
IEC 62541-22:2025 © IEC 2025
Table 7 – IVlanIdType definition
Attribute Value
BrowseName IVlanIdType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable VlanId UInt16 BaseDataVariableType Mandatory
Conformance Units
BNM IETF Interface Vlan Info
VlanId is an UInt16 and contains the Customer VLAN Tag (IEEE Std 802.1Q-2018 C-TAG of
Clause 9) that frames injected at this network interface will be tagged with (see
IEEE Std 802.1Qcc-2018, 46.2.3.7.1).
5.2.6 ISrClassType Interface
This OPC UA Interface defines the content of an SrClass. The ISrClassType is formally defined
in Table 8.
Table 8 – ISrClassType definition
Attribute Value
BrowseName ISrClassType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable Id Byte BaseDataVariableType Mandatory
HasComponent Variable Priority Byte BaseDataVariableType Mandatory
HasComponent Variable Vid UInt16 BaseDataVariableType Mandatory
Conformance Units
BNM TSN Base Info
Id is a Byte and specifies the SRclassID in a numeric representation of the SR classes which
is supported by a particular Bridge Port (SRclassID is defined in IEEE Std 802.1Q-2018,
35.2.2.9.2,). Only values between 0 and 7 shall be used.
Priority is a Byte and holds the Data Frame Priority (item a) in IEEE Std 802.1Q-2018,
35.2.2.8.5) value that will be used for streams that belong to the associated SR class.
(SRclassPriority is defined in IEEE Std 802.1Q-2018, 35.2.2.9.3). Only Values between 0 and
7 shall be used.
Vid is an UInt16 and contains the SR_PVID (item i) in IEEE Std 802.1Q-2018, 35.2.1.4) that the
associated streams will be tagged with by the Talker (SRclassVID is defined in
IEEE Std 802.1Q-2018, 35.2.2.9.4).
IEC 62541-22:2025 © IEC 2025
5.2.7 IIeeeBaseTsnStreamType Interface
The IIeeeBaseTsnStreamType contains Variables which are common for both TSN talkers and
TSN listeners. They represent the configuration properties and diagnostic values like
reservation status and failure codes of a TSN stream. The IIeeeBaseTsnStreamType is formally
defined Table 9.
Table 9 – IIeeeBaseTsnStreamType definition
Attribute Value
BrowseName IIeeeBaseTsnStreamType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable StreamId Byte[8] BaseDataVariableType Mandatory
HasComponent Variable StreamName String BaseDataVariableType Mandatory
HasComponent Variable State TsnStreamState BaseDataVariableType Mandatory
HasComponent Variable AccumulatedLatency UInt32 BaseDataVariableType Optional
HasComponent Variable SrClassId Byte BaseDataVariableType Optional
Conformance Units
BNM TSN Base Info
StreamId is an array of 8 Bytes defined according to the StreamID in IEEE Std 802.1Qcc-2018,
35.2.2.8.2. The StreamId shall be unique in the scope of the related TSN Network. The mapping
between the StreamId Byte array and the IEEE octet string StreamID is as follows: Entry[n] of
StreamId is mapped to octet[n] of StreamID. The StreamId shall be provided in the TSN stream
Objects for diagnostic reasons.
NOTE In the distributed configuration model, the StreamId is typically generated by the TSN control stack of the
endstation. In the fully centralized configuration model, the StreamId is typically generated by the CUC.
StreamName is a String identifying the related stream in the network. The format of the String
is application specific. The uniqueness of the StreamName inside the network segment shall
be guaranteed by the application. If multiple applications use the network segment, they shall
agree on a naming scheme.
State represents the current state of the TSN configuration process of a TSN stream. The
TsnStreamState Enumeration is defined in 5.3.1.6.
AccumulatedLatency of DataType UInt32 is the maximum worst case propagation delay in
nanoseconds calculated and guaranteed by the TSN Control Layer for this Listener. Once the
stream reservation has succeeded the AccumulatedLatency is not expected to increase during
the lifecycle of the TSN Stream (see IEEE Std 802.1Q-2018, 35.2.2.8.6).
SrClassId of DataType Byte contains the Stream Reservation Class that is used for this stream
(see IEEE Std 802.1Qcc-2018, 35.2.2.9.2).
5.2.8 IIeeeBaseTsnTrafficSpecificationType Interface
This OPC UA Interface is used to represent the traffic specification of a TSN stream. The
IIeeeBaseTsnTrafficSpecificationType is formally defined in Table 10.
IEC 62541-22:2025 © IEC 2025
Table 10 – IIeeeBaseTsnTrafficSpecificationType definition
Attribute Value
BrowseName IIeeeBaseTsnTrafficSpecificationType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition Modelling
Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable MaxIntervalFrames UInt16 BaseDataVariableType Mandatory
HasComponent Variable MaxFrameSize UInt32 BaseDataVariableType Mandatory
HasComponent Variable Interval UnsignedRationalNumber BaseDataVariableType Mandatory
Conformance Units
BNM TSN Config
The MaxFrameSize of DataType UInt16 specifies the maximum size frame that will be sent by
a Talker for this Stream (see IEEE Std 802.1Q-2018, 35.2.2.8.4a).
NOTE According to 802.1Q MaxFrameSize only counts the number of bytes of the Ethernet payload without the
media specific framing bytes. (i.e. without 8-byte preamble, 14-byte IEEE 802.3 header, 4-byte IEEE 802.1Q
priority/VID Tag, 4-byte CRC, 12-byte inter frame gap). Same rules apply for counting MaxBytesPerInterval.
The MaxIntervalFrames of DataType UInt16 Variable specifies the maximum number of frames
that will be sent during an Interval. (see IEEE Std 802.1Q-2018, 35.2.2.8.4b,
"MaxIntervalFrames" or IEEE Std 802.1Qcc-2018, 35.2.2.10.6, "MaxFramesPerInterval")
Interval of DataType UnsignedRationalNumber defines the time period of the TSN Stream in
nanoseconds. In that interval a specified number of frames (MaxIntervalFrames) with a
maximum payload size per frame (MaxFrameSize) and a maximum total number of bytes
(MaxBytesPerInterval) will be transmitted. The Interval therefore shall either represent the
"class measurement interval" as used for AVB based Streams (see IEEE Std 802.1Q-2018,
Clause 35 or the "Interval" parameter used in the TrafficSpecification group in
IEEE Std 802.1Qcc-2018, 46.2.3.5.1).
5.2.9 IIeeeBaseTsnStatusStreamType Interface
This OPC UA Interface is used to represent the status of a TSN stream. The
IIeeeBaseTsnStatusStreamType is formally defined in Table 11.
Table 11 – IIeeeBaseTsnStatusStreamType definition
Attribute Value
BrowseName IIeeeBaseTsnStatusStreamType
IsAbstract True
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable TalkerStatus TsnTalkerStatus BaseDataVariableType Optional
HasComponent Variable ListenerStatus TsnListenerStatus BaseDataVariableType Optional
HasComponent Variable FailureCode TsnFailureCode BaseDataVariableType Mandatory
HasComponent Variable FailureSystemIdentifier Byte[][8] BaseDataVariableType Mandatory
Conformance Units
BNM TSN Base Info
IEC 62541-22:2025 © IEC 2025
TalkerStatus of DataType TsnTalkerStatus contains the Reservation Failure Code as defined
in the "FailureInformation" in IEEE Std 802.1Qcc-2018, 46.2.5.1.1.
ListenerStatus of DataType TsnListenerStatus
...