“Service-Oriented Gateway: Connecting Automotive Ethernet

2020 IEEE-SA Ethernet & IP @ Automotive Technology Day

“Service-Oriented Gateway:

Connecting Automotive Ethernet and Cloud

for Efficient Development of Connected Car Services”

Wonseon SimHyundai Motor Group

Seung Jun LeeAirPlug, Inc.


Contents Service-oriented Gateway

• End-to-End Service-oriented Architecture

• External Connectivity : Challenges & Approach

• Structural Concept

• Software Architecture

Features of Service-oriented Gateway

• Protocol Conversion – Service Communication

• Protocol Handling – Service Discovery

• Edge Processing

• Policy & Access Control

• Network Utilization

Connected Car Service Example

• Door Control Service

• Emergency Alarm Service

Concluding Remarks


Service-oriented Gateway• End-to-End Service-oriented Architecture

• External Connectivity : Challenges & Approach

• Structural Concept

• Software Architecture


End-to-End Service-oriented Architecture

End-to-End Service-oriented Architecture

• Extended Service-level Transparency and Integrated Service Design

CANIFC

SoAAdaptor

Ethernet

Services & Consumers Service-

orientedGateway

Ext.NWIFC

CloudFunctions

Ethernet-based IVN External NetworksLegacy IVN

External Function& Information

Legacy Function& Information Service Communication

End-to-End Service-level Transparency

Service ExternalConversion

Legacy ServiceConversion

ServiceRegistry


External Connectivity : Challenges and Approach

External Devices on External Network• Vehicle needs to interwork with external devices like cloud servers and smart devices.

• Interworking need gets much larger for ADAS and other connected car services.

• External networks have very different characteristics compared to IVN

: availability, bandwidth, latency, cost, etc.

• Application Protocols for external connectivity are usually different from those for IVN in general.

• High-risk security issues when interworking through external networks.

Service-oriented Gateway

• Handles issues related with external device/network interworking.

• Converts Application Protocols and Translates Services.

• Caches external information to deal with availability & cost issues of external networks.

• Applies Policy and Performs Service-level Access Control.

• Should be implemented on ECU with external connectivity.


Structural Concept

Structural Concept of Service-oriented Gateway Interworking with Cloud Functions & Services• In-vehicle Service Applications use Data/Functions from Cloud

• Cloud uses Data/Functions provided by In-vehicle Service Applications

Ext. NW.

Interface

Ethernet Switch

TCP/IPAut. Ethernet

High Performance ECUwith External Network Interface

Consu. App

TCP/IPAut. Ethernet

SOME/IP

Other In-vehicleECU’s

Service

• Location• Veh. speed

• Get_RoadCond• Get_WeathFcst

CloudFunctions

&Services

• RoadCond• WeathFcst

• Get_Loc• Get_Speed

Cloud Servers

Service-oriented

G/WServiceConsu.

App

SOME/IP

Service Domain External Domain

※ Cloud Service

※ In-Vehicle Service


Software Architecture


SOME/IP

TCP/IP

MappingInfo.

Parser

Data Processing

Mapping Info.

Service I/F

Svc. Prov. Service Translation & Protocol Conversion

caching

DataHandlingManager

IVN(Ethernet)

Service-oriented G/W relays information between External Devices and In-Vehicle ECU’s• With external devices: HTTP/MQTT/SMS depending on communication pattern

• With in-vehicle ECU’s: Service-oriented communication based on SOME/IP

Cloud Servers

Policy & Control

MQTT HTTP SMS

External Network(Cellular, WiFi, Bluetooth)

Svc. Cons.Policy

In-Vehicle ECU’s


Features of Service-oriented Gateway• Protocol Conversion – Service Communication

• Protocol Handling – Service Discovery

• Edge Processing

• Policy & Access Control

• Network Utilization


Protocol Conversion: Service Communication

Two-way Communication : Vehicle Origination• Service Consumer makes method requests to G/W and the requests are relayed to External Networks

using HTTP.

Cloud(Server)

ServiceApplication(Consumer)

Service Interface

(1) Method Call

(4) MethodResponse

(2) Request

(3) Response

Server Comm. Protocol

Service-oriented Gateway(Service Provider)

Method Request Request to Cloud

Method Response Response from Cloud

Mapping

SOME/IP HTTP (SMS)



Two-way Communication : Vehicle Termination• After receiving requests from Cloud, G/W makes corresponding method calls to an appropriate

Service Provider and relays the responses to Cloud

Cloud(Server)

ServiceApplication(Provider)

Service Interface

(2) Method Call

(3) MethodResponse

(1) Request

(4) Response


Service-oriented Gateway(Service Consumer)

Method Request Request from Cloud

Method Response Response to Cloud

Mapping

SOME/IP MQTT / SMS



One-way Communication : Vehicle Origination• Service Provider fire an event to G/W and then G/W relays the event data to Cloud using HTTP

• To facilitate communication with In-vehicle ECU, G/W utilizes SOME/IP SD to subscribe to events

Cloud(Server)

ServiceApplication(Provider)

Service Interface

(1) Event (2) Publish


Service-oriented G/W(Service Consumer)

Event Publish Message to Cloud

Mapping

SOME/IP HTTP (SMS)

(0) Subscribe

(0) Subscribe ACK

(0) Offer



One-way Communication : Vehicle Termination• G/W relays data from Cloud to In-vehicle ECU’s as event notification

Cloud(Server)


Service Interface

(2) Event(1) Publish


Service-oriented Gateway(Service Provider)

Event Publish Message from Cloud

Mapping

SOME/IP MQTT / SMS

(0) Subscribe

(0) Subscribe ACK

(0) Offer



External Connection Status is mapped to corresponding Service Domain Behavior• Example

- In case of unstable network or busy server: Retry Server Connection (NOT_OK if Time out)

- In case of no available network : Respond with NOT_OK


CloudService

Application(Consumer)

Network Unstable


CloudService


No Available Network

X

Method Call

NOT_OK (Time Out)

Method Call

Try Server Connection & Make a Request

…Time Out

NOT_OK (No N/W)


Protocol Handling: Service Discovery

G/W performs Service Discovery for service-oriented communication with In-vehicle ECU’s• Uses SOME/IP SD Protocol

• Adaptive Operation Timing and Behavior Modes in accordance to External Network status

Service-orientedGateway

CloudService


Connection OK


CloudService


Disconnected

X


CloudServiceApplication(Consumer)

----- Connecting -----

Subscribe

Subscribe ACK

Offer Service

Offer Service

X

Subscribe

Subscribe NACK

Offer Service

(Example)


Edge Processing

Caching Responses from External Networks• Prevents unnecessary excessive connections to external networks

• Improves Responsiveness & Reduces Network Cost

ServiceConsumer

#2

Request

Cloud


ServiceConsumer

#1 ResponseResponse

cache

Request

Response

XX

GetWeatherInfo { }

GetWeatherInfo { }


Edge Processing

Filtering & Aggregation• Relays less data and less frequently to Cloud than received from in-vehicle ECU’s

• Performs Period-based or Contents-based Filtering

• Aggregates Multiple Events from One or Several Service Applications

• Reduces Communication loads and Network costs


CloudServiceApplication

Event (every 10ms)10ms

Publish (every 10sec)

or

Publish (only if significant change)

…


Cloud

ServiceApplication A

Event_A1

…

ServiceApplication B Event_B Publish

{ Event_A1, Event_A2, Event_B}

Event_A2


Policy & Access Control

Service-level Access Control• Access Control at Service Level or Service Element Level (e.g., for each method or event)

• Access Control Policy can be applied Statically or Dynamically from Cloud

Operation Policy• Policy can be applied for other G/W operations like Filtering, Caching, and Network Mapping.

Service-oriented Gateway Cloud


Disable Method A1Method A1 Call

NOT_OK(Not Authorized)



Subscribe A2

Subscribe NACK

Stop Offer

Policy

Cloud

Disable Event A2or

Disable Service A

Policy


Connected Car Service Example• Door Control Service

• Emergency Alarm Service


SoA Adaptor


Remote Door Control Function

• Utilizes existing “Door Control Service” provided by SoA Adaptor


Cloud

Door ControlService

Consumer

DoorControlService

Service Name Service Interface Argument Direction G/W Acts as External Protocol

Door Control Request & ResponseDoor Position (FL/FR/RL/RR)

Target Status (Lock/Unlock)

Vehicle

TerminationService

ConsumerMQTT

SwitchControl

Application

Motion Control

Application

Voice ControlApplication


SoA Adaptor


Airbag Activation Alarm Function

• Utilizes existing “Emergency Alarm Service” provided by Service-oriented G/W


Cloud

Service Name Service Interface Argument Direction G/W Acts as External Protocol

Emergency Alarm Request & ResponseCurrent Position

Alarm Reason

Vehicle

OriginationService

ProviderHTTP

AirBag StatusService

Position Service

SwitchControl

Application

AutomaticEmergencyApplication

EmergencyAlarm

ServiceProvider


Concluding Remarks

• SoA can be extended to End-to-End from legacy ECUs to Cloud.

• Service-oriented G/W can be introduced for efficient SoA extension to Cloud.

• It enables in-vehicle S/W to interact with Cloud in a service-oriented way.

• It efficiently handles external-network related issues like availability, delay, cost, and security,

by performing protocol conversion, caching, filtering, network mapping, and access control.

• Its operation can be dynamically controlled as defined in the policy from Cloud.

• With SoA Adaptor and Service-oriented G/W, new connected car services can be developed

and deployed with least time and effort.

Documents

“Service-Oriented Gateway: Connecting Automotive Ethernet