ETSI TS 186 010-2-2017 Core Network and Interoperability Testing (INT) Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem Conformance test specification (3GPP R_1.pdf

1、 ETSI TS 186 010-2 V4.1.1 (2017-12) Core Network and Interoperability Testing (INT); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance test specification; (3GPP Release 12); Part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPR

2、s notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be giv

3、en 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by thei

4、r owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services

5、or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Core Network and Interoperability Testing (INT). The present document is part 2 of a multi-part deliverable covering the Conformance Test Specification of Confe

6、rence (CONF) using IP Multimedia (IM) Core Network (CN) subsystem, as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS)“; Part 2: “Test Suite Structure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Te

7、sting (PIXIT) proforma specification“. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression

8、of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)5 1 Scope The present document provides the Implementation Conformance Statement (ICS) pro forma for the Conference (CONF) service based on stage one

9、 and two of the ISDN CONF supplementary service defined in ETSI TS 124 605 1 in compliance with the relevant requirements 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific ref

10、erences, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference. NOTE:

11、 While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 124 605 (V12.5.0) (04-2015): “Digital cellular telecommunicatio

12、ns system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 12.5.0 Release 12)“. 2 ETSI TS 124 147: “Digital cellular telecommunications system (Phase 2+) (GSM); U

13、niversal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 Release 12)“. 3 ETSI TS 186 010-1: “Core Network and Interoperability Testing (INT); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subs

14、ystem; Conformance test specification (3GPP Release 12); Part 1: Protocol Implementation Conformance Statement (PICS)“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only

15、 the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following reference

16、d documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ISO/IEC 9646-1: “Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 1: General concepts“. ETSI ET

17、SI TS 186 010-2 V4.1.1 (2017-12)6 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 124 605 1 and the following apply: Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 i.1. PICS pro forma: Refer to IS

18、O/IEC 9646-1 i.1. Point of Control and Observation: Refer to ISO/IEC 9646-1 i.1. Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 i.1. System Under Test (SUT): Refer to ISO/IEC 9646-1 i.1. Test Purpose (TP): Refer to ISO/IEC 9646-1 i.1. NOTE: This may contain additional

19、information. 3.2 Symbols For the purposes of the present document, the symbols given in ETSI TS 124 605 1 apply. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 124 605 1 and the following apply: CONF CONFerence calling IUT Implementation Under Test SUT

20、 System Under Test UE User Equipment 4 Test Suite Structure (TSS) and configuration 4.1 Table of Test Suite Structure ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)7 Table 4.1-1: Test suite structure ConferenceFocus CreateConf CONF_N01_xxx JoinConf CONF_N02_xxxInviteToConf CONF_N03_xxxLeaveConf CONF_N04_xx

21、xRemoveFromConf CONF_N05_xxx TerminateConf CONF_N06_xxxUserEquipment CONF_U01_xxx Interaction TIR CONF_N08_xxxOIR CONF_N09_xxx ACR-CB CONF_N10_xxx4.2 Configuration 4.2.0 Introduction The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as des

22、cribed in ETSI TS 124 605 1. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. 4.2.1 Testing of the AS The AS en

23、tity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. Figure 4.2-1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx) i

24、nterface (see figure 4.2-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)8 Figure 4.2-2: Applicable interfaces for tests using a (generic) NNI interfac

25、e 4.2.2 Testing of the UE There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating user equipment. Therefore the test configuration in figure 4.2-3 has been chosen. Figure 4.2-3: Applicable configuration to test UE functionalities 5 T

26、est Purposes (TP) 5.1 Introduction 5.1.1 TP naming convention TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 5.1-1). Table

27、5.1-1: TP identifier naming convention scheme Identifier: _ = supplementary service: e.g. “CONF“ = type of IUT: U User N Networkyyy service = group 2 digit field representing group reference according to TSS = sequential number (001-999) ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)9 5.1.2 Test strategy A

28、s the base standard ETSI TS 124 605 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 ETSI TS 186 010-1 3. 5.2 Signalling requirements 5.2.1 Conference Focus 5.2.1.1 Conference creation TSS ConferenceFoc

29、us/CreateConf TP CONF_N01_001 Reference 5.3.2.3.1, 5.3.3 2 Selection expression PICS 4.5.1/2 Test purpose Conference creation with a conference factory URI. Conference event package subscribed. Ensure that a conference can be created by a UE using the conference factory URI. The “isfocus“ feature pa

30、rameter indicated in Contact header is received in the 200 OK (INVITE). In addition the conference participant subscribes to the conference event package and receives a NOTIFY request describing the conference status. SIP header values: INVITE: Request URI indicating the conference factory URI 200 O

31、K: conference URI and “isfocus“ feature parameter included in Contact header field SUBSCRIBE: Request URI indicating the conference URI Event header contains “conference“ NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx Comments: ISC#1 Focus INVITE barb4right 200 O

32、K (INVITE) barb4left ACK barb4right SUBSCRIBE barb4right 200 OK (SUBSCRIBE) barb4left NOTIFY barb4left 200 OK NOTIFY barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_002 Reference 5.3.2.3.1 2 Selection expression PICS 4.5.1/2 Test purpose Conference creation with a confe

33、rence factory URI. Conference event package not subscribed. Ensure that a conference can be created by a UE using the conference factory URI. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant does not subscribe to the conferenc

34、e event package. SIP header values: INVITE: Request URI indicating the conference factory URI 200 OK: conference URI and “isfocus“ feature parameter included in Contact header field Comments: ISC#1 Focus INVITE barb4right 200 OK (INVITE) barb4left ACK barb4right Apply post test routine ETSI ETSI TS

35、186 010-2 V4.1.1 (2017-12)10 TSS ConferenceFocus/CreateConf TP CONF_N01_003 Reference 5.3.2.3.2, 5.3.3 2 Selection expression PICS 4.5.1/2 Test purpose Conference creation with a conference URI. Conference event package subscribed. Ensure that a conference can be created by a UE using the conference

36、 URI. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). In addition the conference participant subscribes to the conference event package and receives a NOTIFY request describing the conference status. SIP header values: INVITE: Request URI indicating th

37、e conference URI 200 OK: “isfocus“ feature parameter included in Contact header field conference URI contained in the Contact header field SUBSCRIBE: Request URI indicating the conference URI Event header contains “conference“ NOTIFY: Event contains conference; Subscription-State contains active; ex

38、pires=xxxx Comments: ISC#1 Focus INVITE barb4right 200 OK (INVITE) barb4left ACK barb4right SUBSCRIBE barb4right 200 OK (SUBSCRIBE) barb4left NOTIFY barb4left 200 OK NOTIFY barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_004 Reference 5.3.2.3.2 2 Selection expression PI

39、CS 4.5.1/2 Test purpose Conference creation with a conference URI. Conference event package not subscribed. Ensure that a conference can be created by a UE using the conference URI. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference partici

40、pant does not subscribe to the conference event package. SIP header values: INVITE: Request URI indicating the conference URI 200 OK: “isfocus“ feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus INVITE barb4right 200 OK (INV

41、ITE) barb4left ACK barb4right Apply post test routine ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)11 TSS ConferenceFocus/CreateConf TP CONF_N01_005 Reference 5.3.2.3.1 2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose Conference creation with a conference factory URI. Preconditions indica

42、ted a conference URI is sent in the first provisional response. Ensure that a conference can be created by a UE using the conference factory URI. Preconditions are requested by the originating UE. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). SIP hea

43、der values: INVITE: Request URI indicating the conference factory URI SDP a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv 183 conference URI contained in the Contact header field SDP a=curr:qos local none a=curr:qos remote none a=des:qos

44、 mandatory local sendrecv a=des:qos mandatory remote sendrecv a=conf:qos remote sendrecv UPDATE: SDP a=curr:qos local sendrecv a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos mandatory remote sendrecv 200 OK UPDATE SDP a=curr:qos local sendrecv a=curr:qos remote sendrecv a=des:qo

45、s mandatory local sendrecv a=des:qos mandatory remote sendrecv 200 OK: “isfocus“ feature parameter included in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus INVITE barb4right 183 Session Progress barb4left PRACK barb4right 200 OK PRACK barb4left UPDA

46、TE barb4right 200 OK UPDATE barb4left 200 OK (INVITE) barb4left ACK barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_006 Reference 5.3.2.3.1 2 Selection expression PICS 4.5.1/2 Test purpose Conference creation with a conference factory URI not allocated in the focus, uns

47、uccessful. Ensure that a conference cannot be created by a UE using a conference factory URI not allocated in the focus. The request is rejected by the focus with a 488 Not Acceptable Here final response. SIP header values: INVITE: Request URI indicating a conference factory URI not allocated in the

48、 focus Comments: ISC#1 Focus INVITE barb4right 488 Not Acceptable Here barb4left ACK barb4right ETSI ETSI TS 186 010-2 V4.1.1 (2017-12)12 5.2.1.2 Joining a conference TSS ConferenceFocus/JoinConf TP CONF_N02_001 Reference 5.3.2.4.1 2 Selection expression PICS 4.5.1/2 Test purpose Participant dial-in

49、 the conference, the conference URI is used. UE1 (via ISC#1) established a conference. UE2 (via ISC#2) joins in that conference by sending an INVITE request to the conferencing AS (the conference URI is known at the UE2). The request is successful. SIP header values: INVITE 2: Request URI indicating the conference URI 18x “isfocus“ feature parameter included in Contact header field 200 OK: “isfocus“ feature parameter included in Contact header field conference URI contained in the Contact header field Comments: ISC