Message Templates ZSE Message Templates Message Templates for GBZ Use Cases are detailed in the embedded Use Cases, Section 19.4. These Message Templates are derived from the Mapping Table, and shall be complied with in the construction and population of all such Messages. DLMS COSEM Message Templates Table 18.2 contains Message Templates for all Use Case with DLMS COSEM payloads. These Message Templates are derived from the Mapping Table, and shall be complied with in the construction and population of all such Messages. Table 18.2: DLMS COSEM Message Templates Encoding Italicised terms in this Section 18.2.1 shall have their DLMS COSEM meaning. The Blue Book definition of attribute 2 of Profile Generic objects may be interpreted as requiring to be a structure containing a single ‘entry’ choice from the DLMS data types. The GBCS interprets it as meaning that is a structure that can contain multiple choices of DLMS data ‘entry’ types. These choices vary between instances of Profile Generic object. To identify these different structures, the naming convention is used. ‘entry_nameOfStructure’ The GBCS uses the compact-array data type in attribute 2 of Profile Generic objects. Table 18.2.1 details the derivation of the description element within the compact-array structure for the structures used in the Profile Generic objects required by this GBCS. These encodings are reflected in the DLMS COSEM Message Templates. Number of entries Tag of contents-description for Structure definition Tag (structures entries in compact-array and arrays array only) entry_dlValueLogEntry::= structure { 0x02 0x02 0x1302020606 timestamp: double-long-unsigned, 0x06
Message Templates ZSE Message Templates Message Templates for GBZ Use Cases are detailed in the embedded Use Cases, Section 19.4. These Message Templates are derived from the Mapping Table, and shall be complied with in the construction and population of all such Messages. DLMS COSEM Message Templates Table 18.2 contains Message Templates for all Use Case with DLMS COSEM payloads. These Message Templates are derived from the Mapping Table, and shall be complied with in the construction and population of all such Messages. Table 18.2: DLMS COSEM Message Templates Encoding Italicised terms in this Section 18.2.1 shall have their DLMS COSEM meaning. The Blue Book definition of attribute 2 of Profile Generic objects may be interpreted as requiring ‘entry’ to be a structure containing a single choice from the DLMS data types. The GBCS interprets it as meaning that ‘entry’ is a structure that can contain multiple choices of DLMS data types. These choices vary between instances of Profile Generic object. To identify these different structures, the naming convention ‘entry_nameOfStructure’ is used. The GBCS uses the compact-array data type in attribute 2 of Profile Generic objects. Table 18.2.1 details the derivation of the element within the compact-array structure for the structures used in the Profile Generic objects required by this GBCS. These encodings are reflected in the DLMS COSEM Message Templates. Structure definition Tag Number of entries (structures and arrays only) Tag of entries in array contents-description for compact-array entry_dlValueLogEntry::= structure { 0x02 0x02 0x1302020606 timestamp: double-long-unsigned, 0x06 description