Abstract

This contribution proposes to discuss possible IPTV interconnection scenario between Non-NGN and NGN. As a consequence of this discussion we propose to change the description and figures contained in Section 10.2.

Background and discussion

At the last FG-IPTV meeting, the importance of IPTV Non-NGN and NGN interconnection was recognized and the new section 10.2 was created. However, the text and figures in 10.2 are simple copy of those in the preceding section 10.1 and need precise technical review in this meeting.

First of all, we should identify the IPTV terminal capability placed on the left hand side in Figure 10-4, whether it is NGN-compliant or not. Although neither the original contribution nor the present description defines the IPTV terminal capability, the reader of this text would think it is not compliant to NGN interface. In addition to that, it would be technically difficult to connect NGN compliant IPTV terminal to Non-NGN network. So it could be assumed that the IPTV terminal in Figure 10-4 is not NGN compliant. If this assumption is correct, the present Figure 10-4 shows the case Non-NGN compliant IPTV terminal subscribed to Non-NGN IPTV network accesses the IPTV application in NGN network, most probably via Session Border Controller(S/BC) functions, which are defined in Y.2012 Supplement 1.

On the other hand, the description and figures in the preceding section 10.1 shows the case that NGN-compliant terminal, which has moved from the Home NGN network to Visited NGN network, accesses the IPTV application in Home NGN network. Here, the IPTV terminal is assumed to be NGN-compliant. Actually section 10.1 describes two types of NGN roaming cases, which are also defined in Figure 6 and Figure 7 of Y. NACF-R1, NGN GSI/DOC 221 in September 2007. Roaming is a general term that refers to the extending of connectivity service in a location that is different from the home location where the service was registered.

Consequently the newly created section 10.2 can be judged not intending to describe roaming cases between Non-NGN network and NGN network, but simply describing Non-NGN IPTV terminal subscribed to Non-NGN IPTV network accesses IPTV application in NGN network. Contact: Kazunori Matsuo

KDDI CorporationJapan

Fax: +81 3 6678 2474Email: ka-matsuo @kddi.com

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.

INTERNATIONAL TELECOMMUNICATION UNION FOCUS GROUP ON IPTV

TELECOMMUNICATIONSTANDARDIZATION SECTOR

STUDY PERIOD 2005-2008

FG IPTV-C-1028

English only

WG(s): 1 7th FG IPTV meeting: Qawra, St Paul’s Bay, Malta, 11-18 December 2007

CONTRIBUTION

Source: KDDI Corporation

Title: Proposed changes to Section 10.2 “IPTV Interconnection between Non-NGN network and NGN network”

- 2 -FG IPTV-C-1028

Therefore, modifications are required to both the description and the figures in 10.2 in order to avoid confusion and possible misunderstanding.

Proposal

In order to let the reader to understand the meaning of IPTV Non-NGN and NGN interconnection, we propose the following modifications to the description and the figures in section 10.2:

(1) Replace the notation of Home Provider and Visited Provider by NGN network and Non-NGN network respectively.

(2) In the description, replace RACF function by Resource Control function where appropriate, since RACF is considered as a unique function of NGN Network.

(3) Add the description of Session Border Controller(S/BC), since the conversion function provided by S/BC for media path as well as signaling path is considered necessary for Non-NGN and NGN interconnection.

(4) Delete Figure 10-5 and its description from Section 10.2, since the roaming service shown by this figure would not be supported between Non-NGN and NGN network.

(5) Interchange the position of Service Control Function box and Content Delivery Function box in Figure 10-4 as agreed at the 5th FG-IPTV meeting.

Reference

FG.IPTV- DOC-0148, working document: IPTV Architecture

Y.2012 Supplement 1, Session/border control(S/BC) functions

Draft Y.NACF-R1, NGN GSI/DOC 221, September 2007

Attachment Proposed amended text and figures in Section 10.2

- 3 -FG IPTV-C-1028

Attachment Proposed amended text and figures in Section 10.2

10.2 IPTV Interconnection between Non-NGN network and NGN network

10.2.1 Interconnection with the visited providerNon-NGN network

Figure 9-410-4 illustrates the case that IPTV terminal connected to Non-NGN network accesses the application function in NGN network. interconnection between the home provider and the visited provider. In this figure, visited provider is Non-NGN network while home provider is NGN network.

On the Home Provider part iIn this figure, either Core IMS or IPTV Service Control Function is used depending on the capabilities of the home provide in rNGN network, which. The Service Control Functions of each provider requests the network resources to its RACF. On the Non-NGN side part of Visited Provider, request resource and admission control function are may or may not be supportedcontrolled by IPTV Service Control Function. In this figure, no RACF-to-RACF interface is given. Communication between Resource Control and RACF can be implemented through the interconnection between SCF.It is expected that Session Border Control(S/BC) functions be placed between Non-NGN and NGN for both media path and signaling path conversion. This S/BC functions could also coordinate QoS control between Non-NGN and NGN in case some kind of resource control function is supported in Non-NGN.

Figure 10-4: Interconnection with the Non-NGN network

Figure 10-5 illustrates the interconnection between the home provider and the visited provider. In this figure, visited provider is Non-NGN IPTV network while home network is NGN IPTV network. On Home Provider part in this figure, either Core IMS or IPTV Service Control Function is used depending on the capabilities of the home provider. The RACF of the home provider requests the network resources of the visited provider to the Resource Control of the visited provider.

There can be the access network that the Service Control Functions are not applicable due to the absence of the Service Control Functions or the agreement between providers. In this case, interface between Resource Control and RACF should be given and is used to request the network resources of the visited network.

- 4 -FG IPTV-C-1028

Figure 10-5: Interconnection with the visited provider without Service Control Functions

_______________