1、 ETSI TS 186 021-2 V2.1.1 (2009-07)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);PSTN/ISDN simulation services;Completion of Communications to Busy Subscriber (CCBS)Completion of Communications by No Reply (CCNR);Part 2: Test
2、 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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, n
3、o 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 Technical
4、 Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2 of a multi-part deliverable covering test suite structure and test purposes for the Completion of Commun
5、ications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR), 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 I
6、nformation for Testing (PIXIT) proforma specification“. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)51 Scope The present document specifies the test suite structure and test purposes of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCN
7、R) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). 2 References References are
8、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. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accep
9、ted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NO
10、TE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cit
11、ed applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TS 183 042 (V2.1.1): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Simulation Services; Completion of Comm
12、unications to Busy Subscriber (CCBS), Completion of Communications by No Reply (CCNR); Protocol Specification“. 2 ETSI TS 186 021-1: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Completion of Communications to Busy
13、 Subscriber (CCBS) Completion of Communications by No Reply (CCNR); Part 1: Protocol Implementation Conformance Statement (PICS)“. 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular s
14、ubject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)63 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions give
15、n in 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 1 apply. 4 Test Suite Structure (TSS) CC originating_AS Invocation CC_N01_xxx Revocation CC_N02_xxxOperation CC_N03_xxxterminating_AS possibleIndication CC_N04_xxxInvocation CC_N05_xxx Revocation CC_
16、N06_xxxCCOperation CC_N07_xxxInteraction CDIV CC_N08_xxx4.1 Configuration The scope of the current specification 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 also to r
17、equirements regarding to end devices. Therefore several interfaces (reference points) are addressed 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 perf
18、orm the service. Hence the ISC interface is the appropriate access point. Figure 1 points to this. Figure 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 figur
19、e 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)7CSCF(and/or AS)Implementation under TestTest SystemTest SystemMw, Mg, MxMw, Mg, MxFigure 2: Applicabl
20、e interfaces to test using the (generic) NNI interface Figure 3 illustrates the usage of any NNI interface. Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special configuration appears. User EquipmentImplementation under TestTest SystemGmFigure 3:
21、 Applicable configuration to test the User Equipment Testing of the IBCF functionality: The IBCF is the division between the trusted and the untrusted networks. Figure 3: Applicable configuration to test the IBCF If the Mx interface is not accessible it is also applicable to perform the test of the
22、IBCF using any NNI (Mw, Mg, Mx) interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)85 Test Purposes (TP) 5.1 Introduction For ea
23、ch 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 the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1:
24、 TP identifier naming convention scheme Identifier: _ = supplementary service: e.g. “CC“ = type of IUT: U 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 TS 183 042 1 contains no
25、explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 021-1 2. The criteria applied include the following: whether or not a test case can be built from the TP is not considered. ETSI ETSI TS 186 021-2 V2.1.1 (2009-
26、07)95.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 Selection expression 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
27、 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 Call Completion is possible. The originating user activates via inband interaction the CCBS call completion
28、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. Preconditions: SIP header values: 486 Busy Here: Call-Info: ;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From: To: Contact: E
29、vent:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying barb4left 486 (Busy Here) 183 Session Progress barb
30、4left barb4right ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation barb4right SUBSCRIBE barb4left 202 Accepted barb4left NOTIFY barb4right 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) barb4left ACK barb4right Apply po
31、st test routine TSS CC/originating_AS/Invocation TP CC_N01_002 Reference 4.5.4.2.1 Selection expression Test purpose CCBS not possible, no CCBS indication received. A 486 (Busy Here) is received from the terminating user containing and no Call-Info header field is contained. The originating AS does
32、not starts announcement to provide the activation of the call completion service and pass thru the 486 response. Preconditions: SIP header values: 486 Busy Here: Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 486 (Busy Here) barb4l
33、eft barb4left 486 (Busy Here) ACK barb4right barb4right ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)10TSS CC/originating_AS/Invocation TP CC_N01_003 Reference 4.5.4.2.1 Selection expression Test purpose CCBS not possible, A CC queue limit has been exceeded. Ensure that the AS does not offer the activ
34、ation of the call completion service if the user A CCBS queue limit has been exceeded. The 486 is passed thru. Preconditions: CCBS queue limit exceeded SIP header values: 486 Busy Here: Call-Info: ;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the A queue to limit INVITE bar
35、b4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 486 (Busy Here) barb4left barb4left 486 (Busy Here) ACK barb4right barb4right ACK TSS CC/originating_AS/Invocation TP CC_N01_004 Reference 4.5.4.2.1 Selection expression PICS 1/3 Test purpose CCBS not possible, further identical req
36、uest (communication parameters). Ensure that the AS does not offer the activation of the CCBS call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 486 Busy Here: Call-Info: ;purp
37、ose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke a successful CCBS request INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 486 (Busy Here) barb4left barb4left 486 (Busy Here) ACK barb4right barb4right ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)11TSS
38、 CC/originating_AS/Invocation TP CC_N01_005 Reference 4.5.4.2.1 Selection expression Test purpose CCNR successful request. A 180 (Ringing) 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
39、the sends a 180 (Ringing) without the Call-Info header and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCNR call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating A
40、S. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. Preconditions: SIP header values: 180 Ringing 2: Call-Info: ;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From: To: Contact: Event:call-completion NOTIFY sip:O-AS Event:call-completion Content
41、-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying barb4left 180 Ringing 1 180 Ringing 2 barb4left Announcement that CCNR is possible Inband-interaction procedures for
42、the CC activation barb4right SUBSCRIBE barb4left 202 Accepted barb4left NOTIFY barb4right 200 OK NOTIFY Confirm to the caller that the invocation was successful CANCEL barb4right barb4right CANCEL 200 OK CANCEL barb4left barb4left 200 OK CANCEL 487 Request Terminated barb4left barb4left 487 Request
43、Terminated ACK barb4right barb4right ACK Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_006 Reference 4.5.4.2.1 Selection expression Test purpose CCNR not possible, no CCBS indication received. Ensure that the originating AS does not offer the call completion service if a 180 (Ri
44、nging) is received and a Call-Info header is not present. The 180 (Ringing) is passed unchanged. Preconditions: SIP header values: Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying barb4left 180 Ringing 180 Ringing barb4left CANCEL ba
45、rb4right barb4right CANCEL 200 OK CANCEL barb4left barb4left 200 OK CANCEL 487 Request Terminated barb4left barb4left 487 Request Terminated ACK barb4right barb4right ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07)12TSS CC/originating_AS/Invocation TP CC_N01_007 Reference 4.5.4.2.1 Selection expression
46、Test purpose CCNR not possible, A CC queue limit has been exceeded. Ensure that the originating AS does not offered the call completion service if a 180 (Ringing) is received and a Call-Info header with a purpose parameter set to call-completion and a m parameter set to NR is received and the CCBS q
47、ueue limit is exceeded. Preconditions: CCBS queue limit exceeded SIP header values: 180 Ringing 2: Call-Info: ;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the A queue to limit INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying barb4left 180 Ringi
48、ng 1 180 Ringing 2 barb4left CANCEL barb4right barb4right CANCEL 200 OK CANCEL barb4left barb4left 200 OK CANCEL 487 Request Terminated barb4left barb4left 487 Request Terminated ACK barb4right barb4right ACK TSS CC/originating_AS/Invocation TP CC_N01_008 Reference 4.5.4.2.1 Selection expression PIC
49、S 1/3 Test purpose CCNR not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCNR call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 180 Ringing 1: Call-Info: ;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Successful CCNR request INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying barb4left 180 Ringing 1 180 Ringing 2 barb4left
