ETSI TS 182 027 V3.4.1 (2010-06)
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem
RTS/TISPAN-02070-NGN-R3
General Information
Standards Content (Sample)
ETSI TS 182 027 V3.4.1 (2010-06)
Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
IPTV Architecture;
IPTV functions supported by the IMS subsystem
---------------------- Page: 1 ----------------------
2 ETSI TS 182 027 V3.4.1 (2010-06)
Reference
RTS/TISPAN-02070-NGN-R3
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 2010.
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.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI TS 182 027 V3.4.1 (2010-06)
Contents
Intellectual Property Rights . 10
Foreword . 10
1 Scope . 11
2 References . 11
2.1 Normative references . 11
2.2 Informative references . 12
3 Definitions and abbreviations . 13
3.1 Definitions . 13
3.2 Abbreviations . 15
4 High-level overview . 16
5 Overview of functional entities . 17
5.1 Functional architecture for IPTV services . 17
5.1.1 Functional architecture overview . 17
5.1.2 IPTV services . 18
5.1.2.0 Compliance . 18
5.1.2.1 General . 19
5.1.3 Functional entities . 20
5.1.3A Generic Capabilities . 20
5.1.4 Elementary functions . 20
5.1.4.1 Content security functions . 22
5.1.5 Functional Entities . 22
5.1.5.1 Service Discovery and Selection Functions (SDF and SSF) . 22
5.1.5.2 IPTV Service Control Functions (SCF) . 23
5.1.5.3 IPTV Media Control and Delivery Functions (MCF and MDF) . 24
5.1.5.4 UPSF . 25
5.1.5.5 Transport processing functions . 25
5.2 Interactions between Service Control function and Media Functions . 26
5.3 Void . 27
5.4 Inter-destination media synchronization . 27
5.4.1 Functional entities MSAS and SC . 28
5.4.2 Mapping onto the IPTV architecture . 28
5.4.3 Modification and re-origination of media streams . 29
5.5 IPTV Service State . 30
5.5.1 General . 30
5.5.2 Relationship between IPTV Service State and IPTV presence . 30
6 Reference points . 30
6.1 UE - SSF (Xa) . 30
6.2 UE - IPTV Service Control Functions (Ut) . 30
6.3 UE - Core IMS (Gm) . 30
6.4 UE - Media Control Functions (Xc) . 30
6.5 UE - Media Delivery Functions (Xd) . 31
6.6 IPTV Service Control Functions (SCF) - UPSF (Sh) . 31
6.7 Core IMS - UPSF (Cx) . 31
6.8 Core IMS - IPTV Service Control Functions (ISC) . 31
6.9 Core IMS - IPTV Media Functions (y2) . 31
6.10 Core IMS - SDF (ISC) . 32
6.11 SDF - UPSF (Sh) . 32
6.12 Void . 32
6.13 Application Functions - NASS (e2). 32
6.14 Core IMS - RACS (Gq') . 32
6.15 NASS - RACS (e4). 32
6.16 IPTV Service Control Functions - SLF (Dh) . 32
6.17 Core IMS - SLF (Dx) . 32
ETSI
---------------------- Page: 3 ----------------------
4 ETSI TS 182 027 V3.4.1 (2010-06)
6.18 IPTV Media Control Function - IPTV Media Delivery Function (Xp) . 32
6.19 MSAS-SC reference point (Sync) . 33
6.20 MSAS-SC' reference point (Sync') . 33
6.21 SSF-SCF reference point (Ss') . 33
7 User data . 33
7.1 Classification of information . 33
7.2 Location and access to user data . 34
7.2.1 Data management functions . 34
7.2.2 Access from other application servers . 35
7.2.3 Access from User Equipment (UE) . 35
7.2.4 Access from the SSF . 35
7.3 IPTV user profile structure . 35
7.3.1 IPTV user profile structure . 35
7.3.1.1 BC service package . 37
7.3.1.2 BC service . 37
7.3.1.3 UE . 37
7.3.1.4 Global settings: language preference . 37
7.3.1.5 Global settings: user action recordable . 38
7.3.1.5A Global settings: PC-CostLimit . 38
7.3.1.5B Global settings: PC-TotalCostLimit . 38
7.3.1.5C Global settings: PC-ClassificationRestriction . 38
7.3.1.5D Global settings: PC-TimePeriodRestriction . 38
7.3.1.5E Global settings: PC-TotalPlayTimeLimit . 38
7.3.1.5F Global settings: PC-AdminUser . 38
7.3.1.5G Global settings: dynamic PC-activation . 38
7.3.1.5H Global settings: PC-Contact . 38
7.3.1.6 N-PVR storage-limit . 39
7.3.1.6A PVR: IPTVContentMarkerAuthorizedViewUser . 39
7.3.1.6B PVR: IPTVContentMarkerSourceUser . 39
7.3.1.6C PVR: AuthorizedControlUser . 39
7.3.1.7 BC: ParentalControlLevel . 39
7.3.1.10 PCh: PChId . 39
7.3.1.11 PCh: PChExpiryTime. 40
7.3.1.12 PCh: PChItemServiceType . 40
7.3.1.13 PCh: PChItemContentId . 40
7.3.1.14 PCh: PChItemStartTime . 40
7.3.1.15 PCh: PChItemEndTime . 40
7.3.1.16 PCh: PChItemOffset. 40
7.3.1.17 CR Settings: CR notifications . 40
7.3.1.18 UGC storage-limit . 40
7.3.1.19 UGC: AuthorizedControlUser. 40
7.3.1.20 ICM Settings: ICM rules . 40
7.3.2 Usage of IPTV user profile . 41
7.3.3 Life cycle . 41
7.4 IPTV service action data . 41
7.4.0 General . 41
7.4.1 Data model . 42
7.4.2 Life cycle . 43
7.5 IPTV information storing/sharing services . 44
7.5.1 General . 44
7.5.2 IPTV Content Marker . 44
7.5.2.1 General . 44
7.5.2.2 IPTVContentMarkerID . 44
7.5.2.3 OwnerUserID . 44
7.5.2.4 IPTV service type identifier . 45
7.5.2.5 IPTV Content Identifier . 45
7.5.2.6 StartTimeOfIPTVContentMarker . 45
7.5.2.8 UserComment . 45
7.5.2.9 GenerationTime . 45
7.5.2.10 ExpiryTime . 45
7.5.3 IPTV Service Access History . 45
ETSI
---------------------- Page: 4 ----------------------
5 ETSI TS 182 027 V3.4.1 (2010-06)
7.5.3.1 Data model . 45
7.5.3.2 UserID . 46
7.5.3.3 AccessHistoryID . 46
7.5.3.4 ServiceType . 46
7.5.3.5 ReferencedContentID . 46
7.5.3.6 Rating . 46
7.5.3.7 AccessStartTime . 46
7.5.3.8 AccessEndTime . 47
7.5.3.9 HistoryExpiryTime . 47
7.6 IPTV Content Recommendation profile . 47
7.6.1 Genre . 47
7.6.2 Keyword . 47
7.6.3 Creator . 47
7.6.4 CreationLocation . 47
7.6.5 CreationDate . 48
7.7 IPTV Service State Data . 48
7.7.1 Data model . 48
7.7.2 Life cycle . 49
8 Procedures . 49
8.1 IPTV addressing mechanisms . 49
8.1.1 IPTV end-users identification and addressing mechanisms . 49
8.1.2 Addressing of nodes. 49
8.2 UE start-up procedure . 49
8.3 Broadcast session . 52
8.3.1 Signalling flows for broadcast session initiation . 52
8.3.1.1 Overview of the signalling flows for session initiation . 52
8.3.1.1.1 UE-initiated BC session initiation . 52
8.3.1.1.2 SCF-initiated BC session initiation . 53
8.3.1.2 Signalling flows for the establishment of the delivery channel . 54
8.3.1.2.1 SCF-initiated establishment of the delivery channel . 54
8.3.1.2.2 UE-initiated establishment of the delivery channel . 55
8.3.2 Signalling flows for BC session modification . 56
8.3.2.1 UE-initiated BC session modification . 56
8.3.2.2 SCF-initiated BC session modification . 57
8.3.3 Signalling flows for broadcast session release . 58
8.3.3.1 UE-initiated session release . 58
8.3.3.2 SCF-initiated session release . 59
8.3.4 Signalling flow for Broadcast TV channel switching . 60
8.3.5 Signalling flows for transition from Broadcast TV to Broadcast TV with trick play . 61
8.3.6 Signalling flows for transition from Broadcast TV with trick play to Broadcast TV . 63
8.3.7 Signalling flows for Broadcast TV with trick play session release . 63
8.3.8 Signalling flows for Pay Per View service . 63
8.4 CoD session . 64
8.4.1 Signalling Flows for CoD session initiation . 65
8.4.1.1 Overall signalling flows for CoD session initiation . 65
8.4.1.1.1 UE-initiated CoD session initiation . 65
8.4.1.1.2 SCF-initiated CoD session initiation . 66
8.4.1.2 Media Channel Negotiation . 68
8.4.1.2.1 Signalling flows for the establishment of the content control and content delivery channels
from MF . 68
8.4.1.2.2 Signalling flows for the establishment of the content control and content delivery channels
from UE . 69
8.4.1.2.3 Signalling flows for the establishment of the content control channel from UE . 69
8.4.2 Signalling Flows for CoD session modification . 70
8.4.2.0A UE-initiated CoD session mod ificatio n . 70
8.4.2.0B MF-initiated CoD session modification . 72
8.4.2.1 Signalling flows for the establishment/modification of the content delivery channel from UE. 73
8.4.2.2 Signalling flows for the modification of the content delivery channels from MF . 73
8.4.3 Signalling Flows for CoD session release. 74
8.4.3.1 UE-initiated session release . 74
8.4.3.2 SCF-initiated session release . 75
ETSI
---------------------- Page: 5 ----------------------
6 ETSI TS 182 027 V3.4.1 (2010-06)
8.4.3.3 MF-initiated session release .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.