1. SOURCE
TTA
TITLE
Extension of Application Network Interface in NGN Architecture
MEETING
CJK 08 NGN 12
CONTACT
Jeong Yun Kim ( )
Tel :
Fax :
Extension of Application Network Interface in NGN Architecture April, 2008
Jeong Yun Kim

2. Contents
Overview
Problem statements
Discussion
Proposal

3. 1. Overview Y.2012 “Functional requirements and architecture of
the NGN of Release 1”
Application network interface
Interface which provides a channel for interactions and
exchanges between applications and NGN elements.
Application may break into two categories:
those trusted by network/server providers: may consist of
network/server providers themselves
those not trusted by network/server providers: may consist
of independent service providers, whose access to
southbound resources must be authenticated, controlled,
and filtered by the functions in the service enablers

4. 1. Overview
NGN architecture overview

5. 1. Overview NGN service architecture
ASF&SSF works in conjunction with the service control
functions to provide end-users and applications with
the NGN services
Through the ANI, the functional area of ASF&SSF offers
service-enabling resources to the "applications" area,
independently of the underlying network technologies
Through the ANI, the "applications“ area benefits from the capabilities and resources of the "NGN infrastructure" functional area
Application interactions with ASF&SSF are handled through the ANI reference point

6. 1. Overview
ASF&SSF
ASF&SSF may reside either in the end-user's home network or in a third-party location.
Applications
ANI
A-1: AS-FE*
Application Support Functions and Service Support Functions
A-2: APL-GW-FE*
A-3: APL-SCM-FE*
A-4: SS-FE

7. 1. Overview
ASF&SSF
Residing either as a trusted entity in the user's home network or as an un-trusted entity in a third-party location (requiring certain level of authentication), ASF&SSF interacts with other entities in the network as shown in Figure 7

8. 1. Overview Application gateway functional entity (APL-GW-FE)
It provides a secure open interface for the applications
to use the capabilities and resources of the NGN.
It is the interworking entity between various functions of
NGN and all external application servers and service
enablers
The applications connected to APL-GW-FE are usually
realized by OSA application servers.

9. 1. Overview Interworking with service creation environments
Y.2201 “NGN Release 1 Requirements”
Interworking with service creation environments
Open service creation environment: Examples of this class
of environment using ANI include OSA/Parlay, Parlay X, OMA
IMS-based service creation environment
IN-based service creation environment: INAP, CAMEL, WIN

10. 1. Overview Y.IPTVarch “IPTV architecture” IPTV Application Functions
An IPTV Service is offered to an end-user by a Service
Provider, it may contain one or more Applications that
provide different features to the End User such as
Linear TV, Content on Demand, Communications, etc

11. 1. Overview Third Party Application Functions
invoke application interfaces to make use of IPTV
functionality
support the development of third party applications
Third Party Application Gateway Functional Block
provides a controlled interface for the Third Party
Application Functions to utilise the IPTV related capabilities
and resources

12. 1. Overview

13. 2. Problem statements Applications are categorized into 2 types
trusted or not trusted
In case of not trusted Applications, it is natural that the Applications connect with APL-GW-FE through ANI
But, in case of trusted Applications, it is a wonder that the Applications only connect with APL-GW-FE even though the Applications can support SIP protocol as well as API.
Therefore, it is allowed for trusted Applications to have direct interaction with AS-FE without through APL-GE-FE

14. 2. Problem statements ANI
According to the Fig. 7, ANI indicates the interface between Applications and APL-GW-FE
Applications has to interact with other FEs in ASF&SSF through APL-GW-FE
It means that Applications have direct interaction only with APL-GW-FE
Otherwise, Applications have indirect interaction with other FEs in ASF&SSF, and require the interworking processing with APL-GE-FE
Therefore, it is required to avoid unnecessary interworking processing and get rid of the annoying constraint

15. 2. Problem statements ASF&SSF
ASF&SSF may reside either in the end-user's home Network or in a third-party location. But it is not reasonable for ASF&SSF to reside both in the end-user's home Network and in a third-party location, simultaneously
Applications could be either 3rd Party or not
If 3rd Party Applications want to interact with ASF&SSF in a third-party location, it better to have direct interaction with FEs in the ASF&SSF instead of indirect interaction such as ANI
Therefore, the current definition about both ANI and ASF&SSF need to be more obviously identified

16. 3. Discussion Two alternatives for extending ANI Third Party
Applications
Applications
ANI
A-1: AS-FE*
Application Support Functions and Service Support Functions
A-2: APL-GW-FE*
A-3: APL-SCM-FE*
A-4: SS-FE

17. 3. Discussion
Two alternatives for extending ANI

18. 4. Proposal Two alternatives to reflect the proposals
FRA R1 corrigendum
FRA R2