Project

General

Profile

Issues #6279

sSBOns8 - Test and Check in Cancel after Select request

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

Status:
Closed
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
05/30/2023
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
TP1.2
Updated Test Document:
TP1.3
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

Solution to redmine 6188 and 6279 sSBOns8.docx Solution to redmine 6188 and 6279 sSBOns8.docx 22.8 KB Richard Schimmel, 05/16/2023 09:10 AM

Also available in: Atom PDF