CN116596538A - Purchasing method, device and equipment of vehicle-mounted software function and storage medium - Google Patents
Purchasing method, device and equipment of vehicle-mounted software function and storage medium Download PDFInfo
- Publication number
- CN116596538A CN116596538A CN202310370684.3A CN202310370684A CN116596538A CN 116596538 A CN116596538 A CN 116596538A CN 202310370684 A CN202310370684 A CN 202310370684A CN 116596538 A CN116596538 A CN 116596538A
- Authority
- CN
- China
- Prior art keywords
- software
- information
- vehicle
- controller
- identifier
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000012795 verification Methods 0.000 claims abstract description 70
- 230000006870 function Effects 0.000 claims description 242
- 230000001960 triggered effect Effects 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 8
- 238000009434 installation Methods 0.000 claims description 7
- 230000008901 benefit Effects 0.000 abstract description 7
- 238000010438 heat treatment Methods 0.000 description 19
- 238000010586 diagram Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 230000003993 interaction Effects 0.000 description 4
- 230000009191 jumping Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- 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)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a purchasing method and device of a vehicle-mounted software function, electronic equipment and a storage medium, wherein the purchasing method of the vehicle-mounted software function comprises the following steps: receiving a verification request sent by an application server; acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier; judging whether the vehicle meets the condition of opening the software function or not based on the verification request, the second controller identifier and the second system software information; and under the condition that the vehicle accords with the function of opening the software, sending verification success information to the terminal so as to enable the terminal to enter a payment flow. Before payment, verifying the controller identification and the system software information corresponding to the purchased software function, and the controller identification and the system software information in the vehicle, and allowing the purchase payment when the controller identification and the system software information in the vehicle meet the software function, so that the user benefit is ensured.
Description
Technical Field
The application relates to the technical field of internet of vehicles, in particular to a purchasing method and device of vehicle-mounted software functions, electronic equipment and a storage medium.
Background
At present, more payment software for a vehicle controller is iterated after mass production of the vehicle, and system software corresponding to the vehicle cannot meet the opening condition of purchased payment software, so that additional processing is required or other payment software is purchased when the payment software is used, and the user benefit is not guaranteed.
Disclosure of Invention
In view of the above, the present application provides a method and apparatus for purchasing vehicle-mounted software functions, an electronic device, and a storage medium.
In a first aspect, an embodiment of the present application provides a method for purchasing a vehicle software function, where the method includes: receiving a verification request sent by an application server, wherein the verification request is triggered by the application server in response to the operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function and first system software information corresponding to each first controller identifier; acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier, wherein the second controller identifier is an identifier of a controller integrated with the vehicle; judging whether the vehicle meets the condition of opening the software function or not based on the first controller identifier, the second controller identifier, first system software information corresponding to each first controller identifier and second system software information corresponding to each second controller identifier; and under the condition that the vehicle accords with the function of opening the software, sending verification success information to the terminal so as to enable the terminal to enter a payment flow.
In an optional embodiment, the determining, based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier, and the second system software information corresponding to each second controller identifier, whether the vehicle meets a condition of opening the software function includes: respectively acquiring first software version information in the first system software information and second software version information in the second system software information; and if the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle meets the condition of opening the software function.
In an optional embodiment, the verification request further includes first controller part information corresponding to the first controller identifier, and the determining, based on the first controller identifier, the second controller identifier, first system software information corresponding to each first controller identifier, and second system software information corresponding to each second controller identifier, whether the vehicle meets a condition for opening the software function further includes: acquiring second controller part information corresponding to the second controller identifier; if the first controller part information is the same as the second controller part information, the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle accords with the condition of opening the software function; and if the first controller part information is different from the second controller part information, prompting hardware upgrade of the second controller.
In an optional embodiment, the second system software information includes upgrade download information and upgrade installation information, and the determining, based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier, and the second system software information corresponding to each second controller identifier, whether the vehicle meets a condition for opening the software function further includes: if the second software version information is lower than the first software version information, obtaining upgrading downloading information of the second software version information; if the upgrade downloading information is downloaded, prompting the software corresponding to the second software version information to be upgraded according to the upgrade downloading information; if the second software version information is updated and the updated second software version information is higher than or equal to the first software version information, the first controller identification is the same as the second controller identification, and it is determined that the vehicle meets the condition of opening the software function.
In an optional embodiment, after obtaining the upgrade download information of the second software version information if the second software version information is lower than the first software version information, the method further includes: if the upgrade downloading information is not downloaded, prompting to download the upgrade downloading information of the second software version information; based on the successful downloading information, upgrade installation information corresponding to the second software version information is obtained, and whether the second software version information downloaded with the upgrade downloading information is upgraded or not is judged.
In an optional embodiment, the obtaining upgrade installation information corresponding to the second software version information based on the download success information, and determining whether the second software version information downloaded with the upgrade download information is upgraded includes: if the user is not upgraded, the terminal is instructed to jump to an upgrade interface, and the user is prompted to trigger upgrade.
In a second aspect, an embodiment of the present application provides a method for purchasing a vehicle-mounted software function, where the method includes: receiving a purchase operation for purchasing a software function for the vehicle; responding to the purchase operation, and sending a purchase request to a server, wherein the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function so that the server can judge whether the vehicle meets the condition of opening the software function or not based on the vehicle identifier and the function identifier; and purchasing the software function based on a payment flow triggered by the server after verifying whether the vehicle accords with the condition of opening the software function.
In an optional embodiment, the method further includes, before purchasing the software function, based on a payment procedure triggered by the server after verifying whether the vehicle meets a condition for opening the software function: acquiring the non-downloaded prompt information of the upgrade software information corresponding to the second system software information sent by the server, wherein the server sends the non-downloaded prompt information when the software version of the second system software information is lower than the software version of the first system software information; and downloading the upgrade software information based on the non-downloaded prompt information.
In an optional embodiment, after the downloading of the upgrade software information based on the non-downloaded prompt information, the method further includes: acquiring unelevated prompt information of upgrade software information corresponding to the second system software information sent by the server; and according to the non-upgrading prompt information, skipping to the upgrading interface, prompting a user to trigger the second system software information to be upgraded.
In a third aspect, an embodiment of the present application provides a purchasing apparatus for a vehicle-mounted software function, the apparatus including: the system comprises a verification request receiving module, a verification request receiving module and a verification module, wherein the verification request is sent by an application server, the verification request is triggered by the application server in response to the operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function and first system software information corresponding to each first controller identifier; the vehicle data acquisition module is used for acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier, wherein the second controller identifier is an identifier of a controller integrated with the vehicle; the verification module is used for judging whether the vehicle accords with the condition of opening the software function or not based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier and the second system software information corresponding to each second controller identifier; and the information sending module is used for sending verification success information to the terminal under the condition that the vehicle accords with the function of opening the software so as to enable the terminal to enter a payment flow.
In a fourth aspect, an embodiment of the present application provides a purchasing apparatus for vehicle-mounted software functions, the apparatus including: a purchase operation receiving module for receiving a purchase operation for purchasing a software function for a vehicle; a purchase request sending module, configured to send a purchase request to a server in response to the purchase operation, where the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function, so that the server determines, based on the vehicle identifier and the function identifier, whether the vehicle meets a condition of opening the software function; and the payment module is used for purchasing the software function based on a payment flow triggered by the server after verifying whether the vehicle accords with the condition of opening the software function.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more program configured to perform the method of purchasing the in-vehicle software function provided in the first aspect and the method of purchasing the in-vehicle software function provided in the second aspect.
In a sixth aspect, an embodiment of the present application provides a computer readable storage medium having stored therein program code that is callable by a processor to perform the method of purchasing the in-vehicle software function provided in the first aspect and the method of purchasing the in-vehicle software function provided in the second aspect.
According to the scheme provided by the application, before the terminal selects the software function to be purchased, and the target software is paid, the server initiates a verification request aiming at the purchasing operation, the server judges whether the controller identifier and the system software information in the vehicle accord with the software function to be opened or not by acquiring the controller identifier and the system software information corresponding to the vehicle, and if so, the server sends verification success information to the terminal, so that the terminal enters a payment flow, and purchases the target software version. Before payment, verifying the controller identification and the system software information corresponding to the purchased software function, and the controller identification and the system software information in the vehicle, and allowing the purchase payment when the controller identification and the system software information in the vehicle meet the software function, so that the user benefit is ensured.
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 flow chart illustrating a purchasing method of a vehicle-mounted software function according to an embodiment of the application.
Fig. 2 is a schematic diagram of a verification flow of a verification request in a purchaser method of an on-board software function according to an embodiment of the application.
Fig. 3 is a flow chart illustrating a purchasing method of a vehicle-mounted software function according to another embodiment of the present application.
Fig. 4 is an information interaction schematic diagram of a purchasing method of a vehicle-mounted software function according to an embodiment of the present application.
Fig. 5 is a block diagram showing the construction of a purchasing device of the vehicle-mounted software function according to an embodiment of the present application.
Fig. 6 is a block diagram showing a purchasing apparatus of an in-vehicle software function according to another embodiment of the present application.
Fig. 7 is a block diagram showing the construction of an electronic device for executing the purchase method of the in-vehicle software function according to the embodiment of the present application.
Detailed Description
In order to enable those skilled in the art to better understand the present application, the following description will make clear and complete descriptions of the technical solutions according to the embodiments of the present application with reference to the accompanying drawings.
Aiming at the technical problems of the background technology, the inventor provides a purchasing method, a purchasing device, electronic equipment and a storage medium of a vehicle-mounted software function, a terminal selects the software function to be purchased, a server initiates a verification request aiming at purchasing operation before paying for target software, the server judges whether the controller identifier and the system software information in the vehicle accord with the software function to be opened or not by acquiring the controller identifier and the system software information corresponding to the vehicle, and if so, the server sends verification success information to the terminal, so that the terminal enters a payment flow and purchases the target software version. Before payment, verifying the controller identification and the system software information corresponding to the purchased software function, and the controller identification and the system software information in the vehicle, and allowing the purchase payment when the controller identification and the system software information in the vehicle meet the software function, so that the user benefit is ensured.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for purchasing a vehicle-mounted software function according to an embodiment of the application. In a specific embodiment, the purchasing method of the in-vehicle software function is applied to the purchasing apparatus 300 of the in-vehicle software function as shown in fig. 5 and the electronic device 100 provided with the purchasing apparatus 300 of the in-vehicle software function.
The following will describe the flowchart shown in fig. 1 in detail, and the purchasing method of the vehicle software function may specifically include the following steps:
step S110: and receiving a verification request sent by an application server, wherein the verification request is triggered by the application server in response to the operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function and first system software information corresponding to each first controller identifier.
The application server refers to a server corresponding to an application program on the terminal, and the application server can generate corresponding request or feedback corresponding operation data according to the operation of a user on the application program. The verification request is triggered in response to a user's operation on the application program to purchase a software function for the vehicle.
The terminal can be a mobile phone, a tablet or a vehicle-mounted terminal and other devices with a terminal display function, and the terminal is used for installing application programs and supporting a user to purchase software functions.
The software function refers to an additional software function which is required to be paid and purchased by a user besides a basic function of the vehicle system, the software function can be realized by controlling a controller associated with the software function, the software function works depending on a specific software version, and when the corresponding software version of the controller does not reach a target software version corresponding to the software function, the controller cannot support the software function and cannot realize the software function.
The vehicle identifier is information for uniquely identifying the vehicle, and may be a hardware serial number corresponding to the vehicle, or may be a frame number, or may be a vehicle identifier obtained by further processing according to a preset rule according to the hardware serial number and the frame number, and the vehicle identifier is not specifically limited herein.
The controller is a capability control unit capable of enabling the vehicle to have multi-sensor fusion, positioning, path planning and decision control. The controller identification is used to identify controller information including, but not limited to, controller model number and controller function. The controller identification can also be obtained by carrying out universal identification through operators, so that the controller identification is convenient to be suitable for various occasions. The controller identifier associated with the software function can acquire what controller model the software function is realized through, so that normal use can be ensured after the software function is purchased.
In some embodiments, an operator may put on shelf payment software products including, but not limited to, payment software versions and payment software functions from a terminal or server side. When the payment software commodity is put on shelf, the controller associated with the payment software commodity and the software and hardware version information of the controller are required to be input, and the input payment software commodity and the associated controller information are synchronized to the terminal and the server, so that a user can acquire the latest payment software commodity conveniently.
After the user purchases the target software corresponding to the software function on the terminal according to the software function, the server responds to the purchase operation of the terminal and initiates a verification request corresponding to the purchase operation so as to verify whether the controller identifier associated with the software function and the system software information support the software function or not.
Step S120: and acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier, wherein the second controller identifier is the identifier of the controller integrated by the vehicle.
The second controller identifier to which the vehicle identifier is bound refers to controller information currently used by the vehicle. The second system software information is system software information currently used by the vehicle.
And acquiring whether the controller identification and the software system information on the vehicle are matched with the controller identification and the system software information associated with the software function or not, so as to be used for checking whether the vehicle supports the software function or not.
Step S130: and judging whether the vehicle meets the condition of opening the software function or not based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier and the second system software information corresponding to each second controller identifier.
In some embodiments, referring to fig. 2, fig. 2 is a schematic diagram illustrating a verification flow of a verification request in a purchaser method of an in-vehicle software function according to an embodiment of the application. Judging whether the vehicle meets the condition of opening the software function or not based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier and the second system software information corresponding to each second controller identifier specifically comprises: respectively acquiring first software version information in the first system software information and second software version information in the second system software information; and if the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle meets the condition of opening the software function.
The high-level software version can be downward compatible with the low-level software version, and the system software corresponding to the high-level software version can execute the software function corresponding to the low-level software version, but the low-level software version cannot execute the special software function in the high-level software version.
Therefore, when the second software version information is higher than or equal to the first software version information, the second system software information corresponding to the second software version information can execute the software function in the first system software information, and when the second controller identification in the vehicle is the same as the first controller identification in the verification request, the condition that the vehicle meets the software function opening condition is determined.
Specifically, verifying whether the second controller supports the target software version further includes: if the second software version information is lower than the first software version information, obtaining upgrading downloading information of the second software version information; if the upgrade downloading information is downloaded, prompting the software corresponding to the second software version information to be upgraded according to the upgrade downloading information; if the second software version information is updated and the updated second software version information is higher than or equal to the first software version information, the first controller identification is the same as the second controller identification, and it is determined that the vehicle meets the condition of opening the software function.
The OTA system refers to an Over-the-Air Technology (OTA), which is a system for implementing remote management of terminal equipment and SIM card data through an Air interface of mobile communication.
The OTA system creates each software version and the downloading task of each system software, the vehicle carries out automatic silent downloading when the vehicle is electrified and connected, after the silent downloading is finished, a user can click the software upgrading interface to upgrade the software, if the software upgrading interface is not electrified for a long time or the downloading is not finished due to poor network state, the upgrading interface is not displayed on the terminal.
The software version corresponding to the controller on the vehicle and the system software downloading information depend on the OTA system, and the server can acquire the second software version upgrading downloading information of the second system software information corresponding to the second controller identification of the vehicle by accessing the OTA system. When the upgrade downloading information obtained from the OTA system is downloaded, judging whether the software is installed and upgraded or not through the OTA system. If the vehicle is updated, and the updated second software version information is higher than or equal to the first software version information and the first controller identifier is the same as the second controller identifier, judging that the vehicle supports the target software version.
Before purchasing the software, checking whether the vehicle supports the target software version, and avoiding the loss of user benefits caused by the fact that the software is purchased without checking.
If the upgrade downloading information is not downloaded, prompting to download the upgrade downloading information of the second software version information; based on the successful downloading information, upgrade installation information corresponding to the second software version information is obtained, and whether the second software version information downloaded with the upgrade downloading information is upgraded or not is judged.
And if the upgrade downloading information is not acquired from the OTA system, judging that the upgrade downloading information is not downloaded, feeding back the upgrade downloading information by the OTA system, and downloading the upgrade downloading information of the second software version information at the terminal to prompt the power-on downloading. The prompting mode may be sending popup window information, or may be direct jump triggering download interface, and the specific prompting mode is not limited herein.
The occurrence of the prompt information can avoid time waste caused by the fact that the user forgets to record and download the software, and the user can acquire the corresponding stage of purchasing the software in real time, so that the grasping degree of grasping the purchasing information of the software by the user is improved.
If the user is not upgraded, the terminal is instructed to jump to an upgrade interface, and the user is prompted to trigger upgrade.
The upgrade interface can be a human-computer interface module (Human Interface Module, HIM), the HIM is used for human-computer interaction, and the related HIM is suitable for various human-computer interaction scenes. In the embodiment of the application, when the software is only downloaded and not upgraded, the man-machine upgrading interface is skipped, and the user triggers the upgrading program, so that the normal upgrading of the software is further ensured, and the user can master whether the software is upgraded or not, thereby facilitating the purchase of other payment software or payment functions.
For example, when the user purchases the target software version for the "seat heating" function at the terminal, a verification request is sent to the server before payment, for verifying whether the system software information corresponding to the seat-related controller and the heating-related controller on the vehicle is supported for seat heating. In the verification process, when the current system software information of the vehicle does not support the seat heating function, the server acquires upgrade downloading information of the system software information of the vehicle from the OTA system, and if the upgrade downloading information is downloaded, a terminal prompts a user to upgrade the system software information of the vehicle according to the upgrade downloading information. If the upgrade downloading information is not downloaded, prompting a user to download the upgrade downloading information at the terminal, jumping an upgrade interface after the downloading is finished, prompting the user to trigger the upgrade, and enabling the system software information on the vehicle to support a seat heating function.
When the controller on the vehicle does not support the target software version, prompt information is sent to the user, so that the controller on the vehicle can support the target software version after downloading and upgrading according to the prompt information, and the problem that software functions cannot be opened due to failure in downloading and upgrading of the OTA system after payment by the user is avoided.
In other embodiments, determining whether the vehicle meets the condition of opening the software function based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier, and the second system software information corresponding to each second controller identifier further includes: acquiring second controller part information corresponding to the second controller identifier; and if the first controller part information is the same as the second controller part information, the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle accords with the condition of opening the software function.
The part information includes, but is not limited to, the type of controller, the model of the controller, and software system information supported by the controller.
When the information of the controller parts on the vehicle is different from the information of the controller parts required by the software function, the controller hardware prompt is carried out on the terminal to the user, so that the information of the parts of the controller on the vehicle is identical to the information of the controller parts required by the software function, and the normal operation of the software function is ensured.
The hardware upgrade mode may be to replace a controller higher than or the same as the controller corresponding to the software function, and the hardware upgrade mode is not particularly limited herein.
In the implementation process, a user purchases a target software version aiming at a seat heating function at a terminal, and before paying, a verification request is sent to a server for verifying whether system software information corresponding to a seat-related controller and a heating-related controller on a vehicle is supported for seat heating. In the verification process, when the current system software information of the vehicle does not support the seat heating function, the server acquires upgrade downloading information of the system software information of the vehicle from the OTA system, and if the upgrade downloading information is downloaded, a terminal prompts a user to upgrade the system software information of the vehicle according to the upgrade downloading information. If the upgrade downloading information is not downloaded, prompting a user to download the upgrade downloading information at the terminal, jumping an upgrade interface after the downloading is finished, prompting the user to trigger the upgrade, and enabling the system software information on the vehicle to support a seat heating function.
After verification of the system software functions on the vehicle, it is also necessary to verify whether the controller on the vehicle supports the "seat heating" function. When the controller related to the seat and the controller related to the heating on the vehicle are the same as the controller corresponding to the "seat heating" function, it is determined that the vehicle meets the condition of turning on the "seat heating" function. When the controller related to the seat or the controller related to the heating on the vehicle is different from the controller corresponding to the seat heating function, prompting a user to upgrade the controller related to the seat or the controller related to the heating at the terminal, and checking the upgraded controller to finally achieve that the controller related to the seat and the controller related to the heating on the vehicle are identical to the controller corresponding to the seat heating function.
Step S140: and under the condition that the vehicle accords with the function of opening the software, sending verification success information to the terminal so as to enable the terminal to enter a payment flow.
When the second controller identifier and the second system software information in the vehicle correspond to the first controller identifier and the first system software information in the verification request, the vehicle is judged to accord with the software function, the verification success information is sent to the terminal, and the terminal enters a payment flow after receiving the verification success information.
According to the scheme provided by the application, before the terminal selects the software function to be purchased, and the target software is paid, the server initiates a verification request aiming at the purchasing operation, the server judges whether the controller identifier and the system software information in the vehicle accord with the software function to be opened or not by acquiring the controller identifier and the system software information corresponding to the vehicle, and if so, the server sends verification success information to the terminal, so that the terminal enters a payment flow, and purchases the target software version. Before payment, verifying the controller identification and the system software information corresponding to the purchased software function, and the controller identification and the system software information in the vehicle, and allowing the purchase payment when the controller identification and the system software information in the vehicle meet the software function, so that the user benefit is ensured.
Referring to fig. 3, fig. 3 is a flowchart illustrating a method for purchasing a vehicle-mounted software function according to an embodiment of the application. The purchaser method of the in-vehicle software function is applied to the purchasing apparatus 400 of the in-vehicle software function shown in fig. 6 and the electronic device 100 provided with the purchasing apparatus 400 of the in-vehicle software function. The following details about the flowchart shown in fig. 3, the purchasing method of the vehicle software function may specifically include the following steps:
Step S210: a purchase operation is received to purchase a software function for the vehicle.
Step S220: and responding to the purchase operation, and sending a purchase request to a server, wherein the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function, so that the server can judge whether the vehicle meets the condition of opening the software function or not based on the vehicle identifier and the function identifier.
The purchase request is generated according to a software function purchased by the user for the vehicle, and the vehicle identifier in the purchase request is the same as the vehicle identifier in the previous embodiment, which is not described herein.
The function identifiers are in one-to-one correspondence with the software functions, and the function identifiers can be used for identifying controller identifiers corresponding to the software functions and system software information associated with the controller identifiers. The function identifier may be obtained by acquiring a software function name, the function identifier may also be obtained according to a controller identifier corresponding to a software function and system software information, the function identifier may also be obtained by user definition, and a specific acquisition mode of the function identifier is not specifically limited herein.
The user's application on the terminal views different merchandise information including, but not limited to, payment software for each controller on the vehicle and payment software functions for each controller, the same software having a plurality of different software versions. The user can purchase the software function for the vehicle through the interface of the application program, generate a purchase request according to the purchase operation of the user, send the purchase request to the application server, generate a verification request according to the purchase request, and judge whether the vehicle accords with the condition of opening the software function or not according to the vehicle identification and the function identification by the application server.
In some embodiments, the method further comprises: acquiring the non-downloaded prompt information of the upgrade software information corresponding to the second system software information sent by the server, wherein the server sends the non-downloaded prompt information when the software version of the second system software information is lower than the software version of the first system software information; and downloading the upgrade software information based on the non-downloaded prompt information.
When the server checks whether the vehicle accords with the condition of opening the software function according to the vehicle identification and the function identification, when the software version of the second system software information is lower than that of the first system software information, upgrading downloading information of the vehicle system software information is obtained from the OTA system, and if the upgrading downloading information is not downloaded, the server sends a non-downloading prompt message to the terminal to prompt a user to download the upgrading downloading information in a power-on mode. When the upgrade downloading information is downloaded, the system software information of the vehicle is upgraded according to the upgrade downloading information, so that the upgraded system software information of the vehicle supports the software function.
In other embodiments, after downloading the upgrade software information based on the non-downloaded prompt information, the method further includes: acquiring unelevated prompt information of upgrade software information corresponding to the second system software information sent by the server; and according to the non-upgrading prompt information, skipping to the upgrading interface, prompting a user to trigger the second system software information to be upgraded.
When the upgrade downloading information corresponding to the system software information of the vehicle is downloaded but not upgraded according to the upgrade downloading information, the server sends the non-upgrade prompt information to the terminal, and jumps to the upgrade interface to enable the user to upgrade the upgrade interface of the terminal, and enable the upgraded system software information to meet the condition that the software function is opened.
In some embodiments, the terminal may also filter available payment software or payment software functions corresponding to the vehicle configuration according to the vehicle information in the bound terminal account.
Step S230: and purchasing the software function based on a payment flow triggered by the server after verifying whether the vehicle meets the condition of opening the software function.
After the user selects payment software or payment software functions to be purchased, the application program generates a purchase request according to the purchase operation of the user, the purchase request is sent to the server, the server checks the information in the purchase request and the information of the vehicle according to the information in the purchase request, and after the check is successful, the server sends check success information to the application program. And after receiving the verification success information sent by the server, the application program enters a payment flow to complete the purchase of the software function by the user. After the user purchases, the terminal synchronizes the order information to the server, and the server opens the software function aiming at the software function in the order information.
In the embodiment of the application, the controller identification and the system software information of the vehicle are checked by the controller identification and the system software information corresponding to the function identification of the purchased software function before purchase, and the application program can enter the payment flow after the check is successful, so that the problem that the function cannot be opened after payment by the user is avoided, and the user benefit is ensured.
Referring to fig. 4, an information interaction schematic diagram of a purchasing method of a vehicle-mounted software function according to an embodiment of the present application is shown.
Step S310: a purchase operation is received to purchase a software function for the vehicle.
Step S320: and responding to the purchase operation, and sending a purchase request to a server, wherein the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function, so that the server can judge whether the vehicle meets the condition of opening the software function or not based on the vehicle identifier and the function identifier.
The application program on the terminal of the user selects the software function to be purchased, generates a purchase request according to the purchase operation of the user, and sends the purchase request to an application server in the server.
Step S330: and receiving a verification request sent by an application server, wherein the verification request is triggered by the application server in response to the operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function and first system software information corresponding to each first controller identifier.
The application server analyzes the received purchase request, generates a verification request, and sends the verification request to the software payment platform. The controller identification in the verification request and the system software information corresponding to the controller identification are acquired through the function identification in the purchase request, and the software functions, the function identification and the controller identification are in one-to-one correspondence. The server can conveniently acquire the corresponding function identification according to the purchasing operation of the user on the software function, and can identify the controller identification corresponding to the software function and the system software information corresponding to the controller identification according to the function identification.
Step S340: and acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier, wherein the second controller identifier is the identifier of the controller integrated by the vehicle.
Step S350: and judging whether the vehicle meets the condition of opening the software function or not based on the first controller identifier, the second controller identifier, the first system software information corresponding to each first controller identifier and the second system software information corresponding to each second controller identifier.
Step S360: and under the condition that the vehicle accords with the function of opening the software, sending verification success information to the terminal so as to enable the terminal to enter a payment flow.
Step S370: and purchasing the software function based on a payment flow triggered by the server after verifying whether the vehicle accords with the condition of opening the software function.
Please refer to the steps S110 to S140 and the steps S210 to S230 in the above embodiments for the detailed description of the steps S310 to S370, which are not repeated here.
In the embodiment of the application, based on the software function purchasing operation of the user on the application program interface on the terminal, the application program interface comprises a plurality of payment software functions. The application program generates a purchase request according to the purchase operation of the user, the purchase request carries a vehicle identifier and a function identifier, and the purchase request is sent to an application server of the server side. The application server initiates a verification request according to the purchase request, and obtains a controller identifier associated with the software function and system software information corresponding to the controller identifier according to the function identifier in the purchase request. The application server sends a verification request to the software payment platform. The verification request instructs the software payment platform of the server to acquire at least one second controller identifier bound with the vehicle identifier from the OTA system, and second system software information corresponding to each second controller identifier. And the second controller identifier and the second system software information are used for verifying the first controller identifier and the second controller identifier, which are bound with the vehicle identifier, corresponding to the software function in the software payment platform verification request. The OTA system provides a silent downloading function for the vehicle, and when the system software information is downloaded for the vehicle, the controller information of the vehicle and the currently downloaded system software information are also stored.
And when the verification is successful, the software payment platform sends verification success information to the terminal so that the terminal enters a payment flow and purchases the software function. After the user completes the purchase through the application program interface, the application program sends the purchase success information to the payment software platform, and the payment software platform opens corresponding software functions on the vehicle according to the purchase success information. Before a user pays a software function, a second controller identifier in the vehicle, a first controller identifier associated with the second system software information and the software function, and first system software information are checked to enable the vehicle to meet software function opening conditions, so that the rights and interests of the user are guaranteed.
Referring to fig. 5, a block diagram of a purchasing apparatus 300 with vehicle-mounted software functions according to an embodiment of the application is shown. The in-vehicle software function purchasing apparatus 300 is applied to the electronic device 100, and the in-vehicle software function purchasing apparatus 300 includes: a verification request sending module 310, configured to receive a verification request sent by an application server, where the verification request is triggered by the application server responding to an operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function, and first system software information corresponding to each first controller identifier; a vehicle data obtaining module 320, configured to obtain at least one second controller identifier bound to the vehicle identifier, and second system software information corresponding to each second controller identifier, where the second controller identifier is an identifier of a controller integrated by the vehicle; the verification module 330 is configured to determine whether the vehicle meets a condition for opening the software function based on the first controller identifier, the second controller identifier, first system software information corresponding to each first controller identifier, and second system software information corresponding to each second controller identifier; and the information sending module 340 is configured to send verification success information to the terminal when the vehicle accords with the software function, so that the terminal enters a payment procedure.
In some embodiments of the present application, the verification module 330 includes: the software version information acquisition module is used for respectively acquiring first software version information in the first system software information and second software version information in the second system software information; and the opening condition determining module is used for determining that the vehicle meets the condition of opening the software function if the second software version information is higher than or equal to the first software version information and the first controller identifier is the same as the second controller identifier.
In some embodiments of the present application, the verification module 330 further includes: the part information acquisition module is used for acquiring second controller part information corresponding to the second controller identifier; the part information judging module is used for determining that the vehicle accords with the condition of opening the software function if the first controller part information is identical to the second controller part information, the second software version information is higher than or equal to the first software version information, and the first controller identifier is identical to the second controller identifier; and the prompting hardware upgrading module is used for prompting the hardware upgrading of the second controller if the first controller part information is different from the second controller part information.
Specifically, the verification module 330 further includes: the upgrade downloading information acquisition module is used for acquiring upgrade downloading information of the second software version information if the second software version information is lower than the first software version information; the prompt upgrading module is used for prompting the software corresponding to the second software version information to be upgraded according to the upgrade downloading information if the upgrade downloading information is downloaded; and the updated meeting opening module is used for determining that the vehicle meets the conditions for opening the software function if the second software version information is updated and the updated second software version information is higher than or equal to the first software version information and the first controller identifier is the same as the second controller identifier.
Specifically, the upgrade download information acquisition module further includes: the download prompting module is used for prompting the downloading of the upgrade downloading information of the second software version information if the upgrade downloading information is not downloaded; and the upgrade judging module is used for acquiring upgrade installation information corresponding to the second software version information based on the successful downloading information and judging whether the second software version information downloaded with the upgrade downloading information is upgraded or not.
Specifically, the upgrade judging module includes: and the upgrade prompting module is used for indicating the terminal to jump to an upgrade interface if the terminal is not upgraded, and prompting a user to trigger upgrade.
Referring to fig. 6, a block diagram of a purchasing device 400 with vehicle-mounted software functions according to an embodiment of the application is shown. The in-vehicle software function purchasing apparatus 400 is applied to the electronic device 100, and the in-vehicle software function purchasing apparatus 400 includes: a purchase operation receiving module 410 for receiving a purchase operation for purchasing a software function for a vehicle; and a purchase request sending module 420, configured to send a purchase request to a server in response to the purchase operation, where the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function, so that the server determines whether the vehicle meets a condition of opening the software function based on the vehicle identifier and the function identifier. And the payment module 430 is used for purchasing the software function based on a payment process triggered by the server after verifying whether the vehicle meets the condition of opening the software function.
In some embodiments, the purchasing apparatus 400 of the in-vehicle software function further includes: the non-downloaded prompt information acquisition module is used for acquiring non-downloaded prompt information of upgrade software information corresponding to the second system software information sent by the server, wherein the server sends the non-downloaded prompt information when the software version of the second system software information is lower than that of the first system software information; and the upgrade software information downloading module is used for downloading the upgrade software information based on the non-downloaded prompt information.
In some embodiments, the purchasing apparatus 400 of the in-vehicle software function further includes: the unequipped prompt information acquisition module is used for acquiring unequipped prompt information of the upgraded software information corresponding to the second system software information sent by the server; and the upgrade triggering module is used for jumping to the upgrade interface according to the un-upgrade prompt information to prompt a user to trigger the upgrade of the second system software information.
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. 7, a block diagram of an electronic device according to an embodiment of the present application is shown. The electronic device 100 may be a switch, a computer, or a control unit with data transmission. The electronic device 100 of the present application may include one or more of the following components: a processor 110, a memory 120, and one or more application programs, wherein the one or more application programs may be stored in the memory 120 and configured to be executed by the one or more processors 110, the one or more program(s) configured to perform the method as described in the foregoing method embodiments.
Processor 110 may include one or more processing cores. The processor 110 utilizes various interfaces and lines to connect various portions of the overall electronic device 100, perform various functions of the electronic device 100, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and invoking data stored in the memory 120. Alternatively, the processor 110 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 110 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), a graphics 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 110 and may be implemented solely by a single communication chip.
The Memory 120 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Memory 120 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 120 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 the various method embodiments described below, etc. The storage data area may also store data created by the electronic device 100 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 program code stored therein, the program code being executable 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 ROM. Optionally, the computer readable storage medium comprises a non-volatile computer readable medium (non-transitory computer-readable storage medium). 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 (12)
1. A method of purchasing vehicle software functionality, the method comprising:
receiving a verification request sent by an application server, wherein the verification request is triggered by the application server in response to the operation of purchasing a software function for a vehicle, and the verification request carries a vehicle identifier of the vehicle, at least one first controller identifier associated with the software function and first system software information corresponding to each first controller identifier;
acquiring at least one second controller identifier bound with the vehicle identifier and second system software information corresponding to each second controller identifier, wherein the second controller identifier is an identifier of a controller integrated with the vehicle;
Judging whether the vehicle meets the condition of opening the software function or not based on the first controller identifier, the second controller identifier, first system software information corresponding to each first controller identifier and second system software information corresponding to each second controller identifier;
and under the condition that the vehicle accords with the software function, sending verification success information to the terminal so as to enable the terminal to enter a payment flow of the software function.
2. The method of claim 1, wherein the determining whether the vehicle meets the condition to turn on the software function based on the first controller identification, the second controller identification, first system software information corresponding to each first controller identification, and second system software information corresponding to each second controller identification comprises:
respectively acquiring first software version information in the first system software information and second software version information in the second system software information;
and if the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle meets the condition of opening the software function.
3. The method of claim 2, wherein the verification request further includes first controller part information corresponding to the first controller identification, the determining whether the vehicle meets a condition to turn on the software function based on the first controller identification, the second controller identification, first system software information corresponding to each first controller identification, and second system software information corresponding to each second controller identification, further comprising:
acquiring second controller part information corresponding to the second controller identifier;
if the first controller part information is the same as the second controller part information, the second software version information is higher than or equal to the first software version information, and the first controller identifier is the same as the second controller identifier, determining that the vehicle accords with the condition of opening the software function;
and if the first controller part information is different from the second controller part information, prompting hardware upgrade of the second controller.
4. The method of claim 2, wherein the second system software information includes upgrade download information and upgrade installation information, the determining whether the vehicle meets a condition to turn on the software function based on the first controller identification, the second controller identification, first system software information corresponding to each first controller identification, and second system software information corresponding to each second controller identification, further comprising:
If the second software version information is lower than the first software version information, obtaining upgrading downloading information of the second software version information;
if the upgrade downloading information is downloaded, prompting the software corresponding to the second software version information to be upgraded according to the upgrade downloading information;
if the second software version information is updated and the updated second software version information is higher than or equal to the first software version information, the first controller identification is the same as the second controller identification, and it is determined that the vehicle meets the condition of opening the software function.
5. The method of claim 4, wherein if the second software version information is lower than the first software version information, after obtaining the upgrade download information of the second software version information, further comprising:
if the upgrade downloading information is not downloaded, prompting to download the upgrade downloading information of the second software version information;
based on the successful downloading information, upgrade installation information corresponding to the second software version information is obtained, and whether the second software version information downloaded with the upgrade downloading information is upgraded or not is judged.
6. A method of purchasing vehicle software functionality, the method comprising:
receiving a purchase operation for purchasing a software function for the vehicle;
responding to the purchase operation, and sending a purchase request to a server, wherein the purchase request carries a vehicle identifier of the vehicle and a function identifier of the software function so that the server can judge whether the vehicle meets the condition of opening the software function or not based on the vehicle identifier and the function identifier;
and purchasing the software function based on a payment flow triggered by the server after verifying whether the vehicle accords with the condition of opening the software function.
7. The method of claim 6, wherein the purchasing the software function based on the payment procedure triggered by the server after verifying whether the vehicle meets the condition for opening the software function further comprises:
acquiring the non-downloaded prompt information of the upgrade software information corresponding to the second system software information sent by the server, wherein the server sends the non-downloaded prompt information when the software version of the second system software information is lower than the software version of the first system software information;
And downloading the upgrade software information based on the non-downloaded prompt information.
8. The method of claim 7, wherein after downloading the upgrade software information based on the un-downloaded hint information, further comprising:
acquiring unelevated prompt information of upgrade software information corresponding to the second system software information sent by the server;
and according to the non-upgrading prompt information, skipping to the upgrading interface, prompting a user to trigger the second system software information to be upgraded.
9. A purchasing device for vehicle-mounted software functions, characterized by comprising modules for implementing the method according to any one of claims 1-5.
10. A purchasing device for vehicle-mounted software functions, characterized by comprising modules for implementing the method according to any one of claims 6-8.
11. 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-8.
12. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a program code, which is callable by a processor for executing the method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310370684.3A CN116596538A (en) | 2023-04-07 | 2023-04-07 | Purchasing method, device and equipment of vehicle-mounted software function and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310370684.3A CN116596538A (en) | 2023-04-07 | 2023-04-07 | Purchasing method, device and equipment of vehicle-mounted software function and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116596538A true CN116596538A (en) | 2023-08-15 |
Family
ID=87610599
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310370684.3A Pending CN116596538A (en) | 2023-04-07 | 2023-04-07 | Purchasing method, device and equipment of vehicle-mounted software function and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116596538A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107656752A (en) * | 2017-10-31 | 2018-02-02 | 北京新能源汽车股份有限公司 | A kind of method, apparatus and vehicle of vehicle control device software upgrading |
| CN109284120A (en) * | 2018-10-25 | 2019-01-29 | 北京新能源汽车股份有限公司 | A kind of vehicle control device Oftware updating method and updating device |
| CN114710521A (en) * | 2022-03-11 | 2022-07-05 | 重庆长安汽车股份有限公司 | Vehicle cloud platform architecture system and method for realizing vehicle-mounted software payment authorization |
| CN115396309A (en) * | 2022-08-23 | 2022-11-25 | 浙江吉智新能源汽车科技有限公司 | Software upgrading method, OTA function purchasing method and information interaction system |
-
2023
- 2023-04-07 CN CN202310370684.3A patent/CN116596538A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107656752A (en) * | 2017-10-31 | 2018-02-02 | 北京新能源汽车股份有限公司 | A kind of method, apparatus and vehicle of vehicle control device software upgrading |
| CN109284120A (en) * | 2018-10-25 | 2019-01-29 | 北京新能源汽车股份有限公司 | A kind of vehicle control device Oftware updating method and updating device |
| CN114710521A (en) * | 2022-03-11 | 2022-07-05 | 重庆长安汽车股份有限公司 | Vehicle cloud platform architecture system and method for realizing vehicle-mounted software payment authorization |
| CN115396309A (en) * | 2022-08-23 | 2022-11-25 | 浙江吉智新能源汽车科技有限公司 | Software upgrading method, OTA function purchasing method and information interaction system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210141631A1 (en) | Electronic control system for vehicle, program update approval determination method and program update approval determination program | |
| CN110928567A (en) | Vehicle system upgrading method, terminal device and computer-readable storage medium | |
| CN105162841A (en) | Domestic appliance control method and system | |
| CN111742354A (en) | Vehicle diagnosis method, system, equipment and server | |
| CN110598868A (en) | Machine learning model building method and device and related equipment | |
| CN105376203A (en) | Processing method of interactive information, device and system | |
| AU2013406576A1 (en) | Installation package authorization method and device | |
| CN109947449A (en) | Method for upgrading system, device, storage medium and electronic equipment | |
| CN108363592B (en) | Application software running method, device, equipment and computer readable storage medium | |
| CN109343876A (en) | A kind of method of firmware update, system, device, equipment and storage medium | |
| CN104133701A (en) | Application installation method and device | |
| CN109257652B (en) | Configuration information switching method and device, electronic device, system and storage medium | |
| CN112068854A (en) | Intelligent device algorithm updating system, intelligent device and platform server | |
| CN114675855A (en) | Vehicle software remote upgrading method and device and platform equipment | |
| CN112667301A (en) | Docking station implementation method and system of vehicle-mounted operating system and electronic equipment | |
| CN104516743B (en) | The upgrade method and system of embedded device firmware based on ActiveX | |
| CN116596538A (en) | Purchasing method, device and equipment of vehicle-mounted software function and storage medium | |
| CN108600242B (en) | Account registration method, device and equipment of application software and readable storage medium | |
| CN116308428A (en) | Vehicle accessory management method, device, equipment and medium based on traceability codes | |
| KR20140111137A (en) | Method, server and system for providing coupon of online game | |
| CN116225489A (en) | Vehicle application upgrading method and device, electronic equipment and storage medium | |
| CN106210898B (en) | Upgrading method and system for television terminal in network-free state | |
| KR101907009B1 (en) | Apparatas and method for installation in a digital product | |
| CN115174575A (en) | Service control method and device, electronic equipment and storage medium | |
| CN113868531A (en) | Information acquisition method and device, electronic device and 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 |