Proposed modifications for Appendix II in Y.NGN-Web

advertisement
INTERNATIONAL TELECOMMUNICATION UNION
NGN-GSI – C 821 – E
TELECOMMUNICATION
STANDARDIZATION SECTOR
August 2010
English only
STUDY PERIOD 2009-2012
Original: English
12/13
Question(s):
NGN-GSI – CONTRIBUTION 821
Source:
ETRI
Title:
Proposed modifications for Appendix II in Y.NGN-Web
1. Introduction
This is the proposal for Appendix II in Y.NGN-Web. This contribution compares related functions
specified in Y.2235 and Y.NGN-Web. After that, this contribution provides the modified text for
Appendix II in Y.NGN-Web.
2. Comparison of functions specified in Y.2235 and Y.NGN-Web
Figure 1 shows the functional model for CWB (converged web browsing) capabilities. This model
consists of five components: a web browsing function, a web proxy function, a web serving
function, a profile serving function and a content transformation function.
Figure 1 – Functional model for converged web-browsing capabilities
Contact:
Gyu Myoung Lee
KAIST
Korea (Republic of)
Tel:+82-42-866-6828
Fax:+82-42-866-6226
Email:gmlee@kaist.ac.kr
Contact:
Noel Crespi
Institut Telecom
France
Tel:+33 (0)1 60 76 46 23
Fax:+33 (0)1 60 76 45 78
Email: noel.crespi@it-sudparis.eu
Contact:
Jun Kyun Choi
KAIST
Korea (Republic of)
Tel:+82-42-866-6122
Fax:+82-42-866-6226
Email:jkchoi@ee.kaist.ac.kr
Contact:
Won Ryu
ETRI
Korea (Republic of)
Tel: +82-42-860-6290
Fax:
Email: wlyu@etri.re.kr
Attention: This is not a publication made available to the public, but an internal ITU-T Document intended only for use by the
Member States of ITU, by ITU-T Sector Members and Associates, and their respective staff and collaborators in their ITU related
work. It shall not be made available to, and used by, any other persons or entities without the prior written consent of ITU-T.
-2NGN-GSI – C 821 – E
From Figure 2, we can see positioning of web proxy function and web service component in NGN.
Web proxy function in Y.2235 reside in service control functions of NGN service stratum and web
service component reside within service control and content delivery functions of NGN.
Y.2235
Y.NGN-Web
Applications
Service Stratum
Application Support
Functions and
Service Support Functions
Application
Functions
Management
Functions
S. User
Profile
Functions
Web Service
Component
IPTV
Service Component
Legacy
Terminals
Legacy
Terminals
IP Multimedia
Component
IP Multimedia
&PSTN/ISDN
Simulation
Service Component
GW
GW
Other Networks
PSTN / ISDN Emulation
Service Component
Service
Control
And
Content
Delivery
Functions
Network Attachment
T.User
User
Control Functions
Profile
Profile
(NACF)
Functions
Functions
Customer
Networks
Access
Network
Access Transport
Functions
Functions
NGN
Terminals
Mobility Management
Control Functions
(MMCF)
Edge
Functions
Resource and Admission
Control Functions
(RACF)
Core
Transport
Core
transport
Functions
Functions
Transport Stratum
End-User
Functions
* Note: Gateway (GW) may exist in either Transport Stratum
or End-User Functions.
Figure 1.Positioning of web proxy function and web service component in NGN
Figure 3 shows NGN functional entities interacting with a web proxy function of Y.2235 and PWCFE of Y.NGN-Web.
Y.2235
Applications support functions
and service support functions
Y.NGN-Web
A-1: AS-FE
A-3: APL-SCM-FE
Application support functions and service support functions
Service control functions
Service control functions
Web proxy function
S-13: media
resource control FE
S-5: service user
profile FE
Directory
PWC-FE
NACF
WSGC-FE
Other
Service
Providers
Web Media Functions
RACF
T-12: T. user
profile FE
Other Service
Components
IPTV
PSTN/ISDN
IMS
Web Service
Control
Functions
End-user
T-16: policy
decision FE
PCC-FE
WMRC-FE
WMGC-FE
WMT-FE
Web Server
Content
Transport control functions
T-8: media resource
processing FE
Transport control functions
Transport processing functions
Y.2235(08)_FI-2
Figure 3. NGN functional entities interacting with a web proxy function of Y.2235 and PWC-FE of
Y.NGN-Web
From Figure 1, 2, and 3, we can identify the relationships between web related functions within
service control functions. The followings have similar functionalities.
 Web proxy function (Y.2235) and PWC-FE (Y.NGN-Web)
 Profile serving function (Y.2235) and directory (Y.NGN-Web)
 Content transformation function (Y.2235) and WMT-FE (Y.NGN-Web)
-3NGN-GSI – C 821 – E
3. Proposal
In this contribution, we would like to modify the current Appendix II based on comparison result
between Y.2235 and Y.NGN-Web. We also would like to invite contributions for further
comparison with Y.2012 and other on-going draft recommendations (e.g., Y.NGN-SIDE, Y.OSEarch, Y.WoT, etc) in the future.
References
[1] ITU-T Draft Recommendation Y.NGN-Web, Functional Requirements and Architecture of
Web Service Component in NGN
[2] ITU-T Recommendation Y.2235 (2008), Converged web-browsing service scenarios in
NGN
[3] ITU-T Recommendation Y.2012 (2010), Functional requirements and architecture of next
generation networks
-4NGN-GSI – C 821 – E
Attachment: the modified Appendix II of Y.NGN-Web
________________
Appendix II
Mapping of related functions between ITU-T Recommendations and Y.NGN-Web
(This appendix does not form an integral part of this Recommendation)
The appendix provides mapping information of related functions between Y.NGN-Web and other
Recommendations.
1. Y.2235 and Y.NGN-Web
The Table II-1 show mapping of related functions between Y.2235 and Y.NGN-Web.
Table II-1 Mapping between Y.2235 and Y.NGN-WEB
ITU-T Recommendation Y.2235
ITU-T Draft Recommendation Y.NGN-Web
Functional entities
Corresponding functional entities
Web Proxy Function
PWC-FE
Profile Serving Function
Directory
Content Transformation Function
WMT-FE
(Editor’s Note) Application Gateway Functional Entity, Media Resource Control Functional Entity,
Policy Decision Functional Entity, Policy Enforcement Functional Entity, Media Resource
Processing Functional Entity, Service User Profile Functional Entity and Application Service
Coordination Manager Functional Entity are related to Recommendation Y.2012. So, relevant
contribution for mapping table between Y.2012 and Y.NGN-web is required.
(Editor’s Note) For further clarification, we need to investigate relationships with draft
recommendations (e.g., Y.NGN-SIDE, Y.OSE-arch, Y.WoT, etc) on service aspects under
developing in SG13.
________________
Download