WO2019052352A1 - 基于车辆检测的泊位服务与管理系统及方法 - Google Patents

基于车辆检测的泊位服务与管理系统及方法 Download PDF

Info

Publication number
WO2019052352A1
WO2019052352A1 PCT/CN2018/103562 CN2018103562W WO2019052352A1 WO 2019052352 A1 WO2019052352 A1 WO 2019052352A1 CN 2018103562 W CN2018103562 W CN 2018103562W WO 2019052352 A1 WO2019052352 A1 WO 2019052352A1
Authority
WO
WIPO (PCT)
Prior art keywords
berth
information
terminal
communication module
vehicle
Prior art date
Application number
PCT/CN2018/103562
Other languages
English (en)
French (fr)
Inventor
徐祎君
徐月明
Original Assignee
路特迩科技(杭州)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 路特迩科技(杭州)有限公司 filed Critical 路特迩科技(杭州)有限公司
Publication of WO2019052352A1 publication Critical patent/WO2019052352A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/14—Traffic control systems for road vehicles indicating individual free spaces in parking areas
    • G08G1/141—Traffic control systems for road vehicles indicating individual free spaces in parking areas with means giving the indication of available parking spaces
    • G08G1/144—Traffic control systems for road vehicles indicating individual free spaces in parking areas with means giving the indication of available parking spaces on portable or mobile units, e.g. personal digital assistant [PDA]
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/14—Traffic control systems for road vehicles indicating individual free spaces in parking areas
    • G08G1/149—Traffic control systems for road vehicles indicating individual free spaces in parking areas coupled to means for restricting the access to the parking space, e.g. authorization, access barriers, indicative lights

Definitions

  • the invention relates to the technical field of intelligent transportation systems, in particular to a berth service and management system and method based on vehicle detection.
  • the status quo of China's traditional parking industry includes four major pain points: large total gap, scattered structure, scattered management, and low level of intelligence. This directly leads to problems such as the difficulty of a user, poor parking experience, low efficiency of parking lot berth transfer and high management costs.
  • Traditional parking lots are unevenly distributed and separated from each other, and a unified network has not yet been formed, resulting in unequal availability of berth information; especially for private berths of many residential communities, institutions and associations, berths are less efficient.
  • the berth and vehicle supply and demand are becoming more and more serious, the inefficient and traditional parking information of traditional parking and service is difficult to meet the driver's army. Riley's high demands for efficient transportation and parking service and management.
  • the use of monitoring, induction, road gates and automatic license plate recognition and other means to achieve intelligent parking and management came into being.
  • the berth sharing is just a good vision; parking lots and berths There is a general lack of restrictive management methods, neglecting the time limit and the prohibition of bans, the unlimited parking, and the simple and ruthless retaliatory and punitive remediation methods have seriously affected the normal parking order and customer experience; All kinds of services and management methods are more or less limited to parking lot owners and driving Or the local or individual interests of the government, while ignoring the interests of the community, non-parking owners or non-drivers, because the parking problems cannot be solved by rules, additional traffic pressure, environmental pollution and resource consumption have infringed more Group interests not related to transportation.
  • the berth reservation method proposed in the invention patent "berriage reservation method and system, berth information service platform” with patent number 201610752210.5 includes: obtaining berth information of the parking lot and parking demand information of the driver, and the berth information includes at least the parking lot.
  • the current landing status information of each berth and the reservation status information; the parking demand information includes at least the target parking area, the expected landing berth date and time, the expected exit berth date and time, and the berth of the parking lot according to the berth information and the parking demand information.
  • the patent has the following problems: 1. The patent realizes the management of the berth based on the reservation of the berth, and is not compatible with the instant parking; 2. The patent cannot be compatible with the non-berth reservation terminal customer; 3.
  • the patent does not perform the berth landing /Exit or fail to follow the actual implementation of the berth landing / exit violation of the lack of supervision and management means; 4.
  • the patent lacks technical guarantee for the immediacy and accuracy of information related to communication lag or communication failure; 5. How to ensure parking There is a lack of thinking about the smooth entrances and exits.
  • the technical problem to be solved by the present invention is to propose a vehicle detection-based berth service and management system that can ensure the immediacy and accuracy of the parking lot information through the design of vehicle detection and communication, thereby realizing the management of the berth in the parking lot. And the method of using the system to realize the service and management of the berth in the parking lot.
  • the present invention provides a berth service and management system based on vehicle detection
  • the berth service and management system includes a cloud server, and an administrator terminal, a driver terminal, a vehicle detection module 1 and a parking law enforcement terminal connected to the cloud server signal; the administrator terminal and the driver terminal are both connected to the vehicle detection module I. Connected to the parking law enforcement terminal signal;
  • the cloud server is configured to receive, store, process, and update all parking lot information, vehicle information, and transaction information;
  • the parking lot information includes berth information, berth status information, berth abnormal information, and gate information of the same parking lot;
  • the berth information includes at least a berth code (geographic location), a berth size, an available time period, and a parking time limit;
  • the berth state information is stored under the berth code, and includes at least a berth code, a berth occupancy state, a time of state change, and a state confidence;
  • the berth abnormality information includes at least a berth abnormal state and a corresponding berth code, and the berth abnormal state includes at least an unsuccessful check-in, an unsuccessful check-out, an overtime parking, a berth failure, and a berth respondent, where the berth is referred to as a berth.
  • the abnormal complaint is in the trial period;
  • the gate information includes vehicle entrance information, vehicle exit information and gate abnormality information, and the vehicle entrance information and the vehicle exit information include at least a parking lot code, a gate code, a license plate number and a corresponding approach/
  • the gate abnormality information includes at least parking Code, gate code, corresponding arrival/exit time and abnormal state;
  • vehicle information includes at least license plate number, and berth demand information, berth reservation information, parking information and vehicle respondent saved under the license plate number, the vehicle is
  • the berth demand information includes at least a destination name, a license plate number, a planned parking start time, and a parking length;
  • the berth reservation information includes at least the reserved berth code and the license plate number. , the planned parking start time and the length of parking;
  • the parking information includes at least the license plate number, the berth code, the time of signing in the berth and the time of checking out the berth;
  • the administrator terminal is configured to upload berth information to the cloud server, monitor berth status information and gate information, process abnormal status, and notify the administrator in time; the administrator assists the driver to make an appointment berth, change or cancel, and open the gate through the administrator terminal.
  • the cloud server will gate Information, berth status information, berth reservation information, and transaction information are synchronized to the administrator terminal;
  • the check-in berth refers to the driver expressing the parking intention, accepting the parking service and management terms, and confirming the report or action of the parking start,
  • Check-out berth means the driver acknowledges the parking fact, accepts the parking service and management terms, and confirms the report or action of the parking termination;
  • the driver terminal is configured to send berth demand information to the cloud server, perform berth reservation and change, and also perform operations for opening a gate, signing a berth, checking out a berth, paying a fee, and extending the parking time, and discovering a berth abnormal state. Collect evidence and send it to the administrator terminal or parking law enforcement terminal for reporting, complaints or reporting; the cloud server synchronizes berth demand information, berth reservation information, entry and exit information, parking information and transaction information to the driver terminal;
  • the vehicle detection module 1 is configured to detect a berth occupancy status, and send berth status information to the cloud server, the administrator terminal, and the driver terminal;
  • the parking law enforcement terminal is used for monitoring the illegal parking; the parking law enforcement terminal can query the parking information of any berth, and the parking information is compared with the actual vehicle staying state, and the illegal vehicle is forensic, registered and Processing; the parking enforcement terminal is also capable of receiving, storing, and processing complaints or reporting information from the administrator terminal and the driver terminal, and processing the offending vehicle after verifying the complaint or reporting the information.
  • the berth service and management system further includes a vehicle detection module II, a vehicle detection module III and a gate communication module; the gate communication module is respectively associated with a vehicle detection module II, a vehicle detection module III, a cloud server, an administrator terminal, and a driver terminal Signal connected
  • the vehicle detection module II is configured to detect location information of the vehicle and the gate, and send the vehicle proximity information to the gate communication module, the administrator terminal, and the driver terminal;
  • the vehicle detection module III is configured to detect position information of the vehicle and the gate, and send the vehicle passage information to the gate communication module;
  • the gate communication module is configured to receive vehicle proximity information sent by the vehicle detection module II, vehicle passage information sent by the vehicle detection module III, and an opening command and a license plate number from the administrator terminal or the driver terminal; the gate communication module will license the license plate
  • the gate number, the parking lot code and the gate code are bound to open the gate; the gate communication module sends the arrival information, the exit information and the gate abnormality information of the vehicle in the corresponding parking lot to the cloud server, and the cloud server will correspond to the entry of the vehicle in the parking lot.
  • the information, the exit information, the check-in information and the check-out information are synchronized to all the gate communication modules of the same parking lot code.
  • the administrator terminal includes an administrator PC terminal and an administrator APP having a camera function (that is, the administrator APP implements photo/video collection through a camera provided by the mobile terminal where the administrator is located);
  • the driver terminal includes a driver PC terminal and a driver APP having an imaging function (ie, the driver APP implements photo/video collection through a camera provided by the mobile terminal where the driver is located);
  • the administrator APP/driver APP collects the license plate number and the vehicle violation evidence through the camera function (the administrator APP/driver APP captures and automatically recognizes the license plate number through the camera provided by the mobile terminal where it is located, thereby realizing the collection of the license plate number. );
  • the vehicle detection module I is located on the berth, including the vehicle detection sensor I, the terminal communication module I and the cloud communication module I connected in sequence;
  • the berth service and management system further includes a berth relay module connected to the administrator APP, the driver APP, the cloud communication module I, and the cloud server, and the berth relay module is located at the parking lot pedestrian entrance and exit for relaying and
  • the amplified signal, the administrator APP, the driver APP, and the cloud communication module I are all connected to the cloud server signal through the berth relay module;
  • the vehicle detection module II and the vehicle detection module III are located on both sides of the gate.
  • the vehicle detection module II includes a vehicle detection sensor II, a terminal communication module II and a cloud communication module II connected in sequence;
  • the vehicle detection module III includes a connected vehicle detection sensor.
  • the vehicle detection sensor I, the vehicle detection sensor II and the vehicle detection sensor III are both used for detecting the approach of the vehicle;
  • the vehicle detection sensor I transmits the detected berth occupancy status to the terminal communication.
  • the terminal communication module I sends the berth status information to the cloud communication module I;
  • the vehicle detection sensor II sends the gate status to the terminal communication module II, and the terminal communication module II transmits the vehicle proximity information to the gate communication module through the cloud communication module II
  • the vehicle detection sensor III sends the gate status to the terminal communication module III, and the terminal communication module III transmits the vehicle passing information to the gate communication module through the cloud communication module III;
  • the gate communication module receives a gate enable command from the cloud communication module II, a gate enable of the cloud communication module III, and a gate command from the driver terminal or the administrator terminal, and sends the gate information to the cloud server;
  • the terminal communication module I and the terminal communication module II are respectively connected to the administrator APP and the driver APP signal; the terminal communication module I is used to send berth status information and reception to the administrator APP and the driver APP and the cloud communication module I. Berth reservation information, check-in berth and check-out berth; cloud communication module I is used to send parking information and berth status information to the cloud server through the berth relay module; the terminal communication module II is used for the administrator APP and the driver The APP sends the gate vehicle approach information and the receiving gate command; the cloud communication module II is further configured to send a gate enable command to the gate communication module, and the gate communication module controls the gate to open and send the gate information to the cloud server.
  • the gate communication module comprises a terminal communication module V, and a cloud communication module V, a gate display module and a drive module both connected to the terminal communication module V, and the drive module is connected with the cloud communication module V and the gate signal;
  • the berth relay module includes a connected terminal communication module IV and a cloud communication module IV;
  • the terminal communication module V and the terminal communication module IV are both connected to the administrator APP and the driver APP signal;
  • the cloud communication module V is respectively connected to the cloud server, the cloud communication module II, the cloud communication module III, the cloud communication module IV, and other cloud communication module V signals;
  • the cloud communication module IV is respectively connected to the cloud server, the cloud communication module I, the cloud communication module V, and other cloud communication module IV signals;
  • the berth code and the berth occupancy state are written into the corresponding terminal communication module I in advance; the gate code and the vehicle proximity information are written in advance to the corresponding terminal communication module II; the gate code and the vehicle pass information are written into the corresponding terminal communication in advance Module III;
  • the cloud communication module I periodically sends heartbeat information to the cloud server through the cloud communication module IV, and confirms that the vehicle detection module I and the berth relay module work normally; the cloud communication module II and the cloud communication module III both pass the cloud communication module V timing. Send heartbeat information to the cloud server to confirm that the vehicle detection module II, the vehicle detection module III, and the gate communication module work normally;
  • the heartbeat information includes a device identifier of the corresponding module, an abnormality record of the state change, a clock, a temperature, and a battery remaining amount; the device identifier includes a berth code, a gate code, or a module code;
  • the cloud server When the heartbeat information is abnormal, the cloud server periodically sends a management command to the cloud communication module IV and the cloud communication module V, or sends a device abnormality information to the administrator APP and the administrator PC terminal to prompt maintenance or replacement.
  • the vehicle detecting sensor 1, the vehicle detecting sensor II and the vehicle detecting sensor III adopt a geomagnetic sensor, an infrared sensor, an ultrasonic sensor or a camera;
  • the camera is also used to automatically identify the license plate number (the berth status information, the gate information also includes the license plate number);
  • the terminal communication module I, the terminal communication module II, the terminal communication module III, the terminal communication module IV and the terminal communication module V adopt a Bluetooth communication module (as the technology develops, the Bluetooth communication may be replaced by other similar communication methods, the same below);
  • the cloud communication module I, the cloud communication module II, the cloud communication module III, the cloud communication module IV and the cloud communication module V adopt the LORA communication module (as the technology develops, the Lora communication may be replaced by other similar communication methods, the same below).
  • the present invention also provides a berth service and management method based on vehicle detection
  • berth information release the administrator or berth owner publishes the berth information on the cloud server through the administrator terminal;
  • the berth information includes at least a berth code (geographic location), a berth size, an available time period, and a parking time limit;
  • berth reservation information acquisition the driver uploads the berth demand information to the cloud server through the driver terminal, and the berth demand information includes at least the destination name, the license plate number, the planned parking start time and the parking time; the cloud server will The received berth demand information is matched with the berth information. The successfully matched berth is fed back to the driver through the driver terminal. The driver selects the appropriate berth through the driver terminal and confirms the reservation. At this time, the cloud server separately reports to the administrator terminal and the driver. The terminal feeds back berth reservation information; the berth reservation information includes at least a berth code, a license plate number, a planned parking start time, and a parking time length;
  • berth occupancy status detection When the vehicle enters or leaves the berth, the vehicle detection module I located on the berth detects that the berth occupancy status changes, and at this time, the vehicle detection module I sends to the administrator terminal, the driver terminal and the cloud server.
  • Berth status information includes at least berth code, berth occupancy status, and time of status change (when the vehicle detection module 1 can automatically recognize the license plate number, the berth status information further includes a license plate number);
  • check-in berth When the vehicle enters the berth, the driver terminal receives the berth status information sent by the vehicle detection module I in step 1.3), the driver terminal gives a welcome message to the driver, displays the berth code and requests the driver When the driver confirms the check-in berth, the driver terminal first sends the license plate number to the vehicle detection module I, and then the driver terminal and the vehicle detection module I both send the check-in information to the cloud server, and the check-in information includes at least Corresponding to the berth code, the license plate number, the check-in berth time, the parking time and the planned parking end time; the cloud server receives the check-in information and queries the corresponding berth reservation information according to the license plate number in the check-in information, and the berth reservation information is The berth code is compared with the berth code in the check-in information, and the time period in which the planned parking start time and the parking time are added in the berth reservation information is compared with the time of checking
  • the vehicle detection module I sends the berth status information to the administrator terminal, the driver terminal and the cloud server, and the cloud server unbinds the license plate number and the berth code after receiving the berth status information, and sends the unbinding information to the driving.
  • the driver terminal After receiving the unbinding information, the driver terminal sends a berth checkout success message and sends a message to the driver;
  • the cloud server prompts the administrator berth abnormal information through the administrator terminal, and the administrator patrols, collects and processes the berth through the administrator terminal;
  • the berth abnormal information includes at least the berth abnormal state and the corresponding berth code, and the berth abnormal state is at least This includes unsuccessful signing of berths, unsuccessful checkout of berths and overtime parking.
  • the berth service and management method further includes a berth service and management method for a parking lot provided with a gate control mechanism;
  • the door control mechanism includes a connected gate communication module and a gate;
  • the specific steps include:
  • Gate state detection There is a gate communication module at the gate and a vehicle detection module II and a vehicle detection module III respectively located on both sides of the gate; the gate communication module is respectively connected with the vehicle detection module II and the vehicle detection module III; When the vehicle approaches the gate, the vehicle detection module II detects that there is a vehicle at the gate and transmits vehicle proximity information to the administrator terminal and the driver terminal respectively; the vehicle proximity information includes at least a parking lot code, a gate code, and an approach/play time.
  • the vehicle detection module III detects the passage of the vehicle at the gate, and the vehicle detection module III transmits the vehicle passage information to the gate communication module; the vehicle passage information includes at least the parking lot code, the gate code, and the approach/exit time, and the gate communication module receives After the vehicle passes the information, the control gate is closed;
  • the driver terminal When the vehicle enters the parking lot, the driver terminal receives the vehicle approach information sent by the vehicle detection module II in step 2.1) at the entrance gate, and the driver terminal gives a welcome speech to the driver. Displaying the parking lot code and the gate code, and prompting the driver to perform the opening operation; when the driver performs the opening operation through the driver terminal, the driver terminal first transmits the license plate number information to the vehicle detecting module II, and then the driver terminal and the vehicle
  • the detecting module II respectively sends a opening command, a opening enable command and a license plate number information to the gate communication module; the gate communication module receives the opening command, the opening enable command and the license plate number information, and then the gate is opened; the gate is opened.
  • the gate communication module sends the vehicle entrance information to the cloud server;
  • the vehicle entrance information includes the parking lot code, the gate code, the license plate number, and the approach time;
  • the cloud server receives, stores, and updates the vehicle entry information, and then goes to the same All gate communication modules under the parking lot code send corresponding vehicle arrival information;
  • the driver terminal receives the vehicle approach module II in the step 2.1) to send the vehicle proximity information, and the driver terminal sends a message to the driver to display the parking.
  • Field coding, gate coding and prompting the driver to perform the opening operation when the driver performs the opening operation through the driver terminal, the driver terminal first transmits the license plate number information to the vehicle detection module II, and then the driver terminal and the vehicle detection module II respectively Sending the opening command, opening enable command and license plate number information to the gate communication module; after the gate communication module receives the opening command, the opening enable command and the license plate number information, the vehicle entry information and the checkout information are obtained through the license plate number.
  • the gate communication module turns on the gate according to the opening enable command of the vehicle detection module II and the opening command of the driver terminal; After being turned on, the gate communication module sends the vehicle exit information to the cloud server; the exit information includes a parking lot Code, gate code, license plate number and playing time; after receiving, storing and updating the above information, the cloud server sends corresponding vehicle exit information to all gate communication modules under the same parking lot code.
  • the cloud server queries the berth reservation information by checking the license plate number in the check-in information, and the driver terminal prompts the driver to confirm the berth code and the default parking.
  • the driver can change the parking time to execute the check-in berth; the cloud server queries the berth code to check if the corresponding berth is available, the berth is available, indicating that the berth is not reserved, and the parking time of the berth is checked.
  • the available time period and parking time limit specified in the berth information are met; otherwise, the cloud server 1 prompts the signing failure through the driver terminal, reserves other available berths, and moves the vehicle away from the berth.
  • the berth status information in the step 1.3) further includes a state confidence
  • Step 1.3.1) When the vehicle enters the berth, the vehicle detection module I detects that the berth occupancy status changes, and the vehicle detection module I sends the berth status information to the administrator terminal, the driver terminal and the cloud server;
  • the occupancy status of the berth is car, and the state confidence is the initial value (50%); when the driver successfully signs in the berth, the cloud server increases the state confidence (100%); the berth occupancy state keeps the vehicle in place, and the state confidence
  • the cloud server 1 prompts the administrator berth abnormal information through the administrator terminal, and the administrator can go to the site according to the berth code to assist the driver to check in the berth or prompt the driver to The vehicle moves away from the berth;
  • Step 1.3.2 When the driver confirms the checkout of the berth, the cloud server receives the checkout information and resets the state confidence to the initial value (50%); when the vehicle leaves the berth, the cloud server receives the berth sent by the vehicle detection module I In the status information, the berth occupancy status is no car. At this time, the cloud server once again increases the state confidence level (100%) and updates the berth status information; the driver confirms the checkout berth, and the state confidence does not increase within the prescribed time limit. The cloud server prompts the administrator berth abnormal information through the administrator terminal, and the administrator can go to the scene according to the berth code to prompt the driver to move the vehicle away from the berth;
  • the cloud server When the vehicle exceeds the parking time defined by the check-in information and there is no check-out information, the cloud server prompts the administrator berth abnormal information through the administrator terminal, and the administrator can query the berth according to the berth code and the berth corresponding berth reservation information.
  • the code is adjusted to other available berths;
  • the cloud server When the vehicle leaves the berth, the cloud server receives the berth status information sent by the vehicle detection module I, the berth occupancy status is no car, and when the berth information is not checked out within the specified time limit, the cloud server prompts the administrator through the administrator terminal.
  • the berth abnormal information the administrator can go to the scene according to the berth code to confirm and replace the berth in the driver's check-in or contact the driver to check out the berth according to the check-in information;
  • the administrator When the administrator goes to the berth code site and confirms the berth abnormality information, the administrator adjusts the berth status information through the administrator terminal to be consistent with the actual situation;
  • the evidence can be collected by the administrator terminal, and the collected evidence is sent to the parking law enforcement terminal for reporting;
  • the driver finds the abnormal state of the berth, and can collect the evidence through the driver terminal. And send the collected evidence to the administrator terminal for reporting, or send it to the parking law enforcement terminal for reporting;
  • the gate communication module When there is a vehicle approaching the gate and the gate operation is not successfully performed, the gate communication module sends the gate abnormality information to the cloud server; the administrator terminal receives the gate abnormality information and rushes to the gate to be processed according to the gate code in the gate information.
  • the administrator terminal includes an administrator APP and an administrator PC terminal;
  • the driver terminal includes a driver APP and a driver PC terminal;
  • the administrator can use the administrator APP to replace the user to upload the berth demand information to the cloud server, obtain the berth reservation information, check in the berth, check out the berth, collect the parking fee and execute the opening. command;
  • Non-driver APPs Users of non-driver APPs can complete the corresponding operations through the driver's PC terminal (such as booking a berth, but signing in the berth and checking out the berth must be done by a remote colleague, friend or relative), or the administrator can replace the user through the administrator APP. Check in berths, check out berths, and execute open orders.
  • the invention can ensure the immediacy and accuracy of the parking lot information through the design of vehicle detection and communication;
  • the invention can be compatible with driver terminal customers and non-driver terminal customers, and is also compatible with reserved parking and instant parking;
  • the present invention provides a basic tool for berth sharing services
  • the invention combines parking time limit and license management to improve berth transfer efficiency
  • the invention can ensure the smooth entrance and exit through the design of vehicle detection, communication and process
  • the invention can implement legal supervision and management by performing the operation of forensic and reporting by the administrator or other driver for not performing the check-in berth/check-out berth or the illegal execution of the check-in berth/check-out berth. means.
  • FIG. 1 is a schematic diagram of module connection of a berth service and management system based on vehicle detection according to the present invention
  • FIG. 2 is a schematic diagram of module connection of the vehicle detection module I4 of FIG. 1;
  • FIG. 3 is a schematic diagram of module connection of the vehicle detection module II5 of FIG. 1;
  • FIG. 4 is a schematic flow chart of an appointment berth of a berth service and management method based on vehicle detection according to the present invention
  • FIG. 5 is a schematic flow chart of opening a parking lot of a parking lot based on a berth service and management method for vehicle detection according to the present invention
  • FIG. 6 is a schematic flow chart of a departure parking lot opening according to a berth service and management method for vehicle detection according to the present invention
  • FIG. 7 is a schematic flow chart of a check-in berth of a berth service and management method based on vehicle detection according to the present invention.
  • FIG. 8 is a schematic flow chart of the check-out berth of the berth service and management method based on vehicle detection according to the present invention.
  • Embodiment 1 a berth service and management system based on vehicle detection, as shown in FIG. 1-3, including a cloud server 1, an administrator terminal 2, a driver terminal 3, a vehicle detection module I4, a vehicle detection module II5, and a vehicle
  • the vehicle detection module I4 is connected to the cloud server 1 signal, or is connected to the cloud server 1 through the berth relay module 8;
  • the vehicle detection module III is connected to the cloud server 1 through the gate communication module 6;
  • the gate communication module 6 is connected with the gate to form a gate control mechanism.
  • Cloud Server 1 for receiving, storing, processing and updating all parking lot information, vehicle information, transaction information and heartbeat information;
  • the parking lot information includes berth information, berth status information, berth abnormal information, gate information and remaining available berth information of the same parking lot; berth information includes at least berth code (geographic location), berth size, available time period and parking time limit; In case, the berth information also includes free/private parking time or date, license type and requirements, charging policy, terms of use and penalties; berth status information is stored under berth code, including at least berth code, berth occupancy status and status change
  • the berth abnormality information includes at least the berth abnormal state and the corresponding berth code, and the berth abnormal state includes at least unsuccessful check-in, unsuccessful check-out, overtime parking, berth failure, and berth respondent, wherein the berth is referred to as a berth
  • the abnormal complaint is in the trial period;
  • the gate information includes vehicle entry information (parking code, gate code, license plate number and approach time), vehicle exit information (parking code, gate code, license plate number
  • gate abnormal information includes at least Parking lot code, gate code, corresponding arrival/exit time and abnormal status.
  • the gate abnormality information may also include the license plate number; the remaining available berth information is in the parking lot during the planned parking time of the vehicle (plan Parking start time and planned parking end time) The total number of berths for parking or instant parking and the berth information for the corresponding berth.
  • a checked-in berth means that the driver expresses the willingness to park, accepts the parking service and management terms, and confirms the report or action of the start of the parking.
  • the checked-out berth refers to the driver's acknowledgement of the parking fact, acceptance of the parking service and management terms, confirmation Report or action of termination of parking; vehicle information includes at least the license plate number, berth demand information stored under the license plate number, berth reservation information, parking information and vehicle respondent; vehicle respondent means that the vehicle is being tried for abnormal complaints During the period; the berth demand information includes at least the destination name, the license plate number, the planned parking start time and the parking time; the berth reservation information includes at least the reserved berth code, the license plate number, the planned parking start time and the parking time; parking The information includes at least the license plate number, the berth code, the check-in berth time, and the check-out berth time.
  • the transaction information includes at least information such as berth code, license plate number, date and time, parking fee, and penalty fee.
  • the heartbeat information is used to implement monitoring and maintenance of various hardware devices (including the vehicle detection module I4, the vehicle detection module II5, the vehicle detection module III, the gate communication module 6, and the berth relay module 8) in the berth service and management system of the present invention,
  • the monitoring and maintenance of the above hardware devices may vary depending on the environment, power supply mode, and fault characteristics of the device.
  • the berth vehicle detection module 4 is taken as an example.
  • the heartbeat information includes an abnormal state record, clock, temperature, and battery margin. In the specification, only the relevant heartbeat information of the vehicle detection module 4 is described in detail.
  • the heartbeat information of the vehicle detection module I4 includes at least the berth code corresponding to the vehicle detection module I4 (ie, the device identification, which may also be the gate code or module number corresponding to the device), and the state change abnormal record of the module, the clock, the temperature, and the battery.
  • the abnormality occurs, that is, the cloud server 1 does not receive the heartbeat information within the specified period.
  • the cloud server 1 sends a management command to the abnormal module to process and update, and the cloud server 1 sends the device abnormality to the administrator terminal 2 when the abnormality remains unresolved.
  • the administrator terminal 2 is used to edit and announce the berth information to the cloud server 1, and the cloud server 1 synchronizes the gate information, the berth status information, the berth reservation information, the parking information, the transaction information and the berth respondent information to the administrator terminal 2;
  • the administrator terminal 2 includes an administrator APP (mobile terminal) and an administrator PC terminal (computer terminal), wherein the administrator APP is used for berth site management, mainly including opening a gate and identifying a license plate, viewing parking lot water flow and transaction information, and berths.
  • Plan and berth status information used to assist the driver to reserve berths, change or cancel, check in berths, check out berths and complete on-site transactions, etc., and also to take pictures to collect evidence when berth abnormal conditions occur, and The evidence is sent to the parking law enforcement terminal 7 for reporting, and then the abnormality is corrected;
  • the parking lot water includes the gate code, the license plate number, the corresponding vehicle entry and exit time, and the berth code, the license plate number of the corresponding berth parking vehicle, and the check-in berth and the check-out berth.
  • Time including advance, delay, extension, cancellation, and berth redistribution
  • administrator PC End can be used to edit and publish berth information, and view parking water, transaction information, berths and berths plan view of status information;
  • the driver terminal 3 includes a driver APP (mobile terminal) and a driver PC terminal (computer terminal) for submitting berth demand information to the cloud server 1, signing in berths, checking out berths, searching and making reservations, and changing And cancel, after receiving the reservation, receiving the berth reservation information sent by the cloud server 1; wherein the driver APP can be used to send a gate command to the gate of the parking gate to realize the autonomous approach and exit, when the berth abnormal state or the illegal vehicle is found It is also used for photographing to collect evidence and send it to the administrator terminal 2 or the parking law enforcement terminal 7 for reporting; the cloud server 1 synchronizes the remaining available berth information, berth reservation information, parking information, transaction information and vehicle respondent information to Driver terminal 3.
  • a driver APP mobile terminal
  • driver PC terminal computer terminal
  • the vehicle detection module I4 is located on the berth, as shown in FIG. 2, and includes a vehicle detection sensor I40, a terminal communication module I41 and a cloud communication module I42 connected in sequence; the vehicle detection sensor I40 is used to detect the occupant occupancy state (with/without car) And transmitting the status change result to the terminal communication module I41; the terminal communication module I41 sends the berth status information to the cloud communication module I42, the administrator APP and the driver APP; the berth occupancy status and the berth code in the berth status information are written in advance
  • the vehicle detection sensor I4, and the software of the terminal communication module I41 and the cloud communication module I42 can be upgraded through the terminal communication module I41; the berth occupancy status includes two states: car and no car, and the state change abnormal record is stored in the terminal communication module I41.
  • the driver APP can check the berth code and parking, and the driver APP sends the check-in information to the terminal communication module I41 and records it in the terminal communication module I41; after that, the driver APP communicates with the cloud.
  • Module I42 communicates to the cloud server through its own communication 1 Send the check-in information and send the check-in information in different communication methods to improve the confidence of the berth status information.
  • the berth relay module 8 includes a connected terminal communication module IV and a cloud communication module IV.
  • the berth relay module 8 further includes an Ethernet module I connected to the terminal communication module IV; the berth relay module 8 is used for improving communication. Stability and reduce the communication pressure of the vehicle detection module 4 to improve its energy management.
  • the Ethernet module I allows the LAN to be built between the berth relay modules 8 of the same parking lot to further improve the stability and communication rate of the system within the local area network;
  • the terminal communication module IV can assist the driver to realize the normal check-in berth and the check-out berth operation through the berth relay module 8, and can also perform monitoring, maintenance and software upgrade on the device.
  • the berth relay module 8 may not be used in the on-street parking lot or the open-air parking lot with good communication environment, and the cloud communication module I42 directly communicates with the cloud server 1.
  • the cloud communication module I42 is connected to the cloud server 1 through the berth relay module 8 (one or more) and the LORA communication or Ethernet communication, and the cloud communication module I42 receives the parking sent by the terminal communication module I41.
  • the vehicle information ie, the check-in information and the check-out information
  • the terminal communication module I41 establishes communication with the driver APP and the administrator APP via Bluetooth, and the cloud communication module IV establishes contact with the cloud communication module I42 and the cloud server 1 through the LORA communication respectively, and the Ethernet module I and other berths under the same parking lot
  • the Ethernet module I of the module 8, the Ethernet module II of the gate communication module 6, and the local server establish LAN communication.
  • the berth relay module 8 is installed in a parking lot distribution center suitable for LORA communication, such as an elevator lobby of an underground parking lot, on the one hand, it is convenient to establish communication communication with the cloud communication module I42 at the berth site, and on the other hand, the situation of berth site communication failure At this time, the driver can check in the berth in the elevator lobby where the communication signal is more smooth and the berth relay module 8 is used.
  • the cloud communication module I42 also periodically sends heartbeat information to the cloud server 1 through the berth relay module 8 (ie, the cloud communication module IV), thereby implementing management and maintenance of the device.
  • the vehicle detection module II5 and the vehicle detection module III are located on both sides of the gate.
  • the vehicle detection module II5 includes a connected vehicle detection sensor II50, a terminal communication module II51, and a cloud communication module II52.
  • the vehicle detection sensor II50 is used for detection.
  • the status of the gate is sent to the terminal communication module II51; the terminal communication module II51 receives the information and sends the vehicle proximity information to the administrator APP and the driver APP.
  • the driver APP After receiving the vehicle approach information sent by the terminal communication module II51, the driver APP sends a welcome message to the driver and prompts the opening operation, and the driver can operate the “open gate” command through the driver APP to confirm the parking lot code and the entry/exit.
  • the driver APP sends the opening command, the gate code and the license plate number to the terminal communication module II51 and the gate communication module 6, respectively; wherein the driver APP sends the opening command, the license plate number and the gate code to the gate communication module 6, the gate communication Module 6 saves its license plate number to the queue to be opened; after the driver APP sends the opening command, license plate number and gate code to the terminal communication module II51, the terminal communication module II51 sends the gateway communication module II52 to the gate communication module 6 through the cloud communication module II52.
  • the license plate number, the gate code and the opening enable command; the gate communication module 6 compares the opening command from the cloud communication module II52 with the opening command from the driver APP, and after opening the corresponding gate, Preventing the erroneous operation of the plurality of vehicles, that is, avoiding the situation that the vehicle that issued the opening command does not correspond to the vehicle entering/exiting the parking lot .
  • the vehicle approach information is written in advance to the terminal communication module II51.
  • the vehicle detection module III includes a vehicle detection sensor III, a terminal communication module III and a cloud communication module III connected in sequence; the vehicle detection sensor III is used for detecting the gate state, and sends the state change result to the terminal communication module III; the terminal communication module III receives After that, the cloud communication module III sends the vehicle passing information to the gate communication module 6 to realize the automatic closing of the gate.
  • the vehicle is previously written into the corresponding terminal communication module III by means of information.
  • the gate communication module 6 includes a terminal communication module V, and a cloud communication module V, a gate display module and a drive module both connected to the terminal communication module V signal, wherein the drive module is connected with the gate to control the switch of the gate;
  • the gate communication module 6 further includes an Ethernet module II connected to the terminal communication module V signal, and the Ethernet module II under the same parking lot code, the Ethernet module I of the berth relay module 8, and the local server jointly establish a LAN Ethernet. Communication further improves the communication speed and gate efficiency within the local area network, ensuring the immediacy and accuracy of the parking service and management system of the present invention.
  • the gate display module is used to display the parking lot name, the gate code and the remaining available berth information. When the vehicle approaches and the gate is opened, the license plate number and the welcome information are simultaneously displayed or switched. When the vehicle passes and the gate is closed, the display is simultaneously or switched. License plate number and farewell words.
  • the driver APP and the administrator APP respectively send a command to open the terminal communication module II51 and the terminal communication module V, and the working contents are the same when the driver APP or the administrator APP is opened. Only the driver APP opening operation is described in detail; the terminal communication module II51 receives the opening command and sends a switch enable command to the cloud communication module V through the cloud communication module II52, and the cloud communication module V receives and sends it to the driver.
  • the terminal communication module V sends the open command received by the terminal to the driving module, and the driving module obtains the opening command and the opening enable command with the same license plate number, and drives the corresponding gate to open; the terminal communication module at this time V records the vehicle entrance information, and sends the vehicle arrival information to the cloud server 1 through the cloud communication module V.
  • the cloud server 1 records the vehicle admission information, and synchronizes the vehicle admission information to all cloud communication modules under the same parking lot code. V; the vehicle entry information in this embodiment can also implement vehicle entry information through the Ethernet module II. Quick synchronization.
  • the terminal communication module V determines whether the vehicle exit condition is satisfied according to the stored vehicle entry information and parking information of the corresponding vehicle; when the exit condition is met, the terminal communication module V will open the command and the license plate number. After being sent to the drive module, the drive module obtains the opening command and the opening enable command with the same license plate number, and the control gate is opened. At this time, the terminal communication module V records the vehicle exit information, and the terminal communication module V transmits the vehicle exit information to the cloud server 1 through the cloud communication module V, and the cloud server 1 records the vehicle exit information, and synchronizes the vehicle exit information to the same parking lot code.
  • All the cloud communication modules V when the exit condition is not satisfied, the terminal communication module V does not send the open command to the drive module and records the gate abnormality information, and the terminal communication module V sends the gate abnormality information to the cloud server 1 through the cloud communication module V,
  • the cloud server 1 records the gate abnormality information, and feeds back the gate abnormality information to the driver APP and the administrator APP, thereby providing the driver with a clear instruction or prompting the administrator to timely dispose according to the actual situation; in this embodiment, the vehicle exit information or the gate abnormality is abnormal.
  • Information can also be used to quickly synchronize vehicle presence information via Ethernet Module II.
  • the driving module drives the gate to close according to the vehicle passing information sent to the cloud communication module V through the cloud communication module V.
  • the driving module receives the same opening license enable command and the opening command to obtain the license plate number. It can be invalidated and the gate is re-opened until the new automatic closing is enabled and the gate is completely closed to avoid interference between the vehicle and the gate when the traffic is large.
  • the cloud communication module II and the cloud communication module III respectively send heartbeat information to the cloud server through the gate communication module 6 (ie, the cloud communication module V), and confirm that the vehicle detection module II, the vehicle detection module III, and the gate communication module 6 work normally.
  • the gate communication module 6 ie, the cloud communication module V
  • the driver APP uses the mobile communication to connect with the cloud server 1 to send the gate state information
  • the gate communication module 6 uses the LORA communication through the cloud communication module V or uses the Ethernet communication to transmit the signal to the cloud server 1 through the Ethernet communication.
  • the gate status information transmits the gate status information in different communication modes to improve the efficiency of the parking lot entrance and exit and the confidence of the gate status information.
  • the vehicle detecting sensor I40, the vehicle detecting sensor II50, and the vehicle detecting sensor III may employ a common vehicle detecting or license plate recognition sensor such as a geomagnetic sensor, an ultrasonic sensor, an infrared sensor, and a camera; when a camera or other license plate recognition sensor is used, the vehicle is detected. When the vehicle is close to the situation, the license plate is automatically recognized. At this time, the berth status information and the gate information also include the license plate number, and when the vehicle illegally parks or leaves the parking lot, the camera will violate the information of the vehicle, including the license plate number and location (ie, The camera installs the location, time, etc., and automatically uploads the cloud server 1 without the need for an administrator or other driver to collect evidence.
  • a common vehicle detecting or license plate recognition sensor such as a geomagnetic sensor, an ultrasonic sensor, an infrared sensor, and a camera; when a camera or other license plate recognition sensor is used, the vehicle is detected. When the vehicle is close to the situation,
  • Geomagnetic sensors are suitable for battery-powered applications with high severity and low energy management, such as in-street parking lot berth nodes, ultrasonic sensors, infrared sensors and cameras for occasions where the severity level is not high and can be powered by utility power, such as parking lot import and export. Or indoor berth nodes.
  • the terminal communication module I41, the terminal communication module II51, the terminal communication module III, the terminal communication module IV and the terminal communication module V can adopt a communication module such as Bluetooth low energy (BLE) that can directly connect to the application terminal;
  • the cloud communication module I42, Cloud communication module II52, cloud communication module III, cloud communication module IV and cloud communication module V can adopt dedicated short-range communication module (DSRC) and low-power wide-area network communication module (LPWAN), such as LORA (extended long-range based on spread spectrum technology) Low-power data transmission technology), NBIoT (cellular-based narrow-band Internet of Things) and other cloud modules that can be directly or indirectly connected to the cloud server 1.
  • DSRC dedicated short-range communication module
  • LPWAN low-power wide-area network communication module
  • LORA extended long-range based on spread spectrum technology
  • NBIoT cellular-based narrow-band Internet of Things
  • the vehicle detecting sensor I40, the vehicle detecting sensor II50, and the vehicle detecting sensor III all adopt a geomagnetic sensor, and the terminal communication module I41, the terminal communication module II51, the terminal communication module III, the terminal communication module IV, and the terminal communication module V adopt Bluetooth communication.
  • the module; the cloud communication module I42, the cloud communication module II52, the cloud communication module III, the cloud communication module IV and the cloud communication module V adopt the LORA communication module. Since the working principles of the vehicle detecting module I4, the vehicle detecting module II5 and the vehicle detecting module III are the same, only the working principle of the vehicle detecting module I4 is described in detail in the specification;
  • the geomagnetic sensor is in a periodic detection state.
  • the Bluetooth communication module and the LORA communication module stop working; in order to avoid algorithm misjudgment caused by other interferences and ensure stable and reliable vehicle detection,
  • a geomagnetic sensor having three axes of X, Y, and Z can be used to acquire geomagnetic field data, and a multi-state machine algorithm is used to determine whether the vehicle is parked.
  • the specific method is to store the data of the X, Y, and Z axes, and set a plurality of buffer states between the two states of the vehicle state and the carless state, when the magnetic field data changes and the difference of the changes exceeds the specified domain.
  • the algorithm first enters the buffer state. If the duration of the magnetic field data change is long enough, the system enters the next stable state. If the disturbance continues for a short time and then returns to the original state, the system returns to the previous stable state.
  • the geomagnetic detection is stopped, and the result of the state change wakes up the Bluetooth communication module from the sleep and starts to send the berth to the driver APP and the administrator APP.
  • the driver APP or administrator APP located nearby receives the berth status information, the driver planning the parking operator operates the driver APP to confirm the berth code and parking, and the driver APP sends the license plate number to the Bluetooth communication module via Bluetooth, Bluetooth communication
  • the module receives and saves the license plate number; the driver APP sends the check-in information/check-out information to the cloud server 1 through the mobile communication; the Bluetooth communication module sends the berth status information and the license plate number to the cloud server 1 through the LORA communication module, and the cloud server 1
  • the driver APP displays the successful check-in information/check-out information, the Bluetooth communication module of the vehicle detection module I4 and the LORA communication module enters sleep, and the geomagnetic sensor returns to the periodic detection state.
  • the LORA communication module fails to receive feedback from the cloud server 1 for receiving information successfully due to device abnormality or communication interruption, the LORA communication module will attempt to send information again according to the energy management arrangement, including the abnormal state record of the state change sent with the heartbeat information; heartbeat
  • the information is abnormal, that is, the heartbeat information is not received for more than 24 hours, the occupation status does not match the actual situation (repeated change in a short time or no change within 24 hours), or the battery remaining amount is insufficient, etc.
  • the cloud server 1 passes the administrator terminal 2 Notify the administrator to go to the site view and processing corresponding to the berth code, including extracting the abnormality record of the state change via Bluetooth, replacing the battery or replacing the device.
  • the driver APP and the vehicle detection module I4 synchronize the split communication to compensate for information loss, lag or error caused by device abnormality or communication interruption.
  • Part of the data and timing of the geomagnetic detection cycle, communication dormancy, and heartbeat information associated with energy management depends on the specific application, battery capacity, and expected battery life. Sleep and energy management can be disregarded when using other non-battery-powered vehicle detection sensors.
  • Parking law enforcement terminal 7 The parking law enforcement terminal 7 is used for monitoring the parked vehicle; the parking law enforcement terminal 7 can query the parking information of any berth, and the parking information is compared with the actual vehicle stay condition, and the illegal vehicle is Forensic, registration, and processing; the parking enforcement terminal 7 is also capable of receiving, storing, and processing complaints and reporting information from the administrator terminal 2 and the driver terminal 3, and processing the offending vehicle after verifying the complaint or reporting the information.
  • the parking law enforcement terminal 7 is connected to the relevant supervision department. For example, the road traffic police department, the city appearance management department or the street office can receive complaints about the illegal vehicles through the parking law enforcement terminal 7 and monitor the damage to the public berth. Sharing parking berths in normal parking order violations, thereby improving parking services and management.
  • driver APP and the driver PC terminal work in the same content, only the following berth service and management system and method are described in detail.
  • the work content of the driver app, the administrator app and the parking law enforcement app work in the same content, only the following berth service and management system and method are described in detail. The work content of the driver app, the administrator app and the parking law enforcement app.
  • Payment is a basic component of the transaction information in the berth service and management system and method. According to the parking fee policy, the driver can pay the fee when booking a berth, signing in a berth, checking out a berth or leaving the parking lot. Any reliable and mature payment means such as bank cards and electronic wallets are omitted in this specification.
  • Berth information announcement The parking lot administrator or berth owner announces the berth information to the cloud server 1 through the administrator APP.
  • the berth information includes at least the berth code, the berth size, the available time period and the parking time limit; wherein the berth code is unique. It is helpful to determine the specific location of the parking lot and the berth.
  • the berth size matches the vehicle's vehicle type.
  • the available time period defines the time period during which the berth can be reserved or parked, so as to facilitate the management of the berth and the sharing of personal and organization berths.
  • parking time limit specifies the maximum time that can be parked to improve the efficiency of berth transfer
  • berth information can also include information such as berth fee policy, permit conditions and penalty rules, including the free time or duration, minutes Or hourly rate, daily maximum rate, weekly rate or monthly rate standard
  • permit conditions include disabled person, residence permit, work permit, preferential certificate, visitor's card, parent's card, courier, delivery/delivery, pick-up/send Passenger, special car, taxi and other permits
  • penalties include unsigned berths, unsigned berths, super Occupy berths, time-out berths, overtime stays in parking lots, and parking within non-berth limits.
  • the berth respondent will not be able to be searched and booked by the driver.
  • the driver uploads the berth demand information to the cloud server 1 through the driver APP, and the berth demand information includes at least the destination name, the license plate number, the planned parking start time and the parking duration.
  • Cloud server 1 compares berth demand information and berth information, as shown in Figure 4.
  • the specific comparison content includes: comparison of destination name and berth code (specific location of berth), comparison of parking time and parking time limit, planned parking
  • the vehicle start time is compared with the available time period, and the time period after the planned parking start time and the parking time length are added (ie, the planned parking end time) is compared with the available time period; the cloud server 1 passes the berth information of the available berths.
  • the driver APP feeds back to the driver; the available berth indicates that the berth is not reserved, and the parking time of the checked berth meets the available time period and parking time specified in the berth information; the driver selects the appropriate berth information from the driver APP
  • the berth makes a reservation, and the cloud server 1 feeds back the berth reservation information to the driver and the parking lot administrator/berth owner, that is, the cloud server 1 transmits the berth reservation information to the administrator APP and the driver APP, respectively.
  • the vehicle applicant may not be able to reserve a berth.
  • the vehicle enters the parking lot: When the parking lot has a gate control mechanism, that is, when there is a connected gate communication module 6 and a gate, the gate communication module 6 and the vehicle detection module II5 and the vehicle detection module located on both sides of the gate respectively.
  • the vehicle detecting sensor II50 in the vehicle detecting module II5 detects that the vehicle is approaching, and sends a signal to the terminal communication module II51, and the terminal communication module II51 sends the vehicle to the driver APP and the administrator APP respectively.
  • the proximity information includes at least a parking lot code, a gate code, and an approach/exit time; the gate communication module 6 controls the opening of the gate according to a command of the driver or the administrator; and the vehicle detection sensor III detects the vehicle in the vehicle detection module III.
  • the vehicle detection module III sends the vehicle passage information to the gate communication module 6; the gate communication module 6 controls the gate to close after receiving the vehicle passage information, as shown in FIG. 5, specifically including the following steps;
  • the driver confirms the approach. At this time, the driver operates the "open" button through the driver APP, and the driver APP sends the opening command and the license plate number information to the terminal communication module V and the terminal communication module II51, respectively;
  • the terminal communication module V receives the opening command and the license plate number information from the driver APP and sends it to the driving module; the driving module receives the opening command and the license plate number, and adds the license plate number to the queue to be opened; terminal communication After receiving the opening command and the license plate number information from the driver APP, the module II51 sends the license plate number, the gate code and the opening enable command to the cloud communication module V through the cloud communication module II52, and the cloud communication module V receives and sends the message to the cloud communication module V.
  • the driving module compares the opening command from the cloud communication module II52 with the opening command from the driver APP, and controls the gate to open after the comparison is successful.
  • the gate display module displays the parking lot name, the gate code and the remaining available berth information.
  • the license plate number and the welcome information are simultaneously displayed or switched; and the terminal communication module V retrieves the vehicle berth reservation information by the license plate number. If there is no available berth remaining in the parking lot and the vehicle has not reserved a berth, or the arrival time of the vehicle does not match the planned parking start time, the terminal communication module V prompts the driver through the driver APP and the gate display module to be specified. Leave the parking lot within the time limit. The time limit is determined by the parking lot according to the actual situation.
  • the gate communication module 6 can send the available berth information to the driver APP, and the driver only needs to confirm the berth code and the parking time to realize the instant parking, the driver You only need to leave the parking lot within a limited time after checking out the berth; if the driver enters the parking lot and makes an appointment for the available berth or extends the parking time and succeeds, the driver only needs to reserve or extend the parking. You can leave the parking lot within the length of the car.
  • the cloud communication module V sends the vehicle entrance information to the cloud server 1; after receiving, storing and updating the vehicle entrance information, the cloud server 1 then encodes the cloud communication module of all the gate communication modules 6 of the same parking lot. V sends the vehicle entry information.
  • the state of the gate changes.
  • the vehicle detection sensor II50 sends the vehicle proximity information to the administrator APP and the driver APP through the terminal communication module II51.
  • the gate state in the gate information is a vehicle; when the gate state is If the vehicle has not been updated from no vehicle to no vehicle within the specified time, that is, the administrator APP has not received the information that the gate status has changed again within the specified time, indicating that the driver has not performed the "opening" operation, and the vehicle remains at the vehicle.
  • the administrator gate information is prompted.
  • the administrator can receive the gate abnormality information and rush to the gate according to the gate code in the gate information to assist the driver to open the gate. That is, the administrator can pass the administrator.
  • the camera function of the APP collects the license plate number, and sends the license plate number and the opening command to the drive module through the terminal communication module V, and the corresponding vehicle enters the parking lot;
  • the operation opening gate clearly points to a specific license plate number and gate code, and the invention provides for the opening by the administrator APP.
  • the gate command and the license plate number are sent directly to the drive module through the terminal communication module V.
  • the drive module controls the gate to be opened according to the received opening command and the license plate number without the need to open the gate enable command.
  • the vehicle detection module II5 for detecting the approach of the vehicle is located outside the gate (the side away from the parking lot), and the terminal communication module II51 establishes communication with the administrator APP and the driver APP, thereby Realizing the opening action;
  • the vehicle detecting module III for detecting the passing condition of the vehicle is located inside the gate (on the side close to the parking lot), and when the vehicle detecting sensor III detects that the vehicle disappears, it indicates that the vehicle has passed the gate,
  • the cloud communication module III sends the vehicle passing information to the cloud communication module V to realize the gate closing action.
  • the driving module transmits the vehicle passing information to the cloud communication module V according to the cloud communication module V, that is, the automatic closing of the gate is enabled, the driving gate is closed, and any driving module receives the opening of the brake plate in the closing process.
  • the ability to command and open the command will disable the gate and disable the gate (the vehicle that does not have the opening condition may cause interference between the vehicle and the gate) until the new automatic gate is activated. Turn off the gate to avoid interference between the vehicle and the gate when the traffic is large.
  • the embodiment may be modified according to the situation.
  • the gate communication module 6 that controls the vehicle entering and leaving the parking lot at the gate is changed to a berth lock that acts on a specific berth to control the entry and exit of the berth (the berth lock is located).
  • the berth lock receives the vehicle approach information and the vehicle departure information sent by the vehicle detection module I, and the unlock command and license plate number from the driver APP; the berth lock After the license plate number, the parking lot code and the berth lock code are bound, the berth lock is closed, and the berth lock is popped after being untied; the berth lock sends the berth information and the berth berth information of the corresponding berth vehicle to the cloud server 1.
  • the opening command and the check-in berth/check-out berth are completed synchronously, in other words, the unlocking command of the berthing station is completed synchronously with the check-in berth command, and the command and check-out of the pop-up berth lock leaving the berth
  • the berth command is synchronized.
  • the vehicle enters the berth: the vehicle detection module I4 is provided on the berth.
  • the vehicle detection sensor I40 in the vehicle detection module I4 detects that the berth occupancy state changes, that is, the berth occupancy state is changed from no car to car.
  • the vehicle detecting sensor I40 sends a signal to the terminal communication module I41, and the terminal communication module I41 receives the signal and sends the berth status information to the cloud communication module I42, the driver APP and the administrator APP respectively; the cloud communication module I42 will be
  • the received berth status information is sent to the cloud server 1 through the cloud communication module IV of the berth relay module 8.
  • the driver APP After receiving the above berth status information, the driver APP sends a welcome message to the driver, pops up the berth code and requests the driver to check in the berth; in order to avoid communication abnormality or equipment failure, the driver APP and the vehicle detection module I4 are first exchanged through the terminal communication module I41.
  • the berth code and the license plate number information are then sent to the cloud server 1 through the communication of the host;
  • the specific check-in berth step is, when the driver confirms the check-in berth, the driver APP sends the license plate number to the terminal communication module I41, and then drives The member APP sends the check-in information to the cloud server 1 through the mobile communication;
  • the terminal communication module I41 sends the check-in information to the cloud communication module I42, and the cloud communication module I42 receives the check-in information and passes the cloud communication module IV of the berth relay module 8 to
  • the cloud server 1 sends the check-in information;
  • the check-in information includes at least the corresponding berth code, the license plate number, the check-in berth time, and the planned parking end time;
  • the cloud server 1 receives the check-in information and queries the corresponding berth reservation information according to the license plate number in the check-in information, and compares the queried reservation information with the received berth code and the time of checking in the berth, and specifically compares the content. Comparing the reserved berth code with the actually checked berth code, the planned parking start time is compared with the actual check-in berth time; when the comparison is successful, the cloud server 1 binds the license plate number and the berth code, and Sending the successful check-in berth information to the driver APP and the administrator APP; when the berth cannot be successfully checked, the driver APP is sent the reason for the unsuccessful check-in berth and the subsequent operation request;
  • the above berth status information includes information such as berth code, berth occupancy status, status confidence, and status change time; berth status information when vehicle detection sensor I40, vehicle detection sensor II50, and vehicle detection sensor III employ a camera or other license plate recognition sensor Also included is the license plate number.
  • the cloud communication module I42 sends the berth status information to the cloud server 1 , and the berth occupancy status is the vehicle, and the state confidence is the initial value.
  • the initial value is 50%;
  • the server 1 receives, stores and updates the berth status information, and sends the updated berth status information to the administrator APP, and the administrator APP synchronizes the update.
  • the cloud server 1 receives the check-in information of the vehicle and matches successfully, and binds the corresponding license plate number and berth code.
  • the cloud server 1 increases the state confidence to 100%; In the middle, after the berth occupancy status changes, the cloud server 1 will judge whether the corresponding berth is successfully checked into the berth. If the berth is successfully checked, the state confidence is increased to 100%; the driver can first sign in the berth and then enter the berth when the vehicle is stationed.
  • the cloud server 1 checks that the corresponding berth has been successfully checked in according to the berth number, and the cloud server 1 immediately raises the state confidence to 100%; if the specified time limit is not reached, that is, the vehicle is not in the berth after being placed in the berth. If the berth is successfully checked in, the cloud server 1 prompts the administrator berth to occupy the information by the administrator APP.
  • the above administrator APP can immediately receive the updated berth status information when the administrator is in the vicinity of the berth.
  • the cloud server 1 When the driver confirms the check-in berth, the cloud server 1 does not query the berth reservation information through the license plate number in the check-in information, and the driver APP prompts the driver to confirm the berth code and the default parking time, driving The member can change the parking time to execute the check-in berth; the cloud server 1 checks through the berth code to check that the berth is successful when the corresponding berth is available. Otherwise, the cloud server 1 fails to check the berth through the driver APP. Please reserve other available berths and leave. .
  • the berth can be used to indicate that the parking time reserved for the berth has not been reserved by others, and the available time of the berth (such as parking between 08:00 and 16:00 when the shared berth is set) and the berth time limit (such as road parking)
  • the car can be set to a maximum dwell time of 1 hour.
  • the operation of booking other available berths can be done according to the step 2 berth reservation.
  • the driver PC terminal can be operated by the colleague, relative or friend to send the check-in information to the cloud server 1, or wait for the administrator to come to assist the check-in berth at the berth site; wherein the driver PC
  • the operation of the terminal to check in the berth is the same as that of the driver APP, so it will not be detailed.
  • the specific operation mode of the administrator assisting to check in the berth is: when the vehicle enters the berth, the terminal communication module I41 sends the berth status information to the administrator APP, or the cloud server 1 receives the berth status information for updating, and then periodically sends the information to the management.
  • the APP makes it update (real-time synchronization updates the berth status information in the administrator APP, and avoids the terminal communication module I41 failing to send information to the administrator APP, such as limited by the communication distance), at which time the state confidence in the berth status information is initial State, in this embodiment, the initial state of state confidence is 50%.
  • the administrator terminal 2 prompts the administrator for the berth abnormal occupation information, including the berth code and the occupancy situation (the berth is not successfully checked). The administrator goes to the corresponding berth according to the berth code to assist the driver.
  • the “check in berth” operation can be divided into the following two cases;
  • the driver has reserved the berth through the driver terminal 3: the administrator can assist the driver to complete the check-in berth according to the “check-in berth” operation in step 4) through the administrator APP;
  • the driver does not reserve a berth (immediate parking): the administrator can upload the berth code, license plate number and parking time to the cloud server 1 according to step 4) immediate parking operation through the administrator APP;
  • the administrator can assist the driver to check in other available berths according to step 2) through the administrator APP, or change the berth code reserved by the punctual follow-up person (ie, the driver has left and cannot perform the vehicle)
  • the administrator can change the berth code reserved by the follow-up berth reservation person and notify the follow-up driver of the changed berth reservation information in time); after the reservation is successful, the administrator can "sign" according to step 4) through the administrator APP.
  • the berth operation assists the driver to complete the check-in berth; when the administrator assists the driver to check in the berth, the administrator can use the camera function to automatically recognize and enter the license plate number, improving work efficiency and data entry accuracy.
  • the vehicle respondent may not be able to park immediately according to the severity and rules of the nature of the problem.
  • the driver When the vehicle leaves the berth, the driver confirms the check-out berth through the driver APP, and the driver APP sends the check-out information to the cloud server 1 at the time, the check-out information includes the corresponding berth code, the license plate number and the time of checking out the berth;
  • the server 1 receives the checkout information and queries the corresponding check-in information according to the license plate number of the checkout information, and compares the check-in information with the received berth code and the time of checking out the berth; comparing the successful cloud server 1 to the administrator APP And the driver APP sends a confirmation checkout berth information; at this time, the cloud server 1 receives the checkout information and resets the state confidence to an initial value of 50%; as shown in FIG.
  • the vehicle detection module when the driver drives the vehicle away from the berth, the vehicle detection module
  • the vehicle detecting sensor I40 in I4 detects the change of the berth occupancy state, that is, the berth occupancy state is changed from the car to the no car. At this time, the vehicle detecting sensor I40 sends a signal to the terminal communication module I41, and the terminal communication module I41 receives the signal.
  • the berth status information is sent to the cloud communication module I42, the driver APP and the administrator APP respectively; the cloud server 1 receives the berth status information and then drives the vehicle
  • the brand code and the berth code are untied, and the unbinding information is sent to the driver APP.
  • the driver APP After receiving the unbinding information, the driver APP sends the berth checkout success information and sends a message to the driver; the cloud communication module I42 will receive the message.
  • the berth status information is sent to the cloud server 1 through the cloud communication module IV of the berth relay module 8, and the cloud server 1 receives the berth status information and updates the berth occupancy status to no car, and the berth within the time limit specified by the driver after the check operation is completed.
  • the occupancy status is no car, the cloud server 1 increases the state confidence to 100%, and unbinds the license plate number and the berth code; in the actual working process, after the checkout is successful, the cloud server 1 determines whether the berth occupancy state is consistent with the actual situation.
  • the cloud server 1 If they are consistent, the state confidence is increased to 100%, or the user can leave and then check out the berth.
  • the cloud server 1 immediately increases the state confidence to 100. %, if the agreement is still not reached within the specified time limit, the cloud server 1 prompts the administrator berth to occupy the letter through the administrator APP. interest.
  • the driver confirms the check-out berth
  • the state confidence level does not increase within the specified time.
  • the administrator APP prompts the administrator berth to occupy the abnormal information.
  • the administrator can go to the site to check out the berth according to the berth code; the checkout cannot be successfully performed.
  • the reason for the unsuccessful checkout berth and the subsequent operation request are sent to the driver APP;
  • the berth can wait for the administrator to assist in the operation of “checking out the berth”;
  • the specific operation mode is: the terminal communication module I41 sends the berth status information to the administrator APP when the vehicle leaves the berth.
  • the cloud server 1 receives the berth status information for updating, periodically sends the information to the administrator APP to update it (avoiding the terminal communication module I41 failing to send information to the administrator APP), and the cloud server 1 sets the berth status information.
  • the state confidence is 50%.
  • the administrator APP prompts the administrator for the berth abnormal occupation information.
  • the administrator will go to the corresponding berth according to the berth code to assist the driver to pay and “check out the berth” operation. If the driver does not wait for the administrator to go to the “check out berth” operation at the berth, the administrator will go to the berth to check out the berth according to the berth abnormal occupancy information (the berth has no car and the berth is not checked out), and according to the driver. Record and report the severity of the violation.
  • the cloud server 1 After the driver finishes confirming the check-out berth, the cloud server 1 sends the check-out information of the corresponding vehicle to the cloud communication module V of all the gate communication modules 6 of the same parking lot;
  • a berth relay module 8 for assisting the driver or the administrator to complete the check-in berth and the check-out berth is further provided at the entrance and exit of the parking lot pedestrian, and the driver APP, the administrator APP, and the cloud communication module I42 are both passed.
  • the cloud communication module V of the berth relay module 8 is connected to the cloud server 1 signal, that is, the driver APP, the administrator APP, and the cloud communication module I42 send information to the cloud server 1 through the cloud communication module V of the berth relay module 8
  • the cloud server 1 sends information to the driver APP, the administrator APP, and the cloud communication module I42 through the cloud communication module V of the berth relay module 8, which is beneficial to the energy management of the node and the stability of the system.
  • the berth relay module 8 is not required for all applications. For example, when the cloud communication module I42 of the on-street parking lot and the open-air parking lot is unblocked, the berth relay module 8 can be used to implement direct communication between the cloud communication module I42 and the cloud server 1.
  • the state confidence level that is, the state confidence level of the vehicle detection module I4 changing the parking state information and the state confidence level of changing the parking state information when the driver performs the check-in operation or the check-out operation can be based on the actual work demand at 0.
  • the parking lot manager may be based on the driver's degree of checking in berths and checking out berth habits, for example, the driver has never stopped arbitrarily, and parking according to the steps of the present invention. Then, the state of confidence of the check-in information and the check-out information from the driver is 100%, or the state confidence of the berth state information from the vehicle detecting module I4 is determined according to the vehicle detecting module I4 and the reliability degree of the communication.
  • the parking lot administrator/berth owner can adjust the ratio of the state confidence of the berth status information updated by the vehicle detection module I4 on the berth according to the actual situation between 0% and 100%; the same cloud server 1 can be based on Corresponding to the vehicle historical parking information and transaction information, etc., the ratio of the state of confidence of the check-in information and the check-out information from the driver is 0%. Adjusted between 100%; assume when the state information and the check information to check out a confidence level of 100%, the vehicle may be ignored in claim I4 the detection module.
  • the vehicle detecting sensor II50 at the exit of the parking lot detects that the vehicle is approaching
  • the signal that the vehicle is approaching is transmitted to the terminal communication module II51
  • the terminal communication module II51 is directed to the driver APP and the administrator terminal 2 (administrator)
  • the APP and the administrator PC terminal respectively transmit the vehicle approach information; the driver can send the opening command and the license plate number information to the terminal communication module V and the terminal communication module II51 through the driver APP (or the remote driver PC terminal); the terminal communication
  • the module II51 After receiving the opening command and the license plate number information from the driver APP, the module II51 sends the license plate number, the gate code and the opening enable command to the cloud communication module V through the cloud communication module II52, and the cloud communication module V receives and sends the message to the cloud communication module V.
  • the driving module receives the opening command and the license plate number information from the driver APP, and then retrieves the vehicle entrance information and the berth checkout information through the license plate number when the vehicle leaves within a prescribed time (at the reserved parking time) Leave within or within the time limit of the driver's departure as indicated in step 3.) Terminal communication module V will open the command and license plate The number information is sent to the driving module; the driving module compares the opening and closing command from the cloud communication module II52 with the opening command from the driver APP, and the control gate is opened after the comparison is successful.
  • the gate communication module 6 returns to the driver APP the reason for the failure to open the gate and Subsequent requirements can be divided into the following situations;
  • the driver has not successfully checked out the berth: When the driver fails to check out the berth and the gate fails to be opened, the driver can complete the payment according to the operation of checking out the berth in step 5 and confirm the check-out berth. The berth is successfully checked out. Then, according to step 6, the gate opening command and the license plate number information are re-transmitted to the gate communication module 6;
  • the driver has timed to stay in the parking lot, including the vehicle leaving the parking lot within the time limit indicated when entering the vehicle and the vehicle has not left the parking lot within the specified time limit after the berth is checked out: when the driver has timed to stay in the parking lot
  • the driver can confirm and accept the corresponding punishment according to the parking lot regulations (such as paying the fine, deducting the credit score, etc.), and then re-communicate to the terminal communication module V and the terminal according to step 6.
  • Module II51 sends the opening command and the license plate number information;
  • the vehicle detecting sensor II50 detects that the state of the gate has changed, triggering
  • the terminal communication module II51 transmits the gate information to the driver APP and the administrator terminal 2 (the administrator APP and the administrator PC terminal) respectively, and when the administrator terminal 2 does not receive the information that the gate state is changed again within a predetermined time, it indicates The driver did not perform the “opening” operation, and the vehicle still stayed at the gate.
  • the administrator could go to the corresponding gate according to the gate code in the gate information to assist the driver to open the gate, leave the parking lot, and the administrator passed the management.
  • the camera function of the app APP collects the license plate number of the vehicle, and assists the driver through the administrator APP to complete the payment. After that, the administrator APP sends the license plate number and the opening command to the drive module through the terminal communication module V, and the corresponding vehicle leaves the parking lot.
  • the driver fails to check out the berth: the administrator collects the berth fee through the administrator APP and sends the checkout information, or sends the checkout information to the berth relay module 8 located at the exit of the parking lot, and the berth relay module 8 Receiving the checkout information and sending it to the cloud server 1 to implement the work of assisting the driver to check out the berth; after the berth is successfully checked, the administrator sends the corresponding vehicle license plate number and the open gate command to the gate communication module 6 through the administrator APP, thereby Achieve assistance to the driver to open the gate.
  • the license plate number can be ingested and automatically recognized by the camera of the administrator APP.
  • the vehicle detection module II5 for detecting the approach of the vehicle is located inside the gate (on the side close to the parking lot), and the terminal communication module II51 establishes communication with the administrator APP and the driver APP, thereby Realizing the opening action;
  • the vehicle detection module III for detecting the passing condition of the vehicle is located outside the gate (the side away from the parking lot), and when the vehicle detecting sensor III detects that the vehicle passes the gate, the cloud communication module III is toward the cloud
  • the communication module V transmits the vehicle passing information to realize the closing action.
  • the driving module sends the vehicle passing information to the cloud communication module V according to the cloud communication module III, that is, the automatic closing of the gate is enabled, the driving gate is closed, and the driving module receives a new opening enabling command and the opening command during the closing process.
  • the gate will be disabled and the gate will be re-opened until the new automatic gate is activated and the gate is completely closed to avoid interference between the vehicle and the gate when the traffic is large.
  • the vehicle applicant may not be able to open the parking lot and leave the parking lot autonomously.
  • Abnormal conditions include the most unfair normal use, reasonably foreseeable misuse and single fault conditions
  • Reasonably foreseeable misuse that is, in accordance with foreseeable human behavior, habits or inertial thinking, beyond the prescribed procedures or operating systems, such as misleading and mistaking berths, overtime occupying berths, ignoring or misreading berth status information, chaos Charges and habitual cash payments, non-reserved parking, unskilled clients or non-client drivers, unnecessarily stranded parking lots or the inability to find vehicles/berths and operations that affect driving safety, foreseeable surprises Conditions of use under the influence of
  • a single fault condition that is, a condition in which a preventive measure for preventing information link breakage fails or a condition that may cause a break in the information chain to occur, which can be simply summarized as a hardware failure or a communication failure of the device.
  • the present invention fully contemplates and provides means to prevent and correct the most adverse normal use conditions, reasonably foreseeable misuse, and adverse effects of a single fault condition on the intended function, technical performance, and customer experience of the system. Includes the following measures:
  • the vehicle detection sensor, berth information, berth reservation information, check-in information and check-out information are combined to improve the accuracy and integrity of the berth status information, thereby displaying clear and accurate berth status information to the driver, which facilitates the driver to distinguish useful berths. And vacant berths to avoid misleading and mistaking;
  • Redundant communication design such as mobile communication, terminal communication, cloud communication and Ethernet communication, to avoid incomplete information and errors caused by information lag and loss caused by equipment failure and communication obstacles;
  • the berth abnormal state at least includes the unsuccessful signing of the berth, the unsuccessful checkout of the berth, the overtime parking, the berth failure and the berth respondent;
  • Unsuccessful check in berth After the driver confirms the successful plucking of the berth, the cloud server 1 will increase the state confidence; therefore, the occupant occupancy state keeps the vehicle in place, and the state confidence does not improve within the specified time (driver If the driver does not check in the berth, or if the driver does not leave the berth within the specified time, the administrator terminal 2 prompts the administrator to berth abnormal state, and the administrator can go to assist the driver according to the berth code. Check in the berth, or prompt to move the vehicle away from the berth;
  • the berth is not successfully checked out: when the driver confirms the check-out berth, the cloud server 1 receives and updates the state confidence level as the initial value; when the vehicle leaves the berth, the cloud server 1 increases the state confidence and sends the driver a success.
  • the berth code and the license plate number are untied, the berth status information and the berth information are updated; when the state confidence is reset to the initial value and there is no increase within the stipulated time (indicating that the driver has not left the berth)
  • the administrator terminal 2 prompts the administrator berth abnormal state, and the administrator can go to the berth site according to the berth code to move the driver away from the parking space.
  • Overtime parking When the vehicle exceeds the reserved parking time, the administrator terminal 2 prompts the administrator to berth abnormal state, the administrator can go to the berth site according to the berth code to make the driver move away from the scene, or query the corresponding berth according to the berth code. For the reservation situation, if necessary, the subsequent reservation driver will be adjusted to other vacant berths, and the driver will be notified in time to re-allocate the berth code.
  • the administrator processes the above-mentioned illegal vehicles, and when the circumstances are serious, the evidence can be collected through the administrator terminal 2, and the collected evidence is sent to the parking law enforcement terminal 7 for reporting; when the driver finds that there is a violation of the vehicle or the berth failure, Evidence can be collected by the driver terminal 3, and the collected evidence can be sent to the administrator terminal 2 for reporting, or sent to the parking law enforcement terminal 7 for reporting.
  • the vehicle detecting sensor I40, the vehicle detecting sensor II50, and the vehicle detecting sensor III use a camera or other license plate recognition sensor, the information of the illegal vehicle, including the license plate number, the position (ie, the vehicle detecting sensor installation geographical position), the time, etc., is automatically uploaded to the cloud server. 1 without the need for an administrator or other driver to collect evidence;
  • the berthee may be screened to lose the opportunity to be searched and booked, and the vehicle applicant may not be able to reserve a berth, park immediately or leave the parking lot.
  • the state of the gate is abnormal, that is, if the vehicle stays at the gate for more than the specified time limit
  • the state of the gate changes, and the state of the gate of the vehicle detection module II5 transmitting the gate information to the administrator terminal 2, the driver terminal 3 and the cloud server 1 respectively is the vehicle; the driver turns on the gate vehicle to enter the parking.
  • the cloud server 1 receives and stores the vehicle access information of the gate communication module 6 at this time, and the administrator terminal 2 synchronizes and updates; when the gate state remains unchanged within the prescribed time limit, the administrator terminal 2 prompts the administrator gate abnormality information.
  • the administrator can go to the corresponding gate for processing according to the gate code in the gate abnormality information.
  • the driver APP (or administrator APP) communicates abnormally with the cloud server 1 and cannot successfully send the check-in information, check-out information, and transaction information to the cloud server 1, which may result in loss, lag, or error of the information;
  • the driver APP (or the administrator APP) and the terminal communication module I41 corresponding to the berth send the license plate number and the berth code to each other, and then the driver APP (or the administrator APP) and the terminal communication module I41 each use their own communication method to the cloud.
  • the server 1 sends the check-in information/check-out information, thereby ensuring that under the single fault condition, that is, if the communication between the driver APP (or the administrator APP) and the vehicle detecting module I4 and the cloud server 1 cannot simultaneously fail, The operation of checking in berths and checking out berths can be completed normally;
  • the LORA communication is abnormal: the communication between the cloud communication module I42 and the cloud server 1 is abnormal, and the check-in information, the check-out information, and the heartbeat information cannot be successfully sent to the cloud server 1, which may result in loss, lag, or error of information; (or the administrator APP) and the terminal communication module I41 corresponding to the berth send the license plate number and the berth code to each other, and then the driver APP (or the administrator APP) and the terminal communication module I41 each send a check-in to the cloud server 1 by using its own communication method.
  • the information/checkout information ensures that the check-in can be completed normally under the condition of a single fault, that is, if the communication between the driver APP (or the administrator APP), the vehicle detection module I4 and the cloud server 1 cannot be simultaneously failed. Berths and the operation of checking out berths;
  • the vehicle detection module I4 fails to send information to the cloud server 1. If the cloud communication module I42 or the berth relay module 8 is abnormal, the information will be saved in the cloud communication module I42 or the berth relay module 8, the cloud communication module I42 and the berth. After the module 8 re-sends the information to the cloud server 1 at a timing (such as every 120 minutes) until receiving the receipt successfully received by the cloud server 1, the device is low-energy-managed while ensuring the stability of the berth service and the management system. .
  • the communication module I41 of the terminal communication module is abnormal, and the berth status information cannot be sent to the driver APP (or the administrator APP); at this time, the driver only needs to remember the berth code, and can input the berth code to complete the check-in berth at the berth relay module 8. And the operation of checking out the berth.
  • the cloud communication module I42 communication abnormality cannot send information to the cloud. At this time, the driver can complete the operation of checking in the berth and checking out the berth through the driver APP. In the case of an abnormality of the driver APP communication at the berth site, the driver can perform the operation of checking in the berth/checking out the berth through the driver APP in any signaled place within a limited time.
  • the vehicle detection module I fails, the cloud server 1 cannot completely receive any information from the cloud communication module I42. Since the cloud communication module I42 periodically sends heartbeat information to the cloud server 1, the cloud server 1 The abnormal condition of the equipment can be found in time and the administrator can be notified immediately for repair or replacement, thereby ensuring the normal operation of the berth service and management system of the present invention.
  • the administrator terminal 2 or the parking law enforcement terminal 7 When the administrator terminal 2 or the parking law enforcement terminal 7 receives a berth failure, a report on a parking lot violation or a vehicle violation, a complaint or a report, the administrator or the parking law enforcement officer verifies the submitted report or evidence, if necessary Can go to the site for verification. If the content reported, complained or reported after verification is true, the administrator terminal 2 or the parking enforcement terminal 7 gives feedback to the complainant (administrator or driver), and the berth of the serious violation is the respondent or the vehicle respondent, possibly Unable to operate or park.
  • the driver terminal 3 can collect the evidence and report or complain to the administrator terminal 2 or the parking law enforcement terminal 7.
  • the parking lot manager can eliminate the berth applicant by accepting corresponding treatment (such as paying a fine) Abnormal state.
  • the vehicle applicant cannot reserve the berth: when the vehicle applicant makes a berth reservation through the driver APP, the driver APP submits the berth demand information to the cloud server 1, and the cloud server 1 first passes the berth demand when comparing the berth demand information and the berth information.
  • the license plate number in the information retrieves the corresponding vehicle information.
  • the cloud server 1 will reject the reservation operation of the vehicle, and the rejection reason and the subsequent operation request are fed back to the driver through the driver APP;
  • any vehicle can open the gate to enter the parking lot with the help of the driver APP or the administrator; after the gate is opened, the gate communication module 6 sends the vehicle entry information to the cloud server 1; the cloud server 1 Receiving, storing and updating vehicle entry information, including retrieving whether the corresponding vehicle information is in the vehicle respondent state according to the license plate number, and transmitting the vehicle entry information to all gate communication modules 6 under the same parking lot code (including vehicles when used) Respondent information).
  • the driver APP submits the check-in information to the cloud server 1, and the cloud server 1 first passes the license plate number in the information. Retrieving the corresponding vehicle information, when the vehicle information includes the vehicle applicant, the cloud server 1 will reject the check-in operation of the vehicle, and the rejection reason and the subsequent operation request are fed back to the driver through the driver APP;
  • the driver can eliminate the abnormal state of the vehicle respondent by accepting the corresponding treatment (such as paying a fine).
  • the driver fails to pay the corresponding fine such as no driver APP
  • the administrator goes to the abnormal state to inform the vehicle to be treated by the applicant to eliminate the abnormal state (ie, pay the penalty through the driver terminal 3, or go to the relevant department to pay the fine) .
  • the parking lot administrator will assist the driver to turn on the parking and leave the parking after receiving the penalty according to the rules of not checking in the parking or leaving the parking lot after timeout. field.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Traffic Control Systems (AREA)

Abstract

一种基于车辆检测的泊位服务与管理系统及方法，包括依次进行的以下步骤：泊位信息公布；泊位预约信息获取；泊位占用状态检测；签入泊位和签出泊位的操作；异常信息的提醒及处理；车辆进驻泊位时，泊位占用状态由无车改变为有车，此时驾驶员需进行签入泊位操作确认泊车开始；车辆驶离泊位时，泊位占用状态由有车改变为无车，此时驾驶员需进行签出泊位操作确认泊车终止；当驾驶员未成功签入泊位/签出泊位，则显示异常信息提示管理员处理。

Description

基于车辆检测的泊位服务与管理系统及方法 技术领域
本发明涉及智慧交通系统技术领域，尤其涉及一种基于车辆检测的泊位服务与管理系统及方法。
背景技术
美国、英国、德国、日本、新加坡等国的停车场发展大致经历了路内泊位、地面停车场、地下停车场和立体停车场等发展阶段，纵观这些发达国家停车场规划和布局发展的历史和现状，基本经历了从被动地增加泊位数量来满足泊车需求的增长，逐渐发展到以泊车需求控制用地，以泊车位的供给来控制交通量，即从被动建设转变为主动引导并且结合交通结构的调整，将合理布局停车场和提高已有停车场的利用率相结合在长期的规划、建设和管理实践中。
与以上大多数国外发达国家的停车场发展经历一样，我国泊车难问题受经济、人口、机动车发展的影响，且随着社会经济人口的快速发展和城市机动化进程的不断加快日益突出，车辆增长特别是私家车的快速发展是导致泊位需求增长最重要的因素。然而，从我国机动车泊位的现状和机动车快速发展的态势，泊位和车辆的供需倒挂将日趋严重，单纯从强化停车场规划和增加停车场建设远远不能满足城市发展的需求。
我国传统泊车行业现状包含四大痛点：总量缺口大、结构较分散、管理散乱、智能化水平低。这直接导致了例如用户一位难求、泊车体验差、停车场泊位流转效率低下和管理成本高等诸多问题。传统的停车场由于分布不均且彼此割裂，尚未形成统一网络，导致可用泊位信息不对等；尤其是众多住宅小区、机关和社团的私家泊位，泊位的利用效率更低。与此同时，随着城市停车场数量的日益增加和规模的大型化，泊位和车辆供需倒挂日趋严重的局面，传统泊车人工服务与管理的低效率和孤立的停车场信息，难以满足司机大军日理万机对高效率交通和停车场服务与管理提出的高要求。此时，运用监控、诱导、路闸和车牌自动识别等手段实现泊车的智能化服务与管理应运而生。
但是现有技术仍存在服务与管理不能满足泊车实际需求的问题，即时泊车中会出现当前信息有空余泊位但当车辆到达目的地时发现目的地附近根本没有可用泊位，所得信息即时性和准确性是一个挑战；预约泊车会出现部分预约泊位被占用，或预约车主未按约定到达预约的泊位上，预约客户和非预约客户的兼容性以及预约终端客户和非预约终端客户之间的兼容性等问题，给停车场和驾驶员带来了极大的不便；出入口的障碍、现金交易以及尴尬的支付流程无不影响着泊位的流转效率，泊位共享只是一个美好的愿景；停车场和泊位普遍缺乏限制性管理手段，忽视时段限制和禁令标志的乱停乱放、不计时限的无限泊车以及简单粗暴的报复性和惩罚性整治手段等严重影响了正常的泊车秩序和客户体验；现存各类服务与管理手段或多或少局限于停车场主、驾驶员或政府的局部或个体利益，而忽视了社会的、非停车场主或非驾驶员的群体利益，由于不能从规则上解决泊车难题，额外的交通压力、环境污染和资源消耗侵害了更多与交通无关的群体利益。
如专利号为201610752210.5的发明专利《泊位预约方法及系统、泊位信息服务平台》中所提出的泊位预约方法包括：获取停车场的泊位信息以及驾驶员的泊车需求信息，泊位信息至少包括停车场各个泊位的当前登陆状态信息以及预约状态信息；泊车需求信息至少包括目标泊车区域、预计登陆泊位日期和时间、预计退出泊位日期和时间；根据泊位信息和泊车需求信息对停车场的泊位进行预约，并将预约结果反馈至停车场和驾驶员；在登陆泊位期间，根据驾驶员的延时泊车请求和当前停车场的泊位信息，对驾驶员的退出泊位时间进行延长或对登陆泊位进行变更。通过获取即时、有效、完整的泊位信息，实现智能化的泊位预约及管理，改善驾驶员出行与泊车难题。该专利存在以下几点问题：1.该专利基于对泊位的预约实现对泊位的管理，不能兼容即时泊车；2.该专利不能兼容非泊位预约终端客户；3.该专利对不执行泊位登陆/退出或不按照实际执行泊位登陆/退出的违规缺乏监督和管理手段；4.该专利对通讯滞后或通讯失败相关的信息即时性和准确性问题缺乏技术保障；5.该专利对如何确保停车场出入口畅通缺乏思考。
综上，现今急需一种适用于即时泊车、预约泊车和泊位共享多种泊车服务与管理模式，同时满足驾驶员(包括非终端驾驶员)、停车场主(包括拥有泊位的个体或组织)以及泊车执法需求的泊位服务与管理系统及方法。
发明内容
本发明要解决的技术问题在于提出一种通过车辆检测和通讯的设计能够确保停车场信息的即时性和准确性，从而实现对停车场内泊位进行管理的基于车辆检测的泊位服务与管理系统，以及采用该系统实现对停车场内泊位服务与管理的方法。
为了解决上述技术问题，本发明提供一种基于车辆检测的泊位服务与管理系统；
所述泊位服务与管理系统包括云端服务器，以及与云端服务器信号相连的管理员终端、驾驶员终端、 车辆检测模块Ⅰ和泊车执法终端；所述管理员终端和驾驶员终端均与车辆检测模块Ⅰ和泊车执法终端信号相连；
所述云端服务器用于接收、储存、处理和更新所有停车场信息、车辆信息和交易信息；所述停车场信息包括同一停车场的泊位信息、泊位状态信息、泊位异常信息、闸口信息；所述泊位信息至少包括泊位编码(地理位置)、泊位大小、可用时段和泊车时限；所述泊位状态信息保存在泊位编码下，至少包括泊位编码、泊位占用状态、状态改变的时间及状态置信度；所述泊位异常信息至少包括泊位异常状态和对应泊位编码，泊位异常状态至少包括未成功签入、未成功签出、超时泊车、泊位故障和泊位被申请人，所述泊位被申请人指泊位被异常投诉处于审理期间；所述闸口信息包括车辆入场信息、车辆出场信息和闸口异常信息，所述车辆入场信息和车辆出场信息至少包括停车场编码、闸口编码、车牌号和对应进场/出场时间，所述闸口异常信息至少包括停车场编码、闸口编码、对应进场/出场时间以及异常状态；车辆信息至少包括车牌号，以及保存在车牌号下的泊位需求信息、泊位预约信息、泊车信息和车辆被申请人，所述车辆被申请人指车辆被异常投诉处于审理期间；所述泊位需求信息至少包括目的地名称、车牌号、计划泊车起始时间和泊车时长；所述泊位预约信息至少包括所预约的泊位编码、车牌号、计划泊车起始时间和泊车时长；泊车信息至少包括车牌号、泊位编码、签入泊位的时间和签出泊位的时间；
所述管理员终端用于向云端服务器上传泊位信息，监测泊位状态信息和闸口信息，处理异常状态并及时通知管理员；管理员通过管理员终端协助驾驶员进行预约泊位、更改或取消、开启闸机、签入泊位、签出泊位和收费操作，以及通过管理员终端进行采集泊位异常状态时的证据并发送至驾驶员终端进行处理或发送至泊车执法终端进行举报的工作；云端服务器将闸口信息，泊位状态信息、泊位预约信息和交易信息同步给管理员终端；所述签入泊位指驾驶员表达泊车意愿，接受泊车服务与管理条款，确认泊车开始的报告或行动，所述签出泊位指驾驶员承认泊车事实，接受泊车服务与管理条款，确认泊车终止的报告或行动；
所述驾驶员终端用于向云端服务器发送泊位需求信息，进行泊位预约和变更；还用于进行开闸、签入泊位、签出泊位、缴费和延长泊车时长的操作，以及发现泊位异常状态时采集证据并发送至管理员终端或泊车执法终端进行报告、投诉或举报的工作；云端服务器将泊位需求信息、泊位预约信息、进出场信息、泊车信息和交易信息同步给驾驶员终端；
所述车辆检测模块Ⅰ用于检测泊位占用状态，并向云端服务器、管理员终端和驾驶员终端发送泊位状态信息；
所述泊车执法终端用于对违规泊车进行监察；泊车执法终端可查询任一泊位的泊车信息，通过泊车信息与实际车辆停留状态相比对，对违规车辆进行取证、登记和处理；泊车执法终端还能够接收、保存并处理来自管理员终端和驾驶员终端的投诉或举报信息，并在核实投诉或举报信息后对违规车辆进行处理。
作为本发明基于车辆检测的泊位服务与管理系统的改进：
所述泊位服务与管理系统还包括车辆检测模块Ⅱ、车辆检测模块Ⅲ和闸口通讯模块；所述闸口通讯模块分别与车辆检测模块Ⅱ、车辆检测模块Ⅲ、云端服务器、管理员终端和驾驶员终端信号相连；
所述车辆检测模块Ⅱ用于检测车辆与闸口的位置信息，并向闸口通讯模块、管理员终端和驾驶员终端发送车辆接近信息；
所述车辆检测模块Ⅲ用于检测车辆与闸口的位置信息，并向闸口通讯模块发送车辆通过信息；
所述闸口通讯模块用于接收车辆检测模块Ⅱ发送的车辆接近信息、车辆检测模块Ⅲ发送的车辆通过信息，和来自管理员终端或驾驶员终端的开闸命令及车牌号；闸口通讯模块将车牌号、停车场编码和闸口编码绑定后开启闸机；闸口通讯模块向云端服务器发送对应停车场内车辆的进场信息、出场信息和闸口异常信息，云端服务器将对应停车场内车辆的进场信息、出场信息、签入信息和签出信息同步给同一停车场编码下所有的闸口通讯模块。
作为本发明基于车辆检测的泊位服务与管理系统的进一步改进：
所述管理员终端包括管理员PC终端和具有摄像功能的管理员APP(即，管理员APP通过其所在移动终端自带的摄像头实现照片/视频的采集)；
所述驾驶员终端包括驾驶员PC终端和具有摄像功能的驾驶员APP(即，驾驶员APP通过其所在移动终端自带的摄像头实现照片/视频的采集)；
所述管理员APP/驾驶员APP通过摄像功能采集车牌号和车辆违规证据(管理员APP/驾驶员APP通过其所在移动终端自带的摄像头拍摄并自动识别车牌号，从而实现对车牌号的采集)；
所述车辆检测模块Ⅰ位于泊位上，包括依次相连的车辆检测传感器Ⅰ、终端通讯模块Ⅰ和云端通讯模块Ⅰ；
所述泊位服务与管理系统还包括与管理员APP、驾驶员APP、云端通讯模块Ⅰ和云端服务器均相连的泊位中继模块，所述泊位中继模块位于停车场行人出入口，用于中继和放大信号，管理员APP、驾驶员 APP和云端通讯模块Ⅰ均通过泊位中继模块与云端服务器信号相连；
所述车辆检测模块Ⅱ和车辆检测模块Ⅲ位于闸机两侧，车辆检测模块Ⅱ包括依次相连的车辆检测传感器Ⅱ、终端通讯模块Ⅱ和云端通讯模块Ⅱ；车辆检测模块Ⅲ包括相连的车辆检测传感器Ⅲ、终端通讯模块Ⅲ和云端通讯模块Ⅲ；所述车辆检测传感器Ⅰ、车辆检测传感器Ⅱ和车辆检测传感器Ⅲ均用于检测车辆靠近；车辆检测传感器Ⅰ将检测到的泊位占用状态发送至终端通讯模块Ⅰ，终端通讯模块Ⅰ将泊位状态信息发送至云端通讯模块Ⅰ；车辆检测传感器Ⅱ将闸口状态发送至终端通讯模块Ⅱ，终端通讯模块Ⅱ通过云端通讯模块Ⅱ将车辆接近信息发送至闸口通讯模块；车辆检测传感器Ⅲ将闸口状态发送至终端通讯模块Ⅲ，终端通讯模块Ⅲ通过云端通讯模块Ⅲ将车辆通过信息发送至闸口通讯模块；
所述闸口通讯模块接收来自云端通讯模块Ⅱ的开闸使能命令、云端通讯模块Ⅲ的关闸使能，和来自驾驶员终端或管理员终端的开闸命令，并向云端服务器发送闸口信息；
所述终端通讯模块Ⅰ和终端通讯模块Ⅱ分别与管理员APP和驾驶员APP信号相连；所述终端通讯模块Ⅰ用于向管理员APP和驾驶员APP和云端通讯模块Ⅰ发送泊位状态信息和接收泊位预约信息、签入泊位和签出泊位；云端通讯模块Ⅰ用于通过泊位中继模块向云端服务器发送泊车信息和泊位状态信息；所述终端通讯模块Ⅱ用于向管理员APP和驾驶员APP发送闸口车辆接近信息和接收开闸命令；所述云端通讯模块Ⅱ还用于向闸口通讯模块发送开闸使能命令，闸口通讯模块控制闸机开启并向云端服务器发送闸口信息。
作为本发明基于车辆检测的泊位服务与管理系统的进一步改进：
所述闸口通讯模块包括终端通讯模块Ⅴ，以及均与终端通讯模块Ⅴ相连的云端通讯模块Ⅴ、闸口显示模块以及驱动模块，驱动模块与云端通讯模块Ⅴ和闸机信号相连；
所述泊位中继模块包括相连的终端通讯模块Ⅳ和云端通讯模块Ⅳ；
所述终端通讯模块Ⅴ和终端通讯模块Ⅳ均与管理员APP和驾驶员APP信号相连；
所述云端通讯模块Ⅴ分别与云端服务器、云端通讯模块Ⅱ、云端通讯模块Ⅲ、云端通讯模块Ⅳ以及其他云端通讯模块Ⅴ信号相连；
所述云端通讯模块Ⅳ分别与云端服务器、云端通讯模块Ⅰ、云端通讯模块Ⅴ以及其他云端通讯模块Ⅳ信号相连；
所述泊位编码和泊位占用状态事先写入对应终端通讯模块Ⅰ中；所述闸口编码和车辆接近信息事先写入对应终端通讯模块Ⅱ中；所述闸口编码和车辆通过信息事先写入对应终端通讯模块Ⅲ中；
所述云端通讯模块Ⅰ通过云端通讯模块Ⅳ定时向云端服务器发送心跳信息，确认车辆检测模块Ⅰ和泊位中继模块工作正常；所述云端通讯模块Ⅱ和云端通讯模块Ⅲ均通过云端通讯模块Ⅴ定时向云端服务器发送心跳信息，确认车辆检测模块Ⅱ、车辆检测模块Ⅲ和闸口通讯模块工作正常；
所述心跳信息包括对应模块的设备标识、状态变化异常记录、时钟、温度及电池余量；所述设备标识包括泊位编码、闸口编码或模块编码；
所述心跳信息异常时，云端服务器定时向云端通讯模块Ⅳ和云端通讯模块Ⅴ发送管理命令，或向管理员APP和管理员PC终端发送设备异常信息提示维护或更换。
作为本发明基于车辆检测的泊位服务与管理系统的进一步改进：
所述车辆检测传感器Ⅰ、车辆检测传感器Ⅱ和车辆检测传感器Ⅲ采用地磁传感器、红外传感器、超声波传感器或摄像头；
所述摄像头还用于自动识别车牌号(此时泊位状态信息、闸口信息还包括车牌号)；
所述终端通讯模块Ⅰ、终端通讯模块Ⅱ、终端通讯模块Ⅲ、终端通讯模块Ⅳ和终端通讯模块Ⅴ采用蓝牙通讯模块(随着技术发展，蓝牙通讯可能被其他类似通讯方式代替，下同)；
所述云端通讯模块Ⅰ、云端通讯模块Ⅱ、云端通讯模块Ⅲ、云端通讯模块Ⅳ和云端通讯模块Ⅴ采用LORA通讯模块(随着技术发展，Lora通讯可能被其他类似通讯方式代替，下同)。
为了解决上述技术问题，本发明还提供一种基于车辆检测的泊位服务与管理方法；
1.1)、泊位信息公布：管理员或泊位拥有者通过管理员终端将泊位信息于云端服务器上进行公布；所述泊位信息至少包括泊位编码(地理位置)、泊位大小、可用时段和泊车时限；
1.2)、泊位预约信息获取：驾驶员通过驾驶员终端将泊位需求信息上传云端服务器，所述泊位需求信息至少包括目的地名称、车牌号、计划泊车起始时间和泊车时长；云端服务器将所接收的泊位需求信息与泊位信息进行匹配，匹配成功的泊位通过驾驶员终端反馈给驾驶员，驾驶员通过驾驶员终端选择合适的泊位并确认预约，此时云端服务器分别向管理员终端和驾驶员终端反馈泊位预约信息；所述泊位预约信息至少包括泊位编码、车牌号、计划泊车起始时间和泊车时长；
1.3)、泊位占用状态检测：车辆进驻或驶离泊位时，位于泊位上的车辆检测模块Ⅰ检测到泊位占用状态发生改变，此时车辆检测模块Ⅰ向管理员终端、驾驶员终端和云端服务器发送泊位状态信息；所述泊位 状态信息至少包括泊位编码、泊位占用状态以及状态改变的时间(当车辆检测模块Ⅰ可自动识别车牌号时，泊位状态信息还包括车牌号)；
1.3.1)、签入泊位：车辆进驻泊位时，驾驶员终端接收所述步骤1.3)中车辆检测模块Ⅰ发送泊位状态信息，驾驶员终端向驾驶员致欢迎词，显示泊位编码并请求驾驶员签入泊位；驾驶员确认签入泊位时，驾驶员终端首先向车辆检测模块Ⅰ发送车牌号，之后驾驶员终端和车辆检测模块Ⅰ均向云端服务器发送签入信息，所述签入信息至少包括对应泊位编码、车牌号、签入泊位时间、泊车时长以及计划泊车结束时间；云端服务器接收签入信息并根据签入信息中的车牌号进行查询对应的泊位预约信息，将泊位预约信息中泊位编码与签入信息中泊位编码相比对，泊位预约信息中计划泊车起始时间和泊车时长相加的时间段与签入信息中签入泊位的时间比对；比对成功时云端服务器将车牌号和泊位编码绑定，并向管理员终端和驾驶员终端发送成功签入泊位的信息；
1.3.2)、签出泊位：车辆驶离泊位时，首先驾驶员通过驾驶员终端确认签出泊位，此时驾驶员终端向云端服务器发送签出信息，所述签出信息至少包括对应泊位编码、车牌号和签出泊位的时间；云端服务器接收签出信息并根据签出信息的车牌号查询对应的签入信息，将签入信息与签出信息的泊位编码和签出泊位的时间比对；比对成功云端服务器向管理员终端和驾驶员终端发送确认签出泊位的信息；
车辆驶离泊位后，车辆检测模块Ⅰ向管理员终端、驾驶员终端和云端服务器发送泊位状态信息，云端服务器接收泊位状态信息后将车牌号和泊位编码解绑，并将解绑信息发送至驾驶员终端，驾驶员终端接收解绑信息后，发送泊位签出成功信息并向驾驶员致欢送词；
1.4)、云端服务器通过管理员终端提示管理员泊位异常信息，管理员通过管理员终端对泊位进行巡视、取证和处理；所述泊位异常信息至少包括泊位异常状态及对应泊位编码，泊位异常状态至少包括未成功签入泊位、未成功签出泊位和超时泊车。
作为本发明基于车辆检测的泊位服务与管理方法的改进：
所述泊位服务与管理方法还包括针对设有门控机构的停车场的泊位服务与管理方法；所述门控机构包括相连的闸口通讯模块和闸机；
具体步骤包括：
2.1)、闸口状态检测：闸口处设有闸口通讯模块及分别位于闸机两侧的车辆检测模块Ⅱ和车辆检测模块Ⅲ；闸口通讯模块分别与车辆检测模块Ⅱ和车辆检测模块Ⅲ相连；当有车辆靠近闸口时，车辆检测模块Ⅱ检测到闸口处有车，并分别向管理员终端和驾驶员终端发送车辆接近信息；所述车辆接近信息至少包括停车场编码、闸口编码和进场/出场时间；车辆检测模块Ⅲ检测到闸口处车辆通过，车辆检测模块Ⅲ向闸口通讯模块发送车辆通过信息；所述车辆通过信息至少包括停车场编码、闸口编码和进场/出场时间，闸口通讯模块接收到车辆通过信息后控制闸机关闭；
2.1.1)、进入停车场：车辆进入停车场时，驾驶员终端在入口闸口处接收所述步骤2.1)中车辆检测模块Ⅱ发送的车辆接近信息，此时驾驶员终端向驾驶员致欢迎词，显示停车场编码和闸口编码，并提示驾驶员进行开闸操作；驾驶员通过驾驶员终端进行开闸操作时，驾驶员终端首先向车辆检测模块Ⅱ发送车牌号信息，之后驾驶员终端和车辆检测模块Ⅱ分别向闸口通讯模块发送开闸命令、开闸使能命令以及车牌号信息；闸口通讯模块接收到开闸命令、开闸使能命令以及车牌号信息后控制闸机开启；闸机开启后，闸口通讯模块向云端服务器发送车辆入场信息；所述车辆入场信息包括停车场编码、闸口编码、车牌号和进场时间；云端服务器接收、储存和更新车辆入场信息后，向同一停车场编码下的所有闸口通讯模块发送对应车辆入场信息；
2.1.2)、离开停车场；车辆离开停车场时，驾驶员终端在出口闸口处接收所述步骤2.1)中车辆检测模块Ⅱ发送车辆接近信息，驾驶员终端向驾驶员致欢送词，显示停车场编码、闸口编码并提示驾驶员进行开闸操作；驾驶员通过驾驶员终端进行开闸操作时，驾驶员终端首先向车辆检测模块Ⅱ发送车牌号信息，之后驾驶员终端和车辆检测模块Ⅱ分别向闸口通讯模块发送开闸命令、开闸使能命令以及车牌号信息；闸口通讯模块接收开闸命令、开闸使能命令以及车牌号信息后，通过车牌号对车辆入场信息和签出信息进行查询，当查询到对应车辆确认签出泊位操作或在规定的时限内离开时，闸口通讯模块根据车辆检测模块Ⅱ的开闸使能命令和驾驶员终端的开闸命令开启闸机；闸机开启后，闸口通讯模块向云端服务器发送车辆出场信息；所述出场信息包括停车场编码、闸口编码、车牌号和出场时间；云端服务器接收、储存和更新上述信息后，向同一停车场编码下的所有闸口通讯模块发送对应车辆出场信息。
作为本发明基于车辆检测的泊位服务与管理方法的进一步改进：
所述步骤1.3.1)中，驾驶员确认签入泊位时，云端服务器通过签入信息中的车牌号查询未见泊位预约信息，此时驾驶员终端提示驾驶员确认泊位编码和默认的泊车时长，驾驶员可以改变泊车时长后执行签入泊位；云端服务器通过泊位编码查询到对应泊位可用时签入成功，所述泊位可用，表示泊位空闲没有被预约，且签入泊位的泊车时长符合泊位信息中规定的可用时段和泊车时限；否则云端服务器1通过驾驶员终 端提示签入失败、预约其他可用泊位并将车辆挪离泊位。
作为本发明基于车辆检测的泊位服务与管理方法的进一步改进：
所述步骤1.3)中泊位状态信息还包括状态置信度；
步骤1.3.1)车辆驶入泊位时，车辆检测模块Ⅰ检测到泊位占用状态发生改变，车辆检测模块Ⅰ向管理员终端、驾驶员终端和云端服务器发送泊位状态信息；此时泊位状态信息中的泊位占用状态为有车，状态置信度为初始值(50％)；驾驶员成功签入泊位时，云端服务器提高状态置信度(100％)；泊位占用状态保持车辆入驻不变，且状态置信度在规定的时限内无提高(驾驶员未签入泊位)，云端服务器1通过管理员终端提示管理员泊位异常信息，管理员可根据泊位编码前往现场协助驾驶员签入泊位、或提示驾驶员将车辆挪离泊位；
步骤1.3.2)驾驶员确认签出泊位时，云端服务器接收签出信息并将状态置信度重置为初始值(50％)；当车辆驶离泊位，云端服务器接收车辆检测模块Ⅰ发送的泊位状态信息中，泊位占用状态为无车，此时云端服务器再一次提高状态置信度(100％)并更新泊位状态信息；驾驶员确认签出泊位，且状态置信度在规定的时限内无提高，云端服务器通过管理员终端提示管理员泊位异常信息，管理员可根据泊位编码前往现场提示驾驶员将车辆挪离泊位；
当车辆超出签入信息所限定的泊车时长而未有签出信息时，云端服务器通过管理员终端提示管理员泊位异常信息，管理员可根据泊位编码查询并将对应泊位后续泊位预约信息的泊位编码调整到其他可用泊位；
当车辆驶离泊位，云端服务器接收车辆检测模块Ⅰ发送的泊位状态信息中，泊位占用状态为无车，且在规定的时限内未有签出泊位信息时，云端服务器通过管理员终端提示管理员泊位异常信息，管理员可根据泊位编码前往现场确认并代替驾驶员签出泊位或根据签入信息联系驾驶员签出泊位；
管理员前往泊位编码现场且确认泊位异常信息时，管理员通过管理员终端调整泊位状态信息与实际一致；
管理员对泊位异常状态进行调查和处理时，可通过管理员终端采集证据，并将所采集的证据发送至泊车执法终端进行举报；驾驶员发现泊位异常状态，可通过驾驶员终端采集证据，并将所采集的证据发送至管理员终端进行报告，或发送至泊车执法终端进行举报；
当有车辆接近闸口未成功进行开闸操作时，闸口通讯模块向云端服务器发送闸口异常信息；所述管理员终端接收闸口异常信息并根据闸口信息中的闸口编码赶赴闸口现场处理。
作为本发明基于车辆检测的泊位服务与管理方法的进一步改进：
所述管理员终端包括管理员APP和管理员PC终端；
所述驾驶员终端包括驾驶员APP和驾驶员PC终端；
非驾驶员APP和驾驶员PC终端的用户，管理员可通过管理员APP代替用户向云端服务器上传泊位需求信息、获取泊位预约信息、签入泊位、签出泊位、收取泊车费和执行开闸命令；
非驾驶员APP的用户可通过驾驶员PC终端完成相应操作(比如预约泊位，但签入泊位和签出泊位需通过远端的同事、朋友或亲戚代劳)，或管理员通过管理员APP代替用户进行签入泊位、签出泊位和执行开闸命令。
与现有技术相比，本发明的技术优势在于：
1、本发明通过车辆检测和通讯的设计能够确保停车场信息的即时性和准确性；
2、本发明能够兼容驾驶员终端客户和非驾驶员终端客户，还能够兼容预约泊车和即时泊车；
3、本发明提供了泊位共享服务基础工具；
4、本发明结合泊车时限和许可管理，提高泊位流转效率；
5、本发明通过车辆检测、通讯和流程的设计能够确保出入口畅通；
6、本发明对不执行签入泊位/签出泊位或不按照实际执行签入泊位/签出泊位的违规行为，能够通过管理员或其他驾驶员进行取证和举报的操作实现合法的监督和管理手段。
附图说明
下面结合附图对本发明的具体实施方式作进一步详细说明。
图1为本发明基于车辆检测的泊位服务与管理系统的模块连接示意图；
图2为图1中车辆检测模块Ⅰ4的模块连接示意图；
图3为图1中车辆检测模块Ⅱ5的模块连接示意图；
图4为本发明基于车辆检测的泊位服务与管理方法的预约泊位的流程示意图；
图5为本发明基于车辆检测的泊位服务与管理方法的进入停车场开闸的流程示意图；
图6为本发明基于车辆检测的泊位服务与管理方法的离开停车场开闸的流程示意图；
图7为本发明基于车辆检测的泊位服务与管理方法的签入泊位的流程示意图；
图8为本发明基于车辆检测的泊位服务与管理方法的签出泊位的流程示意图。
具体实施方式
下面结合具体实施例对本发明进行进一步描述，但本发明的保护范围并不仅限于此。
实施例1、一种基于车辆检测的泊位服务与管理系统，如图1-3所示，包括云端服务器1，管理员终端2、驾驶员终端3、车辆检测模块Ⅰ4、车辆检测模块Ⅱ5、车辆检测模块Ⅲ、闸口通讯模块6、泊车执法终端7和泊位中继模块8；车辆检测模块Ⅰ4与云端服务器1信号相连，或通过泊位中继模块8与云端服务器1信号相连；车辆检测模块Ⅱ5和车辆检测模块Ⅲ通过闸口通讯模块6与云端服务器1信号相连；闸口通讯模块6与闸机相连构成门控机构。
云端服务器1：用于接收、储存、处理并更新所有停车场信息、车辆信息、交易信息和心跳信息；
停车场信息包括同一停车场的泊位信息、泊位状态信息、泊位异常信息、闸口信息和剩余可用泊位信息；泊位信息至少包括泊位编码(地理位置)、泊位大小、可用时段和泊车时限；根据适用的情况，泊位信息还包括免费/优惠泊车时段或日期、许可证类型及要求、收费政策、使用条款以及处罚规定；泊位状态信息保存在泊位编码下，至少包括泊位编码、泊位占用状态以及状态改变的时间；泊位异常信息至少包括泊位异常状态和对应泊位编码，泊位异常状态至少包括未成功签入、未成功签出、超时泊车、泊位故障和泊位被申请人，其中泊位被申请人指泊位被异常投诉处于审理期间；闸口信息包括车辆入场信息(停车场编码、闸口编码、车牌号和进场时间)、车辆出场信息(停车场编码、闸口编码、车牌号和出场时间)和闸口异常信息，闸口异常信息至少包括停车场编码、闸口编码、对应进场/出场时间以及异常状态，针对驾驶员APP终端客户，闸口异常信息可能还包括车牌号；剩余可用泊位信息为停车场中在车辆计划泊车时段内(计划停车起始时间和计划停车结束时间)可预约泊车或即时泊车的泊位数量总和及对应泊位的泊位信息。签入泊位指驾驶员表达泊车意愿，接受泊车服务与管理条款，确认泊车开始的报告或行动，所述签出泊位指驾驶员承认泊车事实，接受泊车服务与管理条款，确认泊车终止的报告或行动；车辆信息至少包括车牌号，以及保存在车牌号下的泊位需求信息、泊位预约信息、泊车信息和车辆被申请人；车辆被申请人指车辆被异常投诉处于审理期间；泊位需求信息至少包括目的地名称、车牌号、计划泊车起始时间和泊车时长；泊位预约信息至少包括所预约的泊位编码、车牌号、计划泊车起始时间和泊车时长；泊车信息至少包括车牌号、泊位编码、签入泊位时间和签出泊位时间。
交易信息至少包括泊位编码、车牌号、日期和时间、泊车费用、处罚费用等信息。
心跳信息用于实现对本发明泊位服务与管理系统中各硬件设备(包括车辆检测模块Ⅰ4、车辆检测模块Ⅱ5、车辆检测模块Ⅲ、闸口通讯模块6和泊位中继模块8)的监测和维护，由于对上述硬件设备进行监测及维护的内容可因设备的使用环境、供电方式和故障特点而异，以泊位用车辆检测模块4为例，心跳信息包括状态变化异常记录、时钟、温度及电池余量，说明书中也仅以车辆检测模块4的相关心跳信息进行详细描述。车辆检测模块Ⅰ4的心跳信息至少包括车辆检测模块Ⅰ4对应泊位编码(即，设备标识，还可以为设备所对应的闸口编码或模块编号)，以及该模块的状态变化异常记录、时钟、温度及电池余量，其中状态变化异常记录至少包括占用状态、占用状态发生改变的时间或占用状态在规定时限内没有改变，和任何云端服务器1未响应的记录；心跳信息定时发送云端服务器1，当心跳信息异常时，即，云端服务器1在规定周期内未收到心跳信息，此时云端服务器1向异常的模块发送管理命令处理并更新，异常仍未解决时云端服务器1向管理员终端2发送设备异常信息，提示管理员对该设备进行维护或更换；上述管理命令包括时钟校正或优化能源管理方案。
管理员终端2用于编辑并向云端服务器1公布泊位信息，云端服务器1将闸口信息、泊位状态信息、泊位预约信息、泊车信息、交易信息和泊位被申请人信息同步给管理员终端2；管理员终端2包括管理员APP(移动终端)和管理员PC终端(电脑终端)，其中管理员APP用于泊位现场管理，主要包括开启闸机和识别车牌，查看停车场流水和交易信息、泊位平面图和泊位状态信息图；用于协助驾驶员预约泊位、变更或取消、签入泊位、签出泊位和完成现场交易等操作，还用于在出现泊位异常状态时进行拍照采集证据，并将该证据发送至泊车执法终端7举报，然后纠正异常；停车场流水包括闸口编码、车牌号、对应车辆进出场时间，以及泊位编码、对应泊位泊车车辆的车牌号以及签入泊位和签出泊位时间，还包括提前、延误、延长、取消以及泊位再分配等变更；管理员PC终端可用于编辑并公布泊位信息，以及查看停车场流水、交易信息、泊位平面图和泊位状态信息图；
驾驶员终端3包括驾驶员APP(移动终端)和驾驶员PC终端(电脑终端)，上述两个终端用于向云端服务器1提交泊位需求信息，签入泊位、签出泊位，搜索和预约、变更和取消，预约成功后接收由云端服务器1发送的泊位预约信息；其中驾驶员APP可用于向停车场闸口的闸机发送开闸命令实现自主进场和出场，当发现泊位异常状态或违规车辆时，还用于拍照采集证据并发送至管理员终端2或泊车执法终端7进行举报；云端服务器1将剩余可用泊位信息、泊位预约信息、泊车信息、交易信息和车辆被申请人信息同步给驾驶员终端3。
车辆检测模块Ⅰ4位于泊位上，如图2所示，包括依次连接的车辆检测传感器Ⅰ40、终端通讯模块Ⅰ41和云端通讯模块Ⅰ42；车辆检测传感器Ⅰ40用于检测泊位占用状态(有车/无车)，并将状态变化结果发送至终端通讯模块Ⅰ41；终端通讯模块Ⅰ41向云端通讯模块Ⅰ42、管理员APP和驾驶员APP发送泊位状态信息；泊位状态信息中的泊位占用状态和泊位编码事先写入对应车辆检测传感器Ⅰ4中，且终端通讯模块Ⅰ41及云端通讯模块Ⅰ42的软件可以通过终端通讯模块Ⅰ41进行升级；泊位占用状态包括有车和无车两种状态，状态变化异常记录保存在终端通讯模块Ⅰ41中，需要时可进行提取和处理；驾驶员APP签入泊位确认泊位编码和泊车，驾驶员APP向终端通讯模块Ⅰ41发送签入信息并记录于终端通讯模块Ⅰ41中；之后驾驶员APP和云端通讯模块Ⅰ42通过各自的通讯向云端服务器1发送签入信息，以不同的通讯方式发送签入信息以提高泊位状态信息的置信度。
泊位中继模块8包括相连的终端通讯模块Ⅳ和云端通讯模块Ⅳ，本实施例中泊位中继模块8还包括与终端通讯模块Ⅳ相连的以太网模块Ⅰ；泊位中继模块8用于提高通讯的稳定性并降低车辆检测模块4的通讯压力以改善其能源管理，以太网模块I允许同一停车场各泊位中继模块8之间构建局域网进一步提高局域网范围内系统的稳定性和通讯速率；在地下停车场中移动通讯信号较差时，终端通讯模块Ⅳ可协助驾驶员通过泊位中继模块8实现正常的签入泊位和签出泊位操作，且同样能够对设备实行监测、维护和软件升级。通讯环境良好的路内停车场、露天停车场等可不采用泊位中继模块8，云端通讯模块Ⅰ42直接与云端服务器1进行通讯。
本实施例中云端通讯模块Ⅰ42通过泊位中继模块8(一个或多个)和LORA通讯或以太网通讯的方式与云端服务器1信号相连，云端通讯模块Ⅰ42接收由终端通讯模块Ⅰ41所发送的泊车信息(即，签入信息和签出信息)并将该信息通过云端通讯模块Ⅳ发送至云端服务器1。终端通讯模块Ⅰ41与驾驶员APP和管理员APP通过蓝牙建立通讯，云端通讯模块Ⅳ通过LORA通讯分别与云端通讯模块Ⅰ42和云端服务器1建立联系，以太网模块Ⅰ和同一停车场下的其他泊位中继模块8的以太网模块Ⅰ、闸口通讯模块6的以太网模块Ⅱ以及本地服务器建立局域网以太网通讯。泊位中继模块8安装在有利于LORA通讯的停车场人流集散地，比如地下停车场的电梯大厅，一方面便于与泊位现场的云端通讯模块Ⅰ42建立通讯联系，另一方面针对泊位现场通讯失败的情形，此时，驾驶员可以在通信信号更为通畅的电梯大厅和利用泊位中继模块8签入泊位。云端通讯模块Ⅰ42还通过泊位中继模块8(即，云端通讯模块Ⅳ)定时向云端服务器1发送心跳信息，从而实现对设备的管理和维护。
车辆检测模块Ⅱ5和车辆检测模块Ⅲ位于闸机两侧，如图3所示，车辆检测模块Ⅱ5包括相连的车辆检测传感器Ⅱ50、终端通讯模块Ⅱ51和云端通讯模块Ⅱ52；车辆检测传感器Ⅱ50用于检测闸口状态，并将状态变化结果发送至终端通讯模块Ⅱ51；终端通讯模块Ⅱ51接收该信息后向管理员APP和驾驶员APP发送车辆接近信息。驾驶员APP接收终端通讯模块Ⅱ51发出的车辆接近信息后向驾驶员致欢迎词并提示开闸操作，驾驶员可通过驾驶员APP操作“开闸”命令以确认停车场编码和进场/出场，此时驾驶员APP分别向终端通讯模块Ⅱ51和闸口通讯模块6发送开闸命令、闸口编码和车牌号；其中驾驶员APP向闸口通讯模块6发送开闸命令、车牌号和闸口编码后，闸口通讯模块6将其车牌号保存至待开闸的队列中；驾驶员APP向终端通讯模块Ⅱ51发送开闸命令、车牌号和闸口编码后，终端通讯模块Ⅱ51通过云端通讯模块Ⅱ52向闸口通讯模块6发送车牌号、闸口编码和开闸使能命令；闸口通讯模块6将来自云端通讯模块Ⅱ52开闸使能命令和来自驾驶员APP的开闸命令相比对，比对成功后打开对应闸机，从而防止了多个车辆的开闸误操作，即，避免了下达开闸命令的车辆与进/出停车场的车辆不对应的情况。车辆接近信息事先写入终端通讯模块Ⅱ51中。
车辆检测模块Ⅲ包括依次连接的车辆检测传感器Ⅲ、终端通讯模块Ⅲ和云端通讯模块Ⅲ；车辆检测传感器Ⅲ用于检测闸口状态，并将状态变化结果发送至终端通讯模块Ⅲ；终端通讯模块Ⅲ接收后通过云端通讯模块Ⅲ向闸口通讯模块6发送车辆通过信息，实现自动关闸的使能。车辆通过信息事先写入对应终端通讯模块Ⅲ中。
闸口通讯模块6包括终端通讯模块Ⅴ，以及均与终端通讯模块Ⅴ信号相连的云端通讯模块Ⅴ、闸口显示模块和驱动模块，其中驱动模块与闸机相连，用于控制闸机的开关；本实施例中闸口通讯模块6还包括与终端通讯模块Ⅴ信号相连的以太网模块Ⅱ，同一停车场编码下的以太网模块Ⅱ、泊位中继模块8的以太网模块Ⅰ以及本地服务器共同建立局域网以太网通讯，进一步提高局域网范围内的通讯速度和闸口效率，确保了本发明泊车服务与管理系统的即时性和准确性。闸口显示模块用于显示停车场名称、闸口编码和剩余可用泊位信息，当车辆接近和闸机开启时，同时或切换显示车牌号及欢迎信息，当车辆通过和闸机关闭时，同时或切换显示车牌号及欢送词。
闸口通讯模块6位于停车场入口时，驾驶员APP、管理员APP分别向终端通讯模块Ⅱ51和终端通讯模块Ⅴ发送开闸命令，由于驾驶员APP或管理员APP开闸时工作内容相同，故说明书中仅对驾驶员APP开闸操作进行详细介绍；终端通讯模块Ⅱ51接收开闸命令后通过云端通讯模块Ⅱ52向云端通讯模块Ⅴ发 送开闸使能命令，云端通讯模块Ⅴ接收并将其发送至驱动模块；终端通讯模块Ⅴ将其所接收到的开闸命令发送至驱动模块，驱动模块获得车牌号一致的开闸命令和开闸使能命令后，驱动对应的闸机开启；此时终端通讯模块Ⅴ记录车辆入场信息，并通过云端通讯模块Ⅴ将车辆入场信息发送云端服务器1，云端服务器1记录车辆入场信息，并将车辆入场信息同步给同一停车场编码下的所有云端通讯模块Ⅴ；本实施例中车辆入场信息还可以通过以太网模块Ⅱ实现车辆入场信息的快速同步。
闸口通讯模块6位于停车场出口时，终端通讯模块Ⅴ依据所储存的对应车辆的车辆入场信息和泊车信息判断是否满足车辆出场条件；满足出场条件时终端通讯模块Ⅴ将开闸命令和车牌号发送至驱动模块，驱动模块获得车牌号一致的开闸命令和开闸使能命令后，控制闸机开启。此时终端通讯模块Ⅴ记录车辆出场信息，终端通讯模块Ⅴ通过云端通讯模块Ⅴ将车辆出场信息发送至云端服务器1，云端服务器1记录车辆出场信息，并将车辆出场信息同步给同一停车场编码下的所有云端通讯模块Ⅴ；不满足出场条件时终端通讯模块Ⅴ不将开闸命令发送至驱动模块并记录闸口异常信息，终端通讯模块Ⅴ通过云端通讯模块Ⅴ将闸口异常信息发送至云端服务器1，云端服务器1记录闸口异常信息，并向驾驶员APP和管理员APP反馈闸口异常信息，从而根据实际情况向驾驶员提供明确的指令或令管理员及时处置；本实施例中车辆出场信息或闸口异常信息还可以通过以太网模块Ⅱ实现车辆出场信息的快速同步。
驱动模块依据云端通讯模块Ⅲ通过云端通讯模块Ⅴ向其发送的车辆通过信息，驱动闸机关闭，关闭过程中驱动模块收到车牌号一致的开闸使能命令和开闸命令将使关闸使能无效而重新开启闸机，直至收到新的自动关闸的使能再彻底关闭闸机，以避免车流量大时车辆与闸机的干涉。
云端通讯模块Ⅱ和云端通讯模块Ⅲ均分别通过闸口通讯模块6(即，云端通讯模块Ⅴ)定时向云端服务器发送心跳信息，确认车辆检测模块Ⅱ、车辆检测模块Ⅲ和闸口通讯模块6工作正常。
本实施例中驾驶员APP利用移动通讯与云端服务器1信号相连发送闸口状态信息，闸口通讯模块6通过云端通讯模块Ⅴ利用LORA通讯或通过以太网模块Ⅱ利用以太网通讯与云端服务器1信号相连发送闸口状态信息，以不同的通讯方式发送闸口状态信息从而提高停车场出入口的效率和闸口状态信息的置信度。
上述车辆检测传感器Ⅰ40、车辆检测传感器Ⅱ50和车辆检测传感器Ⅲ可采用地磁传感器、超声波传感器、红外传感器和摄像头等常用的车辆检测或车牌识别传感器；当采用摄像头或其他车牌识别传感器时，在检测车辆靠近情况的同时还对车牌进行自动识别，此时泊位状态信息、闸口信息还包括车牌号，且当车辆违规泊车或离开停车场时，摄像头将违规车辆的信息，包括车牌号、位置(即摄像头安装地理位置)、时间等，自动上传云端服务器1，而无需管理员或其他驾驶员采集证据。
地磁传感器适合严酷等级高和要求低能耗管理的电池供电场合如路内停车场泊位节点，超声波传感器、红外传感器和摄像头适合严酷等级要求不高和可采用市电供电的场合，如停车场进出口或室内泊位结点。上述终端通讯模块Ⅰ41、终端通讯模块Ⅱ51、终端通讯模块Ⅲ、终端通讯模块Ⅳ和终端通讯模块Ⅴ可采用低功耗蓝牙(BLE)等可直接连接应用终端的通讯模块；上述云端通讯模块Ⅰ42、云端通讯模块Ⅱ52、云端通讯模块Ⅲ、云端通讯模块Ⅳ和云端通讯模块Ⅴ可采用专用短程通讯模块(DSRC)和低功耗广域网通讯模块(LPWAN)，如LORA(基于扩频技术的超长距低功耗数据传输技术)、NBIoT(基于蜂窝的窄带物联网)等云端服务器1可直接或间接连接的通讯模块。
本实施例中车辆检测传感器Ⅰ40、车辆检测传感器Ⅱ50、车辆检测传感器Ⅲ均采用地磁传感器，终端通讯模块Ⅰ41、终端通讯模块Ⅱ51、终端通讯模块Ⅲ、终端通讯模块Ⅳ和终端通讯模块Ⅴ采用蓝牙通讯模块；云端通讯模块Ⅰ42、云端通讯模块Ⅱ52、云端通讯模块Ⅲ、云端通讯模块Ⅳ和云端通讯模块Ⅴ采用LORA通讯模块。由于车辆检测模块Ⅰ4、车辆检测模块Ⅱ5和车辆检测模块Ⅲ的工作原理均相同，故说明书中仅对车辆检测模块Ⅰ4的工作原理进行详细阐述；
车辆检测模块Ⅰ4在工作过程中，其地磁传感器处于周期性的检测状态，地磁传感器检测期间，蓝牙通讯模块和LORA通讯模块停止工作；为了避免其他干扰造成的算法误判和确保车辆检测稳定可靠，可采用具有X、Y、Z三轴的地磁传感器来获取地磁场数据，并利用多状态机算法来判断车辆是否停泊。具体方法为，将X、Y、Z三轴的数据存储，在有车状态和无车状态两个稳定状态之间设置多个缓冲状态，当磁场数据出现变化且变化的差值超过规定的域值，算法首先进入缓冲状态，若磁场数据变化的持续时间足够长则系统进入到下一个稳定状态，若扰动持续短时间后又返回原始状态，则系统返回之前的稳定状态。在有车状态和无车状态两个状态，即泊位占用状态发生稳定改变时，停止地磁检测，状态改变的结果将蓝牙通讯模块从休眠中唤醒并启动其向驾驶员APP和管理员APP发送泊位状态信息，位于附近的驾驶员APP或管理员APP接收泊位状态信息，计划泊车的驾驶员操作驾驶员APP确认泊位编码和泊车，驾驶员APP将车牌号通过蓝牙发送至蓝牙通讯模块，蓝牙通讯模块接收并保存车牌号；驾驶员APP通过移动通讯将签入信息/签出信息发送至云端服务器1；蓝牙通讯模块通过LORA通讯模块将泊位状态信息和车牌号发送至云端服务器1，云端服务器1反馈成功接收信息后，驾驶员APP显示成功签入信息/签出信息，车辆检测模 块Ⅰ4的蓝牙通讯模块和LORA通讯模块进入休眠，地磁传感器恢复至周期性的检测状态。
如果LORA通讯模块由于设备异常或通讯中断未能从云端服务器1收到成功接收信息的反馈，LORA通讯模块将根据能源管理的安排再次尝试发送信息，包括随心跳信息发送的状态变化异常记录；心跳信息异常，即，超过24小时未收到心跳信息，占用状态与实际不符(短时间内反复变化或24小时内没有变化)，或电池余量不足等，此时云端服务器1通过管理员终端2通知管理员前往泊位编码对应的现场查看和处理，包括通过蓝牙提取状态变化异常记录、更换电池或更换设备。驾驶员APP与车辆检测模块Ⅰ4同步分头通讯可以弥补设备异常或通讯中断带来的信息丢失、滞后或错误。能源管理相关的地磁检测周期、通讯休眠以及心跳信息的部分数据和时限取决于具体应用、电池容量和期望的电池寿命，当采用其他非电池供电的车辆检测传感器时可以不考虑休眠和能源管理。
泊车执法终端7：泊车执法终端7用于对停泊车辆进行监察；泊车执法终端7可查询任一泊位的泊车信息，通过泊车信息与实际车辆停留状况相比对，对违规车辆进行取证、登记和处理；泊车执法终端7还能够接收、保存并处理来自管理员终端2和驾驶员终端3的投诉和举报信息，并在核实投诉或举报信息后对违规车辆进行处理。本实施例中泊车执法终端7与相关监察部门相联通，例如道路交通警察部门、城市市容管理部门或街道办事处等可通过泊车执法终端7接收对违规车辆的投诉并监察上述损害公共泊位、共享泊位正常泊车秩序的违规行为，从而改善泊车服务与管理。
如图4-6所示，通过上述系统实现基于车辆检测的泊位服务与管理方法，具体工作内容如下：
注：由于驾驶员APP与驾驶员PC终端，管理员APP与管理员PC终端，以及泊车执法APP与泊车执法PC终端工作内容相同，因此下述泊位服务与管理系统及方法中仅详细描述驾驶员APP、管理员APP和泊车执法APP的工作内容。
支付费用是泊位服务与管理系统及方法中交易信息的基本组成部分，根据停车场的费用政策，驾驶员可以在预约泊位、签入泊位、签出泊位或离开停车场时支付费用，支付方式包括银行卡、电子钱包等任意一种可靠成熟的支付手段，因此在本说明书中进行省略。
1、泊位信息公布：停车场管理员或泊位拥有者通过管理员APP，将泊位信息公布云端服务器1，泊位信息至少包括泊位编码、泊位大小、可用时段和泊车时限；其中泊位编码具有唯一性，有利于确定停车场的归属和泊位的具体位置，泊位大小与车辆的车型相匹配，可用时段规定了泊位可以预约或泊车的时间段，以便于路内泊位的管理以及个人和组织泊位的共享管理，泊车时限规定了可以泊车的最长时间，以改善泊位的流转效率；泊位信息还可以包括泊位的费用政策、许可条件和处罚规则等信息，其中费用政策包括免费时段或时长、分钟或小时费率、日最大费率、周费率或月费率标准等；许可条件包括残疾人、居住证、工作证、优待证、访客证、家长证、快递、送货/提货、接客/送客、专车、出租车等许可证；处罚规则包括未签入泊位、未签出泊位、超时占用泊位，超时滞留泊位、超时滞留停车场，以及在非泊位范围内泊车等。根据问题性质的严重程度和规则，泊位被申请人将无法被驾驶员搜索和预约。
2、泊位预约：如图4所示，驾驶员通过驾驶员APP，将泊位需求信息上传云端服务器1，泊位需求信息至少包括目的地名称，车牌号，计划泊车起始时间和泊车时长。云端服务器1比较泊位需求信息和泊位信息，如图4所示，具体比较的内容包括：目的地名称和泊位编码(泊位所在具体位置)相比较、泊车时长与泊车时限相比较，计划泊车起始时间与可用时段相比较，计划泊车起始时间和泊车时长相加后的时间段(即，计划泊车结束时间)与可用时段相比较；云端服务器1将可用泊位的泊位信息通过驾驶员APP反馈给驾驶员；可用泊位，表示泊位空闲没有被预约，且签入泊位的泊车时长符合泊位信息中规定的可用时段和泊车时限；驾驶员通过驾驶员APP从泊位信息中选择合适的泊位进行预约，云端服务器1向驾驶员和停车场管理员/泊位拥有者反馈泊位预约信息，即，云端服务器1将泊位预约信息分别发送至管理员APP和驾驶员APP。根据问题性质的严重程度和规则，车辆被申请人可能无法预约泊位。
3、车辆进入停车场：当停车场具有门控机构时，即，具有相连的闸口通讯模块6和闸机时，闸口通讯模块6分别与位于闸机两侧的车辆检测模块Ⅱ5和车辆检测模块Ⅲ相连；当有车辆靠近闸口时，其中车辆检测模块Ⅱ5中的车辆检测传感器Ⅱ50检测到车辆靠近，将信号发送至终端通讯模块Ⅱ51，终端通讯模块Ⅱ51向驾驶员APP和管理员APP分别发送车辆接近信息，车辆接近信息至少包括停车场编码、闸口编码和进场/出场时间；闸口通讯模块6根据驾驶员或管理员的指令控制闸机开启；车辆检测模块Ⅲ中车辆检测传感器Ⅲ检测到车辆通过闸机，车辆检测模块Ⅲ向闸口通讯模块6发送车辆通过信息；闸口通讯模块6接收到车辆通过信息后控制闸机关闭，如图5所示，具体包括如下步骤；
驾驶员确认进场，此时驾驶员通过驾驶员APP操作“开闸”按钮，驾驶员APP分别向终端通讯模块Ⅴ和终端通讯模块Ⅱ51发送开闸命令和车牌号信息；
终端通讯模块Ⅴ接收来自驾驶员APP的开闸命令和车牌号信息后并将其发送至驱动模块；驱动模块接收开闸命令和车牌号后将该车牌号加入待开闸的队列中；终端通讯模块Ⅱ51接收来自驾驶员APP的开闸 命令和车牌号信息后，通过云端通讯模块Ⅱ52向云端通讯模块Ⅴ发送车牌号、闸口编码和开闸使能命令，云端通讯模块Ⅴ接收并将其发送至驱动模块；驱动模块将来自云端通讯模块Ⅱ52开闸使能命令和来自驾驶员APP的开闸命令相比对，比对成功后控制闸机开启。闸口显示模块显示停车场名称、闸口编码和剩余可用泊位信息，当车辆接近和闸机开启时，同时或切换显示车牌号及欢迎信息；同时终端通讯模块Ⅴ通过车牌号检索该车辆泊位预约信息，如果该停车场没有剩余可用泊位且该车辆未预约泊位，或该车辆到达时间与计划泊车起始时间不符，此时终端通讯模块Ⅴ通过驾驶员APP和闸口显示模块向驾驶员提示需在规定的时限内离开停车场，该时限由停车场根据实际情况自行确定。上述情况中，如车辆未预约泊位但停车场中有可用泊位，闸口通讯模块6可向驾驶员APP发送可用泊位信息，驾驶员仅需要确认泊位编码和泊车时长即可实现即时泊车，驾驶员仅需在签出泊位后在限定的时间内离开停车场即可；驾驶员进入停车场后对可用的泊位进行预约或延长泊车时长并成功的，驾驶员仅需在所预约或延长的泊车时长内离开停车场即可。
闸机开启后，云端通讯模块Ⅴ向云端服务器1发送车辆入场信息；云端服务器1接收、储存和更新车辆入场信息后，之后向同一停车场编码下的所有闸口通讯模块6的云端通讯模块Ⅴ发送该车辆入场信息。
当驾驶员无驾驶员APP或不熟悉驾驶员APP的操作时，即，驾驶员无法通过驾驶员APP操作“开闸”按钮，此时可以在闸口处等候管理员通过管理员APP协助开闸，具体步骤为；
当有车辆靠近闸口时，闸口状态发生改变，车辆检测传感器Ⅱ50通过终端通讯模块Ⅱ51向管理员APP和驾驶员APP发送车辆接近信息，此时闸口信息中的闸口状态为有车辆；当闸口状态在规定的时间内未从有车辆更新为无车辆时，即，管理员APP在规定的时间内未收到闸口状态再一次改变的信息，表示驾驶员未进行“开闸”操作，车辆仍停留在闸机处，此时提示管理员闸口异常信息，管理员可管理员终端接收闸口异常信息并根据闸口信息中的闸口编码赶赴闸口现场协助驾驶员打开闸机，即，管理员可通过管理员APP的摄像功能(即，通过管理员APP所在移动终端自带的摄像头)采集车牌号，并将车牌号和开闸命令通过终端通讯模块V发送至驱动模块，对应车辆进入停车场；由于管理员操作开启闸机明确指向特定的车牌号和闸口编码，本发明规定由管理员APP发送的开闸命令和车牌号直接通过终端通讯模块V发送至驱动模块，驱动模块根据所接收开闸命令和车牌号控制闸机开启而无需开闸使能命令的验证。
注：停车场闸口为入口处时，用于检测车辆接近情况的车辆检测模块Ⅱ5位于闸机外侧(远离停车场的一侧)，终端通讯模块Ⅱ51与管理员APP和驾驶员APP建立通讯，从而实现开闸动作；用于检测车辆通过闸机情况的车辆检测模块Ⅲ位于闸机内侧(靠近停车场的一侧)，当车辆检测传感器Ⅲ检测到车辆消失时，表示车辆已通过闸机，此时云端通讯模块Ⅲ向云端通讯模块Ⅴ发送车辆通过信息从而实现关闸动作。
驱动模块依据云端通讯模块Ⅲ通过云端通讯模块Ⅴ向其发送的车辆通过信息，即自动关闸的使能，驱动闸机关闭，关闭过程中驱动模块收到的任何与车牌号一致的开闸使能命令和开闸命令将使关闸使能无效而重新开启闸机(不具备开闸条件的跟车可能造成车辆与闸机的干涉)，直至收到新的自动关闸的使能再彻底关闭闸机，以避免车流量大时车辆与闸机的干涉。
在实际应用中可根据情况对本实施例变形，例如将本实施例中的作用在闸口处控制车辆进出停车场的闸口通讯模块6变更为作用在具体泊位控制车辆进出泊位的泊位锁(泊位锁位于泊位范围内的一个区域)，其余等同本实施例；具体工作过程中，泊位锁接收车辆检测模块I发送的车辆接近信息和车辆离开信息，以及来自驾驶员APP的开锁命令和车牌号；泊位锁将车牌号、停车场编码和泊位锁编码绑定后收起泊位锁，解绑后弹出泊位锁；泊位锁向云端服务器1发送对应泊位车辆的入驻泊位信息和驶离泊位信息。针对泊位锁的收起和弹出，开闸命令和签入泊位/签出泊位同步完成，换言之，进驻泊位的开锁命令与签入泊位命令同步完成，驶离泊位的弹出泊位锁的命令与签出泊位命令同步完成。
4、车辆驶入泊位：泊位上设有车辆检测模块Ⅰ4，当有车辆靠近时，车辆检测模块Ⅰ4中车辆检测传感器Ⅰ40检测到泊位占用状态改变，即，泊位占用状态由无车改变为有车，此时车辆检测传感器Ⅰ40将信号发送至终端通讯模块Ⅰ41，终端通讯模块Ⅰ41收到该信号后分别向云端通讯模块Ⅰ42、驾驶员APP和管理员APP发送泊位状态信息；云端通讯模块Ⅰ42将所收到的泊位状态信息通过泊位中继模块8的云端通讯模块Ⅳ发送至云端服务器1。
驾驶员APP接收上述泊位状态信息后向驾驶员致欢迎词，弹出泊位编码并请求驾驶员签入泊位；为避免通讯异常或设备故障，驾驶员APP和车辆检测模块Ⅰ4首先通过终端通讯模块Ⅰ41交换泊位编码和车牌号信息，然后通过自身的通讯向云端服务器1发送签入信息；具体签入泊位步骤为，驾驶员确认签入泊位时，驾驶员APP向终端通讯模块Ⅰ41发送车牌号，之后驾驶员APP通过移动通讯向云端服务器1发送签入信息；终端通讯模块Ⅰ41将签入信息发送至云端通讯模块Ⅰ42，云端通讯模块Ⅰ42接收签入信息并通过泊位中继模块8的云端通讯模块Ⅳ向云端服务器1发送签入信息；签入信息至少包括对应泊位编码、车牌号、签入泊位时间及计划泊车结束时间；
云端服务器1接收签入信息并根据签入信息中的车牌号进行查询对应的泊位预约信息，将查询到的泊位预约信息与所接收的泊位编码和签入泊位的时间进行比对，具体对比内容为预约的泊位编码和实际签入 的泊位编码相比对，计划泊车起始时间与实际签入泊位的时间相比对；比对成功时云端服务器1将车牌号和泊位编码绑定，并向驾驶员APP和管理员APP发送成功签入泊位信息；不能成功签入泊位时，向驾驶员APP发送签入泊位不成功的理由和后续操作要求；
以上泊位状态信息包括泊位编码、泊位占用状态、状态置信度和状态改变的时间等信息；当车辆检测传感器Ⅰ40、车辆检测传感器Ⅱ50和车辆检测传感器Ⅲ采用摄像头或其他车牌识别传感器时，泊位状态信息还包括车牌号。
如图7所示，车辆入驻泊位时，云端通讯模块Ⅰ42向云端服务器1发送泊位状态信息，泊位占用状态为有车，状态置信度为初始值，本实施例中设初始值为50％；云端服务器1接收、储存并更新泊位状态信息，同时将更新后的泊位状态信息发送至管理员APP，管理员APP同步更新。车辆成功签入泊位后，即云端服务器1接收该车辆的签入信息并匹配成功，将对应车牌号和泊位编码绑定，此时云端服务器1将提高状态置信度至100％；在实际工作过程中，泊位占用状态发生改变后云端服务器1将判断对应泊位是否成功签入泊位，如成功签入泊位则将状态置信度提高至100％；驾驶员可先签入泊位再入驻泊位，当车辆进驻泊位时云端服务器1根据泊位编号查询到对应泊位已经成功签入，云端服务器1将状态置信度立即提高至100％；如在规定的时限内仍未达到一致，即，车辆进驻泊位后未在规定的时间内成功签入泊位，则云端服务器1通过管理员APP提示管理员泊位异常占用信息。
以上管理员APP，当管理员就在车辆入驻泊位的附近时，可以立刻收到更新的泊位状态信息。
即时泊车：当驾驶员确认签入泊位时，云端服务器1未通过签入信息中的车牌号查询到泊位预约信息，此时驾驶员APP提示驾驶员确认泊位编码和默认的泊车时长，驾驶员可以改变泊车时长后执行签入泊位；云端服务器1通过泊位编码查询到对应泊位可用时签入泊位成功，否则云端服务器1通过驾驶员APP提示签入泊位失败，请预约其他可用泊位并离开。泊位可用表示该泊位所预约的泊车时长没有被他人预约，且符合该泊位的可用时段(如共享泊位所设定08:00—16:00内可泊车)及泊位时限(如路内泊车设定最大可停留时间为1小时)，预约其他可用泊位的操作可根据步骤2泊位预约实现。
当驾驶员无驾驶员APP时，可通过同事、亲戚或朋友操作驾驶员PC终端向云端服务器1发送签入信息，或在泊位现场等候管理员前来协助签入泊位的操作；其中驾驶员PC终端签入泊位的操作与驾驶员APP相同，故不再详述；
管理员协助签入泊位的具体操作方式为：当车辆进驻泊位时终端通讯模块Ⅰ41将泊位状态信息发送至管理员APP，或云端服务器1接收泊位状态信息进行更新后，定时将该信息发送至管理员APP使其更新(实时同步更新管理员APP中泊位状态信息，并避免终端通讯模块Ⅰ41向管理员APP发送信息失败，比如受通讯距离限制)，此时泊位状态信息中的状态置信度为初始状态，本实施例中设状态置信度初始状态为50％，当驾驶员在规定的时限内(例如15min)未进行“签入泊位”的操作，此时泊位占用状态为有车，状态置信度未提高，仍为初始值50％，此时管理员终端2提示管理员泊位异常占用信息，包括泊位编码以及占用情况(未成功签入泊位)，管理员根据泊位编码前往对应泊位协助驾驶员进行“签入泊位”操作，具体可分为以下两种情况；
4.1、驾驶员已通过驾驶员终端3预约泊位：管理员可通过管理员APP根据步骤4)中“签入泊位”操作协助驾驶员完成签入泊位；
4.2、驾驶员未预约泊位(即时泊车)：管理员可通过管理员APP根据步骤4)即时泊车的操作，将泊位编码、车牌号及泊车时长上传至云端服务器1；
该泊位已被预约时，则管理员可通过管理员APP根据步骤2)协助驾驶员签入其他可用泊位，或更改该泊位后续预约者所预约的泊位编码(即驾驶员已经离开不能对车辆进行挪离时，管理员可更改后续泊位预约者所预约的泊位编码，并及时通知后续驾驶员变更后的泊位预约信息)；预约成功后，管理员可通过管理员APP根据步骤4)中“签入泊位”操作协助驾驶员完成签入泊位；管理员协助驾驶员签入泊位时，可通过管理员APP的摄像功能实现自动识别并录入车牌号，提高工作效率和数据录入准确性。
车辆违规泊车被投诉或举报后，根据问题性质的严重程度和规则，车辆被申请人可能无法即时泊车。
5、车辆驶离泊位：
车辆驶离泊位时，驾驶员通过驾驶员APP确认签出泊位，此时驾驶员APP向云端服务器1发送签出信息，该签出信息包括对应泊位编码、车牌号和签出泊位的时间；云端服务器1接收签出信息并根据签出信息的车牌号查询对应的签入信息，将签入信息与所接收的泊位编码和签出泊位的时间比对；比对成功云端服务器1向管理员APP和驾驶员APP发送确认签出泊位信息；此时云端服务器1接收签出信息并重置状态置信度为初始值50％；如图8所示，当驾驶员将车辆驶离泊位，车辆检测模块Ⅰ4中车辆检测传感器Ⅰ40检测到泊位占用状态改变，即，泊位占用状态由有车改变为无车，此时车辆检测传感器Ⅰ40将信号发送至终端通讯模块Ⅰ41，终端通讯模块Ⅰ41收到该信号后分别向云端通讯模块Ⅰ42、驾驶员APP和管理员APP发送泊位状态信息；云端服务器1接收泊位状态信息后将车牌号和泊位编码解绑，并将解绑信息 发送至驾驶员APP，驾驶员APP接收解绑信息后，发送泊位签出成功信息并向驾驶员致欢送词；云端通讯模块Ⅰ42将所收到的泊位状态信息通过泊位中继模块8的云端通讯模块Ⅳ发送至云端服务器1，云端服务器1接收泊位状态信息并更新泊位占用状态为无车，当驾驶员完成签出操作后所规定的时限内泊位占用状态为无车，云端服务器1提高状态置信度至100％，并将车牌号和泊位编码解绑；在实际工作过程中，签出成功后云端服务器1将判断泊位占用状态是否与实际一致，如一致则将状态置信度提高至100％，或者，用户可先驶离再签出泊位，在车辆签出泊位成功后泊位占用状态与实际一致时，云端服务器1立即将状态置信度提高至100％，如在规定的时限内仍未达到一致，则云端服务器1通过管理员APP提示管理员泊位异常占用信息。
当驾驶员确认签出泊位后，状态置信度在规定的时间内无提高，此时管理员APP提示管理员泊位异常占用信息，管理员可根据泊位编码前往现场进行签出泊位；不能成功签出泊位时，向驾驶员APP发送签出泊位不成功的理由和后续操作要求；
当驾驶员无驾驶员APP时，可在泊位等候管理员前来协助“签出泊位”的操作；具体操作方式为：当车辆驶离泊位时终端通讯模块Ⅰ41将泊位状态信息发送至管理员APP，或云端服务器1接收泊位状态信息进行更新后，定时将该信息发送至管理员APP使其更新(避免终端通讯模块Ⅰ41向管理员APP发送信息失败)，此时云端服务器1设置泊位状态信息中的状态置信度为50％，当驾驶员在规定的时限内(例如15min)未进行“签出泊位”的操作，即状态置信度不变，此时管理员APP提示管理员泊位异常占用信息，包括泊位编码以及占用情况(未签出泊位)，管理员根据泊位编码前往对应泊位协助驾驶员进行缴费以及“签出泊位”操作。如驾驶员未在泊位处等待管理员前往协助进行“签出泊位”的操作，管理员根据泊位异常占用信息(泊位无车且未签出泊位)前往泊位进行签出泊位操作，并根据驾驶员违规情节的严重程度进行记录和举报。
注：驾驶员完成确认签出泊位后，云端服务器1将对应车辆的签出信息发送至同一停车场的所有闸口通讯模块6的云端通讯模块Ⅴ；
本实施例中在停车场行人进出口处还设有用于协助驾驶员或管理员完成签入泊位和签出泊位的泊位中继模块8，驾驶员APP、管理员APP以及云端通讯模块Ⅰ42均通过泊位中继模块8的云端通讯模块Ⅴ与云端服务器1信号相连，即，上述驾驶员APP、管理员APP以及云端通讯模块Ⅰ42均通过泊位中继模块8的云端通讯模块Ⅴ向云端服务器1发送信息，云端服务器1则通过泊位中继模块8的云端通讯模块Ⅴ向驾驶员APP、管理员APP以及云端通讯模块Ⅰ42发送信息，有利于节点的能源管理和系统的稳定性。不是所有应用场合需要泊位中继模块8，例如路内停车场和露天停车场的云端通讯模块Ⅰ42信号畅通时，可以不用泊位中继模块8实现云端通讯模块Ⅰ42和云端服务器1的直接通讯。
上述状态置信度，即，车辆检测模块Ⅰ4变更泊车状态信息的状态置信度和由驾驶员进行签入操作或签出操作时变更泊车状态信息的状态置信度均可根据实际工作需求在0％～100％之间调整，例如停车场管理员可以根据驾驶员对签入泊位和签出泊位习惯的程度，如，驾驶员从未乱停乱占，并根据本发明的步骤进行泊车，则令来自该驾驶员的签入信息和签出信息的状态置信度为100％，或者根据车辆检测模块Ⅰ4以及通讯的可靠性程度，令来自车辆检测模块Ⅰ4的泊位状态信息的状态置信度为100％；停车场管理员/泊位拥有者可根据实际情况将泊位上车辆检测模块Ⅰ4所更新泊位状态信息时状态置信度的比例在0％～100％之间调整；同理云端服务器1可根据对应车辆历史泊车信息和交易信息等信息，将来自该驾驶员的签入信息和签出信息的状态置信度的比例在0％～100％之间调整；当假定签入信息和签出信息的状态置信度为100％，可以忽略对车辆检测模块Ⅰ4的要求。
6、车辆离开停车场：
如图6所示，停车场出口处的车辆检测传感器Ⅱ50检测到车辆靠近时，将有车辆靠近的信号发送至终端通讯模块Ⅱ51，终端通讯模块Ⅱ51向驾驶员APP和管理员终端2(管理员APP和管理员PC终端)分别发送车辆接近信息；驾驶员可通过驾驶员APP(或远程的驾驶员PC终端)向终端通讯模块Ⅴ和终端通讯模块Ⅱ51发送开闸命令和车牌号信息；终端通讯模块Ⅱ51接收来自驾驶员APP的开闸命令和车牌号信息后，通过云端通讯模块Ⅱ52向云端通讯模块Ⅴ发送车牌号、闸口编码和开闸使能命令，云端通讯模块Ⅴ接收并将其发送至驱动模块；终端通讯模块Ⅴ接收来自驾驶员APP的开闸命令和车牌号信息后通过车牌号检索车辆入场信息以及泊位签出信息，当车辆在规定的时间内离开(在预约的泊车时长内离开或在步骤3所提示的驾驶员离开的时限内离开)终端通讯模块Ⅴ将开闸命令和车牌号信息发送至驱动模块；驱动模块将来自云端通讯模块Ⅱ52开闸使能命令和来自驾驶员APP的开闸命令相比对，比对成功后控制闸机开启。
入场信息或签出信息丢失，未成功签出泊位，超时滞留停车场和无驾驶员终端31，驾驶员无法开启闸机时，闸口通讯模块6向驾驶员APP返回开启闸机失败的理由以及后续要求，具体可分为以下几种情况；
6.1、有驾驶员APP，且可以根据要求完成操作后重新开启闸机；
6.1.1、驾驶员未成功签出泊位：当驾驶员未成功签出泊位导致开启闸机失败时，驾驶员可根据步骤5 中签出泊位的操作完成缴费并确认签出泊位，签出泊位成功后再根据步骤6重新向闸口通讯模块6发送开闸命令和车牌号信息；
6.1.2、驾驶员超时滞留停车场，包括车辆未在入场时所提示的时限内离开停车场以及车辆未在签出泊位后在规定的时限内离开停车场：当驾驶员超时滞留停车场导致开启闸机失败时，驾驶员可通过驾驶员APP根据停车场规定确认并接受相应的处罚(如缴纳罚款、扣除信誉积分等操作)后，再根据步骤6重新向终端通讯模块Ⅴ和终端通讯模块Ⅱ51发送开闸命令和车牌号信息；
6.2、无驾驶员APP的驾驶员，需等待管理员前来协助开闸操作；
当驾驶员无驾驶员APP(或驾驶员PC终端)时，即，驾驶员无法自行操作“开闸”按钮，此时当车辆靠近闸机时，车辆检测传感器Ⅱ50检测到闸口状态发生改变，触发终端通讯模块Ⅱ51向驾驶员APP和管理员终端2(管理员APP和管理员PC终端)分别发送闸口信息，管理员终端2在规定的时间内未收到闸口状态再一次改变的信息时，表示驾驶员未进行“开闸”操作，车辆仍停留在闸机处，此时管理员可根据闸口信息中的闸口编码前往对应闸机协助驾驶员打开闸机，离开停车场，管理员通过管理员APP的摄像功能采集车辆车牌号，并通过管理员APP协助驾驶员完成缴费，之后管理员APP将车牌号和开闸命令通过终端通讯模块V发送至驱动模块，对应车辆驶离停车场。
6.2.1、驾驶员未成功签出泊位：管理员通过管理员APP收取泊位费并发送签出信息，或向位于停车场出口处的泊位中继模块8发送签出信息，泊位中继模块8接收该签出信息并发送至云端服务器1，从而实现协助驾驶员签出泊位的工作；签出泊位成功后管理员通过管理员APP向闸口通讯模块6发送对应车辆车牌号和开闸命令，从而实现协助驾驶员打开闸机。上述管理员需输入车牌号时(即，协助驾驶员开闸、签入、签出、支付泊位费及变更或取消泊车时间等情况)可通过管理员APP的摄像头摄取并自动识别车牌号。
6.2.2、超时滞留停车场：管理员可通过管理员APP根据停车场规定确认并完成相应的处罚处理后，通过管理员APP向终端通讯模块Ⅴ发送开闸命令和车牌号信息，从而实现协助驾驶员打开闸机。
6.3、如出现丢失车辆入场信息或签出信息等特殊情况，需等待管理员前来对上述丢失信息进行处理，处理完成后管理员通过管理员APP开启闸机。
注：停车场闸口为出口处时，用于检测车辆接近情况的车辆检测模块Ⅱ5位于闸机内侧(靠近停车场的一侧)，终端通讯模块Ⅱ51与管理员APP和驾驶员APP建立通讯，从而实现开闸动作；用于检测车辆通过闸机情况的车辆检测模块Ⅲ位于闸机外侧(远离停车场的一侧)，当车辆检测传感器Ⅲ检测到车辆通过闸机时，云端通讯模块Ⅲ向云端通讯模块Ⅴ发送车辆通过信息从而实现关闸动作。
驱动模块依据云端通讯模块Ⅲ通过云端通讯模块Ⅴ向其发送车辆通过信息，即自动关闸的使能，驱动闸机关闭，关闭过程中驱动模块收到新的开闸使能命令和开闸命令将使关闸使能无效而重新开启闸机，直至收到新的自动关闸的使能再彻底关闭闸机，以避免车流量大时车辆与闸机的干涉。
根据问题性质的严重程度和规则，车辆被申请人可能无法开启停车场的闸机自主离开停车场。
7、出现异常情况具体处理方法如下：
异常情况包括最不利正常使用、合理可预见的误用和单一故障条件；
最不利正常使用，即按照规定的程序或明显预期的目的使用或操作系统时，考虑环境温度、沙尘和雨水，辐射、振动和噪声，车辆类型、入驻泊位和离开泊位的行为，覆盖物和障碍物，电池电压，闸机的开启和关闭，并发与等待等不利条件影响车辆检测、通讯距离时的使用条件；
合理可预见的误用，即按照可以预见的人类行为、习惯或惯性思维方式，超越规定的程序使用或操作系统，如误导和误占泊位，超时占用泊位，忽视或误读泊位状态信息，乱收费和习惯性现金支付，非预约泊车、不熟练客户端或非客户端的驾驶员，不必要滞留停车场或找不到车辆/泊位以及影响行车安全的操作等可预见的意料之外情理之中影响下的使用条件；
单一故障条件，即防止信息链断裂的预防措施发生失效的条件或可能引起信息链断裂而出现一个故障的条件，这些故障条件可以简单地归纳为设备硬件故障或通讯故障。
本发明充分考虑并提供手段以预防和纠正最不利正常使用条件、合理可预见的误用以及单一故障条件对系统预期功能、技术性能和客户体验的不利影响。包括以下措施：
通过车辆检测传感器、泊位信息、泊位预约信息、签入信息和签出信息结合起来提高泊位状态信息的准确性和完整性，从而向驾驶员显示清晰准确的泊位状态信息，利于驾驶员区分有用泊位和不可用泊位，避免误导和误占；
确保硬件设备(包括车辆检测模块Ⅰ4、车辆检测模块Ⅱ5、车辆检测模块Ⅲ和闸口通讯模块6等设备)在恶劣环境、低电压等条件下正常工作的技术性能；
移动通讯、终端通讯、云端通讯和以太网通讯等冗余通讯设计，避免设备故障、通讯障碍等信息滞后、丢失造成的信息不完整和错误；
利用驾驶员报告，停车场管理员巡查、处理以及泊车执法终端的监管和处理等经济和合法的手段确保 出现泊位异常信息时得到及时的纠正。
7.1、合理可预见的误用：
7.1.1、泊位异常状态：至少包括未成功签入泊位、未成功签出泊位、超时泊车、泊位故障和泊位被申请人；
未成功签入泊位：在驾驶员确认签入泊位成功后，云端服务器1将提高状态置信度；因此在泊位占用状态保持车辆入驻不变，且状态置信度在规定的时间内无提高(驾驶员未签入泊位)；或如果驾驶员签出泊位，且未在规定的时间内将车辆驶离泊位，此时管理员终端2提示管理员泊位异常状态，管理员可根据泊位编码前往协助驾驶员签入泊位、或提示将车辆挪离泊位；。
未成功签出泊位：在驾驶员确认签出泊位时，此时云端服务器1接收并更新状态置信度为初始值；在车辆驶离泊位时，云端服务器1提高状态置信度并向驾驶员发送成功签出泊位时，将泊位编码和车牌号解绑、更新泊位状态信息和泊位信息；当状态置信度重置为初始值且在规定的时间内无提高(表示驾驶员未将车辆驶离泊位)，此时管理员终端2提示管理员泊位异常状态，管理员可根据泊位编码前往泊位现场令驾驶员挪离车位。
超时泊车：当车辆超出所预约的泊车时长时，管理员终端2提示管理员泊位异常状态，管理员可根据泊位编码前往泊位现场令驾驶员挪离现场，或根据泊位编码查询对应泊位后续预约情况，适用时将后续预约驾驶员调整至其他空余泊位，并及时通知该驾驶员再分配以后的泊位编码。
管理员对上述违规车辆进行处理，且情节严重时可通过管理员终端2采集证据，并将所采集的证据发送至泊车执法终端7进行举报；驾驶员发现存在违规车辆或泊位故障时，也可以通过驾驶员终端3采集证据，并将所采集的证据发送至管理员终端2进行报告，或发送至泊车执法终端7进行举报。
上述车辆检测传感器Ⅰ40、车辆检测传感器Ⅱ50和车辆检测传感器Ⅲ采用摄像头或其他车牌识别传感器时，违规车辆的信息，包括车牌号、位置(即车辆检测传感器安装地理位置)、时间等自动上传云端服务器1而无需管理员或其他驾驶员采集证据；
在投诉待审理期间，根据问题严重性的程度和相关规则，泊位被申请人可能被屏蔽从而失去被搜索和预约的机会，车辆被申请人可能无法预约泊位、即时泊车或离开停车场。
7.1.2、闸口状态异常，即，有车辆停留在闸口处超过规定的时限；
当有车辆接近闸机时，闸口状态发生改变，车辆检测模块Ⅱ5分别向管理员终端2、驾驶员终端3和云端服务器1发送闸口信息的闸口状态为有车辆；驾驶员开启闸机车辆进入停车场后，云端服务器1接收并储存闸口通讯模块6车辆入场信息，此时管理员终端2同步更新；当闸口状态在规定的时限内保持不变时，管理员终端2提示管理员闸口异常信息，管理员可根据闸口异常信息中的闸口编码前往对应闸口处理。
7.2、单一故障条件：
7.2.1、通讯异常；
移动通讯异常：驾驶员APP(或管理员APP)与云端服务器1通讯异常，无法将签入信息、签出信息和交易信息成功发送至云端服务器1，可能造成信息的丢失、滞后或错误；本发明中驾驶员APP(或管理员APP)与对应泊位的终端通讯模块Ⅰ41互相发送车牌号和泊位编码，然后驾驶员APP(或管理员APP)与终端通讯模块Ⅰ41各自利用自己的通讯方式向云端服务器1发送签入信息/签出信息，从而确保了单一故障条件下，即假定驾驶员APP(或管理员APP)、车辆检测模块Ⅰ4与云端服务器1的通讯不可能同时故障的情况下，也能正常完成签入泊位和签出泊位的操作；
LORA通讯异常：云端通讯模块Ⅰ42与云端服务器1通讯异常，无法将签入信息、签出信息和心跳信息成功发送至云端服务器1，可能造成信息的丢失、滞后或错误；本发明中驾驶员APP(或管理员APP)与对应泊位的终端通讯模块Ⅰ41互相发送车牌号和泊位编码，然后驾驶员APP(或管理员APP)与终端通讯模块Ⅰ41各自利用自己的通讯方式向云端服务器1发送签入信息/签出信息，从而确保了单一故障条件下，即假定驾驶员APP(或管理员APP)、车辆检测模块Ⅰ4与云端服务器1的通讯不可能同时故障的情况下，也能正常完成签入泊位和签出泊位的操作；
7.2.2、设备故障：
车辆检测模块Ⅰ4向云端服务器1发送信息失败，无论云端通讯模块Ⅰ42或泊位中继模块8异常，该信息将被保存在云端通讯模块Ⅰ42或泊位中继模块8中，云端通讯模块Ⅰ42和泊位中继模块8将定时(如每隔120min)向云端服务器1重新发送该信息，直至收到云端服务器1成功接收的回执，在确保泊位服务与管理系统的稳定性的同时对设备进行低能耗的管理。
终端通讯模块Ⅰ41通讯异常，不能向驾驶员APP(或管理员APP)发送泊位状态信息；此时驾驶员仅需记住泊位编码，即可在泊位中继模块8处输入泊位编码完成签入泊位和签出泊位的操作。云端通讯模块Ⅰ42通讯异常不能向云端发送信息，此时驾驶员可通过驾驶员APP完成签入泊位和签出泊位的操作。在泊位现场驾驶员APP通讯异常情况下，驾驶员可以在限定的时间内，在任何有信号的地方通过驾驶员 APP执行签入泊位/签出泊位的操作。
当设备发生故障时，如蓝牙异常、车辆检测模块Ⅰ发生故障，云端服务器1无法完整接收任何来自云端通讯模块Ⅰ42的信息，由于云端通讯模块Ⅰ42定时向云端服务器1发送心跳信息，因此云端服务器1可以及时发现设备异常状况并立即通知管理员进行维修或更换，从而确保本发明泊位服务与管理系统的正常运行。
7.3、异常报告、投诉或举报：
当管理员终端2或泊车执法终端7收到泊位故障、对停车场违规或车辆违规的报告、投诉或举报时，管理员或泊车执法员对所提交的报告或证据进行核实，必要时可前往现场进行核实。如核实后所报告、投诉或举报的内容属实，管理员终端2或泊车执法终端7向投诉人(管理员或驾驶员)进行反馈，严重违规的泊位被申请人或车辆被申请人，可能无法正常营运或泊车。
当驾驶员发现泊位异常状态或其他车辆有违规行为，可通过驾驶员终端3采集证据，并向管理员终端2或泊车执法终端7进行报告或投诉。
7.3.1、对严重违规的泊位被申请人的处理方式：
当驾驶员通过驾驶员APP进行泊位搜索和预约时，由于泊位被申请人属于泊位异常状态的一种，即，非可用泊位，故云端服务器1不会将泊位被申请人的信息反馈给驾驶员，从而使泊位被申请人失去被预约的机会，因此无法利用本发明提供的便利和方法进行运营和管理；停车场管理者可通过接受相应的处理(如缴纳罚款)来消除泊位被申请人的异常状态。
7.3.2、对严重违规的车辆被申请人的处理方式：
车辆被申请人无法预约泊位：车辆被申请人通过驾驶员APP进行泊位预约时，驾驶员APP提交泊位需求信息至云端服务器1，云端服务器1在比较泊位需求信息和泊位信息时，首先通过泊位需求信息中的车牌号检索对应车辆信息，当车辆信息中包含车辆被申请人时，云端服务器1将拒绝该车辆的预约操作，并将拒绝原因和后续操作要求通过驾驶员APP反馈给驾驶员；
为确保停车场入口处的通畅，任何车辆可通过驾驶员APP或管理员的帮助开启闸机进入停车场；闸机开启后，闸口通讯模块6向云端服务器1发送车辆入场信息；云端服务器1接收、储存和更新车辆入场信息，包括根据车牌号检索对应车辆信息是否处于车辆被申请人状态，并向同一停车场编码下的所有闸口通讯模块6发送该车辆入场信息(使用时包括车辆被申请人信息)。
车辆被申请人无法签入泊位和即时泊车：车辆被申请人通过驾驶员APP签入泊位时，驾驶员APP提交签入信息至云端服务器1，云端服务器1首先通过签入信息中的车牌号检索对应车辆信息，当车辆信息中包含车辆被申请人时，云端服务器1将拒绝该车辆的签入操作，并将拒绝原因和后续操作要求通过驾驶员APP反馈给驾驶员；
车辆被申请人无法开启闸机离开停车场：车辆被申请人进入停车场后无法即时泊车，因而应在停车场限定的时间内离开停车场；闸口通讯模块6接收来自驾驶员APP的开闸命令和车牌号信息后，通过车牌号检索车辆入场信息中包括车辆被申请人信息时，闸口通讯模块6将拒绝来自车辆被申请人的开闸命令，并将拒绝原因和后续操作要求通过驾驶员APP反馈给驾驶员。
驾驶员可通过接受相应的处理(如缴纳罚款)消除车辆被申请人的异常状态。当驾驶员未缴纳相应罚款，如无驾驶员APP时，管理员前往处理异常状态时告知车辆被申请人消除异常状态的处理方式(即通过驾驶员终端3缴纳罚款，或前往相关部门缴纳罚款)。如果驾驶员无视车辆被申请人状态任意泊车或超过规定时限离开停车场，按照未签入泊车或超时离开停车场的规则接受处罚后，由停车场管理员协助驾驶员开启闸机离开停车场。
最后，还需要注意的是，以上列举的仅是本发明的若干个具体实施例。显然，本发明不限于以上实施例，还可以有许多变形。本领域的普通技术人员能从本发明公开的内容直接导出或联想到的所有变形，均应认为是本发明的保护范围。

Claims (10)

  1. 基于车辆检测的泊位服务与管理系统，其特征在于：
    所述泊位服务与管理系统包括云端服务器(1)，以及与云端服务器(1)信号相连的管理员终端(2)、驾驶员终端(3)、车辆检测模块Ⅰ(4)和泊车执法终端(7)；所述管理员终端(2)和驾驶员终端(3)均与车辆检测模块Ⅰ(4)和泊车执法终端(7)信号相连；
    所述云端服务器(1)用于接收、储存、处理和更新所有停车场信息和车辆信息；
    所述管理员终端(2)用于向云端服务器(1)上传泊位信息，监测泊位状态信息和闸口信息，处理异常状态并及时通知管理员；
    所述泊位信息至少包括泊位编码、泊位大小、可用时段和泊车时限；
    所述驾驶员终端(3)用于向云端服务器(1)发送泊位需求信息，进行泊位预约和变更；
    所述泊位需求信息至少包括目的地名称、车牌号、计划泊车起始时间和泊车时长；
    所述驾驶员终端还用于进行签入泊位和签出泊位的操作；
    所述管理员终端(2)还用于协助驾驶员进行预约泊位、更改或取消、签入泊位和签出泊位的操作；
    所述车辆检测模块Ⅰ(4)用于检测泊位占用状态，并向云端服务器(1)、管理员终端(2)和驾驶员终端(3)发送泊位状态信息；
    所述泊车执法终端(7)用于对违规泊车进行监察。
  2. 根据权利要求1所述的基于车辆检测的泊位服务与管理系统，其特征在于：
    所述云端服务器(1)还用于接收、储存、处理和更新所有交易信息；
    所述停车场信息包括同一停车场的泊位信息、泊位状态信息、泊位异常信息、闸口信息；所述泊位状态信息保存在泊位编码下，至少包括泊位编码、泊位占用状态、状态改变的时间及状态置信度；所述泊位异常信息至少包括泊位异常状态和对应泊位编码，泊位异常状态至少包括未成功签入、未成功签出、超时泊车、泊位故障和泊位被申请人，所述泊位被申请人指泊位被异常投诉处于审理期间；所述闸口信息包括车辆入场信息、车辆出场信息和闸口异常信息，所述车辆入场信息和车辆出场信息至少包括停车场编码、闸口编码、车牌号和对应进场/出场时间，所述闸口异常信息至少包括停车场编码、闸口编码、对应进场/出场时间以及异常状态；车辆信息至少包括车牌号，以及保存在车牌号下的泊位需求信息、泊位预约信息、泊车信息和车辆被申请人，所述车辆被申请人指车辆被异常投诉处于审理期间；所述泊位预约信息至少包括所预约的泊位编码、车牌号、计划泊车起始时间和泊车时长；泊车信息至少包括车牌号、泊位编码、签入泊位的时间和签出泊位的时间；所述签入泊位指驾驶员表达泊车意愿，接受泊车服务与管理条款，确认泊车开始的报告或行动，所述签出泊位指驾驶员承认泊车事实，接受泊车服务与管理条款，确认泊车终止的报告或行动；所述车辆被申请人指车辆被异常投诉处于审理期间；
    管理员通过管理员终端(2)协助驾驶员进行开启闸机和收费操作，以及通过管理员终端(2)进行采集泊位异常状态时的证据并发送至驾驶员终端(3)进行处理或发送至泊车执法终端(7)进行举报的工作；云端服务器(1)将闸口信息，泊位状态信息、泊位预约信息和交易信息同步给管理员终端(2)；
    所述驾驶员终端(3)还用于进行开闸、缴费和延长泊车时长的操作，以及发现泊位异常状态时采集证据并发送至管理员终端(2)或泊车执法终端(7)进行报告、投诉或举报的工作；云端服务器(1)将泊位需求信息、泊位预约信息、进出场信息、泊车信息和交易信息同步给驾驶员终端(3)；
    所述泊车执法终端(7)可查询任一泊位的泊车信息，通过泊车信息与实际车辆停留状态相比对，对违规车辆进行取证、登记和处理；所述泊车执法终端(7)还能够接收、保存并处理来自管理员终端(2)和驾驶员终端(3)的投诉或举报信息，并在核实投诉或举报信息后对违规车辆进行处理。
  3. 根据权利要求2所述的基于车辆检测的泊位服务与管理系统，其特征在于：
    所述泊位服务与管理系统还包括车辆检测模块Ⅱ(5)、车辆检测模块Ⅲ和闸口通讯模块(6)；所述闸口通讯模块(6)分别与车辆检测模块Ⅱ(5)、车辆检测模块Ⅲ、云端服务器(1)、管理员终端(2)和驾驶员终端(3)信号相连；
    所述车辆检测模块Ⅱ(5)用于检测车辆与闸口的位置信息，并向闸口通讯模块(6)、管理员终端(2)和驾驶员终端(3)发送车辆接近信息；
    所述车辆检测模块Ⅲ用于检测车辆与闸口的位置信息，并向闸口通讯模块(6)发送车辆通过信息；
    所述闸口通讯模块(6)用于接收车辆检测模块Ⅱ(5)发送的车辆接近信息、车辆检测模块Ⅲ发送的车辆通过信息，和来自管理员终端(2)或驾驶员终端(3)泊车执法终端(7)的开闸命令及车牌号；闸口通讯模块(6)将车牌号、停车场编码和闸口编码绑定后开启闸机；闸口通讯模块(6)向云端服务器(1)发送对应停车场内车辆的进场信息、出场信息和闸口异常信息，云端服务器(1)将对应停车场内车辆的进场信息、出场信息、签入信息和签出信息同步给同一停车场编码下所有的闸口通讯模块(6)。
  4. 根据权利要求3所述的基于车辆检测的泊位服务与管理系统，其特征在于：
    所述管理员终端(2)包括管理员PC终端和具有摄像功能的管理员APP；
    所述驾驶员终端(3)包括驾驶员PC终端和具有摄像功能的驾驶员APP；
    所述管理员APP/驾驶员APP通过摄像功能采集车牌号和车辆违规证据；
    非驾驶员APP和驾驶员PC终端的用户，管理员可通过管理员APP代替用户向云端服务器(1)上传泊位需求信息、获取泊位预约信息、签入泊位、签出泊位、收取泊车费和执行开闸命令；
    非驾驶员APP的用户可通过驾驶员PC终端完成相应操作，或管理员通过管理员APP代替用户进行签入泊位、签出泊位和执行开闸命令；
    所述车辆检测模块Ⅰ(4)位于泊位上，包括依次相连的车辆检测传感器Ⅰ(40)、终端通讯模块Ⅰ(41)和云端通讯模块Ⅰ(42)；
    所述泊位服务与管理系统还包括与管理员APP、驾驶员APP、云端通讯模块Ⅰ(42)和云端服务器(1)均相连的泊位中继模块(8)，所述泊位中继模块(8)位于停车场行人出入口，用于中继和放大信号，管理员APP、驾驶员APP和云端通讯模块Ⅰ(42)均通过泊位中继模块(8)与云端服务器(1)信号相连；
    所述车辆检测模块Ⅱ(5)和车辆检测模块Ⅲ位于闸机两侧，车辆检测模块Ⅱ(5)包括依次相连的车辆检测传感器Ⅱ(50)、终端通讯模块Ⅱ(51)和云端通讯模块Ⅱ(52)；车辆检测模块Ⅲ包括依次相连的车辆检测传感器Ⅲ、终端通讯模块Ⅲ和云端通讯模块Ⅲ；所述车辆检测传感器Ⅰ(40)、车辆检测传感器Ⅱ(50)和车辆检测传感器Ⅲ均用于检测车辆靠近；车辆检测传感器Ⅰ(40)将检测到的泊位占用状态发送至终端通讯模块Ⅰ(41)，终端通讯模块Ⅰ(41)将泊位状态信息发送至云端通讯模块Ⅰ(42)；车辆检测传感器Ⅱ(50)将闸口状态发送至终端通讯模块Ⅱ(51)，终端通讯模块Ⅱ(51)通过云端通讯模块Ⅱ(52)将车辆接近信息发送至闸口通讯模块(6)；车辆检测传感器Ⅲ将闸口状态发送至终端通讯模块Ⅲ，终端通讯模块Ⅲ通过云端通讯模块Ⅲ将车辆通过信息发送至闸口通讯模块(6)；
    所述闸口通讯模块(6)接收来自云端通讯模块Ⅱ(52)的开闸使能命令、云端通讯模块Ⅲ的关闸使能，和来自驾驶员终端(3)或管理员终端(2)的开闸命令，并向云端服务器(1)发送闸口信息；
    所述终端通讯模块Ⅰ(41)和终端通讯模块Ⅱ(51)分别与管理员APP和驾驶员APP信号相连；所述终端通讯模块Ⅰ(41)用于向管理员APP和驾驶员APP和云端通讯模块Ⅰ(42)发送泊位状态信息和接收泊位预约信息、签入泊位和签出泊位；云端通讯模块Ⅰ(42)用于通过泊位中继模块(8)向云端服务器(1)发送泊车信息和泊位状态信息；所述终端通讯模块Ⅱ(51)用于向管理员APP和驾驶员APP发送闸口车辆接近信息和接收开闸命令；所述云端通讯模块Ⅱ(52)还用于向闸口通讯模块(6)发送开闸使能命令，闸口通讯模块(6)控制闸机开启并向云端服务器(1)发送闸口信息。
  5. 根据权利要求4所述的基于车辆检测的泊位服务与管理系统，其特征在于：
    所述闸口通讯模块(6)包括终端通讯模块Ⅴ，以及均与终端通讯模块Ⅴ相连的云端通讯模块Ⅴ、闸口显示模块以及驱动模块，驱动模块与云端通讯模块Ⅴ和闸机信号相连；
    所述泊位中继模块(8)包括相连的终端通讯模块Ⅳ和云端通讯模块Ⅳ；
    所述终端通讯模块Ⅴ和终端通讯模块Ⅳ均与管理员APP和驾驶员APP信号相连；
    所述云端通讯模块Ⅴ分别与云端服务器(1)、云端通讯模块Ⅱ(52)、云端通讯模块Ⅲ、云端通讯模块Ⅳ以及其他云端通讯模块Ⅴ信号相连；
    云端通讯模块Ⅳ分别与云端服务器(1)、云端通讯模块Ⅰ(41)、云端通讯模块Ⅴ以及其他云端通讯模块Ⅳ信号相连；
    所述泊位编码和泊位占用状态事先写入对应终端通讯模块Ⅰ(41)中；所述闸口编码和车辆接近信息事先写入对应终端通讯模块Ⅱ(51)中；所述闸口编码和车辆通过信息事先写入对应终端通讯模块Ⅲ中；
    所述云端通讯模块Ⅰ(42)通过云端通讯模块Ⅳ定时向云端服务器(1)发送心跳信息，确认车辆检测模块Ⅰ(4)和泊位中继模块(8)工作正常；所述云端通讯模块Ⅱ(52)和云端通讯模块Ⅲ均通过云端通讯模块Ⅴ定时向云端服务器(1)发送心跳信息，确认车辆检测模块Ⅱ(5)、车辆检测模块Ⅲ和闸口通讯模块(6)工作正常；
    所述心跳信息包括对应模块的设备标识、状态变化异常记录、时钟、温度及电池余量；所述设备标识包括泊位编码、闸口编码或模块编码；
    所述心跳信息异常时，云端服务器(1)定时向云端通讯模块Ⅳ和云端通讯模块Ⅴ发送管理命令，或向管理员APP和管理员PC终端发送设备异常信息提示维护或更换。
  6. 根据权利要求5所述的基于车辆检测的泊位服务与管理系统，其特征在于：
    所述车辆检测传感器Ⅰ(40)、车辆检测传感器Ⅱ(50)和车辆检测传感器Ⅲ采用地磁传感器、红外传感器、超声波传感器或摄像头；
    所述摄像头还用于自动识别车牌号；
    所述终端通讯模块Ⅰ(41)、终端通讯模块Ⅱ(51)、终端通讯模块Ⅲ、终端通讯模块Ⅳ和终端通讯模块Ⅴ采用蓝牙通讯模块；
    所述云端通讯模块Ⅰ(42)、云端通讯模块Ⅱ(52)、云端通讯模块Ⅲ、云端通讯模块Ⅳ和云端通讯模块Ⅴ采用LORA通讯模块。
  7. 如权利要求1-6任一所述的系统进行的泊位服务与管理方法，其特征在于包括以下步骤：
    1.1)、泊位信息公布：管理员或泊位拥有者通过管理员终端(2)将泊位信息于云端服务器(1)上进行公布；
    1.2)、泊位预约信息获取：驾驶员通过驾驶员终端(3)将泊位需求信息上传云端服务器(1)；所述云端服务器(1)将所接收的泊位需求信息与泊位信息进行匹配，匹配成功的泊位通过驾驶员终端(3)反馈给驾驶员，驾驶员通过驾驶员终端(3)选择合适的泊位并确认预约，此时云端服务器(1)分别向管理员终端(2)和驾驶员终端(3)反馈泊位预约信息；
    1.3)、泊位占用状态检测：车辆进驻或驶离泊位时，位于泊位上的车辆检测模块Ⅰ(4)检测到泊位占用状态发生改变，此时车辆检测模块Ⅰ(4)向管理员终端(2)、驾驶员终端(3)和云端服务器(1)发送泊位状态信息；所述泊位状态信息至少包括泊位编码、泊位占用状态以及状态改变的时间；
    1.3.1)、签入泊位：车辆进驻泊位时，驾驶员终端(3)接收所述步骤1.3)中车辆检测模块Ⅰ(4)发送泊位状态信息，驾驶员终端(3)显示泊位编码并请求驾驶员签入泊位；驾驶员确认签入泊位时，驾驶员终端(3)首先向车辆检测模块Ⅰ(4)发送车牌号，之后驾驶员终端(3)和车辆检测模块Ⅰ(4)均向云端服务器(1)发送签入信息，所述签入信息至少包括对应泊位编码、车牌号、签入泊位时间、泊车时长以及计划泊车结束时间；所述云端服务器(1)接收签入信息并根据签入信息中的车牌号进行查询对应的泊位预约信息，将泊位预约信息中泊位编码与签入信息中泊位编码相比对，泊位预约信息中计划泊车起始时间和泊车时长相加的时间段与签入信息中签入泊位的时间比对；比对成功时云端服务器(1)将车牌号和泊位编码绑定，并向管理员终端(2)和驾驶员终端(3)发送成功签入泊位的信息；
    1.3.2)、签出泊位：车辆驶离泊位时，首先驾驶员通过驾驶员终端(3)确认签出泊位，此时驾驶员终端(3)向云端服务器(1)发送签出信息，所述签出信息至少包括对应泊位编码、车牌号和签出泊位的时间；云端服务器(1)接收签出信息并根据签出信息的车牌号查询对应的签入信息，将签入信息与签出信息的泊位编码和签出泊位的时间比对；比对成功云端服务器(1)向管理员终端(2)和驾驶员终端(3)发送确认签出泊位的信息；
    车辆驶离泊位后，车辆检测模块Ⅰ(4)向管理员终端(2)、驾驶员终端(3)和云端服务器(1)发送泊位状态信息，云端服务器(1)接收泊位状态信息后将车牌号和泊位编码解绑，并将解绑信息发送至驾驶员终端(3)，驾驶员终端(3)接收解绑信息后，发送泊位签出成功信息；
    1.4)、云端服务器(1)通过管理员终端(2)提示管理员泊位异常信息，管理员通过管理员终端(2)对泊位进行巡视、取证和处理；所述泊位异常信息至少包括泊位异常状态及对应泊位编码，泊位异常状态至少包括未成功签入泊位、未成功签出泊位和超时泊车。
  8. 根据权利要求7所述的基于车辆检测的泊位服务与管理方法，其特征在于：
    所述泊位服务与管理方法还包括针对设有门控机构的停车场的泊位服务与管理方法；所述门控机构包括相连的闸口通讯模块(6)和闸机；
    具体步骤包括：
    2.1)、闸口状态检测：闸口处设有闸口通讯模块(6)及分别位于闸机两侧的车辆检测模块Ⅱ(5)和车辆检测模块Ⅲ；闸口通讯模块(6)分别与车辆检测模块Ⅱ(5)和车辆检测模块Ⅲ相连；当有车辆靠近闸口时，车辆检测模块Ⅱ(5)检测到闸口处有车，并分别向管理员终端(2)和驾驶员终端(3)发送车辆接近信息；所述车辆接近信息至少包括停车场编码、闸口编码和进场/出场时间；车辆检测模块Ⅲ检测到闸口处车辆通过，车辆检测模块Ⅲ向闸口通讯模块(6)发送车辆通过信息；所述车辆通过信息至少包括停车场编码、闸口编码和进场/出场时间，闸口通讯模块(6)接收到车辆通过信息后控制闸机关闭；
    2.1.1)、进入停车场：车辆进入停车场时，驾驶员终端(3)在入口闸口处接收所述步骤2.1)中车辆检测模块Ⅱ(5)发送的车辆接近信息，此时驾驶员终端(3)向驾驶员致欢迎词，显示停车场编码和闸口编码，并提示驾驶员进行开闸操作；驾驶员通过驾驶员终端(3)进行开闸操作时，驾驶员终端(3)首先向车辆检测模块Ⅱ(5)发送车牌号信息，之后驾驶员终端(3)和车辆检测模块Ⅱ(5)分别向闸口通讯模块(6)发送开闸命令、开闸使能命令以及车牌号信息；闸口通讯模块(6)接收到开闸命令、开闸使能命令以及车牌号信息后控制闸机开启；闸机开启后，闸口通讯模块(6)向云端服务器(1)发送车辆入场信息；所述车辆入场信息包括停车场编码、闸口编码、车牌号和进场时间；云端服务器(1)接收、储存和更新车辆入场信息后，向同一停车场编码下的所有闸口通讯模块(6)发送对应车辆入场信息；
    2.1.2)、离开停车场；车辆离开停车场时，驾驶员终端(3)在出口闸口处接收所述步骤2.1)中车辆检测模块Ⅱ(5)发送车辆接近信息，驾驶员终端(3)向驾驶员致欢送词，显示停车场编码、闸口编码并提示驾驶员进行开闸操作；驾驶员通过驾驶员终端(3)进行开闸操作时，驾驶员终端(3)首先向车辆检测模块Ⅱ(5)发送车牌号信息，之后驾驶员终端(3)和车辆检测模块Ⅱ(5)分别向闸口通讯模块(6)发送开闸命令、开闸使能命令以及车牌号信息；闸口通讯模块(6)接收开闸命令、开闸使能命令以及车牌号信息后，通过车牌号对车辆入场信息和签出信息进行查询，当查询到对应车辆确认签出泊位操作或在规定的时限内离开时，闸口通讯模块(6)根据车辆检测模块Ⅱ(5)的开闸使能命令和驾驶员终端(3)的开闸命令开启闸机；闸机开启后，闸口通讯模块(6)向云端服务器(1)发送车辆出场信息；所述出场信息包括停车场编码、闸口编码、车牌号和出场时间；云端服务器(1)接收、储存和更新上述信息后，向同一停车场编码下的所有闸口通讯模块(6)发送对应车辆出场信息。
  9. 根据权利要求7或8所述的基于车辆检测的泊位服务与管理方法，其特征在于：
    所述步骤1.3.1)中，驾驶员确认签入泊位时，云端服务器(1)通过签入信息中的车牌号查询未见泊位预约信息，此时驾驶员终端(3)提示驾驶员确认泊位编码和默认的泊车时长，驾驶员可以改变泊车时长后执行签入泊位；云端服务器(1)通过泊位编码查询到对应泊位可用时签入成功，所述泊位可用，表示泊位空闲没有被预约，且签入泊位的泊车时长符合泊位信息中规定的可用时段和泊车时限；否则云端服务器(1)通过驾驶员终端(3)提示签入失败、预约其他可用泊位并将车辆挪离泊位。
  10. 根据权利要求9所述的基于车辆检测的泊位服务与管理方法，其特征在于：
    所述步骤1.3)中泊位状态信息还包括状态置信度；
    步骤1.3.1)车辆驶入泊位时，车辆检测模块Ⅰ(4)检测到泊位占用状态发生改变，车辆检测模块Ⅰ(4)向管理员终端(2)、驾驶员终端(3)和云端服务器(1)发送泊位状态信息；此时泊位状态信息中的泊位占用状态为有车，状态置信度为初始值；驾驶员成功签入泊位时，云端服务器(1)提高状态置信度；泊位占用状态保持车辆入驻不变，且状态置信度在规定的时限内无提高(驾驶员未签入泊位)，云端服务器(1)通过管理员终端(2)提示管理员泊位异常信息，管理员可根据泊位编码前往现场协助驾驶员签入泊位、或提示驾驶员将车辆挪离泊位；
    步骤1.3.2)驾驶员确认签出泊位时，云端服务器(1)接收签出信息并将状态置信度重置为初始值；当车辆驶离泊位，云端服务器(1)接收车辆检测模块Ⅰ(4)发送的泊位状态信息中，泊位占用状态为无车，此时云端服务器(1)再一次提高状态置信度并更新泊位状态信息；驾驶员确认签出泊位，且状态置 信度在规定的时限内无提高，云端服务器(1)通过管理员终端(2)提示管理员泊位异常信息，管理员可根据泊位编码前往现场提示驾驶员将车辆挪离泊位；
    当车辆超出签入信息所限定的泊车时长而未有签出信息时，云端服务器(1)通过管理员终端(2)提示管理员泊位异常信息，管理员可根据泊位编码查询并将对应泊位后续泊位预约信息的泊位编码调整到其他可用泊位；
    当车辆驶离泊位，云端服务器(1)接收车辆检测模块Ⅰ(4)发送的泊位状态信息中，泊位占用状态为无车，且在规定的时限内未有签出泊位信息时，云端服务器(1)通过管理员终端(2)提示管理员泊位异常信息，管理员可根据泊位编码前往现场；
    管理员前往泊位编码现场且确认泊位异常信息时，管理员通过管理员终端(2)调整泊位状态信息与实际一致；
    管理员对泊位异常状态进行调查和处理时，可通过管理员终端(2)采集证据，并将所采集的证据发送至泊车执法终端(7)进行举报；驾驶员发现泊位异常状态，可通过驾驶员终端(3)采集证据，并将所采集的证据发送至管理员终端(2)进行报告，或发送至泊车执法终端(7)进行举报；
    当有车辆接近闸口未成功进行开闸操作时，闸口通讯模块(6)向云端服务器(1)发送闸口异常信息；所述管理员终端(2)接收闸口异常信息并根据闸口异常信息中的闸口编码赶赴闸口现场处理。
PCT/CN2018/103562 2017-09-15 2018-08-31 基于车辆检测的泊位服务与管理系统及方法 WO2019052352A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710833974 2017-09-15
CN201710833974.1 2017-09-15
CN201711273631.0A CN107993478B (zh) 2017-09-15 2017-12-06 基于车辆检测的泊位服务与管理系统及方法
CN201711273631.0 2017-12-06

Publications (1)

Publication Number Publication Date
WO2019052352A1 true WO2019052352A1 (zh) 2019-03-21

Family

ID=62036289

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103562 WO2019052352A1 (zh) 2017-09-15 2018-08-31 基于车辆检测的泊位服务与管理系统及方法

Country Status (2)

Country Link
CN (1) CN107993478B (zh)
WO (1) WO2019052352A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112233454A (zh) * 2020-08-31 2021-01-15 浙江创泰科技有限公司 一种智能停车监控的方法

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107993478B (zh) * 2017-09-15 2019-05-03 路特迩科技(杭州)有限公司 基于车辆检测的泊位服务与管理系统及方法
CN108711089A (zh) * 2018-05-15 2018-10-26 成都市微泊科技有限公司 一种基于区块链的跨平台车位共享交易方法
CN109064771A (zh) * 2018-09-21 2018-12-21 四川长虹电器股份有限公司 一种基于nb地磁的泊位实时监控方法
CN109410633A (zh) * 2018-10-22 2019-03-01 安徽中科美络信息技术有限公司 一种智能车库车位导航方法及系统
CN109509365B (zh) * 2018-11-02 2021-06-18 西安艾润物联网技术服务有限责任公司 一种车辆信息纠错方法、系统和手持移动终端装置
CN110033638B (zh) * 2019-03-07 2022-01-28 西安艾润物联网技术服务有限责任公司 车辆进出场所的警示方法及装置
US11842591B2 (en) 2019-08-07 2023-12-12 SpotHero, Inc. Parking facility communication systems and methods
CN110717995B (zh) * 2019-08-26 2024-05-24 江苏慧泽信息技术有限公司 一种停车场闸口监测方法
CN110610610B (zh) * 2019-09-20 2022-04-15 腾讯科技（深圳）有限公司 一种车辆出入管理方法、装置以及存储介质
CN111127932B (zh) * 2019-12-03 2020-12-18 重庆特斯联智慧科技股份有限公司 一种基于分布式识别算法的社区充电车位共享方法和系统
CN110956821A (zh) * 2019-12-12 2020-04-03 天地伟业技术有限公司 一种划定区域内车辆超时滞留的检测方法
CN113472833B (zh) * 2020-03-31 2024-02-20 广州汽车集团股份有限公司 泊车控制方法、系统和云服务平台
CN111915922B (zh) * 2020-06-03 2023-01-17 西安艾润物联网技术服务有限责任公司 基于etc设备的车辆停放位置状态的确定方法及装置
CN111882917B (zh) * 2020-06-12 2021-10-01 深圳市捷顺科技实业股份有限公司 一种车辆插队问题处理的方法以及处理装置
CN111653104B (zh) * 2020-07-13 2022-04-19 深圳华强技术有限公司 磁场基线自维护方法、装置、计算机设备及存储介质
CN112071106A (zh) * 2020-09-18 2020-12-11 四川长虹电器股份有限公司 地磁设备异常离线的实时监控系统及方法
CN112185129B (zh) * 2020-11-13 2021-06-25 重庆盘古美天物联网科技有限公司 基于城市辅路卡口抓拍的停车管理方法
CN112862987A (zh) * 2020-12-31 2021-05-28 深圳市顺易通信息科技有限公司 一种订位停车逾时费的垫付方法及装置
CN117037299A (zh) * 2023-07-31 2023-11-10 杭州时祺科技有限公司 一种城市智能停车收费管理方法、系统、设备及介质
CN116758755B (zh) * 2023-08-22 2023-11-28 成都宜泊信息科技有限公司 室内地下停车场停车管理方法及管理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101847327A (zh) * 2010-04-09 2010-09-29 浙江大学 基于车载导航仪的停车泊位诱导系统及方法
EP2645336A1 (de) * 2012-03-27 2013-10-02 Scheidt & Bachmann GmbH Verfahren zur automatisierten Vermittlung von Parkflächen
CN104900087A (zh) * 2014-03-07 2015-09-09 贺江涛 一种基于手持设备的停车位预定的方法与装置
CN106601021A (zh) * 2016-12-22 2017-04-26 吴中区穹窿山倪源交通器材经营部 一种城市公共停车位智能指示系统
CN107993478A (zh) * 2017-09-15 2018-05-04 路特迩科技(杭州)有限公司 基于车辆检测的泊位服务与管理系统及方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102568246B (zh) * 2010-04-09 2014-04-16 浙江大学 基于车载导航仪的停车泊位诱导方法
CN102231242B (zh) * 2011-06-13 2014-05-14 黄卫 一种路侧停车智能化管理的系统和方法
CN104157130B (zh) * 2013-05-14 2018-02-16 成都国腾电子集团有限公司 一种基于移动互联网的停车管理系统及车位预定方法
CN103985273B (zh) * 2014-06-04 2016-02-03 广西久邻网络有限公司 城市停车智能管理系统
KR101556950B1 (ko) * 2015-03-31 2015-10-06 파킹클라우드 주식회사 주차장 관리 방법, 휴대 단말 및 주차장 관리 시스템
CN105023467B (zh) * 2015-08-20 2017-07-21 桂林电子科技大学 一种停车场车位远程预订系统及方法
CN105632234B (zh) * 2016-02-25 2018-06-22 江苏中兴新泰物联网科技园有限公司 一种智能停车收费系统
CN105702080A (zh) * 2016-04-07 2016-06-22 张勋 智慧城市云计算停车管理信息系统
CN105844960B (zh) * 2016-06-14 2019-04-30 河海大学 一种交互式智能化停车服务系统及其运行方法
CN106297384B (zh) * 2016-08-26 2019-06-11 云赛智联股份有限公司 一种城市道路智慧泊车管理系统
CN106652550A (zh) * 2016-12-08 2017-05-10 赵伟 可预约定位的车位管理系统及其方法
CN107067248B (zh) * 2017-04-17 2020-10-13 北京工业大学 一种智能地锁控制方法及系统
CN107170276B (zh) * 2017-06-08 2020-05-08 浙江大学 一种基于云的无人停车场自动泊车管理系统
CN108010373B (zh) * 2017-09-15 2019-04-09 路特迩科技(杭州)有限公司 基于泊位状态信息的泊位服务与管理系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101847327A (zh) * 2010-04-09 2010-09-29 浙江大学 基于车载导航仪的停车泊位诱导系统及方法
EP2645336A1 (de) * 2012-03-27 2013-10-02 Scheidt & Bachmann GmbH Verfahren zur automatisierten Vermittlung von Parkflächen
CN104900087A (zh) * 2014-03-07 2015-09-09 贺江涛 一种基于手持设备的停车位预定的方法与装置
CN106601021A (zh) * 2016-12-22 2017-04-26 吴中区穹窿山倪源交通器材经营部 一种城市公共停车位智能指示系统
CN107993478A (zh) * 2017-09-15 2018-05-04 路特迩科技(杭州)有限公司 基于车辆检测的泊位服务与管理系统及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112233454A (zh) * 2020-08-31 2021-01-15 浙江创泰科技有限公司 一种智能停车监控的方法

Also Published As

Publication number Publication date
CN107993478B (zh) 2019-05-03
CN107993478A (zh) 2018-05-04

Similar Documents

Publication Publication Date Title
WO2019052352A1 (zh) 基于车辆检测的泊位服务与管理系统及方法
WO2019052353A1 (zh) 基于泊位状态信息的泊位服务与管理系统及方法
CN110741226B (zh) 自动驾驶车辆增强系统的行动装置
CN103942977B (zh) 一种停车位管理系统及其管理方法
CN103345777B (zh) 一种车辆智能收费系统和方法
CN109204586A (zh) 智慧式无人代步车及共享系统及商业模式
CN109949605B (zh) 一种共享车位控制系统及其工作方法
CN205881197U (zh) 一种停车场智能管理系统
US20140344026A1 (en) Unified parking management system and method based on optical data processing
CN107564115A (zh) 一种智能停车场的管理运营系统及方法
CN107657827A (zh) 基于位联网的共享停车无人化智能化运营管理平台
CN108777076A (zh) 一种城市停车管理系统
CN108417080A (zh) 一种分时分位计价的共享停车位无人管理系统及方法
CN104680412A (zh) 一种基于手机app和云管理平台的自行车租赁系统及其实现方法
CN112712600B (zh) 基于移动物联网的停车场移动值守系统及方法
CN105303872B (zh) 停车收费系统
CN107067809A (zh) 一种智慧城市云计算停车管理信息系统
CN107724754A (zh) 云平台服务器及立体车库停车场控制系统
CN111768646A (zh) 一种基于nb-iot和智慧灯杆的智能停车系统及停车方法
CN107341551A (zh) 一种电动交通工具租赁系统及其管理方法
CN110322726A (zh) 一种基于高位视频的半封闭路侧停车管理系统及方法
CN113299109A (zh) 一种适用于智慧城市的智慧停车管理系统
CN107067509A (zh) 执行机构远程侦测系统
CN106355937A (zh) 一种停车场智能管理系统
CN109448430A (zh) 一种自动出入放行组件的控制系统及控制方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18855836

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18855836

Country of ref document: EP

Kind code of ref document: A1