Download international telecommunication union

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Document related concepts

History of business architecture wikipedia, lookup

Transcript
INTERNATIONAL TELECOMMUNICATION UNION
FOCUS GROUP ON IPTV
TELECOMMUNICATION
STANDARDIZATION SECTOR
FG IPTV-C-0182
English only
STUDY PERIOD 2005-2008
2nd FG IPTV meeting:
Busan, 16-20 October 2006
WG(s): 1
CONTRIBUTION
Source: Korea (Republic of)
Title:
Proposal to initiate IPTV functional architecture over NGN
Abstract
This contribution describes two reasons that we have to define IPTV architecture on the basis of
functional entity and proposes to initiate IPTV functional architecture over NGN.
Introduction
Most of telecom operators regard IPTV as a means to complete their triple-play service bundles –
the combination of voice, data, and video services. The integration of IPTV service into
conversation service, thus, is one of the critical issues for operator to solve sooner or later.
In addition, NGN functional architecture can comprise various service-specific components such as
IMS, PIES, and multimedia multicast/broadcast services (e.g. IPTV). NGN functional architecture
for IMS and PIES has completed but that for IPTV is under the development. Therefore, it is a very
important task to define IPTV architecture and to keep the alignment between IMS and IPTV in
NGN.
This contribution describes two reasons to define IPTV architecture on the basis of functional entity
and proposes to initiate IPTV functional architecture over NGN.
Contact:
Jeong Yun Kim
ETRI, Rep. of Korea
Jin Ho Hahm
ETRI, Rep. of Korea
Jun Kyun Choi
ICU, Rep. of Korea
Tel:
Fax:
Email
+82 42 860 5311
+82 42 860 5039
[email protected]
Attention: This is a document submitted to the work of ITU-T and is intended for use by the participants to the activities of ITU-T's
Focus Group on IPTV, and their respective staff and collaborators in their ITU-related work. It is made publicly available for
information purposes but shall not be redistributed without the prior written consent of ITU. Copyright on this document is owned by
the author, unless otherwise mentioned. This document is not an ITU-T Recommendation, an ITU publication, or part thereof.
-2FG IPTV-C-0182
Discussion
This section shows two reasons to define IPTV functional architecture on the basis of functional
entity and some considerations.
(1) IPTV is one of the subsytems for NGN
At last July meeting SG13 finally consented Recommendation Y.2012 “Functional Requirements
and Architecture of the NGN”, which describes the functional entities residing in both service
stratum and transport stratum of NGN. Especially, both IMS component and PSTN/ISDN
Emulation service component belong to the service stratum of NGN for Release 1.
SG13 is developing overall NGN framework architecture. When considering beyond NGN Release
1 scope, IPTV functional architecture could be regard as one of the subsystem for NGN. In addition
FG IPTV is a child of SG13. Consequently, defining both the functional entities and related
reference point for IPTV under NGN umbrella will be a very reasonable method.
(2) IPTV is a means to complete triple-play services
From NGN’s point of view, IPTV could be regarded as a means to complete its triple-play service
bundles – the combination of voice, data, and video service. In addition, IMS functional architecture
comprises some functional entities and related reference points. IPTV functional architecture should
be also defined at functional entity level as like IMS done it. Therefore, the functional entities of
IPTV can be effectively aligned with and easily integrated with those of IMS. It is the reasonable
decision to define IPTV architecture on the basis of functional entity.
Before starting to study on IPTV functional architecture, we have to examine some considerations;
-
Which functional entities of IMS can be reused for IPTV functional architecture without
their extension?
-
Which functional entities of IMS are needed to be extended for reuse in IPTV functional
architecture?
-
What functional entities must be newly defined only for the support of IPTV service?
This contribution proposes to choose two phase method in defining IPTV functional architecture to
reply to the above considerations. First phase is to define the functional entities required for the
purpose of video delivery. In second phase, the new functional entities to integrate video service
into conversational service will be defined. FG IPTV-C108 is an example to try to define IPTV
functional architecture within the scope of first phase.
Proposal
This contribution proposes to define IPTV functional architecture on the basis of functional entity,
and to start the work in two phases.
-----------