667 Receiving duplicated reports after restarting a client.Created: 09 Aug 2010 Status: Not Applicable Part: Part 7-2 (2003) Links: Page: 82 Clause: 14.2.2.15 Paragraph: All, revision also Category: No impact on this part Issue Problem: Neither the old definitions on IEC_61850_7_2 14.2.2, neither the new proposed ones, solves the following question: At power on or restart of a client, it can not know what is the EntryID of the last properly received report. So, in that situation, the client will set an EntryID with all zeros and this will instruct the server, when going to the enabled state, to begin sending reports from the oldest one that is still buffered. This will cause the client to receive again a set of reports already received before it was restarted.
Proposal That problem would be avoided if, while the BRCB is in the disabled state and before setting a new EntryID, the client could read the EntryId and the server informed the EntryID of the last report properly sent, and not "the last (i.e..newest) entry that has been entered into the buffer" as is proposed in the revision. In that manner, the client could resync the server to the oldest buffered report not yet sent.
Privacy | Contact | Disclaimer Tissue DB v. 24.4.30.1 |