A bus data backhaul method and system, electronic device, storage medium

Abstract

The application discloses a bus data backhaul method and system, electronic equipment and a storage medium. The method comprises the following steps: collecting layers to capture each CAN bus message generated by a vehicle in real time; screening the CAN bus message containing a pre-configured target signal from the CAN bus message, and sending the CAN bus message to a trigger calculation backhaul layer and storing the CAN bus message in a hard disk; the trigger calculation backhaul layer uses corresponding trigger operators to calculate the target signal in each CAN bus message received, and generates trigger information entries of each CAN bus message in which the calculation result satisfies the corresponding trigger condition in a database; the trigger calculation backhaul layer extracts the trigger information entries of the unbackhauled CAN bus message in sequence, and finds the corresponding CAN bus message from the hard disk according to the extracted trigger information entries; and the trigger calculation backhaul layer returns the found CAN bus message to a vehicle cloud communication layer, so as to upload the returned CAN bus message to the cloud.

Description

Technical Field

[0001] This application relates to the field of vehicle electronics technology, and in particular to a bus data backhaul method and system, electronic device, and storage medium. Background Technology

[0002] With the increasing intelligence of automobiles, intelligent connected vehicles have become mobile computing and storage platforms, generating massive amounts of data daily. This data holds immense value for big data analytics applications at every stage of the vehicle's lifecycle, including R&D, testing, mass production, and user experience improvement. Therefore, it is necessary to collect this data for subsequent processing and analysis.

[0003] Currently, the main process involves collecting CAN bus data generated by the vehicle during driving or testing, and storing all collected data on a local domain controller hard drive. When data processing and analysis are needed later, the local hard drive is removed and reinserted into the server. The data is then manually copied from the hard drive for processing and analysis.

[0004] However, this method cannot transmit data back in a timely manner, so it has a certain information lag. It also requires storing a large amount of data, of which only a portion is useful, thus occupying a lot of storage space and affecting the efficiency of data processing and analysis. Summary of the Invention

[0005] In view of the shortcomings of the prior art, this application provides a bus data backhaul method and system, electronic device and storage medium to solve the problems of the prior art being lagging behind, requiring a large amount of storage space and affecting processing efficiency.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] The first aspect of this application provides a bus data return method, including:

[0008] The acquisition layer captures all CAN bus messages generated by the vehicle in real time.

[0009] The acquisition layer filters out CAN bus messages containing pre-configured target signals from each CAN bus message, and sends the filtered CAN bus messages to the trigger calculation return layer and stores them in the hard disk; wherein, the target signal is the signal required for the configured trigger operator calculation;

[0010] The trigger calculation backhaul layer uses the corresponding trigger operator to calculate the target signal in each of the received CAN bus messages;

[0011] The trigger calculation feedback layer generates trigger information entries in the database for each CAN bus message whose calculation results satisfy the corresponding trigger conditions;

[0012] The trigger calculation backhaul layer sequentially extracts trigger information entries for CAN bus messages that have not been returned, and retrieves the corresponding CAN bus message from the hard disk based on the extracted trigger information entries;

[0013] The trigger calculation backhaul layer will send the found CAN bus message back to the vehicle-cloud communication layer;

[0014] The vehicle-to-cloud communication layer uploads the returned CAN bus messages to the cloud.

[0015] Optionally, in the above-described bus data return method, after sending the selected CAN bus messages to the trigger calculation return layer and storing them in the hard disk, the method further includes:

[0016] The CAN data entry node of the acquisition layer sends the basic data of each of the selected CAN bus messages to the full data information database management node in the trigger calculation return layer; wherein, the basic data includes at least message attribute information and storage path information;

[0017] The full data information database management node generates data information entries for the CAN bus message in the database using time as the index and the basic data of the CAN bus message as the entries.

[0018] Optionally, in the above-described bus data return method, the trigger calculation return layer sequentially extracts trigger information entries of the CAN bus messages that have not been returned, and retrieves the corresponding CAN bus messages from the hard disk based on the extracted trigger information entries, including:

[0019] The backhaul service node in the trigger calculation backhaul layer periodically calls the trigger information database management node in the trigger calculation backhaul layer to extract the trigger information entries of the CAN bus messages that have not been backhauled in sequence.

[0020] The backhaul service node calls the full data information database management node to find the corresponding data information entry based on the information of the extracted trigger information entry;

[0021] The backhaul service node retrieves the corresponding CAN bus message from the hard drive based on the found data information entries.

[0022] Optionally, the above-described bus data return method further includes:

[0023] The full-database management node identifies data information entries whose storage time has reached a preset time.

[0024] The corresponding CAN bus message is found based on the determined data information entries;

[0025] The found CAN bus messages are compressed and saved, and the original CAN bus messages are deleted.

[0026] The data information entries of the compressed CAN bus message are updated using its storage path.

[0027] Optionally, in the above-described bus data return method, the trigger calculation return layer generates trigger information entries in the database for each CAN bus message whose calculation results satisfy the corresponding trigger conditions, including:

[0028] The operator trigger management node in the trigger calculation backhaul layer determines whether any one of the calculation results of each CAN bus message satisfies the corresponding trigger condition.

[0029] When the operator trigger management node determines that any one of the calculation results of the CAN bus message satisfies the corresponding trigger condition, it sends the trigger information of the CAN bus message to the trigger information library management node in the trigger calculation backhaul layer; wherein, the trigger information includes operator trigger information, the target signal, the calculation result, and the message information to be backhauled;

[0030] The trigger information database management node uses the trigger information of the CAN bus message to generate trigger information entries for the CAN bus message in the database.

[0031] Optionally, the above-described bus data return method further includes:

[0032] The trigger information database management node in the trigger calculation backhaul layer periodically deletes the marked trigger information entries; wherein, after extracting the trigger information entries, the trigger information database management node marks the extracted trigger information entries.

[0033] Optionally, the above-described bus data return method further includes:

[0034] The acquisition layer retrieves the configuration file sent or placed by the user through the cloud from the vehicle-cloud communication layer; wherein, the configuration file includes the trigger operator, the target signal corresponding to the trigger operator, and the trigger condition; the target signal corresponding to the trigger operator is the signal required for its calculation.

[0035] A second aspect of this application provides a bus data return system, comprising:

[0036] The data acquisition layer, the trigger calculation and feedback layer, and the vehicle-to-cloud communication layer;

[0037] The acquisition layer is used to capture each CAN bus message generated by the vehicle in real time, and to filter out the CAN bus messages containing a pre-configured target signal from each CAN bus message, and send the filtered CAN bus messages to the trigger calculation return layer and store them in the hard disk; wherein, the target signal is the signal required for the configured trigger operator calculation;

[0038] The trigger calculation and feedback layer is used to calculate the target signal in each of the received CAN bus messages using the corresponding trigger operators, generate trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database, extract trigger information entries for CAN bus messages that have not been fed back, find the corresponding CAN bus message from the hard disk according to the extracted trigger information entries, and feed the found CAN bus message back to the vehicle-cloud communication layer.

[0039] The vehicle-to-cloud communication layer is used to upload the returned CAN bus messages to the cloud.

[0040] Optionally, in the above-mentioned bus data backhaul system, the acquisition layer includes a CAN data entry node, and the trigger calculation backhaul layer includes a full data information database management node.

[0041] The CAN data entry node is used to send the basic data of each of the selected CAN bus messages to the full data information database management node; wherein, the basic data includes at least message attribute information and storage path information;

[0042] The full data information database management node is used to generate data information entries for the CAN bus message in the database, using time as the index and the basic data of the CAN bus message as the entries.

[0043] Optionally, in the above-described bus data backhaul system, when the trigger calculation backhaul layer sequentially extracts trigger information entries of the CAN bus messages that have not been backhauled, and searches for the corresponding CAN bus message from the hard disk based on the extracted trigger information entries, it is used for:

[0044] The backhaul service node in the trigger calculation backhaul layer periodically calls the trigger information database management node in the trigger calculation backhaul layer to sequentially extract the trigger information terms of the CAN bus messages that have not been backhauled. Based on the information of the extracted trigger information terms, the full data information database management node is called to find the corresponding data information terms. Based on the found data information terms, the corresponding CAN bus message is found from the hard disk.

[0045] Optionally, in the aforementioned bus data backhaul system, the full data information database management node is further configured to:

[0046] Identify the data information entries whose storage time has reached a preset time;

[0047] The corresponding CAN bus message is found based on the determined data information entries;

[0048] The found CAN bus messages are compressed and saved, and the original CAN bus messages are deleted.

[0049] The data information entries of the compressed CAN bus message are updated using its storage path.

[0050] Optionally, in the aforementioned bus data return system, when the trigger calculation return layer generates trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database, it is used for:

[0051] The operator trigger management node in the trigger calculation backhaul layer determines whether any calculation result of each CAN bus message satisfies the corresponding trigger condition. If any calculation result of the CAN bus message satisfies the corresponding trigger condition, the trigger information of the CAN bus message is sent to the trigger information database management node in the trigger calculation backhaul layer. The trigger information includes operator trigger information, the target signal, the calculation result, and the message information to be backhauled.

[0052] The trigger information database management node uses the trigger information of the CAN bus message to generate trigger information entries for the CAN bus message in the database.

[0053] Optionally, in the above-described bus data backhaul system, the trigger calculation backhaul layer is further configured to:

[0054] The trigger information database management node in the trigger calculation backhaul layer periodically deletes the marked trigger information entries; wherein, after extracting the trigger information entries, the trigger information database management node marks the extracted trigger information entries.

[0055] Optionally, in the above-described bus data backhaul system, the acquisition layer is further configured to:

[0056] The configuration file is retrieved from the vehicle-cloud communication layer, which is either sent or placed by the user through the cloud. The configuration file includes the trigger operator, the target signal corresponding to the trigger operator, and the trigger condition. The target signal corresponding to the trigger operator is the signal required for its calculation.

[0057] A third aspect of this application provides an electronic device, comprising:

[0058] Memory and processor;

[0059] The memory is used to store programs;

[0060] The processor is used to execute the program, which, when executed, is specifically used to implement the bus data return method as described in any of the above.

[0061] A fourth aspect of this application provides a computer storage medium for storing a computer program, which, when executed by a processor, is used to implement the bus data return method as described in any of the preceding claims.

[0062] This application provides a bus data backhaul method. The acquisition layer captures various CAN bus messages generated by the vehicle in real time, filters out CAN bus messages containing pre-configured target signals, and sends the filtered CAN bus messages to the trigger calculation backhaul layer and stores them in the hard disk. The target signal is the signal required for calculation by the configured trigger operator. Thus, by using the configured information, messages that require further calculation are filtered and stored, instead of storing all messages, thereby reducing storage space usage. Then, the trigger calculation backhaul layer uses the corresponding trigger operator to calculate the target signal in each received CAN bus message and generates trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database. Subsequently, the trigger calculation backhaul layer sequentially extracts the trigger information entries of CAN bus messages that have not been backhauled and retrieves the corresponding CAN bus messages from the hard disk based on the extracted trigger information entries. Finally, the trigger calculation backhaul layer sends the found CAN bus messages back to the vehicle-cloud communication layer, and the vehicle-cloud communication layer uploads the backed-back CAN bus messages to the cloud. Thus, the trigger operator performs calculations and corresponding judgments on the target signal, extracting only the messages that need to be processed and analyzed and sending them back to the user. Therefore, the required messages can be sent back efficiently in a timely manner, ensuring the timeliness of the data. Attached Figure Description

[0063] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0064] Figure 1 A schematic diagram of the architecture of a bus data backhaul system provided in this application embodiment;

[0065] Figure 2 This application provides a schematic diagram of the architecture of a data acquisition layer.

[0066] Figure 3 A flowchart illustrating a bus data return method provided in this application embodiment;

[0067] Figure 4 A flowchart illustrating a method for compressing stored CAN bus messages, provided as an embodiment of this application;

[0068] Figure 5 A flowchart illustrating a method for generating trigger information terms provided in this application embodiment;

[0069] Figure 6 A flowchart illustrating a method for locating returned CAN bus messages, provided in an embodiment of this application;

[0070] Figure 7 This is a schematic diagram of the architecture of an electronic device provided in an embodiment of this application. Detailed Implementation

[0071] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0072] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0073] This application provides a bus data backhaul method to address the problems of information lag, high storage space requirements, and reduced data processing and analysis efficiency in existing technologies. To implement the bus data backhaul method provided in this application, a bus data backhaul system is also provided, such as... Figure 1 As shown, the top layer is the vehicle's CAN bus data acquisition layer, the middle layer is the trigger calculation and feedback layer, and the bottom layer is the vehicle-cloud communication layer.

[0074] Among them, such as Figure 1 As shown, the acquisition layer can include an active pull interface, an active trigger interface, a CAN publish interface, an acquired information publish interface, a cloud control interface, and a configuration file pull interface. The active pull interface is mainly used by the user to actively pull historical information for feedback, i.e., to pull and transmit previously acquired and stored messages. The active trigger interface is mainly used to actively trigger related transaction processing for CAN bus messages. The CAN publish interface is mainly used to send filtered CAN bus messages to the operator trigger management node of the trigger calculation feedback layer for trigger processing. The acquired information publish interface is used to send relevant information of CAN bus messages to the full data information database management node of the trigger calculation feedback layer to generate corresponding entries for data management. The cloud control interface connects to the vehicle-cloud communication cloud control interface to communicate with the cloud, allowing users to perform related control operations on the system through this interface. The configuration file pull interface is used to pull configuration files uploaded to the cloud by the user through the vehicle-cloud communication layer.

[0075] More specifically, such as Figure 2 As shown, the acquisition layer can capture CAN bus data and filter the captured data.

[0076] like Figure 1As shown, the trigger calculation feedback layer includes an operator trigger management node, a trigger information database management node, a feedback service node, a full data information database management node, a data extraction service node, and a compression service node.

[0077] The operator trigger management node parses the filtered CAN bus messages and periodically performs trigger calculations. It also periodically identifies CAN bus messages that meet the trigger conditions and sends the trigger information to the trigger information database management node. The trigger information database management node uses the trigger information to add messages to its database and continuously deletes information that meets the conditions, i.e., it deletes trigger information for already returned CAN bus messages. When triggering subsequent transmissions based on the database information, the transmission service node calls the data extraction service node to retrieve the CAN bus messages to be transmitted. The data extraction service node primarily responds to requests from the transmission service node and retrieves the necessary CAN bus messages. Then, the transmission service node calls the compression service node to compress the retrieved CAN bus messages before transmitting them back to the vehicle-to-cloud communication layer.

[0078] The full data information database management node stores the collected CAN bus messages and their information in the database, and periodically compresses CAN bus messages stored for a certain period of time. Furthermore, when the data return service retrieves data, it looks up the corresponding CAN bus message and sends it back to the return service node for transmission.

[0079] like Figure 3 As shown in the figure, a bus data backhaul method provided in this application embodiment specifically includes the following steps:

[0080] S301, the acquisition layer captures various CAN bus messages generated by the vehicle in real time.

[0081] Specifically, each CAN bus message can be captured and generated by the CAN bus driver. Alternatively, CAN bus messages can be captured through a capture node set in the acquisition layer.

[0082] S302 The acquisition layer filters out CAN bus messages containing pre-configured target signals from various CAN bus messages, and sends the filtered CAN bus messages to the trigger calculation return layer and stores them in the hard disk.

[0083] The target signal is the signal required for the configured trigger operator to perform calculations.

[0084] It should be noted that, since only a portion of the large number of CAN bus messages generated are often needed, in order to avoid occupying a large amount of storage space to store a large number of CAN bus messages, it is necessary to filter out the required messages from the collected CAN bus messages.

[0085] Optionally, each captured CAN bus message can be filtered. Alternatively, the captured CAN bus messages can be filtered in batches at regular intervals. Or, whenever the number of captured CAN bus messages reaches a certain threshold, these CAN bus messages can be filtered in batches.

[0086] Specifically, in this embodiment, the signals required for calculation by each trigger operator during subsequent trigger analysis are pre-configured, i.e., target signals. Therefore, during the filtering process, if a CAN bus message contains any target signal, it indicates that it is a required CAN bus message and thus needs to be filtered out. Specifically, the CAN bus message can be parsed using a DBC file to obtain the signals within it. Then, a comparison and matching method is used to determine whether the CAN bus message contains a target signal. If the CAN bus message contains a target signal, it is filtered out.

[0087] Optionally, a CAN filtering node can be set in the acquisition layer to filter CAN bus messages.

[0088] Optionally, to facilitate the configuration of target information and triggering operator information, in another embodiment of this application, the retrieval of a configuration file may be further included, specifically including:

[0089] The data acquisition layer retrieves configuration files that users send or place through the cloud from the vehicle-cloud communication layer.

[0090] The configuration file includes the triggering operator, the target signal corresponding to the triggering operator, and the triggering condition. The target signal corresponding to the triggering operator is the signal required for its calculation.

[0091] Therefore, the target signal can be obtained from the configuration file for filtering and screening CAN bus messages.

[0092] It should also be noted that the selected CAN bus messages are sent to the trigger calculation and feedback layer to analyze whether they are messages that need to be fed back to the user for analysis and processing. Furthermore, since there are usually a relatively large number of selected CAN bus messages, and the trigger calculation and analysis takes time, the CAN bus messages need to be stored on the hard drive beforehand for subsequent feedback. This also makes it easier to retrieve them from the hard drive when needed later. Therefore, the selected CAN bus messages need to be stored on the hard drive.

[0093] Optionally, to facilitate quick retrieval of the stored CAN bus messages, in another embodiment of this application, after performing step S302, the following may be further included:

[0094] The CAN data entry node in the acquisition layer sends the basic data of each selected CAN bus message to the full data information database management node in the trigger calculation and feedback layer. The full data information database management node then generates data information entries for the CAN bus message in the database using time as the index and the basic data of the CAN bus message as the entries.

[0095] The basic data includes at least message attribute information and storage path information. Optionally, the message attribute information may include the message size and generation time, etc.

[0096] Optionally, to avoid excessive space usage by existing CAN bus messages, another embodiment of this application further includes compressing the stored CAN bus messages. For example... Figure 4 As shown in the embodiments of this application, the method for compressing stored CAN bus messages includes:

[0097] S401, The full data information database management node identifies data information entries whose storage time has reached the preset time.

[0098] Optionally, the full data information database management node in the trigger computation backhaul layer can periodically perform rolling compression and deletion to identify data information entries whose storage time has reached a preset time. Then, the following operations are performed on these data information entries.

[0099] S402. Locate the corresponding CAN bus message based on the determined data information entries.

[0100] Specifically, based on the storage path information in the determined data information entries, the CAN bus message corresponding to the entry is located from the hard drive.

[0101] S403. Compress and save the found CAN bus messages, and delete the original CAN bus messages.

[0102] The identified CAN bus messages are compressed, and the compressed CAN bus messages are saved to the hard drive. Correspondingly, the original CAN bus messages, i.e., the uncompressed CAN bus messages, need to be deleted to reduce storage space usage.

[0103] S404. Update the data information entries of the compressed CAN bus message using the storage path of the compressed CAN bus message.

[0104] Since the CAN bus message has been re-stored at this time, its storage path has changed. In order to ensure that the compressed file of the CAN bus message can be found later based on the data information entries of the CAN bus message, it is necessary to update its data information entries using the storage path of the compressed CAN bus message.

[0105] S303 and the trigger calculation backhaul layer respectively use the corresponding trigger operators to calculate the target signal in each received CAN bus message.

[0106] It should be noted that while a received CAN bus message indicates the presence of an important signal, i.e., a target signal, this message is not necessarily one that requires immediate processing and analysis. Therefore, to ensure timely processing and avoid information delays and the need to transmit large amounts of useless data back, a trigger operator is used to calculate the target signal to determine whether it requires immediate transmission. For example, the speed data in the message can be used to calculate the vehicle's deceleration rate to determine if the deceleration rate is normal. If it is abnormal, timely transmission for analysis is necessary.

[0107] Specifically, the trigger calculation return layer progressively parses each received CAN bus message using a message parsing file (DBC file) to obtain the target signals contained within. Then, each target signal in the message is substituted into the corresponding trigger operator for calculation, thus obtaining the calculation result for the CAN bus message. Since a single CAN bus message may contain multiple target signals, its calculation result can include multiple values.

[0108] S304. The trigger calculation return layer generates trigger information entries for each CAN bus message whose calculation results meet the corresponding trigger conditions in the database.

[0109] Specifically, after calculating the results of the CAN bus message, the trigger calculation and return layer determines whether each calculation result of the CAN bus message meets the corresponding trigger submission. For example, whether the deceleration frequency is greater than a preset threshold. If any calculation result of the CAN bus message meets the corresponding trigger condition, it means that it needs to be returned. However, since data return takes a certain amount of time, and in order to return messages in parallel during data calculation, in this embodiment, for CAN bus messages that meet the corresponding trigger conditions, trigger information entries for the CAN bus message are generated using their trigger information. These entries are used by the return service node to extract and consume entries from the database, and to return the CAN bus message corresponding to the trigger information entry.

[0110] The triggering information of the CAN bus message includes information related to the triggering of the current CAN bus message, such as information about the triggering operator and the target information.

[0111] Optionally, in another embodiment of this application, one specific manner of step S304 is as follows: Figure 5 As shown, it includes the following steps:

[0112] S501, the operator trigger management node in the trigger calculation backhaul layer determines whether any of the calculation results of each CAN bus message satisfies the corresponding trigger condition.

[0113] When the operator trigger management node determines that any one of the calculation results of the CAN bus message satisfies the corresponding trigger condition, it executes step S302.

[0114] S502. Send the trigger information of the CAN bus message to the trigger information library management node in the trigger calculation and feedback layer.

[0115] The triggering information includes operator triggering information, target signal, calculation results, and message information that needs to be transmitted back. Operator triggering information may include relevant information about the triggering operator, triggering time, etc. The message information that needs to be transmitted back is pre-configured and related to the calculation results, to facilitate subsequent data analysis.

[0116] S503, the trigger information database management node uses the trigger information of the CAN bus message to generate trigger information entries for the CAN bus message in the database.

[0117] S305: The trigger calculation and return layer sequentially extracts the trigger information entries of the CAN bus messages that have not been returned, and finds the corresponding CAN bus messages from the hard disk based on the extracted trigger information entries.

[0118] Optionally, the trigger information entries for each non-returned CAN bus message are extracted sequentially from the trigger calculation and return layer, using the trigger time as the lookup index. Since the trigger information entries of the CAN bus message store relevant information about the CAN bus message, the corresponding CAN bus message is retrieved from the hard drive based on this information, so that it can be returned.

[0119] Optionally, in another embodiment of this application, one specific implementation of step S305 is as follows: Figure 6 As shown, it includes the following steps:

[0120] S601. The backhaul service node in the trigger calculation backhaul layer periodically calls the trigger information database management node in the trigger calculation backhaul layer to extract the trigger information entries of the CAN bus messages that have not been backhauled.

[0121] Specifically, the backhaul service node periodically calls the trigger information database management node in the trigger calculation backhaul layer, using the trigger time as the search index, to sequentially extract the trigger information entries for each CAN bus message that has not been backhauled.

[0122] S602. The return service node calls the full data information database management node based on the information of the extracted trigger information term to find the corresponding data information term.

[0123] Specifically, the return service node calls the full data information database management node, which then retrieves the corresponding data information entry from the full data information database management node based on the information in the CAN bus message in the trigger information entry.

[0124] S603, the return service node retrieves the corresponding CAN bus message from the hard drive based on the found data information entries.

[0125] Specifically, the return service node locates the corresponding CAN bus message from the corresponding path on the hard drive based on the path information in the found data information entries. Optionally, the corresponding CAN bus message can be retrieved through the data retrieval service node.

[0126] Optionally, in addition to periodically extracting trigger information terms and transmitting the corresponding messages back, in another embodiment of this application, the user can also actively extract the required CAN bus messages for transmission back through the acquisition layer.

[0127] Optionally, in order to avoid repeatedly extracting trigger information terms from CAN bus messages and thus avoid repeatedly sending back CAN bus messages, in this embodiment of the application, for trigger information terms that have already been extracted, the terms are marked in the database, so that it can be determined whether the terms have been extracted based on the marking.

[0128] Since the extracted trigger information terms no longer have any tasks, optionally, in another embodiment of this application, it may further include:

[0129] The trigger information database management node in the trigger calculation feedback layer periodically deletes the marked trigger information entries.

[0130] Among them, the trigger information database management node marks the extracted trigger information terms after extracting them.

[0131] S306, the trigger calculation backhaul layer sends the found CAN bus message back to the vehicle-cloud communication layer.

[0132] Optionally, to facilitate the transmission of the found CAN bus messages, the CAN bus messages are compressed before transmission. Optionally, the CAN bus messages can be compressed by a compression service node.

[0133] S307, the vehicle-to-cloud communication layer uploads the returned CAN bus messages to the cloud.

[0134] Specifically, the vehicle-cloud communication layer communicates with the cloud to upload the returned CAN bus messages to the cloud, so that users can obtain the returned CAN bus messages through the cloud.

[0135] This application provides a bus data backhaul method. The acquisition layer captures various CAN bus messages generated by the vehicle in real time, filters out CAN bus messages containing pre-configured target signals, and sends the filtered CAN bus messages to the trigger calculation backhaul layer and stores them in the hard disk. The target signal is the signal required for calculation by the configured trigger operator. Thus, by using the configured information, messages that require further calculation are filtered and stored, instead of storing all messages, thereby reducing storage space usage. Then, the trigger calculation backhaul layer uses the corresponding trigger operator to calculate the target signal in each received CAN bus message, and generates trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database. Subsequently, the trigger calculation backhaul layer sequentially extracts the trigger information entries of CAN bus messages that have not been backhauled, and retrieves the corresponding CAN bus messages from the hard disk based on the extracted trigger information entries. Finally, the trigger calculation backhaul layer sends the found CAN bus messages back to the vehicle-cloud communication layer, and the vehicle-cloud communication layer uploads the backed-back CAN bus messages to the cloud. Thus, the trigger operator performs calculations and corresponding judgments on the target signal, extracting only the messages that need to be processed and analyzed and sending them back to the user. Therefore, the required messages can be sent back efficiently in a timely manner, ensuring the timeliness of the data.

[0136] Another embodiment of this application provides another bus data return system, see also [link to relevant documentation]. Figure 1 ,include:

[0137] The data acquisition layer, the trigger calculation and feedback layer, and the vehicle-to-cloud communication layer.

[0138] The acquisition layer is used to capture various CAN bus messages generated by the vehicle in real time, and to filter out CAN bus messages containing pre-configured target signals from these messages. The filtered CAN bus messages are then sent to the trigger calculation feedback layer and stored on the hard drive. The target signal is the signal required for calculation by the configured trigger operator.

[0139] The trigger calculation and feedback layer is used to calculate the target signal in each received CAN bus message using the corresponding trigger operator, generate trigger information entries for each CAN bus message whose calculation results meet the corresponding trigger conditions in the database, extract trigger information entries for CAN bus messages that have not been fed back, find the corresponding CAN bus message from the hard disk based on the extracted trigger information entries, and send the found CAN bus message back to the vehicle-cloud communication layer.

[0140] The vehicle-to-cloud communication layer is used to upload the returned CAN bus messages to the cloud.

[0141] Optionally, in another embodiment of the bus data backhaul system provided in this application, the acquisition layer includes a CAN data entry node, and the trigger calculation backhaul layer includes a full data information database management node.

[0142] The CAN data entry node is used to send the basic data of each selected CAN bus message to the full data information database management node.

[0143] The basic data includes at least message attribute information and storage path information.

[0144] The full data information database management node is used to generate data information entries for CAN bus messages in the database, using time as the index and the basic data of CAN bus messages as the entries.

[0145] Optionally, in the bus data backhaul system provided in another embodiment of this application, when the trigger calculation backhaul layer sequentially extracts the trigger information entries of the CAN bus messages that have not been backhauled, and searches for the corresponding CAN bus messages from the hard disk based on the extracted trigger information entries, it is used for:

[0146] The backhaul service node in the trigger calculation backhaul layer periodically calls the trigger information database management node in the trigger calculation backhaul layer to extract the trigger information terms of the CAN bus messages that have not been returned. Based on the information of the extracted trigger information terms, the full data information database management node is called to find the corresponding data information terms. Based on the found data information terms, the corresponding CAN bus message is found in the hard drive.

[0147] Optionally, in another embodiment of the bus data backhaul system provided in this application, the full data information database management node is further used for:

[0148] Identify data entries whose storage time has reached the preset time.

[0149] The corresponding CAN bus message is found based on the identified data information entries.

[0150] The found CAN bus messages are compressed and saved, and the original CAN bus messages are deleted.

[0151] The data information entries of the compressed CAN bus message are updated using the storage path of the compressed CAN bus message.

[0152] Optionally, in the aforementioned bus data return system, when the trigger calculation return layer generates trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database, it is used for:

[0153] The operator trigger management node in the trigger calculation backhaul layer determines whether any calculation result of each CAN bus message satisfies the corresponding trigger condition. If any calculation result of the CAN bus message satisfies the corresponding trigger condition, the trigger information of the CAN bus message is sent to the trigger information database management node in the trigger calculation backhaul layer. The trigger information includes operator trigger information, target signal, calculation result, and message information to be backhauled.

[0154] By using the trigger information of CAN bus messages in the trigger information database management node, trigger information entries for CAN bus messages are generated in the database.

[0155] Optionally, in another embodiment of the bus data backhaul system provided in this application, triggering the computation backhaul layer is further used for:

[0156] The trigger information database management node in the trigger computation backhaul layer periodically deletes the marked trigger information entries. Specifically, the trigger information database management node marks the extracted trigger information entries after extraction.

[0157] Optionally, in another embodiment of the bus data backhaul system provided in this application, the acquisition layer is further configured to:

[0158] The system retrieves configuration files from the vehicle-to-cloud communication layer, which are either distributed or placed by the user via the cloud. These configuration files include trigger operators, the target signals corresponding to the trigger operators, and the trigger conditions. The target signals corresponding to the trigger operators are the signals required for their calculations.

[0159] Another embodiment of this application provides an electronic device, such as... Figure 7 As shown, it includes:

[0160] Memory 701 and processor 702.

[0161] The memory 701 is used to store the program.

[0162] The processor 702 is used to execute the program stored in the memory 701. When the program is executed, it is specifically used to implement the bus data return method provided in any of the above embodiments.

[0163] Another embodiment of this application provides a computer storage medium for storing a computer program, which, when executed by a processor, is used to implement the bus data return method provided in any of the above embodiments.

[0164] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0165] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0166] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A bus data return method, characterized in that, include: The acquisition layer captures all CAN bus messages generated by the vehicle in real time. The acquisition layer filters out CAN bus messages containing pre-configured target signals from each CAN bus message, and sends the filtered CAN bus messages to the trigger calculation return layer and stores them in the hard disk; wherein, the target signal is the signal required for the configured trigger operator calculation; The trigger calculation backhaul layer uses the corresponding trigger operator to calculate the target signal in each of the received CAN bus messages; The trigger calculation feedback layer generates trigger information entries in the database for each CAN bus message whose calculation results satisfy the corresponding trigger conditions; The trigger calculation backhaul layer sequentially extracts trigger information entries for CAN bus messages that have not been returned, and retrieves the corresponding CAN bus message from the hard disk based on the extracted trigger information entries; The trigger calculation backhaul layer will send the found CAN bus message back to the vehicle-cloud communication layer; The vehicle-to-cloud communication layer uploads the returned CAN bus messages to the cloud.

2. The method according to claim 1, characterized in that, After sending the selected CAN bus messages to the trigger calculation return layer and storing them on the hard disk, the process further includes: The CAN data entry node of the acquisition layer sends the basic data of each of the selected CAN bus messages to the full data information database management node in the trigger calculation return layer; wherein, the basic data includes at least message attribute information and storage path information; The full data information database management node generates data information entries for the CAN bus message in the database using time as the index and the basic data of the CAN bus message as the entries.

3. The method according to claim 2, characterized in that, The trigger calculation return layer sequentially extracts trigger information entries for CAN bus messages that have not been returned, and retrieves the corresponding CAN bus message from the hard disk based on the extracted trigger information entries, including: The backhaul service node in the trigger calculation backhaul layer periodically calls the trigger information database management node in the trigger calculation backhaul layer to extract the trigger information entries of the CAN bus messages that have not been backhauled in sequence. The backhaul service node calls the full data information database management node to find the corresponding data information entry based on the information of the extracted trigger information entry; The backhaul service node retrieves the corresponding CAN bus message from the hard drive based on the found data information entries.

4. The method according to claim 2, characterized in that, Also includes: The full-database management node identifies data information entries whose storage time has reached a preset time. The corresponding CAN bus message is found based on the determined data information entries; The found CAN bus messages are compressed and saved, and the original CAN bus messages are deleted. The data information entries of the compressed CAN bus message are updated using its storage path.

5. The method according to claim 1, characterized in that, The trigger calculation and feedback layer generates trigger information entries in the database for each CAN bus message whose calculation results satisfy the corresponding trigger conditions, including: The operator trigger management node in the trigger calculation backhaul layer determines whether any one of the calculation results of each CAN bus message satisfies the corresponding trigger condition. When the operator trigger management node determines that any one of the calculation results of the CAN bus message satisfies the corresponding trigger condition, it sends the trigger information of the CAN bus message to the trigger information library management node in the trigger calculation backhaul layer; wherein, the trigger information includes operator trigger information, the target signal, the calculation result, and the message information to be backhauled; The trigger information database management node uses the trigger information of the CAN bus message to generate trigger information entries for the CAN bus message in the database.

6. The method according to claim 1, characterized in that, Also includes: The trigger information database management node in the trigger calculation backhaul layer periodically deletes the marked trigger information entries; wherein, after extracting the trigger information entries, the trigger information database management node marks the extracted trigger information entries.

7. The method according to claim 1, characterized in that, Also includes: The acquisition layer retrieves the configuration file sent or placed by the user through the cloud from the vehicle-cloud communication layer; wherein, the configuration file includes the trigger operator, the target signal corresponding to the trigger operator, and the trigger condition; the target signal corresponding to the trigger operator is the signal required for its calculation.

8. A bus data return system, characterized in that, include: The data acquisition layer, the trigger calculation and feedback layer, and the vehicle-to-cloud communication layer; The acquisition layer is used to capture each CAN bus message generated by the vehicle in real time, and to filter out the CAN bus messages containing a pre-configured target signal from each CAN bus message, and send the filtered CAN bus messages to the trigger calculation return layer and store them in the hard disk; wherein, the target signal is the signal required for the configured trigger operator calculation; The trigger calculation and feedback layer is used to calculate the target signal in each of the received CAN bus messages using the corresponding trigger operators, generate trigger information entries for each CAN bus message whose calculation results satisfy the corresponding trigger conditions in the database, extract trigger information entries for CAN bus messages that have not been fed back, find the corresponding CAN bus message from the hard disk according to the extracted trigger information entries, and feed the found CAN bus message back to the vehicle-cloud communication layer. The vehicle-to-cloud communication layer is used to upload the returned CAN bus messages to the cloud.

9. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor is used to execute the program, which, when executed, is specifically used to implement the bus data return method as described in any one of claims 1 to 7.

10. A computer storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, is used to implement the bus data return method as described in any one of claims 1 to 7.

Images