“4WARD – Architecture and Design for the Future Internet”

“4WARD – Architecture and Design for the Future Internet”

D2.1Technical Requirement

Hoon-gyu [email protected]

2008.11.05

Contents

• Introduction• 4WARD overview• Non-Technical Aspects• Technical Requirements• Annex – Detailed requirements• Summary

23年 4月 20日 MMLAB 2

Introduction

• Both the architecture and the engineering processes of the Internet no longer suitable

• We want to bring innovation back into the network

• Some technical issues to deal with:– Can we cope with the massive number of

communicating things?– Separation of naming and addressing

• Policy and governance

• We need a holistic global approach – 4WARD Project

23年 4月 20日 MMLAB 3

4WARD Objective

• To increase the competiveness of European network industry

• To improve the quality of life for European citizen– By creating a family of dependable and interoperable

networks providing direct and ubiquitous access to information

• To make the development of networks and networked applications faster and easier, leading to both more advanced and more affordable communication services.

• 4WARD takes a “clean slate” approach

23年 4月 20日 MMLAB 4

Project info

• Status– Start Date

• 2008-01-01

– Duration• 24 months

– Project Cost• 23.25 million euro

– Contract Type• Collaborative project

(generic)

– End Date• 2009-12-31

– Project Funding• 14.45 million euro

• Project Lead– Ericsson AB,

Sweden

23年 4月 20日 MMLAB 5

Overall Approach

23年 4月 20日 MMLAB 6

Input

Output

WP1

WP6

WP2

WP4

WP3

WP5

Deriving 4WARD Requirement

• It is important to identify the requirements that consistently should cover the whole 4WARD approach to a Network of the Future

• Requirements Analysis Process

23年 4月 20日 MMLAB 7

Requirements Analysis Process

1. Starting Point – overall 4WARD mission statements2. Stakeholders are identified

– Technical• Network architects, planner, equipment vendors,

operators– Non-technical

• Customers/users– Human users, Business and private users, Content

Producers, Advertisers

• Legal agreement bodies– Regulators (national, EU)– Legislator– governance

23年 4月 20日 MMLAB 8

Requirements Analysis Process

3. Concerns– The purpose or missions of the system– The appropriateness of the system for use– Feasibility of constructing the system– The Risk of system development and operation– Maintainability, deployability, and evolvablility

4. Scenarios• Use case, Growth, Exploratory

5. Requirements6. Views

– Representation of a whole system

23年 4月 20日 MMLAB 9

Non-technical Aspects

• Usage and Services– How will users benefit from the technology advances of

4WARD• E.g. Shall support

– existing as well as emerging business models– service provider requirements for managing their

operation– mass market customer requirement

• Socio-Economics– Services will become ubiquitous, will be underlying to all

social and economic infrastructure• E.g. Shall support safety-critical applications

• Policy, Governance and Regulation

23年 4月 20日 MMLAB 10

Technical requirements

• Primary concern of 4WARD– Information-centric network

• Users only need to be aware of the information identifiers and not of the location of the information

– Future Internet connectivity• Should always available

– Interoperability• Assure the interoperability between different

architectures, different domains– Security

• Privacy, lawful interception

23年 4月 20日 MMLAB 11

Technical Requirements: details

• General Properties [000]– Ubiquity [4W.010], Mobility [4W.020], Scalability [4W.030],

Usability [4W.040]

– Wireless Awareness [4W.050], Green network[4W.060]

• Services and application support [100]– Information-Centric Networking [4W.100]

– Generic Connectivity Services [4W.110], Seamless Service [4W.130]

– Quality-of-Service [4W.120]

• Internetworking [200]– Naming, Addressing, and Name resolution [4W.200]

– Interoperability [4W.210], composition [4W.230]

23年 4月 20日 MMLAB 12

Technical Requirements: details

• Architecture [300]– Diversity and Extensibility [4W.300]

– Virtualization [4W.320]

• Management [400]– Monitoring [4W.400]

– Self-management Properties [4W.410]

• Security [500]– Integrity and Privacy [4W.500]

– Lawful Interception [4W.510]

– Service Abuse [4W.520]

23年 4月 20日 MMLAB 13

Annex 1: From WP Perspectives

• WP (Work Packages)– Based on Bottom-up approach– Detailed requirements are collected by inquiring the

expert groups from the 4WARD Work packages

23年 4月 20日 MMLAB 14

WP1 Business Innovation, Regulation, and Dissemination

BIRD.010-270

WP2 New Architecture Principles and Concepts (NewAPC)

NewAPC.010-120

WP3 Network Virtualisation (VNet) VNET.010-060

WP4 In-Network Management INM.010-140

WP5 A new path abstraction ForMux.010-160

WP6 Networking of Information (NetInf) NetInf.010-090

Annex 2: From Technical themes

• Mobility– Mob.010 – Mob.120

• Quality of Service– QoS.010 – QoS.120

• Security– Sec.010 – Sec.110

• Physical layer awareness– PHY.010 – PHY.090

• Multi-Operator awareness– MultOp.010 – MultOp.080

23年 4月 20日 MMLAB 15

Summary

• In 4WARD, technical requirements are defined• These overall requirements will be transferred

into various specific architecture designs, concepts and realizations, highlighting different views of the respective work packages or technical themes according to the delivery plans.

• Also, these requirements will server as a useful reference for other research groups

23年 4月 20日 MMLAB 16

Reference

• http://www.4ward-project.eu/

23年 4月 20日 MMLAB 17