Method for adapting a vehicle configuration, computer program, device, and vehicle
By adapting vehicle configuration based on service data and position correlation with workshops, the method effectively suppresses false warning messages during maintenance, enhancing user experience and service efficiency.
Patent Information
- Application Number
- PCT/EP2024/055583
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2024-03-04
- Publication Date
- 2024-11-21
AI Technical Summary
Existing vehicle systems often incorrectly trigger warning messages during maintenance in workshops, leading to unnecessary communication and customer confusion, as they cannot differentiate between actual vehicle usage and service situations, causing false alerts and unfounded service processes.
A method to adapt vehicle configuration based on service data, suppressing automatic warning messages by determining service situations through data collection and position correlation with workshops, using a physical customer key reading or map data to filter out false triggers and set configuration parameters accordingly.
Prevents incorrect triggering of warning messages by identifying service situations, improving user experience and reducing unnecessary communication, ensuring timely and accurate service processes.
Smart Images

Figure EP2024055583_21112024_PF_FP_ABST
Abstract
Description
[0001] Method for adapting a vehicle configuration, computer program, device and vehicle
[0002] Description
[0003] Embodiments of the present invention relate to methods for adapting a vehicle configuration, a computer program, a device and a vehicle, in particular but not exclusively to a concept for setting a configuration parameter of the vehicle based on service data.
[0004] A vehicle that detects a certain condition, such as an airbag deployment, can send a warning message about this condition or an event that caused this condition to a backend. This allows necessary measures to be taken, such as placing a call for roadside assistance. However, a warning message can also be triggered unintentionally, for example, by a repair at a workshop. A false warning message can be triggered by a so-called pseudo-error. This can lead to customer confusion and frustration due to unnecessary communication of problems and needs. Furthermore, dealer frustration can arise due to unnecessary communication of required actions.
[0005] For example, it may be necessary to suppress automatically sent warning messages that are technically incorrect in a workshop due to repairs or work on the vehicle. These sent warning messages may lead to unwanted follow-up processes. For example, disconnecting an airbag triggers various warning messages, possibly including data transmission. This leads to the irritating false triggering of a warning message, for example, in a customer app, and can result in unjustified service processes being initiated. This could, for example, be an active call to breakdown assistance.
[0006] To avoid this false triggering of a warning message caused by apparent errors, for example to suppress the sending of a warning message, a physical customer key reading can be carried out in a process step for opening an order. This can generate a data point that can be used to filter false triggers in the backend. However, the customer key reading can be dependent on a workshop. Not every workshop is configured for customer key reading. Furthermore, a physical key is required for customer key reading. There is therefore a need to provide an improved method for adapting a vehicle configuration depending on a service situation. The method, the device, the computer program and the vehicle according to the independent claims take this need into account.
[0007] Embodiments are based on the core idea that a method for adapting a vehicle configuration based on service data can be implemented. This allows, for example, a vehicle configuration parameter to be set depending on a specific service situation in such a way that automatic sending of warning messages is suppressed. For example, data collection (e.g., measurement data from an oil sensor) can be suppressed by software. By suppressing data collection, the software can no longer detect an event that could lead to a false error. This allows the sending of warning messages to be suppressed because the software cannot determine the need to send a warning message.
[0008] Embodiments relate to a method for adapting a vehicle configuration by a control device of a vehicle. The method comprises determining service data indicative of a service situation of the vehicle and setting a configuration parameter of the vehicle based on the service data. The configuration parameter is indicative of a service status of the vehicle. By determining the service data, a service situation of the vehicle can be determined. A configuration parameter of the vehicle can be set for a specific service situation of the vehicle. For example, the configuration parameter can be set such that the sending of a warning message is suppressed. This can prevent a false triggering of a warning message. The user experience can thus be improved.
[0009] In one embodiment, the method may further comprise determining a workshop event and determining the service data based on the workshop event. A workshop event may be an event that occurs in a workshop, for example, raising the vehicle with a lift, resetting a setting for an oil change, or detecting a tester being plugged in. The workshop event may be used to determine a service situation for an individual vehicle. Thus, the vehicle's configuration parameter may be set based solely on the service data. This may simplify setting the configuration parameter. In one embodiment, the method may further comprise obtaining a position of a workshop and obtaining a position of the vehicle. The method may further comprise determining the service data by comparing the position of the vehicle with the position of the workshop.By comparing the vehicle's position with the position of the workshop, it is possible to determine whether the vehicle is in a workshop. This allows a service situation to be determined based on a local correlation between a vehicle's position and a workshop's position. For example, the vehicle's configuration parameter can be set based on data from other vehicles regarding the workshop's position.
[0010] In one embodiment, the method may further comprise obtaining the location of the repair shop by receiving map data indicative of the location of the repair shop. The map data is received from a backend. By receiving the map data from the backend, the timeliness of the map data can be improved. This can improve the determination of the service data.
[0011] In one embodiment, the method may further comprise determining an identity of the repair shop and setting a further configuration parameter of the vehicle based on the determined identity of the repair shop. The further configuration parameter is indicative of the vehicle's presence in the repair shop. The further configuration parameter can, for example, indicate a workshop visit. This allows a backend that communicates with the vehicle to receive information about the workshop visit in a simplified manner.
[0012] In one embodiment, the method may further comprise sending
[0013] Workshop event data indicative of a workshop event of the vehicle.
[0014] Workshop event data is sent to a backend. By sending the workshop event data, the vehicle's control unit can inform the backend about relevant workshop events. Based on the workshop event data, the backend can create the map data. This allows the vehicle's control unit to help keep the map data up to date.
[0015] Embodiments relate to a method for adapting a vehicle configuration, performed by a backend. The method comprises receiving workshop event data indicative of a workshop event of the vehicle. The method further comprises obtaining vehicle position data indicative of a position of the vehicle during an occurrence of the workshop event. Furthermore, the method comprises creating map data indicative of a position of a workshop based on the workshop event data and the vehicle position data and sending the map data for adapting a vehicle configuration. This allows the backend to create map data that can be used by the vehicle's control device to determine service data.
[0016] Embodiments also provide a computer program for performing any of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component.
[0017] Another embodiment is a device for adapting a vehicle configuration. The device comprises an interface for communicating with a backend or a control device of a vehicle and a data processing circuit configured to perform at least one of the methods described herein. Embodiments further provide a vehicle with a device as described herein.
[0018] Exemplary embodiments are explained in more detail below with reference to the accompanying figures. They show:
[0019] Fig. 1 shows a schematic representation of a method for adapting a vehicle configuration;
[0020] Fig. 2 shows a schematic representation of another method for adapting a vehicle configuration;
[0021] Fig. 3 shows a schematic representation of a method for a system; and
[0022] Fig. 4 shows a block diagram of an embodiment of a device for adapting a vehicle configuration.
[0023] Various embodiments will now be described in more detail with reference to the accompanying drawings, in which some embodiments are illustrated. In the figures, the thickness dimensions of lines, layers, and / or regions may be exaggerated for clarity.
[0024] Fig. 1 shows a schematic representation of a method 100 for adapting a
[0025] Vehicle configuration. The method 100 for implementation by a control device of a vehicle includes determining 110 service data indicative of a service situation of the vehicle.
[0026] A service situation can be a situation in which a service is being performed on the vehicle. For example, a tester can be connected to the vehicle, e.g., to an on-board socket. If a tester is connected to the vehicle, the vehicle can be in a service situation. For example, the vehicle can be on a lift. This vehicle condition can be recognized by the fact that the tires are deflated and the vehicle speed is 0 km / h. If the vehicle is on a lift, the vehicle can be in a service situation.
[0027] A service situation can be determined while the service is being performed on the vehicle, for example, while a tester is connected to the vehicle while the vehicle is on a lift. Optionally or alternatively, a service situation can be determined after a service has been performed. For example, after an oil change, an oil change parameter can be changed, which indicates that an oil change is required. The change to the oil change parameter can occur after the oil change has been performed. The service situation can be determined based on the change to the oil change parameter. This allows the service situation to be determined after the service has been completed.
[0028] By determining service data, information about a service situation can be determined. For example, a period of time can be determined during which a false error may occur, which could trigger a warning message.
[0029] A vehicle in a service situation may issue an unwanted warning. For example, a critical warning may be sent as data and trigger an unwanted service process due to a false fault. This could result in, for example, a call from roadside assistance or an automatically generated email or app message, which could diminish the user experience.
[0030] To prevent unnecessary communication due to a false error, a vehicle configuration parameter can be adjusted. The method 100 further includes setting 120 a vehicle configuration parameter based on the service data. By setting the configuration parameter, a vehicle configuration can be changed such that the sending of warning messages triggered by a false error can be prevented. This can improve a user experience. For example, the sending of a warning message can be suppressed by setting the vehicle configuration parameter. Optionally or alternatively, the vehicle configuration parameter can prevent software from performing an action, for example, receiving data from a sensor. By preventing the software action, the generation of a false error can be avoided.Preventing the generation of the fake error can also prevent a warning message from being sent.
[0031] The configuration parameter is indicative of a vehicle's service status. A vehicle's service status can specifically indicate that the vehicle is configured to perform a service. Setting the configuration parameter to 120 can therefore set the vehicle to a service status. This can prevent the sending of a warning message for a false fault.
[0032] Method 100 can identify a vehicle condition that is not based on customer usage but rather on a workshop process, i.e., a service situation. In one embodiment, method 100 can further comprise determining a workshop event and determining the service data based on the workshop event. A workshop event can be determined based on the detection of vehicle conditions that imply a workshop. A vehicle condition that imply a workshop, and thus a workshop event, can be given, for example, by a lift, an occupied on-board socket, and / or an activated vehicle mode (e.g., a programming and diagnostic mode, PAD mode). Furthermore, a vehicle condition that imply a workshop, and thus a workshop event, can be given by a change in an on-board service configuration, for example, resetting an oil service.
[0033] By identifying a workshop event, service data can be determined based on a specific service situation. This can increase the reliability of setting the vehicle's configuration parameters.
[0034] The service data can be indicative of a current service situation. This can be the case, for example, for a workshop event as described above. Optionally or alternatively, the service data can be indicative of an increased probability of a service situation. The service situation of the service data can therefore be either a current service situation and / or an increased probability of a service situation.
[0035] For example, the vehicle may be in a workshop area, which may increase the probability of a service situation. Based on the increased probability, i.e. the positioning of the vehicle in a workshop area, the vehicle's confirmation parameter can be set (as described below). For example, a service situation that cannot be clearly identified (a clear service situation is, for example, a vehicle on a lift or an occupied on-board socket on the vehicle) may occur in a workshop or workshop area. By taking the increased probability into account, a service situation that cannot be clearly correlated with a workshop event, for example the deployment of an airbag due to repair work, can also be taken into account.
[0036] In one embodiment, method 100 may further include obtaining a position of a repair shop and obtaining a position of the vehicle. Furthermore, method 100 may include determining the service data by comparing the position of the vehicle with the position of the repair shop. Obtaining the position of the repair shop may occur by reading a memory unit. For example, the memory unit may be part of the control device. Map data may be stored in the memory unit. The map data is indicative of the position of the repair shop.
[0037] Optionally or alternatively, the location of the workshop can be obtained by receiving map data, for example, from a backend. Alternatively, the map data can also be received from another vehicle.
[0038] The vehicle's position can be obtained by measuring, for example, with a GPS sensor. Optionally or alternatively, the vehicle's position can be obtained by receiving position coordinates. For example, the vehicle can receive the position coordinates from a wireless local area network module in the workshop.
[0039] By comparing the vehicle's position with the position of the workshop, an increased probability of a service situation can be determined. If the vehicle is positioned in a workshop area, the probability of a service situation may be increased. Based on the increased probability of the service situation, the service data can be determined. This service data can then be used to set the vehicle's configuration parameter. A service situation that is not easily or clearly identifiable can be taken into account by preemptively setting the vehicle's configuration parameter. This can prevent a false error for a service situation that is not easily or clearly identifiable.
[0040] For example, a monitoring system stored in the vehicle can detect whether the vehicle is within or outside a workshop area's geoposition window. If the vehicle is within the workshop area's geoposition window, the configuration parameter 120 can be set.
[0041] As described above, a time period can be determined for the occurrence of a pseudo-fault. The vehicle's configuration parameter can be set based on this time period. For example, the time period can be related to the workshop's opening hours. For example, the vehicle's configuration parameter can be set for a workshop's opening hours based on the service data. Outside of the workshop's opening hours, the configuration parameter can be reset so that warning messages can be sent again. This ensures that an event outside of the workshop's opening hours is not incorrectly classified as a pseudo-fault, which would suppress a warning message.
[0042] In one embodiment, method 100 may further comprise obtaining the location of the workshop by receiving map data indicative of the location of the workshop. The map data is received from a backend. The backend may be configured to create the map data. The creation of the map data by the backend is described with reference to Fig. 2. By receiving the map data from the backend, the timeliness of the map data can be improved. This can improve the determination of the service data.
[0043] In one embodiment, method 100 may further comprise determining an identity of the workshop and setting a further configuration parameter of the vehicle based on the determined identity of the workshop. The further configuration parameter is indicative of the vehicle's presence in the workshop or a workshop area. The further configuration parameter can, for example, indicate a workshop location. This allows a backend that communicates with the vehicle to receive information about the workshop location in a simplified manner.
[0044] As soon as the vehicle or control device determines a match between the position of the workshop and the position of the vehicle, the additional configuration parameter can be set. For example, the additional configuration parameter can be set when the vehicle moves into a workshop or workshop area. The additional configuration parameter can be reset when the vehicle leaves a workshop or workshop area.
[0045] In one embodiment, method 100 may further include sending workshop event data indicative of a workshop event of the vehicle. The workshop event data is sent to a backend. By sending the workshop event data, the vehicle's control device can inform the backend about relevant workshop events.
[0046] For example, a function or logic stored in the vehicle can detect vehicle states or workshop events that technically indicate a workshop visit. These can be workshop events such as a check control message, an indicator light for an open bonnet and / or a tester plugged into the on-board socket. The workshop event data can include the GPS position of the vehicle and information about the determination of the workshop event. Optionally, the workshop event data can include a unique vehicle identifier. This allows the map data to be adapted to a vehicle type. The creation of map data, for example map data specific to a vehicle type, is described in more detail below with reference to Fig. 2.
[0047] The control device can generally be a device capable of wireless communication. The control device can communicate with a backend, e.g., a base station, in a mobile communication system. For example, the control device can communicate in / via a mobile communication system. The mobile communication system can include a plurality of transmission points and / or base stations capable of transmitting radio signals with the communication device.
[0048] Further details and aspects are mentioned in connection with the embodiments described below. The embodiment shown in Fig. 1 may include one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described below (e.g., Figs. 2-4).
[0049] Fig. 2 shows a schematic representation of a method 200 for adapting a vehicle configuration. The method 200, for implementation by a backend, includes receiving 210 workshop event data indicative of a workshop event of the vehicle. The backend that implements the method 200 can be a counterpart to the control device described with reference to Fig. 1. For example, the workshop event data can be received 120 from a control device of a vehicle, a base station, and / or a wireless local area network router.
[0050] The method 200 further includes obtaining 220 vehicle position data indicative of a position of the vehicle during an occurrence of the workshop event. The vehicle position data may be received from the vehicle's controller and / or a base station. For example, the vehicle position data may be received in a signal comprising the vehicle position data and the workshop event data. Alternatively, the vehicle position data may be determined by determining the angle of arrival of the signal comprising the workshop event data or by circulation.
[0051] Furthermore, the method 200 includes creating 230 map data indicative of a workshop location based on the workshop event data and the vehicle position data. For example, the backend can data a GPS database or a map with a point cloud. For this purpose, if a defined point density (number of points from different vehicles relative to an area) is exceeded, this area can be defined as a workshop area. The point density distribution can be defined such that small workshops and hobby garages are not taken into account.
[0052] This allows the backend to create a workshop area database. This workshop area database can be included in the map data. To keep the map data up-to-date, data points, i.e., workshop events sent by a vehicle, can be automatically deleted based on time. This allows a workshop area from which no workshop event has been received for a long time to be deleted.
[0053] For example, the workshop event data includes the workshop event, i.e., a reason for the service situation, GPS coordinates of the vehicle, and / or a time of the service situation. Furthermore, the workshop event data can include values from several selected workshop events and / or values from several selected trigger mechanisms for determining workshop events. Furthermore, the workshop event data can include a unique, in particular non-personal, vehicle identifier. Based on the vehicle identifier, a unique vehicle differentiation can be made. This allows distortions caused by frequent workshop events occurring in a small number of vehicles to be filtered out.
[0054] Furthermore, the method 200 includes transmitting 240 the map data for adapting a vehicle configuration. The map data can be transmitted 240, for example, to a base station and / or to a control device of the vehicle or another vehicle.
[0055] Further details and aspects are mentioned in connection with the embodiments described below and / or above. The embodiment shown in Fig. 2 may include one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g., Fig. 1) and / or below (e.g., Figs. 3-4).
[0056] Fig. 3 shows a schematic representation of a method for a system. In 302, a workshop indicator detection can be performed. The workshop indicator detection can determine a workshop event. This allows a service situation to be determined.
[0057] In 304, a check can be performed to determine whether a workshop event (also referred to as a workshop event) has been detected. If a workshop event has been detected, preparations can be made for sending workshop event data in 306, for example, by creating the workshop event data. Optionally or alternatively, service data can be determined in 308 by comparing the position of the vehicle with the position of the workshop. For this purpose, map data can be read from a memory unit of a control device of the vehicle or a general control device. Optionally or alternatively, a workshop configuration parameter of the vehicle can be set in 310.
[0058] At 312, a data packet can be sent. The data packet can include the workshop event data created at 306. At 314, a time-based deletion of received workshop event data can occur in the backend. This allows outdated data to be deleted for the creation of map data. At 316, the backend can create map data. The map data can include a density distribution of existing workshop events, a workshop area geoposition window, GPS coordinates of a center point determination, and / or a radius determination, i.e., a size of the workshop area geoposition window.
[0059] At 318, the map data can be supplemented with additional information. For example, at 320, information about a workshop ID with the associated position can be obtained from another backend, such as a backend of an original equipment manufacturer. At 322, the workshop IDs and positions can be assigned to the map data. This allows workshops, such as workshop area geoposition windows, to be assigned a workshop ID in the map data. This can, in particular, make it possible to set a further configuration parameter, as described above.
[0060] At 324, the created map data can be synchronized between the backend and the vehicle. For this purpose, the backend can send the map data to the vehicle's control unit. At 326, the control unit saves the map data. This allows an on-board database to be created. This on-board database can be used, for example, for later determination of service data.
[0061] At 328, a comparison of the current vehicle position with the on-board database, i.e., the position of the workshop contained in the on-board database, can be performed. At 330, a check can be made to determine whether the comparison is positive, i.e., whether the vehicle is at the location of a workshop or within a workshop area. If no match is detected at 330, the configuration parameter can remain unchanged at 340.
[0062] If a match was detected at 330, a workshop ID can be checked at 332. If no workshop ID is known, the configuration parameter can be set at 334. Furthermore, at 336, a check can be performed to determine whether the vehicle has left the workshop or workshop premises. At 338, it can be determined whether the vehicle has left the workshop or workshop premises. If the vehicle has left the workshop or workshop premises, the configuration parameter can be reset at 340.
[0063] If no match was detected in 332, the configuration parameter can be set in 342. Furthermore, the additional configuration parameter can be set in 344. By setting the additional configuration parameter, a check-in of the vehicle in the workshop or workshop area can be indicated. A data packet concerning the check-in can be sent in 348.
[0064] Furthermore, at 346, a check can be performed to determine whether the vehicle has left the workshop or workshop premises. At 350, it can be determined whether the vehicle has left the workshop or workshop premises. If the vehicle has left the workshop or workshop premises, the configuration parameter can be reset at 352. At 354, the workshop premises can be parameterized. At 356, a data packet concerning the checkout, i.e., leaving the workshop or workshop premises, can be sent.
[0065] An example of the procedure described in Fig. 3 is as follows:
[0066] A Change Data Capture script can monitor a SomelP signal "cclist" for defined Critical Condition Monitoring IDs such as "hood open." Furthermore, states of the on-board socket or other states in the vehicle that indicate a workshop visit or work on the vehicle can be detected. The script can generate a data packet with an ID to distinguish between different vehicles, a rough timestamp, an exact GPS coordinate, the trigger reason (e.g., Critical Condition Monitoring: hood open), and / or the status of other workshop-indicating variables (on-board socket status). A workshop can repair and process x number of vehicles over the course of, say, a month. A quantity of <= x corresponding workshop event data can be sent, each with essentially the same or very similar GPS coordinates.
[0067] In the backend, these data packets can be processed in a database. Individual data records can be automatically deleted after a certain time (e.g., 8 weeks). If numerous workshop events are detected—for example, 30 different vehicles transmit identical GPS coordinates within 4 weeks, to within 3 decimal places (-110 meters accuracy)—the GPS coordinate can be saved as a workshop area with ID y.
[0068] A service can upload or send country-specific coordinates to country-specific vehicles. A function can regularly check whether the vehicle is located at such an address, i.e., a factory area. If so, this information can be provided to functions and / or services via an on-board network signal (message / variable) with the designation "AufWerkstatareal" = "true." If the vehicle is not within the coordinates, the signal "AufWerkstatareal" = "false" can be set.
[0069] Another function can send a data packet to the backend when this state changes, containing the vehicle ID, the time, the factory area ID, and the current value of the "On factory area" signal. This can then be used as a process point for various service processes, similar to a physical key readout.
[0070] Further details and aspects are mentioned in connection with the embodiments described below and / or above. The embodiment shown in Fig. 3 may include one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g., Figs. 1-2) and / or below (e.g., Fig. 4).
[0071] Fig. 4 shows a block diagram of an embodiment of a device 30 for adapting a vehicle configuration. The device can be either a control device of a vehicle (see Fig. 1) or a backend (see Fig. 2). The device 30 comprises an interface 32 for communication with a backend (for example, the backend as described with reference to Fig. 2) or a control device (for example, a control device as described with reference to Fig. 1). The device 30 further comprises a data processing circuit 34 configured to carry out at least one of the methods described herein, for example, the method described with reference to Fig. 1 for the control device of the vehicle or with reference to Fig. 2 for the backend. Further embodiments include a vehicle 40 with a device 30.
[0072] The interface 32 shown in Fig. 4 can, for example, correspond to one or more inputs and / or one or more outputs for receiving and / or transmitting information, for example in digital bit values, based on a code, within a module, between modules, or between modules of different entities. The interface 32 can, for example, be configured to communicate with other network components via a (radio) network or a local interconnection network.
[0073] In exemplary embodiments, the data processing circuit 34 can correspond to any controller or processor or a programmable hardware component. For example, the data processing circuit 34 can also be implemented as software programmed for a corresponding hardware component. In this respect, the data processing circuit 34 can be implemented as programmable hardware with appropriately adapted software. Any processors, such as digital signal processors (DSPs), can be used. Exemplary embodiments are not limited to a specific type of processor. Any processor or even multiple processors are conceivable for implementing the data processing circuit 34.
[0074] As shown in Fig. 4, the interface 32 can be coupled to the respective data processing circuitry 34 of the device 30. In examples, the device 30 can be implemented by one or more processing units, one or more processing devices, any means of processing, such as a processor, a computer, or a programmable hardware component operable with appropriately adapted software. Likewise, the described functions of the data processing circuitry 34 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components can be a general-purpose processor, a digital signal processor (DSP), a microcontroller, etc.Data processing circuitry 34 may be capable of controlling interface 32 so that any data transfer occurring over interface 32 and / or any interaction involving interface 32 may be controlled by data processing circuitry 34. In one embodiment, device 30 may include a memory and at least one data processing circuitry 34 operably coupled to the memory and configured to perform one of the methods described above.
[0075] In examples, interface 32 may correspond to any means for obtaining, receiving, transmitting, or providing analog or digital signals or information, e.g., any terminal, contact, pin, register, input terminal, output terminal, conductor, trace, etc., that enables the provision or receipt of a signal or information. Interface 32 may be wireless or wired and may be configured to communicate with other internal or external components, e.g., to send or receive signals or information.
[0076] In at least some embodiments, the vehicle 40 may, for example, correspond to a land vehicle, a watercraft, an aircraft, a rail vehicle, a road vehicle, a car, a bus, a motorcycle, an off-road vehicle, a motor vehicle, or a truck. The device 30 may, for example, be part of or a control unit of the vehicle 40.
[0077] Further details and aspects are mentioned in connection with the embodiments described above. The embodiment shown in Fig. 4 may include one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g., Figs. 1-3).
[0078] Further embodiments are computer programs for carrying out one of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component. Depending on specific implementation requirements, embodiments of the invention can be implemented in hardware or in software. The implementation can be carried out using a digital storage medium, for example a floppy disk, a DVD, a Blu-ray disc, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, a hard disk, or another magnetic or optical storage device on which electronically readable control signals are stored that can interact or interact with a programmable hardware component in such a way that the respective method is carried out.A programmable hardware component can be formed by a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated circuit (IC = Integrated Circuit), a single-chip system (SOC = System on Chip), a programmable logic element or a field-programmable gate array with a microprocessor (FPGA = Field Programmable Gate Array).
[0079] The digital storage medium can therefore be machine- or computer-readable. Some embodiments thus comprise a data carrier having electronically readable control signals capable of interacting with a programmable computer system or a programmable hardware component such that one of the methods described herein is performed. One embodiment is thus a data carrier (or a digital storage medium or a computer-readable medium) on which the program for performing one of the methods described herein is recorded.
[0080] In general, embodiments of the present invention can be implemented as a program, firmware, computer program, or computer program product with program code or data, wherein the program code or data is effective to perform one of the methods when the program runs on a processor or a programmable hardware component. The program code or data can also be stored, for example, on a machine-readable medium or data carrier. The program code or data can be present, among other things, as source code, machine code, or bytecode, as well as other intermediate code.
[0081] The above-described embodiments are merely illustrative of the principles of the present invention. It is understood that modifications and variations of the arrangements and details described herein will be apparent to others skilled in the art. Therefore, it is intended that the invention be limited only by the scope of the following claims and not by the specific details presented in the description and explanation of the embodiments herein. List of Reference Symbols
[0082] 30 Device
[0083] 32 interface
[0084] 34 Data processing circuit
[0085] 40 vehicles
[0086] 100 Method for implementation by a control device for adapting a
[0087] Vehicle configuration
[0088] 110 Determining service data
[0089] 120 Setting a configuration parameter
[0090] 200 to be carried out by a backend to adapt a vehicle configuration
[0091] 210 Receiving workshop event data
[0092] 220 Obtaining vehicle position data
[0093] 230 Creating map data
[0094] 240 Sending the card data
[0095] 302 Perform workshop indicator detection
[0096] 304 Check whether workshop event was detected
[0097] 306 Preparing to send workshop event data
[0098] 308 Determining service data
[0099] 310 Setting a workshop configuration parameter
[0100] 312 Sending workshop event data
[0101] 314 time-based deletion of workshop event data
[0102] 316 Creating map data
[0103] 318 Adding map data
[0104] 320 Receiving information about a workshop IF
[0105] 322 Assignment of the workshop to the workshop event data
[0106] 324 Synchronization of created map data
[0107] 326 Map data storage
[0108] 328 Comparison of vehicle position and workshop position
[0109] 330 Checking the comparison
[0110] 332 Checking the workshop ID 334 Setting configuration parameters
[0111] 336 Check whether vehicle has left workshop
[0112] 338 Determine that the vehicle has left the workshop
[0113] 340 Reset configuration parameters 342 Set configuration parameters
[0114] Set 344 additional configuration parameters
[0115] 346 Check whether vehicle has left workshop
[0116] 348 Send data packet regarding check-in
[0117] 350 Determine that the vehicle has left the workshop 352 Reset configuration parameters
[0118] 354 Data management of the workshop area
[0119] 356 Send data packet regarding check-out
Claims
Patent claims 1. A method for implementation by a control device of a vehicle for adapting a vehicle configuration, comprising: Determining service data indicative of a service situation of the vehicle; and Setting a configuration parameter of the vehicle based on the service data, the configuration parameter indicative of a service status of the vehicle.
2. The method of claim 1, further comprising Determining a workshop event; and Determine service data based on the workshop event.
3. The method according to any one of the preceding claims, further comprising Obtaining a position of a workshop; Obtaining a position of the vehicle; and Determine service data by comparing the position of the vehicle with the position of the workshop.
4. The method of claim 3, further comprising Obtaining the position of the workshop by receiving, from a backend, map data indicative of the position of the workshop.
5. The method according to any one of claims 3 or 4, further comprising Determining an identity of the workshop; and Setting an additional configuration parameter of the vehicle based on the determined identity of the workshop, the additional configuration parameter indicative of a presence of the vehicle in the workshop.
6. The method according to any one of the preceding claims, further comprising Sending, to a backend, workshop event data indicative of a workshop event of the vehicle.
7. A method for performing a backend for adapting a vehicle configuration, comprising: Receiving workshop event data indicative of a vehicle workshop event; Obtaining vehicle position data indicative of a position of the vehicle during an occurrence of the workshop event; Creating map data indicative of a workshop location based on the workshop event data and the vehicle position data; and Sending map data to adjust a vehicle configuration.
8. A computer program for carrying out one of the methods (100) according to one of the preceding claims, when the computer program runs on a computer, a processor, or a programmable hardware component.
9. A device (30) for adapting a vehicle configuration, comprising: an interface (32) for communication with a backend or a control device; and a data processing circuit (34) configured to carry out at least one of the methods (100) according to any one of claims 1-7.
10. A vehicle (40) having a device (30) according to claim 9.
Citation Information
Patent Citations
Method for operating a control display device, maintenance monitoring device, motor vehicle, and server device
DE102020105066A1
Method, server, computer program, vehicle and system for determining a technical stop of a vehicle
EP3422299A1
Asset health scores and uses thereof
KR1020170117377A
Fault Codes in a motor vehicle
SE1650116A1
Method for Detecting a Malfunction of at Least One Sensor for Controlling a Restraining Device of a Vehicle, Control Apparatus and Vehicle
US20170116794A1
