AP3: Platform architecture and core services

The preceding work packages (AP1 and AP2) describe the view of partners and users such as their requirements in regard to an open mobility platform from the “outside”. The understanding of their current and evolving requirements lays the foundation for the design of the technical platform architecture. A central technical goal is to design a federated platform for local and geo-referenced mobility services.

Besides the services, this platform should also integrate and process heterogeneous data, in particular from different transport providers, vehicles as well as map services. The architecture has to ensure the optimal interaction of the system components based on different quality criteria. These are among other things the clear division of responsibilities and decoupling, but also the guarantee of performance, efficient development and maintenance. A central design objective is safety and data protection in accordance with German and European standards and guidelines. The subproject “Sensing on Demand” (TP 3.4) ensures that only selected end-user generated (sensor-) data of the platform are made accessible. The subproject “Accountability” (TP 3.1) enables users to keep control over their data to restrict the use of the data for specific purposes and using specific mechanisms.

The architectural design for an open digital mobility platform requires a close collaboration between experienced architects, who are familiar with proven architectures from the area of enterprise software (JEE, transaction monitors, relational databases, messaging queues, data warehouses, identity management), and developers of innovative, customer-centered and highly scalable solutions by means of Cloud architectures, NoSQL databases, search engines, JavaScript frameworks, big data analytics engines and semantic web technologies.

Until now there is a lack of publicly available architectural principles, reference architecture or architecture samples specifically for mobility service platforms. It is to be expected, that the design-oriented and empirical research of the TUM LLCM will lead to operational application architectures in analogy to the domain-specific architectures for banks, insurances, telecommunication providers and commercial enterprises.

The term core services is used to describe differentiating value-added services of the platform, which are available for all partners through predefined interfaces and using standardized processes. They can be distinguished into generic domain-specific services (geo-coding, geo-referencing, route planning, proximity search etc.) and horizontal services (authentication, authorization, service management, service level agreement, service monitoring, service billing, onboarding, offboarding etc.), that are in principle relevant for all services.

The example of the highly competitive IaaS- and PaaS-platform providers market shows clearly, that these services have to be produced efficiently and cost-effectively and that they have to evolve in an agile way at the same time. This requires the development and the use of innovative, software engineering methods (service-oriented architectures, model-based tools, micro services, introspective architectures, data-centered big data architectures etc.) and domain-specific, algorithmic and database innovations (proximity search, intermodal route planning, traffic modelling and traffic forecasting).

TP3.1: Accountability
TP3.2: Integrated Monitoring (Infrastructure, Services & Business)
TP3.3: Visual Service-Management Control Panel
TP3.4: Sensing on Demand
TP3.5: Proximity Services
TP3.6: Technical Platform Architecture