Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architecture and reference points of a customer network device for IMS based IPTV services

DTS/TISPAN-05018-NGN-R2

General Information

Status
Published
Publication Date
24-Jul-2008
Current Stage
12 - Completion
Due Date
20-Jun-2008
Completion Date
25-Jul-2008
Ref Project

Buy Standard

Standard
ETSI TS 185 009 V2.1.1 (2008-07) - Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architecture and reference points of a customer network device for IMS based IPTV services
English language
24 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 185 009 V2.1.1 (2008-07)
Technical Specification


Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Architecture and reference points of a customer network
device for IMS based IPTV services

---------------------- Page: 1 ----------------------
2 ETSI TS 185 009 V2.1.1 (2008-07)



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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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

---------------------- Page: 2 ----------------------
3 ETSI TS 185 009 V2.1.1 (2008-07)
Contents
Intellectual Property Rights.5
Foreword.5
Introduction .5
1 Scope.6
2 References.6
2.1 Normative references.6
2.2 Informative references.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 High level functional architecture for IPTV-CNDs .8
4.1 Architecture layers.8
4.1.1 Transport layer.9
4.1.2 Service layer.9
4.1.3 Application and User Experience layer .9
4.2 IPTV operating modes.9
5 IPTV Customer Network Device Architecture .10
5.1 IMS based IPTV compatible devices .10
5.1.1 Detailed Architecture.11
5.1.1.1 Transport Layer Functions .11
5.1.1.1.1 Network attachment functions.11
5.1.1.1.2 Transfer functions.11
5.1.1.1.3 Transport functions.12
5.1.1.2 Service layer functions.12
5.1.1.2.1 IPTV-CND-SIP UA : IPTV Customer Network Device SIP UA.12
5.1.1.2.2 IPTV-CND-SPM: IPTV Service Profile Management function.12
5.1.1.2.3 IPTV-CND-MDP: IPTV Customer Network Device MetaData Processing .12
5.1.1.2.4 IPTV-CND-MPC: IPTV Customer Network Device Media Player Control.12
5.1.1.2.5 IPTV-CND-MD IPTV Customer Network Media Delivery.12
5.1.1.2.6 IPTV-CND-CMM Configuration Management and Monitoring.12
5.1.1.2.7 IPTV-CND-PPF: IPTV Customer Network Device - Plug and Play Function .13
5.1.1.2.8 IPTV-CND-cPVR: IPTV client PVR Function .14
5.1.1.3 Applications and user experience layer functions .14
5.1.1.3.1 IPTV Applications.14
5.1.1.3.2 IPTV-CND-SPA: Service Profile Application .14
5.1.1.3.3 IPTV-CND-MDA: Metadata Application.14
5.1.1.3.4 IPTV-CND-BF: Browser Function.14
6 Reference points.15
6.1 Reference points for IMS based IPTV compatible devices.15
6.1.1 Transport layer Reference points .15
6.1.1.1 Transport Reference points .15
6.1.1.2 Network attachment Reference points .15
6.1.2 Service layer Reference points.15
7 The IPTV - CND Data Model .16
8 Deployment's scenarios.16
8.1 Option 1.16
8.2 Option 2.16
9 Information Flows.17
9.1 Information flows between IPTV-CND and NGN.17
9.1.1 Example message flows on Xa .17
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 185 009 V2.1.1 (2008-07)
9.1.2 Example message flows on Ut.17
9.1.3 Example message flows on Gm.18
9.1.3.1 Registration.18
9.1.3.2 Session Initiation and Termination .18
9.1.3.3 IPTV Service Action Data Delivery.18
9.1.4 Example message flows on Xc and Xd.19
9.1.4.1 Message flows for CoD service .19
9.1.4.2 Message flows for BC service.19
9.1.5 Example message flows on e .20
3
9.1.6 Example message flows on e .20
1
9.2 Information flows between IPTV-CND and CNG .21
9.2.1 Example message flows on C .21
9.2.1.1 Message flows for device and service information exchange .21
9.2.1.2 Message flows for device control.22
9.2.2 Example message flows on G ' .23
m
9.2.2.1 Registration.23
9.2.2.2 IPTV Service Action Data Delivery.23
9.2.3 Example message flows on e ' .23
1
9.2.4 Example message flows on e ' .23
3
9.2.5 Example message flows on a .23
u
History .24

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 185 009 V2.1.1 (2008-07)
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).
Introduction
The present document describes the main type of IMS based IPTV Customer Devices that take part in Customer
Premises Network in terms of general architecture and in terms of reference points with the NGN and CNG.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 185 009 V2.1.1 (2008-07)
1 Scope
The present document defines the stage 2 Customer Network Devices for IPTV services (IPTV-CND) specifications; It
is therefore addressing the overall architecture of the customer network device (CND) enabling the IPTV service
consumption. The architectural definition is covering both transport and service layer related functionalities. The
reference points between the CND and the Customer Network Gateway (CNG) are also part of the specifications.
The 2 solutions elaborated specified in TS 182 027 [2] and TS 182 028 [4] are IMS based IPTV and IPTV Dedicated
Subsystem solutions but only the IMS based IPTV solution is considered in the present document.
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.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and
IPTV".
[2] ETSI TS 182 027: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS
subsystem".
[3] ETSI TS 183 063: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification;".
[4] ETSI TS 182 028: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IPTV Architecture; Dedicated subsystem for IPTV functions".
[5] ETSI TS 183 064: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Dedicated IPTV subsystem stage 3 specification;".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 185 009 V2.1.1 (2008-07)
[6] ETSI TS 185 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Customer Network Gateway Architecture and Reference
Points;".
[7] ETSI TS 185 006: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Customer Devices architecture and interfaces and Reference
Points".
[8] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture".
[9] ETSI TS 181 005: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Service and Capability Requirements".
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 TR 185 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); High level customer network architectures".
[i.2] ETSI TS 185 005: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Services requirements and capabilities for customer networks
connected to TISPAN NGN".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Customer Network Device (CND): physical device enabling service(s) usage
NOTE: CNDs can be dedicated to the internet, conversational and audio-video services, but they could be also
Consumer Electronics equipment and other devices which may have nothing to do with these premium
services (e.g. services performing a content sharing within a CPN, typically between a PC and a music
system, through the CNG).
Customer Network Gateway (CNG): gateway between the Customer Premises Network (CPN) and the Access
Network able to perform networking functions from physical connection to bridging and routing capabilities, but also
possibly implementing functions related to the service support
Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network
devices, network segments (physical wired or wireless connections between customer network elements), network
adapters (performing a L1/L2 conversion between different network segments) and nodes (network adapters with L3
routing capabilities)
IPTV services Customer Network Device (IPTV-CND): physical device enabling consumption of IPTV service(s)
NOTE: IPTV-CNDs are dedicated to the TV like audio-visual services such as live TV or On demand.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CND Customer Network Device
CNG Customer Network Gateway
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 185 009 V2.1.1 (2008-07)
CNGCF Customer Network Gateway Configuration Function
COD Content On Demand
CPN Customer Premises Network
DHCP Dynamic Host Configuration Protocol
IMS IP Multimedia Subsystem
IPTV Internal Protocol TeleVision
NACF Network Access Configuration Function
NAPT Network Address and Port Translation
NAT Network Address Translation
NPVR Network Personal Video recorder
NTF NAPT Traversal Function
P-CSCF Proxy Call Session Control Function
QoE Quality of Experience
QoS Quality of Service
SIP Session Initiation Protocol
SSF Service Selection Function
STB Set Top Box
UA User Agent
UE User Equipment
4 High level functional architecture for IPTV-CNDs
The high level functional architecture of IPTV-CND is composed of 3 layers as represented in figure 4.1.
4.1 Architecture layers
CND
Application & User Experience Layer
Service Layer
Transport Layer

Figure 4.1: Architecture layers
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 185 009 V2.1.1 (2008-07)
4.1.1 Transport layer
This layer comprises functional entities that provide relevant IPTV transport level functions such as network attachment
and media processing and streaming functions.
4.1.2 Service layer
This layer comprises functional entities that provide relevant IPTV functionality to applications above and also include
entities that are used for management and control of platform itself. Depending on the type of services, the service layer
entity must communicate either with other devices in the customer network or the external network using the transport
layer. Service layer entities do not have a direct user interface and may be controlled via appropriate applications layer
entities.
Examples include:
• Media Management function.
• Service Discovery function.
• Platform security function.
• CA/DRM function.
• Configuration and Management function, etc.
4.1.3 Application and User Experience layer
This layer comprises IPTV applications that have user interface (user driven input and /or output) and use the services
provided by the underlying Service Layer to drive end user experience.
Examples of applications include:
• VOD.
• Broadcast TV.
• IPTV Service Guide interface, etc.
The user may be a customer or a service operator.
For the service operator, these functions may include service specific functions such as measurement applications
(e.g. user satisfaction).
4.2 IPTV operating modes
IPTV CNDs can be simple terminals connected to the NGN or be part of a CPN in connection with the CNG. Different
configuration are discussed in TR 185 004 [i.1]. Consequently, the IPTV CND can work in different modes in relation
with the CNG.
• Bridged mode: In this mode, the IPTV CND is working in compliance with TS 183 063 [3] and is connected
to the NGN network or connects to the NGN via a CNG operating in bridged mode. In bridged mode of
operation, the CNG provides only L1-L2 functionality.
• Routed mode: In this mode, the IPTV CND connects to the NGN via a CNG operating in routed mode and is
capable to interact with other devices in the CPN with other protocols above L3. In routed mode of operation,
the CNG includes routing and service layer functionality as well (L3 and above).
- NGN mode: IPTV CND connects directly to the NGN through the CNG.
- CPN mode: the IPTV CND is interacting only in the domain of the CPN and all interactions with the
access network are under control of the CNG. The CNG works in compliance with TS 183 063 [3] and is
acting as an adaptor for all above L3 protocols to the CPN.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 185 009 V2.1.1 (2008-07)
• Intra CPN mode: At service layer, the 2 devices interact with or without the support of the CNG.
NOTE: Specifications for the intra CPN mode are not part of the present document but in this case, for example,
IPTV CND could follow DLNA (Digital Living Network Alliance) interoperability guidelines.
5 IPTV Customer Network Device Architecture
The present document categorizes IPTV-CNDs into two types depending on TISPAN IPTV solutions that have been
developed by WG2. They are:
• Devices compatible with the IPTV dedicated subsystem solution.
• Devices compatible with the IMS based IPTV solution.
Devices compatible with IPTV dedicated subsystem solution:
This category of IPTV CNDs includes IPTV capable device which can be utilized in conjunction with IPTV services
delivered in compliance with TISPAN specifications TS 182 028 [4] TS 183 064 [5].
Devices compatible with the IMS based IPTV solution:
This category of IPTV CNDs includes IPTV capable device which can be utilized in conjunction with IPTV services
delivered in compliance with TISPAN specifications TS 182 027 [2] for "IPTV functions supported by the IMS
subsystem" for the architecture aspects and TS 183 063 [3] for protocols aspects.
Only IMS based IPTV compatible devices are considered for detailed description in the present document.
5.1 IMS based IPTV compatible devices
IMS based IPTV compatible means compliance with TS 182 027 [2].
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 185 009 V2.1.1 (2008-07)
5.1.1 Detailed Architecture
CND
Application & User Experience Layer
IPTV
browser
IPTV Applications
Service Metadata
Applications
(n & cPVR, COD,
Profile App App
BC)
Browser
Service Layer
Configuration
Service
cPVR Management
Profile
& Monitoring
Management
Media Player
Plug and play
SIP User MetaData
Control and
functions
Agent Processing
Media Delivery
Transport Layer
Transport
Network
QoS ctrl
Attachment
Control
Ut
Transport
Xa
Media /Packet
Processing G G ’
Processing Function m, m
QoS
x x
c, d
proces
e e ’
3, 3 ,
e e ’
1, 1 ,
C

Figure 5.1: Detailed IPTV CND architecture
NOTE: Entities in a given layer are interfacing/interacting with one or more functional entities in layers below it
in order to accomplish the given function. Figure 5.1 does not depict all these internal
interfaces / interactions which are implementation specific.
5.1.1.1 Transport Layer Functions
5.1.1.1.1 Network attachment functions
IPTV CND attachment functions are compliant with the specifications for CNDs TS 185 006 [7]. They include:
• IPTV-CND-CMF: Customer Network Device - Configuration and Maintenance Function.
• IPTV-CND-AtF: Customer Network Attachment Function.
• IPTV-CND-LAF: Customer Network Device - Local Authentication Function.
5.1.1.1.2 Transfer functions
IPTV CND transfer functions are compliant with the specifications for CNDs TS 185 006 [7].
• IPTV-CND-NTF : NAPT Traversal Function.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 185 009 V2.1.1 (2008-07)
5.1.1.1.3 Transport functions
5.1.1.1.3.1 IPTV-CND-MPPF: IPTV Customer Network Device-Media Packet Processing Function
The MPPF is the termination point for media flows encrypted or not encrypted, over the Dj interface connecting the UE
to the NGN C-BGF as defined in ES 282 001 [8].
NOTE 1: The handling of encrypted media flows is out of scope of this release.
NOTE 2: This function is providing support for NAT traversal such as the media port punching mechanisms and
also for the usage of IGMPv3.
5.1.1.1.3.2 IPTV-CND-QOS: IPTV Customer Network Device-QoS Function
The IPTV CND should support the following set of QoS functions for egress traffic:
1) Traffic classification based on rules defined by the NGN service provider, access network provider or
connectivity provider (business role definitions are defined in TS 181 005 [9]).
2) Packet marking based on the different service classes.
5.1.1.2 Service layer functions
NOTE: The security aspects are not specified in this release. The term security is to be taken here in a general
sense covering several aspects including content protection, conditional access, privacy and parental
control.
5.1.1.2.1 IPTV-CND-SIP UA : IPTV Customer Network Device SIP UA
This block implements the Gm, Gm' interfaces on IPTV CND compatible with the IMS based IPTV solution. This SIP
UA shall perform the service authentication and manage signalling flows securely following in that what is already
described in clause 6 on Authentication in TS 185 006 [7].
5.1.1.2.2 IPTV-CND-SPM: IPTV Service Profile Management function
This block implements the Ut interface; the Ut enables the access to an Application Sever to support the user in
configuration services update.
5.1.1.2.3 IPTV-CND-MDP: IPTV Customer Network Device MetaData Processing
This functional entity utilizes Xa, Gm and/or Xd to receive service related metadata (e.g. IPTV services plans, EPG,
VOD catalogue, customer applications).
5.1.1.2.4 IPTV-CND-MPC: IPTV Customer Network Device Media Player Control
This functional entity utilizes Xc for control of media delivery (e.g. RTSP set up, Play, stop, etc.).
5.1.1.2.5 IPTV-CND-MD IPTV Customer Network Media Delivery
This functional entity implements the Xd interface for the media streaming (e.g. RTP streams).
5.1.1.2.6 IPTV-CND-CMM Configuration Management and Monitoring
This function provides support for the IPTV-CND-CMF for service layer configuration, middleware management,
performance monitoring (providing fee
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.