CN116881118B - Conflict detection method, device, electronic equipment and storage medium - Google Patents

Conflict detection method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN116881118B
CN116881118B CN202310648674.1A CN202310648674A CN116881118B CN 116881118 B CN116881118 B CN 116881118B CN 202310648674 A CN202310648674 A CN 202310648674A CN 116881118 B CN116881118 B CN 116881118B
Authority
CN
China
Prior art keywords
api
information
software
vehicle
distributed
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202310648674.1A
Other languages
Chinese (zh)
Other versions
CN116881118A (en
Inventor
黄培斌
李辉
杨毅
廖磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Automobile Group Co Ltd
Original Assignee
Guangzhou Automobile Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Automobile Group Co Ltd filed Critical Guangzhou Automobile Group Co Ltd
Priority to CN202310648674.1A priority Critical patent/CN116881118B/en
Publication of CN116881118A publication Critical patent/CN116881118A/en
Application granted granted Critical
Publication of CN116881118B publication Critical patent/CN116881118B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3604—Software analysis for verifying properties of programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Mining & Analysis (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a conflict detection method, a conflict detection device, electronic equipment and a storage medium. The method comprises the following steps: determining first Application Program Interface (API) information on which the software to be released runs, wherein the first API information is used for indicating at least one API on which the software to be released depends and version information of each API; acquiring a vehicle identifier of a vehicle to which software to be released is to be released; determining second API information corresponding to the vehicle identification; if any API in the first API information is not contained in the second API information, or any API in the first API information is contained in the second API information, and the version information of the API is higher than the version information of the API in the second API information, the conflict between the software to be distributed and the vehicle is determined. The technical scheme provided by the application can timely detect whether the product collides with the vehicle before the product is released, avoid the condition that the product cannot run in the vehicle after being released, and provide a basis for the safe release and smooth running of the product.

Description

Conflict detection method, device, electronic equipment and storage medium
Technical Field
The present application relates to the field of software technologies, and in particular, to a method and apparatus for detecting a conflict, an electronic device, and a storage medium.
Background
The product release means that a software developer pushes the self-developed software to an application mall through electronic equipment so as to be convenient for a user to download and install.
However, the device held by the user may not meet the conditions required for the software running, such as the device held by the user does not have an interface that the software running must call, the device held by the user does not have data required for the software running, and so on, so that the software cannot run on the device held by the user.
Disclosure of Invention
The application provides a conflict detection method, a conflict detection device, electronic equipment and a storage medium.
In a first aspect, an embodiment of the present application provides a method for detecting a collision, where the method includes: determining API information of an Application Program Interface (API) on which the software to be released depends, wherein the API information is used for indicating at least one API on which the software to be released depends and version information of each API; acquiring a vehicle identifier of a vehicle to which software to be released is to be released; determining second API information corresponding to the vehicle identifier, wherein the second API information is used for indicating at least one API associated with the vehicle and version information of each API; if any API in the first API information is not contained in the second API information, or any API in the first API information is contained in the second API information, and the version information of the API is higher than the version information of the API in the second API information, the conflict between the software to be distributed and the vehicle is determined.
In a second aspect, an embodiment of the present application provides a collision detection apparatus, where the collision detection apparatus includes a module for implementing the method according to the first aspect.
In a third aspect, an embodiment of the present application provides a collision detection apparatus, including: the first information determining module is used for determining first Application Program Interface (API) information on which the software to be issued runs, wherein the first API information is used for indicating at least one API on which the software to be issued depends and version information of each API; the identification acquisition module is used for acquiring the vehicle identification of the vehicle to which the software to be distributed is to be distributed; a second information determining module, configured to determine second API information corresponding to the vehicle identifier, where the second API information is used to indicate at least one API associated with the vehicle and version information of each API; the conflict detection module is used for determining that the software to be distributed conflicts with the vehicle if any API in the first API information is not contained in the second API information or any API in the first API information is contained in the second API information and the version information of the API is higher than the version information of the API in the second API information.
In a fourth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in memory and configured to be executed by one or more processors, the one or more applications configured to perform the method as described in the first aspect.
In a fifth aspect, embodiments of the present application provide a computer readable storage medium having stored therein computer program instructions which are callable by a processor to perform the method according to the first aspect.
In a sixth aspect, embodiments of the present application provide a computer readable program product for implementing the method of the first aspect when executed.
According to the application program detection method provided by the embodiment of the application, the first API information on which the operation of the product to be issued depends is obtained, then the second API information related to the vehicle to be issued of the software to be issued is obtained, if the first API information contains the API information which is not contained in the second API information, the API related to the vehicle lacks the API required by the operation of the software to be issued, if the version information of the API in the first API information is higher than the version information of the API in the second API information, the version information of the API related to the vehicle is higher than the version information of the API, and the occurrence of any one of the two conditions is indicated, the collision between the software to be issued and the vehicle is indicated, and the software to be issued cannot be operated in the vehicle.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic illustration of an implementation environment provided by one embodiment of the present application.
Fig. 2 is a flowchart of a collision detection method according to an embodiment of the present application.
Fig. 3 is a flowchart of a collision detection method according to another embodiment of the present application.
Fig. 4 is a flowchart of a collision detection method according to another embodiment of the present application.
Fig. 5 is a block diagram of a collision detection apparatus provided in one embodiment of the present application.
Fig. 6 is a block diagram of an electronic device provided in one embodiment of the application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present application and are not to be construed as limiting the present application.
In order to enable those skilled in the art to better understand the solution of the present application, the following description will make clear and complete descriptions of the technical solution of the present application in the embodiments of the present application with reference to the accompanying drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, a schematic diagram of an implementation environment provided by an embodiment of the present application is shown. The implementation environment includes an electronic device 110. In some embodiments, the electronic device 110 may be a personal computer, a mobile terminal, a tablet computer, or the like. In other embodiments, electronic device 110 may be a server. In the embodiment of the present application, only the electronic device 110 is taken as an example of the terminal device for explanation.
In the embodiment of the present application, the electronic device 110 operates a product release system, which is used to detect whether the software to be released conflicts with the vehicle to which the software to be released is to be released. Whether the software to be issued collides with the vehicle or not refers to whether the vehicle supports the operation of the software to be issued or not. For example, in the case that the vehicle does not have a software interface on which the running of the software to be distributed needs to depend, the software to be distributed collides with the vehicle; or the vehicle is provided with an interface on which the running of the software to be distributed needs to depend, but the version of the interface provided by the vehicle is lower than the version of the interface required to be called by the software to be distributed, and the software to be distributed collides with the vehicle.
In the embodiment of the application, the electronic device 110 acquires the first API information on which the product to be distributed depends, then acquires the second API information associated with the vehicle to which the software to be distributed is related, and detects whether the software to be distributed collides with the vehicle based on the first API information and the second API information, so that whether the vehicle has the API on which the software to be distributed depends and whether the version of the API on which the software to be distributed depends is too low can be detected in time before the product is distributed, and a foundation can be provided for safe distribution and smooth operation of the product.
In some embodiments, the implementation environment further includes a first database 120, where the first database 120 is configured to store second API information corresponding to different vehicles, respectively, and the second API information corresponding to the vehicles is configured to indicate at least one API associated with the vehicles and version information of each API.
In some embodiments, the electronic device 110 may further detect whether the capability set on which the software to be released depends matches the capability set corresponding to the model information of the vehicle, and if the capability set is matched with the capability set, perform conflict detection on the next API information, and if the capability set is not matched with the model information, directly determine that the software to be released conflicts with the vehicle, without performing conflict detection on the next API information. In this embodiment, the implementation environment further includes a second database 130, where the second database 130 is configured to store capability sets corresponding to different types of information respectively.
The first database 120 and the second database 130 may be disposed in the same device or may be disposed in different devices. In the embodiment of the present application, only the first database 120 and the second database 130 are disposed in the same device will be described as an example. The device that deploys the first database 120 and the second database 130 simultaneously may be the electronic device 110 or a server. In the case where the first database 120 and the second database 130 are deployed in a server at the same time, the server may be one server, or may be multiple servers, or may be a cloud computing service center. In the case where the first database 120 and the second database 130 are deployed simultaneously in a server, the server establishes a communication connection with the electronic device 100 through a wired or wireless network.
Aiming at the situation that equipment held by a user does not meet the running condition of certain software at a certain probability, the application provides a technical scheme for detecting before the software release, by acquiring first API information on which a product to be released depends and then acquiring second API information related to a vehicle on which the software to be released is to be released, if the first API information contains the API information which is not contained in the second API information, the API related to the vehicle lacks the API required by the running of the software to be released, if the version information of the API exists in the first API information is higher than the version information of the API in the second API information, the version information of the API related to the vehicle is too low, and the occurrence of any one of the two conditions indicates that the software to be released collides with the vehicle, and the software to be released cannot run in the vehicle, namely, the technical scheme provided by the embodiment of the application can timely detect whether the API on which the software to be released depends exists in the product release, and whether the version of the API on which the software to be released depends in the vehicle runs is too low or not, and the like, and can timely detect whether the product collides with the product to run smoothly in the vehicle and the product release is not smoothly.
Referring to fig. 2, a flowchart of a collision detection method according to an embodiment of the application is shown. The method comprises the following procedures.
S201, obtaining first API information on which to-be-released software runs.
The first API information is used to indicate at least one API on which the software to be released depends and version information of each API. Wherein one API may correspond to a plurality of version information.
The software to be distributed depends on a certain API, which means that the running of the software to be distributed needs to call the API. For example, the application to be issued is an "auto-park application" that runs detection data of a sensing-type application (such as an application that controls an ultrasonic radar) and detection data of a detection-type application (such as an application that controls a speed sensor), at which time the "auto-park application" needs to call a detection data reading interface to acquire the detection data and call a detection data reading interface to read the detection data, that is, the "auto-park application" depends on the detection data reading interface and the detection data reading interface.
Reference is made to table-1, which illustrates first API information on which the software to be deployed depends.
TABLE-1
In the embodiment of the application, the to-be-deployed software generates and stores the designated file for recording the first API information when the development is completed. In some embodiments, after receiving the product issue command, the electronic device displays a user interface of the product issue system, a technician may select or input the software to be issued on the user interface, and then the electronic device may obtain a specified file of the software to be issued from the local or from the cloud, and read the first API information of the software to be issued from the specified file.
S202, acquiring a vehicle identifier of a vehicle to which software to be released is to be released.
The vehicle identification of the vehicle is used to uniquely identify the vehicle. The vehicle identifier of the vehicle may be a license plate number of the vehicle or a frame number of the vehicle. In the embodiment of the present application, only the frame number of the vehicle, which is the vehicle identification of the vehicle, will be described as an example. The number of vehicles to which the software to be distributed is distributed may be one or more, and the embodiment of the present application is not limited thereto.
In some embodiments, the user interface of the product release system includes a release object input box where a technician can enter or select a vehicle identification of the vehicle.
In other embodiments, the electronic device obtains the tag of the software to be distributed, and obtains the user portrait information of the vehicle owners to which the plurality of vehicles belong respectively, then determines the user to be distributed of the software to be distributed based on the tag of the software to be distributed and the user portrait information of the vehicle owners to which the plurality of vehicles belong, and then obtains the vehicle identifier of the vehicle corresponding to the user to be distributed as the vehicle identifier of the vehicle to which the software to be distributed is distributed. The tag of the software to be distributed is used for indicating at least one of the following: the function of the software to be distributed, the classification of the software to be distributed, etc. The user portrait information of the vehicle owner is used for indicating at least one of the following: age, gender, hobbies, etc. The electronic device may determine a user corresponding to the user portrayal information matched with the tag of the software to be distributed as a user to be distributed of the software to be distributed. For example, if the function of the software to be distributed is tourist attraction recommendation, the vehicle owners interested in tourism can be determined as users to be distributed of the software to be distributed. Through the mode, the probability that the software to be released is used after being released can be greatly improved, and the marketing effect is improved. In addition, the manner of determining the release object provided by this embodiment may be accomplished by a marketing class application installed by the electronic device.
In some embodiments, after determining the vehicle identifier of the vehicle to which the software to be distributed is to be distributed, the electronic device may acquire a distribution record to determine whether the software to be distributed has been distributed to the vehicle, and if it is determined that the software to be distributed has not been distributed to the vehicle, continue to execute the subsequent steps.
S203, determining second API information corresponding to the vehicle identification.
The second API information is used to indicate at least one API associated with the vehicle and version information of each API. Optionally, the second API information refers to at least one API installed by the vehicle and version information of each API.
In some embodiments, the electronic device obtains an API installation record of the vehicle based on the vehicle identifier, and obtains second API information corresponding to the vehicle identifier from the API installation record of the vehicle.
S204, if any API in the first API information is not contained in the second API information, or any API in the first API information is contained in the second API information, and the version information of the API is higher than the version information of the API in the second API information, determining that the software to be distributed conflicts with the vehicle.
If any API in the first API information is not contained in the second API information, the vehicle is not provided with an interface which needs to be called when the software to be distributed runs, and the software to be distributed cannot run smoothly on the vehicle, so that the software to be distributed collides with the vehicle. For example, the "auto park application" operates on the probe data reading interface, whereas the vehicle does not have the probe data reading interface installed, and at this time the vehicle cannot operate even if the "auto park application" is installed, which collides with the vehicle.
Any API in the first API information is contained in the second API information, and the version information of the API is higher than the version information of the API in the second API information, which indicates that the vehicle has an interface which needs to be called when the software to be distributed runs, but the version of the interface is too low, and the software to be distributed cannot run smoothly on the vehicle, so that the software to be distributed collides with the vehicle. For example, the "auto park application" runs on version 2.0 and version 3.0 probe data reading interfaces, whereas the vehicle installs only version 1.0 probe data reading interfaces, at which point the vehicle cannot run even if the "auto park application" is installed, which conflicts with the vehicle.
In some embodiments, the electronic device may display a detection result when it is determined that the software to be deployed collides with the vehicle, where the detection result may include an API that is not included in the second API information in the first API information, and may also include an API that is included in the second API information in the first API information and has version information higher than version information of the API in the second API information. The technician can reselect the vehicle to be distributed or modify the software to be distributed based on the detection result displayed by the electronic device.
In summary, the technical solution provided in the embodiments of the present application obtains the first API information on which the product to be distributed operates, and then obtains the second API information associated with the vehicle on which the software to be distributed is to be distributed, if the first API information includes the API information not included in the second API information, it is indicated that the API associated with the vehicle lacks the API required for the operation of the software to be distributed, if the first API information includes the API version information higher than the API version information in the second API information, it is indicated that the API version associated with the vehicle is too low, and either of the above two situations occurs, which indicates that the software to be distributed collides with the vehicle, and the software to be distributed cannot operate in the vehicle, that is, the technical solution provided in the embodiments of the present application can timely detect, before the product distribution, whether the API on which the software to be distributed operates depends is too low, and so on whether the API version of the software to be distributed existing in the vehicle is too low, which can timely detect whether the product collides with the vehicle before the product distribution, thereby avoiding the situation that the product cannot operate in the vehicle, and providing a smooth foundation for the safe distribution and running of the product.
Referring to fig. 3, a flowchart of a collision detection method according to an embodiment of the application is shown. The method comprises the following procedures.
S301, obtaining model information of a vehicle to which software to be released is to be released.
In some embodiments, after acquiring a vehicle identifier of a vehicle to which software to be distributed is to be distributed, the electronic device acquires model information of the vehicle based on a mapping relationship between the vehicle identifier and the model information.
In other embodiments, the electronic device further includes a model information input box at which a technician can input model information of the vehicle.
S302, determining a capability set on which software to be released depends and a capability set corresponding to model information.
The capability set on which the software to be distributed depends refers to a set of capabilities that the software to be distributed needs to have to run in a vehicle. The capability set corresponding to the model information is a capability set of the vehicle of the model information.
S303, judging whether the capability set corresponding to the model information is matched with the capability set on which the software to be distributed depends.
Optionally, the electronic device determines whether the capability set corresponding to the model information matches the capability set on which the software to be deployed depends according to the following steps: for each capability information in the capability set on which the software to be released depends, detecting whether the capability information belongs to the capability set corresponding to the model information; if each piece of capability information included in the capability set on which the software to be released depends belongs to the capability set corresponding to the model information, the capability set corresponding to the model information is matched with the capability set on which the software to be released depends; if the capability set on which the software to be released depends has at least one capability set of which the capability information does not belong to the capability set corresponding to the model information, the capability set corresponding to the model information is not matched with the capability set on which the software to be released depends.
For example, the functions implemented by the software to be distributed are: and controlling the sunroof of the vehicle, wherein the capability set relied on by the sunroof comprises the capability of remote control of the sunroof, and if the vehicle of the model A does not support remote control of the sunroof, the capability set corresponding to the model information is not matched with the capability set relied on by the software to be distributed.
S304, if the capability set corresponding to the model information is not matched with the capability set on which the software to be distributed depends, determining that the software to be distributed collides with the vehicle.
At this time, the electronic device does not need to perform the subsequent API information detection step.
S305, if the capability set corresponding to the model information is matched with the capability set on which the software to be issued depends, judging whether the software to be issued collides with the vehicle according to the first API information and the second API information. In the embodiment of the application, whether the software to be distributed conflicts with the vehicle or not is judged according to the first API information and the second API information, which comprises the following steps: if any API in the first API information is not contained in the second API information, or any API in the first API information is contained in the second API information, and the version information of the API is higher than the version information of the API in the second API information, determining that the software to be distributed conflicts with the vehicle; if each API in the first API information is contained in the second API information and the version information of each API is lower than the version information of the API in the second API information, determining that the software to be distributed does not conflict with the vehicle. The specific explanation thereof can be found in the embodiment of fig. 2 and the embodiment of fig. 4, and will not be described herein.
In summary, according to the technical scheme provided by the embodiment of the application, the capability set corresponding to the model information of the vehicle and the capability set on which the software to be distributed depends are firstly obtained, then whether the software to be distributed and the vehicle conflict is detected, if the software to be distributed and the vehicle conflict is not detected, the conflict between the software to be distributed and the vehicle is indicated, whether the vehicle of the model information has all the capabilities on which the software to be distributed depends in operation can be detected before the product is distributed, whether the product conflicts with the vehicle of the model information can be detected in time before the product is distributed, the condition that the product cannot operate in the vehicle of the model information after the product is distributed is avoided, and a foundation is provided for safe distribution and smooth operation of the product.
Referring to fig. 4, a flowchart of a collision detection method according to an embodiment of the application is shown. The method comprises the following procedures.
S401, determining API information of an application program interface, on which the software to be released depends, wherein the API information is used for indicating at least one API on which the software to be released depends and version information of each API.
S402, acquiring a vehicle identifier of a vehicle to which software to be released is to be released.
S403, determining second API information corresponding to the vehicle identification, wherein the second API information is used for indicating at least one API associated with the vehicle and version information of each API.
S404, if each API in the first API information is contained in the second API information and the version information of each API is lower than the version information of the API in the second API information, determining that the software to be distributed does not conflict with the vehicle.
Each API in the first API information is contained in the second API information, and version information of each API is lower than version information of the API in the second API information, which means that the vehicle is provided with all APIs required by running of the software to be distributed, the APIs of the vehicle are of higher versions, the software to be distributed can run in the vehicle, and the software to be distributed does not conflict with the vehicle.
S405, in response to no conflict exists between the software to be distributed and the vehicle, sending a data packet of the software to be distributed to the vehicle to which the software to be distributed is to be distributed.
In the embodiment of the application, if the software to be distributed does not conflict with the vehicle, the electronic device can send the data packet of the software to be distributed to the vehicle to which the software to be distributed is distributed so as to realize the software distribution, and thus, a user of the vehicle can download and install the software to be distributed in an application store.
In some embodiments, the electronic device may send a data packet of the software to be distributed to the vehicle after receiving the distribution instruction. The issuing instruction can be triggered by a technician or by the electronic device itself after a predetermined issuing time is reached. The data packet may include authority information of the software to be issued, the authority information characterizes usage authority of at least one API indicated by the first API information to be acquired by the software to be issued, and the subsequent vehicle to be issued may authorize the issued software according to the authority information, so that the software may run smoothly in the vehicle.
In summary, according to the technical scheme provided by the embodiment of the application, the first API information on which the product to be distributed operates is acquired, then the second API information associated with the vehicle to be distributed of the software to be distributed is acquired, if the second API information includes all APIs included in the first API information and version information of the APIs included in the second API information is higher than version information of the APIs in the first API information, it is indicated that the software to be distributed and the vehicle do not collide, the software to be distributed can operate in the vehicle, at this time, the electronic device distributes the software to be distributed to the vehicle, so that occurrence of the situation that the product cannot operate in the vehicle after distribution can be avoided, and a foundation is provided for safe distribution and smooth operation of the product.
Referring to fig. 5, a block diagram of a collision detection apparatus according to an embodiment of the present application is shown. The device comprises: a first information determination module 510, an identification acquisition module 520, a second information determination module 530, and a collision detection module 550.
The first information determining module 510 is configured to determine first application program interface API information on which the software to be released depends, where the first API information is configured to indicate at least one API on which the software to be released depends and version information of each API.
The identifier obtaining module 520 is configured to obtain a vehicle identifier of a vehicle to which the software to be distributed is to be distributed.
The second information determining module is used for determining second API information corresponding to the vehicle identification, and the second API information is used for indicating at least one API associated with the vehicle and version information of each API.
The conflict detection module 550 is configured to determine that the software to be distributed conflicts with the vehicle if any one of the first API information is not included in the second API information, or if any one of the first API information is included in the second API information and the version information of the API is higher than the version information of the API in the second API information.
In some embodiments, the apparatus further comprises: a model acquisition module and a capability set determination module (not shown in the figure).
The model acquisition module is used for acquiring the model information of the vehicle. And the capability set determining module is used for determining a capability set on which the software to be distributed depends and a capability set corresponding to the model information. The conflict detection module 550 is further configured to determine whether the capability set corresponding to the model information matches a capability set on which the software to be deployed depends; if the capability set corresponding to the model information is not matched with the capability set on which the software to be distributed depends, determining that the software to be distributed collides with the vehicle.
In some embodiments, the conflict detection module 540 is configured to determine whether the software to be issued conflicts with the vehicle according to the first API information and the second API information if the capability set corresponding to the model information matches the capability set of the software to be issued.
In some embodiments, the conflict detection module 540 is specifically configured to detect, for each capability information in the capability set on which the software to be released depends, whether the capability information belongs to a capability set corresponding to the model information; if each piece of capability information included in the capability set on which the software to be released depends belongs to the capability set corresponding to the model information, the capability set corresponding to the model information is matched with the capability set on which the software to be released depends; if the capability set on which the software to be released depends has at least one capability set of which the capability information does not belong to the capability set corresponding to the model information, the capability set corresponding to the model information is not matched with the capability set on which the software to be released depends.
In some embodiments, the apparatus further comprises: a software release module (not shown). The conflict detection module 540 is configured to determine that the software to be deployed and the vehicle do not conflict if each API in the first API information is included in the second API information and the version information of each API is lower than the version information of the API in the second API information. And the software release module is used for transmitting the data packet of the software to be released to the vehicle to which the software to be released is to be released in response to the fact that the software to be released does not conflict with the vehicle.
In some embodiments, the identifier obtaining module 520 is configured to obtain tag information of an application to be deployed; user portrait information of owners of a plurality of vehicles is respectively acquired; and determining the vehicle identification of the vehicle to which the software to be distributed is to be distributed based on the user image information of the vehicle owners to which the vehicles belong and the label information of the application programs to be distributed.
In summary, the technical scheme provided by the embodiment of the application acquires the first API information on which the product to be issued runs, then acquires the second API information associated with the vehicle on which the software to be issued is to be issued, if the first API information contains the API information which is not contained in the second API information, it is indicated that the API associated with the vehicle lacks the API required by the running of the software to be issued, if the first API information contains the version information of the API higher than the version information of the API in the second API information, it is indicated that the version information of the API associated with the vehicle is too low, either of the above two conditions happen, which indicates that the software to be issued collides with the vehicle, and the software to be issued cannot run in the vehicle, that is, if so, the technical scheme provided by the embodiment of the application can timely detect whether the API on which the running of the software to be issued depends exists in the vehicle is too low before the product is issued, so as to timely detect whether the product collides with the vehicle, avoid the situation that the product cannot run in the vehicle before the product is issued, and provide a smooth basis for the safe issuing and running of the product.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus and modules described above may refer to the corresponding process in the foregoing method embodiment, which is not repeated herein.
In several embodiments provided by the present application, the coupling of the modules to each other may be electrical, mechanical, or other.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
Referring to fig. 6, an electronic device 600 is further provided according to an embodiment of the present application, where the electronic device 600 includes: one or more processors 610, memory 620, ultrasonic radar, lidar, and one or more applications. Wherein one or more application programs are stored in the memory 620 and configured to be executed by the one or more processors 66, the one or more application programs configured to perform the methods described in the above embodiments.
Processor 610 may include one or more processing cores. The processor 610 connects various parts within the overall battery management system using various interfaces and lines, performs various functions of the battery management system and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 620, and invoking data stored in the memory 620. Alternatively, the processor 610 may be implemented in at least one hardware form of digital signal Processing (DIGITAL SIGNAL Processing, DSP), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 610 may integrate one or a combination of several of the central processor 610 (Central Processing Unit, CPU), the image processor 66 (Graphics Processing Unit, GPU), and modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 610 and may be implemented solely by a single communication chip.
The Memory 620 may include a random access Memory 620 (Random Access Memory, RAM) or a Read-Only Memory 620. Memory 620 may be used to store instructions, programs, code sets, or instruction sets. The memory 620 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, etc. The storage data area may also store data created by the electronic device map in use (e.g., phonebook, audiovisual data, chat log data), and the like.
Embodiments of the present application also provide a computer readable storage medium having stored therein computer program instructions that are callable by a processor to perform the methods described in the above embodiments.
The computer readable storage medium may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium comprises a non-volatile computer readable storage medium (non-transitory computer-readable storage medium). The computer readable storage medium has storage space for computer program instructions to perform any of the method steps described above. These computer program instructions may be read from or written to one or more computer program products.
Although the present application has been described in terms of the preferred embodiments, it should be understood that the present application is not limited to the specific embodiments, but is capable of numerous modifications and equivalents, and alternative embodiments and modifications of the embodiments described above, without departing from the spirit and scope of the present application.

Claims (9)

1. A method of collision detection, the method comprising:
Determining first Application Program Interface (API) information on which to-be-published software operates, wherein the first API information is used for indicating at least one API on which to-be-published software operates and version information of each API; the first API information is information of an API which needs to be called by the software to be issued after the software to be issued is issued and in running;
Acquiring a vehicle identifier of a vehicle to which the software to be distributed is distributed;
determining second API information corresponding to the vehicle identifier, wherein the second API information is used for indicating at least one API associated with the vehicle and version information of each API;
And if any API in the first API information is not contained in the second API information, or any API in the first API information is contained in the second API information and the version information of the API in the first API information is higher than the version information of the API in the second API information, determining that the software to be distributed collides with the vehicle.
2. The method of claim 1, wherein the method further comprises:
Obtaining model information of the vehicle;
determining a capability set on which the software to be distributed depends and a capability set corresponding to the model information;
Judging whether the capability set corresponding to the model information is matched with the capability set on which the software to be distributed depends;
And if the capability set corresponding to the model information is not matched with the capability set on which the software to be distributed depends, determining that the software to be distributed collides with the vehicle.
3. The method of claim 2, wherein the method further comprises:
and if the capability set corresponding to the model information is matched with the capability set on which the software to be distributed depends, judging whether the software to be distributed and the vehicle have conflict according to the first API information and the second API information.
4. The method of claim 2, wherein determining whether the capability set corresponding to the model information matches the capability set on which the software to be distributed depends comprises:
for each capability information in the capability set on which the software to be distributed depends, detecting whether the capability information belongs to the capability set corresponding to the model information;
If each piece of capability information included in the capability set on which the software to be distributed depends belongs to the capability set corresponding to the model information, the capability set corresponding to the model information is matched with the capability set on which the software to be distributed depends;
If at least one capability set which is depended on by the software to be distributed does not belong to the capability set corresponding to the model information, the capability set corresponding to the model information is not matched with the capability set which is depended on by the software to be distributed.
5. The method according to claim 3, further comprising, after said determining whether there is a conflict between the software to be distributed and the vehicle based on the first API information and the second API information:
If each API in the first API information is contained in the second API information and the version information of each API is lower than the version information of the API in the second API information, determining that the software to be distributed does not conflict with the vehicle;
and responding to no conflict exists between the software to be distributed and the vehicle, and sending a data packet of the software to be distributed to the vehicle to which the software to be distributed is to be distributed.
6. The method according to any one of claims 1 to 4, wherein the obtaining a vehicle identification of a vehicle to which the software to be distributed is to be distributed, includes:
Acquiring label information of the application program to be issued;
user portrait information of owners of a plurality of vehicles is respectively acquired;
and determining the vehicle identification of the vehicle to which the software to be distributed is distributed based on the user portrait information of the vehicle owners to which the vehicles belong and the label information of the application program to be distributed.
7. A collision detection apparatus, characterized by comprising means for implementing the method of any one of claims 1 to 6.
8. An electronic device, comprising:
one or more processors;
A memory;
One or more applications, wherein one or more of the applications are stored in the memory and configured to be executed by one or more of the processors, the one or more applications configured to perform the method of any of claims 1-6.
9. A computer readable storage medium having stored therein computer program instructions which are callable by a processor to perform the method according to any one of claims 1 to 6.
CN202310648674.1A 2023-06-01 2023-06-01 Conflict detection method, device, electronic equipment and storage medium Active CN116881118B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310648674.1A CN116881118B (en) 2023-06-01 2023-06-01 Conflict detection method, device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310648674.1A CN116881118B (en) 2023-06-01 2023-06-01 Conflict detection method, device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN116881118A CN116881118A (en) 2023-10-13
CN116881118B true CN116881118B (en) 2024-05-14

Family

ID=88259367

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310648674.1A Active CN116881118B (en) 2023-06-01 2023-06-01 Conflict detection method, device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116881118B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004127253A (en) * 2002-07-31 2004-04-22 Ricoh Co Ltd Information processing apparatus and version check method
CN107656752A (en) * 2017-10-31 2018-02-02 北京新能源汽车股份有限公司 A kind of method, apparatus and vehicle of vehicle control device software upgrading
CN111061643A (en) * 2019-12-24 2020-04-24 五八同城信息技术有限公司 SDK cluster compatibility detection method and device, electronic equipment and storage medium
CN112015489A (en) * 2020-09-18 2020-12-01 华人运通(江苏)技术有限公司 Management method, device, storage medium and system for vehicle-mounted software
CN112416384A (en) * 2020-06-11 2021-02-26 上海哔哩哔哩科技有限公司 Software upgrading method and device and computer equipment
CN116126377A (en) * 2023-01-06 2023-05-16 北京新能源汽车股份有限公司 Vehicle upgrading method, device and processing equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004127253A (en) * 2002-07-31 2004-04-22 Ricoh Co Ltd Information processing apparatus and version check method
CN107656752A (en) * 2017-10-31 2018-02-02 北京新能源汽车股份有限公司 A kind of method, apparatus and vehicle of vehicle control device software upgrading
CN111061643A (en) * 2019-12-24 2020-04-24 五八同城信息技术有限公司 SDK cluster compatibility detection method and device, electronic equipment and storage medium
CN112416384A (en) * 2020-06-11 2021-02-26 上海哔哩哔哩科技有限公司 Software upgrading method and device and computer equipment
CN112015489A (en) * 2020-09-18 2020-12-01 华人运通(江苏)技术有限公司 Management method, device, storage medium and system for vehicle-mounted software
CN116126377A (en) * 2023-01-06 2023-05-16 北京新能源汽车股份有限公司 Vehicle upgrading method, device and processing equipment

Also Published As

Publication number Publication date
CN116881118A (en) 2023-10-13

Similar Documents

Publication Publication Date Title
WO2019233354A1 (en) Application preloading method and device, storage medium and terminal
CN112331214A (en) Equipment awakening method and device
CN107766747B (en) Method for verifying integrity of application program installation package, mobile terminal and server
CN105100218B (en) Vehicle evaluation method, device and system based on automobile data recorder
EP3617889B1 (en) Stutter detection method and device
WO2018103402A1 (en) Wireless fidelity (wifi) scan method and related product
CN111738316B (en) Zero sample learning image classification method and device and electronic equipment
CN113911872B (en) Fault processing method and system and early warning rescue system
US20200126385A1 (en) Information processing apparatus, information processing system and information processing method
CN111757123A (en) Distributed video decoding system, video decoding output method and device
CN109561134B (en) Electronic device, distributed cluster service distribution method and storage medium
CN116881118B (en) Conflict detection method, device, electronic equipment and storage medium
CN112214770B (en) Malicious sample identification method, device, computing equipment and medium
CN102377793B (en) Flash interaction method and device based on mobile communication equipment terminal
CN113138852A (en) Resource loading method and device, chip and electronic equipment
CN111417908A (en) ECU (electronic control Unit) recognizer, and recognition method, system, equipment and medium thereof
US11102616B2 (en) Method of tracking objects using thermostat
CN114172686A (en) Vehicle-mounted CAN bus message intrusion detection method and related equipment
CN110069731B (en) Data processing method and device, electronic equipment and computer readable storage medium
CN109146694B (en) Electronic device, user vehicle insurance preference level determining method and storage medium
CN113760631A (en) Page loading duration determination method, device, equipment and storage medium
CN110851185A (en) Automatic configuration method and device for equipment, electronic equipment and storage medium
CN111770472A (en) Vehicle positioning method and device, vehicle, storage medium and terminal
CN113111692A (en) Target detection method and device, computer readable storage medium and electronic equipment
CN111352529A (en) Method, device, terminal and storage medium for reporting touch event

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant