Page 275 - ITU-T Focus Group IMT-2020 Deliverables

ITU-T Focus Group IMT-2020 Deliverables 4

using OpenStack (OS) and ONOS. Both these frameworks have been adapted to an ICN/CCN context. OS is
used to manage ICN Service Function (VMs executing specific in-network service logic), provisioning them on
demand by respective service controller over any VSERs. ONOS is extended to execute multiple ICN
controllers to manage foundational functions such as managing the virtual topology as viewed by
applications, proxy the signalling from the ICN forwarders and de-multiplexing to appropriate service
controllers for further actions and provisioning the FIB rules as required by application controllers.

7 IP Services over ICN (InterDigital)
In this PoC, we aim at a solution for delivering IP-based services over an ICN-based routing solution within a
single operator or across collaborating operators at higher efficiency and lower latency than possible in
today’s solutions. With this PoC, we provide a possible migration approach for the introduction of ICN,
enabling full backward compatibility of IP-based services, applications and user equipment, while also
offering the qualitative and quantitative performance advantages of ICN. Specifically, our solution enables
the multicast delivery of HTTP request responses in scenarios such as those of personalized viewing of video
content. Furthermore, we also enable the reduction of experienced latency through the flexible placement
as well as quick activation of surrogate HTTP servers within the network and closer to the end user. Our
solution does not rely on DNS-based methods, overcoming the inherent limitations of DNS-based indirection
in terms of scalability, dynamicity and operational assurance, while piggybacking on the proliferation and
deployment of SDN-based transport networks.
In our specific PoC example, we will showcase the easy integration of ICN networks with existing HTTP based
applications and demonstrate multicast gain in a personalized video scenario, which includes on-site human
users as well as emulated users in a remote data center.
The work was done in conjunction with the EU H2020 projects POINT and RIFE.

This PoC specifically addresses the following gaps identified by the Focus Group:
• Gap E.1 Considering ICN as a protocol for IMT-2020: Our solution is based on a native ICN solution
that directly and efficiently integrates with SDN without any extensions needed to current OpenFlow
specifications (1.2+). As such, it provides the capability for future native ICN applications. In addition,
however, our solution provides a strong migration path for IP-based services, enabling any IP-based
service and application to run on our network as well as connecting standard IP-based user
equipment to the attachment points of our solution, while utilising the multicast and information
routing capabilities of ICN to quantitatively improve on network utilization and latency.
• Gap E.8 ICN mobility and routing: Our solution provides an answer to mobility and flexible routing
in that direct path routing is provided, based on handover triggers delivered to the PCE, and
path/server resilience

• Gap E.12 SDN & Openflow: Our solution uses SDN to control the ICN underlay to transport IP
services. As described above, we do not require any modifications to OpenFlow 1.2 or later.
• Gap E.13 ICN Security: Our solution provides the ability to securely route HTTP service requests to
authorized servers, therefore preventing data leakage often occurring in CDN-based redirections.
Furthermore, our solution supports secure HTTP through providing an HTTPS interception proxy at
the ingress and egress NAP (or GW), requiring a certificate sharing agreement between operator
and content providers. Note however that this security improvement is complementary to the main
idea of the PoC which is to use HTTP on top of ICN.

7.1 InterDigital ICN solution within the IMT-2020 network

7.1.1 ICN over SDN
Within (Trossen and Parisis 2012) individual information items are identified by names or statistically unique
fixed size labels which in themselves hold no meaning. Multiple information items can be placed in a scope
which is also named in the same manner and can be nested within other scopes thus creating graphs of
information which allow computations leading to specific information elements.

269