Annex A (normative) UADP Header Layouts ToC Previous Next

A.2 Message headers for periodic data with fixed layout ToC Previous Next

A.2.6 Header layout for NetworkMessages with integrity and confidentiality (signing and encryption) ToC Previous Next

UADP messages may be signed and encrypted. In this case the SecurityHeader and the Signature have to be added to the message. See clause 7.2.2.4.3 for a complete description of the security mechanisms.

This header layout is basically the same as the header layout defined in A.2.4 but with additional security level ‘signing and encryption’.

The NetworkMessage header layout with signing is shown in Figure A.3.

readme_files/image052.png readme_files/image054.png Table A.4 shows the configuration for the NetworkMessage header with signing and encryption. The table contains only the added or modified rows from Table A.1.

Table A.4 – UADP NetworkMessage header layout with integrity and confidentiality

Name Type Restrictions
ExtendedFlags1 Byte Bit 4: Security enabled
SecurityHeader    
   SecurityFlags Byte    Bit 0: NetworkMessage Signed enabled   Bit 1: NetworkMessage Encryption enabled   Bit 2: SecurityFooter disabled   Bit 3: Force key reset disabledBit range 4-7: Reserved
   SecurityTokenId IntegerId The ID of the security token that identifies the security key in a SecurityGroup.
   NonceLength Byte 8
   MessageNonce Byte[8] A number used exactly once for a given security key.

Previous Next