ETSI ES 202 196-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

《ETSI ES 202 196-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》由会员分享，可在线阅读，更多相关《ETSI ES 202 196-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（54页珍藏版）》请在麦多课文档分享上搜索。

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

2、ential, 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, ha

3、s 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 Technic

4、al Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 9 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 manage

6、ment 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 T

7、est Purposes (TSS Application Programming Interface (API); Part 9: Generic Messaging 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

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

9、 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-9 1, ISO/IEC 9646-1 3, IS

10、O/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 96

11、46-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-9 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): Ref

12、er 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 Implementation Conformance Statement IUT Implementation Under Test IXI

13、T Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Generic Messaging. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered

14、, 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: “GM“ for Generic Messaging part of Generic Messaging SCF GM_APP f

15、or 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 201 915-9 1. 5.1.3 Test strategy As the base standard ES 201 915-9 1 contains no explicit requirements for testing, the TPs were generated as a result of a

16、n analysis of the base standard and the ICS 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 ETS 300 406 5). ETS

17、I ETSI ES 202 196-9 V1.2.1 (2005-02) 7 5.2 TPs for the Generic Messaging SCF All ICS 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. The procedures to trig

18、ger 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 Generic Messaging, SCF side Test GM_01 Summary: IpMessagingManager: all meth

19、ods, successful Reference: ES 201 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 requi

20、red 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 messagingEventNotify() method on the testers (Application) IpAppMessagingManager interfac

21、e. Parameters: messagingManager, eventInfo, assignmentID 3. Method call disableMessagingNotification() Parameters: assignmentId given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. enableMessagingNotification(appInterface, eventCriteria)assignmentID( )

22、2. messagingEventNotify(messagingManager, eventInfo, assignmentID)3. disableMessagingNotification(assignmentID)ETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 8 Test GM_02 Summary: enableMessagingNotification, P_INVALID_CRITERIA Reference: ES 201 915-9 1, clause 8.1 Preamble: Registration of the IUT (User L

23、ocation 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 call enableMessagingNotification() Parameters:

24、appInterface, invalid eventCriteria Check: P_INVALID_CRITERIA is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. enableMessagingNotification(appInterface, invalid eventCriteria)P_INVALID_CRITERIAETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 9 Test GM_03 Summary: disableMessagingNotificat

25、ion, P_INVALID_ASSIGNMENT_ID Reference: ES 201 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 sign

26、ing 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 messagingEventNotify() method on the testers (Application) IpAppMessagingMan

27、ager interface. Parameters: messagingManager, eventInfo, assignmentID 3. Method call disableMessagingNotification() Parameters: invalid assignmentId Check: P_INVALID_ASSIGNMENT_ID is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. enableMessagingNotification(appInterface, eventCrit

28、eria)assignmentID( )2. messagingEventNotify(messagingManager, eventInfo, assignmentID)3. disableMessagingNotification(invalid assignmentID)P_INVALID_ASSIGNMENT_ID( )ETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 10Test GM_04 Summary: IpMessagingManager: all methods, successful Reference: ES 201 915-9 1, cl

29、ause 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. Test Sequence: 1. Meth

30、od call openMailbox() on IpMessagingManager Parameters: mailboxID, authenticationInfo Check: valid value of TpMailboxIdentifier is returned 2. Method call close() on IpMailbox Parameters: mailboxSessionID given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpMessagingMana

31、ger: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID2. close(mailboxSessionID)ETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 11Test GM_05 Summary: openMailbox, P_GMS_INVALID_MAILBOX Reference: ES 201 915-9 1, clause 8.1 Preamble: Registration of the IUT (User Location SCF) and the te

32、ster (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, authen

33、ticationInfo 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 call close() on IpMailbox Parameters: mailboxSessionID given in 1. Check: no exception is returned

34、IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID3. close(mailboxSessionID)2. openMailbox(mailboxID as in 1., authenticationInfo)P_GMS_INVALID_MAILBOXETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 12Test GM_06 Summary: openMailbox

35、, P_GMS_INVALID_AUTHENTIFICATION_INFORMATION Reference: ES 201 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

36、service and signing the required service agreement. Test Sequence: 1. Method call openMailbox() Parameters: mailboxID, invalid authenticationInfo Check: P_GMS_INVALID_AUTHENTIFICATION_INFORMATION is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager1. openMailbox(mailboxID, invalid auth

37、enticationInfo)P_GMS_INVALID_AUTHENTIFICATION_INFORMATIONETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 13Test GM_07 Summary: close, P_INVALID_SESSION_ID Reference: ES 201 915-9 1, clause 8.3 Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester mus

38、t 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 of TpMailboxIdentif

39、ier is returned 2. Method call close() on IpMailbox Parameters: invalid mailboxSessionID Check: P_INVALID_SESSION_ID is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID2. close(invalid mailboxSessionID)P_INVALID_S

40、ESSION_IDETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 14Test GM_08 Summary: IpMailbox all methods, successful Reference: ES 201 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

41、 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 of TpMailboxIdentifier is returned 2. Method call lock() on I

42、pMailbox 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 1. Check: no exception is returned IpAppLogic : IpAppMessagi

43、ngManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID4. close(mailboxSessionID)2. lock(mailboxSessionID)3. unlock(mailboxSessionID)ETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 15Test GM_09 Summary: lock, P_GMS_LOCKING_LOCKED_MAILBOX Reference: ES 201 915-9

44、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 service and signing the required service agreement. Test Sequence: 1.

45、 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 exception is returned 3. Method call lock() Parameters: mailboxSessio

46、nID 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 196-9 V1.2.1 (2005-02) 16IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authent

47、icationInfo)mailboxSessionID4. close(mailboxSessionID)3. lock(invalid mailboxSessionID)P_GMS_LOCKING_LOCKED_MAILBOX2. lock(mailboxSessionID)ETSI ETSI ES 202 196-9 V1.2.1 (2005-02) 17Test GM_10 Summary: unlock, P_GMS_UNLOCKING_UNLOCKED_MAILBOX Reference: ES 201 915-9 1, clause 8.3 Preamble: Registrat

48、ion 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 call openMailbox() on IpM

49、essagingManager 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: mailboxSessionID given in 1. Check: no exception is returned IpAppLogic : IpAppMessagingManager: IpMessagingManager: IpMailbox1. openMailbox(mailboxID, authenticationInfo)mailboxSessionID3. close(mailboxSessionID)2. unlock(mailboxSessionID)P_GMS_UNLOC