ETSI ES 202 196-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interactions SCF《开放业务接入(OSA) 应用_1.pdf

《ETSI ES 202 196-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interactions SCF《开放业务接入(OSA) 应用_1.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 202 196-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interactions SCF《开放业务接入(OSA) 应用_1.pdf（72页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 202 196-5 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 5: User interactions SCF(Parlay 3)ETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-05-OSA Keywords API, OSA, TSS Esse

2、ntial, 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, has

3、 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 Technica

4、l Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 5 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 2: “

5、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 managem

6、ent 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 and Te

7、st Purposes (TSS Application Programming Interface (API); Part 5: User Interaction 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: “Information te

8、chnology - 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 ETS 300 4

9、06: “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-5 1, ISO/IEC 9646-1 3, ISO/

10、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/IEC 9646

11、-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-5 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 (TP): Refer

12、 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 Implementation eXtra

13、 Information for Testing LT Lower Tester OSA Open Service Access TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) User Interaction: IPUIManager interface. IPUI interface. IPUICall interface. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 T

14、P 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 naming convention scheme Identifier: _ = SCG name: “UI“ for User Interaction par

15、t of User Interaction SCF UI_APP for User Interaction part of User interaction Application = sequential number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 201 915-5 1. ETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 7 5.1.3 Test strategy As the base standard ES 201 915-5 1 contains no

16、explicit requirements for testing, the TPs were generated 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

17、 which a real implementation is likely to be faced (see ETS 300 406 5). 5.2 TPs for the User Interaction 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

18、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 this test specification. Those method calls are preceded by the words “Triggered action“. 5.2.1 User Interaction, SCF side Pre-requisite: R

19、egistration of the IUT (User Interaction SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpUIManager interface through selecting that service and signing the required service agreement. 5.2.1.1 IpUIManager interface Test UI_01 Summa

20、ry: IpUIManager, createUI method, successful Reference: ES 201 915-5 1, clause 8.1 Selection: createUI method supported - PICS item: 2 UIM1 Test Sequence: 1. Method call createUI() Parameters: appUI, userAddress Check: valid value of TpUIIdentifier is returned : IpAppUIManager : IpUIManagercreateUI(

21、appUI, userAddress)userInteractionETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 8 Test UI_02 Summary: IpUIManager, createUI method, P_INVALID_NETWORK_STATE Reference: ES 201 915-5 1, clause 8.1 Selection: createUI method supported - PICS item: 2 UIM1 Condition: the underlying protocol cannot support the m

22、ethod call. Test Sequence: 1. Method call createUI() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned : IpAppUIManager : IpUIManagercreateUI(appUI, userAddress)P_INVALID_NETWORK_STATETest UI_03 Summary: IpUIManager, createUI method, P_INVALID_INTERFACE_TYPE Reference: ES 201

23、 915-5 1, clause 8.1 Selection: createUI method supported - PICS item: 2 UIM1 Test Sequence: 1. Method call createUI() Parameters: appUI including an invalid reference type, userAddress Check: P_INVALID_ INTERFACE_TYPE is returned : IpAppUIManager : IpUIManagercreateUI(appUI, userAddress)P_INVALID_I

24、NTERFACE_TYPEETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 9 Test UI_04 Summary: IpUIManager, createUICall method, successful Reference: ES 201 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2 UIM2 Test Sequence: 1. Method call createUICall() Parameters: appUI, uiTargetObject Ch

25、eck: valid value of TpUIIdentifier is returned : IpAppUIManager : IpUIManagercreateUICall(appUI, uiTargetObject)userInteractionTest UI_05 Summary: IpUIManager, createUICall method, P_INVALID_NETWORK_STATE Reference: ES 201 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2 U

26、IM2 Condition: the underlying protocol cannot support the method call. Test Sequence: 1. Method call createUICall() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned : IpAppUIManager : IpUIManagercreateUICall(appUI, uiTargetObject)P_INVALID_NETWORK_STATEETSI ETSI ES 202 196-5

27、 V1.2.1 (2005-02) 10Test UI_06 Summary: IpUIManager, createUICall method, P_INVALID_INTERFACE_TYPE Reference: ES 201 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2 UIM2 Test Sequence: 1. Method call createUICall() Parameters: appUI including an invalid reference type, us

28、erAddress Check: P_INVALID_INTERFACE_TYPE is returned : IpAppUIManager : IpUIManagercreateUICall(appUI, uiTargetObject)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 11Test UI_07 Summary: IpUIManager, all createNotification and destroyNotification methods, successful Reference: ES 2

29、01 915-5 1, clause 8.1 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call destroyNotification() Parameters: assignmentID as ret

30、urned in 1 Check: no exception is returned. : IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriteria1)assignmentIDdestroyNoti ficati on(assignmentID)ETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 12Test UI_08 Summary: IpUIManager, receipt of reportEventNotification method, successful Re

31、ference: ES 201 915-5 1, clauses 8.1 and 8.2 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call reportE

32、ventNotification() method on the testers (Application) IpAppUIManager interface. Check: valid value of userInteraction, eventNotificationInfo and assignmentID given in 1. is transmitted, Return: valid value of IpAppUIRef : IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriter.assi

33、gnmentIDreportEventNotification(userInteraction, eventNotificationInfo, assignmentID)appUIETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 13Test UI_09 Summary: IpUIManager, createNotification method, P_INVALID_INTERFACE_TYPE Reference: ES 201 915-5 1, clause 8.1 Selection: createNotification methods support

34、ed - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager including an invalid reference type, eventCriteria, Check: P_INVALID_INTERFACE_TYPE is returned : IpAppUIManager : IpUIManagercreateNotification(appUIManager_inv, eventCriteria)P_INVALID_INTERFACE_TYPE

35、Test UI_10 Summary: IpUIManager, createNotification method, P_INVALID_CRITERIA Reference: ES 201 915-5 1, clause 8.1 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria containing an invalid cr

36、iteria. Check: P_INVALID_CRITERIA is returned. : IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriteria_inv)P_INVALID_CRITERIAETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 14Test UI_11 Summary: IpUIManager, createNotification and changeNotification methods, P_INVALID_ASSIGNMENT_ID Refe

37、rence: ES 201 915-5 1, clause 8.1 Selection: createNotification and changeNotification methods supported - PICS item: 2 UIM3 AND UIM5 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call changeNoti

38、fication() Parameters: assignmentID different from returned in 1., eventCriteria. Check: P_INVALID_ASSIGNMENT_ID is returned. : IpAppUIManager : IpUIManagerchangeNotification(assignmentID_inv, eventCriteria)P_INVALID_ASSIGNMENT_IDcreateNotification(appUIManager, eventCriteria)a ssi g n m e n tIDETSI

39、 ETSI ES 202 196-5 V1.2.1 (2005-02) 15Test UI_12 Summary: IpUIManager, createNotification and changeNotification method, P_INVALID_CRITERIA Reference: ES 201 915-5 1, clause 8.1 Selection: createNotification and changeNotification methods supported - PICS item: 2 UIM3 AND UIM5 Test Sequence: 1. Meth

40、od call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call changeNotification() Parameters: assignmentID as returned in 1., eventCriteria containing an invalid criteria Check: P_INVALID_CRITERIA is returned. : IpAppUIManager

41、: IpUIManagerchangeNotification(assignmentID, eventCriteria_inv)P_INVALID_CRITERIAcreateNotification(appUIManager, eventCriteria)assignmentIDETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 16Test UI_13 Summary: IpUIManager, destroyNotification method, P_INVALID_ASSIGNMENT_ID Reference: ES 201 915-5 1, claus

42、e 8.1 Selection: createNotification method supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call destroyNotification() Parameters: assignmentID different from 1 Check:

43、P_INVALID_ASSIGNMENT_ID is returned. : IpAppUIManager : IpUIManagerdestroyNotification(assignmentID_inv)P_INVALID_ASSIGNMENT_IDcreateNotification(appUIManager, eventCriteria)assignmentIDETSI ETSI ES 202 196-5 V1.2.1 (2005-02) 175.2.1.2 IpUI interface Test UI_14 Summary: IpUI, sendInfoReq & sendInfoR

44、es methods, successful Reference: ES 201 915-5 1, clauses 8.3 and 8.4 Preamble: A User Interaction object, created either with the createUI or the createUICall method on the IpUIManager interface or reported in a reportEventNotification method, exists. The given sessionID is used in the following me

45、thods to identify this User Interaction object. Selection: sendInfoReq method supported - PICS item: 2 UI1 Test Sequence: 1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, repeatIndicator, responseRequested. Check: valid value of TpAss

46、ignmentID is returned 2. Triggered action: cause IUT to call sendInfoRes() method on the testers (Application) IpAppUI interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.) and response is transmitted, Return: no parameter : IpAppUIManager : IpAppU

47、I : IpUIManager : IpUIpreamble:createUI(appUI, userAddress)userInteractionSessionID1sendInfoReq(userInteractionSessionID1, info, language, variableInfo, repeatIndicator, responseRequested)assignmentID1send In foRes(userInteracti onSe ssion ID1 , assi gnmen tI D1, response)ETSI ETSI ES 202 196-5 V1.2

48、.1 (2005-02) 18Test UI_15 Summary: IpUI, sendInfoReq methods, P_INVALID_SESSION_ID Reference: ES 201 915-5 1, clause 8.3 Preamble: A User Interaction object, created either with the createUI or the createUICall method on the IpUIManager interface or reported in a reportEventNotification method exist

49、s. The given sessionID is used in the following methods to identify this User Interaction object. Selection: sendInfoReq method supported - PICS item: 2 UI1 Test Sequence: 1. Method call sendInfoReq() Parameters: invalid userInteractionSessionID, info, language, variableInfo, repeatIndicator, responseRequested. Check: P_INVALID_SESSION_ID is returned : IpAppUIManager : IpAppUI : IpUIManager : IpUIpreamble:createUI(appUI, userAddress)userInteractionSessionID1sendInfoReq(userInter