1、 ETSI TS 186 010-2 V3.2.1 (2015-10) Core Network and Interoperability Testing (INT); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance test specification (3GPP Release 10); Part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs
2、 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:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given
3、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 Technical Specification (TS) has been produced by ETSI Technical Committee Core Network and Interoperabili
4、ty Testing (INT). The present document is part 2 of a multi-part deliverable covering the Conformance Test Specification of Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem, as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS)“; Part 2: “Test Suite
5、 Structure and Test Purposes (TSS Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 10.1.0 Release 10)“. 2 ETSI TS 124 147: “Digital cellular telecommunications system (Phase
6、2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 Release 10)“. 3 ETSI TS 186 010-1: “Core Network and Interoperability Testing (INT); Conference (CONF) using IP Multimedia (IM) Core Network (CN
7、) subsystem; Conformance test specification (3GPP Release 10); 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
8、, only the cited version applies. For non-specific references, the latest version of the reference 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 refe
9、renced 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“. 3
10、Definitions 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 ISO/IEC 9646-1 i.1. ETSI ETSI TS 186 010-2 V3.2
11、.1 (2015-10)6 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 info
12、rmation. 3.2 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 System Under Test UE User Equipment 4 Test Suite Structure (TSS) 4.0 Introduction Table 4.0-1: Test sui
13、te structure ConferenceFocus CreateConf CONF_N01_xxx JoinConf CONF_N02_xxxInviteToConf CONF_N03_xxxLeaveConf CONF_N04_xxxRemoveFromConf CONF_N05_xxx TerminateConf CONF_N06_xxxUserEquipment CONF_U01_xxx Interaction TIR CONF_N08_xxxOIR CONF_N09_xxx ACR-CB CONF_N10_xxx4.1 Configuration 4.1.0 Introducti
14、on The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described 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 inte
15、rfaces (reference points) are addressed to satisfy the test of the different entities. 4.1.1 Testing of the AS The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. ETSI ETSI TS 186 010-2 V3.2.1 (2015-10)7 Figure 4.1-1: Appl
16、icable 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) interface (see figure 4.1-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verificati
17、on of all requirements may not be possible. Figure 4.1-2: Applicable interfaces for tests using a (generic) NNI interface 4.1.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 t
18、est configuration in figure 4.1-3 has been chosen. Figure 4.1-3: Applicable configuration to test UE functionalities ETSI ETSI TS 186 010-2 V3.2.1 (2015-10)8 5 Test Purposes (TP) 5.1 Introduction 5.1.1 TP naming convention TPs are numbered, starting at 001, within each group. Groups are organized ac
19、cording 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 5.1-1: TP identifier naming convention scheme Identifier: _ = supplementary service: e.g. “CONF“ = type of IUT: U User N Networkyyy service
20、 = group 2 digit field representing group reference according to TSS = sequential number (001-999) 5.1.2 Test strategy As 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 specificati
21、on ETSI TS 186 010-1 3. 5.2 Signalling requirements 5.2.1 Conference Focus 5.2.1.1 Conference creation TSS ConferenceFocus/CreateConf TP CONF_N01_001 Reference 5.3.2.3.1, 5.3.3 2 Selection expression PICS 4.1/2 Test purpose Conference creation with a conference factory URI. Conference event package
22、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). In addition the conference participant subscribes to the conference event package and receives a NOTIFY reques
23、t describing the conference status. SIP header values: INVITE: Request URI indicating the conference factory URI 200 OK: conference URI and “isfocus“ feature parameter included in Contact header field SUBSCRIBE: Request URI indicating the conference URI Event header contains “conference“ NOTIFY: Eve
24、nt contains conference; Subscription-State contains active; expires=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 ETSI ETSI TS 186 010-2 V3.2.1
25、(2015-10)9 TSS ConferenceFocus/CreateConf TP CONF_N01_002 Reference 5.3.2.3.1 2 Selection expression PICS 4.1/2 Test purpose Conference creation with a conference factory URI. Conference event package not subscribed. Ensure that a conference can be created by a UE using the conference factory URI. T
26、he “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant does not subscribe to the conference event package. SIP header values: INVITE: Request URI indicating the conference factory URI 200 OK: conference URI and “isfocus“ feature para
27、meter included in Contact header field Comments: ISC#1 Focus INVITE barb4right 200 OK (INVITE) barb4left ACK barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_003 Reference 5.3.2.3.2, 5.3.3 2 Selection expression PICS 4.1/2 Test purpose Conference creation with a conferen
28、ce URI. Conference event package 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). In addition the conference participant subscribes to the conference event package and
29、 receives a NOTIFY request describing the conference status. SIP header values: INVITE: Request URI indicating the 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
30、 URI Event header contains “conference“ NOTIFY: Event contains conference; Subscription-State contains active; expires=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 App
31、ly post test routine ETSI ETSI TS 186 010-2 V3.2.1 (2015-10)10 TSS ConferenceFocus/CreateConf TP CONF_N01_004 Reference 5.3.2.3.2 2 Selection expression PICS 4.1/2 Test purpose Conference creation with a conference URI. Conference event package not subscribed. Ensure that a conference can be created
32、 by a UE using the conference URI. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant does not subscribe to the conference event package. SIP header values: INVITE: Request URI indicating the conference URI 200 OK: “isfocus“ fea
33、ture parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus INVITE barb4right 200 OK (INVITE) barb4left ACK barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_005 Reference 5.3.2.3.1 2 Selection expression PIC
34、S 4.1/2 AND PICS 4.3/4 Test purpose Conference creation with a conference factory URI. Preconditions indicated 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
35、UE. The “isfocus“ feature parameter indicated in Contact header is received in the 200 OK (INVITE). SIP header 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 conf
36、erence URI contained in the Contact header field SDP a=curr:qos local none a=curr:qos remote none a=des:qos 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:qo
37、s mandatory remote sendrecv 200 OK UPDATE SDP a=curr:qos local sendrecv a=curr:qos remote sendrecv a=des:qos 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 ETSI ETS
38、I TS 186 010-2 V3.2.1 (2015-10)11 Comments: ISC#1 Focus INVITE barb4right 183 Session Progress barb4left PRACK barb4right 200 OK PRACK barb4left UPDATE barb4right 200 OK UPDATE barb4left 200 OK (INVITE) barb4left ACK barb4right Apply post test routine TSS ConferenceFocus/CreateConf TP CONF_N01_006 R
39、eference 5.3.2.3.1 2 Selection expression PICS 4.1/2 Test purpose Conference creation with a conference factory URI not allocated in the focus, unsuccessful. 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 f
40、ocus with a 488 Not Acceptable Here final response. SIP header values: INVITE: Request URI indicating a conference factory URI not allocated in the focus Comments: ISC#1 Focus INVITE barb4right 488 Not Acceptable Here barb4left ACK barb4right 5.2.1.2 Joining a conference TSS ConferenceFocus/JoinConf
41、 TP CONF_N02_001 Reference 5.3.2.4.1 2 Selection expression PICS 4.1/2 Test purpose Participant dial-in 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 U
42、RI 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 hea
43、der field Comments: ISC#1 Focus ISC#2 Conference creation INVITE barb4right INVITE 200 OK (INVITE) barb4left 200 OK (INVITE) ACK barb4right ACK UE#2 joining in the conference INVITE barb4left INVITE 2 18x barb4right 18x 200 OK INVITE barb4right 200 OK INVITE ACK barb4left ACK Apply post test routine
44、 ETSI ETSI TS 186 010-2 V3.2.1 (2015-10)12 TSS ConferenceFocus/JoinConf TP CONF_N02_002 Reference 5.3.2.4.1 2 Selection expression PICS 4.1/2 Test purpose Participant dial-in the conference, the conference URI is not allocated, the request is rejected. UE2 (via ISC#2) tries to join in a conference b
45、ut the conference URI in the INVITE request is not allocated at the focus. The request is rejected with the final response 4xx. SIP header values: INVITE: Request URI contained the conference URI not allocated in the focus (PIXIT) Comments: ISC#1 Focus ISC#2 UE#2 joining in the conference INVITE bar
46、b4left INVITE 2 4xx barb4right 4xx ACK barb4left ACK 5.2.1.3 Inviting other users to a conference TSS ConferenceFocus/InviteToConf TP CONF_N03_001 Reference 5.3.2.5.2, 5.3.2.5.4 2 Selection expression PICS 4.1/2 AND NOT PICS 4.3/3 Test purpose Inviting participant by sending REFER to the focus. UE1
47、(via ISC#1) established a conference and invites UE2 (connected via ISC#2) to join into the conference. UE1 sends a REFER to the focus; the focus sends an INVITE request to UE2 to invite it to the conference. SIP header values: REFER: Request URI indicating the conference URI Refer-To contains the U
48、RI of UE2, method=INVITE Referred-By contains SIP URI of UE1 INVITE 2: Request URI indicating the address of UE2 The P-Asserted-Identity contains the conference URI. conference URI and “isfocus“ feature parameter indicated in Contact header field Referred-By contains SIP or tel URI of UE1 NOTIFY 1 E
49、vent contains refer; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains refer; Subscription-State contains terminated message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 Focus ISC#2 Conference creation INVITE barb4right INVITE 200 OK (INVITE) barb4left 200 OK (INVITE) ACK barb4right ACK UE#1 invites UE#2 to the conference REFER barb4right REFER 202 Accepted barb4left 202 Accepted Focus dials out to invite UE#2 INVITE 2 barb4right INVITE NOTIFY barb4left NO
