Mandate RCB reservation for Ed2.0 client and Amd1 server
Added by Richard Schimmel over 2 years ago.
Updated about 2 years ago.
Discuss in Upcoming Meeting:
Update cRp2 and mandate cBr33 to ensure client does reserve URCB/BRCB
Test Case ID:
cRp2 and cBr33
Test Procedure Update
Amd1 requires Clients to always reserve URCB/BRCB even when the RCB is pre-assigned and servers to refuse configuring/enabling RCBs without prior reservation. To guarantee forward compatibility from Ed2.0 to Amd1; Ed2.0 client shall reserve RCB. In the current test procedures the reservation is optional, because Ed2 servers allow implicit reservation
ResvTms not present in server means -> Go for (re)configuring or RptEna; the response the client get @ RptEna will tell if the report will arrive or not.
ResvTms = -1 in server <Ed2.1 means -> do not write ResvTms – Go for (re)configuring or for RptEna. If you do write ResvTms, do not care for the negative response(s); the response the client get @ RptEna will tell if the report will arrive or not.
ResvTms = -1 in server >= Ed2.1 means -> do write ResvTms before going for (re)configuring or RptEna.
ResvTms = 0 in server <Ed2.1 means -> do write ResvTms before going for(re)configuring or RptEna;.
ResvTms = 0 in server >= Ed2.1 means -> do write ResvTms before going for (re)configuring or RptEna.
- Triggering Tissue changed from in progress (difficult to raise and Ed2 tissue) to https://iec61850.tissue-db.com/tissue/1758
Ed2 client test procedures allows a client per PIXIT Rp22 to support BRCB ResvTms. ResvTms is not a choice of the client to support. It is optional in Ed1 and Ed2 at SErver, but Client need to support the present and the use of it.
I propose to at least update client test procedure to mandate the cBr33.
- Status changed from New to Resolved
- Status changed from Resolved to In Progress
- Discuss in Upcoming Meeting changed from Yes to No
TPWG 20210309 discussion: Issue is very complicated. Cannot add Ed2.0 TISSUEs therefore TPWG cannot mandate new behaviour for Ed2.0 clients therefore Ed2.0 reservation cannot be mandated to become forward compatible with Ed2.1 servers.
61850-7-2:2010 Clause 126.96.36.199 says SetBRCBValues(ResvTms, anyValue) shall fail is ResvTms is -1
which discourages Ed2.0 clients from trying to "actively reserve" a BRCB which is reserved via a SCL ClientLN element.That same clause also states that ResvTms = -1 "shall indicate ... BRCB is currently exclusively reserved ... based upon configuration" which seems to indicate that an "active reservation" (i.e. a write to ResvTms) is not needed.
TPWG will not discussion this redmine issue until until tissue 1758 is resolved outside of the TPWG discussions
- File Redmine636_solution_v1.docx Redmine636_solution_v1.docx added
- Final Decision set to Update cRp2 and mandate cBr33 to ensure client does reserve URCB/BRCB
- Initial Test Document changed from Ed2 TP1.1.2 to Ed2 TP1.2
- Test Case ID changed from TBD to cRp2 and cBr33
- 61850 Standard 7-2 added
- 61850 Standard deleted (
TPWG decided to change cBr33 from conditional to mandatory and change PIXIT-Rp22 to Ed1 only.
And Update cRp2 to ensure client does URCB.Resv=T before configure/enable the URCB.
Update proposal to include certificate page 2 change (change conditional cBr33 to mandatory)
- Status changed from In Progress to Resolved
- Clause Reference changed from Amd1 to Ed2.0
- Closed Reason Test Procedure Update added
Also available in: Atom