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

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

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

2、 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 been car

3、ried 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 Committ

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

5、ta 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“;

6、 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 Test Purpos

7、es (TSS Application Programming Interface (API); Part 6: Mobility 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 technology - Open S

8、ystems 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

9、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-6 1, ISO/IEC 9646-1 3, ISO/IEC 9646-2 4 and

10、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-1 3. Implementat

11、ion 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-6 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 to ISO/IEC 9646-

12、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 Information for

13、Testing LT Lower Tester M MobilityOSA Open Service Access TP Test Purpose TSS Test Suite Structure ULC User Location Camel ULE User Location Emergency US User Status 4 Test Suite Structure (TSS) Mobility (M): User Location: - IpUserLocation interface (UL) (01); - IpTrigerredUserLocation interface (T

14、UL) (02). User Location Camel (ULC) (03). User Location Emergency (ULE) (04). User Status (US) (05). ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 7 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, starting at 01, within each gro

15、up. 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: “M“ for Mobility part of Mobility SCF = group number: two character field representing the group r

16、eference according to TSS = sequential number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 201 915-6 1. 5.1.3 Test strategy As the base standard ES 201 915-6 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard a

17、nd 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 ETS 300 406 5). 5.2 TPs for the Mobility SCF All PI

18、CS 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 trigger the SCF to call methods in the application are dependant on the underlying net

19、work architecture and are out of the scope of this test specification. Those method calls are preceded by the words “Triggered action“. ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 8 5.2.1 User Location 5.2.1.1 IpUserLocation interface Test M_UL_01 Summary: all methods, successful Reference: ES 201 915-6

20、 1, clause 8.1 Selection: locationReportReq method supported - PICS item: 2 UL1 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 IpUserLocation interface through selecting that service

21、 and signing the required service agreement. Test Sequence: 1. Method call locationReportReq() Parameters: appLocation, users Check: valid value of TpSessionID is returned 2. Triggered action: cause IUT to call locationReportRes() method on the testers (Application) IpAppUserLocation interface. Para

22、meters: assignmentId, locations : IpAppUserLocation: IpUserLocation1. locationReportReq(appLocation, users)assignmentID2. locationReportRes(assignmentId, locations)ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 9 Test M_UL_02 Summary: locationReportReq, locationReportErr Reference: ES 201 915-6 1, clause 8

23、.1 Selection: locationReportReq method supported - PICS item: 2 UL1 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 IpUserLocation interface through selecting that service and signing

24、 the required service agreement. Test Sequence: 1. Method call locationReportReq() Parameters: appLocation, users with unknown or absent subscriber Check: valid value of TpSessionID is returned 2. Triggered action: cause IUT to call locationReportErr() method on the testers (Application) IpAppUserLo

25、cation interface. Parameters: assignmentId, cause indicating P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic : IpAppUserLocation: IpUserLocation1. locationReportReq(appLocation, unknown or absent users)assignmentID2. locationReportErr(assignmentId, P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCR

26、IBER, diagnostic)ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 10Test M_UL_03 Summary: all methods, successful Reference: ES 201 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registration of the IUT (User Location SCF) and the tester (application) t

27、o the framework. The tester must have obtained a reference to an instance of the IpUserLocation interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call extendedLocationReportReq() Parameters: appLocation, users, request Check: valid value of

28、 TpSessionID is returned 2. Triggered action: cause IUT to call extendedLocationReportRes() method on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, locations : IpAppUserLocation: IpUserLocation1. extendedLocationReportReq(appLocation, users, request)assignmentID2.

29、extendedLocationReportRes(assignmentId, locations)ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 11Test M_UL_04 Summary: extendedLocationReportReq, extendedLocationReportErr Reference: ES 201 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registration

30、 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 IpUserLocation interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call extendedLocationReportReq()

31、 Parameters: appLocation, users with unknown or absent subscriber, request Check: valid value of TpSessionID is returned 2. Triggered action: cause IUT to call extendedLocationReportErr() method on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, cause indicating P_M_

32、UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic : IpAppUserLocation: IpUserLocation1. extendedLocationReportReq(appLocation, unknown or absent users, request)assignmentID2. extendedLocationReportErr(assignmentId, P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic)ETSI ETSI ES 202 196-6

33、V1.2.1 (2005-02) 12Test M_UL_05 Summary: extendedLocationReportReq, P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED Reference: ES 201 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registration of the IUT (User Location SCF) and the tester (applicatio

34、n) to the framework. The tester must have obtained a reference to an instance of the IpUserLocation interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call extendedLocationReportReq() Parameters: appLocation, users, request with accuracy tha

35、t cannot be delivered Check: P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED is returned, or extendedLocationReportErr() with P_M_POSITION_METHOD_FAILURE value of TpMobilityError. : IpAppUserLocation: IpUserLocation1. extendedLocationReportReq(appLocation, users, inopportune request)P_REQUESTED_ACCURACY_CA

36、NNOT_BE_DELIVEREDrequest with accuracy that cannot be deliveredOR1. extendedLocationReportReq(appLocation, users, inopportune request)extendedLocationReportErr(assignmentId, P_M_POSITION_METHODE_FAILURE, diagnostic)ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 13Test M_UL_06 Summary: extendedLocationRepor

37、tReq, P_REQUESTED_RESPONSE_TIME_CANNOT_BE_DELIVERED Reference: ES 201 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framework. The tester must have obtained a refe

38、rence to an instance of the IpUserLocation interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call extendedLocationReportReq() Parameters: appLocation, users, request with response time that cannot be delivered Check: P_REQUESTED_RESPONSE_TI

39、ME_CANNOT_BE_DELIVERED is returned, or extendedLocationReportErr() with P_M_POSITION_METHOD_FAILURE value of TpMobilityError. : IpAppUserLocation: IpUserLocationrequest with response time that cannot be delivered1. extendedLocationReportReq(appLocation, users, inopportune request)P_REQUESTED_RESPONS

40、E_TIME_CANNOT_BE_DELIVEREDOR1. extendedLocationReportReq(appLocation, users, inopportune request)extendedLocationReportErr(assignmentId, P_M_POSITION_METHODE_FAILURE, diagnostic)ETSI ETSI ES 202 196-6 V1.2.1 (2005-02) 14Test M_UL_07 Summary: all methods, successful Reference: ES 201 915-6 1, clause

41、8.1 Selection: periodicLocationReportingStartReq method supported - PICS item: 2 UL3 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 IpUserLocation interface through selecting that se

42、rvice and signing the required service agreement. Test Sequence: 1. Method call periodicLocationReportingStartReq() Parameters: appLocation, users, request, reportingInterval Check: valid value of TpSessionID is returned 2. Triggered action: periodically cause IUT to call periodicLocationReport() me

43、thod on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, locations Check: These messages are sent with correct reporting Interval given in 1. 3. Method call periodicLocationReportingStop() Parameters: stopRequest Check: No further periodicLocationReport is sent. : IpA

44、ppUserLocation: IpUserLocation1. periodicLocationReportingStartReq(appLocation, users, request, reportingInterval)assignmentID2. periodicLocationReport(assignmentId, locations)3. periodicLocationReportingStop(stopRequest)This messages is sent periodically with the reportingInterval given in 1.ETSI E

45、TSI ES 202 196-6 V1.2.1 (2005-02) 15Test M_UL_08 Summary: all methods, unknown or absent subscriber Reference: ES 201 915-6 1, clause 8.1 Selection: periodocLocationReportingStartReq method supported - PICS item: 2 UL3 Preamble: Registration of the IUT (User Location SCF) and the tester (application

46、) to the framework. The tester must have obtained a reference to an instance of the IpUserLocation interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call periodicLocationReportingStartReq() Parameters: appLocation, users with unknown or abs

47、ent subscriber, request, reportingInterval Check: valid value of TpSessionID is returned 2. Triggered action: cause IUT to call periodicLocationReportErr () method on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, cause indicating P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_

48、SUBSCRIBER, diagnostic : IpAppUserLocat ion: IpUserLocation1. periodicLocationReportingStartReq(appLocation, unknown or absent users, request, reportingInterval)assignmentID2. periodicLocationReportErr(assignmentId, P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic)ETSI ETSI ES 202 196-6 V1.

49、2.1 (2005-02) 16Test M_UL_09 Summary: periodicLocationReportingStartReq, P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED Reference: ES 201 915-6 1, clause 8.1 Selection: periodocLocationReportingStartReq method supported - PICS item: 2 UL3 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 IpUserLocation interface through selecting that service and signing the required service agreement. Test S