A cloud-based parking recommendation system and method

Abstract

A cloud-based parking recommendation system and method are disclosed. The system includes a parking lot terminal, a parking user terminal, and a cloud platform. The method involves a parking user submitting their origin, destination, license plate number, and a request to participate in parking verification, along with their personalized parking needs, to the cloud platform via their terminal. Upon receiving this information, the cloud platform constructs a verification area comprised of multiple parking lots and selects a suitable parking lot in the verification preparation phase for the user. The user then competes for a specific parking verification session within the blockchain system during this verification process. Based on the number of available parking spaces, the absolute value of the difference between the two numbers submitted by each user terminal, and the submission time, the cloud platform selects qualified users as those who have successfully completed the verification. The user then navigates to the selected parking lot using an electronic map. This invention better meets the personalized needs of parking users, solves or alleviates parking difficulties, and avoids related disputes.

Description

Technical Field

[0001] This invention relates to a cloud-based parking recommendation system and method, belonging to the field of intelligent traffic management technology. Background Technology

[0002] In recent years, smart parking has emerged as a product of this need. It primarily uses electronic navigation to guide users to a specific parking lot based on their needs and the availability of the parking facilities. However, because this technology relies on fixed parking lot conditions and user needs, it cannot dynamically adjust to changes in these factors, resulting in poor parking recommendations and a subpar user experience. Summary of the Invention

[0003] The purpose of this invention is to provide a cloud-based parking recommendation system and method that can dynamically adjust to changes in parking lot status and user needs, thereby better meeting user needs, improving user experience, and effectively solving or alleviating parking difficulties.

[0004] To achieve the above objectives, the present invention provides a parking recommendation system based on a cloud platform, including a parking lot terminal, a parking user terminal, and a cloud platform. The parking lot terminal is used to collect the average vehicle speed of the roads near each parking lot at set time intervals, and is also used to collect in real time the time when the verified parking user enters the parking lot, the time when the parking user leaves the parking lot, and their license plate number, and submit the collected data information to the cloud platform.

[0005] The parking user terminal is used to submit requests, departure information and personalized needs information of multiple parking users to participate in the parking verification process to the cloud platform; it is also used to randomly generate multiple random numbers and participate in the parking verification process of the parking blockchain system; it is also used to receive the parking lot location information determined after successful verification sent by the cloud platform; the parking users who have successfully verified their parking experience submit their parking time, license plate number and user evaluation to the cloud platform through the parking user terminal.

[0006] The cloud platform is a blockchain system management terminal used to generate the genesis block of the blockchain for each of the multiple parking lots. The genesis block is the first block in the blockchain. The cloud platform stores the identifier, total number of parking spaces, and charging standard of each parking lot into its genesis block.

[0007] The cloud platform creates buffer zones for each parking lot to temporarily store pre-blocks. A pre-block generation time T is set, which is greater than or equal to 5 minutes and less than or equal to 30 minutes. This time interval is consistent with the time interval at which the parking lot collects the average vehicle speed of roads near each parking lot. A generation difficulty D is set, which is greater than or equal to 10 and less than or equal to 100. Based on the current number of available parking spaces PS, the maximum number N of parking users allowed to wait in the verification preparation state is determined: N = C * PS, where C is a coefficient, greater than 0 and less than 1. The cloud platform also randomly generates multiple target numbers to compare with random numbers generated by parking users.

[0008] When there are available parking spaces in a parking lot, the cloud platform will successively start the verification preparation state and the verification in progress state for that parking lot, and arrange for the parking users to participate in the verification process of different parking lot blockchain systems based on the personalized parking needs of the parking users. When the verification timeout or all available parking spaces are allocated, the cloud platform will end the verification process of that parking lot.

[0009] The cloud platform constructs pre-blocks for each parking user whose verification is successful and temporarily stores them in the buffer. At the appropriate time, the pre-blocks are converted into formal blocks and added to the parking lot's blockchain system.

[0010] The cloud platform is also used to receive, process, and analyze information submitted by parking lots and parking users.

[0011] A cloud-based parking recommendation method, with the following steps:

[0012] Step 1: Parking users set the number of random numbers to be generated on the parking user terminal and submit the departure point, destination, license plate number, and a request to participate in the parking verification to the cloud platform, while also submitting personalized parking requirements.

[0013] Step 2: At set intervals, the cloud platform calculates the number of available parking spaces PS for each parking lot based on the vehicle entry and exit records stored in the blockchain system blocks of each parking lot within its blockchain system management scope; when PS≥1, the corresponding parking lot blockchain system enters the verification preparation state; after the verification preparation state ends, it immediately enters the verification in progress state.

[0014] A blockchain system in the verification preparation stage accepts new parking users within its set time period, while a blockchain system in the verification process refuses to accept new parking users.

[0015] Step 3: After receiving the departure information, parking request verification and personalized parking demand information submitted by the parking user, the cloud platform constructs a set of multiple parking lots within a circular area centered on the parking user's destination and with the farthest distance LD from the parking lot to the destination as the radius. Based on this set, a parking area for parking users is formed, namely the verification area.

[0016] Step 4: For all parking lots within the verification area, the cloud platform, based on the departure information, parking verification request, and personalized parking demand information submitted by the parking user, may encounter three scenarios: unable to select a suitable parking lot from the verification area, only able to select one suitable parking lot, or selecting multiple suitable parking lots. When the cloud platform cannot select a suitable parking lot from the verification area, the parking user adjusts their personalized parking demand on the parking user's end and resubmits the parking verification request to the cloud platform until at least one suitable parking lot is selected. When the cloud platform can only select one suitable parking lot, the parking user is assigned to the verification preparation state of the blockchain system of the selected parking lot. When the cloud platform selects multiple suitable parking lots, the parking user is assigned to the verification preparation state of the blockchain system of the parking lot whose personalized parking demand comes first in the order of their demand.

[0017] Step 5: The cloud platform initiates the verification process of the parking lot blockchain system and randomly generates a target number TN. This target number is sent by the cloud platform to each parking user who has entered the verification preparation state of the parking lot blockchain system. Each parking user generates a corresponding number of random numbers using the number of random numbers set on their user terminal. The user terminal calculates the absolute value of the difference between each user's random number and the target number, and selects the smallest absolute value that is not greater than the generation difficulty D, and submits it to the cloud platform. The parking user corresponding to the selected absolute value can continue to participate in the parking verification.

[0018] If a suitable random number cannot be selected from the random number generated by a parking user, the parking user will not be able to continue participating in this parking verification in the parking blockchain system. However, the user can send a request to participate in the parking verification to the cloud platform again after adjusting the relevant information.

[0019] Step Six: Based on the absolute values ​​submitted by each parking user, the cloud platform first sorts them by value from smallest to largest and by submission time from earliest to latest. Then, based on the number of available parking spaces (PS) in the parking lot, it selects parking users whose numbers are less than or equal to the number of available parking spaces as successful parking users for this verification, granting them the right to park in the corresponding parking lot. The cloud platform uses the parking lot identifier and the license plate number of the successful parking user to form corresponding data records to construct pre-blocks, which are then temporarily stored in the buffer. Simultaneously, the cloud platform sends the parking lot location information to the successful parking user's terminal, allowing the parking user to navigate to the parking lot via an electronic map.

[0020] For parking users whose verification fails, they can send a request to participate in the verification of parking again to the cloud platform after adjusting the relevant information;

[0021] Step 7: When a parking user enters, parks, or leaves the parking lot, the cloud platform stores the time of entry, parking, and departure, along with the user's rating, in the corresponding parking user's record in the pre-block. Once all parking users who successfully completed a certain verification have left the parking lot, the cloud platform converts the pre-block into a formal block and adds it to the corresponding parking lot's blockchain system based on the parking lot identifier in the pre-block. Based on the generated blockchains for each parking lot, the cloud platform can calculate traffic status information related to the parking lot based on the parking information of the parking users recorded in the blocks.

[0022] Furthermore, the personalized parking needs in step one are the main factors influencing user parking, including the distance from the parking lot to the destination, the congestion level near the parking lot, the congestion level inside the parking lot, the parking fee standard, and the parking lot user reviews. The parking user submits the acceptable range of the main factors to the cloud platform through the parking user terminal, which are as follows: the maximum distance from the parking lot to the destination is allowed to be LD, the maximum congestion level near the parking lot is allowed to be NI, the maximum congestion level inside the parking lot is allowed to be SI, the maximum parking fee standard is allowed to be PF, and the minimum user review level of the parking lot is allowed to be PE. The main factors are then ranked according to their importance.

[0023] For a parking lot i within a parking area, assume the cloud platform calculates its congestion level as NI based on the average vehicle speed of roads near the parking lot obtained from the parking lot terminal. i Based on the relevant records stored in the genesis block and the last block of the parking lot blockchain system, the parking fee standard for the parking lot is obtained as PF. i Congestion level SI i The parking lot user rating is PE. i ; when NI i ≤NI and SIi ≤SI and PF i ≤PF and PE i If the parking lot blockchain system is in the verification preparation state and the number of parking users waiting in the verification preparation state does not exceed N, then the parking lot meets the user's personalized parking needs; otherwise, it does not.

[0024] For the average vehicle speed on roads near the parking lot obtained from the parking lot terminal, the cloud platform determines the congestion level according to the set rules. The determination process is as follows: when the average vehicle speed is greater than the threshold PW1, the congestion level is determined to be smooth, denoted as NI. i =1; when the average vehicle speed is greater than the threshold PW2 and less than or equal to PW1, the congestion level is determined to be basically smooth, denoted as NI. i =2; when the average vehicle speed is greater than the threshold PW3 and less than or equal to PW2, the congestion level is determined to be mild congestion, denoted as NI. i =3; when the average vehicle speed is greater than the threshold PW4 and less than or equal to PW3, the congestion level is determined to be moderate congestion, denoted as NI. i =4; when the average vehicle speed is less than or equal to PW4, the congestion level is determined to be severe congestion, denoted as NI. i =5.

[0025] Furthermore, the duration of the verification preparation state in step two is 0.3*T, and the duration of the verification in progress state is 0.7*T. Furthermore, in step seven, based on the parking information of parking users recorded in the block, traffic status information related to the parking lot is calculated, specifically including: judgment of the congestion level in the parking lot, parking lot charging status, parking lot user rating level, statistics of abnormal parking lots, statistics of abnormal parking users, calculation of parking lot traffic flow, and time occupancy rate;

[0026] The method for determining the congestion level in a parking lot is as follows: Subtract the time a vehicle enters the parking lot from the time it finishes parking from the time it finishes parking in each record within the block. This yields the parking time for each vehicle and the average parking time for all vehicles in the block. For parking lot i, the cloud platform determines the congestion level based on the average parking time for all vehicles. The determination rule is: if the average parking time is greater than the threshold PN1, the congestion level is determined to be smooth, denoted as SI. i =1; when the average time is greater than the threshold PN2 and less than or equal to PN1, the congestion level is determined to be basically smooth, denoted as SI. i =2; when the average time is greater than the threshold PN3 and less than or equal to PN2, the congestion level is determined to be mild congestion, denoted as SI. i =3; when the average time is greater than the threshold PN4 and less than or equal to PN3, the congestion level is determined to be moderate congestion, denoted as SI.i =4; when the average travel time is less than or equal to PN4, the congestion level is determined to be severe congestion, denoted as SI. i =5;

[0027] The parking fee information is based on the time a vehicle enters and leaves the parking lot, which is stored in each record in the block. Then, according to the parking fee standard, the parking fee payable for a certain parking time is obtained, and finally the total parking fee collected by the parking lot for any time period can be obtained.

[0028] The parking lot user rating is based on the rating given by parking users in each record in the block, and then the average rating given by all parking users for a certain parking lot in any time period is obtained; the rating includes different numerical levels from 1 to 5, representing very dissatisfied, dissatisfied, somewhat satisfied, satisfied and very satisfied respectively;

[0029] The abnormal parking lot statistics are based on the parking lot vehicle entry and exit records and parking user ratings stored in the block, and then obtain the average number of available parking spaces and the average ratings given by parking users for any time period. If the number of available parking spaces is greater than or equal to ST and the average rating is less than or equal to LT, the parking lot is considered an abnormal parking lot, and relevant departments are alerted to pay attention to the parking lot. The value of ST is less than or equal to the total number of parking spaces in a parking lot and greater than 0. The value of LT is less than or equal to 5 and greater than or equal to 1.

[0030] Abnormal parking users are identified based on the time a vehicle enters the parking lot, the time it is parked, and the time it leaves the parking lot, all of which are stored in each record in the block. This allows us to calculate the time each vehicle spends in the parking lot. If the time spent in parking is greater than or equal to the threshold PPT or the time spent in parking is greater than or equal to the threshold PT, then the parking user is considered an abnormal parking user, and the parking lot management personnel are alerted to pay attention to this user.

[0031] The calculation of parking lot traffic flow is based on the parking lot vehicle entry and exit records stored in the block, and then the average number of vehicles entering and exiting the parking lot in any time period is obtained;

[0032] Time occupancy rate is based on the parking lot vehicle entry and exit records stored in the block, thus obtaining the average parking time of vehicles entering and exiting the parking lot in any time period.

[0033] This invention comprises a parking recommendation system consisting of a parking lot terminal, a parking user terminal, and a cloud platform. The recommendation process is as follows: A parking user sets the number of random numbers to be generated on their parking user terminal and submits their departure point, destination, license plate number, and a request to participate in parking verification to the cloud platform, along with personalized parking requirements. Upon receiving the departure information, parking verification request, and personalized parking requirements submitted by the parking user, the cloud platform constructs a set of multiple parking lots. Based on this set, a parking area, i.e., a verification area, is formed for parking users. The cloud platform selects the parking user with the smaller absolute value of the difference between the two numbers submitted by each parking user terminal and the submission time, based on the number of available parking spaces, the absolute value of the difference between the two numbers submitted by each parking user terminal, and the submission time. The parking user can then navigate to this parking lot via an electronic map. This invention dynamically adjusts parking recommendations based on parking lot status information and users' personalized needs, which can better meet the personalized needs of parking users and effectively solve or alleviate the problem of parking difficulties. By participating in the verification process of the parking lot blockchain system, parking users obtain the right to park in a certain parking lot. This is characterized by fairness and impartiality, which can avoid related disputes. Moreover, the data records stored in the blockchain system are securely stored and efficiently utilized. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of the system structure of the present invention;

[0035] Figure 2 This is a flowchart of the method of the present invention. Detailed Implementation

[0036] The invention will now be further described with reference to the accompanying drawings.

[0037] like Figure 1 As shown, a cloud-based parking recommendation system includes a parking lot terminal, a parking user terminal, and a cloud platform. The parking lot terminal is used to collect the average vehicle speed of the roads near each parking lot at set time intervals. It is also used to collect the time when the verified parking user enters the parking lot, the time when the parking user leaves the parking lot, and the license plate number in real time, and submit the collected data information to the cloud platform.

[0038] The parking user terminal is used to submit requests, departure information and personalized needs information of multiple parking users to participate in the parking verification process to the cloud platform; it is also used to randomly generate multiple random numbers and participate in the parking verification process of the parking blockchain system; it is also used to receive the parking lot location information determined after successful verification sent by the cloud platform; the parking users who have successfully verified their parking experience submit their parking time, license plate number and user evaluation to the cloud platform through the parking user terminal.

[0039] The cloud platform is a blockchain system management terminal used to generate the genesis block of the blockchain for each of the multiple parking lots. The genesis block is the first block in the blockchain. The cloud platform stores the identifier, total number of parking spaces, and charging standard of each parking lot into its genesis block.

[0040] The cloud platform creates buffer zones for each parking lot to temporarily store pre-blocks. A pre-block generation time T is set, which is greater than or equal to 5 minutes and less than or equal to 30 minutes. This time interval is consistent with the time interval at which the parking lot collects the average vehicle speed of roads near each parking lot. A generation difficulty D is set, which is greater than or equal to 10 and less than or equal to 100. Based on the current number of available parking spaces PS, the maximum number N of parking users allowed to wait in the verification preparation state is determined: N = C * PS, where C is a coefficient, greater than 0 and less than 1. The cloud platform also randomly generates multiple target numbers to compare with the random numbers generated by the parking user terminals.

[0041] When there are available parking spaces in a parking lot, the cloud platform will successively start the verification preparation state and the verification in progress state for that parking lot, and arrange for the parking users to participate in the verification process of different parking lot blockchain systems based on the personalized parking needs of the parking users. When the verification timeout or all available parking spaces are allocated, the cloud platform will end the verification process of that parking lot.

[0042] The cloud platform constructs pre-blocks for each parking user whose verification is successful and temporarily stores them in the buffer. At the appropriate time, the pre-blocks are converted into formal blocks and added to the parking lot's blockchain system.

[0043] The cloud platform is also used to receive, process, and analyze information submitted by parking lots and parking users.

[0044] Example:

[0045] like Figure 2 As shown, a parking recommendation method based on a cloud platform includes the following steps:

[0046] Step 1: Parking users set the number of random numbers to be generated on the parking user terminal and submit the departure point, destination, license plate number, and a request to participate in the parking verification to the cloud platform, while also submitting personalized parking requirements.

[0047] Personalized parking needs are the main factors influencing users' parking decisions, including the distance from the parking lot to the destination, congestion near the parking lot, congestion within the parking lot, parking fees, and user reviews of the parking lot. Users submit their acceptable ranges for these main factors to the cloud platform through their parking user app: the maximum distance from the parking lot to the destination is allowed to be LD = 3 kilometers; the maximum congestion level near the parking lot is allowed to be NI = 3; the maximum congestion level within the parking lot is allowed to be SI = 3; the maximum parking fee is allowed to be PF = 20 yuan / hour; and the minimum user review level for the parking lot is allowed to be PE = 3. These main factors are then ranked according to their level of importance.

[0048] For a parking lot i within a parking area, assume the cloud platform calculates its congestion level as NI based on the average vehicle speed of roads near the parking lot obtained from the parking lot terminal. i Based on the relevant records stored in the genesis block and the last block of the parking lot blockchain system, the parking fee standard for the parking lot is obtained as PF. i Congestion level SI i The parking lot user rating is PE. i ; when NI i ≤NI=3 and SI i ≤SI=3 and PF i ≤PF=20 yuan / hour and PE i If ≥PE=3 and the parking lot blockchain system is in the verification preparation state and the number of parking users waiting in the verification preparation state does not exceed N=1.2*PS, then the parking lot meets the user's personalized parking needs; otherwise, it does not.

[0049] For the average vehicle speed on roads near the parking lot obtained from the parking lot terminal, the cloud platform determines the congestion level according to the set rules. The determination process is as follows: when the average vehicle speed is greater than the threshold PW1 = 40 km / h, the congestion level is determined to be smooth, denoted as NI. i =1; when the average vehicle speed is greater than the threshold PW2 = 30 km / h and less than or equal to PW1 = 40 km / h, the congestion level is determined to be basically smooth, denoted as NI. i =2; when the average vehicle speed is greater than the threshold PW3 = 20 km / h and less than or equal to PW2 = 30 km / h, the congestion level is determined to be light congestion, denoted as NI. i =3; when the average vehicle speed is greater than the threshold PW4 = 10 km / h and less than or equal to PW3 = 20 km / h, the congestion level is determined to be moderate congestion, denoted as NI. i =4; when the average vehicle speed is less than or equal to PW410 km / h, the congestion level is determined to be severe congestion, denoted as NI. i =5;

[0050] Step 2: Every 15 minutes, the cloud platform calculates the number of available parking spaces PS for each parking lot based on the vehicle entry and exit records stored in the blockchain system blocks of each parking lot within its blockchain system management scope. When PS≥1, the corresponding parking lot blockchain system enters the verification preparation state, which lasts for 0.3*T=0.3*15=4.5 minutes. After the verification preparation state ends, it immediately enters the verification in progress state, which lasts for 0.7*T=0.7*15=10.5 minutes.

[0051] A blockchain system in the verification preparation stage accepts new parking users within its set time period, while a blockchain system in the verification process refuses to accept new parking users.

[0052] Step 3: After receiving the departure information, parking request verification and personalized parking demand information submitted by the parking user, the cloud platform constructs a set of multiple parking lots within a circular area centered on the parking user's destination and with a radius of LD = 3 kilometers, and forms a parking area for the parking user to park, i.e., the verification area.

[0053] Step 4: For all parking lots within the verification area, the cloud platform, based on the departure information, parking verification request, and personalized parking demand information submitted by the parking user, may encounter three scenarios: unable to select a suitable parking lot from the verification area, only able to select one suitable parking lot, or selecting multiple suitable parking lots. When the cloud platform cannot select a suitable parking lot from the verification area, the parking user adjusts their personalized parking demand on the parking user's end and resubmits the parking verification request to the cloud platform until at least one suitable parking lot is selected. When the cloud platform can only select one suitable parking lot, the parking user is assigned to the verification preparation state of the blockchain system of the selected parking lot. When the cloud platform selects multiple suitable parking lots, the parking user is assigned to the verification preparation state of the blockchain system of the parking lot whose personalized parking demand comes first in the order of their demand.

[0054] Step 5: The cloud platform initiates the verification process of the parking lot blockchain system and randomly generates a target number TN. This target number is sent by the cloud platform to each parking user who has entered the verification preparation state of the parking lot blockchain system. Each parking user sets the number of random numbers to be generated through their parking user terminal and generates a corresponding number of random numbers. The number of random numbers generated can be selected by the user from different quantity levels such as 10, 100, 1000, 5000, and 10000. The parking user terminal calculates the absolute value of the difference between each parking user's random number and the target number, and selects the smallest absolute value of the difference that is not greater than the generation difficulty D=50 and submits it to the cloud platform. The parking user corresponding to the selected absolute value can continue to participate in the parking verification.

[0055] If a suitable random number cannot be selected from the random number generated by a parking user, the parking user will not be able to continue participating in this parking verification in the parking blockchain system. However, the user can send a request to participate in the parking verification to the cloud platform again after adjusting the relevant information.

[0056] Step Six: Based on the absolute values ​​submitted by each parking user, the cloud platform first sorts them by value from smallest to largest and by submission time from earliest to latest. Then, based on the number of available parking spaces (PS) in the parking lot, it selects parking users whose numbers are less than or equal to the number of available parking spaces as successful parking users for this verification, granting them the right to park in the corresponding parking lot. The cloud platform uses the parking lot identifier and the license plate number of the successful parking user to form corresponding data records to construct pre-blocks, which are then temporarily stored in the buffer. Simultaneously, the cloud platform sends the parking lot location information to the successful parking user's terminal, allowing the parking user to navigate to the parking lot via an electronic map.

[0057] For parking users whose verification fails, they can send a request to participate in the verification of parking again to the cloud platform after adjusting the relevant information;

[0058] Step 7: When a parking user enters, parks, or leaves the parking lot, the cloud platform stores the time of entry, parking, and departure, along with the user's rating, in the corresponding parking user's record in the pre-block. Once all parking users who successfully completed a certain verification have left the parking lot, the cloud platform converts the pre-block into a formal block and adds it to the corresponding parking lot's blockchain system based on the parking lot identifier in the pre-block. Based on the generated blockchains for each parking lot, the cloud platform can calculate traffic status information related to the parking lot based on the parking information of the parking users recorded in the blocks.

[0059] Based on the parking information of parking users recorded in the block, traffic status information related to the parking lot is calculated, including the judgment of the congestion level in the parking lot, the charging situation in the parking lot, the user rating level of the parking lot, the statistics of abnormal parking lots, the calculation of traffic flow in the parking lot, and the time occupancy rate.

[0060] The method for determining the congestion level in a parking lot is as follows: Subtract the time a vehicle enters the parking lot from the time it finishes parking from the time it finishes parking in each record within the block. This yields the parking time for each vehicle and the average parking time for all vehicles in the block. For parking lot i, the cloud platform determines the congestion level based on the average parking time for all vehicles. The determination rule is: if the average parking time exceeds the threshold PN1 = 3 minutes, the congestion level is determined to be smooth, denoted as SI. i =1; when the average time is greater than the threshold PN2 = 7 minutes and less than or equal to PN1 = 3 minutes, the congestion level is determined to be basically smooth, denoted as SI. i =2; when the average travel time is greater than the threshold PN3 = 10 minutes and less than or equal to PN2 = 7 minutes, the congestion level is determined to be mild congestion, denoted as SI. i =3; When the average time is greater than the threshold PN4 = 13 minutes and less than or equal to PN3 = 10 minutes, the congestion level is determined to be moderate congestion, denoted as SI. i =4; when the average travel time is less than or equal to PN4 = 13 minutes, the congestion level is determined to be severe congestion, denoted as SI. i =5;

[0061] The parking fee information is based on the time a vehicle enters and leaves the parking lot, which is stored in each record in the block. Then, according to the parking fee standard, the parking fee payable for a certain parking time is obtained. Parking fee = parking fee standard * (time of leaving the parking lot - time of entering the parking lot). Finally, the total parking fee collected by the parking lot for any time period can be obtained.

[0062] The parking lot user rating is based on the rating given by parking users in each record in the block, and then the average rating given by all parking users for a certain parking lot in any time period is obtained; the rating includes different numerical levels from 1 to 5, representing very dissatisfied, dissatisfied, somewhat satisfied, satisfied, and very satisfied respectively;

[0063] The abnormal parking lot statistics are based on the parking lot vehicle entry and exit records and parking user ratings stored in the block, and then obtain the average number of available parking spaces and the average ratings given by parking users for any time period. If the number of available parking spaces is greater than or equal to ST = 0.4 * total number of parking spaces and the average rating is less than or equal to LT = 2, the parking lot is considered to be an abnormal parking lot, and relevant departments are reminded to pay attention to the parking lot.

[0064] Abnormal parking users are identified based on the time a vehicle enters the parking lot, the time it is parked, and the time it leaves the parking lot, all of which are stored in each record in the block. This allows us to calculate the time each vehicle spends in the parking lot. If the parking time of a vehicle is greater than or equal to the threshold PPT = 15 minutes or the parking time of a vehicle is greater than or equal to the threshold PT = 48 hours, then the parking user is considered an abnormal parking user, and the parking lot management personnel can be alerted to pay attention to this user.

[0065] The calculation of parking lot traffic flow is based on the parking lot vehicle entry and exit records stored in the block, and then the average number of vehicles entering and exiting the parking lot in any time period is obtained;

[0066] Time occupancy rate is based on the parking lot vehicle entry and exit records stored in the block, thus obtaining the average parking time of vehicles entering and exiting the parking lot in any time period.

[0067] This invention leverages technologies such as cloud computing and blockchain to guide parking users towards simple and efficient parking. Parking traffic status information stored in the blockchain system is not easily lost or tampered with, and can be used for urban parking management.

Claims

1. A cloud-based parking recommendation system, comprising a parking lot terminal, a parking user terminal, and a cloud platform, characterized in that, The parking lot terminal is used to collect the average vehicle speed of the roads near each parking lot at set time intervals. It is also used to collect the time when the successfully verified parking users enter the parking lot, the time when they leave the parking lot, and their license plate numbers in real time, and submit the collected data information to the cloud platform. The parking user terminal is used to submit requests, departure information and personalized needs information of multiple parking users to participate in the parking verification process to the cloud platform; it is also used to randomly generate multiple random numbers and participate in the parking verification process of the parking blockchain system; it is also used to receive the parking lot location information determined after successful verification sent by the cloud platform; the parking users who have successfully verified their parking experience submit their parking time, license plate number and user evaluation to the cloud platform through the parking user terminal. The cloud platform is a blockchain system management terminal used to generate the genesis block of the blockchain for each of the multiple parking lots. The genesis block is the first block in the blockchain. The cloud platform stores the identifier, total number of parking spaces, and charging standard of each parking lot into its genesis block. The cloud platform creates buffer zones for each parking lot to temporarily store pre-blocks. The generation time T of the pre-blocks is set to be consistent with the interval between the collection of the average vehicle speed of the roads near each parking lot by the parking lot terminal. The generation difficulty D is set, and the maximum number N of parking users allowed to wait in the verification preparation state is determined based on the number of available parking spaces PS of the current parking lot. N = C * PS, where C is a coefficient. The cloud platform is also used to randomly generate multiple target numbers to compare with the random numbers generated by the parking user terminal. When there are available parking spaces in a parking lot, the cloud platform will successively start the verification preparation state and the verification in progress state for that parking lot, and arrange for the parking users to participate in the verification process of different parking lot blockchain systems based on the personalized parking needs of the parking users. When the verification timeout or all available parking spaces are allocated, the cloud platform will end the verification process of that parking lot. The cloud platform constructs pre-blocks for each parking user whose verification is successful and temporarily stores them in the buffer. At the appropriate time, the pre-blocks are converted into formal blocks and added to the parking lot's blockchain system. The cloud platform is also used to receive, process, and analyze information submitted by parking lots and parking users.

2. A method for parking recommendation based on the cloud platform-based parking recommendation system as described in claim 1, characterized in that, The steps are as follows: Step 1: Parking users set the number of random numbers to be generated on the parking user terminal and submit the departure point, destination, license plate number, and a request to participate in the parking verification to the cloud platform, while also submitting personalized parking requirements. Step 2: At set intervals, the cloud platform will calculate the number of available parking spaces PS for each parking lot based on the vehicle entry and exit records stored in the blockchain system blocks of each parking lot within its blockchain system management scope. When PS≥1, the corresponding parking lot blockchain system is activated in the verification preparation state; after the verification preparation state ends, it immediately enters the verification in progress state. A blockchain system in the verification preparation stage accepts new parking users within its set time period, while a blockchain system in the verification process refuses to accept new parking users. Step 3: After receiving the departure information, parking request verification and personalized parking demand information submitted by the parking user, the cloud platform constructs a set of multiple parking lots within a circular area centered on the parking user's destination and with the farthest distance LD from the parking lot to the destination as the radius. Based on this set, a parking area for parking users is formed, namely the verification area. Step 4: For all parking lots within the verification area, the cloud platform, based on the departure information, parking verification request, and personalized parking demand information submitted by the parking user, may encounter three scenarios: unable to select a suitable parking lot from the verification area, only able to select one suitable parking lot, or selecting multiple suitable parking lots. When the cloud platform cannot select a suitable parking lot from the verification area, the parking user adjusts their personalized parking demand on the parking user's end and resubmits the parking verification request to the cloud platform until at least one suitable parking lot is selected. When the cloud platform can only select one suitable parking lot, the parking user is assigned to the verification preparation state of the blockchain system of the selected parking lot. When the cloud platform selects multiple suitable parking lots, the parking user is assigned to the verification preparation state of the blockchain system of the parking lot whose personalized parking demand comes first in the order of their demand. Step 5: The cloud platform initiates the verification process of the parking lot blockchain system and randomly generates a target number TN. The target number is sent by the cloud platform to each parking user who has entered the verification preparation state of the parking lot blockchain system. Each parking user generates a corresponding number of random numbers based on the number of random numbers generated as set by the parking user terminal. The parking user terminal calculates the absolute value of the difference between each parking user's random number and the target number, and selects the one with the smallest absolute value that is no greater than the generation difficulty D and submits it to the cloud platform. The parking user corresponding to the selected absolute value continues to participate in the parking verification. If a suitable random number cannot be selected from the random number generated by a parking user, the parking user will be unable to continue participating in this parking verification in the parking blockchain system. After adjusting the relevant information, the user will send a request to the cloud platform to participate in the parking verification again. Step Six: Based on the absolute values ​​submitted by each parking user, the cloud platform first sorts them by value from smallest to largest and by submission time from earliest to latest. Then, based on the number of available parking spaces (PS) in the parking lot, it selects parking users whose numbers are less than or equal to the number of available parking spaces as successful parking users for this verification, granting them the right to park in the corresponding parking lot. The cloud platform uses the parking lot identifier and the license plate number of the successful parking user to form corresponding data records to construct pre-blocks, which are then temporarily stored in the buffer. Simultaneously, the cloud platform sends the parking lot location information to the successful parking user's terminal, allowing the parking user to navigate to the parking lot via an electronic map. For parking users whose verification fails, after adjusting the relevant information, send the request to participate in the parking verification to the cloud platform again; Step 7: When a parking user enters the parking lot, parks their car, or leaves the parking lot, the cloud platform stores the time the user enters the parking lot, the time the user parks their car, the time the user leaves the parking lot, and the user's rating in the corresponding parking user's record in the pre-block. Once all parking users who have successfully completed a certain verification have left the parking lot, the cloud platform converts the pre-block into a formal block based on the parking lot identifier in the pre-block and adds it to the corresponding parking lot's blockchain system. Based on the generated blockchains of each parking lot, the cloud platform calculates the traffic status information related to the parking lot based on the parking information of the parking users recorded in the blocks.

3. The method for parking recommendation based on a cloud platform according to claim 2, characterized in that, The personalized parking needs in step one are the main factors influencing a user's parking, including the distance from the parking lot to the destination, the congestion level near the parking lot, the congestion level inside the parking lot, the parking fee, and the parking lot user reviews. The parking user submits their acceptable range for the main factors to the cloud platform through the parking user terminal. These ranges are as follows: the maximum distance from the parking lot to the destination is allowed to be LD, the maximum congestion level near the parking lot is allowed to be NI, the maximum congestion level inside the parking lot is allowed to be SI, the maximum parking fee is allowed to be PF, and the minimum user review level of the parking lot is allowed to be PE. The main factors are then ranked according to their importance.

4. The method for parking recommendation based on a cloud platform according to claim 2, characterized in that, The duration of the verification preparation state in step two is 0.3*T, and the duration of the verification in progress state is 0.7*T.

5. The method for parking recommendation in the cloud-based parking recommendation system according to claim 2, characterized in that, In step seven, traffic status information related to the parking lot is calculated based on the parking information of the parking users recorded in the block. Specifically, this includes: judging the congestion level in the parking lot, the charging situation in the parking lot, the user rating level of the parking lot, the statistics of abnormal parking lots, the statistics of abnormal parking users, the calculation of traffic flow in the parking lot, and the time occupancy rate of the parking lot. The method for determining the congestion level in a parking lot is as follows: Subtract the time a vehicle enters the parking lot from the time it finishes parking from the time it finishes parking in each record within the block. This yields the parking time for each vehicle and the average parking time for all vehicles in the block. For parking lot i, the cloud platform determines the congestion level based on the average parking time for all vehicles. The determination rule is: if the average parking time is greater than the threshold PN1, the congestion level is determined to be smooth, denoted as SI. i =1; when the average time is greater than the threshold PN2 and less than or equal to PN1, the congestion level is determined to be basically smooth, denoted as SI. i =2; when the average time is greater than the threshold PN3 and less than or equal to PN2, the congestion level is determined to be mild congestion, denoted as SI. i =3; when the average time is greater than the threshold PN4 but less than or equal to PN3, the congestion level is determined to be moderate congestion, denoted as SI. i =4; when the average time is less than or equal to PN4, the congestion level is determined to be severe congestion, denoted as SI. i =5; The parking fee information is based on the time a vehicle enters and leaves the parking lot, which is stored in each record in the block. Then, according to the parking fee standard, the parking fee payable for a certain parking time is obtained, and finally the total parking fee collected by the parking lot for any time period is obtained. The parking lot user rating is based on the rating given by parking users in each record in the block, and then the average rating given by all parking users for a certain parking lot in any time period is obtained. The abnormal parking lot statistics are based on the parking lot vehicle entry and exit records and parking user ratings stored in the block, and then obtain the average number of available parking spaces and the average ratings given by parking users for any time period. If the number of available parking spaces is greater than or equal to ST and the average rating is less than or equal to LT, the parking lot is considered an abnormal parking lot, and relevant departments are reminded to pay attention to the parking lot. Abnormal parking users are identified based on the time a vehicle enters the parking lot, the time it is parked, and the time it leaves the parking lot, all of which are stored in each record in the block. This allows us to calculate the time each vehicle spends in the parking lot. If the time spent in parking is greater than or equal to the threshold PPT or the time spent in parking is greater than or equal to the threshold PT, then the parking user is considered an abnormal parking user, and the parking lot management personnel are alerted to pay attention to this user. The calculation of parking lot traffic flow is based on the parking lot vehicle entry and exit records stored in the block, and then the average number of vehicles entering and exiting the parking lot in any time period is obtained; Time occupancy rate is based on the parking lot vehicle entry and exit records stored in the block, thus obtaining the average parking time of vehicles entering and exiting the parking lot in any time period.

Images