LINS : Localized Information Navigation System
Zane Starr (zcs), GeetaShroff (gshroff), Brian Loo (bloo), Priya Narasimhan (priya)
Carnegie Mellon University, Pittsburgh, PA
http://www.ece.cmu.edu/~ece549/spring07/team9/index.html
What is LINS?
LINS Architecture
LINS: Localized Information Navigation System
Indoor navigation system that uses localized contextual information to dynamically
adapt to individual user needs
Motivation:
Many situations exist where context is critical to the user’s successful or timely
arrival
Admin-side Application:
Admin GUI:
Creates Map
Path
finding:
Context
aware
Database:
Stores i-Map
Goals:
Improve quality of indoor navigation systems
Contribute to the field of accessibility research
Provide a platform for collaborative for local
information sharing
Map planning
i-Node placement
Provides initial context
i-Map storage
LINS
i-Node
Interpreter:
Reads
i-Node
i-Node:
Unique
Identifier
Applications:
Navigation of the blind
Emergency responders
Physically challenged
Guided grocery shopping
Self-guided tours
User GUI:
Navigates
User
User-side Application:
i-Map retrieval
Contextual path planning
Allows for user preferences
Allows for information sharing
An Implementation of LINS
What is an i-Node?
Admin-side features
An information node (i-Node) is any device
or item that can provide a unique
identification number to the user’s mobile
device
Persistent storage of
multimedia context for
i-Node
User-side features:
Add multimedia content to
i-Node
Voice navigation prompts
Easy to use graphical
interface
Bluetooth
Access
Point
802.15.4B
Firefly
module
UPC
Barcode
Passive
RFID Tag
Active
RFID Tag
Scalable in size of
deployment area
Small memory footprint
Demo of admin side application
Demo of user side
application on PDA
LINS
i-Nodes
Our Implementation
Passive RFID tags
Implementation features
Low-cost
i-Node Interpreter
RFID Reader
Light-weight
User device
PDA
Small form factor
Demonstrating the reading of an i-Node labeled as a fire alarm
Hardware used in our implementation
Context = Localized + Personal Information
Results & Future Work
Where does context come from?
How is context used?
Conclusion:
Admin provides initial context:
Example: Admin adds gender label to
relevant information nodes (restroom).
User provides preferences:
Example: User selects gender preference
User preference
creates context-based
heuristic or cost
function
Examples: Shortest
path, accessibilitycentric, etc.
Using localized information to
provide context for our indoor
navigation provides better
quality paths to the user.
Future Work:
How does context fit into
path planning?
A* path planning
algorithm dynamically
adapts to user preference
heuristics and cost
functions
We look forward to improving
the localized information
framework to enhance the
current implementation to
incorporate richer multimedia
for a better experience.
In the above scenario, the wheel chair accessibility preference
was selected. The shortest accessible route was then
generated as the navigable path.
This path is longer than the normal shortest path.