CN113837828A - Vehicle-mounted software selling method and device, vehicle and storage medium - Google Patents
Vehicle-mounted software selling method and device, vehicle and storage medium Download PDFInfo
- Publication number
- CN113837828A CN113837828A CN202111047418.4A CN202111047418A CN113837828A CN 113837828 A CN113837828 A CN 113837828A CN 202111047418 A CN202111047418 A CN 202111047418A CN 113837828 A CN113837828 A CN 113837828A
- Authority
- CN
- China
- Prior art keywords
- software
- target vehicle
- vehicle
- service
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000013475 authorization Methods 0.000 claims description 11
- 238000009434 installation Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 7
- 238000010200 validation analysis Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 10
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 5
- 238000005336 cracking Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
Images
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
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
Abstract
The application discloses a vehicle-mounted software selling method, a device, a vehicle and a storage medium, wherein the method comprises the following steps: receiving a software purchase request of a vehicle owner; generating a to-be-paid order of the target vehicle-mounted software according to the software purchase request, and after the to-be-paid order is paid, sending software list change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request to authorize the use permission of the target vehicle on the target vehicle-mounted software; and when the target vehicle is detected not to meet the use condition, stopping authorizing the use authority of the target vehicle-mounted software to the target vehicle. Therefore, the selling of the whole vehicle software or the service software is realized, and the safety of related service control is realized.
Description
Technical Field
The application relates to the technical field of vehicles, in particular to a vehicle-mounted software selling method, a vehicle-mounted software selling device, a vehicle and a storage medium.
Background
The era of software-defined automobiles is coming, and the business model in the automobile field is changing from selling only hardware (car sales) to selling software and services. The software may be sold in a variety of ranges, for example: the method can independently purchase value-added services such as a skin package, an avatar, a VIP (very important person) service package, a KTV (Karaoke) function, an automatic driving function, a gesture photographing function and the like at the vehicle end.
Content of application
The application provides a vehicle-mounted software selling method, a vehicle-mounted software selling device, a vehicle and a storage medium, which can realize selling of whole vehicle software or service software and realize safety of relevant service control.
The embodiment of the first aspect of the application provides a vehicle-mounted software selling method, which comprises the following steps:
receiving a software purchase request of a vehicle owner;
generating a to-be-paid order of target vehicle-mounted software according to the software purchase request, and after the to-be-paid order is paid, sending software list change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request to authorize the use permission of the target vehicle on the target vehicle-mounted software; and
and when the target vehicle is detected not to meet the use condition, stopping authorizing the use authority of the target vehicle-mounted software to the target vehicle.
Optionally, after sending software inventory change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the method further includes:
generating a selling signature record according to the order to be paid;
and determining the purchase time range and/or the service validation mode of the target vehicle-mounted software according to the sale signature record, and determining the use condition.
Optionally, after authorizing the right of the target vehicle to use the target on-board software, the method further includes:
when the target vehicle is detected to open the target vehicle-mounted software, acquiring a matching result of a vehicle-end service registration center on the service fingerprint of the target vehicle-mounted software;
if the matching result is matching and the current service of the target vehicle-mounted software is effective, judging whether the target vehicle-mounted software needs to be installed;
and if the target vehicle-mounted software needs to be installed, sending an installation package to the target vehicle, otherwise, directly providing the application service of the target vehicle-mounted software.
Optionally, the method further comprises:
when the use permission of the target vehicle-mounted software is authorized to the target vehicle is stopped, software expiration prompting is conducted on the vehicle owner, and/or purchase prompting and/or fee renewal prompting of the target vehicle-mounted software is pushed, and the use permission of the target vehicle-mounted software authorized to the target vehicle is obtained again.
Optionally, before detecting whether the target vehicle meets the use condition, the method further includes:
detecting a purchase type of the target software;
and if the purchase type is a permanent type, directly providing the application service of the target vehicle-mounted software.
An embodiment of a second aspect of the present application provides an on-vehicle software selling device, including:
the receiving module is used for receiving a software purchasing request of a vehicle owner;
the authorization module is used for generating a to-be-paid order of target vehicle-mounted software according to the software purchase request, sending software list change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request after the to-be-paid order is paid, and authorizing the use permission of the target vehicle on the target vehicle-mounted software; and
and the processing module is used for stopping authorizing the target vehicle to the use authority of the target vehicle-mounted software when detecting that the target vehicle does not meet the use condition.
Optionally, after sending software inventory change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the authorization module further includes:
the generating unit is used for generating a selling signature record according to the order to be paid;
and the determining unit is used for determining the purchase time range and/or the service effective mode of the target vehicle-mounted software according to the sale signature record and determining the use condition.
Optionally, after authorizing the usage right of the target vehicle for the target on-board software, the authorization module further includes:
the acquisition unit is used for acquiring a matching result of a vehicle-end service registration center on the service fingerprint of the target vehicle-mounted software when the target vehicle is detected to open the target vehicle-mounted software;
the judging unit is used for judging whether the target vehicle-mounted software needs to be installed or not if the matching result is matching and the current service of the target vehicle-mounted software is effective;
and the processing unit is used for sending an installation package to the target vehicle if the target vehicle-mounted software needs to be installed, and otherwise, directly providing the application service of the target vehicle-mounted software.
Optionally, the method further comprises:
and the prompting module is used for prompting the software expiration of the vehicle owner while stopping authorizing the use permission of the target vehicle-mounted software to the target vehicle, and/or pushing a purchase prompt and/or a fee renewal prompt of the target vehicle-mounted software to reacquire the use permission of the target vehicle-mounted software authorized to the target vehicle.
Optionally, before detecting whether the target vehicle satisfies the use condition, the processing module further includes:
a detection unit for detecting a purchase type of the target software;
and the providing unit is used for directly providing the application service of the target vehicle-mounted software if the purchase type is a permanent type. An embodiment of a third aspect of the present application provides a vehicle, comprising: the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the vehicle-mounted software selling method according to the embodiment.
A fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, the program being executed by a processor for implementing the method for selling onboard software according to the above embodiment.
Therefore, the software purchase request of the vehicle owner can be received, the order to be paid of the target vehicle-mounted software is generated according to the software purchase request, after the order to be paid is paid, the software list change information is sent to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the use permission of the target vehicle on the target vehicle-mounted software is authorized, and the use permission of the target vehicle on the target vehicle is stopped when the target vehicle is detected not to meet the use condition. Therefore, the selling of the whole vehicle software or the service software is realized, and the safety of related service control is realized.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flow chart of a vehicle software selling method provided according to an embodiment of the application;
FIG. 2 is an exemplary diagram of an in-vehicle software vending service system according to one embodiment of the present application;
FIG. 3 is a schematic view of a vehicle interior support assembly according to one embodiment of the present application;
FIG. 4 is a flow chart of a method for selling onboard software according to one embodiment of the present application;
FIG. 5 is a flow chart of a vehicle end software or service validity check according to one embodiment of the present application;
FIG. 6 is an exemplary diagram of an in-vehicle software vending apparatus according to an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a vehicle according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
An in-vehicle software selling method, an in-vehicle software selling device, a vehicle, and a storage medium according to an embodiment of the present application will be described below with reference to the drawings. In order to solve the problem of vehicle-mounted software selling mentioned in the background technology center, the application provides a vehicle-mounted software selling method, in the method, a software purchase request of a vehicle owner can be received, a to-be-paid order of target vehicle-mounted software is generated according to the software purchase request, after the to-be-paid order is completed, software list change information is sent to a target vehicle according to an identity of the target vehicle corresponding to the software purchase request, the use permission of the target vehicle-mounted software is authorized, and the use permission of the target vehicle-mounted software is stopped when the target vehicle is detected not to meet the use condition. Therefore, the selling of the whole vehicle software or the service software is realized, and the safety of related service control is realized.
Specifically, fig. 1 is a schematic flow chart of a vehicle-mounted software selling method according to an embodiment of the present application.
In the embodiment, the whole vehicle software functions or services are taken as a plurality of virtual commodities which can be sold independently for shelf loading and unloading management, the expansion or starting of the sold vehicle functions is realized by using a remote upgrading mode, and the software services are rejected or stopped by a vehicle end control center after the software availability is exceeded.
As shown in fig. 2, fig. 2 is a schematic view of a vehicle-mounted software selling service system related to a vehicle-mounted software selling method according to an embodiment of the present application, where the system includes a server side and a vehicle side. The server side comprises a gateway, a Service selling application server, a database, a file server, an OTA (Over-the-Air Technology, space download Technology) platform, a TSP (Telematics Service Provider) platform and a payment platform; the vehicle end comprises a software registration center, an encryption and decryption unit and a vehicle end software registration database. The gateway is a server which directly provides service interface exposure for the outside; the application server provides the actual program and logic realization of the service interface and provides the timing execution program realization; the database stores order purchase records, payment records, sale signatures, validity periods, validity times configurations and the like.
Further, as shown in FIG. 3, FIG. 3 is a schematic view of a vehicle interior support assembly. The vehicle-end software registration center provides a service availability check service interface; the registration service center comprises a service providing unit, an encryption and decryption unit and a vehicle-end software registration database; the service providing unit is responsible for logic control, and the encryption and decryption unit is responsible for data reinforcement on the request and receipt data to prevent cracking; the vehicle-end software registration database is used for retrieving service validity periods and other validity controls according to the sale signatures. The software registration center is installed in an intelligent ECU (Electronic Control Unit), and is in network communication with other intelligent ECU devices through a vehicle-mounted gateway, and software service Control of the non-intelligent ECU devices is replaced by Control of the intelligent ECU devices.
Specifically, as shown in fig. 1, the vehicle-mounted software selling method includes the following steps:
in step S101, a software purchase request of a vehicle owner is received.
In step S102, a to-be-paid order of the target vehicle-mounted software is generated according to the software purchase request, and after the payment is completed in the to-be-paid order, software list change information is sent to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, so as to authorize the use permission of the target vehicle-mounted software by the target vehicle.
Specifically, an owner can purchase an application or service to be purchased through a large screen of the Vehicle or a mobile phone app of the owner to generate a purchase order, the system records a Vehicle VIN (Vehicle Identification Number), a hardware serial Number, a software code, the Number of times of purchasing the service or the time of purchasing the service, and the like, and the owner completes payment through a payment channel.
Optionally, in some embodiments, after sending the software inventory change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the method further includes: generating a selling signature record according to the order to be paid; and determining the purchase time range and/or the service validation mode of the target vehicle-mounted software according to the sale signature record, and determining the use condition.
Specifically, the system receives the successful payment order state change message of the owner of the payment platform, generates a corresponding selling signature character string for the owner through the selling order information, and recording a bound vehicle owner purchase order, informing the OTA platform and the TSP platform that the vehicle owner has successfully purchased service by the system, informing the vehicle end that a software selling list state needs to be actively pulled from the selling system by the OTA platform and the TSP platform through a push channel or a vehicle end active pulling mode, forwarding the TBox of the target vehicle to a software registration center after receiving the notification message, triggering the operation of synchronously pulling the software selling list from a server end after the software registration center of the target vehicle receives an update reminding notification message or a vehicle internal ignition message, storing the synchronous software selling list into a local database by the software registration center, and performing digital obfuscation on key validity period information to increase cracking difficulty.
Optionally, in some embodiments, after authorizing the right of the target vehicle to use the target on-board software, the method further includes: when the target vehicle is detected to open the target vehicle-mounted software, acquiring a matching result of the vehicle-side service registration center on the service fingerprint of the target vehicle-mounted software; if the matching result is matching and the current service of the target vehicle-mounted software is effective, judging whether the target vehicle-mounted software needs to be installed; and if the target vehicle-mounted software needs to be installed, sending an installation package to the target vehicle, otherwise, directly providing the application service of the target vehicle-mounted software.
Specifically, after receiving the request, the vehicle-side service registration center performs certain digital confusion processing on the request, queries a local database, checks whether the request is matched, judges whether the service or the software is in an effective state if the request is matched, and returns the service or the software to the requested application software or the intelligent ECU program. And the application software or the intelligent ECU program receives the return information allowing operation and starts the service or the software normally.
In step S103, upon detecting that the target vehicle does not satisfy the use condition, the authorization of the use authority of the target in-vehicle software to the target vehicle is stopped.
Optionally, in some embodiments, the method of the embodiments of the present invention further includes: when the use permission of the target vehicle authorized target vehicle-mounted software is stopped, a software expiration prompt is carried out on a vehicle owner, and/or a purchase prompt and/or a fee renewal prompt of the target vehicle software is pushed, and the use permission of the target vehicle authorized target vehicle-mounted software is obtained again.
That is, the application software or the intelligent ECU program receives the return information that the operation is not allowed, and prompts the vehicle owner to purchase the service or renew the fee and then use the service through a large screen of the vehicle or other modes.
Optionally, in some embodiments, before detecting whether the target vehicle satisfies the use condition, the method further includes: detecting the purchase type of the target software; and if the purchase type is a permanent type, directly providing the application service of the target vehicle-mounted software.
That is to say, the vehicle-mounted software of the embodiment of the application can be purchased in a time-sharing manner or permanently, and if the vehicle-mounted software is of a permanent type, the application service of the target vehicle-mounted software can be directly provided.
In summary, the embodiments of the present application may define a saleable software application or service, and define a saleable software or service through the software application or service identification information; configuring an incidence relation between software application, service and vehicle type, and defining a list of software application or service which can be sold in a specified vehicle type; configuring the vendable type of software or service (time-of-use purchase or permanent purchase, whether trial use is supported); the configuration software can be sold with version, whether remote downloading and installation are needed, corresponding installation task package codes, service codes, download update check addresses and the like; managing a request order and related payment information of a vehicle owner for applying for purchasing software or service; the issuing of a service opening or closing instruction after the management vehicle owner successfully pays; service-related digital signatures for a given vehicle are managed, along with the expiration date and status of the corresponding service. And each vehicle can sell software or service, and when the service is used or the service interface provided by the vehicle-end software service center is called regularly, the current service is judged to be allowed to be provided for the outside.
In order to enable those skilled in the art to further understand the selling method of the onboard software according to the embodiment of the present application, the following detailed description is provided with reference to specific embodiments.
As shown in fig. 4, the selling method of the vehicle-mounted software comprises the following steps:
s401, the owner selects the purchased service or application software to complete payment.
Specifically, the car owner purchases an application or service to be purchased through a large car-mounted screen or a car-owner mobile phone app to generate a purchase order, the system records the purchased vehicle VIN, a hardware serial number, a software code, the purchase service times or the purchase duration and the like, and the car owner completes payment through a payment channel.
S402, the service selling platform receives the order notice of the payment platform that the payment has been successfully paid.
Specifically, the system receives a successful payment order state change message of a vehicle owner of the payment platform, generates a corresponding selling signature character string for the vehicle owner through selling order information, and records and binds a purchasing order of the vehicle owner
And S403, the service selling platform informs the OTA or TSP platform to issue a software list change message to a target Vehicle (VIN).
Specifically, the system informs the OTA platform and the TSP platform that the owner has successfully purchased the service, and the OTA platform and the TSP platform inform the vehicle end that the software selling list state needs to be actively pulled from the selling system through a push channel or a vehicle end active pulling mode.
S404, the target vehicle receives the software list change information through a network connection system (Tbox).
S405, after receiving the software bill change information through the internet system (Tbox), the target vehicle actively requests the software selling platform to synchronize vehicle software/service bill information,
Specifically, the TBox of the target vehicle forwards the notification message to the software registration center after receiving the notification message, and the software registration center of the target vehicle triggers the operation of synchronously pulling the software selling list from the server after receiving the update reminding notification message or the vehicle internal ignition message.
And S406, updating the software list database of the vehicle end software center.
Specifically, the software registration center stores the synchronous software selling list into a local database, and performs digital confusion processing on key validity period information, so that the cracking difficulty is increased.
Further, as shown in fig. 5, the main step flow of checking the validity of the vehicle-end software or service includes the following steps:
s501, the owner requests to use or start a certain service or software.
S502, the application software or ECU requests the vehicle service registration center interface in the vehicle to check whether the service is allowed to be provided, if so, step S503 is executed, otherwise, step S504 is executed.
And S503, normally running the application software.
S504, informing an HMI (Human Machine Interface) that large screen image prompting software is due or not purchased, and guiding a vehicle owner to prompt purchase and renewal.
That is, the owner activates the service to be paid using the service or software application function to be paid; the application software or the intelligent ECU program generates signature information according to the service signature rule and requests an in-vehicle service registration center interface through the service signature information; after receiving the request, the vehicle-end service registration center performs certain digital confusion processing on the request, inquires a local database, checks whether the request is matched, judges whether the service or the software is in an effective state if the request is matched, and returns the service or the software to the requested application software or the intelligent ECU program; the application software or the intelligent ECU program receives the return information allowing operation and normally starts service or software; the application software or the intelligent ECU program receives the return information which is not allowed to run, and prompts the vehicle owner to purchase the service or renew the fee and then to use the service through a large screen of the vehicle or other modes.
Therefore, the automobile end software service registration center is used for realizing switching and registration management of automobile end software service, the server end is used for managing vehicle types and selling commodities, business links such as orders and payment are realized, and service digital signatures are carried out on the server end and the automobile end aiming at bearing equipment of related services to realize safety anti-cracking control of automobile end software service registration information.
According to the vehicle-mounted software selling method provided by the embodiment of the application, a software purchasing request of a vehicle owner can be received, a to-be-paid order of target vehicle-mounted software is generated according to the software purchasing request, after the to-be-paid order is paid, software list change information is sent to a target vehicle according to the identity of the target vehicle corresponding to the software purchasing request, the use permission of the target vehicle-mounted software is authorized by the target vehicle, and the use permission of the target vehicle-mounted software is stopped when the target vehicle is detected not to meet the use condition. Therefore, the selling of the whole vehicle software or the service software is realized, and the safety of related service control is realized.
Next, an in-vehicle software vending apparatus proposed according to an embodiment of the present application is described with reference to the drawings.
Fig. 6 is a block schematic diagram of an onboard software vending apparatus according to an embodiment of the present application.
As shown in fig. 6, the in-vehicle software vending apparatus 10 includes: a receiving module 100, an authorization module 200 and a processing module 300.
The receiving module 100 is configured to receive a software purchase request of a vehicle owner;
the authorization module 200 is configured to generate a to-be-paid order of the target vehicle-mounted software according to the software purchase request, and after the to-be-paid order completes payment, send software inventory change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, and authorize the use permission of the target vehicle for the target vehicle-mounted software; and
the processing module 300 is configured to stop authorizing the usage right of the target vehicle-mounted software to the target vehicle when detecting that the target vehicle does not satisfy the usage condition.
Optionally, after sending the software inventory change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the authorization module 200 further includes:
the generating unit is used for generating a selling signature record according to the order to be paid;
and the determining unit is used for determining the purchase time range and/or the service validation mode of the target vehicle-mounted software according to the sale signature record and determining the use condition.
Optionally, after authorizing the usage right of the target vehicle for the target on-board software, the authorization module 200 further includes:
the acquisition unit is used for acquiring a matching result of the vehicle-side service registration center on the service fingerprint of the target vehicle-mounted software when the target vehicle is detected to open the target vehicle-mounted software;
the judging unit is used for judging whether the target vehicle-mounted software needs to be installed or not when the matching result is matching and the current service of the target vehicle-mounted software is effective;
and the processing unit is used for sending the installation package to the target vehicle if the target vehicle-mounted software needs to be installed, and otherwise, directly providing the application service of the target vehicle-mounted software.
Optionally, the method further comprises:
and the prompting module is used for prompting the expiration of the software for the vehicle owner while stopping authorizing the use permission of the target vehicle-mounted software for the target vehicle, and/or pushing a purchase prompt and/or a fee renewal prompt of the target vehicle-mounted software, and reacquiring the use permission of the target vehicle-mounted software authorized for the target vehicle.
Optionally, before detecting whether the target vehicle satisfies the use condition, the processing module 300 further includes:
a detection unit for detecting a purchase type of the target software;
and the providing unit is used for directly providing the application service of the target vehicle-mounted software if the purchase type is a permanent type.
It should be noted that the foregoing explanation on the embodiment of the vehicle-mounted software selling method is also applicable to the vehicle-mounted software selling device of the embodiment, and details are not described here again.
According to the vehicle-mounted software selling device provided by the embodiment of the application, a software purchase request of a vehicle owner can be received, a to-be-paid order of target vehicle-mounted software is generated according to the software purchase request, after the to-be-paid order is paid, software list change information is sent to a target vehicle according to the identity of the target vehicle corresponding to the software purchase request, the use permission of the target vehicle-mounted software is authorized by the target vehicle, and the use permission of the target vehicle-mounted software is stopped when the target vehicle is detected not to meet the use condition. Therefore, the selling of the whole vehicle software or the service software is realized, and the safety of related service control is realized.
Fig. 7 is a schematic structural diagram of a vehicle according to an embodiment of the present application. The vehicle may include:
The processor 702, when executing the program, implements the in-vehicle software vending method provided in the above-described embodiments.
Further, the vehicle further includes:
a communication interface 703 for communication between the memory 701 and the processor 702.
A memory 701 for storing computer programs operable on the processor 702.
The memory 701 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
If the memory 701, the processor 702 and the communication interface 703 are implemented independently, the communication interface 703, the memory 701 and the processor 702 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.
Optionally, in a specific implementation, if the memory 701, the processor 702, and the communication interface 703 are integrated on a chip, the memory 701, the processor 702, and the communication interface 703 may complete mutual communication through an internal interface.
The processor 702 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present Application.
The present embodiment also provides a computer-readable storage medium on which a computer program is stored, characterized in that the program realizes the above-described in-vehicle software selling method when executed by a processor.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "N" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of implementing the embodiments of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
Claims (10)
1. A vehicle-mounted software selling method is characterized by comprising the following steps:
receiving a software purchase request of a vehicle owner;
generating a to-be-paid order of target vehicle-mounted software according to the software purchase request, and after the to-be-paid order is paid, sending software list change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request to authorize the use permission of the target vehicle on the target vehicle-mounted software; and when the target vehicle is detected not to meet the use condition, stopping authorizing the use authority of the target vehicle-mounted software to the target vehicle.
2. The method of claim 1, further comprising, after sending software inventory change information to the target vehicle based on the identity of the target vehicle to which the software purchase request corresponds:
generating a selling signature record according to the order to be paid;
and determining the purchase time range and/or the service validation mode of the target vehicle-mounted software according to the sale signature record, and determining the use condition.
3. The method of claim 1, further comprising, after authorizing the target vehicle's usage rights for the target on-board software,:
when the target vehicle is detected to open the target vehicle-mounted software, acquiring a matching result of a vehicle-end service registration center on the service fingerprint of the target vehicle-mounted software;
if the matching result is matching and the current service of the target vehicle-mounted software is effective, judging whether the target vehicle-mounted software needs to be installed;
and if the target vehicle-mounted software needs to be installed, sending an installation package to the target vehicle, otherwise, directly providing the application service of the target vehicle-mounted software.
4. The method of claim 1, further comprising:
when the use permission of the target vehicle-mounted software is authorized to the target vehicle is stopped, software expiration prompting is conducted on the vehicle owner, and/or purchase prompting and/or fee renewal prompting of the target vehicle-mounted software is pushed, and the use permission of the target vehicle-mounted software authorized to the target vehicle is obtained again.
5. The method according to any one of claims 1-4, further comprising, before detecting whether the target vehicle satisfies a use condition:
detecting a purchase type of the target software;
and if the purchase type is a permanent type, directly providing the application service of the target vehicle-mounted software.
6. An in-vehicle software vending apparatus, comprising:
the receiving module is used for receiving a software purchasing request of a vehicle owner;
the authorization module is used for generating a to-be-paid order of target vehicle-mounted software according to the software purchase request, sending software list change information to the target vehicle according to the identity of the target vehicle corresponding to the software purchase request after the to-be-paid order is paid, and authorizing the use permission of the target vehicle on the target vehicle-mounted software; and
and the processing module is used for stopping authorizing the target vehicle to the use authority of the target vehicle-mounted software when detecting that the target vehicle does not meet the use condition.
7. The apparatus of claim 6, wherein after sending the software inventory change information to the target vehicle based on the identification of the target vehicle corresponding to the software purchase request, the authorization module further comprises:
the generating unit is used for generating a selling signature record according to the order to be paid;
and the determining unit is used for determining the purchase time range and/or the service effective mode of the target vehicle-mounted software according to the sale signature record and determining the use condition.
8. The apparatus of claim 6, wherein after authorizing the target vehicle's usage rights for the target on-board software, the authorization module further comprises:
the acquisition unit is used for acquiring a matching result of a vehicle-end service registration center on the service fingerprint of the target vehicle-mounted software when the target vehicle is detected to open the target vehicle-mounted software;
the judging unit is used for judging whether the target vehicle-mounted software needs to be installed or not if the matching result is matching and the current service of the target vehicle-mounted software is effective;
and the processing unit is used for sending an installation package to the target vehicle if the target vehicle-mounted software needs to be installed, and otherwise, directly providing the application service of the target vehicle-mounted software.
9. A vehicle, characterized by comprising: memory, processor and computer program stored on the memory and executable on the processor, the processor executing the program to implement the in-vehicle software vending method according to any one of claims 1-5.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the program is executed by a processor for implementing an in-vehicle software vending method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111047418.4A CN113837828A (en) | 2021-09-07 | 2021-09-07 | Vehicle-mounted software selling method and device, vehicle and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111047418.4A CN113837828A (en) | 2021-09-07 | 2021-09-07 | Vehicle-mounted software selling method and device, vehicle and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113837828A true CN113837828A (en) | 2021-12-24 |
Family
ID=78958648
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111047418.4A Pending CN113837828A (en) | 2021-09-07 | 2021-09-07 | Vehicle-mounted software selling method and device, vehicle and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113837828A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710521A (en) * | 2022-03-11 | 2022-07-05 | 重庆长安汽车股份有限公司 | Vehicle cloud platform architecture system and method for realizing vehicle-mounted software payment authorization |
| CN114756428A (en) * | 2022-04-12 | 2022-07-15 | 广州汽车集团股份有限公司 | Internet of vehicles payment software monitoring method and system |
| CN115134149A (en) * | 2022-06-28 | 2022-09-30 | 重庆长安汽车股份有限公司 | Vehicle payment function authentication method and system based on cloud configuration |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120246704A1 (en) * | 2011-03-24 | 2012-09-27 | James Christopher Dorsey | Mobile software entitlements manager |
| CN110275743A (en) * | 2018-03-16 | 2019-09-24 | 长城汽车股份有限公司 | Skin change method, system and the vehicle at vehicle-mounted interface |
| CN110378687A (en) * | 2018-04-13 | 2019-10-25 | 福特全球技术公司 | Wireless digital for vehicle is paid |
| CN112597447A (en) * | 2020-12-15 | 2021-04-02 | 广州橙行智动汽车科技有限公司 | Vehicle-mounted service authorization activation method and device and vehicle |
| CN112784243A (en) * | 2021-03-04 | 2021-05-11 | 北京市商汤科技开发有限公司 | Authorization management method and device, electronic equipment and storage medium |
-
2021
- 2021-09-07 CN CN202111047418.4A patent/CN113837828A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120246704A1 (en) * | 2011-03-24 | 2012-09-27 | James Christopher Dorsey | Mobile software entitlements manager |
| CN110275743A (en) * | 2018-03-16 | 2019-09-24 | 长城汽车股份有限公司 | Skin change method, system and the vehicle at vehicle-mounted interface |
| CN110378687A (en) * | 2018-04-13 | 2019-10-25 | 福特全球技术公司 | Wireless digital for vehicle is paid |
| CN112597447A (en) * | 2020-12-15 | 2021-04-02 | 广州橙行智动汽车科技有限公司 | Vehicle-mounted service authorization activation method and device and vehicle |
| CN112784243A (en) * | 2021-03-04 | 2021-05-11 | 北京市商汤科技开发有限公司 | Authorization management method and device, electronic equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710521A (en) * | 2022-03-11 | 2022-07-05 | 重庆长安汽车股份有限公司 | Vehicle cloud platform architecture system and method for realizing vehicle-mounted software payment authorization |
| CN114756428A (en) * | 2022-04-12 | 2022-07-15 | 广州汽车集团股份有限公司 | Internet of vehicles payment software monitoring method and system |
| CN115134149A (en) * | 2022-06-28 | 2022-09-30 | 重庆长安汽车股份有限公司 | Vehicle payment function authentication method and system based on cloud configuration |
| CN115134149B (en) * | 2022-06-28 | 2023-06-06 | 重庆长安汽车股份有限公司 | Cloud configuration-based vehicle payment function authentication method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11733992B2 (en) | Center device | |
| CN113837828A (en) | Vehicle-mounted software selling method and device, vehicle and storage medium | |
| US11683197B2 (en) | Vehicle master device, update data distribution control method, computer program product and data structure of specification data | |
| US11669323B2 (en) | Vehicle electronic control system, program update notification control method and computer program product | |
| US11947953B2 (en) | Vehicle electronic control system, progress screen display control method and computer program product | |
| US20220179644A1 (en) | Vehicle electronic control system, vehicle master device, and rewrite instruction program product under specific mode | |
| US11960875B2 (en) | Vehicle master device, vehicle electronic control system, configuration setting information rewrite instruction method, and configuration setting information rewrite instruction program product | |
| US11671498B2 (en) | Vehicle master device, update data verification method and computer program product | |
| US11822366B2 (en) | Electronic control unit, vehicle electronic control system, rewrite execution method, rewrite execution program, and data structure of specification data | |
| US20210155177A1 (en) | Vehicle electronic control system, distribution package download determination method and computer program product | |
| US20210155252A1 (en) | Vehicle master device, control method for executing rollback, computer program product for executing rollback and data structure of specification data | |
| US11604637B2 (en) | Electronic control unit, vehicle electronic control system, difference data consistency determination method and computer program product | |
| US11467821B2 (en) | Vehicle master device, installation instruction determination method and computer program product | |
| US11928459B2 (en) | Electronic control unit, retry point specifying method and computer program product for specifying retry point | |
| US20210157492A1 (en) | Vehicle electronic control system, file transfer control method, computer program product and data structure of specification data | |
| US20210157574A1 (en) | Vehicle master device, non-rewrite target power supply administration method and computer program product | |
| US11926270B2 (en) | Display control device, rewrite progress display control method and computer program product | |
| US11941384B2 (en) | Vehicle master device, rewrite target group administration method, computer program product and data structure of specification data | |
| US20220179643A1 (en) | Vehicle master device, vehicle electronic control system, configuration setting information rewrite instruction method, and configuration setting information rewrite instruction program product | |
| US11656771B2 (en) | Electronic control unit, vehicle electronic control system, activation execution control method and computer program product | |
| US11907697B2 (en) | Vehicle electronic control system, center device, vehicle master device, display control information transmission control method, display control information reception control method, display control information transmission control program, and display control information reception control program | |
| US20230254374A1 (en) | Vehicle master device, update data verification method and computer program product | |
| CN110111447B (en) | Internet of vehicles verification method and device | |
| CN111325542B (en) | System and method for multiple authentication and payment with eSIM | |
| CN113254047A (en) | Vehicle configuration upgrading method, vehicle-mounted terminal, server, vehicle 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 |