0x0C where a date required for a Message, / time field is it shall be a 12 octet required string as per the DLMS specification. See in ‘date-timestamp response’ column, ‘Use Case tab in reference’ Mapping Table Yes value Either empty or a 0 or 12 12 character containing the date-time stamp for this Response other-information No length Encoding(X) variable X is length of other information octet string. Len(Encoding(X)) X is 2 or 18 or 26 or variable Yes value Message Code || 2 or 18 or 26 or The Message Code Supplementary variable shall always be present Remote Party ID || In an Alert, Supplementary Supplementary Remote Remote Party Party ID shall be Counter || present, if it is required Supplementary by Section 16 Originator Counter In a Command or || Supplementary Response, the Remote Party Key Supplementary Remote Agreement Party ID, Certificate Supplementary Remote Party Counter and Supplementary Originator Counter, shall be present or not in line with the requirements of Section 4.3.1.4 Supplementary Remote Party Key Agreement Certificate shall only be present where (1) this is a Command, (2) the Response to it should contain encrypted attributes and (3) the Supplementary Remote Party ID is for a Remote Party which does not already have a Key Agreement
0x0C where a date / time field is required required for a Message, it shall be a 12 octet string as per the DLMS specification. See ‘date-timestamp in response’ column, ‘Use Case reference’ tab in Mapping Table Yes value Either empty or a 12 character containing the date-time stamp for this Response 0 or 12 other-information No length Encoding(X) variable Len(Encoding(X)) X is length of other information octet string. X is 2 or 18 or 26 or variable Yes value Message Code || Supplementary Remote Party ID || Supplementary Remote Party Counter || Supplementary Originator Counter || Supplementary Remote Party Key Agreement Certificate 2 or 18 or 26 or variable The Message Code shall always be present In an Alert, Supplementary Remote Party ID shall be present, if it is required by Section 16 In a Command or Response, the Supplementary Remote Party ID, Supplementary Remote Party Counter and Supplementary Originator Counter, shall be present or not in line with the requirements of Section 4.3.1.4 Supplementary Remote Party Key Agreement Certificate shall only be present where (1) this is a Command, (2) the Response to it should contain encrypted attributes and (3) the Supplementary Remote Party ID is for a Remote Party which does not already have a Key Agreement
GBCS_v0_8.DOCX