hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 6.1 Architecture for interception of IMS | The Point of Interception shall be at premises of the CSP, i.e. IRI-IIF and CC-IIF shall reside in equipment under full control (physical access, etc.) of the CSP. Figure 1 (in clause 4.2) identifies the generic architecture for LI. The specific provision of the CC-IIF and IRI-IIF in the NGN for IMS services is as show... |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 6.2 Activation, deactivation and interrogation | The principles described in TS 133 107 [7] apply, with the exception that the list of target identities is restricted to be a SIP URI or a TEL URL. |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 6.3 Intercept Related Information | Communications to or from a targeted subscriber and communications initiated on behalf of a targeted subscriber are intercepted at the P-CSCF or S-CSCF as described in TS 133 107 [7]. The stage 2 definition for interception of IMS found in TS 133 107 [7] shall apply for TISPAN NGN R1. Annex A specifies the parts of TS ... |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 6.4 Content of Communication | Interception of the content of communications takes place at transport processing functional entities identified in the TISPAN NGN R1 architecture (ES 282 001 [1]). Transport processing entities that may provide the CC-IIF are: • An Access Media Gateway Function (A-MGF). • A Core Border Gateway Function (C-BGF). • An I... |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 7 Identification of target of interception | |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 7.1 ISDN/PSTN services | In the context of PSTN/ISDN emulation and services, the target shall be identified in the service domain by a globally unique E.164 identity. NOTE: The PES offers seamless ISDN/PSTN service to existing core network customers who will remain identified by their E.164 identity that may be mapped to a system unique SIP-id... |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 7.2 IMS services | IMS service users shall be identified by either a SIP-url or a tel-url [6]. |
c1de86b509a7d0992f5b1174a12013d6 | 187 005 | 8 Security considerations | The guidelines for security identified in TS 101 331 [3] apply. The provision and actions of the interception measure should be confidential and not discoverable, or alterable, by unauthorized parties. ETSI ETSI TS 187 005 V1.1.1 (2006-12) 13 Annex A (normative): Endorsement statement for TS 133 107 For the stage 2 def... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 1 Scope | The present document specifies interoperability tests for IMS-based IPTV system for NGN Release 3. It covers the use of main IPTV functionality via different methods as defined in NGN Release 2 as well as NGN Release 3 new use cases and features for IPTV and possible interactions with Voice/Data communications such as ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 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... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 182 027 (V3.4.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". [2] ETSI TS 183 063 (V3.5.2):... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 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 EG 202... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project A-RACS Access - Resource and Admission Control Subsystem AAA AA-Answer AAR AA-Request AS (IMS) Application Server BC Broadcast CF (Test) Configuration CoD Content On Demand CoDS Content on Demand Server ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4 IMS-based IPTV Interoperability Test Specification | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.1 Introduction | The IMS-based IPTV interoperability test descriptions (TDs) defined in the following clauses are mainly derived from MSF 2008.169.06 [i.3], TS 183 063 [2] and TS 182 027 [1]. More specifically, these TDs focus on SIP/SDP [5], HTTP [7], RTSP [4], IGMP [6] related messaging procedures without RACS described in clauses 5,... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2 Test Prerequisites | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1 IP Version and protocols | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1.1 IP | The present document assumes that IP-based protocols all use IPv4. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1.2 RTSP | The present document assumes RTSP [3] messages are sent only via TCP. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1.3 SIP | The present document assumes that all SIP [4] messages are sent via UDP to ensure retransmission procedures based on SIP only and to simplify the match procedure between the message flows and real network capture. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1.4 IGMP | The present document assumes that IPTV aware UE requests for multicast group use IGMPv3 [6]. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.1.5 Media transport | The present document assumes that content is transported using one of the following transport technologies: MPEG2TS encapsulation or direct RTP transport (e.g. H264 over RTP). Further it is assumed that transport of IPTV content within MPEG2-TS layer over RTP and UDP is performed according the procedures defined in TS ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.2 Authentication and Security | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.2.1 SIP | The present document assumes that no SIP-based authentication is performed. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.2.2 HTTP | Personalized service selection is out of the scope of the document. Hence, no HTTP authentication is required from the UE toward SSF or SCF. Also no authentication proxy is needed between the UE and the SCF. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.3 Supported Options | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.3.1 Signalling Compression | "No SigComp" is the default signalling configuration in all test descriptions. Tests may be executed with signalling compression if the required nodes support it. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.3.2 SIP Provisional Message Reliability | The present document assumes there is no use of SIP 100rel option tag. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.3.3 SIP precondition option tag | The present document assumes there is no use of SIP precondition option tag. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.3.4 SIP timer option tag (Session Timers) | The present document assumes there is use of SIP timer option tag which supports session timer extension. The inclusion of this option tag in a Supported header field of a SIP request or response indicates that the UE is capable of performing refreshes. The inclusion of this option tag in a Require header of a SIP requ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.4 Content related options | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.4.1 Encrypted contents | The present document assumes that encryption is not used for CoD or BC content provisioning. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.4.2 Digital Rights Management | The present document assumes DRM is not used for CoD or BC content provisioning. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.4.3 FEC | The present document assumes that FEC disabled for CoD and BC content provisioning. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.5 Service discovery | Service discovery should follow the procedures defined in TS 102 539 [10] and TS 102 323 [11]. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 11 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.6 Miscellaneous | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.2.6.1 Network Address Translation (NAT) and Firewall function | The present document assumes there is neither NAT nor Firewall function activated. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3 Test Architecture | In figure 1, various nodes of an IMS-based IPTV system that pertain to testing are introduced. For each node configuration is described and relevant points of observation (POs) are identified. Based on these nodes a static test architecture is defined. Figure 1 shows the abstract test architecture of an IMS-based IPTV ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1 IPTV Nodes | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.1 Core IMS | This node contains P-CSCF, I-CSCF and S-CSCF functions as well as potentially (a part of) the UPSF. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.1.1 Relevant Reference Points | The Gm reference point between the IMS Core and the IP aware UE is used as a point of observation (PO) for testing purposes. The ISC reference point is between the IMS Core and IPTV AS and used as a PO for testing purposes. The y2 reference point is between the IMS Core and the PVRS and CoDS and used as a PO for testin... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.1.2 Node Configuration | The Core IMS should be configured to support the pre-requisites outlined in clause 4.2. The UPSF should be configured with the following user identities. Private Identity Public Identity (SIP URI) Public Identity 2 (Tel URI) Default Public Identity Filter criteria userIPTV_priv userIPTV na 1 contact IPTV AS |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.2 IPTV aware UE | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.2.1 Relevant Reference Points | The Gm interface is used as a PO for interoperability tests towards the IMS Core. The Xa interface is used as a PO for interoperability tests towards the IPTV AS. The Xc and Xd (Dj) interfaces are used as POs for interoperability tests towards the PVRS, CoDS and TV Head End. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.2.2 Node Configuration | The IP aware UE should be configured to support the pre-requisites outlined in clause 4.2. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.3 IPTV Application Server (AS) | This node contains SSF, SDF, and SCF functions as well as may contain also (a part of) the UPSF. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.3.1 Relevant Reference Points | The Xa interface is used as a PO towards the IPTV aware UE whereas the ISC interface is used as a PO towards the IMS Core. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.3.2 Node Configuration | The IPTV AS should be configured to support the pre-requisites outlined in clause 4.2. The media content available in the PVRS, CoDS and TV Head End has to be described within the IPTV AS. IPTV specific data information associated with the user has to be described within the IPTV AS [9]. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.4 OMA Instant Messaging and Presence Service (AS) | This node provides capabilities for Instant Messaging and Presence Service (TS 183 063 [2], clause 5.1.17.1). ETSI ETSI TS 186 020 V3.1.1 (2011-07) 13 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.5 Content on Demand Server (CoDS) | This node contains CoD-MCF and CoD-MDF functions and services based on CoD as UGC. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.5.1 Relevant Reference Points | The y2 reference point is used as a PO between the Core IMS and the CoDS. The Xd reference point is used as PO between the UE and the CoDS. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.5.2 Node Configuration | The CoDS should be configured to support the pre-requisites outlined in clause 4.2. The media contents as described in the EPGs have to be available on the CoDS. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.6 Personal Video Recorder Server (PVRS) | This node contains nPVR-MCF and nPVR-MDF functions. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.6.1 Relevant Reference Points | The y2 reference point is used as a PO between the Core IMS and the PVRS. The Xd reference point is used as PO between the UE and the PVRS. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.6.2 Node Configuration | The PVRS should be configured to support the pre-requisites outlined in clause 4.2. The media contents as described in the EPGs have to be available on the PVRS. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.7 Transport and Access (T&A) | This node contains transport control and processing functions, A-RACS, SPDF, NASS and RCEF. The latter is located in the IP-Edge Node. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.7.1 Relevant Reference Points | The Xd, Xc and Dj reference points are used as POs between the UE and the transport node. Gq' reference point is used as Pos between SPDF and CORE IMS. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.1.7.2 Node Configuration | The T&A should be configured to support the pre-requisites outlined in clause 4.2. Regarding multicast support, the function has to implement IGMPv3, IGMPv2 with SSM (source specific mapping) and in case the multicast sources are not directly connected a CORE network a multicast protocol (e.g.: PIM). |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2 External Nodes | This clause lists nodes which are required for performing some of the interoperability tests but not consider to be part of the SUT, i.e. supporting equipment required for the execution of tests. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.1 TV Head End | This node contains BC-MDF and BC-MCF functions. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 14 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.1.1 Relevant Reference Points | The Xd reference point is used as PO between the UE and the TV Head End. y2 reference point is used between CORE IMS and BC-MCF. It is not a PO so far. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.2 Node Configuration | The TV Head End should be configured to support the pre-requisites outlined in clause 4.2. TV End Head should provide at least one BC channel unconditionally. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.3 Time Shifted TV Server | This node contains TsTV-MDF and TsTV -MCF functions. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.3.1 Relevant Reference Points | The Xd reference point is used as PO between the UE and the TsTV Server. y2 reference point is used between CORE IMS and TsTV-MCF. It is not a PO so far. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.4 Node Configuration | The TsTV Server should be configured to support the pre-requisites outlined in clause 4.2. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.5 Advertising Nodes | The nodes described below are involved in the different types of Advertising architecture (TS 182 027 [1], clause 8.4 and annex E). |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.5.1 Internal Advertising Nodes | NOTE: Internal Advertising Nodes not covered by the present document. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.5.2 SCTE-130 Advertising Nodes | This is the Advertising architecture defined by SCTE-130 ([i.4]). TISPAN and SCTE-130 entities communicate through three AD interfaces are: ADz, ADx and ADy. 4.3.2.5.2.1 Relevant Reference Points ADz reference point is used as PO between the UE and the external SCTE-130 Advertizing Sub-system. ADx reference point is us... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.2.5.3 OMA MobAd Advertising Nodes | NOTE: OMA MobAd Advertising Nodes not covered by the present document. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 15 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.3 Summary of interfaces and protocols | Figure 1 includes also IPTV reference points to be monitored in interoperability testing. Figure 2 identifies again the relevant reference points and provides more information about the protocols they use. FE/ Reference point (protocol) UE IMS core UPSF SDF SSF SCF MCF MDF ECF/ EFF UE --- Gm (SIP/SDP) --- via Core IMS ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.3.4 Method 1 and Method 2 | In the interoperability test descriptions defined in the present document, two methods regarding the procedures using RTSP for IMS-based IPTV are used. More information on these methods is available in clause 7 and annex Q of [2]. |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4 Test Descriptions | This clause defines IMS-based IPTV interoperability test descriptions (TD) for systems composed of equipment by different vendors. Each TD includes a test sequence describing user interactions with IPTV equipment as well as messages exchanged between IPTV equipment at selected standardized reference points. TD identifi... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.10 End of CoD | TD_IMS_IPTV_CoD2 Content on Demand using method 2 4.4.6 4.4.6.1 Start CoD 4.4.6.2 Pause CoD with trick-play 4.4.6.3 Play CoD with trick-play 4.4.6.4 Fast forward CoD using trick-play 4.4.6.5 Fast backward CoD using trick-play 4.4.6.6 Jump to specific location in CoD content 4.4.6.7 Terminate CoD 4.4.6.8 Resume CoD 4.4.... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.1 Service Attachment, Service Discovery and Selection | In the following TDs, we consider step 1 of the IPTV Aware UE start-up procedure, i.e. Network attachment (UE to NASS), as being out of the scope of the test. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 18 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.1.1 Manual configuration of SSF information in pull mode | Interoperability Test Description Identifier: TD_ IMS_IPTV_ADS_0001 (MSF S3A-0101) Summary: UE displays EPG with manual SSF address configuration References: TS 182 027 [1], clause 8.2; TS 183 063 [2], clause 6.1.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test conditions: • IP... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.1.2 Automatic provisioning of SSF in pull mode | Interoperability Test Description Identifier: TD_ IMS_IPTV_ADS_0002 (MSF S3A-0101) Summary: UE displays EPG with automatic SSF provision in pull mode References: TS 182 027 [1], clause 8.2; TS 183 063 [2], clauses 5.1.2.2 and 6.1.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-test... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.1.3 Automatic provisioning of SSF in push mode | Interoperability Test Description Identifier: TD_IMS_IPTV_ADS_0003 (MSF S3A-0101) Summary: UE can display EPG with automatic SSF provision in push mode References: TS 182 027 [1], clause 8.2; TS 183 063 [2], clauses 5.1.2.1 and 6.1.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS Pre-te... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2 Broadcast TV | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.1 Session initiation without RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0001 (S3A-0201) Summary: User requests to watch broadcast TV channel References: TS 182 027 [1], clause 8.3.1; TS 183 063 [2], clauses 5.1.3.1 and 8.1.2.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV HEAD END, T&A Pre-te... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.2 Channel Zapping without RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0002 (S3A-0301) Summary: User changes to a HD channel while watching a SD broadcast TV References: TS 182 027 [1], clause 8.3.4; TS 183 063 [2], clauses 5.1.3.5 and 8.1.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV HEAD... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.3 Session termination without RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0003 (S3A-0401) Summary: User quits watching broadcast TV References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clauses 5.1.4.2 and 7.2.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, TV HEAD END, T&A Pre-test conditions... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.4 Session initiation with RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0004 Summary: User requests to watch broadcast TV channel using QoS References: TS 182 027 [1], clause 8.3.1; TS 183 063 [2], clauses 5.1.3.1 and 8.1.2.1, TS 183 017 [9], clauses 5.1.1 and 5.2.1 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Co... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.5 Channel Zapping with RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0005 Summary: User changes to a HD channel while watching SD broadcast TV using QoS References: TS 182 027 [1], clause 8.3.4; TS 183 063 [2], clauses 5.1.3.5 and 8.1.2; TS 183 017 [9], clauses 5.1.2 and 5.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPT... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.2.6 Session termination with RACS | Interoperability Test Description Identifier: TD_IMS_IPTV_BC_0006 Summary: User quits watching broadcast TV using QoS References: TS 182 027 [1], clause 8.4.1; TS 183 063 [2], clauses 5.1.4.2 and 7.2.1; TS 183 017 [9], clauses 5.1.3 and 5.2.3 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3 Broadcast TV with trick-play using Method 1 | More information about Method 1 is given in clause 4.3.4. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 27 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3.1 Initiate trick-play on a live broadcast channel | Interoperability Test Description Identifier: TD_IMS_IPTV_BC1_0001 (S3A-0501) Summary: User initiates trick mode while watching a broadcast TV channel References: TS 182 027 [1], clause 8.3.5; TS 183 063 [2], clauses 5.1.3.3.1 and 8.1.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3.2 Play in trick-play mode | Interoperability Test Description Identifier: TD_IMS_IPTV_BC1_0002 (S3A-0601) Summary: User requests the normal play mode on a broadcast TV channel in trick play mode 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, TV HEAD E... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3.3 Simple fast forward trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_BC1_0003 (S3A-0601) Summary: User requests fast forward on a paused broadcast TV channel 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 U... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3.4 Fast backward trick-play to beginning of recorded content | Interoperability Test Description Identifier: TD_IMS_IPTV_BC1_0004 (S3A-0701) Summary: User requests fast backward on a paused broadcast TV channel in trick play mode until the beginning of the recording is reached References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.1 Configuration: CF_IMS_IPTV Required Equipment: I... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.3.5 Fast forward to move from trick-play to live broadcast mode | Interoperability Test Description Identifier: TD_IMS_IPTV_BC1_0005 (S3A-0801) Summary: User requests fast forward until the end of recording is reached and moves from trick play to live broadcast TV channel References: TS 182 027 [1], clause 8.3.6; TS 183 063 [2], clauses 5.1.3.3.2, 7.2.1 and 8.1.2.1 Configuration: CF_... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4 Broadcast TV with trick-play using Method 2 | More information about Method 2 is given in clause 4.3.4. ETSI ETSI TS 186 020 V3.1.1 (2011-07) 33 |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4.1 Initiate trick-play on a live broadcast channel | Interoperability Test Description Identifier: TD_IMS_IPTV_BC2_0001 (S3A-0502) Summary: User initiates trick mode while watching a broadcast TV channel References: TS 182 027 [1], clause 8.3.5; TS 183 063 [2], clauses 5.1.3.3.1 and 8.1.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4.2 Play in trick-play mode | Interoperability Test Description Identifier: TD_IMS_IPTV_BC2_0002 (S3A-0602) Summary: User requests the normal play mode on a broadcast TV channel in trick play mode References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS, TV HEAD E... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4.3 Simple fast forward trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_BC2_0003 (S3A-0602) Summary: User requests fast forward on a paused broadcast TV channel in trick play mode without reaching the end of recording References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware U... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4.4 Fast backward trick-play to beginning of recorded content | Interoperability Test Description Identifier: TD_IMS_IPTV_BC2_0004 (S3A-0702) Summary: User request a fast backward on a paused broadcast TV channel in trick play mode References: TS 182 027 [1]; TS 183 063 [2], clause 7.2.2 Configuration: CF_IMS_IPTV Required Equipment: IPTV aware UE, Core IMS, IPTV AS, CoDS, TV HEAD ... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.4.5 Fast forward to move from trick-play to live broadcast mode | Interoperability Test Description Identifier: TD_IMS_IPTV_BC2_0005 (S3A-0802) Summary: User requests fast forward until the end of recording is reached and moves from trick play to live broadcast TV channel References: TS 182 027 [1], clause 8.3.6; TS 183 063 [2], clauses 5.1.3.3.2, 7.2.2 and 8.1.2.1 Configuration: CF_... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5 Content on Demand (CoD) using Method 1 | |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.1 Start CoD | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0001 (S3A-1101) Summary: User requests to watch Content 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,... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.2 Pause CoD with trick-play | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0002 (S3A-1201) Summary: User requests to pause a 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, Core IMS a... |
e92ae14f0d05d3f1f7f623039c9d4b32 | 186 020 | 4.4.5.3 Play CoD in trick-play mode | Interoperability Test Description Identifier: TD_IMS_IPTV_CoD1_0003 (S3A-1201) Summary: User requests play a 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, Core IMS and I... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.