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

4 ITU-T Focus Group IMT-2020 Deliverables

10.1.2 Mobility Solution

The mobility solution implemented to aid seamless producer mobility in ICN/CCN for this demo is described
in (Azgin, Ravindran and Wang 2016). Though the mobility handled by the VSERs are handled in an IP overlay
manner, with appropriate control plane support, an ICN application’s producer mobility can be handled in
the ICN layer, without underlay mobility support. The efficiency of such overlay mobility depends on the
specific approach applied to re-connect UE to the new point-of-attachment (PoA) after handoff, and the cross
layer communication efficiency between the ICN and L2/L3 when a handoff is triggered and specific ICN layer
mobility strategy. We apply a “make-before-break” network-based mobility approach where the IP network
binding of the new PoA is provided to the UE before the handoff. This is based on the current practice of UE
providing the candidate list of base stations based on the signal quality perceived from its current location.

For seamless mobility, late binding approach (Azgin, Ravindran and Wang, Scalable Mobility-Centric
Architecture for Named data Networking 2014) is applied using forwarding label insertion (Ravindran,
Chakraborti and Azgin, Forwarding Label Support in CCN Protocol 2016) in the CCN Interest as a result of
name resolution applied at the ingress PoA which swapped at the producer end PoA with a new forwarding
label, if required, thus achieving seamless mobility. Through this PoC we also demonstrate the feasibility of
a mobility-as-a-service realization (Azgin, Ravindran and Wang, Seamless Mobility as a Service in Information
Centric Networks 2016) where any application can request the ICN mobility control plane to handle mobility
for a name prefix. As a result, all the flows under that name will be provided seamless mobility support.
Further mobility service controller itself is service aware, by managing multiple service profiles and managing
the service names for which mobility has been requested for each profile.
The prototype is developed to show the feature of realizing mobility as a service. Here any application can
request mobility to flows under its name prefix by requesting an agent function in the UE to register it for
mobility service offered by the network. The network then creates appropriate mobility state in the VSER
nodes and the mobility controller to handle the Interest flows with appropriate mobility support.

10.1.3 A/V Application Design
The architecture of the A/V conferencing service is described in (Ravindran, Liu, et al. 2013) (Jangam,
Ravindran and al. 2015). At a high level, the applications implements a producer capturing real-time audio
and video from the video cam and the audio source, encoding and then publishing them as content objects
in the application cache. Considering stringent end-to-end audio and video latency requirements of
100-150 ms and 200-300 ms respectively, the consumers express pre-fetched Interests stored in the
application cache of the producer application. These Interests are satisfied as soon as the content is
generated, and when the content arrives at the consumer, it expresses more Interest for the preset pre-fetch
duration. In addition, the service functions aiding the conferencing application helps with random participant
join and leave, by actively pushing notifications of the producer state in a periodic manner.
10.1.4 POC Workflow and Initial Results

• Figure 18, shows the demo setup. For the demo we use 3 VSER, 1 CCN relay node and 3 participants,
along with the OpenStack/ONOS controllers and Web GUI for Service provisioning and
Management.
• Service Manager’s Browser GUI is used to provision the video conferencing service
– The requirements are provided in the form of number of participants, sites etc.

– This will result in provisioning the Conf. Service VMs on the VSERs.
– It will also program the CCN FIBs for service level connectivity between the VMs.
• The mobility control plane is also provisioned through the OpenStack. This provisions the mobility
service agents in the VSER to aid with name resolution.
• The participants then discover the provisioned conferences in the network.

276