CPM-QE/ RCM
HARMAN BECKER AUTOMOTIVE SYSTEMS GMBH
2018-06-15 12:30:00
CONFIDENTIAL / ALL RIGHTS RESERVED
Regulatory Compliance Management
Manual Hermes
page 5 of 18
3
System Description
3.1.1
System features
The
HERMES
provides the following features:
Calls:
The different calls can either be triggered via Airbag interface (E-Call only), buttons or Headunit.
EU E-Call:
•
Emergency Call to the PSAP in Europe (112 eCall);
•
After call established, the backend pulls MSD via Inband
ERA Glonass E-Call:
•
Emergency Call to the PSAP in Russia
•
After call established, the backend pulls MSD via Inband
E-Call (none US):
•
Emergency Call to a Bosch eCall center
•
Before the call 2 SMS including the MSD are sent to backend. If fails, the backend does pull the MSD via inband
E-Call (US):
•
Emergency Call to a Verison eCall center
•
Before the call 2 messages (ATP) including the MSD are sent to backend. As soon call is connected, basic data is
send to backend via DTMF.
R-Call (none US)
•
Roadside / Workshop call to a Call center from Daimler
•
As soon the call is connected, the backend does pull the MSD via inband
R-Call (US):
•
Roadside / Workshop call to a Call center from Verison;
•
Before the call 2 messages (ATP) including the MSD are sent to backend. As soon call is connected, basic data is
send to backend via DTMF.
I-Call (none US):
•
Information call to a Call center from Daimler (none US)
•
As soon call is connected, basic data is send to backend via DTMF.
I-Call (US):
•
Information call to a Call center from Verison (US)
•
As soon call is connected, basic data is send to backend via DTMF.
LTE Network in US (VoIP calls)
LTE / UMTS / GSM Network in non US countries (circuit switched calls)
Internal Communication to HeadUnit (in car communication)
HERMES acts as a “modem” for the headunit. It provides internet access and is routing data from external network to HU
WIFI 2.4 GHz and 5 Ghz (Only as client, For status and triggers a special protocol (WLAN Connectivity Control) is used)
BT (DUN)
The Headunit communicates via HERMES within a VPN tunnel or SSL secured with the Daimler backend. Traffic from/to HU is
not accessable by HERMES. Firewall rules are setup to secure that routing.
HERMES communicates to the Backend via a secured SSL connection (TLS). Therefore, an initial certificate is stored on
HERMES. HERMES does a certificate exchange (Certificate Exchange Protocol) with the Daimler backend to get a regular
certificate (unique for each device). As soon HERMES got a regular certificate, IP functionality is available for other
components (internal communication, backend communication, HU traffic).
HERMES is IPv4 Only
Telematic features:
The Telematic features are controlled via a proprietary protocol (Advanced Telematics Protocol). To enable/trigger a feature,
a SMS is send from backend to HERMES. HERMES verifies this message based on a SMS key (calculated during CEP), time
and other values. Then the command is executed. The result is most likely send via HTTP, as fallback there is SMS. Telematic
features are enabled over the air by service authorisation based on market needs.
These below telematics features are not testable without proper registration at Daimler backend and car environment!
