1 / 23

Design and Implementation Issues for Explorative Location-based Applications: The NexusRallye

Design and Implementation Issues for Explorative Location-based Applications: The NexusRallye. Daniela Nicklas , Nicola Hönle, Michael Moltenbrey, Bernhard Mitschang GeoInfo 2004, 22. November 2004. Center of Excellence 627: Spatial World Models for Mobile Context-Aware Applications.

angie
Download Presentation

Design and Implementation Issues for Explorative Location-based Applications: The NexusRallye

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design and Implementation Issues for Explorative Location-based Applications:The NexusRallye Daniela Nicklas, Nicola Hönle, Michael Moltenbrey, Bernhard Mitschang GeoInfo 2004, 22. November 2004 Center of Excellence 627: Spatial World Models for Mobile Context-Aware Applications Universität Stuttgart, Germany

  2. Overview • Motivation • A task-oriented approach • Sample application: the NexusRallye • Requirements • Data Model • Context management: the Nexus platform • Platform architecture • Access patterns • Lessons learned

  3. Campus Universität Stuttgart, Germany Scenario

  4. cafeteria CS building library examinationoffice A freshmen at the University

  5. Welcome days for CS freshmen • First day: Guided tours • experienced students show the campus to the freshmen • explain the most important things for "survival" • welcome party • Second day: the Campus rally • morning: freshmen teams get sheets of paper with tasks, e.g.: • "How many steps are in the math building from first to eigth level?" • "What is the registration number of the examination on databases?" • "Who is Fabiola and what is she doing in the students lab?" • "Write a short poem on the food offered today in the cafeteria." • afternoon: teams return, jury assesses the answers • winner team gets prize, another party

  6. Features of the rally game • tasks get the players to move around • require location knowledge • require communication with people • reuse of tasks from last year, add new ones • general & specific tasks (university & computer science) • possible benefits of electronic version: • use of existing information spaces (maps, web sites, ...) • easy reuse of tasks • dependency of tasks • case study for location-based applications (research goal)

  7. question task action task ... multiple choice value free text find/goTo task bringTo task ... A task-oriented approach • what types of tasks to support? task • target: • specific/general • stationary/moving

  8. Overview • Motivation • A task-oriented approach • Sample application: the NexusRallye • Requirements • Data Model • Context management: the Nexus platform • Platform architecture • Access patterns • Lessons learned

  9. Requirements for NexusRallye • get benefits: • use of existing information spaces (maps, web sites, ...) • easy reuse of tasks • dependency of tasks • support different types of tasks • support different rallies sharing tasks • automatic scoring (if applicable), else: sending results to the jury (e-mail) • multiplayer game

  10. Use Case • player searches for rallies in her surrounding • player (or team of players) signs up for a rally • player gets initial tasks • dependencies between tasks lead player to (multiple) paths through the rally • after solving enough tasks or a time-out occured, the game ends • player gets result

  11. Association of tasks and rallies • tasks can have more than one location • for different rallies, a task can be relevant at different locations • Solution: concept of Virtual Task Container (VTC) • a rally consists of VTCs • each VTC has a certain visibility area • VTC references tasks to that area, which get available for player if she enters it

  12. Sample Rallye Scenario ? ? 2 ? ? 4 ? ? ? 3 ? ? 1 Campus University of Stuttgart reference virtual task container with visibility area ? rallye area player task

  13. Tasks can lead to each other find Nexus lab cafeteria ? 2 ? go to cafeteria 4 ? ? ? Nexus Lab 3 ? 1 ? Campus University of Stuttgart reference virtual task container with visibility area ? rallye area player task

  14. Designing a rally • choose tasks: • use goTo/bringTo tasks to let users go to certain locations • choose tasks more or less connected • enable different paths through the rally • model VTCs: • associate appropriate tasks • ensure that players always have "something to do" • Easter eggs: VTCs with no prior hint (e.g. moveTo tasks)

  15. VTC pos: Point visibility: Polygon Rallye name: String extent: Polygon Player name: String pos: Point Data Model of NexusRallye contains takes part references … Task ? + library, street, copy machine, cafeteria, ...  context model Action Task Question Task

  16. Overview • Motivation • A task-oriented approach • Sample application: the NexusRallye • Requirements • Data Model • Context management: the Nexus platform • Platform architecture • Access patterns • Lessons learned

  17. multiplayer game, common model necessary no reuse of existing context data  Nexus platform Context Management • Context model: • map data (buildings, streets, POIs, ...) • user positions (moving objects) • tasks and game related objects (for BringTo-tasks) • Access: queries and events • Design alternatives: • local (on the client) • server-side (one specialized server) • shared (among several servers)

  18. Multimodal Navigation SmartFactory Mobile City Guide Nexus Rallye sensor data The Nexus Vision: Federated World Models Context-aware Applications … GlobalContext Model Federation LocalContext Models Digital Information Spaces ... Digital Libraries WWW

  19. The Nexus Platform: Architecture applicationtier Application B Application A Federation Hoarding Federation Federation Query Component AreaServiceRegister federationtier NavigationService EventService GeoCast register context models: map data, user positions, tasks, ... servicetier ContextServer ContextServer ContextServer

  20. register notification MapService Query Component NavigationService EventService GeoCast notification Value-added Services Queries Events The Nexus Platform: Access Patterns applicationtier Application B Application A Federation Map Service Federation Federation Query Component AreaServiceRegister federationtier NavigationService EventService GeoCast XML interfaces (over SOAP) • simple spatial query language (AWQL) • spatial model exchange language (AWML) • event registration and notification languages(ERL, ENL) • Navigation routes (NRL), Map (MapPL)... servicetier ContextServer ContextServer ContextServer

  21. NexusRallye and Nexus Platform applicationtier Application B NexusRallye Queries: get rallies, get VTC, get tasks Federation Hoarding Query Component AreaServiceRegister federationtier NavigationService Events: OnEnter VTC area, solved moveTo/bringTo EventService GeoCast register ContextServer 1: Campus Model ContextServer 2: VTCs, Rallye-Objects servicetier ContextServer 3: Moving Objects (Players)

  22. Lessons learned • NexusRallye: • good sample application to prove the openess of the Nexus platform • explorative location-based applications: • demand actions from the user by tasks • assumption: • user need time and have to see clear advantage • games can do this (advantage: edutainment) • still pending: user studies to prove acceptability and learning success

  23. Obrigada! www.nexus.uni-stuttgart.de

More Related