Open Service Access (OSA); Application Programming ... · Final draft ETSI ES 202 388-5 V1.1.1...

Final draft ETSI ES 202 388-5 V1.1.1 (2005-01)

ETSI Standard

Open Service Access (OSA);Application Programming Interface (API);

Test Suite Structure and Test Purposes (TSS&TP);Part 5: User interaction SCF;

(Parlay 4)

ETSI

Final draft ETSI ES 202 388-5 V1.1.1 (2005-01) 2

Reference DES/TISPAN-06004-05-OSA

Keywords API, OSA, TSS&TP

ETSI

650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88

Important notice

Individual copies of the present document can be downloaded from: http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at

http://portal.etsi.org/tb/status/status.asp

If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification

No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2005.

All rights reserved.

DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

http://www.etsi.org/

http://portal.etsi.org/tb/status/status.asp

http://portal.etsi.org/chaircor/ETSI_support.asp

ETSI


Contents

Intellectual Property Rights ................................................................................................................................4

Foreword.............................................................................................................................................................4

1 Scope ........................................................................................................................................................5

2 References ................................................................................................................................................5

3 Definitions and abbreviations...................................................................................................................5 3.1 Definitions..........................................................................................................................................................5 3.2 Abbreviations .....................................................................................................................................................6

4 Test Suite Structure (TSS)........................................................................................................................6

5 Test Purposes (TP) ...................................................................................................................................6 5.1 Introduction ........................................................................................................................................................6 5.1.1 TP naming convention ..................................................................................................................................6 5.1.2 Source of TP definition.................................................................................................................................6 5.1.3 Test strategy..................................................................................................................................................7 5.2 TPs for the User Interaction SCF .......................................................................................................................7 5.2.1 User Interaction, SCF side ............................................................................................................................7 5.2.1.1 IpUIManager interface ............................................................................................................................7 5.2.1.2 IpUI interface ........................................................................................................................................17 5.2.1.3 IpUICall interface .................................................................................................................................30 5.2.2 User Interaction, application side ...............................................................................................................54 5.2.2.1 IpAppUIManager interface ...................................................................................................................55 5.2.2.2 IpAppUI interface .................................................................................................................................58 5.2.2.3 IpAppUICall interface...........................................................................................................................62

History ..............................................................................................................................................................73

ETSI


Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, 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 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 Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards Membership Approval Procedure.

The present document is part 5 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 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&TP) specification.

http://webapp.etsi.org/IPR/home.asp

ETSI


1 Scope The present document provides the Test Suite Structure and Test Purposes (TSS&TP) specification for the User Interaction SCF of the Application Programming Interface (API) for Open Service Access (OSA) defined in ES 202 915-5 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-2 [4] and ETS 300 406 [5].

2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

• References are either specific (identified by date of publication and/or edition number or version number) or non-specific.

• For a specific reference, subsequent revisions do not apply.

• For a non-specific reference, the latest version applies.

Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.

[1] ETSI ES 202 915-5: "Open Service Access (OSA); Application Programming Interface (API); Part 5: User Interaction SCF (Parlay 4)".

[2] ETSI 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: 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 Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology".

[6] ETSI ES 202 388-1: "Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS&TP); Part 1: Overview; (Parlay 4)".

3 Definitions and abbreviations

3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 915-5 [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].

Lower Tester (LT): Refer to ISO/IEC 9646-1 [3].

Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 [3].

http://docbox.etsi.org/Reference

ETSI


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 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 ICS Implementation 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) • 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 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: <suite_id>_<nnn> <suite_id> = SCG name: "UI" for User Interaction part of User Interaction SCF 'UI_APP' for User Interaction part of User interaction Application <nn> = sequential number: (01-99)

5.1.2 Source of TP definition

The TPs are based on ES 202 915-5 [1].

ETSI


5.1.3 Test strategy

As the base standard ES 202 915-5 [1] contains no explicit requirements for 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 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 363 [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 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 Interaction, SCF side

Pre-requisite:

• Registration 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

Summary: IpUIManager, createUI method, successful

Reference: ES 202 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 : I pUIManage r

cre ateUI(app UI, userAddress)

userInteraction

ETSI


Test UI_02

Summary: IpUIManager, createUI method, P_INVALID_NETWORK_STATE



Condition: the underlying protocol cannot support the method call.

Test Sequence:

1. Method call createUI() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned

: IpAppUIManager : IpUIManage r

cre ate UI(app UI, u serAddress)

P_INVALID_NETWORK_STATE

Test UI_03

Summary: IpUIManager, createUI method, P_INVALID_INTERFACE_TYPE



Test Sequence:

1. Method call createUI() Parameters: appUI including an invalid reference type, userAddress Check: P_INVALID_ INTERFACE_TYPE is returned


cre ate UI(app UI, u serAddress)

P_INVALID_INTERFACE_TYPE

ETSI


Test UI_04

Summary: IpUIManager, createUICall method, successful


Selection: createUICall method supported - PICS item: [2] UIM2

Test Sequence:

1. Method call createUICall() Parameters: appUI, uiTargetObject Check: valid value of TpUIIdentifier is returned

: IpAppUIManager : IpUIManager

createUICall(appUI, uiTargetObject)

userInteraction

Test UI_05

Summary: IpUIManager, createUICall method, P_INVALID_NETWORK_STATE




Test Sequence:

1. Method call createUICall() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned




ETSI


Test UI_06

Summary: IpUIManager, createUICall method, P_INVALID_INTERFACE_TYPE



Test Sequence:

1. Method call createUICall() Parameters: appUI including an invalid reference type, userAddress Check: P_INVALID_INTERFACE_TYPE is returned




Test UI_07

Summary: IpUIManager, all createNotification and destroyNotification methods, successful


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 returned in 1.. Check: no exception is returned.

ETSI



createNotification(appUIManager, eventCriteria1)

assignmentID

destroyNoti ficati on(assignment ID)

Test UI_08

Summary: IpUIManager, receipt of reportEventNotification method, successful

Reference: ES 202 915-5 [1], clauses 8.1 and 8.2


Test Sequence:


2. Triggered action: cause IUT to call reportEventNotification() method on the tester's (Application) IpAppUIManager interface. Check: valid value of userInteraction, eventNotificationInfo and assignmentID given in 1. is transmitted, Return: valid value of IpAppUIRef

ETSI



createNotification(appUIManager, eventCriter...

assignmentID

reportEventNotification(userInteraction, eventNotificationInfo, assignmentID)

appUI

Test UI_09

Summary: IpUIManager, createNotification method, P_INVALID_INTERFACE_TYPE



Test Sequence:

1. Method call createNotification() Parameters: appUIManager including an invalid reference type, eventCriteria, Check: P_INVALID_INTERFACE_TYPE is returned


createNotification(appUIManager_inv, eventCriteria)


ETSI


Test UI_10

Summary: IpUIManager, createNotification method, P_INVALID_CRITERIA



Test Sequence:

1. Method call createNotification() Parameters: appUIManager, eventCriteria containing an invalid criteria. Check: P_INVALID_CRITERIA is returned.


createNotification(appUIManager, eventCriteria_inv)

P_INVALID_CRITERIA

Test UI_11

Summary: IpUIManager, createNotification and changeNotification methods, P_INVALID_ASSIGNMENT_ID


Selection: createNotification and changeNotification methods supported - PICS item: [2] UIM3 AND UIM5

Test Sequence:


2. Method call changeNotification() Parameters: assignmentID different from returned in 1., eventCriteria. Check: P_INVALID_ASSIGNMENT_ID is returned.

ETSI



cha ngeNot ificat ion(assig nmentID_ inv, eve ntCrite ria)

P_INVALID_ASSIGNMENT_ID

createNo tification(appUIManager, eventCriteria)

assignmentID

Test UI_12

Summary: IpUIManager, createNotification and changeNotification method, P_INVALID_CRITERIA


Selection: createNotification and changeNotification methods supported - PICS item: [2] UIM3 AND UIM5

Test Sequence:


2. Method call changeNotification() Parameters: assignmentID as returned in 1., eventCriteria containing an invalid criteria.. Check: P_INVALID_CRITERIA is returned.


cha ngeNot ificat ion(assig nmentID, eventCriteria _in v)

P_INVALID_CRITERIA

create Notif ication(appUIMan ager, eventCriteria)

assignmentID

ETSI


Test UI_13

Summary: IpUIManager, destroyNotification method, P_INVALID_ASSIGNMENT_ID


Selection: createNotification method supported - PICS item: [2] UIM3

Test Sequence:


2. Method call destroyNotification() Parameters: assignmentID different from 1.. Check: P_INVALID_ASSIGNMENT_ID is returned.


destroyNotification(assignmentID_inv)


createNotification(appUIManager, eventCriteria)

assignmentID

ETSI


Test UI_52

Summary: IpUIManager, all methods, successful


Precondition: enableNotifications supported

Preamble: Registration 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.

Test Sequence:

1. Method call enableNotifications() Parameters: appUIManager Check: valid value of TpAssignmentID is returned

2. Triggered action: cause IUT to call reportEventNotification() method on the tester's (Application) IpAppAccountManager interface. Parameters: userInteraction, eventNotificationInfo, assignmentID

3. Method call disableNotifications() Parameters: none Check: no exception is returned


disableNotifications()

enableNo ti fica ti ons(a ppUIManager)

assignmentID


ETSI


5.2.1.2 IpUI interface

Test UI_14

Summary: IpUI, sendInfoReq & sendInfoRes methods, successful


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 methods 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 TpAssignmentID is returned

2. Triggered action: cause IUT to call sendInfoRes() method on the tester's (Application) IpAppUI interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.) and response is transmitted, Return: no parameter

: IpAppUIManager : IpAppUI : IpUIManager : IpUI

preamble:

createUI(appUI, userAddress)

userInteractionSessionID1

sendIn foReq(use rInteract ionSessi onID1, in fo, la ngua ge, variab leInfo, rep eatIn dicator, respo nse Reque sted)

assignmentID1

send In foRes(userInteracti onSe ssion ID1 , assi gnmen tID1, response)

ETSI


Test UI_15

Summary: IpUI, sendInfoReq methods, P_INVALID_SESSION_ID


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 methods to identify this User Interaction object.


Test Sequence:

1. Method call sendInfoReq() Parameters: invalid userInteractionSessionID, info, language, variableInfo, repeatIndicator, responseRequested. Check: P_INVALID_SESSION_ID is returned


preamble:



sendInfoReq(userInteractionSessionID_invalid, info, language, variableInfo, repeatIndicator, responseRequested)

P_INVALID_SESSION_ID

ETSI


Test UI_16

Summary: IpUI, sendInfoReq methods, P_INVALID_NETWORK_STATE





Test Sequence:

1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, repeatIndicator, responseRequested. Check: P_INVALID_NETWORK_STATE is returned


preamble:



sendInfoReq(userInteractionSessionID1, info, language, variableInfo, repeatIndicator, responseRequested)


ETSI


Test UI_17

Summary: IpUI, sendInfoReq methods, P_ILLEGAL_ID




Test Sequence:

1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, illegal info, language, variableInfo, repeatIndicator, responseRequested. Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned

: I pUIMana ger : IpAppUIManager : IpAppUI : IpUI

preamble:



sendInfoReq(userInteractionSessionID1, info_il legal, language, variableInfo, repeatIndicator, responseRequested)

P_ILLEGAL_ID or P_ID_NOT_FOUND

ETSI


Test UI_18

Summary: IpUI, sendInfoAndCollectReq & sendInfoAndCollectRes methods, successful



Selection: sendInfoAndCollectReq method supported - PICS item: [2] UI2

Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, criteria, responseRequested. Check: valid value of TpAssignmentID is returned

2. Triggered action: cause IUT to call sendInfoAndCollectRes() method on the tester's (Application) IpAppUI interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.), response and collectedInfo is transmitted, Return: no parameter

: IpAppUIManager : IpAppUI : IpUIManag er : IpUI

preamble:



sendInfoAnd Col lectReq(use rInteractio nSessionID1, info, lang uage, vari abl eInfo , criteria, responseRequested)

assignmentID1

sendInfoAndCol lectRes(u serInte racti on Sessio nID1, assi gnmen tID1, colle ctedInfo )

ETSI


Test UI_19

Summary: IpUI, sendInfoAndCollectReq methods, P_INVALID_SESSION_ID




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: invalid userInteractionSessionID, info, language, variableInfo, criteria, responseRequested. Check: P_INVALID_SESSION_ID is returned


preamble:



sendInfoAndCollectReq(userInteractionSessionID_invalid, info, language, variableInfo, criteria, responseRequested)


ETSI


Test UI_20

Summary: IpUI, sendInfoAndCollectReq methods, P_INVALID_NETWORK_STATE





Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, criteria, responseRequested. Check: P_INVALID_NETWORK_STATE is returned


preamble:



sendInfoAndCollectReq(userInteractionSessionID, info, language, variableInfo, criteria, responseRequested)


ETSI


Test UI_21

Summary: IpUI, sendInfoAndCollectReq methods, P_ILLEGAL_ID




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, illegal info, language, variableInfo, criteria, responseRequested Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned

: IpAppUI : IpAppUIManager : IpUIManager : I pUI

preamble:



sendInfoAndCollectReq(userInteractionSessionID, info_illeg al, language, variableInfo, criteria, responseRequested)


ETSI


Test UI_22

Summary: IpUI, sendInfoAndCollectReq methods, P_ILLEGAL_RANGE




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, criteria with collection length out of range, responseRequested. Check: P_ILLEGAL_RANGE is returned

: IpAppUIMan ager : IpAppUI : IpUIManager : IpUI

preamble:

crea te UI(appUI, userAdd re ss)

u serInte ractionSessionID1

sendInfoAndCollectReq(userInteractionSessionID, info, language, variableInfo, criteria_lengthOutOfRange, responseRequested)

P_IL LEGAL_ RANGE

ETSI


Test UI_23

Summary: IpUI, sendInfoAndCollectReq methods, P_INVALID_COLLECTION_CRITERIA




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, invalid collection criteria, responseRequested. Check: P_INVALID_COLLECTION_CRITERIA is returned


preamble:



sendInfoAndCollectReq(userInteracti onSessionID, info, language, variableInfo, criteria_collectionInvalid, resp onseRequested)

P_INVALID_COLLECTION_CRITERIA

ETSI


Test UI_24

Summary: IpUI, release method, successful


Preamble: A User Interaction object, created either with the createUI or the createUICall method on the IpUIManager interface, exists. The given sessionID is used in the following methods to identify this User Interaction object.

Test Sequence:

1. Method call release() Parameters: userInteractionSessionID given in preamble. Check: no exception is returned.

: IpAppUIManager : IpApp UI : IpUIManager : IpUI

preamble:

cre ate UI(ap pUI , userA ddress)

u serIntera ct io nSessi onID1

release(userInteractionSessionID1)

ETSI


Test UI_25

Summary: IpUI, release method, P_INVALID_SESSION_ID



Test Sequence:

1. Method call release() Parameters: invalid userInteractionSessionID, Check: P_INVALID_SESSION_ID is returned.

: IpAppUIManager : IpApp UI : IpUIManager : IpUI

preamble:

cre ate UI(ap pUI , userAddress)


release(userInteractionSessionID_invalid)


ETSI


Test UI_53

Summary: IpUI, all method, successful



Test Sequence:

1. Method call getOriginatingAddress () Parameters: userInteractionSessionID, Check: valid value of TpString is returned.

2. Method call setOriginatingAddress () Parameters: userInteractionSessionID, origin with different value of returned in 1., Check: valid value of TpAssignmentID is returned.

3. Method call getOriginatingAddress () Parameters: userInteractionSessionID, Check: valid value of TpString is returned with value given in 2.

: IpAppUI : IpUI

getOriginatingAddress(userInteractionSessionID)

TpString

setOriginatingAddress(userInteractionSessionID, origin)

assignmentID

getOriginatingAddress(userInteractionSessionID)

TpString

ETSI


5.2.1.3 IpUICall interface

Test UI_26

Summary: IpUICall, sendInfoReq & sendInfoRes methods, successful


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 methods to identify this User Interaction object.

Selection: sendInfoReq method supported - PICS item: [2] UIC1

Test Sequence:


2. Triggered action: cause IUT to call sendInfoRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.) and response is transmitted, Return: no parameter

: IpAppUIManager : IpAppUICall : IpUIManager : IpUICall

preamble:createUICall(appUI, uiTargetObject)


sendInfoReq(userInteractionSessionID1 , info, language, variableInfo, repeatIndicator, responseRequested)

assignmentID1

sendInfo Res(userIn teracti onSessio nID1, assignm en tID1, respon se)

ETSI


Test UI_27

Summary: IpUICall, sendInfoAndCollectReq & sendInfoAndCollectRes methods, successful



Selection: sendInfoAndCollectReq method supported - PICS item: [2] UIC2

Test Sequence:


2. Triggered action: cause IUT to call sendInfoAndCollectRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.), response and collectedInfo is transmitted, Return: no parameter

: IpAppUIManager : IpAppUICall : IpUIMa nager : IpUICall

preamble:createUICall(appUI, u iTa rge tObj ect)


sendInfoAndCollectReq(userInteractionSessionID1, info, language, variableInfo, criteria, responseRequested)

assignmentID1

sendInfoAndCollectRes(userInteractionSessionID1, assignmentID1, response, collectedInfo)

ETSI


Test UI_28

Summary: IpUICall, all methods, successful



Selection: recordMessageReq and deleteMessageReq methods supported - PICS item: [2] UIC4 AND UIC5

Test Sequence:

1. Method call recordMessageReq() Parameters: userInteractionSessionID given in preamble, info, criteria. Check: valid value of TpAssignmentID is returned

2. Triggered action: cause IUT to call recordMessageRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.), response and messageID is transmitted, Return: no parameter

3. Method call deleteMessageReq() Parameters: userInteractionSessionID given in preamble, messageID returned in 2. Check: valid value of TpAssignmentID is returned

4. Triggered action: cause IUT to call deleteMessageRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble), response and assignmentID (returned in 3.) is transmitted, Return: no parameter

ETSI


: IpAppUIManager : IpAppUICall : IpUIManager : IpUICal l

preamble:


u serInteract ionSessi onID1

recordMessageReq(userInteractionSessionID1, info, criteria)

assignme ntID1

recordMessageRes(userInteractionSessionID1, assig nment ID1, response, m essageID1)

deleteMessageReq(userInteractionSessionID1, messageID1)

assignme ntID2

deleteMessageRes(userInteractionSessionID1, response, assignment ID2)

ETSI


Test UI_29

Summary: IpUICall, abortActionReq and abortActionRes methods, successful



Selection: sendInfoReq and abortActionReq methods supported - PICS item: [2] UIC1 AND UIC6

Test Sequence:


2. Method call abortActionReq() Parameters: userInteractionSessionID given in preamble, assignmentID returned in 1. Check: no exception is returned.

3. Triggered action: cause IUT to call abortActionRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble) and assignmentID (returned in 1.) is transmitted, Return: no parameter

: IpAppUIManager : IpAppUICall : IpUIManage r : IpUICall



sendIn foReq(use rInteract io nSessi onID1, i nfo, l ang uage , variableInfo , repeat Indicator, resp onse Requested)

assignmentID1

a bortActionReq(use rInteract io nSessi onID1, a ssign ment ID1)

abortActionRes(userInteractionSessionID1, assignmentID1)

ETSI


Test UI_30

Summary: IpUICall, abortActionReq and abortActionRes methods, successful



Selection: sendInfoAndCollectReq and abortActionReq methods supported - PICS item: [2] UIC2 AND UIC6

Test Sequence:


2. Method call abortActionReq() Parameters: userInteractionSessionID given in preamble, assignmentID returned in 1. Check: no exception is returned.

3. Triggered action: cause IUT to call abortActionRes() method on the tester's (Application) IpAppUICall interface. Check: valid value of userInteractionSessionID (given in preamble) and assignmentID (returned in 1.) is transmitted, Return: no parameter


preamble:crea teUICa ll(appUI, uiTargetObject)


sendInfoAn dColle ctReq(userInteracti onSe ssion ID, in fo, la ngua ge, variab leInfo, criteria, re spo nse Reque sted)

assignmentID1

abortActionReq(userInte raction SessionID1, assign mentID1 )

abortActio nRes(u serInte ra ction SessionID1, a ssign mentID1 )

ETSI


Test UI_31

Summary: IpUICall, release method, successful


Preamble: A User Interaction object, created either with the createUI or the createCallUIcreateUICall method on the IpUIManager interface, exists. The given sessionID is used in the following methods to identify this User Interaction object.

Test Sequence:

1. Method call release() Parameters: userInteractionSessionID given in preamble. Check: no exception is returned.

: IpAp pUIMa nage r : IpAppUICall : IpUIManager : IpUICall

prea mble :createUICall(app UI, uiTa rgetObject)

use rIntera ction SessionID1

release(userInteractionSessionID1)

ETSI


Test UI_32

Summary: IpUICall, sendInfoReq methods, P_INVALID_SESSION_ID




Test Sequence:

1. Method call sendInfoReq() Parameters: invalid userInteractionSessionID, info, language, variableInfo, repeatIndicator, responseRequested. Check: P_INVALID_SESSION_ID is returned

: IpAppUIManager : IpAp pUICall : IpUIManager : IpUICall

preamble:createUICall(app UI, uiT arg etOb je ct)


sendInfoReq(userInteractionSessionID_invalid, info, language, variableInfo, repeatIndicator, responseRequested)


ETSI


Test UI_33

Summary: IpUICall, sendInfoReq methods, P_INVALID_NETWORK_STATE





Test Sequence:

1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, repeatIndicator, responseRequested. Check: P_INVALID_NETWORK_STATE is returned

: IpAppUIManager : IpAp pUICall : IpUIManager : IpUICa ll



sendInfoReq(userInteractionSessionID1, info, language, variableInfo, repeatIndicator, responseRequested)


condition: the underlying protocol cannot support the method call.

ETSI


Test UI_34

Summary: IpUICall, sendInfoReq methods, P_ILLEGAL_ID




Test Sequence:

1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, illegal info, language, variableInfo, repeatIndicator, responseRequested. Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned

: IpAppUIManager : IpApp UICa ll : IpUIManager : I pUICal l

preamble:cre ateUICall(appUI, uiTargetObj ect)


sendInfo Req(userInteractio nSessionID1, i nfo_i l leg al, languag e, va riabl eInfo, repea tIndi cator, responseRequ ested)


ETSI


Test UI_35

Summary: IpUICall, sendInfoAndCollectReq methods, P_INVALID_SESSION_ID




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: invalid userInteractionSessionID, info, language, variableInfo, criteria, responseRequested. Check: P_INVALID_SESSION_ID is returned




sendInfoAnd Col lectReq(userInte ract ion SessionID_in valid , i nfo , la nguage, variableInfo, cri te ria, responseRequ ested)


ETSI


Test UI_36

Summary: IpUICall, sendInfoAndCollectReq methods, P_INVALID_NETWORK_STATE





Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, criteria, responseRequested. Check: P_INVALID_NETWORK_STATE is returned


preamble:

c ondition: the underlying protoc ol ca nnot s upport the method call .


use rInteractio nSessionID1

sendInfoAndCollectReq(userInteractionSessionID1, info, language, variableInfo, criteria, responseRequested)


ETSI


Test UI_37

Summary: IpUICall, sendInfoAndCollectReq methods, P_ILLEGAL_ID




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, illegal info, language, variableInfo, criteria, responseRequested Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned

: IpAppUIMana ger : IpAppUICall : IpUIManager : IpUICall


userIn teractionSe ssion ID1

sendInfoAndCollectReq(userInteractionSessionID, info_il legal, language, variableInfo, criteria, responseRequested)

P_ ILL EGAL_ID or P_ ID_NOT_FOUND

ETSI


Test UI_38

Summary: IpUICall, sendInfoAndCollectReq methods, P_ILLEGAL_RANGE




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, criteria with collection length out of range, responseRequested. Check: P_ILLEGAL_RANGE is returned


preamble:cre ate UICa ll(a ppUI, uiTargetObj ect)


sendInfoAndCollectReq(userInteractionSessionID, info, language, variableInfo, criteria_lengthOutOfRange, responseRequested)

P_ILLEGAL_RANGE

ETSI


Test UI_39

Summary: IpUICall, sendInfoAndCollectReq methods, P_INVALID_COLLECTION_CRITERIA




Test Sequence:

1. Method call sendInfoAndCollectReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, invalid collection criteria, responseRequested. Check: P_INVALID_COLLECTION_CRITERIA is returned

: IpUIManager : IpAppUIManager : IpAppUICall : IpUICall



sendInfoAndCollectReq(userInteractionSessionID, info, language, variableInfo, inval id_collection_criteria, responseRequested)

P_INVALID_COLLECTION_CRITERIA

ETSI


Test UI_40

Summary: IpUICall, recordMessageReq methods, P_INVALID_SESSION_ID



Selection: recordMessageReq method supported - PICS item: [2] UIC4

Test Sequence:

1. Method call recordMessageReq() Parameters: invalid userInteractionSessionID, info, criteria, Check: P_INVALID_SESSION_ID is returned


preamble:



recordMessageReq(userInteractionSessionID_invalid, info, criteria)

P_ INVALID_SESSION_ID

ETSI


Test UI_41

Summary: IpUICall, recordMessageReq methods, P_INVALID_NETWORK_STATE



Condition: the underlying protocol cannot support the method call (e.g. incompatible Call state)


Test Sequence:

1. Method call recordMessageReq() Parameters: userInteractionSessionID given in preamble, info, criteria, Check: P_INVALID_NETWORK_STATE is returned

: IpAppUIManager : IpAppUICall : IpUIManager : I pUICal l

preamble:





ETSI


Test UI_42

Summary: IpUICall, recordMessageReq methods, P_ILLEGAL_ID




Test Sequence:

1. Method call recordMessageReq() Parameters: userInteractionSessionID given in preamble, illegal info, criteria, Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned



userIntera ct io nSessi onID1

recordMessageReq(userInteractionSessionID1, info_il legal, criteria)

P_ILLEGAL_INFO or P_ID_NOT_FOUND

ETSI


Test UI_43

Summary: IpUICall, recordMessageReq methods, P_INVALID_CRITERIA




Test Sequence:

1. Method call recordMessageReq() Parameters: userInteractionSessionID given in preamble, info, invalid criteria, Check: P_INVALID_CRITERIA is returned


preamble:



re cordMessag eReq (userIn teracti onS essio nID1, i nfo, cri te ri a_i nvalid)

P_INVALID_CRITERIA

ETSI


Test UI_44

Summary: IpUICall, deleteMessageReq, P_INVALID_SESSION_ID




Test Sequence:



3. Method call deleteMessageReq() Parameters: invalid userInteractionSessionID, messageID returned in 2. Check: P_INVALID_SESSION_ID is returned


preamble:


u serIntera ct ionSessi onID1


assignme ntID1

re cordMessageRes(userInteractio nSessionID1, assignment ID1, response, m essageID1)

deleteMessageReq(userInteractionSessionID_invalid, messageID1)


ETSI


Test UI_45

Summary: IpUICall, deleteMessageReq, P_ILLEGAL_ID




Test Sequence:



3. Method call deleteMessageReq() Parameters: userInteractionSessionID given in preamble, illegal messageID. Check: P_ILLEGAL_ID or P_ID_NOT_FOUND is returned

: IpAppUIManager : IpAppUICall : IpUICall : IpUIManag er

reco rdMessageReq(u serIntera ct ionSessi onID, i nfo , criteri a)

assignmentID1

recordMessageRes(userInteractionSessionID1, assignmentID1, response, messageID1)

de le teMessageReq (userInte raction SessionID, m essage ID_ il le gal)



userInteractionSessionID

ETSI


Test UI_46

Summary: IpUICall, abortActionReq method, P_INVALID_SESSION_ID




Test Sequence:


2. Method call abortActionReq() Parameters: invalid userInteractionSessionID, assignmentID returned in 1. Check: P_INVALID_SESSION_ID is returned.

: IpAppUICall : IpUICal l

sendInfoReq(userInteractionSessionID, info, language, variableInfo, repeatIndicator, responseRequested)

assignmentID1

abortActionReq(userInteractionSessionID_invalid, assignmentID1)




userInteractionSessionsID

prea mble:

ETSI


Test UI_47

Summary: IpUICall, abortActionReq method, P_INVALID_ASSIGNMENT_ID




Test Sequence:


2. Method call abortActionReq() Parameters: userInteractionSessionID given in preamble, invalid assignmentID. Check: P_INVALID_ASSIGNMENT_ID is returned.



assignmentID1

abortActionReq(userInteractionSessionID, assignmentID_invalid)



prea mble : createUICall(ap pUI, uiTargetObject)


ETSI


Test UI_48

Summary: IpUICall, abortActionReq method, P_INVALID_SESSION_ID




Test Sequence:


2. Method call abortActionReq() Parameters: invalid userInteractionSessionID, assignmentID returned in 1. Check: P_INVALID_SESSION_ID is returned.

: IpAp pUICall : IpUICall


assignment ID1

ab ortActionReq(u serInte ractionSessio nID_in valid, assignmentID1)

P_ INVALID_SESSION_ID


preamble: createUICall(app UI, uiTa rg etOb ject)


ETSI


Test UI_49

Summary: IpUICall, abortActionReq method, P_INVALID_ASSIGNMENT_ID




Test Sequence:


2. Method call abortActionReq() Parameters: userInteractionSessionID given in preamble, invalid assignmentID. Check: P_INVALID_ASSIGNMENT_ID is returned.


sendInfoAndCol lectReq(use rInteractionSessionID, info, language, variabl eIn fo, criteria , response Requested)

assignmentID1

abortActionReq(userInteractionSessionID, assignmentID_invalid)



preamble: createUICall(appUI, uiTargetObject)

use rInteractio nSessi onID

5.2.2 User Interaction, application side

In performing the tests for the application, it may be necessary to permit the application to perform any valid set of method exchanges with the tester in between the triggered actions or method calls indicated in the tests below. The tester shall respond to the application's method calls in conformance to the API specification and as required by the application. The requirements of the application should be made known to the tester's operator in advance.

ETSI


5.2.2.1 IpAppUIManager interface

Test UI_APP_01

Summary: IpAppUIManager, userInteractionAborted


Preamble: A User Interaction object, created either with the createUI or the createUICall method on the corresponding IpUIManager interface or reported in a reportEventNotification method, exists. The given sessionID is used in the following methods to identify this User Interaction object.

Selection: userInteractionAborted method supported - PICS item: [2] AUIM1

Test Sequence:

1. Method call userInteractionAborted() Parameters: userInteractionSessionID as given in preamble. Check: no exception is returned


preamble: a UserInteraction object w ith a giv en userInteractionSessionID exists.

userIn te ractionAb orted (userIn teractionSe ssion ID)

Test UI_APP_02

Summary: IpAppUIMAnager, userInteractionNotificationInterrupted


Preamble: A User Interaction object, created either with the createUI or the createUICall method on the corresponding IpUIManager interface or reported in a reportEventNotification method, exists.

Selection: userInteractionNotificationInterrupted method supported - PICS item: [2] AUIM2

Test Sequence:

1. Method call userInteractionNotificationInterrupted () Parameters: none. Check: no exception is returned

ETSI




userInteractionNotificationInterrupted(userInteractionSessionID )

Test UI_APP_03

Summary: IpAppUIMAnager, userInteractionNotificationContinued


Preamble: A User Interaction object, created either with the createUI or the createUICall method on the corresponding IpUIManager interface or reported in a reportEventNotification method, exists.

Selection: userInteractionNotificationContinued method supported - PICS item: [2] AUIM3

Test Sequence:

1. Method call userInteractionNotificationContinued () Parameters: none. Check: no exception is returned



userInteractionNotificationContinued( userInteractionSessionID)

ETSI


Test AM_APP_20

Summary: IpAppUIMAnager all methods, successful


Precondition: reportEventNotification supported

Preamble: Registration of the IUT (application) and the tester (User Interaction SCF) to the framework. The tester must have obtained a reference to an instance of the IpAppAccountManager interface through selecting that service and signing the required service agreement.

Test Sequence:

1. Triggered action: cause IUT to call enableNotifications () method on the tester's (SCF) IpUIManager interface. Parameters: appAccountManager

2. Method call reportEventNotification () Parameters: userInteraction, eventNotificationInfo, assignmentID Check: no exception is returned

3. Triggered action: cause IUT to call disableNotifications () method on the tester's (SCF) IpUIManager interface. Parameters: none

: I pAp pUIMa nage r : IpUIManager

disableNotifications()

enableNotifications(appUIManager)

assignmentID


ETSI


5.2.2.2 IpAppUI interface

Test UI_APP_04

Summary: IpAppUI, sendInfoRes



Selection: sendInfoRes method supported - PICS item: [2] AUI1

Test Sequence:

1. Triggered action: cause IUT to call sendInfoReq() method on the tester's (SCF) IpUI interface. Check: valid value of userInteraction, info, language, variableInfo, repeatIndicator and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoRes() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. and response is transmitted. Check: no exception is returned

: IpAppUI : IpUI

preamble: a UserInteraction object with a given userInteractionSessionID exists.


assignmentID

sendInfoRes(userInteractionSessionID, assignmentID, response)

ETSI


Test UI_APP_05

Summary: IpAppUI, sendInfoErr



Selection: sendInfoErr method supported - PICS item: [2] AUI2

Test Sequence:

1. Triggered action: cause IUT to call sendInfoReq() method on the tester's (SCF) IpUI interface. Check: valid value of userInteraction, info, language, variableInfo, repeatIndicator and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. and error is transmitted. Check: no exception is returned

: IpAppUI : IpUI



assignmentID

sendInfoErr(userInteractionSessionID, assignmentID, error)

ETSI


Test UI_APP_06

Summary: IpAppUI, sendInfoAndCollectRes



Selection: sendInfoAnd CollectRes method supported - PICS item: [2] AUI3

Test Sequence:

1. Triggered action: cause IUT to call sendInfoAndCollectReq() method on the tester's (SCF) IpUI interface. Check: valid value of userInteraction, info, language, variableInfo, criteria and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoAndCollectRes() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. response and collectedInfo is transmitted. Check: no exception is returned

: IpAppUI : IpUI



assignmentID

send InfoAn dCol le ctRes(userIn teractionSe ssionID, assi gnmentID, resp onse, co llected Info)

ETSI


Test UI_APP_07

Summary: IpAppUI, sendInfoAndCollectErr



Selection: sendInfoAndCollectErr method supported - PICS item: [2] AUI4

Test Sequence:

1. Triggered action: cause IUT to call sendInfoAndCollectReq() method on the tester's (SCF) IpUI interface. Check: valid value of userInteraction, info, language, variableInfo, criteria and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoAndCollectErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. error and collectedInfo is transmitted. Check: no exception is returned

: IpAppUI : IpUI



assignmentID

sendInfoAndCollectErr(userInteractionSessionID, assignmentID, error, col lectedInfo)

ETSI


Test UI_APP_08

Summary: IpAppUI, userInteractionFaultDetected



Selection: userInteractionFaultDetected method supported - PICS item: [2] AUI5

Test Sequence:

1. Method call userInteractionFaultDetected() Parameters: userInteractionSessionID as given in preamble and fault is transmitted. Check: no exception is returned

: I pAp pUI : IpUI

pre amble: a User Inte raction object w ith a given user Inte ractionSes sionID e xis ts.

userInteractionFaultDetected(userInteractionSessionID, fault)

5.2.2.3 IpAppUICall interface

Test UI_APP_09

Summary: IpAppUICall, sendInfoRes



Selection: sendInfoRes method supported - PICS item: [2] AUIC1

Test Sequence:

1. Triggered action: cause IUT to call sendInfoReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, info, language, variableInfo, repeatIndicator and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoRes() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. and response is transmitted. Check: no exception is returned

ETSI





assignmentID

sendInfoRes(userInteractionSessionID, assignmentID, response)

Test UI_APP_10

Summary: IpAppUICall, sendInfoErr



Selection: sendInfoErr method supported - PICS item: [2] AUIC2

Test Sequence:

1. Triggered action: cause IUT to call sendInfoReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, info, language, variableInfo, repeatIndicator and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. and error is transmitted. Check: no exception is returned

ETSI





assignmentID

sendInfoErr(userInteractionSessionID, assignmentID, error)

Test UI_APP_11

Summary: IpAppUICall, sendInfoAndCollectRes



Selection: sendInfoAnd CollectRes method supported - PICS item: [2] AUIC3

Test Sequence:

1. Triggered action: cause IUT to call sendInfoAndCollectReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, info, language, variableInfo, criteria and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoAndCollectRes() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. response and collectedInfo is transmitted. Check: no exception is returned

ETSI





assignmentID

send InfoAn dCol le ctRes(userIn teractionSe ssionID, assi gnmentID, resp onse, co llected Info)

Test UI_APP_12

Summary: IpAppUICall, sendInfoAndCollectErr



Selection: sendInfoAndCollectErr method supported - PICS item: [2] AUIC4

Test Sequence:

1. Triggered action: cause IUT to call sendInfoAndCollectReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, info, language, variableInfo, criteria and responseRequested is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call sendInfoAndCollectErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. error and collectedInfo is transmitted. Check: no exception is returned

ETSI




sen dInfo AndCo llectReq (userIn teracti onSe ssio nID, in fo, la nguag e, vari abl eInfo, cri te ri a, responseRe queste d)

assignmentID

sendInfoAndCollectErr(userInteractionSessionID, assignmentID, error, col lectedInfo)

Test UI_APP_13

Summary: IpAppUICall, userInteractionFaultDetected



Selection: userInteractionFaultDetected method supported - PICS item: [2] AUIC5

Test Sequence:

1. Method call userInteractionFaultDetected() Parameters: userInteractionSessionID as given in preamble and fault is transmitted. Check: no exception is returned

: IpAppUICall : IpUICall

pre amble: a User Inte raction object w ith a given user Inte ractionSes sionID e xis ts.

userInteractionFaultDetected(userInteractionSessionID, fault)

ETSI


Test UI_APP_14

Summary: IpAppUICall, recordMessageRes



Selection: recordMessageRes method supported - PICS item: [2] AUIC6

Test Sequence:

1. Triggered action: cause IUT to call recordMessageReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, info and criteria is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call recordMessageRes() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1, response and messageID is transmitted. Check: no exception is returned



record Me ssageReq(use rInteractio nSessionID, info, cri teria)

assignme ntID

reco rd Me ssageRes(userInteracti onSession ID, assig nm entID, re spo nse , m essage ID)

ETSI


Test UI_APP_15

Summary: IpAppUICall, recordMessageErr



Selection: recordMessageErr method supported - PICS item: [2] AUIC7

Test Sequence:


2. Method call recordMessageErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1, and error is transmitted. Check: no exception is returned

: IpUICal l : IpAppUICall


record Me ssageReq(use rInteractio nSessionID, info, cri teria)

assignme ntID

recordMessageErr(userInteractionSessionID, assignmentID, error)

ETSI


Test UI_APP_16

Summary: IpAppUICall, deleteMessageRes



Selection: deleteMessageRes method supported - PICS item: [2] AUIC8

Test Sequence:

1. Triggered action: cause IUT to call deleteMessageReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction and messageID is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call deleteMessageRes() Parameters: userInteractionSessionID as given in preamble, response and assignmentID as given in 1. is transmitted. Check: no exception is returned



de leteMessageReq(u serInteraction SessionID, messag eID)

assignme ntID

deleteMessageRes(userInteractionSessionID, response, assignmentID)

ETSI


Test UI_APP_17

Summary: IpAppUICall, deleteMessageErr



Selection: deleteMessageErr method supported - PICS item: [2] AUIC9

Test Sequence:

1. Triggered action: cause IUT to call deleteMessageReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction and messageID is transmitted, Return: valid value of TpAssignmentID is returned

2. Method call deleteMessageErr() Parameters: userInteractionSessionID as given in preamble, error and assignmentID as given in 1. is transmitted. Check: no exception is returned



de leteMessageReq(u serInteraction SessionID, messag eID)

assignme ntID

de le teMessageErr(userIn teractionSessio nID, erro r, a ssig nm entID)

ETSI


Test UI_APP_18

Summary: IpAppUICall, abortActionRes



Selection: abortActionRes method supported - PICS item: [2] AUIC10

Test Sequence:


2. Triggered action: cause IUT to call abortActionReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, and assignmentID as given in 1. is transmitted, Return: no exception is returned

3. Method call abortActionRes() Parameters: userInteractionSessionID as given in preamble, and assignmentID as given in 1. is transmitted. Check: no exception is returned



recordMessageReq(use rInteractio nSessionID, info, cri teria)

assignmentID

abortActionReq (userIn teracti onS essionID, assignmentID)

abortActionRes(userInteractionSessionID, assignmentID)

ETSI


Test UI_APP_19

Summary: IpAppUICall, abortActionErr



Selection: abortActionErr method supported - PICS item: [2] AUIC10

Test Sequence:


2. Triggered action: cause IUT to call abortActionReq() method on the tester's (SCF) IpUICall interface. Check: valid value of userInteraction, and assignmentID as given in 1. is transmitted, Return: no exception is returned

3. Method call abortActionErr() Parameters: userInteractionSessionID as given in preamble, assignmentID as given in 1. and error is transmitted. Check: no exception is returned



recordMessageReq(use rInteractio nSessionID, info, cri teria)

assignmentID

abortActionReq (userIn teracti onS essionID, assignmentID)

abortActionErr(userInteractionSessionID, assignmentID, error)

ETSI


History

Document history

V1.1.1 January 2005 Membership Approval Procedure MV 20050311: 2005-01-11 to 2005-03-11

Open Service Access (OSA); Application Programming ... · Final draft ETSI ES 202 388-5 V1.1.1...

Documents

Transcript of Open Service Access (OSA); Application Programming ... · Final draft ETSI ES 202 388-5 V1.1.1...