EP3955219A2 - Procédé de fonctionnement d'un dispositif de stationnement - Google Patents

Procédé de fonctionnement d'un dispositif de stationnement Download PDF

Info

Publication number
EP3955219A2
EP3955219A2 EP21189664.2A EP21189664A EP3955219A2 EP 3955219 A2 EP3955219 A2 EP 3955219A2 EP 21189664 A EP21189664 A EP 21189664A EP 3955219 A2 EP3955219 A2 EP 3955219A2
Authority
EP
European Patent Office
Prior art keywords
parking
data record
vehicle
user
mobile terminal
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP21189664.2A
Other languages
German (de)
English (en)
Other versions
EP3955219A3 (fr
Inventor
Dr. Norbert Miller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Scheidt and Bachmann GmbH
Original Assignee
Scheidt and Bachmann GmbH
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 Scheidt and Bachmann GmbH filed Critical Scheidt and Bachmann GmbH
Publication of EP3955219A2 publication Critical patent/EP3955219A2/fr
Publication of EP3955219A3 publication Critical patent/EP3955219A3/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/02—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems
    • G07B15/04—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems comprising devices to free a barrier, turnstile, or the like
    • 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/145—Traffic control systems for road vehicles indicating individual free spaces in parking areas where the indication depends on the parking areas
    • G08G1/146—Traffic control systems for road vehicles indicating individual free spaces in parking areas where the indication depends on the parking areas where the parking area is a limited parking space, e.g. parking garage, restricted space
    • 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
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • G08G1/205—Indicating the location of the monitored vehicles as destination, e.g. accidents, stolen, rental

Definitions

  • the application relates to a method for operating a parking device.
  • the application relates to a parking system, an executable parking application and a mobile device, including the executable parking application.
  • a parking system with (off-street) parking devices such as parking lots, multi-storey car parks and the like, usually has one or more driveway arrangements.
  • a driveway arrangement generally includes one or more driveway devices.
  • a barrier with a pivotable barrier boom can be provided as the access device.
  • driving through a passage, at which the access device is arranged is monitored or controlled by a vehicle from a first area into a further area.
  • an access arrangement with at least one access device can be provided in order to control a vehicle driving through from a non-controlled area, for example a street, into a controlled area, for example the parking area.
  • driving into the parking device can be controlled by an access device at an entrance to the parking device.
  • an access arrangement with at least one access device can be provided in a parking device in order to control the passage of a vehicle from the controlled area into the non-controlled area.
  • driving out of a vehicle at an exit from the parking device can be controlled by an access device.
  • a parking device driving into a parking device is granted after the creation of a (physical) parking ticket, such as a short-term parking ticket, on the basis of a user action.
  • the short-term parking ticket in particular a paper ticket, is then paid for by a user at a billing device, for example in the form of a machine, after the end of a parking time and checked at the exit by a validator device of the access device. If the check is positive, the passage (in this case the exit) is released. However, if the validator device establishes that the ticket has not yet been paid for, for example, or that the payment was made too long ago, the access device remains closed and passage is blocked.
  • a constant concern for parking systems is to improve user comfort.
  • the required manual user actions are considered user-unfriendly.
  • parking systems and methods for operating parking devices are known from the prior art, in which the required user actions can be reduced.
  • At least one optical detection module can be arranged at the at least one entrance.
  • the optical detection module detects a vehicle registration number of an entering vehicle and transmits the detected vehicle registration number to a backend system of the parking system.
  • the vehicle registration number is stored in the backend system, preferably together with other drive-in data.
  • the vehicle registration number of the exiting vehicle can be detected by a further optical detection module. If it is determined that the vehicle registration number can be assigned to a parking process that has already been paid for, an entry device can be released in the manner described above, ie driving out can be released. Otherwise, the access device can remain blocked, ie exit can be blocked.
  • known parking devices can have at least one access device in order to enable users, in particular on foot, to access the parking area and thus the vehicles parked there.
  • the vehicle registration number can also be queried at an access device.
  • the user can be asked to manually enter his vehicle registration number at a corresponding user interface. Access can only be granted if the vehicle registration number entered corresponds to a vehicle registration number stored in the backend system, in particular if it is identical.
  • a disadvantage of the method of the prior art is the need for manual input at the billing device and/or the access device.
  • the time required for this is a disadvantage, which reduces user comfort.
  • errors regularly occur when entering a vehicle registration number, so that no billing and/or access release can take place.
  • the cause of the incorrect input can be found in the input specifications (e.g. hyphen, space etc.) and/or user errors.
  • User comfort is particularly reduced when the user has forgotten his vehicle registration number (e.g. because it is a rental car, the user has not had to enter the vehicle registration number for a long time, etc.) and therefore cannot initiate a billing process and/or cannot enter the parking area.
  • the application is therefore based on the object of providing a method for operating a parking device of a parking system, in which the disadvantages of the prior art are at least reduced and, in particular, user comfort is increased with simultaneously improved protection against infection and the error rate when entering the vehicle registration number is reduced.
  • the disadvantages of the prior art are at least reduced. In particular, this improves user comfort and input security and at the same time increases protection against infection.
  • the readable parking code stored on the mobile terminal can be used for (indirect) enabling exit from the parking device.
  • the parking code can be read wirelessly by a billing device and/or the access device. There is no need to enter the vehicle registration number manually. The time required for the user is reduced.
  • a parking system can include at least one (off-street) parking device, such as a parking lot, a parking garage or the like.
  • the parking system preferably has one or more driveway arrangements.
  • a driveway arrangement may include one or more driveway devices.
  • a barrier with at least one barrier boom pivotably arranged on a column can preferably be provided as the access device.
  • a roller door, pivoting door, sectional door, retractable bollard and the like can also be used as an alternative or in addition to the access device or blocking means in an access arrangement.
  • the access device can also manage without a material blocking means and, for example, control driving through a passage by means of a light signal.
  • An access arrangement with at least one access device can be arranged in particular at a drive-through of a parking device, such as an entrance and/or exit of a parking device.
  • an access section In front of an access device (seen in the direction of passage), in particular an access section can be provided in the first area, which a vehicle that is going to drive through the access device must first pass.
  • the access device monitors or controls driving through this passage through the access device from a first area into a further area.
  • driving into the parking device can be controlled by an access device at an entrance, for example.
  • driving out of the parking device can be controlled by an access device at an exit. It goes without saying that a parking device can have several entrances and/or exits.
  • a parking system can include at least one backend system.
  • a backend system can be formed by one or more (distributed) servers.
  • a backend system is arranged in particular at a distance from the at least one parking device.
  • the method according to the application can in particular be a computer program which can be executed by the backend system.
  • the backend system receives an entry data record.
  • the received drive-in data record contains at least one vehicle registration number of the vehicle detected when a vehicle drives into the parking device.
  • the vehicle registration number of the vehicle can be detected in particular by at least one optical detection module arranged at at least one entrance of the parking device, preferably in the form of at least one camera.
  • the method can include detecting, by at least one optical detection module arranged at the at least one entrance of the parking device, the vehicle registration number of the vehicle entering.
  • the vehicle registration number (e.g. A - BC - 123) can be determined from the captured image data provided by the optical capture module by an image data analysis module (e.g. based on a fuzzy analysis or the like) of the capture module (or the backend system).
  • the at least one optical detection module of the driveway can preferably cover at least one access section of the driveway.
  • each license plate number of each vehicle that will drive through the gateway can be detected. It can therefore be ensured that each vehicle number plate can be detected by each vehicle entering.
  • a vehicle registration number can preferably be detected by the optical detection module before the vehicle actually drives through an access device.
  • a vehicle can be allowed to drive through the entrance, at least based on the detected vehicle registration number of the vehicle.
  • the vehicle registration number can be evaluated before the access device is released.
  • the recorded vehicle number plate can be compared with a number plate list in which blocked vehicle number plates are stored, i.e. vehicle registration numbers of vehicles that are not authorized to use the parking device.
  • the access device at the at least one entrance can preferably only be released if it is determined that the vehicle is authorized to enter. Otherwise, the access device or the means of blocking the entrance can be blocked. This check can be carried out locally by a computer in the parking device or by the backend system.
  • the at least one entry data set received is stored.
  • the backend system can have a data storage arrangement to store the data therein.
  • the entry data record is unique throughout the system.
  • the application identifier is then assigned to this stored data in accordance with the application.
  • the application identifier is in particular a system-wide unique identifier of a parking application ("Parkapp") installed on a mobile terminal.
  • the application identifier enables identification of the mobile terminal device on which the parking application is installed. In this way, the user of the mobile device can be indirectly identified.
  • the parking application can include a user identifier.
  • the at least one stored entry data record is assigned an application identifier of a user (or his mobile device on which the parking application is stored) who has driven his vehicle into the parking device and has triggered the storage of the entry data record.
  • the user can be the driver or a passenger of the vehicle.
  • the backend system assigns an application identifier to the stored entry data record based on an assignment data record received from a mobile terminal device of a user of the vehicle that has been driven in.
  • the received or received mapping data record contains at least one piece of application identifier information.
  • the application identifier can be determined or derived at least from the application identifier information.
  • the application identifier can be transmitted from the mobile terminal device with a correspondingly installed parking application to the backend system as application identifier information.
  • the application identifier information can also be confirmation information that the application identifier already present in the backend system is the application identifier of the user's parking application. The final assignment is based on the confirmation information.
  • the entry data record and the associated application identifier are stored together by the backend system, for example in the data storage arrangement mentioned.
  • the data mentioned are stored as a common parking process data record.
  • the at least one readable parking code is generated by a generation module of the parking system based on the stored parking process data record. This means in particular that the parking code is based at least on a (system-wide unique) datum of the parking process data record or that this datum is encoded in order to generate the parking code. By decoding the parking code, the at least one datum can be determined again and thus the associated parking process data record.
  • the parking code which can be read in particular by suitable reading devices, is stored in the mobile terminal device on which the parking application is installed with the application identifier that is assigned to the named parking transaction data record.
  • the parking code is stored in such a way that it can be read wirelessly from the mobile terminal device, for example controlled by the parking application of the mobile terminal device.
  • the receiving of the association data record by the backend system can include a transmission of the association data record from a mobile terminal device to the backend system via a wireless communication network, e.g.
  • a wireless communication network e.g.
  • communication between a mobile device and the backend system can take place via a cellular network or the like and/or a near-field network (e.g. WLAN, Bluetooth, etc.).
  • the communication between the backend system and the mobile terminal device can be encrypted.
  • the backend system and the mobile terminal device, in particular the parking application can have suitable encryption means.
  • the communication between the backend system and the at least one optical detection module of the parking device can be encrypted. Data security can be increased.
  • the at least one further entry date can be stored in the parking process data record.
  • all of the entry data mentioned can be recorded when a vehicle enters and stored by the backend system.
  • the drive-in time can be formed from the calendar date and time.
  • the drive-in time can be used (together with a parking end time and valid tariff data) to bill for the parking process.
  • the parking device identifier can be used to identify the parking device (uniquely throughout the system).
  • the entrance identifier enables in particular an identification (at least unambiguously across the parking device) of the entrance used by the vehicle.
  • driving out of the parking device can be released at least indirectly, depending on a check of a read parking code.
  • a parking area of a parking device can only be accessible to a user (on foot) via an access device.
  • the entry device may comprise a door or other controllable locking means.
  • a controllable actuator can be present, which can open and close the blocking means.
  • the access device can include at least one detection module, for example in the form of a reading module, set up at least for the wireless reading of a parking code stored on the mobile terminal device.
  • the user can bring their mobile device within range of the reading module in order to trigger the reading of the parking code.
  • the park code that has been read out can be checked.
  • the checking can in particular include a decoding of the parking code.
  • the date of a parking process data record determined in this way can be compared with the stored parking process data records, in particular by a verification module of the backend system. If it is determined that the data obtained from the parking code can be assigned to a (current) parking process or parking process data record, the access device, for example the door, can be released.
  • the blocking means and/or the actuator can be controlled with a corresponding release signal.
  • the access device can be blocked, in particular remain blocked.
  • the user By allowing a user access to the parking area, the user is indirectly enabled to exit the parking device with his vehicle using the parking code.
  • the parking system in particular the parking device, can include at least one billing device, preferably in the form of a payment machine.
  • the parking code can first be read wirelessly from the mobile terminal device by a detection module, such as a reading module.
  • a detection module such as a reading module.
  • the user can bring their mobile device within range of the detection module in order to trigger the reading of the parking code.
  • the billing device can at least initiate a billing process.
  • the billing device can transmit the read (and/or already decoded) parking code to the backend system.
  • the parking code can first be decoded.
  • the associated stored parking process data record can then be determined using the date of the parking process data record determined in this way.
  • a billing process can then be carried out, preferably by a billing module of the backend system, based on the determined parking process data record.
  • the arrival time information of the determined parking process data set can (together with a parking end time information, ie in particular the current point in time, and valid tariff data) be used to bill for the parking process (in a conventional manner).
  • a parking end time information ie in particular the current point in time, and valid tariff data
  • the amount to be paid can be determined and made available to the billing device.
  • the amount to be paid can be displayed by the billing device.
  • this information can be provided to the backend system.
  • This information can then be stored in the corresponding parking transaction record.
  • this parking transaction record can be marked as "paid” (the unaccounted parking sessions can be marked as "unpaid” or unmarked).
  • the marking can be done by setting at least one bit.
  • driving out can be released for the corresponding user.
  • the user is able to exit the parking device indirectly using the parking code.
  • An electronic receipt can preferably be created after payment of the amount to be paid. This can be transmitted to the mobile device or the parking application installed on it.
  • the detection module can enable bidirectional communication between the billing device and the mobile terminal device.
  • a time specification can be transmitted to the mobile terminal or to the parking application installed on it, which indicates until when it is possible to exit the parking device.
  • This time specification is also referred to as the "grace period". In this way, the user can be informed about the length of time until he has to leave the parking device. After the time has elapsed, an access device remains blocked.
  • the electronic receipt can be transmitted to the parking application when driving out of the parking device.
  • the vehicle registration number can also be captured by another optical detection module when driving out.
  • An associated parking process data record can be determined based on the detected vehicle license plate number, in particular by the backend system. It can then be checked whether the determined parking process data record is marked as "paid” or not. If this is the case, in particular the entry device of the exit can be released, so that driving out of the parking device is made possible. If the parking transaction record is marked as "not paid” (or the above-mentioned "grace period" has already expired), the access device can be blocked.
  • Reading and decoding as well as determination of the parking process data record can take place in the manner described above. Then in the manner described above it can be determined whether the determined parking transaction record is marked as "paid” (or not). A drive-in device is released depending on whether the determined parking process data record is marked as “paid” (or not). Here, too, the "grace period" mentioned can be checked.
  • the received assignment data record can be a vehicle registration number of the user's vehicle detected by an optical detection module of the user's mobile terminal device.
  • the optical detection for example by a camera of the mobile device, can be controlled by the parking application.
  • the parking application may prompt the user to take a corresponding photo of the vehicle's license plate number.
  • the parking application can carry out a pre-check to determine whether the quality of the recorded image data is sufficient for identifying the vehicle license plate number. If the quality is not sufficient, the user can be prompted again to take a corresponding photo.
  • the parking application can determine the vehicle registration number itself from the image data. Alternatively, this can be done through the backend system.
  • the parking application can preferably generate an assignment data record, comprising the recorded vehicle license plate number and, as application identification information, the application identification of the parking application.
  • the parking application can cause the generated assignment data record to be sent to the backend system through a communication interface of the mobile terminal device.
  • a particular advantage of this embodiment is that the user does not have to register in the parking system. So there will be no user data is permanently stored by the user in the backend system, for example in a user data record or user account.
  • a (BLE) advertising message can be transmitted by a near-field transmission device (e.g. a Bluetooth beacon, preferably a BLE (Bluetooth Low Energy) beacon) of the parking device.
  • the advertising message can include instructions which, when executed, cause the parking application to be started.
  • the instructions can contain information that a vehicle registration number should be recorded and sent by the mobile terminal device.
  • the parking application can also be started by the user himself.
  • a BLE advertising signal or message can be sent from almost any mobile device, in particular with a commercially available operating system (e.g. Apple iOS, Google Android, Microsoft Windows Mobile, Microsoft Mobile Phone, Blackberry OS, Symbian OS, Firefox OS, Tizen, Aliyun OS), can be received and evaluated.
  • a commercially available operating system e.g. Apple iOS, Google Android, Microsoft Windows Mobile, Microsoft Mobile Phone, Blackberry OS, Symbian OS, Firefox OS, Tizen, Aliyun OS
  • a parking device of the parking system it may first be necessary for the user to register with this system before using a parking device of the parking system for the first time (e.g. to park a vehicle in the parking device) and/or in an installation process of the parking application.
  • a user data record or user account for the registered user can be created in the parking system, in particular the backend system of the parking system (also known as the background system), by storing the user's identification data in the backend system, such as a unique (user) identifier (ID) of the user, vehicle registration number of the user, application identifier of the installed parking application, authentication data, eg a password, and for example billing data, eg credit card data or account details, address data or other data for billing. In its entirety, this data is called user master data.
  • the parking application with the registered application ID can be installed on the user's mobile device in the form of a so-called app.
  • a detected vehicle registration number of a vehicle that has been driven in can first be compared with the stored vehicle registration number of the stored user data sets.
  • the corresponding user data record can be determined by detecting, in particular, an identity between the recorded vehicle registration number and a stored vehicle registration number.
  • the backend system can send the request message to the (precisely one) mobile device for which the application ID is stored.
  • the query message contains, in particular, a query as to whether the user has (actually) entered the parking device. It can therefore be queried whether the determination of the user data record, based on the registered vehicle registration number, was correct.
  • the user can check whether he has actually driven into a specific parking device with a vehicle. If this is the case, the user can confirm this manually on their mobile device, for example.
  • the request message can be displayed by the (enabled) parking application to request user confirmation.
  • the parking application can cause the response message to be sent to the backend system.
  • the user can also state that he has not entered the parking device.
  • the assignment can be finalized and the parking transaction data record created in this way can be saved. If the response message is received in the negative, the backend system does not assign an application identifier to the parking transaction data record, no parking code is generated for the mobile device, and a (possibly different) user must initiate the billing process to pay for the parking transaction in a known manner by manually entering the license plate number , the user may also have to initiate the release of access devices by manually entering the license plate number.
  • the position of mobile terminals can be determined in addition to detecting the vehicle registration number.
  • various methods can be used to determine the position (e.g. GPS positioning, trilateration positioning, etc.).
  • the determination of the position of the mobile terminal device in particular to determine whether the mobile terminal device is in the vehicle from which the vehicle registration number was recorded, can be carried out by a position determination device which includes a group antenna arrangement.
  • a position determination device which includes a group antenna arrangement, can be positioned at the entrance.
  • the position of a mobile terminal device can be determined with a particularly high degree of accuracy (in particular between 0.3 m and 0.5 m). will. This makes it possible to determine in front of which entrance a mobile device is actually located, even if there are two or more entrances (immediately) next to one another. In this way, an application identifier of the mobile terminal device can be assigned correctly to a vehicle license plate number with a high level of reliability.
  • a group antenna arrangement can process an information signal, ie in particular receive and/or transmit the information signal.
  • a group antenna arrangement enables the evaluation of at least one unmodulated signal section of an information signal such that position data of a mobile terminal device that interacts with the group arrangement using the at least one information signal can be determined with a particularly high level of accuracy.
  • a group antenna arrangement according to the application (also called a phased array antenna) has in particular a plurality of access antennas arranged adjacent to one another.
  • the at least two access antennas of a group antenna arrangement are electrically interconnected.
  • the access antennas have in particular a defined structure and/or a defined position in relation to one another, in particular a defined distance from one another.
  • the structure and the position of the access antennas can be selected depending at least on the frequency of the information signal to be processed.
  • the access antennas can be arranged parallel to one another, each with the same spacing.
  • the approach antennas of a group antenna arrangement are identical in shape.
  • a driveway antenna is designed to transmit and/or receive an information signal.
  • An information signal according to the application is in particular a data packet signal with a modulated signal section and an unmodulated signal section of an electromagnetic signal.
  • the modulated signal section contains data content (eg preamble, access address, PDU, CRC) in a conventional manner.
  • an information signal according to the application contains a unmodulated signal section (eg 1 to 300 ⁇ s unmodulated signal duration, preferably 16 to 160 ⁇ s).
  • the unmodulated signal section provides a constant frequency which, according to the application, can be evaluated for position determination.
  • the unmodulated signal section does not carry data content, so the unmodulated signal section is neither frequency nor amplitude modulated.
  • the unmodulated signal section can be demodulated using signal technology.
  • the unmodulated signal section is divided into two paths in a so-called I&Q process, one path of demodulation is carried out with the original phase position (English: in phase) and results in the I data, the second path is carried out with a reference frequency that is phase-shifted by 90° performed and results in the Q-data (English: quadrature).
  • the information signal is preferably a near-field information signal, e.g. based on one of the technologies such as Bluetooth, Wibree, WiMAX, ZigBee, WLAN or NFC.
  • the information signal may be a Bluetooth information signal, more preferably a Bluetooth version 5.X (or higher) information signal.
  • the information signal can preferably be an advertising signal.
  • the advertising signal can be a Bluetooth Low Energy (BLE) signal (at least version 5.X).
  • BLE Bluetooth Low Energy
  • a mobile terminal After a mobile terminal has been determined, which can be assigned to a detected vehicle registration number, it can be determined whether the application identifier of the parking application installed on the mobile terminal is stored in one of the preferred plurality of user data records. If this is the case, a request message can be sent based on the specific user data record, in particular the application identifier, in particular in a manner analogous to the previous statements.
  • the request message after the request message has been received, it can be checked whether the user has actually driven into a specific parking device with a vehicle. If this is the case, the user can, for example, confirm this manually on his mobile user terminal, as has already been described above. Upon detection of such a manual action, the parking application can cause the response message to be sent. In other variants of the registration, it can be provided that the user can also state that he has not entered the parking device. Upon receipt of the response message with a corresponding confirmation date or corresponding confirmation information, the assignment can be finalized and the parking transaction data record created in this way can be saved.
  • the assignment data record can contain at least one ticket date of a physical ticket (e.g. paper ticket) detected by a detection module of the mobile terminal device, which was issued at the entrance to the parking device.
  • the recorded data and the application ID can be transmitted to the backend system.
  • the ticket date and the application identifier as application identifier information
  • a previously described assignment can be made.
  • the at least one parking code can be generated based on the vehicle registration number and/or other data of the parking process data record.
  • both the vehicle registration number and the parking transaction record are identifiers (one-to-one throughout the system).
  • the system-wide unique parking code can be generated randomly, i.e. independently of other identifiers, and can be assigned to the latter in the backend system.
  • generating the parking code can include generating an optically readable parking code.
  • a barcode and/or QR code can be generated. This can be captured by an optical capture module (the billing device, access device, validator device, etc.), such as a camera.
  • an optical capture module the billing device, access device, validator device, etc.
  • a corresponding optical parking code can be displayed on the display device of the mobile terminal device in order to enable the parking code to be read out by an optical detection module.
  • generating the parking code can include generating a parking code that can be read by a near-field reader, in particular a Bluetooth-based parking code and/or an NFC-based parking code.
  • a corresponding parking code can be read automatically by a Bluetooth reading module, ie without any user action.
  • An NFC reader or the like can also be provided.
  • a billing device and/or an access device and/or a validator device can have a detection module in the form of a near-field reader, in particular a Bluetooth reader.
  • the range of such a near-field reader can preferably be set in such a way (e.g. to a maximum of 2 m for an access device or to a maximum of 0.5 m for a billing device) so that a parking code can only be read when the mobile device and thus the user are in is sufficiently close to the respective device (e.g. when the billing device is directly in front of the billing device).
  • a Release of the access device or a billing process takes place in such a way that the user experiences almost no time delay.
  • the range can be set in particular by specifying a minimum signal strength (in particular an RSSI (Received Signal Strength Indicator) limit value).
  • RSSI Received Signal Strength Indicator
  • a further aspect of the application is a parking system, in particular set up to carry out the method described above.
  • the parking system comprises at least one receiving module, set up to receive an entry data record, containing at least one vehicle registration number of the vehicle detected when a vehicle enters the parking device.
  • the parking system includes at least one first memory module, set up to store the received drive-in data record.
  • the parking system comprises at least one assignment module, set up to assign an application identifier to the stored entry data record, based on an assignment data record received from a mobile terminal of a user of the vehicle that has been driven in, containing at least one piece of application identifier information, wherein the application identifier can be determined at least from the application identifier information.
  • the first memory module is set up to store the assigned application identifier at least together with the entry data record in a parking process data record.
  • the parking system includes at least one generation module, set up to generate at least one readable parking code, assigned to the stored parking process data set.
  • the parking system comprises at least one output module, set up to output the generated parking code by the user's mobile device in such a way that the parking code can be read wirelessly from the mobile device.
  • the parking system preferably includes at least one backend system.
  • the backend system can include the receiving module, the first memory module and the allocation module.
  • the backend system can also include a data storage arrangement that can be controlled by the first storage module.
  • the data storage arrangement for example, the at least one parking process data set can be stored by the first storage module.
  • the backend system can include at least one verification module.
  • the verification module can be set up to determine whether a read parking code (provided, for example, by a detection module of a billing device, an access device and/or a validator device) corresponds to a stored parking transaction data record.
  • the read parking code can be decoded and the resulting data (preferably a vehicle registration number and/or an entry data record) can be compared with the stored data of the at least one parking process data record.
  • the backend system can have an accounting module.
  • the billing module can be set up to carry out a billing process based on a parking process data record determined (by the checking module) (in particular in a conventional manner).
  • the generation module can be implemented in the backend system.
  • the generation module can preferably be implemented in a parking application that can be installed on the mobile terminal device.
  • the data required for generating a parking code (preferably a vehicle registration number and/or an entry data record) can be made available to the parking application (eg by the backend system).
  • the generation module can then generate at least one parking code, preferably an optically readable parking code and a parking code that can be read by a near-field reader, by Vehicle license plate number and/or other data from the entry data set is/are coded according to a predetermined coding rule.
  • a corresponding decoding rule can be known to a decoding module.
  • the output module can preferably be implemented in a parking application that can be installed on the mobile terminal device.
  • the output module can be set up in such a way that the at least one parking code can be read wirelessly from the mobile terminal device.
  • the parking system can comprise at least one parking device (described above).
  • the parking system can include at least one (previously described) optical detection module.
  • the parking system can comprise at least one (previously described) mobile terminal device on which a (previously described) parking application is installed.
  • a further aspect of the application is a parking application, in particular in the form of a software application that can be executed by a processor of a user's mobile terminal device, for installation on a mobile terminal device.
  • the parking application comprises at least one receiving module configured to receive a vehicle registration number of the user's vehicle detected by an optical detection module of the mobile terminal device.
  • the parking application includes at least one transmission module, set up to effect the transmission of an assignment data record containing at least the received vehicle registration number and an application identifier of the parking application.
  • the parking application includes at least one generation module (described above) configured to generate a parking code associated with the parking transaction record.
  • the parking application includes at least one output module (in particular the output module described above) set up to output the generated parking code by the user's mobile device in such a way that the parking code can be read wirelessly from the mobile device.
  • the parking application is in particular a software application that can be installed on a mobile terminal device.
  • the parking application may be required to drive through an access device at an entrance and/or exit of a parking device and, for example, to properly use a parking service.
  • each parking application can be assigned a system-wide, unique application identifier.
  • program memory is non-volatile memory such as flash memory, magnetic memory, EEPROM memory (Electrically Erasable Programmable Read Only Memory), and/or optical memory.
  • a mobile terminal can have a main memory, for example a volatile or non-volatile memory, in particular a random-access memory (RAM), such as a static RAM memory (SRAM), a dynamic RAM memory (DRAM), a ferroelectric random access memory (FeRAM) and/or magnetic random access memory (MRAM).
  • RAM random-access memory
  • SRAM static RAM memory
  • DRAM dynamic RAM memory
  • FeRAM ferroelectric random access memory
  • MRAM magnetic random access memory
  • the processor of the mobile terminal can, for example, store intermediate results or the like in the main memory.
  • Yet another aspect is a mobile device, comprising at least one parking application installed on the mobile device and described above.
  • Exemplary and non-exhaustive mobile end devices are smartphones, tablet computers, mobile game consoles, laptops, netbooks, data glasses, smart watches and similar wearables.
  • a mobile terminal can be a dedicated parking ticketing device designed exclusively for a parking application.
  • a previously described module, element, etc. can at least partially comprise hardware elements (e.g. processor, storage means, etc.) and/or at least partially software elements (e.g. executable code). It is further noted that terms such as “first”; “second” etc. do not indicate an order, but serve in particular to differentiate between two elements (e.g. memory module, area etc.).
  • the figure 1 10 shows a schematic view of an embodiment of a parking system 100 according to the present application.
  • the parking system 100 shown comprises at least one backend system 102.
  • the backend system 102 can be formed from one or more server(s) which is/are arranged remotely from the at least one parking device 116, for example.
  • the present backend system 102 comprises at least one receiving module 104, preferably in the form of at least one communication module 104 for receiving and sending data, at least one first storage module 106, at least one allocation module 108, at least one data storage arrangement 110, at least one verification module 112 and at least one billing module 114 .
  • the present parking system 100 comprises at least one (off-street) parking device 116.
  • a parking system can preferably comprise a plurality of parking devices.
  • the parking device 116 is a multi-storey car park 116, for example.
  • the parking device 116 may include at least one entrance 118 and at least one exit 130 . It goes without saying that two or more entrances and/or two or more exits can be provided.
  • the driveway 118 comprises a driveway arrangement with a first driveway device 120 and at least one optical detection module 128, preferably in the form of a camera 128.
  • the first driveway device 120 is set up to control or monitor driving through the driveway 118.
  • access device 120 can be used to control a vehicle 124 driving through driveway 118 from a first area 122, in particular an access section 122 (which is arranged in front of access device 120 in the direction of travel of a vehicle 124) into a further area 156.
  • the first area 122 is in particular a non-controlled area and the further area 156 is the controlled area, in particular the (beginning of) parking area(s) 156 of parking facility 116.
  • a controllable actuator (not shown) (e.g. an electric motor) can be provided.
  • the actuator can be set up to move a barrier boom between a blocked position and an open position, depending on a control signal. It goes without saying that other access devices can be provided in other variants.
  • a release that is to say in the present case in particular an opening of the barrier, can depend on whether a user is authorized to drive into the parking device (or not).
  • a vehicle license plate number 126 of an entering vehicle 124 can be detected by the optical detection module 128 before the vehicle 124 actually drives into the parking device 116 .
  • the optical detection module 128 can be aligned in such a way that the access section 122 is monitored.
  • Driving through the driveway 118 can be enabled at least on the basis of the detected vehicle license plate number 126 of the vehicle 124 .
  • the recorded vehicle number plate can be evaluated (locally by a parking device computer (not shown) and/or by the backend system 102).
  • the registered vehicle number plate can at least be compared with a number plate list in which blocked vehicle number plates are stored, that is to say vehicle number plates of vehicles that are not authorized to use parking device 116 .
  • the access device 120 at the at least one entrance 118 can preferably only be released if it is determined that the vehicle 124 is authorized to enter, ie the license plate 126 is not in the said number plate list is stored. Otherwise the access device 120 or the blocking means 120 of the driveway 118 can be blocked.
  • a user can also have a parking ticket medium (not shown) with authentication data that can be read out by an interface device (not shown) of the access device 120, for example in the form of an access code (for example magnetic stripe code, barcode, QR code, RFID identifier, another readable user or mobile device identifier, etc.).
  • an access code for example magnetic stripe code, barcode, QR code, RFID identifier, another readable user or mobile device identifier, etc.
  • the at least one exit 130 of the parking device comprises a further access arrangement with a second access device 132 and at least one further optical detection module 134, preferably in the form of a camera 134.
  • the second access device 132 can be formed similarly to the first access device 120.
  • a validator device 140 can optionally be arranged at the exit 130 .
  • the validator device 140 can include, in particular, a detection module 142 (e.g. a scanner for optically scanning barcodes and/or QR codes and/or a near-field reader), set up to read a parking code from a mobile user terminal 160.
  • a detection module 142 e.g. a scanner for optically scanning barcodes and/or QR codes and/or a near-field reader
  • the validator device 140 can also be conventional be set up to capture paper tickets.
  • the parking device 116 preferably includes at least one billing device 150, preferably in the form of a pay machine 150.
  • the billing device 150 can in particular include at least one detection module 154 (e.g. a scanner for optically scanning barcodes and/or QR codes and/or a near-field reader), set up to read a parking code from a mobile user terminal 160.
  • the billing device 150 can also be set up for the conventional detection of paper tickets.
  • the present billing device 150 has a display 152 .
  • an access device 144 of the parking device 116 is shown as an example.
  • the access device 144 comprises a lockable door 146 and at least one detection module 148 (e.g. a scanner for optically scanning barcodes and/or QR codes and/or a near-field reader), set up to read a parking code from a mobile user terminal 160.
  • a detection module 148 e.g. a scanner for optically scanning barcodes and/or QR codes and/or a near-field reader
  • a user gets through the access device 144 to his vehicle parked in the parking device 116 . It goes without saying that the user can also leave the parking device 116 through the entry device 144 after the vehicle has been parked.
  • the backend system 102 can communicate (preferably bidirectionally) with the modules 120, 128, 132, 134, 148 and 154 of the parking system 100 via at least one (wireless and/or wired) communication network 158.
  • this communication can be at least partially encrypted.
  • the parking system 100 can include at least one mobile terminal device 160 .
  • the mobile terminal device 160 is a smartphone 160 with a parking application 164 installed on it.
  • the parking application 164 comprises a receiving module 166, a transmitting module 168 (in variants of the application, a common communication module can be provided to form a transmitting/receiving module), a generation module 170 and an output module 174.
  • Mobile terminal device 160 also has at least one communication interface that is set up for communication with backend system 102 via at least one (wireless and/or wired) communication network 158 .
  • the communication can be at least partially encrypted.
  • Mobile terminal device 160 also includes at least one optical detection module 172, preferably in the form of a camera 172.
  • FIG. 11 shows a diagram of an embodiment of a method for operating a parking device 116 according to the present application. The method can be performed at least in part by the backend system 102 .
  • a first (optional) step 301 at least one optical detection module 128 arranged at the at least one entrance 118 of the parking device 116 detects the vehicle registration number 126 of the entering vehicle 124.
  • an image data evaluation module e.g. based on a fuzzy evaluation.
  • the vehicle license plate number e.g, X - XX - 123
  • a vehicle 124 entry authorization check may be performed as previously described.
  • backend system 102 receives an entry data record containing at least the vehicle registration number detected when vehicle 124 entered parking device 116 .
  • the entry data record received by the receiving module 104 can also contain entry time information (preferably calendar date and time, e.g. January 1st, 2021, 12:00:00) of the entered vehicle 124, a parking device identifier of the parking device 116 and an entry identifier of the entrance 118.
  • the entry data record can be transmitted to the backend system by the acquisition module 128 .
  • step 303 the received entry data record is stored by a first storage module 106 in a data storage arrangement 110 of the backend system.
  • backend system 102 assigns an application identifier to the stored entry data record, based on an assignment data record received from a mobile terminal device 160 of a user of vehicle 124 that has been driven in.
  • the assignment data record contains at least one item of application identifier information, it being possible for the application identifier of the parking application 164 stored on the mobile terminal device 160 to be determined at least from the application identifier information item.
  • the application identifier information may include a vehicle license plate number of the vehicle 124 that has been driven in, as captured by the camera 172 of the mobile terminal device 160 .
  • the user can photograph the license plate of his vehicle using the camera 172.
  • the vehicle registration number can be read out alphanumerically from the recorded image data via an image/writing recognition function integrated in the parking application 162 .
  • the license plate data or the vehicle license plate number can be stored locally on the mobile terminal device 160 .
  • the alphanumeric license plate data stored on the mobile device 160 is compared with the vehicle license plate number of the backend system 102 (e.g. by the parking application 164 or the backend system 102). If the data match (i.e. it is determined that a vehicle 124 with the vehicle registration number has entered the parking device 116), then an association is made between the application identifier and the stored entry data record. Since the application identifier is in a 1:1 relationship to the mobile terminal device 160 used, the entry data record is therefore assigned to exactly one mobile terminal device 160 .
  • the assignment in particular in the case of registered users or registered parking applications, can be based on a reply message and/or paper ticket functions.
  • step 305 the assigned application identifier is stored at least together with the vehicle identifier, in particular by the first storage module 108 of the backend system 102.
  • the assigned application identifier together with the vehicle identifier can be stored in particular in the data storage arrangement 110.
  • At least one readable parking code is generated based on the stored parking process data record, preferably by the generation module 170.
  • Two readable parking codes can preferably be generated, for example a QR code and a code that can be read by a Bluetooth detection module.
  • the generated parking code contains the vehicle registration number as data content, which can be determined from the parking code by decoding the parking code.
  • a predetermined coding rule can be applied to the vehicle registration number by the generation module in order to generate the parking code.
  • At least one decoding module may apply a corresponding decoding rule to re-decode a parking code to determine the license plate number
  • the at least one generated parking code can be output locally by the user's mobile terminal device 160, in particular by the output module 174, such that the parking code can be read wirelessly from the mobile terminal device 160.
  • local storage on the mobile terminal device 160 can take place at least temporarily (e.g. in a main memory).
  • step 308 enabling of a vehicle 124 to drive through at least one exit 130 of the parking device 116 can take place, at least based on a parking code read out by the mobile terminal device 160 of the user of the vehicle 124 .
  • the optical parking code can be used when performing a billing process for a parking process.
  • the parking code can be read wirelessly by the detection module 154 at the billing device 150 .
  • the read parking code can be transmitted to the backend system 102 and e.g. decoded by a decoding module.
  • the verification module 112 can then verify whether the vehicle registration number determined by the decoding is identical to a vehicle registration number that is stored in a parking transaction data record. If this is the case, the billing module 114 can bill the corresponding parking process (in conventional way), in particular based on the stored entry data of the parking process data set, the current time and valid tariff data.
  • At least the amount determined and to be paid for the parking process can be transmitted to the billing device 150 and displayed by it. After a payment has been made, the stored parking process data record can be marked as "paid".
  • the vehicle registration number of the vehicle 124 can first be recorded and compared with the stored vehicle registration number. If, in particular, an identical vehicle license plate number is determined and it is determined that the parking process data set is marked as "paid", driving through the second access device 134 can be enabled, for example by the access device 134 being activated with a corresponding enable signal. As already described, the "grace period" can also be checked.
  • the access device 134 can be controlled with a corresponding blocking signal so that it is or remains blocked.
  • the vehicle registration number can be partially dirty or environmental influences can make correct detection and identification of the vehicle registration number difficult.
  • the parking code can be recorded in step 310, in particular by the recording module 142 of the validator device 140.
  • the parking code that has been read out can then be decoded in the manner described above and the vehicle license plate number, which is in particular identical and stored in the backend system 102, can then be determined. If it is then established that the parking process data record is marked as paid, driving through the second access device 134 can be released. If, on the other hand, it is determined that the parking process has not been paid for, the access device 134 can be blocked or remain blocked.
  • the recording module 148 of an access device 144 of the parking device 116 can optionally read out the parking code stored in the mobile terminal device 160.
  • the read parking code can then be decoded.
  • it can be determined whether, in particular, an identical vehicle identifier is stored in the backend system 102 . If this is the case, the access device 144 can be released, in particular a door 146 or the like. If no license plate number can be determined, the entry device 144 may remain disabled.
  • FIG. 12 shows a schematic view of another embodiment of a parking system 200 according to the present application.
  • a parking system 200 according to the present application.
  • only the exemplary driveway 218 of a parking device is shown for the sake of a better overview.
  • a backend system and the other components of the parking device are not shown.
  • the access device 220 shown is in the present case formed as a barrier 220 with a barrier boom 201 attached to a column 203 . It is understood that other forms of access devices can be used.
  • the parking system 200 in the present case comprises at least one group antenna arrangement 276.
  • the group antenna arrangement 276 can be assigned to the access device 220 (uniquely throughout the system).
  • the antenna array assembly 276 and the access device 220 can form an access set.
  • the group antenna arrangement 276 is arranged above the associated access device 220 .
  • the first array antenna assembly 276 is vertically spaced from the first access device 220.
  • the array antenna assembly 276 may be disposed on and/or integrated with a height restriction device 288 (e.g., in the form of a height restriction bar 288).
  • the group antenna arrangement 276 can alternatively or additionally be arranged at another location, for example on and/or in a ceiling or a roof of a multi-storey car park (above the access device 220). In still other variants of the application, the group antenna arrangement 276 can alternatively or additionally be arranged in or on the access device 220, for example integrated in the column 203.
  • the group antenna arrangement 276 comprises a plurality of (equally designed) driveway antennas 278.
  • three driveway antennas 278 are shown as an example. It goes without saying that only two or more than three access antennas can be provided.
  • the access antennas 278 are electrically interconnected.
  • the access antennas 278 have, in particular, a defined structure and defined position in relation to one another, in particular a defined distance from one another. This can at least depend on the frequency of the data to be processed depend on the information signal.
  • the driveway antennas 278 may be arranged parallel to each other, each equally spaced. It goes without saying that other arrangements are also possible, such as the arrangement along a semicircle or quadrant.
  • the first group antenna arrangement 276 is set up for processing at least one information signal containing at least one modulated signal section and at least one unmodulated signal section.
  • the information signal that can be processed can preferably be a Bluetooth information signal (at least version 5.X).
  • a Bluetooth information signal in particular a BLE advertising signal
  • the following explanations can be applied to the other information signals described above.
  • the combination of using such an information signal with a group antenna arrangement 276 assigned to the access device 220 makes it possible to determine the position of a mobile terminal device 260 in relation to the group antenna arrangement 276 or the correspondingly assigned access device 220 (with a particularly high level of accuracy). This allows a position determination device 290 to determine whether a mobile terminal device 260 is located in the entering vehicle 224 (or not) when a vehicle registration number of a vehicle 224 is detected at the entrance 218 of the parking device by the camera 228 .
  • the group antenna arrangement 276 shown comprises a position determination device 290.
  • the position determination device 290 in the present case comprises a demodulation module 282, a position determination module 284 and a receiving device interface 286. It goes without saying that further components can be provided, such as filters, amplifiers, A/D converters, etc .
  • Each gateway antenna 278 may provide an antenna signal to the demodulation module 282 based on a received information signal.
  • the demodulation module 282 can demodulate the respective antenna signal.
  • the demodulation module 282 can be set up to determine an amplitude datum and a phase datum for each of the antenna signals. An amplitude datum and a phase datum are preferably determined for the respective unmodulated signal section of a received information signal.
  • the modulated signal section of the information signal can also be demodulated in order to decode and, in particular, evaluate the data content contained therein (e.g. application identifier, authentication date, time stamp and/or the like).
  • the determined data can be provided to the position determination module 284 .
  • the position determination module 284 is set up in particular to determine a first angle data item based on the determined amplitude data and the determined phase data of the demodulated antenna signals.
  • the instantaneous position data of the transmitting mobile terminal device 260 can then be determined at least in part, at least based on the first angle datum.
  • the position can be determined, for example, based on the first angle datum and the RSSI (which can be determined in a known manner, for example, by an RSSI module, not shown, of the array antenna arrangement 276 ) of the information signal received by the access antennas 278 .
  • the RSSI which can be determined in a known manner, for example, by an RSSI module, not shown, of the array antenna arrangement 276 .
  • the position can be determined based on the first angle datum and a further angle datum that was determined by an adjacent antenna array arrangement. Different In other words, triangulation can be done to determine the location data of the mobile terminal.
  • Neighboring means in particular that the group antenna arrangement is at least in the same access arrangement.
  • the antenna arrays are immediately adjacent.
  • the adjacent group antenna arrangement can be assigned to a further passage that is closest.
  • the mobile terminal device 260 can have a communication module with an antenna in order to transmit the information signal (in particular periodically and/or almost continuously).
  • the transmission can be controlled by a parking application (not shown) installed on the mobile terminal 260, for example.
  • a transmission can be triggered by a trigger signal that is transmitted by a transmission device (not shown) of the parking system 200 .
  • a (Bluetooth) beacon can be provided as a transmission device, which emits a triggering signal.
  • the trigger signal can contain a code which—after being received by the mobile terminal device 260—when executed by the mobile terminal device 260 (controlled by an activated parking application) causes the information signal to be sent.
  • the parking application can be activated beforehand by the user, for example, or by a wake-up signal from another transmitter (not shown) of the parking system 200.
  • Array antenna assembly 276 may be formed in an antenna housing having a housing wall that is adjacent to the driveway antennas.
  • the housing wall may be formed from a material (e.g., tinned copper foil, plastic, glass, plasterboard) that attenuates and/or filters electromagnetic signals.
  • the group antenna arrangement comprises a position determination device
  • a so-called evaluation of the "angle of arrival” takes place.
  • the group antenna arrangement can emit a group information signal, which can be evaluated in an analogous manner by the mobile terminal device or the parking application installed on it.
  • a so-called evaluation of the "angle of departure” takes place. Both evaluations allow the position data of the mobile terminal device to be determined with a high degree of accuracy in relation to the respective at least one group antenna arrangement (and thus in relation to the respectively assigned access device).
EP21189664.2A 2020-08-10 2021-08-04 Procédé de fonctionnement d'un dispositif de stationnement Pending EP3955219A3 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
DE102020004860.9A DE102020004860A1 (de) 2020-08-10 2020-08-10 Verfahren zum Betreiben einer Parkvorrichtung

Publications (2)

Publication Number Publication Date
EP3955219A2 true EP3955219A2 (fr) 2022-02-16
EP3955219A3 EP3955219A3 (fr) 2022-07-06

Family

ID=77518893

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21189664.2A Pending EP3955219A3 (fr) 2020-08-10 2021-08-04 Procédé de fonctionnement d'un dispositif de stationnement

Country Status (2)

Country Link
EP (1) EP3955219A3 (fr)
DE (1) DE102020004860A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115324398A (zh) * 2022-08-26 2022-11-11 温州金来建设有限公司 一种智能化停车场及其使用方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102022207972A1 (de) 2022-08-02 2024-02-08 Robert Bosch Gesellschaft mit beschränkter Haftung System und Verfahren zum Überwachen eines Parkplatzes

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030130893A1 (en) * 2000-08-11 2003-07-10 Telanon, Inc. Systems, methods, and computer program products for privacy protection
AUPS207502A0 (en) * 2002-05-02 2002-06-06 Cds Worldwide Pty Ltd Parking system
EP2546795A3 (fr) * 2011-07-11 2013-01-30 Richard Rowe Services de stationnement avec programmes de fidélité par zone
ES2555709B1 (es) * 2014-07-02 2016-10-19 Park Smart Solutions, S.L. Sistema de pago mediante un dispositivo móvil y procedimiento de pago asociado
WO2016016068A1 (fr) * 2014-07-29 2016-02-04 Inventio Ag Procédé et système de contrôle d'accès aux véhicules
CN105469452A (zh) * 2014-09-11 2016-04-06 颜振 无人化管理停车场的缴费方法及其装置
CN105279972B (zh) * 2015-10-27 2017-10-31 成都千帆科技开发有限公司 一种含有手机信息识别和车牌识别摄像机的道闸装置
JP6425103B2 (ja) * 2016-05-10 2018-11-21 パーキングクラウド カンパニー，リミテッド 車両番号と車両番号から認識された車種に基づいた車両入出場管理方法及び車両入出場管理システム
JP2018010340A (ja) * 2016-07-11 2018-01-18 三菱プレシジョン株式会社 駐車場管理システム
EP3491414A4 (fr) * 2016-07-29 2020-08-05 TMA Capital Australia Pty Ltd Système, procédé et programme informatique pour un système de surveillance
DE202016105195U1 (de) 2016-09-16 2017-02-07 krauth technology GmbH System zur Parkraumbewirtschaftung
CN113034709B (zh) * 2016-12-29 2023-05-12 西安艾润物联网技术服务有限责任公司 停车费自助缴纳方法及装置
CN107730634B (zh) * 2017-01-24 2020-07-31 西安艾润物联网技术服务有限责任公司 停车场无网络环境下的停车费在线支付方法、装置及系统
EP3407307B1 (fr) * 2017-05-23 2022-05-18 Scheidt & Bachmann GmbH Système de stationnement et son procédé de fonctionnement
CN108306924B (zh) * 2017-09-12 2021-06-29 福建联迪商用设备有限公司 一种通讯方法、通信终端、云服务器及通讯系统
CN108986239A (zh) * 2018-06-28 2018-12-11 西安艾润物联网技术服务有限责任公司 停车场管理方法、装置及计算机可读存储介质
CN109255847A (zh) * 2018-07-02 2019-01-22 北京筑梦园科技有限公司 一种车辆出场缴费校验方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115324398A (zh) * 2022-08-26 2022-11-11 温州金来建设有限公司 一种智能化停车场及其使用方法
CN115324398B (zh) * 2022-08-26 2024-04-30 温州金来建设有限公司 一种智能化停车场及其使用方法

Also Published As

Publication number Publication date
EP3955219A3 (fr) 2022-07-06
DE102020004860A1 (de) 2022-02-10

Similar Documents

Publication Publication Date Title
EP2835788B1 (fr) Procédé de contrôle d'entrée et de sortie pour des parcs de stationnement et installations de stationnement
EP2833329B1 (fr) Procédé et système destinés à améliorer un processus de stationnement payant de véhicule dans une installation de parking, programme informatique et produit-programme informatique
EP3955219A2 (fr) Procédé de fonctionnement d'un dispositif de stationnement
DE10009057A1 (de) Zugangskontrolleinrichtung
EP3051502A1 (fr) Systeme de controle d'entree de stationnement et procede de controle de l'entree dans un stationnement
US20150120527A1 (en) System and method for managing lease of properties
EP3407307B1 (fr) Système de stationnement et son procédé de fonctionnement
DE102017222434A1 (de) Verfahren zur Authentifizierung eines Kraftfahrzeugs
EP3929851A1 (fr) Procédé d'enregistrement d'un support billet
EP3033736A1 (fr) Système et procédé de gestion d'une opération de stationnement d'un véhicule dans une zone de stationnement payant et de gestion d'une opération de paiement des frais de stationnement
EP3382657B1 (fr) Procédé de fonctionnement d'un système d'accès
EP2949096B1 (fr) Production de donnés de position au moyen d'un protocole délimiteur de distance
DE102020113244A1 (de) Zugangssystem mit mindestens einem Gate
EP3910603A1 (fr) Système de stationnement
EP3252697B1 (fr) Dispositif de validation pour un systeme de ticket
EP3040947B1 (fr) Procédé destiné a éviter les mauvais usages d'autorisations d'accès d'un système de contrôle d'accès basé sur un identifiant
EP2023281A1 (fr) Procédé destiné à la commande et au paiement d'une autorisation d'accès, à la surveillance de l'autorisation d'accès, à l'accord d'une autorisation d'accès et/ou à la préparation d'informations liées à l'accès
EP4002306A1 (fr) Système de transport en boucle ouverte doté d'un système d'arrière-plan
EP3886057A1 (fr) Méthode pour la transmission de données précises sur la position
DE102013201730A1 (de) Bereitstellung von Positionsdaten mittels eines Distance-Bounding Protokolls
EP3819875B1 (fr) Procédé de fonctionnement d'un système de stationnement payant
WO2016128081A1 (fr) Système de contrôle
DE102022003533A1 (de) Verfahren zur Interaktion mit einem Mautsystem und Fahrzeug
DE102016105583A1 (de) Parkraumüberwachungssystem sowie Verfahren zur Parkraumüberwachung
DE102020200324A1 (de) Verfahren zur Zugangskontrolle sowie Zugangskontrollsystem

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: G08G 1/017 20060101ALI20220602BHEP

Ipc: G07B 15/04 20060101AFI20220602BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230103

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230427