Docstoc

CONTRIBUTION

Document Sample
CONTRIBUTION Powered By Docstoc
					 INTERNATIONAL TELECOMMUNICATION UNION                                                        FOCUS GROUP ON IPTV
 TELECOMMUNICATION                                                                                FG IPTV-C-0677
 STANDARDIZATION SECTOR
 STUDY PERIOD 2005-2008                                                                                         English only

 WG(s): 5                                                                                             5th FG IPTV meeting:
                                                                                                    Geneva, 23-31 July 2007
                                                      CONTRIBUTION
 Source: NTT Corporation
 Title:      Issues on the IPTV Home Network: Remote Management


 1. Introduction
 As we agreed at the last FG-IPTV meeting, the home network discussion will be done basically
 based on the HGI document (FG IPTV-IL-0060). Although HGI document is well organised and
 provides almost a complete set for the home network technologies, the current version of document
 does not cover sufficiently the characteristic of IPTV.
 The contribution raises issues related to IPTV for further discussion.



 2.         The relationship between HGI and WG5 document



                        Table 1 – The proposed relationship between both documents

             Home Network WD                          Corresponding part of HGI document                             Note
 7 Remote management
 7.1 Management Architecture                         5.4 Management Architecture                          See 3.1
 7.1.1     Device Management                         5.4.1 Device Management                              See 3.2
 7.1.2     QoS Management                            5.4.2 QoS Management
 7.1.3     Security Management                       5.4.3 Security Management                            See 3.3
 7.1.4 Software Management and                       5.4.4 Software Management and Upgrade
 Upgrade
 7.1.5 Performance Monitoring and                    5.4.5 Performance Monitoring and
 Diagnostics & Troubleshooting                       Diagnostics & Troubleshooting
 7.1.6     Local Management Application              5.4.6 Local Management Application                   See 3.4.
 7.2       Management requirement                    6.5 Management                                       See 3.5
 7.2.1     Northbound Interfaces                     6.5.1 Northbound Interfaces                          See 3.6
 7.2.2     RMS Requirements                          6.5.2 RMS Requirements                               See 3.7


Contact:              Yoshinori Goto                                               Tel:       +81 43 211 2109
                      NTT                                                          Fax:       +81 43 211 7493
                      Japan                                                        Email      goto@ansl.ntt.co.jp
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.
                                                         -2-
                                                   FG IPTV–C–0677



7.2.3 General Access gateway                   6.5.3 General HG configuration and
configuration and management                   management

7.2.4 Definition of the data model             6.5.4 Definition of the data model
supported                                      supported
7.2.5 Diagnostics, notifications and           6.5.5 Diagnostics, notifications and alarms
alarms
7.2.5.1 Notifications and logging              6.5.5.1 Notifications and logging
7.2.5.1.1 Mechanisms                           6.5.5.1.1 Mechanisms
7.2.5.1.2 Mechanisms                           6.5.5.1.2 Notification cases
7.2.5.2 Statistics and Diagnostics             6.5.5.2 Statistics and Diagnostics
7.2.5.2.1 Mechanisms                           6.5.5.2.1 Mechanisms
7.2.5.2.2 Defined diagnostics and statistics   6.5.5.2.2 Defined diagnostics and statistics
7.2.6   End device management                  6.5.6 End device management
7.2.6.1 Device Identification                  6.5.6.1 Device Identification                  See 3.8
7.2.6.2 Activity discovery and Database        6.5.6.2 Activity discovery and Database        See 3.9
management                                     management
7.2.7 Local Access Gateway                     6.5.7 Local HG management user
management user interface                      interface
7.2.7.1 General                                6.5.7.1 General
7.2.7.2 Design guidelines                      6.5.7.2 Design guidelines
7.2.7.3 Operator Portal User Interface         6.5.7.3 Operator Portal User Interface link
link
7.2.7.4 Contents and functionality             6.5.7.4 Contents and functionality
7.2.8 Firmware management and                  6.5.8 Firmware management and updates
updates
7.2.8.1 General                                6.5.8.1 General
7.2.8.2 Software upgrades                      6.5.8.2 Software upgrades
7.2.8.3 Configuration                          6.5.8.3 Configuration
7.2.8.4 User Interaction                       6.5.8.4 User Interaction
7.2.9   Security management                    6.5.9 Security management
7.2.9.1 Firewall management                    6.5.9.1 Firewall management
7.2.9.2 Application Layer Gateway              6.5.9.2 Application Layer Gateway
Management                                     Management
7.2.10 End-device recommendations              6.5.10 End-device recommendations              See 3.10



3. Issues of consideration

3.1 Issue of 7.1 Management Architecture
This clause corresponds to clause 5.4 (HGI)
                                                    -3-
                                              FG IPTV–C–0677


The management architecture including NW side entities such as RMS and ACS should be aligned
with WG1 and WG4.
The channel change functionality defined in FG IPTV-DOC-083 (see below) may need to be
considered since it is possible that the Access Gateway (Home Gateway) deal with the multicast
protocol.

IPTV_NET_109: The IPTV Architecture is recommended to support the ability for the DNGF to
support channel change functions between the ITF and service provider [IIF.ARCH.HOME.55].


Figure 11 and 12 (HGI) should be revised.



3.2 Issue of 7.1.1   Device Management
This clause corresponds to clause 5.4.1 (HGI)
Figure 13, 14, 15 and 16 should be revised.
Table 2 shows some categories such as D, U, CD and so on for terminal device from the viewpoint
of remote management capability. The relevant category for IPTV-TD should be specified.



3.3 Issue of 7.1.3   Security Management
This clause corresponds to clause 5.4.3 (HGI)
Security management should be aligned with WG3.



3.4 Issue of 7.1.6   Local Management Application
This clause corresponds to clause 5.4.6 (HGI)
Figure 17 should be revised.


3.5 Issue of 7.2 Management requirement
The original text in clause 7.2 of FG IPTV-DOC-0094 should be re-writed as a requirement.
The original text: “The IPTV TD shall support an IP-based bi-directional communication including
a software updating mechanism for remote management.”


This clause corresponds to clause 6.5(HGI)


3.6 Issue of 7.2.1   Northbound Interfaces
This clause corresponds to clause 6.5.1(HGI)
                                                   -4-
                                             FG IPTV–C–0677


Comment on R214 –Further study is needed on the interface for HG/ACS. Alignment with WG1
and WG4 should be discussed.
R214: “The HG/ACS communication interface MUST comply with all the mandatory requirements
of the CWMP protocol v1 as defined in TR-069 [1].”


3.7 Issue of 7.2.2   RMS Requirements
This clause corresponds to clause 6.5.2(HGI)
Comment on R216, R217, R218, R219, R220, R221, R222, R223 and R224 – RMS needs to be
specified in IPTV architecture. The requirements regarding RMS need to be aligned with WG4.


Comment on R220 – “Northbound Interface” needs to be specified.


Comment on R221 – This requirement is related to the detailed function of RMS, the user interface
of RMS, and not related to IPTV service. Proposed for deletion.


3.8 Issue of 7.2.6.1 Device Identification
This clause corresponds to clause 6.5.6.1(HGI)
Comment on R254, R255 and R256 - These requirements state the gateway’s capability of
discovering and identifying the end device. The case meeting IPTV end system should be
specified.
Comment on R264 and R265 - The use of DHCP option codes should be discussed with relating
documents and practices.


3.9 Issue of 7.2.6.2 Activity discovery and Database management
This clause corresponds to clause 6.5.6.2(HGI)
Comment on R284, R285, R286 and R287 - These requirements states the management of lease
time of DHCP that defines the interval of renewing process. The possibility of causing the service
interruption or destruction of IPTV service during renewing process should be considered.


3.10 Issue of 7.2.10 End-device recommendations
This clause corresponds to clause 6.5.10(HGI)
Comment on R340 – This requirement is relevant in case of IPv4. The following modification is
proposed.
Revised R340: “The IPTV-TDEnd devices is required to MUST support the use of DHCP to
configure IP connectivity during the start-up phase, if it supports and operates in IPv4
enviornment.”
                                                -5-
                                          FG IPTV–C–0677


Comment on R342, R343, R344 and R345 – The relevant documents as well as practices on the use
of DHCP optional code 125 needs to be studied.
R342: “DHCP messages of managed EDs MUST include the IANA Enterprise Number [14] for the
HGI in option 125. This number is 25812”
R343: “The DHCP messages of managed EDs MUST also contain the following Encapsulated
Vendor-Specific Option-Data fields in option 125, as defined in TR-111 and TR-106 [15]
• DeviceManufacturerOUI
• DeviceSerialNumber
• DeviceProductClass”
R344: “Managed EDs of type D MUST also include “DeviceType” in the Encapsulated Vendor-
  Specific Option-Data fields of DHCP option 125. The contents and format of this value are
  identical to the device type suffices as defined by the UPnP forum [16] (i.e.: “urn:uuid”).”
R345: “Managed EDs of types U and CU MUST include “UUID” (Universally Unique IDentifier)
in the Encapsulated Vendor-Specific Option-Data fields of DHCP option 125. The contents and
format of this value are given by RFC 4122 [7]”


                                        ______________

				
DOCUMENT INFO