Three are the computing components of the system architecture; these are the On Route Information Server
(ORIS) running on vehicles, the Android Client Application (ACA) running on traveler mobile devices and the
Information Services Provider (ISP) running on relevant point of the public transport network, see Fig. 1. With the
system architecture, when a vehicle reaches the station, its ORIS communicates with an ISP of the infrastructure,
informing it of its connection address. When the ACA of a passenger seeks available services, it contacts the ISP and
the ISP sends the ACA all the on route information active services in its database and their connection addresses. The
only thing that ACA has to do then is to connect with the ORIS it is most interested in. This way, the system
architecture attains a high degree of scalability of services, as there is no need for a different service identifier for each
server running on vehicles; they all use the same one, and they report their connection address to the ISP. The time
required for the services search is also reduced, as the mobile devices only have to search for a single engine, the
ISP, and then connect directly with the line they are interested in. This arrangement has proven to be much faster
as the search for devices is very slow in such limited devices as mobile telephones, and the more devices there are nearby, the more this limitation increases.