CN116955168A - Vehicle-mounted software product running method and device, electronic equipment and storage medium - Google Patents
Vehicle-mounted software product running method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116955168A CN116955168A CN202310849433.3A CN202310849433A CN116955168A CN 116955168 A CN116955168 A CN 116955168A CN 202310849433 A CN202310849433 A CN 202310849433A CN 116955168 A CN116955168 A CN 116955168A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- software product
- created
- conflict
- mounted software
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000001514 detection method Methods 0.000 claims description 66
- 230000002159 abnormal effect Effects 0.000 abstract description 4
- 238000012986 modification Methods 0.000 description 11
- 230000004048 modification Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 125000004122 cyclic group Chemical group 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 239000011159 matrix material Substances 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a vehicle-mounted software product running method, a device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: determining a conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product as the conflict relation to be created; adding the conflict relation to be created to the initial relation list to obtain a target relation list; if the conflict relation to be created is incomplete conflict, creating a vehicle-mounted software product to be created; if the vehicle-mounted software product to be created reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product; acquiring a target conflict relation between a vehicle-mounted software product to be created and a target vehicle-mounted software product from a target relation list; and controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation. According to the application, accurate positioning of the conflict relation of the products in different stages of software creation, operation and the like is realized, and the problem that the operation is abnormal or can not be operated due to the conflict of the products is reduced.
Description
Technical Field
The present application relates to the field of vehicle management technologies, and in particular, to a method, an apparatus, an electronic device, and a computer readable storage medium for running a vehicle-mounted software product.
Background
With the development of intelligent network connection of automobiles, more and more software products are loaded on the automobiles, different sources of different software products can be carried by the automobiles when the automobiles leave the factories, and the automobiles can also be loaded by the automobiles after the automobiles leave the factories or by the upgrading of the automobiles or the users are custom-created, so that the running environment of the automobile software products presents a trend of being more and more complex, even product conflict can occur, and the running of the products is abnormal or can not be performed.
Therefore, a means is needed to ensure that the products do not interfere with each other during operation, providing a good use experience for the user.
Disclosure of Invention
The application provides a vehicle-mounted software product running method, a vehicle-mounted software product running device, electronic equipment and a computer readable storage medium, so as to overcome the defects.
In a first aspect, an embodiment of the present application provides a method for operating a vehicle-mounted software product, where the method includes: determining a conflict relation between a vehicle-mounted software product to be created and the created vehicle-mounted software product, wherein the vehicle-mounted software product is a software product in a vehicle; adding the conflict relation to be created to the initial relation list to obtain a target relation list; the initial relationship list includes conflicting relationships between each of the created onboard software products; if the conflict relation to be created is that the vehicle-mounted software product to be created and the established vehicle-mounted software product are not completely conflicted, the vehicle-mounted software product to be created is created, the incomplete conflict comprises that the conflict relation between the vehicle-mounted software product to be created and the established vehicle-mounted software product is not conflicted and the conflict relation between the vehicle-mounted software product to be created and the established vehicle-mounted software product is not conflicted under specific conditions; if the vehicle-mounted software product to be created reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product; acquiring a target conflict relation between a vehicle-mounted software product to be created and a target vehicle-mounted software product from a target relation list; and controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
In a second aspect, an embodiment of the present application further provides an apparatus for running a vehicle-mounted software product, where the apparatus includes:
the system comprises a determining module, a judging module and a control module, wherein the determining module is used for determining a conflict relation between a vehicle-mounted software product to be created and the created vehicle-mounted software product, and the vehicle-mounted software product is a software product in a vehicle;
the adding module is used for adding the conflict relation to be created to the initial relation list to obtain a target relation list; the initial relationship list includes conflicting relationships between each of the created onboard software products;
the creating module is used for creating the vehicle-mounted software product to be created if the conflict relation to be created is incomplete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product, wherein the incomplete conflict comprises that the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict and the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict under a specific condition;
the first acquisition module is used for acquiring the created vehicle-mounted software product in the running state as a target vehicle-mounted software product if the vehicle-mounted software product to be created reaches the running condition;
The second acquisition module is used for acquiring a target conflict relation between the vehicle-mounted software product to be created and the target vehicle-mounted software product from the target relation list;
and the control module is used for controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
In a third aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes: 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 the one or more processors, the one or more applications configured to perform the above-described methods.
In a fourth aspect, embodiments of the present application also provide a computer readable storage medium storing program code executable by a processor, the program code when executed by the processor causing the processor to perform the above method.
According to the method, the device, the electronic equipment and the computer readable storage medium for operating the vehicle-mounted software product, the conflict relation between the vehicle-mounted software product to be created and the established vehicle-mounted software product is determined to be used as the conflict relation to be created, the conflict relation to be created is added to the initial relation list to obtain the target relation list, whether the vehicle-mounted software product to be created is established or not is determined according to the conflict relation to be created, when the vehicle-mounted software product to be created is successfully created and reaches the operating condition, the target conflict relation between the vehicle-mounted software product to be created and the established vehicle-mounted software product in the operating condition is obtained from the target relation list, the operating condition of the vehicle-mounted software product to be created is further controlled according to the target conflict relation, and accurate positioning of the product conflict relation in different stages of software creation, operation and the like is achieved, so that whether the product is created and how to operate the product is controlled after the creation is successful can be determined according to the clear product conflict relation, the problem of abnormal operation or incapacity of operation caused by the product conflict is reduced, and user experience is improved. Meanwhile, the conflict relation between the vehicle-mounted software products can be determined according to the target relation list, so that the conflict relation between the vehicle-mounted software products can be prevented from being repeatedly added, the vehicle-mounted software products can be repeatedly detected, and the product research and development efficiency and the product creation efficiency are improved.
Additional features and advantages of embodiments of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of embodiments of the application. The objectives and other advantages of embodiments of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
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 illustrates a flow chart of a method of operating an in-vehicle software product according to one embodiment of the application.
Fig. 2 shows a flow chart of a method of operating an in-vehicle software product according to a further embodiment of the application.
Fig. 3 shows a block diagram of an in-vehicle software product running apparatus according to an embodiment of the present application.
Fig. 4 shows a schematic diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the present application better understood by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that: like reference numerals and letters denote clustered items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Referring to fig. 1, fig. 1 shows a flowchart of a method for running a vehicle-mounted software product according to an embodiment of the present application, where the method includes:
s101, determining a conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product as the conflict relation to be created.
The vehicle-mounted software product is a software product carried in a vehicle, and can be a software product used for serving a user in the vehicle, such as audio/video playing software and the like.
In some embodiments, S101 may include: and according to the operating conditions of the created vehicle-mounted software product and the calling service, performing conflict detection on the operating conditions of the vehicle-mounted software product to be created and the calling service to obtain a conflict relation to be created.
The running conditions of the vehicle-mounted software product comprise condition nodes and condition parameters, and the service called when the running conditions are met comprises service nodes and service parameters, which are shown in the table 1 in detail:
TABLE 1 operating conditions and call service Table for on-Board software products
In some embodiments, the conflict relationship between the on-board software product to be created and the created on-board software product may be a complete conflict relationship, or may be an incomplete conflict relationship, where complete conflict and refers to that the on-board software product to be created and the created on-board software product are in a conflict relationship at runtime. The incomplete conflict relationship includes that the conflict relationship between the on-board software product to be created and the created on-board software product is a non-conflict relationship and that the conflict relationship between the on-board software product to be created and the created on-board software product is a non-conflict relationship under specific conditions. The specific condition refers to a condition that the vehicle-mounted software product to be created does not conflict with the created vehicle-mounted software product, and may be an operation sequence of the vehicle-mounted software product to be created and the created vehicle-mounted software product, or may be other conditions, which is not limited herein.
For example, the running condition of the vehicle-mounted software product A is that the vehicle speed is greater than 70km/h, the running condition of the vehicle-mounted software product B is that the vehicle speed is greater than 80km/h, and if the vehicle-mounted software product B is firstly run, the vehicle-mounted software product A and the vehicle-mounted software product B can both run, i.e. the running vehicle-mounted software product A and the vehicle-mounted software product B do not collide; if the vehicle-mounted software product A is operated firstly, but the vehicle speed is more than 70km/h and less than or equal to 80km/h, the vehicle-mounted software product B cannot be operated at the moment, namely the vehicle-mounted software product A and the vehicle-mounted software product B are operated to generate conflict. The vehicle-mounted software product A and the vehicle-mounted software product B do not conflict under specific conditions, and the conflict relationship between the vehicle-mounted software product A and the vehicle-mounted software product B is an incomplete conflict relationship. The specific condition here is that the in-vehicle software product a runs before the in-vehicle software product B and that the in-vehicle software product B runs before the in-vehicle software product a.
S102, adding the conflict relation to be created to the initial relation list to obtain a target relation list.
Wherein the initial relationship list includes conflicting relationships between each of the created in-vehicle software products.
In some implementations, the conflicting relationship and the initial relationship list can be represented mathematically, and the initial relationship list can be represented in the form of a conflicting relationship matrix.
For example, the in-vehicle software product B and the in-vehicle software product C completely conflict, i.e., no matter which one is running first, the conflict relationship between the in-vehicle software product B and the in-vehicle software product C may be expressed as B = (0, 0); the vehicle-mounted software product B is firstly operated and then the vehicle-mounted software product C is operated without conflict, but if the vehicle-mounted software product C is firstly operated and then the vehicle-mounted software product B is operated, the conflict relation between B and C can be expressed as: b ∈c= (1, 0); the vehicle-mounted software product B is firstly operated and then the vehicle-mounted software product C is operated to conflict, but the vehicle-mounted software product B is firstly operated and then the vehicle-mounted software product C is operated to not conflict, and the conflict relation between B and C can be expressed as: b ∈c= (0, 1); in-vehicle software product B does not conflict at all with in-vehicle software product C, and the conflict relationship of B and C can be expressed as: b ∈c= (1, 1). According to the above-described conflicting relationship expression, a conflicting relationship matrix expression initial relationship list as shown in table 2 may be generated.
Table 2 conflict matrix table
And S103, if the conflict relation to be created is that the vehicle-mounted software product to be created is not completely in conflict with the created vehicle-mounted software product, creating the vehicle-mounted software product to be created.
Wherein the incomplete conflict relationship includes that the conflict relationship between the vehicle-mounted software product to be created and the created vehicle-mounted software product is a non-conflict relationship and that the conflict relationship between the vehicle-mounted software product to be created and the created vehicle-mounted software product is a non-conflict relationship under specific conditions.
The on-board software product to be created is created for an on-board software product to be created that does not completely conflict with the on-board software product already created, i.e. is represented in the target relationship list as (1, 1), (1, 0), (0, 1).
If the conflict relation to be created is that the vehicle-mounted software product to be created and the created vehicle-mounted software product are in complete conflict, namely (0, 0) is represented in the target relation list, the vehicle-mounted software product to be created is not created.
And S104, if the vehicle-mounted software product to be created reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product.
Wherein the target in-vehicle software product comprises at least one created in-vehicle software product.
Taking the in-vehicle software product A, B, C, D as an example, if the in-vehicle software products A, B, C all reach the operation condition and have operated, the in-vehicle software product D does not reach the operation condition, and the in-vehicle software product A, B, C is obtained as the target in-vehicle software product.
If the vehicle-mounted software product to be created reaches the operation condition, the created vehicle-mounted software product in the operation state does not exist, and the vehicle-mounted software product to be created, which is successfully created, is directly operated.
S105, acquiring a target conflict relation between the vehicle-mounted software product to be created and the target vehicle-mounted software product from the target relation list.
Wherein the target conflict relationship comprises a conflict relationship between the on-board software product to be created and each of the created on-board software products in the target on-board software product.
Taking the vehicle-mounted software product to be created as X, the target vehicle-mounted software product includes a vehicle-mounted software product A, B, C as an example, and the target conflict relationship between the vehicle-mounted software product to be created and the target vehicle-mounted software product, that is, the respective conflict relationship between the vehicle-mounted software product X and the vehicle-mounted software product A, B, C, is obtained from the target relationship list.
S106, controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
After the target conflict relation between the vehicle-mounted software product to be created and the target vehicle-mounted software product is obtained, the running state of the vehicle-mounted software product to be created is controlled according to the target conflict relation. The running state of the vehicle-mounted software product may include whether the vehicle-mounted software product continues to run, how the vehicle-mounted software product runs, and the like.
If the created vehicle-mounted software product B is in an operating state, the vehicle-mounted software product A to be created needs to control the operating state of the vehicle-mounted software product A according to the target conflict relation between the vehicle-mounted software product A and the vehicle-mounted software product A, wherein the operating state of the vehicle-mounted software product A can be that the vehicle-mounted software product A is operated after the vehicle-mounted software product B is waited for ending operation, or the vehicle-mounted software product B is controlled to pause and directly operated, and the vehicle-mounted software product A continues to operate after the vehicle-mounted software product A is operated.
In some embodiments, the target in-vehicle software product includes a plurality of target conflict relationships including a plurality of target conflict relationships, one target conflict relationship being a conflict relationship between one target in-vehicle software product and an in-vehicle software product to be created; s106 may include: if the multiple target conflict relations meet the target conditions, running the successfully created vehicle-mounted software product to be created; if at least one target conflict relation does not meet the target condition, acquiring a target vehicle-mounted software product corresponding to the target conflict relation which does not meet the target condition from a plurality of target vehicle-mounted software products as a vehicle-mounted software product to be processed; and controlling the running state of the vehicle-mounted software product to be created according to the running priority of the vehicle-mounted software product to be processed and the running priority of the vehicle-mounted software product to be created.
Wherein the running priority of the on-board software product is set at the time of creation of the product, and can be set according to the importance of the on-board software product in running the vehicle, for example, the running priority of the on-board software product related to vehicle safety is higher than the running priority of the on-board software product related to entertainment.
In some embodiments, the target condition may be that the target conflict relationship is that the on-board software product to be created does not conflict at all with the target on-board software product corresponding to the target conflict relationship, or that the target on-board software product is run first and then the on-board software product to be created does not conflict, but if the on-board software product to be created is run first and then the target on-board software product conflicts. That is, the target condition may be that the conflict relationship between the on-vehicle software product to be created and the target on-vehicle software product corresponding to the target conflict relationship is (1, 0) or (1, 1).
Taking the vehicle-mounted software product to be created as X, taking the vehicle-mounted software product A, B, C as an example, if A & ltX & gt= (1, 0) or A & ltX & gt= (1, 1), B & ltX & gt= (1, 0) or B & ltX & gt= (1, 1), C & ltX & gt= (1, 0) or C & ltX & gt= (1, 1), directly running the vehicle-mounted software product to be created, wherein the vehicle-mounted software product to be created is successfully created, and if the conflict relation between one target vehicle-mounted software product and X is (0, 1), the target vehicle-mounted software product which does not meet the target condition is obtained as the vehicle-mounted software product to be processed; and controlling the running state of the vehicle-mounted software product to be created according to the running priority of the vehicle-mounted software product to be processed and the running priority of the vehicle-mounted software product to be created.
In some embodiments, controlling the running state of the on-board software product to be created according to the running priority of the on-board software product to be processed and the running priority of the on-board software product to be created may include: and if the operation priority of the vehicle-mounted software product to be processed is the same as the operation priority of the vehicle-mounted software product to be created, controlling the operation state of the vehicle-mounted software product to be created according to the operation principle.
The operation principle can be a first-come-first-come principle, a second-come-later-come principle, a safety product priority principle, a driving function related product priority principle and the like, and can be set according to requirements, and the application is not particularly limited.
And if the operation priority of the vehicle-mounted software product to be processed is higher than that of the vehicle-mounted software product to be created, waiting for the vehicle-mounted software product to be processed to finish operation and then operating the vehicle-mounted software product to be created.
If the operation priority of the vehicle-mounted software product to be processed is lower than that of the vehicle-mounted software product to be created, directly operating the vehicle-mounted software product to be created, and directly ending the operation of the vehicle-mounted software product to be processed or suspending the operation of the vehicle-mounted software product to be created and then operating the vehicle-mounted software product after the operation of the vehicle-mounted software product to be created is stopped.
In this embodiment, the conflict relationship between the vehicle-mounted software product to be created and the created vehicle-mounted software product is determined as the conflict relationship to be created, the conflict relationship to be created is added to the initial relationship list, a target relationship list is obtained, whether the vehicle-mounted software product to be created is determined according to the conflict relationship to be created, when the vehicle-mounted software product to be created is successfully created and reaches the operation condition, the target conflict relationship between the vehicle-mounted software product to be created and the created vehicle-mounted software product in the operation state is obtained from the target relationship list, and then the operation state of the vehicle-mounted software product to be created is controlled according to the target conflict relationship, so that accurate positioning of the product conflict relationship in different stages of software creation, operation and the like is realized, whether the product is created and how to control the operation of the product after the creation is successful can be determined, the problem of abnormal operation or incapacitated due to the product conflict is reduced, and the user experience is improved. Meanwhile, the conflict relation between the vehicle-mounted software products can be determined according to the target relation list, so that the conflict relation between the vehicle-mounted software products can be prevented from being repeatedly added, the vehicle-mounted software products can be repeatedly detected, the product research and development efficiency and the product creation efficiency are improved, and the user experience is improved.
Referring to fig. 2, fig. 2 shows a flowchart of a method for running an in-vehicle software product according to another embodiment of the present application, where the method includes:
s201, performing conflict detection on the operating conditions of the created vehicle-mounted software product and the operating conditions of the vehicle-mounted software product to be created, and obtaining a condition conflict detection result.
In some embodiments, if the operating condition of the created in-vehicle software product is established, the operating condition of the in-vehicle software product to be created is necessarily established, or the operating condition of the in-vehicle software product to be created is established, the operating condition of the in-vehicle software product to be created and the operating condition of the created in-vehicle software product are inclusion relationship. For example, the operating conditions α of the created in-vehicle software product are: the running speed of the vehicle is greater than 80km/h, and the running condition beta of the vehicle-mounted software product to be created is as follows: when the vehicle running speed is greater than 70km/h and alpha is true, beta is necessarily true, and the condition alpha is included in beta and recorded
If the operating condition of the vehicle-mounted software product to be created and the operating condition of the created vehicle-mounted software product are in an inclusion relationship or an equal relationship, the operating condition of the vehicle-mounted software product to be created can be modified, so that the modified operating condition of the vehicle-mounted software product to be created and the operating condition of the created vehicle-mounted software product are in a different relationship.
In some embodiments, if the operating conditions of the created in-vehicle software product are the same as the operating conditions of the in-vehicle software product to be created, then the operating conditions of the in-vehicle software product to be created and the operating conditions of the created in-vehicle software product are in equal relationship. For example, the on-board software product to be created and the created on-board software product are triggered by the same voice command, and the voice command triggering conditions of the two products are respectively denoted as α and β, and the conditions α and β are equal, which is denoted as α=β.
In some embodiments, if the operating conditions of the created in-vehicle software product are different from the operating conditions of the in-vehicle software product to be created and do not belong to the inclusion relationship, the operating conditions of the in-vehicle software product to be created and the operating conditions of the created in-vehicle software product are in a different relationship. For example, the operating condition α of the on-board software product to be created, the operating condition of the created on-board software product being β, if the conditions α and β are different, it is noted that
When the relation between the running conditions of the two vehicle-mounted software products is a containing relation or a different relation, the condition conflict detection result is incomplete conflict between the vehicle-mounted software products to be created and the created vehicle-mounted software products; when the relation between the running conditions of the two vehicle-mounted software products is equal, the condition conflict detection result is that the vehicle-mounted software products to be created and the created vehicle-mounted software products are in complete conflict.
S202, performing conflict detection on the call service of the created vehicle-mounted software product and the call service of the vehicle-mounted software product to be created, and obtaining a service conflict detection result.
In some embodiments, the invoked service interface of the created in-vehicle software product may or may not coincide with the invoked service interface of the in-vehicle software product to be created.
When the called service interfaces are not coincident, the service conflict detection result is incomplete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product; when the called service interfaces are coincident, the service conflict detection result is a complete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product.
S203, determining a conflict relation to be created according to the condition conflict detection result and the service conflict detection result.
When at least one of the condition conflict detection result and the service conflict detection result is that the vehicle-mounted software product to be created and the established vehicle-mounted software product are in complete conflict, the conflict relation to be created is that the vehicle-mounted software product to be created and the established vehicle-mounted software product are in complete conflict, otherwise, the conflict relation to be created is that the vehicle-mounted software product to be created and the established vehicle-mounted software product are not in complete conflict.
In some embodiments, S203 may include: determining a cycle conflict detection result according to a first correlation and a second correlation, wherein the first correlation refers to a correlation between an operation result of a calling service of a vehicle-mounted software product to be created and an operation condition of the created vehicle-mounted software product, and the second correlation refers to a correlation between an operation result of the calling service of the created vehicle-mounted software product and the operation condition of the vehicle-mounted software product to be created; and determining a conflict relation to be created according to the condition conflict detection result, the service conflict detection result and the cyclic conflict detection result. The correlation may include that the operation result of the former is the operation condition of the latter, and that the operation result of the former is not the operation condition of the latter.
When the first correlation includes that the operation result of the calling service of the vehicle-mounted software product is the operation condition of the created vehicle-mounted software product, and the second correlation includes that the operation result of the calling service of the created vehicle-mounted software product is the operation condition of the vehicle-mounted software product to be created, determining that the cycle conflict detection result is the complete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product, otherwise, determining that the cycle conflict detection result is the incomplete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product.
When at least one of the condition conflict detection result, the service conflict detection result and the cycle conflict detection result is the complete conflict between the vehicle-mounted software product to be created and the established vehicle-mounted software product, the conflict relationship to be created is the complete conflict between the vehicle-mounted software product to be created and the established vehicle-mounted software product, otherwise, the conflict relationship to be created is the incomplete conflict between the vehicle-mounted software product to be created and the established vehicle-mounted software product.
When the conflict relation to be created is that the vehicle-mounted software product to be created and the created vehicle-mounted software product completely conflict, the mathematical expression of the complete conflict relation is (0, 0), and when the conflict relation to be created is that the vehicle-mounted software product to be created and the created vehicle-mounted software product do not completely conflict, the mathematical expression of the incomplete conflict relation can be determined by specific contents of a conditional conflict detection result, a service conflict detection result and a cyclic conflict detection result to be (1, 0) or (0, 1) or (1, 1).
Taking an on-board software product A to be created and an on-board software product B which is created as an example, if the running conditions of A and B are equal, or the result of the cycle conflict detection is that A and B completely conflict, the conflict relation of A and B is expressed as A ∈B = (0, 0); if the relation between the operating condition alpha of A and the operating condition beta of B is an inclusion relation and When the conflict relation between A and B is expressed as A #, B= (1, 0); if the relation between the operating condition alpha of A and the operating condition beta of B is an inclusion relation and +.>When the conflict relation between A and B is expressed as A #, B= (0, 1); if the operation conditions of a and B are different, the calling service is not coincident, and the result of the cyclic conflict detection is that a and B are not completely in conflict, the conflict relationship between a and B is expressed as a%b= (1, 1).
S204, adding the conflict relation to be created to the initial relation list to obtain a target relation list.
If the running condition of the vehicle-mounted software product to be created is modified, the corresponding conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is changed, and the changed conflict relation is added to the initial relation list.
The other descriptions of S204 refer to the descriptions of S102 above, and are not repeated here.
S205, if the service conflict detection result and the cycle conflict detection result are that the vehicle-mounted software product to be created and the created vehicle-mounted software product are not completely in conflict, and the condition conflict detection result is that the vehicle-mounted software product to be created and the created vehicle-mounted software product are completely in conflict, modifying the condition parameters in the operation condition of the vehicle-mounted software product to be created, and obtaining the modified vehicle-mounted software product.
Wherein, the complete conflict refers to the complete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product when running.
In the case that the conflict relationship is that the vehicle-mounted software product to be created and the established vehicle-mounted software product conflict completely only because the condition conflict detection result is that the vehicle-mounted software product to be created and the established vehicle-mounted software product conflict completely, that is, the relationship between the operation condition of the vehicle-mounted software product to be created and the operation condition of the established vehicle-mounted software product is equal, the condition parameters in the operation condition of the vehicle-mounted software product to be created can be modified, so that the condition conflict detection result is that the vehicle-mounted software product to be created and the established vehicle-mounted software product do not conflict completely, and the vehicle-mounted software product to be created after the condition parameters are modified is obtained to be the modified vehicle-mounted software product.
For example, the condition nodes of the vehicle-mounted software product A to be created and the created vehicle-mounted software product B are both vehicle running speeds, the condition parameters are more than 60km/h, the relation between the running conditions of A and B is equal, the condition parameters of A can be modified to be the condition parameters in a mutually different relation with the running conditions of B, so that the A and the B after the condition parameters are modified are not completely collided, and the condition parameters of A can be modified to be less than 60km/h.
If the condition node of the created vehicle-mounted software product C is an air conditioner, the condition parameter is on (state), and the condition nodes of A and C are different, the condition parameters are also different, and the condition parameters of A cannot be modified so that A and B after the condition parameters are modified do not completely conflict.
S206, creating a modified vehicle-mounted software product; determining a modification conflict relationship between the modified vehicle-mounted software product and the created vehicle-mounted software product; and replacing the conflict relation to be created in the target relation list with the modification conflict relation to obtain a modification relation list.
Creating a modified vehicle-mounted software product, and modifying the conflict relation between the vehicle-mounted software product and the created vehicle-mounted software product into the conflict relation after the condition parameters are modified, namely modifying the conflict relation.
And after the modification conflict relation is acquired, replacing the corresponding conflict relation to be created as the modification conflict relation.
S207, if the modified vehicle-mounted software product reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product; and acquiring the conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product from the modification relation list.
If the modified vehicle-mounted software product reaches the operation condition, the created vehicle-mounted software product in the operation state does not exist, and the modified vehicle-mounted software product which is successfully created is directly operated.
Wherein the target conflict relationship comprises a conflict relationship between the modified in-vehicle software product and each of the created in-vehicle software products.
S208, controlling the running state of the modified vehicle-mounted software product according to the conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product.
After the conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product is obtained, the running state of the successfully created modified vehicle-mounted software product is controlled according to the target conflict relation.
In some implementations, the target in-vehicle software product includes a plurality, and the conflicting relationship between the modified in-vehicle software product and the target in-vehicle software product includes a plurality; s208 may include: if the conflict relation between the modified vehicle-mounted software products and the target vehicle-mounted software products meets the target condition, operating the modified vehicle-mounted software products which are successfully created; if at least one modified conflict relation between the vehicle-mounted software product and the target vehicle-mounted software product does not meet the target condition, acquiring a target vehicle-mounted software product corresponding to the conflict relation which does not meet the target condition from the target vehicle-mounted software product as a vehicle-mounted software product to be processed; and controlling the running state of the modified vehicle-mounted software product according to the running priority of the vehicle-mounted software product to be processed and the running priority of the modified vehicle-mounted software product.
In some embodiments, controlling the operating state of the modified in-vehicle software product according to the operating priority of the in-vehicle software product to be processed and the operating priority of the modified in-vehicle software product may include: and if the operation priority of the vehicle-mounted software product to be processed is the same as the operation priority of the modified vehicle-mounted software product, controlling the operation state of the modified vehicle-mounted software product according to the operation principle.
And if the operation priority of the to-be-processed vehicle-mounted software product is higher than the operation priority of the modified vehicle-mounted software product, waiting for the to-be-processed vehicle-mounted software product to finish operation and then operating the modified vehicle-mounted software product.
If the operation priority of the vehicle-mounted software product to be processed is lower than the operation priority of the modified vehicle-mounted software product, directly operating the modified vehicle-mounted software product, and directly ending the operation of the vehicle-mounted software product to be processed or suspending the operation to wait for the operation of the modified vehicle-mounted software product to be finished and then operating.
In this embodiment, the conflict relationship to be created is determined by determining the condition conflict detection result, the service conflict detection result and the cycle conflict detection result between the vehicle-mounted software product to be created and the vehicle-mounted software product of the created pair, the determined conflict relationship to be created is higher in accuracy, and then the condition parameters of the vehicle-mounted software product to be created, of which the conflict relationship to be created is that the vehicle-mounted software product to be created and the vehicle-mounted software product to be created are completely in conflict, and the conflict relationship to be created meets the preset condition, are modified, so that compatibility between the vehicle-mounted software products and the selection range of the vehicle-mounted software product are improved.
Referring to fig. 3, fig. 3 is a block diagram illustrating a device for running a vehicle-mounted software product according to an embodiment of the present application. For an electronic device, the apparatus 300 comprises:
a determining module 301, configured to determine a conflict relationship between a vehicle-mounted software product to be created and a created vehicle-mounted software product, where the vehicle-mounted software product is a software product in a vehicle, as the conflict relationship to be created;
an adding module 302, configured to add the conflict relationship to be created to the initial relationship list, to obtain a target relationship list; the initial relationship list includes conflicting relationships between each of the created onboard software products;
a creating module 303, configured to create the on-vehicle software product to be created if the conflict relationship to be created is an incomplete conflict between the on-vehicle software product to be created and the created on-vehicle software product, where the incomplete conflict includes that the conflict relationship between the on-vehicle software product to be created and the created on-vehicle software product is non-conflict and that the conflict relationship between the on-vehicle software product to be created and the created on-vehicle software product is non-conflict under a specific condition;
a first obtaining module 304, configured to obtain, as a target vehicle-mounted software product, a created vehicle-mounted software product in an operating state if the vehicle-mounted software product to be created reaches an operating condition;
A second obtaining module 305, configured to obtain, from the target relationship list, a target conflict relationship between the vehicle-mounted software product to be created and the target vehicle-mounted software product;
and the control module 306 is used for controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
Optionally, the determining module 301 is further configured to perform conflict detection on the operating condition of the on-vehicle software product to be created and the calling service according to the operating condition of the created on-vehicle software product and the calling service, so as to obtain a conflict relationship to be created.
Optionally, the determining module 301 is further configured to perform conflict detection on the operating conditions of the created vehicle-mounted software product and the operating conditions of the vehicle-mounted software product to be created, so as to obtain a condition conflict detection result; performing conflict detection on the created calling service of the vehicle-mounted software product and the calling service of the vehicle-mounted software product to be created to obtain a service conflict detection result; and determining a conflict relation to be created according to the condition conflict detection result and the service conflict detection result.
Optionally, the determining module 301 is further configured to determine the cycle conflict detection result according to a first correlation and a second correlation, where the first correlation is a correlation between an operation result of a calling service of the vehicle-mounted software product to be created and an operation condition of the created vehicle-mounted software product, and the second correlation is a correlation between an operation result of a calling service of the created vehicle-mounted software product and an operation condition of the vehicle-mounted software product to be created; and determining a conflict relation to be created according to the condition conflict detection result, the service conflict detection result and the cyclic conflict detection result.
Optionally, the target vehicle-mounted software product comprises a plurality of target conflict relations, wherein one target conflict relation is a conflict relation between one target vehicle-mounted software product and the vehicle-mounted software product to be created; the control module 306 is further configured to run the vehicle-mounted software product to be created that is successfully created if the multiple target conflict relationships meet the target conditions; if at least one target conflict relation does not meet the target condition, acquiring a target vehicle-mounted software product corresponding to the target conflict relation which does not meet the target condition from a plurality of target vehicle-mounted software products as a vehicle-mounted software product to be processed; and controlling the running state of the vehicle-mounted software product to be created according to the running priority of the vehicle-mounted software product to be processed and the running priority of the vehicle-mounted software product to be created.
Optionally, the control module 306 is further configured to control an operation state of the on-board software product to be created according to an operation principle if the operation priority of the on-board software product to be processed is the same as the operation priority of the on-board software product to be created.
Optionally, the adding module 302 is further configured to modify a condition parameter in an operation condition of the on-board software product to be created to obtain a modified on-board software product if the service conflict detection result and the cycle conflict detection result are that the on-board software product to be created and the created on-board software product are not completely conflicting, and the condition conflict detection result is that the on-board software product to be created and the created on-board software product are completely conflicting, where the complete conflict refers to an operation time conflict between the on-board software product to be created and the created on-board software product; creating a modified vehicle-mounted software product; determining a modification conflict relationship between the modified vehicle-mounted software product and the created vehicle-mounted software product; replacing the conflict relation to be created in the target relation list with a modification conflict relation to obtain a modification relation list; if the modified vehicle-mounted software product reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product; acquiring a conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product from the modification relation list; and controlling the running state of the modified vehicle-mounted software product according to the conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software 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 addition, each function in each embodiment of the present application may be integrated into one processing module, 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. 4, a block diagram of an electronic device according to an embodiment of the application is shown. The electronic device 400 may be a smart phone, a tablet computer, an electronic book, a vehicle, or other electronic device capable of running an application program. The electronic device 400 of the present application may include one or more of the following components: a processor 410, a memory 420, and one or more applications. Wherein one or more application programs may be stored in the memory 420 and configured to be executed by the one or more processors 410, the one or more program(s) configured to perform the methods as described in the foregoing method embodiments.
Processor 410 may include one or more processing cores. The processor 410 utilizes various interfaces and lines to connect various portions of the overall electronic device 400, perform various functions of the electronic device 400, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 420, and invoking data stored in the memory 420. Alternatively, the processor 410 may be implemented in hardware in at least one 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 410 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a 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 410 and may be implemented solely by a single communication chip.
The Memory 420 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Memory 420 may be used to store instructions, programs, code sets, or instruction sets. The memory 420 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 (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the method embodiments described below, etc. The storage data area may also store data created by the electronic device 400 in use (e.g., phonebook, audiovisual data, chat log data), and the like.
As another aspect, the present application also provides a computer readable storage medium having stored therein program code that can be invoked by a processor to perform the method described in the above method 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 cluster of ROMs. Optionally, the computer readable storage medium comprises a non-volatile computer readable storage medium (non-transitoroompter-readabblestonemagemedium). The computer readable storage medium has storage space for program code to perform any of the method steps described above. The program code can be read from or written to one or more computer program products. The program code may be compressed, for example, in a suitable form.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be appreciated by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not drive the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method of operating an on-board software product, the method comprising:
determining a conflict relationship between the vehicle-mounted software product to be created and the created vehicle-mounted software product;
adding the conflict relation to an initial relation list to obtain a target relation list; the initial relationship list comprises conflict relationships among the created vehicle-mounted software products;
if the conflict relation to be created is incomplete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product, creating the vehicle-mounted software product to be created, wherein the incomplete conflict comprises that the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict and the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict under specific conditions;
If the vehicle-mounted software product to be created reaches an operation condition, acquiring a target conflict relation between the vehicle-mounted software product to be created and the target vehicle-mounted software product from the target relation list, wherein the target vehicle-mounted software product is the vehicle-mounted software product which is created and is in an operation state;
and controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
2. The method of claim 1, wherein the determining a conflicting relationship between an in-vehicle software product to be created and an in-vehicle software product that has been created comprises:
and according to the running conditions of the created vehicle-mounted software product and the invoked service, performing conflict detection on the running conditions of the vehicle-mounted software product to be created and the invoked service, and determining the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product.
3. The method according to claim 2, wherein the determining the conflict relation between the on-board software product to be created and the on-board software product to be created by conflict detection according to the operating condition of the on-board software product to be created and the invoked service, comprises:
Performing conflict detection on the operating conditions of the created vehicle-mounted software product and the operating conditions of the vehicle-mounted software product to be created to obtain a condition conflict detection result;
performing conflict detection on the called service of the created vehicle-mounted software product and the called service of the vehicle-mounted software product to be created to obtain a service conflict detection result;
and determining a conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product according to the condition conflict detection result and the service conflict detection result.
4. A method according to claim 3, wherein said determining a conflict relationship between an in-vehicle software product to be created and an in-vehicle software product that has been created based on said condition conflict detection result and said service conflict detection result comprises:
determining a cycle conflict detection result according to a first correlation and a second correlation, wherein the first correlation is a correlation between an operation result of a called service of the vehicle-mounted software product to be created and an operation condition of the created vehicle-mounted software product, and the second correlation is a correlation between an operation result of a called service of the created vehicle-mounted software product and an operation condition of the vehicle-mounted software product to be created;
And determining the conflict relation to be created according to the condition conflict detection result, the service conflict detection result and the cycle conflict detection result.
5. The method of claim 1, wherein the target in-vehicle software product comprises a plurality of target conflict relationships, the target conflict relationship comprising a plurality of target conflict relationships, one target conflict relationship being a conflict relationship between one target in-vehicle software product and the in-vehicle software product to be created;
and controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation, wherein the method comprises the following steps:
if the target conflict relationships meet target conditions, operating the vehicle-mounted software product to be created;
if at least one target conflict relation does not meet the target condition, acquiring a target vehicle-mounted software product corresponding to the target conflict relation which does not meet the target condition from a plurality of target vehicle-mounted software products as a vehicle-mounted software product to be processed; and controlling the running state of the vehicle-mounted software product to be created according to the running priority of the vehicle-mounted software product to be processed and the running priority of the vehicle-mounted software product to be created.
6. The method of claim 5, wherein controlling the operating state of the to-be-created in-vehicle software product according to the operating priority of the to-be-processed in-vehicle software product and the operating priority of the to-be-created in-vehicle software product comprises:
And if the operation priority of the vehicle-mounted software product to be processed is the same as the operation priority of the vehicle-mounted software product to be created, controlling the operation state of the vehicle-mounted software product to be created according to an operation principle.
7. A method according to claim 3, wherein said adding said conflicting relationship to an initial relationship list results in a target relationship list, said method further comprising:
if the service conflict detection result and the cycle conflict detection result are incomplete conflicts between the vehicle-mounted software product to be created and the created vehicle-mounted software product, and the condition conflict detection result is complete conflicts between the vehicle-mounted software product to be created and the created vehicle-mounted software product, modifying condition parameters in the operation condition of the vehicle-mounted software product to be created to obtain a modified vehicle-mounted software product, wherein the complete conflicts refer to operation-time conflicts between the vehicle-mounted software product to be created and the created vehicle-mounted software product;
creating the modified vehicle-mounted software product;
determining a conflicting relationship between the modified in-vehicle software product and the created in-vehicle software product;
Modifying a target relationship list according to the conflict relationship between the modified vehicle-mounted software product and the created vehicle-mounted software product to obtain a modified relationship list;
if the modified vehicle-mounted software product reaches the operation condition, acquiring the created vehicle-mounted software product in the operation state as a target vehicle-mounted software product;
acquiring a conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product from the modified relation list;
and controlling the running state of the modified vehicle-mounted software product according to the conflict relation between the modified vehicle-mounted software product and the target vehicle-mounted software product.
8. An in-vehicle software product execution apparatus, the apparatus comprising:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a conflict relation between a vehicle-mounted software product to be created and a created vehicle-mounted software product, and the vehicle-mounted software product is a software product in a vehicle;
the adding module is used for adding the conflict relation to be created to an initial relation list to obtain a target relation list; the initial relationship list comprises conflict relationships among the created vehicle-mounted software products;
The creating module is used for creating the vehicle-mounted software product to be created if the conflict relation to be created is incomplete conflict between the vehicle-mounted software product to be created and the created vehicle-mounted software product, wherein the incomplete conflict comprises that the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict and the conflict relation between the vehicle-mounted software product to be created and the created vehicle-mounted software product is non-conflict under specific conditions;
the first acquisition module is used for acquiring the created vehicle-mounted software product in the running state as a target vehicle-mounted software product if the vehicle-mounted software product to be created reaches the running condition;
the second acquisition module is used for acquiring a target conflict relation between the vehicle-mounted software product to be created and the target vehicle-mounted software product from the target relation list;
and the control module is used for controlling the running state of the vehicle-mounted software product to be created according to the target conflict relation.
9. An electronic device, comprising:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the method of any of claims 1-7.
10. A computer readable storage medium, characterized in that the computer readable storage medium stores a program code executable by a processor, which program code, when executed by the processor, causes the processor to perform the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310849433.3A CN116955168B (en) | 2023-07-11 | 2023-07-11 | Vehicle-mounted software product running method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310849433.3A CN116955168B (en) | 2023-07-11 | 2023-07-11 | Vehicle-mounted software product running method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116955168A true CN116955168A (en) | 2023-10-27 |
| CN116955168B CN116955168B (en) | 2024-04-26 |
Family
ID=88457670
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310849433.3A Active CN116955168B (en) | 2023-07-11 | 2023-07-11 | Vehicle-mounted software product running method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116955168B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070006217A1 (en) * | 2005-06-29 | 2007-01-04 | Macrovision Corporation | Method and system for pre-deployment conflict checking |
| CN113392027A (en) * | 2021-07-07 | 2021-09-14 | 北京智慧星光信息技术有限公司 | Compatibility testing method and system for mobile terminal application and electronic equipment |
| CN113721940A (en) * | 2021-08-25 | 2021-11-30 | 浙江大华技术股份有限公司 | Software deployment method and device, electronic equipment and storage medium |
| CN114371890A (en) * | 2022-03-22 | 2022-04-19 | 天津市天河计算机技术有限公司 | Software management system of HPC cluster |
| CN115220922A (en) * | 2022-02-24 | 2022-10-21 | 广州汽车集团股份有限公司 | Vehicle application program running method and device and vehicle |
| CN116016387A (en) * | 2023-03-10 | 2023-04-25 | 苏州浪潮智能科技有限公司 | Access control list effective control method, device, equipment and storage medium |
-
2023
- 2023-07-11 CN CN202310849433.3A patent/CN116955168B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070006217A1 (en) * | 2005-06-29 | 2007-01-04 | Macrovision Corporation | Method and system for pre-deployment conflict checking |
| CN113392027A (en) * | 2021-07-07 | 2021-09-14 | 北京智慧星光信息技术有限公司 | Compatibility testing method and system for mobile terminal application and electronic equipment |
| CN113721940A (en) * | 2021-08-25 | 2021-11-30 | 浙江大华技术股份有限公司 | Software deployment method and device, electronic equipment and storage medium |
| CN115220922A (en) * | 2022-02-24 | 2022-10-21 | 广州汽车集团股份有限公司 | Vehicle application program running method and device and vehicle |
| CN114371890A (en) * | 2022-03-22 | 2022-04-19 | 天津市天河计算机技术有限公司 | Software management system of HPC cluster |
| CN116016387A (en) * | 2023-03-10 | 2023-04-25 | 苏州浪潮智能科技有限公司 | Access control list effective control method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116955168B (en) | 2024-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108600219B (en) | Voice control method and device | |
| CN103699437A (en) | Resource scheduling method and device | |
| CN107957687B (en) | Method and device for controlling functions of interconnection equipment | |
| CN112783506A (en) | Model operation method and related device | |
| CN113986402A (en) | Function calling method and device, electronic equipment and storage medium | |
| CN116955168B (en) | Vehicle-mounted software product running method and device, electronic equipment and storage medium | |
| CN109561134B (en) | Electronic device, distributed cluster service distribution method and storage medium | |
| CN110619204A (en) | Invitation code generation method and device, terminal equipment and storage medium | |
| CN112286559A (en) | Upgrading method and device for vehicle-mounted intelligent terminal | |
| CN115220922A (en) | Vehicle application program running method and device and vehicle | |
| CN112612427B (en) | Vehicle stop data processing method and device, storage medium and terminal | |
| CN111400281B (en) | GIS data quality inspection and storage method for OSS object storage | |
| US20170090820A1 (en) | Method and device for operating a many-core system | |
| CN110333870B (en) | Simulink model variable distribution processing method, device and equipment | |
| CN109976812B (en) | Vehicle starting method and system, vehicle and device with storage function | |
| CN112764822A (en) | Operating system starting method, device, equipment and medium | |
| CN112035078A (en) | Display method and system of screen content of intelligent terminal and vehicle-mounted terminal | |
| CN111722870B (en) | Driving configuration method, device and equipment of electronic control unit and storage medium | |
| CN109947559A (en) | Optimize method, apparatus, equipment and computer storage medium that MapReduce is calculated | |
| CN117055536B (en) | Function detection method and device and electronic equipment | |
| CN115629881A (en) | Host, data processing system, method, electronic device, and storage medium | |
| CN111475307B (en) | Physical settlement processing method and device | |
| CN112540835B (en) | Method and device for operating hybrid machine learning model and related equipment | |
| CN110321175B (en) | Controller initialization method and related device | |
| CN117555774A (en) | Method and device for generating test case and test script, electronic equipment and storage medium |
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 |