- 2 -
FG IPTV–C–1078
INTERNATIONAL TELECOMMUNICATION UNION / Focus Group On IPTVTELECOMMUNICATION
STANDARDIZATION SECTOR
STUDY PERIOD 2005-2008 / FG IPTV-C-1078
English only
WG(s): 1 / 7th FG IPTV meeting:
Qawra, St Paul’s Bay, Malta, 11-18 December 2007
CONTRIBUTION
Source: / France Telecom
Title: / IPTV Architecture - Section 8 - Editorial modifications
Abstract: This contribution proposes editorial modifications in section 8 "IPTV Architectural Overview" of IPTV Architecture.
1 - Discussion
The contribution proposes editorial modifications in section 8 "IPTV Architectural Overview". These modifications are proposed to harmonize the terminology inside the section and to clarify the text.
These modifications do not change the structure and the technical content of section 8. A companion contribution addresses further potential restructuring of sections 8 and 9.
The modifications are shown using revision marks. Comments inside the text detail some issues that need specific discussion.
8 IPTV Architectural Overview
The Functional Architectural Overview for IPTV showsidentifies the principal functional groupsmain functional components for IPTV. These functional groups components provide a more detailed breakdown of the IPTV functional domains that are defined in Clause 6. The functional domains of Content Provider and End-User remain the same. The functional domains of Service Provider and Network pProvider are not used in the architecture as the commercial and operational boundaries that this implies are not appropriate to an architectural decomposition. The functional groups components in the architecture are derived by grouping related functions. H, how these functional groups components are allocated across operational and organisational boundaries will vary between implementationsis out of scope of this document.
Figure 8-1: IPTV Functional Architecture Framework
[Editor’s note: Y2012 places the management functions on left hand side of the diagram.]
8.1 IPTV functional architecture components
8.1.1 End-User Functions
The End-User Functions (EUF) performs mediation between the end-user and the IPTV infrastructure.
8.1.2 Application Functions
The Aapplication Ffunctions (AF) enable the End-User FunctionsEUF to select, and purchase if necessary, a content item.
8.1.3 Content Delivery Functions
The Ccontent Ddelivery Ffunctions (CDF) facilitate delivery of content from the Aapplication Ffunctions to the end-user IPTV terminal functions using the capabilities of the nNetwork transport and control Ffunctions.
The content is sent from the application functionsAF to the content delivery functionsCDF before or during the service offering process.
Content delivery functionsCDF also provide the capability to facilitate interaction between the end-user FunctionsEUF and selected content, such as playback control (trick mode play functionality with VoD and Network PVR).
8.1.4 Service Control Functions
The sService cControl fFunctions (SCF) provide the functions to request and release the network and service resources required to support the IPTV services.
For example, the SCFit could may request the content delivery functionsCDF to allocate Content Delivery & Storage functions capacity. The SCF may also and request the nNetwork transport and control fFunctions to reserve and allocate Nnetwork bandwidth for the media sStream and get end user’s current location.
Comment N° 1: Content Delivery & Storage functions are not defined at this level .
The sService cControl fFunctions (SCF)
may provide registration, authentication and authorization functions for the End-User FunctionsEUF.
· The service control functions (SCF) process the media content location request from IPTV Applications and deliver it to the Content Delivery FunctionsCDF to identify the most appropriate“best” Content Delivery Storage Function , which is used tofor delivering content to the Media Client.
· The service control functions (SCF) could may request the content delivery functionsCDF or IPTV applications AF to get provide charging information (e.g. charging start time ticket for streaming service etc.) to provide the charging functions.
· The service control functions (SCF) may also provide service discovery functions.
8.1.5 Management Functions
The Management fFunctions (MF) performs overall system management, status monitoring and configuration. This set of functions may be deployed in a centralized or distributed manner.
Comment N° 2: This section concerns Functional architecture, so the deployment aspects should be avoided.
8.1.6 Content Provider Functions
The cContent pProvider fFunctions (CPF) are provided supported by the entity that owns or is licensed to sell content or content assets (i.e. owner of the content, metadata and usage rights).
8.1.7 Network Transport and Control Functions
Comment N° 3: The text should be aligned with the figure: "Network Transport and Control Functions " should be replaced by " Network Functions".
The nNetwork transport and control fFunctions (NTF) isare comprised the combination of network transport functions and network control functions.
The network control functionsNTF control allowthe network transport layer to provideproviding the required Quality of Service (QoS) for the successful operation of IPTV.
The network transport and control functionsNTF provide IP layer connectivity between the IPTV service components and the end-user functionsEUF. These components are normally shared across all services delivered by IP to an end-user.
Comment N° 4: What is referred by "these components": NTF or "service component"?
[Editor’s Note: The description of the functional may need to be aligned with the diagrams and the equivalent sections in clause 9.]
8.2 IPTV Aarchitectureal Aapproaches
Three general approaches have been identified for describing IPTV Functional Architectures, to enable service providers to deliver IPTV services depending on the type of network architecture and evolutionary choices they select. This document identifies three IPTV architecture approaches that enable service providers to deliver IPTV services:
§ (1)“Non-NGN IPTV functional Architecture” (Non-NGN IPTV)
The Non-NGN IPTV architecture is based on existing IPTV network components and protocols/interfaces. The technology components, protocols and interfaces used in this IPTV architecture are already in widespread use and hence this model approach is a representation of typical existing IPTV networks and services. It is intended to use these This architecture may be used as the a basis for evolution towards the other IPTV architectures listed below.
§ (2) “NGN-based non-IMS IPTV Functional Architecture” (NGN-non-IMS IPTV)
The NGN non-IMS IPTV functional architecture utilizes the components of the NGN framework reference architecture as identified in Recommendation Y.2012 to support the provision of IPTV services, in conjunction with other NGN services if required.
§ (3) “NGN IMS-based IPTV Functional Architecture” (NGN-IMS-IPTV)
The NGN-IMS based IPTV functional architecture utilizes NGN components including the IMS component to support the provision of IPTV services, in conjunction with other IMS services if required.
Although the above three architectural approaches in describing IPTV have been selected iIt is recognized that there are several common functional entitiescomponents and similarities between these alternative approaches. This aspect simplifies inter-working between these approaches, as well as allowing an evolution path to be described to maximise similarities. The use of common elements is a key feature of the representations used in this document to describe these three approaches. common functional components will facilitate the interworking between architectures based on different approaches.
Comment N° 5: New paragraph is proposed.
In the following clauses, this document identifies the architectural functional components which are common to the three architectural approaches identified above. This document also describes the main specificities of each architectural approach. This allows to apprehend the issue of interworking between these architectural approaches but also to identify potential evolutionary paths between these architectural approaches.
______