1、 ETSI ES 202 196-7 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 7: Terminal capabilities SCF(Parlay 3)ETSI ETSI ES 202 196-7 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-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 covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part
5、2: “Common data definitions“; Part 3: “Framework“; Part 4: “Call control SCF“; Part 5: “User interactions SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal capabilities SCF“; Part 8: “Data session control SCF“; Part 9: “Generic messaging SCF“; Part 10: “Connectivity manager SCF“; Part 11: “Account man
6、agement SCF“; Part 12: “Charging SCF“. To evaluate conformance of a particular implementation, it is necessary 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 an
7、d Test Purposes (TSS Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 3)“. 2 ETSI ES 202 170: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification (Parlay 3)“. 3 ISO/IEC 9646-1: “Infor
8、mation technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 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
9、ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 201 915-7 1, ISO/IEC 9646-
10、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. ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation Conformance Statement (ICS): Refer to ISO
11、/IEC 9646-1 3. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 196-7 V1.2.1 (2005-02) 6 IXIT proforma: Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Test Purpose (T
12、P): 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 Conformance Statement IUT Implementation Under Test IXIT Implementat
13、ion eXtra Information for Testing LT Lower Tester OSA Open Service Access TC Terminal Capabilities TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Terminal Capabilities SCF. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convent
14、ion 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 naming convention scheme Identifier: _ = SCF name: “TC“ for Terminal Capabilities SCF = group nu
15、mber: two character field representing the group reference according to TSS = sequential number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 201 915-7 1. 5.1.3 Test strategy As the base standard ES 201 915-7 1 contains no explicit requirements for testing, the TPs were generated
16、 as a result of an analysis of the base standard and the PICS specification ES 202 170 2. The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see E
17、TS 300 406 5). ETSI ETSI ES 202 196-7 V1.2.1 (2005-02) 7 5.2 TPs for the Terminal Capabilities SCF All PICS items referred to in this clause are as specified in ES 202 170 2 unless indicated otherwise by another numbered reference. All parameters specified in method calls are valid unless specified.
18、 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 this test specification. Those method calls are preceded by the words “Triggered action“. 5.2.1 Terminal Capabilities, SCF side Test TC_01 Summary: I
19、pTerminalCapabilities.getTerminalCapability(), successful Reference: ES 201 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call getTerminalCapabilities() Parameters: terminaIdentity, value recognized by IUT Check: valid value of TpTerminalCapabilities is returned Application : IpTerminalCap
20、abilities1. getTerminalCapabilities(recognised terminalIdentity)terminalCapabilitiesETSI ETSI ES 202 196-7 V1.2.1 (2005-02) 8 Test TC_02: Summary: IpTerminalCapabilities.getTerminalCapability(), invalid terminalIdentity Reference: ES 201 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Method call g
21、etTerminalCapabilities() Parameters: invalid (non existing) terminaIdentity Check: P_INVALID_TERMINAL_ID exception is returned Application : IpTerminalCapabilities1. getTerminalCapabilities(non-existent terminalIdentity)P_INVALID_TERMINAL_ID exception5.2.2 Terminal Capabilities, application side Tes
22、t TC_APP_01 Summary: IpTerminalCapabilities.getTerminalCapability(), successful Reference: ES 201 915-7 1, clauses 7, 8.1 and 10 Test Sequence: 1. Triggered Action: cause IUT to call getTerminalCapabilities() method on the testers (SCFs) IpTerminalCapabilities interface. Check: valid value of termin
23、aIdentity is transmitted Return: valid value of TpTerminalCapabilities is returned Application : IpTerminalCapabilitiesgetTerminalCapabilities(terminalIdentity)terminalCapabilitiesETSI ETSI ES 202 196-7 V1.2.1 (2005-02) 9 History Document history V1.1.1 August 2003 Publication V1.2.1 December 2004 Membership Approval Procedure MV 20050211: 2004-12-14 to 2005-02-11 V1.2.1 February 2005 Publication
