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

ITU-T Focus Group IMT-2020 Deliverables 4

The second aspect is that of the possibility to reduce service latency through the exposure of surrogate
service endpoints in a fast and flexible manner. This is enabled by the exposure of HTTP-based resources
through the FQDN of their providing servers. Through an authorative registration interface to the ICN routing
solution, our PoC can enable such surrogate endpoints within the network at speeds of less than 1s, therefore
enabling the service completion from a possibly closer endpoint than the one originally being chosen.
Examples for such surrogate functionality is that of choosing alternative HTTP-level streaming servers,
localizing video playout to the regions where these playout point serve clients rather than needing to retrieve
the content from a central server.

With respect to mobility, the path management of the PoC allows for recalculation of path information in the
case of mobility, e.g., triggered by a handover event. Through replication of the PCE (path computation
element) of our solution, the path computation can be regionalized, further reducing the delay for
recalculation. Nonetheless, in typical mobility scenarios, we observe similar signalling delays as for anchor
point approaches. However, our recalculation ensures direct path data transfer, leading to a reduction of
path stretch compared to anchor point approaches.
On the device-local link, there are no direct benefits of our solution, similar to many MEC solutions which
mainly focus on the access network rather than the access link per se.

7.4 Integration with IMT-2020 NWs

From the above it is clear that once SDN is integrated into IMT-2020, integrating our ICN solution is a simple
matter of interfacing the TM of our solution with a standard SDN controller, while relying on OpenFlow-
compliant proactive rule insertion as outlined above and in the annex. Other than an SDN capable network,
the network only requires NAP close to the clients and servers. While a ‘close’ deployment could be in
customer premise equipment, other suitable locations are natural aggregation points, such as a serving
gateway or a local GW (such as BRAS in fixed line networks) for the client and with a PDN gateway for the
server.
SDN is already under study for inclusion in IMT-2020 by many SDOs (incl. ITU-T SG-13).

7.5 Further study and possible standardization

The following areas will benefit from standardization:
– ICN is integrated over SDN through native operations of OpenFlow (1.3) switches over certain e.g.
IPV6 and or Ethernet MAC header fields. The specific fields and their location / significance will have
to be standardized.

– For the network access points:
• The hashing function performed over the (URL) domain names will need to be defined
• The trigger events which cause the sNAP to register a service
• Control signalling necessary to implement RV, TM & FN functions
– Namespaces or both HTTP and IP mapping
– Signalling to support path management with topology changes
– Signalling to support network mobility

– (optional) handling of HTTPS: agree of key management

271