Harman Becker Automotive Systems HERMES2 Users Manual

CPM-QE/ RCM

HERMES 2.0

(“Hardware for Enhanced Remote-, Mobility- & Emergency Services”)

Manual

CPM-QE/ RCM

CONTENTS

1 TECHNICAL DESCRIPTION ............................................................................... 3

1.1.1 Disclaimer................................................................................................................................... 3

2 INTRODUCTION HERMES ................................................................................. 4

3 SYSTEM DESCRIPTION ..................................................................................... 5

3.1.1 System features .......................................................................................................................... 5

3.1.2 Hermes Block Diagram ................................................................................................................ 7

3.1.3 Audio ......................................................................................................................................... 9

3.1.4 Diagnosis .................................................................................................................................. 10

3.1.5 Operating States ....................................................................................................................... 10

3.1.6 HW-clocking table ..................................................................................................................... 10

3.1.7 BT/WLAN Interface ..................................................................................................................... 3

3.1.8 Connectors ............................................................................................................................... 12

3.1.9 Pictures Hermes ........................................................................................................................ 13

4 DECLARATION OF CONFORMITY (DOC IN SHORT FORM) .............................. 14

4.1.1 English: .................................................................................................................................... 14

4.1.2 Bulgarian: ................................................................................................................................. 14

4.1.3 Spanish: ................................................................................................................................... 14

4.1.4 Czech: ...................................................................................................................................... 14

4.1.5 Danish:..................................................................................................................................... 14

4.1.6 German: ................................................................................................................................... 14

4.1.7 Estonian: .................................................................................................................................. 15

4.1.8 Greek: ...................................................................................................................................... 15

4.1.9 French: ..................................................................................................................................... 15

4.1.10 Croatian: .................................................................................................................................. 15

4.1.11 Italian: ..................................................................................................................................... 15

4.1.12 Latvian: .................................................................................................................................... 15

4.1.13 Lithuanian: ............................................................................................................................... 15

4.1.14 Hungarian: ............................................................................................................................... 15

4.1.15 Maltese: ................................................................................................................................... 16

4.1.16 Dutch: ...................................................................................................................................... 16

4.1.17 Polish: ...................................................................................................................................... 16

4.1.18 Portuguese: .............................................................................................................................. 16

4.1.19 Romanian: ................................................................................................................................ 16

4.1.20 Slovak: ..................................................................................................................................... 16

4.1.21 Slovenian: ................................................................................................................................ 16

4.1.22 Finnish: .................................................................................................................................... 17

4.1.23 Swedish: .................................................................................................................................. 17

5 FCC COMPLIANCE STATEMENT, USA............................................................... 18

6 ISED COMPLIANCE STATEMENT, CANADA ...................................................... 18

CPM-QE/ RCM

1 Technical Description

1.1.1 Disclaimer

The information contained in this document is the proprietary information of Harman Becker Automotive Systems GmbH (HBAS) in the Connected Car Division of HARMAN.

The contents are confidential and any disclosure to persons other than the officers, employees, agents or subcontractors of the owner or licensee of this document, without the prior written consent of HBAS, is strictly prohibit.

HBAS makes every effort to ensure the quality of the information it makes available. Not withstanding the foregoing, HBAS does not make any warranty as to the information contained herein, and does not accept any liability for any injury, loss or damage of any kind incurred by use of or reliance upon the information.

HBAS disclaims any and all responsibility for the application of the devices characterized in this document, and notes that the application of the device must comply with the SAFETY standards of the applicable country, and where applicable, with the relevant wiring rules.

HBAS reserves the right to make modifications, additions and deletions to this document due to typographical errors, inaccurate information, or improvements to programs and/or equipment at any time and without notice. Such changes will, nevertheless be incorporated into new editions of this document.

Copyright: Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibit. Offenders will be helt liable for payment of damages. All rights are reserved.

CPM-QE/ RCM

2 Introduction HERMES

The project name HERMES has the meaning “Hardware for Enhanced Remote-, Mobility- & Emergency Services” and thus describes the main features of this device. This unit was designed for

automotive usage and contains the following features: GSM, UMTS, LTE , USB, Bluetooth, Wireless LAN.

It provides different telematic services and is the interface between different types of Daimler car headunits and the public network. Therefore you can connect the headunit either over USB or BT or Wireless LAN with the HERMES Box and over GSM/UMTS/LTE it provides access to public network.

Due to the fact that Conectivity Box is used for different target markets we provide different versions that will support different GSM/UMTS/LTE-bands – depending on the target markets.

The Hermes unit will be used as gateway module for different Daimler Entry and High platforms.

CPM-QE/ RCM

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);

•

ERA Glonass E-Call:

E-Call (none US):

E-Call (US):

R-Call (none US)

R-Call (US):

After call established, the backend pulls MSD via Inband

•

Emergency Call to the PSAP in Russia

•

After call established, the backend pulls MSD via Inband

•

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

•

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.

•

Roadside / Workshop call to a Call center from Daimler

•

As soon the call is connected, the backend does pull the MSD via inband

•

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)

•

I-Call (US):

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!

As soon call is connected, basic data is send to backend via DTMF.

• Information call to a Call center from Verison (US)

•

As soon call is connected, basic data is send to backend via DTMF.

CPM-QE/ RCM

Remote Diagnostics:

•

Run internal scripts for diagnosis of other components in the car and sent back diagnosis results to the Daimler

Remote Door Lock/Unlock:

•

Flash Lights Sound Horn:

POI/Route Download:

Freetext (with URL/Phone#):

Geofencing:

Speed Alert:

Remote Update:

Vehicle Remote Start (only US):

Auxiliary Heating:

Preconditioning (Electric Vehicle)

Departure Time and Charge Optimization (Electric Vehicle)

DataCollector, RCS:

Lock/Unlock door via customer app and backend.

•

Flash Lights Sound Horn via customer app and backend.

•

Sent POI/Route via customer app and backend.

•

Sent Freetext via backend. Only possible for call centers.

•

Notification of customer of geofence violations. Setup is done via customer homepage or app.

•

Notification of customer of speed violations. Setup is done via customer homepage or app.

•

HERMES can update itself via OMA-DM

•

HERMES can start the engine with a special workflow initiated by backend or customer app.

•

HERMES can enable Auxiliary Heating via ATP

•

HERMES can enable Preconditioning via ATP

•

HERMES can set Departure time and other EV settings via ATP

•

For several telematic features CAN signals are needed by the backend to show a status or check the state of different conditions. The DataCollector collects the signals based on enabled features and sents them to the backend (Remote Customer Support) on time or signal based triggers.

backend.

+ 12 hidden pages

Harman Becker Automotive Systems HERMES2 Users Manual

Specifications and Main Features

Frequently Asked Questions

User Manual