Vehicle payment method, vehicle, mobile terminal, server, system, and medium

By using a collaborative parking payment method involving vehicles and mobile terminals, the vehicle obtains payment information before parking and displays it on the in-vehicle screen. Users complete the payment on the vehicle or mobile terminal, solving the problem of cumbersome payment in existing technologies and improving payment convenience and driving smoothness.

WO2026232809A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/142923
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2025-12-16
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The current parking payment methods in public parking lots are cumbersome, which disrupts the user's smooth travel experience and payment experience. In particular, when paying by scanning a QR code with a mobile phone, users need to manually operate the QR code, which affects the smoothness of travel.

Method used

Parking payment is made through collaboration between vehicles and mobile terminals. Before parking, the vehicle retrieves payment information from the cloud server and displays it on the in-vehicle screen. Users can complete the payment on either the vehicle or their mobile terminal, simplifying the payment process and completing the payment before leaving the parking lot.

Benefits of technology

It improves the convenience of payment and the smoothness of driving, reduces congestion in parking lots, and allows users to perceive the payment amount and payment process without the need for cumbersome scanning operations, thus enhancing the parking payment experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025142923_12112026_PF_FP_ABST
    Figure CN2025142923_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and specifically relates to a vehicle payment method, a vehicle, a mobile terminal, a server, a system, and a medium. Parking payment is performed by means of the cooperation between the vehicle and the mobile terminal, thereby improving the convenience and speed of payment, and improving the smoothness of driving when the vehicle leaves a parking lot. Specifically, in a scenario in which a vehicle is parked in a parking lot, the mobile terminal associated with the vehicle may obtain updated fee information of the vehicle from a cloud server, and a user may choose whether to pay the parking fee of the vehicle in advance at the mobile terminal side on the basis of the updated fee information. Furthermore, before the user drives the vehicle out of the parking lot, the vehicle may obtain the payment information of the vehicle from the cloud server. If the user does not pay the parking fee of the vehicle at the mobile terminal side, the payment information obtained by the vehicle comprises a pending payment order of the vehicle, and then the user may pay the parking fee of the vehicle at the vehicle side on the basis of the pending payment order.
Need to check novelty before this filing date? Find Prior Art

Description

Vehicle payment methods, vehicles, mobile terminals, servers, systems, and media

[0001] This application claims priority to Chinese patent application filed on May 8, 2025, with application number 202510591868.1 and title "Vehicle Payment Method, Vehicle, Mobile Terminal, Server, System and Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to the field of communication technology, specifically to a vehicle payment method, a vehicle, a mobile terminal, a server, a system, and a medium. Background Technology

[0003] Currently, users primarily pay parking fees in public parking lots via mobile phone QR code payment and contactless payment. Firstly, in the mobile QR code payment scenario, users need to scan a QR code with their mobile phone before leaving the parking lot, either in advance or at the exit, before they can pass. This process typically involves finding the QR code, parking, adjusting the car window, and aligning the phone's scanner with the QR code to make the payment. This process is rather cumbersome and disrupts the smooth travel experience.

[0004] Therefore, in the current parking payment scenario, how to balance the user's smooth driving experience and payment experience has become a problem that needs to be solved. Summary of the Invention

[0005] This application provides a vehicle payment method, vehicle, mobile terminal, server, system, and medium, which improves the convenience and speed of payment and enhances the smoothness of driving when leaving the parking lot by using a vehicle and mobile terminal in a collaborative manner.

[0006] In a first aspect, this application provides a vehicle payment method applied to a vehicle, the vehicle including an in-vehicle screen, the method comprising: before the vehicle leaves the parking lot, obtaining the vehicle's payment information from a first cloud server, the payment information including the vehicle's paid information or a first pending payment order for the vehicle; displaying a first prompt message on the in-vehicle screen, the first prompt message indicating the payment information; and corresponding to the payment information including the first pending payment order, paying the parking fee in the first pending payment order.

[0007] Therefore, users can pay the parking fee for their vehicle directly at the vehicle's location based on the first pending payment order. For example, they can pay the parking fee before or upon entering the vehicle. In this way, users do not need to go through cumbersome processes such as searching for and scanning QR codes during the vehicle payment process, and can intuitively confirm the parking fee amount, resulting in a better parking payment experience. Furthermore, since the parking fee can be paid before the vehicle leaves the parking lot—that is, before the vehicle reaches the exit gate—the user experiences a smoother driving experience from starting the vehicle to leaving the parking lot, which helps alleviate or even avoid traffic congestion in the parking lot.

[0008] In one possible implementation of the first aspect above, obtaining vehicle payment information from the first cloud server includes: after the vehicle enters the parking lot, if a user is detected inside the vehicle within a first time, sending a second message to the first cloud server, the second message being used to obtain vehicle payment information; obtaining vehicle payment information from the first cloud server, wherein the payment information is the vehicle's first fee information, the first fee information including a first pending payment order.

[0009] For example, a user drives their vehicle into a parking lot and parks it, but the vehicle's power is cut off without the user getting out. After the power is off, the mobile terminal associated with the vehicle can obtain the vehicle's overdue parking fee information and pending payment orders, allowing the user to view the overdue fee information and pay the parking fees in the pending orders on their mobile device. Then, after the vehicle is powered back on, it can retrieve its payment information from the cloud server, such as paid fees or pending payment orders. Therefore, even if the user doesn't pay the parking fee on their mobile device, they can still pay the parking fees in the pending orders on the vehicle's device. It's understandable that when the vehicle is powered off, the user will typically use their mobile device, making it more convenient to pay on the mobile device. When the vehicle is powered back on, the user will generally prefer to use the in-vehicle system, making it more in line with user habits and more convenient to pay on the vehicle's device.

[0010] The second message is used to notify the first cloud server (e.g., cloud server 30A or 30B) that the vehicle's distribution service has been activated, and the vehicle and the first cloud server communicate based on the distribution service.

[0011] In one possible implementation of the first aspect above, obtaining vehicle payment information from the first cloud server includes: after the vehicle enters the parking lot, detecting the user getting off the vehicle and controlling the vehicle to power off; after the vehicle is in the parking lot for a second time, detecting the user getting on the vehicle, controlling the vehicle to power on, and sending a first message to the first cloud server, the first message being used to obtain vehicle payment information; the first cloud server receiving the payment information, wherein the first message is used to instruct the first cloud server to send payment information to the vehicle.

[0012] For example, when the vehicle is within a designated geographical area of ​​the parking lot, during or after the vehicle is powered on, the vehicle sends a first message to a first cloud server (e.g., cloud server 30A or 30B). The first message instructs the first cloud server to send payment information to the vehicle.

[0013] In one possible implementation of the first aspect above, the user getting on and getting off the vehicle is determined based on changes in the vehicle's status information, which includes at least one of the following: the vehicle's location, the vehicle's operating status, the vehicle's door opening / closing status, and the vehicle's seat occupancy status.

[0014] For example, if the vehicle's status information meets the first condition, it indicates that the user has alighted from the vehicle. For example, the first condition may include: the vehicle's operating status is parked, the vehicle's door opening / closing status is closed, and the vehicle's seat status is that the user is not in the vehicle.

[0015] For example, if the vehicle's status information meets the second condition, it indicates that the user has boarded the vehicle. The second condition may include at least one of the following: the vehicle's operating status is parked or in a parked state; the vehicle's door opening / closing status is closed; or the vehicle's seat status is that the user is in a seated state.

[0016] In one possible implementation of the first aspect above, the method further includes: when a vehicle enters the parking lot, obtaining the vehicle's entry information from a second cloud server and displaying a second prompt on the vehicle screen, the second prompt being used to indicate the entry information, wherein the entry information includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules; and determining that the vehicle has entered the parking lot based on the entry information.

[0017] For example, some parking lot fees are as follows: 15 yuan per hour of parking time, with an additional 5 yuan for any increase in parking time less than one hour. Other fees are: 2 yuan for 0-15 minutes, 4 yuan for 15-30 minutes, 7 yuan for 30-60 minutes, and an additional 4 yuan for every 30 minutes thereafter. Still others fees are: a minimum of 30 minutes of free parking; if the free period exceeds one hour but is less than one hour, it is charged as one hour; any time exceeding one hour is charged in 15-minute increments, with any period less than 15 minutes counted as one cycle.

[0018] In one possible implementation of the first aspect above, the basic information of the vehicle and the vehicle's entry time in the entry information are obtained by interaction between the second cloud server and the parking lot server, and the parking lot server is associated with the parking lot; wherein, the first cloud server is the same as the second cloud server, or the first cloud server includes the second cloud server and the parking lot server.

[0019] It is understandable that when a vehicle enters the parking lot, the first cloud server (such as cloud server 30A) or the second cloud server (such as cloud server 30B) can obtain the vehicle's entry information and send the entry information to the vehicle when the vehicle is online (i.e., the vehicle's distribution service is enabled).

[0020] In one possible implementation of the first aspect above, the method further includes: detecting that the vehicle's location has entered a set geographical area of ​​the parking lot, activating the vehicle distribution service, and sending a second message to a first cloud server, wherein the second message is used to notify the first cloud server that the vehicle distribution service has been activated; obtaining the vehicle's payment information from the first cloud server includes: obtaining the vehicle's payment information from the first cloud server based on the distribution service.

[0021] The defined geographical range of the parking lot can be the area around the parking lot; for shopping mall parking lots, it includes the location of the parking lot's road entrance. For example, when a vehicle is within the defined geographical range of the parking lot, during or after the vehicle is powered on, the vehicle can initiate a distribution service and send a first message to a first cloud server (e.g., cloud server 30A or 30B).

[0022] In one possible implementation of the first aspect above, the vehicle is equipped with an in-vehicle payment application to pay the parking fee in the first pending payment order, including: paying the parking fee in the first pending payment order based on the in-vehicle payment application.

[0023] For example, in-vehicle payment applications can be the vehicle's system wallet or a third-party payment application. In this case, the vehicle has payment capabilities, eliminating the need for a mobile phone; users can complete parking fee payments solely through the vehicle.

[0024] In one possible implementation of the first aspect above, the in-vehicle payment application uses a target authentication method to pay the parking fee in the first pending payment order, wherein the target authentication method includes at least one of the following: digital password authentication, image password authentication, and facial image authentication.

[0025] In this way, users can pay parking fees directly at the vehicle without using their mobile phones to scan a QR code; they can complete the payment with a single click. They can also see the parking fee amount and the payment process, thus improving the user's payment experience.

[0026] In one possible implementation of the first aspect mentioned above, an in-vehicle camera is installed on the inside of the A-pillar of the vehicle. This camera is used to capture the user's facial image, and facial image authentication is used to authenticate the facial image captured by the in-vehicle camera. In this case, the user only needs to have their face facing the camera on the A-pillar to complete the authentication, thus completing the parking fee payment conveniently and with good privacy.

[0027] In one possible implementation of the first aspect described above, payment for a first pending payment order based on an in-vehicle payment application includes: receiving a first operation from a user on a first prompt displayed on the in-vehicle screen; responding to the first operation, displaying information about the first pending payment order on the in-vehicle screen; responding to a second operation from the user on the first pending payment order, sending a first payment request message to a payment server using the in-vehicle payment application, the first payment request message being used to request payment for the first pending payment order, the payment server being the same as or different from a first cloud server; receiving a first payment response message from the payment server, the first payment response message indicating that the parking fee in the first pending payment order has been successfully paid; and displaying a third prompt on the in-vehicle screen based on the first payment response message, the third prompt message indicating that the parking fee in the first pending payment order has been successfully paid. This allows users to conveniently pay with a single click in their vehicle and perceive the payment amount and payment confirmation process.

[0028] In one possible implementation of the first aspect described above, the method further includes: if the payment information includes the vehicle's paid information, receiving a fourth operation from the user on the first prompt information displayed on the in-vehicle screen; in response to the fourth operation, displaying the paid information on the in-vehicle screen, the paid information including the vehicle's paid departure time and the amount of the parking fee, wherein the parking fee was paid by a mobile terminal associated with the vehicle. This facilitates timely departure for the user.

[0029] In one possible implementation of the first aspect described above, displaying the first prompt information on the vehicle screen includes: using the vehicle's distribution service to display the first prompt information on the vehicle screen via a live view window.

[0030] This application enables vehicle payment via collaboration between the vehicle and a mobile terminal, such as a smartphone. After a user boards the vehicle, they can pay the parking fee directly on the vehicle's screen. Specifically, upon boarding, the vehicle displays a notification for the first pending payment order, allowing the user to quickly and conveniently pay before leaving the parking lot. Furthermore, no specific parking application needs to be installed on the vehicle; instead, a distribution server can display real-time information related to the payment task (such as entry and exit) in a live window, providing users with timely and convenient access to this information. This approach also places low demands on the vehicle's storage and computing resources.

[0031] In one possible implementation of the first aspect described above, displaying the second notification information on the in-vehicle screen includes: using the vehicle's distribution service to display the second notification information via a live view window on the in-vehicle screen. This facilitates the user's confirmation that the vehicle has arrived.

[0032] In one possible implementation of the first aspect described above, displaying the third prompt information on the in-vehicle screen includes: using the vehicle's distribution service to display the third prompt information via a real-time window on the in-vehicle screen. This allows users to conveniently obtain information such as vehicle payment status and the amount paid.

[0033] In one possible implementation of the first aspect mentioned above, the method further includes: detecting that the vehicle has left the parking lot, using the vehicle's distribution service, canceling the display of the live view window on the in-vehicle screen, and closing the vehicle's distribution service. This helps reduce the resource requirements on the vehicle, such as storage and computing power.

[0034] In one possible implementation of the first aspect described above, detecting a vehicle leaving the parking lot includes: when the vehicle leaves the parking lot, if departure information is received from a second cloud server, or if the vehicle's location is detected to have left a set geographical area of ​​the parking lot, then the vehicle is confirmed to have left the parking lot. The departure information includes the vehicle's basic information, the vehicle's departure time, and the parking fee amount. This allows users to promptly obtain information that their vehicle has successfully left the parking lot.

[0035] In one possible implementation of the first aspect described above, departure information is obtained through interaction between a second cloud server and a parking lot server, the parking lot server being associated with a parking lot; wherein the first cloud server and the second cloud server are the same, or the first cloud server includes both the second cloud server and the parking lot server. For example, the second cloud server can be cloud server 30B.

[0036] Secondly, this application provides a vehicle payment method applied to a mobile terminal, the mobile terminal including a terminal screen. The method includes: before the vehicle associated with the mobile terminal leaves the parking lot, when the distance between the mobile terminal and the vehicle is less than or equal to a set distance, the mobile terminal obtains target fee jump information for the vehicle's parking in the parking lot from a first cloud server; and displays a first target prompt information on the terminal screen, wherein the first target prompt information is used to indicate the target fee jump information. For example, the first cloud server (such as cloud server 30A or 30B) generates target fee jump information for the vehicle and sends the target fee jump information to the mobile phone when the vehicle's parking duration meets the jump condition and the distance between the terminal device, such as a mobile phone, and the vehicle is less than or equal to a set distance (such as 1 kilometer or 2 kilometers). Thus, this application can perform vehicle payment through the collaboration of the vehicle and the mobile terminal, such as a mobile phone, allowing the user to pay the parking fee in advance on the mobile phone before getting into the car. Specifically, after the user gets out of the car, the mobile phone can display a prompt information corresponding to the vehicle's fee jump information, so that the user can quickly and conveniently know that the parking fee is about to jump before leaving the parking lot.

[0037] In one possible implementation of the second aspect above, the method further includes: when a vehicle enters a parking lot, the mobile terminal is connected to the vehicle; when a user gets off the vehicle, the mobile terminal is detected to be disconnected from the vehicle, the mobile terminal's distribution service is activated, and a first target message is sent to a first cloud server, wherein the first target message is used to notify the first cloud server that the mobile terminal's distribution service has been activated; the mobile terminal obtains parking fee information of the vehicle in the parking lot from the first cloud server, including: the mobile terminal obtains the target fee information of the vehicle in the parking lot from the first cloud server through the distribution service.

[0038] In some embodiments, if the parking duration meets the jump condition, it indicates that the parking fee is about to jump. For example, the jump condition is whether the parking duration will reach the jump time after 10 minutes. It can be understood that the jump time in the jump condition is related to the parking lot's billing rules. For example, if the billing rule for the parking lot is 15 yuan per hour, with an additional 5 yuan for each hour of parking time increase, the jump time could be 1 hour, 1.5 hours, 2 hours, 2.5 hours, etc. As an example, if vehicle 10's parking duration is 50 minutes, and the parking duration is 10 minutes away from the jump time of 1 hour, the parking fee will increase by 5 yuan on top of the 15 yuan for 10 minutes. In this case, the target jump fee information for vehicle 10 indicates that the parking duration is 50 minutes, and the parking fee will increase by 5 yuan after 10 minutes.

[0039] In one possible implementation of the second aspect above, the toll information includes a target toll order for the vehicle, and a target payment application is installed on the mobile terminal. The method further includes: the mobile terminal receiving a first target operation from the user on the first target prompt information; in response to the first target operation, the mobile terminal displaying information about the target toll order on the terminal screen; the mobile terminal receiving a second target operation from the user on the target toll order; and in response to the second target operation, the mobile terminal using the target payment application to pay the parking fee in the target toll order.

[0040] In this way, when users pay parking fees on mobile devices such as their phones, they can still perceive the parking fee amount and payment process without scanning a code, which helps improve the user's payment experience.

[0041] In one possible implementation of the second aspect above, the mobile terminal uses a target payment application to pay for the first target pending payment order, including: the mobile terminal using the target payment application to send a target payment request message to the payment server, the target payment request message being used to request payment for the target pending payment order; the mobile terminal receiving a target payment response message sent by the payment server, the target payment response message being used to indicate that the parking fee in the target pending payment order has been successfully paid; and the mobile terminal displaying a second target prompt message on the terminal screen according to the target payment response message, the second target prompt message being used to indicate that the parking fee in the target pending payment order has been successfully paid.

[0042] In one possible implementation of the second aspect above, displaying the first target prompt information on the terminal screen includes: using the distribution service of the mobile terminal to display the first target prompt information on the terminal screen through a live window.

[0043] In this way, mobile terminals, such as mobile phones, do not need to install specific parking applications. Instead, the distribution server can call the real-time window to display real-time information related to the vehicle payment task (such as entry, payment skipping, and exit), which makes it convenient for users to obtain this real-time information in a timely and convenient manner. Moreover, the requirements for storage resources, computing power resources, and other resources of vehicles and mobile phones are relatively low.

[0044] In one possible implementation of the second aspect described above, displaying the second target notification information on the terminal screen includes: using a mobile terminal's distribution service to display the second target notification information on the terminal screen via a live window. This allows users to promptly obtain information that their vehicle payment has been received.

[0045] In one possible implementation of the second aspect described above, the method further includes: disabling the mobile terminal's distribution service when the distance between the mobile terminal and the vehicle exceeds a set distance. This helps reduce the resource requirements of the mobile terminal, such as storage and computing power.

[0046] Thirdly, this application provides a vehicle payment method applied to a cloud server. The method includes: obtaining vehicle payment information before the vehicle leaves the parking lot, the payment information including the vehicle's paid information or the vehicle's first pending payment order, wherein the parking fee is paid by a mobile terminal associated with the vehicle or by the vehicle itself; and sending the payment information to the vehicle. For example, the cloud server can be cloud server 30 as described below. Thus, a user can pay for the vehicle on the vehicle side or the mobile terminal side before driving the vehicle away from the parking lot. For example, the user can pay the parking fee before or when getting into the vehicle.

[0047] In one possible implementation of the third aspect described above, obtaining vehicle payment information includes: if the vehicle's parking fee is unpaid, obtaining the vehicle's first pending payment order from the parking lot server and generating payment information based on the first pending payment order; or, if the vehicle's parking fee has been paid, obtaining paid information and generating payment information based on the paid information. Thus, this method provides a distributed parking payment solution through a collaborative approach between the vehicle and the mobile terminal.

[0048] In one possible implementation of the third aspect above, obtaining paid information includes: generating paid information based on the vehicle's target pending payment order, wherein the parking fee in the target pending payment order has been paid by the mobile terminal.

[0049] In one possible implementation of the third aspect above, the method further includes: receiving a first message sent by the vehicle, wherein the first message is used to instruct the cloud server to send payment information to the vehicle.

[0050] In one possible implementation of the third aspect mentioned above, the first message is sent after the vehicle has been in the parking lot for a short period of time, when the system detects that a user has entered the vehicle and controls the vehicle to be powered on.

[0051] In one possible implementation of the third aspect above, the method further includes: sending vehicle entry information to the vehicle, wherein the entry information includes basic vehicle information, vehicle entry time, and parking lot billing rules information.

[0052] In one possible implementation of the third aspect above, sending vehicle entry information to the vehicle includes: obtaining a vehicle entry notification message from the parking lot server, the entry notification message including at least: basic vehicle information and vehicle entry time; and sending entry information to the vehicle based on the entry notification message.

[0053] In one possible implementation of the third aspect above, the payment information includes a vehicle's pending payment order, the vehicle is equipped with an in-vehicle payment application, the vehicle's parking fee is paid by the vehicle, and the method further includes: receiving a first payment request message sent by the vehicle using the in-vehicle payment application, the first payment request message being used to request payment for the parking fee in the vehicle's first pending payment order; paying the parking fee in the first pending payment order, generating a first payment response message, and sending the first payment response message to the vehicle, wherein the first payment response message is used to indicate that the parking fee in the first pending payment order has been successfully paid.

[0054] In one possible implementation of the third aspect above, the method further includes: receiving a second message sent by the vehicle, the second message indicating that the vehicle-side distribution service has been activated, the second message being sent when the vehicle's location enters a set geographical range of the parking lot; and sending payment information to the vehicle, including: sending payment information to the vehicle through the vehicle-side distribution service.

[0055] In one possible implementation of the third aspect above, the method further includes: generating target toll information for the vehicle when the vehicle's parking duration meets the jump condition, and sending the target toll information to the mobile terminal.

[0056] In one possible implementation of the third aspect above, the method further includes: receiving a first target message sent by a mobile terminal, wherein the first target message is used to indicate that the distribution service on the mobile terminal side has been enabled, and the first target message is sent when the distance between the mobile terminal and the vehicle is less than or equal to a set distance; sending target hopping information to the mobile terminal, including: sending target hopping information to the mobile terminal through the distribution service on the mobile terminal side.

[0057] In one possible implementation of the third aspect mentioned above, the payment information is generated and sent by the cloud server when the parking duration of the vehicle meets the jump condition. The payment information is the vehicle's first jump fee information, which includes the first order to be paid.

[0058] In one possible implementation of the third aspect above, the payment information includes paid information, the parking fee for the vehicle is paid by a mobile terminal, a target payment application is installed in the vehicle, and the method further includes: receiving a target payment request message sent by the mobile terminal, the target payment request message being used to request payment for the parking fee in the target pending payment order of the target toll information; paying the parking fee in the target pending payment order, generating a target payment response message, and sending the target payment response message to the mobile terminal, wherein the target payment response message is used to indicate that the parking fee in the target pending payment order has been successfully paid.

[0059] In one possible implementation of the third aspect above, the method further includes: determining, based on the target payment response message, that the parking fee in the target pending payment order has been paid.

[0060] Fourthly, this application provides a vehicle payment system, comprising a cloud server (cloud server 30B as described below) and a parking lot server. The parking lot server sends a first pending payment order or paid information to the cloud server before the vehicle leaves the parking lot. The cloud server sends payment information to the vehicle before it leaves the parking lot, including paid information or the first pending payment order. The parking fee for the vehicle is paid by a mobile terminal associated with the vehicle or by the vehicle itself. Thus, users can pay for the vehicle on either the vehicle or their mobile terminal before leaving the parking lot. For example, the user can pay the parking fee before or upon entering the vehicle.

[0061] It is understood that the parking lot server in this application is typically a public server. In this case, the messages pushed by the parking lot server, such as payment orders, may contain redundant or insecure information such as advertisements. Cloud servers, on the other hand, can be vendor-manufactured servers such as Huawei Cloud. TM Servers. Data transmission security between vehicles or mobile devices and cloud servers is generally higher than that between vehicles and parking lot servers. Furthermore, cloud servers can push filtered information to vehicles or mobile devices. Therefore, after obtaining vehicle payment task information from the parking lot server, the cloud server can remove advertisements and other irrelevant information, filtering out information related to vehicle entry, payment skipping, and departure. Consequently, the information such as the pending payment orders recommended by the cloud server to vehicles, entry times, and departure times, as well as the pending payment orders recommended to mobile devices, is highly secure and free of redundant information such as advertisements. This improves the user's payment experience.

[0062] In one possible implementation of the fourth aspect above, the parking server is further configured to obtain a payment notification message for the vehicle before the vehicle leaves the parking lot, and determine that the parking fee for the vehicle has been paid based on the payment notification message, wherein the payment notification message is obtained from a payment server or a cloud server, and the payment notification message is used to indicate that the parking fee for the vehicle has been paid; the parking server is further configured to obtain a departure request message for the vehicle when the vehicle arrives at the exit of the parking lot, and generate a departure instruction message if the parking fee for the vehicle has been paid, wherein the departure instruction message is used to instruct the vehicle to leave.

[0063] In one possible implementation of the fourth aspect above, the parking lot server is further configured to, when a vehicle arrives at the entrance of the parking lot, obtain a vehicle entry request message, generate an entry instruction message, and send a vehicle entry notification message to the cloud server, wherein the entry instruction message is used to instruct the vehicle to be allowed to enter; the cloud server is further configured to, based on the entry notification message, generate vehicle entry information and send the entry information to the vehicle, wherein the entry information includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules, and the entry notification message includes at least the vehicle's basic information and the vehicle's entry time.

[0064] In one possible implementation of the fourth aspect above, the parking lot server is further configured to generate a vehicle departure notification message based on the departure request message and send the departure notification message to the cloud server; the cloud server is further configured to generate vehicle departure information based on the departure notification message and send the departure information to the vehicle, the departure information including the vehicle's basic information, the vehicle's departure time, and the vehicle's parking fee amount.

[0065] In one possible implementation of the fourth aspect above, the cloud server is further configured to send an order query message to the parking lot server, the order query message being used to query the vehicle's pending payment orders; the parking lot server is further configured to send an order response message to the cloud server based on the order query message, the order response message including the vehicle's pending payment orders. The aforementioned order query message can be triggered on the mobile terminal side or the vehicle side.

[0066] In one possible implementation of the fourth aspect above, the cloud server is further configured to receive a first message sent by the vehicle, wherein the first message instructs the cloud server to send payment information to the vehicle, and the first message is sent by the vehicle after the user gets in and the vehicle is powered on; wherein the order query message is sent by the cloud server based on the first message and / or when the vehicle's parking duration meets the jump condition.

[0067] In one possible implementation of the fourth aspect above, the cloud server is also used to send the vehicle's target toll information to the mobile terminal when the vehicle's parking duration meets the toll jump condition.

[0068] In one possible implementation of the fourth aspect above, the cloud server is further configured to receive a first target message sent by a mobile terminal associated with the vehicle, wherein the first target message is configured to instruct the cloud server to send the vehicle's target fare information to the mobile terminal, and the first target message is sent after the user gets off the vehicle in the parking lot and the mobile terminal disconnects from the vehicle.

[0069] Fifthly, this application provides a vehicle payment system, comprising a cloud server, a parking server, and a vehicle. The parking server is used to send a first pending payment order or paid information of the vehicle to the cloud server before the vehicle leaves the parking lot. The cloud server is used to send payment information of the vehicle to the vehicle before the vehicle leaves the parking lot, wherein the payment information includes paid information of the vehicle or a first pending payment order. The vehicle is used to pay the parking fee in the first pending payment order corresponding to the payment information including the first pending payment order. The parking fee for the vehicle, corresponding to the payment information including the paid information, is paid by a mobile terminal associated with the vehicle.

[0070] Sixthly, this application provides a vehicle payment system, comprising a cloud server, a vehicle, and a mobile terminal. The cloud server is configured to send target parking fee information to the mobile terminal before the vehicle associated with the mobile terminal leaves the parking lot, provided the distance between the mobile terminal and the vehicle is less than or equal to a set distance. The mobile terminal is configured to display a first target prompt message on its screen, wherein the first target prompt message indicates the target parking fee information. The cloud server is further configured to send payment information to the vehicle before it leaves the parking lot, wherein the payment information includes the vehicle's paid information or a first pending payment order. The vehicle is configured to display the first prompt message on its in-vehicle screen and, corresponding to the first pending payment order, pay the parking fee in the first pending payment order, wherein the first prompt message indicates the payment information, and the payment information includes paid information, and the parking fee is paid by the mobile terminal.

[0071] In a seventh aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the vehicle payment method described in the first aspect and various possible implementations of the first aspect.

[0072] Eighthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the vehicle payment method described in the first aspect and various possible implementations of the first aspect.

[0073] The beneficial effects of the second to eighth aspects mentioned above can be referred to the relevant descriptions in the first aspect and various possible implementations of the first aspect, which will not be repeated here. Attached Figure Description

[0074] Figure 1 shows a scenario diagram illustrating the application of a vehicle payment method provided in an embodiment of this application.

[0075] Figure 2A shows a schematic diagram of interface changes for a vehicle and mobile terminal collaboratively conducting a vehicle payment process according to an embodiment of this application.

[0076] Figure 2B shows a schematic diagram of interface changes during the parking fee payment process provided in an embodiment of this application.

[0077] Figure 2C shows a schematic diagram of interface changes during the process of a vehicle completing payment and leaving the parking lot, as provided in an embodiment of this application.

[0078] Figure 2D shows a schematic diagram of interface changes during the process of a vehicle entering a parking lot, as provided in an embodiment of this application.

[0079] Figure 3A shows a schematic diagram of interface changes for a vehicle and mobile terminal collaboratively conducting a vehicle payment process according to an embodiment of this application.

[0080] Figure 3B shows a schematic diagram of interface changes during the process of a mobile phone sending a billing notification according to an embodiment of this application.

[0081] Figure 3C shows a schematic diagram of interface changes during the parking payment process on a mobile phone according to an embodiment of this application.

[0082] Figure 4 shows a schematic diagram of a framework for collaborative parking payment using a vehicle and a mobile phone, as provided in an embodiment of this application.

[0083] Figure 5A shows the structure of a vehicle payment system provided in an embodiment of this application.

[0084] Figure 5B shows the structure of a vehicle payment system provided in an embodiment of this application.

[0085] Figure 6A shows a flowchart of a vehicle payment method provided in an embodiment of this application.

[0086] Figure 6B shows a schematic diagram of a mobile terminal for paying parking fees according to an embodiment of this application.

[0087] Figure 7A shows a flowchart of a vehicle payment method provided in an embodiment of this application.

[0088] Figure 7B shows a schematic diagram of a vehicle parking fee payment process provided in an embodiment of this application.

[0089] Figure 8A shows a flowchart of a vehicle payment method provided in an embodiment of this application.

[0090] Figure 8B is a flowchart illustrating a vehicle payment method provided in an embodiment of this application.

[0091] Figure 9 is a flowchart illustrating a vehicle payment method provided in an embodiment of this application.

[0092] Figure 10 is a flowchart illustrating a vehicle payment method based on a cloud server and a parking lot server provided in an embodiment of this application.

[0093] Figure 11 shows a structural schematic diagram of a vehicle provided in an embodiment of this application.

[0094] Figure 12 shows a schematic diagram of the structure of a mobile terminal provided in an embodiment of this application.

[0095] Figure 13 shows a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0096] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0097] To facilitate understanding of the solutions in the embodiments of this application by those skilled in the art, some concepts and terms involved in the embodiments of this application will be explained below.

[0098] (1) Live window is a message notification that helps users focus on the current task, view it quickly, and process it instantly. It includes card mode, capsule mode, and immersive mode. Live windows are characterized by timeliness, time-limited nature, variability, and visibility (lock screen immersive mode). Live windows are commonly found in smart cockpits and mobile phone systems (such as HarmonyOS). TM Software systems such as [system name] can display real-time information about the current task. For example, while a user is on a call or watching a TV show, they can check the real-time status of tasks such as food delivery, flight bookings, and parking payments through a real-time window.

[0099] The Live View feature can display cards on the lock screen, notification center, and other locations. It can also display the capsule status in the status bar, and expand into a floating card after clicking the capsule in the status bar. Furthermore, the Live View feature can display both the capsule and card statuses on the lock screen, and long-press or click the card to enter an immersive lock screen state.

[0100] The application scenarios for the Live Capsule mode include: when switching to the desktop or other applications, a Live Capsule will appear in the status bar, displaying a summary of the current task, such as call duration, food delivery status, and parking fee payment information. When multiple tasks are in capsule mode, the Live Capsule will be sorted according to task priority and creation time.

[0101] The application scenarios for the Live Window card mode include: clicking the Live Window capsule mode expands the Live Window into a card mode, allowing you to view detailed information about the current task or quickly perform frequently used operations. Clicking a card outside the button area directly takes you to the task's details page for further operations. Clicking a blank area or swiping up on a Live Window card mode collapses it, automatically switching back to capsule mode.

[0102] (2) An intelligent cabin is a modern automotive interior environment based on intelligence and the Internet of Things. It integrates driving information and in-vehicle applications, leveraging the powerful information processing capabilities of the in-vehicle system to provide drivers with an efficient and technologically advanced driving experience. An intelligent cabin mainly consists of three parts: hardware (such as cabin chips, head-up displays (HUDs), electronic rearview mirrors, etc.), software, and interaction (including voice recognition, facial recognition, touch recognition, and biometrics). As an example, an intelligent cabin can install cameras on the vehicle's A and B pillars and rearview mirrors to provide functions such as emotion recognition, age detection, abandoned object detection, seatbelt detection, and facial recognition.

[0103] It should also be stated that the steps in the methods and processes in this application are numbered for ease of reference, not to limit the order of steps. If there is an order between the steps, the textual description shall prevail.

[0104] As mentioned earlier, in current parking payment scenarios, the process of paying by scanning a QR code with a mobile phone is rather cumbersome and disrupts the smooth travel experience, resulting in a poor payment experience. Therefore, how to balance the user's smooth travel experience with the payment experience has become a problem that needs to be solved.

[0105] To address the aforementioned issues, this application provides a vehicle payment method that uses a collaborative approach between the vehicle and a mobile terminal to process parking fees, thus offering a distributed parking payment solution.

[0106] Specifically, the method includes: in a scenario where a vehicle is parked in a parking lot, a mobile terminal associated with the vehicle can obtain the vehicle's pre-paid parking fee information from a cloud server. At this time, the user can view this pre-paid fee information on the mobile terminal and choose whether to pre-pay the parking fee based on this information on the mobile terminal. Furthermore, before the user drives the vehicle out of the parking lot, such as when the user gets into the vehicle and powers it on, the vehicle can obtain its payment information from the cloud server. If the user has already pre-paid the parking fee on the mobile terminal, the payment information obtained by the vehicle includes the vehicle's paid information to remind the user that the vehicle has been paid. If the user has not paid the parking fee on the mobile terminal, the payment information obtained by the vehicle includes the vehicle's pending payment order, and the user can then pay the parking fee according to the pending payment order on the vehicle side. Thus, the user can pay for the vehicle on either the vehicle side or the mobile terminal side before driving the vehicle out of the parking lot. For example, the user can pay the parking fee before or while getting into the vehicle.

[0107] Thus, in this application, users do not need to go through cumbersome processes such as searching for and scanning QR codes during the vehicle payment process, and can perceive and confirm the payment process, resulting in a better parking payment experience. In addition, since the parking fee can be paid before the vehicle leaves the parking lot, that is, before the vehicle reaches the parking lot exit such as the gate, the user experiences a smoother driving experience from starting the vehicle to leaving the parking lot, which helps to alleviate or even avoid traffic congestion in the parking lot.

[0108] In some embodiments, in a vehicle payment scenario, the vehicle and / or mobile terminal can provide users with real-time information such as vehicle entry, parking fee increment, pending payment, and payment already made. This allows users to conveniently and promptly obtain real-time information about their parking payment task and quickly and easily pay the parking fee on either the vehicle or mobile terminal.

[0109] In some embodiments, this application may display prompts during the parking payment process in the form of a live view window, a notification bar, or a pop-up / banner. The following embodiments primarily illustrate this by showing prompts during the parking payment process in a live view window for both the vehicle and the mobile terminal.

[0110] In some embodiments, the vehicle and mobile terminal in this application may be equipped with system services such as distribution services to support the vehicle and mobile terminal in performing vehicle payment tasks, such as displaying prompts during the vehicle payment task. In this case, it is not necessary to install a specific parking lot application for user parking payment on the vehicle or mobile terminal; instead, the parking payment task can be performed through system services such as distribution services. This reduces the storage space occupied by the vehicle payment task on the vehicle and mobile terminal, and facilitates the smooth execution of the vehicle payment task.

[0111] In some embodiments, in the first parking payment scenario of this application, after a user drives their vehicle into a parking lot and parks, the user gets out of the car, and the vehicle's power is cut off. After the vehicle's power is cut off, the mobile terminal associated with the vehicle can obtain information such as overdue parking fees and pending payment orders, and support the user to learn about the overdue fees and pay the parking fees in the pending payment orders on the mobile terminal. Furthermore, after the user gets back into the car and the vehicle is powered back on, the vehicle can obtain its payment information from the cloud server, such as paid fees or pending payment orders. Therefore, even if the user does not pay the parking fees on the mobile terminal, they can still pay the parking fees in the pending payment orders on the vehicle's side. Even if the user does not pay the parking fees on the mobile terminal, they can still pay the parking fees on the vehicle's side when they get back into the car. In this way, parking fees can be paid quickly and conveniently on the mobile terminal before the user gets back into the car. This allows users to promptly learn about and pay parking fees according to their actual needs, improving the convenience and user-friendly experience of parking payment.

[0112] In some embodiments, in the second parking payment scenario of this application, after a user drives their vehicle into a parking lot and parks, the user does not get out of the car, but the vehicle's power is cut off. After the vehicle's power is cut off, the mobile terminal associated with the vehicle can obtain the vehicle's overdue payment information, pending payment orders, etc., and support the user to obtain overdue payment information and pay the parking fees in the pending payment orders on the mobile terminal side. Furthermore, after the vehicle is powered back on, the vehicle can obtain the vehicle's payment information from the cloud server, such as paid information or pending payment orders. Therefore, even if the user does not pay the parking fees on the mobile terminal side, they can still pay the parking fees in the pending payment orders on the vehicle side. It is understood that when the vehicle is powered off, the user usually uses a mobile terminal, and it is more convenient for the user to pay the vehicle fees on the mobile terminal side. When the vehicle is powered on, the user usually prefers to use the in-vehicle system, and it is more in line with the user's operating habits and more convenient to operate when the user pays the vehicle fees on the vehicle side.

[0113] In some embodiments, in the third parking payment scenario of this application, after a user drives their vehicle into a parking lot and parks, the user does not get out of the car, and the vehicle's power is not cut off. The vehicle can obtain its over-fee information, pending payment orders, etc., from the cloud server, and the user can obtain the over-fee information and pay the parking fees in the pending payment orders on the vehicle side. In this case, the mobile terminal does not need to obtain the vehicle's over-fee information, pending payment orders, etc. That is, the vehicle can complete the vehicle payment process locally, without the mobile terminal participating in the vehicle payment process.

[0114] In the following embodiments, for ease of description, the first parking payment scenario described above is mainly used as an example to illustrate the changes in the user interface during the collaborative execution of the vehicle payment task by the vehicle and the mobile terminal.

[0115] As an example, in the first parking payment scenario of this application, when a vehicle enters a paid parking lot, it can obtain entry information and display corresponding prompts on the in-vehicle screen via a real-time window to inform the user (e.g., the driver) that the vehicle has entered. After the user parks and gets out of the car with a mobile terminal (e.g., a mobile phone), the mobile terminal can obtain the vehicle's fee information and display corresponding prompts on the mobile terminal screen via a real-time window to inform the user that the parking fee is about to change. At this time, the user can open the real-time window on the mobile terminal to obtain the pending payment order and choose whether to pay the parking fee in advance. Subsequently, after the user gets back into the car in the parking lot, the vehicle can obtain payment information and display corresponding prompts on the in-vehicle screen via a real-time window to show the user the vehicle's paid information or pending payment order. If the user has already paid the parking fee in advance on the mobile terminal, the user can open the real-time window on the vehicle side after getting back into the car to obtain the paid information, such as the departure time. If a user does not pay for parking on their mobile device, they can access the payment order through a real-time window on the vehicle's side after boarding and pay the parking fee there. In other words, parking fees can be paid before or upon boarding.

[0116] In some embodiments, the vehicle and mobile terminal can each use a distribution service to control the real-time window for vehicle payment tasks without installing or running a specific application. Thus, since the vehicle and mobile terminal collaboratively display parking fee-related information, pending payment orders, and paid information through the real-time window during the payment process, without requiring the installation of a specific parking payment application on the vehicle or mobile terminal, it allows users to focus on and promptly obtain this information, enabling timely and convenient payment of parking fees.

[0117] In some embodiments, the paid parking lot in this application can be a public parking lot, such as a parking lot in a shopping mall, hospital, or other public place. For example, in the first parking payment scenario, after parking in the parking lot, the user usually gets out of the car and stays in the public place where the parking lot is located for a period of time, such as shopping in a shopping mall or receiving medical treatment in a hospital, before driving away from the parking lot.

[0118] As an example, the parking payment method provided in this application can be applied to scenarios where users pay for parking in shopping malls. For instance, after a user drives into a shopping mall parking lot, parks, and takes their mobile phone into the mall, the phone can obtain and display the parking fee information via a real-time window. The user can then pay the parking fee in advance on their mobile phone based on the fee information before leaving the parking lot. Additionally, after the user gets into their car in the parking lot, the vehicle's onboard terminal can display the vehicle's payment information, such as paid information or pending payment orders, on a real-time window. The user can then pay the parking fee based on these pending payment orders on the vehicle's side after getting into the car. This allows the user to complete the parking fee payment before starting the vehicle.

[0119] Referring to Figure 1, which illustrates a scenario of a vehicle payment method according to an embodiment of this application, the scenario includes a vehicle 10 and a mobile terminal 20. The user typically carries the mobile terminal 20. When the user is inside the vehicle 10, the mobile terminal 20 can establish a wireless connection with the vehicle 10, such as via Bluetooth. When the user is outside the vehicle 10, the mobile terminal 20 can disconnect from the vehicle 10. For example, after parking the vehicle 10 in a public parking lot, the user will get out of the car carrying the mobile terminal 20. Before leaving the parking lot, the user can obtain a payment order for the vehicle 10 on the mobile terminal 20 and choose to pay in advance. Then, when the user gets back in the car to leave, if the parking fee has already been paid in advance, the user can directly drive the vehicle 10 away from the parking lot. Alternatively, if the parking fee has not been paid in advance, the user can obtain a payment order on the vehicle 10 and pay the fee. After paying the fee for the vehicle 10, the user can start the vehicle 10 and smoothly drive it away from the parking lot.

[0120] In some embodiments, the vehicle in this application includes systems such as an intelligent cabin, an in-vehicle terminal, and a vehicle infotainment system, and executes the vehicle payment method described in this application through these systems. The intelligent cabin and vehicle infotainment systems include one or more screens, such as a central control screen, a rear-seat screen, and a passenger-side entertainment screen. In the scenario shown in Figure 1, the in-vehicle screen in vehicle 10 includes in-vehicle screen 11, and in-vehicle screen 11 is illustrated as a central control screen.

[0121] In some embodiments, the mobile terminal in this application may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a mobile phone, wearable device (such as a smartwatch), tablet computer, virtual reality (VR) terminal device, augmented reality (AR) terminal device, etc. These terminal devices include one or more screens. For example, in the scenario shown in Figure 1, the mobile terminal 20 is illustrated as a mobile phone (i.e., phone 20), and the terminal screen in phone 20 includes a terminal screen 21, which is illustrated as the main screen of phone 20.

[0122] Next, taking the central control screen 11 of the vehicle 10 and the terminal screen 21 of the mobile terminal 20 shown in Figure 1 as examples, we will explain the interface change scenarios in the vehicle and mobile terminal collaborative vehicle payment process provided in this application.

[0123] Referring to Figure 2A, this is a schematic diagram illustrating an interface change during the collaborative vehicle payment process between vehicle 10 and mobile terminal 20. Specifically, after the user drives vehicle 10 into the parking lot, vehicle 10 displays a capsule-shaped real-time window 1101 on interface 101 of the in-vehicle screen 11, showing the message "Entered the parking lot." After the user gets out of the car, mobile phone 20 can display a capsule-shaped real-time window 2101 on interface 201 of the terminal screen 21, showing the message "50 minutes," to remind the user that the parking fee is about to increase (i.e., the parking time is about to reach one hour, and the parking fee will change). Furthermore, before the user gets back into the car to leave, vehicle 10 can display a capsule-shaped real-time window 1102 on interface 102 of the in-vehicle screen 11, showing the message "Pending payment," to indicate that the parking fee for vehicle 10 has not yet been paid. At this time, the message "Pending payment" in the real-time window 1102 indicates the pending payment order for vehicle 10.

[0124] In some embodiments, users can complete parking fee payment on the side of vehicle 10 to complete the parking payment process. At this time, the smart cockpit or in-vehicle terminal in vehicle 10 has payment capabilities, such as having an in-vehicle payment application installed, which can support vehicle 10 to complete parking fee payment based on its payment capabilities.

[0125] As an example, the in-vehicle payment application installed on vehicle 10 can be the system wallet or a third-party payment application such as Alipay. TM The embodiments in this application do not specifically limit this.

[0126] Referring to Figure 2B, this is a schematic diagram of the interface changes during the parking fee payment process for vehicle 10. When a user clicks on the live view window 1102 of the interface 102 displayed on the in-vehicle screen 11 shown in Figure 2A, the vehicle 10 can trigger the display of interface 103 as shown in Figure 2B on the in-vehicle screen 11. This interface 103 includes a card-style live view window 1031, which displays detailed parking fee information (such as "Parking duration 2.5 hours", "¥35.00", etc.) and a "Pay Now" control 1032. In addition, the upper left corner of the interface 103 displayed on the in-vehicle screen 11 also includes a capsule-style live view window 1103, which includes the prompt message "Pending Payment" to indicate that the current parking fee payment task is in a pending payment state.

[0127] Furthermore, when the user clicks the "Pay Now" control 1032 in the card-state live view window 1031, it triggers the display of interface 104 on the vehicle screen 11. This interface 104 includes an order confirmation page, which displays detailed information such as the vehicle's license plate number, parking duration, entry time, and parking fee, as well as a "Confirm Payment" control 1041. Additionally, the upper left corner of the interface 104 displayed on the vehicle screen 11 includes a capsule-state live view window 1104, which displays the message "Order Details" to indicate that the current parking payment task is in the order details confirmation stage.

[0128] Subsequently, the user clicks the "Confirm Payment" control 1041 on interface 104, triggering the display of interface 105 on the vehicle screen 11. Interface 105 includes an order payment window 1051. This payment window 1051 includes information such as "Parking Fee ¥35.00," payment account "xx Bank," a prompt "Please click the face image to start face image payment," and a "Face" control 1052. The user clicks the "Face" control 1052 and aligns their face with a camera inside the vehicle 10, such as the camera on the A-pillar, so that the vehicle 10 can capture the face image for face recognition to complete the face image payment. In addition, the upper left corner of interface 105 displayed on the vehicle screen 11 also includes a capsule-shaped live view window 1105, which includes the prompt "Order Payment" to indicate that the current parking payment task is in the order payment state.

[0129] In some embodiments, the size of the capsule-shaped live view window displayed on interfaces 103, 104 and 105 shown in FIG2B is smaller than that of the capsule-shaped live view window shown in FIG2A.

[0130] Furthermore, in some other embodiments, the capsule-state live view window may not be displayed on interfaces 103, 104, and 105 shown in FIG2B.

[0131] Furthermore, in some embodiments, after vehicle 10 successfully pays the fee, vehicle 10 can also notify the user that the vehicle has successfully paid the fee and the departure time.

[0132] Referring to Figure 2C, this is a schematic diagram of the interface changes during the process of vehicle 10 completing payment and leaving the parking lot. Specifically, after vehicle 10 completes payment, a capsule-shaped real-time window 1106 is pulled up on the interface 106 displayed on the in-vehicle screen 11, displaying the message "Paid". Clicking on the capsule-shaped real-time window 1106 triggers interface 107 displayed on the in-vehicle screen 11. This interface 107 includes a card-shaped real-time window 1071, which displays the messages "Paid" and "Your parking fee has been paid. Please leave before 10:45, otherwise you will be charged again," indicating to the user that the expected departure time (i.e., the time expected to leave) without incurring new charges is 10:45. In addition, the upper left corner of the interface 107 displayed on the vehicle screen 11 also includes a capsule-shaped live view window 1107, which includes the prompt message "Departure Information" to indicate that the current parking payment task is completed. Furthermore, after the user clicks the "Confirm" control 1072 in the card-shaped live view window 1071, or clicks a blank area of ​​the interface 107, or swipes up the card-shaped live view window 1071, the live view window can be automatically switched to capsule mode (not shown in the figure). Until the vehicle 10 leaves the parking lot, such as leaving the set area of ​​the parking lot, the live view window, such as the capsule-shaped live view window, is canceled on the interface 108 of the vehicle screen 11.

[0133] Furthermore, referring to Figure 2D, a schematic diagram of interface changes during the process of vehicle 10 entering the parking lot is shown. Specifically, before vehicle 10 enters the parking lot and passes through parking equipment (such as a gate device), as shown in Figure 2D, vehicle 10 displays interface 100 on the in-vehicle screen 11. This interface 100 can be a desktop interface. After vehicle 10 enters the parking lot and passes through the parking equipment, as shown in Figure 2D, vehicle 10 displays interface 101 on the in-vehicle screen 11. This interface 101 displays a capsule-shaped real-time window 1101 with the prompt message "Entered the parking lot". Then, when the user clicks on the capsule-shaped real-time window 1101, it triggers vehicle 10 to display interface 109 on the in-vehicle screen 11. This interface 109 includes a card-shaped real-time window 1091. The real-time window 1091 includes entry information such as parking lot name, license plate number, entry image, entry time, and billing rules, as well as a "confirm" control 1092. This allows users to quickly understand the current parking lot's billing rules, helping them focus on parking fees. Furthermore, after the user clicks the "Confirm" control 1092 in the card-mode live view window 1091, or clicks a blank area of ​​the interface 109, or swipes up the card-mode live view window 1091, it can be collapsed and automatically switched to capsule mode (not shown in the figure). In addition, the upper left corner of the interface 109 displayed on the vehicle screen 11 also includes a capsule-mode live view window 1109, which includes the prompt message "Entry Information" to indicate that the current parking payment task is in the entry state.

[0134] In some embodiments, users can complete parking fee payments on a mobile terminal, such as phone 20, to complete the parking payment process. In this case, phone 20 has payment capabilities and can support parking fee payments based on its payment functionality. For example, phone 20 may have a target payment application installed, such as a system wallet or a third-party payment application.

[0135] Referring to Figure 3A, this is a schematic diagram illustrating an interface change during the collaborative vehicle payment process between vehicle 10 and mobile terminal 20. Specifically, after the user drives vehicle 10 into the parking lot, a capsule-shaped real-time window 1101 on the interface 101 displayed on the vehicle screen 11 shows the message "Entered". After the user gets out of the car, the mobile phone 20 can pull up a capsule-shaped real-time window 2101 on the interface 201 displayed on the terminal screen 21 to show the message "50 minutes", indicating that the parking fee is about to increase (i.e., the parking time is about to reach one hour, and the parking fee will change). Furthermore, before the user gets back into the car to leave, if the user has already completed the parking payment on the mobile phone 20, the vehicle 10 can pull up a capsule-shaped real-time window 1102a on the interface 102 displayed on the vehicle screen 11 to show the message "Paid", indicating that the parking fee for vehicle 10 has been paid. The user can then drive vehicle 10 directly out of the parking lot, or the user can view the vehicle's payment information by clicking on the real-time window 1102a. At this time, the "Paid" message in the real-time window 1102a indicates the payment information of vehicle 10, such as departure information including departure time.

[0136] Similarly, the process of the user clicking on the live view window 1102a to view the departure information of vehicle 10 is similar to the process shown in Figure 2C. Furthermore, the process of the vehicle screen 11 canceling the display of the live view window after vehicle 10 leaves the parking lot is also similar to the process shown in Figure 2C, and will not be elaborated here.

[0137] Furthermore, referring to Figure 3B, a schematic diagram of the interface changes during the process of mobile phone 20 notifying users of overcharge fees is shown. When the parking time of vehicle 10 shown in Figure 3B reaches 50 minutes, mobile phone 20 can display interface 202 as shown in Figure 3B on terminal screen 21. This interface 202 includes a card-style real-time window 2021, which includes overcharge information such as "Fee Increase Reminder," "50 minutes parked, 5 yuan increase in 10 minutes," "Parking fee 15.00 yuan," and a "Pay Now" control 2022. If the user is ready to leave, they can click the "Pay Now" control 2022 to pay the parking fee in advance on mobile phone 20. If the user is not ready to leave, they can click on a blank area of ​​interface 202 or swipe up on the card-style real-time window 2021 to collapse it and automatically switch to capsule mode (not shown in the figure).

[0138] Next, referring to Figure 3C, a schematic diagram of the interface changes during the parking payment process on mobile phone 20 is shown. When the user clicks the "Pay Now" control 2022 in the real-time window 2021 (card state) shown in Figure 3B, it triggers the display of interface 203 on the terminal screen 21. This interface 203 includes an order confirmation page, which contains detailed information such as the vehicle 10's license plate number, parking duration, entry time, and parking fee, as well as a "Confirm Payment" control 2031. Subsequently, clicking the "Confirm Payment" control 2031 triggers the display of interface 204 on the terminal screen 21, which overlays an order payment window 2041. This payment window 2041 includes "Parking Fee: ¥15.00," payment method "xx Bank," a prompt "Use Payment Password," a "Fingerprint Area," and a "Fingerprint" control 2042. The user long-presses the "Fingerprint" control 2042, causing the mobile phone 20 to collect fingerprint information for fingerprint recognition to complete the fingerprint payment. Furthermore, when the user gets into the car to leave, the vehicle 10 can pull up a real-time window on the in-vehicle screen 11 to display a prompt message "Payment Completed," so that the user can quickly and smoothly drive the vehicle 10 out of the parking lot.

[0139] Next, referring to Figure 4, a schematic diagram of the framework for collaborative parking payment by vehicle 10 and mobile phone 20 provided in this application is shown. This framework is applied to vehicle payment system 01, which includes vehicle 10 and mobile phone 20.

[0140] The vehicle 10 in this application includes a vehicle infotainment system 10a, which includes a vehicle status information acquisition module, a vehicle infotainment central control screen (such as an in-vehicle screen 11), and a cockpit collaboration service.

[0141] The vehicle status information acquisition module is used to acquire the vehicle status information of vehicle 10 and detect events such as user getting on and off the vehicle based on changes in the vehicle status information. The vehicle status information includes at least one of the following: vehicle location, vehicle operating status, vehicle door opening / closing status, and vehicle seat occupancy status.

[0142] The vehicle's location can be determined based on its location information.

[0143] The operating status of a vehicle can include driving status, low speed status, and stationary status.

[0144] The opening and closing status of a vehicle's doors can include the door being open and the door being closed.

[0145] The seating status of a vehicle can include a user-occupied status and a user-absent status. A user-occupied status indicates that the user is inside the vehicle, while an absent status indicates that the user is not inside the vehicle. Furthermore, seating status refers to either the driver's seat or all seats; this application does not specify a particular type.

[0146] The vehicle infotainment system (such as the in-vehicle screen 11) is used to interact with the user, such as displaying the user interface of various in-vehicle applications or services, and displaying a live window on the main interface or the user interface of the currently running application or service.

[0147] Cockpit collaboration services are used to interact with cloud servers or other devices such as mobile phones and smart home devices to achieve intelligent navigation, vehicle payment, and in-vehicle air conditioning control through multi-device collaboration. As an example, cockpit collaboration services include a distribution service, which is used by the vehicle (such as the in-vehicle infotainment system) to interact with the cloud server to obtain information related to parking payment tasks, such as entry information, pending payment orders, paid information, and exit information.

[0148] The mobile phone 20 includes a mobile phone screen, for example, the mobile phone screen can be the terminal screen 21 shown in Figure 1.

[0149] As an example, a distribution service can also be installed on mobile phone 20 to interact with the cloud and obtain information related to the parking payment task of the vehicle associated with mobile phone 20, such as vehicle 10, such as entry information, pending payment orders, payment information, and departure information.

[0150] Furthermore, although not shown in Figure 4, the aforementioned vehicle payment system 01 may also include a cloud server such as Huawei Cloud. TM The embodiments of this application do not specifically limit the types of equipment such as servers.

[0151] Specifically, as shown in Figure 4, the vehicle payment process is executed by the vehicle payment system 01, and the process includes the following steps:

[0152] S401: Sensing user entering the parking lot.

[0153] As an example, the vehicle status information detection module in the vehicle infotainment system 10a detects when a user enters the parking lot. That is, the vehicle infotainment system 10a detects when vehicle 10 enters the parking lot.

[0154] In some embodiments, the vehicle status information detection module in the vehicle system 10a can detect that the vehicle 10 has entered a set geographical range of the parking lot, so as to sense that the user has entered the parking lot.

[0155] S402: In-vehicle infotainment system recommends live view window.

[0156] As an example, the vehicle infotainment system 10a recommends a live view window on the vehicle's central control screen, such as the in-vehicle screen 11.

[0157] In some embodiments, when the vehicle infotainment system 10a detects that the vehicle 10 has entered a designated geographical area of ​​the parking lot, it can activate the distribution service in the cockpit collaboration service to obtain the vehicle 10's entry information from the cloud. Then, the vehicle infotainment system 10a can open a real-time window on the vehicle's central control screen to notify the user that the vehicle 10 has entered the parking lot.

[0158] As an example, referring to the scenario shown in Figure 2D, taking the vehicle infotainment screen 11 as an example, the vehicle infotainment system 10a can first pull up the capsule-style real-time window 1101 to display the prompt message "Entered the venue", and then, when triggered by the user, pull up the card-style real-time window 1091 to display detailed information about the vehicle 10's entry, such as the vehicle 10's license plate number, entry time, billing rules, etc.

[0159] In some embodiments, the vehicle infotainment system 10a has enabled a live view window for the parking payment task, that is, it enables the function of displaying real-time information about the parking payment task. For example, the vehicle infotainment system 10a has enabled a live view window for the parking payment task in the system settings application or the system account application.

[0160] S403: Sensing user getting off the vehicle.

[0161] As an example, the vehicle status information detection module in the vehicle infotainment system 10a detects when a user gets out of the vehicle.

[0162] In some embodiments, the vehicle status information of vehicle 10 satisfies a first condition, indicating that the user has disembarked. For example, the first condition may include: the vehicle 10 is in a parked state, the vehicle 10's door is in a closed state, and the vehicle 10's seat is in a non-occupied state.

[0163] S404: Vehicle power failure.

[0164] As an example, the vehicle status information detection module in the vehicle infotainment system 10a triggers the cockpit collaboration service to control the power outage of the vehicle 10.

[0165] In some embodiments, when the vehicle status information detection module in the vehicle infotainment system 10a senses that the user has gotten out of the vehicle, it can send a notification message to the cockpit collaboration service to trigger the cockpit collaboration service to control the vehicle 10 to cut off power and shut down the vehicle infotainment system 10a.

[0166] In some embodiments, vehicle power cut-off mainly refers to powering off the vehicle's infotainment system, such as infotainment system 10a, i.e., shutting down the electronic control system of the infotainment system.

[0167] In some embodiments, the vehicle 10 is powered off during the user's exit from the vehicle. For example, before the user exits, after the user presses the power button, the vehicle infotainment system 10a can control the shutdown of some functions or devices in the vehicle 10, such as turning off the engine, wireless communication system, positioning system, radar, camera, navigation system, etc. At this time, the vehicle screen of the vehicle 10 is in a blackout state. Furthermore, before the user exits the vehicle, the vehicle infotainment system 10a can turn off other functions or devices in the vehicle 10, such as the cabin detection function (detecting the seat occupancy status), to control the vehicle 10 to complete the power-off. At this time, this application can execute S403 and S404 in parallel, that is, the vehicle 10 can sense the user exiting the vehicle during the power-off process.

[0168] In other embodiments, S404 can be executed first and then S403, meaning that the vehicle 10 can be powered off before sensing the user getting off the vehicle.

[0169] S405: The vehicle's infotainment system has lost connection with the mobile phone.

[0170] As an example, the cockpit collaboration service in vehicle infotainment system 10a can control the vehicle infotainment system 10a to disconnect from mobile phone 20 during the process of vehicle 10 power failure, such as when vehicle infotainment system 10a is turned off.

[0171] Specifically, when the vehicle 10 is powered off, the mobile phone 20 will not detect the vehicle's infotainment system 10a and will disconnect from it.

[0172] Normally, when a user drives vehicle 10 into a parking lot, the vehicle's infotainment system 10a and mobile phone 20 have already established a connection, such as a Bluetooth connection or other wireless connection. Therefore, when vehicle 10 is powered off, mobile phone 20 will disconnect from the infotainment system 10a.

[0173] In some embodiments, the vehicle 10, the in-vehicle infotainment system 10a, and the mobile phone 20 are associated, and a cloud server such as Huawei Cloud is used. TM The system can pre-store association information indicating the connection between the vehicle 10, the in-vehicle infotainment system 10a, and the mobile phone 20. For example, the in-vehicle infotainment system 10a and the mobile phone 20 may be logged into the same user account simultaneously (e.g., Huawei). TM (Account or mobile phone number, etc.), or vehicle 10, vehicle system 10a and mobile phone 20 are all bound to the same license plate number.

[0174] S406: Live View Window Collaboration with Mobile Recommendations.

[0175] In some embodiments, if the first coordination condition is met, the live view window can be coordinated from the vehicle system 10a side to the mobile phone 20 side for recommendation.

[0176] As an example, the first condition for collaboration includes: the vehicle's infotainment system disconnecting from the mobile phone.

[0177] As another example, the first coordination conditions include: the mobile phone is disconnected from the vehicle (i.e., the mobile phone is disconnected from the vehicle's infotainment system), the mobile phone has enabled the distribution service, and the distance between the mobile phone and the vehicle is less than or equal to a set distance. For example, the set distance could be 1 kilometer or 2 kilometers, but is not limited to these.

[0178] It's understandable that when users park in public places like shopping malls and hospitals, they typically engage in activities such as shopping or seeking medical treatment in or near those public places. In this situation, the distance between the phone and the vehicle is usually quite close. If the distance is less than or equal to a set distance, it indicates that the user is more likely to be concerned about parking fees. Therefore, a real-time view window can be recommended on the side of the phone to allow users to easily focus on parking fees.

[0179] In some embodiments, when the mobile phone 20 is disconnected from the vehicle infotainment system 10a, the mobile phone 20 can send data to a cloud server such as Huawei Cloud. TM A notification message (such as a first target message) is sent to notify the cloud to subsequently send the toll information and / or pending payment orders for vehicle 10 to mobile phone 20. As an example, mobile phone 20 can activate its local distribution service and send the first target message to the cloud based on this service. Then, based on the received toll information and other parking payment-related information, a real-time view is recommended on mobile phone 20. Thus, in vehicle payment system 01, the real-time view is changed from being recommended by vehicle infotainment system 10a to being recommended by mobile phone 20.

[0180] As an example, the example of the real-time window recommended by mobile phone 20 in this application can be referred to the examples shown in Figure 3B or Figure 3C above, which will not be repeated here. In this way, mobile phone 20 can recommend information such as the toll increase information of vehicle 10 to the user through the real-time window.

[0181] In some embodiments, the mobile phone 20 has enabled the live view window for the parking payment task, that is, it has enabled the function of displaying the live view window for the parking payment task. For example, the mobile phone 20 has enabled the live view window for the parking payment task in its system settings application or system account application.

[0182] S407: Sensing user boarding.

[0183] As an example, the vehicle status information detection module in the vehicle infotainment system 10a detects when a user gets into the vehicle.

[0184] In some embodiments, the vehicle status information of vehicle 10 satisfies a second condition, indicating that a user has boarded the vehicle. The second condition may include at least one of the following: the vehicle 10 is in a parked state or in a parked state; the vehicle 10's door is in a closed state; or the vehicle 10's seat is in a user-occupied state.

[0185] S408: Vehicle powered on.

[0186] As an example, the vehicle status information detection module in the vehicle infotainment system 10a triggers the cockpit collaboration service to power on the vehicle 10.

[0187] In some embodiments, when the vehicle status information detection module in the vehicle infotainment system 10a senses that a user has entered the vehicle, it can send a notification message to the cockpit collaboration service to trigger the cockpit collaboration service to control the vehicle 10 to power on and start the vehicle infotainment system 10a.

[0188] In some embodiments, vehicle 10 is powered on during the user's entry into the vehicle. For example, before the user enters the vehicle, pressing the unlock button on the vehicle remote control can activate some functions or devices in vehicle 10, such as the door detection function and the cabin detection function. At this time, the vehicle screen of vehicle 10 is off. Then, after the user enters the vehicle, the user can press the power button on vehicle 10 to activate other functions or devices in vehicle 10, such as the wireless communication system, positioning system, radar, camera, and navigation system, to power on vehicle 10. In this case, S407 and S408 can be executed in parallel, meaning vehicle 10 can sense the user entering the vehicle during the power-on process.

[0189] In other embodiments, S408 can be executed first and then S407, meaning that the vehicle 10 can be powered on before sensing the user getting into the vehicle.

[0190] S409: Connecting the vehicle's infotainment system to your mobile phone.

[0191] As an example, the cockpit collaboration service in vehicle infotainment system 10a can control the vehicle infotainment system 10a to disconnect from mobile phone 20 during the process of vehicle 10 power failure, such as when vehicle infotainment system 10a is turned off.

[0192] Specifically, when the vehicle 10 is powered on and the vehicle infotainment system 10a is started, the mobile phone 20 can detect the vehicle infotainment system 10a again and automatically establish a connection with the vehicle infotainment system 10a, such as a wireless connection via Bluetooth.

[0193] S410: Real-time window collaboration with vehicle infotainment system recommendations.

[0194] In some embodiments, if the second collaboration condition is met, the live view window can be collaboratively sent from the mobile phone 20 side to the vehicle system 10a side for recommendation.

[0195] As an example, the second collaborative condition includes: sensing that a user has boarded the vehicle.

[0196] As another example, the second coordination condition includes: the vehicle is powered on (the vehicle's infotainment system has been started), the system detects that the user has boarded the vehicle, and the service distribution has been activated.

[0197] In some embodiments, when the vehicle's infotainment system 10a detects a user entering the vehicle, it can send data to a cloud server such as Huawei Cloud. TM A notification message (such as the first message) is sent to instruct the cloud server to subsequently send the payment information or pending payment order of vehicle 10 to the vehicle-mounted system 10a. As an example, the vehicle-mounted system 10a can activate its local distribution service and, based on this service, send the first message to the cloud server, thereby receiving parking payment information such as payment information or pending payment information and displaying it in a live view window on the vehicle-mounted system 10a side. Thus, in the vehicle payment system 01, the live view window changes from being recommended by mobile phone 20 to being recommended by vehicle-mounted system 10a.

[0198] S411: Vehicle infotainment system 10a detects that the user has left the parking lot.

[0199] As an example, the vehicle status information detection module in the vehicle infotainment system 10a detects when a user leaves the parking lot. That is, the vehicle infotainment system 10a detects when vehicle 10 enters the parking lot.

[0200] In some embodiments, the vehicle status information detection module in the vehicle system 10a can detect when the location of the vehicle 10 leaves the set geographical range of the parking lot, so as to sense that the user has left the parking lot.

[0201] In other embodiments, the vehicle infotainment system 10a can be powered by a cloud server such as Huawei Cloud. TM The system receives information that vehicle 10 has left the parking lot to detect when the user has departed.

[0202] S412: Live view window disappears.

[0203] In some embodiments, when the cancellation condition is met, the vehicle infotainment system 10a can cancel the display of the live feed window, causing the live feed window to disappear.

[0204] As an example, cancellation conditions include: the location of vehicle 10 leaving the set geographical range of the parking lot, or vehicle 10 receiving a departure message.

[0205] Thus, in this application, vehicle 10 and mobile phone 20 can work together to complete the vehicle parking payment process, making it convenient and quick for users to pay parking fees on their mobile phones or in their vehicles.

[0206] Next, the structure of the vehicle payment system provided in this application will be described with reference to Figures 5A and 5B.

[0207] Referring to Figure 5A, it is a schematic diagram of the structure of a vehicle payment system provided in an embodiment of this application. As shown in Figure 5A, this scenario includes not only a vehicle 10 and a mobile phone 20, but also a cloud server 30 and parking equipment (such as gate equipment) 40.

[0208] Vehicle 10 and mobile phone 20 are associated. For example, vehicle 10 and mobile phone 20 are logged into the same user account, such as a Huawei account. Furthermore, vehicle 10 and mobile phone 20 establish or disconnect connections (e.g., wireless connections such as Bluetooth). For instance, when a user gets into the vehicle with mobile phone 20, mobile phone 20 can automatically or manually establish a connection with vehicle 10, and when the user gets out of the vehicle with mobile phone 20, mobile phone 20 can disconnect from vehicle 10. A detailed description of vehicle 10 and mobile phone 20 can be found in the relevant descriptions above, and will not be repeated here.

[0209] The cloud server 30A can be used to manage parking fees for vehicles in these parking lots through a parking fee collection system, and to control parking equipment such as parking equipment 40 in each parking lot. Furthermore, the cloud server 30A can also interact with devices such as vehicle 10 and mobile terminal 20 to collaboratively execute the vehicle payment method described in this application.

[0210] As an example, cloud server 30 may include vendor servers such as Huawei Cloud. TM Servers and parking lot servers, etc., or, the cloud server 30A can be a parking lot server that supports the Internet of Things.

[0211] In some embodiments, the cloud server 30A can obtain parking payment task-related information such as toll skipping information, pending payment orders, and paid payment information of vehicle 10, and recommend to mobile phone 20 the toll skipping information and pending payment orders of vehicle 10, as well as recommend paid payment information or pending payment orders of vehicle 10 to vehicle 10.

[0212] Parking equipment 40 can be a gate device in a parking lot that supports the Internet of Things (IoT). Specifically, parking equipment 40 is an automated device used to manage vehicle entry and exit from the parking lot, typically used in conjunction with license plate recognition, parking fee collection systems, etc., to achieve intelligent vehicle management. For example, parking equipment 40 can recognize vehicle license plates, report the license plates to cloud server 30A, and check whether the vehicle's parking fee has been paid.

[0213] Referring to Figure 5B, a schematic diagram of a vehicle payment system provided in an embodiment of this application is shown. As shown in Figure 5B, the scenario includes a vehicle 10 and a mobile phone 20, as well as a cloud server 30B, parking equipment (such as gate equipment) 40, and a parking server 50.

[0214] The main difference between the system structures shown in Figure 5B and Figure 5A is that the cloud server 30A shown in Figure 5A is replaced by two independent servers: cloud server 30B and parking lot server 50. The similarities will not be elaborated here.

[0215] Cloud server 30B can be used for Huawei Cloud. TMThe cloud server is used to interact with devices such as vehicle 10, mobile phone 20 and parking server 50, so as to collaboratively execute the vehicle payment method in this application through vehicle 10 and mobile phone 20.

[0216] Parking server 50 is a server that can be associated with one or more parking lots. For example, parking server 50 can manage parking fees for vehicles in these parking lots through a parking fee collection system and control parking equipment such as parking equipment 40 in each parking lot.

[0217] In the scenario shown in Figure 5B, the parking equipment 40 can identify the license plate of a vehicle, report the license plate to the parking server 30, and query whether the parking fee for the corresponding vehicle has been paid.

[0218] It is understood that the structure of the vehicle payment system shown in Figures 5A and 5B above is only one example. In some other embodiments, the vehicle payment system may include more or fewer devices.

[0219] In one possible implementation, the parking equipment 40 and the parking server 50 can be deployed in the same device, such as a server. For example, the parking equipment 40 is part of the parking server 50, and in this case, the parking equipment 40 and the parking server 50 are collectively referred to as the parking server.

[0220] In another possible implementation, the vehicle payment system described above may also include a payment server for interacting with vehicle 10 or mobile terminal 20 and parking lot server 50 to pay parking fees.

[0221] Next, based on the system shown in Figures 5A and 5B, and referring to Figures 6A, 6B, 7A, and 7B, the process of the vehicle payment method in the first parking payment scenario of this application will be described.

[0222] As shown in Figure 6A, in this vehicle payment method, the parking fee for vehicle 10 is paid by mobile phone 20. This vehicle payment method can be executed interactively by vehicle 10, mobile phone 20, and a cloud server. The cloud server can be cloud server 30A shown in Figure 5A or cloud server 30B shown in Figure 5B. At this time, cloud server 30A and cloud server 30B can be collectively referred to as the first cloud server, and mobile phone 20 is a mobile terminal.

[0223] Specifically, the method shown in Figure 6A includes the following steps:

[0224] S601: Vehicle 10 detects that the vehicle's location has entered the designated geographical area of ​​the parking lot and starts the vehicle distribution service.

[0225] S602: Vehicle 10 sends a second message to cloud server 30A or 30B.

[0226] The geographical scope of the parking lot can be the area around the parking lot, and for shopping malls, it includes the location of the road entrance to the parking lot.

[0227] The second message (also known as the vehicle service start message) is used to notify the cloud server 30A or 30B that the vehicle's distribution service has been started, and the vehicle and the cloud server 30A or 30B communicate based on the distribution service.

[0228] It is understood that the distribution service of vehicle 10 is in the enabled state, and vehicle 10 can use the distribution service to perform vehicle payment tasks. At this time, this application can enable the distribution service when the vehicle is in a parking scenario, such as triggering vehicle 10 to enable the distribution service through the geofence defined by the geographical range of the parking lot, so as to avoid wasting the computing resources of vehicle 10, such as vehicle-mounted system 10a, when enabling the distribution service in a non-parking scenario.

[0229] In some embodiments, after receiving the second message, cloud server 30A or 30B can determine that vehicle 10 is online to ensure that information such as entry, pending payment orders, and departure of parking payment tasks for vehicle 10 is recommended to vehicle 10. As an example, cloud server 30A or 30B can record online status information of vehicle 10. For example, a value of 1 indicates that vehicle 10 is online, and a value of 0 indicates that vehicle 10 is offline. At this time, cloud server 30A or 30B can determine whether vehicle 10 is online by querying the value of the online status information of vehicle 10.

[0230] S603: Vehicle 10 obtains vehicle entry information from cloud server 30A or 30B.

[0231] In some embodiments, vehicle 10 may obtain vehicle entry information from cloud server 30A or 30B when entering or after entering the parking lot.

[0232] The entry information includes basic vehicle information, entry time, and parking fee rules. For example, basic vehicle information includes the vehicle's license plate number, and may also include vehicle type (e.g., electric or gasoline). Entry time can be displayed as year, month, day, hour, and minute, such as April 28, 2025, 08:00:30.

[0233] For example, some parking lot fees are as follows: 15 yuan per hour of parking time, with an additional 5 yuan for any increase in parking time less than one hour. Other fees are: 2 yuan for 0-15 minutes, 4 yuan for 15-30 minutes, 7 yuan for 30-60 minutes, and an additional 4 yuan for every 30 minutes thereafter. Still others fees are: a minimum of 30 minutes of free parking; if the free period exceeds one hour but is less than one hour, it is charged as one hour; any time exceeding one hour is charged in 15-minute increments, with any period less than 15 minutes counted as one cycle.

[0234] It is understandable that when a vehicle enters the parking lot, cloud server 30A or 30B can obtain the entry information of vehicle 10 and send this entry information to vehicle 10 if vehicle 10 is online (i.e., vehicle 10's distribution service is enabled). For example, when a vehicle enters the parking lot, parking lot equipment such as a gate can identify vehicle 10 through a camera, and the cloud server can obtain the entry information of vehicle 10 through the parking lot equipment. Thus, vehicle 10 can obtain its entry information from cloud server 30A or 30B when entering or after entering the parking lot.

[0235] S604: Vehicle 10 displays a second prompt message on the in-vehicle screen.

[0236] The second prompt message is used to indicate entry information.

[0237] In some embodiments, the vehicle 10 may display a second prompt message on the in-vehicle screen via a live window.

[0238] Specifically, vehicle 10 can use the distribution service in vehicle 10 to display the second prompt information on the in-vehicle screen via a live window.

[0239] As an example, referring to the scenario shown in FIG2D, after vehicle 10 enters the parking lot, vehicle 10 can pull up and display a live window 1101 on the in-vehicle screen 11 to display the entry prompt message "Entered".

[0240] S605: Vehicle 10 detects user exiting the vehicle and controls the vehicle to cut off power.

[0241] The descriptions of the user getting out of the vehicle and the vehicle power being cut off can be found in the descriptions of S403 and S404 shown in Figure 4 above.

[0242] In some embodiments, during a power outage, vehicle 10 may shut down the distribution service.

[0243] S606: Mobile phone 20 detected a disconnection from vehicle 10 and started the distribution service.

[0244] In some embodiments, if the vehicle is still powered on before the user gets out, the mobile phone 20 can establish a connection with the vehicle 10, such as the vehicle infotainment system 10a. Then, after the user gets out and the power is cut off, the mobile phone 20 can automatically disconnect from the vehicle 10.

[0245] In other embodiments, the mobile phone 20 can be wired to the vehicle 10 via a data cable before the user gets out of the vehicle, and the user can manually disconnect the data cable between the mobile phone 20 and the vehicle 10 after getting out of the vehicle to disconnect from the vehicle 10.

[0246] S607: Mobile phone 20 sends the first target message to cloud server 30A or 30B.

[0247] In some embodiments, the mobile phone 20 may activate the distribution service and send a first target message when it detects that it has lost connection with the vehicle 10.

[0248] The first target message (also known as the terminal service start message) is used to notify the cloud server 30A or 30B that the distribution service of the mobile phone 20 (i.e., the mobile phone) has been started, and the mobile phone 20 and the cloud server 30A or 30B communicate based on the distribution service.

[0249] In some embodiments, the distribution service of mobile phone 20 is enabled, and mobile phone 20 can use the distribution service to perform vehicle payment tasks. At this time, this application can enable the distribution service when the vehicle is in a parking scenario, such as when the distribution service is triggered by the disconnection of mobile phone 20 from vehicle 10, so as to avoid wasting the computing resources of mobile phone 20 when enabling the distribution service in a non-parking scenario.

[0250] In some embodiments, after receiving the first target message, cloud server 30A or 30B can determine that mobile phone 20 is online and modify the vehicle 10 associated with mobile phone 20 to be offline, to ensure that the parking payment information for vehicle 10 is recommended to mobile phone 20. As an example, cloud server 30A or 30B can record online flag information of mobile phone 20 to record its online status. For example, a value of 1 indicates that mobile phone 20 is online, and a value of 0 indicates that mobile phone 20 is offline. At this time, cloud server 30A or 30B can determine whether mobile phone 20 is online by querying the value of its online flag information.

[0251] S608: When the parking duration of vehicle 10 meets the jump condition, cloud server 30A or 30B sends the target jump fee information to mobile phone 20.

[0252] In some embodiments, if the parking duration meets the jump condition, it indicates that the parking fee is about to jump. For example, the jump condition is: whether the parking duration is about to reach the jump duration after 10 minutes.

[0253] It is understandable that the jump duration in the jump conditions is related to the parking lot's billing rules. For example, if the billing rule for a parking lot is 15 yuan per hour of parking time, and an additional 5 yuan is charged for each additional hour of parking time, the jump time could be 1 hour, 1.5 hours, 2 hours, 2.5 hours, etc.

[0254] As an example, if vehicle 10's parking duration is 50 minutes, and the parking duration is 10 minutes away from the one-hour jump time, the parking fee will increase by 5 yuan from the original 15 yuan after 10 minutes. In this case, the target jump fee information for vehicle 10 is used to indicate that the parking duration is 50 minutes, and the parking fee will increase by 5 yuan after 10 minutes.

[0255] In some embodiments, when the parking duration of vehicle 10 meets the jump condition and the distance between mobile phone 20 and vehicle 10 is less than or equal to a set distance (such as 1 kilometer or 2 kilometers), cloud server 30A or 30B generates target jump information for the vehicle and sends the target jump information to mobile phone 20.

[0256] S609: When the distance between the mobile phone 20 and the vehicle 10 is less than or equal to a set distance, the mobile phone 20 displays a first target prompt message on the terminal screen.

[0257] The first target prompt information (also known as the toll skipping prompt information) is used to indicate the target toll skipping information.

[0258] In some embodiments, the mobile phone 20 can display a first target prompt message on the vehicle screen via a live window.

[0259] Specifically, vehicle 10 can use the distribution service in mobile phone 20 to display the first target prompt information on the terminal screen through a live window.

[0260] As an example, referring to the scenario shown in FIG3B, when vehicle 10 is in a parking lot and the distance between mobile phone 20 and vehicle 10 is less than or equal to a set distance, when the parking time is 50 minutes (8:00-8:50), mobile phone 20 can receive the corresponding target billing information and pull up the real-time window 2101 to display the prompt message "50 minutes" (i.e., the first target prompt message).

[0261] It is understandable that before paying the parking fee, the mobile phone can obtain the fee information corresponding to different time intervals multiple times, such as the fee information corresponding to 1 hour, 1.5 hours, and 2 hours.

[0262] S610: Mobile phone 20 pays the parking fee in the target pending payment order in the target toll information.

[0263] In some embodiments, the target toll information includes the target toll order for vehicle 10.

[0264] It is understood that the vehicle's pending payment order, such as the target pending payment order, may include basic information about the vehicle 10 (e.g., license plate number), basic information about the parking lot (e.g., parking lot name), entry time, parking duration (or billing duration), and parking fee amount. The parking duration can be the time between the entry time and the current system time (e.g., 50 minutes), and the billing duration can be the time between the entry time and the current jump time (e.g., 1 hour) (e.g., 1 hour). Furthermore, in some embodiments, the vehicle's pending payment order, such as the target pending payment order, may also include parking fee payment discount information (e.g., coupons).

[0265] In some embodiments, mobile phone 20 can use the system wallet or a third-party payment application to pay for parking fees in a target order.

[0266] In some embodiments, mobile phone 20 can interact with cloud server 30A or 30B to pay parking fees for a target payment order for vehicle 10. As an example, cloud server 30A or 30B can be associated with mobile phone 20's system wallet, and parking fee payments can be made via mobile phone 20's system wallet from cloud server 30A or 30B. In this case, cloud server 30A or 30B can also be referred to as a payment server.

[0267] In other embodiments, mobile phone 20 can interact with a payment server to pay the parking fee for a target payment order for vehicle 10. This payment server is different from cloud servers 30A or 30B. As an example, this payment server is a server corresponding to a third-party payment application, which can perform parking fee payments based on the third-party payment application on mobile phone 20.

[0268] In some embodiments, if the distance between the mobile phone 20 and the vehicle 10 is greater than the set distance, the mobile phone 20 may shut down the distribution service.

[0269] S611: Cloud server 30A or 30B obtains the payment information of vehicle 10.

[0270] In some embodiments, when mobile phone 20 makes parking fee payment with cloud server 30A or 30B, cloud server 30A or 30B can record the payment status of the pending payment order for vehicle 10, such as the target pending payment order. Furthermore, when the payment status of the target pending payment order is "paid," cloud server 30A or 30B can generate payment information corresponding to the target pending payment order. At this time, cloud server 30A or 30B can pre-store this payment information.

[0271] In other embodiments, when mobile phone 20 makes parking fee payment with the payment server, cloud server 30A can record the payment status of pending payment orders for vehicle 10, such as the target pending payment order. Furthermore, when the payment status of the target pending payment order is "paid," cloud server 30A can generate payment information corresponding to the target pending payment order.

[0272] In other embodiments, when mobile phone 20 pays parking fees with the payment server, the payment server can interact with parking lot server 50 to pay the parking fees for vehicle 10. At this time, parking lot server 50 can record the payment status of pending payment orders for vehicle 10, such as the target pending payment order. Furthermore, when the payment status of the target pending payment order is "paid," cloud server 30B can obtain the payment status of the target pending payment order from parking lot server 50 and generate the corresponding paid information for the target pending payment order.

[0273] As an example, the payment information for vehicle 10 includes the departure time and parking fee amount of vehicle 10. For instance, the departure time is the time when vehicle 10 pays for the target order that is yet to be paid.

[0274] S612: Vehicle 10 detects that a user has entered the vehicle and controls the vehicle to power on.

[0275] In some embodiments, after the vehicle has been in the parking lot for a second period of time, i.e., after the vehicle 10 has been parked in the parking lot for a period of time (e.g., 53 minutes), the user returns to the parking lot from the mall, and the vehicle 10 can detect the user getting into the vehicle and control the vehicle to power on.

[0276] In some embodiments, after a user gets into the vehicle, the vehicle 10 can automatically establish a wireless connection with the mobile phone 20, or the user can manually establish a wired connection via a data cable.

[0277] In some embodiments, after the user gets into the vehicle and a wireless connection is established between the mobile phone 20 and the vehicle 10, the mobile phone 20 can automatically turn off the distribution service on the mobile phone 20 side.

[0278] S613: Vehicle 10 sends the first message to cloud server 30A or 30B.

[0279] In some embodiments, when the vehicle 10 is within a set geographical area of ​​the parking lot, during or after the vehicle is powered on, the vehicle 10 may initiate a distribution service and send a first message to the cloud server 30A or 30B.

[0280] In some embodiments, the first message is used to instruct cloud server 30A or 30B to send payment information to the vehicle. It is understood that the first message is also used to notify cloud server 30A or 30B that the vehicle's distribution service has been activated.

[0281] In some embodiments, after cloud server 30A or 30B receives the first message, it can re-determine that vehicle 10 is online and re-determine that mobile phone 20 associated with vehicle 10 is offline, to ensure that payment information for parking payment task of vehicle 10 is recommended to vehicle 10. At this time, cloud server 30A or 30B will no longer recommend parking payment task information to mobile phone 20. Similarly, cloud server 30A or 30B can reset the online status information of vehicle 10 to determine that vehicle 10 is online.

[0282] S614: Cloud server 30A or 30B sends payment information of vehicle 10 to vehicle 10, which includes payment information.

[0283] In some embodiments, the parking fee for the vehicle is paid by a mobile terminal, and the payment information mentioned above includes the payment information for vehicle 10. In this case, the payment information includes the paid information, which may include the departure time and parking fee amount of vehicle 10, and may also include the expected departure time of vehicle 10. As an example, the expected departure time represents the departure time at which no new fees will be incurred, such as the expected departure time being the actual departure time plus 15 minutes. For example, vehicle 10's paid departure time is 8:50, and the expected departure time is 9:05.

[0284] S615: Vehicle 10 displays the first prompt message on the in-vehicle screen.

[0285] The first prompt message is used to indicate payment information, which includes the vehicle's payment information.

[0286] In some embodiments, the vehicle 10 may display a first prompt message on the in-vehicle screen via a live window.

[0287] Specifically, vehicle 10 can use the distribution service in vehicle 10 to display the first prompt information on the in-vehicle screen through a live window.

[0288] As an example, referring to the scenario shown in FIG2D, after vehicle 10 enters the parking lot, vehicle 10 can pull up and display a live window 1103a on the in-vehicle screen 11 to display the prompt message "Payment Completed" (i.e., the first prompt message) through the live window.

[0289] In some embodiments, when a user clicks on the first prompt (fourth operation), such as clicking on the live view window 1103a shown in Figure 2D, the vehicle 10 can be triggered to display information related to the paid parking fee on the in-vehicle screen 11 (not shown). For example, the information related to the paid parking fee may include prompts such as "Paid" and "Please leave before 9:05, otherwise you will be charged again." In this way, the user can be informed that the current parking payment task is completed and that the departure time without incurring new fees is 9:05.

[0290] S616: Vehicle 10 detected that a vehicle had left the parking lot and shut down the vehicle distribution service.

[0291] In some embodiments, when vehicle 10 detects that it has left the parking lot, it can use the vehicle's distribution service to cancel the display of the live feed window on the in-vehicle screen and close the vehicle's distribution service. Referring to the scenario shown in FIG2C, when vehicle 10 detects that it has left the parking lot, the live feed window 1106 can be canceled on the in-vehicle screen 11 to display an interface 108 that does not include the live feed window.

[0292] In some embodiments, when a vehicle leaves the parking lot, the vehicle 10 receives departure information from the cloud server 30A or 30B, or detects that the vehicle 10's location has left a set geographical area of ​​the parking lot, then it is determined that the vehicle has left the parking lot. The departure information includes the vehicle's basic information, the vehicle's departure time, and the parking fee amount.

[0293] In some embodiments, departure information is obtained through interaction between cloud server 30B (also referred to as the second cloud server) and parking server 50, which is associated with the parking lot. In this case, the first cloud server and the second cloud server are the same, or the first cloud server includes both the second cloud server and the parking server.

[0294] Thus, this application enables vehicle payment via collaboration between the vehicle and a mobile terminal, such as a smartphone, allowing users to prepay parking fees on their phones before entering the vehicle. Specifically, after the user exits the vehicle, the phone displays a notification indicating an upcoming fee change, allowing the user to quickly and conveniently know the parking fee is about to change before leaving the parking lot. Furthermore, no specific parking application needs to be installed on the phone; instead, a distribution server can access a real-time window displaying information related to the vehicle payment task (such as entry, fee increase, and exit), providing users with timely and convenient access to this information, while also requiring minimal storage and computing resources from both the vehicle and the phone.

[0295] Referring to Figure 6B, a schematic diagram of a mobile terminal making parking fee payments according to an embodiment of this application is provided. The executing entity of this process is a mobile terminal, such as mobile phone 20. At this time, the target fee information received by mobile phone 20 includes the target payment order for the vehicle, and mobile phone 20 has a target payment application installed.

[0296] Specifically, the process shown in Figure 6B includes the following steps, that is, S610 shown in Figure 6A includes the following steps:

[0297] S6101: Mobile phone 20 receives the first target operation from the user's prompt information for the first target.

[0298] In some embodiments, the first target operation may be a user's click operation on the live window where the first target prompt information is located.

[0299] S6102: In response to the first target operation, the mobile phone 20 displays information about the target payment order on the terminal screen.

[0300] S6103: Mobile phone 20 receives a second target operation from the user on a target pending payment order.

[0301] S6104: In response to the second target operation, mobile phone 20 uses the target payment application to pay the parking fee in the target pending payment order.

[0302] Referring to the scenarios shown in Figures 3B and 3C, when the mobile phone 20 displays the prompt message "50 minutes" (i.e., the first target prompt message) on the interface 201 through the capsule-shaped live view window 2101, the user's click operation on the live view window 2101 is the first target operation. Subsequently, triggered by the first target operation, the mobile phone 20 can first display the card-shaped live view window 2021 to display the prompt message "Fee Increase Reminder" and the "Pay Now" control 2022, as well as information about the target pending payment order.

[0303] Referring again to the scenarios shown in Figures 3B and 3C, the second target operation may include multiple user operations, such as the user clicking the "Go to Payment" control 2022 in the real-time window 2021 of the card state, the user clicking the "Confirm Payment" control 2031 in the order confirmation page of interface 203, and the user long-pressing the "Fingerprint" control 2042 in interface 204. Then, triggered by the second target operation, the mobile phone 20 uses the target payment application to pay the parking fee in the target pending payment order. Furthermore, after the mobile phone 20 successfully pays the target pending payment order, a second target notification message can be displayed on the terminal screen 21 of the mobile phone 20, indicating that the parking fee in the target pending payment order has been successfully paid.

[0304] In some embodiments, the target payment application can be a system wallet or a third-party payment application. Furthermore, the payment method of the target payment application can be fingerprint payment, facial recognition payment, password payment, etc., and this application embodiment does not specifically limit this.

[0305] In this way, when users pay parking fees on mobile devices such as their phones, they can still perceive the parking fee amount and payment process without scanning a code, which helps improve the user's payment experience.

[0306] As shown in Figure 7A, in this vehicle payment method, the parking fee for vehicle 10 is paid by vehicle 10. This method can be executed interactively by vehicle 10, mobile phone 20, and cloud server. The cloud server can be cloud server 30A shown in Figure 5A or cloud server 30B shown in Figure 5B. At this time, cloud server 30A and cloud server 30B can be collectively referred to as the first cloud server, and mobile phone 20 is a mobile terminal.

[0307] Specifically, the method shown in Figure 7A includes the following steps:

[0308] S701: Vehicle 10 detects that the vehicle's location has entered the designated geographical area of ​​the parking lot and starts the vehicle distribution service.

[0309] S702: Vehicle 10 sends a second message to cloud server 30A or 30B.

[0310] S703: Vehicle 10 obtains vehicle entry information from cloud server 30A or 30B.

[0311] In some embodiments, vehicle 10 may obtain vehicle entry information from cloud server 30A or 30B when entering or after entering the parking lot.

[0312] S704: Vehicle 10 displays a second prompt message on the in-vehicle screen.

[0313] The second prompt message is used to indicate entry information.

[0314] S705: Vehicle 10 detects user exiting the vehicle and controls the vehicle to cut off power.

[0315] S706: Mobile phone 20 detected a disconnection from vehicle 10 and started the distribution service.

[0316] S707: Mobile phone 20 sends the first target message to cloud server 30A or 30B.

[0317] S708: When the parking duration of vehicle 10 meets the jump condition, cloud server 30A or 30B sends the target jump fee information to mobile phone 20.

[0318] S709: When the distance between the mobile phone 20 and the vehicle 10 is less than or equal to the set distance, the mobile phone 20 obtains the target toll information and displays the first target prompt information on the terminal screen.

[0319] S702 to S709 are the same as S602 to S609 in Figure 6A, and will not be described again here. Furthermore, compared to the process shown in Figure 6A, the process shown in Figure 7A does not involve payment of parking fees on the mobile phone 20 side.

[0320] S710: Vehicle 10 detects that a user has entered the vehicle and controls the vehicle to power on.

[0321] S711: Vehicle 10 sends the first message to cloud server 30A or 30B.

[0322] Among them, S710 to S711 are the same as S611 to S612 in Figure 6A, and will not be described again here.

[0323] S712: Cloud server 30A or 30B sends payment information for vehicle 10 to vehicle 10, including the first order to be paid.

[0324] In some embodiments, cloud server 30A or 30B may first obtain the first payment order for the current vehicle 10 based on the first message. For example, cloud server 30B may obtain the first payment order from parking server 50 based on the first message. Then, cloud server 30A or 30B may generate payment information including the first payment order.

[0325] S713: Vehicle 10 displays the first prompt information on the vehicle screen.

[0326] The first prompt information is used to indicate payment information, which includes the vehicle's first pending payment order.

[0327] In some embodiments, the vehicle 10 may display a first prompt message on the in-vehicle screen via a live window.

[0328] Specifically, vehicle 10 can use the distribution service in vehicle 10 to display the first prompt information on the in-vehicle screen through a live window.

[0329] As an example, referring to the scenario shown in FIG2A or FIG2B, before the vehicle 10 leaves the parking lot, the vehicle 10 can pull up and display a live window 1103 on the in-vehicle screen 11 to display the prompt message "Unpaid" (i.e., the first prompt message) through the live window.

[0330] S714: Vehicle 10 pays the parking fee for the first pending payment order.

[0331] It is understandable that the first payment order for a vehicle may include basic information about the vehicle, basic information about the parking lot, entry time, parking duration (or billing duration), parking fee amount, etc.

[0332] The aforementioned target pending payment order and the first pending payment order are usually different pending payment orders corresponding to different parking durations, and at this time, different pending payment orders have different parking fee amounts.

[0333] In some embodiments, a vehicle payment application is installed in the vehicle 10. The vehicle 10 uses the vehicle payment application to pay the parking fee in the first pending payment order. For example, the vehicle payment application is the system wallet or a third-party payment application in the vehicle 10. In this case, the vehicle 10 has payment capability, without the need for the mobile phone 20, and the user can complete the parking fee payment only on the vehicle 10 side.

[0334] In some embodiments, vehicle 10 can interact with cloud servers 30A or 30B to pay the parking fee in the first pending payment order of vehicle 10. As an example, cloud servers 30A or 30B can be associated with the system wallet of vehicle 10, and parking fee payments can be made through the system wallet of vehicle 10 on cloud servers 30A or 30B. In this case, cloud servers 30A or 30B can also be referred to as payment servers.

[0335] In other embodiments, vehicle 10 can interact with a payment server to pay the parking fee in the first pending payment order for vehicle 10. This payment server is different from cloud servers 30A or 30B. As an example, this payment server is a server corresponding to a third-party payment application, and the payment server can perform parking fee payments based on the third-party payment application in vehicle 10.

[0336] In some embodiments, where the payment information includes the vehicle's paid information, a fourth operation is received from the user on the first prompt information displayed on the in-vehicle screen; in response to the fourth operation, the paid information is displayed on the in-vehicle screen, which includes the vehicle's paid departure time and the amount of the parking fee, and the parking fee was paid by the mobile terminal.

[0337] As an example, when a user clicks on the first prompt message, such as clicking on the live view window 1106 shown in Figure 2D (the fourth operation), the vehicle 10 can trigger the display of payment information related to interface 107 on the in-vehicle screen 11. For example, the information in interface 107 may include prompts such as "Paid" or "Your parking fee has been paid. Please leave before 10:45, otherwise you will be charged again." In this way, the user can be informed that the current parking payment task is completed and that the departure time without incurring new fees is 10:45.

[0338] S715: Vehicle 10 detected that a vehicle had left the parking lot and shut down the vehicle distribution service.

[0339] S715 is the same as S616 in Figure 6A, and will not be described again here.

[0340] In addition, in some other embodiments, the steps in S706 to S709 may not be performed in the method shown in FIG7A. That is, the cloud server only recommends vehicle payment task information to vehicle 10, but does not recommend vehicle payment task information to mobile terminals such as mobile phone 20.

[0341] Thus, this application enables vehicle payment through collaboration between the vehicle and a mobile terminal, such as a smartphone. After the user gets into the vehicle, they can pay the parking fee directly on the vehicle's side. Specifically, after the user gets in, the vehicle can display a notification for the first pending payment order, allowing the user to quickly and conveniently pay the parking fee before leaving the parking lot. Furthermore, no specific parking application needs to be installed on the vehicle; instead, a distribution server can use a real-time window to display real-time information related to the vehicle payment task (such as entry and exit), allowing users to access this information promptly and conveniently, while also requiring relatively low storage and computing resources from the vehicle.

[0342] Referring to Figure 7B, a schematic diagram of a vehicle parking fee payment process provided in an embodiment of this application is shown. The vehicle 10 is the executing entity of this process. At this time, the payment information received by the vehicle 10 includes the vehicle's first pending payment order, and the vehicle 10 has a target payment application installed.

[0343] Specifically, the process shown in Figure 7B includes the following steps, that is, S714 shown in Figure 7A includes the following steps:

[0344] S7141: Vehicle 10 receives the user's first operation on the first prompt information displayed on the vehicle screen.

[0345] In some embodiments, the first operation may be a user's click operation on the live window where the first prompt information is located.

[0346] S7142: In response to the first operation, vehicle 10 displays information about the first pending payment order on the vehicle screen.

[0347] S7143: Vehicle 10 receives the user's second operation on the first pending payment order.

[0348] S7144: In response to the second operation, vehicle 10 uses the in-vehicle payment application to send a first payment request message to the payment server.

[0349] The first payment request message is used to request payment for the first pending payment order.

[0350] The payment server may be the same as or different from the first cloud server, namely cloud server 30A or 30B.

[0351] In some embodiments, the above-mentioned in-vehicle payment application uses a target authentication method to pay the parking fee in the first pending payment order, wherein the target authentication method includes at least one of the following: digital password authentication, image password authentication, and facial image authentication.

[0352] In some embodiments, a vehicle-mounted camera is installed on the inner side of the A-pillar of the vehicle 10. This camera is used to capture the user's facial image, and facial image authentication is used to authenticate the facial image captured by the camera. In this case, the user only needs to have their face facing the camera on the A-pillar to complete authentication, thus conveniently and with good privacy in paying parking fees. Furthermore, in other embodiments, a vehicle-mounted camera is installed on the rearview mirror of the vehicle 10. This camera is used to capture the user's facial image, and facial image authentication is used to authenticate the facial image captured by the camera.

[0353] S7145: Vehicle 10 receives the first payment response message sent by the payment server.

[0354] The first payment response message indicates that the parking fee in the first pending payment order has been successfully paid.

[0355] S7146: Based on the first payment response message, vehicle 10 displays a third prompt message on the vehicle screen.

[0356] The third notification message indicates that the parking fee in the first pending payment order has been successfully paid.

[0357] Referring to the scenario shown in Figure 2A, when vehicle 10 displays the prompt message "Pending Payment" (i.e., the first prompt message) on interface 102 via a capsule-shaped live view window 1102, the user's click operation on the live view window 1102 is the first operation. Subsequently, triggered by the first operation, vehicle 10 can display a card-shaped live view window 1031 to show the prompt message "Fee Increase Reminder" and the "Go to Payment" control 1032, as well as information about the first pending payment order.

[0358] Referring again to the scenario shown in Figure 2B, the second operation may include multiple user operations, such as the user clicking the "Go to Payment" control 1032 in the real-time window 1031 of the card state, the user clicking the "Confirm Payment" control 1041 in the order confirmation page of interface 104, and the user long-pressing the "Face" control 1052 in interface 105. Furthermore, triggered by the second operation, the vehicle 10 can capture a facial image through the camera on the A-pillar, and upon successful facial image authentication, use the in-vehicle payment application to pay the parking fee in the first pending payment order.

[0359] In some embodiments, the payment method of the in-vehicle payment application can be not only facial recognition payment, but also password payment, etc. This application embodiment does not specifically limit this.

[0360] In some embodiments, the vehicle 10 in this application may employ a distribution service to display a third notification message on the in-vehicle screen via a live window. For example, the third notification message may be the message "Payment Completed".

[0361] In some embodiments, the first payment response message may include payment information corresponding to the first pending payment order of vehicle 10. Similarly, after the user clicks on the third prompt message, vehicle 10 may also display the payment information of vehicle 10.

[0362] Referring to the scenario shown in Figure 2C, after paying the parking fee, vehicle 10 can display the message "Paid" (third notification message) in the real-time window 1106 as shown in Figure 2C to inform the user that the parking fee has been successfully paid. Furthermore, after the user clicks on the real-time window 1106, vehicle 10 can pull up a card-style real-time window 1071 on interface 107 to display the notification message "Paid", the expected departure time "10:45", and other payment information.

[0363] In this way, users can pay parking fees directly at the vehicle without using their mobile phones to scan a QR code; they can complete the payment with a single click. They can also see the parking fee amount and the payment process, thus improving the user's payment experience.

[0364] Next, the process of vehicle payment method in the second parking payment scenario described above will be explained.

[0365] Referring to Figure 8A, a flowchart illustrating a vehicle payment method provided in an embodiment of the application is shown. In this process, the user remains inside the vehicle and can pay the parking fee via a mobile terminal, such as a mobile phone.

[0366] Specifically, Figure 8A includes the following steps:

[0367] S601 to S604 are the same as those shown in Figure 6A, and will not be described again here.

[0368] S605A: Vehicle 10 controls vehicle power cut-off.

[0369] It is understandable that the difference between S605A and S605 in Figure 6A is that the user did not get out of the vehicle after vehicle 10 stopped. It is also understandable that mobile phone 20 can disconnect from vehicle 10 after the vehicle 10 is powered off.

[0370] S606 to S611 are the same as those shown in Figure 6A, and will not be described again here.

[0371] S612A: Vehicle 10 controls vehicle power-on.

[0372] It is understandable that the difference between S612A and S612 in Figure 6A is that the user remains inside the vehicle after the vehicle 10 is parked. It is also understandable that the mobile phone 20 can re-establish a connection with the vehicle 10 after it is powered on.

[0373] S613 to S616 are the same as those shown in Figure 6A, and will not be described again here.

[0374] Thus, after the vehicle enters the parking lot, if the vehicle 10 stops and is powered off, and the user is still inside the vehicle, the user can pay the parking fee on a mobile terminal such as a mobile phone 20, which is beneficial to improving the user's payment experience.

[0375] Referring to Figure 8B, a flowchart illustrating a vehicle payment method provided in an embodiment of the application is shown. In this process, the user remains inside the vehicle and can pay the parking fee from the side of the vehicle.

[0376] Specifically, Figure 8B includes the following steps:

[0377] S701 to S704 are the same as those shown in Figure 7A, and will not be described again here.

[0378] S705A: Vehicle 10 controls vehicle power cut-off.

[0379] It is understandable that the difference between S705A and S705 in Figure 7A is that the user did not get out of the vehicle after vehicle 10 stopped. It is also understandable that mobile phone 20 can disconnect from vehicle 10 after the vehicle 10 is powered off.

[0380] S706 to S609 are the same as those shown in Figure 6A, and will not be described again here.

[0381] S710A: Vehicle 10 controls vehicle power-on.

[0382] It is understandable that the difference between S710A and S710 in Figure 7A is that the user remains inside the vehicle after vehicle 10 is parked. It is also understandable that mobile phone 20 can re-establish a connection with vehicle 10 after vehicle 10 is powered on.

[0383] S711 to S715 are the same as S611 to S615 shown in Figure 7A, and will not be described again here.

[0384] Thus, after the vehicle enters the parking lot, if vehicle 10 is parked and powered off and the user is still inside the vehicle, the user can pay the parking fee on the side of vehicle 10, which helps to improve the user's payment experience.

[0385] Next, the process of vehicle payment method in the third parking payment scenario described above will be explained.

[0386] Referring to Figure 9, a flowchart illustrating a vehicle payment method provided in an embodiment of the application is shown. In this process, the user remains inside the vehicle and the vehicle is not powered off; the user can pay the parking fee from the side of the vehicle.

[0387] Specifically, Figure 9 includes the following steps:

[0388] S901 to S904 are the same as S601 to S604 shown in Figure 6A, and will not be described again here.

[0389] S905: When the parking duration of vehicle 10 meets the jump condition, cloud server 30A or 30B sends the first jump fee information to vehicle 10.

[0390] The first fee information includes the first order with outstanding fees.

[0391] The description of Figure S905 can be found in the related description of S608 shown in Figure 6A. Furthermore, the difference between S905 and Figure S608 is that the subject of the cloud server's recommended toll information is vehicle 10.

[0392] In some embodiments, the vehicle’s first toll information includes the vehicle’s pending toll order (such as referred to as the first pending toll order).

[0393] In some embodiments, after a vehicle enters a parking lot, if a user is detected inside the vehicle within a first time (i.e., a period of time), the vehicle's payment information is obtained from a first cloud server. The payment information is the vehicle's first fee information, which includes a first pending payment order.

[0394] S906: Vehicle 10 displays the first prompt message on the terminal screen.

[0395] The first prompt message indicates the first toll skipping information. At this time, the aforementioned first toll skipping information is payment information, which includes the vehicle's pending payment order (such as referred to as the first pending payment order).

[0396] In some embodiments, the vehicle 10 may employ a distribution service to display a first prompt message on the in-vehicle screen via a live window.

[0397] Similarly, the interface changes on the vehicle screen displaying the first prompt message indicating the toll increase are similar to the interface changes on the mobile phone 20 side shown in Figure 2B, which will not be described in detail here.

[0398] S907: Vehicle 10 pays the parking fee in the first pending payment order.

[0399] Similarly, the description of S907 can be found in the descriptions of S714 shown in Figure 7A and the related descriptions of S7141 to S7146 shown in Figure 7B, which will not be repeated here.

[0400] S908 is described in the same way as S715 shown in Figure 7A, and will not be repeated here.

[0401] Therefore, in parking payment scenarios, if the user has not left the vehicle and the vehicle's power is not off, the vehicle can obtain information about the upcoming parking fee change and promptly notify the user. This allows users to pay parking fees on the vehicle side in a timely manner, improving the payment experience.

[0402] Furthermore, based on the vehicle payment system shown in Figure 5B, and referring to Figure 10, the vehicle payment method in this embodiment will be described. Specifically, the method shown in Figure 10 is executed interactively by the cloud server 30A and the parking lot server 50, and includes the following steps:

[0403] S1001: When a vehicle arrives at the entrance of the parking lot, the parking lot server 50 obtains the vehicle's entry request message and generates an entry instruction message.

[0404] The entry instruction message is used to indicate that the vehicle can be released, while the entry request message is sent by the parking equipment when it detects that a vehicle has arrived at the entrance of the parking lot.

[0405] In some embodiments, when the parking server 50 and the parking device 40 are different devices, when a vehicle arrives at the entrance of the parking lot, the parking device 40 can identify the vehicle 10, such as by capturing an image of the vehicle 10's license plate, and generate an entry request message based on the identified basic information of the vehicle 10. This entry request message is then sent to the parking server 50. Subsequently, the parking server 50 can generate an entry instruction message based on the entry request message and send this message to the parking device 40, instructing the parking device 40 to allow the vehicle 10 to enter the parking lot.

[0406] S1002: Parking server 50 sends a vehicle entry notification message to cloud server 30B.

[0407] S1003: Cloud server 30B generates vehicle entry information based on the entry notification message.

[0408] S1004: Cloud server 30B sends entry information to the vehicle.

[0409] The entry message includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules. The entry notification message includes at least the vehicle's basic information and the vehicle's entry time.

[0410] S1005: Before a vehicle leaves the parking lot, the parking lot server 50 sends the vehicle's first pending payment order or vehicle payment information to the cloud server 30B.

[0411] S1006: Cloud server 30B sends vehicle payment information to vehicle 10.

[0412] In some embodiments, before the vehicle leaves the parking lot, the cloud server 30B sends the vehicle's payment information to the vehicle 10. The payment information includes payment information or a first pending payment order.

[0413] The parking fee for a vehicle in a parking lot is paid by either the mobile terminal associated with the vehicle or by the vehicle itself.

[0414] In some embodiments, the cloud server 30B can send an order query message to the parking server 50, the order query message being used to query the vehicle's outstanding payment orders. Furthermore, the parking server 50 can send an order response message to the cloud server 30B based on the order query message, the order response message including the vehicle's outstanding payment orders.

[0415] In some embodiments, the cloud server may receive a first message sent by the vehicle, wherein the first message is used to instruct the first cloud server to send payment information to the vehicle, and the first message is sent by the vehicle after the user gets in and the vehicle is powered on.

[0416] It is understood that the order inquiry message is sent by the cloud server based on the first message and / or when the vehicle's parking duration meets the jump condition. As an example, the pending payment order in the order response message obtained by the cloud server based on the first message can be the aforementioned first pending payment order.

[0417] In some embodiments, the order query message is sent by the cloud server 30B when the vehicle's parking duration meets the jump condition. In this case, the order response message includes the vehicle's pending payment order, which is the pending payment order corresponding to the current jump information, such as the target pending payment order mentioned above.

[0418] In some embodiments, the cloud server may receive a first target message sent by a mobile terminal associated with the vehicle. The first target message is used to instruct the first cloud server (i.e., cloud server 30B) to send the vehicle's target fare information to the mobile terminal, such as mobile phone 20. The first target message is sent after the user gets out of the car in the parking lot and when the mobile terminal, such as mobile phone 20, disconnects from the vehicle.

[0419] S1007: Parking server 50 receives payment notification message and confirms that the parking fee for the vehicle has been paid based on the payment notification message.

[0420] In some embodiments, the payment notification message is obtained by cloud server 30B from the payment server or the cloud server.

[0421] The payment notification message indicates that the parking fee for the vehicle has been paid.

[0422] S1008: When a vehicle arrives at the exit of the parking lot, the parking server 50 obtains the vehicle's departure request message and generates a departure instruction message if the parking fee has been paid.

[0423] The departure instruction message is used to instruct the vehicle to leave.

[0424] In some embodiments, when the parking server 50 and the parking device 40 are different devices, when a vehicle arrives at the exit of the parking lot, the parking device 40 can identify the vehicle 10, such as by capturing an image of the vehicle 10's license plate, and generate a departure request message based on the identified basic information of the vehicle 10, and send the departure request message to the parking server 50. Then, the parking server 50 can generate a departure instruction message based on the departure request message, and send the departure instruction message to the parking device 40 to instruct the parking device 40 to allow the vehicle 10 to leave the parking lot.

[0425] S1009: Parking server 50 generates a vehicle departure notification message based on the departure request message.

[0426] S1010: Parking server 50 sends a departure notification message to cloud server 30B.

[0427] S1011: Cloud server 30B generates vehicle departure information based on the departure notification message.

[0428] S1012: Cloud server 30B sends departure information to the vehicle.

[0429] The departure information includes the vehicle's basic information, departure time, and parking fee.

[0430] It is understood that the parking lot server in this application is typically a public server. In this case, the messages pushed by the parking lot server, such as payment orders, may contain redundant or insecure information such as advertisements. Cloud servers, on the other hand, can be vendor-manufactured servers such as Huawei Cloud. TM Servers. Data transmission security between vehicles or mobile devices and cloud servers is generally higher than that between vehicles and parking lot servers. Furthermore, cloud servers can push filtered information to vehicles or mobile devices. Therefore, after obtaining vehicle payment task information from the parking lot server, the cloud server can remove advertisements and other irrelevant information, filtering out information related to vehicle entry, over-payment, and exit. This ensures that the information on pending payments recommended by the cloud server for vehicles, including entry and exit times, as well as the information on pending payments recommended for mobile devices, is highly secure and free of redundant information such as advertisements. This further enhances the user's payment experience.

[0431] The hardware structure of the vehicle in this application will be described next.

[0432] Figure 11 is a structural schematic diagram of a vehicle provided in an embodiment of this application.

[0433] Vehicle 10 may include various subsystems, such as a mobility system 1020, a sensor system 1040, a control system 1060, one or more peripheral devices 1080, a power supply 1010, and a user interface 1016. Optionally, the vehicle may include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and component of the vehicle may be interconnected via wired or wireless means (e.g., Bluetooth).

[0434] The propulsion system 1020 may include components that provide powered motion for the vehicle. In one embodiment, the propulsion system 1020 may include an engine 1018, an energy source 1019, a transmission 1120, and wheels 1121.

[0435] Engine 1018 can be an internal combustion engine, an electric motor, an air-compressed engine, or other combinations of engines, such as a hybrid engine consisting of a gasoline engine and an electric motor, or a hybrid engine consisting of an internal combustion engine and an air-compressed engine. Engine 1018 converts energy source 1019 into mechanical energy. Examples of energy source 1019 include gasoline, diesel, other petroleum-based fuels, propane, other compressed gas-based fuels, ethanol, solar panels, batteries, and other sources of electricity. Energy source 1019 can also provide energy to other systems of the vehicle. Transmission 1120 transmits mechanical power from engine 1018 to wheels 1121. Transmission 1120 may include a gearbox, a differential, and a drive shaft. In one embodiment, transmission 1120 may also include other components, such as a clutch. The drive shaft may include one or more shafts that can be coupled to wheels 1121.

[0436] Sensor system 1040 may include several sensors that sense information about the vehicle's position. For example, sensor system 1040 may include a positioning system 1122 (which may be a GPS system, a BeiDou system, or another positioning system), an inertial measurement unit (IMU) 1124, a radar 1126, a laser rangefinder 1128, and a camera 1130. Sensor system 1040 may also include sensors for the monitored vehicle's internal systems (e.g., an in-vehicle air quality monitor, fuel gauge, oil temperature gauge, etc.). Sensing data from one or more of these sensors can be used to detect objects and their corresponding characteristics (e.g., position, shape, orientation, speed, etc.). This detection and identification is a key function for the safe operation of autonomous vehicles. Furthermore, sensor system 1040 may also include other sensors such as cabin sensors (i.e., seat sensors) and door sensors.

[0437] The positioning system 1122 can be used to estimate the vehicle's geographical location, such as the latitude and longitude information of the vehicle's location. The IMU 1124 is used to sense changes in the vehicle's position and orientation based on inertial accelerometer. In one embodiment, the IMU 1124 can be a combination of an accelerometer and a gyroscope. The radar 1126 can use radio signals to sense objects in the vehicle's surrounding environment, specifically millimeter-wave radar or lidar. In some embodiments, in addition to sensing objects, the radar 1126 can also be used to sense the speed and / or direction of travel of objects. The laser rangefinder 1128 can use lasers to sense objects in the environment in which the vehicle is located. In some embodiments, the laser rangefinder 1128 may include one or more laser sources, a laser scanner, and one or more detectors, as well as other system components. The camera 1130 can be used to capture multiple images of the vehicle's surrounding environment. The camera 1130 can be a still camera or a video camera. In some embodiments, the number of cameras 1130 is one or more, such as including cameras (i.e., webcams) mounted on the vehicle's A-pillars.

[0438] The control system 1060 controls the operation of the vehicle and its components. The control system 1060 may include various components, including a steering system 1132, a throttle 1134, a braking unit 1136, an electronic control unit (ECU) 1138, and a vehicle control unit (VCU) 1140.

[0439] The steering system 1132 is operable to adjust the vehicle's forward direction. For example, in one embodiment, it may be a steering wheel system. The throttle 1134 controls the operating rate of the engine 1018 and thus the vehicle's speed. The braking unit 1136 controls the vehicle's deceleration. The braking unit 1136 may use friction to slow down the wheels 1121. In other embodiments, the braking unit 1136 may convert the kinetic energy of the wheels 1121 into electrical current. The braking unit 1136 may also take other forms to slow down the rotational speed of the wheels 1121 to control the vehicle's speed. The vehicle electronic control unit 1138 may be implemented as a single ECU or multiple ECUs on the vehicle, configured to communicate with peripheral devices 1080 and sensor systems 1040. The vehicle ECU 1138 may include at least one processor 11381 and a memory 11382 (read-only memory, ROM). At least one processor can be implemented or executed using one or more general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described herein. In particular, at least one processor can be implemented as one or more microprocessors, controllers, microcontroller units (MCUs), or state machines. Furthermore, at least one processor can be implemented as a combination of computing devices, such as digital signal processors or microprocessors, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations. ROM can provide data storage, including storage for addresses, routes, and directions of travel as described in this application.

[0440] VCU1140 can provide ECU1138 with information such as vehicle engine status, speed, gear, and steering wheel angle.

[0441] The vehicle interacts with external sensors, other vehicles, other computer systems, or users via peripheral device 1080. Peripheral device 1080 may include wireless communication system 1146, navigation system 1148, microphone 1150 and / or speaker 1152, and in-vehicle screen 1154. In some embodiments, peripheral device 1080 provides a means for the vehicle's user to interact with user interface 1016. For example, navigation system 1148 may be implemented as part of an in-vehicle entertainment system, in-vehicle display system, in-vehicle instrument cluster, etc. In one practical embodiment, navigation system 1148 is implemented to include or cooperate with sensor system 1040, which derives the vehicle's current geographical location in real time or substantially in real time. Navigation system 1148 is configured to provide navigation data to the vehicle's driver. Navigation data may include vehicle location data, suggested route planning instructions, and visible map information for the vehicle operator. Navigation system 1148 may present this location data to the vehicle's driver via display elements or other presentation devices. The vehicle's current location can be described by one or more of the following: triangulation location, latitude / longitude location, x and y coordinates, or any other symbol or measurement method indicating the vehicle's geographical location. The in-vehicle screen 1154 includes one or more screens, such as a central control screen, rear-seat screens, and instrument panel screens.

[0442] User interface 1016 can also operate navigation system 1148 to receive user input. Navigation system 1148 can be operated via a touchscreen. Navigation system 1148 provides route planning and navigation capabilities when the user inputs geographic location values ​​for the origin and destination. In other cases, peripheral device 1080 can provide a means for the vehicle to communicate with other devices located within the vehicle. For example, microphone 1150 can receive audio (e.g., voice commands or other audio input) from the user in the vehicle. Similarly, speaker 1152 can output audio to the user in the vehicle. Wireless communication system 1146 can wirelessly communicate with one or more devices, either directly or via a communication network. For example, wireless communication system 1146 can use 3G cellular communication, or 4G cellular communication, such as Long Term Evolution (LTE), or 5G cellular communication. Wireless communication system 1146 can communicate using WiFi and wireless local area network (WLAN). In some embodiments, wireless communication system 1146 can communicate directly with devices using an infrared link, Bluetooth, or ZigBee. Other wireless protocols, such as various vehicle communication systems, such as wireless communication system 1146, may include one or more dedicated short range communications (DSRC) devices that may include public and / or private data communications between vehicles and / or roadside stations.

[0443] The power source 1010 can provide power to various components of the vehicle. In one embodiment, the power source 1010 can be a rechargeable lithium-ion or lead-acid battery. One or more such battery packs can be configured to provide power to various components of the vehicle. In some embodiments, the power source 1010 and the energy source 1019 can be implemented together, for example, in some fully electric vehicles.

[0444] Alternatively, one or more of these components may be installed separately from or associated with the vehicle. For example, the memory 11382 may exist partially or completely separately from the vehicle. The components may be communicatively coupled together in a wired and / or wireless manner.

[0445] Optionally, the above components are just an example. In actual applications, the components in the above modules may be added or deleted according to actual needs. Figure 11 should not be construed as a limitation on the embodiments of this application.

[0446] The aforementioned vehicles may include cars, trucks, motorcycles, buses, boats, lawnmowers, recreational vehicles, amusement park vehicles, construction equipment, trams, golf carts, and handcarts, etc., and this application does not impose any particular limitation.

[0447] The architecture diagram of the system applicable to the embodiments of this application has been described above with reference to Figure 11. In order to better understand the technical solutions provided by the embodiments of this application, the research ideas of the technical solutions described in this application will be specifically explained below.

[0448] Figure 12 illustrates a hardware structure diagram of a mobile terminal according to an embodiment of this application. The mobile terminal may be, for example, a mobile phone, a smart wearable device (such as a smartwatch), etc. Taking a mobile phone as an example, the mobile terminal may include a processor 310, an external memory interface 320, an internal memory 321, a display screen 330, a camera 340, antenna 1, antenna 2, a mobile communication module 350, and a wireless communication module 360, etc.

[0449] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the mobile terminal. In other embodiments, the mobile terminal may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0450] Processor 310 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, time-frequency codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0451] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a structural limitation on the mobile terminal. In other embodiments of this application, the mobile terminal may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0452] The external storage interface 320 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the mobile terminal. The external storage card communicates with the processor 310 through the external storage interface 320 to perform data storage functions. For example, music, time and frequency files can be saved on the external storage card.

[0453] Internal memory 321 can be used to store executable program code, including instructions. Processor 310 executes various functional applications and data processing of the mobile terminal by running the instructions stored in internal memory 321. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the mobile terminal (such as time-frequency stream data), etc. In addition, internal memory 321 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 310 executes various functions and data processing of the mobile terminal by running instructions stored in internal memory 321 and / or instructions stored in memory disposed in the processor.

[0454] The wireless communication function of the mobile terminal can be implemented through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor.

[0455] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the mobile terminal can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0456] The mobile communication module 350 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in mobile terminals. The mobile communication module 350 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 350 may be housed in the processor 310. In some embodiments, at least some functional modules of the mobile communication module 350 and at least some modules of the processor 310 may be housed in the same device.

[0457] In some embodiments, the mobile terminal initiates or receives call requests through the mobile communication module 350 and the antenna 1.

[0458] In addition, an operating system runs on top of the aforementioned components. Examples include iOS and Android. TM Operating system, Windows TM Operating systems, etc. Applications can be installed and run on the operating system. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant content in any of the mobile terminals provided above can be referred to the corresponding method embodiments provided above, and will not be repeated here.

[0459] Referring to Figure 13, a hardware structure diagram of a server, such as a cloud server, is shown according to an embodiment of this application. The server shown in Figure 13 includes at least one processor 111, at least one memory 112, at least one transceiver 113, at least one network interface 114, and one or more antennas 115. The processor 111, memory 112, transceiver 113, and network interface 114 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited in this respect. The antenna 115 is connected to the transceiver 113. The network interface 114 is used to enable the server to connect to other communication devices through a communication link. For example, the network interface 114 may include a network interface between the server and servers in the core network, such as an S1 interface; the network interface may also include a network interface between the server and other servers, such as an X2 or Xn interface.

[0460] Specifically, the processor 111 shown in Figure 13 can perform the server processing actions in the above method, the memory 112 can perform the storage actions in the above method, the transceiver 113 and the antenna 115 can perform the air interface transmission and reception actions in the above method, and the network interface 114 can perform the interaction actions with the server or other servers in the above method.

[0461] The processor in this application embodiment, such as processor 111, may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., which are various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing. The processor may be a separate semiconductor chip or integrated with other circuits into a single semiconductor chip. For example, it may be integrated with other circuits (such as encoding / decoding circuits, hardware acceleration circuits, or various bus and interface circuits) to form a SoC (System-on-a-Chip), or it may be integrated as a built-in processor in an ASIC. The ASIC with the integrated processor may be packaged separately or packaged together with other circuits. In addition to including cores for executing software instructions to perform calculations or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), PLDs (programmable logic devices), or logic circuits that implement dedicated logic operations.

[0462] The memory in the embodiments of this application may include at least one of the following types: read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; or electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0463] The memory 112 can exist independently and be connected to the processor 111. Optionally, the memory 112 can be integrated with the processor 111, for example, integrated into a single chip. The memory 112 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 111. The various types of computer program code being executed can also be considered as drivers for the processor 111. For example, the processor 111 executes the computer program code stored in the memory 112 to implement the technical solutions of the embodiments of this application.

[0464] Transceiver 113 can be used to support the reception or transmission of radio frequency (RF) signals between the server and other devices. Transceiver 113 can be connected to antenna 115. Transceiver 113 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 115 can receive RF signals. The receiver Rx of transceiver 113 is used to receive RF signals from the antennas, convert the RF signals into digital baseband signals or digital intermediate frequency (IF) signals, and provide the digital baseband signals or IF signals to processor 111 so that processor 111 can perform further processing on the digital baseband signals or IF signals, such as demodulation and decoding. Furthermore, the transmitter Tx in transceiver 113 is also used to receive modulated digital baseband signals or IF signals from processor 111, convert the modulated digital baseband signals or IF signals into RF signals, and transmit the RF signals through one or more antennas 115. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF processing is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF processing is also adjustable. Digital baseband signals and digital IF signals can be collectively referred to as digital signals.

[0465] Furthermore, this application also provides a computer-readable storage medium storing instructions that, when executed on one or more computing devices, cause the one or more computing devices to perform the vehicle payment method described above.

[0466] Furthermore, this application also provides a computer program product. When executed by one or more computing devices, the computer program product enables the computing devices to execute any of the aforementioned vehicle payment methods. The computer program product can be a software installation package. When any of the aforementioned communication methods is required, the computer program product can be downloaded and executed on a computer.

[0467] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer program modules or module code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0468] Computer program modules or module code can be applied to input instructions to perform the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0469] Module code can be implemented using a high-level modular language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used to implement module code when needed. The mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0470] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable storage media. Therefore, machine-readable storage media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, optical discs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable storage media include any type of machine-readable storage media suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0471] In this specification, the reference to "an embodiment" or "an embodiment" means that a specific feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technology disclosed according to an embodiment of this application. The appearance of the phrase "in an embodiment" in various places in the specification does not necessarily refer to the same embodiment.

[0472] The disclosure of embodiments of this application also relates to means for performing operations in text. This means may be specifically constructed for the claimed purpose or may include a general-purpose computer selectively activated or reconfigured by a computer program stored in a computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic or optical cards, application-specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, and each may be coupled to a computer system bus. Furthermore, the computer mentioned in the specification may include a single processor or may be an architecture employing multiple processors for increased computing power.

[0473] Furthermore, the language used in this specification has been primarily chosen for readability and instructional purposes and may not have been chosen to depict or limit the disclosed subject matter. Therefore, the embodiments disclosed herein are intended to illustrate, and not limit, the scope of the concepts discussed herein.

Claims

1. A vehicle payment method, characterized in that, Applied to a vehicle, the vehicle including an in-vehicle screen, the method includes: Before the vehicle leaves the parking lot, the payment information of the vehicle is obtained from the first cloud server. The payment information includes the vehicle's paid information or the vehicle's first pending payment order. A first prompt message is displayed on the vehicle screen, the first prompt message being used to indicate the payment information; The payment information includes the first pending payment order, and the parking fee in the first pending payment order is paid.

2. The method according to claim 1, characterized in that, The step of obtaining the vehicle's payment information from the first cloud server includes: After the vehicle enters the parking lot, if a user is detected inside the vehicle within the first time, a second message is sent to the first cloud server. The second message is used to obtain the vehicle's payment information. The payment information of the vehicle is obtained from the first cloud server, wherein the payment information is the first toll information of the vehicle, and the first toll information includes the first order to be paid.

3. The method according to claim 1, characterized in that, The step of obtaining the vehicle's payment information from the first cloud server includes: After the vehicle enters the parking lot, the system detects that the user has exited the vehicle and controls the vehicle to cut off its power. After the vehicle has been in the parking lot for a second time, the system detects that a user has boarded the vehicle, controls the vehicle to power on, and sends a first message to the first cloud server. The first message is used to obtain the vehicle's payment information. The first cloud server receives the payment information, wherein the first message is used to instruct the first cloud server to send the payment information to the vehicle.

4. The method according to claim 3, characterized in that, The timing of a user getting on and off the vehicle is determined based on changes in the vehicle's status information, which includes at least one of the following: the vehicle's location, the vehicle's operating status, the vehicle's door opening / closing status, and the vehicle's seat occupancy status.

5. The method according to claim 3 or 4, characterized in that, The method further includes: When the vehicle enters the parking lot, the vehicle's entry information is obtained from the second cloud server, and a second prompt message is displayed on the vehicle screen. The second prompt message is used to indicate the entry information, which includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules. Based on the entry information, it is determined that the vehicle has entered the parking lot.

6. The method according to claim 5, characterized in that, The basic information of the vehicle and the entry time of the vehicle in the entry information are obtained by the interaction between the second cloud server and the parking lot server, and the parking lot server is associated with the parking lot; Wherein, the first cloud server is the same as the second cloud server, or the first cloud server includes the second cloud server and the parking lot server.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Once the vehicle's location is detected to have entered a set geographical area of ​​the parking lot, the vehicle's distribution service is activated, and a second message is sent to the first cloud server. The second message is used to notify the first cloud server that the vehicle's distribution service has been activated. The process of obtaining the vehicle's payment information from the first cloud server includes: The payment information for the vehicle is obtained from the first cloud server based on the distribution service.

8. The method according to any one of claims 1 to 6, characterized in that, The vehicle is equipped with an in-vehicle payment application. The payment of the parking fee in the first pending payment order includes: The parking fee in the first pending payment order is paid using the in-vehicle payment application.

9. The method according to claim 8, characterized in that, The in-vehicle payment application uses a target authentication method to pay the parking fee in the first pending payment order, wherein the target authentication method includes at least one of the following: digital password authentication, image password authentication, and facial image authentication.

10. The method according to claim 9, characterized in that, A vehicle-mounted camera is installed on the inside of the A-pillar of the vehicle. The vehicle-mounted camera is used to capture the user's facial image, and the facial image authentication is used to authenticate the facial image captured by the vehicle-mounted camera.

11. The method according to claim 8, characterized in that, The payment of the first order to be paid based on the in-vehicle payment application includes: Receive a first operation from the user on the first prompt information displayed on the vehicle screen; In response to the first operation, information about the first payment order is displayed on the vehicle screen; In response to the user's second operation on the first order to be paid, the in-vehicle payment application sends a first payment request message to the payment server. The first payment request message is used to request payment for the first order to be paid. The payment server may be the same as or different from the first cloud server. Receive a first payment response message sent by the payment server, wherein the first payment response message is used to indicate that the parking fee in the first payment order has been successfully paid; Based on the first payment response message, a third prompt message is displayed on the vehicle screen, indicating that the parking fee in the first pending payment order has been successfully paid.

12. The method according to any one of claims 1 to 7, characterized in that, The method further includes: If the payment information includes the vehicle's payment information, the user performs a fourth operation on the first prompt information displayed on the vehicle screen. In response to the fourth operation, the paid information is displayed on the vehicle screen, including the vehicle's departure time and the amount of the parking fee, wherein the parking fee was paid by a mobile terminal associated with the vehicle.

13. The method according to claim 1, characterized in that, The display of the first prompt information on the vehicle screen includes: Using the vehicle's distribution service, the first prompt information is displayed on the in-vehicle screen via a live window.

14. The method according to claim 5, characterized in that, The display of the second prompt message on the vehicle screen includes: Using the vehicle's distribution service, the second prompt information is displayed on the in-vehicle screen via a live window.

15. The method according to claim 11, characterized in that, The display of a third prompt message on the vehicle screen includes: Using the vehicle's distribution service, the third prompt information is displayed on the in-vehicle screen via a live window.

16. The method according to any one of claims 13 to 15, characterized in that, The method further includes: Upon detecting that the vehicle has left the parking lot, the system uses the vehicle's distribution service to cancel the live feed window on the in-vehicle screen and close the vehicle's distribution service.

17. The method according to claim 16, characterized in that, The detection of the vehicle leaving the parking lot includes: When the vehicle leaves the parking lot, if departure information is received from the second cloud server, or if the vehicle's location is detected to have left the designated geographical area of ​​the parking lot, then it is determined that the vehicle has left the parking lot. The departure information includes the vehicle's basic information, the vehicle's departure time, and the vehicle's parking fee.

18. The method according to claim 17, characterized in that, The departure information is obtained through interaction between the second cloud server and the parking lot server, and the parking lot server is associated with the parking lot. Wherein, the first cloud server is the same as the second cloud server, or the first cloud server includes the second cloud server and the parking lot server.

19. A vehicle payment method, characterized in that, Applied to a mobile terminal, the mobile terminal including a terminal screen, the method includes: Before a vehicle associated with a mobile terminal leaves the parking lot, if the distance between the mobile terminal and the vehicle is less than or equal to a set distance, the mobile terminal obtains the target toll information of the vehicle parking in the parking lot from the first cloud server. The terminal screen displays a first target prompt message, wherein the first target prompt message is used to indicate the target toll information.

20. The method according to claim 19, characterized in that, The method further includes: When a vehicle enters a parking lot, the mobile terminal is connected to the vehicle; When the user gets off the vehicle, the system detects that the mobile terminal has disconnected from the vehicle, activates the mobile terminal's distribution service, and sends a first target message to the first cloud server. The first target message is used to notify the first cloud server that the mobile terminal's distribution service has been activated. The mobile terminal obtains the parking fee information of the vehicle in the parking lot from the first cloud server, including: The mobile terminal obtains the target toll information of the vehicle parking in the parking lot from the first cloud server through the distribution service.

21. The method according to claim 19 or 20, characterized in that, The toll information includes the vehicle's target pending payment order, the mobile terminal has a target payment application installed, and the method further includes: The mobile terminal receives a first target operation from the user in response to the first target prompt information; In response to the first target operation, the mobile terminal displays information about the target payment order on the terminal screen; The mobile terminal receives a second target operation from the user on the target payment order; In response to the second target operation, the mobile terminal uses the target payment application to pay the parking fee in the target pending payment order.

22. The method according to claim 21, characterized in that, The mobile terminal uses the target payment application to pay for the first target order pending payment, including: The mobile terminal uses the target payment application to send a target payment request message to the payment server. The target payment request message is used to request payment for the target order to be paid. The mobile terminal receives a target payment response message sent by the payment server, the target payment response message being used to indicate that the parking fee in the target pending payment order has been successfully paid; Based on the target payment response message, the mobile terminal displays a second target prompt message on the terminal screen, which indicates that the parking fee in the target pending payment order has been successfully paid.

23. The method according to claim 19, characterized in that, The step of displaying the first target prompt information on the terminal screen includes: Using the distribution service of the mobile terminal, a first target prompt message is displayed on the terminal screen via a live window.

24. The method according to claim 22, characterized in that, The step of displaying the second target prompt information on the terminal screen includes: Using the distribution service of the mobile terminal, a second target prompt message is displayed on the terminal screen via a live window.

25. The method according to claim 20, 23 or 24, characterized in that, The method further includes: If the distance between the mobile terminal and the vehicle is greater than the set distance, the distribution service of the mobile terminal is turned off.

26. A vehicle payment method, characterized in that, Applied to a cloud server, the method includes: Before the vehicle leaves the parking lot, the vehicle's payment information is obtained. The payment information includes the vehicle's paid information or the vehicle's first pending payment order. The parking fee of the vehicle is paid by the mobile terminal associated with the vehicle or by the vehicle itself. Send the payment information to the vehicle.

27. The method according to claim 26, characterized in that, The process of obtaining the vehicle's payment information includes: If the parking fee for the vehicle is not paid, the system retrieves the first pending payment order for the vehicle from the parking lot server and generates the payment information based on the first pending payment order. or, If the parking fee for the vehicle has been paid, obtain the payment information and generate the payment information based on the payment information.

28. The method according to claim 27, characterized in that, The process of obtaining the paid information includes: Based on the target pending payment order for the vehicle, the paid information is generated, wherein the parking fee in the target pending payment order has been paid by the mobile terminal.

29. The method according to any one of claims 26 to 28, characterized in that, The method further includes: The system receives a first message sent by the vehicle, wherein the first message instructs the cloud server to send the payment information to the vehicle.

30. The method according to claim 29, characterized in that, The first message is sent when the vehicle detects a user getting into the vehicle and controls the vehicle to power on immediately after it has been in the parking lot for a period of time.

31. The method according to claim 26, characterized in that, The method further includes: Send the vehicle's entry information to the vehicle, wherein the entry information includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules.

32. The method according to claim 31, characterized in that, Sending the vehicle's arrival information to the vehicle includes: The vehicle's entry notification message is obtained from the parking lot server. The entry notification message includes at least: the vehicle's basic information and the vehicle's entry time. The entry information is sent to the vehicle according to the entry notification message.

33. The method according to any one of claims 26 to 28, characterized in that, The payment information includes pending payment orders for the vehicle, the vehicle is equipped with an in-vehicle payment application, the parking fee is paid by the vehicle, and the method further includes: Receive a first payment request message sent by the vehicle using the in-vehicle payment application, the first payment request message being used to request payment for parking fees in the vehicle's first pending payment order; The parking fee in the first pending payment order is paid, a first payment response message is generated, and the first payment response message is sent to the vehicle. The first payment response message is used to indicate that the parking fee in the first pending payment order has been successfully paid.

34. The method according to any one of claims 26 to 28, characterized in that, The method further includes: Receive a second message sent by the vehicle, the second message being used to indicate that the distribution service on the vehicle side has been started, the second message being sent when the vehicle's location enters a set geographical range of the parking lot; Sending the payment information to the vehicle includes: The payment information is sent to the vehicle via the vehicle-side distribution service.

35. The method according to any one of claims 26 to 34, characterized in that, The method further includes: If the parking duration of the vehicle meets the jump condition, the target jump fee information of the vehicle is generated and sent to the mobile terminal.

36. The method according to claim 35, characterized in that, The method further includes: Receive a first target message sent by the mobile terminal, wherein the first target message is used to indicate that the distribution service on the mobile terminal side has been enabled, and the first target message is sent when the distance between the mobile terminal and the vehicle is less than or equal to a set distance; Sending the target fare hopping information to the mobile terminal includes: The target toll hopping information is sent to the mobile terminal through the distribution service on the mobile terminal side.

37. The method according to claim 28, characterized in that, The payment information is generated and sent by the cloud server when the parking duration of the vehicle meets the jump condition. The payment information is the first jump fee information of the vehicle, which includes the first payment order.

38. The method according to claim 36, characterized in that, The payment information includes the paid information, the parking fee for the vehicle is paid by the mobile terminal, the vehicle is equipped with a target payment application, and the method further includes: The system receives a target payment request message sent by the mobile terminal, the target payment request message being used to request payment for the parking fee in the target pending payment order of the target toll information; The parking fee in the target pending payment order is paid, a target payment response message is generated, and the target payment response message is sent to the mobile terminal. The target payment response message is used to indicate that the parking fee in the target pending payment order has been successfully paid.

39. The method according to claim 38, characterized in that, The method further includes: Based on the target payment response message, it is determined that the parking fee in the target pending payment order has been paid.

40. A vehicle payment system, characterized in that, The system includes a cloud server and a parking lot server, and, The parking lot server is used to send the vehicle's first pending payment order or the vehicle's paid information to the cloud server before the vehicle leaves the parking lot. The cloud server is used to send the vehicle's payment information to the vehicle before the vehicle leaves the parking lot. The payment information includes the paid information or the first pending payment order. The parking fee for the vehicle in the parking lot is paid by the mobile terminal associated with the vehicle or by the vehicle itself.

41. The system according to claim 40, characterized in that, The parking lot server is also configured to obtain a payment notification message for the vehicle before the vehicle leaves the parking lot, and determine that the parking fee for the vehicle has been paid based on the payment notification message. The payment notification message is obtained from the payment server or the cloud server, and the payment notification message is used to indicate that the parking fee for the vehicle has been paid. The parking lot server is further configured to obtain a vehicle departure request message when the vehicle arrives at the exit of the parking lot, and generate a departure instruction message if the parking fee of the vehicle has been paid, wherein the departure instruction message is used to instruct the vehicle to leave.

42. The system according to claim 41, characterized in that, The parking lot server is further configured to, when the vehicle arrives at the entrance of the parking lot, obtain the vehicle's entry request message, generate an entry instruction message, and send the vehicle's entry notification message to the cloud server, wherein the entry instruction message is used to instruct the vehicle to be allowed to pass. The cloud server is further configured to generate the vehicle's entry information based on the entry notification message, and send the entry information to the vehicle. The entry information includes the vehicle's basic information, the vehicle's entry time, and the parking lot's billing rules. The entry notification message includes at least the vehicle's basic information and the vehicle's entry time.

43. The system according to claim 41, characterized in that, The parking lot server is also configured to generate a departure notification message for the vehicle based on the departure request message, and send the departure notification message to the cloud server. The cloud server is also configured to generate the vehicle's departure information based on the departure notification message, and send the departure information to the vehicle. The departure information includes the vehicle's basic information, the vehicle's departure time, and the vehicle's parking fee amount.

44. The system according to claim 40, characterized in that, The cloud server is also used to send an order query message to the parking lot server, the order query message being used to query the vehicle's pending payment orders; The parking lot server is also used to send an order response message to the cloud server based on the order query message, the order response message including the vehicle's pending payment order.

45. The system according to claim 44, characterized in that, The cloud server is also used to receive a first message sent by the vehicle, wherein the first message is used to instruct the cloud server to send the payment information to the vehicle, and the first message is sent by the vehicle after the user gets in and the vehicle is powered on; The order query message is sent by the cloud server based on the first message and / or when the parking duration of the vehicle meets the jump condition.

46. ​​The system according to claim 44, characterized in that, The cloud server is also used to send the vehicle's target toll information to the mobile terminal when the vehicle's parking duration meets the toll jump condition.

47. The system according to claim 46, characterized in that, The cloud server is also configured to receive a first target message sent by a mobile terminal associated with the vehicle, wherein the first target message is configured to instruct the cloud server to send the vehicle's target fare information to the mobile terminal, and the first target message is sent after the user gets off the vehicle in the parking lot and the mobile terminal disconnects from the vehicle.

48. A vehicle payment system, characterized in that, The system includes a cloud server, a parking server, and vehicles, and, The parking lot server is used to send the vehicle's first pending payment order or the vehicle's paid information to the cloud server before the vehicle leaves the parking lot. The cloud server is used to send the vehicle's payment information to the vehicle before the vehicle leaves the parking lot, wherein the payment information includes the vehicle's paid information or the vehicle's first pending payment order. The vehicle is used to pay the parking fee in the first payment order, which corresponds to the payment information. The payment information includes the paid information, and the parking fee for the vehicle is paid by the mobile terminal associated with the vehicle.

49. A vehicle payment system, characterized in that, The system includes a cloud server, vehicles, and mobile terminals, and, The cloud server is used to send target fee skipping information of the vehicle parking in the parking lot to the mobile terminal before the vehicle associated with the mobile terminal leaves the parking lot, provided that the distance between the mobile terminal and the vehicle is less than or equal to a set distance. The mobile terminal is configured to display a first target prompt information on the terminal screen of the mobile terminal, wherein the first target prompt information is used to indicate the target toll information; The cloud server is also used to send the vehicle's payment information to the vehicle before the vehicle leaves the parking lot, wherein the payment information includes the vehicle's paid information or the vehicle's first pending payment order. The vehicle is configured to display a first prompt message on its in-vehicle screen, and, corresponding to the payment information including the first pending payment order, to pay the parking fee in the first pending payment order, wherein the first prompt message is used to indicate the payment information, corresponding to the payment information including the paid information, and the parking fee of the vehicle is paid by the mobile terminal.

50. A computer-readable storage medium, characterized in that, The readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the vehicle payment method according to any one of claims 1 to 39.

51. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the vehicle payment method according to any one of claims 1 to 39.