DC-09 Preparing for ANSI Public Review - Security Industry ...

ANSI/SIA DC-09-2013: Internet Protocol Event Reporting• "RSP": remote command• 0001: sequence 1• L2: account prefix 2• #345: account number 345• [#345|: start of data field, repeats account number• "EQUIPCO": manufacturer ID (fictitious in this example)• RZS22.5,XX5: manufacturer specific message format• ]: end of data fieldExample 2: Legacy FormatCCCC001F"RSP"0001L2#345[#345|NZZCCnnnn]• CCCC: checksum, not calculated in this example• 001F: length• "RSP": remote command• 0001: sequence 1• L2: account prefix 2• #345: account number 345• [#345|: start of data field, repeats account number• N: manufacturer ID "legacy"• NZZCCnnnn: manufacturer specific message format• where:• N new message• ZZ code of fixed criteria, indicating a remote command has been sent from CSR to PE• CC code criteria for the type of action, according to a list maintained by the local authority• nnnn zone number (corresponds to the number of the physical contact).• ]: end of data fieldWhen using such remote commands, the following implementation process might be used:• The polling frequency can be increased to shorten response time• When a remote command is to be sent in response to a NULL message, this remote commandmessage replaces the ACK message for the NULL message. The RSP must be considered as anACK by the PE• The PE acknowledges the reception of the remote command message and the change of staterequested by the CSR by sending a new event message• Finally, the CSR sends an acknowledgment message (ACK) to the PEThe figure below shows an example of the sequence:Page 33