V1.2 | 2019-04-03

Concept for CANoe in the Cloud

Testing of Connected Functions

2

1. CANoe Simulation Approach

2. Concept: CANoe-in-the-Cloud

3. Integration and Testing Approach

4. Conclusion

Agenda

3

Classic World with Classic Networks

CANoe Simulation Approach

SUTECU

2

ECU3

real real

sim

SUT

ECU2

ECU3

real

simsim

CANoe

CANoe

Simulate the “needed” environmenthere: model ECU2 and simulate rather than integrate the real ECU2

High coverage of system states possible

Variants can be simply supported in one model (“150% model”)

Less complex

> Only aspects which are really needed in actual context – which is often rather simple

No special embedded SW needed (for ECU2)

> Which often has to have a specific patch/version

> Which causes a lot of effort to maintain and deploy

> Where right version of SW needed

No extra harness which is error prone

Can be debugged

CANoe approach:

Simulate the whole “Remaining” System

Environment

TESTS

TESTS

4

Connected SUTs - Analogy from Classic World

CANoe Simulation Approach

SUTF1

ECU3 – F3

real

sim

SUTF1

Backend (BE) F2

ECU3 F3

real

simsim

CANoe

Simulate the needed environment here: model the backend function F2 and simulate

Advantages: see previous slide

Backend (BE) F2

real

90%

TESTSTESTS

CANoe

5

1. CANoe Simulation Approach

2. Concept: CANoe-in-the-Cloud

3. Integration and Testing Approach

4. Conclusion

Agenda

6

CANoe-in-the-Cloud(a) tunnel only, (b) with model

System Overview

Concept: CANoe-in-the-Cloud

Functional System

COM-Module

(Wifi, xG, BT, …)

SUT

“Connected” IFClassic IF

CANoe (on-PC) - Client

Classic Access: CAN, LIN, ETH, I/O, …

CANoe-in-the-Cloudtunnel only or with model

Pro

tocol IP

based

CANoe proprietaryIP based: HTTPS, WebSockets, …

Internet: 4G, 5G, ...

Instance 0001

Instance 0001

Instance 0002

MQTT,

HTTPS …

7

Connects to the SUT directly via Internet

Thus no specific IT policies required

However, SUT must connect to Vector cloud instead of real productive cloud

First Step: Provide tunnel from CANoe to connected SUT

Next Step: Parts of the CANoe models can be uploaded to CANoe-in-the-Cloud

Every CANoe client instance instantiates one CANoe-in-the-Cloud instance

Properties

Concept: CANoe-in-the-Cloud

8

System Architecture

Concept: CANoe-in-the-Cloud

9

Certificate

Server

Docker Registry

Proxy Server

EC2

Tunnel

Server

Model

Network

Manager

CANoe

Mgmt

Server

Service Gate

Tunnel Admin

6

1

2

3

4

5

7

Create and rundocker containers

Pull docker containers

Create TCP/UDP connection

Forward TCP connection

Get endpoint based on port

Store configuration

Invoke shell via SSH

Get port configuration

Verify instance exists

Forward request

Forward tunnel connection

Request container creation

Request certificate creation

Store certificates

Cloud Part (Server) - Workflow

Concept: CANoe-in-the-Cloud

1

2

4

3

5

7 6

10

Cloud Part (Server) - Workflow

Concept: CANoe-in-the-Cloud

2

3

4

7 6

5

Certificate

Server

Docker Registry

Proxy Server

EC2

Tunnel

Server

Model

Network

Manager

CANoe

Mgmt

Server

1

Service Gate

Tunnel Admin

6

1

2

3

4

5

7

1

2

3

4

Create and rundocker containers

Pull docker containers

Create TCP/UDP connection

Forward TCP connection

Get endpoint based on port

Store configuration

Invoke shell via SSH

Get port configuration

Verify instance exists

Forward request

Forward tunnel connection

Request container creation

Request certificate creation

Store certificates

2

1

3

4

11

4

34

9

10

8

2 2 2 2

3

34

4

7

5

6

5

6

7

3

Certificate

Server

Docker Registry

Proxy Server

EC2

Tunnel

Server

Model

Network

Manager

CANoe

Mgmt

Server

1

11

Service Gate

1

Tunnel Admin

7

8

6

1

2

3

4

5

7

2

3

4

1

5

6

9

10

1

2

3

4

1

2

4

Create and rundocker containers

Pull docker containers

Create TCP/UDP connection

Forward TCP connection

Get endpoint based on port

Store configuration

Invoke shell via SSH

3 Get port configuration

Verify instance exists

Forward request

Forward tunnel connection

Request container creation

Request certificate creation

Store certificates

Cloud Part (Server) - Workflow

Concept: CANoe-in-the-Cloud

12

Tunnel IF & Management

Desk Part (Client)

Concept: CANoe-in-the-Cloud

Admin Tunnel(Tx commands)

Data Tunnel (Tx and Rx Data)

Concurrent Queue

<TunnelObject>

WebAccess

WSS Client

HTTPs Client

Concurrent Queue

<TunnelObject>

…

WebAccess

HTTPs Client

Cloud

Main, Create Instance,

etc…

13

1. CANoe Simulation Approach

2. Concept: CANoe-in-the-Cloud

3. Integration and Testing Approach

4. Conclusion

Agenda

14

Excursus: SUT - Differences in Test Focus

Integration and Testing Approach

Remaining classic buses

HU/Connectivity GW

…

f1

f2f3

BackendGW/DC ECU

HU/Connectivity GW

ECUSUT = One ECU (classic)

Focus

ECU as black box

Signals on classic networks

Remaining classic buses

HU/Connectivity GW

…

f1

f2f3

BackendRemaining

classic buses

HU/Connectivity GW

ECU

f2f3 f4

SUT = Distributed Function (new)→ f = f1 + f2 + f3 + f4

Focus

Software Interfaces

Service level

Function calls

Logical information flow

No ECU context

f1

15

Excursus: SUT - Differences in Test Focus

Integration and Testing Approach

Backendf4

ECUclassic

buses

HU/Connectivity GW

…

f1

f2

f3

f1

classic

buses

HU/Connectivity GW

…

f1

f2

f3

ECUf1

CANoe

CANoe

Backendf4

classic

buses

HU/Connectivity GW

…

f1

f2

f3

f2 f3

ECU

f1

CANoe

sim

sim

test

test

test

Opt. running in VTT or real

Same as in classic approach: Different levels of simulated and real parts of SUT

16

1. CANoe Simulation Approach

2. Concept: CANoe-in-the-Cloud

3. Integration and Testing Approach

4. Conclusion

Agenda

17

Conclusion

For ECU/function developers:

The typical CANoe simulation approach still applies

Possibility to model every aspect rather provide real parts

Bring in the real backed into your simulation

No specific requirements to IT infrastructure because of standardInternet access

The testing workflow stays the same

Even when we look more into SW testing rather than ECU testing

For backend developers:

Concentrate on the backend

All „automotive aspects“ are covered by CANoe

18

Thank you!

For a live demonstrator please visit booth in the exhibition area!

Any Questions?

19 © 2019. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.2 | 2019-04-03

Author:Neuffer, JochenVector Germany

For more information about Vectorand our products please visit

www.vector.com