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

1、 ETSI ES 202 388-9 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 9: Generic messaging SCF(Parlay 4)ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-09-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 9 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 necessa

5、ry 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 9: Generic Messaging SCF (Parlay 4)“. 2 E

6、TSI 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 1: Gene

7、ral 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 specificati

8、ons; 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 terms a

9、nd definitions given in ES 202 915-9 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): Refer to IS

10、O/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-9 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 3. IXIT

11、 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 GM Generic MessagingICS Implementa

12、tion Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access SCF Service Capability Feature TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Generic Messaging 5 Test Purposes (TP) 5.1 Introduct

13、ion 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 naming convention scheme I

14、dentifier: _ = SCG name: “GM“ for Generic Messaging part of Generic Messaging SCF GM_APP for Generic Messaging part of Generic Messaging Application = sequential number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-9 1. 5.1.3 Test strategy As the base standard ES 202 915-

15、9 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the ICS specification ES 202 363 2. ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 7 The TPs are only based on conformance requirements related to the externally observable behaviou

16、r 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 Generic Messaging SCF All ICS items referred to in this clause are as specified in ES 202 363 2 unless indicated otherwise by another numbered reference. A

17、ll 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 words “Triggered acti

18、on“. 5.2.1 Generic Messaging, SCF side Test GM_01 Summary: IpMessagingManager: all methods, successful. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance

19、 of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call enableMessagingNotification() Parameters: appInterface, eventCriteria Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call

20、messagingEventNotify() method on the testers (Application) IpAppMessagingManager interface. Parameters: messagingManager, eventInfo, assignmentID 3. Method call disableMessagingNotification() Parameters: assignmentId given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpM

21、essagingManager1. enableMessagingNotification(appInterface, eventCriteria)assignmentID( )2. messagingEventNotify(messagingManager, eventInfo, assignmentID)3. disableMessagingNotification(assignmentID)ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 8 Test GM_02 Summary: enableMessagingNotification, P_INVALID

22、_CRITERIA. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required

23、service agreement. Test Sequence: 1. Method call enableMessagingNotification() Parameters: appInterface, invalid eventCriteria Check: P_INVALID_CRITERIA is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. enableMessagingNotification(appInterface, invalid eventCriteria)P_INVALID_CRIT

24、ERIAETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 9 Test GM_03 Summary: disableMessagingNotification, P_INVALID_ASSIGNMENT_ID. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a referen

25、ce to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call enableMessagingNotification() Parameters: appInterface, eventCriteria Check: valid value of TpAssignmentID is returned 2. Triggered action: c

26、ause IUT to call messagingEventNotify() method on the testers (Application) IpAppMessagingManager interface. Parameters: messagingManager, eventInfo, assignmentID 3. Method call disableMessagingNotification() Parameters: invalid assignmentId Check: P_INVALID_ASSIGNMENT_ID is returned IpAppLogic : Ip

27、AppMessagingManager: IpMessagingManager1. enableMessagingNotification(appInterface, eventCriteria)assignmentID( )2. messagingEventNotify(messagingManager, eventInfo, assignmentID)3. disableMessagingNotification(invalid assignmentID)P_INVALID_ASSIGNMENT_ID( )ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 10

28、Test GM_04 Summary: IpMessagingManager: all methods, successful. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface th

29、rough selecting that service and signing the required service agreement. Test Sequence: 1. Method call openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call close() on IpMailbox Parameters: mailboxSessionID

30、given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID2. close(mailboxSessionID)ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 11Test GM_05 Summary: openMailbox, P_GMS_INVALID_MAILBOX. Refere

31、nce: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement

32、. Test Sequence: 1. Method call openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call openMailbox() Parameters: mailboxID given in 1., authenticationInfo Check: P_GMS_INVALID_MAILBOX is returned 3. Method ca

33、ll close() on IpMailbox Parameters: mailboxSessionID given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID3. close(mailboxSessionID)2. openMailbox(mailboxID as in 1., authenticationIn

34、fo)P_GMS_INVALID_MAILBOXETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 12Test GM_06 Summary: openMailbox, P_GMS_INVALID_AUTHENTIFICATION_INFORMATION. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must h

35、ave obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call openMailbox() Parameters: mailboxID, invalid authenticationInfo Check: P_GMS_INVALID_AUTHENTIFICATION_INFORMATION is re

36、turned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. openMailbox(mailboxID, invalid authenticationInfo)P_GMS_INVALID_AUTHENTIFICATION_INFORMATIONTest GM_07 Summary: close, P_INVALID_SESSION_ID. Reference: ES 202 915-9 1, clause 8.3. Preamble: Registration of the IUT (User Location SCF) an

37、d the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call openMailbox() on IpMessagingManager Parameters: mailboxID

38、, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call close() on IpMailbox Parameters: invalid mailboxSessionID Check: P_INVALID_SESSION_ID is returned ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 13IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. op

39、enMailbox(mailboxID, authenticationInfo)mailboxSessionID2. close(invalid mailboxSessionID)P_INVALID_SESSION_IDTest GM_08 Summary: IpMailbox all methods, successful. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framew

40、ork. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value

41、of TpMailboxIdentifier is returned 2. Method call lock() on IpMailbox Parameters: mailboxSessionID given in 1. Check: no exception is returned 3. Method call unlock() Parameters: mailboxSessionID given in 1. Check: no exception is returned 4. Method call close() Parameters: mailboxSessionID given in

42、 1. Check: no exception is returned ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 14IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID4. close(mailboxSessionID)2. lock(mailboxSessionID)3. unlock(mailboxSessionID)Test GM_09 Summary

43、: lock, P_GMS_LOCKING_LOCKED_MAILBOX. Reference: ES 202 915-9 1, clause 8.3. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that servic

44、e and signing the required service agreement. Test Sequence: 1. Method call openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call lock() on IpMailbox Parameters: mailboxSessionID given in 1. Check: no except

45、ion is returned 3. Method call lock() Parameters: mailboxSessionID given in 1. Check: P_GMS_LOCKING_LOCKED_MAILBOX is returned 4. Method call close() Parameters: mailboxSessionID given in 1. Check: no exception is returned ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 15IpAppLogic : IpAppMessagingManager:

46、 IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID4. close(mailboxSessionID)3. lock(invalid mailboxSessionID)P_GMS_LOCKING_LOCKED_MAILBOX2. lock(mailboxSessionID)Test GM_10 Summary: unlock, P_GMS_UNLOCKING_UNLOCKED_MAILBOX. Reference: ES 202 915-9 1, clause 8

47、.3. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpMessagingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method ca

48、ll openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call unlock() on IpMailbox Parameters: mailboxSessionID given in 1. Check: P_GMS_UNLOCKING_UNLOCKED_MAILBOX is returned 3. Method call close() Parameters:

49、mailboxSessionID given in 1. Check: no exception is returned ETSI ETSI ES 202 388-9 V1.1.1 (2005-03) 16IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID3. close(mailboxSessionID)2. unlock(mailboxSessionID)P_GMS_UNLOCKING_UNLOCKED_MAILBOXTest GM_11 Summary: IpMailbox, all methods, successful. Reference: ES 202 915-9 1, clause 8.1. Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester m