Payment system in a vehicle hardware and software environment
A universal and abstracted interface in vehicle payment systems facilitates the integration of new services without network modifications, enhancing flexibility and efficiency.
Patent Information
- Application Number
- JP2024527456
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-16
- Filing Date
- 2022-10-24
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2042-10-24
AI Technical Summary
Existing vehicle payment systems require pre-defined user interfaces and adaptations in the vehicle network communication for each payment service or application, limiting flexibility and efficiency.
A payment system with a static, universal, and abstracted interface between the backend and user interface, along with dynamic application-dependent interfaces, allowing seamless integration of new services without altering vehicle network communication.
Enables flexible introduction of new payment services and applications without modifying vehicle network interfaces, optimizing resource use and reducing development efforts and costs.
Smart Images

Figure 2024543393000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a payment system in a hardware and software environment in a vehicle, as more precisely defined in the preamble of claim 1. [Background technology]
[0002] Basically, payment systems are known from the prior art which are displayed in the vehicle and which are able to trigger a payment process. For example, Patent Document 1 describes a vehicle payment system that allows a payment order to be wirelessly received from outside and processed from the vehicle.
[0003] However, known payment systems are limited and customized to one known application case, and therefore the visualization and operation using the in-vehicle User Interface (UI) must be defined prior to implementation, since the communication relationships of all involved control devices must be adapted prior to implementation in order to provide and display the necessary information of all involved control devices in a way that is tailored to the application case.
[0004] A payment process can be, for example, the payment for a charging process when charging an electric vehicle. Furthermore, other services can be paid for by this payment process as well. For example, goods such as toll stickers, in particular Swiss or Austrian vignettes, can be paid for from the vehicle using this type of payment system. A disadvantage of known payment systems is that the user interface has to determine in advance which payment process is to be carried out. For example, it has to be determined that the charging process in question here is a charging process with a certain number of kilowatt-hours and a certain purchase price, which is to be paid in a certain total amount. Furthermore, the user interface has to determine in advance whether to pay for, for example, a toll sticker with a certain purchase price and valid for a certain validity period, for example one year. In this case, different data, different visualizations as well as different selection options are used for each process. Thus, known payment systems have the disadvantage that the paid service or paid application must be known in advance in order for the user interface to be designed accordingly. Moreover, in order to be able to use the service of the payment process, it must also be implemented at the communication partner, where, for example, long-term specified deadlines of the communication layer (NCD) must also be respected. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] WO2015 / 016929A1 Summary of the Invention [Problem to be solved by the invention]
[0006] SUMMARY OF THE DISCLOSURE The object of the present invention is to provide a payment system for vehicles which overcomes the above mentioned drawbacks. [Means for solving the problem]
[0007] According to the invention, this problem is solved by a payment system having the features of claim 1, and here in particular the features of the characterizing part of claim 1. Advantageous configurations and developments emerge from the claims dependent thereon.
[0008] At the core of the payment system according to the invention, communication takes place in a predefined manner via a static, universal and abstracted interface from the backend via a central communication module to the vehicle's user interface; via a static, universal and abstracted interface between the application and the user interface, any payment service can be mapped; via a dynamic, application-dependent interface between the application, the communication module and the backend, the payment process can be handled and all information required for the payment process and user interaction can be transmitted.
[0009] A payment system is provided in the hardware and software environment within the vehicle for providing paid updates or paid services to controls or applications within the vehicle.
[0010] Thus, according to the present invention, a payment system can be integrated into the vehicle, which allows other control devices and applications in the wired vehicle network to process specific paid services. This can be done using a generic predefined interface without adaptations in the vehicle network communication. In other words, according to the present invention, an agile and dynamic payment system is provided in the vehicle with a generic interface. The introduction of new paid services and / or applications is possible without the need to adapt the payment system and its interface. Thus, according to the present invention, paid services and / or applications are associated with a generically available interface.
[0011] The payment system according to the present invention can achieve efficient configuration of scarce resources in the vehicle network. For example, the separation / encapsulation of service domains greatly accelerates service development and greatly reduces the effort and cost, so that the introduction or modification of new services does not require changes to the vehicle communication (NCD), head unit software / UI software, or payment communication lines. Therefore, the proposed payment system can flexibly introduce new payment services without requiring interface changes for each payment service.
[0012] The static, universal and abstracted interface between the application and the user interface can also be called the vehicle payment communication line. The communication along this communication line is predefined and preferably follows a static, universal and / or abstracted format that is concise and efficient in terms of the communication content. In particular, the communication line is formed to map any payment service. Here, for example, a universally unique identifier (UUID) can be used to characterize a particular payment process. This kind of UUID, also called process UUID, is preferably provided by the payment service and required by the payment process. In one alternative embodiment, if there are multiple payment options for a service, structurally subordinate to the process UUID for the payment process, option UUIDs for the different payment options can be provided. In any case, when the payment process is completed, the process UUID and / or option UUID can be used to signal the success of the payment process to the payment service in order to activate the service. In one further embodiment, advantageously, at least one feedback can be provided to the payment service from the user interface, for example indicating an error message or information about a temporarily unavailable connection in a dead zone, etc. Likewise, an interruption of the process can be indicated via an error message.
[0013] The dynamic application-dependent interface between the application, the communication module and the backend can also be called the service domain communication line. Preferably, this communication line or this communication is entirely within the domain and / or under the control of the service developer. Preferably, via this interface, all information required for the payment process and the user interaction is transmitted to the backend. In particular, by appropriately designing the interface along this line, the transmitted data content can be flexibly adapted, supplemented and / or extended at any time for future services. In other words, this interface is preferably a dynamic interface, so that other services not known so far can also be transmitted without modifying the NCD. In one embodiment, for example, data containers with non-predefined content can be used. In one preferred embodiment, the content can be associated with a specific payment process for a service using the process UUID and / or additionally in the backend using the vehicle identification number (VIN), in particular using the option UUID.
[0014] In one embodiment, the information of the service can be sent to the backend in the service domain communication line or can be adapted to the service and directly provided on the backend side of the service. The information can be, for example, an icon and / or an image. Similarly, font, font size, font color and / or font attributes can be included. Advantageously, the service and the specific payment process, i.e. the result brought about, are also represented. Furthermore, the quantity, unit, cost per unit, total cost, currency name, currency abbreviation, appropriately associated text segments or icons can be shown. If multiple options are available in one embodiment, the option UUID can be used as a reference to show various icons, images, names of the service and the specific payment process, quantity, unit, cost per unit, total cost, currency name, currency abbreviation, appropriately associated text segments and / or icons. If multiple options are present, the data can provide information on whether the options are exclusive, e.g. selectable by radio buttons, or whether multiple options should be selectable at the same time. Furthermore, information on the format and / or display of the content can be included. Optionally, the information can also be terms of use information, which can have an option UUID if confirmation is required. Similarly, information on menu points that require confirmation, for example, information on menu points when "ordering for a fee" may be included.
[0015] If the payment process is processed and all information required for the payment process is transmitted, this can be done in the payment system communication line. It is preferably designed as a generic interface so that in a given fixed structure a large number of different services with different requirements can be covered without having to implement changes in one of the components involved, in particular the user interface. In one embodiment, for such data structures JSON objects, YAML structures and / or web page description languages, in particular HTML, can be used. The mapping of the content to the concrete payment process for the service can be done as already explained for the service domain communication line using the process UUID and in the backend, in particular additionally using the vehicle identification number (VIN) and / or the option UUID. In this case it may be done as already explained for the service domain communication line. In particular the information may be the same.
[0016] Preferably, the data is transmitted to a user interface, where it is interpreted, processed and displayed according to a predefined data structure and in accordance with a predefined manner, whereby the data is provided to the customer.
[0017] According to a very advantageous development of the idea, terms of use can be provided and, if necessary, confirmed by the customer, which confirmation can for example be recorded and communicated to the service via the payment system communication line, the service domain communication line and / or the vehicle payment communication line using a corresponding optional UUID.
[0018] Here, according to one advantageous configuration, paid services can be displayed based on specific characteristics according to a predefined display structure. Furthermore, a user confirmation of the purchase and payment process can be performed, recorded and communicated to the service using the process UUID via the payment system communication line, the service domain communication line and / or the vehicle payment communication line. In one alternative embodiment, this can only be done after the successful completion of the payment process.
[0019] In one further advantageous configuration, the purchase or payment process can be confirmed by the customer, which can be done via radio buttons or displayed as a selection list, depending on the requirements of the service option. This confirmation can then be recorded and communicated to the service using the option UUID via the payment system communication line, the service domain communication line, and / or the vehicle payment communication line. In one further embodiment, this can only be done after the successful completion of the payment process.
[0020] In one advantageous embodiment, after a purchase is completed, a payment process can be initiated via a payment system.
[0021] In one further advantageous embodiment, after initiation of the payment process, the purchased paid service can be activated. In one further embodiment, if after a request for the payment process is signaled in the vehicle payment communication line, no information is provided from the backend within a certain time or if no connection exists, the user interface can react accordingly, for example by outputting information or the instruction "please wait".
[0022] Further advantages of the payment system according to the invention result from the remaining dependent claims and will become apparent on the basis of the exemplary embodiments described in detail below with reference to the drawings. [Brief description of the drawings]
[0023] [Figure 1] 1 shows a schematic diagram of one possible embodiment of a payment system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0024] In FIG. 1, one possible embodiment of the payment system 1 is shown in a schematic diagram. The entire system is shown, consisting of a vehicle 8 and a backend 7. Via the backend 7, for example, an external payment service provider 8 can be connected to trigger the payment process. The vehicle 8 comprises a communication module 6, which is in particular formed as a control device and can provide a connection to the cloud. A head unit 10 is also included in the vehicle 8 and is in particular formed as a central telematics platform, in which the user interface 4 can be displayed and operated. Furthermore, further control devices, applications 3 and / or services that can provide paid services are integrated in the vehicle 8. The electronic payment system 11 thus comprises the payment service provider 9, the backend 7, the communication module 6, the head unit 7 and part of the user interface 4. The vehicle 4 is thus mapped with the actual paid services, which are executed in the control device or application 3 or also partially in the backend 7. Therewith, a payment system communication line can be formed from the backend 7 to the head unit 10 at the interface 5a. Another service domain communication line runs at interface 5b via the communication module 6 to the backend 7. In the vehicle 8 a vehicle payment communication line 2 is formed which runs from the service via the head unit 10 to the user interface 4. Thus the entire domain of the service 12 runs from the paid control device, paid application 3 or paid service via the communication module 6 and also includes part of the backend.
Claims
1. A payment system (1) in a hardware and software environment in a vehicle (8), comprising: The payment system (1) for providing paid updates or paid services to a control device or application in the vehicle (8), communication takes place in a predefined manner through a static, universal and abstracted interface (5a) from a backend (7) via a central communication module (6) to a user interface (4) in said vehicle (8), Any payment service can be mapped via a static, universal and abstracted interface (2) between the application (3) and the user interface (4), said payment system, characterized in that the payment process can be handled and all information required for the payment process and user interaction can be transmitted via a dynamic application dependent interface (5b) between said application (3), said communication module (6) and said backend (7).
2. 2. A payment system (1) according to claim 1, characterized in that data is transmitted to the user interface (4), said data being interpreted, processed and displayed according to a predefined data structure and in accordance with a predefined manner.
3. Payment system (1) according to claim 1 or 2, characterized in that terms and conditions are provided and, if necessary, confirmed by the customer.
4. Payment system (1) according to any one of claims 1 to 3, characterized in that the paid services are displayed based on specific characteristics according to a predefined display structure.
5. 5. A payment system (1) according to any one of claims 1 to 4, characterized in that the purchase or payment process is subject to confirmation by the customer, said confirmation being possible via radio buttons or being displayed as a selection list.
6. A payment system (1) according to any one of claims 1 to 5, characterised in that the payment process is initiated via the payment system after a purchase has been completed.
7. Payment system (1) according to claim 6, characterized in that after the initiation of the payment process, purchased paid services are activated.
Citation Information
Patent Citations
In-Vehicle Application Platform for Vehicle-to-Business Communication
US20120143977A1
Vehicle information system with customizable user interface
US20120179325A1
Wireless payment transactions in a vehicle environment
US20170293910A1
In-vehicle consumer purchase system
US20180232788A1
Electronic system hardware for secure payments for vehicles
US20200065807A1
