CN111723135A

CN111723135A - Method and device for processing vehicle configuration feature request

Info

Publication number: CN111723135A
Application number: CN201910208594.8A
Authority: CN
Inventors: 卢丽; 谢福俊; 张桢华; 龚浩; 张轩玮; 潘煜俊; 陈凤佳; 郭小敏
Original assignee: SAIC Motor Corp Ltd
Current assignee: SAIC Motor Corp Ltd
Priority date: 2019-03-19
Filing date: 2019-03-19
Publication date: 2020-09-29
Anticipated expiration: 2039-03-19
Also published as: CN111723135B

Abstract

The application discloses a method and a device for processing a vehicle configuration feature request. And combining the configuration feature libraries corresponding to each subsidiary company under the same vehicle company flag to obtain a total feature library of the vehicle company, namely realizing overall management and control of all vehicle configuration features. When each subsidiary or each vehicle configuration item under each subsidiary transmits a configuration feature request, the configuration feature request is processed by using the total feature library of the vehicle company. Because all the vehicle configuration characteristics of the vehicle company are collected to the total characteristic library for overall management and control, when the configuration characteristic request is met, the related configuration characteristics can be rapidly positioned in all the subsidiary companies and the vehicle configuration items, the accurate tracking of the configuration characteristics is realized, and the tracking time is saved. Therefore, the method and the device can avoid confusion when the vehicle configuration feature request is processed, and realize efficient processing of the configuration feature request.

Description

Method and device for processing vehicle configuration feature request

Technical Field

The present application relates to the field of vehicle engineering technologies, and in particular, to a method and an apparatus for processing a vehicle configuration feature request.

Background

At present, when a plurality of subsidiaries of a vehicle company develop vehicle-related projects, vehicle configurations related to the projects are independently controlled by the interior of the projects, and feature information of the vehicle configurations is not communicated with each other. However, in practical applications, names of the same configuration feature in different projects or different subsidiaries may differ, thereby causing confusion in configuration data management. For example, when a problem is found in a configuration feature a in a certain project, since the configuration feature a is named as configuration feature a' in other projects of the sub-company and is named as configuration feature B in other sub-companies of the main company, the same problem configuration feature cannot be accurately tracked.

It can be seen that the current vehicle configuration data is independently managed and controlled, which causes the accuracy and traceability of the configuration features to be very poor, and the request of the vehicle configuration features is easily confused when being processed.

Disclosure of Invention

Based on the above problems, the present application provides a method and an apparatus for processing a vehicle configuration feature request, so as to implement accurate tracking of a configuration feature and solve a problem of confusion when a vehicle configuration feature request is processed.

The embodiment of the application discloses the following technical scheme:

in a first aspect of the present application, a method for processing a vehicle configuration feature request is provided, including:

acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag;

merging the configuration feature libraries corresponding to each subsidiary company into a total feature library;

and processing a configuration feature request sent by each subsidiary or each vehicle configuration item under each subsidiary by using the total feature library.

Optionally, the obtaining of the configuration feature library corresponding to each subsidiary company under the same vehicle company flag specifically includes:

judging whether each subsidiary company has a corresponding configuration feature library, and if so, acquiring the configuration feature library corresponding to the subsidiary company; if not, all vehicle configurations used by each vehicle configuration project under the subsidiary company are obtained, and a configuration feature library corresponding to the subsidiary company is established according to all the vehicle configurations.

Optionally, the merging the configuration feature libraries corresponding to each of the subsidiaries into a total feature library specifically includes:

obtaining the description and the code of each configuration feature in a configuration feature library corresponding to each subsidiary company;

determining the mutually overlapped configuration characteristics in the configuration characteristic libraries corresponding to different subsidiaries by using the description and/or the code; the mutually overlapping configuration features have the unique code;

and acquiring a union set of various configuration characteristics in a configuration characteristic library corresponding to each subsidiary company to obtain the total characteristic library, wherein the various configuration characteristics in the total characteristic library are not overlapped with each other.

Optionally, the configuration feature request is specifically a configuration feature addition request, and the configuration feature addition request carries associated data of the configuration feature requested to be added;

the processing, by using the total feature library, the configuration feature request sent by each subsidiary or each vehicle configuration item under each subsidiary specifically includes:

determining that the associated data of the newly added configuration features meets the preliminary checking condition;

for a configuration feature adding request sent by each subsidiary company, judging whether the total feature library contains the configuration features requested to be added according to the associated data of the configuration features requested to be added, if so, sending a notification for continuing to use the configuration features requested to be added contained in the total feature library to the subsidiary company; if not, adding the configuration features requested to be added in the configuration feature library corresponding to the subsidiary and the total feature library, and sending a notification of completion of addition of the configuration features to the subsidiary;

for configuration feature adding requests sent by vehicle configuration items of each subsidiary company, judging whether the configuration feature library corresponding to the subsidiary company to which the vehicle configuration items belong contains the configuration features requested to be added according to the associated data of the configuration features requested to be added, and if so, sending a notification for continuing to use the configuration features requested to be added contained in the configuration feature library to the vehicle configuration items; if not, judging whether the total feature library contains the configuration feature requested to be newly added according to the associated data of the configuration feature requested to be newly added, and if so, sending a notification for continuing to use the configuration feature requested to be newly added contained in the total feature library to the vehicle configuration project; and if not, adding the configuration features requested to be newly added into the configuration feature library corresponding to the subsidiary company to which the vehicle configuration item belongs and the total feature library, and sending a notification of completion of newly adding the configuration features to the vehicle configuration item.

Optionally, the configuration feature request is specifically a configuration feature modification request, and the configuration feature modification request carries associated data of the configuration feature requested to be modified;

determining that the associated data of the configuration features requested to be modified meets a preliminary checking condition;

determining all the subsidiaries of the vehicle company using the configuration feature requested to be modified and the vehicle configuration items according to the associated data of the configuration feature requested to be modified;

forwarding the configuration feature modification request to all of the subsidiaries and the vehicle configuration items that use the configuration feature requested to be modified;

and obtaining feedback information of all the subsidiaries using the configuration feature requested to be modified and the vehicle configuration item, and modifying the configuration feature requested to be modified in the configuration feature library corresponding to all the subsidiaries using the configuration feature requested to be modified and the total feature library when all the subsidiaries using the configuration feature requested to be modified and the vehicle configuration item agree with the configuration feature modification request.

Optionally, the configuration feature request is specifically a configuration feature deletion request, and the configuration feature deletion request carries associated data of the configuration feature requested to be deleted;

determining that the associated data of the configuration characteristics requested to be deleted meet a preliminary checking condition;

determining whether the vehicle company has the vehicle configuration item using the configuration feature requested to be deleted according to the associated data of the configuration feature requested to be deleted;

and if not, deleting the configuration characteristics requested to be deleted from the total characteristic library and all the configuration characteristic libraries containing the configuration characteristics requested to be deleted.

In a second aspect of the present application, there is provided a processing apparatus for a vehicle configuration feature request, including:

the system comprises a configuration feature library acquisition module, a configuration feature library analysis module and a configuration feature library analysis module, wherein the configuration feature library acquisition module is used for acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag;

the feature library merging module is used for merging the configuration feature libraries corresponding to the sub-companies into a total feature library;

and the configuration feature request processing module is used for processing the configuration feature request sent by each subsidiary or each vehicle configuration item under each subsidiary by using the total feature library.

Optionally, the configuration feature library obtaining module specifically includes:

the system comprises a first judging unit, a first obtaining unit, a second obtaining unit and a configuration feature library establishing unit;

the first judging unit is used for judging whether each subsidiary company has a corresponding configuration feature library, and if so, the first acquiring unit is used for acquiring the configuration feature library corresponding to the subsidiary company; if not, the second obtaining unit is used for obtaining all vehicle configurations used by each vehicle configuration item under the subsidiary company, and the configuration feature library establishing unit is used for establishing a configuration feature library corresponding to the subsidiary company according to all the vehicle configurations.

Optionally, the feature library merging module specifically includes:

a third obtaining unit, a first determining unit and a merging unit;

the third obtaining unit is configured to obtain descriptions and codes of various configuration features in a configuration feature library corresponding to each subsidiary company;

the first determining unit is used for determining the mutually overlapped configuration characteristics in the configuration characteristic libraries corresponding to different subsidiaries by using the description and/or the code; the mutually overlapping configuration features have the unique code;

the merging unit is configured to obtain a union set for each configuration feature in the configuration feature library corresponding to each subsidiary company, to obtain the total feature library, where each configuration feature in the total feature library is not overlapped with each other.

the configuration feature request processing module specifically includes:

a second determination unit, a first processing unit and a second processing unit;

the second determining unit is configured to determine that the associated data of the configuration feature requested to be newly added meets a preliminary checking condition;

the first processing unit is configured to, for a configuration feature addition request sent by each of the subsidiaries, determine, according to associated data of the configuration feature addition request, whether the total feature library includes the configuration feature addition request, and if so, send a notification to the subsidiaries to continue using the configuration feature addition request included in the total feature library; if not, adding the configuration features requested to be added in the configuration feature library corresponding to the subsidiary and the total feature library, and sending a notification of completion of addition of the configuration features to the subsidiary;

the second processing unit is configured to, for a configuration feature addition request sent by each vehicle configuration item of each of the subsidiaries, determine, according to the associated data of the configuration feature addition request, whether a configuration feature library corresponding to the subsidiary to which the vehicle configuration item belongs includes the configuration feature addition request, and if so, send a notification to the vehicle configuration item to continue using the configuration feature addition request included in the configuration feature library; if not, judging whether the total feature library contains the configuration feature requested to be newly added according to the associated data of the configuration feature requested to be newly added, and if so, sending a notification for continuing to use the configuration feature requested to be newly added contained in the total feature library to the vehicle configuration project; and if not, adding the configuration features requested to be newly added into the configuration feature library corresponding to the subsidiary company to which the vehicle configuration item belongs and the total feature library, and sending a notification of completion of newly adding the configuration features to the subsidiary company.

the configuration feature request processing module specifically includes:

the system comprises a third determining unit, a fourth determining unit, a forwarding unit, a fourth acquiring unit and a third processing unit;

the third determining unit is configured to determine that the associated data of the configuration feature requested to be modified meets a preliminary checking condition;

the fourth determining unit is used for determining all the subsidiaries using the configuration characteristics requested to be modified and the vehicle configuration items of the vehicle company according to the associated data of the configuration characteristics requested to be modified;

a forwarding unit, configured to forward the configuration feature modification request to all the subsidiaries and the vehicle configuration items using the configuration feature requested to be modified;

the fourth obtaining unit is used for obtaining the messages fed back by all the subsidiaries using the configuration features requested to be modified and the vehicle configuration items;

the third processing unit is configured to modify the configuration feature requested to be modified in the configuration feature library corresponding to the subsidiary using the configuration feature requested to be modified and the total feature library when the subsidiary using all the configuration features requested to be modified and the vehicle configuration item agree with the configuration feature modification request.

the configuration feature request processing module specifically includes:

a fifth determining unit, a sixth determining unit and a fourth processing unit;

the fifth determining unit is configured to determine that the associated data of the configuration feature requested to be deleted meets a preliminary checking condition;

the sixth determining unit is used for determining whether the vehicle company has the vehicle configuration item using the configuration feature requested to be deleted according to the associated data of the configuration feature requested to be deleted;

if not, the fourth processing unit is configured to delete the configuration feature requested to be deleted from the total feature library and all feature libraries including the configuration feature requested to be deleted.

Compared with the prior art, the method has the following beneficial effects:

according to the vehicle configuration feature request processing method, the configuration feature libraries corresponding to each subsidiary company under the same vehicle company flag are combined to obtain the total feature library of the vehicle company, and overall management and control over all vehicle configuration features are achieved. When each subsidiary or each vehicle configuration item under each subsidiary transmits a configuration feature request, the configuration feature request is processed by using the total feature library of the vehicle company. Because all the vehicle configuration characteristics of the vehicle company are collected to the total characteristic library for overall management and control, when the configuration characteristic request is met, the related configuration characteristics can be rapidly positioned in all the subsidiary companies and the vehicle configuration items, the accurate tracking of the configuration characteristics is realized, and the tracking time is saved. Therefore, the method can avoid confusion in processing the vehicle configuration feature request and realize efficient processing of the configuration feature request.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is a flowchart of a processing method for a vehicle configuration feature request according to an embodiment of the present application;

FIG. 2 is a flow chart of another method for processing a vehicle configuration feature request provided by an embodiment of the present application;

FIG. 3 is a flow chart of yet another method for processing a vehicle configuration feature request provided by an embodiment of the present application;

FIG. 4 is a flow chart of yet another method for processing a vehicle configuration feature request according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a processing device for a vehicle configuration feature request according to an embodiment of the present application.

Detailed Description

As described above, configuration data of a plurality of vehicle companies are not circulated among subsidiaries, and a plurality of subsidiaries do not establish a configuration feature library for each vehicle configuration project developed in the company, and the project independently manages configuration data related to the project. This causes the accuracy and traceability of the arrangement characteristics to be extremely poor, and the vehicle arrangement characteristic request is likely to be confused when processed.

In view of the above problem, the inventors have studied and provided a method and an apparatus for processing a vehicle configuration feature request, which can accurately track configuration features by comprehensively managing and controlling the configuration features of the respective vehicle configuration items of the subsidiary company and the subsidiary company, thereby solving the problem of confusion in processing the vehicle configuration feature request.

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

First embodiment

Referring to fig. 1, the figure is a flowchart of a processing method for a vehicle configuration feature request according to an embodiment of the present application.

As shown in fig. 1, a method for processing a vehicle configuration feature request provided in an embodiment of the present application includes:

step 101: and acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag.

For a vehicle, the configuration may specifically include various information such as configuration characteristics and binding relationships. To facilitate understanding of the meaning of the configuration features, the configuration features are exemplified below.

As an example, the body color includes blue, white, black, and the like, wherein the body color is referred to as a feature family, and the blue, white, and black are different configuration features in the feature family. As another example, there are ten thousand power, korean tai, etc. tire brands for vehicles, where a tire brand is referred to as a feature family, and ten thousand power, korean tai are respectively different configuration features under the feature family.

It will be appreciated that the above are merely examples of configuration features and that many other configuration features may be included in a practical application and are not necessarily enumerated herein.

It can be understood that, in practical applications, each subsidiary may develop at least one vehicle configuration item, and therefore, in this embodiment, the configuration feature library corresponding to the subsidiary includes configuration features related to all vehicle configuration items developed by the subsidiary. However, there may be a difference in the case where a subsidiary company under its flag establishes a configuration feature library for each vehicle company. Three possible scenarios for the vehicle company to build a library of configuration features for subsidiaries are provided below:

1) all the subsidiaries are established with corresponding configuration feature libraries of the subsidiaries.

2) In all the subsidiaries, only a part of the subsidiaries are established with the configuration feature library corresponding to the subsidiaries, and the other subsidiaries are not established with the configuration feature library corresponding to the subsidiaries.

3) And all the subsidiaries do not establish the corresponding configuration feature library of the subsidiaries.

In this step, in order to obtain the configuration feature corresponding to each sub-company under the flag of the vehicle company, it is necessary to obtain all the vehicle configurations used by each vehicle configuration item under the sub-company that does not establish the configuration feature library corresponding to the sub-company, and then establish the configuration feature library corresponding to the sub-company according to all the vehicle configurations, for the cases of the above 2 nd and 3 rd cases.

Therefore, in the specific implementation of this step, it may be determined whether each of the subsidiaries has a corresponding configuration feature library, so as to determine the establishment of the configuration feature library. If so, acquiring a configuration feature library corresponding to the subsidiary company; if not, all vehicle configurations used by each vehicle configuration project under the subsidiary company are obtained, and a configuration feature library corresponding to the subsidiary company is established according to all the vehicle configurations.

By executing the operations, the configuration feature library corresponding to each subsidiary company under the same vehicle company flag can be obtained.

Step 102: and merging the configuration feature libraries corresponding to each subsidiary into a total feature library.

In this step, when the configuration feature libraries corresponding to the respective subsidiaries are merged, the configuration feature libraries corresponding to the respective subsidiaries are not simply summed up. This is because the configuration feature libraries corresponding to different subsidiaries are likely to contain the same configuration features. These configuration features may be identical in nature, but with some differences in the data that are relevant. For example, the Chinese description of the same configuration feature in the configuration feature library corresponding to the subsidiary company A is a first description, and the Chinese description in the configuration feature library corresponding to the subsidiary company B is a second description; the english Description of the same configuration feature in the configuration feature library corresponding to the subsidiary a is Description _1, and the english Description in the configuration feature library corresponding to the subsidiary B is Description _ 2.

Obviously, the configuration features which are identical in nature but slightly different in related data are respectively recorded in the total feature library, which is likely to cause data redundancy, and meanwhile, the data storage capacity is large, the memory burden is too high, so that the performance is low when the configuration feature request is processed, and the processing speed is too slow. For this reason, duplicate removal may be performed on configuration features that are substantially the same in configuration feature libraries corresponding to different subsidiaries, that is, overlapping configuration features are removed, and only one of the configuration features and its related data are retained and incorporated into the total feature library. In this way, in the final obtained total feature library, the configuration features do not overlap with each other. Therefore, the data redundancy in the total feature library can be effectively avoided, and the processing speed of the configuration feature request is improved.

In a specific implementation, this step 102 may be implemented by performing S1021 to S1023 described below.

S1021: and obtaining the description and the code of each configuration feature in the configuration feature library corresponding to each subsidiary company.

It should be noted that the description of the configuration features includes: english description and/or chinese description.

S1022: and determining the mutually overlapped configuration characteristics in the configuration characteristic libraries corresponding to different subsidiaries by using the description and/or the codes.

It should be noted that the mutually overlapping configuration features have unique codes. That is, even if there is a difference in description in the configuration feature library corresponding to different subsidiaries, the code (code) of the configuration feature that is substantially the same in different configuration feature libraries is uniquely determined. Therefore, the overlapped configuration features in different configuration feature libraries can be determined only according to the codes.

In addition, the configuration features overlapping with each other may be determined only by the description of the configuration features. For example, characters or characters in the description may be recognized, the recognition results are used to match the configuration features in different configuration feature libraries, the similarity of the recognition results is compared, and if the similarity of the recognition results is greater than a preset similarity threshold, it may be determined that the successfully matched configuration features in different configuration feature libraries are mutually overlapped configuration features. It should be understood that the above is only an exemplary implementation manner for determining the configuration features overlapping with each other through the description, and in practical applications, other means may also be used for determining the configuration features overlapping with each other through the description, and the implementation manner is not particularly limited herein.

S1023: and acquiring a union set of various configuration characteristics in a configuration characteristic library corresponding to each subsidiary company to obtain the total characteristic library, wherein the various configuration characteristics in the total characteristic library are not overlapped with each other.

Step 103: and processing a configuration feature request sent by each subsidiary or each vehicle configuration item under each subsidiary by using the total feature library.

In this embodiment, the configuration feature request may specifically be a configuration feature addition request, that is, a request for adding one or more configuration features to a subsidiary company or a vehicle configuration project; or a configuration feature modification request, i.e. a request for modification of one or more configuration features by a subsidiary or vehicle configuration item; it may also be a configuration feature deletion request, i.e. a sub-company or vehicle configuration item requesting the deletion of one or more configuration features. In this embodiment, the specific type of the configuration feature request is not limited.

The above is a processing method of the vehicle configuration feature request provided in the embodiment of the present application. According to the method, the configuration feature libraries corresponding to each subsidiary company under the same vehicle company flag are combined to obtain the total feature library of the vehicle company, namely the overall management and control of all vehicle configuration features are realized. When each subsidiary or each vehicle configuration item under each subsidiary transmits a configuration feature request, the configuration feature request is processed by using the total feature library of the vehicle company. Because all the vehicle configuration characteristics of the vehicle company are collected to the total characteristic library for overall management and control, when the configuration characteristic request is met, the related configuration characteristics can be rapidly positioned in all the subsidiary companies and the vehicle configuration items, the accurate tracking of the configuration characteristics is realized, and the tracking time is saved. Therefore, the method can avoid confusion in processing the vehicle configuration feature request and realize efficient processing of the configuration feature request.

To facilitate understanding of the differences in processing for different types of configuration feature requests, the following describes specific processing manners of three different types of configuration feature requests by using three embodiments.

Second embodiment

Referring to fig. 2, the figure is a flowchart of another processing method for a vehicle configuration feature request according to an embodiment of the present application.

As shown in fig. 2, the present embodiment provides a method for processing a vehicle configuration feature request, which is used to process a configuration feature addition request. The method comprises the following steps:

step 201: and acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag.

Step 202: and merging the configuration feature libraries corresponding to each subsidiary into a total feature library.

In this embodiment, the implementation manners of

steps

201 and 202 are the same as the implementation manners of

steps

101 and 102 in the foregoing embodiment, and reference may be made to the foregoing embodiment for the related description of

steps

201 and 202, which is not described herein again.

Step 203: and determining that the associated data of the configuration features requested to be newly added meets the preliminary checking condition. If the configuration feature addition request is sent by a subsidiary, go to step 204; if the configuration feature addition request is sent by a vehicle configuration item under a subsidiary, step 205 is performed.

For a received configuration feature addition request, a preliminary check needs to be performed on the request. In this embodiment, the configuration feature addition request carries associated data of the configuration feature requested to be added. The associated data includes: and requesting Chinese description, English description and coding of the newly added configuration features, which are all necessary to be contained in the associated data. Of course, the associated data may also include other data besides the above three, and is not limited herein.

As a possible implementation manner, it is determined whether the associated data of the configuration feature requested to be newly added meets the preliminary check condition, specifically, it is determined whether the configuration feature newly addition request completely carries the chinese description, the english description, and the code of the configuration feature requested to be newly added, and whether the configuration feature library in the subsidiary company contains the configuration feature that is the same as the feature family of the configuration feature requested to be newly added but has the same chinese description or english description. And determining that the associated data of the configuration features requested to be newly added meets the preliminary check condition only when the Chinese description, the English description and the code of the configuration features requested to be newly added are completely carried in the configuration feature newly-added request, and the configuration feature library in the subsidiary company does not contain the configuration features which are the same as the feature family requested to be newly added but are the same as the Chinese description or the English description.

For the newly added configuration features meeting the preliminary checking condition, a main body for further explicitly sending the newly added configuration feature request is also needed. The body of the request is sent with two possibilities, one is sent by the subsidiary and the other is sent by the vehicle configuration item under the subsidiary. For the two possible topics, the former sent request may be processed in step 204, and the latter sent request may be processed in step 205.

Step 204: judging whether the total feature library contains the configuration feature requested to be newly added according to the associated data of the configuration feature requested to be newly added, if so, executing step 206; if not, step 207 is performed.

In this embodiment, the default configuration feature adding request from the subsidiary company has been that the configuration feature library corresponding to the subsidiary company has been queried in advance in the configuration feature library corresponding to the subsidiary company that does not include the configuration feature added by the request. Step 204, when executed, may determine whether the total feature library already contains the configuration feature that is requested to be added, by using at least one of the following associated data:

requesting a chinese description, english description, or encoding of the newly added configuration feature.

For example, whether the configuration features consistent with the configuration feature code requested to be newly added exist in the total feature library or not is searched, whether the configuration features matched with the recognition result of the Chinese/English description of the configuration features requested to be newly added exist in the total feature library or not is searched, and the like. Obviously, if the configuration feature requested to be newly added is already contained in the total feature library, the configuration feature in the total feature library may be directly used, so that the notification of using the configuration feature requested to be newly added contained in the total feature library may be sent to the subsidiary company by executing step 206, so that the subsidiary company calls the configuration feature requested to be newly added. If the total feature library does not include the configuration feature requested to be added, the configuration feature needs to be added in the total feature library and the configuration feature library corresponding to the requested subsidiary, and the subsidiary is notified in time after the addition is completed, so that the call is facilitated, see step 207.

Step 205: judging whether the configuration feature library corresponding to the subsidiary company to which the vehicle configuration project belongs contains the configuration feature requested to be newly added according to the associated data of the configuration feature requested to be newly added, if so, executing step 208; if not, step 209 is performed.

Different from the case that the main body of the request is the sub-company, since the main body of the request is a certain vehicle configuration item under the sub-company, and since the configuration features used by each vehicle configuration item in the sub-company are not shared and not communicated, it is first necessary to confirm whether the configuration feature library corresponding to the sub-company to which the request is added includes the configuration feature requested to be added. The specific confirmation method is similar to the foregoing step 204, that is, whether the configuration feature library corresponding to the subsidiary company has the configuration feature whose associated data matches the associated data of the configuration feature requested to be newly added, if yes, it indicates that the configuration feature requested to be newly added included in the configuration feature library can be used, see step 208, if not, the total feature library is also queried, and it is further confirmed whether the configuration feature library includes the configuration feature whose associated data matches the associated data of the configuration feature requested to be newly added, see step 209.

Step 206: sending a notification to the subsidiary to continue using the newly-requested configuration feature included in the master feature library.

Step 207: and adding the configuration features requested to be newly added into the configuration feature library corresponding to the subsidiary company and the total feature library, and sending a notification of completion of the newly added configuration features to the subsidiary company.

Step 208: sending a notification to the vehicle configuration item to continue using the newly-requested configuration feature included in the configuration feature library.

Step 209: judging whether the total feature library contains the configuration feature requested to be newly added according to the associated data of the configuration feature requested to be newly added, if so, executing step 210; if not, step 211 is performed.

Step 210: sending a notification to the vehicle configuration item to follow up the newly-added configuration feature requested included in the total feature library.

Step 211: and adding the configuration features requested to be newly added into the configuration feature library corresponding to the subsidiary company to which the vehicle configuration item belongs and the total feature library, and sending a notification of completion of newly adding the configuration features to the vehicle configuration item.

The above is another processing method for a vehicle configuration feature request provided in the embodiment of the present application. The method takes the example that the configuration feature request is a configuration feature newly-added request as an explanation, and the specific processing flow of the request is explained in detail.

A specific processing manner in which the configuration feature request is a configuration feature modification request will be described below with reference to the third embodiment.

Third embodiment

Referring to fig. 3, the figure is a flowchart of a processing method for a vehicle configuration feature request according to an embodiment of the present application.

As shown in fig. 3, the present embodiment provides a method for processing a request for modifying a configuration feature of a vehicle. The method comprises the following steps:

step 301: and acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag.

Step 302: and merging the configuration feature libraries corresponding to each subsidiary into a total feature library.

In this embodiment, the implementation manners of

steps

301 and 302 are the same as the implementation manners of

steps

101 and 102 in the foregoing embodiment, and reference may be made to the foregoing embodiment for the related descriptions of

steps

301 and 302, which is not described herein again.

Step 303: and determining that the associated data of the configuration features requested to be modified meet the preliminary checking condition.

The configuration feature modification request carries associated data of the configuration feature requested to be modified.

Similarly to the second embodiment, after obtaining the configuration feature modification request, it is first necessary to perform a preliminary check on the associated data of the configuration feature requested to be modified in the request. It should be noted that, in this embodiment, because the configuration feature modification request needs to be processed, the preliminary check condition may be different from the preliminary check condition when the configuration feature newly-added request is processed.

In this embodiment, as an exemplary implementation manner, the preliminary checking condition includes: the configuration characteristic modification request completely carries Chinese description, English description and code of the configuration characteristic requested to be modified.

Step 304: and determining all the subsidiary companies and the vehicle configuration items of the vehicle company using the configuration feature requested to be modified according to the associated data of the configuration feature requested to be modified.

If a configuration feature is modified, the normal use of the configuration feature by a user is affected if the user of the configuration feature other than the subject of the modification request is unknown. To avoid this problem, this step first identifies all of the subsidiaries and the vehicle configuration items that use the configuration feature that the request is to modify.

Step 305: forwarding the configuration feature modification request to all of the subsidiaries and the vehicle configuration items that use the configuration feature requested to be modified.

The configuration feature modification request is forwarded so that all users of this configuration feature are made aware of the specific request content of the request sender. It will be appreciated that the recipient, upon receiving this forwarded request, may feed back a message granting the modification or countering the modification. And then, the message of the multi-party feedback is synthesized to finally process the configuration characteristic modification request.

Step 306: and obtaining feedback information of all the subsidiaries using the configuration feature requested to be modified and the vehicle configuration item, and modifying the configuration feature requested to be modified in the configuration feature library corresponding to all the subsidiaries using the configuration feature requested to be modified and the total feature library when all the subsidiaries using the configuration feature requested to be modified and the vehicle configuration item agree with the configuration feature modification request.

Since the configuration feature is modified in the configuration feature library corresponding to the subsidiary using the configuration feature requested to be modified and the master feature library only when all the subsidiary using the configuration feature requested to be modified and the vehicle configuration item agree with the configuration feature modification request, even if the configuration feature is modified, the use experience of the user is not affected, and the problem of changing the configuration feature under the condition of the position of the user is avoided.

The above is another processing method for a vehicle configuration feature request provided in the embodiment of the present application. The method takes the configuration feature request as an example for explanation, and the specific processing flow of the request is explained in detail.

A specific processing manner in which the configuration feature request is a configuration feature deletion request will be described below with reference to the fourth embodiment.

Fourth embodiment

Referring to fig. 4, the present application provides a flowchart of a processing method for a vehicle configuration feature request according to another embodiment of the present application.

As shown in fig. 4, the present embodiment provides a method for processing a request for deleting a configuration feature of a vehicle. The method comprises the following steps:

step 401: and acquiring a configuration feature library corresponding to each subsidiary company under the same vehicle company flag.

Step 402: and merging the configuration feature libraries corresponding to each subsidiary into a total feature library.

In this embodiment, the implementation manners of

steps

401 and 402 are the same as the implementation manners of

steps

401 and 402, which is not described herein again.

Step 403: and determining that the associated data of the configuration characteristics requested to be deleted meet the preliminary checking condition.

The configuration feature deleting request carries the associated data of the configuration feature requested to be deleted.

Similarly to the foregoing second and third embodiments, after obtaining the configuration feature deletion request, it is also necessary to perform a preliminary check on the associated data of the configuration feature requested to be deleted in the request. It should be noted that, in this embodiment, because the configuration feature deletion request needs to be processed, the preliminary check condition may be different from the preliminary check condition when the configuration feature addition request is processed.

In this embodiment, as an exemplary implementation manner, the preliminary checking condition includes: the configuration characteristic deleting request completely carries Chinese description, English description and code of the configuration characteristic requested to be deleted.

Step 404: determining whether the vehicle company has the vehicle configuration item using the configuration feature requested to be deleted according to the associated data of the configuration feature requested to be deleted; if not, step 405 is performed.

It will be appreciated that if there is a vehicle configuration item currently using a configuration feature that is requested to be deleted, it is clear that deleting this configuration feature will result in the vehicle configuration item not being able to be properly deployed, and therefore it is necessary to first determine whether there is a user of the configuration feature, thereby avoiding this problem.

Step 405: and deleting the configuration feature requested to be deleted from the total feature library and all configuration feature libraries containing the configuration feature requested to be deleted.

Since it has been confirmed in advance through step 404 that there is no vehicle configuration item currently using the configuration feature requested to be deleted, it is possible to smoothly delete the configuration feature directly in the total feature library and all the configuration feature libraries containing the configuration feature. This deletion operation will not affect the use of any subsidiary or vehicle configuration items.

The above is another processing method for a vehicle configuration feature request provided in the embodiment of the present application. The method takes the example that the configuration feature request is a configuration feature deletion request as an explanation, and the specific processing flow of the request is explained in detail.

It should be noted that, in the second, third, and fourth embodiments, the preliminary check is performed on the different types of configuration feature requests by using the preliminary check condition, and only when the preliminary check condition is met, the subsequent request processing flow is executed. In practical application, there may be some configuration feature requests that do not meet the preliminary verification condition, and for these requests, a notification that the request fails the preliminary verification may be fed back to the request sender so that the sender knows, and then modifies the configuration feature request according to the notification, and resends the configuration feature request to perform the subsequent preliminary verification again.

Based on the processing method of the vehicle configuration feature request provided by the foregoing embodiment, correspondingly, the application further provides a processing device of the vehicle configuration feature request. The following describes in detail a specific implementation of the device in conjunction with embodiments and the accompanying drawings.

Fifth embodiment

Referring to fig. 5, the diagram is a schematic structural diagram of a processing device for a vehicle configuration feature request according to an embodiment of the present application.

As shown in fig. 5, a processing device for a vehicle configuration feature request provided in an embodiment of the present application includes:

a configuration feature library obtaining module 501, configured to obtain a configuration feature library corresponding to each sub-company under the same vehicle company flag;

a feature library merging module 502, configured to merge the configuration feature libraries corresponding to each of the subsidiaries into a total feature library;

a configuration feature request processing module 503, configured to process, by using the total feature library, a configuration feature request sent by each of the subsidiaries or the vehicle configuration items under each of the subsidiaries.

The device is a processing device for the vehicle configuration feature request provided by the application, and the device merges the configuration feature libraries corresponding to each subsidiary company under the same vehicle company flag to obtain the total feature library of the vehicle company, namely, the overall management and control of all vehicle configuration features are realized. When each subsidiary or each vehicle configuration item under each subsidiary transmits a configuration feature request, the configuration feature request is processed by using the total feature library of the vehicle company. Because all the vehicle configuration characteristics of the vehicle company are collected to the total characteristic library for overall management and control, when the configuration characteristic request is met, the related configuration characteristics can be rapidly positioned in all the subsidiary companies and the vehicle configuration items, the accurate tracking of the configuration characteristics is realized, and the tracking time is saved. Therefore, the device can avoid confusion when the vehicle configuration feature request is processed, and realize efficient processing of the configuration feature request.

Optionally, the configuration feature library obtaining module 501 specifically includes:

Optionally, the feature library merging module 502 specifically includes:

a third obtaining unit, a first determining unit and a merging unit;

A possible implementation manner of the configuration feature request processing module 503 is described below by taking the configuration feature request as an example, specifically, a configuration feature adding request.

Optionally, the configuration feature addition request carries associated data of the configuration feature requested to be added;

the configuration feature request processing module 503 specifically includes:

Another possible implementation manner of the configuration feature request processing module 503 is described below by taking the configuration feature request as an example, specifically, the configuration feature modification request.

Optionally, the configuration feature modification request carries associated data of the configuration feature requested to be modified;

the configuration feature request processing module 503 specifically includes:

Next, taking the configuration feature request as an example, specifically, a configuration feature deletion request, a still another possible implementation manner of the configuration feature request processing module 503 is described.

Optionally, the configuration feature deletion request carries associated data of the configuration feature requested to be deleted;

the configuration feature request processing module 503 specifically includes:

It should be noted that, in the present specification, all the embodiments are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus and system embodiments, since they are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts suggested as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for processing a vehicle configuration feature request, comprising:

2. The method according to claim 1, wherein the obtaining of the configuration feature library corresponding to each subsidiary company under the same vehicle company flag specifically comprises:

3. The method according to claim 1, wherein the merging the configuration feature libraries corresponding to each of the subsidiaries into a total feature library specifically comprises:

4. The method according to any one of claims 1 to 3, wherein the request for configuration feature is specifically a request for configuration feature addition, and the request for configuration feature addition carries associated data of configuration features requested to be added;

5. The method according to any one of claims 1 to 3, wherein the configuration feature request is specifically a configuration feature modification request, and the configuration feature modification request carries associated data of a configuration feature requested to be modified;

6. The method according to any one of claims 1 to 3, wherein the configuration feature request is specifically a configuration feature deletion request, and the configuration feature deletion request carries associated data of the configuration feature requested to be deleted;

7. A device for processing a vehicle configuration feature request, comprising:

8. The apparatus according to claim 7, wherein the configuration feature library obtaining module specifically includes:

9. The apparatus according to claim 7, wherein the feature library merging module specifically includes:

a third obtaining unit, a first determining unit and a merging unit;

10. The apparatus according to any one of claims 7 to 9, wherein the configuration feature request is specifically a configuration feature addition request, and the configuration feature addition request carries associated data of a configuration feature requested to be added;

the configuration feature request processing module specifically includes: