CN117041344A - Vehicle service request management method and device - Google Patents

Abstract

The application provides a vehicle service request management method and device, relates to the technical field of vehicle service request management, and is applied to electronic equipment. The vehicle service request management method comprises the following steps: the electronic device determines a first service request, determines a corresponding first service request management gray rule according to the first service request, determines a corresponding rule engine and rule script according to the first service request management gray rule when the corresponding first service request management gray rule is determined to exist, executes the rule script according to the rule engine to generate an execution result, and sends the first service request to the target vehicle according to the execution result. In this way, the corresponding rule engine execution rule script can be selected according to the first service request management gray rule corresponding to the first service request, and the vehicle which needs to issue the service request is determined according to the execution result of the rule engine execution rule script, so that the target vehicle which receives the service request can normally execute the service request.

Description

Vehicle service request management method and device

Technical Field

The present application relates to the field of vehicle service request management technologies, and in particular, to a vehicle service request management method and device.

Background

With the rapid development of computer technology, people have more and more requirements on vehicles, and on the premise of taking the vehicles as a walking tool, the vehicles are required to have various functions for users. Therefore, in order to meet the demands of users, vehicle suppliers develop vehicles of different versions, different types and with different functions.

Currently, when the cloud (i.e. the cloud server) sends a service request to a vehicle, the service request is sent to all vehicles registered in the cloud, for example, but since the version of the service request is unique, the versions of different vehicles are different, and if the version of the vehicle is not matched with the version of the service request sent by the cloud, the vehicle cannot execute the service request.

Disclosure of Invention

The application provides a vehicle service request management method and device, which are used for solving the problem that in the prior art, if the version of a vehicle is not matched with the version of a service request sent by a cloud, the vehicle cannot execute the service request.

In a first aspect, the present application provides a vehicle service request management method, applied to an electronic device, the method including: determining a first service request; determining a corresponding rule engine and rule script according to the first service request management gray rule under the condition that the first service request management gray rule corresponding to the first service request exists according to the first service request; executing the rule script according to the rule engine to obtain an execution result; and sending the first service request to the target vehicle according to the execution result.

In the implementation mode of the application, the electronic equipment is specifically electronic equipment such as a cloud server, a mobile terminal and the like.

According to the vehicle service request management method provided by the implementation mode of the application, the corresponding first service request management gray scale rule is determined according to the first service request, and under the condition that the corresponding first service request management gray scale rule is determined to exist, the corresponding rule engine and rule script are determined according to the first service request management gray scale rule, so that the rule engine executes the rule script to generate an execution result, and a target vehicle needing to issue the first service request is determined according to the execution result. In this way, the corresponding rule engine execution rule script can be selected according to the first service request management gray rule corresponding to the first service request, so that the target vehicle which needs to issue the service request can be determined according to the execution result of the rule engine execution rule script, and the first service request can be issued to the vehicle with the version matched with the version of the first service request, namely, the first service request can be issued to the vehicle which can execute the service request, and the target vehicle which receives the first service request can normally execute the first service request.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, according to an execution result, a first service request is sent to a target vehicle, including: if the execution result is that the execution passes, the first service request is sent to a first vehicle, wherein the first vehicle is a gray vehicle corresponding to the first service request management gray rule in vehicles corresponding to the cloud server; and if the execution result is that the execution fails, the first service request is sent to a second vehicle, wherein the second vehicle is a non-gray-scale vehicle corresponding to the first service request management gray-scale rule in the vehicles corresponding to the cloud server.

In an implementation manner of the application, according to an execution result of a rule script executed by a rule engine, a first service request is sent to a gray-scale vehicle when the execution result is that the execution is passed, and the first service request is sent to a non-gray-scale vehicle when the execution result is that the execution is not passed. Therefore, the vehicle which needs to issue the first service request can be determined according to the execution result, and the first service request is issued to the vehicle which can normally execute the first service request through flexible issuing of the first service request.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, the sending the first service request to the first vehicle includes: under the condition that the request parameters in the rule script are confirmed to be modified, the request parameters of the first service request are modified according to the request parameters in the rule script to obtain a modified first service request, and the modified first service request is sent to the first vehicle; in the event that no modification of the request parameters in the rule script is determined, the first service request is sent directly to the first vehicle.

In the implementation mode of the application, under the condition that the request parameters in the rule script are confirmed to be modified, the request parameters of the first service request are modified according to the request parameters in the rule script to obtain a modified first service request, and the modified first service request is issued to the first vehicle. In this way, the request parameters of the first service request are dynamically adjusted according to the request parameters in the rule script, and when the version of the first service request and the version of the grayscale vehicle do not match, and in the case that the versions do not match, the grayscale vehicle cannot execute the first service request, the vehicle can still execute the first service request.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, the method further includes: in the process of executing the rule script by the rule engine, the request parameters in the rule script are modified under the condition that the request parameters in the rule script are required to be modified according to the request parameters of the first service request and the vehicle information of the first vehicle.

In one implementation of the vehicle service request management method provided by the implementation of the present application, the vehicle information includes version information of the vehicle and vehicle identification information of the vehicle.

In the implementation mode of the application, whether the request parameters in the rule script need to be modified is determined by the rule engine according to the request parameters of the first service request and the vehicle information of the first vehicle, so that the rule script can be adapted to the first vehicle, and further the issued service request can be normally executed by the first vehicle.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, the method further includes: and under the condition that the first service request management gray scale rule corresponding to the first service request does not exist according to the first service request, the first service request is sent to a third vehicle, and the third vehicle is a vehicle corresponding to the cloud server.

In the implementation manner of the present application, if there is no first service request management gray rule corresponding to the first service request, it is indicated that the first service request has no wound piece, so that the present application is applicable to all vehicles.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, determining a corresponding rule engine and rule script according to a first service request management gray rule includes: determining a rule engine according to the compiling type of the first service request management gray rule; and determining a rule script according to the request parameters included in the first service request and a rule template of the first service request management gray rule.

In one implementation of the vehicle service request management method provided by the implementation of the present application, the request parameters include a request type, a request content and request version information.

In the implementation mode of the application, the corresponding rule engine is determined according to the compiling type of the service request management gray rule, thereby determining the matched rule engine. And determining a rule script based on the request parameters included in the first service request and the rule template for managing the gray scale rule according to the service request, thereby obtaining the rule script of the first service request.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, the first service request management gray rule corresponding to the first service request is obtained by the following manner: and determining a first service request management gray rule corresponding to the first service request according to the request type of the first service request and the corresponding relation between the preset request type and the service request management gray rule.

In an implementation manner of the application, a first service request management gray rule corresponding to a first service request is obtained according to a corresponding relation between a preset request type and a service request management gray rule. Therefore, the corresponding relation is stored in the cloud server in advance, so that the searching is convenient.

In a second aspect, the present application provides a vehicle service request management apparatus comprising: a first processing module for determining a first service request; the second processing module is used for determining a corresponding rule engine and rule script according to the first service request management gray rule under the condition that the first service request management gray rule corresponding to the first service request exists according to the first service request; the third processing module is used for executing the rule script according to the rule engine to obtain an execution result; and the fourth processing module is used for sending the first service request to the corresponding target vehicle according to the execution result.

The vehicle service request management apparatus provided by the present application includes a module for executing the vehicle service request management method provided by the first aspect, so that the beneficial effects (or advantages) provided by the vehicle service request management method provided by the first aspect can also be achieved.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to implement the vehicle service request management method as provided by the implementation manner of the first aspect described above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, are configured to implement a vehicle service request management method as provided in the implementation manner of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the vehicle service request management method provided by the implementation of the first aspect described above.

It will be appreciated that the advantages of the third to fifth aspects may also be referred to in the description of the first aspect, and are not described here again.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a flow chart of a vehicle service request management method according to an embodiment of the present application;

FIG. 2 is a flowchart illustrating another vehicle service request management method according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating another vehicle service request management method according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a vehicle service request management device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

As described above, in the current internet of vehicles service, when the vehicle receives a service request issued by the cloud (i.e., a cloud server) in the interactive upgrade of the vehicle and the cloud, if the versions of the cloud and the vehicle are inconsistent, the service request received by the vehicle cannot be used temporarily, so that the user experience is affected.

Based on the above, the application provides a vehicle service request management method, when a new version is released, a corresponding gray rule is released, when a service request is sent by a cloud, a matched vehicle is called according to the identification result of the service request sent by the cloud, so that the matched vehicle executes corresponding request service, and the update of the vehicle version is realized on the premise that the normal use of the vehicle function is not influenced.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, as shown in fig. 1, the vehicle service request management method is implemented specifically through the following steps.

S110, determining a first service request.

S120, when the service request management gray scale rule corresponding to the first service request exists according to the first service request, a corresponding rule engine and a rule script are determined according to the service request management gray scale rule.

S130, executing the rule script according to the rule engine to obtain an execution result.

And S140, according to the execution result, sending the first service request to the target vehicle.

According to the vehicle service request management method provided by the implementation mode of the application, the corresponding first service request management gray scale rule is determined according to the first service request, and under the condition that the corresponding first service request management gray scale rule is determined to exist, the corresponding rule engine and rule script are determined according to the first service request management gray scale rule, so that the rule engine executes the rule script to generate an execution result, and the vehicle needing to issue the first service request is determined according to the execution result. In this way, the corresponding rule engine execution rule script can be selected according to the first service request management gray rule corresponding to the first service request, so that the vehicle needing to issue the first service request is determined according to the execution result of the rule engine execution rule script, and the target vehicle receiving the first service request can normally execute the first service request.

In an implementation of the present application, the service request management gray rule, for example, the first service request management gray rule includes a logic expression as a judgment condition, and the judgment condition is a logic connection relationship. For example, if it is determined that the first service request is to open a sunroof, it is determined whether there is a corresponding vehicle capable of opening a sunroof, that is, whether there is a corresponding gray rule.

Thus, a service request management gray rule is whether a vehicle is included that can be used to perform the service request, e.g., the first service request, or whether there is a condition that can be matched to the service type of the service request (e.g., the service type of the first service request).

In the implementation mode of the application, the corresponding relation between the service request and the service request management gray scale rule is preset and stored in the cloud server.

In the implementation mode of the application, the rule engine is a tool for executing the rule script of the gray rule, different gray rules are provided with different rule templates, and the coding types of the rule templates are different, so that the rule engine capable of executing the service request to manage the gray rule needs to be selected.

For example, if the encoding type of the service request management gray scale rule is Python, a rules engine of Python may be used. The service request manages the encoding type of the gray scale rule as Java Script, and then a rule engine of Java Script may be employed. The service request manages the coding type of the gray scale rule to be Groovy, and then a rules engine of Groovy can be adopted.

In the implementation mode of the application, the rule script is generated based on the request parameter of the first service request and the rule template of the gray rule, and the rule script is executed by the rule engine to determine the execution result.

In the implementation mode of the application, the rule template mainly has general code information, such as code information comprising a service request for issuing a skylight, but does not need to comprise specific vehicle information for issuing a vehicle, version information of the service request and specific request content of the service request.

The rule script is generated by the rule template and the request parameters of the first service request such that the rule script includes specific information specific to the request parameters for executing the first service request.

In an implementation manner of the present application, the electronic device may be a cloud server, or may be other electronic devices, such as a server, a cloud platform, and the like.

In one implementation manner of the vehicle service request management method provided by the implementation manner of the present application, as shown in fig. 2, the vehicle service request management method is specifically implemented in the following manner.

S210, the cloud server determines a first service request.

In an implementation manner of the present application, the first service request may specifically be a service request issued by the cloud server, where the user performs vehicle control through a mobile terminal such as a mobile phone to instruct the vehicle to execute a service request of a certain function service, and the mobile terminal sends the first service request to the cloud server, and determines the issued vehicle according to a gray rule by the cloud server.

S220, the cloud server determines whether a first service request management gray rule corresponding to the first service request exists according to the first service request. If it is determined that the first service request management gray rule corresponding to the first service request exists, step S230 is executed, and if it is determined that the first service request management gray rule corresponding to the first service request does not exist, step S280 is executed.

In an exemplary embodiment, the first service request management gray rule corresponding to the first service request is determined according to a request parameter, for example, a request type, of the first service request from a preset corresponding relationship between the service request and the service request management gray rule.

In an implementation manner of the present application, the request parameter for determining the first service request management gray rule is specifically a general parameter of the service request, for example, only a certain execution action, but no specific execution content is needed, and whether a hit vehicle is necessarily provided is determined based on the general parameter. For example, taking window opening as an example, the first service request is window opening, and the cloud server determines that there is a vehicle meeting the condition of window opening according to the first service request, that is, manages the gray rule for the corresponding first service request.

And S230, the cloud server determines a corresponding rule engine and rule script according to the first service request management gray rule.

Illustratively, a corresponding rule engine is determined based on the determined encoding type of the rule template of the first service request management gray scale rule, such that the determined rule engine is capable of executing the code content of the rule template of the first service request management gray scale rule.

Further, according to the request parameters of the first service request and the rule templates of the first service request management gray scale rules, determining rule scripts corresponding to the first service request.

Illustratively, request parameters, such as request content, request version information, etc., of the first service request are input into the rule template to generate a rule script.

In an example of opening the vehicle, the request content of the first service request may specifically be at least one piece of information such as opening a front window, opening a rear window, opening a front window by 30%.

The request version information is specifically version information of application software of the mobile terminal sending the first service request.

In an implementation manner of the present application, the request parameter further includes information such as a vehicle vin code (as an example of the vehicle identification information) carried in the first service request. For example, the cloud server has parsed the vehicle identification information that needs to be executed to open the window from the request parameters.

S240, the cloud server executes the rule script according to the rule engine to obtain an execution result.

Illustratively, the rule engine executes the rule script to obtain the boolean value. When the boolean value is true (as an example of execution passing), it is indicated that the request parameter of the first service request is different from the vehicle version information hit by the first service request management gray rule, and the determination result of the logic expression is true. That is, if the execution result is true, it is indicated that there is a vehicle (i.e., the first vehicle) that can hit the first service request management gray rule, but the version information is different from the version information of the first service request.

When the boolean value is false (as an example of not passing execution), it is indicated that the request parameter of the first service request is the same as the vehicle version information hit by the first service request management gray rule, and the determination result of the logic expression is false. That is, if the execution result is false, a vehicle (i.e., a second vehicle) having the same version information as the version information of the service request and having the service request management gray scale rule hit is described.

S250, determining whether the execution result passes, if the execution result passes, executing step S260, and if the execution result does not pass, executing step S270.

For example, if it is determined that the execution result is true, step S260 is executed, and if it is determined that the execution result is false, step S270 is executed.

And S260, sending the first service request to the first vehicle.

For example, in the case where the execution result is execution pass, the first service request is transmitted to the first vehicle (as an example of the target vehicle).

The first vehicle is a gray-scale vehicle corresponding to the first service request management gray-scale rule in vehicles corresponding to the cloud server.

The vehicle corresponding to the cloud server refers to a vehicle capable of communicating with the cloud server, namely, a vehicle which is currently established with communication connection, a vehicle which is registered in the cloud server, a vehicle which corresponds to the cloud server according to a certain rule, a vehicle which stores vehicle information in the cloud server, and the like.

Specifically, the first service request is sent to the cloud server, and when the cloud server determines that the first service request corresponding to the first service request manages the gray rule, the cloud server can determine the vehicle that needs to issue the first service request. Further, it is determined that the vehicle that is inconsistent with the requested version of the first service request is a grayscale vehicle and that the vehicle that is inconsistent with the requested version of the first service request is a non-grayscale vehicle. And when the execution result is that the execution passes, the first service request is considered to be issued to the gray-scale vehicle.

And S270, sending the first service request to the second vehicle.

For example, in the case where the execution result is that the execution fails, the first service request is transmitted to the second vehicle (as another example of the target vehicle).

The second vehicle is a non-gray-scale vehicle corresponding to the first service request management gray-scale rule in vehicles corresponding to the cloud server.

Specifically, if the execution is not passed, that is, if the execution result is false, the first service request is considered to be issued to the non-gray vehicle, and the first service request can be directly sent to the corresponding non-gray vehicle for execution.

In an implementation of the present application, the grayscale vehicle may also be referred to as a vehicle within the first service request management grayscale rule. That is, the hit range of the first service request management gray rule is a target vehicle which is inconsistent with the version information of the first service request to be issued. A non-gray scale vehicle may also be referred to as a vehicle that is outside the range of the first service request management gray scale rule. That is, the hit range of the first service request management gray rule is the target vehicle which is consistent with the version information of the first service request to be issued.

And S280, sending the first service request to the third vehicle.

For example, in a case where it is determined from the first service request that there is no first service request management gradation rule corresponding to the first service request, the first service request is transmitted to the third vehicle (as another example of the target vehicle). The third vehicle is a vehicle corresponding to the cloud server. That is, if it is determined that there is no first service request management gray rule corresponding to the first service request, it is indicated that the first service request corresponds to all vehicles, and the first service request is sent to all vehicles.

In an implementation manner of the application, the cloud server determines a corresponding first service request management gray scale rule according to the first service request, and if the corresponding first service request gray scale management rule is determined to exist, determines a corresponding rule engine and a rule script, so that the rule engine executes the rule script, and determines a gray scale vehicle and a non-gray scale vehicle based on an execution result. Thus, the target vehicle can be determined based on the different first service request management gray scale rules to enable the first service request to be issued to the appropriate vehicle.

In the implementation manner of the present application, when determining that the first service request is issued to the first vehicle according to the execution result, it is necessary to determine whether to modify the first service request, and the modification of the first service request is mainly performed by determining whether the rule engine modifies the request body information of the first service request in the rule script.

In an implementation of the present application, the grayscale vehicle or the non-grayscale vehicle may specifically be only one vehicle, or may be a vehicle included in a vehicle list, and specifically determined based on the first service request management grayscale rule.

Referring to fig. 3, the vehicle service request management method provided by the implementation manner of the present application further includes the following implementation manner.

S310, the cloud server issues a request.

The cloud server sends a first service request.

S320, judging whether a gray rule meeting the condition exists. If yes, step S330 is executed, and if no, step S410 is executed.

The cloud server queries whether a first service request management gray rule meeting a condition exists according to a request parameter of the first service request.

S330, selecting a gray scale rule engine.

Illustratively, a matching rule engine is selected based on the type of encoding of the gray scale rule.

S340, executing the rule script.

Illustratively, request parameters in the first service request are identified, the request parameters are input to a first service request management gray scale rule, and a rule script is generated according to the first service request management gray scale rule and the request parameters.

S350, judging whether the execution result passes, if yes, executing step S360, and if not, executing step S390.

Illustratively, the rule engine executes the rule script and determines the release policy based on the execution result returned by the rule script.

S360, judging whether the request body is changed, if yes, executing step S370, and if not, executing step S380.

Illustratively, the requestor is a request parameter of a service request (e.g., a first service request) in the rule script, and the cloud server determines whether the rule engine has modified the request parameter in the rule script.

S370, changing the request body.

For example, if the request parameter of the first service request in the rule script is changed, the message content of the first service request (i.e., the request parameter of the first service request) is correspondingly adjusted.

The cloud server obtains a modified first service request by modifying the request parameters of the first service request according to the request parameters in the rule script under the condition that the request parameters in the rule script are modified, and sends the modified first service request to the first vehicle.

Specifically, when the cloud server determines that the version of the issued first service request is different from the vehicle version of the grayscale vehicle, the rule engine is utilized to modify the request parameter of the first service request in the rule script according to the request parameter of the first service request and the vehicle information of the grayscale vehicle, and when the request parameter of the first service request in the rule script is determined to be modified, the cloud server needs to modify the request parameter of the first service request based on the request parameter in the rule script and send the modified first service request to the grayscale vehicle.

In the implementation manner of the application, in the process of executing the rule script, the rule engine determines whether the request parameter in the rule script needs to be modified according to the request parameter of the first service request and the vehicle version information of the gray-scale vehicle, and automatically modifies the request parameter of the first service request in the rule script into a identifiable first service request (i.e. a modified first service request) corresponding to the version information of the gray-scale vehicle under the condition that the request parameter in the rule script needs to be modified is determined, so that the vehicle can normally execute after the first service request is issued to the vehicle.

For example, the request parameters of the first service request are 5, but the version information of the first vehicle is determined to be version 1.0 according to the rule engine, which can only receive 3 request parameters, so the request parameters of the first service request need to be modified to be 3 to adapt to the first vehicle.

In the implementation manner of the application, whether the first service request needs to be regulated or not can be determined according to the determined version type of the vehicle by a dynamic regulation mode, and the rule engine is enabled to modify the rule script according to the attribute information (such as the number of parameters of the received service request and the format information of the received service request) corresponding to the determined version type of the vehicle, so that the cloud server is enabled to modify the first service request based on the modification of the rule script by the rule engine.

Illustratively, the cloud server issues the adjusted service request (i.e., the modified first service request) to a grayscale vehicle (as an example of the first vehicle) that is different from the version information of the original service request (i.e., the first service request), and the grayscale vehicle executes the modified first service request.

Further, in the event that no modification to the request parameters in the rule script is determined, the first service request is sent directly to the first vehicle.

S380, selecting a gray-scale vehicle or a vehicle list.

For example, when the cloud server determines that the request to be issued is a grayscale vehicle with inconsistent request version of the first request service according to the first service request management grayscale rule, the cloud server sends the modified first service request to the grayscale vehicle or the vehicle list, or when it determines that the first service request does not need to be modified, the grayscale vehicle can still normally execute the first service request, the cloud server directly sends the first service request to the grayscale vehicle or the vehicle list.

S390, a non-gray scale vehicle or a list of vehicles is selected.

For example, when the cloud server determines that the request to be issued is a non-gray vehicle or a vehicle list with the same version information as the first service request according to the first service request management gray rule, the first service request is directly sent to the non-gray vehicle or the vehicle list.

S410, a request (e.g., a first service request) is issued to the vehicle.

In the implementation mode of the application, when the cloud server determines that the first service request management gray rule meeting the condition exists, the first service request is determined to be issued to the gray vehicle or the non-gray vehicle according to the execution result of the rule script executed by the rule engine, and when the cloud server determines that the first service request management gray rule meeting the condition does not exist, the first service request is sent to all vehicles.

In the implementation mode of the application, when the versions of the vehicle and the cloud end are released, the gray rule codes are configured according to the version differences of the vehicle and the cloud end, and when the cloud end sends a first service request message to the vehicle, the rule engine is automatically triggered, and the request parameters of the first service request are dynamically changed through judging the content of the request message so that the first service request is matched with the version of the vehicle end.

In an implementation manner of the application, the cloud server determines a corresponding service request management gray scale rule according to the first service request, if the corresponding service request gray scale management rule is determined to exist, a corresponding rule engine and a rule script are determined, so that the rule engine executes the rule script, determines a gray scale vehicle and a non-gray scale vehicle based on an execution result, and modifies request parameters of the first service request according to vehicle version information of the gray scale vehicle when the vehicle is the gray scale vehicle, so that the generated second service request can be identified by the gray scale vehicle, and if the vehicle is the non-gray scale vehicle, the first service request can be issued directly. And if the corresponding first service request management gray scale rule does not exist, issuing the first service request to the vehicle which is registered in the cloud server in advance. Thus, the target vehicle can be determined based on the different first service request management gray scale rules to enable the first service request to be issued to the appropriate vehicle.

And when the corresponding vehicle version is inconsistent with the cloud version, the request parameters of the first service request can be adjusted based on the vehicle version, so that the issued first service request can be executed by the vehicle end, and the problem that the vehicle cannot execute the function of the first service request issued by the cloud when the vehicle version is inconsistent with the cloud version in the prior art is solved. The normal use of the vehicle functions is realized under the condition that the vehicle version and the cloud version are inconsistent.

Further, referring to fig. 4, fig. 4 is a schematic structural diagram of a vehicle service request management device according to an embodiment of the present application. As shown in fig. 4, the vehicle service request management apparatus includes: a first processing module 601, a second processing module 602, a third processing module 603, a fourth processing module 604, and a fifth processing module 605.

A first processing module 601, configured to determine a first service request;

a second processing module 602, configured to determine, when it is determined that a service request management gray rule corresponding to the first service request exists according to the first service request, a corresponding rule engine and rule script according to the first service request management gray rule;

a third processing module 603, configured to execute the rule script according to the rule engine, to obtain an execution result;

The fourth processing module 604 is configured to send the first service request to the corresponding target vehicle according to the execution result.

The vehicle service request management device provided by the embodiment of the application can be used for executing the vehicle service request management method described in the above embodiment, and the implementation principle and technical effects are similar, and are not repeated here.

It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the processing module may be a processing element that is set up separately, may be implemented in a chip of the above-mentioned apparatus, or may be stored in a memory of the above-mentioned apparatus in the form of program codes, and the functions of the above-mentioned processing module may be called and executed by a processing element of the above-mentioned apparatus. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element here may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.

In the implementation mode of the application, the vehicle service request management mode can also be applied to electronic equipment such as mobile terminals and the like. Such as a cell phone, computer, etc.

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 5, the electronic device may include: a transceiver 121, a processor 122, a memory 123.

Processor 122 executes the computer-executable instructions stored in the memory, causing processor 122 to perform the aspects of the embodiments described above. The processor 122 may be a general-purpose processor including a central processing unit CPU, a network processor (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

Memory 123 is coupled to processor 122 via the system bus and communicates with each other, and memory 123 is configured to store computer program instructions.

By way of example, and not limitation, memory 123 may include a Hard Disk Drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or universal serial bus (universal serial bus, USB) drive, or a combination of two or more of these. Memory 123 may include removable or non-removable (or fixed) media as appropriate. Memory 123 may be internal or external to the integrated gateway device, where appropriate. In a particular embodiment, the memory 123 is a non-volatile solid state memory. In a particular embodiment, the memory 123 includes Read Only Memory (ROM). The ROM may be mask programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these, where appropriate.

The transceiver 121 may be used to acquire a task to be run and configuration information of the task to be run.

The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The transceiver is used to enable communication between the database access device and other computers (e.g., clients, read-write libraries, and read-only libraries). The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (non-volatile memory).

The embodiment of the application also provides a chip for running the instruction, which is used for executing the technical scheme of the vehicle service request management method in the embodiment.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions, and when the computer instructions run on a processor of the electronic device, the processor of the electronic device is caused to execute the technical scheme of the vehicle service request management method in the embodiment.

In some possible embodiments, the aspects of the method provided by the present application may also be implemented in the form of a program product, which includes a program code for causing a processor of an electronic device to execute the steps in the method according to the various exemplary embodiments of the present application described in the present specification, when the program product is run on the processor of the electronic device, for example, the electronic device may execute the vehicle service request management method described in the embodiment of the present application.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The implementation manner of the present application also provides a computer program product, which includes a computer program, where the computer program is stored in a computer readable storage medium, and at least one processor may read the computer program from the computer readable storage medium, and the technical solution of the vehicle service request management method in the foregoing embodiment may be implemented when the at least one processor executes the computer program.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable information processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable information processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable information processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable information processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof.

Claims (10)

1. A vehicle service request management method, applied to an electronic device, comprising:

Determining a first service request;

determining a corresponding rule engine and rule script according to the first service request management gray rule under the condition that the first service request management gray rule corresponding to the first service request exists according to the first service request;

executing the rule script according to the rule engine to obtain an execution result;

and sending the first service request to a target vehicle according to the execution result.

2. The vehicle service request management method according to claim 1, characterized in that transmitting the first service request to a target vehicle according to the execution result includes:

if the execution result is that the execution passes, the first service request is sent to a first vehicle, wherein the first vehicle is a gray-scale vehicle corresponding to the first service request management gray-scale rule in vehicles corresponding to the cloud server;

and if the execution result is that the execution fails, the first service request is sent to a second vehicle, wherein the second vehicle is a non-gray-scale vehicle corresponding to the first service request management gray-scale rule in vehicles corresponding to the cloud server.

3. The vehicle service request management method according to claim 2, characterized in that transmitting the first service request to the first vehicle includes:

under the condition that the request parameters in the rule script are confirmed to be modified, the request parameters of the first service request are modified according to the request parameters in the rule script to obtain a modified first service request, and the modified first service request is sent to the first vehicle;

in the event that no modification is determined to exist to the request parameters in the rule script, the first service request is sent directly to the first vehicle.

4. A vehicle service request management method according to claim 2 or 3, characterized in that the method further comprises:

and in the process of executing the rule script by the rule engine, under the condition that the request parameters in the rule script are required to be modified according to the request parameters of the first service request and the vehicle information of the first vehicle, the request parameters in the rule script are modified.

5. The vehicle service request management method according to claim 4, wherein the vehicle information includes vehicle version information and vehicle identification information.

6. The vehicle service request management method according to any one of claims 1 to 5, characterized in that the method further comprises:

and under the condition that the first service request management gray scale rule corresponding to the first service request does not exist according to the first service request, the first service request is sent to a third vehicle, and the third vehicle is the vehicle corresponding to the cloud server.

7. The vehicle service request management method according to any one of claims 1 to 6, wherein determining the corresponding rule engine and rule script according to the first service request management gray scale rule includes:

determining the rule engine according to the compiling type of the first service request management gray rule;

and determining the rule script according to the request parameters included in the first service request and a rule template of the first service request management gray rule.

8. The vehicle service request management method according to claim 7, wherein the request parameters include a request type, a request content, and request version information.

9. The vehicle service request management method according to any one of claims 1 to 8, wherein the first service request management gray scale rule corresponding to the first service request is obtained by:

And determining the first service request management gray rule corresponding to the first service request according to the request type of the first service request and the corresponding relation between the preset request type and the service request management gray rule.

10. A vehicle service request management apparatus, characterized by comprising:

a first processing module for determining a first service request;

the second processing module is used for determining a corresponding rule engine and rule script according to the first service request management gray rule when the first service request management gray rule corresponding to the first service request exists according to the first service request;

the third processing module is used for executing the rule script according to the rule engine to obtain an execution result;

and the fourth processing module is used for sending the first service request to the corresponding target vehicle according to the execution result.