IST Shuttle - Booking, management and monitoring service Duarte Sérgio Ramalho Barbosa Thesis to obtain the Master of Science Degree in Information Systems and Computer Engineering Supervisor: Prof. Teresa Maria Sá Ferreira Vazão Vasques Examination Committee Chairperson: Prof. Mário Rui Fonseca dos Santos Gomes Supervisor: Prof. Teresa Maria Sá Ferreira Vazão Vasques Members of the Committee: Prof. João Pedro Faria Mendonça Barreto April 2015 ii Acknowledgments MichaelJ.Foxputsitbest: ”Familyisnotanimportantthing. It’severything.” iii iv Abstract ThegrowingmobilityproblembetweendifferentpointsinthecityandtheInstitutoSuperiorTe´cnico(IST) campi portraits the shuttle service as one of the most important solutions for current difficulties. It also posesnewchallengesrelatedtoticketing,fraud-evasionandeffectivecost-wisetransportationservices. ISTprovidesitscommunityafreeshuttleservicebetweenTagusparkandAlamedaCampiandother keypointsofthecityensuredbyanoutsourcedvehicleservice. Thisshuttlehasseveralstaticpredefined routes, stops and schedules. All the management is done manually in a tedious and non-optimal way, not allowing the shuttle to effectively surpass its passengers necessities in real-time. Moreover, there arequiteoftenproblemswiththeseatoccupationleadingtoeitheroverorunder-crowdingofthevehicle. This work proposes a dynamic and real-time Booking, Management and Monitoring (BMM) service for the IST shuttle service. Members of the community can access, in real-time, the central platform to bookaseatormonitorthefleetofvehicles. Anembeddedsystemisdeployedineachvehiclethatgrants accesstoauthorizedusers,givingprioritytotheonesthathavebookedseats. Thissystemperiodically communicateswiththecentralplatform,toinformaboutthelocation,speedandseatoccupancyinthat journey. The BMM service was validated in the field with trial experiments and the results have shown thatthesystemissuitableforbeingdeployedandimprovestheuserexperienceoftheshuttleservice. Thisprojectdrawsitsinspirationinempiricalexperiencebytheauthorandothershuttlepassengers livingthesesameproblems. Keywords: Mobilitymanagement,Real-timeBookingsystem,Shuttleservice v vi Resumo O crescente problema de mobilidade entre va´rios pontos da cidade e os campi do IST evidenciam o servic¸odeshuttlecomoumadasmaisimportantessoluc¸o˜esparaestasdificuldades. Trazaindanovos desafiosrelacionadoscomaemissa˜odebilhetes,evasa˜odefraudeseservic¸osdetransporteeficientes nocusto. O IST oferece a` sua comunidade um servic¸o de shuttle gratuito entre os campi do Taguspark e da Alamedaeoutrospontosdacidade. Esteservic¸oe´ asseguradoporumatransportadoracontratada. O shuttletemdiversasrotas,pontosdeparagemehora´riosesta´ticos. Todaagesta˜oe´ feitamanualmente numprocessoentedianteena˜ooptimizado,impossibilitandoqueesteservic¸osupereasnecessidades dosseuspassageirosemtemporeal. Ale´mdisso,e´ frequentehaverproblemasnaocupac¸a˜odelugares, levandoave´ıculossobrelotadosouporvezes,quasevazios. Estetrabalhopropo˜eumservic¸odeReservas,Gesta˜oeMonitorizac¸a˜o(BMM)dinaˆmicoeemtempo real para o shuttle do IST. Os membros da comunidade podera˜o aceder, em tempo real, a` plataforma central e reservar lugares ou monitorizar o estado dos ve´ıculos. Um sistema embebido e´ instalado em cada ve´ıculo e concede o acesso a utilizadores autorizados, dando prioridade aos que tiverem reservadoumlugar. Estesistemacomunicaaindaperiodicamentecomaplataformacentral,informando sobreasualocalizac¸a˜o,velocidadeeocupac¸a˜odelugaresnaquelacarreira. Oservic¸oBMMfoivalidadonoterrenocomtestespilotoeosresultadosmostramqueosistemase encontraprontoparaserinstaladoequemelhoraaexperieˆnciadosutilizadoresdoshuttle. Este projecto e´ fruto da experieˆncia emp´ırica do autor e de outros passageiros com os mesmos problemas. Palavras-chave: Gesta˜odemobilidade,SistemasdeReservaemtemporeal,Servic¸oShut- tle vii viii Contents Acknowledgments iii Abstract v Resumo vii ListofFigures xiv ListofTables xv Acronyms xvii 1 Introduction 1 1.1 Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 ProblemStatement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3 Thesisobjetivesandexpectedcontributions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 Solutionoverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5 Outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 RelatedWork 7 2.1 ElectronicIdentification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1.1 IdentificationDocuments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 AccessControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.1 ElectronicTickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2.2 BookingSystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.3 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 Vehicleinformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.1 GeolocationTracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2 On-boardinformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4 Synthesisanddiscussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3 Architecture 16 3.1 Systemrequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 ix 3.1.1 Usecases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.1.2 Functionalrequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.1.3 ArchitecturalRequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1.4 PerformanceRequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.2 Generalarchitecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.2.1 Designoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.2.2 Systemoverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3 Centralsystem-ShuttleServer(Shuver). . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.3.2 Bookingcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.3 Managementcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.3.4 Monitoringcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.3.5 Databasecomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.3.6 Communicationcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.4 Booking,ManagementandMonitoringServiceClient. . . . . . . . . . . . . . . . . . . . . 30 3.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.4.2 Accesscontrolcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.4.3 Communicationcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.5 Embeddedsystem-YetAnotherEmbeddedClient(YAEC) . . . . . . . . . . . . . . . . . 31 3.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.5.2 Accesscontrolcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.5.3 Datagatheringcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3.5.4 Communicationcomponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3.5.5 Physical/HardwareConstraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 3.6 Moduleinteractions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.6.1 Booking,ManagementandMonitoring(BMM)serviceclientsandShuver . . . . . 37 3.6.2 YAECandShuver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.7 Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4 Implementation 40 4.1 ImplementationOptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.1.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.1.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.2 Prototype-Shuver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.2.2 Booking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.2.3 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 4.2.4 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.2.5 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 x
Description: