Vehicle control demand processing method, device and system and storage medium

Abstract

The invention discloses a vehicle control demand processing method, device and system and a storage medium, and the method comprises the steps: obtaining title information in a vehicle control demand, and the title information comprises a control target of the vehicle control demand; the title information in the vehicle control demand is matched with a preset rule set to obtain a first rule set matched with the vehicle control demand, the preset rule set is a set of a plurality of pre-stored vehicle control rules, and the first rule set comprises at least part of vehicle control rules in the preset rule set; the vehicle control rule is a control logic for controlling the vehicle; converting the first rule set into an executable file for a vehicle end; and sending the executable file to a target vehicle end corresponding to the vehicle control demand. By adopting the scheme provided by the invention, the development efficiency of the vehicle control rule can be improved, and the development period can be shortened.

Description

Technical Field

[0001] The present application relates to the field of vehicle control technology, and in particular to a vehicle control demand processing method, device, system and storage medium. Background Art

[0002] Vehicle control rules, that is, the rules corresponding to vehicle control functions, such as light control rules, door control rules, etc., are the logic used in the vehicle electronic control system for comprehensive analysis and processing of specific business.

[0003] The relationship between vehicle control requirements, vehicle control rules and vehicle control functions is that vehicle control requirements are requirements for realizing corresponding vehicle control functions, and corresponding vehicle control rules can be written based on these vehicle control requirements. These vehicle control rules usually exist in the form of vehicle control rule codes. After these vehicle control rule codes are published to the corresponding vehicles, the vehicles can realize the corresponding vehicle control functions by executing these vehicle control rule codes.

[0004] In the prior art, during the process of developing vehicle control rules, designers often first propose one or more vehicle control requirements, and developers write corresponding vehicle control rule codes based on these vehicle control requirements, or developers write corresponding code generation instructions based on the vehicle control requirements and then the code generation tool generates the corresponding vehicle control rule codes, and then the vehicle control rule codes are released to the corresponding vehicles. This approach results in low development efficiency and long development cycle of vehicle control functions.

[0005] Therefore, how to provide a method for processing vehicle control requirements to improve the development efficiency of vehicle control rules and shorten the development cycle has become a technical problem that needs to be solved urgently. Summary of the invention

[0006] The present application provides a vehicle control demand processing method, device, system and storage medium to improve the development efficiency of vehicle control rules and shorten the development cycle.

[0007] The present application provides a vehicle control demand processing method, including:

[0008] Acquire title information in the vehicle control requirement, wherein the title information includes a control target of the vehicle control requirement;

[0009] Matching the title information in the vehicle control requirement with a preset rule set to obtain a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rule is a control logic for controlling the vehicle;

[0010] Converting the first rule set into an executable file for the vehicle end;

[0011] The executable file is sent to the target vehicle terminal corresponding to the vehicle control requirement.

[0012] The beneficial effect of the present application is: obtaining the title information in the vehicle control requirements, then matching the title information in the vehicle control requirements with the preset rule set to obtain a first rule set that matches the vehicle control requirements, and then automatically converting the first rule set into an executable file for the vehicle end, and sending the executable file to the target vehicle end corresponding to the vehicle control requirements. Therefore, for different vehicle control requirements, this method can automatically match the corresponding rules with the preset rule set directly based on the received vehicle control requirements, and automatically convert the matched rules into an executable file for the vehicle end, without the need for developers to repeatedly write code based on vehicle control requirements, thereby improving the development efficiency of vehicle control rules and shortening the development cycle.

[0013] In one embodiment, the first rule set is an XML file, and converting the first rule set into an executable file for the vehicle side includes:

[0014] Parsing an XML file of a first rule set matching the vehicle control requirement to convert the XML file into a rule set object, wherein the rule set object is a vehicle control rule code in a preset computer language form;

[0015] Convert the rule set object into an executable file for the vehicle side.

[0016] In one embodiment, when the vehicle control requirement includes multiple title information, obtaining a first rule set matching the vehicle control requirement includes:

[0017] Acquire a plurality of first rule sets matching the vehicle control requirement;

[0018] A knowledge package corresponding to the plurality of first rule sets is constructed, wherein the knowledge package is a vehicle control executable code corresponding to the vehicle control rules of the vehicle control requirements.

[0019] In one embodiment, converting the first rule set into an executable file for the vehicle side includes:

[0020] The knowledge packages corresponding to the multiple first rule sets are converted into executable file packages for the vehicle side, wherein the executable file package includes multiple executable files, and each executable file corresponds to a first rule set.

[0021] In one embodiment, the method further comprises:

[0022] When a triggering event for modifying the vehicle control requirement is detected, displaying the first rule set;

[0023] When a modification operation on the first rule set object is received, obtaining title information corresponding to the modification operation;

[0024] The first rule set is edited according to the title information corresponding to the modification operation to modify the first rule set into a second rule set.

[0025] In one embodiment, displaying the first rule set includes:

[0026] Obtaining the first rule set;

[0027] Serializing the first rule set into JSON format;

[0028] The first rule set converted into the JSON format is rendered on the front end to display the first rule set.

[0029] In one embodiment, sending the executable file to the target vehicle corresponding to the vehicle control requirement includes:

[0030] Extracting the vehicle identification code contained in the vehicle control requirement;

[0031] The executable file is sent to the vehicle end corresponding to the vehicle identification code.

[0032] In one embodiment, the process of creating the preset rule set is as follows:

[0033] Receive the input operation of the SOA signal value interval of each vehicle control object through the conditional judgment statement box;

[0034] The execution instruction frame corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction to assign the value to the DBO signal library through the SOA signal;

[0035] An input operation of an instruction to reject the input request is received by an execution instruction frame corresponding to the condition that the judgment result does not fall within the signal value interval.

[0036] The present application also provides a vehicle control demand processing method, including:

[0037] When an operation instruction to enter the knowledge base is received, a first rule set matching each vehicle control requirement is displayed in the display interface; wherein the first rule set includes at least part of the vehicle control rules in the preset rule set; the preset rule set is a collection of multiple pre-stored vehicle control rules;

[0038] When a selection operation of a plurality of the first rule sets is received, a knowledge package including the selected plurality of the first rule sets is constructed; the knowledge package is a vehicle control executable code corresponding to the vehicle control rule of the vehicle control requirement;

[0039] When receiving the sending operation of the first rule set, an interface for inputting the target vehicle VIN code is displayed in the display interface;

[0040] When the input VIN code is received, the knowledge package is sent to the target vehicle end corresponding to the VIN code.

[0041] The present application also provides a vehicle control demand processing device, comprising:

[0042] A first acquisition module is used to acquire title information in the vehicle control requirement, wherein the title information includes a control target of the vehicle control requirement;

[0043] a second acquisition module, configured to match the title information in the vehicle control requirement with a preset rule set to acquire a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rules are control logic for controlling the vehicle;

[0044] A conversion module, used for converting the first rule set into an executable file for the vehicle end;

[0045] The sending module is used to send the executable file to the target vehicle corresponding to the vehicle control requirement.

[0046] In one embodiment, the conversion module includes:

[0047] A matching submodule, used for converting a first rule set matching the vehicle control requirement into an XML file;

[0048] A parsing submodule, used for parsing the XML file to convert the XML file into a rule set object;

[0049] The first conversion submodule is used to convert the rule set object into an executable file for the vehicle side.

[0050] In one embodiment, when the vehicle control requirement includes multiple title information, the second acquisition module includes:

[0051] A first acquisition submodule, used to acquire a plurality of first rule sets matching the vehicle control requirement;

[0052] A construction submodule, used to construct a knowledge package corresponding to the plurality of first rule sets;

[0053] The conversion module comprises:

[0054] The second conversion submodule is used to convert the knowledge packages corresponding to the multiple first rule sets into an executable file package for the vehicle side, wherein the executable file package contains multiple executable files, and each executable file corresponds to a first rule set.

[0055] In one embodiment, the apparatus further comprises:

[0056] A display module, configured to display the first rule set when a triggering event for modifying the vehicle control requirement is detected;

[0057] A third acquisition module is used to, when receiving a modification operation on the first rule set object, acquire title information corresponding to the modification operation;

[0058] The editing module is used to edit the rule set according to the title information corresponding to the modification operation, so as to modify the first rule set into a second rule set.

[0059] In one embodiment, the display module comprises:

[0060] A second acquisition submodule, used to acquire the first rule set;

[0061] A serialization submodule, used for serializing the first rule set into JSON format;

[0062] The rendering submodule is used to render the first rule set converted into JSON format on the front end to display the first rule set.

[0063] In one embodiment, the sending module includes:

[0064] An extraction submodule, used to extract the vehicle identification code contained in the vehicle control requirement;

[0065] The sending submodule is used to send the executable file to the vehicle end corresponding to the vehicle identification code.

[0066] In one embodiment, the process of creating the preset rule set is as follows:

[0067] Receive the input operation of the SOA signal value interval of each vehicle control object through the conditional judgment statement box;

[0068] The execution instruction frame corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction to assign the value to the DBO signal library through the SOA signal;

[0069] An input operation of an instruction to reject the input request is received by an execution instruction frame corresponding to the condition that the judgment result does not fall within the signal value interval.

[0070] The present application also provides a vehicle control demand processing system, including:

[0071] at least one processor; and,

[0072] a memory communicatively connected to the at least one processor; wherein,

[0073] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to implement the vehicle control demand processing method recorded in any of the above embodiments.

[0074] The present application also provides a computer-readable storage medium. When the instructions in the storage medium are executed by a processor corresponding to the vehicle control demand processing system, the vehicle control demand processing system can implement the vehicle control demand processing method recorded in any of the above embodiments.

[0075] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings.

[0076] The technical solution of the present application is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The accompanying drawings are used to provide a further understanding of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the present application and do not constitute a limitation of the present application. In the accompanying drawings:

[0078] Figure 1 This is a flow chart of a vehicle control demand processing method in one embodiment of the present application;

[0079] Figure 2 This is a structural schematic diagram of a vehicle control demand processing device in one embodiment of the present application;

[0080] Figure 3 This is a schematic diagram of an operation interface of a vehicle control demand processing method in an embodiment of the present application;

[0081] Figure 4 This is a schematic diagram of the hardware structure of a vehicle control demand processing system in one embodiment of the present application. DETAILED DESCRIPTION

[0082] The preferred embodiments of the present application are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application.

[0083] Figure 1Flow chart of a vehicle control demand processing method in one embodiment of the present application, such as Figure 1 As shown, the method can be implemented as the following steps S101-S104:

[0084] In step S101, the title information in the vehicle control requirement is obtained, wherein the title information includes the control target of the vehicle control requirement;

[0085] In step S102, the title information in the vehicle control requirement is matched with a preset rule set to obtain a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rules are control logic for controlling the vehicle;

[0086] In step S103, the first rule set is converted into an executable file for the vehicle end;

[0087] In step S104, the executable file is sent to the target vehicle terminal corresponding to the vehicle control requirement.

[0088] In the present application, the title information in the vehicle control requirement is obtained, wherein the title information includes the control target of the vehicle control requirement. The vehicle control requirement is the control target that needs to be achieved in a specific scenario. For example, when the vehicle is in the starting state, press the low beam button and the low beam turns on. Specifically, the entry operation of the vehicle control requirement can be an input operation by the designer in the user operation interface, or it can be the receipt of a requirement file. In the input vehicle control requirement, the corresponding title information, such as "low beam", can be obtained.

[0089] The title information in the vehicle control requirement is matched with the preset rule set to obtain a first rule set that matches the vehicle control requirement, wherein the preset rule set is a collection of multiple pre-stored vehicle control rules, and the first rule set contains at least part of the vehicle control rules in the preset rule set, and the vehicle control rules are control logic for controlling the vehicle. The present application separates the vehicle control rules from the vehicle control code through pre-defined semantic specifications, and establishes a preset rule set for storing vehicle control rules, and each vehicle control rule is stored through branch logic such as "if-then-else". For example, the title information of the vehicle control requirement is "low beam", and the first rule set matching "low beam" in the preset rule set can be obtained by matching the title information "low beam" in the vehicle control requirement with the preset rule set. When the vehicle control requirement contains multiple title information, for example, the vehicle control requirement is "When the vehicle is in the starting state, turn on the air conditioning button, then turn on the air conditioning and close the windows at the same time", at this time, the vehicle control requirement contains title information including "air conditioning" and "windows". At this time, the multiple title information is matched with the preset rule sets respectively to obtain multiple first rule sets that match the vehicle control requirement, and the multiple first rule sets are packaged and managed to construct a knowledge package corresponding to the multiple first rule sets. Further, in one embodiment of the present application, the preset rule set can be stored in the form of an XML file. By matching the title information in the vehicle control requirement with the preset rule set, a first rule set in the form of an XML file that matches the vehicle control requirement can be obtained.

[0090] In addition, when it is necessary to modify the rules in the rule set, for example, it is necessary to modify the effective adjustment range of the air-conditioning temperature from 16-28°C to 16-23°C, the corresponding vehicle control rules can be modified. Specifically, when a trigger event for modifying the vehicle control requirements is detected, the first rule set is displayed. Among them, the modification can be a process of modifying the parameters of an existing vehicle control rule, or a new vehicle control rule, or a deletion of an existing vehicle control rule. The trigger event for modifying the vehicle control requirements can be a click on the modification button of the vehicle control requirements corresponding to the first rule set, or a received modification instruction, and then the corresponding first rule set is obtained from the backend. After the backend obtains the first rule set in the form of an XML file, the XML file is parsed to generate a Java object, and serialized into a JSON format. Finally, the first rule set converted into the JSON format is rendered on the front end to realize the display of the first rule set, so as to facilitate the designer to modify the rules. When a modification operation on the first rule set object is received, the title information corresponding to the modification operation is obtained; the rule set is edited according to the title information corresponding to the modification operation to modify the first rule set to the second rule set.

[0091] The first rule set is converted into an executable file for the vehicle side. Since the vehicle computer needs to execute the specific vehicle control requirements, after obtaining the first rule set, the first rule set is converted into a file that can be executed on the vehicle side. Specifically, first, the first rule set matching the vehicle control requirements is converted into an XML file. For example, the first rule set for door control is converted into a corresponding XML file to form Topic_DoorControl.rs.xml; the first rule set for light control is converted into a corresponding XML file to form Topic_LampControl.rs.xml. Then, the XML file is parsed to convert the XML file into a rule set object. Among them, there are many methods for parsing XML files, such as parsing XML files through SAX (full name Simple API for XML, an interface for parsing XML), and then a rule set object can be obtained, the vehicle control rules contained in the rule set, and the management information of vehicle-side signals and vehicle control signals can be obtained. Finally, the rule set object is converted into an executable file for the vehicle side. For example, the executable file on the vehicle side can be a Lua script. Lua is a small scripting language that can be easily embedded in other languages. It can be called by other programming languages ​​and can also call other programming languages ​​in turn. Therefore, it can be widely used in applications. By converting the rule set object into an executable file for the vehicle side, it is convenient for the vehicle side to execute. When the vehicle control requirement contains multiple title information, the knowledge packages corresponding to the multiple first rule sets are converted into executable file packages for the vehicle side, wherein the executable file package contains multiple executable files, and each executable file corresponds to a first rule set.

[0092] The executable file is sent to the target vehicle end corresponding to the vehicle control requirement. Specifically, the vehicle identification code (VIN code) contained in the vehicle control requirement is extracted. Since the vehicle identification code is the vehicle's ID number, it contains information such as the vehicle's manufacturer, year, model, body type and code, engine code and assembly location. It is a unique code for each vehicle. Therefore, the executable file can be sent to the vehicle end corresponding to the vehicle identification code according to the VIN code. It can be a specific vehicle or a certain type of vehicle.

[0093] The beneficial effect of the present application is: obtaining the title information in the vehicle control requirements, then matching the title information in the vehicle control requirements with the preset rule set to obtain a first rule set that matches the vehicle control requirements, and then automatically converting the first rule set into an executable file for the vehicle end, and sending the executable file to the target vehicle end corresponding to the vehicle control requirements. Therefore, for different vehicle control requirements, this method can automatically match the corresponding rules with the preset rule set directly based on the received vehicle control requirements, and automatically convert the matched rules into an executable file for the vehicle end, without the need for developers to repeatedly write code based on vehicle control requirements, thereby improving the development efficiency of vehicle control rules and shortening the development cycle.

[0094] In one embodiment, the above step S103 may be implemented as the following steps A1-A2:

[0095] In step A1, an XML file of a first rule set matching the vehicle control requirement is parsed to convert the XML file into a rule set object, wherein the rule set object is a vehicle control rule code in a preset computer language form;

[0096] In step A2, the rule set object is converted into an executable file for the vehicle side.

[0097] In this embodiment, the first rule set matching the vehicle control demand is stored in the form of an XML file. For example, the first rule set for door control is stored as a corresponding XML file to form Topic_DoorControl.rs.xml. The XML file is parsed to convert the XML file into a rule set object, wherein the rule set object is a vehicle control rule code in a preset computer language. There are many methods for parsing XML files. For example, the XML file is parsed through SAX (full name SimpleAPI for XML, an interface for parsing XML), and then the rule set object can be obtained to form a vehicle control rule code. The rule set contains several rules, each of which is a branch logic such as if-then-else. The rule set is connected to the vehicle-side signal library, and the vehicle-side signal library is used for signal management.

[0098] The rule set object is converted into an executable file for the vehicle side. For example, the executable file for the vehicle side can be a Lua script. Lua is a compact scripting language that is easily embedded in other languages, can be called by other programming languages, and can also call other programming languages ​​in turn. Therefore, it can be widely used in applications. By converting the rule set object into an executable file for the vehicle side, the execution of the vehicle side is facilitated.

[0099] In one embodiment, when the vehicle control requirement includes multiple title information, the above step S102 may be implemented as the following steps B1-B2:

[0100] In step B1, a plurality of first rule sets matching the vehicle control requirement are obtained;

[0101] In step B2, a knowledge package corresponding to the plurality of first rule sets is constructed, wherein the knowledge package is a vehicle control executable code corresponding to the vehicle control rules of the vehicle control requirements.

[0102] In one embodiment, the above step S103 may be implemented as the following step B3:

[0103] In step B3, the knowledge packages corresponding to the multiple first rule sets are converted into executable file packages for the vehicle side, wherein the executable file package contains multiple executable files, and each executable file corresponds to a first rule set.

[0104] In this embodiment, when the vehicle control requirement contains multiple title information, for example, the vehicle control requirement is "when the vehicle is in the start-up state, turn on the air conditioning button, then turn on the air conditioning and close the windows at the same time", at this time, the vehicle control requirement contains title information including "air conditioning" and "windows". At this time, the multiple title information is matched with the preset rule sets respectively to obtain multiple first rule sets that match the vehicle control requirement, and the multiple first rule sets are packaged and managed to construct a knowledge package corresponding to the multiple first rule sets. The knowledge packages corresponding to the multiple first rule sets are converted into executable file packages for the vehicle side. First, the knowledge packages corresponding to the multiple first rule sets are converted into multiple XML files, and then the multiple XML files are parsed and converted into multiple rule set objects. Finally, the multiple rule set objects are converted into files for execution on the vehicle side. In this way, an executable file package containing multiple executable files is formed.

[0105] In one embodiment, the method can also be implemented as the following steps C1-C3:

[0106] In step C1, when a triggering event for modifying the vehicle control requirement is detected, the first rule set is displayed;

[0107] In step C2, when a modification operation on the first rule set object is received, title information corresponding to the modification operation is obtained;

[0108] In step C3, the first rule set is edited according to the title information corresponding to the modification operation, so as to modify the first rule set into a second rule set.

[0109] In this embodiment, when a triggering event for modifying the vehicle control requirements is monitored, the first rule set is displayed. The modification may be a process of modifying the parameters of an existing vehicle control rule, or a process of creating a new vehicle control rule, or a process of deleting an existing vehicle control rule, etc. The triggering event for modifying the vehicle control requirements may be a click on a modification button for the vehicle control requirements corresponding to the first rule set, or a received modification instruction, and the corresponding first rule set is obtained from the back end. After the back end converts the first rule set into an XML file, it parses the XML file to generate a Java object, and serializes it into JSON format. Finally, the first rule set converted into JSON format is rendered on the front end to display the first rule set, making it easier for designers to modify the rules.

[0110] When a modification operation on the first rule set object is received, title information corresponding to the modification operation is obtained; and the first rule set is edited according to the title information corresponding to the modification operation to modify the first rule set into a second rule set.

[0111] In one embodiment, the above step C1 can be implemented as the following steps C11-C13:

[0112] In step C11, the first rule set is obtained;

[0113] In step C12, the first rule set is serialized into JSON format;

[0114] In step C13, the first rule set converted into the JSON format is rendered on the front end to display the first rule set.

[0115] In this embodiment, the first rule set that has been saved is obtained from the backend. Then, after the backend converts the first rule set into an XML file, it parses the XML file to generate a Java object, and serializes it into the JSON format; after the backend converts the first rule set into an XML file, it parses the XML file to generate a Java object, and serializes it into the JSON format. Finally, the first rule set converted into the JSON format is rendered on the frontend to display the first rule set, so that the designer can modify the rules.

[0116] In one embodiment, the above step S104 may be implemented as the following steps D1-D2:

[0117] In step D1, extracting the vehicle identification code contained in the vehicle control requirement;

[0118] In step D2, the executable file is sent to the vehicle end corresponding to the vehicle identification code.

[0119] In this embodiment, the vehicle identification number (VIN code) is extracted from the vehicle control demand. Since the vehicle identification code is the vehicle ID number, it contains information such as the vehicle manufacturer, year, model, body type and code, engine code and assembly location, and is a unique code for each vehicle. Therefore, the vehicle corresponding to the vehicle control demand can be determined according to the VIN code, which can be a specific vehicle or a certain type of vehicle. Then, the executable file is sent to the vehicle end corresponding to the vehicle identification code, so that the corresponding vehicle end can realize the corresponding vehicle control demand.

[0120] In one embodiment, the process of creating the preset rule set may be implemented as the following steps E1-E3:

[0121] In step E1, the input operation of the SOA signal value interval of each vehicle control object is received through the conditional judgment statement box;

[0122] In step E2, the execution instruction box corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction to assign the value to the DBO signal library through the SOA signal;

[0123] In step E3, an input operation of an instruction to reject the input request is received through the execution instruction box corresponding to the condition that the judgment result does not fall within the signal value interval.

[0124] The input operation of the SOA (Service-Oriented Architecture) signal value interval of each vehicle control object is received through the conditional judgment statement box. Since the vehicle control rules in this application are stored in the form of branch logic such as "if-then-else", the conditional judgment statement box is set in the user interface in advance when establishing the preset rule set. The designer can set the signal value of the SOA signal of different vehicle control objects through the conditional judgment statement box. For example, input "SOA signal library / Topic DoorControl.SRV ControlSource equals 0" and "SOA signal library / Topic DoorControl.SRV_TailDoorCtrlSwReg equals 0x66", then the corresponding interval of the corresponding SOA signal value is set.

[0125] The execution instruction box corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction assigned to the DBO signal library through the SOA signal. Among them, the DBO signal is generated by the vehicle side, including the DBC (Dynamic Body Control) signal, the LDF (LIN description file, LIN bus description file) signal and the DBIS (vehicle information transmission signal) signal. In order to control the vehicle, in the user interface, in addition to the input box for receiving instructions, an execution instruction box is also provided to set the execution operation signal fed back by the vehicle after the received SOA signal falls into the preset signal value interval. For example, the feedback DBO signal is "DBO signal library. TailDoorCtrlSwReg = 2".

[0126] The input operation of the instruction to reject the input request is received through the execution instruction box corresponding to the condition that the judgment result does not fall into the signal value interval. In the user interface, another execution instruction box is also provided, which is used to set the DBO signal of the execution operation fed back by the vehicle after the received SOA signal does not fall into the preset signal value interval.

[0127] Figure 2 Schematic diagram of the structure of a vehicle control demand processing device in one embodiment of the present application. Figure 2 As shown, the device comprises:

[0128] A first acquisition module 201 is used to acquire title information in the vehicle control requirement, wherein the title information includes a control target of the vehicle control requirement;

[0129] A second acquisition module 202 is used to match the title information in the vehicle control requirement with a preset rule set to obtain a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rule is a control logic for controlling the vehicle;

[0130] A conversion module 203, used for converting the first rule set into an executable file for the vehicle end;

[0131] The sending module 204 is used to send the executable file to the target vehicle terminal corresponding to the vehicle control requirement.

[0132] In one embodiment, the conversion module includes:

[0133] A matching submodule, used for converting a first rule set matching the vehicle control requirement into an XML file;

[0134] A parsing submodule, used for parsing the XML file to convert the XML file into a rule set object;

[0135] The first conversion submodule is used to convert the rule set object into an executable file for the vehicle side.

[0136] In one embodiment, when the vehicle control requirement includes multiple title information, the second acquisition module includes:

[0137] A first acquisition submodule, used to acquire a plurality of first rule sets matching the vehicle control requirement;

[0138] A construction submodule, used to construct a knowledge package corresponding to the plurality of first rule sets;

[0139] The conversion module comprises:

[0140] The second conversion submodule is used to convert the knowledge packages corresponding to the multiple first rule sets into an executable file package for the vehicle side, wherein the executable file package contains multiple executable files, and each executable file corresponds to a first rule set.

[0141] In one embodiment, the apparatus further comprises:

[0142] A display module, configured to display the first rule set when a triggering event for modifying the vehicle control requirement is detected;

[0143] A third acquisition module is used to, when receiving a modification operation on the first rule set object, acquire title information corresponding to the modification operation;

[0144] The editing module is used to edit the rule set according to the title information corresponding to the modification operation, so as to modify the first rule set into a second rule set.

[0145] In one embodiment, the display module comprises:

[0146] A second acquisition submodule, used to acquire the first rule set;

[0147] A serialization submodule, used for serializing the first rule set into JSON format;

[0148] The rendering submodule is used to render the first rule set converted into JSON format on the front end to display the first rule set.

[0149] In one embodiment, the sending module includes:

[0150] An extraction submodule, used to extract the vehicle identification code contained in the vehicle control requirement;

[0151] The sending submodule is used to send the executable file to the vehicle end corresponding to the vehicle identification code.

[0152] In one embodiment, the process of creating the preset rule set is as follows:

[0153] Receive the input operation of the SOA signal value interval of each vehicle control object through the conditional judgment statement box;

[0154] The execution instruction frame corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction to assign the value to the DBO signal library through the SOA signal;

[0155] An input operation of an instruction to reject the input request is received by an execution instruction frame corresponding to the condition that the judgment result does not fall within the signal value interval.

[0156] Figure 3 This is a schematic diagram of an operation interface of a vehicle control demand processing method in an embodiment of the present application, combined with Figure 3 The vehicle control demand processing method is described, wherein the drawings and various details of this embodiment are used to understand the present application, and they should be considered as merely exemplary and not used to limit the present application. The method includes:

[0157] When an operation instruction to enter the knowledge base is received, a first rule set matching each vehicle control requirement is displayed in the display interface; wherein the first rule set includes at least part of the vehicle control rules in the preset rule set; the preset rule set is a collection of multiple pre-stored vehicle control rules;

[0158] When a selection operation of a plurality of the first rule sets is received, a knowledge package including the selected plurality of the first rule sets is constructed; the knowledge package is a vehicle control executable code corresponding to the vehicle control rule of the vehicle control requirement;

[0159] When receiving a publishing and sending operation for the first rule set, an interface for inputting a target vehicle VIN code is displayed in the display interface;

[0160] When the input VIN code is received, the knowledge package is sent and published to the target vehicle end corresponding to the VIN code.

[0161] In this embodiment, when an operation instruction to enter the knowledge base is received, a first rule set matching each vehicle control requirement is displayed in the display interface, wherein the first rule set is in the form of an XML file or may be a computer code corresponding to the vehicle control rule.

[0162] By selecting multiple first rule sets, a knowledge package including the selected first rule sets is constructed; when the first rule set is in the form of an XML file, the XML file is parsed to obtain a knowledge package of a computer code set corresponding to the vehicle control rules. Figure 3 As shown, when the user selects the first rule set 2, 3, 6, 7, the first rule sets 2, 3, 6, 7 are combined into a knowledge package. When a sending operation for the first rule set is received, an interface for inputting the target vehicle-side VIN code is displayed in the display interface. For example, the user can click the "Publish Current Knowledge Package" button to perform the sending operation for the first rule set. At this time, an interface for inputting the target vehicle-side VIN code pops up, and the user can enter a specific VIN code, thereby sending the knowledge package composed of the first rule set 2, 3, 6, 7 to the vehicle corresponding to the specific VIN code.

[0163] Figure 4 FIG. 1 is a schematic diagram of the hardware structure of a vehicle control demand processing system in one embodiment of the present application. Figure 4 As shown, the vehicle control demand processing system includes:

[0164] at least one processor 420; and,

[0165] A memory 404 in communication with the at least one processor 420; wherein,

[0166] The memory 404 stores instructions that can be executed by the at least one processor 420, and the instructions are executed by the at least one processor 420 to implement the vehicle control demand processing method recorded in any of the above embodiments.

[0167] Reference Figure 4 The vehicle control demand processing system 400 may include one or more of the following components: a processing component 402, a memory 404, a power component 406, a multimedia component 408, an audio component 410, an input / output (I / O) interface 412, a sensor component 414, and a communication component 416.

[0168] The processing component 402 generally controls the overall operation of the vehicle control demand processing system 400. The processing component 402 may include one or more processors 420 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 402 may include one or more modules to facilitate the interaction between the processing component 402 and other components. For example, the processing component 402 may include a multimedia module to facilitate the interaction between the multimedia component 408 and the processing component 402.

[0169] The memory 404 is configured to store various types of data to support the operation of the vehicle control demand processing system 400. Examples of such data include instructions for any application or method operating on the vehicle control demand processing system 400, such as text, pictures, videos, etc. The memory 404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0170] The power component 406 provides power to various components of the vehicle control request processing system 400. The power component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the vehicle control request processing system 400.

[0171] The multimedia component 408 includes a screen that provides an output interface between the vehicle control demand processing system 400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 408 may also include a front camera and / or a rear camera. When the vehicle control demand processing system 400 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0172] The audio component 410 is configured to output and / or input audio signals. For example, the audio component 410 includes a microphone (MIC), and when the vehicle control demand processing system 400 is in an operation mode, such as an alarm mode, a recording mode, a voice recognition mode, and a voice output mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 404 or sent via the communication component 416. In some embodiments, the audio component 410 also includes a speaker for outputting audio signals.

[0173] I / O interface 412 provides an interface between processing component 402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0174] The sensor assembly 414 includes one or more sensors for providing various aspects of status assessment for the vehicle control demand processing system 400. For example, the sensor assembly 414 may include a sound sensor. In addition, the sensor assembly 414 may detect the open / closed state of the vehicle control demand processing system 400, the relative positioning of the components, such as the display and keypad of the vehicle control demand processing system 400, and the sensor assembly 414 may also detect the operating state of the vehicle control demand processing system 400 or a component of the vehicle control demand processing system 400, such as the operating state of the air distribution plate, the structural state, the operating state of the material discharging scraper, etc., the vehicle control demand processing system 400 orientation or acceleration / deceleration and the temperature change of the vehicle control demand processing system 400. The sensor assembly 414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 414 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 414 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, a material accumulation thickness sensor or a temperature sensor.

[0175] The communication component 416 is configured to enable the vehicle control demand processing system 400 to provide the ability to communicate with other devices and cloud platforms in a wired or wireless manner. The vehicle control demand processing system 400 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 416 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 416 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0176] In an exemplary embodiment, the vehicle control demand processing system 400 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to execute the vehicle control demand processing method described in any of the above embodiments.

[0177] The present application also provides a computer-readable storage medium. When the instructions in the storage medium are executed by a processor corresponding to the vehicle control demand processing system, the vehicle control demand processing system can implement the vehicle control demand processing method recorded in any of the above embodiments.

[0178] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0179] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0180] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0181] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0182] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A vehicle control demand processing method, characterized in that: include: Acquire title information in the vehicle control requirement, wherein the title information includes a control target of the vehicle control requirement; Matching the title information in the vehicle control requirement with a preset rule set to obtain a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rule is a control logic for controlling the vehicle; Converting the first rule set into an executable file for the vehicle end; The executable file is sent to the target vehicle terminal corresponding to the vehicle control requirement.

2. The method according to claim 1, characterized in that The first rule set is an XML file, and converting the first rule set into an executable file for the vehicle side includes: Parsing an XML file of a first rule set matching the vehicle control requirement to convert the XML file into a rule set object, wherein the rule set object is a vehicle control rule code in a preset computer language form; Convert the rule set object into an executable file for the vehicle side.

3. The method according to claim 1, characterized in that When the vehicle control requirement includes multiple title information, the acquiring a first rule set matching the vehicle control requirement includes: Acquire a plurality of first rule sets matching the vehicle control requirement; A knowledge package corresponding to the plurality of first rule sets is constructed, wherein the knowledge package is a vehicle control executable code corresponding to the vehicle control rules of the vehicle control requirements.

4. The method according to claim 3, characterized in that The converting the first rule set into an executable file for the vehicle side includes: The knowledge packages corresponding to the multiple first rule sets are converted into executable file packages for the vehicle side, wherein the executable file package includes multiple executable files, and each executable file corresponds to a first rule set.

5. The method according to claim 1, characterized in that The method further comprises: When a triggering event for modifying the vehicle control requirement is detected, displaying the first rule set; When a modification operation on the first rule set object is received, obtaining title information corresponding to the modification operation; The first rule set is edited according to the title information corresponding to the modification operation to modify the first rule set into a second rule set.

6. The method according to claim 5, characterized in that The displaying the first rule set comprises: Obtaining the first rule set; Serializing the first rule set into JSON format; The first rule set converted into the JSON format is rendered on the front end to display the first rule set.

7. The method according to claim 1, characterized in that The process of creating the preset rule set is as follows: Receive the input operation of the SOA signal value interval of each vehicle control object through the conditional judgment statement box; The execution instruction frame corresponding to the condition that the judgment result falls into the signal value interval receives the input operation of the instruction to assign the value to the DBO signal library through the SOA signal; An input operation of an instruction to reject the input request is received by an execution instruction frame corresponding to the condition that the judgment result does not fall within the signal value interval.

8. A vehicle control demand processing method, characterized in that: include: When an operation instruction to enter the knowledge base is received, a first rule set matching each vehicle control requirement is displayed in the display interface; wherein the first rule set includes at least part of the vehicle control rules in the preset rule set; the preset rule set is a collection of multiple pre-stored vehicle control rules; When a selection operation of a plurality of the first rule sets is received, a knowledge package including the selected plurality of the first rule sets is constructed; the knowledge package is a vehicle control executable code corresponding to the vehicle control rule of the vehicle control requirement; When receiving the sending operation of the first rule set, an interface for inputting the target vehicle VIN code is displayed in the display interface; When the input VIN code is received, the knowledge package is sent to the target vehicle end corresponding to the VIN code.

9. A vehicle control demand processing device, characterized in that: include: A first acquisition module is used to acquire title information in the vehicle control requirement, wherein the title information includes a control target of the vehicle control requirement; a second acquisition module, configured to match the title information in the vehicle control requirement with a preset rule set to acquire a first rule set matching the vehicle control requirement, wherein the preset rule set is a set of multiple pre-stored vehicle control rules, the first rule set includes at least part of the vehicle control rules in the preset rule set, and the vehicle control rules are control logic for controlling the vehicle; A conversion module, used for converting the first rule set into an executable file for the vehicle end; The sending module is used to send the executable file to the target vehicle corresponding to the vehicle control requirement.

10. A vehicle control demand processing system, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to implement the vehicle control demand processing method as described in any one of claims 1-7.

11. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by the processor corresponding to the vehicle control demand processing system, the vehicle control demand processing system can implement the vehicle control demand processing method as described in any one of claims 1-7.

Images