1、 ETSI TS 186 018-2 V2.1.1 (2009-07)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);PSTN/ISDN simulation services;Malicious Communication Identification (MCID);Part 2: Test Suite Structure and Test Purposes (TSS Essential, or po
2、tentially 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, including IPR searches, has been carrie
3、d 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 Specification (TS) has been produced by ETSI Technical
4、Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2 of a multi-part deliverable covering the Malicious Communication Identification (MCID) service, related to PSTN/ISDN simulation services, as identified below: P
5、art 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 Testing (PIXIT) proforma specification“. ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)51 Scope Th
6、e present document specifies the test suite structure and test purposes of the Malicious Communication Identification (MCID) service based on the stage three of IMS MCID simulation service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Con
7、trol Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The MCID service will store session related information independent of the service requested. 2 References References are either specific (identified by date of publication and/or edition number or versi
8、on 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 accepted that it will be possible to use all future changes of the referenced document
9、 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. NOTE: While any hyperlinks included in this clause were valid at the time of public
10、ation 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 cited applies. For non-specific references, the latest edition of the referenced doc
11、ument (including any amendments) applies. 1 ETSI TS 183 016: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol Specification“. 2 ETSI TS 186 018-1: “Telecommunicat
12、ions and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 1: Protocol Implementation Conformance Statement (PICS)“. 3 ETSI TS 181 002: “Telecommunications and Internet converged Services and
13、 Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services“. 4 ETSI TS 181 006: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description Endorsement of OMA-ER
14、ELD-PoC-V1“. 5 ETSI TR 180 000: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology“. ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)62.2 Informative references The following referenced documents are not essential to the use of the present docu
15、ment but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 IETF RFC 3966: “The tel URI for Telephone Numbers“. i.2 IETF RFC 3986: “Uniform Resource Identifier (URI): Generi
16、c Syntax“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 181 002 3, TS 181 006 4, TR 180 000 5 and the following apply: communication information: information collected and registered by the MCID service identity infor
17、mation: includes all the information identifying a user, including trusted (network generated) and/or untrusted (user generated) identities NOTE: See RFC 3966 i.1 / RFC 3986 i.2. trusted identity: network generated user address information untrusted identity: user generated user address information
18、NOTE: This may contain additional information. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Application Server ID user IDentification IM IP Multimedia IMS IP Multimedia Subsystem IP Internet Protocol ISC IP multimedia subsystem Service Control ISD
19、N Integrated Services Digital Network MCID Malicious Call Identification MIME Multipurpose Internet Mail Extensions NGN Next Generation Network NNI Network Network Interface PSTN Public Switched Telephone Network S-CSCF Service - Call Session Control Function SDP Session Description Protocol SIP Ses
20、sion Initiation Protocol TP Test Purposes TSS Test Suite Structure UE User EquipmentURI Uniform Resource Identifier XML eXtensible Markup LanguageETSI ETSI TS 186 018-2 V2.1.1 (2009-07)74 Test Suite Structure (TSS) MCID terminating_S-CSCF MCID_N01_xxx terminating_AS CID_N02_xxxdestination_UE MCID_U0
21、1_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 TS 183 016 1. The stage 3 description describes the requirements for several network entities and also the requirements regarding for terminal de
22、vices. 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. 4.1.1 Testing of the AS The AS entity is responsible for performing and managing services. The ISC i
23、nterface is the appropriate access point for testing. Figure 1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also possible to perform the tests of the AS using any NNI (Mw, Mg, Mx) interface (see figure 2). In case only the Gm interface is accessible t
24、his interface can be used instead for testing, but the verification of all requirements may not be possible. CSCF(and/or AS)Implementation under TestTest SystemTest SystemMw, Mg, MxMw, Mg, MxFigure 2: Applicable interfaces for tests using a (generic) NNI interface ETSI ETSI TS 186 018-2 V2.1.1 (2009
25、-07)84.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 test configuration below has been chosen. User EquipmentImplementation under TestTest SystemGmFigure 3: Applicable con
26、figuration to test UE functionalities 4.1.3 Testing of the S-CSCF This entity is responsible for handling the initial filter criteria and for passing messages to the relevant AS. For testing both the Mw and the ISC interface are involved. S-CSCFImplementation under TestTest SystemTest SystemMw ISC F
27、igure 4: Applicable interfaces to test S-CSCF functionalities If the either the ISC or the Mw interface is not accessible, it is also possible to perform the test of the S-CSCF using any NNI (Mw, Mg, Mx) interface (see figure 4). In case only the Gm interface is accessible this interface can be used
28、 instead for testing, but the verification of all requirements may not be possible. CSCF(and/or AS)Implementation under TestTest SystemTest SystemMw, Mg, MxMw, Mg, MxFigure 5: Applicable interfaces for tests using a (generic) NNI interface ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)95 Test Purposes (TP)
29、 5.1 Introduction 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 the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user
30、 (see table 1). Table 1: TP identifier naming convention scheme Identifier: _ = supplementary service: e.g. “MCID“ = type of IUT: U User equipment N Network entity= group 2 digit field representing group reference according to TSS = sequential number (001-999) 5.1.2 Test strategy As the base standar
31、d TS 183 016 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 TS 186 018-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 TPs f
32、or Malicious Communication Identification (MCID) 5.2.1 Actions at the terminating S-CSCF TSS MCID/terminating_S-CSCF TP MCID_N01_001 MCID reference clause 4.5.2.4 Selection expression PICS 1/3 Test purpose Ensure that the S-CSCF forwards the INVITE request to the AS if the called subscriber has a pe
33、rmanent MCID subscription. Preconditions: Called user has MCID subscription with mode permanent SIP header values: Comments: Test equipment (Mw) S-CSCF Test equipment (ISC, Mw) INVITE barb4right barb4right INVITE ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)10TSS MCID/terminating_S-CSCF TP MCID_N01_002 MC
34、ID reference clause 4.5.2.4 Selection expression PICS 1/4 Test purpose Ensure that the S-CSCF forwards the Re-INVITE requesting MCID to the AS if the called subscriber has a case by case MCID subscription. Preconditions: Called user has MCID subscription with mode temporary SIP header values: Re-INV
35、ITE without session modification Comments: Test equipment (Mw) S-CSCF Test equipment (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 180 Ringing barb4left barb4left 180 Ringing 200 OK INVITE barb4left barb4left 200 OK INVITE ACK barb4right barb4right ACK Re-INVITE
36、 barb4left barb4left Re-INVITE 200 OK INVITE barb4right barb4right 200 OK INVITE TSS MCID/terminating_S-CSCF TP MCID_N01_003 MCID reference clause 4.5.2.5.2 Selection expression PICS 1/4 AND PICS 1/5 Test purpose Ensure that the S-CSCF forwards the Re-INVITE requesting MCID to the AS if the called s
37、ubscriber has a case by case MCID subscription. A XML MIME body is received indicating MCID request. Preconditions: Called user has MCID subscription with mode temporary SIP header values: Re-INVITE without session modification XML mcid requestMcidRequestIndicator = 1 Comments: Test equipment (Mw) S
38、-CSCF Test equipment (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 180 Ringing barb4left barb4left 180 Ringing 200 OK INVITE barb4left barb4left 200 OK INVITE ACK barb4right barb4right ACK Re-INVITE barb4left barb4left Re-INVITE 200 OK INVITE barb4right barb4rig
39、ht 200 OK INVITE 5.2.2 Actions at the AS of the terminating user TSS MCID/terminating_AS TP MCID_N02_001 MCID reference clause 4.5.2.5 Selection expression Test purpose If the INVITE request does not contain the information of the originating party, the AS shall send an INFO Message containing a XML
40、 mcid body with MCID XML Request schema requesting the originating ID. Preconditions: Called user has MCID subscription SIP header values: INFO XML mcid requestMcidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left bar
41、b4left 100 Trying INFO (MIME body) barb4left 200 OK INFO barb4right ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)11TSS MCID/terminating_AS TP MCID_N02_002 MCID reference clause 4.5.2.5.3 Selection expression PICS 1/4 Test purpose The AS holds the call state after a BYE from the originating UE Ensure that
42、the AS holds the call state while TMCID-BYEis running, if MCID was requested by the called user. When TMCID-BYEis expired, the BYE is forwarded to the terminating UE. Preconditions: Called user has MCID subscription with mode temporary SIP header values: Comments: Test equipment (ISC) AS Test equipm
43、ent (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 180 Ringing barb4left barb4left 180 Ringing 200 OK INVITE barb4left barb4left 200 OK INVITE ACK barb4right barb4right ACK BYE barb4right TMCID-BYEstarted 200 OK BYE barb4left TMCID-BYEexpires barb4right BYE barb4
44、left 200 OK BYE TSS MCID/terminating_AS TP MCID_N02_003 MCID reference clause 4.5.2.2 Selection expression PICS 1/4 Test purpose The AS holds the call state after a BYE from the originating UE in the confirmed dialogue Ensure that the AS holds the call state while TMCID-BYEis running. If a reINVITE
45、to invoke the MCID service was received while TMCID-BYEis running, ensure that the BYE is forwarded to the terminating UE. Preconditions: Called user has MCID subscription with mode temporary SIP header values: reINVITE without session modification Comments: Test equipment (ISC) AS Test equipment (I
46、SC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying 180 Ringing barb4left barb4left 180 Ringing 200 OK INVITE barb4left barb4left 200 OK INVITE ACK barb4right barb4right ACK BYE barb4right TMCID-BYEstarted 200 OK BYE barb4left barb4left Re-INVITE requesting MCID barb4ri
47、ght 200 OK INVITE barb4left ACK TMCID-BYEexpires barb4right BYE barb4left 200 OK BYE ETSI ETSI TS 186 018-2 V2.1.1 (2009-07)12TSS MCID/terminating_AS TP MCID_N02_004 MCID reference clause 4.5.2.5.3 Selection expression PICS 1/8 Test purpose Ensure that the AS, having sent an INFO message containing
48、a XML mcid body with MCID XML Request schema requesting the originating ID, on receipt of an INFO message containing a XML mcid body with MCID XML Response schema and the originating identity, passes on the 180 Ringing from the called user. Preconditions: Called user has MCID subscription SIP header
49、 values: INFO1 XML mcidrequest McidRequestIndicator = 1 INFO2 P-Asserted-Identity XML mcidResponse McidResponseIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (ISC) INVITE barb4right barb4right INVITE 100 Trying barb4left barb4left 100 Trying INFO1 (MIME body) barb4left TO-IDstarted 200 OK INFO barb4right barb4left 180 Ringing INFO2 (MIME body) barb4right 200 OK INFO barb4left TO-IDstopped 180 Ringing barb4left TSS MCID/terminating_AS TP MCID_N02_004 MCID reference clause 4.5.2.5.3 Selection expression PICS 1/8 Test purpose Ensure
