This clause defines a component model to structure the selection of functional networking features. This component model consists of Bridge Component (see 6.2), End Station Component (see 6.3), IA-station (see 6.4), and UAFX Station (see 6.5).
A Bridge Component interconnects two or more network segments and forwards packets between them. This document supports the Bridge Component features listed in 6.2.2, including link speeds of 10 Mb/s to 10 Gb/s.
C-VLAN component requirements as defined in IEEE Std 802.1Q2022, 5.5.
NOTE This document does not make use of the Multiple VLAN Registration Protocol (MVRP).
Strict priority algorithm for transmission selection as defined in IEEE Std 802.1Q2022, 188.8.131.52 on each port for each traffic class
Regenerating priority as defined in IEEE Std 802.1Q2022, 6.9.4
Frame filtering as defined in IEEE Std 802.1Q2022, 5.4.1, Item h)
Per-stream filtering and policing as defined in IEEE Std 802.1Q2022, 184.108.40.206
Enhancements for scheduled traffic as defined in IEEE Std 802.1Q2022, 5.4.1, Items ac) and ad)
NOTE For UAFX, the enhancements for scheduled traffic mechanism rely on a synchronised Working Clock.
Frame Preemption as defined in:
IEEE Std 802.1Q2022, 5.4.1, Item ae)
TE-MSTID as defined in IEEE Std 802.1Qcc2018, 5.5.2 Items a) and b).
Transmission and reception of C-VLAN tagged frames.
IA-stations can be a simple End Station Component (see 6.3) acting as the source or destination for industrial data traffic. IA-stations may also include a Bridge Component (see 6.2). More complex IA-stations incorporating several End Station Components and Bridge Components within one device can also be found in industrial automation (e.g., a Controller with multiple modules).
An IA-station can include one or more IA-station functions acting as the source or destination for data traffic. These functions, located in the End Station Components, include industrial automation applications, Remote Management, and other applications or services such as Time Synchronisation or Topology Discovery. IA-station functions can reside in a single or multiple End Station Components within a given IA-station.
Figure 13 shows three examples of an IA-station. IA-station 1 comprises one End Station Component hosting two IA-station functions. IA-station 2 comprises one End Station Component hosting one IA-station function and one Bridge Component. IA-station 3 comprises a Bridge Component and two End Station Components hosting four IA-station functions. IA-station 3 shows that an IA-station function can span across multiple End Station Components.
An IA-station shall:
support topology discovery as defined in clause 7.3.
An IA-station may:
support remote management as defined in clause 7.2,
support time synchronisation as defined in clause 7.4,
support middleware applications.
Ethernet QoS mechanisms are defined to operate on PCP or traffic classes. For the latter, a mapping between the PCP value in the frame and the associated TC is needed. If the PCP to TC mapping has not been explicitly configured, an IA-station shall use the mapping defined in IEEE Std 802.1Q2022, Table 8-5.
A UAFX Station is an IA-station (see 6.4) supporting the UAFX communication and application layer (see Figure 1). The UAFX communication and application layer is a logical component acting as a source of and/or destination for link layer data traffic. Thus, each UAFX Station incorporates at least one End Station Component where the UAFX communication and application layer can be located. Figure 14 shows that the UAFX communication and application layer can reside in one or multiple End Station Components.
comprise a conformant IA-station,
support middleware modelling of network interfaces and QoS in the UAFX communication and application layer:
- priority mapping configuration representation as defined in OPC 1000022, including the PriorityMappingTableType, MappingTables Folder, and the UsesPriorityMappingTable ReferenceType (see 6.5.4);
- network interface representation as defined in OPC 10000-22, including the IetfBaseNetworkInterfaceType, the IIetfBaseNetworkInterfaceType and IIeeeBaseEthernetPortType Interfaces, and the NetworkInterfaces Folder (see 6.5.3);
- C-VLAN configuration representation as defined in OPC 1000022, including the IVlanIdType Interface and the HasLowerLayerInterface ReferenceType (see 6.5.3).
Each physical network interface available to the UAFX Application shall be represented as an instance of IetfBaseNetworkInterfaceType in the NetworkInterfaces Folder defined in OPC 1000022. All VLAN interfaces attached to these physical network interfaces shall be represented as defined in OPC 1000022. A UAFX Station shall at least provide the default VLAN interface with the BrowseName as defined in Table 2 and a HasLowerLayerInterface reference to the respective physical network for each of these physical network interfaces. If the VlanId value has not been explicitly configured for this default VLAN interface, the VlanId shall assume the value defined in Table 2.
Note: The BrowseName of the default VLAN interface in Table 2 starts with the physical interface that this VLAN interface is associated with and ends with the interface label “uafx-vlan” separated by a dot (“.”). “<physical-interface>” in Table 2 is a placeholder for the BrowseName (e.g., “eth0”) of the associated physical interface. This composition ensures the uniqueness of the default VLAN interface BrowseName in UAFX Stations with multiple network interfaces.
A UAFX Station shall provide a PriorityMappingTable with at least the default entries for MappingUri/QosCate gory and PriorityLabel as defined in Table 3. If PCP and DSCP values have not been explicitly configured (i.e., to accommodate the needs of an existing network), PriorityValue_PCP and PriorityValue_DSCP shall assume the values defined in Table 3.
Each physical network interface available to the UAFX Application represented by an instance of IetfBaseNetworkInterfaceType in the NetworkInterfaces Folder shall have a reference to an instance of PriorityMappingTableType that is exposed to OPC UA Clients, e.g., for adaptation during the system integration phase (see 220.127.116.11), as defined in OPC 1000022. The referenced PriorityMappingTableType instance shall include the AddPriorityMappingEntry and DeletePriorityMappingEntry Methods.