hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.4 Simple fast forward of CoD using trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0004 (S3A-1201) Summary: User requests fast forward on a paused CoD in trick play mode without reaching the end of recording References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPT... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.5 Simple fast backward on CoD using trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0005 (S3A-1201) Summary: User requests fast backward on a paused CoD using trick play in trick play mode without reaching the beginning of the recording References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.1 Configuration: CF_IMS_IPTV Required Equipment: ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.6 Jump to specific location in CoD content | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0006 (S3A-1201) Summary: User jumps to specific point in CoD using trick-play References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Cor... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.7 Quit watching CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0007 (S3A-1301) Summary: User quits watching CoD References: TS 182 027 [1], clause 8.4.3; TS 183 063 [2], clause 5.1.4.4.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core IMS and I... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.8 Resume CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0008 (S3A-1401) Summary: User resumes a CoD from the last watching point References: TS 182 027 [1], clause 8.3.3; TS 183 063 [2], clauses 5.1.3.4 and 8.1.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test con... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.9 CoD termination by IPTV AS | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0009 (-) Summary: IPTV AS stops user from watching CoD References: TS 182 027 [1], clause 8.4.3; TS 183 063 [2], clause 5.1.4.4.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core IMS... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6 Video on Demand (CoD) using Method 2 | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.1 Start CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0001 (S3A-1102) Summary: User watches Video on Demand References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core IMS an... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.2 Pause CoD with trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0002 (S3A-1201) Summary: User pauses a CoD using trick-play References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.3 Play CoD with trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0003 (S3A-1201) Summary: User plays a CoD using trick-play References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core I... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.4 Fast forward CoD using trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0004 (S3A-1202) Summary: User fast forwards CoD using trick play References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.5 Fast backward CoD using trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0005 (S3A-1202) Summary: User fast backwards CoD using trick play References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS,... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.6 Jump to specific location in CoD content | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0006 (S3A-1202) Summary: User jumps in CoD to specific point using trick-play References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions:... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.7 Terminate CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0007 (S3A-1302) Summary: User quits watching CoD References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core IMS and IPT... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.8 Resume CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0008 (S3A-1402) Summary: User resumes a CoD from the last watching point References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.9 CoD termination by IPTV AS | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_0009 (S3A-1402) Summary: AS IPTV stops user from watching CoD References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Cor... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.6.10 CoD termination at the end of stream | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD2_00010 (S3A-1701) Summary: User watches a CoD until its end References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clause 5.1.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS Pre-test conditions: • UE, CoDS, Core I... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.7 NPVR using Method 1 | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.7.1 Impulsive recording request | Interoperability Test Description Identifier: TD_IMS_IPTV_nP1_0001 (S3A-1901) Summary: User requests an impulsive recording of a broadcast TV channel References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV Head End, T&A, PVRS Pre-test co... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.7.2 Scheduled recording request | Interoperability Test Description Identifier: TD_IMS_IPTV_nP1_0002 (S3A-2001) Summary: User requests a scheduled recording of a broadcast TV channel References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV Head End, T&A, PVRS Pre-test con... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.7.3 Watching a recorded nPVR content | Interoperability Test Description Identifier: TD_IMS_IPTV_nP1_0003 (S3A-2201) Summary: User watches a recorded content References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, PVRS Pre-test conditions: • UE, PVRS, Core IMS and IPTV AS are co... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.8 NPVR - Method 2 | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.8.1 Impulsive recording request | Interoperability Test Description Identifier: TD_IMS_IPTV_nP2_0001 (S3A-1902) Summary: User requests to park and pickup a broadcast TV channel References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV Head End, T&A, PVRS Pre-test condition... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.8.2 Scheduled recording request | Interoperability Test Description Identifier: TD_IMS_IPTV_nP2_0002 (S3A-2102) Summary: User requests the scheduled recording of a broadcast TV channel References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV Head End, T&A, PVRS Pre-test c... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.8.3 Watching a recorded content | Interoperability Test Description Identifier: TD_IMS_IPTV_nP2_0003 (S3A-2202) Summary: User watches a recorded nPVR content References: TS 182 027 [1], clause 8.5; TS 183 063 [2] Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, PVRS Pre-test conditions: • UE, PVRS, Core IMS and IPTV AS a... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9 User General Content (UGC) | UGC (User-generated Content) refers to various kinds of media content, that are produced by end-users (TS 181 016 [12], clause A.9.13). They are two kinds of UGC procedures: • The creation of UGC content: the user is allowed to declare and upload/upstream his own content to the network. • The watching of UGC content: t... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9.1 UGC declaration procedures | Interoperability Test Description Identifier: TD_ IMS_IPTV_UGC_0001 Summary: UE declares a new UGC content References: TS 182 027 [1], clause 8.9.2; TS 183 063 [2], clauses 5.1.8.1 and 5.3.5.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • UE profile is configured... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9.2 UGC creation procedures | 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_UGC_0002 Summary: UE creates a UGC content References: TS 182 027 [1], clause 8.9.2; TS 183 063 [2], clauses 5.1.8.3.1, 5.3.5.3 and 5.4.4.1 C... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9.3 UGC watching procedures | As specified in TS 182 027 [1], clause 8.9.3, the UE may select UGC content on several methods: • Selection through SSF, see TS 182 027 [1], clause 8.2 Step 4. • Pre-selection. Other methods are out of scope. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9.3.1 UGC watching procedures: Pre-selection (using Method 2) | Interoperability Test Description Identifier: TD_IMS_IPTV_UGC_0004 Summary: User requests to watch a UGC content – pre selection (using method 2) References: TS 182 027 [1], clause 8.9.3; TS 183 063 [2], clauses 5.1.8.4, 5.3.5.4, 5.4.4.2 and clause A.3.1A Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Co... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.9.3.2 UGC watching procedures: selection through the SSF (using Method 1) | Interoperability Test Description Identifier: TD_IMS_IPTV_UGC_0003 Summary: User requests to watch a UGC content – selection through SSF (using method 1) References: TS 182 027 [1], clause 8.9.3; TS 183 063 [2], clauses 5.1.8.4, 5.3.5.4 and 5.4.4.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS,... |
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 ... |
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 conditio... |
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 condi... |
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.1... |
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 ... |
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 ... |
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, Cor... |
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 ... |
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... |
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: ... |
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 PR... |
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 diagram... |
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 dura... |
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 parent... |
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-P... |
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... |
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 P... |
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... |
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 C... |
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: t... |
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 wat... |
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/I... |
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 ar... |
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... |
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... |
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 Un... |
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 T... |
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 ... |
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... |
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 ... |
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 UE1atSUTho... |
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 ... |
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 (... |
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 re... |
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... |
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(charst... |
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.... |
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 ... |
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... |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-3 | 5.3.2 Use of TTCN-3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.