Support #484
A question was raised in regards can Report EntryIDs be reused after IED restart. If so, guidance needs to be given for system d
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:
0%
Estimated time:
ID:
40
Source:
IOP_2013
TF Unique ID:
40 # IOP_2013
WG10 Proposal:
The unicity of the entry is given by the couple entryID and TimeOfEntry.
Estimated Completion:
Discuss in Upcoming Meeting:
To discuss in WG10:
Short Proposal:
Add note to clause 17.2.2 (somewhere) that EntryIDs must be unique across restarts.
Standard(s):
Needs More Information:
Assigned TF:
Description
A question was raised in regards can Report EntryIDs be reused after IED restart. If so, guidance needs to be given for system design on how to recover/resync
The standards do not mandate any particular behavior. In general, this should not represent an issue since the events previously buffered are no longer present.
The issue is if a client reads the RCB and sees the same EntryID, what should the client do. This is part of the resync process that needs to be described.
Target would be for a system design document within UCA IUG.