Search

Scope: Core (OPC-10000-*) All specs

11 result(s) for SequenceNumber

OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

5.1.14 Message Suppression

this threat. A Client and Server can counter message suppression by using checking the SequenceNumber in the sequence header. A SecureChannel is required to be closed if a SequenceNumber
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.7.2.4 Sequence Header

channel will start with different data. Table 60 - Sequence header Name Data Type Description SequenceNumber UInt32 A monotonically increasing sequence number assigned by the sender to each MessageChunk sent over ... MessageChunks for the request and the associated response use the same identifier. A SequenceNumber shall not be reused for any TokenId . The SecurityToken lifetime shall be short enough to ensure
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.7.7 Verifying Message Security

After the security validation is complete the receiver shall verify the RequestId and the SequenceNumber . If these checks fail a Bad_SecurityChecksFailed error is reported. The RequestId is verified ... Client since only the Client knows if it is valid or not. If the SequenceNumber is not valid, the receiver shall log a Bad_SequenceNumberInvalid error. At this point
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.8.1 Secure Channel Handshake

processed. It is encoded as a UInt32 as described in 5.2.2.2. LastSequenceNumber 4 The SequenceNumber specified in the SequenceHeader of last MessageChunk sent in the same direction on the SecureChannel ... ServerInitializationVector is used when the Server encrypts the MessageChunk . The LastSequenceNumber is the SequenceNumber from the previously sent Message which normally requires the previous Message to be decrypted
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.4 NetworkMessageContentMask

DataSets of the group. The flag is only valid if Bit 1 is set. SequenceNumber 5 The SequenceNumber field is included in the GroupHeader . The flag is only valid
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.3 SequenceNumber in headers

SequenceNumber in headers SequenceNumber fields are defined in different headers of the UADP or JSON Message Mapping. A SequenceNumber is a monotonically increasing number assigned to messages headers represented ... unsigned integer of width N which is further specified in Table 152 . The SequenceNumber starts at 0 and shall be incremented by exactly one for each message. Receivers need
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

Writer GroupId enabled Bit 1: GroupVersion enabled Bit 2: NetworkMessageNumber enabled Bit 3: SequenceNumber enabled Bits 4-6: Reserved Bit 7: Reserved for further extended flag fields Reserved bits shall ... invalid. This field shall be omitted if bit 2 of the GroupFlags is false. SequenceNumber UInt16 Sequence number for each new NetworkMessage as defined in 7.2.3 . This field shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.4 Header layout for NetworkMessages

fields according to this header layout: Version / Flags ExtendedFlags1 PublisherId GroupFlags WriterGroupId GroupVersion NetworkMessageNumber SequenceNumber Additional restrictions: The datatype for the PublisherId shall be UInt16 or UInt64 The NetworkMessage header ... enabled = 1 Bit 1: GroupVersion enabled = 1 Bit 2: NetworkMessageNumber enabled = 1 Bit 3: SequenceNumber enabled = 1 Bits 4-6: 0 Bit 7: 0 WriterGroupId UInt16 Configured value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

This value results of the following options: Bit 2: StatusCode enabled = 1 Bit 5: SequenceNumber enabled = 1 DataSetFieldContentMask 0x00000020 This value results of the following options: Bit 5: RawData DataSetOrdering
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

enabled = 1 Bit 2: Status enabled = 1 Bit 4: MinorVersion enabled = 1 Bit 5: SequenceNumber enabled = 1 DataSetFieldContentMask <anything
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.4.4 Configuration parameters

allows the following options: Bit 0: DataSetWriterId = 1 Bit 1: MetaDataVersion = 0 Bit 2: SequenceNumber = 1 The SequenceNumber is always omitted for Action messages. Bit 3: Timestamp