1、 ETSI ES 202 388-6 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 6: Mobility SCF(Parlay 4)ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-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. Full details of the entire series can be found in part 1 6. To evaluate conformance of a particular implementation, it is necessary to hav
5、e 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 6: Mobility SCF (Parlay 4)“. 2 ETSI ES 202 363: “O
6、pen 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: General concepts“. 4 I
7、SO/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 specifications; Standardizati
8、on 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 and definitions giv
9、en in ES 202 915-6 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 ISO/IEC 9646-1 3. Lo
10、wer 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-6 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 proforma: Refer t
11、o 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 ICS Implementation Conformance Statement IUT Impleme
12、ntation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester M MobilityOSA Open Service Access SCF Service Capability Feature 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)
13、User Location - IpUserLocation interface (UL) (01) - IpTrigerredUserLocation interface (TUL) (02) User Location Camel (ULC) (03) User Location Emergency (ULE) (04) User Status (US) (05) 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. ETSI ETSI ES 202 388-6 V1.1.1 (20
14、05-03) 7 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 Identifier: _ = SCG name: “M“ for Mobil
15、ity part of Mobility SCF = group number: two character field representing the group reference according to TSS = sequential number: (01-99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-6 1. 5.1.3 Test strategy As the base standard ES 202 915-6 1 contains no explicit requirements for
16、 testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ES 202 363 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 implementat
17、ion is likely to be faced (see ETS 300 406 5). 5.2 TPs for the Mobility SCF All PICS items referred to in this clause are as specified in ES 202 363 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 the present document. Those method calls are preceded by the words “Triggered action“. 5.2.1 User Location 5.2.1.1 IpUserLocation interface Test M_UL_01 Summary: all method
19、s, successful Reference: ES 202 915-6 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 int
20、erface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call locationReportReq() Parameters: appLocation, users Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call locationReportRes() method on the testers (Applic
21、ation) IpAppUserLocation interface. Parameters: assignmentId, locations ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 8 : IpAppUserLocation: IpUserLocation1. locationReportReq(appLocation, users)assignmentID2. locationReportRes(assignmentId, locations)Test M_UL_02 Summary: locationReportReq, locationRepor
22、tErr Reference: ES 202 915-6 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 th
23、rough selecting that service and signing the required service agreement. Test Sequence: 1. Method call locationReportReq() Parameters: appLocation, users with unknown or absent subscriber Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call locationReportErr() meth
24、od on the testers (Application) IpAppUserLocation 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
25、 P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic)ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 9 Test M_UL_03 Summary: all methods, successful Reference: ES 202 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registration of the IUT (User L
26、ocation 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() Parameters: appLoc
27、ation, users, request Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call extendedLocationReportRes() method on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, locations : IpAppUserLocation: IpUserLocation1. extendedLocationReportR
28、eq(appLocation, users, request)assignmentID2. extendedLocationReportRes(assignmentId, locations)Test M_UL_04 Summary: extendedLocationReportReq, extendedLocationReportErr Reference: ES 202 915-6 1, clause 8.1 Selection: extendedLocationReportReq method supported - PICS item: 2 UL2 Preamble: Registra
29、tion 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 extendedLocationReportR
30、eq() Parameters: appLocation, users with unknown or absent subscriber, request Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call extendedLocationReportErr() method on the testers (Application) IpAppUserLocation interface. Parameters: assignmentId, cause indicati
31、ng P_M_UNKNOWN_SUBSCRIBER or P_ABSENT_SUBSCRIBER, diagnostic ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 10: IpAppUserLocation: IpUserLocation1. extendedLocationReportReq(appLocation, unknown or absent users, request)assignmentID2. extendedLocationReportErr(assignmentId, P_M_UNKNOWN_SUBSCRIBER or P_ABSE
32、NT_SUBSCRIBER, diagnostic)Test M_UL_05 Summary: extendedLocationReportReq, P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED Reference: ES 202 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 (app
33、lication) 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 accur
34、acy that 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_ACCU
35、RACY_CANNOT_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 388-6 V1.1.1 (2005-03) 11Test M_UL_06 Summary: extendedLocati
36、onReportReq, P_REQUESTED_RESPONSE_TIME_CANNOT_BE_DELIVERED Reference: ES 202 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
37、 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 response time that cannot be delivered Check: P_REQUESTED_RESP
38、ONSE_TIME_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_
39、RESPONSE_TIME_CANNOT_BE_DELIVEREDOR1. extendedLocationReportReq(appLocation, users, inopportune request)extendedLocationReportErr(assignmentId, P_M_POSITION_METHODE_FAILURE, diagnostic)ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 12Test M_UL_07 Summary: all methods, successful Reference: ES 202 915-6 1,
40、clause 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
41、that service and signing the required service agreement. Test Sequence: 1. Method call periodicLocationReportingStartReq() Parameters: appLocation, users, request, reportingInterval Check: valid value of TpAssignmentID is returned 2. Triggered action: periodically cause IUT to call periodicLocationR
42、eport() method 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 s
43、ent. : IpAppUserLocation: IpUserLocation1. periodicLocationReportingStartReq(appLocation, users, request, reportingInterval)assignmentID2. periodicLocationReport(assignmentId, locations)3. periodicLocationReportingStop(stopRequest)This messages is sent periodically with the reportingInterval given i
44、n 1.ETSI ETSI ES 202 388-6 V1.1.1 (2005-03) 13Test M_UL_08 Summary: all methods, unknown or absent subscriber Reference: ES 202 915-6 1, clause 8.1 Selection: periodicLocationReportingStartReq method supported - PICS item: 2 UL3 Preamble: Registration of the IUT (User Location SCF) and the tester (a
45、pplication) 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 unkn
46、own or absent subscriber, request, reportingInterval Check: valid value of TpAssignmentID 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
47、 or P_ABSENT_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)Test M_UL_09
48、Summary: periodicLocationReportingStartReq, P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED Reference: ES 202 915-6 1, clause 8.1 Selection: periodicLocationReportingStartReq method supported - PICS item: 2 UL3 Preamble: Registration of the IUT (User Location SCF) and the tester (application) to the framew
49、ork. 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, request with accuracy that cannot be delivered, reportingInterval Check: P_REQUESTED_ACCURACY_CANNOT_BE_DELIVERED is returned, or periodicLocationReportErr() with P_M_POSITION_METHOD_FAILURE value of TpMobilityError. ETSI ETSI ES 20
