Project

General

Profile

Support #481

A question was raised in regards to how a client should resynchronize to receive the last report (Buffered Reporting). The sta

Added by Herbert Falk about 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
37
Source:
IOP_2013
TF Unique ID:
37 # IOP_2013
WG10 Proposal:

Solved with tissue 1276

Estimated Completion:
Discuss in Upcoming Meeting:
To discuss in WG10:
Short Proposal:

Guideline would be as follows:
Write BRCB.RptEna value "false"
Write BRCB.EntryID to last known value
If (Response-)
Write BRCB.PurgeBuf value "true"
(optional) Write BRCB.EntryID value zeros
}
Write BRCB.RptEna value "true"

NB: Writing to EntryID not needed because:
1) Upon failure to write EntryID, state=disabled
2) transition from disabled to enabled "start repoting with first available entry"

Alternative resync if client wants every available entry but Write BRCB.EntryID fails:
Client notes "gap in data" and simply writes BRCB.RptEna value "true"

Standard(s):
Needs More Information:
Assigned TF:

Description

A question was raised in regards to how a client should resynchronize to receive the last report (Buffered Reporting).

The standard is clear that resynchronization gives the next report, not the last report. However, it was suggested that guidance be given on how clients should generally perform this (e.g. GI for synchronization of data and the use of EntryID.). Guidance also needs to be given on the use of PurgeBuf and EntryID=00000000.

Target would be for a system design document within UCA IUG.

#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Closed

Also available in: Atom PDF