Introduction • The aim is to get the location of the bus stop number, bus number and direction from the user and give him the estimated time. • The buses update their status every 30 seconds with the server with their location. • Current buses are obtained from the list and location of the requested bus can be obtained. • The information is updated to the register and then the time is calculated and returned to the customer.
Introduction • The billing is done at the register per message and per response basis.
Measurements • Measurements were taken for locating the bus stop location. • We used GARMIN 12XL GPS equipment. • Measurements were taken for bus number 71A 10A and 20A. • Bus Stop location was recorded with Latitude and Longitude. • The average time required by the bus to reach location A to location B was measured.
Server BUS Model of the system Bus Number, Bus Stop Bus ID, Location, Time Bus, Time for arrival
Modules Bus Mail Box Bus Mail Handler Bus Schedule Active Bus List Position Update Read Bus Mails Get Bus Number, direction Update Active Bus
Modules Client Mail Box Client Records Bus Mail Handler Active Bus List Time Calculator Bus Schedule Bus Location request Read Client Mails Validate Client Query Active Buses Calculated Estimated Arrival time Get Bus Stop time offset Get Bus time offset Record Access Response
User request • Customer request: • Customers email ID. • Bus Number. • Inbound or Outbound (In or Out). • Bus stop ID. • Location of the bus stop is denoted by the number and its coordinates are retrieved from the database.
User Authentication • The authentication is done when email is sent to the server. • The email field is checked for the authentication purpose. • If the user is authenticated, then the request is forwarded to the information processing functions.
Query function • Inputs: Bus Number, direction. • Functionality: • Access hash table and get the currently running buses with given bus number and direction
Active Bus Updates • Inputs: BusID, Bus Number, Time, Direction. • Functionality: • Maintain a hash table based on bus number and direction (Addition/ Updating buses in this list). • maintain list of bus ids for given number and direction (current and previous time and location ) • Provide exclusion for deletion of outdated records • If records older than 10 minutes delete the entry in hash table.
Performance Parameters • Average Speed of buses 250 meters per minute • Update every 30 sec gives update at 125 meter distance approx. • Mails from all buses handled together every 30 sec improves the performance because less number of thread/tasks involved • Access to the Active buses through hash on bus ID and direction of travel improves response time
OUTLINE Format of Information Table for a particular Bus Number Stopid Stoplat Stoplon Timetaken Additional Information Retrieved: Bdirection : Inbound / Outbound retrieved from the Active Bus List
From the Previous Position ( latp,lonp ) and Current Position ( latb, lonb ) of the bus reported, the closest stop is found : Find the distance between the bus location and the stop location using the function acos(cos(lat)*cos(lon)*cos(latb)*cos(lonb) + cos(lat)*sin(lon)*cos(latb)*sin(lonb) +sin(lat)*sin(lonb)) * r r - radius of the earth The stop with the least difference in distance is chosen.
TimeTaken is got from the InformationTable Get the Current time Get the Last Update time To get the Net Effective time for the bus to reach the customer Durtime : TimeTaken - ( Currenttime – Update Time)
Read Customer record file INPUTS : PCustrecfile PCustacesfile OUTLINE Query the Customer Access Record file and find the number of times a particular customer has used the facility based on the Email-id. Generate the Billing Statement for the customer No of accesses * Price per access Update the Customer with the information via email
Equipment Source : http://www.garmin.com
Business Model • The total cost estimated will include GPS equipment price, charges for sending bus updates from the bus to the server. • Above expenses should be covered by the service provider. • The service provider gets the revenue from the Customer.
The Cost • Cost of Rino 110 / Rino 120 : $150 each • We assume that there are 200 buses. • The Initial cost is : • For 200 equipments= $150*200 • For updating software = $50000 • The running Cost • SMS messages cost around 3cents to the service provider. • Updating for each bus in 30 seconds will cost 200*(0.7(2880*0.03))=$8064 per day. (I.e.) $2’943,360 per year. • Total Cost: • $3’023,360.
Customer Charge • Users will be charged 10 cents a request. • To use this service minimal charge of $4 will be applied to the customer. • We assume that registered customers are around 50000. • From the predictions it is assumed to increase @ rate of 10% per yr. • We assume that there are approximately 5000 requests. • The annual revenue will be around $2546000 for 2002. • (All the figures received from the • http://www.mobileinfo.com/News_2002/Issue23/IDC_survey.htm • http://www.wqed.org/erc/pghist/units/WPAhist/pop_growth.html )
Graph Revenue 3777735 2006 3192000 2005 2940000 2840750 2004 2546000 2003 2002 year