Crowd Steering: Music Festival Case Study


Published on

Case study presentation by Jose Luis Fernandez-Marquez @ AWASS 2012

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Crowd Steering: Music Festival Case Study

  1. 1. Crowd Steering:Music Festival Case Study Jose Luis Fernandez-Marquez University of Geneva, Switzerland 1
  2. 2. Outline  Motivation – Opportunistic networks  SAPERE project  Music Festival   Description   Requirements  What are we expecting from you?  What should you think about? 2
  3. 3. Motivation   Traffic control   Alerts about accidents or dangers on the road (e.g. ice, or oil)   Cars navigators using context information. (e.g avg. speed of cars)   Virtual tourist guide   Avoid very crowded streets   Receive information about event that are happening close to you   Cinema, theather, etc..   Taxi booking service 3
  4. 4. Motivation   Characterized by:   Large Scale   Openness   Unpredictability   Requirements:   Scalability   Robustness   Adaptability   Context-aware 4
  5. 5. SAPERE project   Theoretical and practical framework for decentralized development and execution of self-aware and adaptive services for future and emerging pervasive network scenarios.   Chemical Interactions among Services   Smooth data/service distinction   Spontaneous interactions of available services   Bio-chemical reactions   Middleware for Android phones / tablets   Context-awareness (user, situation recognition)   Case Study   Focus on public/private displays for crowd steering   Domains   Context-Aware Advertisement, Crowd Steering, User guidance   EU Funded Project (SAPERE:É DES SCIENCES U Bologna, U Modena, U Linz, U St-Andrews   Collaboration: U Geneva,ÉCONOMIQUES ET SOCIALES   2010-2013Département des Hautes Etudes Commerciales -HEC
  6. 6. Music Festival  Features:   Current centralised solutions are not scalable:   It’s not possible to make calls, send messages, or have internet connection.   Mobile network overload.   High density of people, most of them bringing mobile phones or pdas.   Open spaces:   It makes easy the positioning (use of GPS) 6
  7. 7. App. Requirements  Crowd steering:   A user wants to find other users.   A user wants to find a point of interest.  Organisers want to publish events (without using centralised infrastructure):   Taxi or bus location   Music Festival Agenda   Emergency exits, toilets, bars, merchandising.   A bar owner wants to advert offers during the festival 7
  8. 8. App. Requirements  Social Network:   Add people to your social network   Sharing profiles, pictures   To know if people in your social network are in the music festival   A user wants to chat with other users (friends)   One to one, or one to n-users. 8
  9. 9. What are we expecting from you?  Designing the application:   Use of self-organising design patterns.   Contribution of each pattern.   Relationships between them.   Description of the entities participating in the system.   Description of the interactions between the entities. 9
  10. 10. What you should think about?  How does the information spread?   Analysis of the different spreading algorithms existing in the literature (e.g. probabilistic, position-based, counter-based)  Routing algorithms for opportunistic networks?   Are they required? When should they be used?  What are the current technologies that give support for this type of infrastructures?   Bluetooth, zigbee, wi-fi, direct wi-fi…etc.   Are they satisfying the current requirements of this type of applications?   Which one would be the best? 10
  11. 11. What you should think about?  What are the main challenges in the implementation?   Information collisions, network overload, Memory, CPU   How could these problems be overcome?  How can we simulate the application?   What is the goal of the simulation? Scalability, robustness, Feasibility? Validating the design?   Which are the existing tools that allow us to simulate this application. (Repast, one, ns2, …)  SASO workshops. Deadline: 4th July 11
  12. 12. Any questions?Thank you for your attention! Jose Luis Fernandez-Marquez 12