CN116151829A - Vehicle payment function authorization method and device, vehicle end controller and vehicle - Google Patents
Vehicle payment function authorization method and device, vehicle end controller and vehicle Download PDFInfo
- Publication number
- CN116151829A CN116151829A CN202211695987.4A CN202211695987A CN116151829A CN 116151829 A CN116151829 A CN 116151829A CN 202211695987 A CN202211695987 A CN 202211695987A CN 116151829 A CN116151829 A CN 116151829A
- Authority
- CN
- China
- Prior art keywords
- function
- payment function
- vehicle
- target vehicle
- controller
- 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
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
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
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 relates to a vehicle payment function authorization method, a device, a vehicle end controller and a vehicle, wherein the method comprises the following steps: acquiring order information, and judging whether a controller software version of a target vehicle with a payment function to be used meets the function requirement according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; therefore, the user can continuously use the payment function according to the self requirement after purchasing the vehicle, and the limitation of using the payment function is widened.
Description
Technical Field
The application relates to the technical field of internet of vehicles, in particular to a vehicle payment function authorization method and device, a vehicle end controller and a vehicle.
Background
At present, with the continuous development of the Internet of vehicles, a mainstream vehicle enterprise builds a vehicle cloud platform, so that after selling vehicles, after-sale value-added services based on the Internet of vehicles can be continuously provided for vehicle owners, and the vehicle owners hope to realize profit by providing value-added services; such profitable value-added services are typically implemented by providing payment functionality in the in-vehicle software.
In the related technology, the paid vehicle and cloud cooperative authority management is mainly adopted in the vehicle payment function authorization, the authorization mode does not consider the follow-up problem of modification, and development and release of an APP end are required to be carried out when the functions are updated or added, so that certain limitations exist.
Disclosure of Invention
The application provides a vehicle payment function authorization method, a device, a vehicle end controller and a vehicle, which solve the problem that in the related art, the problem that the vehicle payment function authorization process does not consider upgrading and modifying occurs, so that a user can selectively purchase and use a value-added function after purchasing the vehicle, and the vehicle has sustainable upgrading and charging capabilities, thereby widening the limitation.
An embodiment of a first aspect of the present application provides a method for authorizing a payment function of a vehicle, including the steps of: acquiring order information; judging whether the controller software version of the target vehicle with the payment function meets the function requirement according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; and receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle.
According to the technical means, the embodiment of the application judges whether the controller software version of the target vehicle with the payment function to be used meets the function requirement according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; the user can continuously use the payment function according to the own requirements after purchasing the vehicle, so that the limitation of using the payment function is widened.
Further, if the controller software version of the target vehicle to be used with the payment function does not meet the function requirement, an upgrade package is sent to an OTA system, so that the controller software version is upgraded according to the upgrade package, and the controller software version meets the function requirement.
According to the technical means, the embodiment of the application can update the version of the controller software by acquiring the update package meeting the version of the controller software, so that a user can continue to use the updated payment function.
Further, after completing the payment function authorization of the target vehicle, the method further includes: receiving a function use request; judging whether the rights and interests meet the requirements according to the function use request; and if so, allowing the target vehicle to use the function, and if not, controlling the controller of the target vehicle to close the configuration code brush so as to reject the target vehicle to use the function.
According to the technical means, whether the requirements are met or not can be judged according to the rights and interests created during authorization when the user uses the payment function each time, so that the vehicle-end payment function can be turned on or off according to the corresponding result, and real-time management can be better performed.
Further, before order information is acquired, the payment function is also created, wherein the created content comprises basic information of the payment function, a vehicle controller and a software version which are correspondingly used by the payment function, a configuration code for activating the payment function and a configuration code for closing the payment function.
Further, before order information is acquired, corresponding rights and interests are defined according to the payment function, wherein defined contents comprise a body of rights and interests metering mode.
Further, before order information is acquired, corresponding basic flow creation is performed according to the payment function, wherein the created content comprises a plurality of key nodes in the basic flow creation.
Further, before order information is acquired, corresponding commodity creation and release are also carried out according to the payment function.
According to the technical means, the corresponding content is created in advance, so that the operation can be performed according to the created content in the subsequent authorization.
An embodiment of a second aspect of the present application provides a vehicle payment function authorization device, including: the acquisition module is used for acquiring order information; the judging module is used for judging whether the controller software version of the target vehicle with the payment function to be used meets the function requirement according to the order information; the activation module is used for sending a configuration code to the target vehicle when judging that the controller software version of the target vehicle with the payment function meets the function requirement, so that the controller of the target vehicle activates the payment function according to the configuration code; and the rights creation module is used for receiving the activation result and creating rights according to the activation result so as to complete payment function authorization of the target vehicle.
An embodiment of a third aspect of the present invention provides a vehicle-end controller, where the vehicle-end controller is configured to activate a payment function of a vehicle according to a configuration code issued by a server, and obtain an activation result, where the server is configured to obtain order information, determine, according to the order information, whether a controller software version of a target vehicle to which the payment function is to be used meets a function requirement, and if the controller software version of the target vehicle to which the payment function is to be used meets the function requirement, send the configuration code to the target vehicle, receive the activation result, and create rights according to the activation result, so as to complete payment function authorization of the target vehicle.
An embodiment of a fourth aspect of the present application provides a vehicle including the vehicle end controller described above.
An embodiment of a fifth aspect of the present application provides a server, including: the vehicle payment function authorization method comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the program to realize the vehicle payment function authorization method according to the embodiment.
A sixth aspect of the present invention provides a computer-readable storage medium storing computer instructions for causing the computer to execute the vehicle payment function authorization method according to the above embodiment.
According to the embodiment of the application, the order information can be acquired after the user places an order, and whether the controller software version of the target vehicle with the payment function to be used meets the function requirement is judged according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; after the activation is successful, receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; therefore, the user can continuously use the payment function according to the self requirement after purchasing the vehicle, and the limitation of using the payment function is widened.
Additional aspects and advantages of the 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 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, in which:
FIG. 1 is a flow chart of a method for authorizing a vehicle payment function according to an embodiment of the present application;
FIG. 2 is a flow chart of function creation according to one embodiment of the present application;
FIG. 3 is a flow chart of a benefit definition according to one embodiment of the present application;
FIG. 4 is a flow chart of functional flow creation according to one embodiment of the present application;
FIG. 5 is a flow chart of product creation and distribution according to one embodiment of the present application;
FIG. 6 is a flow chart of a method for authorizing a vehicle payment function according to one embodiment of the present application;
FIG. 7 is a flow chart of a payment function use according to one embodiment of the present application;
FIG. 8 is a schematic diagram of a vehicle payment function authorization device according to an embodiment of the present application;
fig. 9 is an exemplary diagram of a server according to an embodiment of the present application.
Wherein, 10-the vehicle pays the function authorization device; 100-acquisition module, 200-judgment module, 300-activation module, 400-rights creation module.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present application and are not to be construed as limiting the present application.
The following describes a vehicle payment function authorization method, a device, a vehicle end controller and a vehicle according to the embodiments of the present application with reference to the accompanying drawings. Aiming at the problem that the vehicle payment function authorization process mentioned in the background art center does not consider the problem after upgrading and changing, the application provides a vehicle payment function authorization method, in the method, order information can be acquired after a user places an order, and whether the controller software version of a target vehicle with a payment function to be used meets the function requirement is judged according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; after the activation is successful, receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; the user can continuously use the payment function according to the own requirements after purchasing the vehicle, so that the limitation of using the payment function is widened.
Specifically, fig. 1 is a flow chart of a vehicle payment function authorization method according to an embodiment of the present application.
As shown in fig. 1, the vehicle payment function authorization method includes the steps of:
in step S101, order information is acquired.
It should be noted that the user may purchase the required payment function in the digital mall to generate the order information.
Further, in some embodiments, before the order information is obtained, a payment function is created, wherein the created content includes basic information of the payment function, a vehicle controller and a software version used by the payment function, a configuration code for activating the payment function, and a configuration code for turning off the payment function.
That is, when the payment function is created, in addition to basic information such as name, code, description, it is necessary to define the controller on the vehicle end to which the payment function is associated, and the lowest software version that all controllers using the payment function need to reach; the information can be obtained and selected from an OTA system; meanwhile, configuration codes which are required to be used for activating and closing the payment function are defined, each configuration code for activating and closing the payment function consists of a string of character strings, and the information on the configuration codes manages the on-off states of all controllers; the support of the function by the controller is in an on state when the vehicle end writes the activated configuration code, and is in an off state when the vehicle end writes the closed configuration code.
As a specific embodiment, as shown in fig. 2, the flow chart of the function creation includes the following steps:
s201, create function: name, code, and description.
That is, the function management system first creates a basic function including a function name, an encoding, and a description.
S202, requesting a vehicle controller and a software version.
That is, the function management system sends a request to the OTA system to acquire the vehicle controller and the software version.
S203, returning to the vehicle controller and the software version.
That is, the OTA system returns the vehicle controller and software version to the function management system.
S204, associating 1-n controllers and the lowest software version of each controller.
S205, the developer inputs the function activation configuration code and the closing configuration code.
S206, the function creation is completed.
It should be noted that, the function management system is mainly responsible for defining functions, including a controller, a controller software version and a function activation and closing configuration code associated with the functions.
Further, in some embodiments, prior to obtaining the order information, a corresponding equity definition is also made according to the payment function, wherein the defined content includes the principal of the equity and the metering manner of the equity.
That is, rights are defined for functions in the cloud rights center, which mainly includes the main body of the rights: vehicle/user; rights metering mode: time, volume, time.
As a specific example, as shown in fig. 3, the flow chart of the benefit definition includes the following steps:
s301, requesting a function list.
That is, the cloud rights center sends a request to acquire a function list to the function management system.
S302, returning to the function list.
That is, the function management system returns the list of functions to the cloud rights center.
S303, selecting function definition rights and interests.
S304, setting a rights main body.
S305, setting a rights metering mode.
S306, rights and interests are defined.
The cloud rights center is mainly responsible for defining rights and interests of the functions, creating rights and interests examples of the functions for the users after the users purchase the functions, synchronizing data with the vehicle-end rights center, and recording information such as use, change, balance and the like of the rights and interests.
Further, in some embodiments, prior to obtaining the order information, a corresponding active basic flow creation is also performed according to the payment function, wherein the created content includes a plurality of key nodes in the created basic flow.
That is, a flow template is created for function payment and activation; the flow comprises at least 4 nodes: judging whether the user vehicle meets the function requirement, pushing an upgrade package for the user, sending an activation code for the user, and creating rights and interests for the user.
As a specific embodiment, as shown in fig. 4, the flowchart created by the functional flow includes the following steps:
s401, request a function list.
That is, the function activating system transmits a request for acquiring a function list to the function managing system.
S402, returning to the function list.
That is, the function management system returns the function list to the function activation system.
S403, selecting a function creation flow.
It should be noted that, four nodes are created, specifically including node 1: transmitting a controller version judgment instruction to the OTA system, wherein node 2: sending a push upgrade package instruction to an OTA system, wherein node 3: transmitting the configuration code to the vehicle-end rights center, and node 4: and sending a rights example creation instruction to the cloud rights center.
S404, completing configuration of the node flow relation.
S405, the function flow creation is completed.
It should be noted that, the function activation system is mainly responsible for constructing a flow and an engine required for activating a certain function; after the user purchases, the task is sent to the business system required by the function activation.
Further, in some embodiments, prior to acquiring the order information, corresponding merchandise creation and release is also performed according to a payment function.
That is, in the digital mall platform, SPU, SKU, and merchandise are created based on functionality; configuring detailed information of commodities, payment modes, selling channels, discounts, full-reduction information, released vehicle types and the like; after the commodity is created, the user can see the commodity and purchase the commodity in channels such as a car end APP, a car and machine mall and the like.
As a specific embodiment, as shown in fig. 5, the flow chart of commodity creation and distribution includes the following steps:
s501, request a function list.
That is, the digital mall platform sends a get function list request to the function management system.
S502, returning to the function list.
That is, the function management system returns the list of functions to the digital mall platform.
S503, selecting a function to create a commodity.
S504, filling commodity information, payment modes, selling channels and the like.
S505, selecting a release vehicle type range to finish commodity creation.
S506, finishing commodity shelf loading.
It should be noted that, the digital mall platform is mainly responsible for commercial packaging of functions, so that users can pay for purchase.
In step S102, it is determined whether the controller software version of the target vehicle to which the payment function is to be applied satisfies the function requirement according to the order information.
That is, the controller software version of the target vehicle to be used with the payment function is judged through the order information in the authorization process, so that the authorized target vehicle can normally use the payment function corresponding to the order information.
In step S103, if the controller software version of the target vehicle to which the payment function is to be applied satisfies the function requirements, a configuration code is transmitted to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code.
That is, the controller of the target vehicle is controlled by the created configuration code corresponding to the payment function so as to enable the controller to support the payment function.
As an embodiment, if the controller software version of the target vehicle to which the payment function is to be applied does not meet the function requirement, an upgrade package is sent to the OTA system, so that the version of the controller software is upgraded according to the upgrade package to meet the function requirement.
In step S104, an activation result is received, and rights are created according to the activation result to complete payment function authorization of the target vehicle.
Specifically, the embodiment can acquire order information after the user places an order, and judge whether the controller software version of the target vehicle with the payment function meets the function requirement according to the order information; if a target vehicle is to use a payment function
If the controller software version of the vehicle meets the function requirement, transmitting a configuration code to the target vehicle so that the controller of the target vehicle activates a payment function according to the configuration code 5; receiving the activation result after the activation is successful, and creating rights according to the activation result to
Completing payment function authorization of the target vehicle; therefore, the user can continuously use the payment function according to the self requirement after purchasing the vehicle, and the limitation of using the payment function is widened.
In order to enable those skilled in the art to further understand the vehicle payment function authorization method according to the embodiments of the present application, the following detailed description is provided with reference to specific embodiments.
0 specifically, as shown in fig. 6, fig. 6 is a flow chart of a vehicle payment function authorization method according to one embodiment of the present application
The vehicle payment function authorization method comprises the following steps:
s601, checking and purchasing the commodity.
It should be noted that, the user views and purchases the commodity, wherein the commodity is a payment function.
S602, generating an order.
And 5S603, sending an instruction to the OTA system, and judging whether the user vehicle controller meets the functional requirement.
S604, finishing the controller version judgment and returning the result.
S605, judging whether the test result is satisfied. If yes, step S609 is performed; if not, step S606 is performed.
S606, sending an instruction for pushing the upgrade package for the user to the OTA system.
S607, pushing the upgrade package to the user vehicle.
0S608, the OTA upgrade is completed for the vehicle, and the step S603 is executed back.
S609, sending the configuration code to the vehicle-end rights center.
S610, receiving the configuration code and instructing controllers at the vehicle end to execute configuration code refreshing.
S611, the activated configuration code is written and the result is reported.
S612, reporting the execution result of the configuration code.
5S613, creating a benefit example for the user.
S614, creating a right instance.
S615, rights and interests instance synchronization.
That is, the rights and interests instance is synchronized to the vehicle end rights and interests center.
S616, the function is in an available state.
0, that is, after the user completes the purchase, starting the flow engine; the process engine sends instructions to each service system and judges
Whether the flow path node is complete. The method comprises the following steps: after the user completes function purchase, the flow engine sends an instruction to the OTA system to judge whether the controller software of the user vehicle meets the minimum version requirement of the function; when the requirements of the functions are not met, an instruction is sent to an OTA system, and the upgrade package is pushed for a user; after the user finishes OTA upgrading, sending a function activation and closing configuration code to the vehicle-end rights center, executing configuration code refreshing by the vehicle-end rights center, and reporting the result to the flow engine; after the user completes the function activation, a function benefit instance is created to the cloud end benefit center and synchronized to the vehicle end benefit center.
The vehicle-end rights center is mainly responsible for reporting rights and interests use records to the cloud end, acquiring the latest rights and interests state from the cloud end rights and interests center, and sending an activation and closing configuration code to each controller at the vehicle end based on the rights and interests state and rights and interests use condition to control actual opening or closing of functions.
In addition, after the payment function authorization of the target vehicle is completed, further comprising: firstly, receiving a function use request; then, judging whether the rights and interests meet the requirements according to the function use request; if so, allowing the target vehicle to use the function, and if not, controlling the controller of the target vehicle to close the configuration code brush to reject the target vehicle to use the function.
As a specific example, as shown in fig. 7, the flowchart used by the payment function includes the following steps:
s701, a request is made to use a function.
That is, when the user needs to use the payment function, a request for using the function is transmitted to the vehicle-side rights center through the vehicle-side.
S702, judging whether the balance of rights and interests is enough. If so, step S705 is performed; if not, step S703 is performed.
S703, the vehicle-side controller is instructed to flush the shutdown configuration code, and then step S704 and step S707 are executed simultaneously.
S704, the configuration code brushing is completed, and the function is closed.
S705, normal use functions.
S706, recording function usage information.
S707, recording and reporting rights and interests changing information.
S708, updating the rights and interests changing information.
That is, the cloud rights center manages the balance of the functional rights and synchronizes to the vehicle-end rights center; when the vehicle end uses the function, authenticating the vehicle end rights center, and when the vehicle end is in the effective period, allowing the function to be used, metering the vehicle end rights center and synchronizing the vehicle end rights center with the cloud; when the balance is exhausted, the function is refused to use, and the writing of the closing configuration code is executed.
It should be noted that, the above process can implement payment authorization of all vehicle end functions including automatic driving; by configuring specific nodes of the function activation engine, the method can also support the theme, wallpaper and application of the intelligent automobile, including remote control functions and the like.
According to the vehicle payment function authorization method provided by the embodiment of the application, the order information can be acquired after the user places an order, and whether the controller software version of the target vehicle with the payment function to be used meets the function requirement is judged according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; after the activation is successful, receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; the user can continuously use the payment function according to the own requirements after purchasing the vehicle, so that the limitation of using the payment function is widened.
Next, a vehicle payment function authorization device according to an embodiment of the present application will be described with reference to the accompanying drawings.
Fig. 8 is a block diagram of a vehicle payment function authorization device according to an embodiment of the present application.
As shown in fig. 8, the vehicle payment function authorization device 10 includes: the system comprises an acquisition module 100, a judgment module 200, an activation module 300 and a benefit creation module 400.
Wherein, the acquiring module 100 is configured to acquire order information;
the judging module 200 is used for judging whether the controller software version of the target vehicle with the payment function to be used meets the function requirement according to the order information;
an activation module 300, configured to send a configuration code to the target vehicle when it is determined that the controller software version of the target vehicle to which the payment function is to be applied meets the function requirement, so that the controller of the target vehicle activates the payment function according to the configuration code;
the rights creation module 400 is configured to receive the activation result and create rights according to the activation result, so as to complete payment function authorization of the target vehicle.
Further, the system also comprises a version upgrading module which is used for sending an upgrading packet to the OTA system when the controller software version of the target vehicle with the payment function does not meet the function requirement, so that the version of the controller software is upgraded according to the upgrading packet to meet the function requirement.
Further, after completing the payment function authorization of the target vehicle, it further includes: receiving a function use request; judging whether the rights and interests meet the requirements according to the function use request; if so, allowing the target vehicle to use the function, and if not, controlling the controller of the target vehicle to close the configuration code brush to reject the target vehicle to use the function.
Further, before order information is acquired, a payment function is created, wherein the created content comprises basic information of the payment function, a vehicle controller and a software version which are correspondingly used by the payment function, a configuration code for activating the payment function and a configuration code for closing the payment function.
Further, before order information is acquired, corresponding rights and interests are defined according to the payment function, wherein the defined contents comprise the rights and interests main body and rights and interests metering mode.
Further, before order information is acquired, corresponding basic flow creation is performed according to the payment function, wherein the created content comprises a plurality of key nodes in the basic flow creation.
Further, before order information is acquired, corresponding commodity creation and release are also performed according to the payment function.
It should be noted that the foregoing explanation of the embodiment of the vehicle payment function authorization method is also applicable to the vehicle payment function authorization device of this embodiment, and will not be repeated here.
According to the vehicle payment function authorization device provided by the embodiment of the application, the order information can be acquired after the user places an order, and whether the controller software version of the target vehicle with the payment function to be used meets the function requirement is judged according to the order information; if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code; after the activation is successful, receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle; the user can continuously use the payment function according to the own requirements after purchasing the vehicle, so that the limitation of using the payment function is widened.
The embodiment of the application also provides a vehicle-end controller, wherein the vehicle-end controller is used for activating the payment function of the vehicle according to the configuration code issued by the server to obtain an activation result, the server is used for acquiring order information, judging whether the controller software version of the target vehicle with the payment function meets the function requirement according to the order information, if the controller software version of the target vehicle with the payment function meets the function requirement, sending the configuration code to the target vehicle, receiving the activation result, and creating rights according to the activation result to complete payment function authorization of the target vehicle.
The embodiment of the application also provides a vehicle, which comprises the vehicle end controller.
Fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application. The server may include:
The processor 902 implements the vehicle payment function authorization method provided in the above embodiment when executing the program.
Further, the server further includes:
a communication interface 903 for communication between the memory 901 and the processor 902.
If the memory 901, the processor 902, and the communication interface 903 are implemented independently, the communication interface 903, the memory 901, and the processor 902 may be connected to each other through a bus and perform communication with each other. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 901, the processor 902, and the communication interface 903 are integrated on a chip, the memory 901, the processor 902, and the communication interface 903 may communicate with each other through internal interfaces.
The processor 902 may be a central processing unit (Central Processing Unit, abbreviated as CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more integrated circuits configured to implement embodiments of the present application.
The embodiment of the application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the vehicle payment function authorization method as above.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," 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 present application. In this specification, schematic representations of the above terms are not necessarily directed 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, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless explicitly defined 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 specific logical functions or steps of the process, and further 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 the embodiments of the present application.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or N wires, a portable computer cartridge (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described 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. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like. Although embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.
Claims (13)
1. A method for authorizing a vehicle payment function, comprising the steps of:
acquiring order information;
judging whether the controller software version of the target vehicle with the payment function meets the function requirement according to the order information;
if the controller software version of the target vehicle to be used with the payment function meets the function requirement, sending a configuration code to the target vehicle so that the controller of the target vehicle activates the payment function according to the configuration code;
and receiving an activation result, and creating rights and interests according to the activation result so as to complete payment function authorization of the target vehicle.
2. The method of claim 1, wherein if the controller software version of the target vehicle for which the payment function is to be used does not meet the function requirement, sending an upgrade package to an OTA system to upgrade the version of the controller software according to the upgrade package so as to meet the function requirement.
3. The method of claim 2, further comprising, after completing the payment function authorization of the target vehicle:
receiving a function use request;
judging whether the rights and interests meet the requirements according to the function use request;
and if so, allowing the target vehicle to use the function, and if not, controlling the controller of the target vehicle to close the configuration code brush so as to reject the target vehicle to use the function.
4. The method of claim 1, wherein the payment function is further created prior to acquiring order information, wherein the created content includes basic information of the payment function, a vehicle controller and software version to which the payment function corresponds, a configuration code to activate the payment function, and a configuration code to deactivate the payment function.
5. The method of claim 1, further comprising defining corresponding equity according to the payment function prior to acquiring order information, wherein the defined content includes a principal of equity and a metering of equity.
6. The method of claim 1, wherein prior to obtaining order information, corresponding active basic flow creation is further performed in accordance with the payment function, wherein creating content includes creating a plurality of key nodes in the basic flow.
7. The method of claim 1, wherein prior to acquiring order information, corresponding merchandise creation and release is also performed in accordance with the payment function.
8. A vehicle payment function authorization device, comprising:
the acquisition module is used for acquiring order information;
the judging module is used for judging whether the controller software version of the target vehicle with the payment function to be used meets the function requirement according to the order information;
the activation module is used for sending a configuration code to the target vehicle when judging that the controller software version of the target vehicle with the payment function meets the function requirement, so that the controller of the target vehicle activates the payment function according to the configuration code;
and the rights creation module is used for receiving the activation result and creating rights according to the activation result so as to complete payment function authorization of the target vehicle.
9. The apparatus as recited in claim 8, further comprising:
and the version upgrading module is used for sending an upgrading packet to the OTA system when the controller software version of the target vehicle with the payment function does not meet the function requirement, so that the version of the controller software is upgraded according to the upgrading packet to meet the function requirement.
10. The vehicle-end controller is characterized in that the vehicle-end controller is used for activating the payment function of a vehicle according to a configuration code issued by a server to obtain an activation result, wherein the server is used for acquiring order information, judging whether the controller software version of a target vehicle with the payment function meets the function requirement according to the order information, if the controller software version of the target vehicle with the payment function meets the function requirement, sending the configuration code to the target vehicle, receiving the activation result, and creating rights according to the activation result to complete payment function authorization of the target vehicle.
11. A vehicle comprising the vehicle end controller of claim 10.
12. A server, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the program to implement the vehicle payment function authorization method according to any one of claims 1 to 7.
13. A computer-readable storage medium having stored thereon a computer program, characterized in that the program is executed by a processor for implementing a vehicle payment function authorization method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211695987.4A CN116151829A (en) | 2022-12-28 | 2022-12-28 | Vehicle payment function authorization method and device, vehicle end controller and vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211695987.4A CN116151829A (en) | 2022-12-28 | 2022-12-28 | Vehicle payment function authorization method and device, vehicle end controller and vehicle |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116151829A true CN116151829A (en) | 2023-05-23 |
Family
ID=86361210
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211695987.4A Pending CN116151829A (en) | 2022-12-28 | 2022-12-28 | Vehicle payment function authorization method and device, vehicle end controller and vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116151829A (en) |
-
2022
- 2022-12-28 CN CN202211695987.4A patent/CN116151829A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106257416B (en) | Method for wireless remote updating of vehicle software | |
| CN106257420B (en) | Method for updating ECU using differential update package | |
| CN108985774B (en) | Excitation method, device, equipment and storage medium of block chain network | |
| CN108959621B (en) | Method, device, equipment and storage medium for realizing block chain network | |
| US9841965B2 (en) | Centralized system for software updating vehicle components | |
| CN110300954B (en) | Control device, program update method, and computer program | |
| US10165084B2 (en) | Method for software updating of vehicle components | |
| US10101992B2 (en) | Telematics control unit comprising a differential update package | |
| US10127036B2 (en) | Method for OTA updating vehicle electronic control unit | |
| JP2019007954A (en) | Road traffic management | |
| CN108241494A (en) | Vehicle Electronic Control Unit upgrade method, device, vehicle control electronics and vehicle | |
| JP2019191742A (en) | On-vehicle update device, on-vehicle update system, update processing method, and update processing program | |
| US20230033167A1 (en) | Vehicle electronic control system, data initialization method, center device, vehicle master device, storage medium for storing initialization package distribution program, and storage medium storing data initialization program | |
| CN110990034A (en) | ECU upgrading method and system, electronic equipment and storage medium | |
| CN113837828A (en) | Vehicle-mounted software selling method and device, vehicle and storage medium | |
| WO2018189975A1 (en) | Relay apparatus, transfer method, and computer program | |
| CN115208910B (en) | Cloud configuration method and device for vehicle | |
| CN108710497A (en) | A kind of method for updating system of vehicle-mounted middle control and vehicle-mounted middle control | |
| CN115967720A (en) | Activation of ADS features based on subscription | |
| JP2008030691A (en) | Message management device of vehicular control system, and vehicular control system | |
| CN116151829A (en) | Vehicle payment function authorization method and device, vehicle end controller and vehicle | |
| US11077861B2 (en) | Control apparatus for enabling functions, motor vehicle having a control apparatus and method for operating a control apparatus | |
| CN104737174A (en) | Application modes determined from previous and current states of a license | |
| CN106254440A (en) | The upgrade method of a kind of AP and device | |
| JP2021081780A (en) | Vehicle electronic control system, data repeating device, distribution control method of campaign information and distribution control program of campaign information |
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 |