Method for the dynamic, vehicle-specific control of a navigation system
Patent Information
- Application Number
- DE102017218094
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2017-10-11
- Publication Date
- 2025-03-20
- Estimated Expiration
- 2037-10-11
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The present invention relates to a method for dynamic, vehicle-specific control of a navigation system.
[0002] Navigation systems for vehicles, particularly motor vehicles, are well known. They allow the vehicle user to define a destination to which they wish to travel. After entering the destination, an optimal route to the entered destination is calculated, depending on the user's personal settings. Furthermore, it is known to display specific destinations as so-called "Points of Interest (POIs)" and allow the vehicle user to select them. POIs include, for example, gas stations, parking lots, restaurants, supermarkets, certain tourist attractions, etc. However, it is not possible to automatically transfer a destination to the navigation system based on vehicle-specific parameters. DE 10 2013 208 130 A1 describes a system for transmitting data between a vehicle and a workshop.US 2013 / 0227648 A1 describes a diagnostic module for a vehicle that can determine a suitable workshop to repair the vehicle.
[0003] The object of the invention is to avoid the above-mentioned disadvantages and to provide a solution that enables automatic, dynamic, vehicle-specific control of the navigation system.
[0004] This object is achieved according to the invention by the features of the independent claims. Preferred embodiments are the subject of the dependent claims.
[0005] According to a first aspect of the invention, the object is achieved by a system for dynamic, vehicle-specific control of a navigation system in a vehicle, comprising: at least one backend server, wherein the backend server is configured - to receive a message comprising technical status parameters from the vehicle, wherein the technical status parameters comprise a vehicle identification number and at least one technical status of the vehicle to be changed; - to generate a response relating to the technical condition parameters, the response including a destination for use by the vehicle's navigation system; and - transmit the response to the vehicle.
[0006] The vehicle's navigation system includes a navigation module configured to provide route guidance. This can be implemented, for example, as on-board route guidance, where the relevant road maps are stored locally in the vehicle and the route to the entered destination is determined by an on-board navigation system.
[0007] The vehicle can further comprise a communications module. The communications module can be a communications module arranged in the vehicle which is capable of establishing a communications connection with other communications participants, for example with the backend server. The communications module can comprise a subscriber identity module or a SIM card, which serves to establish a communications connection via a mobile radio system. The subscriber identity module uniquely identifies the communications module in the mobile radio network. The communications connection can be a data connection (e.g. packet switching) and / or a wired communications connection (e.g. circuit switching). Any communication between the vehicle and other communications participants can take place via the communications module.
[0008] The user of the vehicle may be its owner and / or authorized driver of the vehicle.
[0009] The backend server is configured to receive messages from the vehicle and transmit or send corresponding responses or response messages to the vehicle. For example, the backend server can receive a request from the vehicle as a message in the sense of the client-server paradigm, generate a corresponding response as an answer and transmit or send this to the vehicle. Each message contains technical status parameters of the vehicle. The technical status parameters include at least a vehicle identification number (VIN) and at least one technical status of the vehicle that needs to be changed. With reference to the technical status parameters, the backend server creates the response, which contains a destination for use by the navigation system. The response is transmitted or sent from the backend server to the vehicle.The vehicle's navigation system can use the received destination to guide the vehicle to the destination.
[0010] The vehicle's message can include the vehicle's current position data, so that the vehicle's current position data is transmitted to the backend server. The vehicle's current position data can be determined using a navigation satellite system. The navigation satellite system can be any current or future global navigation satellite system or Global Navigation Satellite System (GNSS) for positioning and navigation by receiving signals from navigation satellites and / or pseudo-satellites. For example, this can be the Global Positioning System (GPS), GLObal NAvigation Satellite System (GLONASS), Galileo positioning system, and / or BeiDou Navigation Satellite System. For example, the vehicle can include a module suitable for detecting a vehicle's position in the respective system.In the example of GPS, the vehicle may include a position determination unit comprising a GPS module configured to determine the current GPS position of the vehicle. The determination of the GPS position of the vehicle may occur during driving operation at predefinable or predefined intervals, e.g., every 1 second (s), every 5 s, every 10 s, every 15 s, or any other suitable predefined event, for example, immediately before sending a message. For example, the navigation module may include the position determination unit. In another example, the navigation module and the position determination unit are separate modules.
[0011] The vehicle may include an input and output unit for one-time registration of a vehicle user on the backend server. During the one-time registration, certain data of the vehicle user, e.g., name, address, telephone number, driver profile data, etc., may be captured and stored in a storage unit. One-time registration of the vehicle user on the backend server (or another suitable server that provides this functionality) may be required before dynamic, vehicle-specific control of the navigation system in the vehicle can be provided via the backend server. The input and output unit may include a speech recognition module. Alternatively, the speech recognition module and the input and output unit may be separate components in the vehicle.
[0012] In addition or alternatively, the one-time registration can also be carried out via a stationary end device, such as a personal computer and / or a mobile device. A mobile device is a device that is capable of communicating wirelessly in a mobile network via local areas networks (LANs), such as wireless LAN (WiFi / WLAN), or via wide areas networks (WANs) such as Global System for Mobile Communication (GSM), General Package Radio Service (GPRS), Enhanced Data Rates for Global Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), High Speed Downlink / Uplink Packet Access (HSDPA, HSUPA), Long-Term Evolution (LTE), or World Wide Interoperability for Microwave Access (WIMAX). Communication via other common or future communication technologies, e.g. 5G mobile data systems, is possible.The term mobile device includes in particular smartphones, but also other mobile telephones or cell phones, personal digital assistants (PDAs), tablet PCs, notebooks, smart watches and all current and future electronic devices that are equipped with technology for loading and running apps and / or a browser.
[0013] Driver profile data can include, for example, one or more preferred car repair shops, preferred alternative means of transportation (e.g., public transport, rental and / or car hire, car sharing, and possibly preferred car sharing providers, etc.). This driver profile data can be stored for each user in the backend server's storage unit.
[0014] Thus, the backend server can also create the response with reference to a current position of the vehicle and / or a driver profile (based on the driver profile data) of the vehicle user and transmit it to the vehicle.
[0015] Preferably, the at least one technical condition of the vehicle to be changed comprises: - a recognized need for repair of the vehicle; - a recognized need for service of the vehicle; and / or - a recognized time- and / or season-specific need for the vehicle.
[0016] The message can include at least one, but also a multitude of changing technical conditions of the vehicle.
[0017] The at least one technical condition of the vehicle that needs to be changed may, for example, include a recognized need for repair of the vehicle. The recognized need for repair may include: - a detected technical defect in the vehicle; - a detected electronic defect in the vehicle; - a defect in the braking system which allows you to continue driving moderately, but which requires immediate repair by a specialist workshop; - a defect in the drive that requires immediate inspection; - an engine malfunction that may lead to damage to the catalytic converter; etc.
[0018] Additionally or alternatively, the at least one technical condition of the vehicle to be changed may include a detected service requirement of the vehicle. The detected service requirement may include one or more of the following: - a need for maintenance; - a need for inspection; - an oil service requirement; - a need for brake service; - a need to replace the microfilter; - a Selective Catalytic Reduction refill requirement; - a brake fluid replacement requirement; etc.
[0019] In addition or alternatively, the at least one technical condition of the vehicle to be changed may include a recognized time- and / or season-specific requirement of the vehicle. The time- and / or season-specific requirement of the vehicle may, for example, - a tire change; - a wheel change; - replacing the wiper blades; - a seasonal check comprising visual and / or functional tests on the vehicle,
[0020] Preferably, the vehicle is configured to automatically record the technical condition to be changed and then automatically transmit the message to the backend server.
[0021] For example, the vehicle can automatically detect the technical condition to be changed using suitable sensors.
[0022] A suitable sensor, for example, is a tire pressure sensor that detects a deviation from the optimal tire pressure of x% (e.g., x=1 or x=2 or x=3) as a technical condition that needs to be changed. If this is the case, the vehicle can automatically create the message and transmit it to the backend server. The message can, for example, contain current geographical position data and / or a currently driven or planned route. The backend server can, for example, determine a workshop near the current geographical position and / or on or near the currently driven or planned route and transmit the geographical position data of the determined workshop to the vehicle as the destination. The vehicle's navigation system can provide route guidance to the received destination.
[0023] Other examples of suitable sensors include oil level sensors, brake wear sensors, tire pressure sensors, engine diagnostics, etc.
[0024] Preferably, the response also includes replacement mobility data related to the destination.
[0025] From the technical condition to be changed, the backend server can, for example, deduce that the vehicle must remain at the destination received with the response, e.g. a workshop, for a certain period of time. For example, the vehicle can automatically determine whether the vehicle requires repairs using a suitable sensor. Using the VIN and, if applicable, current position data and / or driver profile data of the vehicle user (e.g. preferred workshop), the backend server can automatically determine a workshop that can carry out the repair for the vehicle type. Determining the optimal workshop can, in particular, also include comparing the calendar of the vehicle user with the appointment calendar of the respective workshop, so that an appointment is booked for the vehicle repair. The estimated time of arrival of the vehicle at the destination can be taken into account when booking the appointment.Appointment booking can be automatic or with the involvement of the vehicle user. For example, one or more appointments can be issued to the user via the input and output unit, which are consistent with the user's and the workshop's appointment calendar. The user can then select one of the appointments. The selection can be transmitted as a new message to the backend server. The backend server can book the appointment. This can be followed by an update of the user calendar and / or the workshop calendar. The backend server can confirm the appointment selection after successful booking, for example, by transmitting a corresponding confirmation to the vehicle and outputting it via the input and output unit. If the technical condition of the vehicle to be changed results in it having to remain in the workshop for longer than a predetermined period of time (e.g., 0.5h, 1h, or 1.5h) (e.g.,Since the repair time of the identified repair need is on average 3 hours, the backend server can determine replacement mobility data with reference to the destination and send it to the vehicle together with the response.
[0026] The replacement mobility data may include: - a replacement vehicle from a fleet belonging to the workshop and any costs incurred; - Timetable data for one or more public transport means; - Car-sharing data regarding available and bookable car-sharing vehicles within a predefined radius (e.g. 500m, 600m or 1km) around the destination position; - a vehicle configured in the customer's virtual garage; - a vehicle from a fleet of professional car rentals; - Arranging a taxi company or similar service provider; etc.
[0027] The alternative mobility data can be output via the input and output unit. The alternative mobility data can, if necessary, take into account the driver profile data of the vehicle user. For example, only alternative mobility data for the preferred alternative mode of transport is output. In another example, the output order can correspond to the user profile data.
[0028] Preferably, the vehicle creates the message after receiving input from a user of the vehicle with reference to the received input and then transmits the message to the backend server.
[0029] The vehicle may include an input and output unit, which may include a speech recognition module. In another example, the input and output unit and the speech recognition module are separate units. The input and output unit may be the vehicle's infotainment system, for example. The user input may be via a manual input (e.g., touch screen, rotary push button, etc.) of the input and output unit and / or via the speech recognition module. The speech recognition module includes an automated speech recognition system or an Automatic Speech Recognition (ASR) system to receive speech input from the vehicle user. The speech recognition module may be configured to perform a variety of different tasks. For example, the vehicle user can make a speech input by means of a speech utterance, which is fed to the automated speech recognition system, for example, via a microphone.The automated speech recognition system can be designed in a conventional manner. Providing voice input via the speech recognition module has the advantage that the vehicle user is distracted as little as possible from the traffic situation when making voice inputs, allowing the driver to make voice inputs while driving, while simultaneously ensuring the safety of all road users.
[0030] The user's input can include at least one technical condition of the vehicle to be changed. After the user's input is received via the input / output unit or the speech recognition module, the vehicle can create the message in a suitable module—e.g., the communication module—referring to the received input and transmit or send it to the backend server.
[0031] According to a second aspect, the underlying object is achieved by a method for dynamic, vehicle-specific control of a navigation system in a vehicle, comprising: Receiving, at a backend server, a message from the vehicle, wherein the message comprises technical status parameters of the vehicle, wherein the technical status parameters comprise a vehicle identification number and at least one technical status of the vehicle to be changed; Creating, by the backend server, a response with respect to the received technical status parameters, the response comprising a destination for use by the vehicle's navigation system; and Transferring the response from the backend server to the vehicle.
[0032] Preferably, the at least one technical condition of the vehicle to be changed comprises: - a recognized need for repair of the vehicle; - a recognized need for service of the vehicle; and / or - a recognized time- and / or season-specific need for the vehicle.
[0033] Preferably, the vehicle is configured to automatically record the technical condition to be changed and to automatically transmit the message to the backend server.
[0034] Preferably, the response also includes replacement mobility data related to the destination.
[0035] Preferably, the vehicle creates the message after receiving input from a user of the vehicle with reference to the received input and transmits it to the backend server.
[0036] These and other objects, features, and advantages of the present invention will become more apparent upon review of the following detailed description of preferred embodiments and the accompanying drawings. It will be appreciated that, although embodiments are described separately, individual features thereof may be combined to form additional embodiments. Fig. 1 schematically shows a system for dynamic, vehicle-specific control of a navigation system in a vehicle. Fig. 2 shows a flowchart illustrating a method for dynamic, vehicle-specific control of a navigation system in a vehicle.
[0037] Fig. 1 shows a schematic system 100 for dynamic, vehicle-specific control of a navigation system 120 in a vehicle 110. The system 100 is configured to implement a method for dynamic, vehicle-specific control of a navigation system 120 in a vehicle 110 as described with reference to Fig. 2. The system comprises at least one vehicle 110 and at least one backend server 170.
[0038] The backend server 170 is a central data pool and may include a computing device (not shown) and a storage device 175, e.g., a database, in which data can be centrally controlled, stored, managed, and processed.
[0039] The term vehicle 110 includes passenger cars (cars), trucks (lorries), buses, mobile homes, motorcycles, etc.
[0040] The vehicle 110 comprises a navigation system 120, which is configured to provide route guidance. This can be implemented, for example, as on-board route guidance, in which the corresponding road maps are stored locally in the vehicle 110 and the route to the destination is determined on the vehicle side. The vehicle 110 can comprise a communication module 140. The communication module 140 is configured to establish a communication connection with other communication participants, for example with the backend server 170. The communication module 140 can comprise a subscriber identity module 145 or a SIM card, which serves to establish a communication connection via a mobile radio system (not shown). The subscriber identity module 145 uniquely identifies the communication module 140 in the mobile radio network. The communication connection can be a data connection (e.g.This can be a network connection (e.g., packet switching) and / or a wired communication connection (e.g., circuit switching). Any communication between the vehicle 110 and other communication participants, e.g., the backend server 170, can take place via the communication module 140.
[0041] The vehicle 110 may also include an input and output unit 135. The input and output unit 135 may include a speech recognition module 130. In another example, the input and output unit 135 and the speech recognition module 130 are separate units. The input and output unit 135 may, for example, be the infotainment system of the vehicle 110. The user of the vehicle 110 can perform a manual input (e.g., touch screen, rotary push button, etc.) via the input and output unit 135 or a voice input 130 via the speech recognition module 130. The user of the vehicle 110 can be its owner and / or authorized driver of the vehicle 110. The user can receive an acoustic, visual and / or audiovisual output via the input and output unit 135. The speech recognition module 130 includes a system for automated speech recognition oran Automatic Speech Recognition (ASR) system for receiving voice inputs from the user of the vehicle 110. The speech recognition module 135 can be configured to perform a variety of different tasks. For example, the user of the vehicle 110 can make a voice input by means of a spoken utterance, which is fed to the automated speech recognition system, for example, via a microphone. The automated speech recognition system can be configured in a manner known per se. The provision of voice inputs via the speech recognition module 130 has the advantage that the user, in particular the driver of the vehicle 110, is distracted as little as possible from the traffic situation when making voice inputs. This allows the user to make voice inputs while driving, while simultaneously ensuring the safety of all road users.
[0042] The user of the vehicle can perform a one-time registration on the backend server 170 via the input and output unit 135 and / or the speech recognition module 130. The one-time registration of the user and / or the vehicle 110 may be required before the dynamic, vehicle-specific control of the navigation system 120 can be provided in the vehicle 110. In addition or alternatively, the one-time registration can also be carried out via a stationary terminal, such as a personal computer and / or a mobile terminal (not shown). During the one-time registration, in addition to the VIN, driver profile data of the user of the vehicle 110 can be recorded and stored in the storage unit 175. Driver profile data can, for example, include one or more preferred car repair shops, preferred alternative means of transport (e.g. public transport, rental and / or car rental, car sharing and, if applicable,preferred car-sharing provider), preferred gas stations, etc.
[0043] The backend server 170 is configured to receive messages from the vehicle 110 and to transmit or send corresponding responses or response messages to the vehicle 110. For example, the backend server 170 can receive a request from the vehicle 110 as a message in the sense of the client-server paradigm, generate a corresponding response as a response and transmit or send it to the vehicle 110. Each message includes technical status parameters of the vehicle 110. The technical status parameters include at least one vehicle identification number (VIN) and at least one technical status of the vehicle 110 that is to be changed. The technical status parameters can also include current position data of the vehicle 110 and / or a current or planned route of the vehicle 110.
[0044] Position data of the vehicle 110 can be determined using a navigation satellite system. The vehicle 110 can include a position determination unit 125 that is suitable for detecting a position of the vehicle in the respective system. In the example of GPS, the position determination unit 125 can include a GPS module (not shown) that is designed to determine the current GPS position of the vehicle 110. The GPS position of the vehicle 110 can be determined during driving operation at predefinable or predefined intervals, e.g., every 1 second (s), every 5 s, every 10 s, every 15 s, or any other suitable predefined event, for example, when the message is created.
[0045] The at least one technical condition of the vehicle 110 to be changed may include: - a recognized need for repair of the vehicle 110; - a recognized service requirement of the vehicle 110; and / or - a recognized time- and / or season-specific requirement of the vehicle 110.
[0046] The message may include at least one, but also a plurality of technical states of the vehicle 110 that are to be changed.
[0047] The identified repair needs of the vehicle 110 may include: - a detected technical defect on the vehicle 110; and / or - a detected electronic defect on the vehicle 110; - a defect in the braking system that allows you to continue driving moderately, but requires immediate repair by a specialist workshop - a defect in the braking system which allows you to continue driving moderately, but which requires immediate repair by a specialist workshop; - a defect in the drive that requires immediate inspection; - an engine malfunction that may lead to damage to the catalytic converter; etc.
[0048] The identified service needs of the vehicle 110 may include, for example: - a need for maintenance; - a need for inspection; - an oil service requirement; - a need for brake service; - a need to replace the microfilter; - a Selective Catalytic Reduction refill requirement; and / or - a need to replace the brake fluid;
[0049] The time and / or season-specific requirements of the vehicle 110 can, for example, - a tire change; - a wheel change; - replacement of the wiper blades; and / or - a seasonal check comprising visual and / or functional tests on the vehicle 110.
[0050] The vehicle 110 can be configured to automatically detect a technical condition to be changed. For example, the vehicle 110 can automatically detect the technical condition to be changed using suitable sensors. An example of a suitable sensor is a tire pressure sensor that automatically detects a deviation from the optimal tire pressure by x% (e.g., x=1 or x=2; x=3; or x=5) as the technical condition to be changed. If this is the case, the vehicle 110 can automatically create the message that includes the detected deviation from the optimal tire pressure, the VIN, and, if applicable, the current geographical position of the vehicle 110, and send or transmit it to the backend server 170.
[0051] Other examples of suitable sensors include oil level sensors, brake wear sensors, tire pressure sensors, engine diagnostics, etc.
[0052] In another example, the user of vehicle 110 can record the technical condition to be changed and manually enter it via input / output unit 135 and / or voice module 130. After the user has entered the input, vehicle 110 can create the message in a suitable module—e.g., communication module 140—with reference to the received input and including the technical condition parameters and transmit it to backend server 170.
[0053] The backend server 170 is configured to receive the message from the vehicle 110, either automatically initiated by the vehicle 110 or manually initiated by the user of the vehicle 110, and to create a corresponding response with reference to the technical status parameters. The response includes a destination for use by the vehicle's navigation system. The backend server 170 transmits the response to the vehicle 110. The navigation system 120 can automatically adopt the destination and provide route guidance to the destination.
[0054] Advantageously, a dynamic, vehicle-specific, automatic operation of the navigation system 120 of the vehicle 110 can be realized in this way.
[0055] The response from backend server 170 can also include replacement mobility data relating to the destination. From the technical condition to be changed, backend server 170 can, for example, deduce that vehicle 110 must remain at the destination received with the response, e.g., a workshop, for a specific period of time. For example, vehicle 110 can automatically determine a vehicle repair requirement using a suitable sensor. Using the VIN and, if applicable, current position data and / or driver profile data of the user of vehicle 110 (e.g., preferred workshop), backend server 170 can automatically determine a workshop that can perform the repair for the vehicle type—which is derived from the VIN.Determining the optimal workshop can, in particular, also include comparing a calendar of the user of the vehicle 110 with an appointment calendar of the respective workshop so that an appointment can be booked for the vehicle repair. When booking the appointment, the expected arrival time of the vehicle 110 at the destination can be taken into account. The appointment booking can be carried out automatically or with the involvement of the user of the vehicle 110. For example, one or more appointments that correspond to the appointment calendar of the user and the workshop can be issued to the user via the input and output unit 135 and / or the voice module 130. The user can select one of the appointments. The backend server 170 can book the appointment according to the user selection. Booking the appointment can include updating the user calendar and / or the workshop calendar.The backend server 170 can confirm the appointment selection after a successful booking, for example, by outputting a corresponding confirmation via the input / output unit 135 and / or the voice module 130. The backend server 170 can retrieve the workshop's appointment calendar via the Internet or communicate with a workshop server.
[0056] If the technical condition of the vehicle 110 to be changed indicates that it must remain in the workshop for longer than a predetermined period of time (e.g., 0.5 hours, 1 hour, or 1.5 hours), the backend server 170 can determine replacement mobility data with reference to the destination and send it along with the response to the vehicle 110. This can result, for example, from the type of repair to be performed (e.g., average repair time) and / or from the appointment booking (e.g., duration of the appointment or appointment at a later time).
[0057] The replacement mobility data may include: - a replacement vehicle from a fleet belonging to the workshop and any costs incurred; - Timetable data for one or more public transport means; - Car-sharing data regarding available and bookable car-sharing vehicles within a predefined radius (e.g. 500m, 600m or 1km) around the destination position; - a vehicle configured in the customer's virtual garage; - a vehicle from a fleet of professional car rentals; - Arranging a taxi company or similar service provider; etc.
[0058] The replacement mobility data can be output via the input and output unit 135 and / or the voice module 130. The replacement mobility data can, if appropriate, take into account driver profile data of the user of the vehicle 110. For example, only replacement mobility data for the preferred alternative mode of transport is output. In another example, the order of output can correspond to the user profile data. Example 1
[0059] The following is an example of the dynamic, vehicle-specific control of the navigation system 120 in the vehicle 110. In this example, the user of the vehicle 110 has registered himself and / or the vehicle 110 once with the backend server 170.
[0060] During a journey with the vehicle 110, a tire pressure sensor (not shown) can automatically detect a deviation from the optimal tire pressure of more than 5% on a tire as a technical condition that needs to be changed. This technical condition that needs to be changed can be dangerous at excessively high speeds. Therefore, a corresponding warning can first be issued to the user of the vehicle 110 via the input and output unit 135. The VIN can be read from a memory unit 160 via a suitable computing unit in the vehicle 110, e.g. the control module 150. In addition, the position determination unit 125 can be controlled such that it determines current position data of the vehicle 110. The control module 150 automatically generates a message comprising the VIN, the current position data, a current route of the vehicle 110 and the technical condition that needs to be changed (tire pressure too low) and sends ortransmits this via the communication module 140 to the backend server 170. The backend server 170 extracts the data and, according to the currently driven route, determines a workshop or gas station that is located on the current route or near the current route.
[0061] The backend server 170 generates a response that includes the determined workshop or gas station as the destination and transmits or sends it to the vehicle 110. The destination is displayed to the user of the vehicle 110 via the input and output unit 135. The destination is automatically adopted by the navigation system 120 for route guidance to the destination.
[0062] Thus, the user of the vehicle 110 can be automatically navigated to a workshop or gas station where the tire pressure can be correctly adjusted again. Example 2
[0063] The following is another example of the dynamic, vehicle-specific control of the navigation system 120 in the vehicle 110. The user of the vehicle 110 has registered himself and / or the vehicle 110 once with the backend server 170.
[0064] During a journey with the vehicle 110, a sensor can automatically detect a defective control unit responsible for the anti-lock braking system (ABS) as a technical condition that needs to be changed. This technical condition can endanger the safety of the vehicle occupants. Therefore, a corresponding warning can first be sent to the user of the vehicle 110 via the input and output unit 135 and 130. The VIN can be read from a memory unit 160 via a suitable computing unit in the vehicle 110, e.g., the control module 150. Furthermore, the position determination unit 125 can be controlled such that it determines current position data of the vehicle 110. The control module 150 automatically generates a message comprising the VIN, the current position data, a current route of the vehicle 110 (from the navigation module 120), and the technical condition that needs to be changed (ABS control unit defective), and sends or transmits this message to the backend server 170.
[0065] The backend server 170 extracts the data and identifies a workshop near the currently traveled route that can repair the control unit of the vehicle 110 (which can be determined from the VIN). Using the VIN, the current position status data, the current route data, and driver profile data stored on the server for the user of the vehicle 110 (e.g., preferred workshop), the backend server identifies a workshop that can perform the repair for the control unit of the vehicle type—which can be determined from the VIN—that is located near the current route and corresponds to or is similar to the preferred workshop (e.g., similar customer reviews). Determining the optimal workshop involves comparing a calendar of the user of the vehicle 110 with an appointment calendar of the respective workshop so that an appointment can be booked for the vehicle repair.When booking an appointment, the estimated arrival time of the vehicle 110 at the destination is taken into account. Multiple appointments that correspond to the user's and the workshop's appointment calendar can be output to the user via the input and output unit 135 and / or the voice module 130. The user selects one of the appointments. The backend server 170 can book the appointment according to the user's selection. The booking includes an update of the user calendar and the workshop calendar. The backend server 170 confirms the workshop appointment after a successful booking by sending a corresponding confirmation to the vehicle 110, where it is output via the input and output unit 135.
[0066] The backend server 170 generates a response that includes the determined workshop as the destination and transmits or sends it to the vehicle 110. The destination can be displayed to the user of the vehicle 110 via the input and output unit 135. The destination can be automatically transferred to the navigation system 120 for route guidance to the destination.
[0067] From the type of technical condition to be changed (ABS control unit defective), the backend server 170 recognizes (e.g., by retrieving the technical condition from the database 175) that the vehicle 110 must remain in a workshop for at least one day (e.g., because the average repair time is 1 day). Therefore, the backend server 170 determines replacement mobility data with reference to the destination, which is sent to the vehicle 110 along with the response. The replacement mobility data is also determined with reference to the driver profile data. In this case, the user of the vehicle 110 prefers a replacement vehicle from a fleet belonging to the workshop. The input and output unit provides the user with several replacement vehicles belonging to the fleet, along with the corresponding costs, via the input and output unit 135. The user selects a replacement vehicle via the input and output unit 135. The selection is sent to the backend server 170.The backend server 170 books the selected replacement vehicle at the workshop and, after successful booking, transmits a booking confirmation to the vehicle 110, where it is output via the input and output unit 135.
[0068] Fig. 2 shows a flowchart illustrating a method 200 for dynamic, vehicle-specific control of a navigation system 120 in a vehicle 110 - as described above with reference to Fig. 1. The process steps can be described as with reference to Fig. 1 described.
[0069] The method 200 includes receiving 210, at a backend server 170, a message from the vehicle 110, wherein the message includes technical status parameters of the vehicle 110, wherein the technical status parameters include a vehicle identification number and at least one technical status of the vehicle 110 to be changed. The at least one technical status of the vehicle 110 to be changed may include: - a recognized need for repair of the vehicle 110; - a recognized service requirement of the vehicle 110; and / or - a recognized time- and / or season-specific requirement of the vehicle 110.
[0070] The method 200 further includes creating 220, by the backend server 170, a response with respect to the received technical status parameters, wherein the response includes a destination for use by the navigation system 120 of the vehicle 110. The response may further include replacement mobility data with respect to the destination. The method 200 further includes transmitting 230 the response from the backend server 170 to the vehicle 110.
[0071] The vehicle 110 can be configured to automatically detect the technical condition to be changed and to automatically generate the message and transmit it to the backend server 170.
[0072] Furthermore, or alternatively, the vehicle 110 can create the message after receiving input from a user of the vehicle 110 with reference to the received input and transmit it to the backend server 170. In this case, the received input from the user includes at least one technical condition to be changed.
Claims
[1] System (100) for dynamic, vehicle-specific control of a navigation system (120) in a vehicle (110), comprising: at least one backend server (170), wherein the backend server (170) is configured - to receive a message comprising technical status parameters from the vehicle (110), wherein the technical status parameters comprise a vehicle identification number and at least one technical status of the vehicle (110) to be changed; - to determine, on the basis of the technical condition to be changed, whether the vehicle (110) must remain at a destination for longer than a predetermined period of time; - to determine replacement mobility data with respect to the destination if the vehicle (110) has to remain at the destination for longer than the predetermined period of time; - to create a response with respect to the technical condition parameters, the response comprising the destination for use by the navigation system (120) of the vehicle (110); and the response comprising the replacement mobility data with respect to the destination if the vehicle (110) must remain at the destination for longer than the predetermined period of time; and - transmit the response to the vehicle (110). [2] System (100) according to claim 1, wherein the at least one technical state of the vehicle (110) to be changed comprises: - a recognised need for repair of the vehicle (110); - a recognized service requirement of the vehicle (110); and / or - a recognized time- and / or season-specific need of the vehicle (110). [3] System (100) according to one of the preceding claims, wherein the system (100) comprises the vehicle (110) and wherein the vehicle (110) is configured to automatically detect the technical condition to be changed and then automatically transmit the message to the backend server (170). [4] System (100) according to one of the preceding claims, wherein the system (100) comprises the vehicle (110) and wherein the vehicle (110) creates the message after receiving input from a user of the vehicle (110) with reference to the received input and transmits it to the backend server (170). [5] Method (200) for dynamic, vehicle-specific control of a navigation system (120) in a vehicle (110), comprising: Receiving (210), at a backend server (170), a message from the vehicle (110), wherein the message comprises technical status parameters of the vehicle (110), wherein the technical status parameters comprise a vehicle identification number and at least one technical status of the vehicle (110) to be changed; Determining, based on the technical condition to be changed, whether the vehicle (110) must remain at a destination for longer than a predetermined period of time; Determining replacement mobility data with respect to the destination if the vehicle (110) must remain at the destination for longer than the predetermined period of time; Creating (220), by the backend server (170), a response with respect to the received technical status parameters, wherein the response comprises the destination for use by the navigation system (120) of the vehicle (110); and wherein the response comprises the replacement mobility data with respect to the destination if the vehicle (110) must remain at the destination for longer than the predetermined period of time; and Transmitting (230) the response from the backend server (170) to the vehicle (110). [6] Method (200) according to claim 5, wherein the at least one technical state of the vehicle (110) to be changed comprises: - a recognised need for repair of the vehicle (110); - a recognized service requirement of the vehicle (110); and / or - a recognized time- and / or season-specific need of the vehicle (110). [7] Method (200) according to one of claims 5 or 6, wherein the vehicle (110) automatically detects the technical condition to be changed and automatically transmits the message to the backend server (170). [8] Method (200) according to one of claims 5 to 7, wherein the vehicle (110) creates the message after receiving input from a user of the vehicle (110) with reference to the received input and transmits it to the backend server (170).
Citation Information
Patent Citations
Vehicle communication system
DE102013208130A1
On board vehicle network security
US20130227648A1