5.1.2017 1

Helsinki Developers Day 28.2.2017

Olli Pihlajamaa & Immo Heino, VTT

Living Lab Bus as a development platform

24.3.2017 2

THE GOAL

Enabling and supporting faster development of mobility services through a concrete, open test environment in a real public transport context.

24.3.2017 3

OBJECTIVES• Open platform for technology and service providers –

development, testing and demonstration of newtechnologies and services

• Quick prototyping and testing – fastercommercialization and credible verification and references

• Real context and real users – user acceptance, feedback and development ideas

• Co-development ecosystem – new mobility servicevalue chains, and information exchange

You?

New ideas and users are welcome!

RESEARCH ORGANIZATIONS

COLLABORATING COMPANIES

ENABLERS AND SUPPORTERS

THIRD PARTY PARTICIPATION

24.3.2017 4

24.3.2017 5

Real buses as concrete test platform

Electric buses being deployed by end of 2016 in the Helsinki region, Tampere and Turku

BUSES AS A PLATFORM

VTT’s test bus

Bus mule for prototypes and testing before deployment

24.3.2017 6

LLB technical environment

BLE Beacons TinyNode sensor hubs (w/ BT connectivity)- temperature- humidity- air pressure- acceleration

Real-timedata:- sensor data- CAN data

APIs for developers

LLBResource

mgmtCAN data DC 24V

LIJ

VTC 1010 in-vehicleComputer w/ U-bloxM8N GPS + deadreckoning

BeagleBone Black single-board computer 3G/4G/GPS

multibandantenna

Component case

Displays

3/24/2017 7

Bus as a mobile sensor platform

• Road surface (temp., water layer thickness, black ice, …)

• Weather (temp., humidity, air pressure etc.)• Light (luminosity, sunshine)• Air quality (O3, NO2)• Position (GPS)

• Air quality (temp, humidity, air pressure, CO2)• Acceleration• Vibration• Acoustic (Noise / sound level)• People counting (many technologies)• CAN data• Real time video

Outside

Inside

Outside

Bold = planned for initial infrastructure

24.3.2017 8

Developer portal & landing page

24.3.2017 9

EXAMPLES

• New solutions could be, for example:

• Bus interior design choices; comfort and passenger experience

• Passenger services such as real-time information on connections or alternativeoptions (e.g. availability of nearby city bikes and last-mile solutions)

• Environmental monitoring technologies (e.g. indoor and outdoor air quality)

• Sensor and IoT data from the vehicle and environment for service development

• Technology testing and validation (e.g. passenger counting, V2X)

• …

24.3.2017 10

LBB – current status and near term plans

• Technical environment provided by VTT• VTT software components (long-term) tested and ready for installation (since 2Q/2016)

• Waiting for the new HW (Beagle Bone => Nexcom VTC 1010)

• Integrating data also from HSL LIJ (MQTT Broker @ MS Azure)

• First installation in Linkker electric bus operated by HelB (nr. 5, line 23) during March 2017• Linkker has started the planning for installation (vehicle computing & display units)

• Some practical installation details are still under negotiations

• 9 more bus installations are expected during the 2-3Q/2017

24.3.2017 11

LLB Vehicle Data Collection

• API’s• Implemented the real-time data API, data visualization,

and data blob API for the sensor (temperature, humidity, pressure, etc.) data (to be) collected from the bus.

• Beacons

• 6-12 beacons ready to be installed to first busses (tests already done in BussiMuuli)

• Implemented public API for beacon information.

• Smart Stop• Bluetooth environment sensors installed to bus stop’s and

the bus system conveys the data to the cloud upon drive-by (Oulu test done, to be installed in Espoo next). BUS

LLB MQTT Broker

AZURE MQTT Client

data queue 1

HSL MQTT Broker

veh

icle

da

ta

subscribe sensor data

LIJ SystemDisplay

data queue 2

data queue n

...

Azure data queues

AZURE Blob Storage

AZURE Real-time Data storage

Real-time Data API

Cold Data API

Sensor

Sensor

Sensor

BEAGLEBONE BLACK

BT

VTC 1010

24.3.2017 12

Publicly available interfaces

• Sensor and location data available from the electric bus fleet• ”Sensor data” provided by VTT and ”location data” by HSL (combined @ MS Azure)• ”Hot path” (real time sensor & location information snapshot)• E.g.: http://13.69.197.43:8080/RTDataAPI/?busId=1&gwId=1• “Cold path” (cumulative sensor information / day example)• E.g.: https://llb.blob.core.windows.net/llbbusdata/2016_04_23

• Permanent URIs will be defined later when the system will be operational• Documentation should be improved (currently nearly no-existent)• Sensor set might be unique to a certain bus• Same data is also available from LLB’s MQTT server

24.3.2017 13

MQTT server interface

• Broker address : 52.169.157.94:1883

• Topic: fi/llb/type/target/targetid/gatewayId/• Type: sensor, location,…• Target: bus, tram, metro, stop,...• TargetId: id of the target, bus id/stop id (from HSL system)

• Content (sensor):• {“timestamp”:“"2016-03-31T06:44:05.232Z", “sensor”:”sensortype”:”sensorid”:”sensorvalue”,...}

• Content (location):• {"timestamp":2017-03-

01T13:03:22.000Z,"latitude":65.056122667,"longitude":25.455772167,"altitude":-3.900000000,"eps":nan,"epx":nan,"epv":97.290000000,"ept":0.005000000,"speed":0.073000000,"climb":0.000000000,"track":0.000000000,"mode":3.000000000}

24.3.2017 14

Used formats (JSON)

• Sensor data• {"fi/llb/bus/1/1":{"pressure": 1015.1, "index": 7366, "temperature": 22.1, "timestamp":

"2016-04-11T20:59:04.776Z", "battery": 3.0, "sensorId": 2, "rssi": 73.7, "humidity": 24.2}}

• Location data• {"timestamp":1462957092749,"type":"sense","deviceAuthUuid":"13db45d0-faff-11e5-8f18-

8b5839d6eca3","cause":{"engine":{"pId":"5716128dc4e2b27350b51b1b","puId":1,"stId":0,"evId":0,"ts":1462957092749},"senses":[{"sId":"0x00010100","val":60.1803512573,"ts":1462957092749},{"sId":"0x00010200","val":24.8259334564,"ts":1462957092749},{"sId":"0x00010300","val":17,"ts":1462957092749},{"sId":"0x00010400","val":19,"ts":1462957092749},{"sId":"0x00020100","val":1,"ts":1462957092749}]}}},"sensedata": {"/13db45d0-faff-11e5-8f18-8b5839d6eca3/events":{"timestamp":1462957069349,"type":"sense","deviceAuthUuid":"13db45d0-faff-11e5-8f18-

24.3.2017 15

APIs will be documented…

group property sensor_id unit datatype

location latitude, signed 0x00010100 degrees float

location longitude, signed 0x00010200 degrees float

location altitude, signed 0x00010300 metres float

location accuracy 0x00010400 metres float

location Is inside geofence 0x00010500 boolean boolean

speed gps speed 0x00020100 m/s float

energyBattery full capacity

0x00030100 mAh float

24.3.2017 16

Availability & further information

• Mandatory registration as a user is planned• Collecting knowledge how information is utilized

• enables promotion of new services in the LLB “landing page” (“HSL quality control” needed)

• Estimations how much resources will be needed

• “Official site” http://livinglabbus.fi/• More information will be provided when open data will be publicly available

• For more technical information & related inquires – contact: Janne.Lahti@vtt.fi

THANK YOU!

Olli Pihlajamaa & Immo HeinoVTT TECHNICAL RESEARCH CENTRE OF FINLAND LTD

olli.pihlajamaa@vtt.fi, immo.heino@vtt.fi

www.livinglabbus.fi

Contact: info@LivingLabBus.fi