Vehicle parking payment method and device

Abstract

The embodiment of the invention provides a vehicle parking payment method and device, and the method comprises the steps: enabling a vehicle terminal to submit a vehicle leaving instruction to a server in a vehicle parking payment process, and receiving a payment address returned by the server, starting a client installed on the vehicle terminal based on the payment address, transmitting the payment address and the vehicle identifier, operating a virtual container deployed by the client, loading the payment address through the virtual container, and cooperating with the server according to the vehicle identifier to carry out payment query processing so as to carry out payment processing according to the obtained to-be-paid fee. Therefore, the parking payment of the vehicle is realized through the cooperation of the vehicle terminal and the server.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a vehicle parking payment method and device. Background Art

[0002] With the continuous development and promotion of the Internet and smart hardware, the application scope of various application services provided by the Internet and smart devices is becoming wider and wider. In this case, many service processing implementations through smart devices have emerged, such as the implementation scenario of parking payment through user terminals. Users can use the user terminal to scan the QR code of the parking lot to pay the parking fee. However, with the continuous increase in the number of vehicles, when leaving many parking lots, they often need to queue up at the exit gate of the parking lot to pay. Summary of the Invention

[0003] One or more embodiments of this specification provide a vehicle parking fee payment method, applicable to an in-vehicle terminal. The method comprises: submitting a vehicle departure instruction to a server, and receiving a payment address returned by the server. Based on the payment address, a client installed on the in-vehicle terminal is launched, the payment address and vehicle identification are passed in, and a virtual container deployed by the client is run. The payment address is loaded through the virtual container, and payment query processing is performed in cooperation with the server based on the vehicle identification, so as to process payment based on the obtained pending payment amount.

[0004] One or more embodiments of this specification provide another method for paying parking fees on a server side. The method comprises: performing a parking lot query based on a vehicle identification carried in a vehicle departure instruction submitted by a vehicle terminal to obtain a parking location; generating a payment address for the parking location and returning it to the vehicle terminal; and performing a payment query with a virtual container deployed by a client installed on the vehicle terminal to process the payment of the parking location and return the obtained payment to the virtual container for payment processing.

[0005] One or more embodiments of this specification provide a vehicle parking payment device that runs on a vehicle terminal, and the device includes: a departure instruction submission module, configured to submit a vehicle departure instruction to a server, and receive a payment address returned by the server. A virtual container operation module, configured to start a client installed on the vehicle terminal based on the payment address, pass in the payment address and vehicle identification, and run the virtual container deployed by the client. A payment query module, configured to load the payment address through the virtual container and cooperate with the server to perform payment query processing based on the vehicle identification, so as to perform payment processing based on the obtained fees to be paid.

[0006] One or more embodiments of this specification provide another vehicle parking payment device, which operates on a server, and includes: a parking place query module, configured to query a parking place based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain a parking place; a payment address generation module, configured to generate the payment address of the parking place and return it to the vehicle terminal; and a payment query processing module, configured to cooperate with a virtual container deployed by a client installed on the vehicle terminal to perform payment query processing on the parking place, and return the obtained pending payment fee to the virtual container for payment processing.

[0007] One or more embodiments of this specification provide a vehicle parking payment device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein when executed, the computer-executable instructions cause the processor to: submit a vehicle departure instruction to a server, and receive a payment address returned by the server. Based on the payment address, a client installed on a vehicle terminal is started, the payment address and vehicle identification are passed in, and a virtual container deployed by the client is run. The payment address is loaded through the virtual container, and payment query processing is performed in cooperation with the server based on the vehicle identification, so as to process payment based on the obtained fees to be paid.

[0008] One or more embodiments of this specification provide another vehicle parking fee payment device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein when executed, the computer-executable instructions cause the processor to: query a parking lot based on a vehicle identification carried in a vehicle departure instruction submitted by a vehicle terminal to obtain a parking lot; generate a payment address for the parking lot and return it to the vehicle terminal; and cause a virtual container deployed in conjunction with a client installed on the vehicle terminal to query the parking lot for payment and return the received payment to the virtual container for payment processing.

[0009] One or more embodiments of this specification provide a computer-readable storage medium for storing computer-executable instructions, which, when executed, implement the following process: submitting a vehicle departure instruction to a server and receiving a payment address returned by the server. Based on the payment address, launching a client installed on the vehicle terminal, passing in the payment address and vehicle identification, and running a virtual container deployed by the client. Loading the payment address through the virtual container and cooperating with the server to perform payment query processing based on the vehicle identification, so as to process the payment based on the obtained pending fees.

[0010] One or more embodiments of this specification provide another computer-readable storage medium for storing computer-executable instructions that, when executed, implement the following process: querying a parking lot based on the vehicle identification carried in the vehicle departure instruction submitted by a vehicle terminal to obtain a parking lot; generating a payment address for the parking lot and returning it to the vehicle terminal; and executing a payment query with a virtual container deployed by a client installed in the vehicle terminal to process the payment of the parking lot and return the obtained pending payment fee to the virtual container for payment processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate one or more embodiments of this specification or technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments described in this specification. Those skilled in the art can derive other drawings based on these drawings without inventive effort. In order to more clearly illustrate one or more embodiments of this specification or technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments described in this specification. Those skilled in the art can derive other drawings based on these drawings without inventive effort. Figure 1 A schematic diagram of an implementation environment of a vehicle parking fee payment method provided in one or more embodiments of this specification; Figure 2 A process flow chart of a vehicle parking fee payment method provided in one or more embodiments of this specification; Figure 3 A processing sequence diagram of a vehicle parking fee payment method applied to a first vehicle payment scenario provided in one or more embodiments of this specification; Figure 4 A processing sequence diagram of a vehicle parking fee payment method applied to a second vehicle payment scenario provided in one or more embodiments of this specification; Figure 5 A flowchart of another method for paying for parking a vehicle provided in one or more embodiments of this specification; Figure 6 A schematic diagram of an embodiment of a vehicle parking fee payment device provided in one or more embodiments of this specification; Figure 7 A schematic diagram of another embodiment of a vehicle parking fee payment device provided in one or more embodiments of this specification; Figure 8A schematic diagram of the structure of a vehicle parking fee payment device provided in one or more embodiments of this specification; Figure 9 A schematic structural diagram of another vehicle parking payment device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0012] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0013] The vehicle parking fee payment method provided in one or more embodiments of this specification can be applied to the implementation environment of parking fee payment. Figure 1 , the implementation environment includes at least: Vehicle terminal 101, client 102, server 103; The vehicle terminal 101 refers to a terminal device configured in the vehicle, which realizes data processing or control of the vehicle and can also communicate with external systems to perform corresponding processing or control of the vehicle; The client 102 refers to a third-party application client installed on the vehicle terminal 101. The client can be in the form of an application, an application / program component, or an application / program container. The client 102 has a virtual container 102-1 installed on it. The virtual container 102-1 is used to load and run subroutines and can also be used to process vehicle parking fees or cooperate with the server 103 to process vehicle parking fees. The virtual container 102-1 specifically provides an execution framework or execution engine for loading and running subroutines. The server 103 is used to cooperate with the vehicle terminal 101 to perform vehicle entry-related processing and / or vehicle departure-related processing. Specifically, it can be used to respond to vehicle departure instructions uploaded by the vehicle terminal 101 through the SDK (Software Development Kit) and return the corresponding payment address to the vehicle terminal 101. The server 103 can also be used to cooperate with the virtual container 102-1 to perform payment-related processing, such as cooperating with the virtual container 102-1 to perform payment query processing and obtain the amount to be paid; In this implementation environment, the vehicle terminal 101 submits a vehicle departure instruction to the server 103. The server 103 queries the parking lot according to the vehicle identification carried in the vehicle departure instruction to obtain the parking lot, and returns the payment address of the parking lot to the vehicle terminal 101; the vehicle terminal 101 starts the client 102 installed on the vehicle terminal 101 based on the payment address and passes in the payment address and vehicle identification, and runs the virtual container 102-1 deployed by the client 102. The payment address is loaded through the virtual container 102-1 and the payment query is processed in cooperation with the server 103 according to the vehicle identification, so as to process the payment according to the obtained fees to be paid. In this way, the fees to be paid are obtained through the cooperation between the vehicle terminal and the server, so that the parking payment of the vehicle can be realized based on the fees to be paid.

[0014] It should be noted that the processing process of the vehicle terminal in this embodiment may be the processing process of the vehicle system. Therefore, the vehicle terminal in this embodiment may be replaced by the vehicle system.

[0015] One or more embodiments of a vehicle parking fee payment method provided in this specification are as follows: Reference Figure 2 The vehicle parking payment method provided in this embodiment can be applied to the vehicle terminal, and the method specifically includes steps S202 to S206.

[0016] Step S202: Submit the vehicle departure instruction to the server and receive the payment address returned by the server.

[0017] In the parking scenario, after a vehicle enters a parking lot for parking and starts to leave, the vehicle terminal can submit a vehicle departure instruction to the server after the vehicle starts, and initiate parking payment for the vehicle by submitting the vehicle departure instruction to the server. The server receives the vehicle departure instruction and can query the parking lot based on the vehicle departure instruction. After querying the parking lot where the current vehicle is parked, it generates and returns the payment address for the current vehicle to pay for leaving the parking lot.

[0018] During the specific execution process, the vehicle departure instruction may be generated after the vehicle departure detection is performed on the vehicle terminal. If the vehicle departure behavior is detected by the vehicle terminal, the vehicle departure instruction is generated and submitted to the server. The vehicle departure instruction may include a vehicle identification, which may be stored by the vehicle terminal or obtained by calling an interface by the vehicle terminal; Specifically, vehicle departure detection can be performed based on vehicle operation data, and a vehicle departure instruction can be submitted to the server after the vehicle departure action is detected; in the process of performing vehicle departure detection based on vehicle operation data, if the vehicle operation data meets the vehicle departure conditions, it is determined that the vehicle departure action is detected; for example, after receiving the vehicle start instruction, it is detected whether the vehicle stop time is less than a preset threshold, and if so, it is determined that the vehicle departure action is detected; for another example, if it is detected that the vehicle operation image contains departure behavior, it is determined that the vehicle departure behavior is detected.

[0019] In addition, vehicle departure detection can be performed based on the device interaction results with third-party devices, and a vehicle departure instruction can be submitted to the server after the vehicle departure action is detected; in the process of performing vehicle departure detection based on the device interaction results with third-party devices, if data communication is detected with the departure device installed in the exit area of ​​the parking lot, a vehicle departure instruction is submitted to the server.

[0020] The above specifically describes the process of detecting vehicle departures on the vehicle terminal and, upon detecting a vehicle departure, generating a vehicle departure instruction and submitting it to the server. Alternatively, the vehicle terminal can use the SDK to detect vehicle departures, generate a vehicle departure instruction upon detecting a vehicle departure, and submit it to the server. For example, the vehicle terminal may generate a vehicle departure instruction upon detecting that the vehicle has been idle for less than a preset threshold by invoking an SDK interface. In this embodiment, in addition to generating a vehicle departure instruction upon detecting a vehicle departure, a vehicle start instruction may also be used as the vehicle departure instruction; that is, upon detecting a vehicle start instruction, a vehicle departure instruction is submitted to the server.

[0021] The server includes a server that cooperates with the vehicle terminal to perform parking lot query and payment query processing for vehicle parking payment; the server can be a payment server, or it can be a module in the payment server for parking lot query and payment query processing, which is not limited in this embodiment.

[0022] During the specific implementation process, the SDK can be deployed on the vehicle terminal. When the SDK is deployed on the vehicle terminal, the vehicle terminal can send a vehicle departure instruction to the server through the deployed SDK to query the parking space; among them, the SDK and the server can be provided by the same service provider. For example, the vehicle terminal deploys the SDK provided by the payment service provider. If the vehicle terminal detects a vehicle start-up instruction, it sends a vehicle departure instruction to the server provided by the payment service provider through the SDK.

[0023] In specific implementation, after the vehicle terminal submits a vehicle departure instruction to the server, the server queries the parking space based on the vehicle departure instruction. Specifically, the parking space can be queried in the parking entry record based on the vehicle identification carried in the vehicle departure instruction. The parking space can also be obtained by matching the vehicle position uploaded by the vehicle terminal with the location information of the candidate parking space. The two can also be combined to obtain the parking space. In an optional implementation provided by this embodiment, the parking space query is performed in the following manner: The query result is obtained by querying the parking entry record according to the vehicle identification carried by the vehicle departure instruction; If the target entry record corresponding to the vehicle identification is found, the parking space is determined according to the target entry record; If the target entry record corresponding to the vehicle identification is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking place to obtain the parking place.

[0024] Specifically, if a target entry record corresponding to the vehicle identifier carried in the vehicle departure instruction is found, the parking place can be determined based on the target entry record. The parking place identifier carried in the target entry record can be used to determine the parking place; wherein the parking place identifier may include an identifier representing the uniqueness of the parking place, such as the parking place name or parking place number; In addition, if the target entry record corresponding to the vehicle identification carried by the vehicle departure instruction is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking places to obtain the parking place; optionally, the candidate parking place includes at least one parking place registered on the server side; wherein, the vehicle departure instruction may carry the vehicle position, or, if the target entry record corresponding to the vehicle identification is not found, a vehicle position collection reminder may be returned to the vehicle terminal, and the receiving vehicle terminal collects and uploads the vehicle position based on the vehicle position collection reminder. This embodiment does not limit this.

[0025] The above-mentioned vehicle terminal submits a vehicle departure instruction to the server. After receiving the vehicle departure instruction, the server queries the parking lot based on the vehicle departure instruction, and after querying the parking lot where the current vehicle is parked, generates and returns a payment address for the current vehicle to pay for leaving the parking lot at the parking lot; specifically, in the process of generating the payment address, the payment address can be generated according to the subroutine address of the payment subroutine generated by the server; in this case, the payment address may include the subroutine address of the payment subroutine generated by the server (payment subroutine address); in addition, the payment address can also be generated according to the third-party payment address of the parking lot; in this case, the payment address may include the third-party payment address of the parking lot that matches the vehicle identification (venue payment address / service provider payment address); among which, the third-party payment address of the parking lot refers to the access address of the payment program or payment subroutine provided by the parking service provider or parking service system of the parking lot itself; that is, the third-party payment address includes the access address of the payment program or payment subroutine corresponding to the parking lot that matches the vehicle identification. It should be noted that the relevant content of the parking space in the technical solution of this application is actually the interactive processing process with the parking service provider or parking service system. Therefore, the parking space in the technical solution of this application can be replaced by a parking service provider or parking service system.

[0026] Corresponding to the above-mentioned vehicle terminal sending a vehicle departure instruction to the server through the deployed SDK to query the vehicle location, when the vehicle terminal deploys the SDK, the vehicle terminal can also receive the payment address returned by the server through the SDK; it should be noted that when the vehicle terminal deploys the SDK, the data interaction between the vehicle terminal and the server can be carried out through the SDK, for example, the vehicle terminal receives the vehicle location collection reminder returned by the server through the SDK, collects the vehicle location according to the vehicle location collection reminder and uploads it to the server through the SDK, or the vehicle terminal receives the vehicle location collection reminder returned by the server through the SDK, calls the interface provided by the SDK to collect the vehicle location and upload it to the server; this embodiment will not be repeated here.

[0027] The parking entry record in this embodiment can be synchronized to the server by the parking service system. Specifically, when the parking lot entry equipment detects that a vehicle has entered the lot, it uploads the parking entry record to the parking service system, and the parking service system receives and synchronizes the parking entry record to the server. Optionally, the parking entry record carries at least one of the following: vehicle identification, parking lot identification, entry time, and entry location.

[0028] In addition, the parking entry record can also be generated based on the payment identification image collected and uploaded by the vehicle terminal after detecting the vehicle entering the parking lot. The payment identification image in this embodiment can be collected by calling at least one collection component deployed on the vehicle. In this embodiment, the parking entry record can be generated based on the payment identification image collected after detecting the vehicle entering the parking lot. In this way, the parking entry record is generated based on the vehicle entering the parking lot and the payment identification image collected by the vehicle terminal, improving the comprehensiveness of the generated parking entry record. In an optional implementation provided by this embodiment, the vehicle terminal obtains the payment identification image by performing the following operations: Carry out vehicle approach detection based on vehicle operation data collected by the vehicle terminal; If a vehicle entering the site is detected, an image of the vehicle entering the site is collected and image recognition is performed to obtain a payment identification image.

[0029] Optionally, the vehicle operation data includes vehicle behavior data generated during vehicle operation, collected vehicle operation images and / or device interaction results with third-party devices; vehicle approach detection includes device peer detection and / or device connection detection of third-party devices; vehicle approach images include images of the outside of the vehicle collected when the vehicle approach action occurs; payment identification images include images carrying payment identification, such as images carrying QR codes.

[0030] Specifically, vehicle approach detection can be performed based on vehicle operation data, and a vehicle approach image can be collected after the vehicle approach action is detected; in the process of performing vehicle approach detection based on vehicle operation data, if the vehicle operation image contains an approach action, the vehicle approach image is collected; for example, vehicle approach detection is performed based on the vehicle operation image collected by the vehicle terminal, and if a vehicle operation image containing an approach barrier lifting action is detected in the vehicle operation image, it is determined that the vehicle approach action is detected; In addition, vehicle approach detection can be performed based on the device interaction results with third-party devices, and vehicle approach images can be collected after the vehicle approach action is detected; in the process of performing vehicle approach detection based on the device interaction results with third-party devices, if data communication is detected with the approach device installed in the entrance area of ​​the parking lot, the vehicle approach image can be collected.

[0031] It should be noted that when the vehicle terminal is configured with SDK, if the vehicle terminal detects the vehicle entering the site, it can collect the vehicle entry image through SDK and perform image recognition to obtain the payment identification image, or the vehicle terminal can collect the vehicle entry image and perform image recognition through SDK to obtain the payment identification image, that is, if the vehicle entry action is detected, the vehicle entry image is collected and the payment identification image is obtained through SDK for image recognition; in addition, the vehicle terminal can perform vehicle entry detection, vehicle entry image collection and image recognition through SDK; for example, the vehicle terminal calls the interface provided by SDK to detect that the vehicle operation image contains the entry behavior, and then collects the vehicle entry image and performs image recognition to obtain the payment identification image.

[0032] Furthermore, based on the obtained payment identification image, the payment identification image is uploaded to the server. Specifically, the payment identification image can be uploaded to the server through the SDK; after receiving the payment identification image, the server can generate a parking entry record based on the payment identification image; that is, the vehicle terminal uploads the payment identification image to the server to generate a parking entry record; correspondingly, in an optional implementation manner provided by this embodiment, in the process of generating a parking entry record: first, the payment identification image is decoded to obtain a decoding address, and then the payment access verification is performed according to the decoding address, and after the verification is passed, the parking entry record is generated according to the decoding address, vehicle identification, entry time and / or entry location.

[0033] During the specific execution process, after the server receives the payment identification image, it first decodes the payment identification image to obtain the decoding address, and then performs payment access verification based on the decoding address, and generates a parking entry record after the verification is passed; optionally, during the payment access verification process, it is verified whether there is an access anomaly in the decoding address. If not, it is determined that the verification is passed. If so, it is determined that the verification is failed; or, it is verified whether the decoding address is the payment address of the parking lot, that is, whether the decoding address is associated with the parking lot. If so, it is determined that the verification is passed. If not, it is determined that the verification is failed; or, it is verified whether the decoding address is within the preset validity period. If so, it is determined that the verification is passed. If not, it is determined that the verification is failed.

[0034] Furthermore, the above payment access verification process can be combined, for example: Verify whether there is any access anomaly to the decoding address; if so, determine that the verification has failed; If not, verify whether the decoded address is associated with the parking place; if not, determine that the verification has failed; If so, verify whether the decoded address is within the preset validity period; if so, determine that the verification is passed; if not, determine that the verification is failed.

[0035] It should be noted that the vehicle identification, entry time and / or entry location required to generate the parking entry record can be uploaded by the vehicle terminal or through the SDK. It can be uploaded when uploading the payment identification image, or it can be uploaded based on the information returned by the server after the above-mentioned payment access verification is passed. This embodiment does not limit this.

[0036] In this embodiment, in addition to the vehicle terminal and the server cooperating to generate parking entry records based on the payment identification image, the vehicle terminal and the server can also cooperate to update the parking lot based on the payment identification image; optionally, the vehicle terminal performs vehicle entry detection based on the vehicle operation data collected by the vehicle terminal. If a vehicle entry action is detected, the vehicle entry image is collected and image recognition is performed through the SDK to obtain the payment identification image, and the payment identification image is uploaded to the server through the SDK to update the parking lot; correspondingly, the server decodes the payment identification image to obtain a decoding address, performs payment access verification based on the decoding address, and updates the third-party payment address of the parking lot based on the decoding address after the verification is passed.

[0037] In the process of updating the third-party payment address of the parking lot, the update verification can be performed based on the decoding address and the third-party payment address associated with the parking lot. After the update verification is passed, the third-party payment address associated with the parking lot is updated to the decoding address; optionally, the update verification includes: verifying whether the decoding address and the third-party payment address are consistent. If not, it is determined that the update verification is passed. If so, it is determined that the update verification has failed.

[0038] In the process of updating the third-party payment address of the parking lot, it is possible to verify whether the third-party payment address associated with the parking lot is empty. If so, the decoded address is used as the third-party payment address associated with the parking lot; if not, an update verification is performed based on the decoded address and the third-party payment address associated with the parking lot. After the update verification is passed, the third-party payment address associated with the parking lot is updated to the decoded address. If the update verification fails, no processing is required.

[0039] During the specific implementation process, the parking lot can also be updated according to a preset period. For example, after the server receives the payment identification image, it detects whether the preset period has expired. If so, it decodes the payment identification image to obtain a decoding address, performs payment access verification based on the decoding address, and updates the third-party payment address of the parking lot based on the decoding address after the verification is passed; In addition, when the server detects that the preset period has expired, it can return an identification image collection instruction to the vehicle terminal. The vehicle terminal performs vehicle entry detection based on the vehicle operation data. If a vehicle entry action is detected, the vehicle entry image is collected and image recognition is performed through the SDK to obtain a payment identification image. The payment identification image is uploaded to the server through the SDK. The server decodes the received payment identification image to obtain a decoding address, and performs payment access verification based on the decoding address. After the verification is passed, the third-party payment address of the parking lot is updated based on the decoding address.

[0040] The above-mentioned vehicle terminal and the service end cooperate to update the relevant content of the parking lot according to the payment identification image. The above-mentioned vehicle terminal and the service end can also cooperate to update the relevant content of the parking lot according to the payment identification image. Please refer to the above-mentioned vehicle terminal and the service end can also cooperate to update the specific content of the parking lot according to the payment identification image. This embodiment will not be repeated here.

[0041] Step S204: start the client installed in the vehicle terminal based on the payment address, input the payment address and vehicle identification, and run the virtual container deployed by the client.

[0042] In specific implementation, after receiving the payment address returned by the server, the client installed on the vehicle terminal is started based on the payment address, the payment address and vehicle identification are passed in, and the virtual container deployed by the client is run.

[0043] During the specific execution process, the payment address may include a protocol field for starting the client installed on the vehicle terminal; optionally, the client installed on the vehicle terminal is started based on the protocol field included in the subroutine address.

[0044] Specifically, based on the protocol field contained in the payment address, the client installed on the vehicle terminal is started and the payment address and vehicle identification are passed in, and the virtual container deployed by the client is run; for example, based on the protocol field contained in the subroutine address, the lightweight application installed on the vehicle terminal is started and the subroutine address and vehicle identification are passed in to run the subroutine corresponding to the subroutine address.

[0045] The client in this embodiment includes a third-party application client installed on the vehicle terminal. The client can be an application, an application / program component, or an application / program container. Furthermore, the client can be a lightweight application provided by a third-party application. The virtual container in this embodiment is used to load and run subprograms. The virtual container can be a module in the client for loading and running subprograms, or a subprogram in the client, such as a subprogram corresponding to a payment address in a lightweight application.

[0046] It should be noted that the SDK, server, client and / or virtual container in this embodiment can be provided by the payment service provider or a third-party service provider. By deploying the SDK, client and / or virtual container provided by the payment service provider or the third-party service provider on the vehicle terminal, cooperation with the server provided by the payment service provider or the third-party service provider can be achieved, thereby realizing vehicle parking payment.

[0047] Step S206: Load the payment address through the virtual container and perform payment query processing in cooperation with the server according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

[0048] In specific implementation, based on the above-mentioned process of starting the client based on the payment address, passing the payment address and vehicle identification to the client, and running the virtual container, the payment address is loaded through the virtual container, and based on the loaded payment address, the payment query is processed in cooperation with the server according to the vehicle identification, and the payment is processed according to the pending fees obtained from the payment query.

[0049] Among them, in the process of cooperating with the server to query the payment according to the vehicle identification, the payment query can be made through the interface call, and the payment query can also be made by loading the third-party payment address of the parking lot through the cloud container deployed by the server; Specifically, in the process of querying the payment through the interface call, the query interface of the parking lot is called with the vehicle identification as the input parameter to query the payment, and the fee to be paid returned by the interface call is obtained, that is, the payment query processing includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to query the payment; In the process of querying the payment by loading the third-party payment address of the parking lot through the cloud container deployed on the server, the third-party payment address of the parking lot can be loaded through the cloud container, the vehicle identification is entered on the loaded third-party payment page and the query action is triggered to obtain the payment fee returned by the parking lot; that is, the payment query processing includes: loading the third-party payment address through the cloud container to trigger the third-party payment page and the query action.

[0050] During the specific implementation process, when loading the payment address and cooperating with the server to perform payment query processing based on the vehicle identification, a request can be submitted to the server by loading the payment address, so that the server can perform payment query processing on the parking lot and return the query result; among which, the query result can be the pending payment fee obtained by the payment query processing, or it can be the third-party payment address of the parking lot.

[0051] In an optional implementation provided by this embodiment, the payment address is loaded and payment query processing is performed in cooperation with the server according to the vehicle identification, including: Submit an access request for the payment subroutine to the server by loading the payment address, so that the server can query the parking lot that matches the vehicle ID through the payment query process; or submit a payment query processing request to the server by loading the payment address, so that the server can query the parking lot through the payment query process; The subroutine page is rendered and displayed based on the pending fees returned by the server.

[0052] As described above, the payment query processing includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and / or loading the third-party payment address through the cloud container to trigger the third-party payment page and query action; accordingly, in the process of the server performing payment query processing on the parking lot that matches the vehicle identification, the server can adopt the method of calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and perform payment query processing on the parking lot that matches the vehicle identification. Specifically, in an optional implementation manner provided by this embodiment, the payment query processing on the parking lot that matches the vehicle identification includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and obtaining the fees to be paid returned by the interface call; In addition, during the process of the server performing payment query processing on the parking lot that matches the vehicle identification, the server can also use the method of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action to perform payment query processing on the parking lot that matches the vehicle identification. Specifically, in an optional implementation provided by this embodiment, payment query processing is performed on the parking lot that matches the vehicle identification, including: loading the third-party payment address of the parking lot through the cloud container deployed by the server, entering the vehicle identification on the loaded third-party payment page and triggering the query action, and obtaining the fees to be paid returned by the parking lot.

[0053] In actual applications, considering that the above-mentioned method of using the vehicle identification as an input parameter to call the parking lot's query interface for payment query or the method of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action for payment query, there may be query failures or query delays. In order to improve the success rate of payment query processing and also to reduce the response time of payment query processing, in the case of query failure or query delay, the third-party payment address of the parking lot can be returned to the virtual container, thereby loading the third-party payment address through the virtual container to perform payment query. Specifically, in an optional implementation provided by this embodiment, the payment address is loaded and the payment query processing is performed in cooperation with the server according to the vehicle identification, including: Submit a payment query processing request to the server by loading the payment address; The receiving server returns the third-party payment address after the payment query processing fails, and performs payment query based on the third-party payment address to obtain the fees to be paid.

[0054] Specifically, in order to improve the convenience of payment inquiries for users, in the process of obtaining the fees to be paid by performing payment inquiries based on the third-party payment address, the payment simulation script can be called to simulate the user's operation to perform corresponding operations on the page of the third-party payment address to obtain the fees to be paid. Specifically, the payment inquiry based on the third-party payment address to obtain the fees to be paid can be implemented as follows: load the third-party payment address to obtain the third-party payment page, call the payment simulation script to enter the vehicle identification on the third-party payment page and trigger the payment inquiry to obtain the payment confirmation page containing the fees to be paid.

[0055] In an optional implementation provided by this embodiment, if the payment query processing fails, it is determined in the following way: check whether there is a query interface for the parking lot that matches the vehicle identification; if not, load the third-party payment address of the parking lot through the cloud container deployed by the server to perform payment query. If the query fails or the query is delayed, it is determined that the payment query processing has failed.

[0056] In addition, the payment query processing failure can also be determined when the query result of calling the parking lot's query interface with the vehicle identification as the input parameter for payment query is empty or the query fails, that is: the payment query processing failure is determined based on the failure result of calling the parking lot's query interface with the vehicle identification as the input parameter for payment query; or, the payment query processing failure can also be determined when the query result of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action is empty or the query fails, that is: the payment query processing failure is determined based on the failure result of loading the third-party payment address through the cloud container to trigger the query on the third-party payment page and query action.

[0057] It should be noted that, when the payment address includes the third-party payment address of the parking lot, the server can also send the third-party payment address of the parking lot to the vehicle terminal after receiving the vehicle departure instruction submitted by the vehicle terminal. Accordingly, the vehicle terminal starts the client installed on the vehicle terminal based on the third-party payment address and passes in the third-party payment address and vehicle identification, and runs the virtual container deployed by the client. Thereafter, the virtual container performs payment query and payment processing according to the third-party payment address. Specifically, payment query and payment processing are performed according to the third-party payment address, including: loading the third-party payment address through the virtual container to obtain a third-party payment page, calling the payment simulation script to enter the vehicle identification on the third-party payment page and triggering the payment query, and obtaining a payment confirmation page containing the fees to be paid; and performing payment processing according to the payment instruction submitted through the payment confirmation page.

[0058] In this case, the process of loading the payment address through a virtual container and cooperating with the server to perform payment query processing based on the vehicle identification to process the payment according to the obtained fees to be paid can be replaced by: loading the third-party payment address through a virtual container to obtain a third-party payment page, calling the payment simulation script to enter the vehicle identification on the third-party payment page and triggering the payment query to obtain a payment confirmation page containing the fees to be paid; and processing the payment according to the payment instruction submitted through the payment confirmation page.

[0059] In addition, in actual applications, in order to improve the success rate of payment query processing, the three payment query processing implementation methods provided above can also be combined. Specifically, any two or three of the three payment query processing methods can be combined to form a new implementation method, such as: payment query processing, including: calling the parking lot's query interface with the vehicle identification as the entry parameter to query the payment, if the interface call returns a query failure result, returning the third-party payment address to the virtual container, and the virtual container performs a payment query based on the third-party payment address to obtain the fee to be paid; or, payment query processing, including: calling the parking lot's query interface with the vehicle identification as the entry parameter to query the payment, if the interface call returns a query failure result, through The cloud container loads the third-party payment address, enters the vehicle identification on the loaded third-party payment page, and performs a query action to trigger the payment query to obtain the fees to be paid; or, the third-party payment address is loaded through the cloud container, enters the vehicle identification on the loaded third-party payment page, and performs a query action to trigger the payment query. If the query fails or the query is delayed, the virtual container returns the third-party payment address, and the virtual container performs a payment query based on the third-party payment address to obtain the fees to be paid; or, the payment query processing includes: detecting whether there is a query interface for the parking lot with a matching vehicle identification; if not, loading the third-party payment address of the parking lot through the cloud container deployed on the server to perform a payment query to obtain the fees to be paid.

[0060] It should be noted that, in the process of loading the payment address, the virtual container can load the subroutine by calling the subroutine framework or subroutine engine provided by the client. In this case, loading the payment address through the virtual container can be replaced by loading the payment address in the virtual container, and performing subsequent corresponding processing on this basis; in addition, the virtual container can also be integrated into the client. In this case, starting the client installed on the vehicle terminal based on the payment address and passing in the payment address and vehicle identification, and running the virtual container deployed by the client can be replaced by: starting the client installed on the vehicle terminal based on the payment address and passing in the payment address and vehicle identification; accordingly, subsequently loading the payment address through the virtual container and cooperating with the server to perform payment query processing based on the vehicle identification can be replaced by: loading the payment address through the client and cooperating with the server to perform payment query processing based on the vehicle identification.

[0061] To sum up, the one or more vehicle parking payment methods provided in this embodiment are that the vehicle terminal submits a vehicle departure instruction to the server and receives the payment address returned by the server, starts the client installed on the vehicle terminal based on the payment address and passes in the payment address and vehicle identification, and runs the virtual container deployed by the client, loads the payment address through the virtual container and cooperates with the server to perform payment query processing based on the vehicle identification, so as to perform payment processing based on the obtained fees to be paid. In this way, the fees to be paid are queried through the cooperation of the vehicle terminal and the server, thereby improving the convenience and effectiveness of the query of fees to be paid.

[0062] The above-mentioned steps S202 to S206 provided in this embodiment can be executed by the vehicle terminal. It should be noted that the above-mentioned steps S202 to S206 executed by the vehicle terminal and the steps S502 to S506 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S502 to S506 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S202 to S206 provided in this embodiment.

[0063] The following takes the application of a parking fee payment method provided by this embodiment in the first vehicle payment scenario as an example, combined with Figure 3 , for further explanation of the parking fee payment method provided in this embodiment, see Figure 3 The vehicle parking payment method applied to the first vehicle payment scenario specifically includes the following steps.

[0064] Step S302: Submit a vehicle departure instruction carrying the vehicle identification to the server.

[0065] Step S308: Receive the payment address of the parking lot returned by the server.

[0066] Step S310: start the client installed on the vehicle terminal based on the payment address, input the payment address and vehicle identification, and run the virtual container deployed by the client.

[0067] In step S312, the virtual container submits an access request for the payment subroutine to the server by loading the payment address.

[0068] Step S318: Render and display the subroutine page based on the fees to be paid returned by the server.

[0069] Step S320: Process the payment according to the payment instruction submitted through the subroutine page.

[0070] It should be noted that any one or any combination of steps in step S302, steps S308 to step S312, and steps S318 to step S320 can be combined with any one or any combination of steps in the above steps S202 to step S206 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S302, steps S308 to step S312, and steps S318 to step S320 can be selected and combined with any one or more technical features provided in the above steps S202 to step S206 to form a new implementation method; or, any one or any combination of technical features in steps S302, steps S308 to step S312, and steps S318 to step S320 can be replaced with any one or more technical features provided in the above steps S202 to step S206 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0071] In addition, it should be noted that the above-mentioned steps S302, steps S308 to S312 and steps S318 to S320 provided in this embodiment can be executed by the vehicle terminal. It should be noted that the above-mentioned steps S302, steps S308 to S312 and steps S318 to S320 executed by the vehicle terminal and steps S304 to S306 and steps S314 to S316 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S304 to S306 and steps S314 to S316 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S302, steps S308 to S312 and steps S318 to S320 provided in this embodiment.

[0072] The following is an example of the application of a parking fee payment method provided by this embodiment in a second vehicle payment scenario. Figure 4 , for further explanation of the parking fee payment method provided in this embodiment, see Figure 4 The vehicle parking payment method applied to the second vehicle payment scenario specifically includes the following steps.

[0073] Step S402: Submit a vehicle departure instruction carrying the vehicle identification to the server.

[0074] Step S408: Receive the payment address of the parking lot returned by the server.

[0075] Step S410: start the client installed on the vehicle terminal based on the payment address, input the payment address and vehicle identification, and run the virtual container deployed by the client.

[0076] In step S412, the virtual container submits a payment query processing request to the server by loading the payment address.

[0077] Step S420: load the third-party payment address through the virtual container to obtain the third-party payment page, call the payment simulation script to input the vehicle identification and trigger the payment query, and obtain the payment confirmation page containing the fees to be paid.

[0078] Step S422: Process the payment according to the payment instruction submitted through the payment confirmation page.

[0079] It should be noted that any one of steps S402, steps S408 to S412, and steps S420 to S422, or any combination of multiple steps, can be combined with any one of steps S202 to S206 or any combination of multiple steps to form a new implementation method according to the needs of implementation deployment; in addition, any one or multiple technical features can be selected from steps S402, steps S408 to S412, and steps S420 to S422 according to the needs of actual deployment, and combined with any one or multiple technical features provided by steps S202 to S206 to form a new implementation method; or, any one or multiple technical features in steps S402, steps S408 to S412, and steps S420 to S422 can be replaced with any one or multiple technical features provided by steps S202 to S206 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0080] In addition, it should be noted that the above-mentioned steps S402, steps S408 to S412 and steps S420 to S422 provided in this embodiment can be executed by the vehicle terminal. It should be noted that the above-mentioned steps S402, steps S408 to S412 and steps S420 to S422 executed by the vehicle terminal and steps S404 to S406 and steps S414 to S418 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S404 to S406 and steps S414 to S418 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S402, steps S408 to S412 and steps S420 to S422 provided in this embodiment.

[0081] One or more embodiments of a vehicle parking fee payment method provided in this specification are as follows: Reference Figure 5The vehicle parking payment method provided in this embodiment can be applied to the server, and the method specifically includes steps S502 to S506.

[0082] Step S502: A parking space is searched based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain a parking space.

[0083] In the parking scenario, after a vehicle enters a parking lot for parking and starts to leave, the vehicle terminal can submit a vehicle departure instruction to the server after the vehicle starts, and initiate parking payment for the vehicle by submitting the vehicle departure instruction to the server. The server receives the vehicle departure instruction and can query the parking lot based on the vehicle departure instruction. After querying the parking lot where the current vehicle is parked, it generates and returns the payment address for the current vehicle to pay for leaving the parking lot.

[0084] During the specific execution process, the vehicle departure instruction may be generated after the vehicle departure detection is performed on the vehicle terminal. If the vehicle departure behavior is detected by the vehicle terminal, the vehicle departure instruction is generated and submitted to the server. The vehicle departure instruction may include a vehicle identification, which may be stored by the vehicle terminal or obtained by calling an interface by the vehicle terminal; Specifically, vehicle departure detection can be performed based on vehicle operation data, and a vehicle departure instruction can be submitted to the server after the vehicle departure action is detected; in the process of performing vehicle departure detection based on vehicle operation data, if the vehicle operation data meets the vehicle departure conditions, it is determined that the vehicle departure action is detected; for example, after receiving the vehicle start instruction, it is detected whether the vehicle stop time is less than a preset threshold, and if so, it is determined that the vehicle departure action is detected; for another example, if it is detected that the vehicle operation image contains departure behavior, it is determined that the vehicle departure behavior is detected.

[0085] In addition, vehicle departure detection can be performed based on the device interaction results with third-party devices, and a vehicle departure instruction can be submitted to the server after the vehicle departure action is detected; in the process of performing vehicle departure detection based on the device interaction results with third-party devices, if data communication is detected with the departure device installed in the exit area of ​​the parking lot, a vehicle departure instruction is submitted to the server.

[0086] The above specifically describes the process of detecting vehicle departures on the vehicle terminal and, upon detecting a vehicle departure, generating a vehicle departure instruction and submitting it to the server. Alternatively, the vehicle terminal can use the SDK to detect vehicle departures, generate a vehicle departure instruction upon detecting a vehicle departure, and submit it to the server. For example, the vehicle terminal may generate a vehicle departure instruction upon detecting that the vehicle has been idle for less than a preset threshold by invoking an SDK interface. In this embodiment, in addition to generating a vehicle departure instruction upon detecting a vehicle departure, a vehicle start instruction may also be used as the vehicle departure instruction; that is, upon detecting a vehicle start instruction, a vehicle departure instruction is submitted to the server.

[0087] The server includes a server that cooperates with the vehicle terminal to perform parking lot query and payment query processing for vehicle parking payment; the server can be a payment server, or it can be a module in the payment server for parking lot query and payment query processing, which is not limited in this embodiment.

[0088] During the specific implementation process, the SDK can be deployed on the vehicle terminal. When the SDK is deployed on the vehicle terminal, the vehicle terminal can send a vehicle departure instruction to the server through the deployed SDK to query the parking space; among them, the SDK and the server can be provided by the same service provider. For example, the vehicle terminal deploys the SDK provided by the payment service provider. If the vehicle terminal detects a vehicle start-up instruction, it sends a vehicle departure instruction to the server provided by the payment service provider through the SDK.

[0089] In specific implementation, after the vehicle terminal submits a vehicle departure instruction to the server, the server queries the parking space based on the vehicle departure instruction. Specifically, the parking space can be queried in the parking entry record based on the vehicle identification carried in the vehicle departure instruction. The parking space can also be obtained by matching the vehicle position uploaded by the vehicle terminal with the location information of the candidate parking space. The two can also be combined to obtain the parking space. In an optional implementation provided by this embodiment, the parking space query is performed in the following manner: The query result is obtained by querying the parking entry record according to the vehicle identification carried by the vehicle departure instruction; If the target entry record corresponding to the vehicle identification is found, the parking space is determined according to the target entry record; If the target entry record corresponding to the vehicle identification is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking place to obtain the parking place.

[0090] Specifically, if a target entry record corresponding to the vehicle identifier carried in the vehicle departure instruction is found, the parking place can be determined based on the target entry record. The parking place identifier carried in the target entry record can be used to determine the parking place; wherein the parking place identifier may include an identifier representing the uniqueness of the parking place, such as the parking place name or parking place number; In addition, if the target entry record corresponding to the vehicle identification carried by the vehicle departure instruction is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking places to obtain the parking place; optionally, the candidate parking place includes at least one parking place registered on the server side; wherein, the vehicle departure instruction may carry the vehicle position, or, if the target entry record corresponding to the vehicle identification is not found, a vehicle position collection reminder may be returned to the vehicle terminal, and the receiving vehicle terminal collects and uploads the vehicle position based on the vehicle position collection reminder. This embodiment does not limit this.

[0091] Step S504: Generate the payment address of the parking lot and return it to the vehicle terminal.

[0092] During specific implementation, the server queries the parking lot based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain the parking lot. After querying the parking lot where the current vehicle is parked, it generates and returns the payment address for the current vehicle to pay for leaving the parking lot. Specifically, in the process of generating the payment address, the payment address can be generated based on the subroutine address of the payment subroutine generated by the server. In this case, the payment address may include the subroutine address of the payment subroutine generated by the server. In addition, the payment address can also be generated based on the third-party payment address of the parking lot. In this case, the payment address may include the third-party payment address of the parking lot that matches the vehicle identification. Among them, the third-party payment address of the parking lot refers to the access address of the payment program or payment subroutine provided by the parking service provider or parking service system of the parking lot itself; that is, the third-party payment address includes the access address of the payment program or payment subroutine corresponding to the parking lot that matches the vehicle identification. It should be noted that the relevant content of the parking space in the technical solution of this application is actually the interactive processing process with the parking service provider or parking service system. Therefore, the parking space in the technical solution of this application can be replaced by a parking service provider or parking service system.

[0093] Corresponding to the above-mentioned vehicle terminal sending a vehicle departure instruction to the server through the deployed SDK to query the vehicle location, when the vehicle terminal deploys the SDK, the vehicle terminal can also receive the payment address returned by the server through the SDK; it should be noted that when the vehicle terminal deploys the SDK, the data interaction between the vehicle terminal and the server can be carried out through the SDK, for example, the vehicle terminal receives the vehicle location collection reminder returned by the server through the SDK, collects the vehicle location according to the vehicle location collection reminder and uploads it to the server through the SDK, or the vehicle terminal receives the vehicle location collection reminder returned by the server through the SDK, calls the interface provided by the SDK to collect the vehicle location and upload it to the server; this embodiment will not be repeated here.

[0094] The parking entry record in this embodiment can be synchronized to the server by the parking service system. Specifically, when the parking lot entry equipment detects that a vehicle has entered the lot, it uploads the parking entry record to the parking service system, and the parking service system receives and synchronizes the parking entry record to the server. Optionally, the parking entry record carries at least one of the following: vehicle identification, parking lot identification, entry time, and entry location.

[0095] In addition, the parking entry record can also be generated based on the payment identification image collected and uploaded by the vehicle terminal after detecting the vehicle entering the parking lot. The payment identification image in this embodiment can be collected by calling at least one collection component deployed on the vehicle. In this embodiment, the parking entry record can be generated based on the payment identification image collected after detecting the vehicle entering the parking lot. In this way, the parking entry record is generated based on the vehicle entering the parking lot and the payment identification image collected by the vehicle terminal, improving the comprehensiveness of the generated parking entry record. In an optional implementation provided by this embodiment, the vehicle terminal obtains the payment identification image by performing the following operations: Carry out vehicle approach detection based on vehicle operation data collected by the vehicle terminal; If a vehicle entering the site is detected, an image of the vehicle entering the site is collected and image recognition is performed to obtain a payment identification image.

[0096] Optionally, the vehicle operation data includes vehicle behavior data generated during vehicle operation, collected vehicle operation images and / or device interaction results with third-party devices; vehicle approach detection includes device peer detection and / or device connection detection of third-party devices; vehicle approach images include images of the outside of the vehicle collected when the vehicle approach action occurs; payment identification images include images carrying payment identification, such as images carrying QR codes.

[0097] Specifically, vehicle approach detection can be performed based on vehicle operation data, and a vehicle approach image can be collected after the vehicle approach action is detected; in the process of performing vehicle approach detection based on vehicle operation data, if the vehicle operation image contains an approach action, the vehicle approach image is collected; for example, vehicle approach detection is performed based on the vehicle operation image collected by the vehicle terminal, and if a vehicle operation image containing an approach barrier lifting action is detected in the vehicle operation image, it is determined that the vehicle approach action is detected; In addition, vehicle approach detection can be performed based on the device interaction results with third-party devices, and vehicle approach images can be collected after the vehicle approach action is detected; in the process of performing vehicle approach detection based on the device interaction results with third-party devices, if data communication is detected with the approach device installed in the entrance area of ​​the parking lot, the vehicle approach image can be collected.

[0098] It should be noted that when the vehicle terminal is configured with SDK, if the vehicle terminal detects the vehicle entering the site, it can collect the vehicle entry image through SDK and perform image recognition to obtain the payment identification image, or the vehicle terminal can collect the vehicle entry image and perform image recognition through SDK to obtain the payment identification image, that is, if the vehicle entry action is detected, the vehicle entry image is collected and the payment identification image is obtained through SDK for image recognition; in addition, the vehicle terminal can perform vehicle entry detection, vehicle entry image collection and image recognition through SDK; for example, the vehicle terminal calls the interface provided by SDK to detect that the vehicle operation image contains the entry behavior, and then collects the vehicle entry image and performs image recognition to obtain the payment identification image.

[0099] Furthermore, based on the obtained payment identification image, the payment identification image is uploaded to the server. Specifically, the payment identification image can be uploaded to the server through the SDK; after receiving the payment identification image, the server can generate a parking entry record based on the payment identification image; that is, the vehicle terminal uploads the payment identification image to the server to generate a parking entry record; correspondingly, in an optional implementation manner provided by this embodiment, in the process of generating a parking entry record: first, the payment identification image is decoded to obtain a decoding address, and then the payment access verification is performed according to the decoding address, and after the verification is passed, the parking entry record is generated according to the decoding address, vehicle identification, entry time and / or entry location.

[0100] During the specific execution process, after the server receives the payment identification image, it first decodes the payment identification image to obtain the decoding address, and then performs payment access verification based on the decoding address, and generates a parking entry record after the verification is passed; optionally, during the payment access verification process, it is verified whether there is an access anomaly in the decoding address. If not, it is determined that the verification is passed. If so, it is determined that the verification is failed; or, it is verified whether the decoding address is the payment address of the parking lot, that is, whether the decoding address is associated with the parking lot. If so, it is determined that the verification is passed. If not, it is determined that the verification is failed; or, it is verified whether the decoding address is within the preset validity period. If so, it is determined that the verification is passed. If not, it is determined that the verification is failed.

[0101] Furthermore, the above payment access verification process can be combined, for example: Verify whether there is any access anomaly to the decoding address; if so, determine that the verification has failed; If not, verify whether the decoded address is associated with the parking place; if not, determine that the verification has failed; If so, verify whether the decoded address is within the preset validity period; if so, determine that the verification is passed; if not, determine that the verification is failed.

[0102] It should be noted that the vehicle identification, entry time and / or entry location required to generate the parking entry record can be uploaded by the vehicle terminal or through the SDK. It can be uploaded when uploading the payment identification image, or it can be uploaded based on the information returned by the server after the above-mentioned payment access verification is passed. This embodiment does not limit this.

[0103] In this embodiment, in addition to the vehicle terminal and the server cooperating to generate parking entry records based on the payment identification image, the vehicle terminal and the server can also cooperate to update the parking lot based on the payment identification image; optionally, the vehicle terminal performs vehicle entry detection based on the vehicle operation data collected by the vehicle terminal. If a vehicle entry action is detected, the vehicle entry image is collected and image recognition is performed through the SDK to obtain the payment identification image, and the payment identification image is uploaded to the server through the SDK to update the parking lot; correspondingly, the server decodes the payment identification image to obtain a decoding address, performs payment access verification based on the decoding address, and updates the third-party payment address of the parking lot based on the decoding address after the verification is passed.

[0104] In the process of updating the third-party payment address of the parking lot, the update verification can be performed based on the decoding address and the third-party payment address associated with the parking lot. After the update verification is passed, the third-party payment address associated with the parking lot is updated to the decoding address; optionally, the update verification includes: verifying whether the decoding address and the third-party payment address are consistent. If not, it is determined that the update verification is passed. If so, it is determined that the update verification has failed.

[0105] In the process of updating the third-party payment address of the parking lot, it is possible to verify whether the third-party payment address associated with the parking lot is empty. If so, the decoded address is used as the third-party payment address associated with the parking lot; if not, an update verification is performed based on the decoded address and the third-party payment address associated with the parking lot. After the update verification is passed, the third-party payment address associated with the parking lot is updated to the decoded address. If the update verification fails, no processing is required.

[0106] During the specific implementation process, the parking lot can also be updated according to a preset period. For example, after the server receives the payment identification image, it detects whether the preset period has expired. If so, it decodes the payment identification image to obtain a decoding address, performs payment access verification based on the decoding address, and updates the third-party payment address of the parking lot based on the decoding address after the verification is passed; In addition, when the server detects that the preset period has expired, it can return an identification image collection instruction to the vehicle terminal. The vehicle terminal performs vehicle entry detection based on the vehicle operation data. If a vehicle entry action is detected, the vehicle entry image is collected and image recognition is performed through the SDK to obtain a payment identification image. The payment identification image is uploaded to the server through the SDK. The server decodes the received payment identification image to obtain a decoding address, and performs payment access verification based on the decoding address. After the verification is passed, the third-party payment address of the parking lot is updated based on the decoding address.

[0107] The above-mentioned vehicle terminal and the service end cooperate to update the relevant content of the parking lot according to the payment identification image. The above-mentioned vehicle terminal and the service end can also cooperate to update the relevant content of the parking lot according to the payment identification image. Please refer to the above-mentioned vehicle terminal and the service end can also cooperate to update the specific content of the parking lot according to the payment identification image. This embodiment will not be repeated here.

[0108] In specific implementation, after the vehicle terminal receives the payment address returned by the server, it starts the client installed on the vehicle terminal based on the payment address, passes in the payment address and vehicle identification, and runs the virtual container deployed by the client.

[0109] During the specific execution process, the payment address may include a protocol field for starting the client installed on the vehicle terminal; optionally, the client installed on the vehicle terminal is started based on the protocol field included in the subroutine address.

[0110] Specifically, the vehicle terminal starts the client installed on the vehicle terminal based on the protocol field contained in the payment address and passes in the payment address and vehicle identification, and runs the virtual container deployed by the client; for example, based on the protocol field contained in the subroutine address, the lightweight application installed on the vehicle terminal is started and the subroutine address and vehicle identification are passed in to run the subroutine corresponding to the subroutine address.

[0111] The client in this embodiment includes a third-party application client installed on the vehicle terminal. The client can be an application, an application / program component, or an application / program container. Furthermore, the client can be a lightweight application provided by a third-party application. The virtual container in this embodiment is used to load and run subprograms. The virtual container can be a module in the client for loading and running subprograms, or a subprogram in the client, such as a subprogram corresponding to a payment address in a lightweight application.

[0112] It should be noted that the SDK, server, client and / or virtual container in this embodiment can be provided by the payment service provider or a third-party service provider. By deploying the SDK, client and / or virtual container provided by the payment service provider or the third-party service provider on the vehicle terminal, cooperation with the server provided by the payment service provider or the third-party service provider can be achieved, thereby realizing vehicle parking payment.

[0113] Step S506 , the virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot, and returns the obtained fee to be paid to the virtual container for payment processing.

[0114] During specific implementation, after the payment address of the parking lot is generated and returned to the vehicle terminal, the vehicle terminal starts the client installed on the vehicle terminal based on the payment address and passes in the payment address and vehicle identification, and runs the virtual container deployed by the client. The vehicle terminal loads the payment address through the virtual container and cooperates with the server to perform payment query processing based on the vehicle identification, so as to process the payment according to the fees to be paid; correspondingly, the server cooperates with the virtual container deployed by the client installed on the vehicle terminal to perform payment query processing on the parking lot, and returns the obtained fees to be paid to the virtual container for payment processing.

[0115] Among them, in the process of making payment inquiries to the parking lot, payment inquiries can be made through interface calls, and payment inquiries can also be made by loading the third-party payment address of the parking lot through the deployed cloud container; Specifically, in the process of querying the payment through the interface call, the query interface of the parking lot is called with the vehicle identification as the input parameter to query the payment, and the fee to be paid returned by the interface call is obtained, that is, the payment query processing includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to query the payment; In the process of performing payment query by loading the third-party payment address of the parking lot through the deployed cloud container, the third-party payment address of the parking lot can be loaded through the cloud container, and the vehicle identification is entered on the loaded third-party payment page and the query action is triggered to obtain the pending payment fee returned by the parking lot; that is, the payment query processing includes: loading the third-party payment address through the cloud container to trigger the third-party payment page and the query action.

[0116] During the specific implementation process, when loading the payment address and cooperating with the server to perform payment query processing based on the vehicle identification, a request can be submitted to the server by loading the payment address, so that the server can perform payment query processing on the parking lot and return the query result; among which, the query result can be the pending payment fee obtained by the payment query processing, or it can be the third-party payment address of the parking lot.

[0117] In an optional implementation provided by this embodiment, the payment address is loaded and payment query processing is performed in cooperation with the server according to the vehicle identification, including: Submit an access request for the payment subroutine to the server by loading the payment address, so that the server can query the parking lot that matches the vehicle ID through the payment query process; or submit a payment query processing request to the server by loading the payment address, so that the server can query the parking lot through the payment query process; The subroutine page is rendered and displayed based on the pending fees returned by the server.

[0118] As described above, the payment query processing includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and / or loading the third-party payment address through the cloud container to trigger the third-party payment page and query action; accordingly, in the process of the server performing payment query processing on the parking lot that matches the vehicle identification, the server can adopt the method of calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and perform payment query processing on the parking lot that matches the vehicle identification. Specifically, in an optional implementation manner provided by this embodiment, the payment query processing on the parking lot that matches the vehicle identification includes: calling the query interface of the parking lot with the vehicle identification as the input parameter to perform payment query, and obtaining the fees to be paid returned by the interface call; In addition, during the process of the server performing payment query processing on the parking lot that matches the vehicle identification, the server can also use the method of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action to perform payment query processing on the parking lot that matches the vehicle identification. Specifically, in an optional implementation provided by this embodiment, payment query processing is performed on the parking lot that matches the vehicle identification, including: loading the third-party payment address of the parking lot through the cloud container deployed by the server, entering the vehicle identification on the loaded third-party payment page and triggering the query action, and obtaining the fees to be paid returned by the parking lot.

[0119] In actual applications, considering that the above-mentioned method of using the vehicle identification as an input parameter to call the parking lot's query interface for payment query or the method of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action for payment query, there may be query failures or query delays. In order to improve the success rate of payment query processing and also to reduce the response time of payment query processing, in the case of query failure or query delay, the third-party payment address of the parking lot can be returned to the virtual container, thereby loading the third-party payment address through the virtual container to perform payment query. Specifically, in an optional implementation provided by this embodiment, the payment address is loaded and the payment query processing is performed in cooperation with the server according to the vehicle identification, including: Submit a payment query processing request to the server by loading the payment address; The receiving server returns the third-party payment address after the payment query processing fails, and performs payment query based on the third-party payment address to obtain the fees to be paid.

[0120] Specifically, in order to improve the convenience of payment inquiries for users, in the process of obtaining the fees to be paid by performing payment inquiries based on the third-party payment address, the payment simulation script can be called to simulate the user's operation to perform corresponding operations on the page of the third-party payment address to obtain the fees to be paid. Specifically, the payment inquiry based on the third-party payment address to obtain the fees to be paid can be implemented as follows: load the third-party payment address to obtain the third-party payment page, call the payment simulation script to enter the vehicle identification on the third-party payment page and trigger the payment inquiry to obtain the payment confirmation page containing the fees to be paid.

[0121] In an optional implementation provided by this embodiment, if the payment query processing fails, it is determined in the following way: check whether there is a query interface for the parking lot that matches the vehicle identification; if not, load the third-party payment address of the parking lot through the cloud container deployed by the server to perform payment query. If the query fails or the query is delayed, it is determined that the payment query processing has failed.

[0122] In addition, the payment query processing failure can also be determined when the query result of calling the parking lot's query interface with the vehicle identification as the input parameter for payment query is empty or the query fails, that is: the payment query processing failure is determined based on the failure result of calling the parking lot's query interface with the vehicle identification as the input parameter for payment query; or, the payment query processing failure can also be determined when the query result of loading the third-party payment address through the cloud container to trigger the third-party payment page and query action is empty or the query fails, that is: the payment query processing failure is determined based on the failure result of loading the third-party payment address through the cloud container to trigger the query on the third-party payment page and query action.

[0123] It should be noted that, when the payment address includes the third-party payment address of the parking lot, the server can also send the third-party payment address of the parking lot to the vehicle terminal after receiving the vehicle departure instruction submitted by the vehicle terminal. Accordingly, the vehicle terminal starts the client installed on the vehicle terminal based on the third-party payment address and passes in the third-party payment address and vehicle identification, and runs the virtual container deployed by the client. Thereafter, the virtual container performs payment query and payment processing according to the third-party payment address. Specifically, payment query and payment processing are performed according to the third-party payment address, including: loading the third-party payment address through the virtual container to obtain a third-party payment page, calling the payment simulation script to enter the vehicle identification on the third-party payment page and triggering the payment query, and obtaining a payment confirmation page containing the fees to be paid; and performing payment processing according to the payment instruction submitted through the payment confirmation page.

[0124] In this case, the process of loading the payment address through a virtual container and cooperating with the server to perform payment query processing based on the vehicle identification to process the payment according to the obtained fees to be paid can be replaced by: loading the third-party payment address through a virtual container to obtain a third-party payment page, calling the payment simulation script to enter the vehicle identification on the third-party payment page and triggering the payment query to obtain a payment confirmation page containing the fees to be paid; and processing the payment according to the payment instruction submitted through the payment confirmation page.

[0125] In addition, in actual applications, in order to improve the success rate of payment query processing, the three payment query processing implementation methods provided above can also be combined. Specifically, any two or three of the three payment query processing methods can be combined to form a new implementation method, such as: payment query processing, including: calling the parking lot's query interface with the vehicle identification as the entry parameter to query the payment, if the interface call returns a query failure result, returning the third-party payment address to the virtual container, and the virtual container performs a payment query based on the third-party payment address to obtain the fee to be paid; or, payment query processing, including: calling the parking lot's query interface with the vehicle identification as the entry parameter to query the payment, if the interface call returns a query failure result, through The cloud container loads the third-party payment address, enters the vehicle identification on the loaded third-party payment page, and performs a query action to trigger the payment query to obtain the fees to be paid; or, the third-party payment address is loaded through the cloud container, enters the vehicle identification on the loaded third-party payment page, and performs a query action to trigger the payment query. If the query fails or the query is delayed, the virtual container returns the third-party payment address, and the virtual container performs a payment query based on the third-party payment address to obtain the fees to be paid; or, the payment query processing includes: detecting whether there is a query interface for the parking lot with a matching vehicle identification; if not, loading the third-party payment address of the parking lot through the cloud container deployed on the server to perform a payment query to obtain the fees to be paid.

[0126] It should be noted that, in the process of loading the payment address, the virtual container can load the subroutine by calling the subroutine framework or subroutine engine provided by the client. In this case, loading the payment address through the virtual container can be replaced by loading the payment address in the virtual container, and performing subsequent corresponding processing on this basis; in addition, the virtual container can also be integrated into the client. In this case, starting the client installed on the vehicle terminal based on the payment address and passing in the payment address and vehicle identification, and running the virtual container deployed by the client can be replaced by: starting the client installed on the vehicle terminal based on the payment address and passing in the payment address and vehicle identification; accordingly, subsequently loading the payment address through the virtual container and cooperating with the server to perform payment query processing based on the vehicle identification can be replaced by: loading the payment address through the client and cooperating with the server to perform payment query processing based on the vehicle identification.

[0127] The following takes the application of a parking fee payment method provided by this embodiment in the first vehicle payment scenario as an example, combined with Figure 3 , for further explanation of the parking fee payment method provided in this embodiment, see Figure 3 The vehicle parking payment method applied to the first vehicle payment scenario specifically includes the following steps.

[0128] Step S304: Query the parking space according to the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain the parking space.

[0129] Step S306: Generate the payment address of the parking lot and return it to the vehicle terminal.

[0130] Step S314: receiving an access request for the payment subroutine submitted by the virtual container.

[0131] Step S316: The parking lot query interface is called with the vehicle identification as an input parameter to query the payment fee, and the fee to be paid returned by the interface call is obtained and returned to the virtual container.

[0132] The following is an example of the application of a parking fee payment method provided by this embodiment in a second vehicle payment scenario. Figure 4 , for further explanation of the parking fee payment method provided in this embodiment, see Figure 4 The vehicle parking payment method applied to the second vehicle payment scenario specifically includes the following steps.

[0133] Step S404: Query the parking space according to the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain the parking space.

[0134] Step S406: Generate the payment address of the parking lot and return it to the vehicle terminal.

[0135] Step S414: receiving a payment query processing request submitted by the virtual container.

[0136] In step S416, if the query interface of the parking lot is not detected, the payment query is performed by loading the third-party payment address of the parking lot through the cloud container.

[0137] Step S418: If the query fails, the third-party payment address of the parking lot is returned to the virtual container.

[0138] An embodiment of a vehicle parking fee payment device provided in this specification is as follows: In the above embodiment, a vehicle parking fee payment method is provided, and correspondingly, a vehicle parking fee payment device is also provided, which is described below with reference to the accompanying drawings.

[0139] Reference Figure 6 , which shows a schematic diagram of an embodiment of a vehicle parking payment device provided in this embodiment.

[0140] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0141] This embodiment provides a vehicle parking fee payment device that can be operated on a vehicle terminal. The device includes: The departure instruction submission module 602 is configured to submit the vehicle departure instruction to the server and receive the payment address returned by the server; The virtual container running module 604 is configured to start the client installed on the vehicle terminal based on the payment address, input the payment address and vehicle identification, and run the virtual container deployed by the client; The payment query module 606 is configured to load the payment address through the virtual container and cooperate with the server to perform payment query processing according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

[0142] Another embodiment of a vehicle parking fee payment device provided in this specification is as follows: In the above embodiment, another method for paying for parking fees is provided. Correspondingly, another device for paying for parking fees is also provided, which will be described below with reference to the accompanying drawings.

[0143] Reference Figure 7 , which shows a schematic diagram of another embodiment of a vehicle parking payment device provided in this embodiment.

[0144] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0145] This embodiment provides a vehicle parking fee payment device that can be run on a server. The device includes: The parking space query module 702 is configured to query a parking space based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain a parking space; The payment address generation module 704 is configured to generate the payment address of the parking lot and return it to the vehicle terminal; The payment inquiry processing module 706 is configured to cooperate with the virtual container deployed by the client installed in the vehicle terminal to perform payment inquiry processing on the parking lot, and return the obtained payment to be paid to the virtual container for payment processing.

[0146] An embodiment of a vehicle parking fee payment device provided in this specification is as follows: Corresponding to the above-described method for paying for parking fees, based on the same technical concept, one or more embodiments of this specification further provide a vehicle parking fee payment device, which is used to execute the above-described method for paying for parking fees. Figure 8A schematic diagram of the structure of a vehicle parking fee payment provided in one or more embodiments of this specification.

[0147] This embodiment provides a vehicle parking fee payment device, including: like Figure 8 As shown, the vehicle parking payment device can vary significantly depending on its configuration or performance. It may include one or more processors 801 and memory 802. Memory 802 may store one or more applications or data. Memory 802 may be either ephemeral or persistent. The applications stored in memory 802 may include one or more modules (not shown), each of which may comprise a series of computer-executable instructions within the vehicle parking payment device. Furthermore, processor 801 may be configured to communicate with memory 802 to execute the series of computer-executable instructions within memory 802 on the vehicle parking payment device. The vehicle parking payment device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, and the like.

[0148] In a specific embodiment, a vehicle parking payment device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the vehicle parking payment device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: Submit the vehicle departure instruction to the server and receive the payment address returned by the server; Based on the payment address, the client installed on the vehicle terminal is started, the payment address and vehicle identification are input, and the virtual container deployed by the client is run; The payment address is loaded through the virtual container and payment query processing is performed in cooperation with the service end according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

[0149] Another embodiment of a vehicle parking fee payment device provided in this specification is as follows: Corresponding to the other vehicle parking fee payment method described above, based on the same technical concept, one or more embodiments of this specification also provide another vehicle parking fee payment device, which is used to execute the other vehicle parking fee payment method provided above. Figure 9 A schematic structural diagram of another vehicle parking payment device provided in one or more embodiments of this specification.

[0150] This embodiment provides a vehicle parking fee payment device, including: like Figure 9 As shown, the vehicle parking payment device can vary significantly depending on its configuration or performance. It may include one or more processors 901 and memory 902. Memory 902 may store one or more applications or data. Memory 902 may be either ephemeral or persistent. The applications stored in memory 902 may include one or more modules (not shown), each of which may comprise a series of computer-executable instructions within the vehicle parking payment device. Furthermore, processor 901 may be configured to communicate with memory 902 to execute the series of computer-executable instructions within memory 902 on the vehicle parking payment device. The vehicle parking payment device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, and the like.

[0151] In a specific embodiment, a vehicle parking payment device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the vehicle parking payment device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: The parking lot is searched and obtained based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal; Generate the payment address of the parking lot and return it to the vehicle terminal; The virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot and returns the obtained fee to be paid to the virtual container for payment processing.

[0152] An embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the above-described vehicle parking payment method, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0153] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented: Submit the vehicle departure instruction to the server and receive the payment address returned by the server; Based on the payment address, the client installed on the vehicle terminal is started, the payment address and vehicle identification are input, and the virtual container deployed by the client is run; The payment address is loaded through the virtual container and payment query processing is performed in cooperation with the service end according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

[0154] It should be noted that the embodiment of a computer-readable storage medium in this specification and the embodiment of a vehicle parking payment method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0155] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the other vehicle parking payment method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0156] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented: The parking lot is searched and obtained based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal; Generate the payment address of the parking lot and return it to the vehicle terminal; The virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot and returns the obtained fee to be paid to the virtual container for payment processing.

[0157] It should be noted that the embodiment of another computer-readable storage medium in this specification and the embodiment of another vehicle parking payment method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0158] An embodiment of a computer program product provided in this specification is as follows: Corresponding to the above-described method for paying for parking fees, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0159] A computer program product comprising a computer program / instructions, which, when executed by a processor, implements the following steps: Submit the vehicle departure instruction to the server and receive the payment address returned by the server; Based on the payment address, the client installed on the vehicle terminal is started, the payment address and vehicle identification are input, and the virtual container deployed by the client is run; The payment address is loaded through the virtual container and payment query processing is performed in cooperation with the service end according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

[0160] It should be noted that the embodiment of a computer program product in this specification and the embodiment of a vehicle parking payment method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0161] Another computer program product embodiment provided in this specification is as follows: Corresponding to the other vehicle parking payment method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0162] A computer program product comprising a computer program / instructions, which, when executed by a processor, implements the following steps: The parking lot is searched and obtained based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal; Generate the payment address of the parking lot and return it to the vehicle terminal; The virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot and returns the obtained fee to be paid to the virtual container for payment processing.

[0163] It should be noted that the embodiment of another computer program product in this specification and the embodiment of another vehicle parking payment method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0164] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For example, the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments are similar to the method embodiments, so the description is relatively simple. For relevant content in the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, please refer to the partial description of the method embodiments.

[0165] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0166] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using physical hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly performed using software called a "logic compiler." This is similar to the software compilers used during program development. Before compilation, the original code must be written in a specific programming language, called a Hardware Description Language (HDL). There are many different HDLs, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also appreciate that simply programming a method flow in one of these hardware description languages ​​and then programming it into an integrated circuit can easily create a hardware circuit that implements the logic method flow.

[0167] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the memory control logic. Those skilled in the art will also appreciate that, in addition to implementing the controller purely in computer-readable program code, the controller can also be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing the various functions included therein can also be considered as structures within the hardware component. Alternatively, the means for implementing the various functions can be considered both a software module implementing the method and a structure within the hardware component.

[0168] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0169] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0170] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0171] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0172] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0173] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0174] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0175] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0176] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0177] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising at least one ..." does not exclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the element.

[0178] One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0179] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A vehicle parking fee payment method, applied to a vehicle terminal, comprising: Submit the vehicle departure instruction to the server and receive the payment address returned by the server; Based on the payment address, the client installed on the vehicle terminal is started, the payment address and vehicle identification are input, and the virtual container deployed by the client is run; The payment address is loaded through the virtual container and payment query processing is performed in cooperation with the service end according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

2. According to the vehicle parking payment method according to claim 1, the payment address includes a subroutine address of a payment subroutine generated by the server, and the client is started based on the protocol field contained in the subroutine address.

3. The parking fee payment method according to claim 2, wherein the step of loading the payment address and cooperating with the server to perform payment query processing based on the vehicle identification comprises: Submitting an access request of the payment subroutine to the server by loading the payment address, so as to perform payment query processing on the parking lot matching the vehicle identification through the server; The subroutine page is rendered and displayed according to the pending payment returned by the server.

4. The parking fee payment method according to claim 3, wherein the step of querying the parking lot that matches the vehicle identification comprises: The query interface of the parking lot is called with the vehicle identification as an input parameter to perform payment query, and the to-be-paid fee returned by the interface call is obtained.

5. The vehicle parking fee payment method according to claim 3, wherein the step of performing a payment query on the parking lot that matches the vehicle identification comprises: The third-party payment address of the parking lot is loaded through the cloud container deployed by the server, the vehicle identification is input on the loaded third-party payment page and a query action is triggered to obtain the to-be-paid fee returned by the parking lot.

6. The vehicle parking fee payment method according to claim 1, wherein the step of loading the payment address and cooperating with the server to perform payment query processing based on the vehicle identification comprises: Submit a payment query processing request to the server by loading the payment address; Receive the third-party payment address of the parking lot returned by the server after the payment query processing fails, and perform payment query based on the third-party payment address to obtain the fee to be paid.

7. The vehicle parking fee payment method according to claim 6, wherein the step of performing a payment query based on the third-party payment address to obtain the fee to be paid comprises: The third-party payment address is loaded to obtain a third-party payment page, and a payment simulation script is called to input the vehicle identification on the third-party payment page and trigger a payment query to obtain a payment confirmation page containing the fees to be paid.

8. The parking fee payment method according to claim 6, wherein the failure of the payment inquiry process is determined by: A query interface for detecting whether there is a parking space matching the vehicle identification; If it does not exist, the third-party payment address of the parking lot is loaded through the cloud container deployed by the server to perform payment query. If the query fails or the query is delayed, it is determined that the payment query processing has failed.

9. According to the vehicle parking payment method according to claim 1, the vehicle terminal sends the vehicle departure instruction to the server through the deployed SDK to query the parking lot, and receives the payment address returned by the server through the SDK.

10. The vehicle parking fee payment method according to claim 9, wherein the parking lot query comprises: Searching the parking entry record according to the vehicle identification carried in the vehicle departure instruction to obtain a query result; If a target entry record corresponding to the vehicle identification is found, a parking space is determined according to the target entry record; If the target entry record corresponding to the vehicle identification is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking place to obtain the parking place.

11. The vehicle parking fee payment method according to claim 9, further comprising: Perform vehicle approach detection based on vehicle operation data collected by the vehicle terminal; If a vehicle entry is detected, an image of the vehicle entry is collected and image recognition is performed through the SDK to obtain a payment identification image, and the payment identification image is uploaded to the server through the SDK to update the parking lot.

12. The parking fee payment method according to claim 11, wherein the parking lot is updated by: Decoding the payment identification image to obtain a decoding address; The payment access verification is performed according to the decoded address, and after the verification is passed, the third-party payment address of the parking lot is updated based on the decoded address.

13. A method for paying parking fees for a vehicle, applied to a service end, comprising: The parking lot is searched and obtained based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal; Generate the payment address of the parking lot and return it to the vehicle terminal; The virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot and returns the obtained fee to be paid to the virtual container for payment processing.

14. The vehicle parking fee payment method according to claim 13, wherein the step of performing a payment inquiry process on the parking lot comprises: The query interface of the parking lot is called with the vehicle identification as an input parameter to perform payment query, and the to-be-paid fee returned by the interface call is obtained.

15. The vehicle parking fee payment method according to claim 13, wherein the step of performing a payment inquiry process on the parking lot comprises: The third-party payment address of the parking lot is loaded through the cloud container deployed by the server, the vehicle identification is input on the loaded third-party payment page and a query action is triggered to obtain the to-be-paid fee returned by the parking lot.

16. The vehicle parking fee payment method according to claim 13, wherein the step of performing a payment inquiry process on the parking lot comprises: A query interface for detecting whether there is a parking space matching the vehicle identification; If it does not exist, the third-party payment address of the parking lot is loaded through the cloud container deployed by the server to perform payment query. If the query fails or the query is delayed, the third-party payment address is returned to the virtual container.

17. The vehicle parking fee payment method according to claim 13, wherein the step of querying a parking space based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal to obtain the parking space comprises: Searching the parking entry record according to the vehicle identification carried in the vehicle departure instruction to obtain a query result; If a target entry record corresponding to the vehicle identification is found, a parking space is determined according to the target entry record; If the target entry record corresponding to the vehicle identification is not found, the vehicle position uploaded by the vehicle terminal is matched with the position information of the candidate parking place to obtain the parking place.

18. A vehicle parking fee payment device, operating on a vehicle terminal, comprising: A departure instruction submission module is configured to submit a vehicle departure instruction to a server and receive a payment address returned by the server; a virtual container running module, configured to start the client installed on the vehicle terminal based on the payment address, input the payment address and vehicle identification, and run the virtual container deployed by the client; The payment inquiry module is configured to load the payment address through the virtual container and cooperate with the server to perform payment inquiry processing according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

19. A vehicle parking fee payment device, running on a service end, comprising: The parking lot query module is configured to query the parking lot according to the vehicle identification carried by the vehicle departure instruction submitted by the vehicle terminal to obtain the parking lot; a payment address generating module, configured to generate a payment address for the parking lot and return it to the vehicle terminal; The payment inquiry processing module is configured to cooperate with the virtual container deployed by the client installed on the vehicle terminal to perform payment inquiry processing on the parking lot, and return the obtained fees to be paid to the virtual container for payment processing.

20. A vehicle parking fee payment device comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: Submit the vehicle departure instruction to the server and receive the payment address returned by the server; Based on the payment address, the client installed on the vehicle terminal is started, the payment address and vehicle identification are input, and the virtual container deployed by the client is run; The payment address is loaded through the virtual container and payment query processing is performed in cooperation with the service end according to the vehicle identification, so as to perform payment processing according to the obtained fees to be paid.

21. A vehicle parking fee payment device, comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: The parking lot is searched and obtained based on the vehicle identification carried in the vehicle departure instruction submitted by the vehicle terminal; Generate the payment address of the parking lot and return it to the vehicle terminal; The virtual container deployed in conjunction with the client installed on the vehicle terminal performs payment inquiry processing on the parking lot and returns the obtained fee to be paid to the virtual container for payment processing.

22. A computer-readable storage medium for storing computer-executable instructions, wherein the computer-executable instructions implement the steps of the method of claim 1 or 13 when executed.

Images