ETSI TS 183 064 V2.1.1 (2008-10)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Dedicated IPTV subsystem stage 3 specification

DTS/TISPAN-03137-NGN-R2

General Information

• Status: Published
• Publication Date: 21-Oct-2008
• Technical Committee: TISPAN 3 - TISPAN Protocols
• Current Stage: 12 - Completion
• Due Date: 08-Aug-2008
• Completion Date: 22-Oct-2008

Standards Content (Sample)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Dedicated IPTV subsystem stage 3 specification

2 ETSI TS 183 064 V2.1.1 (2008-10)

Reference
DTS/TISPAN-03137-NGN-R2
Keywords
IP, TV, Stage3
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 183 064 V2.1.1 (2008-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Applicability . 10
4.1 Concept and Approach . 10
4.2 Overview . 10
4.3 Functional Entities . 13
4.3.1 User Equipment(UE) . 13
4.3.2 Service Discovery and Selection (SD&S) . 13
4.3.3 Customer Facing IPTV Applications (CF-IPTV-Apps). 13
4.3.4 IPTV Control (IPTV-C) . 13
4.3.5 Media Control Function (MCF) . 13
4.3.6 Media Delivery Function (MDF) . 13
4.3.7 IPTV User Data Function (IPTV UDF) . 13
4.3.8 NGN User Data Access Function (NGN UDAF) . 14
5 Procedures using HTTP for dedicated IPTV . 14
5.1 User Equipment (UE) . 14
5.1.1 Procedures for SD&S. 14
5.1.1.1 Push mode . 14
5.1.1.2 Pull Mode . 14
5.1.2 Procedure for Service Configuration . 14
5.1.3 Procedure for Authentication . 15
5.1.4 Procedure for Customer Facing IPTV Applications . 15
5.1.5 Procedure for Notifications . 15
5.1.6 Procedure for Messaging . 15
5.1.7 Procedure for presence information . 15
6 Procedures using RTSP for dedicated IPTV . . 15
6.1 User Equipment (UE) and Control Functions . 17
6.1.1 Procedure for BTV service . 17
6.1.2 Procedure for CoD service . 17
6.1.3 Procedure for BTV with trick modes service . 19
6.1.4 Procedure for time-shift TV . 19
6.1.5 Procedure for nPVR . 20
6.2 IPTV Control (IPTV-C) . 20
6.2.1 Procedure for BTV service . 20
6.2.2 Procedure for CoD service . 20
7 Procedures using IGMP for dedicated -IPTV . . 20
7.1 User Equipment (UE) . 20
7.1.1 Procedure for BTV service . 21
7.1.1.1 Procedure for starting to receive multicast . 21
7.1.1.2 Procedure for stopping to receive multicast . 21
7.1.1.3 Procedure for channel switching . 21
7.1.2 Procedure for BTV with trick modes service . 21
7.2 Transport Functions . 22
8 Procedures using SIP for dedicated -IPTV . 22
ETSI
4 ETSI TS 183 064 V2.1.1 (2008-10)
8.1 User Equipment (UE) . 22
8.1.1 Procedure for Notifications . 22
8.1.2 Procedure for Messaging . 22
9 Procedures using DVBSTP for dedicated-IPTV . 22
9.1 User Equipment (UE) . 22
9.1.1 Service Discovery and Selection (SD&S) . 22
9.1.1.1 Request of DVB Service Discovery and Selection data . 22
9.1.1.2 Request of DVB Broadband Content Guide . 23
9.2 Service Discovery and Selection (SD&S) . 23
9.2.1 Procedure for Service Selection . 23
9.2.1.1 Delivery of DVB Service Discovery and Selection data . 23
9.2.1.2 Delivery of DVB Broadband Content Guide . 23
10 Procedures using RTP/RTCP and UDP for dedicated IPTV . 23
10.1 User Equipment (UE) . 23
10.1.1 Procedures for Real-Time Transport. 23
10.1.1.1 Transport using MPEG2TS . 23
10.1.2 Procedure for Real-Time Transport Error Correction . 23
10.1.2.1 Unidirectional Transport Error Correction . 23
10.2 Media Delivery Function (MDF) . 24
10.2.1 Procedures for Real-Time Transport. 24
10.2.1.1 Transport using MPEG2TS . 24
10.2.2 Procedure for Real-Time Transport Error Correction . 24
10.2.2.1 Unidirectional Transport Error Correction . 24
Annex A (informative): Functional entity relations and example signalling flows of NGN
based dedicated IPTV operations . 25
A.1 Functional entities relations and overview of the NGN based dedicated IPTV procedures. 25
A.2 Example signalling flows of service discovery and selection . 26
A.3 Signalling flow and protocol RTP/RTCP for Retransmission. 27
A.3.1 User Equipment (UE) procedure for BTV service . 27
A.3.2 User Equipment (UE) procedure for CoD service . 28
A.4 Example signalling flows of nPVR . 29
A.5 Example signalling flows of IPTV service for messaging . 30
A.6 Example signalling flows of IPTV presence services . 32
A.6.1 Example signalling flows of IPTV presence notification using PA . 32
A.6.2 Example signalling flows of IPTV presence notification using RLS . 34
A.6.3 Example signalling flows of IPTV presence updates . 35
A.7 Example signalling flows of IPTV service interaction with NGN/IMS services . 35
A.7.1 Example signalling flows of IPTV service handling of incoming calls . 36
A.8 Example signalling flows of Notifications . 38
Annex B (normative): UE capabilities and example signalling flows of NGN based dedicated
IPTV operations . 40
B.1 UE capabilities . 40
B.2 Signalling flows of BTV . . 41
B.3 Signalling flows of CoD . 43
B.3.1 CoD Session initiation . 43
B.3.2 CoD Session termination . 44
B.4 Signalling flows of BTV with trick modes. 44
History . 46

ETSI
5 ETSI TS 183 064 V2.1.1 (2008-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
ETSI
6 ETSI TS 183 064 V2.1.1 (2008-10)
1 Scope
The present document provides the stage 3 description of the dedicated IPTV subsystem based on the architecture and
stage 2 information flows described in TS 182 028 [4].
The protocol enhancements will form the scope of new or enhanced protocol specifications.
The interaction with other NGN subsystems such as PES, IMS and RACS will be considered.
The current release is applicable to:
• the interface between the User Equipment (UE) and the SD&S;
• the interface between the User Equipment (UE) and Customer facing IPTV Applications (CF-IPTV-Apps);
• the interface between the User Equipment (UE) and IPTV Control (IPTV-C);
• the interface between the User Equipment (UE) and Media Control Functions (MCF);
• the interface between the User Equipment (UE) and Media Delivery Functions (MDF);
• the interface between the Customer facing IPTV Applications (CF-IPTV-Apps) and IPTV Control (IPTV-C);
• the interface for access to IPTV User Data Function (IPTV UDF);
• the interface between the IPTV Control (IPTV-C) and Media Control Functions (MCF);
• the interface for access to NGN User Data Access Function (NGN UDAF).
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.
ETSI
7 ETSI TS 183 064 V2.1.1 (2008-10)
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 ES 282 001 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); NGN Functional Architecture".
[2] ETSI ES 282 004 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network
Attachment Sub-System (NASS)".
[3] ETSI ES 282 003 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); Resource and Admission Control
Sub-System (RACS): Functional Architecture".
[4] ETSI TS 182 028 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); IPTV Architecture; Dedicated subsystem for
IPTV functions".
[5] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB
Services over IP Based Networks".
[6] IETF RFC 2326 (April 1998): "Real Time Streaming Protocol (RTSP)".
[7] IETF RFC 2617 (June 1996): " HTTP Authentication: Basic and Digest Access Authentication".
[8] ETSI TS 102 539: "Digital Video Broadcasting (DVB); Carriage of Broadband Content
Guide (BCG) information over Internet Protocol (IP)".
[9] IETF RFC 2616 (June 1999): "Hypertext Transfer Protocol - HTTP/1.1".
[10] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant
Messaging".
[11] ETSI TS 183 041 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); Messaging service using the IP Multimedia (IM)
Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of
3GPP TS 24.247 Release 6]".
[12] IETF RFC 3856 (August 2004): "Presence Event Package for the Session Initiation
Protocol (SIP)".
[13] ETSI TS 182 008 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional
description [Endorsement of 3GPP TS 23.508 Release 7 and OMA-AD-Presence_SIMPLE-
V1_0]".
[14] IETF RFC 4662 (August 2006): "Session Initiation Protocol (SIP) Event Notification Extension
for Resource Lists".
[15] IETF RFC 4825 (May 2007): "The Extensible Markup Language (XML). Configuration Access
Protocol (XCAP)".
[16] IETF RFC 5025 (December 2007): "Presence Authorization Rules".
[17] ETSI TS 183 063 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification".
[18] IETF RFC 3265 (June 2002): "Session Initiation Protocol (SIP)-Specific Event Notification".
[19] IETF RFC 1321 (April, 1992): "The MD5 Message-Digest Algorithm".
[20] IETF RFC 3376 (October 2002): "Internet Group Management Protocol, Version 3".
ETSI
8 ETSI TS 183 064 V2.1.1 (2008-10)
[21] IETF RFC 3810 (June 2004): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
[22] ETSI TS 183 017 (Release 2): "Telecommunications and Internet Converged Services and
Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER
protocol for session based policy set-up information exchange between the Application
Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification".
[23] IETF RFC 4585 (July 2006): "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)".
[24] IETF RFC 4588 (July 2006): "RTP Retransmission Payload Format".
[25] IETF RFC 3261: "SIP: Session Initiation Protocol".
[26] ETSI TS 184 009 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN) Rules covering the use of TV URIs for the
Identification of Television Channels".
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] ETSI TS 187 003 (Release 2): "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
UE (converged): end user device, eg set top box or enhanced TV, capable of supporting IPTV services and services
provided by other NGN subsystems
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASF Application Server Function
BC BroadCast
BCG Broadband Content Guide
BTV Broadcast TV
CF Customer Facing
CFIA Customer Facing IPTV Applications
CoD Content on Demand
CoD-MF Content on Demand Media Functions
CSS Cascading Style Sheets
Ct2 interfaces name defined in TS 182 028 [4]
Di interfaces name defined in TS 182 028 [4]
DVB Digital Video Broadcast
DVBSTP Digital Video Broadcasting Service discovery and selection Transport Protocol
ECF Elementary Control Function
EFF Elementary Forwarding Function
EPG Electric Program Guide
FB FeedBack
FE Functional Entity
HTTP HyperText Transfer Protocol
ETSI
9 ETSI TS 183 064 V2.1.1 (2008-10)
IGMP Internet Group Management Protocol
IGMPv2 Internet Group Management Protocol version 2
IGMPv3 Internet Group Management Protocol version 3
IMS IP Multimedia Subsystem
IPTV Internet Protocol TeleVision
IPTV-C IPTV Control
IPv4 Internet Protocol version 4
IUDF IPTV User Data Function
LMB Linear Media Broadcast
MBwTM Media Broadcast with Trick Modes
MC MulitCast
MCF Media Control Function
MDF Media Delivery Function
MLD Multicast Listener Discovery (protocol)
MLDv1 Multicast Listener Discovery version 1
MLDv2 Multicast Listener Discovery version 2
NGN Next Generation Network
nPVR network-side Personal Video Recorder
PS Presence Server
PUA Presence User Agent
RACS Resources Admission Control Sub-system
RLS Resource List Server
RR Receiver Report
RSI Receiver Summary Information
RTCP Real Time Control Protocol
RTCPSSM RTCP extension for Source Specific Multicast
RTP Real Time transport Protocol
RTSP Real Time Streaming Protocol
Sa interfaces name defined in TS 182 028 [4]
SD&S Service Discovery and Selection
SDES Source Description RTCP Packet
SDP Session Initiation Protocol
Sh interfaces name defined in TS 182 028 [4]
SIP Session Initiation Protocol
SMTP Simple Mail Transfer Protocol
SSRC Synchronization SouRCe
TCP Transmission Control Protocol
Tr interfaces name defined in TS 182 028 [4]
TsTV Time-shift TV
Ud interfaces name defined in TS 182 028 [4]
UDP User Datagram Protocol
UE User Equipment
UPSF User Profile Server Function
URI Uniform Resource Identifier
URL Uniform Resource Locator
WEB4CE Web-based Protocol and Framework for Consumer Electronics
Xc interfaces name defined in TS 182 028 [4]
XCAP XML Configuration Access Protocol
Xd interfaces name defined in TS 182 028 [4]
XDMS XML Data Management Server
XML Extensible Markup Language
ETSI
10 ETSI TS 183 064 V2.1.1 (2008-10)
4 Applicability
The following clauses explain the concept and approach used to define the protocols for the dedicated IPTV subsystem.
4.1 Concept and Approach
This clause outlines concept and approach adopted in the present document. The approach is then applied to protocol
selections, mapping to interfaces and protocol extensions.
The document focuses on defining protocols for flexible functional architecture described in [4], which can:
• Allow development of new IPTV subsystem in NGN;
• Integrate existing IPTV subsystem in NGN;
• Extend both to support other NGN services.
In order to achieve high level of flexibility and support integration of existing subsystems, the work is focused on
evaluating and endorsing protocols already defined for similar functions in [5] and other standard bodies. Protocol
extensions are defined where applicable as well as overall applicability to the end-to-end architecture [4].
For example, recommendations are made how to integrate DVB compliant UE without modifications and DVB
compliant system with minimal modification to the service layer.
4.2 Overview
The clause describes applicability of the protocols discussed further in the present document to reference points defined
in TS 182 028 [4]. The overall functional architecture for the dedicated IPTV service conforms to [4].
Figure 1 presents mapping of protocols to interfaces in dedicated NGN-IPTV and to interworking with other NGN
subsystems and common components.
ETSI
11 ETSI TS 183 064 V2.1.1 (2008-10)
UE &
NGN
Legend: NGN dedicated IPTV model
Apps Intr
Ug
NGN Apps
UDP/RTP/RTCP
IUDF
Diameter
Tr
NGN App UDF
RTSP
SD&S
HTTP
Intr NGN
IGMP/MLD
and CFIA Sh
UPSF
DVBSTP
CFIA
Other
Sh
Not defined
Ss
IUDF
Tr
Ct2
IPTV-C
Ud
Sa
MCF
Xp
MDF
Gq’
e2
e4
UE
NACS RACS
Xc
Dj
ECF/EFF
Xd
NOTE: Xc and Xd are logical interfaces that can be decomposed into Dj and optionally Di, Ds or Iz interfaces
depending on the location of the MCF or MDF as described in [4] clause 5.2.5 for Xc and clause 5.1.6 for
Xd.
Figure 1: Protocols mapped to NGN dedicated IPTV functional architecture
ETSI
12 ETSI TS 183 064 V2.1.1 (2008-10)
Table 1: NGN dedicated IPTV functional entities and protocols used on interfaces
FE/ UE IPTV-C CFIA SD&S UPSF IUDF MCF MDF ECF/
Referenc EFF
e .point
(protocol)
UE
--- Ct2 Tr Tr --- --- Xc Xd Dj, Di
(RTSP), (HTTP) (HTTP, (RTSP) (UDP/ IGMP/
(HTTP, DVBSTP) RTP MLD
Optional) /RTCP)
IPTV-C Ct2 --- Ss --- Sh Ud Sa --- ---
(RTSP), (HTTP) (Diameter) (not (RTSP)
(HTTP, defined)
Optional)
CFIA Tr Ss Sh (not --- --- --- --- ---
(HTTP) (HTTP) (Diameter) defined)
SD&S Tr --- (not --- --- --- --- --- ---
(HTTP, defined)
DVBSTP)
UPSF
--- Sh Sh --- --- --- --- --- ---
(Diameter) (Diameter)
IUDF
--- Ud --- --- --- --- Ud --- ---
(not (not
defined) defined)
MCF Xc Sa --- --- --- Ud --- Xp ---
(RTSP) (RTSP) (not (not
defined) defined)
MDF Xd --- --- --- --- --- Xp ---
(UDP/ (not
RTP/RTCP) defined)
ECF/ EFF --- --- --- --- --- --- --- --- ---

NOTE 1: NGN dedicated IPTV protocol model is required to comply with standards applicable for NGN dedicated
IPTV as defined below.
Usage of the HTTP protocol across the following interfaces is described in clause 5:
• interface Tr;
• interface Xc;
• interface Ct2 (Optional).
Usage of the HTTP protocol for interactions between NGN Applications and UE is described in annex E.
Usage of the RTSP protocol across the following interfaces is described in clause 6:
• interface Ct2;
• interface Xc.
Usage of the IGMP/MLD protocol across the following interfaces is described in clause 7:
• interface Dj, Di.
Usage of the SIP protocol for interactions between NGN Applications and UE is described in the clause 8.
Usage of the DVBSTP across the following interfaces is described in clause 9:
• interface Tr.
Usage of the RTP/RTCP protocol across the following interface is described in clause 10:
• interface Xd.
ETSI
13 ETSI TS 183 064 V2.1.1 (2008-10)
Usage of the MPEG2 TS across the following interfaces is described in clause 10:
• interface Xd;
• interface Tr.
NOTE 2: Applications can be transferred as private data streams inside MPEG2 TS. Applicability of MPEG2 TS to
Tr interface is outside the current release.
Usage of the AL-FEC protocol across the following interface is described in clause 10:
• interface Xd.
Use of Diameter shall comply to the following specifications:
• [22] and [3] for interface;
• [3] for e2 interface;
• [1] for Sh interfaces.
4.3 Functional Entities
The functional entities that constitute the NGN dedicated IPTV subsystem are defined in TS 182 028 [4]. The following
clauses summarize the functionality of each functional entity.
4.3.1 User Equipment(UE)
The UE is a functional entity that provides the user with access to IPTV services.
4.3.2 Service Discovery and Selection (SD&S)
The Service Discovery and Selection (SD&S) is a functional entity that provides description information for discovery
of the service as well as information required for description and selection of IPTV services.
4.3.3 Customer Facing IPTV Applications (CF-IPTV-Apps)
The Customer Facing IPTV Application (CFIA) is a functional entity that provides IPTV service provisioning, selection
and authorization.
4.3.4 IPTV Control (IPTV-C)
The IPTV Control (IPTV-C) is a functional entity that checks if UE has been authorized by the Customer Facing IPTV
Application to use IPTV Service Control and Delivery Functions (provides selection of the Media Control Function).
4.3.5 Media Control Function (MCF)
The Media Control Function (MCF) is a functional entity that provides the UE with functions required to control media
flows and manages the MDFs under its control.
4.3.6 Media Delivery Function (MDF)
The Media Delivery Function (MDF) is a functional entity that delivers content data to the UE.
4.3.7 IPTV User Data Function (IPTV UDF)
IPTV user data (IUDF) functional entity is responsible for handling dedicated IPTV user data.
ETSI
14 ETSI TS 183 064 V2.1.1 (2008-10)
4.3.8 NGN User Data Access Function (NGN UDAF)
NGN Application User Data FE (NGN UDF) is a functional entity responsible for handling NGN application and user
data.
5 Procedures using HTTP for dedicated IPTV
5.1 User Equipment (UE)
5.1.1 Procedures for SD&S
Mechanisms used to identify service providers and services in the context of service discovery shall apply conforming
to TS 102 034 [5], clause 5.2.
5.1.1.1 Push mode
Push model delivery of BCGs using multicast shall use the DVBSTP protocol for this purpose in alignment with
clause .4.1.2 of TS 102 034 [5].
5.1.1.2 Pull Mode
In the pull model of unicast delivery of a DVB SD&S data, the HTTP protocol shall be used conforming to
TS 102 034 [5], clause 5.4.2.
In the pull model of unicast container-based delivery of DVB BCG data, the HTTP protocol shall be used conforming
to TS 102 539 [8], clause 4.1.2.2.2.
In the pull model of unicast query mechanism of DVB BCG data, the HTTP protocol is used to transport SOAP
messages. This shall be conforming to TS 102 539 [8], clause 4.2.
NOTE: Some services such as network PVR, notification may fall outside current [5] SD&S scope. In this case
and for additional services the following mechanism may be used:
The http request may contain other header fields conforming to the [9] and XML records specifying
additional service name in the XML format;
The response to the HTTP requests above shall contain matching XML service definition records
or http URL of other SD&S server where this information can be discovered via alternative means.
The additional XML definitions may be discarded by the UE.
5.1.2 Procedure for Service Configuration
One of the following options should be supported.
• An Application Server may implement the role of an XCAP server as described in [15] with standard
authentication mechanisms as discussed below.
• Standalone XDMS server may be used, in which case Tr interface is re-used between UE and the server.
XCAP usage shall comply with [15].
• Service can be configured over standard http [9]. In this case UE normally implements WEB browser with
JavaScript (v tbd) or higher support for running WEB applications.
ETSI
15 ETSI TS 183 064 V2.1.1 (2008-10)
5.1.3 Procedure for Authentication
HTTP Digest [7] is recommended on the Tr interface.
MD5 is recommended digest algorithm as defined in [19], MD5 Message Digest Algorithm.
5.1.4 Procedure for Customer Facing IPTV Applications
Application interface is based on http protocol between UE (converged) and ASF (Customer Facing IPTV applications).
UE should implement an http [9] compliant web browser with JavaScript support. Special requirement for CSS is to
support to enable rendering capabilities.
A particular implementation of the Web Browser is outside the scope of the present document, however, most of widely
used browsers can be supported.
Application Gateway may be used on the Tr interface; however, the gateway specification is outside the scope of the
prestent document.
5.1.5 Procedure for Notifications
The UE may receive notifications from the CFIA using Tr interface between the UE (converged) and IPTV ASF
(Customer Facing IPTV applications) via HTTP protocol [9].
5.1.6 Procedure for Messaging
The UE may initiate and present received messages via CFIA using Tr interface between UE (converged) and ASF
(Customer Facing IPTV applications) via HTTP protocol [9].
The UE may initiate and present received messages through interactions with the Common NGN ASF as described in
TS 182 028 [4], clause A.
5.1.7 Procedure for presence information
The UE may receive presence information via CFIA on Tr interface via HTTP protocol [9].
The CFIA may use the Presence User Agent (PUA) as described in [12] and [13].
Alternatively, presence Network Agent as described in [13] may be used for IPTV in the Common NGN ASF as a
gateway to the NGN Presence Server (PS). The Presence Server or agent can be located in the network.
The PUA can request resource lists from a Resource List Server (RLS) as described in [14] to retrieve presence
information from multiple users.
The PUA (or presence network agent if used alternatively) should provide the mapping of IPTV user account to IMS
user identities.
UE may inform CFIA about presence status information.
Alternatively presence information may be collected by the PUA or network agent (in Common NGN ASF) and
reported to the NGN presence server.
6 Procedures using RTSP for dedicated IPTV
The Real Time Streaming Protocol [6], or RTSP, is an application-level protocol for control over the delivery of data
with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of
real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips.
This clause defines usage of RTSP in dedicated NGN IPTV for interactive control between UE and IPTV service
control functions: IPTV-C and MCF.
ETSI
16 ETSI TS 183 064 V2.1.1 (2008-10)
RTSP application for interactive service control over IP multimedia delivery is defined in DVB-IPI [5] and unless stated
explicitly otherwise, the application defined in DVB-IPI [5] is used.
Service selection
The service discovery and selection process as defined in clause 5 provides UE with the RTSP URL for initializing
interactive multimedia delivery session. The URL discovery methods are discussed in clause 6.1.1 of [5].
The format of RTSP URL shall comply with [7].
Session transport
A transient TCP connection is a temporary connection that exists only long enough to transmit one or more requests.
The UE should use transient connection for exchanging control messages on Ct2 interface for selecting most suitable
MCF function. After MCF is selected there is no need to keep the connection.
A persistent TCP connection is a lasting connection between a client and RTSP server, all requests and replies are sent
over the same connection, and the connection remains intact until the session is completed. The UE should use
persistent connection for RTSP control over interactive media delivery on Xc interface. The usage of persistent
connection is discussed in clause 6.1.2 of [5].
Optionally, transient connection can be used on Xc interface.
A method to keep a persistent connection active is discussed in clause 6.1.
Security considerations
Security considerations discussed in clause 6.1.4 of [5] apply.
Optionally HTTP Digest Access Authentication can be applied to RTSP control messages as defined in [7].
Mapping between DVB and TISPAN profiles
The services defined in the service level requirements and dedicated IPTV architecture is identical when mapped to
DVB service profiles as defined in table 2.
Table 2: Mapping between TISPAN IPTV services and DVB service profiles
TISPAN Service DVB Service profile
BTV LMB
BTV with trick modes MBwTM
CoD CoD
Time-shift TV CoD
Network PVR CoD
RTSP Methods
RTSP methods supported for each profiles and their definitions are identical to clause 6.3 [5].
The requirement to support XML structures in clause 6.3 of [5] is optional. SDP parameters can be used instead.
RTSP Headers
The pause trick mode operation may be signalled by the standard RTSP PAUSE message as defined in [6].
RTSP scale header with 0 value is optional.
ETSI
17 ETSI TS 183 064 V2.1.1 (2008-10)
6.1 User Equipment (UE) and Control Functions
6.1.1 Procedure for BTV service
Usage of RTSP protocol for normal broadcast services without trick modes is not defined in the present document.
6.1.2 Procedure for CoD service
NGN dedicated IPTV uses RTSP protocol [6] for control over the delivery of multimedia with real-time properties.
Usage should be compliant with TS 102 034 [5] unless specified otherwise.
Table 3 illustrates RTSP methods in [6], [5] and NGN dedicated IPTV.
Table 3: RTSP methods in [6], [5] and NGN dedicated IPTV
RTSP Method Direction: RFC 2326 [6] DVB Requirement TISPAN
C = client - TS 102 034 [5] NGN dedicated IPTV
UE;
S = Server -
MCF;
LMB MBwTM Coupled Decoupled
and CoD mode mode
ANNOUNCE C→S MAY MAY MAY MAY MAY
ANNOUNCE MAY SHOULD SHOULD SHOULD SHOULD
S→C
DESCRIBE SHOULD SHOULD SHOULD SHOULD SHOULD
C→S
GET_PARAMETER C→S MAY SHOULD SHOULD SHOULD SHOULD
GET_PARAMETER S→C MAY MAY MAY MAY MAY
OPTIONS SHALL SHALL SHALL SHOULD SHOULD
C→S
OPTIONS MAY MAY MAY MAY MAY
S→C
PAUSE SHOULD N.A. SHALL SHALL SHALL
C→S
PLAY C→S SHALL SHALL SHALL SHALL SHALL
REDIRECT S→C MAY SHALL SHALL N.A. SHALL
SETUP SHALL SHALL SHALL SHALL SHALL
C→S
TEARDOWN SHALL SHALL SHALL SHALL SHALL
C→S
SET_PARAMETER C→S MAY N.A. N.A. N.A. N.A.
SET_PARAMETER S→C MAY N.A. N.A. N.A. N.A.
RECORD MAY N.A. N.A. N.A. N.A.
C→S
NOTE 1: N.A. - Not Applicable. The text in bold shows optional difference in the required support of
RTSP methods in NGN dedicated IPTV and TS 102 034 [5].
NOTE 2: ANNOUNCE, DESCRIBE, OPTIONS are optional methods which are not shown explicitly on
the NGN dedicated IPTV flows, but may be supported by UE and MCF.

Coupled mode: In the coupled mode Customer facing IPTV applications reserves the delivery resources via IPTV
Control on Ss interface and returns the UE RTSP URL with the exact location of the MCF to request interactive media
delivery. The format of RTSP URL shall comply with [6].
ETSI
18 ETSI TS 183 064 V2.1.1 (2008-10)
The UE in the coupled mode shall send RTSP SETUP message containing at minimum RTSP URL, Sequence, and
Transport headers to establish video delivery. Sample message flow in the coupled mode is shown in table 4.
Table 4: Sample RTSP message flow in coupled mode
RTSP Method RTSP Method Reference Notes
from UE to UE point
SETUP Xc UE requested on-demand session from MCF
RTSP 200 OK Xc
PLAY Xc UE requested the play-out to start
RTSP 200 OK Xc
GET_PARAMETER Xc UE sends heartbeat to keep the session active
RTSP 200 OK Xc
PAUSE Xc UE initiated trick mode
RTSP 200 OK Xc
A
...