In my solution, the device itself will serve as the ticket. A unique ID gets sent trough NFC to the inspector’s device and gets checked in about 1 second, while the passenger’s device remains locked. The process is simple and it is constructed on the already existing basis of the Wiener Linien system.
When the passenger starts the Vienna Mobile App for the first time, a unique ID (ID) is generated, which clearly identifies the device. When a passenger buys a ticket in the App, the ID is transferred to the backend server and is linked to the purchased ticket. Because of the ID, the ticket is bound to the device. The process is simple and it is constructed on the already existing basis of the Wiener Linien system.
During the checking process the passenger and the inspector hold their devices together for a short moment. The unique ID is transmitted via NFC to the inspector's device. Best of all, the passenger's device can remain locked during the entire process. The inspector's smartphone forwards the ID to the server. The server checks whether a valid ticket is assigned to the ID and returns a corresponding response. The whole process of checking a ticket needs about one second.
The unique ID turns the device itself into a ticket. This means that only the smartphone owner can use the ticket. Transfer to third parties is not possible. Each ticket check is stored on the server, the amount of checked tickets is logged.
Data protection is also covered. The ID alone cannot be used to determine what kind of device it is or who the owner is. Only when the ID is sent to an inspector, is the assignment to the device and to a person traceable.
But there are more features. During the ticket check the passenger's smartphone can either remain locked, or if the passenger is using the device (chatting, surfing on internet, listening to music etc.), it is enough to hold it briefly to the inspector's device. No interaction on the passenger’s phone is necessary.
If more than one person is travelling together, it is possible to buy more tickets from one device, which then also get linked to the same device ID. During the checking process the inspector will see that there are more tickets linked.
If for any reason there would be a problem with the NFC communication between the passenger’s and the inspector’s device, simply open the Vienna Mobile App and show the ticket as usually.
The function to generate the unique ID and the necessary programming for the NFC communication should be integrated in the already existing Vienna Mobile App environment.
What I intend to deliver in the end of the Hackathon
- a explanation video (already available under Video description)
- a demonstration video
- a prototype for the passenger phone (Android)
- a prototype for the inspector phone (Android)
My name is Ronald Logan and i am 44 years old. I work as a software developer and system administrator at a university of applied sciences. I mainly develope and implement workflows in IT-solutions, furthermore redesign and optimize processes by automations. I have experience in C#, PHP, JAVA, WPF and Android development.