Soft switching configuration method and device of vehicle, processor and electronic equipment

Abstract

The application discloses a soft switch configuration method and device of a vehicle, a processor and electronic equipment. The method comprises the following steps: in response to a car machine system of the vehicle being in a power-on state, a historical configuration file of a soft switch of the car machine system is acquired from a configuration area of the car machine system, wherein the historical configuration file is used for recording historical parameters of the soft switch; the soft switch is initially configured according to the historical configuration file, wherein the soft switch acts on the car machine system under the historical parameters; in response to the soft switch being in a touch state after the initial configuration, current parameters of the soft switch are acquired, and the current parameters are temporarily written or permanently written in a corresponding writing area of the car machine system to obtain a current configuration file, wherein the writing area is a configuration area or a cache area of the car machine system; and the soft switch is reconfigured according to the current configuration file, wherein the soft switch acts on the car machine system under the current parameters. The application solves the technical problem of low soft switch configuration efficiency of the vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicles, and more specifically, to a method, apparatus, processor, and electronic device for configuring a soft switch for a vehicle. Background Technology

[0002] Currently, vehicles' automatic emergency braking systems (AEB) and door opening warning systems (DOW) are equipped with virtual soft switches in the vehicle's infotainment system. However, in related technologies, the status of these soft switches cannot be traced, resulting in a technical problem of low efficiency in the configuration of vehicle soft switches.

[0003] There is currently no effective solution to the technical problem of low efficiency in the soft-switching configuration of the aforementioned vehicles. Summary of the Invention

[0004] This application provides a method, apparatus, processor, and electronic device for configuring soft switches in a vehicle, to at least solve the technical problem of low efficiency in configuring soft switches in a vehicle.

[0005] According to one aspect of the embodiments of this application, a soft switch configuration method for a vehicle is provided. The method includes: in response to the vehicle's infotainment system being powered on, obtaining a historical configuration file of the soft switch from the configuration area of ​​the infotainment system, wherein the historical configuration file is used to record historical parameters of the soft switch; configuring the soft switch for the first time according to the historical configuration file, wherein the soft switch operates on the infotainment system under the historical parameters; in response to the soft switch being in a touch state after the initial configuration, obtaining the current parameters of the soft switch, and temporarily or permanently writing the current parameters into the corresponding write area of ​​the infotainment system to obtain a current configuration file, wherein the write area is the configuration area or cache area of ​​the infotainment system; and configuring the soft switch again according to the current configuration file, wherein the soft switch operates on the infotainment system under the current parameters.

[0006] Optionally, the soft switch is configured for the first time according to the historical configuration file, including: verifying the historical configuration file and obtaining the verification result; in response to the verification result indicating that the historical configuration file has passed verification, the soft switch is configured for the first time according to the historical configuration file.

[0007] Optionally, the historical configuration file is validated to obtain a validation result, including: determining the inherent validation parameters that already exist in the historical configuration file, and performing validation calculations on the historical configuration file to obtain real-time validation parameters for the historical configuration file; in response to the inherent validation parameters being the same as the real-time validation parameters, the historical configuration file is validated, and the validation result indicates that the historical configuration file has passed validation; in response to the inherent validation parameters being different from the real-time validation parameters, the historical configuration file is validated, and the validation result indicates that the historical configuration file has failed validation.

[0008] Optionally, the current configuration file includes: a first current configuration file and a second current configuration file. In response to the soft switch being in touch mode after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file. This includes: in response to the soft switch being in touch mode after initial configuration and the current parameter writing mode being temporary write mode, the current parameters are obtained and temporarily written to the cache area to obtain the first current configuration file; in response to the soft switch being in touch mode after initial configuration and the current parameter writing mode being permanent write mode, the current parameters are obtained and permanently written to the configuration area to obtain the second current configuration file.

[0009] Optionally, the method further includes: in response to the vehicle system being powered down and the current configuration file being a first current configuration file, deleting the first current configuration file from the cache area; and in response to the vehicle system being powered down and the current configuration file being a second current configuration file, replacing the historical configuration file with the second current configuration file from the configuration area.

[0010] Optionally, the method further includes: in response to the soft switch being in a touch state after initial configuration, generating log data by monitoring touch operations used to put the soft switch in a touch state; writing the log data to a configuration area, and retaining the written log data during a retention period, wherein the write position of the log data in the configuration area is different from the write position of the historical configuration file in the configuration area.

[0011] According to one aspect of the embodiments of this application, a soft switch configuration device for a vehicle is provided. The device may include: an acquisition unit, configured to acquire a historical configuration file of the soft switch of the vehicle system from the configuration area of ​​the vehicle system in response to the vehicle system being powered on, wherein the historical configuration file is used to record historical parameters of the soft switch; a first configuration unit, configured to initially configure the soft switch according to the historical configuration file, wherein the soft switch operates on the vehicle system under the historical parameters; a writing unit, configured to acquire the current parameters of the soft switch in response to the soft switch being in a touch state after initial configuration, and temporarily or permanently write the current parameters to the corresponding writing area of ​​the vehicle system to obtain a current configuration file, wherein the writing area is the configuration area or cache area of ​​the vehicle system; and a second configuration unit, configured to reconfigure the soft switch according to the current configuration file, wherein the soft switch operates on the vehicle system under the current parameters.

[0012] According to another aspect of the embodiments of this application, a processor is also provided. The processor is used to run a program, wherein the program is executed by the processor to perform the methods described in the embodiments of this application.

[0013] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in the embodiments of this application when it runs.

[0014] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. This computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the methods of the embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, the computer program product including a computer program, wherein the computer program implements the method in the embodiments of this application when executed by a processor.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the method in the embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the embodiments of this application.

[0018] In this embodiment, in response to the vehicle's infotainment system being powered on, the historical configuration file of the soft switch of the infotainment system is obtained from the configuration area of ​​the infotainment system; the soft switch is initially configured according to the historical configuration file; in response to the soft switch being in a touch state after the initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the infotainment system to obtain the current configuration file; the soft switch is then configured again according to the current configuration file. Because this embodiment obtains the historical configuration file of the soft switch from the configuration area of ​​the infotainment system when the infotainment system is powered on, initially configures the soft switch according to the historical configuration file, and then temporarily or permanently writes the obtained current parameters to the configuration area or cache area of ​​the infotainment system after the initial configuration when the soft switch is in a touch state to obtain the current configuration file, and then configures the soft switch again according to the current configuration file, since the soft switch can operate on the infotainment system with the current parameters, and the current parameters can be recorded in the current configuration file, the purpose of saving the current parameters of the soft switch is achieved, thereby solving the technical problem of low configuration efficiency of vehicle soft switches, and thus achieving the technical effect of improving the configuration efficiency of vehicle soft switches. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a flowchart of a soft-switch configuration method for a vehicle according to an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of an in-vehicle ADAS safety function vehicle soft switch control system with persistent state memory and operation traceability according to an embodiment of this application;

[0022] Figure 3 This is a flowchart of a vehicle-mounted ADAS safety function vehicle soft switch control method with persistent state memory and operation traceability according to an embodiment of this application;

[0023] Figure 4 This is a flowchart of an OTA upgrade method for a vehicle infotainment system according to an embodiment of this application;

[0024] Figure 5 This is a schematic diagram of a soft-switch configuration device for a vehicle according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] According to an embodiment of this application, an embodiment of a vehicle power-on / off control method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] It should be noted that all information and data involved in this application (including but not limited to historical configuration files and current configuration files) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of such data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0030] Figure 1 This is a flowchart of a vehicle soft-switch configuration method according to an embodiment of this application, such as... Figure 1 As shown, the method may include the following steps.

[0031] Step S101: In response to the vehicle's infotainment system being powered on, retrieve the historical configuration file of the soft switch of the infotainment system from the configuration area of ​​the infotainment system.

[0032] In the technical solution provided by step S101 of this application, the aforementioned historical configuration file can be used to record historical parameters of the soft switch. Specifically, the historical configuration file may include: a historical configuration file for the Automatic Emergency Braking (AEB) soft switch and a historical configuration file for the Door Opening Warning (DOW) soft switch. For example, the historical configuration file for the AEB soft switch can be an aeb_config.txt file, and the historical configuration file for the DOW soft switch can be adow_config.txt file.

[0033] In this embodiment, the vehicle infotainment system can be used to control vehicle braking and / or door opening. The vehicle infotainment system may include Automatic Emergency Braking (AEB) and Door Opening (DOW), whereby AEB is used to control vehicle braking and DOW is used to control vehicle door opening. The vehicle infotainment system can be simply referred to as the vehicle infotainment system.

[0034] In this embodiment, the aforementioned power-on state can be used to indicate that the vehicle has been started.

[0035] In this embodiment, the aforementioned configuration area can be used to represent an independent security configuration partition partitioned by the embedded Multi-Media Card (eMMC) storage chip built into the vehicle's infotainment system. For example, the aforementioned configuration partition can also be referred to as an eMMC partition.

[0036] In this embodiment, the aforementioned historical parameters can be used to represent values ​​stored in a historical configuration file, which can be used to represent the on / off state of the soft switch. For example, the value "1" can represent the on state, and the value "0" can represent the off state.

[0037] In this embodiment, in response to the vehicle's infotainment system being powered on, the historical configuration file of the soft switch of the infotainment system is obtained from the configuration area of ​​the infotainment system. Optionally, this embodiment monitors in real time whether the infotainment system is powered on. When the infotainment system is detected to be powered on, the historical configuration file of the soft switch can be obtained by accessing the configuration area of ​​the infotainment system, thereby achieving the purpose of obtaining the historical configuration file from the configuration area.

[0038] Optionally, in response to the vehicle being started, the persistent storage module for switch states inside the vehicle is automatically activated. The persistent storage module for switch states accesses the preset configuration area inside the vehicle's infotainment system and reads previously saved historical configuration files, such as reading the status files of AEB and DOW functions saved during a historical period.

[0039] Step S102: Configure the soft switch for the first time according to the historical configuration file.

[0040] In the technical solution provided by step S202 of this application, the aforementioned soft switch can act on the vehicle system under historical parameters. For example, in response to the historical parameter being "1" corresponding to the AEB soft switch, the AEB can be triggered to perform the braking function; in response to the historical parameter being "0" corresponding to the DOW soft switch, the DOW can be triggered to perform the door closing function. This is only an example and not a specific example.

[0041] In this embodiment, the aforementioned soft switch can be used to represent a virtual control component deployed on the vehicle's user interface (UI), and the soft switch can be used to display and control the activation or deactivation of AEB and DOW functions. For example, the soft switch can be a slider or toggle button on the UI.

[0042] In this embodiment, after obtaining the historical configuration file of the soft switch from the vehicle's infotainment system, the soft switch is initially configured according to the historical configuration file. Optionally, in this embodiment, the vehicle's infotainment system performs the initial configuration of the soft switch according to the historical configuration file. For example, the Advanced Driver Assistance Systems (ADAS) soft switch UI module extracts historical parameters from the aforementioned historical configuration file and updates the display status of the virtual control components on the UI according to the extracted historical parameters. In addition, the updated display status is synchronized to the underlying ADAS function modules via the Controller Area Network (CAN) bus or internal process communication. At this time, the AEB or DOW functions start working according to their respective historical parameters, thereby achieving the purpose of initially configuring the soft switch according to the historical configuration file.

[0043] Step S103: In response to the soft switch being in touch state after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file.

[0044] In the technical solution provided by step S103 of this application, the writing area can be a configuration area or a cache area of ​​the vehicle system. Specifically, the configuration area can represent an independent security configuration partition divided by the vehicle's built-in eMMC storage chip, and the cache area can represent a temporary cache of the Random Access Memory (RAM).

[0045] In this embodiment, the aforementioned current parameter can be used to represent a value to be stored in the current configuration file. This value represents the on / off state of the soft switch after a touch operation. For example, the value "1" can represent the on state, and the value "0" can represent the off state.

[0046] In this embodiment, the aforementioned touch state can be used to represent the state triggered by a manual touch operation on the soft switch. For example, the aforementioned touch state can be the state triggered by a manual touch operation on the AEB soft switch, or it can be the state triggered by a manual touch operation on the DOW soft switch. The aforementioned manual touch operation can also be referred to as a touch operation.

[0047] In this embodiment, the aforementioned current configuration file can be used to record the current parameters of the soft switch. The current configuration file may include the current configuration file for the AEB soft switch and the current configuration file for the DOW soft switch. For example, the current configuration file for the AEB soft switch can be an aeb_config.txt file, and the current configuration file for the DOW soft switch can be adow_config.txt file.

[0048] In this embodiment, after the soft switch is initially configured according to the historical configuration file, in response to the soft switch being in a touch state after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file. Optionally, this embodiment detects whether the soft switch has been manually touched after initial configuration. If a manual touch operation is detected, the system monitors in real time whether the soft switch is in a touch state after the manual touch operation. If the soft switch is detected to be in a touch state after the manual touch operation, the current parameters set by the manual touch operation are obtained, and the obtained current parameters are temporarily written to the cache area or permanently written to the configuration area to obtain the current configuration file. This achieves the purpose of writing the current parameters to the corresponding write area of ​​the vehicle system to obtain the current configuration file.

[0049] Optionally, if it is detected that the soft switch is not in a touch state after a manual touch operation, the detection continues to check whether the soft switch has been subjected to the next manual touch operation after the initial configuration. If the soft switch is detected to have been subjected to the next manual touch operation after the initial configuration, the detection continues in real time to check whether the soft switch is in a touch state after the next manual touch operation, and then the current parameters set by the next manual touch operation are obtained.

[0050] Step S104: Configure the soft switch again according to the current configuration file.

[0051] In the technical solution provided in step S104 of this application, the aforementioned soft switch operates on the vehicle system under the current parameters. For example, the AEB soft switch can trigger the AEB to perform the braking function under the current parameter of "1", and the DOW soft switch can trigger the DOW to perform the door opening function under the historical parameter of "1". This is only an example and is not described in detail.

[0052] In this embodiment, after obtaining the current configuration file, the soft switch is reconfigured according to the current configuration file. Optionally, the current configuration file can be obtained by accessing the write area. The current parameters are extracted from the current configuration file, and then the soft switch is reconfigured according to the extracted current parameters, thereby achieving the purpose of reconfiguring the soft switch according to the current configuration file.

[0053] For example, by accessing the configuration area, the current configuration file of the AEB soft switch can be obtained. Parameter identification of the current configuration file of the AEB soft switch can reveal its current parameters, or these parameters can be extracted from the current configuration file. Then, the AEB soft switch can be reconfigured according to these current parameters, thereby enabling the AEB soft switch to operate according to the configured parameters.

[0054] In steps S101 to S104 of this application, in response to the vehicle's infotainment system being powered on, the historical configuration file of the soft switch of the infotainment system is obtained from the configuration area of ​​the infotainment system; the soft switch is configured for the first time according to the historical configuration file; in response to the soft switch being in a touch state after the initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the infotainment system to obtain the current configuration file; the soft switch is configured again according to the current configuration file. In this embodiment, when the vehicle system is powered on, the historical configuration file of the soft switch is obtained from the configuration area of ​​the vehicle system. The soft switch is configured for the first time according to the historical configuration file. Then, after the soft switch is configured for the first time and is in touch mode, the obtained current parameters are temporarily or permanently written to the configuration area or cache area of ​​the vehicle system to obtain the current configuration file. After that, the soft switch is configured again according to the current configuration file. Since the soft switch can act on the vehicle system with the current parameters and the current parameters can be recorded in the current configuration file, the purpose of saving the current parameters of the soft switch is achieved, thereby solving the technical problem of low configuration efficiency of vehicle soft switches and thus achieving the technical effect of improving the configuration efficiency of vehicle soft switches.

[0055] The method described in this embodiment will be further described below.

[0056] As an optional embodiment, step S102, configuring the soft switch for the first time according to the historical configuration file, includes: verifying the historical configuration file and obtaining a verification result; in response to the verification result indicating that the historical configuration file has passed verification, configuring the soft switch for the first time according to the historical configuration file.

[0057] In this embodiment, the above verification result can be used to indicate whether the historical configuration file verification passed or failed.

[0058] In this embodiment, after obtaining the historical configuration file of the soft switch of the vehicle system, the historical configuration file is verified to obtain the verification result.

[0059] Optionally, this embodiment extracts inherent verification parameters from historical configuration files and performs verification calculations on the historical configuration files to obtain real-time verification parameters for the historical configuration files. By comparing the inherent verification parameters and the real-time verification parameters, the parameter relationship between the inherent verification parameters and the real-time verification parameters can be obtained. Based on the above relationship, the historical configuration files are verified to obtain the verification results.

[0060] In this embodiment, after verifying the historical configuration file and obtaining the verification result, in response to the verification result indicating that the historical configuration file has passed verification, the soft switch is initially configured according to the historical configuration file.

[0061] Optionally, in this embodiment, if the verification result indicates that the historical configuration file has passed verification, the vehicle system performs initial configuration of the soft switch according to the verified historical configuration file. For example, the ADAS soft switch UI module extracts historical parameters from the aforementioned historical configuration file and updates the display status of the virtual control components on the UI according to the extracted historical parameters. Next, the updated display status is synchronized to the underlying ADAS function modules via the CAN bus or internal process communication. At this time, the AEB or DOW functions begin to work according to their respective historical parameters, thereby achieving the goal of initial configuration of the soft switch according to the historical configuration file, thus realizing the technical effect of improving the initial configuration efficiency of the soft switch.

[0062] The following section further describes the steps of verifying the historical configuration file and obtaining the verification result in this embodiment.

[0063] As an optional embodiment, the historical configuration file is validated to obtain a validation result, including: determining the inherent validation parameters that already exist in the historical configuration file, and performing validation calculations on the historical configuration file to obtain real-time validation parameters for the historical configuration file; in response to the inherent validation parameters being the same as the real-time validation parameters, the historical configuration file is validated, and the validation result indicates that the historical configuration file has passed validation; in response to the inherent validation parameters being different from the real-time validation parameters, the historical configuration file is validated, and the validation result indicates that the historical configuration file has failed validation.

[0064] In this embodiment, the aforementioned inherent verification parameter can be used to represent the end-of-file checksum of a historical configuration file. For example, the aforementioned inherent verification parameter can be the end-of-file checksum of an aeb_config.txt file or a dow_config.txt file; this is merely an example and not a specific limitation.

[0065] In this embodiment, the aforementioned real-time verification parameter can be used to represent the real-time calculated verification value for verifying the checksum at the end of the historical configuration file. For example, the aforementioned real-time verification parameter can be the real-time calculated verification value obtained by verifying the aeb_config.txt file, or it can be the real-time calculated verification value obtained by verifying the down_config.txt file. This is only an example and is not specifically limited.

[0066] In this embodiment, after obtaining the historical configuration file of the vehicle system's soft switch, existing inherent verification parameters are extracted from the historical configuration file, and verification parameters are calculated on the historical configuration file to obtain real-time verification parameters for the historical configuration file. Comparing the inherent verification parameters with the real-time verification parameters reveals the parameter relationship between them. If the parameter relationship indicates that the inherent verification parameters and the real-time verification parameters are the same, the historical configuration file is verified. A verification result indicates that the historical configuration file has passed verification, thereby achieving the goal of confirming that the historical configuration file has passed verification and improving the accuracy of the verification results.

[0067] For example, the persistent storage module for switch states automatically reads the aeb_config.txt and down_config.txt configuration files from the eMMC partition. It then verifies the data in the configuration files. If the configuration file data verification is successful, the switch state values ​​are transmitted to the ADAS soft-switch UI module.

[0068] In this embodiment, after obtaining the historical configuration file of the vehicle system's soft switch, existing inherent verification parameters are extracted from the historical configuration file, and verification parameters are calculated for the historical configuration file to obtain real-time verification parameters for the historical configuration file. The inherent verification parameters and the real-time verification parameters are compared to determine the parameter relationship between them. If the parameter relationship indicates that the inherent verification parameters and the real-time verification parameters are different, the historical configuration file is verified. The verification result indicates that the historical configuration file verification has failed, thereby achieving the goal of determining whether the historical configuration file verification has failed and thus improving the accuracy of the verification results.

[0069] For example, the persistent storage module for on / off status automatically reads the aeb_config.txt and down_config.txt configuration files from the eMMC partition. It then verifies the data in these configuration files. If the verification is successful, the factory default on / off state is restored, and the operation log recording module generates a configuration exception record, which is written to the exception log.

[0070] The following section further describes the steps of the above embodiment in which the soft switch is in a touch state after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file.

[0071] As an optional embodiment, step S103, in response to the soft switch being in touch mode after initial configuration, obtains the current parameters of the soft switch and temporarily or permanently writes the current parameters to the corresponding write area of ​​the vehicle system to obtain the current configuration file, including: in response to the soft switch being in touch mode after initial configuration and the current parameter writing mode being temporary write mode, obtaining the current parameters and temporarily writing the current parameters to the cache area to obtain the first current configuration file; in response to the soft switch being in touch mode after initial configuration and the current parameter writing mode being permanent write mode, obtaining the current parameters and permanently writing the current parameters to the configuration area to obtain the second current configuration file.

[0072] In this embodiment, the aforementioned write mode can be used to represent the mode of writing the current parameter to the write area corresponding to the vehicle system. The write mode can include a temporary write mode and a permanent write mode. The temporary write mode can be used to represent the mode of writing the current parameter to the cache area, and the permanent write mode can be used to represent the mode of writing the current parameter to the configuration area. For example, the temporary write mode can also be simply referred to as the temporary mode, and the permanent write mode can also be simply referred to as the permanent mode.

[0073] In this embodiment, the current configuration file may include a first current configuration file and a second current configuration file. The first current configuration file may be a temporary configuration file, and the second current configuration file may be a permanent configuration file.

[0074] In this embodiment, after configuring the soft switch for the first time according to the historical configuration file, in response to the soft switch being in a touch state after the initial configuration and the current parameter being in temporary write mode, the current parameter is obtained and temporarily written to the cache area to obtain the first current configuration file.

[0075] Optionally, this embodiment detects whether the soft switch has been touched after initial configuration. If a touch operation is detected after initial configuration, the system monitors in real time whether the soft switch is in a touch state after the touch operation and identifies the writing mode of the current parameters. If the soft switch is detected to be in a touch state after the touch operation and the writing mode is identified as a temporary writing mode, the system obtains the current parameters set by the touch operation and temporarily writes the obtained current parameters into the cache area to obtain the first current configuration file. This achieves the goal of writing the current parameters into the cache area corresponding to the vehicle system, thereby improving the writing efficiency of the current parameters.

[0076] For example, after the ADAS soft-switch UI module generates the state change command and displays the storage mode selection pop-up, it determines the storage mode selected by the user. If the selected storage mode is determined to be temporary mode, the current parameters are written to the RAM temporary cache.

[0077] In this embodiment, after configuring the soft switch for the first time according to the historical configuration file, in response to the soft switch being in a touch state after the initial configuration and the current parameter being in permanent write mode, the current parameter is obtained and permanently written to the configuration area to obtain the second current configuration file.

[0078] Optionally, this embodiment detects whether the soft switch has been touched after initial configuration. If a touch operation is detected after initial configuration, the system monitors in real time whether the soft switch is in a touch state after the touch operation and identifies the current parameter writing mode. If the soft switch is detected to be in a touch state after the touch operation and the writing mode is identified as a permanent writing mode, the system obtains the current parameters set by the touch operation and temporarily writes the obtained current parameters into the configuration area to obtain a second current configuration file. This achieves the goal of writing the current parameters into the configuration area corresponding to the vehicle system, thereby improving the writing efficiency of the current parameters.

[0079] For example, after the ADAS soft switch UI module generates the state change command and displays a storage mode selection pop-up, it determines the storage mode selected by the user. If the selected storage mode is determined to be permanent mode, the current parameters are written to the eMMC configuration file, and the verification code is updated.

[0080] The soft switch configuration method for the vehicle described in this embodiment will be further described below.

[0081] As an optional embodiment, the method further includes: in response to the vehicle system being powered down and the current configuration file being a first current configuration file, deleting the first current configuration file from the cache area; and in response to the vehicle system being powered down and the current configuration file being a second current configuration file, replacing the historical configuration file with the second current configuration file from the configuration area.

[0082] In this embodiment, the aforementioned power-down state can be used to indicate that the vehicle infotainment system has been powered down. For example, the aforementioned power-down state can also be referred to as "stopped".

[0083] In this embodiment, if the vehicle system is powered off and the current configuration file is the first current configuration file, then the first current configuration file is deleted from the cache area.

[0084] Optionally, the system can monitor in real time whether the vehicle infotainment system is powered down and identify the current configuration file. If the system is detected to be powered down and the current configuration file is identified as the first current configuration file, it can be deleted from the cache area. For example, after the vehicle arrives at its destination, the system can power down the vehicle and clear the aeb_config.txt or dow_config.txt configuration file in the RAM temporary cache. This achieves the goal of clearing the RAM temporary cache in real time, thereby increasing the storage space of the RAM temporary cache.

[0085] In this embodiment, if the vehicle system is powered off and the current configuration file is the second current configuration file, the historical configuration file is replaced with the second current configuration file from the configuration area.

[0086] Optionally, the system can monitor in real time whether the vehicle infotainment system is powered down and identify the current configuration file. If the system is detected to be powered down and the current configuration file is identified as the second current configuration file, the historical configuration file is replaced with the second current configuration file from the configuration area. For example, after the vehicle arrives at its destination, the vehicle is powered down, and the permanent configuration file and historical log file in the eMMC partition are continuously saved. This achieves the goal of continuously saving the configuration files in the partition, thereby improving the efficiency of configuration file retrieval.

[0087] The soft switch configuration method for the vehicle described in this embodiment will be further described below.

[0088] As an optional embodiment, the method further includes: in response to the soft switch being in a touch state after initial configuration, generating log data by monitoring touch operations used to put the soft switch in a touch state; writing the log data to a configuration area; and retaining the written log data during a retention period.

[0089] In this embodiment, because the operation log recording module and the eMMC storage chip are separated into independent log storage sub-partitions, the location of the log data in the configuration area differs from the location of the historical configuration file in the configuration area. For example, the log data can be stored in log files according to natural dates, with the daily log file naming format being operation_yyyyMMdd.log. This is only an example and is not a specific limitation.

[0090] In this embodiment, the write location of the log data in the configuration area is different from the write location of the historical configuration file in the configuration area. For example, the log data may include: operation time (accurate to the hour, minute and second, taken from the vehicle time synchronization module), operation object (AEB / DOW identifier), status value before change, status value after change, and temporary / permanent storage marker.

[0091] In this embodiment, the retention period can be used to represent the duration for which log data is retained after it has been written. For example, the retention period can be, but is not limited to, 90 days.

[0092] In this embodiment, after the soft switch is initially configured and is in touch mode, touch operations that cause the soft switch to be in touch mode are monitored, and log data is generated. The generated log data is then written to the configuration area, and the written log data is retained for a retention period.

[0093] For example, the system monitors in real time whether a soft switch is in a touch-sensitive state after a touch operation. If the soft switch is detected to be in a touch-sensitive state, the system obtains the operation time, operation object, pre-change state value, post-change state value, and temporary / permanent storage markers for the touch operation. These data are then generated into a log file. The generated log file is then written to an independent security configuration partition defined by the vehicle's built-in eMMC storage chip, and the written log file is retained for 90 days. This achieves the goal of retaining the written log data within the retention period, thereby improving the security of the log data.

[0094] In this embodiment, when the vehicle system is powered on, the historical configuration file of the soft switch is obtained from the configuration area of ​​the vehicle system. The soft switch is configured for the first time according to the historical configuration file. Then, when the soft switch is in touch mode after the initial configuration, the obtained current parameters are temporarily or permanently written to the configuration area or cache area of ​​the vehicle system to obtain the current configuration file. After that, the soft switch is configured again according to the current configuration file. Since the soft switch can act on the vehicle system under the current parameters, and the current parameters can be recorded in the current configuration file, the purpose of saving the current parameters of the soft switch is achieved, thereby solving the technical problem of low configuration efficiency of vehicle soft switches and thus achieving the technical effect of improving the configuration efficiency of vehicle soft switches.

[0095] The technical solutions of the embodiments of this application will be illustrated below with reference to preferred embodiments.

[0096] Currently, vehicles are equipped with in-vehicle virtual soft switches for features such as AEB and DOW. However, in related technologies, the status of these soft switches cannot be traced, resulting in low efficiency in the configuration of vehicle soft switches.

[0097] To address the aforementioned technical problems, this application proposes a method for configuring a vehicle's soft switch. When the vehicle's infotainment system is powered on, a historical configuration file for the soft switch is retrieved from the system's configuration area. The soft switch is then configured initially according to this historical configuration file. After the initial configuration, when the soft switch is in touch-sensitive mode, the retrieved current parameters are temporarily or permanently written to the system's configuration area or cache area to obtain the current configuration file. The soft switch is then configured again according to this current configuration file. Since the soft switch can operate on the vehicle's infotainment system with the current parameters, and these current parameters can be recorded in the current configuration file, the current parameters of the soft switch can be saved. This solves the technical problem of low configuration efficiency for vehicle soft switches and improves the overall efficiency of vehicle soft switch configuration.

[0098] In this embodiment, the vehicle-mounted ADAS safety function soft-switch control system, which possesses persistent state memory and operation traceability, executes the vehicle-mounted soft-switch control method, allowing the soft switch to be configured according to the current configuration file. For example, Figure 2 This is a schematic diagram of a vehicle-mounted ADAS safety function soft-switch control system with persistent state memory and operation traceability according to an embodiment of this application, as shown below. Figure 2 As shown, the system may include: a front-end visualization interaction layer 201, a storage read / write logic layer 202, and a log read / write logic layer 203. The front-end visualization interaction layer 201 may be equipped with an ADAS soft switch UI module 2011, the storage read / write logic layer 202 may be equipped with a persistent storage module for switch states 2021, and the log read / write logic layer 203 may be equipped with an operation log recording module 2031.

[0099] In this embodiment, the ADAS soft switch UI module 2011 can be deployed on a separate subpage of vehicle safety settings on the vehicle's touchscreen display. The virtual switch has only two display states: in the on state, the slider is docked on the right side of the interface, and the switch background is blue; in the off state, the slider is docked on the left side of the interface, and the switch background is gray. There is no intermediate setting or graded adjustment control. The ADAS soft switch UI module 2011 can also be used to send a standard state change command to the upper-level process after the driver touches the slider and completes the click operation. The change command carries an identifier field and a changed state identifier. The identifier field can be used to distinguish whether the current modification object is an AEB switch or a DOW switch. The state identifier can be 0 to represent off and 1 to represent on.

[0100] In this embodiment, the underlying read / write carrier of the aforementioned persistent switch state storage module 2021 can be an independent security configuration partition partitioned by the vehicle's built-in eMMC storage chip. This partition is unaffected by vehicle system partition formatting or OTA upgrade package overwriting. The partition file system adopts the vehicle's universal EXT4 format. Two independent configuration text files are created within the partition, named aeb_config.txt and down_config.txt respectively. aeb_config.txt corresponds to the AEB switch configuration, and down_config.txt corresponds to the DOW switch configuration. The storage spaces between the files are isolated from each other, and modifying one file will not overwrite the data in the other file. The aforementioned persistent switch state storage module 2021 can be used to compare the checksum at the end of the file with the real-time calculated checksum each time the configuration file is read upon power-on.

[0101] For example, if the checksum at the end of the file does not match the real-time calculated checksum, the configuration file is determined to be corrupted, the factory default startup state is automatically restored, and the configuration exception record is generated by the operation log recording module 2031.

[0102] In this embodiment, the operation log recording module 2031 can be separated from the eMMC storage chip into an independent log storage sub-partition. Log files are stored according to natural dates, with the daily log file naming format being operation_yyyyMMdd.log. The maximum storage capacity of a single file is set to 50MB. Once the capacity limit is reached, a new log file for the next day is automatically created. The minimum local retention time for log data is fixed at 90 days. Logs older than 90 days are automatically and silently deleted in the background to avoid occupying vehicle system storage space. The operation log recording module 2031 can be used to determine the source of the operation when the ADAS soft switch UI module 2011 sends a switch status change command. It only recognizes change commands triggered by manual touch by the user. If the command is identified as a non-manual operation command such as automatic system power-on configuration recovery or default background program reset, the log writing process is skipped. If a manual operation command is identified, a log entry is triggered. Each log entry contains five fields separated by commas: operation time (accurate to the hour, minute, and second, taken from the vehicle's time synchronization module), operation object (AEB / DOW identifier), status value before change, status value after change, and temporary / permanent storage flag.

[0103] Optionally, the hardware configuration of the aforementioned vehicle infotainment system may include: a touchscreen display, an eMMC non-volatile memory chip, a Universal Serial Bus (USB) data output interface, and a Controller Area Network (CAN) communication channel. The aforementioned vehicle infotainment system soft-switch control system with persistent state memory and operation traceability is integrated into the vehicle infotainment system's vehicle settings application (App) as an application-layer software module.

[0104] In this embodiment, by executing the vehicle-mounted ADAS safety function soft switch control method with persistent state memory and operation traceability, the soft switch can be configured according to the current configuration file. For example, Figure 3 This is a flowchart of a vehicle-mounted ADAS safety function soft-switch control method with persistent state memory and operation traceability according to an embodiment of this application, such as... Figure 3 As shown, the method may include the following steps.

[0105] Step S301: The vehicle accessory (Acc) is powered on, and the vehicle's infotainment system starts.

[0106] After the vehicle's Accelerator is powered on and the vehicle's infotainment system starts, step S302 is executed, where the persistent storage module for switch status automatically reads the aeb_config.txt and down_config.txt configuration files from the eMMC partition.

[0107] After the switch state persistent storage module automatically reads the aeb_config.txt and dow_config.txt configuration files in the eMMC partition, step S303 is executed to verify the data in the configuration files.

[0108] If the configuration file data verification is successful, proceed to step S304 to transmit the switch status value to the ADAS soft switch UI module.

[0109] If the configuration file data verification fails, proceed to step S305 to restore the factory default startup state and generate a configuration exception record by the operation log recording module, and write the generated configuration exception record to the exception log.

[0110] After transmitting the switch status value to the ADAS soft switch UI module, step S306 is executed, the screen displays the historical switch status, and the system waits for operation.

[0111] After displaying the historical switch status on the screen and waiting for operation, execute step S307 or step S308 to determine whether it is a manual operation by the driver or the vehicle's Accelerator is powered off.

[0112] If it is determined that the operation is performed manually by the driver, then step S309 is executed, whereby the ADAS soft switch UI module generates a status change command and pops up a storage mode selection pop-up window.

[0113] After the ADAS soft switch UI module generates the state change command and displays the storage mode selection pop-up window, step S310 is executed to determine the storage mode selected by the user. If the selected storage mode is determined to be temporary mode, step S311 is executed to write to the RAM temporary cache. If the selected storage mode is determined to be permanent mode, step S312 is executed to write to the eMMC configuration file and update the verification code.

[0114] After writing to the RAM temporary cache or the eMMC configuration file, execute step S313 to collect all fields of the log.

[0115] After collecting all fields of the log, execute step S314 to write the log file for the day and automatically retain it for 90 days.

[0116] If it is determined that the operation was not performed manually by the driver, then return to step S306.

[0117] After the vehicle's Accelerator is powered off, step S315 is executed, which clears the temporary RAM cache data and continuously saves the permanent configuration files and historical log files in the eMMC partition.

[0118] In this embodiment, by executing the Over-The-Air (OTA) upgrade method, the system application partition can be covered, and the vehicle's OTA system can be upgraded. For example, Figure 4 This is a flowchart of a vehicle infotainment system OTA upgrade method according to an embodiment of this application, such as... Figure 4 As shown, the method may include the following steps.

[0119] Step S401: Trigger the vehicle infotainment system OTA upgrade.

[0120] After triggering the vehicle infotainment OTA system upgrade, execute step S402, where the upgrade only covers the system application partition and isolates the security / log eMMC partition.

[0121] In this embodiment, the upgrade process only covers the system application partition and does not modify the security configuration partition or the log partition.

[0122] After upgrading only the system application partition and isolating the security / log eMMC partition, proceed to step S403. The upgrade is complete, and the vehicle will automatically restart.

[0123] In this embodiment, after the vehicle is automatically restarted, the original switch configuration is automatically read by the persistent storage module of switch status, without requiring the user to repeat the settings.

[0124] In this embodiment, when the vehicle system is powered on, the historical configuration file of the soft switch is obtained from the configuration area of ​​the vehicle system. The soft switch is configured for the first time according to the historical configuration file. Then, when the soft switch is in touch mode after the initial configuration, the obtained current parameters are temporarily or permanently written to the configuration area or cache area of ​​the vehicle system to obtain the current configuration file. After that, the soft switch is configured again according to the current configuration file. Since the soft switch can act on the vehicle system under the current parameters, and the current parameters can be recorded in the current configuration file, the purpose of saving the current parameters of the soft switch is achieved, thereby solving the technical problem of low configuration efficiency of vehicle soft switches and thus achieving the technical effect of improving the configuration efficiency of vehicle soft switches.

[0125] According to an embodiment of this application, a soft-switching configuration device for a vehicle is also provided. It should be noted that this soft-switching configuration device for a vehicle can be used to execute a soft-switching configuration method for a vehicle according to one of the embodiments.

[0126] Figure 5 This is a schematic diagram of a soft-switch configuration device for a vehicle according to an embodiment of this application. Figure 5 As shown, the soft switch configuration device 500 of the vehicle may include: an acquisition unit 501, a first configuration unit 502, a writing unit 503, and a second configuration unit 504.

[0127] The acquisition unit 501 is used to acquire the historical configuration file of the soft switch of the vehicle system from the configuration area of ​​the vehicle system in response to the vehicle system being powered on. The historical configuration file is used to record the historical parameters of the soft switch.

[0128] The first configuration unit 502 is used to initially configure the soft switch according to the historical configuration file, wherein the soft switch operates on the vehicle system under the historical parameters.

[0129] The writing unit 503 is used to respond to the soft switch being in a touch state after initial configuration, obtain the current parameters of the soft switch, and temporarily or permanently write the current parameters to the corresponding writing area of ​​the vehicle system to obtain the current configuration file, wherein the writing area is the configuration area or cache area of ​​the vehicle system.

[0130] The second configuration unit 504 is used to reconfigure the soft switch according to the current configuration file, wherein the soft switch operates on the vehicle system under the current parameters.

[0131] Optionally, the first configuration unit 502 may include: a verification module for verifying the historical configuration file and obtaining a verification result; and a configuration module for initially configuring the soft switch according to the historical configuration file in response to the verification result indicating that the historical configuration file has passed verification.

[0132] Optionally, the verification module may include: a calculation submodule, used to determine the inherent verification parameters already existing in the historical configuration file, and to perform verification calculations on the historical configuration file to obtain real-time verification parameters for the historical configuration file; a first verification submodule, used to verify the historical configuration file in response to the inherent verification parameters being the same as the real-time verification parameters, and to obtain a verification result indicating that the historical configuration file has passed verification; and a second verification submodule, used to verify the historical configuration file in response to the inherent verification parameters being different from the real-time verification parameters, and to obtain a verification result indicating that the historical configuration file has failed verification.

[0133] Optionally, the current configuration file includes: a first current configuration file and a second current configuration file. The writing unit 503 may include: a first writing module, used to obtain the current parameter and temporarily write the current parameter to the cache area in response to the soft switch being in the touch state after initial configuration and the current parameter being in the temporary writing mode, to obtain the first current configuration file; and a second writing module, used to obtain the current parameter and permanently write the current parameter to the configuration area in response to the soft switch being in the touch state after initial configuration and the current parameter being in the permanent writing mode, to obtain the second current configuration file.

[0134] Optionally, the vehicle's soft-switch configuration device 500 may further include: a deletion unit, configured to delete the first current configuration file from the cache area in response to the vehicle system being powered down and the current configuration file being a first current configuration file; and a replacement unit, configured to replace the historical configuration file with the second current configuration file from the configuration area in response to the vehicle system being powered down and the current configuration file being a second current configuration file.

[0135] Optionally, the soft switch configuration device 500 of the vehicle may further include: a generation unit, configured to generate log data by monitoring touch operations used to put the soft switch into the touch state in response to the soft switch being in a touch state after initial configuration; and a retention unit, configured to write the log data into a configuration area and retain the written log data during a retention period, wherein the write position of the log data in the configuration area is different from the write position of the historical configuration file in the configuration area.

[0136] In this embodiment, a vehicle soft switch configuration device is provided. The device may include: an acquisition unit, configured to acquire a historical configuration file of the soft switch of the vehicle system from the configuration area of ​​the vehicle system in response to the vehicle system being powered on, wherein the historical configuration file is used to record historical parameters of the soft switch; a first configuration unit, configured to initially configure the soft switch according to the historical configuration file, wherein the soft switch operates on the vehicle system under the historical parameters; a writing unit, configured to acquire the current parameters of the soft switch in response to the soft switch being in a touch state after initial configuration, and temporarily or permanently write the current parameters to the corresponding writing area of ​​the vehicle system to obtain the current configuration file, wherein the writing area is the configuration area or cache area of ​​the vehicle system; and a second configuration unit, configured to reconfigure the soft switch according to the current configuration file, wherein the soft switch operates on the vehicle system under the current parameters. This achieves the purpose of saving the current parameters of the soft switch, thereby solving the technical problem of low configuration efficiency of vehicle soft switches and thus achieving the technical effect of improving the configuration efficiency of vehicle soft switches.

[0137] According to an embodiment of this application, a processor is also provided for running a program, wherein the program is executed by the processor to perform the methods described in the embodiment.

[0138] According to an embodiment of this application, an electronic device is also provided. Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application, such as... Figure 6 As shown, the electronic device 600 may include a memory 610 and a processor 620, wherein the memory 610 is used to store an executable program; and the processor 620 is used to run the program stored in the memory 610, wherein the program executes the methods in various embodiments of this application when it runs.

[0139] In this application, "multiple" refers to two or more.

[0140] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0141] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0142] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0143] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. This computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method described in the embodiments.

[0144] Computer-readable storage media, also known as computer storage media, may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. These propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable storage media can transmit, propagate, or transfer programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0145] The program code contained in a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, radio frequency, or any suitable combination thereof.

[0146] According to an embodiment of this application, a computer program product is also provided, which includes a computer program, wherein the computer program, when executed by a processor, implements the method in the embodiment.

[0147] According to an embodiment of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the method described in the embodiment.

[0148] According to an embodiment of this application, a computer program is also provided, which, when executed by a processor, implements the method described in the embodiment.

[0149] According to an embodiment of this application, a vehicle is also provided, including the electronic equipment described in the embodiment of this application.

[0150] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0151] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0152] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0153] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0154] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0155] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for configuring a soft switch for a vehicle, characterized in that, include: In response to the vehicle's infotainment system being powered on, the historical configuration file of the soft switch of the infotainment system is obtained from the configuration area of ​​the infotainment system, wherein the historical configuration file is used to record the historical parameters of the soft switch; According to the historical configuration file, the soft switch is configured for the first time, wherein the soft switch operates on the vehicle system under the historical parameters; In response to the soft switch being in a touch state after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file, wherein the write area is the configuration area or cache area of ​​the vehicle system; According to the current configuration file, the soft switch is reconfigured, wherein the soft switch operates on the vehicle system under the current parameters.

2. The method according to claim 1, characterized in that, According to the historical configuration file, the initial configuration of the soft switch includes: The historical configuration file is verified to obtain the verification result; In response to the verification result indicating that the historical configuration file has passed verification, the soft switch is configured for the first time according to the historical configuration file.

3. The method according to claim 2, characterized in that, The historical configuration file is validated to obtain the validation results, including: The inherent verification parameters that already exist in the historical configuration file are determined, and the historical configuration file is verified and calculated to obtain the real-time verification parameters for the historical configuration file. In response to the fact that the inherent verification parameter is the same as the real-time verification parameter, the historical configuration file is verified, and the verification result indicates that the historical configuration file has passed the verification. In response to the difference between the inherent verification parameters and the real-time verification parameters, the historical configuration file is verified, and the verification result indicates that the historical configuration file verification failed.

4. The method according to claim 1, characterized in that, The current configuration file includes: a first current configuration file and a second current configuration file. In response to the soft switch being in a touch state after initial configuration, the current parameters of the soft switch are obtained, and the current parameters are temporarily or permanently written to the corresponding write area of ​​the vehicle system to obtain the current configuration file, which includes: In response to the soft switch being in the touch state after initial configuration, and the current parameter being written in temporary write mode, the current parameter is obtained and temporarily written to the cache area to obtain the first current configuration file; In response to the soft switch being in the touch state after initial configuration and the current parameter being written in permanent write mode, the current parameter is obtained and permanently written to the configuration area to obtain the second current configuration file.

5. The method according to claim 4, characterized in that, The method further includes: In response to the vehicle system being powered down and the current configuration file being the first current configuration file, the first current configuration file is deleted from the cache area; In response to the vehicle system being in the power-down state and the current configuration file being the second current configuration file, the historical configuration file is replaced with the second current configuration file from the configuration area.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: In response to the soft switch being in the touch state after initial configuration, log data is generated by monitoring touch operations used to put the soft switch in the touch state; The log data is written to the configuration area, and the written log data is retained during the retention period, wherein the write position of the log data in the configuration area is different from the write position of the historical configuration file in the configuration area.

7. A soft-switching configuration device for a vehicle, characterized in that, include: The acquisition unit is configured to, in response to the vehicle's infotainment system being powered on, acquire the historical configuration file of the soft switch of the infotainment system from the configuration area of ​​the infotainment system, wherein the historical configuration file is used to record the historical parameters of the soft switch; The first configuration unit is used to initially configure the soft switch according to the historical configuration file, wherein the soft switch operates on the vehicle system under the historical parameters; The writing unit is used to respond to the soft switch being in a touch state after initial configuration, to obtain the current parameters of the soft switch, and to temporarily or permanently write the current parameters to the writing area corresponding to the vehicle system to obtain the current configuration file, wherein the writing area is the configuration area or cache area of ​​the vehicle system; The second configuration unit is used to reconfigure the soft switch according to the current configuration file, wherein the soft switch operates on the vehicle system under the current parameters.

8. A processor, characterized in that, The processor is used to run a program, wherein the program is executed by the processor to perform the method according to any one of claims 1 to 6.

9. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 1 to 6.

Images