Software architecture of controller, and controller, black box system and vehicle

Abstract

The present application relates to a software architecture of a controller, and a controller, a black box system and a vehicle. The software architecture comprises: an application layer and a platform software layer, wherein the application layer is used for storing automobile operation state data in a local memory unit of the controller in real time, and when a fault trigger event has been received, sending indication information to the platform software layer; the platform software layer comprises a fault management module; the fault management module is used for adding a corresponding black box data writing request to a fault handling queue when the indication information has been received, and using, as black box data, the automobile operation state data which is temporarily stored in the local memory unit; and the fault management module is further used for periodically storing the corresponding black box data in a main storage unit on the basis of request information in the fault handling queue. By using the software architecture of the controller, the storage locations of black box data can be rationally allocated, thereby solving the problem of memory resources of the controller being insufficient.

Description

Software architecture of a controller, controller, black box system and vehicle

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application CN2024104270997, filed on April 10, 2024, entitled “Software architecture of a controller, controller, black box system and vehicle”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the technical field of vehicles, and in particular to a software architecture of a controller, a controller, a black box system and a vehicle. BACKGROUND

[0004] In recent years, new energy vehicles have become an important development direction in the automotive field due to their energy-saving and environmentally friendly advantages, and their safety has received widespread attention in the industry. The automobile controller black box technology is widely used because it meets the safety requirements of automobiles. The automobile controller black box technology can record the key information of the running state of the automobile before and after the fault occurs, such as three-phase current, voltage, speed, carrier frequency, output duty cycle, etc., and the data in the black box can be obtained through a diagnostic tool, effectively analyzing the vehicle state information in the black box data, quickly and accurately locating the cause of the fault, thereby realizing the troubleshooting of vehicle faults.

[0005] Currently, the automobile black box system is integrated with the automobile controller software, without the need for a special black box device, which can greatly reduce the development cost of the whole vehicle. However, the automobile black box data occupies a large amount of memory space in the controller, which can cause the controller memory resource to be tight, and even the black box data can cover other data areas, thereby causing the controller to be in an abnormal state, increasing the risk of vehicle operation.

[0006] SUMMARY

[0007] Therefore, it is necessary to provide a software architecture of a controller, a controller, a black box system, a vehicle and a storage medium, which can reasonably allocate the storage location of the black box data and solve the problem of tight memory resources in the controller.

[0008] In a first aspect, the present application provides a software architecture of a controller, the software architecture comprising: an application layer and a platform software layer, wherein,

[0009] The application layer is configured to store vehicle running state data in a local memory unit of the controller in real time, and send indication information to the platform software layer in the case that a fault trigger event is received;

[0010] The platform software layer comprises a fault management module, which is configured to, in response to receiving the indication information, add a corresponding black box data writing request into a fault processing queue, and store the automotive operation state data temporarily stored in the local memory unit as black box data;

[0011] The fault management module is further configured to periodically store the corresponding black box data in the main memory unit according to the request information in the fault processing queue.

[0012] In one of the embodiments, the application layer is further configured to, in response to receiving a fault triggering event, classify the data fault, and output corresponding indication information according to the type of the data fault;

[0013] The fault management module is further configured to determine the fault type according to the indication information, and store the corresponding black box data in a specified area of the main memory unit according to the fault type when storing the black box data in the main memory unit, wherein different fault types correspond to different storage areas in the main memory unit.

[0014] In one of the embodiments, the platform software layer further comprises a diagnosis module, which is configured to, in response to receiving a diagnosis packet indicating reading of the black box data, send a calling instruction to the fault management module;

[0015] The fault management module is further configured to, in response to the calling instruction, copy the fault data in the corresponding area of the main memory unit to the local memory unit, and transmit the fault data in the local memory unit to the diagnosis module, so that the diagnosis module outputs the fault data.

[0016] In one of the embodiments, the fault management module is further configured to, in response to receiving a diagnosis service packet with a data identifier, erase the data in the corresponding storage area of the main memory unit according to the diagnosis service packet.

[0017] In one of the embodiments, the main memory unit has a plurality of storage areas and a plurality of backup areas; the fault management module is further configured to determine a corresponding target check code according to the target black box data to be stored, write the target black box data and the target check code into a target storage area of the main memory unit, and backup the storage data in the target storage area to a corresponding target backup space after successful writing.

[0018] In one of the embodiments, after the controller is powered on, the fault management module is further configured to read the storage data of the target storage area during initialization, calculate the reference check code corresponding to the target storage area according to the read data, and determine that the storage data of the target storage area is abnormal if the check code stored in the target storage area is different from the reference check code, and store the backup data of the target backup area to the target storage area.

[0019] In one of the embodiments, the main memory unit has a plurality of storage areas; and the fault management module is further configured to periodically store the corresponding black box data in the plurality of storage areas of the main memory unit according to the request information in the fault processing queue.

[0020] In the second aspect, the application further provides a controller, and the software architecture of the processor adopts the software architecture of the controller as described in the first aspect.

[0021] In the third aspect, the application further provides a black box system, which comprises a main memory unit and a controller as described in the second aspect; and the controller is connected with the local memory unit and the main memory unit respectively.

[0022] In the fourth aspect, the application further provides a control method of a black box system, which comprises:

[0023] acquiring the automobile running state data in real time and storing the automobile running state data in the local memory unit;

[0024] in the case of receiving a fault triggering event, adding a corresponding black box data writing request to the fault processing queue, and taking the automobile running state data temporarily stored in the local memory unit as the black box data;

[0025] periodically storing the corresponding black box data in the main memory unit according to the request information in the fault processing queue.

[0026] In the fifth aspect, the application further provides a vehicle, which comprises a memory and a processor, and the memory stores a computer program; and the processor implements the steps of the method as described in the fourth aspect when executing the computer program.

[0027] In the sixth aspect, the application further provides a computer readable storage medium, which stores a computer program; and the computer program is executed by a processor to implement the steps of the method as described in the fourth aspect.

[0028] The software architecture of the controller, the controller and the black box system include an application layer and a platform software layer, the application layer is configured to store the vehicle running state data in the local memory unit of the controller in real time, and send the indication information in the case of receiving the fault trigger event; the platform software layer includes a fault management module, the fault management module is configured to add the request of writing the corresponding black box data into the fault processing queue in the case of receiving the indication information, and store the vehicle running state data temporarily stored in the local memory unit as the black box data, on the basis of which, the fault management module can store the corresponding black box data in the main memory unit periodically according to the request information in the fault processing queue, so that the main memory unit is used to store the black box data, and the problem of the shortage of memory resources in the controller is solved. In addition, the fault management module stores the corresponding black box data in the main memory unit periodically according to the request information in the fault processing queue, so that the storage process of the black box data is asynchronous with the fault trigger event, thereby realizing the asynchronous storage of the black box data and ensuring the stable operation of the controller.

[0029] The control method of the black box system, the vehicle and the computer readable storage medium, by acquiring the vehicle running state data in real time and storing in the local memory unit, in the case of receiving the fault trigger event, the corresponding black box data writing request is added to the fault processing queue, the vehicle running state data temporarily stored in the local memory unit is taken as the black box data, and then the corresponding black box data is stored in the main memory unit periodically according to the request information in the fault processing queue, so that the main memory unit is used to store the black box data, and the problem of the shortage of memory resources in the controller is solved. In addition, the corresponding black box data is stored in the main memory unit periodically according to the request information in the fault processing queue, so that the storage process of the black box data is asynchronous with the fault trigger event, thereby realizing the asynchronous storage of the black box data and ensuring the stable operation of the controller. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or the related art description. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, without creative labor, other drawings can also be obtained from these drawings.

[0031] Fig. 1 is a schematic diagram of the software architecture of the controller in one embodiment;

[0032] Fig. 2 is a schematic diagram of the software architecture of the controller in another embodiment;

[0033] Fig. 3 is a schematic diagram of the black box data reading process in one embodiment;

[0034] Fig. 4 is a schematic diagram of memory resource distribution of a main memory unit in an embodiment;

[0035] Fig. 5 is a schematic diagram of a structure of a black box system in an embodiment;

[0036] Fig. 6 is a schematic diagram of a flow of a control method of the black box system in an embodiment;

[0037] Fig. 7 is a schematic diagram of an internal structure of a vehicle in an embodiment.

[0038] Legend: 10-controller, 11-application layer, 12-platform software layer, 13-main memory unit, 20-CAN tool, 30-black box host computer. DETAILED DESCRIPTION

[0039] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application.

[0040] As described in the background, the automobile controller black box technology can record the key information of the automobile running state before and after the fault occurs, such as three-phase current, voltage, speed, carrier frequency, output duty cycle, etc. The data in the black box can be obtained through the diagnostic tool, and the automobile state information in the black box data can be effectively analyzed to quickly and accurately locate the cause of the fault, thereby realizing the troubleshooting of the vehicle fault.

[0041] At present, the automobile black box system is integrated with the automobile controller software, and no special black box device is needed, which can greatly reduce the development cost of the whole vehicle. However, the automobile black box data occupies a large amount of memory space of the controller, which can cause the shortage of memory resources of the controller, and even can cause the black box data to cover other data areas, thereby causing the abnormal state of the controller and increasing the risk of vehicle operation.

[0042] In order to solve the above problems, in an exemplary embodiment, as shown in Fig. 1, a software architecture of a controller is provided, which includes an application layer 11 and a platform software layer 12.

[0043] The application layer 11 is used to store the automobile running state data in the local memory unit of the controller in real time, and send an indication information to the platform software layer 12 in the case of receiving a fault trigger event.

[0044] The local memory unit can be a RAM memory. By storing the automobile running state data in the local memory unit of the controller in real time through the application layer 11, the data before and after the fault occurs can be stored. And the application layer 11 sends an indication information in the case of receiving a fault trigger event.

[0045] The platform software layer 12 comprises a fault management module, which is configured to add a corresponding black box data writing request into a fault processing queue and store the automobile running state data temporarily stored in the local memory unit as the black box data upon receiving the indication information. The fault management module is further configured to periodically store the corresponding black box data in the main storage unit 13 according to the request information in the fault processing queue.

[0046] The main storage unit 13 can be a non-volatile storage medium, such as a DFlash memory.

[0047] It can be understood that the fault management module receives the fault trigger notification upon receiving the indication information, and the automobile running state data temporarily stored in the local memory unit is the fault associated data, which is stored as the black box data. After the fault management module periodically stores the corresponding black box data in the main storage unit 13 according to the request information in the fault processing queue, the black box data can be stored for a long time, which facilitates the subsequent acquisition of the black box data by the staff through the diagnostic tool to realize fault positioning. The main storage unit 13 is used to store the black box data, which solves the problem of tight memory resources in the controller. In addition, since the amount of black box data is large, a long processing time is required when storing the black box data in the main storage unit 13. If synchronous storage is used, the task scheduling will be blocked, which will cause the abnormal task scheduling of the platform software layer 12 and the abnormal state of the controller. According to the request information in the fault processing queue, the corresponding black box data is periodically stored in the main storage unit 13, which makes the storage process of the black box data asynchronous with the fault trigger event, thereby realizing the asynchronous storage of the black box data and ensuring the stable operation of the controller.

[0048] In the application, the software architecture of the controller can further comprise a hardware resource configuration layer, and the fault management module manages the storage resources through the hardware resource configuration layer, i.e., stores the black box data in the main storage unit 13.

[0049] The software architecture of the controller includes an application layer 11 and a platform software layer 12. The application layer 11 is configured to store the vehicle running state data in the local memory unit of the controller in real time, and send the indication information when the fault trigger event is received. The platform software layer 12 includes a fault management module. The fault management module is configured to add the request for writing the corresponding black box data into the fault processing queue when the indication information is received, and store the vehicle running state data temporarily stored in the local memory unit as the black box data. On this basis, the fault management module can periodically store the corresponding black box data in the main memory unit 13 according to the request information in the fault processing queue, so as to store the black box data in the main memory unit 13, and solve the problem of the shortage of memory resources in the controller. In addition, the fault management module periodically stores the corresponding black box data in the main memory unit 13 according to the request information in the fault processing queue, so that the storage process of the black box data is asynchronous with the fault trigger event, thereby realizing the asynchronous storage of the black box data, and ensuring the stable operation of the controller.

[0050] In one embodiment, the application layer 11 is further configured to classify the data fault when the fault trigger event is received, and output the corresponding indication information according to the type of the data fault.

[0051] The fault management module is further configured to determine the fault type according to the indication information, and store the corresponding black box data to the specified area of the main memory unit 13 according to the fault type when storing the black box data to the main memory unit 13, wherein different fault types correspond to different storage areas of the main memory unit 13.

[0052] The fault type mainly includes a hardware overcurrent fault, a hardware overvoltage fault and an IGBT fault.

[0053] It can be understood that the application layer 11 classifies the data fault when the fault trigger event is received, and outputs the corresponding indication information according to the type of the data fault, and the fault management module stores the corresponding black box data to the specified area of the main memory unit 13 according to the fault type, so as to store different types of faults in different storage areas of the main memory unit 13. In the later diagnosis process, the fault type can be determined based on the storage area of the read data, and then the fault analysis and positioning are facilitated.

[0054] In one embodiment, as shown in FIG. 2, the platform software layer 12 further includes a diagnosis module. The diagnosis module is configured to send a call instruction to the fault management module when a diagnosis packet indicating reading the black box data is received.

[0055] The fault management module is also configured to copy the fault data of the corresponding region in the main storage unit 13 to the local memory unit and transmit the fault data in the local memory unit to the diagnostic module in response to the calling instruction, so that the diagnostic module outputs the fault data.

[0056] In application, the black box host computer 30 reads the black box data, and the specific process can be as follows: the black box host computer 30 is connected to the controller 10 of the vehicle through the CAN tool 20, the black box host computer 30 sends a diagnostic message for reading the black box data to the CAN bus through the CAN tool 20, the diagnostic module of the controller 10 receives the diagnostic message of the CAN bus and sends a calling instruction to the fault management module, the fault management module copies the fault data of the corresponding region in the main storage unit 13 to the local memory unit in response to the calling instruction, and transmits the fault data in the local memory unit to the diagnostic module, the diagnostic module outputs the fault data to the CAN bus, which is received by the CAN tool 20 and fed back to the black box host computer 30 for analysis, so that the fault data is read and analyzed by the black box host computer 30.

[0057] In one embodiment, the fault management module is also configured to erase the data of the corresponding storage region in the main storage unit 13 according to the diagnostic service message with the data identifier.

[0058] It can be understood that, in order to avoid too much fault data occupying the memory of the main storage unit 13, the fault management module needs to have a fault data erasing function to erase the data of the corresponding storage region in the main storage unit 13, so that the storage region can store new data.

[0059] In application, the staff sends a diagnostic service message with a specific data identifier to the controller 10 through the black box host computer 30, and the fault management module of the controller 10 erases the data of the corresponding storage region in the main storage unit 13 according to the diagnostic service message with the data identifier.

[0060] In one embodiment, the main storage unit 13 has a plurality of storage regions and a plurality of backup regions, as shown in FIG. 4. The fault management module is also configured to determine the corresponding target check code according to the target black box data to be stored, write the target black box data and the target check code to the target storage region of the main storage unit 13, and backup the storage data in the target storage region to the corresponding target backup space after successful writing.

[0061] In application, when the fault management module executes the process of writing the black box data to the main storage unit 13, the controller 10 may be abnormally powered off, resulting in incomplete writing of the black box data.

[0062] The fault management module, when performing the black box data writing, first calculates a check code according to all the data to be written. The calculation rule of the check code can be preset and is not specifically limited herein. The fault management module writes the black box data in the storage area and simultaneously writes the check code in the storage area of the main storage unit 13. Meanwhile, the main storage unit 13 has a space for storing the backup data of the black box. After the black box data and the check code are successfully stored in the main storage unit 13, a copy of the data is stored in the backup area of the main storage unit 13. Therefore, the fault management module can calculate the check code based on the black box data in the storage area and compare the check code with the check code stored in the area to determine whether the black box data in the storage area is normal, thereby achieving the check of the black box data.

[0063] In one embodiment, after the controller 10 is powered on, the fault management module is further configured to read the storage data of the target storage area during initialization, calculate a reference check code corresponding to the target storage area according to the read data, and determine that the storage data of the target storage area is abnormal and store the backup data of the target backup area to the target storage area when the check code stored in the target storage area is different from the reference check code.

[0064] It can be understood that, after the controller 10 is powered on, the fault management module reads the storage data of the target storage area during initialization, which can ensure that the state of the controller 10 is stable and the fault management module can normally read the storage data of the target storage area. The fault management module reads the storage data of the target storage area during initialization, calculates a reference check code corresponding to the target storage area according to the read data, and compares the check code stored in the target storage area with the reference check code. If the check code stored in the target storage area is the same as the reference check code, the black box data stored in the target storage area is correct. If the check code stored in the target storage area is different from the reference check code, the black box data is abnormal during storage, which causes the abnormality of the stored black box data. Therefore, it can be determined that the storage data of the target storage area is abnormal. At this time, the last backup black box data (i.e., the black box data backed up by the target backup area) is stored in the target storage area, thereby ensuring the consistency of the black box data.

[0065] In one embodiment, the fault management module is further configured to periodically store the corresponding black box data in the plurality of storage areas of the main storage unit 13 according to the request information in the fault processing queue.

[0066] The black box data is stored in a circular manner, which can ensure uniform erasure of the main memory unit 13, prevent the situation where the storage is continuously erased in the same area, and effectively ensure the life of the main memory unit 13. For example, as shown in Figure 4, the main memory unit 13 can include n (n is greater than 1) storage areas, and the fault management module cyclically stores the black box data in the n storage areas of the main memory unit 13. When the fault management module executes the black box data storage for the first time, the black box data is stored in storage area 1. When the black box data storage is triggered for the second time, the black box data is stored in storage area 2. And so on. When the black box data storage is completed for the nth time, when the black box data is stored again, the storage starts again from storage area 1, and the cycle repeats, thereby improving the service life of the main memory unit 13.

[0067] It should be noted that if different fault types correspond to different storage areas in the main memory unit 13, multiple storage areas can be divided for each fault type, and the fault management module cyclically stores the fault data in multiple storage areas corresponding to the fault type according to the type of the fault data.

[0068] Based on the same inventive concept, the present application also provides a controller, and the software architecture of the controller adopts the software architecture of the controller in any of the above embodiments.

[0069] The processor, utilizing the software architecture of the controller described in any of the above embodiments, stores vehicle operating status data in real time in the controller's local memory unit via the application layer and, upon receiving a fault trigger event, sends an indication message. Upon receiving the indication message, the fault management module of the platform software layer adds the corresponding black box data write request to the fault processing queue and uses the vehicle operating status data temporarily stored in the local memory unit as the black box data. Furthermore, the fault management module can periodically store the corresponding black box data in the main memory unit based on the request information in the fault processing queue, thereby using the main memory unit to store black box data and addressing the controller's limited memory resources. Furthermore, the fault management module periodically stores the corresponding black box data in the main memory unit based on the request information in the fault processing queue, making the black box data storage process asynchronous with the fault trigger event, thereby achieving asynchronous storage of the black box data and ensuring stable operation of the controller.

[0070] In one embodiment, as shown in FIG5 , the present application further provides a black box system, comprising: a main memory unit 13 and a controller 10 as in any of the above embodiments; wherein the controller 10 is connected to the local memory unit and the main memory unit 13 respectively.

[0071] The black box system, including the main storage unit 13 and the controller 10 of any of the above embodiments, periodically stores the corresponding black box data in the main storage unit 13 according to the request information in the fault processing queue, thereby using the main storage unit 13 to store the black box data, solving the problem of tight memory resources in the controller 10, and ensuring the storage of the black box data. In addition, the controller 10 periodically stores the corresponding black box data in the main storage unit 13 according to the request information in the fault processing queue, so that the storage process of the black box data is asynchronous with the fault triggering event, thereby realizing asynchronous storage of the black box data, ensuring stable operation of the controller 10, and ensuring stable storage of the black box data.

[0072] Based on the same inventive concept, the application also provides a control method of a black box system, as shown in FIG. 6, which includes the following steps S601-S603.

[0073] S601: Real-time acquisition of automobile running state data and storage in a local memory unit.

[0074] S602: In the case of receiving a fault triggering event, a corresponding black box data write request is added to the fault processing queue, and the automobile running state data temporarily stored in the local memory unit is used as the black box data.

[0075] S603: Periodically store the corresponding black box data in the main storage unit according to the request information in the fault processing queue.

[0076] The control method of the black box system, by real-time acquisition of automobile running state data and storage in a local memory unit, in the case of receiving a fault triggering event, a corresponding black box data write request is added to the fault processing queue, and the automobile running state data temporarily stored in the local memory unit is used as the black box data, and then the corresponding black box data is periodically stored in the main storage unit according to the request information in the fault processing queue, thereby using the main storage unit to store the black box data, solving the problem of tight memory resources in the controller. In addition, according to the request information in the fault processing queue, the corresponding black box data is stored in the main storage unit, so that the storage process of the black box data is asynchronous with the fault triggering event, thereby realizing asynchronous storage of the black box data, ensuring stable operation of the controller.

[0077] In one embodiment, the control method of the black box system further includes the steps of: in the case of receiving a fault triggering event, determining the fault type, and when storing the black box data to the main storage unit, storing the corresponding black box data to a specified area of the main storage unit according to the fault type. Different fault types correspond to different storage areas in the main storage unit.

[0078] In one embodiment, the control method of the black box system further comprises: in the case that a diagnostic message indicating reading of the black box data is received, copying the fault data of the corresponding region in the main storage unit to the local memory unit in response to the calling instruction, and outputting the fault data in the local memory unit.

[0079] In one embodiment, the control method of the black box system further comprises: in the case that a diagnostic service message with a data identifier is received, erasing the data of the corresponding storage region in the main storage unit according to the diagnostic service message.

[0080] In one embodiment, the main storage unit has a plurality of storage regions and a plurality of backup regions. In S603, periodically storing the corresponding black box data in the main storage unit according to the request information in the fault processing queue comprises: determining a corresponding target check code according to the target black box data to be stored, writing the target black box data and the target check code to a target storage region of the main storage unit, and after successful writing, backing up the stored data in the target storage region to a corresponding target backup space.

[0081] In one embodiment, the control method of the black box system further comprises: in the case that the power is turned on, reading the stored data of the target storage region at initialization, calculating a reference check code corresponding to the target storage region according to the read data, and in the case that the check code stored in the target storage region is different from the reference check code, determining that the stored data of the target storage region is abnormal, and storing the backup data of the target backup region to the target storage region.

[0082] In one embodiment, in S603, periodically storing the corresponding black box data in the main storage unit according to the request information in the fault processing queue comprises: the fault management module is further configured to periodically store the corresponding black box data in a plurality of storage regions of the main storage unit according to the request information in the fault processing queue.

[0083] It should be understood that, although each step in the flowchart involved in each embodiment as described above is shown in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or stages in other steps.

[0084] In one example embodiment, the application also provides a vehicle comprising a memory and a processor, the memory storing a computer program, the processor implementing the steps of the control method of the black box system according to any one of the above embodiments when executing the computer program.

[0085] The internal structure of the vehicle can be as shown in FIG. 7. The vehicle comprises a processor (which can be the vehicle controller, corresponding to the controller above), a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the vehicle is configured to provide computing and control capabilities. The memory of the vehicle comprises a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The input / output interface of the vehicle is configured to exchange information between the processor and external devices. The communication interface of the vehicle is configured to communicate with external terminals in a wired or wireless manner. The wireless manner can be achieved through WIFI, mobile cellular network, NFC (Near Field Communication) or other technologies. The computer program is executed by the processor to implement a control method of a black box system. The display unit of the vehicle is configured to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the vehicle can be a touch layer overlaid on the display screen, or a key, trackball or touchpad arranged on the vehicle shell, or an external keyboard, touchpad or mouse, etc.

[0086] Those skilled in the art can understand that the structure shown in FIG. 7 is only a block diagram of part of the structure related to the scheme of the application, and does not constitute a limitation on the computer device to which the scheme of the application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0087] In one embodiment, the application also provides a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the steps of the control method of the black box system according to any one of the above embodiments.

[0088] In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the control method of the black box system according to any one of the above embodiments.

[0089] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0090] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to a memory, a database or other medium used in the embodiments provided in the present application can include at least one of a non-volatile and a volatile memory. The non-volatile memory can include a read-only memory (ROM), a magnetic tape, a floppy disk, a flash memory, an optical storage, a high-density embedded non-volatile memory, a resistive memory (ReRAM), a magnetoresistive random access memory (MRAM), a ferroelectric memory (FRAM), a phase change memory (PCM), a graphene memory, etc. The volatile memory can include a random access memory (RAM) or an external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as a static random access memory (SRAM) or a dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., and is not limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., and is not limited thereto.

[0091] The technical features of the above embodiments can be combined in any manner. To make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combinations of the technical features do not exist contradictions, they should be considered as the scope of the present disclosure.

[0092] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. A software architecture of a controller, characterized in that: The software architecture includes: an application layer and a platform software layer, wherein: The application layer is used to store the vehicle operation status data in the local memory unit of the controller in real time, and send indication information to the platform software layer when a fault trigger event is received; The platform software layer includes a fault management module, which is used to add the corresponding black box data write request to the fault processing queue when receiving the instruction information, and use the vehicle operation status data temporarily stored in the local memory unit as black box data; The fault management module is further configured to periodically store the corresponding black box data in a main memory unit according to the request information in the fault processing queue.

2. The software architecture of the controller according to claim 1, characterized in that: The application layer is further configured to classify data faults upon receiving a fault trigger event, and output corresponding indication information according to the type of data fault; The fault management module is also used to determine the fault type according to the indication information, and when storing the black box data in the main memory unit, store the corresponding black box data in a designated area of ​​the main memory unit according to the fault type, wherein different fault types correspond to different storage areas of the main memory unit.

3. The software architecture of the controller according to claim 1, characterized in that: The platform software layer further includes a diagnostic module, which is configured to send a call instruction to the fault management module upon receiving a diagnostic message indicating to read black box data; The fault management module is also used to copy the fault data of the corresponding area in the main memory unit to the local memory unit in response to the call instruction, and transmit the fault data in the local memory unit to the diagnosis module so that the diagnosis module outputs the fault data.

4. The software architecture of the controller according to claim 3, characterized in that: The fault management module is further configured to, upon receiving a diagnostic service message having a data identifier, erase data in a corresponding storage area in the main memory unit according to the diagnostic service message.

5. The software architecture of the controller according to claim 1, characterized in that: The main memory unit has multiple storage areas and multiple backup areas; the fault management module is also used to determine the corresponding target verification code according to the target black box data that needs to be stored, and write the target black box data and the target verification code into the target storage area of ​​the main memory unit. After the writing is successful, the storage data in the target storage area is backed up to the corresponding target backup space.

6. The software architecture of the controller according to claim 5, characterized in that: After the controller is powered on, the fault management module is further used to read the storage data of the target storage area during initialization, calculate the reference check code corresponding to the target storage area based on the read data, and when the check code stored in the target storage area is different from the reference check code, determine that the storage data of the target storage area is abnormal, and store the backup data of the target backup area in the target storage area.

7. The software architecture of the controller according to claim 1, characterized in that: The main memory unit has multiple storage areas; the fault management module is further used to periodically and cyclically store the corresponding black box data in the multiple storage areas of the main memory unit according to the request information in the fault processing queue.

8. A controller, characterized in that: The software architecture of the processor adopts the software architecture of the controller according to any one of claims 1 to 7.

9. A black box system, characterized in that: include: A main memory unit and a controller as claimed in claim 8; wherein the controller is connected to the local memory unit and the main memory unit respectively.

10. A method for controlling a black box system, characterized in that: The method comprises: Acquire vehicle operating status data in real time and store it in a local memory unit; In the case of receiving a fault trigger event, adding the corresponding black box data write request to the fault processing queue, and using the vehicle running status data temporarily stored in the local memory unit as the black box data; The corresponding black box data is periodically stored in a main memory unit according to the request information in the fault processing queue.

11. A vehicle comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to claim 10 are implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to claim 10 are implemented.

Images