Project

General

Profile

Actions

Feature #3800

closed

autoconfig: geolocation-based router selection

Added by Junxiao Shi about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Tools
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
12.00 h

Description

Introduce a geolocation-based router selection step to ndn-autoconfig.

NDN-FCH is a geolocation service for automatic NDN network attachment.
It allows an end host to find the geographically nearest NDN testbed router through an Interest-Data query using the end host's IP address or GPS coordinates.

NDN-FCH was initially designed by Gregory Liu as a class project at UCLA CS217B.

The issue includes:

  • Have a concrete definition of NDN-FCH protocol.
  • Implement an NDN-FCH client inside ndn-autoconfig program. After an initial testbed connection is made, the NDN-FCH client is invoked to find a potentially closer router and connect to it.
Actions #1

Updated by Junxiao Shi about 8 years ago

  • Assignee set to Gregory Liu
Actions #2

Updated by Alex Afanasyev about 8 years ago

There are a few new thoughts on this feature. Specifically, simplification of the protocol stages. Overall, I see the following pieces

  1. The server part (required only IP connectivity, e.g., somewhere in the cloud)

1.1. Mapping database from IP addresses to locations
1.2. Mapping database from locations to "closest" NDN hubs
1.3. UDP/TCP/or HTTP interface (I would vote for HTTP) to request "closest" NDN hub: (version 1) with empty request to infer location from source IP; (version 2) with explicit coordinates in request to use the specified location directly.

  1. The client part

2.1. ("Desktop") Extension of ndn-autoconfig tool to run UDP/TCP/or HTTP interface to get closest hub
2.2. NFD-Android extension to run the protocol, supplying GPS coordinates

The protocol could be very simple like this

 client                                    well known hostname of cloud based geo service
   |                                              (e.g., http://geohub.named-data.net)
   |      (a) GET /localhop/ndn-autoconf/hub HTTP/1.0           |
   | -------------------------------------------------------->  |
   |                                                            |
   |      (b) GET /localhop/ndn-autoconf/hub?                   |
   |               lon=34.0644371&lat=-118.4505164 HTTP/1.0     |
   | -------------------------------------------------------->  |
   |                                                            |
   |                                                            |
   |                                                           ...
   |                                                            |
   |      HTTP 200    "udp://spurs.cs.ucla.edu:6363"            |
   | <--------------------------------------------------------  |
   |                                                            |
Actions #3

Updated by Alex Afanasyev almost 8 years ago

  • Assignee deleted (Gregory Liu)
  • % Done changed from 0 to 50

The server part has been completed and deployed into operation at http://ndn-fch.named-data.net

The source code is currently at https://github.com/cawka/ndn-fch and the protocol description in the README.md file

Actions #4

Updated by Alex Afanasyev almost 8 years ago

  • Assignee set to Alex Afanasyev

I will implement addition to ndn-autoconfig app to request hub information from ndn-fch, adding it just before the current 3rd step.

Actions #5

Updated by Alex Afanasyev almost 8 years ago

  • Status changed from New to Code review
  • % Done changed from 50 to 90
Actions #6

Updated by Alex Afanasyev almost 8 years ago

  • Status changed from Code review to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF