CN117931266A

CN117931266A - Software version management method, device and system

Info

Publication number: CN117931266A
Application number: CN202310934774.0A
Authority: CN
Inventors: 蒋京哲; 夏雪妍
Original assignee: Xiaomi Automobile Technology Co Ltd
Current assignee: Xiaomi Automobile Technology Co Ltd
Priority date: 2023-07-27
Filing date: 2023-07-27
Publication date: 2024-04-26

Abstract

The present disclosure relates to a software version management method, device and system, wherein the method comprises: the control equipment acquires first software version information used by a target vehicle; comparing the first software version information with second software version information of control equipment; and determining a version management method based on a compatibility relation between the first software version information and the second software version information when the first software version information and the second software version information are different. Thus, the problems of failure or abnormality of response of the control request and the like caused by inconsistent software versions installed by the control equipment and the vehicle in the related art can be solved.

Description

Software version management method, device and system

Technical Field

The disclosure relates to the technical field of vehicles, and in particular relates to a software version management method, device and system.

Background

Along with the continuous improvement of the level of vehicle intellectualization and networking, terminal equipment (such as a user mobile phone) and vehicles are provided with corresponding Application software (APP), and users can send vehicle control instructions to the vehicles through the software so as to realize remote control of the vehicles. However, due to the continuous update of the software technology, the software version installed in the terminal device is inconsistent with the software version installed in the vehicle, so that incompatibility of the software version, for example, occurs, and the vehicle production or control problem is caused, so that the use experience of the vehicle is affected. Therefore, how to manage the software version of the software installed in different devices is an important problem that needs to be solved at present.

Disclosure of Invention

In order to overcome the problems in the related art, the present disclosure provides a method, an apparatus and a system for managing a software version, so as to solve the problems in the related art, such as incompatibility of the software version caused by inconsistent software version installed by a terminal device and the software version installed by a vehicle, vehicle generation or control problem, influence on the use experience of the vehicle, and the like.

According to a first aspect of embodiments of the present disclosure, there is provided a software version management method, the method including:

Acquiring first software version information used by a target vehicle;

comparing the first software version information with second software version information of control equipment;

And determining a version management method based on a compatibility relation between the first software version information and the second software version information when the first software version information and the second software version information are different.

In some embodiments, the method further comprises:

and when the first software version information and the second software version information are the same, sending a control request for the target vehicle.

In some embodiments, the determining a version management method based on a compatibility relationship between the first software version information and the second software version information includes:

When the compatibility relation is that the first software version information and the second software version information are not compatible, a control request is sent to a server, and response information corresponding to the control request is received;

the control request is used for requesting corresponding operation processing to the target vehicle based on the vehicle functions supported in the second software version information, and the response information is used for indicating that the control request fails to respond.

And when the compatibility relation is that the first software version information and the second software version information are incompatible, receiving first prompt information, wherein the first prompt information comprises prompting that the first software version information and the second software version information are incompatible, and/or prompting that the second software version information is updated.

and when the compatibility relation is that the first software version information and the second software version information are compatible, a control request for the target vehicle is sent.

In some embodiments, the control request includes a vehicle control request or a data subscription request, where the vehicle control request is used to request control processing of a target function for the target vehicle, the target function is at least one vehicle function supported in the second software version information, and the data subscription request is used to request data subscription for the vehicle function supported in the second software version information.

In some embodiments, the method further comprises:

When the first information which is not included in the first software version information is newly added in the second software version information, receiving second prompt information, wherein the first information is associated with a control request sent by the control equipment to the target vehicle, and the second prompt information comprises a prompt that the target vehicle cannot respond to the control request currently.

In some embodiments, the method further comprises:

And when the second information included in the second software version information is deleted from the first software version information, receiving third prompt information, wherein the second information is associated with a control request sent by the control equipment to the target vehicle, and the third prompt information comprises a prompt that the target vehicle does not support the control request.

In some embodiments, the method further comprises:

and receiving a rule conversion model, wherein the rule conversion model is used for converting third information in the second software version information when the first software version information and the second software version information are different and are not compatible, and the third information is associated with a control request of the target vehicle sent by the control equipment.

In some embodiments, the obtaining the first software version information for use by the target vehicle includes:

Sending an information inquiry request of the target vehicle to a server, wherein the information inquiry request is at least used for requesting to acquire first software version information used by the target vehicle;

And receiving the first software version information returned by the server.

In some embodiments, the first software version information and the second software version information include function identifiers of the target vehicles of different models.

According to a second aspect of embodiments of the present disclosure, there is provided a software version management method, the method comprising:

Receiving a control request sent by control equipment, wherein the control request is used for requesting corresponding operation processing on the target vehicle based on the vehicle functions supported in the second software version information used by the control equipment;

And based on the control request, corresponding response information is returned to the control equipment, wherein the response information is used for indicating a response result corresponding to the control request.

In some embodiments, the returning corresponding response information to the control device based on the control request includes:

acquiring first software version information used by the target vehicle;

and when the first software version information and the second software version information are different, returning response information corresponding to the control request to the control equipment based on the compatibility relation between the first software version information and the second software version information.

In some embodiments, returning response information corresponding to the control request to the control device based on a compatibility relationship between the first software version information and the second software version information includes:

When the compatibility relation is that the first software version information and the second software version information are not compatible, responding to the control request, and determining that no vehicle function matched with the control request exists in the first software version information;

And returning corresponding response information to the control equipment, wherein the response information is used for indicating that the control request fails to respond.

When the compatibility relation is that the first software version information and the second software version information are compatible, responding to the control request, and determining that a vehicle function matched with the control request exists in the first software version information;

And returning corresponding response information to the control equipment, wherein the response information is used for indicating that the control request is successfully responded.

In some embodiments, the method further comprises:

When the first information which is not included in the first software version information used by the target vehicle is newly added in the second software version information, second prompt information is sent to the control equipment, the first information is associated with a control request sent by the control equipment to the target vehicle, and the second prompt information comprises a prompt that the target vehicle cannot respond to the control request at present.

In some embodiments, the method further comprises:

And when the second information included in the second software version information is deleted from the first software version information used by the target vehicle, sending third prompt information to the control equipment, wherein the second information is associated with a control request sent by the control equipment to the target vehicle, and the third prompt information comprises a prompt that the target vehicle does not support the control request.

In some embodiments, the method further comprises:

And transmitting a rule conversion model to the control device, wherein the rule conversion model is used for converting third information in the second software version information when the first software version information and the second software version information used by the target vehicle are different and are not compatible, and the third information is associated with a control request of the target vehicle transmitted by the control device.

In some embodiments, the method further comprises:

Receiving an information inquiry request sent by the control equipment, wherein the information inquiry request is at least used for requesting to acquire first software version information used by the target vehicle;

and sending the first software version information to the control equipment based on the information inquiry request.

According to a third aspect of the embodiments of the present disclosure, there is provided a software version management apparatus, including:

an acquisition module configured to acquire first software version information used by a target vehicle;

The processing module is configured to compare the first software version information with second software version information of control equipment;

the processing module is further configured to determine a version management method based on a compatibility relationship between the first software version information and the second software version information when the first software version information and the second software version information are different.

According to a fourth aspect of embodiments of the present disclosure, there is provided another software version management apparatus, comprising:

The receiving and transmitting module is configured to receive a control request sent by control equipment, wherein the control request is used for requesting corresponding operation processing on the target vehicle based on the vehicle functions supported in the second software version information used by the control equipment;

the transceiver module is further configured to return corresponding response information to the control device based on the control request, wherein the response information is used for indicating a response result corresponding to the control request.

The embodiments of the present disclosure are not limited to the descriptions or illustrations of the embodiments of the methods described above.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a control apparatus including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the steps of the software version management method described in the first aspect above.

According to a sixth aspect of embodiments of the present disclosure, there is provided a server comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the steps of the software version management method described in the second aspect above.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the software version management method provided in the first or second aspect of the present disclosure.

According to an eighth aspect of embodiments of the present disclosure, there is provided a chip comprising: a processor and an interface; the processor is configured to read the instructions to perform the steps of the software version management method described above.

According to a ninth aspect of embodiments of the present disclosure, there is provided a system comprising a control device and a server, wherein the control device may perform the steps of the method as described in the first aspect above, and the server may perform the steps of the method as described in the second aspect above.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects: the control equipment acquires first software version information used by a target vehicle; comparing the first software version information with second software version information of control equipment; and determining a version management method based on a compatibility relation between the first software version information and the second software version information when the first software version information and the second software version information are different. Therefore, the control device can perform corresponding software management processing according to the compatible relation between the software version information used by the control device and the target vehicle, so that the problems that the vehicle is generated or controlled and the use experience of the vehicle is affected due to the fact that the software versions used by the control device and the target vehicle are inconsistent, such as incompatibility of the software versions, can be avoided, the reliability and the practicability of the software management are improved, the use experience of the vehicle is improved, and the user viscosity of vehicle products is enhanced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

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

Fig. 1 is a schematic diagram illustrating a software version management system according to an exemplary embodiment.

Fig. 2 is a schematic diagram of a DDF file framework, according to an exemplary embodiment.

Fig. 3 is a flow diagram illustrating a software version management method according to an exemplary embodiment.

Fig. 4 is a flow diagram illustrating a first software version information acquisition according to an exemplary embodiment.

Fig. 5 is a flow diagram illustrating a version management process according to an example embodiment.

Fig. 6 is a flow diagram illustrating another version management process according to an example embodiment.

Fig. 7 is a flow diagram illustrating another version management process according to an example embodiment.

Fig. 8 is a schematic diagram showing a structure of a software version management apparatus according to an exemplary embodiment.

Fig. 9 is a schematic diagram illustrating the structure of another software version management apparatus according to an exemplary embodiment.

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 are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

It should be noted that, all actions for acquiring signals, information or data in the present disclosure are performed under the condition of conforming to the corresponding data protection rule policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.

Referring to FIG. 1, a schematic diagram of a software version management system is shown according to an exemplary embodiment. The system as shown in fig. 1 may include a control device 100, a target vehicle 200, and a server 300. In general, in the embodiment of the present disclosure, data communication between the control device 100 and the target vehicle 200 needs to be forwarded through the server 300, that is, the server 300 may serve as a communication bridge between the control device 100 and the target vehicle 200 to manage software versions installed in each of the control device 100 and the target vehicle 200, which is specifically described in detail below in the present disclosure. The control apparatus 100 of the present disclosure may refer to a terminal apparatus having a control function, for example, a corresponding software version may be installed in the control apparatus 100 to perform a control operation or the like on the target vehicle 200. The server 300 of the present disclosure may be a cloud server deployed at the cloud, or may be a server local to the target vehicle 200, or the like, which is not limited in the present disclosure.

The information of the software version currently being used in the target vehicle 200 (simply referred to as software version information) is referred to as first software version information, and the information of the software version currently being used in the control apparatus 100 (simply referred to as software version information) is referred to as second software version information in the present disclosure. The above-described software version information may be stored in a predetermined format in the corresponding control device 100 or the target vehicle 200, and at this time, the software version information may be referred to as a device description framework (Device Distribution Frame, DDF) file. The DDF file (i.e. corresponding software version information) may include function identifiers (iid) corresponding to different vehicle types, different components, and different functions, and the DDF file in this embodiment includes at least all or part of the vehicle functions of the target vehicle 200 and the function identifiers corresponding to each of the vehicle functions. In practical applications, the description dimension or attribute of the DDF file may include a vehicle model number and a version number, for example, an initial software version01 of the vehicle type 1, an upgrade software version02 of the vehicle type 1, a re-upgrade software version03 of the vehicle type 1, and the like. When the software version of the same vehicle type is updated, the vehicle functions of the vehicle type can be changed or not. For example, when the function definition of the reserved charging of the vehicle changes, the present disclosure needs to update on the previous DDF file (i.e., the previous software version) to generate a new DDF file, and the version number corresponding to the file or the updated version may be automatically increased by 1. The new DDF file may be added with some function identifiers (iid) of newly added vehicle functions, or some function identifiers (iid) of old vehicle functions that are not used any more may be deleted, for example, a function identifier corresponding to vehicle reservation charging may be added to the new DDF file.

The function identifier in the DDF file is a unique identifier, and since the vehicle functions that it may have may be different for different vehicle models or the same vehicle component, the corresponding function identifiers in the DDF file are also different. The present disclosure is not limited to the expression of the above-mentioned functional identifier, and for example, it may be embodied in the form of numerals, characters, letters, or a combination thereof. For example, a driver's door of the vehicle type 1 has a closing function, and the corresponding function identifier may be 2.1.1; the driving door of the vehicle type 2 has a half-open function, and the corresponding function identifier may be 2.1.2, etc., which is only an example and not a limitation in this disclosure. In practical applications, the vehicle functions may be transmitted or indicated by using, for example, a controller area network (Controller Area Network, CAN) signal or a signal generated by a service oriented architecture (Service Oriented Architecture, SOA) module (which may be simply referred to as an SOA signal).

Referring also to fig. 2, a schematic diagram of a possible DDF file framework is shown according to an exemplary embodiment. The frame shown in fig. 2 describes specific contents included in the DDF file, taking vehicle models as a model 1, a model 2 and a model 3 respectively as examples, each vehicle model can be correspondingly designed with at least one software version, and the specific contents included in each software version can be called as software version information, for example, in the illustration, the model 1 has two software versions version01 and version02, which are respectively shown as a model 1-version01 and a model 1-version02 in the illustration; the model 2 corresponds to two software versions, and is respectively indicated as model 2-version01 and model 2-version02 in the diagram; model 3 corresponds to 1 software version, which is shown in the figure as model 3-version01. The software version of each vehicle type (specifically, the software version information corresponding to the vehicle type) CAN include a mapping relation between the vehicle functions indicated by the CAN signals and the SOA signals in the vehicle type and corresponding function identifiers thereof, wherein the mapping relation is that the vehicle functions and the function identifiers are in one-to-one correspondence/mapping. For example, in the illustration, taking a software version of a vehicle type 1-version01 as an example, a CAN signal is adopted to indicate that a vehicle driving door is in an open state, and the corresponding function identifier CAN be 1.1.1; the CAN signal is adopted to indicate that the vehicle driving door is in a closed state, and the corresponding function identifier CAN be 1.1.2; the CAN signal is adopted to indicate that the vehicle driving door is in a half-open state, and the corresponding function identifier CAN be 1.1.3 and the like. The SOA signal is adopted to indicate that the central control lock is in an open state, and the corresponding function identifier can be 2.1.1; the SOA signal is adopted to indicate that the central control lock is in a closed state, and the corresponding function identifier can be 2.1.2 and the like. Similarly, for the software version of other vehicle models, the mapping between the vehicle functions and the function identifiers is also as described above, and will not be described here again. The present embodiment is merely an example, but is not limited thereto, and may be determined according to actual situations.

Two application scenarios to which the present disclosure is applicable are described below.

First kind: the version number corresponding to the first software version information used by the target vehicle 200 is lower than the version number corresponding to the second software version information used by the control device 100, that is, the version number of the software used by the target vehicle 200 is lower than the version number of the software used by the control device 100. The specific application scenario involved may be an upgrade of the application software installed by the control device 100, while the application software installed by the target vehicle 200 is not.

Second kind: the version number corresponding to the first software version information used by the target vehicle 200 is higher than the version number corresponding to the second software version information used by the control device 100, that is, the version number of the software used by the target vehicle 200 is higher than the version number of the software used by the control device 100. The specific application scenario involved may be that the application software installed by the control apparatus 100 is not upgraded, and the application software installed by the target vehicle 200 is upgraded.

Based on the above embodiments, please refer to fig. 3, which is a flowchart illustrating a software version management method according to an exemplary embodiment. The method shown in fig. 3 is applied to the system shown in fig. 1, and comprises the following implementation steps:

S301, the control apparatus 100 acquires the first software version information used by the target vehicle 200.

The first software version information refers to software version information used on the side of the target vehicle 200, and the software version information may be represented by a DDF file. The present disclosure is not limited to the above-described embodiment of obtaining the first software version information, and may be obtained from other devices (e.g., the target vehicle 200) through a network in one example, for example. As another example, please refer to fig. 4, which is a schematic flow chart illustrating a first software version information acquisition according to an exemplary embodiment. The method shown in fig. 4 is applied to the system shown in fig. 1, and comprises the following implementation steps:

S401, the control device 100 sends an information query request of the target vehicle 200 to the server 300, where the information query request is at least used for requesting to obtain the first software version information used by the target vehicle 200. Accordingly, the server 300 receives the above information inquiry information.

S402, the server 300 sends the first software version information to the control device 100 based on the information query request. Accordingly, the control apparatus 100 receives the above-described first software version information.

The information query request of the present disclosure may carry, for example, a vehicle identifier of the target vehicle 200, an identifier of the control device 100, or other customized information, which is not limited by the present disclosure. The information inquiry request is for requesting acquisition of first software version information used by the side of the target vehicle 200. Accordingly, after receiving the information inquiry request, the server 300 may inquire from its own database about the first software version information used on the side of the target vehicle 200, and return/send the first software version information to the control apparatus 100.

In practical applications, the server 300 may store the current software version information (i.e., the first software version information described above) used by the target vehicle 200 in advance. The first software version information and the second software version information may be the DDF file, which may be pre-generated and stored in the server 300, and the present disclosure is not limited thereto. The generation implementation of each of the first software version information and the second software version information may correspond to the relevant description in the embodiment described with reference to fig. 1, and will not be repeated here.

S302, the control device 100 compares the first software version information with the second software version information used by the control device 100.

The control apparatus 100 may store a plurality of software version information for controlling the above-described target vehicle 200 in a local database, for example, all of the history software version information and the like; only the latest software version information for controlling the target vehicle 200 may be stored, and other software version information may be deleted, for example, the control device 100 may delete the old version of software version information after receiving the latest version of software version information. The control device 100 may select one of the latest or the largest software version number from the local database as the second software version information. Then, the first software version information and the second software version information are compared to determine whether they are identical and compatible.

S303, when the first software version information and the second software version information are different, the control apparatus 100 determines a version management method based on a compatibility relationship between the first software version information and the second software version information.

After obtaining the first software version information and the second software version information, the control device 100 may analyze and identify a difference relationship and a compatibility relationship between the first software version information and the second software version information, and further perform corresponding software version management processing based on the difference relationship and the compatibility relationship. The difference relationship is used for indicating whether the first software version information and the second software version information are the same, and the compatibility relationship is used for indicating whether the first software version information and the second software version information are compatible.

In an implementation process, when the control device 100 recognizes that the first software version information and the second software version information are the same, a corresponding control request may be sent to the server 300 or the target vehicle 200 to request a corresponding operation process for the target vehicle 200. Accordingly, upon receiving the control request, the server 300 or the target vehicle 200 may generate a corresponding control instruction to control the target vehicle 200 to perform a corresponding operation process, and the specific implementation of the control request will be described in detail below in this disclosure. Or when the first software version information and the second software version information are the same, the process may be ended, and no software version management is performed. In contrast, when it is recognized that the first software version information and the second software version information are different, the control apparatus 100 may perform corresponding software version management processing based on compatibility between the first software version information and the second software version information.

The present disclosure is not limited to the specific implementation of the version management process, and please refer to fig. 5, which is a schematic flow chart of a version management process according to an exemplary embodiment. The flow shown in fig. 5 is applied to the system shown in fig. 1, and includes the following implementation steps:

S501, the control device 100 sends a control request to the server 300, where the control request is used to request corresponding operation processing for the target vehicle based on the vehicle function supported in the second software version information. Accordingly, the server 300 receives the control request.

S502, the server 300 returns corresponding response information to the control device 100 based on the control request, where the response information is used to indicate a response result corresponding to the control request. Accordingly, the control apparatus 100 receives the above-described response information.

The server 300 may return response information corresponding to the control request to the control apparatus 100 in response to the control request. The present disclosure is not limited to the specific embodiment of the server 300 responding to the control request, and the server 300 may obtain the first software version information, which is stored in the server device in advance and used by the target vehicle 200, through a service such as a vehicle information service. Next, in response to the control request based on the compatibility relationship between the first software version information and the second software version information, corresponding response information is returned to the control apparatus 100.

In a specific implementation, when the compatibility relationship between the first software version information and the second software version information is used to indicate (or the compatibility relationship is that) that the first software version information and the second software version information are not compatible, the control device 100 may send a control request to the server 300. Accordingly, the server 300 may query and determine in the first software version information that there is no vehicle function or a function identification corresponding to the vehicle function that matches the control request in response to the control request. At this time, the server 300 may return corresponding response information indicating that the above-described control request response fails or that the incomplete response is successful to the control apparatus 100.

Conversely, when the compatibility relationship between the first software version information and the second software version information is used to indicate that the first software version information and the second software version information are compatible, the control device 100 may also send a control request to the server 300. Accordingly, the server 300 may query and determine in the first software version information that there is a vehicle function or a function identification corresponding to the vehicle function that matches the control request in response to the control request. At this time, the server 300 may return corresponding response information to the control apparatus 100, which is used to indicate that the above-described control request response is successful.

In some alternative embodiments, when the first software version information and the second software version information are incompatible, the control device 100 may receive first hint information, where the first hint information includes a hint that the first software version information and the second software version information are incompatible; and/or includes prompting a user to update or upgrade the second software version information described above for use by the control device 100. The specific embodiment of the prompt information is not limited in this disclosure, and may be, for example, a text, a vibration, a sound, a caption, a picture, or the like.

In some alternative embodiments, when the first information not included in the first software version is newly added to the second software version information, the server 300 may send the second prompt information to the control device 100 in response to the control request. Accordingly, the control apparatus 100 may receive the second prompt information, and the first information is associated with the control request, and may specifically be related to the first information and the vehicle function related to the target vehicle 300 requested by the control request. The second prompt message includes a prompt that the target vehicle 300 is currently unable to respond to the control request.

In some alternative embodiments, when the second information included in the second software version information is deleted from the first software version information, the server 300 may transmit third hint information to the control apparatus 100 in response to the control request. Accordingly, the control device 100 may receive the third prompt information, where the second information is also associated with the control request, and may specifically be related to a vehicle function related to the target vehicle 300 requested by the control request. The third prompting information includes prompting that the target vehicle temporarily does not support the vehicle function associated with the second information, or that the target vehicle cannot respond to the control request currently.

In some alternative embodiments, the server 300 may send the rule conversion model to the control device 100 according to actual requirements, e.g., the server 300 may issue to the control device 100 after receiving a request for the rule conversion model sent by the controller 100, etc. Accordingly, the control apparatus 100 may receive the rule conversion model, which may be used to convert, when the first software version information and the second software version information are incompatible, third information in the second software version information, where the third information is associated with the control request, and may specifically be related to a vehicle function related to the target vehicle 200 requested by the control request.

There may be different rule conversion models for different vehicle functions (which may be information or signals indicating the above-described vehicle functions) in the control apparatus 100, which may be determined according to actual situations. For example, for the third information related to time, the rule conversion model may be a time rule conversion model, such as time information of individual hours, minutes, and the like may be uniformly converted into time information of 24 hours, and the like. As another example, for the third information related to the units, the rule conversion model may be a unit value conversion model, such as converting Kpa (kilopascal) values in the third information to unit values of psi, etc., and the disclosure is not limited.

In some embodiments, the control request includes, but is not limited to, for example, a control request, a data subscription request, or a control or operation request of other custom vehicle functions, and the disclosure is not limited thereto. When the control request is a vehicle control request, the vehicle control request may be used to request a control process of a target function for the target vehicle, where the target function is a vehicle function of any one or more items supported in the second software version information. When the control request is a data subscription request, the data subscription request is used for requesting data subscription and the like for any one or more vehicle functions supported in the second software version information.

In practical applications, when the control request is the data subscription request, if the first software version information and the second software version information are not compatible, the response information returned by the server 300 may be further used to indicate that the first software version information and the second software version information have the same information such as function identifier and subscription data corresponding to the same vehicle function. Otherwise, when the first software version information and the second software version information are compatible, and the version number corresponding to the second software version information is lower than the version number corresponding to the first software version information (i.e., the software version used by the control device is lower than the software version used by the target vehicle), the response information may be further used to indicate the function identifier, subscription data, and other information corresponding to the vehicle function different from the second software version information in the first software version information.

For a better understanding of the disclosed embodiments, the following is illustrative. Fig. 6 is a schematic flow chart of a software version management process. The flow shown in fig. 6 is applied to the first application scenario, where the application software installed by the control device 100 is updated and the application software installed by the target vehicle 200 is not updated, that is, the version number corresponding to the second software version information used by the control device 100 is higher than the version number corresponding to the first software version information used by the target vehicle 200. The process comprises the following implementation steps:

S601, the control device 100 sends an information query request to the server 300, where the information query request is at least used to request to obtain the first software version information used by the target vehicle 200. Accordingly, the server 300 receives the above-described information inquiry request.

S602, the server 300 sends the first software version information to the control device 100 based on the information query request. Accordingly, the control apparatus 100 receives the above-described first software version information.

The description of steps S601-S602 may correspond to the description of the embodiment described above with reference to fig. 4, and will not be repeated here.

S603, the control device 100 determines whether the second software version information used by itself and the first software version information are the same and compatible.

When the control device 100 determines that the first software version information and the second software version information are the same, or the first software version information and the second software version information are different but compatible, the control device 100 may send a vehicle control request to the target vehicle 200, for example, may directly send the vehicle control request to the target vehicle 200 or perform step S604 to send the vehicle control request to the server 300, which may refer to the related description in the embodiment of fig. 5 and will not be repeated herein. Otherwise, when it is determined that the first software version information and the second software version information are different and incompatible, step S604 may be continued.

S604, the control device 100 sends a vehicle control request to the server 300, where the vehicle control request is used to instruct the control process of the target function to the target vehicle, and the target function is at least one vehicle function supported in the second software version information. Accordingly, the server 300 receives the above-described request for controlling the vehicle.

S605, the server 300 queries whether the function identification of the target function matched with the control request exists in the first software version information based on the control request.

S606, the server 300 returns a control response to the control apparatus 100 for indicating that the target vehicle 200 temporarily does not support the target function indicated by the above-described control request.

In practical application, the control request may carry a function identifier (idd) corresponding to the target function or other user-defined information, where the control request is used to request control processing of at least one vehicle function (target function) supported by the second software information on the target vehicle. Accordingly, the server 300 may query whether there is a vehicle function or a function identification of a vehicle function matching the vehicle control request in the first software version information in response to the vehicle control request. In this application scenario, it may be determined that there is no vehicle function or its function identifier that matches the above-mentioned vehicle control request, and the server 300 may further send a vehicle control response to the control device 100, where the vehicle control response may be used to prompt the user that the above-mentioned target vehicle 200 does not support the vehicle function requested/indicated by the vehicle control request at present.

S607, the control device 100 sends a data subscription request to the server 300, where the data subscription request is used to request data subscription for the vehicle function supported in the second software version information. Accordingly, the server 300 receives the above-described data subscription request.

It should be noted that, the execution sequence of each of the traffic control process flow shown in steps S604-S606 and the data subscription process flow shown in steps S607-S609 in the present disclosure is not limited, and may be determined according to practical situations, for example, the present disclosure may execute the data subscription process flow shown in steps S607-S609 first, then execute the traffic control process flow shown in steps S604-S606, and so on.

S608, the server 300 queries whether there is a function identifier of the vehicle function matching the data subscription request in the first software version information based on the data subscription request.

S609, the server 300 returns a data subscription response to the control device 100, the data subscription response indicating subscription data corresponding to the subscribed vehicle function.

In practical applications, the control device 100 may subscribe to any one or more vehicle functions supported in the second software version information through the data subscription request, where the data subscription request may carry the function identifier (idd) of the vehicle function or other custom information, etc. Accordingly, the server 300 may query whether there is a vehicle function or a function identification of the vehicle function matching the data subscription request in the first software version information in response to the data subscription request. In this application scenario, if the subscribed vehicle function is a vehicle function compatible/existing with both the first software version information and the second software version information, the server 300 may query the first software version for a vehicle function or a function identifier of the vehicle function that matches the data subscription request. The server 300 may indicate subscription data corresponding to the vehicle function through the above-described data subscription response.

Otherwise, if the subscribed vehicle function is a vehicle function (in the second software version information) that does not exist in the first software information, the server 300 does not query the first software version information for a vehicle function or a function identifier of the vehicle function that matches the data subscription request. The server 300 may return a corresponding data subscription response to the control device 100, which is used to prompt subscription data corresponding to the data subscription request. Alternatively, when the vehicle function or the function identifier of the vehicle function matched with the data subscription request is not queried, the server 300 may filter the vehicle functions or the function identifiers thereof, subscribe again to the vehicle functions compatible/existing with the first software version information and the second software version information, and send a data subscription response to the control device 100 to indicate that the data subscription is successful. In this case, the data subscription response may indicate/carry subscription data corresponding to the same vehicle function as the second software version information in the first software version information, where the subscription data refers to vehicle data corresponding to the vehicle function in the target vehicle 200, and the disclosure will not excessively define and detail this.

In some alternative embodiments, when the control device 100 determines that the first software version information and the second software version information are different and compatible, the control device 100 may send a control request to the server 300, where the control request may be the above-mentioned control request or the above-mentioned data subscription request. Since the first software version information and the second software version information are compatible, the server 300 can normally respond/execute the control request. For example, when the control request is the above-mentioned control request, the server 300 may query the first software version information for a vehicle function or a function identifier thereof that matches the control request, and then the server 300 may forward the control request to the target vehicle 200. Accordingly, the target vehicle 200 may perform control processing of corresponding functions, such as control processing of deceleration, braking, etc., on the target vehicle 200 in response to the vehicle control request, which is not limited in the present disclosure.

In another example, when the control request is the data subscription request, the server 300 may query the first software version information for a vehicle function or a function identifier thereof that matches the data subscription request, and then the server 300 may send the data subscription request to the target vehicle 200. Accordingly, the target vehicle 200 may collect vehicle data of the corresponding vehicle function in the target vehicle 200 as corresponding subscription data in response to the data subscription request, and return the same to the control device 100 through the server 300.

Fig. 7 is a schematic flow chart of another software version management process. The flow shown in fig. 7 is applied to the second application scenario, where the application software installed by the control device 100 is not updated, and the application software installed by the target vehicle 200 is updated, that is, the version number corresponding to the second software version information used by the control device 100 is lower than the version number corresponding to the first software version information used by the target vehicle 200. The process comprises the following implementation steps:

S701, the control apparatus 100 transmits an information inquiry request to the server 300, the information inquiry request being at least for requesting acquisition of the first software version information used by the target vehicle 200. Accordingly, the server 300 receives the above-described information inquiry request.

S702, the server 300 sends the first software version information to the control device 100 based on the information query request. Accordingly, the control apparatus 100 receives the above-described first software version information.

The descriptions of steps S701-S702 may correspond to the related descriptions of the embodiment described above with reference to fig. 4, and are not repeated here.

S703, the control device 100 determines whether the second software version information used by itself and the first software version information are the same and compatible.

When the control device 100 determines that the first software version information and the second software version information are the same, or the first software version information and the second software version information are different and compatible, the control device 100 may send a vehicle control request to the target vehicle 200, for example, may directly send the vehicle control request to the target vehicle 200, or perform step S604 to send the vehicle control request to the server 300, which may refer to the related description in the embodiment of fig. 5 and will not be repeated herein. Otherwise, when it is determined that the first software version information and the second software version information are different and incompatible, step S704 may be performed continuously.

S704, the control device 100 displays a prompt message, where the prompt message is used to prompt updating the second software version information.

The specific form of the prompt information is not limited in the disclosure, for example, the user may be prompted to update the second software version information used on the control device 100 side by using a popup window, which may be correspondingly referred to the related description in the foregoing embodiment, and will not be repeated herein.

S705, the control device 100 sends a vehicle control request to the server 300, the vehicle control request being for instructing a control process of performing a target function on the target vehicle, the target function being at least one vehicle function supported in the second software version information. Accordingly, the server 300 receives the above-described request for controlling the vehicle.

S706, the server 300 queries whether the function identifier of the target function matched with the control request exists in the first software version information based on the control request.

S707, the server 300 returns a vehicle control response for indicating that the target vehicle 200 temporarily does not support the target function indicated by the above-described vehicle control request to the control apparatus 100.

Since the version number corresponding to the second software version information used by the control device 100 is lower than the first software version information used in the target vehicle 200, the first software version information may be software version information obtained by adding or modifying and upgrading the vehicle functions in the second software version information, where the first software version information includes all or distributed vehicle functions or function identifiers thereof in the second software version information, and may also include some custom added vehicle functions or function identifiers thereof, and the like. Or the first software version information may be version information obtained by deleting and upgrading the vehicle function in the second software version information, where the first software version information includes a part of the vehicle functions in the second software version information or function identifiers thereof, that is, supports a part of the vehicle functions in the second software version information, and does not support the deleted part of the vehicle functions.

Taking the control request to control the vehicle function deleted in the second software version information as an example, the server 300 does not query the first software version information for the vehicle function or the function identifier thereof that matches the control request after receiving the control request. In this case, the server 300 transmits a corresponding vehicle control response for prompting the user that the above-described target vehicle 200 does not support the vehicle function requested/indicated by the vehicle control request at present to the control apparatus 100.

S708, the control device 100 sends a data subscription request to the server 300, where the data subscription request is used to request to subscribe to data for the vehicle function supported in the second software version information. Accordingly, the server 300 receives the above-described data subscription request.

S709, the server 300 returns a data subscription response for indicating subscription data corresponding to the subscribed vehicle function to the control device 100.

If the vehicle function to be subscribed to in the data subscription request is a vehicle function compatible with each other in the first software version information and the second software version information, the server 300 may subscribe to the vehicle data corresponding to the vehicle function normally, and return a data subscription response to the control device 100, where the response indicates that the data subscription request subscription/response is successful. Meanwhile, the server 300 may transmit the vehicle function or the function identifier thereof, which is different from or is newly added to the second software version information in the first software version, to the control device 100, etc., through the data subscription response, which is not limited in the present disclosure. Other relevant descriptions regarding the above steps S805-S809 may correspond to those described in the embodiment described with reference to fig. 6, and are not described herein.

It can be seen that by implementing the embodiment of the present disclosure, the problem that the terminal uses 100 to use the first software version information with a high version to remotely control the target vehicle 200 to use the second software version information with a low version to cause failure or abnormality of vehicle control can be solved, and the problem that the terminal uses 100 to use the first software version information with a low version to remotely control the target vehicle 200 to use the second software version information with a high version to discard or change the vehicle control format to cause failure of vehicle control can be solved. The problem that the above-described second software version information used by the control apparatus 100 may exhibit errors, abnormalities, or non-exhibition of the deleted vehicle functions and states thereof may also be solved.

In an example embodiment, the present disclosure also provides a communication system that may include the control device 100 and the server 300. Wherein the control device 100 may perform the software version management method related to the control device in the foregoing embodiments of the present disclosure; the server 300 may perform the software version management method related to the server in the foregoing embodiments of the present disclosure.

Fig. 8 is a schematic structural diagram of a software version management device according to an exemplary embodiment. The apparatus shown in fig. 8 may be applied to the control device 100, and the apparatus may include an acquisition module 101 and a processing module 102. Wherein:

The acquiring module 101 is configured to acquire first software version information used by a target vehicle;

The processing module 102 is configured to compare the first software version information with second software version information of a control device;

The processing module 102 is further configured to determine a version management method based on a compatibility relationship between the first software version information and the second software version information when the first software version information and the second software version information are different.

In some embodiments, the processing module 102 is configured to:

When the compatibility relation is that the first software version information and the second software version information are not compatible, a control request is sent to a server, and response information returned by the server is received;

The control request is used for indicating that the operation process indicated by the control request is performed on the target vehicle based on the vehicle functions supported in the second software version information, and the response information is used for indicating that the control request response fails.

In some embodiments, the processing module 102 is further configured to:

And when the compatibility relation is that the first software version information and the second software version information are incompatible, receiving first prompt information, wherein the first prompt information comprises prompting that the first software version information and the second software version information are incompatible, and/or prompting that the second software version information used by the control equipment is updated.

In some embodiments, the processing module 102 is configured to:

when the compatibility relation is used for indicating that the first software version information and the second software version information are compatible, a control request is sent to a server, and response information returned by the server is received;

The control request is used for indicating that the operation process indicated by the control request is performed on the target vehicle based on the vehicle functions supported in the second software version information, and the response information is used for indicating that the control request response is successful.

In some embodiments, the processing module 102 is further configured to:

And when the second information included in the second software version information is deleted from the first software version information, receiving third prompt information, wherein the second information is associated with a control request sent by the control equipment to the target vehicle, and the third prompt information comprises a prompt that the target vehicle does not support the vehicle function associated with the second information.

In some embodiments, the processing module 102 is further configured to:

In some embodiments, the acquisition module 101 is configured to:

And receiving the first software version information returned by the server.

Fig. 9 is a schematic diagram illustrating another software version management apparatus according to an exemplary embodiment. The apparatus shown in fig. 9 may be applied to a server 300, and the apparatus may include a transceiver module 301 and a processing module 302. Wherein:

The transceiver module 301 is configured to receive a control request sent by a control device, where the control request is used to instruct the target vehicle to perform an operation process indicated by the control request based on a vehicle function supported in second software version information used by the control device;

the processing module 302 is configured to return corresponding response information to the control device based on the control request, where the response information is used to indicate a response result of the control request.

In some embodiments, the transceiver module 301 is further configured to:

In some embodiments, the processing module 302 is configured to:

acquiring first software version information used by the target vehicle;

In some embodiments, the processing module 302 is configured to:

When the compatibility relation is used for indicating that the first software version information and the second software version information are not compatible, responding to the control request, and determining that no vehicle function matched with the control request exists in the first software version information;

In some embodiments, the processing module 302 is configured to:

when the compatibility relation is used for indicating that the first software version information and the second software version information are compatible, responding to the control request, and determining that a vehicle function matched with the control request exists in the first software version information;

In some embodiments, the transceiver module 301 is further configured to:

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

By implementing the embodiment of the disclosure, the device can acquire the first software version information used by the target vehicle; comparing the first software version information with second software version information of control equipment; and determining a version management method based on a compatibility relation between the first software version information and the second software version information when the first software version information and the second software version information are different. Therefore, the control device can perform corresponding software management processing according to the compatible relation between the software version information used by the control device and the target vehicle, so that the problems that the vehicle is generated or controlled and the use experience of the vehicle is affected due to the fact that the software versions used by the control device and the target vehicle are inconsistent, such as incompatibility of the software versions, can be avoided, the reliability and the practicability of the software management are improved, the use experience of the vehicle is improved, and the user viscosity of vehicle products is enhanced.

The present disclosure also provides a computer readable storage medium having stored thereon a computer program request which, when executed by a processor, implements the steps of the software version management method provided by the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method of software version management, the method comprising:

Acquiring first software version information used by a target vehicle;

2. The method of claim 1, wherein the determining a version management method based on a compatibility relationship between the first software version information and the second software version information comprises:

3. The method of claim 1, wherein the determining a version management method based on a compatibility relationship between the first software version information and the second software version information comprises:

4. The method according to claim 1, wherein the method further comprises:

5. The method according to claim 1, wherein the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

7. The method of claim 1, wherein the obtaining the first software version information for use by the target vehicle comprises:

And receiving the first software version information returned by the server.

8. The method according to any one of claims 1-7, wherein the first software version information and the second software version information include function identifications of different models of the target vehicle.

9. The method according to any one of claims 1-7, further comprising:

10. A method of software version management, the method comprising:

11. The method according to claim 10, wherein the method further comprises:

12. The method according to claim 10, wherein the method further comprises:

13. The method according to claim 10, wherein the method further comprises:

14. The method according to claim 10, wherein the method further comprises:

15. The method according to any one of claims 10-14, wherein the first software version information and the second software version information include functional identifications of the target vehicles of different models.

16. A software version management apparatus, comprising:

17. A software version management apparatus, comprising:

The receiving and transmitting module is configured to receive a control request sent by control equipment, wherein the control request is used for indicating the corresponding operation processing to the target vehicle based on the vehicle functions supported in the second software version information used by the control equipment;

18. A software version management system, comprising:

a control device that performs the method of any one of claims 1 to 9;

a server performing the steps of the method according to any one of claims 10 to 15.