Extract from IEC 61850-10 : General Tests case ...



Extract from IEC 61850-10 : General Tests case requirements plus abstract test case examplesConformance test proceduresGeneralThis subclause describes the test procedure requirements, test structure, the test cases (what is to be tested), the format and a few examples of test procedures (how to be tested) which are given in Annex A. Test procedure requirementsThe test procedure requirements are:–The test cases describe what shall be tested, the test procedures describe how a test engineer or a test system shall perform the test.–Test cases include a reference to the applicable paragraph(s) in the referenced document(s).–The test results shall be reproducible in the same test lab and in other test labs.–Support automated testing with minimal human intervention, as far as reasonably possible.–The tests shall focus on situations that can’t easily be tested during, for example, a factory or site acceptance test, and prevent inter-operability risks, for example:check behaviour of the device on delayed, lost, double and out of order packets,configuration, implementation, operation risks,mismatching names, parameters, settings, or data types,exceeding certain limits, ranges or timeouts,force situations to test negative responses,check all (control) state machine paths, andforce simultaneous control operations from multiple clients.–The ACSI tests focus on the application layer (mapping).–The Device Under Test (DUT) is considered as a black box. The I/O and the communication interface are used for testing.–The test includes testing the versions, data model and configuration file, and the use of applicable ISO 9646 series terminology.The test procedures shall be formatted as outlined in Figure 3. With this format, the test procedures document can also be used as test report. A few test procedure examples are depicted in Annex?A.Test purpose, e.g. test if association is set up correctlyTest reference: <ACSI-model><P/N[p/s]><number>e.g. RptP3Test resultReferences to the IEC?61850 documentsClause and SubclauseTest reference Test purpose Passed Failed InconclusiveRef. Part Clause and Subclause of IEC?61850Definition of the expected behavior after a stepExpected resultStep by step description of how to perform the testTest descriptionArea for comments during testing, e.g. found problems and remarksCommentIEC 600/05Figure 3 – Test procedure formatTest structureThe server test cases are structured as follows:Documentation and version control (IEC?61850-4).Configuration file (IEC?61850-6).Data model (IEC?61850-7-3 and IEC?61850-7-4).Mapping of ACSI models and services (IEC?61850-7-2 and applicable SCSM); the corresponding subclauses that define the abstract test cases are given in brackets:–application association model (6.2.4.6)–server, logical device, logical node, and data model (6.2.4.7)–data set model (6.2.4.8)–substitution model (6.2.4.9)–setting group control model (6.2.4.10)–reporting model (6.2.4.11)–log model (6.2.4.12)–generic substation events model (6.2.4.13)–transmission of sampled values model (6.2.4.14)–control model (6.2.4.15)–time and time synchronization model (0)–file transfer model (6.2.4.17)–combination test case (6.2.4.18)Test cases to test a server deviceGeneralThis part of the IEC?61850 series specifies abstract test cases (see 6.2.4.6 to 6.2.4.18). The abstract test cases shall be used for the definition of test procedures to run in tests.NOTE?The concrete syntax of test cases depends on the test system environment, i.e., mainly on the test script language. The concrete test cases are to be provided by test facilities agreed upon by the market participants.Documentation and version control test procedure overviewCheck if the manufacturer’s PICS, MICS and PIXIT documentation and hardware and software versions of the DUT match (IEC?61850-4).Configuration file test casesTest if the ICD configuration file conforms to the SCL XML schema definition according to IEC?61850-6. Check if the ICD configuration file corresponds with the actual data, data types and services exposed by the DUT on the network. Change end-user configurable parameters in the SCD configuration file, configure the DUT using the SCD configuration file (using the supplied configuration tool) and check the configuration using online services corresponds with the SCD file.Data model test casesThe data model test cases shall–verify the presence of mandatory objects for each LN (presence = M, optional = O, and conditional = C);–verify that conditional objects are present and correct;–verify the data type of all objects for each LN; and–verify that data attribute values from the device are in the specified range (this is a continuous effort during the whole conformance test).The test result is a list of object references with data type, common data class, data attribute type, M/O/C presence indication (from IEC?61850-7-3 and IEC?61850-7-4), snapshot attribute values and applicable error indication. The data model extensions shall be checked according to the standardised extension rules including the use of namespaces. The manufacturer-specific data model extensions shall be documented. To enable this, the MICS shall include definitions of the specific logical nodes, common data classes and data attribute types in the same format as IEC?61850-7-3 and IEC?61850-7-4. These definitions are found also in the ICD file and by the response of the service GetDirectory if applicable.The data model mapping shall be verified:–verify the name length and the object expansion;–verify the organisation of the functional components;–verify the naming of the control blocks and logs.Mapping of ACSI models and services test casesTest items shall be grouped together in tables. The tables shall reflect the services specified in the models in 5.2 of IEC?61850-7-2:–Application association (Ass);–Server, Logical device, Logical node, Data, and Data Attribute model (Srv);–Data set model (Dset);–Setting group model (Sg);–Report control model (Rpt);–Log control model (Log);–Generic object oriented system-wide events (Goo);–Control model (Ctl);–Substitution model (Sub);–Transmission of sampled values model (Sv);–Time and time synchronisation model (Tm);–File transfer model (Ft).Test cases are defined for each ACSI model and services in the following categories: –positive = verification of normal conditions, typically resulting in response+–negative = verification of abnormal conditions, typically resulting in response–A test case is mandatory when the applicable ACSI model and ACSI service is supported by the DUT. This is specified in the PICS according to IEC?61850-7-2, Annex A. The test result interpretation (passed/failed) depends on the declared IED capabilities e.g. in the ICD file as well as on the test result.Application association modelPositive test casesThe test cases listed in Table 1 shall apply.Table 1 – Positive test casesTest caseTest case descriptionAssociate and release a TPAA association (IEC 61850-7-2 clause 7.4)Associate and client-abort TPAA association (IEC 61850-7-2 clause 7.4)Associate with maximum number of clients simultaneously (PIXIT)Negative test casesThe test cases listed in Table 2 shall apply.Table 2 – Negative test casesTest caseTest case descriptionCheck that with incorrect authentication parameters and authentication turned on at server the association fails, and with authentication turned off the server associates (IEC 61850-7-2 clause 7.4)Check that with incorrect association parameters at server or client the association fails (IEC 61850-7-2 clause 7.4, PIXIT)Set up maximum+1 associations, verify the last associate is refusedDisconnect the communication interface, the DUT should detect link lost within a specified periodInterrupt and restore the power supply, the DUT should accept an association request when ready Re-use of dropped association resourceExtract from UCAIug Server Test ProceduresA4.1Application associationAbstract test casesAssociate and release a TPAA association (IEC 61850-7-2 clause 7.4)Associate and client-abort TPAA association (IEC 61850-7-2 clause 7.4)Associate with maximum number of clients simultaneously (PIXIT)Check that with incorrect authentication parameters and authentication turned on at server the association fails, and with authentication turned off the server associates (IEC 61850-7-2 clause 7.4)Check that with incorrect association parameters at server or client the association fails (IEC 61850-7-2 clause 7.4, PIXIT)Set up maximum+1 associations, verify the last associate is refusedDisconnect the communication interface, the DUT should detect link lost within a specified periodInterrupt and restore the power supply, the DUT should accept an association request when ready Re-use of dropped association resourceDetailed test proceduresAss1Associate and release a TPAA association Passed Failed InconclusiveIEC 61850-7-2 clause 7.4IEC 61850-8-1 clause 10.2Expected result2. DUT sends Associate Response+3. DUT sends Release Response+Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client request Associate 3.Client request Release 4.Repeat step 2 and 3 250 timesCommentAss2Associate and client-abort TPAA association Passed Failed InconclusiveIEC 61850-7-2 clause 7.4IEC 61850-8-1 clause 10.2Expected result2.DUT sends Associate Response+3.DUT sends Abort Response+Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client requests Associate 3.Client requests Abort 4.Repeat step 2 and 3 250 timesCommentAss3Associate with maximum number of clients simultaneously Passed Failed InconclusiveIEC 61850-7-2 clause 7.4, IEC 61850-8-1 clause 10.2PIXITExpected result2.DUT sends Associate Response+ for each client3.DUT sends Abort Response+ for each clientTest description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client 1 to max requests Associate 3.Client 1 to max requests Release 4.Repeat step 2 and 3 250 timesCommentAssN1Associate with incorrect authentication parameters Passed Failed InconclusiveCommentIEC 61850-8-1 does not support authenticationAssN2Associate with incorrect association parameters Passed Failed InconclusiveIEC 61850-7-2 clause 7.4IEC 61850-8-1 clause 10.2, PIXITExpected result1.Client sends Associate Response+2.Client sends Release Response+4.DUT sends Associate Response- when PIXIT indicates the DUT verifies the parameter, otherwise the DUT sends Associate Response+Test description1.Configure the SIMULATOR and DUT with correct association and authentication parameters and request Associate2.Client requests Release3.Configure the SIMULATOR and DUT with correct authentication parameters and one of the following incorrect configurable association parameters:called / calling transport selectorcalled / calling session selectorcalled / calling presentation selectorcalled / calling AP titlecalled / calling AE qualifier4.Client requests Associate5.When DUT sends Associate Response+, Client sends Release request6.Repeat step 1 to 5 for the next association parameterCommentThe following table indicates the associate response results with incorrect:called / calling transport selector- / +called / calling session selector+ / +called / calling presentation selector+ / +called / calling AP title+ / +called / calling AE qualifier+ / +“-“ = associate failed, DUT sends Response-“+”= associate succeeded, DUT sends Response+AssN3Associate with maximum+1 number of clients simultaneously Passed Failed InconclusiveIEC 61850-7-2 clause 7.4, IEC 61850-8-1 clause 10.2PIXITExpected result2.DUT sends Association Response+ for a count of at least the maximum server associate value in the PIXIT3.DUT sends Release Response+Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client sends Associate request until DUT sends Response-3.Client sends release for all accepted associations4.Repeat step 2 and 3 25 timesCommentAssN4Detection of lost link Passed Failed InconclusiveIEC 61850-7-2 clause 7.4, IEC 61850-8-1 clause 10.2PIXITExpected result2.DUT sends Associate Response+3.DUT sends GetDataValues Response+6.DUT sends GetDataValues Response- Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client requests Associate3.Client requests a correct GetDataValues 4.Disconnect the physical link, between the switch and the client, some seconds longer than the KEEP ALIVE timeout specified in the PIXIT5.Connect the physical link6.Verify the DUT has lost the association by sending a correct GetDataValues requestCommentAssN5Power supply interrupt Passed Failed InconclusiveIEC 61850-7-2 clause 7.4, IEC 61850-8-1 clause 10.2 PIXITExpected result2.DUT sends Associate Response+4.The DUT sends Associate Response+Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2.Client requests Associate3.Interrupt and restore the DUT power supply and wait till the DUT is initialised4.Client requests Associate and DUT Response+CommentAssN6Re-use of dropped association resource Passed Failed InconclusiveIEC 61850-7-2 clause 7.4, IEC 61850-8-1 clause 10.2PIXITExpected result2. DUT sends at least one Associate Response+ 3. DUT sends Abort Response+ 5. DUT sends Asociate Response+ 6. DUT sends GetDataValues Response+7.Note: DUT should internally abort all stack layers, a half-open TCP connection is not allowed 9. DUT sends Associate Response+. 10. DUT sends GetDataValues Response+Test description1.Configure the SIMULATOR and DUT with the correct association and authentication parameters2. Client 1 requests associations until they are refused3. Client 1 aborts the last association4. DUT issues keepalives on all associations5. Client 2 requests association and sends keepalves 6. Client 2 requests a correct GetDataValues7. Disconnect physical link between Client 2 and the switch, some seconds longer than the KEEPALIVE timeout specified in the PIXIT8.Connect the physical link to Client29. Client 2 requests association10.Client 2 requests a correct GetDataValuesComment ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download