Log processing method, vehicle control system, vehicle and computer program product

Abstract

The invention provides a log processing method, a vehicle control system, a vehicle and a computer program product, and the method comprises the steps: responding to a received first request that a log reporting event is triggered, and according to at least one of log identification information, a trigger event and a trigger source associated with the log reporting event, determining a first request that the log reporting event is triggered; determining a target domain controller to which the to-be-uploaded first target log belongs from a plurality of domain controllers of the target vehicle; wherein logs respectively generated by the plurality of domain controllers are stored in storage spaces respectively associated with the plurality of domain controllers; distributing a second request to the target domain controller, wherein the second request is used for indicating the target domain controller to upload the first target log to a log cloud platform; and reporting the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

Description

Technical Field

[0001] The present disclosure relates to the field of automobile technology, and in particular to a log processing method, a vehicle control system, a vehicle, and a computer program product. Background Art

[0002] With the development of the automobile industry, the collection and processing of various vehicle data has become increasingly important. These data include the vehicle's operating status, driving environment, driving habits, etc., which are of great significance to the maintenance, optimization and safety of the vehicle. However, current automobile manufacturers are facing problems in log data management, mainly because the collection, storage, transmission and processing of log data are inefficient and cannot meet the needs of the modern automobile industry. Therefore, a new vehicle log upload solution is needed to solve these problems. Summary of the invention

[0003] The embodiments of the present disclosure at least provide a log processing method, a vehicle control system, a vehicle, and a computer program product.

[0004] In a first aspect, an embodiment of the present disclosure provides a log processing method, which is applied to a first domain controller among multiple domain controllers in a vehicle management system; the log processing method includes:

[0005] In response to receiving a first request generated by a log reporting event being triggered, determining a target domain controller to which a first target log to be uploaded belongs from multiple domain controllers of the target vehicle according to at least one of log identification information associated with the log reporting event, a triggering event, and a triggering source; wherein the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively;

[0006] Distributing a second request to the target domain controller, the second request being used to instruct the target domain controller to upload the first target log to the log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request;

[0007] And, reporting the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

[0008] In an optional implementation manner, before distributing the second request to the target domain controller, the method further includes:

[0009] generating, according to at least part of the information carried in the first request and the target domain controller, a task to be executed for sending the second request to the target domain controller;

[0010] The tasks to be executed are stored in the target queue and the tasks to be executed are persisted;

[0011] The distributing the second request to the target domain controller comprises:

[0012] Based on the task to be executed, generate the second request, and send the second request to the target domain controller;

[0013] In the case where distribution of the second request to any target domain controller fails, the second request is periodically redistributed to the any target domain controller.

[0014] In an optional implementation manner, the method further includes:

[0015] When the second request is successfully distributed to the target domain controller, and / or when the target domain controller successfully uploads the first target log to the log cloud platform according to the second request, the to-be-executed task corresponding to the successfully sent second request is deleted from the target queue.

[0016] In an optional implementation, the method further includes: after a preset period of time, if there is a target domain controller that fails to send the second request, reporting identification information of the target domain controller that fails to send the second request to the log cloud platform.

[0017] In a second aspect, an embodiment of the present disclosure provides a log processing method, which is applied to a second domain controller among multiple domain controllers of a vehicle; the log processing method includes:

[0018] In response to receiving a second request sent by a first domain controller among the multiple domain controllers, determining a first target log to be sent from the logs generated by the second domain controller according to the second request; the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively;

[0019] The first target log is uploaded to the log cloud platform; the second request and the first target log uploaded to the log cloud platform both carry a request identifier associated with the second request; the request identifier is used by the log cloud platform to establish an association between the first target log and the log reporting event reported by the first domain controller to the log cloud platform.

[0020] In an optional implementation manner, uploading the first target log to the log cloud platform includes:

[0021] Uploading the first target log to a cloud warehouse associated with the log cloud platform;

[0022] The method further includes: when the first target log is successfully sent to the log cloud platform, reporting to the log cloud platform a result mapping relationship between a log list of the first target log and the first target log uploaded to the cloud warehouse.

[0023] In an optional implementation, the method further includes:

[0024] In response to receiving a log list pull request from the log cloud platform, determining candidate logs from the logs generated by the second domain controller, and sending the log list of the candidate logs to the log cloud platform;

[0025] In response to receiving a third request generated by the log cloud platform according to the log list, determining a second target log from the candidate logs according to the log identification information of the candidate log carried in the third request;

[0026] Upload the second target log to the log cloud platform.

[0027] In an optional implementation manner, the method further includes:

[0028] In response to receiving a fourth request sent by a health monitor deployed in the same domain controller, determining, from logs corresponding to the same domain controller, a third target log associated with a fault that triggers the fourth request;

[0029] Upload the third target log to the log cloud platform.

[0030] In a fourth aspect, the embodiment of the present disclosure also provides another log processing method, which is applied to the log cloud platform; the log processing method includes:

[0031] Receiving a log reporting event sent by a first domain controller among multiple domain controllers of a target vehicle and a request identifier associated with the log reporting event; and

[0032] receiving a target log associated with the log reporting event and reported by a second domain controller among the multiple domain controllers; the target log carries the request identifier;

[0033] Based on the request identifier reported by the first domain controller and the request identifier carried in the target log reported by the second domain controller, an association relationship between the log reporting event and the target log is established.

[0034] In a fourth aspect, an embodiment of the present disclosure further provides a vehicle control system, comprising: a plurality of domain controllers; a first domain controller among the plurality of domain controllers is deployed with a log management service; a second domain controller among the plurality of domain controllers is deployed with a remote log service; logs generated by the plurality of domain controllers are stored in storage spaces associated with the plurality of domain controllers;

[0035] The log management service is used to, in response to receiving a first request generated by a log reporting event being triggered, determine, from multiple domain controllers of the target vehicle, a target domain controller to which a first target log to be uploaded belongs, according to at least one of log identification information associated with the log reporting event, a triggering event, and a triggering source; distribute a second request to the target domain controller, the second request being used to instruct the target domain controller to upload the first target log to a log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request; and report the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

[0036] The remote log service is configured to, in response to receiving a second request sent by the first domain controller, determine, according to the second request, a first target log to be sent from the log generated by the second domain controller;

[0037] The first target log is uploaded to a cloud warehouse associated with the log cloud platform.

[0038] In a fifth aspect, an embodiment of the present disclosure further provides a vehicle, comprising a vehicle control system as described in the fourth aspect.

[0039] In a sixth aspect, an optional implementation of the present disclosure further provides a computer program product, which carries a program code, and the requests included in the program code can be used to execute the steps of the log processing method as described in the first aspect, or any item of the first aspect, or execute the steps of the log processing method as described in the second aspect, or any item of the second aspect, or execute the steps of the log processing method as described in the third aspect.

[0040] In the log processing method provided by the embodiment of the present disclosure:

[0041] 1: Support multiple trigger sources and trigger methods to trigger log upload, providing more abundant upload methods for vehicle log upload to meet the use in different conditions.

[0042] 2: During the log upload process, the request identifier is used to establish the association between the log reporting event and the log to be uploaded. The triggering event and the uploaded log file are bound through the request identifier to achieve a closed loop of the log upload process, thereby monitoring the log upload process to reduce data mistransmission and loss during the log upload process.

[0043] 3: The logs generated by the car are stored in the storage space associated with each domain controller that generates the log. When uploading the logs, each domain controller controls the uploading of its own log. Compared with the unified uploading of the entire vehicle log data, multiple domain controllers can achieve synchronous log uploading, thereby improving the efficiency of log uploading.

[0044] 4: During the log upload process, the Log Master persists the log upload events. Even if the vehicle control system loses power or the network is interrupted, the log upload can continue after the vehicle control system is restarted or the network is reconnected, thus maintaining the stability of the log upload.

[0045] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0047] Figure 1 A schematic diagram showing the structure of a vehicle control system provided by some embodiments of the present disclosure is shown;

[0048] Figure 2 A schematic diagram showing a specific example of uploading logs by using a vehicle control system provided by some embodiments of the present disclosure;

[0049] Figure 3 A flow chart of a log processing method provided by some embodiments of the present disclosure is shown;

[0050] Figure 4 A flowchart of another log processing method provided by some embodiments of the present disclosure is shown;

[0051] Figure 5A flowchart of another log processing method provided by some embodiments of the present disclosure is shown; DETAILED DESCRIPTION

[0052] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the present disclosure claimed for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0053] The vehicle log of a car is usually stored in a storage space associated with the vehicle control system. When an event is triggered to upload the log to the log cloud platform, the vehicle control system establishes a connection with the cloud platform and uploads the log to the log cloud platform. However, since the data volume of the vehicle log is usually large and the connection with the log cloud platform can only be established when the vehicle is powered on, it usually takes a long time to complete the log upload to ensure that the vehicle control system of the vehicle is powered on. If the vehicle control system is turned off during the log upload process, the log upload will be interrupted. Therefore, while it is difficult to ensure the upload efficiency of the vehicle log data, there is also a risk of mistransmission and loss of log data.

[0054] Based on the above research, the present disclosure provides a log processing method. When receiving the first request generated by the triggering of the log reporting event, the target domain controller to which the first target log belongs is determined from multiple domain controllers of the target vehicle according to the log identification information associated with the log reporting event, the triggering event, and at least one of the triggering sources, and then a second request is sent to the target domain controller. In the second request, a request identifier associated with the second request is carried. At the same time, the request identifier and the log reporting event are also reported to the log cloud platform. After receiving the second request, the target control domain controller uploads the first target log to the log cloud platform, and the first target log it uploads will carry a request identifier; after receiving the first target log uploaded by the target domain controller, the log cloud platform uses the request identifier carried in the first target log and the request identifier reported by the vehicle control system to establish an association between the log reporting event and the first target log, and then uses the association to monitor the log uploading process to reduce data mistransmission during the log uploading process; at the same time, the logs generated by the car are stored in the storage space associated with each domain controller that generates the log. When uploading the log, each domain controller controls the uploading of its own log. Compared with the unified uploading of the entire vehicle log data, multiple domain controllers can realize synchronous log uploading, thereby improving the efficiency of log uploading.

[0055] The defects existing in the above solutions are the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above problems and the solutions proposed by the present disclosure for the above problems below should be the contributions made by the inventor to the present disclosure during the disclosure process.

[0056] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0057] To facilitate understanding of this embodiment, a vehicle control system disclosed in the embodiment of the present disclosure is first introduced in detail.

[0058] See also Figure 1 As shown, it is a schematic diagram of a vehicle control system provided in an embodiment of the present disclosure, comprising: a plurality of domain controllers; wherein a log management service is deployed in the first domain controller among the plurality of domain controllers, and a remote log service is deployed in each of the plurality of domain controllers.

[0059] Specifically, the domain controller in the vehicle control system is, for example, a controller of multiple functional domains determined by functionally dividing the vehicle control system deployed in the vehicle control system. Different domain controllers are used to implement relevant functions of the vehicle under the corresponding functional domain, which may include, for example, at least one of the following: cockpit domain controller (CDC), body gateway module (BGM), automated-driving control unit (ACU), telematics & connectivity antenna module (TCAM), etc. There may be other domain controllers, which are not limited in the embodiments of the present disclosure.

[0060] Among them, CDC is used to realize various functions in the vehicle cabin, such as air conditioning, ambient light, ceiling light, etc. BGM is used to realize the relevant functions of the vehicle gateway, ACU is used to realize various driving-related functions, and the network connection module is used to realize the relevant functions of the vehicle network connection.

[0061] The first domain controller among the multiple domain controllers can be, for example, any one of the above-mentioned domain controllers. In addition, in the disclosed embodiment, log upload can be triggered by a cloud platform trigger. Therefore, for the convenience of data transmission, a domain controller related to the network can be used as the first domain controller, such as BGM. A log management service (Log master) is deployed in the first domain controller. The log management service is mainly used to convert, send, manage, and store messages for the entire log upload trigger process.

[0062] In each domain controller, a remote log service is also deployed, which is responsible for the association of log reporting events of log upload and log files to be uploaded, uploading of log files, and reporting of log upload results.

[0063] Here, the domain controllers deploying the remote log service include the first domain controller described above, which is responsible for uploading the log files generated by the first domain controller itself.

[0064] See also Figure 2 As shown, the embodiment of the present disclosure provides an example of a specific architecture of a vehicle control system, in which the domain controller includes: BGM, TCAM, CDC, and ACU. Among them, the Log master is deployed in the BGM, and the BGM, TCAM, CDC, and ACU are respectively deployed with remote log services.

[0065] The specific functions of the log management service (Log master) and the remote log service (Remote log) are described in detail below.

[0066] A: For the log management service Log master, it is used to receive a first request generated by a log reporting event being triggered, and determine a target domain controller to which a first target log to be uploaded belongs from multiple domain controllers of the target vehicle according to log identification information associated with the log reporting event, a triggering event, and at least one of a triggering source; wherein the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively;

[0067] Distributing a second request to the target domain controller so that the target domain controller uploads the corresponding first target log to the log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request;

[0068] And, reporting the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

[0069] In a specific implementation, the log reporting event may be triggered by any of the following triggering methods:

[0070] a1: Intelligent driving trigger.

[0071] In specific implementation, the ACU will record the relevant information generated during the vehicle driving (autonomous driving or manual driving) in the form of a log. In certain specific situations, such as vehicle collision, system failure during driving, abnormal driving data, etc., the ACU can actively trigger a log reporting event.

[0072] a2: button trigger.

[0073] In a specific implementation, for example, a button for triggering log upload may be displayed on the display screen of the vehicle control system. The button may be displayed on the display screen in certain specific circumstances, for example, after a vehicle collision occurs, a button may be displayed on the display screen, and the button is used by the user to choose whether to actively trigger the upload of relevant logs within a certain period of time before and after the accident.

[0074] In addition, a specific log upload control page can also be set in the vehicle control system, and the button can be set in the log upload control page. The user can choose to display the specific log upload control page on the display screen through the input device of the vehicle control system, and trigger the upload log by displaying the button in the log upload control page.

[0075] Here, the log upload control page can also display a control for filtering the logs to be uploaded. The control can, for example, include multiple optional items, each optional item corresponding to a filtering condition for the logs to be uploaded, such as the source of the log (which domain controller it comes from), the type of log, the time when the log is generated, the reason for the log to be generated (for example, the log is generated due to an erroneous operation, the log is generated due to an accident, etc.), etc., which can be set according to actual needs.

[0076] When the button is triggered, a log reporting event is triggered.

[0077] a3: Voice trigger.

[0078] In a specific implementation, for example, a voice input interface may be provided in a vehicle control system; the vehicle control system may obtain a voice request input by a user through the voice input interface, and parse the voice request to analyze the operation content specifically indicated by the voice request.

[0079] When the operation content indicates uploading a log, it is considered that the log reporting event is triggered.

[0080] a4: Gesture trigger.

[0081] In a specific implementation, the gesture trigger may include, for example: a specific operation gesture on the display screen, such as sliding the screen in a specific direction; or, it may also include certain specific actions performed by the user, such as obtaining the actions performed by the user in the vehicle through the vehicle's visual perception. When the user is detected to perform the action, the log reporting event is triggered.

[0082] a5: Triggered by a specific event.

[0083] In a specific implementation, certain specific events may be set; when a specific event occurs, a log reporting event is triggered. The specific event may include, for example, a failure to upgrade a vehicle control system deployed in the vehicle control system.

[0084] a6: Cloud trigger.

[0085] The log cloud platform, for example, is a cloud platform that has access to the vehicle logs. The log cloud platform can automatically trigger log reporting events according to certain rules. For example, the vehicle logs are uploaded periodically. When the preset upload time arrives, the log reporting event is triggered, or the log reporting event can be triggered when certain specific conditions of the vehicle are detected.

[0086] The vehicle control system can provide an interface for triggering a log reporting event; when the log reporting event is triggered, the trigger source generates a first request for reporting the log, and sends the first request to the Log master through the interface. In the first request, the trigger source information, the trigger event, the request identifier corresponding to the log reporting event, and at least one of the upload parameters can be carried. Among them, the trigger source can include, for example: any domain controller among multiple domain controllers; the trigger event can correspond to a specific trigger method, which includes, for example: voice trigger, button trigger, system upgrade failure trigger, cloud trigger, gesture trigger, smart driving trigger, etc.; the upload parameter is used to determine the conditions corresponding to the first target log to be uploaded, that is, the log identification information.

[0087] After receiving the first request for reporting a log, the log master parses the first request to obtain relevant information carried in the first request, and determines the target domain controller to which the first target log belongs from multiple domain controllers of the target vehicle based on at least one of the log identification information associated with the log reporting event, the trigger event, and the trigger source in the above relevant information.

[0088] Here, the log identification information associated with the log reporting event is, for example, carried in the first request, and is used to specifically indicate the relevant information of which logs to upload. For example, it may include: the generation time of the log, the type of log, the source of the log, etc. These log identification information are carried in the voice request issued by the user when triggered by voice. For example, if the user issues a voice: "Save the logs of the last three days", a period of 3 days is determined from the moment of receiving the first request as the end time, and the start and end time of the period are carried as log identification information, which is carried in the relevant parameters of the first request and sent to the Log master. For another example, the user triggers the log reporting event through a button, and when the log reporting event is triggered, the conditions of the log to be uploaded are selected from a specific log upload control page. At this time, these conditions can be carried in the first request as log identification information and sent to the Log master. After receiving the first request, the Logmaster determines the target domain controller to which the first target log to be uploaded belongs from multiple domain controllers according to the log identification information carried in the first request.

[0089] The trigger source may include, for example, any domain controller among multiple domain controllers, or a log cloud platform. Figure 2 In the corresponding example, the trigger source may include, for example, any domain controller of CDC, ACU, BGM, and TCAM. Corresponding log upload conditions can be set for different trigger sources, and the log upload conditions are used to describe which domain controllers' logs are to be uploaded to the log cloud platform when the log reporting event is triggered by a certain trigger source. In the case where the first request corresponding to the log reporting event carries a trigger source, the target domain controller to which the first target log to be uploaded belongs can be determined from multiple domain controllers according to the log upload conditions corresponding to the trigger source.

[0090] A trigger event, for example, may correspond to a specific triggering method, such as voice triggering, button triggering, specific event triggering, etc., wherein the triggering event corresponding to the voice triggering includes receiving an input voice request; the triggering event corresponding to the button triggering includes a specific button for uploading logs being triggered; the triggering time corresponding to the specific event triggering is the occurrence of a specific event. For different triggering events, log upload conditions corresponding to each triggering event may also be set. The log upload conditions corresponding to the triggering event are used to describe which domain controllers' logs are to be uploaded to the log cloud platform when the log reporting event corresponds to the corresponding triggering method. In the case where the first request corresponding to the log reporting event carries a triggering event, the target domain controller to which the first target log to be uploaded belongs may be determined from multiple domain controllers according to the log upload conditions corresponding to the triggering event.

[0091] When determining the target domain controller based on any of the above-mentioned log identification information, trigger events and trigger sources, the domain controllers determined based on different factors may be different; usually, the union of domain controllers determined by multiple factors can be used as the target domain controller.

[0092] The Log master stores a list of remote log services. The list can add new remote log services or reduce certain remote log services according to the application. When determining the target domain controller, the Log master uses, for example, the identifiers of each remote log service in the remote log service list to determine the target remote log service associated with the target domain controller. The domain controller that deploys the target remote log service is the target domain controller.

[0093] After the Log Master determines the target domain controller, it distributes the second request to the target domain controller.

[0094] The second request carries a request identifier request_id, which may be carried in the first request when the interface for receiving the first request corresponding to the log reporting event sends the first request to the Log master. The Logmaster obtains the request_id by parsing the first request, and carries it in the second request when repackaging and generating the second request.

[0095] In addition, request_id can also be assigned by the Log master for the request after receiving the first request, and carried in the second request when repackaging and generating the second request. After receiving the second request, the target domain controller will upload the first target log to the log cloud platform according to the instructions of the second request, and when uploading the first target log, it will send the request_id to the log cloud platform as part of the uploaded information.

[0096] In addition, the second request may also carry other information, such as at least one of a trigger source, a trigger event, and identification information of the first target log.

[0097] After receiving the log report event, the log master will also report the request identifier and the log report event to the log cloud platform. After receiving the first target log uploaded by the target domain controller, the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log report event through the request_id.

[0098] Before distributing the second request to the target domain controller, the log master is further configured to:

[0099] generating, according to at least part of the information carried in the first request and the target domain controller, a task to be executed for sending the second request to the target domain controller;

[0100] The tasks to be executed are stored in the target queue, and the tasks to be executed are persisted.

[0101] In a specific implementation, the purpose of persisting the task to be executed is to enable the first target log to be reported after the vehicle control system is powered on again when the vehicle control system loses power and the first target log has not been fully uploaded to the log cloud platform, so as to maintain the continuity of the log reporting event.

[0102] Log master persists pending tasks, which is actually persisting log reporting events. In this process, Logmaster parses the first request, obtains various information carried in the first request, and determines the target domain controller. Then, Logmaster uses at least part of the information carried in the first request and the target domain controller to generate a pending task for sending a second request to the target domain controller. The pending tasks can be one or more. After the pending tasks are stored in the target queue, the pending tasks in the target queue are persisted, which means that the persistent processing of log reporting events is realized.

[0103] When distributing the second request to the target domain controller, for example, the second request may be generated based on the task to be executed, and the second request may be sent to the target domain controller;

[0104] In the case where distribution of the second request to any target domain controller fails, the second request is periodically redistributed to the any target domain controller.

[0105] When generating a second request based on the tasks to be executed, for example, each task to be executed can be read from the target list in a first-in-first-out order; then, according to the data format of the second request, the various information corresponding to the tasks to be requested are added to the various fields of the second request to form a second request, and then the second request is sent to the target domain controller.

[0106] In addition, Log master is also used to delete the to-be-executed task corresponding to the successfully sent second request from the target queue when the second request is successfully distributed to the target domain controller and / or when the target domain controller successfully uploads the first target log to the log cloud platform according to the second request.

[0107] Here, after receiving the second request, the target domain controller may send a feedback to the Log master indicating that the second request has been delivered.

[0108] In one embodiment, after receiving the second request, the target domain controller can persist the log upload task generated according to the second request locally in the target domain controller, so as to enable the corresponding log upload task to continue to be executed after the vehicle control system is powered off and restarted. In this case, after receiving the feedback that the second request sent by the target domain controller has been delivered, the Log master deletes the corresponding task from the target queue.

[0109] In another embodiment, after receiving the second request, the target domain controller will not persist the log upload task; after the vehicle control system is powered off and restarted, the Log master needs to resend the second request to the target domain controller. In this case, after the target domain controller successfully uploads the first target log to the log cloud platform, the target domain controller or the log cloud platform can send feedback on the successful log upload to the Log master. At this time, after receiving the feedback on the successful upload of the first target log sent by the target domain controller or the log cloud platform, the Log master deletes the corresponding task from the target queue.

[0110] In another embodiment, after receiving the second request, the target domain controller will persist the log upload task; after the vehicle control system is powered off and restarted, the Log master does not need to send the second request to the target domain controller again, but the target domain controller continues to upload the log according to the persistent log upload task. In this case, after the target domain controller successfully uploads the first target log to the log cloud platform, the target domain controller or the log cloud platform can send feedback on the successful log upload to the Log master; when the Log master receives the feedback sent by the target domain controller that the second request has been received, and at the same time, receives the feedback sent by the target domain controller or the log cloud platform that the first target log has been successfully uploaded, the corresponding task will be deleted from the target queue. In this way, the integrity of the log upload is further guaranteed through the mutual confirmation of the log cloud platform, the target domain server, and the Log master.

[0111] In addition, the Log master is also used to: after a preset period of time, if there is a target domain controller that fails to send the second request, report the identification information of the target domain controller that fails to send the second request to the log cloud platform. In this way, the log cloud platform can monitor the upload process of the first target log.

[0112] B: for remote log remote log, in response to receiving a second request sent by a first domain controller among the multiple domain controllers, determine a first target log to be sent from a log generated by the second domain controller according to the second request; the second domain controller includes any domain controller among the multiple domain controllers;

[0113] The first target log is uploaded to a cloud warehouse associated with the log cloud platform.

[0114] Specifically, after receiving the second instruction sent by the Log master, the remote log will parse the second instruction and obtain various information carried in the second instruction, such as at least one of the trigger source, the trigger event, and the identification information of the first target log. Based on this information, the first target log to be uploaded to the log cloud platform can be determined from the log generated by the second domain controller where the remote log is located. After that, the first target log can be uploaded to the log cloud platform by establishing a network link with the log cloud platform, such as an HTTP link.

[0115] The log cloud platform usually includes: a cloud platform and a cloud warehouse; the cloud platform is used to execute log upload triggering, log upload process monitoring, uploaded log management and other control and interaction-related tasks; the cloud warehouse is used to store logs uploaded by vehicles.

[0116] Furthermore, when uploading the first target log to the log cloud platform, remote log is used to: upload the first target log to the cloud warehouse associated with the log cloud platform.

[0117] Remote log is also used to: when the first target log is successfully sent to the log cloud platform, report to the log cloud platform the result mapping relationship between the log list of the first target log and the first target log uploaded to the cloud warehouse.

[0118] Here, the result mapping relationship, for example, can be used to describe the relationship between the first target log and the storage location in the cloud warehouse.

[0119] In addition to being able to trigger log uploads to the Log master, the Log Cloud Platform can also trigger log uploads directly to the remote log.

[0120] In this case, the remote log is further used to: in response to receiving a log list pull request from the log cloud platform, determine candidate logs from the logs generated by the second domain controller, and send the log list of the candidate logs to the log cloud platform;

[0121] In response to receiving a third request generated by the log cloud platform according to the log list, determining a second target log from the candidate logs according to the log identification information of the candidate log carried in the third request;

[0122] Upload the second target log to the log cloud platform.

[0123] Here, the user can actively call certain logs in a specific domain controller in the vehicle through the log cloud platform. In this case, the user can trigger the log cloud platform to send a log list pull request to any domain controller among multiple domain controllers through the interactive interface provided by the log cloud platform. In the log list pull request, the identifier of the specific domain controller to which the second target log to be uploaded belongs is carried.

[0124] Here, the vehicle control system will provide an interface for establishing a remote connection with the vehicle control system; the log cloud platform will send the log list pull request to the vehicle control system through the interface, and the interface will transmit the log list pull request to the remote log deployed in the specific domain controller to which the second target log belongs based on the identifier of the domain controller carried in the log list pull request.

[0125] Afterwards, after receiving the log list pull request, remote log determines candidate logs from the logs generated by the second domain controller according to certain rules, and sends the log list of the candidate logs to the log cloud platform.

[0126] Here, when determining the candidate logs, for example, the candidate logs may be screened from the logs according to the information carried in the log list pull request, such as the generation time of the candidate logs, the type of the candidate logs, the fields of the candidate logs, etc. Alternatively, the candidate logs may be determined according to certain triggering rules, such as after receiving the log list pull request, all currently saved logs are determined as candidate logs, or logs that have not been reported to the log cloud platform are determined as candidate logs.

[0127] After the candidate logs are determined, a log list of the candidate logs is generated according to the relevant information of the candidate logs, such as log identifiers, attributes, etc., and the log list is sent to the log cloud platform.

[0128] After receiving the log list sent by the remote log, the log cloud platform can display the log list to the user. The user can filter the candidate logs in the log list to determine the second target log to be uploaded, generate a third request based on the log identification information of the second target log, and send the third request to the remote log in the second domain controller.

[0129] After receiving the third request, remote log determines the second target log from the candidate logs according to the log identification information carried in the third request, and uploads the second target log to the log cloud platform.

[0130] In another embodiment of the present disclosure, a health monitor HealthMoniter may also be deployed in each domain controller, for example.

[0131] The Health Monitor is used to monitor the running status of the domain controller; and when it is detected that an Error occurs in the running status of the domain controller, a fourth request is sent to the remote log deployed in the corresponding domain controller.

[0132] In response to receiving a fourth request sent by a health monitor deployed in the same domain controller, remote log determines a third target log associated with the fault that triggers the fourth request from the log corresponding to the same domain controller; and uploads the third target log to the log cloud platform.

[0133] In this way, the health status of each domain controller is monitored by the Health Monitor deployed in each domain controller. When the health status indicates that the operating status of the domain controller has failed, the remote log is driven to actively report the third target log related to the failure to the log cloud platform, so that the log cloud platform can monitor the relevant operating status of the vehicle control system more timely, so as to facilitate timely handling of the failure or improvement of the vehicle control system, improve the stability of the vehicle controller system, and improve the safety of the vehicle during driving.

[0134] In an embodiment of the present disclosure, a log cloud platform is further provided, which is specifically used to: receive a log reporting event sent by a first domain controller among multiple domain controllers of a target vehicle and a request identifier associated with the log reporting event; and

[0135] receiving a target log associated with the log reporting event and reported by a second domain controller among the multiple domain controllers; the target log carries the request identifier;

[0136] Based on the request identifier reported by the first domain controller and the request identifier carried in the target log reported by the second domain controller, an association relationship between the log reporting event and the target log is established.

[0137] See also Figure 2 As shown, the embodiment of the present disclosure provides a specific example of a vehicle control system, in which the vehicle control system includes four domain controllers: BGM, CDC, TCAM, and ACU. Among them, the BGM is deployed with a log management service Log master; the BGM, CDC, TCAM, and ACU are respectively deployed with a remote log service Remote Log.

[0138] The voice trigger and button trigger functions for log upload are integrated in CDC; the intelligent driving trigger function is integrated in ACU; the cloud trigger function is integrated in the log platform; BGM and TCAM are respectively deployed with health monitors.

[0139] like Figure 2 As shown in the corresponding step ① in FIG, after the log reporting event is triggered by any of the triggering methods such as voice triggering, button triggering, cloud triggering, or intelligent driving triggering, the Log master receives the first request sent by the trigger source.

[0140] After the Log Master determines the target domain controller based on the first request, Figure 2 In step ②, a second instruction is sent to deploy Remote Log in the target domain controller. Among them, any one of BGM, CDC, TCAM, and ACU can be used as the target domain controller.

[0141] After receiving the second instruction, the target domain controller deploys Remote Log. Figure 2 As shown in step ③ in the figure, upload the first target log to the cloud warehouse. Figure 2 In step ④, the result mapping information is fed back to the log cloud platform.

[0142] Log cloud platform Figure 2 As shown in 5, the log directory upload control is performed on any one of BGM, CDC, TCAM, and ACU. The process includes the log cloud platform sending a log list pull request to any one of BGM, CDC, TCAM, and ACU. After receiving the log list pull request, the Remote Log of any one of BGM, CDC, TCAM, and ACU reports the log list of candidate logs to the cloud log platform, that is, the directory upload progress. Then the log cloud platform sends a third request to the Remote Log of the corresponding domain controller based on the log list of candidate logs.

[0143] After receiving the third request, Remote Log Figure 2 In step ③, the corresponding second target log is uploaded to the cloud warehouse.

[0144] When any of the health monitors deployed by BGM and TCAM detects that an error has occurred in the corresponding domain controller, it triggers the error log upload, that is, sends a fourth request to the Remote Log deployed in the corresponding domain controller. After receiving the fourth request, the Remote Log Figure 2 In step ③, the corresponding third target log is uploaded to the cloud warehouse.

[0145] The architecture of the above vehicle control system has the following characteristics:

[0146] 1: Support multiple trigger sources and trigger methods to trigger log upload, providing more abundant upload methods for vehicle log upload to meet the use in different conditions.

[0147] 2: During the log upload process, the request identifier is used to establish the association between the log reporting event and the log to be uploaded. The triggering event and the uploaded log file are bound through the request identifier to achieve a closed loop of the log upload process, thereby monitoring the log upload process to reduce data mistransmission and loss during the log upload process.

[0148] 3: The logs generated by the car are stored in the storage space associated with each domain controller that generates the log. When uploading the logs, each domain controller controls the uploading of its own log. Compared with the unified uploading of the entire vehicle log data, multiple domain controllers can achieve synchronous log uploading, thereby improving the efficiency of log uploading.

[0149] 4: During the log upload process, the Log Master persists the log upload events. Even if the vehicle control system loses power or the network is interrupted, the log upload can continue after the vehicle control system is restarted or the network is reconnected, thus maintaining the stability of the log upload.

[0150] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0151] Based on the same inventive concept, a log processing method corresponding to the vehicle management system is also provided in the embodiment of the present disclosure. Since the principle of solving the problem by the log processing method in the embodiment of the present disclosure is similar to the above-mentioned vehicle management system in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0152] Reference Figure 3 As shown, it is a flow chart of a log processing method provided by an embodiment of the present disclosure, and the log processing method is applied to a first domain controller among multiple domain controllers in a vehicle management system; the log processing method includes:

[0153] S301: In response to receiving a first request generated by a log reporting event being triggered, determine a target domain controller to which a first target log to be uploaded belongs from multiple domain controllers of the target vehicle according to log identification information associated with the log reporting event, a triggering event, and at least one of a triggering source; wherein the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively;

[0154] S302: Distribute a second request to the target domain controller, where the second request is used to instruct the target domain controller to upload the first target log to the log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request;

[0155] S303: Reporting the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

[0156] In a possible implementation manner, before distributing the second request to the target domain controller, the method further includes:

[0157] generating, according to at least part of the information carried in the first request and the target domain controller, a task to be executed for sending the second request to the target domain controller;

[0158] The tasks to be executed are stored in the target queue and the tasks to be executed are persisted;

[0159] The distributing the second request to the target domain controller comprises:

[0160] Based on the task to be executed, generate the second request, and send the second request to the target domain controller;

[0161] In the case where distribution of the second request to any target domain controller fails, the second request is periodically redistributed to the any target domain controller.

[0162] In a possible implementation manner, the method further includes:

[0163] When the second request is successfully distributed to the target domain controller, and / or when the target domain controller successfully uploads the first target log to the log cloud platform according to the second request, the to-be-executed task corresponding to the successfully sent second request is deleted from the target queue.

[0164] In a possible implementation manner, the method further includes: after a preset period of time, if there is a target domain controller that fails to send the second request, reporting identification information of the target domain controller that fails to send the second request to the log cloud platform.

[0165] Reference Figure 4 As shown, a flow chart of another log processing method provided in an embodiment of the present disclosure is provided, and the log processing method is applied to the second domain controller among multiple domain controllers in a vehicle management system; the log processing method includes:

[0166] S401: In response to receiving a second request sent by a first domain controller among multiple domain controllers, determine, according to the second request, a first target log to be sent from the logs generated by the second domain controller; the second domain controller includes any domain controller among the multiple domain controllers; the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively;

[0167] S402: Upload the first target log to the log cloud platform; the second request and the first target log uploaded to the log cloud platform both carry a request identifier associated with the second request; the request identifier is used by the log cloud platform to establish an association between the first target log and the log reporting event reported by the first domain controller to the log cloud platform.

[0168] In a possible implementation manner, uploading the first target log to the log cloud platform includes:

[0169] Uploading the first target log to a cloud warehouse associated with the log cloud platform;

[0170] The method further includes: when the first target log is successfully sent to the log cloud platform, reporting to the log cloud platform a result mapping relationship between a log list of the first target log and the first target log uploaded to the cloud warehouse.

[0171] In a possible implementation, the following further includes:

[0172] In response to receiving a log list pull request from the log cloud platform, determining candidate logs from the logs generated by the second domain controller, and sending the log list of the candidate logs to the log cloud platform;

[0173] In response to receiving a third request generated by the log cloud platform according to the log list, determining a second target log from the candidate logs according to the log identification information of the candidate log carried in the third request;

[0174] Upload the second target log to the log cloud platform.

[0175] In a possible implementation manner, the method further includes:

[0176] In response to receiving a fourth request sent by a health monitor deployed in the same domain controller, determining, from logs corresponding to the same domain controller, a third target log associated with a fault that triggers the fourth request;

[0177] Upload the third target log to the log cloud platform.

[0178] Reference Figure 5 As shown, a flowchart of another log processing method provided in an embodiment of the present disclosure is provided, and the log processing method is applied to a log cloud platform; the log processing method includes:

[0179] S501: receiving a log reporting event sent by a first domain controller among multiple domain controllers of a target vehicle and a request identifier associated with the log reporting event; and

[0180] S502: Receive a target log associated with the log reporting event and reported by a second domain controller among the multiple domain controllers; the target log carries the request identifier;

[0181] S503: Establishing an association relationship between the log reporting event and the target log based on the request identifier reported by the first domain controller and the request identifier carried in the target log reported by the second domain controller.

[0182] For the specific processing flow of each step in the above-mentioned log processing method, reference may be made to the relevant description in the above-mentioned vehicle control system embodiment, which will not be described in detail here.

[0183] An embodiment of the present disclosure also provides a vehicle, comprising a vehicle control system as described in any embodiment of the present disclosure.

[0184] The embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the log processing method described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0185] The embodiments of the present disclosure also provide a computer program product, which carries a program code. The instructions included in the program code can be used to execute the steps of the log processing method described in the above method embodiment. For details, please refer to the above method embodiment, which will not be repeated here.

[0186] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0187] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0188] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0189] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0190] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several requests for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0191] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A log processing method, characterized in that: Applicable to a first domain controller among multiple domain controllers in a vehicle management system; The log processing method comprises: In response to receiving a first request generated by a log reporting event being triggered, determining a target domain controller to which a first target log to be uploaded belongs from multiple domain controllers of the target vehicle according to at least one of log identification information associated with the log reporting event, a triggering event, and a triggering source; wherein the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively; Distributing a second request to the target domain controller, the second request being used to instruct the target domain controller to upload the first target log to the log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request; And, reporting the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event.

2. The method according to claim 1, characterized in that Before distributing the second request to the target domain controller, the method further includes: generating, according to at least part of the information carried in the first request and the target domain controller, a task to be executed for sending the second request to the target domain controller; The tasks to be executed are stored in the target queue and the tasks to be executed are persisted; The distributing the second request to the target domain controller comprises: Based on the task to be executed, generate the second request, and send the second request to the target domain controller; In the case where distribution of the second request to any target domain controller fails, the second request is periodically redistributed to the any target domain controller.

3. The method according to claim 2, characterized in that The method further comprises: When the second request is successfully distributed to the target domain controller, and / or when the target domain controller successfully uploads the first target log to the log cloud platform according to the second request, the to-be-executed task corresponding to the successfully sent second request is deleted from the target queue.

4. The method according to claim 2, characterized in that: The method further includes: after a preset time period, if there is a target domain controller that fails to send the second request, reporting identification information of the target domain controller that fails to send the second request to the log cloud platform.

5. A log processing method, characterized in that: A second domain controller among a plurality of domain controllers applied to a vehicle; The log processing method comprises: In response to receiving a second request sent by a first domain controller among the multiple domain controllers, determining a first target log to be sent from the logs generated by the second domain controller according to the second request; the logs respectively generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively; The first target log is uploaded to the log cloud platform; the second request and the first target log uploaded to the log cloud platform both carry a request identifier associated with the second request; the request identifier is used by the log cloud platform to establish an association relationship between the first target log and the log reporting event reported by the first domain controller to the log cloud platform.

6. The method according to claim 5, characterized in that The uploading the first target log to the log cloud platform includes: Uploading the first target log to a cloud warehouse associated with the log cloud platform; The method further includes: when the first target log is successfully sent to the log cloud platform, reporting to the log cloud platform a result mapping relationship between a log list of the first target log and the first target log uploaded to the cloud warehouse.

7. The method according to claim 5 or 6, characterized in that: Also includes: In response to receiving a log list pull request from the log cloud platform, determining candidate logs from the logs generated by the second domain controller, and sending the log list of the candidate logs to the log cloud platform; In response to receiving a third request generated by the log cloud platform according to the log list, determining a second target log from the candidate logs according to the log identification information of the candidate log carried in the third request; Upload the second target log to the log cloud platform.

8. The method according to claim 5 or 6, characterized in that: The method further comprises: In response to receiving a fourth request sent by a health monitor deployed in the same domain controller, determining, from logs corresponding to the same domain controller, a third target log associated with a fault that triggers the fourth request; Upload the third target log to the log cloud platform.

9. A log processing method, characterized in that: Applied to the log cloud platform; the log processing method includes: Receiving a log reporting event sent by a first domain controller among multiple domain controllers of a target vehicle and a request identifier associated with the log reporting event; and receiving a target log associated with a log reporting event and reported by a second domain controller among the multiple domain controllers; the target log carries the request identifier; Based on the request identifier reported by the first domain controller and the request identifier carried in the target log reported by the second domain controller, an association relationship between the log reporting event and the target log is established.

10. A vehicle control system comprising: Multiple domain controllers; A log management service is deployed in a first domain controller among the multiple domain controllers; A remote log service is deployed in the second domain controller among the multiple domain controllers; logs generated by the multiple domain controllers are stored in storage spaces associated with the multiple domain controllers respectively; The log management service is used to, in response to receiving a first request generated by a log reporting event being triggered, determine, from multiple domain controllers of the target vehicle, a target domain controller to which a first target log to be uploaded belongs, according to at least one of log identification information associated with the log reporting event, a triggering event, and a triggering source; distribute a second request to the target domain controller, the second request being used to instruct the target domain controller to upload the first target log to a log cloud platform; wherein the second request and the first target log uploaded by the target domain controller to the log cloud platform both carry a request identifier associated with the second request; and report the request identifier and the log reporting event to the log cloud platform, so that the log cloud platform establishes an association relationship between the first target log uploaded by the target domain controller and the log reporting event. The remote log service is configured to, in response to receiving a second request sent by the first domain controller, determine, according to the second request, a first target log to be sent from the log generated by the second domain controller; The first target log is uploaded to a cloud warehouse associated with the log cloud platform.

11. A vehicle, characterized in that: include: The vehicle control system as claimed in claim 10.

12. A computer program product, characterized in that The computer program product carries a program code, and the program code includes instructions that can be used to execute the steps of the log processing method according to any one of claims 1 to 9.

Images