Method for realizing payment service, electronic equipment, storage medium and vehicle

Abstract

The invention discloses a payment business realization method, electronic equipment, a storage medium and a vehicle, and the method comprises the steps: transmitting a transaction request and vehicle bill information to a vehicle main engine plant server when the transaction request and the vehicle bill information transmitted by a payee business server are received; and payment processing is carried out according to the feedback information of the vehicle main engine plant server and the feedback information of the payee business server. According to the method provided by the invention, the function that the vehicle participates in the payment service as a payment subject is realized, so that the vehicle becomes an intelligent payment acceptance terminal with relatively high mobility and is not limited by fixed places, and thus the convenience and efficiency of the payment service are improved.

Description

Technical Field

[0001] This invention relates to the field of payment technology, and in particular to a method for implementing payment services, an electronic device, a non-volatile readable storage medium, and a vehicle. Background Technology

[0002] With the rapid popularization of mobile internet and the widespread use of smartphones, payment acceptance terminals are moving towards mobile intelligence. For example, UnionPay's mobile POS (Point of Sale) system is an underlying service that runs on smartphones, providing support for third-party applications through open APIs (Application Programming Interfaces). Users only need to install a third-party application that supports the UnionPay mobile POS API on their smartphones, or register and activate the system through the mobile wallet application provided by the phone manufacturer, via online identity authentication, etc., to enable their phones to have multiple functions such as UnionPay IC (Integrated Circuit) card contactless payment, UnionPay mobile contactless payment, and QR code scanning, thus transforming their phones into multi-functional payment devices.

[0003] However, in the current context of mobile smart payment terminals, even when using a mobile phone as the terminal, the payment scenarios for payees remain relatively fixed. This is because, while mobile phones are portable, their essential purpose is still to replace traditional POS acquiring devices and handle related transactions. In this situation, even if payees use mobile POS for payment collection, their payment scenarios are still limited by the usage methods and scenario requirements of traditional POS devices. This means that mobile POS systems cannot flexibly adapt to different application scenarios, i.e., they cannot easily integrate with other application scenarios. Summary of the Invention

[0004] This invention aims to at least solve one of the technical problems existing in the prior art. Therefore, one objective of this invention is to propose a method for implementing payment services, which enables vehicles to participate in payment transactions as payment entities, making vehicles highly mobile intelligent payment acceptance terminals, not limited by fixed locations, thereby improving the convenience and efficiency of payment services.

[0005] The second objective of this invention is to propose a method for implementing payment services.

[0006] The third objective of this invention is to provide an electronic device.

[0007] The fourth objective of this invention is to provide a non-volatile readable storage medium.

[0008] The fifth objective of this invention is to provide a vehicle.

[0009] To achieve the above objectives, a method for implementing payment services according to a first aspect of the present invention is provided for vehicles. The method includes: upon receiving a transaction request and vehicle billing information from a payee's business server, sending the transaction request and the vehicle billing information to a vehicle OEM server; and performing payment processing based on feedback information from the vehicle OEM server and the payee's business server.

[0010] According to the payment method of this invention, the vehicle manufacturer's server is a key link in the entire payment process. It enables the vehicle to process payment transactions. Specifically, the vehicle manufacturer's server can receive transaction requests and vehicle billing information sent by the payee's business server, and verify and process their accuracy. At the same time, the payee's business server can also provide feedback on whether the payment is confirmed and whether the payment amount is correct. Based on this feedback, the vehicle can perform the corresponding payment processing. This process reflects the vehicle's function as a payment subject participating in payment transactions. Due to the vehicle's strong mobility, it can participate in payment transactions at any time and any place, no longer limited to fixed payment terminal locations. This improved mobility makes payments more convenient and efficient. Users do not need to go to a specific location to complete the payment; they can complete the payment process simply by operating the system inside the vehicle, thus providing users with a more convenient and efficient payment experience.

[0011] In some embodiments, the feedback information from the payee's business server includes a transaction confirmation reminder message, which is sent by the payee's business server when it receives a response from the vehicle manufacturer's server to the transaction request. The vehicle manufacturer's server responds to the transaction request after identifying the vehicle as a registered vehicle based on the vehicle billing information. The payment processing includes prompting the user to confirm the transaction and sending transaction confirmation information to the vehicle manufacturer's server in response to the user's transaction confirmation instruction.

[0012] In some embodiments, the feedback information from the vehicle OEM server includes a UnionPay card transaction authentication certificate, which is obtained by the vehicle OEM server sending a certificate request to the UnionPay server in response to the transaction confirmation information; the payment processing includes prompting the user to perform a payment operation.

[0013] In some embodiments, the method further includes: switching to the payment platform hosting business mode in response to a payment platform program initialization request before the user performs a payment operation.

[0014] In some embodiments, the method further includes: obtaining payment account information of the user terminal; and sending the payment account information and the UnionPay card transaction authentication certificate to the vehicle manufacturer's server.

[0015] In some embodiments, the method further includes: the feedback information from the vehicle manufacturer's server also includes bank account change information; the payment processing further includes sending the bank account change information to the payee's business server.

[0016] In some embodiments, the feedback information from the payee's business server may further include a transaction completion signal; the transaction completion signal is a signal fed back by the payee's business server based on the bank account change information; the payment processing may further include prompting the transaction result.

[0017] In some embodiments, the method further includes: responding to a digital key mode request to switch from the payment platform hosting business mode to digital key mode, and prompting the user.

[0018] In some embodiments, the method further includes: obtaining vehicle owner identity information and authenticating the vehicle owner's identity based on the vehicle owner identity information.

[0019] In some embodiments, the vehicle owner identity information includes at least one of the vehicle owner digital key information and the vehicle owner cloud service account information.

[0020] In some embodiments, authenticating the vehicle owner's identity based on the vehicle owner's identity information includes at least one of the following: unlocking or locking the vehicle based on the vehicle owner's digital key information; obtaining vehicle engine start authorization based on the vehicle owner's digital key information; and obtaining vehicle owner's digital key information based on the vehicle owner's cloud service account information.

[0021] To achieve the above objectives, a method for implementing payment services according to a second aspect of the present invention is used in a vehicle OEM server. The method includes: receiving a transaction request and vehicle billing information sent by a vehicle, wherein the vehicle billing information is ciphertext encrypted by a payee's business server using a public key provided by the vehicle OEM server; and decrypting the vehicle billing information using a self-owned private key.

[0022] According to the payment method of this invention, the vehicle manufacturer's server is a key link in the entire payment process. It enables the vehicle to process payment transactions. Specifically, the payee's business server encrypts the vehicle bill information using the public key provided by the vehicle manufacturer's server and sends it along with the transaction request to the vehicle manufacturer's server. This process ensures secure data transmission and prevents data from being illegally stolen or tampered with during transmission. The vehicle manufacturer's server decrypts the vehicle bill information using its own private key. This process ensures data confidentiality. Only the vehicle manufacturer's server with the corresponding private key can decrypt and obtain the bill information. Therefore, the vehicle manufacturer's server plays an important security role in the payment process, providing reliable technical support for vehicle payment transactions and enabling the vehicle to participate in payment transactions as a payment subject. This makes the vehicle a highly mobile intelligent payment acceptance terminal, not limited by fixed locations, thereby improving the convenience and efficiency of payment transactions.

[0023] In some embodiments, the vehicle billing information includes vehicle identity information; the vehicle OEM server identifies the vehicle based on the vehicle identity information and responds to the transaction request when the vehicle is a registered vehicle.

[0024] In some embodiments, the method further includes: upon receiving transaction confirmation information sent by the vehicle, confirming that the vehicle owner's identity has been authenticated, sending a request for a UnionPay card transaction authentication certificate to the UnionPay server; obtaining ciphertext containing the UnionPay card transaction authentication certificate, decrypting the ciphertext using a self-owned private key to obtain the UnionPay card transaction authentication certificate and the UnionPay public key, and verifying the signature of the UnionPay public key; and sending the UnionPay card transaction authentication certificate to the vehicle.

[0025] In some embodiments, the method further includes: upon receiving payment account information and UnionPay card transaction authentication certificate sent by the vehicle, encrypting the vehicle billing information, the payment account information, and the UnionPay card transaction authentication certificate using a self-owned private key and sending them to the UnionPay server, and sending a request to the UnionPay server for bank account change information.

[0026] In some embodiments, the method further includes: upon receiving bank account change information sent by the UnionPay server, sending the bank account change information to the vehicle.

[0027] In some embodiments, the method further includes sending a payment platform program initialization request or a digital key mode request to the vehicle.

[0028] To achieve the above objectives, an electronic device according to a third aspect of the present invention includes: at least one processor; a memory communicatively connected to the at least one processor; the memory storing a computer program executable by the at least one processor, wherein the at least one processor executes the computer program to implement the payment service method described in the above embodiment.

[0029] The electronic device according to the embodiments of the present invention, by adopting the payment service method described in the above embodiments, realizes the function of vehicles participating in payment services as payment subjects, making vehicles a highly mobile intelligent payment acceptance terminal, not restricted by fixed locations, thereby improving the convenience and efficiency of payment services.

[0030] To achieve the above objectives, a non-volatile readable storage medium according to a fourth aspect of the present invention stores a computer program thereon, characterized in that, when the computer program is executed, it implements the method for implementing payment services as described in the above embodiments.

[0031] According to the embodiments of the present invention, the non-volatile readable storage medium, by adopting the payment business implementation method described in the above embodiments, realizes the function of vehicles participating in payment business as payment subjects, making vehicles a highly mobile intelligent payment acceptance terminal, not restricted by fixed locations, thereby improving the convenience and efficiency of payment business.

[0032] To achieve the above objectives, a vehicle according to a fifth aspect embodiment of the present invention includes: a communication module for communicating with a payee's business server and a vehicle OEM's server respectively; a display module for prompting the user with payment information; and a payment module connected to the display module and the communication module respectively, for executing the method for implementing payment business as described in the above embodiment.

[0033] According to the vehicle of the present invention, the payment module is connected to the display module and the communication module respectively, and is used to execute the payment business method described in the above embodiment. Through the payment module, the vehicle can process payment according to the transaction request and vehicle bill information sent by the payee's business server. The payment module is responsible for executing payment instructions and exchanging data with the payee's business server and the vehicle's OEM server to ensure the smooth progress of the payment process. These components together constitute the payment system of the intelligent vehicle, realizing the function of the vehicle as a payment subject to participate in payment business, making the vehicle a highly mobile intelligent payment acceptance terminal, not restricted by fixed locations, thereby improving the convenience and efficiency of payment business.

[0034] In some embodiments, the vehicle includes a tray for placing a user terminal; the payment module includes a near-field communication module located on the tray.

[0035] In some embodiments, the near-field communication module includes: a sensing unit for sensing payment account information provided by the user terminal; a security unit for encrypting and decrypting data, securely storing data, and switching the operating mode of the near-field communication module; and a control unit connected to the sensing unit and the security unit respectively, for controlling the sensing unit and the security unit.

[0036] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0037] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which:

[0038] Figure 1 This is a flowchart of a method for implementing payment services according to an embodiment of the present invention;

[0039] Figure 2 This is a flowchart of a method for implementing payment services according to yet another embodiment of the present invention;

[0040] Figure 3 This is an interactive diagram illustrating the opening of a bank card application in a mobile wallet according to an embodiment of the present invention.

[0041] Figure 4 This is an interactive diagram illustrating the fulfillment of preconditions for a payment transaction according to an embodiment of the present invention;

[0042] Figure 5 This is an interactive schematic diagram of a payment transaction process according to an embodiment of the present invention;

[0043] Figure 6 This is a block diagram of an electronic device according to an embodiment of the present invention;

[0044] Figure 7 This is a block diagram of a vehicle according to an embodiment of the present invention;

[0045] Figure 8 This is a block diagram of a near-field communication module according to an embodiment of the present invention;

[0046] Figure 9 This is a topology diagram of tNFC payment acceptance according to an embodiment of the present invention;

[0047] Figure 10 This is a schematic diagram of the architecture of a tNFC payment acceptance system according to an embodiment of the present invention.

[0048] Figure label:

[0049] 100 vehicles;

[0050] Communication module 1; Display module 2; Payment module 3;

[0051] Near-field communication module 30;

[0052] Sensing unit 31; Safety unit 32; Control unit 33;

[0053] 200 electronic devices;

[0054] Processor 201; Memory 202. Detailed Implementation

[0055] The embodiments of the present invention are described in detail below. The embodiments described with reference to the accompanying drawings are exemplary. The embodiments of the present invention are described in detail below.

[0056] The following is for reference. Figure 1 This invention describes a method for implementing payment services according to an embodiment of the invention. This method is used in vehicles, enabling vehicles to become highly mobile intelligent payment acceptance terminals, free from the limitations of fixed locations, thereby improving the convenience and efficiency of payment services.

[0057] Figure 1 This is a flowchart of a method for implementing payment services according to an embodiment of the present invention, such as... Figure 1 As shown, the method for implementing payment services according to an embodiment of the present invention includes at least steps S1-S2, as detailed below:

[0058] S1, upon receiving the transaction request and vehicle billing information from the payee's business server, sends the transaction request and vehicle billing information to the vehicle manufacturer's server.

[0059] In some embodiments, the payee's business server can be a server responsible for initiating transaction requests, such as a payment system at a highway toll station, a gas station, or a parking lot. The function of the payee's business server is to send transaction requests and vehicle billing information to the vehicle.

[0060] Among them, vehicle billing information can be the specific transaction details of the payment requested by the payee. Taking the smart parking payment scenario as an example, vehicle billing information includes, but is not limited to: order number, license plate number, entry / exit time, transaction amount, etc.

[0061] In some embodiments, the vehicle manufacturer's server can be the vehicle's central processing unit, responsible for managing vehicle payments and related business, and is provided by the vehicle manufacturer or operator. The role of the vehicle manufacturer's server is to receive transaction requests and vehicle billing information from the payee's business server.

[0062] Specifically, the communication module of a smart car can receive transaction requests and vehicle billing information from the payee's business server. The vehicle then sends the received transaction requests and vehicle billing information to the vehicle manufacturer's server. During transmission, this information can be encrypted to ensure security and prevent unauthorized access or tampering. After receiving the transaction requests and billing information, the vehicle manufacturer's server can verify and confirm their accuracy. This includes checking the legitimacy of the transaction requests and the correctness of the vehicle billing information.

[0063] S2 processes payments based on feedback from the vehicle manufacturer's server and the payee's business server.

[0064] Specifically, the intelligent vehicle receives feedback information from the vehicle manufacturer's server and the payee's business server. This feedback information may include whether the payment has been confirmed and whether the payment amount is correct. Based on the received feedback information, the intelligent vehicle processes the payment. If payment is confirmed, the intelligent vehicle can execute the payment operation and transfer the funds to the payee. If the payment is canceled or there are any abnormalities, the intelligent vehicle will handle the situation accordingly, such as re-initiating the payment request or prompting the user to perform other operations.

[0065] According to the payment method of this invention, the vehicle manufacturer's server is a key link in the entire payment process. It enables the vehicle to process payment transactions. Specifically, the vehicle manufacturer's server can receive transaction requests and vehicle billing information sent by the payee's business server, and verify and process their accuracy. At the same time, the payee's business server can also provide feedback on whether the payment is confirmed and whether the payment amount is correct. Based on this feedback, the vehicle can perform the corresponding payment processing. This process reflects the vehicle's function as a payment subject participating in payment transactions. Due to the vehicle's strong mobility, it can participate in payment transactions at any time and any place, no longer limited to fixed payment terminal locations. This improved mobility makes payments more convenient and efficient. Users do not need to go to a specific location to complete the payment; they can complete the payment process simply by operating the system inside the vehicle, thus providing users with a more convenient and efficient payment experience.

[0066] In some embodiments, compared to mobile phones, smart cars, as mobile smart payment acceptance terminals, have two significant characteristics:

[0067] First, it boasts enhanced mobility. Current core usage scenarios for automobiles often involve movement, allowing cars to enter and stop at various offline payment / collection locations that meet certain conditions, such as gas stations, parking lots, and toll booths. This makes smart cars true mobile payment terminals, unrestricted by fixed locations. For example, car owners can complete payment directly on the car's smart interface while refueling at a gas station, without requiring additional devices or steps. This versatility and mobility make smart cars a more flexible and convenient payment acceptance terminal.

[0068] Second, car owners are mostly the payers. In each independent and specific payment / receipt scenario, the payment acceptance model has changed from 1 payee + x acquiring devices to y payers (1≤x is much less than y) to 1 payee + y acquiring devices to y payers (y is much greater than 1).

[0069] In this scenario, a payment processing method can be described as 1 payee + x acquiring devices for y payers (1 ≤ x is much smaller than y). This model represents a traditional payment processing method where one payee (e.g., a smart cloud server for smart parking) is equipped with only one or a few POS terminals to accept payments from multiple payers (e.g., users). In this case, the number of acquiring devices is relatively small compared to the number of payers. When multiple payers need to make payments, they need to queue. Because the payee has a limited number of acquiring devices, payers may experience long waiting times, especially in busy scenarios.

[0070] The model of 1 payee + y acquiring devices for y payers (y is much greater than 1) can refer to the scenario where smart cars act as mobile payment terminals. In this case, the payee can be a smart cloud platform such as a smart parking server, and each smart car can become an independent acquiring device, capable of handling payment requests from multiple payers simultaneously. The advantage of this model is improved payment efficiency, especially in high-concurrency payment scenarios. As long as the vehicle manufacturer's servers have sufficient load balancing and disaster recovery capabilities, they can support the high-efficiency payment processing of smart cars. Because each car can process payments independently, there is no need to wait in line, thus speeding up the entire payment process.

[0071] In conclusion, smart cars, as mobile intelligent payment acceptance terminals, offer greater mobility and higher payment collection efficiency. With the car owner as the payer, each vehicle can independently handle payment requests, making payment / collection models in smart cars more flexible and convenient, while also bringing new possibilities for the development of mobile payments.

[0072] In some embodiments, the feedback information from the payee's business server includes a transaction confirmation reminder message. This message is sent by the payee's business server upon receiving a response from the vehicle manufacturer's server regarding the transaction request. The vehicle manufacturer's server responds to the transaction request after identifying the vehicle as a registered vehicle based on the vehicle billing information. The payment processing includes prompting the user to confirm the transaction and, in response to the user's confirmation instruction, sending transaction confirmation information to the vehicle manufacturer's server.

[0073] Specifically, when a smart car enters a smart parking lot, the parking fee collection system, acting as the payment server, sends a transaction request and vehicle billing information. The vehicle manufacturer's server, after identifying the vehicle as a registered vehicle based on the billing information, responds to the transaction request. Upon receiving the response from the vehicle manufacturer's server, the parking fee collection system sends a transaction confirmation reminder to the smart car. This reminder may include: payment amount, order details, payment deadline, etc. This information will then pop up in the service provider's app on the host PAD (tablet), reminding the user that there is an pending parking payment order that needs to be processed.

[0074] Furthermore, after seeing the transaction information on the display screen, the user can choose to confirm the transaction. If the user confirms the payment, the smart car will respond to the user's confirmation command and send the transaction confirmation information to the vehicle manufacturer's server. Upon receiving the transaction confirmation information, the vehicle manufacturer's server can proceed with the final payment processing. If everything goes smoothly, the vehicle manufacturer's server sends a payment success message to the parking lot payment system. Upon receiving the payment success feedback, the parking lot payment system will release the parking barrier, allowing the vehicle to leave the parking lot.

[0075] Therefore, the intelligent vehicle participates in the entire payment process as the payment entity. Feedback from the payee's server serves to remind the user to confirm the transaction. The user confirms via the intelligent vehicle's display screen, and the intelligent vehicle then sends the confirmation information to the vehicle manufacturer's server, completing the payment process. This process design improves the user's controllability and convenience in payment transactions. Users can complete payment confirmation through the intelligent vehicle's interface without needing to log into other platforms or operate other devices. Simultaneously, the vehicle manufacturer's server, as the central processing unit, manages the entire payment process, ensuring the security and reliability of the transaction.

[0076] In some embodiments, the feedback information from the vehicle manufacturer's server includes a UnionPay card transaction authentication certificate, which is obtained by the vehicle manufacturer's server in response to a transaction confirmation message by sending a certificate request to the UnionPay server. Payment processing includes prompting the user to perform a payment operation.

[0077] The UnionPay server, operated by China UnionPay, is responsible for processing UnionPay card transactions and payment requests. It is a highly secure and reliable payment platform used to handle transactions from various UnionPay cards, including debit and credit cards. Connecting the payment systems of various merchants and banks, the UnionPay server is a crucial link in the payment process. Its role is to process payment transaction requests, verify and authorize transactions, and ultimately complete the payment process. When a smart car needs to make a payment, the vehicle's OEM server responds with transaction confirmation information and sends a certificate authorization request to the UnionPay server. Upon receiving the request, the UnionPay server verifies the user's identity, account balance, and other information. Once authorization is successful, the UnionPay server generates a UnionPay card transaction authentication certificate and sends it to the vehicle's OEM server as proof of payment.

[0078] In some embodiments, the UnionPay card transaction authentication certificate is a digital certificate generated by the UnionPay server to prove the legality and authorization of a transaction. It contains key transaction information, such as the transaction amount and time. The UnionPay card transaction authentication certificate plays a crucial role in the payment process. Through digital signatures, it ensures the integrity and authenticity of transaction information, preventing tampering or forgery. This certificate serves as authorization credential from the UnionPay server for the transaction, indicating that it is an authorized and legitimate transaction. After receiving the UnionPay card transaction authentication certificate, the smart car can confirm that the payment process is complete and can proceed with subsequent business processes.

[0079] In some embodiments, the method for implementing payment services further includes: switching to the payment platform hosting business mode in response to a payment platform program initialization request before the user performs a payment operation.

[0080] Specifically, taking smart parking payment as an example, when a user chooses to pay the parking fee, the smart car's payment module can receive an initialization request from the payment platform program. This request can be issued by the parking lot's payment system, requesting the establishment of a secure channel and readiness to receive payment information.

[0081] Furthermore, upon receiving the initialization request from the payment platform program, the payment module will immediately respond and begin executing the corresponding operations. The payment module establishes a secure communication channel with the payment platform via an encryption protocol to ensure the security of the payment process. After responding to the initialization request, the payment module will switch to the payment platform-hosted business mode, meaning that the payment module is ready to receive payment instructions and transaction data from the payment platform and begin processing payment transactions.

[0082] Furthermore, once the payment module switches to a business mode hosted by the payment platform, it becomes the central hub for payment transactions, enabling real-time interaction and communication with the payment platform. When the smart car receives a payment instruction from the payment platform, the payment module can process it accordingly, such as verifying the instruction's validity and checking the payment amount. After confirming all conditions are met, the payment module can execute the payment operation, transferring the payment amount from the user's bank account to the payee's account. Simultaneously, the payment module can generate payment vouchers or transaction records and store them in the vehicle's storage device for later retrieval and management.

[0083] In some embodiments, the method for implementing payment services further includes obtaining the user terminal's payment account information and sending the payment account information and UnionPay card transaction authentication certificate to the vehicle manufacturer's server. The user terminal's payment account information may be a simulated bank card CID (Card Identifier) ​​in the mobile wallet of a smartphone. The simulated bank card CID in the mobile wallet is virtual bank card information used to simulate a real bank card for payment operations. The simulated bank card CID may include, but is not limited to, a bank account number, payment password, payment method, and payment limit. The bank account number may be a simulated bank account number used to indicate the source of payment funds. The payment password may be a password used to verify user identity and authorize payment. The payment method may be a specified payment method, such as a credit card or debit card. The payment limit may be a specified payment limit, controlling the upper limit of each transaction.

[0084] Specifically, taking smart parking payment as an example, a user drives a smart car to a parking lot and needs to pay a parking fee. The user opens a payment application on their mobile phone and selects to pay using a simulated bank card CID from their mobile wallet. The smart car's payment module detects the simulated bank card CID and other payment account information from the user's mobile phone.

[0085] Furthermore, the payment module encrypts the user's payment account information along with the UnionPay card transaction authentication certificate and sends it to the vehicle manufacturer's server. Upon receiving this information, the vehicle manufacturer's server first uses its private key to decrypt and verify the validity of the user's payment account information, such as checking the bank account number and payment password.

[0086] Furthermore, the server uses a UnionPay card transaction authentication certificate to authenticate the payment transaction, ensuring its legality and security. Then, the vehicle manufacturer's server sends a confirmation message to the payment module, informing it that the payment operation can proceed. Upon receiving the confirmation message, the payment module continues the payment process, completing the parking fee payment.

[0087] In some embodiments, the feedback information from the vehicle manufacturer's server may also include bank account change information. This bank account change information may include, but is not limited to, changes in account balance, changes in linked bank cards, and changes in account status.

[0088] In some embodiments, after receiving bank account change information from the vehicle manufacturer's server, the payment module of the smart car can send this information to the payee's business server. This is to allow the payee's business server to be promptly aware of changes in the vehicle's bank account status, enabling adjustments to payment processing procedures or reminders to the user to top up their account. Upon receiving the bank account change information, the payee's business server can take appropriate action. For example, if the account balance is insufficient to cover the current transaction amount, the payee's business server can send a reminder to the smart car, prompting the user to top up their account or choose an alternative payment method. If bank card information changes, the payee's business server can update the relevant payment records and account information. If the account status changes, such as an account freeze, the payee's business server can suspend related payment services until the account status is restored.

[0089] In some embodiments, the feedback information from the payee's business server may also include a transaction completion signal, which is a signal fed back by the payee's business server based on changes in bank account information.

[0090] Specifically, after receiving bank account change information from the vehicle manufacturer's server, the payee's business server can process this information. The payee's business server confirms whether the transaction is complete based on the bank account change information. If the transaction is successfully completed, the payee's business server can generate a transaction completion signal and send it to the vehicle manufacturer's server in encryption. The transaction completion signal includes, but is not limited to: transaction status (success or failure), transaction completion time, payment amount and payment details, and relevant transaction reference number or order number, etc.

[0091] In some embodiments, payment processing also includes displaying the transaction result. Specifically, the vehicle OEM server receives a transaction completion signal from the payee's business server. Through a display module, the vehicle OEM server can show the transaction result to the user. The user can see a message indicating whether the transaction was successfully completed on a display screen inside the vehicle. If the transaction is successful, the user receives a corresponding success notification and can view the transaction details. If the transaction fails, the user receives a failure notification and is prompted to perform other operations or contact customer service to resolve the issue. Therefore, through the display module inside the vehicle, the vehicle can intuitively display the transaction result to the user. This display of the transaction result increases the user's trust and control over the payment process, while allowing the user to easily view transaction details and confirm the payment result.

[0092] In some embodiments, the method for implementing payment services further includes: switching from the payment platform-hosted service mode to the digital key mode in response to a digital key mode request, and prompting the user. Here, digital key mode can refer to a vehicle being able to simulate the functions of a traditional car key via a mobile phone or other smart device, enabling remote unlocking, starting, and other operations. The vehicle's digital key mode requires authorization and verification to ensure security.

[0093] Specifically, when a user makes a payment inside the vehicle, the vehicle's payment module can prompt the user to complete the payment. If the user also needs to use the digital key mode (for example, to remotely unlock the car door), they can switch to the digital key mode request function through the payment module.

[0094] Furthermore, on the payment module's display interface, users will see an option or button to request switching to digital key mode. After the user selects to request switching to digital key mode, the payment module can send a request to the vehicle manufacturer's server to apply for switching to digital key mode.

[0095] Furthermore, the vehicle manufacturer's server can verify the user's identity and permissions, confirming that the user can use the digital key mode. If the verification is successful, the vehicle manufacturer's server can send a confirmation signal to the payment module. After receiving the confirmation signal, the payment module will prompt the user to switch to digital key mode. After the user confirms the switch on the payment module, the payment module will switch to digital key mode and simultaneously send a prompt to the vehicle manufacturer's server. After switching to digital key mode, the user can use their mobile phone as a digital key to unlock and start the vehicle.

[0096] In some embodiments, the method for implementing payment services further includes: obtaining vehicle owner identity information and authenticating the vehicle owner's identity based on the vehicle owner identity information. The main purpose of this authentication is to ensure that only the legitimate vehicle owner can perform sensitive operations, such as making payments or switching to digital key mode. Authenticating the vehicle owner's identity can effectively protect the rights and interests of the vehicle owner and the security of the vehicle, preventing unauthorized personnel from performing malicious operations or stealing the vehicle owner's identity information.

[0097] In some embodiments, the vehicle owner's identity information includes at least one of the following: vehicle owner digital key information and vehicle owner cloud service account information. The vehicle owner's digital key information may refer to a digital key used for remotely controlling the vehicle, which can be used to unlock, start, and perform other operations on the vehicle via a smartphone application or other remote control devices. During vehicle owner authentication, the system may require the vehicle owner to provide digital key information, such as logging into a digital key application or entering a digital key password. This is to ensure that only the authorized vehicle owner can perform remote control operations, thereby increasing vehicle security.

[0098] In some embodiments, the vehicle owner's cloud service account information may refer to the cloud service account associated with the vehicle, which can be used for functions such as remotely monitoring vehicle status, receiving vehicle alarms, and managing vehicle settings. During vehicle owner authentication, the system may require the owner to enter their cloud service account and password to access the vehicle's online platform for authentication. This is to ensure that only authorized vehicle owners can access the vehicle's cloud service functions, preventing unauthorized users from operating the system.

[0099] In some embodiments, authenticating the vehicle owner's identity based on the vehicle owner's identity information includes at least one of the following:

[0100] First, the vehicle is unlocked or locked based on the owner's digital key information. Specifically, when the owner approaches the vehicle, the smart car's onboard system can communicate with the owner's digital key, for example, via Near Field Communication (NFC) or Bluetooth. If the owner's digital key information matches the vehicle, the owner's identity is successfully authenticated. The smart car can then unlock the vehicle, allowing the owner to enter. Conversely, if the digital key information does not match or is unavailable, the owner's identity has not been authenticated. The smart car will remain locked, prohibiting unauthorized access.

[0101] Second, the vehicle engine start authorization is obtained based on the owner's digital key information. Specifically, the owner can use the digital key application on their mobile phone to click the engine start button. The application will then encrypt the start command and send it to the vehicle. After receiving the start command, the vehicle manufacturer's server will authenticate the owner and verify the command's legitimacy. If the authentication is successful, the system will issue a start command to the vehicle, and the engine will start.

[0102] Third, the vehicle owner's digital key information is obtained based on their cloud service account information. Specifically, vehicle owners can log in to their cloud service account through a mobile app or website provided by the smart car manufacturer. Within this account, owners can manage their digital key information, including actions such as claiming, deleting, and authorizing. Once the owner logs in and verifies their identity, the smart car can retrieve the latest digital key information from the cloud, ensuring that the owner can use the digital key to operate the vehicle anytime, anywhere.

[0103] In some embodiments of the present invention, a method for implementing payment services is also proposed. This method is used in a vehicle OEM server and can enable vehicles to participate in payment services as payment entities, making vehicles a highly mobile intelligent payment acceptance terminal that is not limited by fixed locations, thereby improving the convenience and efficiency of payment services.

[0104] Figure 2This is a flowchart of a method for implementing payment services according to another embodiment of the present invention, as shown below. Figure 2 As shown, the method for implementing payment transactions includes at least steps S10-S11, as detailed below:

[0105] S10 receives the transaction request and vehicle billing information sent by the vehicle.

[0106] In some embodiments, vehicle billing information is ciphertext encrypted by the payee's business server using a public key provided by the vehicle manufacturer's server. This information may include transaction-related data such as order number, license plate number, timestamp, and transaction amount.

[0107] Specifically, in the system design, the vehicle manufacturer's server can generate a public and private key pair for encrypting and decrypting vehicle billing information. The public key can be provided to the payee's business server for encrypting the vehicle billing information. The private key is held only by the vehicle manufacturer's server and is used to decrypt the received encrypted information. The vehicle sends a transaction request and vehicle billing information to the vehicle manufacturer's server via the communication module. The vehicle manufacturer's server receives the data packet, which contains the encrypted vehicle billing information. The vehicle billing information in the data packet is encrypted using the public key provided by the vehicle manufacturer's server to ensure security during transmission.

[0108] S11, decrypt the vehicle billing information using your own private key.

[0109] In some embodiments, the vehicle manufacturer's server uses its own private key to decrypt the received ciphertext to obtain the original vehicle billing information. During decryption, the vehicle manufacturer's server uses its own private key, which is a key pair paired with the public key, to decrypt the received encrypted data. This design ensures security during information transmission and prevents sensitive information from being obtained by unauthorized parties.

[0110] According to the payment method of this invention, the vehicle manufacturer's server is a key link in the entire payment process. It enables the vehicle to process payment transactions. Specifically, the payee's business server encrypts the vehicle bill information using the public key provided by the vehicle manufacturer's server and sends it along with the transaction request to the vehicle manufacturer's server. This process ensures secure data transmission and prevents data from being illegally stolen or tampered with during transmission. The vehicle manufacturer's server decrypts the vehicle bill information using its own private key. This process ensures data confidentiality. Only the vehicle manufacturer's server with the corresponding private key can decrypt and obtain the bill information. Therefore, the vehicle manufacturer's server plays an important security role in the payment process, providing reliable technical support for vehicle payment transactions and enabling the vehicle to participate in payment transactions as a payment subject. This makes the vehicle a highly mobile intelligent payment acceptance terminal, not limited by fixed locations, thereby improving the convenience and efficiency of payment transactions.

[0111] In some embodiments, vehicle billing information includes vehicle identification information. Vehicle identification information may include various information that can uniquely identify the vehicle, such as license plate number and vehicle identification number (VIN). The vehicle manufacturer's server identifies the vehicle based on the vehicle identification information and responds to transaction requests when the vehicle is a registered vehicle.

[0112] Specifically, the vehicle manufacturer's server receives a data packet containing a transaction request and vehicle billing information from the vehicle. The vehicle billing information includes vehicle identification information (such as license plate number or VIN) and transaction details (transaction amount, order number, etc.). The vehicle manufacturer's server uses the corresponding private key to decrypt the vehicle billing information to obtain the original vehicle identification information.

[0113] Furthermore, the vehicle manufacturer's server can compare the extracted vehicle identification information with the registered vehicle information stored in its database. If a record matching the received vehicle identification information exists in the database, the vehicle is considered a registered vehicle.

[0114] Furthermore, after the vehicle manufacturer's server confirms that the vehicle is a registered vehicle based on the matching results, it can send a response to the payee's business server, indicating that it can process the transaction request and continue with the subsequent payment processing flow.

[0115] In some embodiments, the method for implementing payment services further includes: upon receiving transaction confirmation information sent by the vehicle, confirming that the vehicle owner's identity has been authenticated. Based on the authenticated vehicle owner information, the vehicle OEM server sends a request for a UnionPay card transaction authentication certificate to the UnionPay server. Upon receiving the request, the UnionPay server encrypts the UnionPay card transaction authentication certificate using the public key provided by the vehicle OEM server, generating ciphertext and sending it to the vehicle OEM server. Upon receiving the ciphertext containing the UnionPay card transaction authentication certificate, the vehicle OEM server decrypts the ciphertext using its own private key to obtain the UnionPay card transaction authentication certificate and the UnionPay public key. The vehicle OEM server uses the UnionPay public key to verify the received UnionPay card transaction authentication certificate, ensuring the authenticity and integrity of the certificate to prevent tampering or forgery. After successful verification, the vehicle OEM server obtains a trusted UnionPay card transaction authentication certificate. The vehicle OEM server sends the verified UnionPay card transaction authentication certificate to the vehicle. Upon receiving the UnionPay card transaction authentication certificate, the vehicle confirms its authenticity and can use it for subsequent payment operations.

[0116] Therefore, the above workflow demonstrates that secure communication between the vehicle manufacturer's server and the UnionPay server after receiving transaction confirmation information ensures the reliability and security of the UnionPay card transaction authentication certificate. Once the vehicle receives the verified UnionPay card transaction authentication certificate, it can proceed with the payment operation, ensuring the security and accuracy of the payment process.

[0117] In some embodiments, the method for implementing payment services further includes: upon receiving payment account information and UnionPay card transaction authentication certificate sent by the vehicle, encrypting the vehicle bill information, payment account information and UnionPay card transaction authentication certificate using a self-owned private key and sending them to the UnionPay server, and sending a request to the UnionPay server for bank account change information.

[0118] Specifically, when a vehicle needs to make a payment, it can send a data packet containing payment account information and a UnionPay card transaction authentication certificate to the vehicle manufacturer's server. The payment account information may include a simulated bank card CID from a mobile wallet.

[0119] Furthermore, the vehicle manufacturer's server receives the payment account information and UnionPay card transaction authentication certificate sent by the vehicle. The vehicle manufacturer's server encrypts the vehicle billing information, payment account information, and UnionPay card transaction authentication certificate using its own private key. This encrypted data is then sent to the UnionPay server, ensuring security and confidentiality during transmission.

[0120] Furthermore, the vehicle manufacturer's server simultaneously sends a request to the UnionPay server for information regarding changes in the bank account. This can include information such as the bank account status and balance to ensure the validity of the payment.

[0121] Furthermore, the UnionPay server receives encrypted data from the vehicle manufacturer's server, including vehicle billing information, payment account information, and UnionPay card transaction authentication certificate. The UnionPay server also receives a request from the vehicle manufacturer's server requesting bank account change information. The UnionPay server uses the public key provided by the vehicle manufacturer's server to decrypt the received encrypted data. After decryption, the UnionPay server obtains the original vehicle billing information, payment account information, and UnionPay card transaction authentication certificate.

[0122] Furthermore, the UnionPay server first verifies the UnionPay card transaction authentication certificate to ensure its authenticity and validity. Then, the UnionPay server verifies the legality and correctness of the payment based on the payment account information and vehicle billing information.

[0123] Furthermore, the UnionPay server generates encrypted data containing the requested bank account change information. The UnionPay server then sends this encrypted data to the vehicle manufacturer's server.

[0124] Furthermore, the vehicle manufacturer's server receives encrypted data and bank account change information from the UnionPay server. The vehicle manufacturer's server decrypts the encrypted data using its own private key to obtain the original bank account change information.

[0125] Through the above workflow, the vehicle manufacturer's server can encrypt and send the vehicle's payment account information and UnionPay card transaction authentication certificate to the UnionPay server, and process bank account change information based on the UnionPay server's response, ensuring the security and accuracy of the payment process. Simultaneously, the UnionPay server can also respond promptly to the vehicle manufacturer's server's requests, providing the necessary bank account change information, thus perfecting the entire payment process.

[0126] In some embodiments, the method for implementing payment services further includes sending bank account change information to the vehicle upon receiving such information from the UnionPay server. The vehicle can then provide the user with relevant notifications based on the received bank account change information. For example, if the bank account balance is insufficient to complete the payment, the vehicle can remind the user to top up or choose another payment method. Alternatively, if the bank account status changes, the user may need to confirm or update relevant information. In smart parking payment scenarios, bank account change information plays a crucial role. By receiving and processing this information, the vehicle manufacturer's server can promptly update the vehicle owner's account status, ensuring the accuracy and timeliness of the payment process. This mechanism allows vehicle owners to understand their bank account status, replenish funds promptly, or perform other operations, avoiding parking fee payment failures or other problems due to insufficient funds.

[0127] Therefore, through the above workflow, the vehicle manufacturer's server can exchange information with the UnionPay server, transmitting bank account change information to the vehicle, making the entire payment system more intelligent and convenient. Simultaneously, the vehicle manufacturer's server can also monitor the vehicle owner's bank account changes in real time, providing more accurate and timely data support for subsequent payments and management.

[0128] In some embodiments, the method for implementing payment services further includes sending a payment platform program initialization request or a digital key mode request to the vehicle. Specifically, when payment is required, the vehicle's OEM server sends a payment platform program initialization request to the vehicle. The purpose of this request is to put the vehicle into the initialization state of the payment platform program, preparing for subsequent payment. When the vehicle owner needs to perform digital key mode operations, the vehicle's OEM server sends a digital key mode request to the vehicle. The purpose of this request is to allow the vehicle owner to use their smartphone as a digital key to operate the vehicle, such as locking, unlocking, and starting the engine.

[0129] In some embodiments, the vehicle manufacturer's server sends a payment platform program initialization request or a digital key mode request to the vehicle. This process can be performed via the vehicle's built-in communication module, such as via wires, Bluetooth, Wi-Fi, or a mobile network.

[0130] Figure 3 This is an interactive diagram illustrating the card opening process of a mobile wallet bank card application according to an embodiment of the present invention, such as... Figure 3 As shown, users first need to activate the UnionPay bank card application in their mobile wallet as a prerequisite for payment. This means that users store their bank card information in their mobile wallet for future use in scenarios requiring payment. Specifically, the system collects security elements, which may include facial recognition information, ID card number, and the mobile phone number used to open the account at a branch, among other personal identity verification information. This information is encrypted using a Secure Element (SE) in the mobile wallet before being uploaded to the mobile wallet server. The SE is used to securely store and process sensitive information, ensuring the security of user data.

[0131] Furthermore, after receiving the encrypted security element data uploaded by the user, the mobile wallet server decrypts it, assembles it into a security element data packet, and then encrypts it again before uploading it to the UnionPay server. These security elements will be compared with the in-store card opening identity security element database on the UnionPay server to verify the consistency of the user's identity. After confirming the consistency of the user's identity information, the UnionPay server assembles the UnionPay card transaction authentication certificate (CFCA (China Financial Certification Authority) certificate), bank card CID, self-owned public key, and self-signature into data packet A, encrypts the data packet using the mobile phone manufacturer's public key, and then sends it out.

[0132] Furthermore, after receiving the encrypted data from the UnionPay server, the mobile wallet server decrypts data packet A using its own private key to obtain the UnionPay card transaction authentication certificate, bank card CID, its own public key, and self-signature. It then uses the CFCA public key for signature verification, completing the tamper-proof verification. Next, the UnionPay card transaction authentication certificate, bank card CID, and other data are re-encrypted and sent to the mobile phone's Secure Element (SE) for storage. The BC (Business Component) Applet (a Java applet) within the SE processes this data, generating a simulated bank card CID based on the bank card CID, completing the initialization and personalization of the bank card application for subsequent payment operations in the vehicle.

[0133] Figure 4 This is an interactive diagram illustrating the fulfillment of preconditions for a payment transaction according to an embodiment of the present invention, such as... Figure 4 As shown, taking the smart parking payment scenario as an example, when a user drives into a parking lot equipped with a smart parking service provider's system, the parking lot's camera can scan and obtain the vehicle's license plate information, transmit it to the payment recipient's business server for registration, record the entry time, and create the order (order number, license plate, etc.) in the background.

[0134] Furthermore, when a vehicle prepares to leave the parking lot to pay, the parking lot's cameras scan again to obtain the vehicle's license plate information and record the departure time. The system compares the departure time at the time of departure registration with the entry time at the time of entry registration to determine the vehicle's parking time. Based on the parking lot's fee schedule and the vehicle's parking time, the payment server calculates the transaction amount for this departure payment. Then, it supplements the order information (including order number, license plate number, entry time, departure time, transaction amount, etc.) and assembles it into data packet B. This data packet B can be encrypted using the public key provided by the DK (Digital Key) / CP (Collection Platform) server in the vehicle manufacturer's server to ensure the security of the transaction data. Then, this encrypted data packet is sent to the vehicle manufacturer's server, initiating a payment transaction request.

[0135] Furthermore, the vehicle manufacturer's server receives the encrypted transaction request and order data packet transmitted via a trusted relay. The trusted relay enables data relay transmission between the OEM and the payee. The OEM server decrypts the data packet using its own private key and identifies the requested vehicle based on the binding relationship between the vehicle's license plate number and vehicle identification number (VIN) in the system. After identifying the vehicle, the OEM server sends a response to the payee's business server, indicating that it can process the transaction request.

[0136] Furthermore, the receiving party's business server receives a response from the vehicle manufacturer's server and initiates a transaction confirmation notification. The service provider's app on the main unit's PAD can then display a corresponding prompt, reminding the user that there is a parking payment order pending confirmation. After the user confirms, since vehicle unlocking / locking, authorization, and cloud service account login have already been completed in the previous transaction, the identity of the vehicle owner (or temporary owner) has essentially been verified.

[0137] Furthermore, the vehicle manufacturer's server requests a UnionPay card transaction authentication certificate from the CFCA (China Financial Certification Authority) server. The UnionPay server responds to the request, assembling the UnionPay card transaction authentication certificate, the UnionPay public key, and a signature of the public key using its own private key into a data packet C. This data packet is then encrypted using the vehicle manufacturer's public key and sent to the vehicle manufacturer's server.

[0138] Furthermore, after receiving the encrypted data packet C, the vehicle manufacturer's server decrypts it using its own private key, obtaining the UnionPay card transaction authentication certificate, the UnionPay public key, and UnionPay's self-signature on the public key. Then, the vehicle manufacturer's server verifies the signature in data packet C using the UnionPay public key, completing the tamper-proof verification to ensure the integrity and authenticity of the data packet. After successful verification, the vehicle manufacturer's server sends the UnionPay card transaction authentication certificate and CP Applet initialization instructions to the payment module. The payment module receives the UnionPay card transaction authentication certificate and CP Applet initialization instructions transmitted from the vehicle manufacturer's server and completes the CP / DK Applet switching and initialization. Then, the host PAD displays that the user can now pay by swiping their mobile phone.

[0139] Figure 5 This is an interactive schematic diagram of a payment transaction process according to an embodiment of the present invention, such as... Figure 5 As shown, the user places their phone on the card-swiping area of ​​the payment module. The phone automatically pops up a wallet application, displaying the bank card information (at this time, the payment module is hosted by a CP Applet, and the CID-based anti-collision intelligent selection can identify the bank card simulation application). "CID-based anti-collision intelligent selection" refers to a mechanism used by the payment module that intelligently selects the card to communicate with by recognizing the card's CID. This mechanism prevents conflicts when multiple cards are within the reading range simultaneously, ensuring the validity and accuracy of interaction with the bank card simulation application. Then, the user's mobile wallet application performs transaction authentication with the payment module, ensuring the security and validity of the transaction.

[0140] Furthermore, the Security Element (SE) in the mobile wallet uploads data such as the bank card's CID (Card Identifier) ​​and UnionPay transaction authentication certificate to the wallet server. The wallet server assembles this data into a data packet D, encrypts it using its own private key, and then uploads it. Simultaneously, the wallet server requests order information related to the transaction (if necessary and within the cooperation framework), bank transaction information, and receipts. "If necessary and within the cooperation framework" means that when making a payment in a smart car, the system can simultaneously send requests to relevant servers within a pre-defined cooperation framework to obtain the latest order information. This ensures that users see accurate fees and order information during payment, guaranteeing a smooth transaction.

[0141] Furthermore, the payment module uploads data such as the bank card simulation card CID and UnionPay card transaction authentication certificate to the vehicle manufacturer's server. The vehicle manufacturer's server assembles the received bank card simulation card CID, UnionPay card transaction authentication certificate, and other data along with order information into a data packet E, encrypts data packet E using its own private key, and then uploads it. Simultaneously, the vehicle manufacturer's server requests bank transaction information and receipts for subsequent transaction processing and recording.

[0142] Furthermore, the CFCA server uses the public key provided by the vehicle manufacturer's server to decrypt data packet E from the vehicle manufacturer's server, and simultaneously uses the mobile phone manufacturer's public key to decrypt data packets received from the mobile wallet server. The CFCA server compares the consistency between the bank card CID and the bank card emulator CID, and confirms that both parties (the vehicle manufacturer's server and the mobile wallet) hold UnionPay card transaction authentication certificates. After successful verification, the UnionPay server is notified. The UnionPay server confirms the current subject and object identities and transaction relationship, and sends bank transaction information and transaction receipts to the vehicle manufacturer's server and the mobile wallet.

[0143] Furthermore, the CFCA server uses public keys provided by the vehicle manufacturer's server and the mobile phone manufacturer to encrypt bank transaction information and receipts before sending them out. The mobile wallet server uses its own private key to decrypt the data and then displays the transaction result to the user. In addition, the vehicle manufacturer's server also transmits the encrypted data to the smart parking service provider's payment collection server and initiates the DK Applet initialization operation.

[0144] Furthermore, the receiving party's business server uses the public key provided by the vehicle manufacturer's server to decrypt the transmitted data, obtain transaction-related information, and archive the order. Subsequently, the receiving party's business server sends the transaction result to the service provider's app for display to the user. Simultaneously, the receiving party's business server issues instructions to the parking lot's supporting terminal facilities. These instructions may include operations such as raising guardrails and displaying license plates on screens to complete the corresponding services within the parking lot.

[0145] Furthermore, the application on the host PAD can display the final transaction result, informing the user of the payment status, such as whether the payment was successful or failed. The vehicle manufacturer's server transmits the DK Applet initialization command to the payment module in the intelligent vehicle system. The SE in the payment module completes the CP / DK Applet switching operation and notifies the host PAD that the switching is complete. The application on the host PAD can prompt the user that the payment module has restored the functions related to the DK (digital key) and can conduct digital key transactions normally.

[0146] In summary, the payment service implementation method of this invention adopts a key architecture under the Public Key Infrastructure (PKI) system. This means that public and private keys are used for encryption and decryption operations in this system. These encryption algorithms are widely used in banking and vehicle networking, ensuring data security and reliability. Furthermore, the payment service implementation method also employs a two-factor authentication approach. Two-factor authentication means that identity is confirmed through two independent verification steps, typically different authentication methods or data sources. This combined use of two-factor authentication achieves a 1+1>2 effect, meaning it is more secure and reliable than single authentication. This two-factor authentication method and the adopted encryption algorithms not only meet financial-grade security requirements but may even exceed them. Financial-grade security requirements are very high because they involve the security of funds and the reliability of transactions; employing such encryption algorithms and two-factor authentication ensures the security of the payment system.

[0147] The method for implementing payment services based on the above embodiments is described below with reference to... Figure 6 An electronic device according to an embodiment of the present invention.

[0148] Figure 6 This is a block diagram of an electronic device according to an embodiment of the present invention, such as... Figure 6 As shown, the electronic device 200 includes a memory 202 and at least one processor 201.

[0149] The processor 201 can be one processor, or multiple processors such as two, three, five, eight, or ten. These processors 201 can be general-purpose processors or dedicated chips, depending on the design and purpose of the electronic device 200. The processor 201 is responsible for processing transaction requests and billing information sent by the vehicle, communicating with the vehicle manufacturer's server and the payee's business server, and performing payment processing. Through the execution of the processor 201, the vehicle can perform various payment-related operations, such as confirming transactions, requesting bank card transaction authentication certificates, and processing digital key information.

[0150] In some embodiments, memory 202 may be used to store computer programs and other necessary data. This memory 202 may include RAM (Random Access Memory) and ROM (Read-Only Memory), etc. The computer program is stored in memory 202, awaiting execution by processor 201.

[0151] In some embodiments, the memory 202 is communicatively connected to at least one processor 201, and the memory 202 stores a computer program that can be executed by at least one processor 201. When the at least one processor 201 executes the computer program, it implements the method for implementing payment services as described in the above embodiments.

[0152] According to the embodiment of the present invention, the electronic device 200 realizes the function of a vehicle as a payment subject by adopting the payment business method described in the above embodiment, making the vehicle a highly mobile intelligent payment acceptance terminal that is not restricted by a fixed location, thereby improving the convenience and efficiency of payment business.

[0153] This invention also proposes a non-volatile readable storage medium storing a computer program. When the computer program is executed, it implements the payment service method described in the above embodiments. The specific implementation process of the payment service method can be referred to the description in the above embodiments.

[0154] In some embodiments, the non-volatile readable storage medium can be, for example, a disk, solid-state drive, CD-ROM, DVD-ROM, flash drive, etc., which have the characteristic of non-volatility, meaning that data will not be lost due to power outages or device shutdown. The computer program in the non-volatile readable storage medium can be the software code of an intelligent vehicle payment system, including transaction processing programs, encryption / decryption algorithms, programs for communicating with the vehicle manufacturer's server and the payee's business server, etc. The execution of these computer programs enables the intelligent vehicle to receive transaction requests, send vehicle billing information, and perform payment processing, etc.

[0155] According to the embodiments of the present invention, the non-volatile readable storage medium, by adopting the payment business implementation method described in the above embodiments, realizes the function of vehicles participating in payment business as payment subjects, making vehicles a highly mobile intelligent payment acceptance terminal, not restricted by fixed locations, thereby improving the convenience and efficiency of payment business.

[0156] The following is for reference. Figure 7 A vehicle described in an embodiment of the present invention.

[0157] Figure 7 This is a block diagram of a vehicle according to an embodiment of the present invention, such as... Figure 7 As shown, vehicle 100 includes: communication module 1, display module 2 and payment module 3.

[0158] In some embodiments, vehicle 100 may be a vehicle with smart payment functionality, such as a smart car or other types of vehicle. This vehicle 100 possesses certain intelligence and communication capabilities, enabling it to communicate with the payee's business server and the vehicle manufacturer's server, and to display payment information to the user.

[0159] In some embodiments, the communication module 1 on the vehicle 100 is used to communicate with the payee's business server and the vehicle manufacturer's server, respectively. This communication can be conducted via wireless networks (such as 4G, 5G) or Bluetooth. The communication module 1 is responsible for receiving and sending transaction requests, vehicle billing information, authentication information, etc.

[0160] In some embodiments, the display module 2 can be a display screen on the vehicle's dashboard or a central control screen. The display module 2 is used to display payment-related information to the vehicle owner, such as transaction amount, payment status, and transaction confirmation prompts. When the user is required to perform a payment operation, the display module 2 can remind the user.

[0161] In some embodiments, the payment module 3 is connected to the display module 2 and the communication module 1 respectively, and is used to execute the payment service method described in the above embodiments. When the user confirms the payment, the payment module 3 can process the transaction request, perform the payment operation, and communicate with the payee's business server, the vehicle OEM server, etc., to complete the entire payment process.

[0162] According to an embodiment of the present invention, in the vehicle 100, the payment module 3 is connected to the display module 2 and the communication module 1 respectively, and is used to execute the payment business method described in the above embodiment. Through the payment module 3, the vehicle 100 can process payments according to the transaction request and vehicle bill information sent by the payee's business server. The payment module 3 is responsible for executing payment instructions and exchanging data with the payee's business server and the vehicle OEM server to ensure the smooth progress of the payment process. These components together constitute the payment system of the intelligent vehicle, realizing the function of the vehicle 100 as a payment subject to participate in payment business, making the vehicle 100 a highly mobile intelligent payment acceptance terminal, not restricted by fixed locations, thereby improving the convenience and efficiency of payment business.

[0163] In some embodiments, vehicle 100 includes a tray for placing a user terminal. The tray may be located on the center console, dashboard, center armrest, or other similar locations within vehicle 100. The tray can accommodate and secure the user's mobile device, such as a smartphone or tablet. The tray is designed to provide a convenient location for users to easily place and retrieve their devices.

[0164] In some embodiments, the payment module 3 includes a Near Field Communication (NFC) module 30, which is located on a tray, i.e., tNFC (tray NFC). The function of the NFC module 30 is to enable end-to-end payment methods and payment experience. Specifically, the NFC module 30 can interact with the NFC function of the user terminal. Users can establish a connection between their mobile phone or other NFC devices and the NFC module 30 in the vehicle 100 by placing them on the tray, thus enabling fast and secure payment transactions.

[0165] like Figure 8 As shown, the near-field communication module 30 includes a sensing unit 31, a security unit 32, and a control unit 33. The sensing unit 31 is a crucial component of the near-field communication module 30, used to sense payment account information provided by the user terminal. When a user places a smartphone or other NFC device on the vehicle tray, the sensing unit 31 can identify and obtain the payment account information provided by the user terminal, including bank card information, digital wallet information, etc.

[0166] In some embodiments, the security unit 32 is a key component of the near-field communication module 30. The security unit 32 may include encryption / decryption functions, security protocol implementations, etc., for encrypting, decrypting, and securely storing transmitted payment data. Furthermore, the security unit 32 can also be used to switch the operating modes of the near-field communication module 30, ensuring the security and data integrity of the near-field communication module 30 in different operating modes.

[0167] In some embodiments, the control unit 33 is the core of the entire near-field communication module 30. It is connected to the sensing unit 31 and the security unit 32 respectively, and is responsible for controlling the operation of these two units. The control unit 33 is responsible for coordinating the communication and workflow between the sensing unit 31 and the security unit 32. It receives the payment account information acquired by the sensing unit 31 and transmits it to the security unit 32 for encryption. At the same time, the control unit 33 can also receive encrypted data from the security unit 32 and switch operating modes as needed to complete the payment operation.

[0168] Figure 9 This is a topology diagram of tNFC payment acceptance according to an embodiment of the present invention, such as... Figure 9 As shown, Figure 1The tNFC payment acceptance topology was demonstrated. The host + PAD on vehicle 100 is interconnected with the BCM (Body Control Module) + IKEY (a cryptographic data transceiver controller integrated in the domain controller), the host + PAD is interconnected with the tNCM (tray near-field communication control module) + SE, the BCM + IKEY is interconnected with the aNCM (external near-field communication control module) + SE, and the BCM + IKEY is interconnected with the tNCM + SE. Simultaneously, the host + PAD is interconnected with the vehicle manufacturer's server, the vehicle manufacturer's server is mutually trusted with the mobile wallet server, the tNCM + SE is interconnected with the mobile wallet server, the mobile wallet server is interconnected with the UnionPay server (trusted relay), and the UnionPay server is interconnected with the payee's business server and the vehicle manufacturer's server (trusted relay).

[0169] In this topology, the host + PAD on vehicle 100 plays a core role, communicating and exchanging data with various modules within vehicle 100 (BCM, IKEY, tNCM) and external devices such as the vehicle manufacturer's server, mobile wallet server, UnionPay server, and payee's business server. When the vehicle owner needs to make a payment, the host + PAD communicates with the mobile wallet on the vehicle owner's smartphone via tNCM + SE, sending the payment request and vehicle billing information to the mobile wallet server. Upon receiving the request, the mobile wallet server establishes a connection with the UnionPay server to obtain and verify the UnionPay card transaction authentication certificate. The UnionPay server, acting as a trusted relay, exchanges data and confirms payments with the payee's business server and the vehicle manufacturer's server, ensuring payment security and accuracy. Simultaneously, the modules within vehicle 100 (BCM, IKEY, tNCM) are responsible for data encryption and secure transmission, ensuring data security during the payment process.

[0170] In summary, this tNFC payment acceptance topology achieves secure, efficient, and reliable vehicle payments through complex connections between the vehicle's internal host + PAD and various control modules, and external OEM servers, mobile wallet servers, UnionPay servers, and payee business servers. Vehicle owners simply place their smartphones on the vehicle's tray and complete the payment via near-field communication technology, eliminating the need for physical bank cards or PINs, thus improving convenience and security. The entire payment process undergoes multiple layers of encryption and verification, ensuring user privacy and the security of payment information, while also providing a convenient payment experience for both vehicle owners and payees.

[0171] Figure 10 This is a schematic diagram of the tNFC payment acceptance system architecture according to an embodiment of the present invention, as shown below. Figure 10 As shown, Figure 10The architecture of a tNFC payment acceptance system is demonstrated, which includes a vehicle module, a vehicle owner device module, a vehicle owner device OEM server module, a vehicle OEM server module, and an NFC server module.

[0172] In this system, the vehicle modules include the BCM (Body Control Module), the main unit PAD, aNFC (Access NFC, external near-field communication), and tNFC (Tray NFC). The BCM includes the IKEY, tNFC includes the NCM (Near-Field Communication Control Module), aNFC includes the NCM and SE, and the SE includes the DK (Digital Key) Applet. These modules are responsible for communication and data processing within the vehicle 100, with the BCM handling body control, tNFC handling near-field communication control, and aNFC handling access control and security element management.

[0173] The vehicle owner device module includes a mobile wallet, SE (Secure Device), DK (Digital Key) frame, OEM (Original Equipment Manufacturer) app, and NFC module. SE includes a BC (Bank Card) applet and a DK (Digital Key) applet. The BC applet communicates with the mobile wallet, and the DK applet is used for digital key functionality. The DK frame interconnects with the mobile wallet, DK applet, and NFC module. The NFC module interconnects with the vehicle module's aNFC (Access NFC, external near-field communication) and tNFC (Tray NFC, tray near-field communication). These modules are responsible for the management and security functions of the vehicle owner device, including payment authorization, digital key functionality, and communication with the vehicle.

[0174] The vehicle owner device OEM server module includes a CA (Certificate Authority) management module, SEI-TSM (SE Issuer Trusted Service Management) for DK, and SEI-TSM for BC, responsible for certificate management and security element service management of the vehicle owner device. The vehicle OEM server module includes a TSP (Telematics Service Platform) module, providing smart parking application services and pre-installed application management systems, and interconnects with the vehicle owner device OEM server and vehicle module to achieve comprehensive vehicle management and application services. In this embodiment, the TSP can access specific payment items and products from cooperating payment recipients, such as smart parking applications and services. Thus, in smart parking payment scenarios involving this payment recipient, users can complete payments via in-vehicle payment, with the OEM providing payment reminders and security verification services throughout the process.

[0175] The NFC (Near Field Communication) server module includes DK (Digital Key) management and services and CP (Content Provider) management and services. DK management and services include CA (Certificate Authority) management, SP-TSM (Application Provider Trusted Service Management), and DK management. CP management and services include CA management, SP-TSM, and CP management. These modules are responsible for handling the management services of the payment and collection platform, interconnecting with UnionPay servers, vehicle owner device OEM servers, and vehicle modules to achieve payment transactions and secure authentication.

[0176] In general, Figure 10 The demonstrated tNFC payment acceptance system architecture is a complex interconnected network. Through the connection and communication between various modules, it enables secure payment and digital key functions between vehicle 100 and the owner's device. The owner controls vehicle 100 via mobile wallet and digital key, performing payment and authorization operations. Vehicle 100 interconnects with the owner's device and payment platform through BCM, tNFC, and aNFC modules, enabling convenient and secure payment and vehicle management functions. The owner's device OEM server and NFC server provide certificate management and security services, ensuring the security and reliability of the payment process. The entire system employs multi-layered encryption and authentication to ensure the security of payment information and user privacy.

[0177] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example.

[0178] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

Claims

1. A method for implementing payment services, characterized in that, For use in a vehicle, the method includes: Upon receiving a transaction request and vehicle billing information from the payee's business server, the transaction request and vehicle billing information are sent to the vehicle manufacturer's server. Payment is processed based on feedback information from the vehicle manufacturer's server and the payee's business server.

2. The method according to claim 1, characterized in that, The feedback information from the payee's business server includes a transaction confirmation reminder message. This message is sent by the payee's business server when it receives a response from the vehicle manufacturer's server to the transaction request. The vehicle manufacturer's server responds to the transaction request after identifying the vehicle as a registered vehicle based on the vehicle billing information. The payment processing includes prompting the user to confirm the transaction and, in response to the user's confirmation instruction, sending transaction confirmation information to the vehicle manufacturer's server.

3. The method according to claim 2, characterized in that, The feedback information from the vehicle manufacturer's server includes a UnionPay card transaction authentication certificate, which is obtained by the vehicle manufacturer's server in response to the transaction confirmation information by sending a certificate request to the UnionPay server. The payment processing includes prompting the user to perform a payment operation.

4. The method according to claim 3, characterized in that, The method further includes: Before the user makes a payment, the system switches to the payment platform-hosted business mode in response to the payment platform program initialization request.

5. The method according to claim 3, characterized in that, The method further includes: Obtain payment account information from the user's terminal; The payment account information and the UnionPay card transaction authentication certificate are sent to the vehicle manufacturer's server.

6. The method according to claim 5, characterized in that, The method further includes: The feedback information from the vehicle manufacturer's server also includes bank account change information; The payment processing also includes sending the bank account change information to the payee's business server.

7. The method according to claim 6, characterized in that, The feedback information from the payee's business server also includes a transaction completion signal, which is a signal fed back by the payee's business server based on the bank account change information. The payment processing also includes displaying the transaction result.

8. The method according to claim 4, characterized in that, The method further includes: In response to a request to switch from the payment platform's hosted business mode to the digital key mode, the system prompts the user.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Obtain the vehicle owner's identity information and authenticate the vehicle owner's identity based on the vehicle owner's identity information.

10. The method according to claim 9, characterized in that, The vehicle owner's identity information includes at least one of the following: vehicle owner's digital key information and vehicle owner's cloud service account information.

11. The method according to claim 10, characterized in that, Authentication of the vehicle owner's identity based on the vehicle owner's identity information includes at least one of the following: The vehicle can be unlocked or locked based on the owner's digital key information; Obtain vehicle engine start authorization based on the owner's digital key information; The owner's digital key information is obtained based on the owner's cloud service account information.

12. A method for implementing payment services, characterized in that, For use with vehicle OEM servers, the method includes: The system receives a transaction request and vehicle billing information from the vehicle. The vehicle billing information is encrypted by the payee's business server using the public key provided by the vehicle's OEM server. The vehicle billing information is decrypted using the self-owned private key.

13. The method according to claim 12, characterized in that, The vehicle billing information includes vehicle identification information; The vehicle manufacturer's server identifies the vehicle based on the vehicle's identity information and responds to the transaction request when the vehicle is a registered vehicle.

14. The method according to claim 12, characterized in that, The method further includes: Upon receiving the transaction confirmation information from the vehicle, the system confirms that the vehicle owner's identity has been verified and sends a request for a UnionPay card transaction authentication certificate to the UnionPay server. Obtain the ciphertext containing the UnionPay card transaction authentication certificate, decrypt the ciphertext using your own private key to obtain the UnionPay card transaction authentication certificate and the UnionPay public key, and verify the signature using the UnionPay public key; Send the UnionPay card transaction authentication certificate to the vehicle.

15. The method according to claim 12, characterized in that, The method further includes: Upon receiving the payment account information and UnionPay card transaction authentication certificate sent by the vehicle, the system encrypts the vehicle billing information, the payment account information, and the UnionPay card transaction authentication certificate using its own private key and sends them to the UnionPay server, and also sends a request to the UnionPay server for bank account change information.

16. The method according to claim 15, characterized in that, The method further includes: Upon receiving bank account change information from the UnionPay server, the information is sent to the vehicle.

17. The method according to any one of claims 12-16, characterized in that, The method further includes sending a payment platform program initialization request or a digital key mode request to the vehicle.

18. An electronic device, characterized in that, include: At least one processor; A memory that is communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor. When the at least one processor executes the computer program, it implements the method for implementing payment services as described in any one of claims 1-11 or the method for implementing payment services as described in any one of claims 12-17.

19. A non-volatile readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed, it implements the method for implementing payment services as described in any one of claims 1-11 or the method for implementing payment services as described in any one of claims 12-17.

20. A vehicle, characterized in that, include: The communication module is used to communicate with the payee's business server and the vehicle manufacturer's server, respectively. The display module is used to prompt users for payment information; The payment module is connected to the display module and the communication module respectively, and is used to execute the method for implementing payment business as described in any one of claims 1-11.

21. The vehicle according to claim 20, characterized in that, The vehicle includes a tray for placing user terminals; The payment module includes a near-field communication module, which is located on the tray.

22. The vehicle according to claim 21, characterized in that, The near-field communication module includes: The sensing unit is used to sense the payment account information provided by the user terminal; A security unit is used for data encryption / decryption, secure storage, and switching of the operating mode of the near-field communication module; A control unit, connected to the sensing unit and the safety unit respectively, is used to control the sensing unit and the safety unit.

Images