Project

General

Profile

Issues #5138

sBr13 without pre-assignment

Added by Richard Schimmel over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
8-1
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

Some Ed2 servers do support BRCB.Owner, but don't support BRCB.ResvTms and the corresponding pre-assignment. As such these servers don't support step 8:

1. Client requests GetBRCBValues of a free (not pre-assigned) BRCB
2. Client configures and enables this BRCB using SetBRCBValues
3. Client requests GetBRCBValues
4. Client disables the BRCB
5. Client requests GetBRCBValues
6. Client releases the association, waits more then the reservation time and associates again
7. Client requests GetBRCBValues
8. A non pre-assigned Client requests GetBRCBValues of a pre-assigned BRCB
When PIXIT Rp13 indicates, the server accepts any client to configure/enable a pre-assigned BRCB continue with:
9. Client configures and enables this BRCB using SetBRCBValues
10. Client requests GetBRCBValues
11. Client disables the BRCB
12. Client requests GetBRCBValues
13. Client releases the association, waits more than the reservation time and associates again
14. Client requests GetBRCBValues

For Ed2 I propose to make step 8 and 14 conditional "when resvTms is not supported skip step 8 and 14".

Also available in: Atom PDF