WO2023134166A1

WO2023134166A1 - Vehicle-mounted payment methods, terminals, servers, system and medium

Info

Publication number: WO2023134166A1
Application number: PCT/CN2022/112412
Authority: WO
Inventors: 刘刚; 彭程; 孙权; 金可威; 詹成初; 才华
Original assignee: 中国银联股份有限公司
Priority date: 2022-01-17
Filing date: 2022-08-15
Publication date: 2023-07-20
Also published as: CN114220235A; TW202331659A

Abstract

Vehicle-mounted payment methods, belonging to the field of data processing. One method comprises: when vehicle-mounted terminals (11, 800, 1100) of a target vehicle (21) are sensed by acceptance terminals (12, 900, 1200) of a parking lot, receiving a parking charging message sent by the acceptance terminals (12, 900, 1200), the parking charging message comprising a vehicle identifier and payment information (S301); according to the parking charging message and payment card information pre-stored in the vehicle-mounted terminals (11, 800, 1100), generating a payment initiation message, the payment card information comprising personalized data of a payment card (S302); and sending the payment initiation message, so that payment management servers (13, 1000, 1300) acquire the payment initiation message, and interact with a payment resource server (14) by means of the payment initiation message to complete payment (S303).

Description

Vehicle payment method, terminal, server, system and medium

Cross References to Related Applications

This application claims the priority of the Chinese patent application 202210048063.9 entitled "Vehicle Payment Method, Terminal, Server, System and Media" filed on January 17, 2022, the entire content of which is incorporated herein by reference.

technical field

The present application belongs to the field of data processing, and in particular relates to a vehicle payment method, terminal, server, system and medium.

Background technique

With the advancement of science and technology, vehicles have occupied an important position in people's lives.

When the user is not using the vehicle, the vehicle can be parked in the parking lot. Correspondingly, the parking lot will charge corresponding fees for parking the vehicle. For example, the vehicle has been parked in the parking lot for a period of time. When the vehicle is about to leave the parking lot, the user needs to hand over the cash to the parking lot manager or pay the parking fee by scanning the code. The payment requires the user to manually participate in the operation. The payment process is cumbersome and inefficient.

Contents of the invention

Embodiments of the present application provide an in-vehicle payment method, terminal, server, system, and medium, which can improve payment efficiency.

In the first aspect, an embodiment of the present application provides a vehicle payment method, which is applied to a vehicle terminal, and the method includes: when the vehicle terminal of the target vehicle is sensed by the acceptance terminal of the parking lot, receiving a parking charge message sent by the acceptance terminal , the parking charging message includes the vehicle identification and payment information; according to the parking charging message and the payment card information pre-stored in the vehicle terminal, a payment initiation message is generated, and the payment card information includes the personalized data of the payment card; the payment initiation message is sent to make the payment The management server obtains the payment initiation message, and uses the payment initiation message to interact with the payment resource server to complete the payment.

In the second aspect, the embodiment of the present application provides a method for in-vehicle payment, which is applied to the acceptance terminal of the parking lot. The method includes: when the acceptance terminal senses the in-vehicle terminal of the target vehicle, acquiring the vehicle identification and payment information of the target vehicle ; According to the vehicle identification and payment information of the target vehicle, generate a parking charge message, the parking charge message includes the vehicle identification and payment information of the target vehicle; send the parking charge message to the vehicle-mounted terminal, so that the vehicle-mounted terminal is based on the parking charge message and pre-stored in the vehicle-mounted terminal The payment card information generates a payment initiation message. The payment initiation message is obtained by the payment management server to interact with the payment resource server to complete the payment. The payment card information includes the personalization data of the payment card.

In the third aspect, the embodiment of the present application provides a vehicle payment method, which is applied to a payment management server. The method includes: obtaining a payment initiation message, and the payment initiation message is sent by the vehicle terminal according to the parking charging message and the payment card information pre-stored in the vehicle terminal. Generated, the parking charging message includes the vehicle identification and payment information obtained by the acceptance terminal of the parking lot when it senses the vehicle terminal of the target vehicle, and the payment card information includes the personalized data of the payment card; use the payment initiation message to interact with the payment resource server , to complete the payment.

In a fourth aspect, the embodiment of the present application provides a vehicle-mounted terminal, including: a receiving module, configured to receive a parking charge message sent by the acceptance terminal when the vehicle-mounted terminal of the target vehicle is sensed by the acceptance terminal of the parking lot, and the parking charge The message includes vehicle identification and payment information; the generation module is used to generate a payment initiation message according to the parking charge message and the payment card information pre-stored in the vehicle terminal, and the payment card information includes the personalized data of the payment card; the sending module is used to send A payment initiation message, so that the payment management server obtains the payment initiation message, and utilizes the payment initiation message to interact with the payment resource server to complete the payment.

In the fifth aspect, the embodiment of the present application provides an acceptance terminal, including: an acquisition module, configured to acquire the vehicle identification and payment information of the target vehicle when the acceptance terminal senses the vehicle-mounted terminal of the target vehicle; a generation module, configured to According to the vehicle identification and payment information of the target vehicle, a parking charge message is generated, and the parking charge message includes the vehicle identification and payment information of the target vehicle; the sending module is used to send the parking charge message to the vehicle-mounted terminal, so that the vehicle-mounted terminal is based on the parking charge message and the predetermined payment information. The payment card information stored in the vehicle terminal generates a payment initiation message, which is acquired by the payment management server to interact with the payment resource server to complete the payment. The payment card information includes the personalization data of the payment card.

In the sixth aspect, the embodiment of the present application provides a payment management server, including: a receiving module, configured to obtain a payment initiation message, the payment initiation message is generated by the vehicle-mounted terminal according to the parking charging message and the payment card information pre-stored in the vehicle-mounted terminal, and the parking The charging message includes the vehicle identification and payment information acquired by the acceptance terminal of the parking lot when it senses the vehicle-mounted terminal of the target vehicle, and the payment card information includes the personalized data of the payment card; the sending module is used to use the payment initiation message and payment resource The server interacts and completes the payment.

In a seventh aspect, the embodiment of the present application provides a vehicle-mounted terminal, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the vehicle-mounted payment method of the first aspect is implemented.

In an eighth aspect, an embodiment of the present application provides an acceptance terminal, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the in-vehicle payment method of the second aspect is implemented.

In the ninth aspect, the embodiment of the present application provides a payment management server, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the in-vehicle payment method of the third aspect is implemented.

In a tenth aspect, the embodiment of the present application provides an in-vehicle payment system, including the in-vehicle terminal in the seventh aspect, the acceptance terminal in the eighth aspect, and the payment management server in the ninth aspect.

In the eleventh aspect, the embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the in-vehicle payment method of the first aspect and the second aspect are implemented. The in-vehicle payment method or the in-vehicle payment method of the third aspect.

Embodiments of the present application provide a vehicle payment method, terminal, server, system, and medium. When an acceptance terminal in a parking lot senses the vehicle terminal, the acceptance terminal can send a parking charge message to the vehicle terminal. The vehicle-mounted terminal can generate and send a payment initiation message according to the parking charge information and the payment card information pre-stored in the vehicle-mounted terminal. The parking charge message includes vehicle identification and payment information, and the payment card information includes personalization data of the payment card. The payment management server can interact with the payment resource server through the payment initiation message, and use the vehicle identification, payment information, and personalized data of the payment card represented by the payment initiation message to complete the payment. The payment process does not require the user to manually participate in the operation, which simplifies the payment process and improves payment efficiency.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings that need to be used in the embodiments of the present application. Additional figures can be derived from these figures.

FIG. 1 is a schematic diagram of an example of an application scenario of an in-vehicle payment method provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of another example of an application scenario of an in-vehicle payment method provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of another example of an application scenario of an in-vehicle payment method provided by an embodiment of the present application;

Fig. 4 is a flow chart of an embodiment of the in-vehicle payment method provided by the first aspect of the present application;

Fig. 5 is a flow chart of another embodiment of the in-vehicle payment method provided by the first aspect of the present application;

Fig. 6 is a flow chart of an embodiment of the in-vehicle payment method provided by the second aspect of the present application;

Fig. 7 is a flow chart of another embodiment of the in-vehicle payment method provided by the second aspect of the present application;

Fig. 8 is a flow chart of an embodiment of the in-vehicle payment method provided by the third aspect of the present application;

Fig. 9 is a flow chart of an example in-vehicle payment process provided by the embodiment of the present application;

Fig. 10 is a flow chart of another example in-vehicle payment process provided by the embodiment of the present application;

FIG. 11 is a schematic structural diagram of an embodiment of the vehicle-mounted terminal provided in the fourth aspect of the present application;

FIG. 12 is a schematic structural diagram of another embodiment of the vehicle-mounted terminal provided in the fourth aspect of the present application;

Fig. 13 is a schematic structural diagram of an embodiment of an acceptance terminal provided in the fifth aspect of the present application;

Fig. 14 is a schematic structural diagram of another embodiment of the acceptance terminal provided in the fifth aspect of the present application;

Fig. 15 is a schematic structural diagram of an embodiment of the payment management server provided by the sixth aspect of the present application;

Fig. 16 is a schematic structural diagram of another embodiment of the payment management server provided by the sixth aspect of the present application;

FIG. 17 is a schematic structural diagram of an embodiment of the vehicle-mounted terminal provided by the seventh aspect of the present application;

FIG. 18 is a schematic structural diagram of an embodiment of an acceptance terminal provided in the eighth aspect of the present application;

Fig. 19 is a schematic structural diagram of an embodiment of the payment management server provided in the ninth aspect of the present application.

Detailed ways

The characteristics and exemplary embodiments of various aspects of the application will be described in detail below. In order to make the purpose, technical solution and advantages of the application clearer, the application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the present application rather than limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

With the advancement of modern technology, cars have played an important role in people's travel life. When the user is not using the vehicle, the user can park the vehicle in the parking lot. The parking lot manager can record the parking information of the user, and charge the user for the parking fee when the user drives the vehicle to leave the parking lot. Users need to take out cash to pay or use terminals such as mobile phones to scan codes for payment to complete the payment of vehicle parking fees. The payment process requires the user to manually participate in the operation, the payment process is relatively cumbersome, the efficiency is low, and the user experience is relatively poor.

This application provides a vehicle-mounted payment method, terminal, server, system, and medium. The vehicle-mounted terminal and the acceptance terminal of the parking lot can actively interact and initiate payment to the payment management server, so that the payment management server and the payment resource server pass through Interactively complete the payment. In the payment process of the embodiment of the present application, the manual operation of the user can be exempted, thereby simplifying the payment process and improving payment efficiency and user experience.

The in-vehicle payment method provided in this application may involve an in-vehicle terminal, an acceptance terminal, a payment management server and a payment resource server.

FIG. 1 is a schematic diagram of an example of an application scenario of an in-vehicle payment method provided by an embodiment of the present application. As shown in FIG. 1 , the vehicle-mounted terminal 11 can communicate with the acceptance terminal 12 , the acceptance terminal 12 can communicate with the payment management server 13 , and the payment management server 13 can communicate with the payment resource server 14 .

The vehicle-mounted terminal 11 is installed in a vehicle 21 . The vehicle-mounted terminal 11 can be provided with a short-distance wireless communication module, so that the vehicle-mounted terminal 11 can perform short-distance wireless communication with other devices, for example, the vehicle-mounted terminal 11 can perform short-distance wireless communication with the acceptance terminal 12 . A security area is set in the vehicle terminal 11, and the security area may include one or more of a secure element (Secure Element, SE), an embedded secure element (eSE), and a trusted execution environment (Trusted Execution Environment, TEE). Not limited. The information interaction between the vehicle terminal and the security area can optimize multiple Application Protocol Data Unit (Application Protocol Data Unit, APDU) commands into one command.

Acceptance terminal 12 is the payment acceptance equipment of the parking lot, specifically may include a point of sales terminal (point of sales terminal, POS) or other equipment, and is not limited herein. The reception terminal 12 may be provided with a short-distance wireless communication module, so that the reception terminal 12 can perform short-distance wireless communication with other devices, for example, the reception terminal 12 can perform short-distance wireless communication with the vehicle-mounted terminal 11 . The acceptance terminal 12 can also perform wired communication and/or wireless communication with other devices, for example, the acceptance terminal 12 can perform wired communication with the payment management server 13, or the acceptance terminal 12 and the payment management server 13 can be transferred through other equipment , that is, the communication interaction between the acceptance terminal 12 and the payment management server 13 may be an interaction combining wired communication and wireless communication. In some cases, the reception terminal 12 can control the opening and closing of the turnstiles 22 of the parking lot. The gate 22 can also be controlled by other devices, which is not limited here. When the payment of the vehicle 21 is completed, the gate 22 can be opened to allow the vehicle 21 to pass through.

The payment management server 13 can be used as a component of the Internet of Things platform, and the Internet of Things platform can include at least one payment management server 13, which is not limited here. The payment management server 13 can interact with the payment resource server 14 to complete the payment.

The payment resource server 14 may be a server of a payment card issuer. For example, if the payment card is a bank card, the payment resource server 14 may be a server of a corresponding bank. The payment resource server 14 can charge the payment card to complete the payment.

FIG. 2 is a schematic diagram of another example of an application scenario of the in-vehicle payment method provided by the embodiment of the present application. The difference between FIG. 2 and FIG. 1 is that the vehicle-mounted terminal 11 shown in FIG. 2 can also communicate with the payment management server 13 wirelessly. For example, the vehicle-mounted terminal 11 can be provided with an entity user identification (Subscriber Identification Module, SIM) card or a virtual SIM card, so that the vehicle-mounted terminal 11 can perform data network communication with the payment management server 13, such as the vehicle-mounted terminal 11 can use the SIM card to pass 3G, Data networks such as 4G and 5G communicate with the payment management server 13 . For the specific content of the acceptance terminal 12, the payment management server 13 and the payment resource server 14, please refer to the relevant description above, which will not be repeated here.

Fig. 3 is a schematic diagram of another example of an application scenario of the in-vehicle payment method provided by the embodiment of the present application. The difference between FIG. 3 and FIG. 2 is that the user terminal 15 is also shown in FIG. 3 . As shown in FIG. 3 , the user terminal 15 can perform short-distance wireless communication or wired communication with the vehicle terminal 11 , which is not limited here. The user terminal 15 can perform user authorization on the vehicle terminal 11, so that the vehicle terminal 11 can interact with the authorized server. The user terminal 15 can also directly transmit the data required by the vehicle terminal 11 to the vehicle terminal 11 . The user terminal 15 may include a mobile phone, a tablet computer, a smart wearable device, etc., and is not limited here. For the specific content of the vehicle terminal 11 , the acceptance terminal 12 , the payment management server 13 and the payment resource server 14 , please refer to the relevant description above, and will not repeat them here.

The in-vehicle payment method, in-vehicle terminal, acceptance terminal, payment management server, in-vehicle payment system, and computer-readable storage medium will be described in sequence below.

The first aspect of the present application provides an in-vehicle payment method, which can be applied to an in-vehicle terminal, that is, the in-vehicle payment method can be executed by an in-vehicle terminal. For details of the in-vehicle terminal, please refer to the relevant description above, and details will not be repeated here. Fig. 4 is a flowchart of an embodiment of the in-vehicle payment method provided in the first aspect of the present application. As shown in Fig. 4, the vehicle payment method may include steps S301 to S303.

In step S301, when the vehicle-mounted terminal of the target vehicle is sensed by the acceptance terminal of the parking lot, the parking charging message sent by the acceptance terminal is received.

The target vehicle is any vehicle to which the in-vehicle payment method is applied in the embodiment of this application. In order to distinguish this vehicle from other vehicles, this vehicle is called a target vehicle. The vehicle-mounted terminal and the receiving terminal can perform wireless communication, and when the distance between the vehicle-mounted terminal and the receiving terminal is within the sensing distance range, the receiving terminal can sense the vehicle-mounted terminal. When the acceptance terminal senses the vehicle terminal, the acceptance terminal can communicate and interact with the vehicle terminal. In some examples, the vehicle-mounted terminal may receive the parking charging message sent by the accepting terminal through a short-distance wireless communication technology. The short-distance wireless communication technology may include Bluetooth technology, 900M communication technology, Wi-Fi technology, ZigBee technology, etc., which are not limited here. Correspondingly, a Bluetooth communication module, a 900M communication module, a Wi-Fi communication module, a ZigBee communication module, etc. may be set in the vehicle-mounted terminal and the reception terminal, which are not limited here.

In some examples, the entrance and exit of the parking lot are located at different locations, and the acceptance terminal can be set at the exit. When the target vehicle enters the parking lot through the entrance, the recording device at the entrance can record the vehicle identification and entry time of the target vehicle. The recording device at the entrance can directly or indirectly transmit the vehicle identification and entry time of the target vehicle to the acceptance terminal. The vehicle-mounted terminal of the target vehicle is sensed by the receiving terminal, indicating that the target vehicle needs to leave the parking lot. When the target vehicle needs to leave the parking lot, the acceptance terminal can record the vehicle identification and departure time of the target vehicle, and generate a parking charging message according to the vehicle identification, entry time, and departure time of the target vehicle. The acceptance terminal can send out parking charge information, and correspondingly, the vehicle-mounted terminal can receive the parking charge information.

In some other examples, the entrance and exit of the parking lot are located at the same position, that is, the parking lot is provided with an entrance and exit, and the entrance and exit can be used as both the entrance and the exit. Within a period of time, the target vehicle is sensed by the acceptance terminal for the first time, indicating that the target vehicle needs to enter the parking lot; during this period of time, the target vehicle is sensed by the acceptance terminal for the second time, indicating that the target vehicle needs to leave the parking lot. When the target vehicle needs to enter the parking lot, the acceptance terminal can record the vehicle identification and entry time of the target vehicle. When the target vehicle needs to leave the parking lot, the acceptance terminal can record the vehicle identification and departure time of the target vehicle, and generate a parking charging message according to the vehicle identification, entry time, and departure time of the target vehicle. The acceptance terminal can send out parking charge information, and correspondingly, the vehicle-mounted terminal can receive the parking charge information.

The parking charge message includes vehicle identification and payment information. Vehicle identification is used to identify the vehicle. The vehicle identification is unique to the vehicle. In some examples, the vehicle identification may include license plate information and/or vehicle identification number (Vehicle Identification Number, VIN), etc., but is not limited thereto. The acceptance terminal can identify the vehicle through the vehicle identification. The payment information is information used to characterize the content of this payment. In some examples, the payment information may include one or more of the following: charging party information, payment time, payment fee, and parking duration. The charging party information is used to characterize the charging party. The payment time is the time when the payment occurs. The payment fee is the fee that needs to be paid. The parking time is the time when the target vehicle is parked in the parking lot. In some cases, the payment fee has a certain correspondence with the parking duration, and the longer the parking duration, the higher the payment fee.

The receiving terminal may send parking charge information to the vehicle terminal in a directional manner, or broadcast the parking charge information, which is not limited here.

In step S302, a payment initiation message is generated according to the parking charge message and the payment card information pre-stored in the vehicle-mounted terminal.

Payment card information includes payment card personalization data. The personalized data of the payment card is used to realize the transaction and verification of the payment card during the payment process. Personalization data for a payment card may include personal information about the cardholder holding the payment card and card information for the payment card. For example, personal information may include the cardholder's name, cardholder's ID number, etc., which are not limited here; card information may include card number, card payment identification Token, etc., which are not limited here. The payment card information is stored in the vehicle-mounted terminal, that is, the payment card is bound to the vehicle-mounted terminal, and the vehicle-mounted terminal can use the payment card to initiate payment. In some examples, the payment card information can be stored in the safe area of the vehicle terminal to avoid data leakage and thus ensure the safety of payment.

The payment initiation message may include vehicle identification, payment information, payment card personalization data and other information, which is not limited here. The payment initiation message can be specifically implemented as a message such as an authorization request cryptogram (Authenticate Request Cryptogram, ARQC), which is not limited here.

Before step S301, the vehicle-mounted terminal can acquire payment card information from the outside and store it.

In some examples, the vehicle terminal can obtain and store payment card information from a payment management server or a payment resource server. Specifically, the vehicle-mounted terminal establishes a communication connection with the user terminal, obtains payment card information authorization information from the user terminal, obtains payment card information from the payment management server or payment resource server according to the payment card information authorization information, and stores the payment card information.

The vehicle terminal and the user terminal can establish a wired communication or wireless communication connection. For example, the vehicle-mounted terminal establishes a Bluetooth communication connection with the user. The authorization information is used to indicate that the vehicle-mounted terminal has the authority to store payment card information. The vehicle-mounted terminal can use the authorization information to request payment card information from the payment management server or payment resource server, and store the payment card information obtained from the payment management server or payment resource server. The vehicle-mounted terminal can pre-agreed with the payment management server or payment resource server on the encryption key, and write the encryption key into the safe area of the vehicle-mounted terminal. The encrypted payment card information can be sent from the payment management server or payment resource through a secure encryption channel such as a GP security channel. The server transmits the information to the safe area of the vehicle terminal and stores it in the safe area of the vehicle terminal. The encryption key can be used to decrypt the encrypted payment card information in the safe area to obtain the payment card information.

In some other examples, the vehicle terminal can obtain and store the payment card information from the user terminal. Specifically, the vehicle-mounted terminal establishes a communication connection with the user terminal, acquires payment card information from the user terminal, and stores the payment card information.

The vehicle terminal and the user terminal can establish a wired communication or wireless communication connection. For example, the vehicle-mounted terminal establishes a Bluetooth communication connection with the user. The user terminal stores payment card information, that is, the user terminal is bound with the payment card. The vehicle terminal can store the payment card information transmitted from the user terminal. The vehicle-mounted terminal can pre-agreed with the user terminal on the encryption key, write the encryption key into the security area of the vehicle-mounted terminal, and the encrypted payment card information can be transmitted from the user terminal to the security area of the vehicle-mounted terminal through a secure encryption channel such as a GP security channel, and Stored in the safe area of the vehicle terminal, the encrypted payment card information can be decrypted by using the encryption key in the safe area to obtain the payment card information.

In step S303, a payment initiation message is sent, so that the payment management server acquires the payment initiation message, and uses the payment initiation message to interact with the payment resource server to complete the payment.

In some examples, the vehicle terminal can directly send a payment initiation message to the payment management server. For example, a SIM card can be set in the vehicle terminal, and a payment initiation message can be sent to the payment management server through the data network. After obtaining the payment initiation message, the payment management server can use the information in the payment initiation message to interact with the payment resource server, so that the payment resource server can deduct this parking fee.

In other examples, the vehicle terminal may send a payment initiation message to the acceptance terminal, and the acceptance terminal then sends the payment initiation message to the payment management server. After obtaining the payment initiation message, the payment management server can use the information in the payment initiation message to interact with the payment resource server, so that the payment resource server can deduct this parking fee.

In some examples, payment first and release later may be implemented. The vehicle-mounted terminal can send a payment initiation message before the exit gate of the parking lot is opened, that is, the vehicle-mounted terminal makes payment before the exit gate is opened. When the payment is completed, the payment resource server can send a payment success message to the payment management server, and the payment management server can send the payment success message to the acceptance terminal, and the acceptance terminal can control the opening of the exit gate of the parking lot in response to the payment success message , allowing the target vehicle to leave.

In other examples, release first and pay later may be implemented. The vehicle-mounted terminal can send a payment initiation message after the exit gate of the parking lot is opened, that is, the vehicle-mounted terminal can make payment after the exit gate is opened. The acceptance terminal can obtain the historical payment orders of the vehicle terminal. If there is no unpaid order in the historical payment orders, it can control the opening of the exit gate of the parking lot to allow the target vehicle to leave.

In the embodiment of the present application, when the acceptance terminal of the parking lot senses the vehicle-mounted terminal, the vehicle-mounted terminal can receive the parking charging message sent by the acceptance terminal. The vehicle-mounted terminal can generate and send a payment initiation message according to the parking charge information and the payment card information pre-stored in the vehicle-mounted terminal. The parking charge message includes vehicle identification and payment information, and the payment card information includes personalization data of the payment card. The payment management server can interact with the payment resource server through the payment initiation message, and use the vehicle identification, payment information, and personalized data of the payment card represented by the payment initiation message to complete the payment. The payment process does not require the user to manually participate in the operation, which simplifies the payment process and improves payment efficiency. Moreover, the payment process does not require the user to manually participate in the operation, and the user has no perception, which also improves the user's payment experience.

The accepting terminal can sense more than one vehicle-mounted terminal, and when the accepting terminal senses one or more than two vehicle-mounted terminals, the accepting terminal can broadcast parking fee information in a broadcasting manner. Each vehicle-mounted terminal can selectively obtain information matching itself to generate a payment initiation message. Fig. 5 is a flow chart of another embodiment of the in-vehicle payment method provided in the first aspect of the present application. The difference between FIG. 5 and FIG. 4 lies in that step S302 in FIG. 4 can be subdivided into step S3021 and step S3022 in FIG. 5 .

In step S3021, the first vehicle identification and the first payment information are obtained from the parking charging message broadcast by the receiving terminal.

The receiving terminal can sense each vehicle-mounted terminal located within the sensing distance range of the receiving terminal. The acceptance terminal can directly sense the vehicle-mounted terminal, or sense the vehicle, and then determine the vehicle-mounted terminal of the vehicle. The parking charging message may include vehicle identification and payment information corresponding to each vehicle-mounted terminal that can be sensed by the receiving terminal.

The vehicle-mounted terminal may filter the vehicle identification consistent with the target vehicle identification stored by itself, that is, the first vehicle identification, in the parking charging message. The first vehicle identifier is a vehicle identifier consistent with the target vehicle identifier stored in the vehicle-mounted terminal. The target vehicle identification includes a vehicle identification of the target vehicle. After the vehicle-mounted terminal obtains the first vehicle identification through screening, it can obtain the payment information corresponding to the first vehicle identification, that is, the first payment information. The first payment information is payment information corresponding to the first vehicle identifier.

For example, the acceptance terminal has sensed 3 vehicle-mounted terminals, that is, the acceptance terminal has sensed 3 vehicle-mounted terminals. The vehicle identifiers corresponding to the three vehicle-mounted terminals are ID1, ID2 and ID3 respectively, and the payment information corresponding to the three vehicle-mounted terminals A1, A2 and A3 are payment information B1, payment information B2 and payment information B3. Correspondingly, the parking charging message broadcast by the accepting terminal includes "ID1: payment information B1; ID2: payment information B2; ID3: payment information B3". For the vehicle-mounted terminal A1, the first vehicle identification is ID1, and the first payment information is the payment information B1. When the vehicle-mounted terminal A1 receives the parking fee message broadcast by the accepting terminal, it can filter the parking fee message to obtain " ID1: payment information B1". Similarly, for the vehicle-mounted terminal A2, the first vehicle identification is ID2, and the first payment information is the payment information B2. When the vehicle-mounted terminal A2 receives the parking charge message broadcast by the accepting terminal, it can obtain the parking charge message from the parking charge message. Filter to get "ID2: payment information B2". For the vehicle-mounted terminal A3, the first vehicle identification is ID3, and the first payment information is the payment information B3. When the vehicle-mounted terminal A3 receives the parking charge message broadcast by the accepting terminal, it can filter the parking charge message to obtain " ID3: payment information B3".

In step S3022, a payment initiation message is generated according to the first vehicle identification, the first payment information, and the personalization data of the payment card pre-stored in the vehicle-mounted terminal.

When the vehicle-mounted terminal screens out the matching first vehicle identification and first payment information, the vehicle-mounted terminal can generate the vehicle-mounted terminal according to the first vehicle identification, the first payment information and the personalized data of the payment card pre-stored in the vehicle-mounted terminal. The terminal's payment initiation message. In some examples, the payment initiation message may include the first vehicle identifier, the first payment information, and personalization data of the payment card, which is not limited herein.

The accepting terminal can sense more than two vehicle-mounted terminals, and correspondingly, the parking fee message broadcast by the accepting terminal can include vehicle identifications and payment information corresponding to more than two vehicle-mounted terminals. The vehicle-mounted terminal can filter and obtain the first vehicle identification and the first payment information matching itself, so as to generate a payment initiation message. The embodiment of the present application can realize the payment of parking fees for multiple vehicles, and the process is simple, and the payment efficiency can be further improved in the scenario where multiple vehicles leave the parking lot.

In order to improve the security of payment, the information in the messages exchanged between the vehicle-mounted terminal and the acceptance terminal in the above embodiment may be encrypted information. Before the interaction between the vehicle-mounted terminal and the receiving terminal, the security verification of the key can be performed first, so as to determine the security of the transmission between the vehicle-mounted terminal and the receiving terminal. Before receiving the parking charging message sent by the receiving terminal, the vehicle-mounted terminal can perform key security verification with the receiving terminal. If the key security verification passes, the vehicle-mounted terminal receives the parking charging message sent by the receiving terminal. That is to say, the accepting terminal can only access the vehicle-mounted terminal when the security verification of the key is passed.

Specifically, the vehicle-mounted terminal can generate a random number, and send the random number to the receiving terminal. The vehicle-mounted terminal receives the certificate authority certificate, ie, the CA certificate, sent by the accepting terminal. The vehicle-mounted terminal uses the pre-written CA public key to recover the public key from the CA certificate. The accepting terminal uses the private key of the CA certificate to encrypt the random number to obtain the ciphertext, and sends the ciphertext to the vehicle terminal. The vehicle-mounted terminal uses the recovered public key to decrypt the ciphertext to obtain the plaintext. The vehicle-mounted terminal compares the plaintext and the random number, and if the plaintext is consistent with the random number, the key security verification is passed.

The second aspect of the present application provides an in-vehicle payment method that can be applied to an acceptance terminal of a parking lot, that is, the in-vehicle payment method can be executed by the acceptance terminal. For the specific content of the acceptance terminal, please refer to the relevant description above, which will not be repeated here. Fig. 6 is a flow chart of an embodiment of the in-vehicle payment method provided by the second aspect of the present application. As shown in Fig. 6, the in-vehicle payment method may include steps S401 to S403.

In step S401, when the acceptance terminal senses the vehicle-mounted terminal of the target vehicle, acquire the vehicle identification and payment information of the target vehicle.

The receiving terminal senses the vehicle-mounted terminal of the target vehicle, and can obtain the vehicle identification of the target vehicle from the vehicle-mounted terminal through wireless communication, and can also determine and obtain the vehicle identification of the identified target vehicle through the identification of the target vehicle. limited. When the vehicle identification is obtained, the accepting terminal can determine the payment information corresponding to the vehicle identification, that is, the payment information of the target vehicle according to the vehicle identification.

In some examples, the vehicle identification may include but not limited to the license plate information and/or the vehicle identification code. For specific content, please refer to the relevant description in the above-mentioned embodiments, which will not be repeated here.

In the case that the vehicle identification includes license plate information, the acceptance terminal can obtain the vehicle image of the target vehicle, and identify the license plate information from the vehicle image. According to the license plate information, the payment information corresponding to the license plate information is generated as the payment information of the target vehicle.

The parking lot can be equipped with shooting devices such as cameras for taking pictures or taking pictures, and the shooting devices can take images of vehicles including license plates. The acceptance terminal can acquire the vehicle image from the shooting device, and recognize the vehicle image to obtain the license plate information, and then generate corresponding payment information based on the license plate information. For example, when the target vehicle enters the parking lot, the shooting device installed at the entrance of the parking lot can capture the vehicle image of the target vehicle, identify the vehicle image, obtain the license plate information and transmit it to the acceptance terminal; when the target vehicle is about to leave the parking lot , the shooting device installed at the exit of the parking lot can capture the vehicle image of the target vehicle, recognize the vehicle image, obtain the license plate information and transmit it to the acceptance terminal, the acceptance terminal can determine the parking duration of the target vehicle according to the license plate information, and according to the parking duration And the preset charging rules, etc., get the payment fee, and generate the payment information of the target vehicle according to the parking time, payment fee and other information.

In some examples, the payment information may include, but not limited to, one or more of the following: charging party information, payment time, payment fee, and parking duration. For details, please refer to the relevant descriptions in the above-mentioned embodiments, and will not repeat them here .

In step S402, a parking charging message is generated according to the vehicle identification and payment information of the target vehicle.

The parking charging message includes the vehicle identification and payment information of the target vehicle, and the format of the parking charging message and the form of the vehicle identification and payment information in the parking charging message are not limited here.

In the case that the receiving terminal senses the vehicle-mounted terminals in more than two vehicles, the parking charge message generated by the receiving terminal may include the vehicle identifications and payment information of the two or more vehicles.

In step S403, a parking charge message is sent to the vehicle-mounted terminal, so that the vehicle-mounted terminal generates a payment initiation message according to the parking charge message and the payment card information pre-stored in the vehicle-mounted terminal.

The payment initiation message is acquired by the payment management server and used to interact with the payment resource server to complete the payment. The payment initiation message may include vehicle identification, payment information, and payment card information. Payment card information includes payment card personalization data.

In some examples, the vehicle-mounted terminal may directly send the payment initiation message to the payment management server, that is, the vehicle-mounted terminal directly initiates payment to the payment management server without going through the acceptance terminal. The receiving terminal does not need to process. Alternatively, after obtaining the vehicle identification and payment information of the target vehicle, the accepting terminal can send the vehicle identification and payment information of the target vehicle to the payment management server, so that the payment management server can compare the payment initiation message received from the vehicle terminal with the payment information obtained from the acceptance terminal. Match the vehicle identification and payment information of the target vehicle, and determine whether to make payment according to the matching result. Specifically, if the vehicle identification and payment information in the payment initiation message received from the vehicle-mounted terminal are consistent with the vehicle identification and payment information of the target vehicle obtained from the accepting terminal, the matching result is a successful match, and payment is determined to be made; if the vehicle-mounted terminal If the vehicle identification and payment information in the received payment initiation message are inconsistent with the vehicle identification and payment information of the target vehicle acquired from the acceptance terminal, the matching result will be matching failure, and the payment will be stopped.

The accepting terminal further verifies the security of the payment by matching the payment initiation message received from the vehicle-mounted terminal with the vehicle identification and payment information of the target vehicle acquired from the accepting terminal. If the matching result is successful, it means the payment is safe, and the payment can be continued; if the matching result is failed, it indicates that there is a risk in the payment, and the payment can be stopped to avoid the payment risk.

In some other examples, the vehicle-mounted terminal may send a payment initiation message to the accepting terminal. Correspondingly, the acceptance terminal receives the payment initiation message, and the acceptance terminal sends the payment initiation message to the payment management server. That is, the acceptance terminal initiates payment to the payment management server.

In some examples, payment first and release later may be implemented. The payment initiation message can be sent by the vehicle terminal before the exit gate of the parking lot is opened. That is, after the payment is completed, the payment management server may send a payment success message to the accepting terminal. Correspondingly, the acceptance terminal receives the payment success message sent by the payment management server. The payment success message is used to indicate that the payment is successful. In response to the payment success message, the accepting terminal can control the exit gate of the parking lot to open, allowing the target vehicle to leave.

In other examples, release first and pay later may be implemented. The payment initiation message can be sent by the vehicle-mounted terminal after the exit gate of the parking lot is opened. The acceptance terminal can obtain the historical payment orders of the target vehicle according to the vehicle identification of the target vehicle. The historical payment orders of the target vehicle include payment orders of the target vehicle in at least a period of time before. There are no unpaid orders in the historical payment orders of the target vehicle, which means that the payment of the target vehicle has been completed and the credit is good. There are unpaid orders in the historical payment orders of the target vehicle, which means that the target vehicle has unfinished payment and has poor credit. When there is no unpaid order in the historical payment order of the target vehicle, the exit gate of the parking lot is controlled to open, allowing the target vehicle to leave, and the payment is initiated after the exit gate is opened, that is, the target vehicle can make payment after passing . If there is an unpaid order in the historical payment order of the target vehicle, the exit gate of the parking lot is controlled to close, and the target vehicle is not allowed to leave. After the target vehicle completes the payment, the exit gate of the parking lot is controlled to open, allowing the target vehicle to leave. The vehicle leaves.

In the embodiment of the present application, when the acceptance terminal of the parking lot senses the vehicle terminal, the acceptance terminal may send a parking charging message to the vehicle terminal. The vehicle-mounted terminal can generate and send a payment initiation message according to the received parking charge information and the payment card information pre-stored in the vehicle-mounted terminal. The parking charge message includes vehicle identification and payment information, and the payment card information includes personalization data of the payment card. The payment management server can interact with the payment resource server through the payment initiation message, and use the vehicle identification, payment information, and personalized data of the payment card represented by the payment initiation message to complete the payment. The payment process does not require the user to manually participate in the operation, which simplifies the payment process and improves payment efficiency. Moreover, the payment process does not require the user to manually participate in the operation, and the user has no perception, which also improves the user's payment experience.

In some embodiments, the acceptance terminal may broadcast the parking charge message in a broadcast manner. Each vehicle-mounted terminal can selectively obtain information matching itself to generate a payment initiation message. Fig. 7 is a flow chart of another embodiment of the in-vehicle payment method provided by the second aspect of the present application. The difference between FIG. 7 and FIG. 6 is that step S403 in FIG. 6 can be specifically refined into step S4031 in FIG. 7 .

In step S4031, the parking charging message is broadcast to the vehicle-mounted terminal, so that the vehicle-mounted terminal generates a payment initiation message according to the parking charging message and the payment card information pre-stored in the vehicle-mounted terminal.

The parking charging message includes a first vehicle identification and first payment information. The first vehicle identifier is a vehicle identifier consistent with the target vehicle identifier stored in the vehicle-mounted terminal. The target vehicle identification includes a vehicle identification of the target vehicle. The first payment information is payment information corresponding to the first vehicle identifier. The payment initiation message is generated by the vehicle-mounted terminal according to the first vehicle identification, the first payment information, and the payment card information pre-stored in the vehicle-mounted terminal. In the case that the accepting terminal detects other vehicle-mounted terminals other than the vehicle-mounted terminal of the target vehicle, the parking charge message may also include vehicle identifications and payment information corresponding to other vehicle-mounted terminals. The target vehicle can identify the vehicle identification and payment information matching itself in the parking charging message, that is, the first vehicle identification and the first payment information. The embodiment of the present application can realize the payment of parking fees for multiple vehicles, and the process is simple, and the payment efficiency can be further improved in the scenario where multiple vehicles leave the parking lot.

In order to improve the security of payment, before the interaction between the vehicle-mounted terminal and the acceptance terminal, the security verification of the key can be performed first, so as to determine the security of the transmission between the vehicle-mounted terminal and the acceptance terminal. Before the accepting terminal acquires the vehicle identification and payment information of the target vehicle, the accepting terminal can perform key security verification with the vehicle terminal. When the security verification of the key is passed, the accepting terminal obtains the vehicle identification and payment information of the target vehicle. For specific details, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

For the specific content of the embodiment of the in-vehicle payment method in the second aspect of the present application, please refer to the relevant description in the embodiment of the in-vehicle payment method in the first aspect of the present application, and details will not be repeated here.

The third aspect of the present application provides an in-vehicle payment method that can be applied to a payment management server, that is, the in-vehicle payment method can be executed by the payment management server. For the specific content of the payment management server, please refer to the relevant description above, which will not be repeated here. Fig. 8 is a flow chart of an embodiment of the in-vehicle payment method provided by the third aspect of the present application. As shown in Fig. 8, the vehicle payment method may include step S501 and step S502.

In step S501, a payment initiation message is acquired.

The payment initiation message is generated by the vehicle-mounted terminal according to the parking charging message and the payment card information pre-stored in the vehicle-mounted terminal. The parking charging message includes the vehicle identification and payment information acquired by the acceptance terminal of the parking lot when it senses the vehicle-mounted terminal of the target vehicle. Payment card information includes payment card personalization data.

Specifically, the vehicle identification may include but not limited to license plate information and/or vehicle identification code.

Specifically, the payment information includes one or more of the following: charging party information, payment time, payment fee, and parking duration.

In some examples, the payment management server may receive a payment initiation message from the vehicle terminal. That is, the vehicle terminal directly initiates payment to the payment management server.

In some other examples, the payment management server may receive the payment initiation message from the acceptance terminal. The payment initiation message is sent by the vehicle terminal to the acceptance terminal. That is, the acceptance terminal initiates payment to the payment management server.

In step S502, the payment initiation message is used to interact with the payment resource server to complete the payment.

In some examples, payment first and release later may be implemented. The payment management server may obtain the payment initiation message before the exit gate of the parking lot is opened.

Specifically, the payment management server may send a payment initiation message to the payment resource server. The payment resource server deducts the payment from the payment card according to the information in the payment initiation message. After deduction, the payment resource server may send a payment success message to the payment management server. The payment management server can send a payment success message to the acceptance terminal, so that the acceptance terminal releases the vehicle.

In other examples, release first and pay later may be implemented. The payment management server may obtain the payment initiation message after the exit gate of the parking lot is opened.

When the payment management server receives the payment initiation message from the vehicle-mounted terminal, that is, the vehicle-mounted terminal directly initiates payment to the payment management server, after the acceptance terminal obtains the vehicle identification and payment information of the target vehicle, the payment management server can receive the target payment information from the acceptance terminal. Vehicle identification and payment information for the vehicle. The payment management server matches the payment initiation message received from the vehicle-mounted terminal with the vehicle identification and payment information of the target vehicle obtained from the accepting terminal. If the matching result is matching success, the payment initiation message is used to interact with the payment resource server to complete the payment; if the matching result is matching failure, the payment is stopped.

In the embodiment of the present application, when the acceptance terminal of the parking lot senses the vehicle terminal, the acceptance terminal may send a parking charging message to the vehicle terminal. The vehicle-mounted terminal can generate and send a payment initiation message according to the parking charge information and the payment card information pre-stored in the vehicle-mounted terminal. The parking charge message includes vehicle identification and payment information, and the payment card information includes personalization data of the payment card. The payment management server can interact with the payment resource server through the payment initiation message, and use the vehicle identification, payment information, and personalized data of the payment card represented by the payment initiation message to complete the payment. The payment process does not require the user to manually participate in the operation, which simplifies the payment process and improves payment efficiency. Moreover, the payment process does not require the user to manually participate in the operation, and the user has no perception, which also improves the user's payment experience.

For the specific content of the embodiment of the in-vehicle payment method of the third aspect of the present application, please refer to the relevant descriptions in the embodiment of the in-vehicle payment method of the first aspect of the application and the embodiment of the in-vehicle payment method of the second aspect of the present application, and will not be repeated here.

For ease of understanding, two examples are used below to specifically illustrate the vehicle payment process between the user terminal, the vehicle terminal, the acceptance terminal, the payment management server and the payment resource server.

Fig. 9 is a flow chart of an example in-vehicle payment process provided by the embodiment of the present application. As shown in FIG. 9 , the in-vehicle payment process may include steps S601 to S612.

In step S601, the vehicle-mounted terminal establishes a communication connection with the user terminal, and downloads payment card information to the vehicle-mounted terminal.

In step S602, when the vehicle enters or exits the parking lot, the receiving terminal senses the vehicle-mounted terminal, obtains the vehicle identification and payment information, and generates a parking charge message according to the vehicle identification and payment information.

In step S603, the vehicle-mounted terminal receives the parking charge message sent by the receiving terminal through 900M communication technology.

In step S604, the vehicle-mounted terminal screens the parking charge message to obtain the vehicle identification and payment information matching itself.

In step S605, the vehicle-mounted terminal generates a payment initiation message according to the vehicle identification and payment information matched with itself, as well as the payment card information.

In step S606, the vehicle-mounted terminal sends a payment initiation message to the accepting terminal.

In step S607, the accepting terminal sends a payment initiation message to the payment management server.

In step S608, the payment management server sends a payment initiation message to the payment resource server.

In step S609, the payment resource server debits the payment card according to the payment initiation message.

In step S610, the payment resource server sends a payment success message to the payment management server.

In step S611, the payment management server sends a payment success message to the accepting terminal.

In step S612, in response to the payment success message, the accepting terminal controls the opening of the gate and releases the vehicle.

Fig. 10 is a flow chart of another example in-vehicle payment process provided by the embodiment of the present application. As shown in FIG. 10 , the in-vehicle payment process may include steps S701 to S712.

In step S701, the vehicle-mounted terminal establishes a communication connection with the user terminal, and downloads payment card information to the vehicle-mounted terminal.

In step S702, when the vehicle enters or leaves the parking lot, the reception terminal obtains the vehicle image captured by the camera, recognizes the license plate information from the vehicle image, obtains the payment information according to the license plate information, and generates a parking charge message according to the vehicle identification and payment information.

In step S703, the receiving terminal broadcasts a parking charging message through Bluetooth.

In step S704, the acceptance terminal sends the license plate information and payment information to the payment management server.

In step S705, the vehicle-mounted terminal screens the parking charge message to obtain license plate information and payment information that match itself.

In step S706, the vehicle-mounted terminal generates a payment initiation message according to the vehicle identification and payment information matched with itself, as well as the payment card information.

In step S707, the vehicle-mounted terminal sends a payment initiation message to the payment management server.

In step S708, the payment management server sends a payment initiation message to the payment resource server.

In step S709, the payment resource server debits the payment card according to the payment initiation message.

In step S710, the payment resource server sends a payment success message to the payment management server.

In step S711, the payment management server sends a payment success message to the accepting terminal.

In step S712, in response to the payment success message, the accepting terminal controls the opening of the gate and releases the vehicle.

A fourth aspect of the present application provides a vehicle-mounted terminal. FIG. 11 is a schematic structural diagram of an embodiment of the vehicle-mounted terminal provided in the fourth aspect of the present application. As shown in FIG. 11 , the vehicle-mounted terminal 800 may include a receiving module 801 , a generating module 802 and a sending module 803 .

The receiving module 801 can be configured to receive the parking charge message sent by the receiving terminal when the vehicle-mounted terminal of the target vehicle is sensed by the receiving terminal of the parking lot.

The parking charge message includes vehicle identification and payment information.

In some examples, the vehicle identification includes license plate information and/or a vehicle identification number.

In some examples, the payment information includes one or more of the following: charging party information, payment time, payment fee, and parking duration.

The generation module 802 may be configured to generate a payment initiation message according to the parking charge message and the payment card information pre-stored in the vehicle terminal.

Payment card information includes payment card personalization data.

The sending module 803 may be configured to send a payment initiation message, so that the payment management server obtains the payment initiation message, and uses the payment initiation message to interact with the payment resource server to complete the payment.

In some examples, the sending module 803 may be used to send the payment initiation message before the exit gate of the parking lot is opened.

In some other examples, the sending module 803 may be used to send the payment initiation message after the exit gate of the parking lot is opened.

In some examples, the generating module 802 may be configured to: obtain the first vehicle identification and the first payment information from the parking charge message broadcast by the receiving terminal, where the first vehicle identification is a vehicle identification consistent with the target vehicle identification stored in the vehicle terminal, The target vehicle identification includes the vehicle identification of the target vehicle, and the first payment information is the payment information corresponding to the first vehicle identification; according to the personalization data of the first vehicle identification, the first payment information and the payment card pre-stored in the vehicle-mounted terminal, generate Payment initiation message.

In some examples, the above-mentioned sending module 803 may be configured to send a payment initiation message to the payment management server.

In some other examples, the sending module 803 may be configured to send a payment initiation message to the acceptance terminal.

Fig. 12 is a schematic structural diagram of another embodiment of the vehicle-mounted terminal provided in the fourth aspect of the present application. The difference between FIG. 12 and FIG. 11 is that the vehicle-mounted terminal 800 shown in FIG. 12 may further include a storage module 804 and a verification module 805 .

In some examples, the above-mentioned receiving module 801 can also be used to: establish a communication connection with the user terminal; obtain authorization information of payment card information from the user terminal; obtain a payment card from a payment management server or a payment resource server according to the authorization information of payment card information information.

The storage module 804 may be used to store payment card information.

In some other examples, the receiving module 801 is further configured to: establish a communication connection with the user terminal; obtain payment card information from the user terminal.

The storage module 804 may be used for and store payment card information.

In some examples, the verification module 805 can be used to perform key security verification with the accepting terminal.

The above-mentioned receiving module 801 may be configured to receive the parking charging message sent by the accepting terminal when the security verification of the key is passed.

In some examples, the above-mentioned receiving module 801 may be configured to receive the parking charging message sent by the accepting terminal through the short-distance wireless communication technology. The receiving module 801 may specifically be a short-distance wireless communication module, which is not limited here.

The fifth aspect of the present application provides an acceptance terminal. Fig. 13 is a schematic structural diagram of an embodiment of an acceptance terminal provided in the fifth aspect of the present application. As shown in FIG. 13 , the acceptance terminal 900 may include an acquisition module 901 , a generation module 902 and a sending module 903 .

The acquiring module 901 can be used to acquire the vehicle identification and payment information of the target vehicle when the acceptance terminal senses the vehicle-mounted terminal of the target vehicle.

The generating module 902 may be configured to generate a parking charging message according to the vehicle identification and payment information of the target vehicle.

The parking charge message includes the target vehicle's vehicle identification and payment information.

The sending module 903 may be configured to send a parking fee message to the vehicle terminal, so that the vehicle terminal generates a payment initiation message according to the parking fee message and the payment card information pre-stored in the vehicle terminal.

The payment initiation message is obtained by the payment management server to interact with the payment resource server to complete the payment. Payment card information includes payment card personalization data.

In some examples, the payment initiation message is sent by the vehicle terminal before the exit gate of the parking lot is opened.

In some other examples, the payment initiation message is sent by the vehicle terminal after the exit gate of the parking lot is opened.

In some examples, the acquisition module 901 is further configured to receive a payment initiation message sent by the vehicle terminal.

The sending module 903 is further configured to send a payment initiation message to the payment management server.

In some examples, the above-mentioned sending module 903 may be used to broadcast a parking charge message to the vehicle terminal.

The parking charging message includes a first vehicle identification and first payment information. The first vehicle identifier is a vehicle identifier consistent with the target vehicle identifier stored in the vehicle-mounted terminal. The target vehicle identification includes a vehicle identification of the target vehicle. The first payment information is payment information corresponding to the first vehicle identifier. The payment initiation message is generated by the vehicle-mounted terminal according to the first vehicle identification, the first payment information, and the payment card information pre-stored in the vehicle-mounted terminal.

In some examples, the vehicle identification includes license plate information.

The acquisition module 901 can be used to acquire the vehicle image of the target vehicle, identify the license plate information from the vehicle image, and generate payment information corresponding to the license plate information as the payment information of the target vehicle according to the license plate information.

In some examples, the above-mentioned sending module 903 can also be used to: send the vehicle identification and payment information of the target vehicle to the payment management server, so that the payment management server can compare the payment initiation message received from the vehicle terminal with the target vehicle's information obtained from the acceptance terminal. The vehicle identification and payment information are matched, and according to the matching result, it is determined whether to make payment.

Fig. 14 is a schematic structural diagram of another embodiment of the acceptance terminal provided in the fifth aspect of the present application. The difference between FIG. 14 and FIG. 13 is that the acceptance terminal 900 shown in FIG. 14 may further include a verification module 904 and a control module 905 .

The verification module 904 can be used to perform key security verification with the vehicle-mounted terminal.

The acquisition module 901 may be used to acquire the vehicle identification and payment information of the target vehicle when the security verification of the key is passed.

The acquisition module 901 is further configured to receive a payment success message sent by the payment management server.

The payment success message is used to indicate that the payment is successful.

The control module 905 may be configured to control the exit gates of the parking lot to open in response to the payment success message, allowing the target vehicle to leave.

In some examples, the acquisition module 901 can also be used to acquire the historical payment orders of the target vehicle according to the vehicle identification of the target vehicle.

The above-mentioned control module 905 can also be used to control the opening of the exit gate of the parking lot to allow the target vehicle to leave when there is no unpaid order in the historical payment orders of the target vehicle.

The sixth aspect of the present application provides a payment management server. Fig. 15 is a schematic structural diagram of an embodiment of the payment management server provided in the sixth aspect of the present application. As shown in FIG. 15 , the payment management server 1000 may include a receiving module 1001 and a sending module 1002 .

The receiving module 1001 can be used to obtain a payment initiation message.

In some examples, the receiving module 1001 may be used to acquire the payment initiation message before the exit gate of the parking lot is opened.

In some other examples, the receiving module 1001 may be used to acquire the payment initiation message after the exit gate of the parking lot is opened.

The sending module 1002 can be configured to use the payment initiation message to interact with the payment resource server to complete the payment.

In some examples, the above-mentioned receiving module 1001 may be used to receive a payment initiation message from a vehicle-mounted terminal.

In some other examples, the above-mentioned receiving module 1001 may be configured to receive a payment initiation message from an acceptance terminal. The payment initiation message is sent from the vehicle-mounted terminal to the acceptance terminal.

Fig. 16 is a schematic structural diagram of another embodiment of the payment management server provided in the sixth aspect of the present application. The difference between FIG. 16 and FIG. 15 is that the payment management server 1000 shown in FIG. 16 may further include a matching module 1003 .

The above-mentioned receiving module 1001 can also be used to receive the vehicle identification and payment information of the target vehicle from the acceptance terminal after the acceptance terminal acquires the vehicle identification and payment information of the target vehicle.

The matching module 1003 can be used to match the payment initiation message received from the vehicle-mounted terminal with the vehicle identification and payment information of the target vehicle obtained from the accepting terminal.

The above-mentioned sending module 1002 can be configured to use the payment initiation message to interact with the payment resource server to complete the payment when the matching result is a successful match.

The seventh aspect of the present application also provides a vehicle-mounted terminal. Fig. 17 is a schematic structural diagram of an embodiment of the vehicle-mounted terminal provided by the seventh aspect of the present application. As shown in FIG. 17 , the vehicle-mounted terminal 1100 includes a memory 1101 , a processor 1102 and a computer program stored in the memory 1101 and operable on the processor 1102 .

In some examples, the above-mentioned processor 1102 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 1101 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform the operations described with reference to the in-vehicle payment method according to the first aspect of the present application.

The processor 1102 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 1101, so as to implement the vehicle payment method in the embodiment of the first aspect above.

In some examples, the vehicle terminal 1100 may further include a communication interface 1103 and a bus 1104 . Wherein, as shown in FIG. 17 , the memory 1101 , the processor 1102 , and the communication interface 1103 are connected through a bus 1104 to complete mutual communication.

The communication interface 1103 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 1103 .

The bus 1104 includes hardware, software or both, and couples the components of the vehicle terminal 1100 to each other. For example and without limitation, the bus 1104 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industrial Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, Micro Channel architecture (Micro Channel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association local ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Bus 1104 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

The eighth aspect of the present application also provides an acceptance terminal. Fig. 18 is a schematic structural diagram of an embodiment of an acceptance terminal provided in the eighth aspect of the present application. As shown in FIG. 18 , the acceptance terminal 1200 includes a memory 1201, a processor 1202, and a computer program stored in the memory 1201 and operable on the processor 1202.

In some examples, the above-mentioned processor 1202 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 1201 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform the operations described with reference to the in-vehicle payment method according to the second aspect of the present application.

The processor 1202 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 1201, so as to implement the vehicle payment method in the embodiment of the second aspect above.

In some examples, the acceptance terminal 1200 may further include a communication interface 1203 and a bus 1204 . Wherein, as shown in FIG. 18 , the memory 1201 , the processor 1202 , and the communication interface 1203 are connected through a bus 1204 to complete mutual communication.

The communication interface 1203 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 1203 .

The bus 1204 includes hardware, software or both, and couples the components of the acceptance terminal 1200 to each other. For example and without limitation, the bus 1204 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industrial Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, Micro Channel architecture (Micro Channel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association local ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Bus 1204 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

The ninth aspect of the present application also provides a payment management server. Fig. 19 is a schematic structural diagram of an embodiment of the payment management server provided in the ninth aspect of the present application. As shown in FIG. 19 , the payment management server 1300 includes a memory 1301 , a processor 1302 and a computer program stored in the memory 1301 and operable on the processor 1302 .

In some examples, the above-mentioned processor 1302 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 1301 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform the operations described with reference to the in-vehicle payment method according to the third aspect of the present application.

The processor 1302 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 1301, so as to implement the vehicle payment method in the embodiment of the third aspect above.

In some examples, the payment management server 1300 may further include a communication interface 1303 and a bus 1304 . Wherein, as shown in FIG. 19 , the memory 1301 , the processor 1302 , and the communication interface 1303 are connected through a bus 1304 to complete mutual communication.

The communication interface 1303 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 1303 .

The bus 1304 includes hardware, software, or both, and couples the components of the payment management server 1300 to each other. For example and not limitation, the bus 1304 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industrial Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, Micro Channel architecture (Micro Channel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association local ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Bus 1304 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

The tenth aspect of the present application provides an in-vehicle payment system. The in-vehicle payment system may include the in-vehicle terminal, the acceptance terminal and the payment management server in the above-mentioned embodiments. For details, please refer to the related descriptions in the above-mentioned embodiments, which will not be repeated here.

In some embodiments, the in-vehicle payment system may further include a payment resource server. For details, please refer to the relevant descriptions in the above embodiments, and details are not repeated here.

The eleventh aspect of the present application also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the vehicle-mounted The payment method, the in-vehicle payment method in the second aspect, or the in-vehicle payment method in the third aspect can achieve the same technical effect, and will not be repeated here to avoid repetition. Wherein, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk. etc., are not limited here.

It should be clear that each embodiment in this specification is described in a progressive manner, and the same or similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. place. The method embodiments can refer to each other. For the car terminal embodiment, the acceptance terminal embodiment, the payment management server embodiment, the system embodiment, and the computer-readable storage medium embodiment, for relevant parts, please refer to the description of the method embodiment. The application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application. Also, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each block of the flowchart and/or block diagrams, and combinations of blocks in the flowchart and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of these instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of the flowchart and/or block diagrams. Such processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It can also be understood that each block in the block diagrams and/or flowcharts and combinations of blocks in the block diagrams and/or flowcharts can also be realized by dedicated hardware for performing specified functions or actions, or can be implemented by dedicated hardware and combination of computer instructions.

Those skilled in the art should understand that the above-mentioned embodiments are illustrative rather than restrictive. Different technical features in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other modified embodiments of the disclosed embodiments on the basis of studying the drawings, specification and claims. In the claims, the term "comprising" does not exclude other means or steps; the numerical word "a" does not exclude a plurality; the terms "first" and "second" are used to indicate names and not to indicate any specific order . Any reference signs in the claims should not be construed as limiting the scope. The functions of several parts appearing in the claims can be realized by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to obtain beneficial effects.

Claims

A vehicle-mounted payment method applied to a vehicle-mounted terminal, the method comprising:

When the in-vehicle terminal of the target vehicle is sensed by the acceptance terminal of the parking lot, receiving a parking charge message sent by the acceptance terminal, the parking charge message including vehicle identification and payment information;

Generate a payment initiation message according to the parking charging message and the payment card information pre-stored in the vehicle terminal, the payment card information including personalization data of the payment card;

Sending the payment initiation message, so that the payment management server acquires the payment initiation message, and uses the payment initiation message to interact with the payment resource server to complete the payment.
The method according to claim 1, wherein the generating a payment initiation message according to the parking charge message and the payment card information pre-stored in the vehicle terminal includes:

Obtain the first vehicle identification and the first payment information from the parking charging message broadcast by the receiving terminal, the first vehicle identification is a vehicle identification consistent with the target vehicle identification stored in the vehicle-mounted terminal, and the target vehicle The identification includes a vehicle identification of the target vehicle, and the first payment information is payment information corresponding to the first vehicle identification;

A payment initiation message is generated according to the first vehicle identifier, the first payment information, and the personalization data of the payment card pre-stored in the vehicle-mounted terminal.
The method according to claim 1, wherein the sending the payment initiation message comprises:

sending the payment initiation message to the payment management server;

or,

Sending the payment initiation message to the acceptance terminal.
The method according to claim 1, before receiving the parking charge message sent by the acceptance terminal of the parking lot, further comprising:

Establish a communication connection with the user terminal; obtain the authorization information of the payment card information from the user terminal; obtain the payment card information from the payment management server or the payment resource server according to the authorization information of the payment card information , and store the payment card information;

or,

Establishing a communication connection with the user terminal; obtaining the payment card information from the user terminal, and storing the payment card information.
The method according to claim 1, before receiving the parking charge message sent by the acceptance terminal of the parking lot, further comprising:

Perform key security verification with the accepting terminal;

The receiving the parking charge message sent by the acceptance terminal of the parking lot includes:

If the security verification of the key is passed, the parking charge message sent by the accepting terminal is received.
The method according to claim 1, wherein the receiving the parking charge message sent by the acceptance terminal of the parking lot comprises:

receiving the parking charging message sent by the accepting terminal through short-distance wireless communication technology.
The method according to claim 1, wherein the sending the payment initiation message comprises:

sending the payment initiation message before the exit gate of the parking lot is opened;

or,

The payment initiation message is sent after the exit gate of the parking lot is opened.
The method according to any one of claims 1 to 7, wherein the vehicle identification includes license plate information and/or vehicle identification code.
The method according to any one of claims 1 to 7, wherein the payment information includes one or more of the following:

Payer information, payment time, payment fee, and parking duration.
A vehicle payment method applied to an acceptance terminal of a parking lot, the method comprising:

When the accepting terminal senses the vehicle terminal of the target vehicle, acquire the vehicle identification and payment information of the target vehicle;

generating a parking charging message according to the vehicle identification and payment information of the target vehicle, the parking charging message including the vehicle identification and payment information of the target vehicle;

Send the parking fee message to the vehicle terminal, so that the vehicle terminal generates a payment initiation message according to the parking fee message and the payment card information pre-stored in the vehicle terminal, and the payment initiation message is received by the payment management server The acquisition is used to interact with the payment resource server to complete the payment, and the payment card information includes personalization data of the payment card.
The method according to claim 10, after sending the parking charge message to the vehicle-mounted terminal, further comprising:

receiving the payment initiation message sent by the vehicle terminal;

Send the payment initiation message to the payment management server.
The method according to claim 10, wherein the sending the parking charging message to the vehicle terminal comprises:

broadcast the parking fee message to the vehicle terminal,

The parking charging message includes a first vehicle identification and first payment information, the first vehicle identification is a vehicle identification consistent with the target vehicle identification stored in the vehicle terminal, and the target vehicle identification includes the vehicle identification of the target vehicle, The first payment information is the payment information corresponding to the first vehicle identification, and the payment initiation message is sent by the vehicle-mounted terminal according to the first vehicle identification, the first payment information and the information pre-stored in the vehicle-mounted terminal. The payment card information in is generated.
The method of claim 10, wherein the vehicle identification includes license plate information,

The acquisition of the vehicle identification and payment information of the target vehicle includes:

acquiring a vehicle image of the target vehicle, and identifying the license plate information from the vehicle image;

According to the license plate information, the payment information corresponding to the license plate information is generated as the payment information of the target vehicle.
The method according to claim 11, after said obtaining the vehicle identification and payment information of the target vehicle, further comprising:

Sending the vehicle identification and payment information of the target vehicle to the payment management server, so that the payment management server compares the payment initiation message received from the vehicle terminal with the target vehicle information obtained from the acceptance terminal Match the vehicle identification and payment information, and determine whether to make payment according to the matching result.
The method according to claim 10, before said acquiring the vehicle identification and payment information of the target vehicle, further comprising:

Perform key security verification with the vehicle-mounted terminal;

The acquisition of the vehicle identification and payment information of the target vehicle includes:

If the security verification of the key is passed, the vehicle identification and payment information of the target vehicle are acquired.
The method of claim 10, further comprising:

receiving a successful payment message sent by the payment management server, where the successful payment message is used to indicate successful payment;

In response to the payment success message, an exit gate of the parking lot is controlled to be opened, allowing the target vehicle to leave.
The method of claim 10, further comprising:

Acquiring historical payment orders of the target vehicle according to the vehicle identification of the target vehicle;

In the case that there is no unpaid order in the historical payment order of the target vehicle, the exit gate of the parking lot is controlled to be opened, allowing the target vehicle to leave.
The method of claim 10, wherein,

The payment initiation message is sent by the vehicle-mounted terminal before the exit gate of the parking lot is opened;

or,

The payment initiation message is sent by the vehicle-mounted terminal after the exit gate of the parking lot is opened.
The method according to any one of claims 10 to 18, wherein the vehicle identification includes license plate information and/or a vehicle identification code.
The method according to any one of claims 10 to 18, wherein the payment information includes one or more of the following:

Payer information, payment time, payment fee, and parking duration.
A vehicle payment method applied to a payment management server, the method comprising:

Obtain a payment initiation message, the payment initiation message is generated by the vehicle-mounted terminal according to the parking charging message and the payment card information pre-stored in the vehicle-mounted terminal, and the parking charging message includes that the acceptance terminal of the parking lot senses the location of the target vehicle The vehicle identification and payment information acquired in the case of the vehicle-mounted terminal, the payment card information including personalization data of the payment card;

Use the payment initiation message to interact with the payment resource server to complete the payment.
The method according to claim 21, wherein said obtaining the payment initiation message comprises:

receiving the payment initiation message from the vehicle terminal;

or,

The payment initiation message is received from the acceptance terminal, and the payment initiation message is sent to the acceptance terminal by the vehicle-mounted terminal.
The method according to claim 21, before said utilizing said payment initiation message to interact with a payment resource server to complete payment, further comprising:

After the acceptance terminal acquires the vehicle identification and payment information of the target vehicle, receiving the vehicle identification and payment information of the target vehicle from the acceptance terminal;

matching the payment initiation message received from the in-vehicle terminal with the vehicle identification and payment information of the target vehicle acquired from the acceptance terminal;

The use of the payment initiation message to interact with the payment resource server to complete the payment includes:

If the matching result is that the matching is successful, the payment initiation message is used to interact with the payment resource server to complete the payment.
The method according to claim 21, wherein said obtaining the payment initiation message comprises:

Obtaining the payment initiation message before the exit gate of the parking lot is opened;

or,

The payment initiation message is acquired after the exit gate of the parking lot is opened.
The method according to any one of claims 21 to 24, wherein the vehicle identification includes license plate information and/or a vehicle identification code.
The method according to any one of claims 21 to 24, wherein the payment information includes one or more of the following:

Payer information, payment time, payment fee, and parking duration.
A vehicle terminal, comprising:

A receiving module, configured to receive a parking fee message sent by the acceptance terminal when the vehicle-mounted terminal of the target vehicle is sensed by the acceptance terminal of the parking lot, the parking fee message includes the vehicle identification and payment information;

A generation module, configured to generate a payment initiation message according to the parking charge message and the payment card information pre-stored in the vehicle terminal, the payment card information including personalization data of the payment card;

A sending module, configured to send the payment initiation message, so that the payment management server acquires the payment initiation message, and utilizes the payment initiation message to interact with the payment resource server to complete the payment.
An acceptance terminal, comprising:

An acquisition module, configured to acquire the vehicle identification and payment information of the target vehicle when the acceptance terminal senses the vehicle-mounted terminal of the target vehicle;

A generating module, configured to generate a parking charging message according to the vehicle identification and payment information of the target vehicle, the parking charging message including the vehicle identification and payment information of the target vehicle;

A sending module, configured to send the parking charging message to the vehicle-mounted terminal, so that the vehicle-mounted terminal generates a payment initiation message according to the parking charging message and payment card information pre-stored in the vehicle-mounted terminal, and the payment initiation The message is acquired by the payment management server to interact with the payment resource server to complete the payment, and the payment card information includes personalization data of the payment card.
A payment management server, comprising:

The receiving module is used to acquire a payment initiation message, which is generated by the vehicle-mounted terminal according to the parking charging message and the payment card information pre-stored in the vehicle-mounted terminal. The vehicle identification and payment information obtained under the condition of the vehicle-mounted terminal of the target vehicle, the payment card information including personalization data of the payment card;

A sending module, configured to use the payment initiation message to interact with the payment resource server to complete the payment.
A vehicle-mounted terminal, comprising: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the in-vehicle payment method according to any one of claims 1 to 9 is realized.
An acceptance terminal, comprising: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the in-vehicle payment method according to any one of claims 10 to 20 is realized.
A payment management server, comprising: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the in-vehicle payment method according to any one of claims 21 to 26 is realized.
An in-vehicle payment system, comprising the in-vehicle terminal as claimed in claim 30, the acceptance terminal as claimed in claim 31, and the payment management server as claimed in claim 32.
A computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the in-vehicle payment method according to any one of claims 1 to 26 is implemented.