A vehicle identification lamp failure response method, vehicle, and electronic device

Abstract

The application relates to a vehicle identification lamp fault response method, a vehicle and an electronic device. The method comprises the following steps: acquiring fault information of a vehicle identification lamp, wherein the fault information comprises a fault type and a fault number; determining a fault response strategy corresponding to the fault information according to a design mode of the vehicle identification lamp, wherein the design mode reflects the influence of a single vehicle identification lamp fault on other vehicle identification lamps; and executing the fault response strategy. According to the technical scheme, the fault response strategy is determined in combination with the design mode of the vehicle identification lamp and the fault information, the fault can be responded to under the condition of meeting the design characteristics of the vehicle identification lamp, and the driving safety and the driving experience are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method for dealing with vehicle indicator light malfunctions, a vehicle, and electronic equipment. Background Technology

[0002] Vehicle indicator lights are lights on vehicles used to alert other road users. During use, vehicle indicator lights may malfunction, such as failing to illuminate. However, current technology cannot provide a reasonable handling strategy when vehicle indicator lights malfunction, leading to situations that could result in driving safety issues, violations of regulations, or other unknown penalties, thus affecting driving safety and the driving experience. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a method for dealing with vehicle indicator light malfunctions, a vehicle, and electronic equipment that can deal with malfunctions while conforming to the design characteristics of vehicle indicator lights, thereby improving driving safety and driving experience.

[0004] To achieve the above objectives, this application provides a method for dealing with vehicle indicator light malfunctions, including: Obtain fault information of vehicle indicator lights, including fault type and number of faults; Based on the design of the vehicle indicator light, a fault response strategy corresponding to the fault information is determined, wherein the design reflects the impact of a single vehicle indicator light malfunction on other vehicle indicator lights. Implement the aforementioned fault response strategy.

[0005] In some embodiments, determining the fault response strategy corresponding to the fault information based on the design of the vehicle indicator light includes: Based on the design of the vehicle indicator lights, determine the fault conditions that the fault information meets; The fault response strategy is determined based on the fault conditions.

[0006] In some embodiments, the design of the vehicle indicator light includes a first design and a second design. The first design reflects that a malfunction of a single vehicle indicator light will affect the operation of other vehicle indicator lights, while the second design reflects that a malfunction of a single vehicle indicator light will not affect the operation of other vehicle indicator lights. The fault conditions corresponding to the first design method and the second design method are different.

[0007] In some embodiments, when the vehicle indicator light is designed in the first design manner, determining the fault response strategy based on the fault conditions includes: When the fault condition satisfied by the fault information is that the fault type indicates that the vehicle indicator light is malfunctioning, the fault response strategy is determined to be the first response strategy, and the first response strategy is at least used to control vehicle functions. When the fault condition met by the fault information is that the fault type indicates that the vehicle indicator light has a non-indicative abnormality, the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

[0008] In some embodiments, when the vehicle indicator light is designed in the second design manner, determining the fault response strategy based on the fault conditions includes: The fault information satisfies the fault condition that the fault type indicates that the vehicle indicator light is malfunctioning, and the number of faults is equal to the total number of vehicle indicator lights. In this case, the fault response strategy is determined to be the first response strategy, which is used at least to control vehicle functions. If the fault information meets the fault conditions that the fault type indicates that the vehicle indicator light has a non-indicative abnormality, or if the number of faults is less than the total number of vehicle indicator lights, then the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

[0009] In some embodiments, when the fault response strategy is used at least to manage vehicle functions, executing the fault response strategy includes: Output maintenance reminder information; The number of times a repair is not completed is accumulated each time it is confirmed that the repair has not been completed. When the number of times the repair is not completed reaches a preset number, the preset vehicle function is disabled; And / or, when the fault response strategy is used to provide an alert function, executing the fault response strategy includes: A maintenance reminder message is output each time it is confirmed that the maintenance is not completed.

[0010] In some embodiments, the confirmation that the repair is not complete includes: When the vehicle is powered on or the preset vehicle function is activated, determine whether the fault information matches the fault conditions corresponding to the currently executed fault response strategy. If the conditions are met, then the repair is confirmed to be incomplete.

[0011] In some embodiments, the method further includes: During the execution of the fault response strategy, the fault information of the vehicle indicator light is monitored; When the fault information indicates that the vehicle indicator light has returned to normal, the fault response strategy is stopped; or, when the fault information changes, the fault response strategy is adjusted.

[0012] This application also provides a vehicle, including vehicle indicator lights, a body domain controller, and a driver domain controller; The vehicle body domain controller, connected to the vehicle indicator light, is configured to acquire fault information and configuration information of the vehicle indicator light and send them to the driving domain controller. The driving domain controller, connected to the body domain controller, is configured to perform the steps of the method described in any of the preceding descriptions.

[0013] This application also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of any of the methods described above.

[0014] Based on the above, this application discloses a method, vehicle, and electronic device for handling vehicle indicator light malfunctions. The method includes: acquiring malfunction information of the vehicle indicator lights, including malfunction type and number of malfunctions; determining a malfunction response strategy corresponding to the malfunction information based on the design of the vehicle indicator lights, wherein the design reflects the impact of a single vehicle indicator light malfunction on other vehicle indicator lights; and executing the malfunction response strategy. The technical solution of this application, by combining the design of the vehicle indicator lights and the malfunction information to determine the malfunction response strategy, can handle malfunctions while adhering to the design characteristics of the vehicle indicator lights, thus improving driving safety and driving experience. Attached Figure Description

[0015] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is a flowchart illustrating a method for handling vehicle indicator light malfunctions according to one embodiment.

[0017] Figure 2 This is another flowchart illustrating a method for handling vehicle indicator light malfunctions according to one embodiment.

[0018] Figure 3 This is another flowchart illustrating a method for dealing with vehicle indicator light malfunctions according to one embodiment.

[0019] Figure 4 This is a structural schematic diagram of a vehicle according to one embodiment.

[0020] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment.

[0021] Reference numerals: 401-Vehicle identification light; 402-Body domain controller; 403-Driver domain controller; 310-Processor; 311-Memory; 312-Network interface; 313-Bus system. Detailed Implementation

[0022] The specific embodiments of this application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some, not all, of the embodiments of this application. Based on the description of this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application.

[0023] In the description of this application, unless otherwise expressly specified and limited, the terms "set," "install," "connect," etc., 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. Those skilled in the art can understand the specific meaning of the above terms based on the specific circumstances.

[0024] The terms “first,” “second,” “third,” etc., are used merely to distinguish numerical values ​​or elements with similar properties, rather than to indicate or imply relative importance or a specific order.

[0025] The terms “include,” “comprising,” or any other variation thereof are intended to cover non-exclusive inclusion, which includes not only the elements listed but also other elements not expressly listed.

[0026] In this application, vehicle identification lights can be installed on at least one of the front, rear, left, and right sides of the vehicle. To achieve comprehensive identification, vehicle identification lights can be installed on each side of the vehicle, with two or more lights on each side. The rear vehicle identification lights are used to warn drivers of following vehicles and guide them to avoid risks. The front vehicle identification lights are mainly used to indicate pedestrians, such as when a vehicle starts moving or when a vehicle is approaching and needs to be crossed. The left and right-facing vehicle identification lights are used to warn drivers when the vehicle is turning left or right and to provide oncoming vehicle warnings to adjacent lanes during automatic lane changes.

[0027] Each vehicle's side marker lights can be independently troubleshooted using the methods described in this application to ensure that each side's marker lights function as their corresponding indicator lights. Considering that the warning effect of the rear vehicle marker lights is relatively greater than that of the other side marker lights, in some preferred embodiments, it is preferable to apply the methods described in this application to at least the rear vehicle marker lights.

[0028] Figure 1 This is a flowchart illustrating a method for handling vehicle indicator light malfunctions according to one embodiment. Figure 1 As shown, the method for dealing with vehicle indicator light malfunctions in this application includes: Step S1: Obtain fault information of vehicle indicator lights, including fault type and number of faults.

[0029] The fault type indicates the specific malfunction of each vehicle's indicator light, such as the indicator light failing to illuminate, failing to turn off, or exhibiting abnormal flashing. The fault count represents the number of faulty vehicle indicator lights, which can be determined by statistically analyzing the location of the faulty indicator lights.

[0030] Fault information can be automatically detected when the vehicle is powered on, or during the use of preset vehicle functions (functions that require indication via vehicle indicator lights).

[0031] In some embodiments, preset vehicle functions include driver assistance functions and / or autonomous driving functions.

[0032] Driver assistance functions (Levels 0-2): The driver remains the primary driver. The vehicle system only provides lateral or longitudinal assistance control. The driver must monitor road conditions throughout the journey and be ready to take over at any time, assuming full responsibility for driving. Driver assistance functions focus on reducing driver fatigue (such as adaptive cruise control and lane keeping assist).

[0033] Autonomous driving functions (Level 3-5): Under designed operating conditions, the vehicle system is the driving agent. Level 3 involves the system taking over under specific conditions, with the driver required to take over only when requested by the system. Levels 4-5 involve the system performing all driving tasks under specific or all conditions. Autonomous driving functions focus on independently completing driving tasks in specific or all scenarios, including emergency handling.

[0034] It should be noted that the solution method of this application can be used independently for the vehicle identification lights on each side of the vehicle. Therefore, the vehicle identification lights mentioned in the steps of the solution method of this application refer to the vehicle identification lights on the same side of the vehicle.

[0035] Step S2: Based on the design of the vehicle indicator lights, determine the fault response strategy corresponding to the fault information. The design reflects the impact of a single vehicle indicator light malfunction on other vehicle indicator lights.

[0036] The design of the vehicle marker lights involves the circuit design of the marker lights on one side applying the solution method of this application, reflecting the impact of a single vehicle marker light malfunction on other vehicle marker lights. For example, if marker light A and marker light B share a power supply and driver at the rear of the vehicle, a malfunction in marker light A will affect marker light B, causing it to malfunction as well. Alternatively, if marker light A and marker light B each use their own power supply and driver, a malfunction in marker light A will not affect marker light B and will not cause it to malfunction.

[0037] The design of vehicle marker lights can be implemented by directly storing the marker data, which can be retrieved each time the vehicle marker light is used. Alternatively, the design of vehicle marker lights can be implemented by detecting the pin data or interface data in the design circuit of the vehicle marker light. This method can be performed when the vehicle marker light is used for the first time and the detection results can be stored for subsequent use, or the detection can be performed again each time the vehicle marker light is used.

[0038] When different design approaches are adopted, the interaction between vehicle indicator lights varies, resulting in different impacts on their normal indication function even when the same type and number of faults occur. Therefore, determining fault response strategies based on fault information and the design approach of the vehicle indicator lights can ensure that the response strategies align with the design characteristics of the vehicle indicator lights, making them more reasonable and accurate, and reducing the possibility of mishandling or omissions.

[0039] Step S3: Implement the fault response strategy.

[0040] The fault handling strategy can be used to control vehicle functions and / or provide alerts. For the current design of vehicle indicator lights, if an analysis shows that a fault in the vehicle indicator light has a significant impact on the safe use of vehicle functions, then the fault handling strategy should at least be used to control vehicle functions, including directly disabling preset vehicle functions and disabling preset vehicle functions under specific conditions. In addition, the fault handling strategy can also be used to provide alerts so that users can intervene in the fault handling process in a timely manner. For the current design of vehicle indicator lights, if an analysis shows that a fault in the vehicle indicator light has a minor impact on the safe use of vehicle functions, then the fault handling strategy should at least be used to provide alerts, in which case disabling vehicle functions may not be necessary.

[0041] In summary, the technical solution of this application combines the design of the vehicle indicator light with fault information to determine the fault response strategy, which can deal with faults while conforming to the design characteristics of the vehicle indicator light, thus improving driving safety and driving experience.

[0042] In some embodiments, step S2, determining the fault response strategy corresponding to the fault information based on the design of the vehicle indicator lights, includes: Step S21: Determine the fault conditions that the fault information meets based on the design of the vehicle indicator lights; Step S22: Determine the fault response strategy based on the fault conditions.

[0043] Here, fault conditions refer to the conditions satisfied by the fault type and / or the number of faults. For the same design approach, different fault conditions reflect the degree of impact of the fault on the safe use of the vehicle's functions; therefore, different fault conditions correspond to different fault response strategies. Based on the setting of fault conditions, fault response strategies can be further refined and precise under the corresponding design approach.

[0044] In some embodiments, the design of vehicle indicator lights includes a first design and a second design, but is not limited to two. Different design methods result in different impacts on other vehicle indicator lights when a single vehicle indicator light malfunctions, and the fault conditions corresponding to the first and second design methods are different. Thus, by setting different fault conditions based on the mutual influence of vehicle indicator light malfunctions, fault response strategies can be applied to different design methods, improving the adaptability of fault response.

[0045] In some embodiments, the first design approach reflects the situation where a failure of a single vehicle indicator light affects the operation of other vehicle indicator lights. This design approach can be referred to as a "single-failure light," for example, in a dual-lamp, single-channel configuration where a failure of a single vehicle indicator light causes a failure of all vehicle indicator lights.

[0046] In some embodiments, the second design reflects that a failure of a single vehicle indicator light does not affect the operation of other vehicle indicator lights. This design can be called a "dual or multiple failure light," for example, dual lights with dual channels or multiple lights with multiple channels. A failure of a single vehicle indicator light will not cause all vehicle indicator lights to fail; only when all vehicle indicator lights fail will the entire system fail.

[0047] In some embodiments, when the vehicle indicator light is designed in the first design manner, step S22, determining the fault response strategy based on the fault conditions, includes: When the fault condition met by the fault information is that the fault type indicates that the vehicle indicator light is malfunctioning, the fault response strategy is determined to be the first response strategy. The first response strategy is used to control vehicle functions at least. When the fault condition met by the fault information is that the fault type indicator light of the vehicle is experiencing a non-indicative abnormality, the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

[0048] Among them, abnormal indication faults include those that cannot be turned on or off, which significantly affect the indication function. Non-abnormal indication faults include those that have less impact on the indication function, such as those that cannot be turned on or off, for example, those that flicker or flicker at a frequency within a preset range, which prevent the indicator lights from remaining constantly lit. When non-abnormal indication faults occur, the vehicle indicator lights still have an indication function.

[0049] When an abnormal fault occurs, it has a significant impact on the safe use of vehicle functions. Therefore, a first response strategy is adopted to at least control vehicle functions, including directly disabling preset vehicle functions and disabling preset vehicle functions when specific conditions are met. In addition, the first response strategy can also be used to provide an alert function so that users can intervene in the fault handling process in a timely manner and eliminate safety hazards as soon as possible.

[0050] When a non-indicative fault occurs and has a minor impact on the safe use of vehicle functions, a second response strategy is adopted to at least provide an alert function, without involving the disabling of vehicle functions.

[0051] In the case of the first design method, the failure of a single vehicle indicator light will cause all vehicle indicator lights to fail. Therefore, it is necessary to only determine whether the fault type meets the fault conditions, select the corresponding fault response strategy according to different fault types, simplify the judgment process, and at the same time, provide a reasonable fault response strategy.

[0052] In some embodiments, when the vehicle indicator light is designed in the second design manner, step S22, determining the fault response strategy based on the fault conditions, includes: When the fault information meets the fault conditions that the fault type indicates that the vehicle indicator light is malfunctioning and the number of faults is equal to the total number of vehicle indicator lights, the fault response strategy is determined to be the first response strategy. The first response strategy is used to control vehicle functions at least. If the fault information meets the fault conditions, such as the fault type indicating that the vehicle indicator light has a non-indicative abnormality, or the number of faults is less than the total number of vehicle indicator lights, then the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

[0053] Specifically, when the number of malfunctioning indicators equals the total number of vehicle indicator lights, it indicates that the entire vehicle indicator light system has lost its indicative function, significantly impacting the safe use of the vehicle. Therefore, a first response strategy is adopted to at least control vehicle functions, including directly disabling preset vehicle functions and disabling preset vehicle functions under specific conditions. Furthermore, the first response strategy can also provide a reminder function so that users can intervene in the fault handling process in a timely manner and eliminate safety hazards as soon as possible. Specific conditions include the vehicle indicator lights failing to complete repairs within a preset number of repair attempts.

[0054] When a non-indicative fault occurs, or the number of faults is less than the total number of vehicle indicator lights, it indicates that the fault type of the vehicle indicator lights has little impact on the indication function or there are no faults, and the impact on the safe use of vehicle functions is small. In this case, a second response strategy is adopted to at least provide a reminder function, without involving the disabling of vehicle functions.

[0055] For the case of the second design method, the failure of a single vehicle indicator light will not lead to the failure of all vehicle indicator lights. Only when all vehicle indicator lights fail will there be an overall failure. Therefore, it is necessary to comprehensively judge whether the failure type and number of failures meet the failure conditions, and select the corresponding failure response strategy according to different combinations of failure types and numbers of failures. This will avoid mishandling or omissions caused by judging based on a single piece of information, and at the same time, provide a reasonable failure response strategy.

[0056] In some embodiments, when the fault response strategy is used at least to control vehicle functions, step S3, executing the fault response strategy, includes: Output maintenance reminder information; The number of times a repair is not completed is accumulated each time it is confirmed that the repair has not been completed. When the number of times a vehicle fails to complete a repair reaches a preset number, the preset vehicle functions will be disabled.

[0057] The preset vehicle functions are those that need to be indicated to other road users via vehicle indicator lights. The fault response strategy is used at least to control vehicle functions; that is, when the first response strategy is adopted, the fault response strategy can be used simultaneously to control vehicle functions and provide alerts, in order to comprehensively promote fault elimination.

[0058] During the application of preset vehicle functions, if it is determined that a first response strategy for controlling vehicle functions needs to be executed, a maintenance reminder message can be output immediately or at the latest at the end of the application, so that the user can be informed of the fault status in a timely manner. Subsequently, each time the vehicle is powered on or the preset vehicle function is activated, it is confirmed whether the fault has not been repaired. Specifically, this can be determined by judging the fault information. If the fault information still exists and still meets the fault conditions for executing the first response strategy, it is confirmed that the repair is incomplete, and one instance of incomplete repair is counted. When the number of incomplete repairs reaches a preset number, the preset vehicle function is disabled to ensure driving safety. The preset number of times can be selected and determined based on safety, user needs, etc., for example, it can be set to 3 times.

[0059] In some embodiments, when the fault response strategy is used to provide an alert function, step S3, executing the fault response strategy, includes: A maintenance reminder message is output each time it is confirmed that the maintenance is not completed.

[0060] Among them, when the fault response strategy is used to provide a reminder function, that is, when the second response strategy is adopted, the user can be alerted to the fault situation by reminding them when the vehicle indicator light function has not completely failed. At the same time, the user can be reminded to carry out timely maintenance to improve driving safety.

[0061] During the application of preset vehicle functions, if it is determined that a second response strategy for providing reminders needs to be executed, a maintenance reminder message can be output immediately or at the latest at the end of the application, so that the user can be informed of the fault status in a timely manner. Subsequently, each time the vehicle is powered on or the preset vehicle functions are activated, it is confirmed whether the fault has not been repaired. Specifically, this can be determined by judging the fault information. If the fault information still exists and still meets the fault conditions for executing the second response strategy, it is confirmed that the repair is not complete, and the maintenance reminder message continues to be output, but the vehicle function is not disabled.

[0062] The above solutions provide corresponding fault response strategies for different design methods and different fault conditions. They can provide differentiated safety degradation strategies to ensure that the fault response strategies reasonably meet the requirements of safe driving, reduce the impact on users' use of vehicle functions, and improve the user experience.

[0063] In some embodiments, the method of this application further includes the step of: During the execution of fault response strategies, monitor the fault information of vehicle indicator lights; Stop implementing the fault response strategy when the fault information indicates that the vehicle's indicator lights have returned to normal, or adjust the fault response strategy when the fault information changes.

[0064] As the vehicle moves, the status of its indicator lights may change. For example, a sudden bump might cause a temporary circuit failure in the indicator light, which may return to normal once the driving surface is stable. Alternatively, a previously functioning indicator light might malfunction during driving due to issues such as temperature or contact problems. Furthermore, the indicator light will usually return to normal after repair. Therefore, monitoring the indicator light's fault information during the implementation of fault response strategies allows for timely cessation or adjustment of these strategies, making the fault response process more intelligent.

[0065] The fault information can be confirmed when the vehicle's indicator lights return to normal and remain so for a certain duration (e.g., 500ms or 1-3 seconds). At this point, the current fault handling strategy should be stopped. Stopping the current fault handling strategy includes stopping the output of maintenance reminder messages. If the currently executed fault handling strategy is the first strategy, stopping the current fault handling strategy also includes resetting the currently accumulated number of uncompleted repairs to zero.

[0066] In addition to maintenance and recovery mechanisms, fault response strategies can also be adjusted. For example, when two indicator lights go out instead of one, the fault conditions change, and the response strategy can be adjusted from providing a reminder to controlling vehicle functions to provide more timely driving safety assurance. Alternatively, when two indicator lights go out instead of one, the fault conditions change, and the response strategy can be adjusted from controlling vehicle functions to providing a reminder, allowing users to use vehicle functions normally and ensuring a smooth driving experience.

[0067] The following provides a general explanation of the specific procedures for when the vehicle indicator light design is the first design method. Please refer to [link / reference]. Figure 2 Response methods include: Step S201: Determine the design method of the vehicle indicator light as the first design method. This step can be performed when the vehicle function is first applied, or it can be performed every time the vehicle function is applied.

[0068] Step S202: Obtain fault information for the vehicle's indicator lights. This is the same as step S1 above and will not be repeated.

[0069] Step S203: Determine the fault conditions that the fault information meets. This is the same as step S21 above and will not be repeated. Based on the fault conditions met by the fault information, select to execute either step S204 or step S205.

[0070] Step S204: When the fault condition is met, indicating that the vehicle indicator light is malfunctioning, output a maintenance reminder message; each time maintenance is not completed, accumulate the number of times maintenance is not completed; when the number of times maintenance is not completed reaches a preset number, disable the preset vehicle function.

[0071] Step S205: When the fault condition is that the fault type indicator light of the vehicle is not an indication of an abnormality, a maintenance reminder message is output each time it is confirmed that the repair has not been completed.

[0072] In the above response process, the design method based on the vehicle indicator light is the first design method. The corresponding fault response strategy is executed according to the fault conditions satisfied by the fault type. When adopting the first design method, a response strategy that conforms to the characteristics can be provided for the fault, thereby improving driving safety and driving experience.

[0073] The following provides a general explanation of the specific procedures for handling vehicle identification lights when the second design method is used. Please refer to... Figure 3 Response methods include: Step S301: Determine the design method of the vehicle indicator light as the second design method. This step can be performed when the vehicle function is first applied, or it can be performed every time the vehicle function is applied.

[0074] Step S302: Obtain fault information for the vehicle's indicator lights. This is the same as step S1 above and will not be repeated.

[0075] Step S303: Determine the fault conditions that the fault information meets. This is the same as step S21 described above and will not be repeated. Based on the fault conditions met by the fault information, select to execute either step S304 or step S305.

[0076] Step S304: When the fault condition is met, the fault type indicates that the vehicle indicator light is malfunctioning, and the number of faults is equal to the total number of vehicle indicator lights, output a maintenance reminder message; each time it is confirmed that the maintenance is not completed, accumulate the number of times the maintenance is not completed; when the number of times the maintenance is not completed reaches a preset number, disable the preset vehicle function.

[0077] Step S305: When the fault condition is met, the fault type indicates that the vehicle indicator light has a non-indicating abnormality, or the number of faults is less than the total number of vehicle indicator lights, a maintenance reminder message is output each time it is confirmed that the maintenance is not completed.

[0078] In the above response process, the design method based on the vehicle indicator light is the second design method. The corresponding fault response strategy is executed according to the fault conditions satisfied by the fault type and the number of faults. When adopting the second design method, a response strategy that conforms to the characteristics can be provided for the fault, reducing mishandling and omissions, and improving driving safety and driving experience.

[0079] Figure 4 This is a structural schematic diagram of a vehicle according to one embodiment. Figure 4 As shown, the vehicle in this application includes a vehicle identification light 401, a body domain controller 402, and a driver domain controller 403.

[0080] The vehicle domain controller 402 is connected to the vehicle indicator light 401 and is configured to acquire fault information and configuration information of the vehicle indicator light 401 and send them to the driver domain controller 403.

[0081] The driving domain controller 403, connected to the body domain controller 402, is configured to perform the steps described in any of the above embodiments. The steps described in any of the above embodiments are detailed in the embodiments described above and will not be repeated here.

[0082] This application also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method described in any of the above embodiments.

[0083] like Figure 5 As shown, the electronic device includes: a processor 310 and a memory 311 storing a computer program; wherein, Figure 5 The processor 310 shown in the diagram does not indicate that there is only one processor 310, but only indicates the positional relationship of the processor 310 relative to other devices. In practical applications, there can be one or more processors 310; similarly, Figure 5 The memory 311 illustrated herein has the same meaning, that is, it is only used to indicate the positional relationship of memory 311 relative to other devices. In practical applications, there can be one or more memories 311. When the processor 310 runs the computer program, the above method is implemented.

[0084] The electronic device may also include at least one network interface 312. The various components of the electronic device are coupled together via a bus system 313. It is understood that the bus system 313 is used to implement communication between these components. In addition to a data bus, the bus system 313 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 5 The general designated all buses as Bus System 313.

[0085] The memory 311 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 311 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0086] The memory 311 in this embodiment of the invention is used to store various types of data to support the operation of the electronic device. Examples of this data include: any computer programs used to operate on the electronic device, such as operating systems and applications; contact data; phonebook data; messages; pictures; videos, etc. The operating system includes various system programs, such as a framework layer, core library layer, driver layer, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications, such as media players, browsers, etc., used to implement various application services. Here, the program implementing the method of this embodiment of the invention can be included in the application.

[0087] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in any of the above embodiments.

[0088] Computer-readable storage media can be magnetic random access memory (FRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc. When a computer program stored in the computer-readable storage medium is executed by a processor, it implements the methods described in the above embodiments. For the specific steps implemented when the computer program is executed by the processor, please refer to [link to relevant documentation]. Figure 1 The description of the illustrated embodiments will not be repeated here.

[0089] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims

1. A method for dealing with vehicle indicator light malfunctions, characterized in that, include: Obtain fault information of vehicle indicator lights, including fault type and number of faults; Based on the design of the vehicle indicator light, a fault response strategy corresponding to the fault information is determined, wherein the design reflects the impact of a single vehicle indicator light malfunction on other vehicle indicator lights. Implement the aforementioned fault response strategy.

2. The method according to claim 1, characterized in that, The step of determining the fault response strategy corresponding to the fault information based on the design of the vehicle indicator light includes: Based on the design of the vehicle indicator lights, determine the fault conditions that the fault information meets; The fault response strategy is determined based on the fault conditions.

3. The method according to claim 2, characterized in that, The design of the vehicle indicator lights includes a first design and a second design. The first design reflects that a malfunction of a single vehicle indicator light will affect the operation of other vehicle indicator lights, while the second design reflects that a malfunction of a single vehicle indicator light will not affect the operation of other vehicle indicator lights. The fault conditions corresponding to the first design method and the second design method are different.

4. The method according to claim 3, characterized in that, When the vehicle indicator light is designed in the first design manner, determining the fault response strategy based on the fault conditions includes: When the fault condition satisfied by the fault information is that the fault type indicates that the vehicle indicator light is malfunctioning, the fault response strategy is determined to be the first response strategy, and the first response strategy is at least used to control vehicle functions. When the fault condition met by the fault information is that the fault type indicates that the vehicle indicator light has a non-indicative abnormality, the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

5. The method according to claim 3, characterized in that, When the vehicle identification light is designed using the second design method, determining the fault response strategy based on the fault conditions includes: The fault information satisfies the fault condition that the fault type indicates that the vehicle indicator light is malfunctioning, and the number of faults is equal to the total number of vehicle indicator lights. In this case, the fault response strategy is determined to be the first response strategy, which is used at least to control vehicle functions. If the fault information meets the fault conditions that the fault type indicates that the vehicle indicator light has a non-indicative abnormality, or if the number of faults is less than the total number of vehicle indicator lights, then the fault response strategy is determined to be the second response strategy, which is used to provide a reminder function.

6. The method according to any one of claims 1 to 5, characterized in that, When the fault response strategy is used at least to control vehicle functions, executing the fault response strategy includes: Output maintenance reminder information; The number of times a repair is not completed is accumulated each time it is confirmed that the repair has not been completed. When the number of times the repair is not completed reaches a preset number, the preset vehicle function is disabled; And / or, when the fault response strategy is used to provide an alert function, executing the fault response strategy includes: A maintenance reminder message is output each time it is confirmed that the maintenance is not completed.

7. The method according to claim 6, characterized in that, The confirmation that the repair is not complete includes: When the vehicle is powered on or the preset vehicle function is activated, determine whether the fault information matches the fault conditions corresponding to the currently executed fault response strategy. If the conditions are met, then the repair is confirmed to be incomplete.

8. The method according to any one of claims 1 to 5, characterized in that, The method further includes: During the execution of the fault response strategy, the fault information of the vehicle indicator light is monitored; When the fault information indicates that the vehicle indicator light has returned to normal, the fault response strategy is stopped; or, when the fault information changes, the fault response strategy is adjusted.

9. A vehicle, characterized in that, This includes vehicle indicator lights, body domain controllers, and driver domain controllers; The vehicle body domain controller, connected to the vehicle indicator light, is configured to acquire fault information and configuration information of the vehicle indicator light and send them to the driving domain controller. The driving domain controller, connected to the body domain controller, is configured to perform the steps of the method as described in any one of claims 1 to 8.

10. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 8.

Images