1. FG-FN results and future steps
20th CJK UNIOT-WG
TTC
Takashi Egawa 1

2. I. FG-FN results

3. Future Network activities in ITU-T
ITU-T Study Group (SG) 13 established two groups to study Future Networks
Question 21 (Q.21)
Standing group
Limited to ITU-T members
Possible to make ITU-T recommendations
Focus Group on Future Networks (FG-FN)
Temporary group (~ )
Open to everybody
Asks its parent SG to make its deliverable ITU-T recommendation
Since the establishment of FG-FN, all technical discussions were in FG-FN; Q.21 worked as a caretaker of FG-FN

4. FG-FN Scope
The Focus Group, by collaborating with worldwide future network (FN) communities (e.g., research institutes, forums, academia and etc), aims to
collect and identify visions of future networks, based on new technologies,
assess the interactions between future networks and new services,
familiarize ITU-T and standardization communities with emerging attributes of future networks, and
encourage collaboration between ITU-T and FN communities.

5. To achieve this objective the Focus Group will
FG-FN Objective
The objective of the Focus Group is to document results that would be helpful for developing Recommendations for future networks.
To achieve this objective the Focus Group will
gather new ideas relevant to Future Networks and identify potential study areas on Future Networks,
describe visions of the Future Networks,
identify a timeframe of Future Networks,
identify potential impacts on standards development, and
suggest future ITU-T study items and related actions.

6. Milestones 1. 2009; ITU-T SG13; Establishment of FG-FN
Question 21 (Q.21) was also established
6.2009; FG-FN Sweden
Collocated with FIREweek
; FG-FN Lake, US
Collocated with GENI Engineering Conference (GEC)
1.2010; FG-FN Switzerland
Collocated with NGN-GSI
3.2010; FG-FN Japan
Collocated with Int. Symposium on ICT System Testbed
4.2010; ITU-T SG13; FG-FN lifetime was extended till
6.2010; FG-FN Switzerland
9.2010; FG-FN Switzerland
; FG-FN Korea
; FG-FN Slovenia
1.2011; ITU-T SG13; FG results review
1st half: information collection phase; 2nd half: document development phase

7. Management Chairperson Vice-chairpersons Mr. Takashi Egawa (NEC)
Succeeded the position from Mr. Naotaka Morita (NTT) at FG-FN #4 (3.2010)
Vice-chairpersons
Mr. Hyoung-Jun Kim (ETRI)
Prof. Dr. Alex Galis (UCL)

8. Developed deliverables
Developed overall vision document and three supporting specific technology document, plus two others
Overall vision document ‘Future Networks: design goals and promising technologies (FNvision)’
Identifies FN’s high-level objectives, design goals and time frames
Mature to publish
Three supporting specific technology document
Framework of Network Virtualization (FNvirt)
Overview of Energy Saving of Networks (FNenergy)
Identifiers and Identification processes in Future Networks (FNidentification)
Two misc documents
Terminology
Project descriptions; information on research activities going in various places

9. Appropriate timeframe: 2015-2020
Key findings (1/3)
New social requirements (e.g., environment), New application areas (e.g., M2M, cloud, smart grid), new implementation technologies are emerging
These may introduce the development of new network architectures; we call this Future Networks
Appropriate timeframe:
Possible differentiator of FN from existing network architectures
Environment awareness; ‘of networks’ and ‘by networks’
Service awareness; how to manage huge amount of extremely divers services?
Data awareness; today’s network is mainly used to access data, but not designed for that
Social-economic awareness; architecture must pay attention to the influence of social-economic issues on e.g., evolvability or service universalization
As far as FG-FN reviewed, there is no consensus on the architecture
or the priority of requirements

10. Key findings (2/3) Various important technical areas are emerging
FG developed three deliverables for each areas (Network virtualization, electric power savings, and identification processes and identifiers)
There are other important areas, but documents were not developed because of limited resources
Network virtualization
Enabler for co-existence of different network architecture in a physical network
Important tool for network management to manage diversified requirements of each applications
Electric power savings
Important to reduce environmental impact as well as avoiding power consumption (and resulting heat, etc.) to become the limitation for network operation
Identification processes and identifiers
Identifiers themselves are not new; but they are the starting point for everything, in particular for better mobility and for data acces

11. Key findings (3/3)
To design FN, wider collaboration than traditional ICT framework is necessary.
Today’s promising areas are all interdisciplinary ones between ICT and other industries Cloud: computer, smart grid: power, IoT: health, vehicle, etc.
ICT has become an infrastructure of every industry, so we need to learn their needs to design future networks We can’t design smart grid ready network without understanding power industry’s requirements

12. II. Future steps

13. Proposal to SG13 at 1.2011 Documents No new GSIs, no WP or question
This will be discussed and decided at the FG-FN#8.
Documents
FN vision
approve it as a recommendation immediately
Distribute it to all SG13 questions to consider what to do next
Network virtualization (FNvirt), Power savings (FNenergy): continue development at Q.21/13
Identification process (FNidentifier): to stop development; if necessary it can easily re-started in Q.21/13 or some other groups
No new GSIs, no WP or question
FNs is a very important topic, but
it is still in the pre-standardization phase
Discussion point: if collaboration with other industries is the key, what is the appropriate way to handle this? There is Q.21, but it’s resources are very limited.

14. Backup slides

15. Some FG results
FG-NGN  NGN-GSI (SG13, 11, etc.)
FG-IPTV  IPTV-GSI (SG13, 16, etc.)
OCAF-FG  new question (Q.16/13)
NGNM-FG  just finished
FG-IdM  IdM-GSI (Q.10/17, Q.16/13)
FG-ICT&CC  new WP (WP3/5)
FG-CarCom  FG-CarCom II, after 4 month interval