As stated previously, commuters will have the ability of connecting to metro monitors via Bluetooth or through USB cables. The exchange between devices will undoubtedly leave traces of information from one another. So firstly, users will only be able to access a certain area of information on a metro monitor. When they connect their mobile devices they will have the option to download schedules or other information. However, they are limited to only that set of data on the monitor. Secondly, metro monitors will live for a single generation/cycle a generation being 5 years before they get replaced.
Furthermore, considering that information is easily retrieved on devices, all metro monitors will be overwritten or destroyed of properly as to not endanger commuters who have used the metro monitors. They will be promptly replaced by recently recycled devices for another generation and the process will be repeated.
The amount of memory required for each device will be small since most of the data will be stored on a server and the monitors are acting more or less like viewers. What they will store temporarily in their memory, however, are daily schedules or schedule changes.
Interesting post -- good thoughts on some of the roles hardware would play in the successful implementation of your idea. Many other students discussed how RFID could be used with there ideas? Does use of RFID make sense with regards to your idea?
ReplyDeleteWhat are others doing in this space? How are they using hardware. I know the Washington, DC Metro Transit Authority uses something similar. I used to have the application on my phone so I knew when the metro was coming.
Perhaps it'd be interesting to see how they utilize hardware effectively for their backend processing?