hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.10 Sending Notification
|
Note that SIP messages as 100 TRYING are not included in sequence diagrams below. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 87
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.10.1 Notification in Signalling path
|
This test description logic will be used also by Content Recommendation (4.4.19) using specific parameters as NotificationReason (see TS 183 063 [2], clause 5.3.6.1). Interoperability Test Description Identifier: TD_ IMS_IPTV_Not_0001 Summary: SCF generates and sends a message request for the transport of notification References: TS 182 027 [1], clause 9.4; TS 183 063 [2], clauses 5.1.9.1 and 5.3.6.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE has initiated trick-play on a live broadcast channel (see TD_IMS_IPTV_BC1_0001) Test Sequence: Step 1 User is watching BC channel 2 SCF receives a trick play reports from MF 3 Verify that UE presents the received notification to the user Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S C O D S 1 SCF receives a trick play reports from MF 2 SIP AS sends SIP MESSAGE to CORE via ISC 3 SIP CORE sends SIP MESSAGE to UE via Gm 4 SIP UE sends SIP 200 OK response to CORE via Gm 5 SIP CORE sends SIP 200 OK response to AS via ISC 6 Verify that UE presents the received notification to the user Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.11 Instant Messaging
|
The UE shall support OMA Instant Messaging according to [13] and [14]. Note that SIP messages as 100 TRYING are not included in sequence diagrams below. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 88
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.11.1 Instant Messaging Sending
|
Interoperability Test Description Identifier: TD_IMS_IPTV_IM_0001 Summary: User sends an instant message through OMA Instant Messaging References: TS 182 027 [1], clause 9.3.1; TS 183 063 [2], clauses 5.1.17.1 and 5.3.16.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • UE supports OMA Instant Messaging • UE is registered in Core IMS using userIPTV_priv identity Test Sequence: Step 1 User registers to OMA Instant Messaging service 2 User sends "Available soon?" IM 3 Verify that UE receives SIP 200 OK Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 User registers to OMA Instant Messaging service 2 UE sends SIP REGISTER request including OMA feature tag [14] to CORE via Gm 3 CORE sends SIP REGISTER request to AS via ISC 4 AS sends SIP 200 OK response to CORE via ISC 5 CORE sends SIP 200 OK response to UE via Gm 6 UE sends "Available soon?" IM 7 SIP UE sends SIP MESSAGE with specified header to CORE via Gm 8 SIP CORE sends SIP MESSAGE with specified header to AS via ISC 9 SIP AS sends SIP 200 OK response to CORE via ISC 10 SIP CORE sends SIP 200 OK response to UE via Gm 11 UE receives SIP 200 OK Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 89
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.11.2 Instant Messaging Receiving
|
Interoperability Test Description Identifier: TD_IMS_IPTV_IM_0002 Summary: User receives an instant message through OMA Instant Messaging References: TS 182 027 [1], clause 9.3.1; TS 183 063 [2], clauses 5.1.17.1 and 5.3.16.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • UE supports OMA Instant Messaging • UE is registered in Core IMS using userIPTV_priv identity • UE is registered to OMA IM service (see TD_IMS_IPTV_IM_0001) Test Sequence: Step 1 An Instant Message is required to be sent to UE 2 Verify that UE displays the received IM Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 An Instant Message is required to be sent to UE 2 AS sends SIP MESSAGE to CORE via ISC 3 CORE sends SIP MESSAGE to UE via Gm 4 UE sends 200 OK to CORE via Gm 5 CORE sends 200 OK to AS via ISC 6 Verify that UE displays the received IM Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.12 PushCoD
|
Note that SIP messages as 100 TRYING are not included in sequence diagrams below. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 90
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.12.1 UE-initiated Content download for unicast download
|
Refer to TS 183 063 [2], clause 5.3.2.1 for the procedure to handling for missing parameters before session initiation. Interoperability Test Description Identifier: TD_IMS_IPTV_pCoD_0001 Summary: User request to download a CoD content References: TS 182 027 [1], clauses 8.17.1 and 8.18.2; TS 183 063 [2], clauses 5.1.18.1, 5.4.1.2 and 6.5.1.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • Refer to test description TD_IMS_IPTV_CoD1_0001 Test Sequence: Step 1 User requests to download a CoD content 2 Verify that UE has downloaded the expected content Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S C o D S 1 User requests to download a CoD 2 SIP/SDP UE sends SIP INVITE including the contentID and the download content URI and a SDP offer to CORE via Gm 3 SIP/SDP CORE sends SIP INVITE to AS via ISC 4 SIP/SDP AS sends SIP INVITE to CORE via ISC 5 SIP/SDP CORE sends SIP INVITE to CoDS via y2 6 SIP/SDP CoDS sends SIP 200 OK response to CORE via y2 7 SIP/SDP CORE sends SIP 200 OK response to AS via ISC 8 SIP/SDP AS sends SIP 200 OK response to CORE via ISC 9 SIP/SDP CORE sends SIP 200 OK response to UE via Gm 10 SIP/SDP UE sends SIP ACK to CORE via Gm 11 SIP/SDP CORE sends SIP ACK to AS via ISC 12 SIP/SDP AS sends SIP ACK to CORE via ISC 13 SIP/SDP CORE sends SIP ACK to CoDS via y2 14 HTTP UE sends HTTP GET request with header "Connection" set to "Keep Alive" via Xd 15 HTTP CoDS sends HTTP response via Xd 16 Verify that UE has downloaded the expected content Note that this test description will be reused in clause 4.4.9.10 because of the test logic is identical, only SDP offer parameters shall be changed as the type of content element: it shall be set to "streaming" (see TS 183 063 [2], clause 5.1.18.1 bullet 6). Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 91
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.12.2 UE-initiated Content download for unicast progressive download
|
Refer to test description 4.4.9.8 for the logic of the test description. Modifying SDP offer parameters (as the type of content element set to "progressive") permits to cover all test descriptions.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.13 Targeted Ad Insertion (TAI) - SCTE
|
These test descriptions cover delivery of personalised advertising to subscribers. The clauses below depict the general procedure for targeted Ad insertion (see TS 182 027 [1], clause 8.14). Note that SIP messages as 100 TRYING are not included in sequence diagrams below.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.13.1 TAI by notification at UE side
|
In this test description, we assume that UE initiates a separate session to MF that includes the target Ad content (see TS 182 027 [1], clause 8.14.2.1 step 6). Interoperability Test Description Identifier: TD_IMS_IPTV_TAI2_0001 Summary: User receives an advertising message References: TS 182 027 [1], clauses 8.14.2.1 and E.2; TS 183 063 [2], clauses 5.1.15.1 and 5.3.14 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE subscription is configured to accept Advertising service • The UE is watching CoD content (see TD_IMS_IPTV_CoD1_0001) • SCF is connected to at least one Ad Server (see clause E.2.4.2.1) Test Sequence: Step 1 SCF sends Ad message to UE 2 Verify that UE displays the Advertising message without interruption of watching CoD Conformance Criteria: Check 1 Message exchange follows the below table ETSI ETSI TS 186 020 V3.1.1 (2011-07) 92 Step Direction Protocol Comment U s e r U E T & A C O R E A S C O D S 1 SCF sends Advertising message to UE 2 SIP AS sends SIP MESSAGE request to CORE via ISC 3 SIP CORE sends SIP MESSAGE request to UE via Gm 4 SIP UE sends 200 OK to CORE via Gm 5 SIP CORE sends 200 OK to AS via ISC 6 UE initiate s a session for content insertion 7 SIP/SDP UE sends SIP INVITE to CORE via Gm 8 SIP/SDP CORE sends SIP INVITE to AS via ISC 9 SIP/SDP AS sends SIP INVITE to CORE via ISC 10 SIP/SDP CORE sends SIP INVITE to CoDS via y2 11 SIP CoDS sends SIP 200 OK response to CORE via y2 12 SIP CORE sends SIP 200 OK response to AS via ISC 13 SIP AS sends SIP 200 OK response to CORE via ISC 14 SIP CORE sends SIP 200 OK response to UE via Gm 15 SIP UE sends SIP ACK to CORE via Gm 16 SIP CORE sends SIP ACK to AS via ISC 17 SIP AS sends SIP ACK to CORE vi ISC 18 SIP CORE sends ACK to CoDS via y2 19 RTSP UE sends RTSP PLAY to CoDS via Xc 20 RTSP CoDS sends RTSP 200 OK to UE via Xc 21 UE displays the Advertising message without interruption of watching CoD Refer to test description TD_IMS_IPTV_CoD1_0010 (4.4.5.10) for normal session termination at the end of stream.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.13.2 TAI by content insertion at UE side
|
In this test description, we assume that UE initiates a separate session to MF that includes the target Ad content (see TS 182 027 [1], clause 8.14.2.1 step 6). Interoperability Test Description Identifier: TD_IMS_IPTV_TAI2_0002 Summary: User receives an advertising message References: TS 182 027 [1], clauses 8.14.2.1 and E.2; TS 183 063 [2], clauses 5.1.15.2 and 5.3.14 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE subscription is configured to accept Advertising service • The UE is watching CoD content (see TD_IMS_IPTV_CoD1_0001) • SCF is connected to at least one Ad Server (see clause E.2.4.2.1) Test Sequence: Step 1 SCF sends Ad message to UE 2 Verify that UE displays the Advertising message without interruption of watching CoD Conformance Criteria: Check 1 Message exchange follows the below table ETSI ETSI TS 186 020 V3.1.1 (2011-07) 93 Step Direction Protocol Comment U s e r U E T & A C O R E A S C O D S 1 SCF sends Advertising message to UE 2 SIP AS sends SIP INFO request including "ContentInsertionReason" element set to "Advertising" to CORE via ISC 3 SIP CORE sends SIP INFO request to UE via Gm 4 SIP UE sends 200 OK to CORE via Gm 5 SIP CORE sends 200 OK to AS via ISC 6 UE initiate s a session for content insertion 7 SIP/SDP UE sends SIP INVITE to CORE via Gm 8 SIP/SDP CORE sends SIP INVITE to AS via ISC 9 SIP/SDP AS sends SIP INVITE to CORE via ISC 10 SIP/SDP CORE sends SIP INVITE to CoDS via y2 11 SIP CoDS sends SIP 200 OK response to CORE via y2 12 SIP CORE sends SIP 200 OK response to AS via ISC 13 SIP AS sends SIP 200 OK response to CORE via ISC 14 SIP CORE sends SIP 200 OK response to UE via Gm 15 SIP UE sends SIP ACK to CORE via Gm 16 SIP CORE sends SIP ACK to AS via ISC 17 SIP AS sends SIP ACK to CORE vi ISC 18 SIP CORE sends ACK to CoDS via y2 19 RTSP UE sends RTSP PLAY to CoDS via Xc 20 RTSP CoDS sends RTSP 200 OK to UE via Xc 21 UE displays the Advertising message without interruption of watching CoD Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.13.3 TAI by content insertion at MF side
|
Refer to test description above (see TS 183 063 [2], clause 5.1.15.2).
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.14 Emergency Information
|
We assume that the user is located in its home network. If not, UE is required to perform an IMS emergency registration. Note that SIP messages as 100 TRYING are not included in sequence diagrams below. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 94
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.14.1 Emergency Information by Notification
|
Refer to test description TD_IMS_IPTV_CoD1_0001, Start CoD to achieve pre-conditions. Interoperability Test Description Identifier: TD_IMS_IPTV_EMI_0001 Summary: UE receives an emergency alert References: TS 182 027 [1], clauses 15 bullets 1 and 8.11.1.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE is registered in Core IMS using userIPTV_priv identity • UE is registered in home network • UE is watching CoD as described by TD_IMS_IPTV_CoD1_0001 Test Sequence: Step 1 An emergency event is triggered on SCF 2 Verify that TV watching is interrupted and the user is alerted Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 An emergency event is triggered on SCF 2 SIP AS sends SIP MESSAGE including header field Priority set to "emergency" to CORE via ISC 3 SIP CORE sends SIP MESSAGE to UE via Gm 4 SIP UE sends 200 OK to CORE via Gm 5 SIP CORE sends 200 OK to AS via ISC 6 TV watching is interrupted and the user is alerted Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 95
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.14.2 Emergency Information by Content Insertion
|
Refer to test description TD_IMS_IPTV_BC_0001, Session initiation without RACS for broadcast TV to achieve pre-conditions. Interoperability Test Description Identifier: TD_IMS_IPTV_EMI_0002 Summary: References: TS 182 027 [1], clauses 15 bullet 2 and 8.11.1.2; TS 183 063 [2], clause 5.3.12.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE is registered in Core IMS using userIPTV_priv identity • UE is registered in home network • UE is watching broadcast TV as described by TD_IMS_IPTV_BC_0001 Test Sequence: Step 1 An emergency event is triggered on SCF to MF 2 Verify that TV watching is interrupted and the user is alerted Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S C O D S 1 An emergency event is triggered on SCF 2 SIP AS sends SIP MESSAGE including header field Priority set to "emergency" to CORE via ISC 3 SIP CORE sends SIP MESSAGE including header field Priority set to "emergency" to CoDS via y2 4 SIP CoDS sends SIP INFO message to CORE via y2 5 SIP CORE sends SIP INFO messages to UE via Gm 6 SIP UE sends 200 OK to CORE via Gm 7 SIP CORE sends 200 OK to CoDS via y2 8 SIP CoDS sends 200 OK to CORE via y2 9 SIP CORE sends 200 OK to AS via ISC 10 TV watching is interrupted and the user is alerted Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15 Incoming call management
|
In the test descriptions below, the same user B has two devices (UE): • An IPTV device, identified by UE B or UE B1 • A phone device, identified by UE B2 The user A calls the user B and user B could accept or reject the incoming call. The clauses below depict different Incoming Call behavior: 1) Incoming Call Rejection (4.4.9.18): The User B does not answer to the notification message (call rejection on notification time out) ETSI ETSI TS 186 020 V3.1.1 (2011-07) 96 2) Incoming Call Acceptance (4.4.9.19): The User B accepts the incoming call answering to the notification message, the call is sends on the IPTV device 3) Incoming Call Forwarding (4.4.9.20): The User B accepts the incoming call answering to the notification, the call is sends on the phone device
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15.1 Incoming call notification
|
Refer to Notification test description (4.4.9.4) using specific parameters as described in TS 183 063 [2], clause 5.3.6.1 (NotificationReason set to IncomingCall…). IncomingCallInfo shall be set to the information of the caller.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15.2 Incoming call handling
|
Refer to Incoming Call test descriptions below for Incoming Call handling (TS 182 027 [1], clause 9.2.1).
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15.3 Incoming call rejection
|
This test description depicts the following procedure: • User B is watching BC TV • User A calls User B • User B is notified of the incoming call • User B ignore the notify message (time out) Note that SIP messages as 100 TRYING are not included in sequence diagrams below. Interoperability Test Description Identifier: TD_IMS_IPTV_ICM_0001 Summary: References: TS 182 027 [1], clauses 9.2.1 and 9.2.2; TS 183 063 [2], clause 5.3.6.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE B, Core IMS, IPTV AS, UE A Pre-test conditions: • UE B is registered in Core IMS using userIPTV_priv identity • UE B is registered in home network • UE B is watching broadcast TV as described by TD_IMS_IPTV_BC_0001 Test Sequence: Step 1 UE A calls UE B 3 UE B refused the incoming call 4 Verify that TV signal was not interrupted Conformance Criteria: Check 1 Message exchange follows the below table ETSI ETSI TS 186 020 V3.1.1 (2011-07) 97 Step Direction Protocol Comment U s e r B U E B T & A C O R E A S U s e r A 1 An incoming call is received by CORE from UE A 2 SIP/SDP CORE sends SIP INVITE request to AS via ISC 3 SIP/SDP AS sends SIP MESSAGE with IncomingCallInfo to CORE via ISC (optional) 4 SIP/SDP CORE sends SIP MESSAGE to UE B via Gm (optional) 5 Verify that UE B is informed of incoming call (optional) 6 UE B does not answer after timeout 7 SIP AS sends SIP CANCEL to CORE via ISC 8 SIP CORE sends SIP CANCEL to UE A 9 SIP UE A sends SIP 200 OK to CORE 10 SIP CORE sends SIP 200 OK to AS via ISC 11 Verify that TV signal was not interrupted Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15.4 Incoming call acceptance on IPTV UE
|
This test description depicts the following procedure: • User B is watching BC TV • User A calls User B • User B is notified of the incoming call • User B accepts the incoming call on TV Note that SIP messages as 100 TRYING and 183 SESSION PROGRESS are not included in sequence diagrams below. By the way, 183 SESSION PROGRESS message shall be checked. Interoperability Test Description Identifier: TD_IMS_IPTV_ICM_0002 Summary: References: TS 182 027 [1], clause 9.2.2; TS 183 063 [2], clause 5.3.6.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE B, Core IMS, IPTV AS, UE A Pre-test conditions: • UE B is registered in Core IMS using userIPTV_priv identity • UE B is registered in home network • UE B is watching broadcast TV as described by TD_IMS_IPTV_BC_0001 Test Sequence: Step 1 UE A calls UE B 2 Verify that UE B is notified 3 UE B accepts the incoming call 4 Verify that UE A and UE B are connected Conformance Criteria: Check 1 Message exchange follows the below table ETSI ETSI TS 186 020 V3.1.1 (2011-07) 98 Step Direction Protocol Comment U s e r B U E B T & A C O R E A S U s e r A 1 An incoming call is received by CORE from UE A 2 SIP/SDP CORE sends SIP INVITE request to AS via ISC 3 SIP/SDP AS sends SIP MESSAGE with IncomingCallInfo to CORE via ISC (optional) 4 SIP/SDP CORE sends SIP MESSAGE to UE B via Gm (optional) 5 Verify that UE B is informed of incoming call (optional) 6 SIP/SDP UE B sends SIP 200 OK to CORE via Gm (UE B accepts the incoming call) 7 SIP/SDP CORE sends SIP 200 OK to AS via ISC 8 SIP/SDP AS sends SIP INVITE request to CORE via ISC 9 SIP/SDP CORE sends SIP INVITE to UE B via Gm 10 SIP/SDP UE B sends SIP 200 OK to CORE via Gm 11 SIP/SDP CORE sends SIP 200 OK to AS via ISC 12 SIP/SDP AS sends SIP 200 OK to CORE via ISC 13 SIP/SDP CORE sends SIP 200 OK to UE A 14 Verify that TV signal is paused and phone is ringing 15 SIP/SDP UE B sends SIP ACK to CORE via Gm 16 SIP/SDP CORE sends SIP ACK to AS via ISC 17 SIP/SDP AS sends SIP ACK to CORE via ISC 18 SIP/SDP CORE sends SIP ACK to UE A 19 Verify that UE A and UE B are connected Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.15.5 Incoming call forwarding to other UE
|
This test description depicts the following procedure: • UE B1 has registered call forward to User B2 • UE B1 is watching BC TV • UE A calls UE B1 • UE B2 is notified of the incoming call • UE B2 accepts the incoming call Note that SIP messages as 100 TRYING and 183 SESSION PROGRESS are not included in sequence diagrams below. By the way, 183 SESSION PROGRESS message shall be checked. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 99 Interoperability Test Description Identifier: TD_IMS_IPTV_ICM_0003 Summary: References: TS 182 027 [1], clause 9.2.2; TS 183 063 [2], clause 5.3.6.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE B, Core IMS, IPTV AS, UE A Pre-test conditions: • UE B1 and User B2 are registered in Core IMS using userIPTV_priv identity • UE B1 is registered in home network • UE B1 is watching broadcast TV as described by TD_IMS_IPTV_BC_0001 • UE B1 has registered call forward to User B2 Test Sequence: Step 1 UE A calls UE B1, call is forwarded to UE B2 2 Verify that UE B is notified 3 UE B accepts the incoming call 4 Verify that UE A and UE B are connected Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r B1 U E B1 U s e r B2 C O R E A S U s e r A 1 An incoming call is received by CORE from UE A 2 SIP/SDP CORE sends SIP INVITE request to AS via ISC 3 SIP/SDP AS sends SIP MESSAGE with IncomingCallInfo to CORE via ISC (optional) 4 SIP/SDP/SD P CORE sends SIP MESSAGE to UE B1 via Gm (optional) 5 Verify that UE B1 is informed of incoming call (optional) 6 SIP/SDP UE B1 sends SIP 200 OK to CORE via Gm (UE B accepts the incoming call) 7 SIP/SDP CORE sends SIP 200 OK to AS via ISC 8 SIP/SDP AS sends SIP INVITE request to CORE via ISC 9 SIP/SDP CORE sends SIP INVITE to UE B2 via Gm 10 SIP/SDP UE B sends SIP 200 OK to CORE via Gm 11 SIP/SDP CORE sends SIP 200 OK to AS via ISC 12 SIP/SDP AS sends SIP 200 OK to CORE via ISC 13 SIP/SDP CORE sends SIP 200 OK to UE A 14 Verify that TV signal is not interrupted on UE B1paused and phone is ringing 15 Verify that UE B2 is ringing 16 SIP/SDP UE B2 sends SIP ACK to CORE via Gm 17 SIP/SDP CORE sends SIP ACK to AS via ISC 18 SIP/SDP CORE sends SIP ACK to UE A 18 Verify that UE A and UE B2 are connected Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 100
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.16 Time Shifted TV
|
The Time Shift TV (tsTV) service allows user to view a video content that has already been broadcasted. In order to enable TsTV IPTV SP needs to record content in the MDF. IPTV SP may limit BC content available for TsTV. The logic for TsTV is very similar to that introduced for nPVR. The main difference resides in duration of expiration time: for TsTV, the expiration time is very short (some few minutes). In consequence, the test description logics are also very close to that introduced by Impulsive recording request and Watching a recorded content (refer to test descriptions TD_IMS_IPTV_nP2_0001 and TD_IMS_IPTV_nP2_0003).
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.17 Parental Control
|
For test descriptions below, the IPTV user profile shall be modified to set the parental control level.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.17.1 Parental Control applied for BC
|
Referring to test descriptions TD_IMS_IPTV_BC_0001 (4.4.2.1) and TD_IMS_IPTV_BC_0005 (4.4.2.5) for the logic of the test, add the checks listed below: 1) Check that EPG is filtered correctly, this means that channels not compatible with parental control level 2) SCF shall refused a BC request not compatible with parental control level
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.17.2 Parental Control applied for CoD
|
Referring to test description TD_IMS_IPTV_CoD1_0001 (4.4.5.1) for the logic of the test, add the checks listed below: 1) Check that EPG is filtered correctly, this means that channels not compatible with parental control level 2) SCF shall refused a CoD content request not compatible with parental control level
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.17.3 Parental Control applied for UGC
|
Referring to test description TD_IMS_IPTV_UGC_0004 (4.4.5) for the logic of the test, add the checks listed below: 1) Check that EPG is filtered correctly, this means that channels not compatible with parental control level 2) SCF shall refused a UGC content request not compatible with parental control level
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.17.4 Parental Control applied for PVR
|
Referring to test descriptions TD_IMS_IPTV_nP1_0001 (4.4.7.1), TD_IMS_IPTV_nP1_0002 (4.4.7.2) and TD_IMS_IPTV_nP1_0003 (4.4.7.3) for the logic of the test, add the checks listed below: 1) Check that EPG is filtered correctly, this means that channels not compatible with parental control level 2) SCF shall refused a n-PVR content request not compatible with parental control level
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.18 Content Marker Service (CM)
|
This feature allows users to bookmark content (entire movies/channels or individual scenes) for sharing with other users.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.18.1 Creating, updating and querying Content Marker (CM)
|
Using parameters, this test description logic covers procedure applied to creating (IPTVContentMarkerID provided by UE does not exist), updating and querying (IPTVContentMarkerID provided by UE exists) Content Marker. We assume that Content Marker procedures occur within an existing SIP session. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 101 Interoperability Test Description Identifier: TD_IMS_IPTV_CM_0001 Summary: UE creates, update or queries a Content Marker References: TS 183 063 [2], clauses 5.1.14.1 and 6.1.1.7 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • The SCF must have indicated its willingness to receive the IPTV-Content-Marker Info Package • The UE is watching CoD content (see TD_IMS_IPTV_CoD1_0001) Test Sequence: Step 1 User creates a Content Marker 2 Verify that the Content Marker was created Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 User creates a Content Marker 2 SIP UE sends SIP INFO including IPTV-Content- Marker Info Package to CORE via Gm 3 SIP CORE sends SIP INFO to AS via ISC 4 SIP AS sends SIP 200 OK response to CORE via ISC 5 SIP CORE sends SIP 200 OK response to UE via Gm 6 Verify that the Content Marker was created 7 HTTP UE sends HTTP POST request including the domain name of the SSF to AS via Xa 8 HTTP AS sends HTTP 200 OK to UA via Xa 9 XML Evaluate payload in HTTP response to verify that UE received to correct Content Marker Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 102
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.18.2 Removing Content Marker (CM)
|
We assume that removing Content Marker occurs outside an existing SIP session. Interoperability Test Description Identifier: TD_IMS_IPTV_CM_0002 Summary: UE removes a Content Marker References: TS 183 063 [2], clauses 5.1.14.1 and 6.1.1.7 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • The UE is register to CORE IMS • The UE has retrieved EPG (see clause 4.4.1) • The SCF must have indicated its willingness to receive the IPTV-Content-Marker Info Package • At least one Content Marker was created Test Sequence: Step 1 User removes a Content Marker 2 Verify that the Content Marker was removed Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 User removes a Content Marker 2 SIP UE sends SIP MESSAGE including IPTV- Content-Marker Info Package to CORE via Gm 3 SIP CORE sends SIP MESSAGE to AS via ISC 4 SIP AS sends SIP 200 OK response to CORE via ISC 5 SIP CORE sends SIP 200 OK response to UE via Gm 6 Verify that the Content Marker was removed 7 HTTP UE sends HTTP POST request including the domain name of the SSF to AS via Xa 8 HTTP AS sends HTTP 404 Not Found to UA via Xa Refer to test description TD_IMS_IPTV_CoD2_0007 (4.4.6.7) - Step 8 for normal session termination initiated by UE.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.19 Content Recommendation (CR)
|
Refer to Notification test description (4.4.9.4) using specific parameters as described in TS 183 063 [2], clause 5.3.6.1 (NotificationReason set to ContentRecommendation…) and TS 182 027 [1], clause 8.13.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.20 Presence
|
Note that SIP messages as 100 TRYING and 183 SESSION PROGRESS are not included in sequence diagrams below. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 103
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.20.1 Subscribing to presence
|
Interoperability Test Description Identifier: TD_IMS_IPTV_PRE_0001 Summary: UE subscribes to Presence service References: TS 182 027 [1], clause 9.1, TS 183 063 [2], clauses 5.1.6, 5.1.6.1 and annex E Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, Presence server, CoD Pre-test conditions: • The UE is register to CORE IMS • The UE is registered on CoD (refer to TD_IMS_IPTV_CoD1_0001 for the details of CoD session initiation procedure) Test Sequence: Step 1 Verify that UE displays the "available" presence status Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 UE has completed The CoD session initiation procedure 2 SIP/XML UE sends SIP SUBSCRIBE message to CORE via Gm 3 SIP/XML CORE sends SIP SUBSCRIBE message to AS via ISC 4 SIP AS sends SIP 200 OK including the expiration time to CORE via ISC 5 SIP CORE sends SIP 200 OK including the expiration time to UE via Gm 6 SIP/XML UE sends SIP PUBLISH message including CoDServicePresence XML element to CORE via Gm 7 SIP/XML CORE sends SIP PUBLISH message including CoDServicePresence XML element to AS via ISC 8 SIP AS sends SIP 200 OK to CORE via ISC 9 SIP CORE sends SIP 200 OK to UE via Gm 10 Verify that UE displays the "available" presence status Refer to test description TD_IMS_IPTV_CoD1_0001 (4.4.5.1) for normal session termination. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 104
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.20.2 Receiving presence notifications
|
Interoperability Test Description Identifier: TD_IMS_IPTV_PRE_0002 Summary: UE subscribes to Presence service References: TS 182 027 [1], clause 9.1, TS 183 063 [2], clause 5.1.6.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, Presence server, CoD Pre-test conditions: • The UE is register to CORE IMS • The UE has subscribed to Presence service (refer to TD_IMS_IPTV_PRE_0001) Test Sequence: Step 1 UE receive a presence notification message 2 Verify that UE displays the display the presence information Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E T & A C O R E A S 1 UE has subscribed to Presence service 2 SIP/XML AS sends SIP NOTIFY message to CORE via ISC 3 SIP/XML CORE sends SIP NOTIFY message to UE via Gm 4 SIP UE sends SIP 200 OK to CORE via Gm 5 SIP CORE sends SIP 200 OK to AS via ISC 6 Verify that UE displays the presence information Refer to test description TD_IMS_IPTV_CoD1_0001 (4.4.5.1) for normal session termination.
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.21 Service Continuation
|
An example of Service Continuation occurs when a user A in watching a CoD or BC content on a first IPTV device (an IPTV mobile for instance), he decides to transfer the current watching session on a second IPTV device (his computer) without interruption of the content. The Service Continuation proceeds in two stages: the pause procedure and the restart procedure. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 105
|
e92ae14f0d05d3f1f7f623039c9d4b32
|
186 020
|
4.4.21.1 Service Continuation between IPTV UEs
|
Interoperability Test Description Identifier: TD_IMS_IPTV_ST2_0001 Summary: UE initiates a CoD content transfer References: TS 183 063 [2], clause 5.1.20.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, Presence server, CoD Pre-test conditions: • The UEA is register to CORE IMS • The UEA is watching a CoD content (refer to refer to TD_IMS_IPTV_CoD1_0001) • User has selected the transferee: UE B, UE A is the transferor Test Sequence: Step 1 UE A initiates the transfer to UE B 2 Verify that UE A watching session is terminated 3 Verify that UE B displays the same content from the correct play time Conformance Criteria: Check 1 Message exchange follows the below table Step Direction Protocol Comment U s e r U E A U E B C O R E A S C o D s 1 UE A displays CoD content 2 User request a watching session transfer 3 RTSP UE A sends a RTSP PAUSE including the current play time to CoDs via Xc 4 RTSP CoDs sends RTSP 200 OK to UE A via Xc 5 SIP/SDP UE A sends SIP REFER request including the GRUU of the target device and the IPTV Content Marker to CORE via Gm 6 SIP/SDP CORE sends SIP REFER request including the GRUU of the target device and the IPTV Content Marker to AS via ISC 7 SIP/SDP AS sends SIP REFER request including the GRUU of the target device and the IPTV Content Marker to CORE via ISC 8 SIP/SDP CORE sends SIP REFER request including the GRUU of the target device and the IPTV Content Marker to CoDs via y2 9 SIP CoDs sends SIP 202 ACCPETED to CORE via y2 10 SIP CORE sends SIP 202 ACCPETED to AS via ISC 11 SIP AS sends SIP 202 ACCPETED to CORE via ISC 12 SIP CORE sends SIP 202 ACCPETED to UE via Gm 13 SIP/SDP CoDs sends SIP INVITE to CORE via y2 14 SIP/SDP CORE sends SIP INVITE to AS via ISC 15 SIP/SDP AS sends SIP INVITE to CORE via ISC 16 SIP/SDP CORE sends SIP INVITE to UE B via Gm 17 SIP UE B sends SIP 200 OK to CORE via Gm 18 SIP CORE sends SIP 200 OK to AS via ISC 19 SIP AS sends SIP 200 OK to CORE via ISC 20 SIP CORE sends SIP 200 OK to CoDs via y2 21 SIP CoDs sends SIP ACK to CORE via y2 22 SIP CORE sends SIP ACK to AS via ISC ETSI ETSI TS 186 020 V3.1.1 (2011-07) 106 Step Direction Protocol Comment U s e r U E A U E B C O R E A S C o D s 23 SIP AS sends SIP ACK to CORE via ISC 24 SIP CORE sends SIP ACK to UE B via Gm 25 SIP UE B sends SIP NOTIFY to CORE via y2 26 SIP CORE sends SIP NOTIFY to AS via ISC 27 SIP AS sends SIP NOTIFY to CORE via ISC 28 SIP CORE sends SIP NOTIFY to UE A via Gm 29 SIP UE A sends SIP 200 OK to CORE via Gm 30 SIP CORE sends SIP 200 OK to AS via ISC 31 SIP AS sends SIP 200 OK to CORE via ISC 32 SIP CORE sends SIP 200 OK to CoDs via y2 33 SIP CoDs sends SIP BYE to CORE via y2 34 SIP CORE sends SIP BYE to AS via ISC 35 SIP AS sends SIP BYE to CORE via ISC 36 SIP CORE sends SIP BYE to UE A via Gm 37 SIP UE A sends SIP 200 OK to CORE via Gm 38 SIP CORE sends SIP 200 OK to AS via ISC 39 SIP AS sends SIP 200 OK to CORE via ISC 40 SIP CORE sends SIP 200 OK to CoDs via y2 41 RTSP UE A sends a RTSP PLAY including the current play time to CoDs via Xc 42 RTSP CoDs sends RTSP 200 OK to UE A via Xc 43 Verify that UE A session is terminated 44 Verify that UE B displays the same content from the correct play time Refer to test description TD_IMS_IPTV_CoD1_0001 (4.4.5.1) for normal session termination. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 107 Annex A (informative): Bibliography IETF RFC 4566: "SDP: Session Description Protocol". ETSI ETSI TS 186 020 V3.1.1 (2011-07) 108 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 20-10-10 TISPAN(10)0182 01 B Scope_and ToC_update_for_IMS-IPTV_test-spec 3.0.0 3.0.3 15-03-11 TISPAN06(11)0002r2 02 B new testcases 3.0.3 3.0.4 15-06-11 TISPAN06(11)0015r2 03 B additional testcases for services from Release 3 and incorporate input from STF-413 3.0.4 3.0.5 15-06-11 TISPAN06(11)0016r1 04 F WI6061 update for figure 1 3.0.4 3.0.5 Publication 3.0.5 3.1.1 ETSI ETSI TS 186 020 V3.1.1 (2011-07) 109 History Document history V2.1.1 December 2009 Publication V3.1.1 July 2011 Publication
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
1 Scope
|
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 018-2 [3]. The TSS&TP have been developed to test the Malicious Communication Identification (MCID) PSTN/ISDN simulation services. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN-3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
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.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification". [2] ETSI TS 186 018-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ETSI TS 186 018-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 6 [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [6] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [7] ETSI ES 201 873-1 (V3.4.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)". [9] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [10] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [12] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [13] ETSI TS 186 005-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [14] ETSI TS 186 016-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Closed User Group (CUG); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [15] ETSI TS 186 017-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Anonymous Communication Rejection (ACR) and Communication Barring (CB); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [16] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [17] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
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 EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". [i.2] ETSI TS 102 587-2: " Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to- Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS&TP) specification". ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 7
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
3 Definitions and abbreviations
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [i.2] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [5]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [5]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5]. Lower Tester (LT): Refer to ISO/IEC 9646-1 [5]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6] and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (see annex B). ACK SIP message like INVITE, REGISTER AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CSCF Call Session Control Function EDS Encoding/Decoding System ETS Executable Test Suite HTML HyperText Markup Language IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem INT IMS Network Testing IP Internet Protocol IPV IP Version ISC interface between SUT and AS ISDN Integrated Services Digital Network IUT Implementation Under Test LAN Local Area Network LT Lower Tester LWS Linear White Spaces MCID Malicious Communication Identification PA Platform Adapter PCO Point of Control and Observation P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement PIXIT Partial Protocol Implementation Extra Information for Testing PSTN Public Switched Telephone Network PTC Parallel Test Component SA SUT Adapter S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol SS Supplementary Services ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 8 SUT System under Test T3RTS TTCN 3 Runtime System TC Test Case TCI TTCN-3 Control Interface TCP check TE TTCN 3 Executable TL Test Logging TM Test Management TP Test Purpose TRI TTCN-3 Runtime Interface TS Test System TSI Transmission Control Protocol TSS Test Suite Structure TTCN Testing and Test Control Notation TTCN-3 Testing and Test Control Notation version 3 UDP User Datagram Protocol UE User Equipment XML eXtensible Markup Language
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4 Abstract Test Method (ATM)
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.1 Network architecture
|
The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF, E-CSCF and IBCF. As illustrated in the following figure the PCOs for the communication between the systems are Gm, Mw, Ic and Isc. Each component can play role of SUT. Figure 1: SUT test interface AS IMSx IMSy UE IMS Mw Ic Isc Gm SIP protocol ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 9
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.2 Protocol architecture
|
The Implementation Under Test (IUT) for which this test case specification applies consists of the SIP protocol (see figure 2). SUT IMS CN SIP/IMS Extension SIP RFC 3261 [4] Compression algorithms (2) UDP TCP Security Algorithms (2) IPV4/IPV6 (1) (LAN) Figure 2: SIP protocol architecture
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3 Test architecture
|
The target SUT to be covered by the test purposes of TS 186 018-2 [3] address the IMS functional entities that are accessible via the following interfaces: Gm, Mw, Ic and ISC. This clause introduces the test configurations that have been used for the test purpose definitions. Depending on the specific configuration the Test System (TS) simulates the behaviour of the UE or another IMS communicating with the SUT. Figures 3 to 7 provide the different configurations in detail. The test configuration is specified in the context of TTCN-3 functions (e.g. f_cf_1UeUp). The letters "P", "S", "I" and "B" etc. indicate the CSCFs within the SUT or TS. If applicable used identifiers on user profiles (see clause 5.3.2.4) have also been added in the figures (e.g. "PCSCFwithHomeUE" corresponds to TTCN-3 constant c_userProfile_PCSCFwithHomeUE).
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.1 Test configuration
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.1.1 Configuration using Gm interface
|
The Gm interface is located between UE and IMS. UE1 SUT IMS P gm ue1home PCSCFwithHomeUE UE1 SUT IMS P gm ue1home PCSCFwithHomeUE Figure 3: Test configuration with CF_1Ue ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 10 IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome Figure 4: Test configuration with CF_2Ue
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.1.2 Configuration using ISC interface
|
The ISC interface provides an access to the AS. AS SUT IMS S isc AS ue1home SCSCFwithHomeUE AS SUT IMS S isc AS ue1home SCSCFwithHomeUE Figure 5: Test configuration with CF_1Scscf AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome Figure 6: Test configuration with CF_1As2Ue
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.1.3 Configuration using Mw and Ic interfaces
|
The Mw or Ic interface is located between two different IMS, e.g. due to at least one user visiting a network outside of the home network. IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic Figure 7: Test configuration with CF_1Scscf1Ibcf ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 11
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2 Test system architecture
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.2 Structure
|
An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 8 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (SA) Platform Adapter (PA) Figure 8: Abstract Test System Architecture A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA) and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [11]. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 12
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.3.1 Sending and receiving SIP/IMS messages
|
Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (see figure 2). In order to forward messages received in the SA to the test suite and to send them to the SUT a clear and unique association between the TTCN-3 TSI ports and the real IP and port addresses used by the SUT is needed during test execution. The SA retrieves this information via values of TTCN-3 module parameters, i.e. PIXITs, and mappings to TSI ports, i.e. triMap operation invocations. TSI port names are the main source for the relating TSI ports with SUT IP addresses and ports. Table 1 provides the relationships for TSI ports and SUT IP addresses and ports. Table 1: TSI port mappings TSI port SUT (IP address, Port Id) Test system (IP address, Port id) UE1 PX_IMS_SUT_PCSCF1_IPADDR, PX_IMS_SUT_PCSCF1_PORT PX_IMS_TS_UE1_IPADDR, PX_IMS_TS_UE1_PORT UE2 PX_IMS_SUT_PCSCF2_IPADDR, PX_IMS_SUT_PCSCF2_PORT PX_IMS_TS_UE2_IPADDR, PX_IMS_TS_UE2_PORT UE3 PX_IMS_SUT_PCSCF3_IPADDR, PX_IMS_SUT_PCSCF3_PORT PX_IMS_TS_UE3_IPADDR, PX_IMS_TS_UE3_PORT PCSCF PX_IMS_SUT_UE_IPADDR, PX_IMS_SUT_UE_PORT PX_IMS_TS_PCSCF_IPADDR, PX_IMS_TS_PCSCF_PORT SCSCF PX_IMS_SUT_AS_IPADDR, PX_IMS_SUT_AS_PORT PX_IMS_TS_SCSCF_IPADDR, PX_IMS_TS_SCSCF_PORT MW_I1 PX_IMS_SUT_ICSCF_IPADDR, PX_IMS_SUT_ICSCF_PORT PX_IMS_TS_SCSCF_IPADDR, PX_IMS_TS_SCSCF_PORT IC1 PX_IMS_SUT_IBCF_IPADDR, PX_IMS_SUT_IBCF_PORT PX_IMS_TS_IBCF1_IPADDR, PX_IMS_TS_IBCF1_PORT AS1 PX_IMS_SUT_SCSCF_IPADDR, PX_IMS_SUT_ SCSCF_PORT PX_IMS_TS_AS1_IPADDR, PX_IMS_TS_AS1_PORT NOTE 1: TSI port names are defined in AtsIms_TestSystem module as part of the ImsComponent type. Module parameters for the address information are defined in LibIms_PIXIT module (see table 3; section LibIms). NOTE 2: For each test configuration listed above a TTCN-3 configuration functions has been implemented with the required mapping and unmapping statements (see table 3; module SS_Ims_TestConfiguration), e.g. f_cf_1Ueup map one UE1 related port of the test system to the SUT. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 13 Figure 9 illustrates the interconnection of TS and SUT in terms of signalling message associations. TS as1 port:sipp port:sipp port:AS1 ue1 port:UE1 port:sipp ic1 port:IC1 port:MW_I1 mwi1 SUT IMS port:UE2 ue2 port:UE3 ue3 SUT AS SUT UE scscf port:SCSCF port:sipp pcscf port:PCSCF port:sipp TS as1 port:sipp port:sipp port:AS1 ue1 port:UE1 ue1 port:UE1 port:sipp ic1 port:IC1 port:IC1 port:MW_I1 port:MW_I1 mwi1 SUT IMS port:UE2 ue2 port:UE2 ue2 port:UE3 ue3 port:UE3 ue3 SUT AS SUT UE scscf port:SCSCF scscf port:SCSCF port:sipp pcscf port:PCSCF pcscf port:PCSCF port:sipp Figure 9: Abstract port association
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.3.2 Security and messages compression feature
|
Security transport layer, and signalling compression may be used transparently to the ATS.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.3.3 Additional SA constraints
|
In order to execute this test suite the SA should support: • communication channel handling (at least UDP and possibly also TCP); • IPv4 transport.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.4 Encoding/Decoding requirements
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers
|
SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use an EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messages. This EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters like "=" or ";" that are used to separate encoded values. LWS Linear White Spaces as defined in RFC 3261 [4]. Parameter name name of header parameters as defined in RFC 3261 [4]. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 14 Parameter value the value of a parameter as defined in RFC 3261 [4]. Undefined method an undefined method is a method other than: "INVITE", "ACK", "OPTIONS", "BYE", "CANCEL" and "REGISTER". Undefined header an undefined header is a header other than general-header, entity-header, request-header and response header as defined in RFC 3261 [4]. Unexpected header an unexpected header is a header, which shall not be present in a specific request message. This definition complies with the definition of NOT APPLICABLE in RFC 3261 [4], clause 20 for request messages. Decoder requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the information provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. For charstring fields the following decoding rules shall be applied by the EDS: 1) Subsequent LWS shall compress to a single space character " ". 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rules shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. However the message is subject to logging as defined in clause 4.3.3 ("Logging conventions"). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 [4] allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the corresponding header field. The SIP ATS has been written assuming only the first format. Therefore, should the EDS receive multiple header fields of the same kind in a SIP message, e.g. of a Via header field, it shall convert them into the equivalent single header field with multiple values. This can be achieved by adding the value of, e.g. the second received Via header field as the last value to the value(s) of the first Via header field. Encoder requirements Encoders shall follow all encoding rules that are defined in RFC 3261 [4] when encoding structured values received from templates. This applies in particular to but it is not restricted to clause 7.3.1 of RFC 3261 [4]. Values of type Raw shall be sent to the SUT without any modification.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
4.3.2.5 Platform adaptation requirements
|
For the execution of this test suite implementations of the following external functions have to be provided (cp. module LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; 3) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 15 calculateDigestResponse(charstring nonce, charstring cnonce, charstring user, charstring realm, charstring passwd, charstring alg, charstring nonceCount, charstring method, charstring qop, charstring URI, charstring HEntity) return charstring; generates a digest response according to RFC 2617 [16] (HTTP Authentication: Basic and Digest Access Authentication), and RFC 1321 [17] The MD5 Message-Digest Algorithm. (See RFC 2617 [16], clause 5 Sample implementation, for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC.)
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5 The ATS development process
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.1 Requirements and Test Purposes
|
For each Test Purpose there is a table defined in clause 5 of TS 186 018-2 [3]. The requirements applicable to this TP are given by a reference to RFC 3261 [4] (SIP), or TS 183 016 [1]. There are no explicit formulations of requirements.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.2 ATS structure
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.2.1 Test case grouping
|
The ATS structure defined in table 2 is based on the structuring of Test Purposes in clause 4 of TS 186 018-2 [3]. The group names in column 2 of table 2 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 018-2 [3], but use the naming conventions defined for the ATS (see clause 5.3.2.2). Table 2: ATS structure MCID terminating_S-CSCF MCID_N01_xxx terminating_AS MCID_N02_xxx destination_UE MCID_U01_xxx
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in column 4 of table 2 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". EXAMPLE: TC_MCID_N01_001: i) the identifier has Group index "MCID_N01", i.e. it is in the subgroup having complete path: SupplementaryService_MCID/SS_MCID_SIPSIP/terminating_S_CSCF; ii) the identifier is the first test case of this group/subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 018-2 [3] and test case names. The TP identifier of TC_ MCID_N01_001 is TP MCID_N01_001. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 16
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3 ATS specification framework
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules - project includes test cases from documents TS 186 005-2 [13], TS 186 016-2 [14], TS 186 017-2 [15] and TS 186 018-1 [2]; 2) LibIms modules; 3) LibSip modules (RFC 3261 [4]); 4) LibCommon modules (taken from an improved version of TS 102 351 [12]). NOTE 1: Due to the common LibSip and LibIms library approach with some other parallel running projects there is necessary to create tag version of all library modules. Table 3 shows the organization of the ATS as library of modules. Table 3: Library of modules Module Class Module Id Description AtsCommon SS_Ims_PICS Module Parameter declarations associated with PICS. SS_Ims_PIXITS SIP common Module Parameter declarations associated with PIXIT. SS_Ims_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations. SS_Ims_TestSystem TSI components, test system internal ports. SS_Ims_TestCases Test case definitions. SS_Ims_TCFunctions Test case functions. LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT. LibIms_Interface IMS component. LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note). LibIms_Templates Modified templates with IMS specific header fields. LibIms_Steps functions using IMS specific types. LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT. LibSip_Interface SIP component. LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note). LibSip_SDPTypes SDP types and constants. LibSip_Templates Basic and modified templates with SIP specific header fields. LibSip_Steps SIP specific behaviour function library. LibSip_XMLTypes XML types for SIP tests. XSDAUX Basic types used in XML. LibCommon LibCommon_AbstractData Generic data types for a stack and its operations. LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean). LibCommon_DataStrings Bit and Octet string types. LibCommon_Sync Co-ordination/synchronization of test components. LibCommon_TextStrings Basic character and string types with fixed length. LibCommon_Time Time handling functions and module parameter. LibCommon_VerdictControl Basic functions for setting of test component verdicts. NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only. NOTE 2: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 17
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2 Use of TTCN-3
| |
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [7] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP IMS ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and naming conventions. 4) TTCN-3 is human-readable. 5) TTCN-3 specification is feasible, implementable, compliable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. 10) Giving enough design freedom to the test equipment manufacturers. Fulfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.2 TTCN-3 naming conventions
|
Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the SIP/IMS ATS are based on the following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in clause 8 [i.1] should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (see table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 18 Table 4 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. Table 4: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup SIP message type Use upper-case initial letter none Request, Response Note 2 SIP header type Use upper-case initial letter none MaxForwards Note 2 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component ref Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use naming as specified in clause 5.2.2 TC_ TC_IMST2_xxxxx Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameter Use initial upper case letters PX PX_MAC_ID Note 1 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: In this case it is acceptable to use underscore as a word delimiter. NOTE 2: This convention has been used in TS 102 027-3 [11] (SIP ATS).
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.3 Additional TTCN-3 IMS/SIP naming convention
|
In addition to the general TTCN-3 naming conventions listed in the previous clause the following rules have been applied to templates. Table 5: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Message template Use lower-case initial letter, followed by message type in upper-case letters (for requests) or "Response" keyword m_ m_BYE_Request_UE Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_SUBSCRIBE_Request_IMS Templates have been defined in a 3-step approach. First, a dummy template is defined for every message type and direction, e.g. m_ACK_Dummy and mw_ACK_Dummy. Secondly, for each message type and direction a base template has been defined that modifies respective dummy templates and includes all mandatory header fields. Template identifiers of these modifications include the keyword "Base", e.g. m_ACK_Request_Base, mw_ACK_Request_Base. More specific templates are then derived on the basis of these base templates and modify fields that need to be restricted for a very specific purpose, e.g. m_ACK_Request_route, etc. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 19
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.4 Additional concepts and conventions
|
IMS procedures and tests require the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular parameter collections (records) that are related to IMS users and interfaces. The so-called user profile information (cp. module LibSip_SIPTypesAndValue) contains the following elements: user profile identifier, current IP port and address to exchange SIP messages, IP port and address for further contact, IP address used by the TS to exchange media streams, public identity (home domain, username), quality-of-protection parameters, authentication parameters (see RFC 2617 [16], clause 3.2.2). A list of user profile identifiers (module LibIMS_SIPTypesAndValue) introduces available settings for UE with different locations and homes: e.g. c_userProfile_UE1atSUThome should be used in case where UE1 is a registered user of SUT and currently not visiting another IMS. User profiles are constructed from module parameters (cp. module LibIMS_Steps). Additionally some interface information is needed to indicate or validate IMS component addresses to be used in SIP header fields like Via, Route, etc. They are defined in a similar way as user profiles (cp. LibIms_SIPTypeAndValues) and contain IP address, port and domain information. For example c_interfaceProfile_IMS_SUT_IBCF1 defines an IBCF access point at the SUT. Interface profiles are also constructed based on module parameters (cp. module LibIMS_Steps).
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.5 PICS information
|
No TTCN-3 control part has been defined for this test suite. If applicable PICS information is evaluated at the beginning of each test case definition using an "if" statement. Log information is provided in case that a test has not been executed due to PICS setting violation.
|
1f1ab48bf07a660f0e3392826799d4d9
|
186 018-3
|
5.3.2.6 Test Suite documentation
|
In order to allow browsing of the SIP/IMS ATS without the use of a specific TTCN-3 test development environment, the TTCN ATS is made available in HTML format with hyperlinks between entities in the ATS. The documentation in the ATS makes use of special comment tags used by the tool that converts the ATS to the HTML format. These tags are defined in clause 9 of [8] and the tags shown in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc Describes the purpose of a particular piece of TTCN-3 code. The description should be concise yet informative and describe the function and use of the construct. @remark Adds extra information, such as the highlighting of a particular feature or aspect not covered in the description. @img Associates images with a particular piece of TTCN-3 code. @see Refers to other TTCN-3 definitions in the same or another module. @url Associates references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return Provides additional information on the value returned by a given function. @param Documents the parameters of parameterized TTCN-3 definitions. @version States the version of a particular piece of TTCN-3 code. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 20 Annex A (normative): Partial PIXIT proforma 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 PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and IMS-related PIXIT. NOTE: The tables in this clause have been generated automatically from the TTCN-3 modules. A.2.1 SIP-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The SIP-related PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions on SIP and TS address information that are not used in this ATS and therefore not present in table A.1. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 21 Table A.1: SIP-related PIXIT items No PIXIT Name Description 1 PX_SIP_SDP_dyn charstring for SDP dynamic port 2 PX_SIP_SDP_b_modifier charstring for SDP bandwidth modifier 3 PX_SIP_SDP_b_bandwidth integer for SDP bandwidth value 4 PX_SIP_SDP_encoding charstring for SDP media attribute encoding supported by the IUT 5 PX_SIP_TRANSPORT charstring for Used Transport in upper case "UDP"/"TCP" 6 PX_SIP_SUT_PORT integer for SUT port number to exchange SIP messages 7 PX_SIP_SUT_IPADDR charstring for SUT IP address to exchange SIP messages 8 PX_SIP_TS1_PORT integer for port number used by the TS1 to exchange SIP messages 9 PX_SIP_TS1_IPADDR charstring for IP address used by the TS1 to exchange SIP messages 10 PX_SIP_TS1_LOCAL_DOMAIN charstring for identity of the tester local domain 11 PX_SIP_TS1_LOCAL_USER charstring for identity of the tester local user 12 PX_SIP_TS1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 13 PX_SIP_TS2_PORT integer for port number used by the TS2 to exchange SIP messages 14 PX_SIP_TS2_IPADDR charstring for IP address used by the TS2 to exchange SIP messages 15 PX_SIP_TS2_LOCAL_DOMAIN charstring for identity of the tester local domain 16 PX_SIP_TS2_LOCAL_USER charstring for identity of the tester local user 17 PX_SIP_TS2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 18 PX_SIP_REGISTRATION boolean for the SIP user if it have to register itself before executing a test case 19 PX_SIP_SUT_REGISTRAR_DOMAIN charstring for REGISTRAR domain 20 PX_SIP_CheckConversation boolean for True, if conversation check is implemented 21 PX_SIP_REGISTER_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for REGISTER messages 22 PX_SIP_INVITE_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for INVITE messages 23 PX_SIP_SUT_UE1_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server. The value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 24 PX_SIP_SUT_UE1_USERNAME charstring for RFC 2617 [16], clause 3.2.2 username: The name of user in the specified realm 25 PX_SIP_SUT_UE1_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 26 PX_SIP_SUT_UE2_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server. The value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 27 PX_SIP_SUT_UE2_USERNAME charstring for RFC 2617 [16, ]clause 3.2.2 username: The name of user in the specified realm 28 PX_SIP_SUT_UE2_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 29 PX_SIP_T1 float for T1 RTT estimate (500 ms) 30 PX_SIP_TF float for TDELAY default value for timeout on outgoing SIP request (i.e. 64*T1) ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 22 A.2.2 IMS-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.2: IMS-related PIXIT items (Ports and addresses of IUT) No PIXIT Name Description 1 PX_IMS_SUT_PCSCF1_IPADDR charstring for SUT - PCSCF1 IP address to exchange SIP messages - connection point for UE1 2 PX_IMS_SUT_PCSCF1_PORT integer for SUT - PCSCF1 port number to exchange SIP messages - connection point for UE1 3 PX_IMS_SUT_PCSCF1_HOME_DOMAIN charstring for SUT/PCSCF1 domain - connection point for UE1 4 PX_IMS_SUT_UE1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE1 5 PX_IMS_SUT_UE1_HOME_DOMAIN charstring for identity of the tester UE1 local domain 6 PX_IMS_SUT_UE1_PUBLIC_USER charstring for identity of the tester UE1 local user 7 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring for RFC 2617 [16], clause 3.2.2 username of UE1: The name of user in the specified realm 8 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username 9 PX_IMS_SUT_UE1_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options of UE1: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 10 PX_IMS_SUT_UE1_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE1 11 PX_IMS_SUT_PCSCF2_IPADDR charstring for SUT - PCSCF2 IP address to exchange SIP messages - connection point for UE2 12 PX_IMS_SUT_PCSCF2_PORT integer for SUT - PCSCF2 port number to exchange SIP messages - connection point for UE2 13 PX_IMS_SUT_PCSCF2_HOME_DOMAIN charstring for SUT/PCSCF2 domain - connection point for UE2 14 PX_IMS_SUT_UE2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE2 15 PX_IMS_SUT_UE2_HOME_DOMAIN charstring for identity of the tester UE2 local domain 16 PX_IMS_SUT_UE2_PUBLIC_USER charstring for identity of the tester UE2 local user 17 PX_IMS_SUT_UE2_PRIVAT_USERNAME charstring for RFC 2617 [16], clause 3.2.2 username of UE2: The name of user in the specified realm 18 PX_IMS_SUT_UE2_PRIVAT_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd of UE2: A known shared secret, the password of user of the specified username 19 PX_IMS_SUT_UE2_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options of UE2: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 20 PX_IMS_SUT_UE2_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE2 21 PX_IMS_SUT_UE3_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE3 22 PX_IMS_SUT_UE3_HOME_DOMAIN charstring for identity of the tester UE2 local domain 23 PX_IMS_SUT_UE3_PUBLIC_USER charstring for identity of the tester UE3 local user 24 PX_IMS_SUT_UE3_PRIVAT_USERNAME charstring for RFC 2617 [16], clause 3.2.2 username of UE3: The name of user in the specified realm 25 PX_IMS_SUT_UE3_PRIVAT_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd of UE3: A known shared secret, the password of user of the specified username ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 23 No PIXIT Name Description 26 PX_IMS_SUT_UE3_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options of UE3: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection. 27 PX_IMS_SUT_UE3_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE3 28 PX_IMS_SUT_UE4_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE4 29 PX_IMS_SUT_UE4_HOME_DOMAIN charstring for identity of the tester UE2 local domain 30 PX_IMS_SUT_UE4_PUBLIC_USER charstring for identity of the tester UE4 local user 31 PX_IMS_SUT_UE4_PRIVAT_USERNAME charstring for RFC 2617 [16], clause 3.2.2 username of UE4: The name of user in the specified realm 32 PX_IMS_SUT_UE4_PRIVAT_PASSWD charstring for RFC 2617 [16], clause 3.2.2.2 passwd of UE4: A known shared secret, the password of user of the specified username 33 PX_IMS_SUT_UE4_QOP charstring for RFC 2617 [16], clause 3.2.1 qop options of UE4: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 34 PX_IMS_SUT_UE4_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE4 35 PX_IMS_SUT_unknownUE_PUBLIC_USER charstring for identity of unknown UE public user 36 PX_IMS_SUT_EMERGENCY_HOME_DOMAIN charstring for identity of emergency service local domain 37 PX_IMS_SUT_EMERGENCY_SERVICE charstring for identity of the emergency service 38 PX_IMS_SUT_EMERGENCY_SERVICE_INVALID charstring for identity of the invalid emergency service 39 PX_IMS_SUT_IBCF1_IPADDR charstring for SUT/IBCF1 IP address to exchange SIP messages 40 PX_IMS_SUT_IBCF1_PORT integer for SUT/IBCF1 port number to exchange SIP messages 41 PX_IMS_SUT_IBCF1_HOME_DOMAIN charstring for SUT/IBCF1 domain 42 PX_IMS_SUT_IBCF2_IPADDR charstring for SUT/IBCF2 IP address to exchange SIP messages 43 PX_IMS_SUT_IBCF2_PORT integer for SUT/IBCF2 port number to exchange SIP messages 44 PX_IMS_SUT_IBCF2_HOME_DOMAIN charstring for SUT/IBCF2 domain 45 PX_IMS_SUT_PCSCF_IPADDR charstring for SUT/P-CSCF IP address to exchange SIP messages 46 PX_IMS_SUT_PCSCF_PORT integer for SUT/P-CSCF port number to exchange SIP messages 47 PX_IMS_SUT_PCSCF_HOME_DOMAIN charstring for SUT/P-CSCFdomain 48 PX_IMS_SUT_SCSCF_IPADDR charstring for SUT/S-CSCF IP address to exchange SIP messages 49 PX_IMS_SUT_SCSCF_PORT integer for SUT/S-CSCF port number to exchange SIP messages 50 PX_IMS_SUT_SCSCF_HOME_DOMAIN charstring for SUT/S-CSCFdomain 51 PX_IMS_SUT_ICSCF_IPADDR charstring for SUT/I-CSCF IP address to exchange SIP messages 52 PX_IMS_SUT_ICSCF_PORT integer for SUT/I-CSCF port number to exchange SIP messages 53 PX_IMS_SUT_ICSCF_HOME_DOMAIN charstring for SUT/I-CSCFdomain 54 PX_IMS_SUT_AS_IPADDR charstring for SUT - AS IP address to exchange SIP messages - connection point for SCSCF 55 PX_IMS_SUT_AS_PORT integer for SUT - AS port number to exchange SIP messages - connection point for SCSCF 56 PX_IMS_SUT_AS_HOME_DOMAIN charstring for SUT/AS domain 57 PX_IMS_SUT_IMGCF_IPADDR charstring for SUT/I-MGCF IP address to exchange SIP messages 58 PX_IMS_SUT_IMGCF_PORT integer for SUT/I-MGCF port number to exchange SIP messages 59 PX_IMS_SUT_IMGCF_HOME_DOMAIN charstring for SUT/I-MGCFdomain ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 24 No PIXIT Name Description 60 PX_IMS_SUT_CONF_PORT integer for SUT/conference port number to exchange SIP messages 61 PX_IMS_SUT_CONF_HOME_DOMAIN charstring for SUT/conference domain 62 PX_IMS_SUT_CONF_FACTORY_NAME charstring for conference factory URI name 63 PX_IMS_TS_UE1_IPADDR charstring for IP address used by the UE1 to exchange SIP messages 64 PX_IMS_TS_UE1_PORT integer for port number used by the UE1 to exchange SIP messages 65 PX_IMS_TS_UE2_IPADDR charstring for IP address used by the UE2 to exchange SIP messages 66 PX_IMS_TS_UE2_PORT integer for port number used by the UE2 to exchange SIP messages 67 PX_IMS_TS_UE3_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 68 PX_IMS_TS_UE3_PORT integer for port number used by the UE3 to exchange SIP messages 69 PX_IMS_TS_UE4_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 70 PX_IMS_TS_UE4_PORT integer for port number used by the UE3 to exchange SIP messages 71 PX_IMS_TS_IBCF_IPADDR charstring for TS/IBCF IP address to exchange SIP messages 72 PX_IMS_TS_IBCF_PORT integer for TS/IBCF port number to exchange SIP messages 73 PX_IMS_TS_ICSCF_IPADDR charstring for TS/I-CSCF IP address to exchange SIP messages 74 PX_IMS_TS_ICSCF_PORT integer for IUT/I-CSCF port number to exchange SIP messages 75 PX_IMS_TS_PCSCF_IPADDR charstring for TS/P-CSCF IP address to exchange SIP messages 76 PX_IMS_TS_PCSCF_PORT integer for IUT/P-CSCF port number to exchange SIP messages 77 PX_IMS_TS_SCSCF_IPADDR charstring for TS/S-CSCF IP address to exchange SIP messages 78 PX_IMS_TS_SCSCF_PORT integer for TS/S-CSCF port number to exchange SIP messages 79 PX_IMS_TS_SCSCF_HOME_DOMAIN charstring for TS/S-CSCFdomain 80 PX_IMS_TS_ECSCF_IPADDR charstring for TS/E-CSCF IP address to exchange SIP messages 81 PX_IMS_TS_ECSCF_PORT integer for TS/E-CSCF port number to exchange SIP messages 82 PX_IMS_TS_IMS1UE_PUBLIC_USER charstring for public userinfo/displayname addressing IMS1UE (simulated by the TS) 83 PX_IMS_TS_IMS1UE_HOME_DOMAIN charstring for TS/domain 84 PX_IMS_TS_ISUP_PUBLIC_USER charstring for public userinfo addressing ISUPUE (simulated by the TS) 85 PX_IMS_TS_ISUP_HOME_DOMAIN charstring for ISUP TS/domain or IPAddres 86 PX_IMS_TS_AS1_IPADDR charstring for TS/AS1 IP address to exchange SIP messages 87 PX_IMS_TS_AS1_PORT integer for TS/AS1 port number to exchange SIP messages 88 PX_IMS_TS_AS1_HOME_DOMAIN charstring for TS/AS1 domain 89 PX_IMS_TS_AS2_IPADDR charstring for TS/AS2 IP address to exchange SIP messages 90 PX_IMS_TS_AS2_PORT integer for TS/AS2 port number to exchange SIP messages 91 PX_IMS_TS_AS2_HOME_DOMAIN charstring for TS/AS2 domain ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 25 Table A.3: IMS-related PIXIT (ATS specific) No PIXIT Name Description 1 PX_Timeout_MCID_BYE float default timer value for PX_Timeout_MCID_BYE (0 s to 120 s) 2 PX_Timeout_MCID_O_ID float default timer value for PX_Timeout_MCID_O_ID (4 s to 10 s) 3 PX_SIP_NameAddr_PAsserted NameAddr default value for PAsserted(with sip scheme) 4 PX_SIP_NameAddr_PPreferred NameAddr default value for PPreferred(with sip scheme) ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 26 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18601803v020201p0.zip which accompanies the present document. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 27 Annex C (informative): Bibliography ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification". ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". ETSI ETSI TS 186 018-3 V2.2.1 (2010-11) 28 History Document history V2.1.1 July 2009 Publication V2.2.1 November 2010 Publication
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
1 Scope
|
The present document specifies the test suite structure and test purposes of the Malicious Communication Identification (MCID) service based on the stage three of IMS MCID simulation service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The MCID service will store session related information independent of the service requested.
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol Specification". [2] ETSI TS 186 018-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [4] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1]". [5] ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 6 [6] ETSI ES 283 027: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks [3GPP TS 29.163 (Release 7), modified]".
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] IETF RFC 3966: "The tel URI for Telephone Numbers". [i.2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
3 Definitions and abbreviations
| |
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 181 002 [3], TS 181 006 [4], TR 180 000 [5] and the following apply: communication information: information collected and registered by the MCID service identity information: includes all the information (RFC 3966 [i.1] // RFC 3986 [i.2]) identifying a user, including trusted (network generated) and/or untrusted (user generated) identities trusted identity: network generated user address information untrusted identity: user generated user address information NOTE: This may contain additional information.
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACM Address Complete Message ANM Answer Message AS Application Server CDIV Communication DIVersion services HOLD communication HOLD IAM Initial Address Message IDR Identification Request message IM IP Multimedia IMS IP Multimedia Subsystem IP Internet Protocol IRS Identification Response message ISDN Integrated Service Digital Network MCID Malicious Call Identification MGCF Media Gateway Control Function NGN Next Generation Network PSTN Public Switched Telephone Network REL Release message RLC Release Complete message S-CSCF Service - Call Session Control Function SDP Session Description Protocol SIP Session Initiation Protocol ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 7 TP Test Purposes TSS Test Suite Structure UE User Equipment URI Uniform Resource Identifier
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
4 Test Suite Structure (TSS)
|
MCID terminating_S-CSCF MCID_N01_xxx terminating_AS MCID_N02_xxx destination_UE MCID_U01_xxx SIP-ISUP SS MCID TP507xxx ISUP-SIP SS MCID TP614xxx
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5 Test Purposes (TP)
| |
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-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 1). Table 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 <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.1.2 Test strategy
|
As the base standard TS 183 016 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 018-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 8
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.2 TPs for Malicious Communication Identification (MCID)
| |
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.2.1 Actions at the terminating S-CSCF
|
TSS MCID/terminating_S-CSCF TP MCID_N01_001 SUB reference clause 4.5.2 Selection expression PICS 1/3 Test purpose Called user has permanent MCID subscription Ensure that the S-CSCF forwards the INVITE request to the AS if the called subscriber has a permanent MCID subscription. Preconditions: SIP header values: Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS MCID/terminating_S-CSCF TP MCID_N01_002 SUB reference clause 4.5.2 Selection expression PICS 1/4 Test purpose Called user has case by case MCID subscription Ensure that the S-CSCF forwards the INVITE request to the AS if the called subscriber has a case by case MCID subscription. Preconditions: SIP header values: reINVITE without session modification Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK Store the session related information BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 9 TSS MCID/terminating_S-CSCF TP MCID_N01_003 SUB reference clause 4.5.2 Selection expression PICS 1/4 AND PICS 1/5 Test purpose Called user has permanent MCID subscription Ensure that the S-CSCF forwards the INVITE request to the AS if the called subscriber has a case by case MCID subscription. A XML MIME body is received indicating MCID request. Preconditions: SIP header values: reINVITE without session modification XML mcid McidRequestIndicator = ‘1’ Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK Store the session related information BYE BYE 200 OK BYE 200 OK BYE
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.2.2 Actions at the AS of the terminating user
|
TSS MCID/terminating_AS TP MCID_N02_001 SUB reference clause 4.5.2 Selection expression PICS 1/9 Test purpose The AS requests identification information in an INFO request, if no identification was received in the initial INVITE. Ensure that the AS sends an INFO request including a XML mcid request McidRequestIndicator set to 1 if the initial INVITE does not contain information of the originating party. Ensure that the received INFO contains the following headers: • Destination Party Identity Information included in the INVITE Request-URI; • Originating Party Identity Information included in the INFO body; • Local time and date of the invocation in the network serving the called user; • Call diversion information received in the History-Info header, if the History-Info header field is included in the request (escaped Reason); and • Contact header field. Preconditions: SIP header values: INFO XML mcid request McidRequestIndicator = ‘1’ Comments: UA C SUT UA S INVITE 100 Trying INFO (XML mcid request) 200 OK INFO INVITE 100 Trying INFO (XML mcid response) 200 OK INFO 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 10 TSS MCID/terminating_AS TP MCID_N02_002 SUB reference clause 4.5.2 Selection expression PICS 1/3 Test purpose The AS stores the session information if the called user has permanent MCID subscription Ensure that the AS stores the session related information if the called subscriber has a permanent MCID subscription. Ensure that the stored information contains the following header and information: • Destination Party Identity Information included in the Request-URI; • Originating Party Identity Information included in the P-Asserted-Identity header field, if the P-Asserted-Identity header field is included in the request; • Local time and date of the invocation in the network serving the called user; • Call diversion information received in the History-Info header, if the History-Info header field is included in the request (escaped Reason); • Referred-By header field when available; • Contact header; • To header; and • From header. Preconditions: SIP header values: Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS MCID/terminating_AS TP MCID_N02_003 SUB reference clause 4.5.2 Selection expression PICS 1/4 Test purpose The AS stores the session information if the called user has case by case MCID subscription Ensure that the AS stores the session related information if the called subscriber has a case by case MCID subscription and a reINVITE was received to invoke the MCID service. Ensure that the stored information contains the following header and information: • Destination Party Identity Information included in the Request-URI; • Originating Party Identity Information included in the P-Asserted-Identity header field, if the P-Asserted-Identity header field is included in the request; • Local time and date of the invocation in the network serving the called user; • Call diversion information received in the History-Info header, if the History-Info header field is included in the request (escaped Reason); • Referred-By header field when available; • Contact header; • To header; and • From header. Preconditions: SIP header values: reINVITE without session modification Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK Store the session related information BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 11 TSS MCID/terminating_AS TP MCID_N02_004 SUB reference clause 4.5.2 Selection expression PICS 1/4 AND PICS 1/5 Test purpose The AS stores the session information if the called user has case by case MCID subscription. Invoke contains a XML mcid request. Ensure that the AS stores the session related information if the called subscriber has a case by case MCID subscription and a reINVITE was received to invoke the MCID service. The reINVITE contains a XML mcid request body. Ensure that the stored information contains the following header and information: • Destination Party Identity Information included in the Request-URI; • Originating Party Identity Information included in the P-Asserted-Identity header field, if the P-Asserted-Identity header field is included in the request; • Local time and date of the invocation in the network serving the called user; • Call diversion information received in the History-Info header, if the History-Info header field is included in the request (escaped Reason); • Referred-By header field when available; • Contact header; • To header; and • From header. Preconditions: SIP header values: reINVITE without session modification XML mcid request McidRequestIndicator = ‘1’ Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK Store the session related information BYE BYE 200 OK BYE 200 OK BYE TSS MCID/terminating_AS TP MCID_N02_005 SUB reference clause 4.5.2 Selection expression PICS 1/4 Test purpose The AS holds the call state after a BYE from the originating UE Ensure that the AS holds the call state while TMCID-BYE is running. When TMCID-BYE is expired, the BYE is forwarded to the terminating UE. Preconditions: SIP header values: Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE 200 OK BYE TMCID-BYE expires BYE 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 12 TSS MCID/terminating_AS TP MCID_N02_006 SUB reference clause 4.5.2 Selection expression PICS 1/4 Test purpose The AS holds the call state after a BYE from the originating UE in the confirmed dialogue Ensure that the AS holds the call state while TMCID-BYE is running. Ensure that the AS stores the session related information if a reINVITE to invoke the MCID service was received while TMCID-BYE is running Ensure that the BYE is forwarded to the terminating UE. Preconditions: SIP header values: reINVITE without session modification Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE 200 OK BYE INVITE 200 OK INVITE ACK Store the session related information BYE 200 OK BYE TSS MCID/terminating_AS TP MCID_N02_007 SUB reference clause 4.5.2 Selection expression PICS 1/4 Test purpose The AS deletes the stored session information if no MCID request was received Ensure that the AS deletes all session related information if no MCID request was received from the served user. Preconditions: SIP header values: Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 13
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.2.3 Actions at the destination UE
|
TSS MCID/destination_UE TP MCID_U01_001 SUB reference clause 4.5.2 Selection expression NOT PICS 1/1 Test purpose The UE sends a MCID request Ensure that the UE is able to invoke MCID. The UE sends a reINVITE without session modification. Preconditions: SIP header values: reINVITE without session modification Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK BYE BYE 200 OK BYE 200 OK BYE TSS MCID/destination_UE TP MCID_U01_002 SUB reference clause 4.5.2 Selection expression PICS 1/2 Test purpose The UE sends a MCID request using the XML McidRequestIndicator Ensure that the UE is able to invoke MCID. The UE sends a reINVITE without session modification. Ensure that the UE is able to send a XML MIME body with the McidRequestIndicator set to 1. Preconditions: SIP header values: reINVITE without session modification XML mcid request McidRequestIndicator = ‘1’ Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication INVITE 200 OK INVITE ACK BYE BYE 200 OK BYE 200 OK BYE
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.3 Interaction with other services
| |
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.3.1 Communication Diversion Services (CDIV)
|
It is not possible to test MCID in case of CDIV. ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 14
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.4 Test purposes for the ISUP/SIP Interworking
| |
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.4.1 Interworking at the I-MGCF
|
TP507001 Reference: ES 283 027 [6], clause 7.4.4 Selection criteria: NOT PICS 1/6 TSS reference: SIP-ISUP/SS/MCID/ Preconditions: Test purpose: No interworking MGCF sends IRS Ensure that the SUT if an IDR is received returns an IRS message. The MCID response indicator is set to "MCID not included". The SIP signalling procedure is not disrupted. SIP Parameter values: No influence ISUP Parameter values: IDR: MCID requested IRS: MCID not included SIP MGCF ISUP INVITE IAM 100 Trying IDR IRS 180 Ringing ACM 200 OK INVITE ANM ACK Communication BYE REL Comments: 200 OK BYE RLC TP507002 Reference: ES 283 027 [6], clause 7.4.4 Selection criteria: NOT PICS 1/6 TSS reference: SIP-ISUP/SS/MCID/ Preconditions: Test purpose: No interworking timeout T39 Ensure that the SUT if an IDR is received, no IRS is sent. The SIP signalling procedure is not disrupted SIP Parameter values: No influence ISUP Parameter values: IDR: MCID requested SIP MGCF ISUP INVITE IAM 100 Trying IDR T39 timeout 180 Ringing ACM 200 OK INVITE ANM ACK Communication BYE REL Comments: 200 OK BYE RLC ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 15
|
86ee5808f5cc5965b2c7d7b47202895b
|
186 018-2
|
5.4.2 Interworking at the O-MGCF
|
TP614001 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (McidRequestIndicator) Ensure that the XML mcid McidRequestIndicator contained in a received INFO request mapped into the MCID request indicator requested in the sent IDR SIP Parameter values: INFO XML mcid request McidRequestIndicator = ‘1’ ISUP Parameter values: IDR: MCID request indicator: MCID requested ISUP MGCF SIP IAM INVITE 100 Trying IDR(MCID request indicator) INFO (XML mcid request) 200 OK INFO ACM 180 Ringing ANM 200 OK INVITE ACK Communication REL BYE Comments: RLC 200 OK BYE TP614002 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 AND PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (HoldingIndicator) Ensure that the XML mcid HoldingIndicator is mapped into the MCID request indicator holding requested in the sent IDR SIP Parameter values: INFO: XML mcid request HoldingIndicator = ‘1’ ISUP Parameter values: IDR: Holding indicator (national use): holding requested ISUP MGCF SIP IAM INVITE 100 Trying IDR(MCID request indicator) INFO (XML mcid request) 200 OK INFO ACM 180 Ringing ANM 200 OK INVITE ACK Communication REL BYE Comments: RLC 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 16 TP614003 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (McidResponseIndicator) Ensure that MCID response indicator provided, contained in an IRS is mapped into the XML mcid response McidResponseIndicator. SIP Parameter values: INFO: XML mcid request McidRequestIndicator = ‘1’ INFO: XML mcid response McidResponseIndicator = ‘1’ ISUP Parameter values: IDR: MCID request indicator: MCID requested IRS: MCID response indicator: MCID provided ISUP MGCF SIP IAM INVITE 100 Trying IDR(MCID request indicator) INFO (XML mcid request) 200 OK INFO IRS (MCID response indicator) INFO (XML mcid response) 200 OK INFO ACM 180 Ringing ANM 200 OK INVITE ACK Communication REL BYE Comments: RLC 200 OK BYE TP614003 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 AND NOT PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (HoldingProvidedIndicator) Ensure that MCID response indicator holding provided, contained in an IRS is mapped into the XML mcid response HoldingProvidedIndicator. SIP Parameter values: INFO: XML mcid request HoldingIndicator = ‘1’ INFO: XML mcid response HoldingProvidedIndicator = ‘0’ ISUP Parameter values: IDR: Holding indicator (national use) IRS: Hold provided indicator (national use) ISUP MGCF SIP IAM INVITE 100 Trying IDR(MCID request indicator) INFO (XML mcid request) 200 OK INFO IRS (no MCID response indicator) INFO (XML mcid response) 200 OK INFO ACM 180 Ringing ANM 200 OK INVITE ACK Communication REL BYE Comments: RLC 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 17 TP614004 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 AND PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (HoldingProvidedIndicator) Ensure that MCID response indicator holding provided, contained in an IRS is mapped into the XML mcid response HoldingProvidedIndicator (Holding indicator is not for national use). SIP Parameter values: INFO: XML mcid request HoldingIndicator = ‘1’ INFO: XML mcid response HoldingProvidedIndicator = ‘1’ ISUP Parameter values: IDR: Holding indicator: holding requested IRS: Hold provided indicator holding provided ISUP MGCF SIP IAM INVITE 100 Trying IDR(MCID request indicator) INFO (XML mcid request) 200 OK INFO IRS (no MCID response indicator) INFO (XML mcid response) 200 OK INFO ACM 180 Ringing ANM 200 OK INVITE ACK Communication REL BYE Comments: RLC 200 OK BYE ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 18 History Document history V1.0.0 June 2008 Publication
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
1 Scope
|
The present document specifies the protocol implementation conformance statement of the Malicious Call Communication Identification (MCID) service based on the stage IMS Malicious Communication Identification simulation service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The MCID service will store session related information independent of the service requested.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol Specification". [2] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [3] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1]". [4] ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". [5] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [6] IETF RFC 3966: "The tel URI for Telephone Numbers". ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 6 [7] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.