oSIST prEN IEC 62541-22:2024

SLOVENSKI STANDARD
01-marec-2024
Enotna arhitektura OPC - 22. del: Osnovni mrežni model
OPC unified architecture - Part 22: Base network model
Ta slovenski standard je istoveten z: prEN IEC 62541-22:2024
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.

65E/1047/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62541-22 ED1
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2024-01-26 2024-04-19
SUPERSEDES DOCUMENTS:
65E/957/NP, 65E/1017/RVN
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:

Other TC/SCs are requested to indicate their interest, if any,
in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for
Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which
they are aware and to provide supporting documentation.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some Countries”
clauses to be included should this proposal proceed. Recipients are reminded that the CDV stage is the final stage for
submitting ISC clauses. (SEE AC/22/2007 OR NEW GUIDANCE DOC).

TITLE:
OPC Unified Architecture – Part 22: Base Network Model

PROPOSED STABILITY DATE: 2026
NOTE FROM TC/SC OFFICERS:
electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.
You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without
permission in writing from IEC.

IEC CDV 62541-22 © IEC 2023
1 CONTENTS
2 Page
4 1 Scope . 1
5 2 Normative references . 1
6 3 Terms, definitions, abbreviated terms, and conventions . 2
7 Terms and definitions . 2
8 Abbreviated terms . 2
9 4 Concepts . 2
10 Type and Naming Conventions . 2
11 Usage of OPC UA Interfaces . 2
12 5 Base Network Model . 3
13 Overview. 3
14 OPC UA InterfaceTypes . 5
15 IIetfBaseNetworkInterfaceType Interface . 5
16 IIeeeBaseEthernetPortType Interface . 6
17 IIeeeAutoNegotiationStatusType Interface . 6
18 IBaseEthernetCapabilitiesType Interface . 7
19 IVlanIdType Interface . 7
20 ISrClassType Interface . 7
21 IIeeeBaseTsnStreamType Interface . 8
22 IIeeeBaseTsnTrafficSpecificationType Interface . 9
23 IIeeeBaseTsnStatusStreamType Interface. 9
24 IIeeeTsnInterfaceConfigurationType Interface . 10
25 IIeeeTsnInterfaceConfigurationTalkerType Interface . 10
26 IIeeeTsnInterfaceConfigurationListenerType Interface. 10
27 IIeeeTsnMacAddressType Interface . 11
28 IIeeeTsnVlanTagType Interface . 11
29 IPriorityMappingEntryType Interface . 11
30 DataTypes . 12
31 Enumeration DataTypes . 12
32 Structure DataTypes . 17
33 Instance Entry Points . 17
34 Resources Folder . 18
35 Communication Folder . 18
36 MappingTables Folder . 19
37 NetworkInterfaces Folder . 19
38 Streams Folder . 19
39 TalkerStreams Folder . 20
40 ListenerStreams Folder . 20
41 ObjectTypes. 20
42 IetfBaseNetworkInterfaceType . 20
43 PriorityMappingTableType . 22
44 ReferenceTypes . 24
45 UsesPriorityMappingTable ReferenceType . 24
46 HasLowerLayerInterface ReferenceType . 25
47 Annex A Modelling Examples (informative) . 26
48 A.1 Modelling Examples for Network Interfaces . 26
49 A.1.1 Virtual Network Interfaces . 26
50 A.1.2 Link Aggregation . 27

ii IEC CDV 62541-22 © IEC 2023

51 A.2 Modelling Examples for PriorityMappingEntries and IetfBaseNetworkInterface . 27
52 A.3 Usage of BNM in other UA Specifications . 29
53 A.3.1 Usage of BNM for PubSub over TSN . 29
54 A.3.2 Usage of BNM in PROFINET Companion Spec . 29
iii IEC CDV 62541-22 © IEC 2023

57 Figures
59 Figure 1 – Scope of Base Network Model . 1
60 Figure 2 – Overview of Base Network Model . 4
61 Figure 3 – Instance Entry Points for Network Interfaces and Streams . 18
62 Figure 4 – IetfBaseNetworkInterfaceType . 21
63 Figure 5 – PriorityMappingTableType . 22
64 Figure A-1 – Modelling Example for virtual network interfaces . 26
65 Figure A-2 – Modelling example for link aggregation . 27
66 Figure A-3 – Modelling Example for PriorityMappingTableType and IetfBaseNetworkInterface28
67 Figure A-4 – Possible Integration of BNM into PubSub . 29
68 Figure A-5 – Recommended Integration of BNM into Companion Spec exemplified by
69 PROFINET . 29
iv IEC CDV 62541-22 © IEC 2023

72 Tables
73 Table 1 – IIetfBaseNetworkInterfaceType definition . 5
74 Table 2 – IIetfBaseNetworkInterfaceType Attribute values for child Nodes . 5
75 Table 3 – IIeeeBaseEthernetPortType definition . 6
76 Table 4 – IIeeeBaseEthernetPortType Attribute values for child Nodes . 6
77 Table 5 – IIeeeAutoNegotiationStatusType definition . 6
78 Table 6 – IBaseEthernetCapabilitiesType definition . 7
79 Table 7 – IVlanIdType definition . 7
80 Table 8 – ISrClassType definition . 7
81 Table 9 – IIeeeBaseTsnStreamType definition . 8
82 Table 10 – IIeeeBaseTsnTrafficSpecificationType definition . 9
83 Table 11 – IIeeeBaseTsnStatusStreamType definition . 9
84 Table 12 – IIeeeTsnInterfaceConfigurationType definition . 10
85 Table 13 – IIeeeTsnInterfaceConfigurationTalkerType definition . 10
86 Table 14 – IIeeeTsnInterfaceConfigurationListenerType definition . 10
87 Table 15 – IIeeeTsnMacAddressType definition . 11
88 Table 16 – IIeeeTsnVlanTagType definition . 11
89 Table 17 – IPriorityMappingEntryType definition . 12
90 Table 18 – Duplex Values . 12
91 Table 19 – Duplex Definition. 12
92 Table 20 – InterfaceAdminStatus Values . 13
93 Table 21 – InterfaceAdminStatus Definition . 13
94 Table 22 – InterfaceOperStatus Values . 13
95 Table 23 – InterfaceOperStatus Definition . 13
96 Table 24 – NegotiationStatus Values . 14
97 Table 25 – NegotiationStatus Definition . 14
98 Table 26 – TsnFailureCode values . 15
99 Table 27 – TsnFailureCode Definition . 15
100 Table 28 – TsnStreamState Values . 16
101 Table 29 – TsnStreamState Definition . 16
102 Table 30 – TsnTalkerStatus Values . 16
103 Table 31 – TsnTalkerStatus Definition . 16
104 Table 32 – TsnListenerStatus Values . 17
105 Table 33 – TsnListenerStatus Definition . 17
106 Table 34 – PriorityMappingEntryType structure . 17
107 Table 35 – PriorityMappingEntryType Definition . 17
108 Table 36 – Resources definition . 18
109 Table 37 – Communication definition . 19
110 Table 38 – MappingTables definition . 19
111 Table 39 – NetworkInterfaces definition . 19
112 Table 40 – Streams definition . 20
113 Table 41 – TalkerStreams definition . 20
114 Table 42 – ListenerStreams definition. 20
115 Table 43 – IetfBaseNetworkInterfaceType definition . 21

v IEC CDV 62541-22 © IEC 2023
116 Table 44 – IetfBaseNetworkInterfaceType Attribute values for child Nodes . 22
117 Table 45 – IetfBaseNetworkInterfaceType Additional References . 22
118 Table 46 – PriorityMappingTableType definition . 22
119 Table 47 – AddPriorityMappingEntry Method arguments . 23
120 Table 48 – AddPriorityMappingEntry Method result codes . 23
121 Table 49 – AddPriorityMappingEntry Method AddressSpace definition. 24
122 Table 50 – DeletePriorityMappingEntry Method arguments . 24
123 Table 51 – DeletePriorityMappingEntry Method result codes . 24
124 Table 52 – DeletePriorityMappingEntry Method AddressSpace definition. 24
125 Table 53 – UsesPriorityMappingTable definition . 25
126 Table 54 – HasLowerLayerInterface definition . 25
vi IEC CDV 62541-22 © IEC 2023

129 INTERNATIONAL ELECTROTECHNICAL COMMISSION
130 ____________
132 OPC UNIFIED ARCHITECTURE –
134 Part 22: Base Network Model
136 FOREWORD
137 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national
138 electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all
139 questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities,
140 IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS)
141 and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC
142 National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental
143 and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with
144 the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between
145 the two organizations.
146 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus
147 of opinion on the relevant subjects since each technical committee has representation from all interested IEC National
148 Committees.
149 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in
150 that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC
151 cannot be held responsible for the way in which they are used or for any misinterpretation by any end user.
152 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to
153 the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and
154 the corresponding national or regional publication shall be clearly indicated in the latter.
155 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment
156 services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out by
157 independent certification bodies.
158 6) All users should ensure that they have the latest edition of this publication.
159 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of
160 its technical committees and IEC National Committees for any personal injury, property damage or other damage of any
161 nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication,
162 use of, or reliance upon, this IEC Publication or any other IEC Publications.
163 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable
164 for the correct application of this publication.
165 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights.
166 IEC shall not be held responsible for identifying any or all such patent rights.
167 The main task of IEC technical committees is to prepare International Standards. However, a technical
168 committee may propose the publication of a technical report when it has collected data of a different
169 kind from that which is normally published as an International Standard, for example "state of the art".
170 International Standard IEC 62541-22 has been prepared by subcommittee 65E: Devices and integration
171 in enterprise systems, of IEC technical committee 65: Industrial-process measurement, control and
172 automation.
173 The text of this international standard is based on the following documents:
CDV Report on voting
65E/XX/CDV 65E/XX/RVC
175 Full information on the voting for the approval of this international standard can be found in the report
176 on voting indicated in the above table.
177 This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
178 Throughout this document and the other Parts of the series, certain document conventions are used:

vii IEC CDV 62541-22 © IEC 2023

179 Italics are used to denote a defined term or definition that appears in the “Terms and definition” clause
180 in one of the parts of the series.
181 Italics are also used to denote the name of a service input or output parameter or the name of a structure
182 or element of a structure that are usually defined in tables.
183 The italicized terms and names are also often written in camel-case (the practice of writing compound
184 words or phrases in which the elements are joined without spaces, with each element's initial letter
185 capitalized within the compound). For example, the defined term is AddressSpace instead of Address
186 Space. This makes it easier to understand that there is a single definition for AddressSpace, not
187 separate definitions for Address and Space.
188 A list of all parts of the IEC 62541 series is included in IEC 62541-1 clause 4 Structure of the OPC UA
189 series and published under the general title OPC Unified Architecture, can be found on the IEC website.
190 The committee has decided that the contents of this publication will remain unchanged until the stability
191 date indicated on the IEC web site under "http://webstore.iec.ch" in the data related to the specific
192 publication. At this date, the publication will be
193 • reconfirmed,
194 • withdrawn,
195 • replaced by a revised edition, or
196 • amended.
198 A bilingual version of this publication may be issued at a later date.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.
1 IEC CDV 62541-22 © IEC 2023
205 1 Scope
206 The Base Network Model (BNM) specifies an OPC UA Information Model for a basic set of network
207 related components to be used in other Information Models.
208 The initial version defines parameter sets for TSN Talkers and Listeners as well as network interfaces
209 and ports as shown in Figure 1. A future version of this document is expected to have a broader scope
210 of other network technologies than Ethernet only.
Host
Application
OPC Server
Server
Base Network Model
Resources
Communication
Streams
IIeeeBaseTsnStreamType
TsnTalker1
IIeeeBaseTsnStatusStreamType
TsnListener2
NetworkInterfaces
IIetfBaseNetworkInterfaceType
NwInterfaceA
IIeeeBaseEthernetPortType
NwInterfaceB
Local
TSN TSN
TsnListene
TsnTalker
Network
Talker1 Listener2
r
Stack
Network Network
Interface A Interface B
Port Port Port
212 Figure 1 – Scope of Base Network Model
213 2 Normative references
214 The following referenced documents are indispensable for the application of this OPC UA part. For
215 dated references, only the edition cited applies. For undated references, the latest edition of the
216 referenced document (including any amendments and errata) applies.

2 IEC CDV 62541-22 © IEC 2023
217 IEC 62541-1, OPC Unified Architecture – Part 1: Overview and Concepts
218 IEC 62541-5, OPC Unified Architecture – Part 5: Information Model
219 IEC 62541-8, OPC Unified Architecture – Part 8: Data Access
221 IEEE Std 802.3, ETHERNET
222 http://www.ieee802.org/3/
223 IEEE 802.1Q-2018, IEEE Standard for Local and Metropolitan Area Networks Bridges and Bridged
224 Networks
225 http://www.ieee802.org/1/
226 IEEE 802.1Qcc-2018, Bridges and Bridged Networks, Amendment: Stream Reservation Protocol
227 (SRP) Enhancements and Performance Improvements
228 http://www.ieee802.org/1/
229 IETF RFC 2863, The Interfaces Group MIB
230 https://tools.ietf.org/html/rfc2863
231 3 Terms, definitions, abbreviated terms, and conventions
232 Terms and definitions
233 For the purposes of this document, the terms and definitions given in IEC 62541-1, IEC 62541-5 and
234 IEC 62541-8 apply.
235 All used terms are italicized in this document.
236 Abbreviated terms
237 AVB Audio Video Bridging
238 BNM Base Network Model
239 CNC Centralized Network Configuration
240 CUC Centralized User Configuration
241 DSCP Differentiated services code point for packet classification purposes
242 IEEE Institute of Electrical and Electronics Engineers
243 IETF Internet Engineering Task Force
244 MAU Medium Attachment Units
245 MIB Management Information Base
246 PCP Priority Code Point for classifying and managing network traffic
247 TSN Time Sensitive Networks
248 VLAN Virtual Local Area Network
249 YANG Yet Another Next Generation (Data modelling language for network management)
250 4 Concepts
251 Type and Naming Conventions
252 The BNM shall align its parameters to existing standards defined by IETF and the IEEE to allow an
253 effortless mapping against existing network technologies. Therefore, selected DataTypes shall fit to
254 the types used by the related managed objects of IEEE and IETF. BrowseNames of Variables and
255 parameter sets (UA interface) are preferably derived from standardized IETF / IEEE YANG models. If
256 no standardized YANG representation is available, MIB definitions are chosen.
257 Usage of OPC UA Interfaces
258 The parameters of the BNM are grouped in the form of OPC UA Interfaces. Interfaces have been
259 chosen to define parameter sets independent of the implementation in future ObjectType hierarchies.
260 This allows these grouped parameters to be used in other Information Models independent of
261 ObjectType hierarchies that may be found in the BNM.

3 IEC CDV 62541-22 © IEC 2023
262 It is expected that a future version of the BNM will define a collection of network related ObjectTypes.
263 5 Base Network Model
264 Overview
265 The Base Network Model defined in this document is shown in Figure 2.

4 IEC CDV 62541-22 © IEC 2023
“Implementation Space - Objects“
“Implementation Space - ObjectTypes“
Scope of Base Network Model
(Not in Scope of Part 22)
(Not in Scope of Part 22)
TalkerStream
TalkerStreamType
StreamName
StreamId
StreamName
State
StreamId
AccumulatedLatency
State
SrClassId
AccumulatedLatency
IIeeeBaseTsnStreamType
SrClassId
StreamId
StreamName
ListenerStreamType
State
AccumulatedLatency
StreamName
SrClassId
StreamId
State
AccumulatedLatency
SrClassId
trafficSpecification IIeeeBaseTsnTrafficSpecificationType
TrafficSpecificationType
MaxIntervalFrames
MaxIntervalFrames
MaxFrameSize
MaxFrameSize
MaxIntervalFrames
TimeAware
TimeAware
MaxFrameSize
Interval
Interval
TimeAware
Interval
statusStream IIeeeBaseTsnStatusStreamType
StatusStreamType
FailureCode
FailureCode
FailureSystemIdentifier
FailureCode
[ FailureSystemIdentifier ]
FailureSystemIdentifier
IIeeeTsnInterfaceConfigurationType
interfaceConfiguration
TalkerInterfaceConfigurationType
MacAddress
MacAddress
InterfaceName
MacAddress
InterfaceName
InterfaceName
TimeAwareOffset
TimeAwareOffset IIeeeTsnInterfaceConfigurationTalkerType
ListenerInterfaceConfigurationType
TimeAwareOffset
MacAddress
IIeeeTsnInterfaceConfigurationListenerType
InterfaceName
ReceiveOffset
ReceiveOffset
macAddress IIeeeTsnMacAddressType
MacAddressType
DestinationAddress DestinationAddress
DestinationAddress
IIeeeTsnVlanTagType
vlanTag
VlanTagType
VlanId
VlanId
VlanId
PriorityCodePoint
PriorityCodePoint
PriorityCodePoint
“Implementation Space - Objects“ “Implementation Space - ObjectTypes“
Scope of Base Network Model
(Not in Scope of Part 22) (Not in Scope of Part 22)
IVlanIdType
eth0 IetfNetworkInterfaceType
VlanId
VlanId VlandId
AdminStatus
AdminStatus
IIetfBaseNetworkInterfaceType
OperStatus OperStatus
PhysAddress
PhysAddress
AdminStatus
Speed
Speed
OperStatus
PhysAddress
EthernetPortType
ethPort
Speed
Speed Speed
IIeeeBaseEthernetPortType
Duplex Duplex
MaxFrameLength MaxFrameLength
Speed
Duplex
autoNegotiation AutoNegotiationFeatureType
MaxFrameLength
NegotiationStatus NegotiationStatus
IIeeeAutoNegotiationStatusType
ethernetCapabilities EthernetCapabilitiesType
NegotiationStatus
VlanTagCapable VlanTagCapable
IBaseEthernetCapabilitiesType
tsnSrClass SrClassType
VlanTagCapable
Id Id ISrClassType
Priority Priority
Vid
Vid Id
Priority
Vid
267 Figure 2 – Overview of Base Network Model

5 IEC CDV 62541-22 © IEC 2023
268 OPC UA InterfaceTypes
269 IIetfBaseNetworkInterfaceType Interface
270 This OPC UA Interface defines the basis of an IETF network interface. The
271 IIetfBaseNetworkInterfaceType is formally defined in Table 1.
272 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
274 AdminStatus of DataType InterfaceAdminStatus specifies the desired state of the network interface.
275 This Variable has the same read semantics as ifAdminStatus (see IETF RFC 2863: The Interfaces
276 Group MIB - ifAdminStatus). The InterfaceAdminStatus Enumeration is defined in 5.3.1.2.
277 OperStatus of DataType InterfaceOperStatus specifies the current operational state of the network
278 interface. This Variable has the same semantics as ifOperStatus (see IETF RFC 2863: The Interfaces
279 Group MIB - ifOperStatus). The InterfaceOperStatus Enumeration is defined in 5.3.1.3.
280 PhysAddress of DataType String specifies the network interface's address at its protocol sub-layer.
281 For example, for an 802.x network interface, this parameter normally contains a Media Access Control
282 (MAC) address. The network interface's media-specific modules must define the bit and byte ordering
283 and the format of the value of this object. For network interfaces that do not have such an address
284 (e.g., a serial line), this node is not present (see IETF RFC 2863: The Interfaces Group MIB -
285 ifPhysAddress).
286 Speed of DataType UInt64 specifies an estimate of the network interface's current bandwidth in bits
287 per second. For network interfaces that do not vary in bandwidth or for those where no accurate
288 estimation can be made, this value should contain the nominal bandwidth (see IETF RFC 2863:
289 ifSpeed, ifHighSpeed).
290 The component Variables of the IIetfBaseNetworkInterfaceType have the Attribute values defined in
291 Table 2.
292 Table 2 – IIetfBaseNetworkInterfaceType Attribute values for child Nodes
Source Path Value Attribute Description Attribute
NamespaceUri: http://www.opcfoundation.org/UA/units/un/cefact -
Speed
UnitId: 4337968
EngineeringUnits
DisplayName: bit/s
Description: bit per second
6 IEC CDV 62541-22 © IEC 2023
294 IIeeeBaseEthernetPortType Interface
295 This OPC UA Interface defines capabilities of an Ethernet-based port. The IIeeeBaseEthernetPortType
296 is formally defined in Table 3.
297 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
299 Speed of DataType UInt64 specifies the configured, negotiated, or actual speed of an Ethernet port in
300 entities of 1 Mb/s (data rate). The default value is implementation-dependent (see IEEE Std 802.3).
301 Duplex of DataType Duplex represents the configured, negotiated, or actual duplex mode of an
302 Ethernet port (see IEEE Std 802.3, clause 30.3.1.1.32, “aDuplexStatus”). The Duplex DataType is
303 defined in 5.3.1.1.
304 MaxFrameLength of DataType UInt16 indicates the MAC frame length (including FCS bytes) at which
305 frames are dropped for being too long (see IEEE Std 802.3, clause 30.3.1.1.37, “aMaxFrameLength”).
306 The component Variables of the IIeeeBaseEthernetPortType have the Attribute values defined in Table
307 4.
308 Table 4 – IIeeeBaseEthernetPortType Attribute values for child Nodes
Source Path Value Attribute Description Attribute
NamespaceUri: http://www.opcfoundation.org/UA/units/un/cefact -
Speed
UnitId: 4534832
EngineeringUnits
DisplayName: Mbit/s
Description: megabit per second
310 IIeeeAutoNegotiationStatusType Interface
311 This OPC UA Interface defines the auto negotiation status of an Ethernet-based port. The
312 IIeeeAutoNegotiationStatusType is formally defined in Table 5.
313 Table 5 – IIeeeAutoNegotiationStatusType definition
Attribute Value
BrowseName IIeeeAutoNegotiationStatusType
IsAbstract True
Modelling
References NodeClass BrowseName DataType TypeDefinition
Rule
Subtype of the BaseInterfaceType defined in IEC 62541-5
HasComponent Variable NegotiationStatus NegotiationStatus BaseDataVariableType Mandatory
Conformance Units
BNM AutoNeg
315 NegotiationStatus of DataType NegotiationStatus specifies the status of the auto-negotiation protocol
316 (see IEEE Std 802.3, clause 30.6.1.1.4, “aAutoNegAutoConfig”). The NegotiationStatus DataType is
317 defined in 5.3.1.4.
7 IEC CDV 62541-22 © IEC 2023
318 IBaseEthernetCapabilitiesType Interface
319 This OPC UA Interface defines if an Ethernet-based port is VLAN Tag capable. The
320 IBaseEthernetCapabilitiesType is formally defined in Table 6.
321 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
323 When VlanTagCapable is true, the network interface supports the ability to tag/untag frames using a
324 Customer VLAN Tag (C-TAG of clause 9) provided by the network (see IEEE 802.1Qcc-2018 clause
325 46.2.3.7.1.).
326 IVlanIdType Interface
327 This OPC UA Interface specifies a VLAN Id to be associated with a network interface. The IVlanIdType
328 is formally defined in Table 7.
329 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
331 VlanId is an UInt16 and contains the Customer VLAN Tag (IEEE 802.1Q-2018 C-TAG of clause 9) that
332 frames injected at this network interface will be tagged with (see IEEE 802.1Qcc-2018 clause
333 46.2.3.7.1).
334 ISrClassType Interface
335 This OPC UA Interface defines the content of an SrClass. The ISrClassType is formally defined in
336 Table 8.
337 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
339 Id is a Byte and specifies the SRclassID in a numeric representation of the SR classes which is
340 supported by a particular Bridge Port (see IEEE 802.1Q-2018, clause 35.2.2.9.2, SRclassID). Only
341 Values between 0 and 7 shall be used.

8 IEC CDV 62541-22 © IEC 2023
342 Priority is a Byte and holds the Data Frame Priority (item a) in IEEE 802.1Q-2018 clause 35.2.2.8.5)
343 value that will be used for streams that belong to the associated SR class. (see IEEE 802.1Q-2018,
344 clause 35.2.2.9.3, SRclassPriority). Only Values between 0 and 7 shall be used.
345 Vid is an UInt16 and contains the SR_PVID (item i) in IEEE 802.1Q-2018 clause 35.2.1.4) that the
346 associated streams will be tagged with by the Talker (see IEEE 802.1Q-2018, clause 35.2.2.9.4,
347 SRclassVID).
348 IIeeeBaseTsnStreamType Interface
349 The IIeeeBaseTsnStreamType contains Variables which are common for both TSN talkers and TSN
350 listeners. They represent the configuration properties and diagnostic values like reservation status
351 and failure codes of a TSN stream. The IIeeeBaseTsnStreamType is formally defined Table 9.
352 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
354 StreamId is an array of 8 Bytes defined according to the StreamID in IEEE 802.1Qcc-2018 clause
355 35.2.2.8.2. The StreamId shall be unique in the scope of the related TSN Network. The mapping
356 between the StreamId Byte array and the IEEE octet string StreamID is as follows: Entry[n] of StreamId
357 is mapped to octet[n] of StreamID. The StreamId shall be provided in the TSN stream Objects for
358 diagnostic reasons.
359 Note: In the distributed configuration model the StreamId is typically generated by the TSN control stack of the endstation.
360 In the fully centralized configuration model the StreamId is typically generated by the CUC.
361 StreamName is a String identifying the related stream in the network. The format of the String is
362 application specific. The uniqueness of the StreamName inside the network segment shall be
363 guaranteed by the application. If multiple applications use the network segment, they need to agree
364 on a naming scheme.
365 State represents the current state of the TSN configuration process of a TSN stream. The
366 TsnStreamState Enumeration is defined in 5.3.1.6.
367 AccumulatedLatency of DataType UInt32 is the maximum worst case propagation delay in
368 nanoseconds calculated and guaranteed by the TSN Control Layer for this Listener. Once the stream
369 reservation has succeeded the AccumulatedLatency is not expected to increase during the lifecycle of
370 the TSN Stream (see IEEE 802.1Q-2018 clause 35.2.2.8.6).
371 SrClassId of DataType Byte contains the Stream Reservation Class that is used for this stream (see
372 IEEE 802.1Qcc-2018 clause 35.2.2.9.2).

9 IEC CDV 62541-22 © IEC 2023
373 IIeeeBaseTsnTrafficSpecificationType Interface
374 This OPC UA Interface is used to represent the traffic specification of a TSN stream. The
375 IIeeeBaseTsnTrafficSpecificationType is formally defined in Table 10.
376 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
378 The MaxFrameSize of DataType UInt16 specifies the maximum size frame that will be sent by a Talker
379 for this Stream (see IEEE 802.1Q-2018 clause 35.2.2.8.4a).
380 Note: According to 802.1Q MaxFrameSize only counts the number of bytes of the Ethernet payload without the media specific
381 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,
382 12-byte inter frame gap). Same rules apply for counting MaxBytesPerInterval.
383 The MaxIntervalFrames of DataType UInt16 Variable specifies the maximum number of frames that
384 will be sent during an Interval. (see IEEE 802.1Q-2018, clause 35.2.2.8.4b, “MaxIntervalFrames” or
385 IEEE 802.1Qcc-2018, clause 35.2.2.10.6, “MaxFramesPerInterval”)
386 Interval of DataType UnsignedRationalNumber defines the time period of the TSN Stream in
387 nanoseconds. In that interval a specified number of frames (MaxIntervalFrames) with a maximum
388 payload size per frame (MaxFrameSize) and a maximum total number of bytes (MaxBytesPerInterval)
389 will be transmitted. The Interval therefore shall either represent the “class measurement interval” as
390 used for AVB based Streams (see IEEE 802.1Q-2018 clause 35 or the “Interval” parameter used in
391 the TrafficSpecification group in IEEE 802.1Qcc-2018 clause 46.2.3.5.1).
392 IIeeeBaseTsnStatusStreamType Interface
393 This OPC UA Interface is used to represent the status of a TSN stream. The
394 IIeeeBaseTsnStatusStreamType is formally defined in Table 11.
395 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
397 TalkerStatus of DataType TsnTalkerStatus contains the Reservation Failure Code as defined in the
398 “FailureInformation” in IEEE 802.1Qcc-2018 clause 46.2.5.1.1.
399 ListenerSt
...