Jeong Yun, Kim

1
CJK NGN WG (Clarification for IPTV Functions)

• Jeong Yun, Kim
• jykim_at_etri.re.kr

2
Contents

• NGN Functional Architecture
• IPTV Functional Architecture
• Clarifications of difference bet. them

3
1. NGN Functional Architecture

• NGN Architecture Overview
• NGN functions are divided into service stratum
  functions and transport stratum functions
  according to Y.2011

4
1. NGN Functional Architecture

• Service Control Functions
• include resource control, registration, and
  authentication and authorization functions at the
  service level for both mediated and non-mediated
  services
• include functions for controlling media
  resources, i.e., specialized resources and
  gateways at the service-signaling level
• accommodate service user profiles which represent
  the combination of user information and other
  control data into a single user profile function
  in the service stratum
• Application Support Functions and Service Support
  Functions
• include functions such as the gateway,
  registration, authentication and authorization
  functions at the application level
• work in conjunction with the service control
  functions to provide end-users and applications
  with the NGN services they request

5
1. NGN Functional Architecture
6
1. NGN Functional Architecture
7
1. NGN Functional Architecture
8
1. NGN Functional Architecture

• Application Support Functional Entity (AS-FE)
• supports generic application server functions
  including hosting and executing services
• The examples of AS-FE are call feature
  application servers, presence servers, various
  messaging servers, conferences servers, home
  application servers, and so on
• Application Gateway Functional Entity (APL-GW-FE)
  
• serves as an interworking entity between the
  Application and the S-CSC-FE of the Service
  stratum
• APL-GW-FE provides a secure open interface for
  the Applications to use the capabilities and
  resources of the NGN
• The Applications connected to APL-GW-FE are
  usually realized by OSA Application Servers

9
1. NGN Functional Architecture

• Application Service Coordination Manager
  Functional Entity (APL-SCM-FE)
• Manages interactions between multiple application
  services (or servers)
• The functional entities of ASFSSF might
  interwork with each other via APL-SCM-FE to
  provide convergent services to the end users
• Service Switching Functional Entity (SS-FE)
• Provides access and interworking to a legacy IN
  SCP
• For the IN services, the S-CSC-FE is connected
  through SS-FE to SG-FE to interact with a legacy
  IN SCP
• It provides IN service switching functions
  including service trigger detection, service
  filtering, call state management, etc and the
  protocol adaptation function between INAP and SIP

10
2. IPTV Functional Architecture

• High-Level Functions

11
2. IPTV Functional Architecture

• High-Level Functions
• Application Components The functional components
  of the IPTV Application. The main role of this
  layer is to enable the use of the IPTV terminal
  to select, and purchase if necessary, and item of
  content. It will also contain support for content
  protection
• Service Components The functional components
  that support the origination of the media content
  stream the functional components for the
  management of the network to ensure the
  successful delivery of the media content from it
  source to the IPTV Terminal

12
2. IPTV Functional Architecture

• NGN based Architecture - IMS session control

13
2. IPTV Functional Architecture

• NGN based Architecture including Content Provider
  and OSS/BSS

14
2. IPTV Functional Architecture

• IPTV Functions
• Application component layer - this contains the
  functional components of the IPTV Application.
  The main role of this layer is to enable the use
  of the IPTV terminal to select, and purchase if
  necessary, and item of content. It will also
  contain support for content protection
• Service Support Functions - this contains the
  functional components that support the delivery
  of the media content from it source to the IPTV.
• Service Control Functions - this contains the
  functional components for the management of the
  network to ensure the delivery of the media
  content from it source to the IPTV Terminal

15
2. IPTV Functional Architecture

• Application Component Functions
• IPTV Application - Provides the server side
  functions of the IPTV Application. In general,
  this supports selection of IPTV service and the
  browsing and selection of content with the
  service
• IPTV subscriber Management Provides the
  functions for the application level management of
  the customers details
• Service Support Functions
• Distribution Delivery Broadcast VoD
  Provides the functions for the distribution and
  delivery of content for Broadcast and On-Demand
  services
• Service Control Functions
• Core IMS - Provides the session control to
  deliver SIP-based services to the IPTV Terminal.
• User Profile Functions Provides for the storage
  and management of the user profiles required to
  support the network service functions

16
3. Clarifications of difference bet. them
NGN Functions
IPTV Functions (as is)

• Application
• Application Support Functions and Service Support
  Functions
• AS-FE
• APL-SCM-FE
• APL-GW-FE
• Service Control Functions
• Core IMS
• PES

• Application Component
• IPTV Application
• IPTV Subscriber Management
• DRM/IPG Server
• Service Support Functions
• Distribution Delivery Broadcast VoD
• Service Control Functions
• Core IMS
• User Profile Functions

17
3. Clarifications of difference bet. them
NGN Functions
IPTV Functions (to be)

• Application
• Application Support Functions and Service Support
  Functions
• AS-FE
• APL-SCM-FE
• APL-GW-FE
• Service Control Functions
• Core IMS
• PES

• Application
• IPTV Application
• Application Support Functions and Service Support
  Functions
• IPTV Subscriber Management
• DRM/IPG Server
• Distribution Delivery Broadcast VoD
• Service Control Functions
• Core IMS
• User Profile Functions

IPTV Functions should be aligned with NGN
Functions and then we can build single service
platform to cover multiple services