Mobility Scenario
4.1.8 Use Case 05.1M: Added Value Services based on QoS Crowded Bus Metric
Use case Id
UC05.1M
Title Added value services based on QoS crowded bus metric Involved building blocks
Discovery Service, Transport System
Involved applications
GAMBAS mobile application
Required data
Routes, MAC addresses detected inside the buses
Offered services Route with the lowest number of passenger per bus Involved partners
UDE, ETRA I+D, NUIG, OU, EMT
Table 8 – Added Value Services based on QoS Crowded Bus Metric Summary
In the same way the crowded metric can be valuable for the transport operator, the GAMBAS mobile application could use this piece of information to establish complex queries, involving not only the desired destination, but also imposing constraints on the how crowded the selected route – specific bus – may be.
In this way, the traveler could use a composite trip planner that would require as input data not only the final destination, but also parameters as “allowed crowd level in a bus”, “preference in travelling with a friend” or “preference in making use of a low polluted route”
Gambas App Discovery Service
Transport System
PTES EMT
BIT
detect/remove MAC Discover services
Registre data service
close door Query route by less crowed criteria
update passengers
Query route extended
routes with load crowed info
route with info extended
calculate load crow in route
Figure 8 – Added Value Services based on QoS Crowed Bus Metric Sequence Diagram
4.1.9 Use Case 06M: Added Value Services based on Shopping Layer
Use case Id
UC06M
Title
Added value services based on Shopping layer
Involved building blocks Discovery Service, Processing System, Shopping layer Involved applications
GAMBAS mobile application, Shopping announce system Required data
Offers, shops positions, wish list
Offered services
Customized information related to shopping
Involved partners
UDE, NUIG, OU Table 9 – Added Value Services based on Shopping Layer Summary
The user is interested in knowing the shopping possibilities (special offers, new shops, sporting equipment etc.) while travelling from point A to point B. This interest can be registered either by user speaking it to the phone or by setting it visually using the GAMBAS shopping application. The user is encouraged to use the shopping layer app by getting discount coupons, e.g. doing grocery from a suggested store will give users discount coupons for filling tanks at particular gas stations. On the other hand, the shopping stores may benefit from announcing themselves on GAMBAS app by having their advertisements send to other users.
Gambas App
Discovery Service
Processing System
Shopping System
Register shopping data service Register shopping data service
Discover shopping data service
Capture "Go To"
Allow location query (PRF)
Start continuous query location (CQP)
Location data
Continuously query shopping possibilites (CQP)
Query (CQP)
loop loop
Shopping data
Shopping data
Location data
Updated query (CQP)
Shopping data
Shopping data
Alert reached destination
Figure 9 – Added Value Services based on Shopping Layer Summary
During the travel to point B, based on the user’s preferences the user is notified about the shopping possibilities that are nearby and will not require user to alter his path of travel and also those possibilities which are not nearby and will require change in user’s path to the destination. The notification of shopping possibility is announced either on the device’s screen and/or using a device’s speakers.
In order to get the useful notifications (nearby shopping possibilities), the user device will send its current location to the processing system. Moreover depending on user’s privacy setting the processing system will be notified at which shopping possibility the user stopped and did the shopping.
The Shopping System is out of the scope of the project. A third party should provide for its functionalities, or at least for the data required by the processing system to run the queries. Nevertheless, this scenario was one of the original ones motivating the project, since it describes the use of two completely different sources of information, in order to provide a new functionality to the user: customized shopping information on route from point A to point B.
This use case could also be extended in the context of the mobility scenario by sending the offers directly to the bus information screens, or even to the bus stops, adapting the advertisements to the public interests in real time.
4.1.10 Use Case 07M: Added Value Services based on Social Layer
Use case Id
UC07M
Title
Added value services based on Social Layer
Involved building blocks Discovery Service, Processing System, Transport System Involved applications
GAMBAS mobile application
Required data Desired destination, routes, incidents, ETA, position of people, friend relationship
Offered services Adaptive trip plan, notifications on when to start the trip and incidents on route, position of friends
Involved partners
UDE, ETRA I+D, NUIG, OU, EMT
Table 10 – Added Value Services based on Social Layer Summary
The user is interested in knowing the possibilities to meet friends or become part of different social activity groups (reading group, ice hockey playing group etc.) during his movement from point A to point B. The user can specify this interest by speaking it to the phone or by setting it visually using the GAMBAS social layer application, as it was done in UC01M.
During travel to point B, the user is notified of the possibility to meet a friend (listed in the users contact list, retrieved from a social network or explicitly specified by the user). Similarly, the user is also notified about nearby social activity groups.
In order to get the notifications the user will be required to send his current location continuously to the processing system. The user retrieves the location of the friend or the interested social activity group using the Discovery Service and the Processing System. This information can be retrieved from the user’s online social media profiles. Based on this information the processing system will send a
continuous query containing the friend/social activity group to the user. The device can then notify the user in the form “Your friend James is 300 meter to the left” or “A group of people interested in continuous query containing the friend/social activity group to the user. The device can then notify the user in the form “Your friend James is 300 meter to the left” or “A group of people interested in
In order to avoid the explicit existence of a social layer – the citizen network layer identified in section 2 as strong concept – the preliminary architecture that arises from the building blocks defined in section 3 enables GAMBAS to appoint a processing system for a specific period of time as responsible of tracking the user willing to meet friends. In this way, private data is never stored out of the personal GAMBAS mobile phone application, and the user can at any time decide on which data is going to be shared and for how long its position is going to be tracked.
Gambas App
Gambas App
Discovery Service
Processing System Transport System
Register service
Get the route from the user Register service
Retrieve the friends from the user's contact list, social network, etc. (PRF) Request friend/activity group's location (PRF) Start the location query on the friend/activity group's location
Query
Contact friend/activity group for location (PRF) Register location for friends (PRF)
Query for friend/activity group location (CQP, PRF) Start continuous query (CQP)
Register location
Query for route including friend/activity group POI
Query
Receive current route Update friend/activity group location from continuous query (CQP)
loop Update query Update route including POI (if necessary)
Receive updated route (if necessary) Friend/activity group is in vicinity (CQP)
Talk to friend/activity group directly (P2P) Talk to friend/activity group directly (P2P)
Figure 10 – Added Value Services based on Social Layer Sequence Diagram