Anonymous and Privacy-Sensitive Collection of Sensed Data in Location-Based Applications Presenter: Jen Chen
Outline <ul><li>Introduction </li></ul><ul><li>Use hitchhiking </li></ul><ul><li>Discussion </li></ul><ul><li>Conclusion <...
Introduction <ul><li>Use ZipDash  approach  http://www .google .com /gmm /index.html </li></ul><ul><li>Use  hitchhiking  h...
Use  Hitchhiking <ul><li>The Hitchhiking Approach </li></ul><ul><li>Hitchhiking approach has seven requirements </li></ul>
The Hitchhiking Approach <ul><li>Existing commodity devices, including notebook and mobile-phones. </li></ul><ul><li>Use G...
S even requirements <ul><li>Location is computed on the client. </li></ul><ul><li>Only the client device is trusted. </li>...
S even requirements  (continue) <ul><li>Location identifiers are based in the physical location. </li></ul><ul><li>Locatio...
Location is computed on the client <ul><li>Client use GPS </li></ul><ul><li>Server only know  device’s location </li></ul>
Only the client device is trusted <ul><li>Design Client is easy </li></ul><ul><li>Server must  higher standard </li></ul>
Each person must approve reporting from a location. <ul><li>No  approve reporting, No application </li></ul><ul><li>Applic...
Physical constraints prevent location spoofing <ul><li>Request location must be  approved </li></ul><ul><li>Malicious serv...
Location identifiers are based in the physical location. <ul><li>ID and GPS (or WiFi  access points ) identify together </...
Location identifiers are generated by the client <ul><li>Use GPS to provide location identifier </li></ul><ul><li>Server o...
Sensed identifiers are not reported to a server . <ul><li>No report the sensed identifier </li></ul><ul><li>Malicious oper...
Discussion <ul><li>What is hot </li></ul><ul><li>Share location is currently busy </li></ul><ul><li>Letting others join th...
Conclusion <ul><li>Danger and convenience is contradictory </li></ul><ul><li>Make laws to protect  privacy </li></ul>
Upcoming SlideShare
Loading in …5
×

Anonymous and Privacy-Sensitive Collection of Sensed Data in Location-Based Applications

728 views
651 views

Published on

Location application

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
728
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Anonymous and Privacy-Sensitive Collection of Sensed Data in Location-Based Applications

  1. 1. Anonymous and Privacy-Sensitive Collection of Sensed Data in Location-Based Applications Presenter: Jen Chen
  2. 2. Outline <ul><li>Introduction </li></ul><ul><li>Use hitchhiking </li></ul><ul><li>Discussion </li></ul><ul><li>Conclusion </li></ul>
  3. 3. Introduction <ul><li>Use ZipDash approach http://www .google .com /gmm /index.html </li></ul><ul><li>Use hitchhiking http://labs .google .com /ridefinder </li></ul><ul><li>Hitchhiking danger </li></ul>
  4. 4. Use Hitchhiking <ul><li>The Hitchhiking Approach </li></ul><ul><li>Hitchhiking approach has seven requirements </li></ul>
  5. 5. The Hitchhiking Approach <ul><li>Existing commodity devices, including notebook and mobile-phones. </li></ul><ul><li>Use GPS </li></ul><ul><li>Application: Traffic flow model </li></ul>
  6. 6. S even requirements <ul><li>Location is computed on the client. </li></ul><ul><li>Only the client device is trusted. </li></ul><ul><li>Each person must approve reporting from a location. </li></ul><ul><li>Physical constraints prevent location spoofing. </li></ul>
  7. 7. S even requirements (continue) <ul><li>Location identifiers are based in the physical location. </li></ul><ul><li>Location identifiers are generated by the client . </li></ul><ul><li>Sensed identifiers are not reported to a server . </li></ul>
  8. 8. Location is computed on the client <ul><li>Client use GPS </li></ul><ul><li>Server only know device’s location </li></ul>
  9. 9. Only the client device is trusted <ul><li>Design Client is easy </li></ul><ul><li>Server must higher standard </li></ul>
  10. 10. Each person must approve reporting from a location. <ul><li>No approve reporting, No application </li></ul><ul><li>Applications can’t reveal identity </li></ul>
  11. 11. Physical constraints prevent location spoofing <ul><li>Request location must be approved </li></ul><ul><li>Malicious server may be request the sensitive location. </li></ul>YES or NO
  12. 12. Location identifiers are based in the physical location. <ul><li>ID and GPS (or WiFi access points ) identify together </li></ul><ul><li>If only use the ID, it may be danger </li></ul>
  13. 13. Location identifiers are generated by the client <ul><li>Use GPS to provide location identifier </li></ul><ul><li>Server only provide state about location of interest </li></ul>
  14. 14. Sensed identifiers are not reported to a server . <ul><li>No report the sensed identifier </li></ul><ul><li>Malicious operator may be track by sensed identifiers </li></ul>
  15. 15. Discussion <ul><li>What is hot </li></ul><ul><li>Share location is currently busy </li></ul><ul><li>Letting others join the party </li></ul>
  16. 16. Conclusion <ul><li>Danger and convenience is contradictory </li></ul><ul><li>Make laws to protect privacy </li></ul>

×