ETSI ES 202 388-14-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 14 Presence and Availability Manageme_1.pdf

1、 ETSI ES 202 388-14 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 14: Presence and Availability Management SCF(Parlay 4)ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-14-OSA Keywo

2、rds API, OSA, TSS 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, inclu

3、ding 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 pro

4、duced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 14 of a multi-part deliverable. Full details of the entire series can be found in part 1 6. To evaluate conformance of a particular implem

5、entation, 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 Application Programming Interface (API); Part 14: Presence and A

6、vailability Management 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 testi

7、ng 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

8、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 Part 1: Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the pu

9、rposes of the present document, the terms and definitions given in ES 202 915-14 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.

10、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. ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 6 ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation eXtra Information for Te

11、sting (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

12、Test Suite ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access PAM Presence and Availability Management SCF Service Capability Feature TP Test Purpose TSS Test Suite Structure 4 Test Suite St

13、ructure (TSS) Presence and Availability Management - PAM Access Service - PAM Event Handler 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. Addi

14、tional references are added to identify the actual test suite (see table 1). Table 1: TP identifier naming convention scheme Identifier: _ = SCG name: “PAM“ for Presence and Availability Management SCF = group number: two character field representing the group reference according to TSS = sequential

15、 number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-14 1. ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 7 5.1.3 Test strategy As the base standard ES 202 915-14 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base sta

16、ndard and the ICS 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 Presence and

17、Availability Management SCF All ICS 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 ar

18、e 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 Presence and Availability Management, SCF side 5.2.1.1 PAM Access Service 5.2.1.1.1 IpPAMPresenceAvailabilityManager Preconditio

19、n: IpPAMPresenceAvailabilityManager supported. Test PAM_AS_01 Summary: IpPAMPresenceAvailabilityManager, obtainInterface and getAuthToken successful. Reference: ES 202 915-14 1, clause 8.2.1. Preamble: Registration of the IUT (PAM SCF) and the tester (application) to the framework. The tester must h

20、ave obtained a reference to an instance of the IpPAMPresenceAvalibilityManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call obtainInterface() Parameters: interfaceName Check: valid value of IpInterfaceRef is returned 2. Method cal

21、l getAuthToken() Parameters: askerData Check: valid value of TpPAMCredential is returned ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 8 : IpInitial : IpPAMPresenceAvailabilityManagerApplication1. obtainInterface(interfaceName)2. getAuthToken(askerData)IpInterfaceRefTpPAMCredentialPreamble_getAuthToken_A

22、S Summary: Preamble to obtain the authentication token. Reference: ES 202 915-14 1, clause 8.2. Pre-preamble: Registration of the IUT (PAM SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpPAMPresenceAvalibilityManager interface thr

23、ough selecting that service and signing the required service agreement. Test Sequence: 1. Method call obtainInterface() Parameters: interfaceName Check: valid value of IpInterfaceRef is returned 2. Method call getAuthToken() Parameters: askerData Check: valid value of TpPAMCredential is returned ETS

24、I ETSI ES 202 388-14 V1.1.1 (2005-03) 9 : IpInitial : IpPAMPresenceAvailabilityManagerApplication1. obtainInterface(interfaceName)2. getAuthToken(askerData)IpInterfaceRefTpPAMCredentialTest PAM_AS_02 Summary: IpPAMPresenceAvailabilityManager, getAccessControl successful. Reference: ES 202 915-14 1,

25、clause 8.2.1.3. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call getAccessControl() Parameters: identity, authToken as obtained in Preamble Check: valid value of TpPAMAccessControlData is returned FrameworkApplication : IpPAMPresenceAvailabilityManager1. getAccessControl(identity, a

26、uthToken)TpPAMAccessControlDataETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 10Test PAM_AS_03 Summary: IpPAMPresenceAvailabilityManager, getAccessControl and setAccessControl successful. Reference: ES 202 915-14 1, clause 8.2.1.4. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setAcces

27、sControl() Parameters: identity, operation, newAccessControl, authToken as obtained in Preamble Check: no exception returned NOTE: setAccessControl() can be used in conjunction with getAccessControl(). : IpPAMPresenceAvailabilityManagerFrameworkApplication1. setAccessControl(identity, operation, new

28、AccessControl, authToken)5.2.1.1.2 IpPAMIdentityPresence Precondition: IpPAMIdentityPresence supported. Test PAM_AS_04 Summary: IpPAMIdentityPresence, setIdentityPresence successful. Reference: ES 202 915-14 1, clause 8.2.2.1. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setIden

29、tityPresence() Parameters: identity, identityType, attributes, authToken as obtained in Preamble Check: no exception returned : IpPAMIdentityPresenceFrameworkApplication1. setIdentityPresence(identity, identityType, attributes, authToken)ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 11Test PAM_AS_05 Summ

30、ary: IpPAMIdentityPresence, setIdentityPresenceExpiration successful. Reference: ES 202 915-14 1, clause 8.2.2.2. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setIdentityPresenceExpiration() Parameters: identity, identityType, attributeNames, expiresIn, authToken as obtained in

31、Preamble Check: no exception returned : IpPAMIdentityPresenceApplication1. setIdentityPresenceExpiration(identity, identityType, attributeNames, expiresIn, authToken)Test PAM_AS_06 Summary: IpPAMIdentityPresence, getIdentityPresence successful. Reference: ES 202 915-14 1, clause 8.2.2.3. Preamble: P

32、reamble_getAuthToken_AS. Test Sequence: 1. Method call getIdentityPresence () Parameters: identity, identityType, attributeNames, authToken as obtained in Preamble Check: valid value of TpPAMAttributeList is returned : IpPAMIdentityPresenceFrameworkApplication1. getIdentityPresence(identity, identit

33、yType, attributeNames, authToken)TpPAMAttributeListETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 125.2.1.1.3 IpPAMAvailability Precondition: IpPAMAvailability supported. Test PAM_AS_07 Summary: IpPAMAvailability, getAvailability successful. Reference: ES 202 915-14 1, clause 8.2.3.1. Preamble: Preamble_g

34、etAuthToken_AS. Test Sequence: 1. Method call getAvailability() Parameters: identity, pamContext, attributeNames, authToken as obtained in Preamble Check: valid value of TpPAMAvailabilityProfileList is returned : IpPAMAvailabilityFrameworkApplication1. getAvailability(identity, pamContext, attribute

35、Names, authToken)TpPAMAvailabilityProfileListTest PAM_AS_08 Summary: IpPAMAvailability, getAvailability successful. Reference: ES 202 915-14 1, clause 8.2.3.1. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call getAvailability() Parameters: identity, pamContext, attributeNames, authTo

36、ken as obtained in Preamble Check: valid value of TpPAMAvailabilityProfileList is returned 2. Triggered action: cause IUT to call computeAvailability() method on the testers (Application) IpAppPAMPreferenceCheck interface. Parameters: identity, pamContext, attributeNames, authToken. ETSI ETSI ES 202

37、 388-14 V1.1.1 (2005-03) 13FrameworkApplication : IpPAMAvailability : IpAppPAMPreferenceCheckgetAvailability(identity, pamContext, attributeNames, authToken)TpPAMAvailabilityProfileList2. computeAvailability(identity, pamContext, attributeNames, authToken)Test PAM_AS_09 Summary: IpPAMAvailability, g

38、etPreference successful. Reference: ES 202 915-14 1, clause 8.2.3.2. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call getPreference() Parameters: identity, pamContext, authToken as obtained in Preamble Check: valid value of TpPAMPreferenceData is returned : IpPAMAvailabilityFramewor

39、kApplication1. getPreference(identity, pamContext, authToken)TpPAMPreferenceDataETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 14Test PAM_AS_10 Summary: IpPAMAvailability, setPreference successful. Reference: ES 202 915-14 1, clause 8.2.3.3. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method cal

40、l setPreference() Parameters: identity, pamContext, operation, newPreference, authToken as obtained in Preamble Check: valid value of TpPAMPreferenceData is returned : IpPAMAvailabilityFrameworkApplication1. setPreference(identity, pamContext, operation, newPreference, authToken)5.2.1.1.4 IpPAMAgent

41、Presence Precondition: IpPAMAgentPresence supported. Test PAM_AS_11 Summary: IpPAMAgentPresence, setAgentPresence successful. Reference: ES 202 915-14 1, clause 8.2.4.1. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setAgentPresence() Parameters: agent, agentType, attributes, aut

42、hToken as obtained in Preamble Check: no exception returned : IpPAMAgentPresenceFrameworkApplication1. setAgentPresence(agent, agentType, attributes, authToken)ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 15Test PAM_AS_12 Summary: IpPAMAgentPresence, setCapabilityPresence successful. Reference: ES 202 9

43、15-14 1, clause 8.2.4.2. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setCapabilityPresence() Parameters: agent, capability, attributes, authToken as obtained in Preamble Check: no exception returned : IpPAMAgentPresenceFrameworkApplication1. setCapabilityPresence(agent, capabil

44、ity, attributes, authToken)Test PAM_AS_13 Summary: IpPAMAgentPresence, setAgentPresenceExpiration successful. Reference: ES 202 915-14 1, clause 8.2.4.3. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setAgentPresenceExpiration() Parameters: agent, agentType, attributeNames, expir

45、esIn, authToken as obtained in Preamble Check: no exception returned : IpPAMAgentPresenceFrameworkApplication1. setAgentPresenceExpiration(agent, agentType, attributeNames, expiresIn, authToken)ETSI ETSI ES 202 388-14 V1.1.1 (2005-03) 16Test PAM_AS_14 Summary: IpPAMAgentPresence, setCapabilityPresen

46、ceExpiration successful. Reference: ES 202 915-14 1, clause 8.2.4.4. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call setCapabilityPresenceExpiration() Parameters: agent, capability, attributeNames, expiresIn, authToken as obtained in Preamble Check: no exception returned : IpPAMAge

47、ntPresenceFrameworkApplication1. setCapabilityPresenceExpiration(agent, capability, attributeNames, expiresIn, authToken)Test PAM_AS_15 Summary: IpPAMAgentPresence, getAgentPresence successful. Reference: ES 202 915-14 1, clause 8.2.4.5. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method c

48、all getAgentPresence() Parameters: agent, agentType, attributeNames, authToken as obtained in Preamble Check: valid value of TpPAMAttributeList is returned Application : IpPAMAgentPresence1. getAgentPresence(agent, agentType, attributeNames, authToken)TpPAMAttributeListETSI ETSI ES 202 388-14 V1.1.1

49、 (2005-03) 17Test PAM_AS_16 Summary: IpPAMAgentPresence, getCapabilityPresence successful. Reference: ES 202 915-14 1, clause 8.2.4.6. Preamble: Preamble_getAuthToken_AS. Test Sequence: 1. Method call getCapabilityPresence() Parameters: agent, capability, attributeNames, authToken as obtained in Preamble Check: valid value of TpPAMAttributeList is returned : IpPAMAgentPresenceApplication1. getCapabilityPresence(agent, capability, attributeNames, authToken)TpPAMAttributeList5.2.1.2 PAM Event Management Servic