Project

General

Profile

Support #480

A different client made use of a URCB that had been reserved in SCL for use by a different client via ClientLN. Currently, there

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:
36
Source:
IOP_2013
TF Unique ID:
36 # IOP_2013
WG10 Proposal:

According to Cathedral City meeting (ref. to UFTF-CathedralMOM20160219) this issue is closed.

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

Already solved in http://tissue.iec61850.com/tissue.mspx?issueid=1276 . This requires Client to read the SCD file containing the reservation

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

Description

A different client made use of a URCB that had been reserved in SCL for use by a different client via ClientLN.
Currently, there is no way to enforce reservation on the server without utilizing Authentication which was not part of the IOP. Therefore, it is up to the clients to behave in accordance with the ClientLN reservation. Since the URCB does not have an indication that the RCB is reserved (e.g. no resvTms), this may happen in the real world. An option could be to add a reservation indicator into the control block as part of IEC 61850-8-1.

#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Closed

Also available in: Atom PDF