Digital key version management and control method and device and computer readable storage medium

Abstract

The invention discloses a digital key version control method and device and a computer readable storage medium, and the method comprises the steps: receiving a version number broadcast of each controller, the version number broadcast being sent by each controller according to a preset frequency and through a bus message, the broadcast comprises a broadcast of a version corresponding to the current running software; determining whether each controller is abnormal or not according to the receiving state of the version number broadcast; and if an abnormal controller exists, reporting fault information corresponding to the abnormal controller to the network access equipment, otherwise, reporting the version number of each controller to the network access equipment. According to the invention, a self-adaptive digital key version management and control scheme is realized, the troubleshooting difficulty of faults of the vehicle controller is reduced, the analysis capability of market problems is effectively guaranteed, and the efficiency of vehicle research and development and vehicle maintenance is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle electronics technology, and in particular, to a digital key version control method, device, and computer-readable storage medium. Background Art

[0002] In the prior art, the degree of vehicle intelligence and integration is getting higher and higher, which has promoted the birth of many new concepts and solutions. For example, the implementation of multiple intelligent solutions such as intelligent cockpits and third spaces. Among them, the intelligent cockpit has multiple subsystems, including central control, entertainment, voice interaction, monitoring, and digital keys. The digital key can be generated digitally and can remotely control and start the vehicle.

[0003] Currently, there are the following problems in the version control related to the current digital key:

[0004] First, the digital key solution often involves the software cooperation of several ECU controllers to achieve. Therefore, to implement a new function, different controllers need to be upgraded simultaneously. However, when the digital key function cannot be used, the difficulty of problem troubleshooting also increases accordingly;

[0005] Second, based on the above background, an intuitive method is needed to determine whether the relevant controllers involved in the intelligent digital key are currently using a normal and legal version or are currently working properly to guide the analysis and troubleshooting of market problems. Summary of the Invention

[0006] In order to overcome the deficiencies in the prior art, the purpose of the present invention is to provide a method to solve the problems of large difficulty in troubleshooting and inability to guide the analysis and troubleshooting of market problems existing in the current version management related to digital keys.

[0007] The present invention proposes a digital key version control method, which is applied to a microcontroller inside a vehicle networking terminal. The vehicle networking terminal further includes a network access device. The method includes:

[0008] Receiving the version number broadcasts of each controller, where the version number broadcasts are sent by each controller at a preset frequency through bus messages and contain the broadcasts of the versions corresponding to the software currently running on itself;

[0009] Determining whether there is an abnormality in each controller according to the reception status of the version number broadcasts;

[0010] If there is an abnormal controller, reporting the fault information corresponding to the abnormal controller to the network access device; otherwise, reporting the version numbers of each controller to the network access device.

[0011] Optionally, before receiving the version number broadcasts of each controller, it includes:

[0012] Obtain one or more controller parameters such as the working status, task information, and the category to which each controller belongs;

[0013] Preset a first configuration corresponding to each controller according to the controller parameters to which it belongs, where the first configuration includes the broadcast frequency and monitoring threshold of each controller.

[0014] Optionally, the receiving of the version number broadcasts of each controller specifically includes:

[0015] When receiving the version number broadcast of the controller, open a preset detection window;

[0016] During the detection period corresponding to the detection window, record the number of times the version number broadcast is received.

[0017] Optionally, determining whether there is an abnormality in each controller according to the reception status of the version number broadcast specifically includes:

[0018] Calculate a first status value within the detection window based on the number of receptions and the detection period;

[0019] Judge whether the first status value is within the range of the monitoring threshold. If so, determine that the controller is normal; otherwise, determine that the controller is abnormal.

[0020] Optionally, determining whether there is an abnormality in each controller according to the reception status of the version number broadcast specifically includes:

[0021] Calculate a second status value within the detection window based on the number of receptions and the detection period;

[0022] Judge whether the second status value is within the range of the broadcast frequency. If so, determine that the controller is normal; otherwise, determine that the controller is abnormal.

[0023] Optionally, if there is an abnormal controller, reporting fault information corresponding to the abnormal controller to the network access device specifically includes:

[0024] Determine the fault part number corresponding to the controller;

[0025] Fill in a first preset value corresponding to the fault part number as the fault information corresponding to the abnormal controller.

[0026] Optionally, reporting the version numbers of each controller to the network access device specifically includes:

[0027] Determine the part number corresponding to the controller;

[0028] Fill in the second preset value corresponding to the part number as the information corresponding to the normal controller, and broadcast it to the network access device.

[0029] Optionally, the method further includes:

[0030] Detect the reception status of the version number broadcast corresponding to the abnormal controller;

[0031] If the reception status is normal, report the version number of the controller that has turned normal to the network access device, so that the network access device updates the status record information corresponding to the abnormal controller.

[0032] The present invention also provides a digital key version control device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, the steps of the digital key version control method described in any one of the above are implemented.

[0033] The present invention also provides a computer-readable storage medium, on which a digital key version control program is stored. When the digital key version control program is executed by a processor, the steps of the digital key version control method described in any one of the above are implemented.

[0034] Implementing the digital key version control method, device, and computer-readable storage medium of the present invention, by receiving the version number broadcasts of each controller, where the version number broadcast is sent by each controller at a preset frequency and through a bus message, and includes a broadcast of the version corresponding to the currently running software of itself; determining whether each controller is abnormal according to the reception status of the version number broadcast; if there is an abnormal controller, reporting the fault information corresponding to the abnormal controller to the network access device, otherwise, reporting the version number of each controller to the network access device. An adaptive digital key version control solution is realized, the difficulty of troubleshooting vehicle controller faults is reduced, the parsing ability of market problems is effectively guaranteed, and the efficiency of vehicle R & D and vehicle maintenance is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The present invention will be further described below in conjunction with the drawings and embodiments. In the drawings:

[0036] Figure 1 is the first flowchart of the digital key version control method of the present invention;

[0037] Figure 2It is the second flowchart of the digital key version control method of the present invention;

[0038] Figure 3 It is the third flowchart of the digital key version control method of the present invention;

[0039] Figure 4 It is the fourth flowchart of the digital key version control method of the present invention;

[0040] Figure 5 It is the fifth flowchart of the digital key version control method of the present invention;

[0041] Figure 6 It is the sixth flowchart of the digital key version control method of the present invention;

[0042] Figure 7 It is the seventh flowchart of the digital key version control method of the present invention;

[0043] Figure 8 It is the eighth flowchart of the digital key version control method of the present invention;

[0044] Figure 9 It is the ninth flowchart of the digital key version control method of the present invention. Detailed implementation manners

[0045] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0046] In the subsequent descriptions, the suffixes such as "module", "component" or "unit" used to represent elements are only for the convenience of describing the present invention and have no specific meaning in themselves. Therefore, "module", "component" or "unit" can be used interchangeably.

[0047] Figure 1 It is the first flowchart of the digital key version control method of the present invention. This embodiment proposes a digital key version control method applied to the microcontroller inside the vehicle networking terminal. The vehicle networking terminal further includes a network access device. The method includes:

[0048] S1. Receive the version number broadcasts of each controller, where the version number broadcasts are sent by each controller at a preset frequency through bus messages and contain the versions corresponding to the software currently running on itself;

[0049] S2. Determine whether there is an abnormality in each controller according to the reception status of the version number broadcast;

[0050] S3. If there is an abnormal controller, report the fault information corresponding to the abnormal controller to the network access device; otherwise, report the version numbers of all the controllers to the network access device.

[0051] In this embodiment, the vehicle networking terminal serves as the gateway entrance of the controllers related to the digital key and has the routing and processing capabilities for the relevant diagnostic signals.

[0052] In this embodiment, when the relevant application software runs inside the digital key-related controller ECU (Electronic Control Unit) (such as UWB, WPC, NFC, etc.), the version number of the software is reported and broadcast through different CAN messages; optionally, the intelligent digital key-related controller broadcasts the version number of the currently running software to the vehicle networking terminal through CAN messages at a certain period (such as 1 second or 500 milliseconds). The MCU (Microcontroller Unit) of the vehicle networking terminal receives and determines whether there is a legal version number. If the version number message of the part number is not received, the MCU needs to report a fault to the NAD (Network Access Device) side of the vehicle networking terminal. If the part number is received, the MCU reports the correct part number to the NAD side of the vehicle networking terminal, and the NAD stores the part number. When the OEM or 4S store reads the version number and the fault DTC through the host computer or the diagnostic device, it can intuitively judge which intelligent digital key controller has a fault and can perform targeted troubleshooting.

[0053] Please refer to Figure 9 , in this embodiment, the above operation logic mainly includes:

[0054] Step 1. Broadcast of the part numbers of the intelligent digital key-related controllers. The intelligent digital key-related controllers broadcast their respective currently running version numbers to the vehicle networking terminal through different CAN messages.

[0055] Step 2. Processing of the part numbers by the MCU of the vehicle networking terminal. The MCU receives the version numbers broadcast by each intelligent digital key-related controller through CAN and checks their validity. Among them, if one or more controllers do not send the broadcast CAN message of the version number within 5 cycles, the MCU will fill all 1s as the fault part number and report it to the NAD; if the version numbers of all controllers are broadcast normally, the MCU will report the version number of the actual CAN message to the NAD.

[0056] Step 3: The MCU of the vehicle networking terminal processes DTC. For example, when one or more controllers do not send the broadcast CAN message of the version number within 5 cycles, the MCU will report the DTC (Diagnostic Trouble Code, the digital identifier of vehicle faults) indicating that the corresponding controller is offline to the NAD at the same time.

[0057] Step 4: The NAD part number processing of the vehicle networking terminal. For example, the NAD will receive the part number of the intelligent digital key controller reported by the MCU and store it in the NV file, which is convenient for subsequent OEMs or 4S stores of vehicles to troubleshoot faults. Among them, after the NAD is powered on for the first time, if it has not received the part number of the MCU all the time, then the NAD defaults to fill the part number with all 00s. Until the MCU reports, the NAD will store the part number reported by the MCU. Among them, the normal part number is not all 11.

[0058] Step 5: The host computer or diagnostic device reads the part number and DTC. Among them, when the digital key function is unavailable, the DTC and version number of all relevant controllers can be read through the host computer or diagnostic device. If a certain controller has a DTC and the version number is 11, that is, this controller has a fault, and the sample needs to be replaced or the power supply needs to be checked.

[0059] The beneficial effect of this embodiment is that by receiving the version number broadcasts of each controller, where the version number broadcasts are sent by each of the controllers at a preset frequency and through bus messages, and contain the broadcasts of the versions corresponding to the currently running software of themselves; determining whether there are abnormalities in each of the controllers according to the reception status of the version number broadcasts; if there is an abnormal controller, reporting the fault information corresponding to the abnormal controller to the network access device, otherwise, reporting the version numbers of each of the controllers to the network access device. An adaptive digital key version control scheme is realized, the difficulty of troubleshooting vehicle controller faults is reduced, the ability to analyze market problems is effectively guaranteed, and the efficiency of vehicle R & D and vehicle maintenance is improved.

[0060] Figure 2 This is the second flowchart of the digital key version control method of the present invention. Based on the above embodiment, before receiving the version number broadcasts of each controller, it includes:

[0061] S01: Obtain one or more controller parameters such as the working status, task information, and category of each of the controllers;

[0062] S02: Preset a first configuration corresponding to each of the controllers according to the controller parameters, where the first configuration includes the broadcast frequency and monitoring threshold of each of the controllers.

[0063] In this embodiment, when the controller is in the working state, the broadcast frequency and monitoring threshold of the first level are determined, and when it is in the idle state, the broadcast frequency and monitoring threshold of the second level are determined, where the parameter value of the first level is higher than that of the second level, thereby saving power consumption.

[0064] In this embodiment, when the controller is in the task execution state, the broadcast frequency and monitoring threshold of the second level are determined, and when the controller does not receive a task, the broadcast frequency and monitoring threshold of the first level are determined, thereby avoiding an additional processing burden during its task execution state.

[0065] In this embodiment, when the controller belongs to a controller related to vehicle body unlocking and locking (for example, an NFC controller), during the vehicle body locking or unlocking stage, the broadcast frequency and monitoring threshold of the first level are set, and in other stages, the parameters are adjusted downwards, thereby avoiding waste of additional resources or power consumption.

[0066] The beneficial effect of this embodiment is that by obtaining one or more controller parameters such as the working state, task information, and category of each controller, and presetting a first configuration corresponding to each controller according to the controller parameters, where the first configuration includes the broadcast frequency and monitoring threshold of each controller, the monitoring of the version number is more timely and effective, and resource waste is effectively avoided.

[0067] Figure 3 It is the third flowchart of the digital key version control method of the present invention. Based on the above embodiment, the receiving of the version number broadcasts of each controller specifically includes:

[0068] S11. When receiving the version number broadcast of the controller, open a preset detection window;

[0069] S12. Record the number of times the version number broadcast is received within the detection period corresponding to the detection window.

[0070] In this embodiment, in one way, when receiving the version number broadcast of the controller, open a preset detection window; in another way, when it is determined that the current controller is in the working state or the task execution state and receives the version number broadcast of the controller for the first time, open a preset detection window.

[0071] In this embodiment, in another way, when it is determined that the current controller enters the idle state or completes a task, the controller starts to broadcast, and when the MCU receives the first version number broadcast of the controller, open the above-mentioned preset detection window.

[0072] The beneficial effect of this embodiment is that when it is recognized that the version number broadcast of the controller is received, a preset detection window is opened, and within the detection period corresponding to the detection window, the number of times the version number broadcast is received is recorded, thereby effectively improving the differentiation degree of the MCU's monitoring of each controller, improving the monitoring efficiency, clarifying the monitoring target, and avoiding resource consumption.

[0073] Figure 4 It is the fourth flowchart of the digital key version control method of the present invention. Based on the above embodiment, determining whether there is an abnormality in each of the controllers according to the reception status of the version number broadcast specifically includes:

[0074] S21. Calculate a first status value within the detection window according to the number of receptions and the detection period;

[0075] S22. Determine whether the first status value is within the range of the monitoring threshold. If so, determine that the controller is normal; otherwise, determine that the controller is abnormal.

[0076] In this embodiment, the first status value is the number of times falling within a detection period. If this number is greater than or equal to the above monitoring threshold, it is determined that the controller is normal; otherwise, it is determined that the controller is abnormal.

[0077] The beneficial effect of this embodiment is that a first status value within the detection window is calculated according to the number of receptions and the detection period, and it is determined whether the first status value is within the range of the monitoring threshold. If so, it is determined that the controller is normal; otherwise, it is determined that the controller is abnormal, thereby associating the abnormal status monitoring with the specific number of times and ensuring the continuity of the monitoring.

[0078] Figure 5 It is the fifth flowchart of the digital key version control method of the present invention. Based on the above embodiment, determining whether there is an abnormality in each of the controllers according to the reception status of the version number broadcast specifically includes:

[0079] S23. Calculate a second status value within the detection window according to the number of receptions and the detection period;

[0080] S24. Determine whether the second status value is within the range of the broadcast frequency. If so, determine that the controller is normal; otherwise, determine that the controller is abnormal.

[0081] In this embodiment, the second status value is the reception frequency within a monitoring period calculated based on the number of times falling within a detection period as described above. If the reception frequency is greater than or equal to the broadcast frequency, it is determined that the controller is normal; otherwise, it is determined that the controller is abnormal.

[0082] The beneficial effect of this embodiment is that the second status value within the detection window is calculated through the reception times and the detection period, and it is determined whether the second status value is within the range of the broadcast frequency. If so, it is determined that the controller is normal; otherwise, it is determined that the controller is abnormal, thereby associating the abnormal status monitoring with the specific frequency and ensuring the timeliness of the monitoring.

[0083] Figure 6 It is the sixth flowchart of the digital key version control method of the present invention. Based on the above embodiment, if there is an abnormal controller, the fault information corresponding to the abnormal controller is reported to the network access device, which specifically includes:

[0084] S31. Determine the fault part number corresponding to the controller;

[0085] S32. Fill in the first preset value corresponding to the fault part number as the fault information corresponding to the abnormal controller.

[0086] In this embodiment, after completion of filling, it is sent to the NAD as the fault information, so that the NAD can feedback the fault information of the specific controller according to an external query request. After the above fault information is sent to the NAD, the NAD adds a timestamp, so that the subsequent fault information fed back to the outside also includes the specific fault time.

[0087] The beneficial effect of this embodiment is that by determining the fault part number corresponding to the controller and filling in the first preset value corresponding to the fault part number as the fault information corresponding to the abnormal controller, the NAD can timely and effectively master the fault status of each controller, and also reduces the cache requirement for the MCU.

[0088] Figure 7 It is the seventh flowchart of the digital key version control method of the present invention. Based on the above embodiment, reporting the version numbers of the respective controllers to the network access device specifically includes:

[0089] S33. Determine the part number corresponding to the controller;

[0090] S34. Fill in the second preset value corresponding to the part number as the information corresponding to the normal controller and broadcast it to the network access device.

[0091] In this embodiment, after completion of filling, it is sent to the NAD as normal information, so that the NAD feeds back the normal state of the specific controller according to an external query request. After the above normal information is sent to the NAD, the NAD adds a time stamp, so that the subsequent feedback of the normal state to the outside also includes the specific detection time.

[0092] The beneficial effect of this embodiment is that by determining the part number corresponding to the controller and filling in the second preset value that matches the part number as the information corresponding to the normal controller and broadcasting it to the network access device, the NAD can timely and effectively master the normal or faulty state of each controller, and also reduces the cache requirement for the MCU.

[0093] Figure 8 It is the eighth flowchart of the digital key version control method of the present invention. Based on the above embodiment, the method further includes:

[0094] S41. Detect the reception status of the broadcast of the version number corresponding to the abnormal controller;

[0095] S42. If the reception status is normal, report the version number of the controller that has turned normal to the network access device, so that the network access device updates the status record information corresponding to the abnormal controller.

[0096] In this embodiment, detect the reception status of the broadcast of the version number corresponding to the normal controller; if the reception status is abnormal, report the version number of the controller that has turned abnormal to the network access device, so that the network access device updates the status record information corresponding to the normal controller.

[0097] The beneficial effect of this embodiment is that by detecting the reception status of the broadcast of the version number corresponding to the abnormal controller, and if the reception status is normal, reporting the version number of the controller that has turned normal to the network access device, so that the network access device updates the status record information corresponding to the abnormal controller, thereby improving the feedback update efficiency of each controller after the state change.

[0098] Based on the above embodiment, the present invention also proposes a digital key version control device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the digital key version control method described in any one of the above.

[0099] It should be noted that the above device embodiments and method embodiments belong to the same concept. The specific implementation process is described in detail in the method embodiments, and the technical features in the method embodiments are correspondingly applicable to the device embodiments, so they will not be elaborated here.

[0100] Based on the above embodiments, the present invention also proposes a computer-readable storage medium, on which a digital key version control program is stored. When the digital key version control program is executed by a processor, it implements the steps of the digital key version control method as described in any one of the above.

[0101] It should be noted that the above medium embodiments and method embodiments belong to the same concept. The specific implementation process is described in detail in the method embodiments, and the technical features in the method embodiments are correspondingly applicable to the medium embodiments, so they will not be elaborated here.

[0102] Implementing the digital key version control method, device and computer-readable storage medium of the present invention, by receiving the version number broadcasts of each controller, where the version number broadcasts are sent by each of the controllers at a preset frequency and through bus messages, and include the broadcasts of the versions corresponding to the currently running software of themselves; determining whether there is an abnormality in each of the controllers according to the reception status of the version number broadcasts; if there is an abnormal controller, reporting the fault information corresponding to the abnormal controller to the network access device, otherwise, reporting the version numbers of each of the controllers to the network access device. An adaptive digital key version control scheme is realized, the difficulty of troubleshooting vehicle controller faults is reduced, the ability to analyze market problems is effectively guaranteed, and the efficiency of vehicle R & D and vehicle maintenance is improved.

[0103] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence or the part that makes a contribution to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0104] It should be noted that in this text, the terms "including", "comprising" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including such element.

[0105] The embodiments of the present invention have been described above in conjunction with the accompanying drawings. However, the present invention is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present invention, those of ordinary skill in the art can also make many forms without departing from the spirit and scope protected by the claims of the present invention, and these all fall within the protection scope of the present invention.

Claims

1. A digital key version control method is applied to a microcontroller inside a vehicle networking terminal, wherein the vehicle networking terminal also includes a network access device, characterized in that: The method comprises: Receiving a version number broadcast of each controller, wherein the version number broadcast is sent by each controller at a preset frequency and through a bus message, and includes a broadcast of a version corresponding to the software currently running on the controller; Determine whether each of the controllers has an abnormality according to the reception status of the version number broadcast; If there is an abnormal controller, the fault information corresponding to the abnormal controller is reported to the network access device; otherwise, the version number of each controller is reported to the network access device.

2. The digital key version control method according to claim 1, characterized in that: The receiving of the version number broadcast of each controller includes: Obtaining the working status, task information and one or more controller parameters of each controller in the corresponding category; A first configuration corresponding to each of the controllers is preset according to the parameters of the corresponding controller, wherein the first configuration includes a broadcast frequency and a monitoring threshold of each of the controllers.

3. The digital key version control method according to claim 2, characterized in that: The receiving of the version number broadcast of each controller specifically includes: When receiving the version number broadcast of the controller, opening a preset detection window; In a detection period corresponding to the detection window, the number of times the version number broadcast is received is recorded.

4. The digital key version control method according to claim 3, characterized in that: The determining whether each of the controllers is abnormal according to the reception status of the version number broadcast specifically includes: Calculate a first state value within the detection window according to the number of receptions and the detection period; It is determined whether the first state value is within the range of the monitoring threshold value. If so, it is determined that there is no abnormality in the controller; otherwise, it is determined that there is an abnormality in the controller.

5. The digital key version control method according to claim 3, characterized in that: The determining whether each of the controllers is abnormal according to the reception status of the version number broadcast specifically includes: Calculate a second state value within the detection window according to the number of receptions and the detection period; It is determined whether the second state value is within the range of the broadcast frequency. If so, it is determined that there is no abnormality in the controller; otherwise, it is determined that there is an abnormality in the controller.

6. The digital key version control method according to claim 1, characterized in that: If there is an abnormal controller, reporting fault information corresponding to the abnormal controller to the network access device specifically includes: Determining a fault part number corresponding to the controller; Fill in a first preset value that matches the fault part number as the fault information corresponding to the abnormal controller.

7. The digital key version control method according to claim 4, characterized in that: The reporting the version number of each controller to the network access device specifically includes: Determining a part number corresponding to the controller; A second preset value corresponding to the part number is filled in as information corresponding to a normal controller, and is broadcast to the network access device.

8. The digital key version control method according to claim 1, characterized in that: The method further comprises: Detecting a reception status of the version number broadcast corresponding to the abnormal controller; If the receiving status is a normal status, the version number of the controller that has become normal is reported to the network access device, so that the network access device updates the status record information corresponding to the abnormal controller.

9. A digital key version control device, characterized in that: The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the digital key version management method as described in any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a digital key version control program, which, when executed by a processor, implements the steps of the digital key version control method according to any one of claims 1 to 8.

Images