Location Aware Social Network
Group 2
CS 8803
Team Introduction
Prasun Johari
M.S. ECE
Ankur Aggarwal
M.S. CS
Gurlal Kahlon
M.S. CS
Shobith Alva
M.S. CS
Outline
1. High Level Description
2. IP Multimedia Subsystem
3. Google Android
4. Conclusions
3
High Level Description
4
High Level Description
Facilitate sharing of experiences, ideas, thoughts
etc. among people
5
High Level Description
But to share experiences or ideas with someone
you need to have a common interest
Location
6
High Level Description
Location – Aware Social Networking System
1. Dynamic groups - location and interests
2. Static groups - interests
3. Facilitate communication among members
7
Dynamic Groups
User 4
User 1
User
2
User
3
High Level Description
Dynamic Advertisement Technology
4. Self-adaptive Advertisement System based on
the current location of a user
5. Location aware search
6. Revenue generation by Pay-per-potential Sale
7. Surveys – Feedback to advertisers
9
High Level Description
How do we actually make this happen on a cell
phone ?
1. IMS
2. Google Android
IP Multimedia Subsystem
The IP Multimedia Subsystem (IMS) is an
architectural framework for delivering Internet
Protocol (IP) multimedia to mobile users.
Source: Wikipedia
Framework ?

IMS Network Architecture
12
Use Cases
13
Use Cases
Communication with colleagues in a class room
14
Use Cases
This use-case would demonstrate how our
system could function as a dynamic “spatialforum” for requesting guidance
15
Use Cases – Step 1 / 8

User logs into our
service
16
Use Cases – Step 1 / 8


Registration
The SIP Protocol
is used to
perform
registration
17
Use Cases – Step 2 / 8


User's location
from WhereAmI
/ GPS
It locates
neighboring
users and ads
18
Use Cases – Step 2 / 8


Location information
from WhereAmI
This is submitted to
the location server
and a list of
neighboring users is
obtained
19
Use Cases – Step 2 / 8

Interactions between

The UE and WhereAmI Service
20
Use Cases – Step 3 / 8


The service makes
available to this user
a list of other users in
his vicinity
A dynamic group is
created
21
Use Cases – Step 3 / 8

Interactions between

The UE and Location Server
22
Use Cases – Step 3 / 8

The user
subscribes to
the presence
server to
obtain the
availability /
presence of
other users
23
Use Cases – Step 4 / 8

The user can now communicate with those
around him
24
Application Features
25
Application Features
26
Application Features
27
Application Features
28
Application Features
29
Application Features
30
Application Features
31
Strategy ?
Socially Noble
Commercially
Viable
32
Use Cases
33
Use Cases – Step 5 / 8

Pay-per-Potential Sale
34
Use Cases – Step 6 / 8

Pay-per-Potential Sale
35
Use Cases – Step 7 / 8

Pay-per-Potential Sale
36
Use Cases – Step 8 / 8

Pay-per-Potential Sale
37
How do we charge the
advertisers ?

Fixed rate ?

Hourly rate ?

Wouldn't it make more sense to charge the
advertisers based on the number of customers
that our system directed to them ?

Pay-per-Potential Sale
Google Android
Android Platform

Android is a software stack for mobile devices
that includes an operating system, middleware
and key applications.




Application framework
Dalvik virtual machine
Integrated browser, Media support, Optimized
Graphics, SQLite,
Android relies on Linux version 2.6 for core
system services such as security, memory
management, process management, network
stack, and driver model.
Android Implementation


Our robust design easily leveraged the facilities
provided by Google's Android.
Android provides excellent integration with
Google's location based and map services.



Location Providers – whereami, gps (mock, for
now) etc...
Map Controller, Overlay Controller
Implementation of our service is in the form of
an overlay on the base map service.
Android Advantage



Focussed on the Developer, lots of
documentation and a powerful, well structured
API.
Very good integration with web-services
(although not complete), including Google's
own.
Android is based on several open-source
technologies.
Challenges
1. Figuring out IMS
2. Power v/s Frequency of querying WhereAmI
3. Bandwidth for maps
Conclusions