ETSI ES 202 388-7-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 7 Terminal Capabilities SCF (V1 1 1 Pa_1.pdf

1、 ETSI ES 202 388-7 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 7: Terminal Capabilities SCF(Parlay 4)ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-07-OSA Keywords API, OSA, TSS

2、Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches,

3、 has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Tech

4、nical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 6. To evaluate conformance of a particular implementation, it is nec

5、essary to have a set of test purposes to evaluate the dynamic behaviour of the Implementation Under Test (IUT). The specification containing those test purposes is called a Test Suite Structure and Test Purposes (TSS Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay

6、4)“. 2 ETSI ES 202 363: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification; (Parlay 4)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part

7、 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 5 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing spe

8、cifications; Standardization methodology“. 6 ETSI ES 202 388-1: “Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 1: Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the

9、 terms and definitions given in ES 202 915-7 1, ISO/IEC 9646-1 3, ISO/IEC 9646-2 4 and the following apply: abstract test case: Refer to ISO/IEC 9646-1 3. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Ref

10、er to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 6 ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1

11、 3. IXIT proforma: Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ATM Abstract Test Method ATS Abstract Test Suite ICS Implementation Conform

12、ance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access SCF Service Capability Feature TC Terminal Capabilities TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Terminal Capabilities SCF. 5 Test Purpo

13、ses (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite (see table 1). Table 1: TP identifier nami

14、ng convention scheme Identifier: _ = SCF name: “TC“ for Terminal Capabilities SCF = group number: two character field representing the group reference according to TSS = sequential number: (01-99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-7 1. ETSI ETSI ES 202 388-7 V1.1.1 (2005-

15、03) 7 5.1.3 Test strategy As the base standard ES 202 915-7 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ES 202 363 2. The TPs are only based on conformance requirements related to the externally ob

16、servable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see ETS 300 406 5). 5.2 TPs for the Terminal Capabilities SCF All PICS items referred to in this clause are as specified in ES 202 363 2 unless indicated otherwise by another

17、 numbered reference. All parameters specified in method calls are valid unless specified. The procedures to trigger the SCF to call methods in the application are dependant on the underlying network architecture and are out of the scope of the present document. Those method calls are preceded by the

18、 words “Triggered action“. 5.2.1 Terminal Capabilities, SCF side Test TC_01 Summary: IpTerminalCapabilities.getTerminalCapability(), successful Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call getTerminalCapabilities() Parameters: terminalIdentity, value recognized by I

19、UT Check: valid value of TpTerminalCapabilities is returned Application : IpTerminalCapabilities1. getTerminalCapabilities(recognised terminalIdentity)terminalCapabilitiesETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 8 Test TC_02: Summary: IpTerminalCapabilities.getTerminalCapability(), invalid terminalId

20、entity Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call getTerminalCapabilities() Parameters: invalid (non existing) terminalIdentity Check: P_INVALID_TERMINAL_ID exception is returned Application : IpTerminalCapabilities1. getTerminalCapabilities(non-existent terminalI

21、dentity)P_INVALID_TERMINAL_ID exceptionTest TC_03: Summary: IpExtendedTerminalCapabilities all method, successful Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call triggeredTerminalCapabilityStartReq() Parameters: appTerminalCapabilities, terminals, capabilityScope, crit

22、eria Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call triggeredTerminalCapabilityReport() method on the testers (Application) IpAppExtendedTerminalCapabilities interface. Parameters: assignmentID, terminals, criteria, capabilities 3. Method call triggeredTermin

23、alCapabilityStop () Parameters: assignmentID returned in 1. Check: no exception is returned ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 9 Application: IpExtendedTerminalCapabilities: IpAppExtendedTerminalCapabilitiestriggeredTerminalCapabilityStartReq(appTerminalCapabilities, terminals, capabilityScope,

24、 criteria)TpAssignmentIDtriggeredTerminalCapabilityReport(assignmentID, terminals, criteria, capabilities)triggeredTerminalCapabilityStop(assignmentID)Test TC_04: Summary: IpExtendedTerminalCapabilities triggeredTerminalCapabilityStartReq, P_INVALID_CRITERIA Reference: ES 202 915-7 1, clauses 7, 8.1

25、 and 10 Test Sequence: 1. Method call triggeredTerminalCapabilityStartReq() Parameters: appTerminalCapabilities, terminals, capabilityScope, invalid criteria Check: P_INVALID_CRITERIA is returned Application: IpExtendedTerminalCapabilitiestriggeredTerminalCapabilityStartReq(appTerminalCapabilities,

26、terminals, capabilityScope, invalid criteria)P_INVALID_CRITERIAETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 10Test TC_05: Summary: IpExtendedTerminalCapabilities triggeredTerminalCapabilityStartReq, P_INVALID_TERMINAL_ID Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call trigg

27、eredTerminalCapabilityStartReq() Parameters: appTerminalCapabilities, terminals with at least one invalid terminalID, capabilityScope, criteria Check: P_INVALID_TERMINAL_ID is returned Application: IpExtendedTerminalCapabilitiestriggeredTerminalCapabilityStartReq(appTerminalCapabilities, terminals w

28、ith at least one invalid terminalID, capabilityScope, criteria)P_INVALID_TERMINAL_IDTest TC_06: Summary: IpExtendedTerminalCapabilities triggeredTerminalCapabilityStop, P_INVALID_ASSIGNMENT_ID Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call triggeredTerminalCapabilityS

29、tartReq() Parameters: appTerminalCapabilities, terminals, capabilityScope, criteria Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call triggeredTerminalCapabilityReport() method on the testers (Application) IpAppExtendedTerminalCapabilities interface. Parameters:

30、 assignmentID, terminals, criteria, capabilities 3. Method call triggeredTerminalCapabilityStop () Parameters: invalid assignmentID, Check: P_INVALID_ASSIGNMENT_ID is returned ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 11Application: IpExtendedTerminalCapabilities: IpAppExtendedTerminalCapabilitiestrig

31、geredTerminalCapabilityStartReq(appTerminalCapabilities, terminals, capabilityScope, criteria)TpAssignmentIDtriggeredTerminalCapabilityStop(invalid assignmentID)triggeredTerminalCapabilityReport(assignmentID, terminals, criteria, capabilities)P_INVALID_ASSIGNMENT_ID5.2.2 Terminal Capabilities, appli

32、cation side Test TC_APP_01 Summary: IpTerminalCapabilities.getTerminalCapability(), successful Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Triggered Action: cause IUT to call getTerminalCapabilities() method on the testers (SCF) IpTerminalCapabilities interface. Check: valid v

33、alue of terminalIdentity is transmitted, Return: valid value of TpTerminalCapabilities is returned ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 12Application : IpTerminalCapabilitiesgetTerminalCapabilities(terminalIdentity)terminalCapabilitiesTest TC_APP_02 Summary: IpAppExtendedTerminalCapabilities trig

34、geredTerminalCapabilityReport, successful Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Triggered action: cause IUT to call triggeredTerminalCapabilityStartReq () method on the testers (SCF) IpExtendedTerminalCapabilities interface. Parameters: assignmentID, terminals, criteria,

35、 capabilities 2. Method call triggeredTerminalCapabilityReport () Parameters: assignmentID, terminals, criteria, capabilities Check: no exception is returned 3. Triggered action: cause IUT to call triggeredTerminalCapabilityStartReq () method on the testers (SCF) IpExtendedTerminalCapabilities inter

36、face. Parameters: assignmentID returned in 1 ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 13: IpExtendedTerminalCapabilitiesApplication : IpAppExtendedTerminalCapabilitiestriggeredTerminalCapabilityStartReq(appTerminalCapabilities, terminals, capabilityScope, criteria)TpAssignmentIDtriggeredTerminalCapab

37、ilityStop(assignmentID)triggeredTerminalCapabilityReport(assignmentID, terminals, criteria, capabilities)Test TC_APP_03 Summary: IpAppExtendedTerminalCapabilities triggeredTerminalCapabilityReportErr, successful Reference: ES 202 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Triggered action: cau

38、se IUT to call triggeredTerminalCapabilityStartReq () method on the testers (SCF) IpExtendedTerminalCapabilities interface. Parameters: assignmentID, terminals, criteria, capabilities 2. Method call triggeredTerminalCapabilityReportErr() Parameters: assignmentID, terminals, criteria, capabilities Ch

39、eck: no exception is returned 3. Triggered action: cause IUT to call triggeredTerminalCapabilityStartReq () method on the testers (SCF) IpExtendedTerminalCapabilities interface. Parameters: assignmentID returned in 1 ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 14: IpAppExtendedTerminalCapabilities: IpEx

40、tendedTerminalCapabilitiesApplicationtriggeredTerminalCapability StartReq(appTerminalCapabilities, terminals, capabilityScope, criteria)TpAssignmentIDtriggeredTerminalCapabilityStop(assignmentID)triggeredTerminalCapabilityReportErr(assignmentId, terminals, cause)ETSI ETSI ES 202 388-7 V1.1.1 (2005-03) 15History Document history V1.1.1 January 2005 Membership Approval Procedure MV 20050311: 2005-01-11 to 2005-03-11 V1.1.1 March 2005 Publication