Configuration-based command distribution safety control system, method and storage medium

By introducing configuration-based instructions to issue safety control systems in remote vehicle control systems, using modular settings modules to flexibly manage the security of vehicle control instructions, the existing system cannot adapt to changes in market and user demand and multi-version compatibility. The problem has achieved more efficient security control.

CN114779690BActive Publication Date: 2024-11-22CHONGQING CHANGAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210391133.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-14
Publication Date
2024-11-22
Estimated Expiration
2042-04-14

AI Technical Summary

Technical Problem

The existing remote control vehicle safety control system cannot be flexibly adjusted to adapt to changes in market and user needs, and cannot be compatible with multiple versions of coexistence mode, and the same verification method is adopted for different vehicle control instructions, so it is not flexible enough to use.

Method used

A configuration-based instruction issuance safety control system is designed, including the user end and the vehicle machine end. Through the vehicle code control setting module, the version setting module, the critical vehicle control command setting module and the conventional vehicle control command setting module, the control is controlled according to different types. The name, cycle time and number of limits of the vehicle command determine whether the vehicle code is required to be checked, so as to achieve flexible and safe control of the vehicle command.

Benefits of technology

Realizes the configurability of almost all safety verification policies, can adjust the safety level of vehicle control instructions according to needs, be compatible with multiple versions, and adopts different verification methods for different vehicle control instructions, providing safer, flexible and user-friendly services. , has been tested in actual combat.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114779690B_ABST
    Figure CN114779690B_ABST
Patent Text Reader

Abstract

The present invention discloses a configuration-based command issuing safety control system, method and storage medium, the control system includes a user end and a vehicle machine end, the user end is provided with a vehicle control application, the vehicle machine end central control vehicle code setting module is used to set the vehicle control code of the vehicle; the version setting module is used to set the version of the vehicle machine end; the key vehicle control instruction setting module is used to set the key vehicle control instructions of the vehicle; the conventional vehicle control instruction setting module is used to set the conventional vehicle control instructions of the vehicle; the vehicle control instruction issuing time and number setting module is used to set the issuing time and number of issuing of the vehicle control instruction. The present invention is compatible with multiple versions, flexible and variable in configuration, can be flexibly adjusted with changes in market and user needs, compatible with the common multi-version coexistence mode of mobile applications, and can also adopt different verification methods for different vehicle control instructions, thereby providing users with safer, more flexible and more humane services.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent networked vehicles, and in particular to a configuration-based instruction issuance safety control system, method and storage medium. Background Art

[0002] With the development of society, the production, manufacturing, sales and use of automobiles are becoming more and more intelligent. In the field of autonomous driving, car manufacturers and users have higher and higher requirements for the safety of functions in terms of remote control of vehicles. On the premise of ensuring the normal use of functions, new requirements are also put forward for safety. On the premise of ensuring safety, there is also a higher demand for the flexibility and configurability of safety control.

[0003] When users use the remote vehicle control function and issue vehicle control commands, how does the cloud identify whether the user's identity is legitimate, how does it analyze whether the user's behavior is abnormal and whether there are safety hazards, how does it control possible safety risks, and how does it ensure that this safety control method is flexible and configurable and compatible with multiple software iterations? These issues must be considered by vehicle remote control software developers. At the same time, with the advancement of iterations, user needs and market demands are constantly updated, and safety control methods cannot remain unchanged, so the control methods involved in vehicle control safety must also be configurable.

[0004] In response to the above problems, the invention application with application number CN202111234542.1 discloses a safe remote driving system, including: a controlled vehicle end, for receiving command data and executing command data to control vehicle driving; a remote cockpit, which is connected to the controlled vehicle end to output command data; a safety control system, which is connected to the controlled vehicle end and the remote cockpit to verify the authority of the remote cockpit and store the command data at the same time. The safe remote driving system of this method can effectively improve the safety of remote driving through the setting of the safety control system, but the method also has the following problems when it is actually used: 1. The method is not configurable and cannot be flexibly adjusted as the market and user needs change; 2. The method is a single version and is not compatible with the common multi-version coexistence mode of mobile applications; 3. The method uses the same verification method for all vehicle control commands, which is not flexible enough to use. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the technical problem to be solved by the present invention is: how to provide a safety control system and method that can be flexibly adjusted as market and user needs change, compatible with the common multi-version coexistence mode of mobile applications, and adopt different verification methods for different vehicle control commands, and use a more flexible configuration-based command issuance safety control system and method.

[0006] In order to solve the above technical problems, the present invention adopts the following technical solutions:

[0007] A configuration-based command issuing safety control system includes a user end and a vehicle computer end, wherein the user end is provided with a vehicle control application program, and the vehicle computer end includes a vehicle control code setting module, a version setting module, a key vehicle control command setting module, a conventional vehicle control command setting module, and a vehicle control command issuing time and frequency setting module;

[0008] The vehicle control code setting module is used to set the vehicle control code of the vehicle;

[0009] The version setting module is used to set the version of the vehicle terminal to adapt to the version of the control application program of the user terminal;

[0010] The key vehicle control instruction setting module is used to set the key vehicle control instructions of the vehicle;

[0011] The conventional vehicle control instruction setting module is used to set the conventional vehicle control instructions of the vehicle;

[0012] The vehicle control command issuing time and frequency setting module is used to set the issuing time and frequency of the vehicle control command.

[0013] The configuration-based instruction issuance safety control method adopts the above-mentioned configuration-based instruction issuance safety control system, and the instruction issuance safety control method is:

[0014] The name of the key vehicle control instruction is set by the key vehicle control instruction setting module, and the cycle time of the key vehicle control instruction, the limit number of key vehicle control instructions, and whether the first issuance of the key vehicle control instruction within the cycle time period needs to be verified by the vehicle control code are set by the vehicle control instruction issuance time and frequency setting module, and the first issuance of the key vehicle control instruction within the cycle time period needs to be verified by the vehicle control code;

[0015] The name of the conventional vehicle control instruction is set through the conventional vehicle control instruction setting module, and the cycle time of the conventional vehicle control instruction, the limited number of conventional vehicle control instructions, and whether the first issuance of the conventional vehicle control instruction within the cycle time period needs to be verified by the vehicle control code are set through the vehicle control instruction issuance time and frequency setting module. The first issuance of the conventional vehicle control instruction within the cycle time period does not need to be verified by the vehicle control code, but the vehicle control code will be verified when the number of calls of the conventional vehicle control instruction within the cycle time exceeds the limited number.

[0016] Preferably, the command issuing safety control method includes a key vehicle control command control method and a conventional vehicle control command control method, and the conventional vehicle control command control method includes the following steps:

[0017] Step 1) The user terminal sends a conventional vehicle control command to the vehicle computer terminal;

[0018] Step 2) The vehicle computer determines whether the conventional vehicle control command is issued for the first time, if so, execute step 3), if not, execute step 4);

[0019] Step 3) The process of issuing the conventional vehicle control command for the first time is completed;

[0020] Step 4) ends after executing the non-first issuance process of the conventional vehicle control command.

[0021] Preferably, step 3) includes the following steps:

[0022] Step 3.1) The number of times the conventional vehicle control command is called is recorded as 1, and the cycle time of the conventional vehicle control command is used as the expiration time;

[0023] Step 3.2) Whether the conventional vehicle control command needs to be verified by the vehicle control code when it is first issued, if yes, execute step 3.3), if not, execute step 3.4);

[0024] Step 3.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, execute step 3.4); if not, execute step 3.5);

[0025] Step 3.4) The user request for the conventional vehicle control command passes the verification, and then executes step 3.6);

[0026] Step 3.5) reject the user request for the conventional vehicle control command, and then execute step 3.6);

[0027] Step 3.6) is finished.

[0028] Preferably, step 4) includes the following steps)

[0029] Step 4.1) Increase the number of calls of the conventional vehicle control command by 1;

[0030] Step 4.2) Determine whether the number of calls of the conventional vehicle control command exceeds the limit number, if yes, execute step 4.3), if no, execute step 4.5);

[0031] Step 4.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, execute step 4.4); if not, execute step 4.6);

[0032] Step 4.4) The number of calls of the conventional vehicle control command is reset to 1, and the cycle time of the conventional vehicle control command is used as the expiration time before executing step 4.5);

[0033] Step 4.5) The user request for the conventional vehicle control command passes the verification, and then executes step 4.7);

[0034] Step 4.6) reject the user request for the conventional vehicle control command, and then execute step 4.7);

[0035] Step 4.7) is finished.

[0036] Preferably, the key vehicle control command control method comprises the following steps:

[0037] Step S1) the user terminal sends a key vehicle control command to the vehicle terminal;

[0038] Step S2) the vehicle computer determines whether the number of calls of the key vehicle control command exceeds the limit number of the key vehicle control command, if yes, execute step S3), if no, execute step S4);

[0039] Step S3) determines that the user's behavior is abnormal, and ends after executing the abnormal issuance process of the key vehicle control command;

[0040] Step S4) ends after executing the normal issuing process of the key vehicle control instruction.

[0041] Preferably, step S3) includes the following steps:

[0042] Step S3.1) The number of times the key vehicle control instruction is called is recorded as 1, and the cycle time of the key vehicle control instruction is used as the expiration time;

[0043] Step S3.2) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S3.3 is executed. If not, step S3.4 is executed.

[0044] Step S3.3) Clear the cache, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S3.5);

[0045] Step S3.4) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S3.6 is executed);

[0046] Step S3.5) The user request for the key vehicle control command passes the verification, and then executes step S3.7);

[0047] Step S3.6) reject the user request for the key vehicle control command, and then execute step S3.7);

[0048] Step S3.7) ends.

[0049] Preferably, step S4) includes the following steps:

[0050] Step S4.1) Whether the number of successes of the key vehicle control command is 0, if yes, execute step S4.2); if no, execute step S4.3);

[0051] Step S4.2) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S4.4 is executed; otherwise, step S4.5 is executed);

[0052] Step S4.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S4.6 is executed. If not, step S4.7 is executed.

[0053] Step S4.4) Clear the cache, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S4.8);

[0054] Step S4.5) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.9 is executed);

[0055] Step S4.6) The total number of calls of the key vehicle control command is increased by 1, the number of successes is increased by 1, the number of failures and the expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed):

[0056] Step S4.7) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed);

[0057] Step S4.8) The user request for the key vehicle control command passes the verification, and then executes step S4.10);

[0058] Step S4.9) reject the user request for the key vehicle control command, and then execute step S4.10);

[0059] Step S4.10) ends.

[0060] A storage medium stores one or more programs, and when the one or more programs are run by a processor, the above-mentioned configuration-based instruction issuance security control method is executed.

[0061] Compared with the prior art, the present invention has the following advantages:

[0062] 1. Almost all the security verification strategies in the present invention are configurable. The security level of each vehicle control instruction can be determined by configuration. Through the above configuration, the cached process can be obtained and modified according to the corresponding judgment, so as to complete the security control of the vehicle control instruction.

[0063] 2. The present invention is compatible with multiple versions in time and flexible in configuration. It can not only be flexibly adjusted with changes in market and user needs, and compatible with the common multi-version coexistence mode of mobile applications, but also can adopt different verification methods for different vehicle control instructions, thereby providing users with safer, more flexible and more humane services. The control method of the present invention has withstood the test of the market in actual applications and adapted to market demand. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 A system block diagram of a safety control system for issuing instructions based on configurations of the present invention;

[0065] Figure 2 It is a configuration example in the security control method of issuing configuration-based instructions of the present invention;

[0066] Figure 3 It is a flow chart of judging conventional vehicle control instructions in the safety control method for issuing configuration-based instructions of the present invention;

[0067] Figure 4 The present invention is a flow chart for determining key vehicle control instructions in a safety control method based on configuration instructions. DETAILED DESCRIPTION

[0068] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0069] As attached Figure 1 As shown, a configuration-based command issuance safety control system includes a user end and a vehicle computer end. The user end is provided with a vehicle control application, and the user end can be a mobile phone end or a cloud end. The vehicle computer end includes a vehicle control code setting module, a version setting module, a key vehicle control command setting module, a conventional vehicle control command setting module, and a vehicle control command issuance time and frequency setting module.

[0070] The vehicle control code setting module is used to set the vehicle control code of the vehicle; specifically, each user can set a dedicated vehicle control code for his or her own vehicle. When the user issues a remote vehicle control command, the present invention verifies the vehicle control code provided by the user against the vehicle control code that the user has set, thereby determining whether the user is a legitimate user. However, in order to improve the user experience and provide users with a smoother vehicle control process, it is obviously unnecessary and unreasonable to initiate a vehicle control code verification request for each instruction issued by the user, so it is only necessary to verify the vehicle control code for a number of instructions that are strongly related to safety.

[0071] The version setting module is used to set the version of the vehicle computer to adapt to the version of the control application on the user side; specifically, since the application on the user side (such as the mobile phone side) is updated and iterated quickly, different users are likely to use different versions of the user-side application, so different versions of configurations are needed to be compatible with all versions of user-side vehicle control applications currently on the market. In different version configurations, the same vehicle control command may have different verification requirements for the vehicle control code. For example, the horn command requires the user to pass the vehicle control code verification in one version, while in another version the vehicle control code verification can be ignored.

[0072] The key vehicle control command setting module is used to set the key vehicle control commands (types group) of the vehicle; specifically, for the key vehicle control commands that must provide vehicle control code verification within a period of time, the issuance of these commands must require the user to pass the vehicle control code verification within a period of time, otherwise the command will be rejected and not executed; these commands are usually commands that are strongly related to vehicle control safety, such as unlocking the door, starting the engine, etc.

[0073] The conventional vehicle control command setting module is used to set the conventional vehicle control commands (group) of the vehicle; specifically, for conventional vehicle control commands whose vehicle control code verification can be ignored, the issuance of these commands usually does not require vehicle control code verification; however, there is still a limit on the number of times the command is issued within a period of time, such as flashing light commands and horn commands.

[0074] The module for setting the time and frequency of issuing vehicle control commands is used to set the time and frequency of issuing vehicle control commands; specifically, by limiting whether it is necessary to pass the vehicle control code verification within a certain period of time, and the upper limit of the number of times a certain vehicle control command is issued, such as within half an hour, the engine start command must first pass the vehicle control code verification, and the number of times the command is issued cannot exceed 100 times; if the user issues a vehicle control command but fails to pass the vehicle control code verification, the command is rejected and not executed; if the number of times the user issues the vehicle control command exceeds the limit within the configured time period, the vehicle control command verification request is re-initiated for the user.

[0075] Through the above configurations, according to the corresponding judgment and acquisition and modification of the cache process, the safety control of the issuance of vehicle control instructions can be completed.

[0076] In addition, in this embodiment, a configuration-based instruction issuance safety control method is also provided. Using the above configuration-based instruction issuance safety control system, the instruction issuance safety control method is:

[0077] The name (type field) of the key vehicle control instruction (types group) is set through the key vehicle control instruction setting module, and the cycle time (seconds field) of the key vehicle control instruction, the limit number of key vehicle control instructions (times field), and whether the key vehicle control instruction needs to be verified by the vehicle control code when it is first issued within the cycle time period (ignoreFirst field) are set through the vehicle control instruction issuance time and frequency setting module. When the ignoreFirst value is true, it is not required, and when it is false, it is required; and the first issuance of the key vehicle control instruction within the cycle time period needs to be verified by the vehicle control code;

[0078] The name of the conventional vehicle control instruction (group) is set through the conventional vehicle control instruction setting module, and the cycle time (seconds field) of the conventional vehicle control instruction, the limit number of conventional vehicle control instructions (times field), and whether the conventional vehicle control instruction needs to be verified by the vehicle control code when it is first issued within the cycle time period (ignoreFirst field) are set through the vehicle control instruction issuance time and frequency setting module. When the ignoreFirst value is true, it is not required, and when it is false, it is required. The first issuance of the conventional vehicle control instruction within the cycle time period does not need to be verified by the vehicle control code, but the vehicle control code will be verified when the number of calls of the conventional vehicle control instruction within the cycle time exceeds the limit.

[0079] Specifically, Figure 2As shown, the first level of the main configuration in this method is the version number, namely v3 and reserved in the figure. The configuration format in the two versions is the same. The instructions are divided into key vehicle control instructions, namely types group, and regular vehicle control instructions, namely group group instructions. In the types group, the type field is the name of the key vehicle control instruction, the seconds field is the cycle time of the key vehicle control instruction, the times field is the limit number of key vehicle control instructions, and the ignoreFirst field indicates whether the first issuance of the key vehicle control instruction within the time period requires the user to pass the vehicle control code verification. When the value is true, it is not required, and when the value is false, it is required. In the group group instruction, the name field is the group name of the regular vehicle control instruction, the seconds field is the cycle time of the regular vehicle control instruction, the times field is the limit number of regular vehicle control instructions, the types field is the set of regular vehicle control instructions, and the ignoreFirst field indicates whether the first issuance of the regular vehicle control instruction within the time period requires the user to pass the vehicle control code verification. When the value is true, it is not required, and when the value is false, it is required.

[0080] In addition, the present invention discusses whether the vehicle control code verification can be ignored in two situations. The first situation is the logic of whether the vehicle control code of the vehicle control instruction with strong safety correlation, that is, the key vehicle control instruction, can be ignored, which is called the type group. The second situation is the logic of whether the vehicle control code of the vehicle control instruction with weak safety correlation, that is, the conventional vehicle control instruction, can be ignored, which is called the group group. The recommended configuration is that the instructions in the conventional vehicle control instruction group group uniformly ignore the vehicle control code verification of the vehicle control instruction input for the first time, but retain the upper limit of the number of vehicle control code verifications within a period of time; that is, the vehicle control instructions within the group group do not need to be verified under normal circumstances. If the number of instruction calls exceeds a certain set number of times (for example, 100 times) within a certain set time period (for example, 30 minutes), the system can determine that the user call is an abnormal behavior, thereby initiating a vehicle control code verification request to the user to verify whether the user is legal. For the instructions in the types group, each vehicle control instruction has its own vehicle control code ignoring logic setting, as well as its own upper limit setting for the frequency of use. Currently, group commands cover most common vehicle control commands, while types commands are used to make special settings on key vehicle control commands to meet higher safety requirements for vehicle control. It is usually recommended to configure the commands in types to require the user to enter the vehicle control code for the first time, otherwise the command can be included in group commands.

[0081] When it is necessary to clarify whether the vehicle control code can be ignored, the method can be discussed separately according to the types group and group group to which the instruction belongs. Since different iteration versions have different logic configurations for whether the vehicle control code can be ignored, the method also needs to obtain the corresponding configuration based on the version number. And since there is a requirement in the logic of whether the vehicle control code can be ignored to determine whether it can be ignored for the first time, that is, within a period of time, whether the user needs to pass the vehicle control code verification when issuing a certain vehicle control instruction for the first time, so this method also needs to introduce a cache mechanism to record the user's vehicle control instruction issuance history.

[0082] As attached Figure 3 As shown, in this embodiment, the instruction issuance safety control method includes a key vehicle control instruction control method and a conventional vehicle control instruction control method, and the conventional vehicle control instruction control method includes the following steps:

[0083] Step 1) The user terminal sends a conventional vehicle control command to the vehicle computer terminal;

[0084] Step 2) The vehicle computer determines whether the conventional vehicle control command is issued for the first time by checking the number of vehicle control command issuances n in the cache. If so, that is, n is empty, execute step 3); otherwise, execute step 4);

[0085] Step 3) The process of issuing the conventional vehicle control command for the first time is completed;

[0086] Step 4) ends after executing the non-first issuance process of the conventional vehicle control command.

[0087] In this embodiment, step 3) includes the following steps:

[0088] Step 3.1) The number of calls n of the conventional vehicle control command is recorded as 1, and the cycle time seconds of the conventional vehicle control command is used as the expiration time;

[0089] Step 3.2) Whether the conventional vehicle control command needs to be verified by the vehicle control code when it is first issued, if yes, execute step 3.3), if not, execute step 3.4);

[0090] Step 3.3) The user sends the vehicle control code, and the vehicle computer verifies whether the vehicle control code is correct. If so, proceed to step 3.4). If not, proceed to step 3.5);

[0091] Step 3.4) The user request for the conventional vehicle control command passes the verification, and then executes step 3.6);

[0092] Step 3.5) reject the user request for the conventional vehicle control command, and then execute step 3.6);

[0093] Step 3.6) is finished.

[0094] In this embodiment, step 4) includes the following steps:

[0095] Step 4.1) Increase the number of calls n of the conventional vehicle control command by 1;

[0096] Step 4.2) Determine whether the number of calls n of the conventional vehicle control command exceeds the limit number, if yes, execute step 4.3), if no, execute step 4.5);

[0097] Step 4.3) The user sends the vehicle control code, and the vehicle computer verifies whether the vehicle control code is correct. If so, proceed to step 4.4); if not, proceed to step 4.6);

[0098] Step 4.4) The number of calls n of the conventional vehicle control command is reset to 1, and the cycle time seconds of the conventional vehicle control command is used as the expiration time before executing step 4.5);

[0099] Step 4.5) The user request for the conventional vehicle control command passes the verification, and then executes step 4.7);

[0100] Step 4.6) reject the user request for the conventional vehicle control command, and then execute step 4.7);

[0101] Step 4.7) is finished.

[0102] Specifically, for group group instructions, when the method obtains the corresponding configuration according to the corresponding version, and it is clear that the instruction currently issued by the user belongs to the regular vehicle control instruction of the group group, then the method needs to combine the historical instruction issuance records in the cache and the verification result of the current user's vehicle control code to calculate whether the vehicle control code of the user's current instruction can be ignored. For example, if the record in the current cache is empty, it means that the current vehicle control instruction is the first vehicle control instruction issued by the user in the current time period. In this case, whether the vehicle control code can be ignored can be obtained based on the ignoreFirst field in the configuration, and the current instruction issuance is counted as an operation and stored in the cache, and the expiration time corresponding to the cache is set to the seconds field in the configuration. For example again, if the current cache already has a record of the number of times the user has issued the command, it means that the vehicle control command issued by the current user is not the first command in the current time period. The method still needs to store the user's command in the cache counter, and then judge the number of times in the counter in the cache. If the number does not exceed the maximum number of times configured, the vehicle control code verification for this command can be ignored. If the number of times the command has been issued has exceeded the limit in the configuration, then for safety reasons, the method will determine the current call as an abnormal user operation, and require the user to pass the vehicle control code verification. Note here that if the user's current frequency of issuing commands has exceeded the limit and provides a correct vehicle control code verification result, the method will reset the counter in the cache to 1, and the expiration time of the cache record will be reset to the seconds field in the configuration.

[0103] As attached Figure 4 As shown, in this embodiment, the key vehicle control command control method includes the following steps:

[0104] Step S1) The user terminal sends key vehicle control instructions to the vehicle computer terminal;

[0105] Step S2) The vehicle computer determines whether the number of calls of the key vehicle control command exceeds the limit number of the key vehicle control command through the total number of calls in the cache. If yes, execute step S3); otherwise, execute step S4);

[0106] Step S3) determines that the user's behavior is abnormal, and ends after executing the abnormal issuance process of the key vehicle control command;

[0107] Step S4) ends after executing the normal issuing process of the key vehicle control instruction.

[0108] In this embodiment, step S3) includes the following steps:

[0109] Step S3.1) The number of times the key vehicle control command is called is recorded as 1, and the cycle time of the key vehicle control command is seconds as the expiration time;

[0110] Step S3.2) The user terminal sends the vehicle control code, and the vehicle computer verifies whether the vehicle control code is correct. If so, execute step S3.3); if not, execute step S3.4);

[0111] Step S3.3) Clear the cache, re-circulate, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S3.5);

[0112] Step S3.4) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S3.6 is executed);

[0113] Step S3.5) The user request for the key vehicle control command passes the verification, and then executes step S3.7);

[0114] Step S3.6) reject the user request for the key vehicle control command, and then execute step S3.7);

[0115] Step S3.7) ends.

[0116] In this embodiment, step S4) includes the following steps:

[0117] Step S4.1) Whether the number of successes of the key vehicle control command is 0, if yes, execute step S4.2); if no, execute step S4.3);

[0118] Step S4.2) The user terminal sends the vehicle control code, and the vehicle computer verifies whether the vehicle control code is correct. If so, execute step S4.4); if not, execute step S4.5);

[0119] Step S4.3) The user terminal sends the vehicle control code, and the vehicle computer verifies whether the vehicle control code is correct. If so, execute step S4.6); if not, execute step S4.7);

[0120] Step S4.4) Clear the cache, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S4.8);

[0121] Step S4.5) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.9 is executed);

[0122] Step S4.6) The total number of calls of the key vehicle control command is increased by 1, the number of successes is increased by 1, the number of failures and the expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed):

[0123] Step S4.7) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed);

[0124] Step S4.8) The user request for the key vehicle control command passes the verification, and then executes step S4.10);

[0125] Step S4.9) reject the user request for the key vehicle control command, and then execute step S4.10);

[0126] Step S4.10) ends.

[0127] Specifically, for instructions in the types group, there is a more complex cache setting logic. In the cache, the method will store three data: the total number of calls to key vehicle control instructions, the number of successful verifications of key vehicle control instructions, and the number of failed verifications of key vehicle control instructions. First, before determining whether the vehicle control code of the types group instruction can be ignored, the method needs to prepare the type group instruction vehicle control code ignorable logic configuration corresponding to the current version number, as well as the vehicle control code verification result of the instruction issued by the current user. If the currently issued instruction belongs to the instruction in the types group, the method needs to first obtain the cache of the user's issuance of the instruction. The method is then discussed in different situations:

[0128] If the total number of key vehicle control commands issued in the cache exceeds the limit, this method will determine it as abnormal user behavior, and the user will need to pass the vehicle control code verification anyway. At the same time, this method also needs to update the cache based on the verification result of the current vehicle control code. If the current vehicle control code is correct, this method will clear the records in the cache and start recording a new period of time, that is, the total number of times in the cache is set to 1, the number of successes is set to 1, the number of failures is set to 0, and the cache expiration time is set to the corresponding seconds field in the configuration. If the current vehicle control verification fails, this method will add 1 to the total number and number of failures in the current cache, and the cache expiration time remains unchanged.

[0129] If the number of times the user in the cache sends key vehicle control commands does not exceed the limit in the configuration. There are two cases to discuss: one is that the number of successes in the cache is greater than 0, indicating that this command is not the first successful command of the user in the current time period. Since the current command is not the first successful command, this method regards it as a regular intermediate command, and such commands do not require vehicle control code verification. However, the cache still needs to be updated according to the vehicle control code verification situation. The update rule is: the total number of times plus 1, if the vehicle control code verification result is correct, the number of successes plus 1, otherwise the number of failures plus 1, and the cache expiration time remains unchanged. Another case is that the number of successes in the cache is 0, indicating that the current command is issued for the first time in the current time period. If the current vehicle control code verification result is correct, this is the first time the vehicle control code is correctly entered in this time period. The method will clear the cache and start a new cycle, that is, the total number of times in the cache is set to 1, the number of successes is set to 1, the number of failures is set to 0, and the cache expiration time is set to the corresponding seconds field in the settings. If the verification result of the current vehicle control code fails, this method will increase the total number of times and the number of failures in the current cache by 1, and the cache expiration time remains unchanged.

[0130] In addition, the present invention also provides a storage medium, which stores one or more programs. When the one or more programs are run by a processor, the above-mentioned configuration-based instruction issuance security control method is executed.

[0131] Compared with the prior art, almost all the security verification strategies in the present invention are configurable, and the security level of each vehicle control instruction can be determined by configuration. Through the above configuration, the cached process can be obtained and modified according to the corresponding judgment, and the security control of the vehicle control instruction can be completed. The present invention is compatible with multiple versions in time and flexible in configuration. It can not only flexibly adjust with the changes in market and user needs, and is compatible with the common multi-version coexistence mode of mobile applications, but also can adopt different verification methods for different vehicle control instructions, thereby providing users with safer, more flexible and more humane services, and the control method of the present invention has withstood the test of the market in actual combat applications and adapted to the needs of the market.

[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit the technical solution. Those skilled in the art should understand that those modifications or equivalent substitutions of the technical solution of the present invention that do not depart from the purpose and scope of the technical solution should be included in the scope of the claims of the present invention.

Claims

1. A configuration-based instruction issuance security control method, characterized in that: A configuration-based command issuing safety control system is adopted, including a user end and a vehicle computer end, wherein the user end is provided with a vehicle control application program, and the vehicle computer end includes a vehicle control code setting module, a version setting module, a key vehicle control command setting module, a conventional vehicle control command setting module, and a vehicle control command issuing time and frequency setting module; The vehicle control code setting module is used to set the vehicle control code of the vehicle; The version setting module is used to set the version of the vehicle terminal to adapt to the version of the control application program of the user terminal; The key vehicle control instruction setting module is used to set the key vehicle control instructions of the vehicle; The conventional vehicle control instruction setting module is used to set the conventional vehicle control instructions of the vehicle; The vehicle control command issuing time and frequency setting module is used to set the issuing time and frequency of the vehicle control command; The instruction issuing safety control method is: The name of the key vehicle control instruction is set by the key vehicle control instruction setting module, and the cycle time of the key vehicle control instruction and the limit number of key vehicle control instructions are set by the vehicle control instruction issuance time and frequency setting module, and the first issuance of the key vehicle control instruction within the cycle time period needs to be verified by the vehicle control code; The name of the conventional vehicle control instruction is set through the conventional vehicle control instruction setting module, and the cycle time of the conventional vehicle control instruction and the limited number of conventional vehicle control instructions are set through the vehicle control instruction issuance time and frequency setting module. The first issuance of the conventional vehicle control instruction within the cycle time period does not need to be verified by the vehicle control code, but the vehicle control code will be verified when the number of calls of the conventional vehicle control instruction within the cycle time exceeds the limited number.

2. The configuration-based instruction issuance safety control method according to claim 1, characterized in that: The command issuing safety control method includes a key vehicle control command control method and a conventional vehicle control command control method, and the conventional vehicle control command control method includes the following steps: Step 1) The user terminal sends a conventional vehicle control command to the vehicle computer terminal; Step 2) The vehicle computer determines whether the conventional vehicle control command is issued for the first time, if so, execute step 3), if not, execute step 4); Step 3) The process of issuing the conventional vehicle control command for the first time is completed; Step 4) ends after executing the non-first issuance process of the conventional vehicle control command.

3. The configuration-based instruction issuance safety control method according to claim 2 is characterized in that: Step 3) includes the following steps: Step 3.1) The number of times the conventional vehicle control command is called is recorded as 1, and the cycle time of the conventional vehicle control command is used as the expiration time; Step 3.2) Whether the conventional vehicle control command needs to be verified by the vehicle control code when it is first issued, if yes, execute step 3.3), if not, execute step 3.4); Step 3.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, execute step 3.4); if not, execute step 3.5); Step 3.4) The user request for the conventional vehicle control command passes the verification, and then executes step 3.6); Step 3.5) reject the user request for the conventional vehicle control command, and then execute step 3.6); Step 3.6) is finished.

4. The configuration-based instruction issuance safety control method according to claim 3 is characterized in that: Step 4) includes the following steps) Step 4.1) Increase the number of calls of the conventional vehicle control command by 1; Step 4.2) Determine whether the number of calls of the conventional vehicle control command exceeds the limit number, if yes, execute step 4.3), if no, execute step 4.5); Step 4.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, execute step 4.4); if not, execute step 4.6); Step 4.4) The number of calls of the conventional vehicle control command is reset to 1, and the cycle time of the conventional vehicle control command is used as the expiration time before executing step 4.5); Step 4.5) The user request for the conventional vehicle control command passes the verification, and then executes step 4.7); Step 4.6) reject the user request for the conventional vehicle control command, and then execute step 4.7); Step 4.7) is finished.

5. The configuration-based instruction issuance safety control method according to claim 4 is characterized in that: The key vehicle control command control method comprises the following steps: Step S1) the user terminal sends a key vehicle control command to the vehicle terminal; Step S2) the vehicle computer determines whether the number of calls of the key vehicle control command exceeds the limit number of the key vehicle control command, if yes, execute step S3), if no, execute step S4); Step S3) determines that the user's behavior is abnormal, and ends after executing the abnormal issuance process of the key vehicle control command; Step S4) ends after executing the normal issuing process of the key vehicle control instruction.

6. The configuration-based instruction issuance safety control method according to claim 5, characterized in that: Step S3) includes the following steps: Step S3.1) The number of times the key vehicle control instruction is called is recorded as 1, and the cycle time of the key vehicle control instruction is used as the expiration time; Step S3.2) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S3.3 is executed. If not, step S3.4 is executed. Step S3.3) Clear the cache, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S3.5); Step S3.4) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S3.6 is executed); Step S3.5) The user request for the key vehicle control command passes the verification, and then executes step S3.7); Step S3.6) reject the user request for the key vehicle control command, and then execute step S3.7); Step S3.7) ends.

7. The configuration-based instruction issuance safety control method according to claim 6, characterized in that: Step S4) includes the following steps: Step S4.1) Whether the number of successes of the key vehicle control command is 0, if yes, execute step S4.2); if no, execute step S4.3); Step S4.2) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S4.4 is executed; otherwise, step S4.5 is executed); Step S4.3) The user terminal sends the vehicle control code, and the vehicle terminal checks whether the vehicle control code is correct. If so, step S4.6 is executed. If not, step S4.7 is executed. Step S4.4) Clear the cache, record the total number of calls of the key vehicle control command as 1, the number of successes as 1, the number of failures as 0, and reconfigure the expiration time of the key vehicle control command before executing step S4.8); Step S4.5) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.9 is executed); Step S4.6) The total number of calls of the key vehicle control command is increased by 1, the number of successes is increased by 1, the number of failures and the expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed): Step S4.7) The total number of calls of the key vehicle control command is increased by 1, the number of failures is increased by 1, and the number of successes and expiration time of the key vehicle control command remain unchanged, and then step S4.8 is executed); Step S4.8) The user request for the key vehicle control command passes the verification, and then executes step S4.10); Step S4.9) reject the user request for the key vehicle control command, and then execute step S4.10); Step S4.10) ends.

8. A storage medium, characterized in that: The storage medium stores one or more programs, and when the one or more programs are executed by the processor, the configuration-based instruction issuance safety control method according to any one of claims 1 to 7 is executed.