1、 ETSI ES 202 196-3 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 3: Framework(Parlay 3)ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-03-OSA Keywords API, OSA, TSS Essential, or po
2、tentially 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, has been carrie
3、d 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 Technical Committee
4、Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 3 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 2: “Common data
5、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 management SCF“; Pa
6、rt 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 and Test Purposes
7、(TSS Application Programming Interface (API); Part 3: Framework (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: “Information technology - Open Systems
8、 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 ETS 300 406: “Methods for Testin
9、g 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-3 1, ISO/IEC 9646-1 3 and ISO/IEC 9646-2 4 and the
10、 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/IEC 9646-1 3. Implementation
11、 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-3 V1.2.1 (2005-02) 7 IXIT proforma: Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3
12、. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Access Session ATM Abstract Test Method ATS Abstract Test Suite FTA Framework To Application FTE Framework To Enterprise FTS Framework To Service FW FrameWork ICS Implementation Conformance Statement
13、IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester SCF Switching Control Function SUT System Under Test TP Test Purpose TSM Trust and Security Management TSS Test Suite Structure 4 Test Suite Structure (TSS) for Framework Framework (FW): Framework Access
14、Session (AS): - Trust and Security Management (TSM). Framework to Application (FTA): - Service discovery; - Service agreement management; - Integrity management; - Event notification. Framework to Service (FTS): - Service registration; - Service instance lifecycle management; - Service discovery; -
15、Integrity management; - Event notification. Framework to Enterprise operator (FTE): - Service subscription. ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 8 5 Test Purposes (TP) for Framework For each test requirement a TP is defined. 5.1 TP naming convention TPs are numbered, starting at 01, within each g
16、roup. 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: _ = IUT name: “FW“ for FrameWork SCF = group number: two character field representing the group reference acco
17、rding to TSS = sequential number: (01 to 99) 5.2 Source of TP definition The TPs are based on ES 201 915-3 1. 5.3 Test strategy As the base standard ES 201 915-3 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the ICS specif
18、ication 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 ETS 300 406 5). 5.4 TPs for the Framework All ICS items referred to i
19、n 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. The procedures to trigger the SCF to call methods in the application are dependant on the underlying network architecture and
20、are out of the scope of this test specification. Those method calls are preceded by the words “Triggered action“. 5.4.1 Framework Access Session API 5.4.1.1 Trust and Security Management (TSM) Methods/Test Nr 01 02 03 04 05 06 07 08 09 initiateAuthentication X X X X X X X X X requestAccess X X X X X
21、 X X X X selectEncryptionMethod X X X X X X X authenticate X X X X X X X abortAuthentication X AuthenticationSucceeded X X X X X X X obtainInterface X X X X X obtainInterfaceWithCallback X endAccess X listInterfaces X releaseInterface X ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 9 Test FW_AS_TSM_01 Sum
22、mary: Initial Access for Trusted Parties, no authentication is needed, all methods, successful Reference: ES 201 915-3 1, clause 6.1.1.1 Precondition: Authentication not required by IUT Preamble: Registration of the tester (Application) to the IUT (framework) by an off-line service agreement. Test S
23、equence: 1. Method call initiateAuthentication() on IpInitial interface. Parameters: clientDomain, authType Check: valid value of TpAuthDomain is returned 2. Triggered action: cause IUT to call authenticationSucceeded() method on the testers (Application) IpClientAPILevelAuthentication interface. Pa
24、rameters: none 3. Method call requestAccess() on IpAPILevelAuthentication interface. Parameters: accessType, clientAccessInterface Check: valid value of TpInterfaceRef is returned : IpClientAPILevelAuthentication Client : IpAPILevelAuthentication Framework : IpInitialinitiateAuthentication(clientDom
25、ain, authType)authDomainauthenticationSucceeded( )requestAccess(accessType, clientAccessInterface)intReferencePreamble : registration of the tester (application) to the Framework by an off-line service agrement.ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 10Test FW_AS_TSM_02 Summary: API level authentica
26、tion, FW authenticates the client only, all methods, successful, use of listInterface method to get the name of supported interfaces Reference: ES 201 915-3 1, clauses 6.1.1.2 and 6.1.1.4 Precondition: API level authentication required by IUT, listInterfaces supported Preamble: Registration of the t
27、ester (Application) to the IUT (framework) by an off-line service agreement. Test Sequence: 1. Method call initiateAuthentication on IpInitial interface. Parameters: clientDomain, authType=P_OSA_AUTHENTICATION Check: valid value of TpAuthDomain is returned 2. Method call selectEncryptionMethod on Ip
28、APILevelAuthentication interface. Parameters: encryptionCaps Check: valid value of TpEncryptionCapability is returned 3. Triggered action: cause IUT to call authenticate method on the testers (Application) IpClientAPILevelAuthentication interface. Parameters: challenge NOTE: This method may be repea
29、ted with different challenges as required by the IUT. 4. Triggered action: cause IUT to call authenticationSucceeded method on the testers (Application) IpClientAPILevelAuthentication interface. Parameters: none 5. Method call requestAccess on IpAPILevelAuthentication interface. Parameters: accessTy
30、pe, clientAccessInterface Check: valid value of TpInterfaceRef is returned 6. Method call listInterfaces on IpAccess interface. Parameters: none Check: valid value of TpInterfaceNameList is returned 7. Method call obtainInterface on IpAccess interface. Parameters: interfaceName (suggest use of P_DIS
31、COVERY) Check: valid value of IpInterfaceRef is returned ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 11: IpClientAPILevelAuthentication Client : IpInitial : IpAPILevelAuthentication Framework : IpAccessPreamble : registration of the tester (application) to the Framework by an off-line service agrement.r
32、equestAccess(accessType, clientAccessInterface)intReferenceinitiateAuthentication(clientDomain, P_OSA_AUTHENTICATION)authDomainselectEncryptionMethod(encryptionCaps)encryptionCapabilityauthenticate(challenge)octetSetauthenticati onSucceeded( )listInt erfaces( )interfaceNameListobtainInterface(interf
33、aceName)interfaceRefETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 12Test FW_AS_TSM_03 Summary: API level authentication, FW and client authenticate mutually, all methods, successful Reference: ES 201 915-3 1, clauses 6.1.1.2 and 6.1.1.4 Precondition: Authentication required by IUT Preamble: Registration o
34、f the tester (Application) to the IUT (framework) by an off-line service agreement. Test Sequence: 1. Method call initiateAuthentication on IpInitial interface. Parameters: clientDomain, authType=P_OSA_AUTHENTICATION Check: valid value of TpAuthDomain is returned 2. Method call selectEncryptionMetho
35、d on IpAPILevelAuthentication interface. Parameters: encryptionCaps Check: valid value of TpEncryptionCapability is returned 3. Triggered action: cause IUT to call authenticate method on the testers (Application) IpClientAPILevelAuthentication interface. Parameters: challenge NOTE 1: This method may
36、 be repeated with different challenges as required by the IUT. 4. Triggered action: cause IUT to call authenticationSucceeded method on the testers (Application) IpClientAPILevelAuthentication interface. Parameters: none 5. Method call authenticate on IpAPILevelAuthentication interface. Parameters:
37、challenge Check: valid value of TpOctetSet is returned NOTE 2: This method may be repeated with different challenges as required by the tester. 6. Method call authenticationSucceeded on IpAPILevelAuthentication interface. Parameters: none Check: no exception is returned. NOTE 3: The method calls 5.
38、and 6. may interleave between the method calls 3. and 4. 7. Method call requestAccess on IpAPILevelAuthentication interface. Parameters: accessType, clientAccessInterface Check: valid value of TpInterfaceRef is returned 8. Method call obtainInterface on IpAccess interface. Parameters: interfaceName
39、(suggest use of P_DISCOVERY) Check: valid value of IpInterfaceRef is returned ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 13: IpClientAPILevelAuthentication Client : IpInitial : IpAPILevelAuthenticationFramework : IpAccessPreamble : registration of the tester (application) to the Framework by an off-lin
40、e service agrement.initiateAuthentication(clientDomain, P_OSA_AUTHENTICATION)authDomainrequestAccess(accessType, clientAccessInterface)intReferenceselectEncryptionMethod(encryptionCaps)encryptionCapabilityauthenticate(challenge)octetSetauthenticationSucceeded( )obtainInterface(interfaceName)interfac
41、eRefauthenticate(challenge)octetSetauthenticationSucceded()ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 14Test FW_AS_TSM_04 Summary: API level authentication, FW authenticates the client only, unsuccessful call of requestAccess method (preceding authenticationSucceeded method call) Reference: ES 201 915-
42、3 1, clauses 6.1.1.2 and 6.1.1.4 Precondition: Authentication required by IUT. Preamble: Registration of the tester (Application) to the IUT (framework) by an off-line service agreement. Test Sequence: 1. Method call initiateAuthentication on IpInitial interface. Parameters: clientDomain, authType=P
43、_OSA_AUTHENTICATION Check: valid value of TpAuthDomain is returned 2. Method call selectEncryptionMethod on IpAPILevelAuthentication interface. Parameters: encryptionCaps Check: valid value of TpEncryptionCapability is returned 3. Method call requestAccess on IpAPILevelAuthentication interface. Para
44、meters: accessType, clientAccessInterface Check: P_ACCESS_DENIED is returned Client : IpInitial : IpAPILevelAuthenticationPreamble : registration of the tester (application) to the Framework by an off-line service agrement.ini ti at eAuthe nti ca ti on(cl ien tD om ain , P_O SA _AUT HEN T IC ATI ON)
45、authDomainselectEncryptionMethod(encryptionCaps)encryptionCapabilityrequestAccess(accessType, clientAccessInterface)P_ACCESS_DENIEDETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 15Test FW_AS_TSM_05 Summary: API level authentication, FW authenticates the client only, use of obtainInterfaceWithCallback, succ
46、essful Reference: ES 201 915-3 1, clauses 6.1.1.2 and 6.1.1.4 Precondition: Authentication required by IUT Preamble: Registration of the tester (Application) to the IUT (framework) by an off-line service agreement. Test Sequence: 1. Method call initiateAuthentication on IpInitial interface. Paramete
47、rs: clientDomain, authType=P_OSA_AUTHENTICATION Check: valid value of TpAuthDomain is returned 2. Method call selectEncryptionMethod on IpAPILevelAuthentication interface. Parameters: encryptionCaps Check: valid value of TpEncryptionCapability is returned 3. Triggered action: cause IUT to call authe
48、nticate method on the testers (Application) IpClientAPILevelAuthentication interface. Parameters: challenge NOTE: This method may be repeated with different challenges as required by the IUT. 4. Triggered action: cause IUT to call authenticationSucceeded method on the testers (Application) IpClientA
49、PILevelAuthentication interface. Parameters: none Check: no exception is returned. 5. Method call requestAccess on IpAPILevelAuthentication interface. Parameters: accessType, clientAccessInterface 6. Method call obtainInterfaceWithCallback on IpAccess interface. Parameters: interfaceName (suggest use of P_FAULT_MANAGER), clientInterface Check: valid value of IpInterfaceRef is returned ETSI ETSI ES 202 196-3 V1.2.1 (2005-02) 16: IpInitial : IpClientAPILev elAuthentication Client : IpAPILevelAuthenticationFram
