Issues #6279
sSBOns8 - Test and Check in Cancel after Select request
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
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
Updated by Richard Schimmel over 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)
Updated by IEC 61850 TPWG over 1 year ago
Check bits are not present, this requirement needs to be removed.
Further review needed.
Updated by IEC 61850 TPWG over 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.
Updated by Richard Schimmel over 1 year ago
- File Solution to redmine 6188 and 6279 sSBOns8.docx Solution to redmine 6188 and 6279 sSBOns8.docx added
removed step 2g and 2h added solution.
Updated by IEC 61850 TPWG over 1 year ago
- Status changed from In Progress to Resolved
- Closed Reason Test Procedure Update added
- Closed Reason deleted (
--Not Set---)
Updated by Richard Schimmel 9 months ago
- Status changed from Resolved to Closed
- Updated Test Document set to TP1.3