Implementation methods and differences between channel following reporting and active reporting in object-oriented protocol smart meter module

Smart meter follow-up reporting can be implemented on all communication channels of smart meters, such as 485 or Bluetooth channels. Follow reporting mainly follows a reporting content (33200201 and 20150200) at the end of the message when passively calling for data. But in the carrier channel, the active reporting function similar to the original 645 protocol can be achieved by cooperating with the module. This article mainly elaborates on the implementation methods of channel following reporting and active reporting in the communication (carrier) module.

1. The channel of the smart meter module follows the reporting process

The smart meter pulls the EVENT OUT pin, and the module reads 33200201 (newly added event list OAD) and 20150200 (following the reporting status word OAD), reports them to the terminal. After receiving them, the terminal reads the corresponding event associated object content of the smart meter and then reports it to the main station.

Implementation steps:

1). Trigger: After the smart meter generates an event, actively pull the EVENT OUT hardware pin to high resistance (physical level change).

2). Perception: The module perceives pin actions and reads event identifiers (33200201, 20150200) from the smart meter.

3). Report: The module transmits data to the terminal.

4). Processing: The terminal reads the content of the smart meter event or reports it on 20150200, and then reports it to the main station.

2. Active reporting process of smart meter module channel

The smart meter actively reports (report request service 88 01) 33200200 and 20150200, which are forwarded by the module. After receiving the active report message, the terminal responds (report response service 08 01), reads the content of the corresponding event associated object of the smart meter, and then reports to the main station.

Implementation steps:

1). Initiate: The smart meter detects an event and sends an active reporting request message (88 01) through the module serial port.

2). Forwarding: After receiving the reporting request, the module directly forwards it to the terminal.

3). Response: The terminal responds with a report confirmation (08 01).

4). Reading: The terminal reads the specific event content in the smart meter based on the reported content (such as event records corresponding to 33200200 and 20150200).

5). Reporting: The terminal packages and reports the data to the main station.

Proactively report security and provide additional content explanations:

1) The 698 protocol requires that power outages be actively reported in fixed plaintext to record power outage events (after a power outage, ESAM does not work, so fixed plaintext is used);

2). After power on, ESAM can work normally and report 33200200 and 20150200 using plaintext+RN+MAC security method (can report both 33200200 and 20150200 at the same time, or report one of them). The terminal uses plaintext+MAC response, and the smart meter determines the correctness of the MAC response message for processing.

3. Report relevant important parameters

1). Report channel selection:

43000A00: Specify the physical channels for reporting, including carrier (F2090201), RS485 (F2010201, F2010202, F2010203), Bluetooth (F20B0201), IoT table extension module channels (F20D0201, F20D0202, F20D0203)

2). Total allowable switch:

43000800: Enable proactive reporting.

43000700: Enable follow-up reporting.

3). Reporting method:

Ordinary Category 7 Events

Attribute 8 reporting identifier:

(0) Do not report (1) Report event occurrence (2) Report event recovery (3) Report both event occurrence and recovery.

Attribute 11 reporting method:

(0) Proactive reporting (1) Follow up reporting.

Ordinary 24 types of events

Attribute 11 reporting identifier:

(0) Do not report (1) Report event occurrence (2) Report event recovery (3) Report both event occurrence and recovery.

Attribute 15 reporting method:

(0) Proactive reporting (1) Follow up reporting.

Proactively reporting, due to the limitation of carrier communication capability, currently only 33200200 (newly added event OAD list) and 20150200 are reported after the smart meter is powered on, in order to reduce the time occupied by uplink bandwidth. It is said that the latest State Grid has planned to configure all events to be reported as record content (long messages) or event list OAD.

In addition, it should be noted that the majority of power outage reporting still relies on the original communication module power outage reporting method, and generally does not use the active reporting method of smart meter power outage reporting and power outage records.