CN112581638A

CN112581638A - Parking fee payment method and system without network parking meter

Info

Publication number: CN112581638A
Application number: CN202011435511.8A
Authority: CN
Inventors: 卢川
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-12-10
Filing date: 2020-12-10
Publication date: 2021-03-30

Abstract

The specification discloses a parking fee payment method and system without a network parking meter, wherein the method is applied to a client and comprises the following steps: connecting a parking meter based on a short-distance communication mode; acquiring parking space information from a parking meter, wherein the parking space information comprises a digital signature of the parking meter; verifying the digital signature of the parking meter, and performing the following operations after verification: sending a parking fee payment request to a user; and acquiring a parking fee payment result of the user from the payment platform, and sending the parking fee payment result and the preset parking time to the parking meter. The method and the system can realize mobile payment of the network-free parking meter, and simultaneously, a large amount of hardware equipment and network erection are not required to be configured, so that the cost for modifying the network-free parking meter is reduced.

Description

Parking fee payment method and system without network parking meter

Technical Field

The specification relates to the field of road parking charge management, in particular to a parking fee payment method and system without a network parking meter.

Background

Parking meters are electronic meters used for parking, timing and charging. The traditional parking meter has no network communication module and can only pay parking fee in a coin-feed and card-swiping mode. Meanwhile, a large amount of manpower and material resources are needed for erecting a network and replacing a parking meter with a network communication module or configuring the network communication module for the traditional parking meter.

Accordingly, it is desirable to provide a parking fee payment method without a network parking meter.

Disclosure of Invention

One aspect of the present specification provides a parking fee payment method without a network parking meter, which is applied to a client and includes: connecting a parking meter based on a short-distance communication mode; acquiring parking space information from a parking meter, wherein the parking space information comprises a digital signature of the parking meter; verifying the digital signature of the parking meter, and performing the following operations after verification: sending a parking fee payment request to a user, wherein the parking fee payment request comprises a pre-payment amount, and the pre-payment amount is determined based on preset parking time input by the user; and acquiring a parking fee payment result of the user from the payment platform, and sending the parking fee payment result and the preset parking time to the parking meter.

Another aspect of the present specification provides a parking fee payment system without a network parking meter, the system being implemented on a client, the system comprising: the first communication module is used for connecting the parking meter based on a short-distance communication mode; the parking space information acquisition module is used for acquiring parking space information from the parking meter, wherein the parking space information comprises a digital signature of the parking meter; the verification module is used for verifying the digital signature of the parking meter, and the following modules are executed after verification: the parking fee payment request module is used for sending a parking fee payment request to a user, wherein the parking fee payment request comprises a pre-payment amount, and the pre-payment amount is determined based on preset parking time input by the user; and the parking fee payment result acquisition module is used for acquiring a parking fee payment result of the user from the payment platform and sending the parking fee payment result and the preset parking time to the parking meter.

Another aspect of the present specification provides a parking fee payment method without a network parking meter, which is applied to a parking meter, and includes: connecting a client based on a near field communication mode; sending parking space information to a client, wherein the parking space information comprises a digital signature of the parking meter, so that the client verifies the digital signature, and the following operations are executed after the verification is passed: receiving a parking fee payment result and preset parking time input by a user from a client; acquiring parking fee settlement information based on parking start time, parking end time and pre-payment amount, and sending the parking fee settlement information to the client, wherein the parking start time and the parking end time are acquired based on a sensing device of a parking space, and the pre-payment amount is determined based on preset parking time input by the user; and receiving a subsidy payment result from the client.

Another aspect of the present specification provides a parking fee payment system without a network parking meter, the system being implemented on a parking meter, the system comprising: the second communication module is used for connecting the client based on a near field communication mode; the parking space information sending module is used for sending parking space information to a client, the parking space information comprises a digital signature of the parking meter, so that the client can verify the digital signature, and the following modules are executed after verification: the system comprises a preset parking time receiving module, a parking fee payment module and a parking fee payment module, wherein the preset parking time receiving module is used for receiving a parking fee payment result and preset parking time input by a user from a client; the parking fee settlement information acquisition module is used for acquiring parking fee settlement information based on parking start time, parking end time and pre-paid amount, and sending the parking fee settlement information to the client, wherein the parking start time and the parking end time are acquired based on a sensing device of a parking space, and the pre-paid amount is determined based on preset parking time input by the user; and the additional payment result receiving module is used for receiving the additional payment result from the client.

Another aspect of embodiments of the present specification provides a computer-readable storage medium, wherein the storage medium stores computer instructions that, when executed by a processor, implement a network meter-less parking fee payment method.

Drawings

The present description will be further described by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. These embodiments are not intended to be limiting, and in these embodiments like numerals are used to indicate like structures, wherein:

FIG. 1 is a schematic diagram of an application scenario of a parking fee payment system without a network parking meter according to some embodiments of the present description;

FIG. 2 is an exemplary block diagram of a client shown in accordance with some embodiments of the present description;

fig. 3 is an exemplary block diagram of a parking meter shown in accordance with some embodiments of the present description;

FIG. 4 is an exemplary flow chart of a parking fee payment method applied to a client without a network parking meter, according to some embodiments of the present description;

FIG. 5 is an exemplary flow chart of another network-less parking fee payment method applied to a client, according to some embodiments of the present description;

fig. 6 is an exemplary flow diagram of a parking fee payment method applied to a network-less parking meter of the parking meter according to some embodiments of the present description;

fig. 7 is a schematic diagram illustrating verification of a digital signature of a parking meter, according to some embodiments of the present description;

fig. 8 is a schematic diagram illustrating encryption and decryption of a digital signature according to some embodiments of the present description.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the present description, and that for a person skilled in the art, the present description can also be applied to other similar scenarios on the basis of these drawings without inventive effort. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

It should be understood that "system", "device", "unit" and/or "module" as used in this specification is a method for distinguishing different components, elements, parts or assemblies at different levels. However, other words may be substituted by other expressions if they accomplish the same purpose.

As used in this specification and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

Flow charts are used in this description to illustrate operations performed by a system according to embodiments of the present description. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, the various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or several steps of operations may be removed from the processes.

Fig. 1 is a schematic view of an application scenario of a parking fee payment system without a parking meter according to some embodiments of the present description.

The parking fee payment system 100 without a parking meter can train a medical image segmentation model conforming to the habit of a user with only a small number of user interactions by implementing the method and/or process disclosed in the specification.

As shown in fig. 1, the parking fee payment system 100 without a network parking meter may include a client 101, a parking meter 102, a payment platform 104, a sensing device 105, a short-range communication 106, a network 107, and the like.

The client 101 may be any type of device having information receiving and/or transmitting capabilities. In some embodiments, the client 101 may receive and/or transmit information from the meter 102 based on the close range communication 106. For example, the client 101 may receive parking space information and parking fee settlement information from a parking meter. For another example, the client 101 may transmit the parking fee payment result and the preset parking time to the parking meter. In some embodiments, the client may receive and/or transmit information from the payment platform based on the network 107. For example, the client 101 may receive a parking fee payment result from the payment platform. As another example, the client 101 may send a refund payment request to the payment platform. In some embodiments, the client 101 may be a mobile device that is conveniently carried by the user 103. For example, the client 101 may include a cell phone, a tablet, a wearable device, other electronic devices, and the like.

The parking meter 102 is an electronic meter for charging parking time. In some embodiments, the meter may be based on the proximity communication 106, and the client may perform data transfer. For example, the parking meter may send parking space information and parking fee calculation information to the client. As another example, the parking meter may receive a parking fee payment result from the client. In some embodiments, the meter 102 may manage one or more parking spaces. For example, the parking meter may obtain parking space information based on the sensing device 105. For another example, the parking meter may perform a lighting operation based on the parking fee payment result.

The payment platform 104 is a platform for parking meters merchants to collect parking fees for users. In some embodiments, the payment platform may be a broker that is independent of the meter merchant. For example, the payment platform may include online banking, third party payment platforms, and the like. In some embodiments, the payment platform may also include a meter merchant's billing platform. In some embodiments, the payment platform may be a system with computing capabilities, may include various computers, such as a server, a personal computer, or may be a computing platform consisting of multiple computers connected in various configurations.

The sensing device 105 is a device that converts information detected by the sensing element into an electrical signal or other desired form of information output. In some embodiments, the sensing device may include, but is not limited to, a combination of one or more of a vibration sensing device, a magnetic sensing device, a gas sensing device, a pressure sensing device, and the like. It will be appreciated that the sensing devices differ in their sensing elements and the information detected will vary accordingly. For example, if the sensing element of the magnetic sensing device is an electromagnetic coil and the detected information is an electrical signal, the end time of the detected electrical signal can be converted into the parking start time and sent to the parking meter 102.

The close range communication 106 may facilitate the exchange of data and/or information for the client 101 and the meter 102. For example, the client 101 may obtain parking space information from the parking meter 102 via the near-end distance communication 106. For another example, the client 101 may transmit the parking fee payment result and the preset parking time to the parking meter 102 through the short-range communication 106. In some embodiments, the close range communication 106 may include bluetooth, ZigBee, wifi, radio frequency, Near Field Communication (NFC), and the like.

The network 107 may facilitate the exchange of data and/or information for the client 101 and the payment platform 104. For example, the client 101 may obtain the parking fee payment result of the user from the payment platform 104 through the network 107. In some embodiments, the network 107 may be any type of wired or wireless network. For example, network 107 may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Public Switched Telephone Network (PSTN), a short-range communication, and the like, or any combination thereof. In some embodiments, the network 107 may include one or more network entry and exit points. For example, the network 107 may include wired or wireless network access points, such as base stations and/or internet switching points, through which one or more components of the system 100 may connect to the network 107 to exchange data and/or information.

Fig. 2 is an exemplary block diagram of a client shown in accordance with some embodiments of the present description.

In some embodiments, the first communication module 210, the parking space information obtaining module 220, the verification module 230, the parking fee payment request module 240, and the parking fee payment result obtaining module 250 may be included in the modules of the client 101.

The first communication module 210 is configured to connect to a parking meter based on a short-range communication method. For more description of the first communication module 210, refer to step 410, which is not described herein.

The parking space information obtaining module 220 is configured to obtain parking space information from the parking meter, where the parking space information includes a digital signature of the parking meter. In some embodiments, the parking space information further includes a parking space identification and a parking start time. For more description of the parking space information obtaining module 220, refer to step 420, and are not described herein.

And the verification module 230 is used for verifying the digital signature of the parking meter. In some embodiments, the digital signature is encrypted with the first key via the parking meter, and the verification module is further configured to: the digital signature is decrypted based on a second key that matches the first key. For more description of the verification module 230, refer to step 430, which is not described in detail herein.

A parking fee payment request module 240, configured to send a parking fee payment request to the user, where the parking fee payment request includes a prepaid amount, and the prepaid amount is determined based on a preset parking time input by the user. For more description of the parking fee payment request module 240, refer to step 440, which is not described in detail herein.

And a parking fee payment result obtaining module 250, configured to obtain a parking fee payment result of the user from the payment platform, and send the parking fee payment result and preset parking time to the parking meter. For more description of the parking fee payment result acquisition module 250, refer to step 450, which is not described herein.

In some embodiments, the modules of the client 101 may further include a parking fee settlement information receiving module 260, a settlement payment request module 270, and a reimbursement payment result sending module 280.

And a parking fee settlement information receiving module 260 for receiving parking fee settlement information from the parking meter. In some embodiments, the parking fee settlement information includes a reimbursement fee or a refund fee. For more description of the parking fee settlement information receiving module 260, refer to step 510, which will not be described in detail.

And a settlement payment request module 270, configured to initiate a subsidy payment request to the user or send a refund payment request to the payment platform based on the parking fee settlement information. For more description of the settlement payment request module 270, refer to step 520, which is not described herein.

And the reimbursement payment result sending module 280 is used for sending the reimbursement payment result acquired from the payment platform to the parking meter. For more description of the reimbursement payment result sending module 280, refer to step 530, which is not described herein.

Fig. 3 is an exemplary block diagram of a parking meter shown in accordance with some embodiments of the present description.

In some embodiments, the parking meter 102 may include a second communication module 310, a parking space information transmitting module 320, a preset parking time receiving module 330, a parking fee settlement information acquiring module 340, and a subsidy payment result receiving module 350.

And a second communication module 310, configured to connect to the client based on the near field communication method. For more description of the second communication module 310, refer to step 610, which is not described herein.

The parking space information sending module 320 is configured to send parking space information to the client, where the parking space information includes a digital signature of the parking meter, so that the client verifies the digital signature. For more description of the parking space information sending module 320, refer to step 620, which is not described herein.

The preset parking time receiving module 330 is configured to receive a parking fee payment result and a preset parking time input by a user from the client. For more description of the preset parking time receiving module 330, refer to step 630, which is not described herein.

The parking fee settlement information obtaining module 340 is configured to obtain parking fee settlement information based on a parking start time, a parking end time, and a prepaid amount, and send the parking fee settlement information to the client, where the parking start time and the parking end time are obtained based on a sensing device of a parking space, and the prepaid amount is determined based on a preset parking time input by the user. For more description of the parking fee settlement information acquiring module 340, refer to step 640, which will not be described in detail herein.

And a reimbursement payment result receiving module 350, configured to receive a reimbursement payment result from the client. For more description of the reimbursement payment result receiving module 350, refer to step 650, which is not described herein.

Fig. 4 is an exemplary flow chart of a parking fee payment method applied to a client without a network parking meter according to some embodiments of the present description.

As shown in fig. 4, the parking fee payment method 400 without a network parking meter may include:

and step 410, connecting the parking meter based on the short-distance communication mode.

In particular, step 410 may be performed by the first communication module 210.

The short-range communication system is a system in which both communication parties transmit information by radio waves within a transmission distance of a short range (several tens of meters). In some embodiments, the close range communication means may include one or more of bluetooth, zigbee, radio frequency, wifi, near field communication, and the like.

Parking meters are electronic meters used for parking, timing and charging. The traditional network-free parking meter has no network communication module, so that the client can be connected with the network-free parking meter in a short-distance communication mode.

Specifically, after the user enters the transmission distance of the parking meter, the client actively establishes a communication link with the parking meter by receiving radio waves sent by the parking meter.

Taking a bluetooth communication mode as an example, after a user carries a mobile phone to a place near a parking meter, opens the bluetooth of the mobile phone, finds the parking meter by receiving radio waves sent by the parking meter, and completes the establishment of a communication link with the parking meter after the parking meter is successfully paired.

Step 420, parking space information is obtained from the parking meter.

Specifically, step 420 may be performed by parking space information acquisition module 220.

The parking space information is information related to a parking space selected by a user. As described above, the parking meter is an electronic meter for parking fee counting. In some embodiments, a meter may charge one or more parking spaces on a timed basis. After the user selects the parking space for parking, the parking meter corresponding to the parking space sends parking space information to the client.

In some embodiments, the parking space information includes a digital signature of the parking meter. The digital signature of the parking meter is a character string which is generated by the parking meter based on transmission data and cannot be forged by other people. For a detailed description of the digital signature of the parking meter, reference may be made to fig. 7, which is not described herein again.

In some embodiments, the parking space information further includes a parking space identification and a parking start time.

The parking space identifier is a symbol for representing a parking space. It will be appreciated that each parking space may be represented by a corresponding identification. The identification may include numbers (e.g., 1, 2), letters (e.g., a, b), addresses of parking spaces, or other symbols. For example, the identification of the parking space selected by the user is: greening road No. 999.

The parking start time refers to a time during which the user's vehicle enters a parking space and stops moving. It is understood that the parking start time is a parking fee counting start time.

The detailed description of the parking space information may be referred to in step 620, which is not repeated herein.

In some embodiments, the client may receive parking space information from the parking meter via a short-range communication means connected to the parking meter.

And step 430, verifying the digital signature of the parking meter.

In particular, step 430 may be performed by the verification module 230.

As mentioned above, the digital signature of the parking meter is a character string that is generated based on the transmission data and cannot be forged by others. Therefore, the client can verify the identity information of the parking meter by verifying the digital signature of the parking meter.

For a detailed description of verifying the digital signature of the parking meter, reference may be made to fig. 7, which is not described herein again.

Further, if the digital signature of the parking meter is not verified by the client, the operation is stopped; if the digital signature of the parking meter is verified by the client, the steps 440 and 450 are continued:

step 440, a parking fee payment request is sent to the user.

Specifically, step 440 may be performed by the parking fee payment request module 240.

In order to reduce the occupied time and space of the vehicle for the parking space and prompt the user to have a reasonable concept of parking time, the parking fee payment request module 240 may transmit a parking fee payment request to the user.

The parking fee payment request is a request initiated by the user to make a pre-payment before the end of the parking time. In some embodiments, the parking fee payment request includes a prepaid amount that is determined based on a preset parking time entered by the user. The preset parking time is estimated parking time of a user based on a reasonable parking time concept.

In some embodiments, the parking fee payment request module 240 may obtain the preset parking time from the user and then generate the parking fee payment request including the prepaid amount based on the preset parking time.

For example, if the user inputs the preset parking time at the client for 2 hours, the client calculates the prepayment amount to be 20 yuan based on the preset parking time for 2 hours; further, the client generates a parking fee payment request based on the prepaid amount of 20 yuan and sends the parking fee payment request to the user.

In some embodiments, the parking fee payment request module 240 may also first send the parking fee payment request including the option of the pre-set parking time and the pre-payment amount to the user, and generate a complete parking fee payment request based on the option input by the user.

For example, the parking fee payment request sent by the client to the user includes: and (3) selecting options of [ preset parking time 1 hour, prepayment amount 8 Yuan ], [ preset parking time 2 hours, prepayment amount 20 Yuan ], and [ preset parking time 3 hours, prepayment amount 40 Yuan ], and generating a complete parking fee payment request after a user selects [ preset parking time 2 hours, prepayment amount 20 Yuan ].

In some embodiments, the user may also enter a selected payment platform. The payment platform is a platform for parking meter merchants to charge parking fees of users.

In some embodiments, the payment platform may be a broker that is independent of the meter merchant. For example, the payment platform may include online banking, third party payment platforms, and the like.

Specifically, the client may transfer the prepaid amount from the user account of the payment platform to the account of the meter merchant in the payment platform based on the payment platform selected by the user and the corresponding payment password.

For example, after the user inputs the preset parking time for 2 hours, and inputs the selected payment platform bank a, the client may transfer 20 yuan from the account of the user in the bank a to the account of the parking meter merchant in the bank a.

In some embodiments, the payment platform may also include a meter merchant's billing platform.

Specifically, the user transfers a certain amount of money to the parking meter merchant from an internet bank or a third-party payment platform to replace the virtual token with the amount corresponding to the charging platform of the parking meter merchant, and then directly deducts the virtual token with the same value as the pre-paid amount from the charging platform of the parking meter merchant based on the charging platform of the parking meter merchant selected by the user and the corresponding payment password.

For example, a user purchases 100 virtual tokens of a charging platform of a parking meter merchant by transferring 100 dollars from a user account of an internet bank or a third party payment platform to a corresponding payment platform account of the parking meter merchant, and the user inputs a selected payment platform after inputting a preset parking time of 2 hours: the charging platform of the parking meter merchant, the client can deduct 20 virtual tokens from the account of the user on the charging platform of the parking meter merchant directly.

And 450, acquiring a parking fee payment result of the user from the payment platform, and sending the parking fee payment result and preset parking time to the parking meter.

Specifically, step 450 may be performed by the parking fee payment result acquisition module 250.

After the user finishes payment on the payment platform, the payment platform generates a parking fee payment result of the user. The parking fee payment result is information representing whether the user pays the parking fee in advance successfully. In some embodiments, the client may obtain the parking fee payment result of the user from the payment platform through the network 107. Further, the client may send the parking fee payment result to the parking meter 102 through the short-range communication 106, so that the parking meter performs other operations based on the parking fee payment result. For a detailed description of the parking meter performing other operations based on the parking fee payment result, reference may be made to step 630, which is not described herein again.

In some embodiments, the client may also obtain payment time of the user, other parking fee payment information of the payment platform, and the like from the payment platform. It can be understood that the client can store the payment time, the payment platform and other parking fee payment information acquired from the payment platform in the client, so that the user can conveniently inquire the parking fee payment information.

In some embodiments, the client may also send the preset parking time input by the user at the client to the parking meter through the short-range communication 106. Further, the parking meter may determine whether parking is overtime based on a preset parking time. For a detailed description of the parking meter determining whether the parking time is over based on the preset parking time, reference may be made to step 650, which is not described herein again.

Fig. 5 is an exemplary flow chart of another network-less parking fee payment method applied to a client according to some embodiments of the present description.

As shown in fig. 5, the parking fee payment method 500 without a parking meter may include:

step 510, receiving parking fee settlement information from the parking meter.

Specifically, the step 510 may be performed by the parking fee settlement information receiving module 260.

In some embodiments, when the user's parking time is over, the client may again connect with the parking meter.

In some embodiments, since the client is connected to the parking meter based on the short-distance communication mode, after the client enters the transmission distance of the parking meter, the client may automatically establish a communication link with the parking meter by receiving radio waves sent by the parking meter.

Continuing to take the bluetooth communication mode as an example, the user carries the mobile phone to the vicinity of the parking meter, turns on the bluetooth of the mobile phone, and automatically establishes a communication link with the parking meter based on the result of successful pairing after receiving the radio waves sent by the parking meter.

Further, the client may receive parking fee settlement information from the parking meter.

The parking fee settlement information is parking fee information settled based on the parking meter. In some embodiments, the parking fee settlement information includes a reimbursement fee or a refund fee.

It will be appreciated that the user prepays for a parking fee calculated based on the preset parking time before the parking time is over, and the actual parking time may be more or less than the preset parking time, and the actual parking fee may be higher or lower than the prepayment fee accordingly.

The additional payment is the parking fee which needs to be paid by the user when the actual parking fee is higher than the pre-payment fee. In some embodiments, the amount of the subsidized fee, i.e., the actual parking fee, is subtracted by the prepaid fee.

The refund fee is the fee for parking that the parking meter merchant refunds to the user from the prepaid fee when the actual parking fee is lower than the prepaid fee. In some embodiments, the amount of the refund fee, i.e., the pre-paid payment, is less the actual parking fee.

The detailed description of the parking meter acquiring the parking fee settlement information can be referred to in step 640, and will not be described herein.

In some embodiments, the client may obtain parking fee settlement information from the parking meter through the short-distance communication mode.

And step 520, initiating a subsidy payment request to the user or sending a refund payment request to the payment platform based on the parking fee settlement information.

In particular, step 520 may be performed by settlement payment request module 270.

If the parking fee settlement information includes the subsidy fee, a request for subsidy payment may be sent to the user. The request for payment due is a request for payment after the parking time is over, which is initiated to the user. In some embodiments, the reimbursement payment request includes an amount of the reimbursement charge. In some embodiments, the user may also enter the selected payment platform at the client.

Specifically, the client may transfer the additional payment amount from the user account of the payment platform to the account of the parking meter merchant in the payment platform or directly deduct the virtual token equivalent to the additional payment amount from the user account of the charging platform of the parking meter merchant based on the payment platform selected by the user and the corresponding payment password. For a detailed description of the payment platform, reference may be made to step 440, which is not described herein again.

If the parking fee settlement information includes a refund fee, a refund payment request may be sent to the payment platform. The request for paying for additional payment is a request for refunding to the parking meter merchant after the parking time is over. In some embodiments, the refund payment request includes a refund fee amount.

Specifically, the client may transfer the refund fee amount from the account of the parking meter merchant of the payment platform to the user account of the payment platform or directly add a virtual token equivalent to the refund amount from the user account of the charging platform of the parking meter merchant based on the payment platform selected by the user for pre-payment. For a detailed description of the payment platform, reference may be made to step 440, which is not described herein again.

And step 530, sending the payment supplementing result acquired from the payment platform to a parking meter.

Specifically, step 530 may be performed by the reimbursement payment result sending module 280.

Like the prepayment, after the user completes the payment of the additional payment fee on the payment platform, the payment platform generates an additional payment result of the user. The subsidy payment result is information representing whether the user successfully subsidies and pays the parking fee.

In some embodiments, the client may obtain the user's subsidy payment results from the payment platform via the network 107.

Further, the client may send the payment result to the parking meter 102 through the short-distance communication 106, so that the parking meter performs other operations based on the payment result. For a detailed description of the parking meter performing other operations based on the result of the payment of the subsidy, refer to step 650, which is not described herein.

In some embodiments, the client may also obtain other information of the user's reimbursement time, payment platform, and the like from the payment platform. The client can store the parking fee payment information such as the payment completion time and the payment platform acquired from the payment platform in the client, so that the client can conveniently inquire.

In some alternative embodiments, the user may pay the entire parking fee directly after parking is complete, without making a pre-payment for the parking fee.

Specifically, the client may receive an actual parking fee obtained based on the parking start time and the parking end time from the parking meter, and then initiate a payment request to the user based on the actual parking fee. Further, the client sends the payment result obtained from the payment platform to the parking meter.

Fig. 6 is an exemplary flow chart of a parking fee payment method applied to a network-less parking meter according to some embodiments of the present description.

As shown in fig. 6, the parking fee payment method 600 without a parking meter may include:

step 610, connecting the client based on the near field communication mode.

In particular, step 610 may be performed by the second communication module 310.

As described above, the short-range communication system is a system in which both communication parties transmit information by radio waves within a transmission distance of a short range (several tens of meters). Parking meters are electronic meters used for parking, timing and charging.

Specifically, the meter continuously transmits radio waves, waiting for a communication link to be established with a client entering a transmission distance. The detailed description of the short-range communication method can be referred to in step 410, and is not repeated here.

Step 620, sending parking space information to the client, wherein the parking space information comprises a digital signature of the parking meter.

Specifically, step 620 may be performed by parking space information sending module 320.

As described above, the parking space information is information related to the parking space selected by the user. In some embodiments, the parking space information includes a digital signature of the parking meter. The digital signature of the parking meter is a character string which is generated by the parking meter based on transmission data and cannot be forged by other people.

Further, the parking meter can send the digital signature of the parking meter to the client through the short-distance communication mode 106, so that the client can verify the digital signature. For a detailed description of the digital signature of the client verification parking meter, reference may be made to fig. 7, which is not repeated herein.

Further, if the digital signature of the parking meter is not verified by the client, the operation is stopped; if the digital signature of the parking meter is verified by the client, the steps 630 to 650 are continued.

In some embodiments, the parking space information may also include a parking space identification and a parking start time. As described above, the parking space identification is a symbol for representing a parking space. The parking start time refers to a time during which the user's vehicle enters a parking space and stops moving. In some embodiments, the parking meter may obtain the parking space identification and the parking start time through a sensing device of the parking space.

The sensing device is a device for converting information detected by the sensing element into an electric signal or outputting information in a required form. In some embodiments, the sensing device may include, but is not limited to, a combination of one or more of a vibration sensing device, a magnetic sensing device, a gas sensing device, a pressure sensing device, and the like. It will be appreciated that the sensing devices differ in their sensing elements and the information detected will vary accordingly. For example, if the sensitive element of the magnetic sensing device is an electromagnetic coil and the detected information is an electrical signal, the end time of the detected electrical signal can be converted into the parking start time, and the identifier of the parking space where the electrical signal is detected can be obtained.

Specifically, after the sensor of the parking space detects that the vehicle enters the parking space selected by the user and stops moving, the parking space identifier and the parking start time are sent to the parking meter corresponding to the parking space through a near-end network or a wired cable.

In some embodiments, the parking space further comprises a parking lock device for restricting egress of a vehicle from the parking space. The parking lock device may be a retractable barrier on the floor of the parking space. In some embodiments, when the parking space is empty, the parking lock device retracts into the ground, and when the sensing device detects that the vehicle enters the parking space selected by the user and stops moving, a vehicle locking instruction is sent to the parking lock device; furthermore, the parking lock stretches out of the ground after receiving the vehicle locking command, and the vehicle is prevented from running out. In some embodiments, the park lock may also receive a lock command from the parking meter.

Step 630, receiving the parking fee payment result and the preset parking time input by the user from the client.

Specifically, step 630 may be performed by preset parking time receiving module 330.

As described above, the parking fee payment result is information representing whether the user pays the parking fee in advance successfully. In some embodiments, the parking meter may prompt the traffic police to manage the user's vehicle based on the parking fee payment result.

Specifically, after the parking meter receives a signal that a user vehicle drives into a parking space from the sensor, the prompting lamp can be turned on to indicate that the parking fee is not paid, and if the user pays the parking fee, the parking meter receives a parking fee payment result of 'the user pays the parking fee in advance successfully' from the client, and then the prompting lamp is turned off; if the user does not pay the parking fee or the parking meter receives the parking fee payment result of 'the user does not pay the parking fee successfully' from the client and then leaves, the parking meter continuously lights a prompting lamp so as to prompt a traffic police to carry out penalty attaching on the user vehicle without paying the parking fee in advance.

As previously described, the preset parking time is the estimated parking time of the user based on the concept of reasonable parking time. In some embodiments, the parking meter may acquire parking fee settlement information based on a preset parking time. For a detailed description of acquiring the parking fee settlement information based on the preset parking time, reference may be made to step 650, which is not described herein again.

In some embodiments, the parking meter may receive the parking fee payment result and the preset parking time input by the user from the client through the short-distance communication.

And step 640, acquiring parking fee settlement information based on the parking start time, the parking end time and the prepaid amount, and sending the parking fee settlement information to the client.

Specifically, the step 640 may be performed by the parking fee settlement information acquiring module 340.

The parking fee settlement information is parking fee information settled based on the parking meter. In some embodiments, the parking fee settlement information includes a reimbursement fee or a refund fee. The additional payment is the parking fee which needs to be paid by the user when the actual parking fee is higher than the pre-payment fee. The refund fee is the fee for parking that the parking meter merchant refunds to the user from the prepaid fee when the actual parking fee is lower than the prepaid fee.

It should be noted that before the parking meter obtains the parking fee settlement information, the parking meter needs to connect to the client again based on the short-range communication method, and the detailed description may refer to step 510, which is not described herein again.

As described above, since the user prepays the parking fee calculated based on the preset parking time before the parking time is over, the actual parking time may be more or less than the preset parking time, and the amount of the actual parking fee may be correspondingly higher or lower than the prepayment amount, the parking meter may acquire the parking fee settlement information based on the parking start time, the parking end time, and the preset parking time.

The parking start time refers to a time during which the user's vehicle enters a parking space and stops moving. It is understood that the parking start time is a parking fee counting start time. For a detailed description of obtaining the parking start time, refer to step 620, which is not described herein.

The parking end time is a time when the user's vehicle is ready to exit the parking space, corresponding to the parking start time. It is understood that the parking end time is a parking fee counting end time.

In some embodiments, the parking meter may obtain the parking end time through a sensing device of the parking space. For a detailed description of the sensing device, refer to step 620, which is not described herein.

Specifically, after the sensor of the parking space detects that the vehicle starts to move in the parking space, the parking space identifier and the time for detecting the movement of the vehicle are used as the parking end time, and the parking end time is sent to the parking meter corresponding to the parking space through a near-end network or a wired cable.

In some embodiments, the parking meter may also obtain the parking end time by receiving a parking end instruction input by the user from the client.

Specifically, the client takes the time when the user inputs the parking ending instruction at the client as the parking ending time, and sends the parking ending time to the parking meter corresponding to the parking space in the short-distance communication mode.

As previously described, the prepaid amount is determined based on the preset parking time input by the user. For a detailed description of the prepaid amount, reference may be made to step 440, which is not described in detail herein.

Further, the parking meter calculates actual parking time based on parking start time and parking end time of the same parking space identifier, then obtains actual parking fee amount based on the actual parking time, compares the actual parking fee amount with the pre-paid amount, judges whether the user needs to make up payment or whether the merchant needs to refund payment, and obtains the making up payment fee or the refund fee.

For example, if the parking meter receives the greening road 999 in sequence that the parking start time of the parking space is 9:00:00 within 20 days of 5 months and the parking end time is 12:00:00 within 20 days of 5 months, the actual parking time which can be obtained by the parking meter is 3 hours; further, the parking meter can obtain the amount of the actual parking fee as 40 yuan based on the actual parking time, and the amount of the actual parking fee is compared with the pre-paid amount of 20 yuan to judge that the user needs to be paid additionally, and obtain the additional payment fee as 20 yuan.

For another example, if the parking meter receives the greening road 999 that the parking start time of the parking space is 9:00:00 in 20 days in 5 months and the parking end time is 10:00:00 in 20 days in 5 months, the actual parking time which can be obtained by the parking meter is 1 hour; further, the parking meter can obtain the amount of the actual parking fee as 8 yuan based on the actual parking time, and by comparing the amount with the pre-paid amount of 20 yuan, the fact that the merchant needs to refund is judged, and the refund fee is obtained as 12 yuan.

In some embodiments, the parking meter may send the parking fee settlement information to the client through the short-distance communication mode.

For example, the parking meter may send "make up 20 yuan" or "refund 12 yuan" to the client via bluetooth.

Step 650, receiving the subsidy payment result from the client.

In particular, step 650 may be performed by the payup payment result receiving module 350.

As mentioned above, the subsidy payment result is information indicating whether the user is successful in subsidy payment. In some embodiments, the parking meter may prompt the traffic police to manage the user's vehicle based on the subsidy payment results.

Specifically, when the parking meter judges that the parking of the user is overtime based on the parking start time, the parking end time and the preset parking time, the prompting lamp can be turned on to indicate that the parking is overtime, and if the user pays the additional payment fee, the parking meter receives a parking fee payment result of 'the user successfully pays the additional payment fee' from the client, and then the prompting lamp is turned off; if the user does not pay the additional payment or the parking meter receives the parking fee payment result that the user does not pay the additional payment successfully from the client and then leaves, the parking meter continuously lights a prompting lamp so as to prompt a traffic police to carry out penalty attaching on the user vehicle which does not pay the additional payment.

As mentioned above, the parking space further comprises a parking lock device for restricting the vehicle in the parking space from exiting the parking space. In some embodiments, when the sensing device detects that the vehicle starts moving, an unlocking instruction is sent to the parking lock device; furthermore, the parking lock retracts to the ground after receiving the unlocking instruction, and the vehicle can run out.

In some embodiments, the parking meter may also send an unlocking instruction to the parking lock based on the subsidy payment result. Specifically, if the user pays the additional payment fee, the parking meter receives a parking fee payment result of 'the user pays the additional payment fee successfully' from the client, an unlocking instruction is sent to the parking lock, and the vehicle can be driven out; if the user does not pay the additional payment or the parking meter receives a parking fee payment result of 'the user does not pay the additional payment successfully' from the client, the parking meter does not send an unlocking instruction, and the parking lock continuously prevents the vehicle from running out.

Fig. 7 is a schematic diagram illustrating verification of a digital signature of a parking meter, according to some embodiments of the present description.

As mentioned above, the digital signature of the parking meter is a character string that is generated based on the transmission data and cannot be forged by others.

As shown in fig. 7, when the parking meter sends transmission data, a digest is generated from the transmission data through a hash function, then the digest is encrypted by using a private key of the parking meter to obtain a digital signature of the parking meter, and the digital signature and the transmission data are sent to the client together.

Further, the client calculates the digest from the received transmission data by using the same hash function, decrypts the received digital signature based on the public key, and if the calculated digest is the same as the decrypted digital signature, the parking meter is proved to transmit the transmission data.

In some embodiments, the transmission data may be a random number generated by the parking meter, or may be a parking space identifier and/or a parking start time in the parking space information of the parking meter.

In some embodiments, the digital signature may be encrypted with the first key via a parking meter.

Wherein the encryption may comprise a combination of one or more of symmetric encryption and asymmetric encryption.

Symmetric encryption refers to an encryption technique in which the encryption key and the decryption key are the same. In some embodiments, symmetric encryption may include, but is not limited to: data Encryption Standard (DES), Triple Data Encryption Standard (3 DES), Advanced Encryption Standard (AES), RC2 algorithm, RC4 algorithm, RC5, Blowfish Encryption algorithm, and the like.

Asymmetric encryption refers to an encryption technique in which an encryption password and a decryption password are different. In some embodiments, asymmetric encryption may include, but is not limited to: RSA Algorithm, Digital Signature Algorithm (DSA), Elliptic Curve Algorithm (ECC), Elliptic Curve Signature Algorithm (Elliptic Curve Cryptography and Digital Signature Algorithm (ECDSA), etc. In some embodiments, the encryption technology may also be in other ways, and the embodiments of the present application are not limited.

In some embodiments, the first key in the parking meter may be stored in the parking meter by the management platform of the parking meter merchant at the time of setting up the parking meter.

Specifically, the management platform of the parking meter merchant may generate a first key and a second key that match, store the first key in the parking meter when the parking meter is set, and send the second key to the client of the user when the user is registered as a parking meter user.

In some embodiments, the first key and the second key may be the same or different. It will be appreciated that if the parking meter utilizes symmetric encryption, the first key and the second key are the same; if the parking meter utilizes asymmetric encryption, the first key and the second key are different.

Further, the client 101 may decrypt the digital signature based on a second key that matches the first key. Taking fig. 8 as an example, the parking meter 102 encrypts the digital signature based on the first key and transmits the encrypted digital signature to the client 101, and the client 101 decrypts the digital signature based on the second key.

The beneficial effects that may be brought by the embodiments of the present description include, but are not limited to: (1) the short-distance communication mode is simple to configure, the modification cost of the traditional network-free parking meter is reduced, meanwhile, the network-free parking meter can realize mobile payment, and the use experience of a user is improved; (2) the existing client of the user can be connected with the parking meter based on a short-distance communication mode and can also be connected with the payment platform based on a network, so that the network-free parking meter and the payment platform can be connected without independently erecting a network for the network-free parking meter, and manpower and material resources are reduced; (3) the client verifies the identity information of the parking meter based on the digital signature, so that the client and the parking meter can be matched, and data transmission errors are reduced. It is to be noted that different embodiments may produce different advantages, and in different embodiments, any one or combination of the above advantages may be produced, or any other advantages may be obtained.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing detailed disclosure is to be regarded as illustrative only and not as limiting the present specification. Various modifications, improvements and adaptations to the present description may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present specification and thus fall within the spirit and scope of the exemplary embodiments of the present specification.

Also, the description uses specific words to describe embodiments of the description. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the specification is included. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the specification may be combined as appropriate.

Moreover, those skilled in the art will appreciate that aspects of the present description may be illustrated and described in terms of several patentable species or situations, including any new and useful combination of processes, machines, manufacture, or materials, or any new and useful improvement thereof. Accordingly, aspects of this description may be performed entirely by hardware, entirely by software (including firmware, resident software, micro-code, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the present description may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media.

The computer storage medium may comprise a propagated data signal with the computer program code embodied therewith, for example, on baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, etc., or any suitable combination. A computer storage medium may be any computer-readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code located on a computer storage medium may be propagated over any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or any combination of the preceding.

Computer program code required for the operation of various portions of this specification may be written in any one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB.NET, Python, and the like, a conventional programming language such as C, Visual Basic, Fortran2003, Perl, COBOL2002, PHP, ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or processing device. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).

Additionally, the order in which the elements and sequences of the process are recited in the specification, the use of alphanumeric characters, or other designations, is not intended to limit the order in which the processes and methods of the specification occur, unless otherwise specified in the claims. While various presently contemplated embodiments of the invention have been discussed in the foregoing disclosure by way of example, it is to be understood that such detail is solely for that purpose and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements that are within the spirit and scope of the embodiments herein. For example, although the system components described above may be implemented by hardware devices, they may also be implemented by software-only solutions, such as installing the described system on an existing processing device or mobile device.

Similarly, it should be noted that in the preceding description of embodiments of the present specification, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to imply that more features than are expressly recited in a claim. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

For each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., cited in this specification, the entire contents of each are hereby incorporated by reference into this specification. Except where the application history document does not conform to or conflict with the contents of the present specification, it is to be understood that the application history document, as used herein in the present specification or appended claims, is intended to define the broadest scope of the present specification (whether presently or later in the specification) rather than the broadest scope of the present specification. It is to be understood that the descriptions, definitions and/or uses of terms in the accompanying materials of this specification shall control if they are inconsistent or contrary to the descriptions and/or uses of terms in this specification.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present disclosure. Other variations are also possible within the scope of the present description. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the specification can be considered consistent with the teachings of the specification. Accordingly, the embodiments of the present description are not limited to only those embodiments explicitly described and depicted herein.

Claims

1. A parking fee payment method without a network parking meter is applied to a client side and comprises the following steps:

connecting a parking meter based on a short-distance communication mode;

acquiring parking space information from the parking meter, wherein the parking space information comprises a digital signature of the parking meter;

verifying the digital signature of the parking meter, and executing the following operations after verification:

sending a parking fee payment request to a user, wherein the parking fee payment request comprises a pre-payment amount, and the pre-payment amount is determined based on preset parking time input by the user;

and acquiring a parking fee payment result of the user from a payment platform, and sending the parking fee payment result and the preset parking time to the parking meter.

2. The method of claim 1, further comprising:

receiving parking fee settlement information from the parking meter;

based on the parking fee settlement information, initiating a subsidy payment request to the user or sending a refund payment request to the payment platform;

and sending the payment result of the additional payment acquired from the payment platform to the parking meter.

3. The method of claim 2, the parking space information further comprising a parking space identification and a parking start time, the parking fee settlement information comprising a reimbursement fee or a refund fee.

4. The method of claim 1, the digital signature being encrypted with a first key via a parking meter, the method further comprising:

decrypting the digital signature based on a second key that matches the first key.

5. A parking fee payment system without a network parking meter, the system implemented on a client, the system comprising:

the first communication module is used for connecting the parking meter based on a short-distance communication mode;

the parking space information acquisition module is used for acquiring parking space information from the parking meter, and the parking space information comprises a digital signature of the parking meter;

the verification module is used for verifying the digital signature of the parking meter, and the following modules are executed after the verification is passed:

the parking fee payment request module is used for sending a parking fee payment request to a user, wherein the parking fee payment request comprises a pre-payment amount, and the pre-payment amount is determined based on preset parking time input by the user;

and the parking fee payment result acquisition module is used for acquiring a parking fee payment result of the user from a payment platform and sending the parking fee payment result and the preset parking time to the parking meter.

6. The system of claim 5, further comprising:

the parking fee settlement information receiving module is used for receiving parking fee settlement information from the parking meter;

the settlement payment request module is used for initiating a subsidy payment request to the user or sending a refund payment request to the payment platform based on the parking fee settlement information;

and the payment supplementing and paying result sending module is used for sending the payment supplementing and paying result acquired from the payment platform to the parking meter.

7. The system of claim 5, the digital signature encrypted with a first key via a parking meter, the verification module further to:

8. A parking fee payment method without a network parking meter is applied to the parking meter and comprises the following steps:

connecting a client based on a near field communication mode;

sending parking space information to the client, wherein the parking space information comprises a digital signature of the parking meter, so that the client can verify the digital signature, and after verification, executing the following operations:

receiving a parking fee payment result and preset parking time input by a user from the client;

acquiring parking fee settlement information based on parking start time, parking end time and pre-payment amount, and sending the parking fee settlement information to the client, wherein the parking start time and the parking end time are acquired based on a sensing device of a parking space, and the pre-payment amount is determined based on preset parking time input by the user;

and receiving a subsidy payment result from the client.

9. A network meter-less parking fee payment system, the system implemented on a parking meter, the system comprising:

the second communication module is used for connecting the client based on a near field communication mode;

a parking space information sending module, configured to send parking space information to the client, where the parking space information includes a digital signature of the parking meter, so that the client verifies the digital signature, and executes the following modules after verification:

the system comprises a preset parking time receiving module, a parking fee payment module and a parking fee payment module, wherein the preset parking time receiving module is used for receiving a parking fee payment result and preset parking time input by a user from the client;

the parking fee settlement information acquisition module is used for acquiring parking fee settlement information based on parking start time, parking end time and pre-paid amount, and sending the parking fee settlement information to the client, wherein the parking start time and the parking end time are acquired based on a sensing device of a parking space, and the pre-paid amount is determined based on preset parking time input by the user;

and the subsidy payment result receiving module is used for receiving the subsidy payment result from the client.

10. A computer-readable storage medium, wherein the storage medium stores computer instructions that, when executed by a processor, implement the method of any of claims 1-4 and 8.