The PriorityMappingTableType is formally defined in Table 61.
Table 61 – PriorityMappingTableType definition
Attribute |
Value |
||||
BrowseName |
PriorityMappingTableType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the BaseObjectType defined in OPC 10000-5 |
|||||
HasProperty |
Variable |
PriorityMapppingEntries |
PriorityMappingEntryType[] |
PropertyType |
M |
HasComponent |
Method |
AddPriorityMappingEntry |
Defined in 5.5.2.3 |
O |
|
HasComponent |
Method |
DeletePriorityMappingEntry |
Defined in 5.5.2.4 |
O |
|
Conformance Units |
|||||
BNM Priority Mapping 2 |
PriorityMappingEntries represents a list of all instances of PriorityMappingEntryType. For a formal definition see 5.3.2.1. The order of the elements in the array does not have any influence, as elements are indexed via the MappingUri and PriorityLabel.
The combination of QosCategory and PriorityLabel are used as indices into the referenced PriorityMappingTable to look up the priority values. The reference from an IetfBaseNetworkInterface is described in Section 5.5.1. For the sender, the priority values shall be included within the frame, if the according fields are available, i.e., VLAN Tag to use the PCP value and IP header to use the DSCP value. The receiver can use the priority values for internal packet processing.
Note: An example for a simplified PubSub connection is shown in Annex A.2. Within the PubSubConnection, each WriterGroup can contain a QosCategory and DatagramQos structure with a PriorityLabel. For the subscriber side these values are specified on the DataSetReader level.
AddPriorityMappingEntry allows to add an entry to this instance of PriorityMappingTableType.
DeletePriorityMappingEntry allows to delete an entry from this instance of PriorityMappingTableType.