hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
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 5.1.1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "TIP" <iut> = type of IUT: U User N Network entity, e.g. P-CSCF <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999) ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 9 5.2 TPs for Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)
|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.2.1 Actions at the originating UE
|
TSS User/OrigUserE TP TIP_U01_001 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 Test purpose: The originating UE receives one P-Asserted-Identity in a sip URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing a P-Asserted-Identity heeder with a valid sip URI accepts the call following the basic request handling procedures. SIP message: SIP_MESSAGE_VA P-Asserted-Identity: <sip:[any value]> Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA TSS User/OrigUserE TP TIP_U01_002 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 Test purpose: The originating UE receives one P-Asserted-Identity in a tel URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing a P-Asserted-Identity heeder with a valid tel URI, accepts the call following the basic request handling procedures. SIP message: SIP_MESSAGE_VA P-Asserted-Identity: <tel:[any value]> Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA TSS User/OrigUserE TP TIP_U01_003 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 Test purpose: The originating UE receives two P-Asserted-Identity headers in a sip URI and a tel URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing one P-Asserted-Identity header with a valid sip URI and one P-Asserted-Identity header with a valid tel URI, accepts the call following the basic request handling procedures. SIP message: SIP_MESSAGE_VA P-Asserted-Identity: <sip:[any value]> P-Asserted-Identity: <tel:[any value]> Comments: User equipment UA S INVITE SIP_MESSAGE_VA ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 10 TSS User/OrigUserE TP TIP_U01_004 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 Test purpose: The originating UE receives a Privacy header field value 'id' indicating the TIR service. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA with a Privacy header with privacy type of "id" and without P-Asserted-Identity headers, accepts the call following the basic request handling procedures. SIP message: SIP_MESSAGE_VA Privacy: id Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA Values for tests purposes TIP_U01_001 to TIP_U02_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK TSS User/OrigUserE TP TIP_U01_005 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose: The originating user is able to send the "from-change" tag in the Supported header in the initial INVITE. Ensure that the Originating UE sends a "from-change" tag in the Supported header in the initial INVITE. SIP message: INVITE Supported "from-change" Comments: User equipment Test equipment INVITE with "from-change" tag TSS Syntax/OrigUserE TP TIP_U01_006 TIP/TIR reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose: The originating user is able to receive a connected identity in the From header of an UPDATE request. Ensure that the Originating UE is able to receive a second identity in the From header of an UPDATE request if the UE indicates the support of this procedure by sending the "from-change" tag in the Supported header in the initial INVITE and this identity is displayed to the user. SIP message: INVITE Supported "from-change" UPDATE From <second identity> Comments: User equipment SUT Test equipment INVITE with "from-change" tag 180 Ringing 200 OK INVITE ACK UPDATE with new URI in From header 200 OK UPDATE ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 11
|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.2.2 Actions at the AS serving the originating UE
|
TSS Signalling/OrigNetw TP TIP_N01_001 TIP/TIR reference 4.3.2 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user subscribes to the TIP service. Ensure that for originating users that subscribe to TIP simulation service, if network provided identity information about the terminator is available, and if presentation is not restricted, the AS shall pass that information in any non 100 response message defined as SIP_MESSAGE_VA. Precondition: The originating user has subscribed to the TIP service SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity SIP_MESSAGE_VA2: P-Asserted-Identity Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 TSS Network entity/OrigNetw TP TIP_N01_002 TIP/TIR reference 4.5.2.4 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user does not subscribe to the TIP service P-Asserted-Identity header not present. Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes any P-Asserted-Identity header fields included in the SIP response defined as SIP_MESSAGE_VA before forwarding the response. Precondition: The originating user has not subscribed to the TIP service SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity SIP_MESSAGE_VA2: P-Asserted-Identity not present Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 TSS Network entity/OrigNetw TP TIP_N01_003 TIP/TIR reference 4.5.2.4 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user does not subscribe to the TIP service Privacy header not present. Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes any Privacy header fields included in the SIP response defined as SIP_MESSAGE_VA before forwarding the response. Precondition: The originating user has not subscribed to the TIP service SIP messages: SIP_MESSAGE_VA1: Privacy: id SIP_MESSAGE_VA2: Privacy header not present Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 12 TSS Signalling/TIR TP TIP_N01_004 TIP/TIR reference 4.6.3 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 AND PICS 4.7.1/7 Test purpose: The originating user has TIR override category. Ensure that, if the originating user has the override category, the AS removes Privacy header fields restricting the presentation of the terminating identity and sends the P-Asserted-Identity header in the SIP response defined as SIP_MESSAGE_VA before forwarding the response. Precondition: The originating user has subscribed to the TIP service and Originating user has the override category SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity, Privacy = id SIP_MESSAGE_VA2: P-Asserted-Identity, no Privacy header or Privacy = none Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA2 SIP_MESSAGE_VA1 Values for tests purposes TIP_N01_001 to TIP_N02_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK TSS Network entity/OrigAS TP TIP_N01_005 TIP/TIR reference 4.5.2.4 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user subscribes to the TIP service. The "from-change" tag is passed on. Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service passes on the "from change" tag within the Supported header in a received initial INVITE request before forwarding the request. Precondition: The originating user has subscribed to the TIP service SIP message: INVITE1 Supported "from-change" INVITE2 Supported "from-change" Comments: Test equipment AS Test equipment INVITE1 with "from-change" tag INVITE2 with "from-change" tag TSS Network entity/OrigAS TP TIP_N01_006 TIP/TIR reference 4.5.2.4 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user subscribes to the TIP service. The "from-change" tag is not received. Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service, receiving an initial INVITE request without the "from-change" tag in the Supported header, does not insert the "from-change" tag into the Supported header before forwarding the request. Precondition: The originating user has subscribed to the TIP service SIP message: INVITE1 Supported "from-change" not included INVITE2 Supported "from-change" not included Comments: Test equipment AS Test equipment INVITE1 without "from-change" tag INVITE2 with "from-change" tag ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 13 TSS Network entity/OrigAS TP TIP_N01_007 TIP/TIR reference 4.5.2.4 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/3 Test purpose: The originating user does not subscribe to the TIP service. The "from-change" tag is removed from the Supported header. Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request. Precondition: The originating user has not subscribed to the TIP service SIP message: INVITE1 Supported "from-change" INVITE2 Supported "from-change" not included Comments: Test equipment AS Test equipment INVITE1 with "from-change" tag INVITE2
|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.2.3 Actions at the AS serving the terminating UE
|
TSS Network entity/DestAS TP TIP_N02_001 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/4 AND PICS 4.7.1/6 Test purpose: The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The terminating user subscribes to TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response. Precondition: The terminating user has subscribed to the TIR service in permanent mode SIP messages: SIP_MESSAGE_VA1 SIP_MESSAGE_VA2: Privacy: id Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 TSS Network entity/DestAS TP TIP_N02_002 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/4 AND PICS 4.7.1/6 Test purpose: The AS inserts the Privacy id value in the response if the response contains Privacy "none". The terminating user subscribes to TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA with a Privacy header "none", the AS shall remove the "none" and insert a Privacy header with privacy value "id" before forwarding the response. Precondition: The terminating user has subscribed to the TIR service in permanent mode SIP messages: SIP_MESSAGE_VA1 Privacy: none SIP_MESSAGE_VA2: Privacy: id Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 14 TSS Network entity/DestAS TP TIP_N02_003 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/4 AND PICS 4.7.1/5 Test purpose: The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The user subscribes TIR temporary mode with default "presentation restricted". Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "temporary mode" with default value "presentation restricted", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response. Precondition: The terminating user has subscribed to the TIR service in temporary mode "presentation restricted" SIP messages: SIP_MESSAGE_VA1 SIP_MESSAGE_VA2: Privacy: id Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA 2 SIP_MESSAGE_VA 1 TSS Network entity/DestAS TP TIP_N02_004 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/4 AND PICS 4.7.1/5 Test purpose: The AS passes the Privacy value 'id' in the response. The user subscribes TIR temporary mode with default "presentation not restricted". Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "temporary mode" with default value "presentation not restricted", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA with a Privacy header set to 'id', the AS shall pass Privacy header with the privacy value before forwarding the response. Precondition: The terminating user has subscribed to the TIR service in temporary mode "presentation not restricted" SIP messages: SIP_MESSAGE_VA1: Privacy: id SIP_MESSAGE_VA2: Privacy: id Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA SIP_MESSAGE_VA Values for tests purposes TIP_N02_001 to TIP_N01_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK TSS Network entity/DestAS TP TIP_N02_005 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/4 AND PICS 4.7.1/6 Test purpose: The AS remove the "from-change" tag from the Supported header. The user subscribes TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to the TIR service in "permanent mode" removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request. Precondition: The terminating user has subscribed to the TIR service in permanent mode SIP messages: INVITE1 Supported: "from-change" INVITE2 Supported without "from-change" Comments: Test equipment AS Test equipment INVITE1 with "from-change" tag INVITE2 without "from-change" tag ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 15 TSS Signalling/DestAS TP TIP_N02_006 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/8 Test purpose: The terminating user is not subscribed to the "no screening" special arrangement From header value does not match. Ensure that, if the IUT attempt to match the information in the From header with the set of registered public user identities for the served user and if no match is found, the AS changes the value of the From header in the UPDATE to the public user identity of the served user if the terminating user is not subscribed to the "no screening" special arrangement. SIP messages: INVITE: Supported: from-change UPDATE1: From <connected user identity> UPDATE2: From <public user identity> Precondition: Terminating user is not subscribed to the "no screening" special arrangement Comments: Test equipment AS Test equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK UPDATE2 UPDATE1 200 OK UPDATE 200 OK UPDATE TSS Signalling/DestAS TP TIP_N02_007 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/8 Test purpose: The terminating user is not subscribed to the "no screening" special arrangement From header value matches. Ensure that, if the IUT attempt to match the information in the From header with the set of registered public user identities for the served user and if a match is found, the AS passes the value of the From header in the UPDATE if the terminating user is not subscribed to the "no screening" special arrangement. SIP messages: INVITE: Supported: from-change 18x/200: Supported: from-change UPDATE1: From <public user identity> UPDATE2: From <public user identity> Precondition: Terminating user is not subscribed to the "no screening" special arrangement Comments: Test equipment AS Test equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK UPDATE2 UPDATE1 200 OK UPDATE 200 OK UPDATE ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 16 TSS Signalling/DestAS TP TIP_N02_008 TIP/TIR reference 4.5.2.9 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/8 Test purpose: The terminating user is subscribed to the "no screening" special arrangement. Ensure that, if the IUT passes the information in the From header in the UPDATE request if the terminating user is subscribed to the "no screening" special arrangement. SIP messages: INVITE: Supported: from-change 18x/200: Supported: from-change UPDATE1: From <connected user identity> UPDATE2: From <connected user identity> Precondition: Terminating user is subscribed to the "no screening" special arrangement Comments: Test equipment AS Test equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK UPDATE2 UPDATE1 200 OK UPDATE 200 OK UPDATE
|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.2.4 Actions at the terminating UE
|
TSS User/TermUserE TP TIP_U02_001 TIP/TIR reference 4.5.2.12 Selection expression PICS 4.5.1/2 AND PICS 4.6.1/1 Test purpose: The Terminating UE supports the "from-change" tag in the Supported header. Ensure that the Terminating UE supports the "from-change" tag in the Supported header. If the UE receives a "from-change" tag in a Supported header in an initial INVITE, the UE sends the "from-change" tag in the Supported header in any provisional or final response message (e.g. 180, 183, 200). SIP messages: INVITE: Supported: from-change SIP_MESSAGE_VA: Supported: from-change Comments: Test equipment User equipment INVITE with "from-change" tag SIP_MESSAGE_VA TSS User/TermUserE TP TIP_U02_002 TIP/TIR reference 4.5.2.12 Selection expression PICS 4.5.1/2 AND PICS 4.6.1/2 Test purpose: The Terminating UE sends an UPDATE request with an updated From and To header. Ensure that the Terminating UE supports the "from-change" tag in the Supported header. If the UE receives a "from-change" tag in a Supported header in an initial INVITE, the user equipment sends an UPDATE request after the ACK for the 200 OK INVITE was received containing a connected identity in the From header. SIP messages: INVITE: Supported: from-change 180/200: Supported: from-change UPDATE: From <identity user equipment> Comments: Test equipment User equipment INVITE with "from-change" tag 180 Ringing 200 OK INVITE ACK UPDATE with updated From and To header 200 OK UPDATE ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 17 TSS User/TermUserE TP TIP_U02_003 TIP/TIR reference 4.5.2.12 Selection expression PICS 4.5.1/2 Test purpose: The Terminating UE overrides a default "Presentation not restricted" by sending Privacy "id". Ensure that the Terminating UE having subscribed to TIR temporary mode, default value "presentation not restricted", to override the default TIR setting, sends a Privacy header with value "id" in any non 100 response message (e.g. 180, 183, 200). SIP messages: SIP_MESSAGE_VA: Privacy: "id" Comments: Test equipment User equipment INVITE SIP_MESSAGE_VA TSS User/TermUserE TP TIP_U02_004 TIP/TIR reference 4.5.2.12 Selection expression PICS 4.5.1/2 Test purpose: The Terminating UE overrides a default "Presentation restricted" by sending Privacy "none". Ensure that the Terminating UE having subscribed to TIR temporary mode, default value "presentation restricted", to override the default TIR setting, sends a Privacy header with value "none" in any non 100 response message (e.g. 180, 183, 200). SIP messages: SIP_MESSAGE_VA: Privacy: "none" Comments: Test equipment User equipment INVITE SIP_MESSAGE_VA Values for tests purposes TIP_U02_001 and TIP_U02_003 to TIP_U02_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 18
|
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.3 Interaction with other services
| |
c98c8c16b30ad1284cf64a54f8c7b3ea
|
101 596-2
|
5.3.1 Communication diversion services
|
TSS Interaction/CDIV TP TIP_N03_001 TIP/TIR reference 4.6.7 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/1 AND PICS 4.7.2/1 AND PICS 4.7.2/2 Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in permanent mode and the originating user has subscribed to the TIP service, no P-Asserted-Identity header including the URI of the diverted-to user and no history-entry identifying the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". SIP messages: 181: History-Info diverted-to URI not present SIP_MESSAGE_VA 2 History-Info diverted-to URI not present Privacy: id Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA 2 without P-Asserted-Identity SIP_MESSAGE_VA 1 TSS Interaction/CDIV TP TIP_N03_002 TIP/TIR reference 4.6.7 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/1 AND PICS 4.7.2/1 AND PICS 4.7.2/2 Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send no Privacy header within the SIP_MESSAGE_VA response, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". SIP messages: 181: History-Info diverted-to URI not present SIP_MESSAGE_VA 2 History-Info diverted-to URI not present Privacy: id Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA 2 without P-Asserted-Identity SIP_MESSAGE_VA 1 ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 19 TSS Interaction/CDIV TP TIP_N03_003 TIP/TIR reference 4.6.7 Selection expression PICS 4.5.1/3 AND PICS 4.7.1/1 AND PICS 4.7.2/1 AND PICS 4.7.2/2 Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation not restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send a Privacy header with value "id" within the SIP_MESSAGE_VA response, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". SIP messages: 181: History-Info diverted-to URI not present SIP_MESSAGE_VA 1 Privacy: id SIP_MESSAGE_VA 2 History-Info diverted-to URI not present Privacy: id Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA 2 without P-Asserted-Identity SIP_MESSAGE_VA 1 with Privacy "id" Values for tests purposes TIP_N03_001 to TIP_N03_003 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK ETSI ETSI TS 101 596-2 V5.1.1 (2012-10) 20 History Document history V5.1.1 October 2012 Publication
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
1 Scope
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10) defined in TS 124 608 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [2].
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
2 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. 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 http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 608: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)". [2] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [3] ISO/IEC 9646-1: "Information technology -- Open systems interconnection -- Conformance testing methodology and framework -- Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology -- Open systems interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". [5] ETSI TS 124 604: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 Release 10)".
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 6
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
3 Definitions, symbols and abbreviations
| |
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 608 [1], ETS 300 406 [2], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, API ICS, etc. ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
3.2 Symbols
|
For the purposes of the present document, the symbols given in TS 124 608 [1] apply.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 608 [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test PICS Protocol ICS SCS System Conformance Statement SUT System Under Test
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4 PICS proforma for TS 124 608
|
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.1 Guidance for completing the PICS proforma
| |
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.1.1 Purposes and structure
|
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in TS 124 608 [1] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of information: • guidance for completing the PICS proforma; • identification of the implementation; • identification of the TS 124 608 [1]; • global statement of conformance; • roles; ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 7 • user role: - major capabilities; • network role: - major capabilities; - CDIV capabilities.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.1.2 Abbreviations and conventions
|
The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Status column The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column: m mandatory - the capability is required to be supported. o optional - the capability may be supported or not. n/a not applicable - in the given context, it is impossible to use the capability. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table. Reference column The reference column makes reference to TS 124 608 [1], except where explicitly stated otherwise. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [4], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 8 Prerequisite line A prerequisite line takes the form: Prerequisite: <predicate>. A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.1.3 Instructions for completing the PICS proforma
|
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 4.1.2. However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations. If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately. More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2 Identification of the implementation
|
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.1 Date of the statement
|
.........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.2 Implementation Under Test (IUT) identification
|
IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: .........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.3 System Under Test (SUT) identification
|
SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 9 Operating system: .........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.4 Product supplier
|
Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.5 Client (if different from product supplier)
|
Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 10 Additional information: ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.2.6 PICS contact person
|
(A person to contact if there are any queries concerning the content of the PICS) Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.3 Identification of the TS 124 608
|
This PICS proforma applies to the following standard: TS 124 608 [1]: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)".
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.4 Global statement of conformance
|
Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to the <reference specification type> specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma.
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.5 Roles
|
Table 4.5.1: Roles Item Role Reference Status Support 1 Is the implementation an originating user equipment? 4.5.2.1 o 2 Is the implementation a terminating user equipment? 4.5.2.12 o 3 Is the implementation an Application Server serving the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) 4.5.2.9 o Comments: ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 11
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.6 User role
|
This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations: Prerequisite: 4.5.1/1 -- user role
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.6.1 Major capabilities
|
Table 4.6.1: User Equipment capabilities Item Call direction Reference Status Support 1 Does the user equipment support the "from-change" tag in the Supported header? 4.5.2.12 c21 2 [2/6] Does the terminating user equipment send an UPDATE request if a "from-change" tag was received in the initial INVITE? 4.5.2.12 c22 c21: IF 4.5.1/1 THEN o ELSE n/a. c22: IF 4.5.1/2 THEN o ELSE n/a. Comments:
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.7 Network role
|
This clause contains the PICS proforma tables related to the network role. They need to be completed only for Application Server implementations: Prerequisite: 4.5.1/2 -- user role
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.7.1 Major capabilities
|
Table 4.7.1: Network capabilities Item Call direction Reference Status Support 1 Is the network able to divert a call? TS 124 604 [5] o 2 Does the network support the "special arrangement" for the terminating user? 4.5.2.9 o 3 Does the network support the Terminating Identification Presentation (TIP) service? 4.3.1.1 o 4 Does the network support the Terminating Identification Restriction (TIR) service? 4.3.1.2 o 5 Does the network support the "TIR service in temporary mode"? 4.3.1.2 o 6 Does the network support the "TIR service in permanent mode"? 4.3.1.2 o 7 Does the network support the "override category for the TIR service"? 4.6.3 o 8 Does the network support the "special arrangement" for the terminating user? 4.5.2.9 o Comments: ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 12 Prerequisite: 4.7.1/4 --Major capabilities
|
9998345ee5dbb598b255dd03978ee6a5
|
101 596-1
|
4.7.2 CDIV capabilities
|
Table 4.7.2: CDIV Network capabilities Item Call direction Reference Status Support 1 Is the subscription option "Originating user receives notification that his communication has been diverted (forwarded or deflected)" supported? 4.3.1 [5] c31 2 Is the subscription option "Served user allows the presentation of diverted to URI to originating user in diversion notification" supported? 4.3.1 [5] c32 c31: IF 4.7.1/4 THEN o ELSE n/a. c32: IF 4.7.1/4 AND 4.7.2/1 THEN o ELSE n/a. Comments: ETSI ETSI TS 101 596-1 V5.1.1 (2012-10) 13 History Document history V5.1.1 October 2012 Publication
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
1 Scope
|
The present document provides the Test Suite Structure an Test Purposes for the Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; conformance test specification (based on 3GPP TS 24.616 Release 10).
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
2 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. For non-specific references, the latest version of the reference document (including any amendments) applies. 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 publication, ETSI cannot guarantee their long term validity.
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 616: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10)". [2] ETSI TS 101 595-1: "IMS Network Testing (INT); Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP Release 10); Part 1: Protocol Implementation Conformance Statement (PICS)".
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
2.2 Informative references
|
The following referenced 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] IETF RFC 3966: "The tel URI for Telephone Numbers". [i.2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
3 Definitions, symbols and abbreviations
| |
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in [1] and the following apply: communication information: information collected and registered by the MCID service identity information: 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]. ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 6 trusted identity: network generated user address information untrusted identity: user generated user address information NOTE: This may contain additional information.
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
3.2 Symbols
|
For the purposes of the present document, the symbols given in [1] apply.
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in [1] and the following apply: AS Application Server ID user IDentification IM IP Multimedia IMS IP Multimedia Subsystem IP Internet Protocol ISC IP multimedia subsystem Service Control MCID Malicious Call Identification MIME Multipurpose Internet Mail Extensions SIP Session Initiation Protocol TP Test Purposes TSS Test Suite Structure UE User Equipment URI Uniform Resource Identifier XML eXtensible Markup Language
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
4 Test Suite Structure (TSS)
|
Table 4-1: Test Suite Structure (TSS) MCID terminating_AS MCID_N01_xxx destination_UE MCID_U01_xxx interaction ECT MCID_N02_xxx
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
4.1 Configuration
|
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in TS 124 616 [1]. The stage 3 description describes the requirements for several network entities and also the requirements regarding for terminal 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.
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
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 101 595-2 V5.1.1 (2012-10) 7 Figure 4.1.1-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 4.1.1-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. Figure 4.1.1-2: Applicable interfaces for tests using a (generic) NNI interface
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
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 test configuration below has been chosen. User Equipment Implementation under Test Test System Gm Figure 4.1.2-1: Applicable configuration to test UE functionalities ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 8
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5 Test Purposes (TP)
| |
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
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-1). Table 5.1.1-1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "MCID" <iut> = type of IUT: U User equipment N Network entity <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.1.2 Test strategy
|
As the base standard TS 124 616 [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 101 595-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 101 595-2 V5.1.1 (2012-10) 9
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.2 TPs for Malicious Communication Identification (MCID)
| |
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.2.1 Actions at the AS of the terminating user
|
TSS MCID/terminating_AS TP MCID_N01_001 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose The AS holds the call state after a BYE from the originating UE Ensure that the AS holds the confirmed call state while TMCID-BYE is running, if MCID is subscribed by the called user and a BYE was received from the originating user UE. When TMCID-BYE is expired, the BYE is forwarded to the terminating UE. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK BYE TMCID-BYE started 200 OK BYE TMCID-BYE expires BYE 200 OK BYE TSS MCID/terminating_AS TP MCID_N01_002 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose The AS holds the early dialogue state after a CANCEL from the originating UE Ensure that the AS holds the early dialogue state while TMCID-BYE is running, if MCID is subscribed by the called user and a CANCEL was received from the originating user UE. When TMCID-BYE is expired, the CANCEL is forwarded to the terminating UE. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing CANCEL TMCID-BYE started 200 OK CANCEL 487 Request Terminated ACK TMCID-BYE expires CANCEL 200 OK CANCEL 487 Request Terminated ACK ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 10 TSS MCID/terminating_AS TP MCID_N01_003 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request containing a mcid XML body. The AS holds the call state after a BYE from the originating UE in the confirmed dialogue MCID is subscribed by the called user and a BYE was received from the originating user UE in the confirmed dialogue. Ensure that the AS holds the call state while TMCID-BYE is running. If a reINVITE and the 'mcid' XML body is present to invoke the MCID service was received while TMCID-BYE is running, ensure that the BYE is forwarded to the terminating UE when TMCID-BYE is expired. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification XML mcid request McidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK BYE TMCID-BYE started 200 OK BYE Re-INVITE requesting MCID 200 OK INVITE ACK TMCID-BYE expires BYE 200 OK BYE TSS MCID/terminating_AS TP MCID_N01_004 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request a mcid XML body is not present. The AS holds the call state after a BYE from the originating UE in the confirmed dialogue MCID is subscribed in Temporary Mode by the called user and a BYE was received from the originating user UE in the confirmed dialogue. Ensure that the AS holds the call state while TMCID-BYE is running. If a reINVITE and the 'mcid' XML body is not present to invoke the MCID service was received while TMCID-BYE is running, ensure that the BYE is forwarded to the terminating UE when TMCID-BYE is expired. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK BYE TMCID-BYE started 200 OK BYE Re-INVITE requesting MCID 200 OK INVITE ACK TMCID-BYE expires BYE 200 OK BYE ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 11 TSS MCID/terminating_AS TP MCID_N01_005 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request containing a mcid XML body in the confirmed dialogue MCID is subscribed with Temporary Mode by the called user Ensure that a reINVITE and the 'mcid' XML body is present to invoke the MCID service was received in the confirmed state the reINVITE is not sent toward the originating UE. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification XML mcid request McidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Re-INVITE requesting MCID 200 OK INVITE ACK Apply post test routine TSS MCID/terminating_AS TP MCID_N01_006 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request a mcid XML body is not present in the confirmed dialogue MCID is subscribed with Temporary Mode by the called user A reINVITE and the 'mcid' XML body is not present to invoke the MCID service was received in the confirmed state the reINVITE is possible sent toward the originating UE. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK CASE A Re-INVITE requesting MCID 200 OK INVITE ACK CASE B Re-INVITE Re-INVITE requesting MCID 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 12 TSS MCID/terminating_AS TP MCID_N01_007 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request containing a mcid XML body. The AS holds the call state after a CANCEL from the originating UE in the early dialogue MCID is subscribed with Temporary Mode by the called user and a CANCEL was received from the originating user UE in the early dialogue. Ensure that the AS holds the call state while TMCID-BYE is running. If a reINVITE to invoke the MCID service was received and the 'mcid' XML body is present while TMCID-BYE is running, ensure that the CANCEL is forwarded to the terminating UE when timer TMCID-BYE is expired. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification XML mcid request McidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing CANCEL TMCID-BYE started 200 OK CANCEL 487 Request Terminated ACK Re-INVITE requesting MCID 200 OK INVITE ACK TMCID-BYE expires CANCEL 200 OK CANCEL 487 Request Terminated ACK ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 13 TSS MCID/terminating_AS TP MCID_N01_008 MCID reference 4.5.2.5.2 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose MCID request a mcid XML body is not present. The AS holds the call state after a CANCEL from the originating UE in the early dialogue MCID is subscribed in Temporary Mode by the called user and a CANCEL was received from the originating user UE in the early dialogue. Ensure that the AS holds the call state while TMCID-BYE is running. If a reINVITE to invoke the MCID service was received and the 'mcid' XML body is not present while TMCID-BYE is running, ensure that the CANCEL is forwarded to the terminating UE when timer TMCID-BYE is expired. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: reINVITE without session modification Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing CANCEL TMCID-BYE started 200 OK CANCEL 487 Request Terminated ACK Re-INVITE requesting MCID 200 OK INVITE ACK TMCID-BYE expires CANCEL 200 OK CANCEL 487 Request Terminated ACK ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 14 TSS MCID/terminating_AS TP MCID_N01_009 MCID reference 4.5.2.5.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose Requesting the originating identity not received in the initial INVITE; response received containing the requested Identity An INVITE request was received and a P-Asserted. Identity is not present. Ensure that the AS, having sent an INFO message containing 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 (Permanent Mode or Temporary Mode) SIP header values: INVITE: without P-Asserted-Identity INFO1 XML mcid request McidRequestIndicator = 1 INFO2 XML mcid Response McidResponseIndicator = 1 OrigPartyIdentity (otional) OrigPartyPresentationRestriction (otional) GenericNumber (otional) GenericNumberPresentationRestriction (otional) Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE 100 Trying CASE A INFO1 (MIME body) TO-ID started INVITE 200 OK INFO 100 Trying 180 Ringing INFO2 (MIME body) TO-ID stopped 200 OK INFO 180 Ringing CASE B INFO1 (MIME body) TO-ID started 200 OK INFO INFO2 (MIME body) TO-ID stopped INVITE 200 OK INFO 100 Trying 180 Ringing 180 Ringing Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 15 TSS MCID/terminating_AS TP MCID_N01_010 MCID reference 4.5.2.5.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose Requesting the originating identity not received in the initial INVITE; response received without originating Identity An INVITE request was received and a P-Asserted-Identity is not present. Ensure that the AS, having sent an INFO message containing a XML 'mcid' body with MCID XML Request schema requesting the originating ID, on receipt of an INFO message not containing the originating identity, passes on the 180 Ringing from the called user. Preconditions: Called user has MCID subscription (Permanent Mode or Temporary Mode) SIP header values: INVITE: without P-Asserted-Identity INFO1 XML mcid request McidRequestIndicator = 1 INFO2 XML mcid response McidResponseIndicator = 0 without originating identity Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE 100 Trying CASE A INFO1 (MIME body) TO-ID started INVITE 200 OK INFO 100 Trying 180 Ringing INFO2 (MIME body) TO-ID stopped 200 OK INFO 180 Ringing CASE B INFO1 (MIME body) TO-ID started 200 OK INFO INFO2 (MIME body) TO-ID stopped INVITE 200 OK INFO 100 Trying 180 Ringing 180 Ringing Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 16 TSS MCID/terminating_AS TP MCID_N01_011 MCID reference 4.5.2.5.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose Requesting the originating identity not received in the initial INVITE; no response received An INVITE request was received and a P-Asserted. Identity is not present. Ensure that the AS, having sent an INFO message containing a XML 'mcid' body with MCID XML Request schema requesting the originating ID, on the expiry of TO-ID, passes on the 180 Ringing from the called user. Preconditions: Called user has MCID subscription (Permanent Mode or Temporary Mode) SIP header values: INFO XML mcid request McidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE 100 Trying CASE A INFO (MIME body) TO-ID started INVITE 200 OK INFO 100 Trying 180 Ringing 180 Ringing TO-ID expires CASE B INFO1 (MIME body) TO-ID started 200 OK INFO TO-ID expires INVITE 100 Trying 180 Ringing 180 Ringing Apply post test routine
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.2.2 Actions at the destination UE
|
TSS MCID/destination_UE TP MCID_U01_001 MCID reference 4.5.2.12 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose The UE sends a MCID request in the confirmed state Ensure that the UE is able to invoke MCID in the confirmed state. The UE sends a Re-INVITE without session modification and no 'mcid' XML element is present. Preconditions: SIP header values: Re-INVITE without session modification Comments: Test equipment User equipment INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Re-INVITE requesting MCID 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 17 TSS MCID/destination_UE TP MCID_U01_002 MCID reference 4.5.2.12 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose The UE sends a MCID request in the early dialogue Ensure that the UE is able to invoke MCID in the early dialogue. The UE sends a Re-INVITE without session modification and no 'mcid' XML element is present. Preconditions: SIP header values: Re-INVITE without session modification Comments: Test equipment User equipment INVITE 100 Trying 180 Ringing Re-INVITE requesting MCID 200 OK INVITE ACK Apply post test routine TSS MCID/destination_UE TP MCID_U01_003 MCID reference 4.5.2.12 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/2 Test purpose The UE sends a MCID request using the XML McidRequestIndicator in the confirmed state Ensure that the UE is able to invoke MCID in the confirmed state. The UE sends a Re-INVITE without session modification. Ensure that the UE is able to send a 'mcid' XML MIME body with the McidRequestIndicator set to 1. Preconditions: SIP header values: Re-INVITE without session modification XML mcid request McidRequestIndicator = '1' Comments: Test equipment User equipment INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Re-INVITE requesting MCID 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 18 TSS MCID/destination_UE TP MCID_U01_004 MCID reference 4.5.2.12 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/2 Test purpose The UE sends a MCID request using the XML McidRequestIndicator in the early dialogue Ensure that the UE is able to invoke MCID in the early dialogue. The UE sends a Re-INVITE without session modification. Ensure that the UE is able to send a 'mcid' XML MIME body with the McidRequestIndicator set to 1. Preconditions: SIP header values: Re-INVITE without session modification XML mcid request McidRequestIndicator = '1' Comments: Test equipment User equipment INVITE 100 Trying 180 Ringing Re-INVITE requesting MCID 200 OK INVITE ACK Apply post test routine
|
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.3 Interaction with other services
| |
68c00332306f50fa8c1d0ade394e7e34
|
101 595-2
|
5.3.1 Explicit Communication Transfer (ECT)
|
TSS MCID/interaction/ECT TP MCID_N02_001 MCID reference 4.6.10 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose MCID request is rejected if a communication is transferred MCID is subscribed in Temporary Mode by the called user and the confirmed communication is set on hold. Ensure that a MCID request is rejected if a communication was transferred before by the called user. Preconditions: Called user has MCID subscription with Temporary Mode SIP header values: INVITE XML mcid request McidRequestIndicator = 1 Comments: Test equipment (ISC) AS Test equipment (Gm) INVITE 1 INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK INVITE INVITE 2 (sendonly) 200 OK INVITE 200 OK INVITE (recvonly) ACK ACK REFER 202 Accepted INVITE 3 488 Not Acceptable Here ACK Apply post test routine ETSI ETSI TS 101 595-2 V5.1.1 (2012-10) 19 History Document history V5.1.1 October 2012 Publication
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
1 Scope
|
The present document provides the Implementation Conformance Statement (ICS) proforma for the Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10) defined in TS 124 616 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [2].
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
2 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. For non-specific references, the latest version of the reference document (including any amendments) applies. 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 publication, ETSI cannot guarantee their long term validity.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 616: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10)". [2] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [3] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [4] ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 1: General concepts".
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
2.2 Informative references
|
The following referenced 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] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)". ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 6
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
3 Definitions, symbols and abbreviations
| |
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 616 [1], ETS 300 406 [2], ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [3] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, API ICS etc. ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
3.2 Symbols
|
For the purposes of the present document, the symbols given in [1] apply.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test PICS Protocol ICS SUT System Under Test ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 7
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4 PICS proforma for TS 124 616
|
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.1 Guidance for completing the PICS proforma
| |
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.1.1 Purposes and structure
|
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in TS 124 616 [1] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of information: • guidance for completing the ICS proforma; • identification of the implementation; • identification of TS 124 616 [1]; • global statement of conformance; • roles; • user role: - major capabilities; • network role: - major capabilities.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.1.2 Abbreviations and conventions
|
The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [3]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 8 Status column The following notations, defined in ISO/IEC 9646-7 [3], are used for the status column: m mandatory - the capability is required to be supported. o optional - the capability may be supported or not. n/a not applicable - in the given context, it is impossible to use the capability. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table. Reference column The reference column makes reference to TS 124 616 [1], except where explicitly stated otherwise. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [3], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). References to items For each possible item answer (answer in the support column) within the ICS proforma a unique reference exists, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. If there is more than one support column in a table, the columns are discriminated by letters (a, b, etc.), respectively. EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of clause 4. EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 6 of clause 4. Prerequisite line A prerequisite line takes the form: Prerequisite: <predicate>. A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.1.3 Instructions for completing the PICS proforma
|
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 4.1.2. However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations. If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately. ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 9 More detailed instructions are given at the beginning of the different clauses of the ICS proforma.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2 Identification of the implementation
|
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.1 Date of the statement
|
.........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.2 Implementation Under Test (IUT) identification
|
IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.3 System Under Test (SUT) identification
|
SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Operating system: .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.4 Product supplier
|
Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 10 Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.5 Client (if different from product supplier)
|
Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.2.6 PICS contact person
|
(A person to contact if there are any queries concerning the content of the PICS) Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 11 E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.3 Identification of the TS 124 616
|
This PICS proforma applies to the following standard: TS 124 616 (2011-03): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10)".
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.4 Global statement of conformance
|
Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to TS 124 616. Non-supported mandatory capabilities are to be identified in the ICS, with an explanation of why the implementation is non-conforming, on pages attached to the ICS proforma.
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.5 Roles
|
Table 4.5.1: Roles Item Role Reference Status Support 1 User 4.5.2.12 o.1 2 Network 4.5.2.5 o.1 o.1: It is mandatory to support exactly one of these items. Comments: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.6 User role
|
This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations: Prerequisite: 4.5.1/1 -- user role ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 12
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.6.1 Major capabilities
|
Table 4.6.1: Call directions Item Item description Reference Status Support 1 [UE] Is the invocation of the MCID service provided? 4.5.2.12 o 2 [UE] Is the invocation of the MCID service using the XML MIME body mcid provided? 4.5.2.12 o Comments: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.7 Network role
|
This clause contains the PICS proforma tables related to the network role. They need to be completed only for Application Server implementations: Prerequisite: 4.5.1/2 -- network role
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.7.1 Major capabilities
|
Table 4.7.1: Network capabilities Item Item description Reference Status Support 1 Is the MCID service in permanent case provided? 4.5.2.5.1 o.1 2 Is the MCID service case by case provided? 4.5.2.5.2 o.1 3 When interacting with the PSTN/ISDN applies is a missing or incomplete originating user ID requested? 4.5.2.5.3 o 4 The network supports the Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem simulation service? [i.1] o o.1: For this service, it is mandatory to support at least one of these items. Comments: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 13
|
65e4429317653de2b0d8d4dea6bb402e
|
101 595-1
|
4.7.2 Timers
|
Table 4.7.2: Timers Item Item description Reference Status Support Values Allowed [s] Supported 1 TMCID-BYE 4.5.2.5.2 m 0 to 120 2 TO-ID 4.5.2.5.3 c1 4 to 15 c1: IF 4.7.1/3 THEN m ELSE n/a. ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 14 Annex A (informative): Bibliography ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 1: General concepts". ETSI TS 124 604: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 Release 10)". ETSI ETSI TS 101 595-1 V5.1.1 (2012-10) 15 History Document history V5.1.1 October 2012 Publication
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
1 Scope
|
The present document provides the Test Suite Structure and Test Purposes (TSS&TP) for the protocol specification as defined in ETSI [1] in compliance with the relevant requirements.
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
2 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. 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 http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)". [2] ETSI TS 101 594-1: "Technical Committee for IMS Network Testing (INT); Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP Release 10); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ETSI TS 124 628: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628 Release 10)".
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
3 Definitions, symbols and abbreviations
| |
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in [1] apply. ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 6
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
3.2 Symbols
|
For the purposes of the present document, the symbols given in [1] apply.
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in [1] and the following apply: ACR-CB Anonymous Communication Rejection- Communication Barring ISC IM-CN Service Control IUT Implementation Under Test NNI Network Network Interface PIXIT Protocol Implementation eXtra Information for Testing SIP Session Initiation Protocol SUT System Under Test TP Test Purpose UE User Equipment URI Uniform Resource Identifier
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
4 Test Suite Structure (TSS) and configuration
|
Netw TransferorAS ECT_N01_xxx TransfereeAS ECT_N02_xxx User Transferor ECT_U01_xxx Transferee ECT_U02_xxx TransferTarget ECT_U03_xxx Interaction OIR ECT_N03_xxx ACR-CB ECT_N04_xxx CONF ECT_N05_xxx ECT ECT_N06_xxx Figure 4.1: Test suite structure
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
4.1 Configuration
|
The scope of the 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 also to requirements 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 perform the service. Hence the ISC interface is the appropriate access point. Figure 4.1.1 points to this. ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 7 Figure 4.1.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.1.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. CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 4.1.2: Applicable interfaces to test using the (generic) NNI interface Figure 4.1.2 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 Equipment Implementation under Test Test System Gm Figure 4.1.3: Applicable configuration to test the User Equipment ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 8
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
5 Test Purposes (TP)
| |
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
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 5.1.1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "ECT" <iut> = type of IUT: U User N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
5.1.2 Test strategy
|
As the base standard [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 [2]. ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 9
|
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
5.2 Signalling requirements
| |
9c9040046fb0b6b58964d63a2286c73c
|
101 594-2
|
5.2.1 Actions at the Transferor UE
|
TSS User/Transferor TP ECT_U01_001 Reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, blind transfer). Ensure that the UE is able to transfer a communication with the Transferee, optionally put on hold before, to the Transfer Target using the blind transfer method. The session with user Transferee is terminated before information about the progress of the transfer is received. SIP header values: REFER: Request URI: Gm#2 Refer-To contains Gm#3 URI, method=invite Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE (Gm#1) Test equipment (Gm#2) Establishment of session #1 CASE A Session #1 on hold REFER REFER 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY CASE B REFER REFER 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 10 TSS User/Transferor TP ECT_U01_002 Reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/2 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, assured transfer). Ensure that the UE is able to transfer a communication with the Transferee, optionally put on hold before, to the Transfer Target using the assured transfer method. The session with Transferee is terminated after information about the progress of the transfer is received. SIP header values: REFER: Request URI: Gm#2 Refer-To contains Gm#3 URI; method=invite Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 CASE A Session #1 on hold REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE(inactive/sendonly) INVITE(inactive/sendonly) 200 OK INVITE(inactive/recvonly) 200 OK INVITE(inactive/recvonly) ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) CASE B REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE(inactive/sendonly) INVITE(inactive/sendonly) 200 OK INVITE(inactive/recvonly) 200 OK INVITE(inactive/recvonly) ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 11 TSS User/Transferor TP ECT_U01_003 Reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/3 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, consultative transfer). Ensure that the UE is able to transfer a communication with the Transferee, optionally put on hold before, to the Transfer Target, having a session, optionally put on hold before, using the consultative transfer method. The REFER request contains a replaces header escaped in the Refer-To header to request the termination of the session between Transferor and Transfer Target (session #2). SIP header values: REFER: Request URI: Gm#2 Refer-To: contains Gm#3 URI; method=invite?Replaces=call-id1%3Bto-tag%3DSession1%3B from-tag%3DSession1& Require=replaces Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 (Session #1 on hold) Establishment of session #2 (Session #2 on hold) REFER REFER 202 Accepted 202 Accepted CASE A NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE #1 BYE 200 OK (BYE) 200 OK (BYE) BYE BYE #2 200 OK (BYE) 200 OK (BYE) CASE B NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY BYE BYE #2 200 OK (BYE) 200 OK (BYE) NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE #1 BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 12
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.