Vehicle capable of wirelessly exchanging data between a computing unit and a mobile device

Abstract

The invention relates to a vehicle (1) having at least two computing units (SG, KG) with a direct communication link to each other or an indirect communication link to each other over Ethernet. Data traffic to be wirelessly exchanged between a second computing unit (KG) and a mobile device (MG) can be processed by a first computing unit (SG). The vehicle according to the invention is characterized in that - the first computing unit (SG) comprises a Bluetooth transceiver (2) and is designed to communicate with the mobile device (MG) using Bluetooth; and - the first computing unit (SG) and the second computing unit (KG) are each designed to exchange information with one another via an Ethernet data line (3) using the SOME / IP protocol, wherein - the second computing unit (KG) is designed to transmit a Bluetooth configuration to the first computing unit (SG) using at least one application programming interface, the Bluetooth configuration comprising a configuration for a Bluetooth service to be carried out between the second computing unit (KG) and the mobile device (MG); - the first computing unit (SG) is designed to receive the Bluetooth configuration and to provide the Bluetooth service for the second computing unit (KG) and the mobile device (MG), thereby configuring the Bluetooth transceiver (2) using the Bluetooth configuration; and - the second computing unit (KG) and the mobile device (MG) are designed to use the Bluetooth service while a first processing is carried out by the first computing unit (SG).

Description

[0001] Mercedes-Benz Group AG

[0002] Vehicle with the capability for wireless data exchange between a computing unit and a mobile device

[0003] The invention relates to a vehicle of the type defined in more detail in the preamble of claim 1.

[0004] Providing services via computer systems can require data exchange between multiple computer systems. This data exchange can be wired or wireless. A wide variety of communication protocols are known. For example, the control units in a vehicle can exchange information via a fieldbus system such as CAN, Ethernet, and similar protocols, while mobile devices can exchange data via Wi-Fi or Bluetooth. It is also known to connect mobile devices to a vehicle, for which Bluetooth can also be used. This allows, for example, a vehicle user to read audio files such as MP3s from a computer-readable storage medium on the mobile device and then play the audio file through the vehicle's sound system.

[0005] Modern vehicles can also be capable of at least semi-automated driving. Steering, acceleration, and braking maneuvers can be performed by the vehicle itself. This enables the use of parking assistants. The vehicle determines a trajectory for parking in a space and drives along it as needed. If the parking space is particularly tight, the driver can exit the vehicle using a remote parking assistant and control the automated parking process remotely via a mobile device such as a smartphone connected to the vehicle.

[0006] Typically, the hardware and software required for Bluetooth communication are implemented in the same computing unit that uses the corresponding Bluetooth service. Referring back to the previous example, the control unit for the remote parking assistant—that is, the computing unit used to issue control commands to the vehicle—has its own Bluetooth module for communication with the smartphone. This approach has several disadvantages.

[0007] Thus, every computing unit that provides a Bluetooth-based service must have its own Bluetooth module. Such a Bluetooth module, also known as a Bluetooth transceiver or Bluetooth receiver, includes the means for receiving and transmitting Bluetooth signals. This increases the complexity of the hardware installed in the vehicle, which also leads to higher manufacturing costs. Furthermore, the need for multiple redundant Bluetooth modules is generally eliminated, as typically only one mobile device is paired with the vehicle at a time. The functionalities provided by vehicles are becoming increasingly complex, necessitating the integration of more powerful hardware components. This, in turn, leads to an increase in energy consumption and the dissipation heat emitted by these hardware components.Due to the limited installation space available in the vehicle, electronic components can be affected by the heat dissipation from nearby components. It is therefore desirable to utilize the available installation space in the vehicle more efficiently.

[0008] US patent 2016 / 0050269 A1 discloses a data system in a vehicle that uses publish / subscribe gateways for data exchange. The patent describes a network interface integrated into a vehicle that is capable of communication over a wide area network (WAN). Within the vehicle, sensors can be connected to a mobile gateway via Ethernet through a sensor control unit. The mobile gateway can thus receive sensor data over an Ethernet data line. The mobile gateway establishes a wireless communication link to a client device. The sensor data can be transmitted to the client device via the mobile gateway using the wireless communication link, specifically a Wi-Fi connection.

[0009] The present invention aims to provide a vehicle with an improved system architecture. According to the invention, this objective is achieved by a vehicle with the features of claim 1. Advantageous embodiments and further developments are described in the dependent claims.

[0010] A vehicle of this type, comprising at least two computing units that are in communication with each other directly or indirectly via Ethernet, wherein the data traffic to be exchanged wirelessly between a second computing unit and a mobile device can be handled via a first computing unit, is further developed according to the invention in that

[0011] - the first computing unit includes a Bluetooth transceiver and is set up to communicate with the mobile device using Bluetooth;

[0012] - the first computing unit and the second computing unit are each configured to exchange information with each other via an Ethernet data line using the SOME / IP protocol; wherein

[0013] - the second computing unit is configured to transmit a Bluetooth configuration to the first computing unit using at least one application programming interface, wherein the Bluetooth configuration includes a configuration for a Bluetooth service to be handled between the second computing unit and the mobile device;

[0014] - the first processing unit is configured to receive the Bluetooth configuration and, by configuring the Bluetooth transceiver with the Bluetooth configuration, to provide the Bluetooth service to the second processing unit and the mobile device; and

[0015] - the second computing unit and the mobile device are set up to use the Bluetooth service under processing by the first computing unit.

[0016] The vehicle according to the invention is characterized by an improved system architecture compared to the prior art. The vehicle has the aforementioned first computing unit, which serves to provide a Bluetooth interface between other computing units of the vehicle and corresponding mobile devices. Thus, not only one second computing unit, but also several second computing units can be connected to the first computing unit. This allows for an efficient system design, since it is no longer necessary to have a separate Bluetooth transceiver for each computing unit that relies on a Bluetooth service. This reduces power consumption and heat dissipation caused by heat loss. The available installation space in the vehicle can be used more efficiently. The Bluetooth transceiver, or...This allows the first processing unit to be positioned far away from strong heat sources, thus preventing or at least delaying thermal damage to electronic components. This increases the reliability and lifespan of the corresponding electronic components.

[0017] Using Scalable Service-Oriented Middleware over IP (SOME / IP), efficient and reliable data transmission between the respective computing units in the vehicle is possible. The first computing unit establishes a communication link between the second computing unit and the mobile device and can also be referred to as the server device in this context. The second computing unit uses the Bluetooth-based communication services offered by the first computing unit and can also be referred to as the client device in this context. All types of mobile devices are eligible as mobile devices, such as smartphones, tablet computers, wearables, laptops, and the like.

[0018] A Bluetooth transceiver comprises a transmitter and a receiver for radio signals that conform to the Bluetooth standard. Such a Bluetooth transceiver can also be called a Bluetooth adapter or Bluetooth module. Specifically, the Bluetooth transceiver can be manufactured in the form of a chip. To use the Bluetooth transceiver, suitable software in the form of a driver is required. Several programs serving a common purpose, or the underlying program code, are also referred to as a "stack." Accordingly, a processor of the first processing unit has at least one read access to a computer-readable storage medium containing the corresponding computer program. By executing this computer program, or the underlying driver / stack, the processor of the first processing unit enables the first processing unit to provide the aforementioned Bluetooth service.The first processing unit receives the necessary information for configuring the Bluetooth transceiver and / or Bluetooth service from the second processing unit via the application programming interface (API). This enables a reliable, secure, and automated process between the two units. Furthermore, the approach to providing Bluetooth services is particularly flexible. The second processing unit can configure the Bluetooth transceiver using the Bluetooth configuration, depending on the requirements of the Bluetooth service usage. In previously known system architectures, each processing unit has its own Bluetooth transceiver, which necessitates a static configuration of the respective Bluetooth services.According to the invention, the second processing unit is able to adapt the Bluetooth configuration depending on the application scenario, thus enabling flexible adaptation to new Bluetooth-based services. This allows new functionalities to be implemented gradually.

[0019] Decoupling the communication layer from the vehicle's core system enables modularity and scalability of the vehicle's integrated information technology system. This allows for optimized resource utilization within the vehicle and facilitates the efficient integration of various system architectures.

[0020] A dynamic configuration of the Bluetooth transceiver is therefore proposed, which requires the implementation of robust service discovery. Using the SOME / IP framework to manage the communication pipeline between the first and second computing units, it is possible to provide such robust service discovery.

[0021] An advantageous embodiment of the vehicle according to the invention provides that the first computing unit is configured to transmit a service summary to the second computing unit via the Ethernet data line, comprising a description of the Bluetooth services that the first computing unit can provide. Thus, the first computing unit is able to inform the second computing unit(s) which Bluetooth services are available. This, in turn, allows the second computing unit to decide whether a Bluetooth service should be used and, if so, how the Bluetooth transceiver of the first computing unit must be configured to use that Bluetooth service.

[0022] According to a further advantageous embodiment of the vehicle according to the invention, the first computing unit is configured to output the service summary in the form of a broadcast message during the initialization process and / or a broadcast request issued by the second computing unit. The service summary can thus be transmitted via the Ethernet data line using SOME / IP as a broadcast message to all second computing units communicatively connected to the first computing unit. This can occur either during the initialization process, i.e., when the first computing unit is started, or during operation. The first computing unit can, for example, retransmit the broadcast message at fixed time intervals or after the occurrence of an event. Such an event could be the issuance of a broadcast request by the second computing unit.The second processing unit can then transmit a corresponding Bluetooth configuration to the first processing unit via the aforementioned API. This can also occur during runtime, allowing the Bluetooth configuration to be adapted as needed. This enables a flexible response to changing operating conditions. This underscores the flexibility of the system integrated into the vehicle.

[0023] A further advantageous embodiment of the vehicle according to the invention provides that the Bluetooth transceiver in the first computing unit is integrated with a Wi-Fi transceiver into a common communication module, in particular integrated on a common circuit board. This enables the first computing unit to facilitate communication between the vehicle's integrated information technology system and external computer systems not only via Bluetooth but also via Wi-Fi. The first computing unit comprises a communication module that includes both a Bluetooth transceiver and a Wi-Fi transceiver. Such combined communication modules are widely available as standard components, allowing for cost-effective and reliable integration of both wireless data transmission technologies.This eliminates the need to include additional Wi-Fi transceivers in other computing units in the vehicle, further reducing manufacturing costs.

[0024] The vehicle can be any road vehicle such as a car, truck, van, bus, or the like. It could also be a rail vehicle, watercraft, or aircraft. Further advantageous embodiments of the vehicle according to the invention will also become apparent from the exemplary embodiments, which are described in more detail below with reference to the figures.

[0025] This shows:

[0026] Fig. 1 is a schematic top view of a vehicle according to the invention, performing an automated parking operation;

[0027] Fig. 2 shows a schematic representation of the components involved in using a Bluetooth service; and

[0028] Fig. 3 shows a detailed representation of a first and second computing unit of the vehicle according to the invention, showing a software layer structure.

[0029] Figure 1 shows a top view of a vehicle 1 according to the invention, which performs an automated parking maneuver into a parking space 6. The vehicle 1 according to the invention is remotely controlled via a mobile device MG, for example, in the form of a smartphone. The mobile device MG is operated by a user 7. The mobile device MG is paired with the vehicle 1 via Bluetooth. Control commands for the automated parking maneuver are issued by a second processing unit KG, where KG stands for "client device". The second processing unit KG is connected to the mobile device MG via a first processing unit SG, where SG stands for "server device". The mobile device MG and the first processing unit SG exchange information via Bluetooth.The second computing unit KG and the first computing unit SG exchange information via an Ethernet data line 3, which is shown in Figure 2, using the “Scalable Service-Oriented Middleware overlP” (SOME / IP) protocol.

[0030] Figure 2 shows a simplified representation of the system architecture. The mobile device MG, the first computing unit SG, the second computing unit KG, and the Ethernet data line 3 are visible. Additional second computing units, not shown in detail, may be present; these are indicated in Figure 2 by several dotted lines. Figure 2 also shows a simplified representation of the software implemented on the first and second computing units SG and KG. Box 201 represents software for providing an application, also referred to as an application or app. Box 202 represents software or a stack for using the SOME / IP protocol. Box 203 represents software implemented in the operating system for data exchange over a network, such as drivers.The first computing unit SG is additionally characterized by software 204, which is intended for use with a Bluetooth transceiver 2 shown in Figure 3, i.e. a “Bluetooth stack”.

[0031] Figure 3 illustrates in detail the structure of the first computing unit SG and the second computing unit KG. The first computing unit SG and the second computing unit KG are similar in structure. Both computing units include Hardware 301, which serves to provide the physical layer, also known as the "Physical Hardware Layer" (PHY), of the OSI model.

[0032] Indicated by box 302 is an Ethernet connection along with the software required for its operation. Above this, indicated by box 303, is the so-called network stack of the operating system of the second computing unit, KG. The network stack serves to provide network layer L2 of the OSI model, also known as the "Network Layer," and includes an inter-process communication stack. A routing manager 304 can be configured with a client network configuration 305. Also shown are a "Local End Point" 306 and various protocol examples such as TCP / UDP and IPv4 / IPv6.

[0033] Above this is the so-called SOME / IP stack 307, which in turn contains common API core generated code 308, also known as "Common API Core Generated Code". Also included are the common API core runtime 309, also known as the Common API Core Runtime, the common API binding runtime 310, also known as the Common API Binding Runtime, and the corresponding common API binding generated code 311, also known as "Common API Binding Generated Code".

[0034] The corresponding program code can be automatically generated by a common API core code generator 312 and a common API binding code generator 313, also known as a "Common API Binding Code Generator". The modules contained in the SOME / IP stack 307 are shared by the second computing unit (KG) and the first computing unit (SG), or rather, they interact with each other. The SOME / IP stack 307 forms the so-called L3 middleware layer of the OSI model.

[0035] Above this is the so-called "client application" 314, which represents the so-called "application layer" L4 of the OSI model.

[0036] The first and second computing units SG and KG communicate via the aforementioned Ethernet data line 3. Otherwise, the setup of the first and second computing units SG and KG is almost identical, with the routing manager 304 of the first computing unit SG being configured via a server network configuration 315. Furthermore, a so-called server application 316, also referred to as a "server application", is executed on the first computing unit SG.

[0037] The first processing unit SG acts as an intermediary between the second processing unit KG and the mobile device MG using a Bluetooth connection. For this purpose, the first processing unit SG includes a Bluetooth transceiver 2, which is preferably integrated with a Wi-Fi transceiver 4 into a common communication module 5. The Bluetooth transceiver can be a solution integrated on a single chip. A Bluetooth stack 317 is required for the operation of the Bluetooth transceiver 2. This stack comprises a controller 318 and a host 319. These can be connected via a layer that can be referred to as HCL (not shown). The controller 318 can include a link layer and a physical layer (PHY). The host 319 has various protocols such as GATT, ATT, SMP, GAP, and the like, as well as an L2CAP layer.

[0038] Above that is a so-called D-Bus 320. Above that, in turn, is the so-called Bluetooth Stack API adapter 321.

[0039] SOME / IP is a middleware protocol that operates above the network layer of the OSI model. SOME / IP integrates the network layer, particularly within the context of operating systems such as Linux. SOME / IP is designed to work with the operating system's standard IP stack. In the case of Linux, this is the TCP / IP stack, which is part of the kernel. SOME / IP can use either TCP or UDP as its transport layer protocol. TCP provides reliable, orderly, and error-checked transmission of data streams, making it suitable for services requiring high reliability. UDP, on the other hand, is used for services that require low latency and allow for a certain degree of packet loss.

[0040] At the network layer (L2), IP is used to route SOME / IP messages across network boundaries. The IP layer ensures that some SOME / IP packets are encapsulated within IP packets and correctly addressed before being sent to their destination. SOME / IP encapsulates its messages within the so-called "payload," either within TCP or UDP packets. This encapsulation is transparent to the network layer, which uses SOME / IP messages as the data to be transported. SOME / IP includes mechanisms for service discovery and service binding. These are typically managed by the service layer above the network layer. Service discovery allows devices to find dynamically provisioned services within the network, while service binding establishes a communication link between the client and the service.

[0041] As middleware, SOME / IP provides an abstraction layer between the 314 application and the network layer L2. This allows 314 applications to communicate with each other over the network without having to deal with the complexity of the underlying network protocol.

[0042] In an operating system like Linux, SOME / IP is often integrated into the operating system's network subsystem via a so-called daemon or service that interacts with the kernel of the network stack. This integration allows SOME / IP to manage communication sessions, message serialization / de-serialization, and / or protocol-specific functions.

Claims

Mercedes-Benz Group AG Patent claims 1. Vehicle (1) comprising at least two computing units (SG, KG) that are in communication connection with each other directly or indirectly via Ethernet, wherein the data traffic to be exchanged wirelessly between a second computing unit (KG) and a mobile device (MG) can be handled via a first computing unit (SG), characterized in that - the first computing unit (SG) includes a Bluetooth transceiver (2) and is set up to communicate with the mobile device (MG) using Bluetooth; - the first computing unit (SG) and the second computing unit (KG) are each configured to exchange information with each other via an Ethernet data line (3) using the SOME / IP protocol; wherein - the second computing unit (KG) is configured to transmit a Bluetooth configuration to the first computing unit (SG) using at least one application programming interface, wherein the Bluetooth configuration includes a configuration for a Bluetooth service to be handled between the second computing unit (KG) and the mobile device (MG); - the first processing unit (SG) is configured to receive the Bluetooth configuration and, by configuring the Bluetooth transceiver (2) with the Bluetooth configuration, to provide the Bluetooth service to the second processing unit (KG) and the mobile device (MG); and - the second computing unit (KG) and the mobile device (MG) are set up to use the Bluetooth service under processing by the first computing unit (SG).

2. Vehicle (1) according to claim 1 , characterized in that the first computing unit (SG) is configured to transmit a service summary via the Ethernet data line (3) to the second computing unit (KG), comprising a description of the Bluetooth services that can be provided by the first computing unit (SG).

3. Vehicle (1) according to claim 2 characterized in that the first computing unit (SG) is configured to output the service summary in the form of a broadcast message during the initialization process and / or a broadcast request issued by the second computing unit (KG).

4. Vehicle (1) according to one of claims 1 to 3, characterized in that the Bluetooth transceiver (2) in the first computing unit (SG) is integrated with a Wi-Fi transceiver (4) in a common communication module (5), in particular integrated on a common circuit board.

Images