INTERNATIONAL TELECOMMUNICATION UNION
FOCUS GROUP ON FUTURE
NETWORKS
TELECOMMUNICATION
STANDARDIZATION SECTOR
FG-FN OD-6
Original: English
STUDY PERIOD 2009-2012
1st FG-FN meeting:
Lulea, Sweden, 29 June – 3 July 2009
OUTPUT DOCUMENT 6
Source:
Moderator
Title:
1st Collection of Concept, Key Characteristics and Requirements of Future Networks
For:
Invite further contributions
Background:
This document contains initial materials on concept, vision, requirements and architectural aspect of
Future Networks which collected from the various input contributions at the 1st FG-FN meeting
held in Lulea Sweden from 29 June to 3 July 2009. Because of time limitation, the meeting agreed
to collect relevant valuable information into one document and will need further examination.
Therefore contributions are required for further enhancement of collected information including
better arrangements as well as clarify the relationships between different information but mutually
related.
Summary of Process:
All input contributions are re-reviewed by the Convener and initial collection has been made by the
moderator with the following classifications: Terminology, Vision and Concept, Requirements and
Architecture. Drafting team examined moderator’s initial attempt and enhanced within the drafting
team. Finally 1st FG-FN meeting examined the contents based on input from drafting team.
Future action:
Because of time limitation, all contents in this document are not thoroughly examined and
especially clarification on the relationships between different models, definitions and requirements
which have different flavours are not identified yet. Therefore contributions are strongly required
for further enhancement of the contents.
Contact:
Mr. N. Morita
NTT
Tel:
Fax:
Email
+81 422 59 7464
+81 422 60 7429
morita.naotaka[at]lab.ntt.co.jp
-2FGFN OD-6
Table of Contents
1. Terms and Definitions .......................................................................................................... 3
2. Vision and Concept .............................................................................................................. 4
2.1 High Level Vision................................................................................................... 4
2.2 Vision for network aspects ..................................................................................... 4
3. Requirements ....................................................................................................................... 6
3.1 High level requirements .......................................................................................... 6
3.2 Functional requirements ......................................................................................... 7
3.3 Requirements on specific aspects ........................................................................... 9
4. Architectures ........................................................................................................................ 11
4.1 High Level Model ................................................................................................... 11
4.2 Configuration Model of Future Networks .............................................................. 12
4.3 Virtualization aspects of Future Networks Architecture ........................................ 15
4.4 Autonomic network aspects of Future Networks Architecture .............................. 17
4.5 Specific aspects of Future Networks Architecture ................................................. 19
Appendix 22
1. Status of Mobile Internet related activities ............................................................... 22
2. Status of Multicast Technology activities................................................................. 23
3. Status of Internet security technology activities ....................................................... 23
-3FGFN OD-6
1. Terms and Definitions
[Editor’s Note] Following “Terms and definitions” are used in input contributions. During the
meeting it is requested to examine “Terms and Definitions’ already used in ITU-T such as in
SANCHO and should use if existing terms are useful for the Future Networks aspects rather than
develop own definitions. Contributions are invited to further enhancement.
Autonomic Control Provision of a self-managing virtual resource overlay. The creation of a
Overlay
communication resource overlay with autonomic characteristics for the
purposes of fast and guaranteed service delivery. [FG-FN C23 Page 3]
Error
a discrepancy between a computed, observed, or measured value or condition
and a true, specified, or theoretically correct value or condition. Error is a
consequence of a fault. Errors may cause deviation of a delivered service
from the specified service, which is visible to the outside world. The term
failure is used to denote this type of an error. [FG-FN C17R1 Page 4]
Failure
Deviation of the delivered service from fulfilling the system function.
Transition from correct service delivery to incorrect service delivery. [FG-FN
C17R1 Page 5]
Fault
Adjudged or hypothesized cause of an error. Faults can be internal or external
to system. The prior presence of a vulnerability i.e., an internal fault that
enables an external fault to harm the system, is necessary for an external fault
to cause an error, and possibly subsequent failure(s). [FG-FN C17R1 Page 3]
Federation
None but need to fill up
Future Networks
A network which is able to provide revolutionary services, capabilities, and
facilities that are hard to provide using existing network technologies [FG-FN
C20 Page 5]
Network
Virtualization
the technology that creates logically isolated network partitions overlaid on
top of single physical network infrastructure so that multiple heterogeneous
networks can coexist over the shared infrastructure. Network virtualization
may provide deep programmability so that users can program network
elements on any layers from physical layer to application layer. [FG-FN C10
Page 5]
Resilience
the ability of the network to provide and maintain an acceptable level of
service in the face of various challenges to normal operation [FG-FN C17R1
Page 2]
Server
Virtualization
The ability to run an entire VM with its own (guest) OS on another OS or on
a bare-machine [FG-FN C12 Page 13]
Virtualization
Virtualization refers to a technique for hiding the physical characteristics of
computing resources from the way in which other systems, applications, or
end users interact with those resources. The main objectives of virtualization
are to simplify the use of the underlying resource, to create multiple instances
of the resource, and to separate the uses of the underlying resources. [FG-FN
C10 Page 4]
-4FGFN OD-6
2. Vision and Concept
[Editor’s Note] Following “Visions and concepts” are introduced in input contributions.
Contributions are invited for further enhancement.
2.1 High Level Vision
1) ESC vision from ETRI [FG-FN C03 Page 1~2]
If we highly abstract the future network, it could be seen as a sphere. In a sense, the sphere would
be a kind of virtual media for communication between people. It just seems a black box and is
completely hidden from people. In the environment, it is assumed that people move around the
communication sphere with various movement patterns and communicate with other people
thorough it as illustrated in following figure.
Fig. 2-1 Abstraction of communication sphere
2.2 Vision for network aspects
1) From NiCT [FG-FN C06 Page 3 and 12]
Future networks may not be the continuous evolution of the current Internet / IP technologies
Earth
E: Sustainable Network
E-1 Green network
E-2Efficient spectrum usage
A: Value Creation Network
A-1 Service creation network
A-2 Media creation network
Society
Living Space
Human
B: Trustable Network
B-1 Social infrastructure for trustable network
B-2 Trustable network for human and society
C: Ambient/Ubiquitous Network
C-1 Global-scale sensor/actuator cloud
C-2 : Real-world info. processing platform
Things
D: "Self-* Network
D-1 Network for diversity
D-2 Network unification
D-3 "OMOTENASHI"" (Hospitable) network
FN Fundamentals
Network Architecture
Network fundamentals for knowledge society
Network physical architecture
Fig. 2-2 High level vision of FN
-5FGFN OD-6
2) From MANA [FG-FN C01 Page 4]
Novel solutions for the FN: In order to achieve the objective of having service-aware networks and
network-aware services (that is, service and network resources must be aware of the relevant
environmental conditions, as well as their own state: which is self-awareness), and to overcome the
ossification of the current Internet
3) From NTT [FG-FN C07 Page 3]
•
•
Network as a indispensable partner for social life
–
From various viewpoints such as Medical Care, Education, Crime-prevention etc.
–
Network Design for Environmentalism, Digital Divide, Social Diversity etc.
Basic Infrastructure for various life-styles in networked society
–
•
Digitizing information of the real world, Distribution of digital contexts, Knowledge
Sharing, Risk Management.
For enlarging network users ( human, machine etc. )
–
Huge amount of network traffics and number of networked devices.
–
Flexibility for diversification of network services is important.
Implementation Limits
of Network
Dynamic range expansion
of user requirements
Complexity of Network /
Service Operation
Making “Paradigm Shift”
Every network user can get customized services for his/her needs.
Customer requirements is dynamically reflected in network.
Static or dynamic optimization strategies are provided in any levels of network.
Green (Environmental issues) & Security (Social issues)
Fig. 2-2 Paradigm shift towards Future Networks
-6FGFN OD-6
3. Requirements
[Editor’s Note] Following “Requirements” are introduced in input contributions. Contributions
are invited to further enhancement.
3.1 High level requirements
1) ESC requirements from ETRI [FG-FN C03 Page 2]
To design the architecture of the communication sphere, i.e. future network, it will be appropriate to
focus on users’ perspective rather than network owners’ because future network is envisioned a
social infrastructure, not just an industrial technology.
Firstly, it is required that people can access the future network EASILY regardless of their
intellectual level, age, culture, language skill and so on if we consider the future network is a social
infrastructure which is essential for all people’s daily life.
Next the future network should support people’s communication SAFELY so as to guarantee
people’s communication privacy, to prevent unwanted communications like spam, to protect
people/network from malicious attacks and so on.
In addition, the future network should make sure that people can use the network CHEAPLY (InExpensive) as possible as because it will become a part of people’s daily life, no longer an optional
thing and should be provided regardless of people’s wealth. It also should have pros in terms of
Capex/Opex to guarantee the building of cost-effective future network infrastructure. Green IT
concept, highly required recently, could be included in this vision.
2) Socio-economic (?) considerations for the Future Networks from NiCT [FG-FN C06 Page 9]
Field
Technological Items
Energy saving / Reduction of
environmental impact
- Power saving technology
- Predict, detect, and alert environmental pollution
Disaster management
- Predict, detect, and alert disaster
- Protect important data, facilities, and so on
Medical care
- Healthcare
- Remote medical care
Food shortage
- Improve the food-sufficiency ratio
- Provide safe food
Secure life/society
- Crime prevention
- Accident prevention
- Secure networks
Gaps
- Gaps between cities and countries
- Share knowledge and information
Aging population
- Healthcare
- Care for aging People
Globalization
- Support global mobility
- Support diversity
-7FGFN OD-6
Be adaptive to each user’s
situation

Rapid deploy of services to suit user-context
 Coordination with privacy and related rights
 Protect “digital assets”
Respond to enlarging dynamic ranges of users’
requirements

from sensory data of Kb/s to gigantic data exchange of Tb/s
 allow variety of communication schemes and protocols suitable
and optimized to each application and terminal.
 Provide seamless NW services over wireless and wired access
Future Networks
Be scalable to massive data amount and
huge number of terminals
 Total
Reduce environmental impact
 low
traffic in Peta-bytes
 Billions of tiny/thin terminals (tags and sensors)
 Very large number of transactions and sessions
power-consumption
 Promote “greening” of society through
 “evolvable network” without replacing physical facilities .
Fig. 3-1 High level requirements of Future Networks [From NTT, FG-FN C07 Page 8]
3) Principle considerations for the Future Networks from NiCT [FG-FN C06 Page 8]
Future Networks should be a network for:
 Minimize the Negatives
 Maximize the Potential
‒ To establish new societal systems.
‒ To promote the wisdom of human beings.
‒ To establish a sustainable society.
‒ To improve QOL.
‒ To minimize environmental impact.
‒ To promote innovation.
‒ To improve disaster management.
‒ …
 Inclusion
‒ To Respect diversity in civilization, culture, and people.
‒ To involve people in ICT on a global scale …
3.2 Functional requirements
1) Overall Functional aspects
From KDDI [FG-FN C02 Page 5] and ETRI [FG-FN C03 Page 2]
 Mobility of user terminal (including mobility control architecture) as a basic functional
level,
 high-speed communication almost same as fixed network,
 and large capacity for many users and devices
From ETRI [FG-FN C05 Page 6]
 Multiple/Heterogeneous/Simultaneous
 Scalability (# of experiments)
 Threat-Zero (Concerns addressed on this is a practical requirement)
 Diverse Wireless Subnet Support
 Domain Federation
 Inter-working with Today’s Network (e.g., IPv6, NGN(BcN), etc. – ISP Peering)
[Editor’s note] Both two above proposals should be merged.
-8FGFN OD-6
2) Requirements on network Functional aspects
From NTT [FG-FN C07 Page 9]
 Network is isolated/separated based on communication granularity.
‒ It makes the use of given bandwidth maximize.
‒ It is operational or governable in optimal way.
 Virtual layered structure
‒ Each layer corresponds to an application specific networking.
‒ Various applications can be implemented and deployed effectively.
‒ A sort of isolation helps keeping application’s secure level.
 Network Operation/Customer support based on user contexts
‒ Precise observation and estimation of communication status is done at the end-points
and it is recognized as “Context”.
‒ Intelligent control/support is provided according to the context of customer usage.
3) Requirements on service aspects
From NTT [FG-FN C07 Page 11 and 12]
 HBS (Huge Band Service): Transparency, ultra wide bandwidth, low latency …
 BPS (Broadband Packet Service): Packet-based network which aggregates wide variety of
services.
 TMS (Tiny-band Mass Service): Service platform for data sensing and mining of real-world
and machine-to-machine communication.
Huge
Number of
networked
terminals
Small
New Service
Domains
(Categories)
TMS
RFID Tags
Sensors
Actuators
etc.
Digitization of
various events in
the real world.
Narrow
BPS
Interactive Video
Communication,
Circulation of CGM, CloudComputing etc.
Current network services
(VoIP, Web, P2P etc.)
HBS
Huge Data Center, High quality
communication with realistic
sensation, CDN etc.
Communication
Bandwidth
Fig. 3-2 High level view of new services domains
Wide
-9FGFN OD-6
Table 3-1 Network features to support services
Network for a service
Features of Network
WTN (Wide Transparent
Network) for HBS
 Huge and Fat pipe
VLN (Virtualized Logical
Network) for BPS
 Virtual network layer
 Not only in Core or Backbone, end-to-end Huge pipe are
requested.
 It aggregates various service traffics effectively.
 Mapped to appropriate λ-path on transport network
TPN (Transaction Processing
Network) for TMS
 Handling transaction/event processing
AAN (Adaptive Access
Network)
 User can choice access method suitable for the service
application.
 Gathering, storing, abstracting if needed
 Wide variety of access method such as wired and wireless can
be selected.
4) Requirements on cost transparency aspects from BT [FG-FN C11 Page 15]
 separation of service & network: fine industry goal, but idealistic if networks cannot even
know their costs
 numerous deep preconceptions to discard
‒ flow rate equality / TCP friendliness badly shares network resources
‒ volume represents cost
‒ humans want known bit-rate
 the elusive problem: traffic cost designed to only be handled by end-points (transport layer)
 solution: reinsert cost information into network layer = re-feedback
 once resource sharing fixed properly at the neck of the hourglass
‒ over-restrictive lower layer controls can be removed
‒ opens new space for service innovation
3.3 Requirements on specific aspects
1) Requirements on Core Networks [FG-FN C02 Page 8]
 Minimized functions of core network by moving mobility function to access network
 Permission to directly exchange some contents within access network
 Access network based mobility and security (transparent to AT)
 No degradation of security and quality level
- 10 FGFN OD-6
MM
AAA
Core
AGW
Access
AS
AP+ AP+
MM MM
AGW
Access
AS
AP+
MM
AP+
MM
AGW
Access
AP+
MM
AS
AP+
MM
Fig. 3-3 Core networks with minimum functions
2) Requirements for Autonomic management [FG-FN C23R1 Page 14 and 15]
 Embeded (In) Network functions: The entire management functionality should be imbedded
in the network.
 Aware and Self-aware functions: It monitors the network and operational context as well as
internal operational network state in order to assess if the network current behaviour serve
its service purposes.
 Adaptive and Self-adaptive functions: It triggers changes in network operations (state,
configurations, functions) function of the changes in network context.
 Automatic self-functions: It enables self-control (i.e. self-FCAPS, -*) of its internal network
operations, functions and state. It also bootstraps itself and it operates without manual
external intervention. Only manual/external input is the setting-up of the goal(s).
 Extensibility functions: It adds new functions without disturbing the rest of the system
(Plug_and_Play/Unplug_and_Play/ Dynamic programmability of management functions &
services)
 Outlay functions: Minimize life-cycle network operations’ costs and minimize energy
footprint.
Service Enablers /Service Plane
Orchestration Systems /Orchestration Plane
Management Systems /Management Plane
Information Systems /Knowledge Plane
Domain A
Virtual Networks / Virtualisation Plane
Networking Resources
Fig. 3-4 Autonomic Management Framework
- 11 FGFN OD-6
4. Architectures
[Editor’s Note] Following “Architectural information” is introduced in input contributions.
Contributions are invited to further enhancement.
4.1 High Level Model
1) High Level Vertical view of Future Networks from KDDI [GF-FN C-08 Page 3]
 Providing overlay infrastructures independent on underlay infrastructures
 Providing various service classes and functions for each overlay
 Establishing large scale infrastructure across multiple domains
Fig. 4-1 High level view of Future Networks
2) Layer restructuring aspects from China [FG-FN C22R1 Page 25]
China introduced the structure of each network architecture can be divided into two basic layers,
one is service layer and the other is network layer. And it proposes a new two-layer architecture
model, that is, “service layer” and “switching and routing layer.”
Fig. 4-2 Layer restructuring of Future Networks
- 12 FGFN OD-6
[Editor’s note] It is requested to identify difference of this model with NGN architecture model
called “transport stratum” and “Service Stratum.”
3) Design principles for Future Networks from Trilogy [by e-mail input at 2 July 2009]
[Editor’s note] Following texts are proposed by the e-mail as Trilogy input during the drafting
period and therefore need discussion.
 Information exposure: The data (or transaction) that uses up scarce networking resources,
through being sent (or acted on) should integrate control information (e.g. a metric) that
reflects its resource usage in ‘real time’. The control information should provide sufficient
information about resource usage to support an efficient and accountable allocation of
resources. The control information may be used as a variable in a pricing structure.
 Separation between policy and mechanism: Allow a network entity local choice according
to its priorities (policy). Have a common protocol or method through which the policies
interact to determine how networking resources are shared. Constrain conflicting policies
via the Information Exposure Design Principle.
 Fuzzy end-to-end principle: Allow the endpoint to explicitly delegate some functions into
the network, so the end is effectively a distributed system. This may imply some state in the
network, which should be “soft and hinty”.
 Resource pooling: Allow sufficient pooling of resources to be effective. Ensure that the
resource pooling mechanisms don’t conflict with each other.
4.2 Configuration Model of Future Networks
1) Overall configuration model of Future Networks with key features from NTT [FG-FN C07 Page
13 and 14]
TPN :
Transaction Processing Network
TMS
BPS
VLN :
Virtualized Logical Network (Layer)
HBS
HPC
WTN : Wide Transparent Network
AAN :
Adaptive Access Network
Fig. 4-3 Rough Sketch of Future Networks [FG-FN C07 Page 13]
Key characteristics of Future networks
- 13 FGFN OD-6
2) Overall functional configuration model from MANA [FG-FN C01]
Fig. 4-4 Overall Functional model from MANA [FG-FN C01 Page 6]
The general capabilities are applicable to all layers the Architectural Model as illustrated in Figure
4-4. They include [FG-FN C01 Page 7]:
 Availability of services – anywhere anytime seamless migration all according to SLA and
high level objectives.
 Connectivity anywhere and anytime, meaning the possibility to connect everywhere.
- 14 FGFN OD-6
 Manageability anywhere and anytime with an increase level of self-management - as the
networked systems become more and more complex this is a necessity as well as an enabler
for evolution.
 Mobility anywhere and anytime.
 Adaptability everywhere to changes in context and environment.
 Dependability, resiliency, and survivability to withstand threats and (D)DOS.
 Robustness and stability, including support for mission critical applications.
 Accountability anywhere and anytime - to ensure the possibility of tracking actions
performed by a user or a management agent that might impact the networked systems and
their performance.
 Evolvability as an inherent feature to ensure the possibility to evolve the networking
systems in a smooth way without major disruptions.
 Scalability with respect to features and functions, as well as complexity.
 Trust and security ensuring that users make use of the networks and services in a secure
environment.
 Multi-domains to allow for different administrations, technologies, and parallel or federated
Internets.
 Support of heterogeneity for possible technology optimization.
 Openness towards application and services enabling the Internet Openness.
 Energy efficiency of the systems architectures, protocols, and radio spectrum; the use of the
networked systems for control of energy consumption.
Fig. 4-5 Overall capabilities based on MANA model [FG-FN C01 Page 16]
- 15 FGFN OD-6
4.3 Virtualization aspects of Future Networks Architecture
1) Virtualization aspects of Future Networks from ETRI with [FG-FN C05 Page 4]
Fig. 4-6 Future Networks with Network Virtualization
2) Server Virtualization from ETRI [FG-FN C12 Page 12]
Server virtualization is the ability to run an entire VM with its own (guest) OS on another OS or on
a bare-machine with following features:

Allows multiple VMs, with heterogeneous guest OSes to run in isolation, side-by-side on the
same physical machine

Each VM has its own set of virtual H/W upon which a guest OS and guest applications are
loaded

The guest OS sees a consistent, normalized set of H/W regardless of the actual physical H/W
components
VM
Guest
App.
VM
Guest
App.
Guest OS
Guest OS
Guest OS
Virtual H/W
Virtual H/W
Virtualization Layer
Virtual H/W
VM
Non-privileged Modes Virtualization Layer
Privileged Modes
Host OS
H/W
H/W
Fig. 4-7 Architecture model of Server virtualization
3) Network virtualization from ETRI [FG-FN C12 Page 14] with following benefits:
 Partitioning network into multiple sub-networks
- 16 FGFN OD-6
 Used within a single domain or across multiple, independently managed domains
 Increasing application performance by dynamically maximizing network asset utilization
while reducing operational requirements
Fig. 4-8 Architecture model of Network virtualization
4) Functional model of Virtualization Layer from Autonomic Internet Project [FG-FN C23 Page 17]
vCPI (Virtual Component Programming Interf ace)
•
Start / Stop / Modif y virtual network
•
Provide monitoring values
•
Cooked values
•
Abstraction f rom virtualisation solution
vSPI (Virtualisation System Programmability Interf ace)
• Overall management via Autonomous Management
Systems (AMS)
Fig. 4-9 Functional model of virtualization layer
5) Expansion aspects of Virtualization from AKARI [FG-FN C14 Page 11]
Virtualization would be expanded with following aspect.
- 17 FGFN OD-6
Fig. 4-9 Expansion model of Virtualization
4.4 Autonomic network aspects of Future Networks Architecture
1) Autonomic Networking Architecture from ANA [FG-FN C016R1 Page 8 and 22]
ANA is a meta-architecture to host, interconnect and federate multiple heterogeneous networks
Fig. 4-10 ANA Framework in Future Networks
2) Autonomic network management architecture from Autonomic Internet Project [FG-FN C23
Page 16]
- 18 FGFN OD-6
Inter-System View
Service Enablers Plane
Service
Lifecycle
Management
Business Goals
Customer Needs
…
Developer Interface
Operator Interface
…
User Interf ace Services
Lif ecycle Management Services
Others
Federation
Distribution
Mapping
WP3 (D3.)
Negotiation
Federation Services
Orchestra
tion
Orchestra
Modules
tion
Mapping
Plane
Intra-System View
Distributed
Orchestration
Component
…
vSPI
vCPI vCPI
vCPI
…
End-User
Virtualised
Services
End-User
Composite
Virtualised
Services
Virtualisati
on
Plane
vCPI vCPI
Compon
ent
16
Physical
Resource
Fig. 4-11 Overall Autonomic Management Architecture
InNetwork-Management Space Resources
Control
ControlAlgorithms
Algorithms
OrchestationPlane(WP2)
Plane
Knowledge
InformationModels
InformationModels
&Ontologies
Ontologies
Knowledge Plane
Knowledge
Policy-Based
-Based
Policy
Management
Management
Knowledge
Knowledge
ManagementPlane(WP4)
Plane
SelfManagement
Knowledge
Virtual Networks: Resource
Knowledge
Virtualisation
Knowledge
Knowledge
Internet
Internet
Knowledge
Network Space
Programmable
Resources
Networks
IPNetworks
UMTSNetworks
Others
WirelessNetworks
SensorNetworks
4
Fig. 4-12 Overall configuration model of Autonomic Control Overlay [FG-FN C23 Page 4]
- 19 FGFN OD-6
4.5 Specific aspects of Future Networks Architecture
1) Future networks with minimum core network function from KDDI [FG-FN C02 Page 10]
Following architecture model has been proposed conjunction with relevant requirements in clause
3.3 1).
Registrar/MM
Minimum
Core
AS
AAA
AS
Distributed resource allocation function based on
estimated connection quality in overlay network
Overlay
Signaling
Network
Secure connection within transport and access network
without transferring to the core network
AS
Access/
Transport
Network
BS+MM+AS
Access
Terminal
Part II: Service control in
coordination with core
network and distributed
access overlay network
AS
BS+MM+AS
BS+MM+AS
Mobility support at base station level for less
functionality of access terminal
Part I: Route optimization
of application data
Part III: Access network
based mobility and
transparent security
MM: Mobility Management, AAA: Authentication, Authorization, and Accounting,
AS: Application Server, BS: Base Station
Fig. 4-13 Architecture model with minimum core concept
2) Resilient Network Architecture from ResumeNet project [FG-FN C17R1 Page 13]
- 20 FGFN OD-6
Fig. 4-14 Resilient Network Architecture of Future Networks
This contribution also introduces resilience strategy as following two phases:
Phase 1: Real-Time Control Loop –D2R2
 Defend against challenges and threats to normal operation.
‒ reduce the probability of a fault leading to a failure
‒ reduce the impact of a adverse event or condition
 Detect when an adverse event or condition has occurred.
‒ Determine when defences have failed and remediation needs to occur
 Remediate the effects of the adverse event to minimize the impact.
‒ The goal is to do the best possible at all levels after an adverse eventand during an
adverse condition.
‒ Corrective action must be taken at all levels to minimize the impact of service failure,
including correct operation with graceful degradation of performance.
 Recover to original and normal operations
‒
Once an adverse event has ended or an adverse condition is removed
Phase 2: Background Operations –DR
 Diagnose the fault that was the root cause of an error or failure
‒ While it is not possible to directly detect faults, a system detects symptoms
‒ derive an improved system design
‒ recover to a better state
 Refine system behavior for the future based on past D2R2cycles.
‒ learn and reflect on how the system has defended, detected, remediated, and recovered
‒ continuously increase the resilience of the network.
3) Architecture for cooperation and coding framework from 4WARD [FG-FN C19R1 Page 4 and 5]
 One Cooperation/Coding Facility (CF) per node: Provides runtime environment for actual
operations
- 21 FGFN OD-6
 Interaction with ISO/OSI stack and layer-less architectures
 Arbitrary number of Modules per CF: Libraries which contain technique-specific
functionality
‒ Monitoring
‒
Traffic transformation
Fig. 4-15 Cooperation and coding framework of Future Networks
- 22 FGFN OD-6
Appendix
Status of Standard Activities
This appendix contains status of standard activities related to internet which are useful to identify
the status of current development of standards in specific technology areas. Contents have been
copied from a contribution [FG-FN C22R1 on Pages 20, 21 and 22].
1. Status of Mobile Internet related activities
- 23 FGFN OD-6
2. Status of Multicast Technology activities
3. Status of Internet security technology activities
____________