623   BRCB entryID

Created: 16 Jun 2008

Status: Not Applicable

Part: Part 7-2 (2003)

Links:

Page: 82

Clause: 14.2.2.15

Paragraph:

Category: Issue for edition 2 of this part

Issue

For BRCB, all the report have one unique and increasing entryID including integrity and GI report,
but usually the integrity and GI reports are not buffered. so the entryID in the buffer may be not sequential.

in clause 14.2.2.15, "After an association (which was down) has been re-established by a client, the client shall set
the EntryID to the value received last. The BRCB shall continue sending reports with the next value of EntryID after enabling the BRCB to receive the reports buffered." in this condition, there may be a problem, because the cient set the entryID which is not existent in the buffer for integrity and GI report. so the BRCB will continue sending reports with the first available value of EntryID but not with the next value of EntryID after enabling the BRCB.

Proposal

in Edt2, it necessary to declare how the client should set the entryID after an assoaciation has been re-established by a client. the condition for example, entryID in buffer is not sequential such as 1,2,3,8,9,10, but the cient may set entryID 6 after re-establishing. I think the BRCB should send reports begin entryID which is more than 6.

Discussion Created Status
See tissue resolution 453 including attached definition of buffered reporting, or 61850-7-2 CDV for Edition 2.
Integrity will be buffered.
Only last GI will be buffered.
The format of EntryID is out of scope of the standard. The couple (EntryID, TimeOfEntry) must be unique.
20 Feb 09 Not Applicable
<<For BRCB, all the report have one unique and increasing entryID >>
No: EntryIDs are unique but not increasing, they are tags, labels, withiout any relation of order between them.
16 Jun 08 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1