Parking fee payment method and apparatus, and vehicle

Abstract

The present application provides a parking fee payment method and apparatus, and a vehicle. The method may be applied to the field of intelligent vehicles. The method comprises: receiving identification information and an image of one or more parking lots, sent by one or more mobile terminals; on the basis of the identification information and the image of the one or more parking lots, establishing a mapping relationship, the mapping relationship comprising a correspondence relationship between the identification information of each parking lot of the one or more parking lots and a payment link resource for each parking lot; receiving a first request message sent by a vehicle, the first request message being used for requesting a payment link resource of a first parking lot; and, on the basis of the first request message and the mapping relationship, sending a first response message to the vehicle. The present application can be applied to an intelligent vehicle or an electric vehicle, helping the vehicle to conveniently pay a parking fee, and thus helping improve the driving experience of a user.

Description

Parking fee payment methods, devices and vehicles Technical Field

[0001] This application relates to the field of intelligent vehicles, and more specifically, to a parking fee payment method, device, and vehicle. Background Technology

[0002] In the process of users driving their vehicles into and out of parking lots, they usually need to perform cumbersome operations such as scanning QR codes on walls, pillars or gates with their mobile phones and making payments, resulting in a poor driving experience for users.

[0003] Summary of the Invention

[0004] This application provides a parking fee payment method, device, and vehicle. A cloud server can store a payment link resource library for parking lots, and vehicles can request payment link resources for their parking lots from the cloud server, enabling vehicles to conveniently pay parking fees and helping to improve the user's driving experience.

[0005] In a first aspect, this application provides a method for paying parking fees, the method comprising: receiving identification information and images of one or more parking lots sent by one or more mobile terminals, the images including payment link resources of one or more parking lots; establishing a mapping relationship based on the identification information and images of the one or more parking lots, the mapping relationship including the correspondence between the identification information of each parking lot in the one or more parking lots and the payment link resource of each parking lot; receiving a first request message sent by a vehicle, the first request message being used to request payment link resources of a first parking lot; and sending a first response message to the vehicle based on the first request message and the mapping relationship.

[0006] Based on the above technical solution, the cloud server can establish a mapping relationship (or payment link resource library) based on parking lot signage information and images sent by one or more mobile terminals. Upon receiving a request message from a vehicle, it can send a response message to the vehicle based on this mapping relationship. This avoids the cumbersome process of users manually scanning QR codes on walls, pillars, or gates with their mobile phones to pay when leaving the parking lot, facilitating convenient parking fee payment and improving the user's driving experience.

[0007] In conjunction with the first aspect, in certain implementations of the first aspect, sending a first response message to the vehicle based on the first request message and the mapping relationship includes: when the mapping relationship includes a correspondence between the first parking lot and the first payment link resource, sending the first payment link resource to the vehicle based on the first request message; wherein the method further includes: receiving first instruction information sent by the vehicle, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource; and in response to receiving the first instruction information, maintaining the correspondence between the first parking lot and the first payment link resource in the mapping relationship.

[0008] Based on the above technical solution, after a vehicle successfully pays the parking fee using the first payment link resource, it can send a first instruction message to the cloud server. This allows the cloud server to accurately determine the correspondence between the first parking lot and the first payment link resource based on the instruction message sent by the vehicle.

[0009] In some possible implementations, the method further includes: in response to receiving the first instruction information, the cloud server updates the number of successful parking fee payments corresponding to the first payment link resource in the mapping relationship, and / or, the cloud server updates the confidence level of the first payment link resource.

[0010] In conjunction with the first aspect, in certain implementations of the first aspect, sending a first response message to the vehicle based on the first request message and the mapping relationship includes: when the mapping relationship includes a correspondence between the first parking lot and the first payment link resource, sending the first payment link resource to the vehicle based on the first request message; wherein the method further includes: receiving a second request message sent by the vehicle, the second request message being used to request updating the payment link resource corresponding to the first parking lot in the mapping relationship from the first payment link resource to the second payment link resource, the second request message including the second payment link resource; and in response to receiving the second request message, updating the correspondence between the first parking lot and the first payment link resource in the mapping relationship to the correspondence between the first parking lot and the second payment link resource.

[0011] Based on the above technical solution, after the cloud server receives a request from a vehicle to update the payment link resource, it can update the mapping relationship based on the payment link resource sent by the vehicle. This helps improve the accuracy of the correspondence between parking lots and payment link resources, making it easier for other vehicles to obtain accurate payment link resources when they request payment link resources from the same parking lot again.

[0012] In some possible implementations, before updating the mapping relationship between the first parking lot and the first payment link resource to the mapping relationship between the first parking lot and the second payment link resource in response to receiving the second request message, the method further includes: determining that the second payment link resource has passed anti-counterfeiting authentication.

[0013] In conjunction with the first aspect, in certain implementations of the first aspect, sending a first response message to the vehicle based on the first request message and the mapping relationship includes: when the mapping relationship does not include the correspondence between the first parking lot and the first payment link resource, sending the first response message to the vehicle based on the first request message, the first response message being used to indicate that the payment link resource for the first parking lot is not stored in the cloud server; wherein, the method further includes: receiving a third request message sent by the vehicle, the third request message being used to request the addition of the correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource; and in response to receiving the third request message, adding the correspondence between the first parking lot and the third payment link resource in the mapping relationship.

[0014] Based on the above technical solution, after the cloud server receives a request to add a mapping between parking lots and payment link resources, it can add a mapping between the first parking lot and the third payment link resource to the mapping relationship. This allows other vehicles to easily obtain the third payment link resource when requesting payment link resources for the first parking lot, thus improving the convenience for other vehicles paying parking fees at the first parking lot.

[0015] In some possible implementations, in response to receiving the third request message, before adding the correspondence between the first parking lot and the third payment link resource in the mapping relationship, the method further includes: determining that the third payment link resource has passed anti-counterfeiting authentication.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, receiving identification information and images of one or more parking lots sent by one or more mobile terminals includes: receiving identification information of a second parking lot and an image including a fourth payment link resource of the second parking lot sent by a first mobile terminal; obtaining the first account name, first account type, and transaction amount of the first mobile terminal corresponding to the fourth payment link resource; wherein establishing a mapping relationship includes: establishing a correspondence between the second parking lot and the fourth payment link resource when one or more of the following conditions are met: the first account name is associated with the name of the second parking lot; the first account type is a corporate account; or, the transaction amount matches the parking duration of the first vehicle in the second parking lot, and the first mobile terminal is associated with the first vehicle.

[0017] Based on the above technical solution, the authenticity of a payment link resource can be determined by the account name, account type, and transaction amount on the mobile terminal. After successful authentication, a mapping relationship can be established between the parking lot and the payment link resource. This improves the accuracy of the mapping relationship and prevents financial losses to users caused by illegitimate payment link resources.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, receiving identification information and images of one or more parking lots sent by one or more mobile terminals includes: receiving identification information of a third parking lot and an image including a fifth payment link resource of the third parking lot sent by a second mobile terminal; obtaining a second account type corresponding to the fifth payment link resource; wherein establishing a mapping relationship includes: when the second account type is a private account, establishing a correspondence between the third parking lot and the fifth payment link resource and marking the fifth payment link resource as a risky payment link resource.

[0019] Based on the above technical solution, when the account type corresponding to the fifth payment link resource is a private account, the cloud server can mark the fifth payment link resource as a risky payment link resource.

[0020] In some possible implementations, receiving identification information and images of one or more parking lots sent by one or more mobile terminals includes: receiving identification information of a third parking lot and an image including a fifth payment link resource of the third parking lot sent by a second mobile terminal; obtaining a second account type corresponding to the fifth payment link resource; wherein establishing a mapping relationship includes: when the second account type is a private account, not establishing a mapping relationship between the third parking lot and the fifth payment link resource.

[0021] Based on the above technical solution, when the account type corresponding to the fifth payment link resource is a private account, the cloud server does not need to establish a correspondence between the third parking lot and the fifth payment link resource. This avoids financial losses to users caused by high-risk payment link resources.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving a fourth request message sent by a vehicle, the fourth request message being used to request a payment link resource of the third parking lot; sending a second response message to the vehicle, the second response message including the fifth payment link resource and second indication information, the second indication information being used to indicate that the fifth payment link resource is risky.

[0023] Based on the above technical solution, when a vehicle requests a payment link resource from a third parking lot, the cloud server can also indicate that the fifth payment link resource is risky, so that the vehicle can be alerted that the fifth payment link resource is risky.

[0024] Secondly, this application provides a method for paying parking fees, the method comprising: detecting a user's intention to drive a vehicle into a first parking lot; sending a first request message to a cloud server, the first request message being used to request a first payment link resource of the first parking lot, the cloud server storing a mapping relationship, the mapping relationship including a correspondence between the identification information of each parking lot in one or more parking lots and the payment link resource of each parking lot; receiving a first response message, the first response message being a response to the first request message; and, based on the first response message, performing a parking fee payment operation when the user's intention to drive the vehicle away from the first parking lot is detected.

[0025] Based on the above technical solution, upon receiving the user's intention to enter the first parking lot, a payment link resource corresponding to the first parking lot can be requested from the cloud server. This avoids the cumbersome process of manually scanning QR codes on walls, pillars, or gates with a mobile phone and making payments when the user leaves the first parking lot. Instead, it facilitates convenient payment of parking fees based on the payment link resource sent by the cloud server, thus improving the user's driving experience.

[0026] In some possible implementations, the user's intention to drive the vehicle into the first parking lot is detected, including: detecting the user's intention to manually drive the vehicle into the first parking lot; or, detecting the intention of a vehicle in autonomous driving mode to enter the first parking lot.

[0027] In some possible implementations, the intention of a user to drive the vehicle away from the first parking lot is detected, including: detecting the user's intention to manually drive the vehicle away from the first parking lot; or, detecting the intention of a vehicle in autonomous driving mode to leave the first parking lot.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, the one or more parking lots include the first parking lot, and the first response message includes the first payment link resource. The operation of paying parking fees upon detecting an intention to leave the first parking lot, based on the first response message, includes: upon detecting that the first payment link resource is valid and detecting the intention of the vehicle to leave the first parking lot, performing the operation of paying parking fees based on the first payment link resource; and sending first instruction information to a cloud server, the first instruction information being used to instruct the vehicle to successfully pay parking fees within the first parking lot based on the first payment link resource.

[0029] In some possible implementations, detecting the validity of the first payment link resource includes determining that the first payment link resource is valid when one or more of the following conditions are met: the account name corresponding to the first payment link resource is associated with the name of the first parking lot; the account type corresponding to the first payment link resource is a corporate account; or, the transaction amount corresponding to the first payment link resource matches the duration of the vehicle's parking in the first parking lot.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the one or more parking lots include the first parking lot, the first response message includes the first payment link resource, and according to the first response message, when an intention to leave the first parking lot is detected, an operation to pay parking fees is performed, including: when the first payment link resource is detected to be invalid and the vehicle is in the first parking lot, obtaining the second payment link resource of the first parking lot based on images captured by a dashcam and / or an external camera device; when an intention to leave the first parking lot is detected, performing an operation to pay parking fees based on the second payment link resource; wherein, the method further includes: when the operation to pay parking fees is successfully performed, sending a second request message to the cloud server, the second request message being used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, the second request message including the second payment link resource.

[0031] In some possible implementations, detecting the invalidity of the first payment link resource includes determining that the first payment link resource is invalid when one or more of the following conditions are met: the account name corresponding to the first payment link resource is not associated with the name of the first parking lot; the account type corresponding to the first payment link resource is a private account; or, the transaction amount corresponding to the first payment link resource does not match the duration of the vehicle's parking in the first parking lot.

[0032] In conjunction with the second aspect, in certain implementations of the second aspect, according to the first response message, the operation of paying parking fees upon detecting a user's intention to drive a vehicle away from the first parking lot includes: when the first response message indicates that the cloud server does not store payment link resources for the first parking lot and the vehicle is detected to be in the first parking lot, obtaining a third payment link resource for the first parking lot based on images captured by a dashcam and / or an external camera; and when the user's intention to drive the vehicle away from the first parking lot is detected, performing the operation of paying parking fees based on the third payment link resource; wherein the method further includes: upon successfully performing the operation of paying parking fees, sending a third request message to the cloud server, the third request message being used to request the addition of a correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource.

[0033] Thirdly, this application provides an apparatus for paying parking fees, comprising: a receiving unit for receiving identification information and images of one or more parking lots sent by one or more mobile terminals, the images including payment link resources of one or more parking lots; a mapping relationship establishment unit for establishing a mapping relationship based on the identification information and images of the one or more parking lots, the mapping relationship including the correspondence between the identification information of each parking lot and the payment link resource of each parking lot; the receiving unit is further configured to receive a first request message sent by a vehicle, the first request message requesting payment link resources of a first parking lot; and a sending unit for sending a first response message to the vehicle based on the first request message and the mapping relationship.

[0034] In conjunction with the third aspect, in some implementations of the third aspect, the sending unit is specifically configured to: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, send the first payment link resource to the vehicle according to the first request message; the receiving unit is further configured to receive first instruction information sent by the vehicle, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource; the mapping relationship establishment unit is further configured to maintain the correspondence between the first parking lot and the first payment link resource in the mapping relationship in response to the receiving unit receiving the first instruction information.

[0035] In conjunction with the third aspect, in some implementations of the third aspect, the sending unit is specifically configured to: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, send the first payment link resource to the vehicle according to the first request message; the receiving unit is further configured to receive a second request message sent by the vehicle, the second request message being used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, the second request message including the second payment link resource; the mapping relationship establishment unit is further configured to, in response to the receiving unit receiving the second request message, update the correspondence between the first parking lot and the first payment link resource in the mapping relationship to the correspondence between the first parking lot and the second payment link resource.

[0036] In conjunction with the third aspect, in some implementations of the third aspect, the sending unit is specifically configured to: when the mapping relationship does not include the correspondence between the first parking lot and the first payment link resource, send the first response message to the vehicle according to the first request message, the first response message being used to indicate that the payment link resource of the first parking lot is not stored in the cloud server; the receiving unit is further configured to receive a third request message sent by the vehicle, the third request message being used to request the addition of the correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource; the mapping relationship establishment unit is further configured to, in response to the receiving unit receiving the third request message, add the correspondence between the first parking lot and the third payment link resource in the mapping relationship.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the device further includes an acquisition unit. The receiving unit is configured to receive identification information of the second parking lot and an image including a fourth payment link resource of the second parking lot sent by the first mobile terminal. The acquisition unit is configured to acquire the first account name, the first account type, and the transaction amount of the first mobile terminal corresponding to the fourth payment link resource. Specifically, the mapping relationship establishment unit is configured to establish a correspondence between the second parking lot and the fourth payment link resource when one or more of the following conditions are met: the first account name is associated with the name of the second parking lot; the first account type is a corporate account; or, the transaction amount matches the parking duration of the first vehicle in the second parking lot, and the first mobile terminal is associated with the first vehicle.

[0038] In conjunction with the third aspect, in some implementations of the third aspect, the device further includes an acquisition unit; the receiving unit is configured to receive the identification information of the third parking lot and an image including the fifth payment link resource of the third parking lot sent by the second mobile terminal; the acquisition unit is configured to acquire the second account type corresponding to the fifth payment link resource; wherein, the mapping relationship establishment unit is specifically configured to: when the second account type is a private account, establish a correspondence between the third parking lot and the fifth payment link resource and mark the fifth payment link resource as a risky payment link resource.

[0039] In conjunction with the third aspect, in some implementations of the third aspect, the receiving unit is further configured to receive a fourth request message sent by the vehicle, the fourth request message being used to request the payment link resource of the third parking lot; the sending unit is further configured to send a second response message to the vehicle, the second response message including the fifth payment link resource and second indication information, the second indication information being used to indicate that the fifth payment link resource is risky.

[0040] Fourthly, this application provides a device for paying parking fees, comprising: a detection unit for detecting a user's intention to drive a vehicle into a first parking lot; a sending unit for sending a first request message to a cloud server, the first request message requesting a first payment link resource of the first parking lot, the cloud server storing a mapping relationship including a correspondence between the identification information of each parking lot in one or more parking lots and the payment link resource of each parking lot; a receiving unit for receiving a first response message, the first response message being a response to the first request message; and a parking fee payment unit for performing a parking fee payment operation based on the first response message, after the detection unit detects the user's intention to drive away from the first parking lot.

[0041] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the one or more parking lots include the first parking lot, the first response message includes the first payment link resource, and the parking fee payment unit is specifically used to: when the detection unit detects that the first payment link resource is valid and detects the user's intention to drive the vehicle away from the first parking lot, perform the operation of paying the parking fee according to the first payment link resource; the sending unit is also used to send a first instruction information to the cloud server, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource.

[0042] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the one or more parking lots include the first parking lot, the first response message includes the first payment link resource, the acquisition unit is used to acquire the second payment link resource of the first parking lot based on images collected by a dashcam and / or an external camera when the detection unit detects that the first payment link resource is invalid and the vehicle is in the first parking lot; the parking fee payment unit is used to perform a parking fee payment operation based on the second payment link resource when the user's intention to drive the vehicle away from the first parking lot is detected; the sending unit is further used to send a second request message to the cloud server when the parking fee payment unit successfully performs the parking fee payment operation, the second request message is used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, and the second request message includes the second payment link resource.

[0043] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the acquisition unit is configured to acquire the third payment link resource of the first parking lot based on images captured by a dashcam and / or an external camera when the first response message indicates that the cloud server does not store the payment link resource of the first parking lot and the detection unit detects that the vehicle is in the first parking lot; the parking fee payment unit is configured to perform a parking fee payment operation based on the third payment link resource when the detection unit detects the user's intention to drive the vehicle away from the first parking lot; the sending unit is further configured to send a third request message to the cloud server when the parking fee payment unit successfully performs the parking fee payment operation, the third request message being used to request the addition of a correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource.

[0044] Fifthly, this application provides an apparatus for paying parking fees, the apparatus including a processor and a memory, wherein the memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the apparatus to perform any of the possible methods in the first aspect.

[0045] In a sixth aspect, this application provides an apparatus for paying parking fees, the apparatus including a processor and a memory, wherein the memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the apparatus to perform any of the possible methods in the second aspect.

[0046] In a seventh aspect, this application provides a server that includes any of the possible devices described in the third or fifth aspect above.

[0047] Eighthly, this application provides a vehicle that includes any of the possible devices in the fourth or sixth aspects described above.

[0048] Ninthly, this application provides a computer program product comprising: computer program code, which, when executed on a computer, causes the computer to perform any one of the possible methods described in the first or second aspect above.

[0049] It should be noted that the above-mentioned computer program code can be stored in whole or in part on the first storage medium, wherein the first storage medium can be packaged together with the processor or packaged separately from the processor. This application embodiment does not specifically limit this.

[0050] In a tenth aspect, this application provides a computer-readable storage medium storing program code that, when executed on a computer, causes the computer to perform any of the possible methods described in the first or second aspect above.

[0051] In one aspect, this application provides a chip system including circuitry for performing any of the possible methods described in the first or second aspect above. Attached Figure Description

[0052] Figure 1 is a functional block diagram of the vehicle provided in an embodiment of this application.

[0053] Figure 2 is a schematic flowchart of the method for paying parking fees provided in an embodiment of this application.

[0054] Figure 3 is another schematic flowchart of the method for paying parking fees provided in the embodiments of this application.

[0055] Figure 4 is a GUI provided in an embodiment of this application.

[0056] Figure 5 is another GUI provided in an embodiment of this application.

[0057] Figure 6 is a schematic block diagram of a device for paying parking fees provided in an embodiment of this application.

[0058] Figure 7 is another schematic block diagram of the device for paying parking fees provided in an embodiment of this application. Detailed Implementation

[0059] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this document is merely a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. "At least one" refers to one or more. For example, "at least one of A and B," similar to "A and / or B," describes the association relationship between related objects, indicating that three relationships can exist. For example, at least one of A and B can represent: A existing alone, A and B existing simultaneously, and B existing alone.

[0060] The prefixes such as "first" and "second" used in this application embodiment are merely for distinguishing different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes used to distinguish descriptive objects in this application embodiment does not constitute a limitation on the described objects. The description of the described objects is given in the claims or the context of the embodiments, and should not constitute unnecessary restrictions due to the use of such prefixes. Furthermore, in the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0061] Figure 1 is a functional block diagram of a vehicle 100 provided in an embodiment of this application.

[0062] As shown in Figure 1, vehicle 100 may include a perception system 110, a computing platform 120, and a communication system 130. The perception system 110 may include one or more sensors for sensing information about the environment surrounding vehicle 100. For example, the perception system 110 may include a positioning system, which may be a Global Positioning System (GPS), a BeiDou Navigation Satellite System, or another positioning system. Alternatively, the perception system 110 may include one or more of the following: an inertial measurement unit (IMU), an accelerometer, a lidar, millimeter-wave radar, ultrasonic radar, and a camera device. Furthermore, the perception system 110 may include one or more collision sensors.

[0063] Some or all of the functions of vehicle 100 can be controlled by computing platform 120. Computing platform 120 may include one or more processors, such as processors 121 to 12n (n being a positive integer). A processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field-programmable gate array (FPGA). In reconfigurable hardware circuits, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement some or all of the functions of the aforementioned units. Furthermore, the processor can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc. In addition, the computing platform 120 may also include a memory for storing instructions. Some or all of the processors 121 to 12n can call the instructions in the memory to implement the corresponding functions.

[0064] The communication system 130 may integrate one or more devices, including at least one communication module. The communication system 130 can transmit and receive electromagnetic waves via an antenna, enabling the vehicle 100 to communicate with servers, other vehicles, roadside equipment, etc., based on a vehicle-to-everything (V2X) network, such as vehicle-to-vehicle (V2V) communication networks, vehicle-to-infrastructure (V2I) communication networks, and vehicle-to-network (V2N) communication networks. Wireless communication technologies may also include short-range wireless communication technologies, such as Bluetooth (BT), radio frequency identification (RFID), and NearLink. For example, the communication system 130 may include an onboard telematics box (T-box), or it may include other communication modules. In practice, vehicle 100 communicates with cloud servers, roadside equipment, etc. via T-box. Vehicle 100 can also communicate with other devices that have the same wireless short-range communication module via other wireless short-range communication modules.

[0065] Optionally, the structure of the vehicle 100 described above is merely illustrative. In actual applications, various components of the vehicle 100 may be added or removed as needed.

[0066] The vehicle 100 in this application may include: road vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc. For example, vehicle 100 may be a means of transportation (such as commercial vehicles, passenger cars, motorcycles, flying cars, trains, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as lawnmowers, harvesters, etc.), amusement equipment, toy vehicles, etc. The embodiments of this application do not specifically limit the type of vehicle.

[0067] During daily driving, users still need to perform cumbersome operations such as scanning QR codes and making payments using their mobile phones when entering and exiting temporary parking lots. Scanning codes in advance or while driving may pose security risks or cause users to miss the factory's production time, resulting in various inconveniences, such as:

[0068] (1) The operation of scanning QR codes with mobile phones is complicated: users need to perform multiple steps such as scanning the code, following the official account, outputting the license plate number, and paying the fee.

[0069] (2) The exit time cannot be controlled or there are security risks in scanning the code while driving: If you pay in advance, you need to leave within 15 minutes (or 30 minutes), while scanning the code after starting the vehicle poses a security risk of using a mobile phone.

[0070] (3) The parking payment technology does not achieve end-to-end interaction: the method of using cooperative parking lots requires cooperation with parking lots for operation, and there are coverage blind spots.

[0071] This application provides a method, device, and vehicle for paying parking fees. When the intention of a user to enter a temporary parking lot is recognized, the payment link resource of the temporary parking lot can be obtained from the cloud server, which can realize the automatic completion of temporary payment before the vehicle leaves the parking lot, and achieve seamless exit in the temporary parking lot scenario.

[0072] Figure 2 shows a schematic flowchart of a parking fee payment method 200 provided in an embodiment of this application. The method 200 can be executed by the vehicle 100 and a cloud server. The method 200 includes:

[0073] S210, the cloud server receives identification information and images of one or more parking lots sent by one or more mobile terminals, the images including payment link resources for one or more parking lots.

[0074] The mobile terminals mentioned above can include portable terminal devices with cameras, such as mobile phones, tablets, smartwatches, and vehicles.

[0075] Data sent from one or more mobile terminals to a cloud server can also be called crowdsourced data.

[0076] For example, the identification information of the parking lot may include the location and name of the parking lot.

[0077] For example, when user A is in parking lot a, he can use his mobile phone camera to capture an image including the QR code a used to pay parking fees in parking lot a, and upload the location (e.g., No. xx, xx Road, Pudong District, Shanghai), name (e.g., underground parking lot a of xx shopping mall) and other information of parking lot a to the cloud server through the application.

[0078] For example, when user B is driving a vehicle in parking lot b, he can use a dashcam and / or an external camera to capture images, including a QR code b used to pay parking fees in parking lot b, and upload the location (e.g., No. xx, xx Road, Yangpu District, Shanghai), name (e.g., underground parking lot b of xx office building) of parking lot b to a cloud server via an application.

[0079] The location and name of the parking lots can be obtained from map information on the mobile terminal. For example, the mobile terminal can obtain the location information when the user scans the QR code. Based on this location information and map information, the location of the parking lot where the mobile terminal is currently located and the name of the parking lot can be obtained.

[0080] S220, the cloud server establishes a mapping relationship based on the identification information and images of one or more parking lots. This mapping relationship includes the correspondence between the identification information of each parking lot in the one or more parking lots and the payment link resources of each parking lot.

[0081] For example, after receiving information such as the location and name of parking lot a and the image, the cloud server can process the image to obtain the QR code a in the image and establish the correspondence between the location and name of parking lot a and the QR code a.

[0082] For example, after receiving information such as the location and name of parking lot b and the image, the cloud server can process the image to obtain the QR code b in the image and establish the correspondence between the location and name of parking lot b and the QR code b.

[0083] For example, the mapping relationship established by the cloud server can be shown in Table 1.

[0084] Table 1

[0085] The mapping relationships shown in Table 1 above are merely illustrative and may include more or less information. For example, the mapping relationship may only include the correspondence between parking lot locations and payment link resources.

[0086] Optionally, the cloud server receives identification information and images of one or more parking lots sent by one or more mobile terminals, including: the cloud server receiving identification information of a second parking lot and an image including a fourth payment link resource of the second parking lot sent by a first mobile terminal; the cloud server obtaining the first account name, first account type, and transaction amount of the first mobile terminal corresponding to the fourth payment link resource; wherein, the cloud server establishes a mapping relationship, including: when one or more of the following conditions are met, the cloud server establishes a correspondence between the second parking lot and the fourth payment link resource: the first account name is associated with the name of the second parking lot; the first account type is a corporate account; or, the transaction amount matches the parking duration of the first vehicle in the second parking lot, and the first mobile terminal is associated with the first vehicle.

[0087] For example, taking the second parking lot as parking lot b, the cloud server can perform anti-counterfeiting verification on QR code b after obtaining it. For example, with the authorization of user B, the vehicle can also send its license plate number information to the cloud server. Based on QR code b, the cloud server can determine the account name and account type corresponding to the payment link resource, and based on QR code b and license plate number information, determine the parking duration and parking fee transaction amount for the vehicle in parking lot b.

[0088] For example, if the account name is "xx office building underground parking lot b" ​​and the account type is a corporate account, then the cloud server can determine that the QR code b has passed the anti-counterfeiting authentication, thereby establishing the correspondence between the location and name of parking lot b and the QR code b.

[0089] For example, if the account name is "xx office building underground parking lot", the account type is a corporate account, and the vehicle's parking duration (e.g., 3 hours and 24 minutes) matches the transaction amount (e.g., 16 yuan) through the vehicle's license plate information, then the cloud server can determine that the QR code b has passed the anti-counterfeiting authentication, thereby establishing the correspondence between the location and name of parking lot b and QR code b.

[0090] For example, after 11 mobile terminals send the identification information of parking lot 'a' and the information of QR code 'a' to the cloud server, the cloud server can perform anti-counterfeiting authentication on the QR code 'a' sent by each mobile terminal. If the result of each anti-counterfeiting authentication is that the account name corresponding to QR code 'a' matches the name of parking lot 'a', the account type is a corporate account, and the transaction amount matches the parking duration of the vehicle, the cloud server can also set the confidence level of QR code 'a' to 99% in the mapping relationship and record the number of times QR code 'a' was successfully used to pay parking fees as 11 times.

[0091] For example, after a mobile terminal sends the identification information of parking lot b and QR code b to the cloud server, the cloud server can perform anti-counterfeiting authentication on the QR code b sent by the mobile terminal. If the anti-counterfeiting authentication result shows that the account name corresponding to QR code b matches the name of parking lot b, the account type is a corporate account, and the transaction amount matches the parking duration of the vehicle, the cloud server can also set the confidence level of QR code b to 60% in this mapping relationship and record the number of times parking fees are successfully paid using QR code b as 1.

[0092] For example, the mapping relationship established by the cloud server can also be shown in Table 2.

[0093] Table 2

[0094] Optionally, the cloud server receives identification information and images of one or more parking lots sent by one or more mobile terminals, including: the cloud server receiving identification information of a third parking lot and an image including a fifth payment link resource of the third parking lot sent by a second mobile terminal; the cloud server obtaining a second account type corresponding to the fifth payment link resource; wherein, the cloud server establishing a mapping relationship includes: when the second account type is a private account, the cloud server establishing a correspondence between the third parking lot and the fifth payment link resource and marking the fifth payment link resource as a risky payment link resource.

[0095] For example, taking parking lot c as an example, after obtaining QR code c, the cloud server can perform anti-counterfeiting verification on QR code c. Based on QR code c, the cloud server can determine that the account type corresponding to QR code c is a private account. At this point, the cloud server can determine that QR code c has failed the anti-counterfeiting verification. The cloud server can set the confidence level of QR code c to 10% in this mapping relationship and not record the number of successful parking fee payments corresponding to parking lot c. Simultaneously, the cloud server can also mark the risk level of the payment link resource corresponding to parking lot c as high risk.

[0096] For example, the mapping relationship established by the cloud server can also be shown in Table 3.

[0097] Table 3

[0098] The risk level in Table 3 above can be correlated with the number of times parking fees are successfully paid.

[0099] For example, for payment link resources with a corporate account type, if the number of successful parking fee payments is greater than or equal to 10, the risk level can be considered low; if the number of successful parking fee payments is greater than or equal to 1 but less than 10, the risk level can be considered medium. For payment link resources with a private account type, the risk level can be considered high.

[0100] Optionally, the method 200 further includes: the vehicle sending a fourth request message to a cloud server, the fourth request message being used to request a payment link resource of the third parking lot; the cloud server sending a second response message to the vehicle, the second response message including the fifth payment link resource and second indication information, the second indication information being used to indicate that the fifth payment link resource is risky.

[0101] For example, when vehicle 100 detects that it is about to enter parking lot c, it can request the payment link resource corresponding to parking lot c from the cloud server. In response to receiving the vehicle's request, the cloud server can send a response message to vehicle 100. This response message may include information about the QR code c and indication information, which indicates that the QR code c is high-risk. In response to receiving this response message, vehicle 100 can control its display screen to show a prompt message, which alerts the user that the payment link resource for parking lot c obtained from the cloud server is high-risk.

[0102] Optionally, for medium- and high-risk payment link resources, the cloud server can include the payment link resource and its corresponding risk level when sending the first response message to the vehicle.

[0103] For example, if the first response message carries a payment link resource and the risk level corresponding to the payment link resource is medium risk, the vehicle can indicate that the payment link is medium risk through a prompt message and display a yellow warning on the display screen.

[0104] For example, if the first response message carries a payment link resource and the risk level corresponding to the payment link resource is high risk, the vehicle can indicate that the payment link is high risk through a prompt message and display a red warning on the display screen.

[0105] Optionally, the cloud server receives identification information and images of one or more parking lots sent by one or more mobile terminals, including: the cloud server receiving identification information of a third parking lot and an image including a fifth payment link resource of the third parking lot sent by a second mobile terminal; the cloud server obtaining a second account type corresponding to the fifth payment link resource; when the second account type is a private account, the cloud server does not establish a correspondence between the identification information of the third parking lot and the fifth payment link resource.

[0106] Steps S210 and S220 above describe the process by which the cloud server establishes a payment link resource library based on information sent by one or more mobile terminals (or, as crowdsourced data). The following section, in conjunction with steps S230 and S240, describes the process by which a vehicle requests payment link resources from the cloud server and pays parking fees.

[0107] S230, when the vehicle detects the user's intention to drive the vehicle into the first parking lot, it sends a first request message to the cloud server, which is used to request the payment link resource of the first parking lot.

[0108] Accordingly, the cloud server receives the first request message sent by the vehicle.

[0109] Optionally, the first request message may include identification information of the first parking lot. For example, the identification information of the first parking lot may include its location and name.

[0110] For example, vehicle 100 can send the first request message to a cloud server through communication system 130 within vehicle 100.

[0111] Optionally, detecting the user's intention to drive the vehicle into the first parking lot includes: the vehicle detecting that the user selects a navigation route from the current location to the first parking lot through an in-vehicle map application.

[0112] Optionally, detecting a user's intention to drive a vehicle into the first parking lot includes: determining, based on data collected by the vehicle's sensors, that the vehicle is about to enter the entrance gate of the first parking lot.

[0113] Optionally, detecting the user's intention to drive the vehicle into the first parking lot includes: determining, through data collected by the vehicle's sensors, that the vehicle has passed through the entrance gate of the first parking lot, and determining, through location information obtained by the positioning device, that the vehicle is currently located inside the first parking lot.

[0114] S240, the cloud server sends a first response message to the vehicle based on the first request message and the mapping relationship.

[0115] Accordingly, the vehicle receives the first response message sent by the cloud server.

[0116] Optionally, the cloud server sends a first response message to the vehicle based on the first request message and the mapping relationship, including: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, the cloud server sends the first payment link resource to the vehicle based on the first request message; wherein, the method 200 further includes: when the first payment link resource is detected to be valid and the vehicle's intention to leave the first parking lot is detected, the vehicle performs a parking fee payment operation based on the first payment link resource; when the parking fee payment operation is successfully performed, the vehicle sends a first instruction information to the cloud server, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource; in response to receiving the first instruction information, the cloud server maintains the correspondence between the first parking lot and the first payment link resource in the mapping relationship.

[0117] Optionally, detecting the user's intention to drive the vehicle away from the first parking lot includes: determining, through the location information obtained by the vehicle via the positioning device, that the vehicle is currently located in the first parking lot and selecting a navigation route from the current location to a destination (which is not the first parking lot) via an in-vehicle map application.

[0118] Optionally, detecting the user's intention to drive the vehicle away from the first parking lot includes: determining that the vehicle is located in the first parking lot based on the location information obtained by the positioning device and switching the vehicle from a power-off state to a power-on state.

[0119] Optionally, detecting the user's intention to drive the vehicle away from the first parking lot includes: determining, based on data collected by the vehicle's sensors, that the distance between the vehicle and the exit gate of the first parking lot is less than or equal to a preset distance.

[0120] For example, when the system detects that a user intends to drive vehicle 100 into the first parking lot, vehicle 100 can send a request message 1 to the cloud server. This request message 1 requests the payment link resource corresponding to parking lot a. In response to receiving the request message 1, the cloud server can send a response message 1 to vehicle 100 based on the mapping relationship. This response message 1 may include information about the QR code a. In response to receiving the response message 1, vehicle 100 can perform anti-counterfeiting verification on the QR code a. If the verification is successful, the QR code a is deemed valid; otherwise, it is deemed invalid.

[0121] Optionally, detecting that the first payment link resource is valid includes determining that the first payment link resource is valid when one or more of the following conditions are met: the account name corresponding to the first payment link resource is associated with the name of the first parking lot; the account type corresponding to the first payment link resource is a corporate account; or, the transaction amount corresponding to the first payment link resource matches the duration of the vehicle's parking in the first parking lot.

[0122] When QR code a passes anti-counterfeiting verification (or QR code a is detected as valid) and the user's intention to drive vehicle 100 away from parking lot a is detected, vehicle 100 can automatically perform parking fee payment based on QR code a. After successfully performing parking fee payment, vehicle 100 can send instruction information 1 to the cloud server, which instructs vehicle 100 to successfully pay the parking fee in parking lot a based on QR code a. In response to receiving instruction information 1, the cloud server can maintain the correspondence between parking lot a and QR code a in Table 1 unchanged.

[0123] Optionally, taking the mapping relationship shown in Table 2 as an example, after receiving instruction information 1, the cloud server can also adjust the confidence level of the payment link resource corresponding to parking lot a and the number of successful parking fee payments. For example, the cloud server updates the mapping relationship to the mapping relationship shown in Table 4.

[0124] Table 4

[0125] The above example illustrates how the confidence level of the payment link resource in parking lot a increases by 0.1% after a successful payment of parking fees once. This embodiment is not limited to this; the relationship between the confidence level of the parking lot's payment link resource and the number of successful parking fee payments can also be determined in other ways.

[0126] Optionally, the response message 1 sent by the cloud server to vehicle 100 may also include the number of times parking fees have been successfully paid using QR code a.

[0127] Optionally, the method 200 further includes: in response to receiving the response message 1, the vehicle can display the number of times it has successfully paid parking fees using QR code a on a display device.

[0128] Optionally, the cloud server sends a first response message to the vehicle based on the first request message and the mapping relationship, including: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, sending the first payment link resource to the vehicle based on the first request message; wherein, the method 200 further includes: when the first payment link resource is detected to be invalid and the vehicle is in the first parking lot, the vehicle obtains the second payment link resource of the first parking lot based on images collected by a dashcam and / or an external camera device; when the user's intention to drive the vehicle away from the first parking lot is detected, the vehicle performs a parking fee payment operation based on the second payment link resource; when the parking fee payment operation is successfully performed, the vehicle sends a second request message to the cloud server, the second request message being used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, the second request message including the second payment link resource; in response to receiving the second request message, the cloud server updates the correspondence between the first parking lot and the first payment link resource in the mapping relationship to the correspondence between the first parking lot and the second payment link resource.

[0129] For example, when the system detects a user's intention to drive their vehicle into parking lot b, vehicle 100 can send a request message 2 to the cloud server. This request message 2 requests the payment link resource corresponding to parking lot b. In response to receiving the request message 2, the cloud server can send a response message 2 to vehicle 100 based on the mapping relationship. This response message 2 may include information about the QR code b. In response to receiving the response message 2, vehicle 100 can perform anti-counterfeiting verification on the QR code b.

[0130] When it is detected that QR code b has failed the anti-counterfeiting authentication (or QR code b is detected to be invalid) and vehicle 100 is in parking lot b, vehicle 100 can obtain the payment link resource of parking lot b through the image collected by the dashcam and / or the image collected by the camera outside the cabin.

[0131] For example, vehicle 100 can obtain QR code d by processing images captured by the dashcam and images captured by the external camera. When the system detects the user's intention to drive vehicle 100 away from parking lot b, vehicle 100 can automatically perform a parking fee payment operation based on QR code d. After successfully performing the parking fee payment operation, vehicle 100 can send a request message 3 to the cloud server, which instructs the cloud server to update the payment link resource corresponding to parking lot b in the mapping relationship from QR code b to QR code d. In response to receiving the request message 3, the cloud server can update the mapping relationship from Table 1 to as shown in Table 5.

[0132] Table 5

[0133] Optionally, before the cloud server updates the mapping relationship between the first parking lot and the first payment link resource to the mapping relationship between the first parking lot and the second payment link resource, the method 200 further includes: the cloud server performing anti-counterfeiting authentication on the second payment link resource.

[0134] Optionally, the cloud server sends a first response message to the vehicle based on the first request message and the mapping relationship, including: when the mapping relationship does not include the correspondence between the first parking lot and the first payment link resource, the cloud server sends the first response message to the vehicle based on the first request message, the first response message indicating that the cloud server does not store the payment link resource for the first parking lot; wherein, the method 200 further includes: when the vehicle is detected to be in the first parking lot, the vehicle obtains the third payment link resource for the first parking lot based on images captured by a dashcam and / or an external camera; when the vehicle's intention to leave the first parking lot is detected, the vehicle performs a parking fee payment operation based on the third payment link resource; when the parking fee payment operation is successfully performed, the vehicle sends a third request message to the cloud server, the third request message requesting the addition of the correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource; in response to receiving the third request message, the cloud server adds the correspondence between the first parking lot and the third payment link resource in the mapping relationship.

[0135] For example, when the system detects a user's intention to drive their vehicle into parking lot d, vehicle 100 can send a request message 4 to the cloud server. This request message 4 requests the payment link resource corresponding to parking lot d. In response to receiving the request message 4, the cloud server can send a response message 4 to vehicle 100 based on the mapping relationship. This response message 4 indicates that the cloud server has not saved the payment link resource corresponding to parking lot d.

[0136] In response to receiving response message 4, vehicle 100 can determine the payment link resource of parking lot d using images captured by the dashcam and / or images captured by an external camera. For example, vehicle 100 can obtain QR code e by processing the images captured by the dashcam and the external camera. When the vehicle detects the user's intention to leave parking lot d, it can automatically perform parking fee payment based on QR code e. After successfully performing parking fee payment, vehicle 100 can send request message 5 to the cloud server. Request message 5 instructs the cloud server to add a mapping between parking lot d and QR code e in the mapping relationship. Request message 5 includes the identification information of parking lot d and the information of QR code e. In response to receiving request message 5, the cloud server can update the mapping relationship from Table 1 to Table 6.

[0137] Table 6

[0138] Figure 3 shows a schematic flowchart of a parking fee payment method 300 provided in an embodiment of this application. The method 300 can be executed by the vehicle 100 described above, and includes:

[0139] S301, obtain the user's intention to drive the vehicle into the first parking lot.

[0140] The process of obtaining the user's intention to drive the vehicle into the first parking lot can be referred to the description in the above embodiments, and will not be repeated here.

[0141] S302, send a first request message to the cloud server, which is used to request the payment link resource of the first parking lot.

[0142] For example, the first request message can be the aforementioned request message 1.

[0143] Optionally, the first request message includes the identification information of the first parking lot.

[0144] S303 receives the first response message sent by the cloud server.

[0145] For example, the first response message is the response message 1 mentioned above.

[0146] S304, determine whether the first response message carries the payment link resource for the first parking lot.

[0147] For example, if the first response message carries the first payment link resource for the first parking lot, execute S305; otherwise, execute S308.

[0148] S305, determine whether the first payment link resource is valid.

[0149] For example, if the first payment link resource is valid, then S306 is executed; otherwise, S308 is executed.

[0150] S306, upon obtaining the user's intention to drive the vehicle away from the first parking lot, executes the operation of paying the parking fee.

[0151] Optionally, the first response message may include a payment link resource for the first parking lot and the number of successful parking fee payments for the first parking lot.

[0152] For example, Figure 4 illustrates a graphical user interface (GUI) provided in an embodiment of this application.

[0153] Upon receiving the initial response message, the vehicle can display a prompt on the central control screen stating, "The parking lot payment QR code has been received from the server. Historically, this QR code has been successfully used to pay parking fees 30 times. The QR code has high confidence; please pay with confidence," along with payment and cancellation controls. Upon the user clicking the payment control or issuing a voice payment command, the vehicle can complete the parking fee payment operation.

[0154] Optionally, the first response message may include a payment link resource for the first parking lot and a second instruction message indicating that the payment link resource is risky.

[0155] For example, Figure 5 illustrates another GUI provided in an embodiment of this application.

[0156] Upon receiving the first response message, the vehicle can display a prompt message on the central control screen stating "A payment QR code for the parking lot has been received from the server. This QR code is risky; please proceed with caution," along with payment and cancellation controls. For example, the cancellation control displays a countdown timer (e.g., "10 seconds"). If no user clicks the payment control or issues a voice payment command when the countdown ends, the vehicle can automatically cancel the payment.

[0157] S307, after successfully executing the parking fee payment operation, sends a first instruction message to the cloud server, which instructs the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource.

[0158] Accordingly, upon receiving the first instruction, the cloud server can update the mapping relationship. For example, the cloud server can increase the confidence level of the payment link resource corresponding to the parking lot and increment the number of successful parking fee payments for that parking lot by 1.

[0159] S308, when a vehicle is detected to be in the first parking lot, obtains the payment link resource of the first parking lot based on images captured by the dashcam and / or the external cockpit camera.

[0160] For example, when the vehicle determines that it is currently in the first parking lot based on data collected by the positioning sensor, the vehicle can process and analyze images collected by the dashcam and / or the camera outside the cabin to obtain the payment link resources of the first parking lot.

[0161] Optionally, the vehicle may also send images captured by the dashcam and / or external cameras to a cloud server, which will then analyze the images and send the resulting payment link for the first parking lot to the vehicle.

[0162] S309, upon receiving the user's intention to leave the first parking lot in a timely manner, executes the operation of paying the parking fee based on the payment link resource of the first parking lot.

[0163] After successfully executing the parking fee payment operation, S310 sends the payment link resource of the first parking lot to the cloud server.

[0164] For example, if it is determined in S304 that the first response message carries the payment link resource of the first parking lot and in S305 it is determined that the first payment link resource is invalid, then in S310, the vehicle can send a second request message to the cloud server. The second request message is used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the payment link resource obtained in S308. The second request message includes the payment link resource obtained in S308.

[0165] For example, if it is determined in S304 that the first response message does not carry the payment link resource of the first parking lot, then in S310, the vehicle can send a third request message to the cloud server. The third request message is used to request the addition of the correspondence between the first parking lot and the payment link resource obtained in S308 in the mapping relationship. The third request message includes the identification information of the first parking lot and the payment link resource obtained in S308.

[0166] Figure 6 shows a schematic block diagram of a parking fee payment device 600 provided in an embodiment of this application. The device 600 includes: a receiving unit 610, configured to receive identification information and images of one or more parking lots sent by one or more mobile terminals, the images including payment link resources for one or more parking lots; a mapping relationship establishment unit 620, configured to establish a mapping relationship based on the identification information and images of the one or more parking lots, the mapping relationship including the correspondence between the identification information of each parking lot and the payment link resource of each parking lot; the receiving unit 610 is further configured to receive a first request message sent by a vehicle, the first request message requesting payment link resources for a first parking lot; and a sending unit 630, configured to send a first response message to the vehicle based on the first request message and the mapping relationship.

[0167] Optionally, the sending unit 630 is specifically configured to: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, send the first payment link resource to the vehicle according to the first request message; the receiving unit 610 is further configured to receive the first instruction information sent by the vehicle, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource; the mapping relationship establishment unit 620 is further configured to maintain the correspondence between the first parking lot and the first payment link resource in the mapping relationship in response to the receiving unit receiving the first instruction information.

[0168] Optionally, the sending unit 630 is specifically configured to: when the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, send the first payment link resource to the vehicle according to the first request message; the receiving unit 610 is further configured to receive a second request message sent by the vehicle, the second request message being used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, the second request message including the second payment link resource; the mapping relationship establishment unit 620 is further configured to, in response to the receiving unit receiving the second request message, update the correspondence between the first parking lot and the first payment link resource in the mapping relationship to the correspondence between the first parking lot and the second payment link resource.

[0169] Optionally, the sending unit 630 is specifically configured to: when the mapping relationship does not include the correspondence between the first parking lot and the first payment link resource, send the first response message to the vehicle according to the first request message, the first response message indicating that the payment link resource of the first parking lot is not stored in the cloud server; the receiving unit 610 is further configured to receive a third request message sent by the vehicle, the third request message requesting the addition of the correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource; the mapping relationship establishment unit 620 is further configured to add the correspondence between the first parking lot and the third payment link resource in the mapping relationship in response to the receiving unit receiving the third request message.

[0170] Optionally, the device further includes an acquisition unit, wherein the receiving unit 610 is configured to receive the identification information of the second parking lot and an image including the fourth payment link resource of the second parking lot sent by the first mobile terminal; the acquisition unit is configured to acquire the first account name, the first account type, and the transaction amount of the first mobile terminal corresponding to the fourth payment link resource; wherein the mapping relationship establishment unit 620 is specifically configured to establish a correspondence between the second parking lot and the fourth payment link resource when one or more of the following conditions are met: the first account name is associated with the name of the second parking lot; the first account type is a corporate account; or, the transaction amount matches the parking duration of the first vehicle in the second parking lot, and the first mobile terminal is associated with the first vehicle.

[0171] Optionally, the device further includes an acquisition unit, a receiving unit 610, configured to receive the identification information of the third parking lot and an image including the fifth payment link resource of the third parking lot sent by the second mobile terminal; the acquisition unit is configured to acquire the second account type corresponding to the fifth payment link resource; wherein, the mapping relationship establishment unit 620 is specifically configured to: when the second account type is a private account, establish a correspondence between the third parking lot and the fifth payment link resource and mark the fifth payment link resource as a risky payment link resource.

[0172] Optionally, the receiving unit 610 is further configured to receive a fourth request message sent by the vehicle, the fourth request message being used to request the payment link resource of the third parking lot; the sending unit 630 is further configured to send a second response message to the vehicle, the second response message including the fifth payment link resource and second indication information, the second indication information being used to indicate that the fifth payment link resource is risky.

[0173] Figure 7 shows a schematic block diagram of another parking fee payment device 700 provided in an embodiment of this application. The device 700 includes: a detection unit 710 for detecting the intention of a vehicle to enter a first parking lot; a sending unit 720 for sending a first request message to a cloud server, the first request message requesting a first payment link resource of the first parking lot, the cloud server storing a mapping relationship including the correspondence between the identification information of each parking lot in one or more parking lots and the payment link resource of each parking lot; a receiving unit 730 for receiving a first response message, the first response message being a response to the first request message; and a parking fee payment unit 740 for performing a parking fee payment operation based on the first response message, after the detection unit detects the intention of a vehicle to leave the first parking lot.

[0174] Optionally, the one or more parking lots include the first parking lot, the first response message includes the first payment link resource, and the parking fee payment unit 740 is specifically used to: when the detection unit detects that the first payment link resource is valid and detects the vehicle's intention to leave the first parking lot, perform a parking fee payment operation based on the first payment link resource; the sending unit 720 is further used to send a first instruction information to the cloud server, the first instruction information being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource.

[0175] Optionally, the one or more parking lots include the first parking lot, the first response message includes the first payment link resource, the detection unit 710 is used to obtain the second payment link resource of the first parking lot based on images collected by the dashcam and / or the external camera when the detection unit detects that the first payment link resource is invalid and the vehicle is in the first parking lot; the parking fee payment unit 740 is used to perform a parking fee payment operation based on the second payment link resource when the intention of the vehicle to leave the first parking lot is detected; the sending unit 720 is further used to send a second request message to the cloud server when the parking fee payment unit successfully performs the parking fee payment operation, the second request message is used to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource, and the second request message includes the second payment link resource.

[0176] Optionally, the acquisition unit is configured to acquire a third payment link resource for the first parking lot based on images captured by a dashcam and / or an external camera when the first response message indicates that the cloud server does not store the payment link resource for the first parking lot and the detection unit detects that the vehicle is in the first parking lot; the parking fee payment unit 740 is configured to perform a parking fee payment operation based on the third payment link resource when the detection unit detects that the vehicle intends to leave the first parking lot; the sending unit 720 is further configured to send a third request message to the cloud server when the parking fee payment unit successfully performs the parking fee payment operation, the third request message being used to request the addition of a correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource.

[0177] It should be understood that the division of units in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the device can be implemented by a processor calling software; for example, the device includes a processor connected to memory, which stores instructions. The processor calls the instructions stored in memory to implement any of the above methods or to implement the functions of each unit in the device. The processor can be, for example, a general-purpose processor, such as a CPU or microprocessor, and the memory can be internal or external to the device. Alternatively, the units in the device can be implemented as hardware circuits. The functions of some or all units can be implemented through the design of the hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an ASIC, and the functions of some or all units are implemented through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a PLD, such as an FPGA, which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby implementing the functions of some or all units. All units of the above devices can be implemented entirely through processor calling software, or entirely through hardware circuits, or partially through processor calling software with the remaining parts implemented through hardware circuits.

[0178] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a CPU, microprocessor, GPU, or DSP. In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement the functions of some or all of the above units. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as an NPU, TPU, or DPU.

[0179] As can be seen, each unit in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0180] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a System-on-a-Chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and AI processor, CPU and GPU, etc.

[0181] This application also provides a device for paying parking fees. The device includes a processing unit and a storage unit, wherein the storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to cause the device to perform the methods or steps described in the above embodiments.

[0182] Optionally, if the device for paying parking fees is located in the vehicle, the processing unit may be the processor 121-12n shown in FIG1.

[0183] This application also provides a system for paying parking fees, which may include a camera device and a computing platform, the computing platform including the aforementioned parking fee payment device 700.

[0184] This application also provides a server, which may include the above-described parking fee payment device 600.

[0185] This application also provides a vehicle that may include the above-described parking fee payment device 700 or the above-described parking fee payment system.

[0186] This application also provides a computer program product, which includes computer program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0187] This application also provides a computer-readable medium storing program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0188] This application also provides a chip, which includes a circuit for performing the methods described in the above embodiments.

[0189] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, power-on erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0190] It should be understood that in the embodiments of this application, the memory may include read-only memory and random access memory, and provides instructions and data to the processor.

[0191] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0192] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0193] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0194] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0195] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0196] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0197] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0198] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be covered. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for paying parking fees, characterized in that, include: Receive identification information and images of one or more parking lots sent by one or more mobile terminals, wherein the images include payment link resources of one or more parking lots; Based on the identification information of one or more parking lots and the image, a mapping relationship is established, wherein the mapping relationship includes the correspondence between the identification information of each parking lot in the one or more parking lots and the payment link resource of each parking lot; Receive a first request message sent by the vehicle, the first request message being used to request payment link resources for the first parking lot; Based on the first request message and the mapping relationship, a first response message is sent to the vehicle.

2. The method according to claim 1, characterized in that, Sending a first response message to the vehicle based on the first request message and the mapping relationship includes: When the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, the first payment link resource is sent to the vehicle according to the first request message; The method further includes: Receive a first instruction message sent by the vehicle, the first instruction message being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource; In response to receiving the first instruction information, the mapping relationship between the first parking lot and the first payment link resource is maintained.

3. The method according to claim 1, characterized in that, Sending a first response message to the vehicle based on the first request message and the mapping relationship includes: When the mapping relationship includes the correspondence between the first parking lot and the first payment link resource, the first payment link resource is sent to the vehicle according to the first request message; The method further includes: The system receives a second request message sent by the vehicle. The second request message requests that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource. The second request message includes the second payment link resource. In response to receiving the second request message, the mapping relationship between the first parking lot and the first payment link resource is updated to the mapping relationship between the first parking lot and the second payment link resource.

4. The method according to claim 1, characterized in that, Sending a first response message to the vehicle based on the first request message and the mapping relationship includes: When the mapping relationship does not include the correspondence between the first parking lot and the first payment link resource, the first response message is sent to the vehicle according to the first request message. The first response message is used to indicate that the payment link resource of the first parking lot is not stored in the cloud server. The method further includes: Receive a third request message sent by the vehicle, the third request message being used to request the addition of a correspondence between the first parking lot and the third payment link resource in the mapping relationship, the third request message including the third payment link resource; In response to receiving the third request message, a correspondence between the first parking lot and the third payment link resource is added to the mapping relationship.

5. The method according to any one of claims 1 to 4, characterized in that, The receipt of one or more parking lot identification information and images sent by one or more mobile terminals includes: Receive the identification information of the second parking lot and the image including the fourth payment link resource of the second parking lot sent by the first mobile terminal; Obtain the first account name, first account type, and transaction amount of the first mobile terminal corresponding to the fourth payment link resource; The establishment of the mapping relationship includes: A correspondence is established between the identification information of the second parking lot and the fourth payment link resource when one or more of the following conditions are met: The first account name is associated with the name of the second parking lot; The first account type is a corporate account; or, The transaction amount is matched with the duration the first vehicle is parked in the second parking lot, and the first mobile terminal is associated with the first vehicle.

6. The method according to any one of claims 1 to 5, characterized in that, The receipt of one or more parking lot identification information and images sent by one or more mobile terminals includes: Receive the identification information of the third parking lot and an image including the fifth payment link resource of the third parking lot sent by the second mobile terminal; Obtain the second account type corresponding to the fifth payment link resource; The establishment of the mapping relationship includes: When the second account type is a private account, a correspondence is established between the third parking lot and the fifth payment link resource, and the fifth payment link resource is marked as a risky payment link resource.

7. The method according to claim 6, characterized in that, The method further includes: Receive a fourth request message sent by the vehicle, the fourth request message being used to request the payment link resource of the third parking lot; A second response message is sent to the vehicle. The second response message includes the fifth payment link resource and second indication information, the second indication information being used to indicate that the fifth payment link resource is risky.

8. A method for paying parking fees, characterized in that, include: The user's intention to drive their vehicle into the first parking lot was detected; A first request message is sent to the cloud server. The first request message is used to request the first payment link resource of the first parking lot. The cloud server stores a mapping relationship, which includes the correspondence between the identification information of each parking lot in one or more parking lots and the payment link resource of each parking lot. Receive a first response message, which is a response to the first request message; Based on the first response message, upon detecting the user's intention to drive their vehicle away from the first parking lot, an operation to pay the parking fee is performed.

9. The method according to claim 8, characterized in that, The one or more parking lots include the first parking lot, and the first response message includes the first payment link resource. The step of performing the parking fee payment operation upon detecting the user's intention to drive their vehicle away from the first parking lot, based on the first response message, includes: When the first payment link resource is detected to be valid and the user's intention to drive the vehicle away from the first parking lot is detected, the parking fee payment operation is performed according to the first payment link resource; Send a first instruction message to the cloud server, the first instruction message being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource.

10. The method according to claim 8, characterized in that, The one or more parking lots include the first parking lot, the first response message includes the first payment link resource, and the step of performing the operation of paying parking fees upon detecting the user's intention to drive the vehicle away from the first parking lot according to the first response message includes: When the first payment link resource is detected to be invalid and the vehicle is in the first parking lot, the second payment link resource of the first parking lot is obtained based on the images collected by the dashcam and / or the camera outside the cabin. Upon detecting the user's intention to drive their vehicle away from the first parking lot, the parking fee payment operation is performed based on the second payment link resource; The method further includes: Upon successful execution of the parking fee payment operation, a second request message is sent to the cloud server. The second request message requests that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource. The second request message includes the second payment link resource.

11. A device for paying parking fees, characterized in that, include: The detection unit is used to detect the user's intention to drive the vehicle into the first parking lot; The sending unit is used to send a first request message to the cloud server. The first request message is used to request the first payment link resource of the first parking lot. The cloud server stores a mapping relationship, which includes the correspondence between the identification information of each parking lot in one or more parking lots and the payment link resource of each parking lot. A receiving unit is configured to receive a first response message, wherein the first response message is a response to the first request message; The parking fee payment unit is used to, based on the first response message, respond when the detection unit detects that the user has driven the vehicle away from the first parking space. The venue intends to execute the payment of parking fees.

12. The apparatus according to claim 11, characterized in that, The one or more parking lots include the first parking lot, and the first response message includes the first payment link resource. The parking fee payment unit is specifically used to: when the detection unit detects that the first payment link resource is valid and detects the user's intention to drive the vehicle away from the first parking lot, perform the operation of paying the parking fee according to the first payment link resource; The sending unit is further configured to send a first instruction message to the cloud server, the first instruction message being used to instruct the vehicle to successfully pay the parking fee in the first parking lot based on the first payment link resource.

13. The apparatus according to claim 11, characterized in that, The one or more parking lots include the first parking lot, the first response message includes the first payment link resource, and the device further includes an acquisition unit. The acquisition unit is configured to acquire a second payment link resource of the first parking lot based on images collected by the dashcam and / or the camera outside the cabin when the detection unit detects that the first payment link resource is invalid and the vehicle is in the first parking lot; The parking fee payment unit is used to perform a parking fee payment operation based on the second payment link resource when it detects the user's intention to drive the vehicle away from the first parking lot. The sending unit is further configured to send a second request message to the cloud server when the parking fee payment unit successfully executes the parking fee payment operation. The second request message is configured to request that the payment link resource corresponding to the first parking lot in the mapping relationship be updated from the first payment link resource to the second payment link resource. The second request message includes the second payment link resource.

14. The apparatus according to claim 11, characterized in that, The device also includes an acquisition unit. The acquisition unit is configured to acquire the third payment link resource of the first parking lot based on images collected by the dashcam and / or the camera outside the cabin when the first response message indicates that the cloud server does not store the payment link resource of the first parking lot and the detection unit detects that the vehicle is in the first parking lot. The parking fee payment unit is used to perform a parking fee payment operation based on the third payment link resource when the detection unit detects the user's intention to drive the vehicle away from the first parking lot. The sending unit is further configured to send a third request message to the cloud server when the parking fee payment unit successfully executes the parking fee payment operation. The third request message is used to request the addition of a correspondence between the first parking lot and the third payment link resource in the mapping relationship. The third request message includes the third payment link resource.

15. A device for paying parking fees, characterized in that, include: Memory, used to store computer programs; A processor for executing a computer program stored in the memory to cause the apparatus to perform the method as described in any one of claims 1 to 10.

16. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 11 to 14.

Images