Parking payment device, system and method

Abstract

A parking payment device disposed on a vehicle is provided. The parking payment device includes a first reading device and a controller. The first reading device is configured to read an identifiable marker disposed at or near a parking location. The controller is configured to identify the identifiable marker in response to an end of a parking process of the vehicle. The controller is further configured to communicate with a parking server to request a copy of the identifiable marker to be generated in or near the vehicle to pay for the parking based on the copy of the identifiable marker in response to an identification time of the identifiable marker exceeding a time threshold. A vehicle parking payment system and method are also provided.

Description

[Technical Field]

[0001] This application relates to payment devices, systems, and methods for parking fees, and in particular to devices, systems, and methods capable of paying parking fees by recognizing identifiable markers. [Background Technology]

[0002] Some automated parking payment systems work by recognizing a barcode located at a parking location. US Patent Application US20150149263A1 discloses a method for automated parking payment, including recognizing a scannable image barcode at a parking location, parsing the metadata contained in the barcode, sending the metadata, along with data indicating the start and / or end time of parking, to a parking server using a mobile device, calculating the parking fee based on the data, and automatically paying the fee. In such systems, the scannable image at the parking location must be intact; damage or obstruction can lead to recognition failures or generate incorrect data, and these errors are difficult for parking location administrators to detect. Therefore, there is a need for a parking payment system that improves the recognition process and is easier to manage. [Summary of the Invention]

[0003] This application provides a parking payment system and method that facilitates user payment and management, addressing at least one of the aforementioned problems.

[0004] According to one aspect of this application, a parking payment device is provided. The parking payment device includes a first reading device and a controller. The first reading device is configured to read an identifiable marker located at or near a parking location. The controller is configured to: identify the identifiable marker in response to the end of a vehicle parking process. The controller also communicates with a parking server in response to an identification time exceeding a time threshold to request the generation of a copy of the identifiable marker in or near the vehicle for payment of parking fees based on the copy of the identifiable marker.

[0005] In some embodiments, the parking server determines a copy of the corresponding identifiable tag based on the vehicle's location and parking position.

[0006] In some embodiments, the parking payment device further includes a display located in the vehicle, on which a copy of the identifiable tag is displayed. The display includes a second reading device for reading the copy of the identifiable tag to activate the parking payment process.

[0007] In some embodiments, the parking payment device further includes a display mounted on the vehicle, on which a copy of the identifiable tag is displayed. A user can use a second reading device to read and identify the copy of the identifiable tag.

[0008] In some embodiments, a copy of the identifiable marker is displayed at or near the parking location.

[0009] In some embodiments, the controller is further configured to stop displaying a copy of the identifiable marker in response to parking fees being paid.

[0010] In some embodiments, the controller is further configured to: stop displaying a copy of the identifiable tag in response to the display time of the copy exceeding a display time threshold.

[0011] In some embodiments, the controller is further configured to: in response to an ambient brightness less than a brightness threshold, communicate with the parking server to request the generation of a copy of an identifiable tag.

[0012] In some embodiments, the controller is further configured to report fault information of the identifiable tag to the parking server in response to the recognition time exceeding a threshold time.

[0013] According to another aspect of this application, a vehicle parking payment system is provided. The parking payment system includes a memory unit and a controller. The memory unit may include a parking location, a copy of an identifiable marker corresponding to the parking location, and a parking fee. The controller is configured to: receive parking location information and parking process completion information of the vehicle, and pay the parking fee based on the identifiable marker corresponding to the parking location. The controller is also configured to, in response to an identification time exceeding a time threshold, instruct the display of a copy of the identifiable marker in or near the vehicle, and pay the parking fee based on the copy of the identifiable marker.

[0014] In some embodiments, the controller is located in a parking server.

[0015] In some embodiments, a copy of the identifiable tag is displayed on a display. In some embodiments, the parking payment system further includes a projection device located at or near the parking location and communicating with a parking server. The projection device is configured to generate a copy of the identifiable tag at or near the vehicle in response to an instruction from the parking server. The projection device may include a manual switch.

[0016] In some embodiments, both the identifiable marker and a copy of the identifiable marker contain price information for the parking location. The parking server is further configured to calculate the parking fee based on the start and end times of the parking process and the price information contained in the identifiable marker. The parking server is further configured to deduct the parking fee from the user's account upon user confirmation.

[0017] According to another aspect of this application, a parking payment method is provided. The parking payment method includes: obtaining parking time information of a parking process, the parking time information including the start time and end time of the parking process; in response to the end time of the parking process, identifying an identifiable marker at or near the parking location; in response to the identification time being greater than a time threshold, generating a copy of the identifiable marker in or near the vehicle; and identifying the copy of the identifiable marker and paying the parking fee based on the copy of the identifiable marker.

[0018] In some embodiments, the parking payment method further includes displaying an identifiable marker or a copy of an identifiable marker on a display in the vehicle to initiate the process of paying the parking fee for the user.

[0019] In some embodiments, the parking payment method further includes a projection device indicating the parking location to project a copy of an identifiable marker near the vehicle and to identify the copy of the identifiable marker in order to pay the parking fee.

[0020] In some embodiments, the information in both the identifiable marker and a copy of the identifiable marker includes parking location price information, and the parking fee is calculated based on parking time information and parking location price information.

[0021] In some embodiments, the parking payment method further includes: reporting fault information of the identifiable marker in response to the identification time being greater than a threshold time.

[0022] It should be understood that the above brief description is provided to introduce, in a simplified form, a range of alternative concepts that will be further described in the detailed description, and does not imply confirmation of key or essential features of the protected subject matter of the invention, the scope of which will be uniquely defined by the claims of the invention. Furthermore, the protected subject matter is not limited to embodiments that overcome any of the disadvantages described above or in any part of this specification. [Attached Image Description]

[0023] One or more features and / or advantages of the present invention will become apparent from one or more embodiments described in detail below, taken in conjunction with the accompanying drawings.

[0024] Figure 1 This is an example block topology diagram of a vehicle's onboard computer system (VCS), and embodiments of this application can be implemented in a VCS system.

[0025] Figure 2 This is a schematic diagram of a parking payment system according to an embodiment of this application.

[0026] Figures 3A-3B For respectively Figure 2 The diagram shows the display of a parking payment system, illustrating different methods for identifying copies of identifiable markers.

[0027] Figure 4 for Figure 2 The diagram shows the connection relationships between the various devices associated with the parking payment system.

[0028] Figure 5 Another schematic diagram of the parking payment system 10 shows its different recognition process.

[0029] Figure 6 This is a flowchart of the parking payment method according to this application.

[0030] Figure 7 This is a schematic diagram of a parking payment system according to another embodiment of this application.

[0031] Figure 8A and 8B Different identifiable markers are shown for parking payment systems according to other embodiments of this application.

[0032] Figure 9 A flowchart of another parking payment method according to this application.

Detailed Implementation Methods

[0033] Specific embodiments of the invention are disclosed herein as needed; however, it should be understood that the embodiments disclosed herein are merely examples of the invention that can be implemented in various alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or reduced to show details of specific components. The same or similar reference numerals may indicate the same parameters and components or similar modifications and substitutions. In the following description, various operating parameters and components are described in several contemplated embodiments. These specific parameters and components are merely examples in this specification and are not intended to be limiting. Therefore, the specific structural and functional details disclosed herein should not be construed as limiting, but are merely representative bases for teaching those skilled in the art to implement the invention in various forms.

[0034] Figure 1 An example block topology diagram of an in-vehicle computer system (VCS) 1 for vehicle 31 is illustrated. An example of such a vehicle-based computer system 1 is the SYNC system manufactured by Ford Motor Company. A vehicle equipped with a vehicle-based computer system may include a visual front-end interface 4 located within the vehicle. Users may also interact with this interface (if present), for example, via a touchscreen. In another illustrative embodiment, interaction is performed via button presses, verbal dialogue, and speech synthesis. Voice interaction in one or more embodiments of this application can be accomplished using the aforementioned in-vehicle computer system (VCS).

[0035] exist Figure 1In the illustrative embodiment 1 shown, processor 3 controls at least a portion of the operation of the in-vehicle computer system. The processor, located in the vehicle, allows for the processing of in-vehicle instructions and programs. Furthermore, the processor is connected to non-persistent memory 5 and persistent memory 7. In this illustrative embodiment, the non-persistent memory is random access memory (RAM) and the persistent memory is a hard disk drive (HDD) or flash memory.

[0036] Processor 3 also provides multiple different inputs, allowing the user to interact with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24, and a Bluetooth input 15 are provided. An input selector 51 is also provided to allow the user to switch between multiple inputs. Inputs to the microphone and auxiliary connector are converted from analog to digital signals by a converter (A / D) 27 before being passed to the processor. Although not shown, multiple vehicle components and auxiliary components communicating with the VCS can use a vehicle network (e.g., but not limited to, a CAN bus) to transmit or receive data to or from the VCS (or its components).

[0037] The system outputs may include, but are not limited to, the visual front-end interface 4 and the speaker 13 or stereo system output. The speaker is connected to the amplifier (AMP) 11 and receives its signal from the processor 3 via the digital-to-analog converter (D / A) 9. It may also output bidirectional data streams as shown at 19 and 21 to a remote Bluetooth device (e.g., PND 54) or a USB device (e.g., a vehicle navigation device 60).

[0038] In one illustrative embodiment, system 1 uses Bluetooth transceiver 15 to communicate 17 with a user's roaming device (ND) 53 (e.g., a cellular phone, smartphone, PDA, etc.). The roaming device can then be used to communicate 59 with a network 61 outside vehicle 31 via, for example, communication 55 with a cellular tower 57. In some embodiments, the cellular tower 57 may be a WiFi access point.

[0039] Signal 14 represents an exemplary communication between the roaming device and the Bluetooth transceiver.

[0040] Pairing of the roaming device 53 and the Bluetooth transceiver (BTT) 15 can be indicated via button 52 or similar input, thus instructing the CPU vehicle Bluetooth transceiver to pair with the Bluetooth transceiver in the roaming device.

[0041] Data can be transferred between CPU 3 and network 61 using, for example, a data-plan associated with roaming device 53, data overvoice, or dual-tone multi-frequency (DTMF) tones. Alternatively, an in-vehicle modem (MDM) 63 with antenna 18 may be required to transfer data between CPU 3 and network 61 via a voice band. Roaming device 53 can then communicate with network 61 outside vehicle 31 via, for example, communication 55 with cellular tower 57. In some embodiments, modem 63 may establish communication 20 with cellular tower for communication with network 61. As a non-limiting example, modem 63 may be a USB cellular modem and communication 20 may be cellular communication.

[0042] In one illustrative embodiment, the processor may be equipped with an operating system including APIs to communicate with modem application software. The modem application software may access embedded modules or firmware on the Bluetooth transceiver to enable wireless communication with remote Bluetooth transceivers (e.g., those found in roaming devices).

[0043] In another embodiment, roaming device 53 includes a modem for voiceband or broadband data communication. In the voiceband data embodiment, when the owner of the roaming device speaks to the device during data transmission, a technique known as frequency division multiplexing can be performed. At other times, when the owner is not using the device, data transmission can utilize the entire bandwidth (300 Hz to 3.4 kHz in one example).

[0044] If the user has a data plan associated with the roaming device, that data plan may allow for broadband transmission and the system can use a wider bandwidth (accelerating data transmission). In another embodiment, the roaming device 53 is replaced by a cellular communication device (not shown) installed in the vehicle 31. In yet another embodiment, the roaming device 53 may be a wireless local area network (LAN) device capable of communicating via, for example (but not limited to), an 802.11 network (e.g., WiFi) or a WiMax network.

[0045] In one embodiment, input data may pass through the roaming device, through the vehicle's Bluetooth transceiver, and into the vehicle's internal processor 3 via audio data or a data schedule. For example, in the case of some temporary data, the data may be stored on an HDD or other storage medium 7 until it is no longer needed.

[0046] Other sources that can interact with the vehicle include a personal navigation device 54 with, for example, a USB connection 56 and / or an antenna 58, or a vehicle navigation device 60 with a USB 62 or other connection, an in-vehicle GPS device 24, or a remote navigation system (not shown) connected to a network 61.

[0047] In addition, the CPU can communicate with multiple other auxiliary devices 65. These devices can be connected via a wireless connection 67 or a wired connection 69. Similarly or alternatively, the CPU can use, for example, a WiFi transceiver 71 to connect to a vehicle-based wireless router 73. This allows the CPU to connect to a remote network within the range of the local router 73. Auxiliary devices 65 may include, but are not limited to, personal media players, wireless health devices, mobile computers, etc.

[0048] The controller may include a microprocessor or central processing unit (CPU) that communicates with various types of computer-readable storage devices or media. Computer-readable storage devices or media may include volatile and non-volatile memory such as read-only memory (ROM), random access memory (RAM), and keep-alive memory (KAM). Computer-readable storage devices or media may be implemented using any number of known storage devices, such as programmable read-only memory (PROM), EPROM (electrically programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), flash memory, or any other electronic, magnetic, optical, or combined storage devices, some of which represent executable instructions used by the controller to control engine 14 or vehicle 10. Additionally, the controller communicates with multiple engine / vehicle sensors and drives via an input / output (I / O) interface, which may be implemented as a single integrated interface providing multiple raw data or signal conditioning, processing and / or conversion, short-circuit protection, etc. Alternatively, specific signals may be conditioning and processed using one or more dedicated hardware or firmware chips before data is provided to the CPU.

[0049] In addition to having an example program executed via a vehicle computer system located within the vehicle, in some embodiments, the example program may be executed via a computer system communicating with the vehicle computer system. Such a system may include, but is not limited to, wireless devices (e.g., but not limited to, mobile phones) or remote computer systems (e.g., but not limited to, servers) connected via wireless devices. Commonly, such a system may refer to a vehicle associated computing system (VACS). In some embodiments, depending on the specific implementation of the system, specific components of the VCS may execute specific parts of the program. By way of example, without limitation, if the program has steps for sending or receiving information with a paired wireless device, then the wireless device may not execute the program because it cannot send and receive information with itself. Those skilled in the art will understand when it is inappropriate to apply a particular VCS to a given solution. In all solutions, it is contemplated that at least the VCS located within the vehicle itself can execute the example program.

[0050] In the illustrative embodiments, the parking payment system and method can be implemented using the VCS described above. Users, such as vehicle drivers, can perform related controls through the VCS and / or a parking server communicating with the VCS during the parking payment process.

[0051] Figure 2 This is a schematic diagram of a parking payment system 10 according to an embodiment of this application. (See reference...) Figure 2 The parking payment system 10 includes a parking payment device 100 and a parking server 20 that communicates with the parking payment device 100 via a network 30. The parking payment device 100 can... Figure 1 The parking payment system 10 communicates with the parking server 20 using the described method or any suitable means. The parking payment system 10 can identify when the vehicle 12 enters and leaves the parking location 200. For example, the parking payment system 10's timer can determine the start and end times of the parking process for the vehicle 12, and then report the parking time (e.g., by subtracting the start time from the end time of the parking process) to the parking server 20. The parking server 20 calculates the parking fee based on the parking time and the price of the parking location 200, and automatically deducts the parking fee from the account associated with the vehicle 12 or the parking payment system 10.

[0052] The parking payment device 100 includes a first reader 110 mounted on the vehicle 12 and a controller 120 communicatively connected thereto. The parking payment system 10 may further include an identifiable tag 210. In some embodiments, the controller 120 is configured to instruct the first reader 110 to read the identifiable tag 210 and have it identified by the controller based on the start and end of the parking process of the vehicle 12, enabling automatic payment of parking fees; if the identification time exceeds a time threshold, it communicates with the parking server 20 to request the generation of a copy 210' of the identifiable tag in or near the vehicle 12. Thus, the first reader 110 can automatically pay parking fees by identifying the copy 210' of the identifiable tag.

[0053] In the illustrated embodiment, the identifiable marker 210 is located on parking location 200. In another embodiment, the identifiable marker 210 may be located near the parking location. The identifiable marker 210 may be a quick-response code, barcode, symbol, digital code, augmented reality pattern, or optical pattern, which may be drawn or affixed to the ground, parking lot, or garage floor or wall in or near parking location 200. The identifiable marker 210 may contain metadata or information related to parking location 200, such as the geographical location, size, price, etc. of parking location 200.

[0054] The first reading device 110 is configured to read identifiable markers 210 located at or near the parking position 200. The first reading device 110 can, as follows: Figure 2The first reading device 110 is located at the rear R of the vehicle to read the identifiable marker 210 when the vehicle is reversed and parked. The vehicle may also include another identifiable marker 210 (not shown) located at the front F of the vehicle to read the identifiable marker 210 when the vehicle is moving forward and parked. It should be understood that, based on the position of the identifiable marker 210 relative to the parking position 200, the first reading device 110 may be located in other locations on the vehicle 10, such as the side (door panel, rearview mirror, pedal) or the bottom.

[0055] In some embodiments, the first reading device 110 may be a scanner, an optical reading device, a magnetic reading device, a radio reading device, or other reading device, configured to read the identifiable tag 210 and transmit the metadata or information contained in the identifiable tag 210. In some embodiments, the optical reading device may include a camera, a charge-coupled device (CCD), or other types of scanners. In some embodiments, the first reading device 110 is capable of identifying the identifiable tag 210 and transmitting the identified information to the controller 120 or the parking server.

[0056] In the illustrated embodiment, controller 120 is integrated into the VCS of vehicle 10, such as in the vehicle's human-machine interface 102. It should be understood that in some embodiments, parking server 20 may process the instructions and programs processed by controller 120. Controller 120 may communicate with parking server 20, sending a start signal to parking server 20 at the start of the parking process and an end signal to parking server 20 at the end of the parking process.

[0057] The start signal includes the start time of the parking process. The controller 120 may send a start signal in response to the vehicle 12 entering the parking position 200, for example, based on the current position of the vehicle 12, vehicle conditions, or a sensor 201 located at the parking position 200 determining whether the vehicle 12 has entered the parking position 200, and thus determining whether to send a parking start signal. In one example, the vehicle 12 includes a positioning device (refer to the block diagram of FIG3) that tracks the vehicle's position, thereby determining whether the vehicle has entered the parking position. In another example, the controller 120 may also determine that the vehicle 12 has entered the parking position based on its first reading device 110 detecting at least a portion of the identifiable marker 210. In yet another example, the controller 120 may also determine that the vehicle 12 has entered the parking position based on vehicle conditions. Vehicle conditions may include the similarity between the vehicle 12's movement trajectory and a conventional parking trajectory exceeding a threshold, or the vehicle 12's power system being deactivated for a predetermined time. Vehicle conditions also include vehicle speed. For example, if the VCS-related speed sensor detects that the vehicle speed has decreased from a typical driving speed (e.g., in the range of 20 mph to 80 mph) to a typical parking speed (e.g., in the range of 1 mph to 10 mph), then the controller 120 determines that the vehicle 12 has entered the parking position based on the vehicle's driving speed and, in conjunction with the vehicle's current position. In one example, sensors 201 for detecting the presence of the vehicle are located near the parking position 200, including weight sensors, inductive sensors, or mechanical switches activated in response to the vehicle stopping. Thus, the controller 120 can determine that the vehicle 12 has entered the parking position 200 and record the parking start time or report information related to the start time of the parking process to the parking server 20.

[0058] The end signal includes the end time of the parking process. The controller 120 may send an end signal in response to the vehicle 12 leaving or about to leave the parking position 200, for example, based on the vehicle's position, vehicle conditions, or sensors located at the parking position to determine whether the vehicle has left the parking position 200, and thus determine whether to send an end signal. For example, the vehicle 12's positioning device indicates that the vehicle 12 has left the parking position 200. Alternatively, the end time of the parking process may be determined based on the vehicle 12's first reading device 110 detecting at least a portion of the identifiable marker 210 again. Alternatively, the end time of the parking process may be determined based on the starting of the vehicle 12's power system. Alternatively, a weight sensor at or near the parking position 200 indicates the loss of weight of the vehicle 12. Based on these conditions, it can be determined that the vehicle 12 has left the parking position, and the controller 120 then sends an end signal to the parking server 20, reporting the end time of the parking process, so that the parking server 20 can calculate the parking time.

[0059] Alternatively, controller 120 is configured to generate a parking time signal at the end of the parking process (i.e., when leaving the parking position), including the time when the vehicle enters the parking position (e.g., the start time of the parking process) and the time when the vehicle leaves the parking position (e.g., the end time of the parking process).

[0060] After the parking process is completed, the parking payment system 10 begins the identification process of the identifiable marker 210. The parking payment device 100 records the time spent identifying the identifiable marker 210, i.e., the identification time. When the identification time exceeds a time threshold, the controller 120 communicates with the parking server 20 via the network 30 to request the generation of a copy of the identifiable marker 210' in or near the vehicle 12. Furthermore, the controller 120 can also send fault information to the parking server 20, indicating that the identifiable marker 210 is damaged or covered. This facilitates timely maintenance by the administrator of the parking payment system 10.

[0061] In some embodiments, the parking payment device 100 begins recording the recognition time with reference to the aforementioned sending of the parking end signal. The time threshold can be set as the average time taken to recognize the identifiable marker 210 in the art. It should be understood that within the time threshold, the general recognition process can be completed successfully. If the time threshold is exceeded, the recognition process is considered unsuccessful by default.

[0062] It should be understood that the copy 210' of the identifiable marker has a substantially identical or different pattern from the identifiable marker 210, and both include the same metadata. That is, once both are successfully identified by the controller 120, they can provide the same parking payment information, including the area of ​​the parking space, parking space availability, parking space payment standard, etc. (Reference) Figure 2 A copy 210' of the identifiable marker can be generated by a projection device 122 located at or near the parking location 200 and displayed at or near the parking location 200. The parking payment system 10 or controller 120 can activate the parking payment process by recognizing the copy 210' of the identifiable marker.

[0063] Alternatively, a copy 210' of the identifiable tag may be sent by the parking server 20 to the vehicle 12, such as a display screen located near the front dashboard of the vehicle 10, or a display 130 on the human-machine interface 102, or on the vehicle's windshield.

[0064] The controller 120 of the parking payment system 10 is configurable to receive start and end signals (or parking time signals), as well as metadata of the identifiable tag 210 or its copy 210', and to calculate and collect parking fees based on the parking time and parking location price. Users of vehicle 12 can register an account with the parking server 20 via the network and link their payment account, such as a debit card, credit card, or other payment instrument. Upon successful identification of the identifiable tag 210 or its copy 210' by the user at the end of the parking process, the parking server 20 automatically deducts the parking fee from the vehicle user's account. In some embodiments, further confirmation from the user is required before the parking server 20 automatically deducts the parking fee from the vehicle user's account.

[0065] Figures 3A-3B A display 130 on vehicle 12 is shown illustrating the process of a user interacting with an identifiable marker or a copy thereof to make a payment. Display 130 may be, for example... Figure 1 The described VCS's visual front-end interface or human-computer interaction device 102's touchscreen can communicate with the parking server 20 to receive a copy 210 of the identifiable marker. The user can identify the copy 210' of the identifiable marker. Thus, when the identifiable marker 210 is unrecognizable due to partial loss, partial coverage, or ambient brightness below a brightness threshold, the parking payment process can be activated by identifying the copy 210' of the identifiable marker. (See reference) Figure 3A The controller 120 of the parking payment device 100 is configured to recognize a copy 210' of the identifiable marker. When the copy 210' is displayed on the display 130, the user can tap or press and hold the copy 210' for a certain period, thereby causing the controller 120 to recognize the copy 210'. After recognizing the copy 210', the controller 120 activates the parking payment process. Activating the parking payment process may include displaying parking payment-related information such as parking start time, parking end time, and parking fee for user confirmation. In some embodiments, the user can pay online after activating the confirmation button on the touchscreen.

[0066] Alternatively, the parking payment system 10 may include a second reading device 40 for reading copies of the identifiable tag. The second reading device 40 may be included in a mobile device carried by the user, such as a smartphone. (See reference) Figure 3BThe user-carried mobile device 40 has a built-in reader 410. When a copy 210' of the identifiable tag is displayed on the display 130, the user can read the identifiable copy 210' and parking payment-related information via the reader 410 of the mobile device 40. The user can scan the identifiable copy 210' with the mobile device 40 to activate the parking payment process and pay online. The mobile device 40 may be a smartphone, mobile phone, personal digital assistant, tablet computer, laptop computer, personal navigation device, portable navigation device, and / or other known or future portable or mobile computing device.

[0067] In some embodiments, the display 130 is communicatively connected to the controller 120 and configured to stop displaying a copy 210' of the identifiable marker in response to the activation of a parking payment process. For example, after identifying the copy 210' of the identifiable marker, the controller 120 may send parking time information to the parking server 20. The parking time information may include the start time, end time, and parking location information of the parking process. When the parking server 20 receives the parking time information sent by the controller 120, it indicates that the parking payment process has been activated. At this time, the controller 120 may instruct the display 130 to stop displaying the copy 210' of the identifiable marker and instead perform other functions, such as displaying a navigation interface or an electronic entertainment system interface. Alternatively, the controller 120 may be configured to stop displaying the copy 210' of the identifiable marker in response to the display time exceeding a display time threshold.

[0068] Figure 4 for Figure 2 A block diagram of the parking payment system 10. Combined with... Figure 2-4 The parking payment system 10 includes a parking payment device 100 and a server 20. The parking payment device 100 includes a first reading device 110 and a controller 120 communicatively connected to each other. The controller 120 includes a processor and a memory unit. In some embodiments, the controller 120 may be integrated into the vehicle's VCS. The controller 120 may execute the parking payment method of this application. For example, in response to the end of the parking process of the vehicle 10, the controller 120 may identify an identifiable marker 210 or a copy 210' of the identifiable marker to activate the parking payment process. The copy 210' of the identifiable marker may be displayed on the vehicle's display, on the vehicle's windshield, in the parking position, or near the parking position. Although... Figure 4 The display controller 120 is located in the vehicle 12. It should be understood that the controller 120 may also be located in the server 20, or the server 20 may include a processor and a memory unit to execute a program or at least a portion of the parking payment method of this application.

[0069] The parking payment device 100 includes a first reading device 110 installed on the vehicle 12 to read identifiable markers near the parking location.

[0070] The parking payment device 100 may also include a second reading device 112. The second reading device 112 is configured to receive and identify an identifiable tag or a copy of an identifiable tag. In some embodiments, the second reading device may be integrated into the vehicle's human-machine interface device 102. In some embodiments, the second reading device may be integrated into a mobile device such as a smartphone.

[0071] The parking payment device 100 may also include a display 130. In some embodiments, the display 130 may be integrated into the vehicle's human-machine interface 102.

[0072] The parking payment device 100 may further include a timer 140 to record the time spent on the identification process, i.e., the identification time. The parking payment device 100 also includes a positioning device 150 communicatively connected to the controller 120. The positioning device 150 may be a navigation device connected to the vehicle's human-machine interface 102. The positioning device 150 enables the current location of the vehicle to be obtained. The controller 120 may determine the start or end of the vehicle parking process based on the vehicle's current location. In some embodiments, the controller 120 determines the start of the parking process by determining whether the vehicle is parked in or near a parking location based on the vehicle's current location and navigation information, and records the start time. The controller 120 may also determine whether the vehicle is about to leave by determining whether it has deviated from the parking location based on the vehicle's current location and navigation information, and records the end time of the parking process.

[0073] From the start of the identification process, timer 140 records the identification time. If the identification time exceeds a time threshold, the identifiable tag 210 is considered unrecognizable by the first reading device 110. This can occur under various conditions, such as partial damage to the identifiable tag 210, partial obscuring, or ambient brightness below a brightness threshold. In this case, controller 120 requests a copy of the identifiable tag 210' from a remote parking server 20, to be displayed on the vehicle 12, at parking position 200, or near parking position 200. Timer 140 may also record the parking start time and parking end time.

[0074] In some embodiments, besides the recognition time exceeding a threshold time, the controller 120 may request the parking server 20 to generate a copy 210' of the identifiable marker in or near the vehicle 12 based on other conditions. The parking payment device 100 also includes an ambient brightness sensor 160 for detecting the ambient brightness around the identifiable marker 210 and comparing it to an ambient brightness threshold. The controller 120 is communicatively connected to the ambient brightness sensor 160 and configured to communicate with the parking server 20 to request a copy 210' of the identifiable marker when the ambient brightness is less than a brightness threshold. In other words, when the ambient brightness is less than the brightness threshold, the probability of successfully recognizing the identifiable marker 210 is low, thus requesting the generation of a copy 210' of the identifiable marker before the threshold time arrives reduces the recognition time.

[0075] Continue to refer to Figure 4 The parking payment system 10 also includes a parking server 20 that is communicatively connected to the parking payment device 100 via a network 30. The parking server 20 includes a processor 22 and a memory unit 24. The processor 22 and memory unit 24 can perform one or more steps of the parking payment method of this application. The memory unit 24 also stores parking-related information. For example, the memory unit 24 may include a parking location 27, a parking fee 28 corresponding to the parking location 27, an identifiable marker 210 corresponding to the parking location 27, and a copy 210' of the identifiable marker. In one embodiment, when the time for determining the parking location of the vehicle and identifying the identifiable marker exceeds a time threshold, the parking server 20 may transmit the corresponding identifiable marker 210 for display on the vehicle's display. In yet another embodiment, when the time for determining the parking location of the vehicle and identifying the identifiable marker exceeds a time threshold, the parking server 20 may instruct a projection device to display a copy 210' of the identifiable marker near the vehicle (e.g., at or near the parking location).

[0076] Figure 5 Another schematic diagram of the parking payment system 10. (Reference) Figure 5 The parking area includes three different parking spaces: parking space 200a, parking space 200b, and parking space 200c. Due to differences in location and size, the fees or prices for these three parking spaces differ, and therefore each is marked with a different identifiable symbol: identifiable symbol 202, identifiable symbol 204, and identifiable symbol 206. For example, parking space 200a is closer to the entrance of the community or the entrance / exit of the parking area, and therefore charges a higher fee. Figure 4 The controller 120 determines the parking location where the vehicle 12 will be parked based on the location information provided by the positioning device 150, and sends a copy of the identifiable marker corresponding to that parking location. (See reference) Figure 5The controller 120 compares the distances of the vehicle 12's current position with various parking locations or identifiable markers, and determines the parking location with the shortest distance as the parking location where the vehicle 12 will park, such as the second parking location 200b. Based on the second parking location 200b, the controller 120 requests a copy 204' of the identifiable marker corresponding to the second identifiable marker 204 and displays it on the vehicle 12's display 130. Subsequently, the user activates the parking payment process by accessing the copy 204' of the identifiable marker.

[0077] Figure 5 The parking server 20, which is connected to the network 30, is also shown. The parking server 20 can store the geographic location information of the parking location, the identifiable marker of the corresponding parking location, and a copy of the identifiable marker. In response to the parking location of the vehicle, the time for identifying the identifiable marker exceeding a time threshold, or a request for the identifiable marker, the parking server 20 sends a copy of the identifiable marker to a display device or human-machine interaction device on the vehicle, or instructs a projector near the parking location to project a copy of the identifiable marker near the parking location.

[0078] Figure 6 The flowchart illustrates a parking payment method 600 according to this application, which can be executed using the aforementioned parking payment device. (See reference...) Figure 6 At point 610, method 600 obtains parking time information for the vehicle parking process. The parking time information may include the start and end times of the vehicle parking process. In some instances, the parking payment device 100 may determine the start and end times using vehicle conditions provided by the vehicle controller or location information provided by the vehicle positioning device.

[0079] At 620, method 600, in response to the end time of the parking process, identifies an identifiable marker at or near the parking location. Identifying an identifiable marker at or near the parking location may include receiving an identifiable marker 210 from a first reading device 110. A controller 120 identifies and analyzes the identifiable marker. The identifiable marker 210 includes price information for the parking location. The first reading device 110 scans or captures the identifiable marker, and the controller 120 identifies and / or analyzes the identifiable marker to obtain its metadata, such as the price information for the parking location. It should be understood that, depending on the type of identifiable marker 210, the first reading device 110 can identify the metadata of the identifiable marker 210.

[0080] At 630, method 600 determines whether the identification time exceeds a time threshold. If it does, at 640, a copy of the identifiable marker is generated at or near the vehicle. The copy of the identifiable marker is similar to or identical to the identifiable marker and includes the same metadata, such as parking location price information, which the controller 120 can obtain by identifying the copy of the identifiable marker. Generating the copy of the identifiable marker includes instructing an associated device to display the copy of the identifiable marker. In some embodiments, the controller 120 may instruct the vehicle's display 130 to display the copy of the identifiable marker. In some embodiments, the controller 120 may instruct a projection device 122 at or near the parking location to project the copy of the identifiable marker onto the ground at or near the parking location.

[0081] Next, at 650, a copy of the identifiable marker is identified. In some embodiments, the controller 120 may be integrated into the second reading device 112 in the human-machine interface 102 to identify the copy of the identifiable marker to obtain parking location price information. Thus, the controller 120 can calculate the parking fee based on parking time information (e.g., obtained by subtracting the start time from the end time of the parking process) and the parking location price information, and display it on the vehicle's display or the user's mobile device. In some embodiments, the controller 120 identifies a copy 210' of the identifiable marker projected onto or near the parking location to obtain parking location price information.

[0082] Next, at point 660, method 600 pays the parking fee. For example, payment can be made automatically after identification based on a copy of the identifiable tag; that is, the parking fee is automatically deducted from the vehicle's account once the copy of the identifiable tag is successfully identified. In some embodiments, the controller 120 can be connected to the user's account. After the parking fee is determined, the controller 120 can connect to the user's account and automatically deduct the fee. For example, when the controller receives a copy of the identifiable tag from the first reading device and determines the parking fee, it can connect to the user's account to make payment. In some embodiments, payment can also be made only after user confirmation. When the copy of the identifiable tag is displayed on the vehicle's screen, the time and fee of the parking process are also displayed. After further user input (e.g., clicking a payment link or voice confirmation) to confirm, the payment is completed.

[0083] In method 670, method 600 may further include reporting fault information about identifiable markings. For example, fault information may include that the identifiable markings are partially missing or covered. This allows the parking fee collection management to obtain this information promptly and take immediate maintenance measures.

[0084] If at point 630, the recognition time is within the threshold time range, meaning the reading device successfully recognizes the identifiable tag, then the process proceeds to point 660 to pay the parking fee.

[0085] Figure 7 This is a schematic diagram of a parking payment system 70 according to another embodiment of this application. (See reference) Figure 7 The parking payment system 70 includes an identifiable marker 710 located at or near parking location 71, a controller 72, and a reader 730. The controller 72 is configured to read the identifiable marker 710 in response to the end of the parking process of vehicle 12. The parking payment system 70 also includes a remote parking server 74, which is communicatively connected to the controller 72 via a network 75. The parking server 74 is configured to generate a copy 710' of the identifiable marker in or near vehicle 12 in response to an identification time exceeding a time threshold.

[0086] although Figure 7 The diagram shows that controller 72 is located in vehicle 10, for example, integrated into the VCS of vehicle 10. It should be understood that controller 72 may also be located in parking server 74.

[0087] although Figure 7 The image shows the identifiable marker 710 located at parking position 71, for example, in the middle of the rear end of parking position 71, to facilitate identification by the rear-facing camera (i.e., reversing camera) of vehicle 73 as a reading device 73. It should be understood that the identifiable marker 710 can also be located in the middle of the front end of parking position 71 to facilitate identification by the front-facing camera of vehicle 10 as a reading device 73a. Alternatively, the identifiable marker 710 can be located in other positions, such as in the middle, on either side of parking position 71, or anywhere outside parking position 71 adjacent to it (not shown). In such embodiments, vehicle 73 may include other corresponding reading devices for identifying the identifiable marker 710, such as reading devices 73b located on either side of vehicle 73 and reading devices 73c located at the bottom of vehicle 73.

[0088] Similarly, the location of the generated copy 710' of the identifiable tag is not limited to... Figure 7 The embodiment shown is located in the middle position outside the rear of the parking position 71. Any position applicable to the above-mentioned identifiable mark 710 is applicable to the copy 710' of the identifiable mark.

[0089] Continue to refer to Figure 7The parking payment system 70 includes a projection device 76 communicatively connected to a parking server 74, for generating a copy 710' of an identifiable marker at or near the parking location 71. The projection device 76 may be located adjacent to the parking location 71, for example, behind the parking location 71. It should be understood that the projection device 76 may also be located in other locations that do not affect the user's parking, such as the side exterior of the parking location 71 (not shown). In response to an identification time exceeding a time threshold, based on a request from the controller 72, the projection device 76 displays a copy 710' of the identifiable marker at or near the parking location 71. Thus, when the identifiable marker 710 is damaged or obscured and cannot be identified, the projection device 76 provides an additional copy 710' of the identifiable marker, allowing the user to continue activating the parking payment process.

[0090] Continue to refer to Figure 7 The projection device 76 may be mounted on a support 760 adjacent to the parking position 71. The support 760 may have a considerable height, and the projection device 76 may be positioned appropriately on the support 760 to project a copy 710' of the corresponding identifiable mark. The support 760 may be provided with multiple projection devices 76 or may project different patterns in response to different instructions to provide copies of the identifiable mark for multiple parking positions.

[0091] like Figure 7 As shown, the parking area also includes a first parking position 77 and a second parking position 78 adjacent to parking position 71, with parking position 71 located between the two. The first parking position 77 and the second parking position 78, or their vicinity, are provided with corresponding first identifiable markers 770 and 780. When the controller 72 determines, based on the vehicle 73's positioning device, that the vehicle 73 is approaching parking position 71 (e.g., the positioning device shows that the vehicle 10 is closest to parking position 71), it communicates with the parking server 74 to transmit the location information of parking position 71 and requests a copy 710' of the first identifiable marker 710 corresponding to parking position 71. The projection device 76 correspondingly projects the copy 710' of the identifiable marker 710 onto the first parking position 77 or its vicinity for recognition by the vehicle 10's reading device 73a.

[0092] In some embodiments, reference Figure 7The projection device 76 also includes a manual switch 764 and a display 766 mounted on a support 760. The manual switch 764 is used to activate the projection device 76 to display a copy 710' of the identifiable marker. In the event of a communication failure between the projection device 76 and the parking server 74, the user can exit the vehicle and operate the manual switch 764 to activate the projection device 76. The display 766 may include an input module and a display module. The input module is used to receive user instructions (e.g., selecting which parking location's identifiable marker copy to project), and the display module is used to output parking location information (e.g., pricing, availability). In some embodiments, the user can also activate and complete the parking payment process through the display 766.

[0093] In some embodiments, the parking payment system 70 may also include an ambient light sensor (not shown, but may be referenced). Figure 4 (Example from [example]). The controller 72 is further configured to: in response to the ambient brightness around the identifiable marker 710 being less than a brightness threshold, request the parking server 74 to generate a copy 710' of the identifiable marker. Due to the low brightness, the reading device 730 is more likely to fail to recognize it. The controller 72 sends the result that the ambient brightness around the identifiable marker 710 is less than the brightness threshold to the parking server 74, and the parking server 74 instructs the projection device 76 to display the copy 710' of the identifiable marker near the parking location 71. In this way, the copy 710' of the identifiable marker is generated proactively without waiting for the recognition threshold time to be reached, thus saving the total time of the parking payment process.

[0094] In some embodiments, the controller 72 or parking server 75 calculates the parking fee based on the fee information and parking time of the parking location 71 contained in the identifiable marker 710 or a copy of the identifiable marker 710', and automatically deducts the calculated parking fee from the user account associated with the vehicle 73. Alternatively, the parking payment process can be completed by re-identifying the identifiable marker 710 or a copy of the identifiable marker 710'. That is, after the vehicle 73's power system is restarted, the reading device 730 re-identifies the identifiable marker 710 (or communicates with the parking server 74 to request a copy of the identifiable marker 710' displayed by the projection device 76), thereby activating the payment process.

[0095] According to this application, the identifiable mark can be a drawing on the ground, such as... Figure 2 , 3A As shown in embodiments -3B, 5, and 7; it can also be a projected pattern displayed by a projection device, such as Figure 7 As shown. Alternatively, the identifiable marker can also be a luminous pattern. Figure 8A and 8B Different identifiable markers are shown for parking payment systems according to other embodiments of this application.

[0096] refer to Figure 8A The parking position 81 includes a weight sensor 810 and a piezoelectric light-emitting device 812 connected to the weight sensor 810. In response to a signal from the weight sensor 810 indicating that the weight exceeds a weight threshold, the piezoelectric light-emitting device 812 displays a pattern of illuminated identifiable markings 814 on the surface of the parking position 81. The weight threshold corresponds to the weight of the vehicle 82. When no weight of the vehicle 82 is detected (e.g., when the weight is below the weight threshold), the piezoelectric light-emitting device 812 is deactivated, and the parking position 81 is provided with the illuminated pattern representing the identifiable markings 814. When the weight sensor 810 detects the vehicle 82, the piezoelectric light-emitting device 812 is activated, and the pattern of illuminated identifiable markings 814 is displayed in the parking position 81.

[0097] refer to Figure 8B The parking position 83 includes a brightness sensor 830 and a photoelectric light-emitting device 832 connected to the brightness sensor 830. In response to a signal from the brightness sensor 830 indicating that the brightness exceeds a brightness threshold, the photoelectric light-emitting device 832 displays a pattern of an illuminated identifiable mark 834 on the surface of the parking position 83. The brightness threshold corresponds to the brightness provided by the lighting device 840 of the vehicle 84. When no vehicle 84 is detected (e.g., when the brightness is below the brightness threshold), the photoelectric light-emitting device 832 is deactivated, and the parking position 83 does not display the illuminated pattern representing the identifiable mark 834. When the brightness sensor 830 detects a vehicle 84, the photoelectric light-emitting device 832 is activated, and the pattern of the illuminated identifiable mark 834 is displayed in the parking position 83.

[0098] Figure 9 The flowchart illustrates another parking payment method 900 according to this application, which can be executed via the aforementioned parking payment server 20. (See reference...) Figure 9 At 910, method 900 includes receiving information about the parking start time. In some embodiments, the timer of the vehicle payment device 100 may determine that the vehicle has entered the parking position based on the vehicle's current location and begin recording the parking start time, which is then transmitted to the server 20 via the controller 120. At 920, method 900 includes receiving information about the parking end time. The controller 120 may determine whether the vehicle has left the parking position based on the vehicle's location and vehicle conditions, and then record the parking end time, which is then transmitted to the server 20 via the controller 120.

[0099] At 930, in response to the end of the parking process, a time is received to identify the parking location or a nearby identifiable marker. In some embodiments, the vehicle's payment device 100 can identify the parking location or a nearby identifiable marker. The identifiable marker may be a quick-response code, barcode, symbol, digital code, augmented reality pattern, or optical pattern, which may be drawn or affixed to the ground, parking lot, or garage floor or wall in or near the parking location. The identifiable marker may contain metadata or information related to the parking location, such as the parking location's geographic location, size, and price information. The identifiable marker may be read by a reading device on the vehicle, such as the first reading device described above, and transmitted to the vehicle's controller for identification. The vehicle's payment device 100 records the identification time and transmits the identification time to the parking server.

[0100] At 940, it is determined whether the recognition time exceeds a time threshold. If it does, at 950, method 900 includes instructing the generation of a copy of the identifiable marker on or near the vehicle. In some cases, the recognition time is too long, and the controller on the vehicle cannot obtain the price information for the parking location (i.e., recognition failure or recognition malfunction), preventing the parking server 20 from completing the charging process. When it is determined that the recognition time exceeds the time threshold, the parking server 20 may instruct the generation of a copy of the identifiable marker. Alternatively, the parking server 20 may generate a copy of the identifiable marker in response to a request from the controller 120 requesting a copy of the identifiable marker. Generating a copy of the identifiable marker includes instructing an associated device to display a copy of the identifiable marker. In some embodiments, the controller 120 may instruct the vehicle's display 130 to display a copy of the identifiable marker. In some embodiments, the controller 120 may instruct a projection device 122 at or near the parking location to project a copy of the identifiable marker onto the ground at or near the parking location. The parking server may determine the parking location where the vehicle is to be parked based on the vehicle's location and then transmit a copy of the identifiable marker corresponding to that parking location. A copy of the identifiable marker is similar to or identical to the identifiable marker and also includes parking location pricing information. The reading device can obtain the parking location pricing information by identifying the copy of the identifiable marker. The copy of the identifiable marker can be displayed on the vehicle's display or projected onto the ground near the vehicle via a projection device at or near the parking location.

[0101] Next, at 960, method 900 includes determining the parking fee. A remote parking server can calculate the parking fee based on parking time information (e.g., obtained by subtracting the start time from the end time of the parking process) and price information of the parking location contained in the identifiable marker. It should be understood that determining the parking fee can also be performed on the controller of the parking payment device 100, and therefore, step 960 can be omitted.

[0102] At 970, method 900 receives payment from the user. For example, parking server 20 deducts parking fees from the account corresponding to the vehicle after the vehicle controller 120 identifies a copy of the identifiable tag. In another embodiment, parking server 20 deducts parking fees from the account corresponding to the vehicle after the vehicle controller 120 identifies a copy of the identifiable tag and the user confirms the deduction.

[0103] If, at step 940, the recognition time is within the threshold time range (i.e., the reading device successfully recognizes the identifiable marker), then method 900 proceeds to step 960, where method 900 determines the parking fee based on the identifiable marker. At step 970, method 900 receives payment from the user.

[0104] According to the parking payment device, parking payment system, and parking payment method of this application, the corresponding control can be initiated proactively based on environmental conditions (e.g., ambient brightness, current state of identifiable markers) and vehicle conditions (e.g., start or end of the vehicle parking process), including generating copies of identifiable markers inside the vehicle and at or near the parking location, which can improve the success rate of identification and thus partially optimize the parking payment process.

[0105] It should be noted that the methods of this application can be executed by program instructions stored on a computer-readable medium in a mobile communication device. The exemplary control and estimation programs included herein can be applied with various vehicle system architectures. The specific programs described herein can represent one or more of any number of processing strategies, such as event-driven, interrupt-driven, multitasking, multithreaded, etc. Therefore, the various actions, operations, or functions shown can be performed in the order shown, in parallel, or in some cases can be omitted. Similarly, the order of processing is not required to achieve the features and advantages of the exemplary embodiments described herein, but is provided for ease of illustration and description. One or more of the actions or functions shown can be repeated according to the specific strategy used. Moreover, the actions can be illustrated as code programmed into a computer-readable storage medium in a vehicle control system.

[0106] It should be understood that the structures and procedures disclosed in this application are exemplary, and the specific embodiments should not be construed as limiting, as various modifications may exist. The above descriptions are merely preferred embodiments of the present invention and are not intended to limit the invention. For those skilled in the art, the present invention can have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A parking payment device arranged on a vehicle, comprising: a first reading device configured to read an identifiable marker arranged at or near a parking location; and a controller configured to: identify the identifiable marker in response to an end of a parking process of the vehicle; and request, in response to an identification time exceeding a time threshold, a generation of a copy of the identifiable marker in or near the vehicle to pay a parking fee based on the copy of the identifiable marker from a parking server.

2. The device of claim 1, wherein the parking server determines a corresponding copy of the identifiable marker according to a location of the vehicle and the parking location.

3. The device of claim 1, further comprising a display arranged in the vehicle, wherein the copy of the identifiable marker is displayed on the display; the display comprises a second reading device for reading the copy of the identifiable marker to activate a parking payment process.

4. The device of claim 1, further comprising a display arranged on the vehicle, wherein the copy of the identifiable marker is displayed on the display for a user to read and identify using a second reading device.

5. The apparatus of claim 1, wherein, The copy of the identifiable marker is displayed at or near the parking location.

6. The device of claim 1, wherein the controller is further configured to stop the display of the copy of the identifiable marker in response to a payment of the parking fee.

7. The device of claim 1, wherein the controller is further configured to stop the display of the copy of the identifiable marker in response to a display time of the copy of the identifiable marker exceeding a display time threshold.

8. The device of claim 1, wherein the controller is further configured to request the generation of the copy of the identifiable marker from the parking server in response to an ambient brightness being less than a brightness threshold.

9. The device of claim 1, wherein the controller is further configured to report a failure information of the identifiable marker to the parking server in response to the identification time exceeding a threshold time.

10. A parking payment system for a vehicle, comprising: a memory unit comprising information of parking locations, identifiable markers corresponding to the parking locations, copies of the identifiable markers, and parking fees; a controller configured to: receive parking location information of a vehicle and an end information of a parking process of the vehicle, pay a parking fee based on an identifiable marker corresponding to the parking location; and in response to an identification time being greater than a time threshold, instruct a display of a copy of the identifiable marker in or near the vehicle, and pay the parking fee based on the copy of the identifiable marker.

11. The system of claim 10, wherein the controller is located in a parking server.

12. The system of claim 10, wherein the copy of the identifiable marker is displayed on a display.

13. The system of claim 10, further comprising a projection device arranged at or near a parking location and in communication with a parking server, the projection device configured to generate a copy of the identifiable marker in or near the vehicle in response to an instruction from the parking server.

14. The system of claim 13, wherein the projection device comprises a manual switch.

15. The system of claim 11, wherein the identifiable marker and the copy of the identifiable marker each contain price information of the parking location; and the parking server is further configured to calculate the parking fee based on the start time and the end time of the parking process and the price information contained in the identifiable marker.

16. The system of claim 15, wherein the parking server is further configured to deduct the parking fee from the user's account after the user's confirmation.

17. A method for paying a parking fee, comprising: obtaining parking time information of a parking process, the parking time information comprising a start time and an end time of the parking process; in response to the end time of the parking process, identifying an identifiable marker of a parking location or in the vicinity of the parking location; in response to an identification time being greater than a time threshold, generating a copy of the identifiable marker in the vehicle or in the vicinity of the vehicle; and identifying the copy of the identifiable marker and paying a parking fee based on the copy of the identifiable marker.

18. The method of claim 17, further comprising displaying the identifiable marker or the copy of the identifiable marker on a display in the vehicle to enable a user to initiate a process of paying the parking fee.

19. The method of claim 17, further comprising projecting, by a projection device indicated in the vicinity of the parking location, the copy of the identifiable marker in the vicinity of the vehicle and identifying the copy of the identifiable marker to pay the parking fee.

20. The method of claim 17, wherein information of the identifiable marker and the copy of the identifiable marker each contain price information of the parking location, and the parking fee is calculated based on the parking time information and the price information of the parking location.

21. The parking payment method of claim 17, further comprising: in response to the identification time being greater than the threshold time, reporting failure information of the identifiable marker.

Images