CAN Signaling Agent. A generic model to handle signals. AGL AMM Feb/2017 Fulup Ar Foll Lead Architect

Transcription

1 CAN Signaling Agent A generic model to handle signals AGL AMM Feb/2017 Fulup Ar Foll Lead Architect fulup@iot.bzh

2 st 1 technical Contributor Application Development Integration Yocto recipes Releases automation & Testing (CI) Renesas boards support Security (MAC, Cynara, Systemd, CGroups, NameSpaces,...) Low Level Services SDK (binary distro + development ready docker container) Application Framework (live cycle, cybersecurity provisioning) Application Binder Framework (APIs exposure & protection) Audio Manager Connectivity Signaling & Events SOTA Secure Boot & Trusted Zone Community Support Documentation (kickstart, developer samples, guides...) White Papers & Conferences (Genivi, AGL, Fosdem, ELC,...) Renesas Community support 2

3 Event/Signal Requirements Applications Platform Easy way to decode CAN vectors API independent of low level formatting Composed signals (ex: all doors closed) Long term API stability (W3C?) Efficient, limit resource consumption as much as possible, fast decoding/encoding Reduce number of fired event as low as possible and if possible directly at hardware level Extendable to other bus model (Lin, Flexray, Ethernet, MOST,...) Built in Security Manufacturer Keep signal vector description confidential Allow developers to nevertheless write applications Protect from intrusion Only expose meaningful signal to application 3

4 AGL Micro-Services Architecture Entertainement Cluster Navigation Service Head Unix Direction Indication Carte handling Localistion management POI My Car Portal Maintenance Portal Paiement Know Bugs Subcriptions Maintenances Preference Service Packs Transport & ACL Transport & ACL Transport & ACL Cluster Virtual Signal Cloud CAN-BUS Virtual Signal Engine-CAN-BUS CAN-BUS ABS LIN-BUS Geopositioning Virtual Signal Preferences & Custumisation Gyro, Acelerometer MongoDB Engine No-SQL Engine Paiement Service Statistics & Analytics CAN GPS Log Analytics Multi ECU & Cloud Aware Architecture AGL-2.0 Application Security Model 4

5 Current Framework Capabilities Asynchronous signalization Basic Create/Subscribe event model Transport onto WebSocket/Dbus AGL-CC event signaling API handle = afb_daemon_make_event (bindif, name) afb_req_subscribe(request, handle) afb_req_unsubscribe(request, handle) afb_event_push(handle, json_object_get(object)); Notes: bindif provided by binder at binding registration time request provided by framework on behalf of client 5

6 API Binding Registration 6

7 Event Create/Subscribe 7

8 Built In Security Security Context Cynara Security Check Transport Layer UI Binder Security Context Binder CAN API CAN High Level Binding(s) XXXXX API CAN Low Level Binding(s) 8

9 CAN agent base on AGL framework Clear Isolation Security Built In Low level CAN operation only depends on equipment High level business logic dedicated to applications Navigation APP may access GeoLocation by not Telephony Implement statistic/counter to monitor unexpected behavior Leverage AGL-CC framework API transparency for client applications Reuse existing technology (faster, cheaper, safer) 9

10 AGL CAN Mapping UI Publish Subscribe Binder CAN High Level Binding(s) Logic Aggregation («vehicle.doors.any.open») Advanced Ops Signals - «vehicle.doors.left.open» (Binder Events) CAN Low Level Binding(s) Decoding / Encoding Authentication / Crypto / Firewalling Transaction (set ack...) Stats & Maths Caching (low freq. Signals, get() call) Debug CAN frames CAN BUS 10

11 High Level Binding Business API level Composing event W3C? Separation/Isolation All doors closes Long Term APIs move > 300m or Angle > 30 or 600s Responsibility Live cycle Hardware dependencies Long Term API W3C (VISS) VW (ViWi) Others? 11

12 Low Level Binding Low Level Binding Close to Automatic Code Generation OpenXC CAN vector definition in JSON Other CAN vector as CANoe Include Basic Filtering & Statistic Binary encoding decoding Generate Application Friendly Signal Name & Values GT/GE LT/LE Timer, Cycle, Timestamps Counter: last value, average, invalid ID, Can be ship to developer as binary only 12

13 From OpenXC to CAN Binding OPENXC OPENXC Signal OPENXC Signal Description Signal Description (JSON) Description (JSON) (JSON) OPENXC Code Generator (python) Low Level Binding Static Code (AGL) Optional Message Handlers (vendor) CAN Decoding/ Encoding C Code (vendor) C/C++ Compiler CAN Low Level Bindng (Shared Library) 13

14 OpenXC Specification Signals Generic_name - The name of the associated generic signal name bit_position - Staring bit position of this signal within the message. bit_size - The width in bits of the signal. factor - The signal value is multiplied by this if set. offset - This is added to the signal value if set. value_handler - type & function name applied to signal value signal. Useful with custom handler for an entire message states - Mapping between descriptive enum states and values send_frequency slow down high level signal frequency (ex: 1/10) send_same if false only send signal when value change writable signal is writable on can write_handler in case a custom encoder is needed Messages name - The name of the CAN message. handler Function name applid to entire message signals - A list of CAN signal objects that are in this message, 14

15 OpenXC Sample Definition "0x49": { "name": "BrkSt", "bus": "hs", "signals": { "BrakePedalPosition": { "generic_name": "brake_pedal_status", "send_same": false, "decoder": "booleandecoder", "bit_position": 0, "bit_size": 1 }, "TirePressure": { "generic_name": "tire_pressure_front_left", "decoder": "tirepressuredecoder", "bit_position": 3, "bit_size": 5 } } }, 15

16 W3C ViWi (VW) proposal Originally based on REST, moving to WS The depth of the URI tree is limited to 3, i.e. /<service>/<resource>/<element> Query filter GET /<service>/<resource>/?name=foo,bar An event 'on change' if two subsequent GET requests result in different responses Keep overall network traffic minimum (filtering) Every object inherits from Xobject. 3 non filtrable mandatory properties: id, uri and name Example GET dashboard/decoration/?id=0dde0b53-b862-44ec-bab2... GET medialibrary/tracks/?rating=5 EVENT { "type" : "subscribe", "event" : "/<service>/<resource>/<element>?<queryparams>#<uniqueid-per-session>", "interval":<ms> "updatelimit":<ms>, "Authorization": <token>} JSON RESPONSE: { "status" : "ok"} 16

17 W3C VISS (JLR) proposal Based on WS & JSON (no REST/DBUS) OAuth2 for AuthN+AuthZ Request base on VSS path [i.e. "Signal.Drivetrain.InternalCombustion Engine.RPM"] Signal Grouping [i.e. "Signal.Cabin.Door.*.IsLocked"] 17

18 Plan for 2017 Expert group F2F in Karlsruhe (April) ALS Japan (June) Basic Can Agent Automatic low level binding from OpenXC Low level to high level vector decoding/encoding Simple high level API Low level filtering Basic statistics Debugging capability Beta for W3C or VIWI API CES (hopefully before Xmas break) Code cleanup & bug fixes Demos: OBD2, tracking cloud demo, trace&debug 18

19 Plan for 2017 Expert group F2F in Karlsruhe (April) ALS Japan (June) Basic Can Agent Automatic low level binding from OpenXC Low level to high level vector decoding/encoding Simple high level API Low level filtering Basic statistics Debugging capability Beta for W3C or VIWI API CES (hopefully before Xmas break) Code cleanup & bug fixes Demos: OBD2, tracking cloud demo, trace&debug 19

20 Further Information Some References OpenXC ViWi AGL Download links AppFramework code AGL Signaling Benchmark AGL-2.0 Application Security Model 20