1 / 17

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

“4WARD – Architecture and Design for the Future Internet”. D2.1 Technical Requirement Hoon-gyu Choi hgchoi@mmlab.snu.ac.kr 2008.11.05. Contents. Introduction 4WARD overview Non-Technical Aspects Technical Requirements Annex – Detailed requirements Summary. Introduction.

claudia-mcintyre
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “4WARD – Architecture and Design for the Future Internet” D2.1 Technical Requirement Hoon-gyu Choi hgchoi@mmlab.snu.ac.kr 2008.11.05

  2. Contents • Introduction • 4WARD overview • Non-Technical Aspects • Technical Requirements • Annex – Detailed requirements • Summary MMLAB

  3. 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 MMLAB

  4. 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 MMLAB

  5. 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 MMLAB

  6. Overall Approach Input WP1 WP6 WP2 WP4 Output WP3 WP5 MMLAB

  7. 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 MMLAB

  8. Requirements Analysis Process • Starting Point – overall 4WARD mission statements • 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 MMLAB

  9. Requirements Analysis Process • 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 • Scenarios • Use case, Growth, Exploratory • Requirements • Views • Representation of a whole system MMLAB

  10. 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 MMLAB

  11. 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 MMLAB

  12. 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] MMLAB

  13. 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] MMLAB

  14. 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 MMLAB

  15. 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 MMLAB

  16. 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 MMLAB

  17. Reference • http://www.4ward-project.eu/ MMLAB

More Related