Added value services

Added value of the MOBiCENTRE services from a business perspective

Connectivity is ensured through the Communication Manager and the Communication Agent

To support real-time and location-based ITS services, the MOBiNET platform provides the components Communication Agent (CA) and Communication Manager (CM). The CA is a centralised component that resides in the MOBiCENTRE. It is responsible for periodically receiving and processing anonymised location information from end user devices (e.g., on-board units, smartphones, tablets) equipped with the CM. This CM is part of the MOBiAGENT and provides periodic updates that can contain information about the current location of the device, its CM equipped neighbours and its communication capabilities. The CA has an interface towards roadside unit operators and mobile network operators and maintains information about coverage and service availability in a geographical area. Because of its centralided nature, the CA can provide advanced features, for example, geo-fencing and real-time statistics.

The CM ensures that periodic updates are sent to the CA. Applications can deliver their messages for further distribution with the CA while the CA decides on the optimum way to communicate them towards CM’s. (1)

(1) “MOBiNET: Architecture and experiences from a marketplace for mobility services”, Ulf Noyer, DLR
Paper presented at the ITS European, Glasgow, 6 to 9 June 2016

Read about the Communication Agent (CA)

Interplatform clearing represents an important commercial opportunity for exploitation. Several of the MOBiNET use cases but also many potential ones involve users making use of multiple transport means of services during one journey. The particular value that MOBiNET brings is its billing and clearing function that can be called up by a provider’s service app. It would offer automated application of the various operator charges and allow the B2C provider to offer its customers a single payment facility. The outcome would be a mix of cost savings as well as new revenue opportunities for all actors in the service chain.

Read about the billing component tool
For more information, consult report D34.9.1 “Billing ticketing and clearing manager (final) in the library/deliverables section.

Authentication: the Identity Manager (IDM) provides user authentication for using MOBiNET services.

The IDM provides capabilities to manage common identities and to handle all security and privacy related concerns.

The Identity Management framework establishes a common identity for MOBiNET actors (e.g., platform administrator, party administrator, developer, end user). This approach offers end users a single subscription to all MOBiNET services and enables service providers to offer services to end users who have no prior affiliation but are accredited through MOBiNET.

To solve related interoperability issues on the information and technology levels, the IDM defines an identity management ontology and provides corresponding components to manage identities and related identity attributes. In this context the IDM also handles privacy related aspects to ensure that corresponding actors have full control over their personal data. On this basis the IDM framework establishes support for single sign-on, authentication (e.g., OpenID), and authorisation mechanisms (e.g., OAuth). (1)

(1) MOBiNET: Architecture and experiences from a marketplace for mobility services”, Ulf Noyer, DLR
Technical paper presented at the European ITS Congress, Glasgow, 6 to 9 June 2016
Read full description of IDM

Authorisation: this sub-model should provide authorisation features for both clients (e.g. apps) and entities (e.g. users). Client authorisation is foreseen for some use cases that have been implemented.
More information
Full description of Identity Manager

Businesses must make a fundamental strategic choice when they decide how seriously they want to consider and handle data privacy. This will impact their reputation and credibility, the quality of their service, and eventually the scope of their business and the profile of their customers.

To implement privacy one must secure the storage of the data considered private according to the regulations of the country where the ‘service’ (i.e. online cloud/web application service) is deployed. This necessitates the translation of legal constraints into technical requirements. Coding options to fulfil these requirements include anonymisation, access control or both — via well-known security libraries with encryption/decryption or resource/rules/context-based access controllers.

But managing privacy is much more than mere data storage security. Privacy management must be considered as an interactive social process to build mutual trust between the providers and receivers of personal information. This is the precise purpose and role of the MOBiNET Privacy Framework. With proper data privacy controls in place, trust starts to build further trust. The core principle in MOBiNET Privacy Framework is that such mutual trust must be expressed in privacy policies from both sides (the service provider and the data owner), for an automated enforcement at data access time.

With the help and support from the MOBiNET Privacy Framework, agile programmers can develop incredibly creative applications based on MOBiNET services without having to add the complexity of implementing privacy oriented requirements. Still it is possible to associate privacy policies with the risks identified at any time of the following deployment lifecycle.

For more information, consult report D33.8.2 “Privacy and Security Framework” in the library/deliverables section.

The MOBiNET project will prepare a certification framework for MOBiNET services, applications and data. Decisions related to certification of MOBiNET services, applications and data are related to the strategic choices on the future development of MOBiNET, the rights and obligations of individual stakeholders and their business opportunities. The MOBiNET project aims to develop a certification framework that will enjoy wide support by the members of MOBiNET consortium.

The MOBiNET project ensured that the platform and its components were designed and implemented based as much as possible on industry standards.
The functionalities of components supported certain standards (e.g. communications with the Communication Agent / Communication Manager) allowing any types of data formats to be described.