- 1 -
FG IPTV-C-0443
INTERNATIONAL TELECOMMUNICATION UNION / Focus Group On IPTVTELECOMMUNICATION
STANDARDIZATION SECTOR
STUDY PERIOD 2005-2008 / FG IPTV-C-0443
English only
WG(s): 1 / 4th FG IPTV meeting:
Bled, Slovenia, 7-11 May 2007
CONTRIBUTION
Source: / Nortel Networks (Canada)
Title: / Comments on clause8 of FG IPTV–DOC-0062-Part 8
Abstract
This contribution provides replacement for parts of clause 8 of “FG IPTV-DOC-0062 (22-26 January 2007), Working document:IPTV architecture” in order to enhance its accuracy and quality.
Background and discussion
At the most recent FG IPTV meeting, i.e. 22-26 January 2007, significant progress was made on the IPTV architecture document. However, more work is needed to enhance its accuracy and appearance. This contribution proposes revisions/replacement for parts of clauses 8 in line with the proposed table of content for FG IPTV-DOC-0062 as presented in the accompanying contribution.
Reference
FG IPTV-DOC-0062 (22-26 January 2007), workingdocument:IPTV architecture
Proposal
It is proposed to accept the following.
8.5NGN based Architecture –Coexisting IMS and non-IMS based NGN
Non-IMS to IMS Gateway
A hybrid approach can exist where Core IMS is used to manage and control the network resources and a gateway function is used to translate these protocols for the IPTV client.
NGN based Architecture including Content Provider and OSS/BSS
The figure below extends the above figures toFigure 8-5 includes the functional components that relate to Content and to Operational Support Systems, OSS, and Business Support Systems, BSS. It also shows the details for the coexistence of IMS and non-IMS approaches.
Figure 8-75: NGN based Architecture including Content Provider and OSS/BSS- Coexisting IMS and non-IMS based NGN
Editor’s note2: the 3rd party network should be removed from the above diagram for the time being.
The additional components included in this figure are:
8.5.1Consumer
8.5.1.1IPTV device
Contributor’s note: Functional entities IPG client and DRM client have not been defined for either of NGN cases identified previously
IPG client: This functional component provides for the delivery and presentation of the metadata that describes the IPTV services and their content.
DRM Cclient, DRM Server and DRM & Rights Source –: These functional components provide for the description and protection of a content item’s rights. In general, the Content Provider will be the source of the content for the IPTV service and define the usage rights for a content item. The DRM Server protects the content and provides the DRM client with the key to enable it to access the content.
Application client: See 8.3.1.1
Media client: See 8.3.1.1
IPTV/session client: See 8.4.1.1
8.5.1.2Consumer transport
Delivery network gateway functions: See 8.3.1.2
8.5.2Application components
Contributor’s note: Functional entities IPG server and DRM server have not been defined for either of NGN cases identified previously
IPG server: This functional component provides for the delivery and presentation of the metadata that describes the IPTV services and their content.
DRM server: This functional component provides for the description and protection of a content item’s rights. In general, the Content Provider will be the source of the content for the IPTV service and define the usage rights for a content item. The DRM Server protects the content and provides the DRM client with the key to enable it to access the content.
Content preparation: TBD
IPTV application: See 8.3.2
IMS application: TBD
IPTV subscriber management: see 8.3.2
8.5.3Service components
8.5.3.1Service support functions
Distribution & delivery broadcast & VoD: See 8.3.3.1
8.5.3.2Service control functions
Core IMS: See 8.4.3.2
User profile: See 8.3.3.2
IPTV control: See 8.3.3.2
8.5.4Network components
See 8.3.4
8.5.4.1Network control functions
Network attachment control function (NACF): See 8.3.4.1
Resource and admission control function (RACF): See 8.3.4.1
8.5.4.2Network transport functions
Access network function: See 8.3.4.2
Edge function: See 8.3.4.2
Core transport function: See 8.3.4.2
8.5.5Content provider
IPG Client, IPG Server and IPG Ddata Sourcesource:– These This functional components provides for the delivery and presentation of the metadata that describes the IPTV services and their content.
DRM & rights source: This functional component provides for the description and protection of a content item’s rights. In general, the Content Provider will be the source of the content for the IPTV service and define the usage rights for a content item. The DRM Server protects the content and provides the DRM client with the key to enable it to access the content.
Content source: TBD
Media format: TBD
8.5.6OSS / BSS
OSS/BSS – : These are the Operational and Business Support Systems for the different layers in the architecture. In general, these will be common to all services provided by an entity at that layer in the architecture, e.g. a Network Provider
.
8.5.7Reference points
TBD
[Editor’s note: Align 3rd party with other boxes in NGN architecture.]
[Editor’s note: the relationship between MDDCF from 316, the MRBF from 390 and the Distribution & Delivery Broadcast & VoD is for further study.]
<Source from 316 end>
The MDDCF function entity is marked in purple in the above Figure, which has the following functions:
Manage the content distribution from the content source to the media servers throughout the network based on the business policies of the operator. The MDDCF is aware of the content distribution info among the media servers.
Collect the status information of all the available media servers, e.g. online or offline, media processing capability, available resource capability etc. The MDDCF is aware of all media servers’ status info.
Select the most suitable media server for the user’s IPTV service request based on the information above, and transfer the service request to media server.
The functionality of CMF (Content Management Function) is as follows:
Serve as the contact point with the Content Provider;
Get and manage the content related information, i.e. content metadata, from the Content Provider, including identifier of the content, the time duration, the brief introduction etc.
ditor’s note: This text needs additional clarification, contributions are encouraged.
[Editor’s note: the relationship between the SGF and the IPG is for further study. Terminology needs to be aligned.]
The functionality of SGF (Service Guide Function) is as follows:
Generate the Electronic Program Guide based on the necessary information, e.g. metadata information, some service related information and user profile etc;
Provide the produced EPG to the user through interactions with the user.
______