Grouping Remote Party Message Message Type Command, Response and Alert (if future dated) Message Type Category SME.C.C Capable of future dated invocation? Yes Protection Against Replay Required? No SEC User Gateway Services Schedule (Service Request) N/A for Communications Hub Reference (this Command is not available as part of the User Gateway Services) 11.3 for ESME and GSME Valid Target Device(s) ESME / GSME / CH Valid Business Originator role(s) for Command invocation (and Supplier for ESME / GSME so, for DLMS COSEM Commands, which Application Association WAN Provider for CH is to be used for delivery of the Command to the Device) [Remote Party Messages Only] Valid Response Recipient role(s) (only for Messages authorised N/A by the Access Control Broker on behalf of parties not known to the Device) [Remote Party Messages Only] Valid initiating Device type(s) [HAN Only Messages] N/A Protocol ASN.1 Table 11.5: Use Case Cross References for CS06 Activate Firmware Pre-conditions None. Detailed Steps Construction of Command Activate Firmware Command Payloads shall be constructed according to the requirements of Section 11.5.2.3 and populated as specified in Table 11.5.2.1. MAC Header, Grouping Header, KRP Signature and ACB-SMD MAC shall be populated as required for a Command of the SME.C.C Message Category. Attribute name Data Type Value (blank cells mean Mandatory, Notes the command specific OPTIONAL or value is derived by the DEFAULT encoding process) value SEQUENCE OCTET The Manufacturer Image Mandatory An octet-string of manufacturerImageHash STRING Hash of the image to be length 32 interpreted activated. as the Manufacturer Image Hash of the Manufacturer Image that is to be activated The date-time at which OPTIONAL executionDateTime the Command is to be executed, if future dated Table 11.5.2.1: population @ActivateFirmware.CommandPayload
Grouping Remote Party Message Message Type Command, Response and Alert (if future dated) Message Type Category SME.C.C Capable of future dated invocation? Yes Protection Against Replay Required? No SEC User Gateway Services Schedule (Service Request) Reference N/A for Communications Hub (this Command is not available as part of the User Gateway Services) 11.3 for ESME and GSME Valid Target Device(s) ESME / GSME / CH Valid Business Originator role(s) for Command invocation (and so, for DLMS COSEM Commands, which Application Association is to be used for delivery of the Command to the Device) [Remote Party Messages Only] Supplier for ESME / GSME WAN Provider for CH Valid Response Recipient role(s) (only for Messages authorised by the Access Control Broker on behalf of parties not known to the Device) [Remote Party Messages Only] N/A Valid initiating Device type(s) [HAN Only Messages] N/A Protocol ASN.1 Table 11.5: Use Case Cross References for CS06 Activate Firmware Pre-conditions None. Detailed Steps Construction of Command Activate Firmware Command Payloads shall be constructed according to the requirements of Section 11.5.2.3 and populated as specified in Table 11.5.2.1. MAC Header, Grouping Header, KRP Signature and ACB-SMD MAC shall be populated as required for a Command of the SME.C.C Message Category. Attribute name Data Type Value (blank cells mean the command specific value is derived by the encoding process) Mandatory, OPTIONAL or DEFAULT value Notes SEQUENCE manufacturerImageHash OCTET STRING The Manufacturer Image Hash of the image to be activated. Mandatory An octet-string of length 32 interpreted as the Manufacturer Image Hash of the Manufacturer Image that is to be activated executionDateTime The date-time at which the Command is to be executed, if future dated OPTIONAL Table 11.5.2.1: @ActivateFirmware.CommandPayload population
GBCS_v0.8.1.docx