Project

General

Profile

Issues #6279

sSBOns8 - Test and Check in Cancel after Select request

Added by Hua Qin over 1 year ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Due date:
05/30/2023
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
sSBOns8
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

There is no way to check the consistency between Select and Cancel.
But as a normal control service, it should be subject to the normal checks, such as Test and Check in this test case.
Thus, DUT may give a Cancel response- on step h/j.

I understand that this test case is introduced because of TISUSE 1703.
Tissue 1703 comments talks about there is no way to check the consistency in SBOns situation.
The last comment also says "for the case of normal security a cancel request has to carry service parameters that have no meaning."
Tissue 1703 suggests that update will be added into part 7-2 amend 1.

In part 7-2 ED2 Amend 1, I do not find anywhere mentioning it.

But in part 8-1 20.7.4 says "the service parameter consistency check of the Cancel request can not be excecuted in case the Cancel request is used after a Select request, as long as no Operate / TimeActivatedOperate request was received.Cancel response+ "

Again this part talks about no way to check the consistency.


Files

#1

Updated by IEC 61850 TPWG over 1 year ago

  • Due date set to 03/21/2023
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel
#2

Updated by IEC 61850 TPWG about 1 year ago

  • Due date changed from 03/21/2023 to 05/02/2023
#3

Updated by Richard Schimmel about 1 year ago

What is the proposed solution? Allow Cancel response- on Cancel.Check=00/11 (step h and j)? If both Cancel+ and Cancel- are allowed we just skip step h and j. (See also #6188 in which we removed the Cancel.orCat)

#4

Updated by IEC 61850 TPWG about 1 year ago

Check bits are not present, this requirement needs to be removed.

Further review needed.

#5

Updated by IEC 61850 TPWG about 1 year ago

  • Due date changed from 05/02/2023 to 05/30/2023

Richard to propose solution.

Device may do plausibility check on each parameter, for example orCat and Test. Remove Cancel.Test step.

#7

Updated by IEC 61850 TPWG 12 months ago

  • Status changed from In Progress to Resolved
  • Closed Reason Test Procedure Update added
  • Closed Reason deleted (--Not Set---)
#8

Updated by Richard Schimmel 4 months ago

  • Status changed from Resolved to Closed
  • Updated Test Document set to TP1.3

Also available in: Atom PDF