A Platform for Efficient Supply Chain Management Support in Logistics

Transcription

1 A Platform for Efficient Supply Chain Management Support in Logistics Maik Bevermeier*, Stephan Flake**, Reinhold Häb-Umbach*, Jan Stehr*** *University of Paderborn **Orga Systems GmbH ***omp computer GmbH Dept. of Comm. Eng. Paderborn, Germany Paderborn, Germany March 22th 2011

2 Outline 1. Introduction 2. System overview 3. Architecture of the DraFaLa system 4. Some security aspects 5. Summary and outlook

3 Project DraFaLa (Wireless Truck and Cargo Monitoring supported by On-Board Units of Telematics Toll Systems) Objective Development of an open multi-provider platform for customizable valueadded services (VAS) in the transport telematics domain Integration of existing infrastructure and technology by re-using elements of telematics toll systems (e.g. On-Board-Unit) Investigation, development and integration of flexible and cheap valueadded services Focus on the VAS: Wireless truck & cargo monitoring in realtime Offering of value-added services to carriers -> abfrage via internet e.g. Key information The project is integrated in the Ziel2.NRW program (Automotive.NRW) and encouraged by funds of the EU Project duration: February 2009 January

4 System overview Electronic Toll Collection OBE Primary task: Toll collection Data exchange via GSM, CAN, GPS, Data exchange with other devices Truck & Cargo Monitoring ECU Soft- and Hardware Platform for the integration of VAS Cargo Bay Unit (CBU) Cargo Monitoring Hardware for quering sensor information Wireless comm. with TCM-ECU VAS Center Service platform Interface for customers etc. to get access to the information Billing gateway for offering services with transparent tariffs

5 System architecture ETC OBE (Electronic Toll Collection On Board Equipment) Subsystem for OBE functions (e.g toll collection) Main components: 1. VAS Client Gateway Interface between telematics system and VAS subsystem Managing of VAS messages (forwarding/negotiating) Forwarding of positiong information to the VAS subsystem Forwarding of reports from the TCM ECU to VAS Centers Payment functionalities Access to the Human-Machine interface in the truck 2. OBE Application Implements the corresponding business logics (e.g. ETC) Offers controlled access to OBE resources Maintaining priorities of crucial services 3. OBE API Access to communication interfaces (e.g. GSM, DSRC) Access to positiong module of the ETC OBE

6 System architecture TCM ECU (Truck & Cargo Monitoring Electr. Control Unit) Core unit for VASs, connected to ETC OBE via telematic bus Main components: 1. VAS-OBE Gateway Offers the comm. interface for VAS applications on the TCM ECU Registering and Self-authentication to the ETC OBE Uses the interface to the ETC OBE to communicate with other system components Mapping of all functions offered by the VAS Client Gateway 2. VAS System Application Initialises all subcomponents (e.g. security & diagnostic modules) Starting of individual VASs Managing of systems state machines a) Service Manager: Controlling of VASs, providing of the required interf. b) Configuration: encapsulates the functions for the administration of the static and dynamic system configurations c) VAS Security: Security component (TCM ECU + CBU <-> VAS Center) d) VAS Diagnostics: Logging and debugging purposes e) VAS Location: Offering an interface to request position information

7 System architecture CBU (Cargo Bay Unit) Core unit for VAS Cargo Monitoring Access via the CBU Controller Main components: 1. CBU Controller Periodically polls all connected CBUs Scanning for unknown CBUs Reconnection (if link is lost) Offers an interface for wireless access to the CBU Includes a bluetooth API with SOAP Invoking methods of the CBU Application (e.g. querying of the sensor reports in the CBU) 2. CBU Application CBU s main component Managing of the queries by the CBU Controller Communication with the individual sensor hardware Access via SOAP Link to the corresponding bluetooth proxy

8 Query Query Query Workshop on Intelligent Transportation Systems (WIT 2011) System architecture CBU Application: Level A: Hardware-Abstraction-Layer (HAL) with core comm. CBU Manager Core comm. (Hardware X) Manager Core comm. (Hardware Y) LEVEL A components (hardware access) Level B: Periodical quering of the Notify Manager Joiner & Timer Manager Joiner & Timer LEVEL B sensor information Level C: Notify Joining, storing & providing Manager all information for handlers Joiner & Timer LEVEL C Additionally: Configuration of a software instance via XML-files GUI/ Logger SOAP- Server Handler- LEVEL

9 Some security aspects Bluetooth communication (TCM ECU <-> CBU): CBU Controller (Truck) BT-Proxy (Java) CBU Application (Trailer) Client SOAP Frontend RFCOMM Backend SOAP Server Proxy implementations are transparent to SOAP communication SOAP queries are transmitted via BT s RFCOMM profile Bluetooth partners must match to a special service profile The CBU can be choosen by a Human-Machine interface (by truck driver) Automatic reconnection if a bluetooth link is lost Security (TCM ECU <-> CBU): Pairing comparable to the KERBEROS authentication protocol VAS Center is the authority, which allows/denies a link Public/private key protocol similar to Needham-Schroeder Exchange of symmetric keys and nonces (RSA) Keys can be renewed sporadically

10 Summary and outlook Summary: Platform for efficient supply chain management, which uses the infrastructure of modern electronic tolling systems Requires less proprietary hardware -> economically attractive Software concept allows integration on a smartphone Reliability is achieved by a strict separation of toll-related and VAS-related subcomponents VAS Center supports various tariff models Demonstration system has been set-up Outlook: Integration of other value-added services Mobile devices instead of a PC-based platform Analysis of billing services Presentation of the demonstration systems to interested third parties

11 Thank you very much for your attention??? Questions???