ETSI TS 101 588-2-2018 Core Network and Interoperability Testing (INT) Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) usyst.pdf

《ETSI TS 101 588-2-2018 Core Network and Interoperability Testing (INT) Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) usyst.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 588-2-2018 Core Network and Interoperability Testing (INT) Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) usyst.pdf（117页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 588-2 V6.1.1 (2018-07) Core Network and Interoperability Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP Release 12); Part

2、 2: Test Suite Structure and Test Purposes (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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no inve

3、stigation, 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. Trademarks The present docume

4、nt may include trademarks and/or tradenames which are asserted and/or registered by their 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 i

5、n the present document does not constitute an endorsement by ETSI of products, services 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

6、 part 2 of a multi-part deliverable covering Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification, as identified below: Part 1: “Protocol Implementation Conforma

7、nce Statement (PICS)“; Part 2: “Test Suite Structure and Test Purposes (TSS Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protoco

8、l specification (3GPP TS 24.642 Release 12)“. 2 ETSI TS 101 588-1: “Core Network and Interoperability Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Speci

9、fication (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 the cited version applies. F

10、or 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 referenced documents are not necessary

11、 for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 124 642 1 apply. ETSI ETSI TS

12、101 588-2 V6.1.1 (2018-07)6 3.2 Symbols For the purposes of the present document, the symbols given in ETSI TS 124 642 1 apply. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 124 642 1 apply. 4 Test Suite Structure (TSS) 4.0 Table of Test Suite Structu

13、re Table 4-1: Test Suite Structure CC originating_AS Invocation CC_N01_xxx Revocation CC_N02_xxxOperation CC_N03_xxxterminating_AS possibleIndication CC_N04_xxxInvocation CC_N05_xxx Revocation CC_N06_xxxCCOperation CC_N07_xxxInteraction TIR CC_N08_xxxCDIV CC_N09_xxx 4.1 Configuration The scope of th

14、e present document is to test the signalling and procedural aspects of the stage 3 requirements as described in 1. The stage 3 description respects the requirements to several network entities and to requirements regarding to end devices. Therefore, several interfaces (reference points) are addresse

15、d to satisfy the test of the different entities. Therefore, to test the appropriate entities the configurations below are applicable: Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the appropriate access point. Figure 4-1 points to th

16、is. Figure 4-1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (consider figure 4-2). In case only the Gm interface is accessible this shall be used instead. In this case,

17、 be aware that the verification of several requirements is impeded. ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)7 Figure 4-2: Applicable interfaces to test using the (generic) NNI interface Testing of User Equipment: There are several requirements regarding to the end devices. Therefore, a special config

18、uration appears. Figure 4-3: Applicable configuration to test the User Equipment 5 Test Purposes (TP) 5.1 Introduction 5.1.0 General treatment For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, starting at 001, within each group. Groups are organized according to

19、 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). ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)8 Table 5-1: TP identifier naming convention scheme Identifier: _ = supplementary service: e.g. “CC“ = type of IUT: U

20、User - equipment N Network = group 2 digit field representing group reference according to TSS = sequential number (001 to 999) 5.1.2 Test strategy As the base standard ETSI TS 124 642 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base stan

21、dard and the PICS specification ETSI TS 101 588-1 2. The criteria applied include the following: whether or not a test case can be built from the TP is not considered. 5.2 Actions at the originating AS 5.2.1 CC Invocation TSS CC/originating_AS/Invocation TP CC_N01_001 Reference 4.5.4.2.1.1.1, 4.5.4.

22、2.1.1.3 Selection expression PICS 4.7.1/9 Test purpose Detecting CCNL is possible. Ensure that when an originating user establishes a session to a terminating user not logged in, a 183 (Session Progress) response is forwarded to the originating user if a 480 (Temporarily Unavailable) response has be

23、en received. The Application Server provides an announcement. Preconditions: SIP header values: 480 Temporarily Unavailable Call-Info: ;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 480 (Temporarily Unavailable) 183 Session Progress g205 g206 ACK Anno

24、uncement that CC is possible Apply post test routine ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)9 TSS CC/originating_AS/Invocation TP CC_N01_002 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression Test purpose Detecting CCBS is possible. Ensure that when an originating user establishes a session

25、 to a terminating user is busy, a 183 (Session Progress) response is forwarded to the originating user if a 486 (Busy Here) response has been received. The Application Server provides an announcement. Preconditions: SIP header values: 486 Busy Here: Call-Info: ;purpose=call-completion;m=BS Comments:

26、 SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 486 (Busy Here) 183 Session Progress g205 g206 ACK Announcement that CC is possible Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_003 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression Test purpose Detecting CCNR

27、is possible. Ensure that when an originating user establishes a session to a terminating user is busy, a 183 (Session Progress) response is forwarded to the originating user if a 180 (Ringing) response has been received. The Application Server provides an announcement. The Call-Info header is remove

28、d from the 180 (Ringing) sent to the originating user. Preconditions: SIP header values: 180 Ringing 1 Call-Info: ;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 180 (Ringing) 1 180 (Ringing) g205 Start CCNR-T5 Timeout CCNR-T5 Announcement that CC is p

29、ossible Apply post test routine ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)10 TSS CC/originating_AS/Invocation TP CC_N01_004 Reference 4.5.4.2.1.1.3 Selection expression PICS 4.7.1/9 Test purpose CCNL is possible hence not confirmed. Ensure that when the originating user does not confirm the CCNL indica

30、tion to invoke the service a 486 (Busy Here) is forwarded to the originating user when Retention timer CC-T1 is expired. Preconditions: SIP header values: 480 Temporarily Unavailable 1 Call-Info: ;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 480 (Tem

31、porarily Unavailable) 1 183 Session Progress g205 Start CC-T1 g206 ACK Announcement that CC is possible 480 (Temporarily Unavailable) g205 Timeout CC-T1 ACK g206 Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_005 Reference 4.5.4.2.1.1.3 Selection expression Test purpose CCBS is p

32、ossible hence not confirmed. Ensure that when the originating user does not confirm the CCBS indication to invoke the service a 486 (Busy Here) is forwarded to the originating user when Retention timer CC-T1 is expired. Preconditions: SIP header values: 486 Busy Here: Call-Info: ;purpose=call-comple

33、tion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 486 (Busy Here) 183 Session Progress g205 Start CC-T1 g206 ACK Announcement that CC is possible 486 (Busy Here) g205 Timeout CC-T1 ACK g206 Apply post test routine ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)11 TSS CC/originating

34、_AS/Invocation TP CC_N01_006 Reference 4.5.4.2.1.1.3 Selection expression Test purpose CCNR is possible hence not confirmed. Ensure that when the originating user does not confirm the CCBS indication to invoke the service a 199 (Early Dialog Terminated) is forwarded to the originating user when Rete

35、ntion timer CC-T1 is expired. Preconditions: SIP header values: 180 Ringing 1 Call-Info: ;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 180 (Ringing) 1 180 (Ringing) g205 Start CCNR-T5, CC-T1 Timeout CCNR-T5 Announcement that CC is possible Timeout CC

36、-T1 199 (Early Dialog Terminated) g205 Apply post test routine ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)12 TSS CC/originating_AS/Invocation TP CC_N01_007 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression NOT PICS 4.7.1/10 AND NOT PICS 4.7.1/11 Test purpose Successful CCBS request. A 486 (Bus

37、y Here) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the AS withholds the 486 and sends a 183 Session Progress and starts to play an announcement to inform the originating user that Ca

38、ll Completion is possible. The originating user activates via inband interaction the CCBS call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server conf

39、irms the successful invocation to the originating user by sending of a 486 (Busy Here) final response. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: ;purpose=call-completion;m=BS SUBSCRIBE sip: T-AS;m=BS From: To: Contact: Call.Info: ; purpose=call-completion;m=BS P-Assertd-Identity:

40、 UE-A Expires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 486 (Busy Here) 1 183 Session Progress g205 g206 ACK Announcement that CCBS is possible Inband-interact

41、ion procedures for the CC activation g206 SUBSCRIBE g205 200 OK SUBCSRIBE g205 NOTIFY g206 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) 2 g205 ACK g206 Apply post test routine ETSI ETSI TS 101 588-2 V6.1.1 (2018-07)13 TSS CC/originating_AS/Invocation TP CC_N

42、01_008 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression PICS 4.7.1/10 AND PICS 4.7.1/11 Test purpose Successful CCBS request. A 486 (Busy Here) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to

43、BS. Ensure that the AS withholds the 486 and sends a 183 Session Progress and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCBS call completion service. Ensure that the AS sends a SUBSCRIBE t

44、o the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server confirms the successful invocation to the originating user by sending of a 486 (Busy Here) final response. Ensure that a Date header and a Content-Type heade

45、r containing a message/external-body value are present in the 486 sent to the originating user. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: ;purpose=call-completion;m=BS SUBSCRIBE sip: T-AS;m=BS From: To: Contact: Call.Info: ; purpose=call-completion;m=BS P-Assertd-Identity: UE-A E

46、xpires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued 486 Busy Here 2: Date: Content-Type: message/external-body; access-type=”URL”; URL= Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE g206 g206 INVITE g205 486 (Busy Here) 1 183 Sess

47、ion Progress g205 g206 ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation g206 SUBSCRIBE g205 200 OK SUBCSRIBE g205 NOTIFY g206 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) 2 g205 ACK g206 Apply post test routine ETSI

48、ETSI TS 101 588-2 V6.1.1 (2018-07)14 TSS CC/originating_AS/Invocation TP CC_N01_009 Reference 4.5.4.2.1.1.1 Selection expression Test purpose CCBS not possible, A CC queue limit has been exceeded. Ensure that the AS does not offer the activation of the call completion service if the user A CCBS queu

49、e limit has been exceeded. The 486 is passed through. Preconditions: CCBS queue limit exceeded SIP header values: 486 Busy Here: Call-Info: ;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Set the A queue to limit INVITE g206 g206 INVITE 100 Trying g205 g205 100 Trying 486 (Busy Here) g205 g205 486 (Busy Here) ACK g206 g206 ACK TSS CC/originating_AS/Invocation TP CC_N01_010 Reference 4.5.4.2.1.1.1 Selection expression NOT PICS 4.7.1/3 Test purpose CCBS invocation not possible, further identical request (communication parameters). Ensure t