Digital management of the railway sector through OSGi. The TRACK project

Transcription

1 Digital management of the railway sector through OSGi The TRACK project

2 What is IBBT? IBBT introduction

3 IBBT Research

4 IBBT: Entrepreneurship

5 IBBT: Develop & Test

6 Information on an OSGi based product solution TRACK framework

7 Problem description Train A from into depot for back update to riding Depot Update Transfer train dependent A with software libraries X

8 Problem description Train B from into depot for back update to riding Depot Update Transfer Library Change already train upload dependent B with present, files, software libraries update blue train X library B missing

9 Problem description Need Use Custom 3rd diagnostics IO party handler IO components information initiates connection from train over technology of choice Custom IO handler Diagnostics Application Custom IO handler

10 Problem description For every other application: custom IO handlers preferred connection type

11 Solution goal Functional requirements No wasted time spent in depot for updates Immediate updates Software version management Extra requirements (research) Modular system Remotely accessible Solve unreliable connections

12 GPSLocation LogService Timetables GPSLocation LogService Timetables MediaService LogService CateringInfo Timetables /07/

13 GPSLocation LogService Timetables GPSLocation LogService Timetables CCTVDriver GPSLocation Undeploying GPSLocation Deploying LogService Deployed Timetables Deployed MediaService Deployed CCTVDriver Deploying MediaService LogService CateringInfo Timetables CCTVDriver /07/

14 GPSLocation LogService Timetables GPSLocation LogService Timetables CCTVDriver GPSLocation Undeploying GPSLocation Deploying LogService Deployed Timetables Deployed MediaService Deployed CCTVDriver Deployed MediaService LogService CateringInfo Timetables CCTVDriver GPSLocation LogService Timetables /07/ CCTVDriver 5.1.0

15 Overview Technical requirements Why OSGi? TRACK overview Feature highlights Challenges Way forward

16 Technical requirements Two types of customers Railway stakeholders but also 3rd party developers

17 Technical requirements Very dynamic environments: unreliable connections

18 Technical requirements Inter-node communication Other research group: network aspects Remote communication (inter-node)

19 Technical requirements Legacy application support: existing (native) applications

20 Why OSGi? Only Java runtime Modular by design Standard JAVA language Dynamic Platform independent!

21 TRACK overview: node layout TRACK Container

22 TRACK overview: framework layout RST Infrastructure Node modules Central System System + Op. services Fleet Node modules TRACK Platform TRACK Platform TRACK Platform Reliable link WiFi/GPRS /3G Node modules TRACK Platform 3rd party providers 4/07/

23 Feature highlights Fleet management Content management Module deployment Monitoring Remote service discovery Job scheduling File transfer: BitTorrent Vaadin UI Legacy application support Communication

24 Fleet management DeviceProfile Definition of device type/family ID + properties definition Can inherit from other DeviceProfiles OPERATOR_X/train hardwareversion inherits from GENERIC/train buildyear, operationarea

25 Fleet management TrackNode Represents a node in the framework Name Host (IP or ID) Is assigned a DeviceProfile TrainX Profile: OPERATOR_X/train buildyear 2000 operationarea ParisNord hardwareversion 4.2

26 Fleet management Querying GENERIC/train (&(operationarea=parisnord)(buildyear>1999)) All devices adhering to this which profile meet or subtypes these conditions.

27 Content management TRACK module Track Module Application binaries or content Meta-data Packaged as JAR/ZIP 4/07/

28 Content management Versioned Item versions meta-data Version Track Module meta-data Version Track Module meta-data Version Track Module meta-data 4/07/

29 Module deployment Central System INIT -> DEPLOYING Content Manager Global Update Mgr. update request Fleet Manager File Sharing Event System 4/07/

30 Target Node Local Update Mgr. Application Manager file transfer Download Manager Update Handler Event System 4/07/

31 Module deployment Central System Content Manager Global Update Mgr. Fleet Manager File Sharing Event System 4/07/

32 Module updates Central System Target Node DiffGenerator Global Update Mgr. Local Update Mgr. DiffBuilder version info? generatediff 1.2-> Δ Archive containing: changed/new files build script buildmodule Track Module 4/07/

33 Monitoring: job status 4/07/

34 Monitoring: remote OSGi console 4/07/

35 Remote service discovery Custom solution for OSGi 4.1 (no RSA available): R-OSGi Producer Node A Node B Consumer Remoting is transparent TRACK framework TRACK framewrok Register service Expose service Generate proxy R-OSGi SLP Discovery: advertise SLP R-OSGi R-OSGi specific communication

36 Job scheduling Updates are scheduled as jobs Concurrent update jobs Scheduler allows Prioritization of individual jobs Pauze / resume of individual jobs

37 File transfer: BitTorrent Downloads are divided in small parts Clients download small parts in random order Client stitches everything together Unreliability solved: In case of failure, only small piece lost Immediately start downloading piece from other source

38 Vaadin UI Webpage UI done with vaadin Modularity of OSGi bundles visible in UI Easily integrated with the webserver (Jetty) hosted in OSGi All fleet and content interfaces done in Vaadin

39 Legacy application support Installing, uninstalling, updating Custom update handler TRACK container External System Update Mechanism Track Module updatehandler install uninstall Controller Extension possible TRACK update handler

40 Legacy application support Life cycle management: start, stop OSGi TRACK Container External legacy application MyApplication JVM bridge JNI EntryPoint OS Implement Application interface (TRACK Activator) through JNI (Java Native Interface)

41 Challenges Remote communication R-OSGi (Common) external libraries in OSGi context Simple: wrap as OSGi bundle Nasty: fix class loading issues (class loaders ) Last resort: * DynamicImport-Package *

42 Way forward (RAILS) Decentralizing the current framework Allows for more robustness, server may fail, others can resolve issues. => No single point of failure Replace R-OSGi with Remote Service Admin Own implementation: focus on open standards => Better support for 3rd party Discovery: JGroups Service communication: HTTP/JSON

43 Thank you for your attention Questions?