Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/327—Short range or proximity payments by means of M-devices
  • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
• • 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
• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07F—COIN-FREED OR LIKE APPARATUS
  • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
  • G07F17/24—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for parking meters

Definitions

• a parking lot (e.g., a parkade) is an area where motor vehicles may be parked.
• a parking lot may be fee-based such that a motor vehicle may be permitted to park in the lot in exchange for payment of a fee.
• this fee is based on a time period in which the vehicle is parked in the lot.
• a driver of the vehicle may receive a time-stamped ticket from an entry terminal. Before the driver leaves the lot with the vehicle, the driver may be required to insert the ticket into a payment terminal, which may determine a fee (e.g., based on the amount of time that has passed since the driver received the ticket). The driver may then pay the fee, either by providing cash or a payment instrument such as a credit card or debit card into the payment terminal. The payment terminal may then validate the ticket and return it to the driver. To exit the parking lot, the driver may drive up to an exit terminal and insert the validated ticket into the exit terminal.
• a fee e.g., based on the amount of time that has passed since the driver received the ticket.
• the driver may then pay the fee, either by providing cash or a payment instrument such as a credit card or debit card into the payment terminal.
• the payment terminal may then validate the ticket and return it to the driver.
• the driver may drive up to an exit terminal and insert the validated ticket into the exit terminal.
• the exit terminal may confirm that the ticket has been validated, and in response, the exit terminal may cause a boom to rise so as to allow the driver's vehicle to exit the parking lot.
• This process of paying a fee for a parking lot can be inconvenient and can present safety and health concerns.
• the payment terminal may be located at or near a pedestrian entrance to the parking lot. In such arrangements, queues at the payment terminal may be lengthy, particularly at peak times, thus causing delay and leading to driver impatience and frustration. Furthermore, the payment terminal may be out of service or may have insufficient cash to provide correct change, thereby further exacerbating these problems.
• the need for the driver to handle cash or payment instruments in a public environment may cause safety concerns.
• a payment terminal may be integrated with the exit terminal, which may allow a driver to pay the fee while sitting in the vehicle just before exiting the parking lot.
• a payment terminal may be integrated with the exit terminal, which may allow a driver to pay the fee while sitting in the vehicle just before exiting the parking lot.
• the lengthy queues of vehicles can cause high levels of emissions in a relatively small area, which may be undesirable for health reasons.
• an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
• an example embodiment takes the form of a mobile device.
• the mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) transmitting authorization to pay the received fee.
• an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
• an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a server.
• the server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
• an example embodiment takes the form of a mobile device.
• the mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) transmitting authorization to pay the received fee.
• an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
• an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a server.
• the server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
• an example embodiment takes the form of a method comprising (i) scanning, using a mobile device, a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (ii) decoding, using the mobile device, the QR code to recover the unique ticket code; (iii) transmitting from the mobile device to an application server the unique ticket code; (iv) receiving, at the mobile device, a parking fee for using the parkade, and displaying, on the mobile device, the parking fee; (v) selecting, using the mobile device, a payment instrument for paying the parking fee, and authorizing the parking fee for payment; (vi) transmitting from the mobile device to the application server data pertaining to the payment instrument; and (vii) receiving, at the mobile device from an application server, status data indicating whether the parking fee was successfully or unsuccessfully paid.
• QR quick response
• an example embodiment takes the form of a mobile device comprising: (i) a processor; (ii) a camera configured to capture a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (iii) a non-transitory computer-readable data storage device comprising computer-readable program instructions, wherein the program instructions are executable by the processor to decode the QR code; (iv) a user interface configured to display a parking fee for using the parkade and to allow a user to select a payment instrument for an attempt at paying the parking fee and to authorize a parking fee for payment; and (v) a network interface; (vi) wherein the network interface is configured to transmit, to an application server, the unique ticket code and data pertaining to the payment instrument; and (vii) wherein the network interface is configured to receive, from an application server, status data indicating whether the initial attempt at paying the fee was successful or unsuccessful.
• QR quick response
• an example embodiment takes the form of a method comprising: (i) receiving, at an application server from a mobile device, a unique ticket code that identifies a parking ticket for using a parkade; (ii) determining, at the application server, a parking fee for using the parkade; (iii) transmitting, from the application server to the mobile device, the parking fee; (iv) receiving, at the application server from the mobile device, data pertaining to a payment instrument selected for an attempt at paying the fee; (v) determining, at the application server, whether processing the data pertaining to the parking fee and the data pertaining to the first payment instrument results in successful or unsuccessful payment of the parking fee; and (vi) transmitting, from the application server to the mobile device, status data indicating whether the attempt at paying the parking fee was successful or unsuccessful.
• an example embodiment takes the form of an application server system comprising: (i) a processor; (ii) a non-transitory computer-readable data storage device comprising computer-readable program instructions; and (iii) a network interface; (iv) wherein the network interface is configured to receive, from a mobile device, (1) a unique ticket code that identifies a parking ticket for using a parkade, and, (2) data pertaining to a payment instrument selected for an attempt at paying a parking fee for using the parkade; and (iv) wherein the program instructions are executable by the processor to determine whether processing the parking fee and the data pertaining to the payment instrument results in successful or unsuccessful payment of the parking fee; (v) wherein the program instructions are executable by the processor to cause the network interface to transmit status data to the mobile device; and (vi) wherein the status data indicates whether the attempt at paying the parking fee was successful or unsuccessful.
• an example embodiment takes the form of a method comprising: (i) providing, at a parkade, a parking ticket for using the parkade; and (ii) providing, at the parkade, a quick response (QR) code that encodes a unique ticket number that identifies the parking ticket.
• QR quick response
• FIG. 1 is a schematic representation of a system for paying a fee in accordance with an example embodiment
• FIG. 2 illustrates an example quick response (QR) code
• FIG. 3 is a block diagram of a mobile device in accordance with an example embodiment
• FIG. 4 is a block diagram of an application server in accordance with an example embodiment
• FIG. 5A is a first part of a flow chart of functions of a method in accordance with an example embodiment
• FIG. 5B is a second part of the flow chart of FIG. 5A;
• FIG. 5C is a third part of the flow chart of FIG. 5A.
• FIG. 6 illustrates a display of a mobile device in accordance with an example embodiment DETAILED DESCRIPTION
• FIG. 1 is a schematic representation of a system 100 for paying a fee in accordance with an example embodiment.
• the system 100 is described in connection with a parking lot. However, as described further below, the system 100 may be used in connection with other environments as well.
• the system 100 includes an application server 102, an entry or dispenser terminal 104, a mobile device 106, an exit terminal 108, a payment processing server 1 10, and a parking record database 112.
• the dispenser terminal 104 may be configured to dispense a medium to a user, such as a driver of a vehicle. In some instances, in response to a vehicle entering the parking lot, the dispenser terminal 104 may dispense the medium.
• the medium may take a variety of forms. For example, the medium may take the form of a paper ticket or a token.
• the medium may have disposed thereon a code that encodes a session identifier.
• the code may take a variety of forms.
• the code may take the form of a one-dimensional code such as a linear barcode, or a two-dimensional code such as a QR code.
• the session identifier may uniquely identify a particular parking session, that is, a given instance of a vehicle parking in the parking lot.
• the session identifier can take a variety of forms.
• the session identifier may be a numeric or an alphanumeric code.
• the code can also encode other data, including for example a time or a parking lot identifier.
• the dispenser terminal 104 may be configured to print the code on the medium (or otherwise cause the code to be disposed on the medium) proximate (i.e., at or about) the time that the medium is dispensed.
• an event is proximate a time if the event and the time are within a threshold number of seconds of each other.
• the threshold may be, for example, five seconds, ten seconds, or twenty seconds.
• the medium may already have a code disposed thereon when it is loaded into the dispenser terminal 104.
• the dispenser terminal 104 may be operatively connected to the application server 102, and may further be configured to transmit to the application server 102 the session identifier encoded in the code and/or a time that generally indicating a time the vehicle entered the parking lot.
• time refers to a time and/or date.
• the application server 102 may be configured to store the received session identifier and the time in a parking record database 112 as described in greater detail below.
• the exit device 108 may be configured to regulate the exiting of vehicles out of the parking lot and may include or be integrated with an access control device, which may take a variety of forms.
• the access control device may take the form of a boom mechanism that is configured to move between a low position, thereby obstructing vehicles from exiting the lot, and a high position, thereby permitting vehicles to exit the lot.
• the exit device 108 may raise and lower the boom.
• control access device may be used to regulate the entry of vehicles into the lot and the exiting of vehicles out of the lot.
• separate control access devices may be used for each purpose.
• the exit terminal 108 may be operatively connected to the application server 102.
• the application server 102, the mobile device 106 and the payment processing server 1 10 can communicate with each other by means of a communication network 1 16.
• the communication network 1 16 can take a variety of forms.
• the communication network 1 16 may take the form of a local-area network or a wide-area network, such as the world-wide web or the Internet.
• the communication network 1 16 may be supported by wired or wireless interfaces (e.g., interfaces configured to communicate using a Wi-Fi or Bluetooth protocol, for instance).
• other devices in the system 100 may also communicate with each other via a communication network. Communication between any such devices may be facilitated by corresponding network interfaces.
• Communication between the application server 102, the mobile device 106 and the payment processing server 110 can be facilitated by using a server-hosted program that is installed on the application server 102, a payment application program (a "payment app”) that is installed and executed on the mobile device 106, and a processing application program (a "processing app”) that is installed and executed on the payment processing server 110.
• a server-hosted program that is installed on the application server 102
• a payment application program (a "payment app") that is installed and executed on the mobile device 106
• processing application program a "processing app”
• a user can download a copy of the payment app from a download repository, for example, from a data storage device 188 of the application server 102 (FIG. 4) and install the payment app on the mobile device 106.
• the payment app may create a user profile 1 14 on the mobile device 106 and prompt the user to manually provide certain attributes such as, the user's first name, the user's last name, an e-mail address, a physical address and particulars of one or more payment instruments such as credit cards, debit cards, e-wallets and the like.
• the user profile 1 14 may be stored locally on the mobile device 106 and not passed to the application server 102.
• the payment app may facilitate the performance of a variety of functions, including but not limited to the functions of capturing a code that encodes a session identifier, decoding the captured code to recover the session identifier, transmitting to a server the recovered session identifier, receiving from the server a fee associated with the recovered session identifier, and providing to the server authorization to pay the fee.
• FIG. 2 illustrates an example QR code 200.
• a QR code is a two-dimensional code.
• the example embodiments may use any of a variety of two-dimensional codes, such as an Aztec barcode, a codablock F code, a code16K barcode, a code49 barcode, a data-matrix barcode, a micro PDF417 barcode, a QR code, a micro QR code or some other two-dimensional code.
• the example embodiments may use a one-dimensional code, such as a barcode in which only a width of each bar is used to decode the barcode..
• FIG. 3 is a block diagram depicting an example embodiment of mobile device
• the mobile device 106 includes (i) a processor 150, (ii) a network interface 152 for transmitting data to and receiving data from communication network 116, (iii) a user interface 154, (iv) a camera (or other capture device) 156 configured to capture a code such as a QR code, and (v) a data storage device 158, all of which can be linked together via a system bus or other connection mechanism 160.
• Data storage device 158 includes computer-readable program instructions (CRPI) 162, the payment app 164, and a user profile 114. CRPI 162 can include the payment app 164.
• Data storage device 158 can comprise a non-transitory computer-readable storage medium readable by processor 150. Each computer-readable storage medium described herein can comprise volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with a processor.
• Each processor described herein can comprise one or more general purpose processors (for example, INTEL single core microprocessors or INTEL multicore microprocessors) or one or more special purpose processors (for example, digital signal processors).
• Processor 150 is configured to execute CRPI 162 and the payment app 164.
• Mobile device 106 can be configured as or comprise a cellular phone, a smartphone, a tablet device, or some other device arranged to carry out cellular communications.
• communication network 116 can comprise a cellular communication network, such as a network for carrying out communications according to the 4G Long Term Evolution (LTE) standard developed by the 3 rd Generation Partnership Project (3GPP), or some other communication standard developed for a cellular communication network.
• LTE Long Term Evolution
• 3GPP 3 rd Generation Partnership Project
• FIG. 4 is a block diagram depicting an example embodiment of the application server 102.
• application server 102 can include (i) a processor 182, (ii) a network interface 184 for transmitting data to and receiving data from communication network 1 16, (iii) a user interface 186, and (iv) a data storage device 188, all of which can be linked together via a system bus or other connection mechanism 190.
• Data storage device 188 can include (i) CRPI 192, and (ii) the payment app 194 (which may be the same as the payment app 164) to be downloaded by the mobile device 106.
• CRPI 192 can include the payment app 194.
• Data storage device 188 can comprise a non-transitory computer-readable storage medium readable by processor 182.
• Processor 182 is configured to execute CRPI 192. III. EXAMPLE OPERATION
• the system 100 can be used to pay a fee.
• the following example describes an example use of the system 100 in connection with a user who wishes to pay a parking lot fee.
• the system 100 may be used in connection with users who wish to pay other types of fees as well.
• FIGS. 5A-5C shows a flow chart depicting a set of functions of a method in accordance with an example embodiment.
• the set of functions are shown within blocks 502 through 548. A description of those blocks now follows.
• the method may involve the dispenser terminal 104 dispensing a medium having a code disposed thereon, wherein the code encodes a session identifier.
• the method may involve the mobile device 106 capturing the code disposed on the medium. This may involve the mobile device 106 using the camera 156 and the payment app 164 to capture the code.
• the method may involve the mobile device 106 decoding the captured code to recover the session identifier. This may involve the mobile device 106 using the payment app 164 to decode the captured code and to recover the session identifier.
• the mobile device 106 may determine that the captured code has a particular property, and in responsive the mobile device 106 may automatically launch an application, such as the payment app 164.
• the captured code having the particular property may involve the capture code having a particular set of data (e.g., the string "launch_payment_app" encoded therein.
• the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 the recovered session identifier.
• the method may involve the application server 102 receiving from the mobile device 106 via the communication network 116 the transmitted session identifier.
• the method may involve the application server 102 determining a fee associated with the received session identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time.
• the first time is proximate a time when the vehicle enters the parking lot.
• the application server 102 may determine the first time in a variety of ways. For example, the dispenser terminal 104 may determine the first time to be a time when the dispenser terminal 104 dispenses the medium. The dispenser terminal 104 may then transmit the first time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the first time to be a time when the application server 102 receives the session identifier from the dispenser terminal 104. In either of the two examples described above, the application server 102 may store in the parking record database 112 the received session identifier together with the received first time. Therefore, the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding first time from the parking record database 1 12.
• the second time is proximate a time when the driver is in the process of paying the fee and/or exiting the parking lot.
• the application server 102 may determine the second time in a variety of ways. For example, the mobile device 106 may determine the second time to be a time when the mobile device 106 (i) captures the code, (ii) decodes the captured code to recover the session identifier, or (iii) transmits to the application server 102 the recovered session identifier. The mobile device 106 may then transmit the second time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the second time to be a time when the application server 102 receives the session identifier from the mobile device 106.
• the application server 102 may store in the parking record database 112 the received session identifier together with the received second time.
• the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding second time from the parking record database 1 12.
• the fee may be a function of at least the time period.
• the application server 102 may use a look-up table (e.g., that is stored in a data storage of the application server 102) to determine the fee based on the time period.
• the data in the look-up table may be set via a user interface by, e.g., a manager of the parking lot.
• the fee may further be a function of other factors, including but not limited to a location of the parking lot, a time of day, week, month, or year in which the time period falls within, and the user profile.
• the dispenser terminal 104, the mobile device 106, and/or another device may provide such data to the application server 102 so that the application server 102 can determine the fee by using such factors.
• the method may involve the application server 102 transmitting to the mobile device 106 via the communication network 1 16 the determined fee.
• the method may involve the mobile device 106 receiving the transmitted fee.
• the method may involve the mobile device 106 displaying the received fee.
• FIG. 6 shows an example screenshot 600 of a display of the mobile device 106 at block 518.
• the mobile device 106 may further display the first time and the second time. This allows the user to review details relating to a parking session before authorizing payment of the fee for the parking session.
• the user may provide such authorization via the user interface 154 of the mobile device 106.
• the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 authorization to pay the received fee.
• the mobile device 106 may further transmit payment data to the application server 102.
• Payment data may include at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a PIN, and a mailing code associated with the cardholder, among other things.
• the user may provide such payment data to the mobile device 106 via the user interface 154.
• the mobile device 106 may transmit to the application server 102 a user profile identifier, which the application server 102 may use to retrieve payment data associated with the user (e.g., stored in the user profile 1 14).
• the application server 102 may transmit to the mobile device at least a portion of the retrieved payment data such that the mobile device 106 may display payment data options to the user. This may allow the user to select payment data (e.g., a particular payment instrument) from among the payment data options being displayed. In turn, the mobile device 106 may select such payment data and transmit the selection to the application server 102.
• payment data e.g., a particular payment instrument
• the method may involve responsive to the application server 102 receiving authorization to pay the determined fee, the application server 102 transmitting the particulars of the fee transaction (for example the parking fee and details relating to a selected payment instrument to the payment processing server 110 for processing).
• the application server 102 transmitting the particulars of the fee transaction (for example the parking fee and details relating to a selected payment instrument to the payment processing server 110 for processing).
• the method may involve the application server 102 determining that the fee was paid. In some examples, the application server 102 may determine this based on the payment processing server 1 10 transmitting a payment status indicator to the application server 102, for example, either successful or unsuccessful.
• the method may involve responsive to the application server 102 determining that the fee was paid, the application server 102 updating a status of the session identifier in the parking record database 1 12 as paid. Further in response, at block 528, the method may involve the application server 102 transmitting to the mobile device 106 an indication that the fee was paid.
• the method may involve the mobile device 106 receiving the indication that the fee was paid. And in response, at block 532, the method may involve the mobile device 106 displaying an indication that the fee was paid.
• the application server 102 may initiate a countdown timer that indicates how much time remains until the vehicle must exit the parking lot (e.g., before incurring an additional fee). For example, the countdown timer may start at 10 or 15 minutes once initiated. In one example, the application server 102 may also communicate with the mobile device 106 to cause the mobile device 106 to display the value of the countdown timer in a dynamic or live manner.
• the application server 102 may notify the mobile device 106 accordingly, such that the mobile device 106 may re-authorize payment of the fee, perhaps after selecting alternate payment data.
• the driver of the vehicle may provide the code to the exit terminal 108 to gain permission to leave the parking lot with the vehicle.
• the driver may do this by providing to the exit terminal 108, the medium with the code disposed thereon.
• the mobile device 106 may be configured to display the code, and therefore, the driver may provide to the exit terminal 108 the mobile device 106 with the code displayed thereon.
• the method may involve the exit terminal 108 capturing the code. This may involve the exit terminal 108 using a camera and a payment app to capture the code.
• the method may involve the exit terminal 108 decoding the captured code to recover the session identifier. This may involve the exit terminal 108 using a payment app to decode the captured code and to recover the session identifier.
• the method may involve the exit terminal 108 transmitting the recovered session identifier to the application server 102.
• the method may involve the application server 102 receiving the transmitted session identifier.
• the method may involve, responsive to the application server 102 receiving the transmitted session identifier, the application server 102 determining that the fee associated with the received session identifier has been paid. This may involve the application server 102 using the received session identifier to perform a lookup in the parking record database 1 12 to retrieve the session identifier's corresponding status.
• the method may involve the application server 102 transmitting to the exit terminal 108 an indication that the fee has been paid.
• the method may involve the exit terminal 108 receiving the indication that the fee has been paid.
• the method may involve responsive to the exit terminal 108 receiving the indication that the fee has been paid, the exit terminal 108 causing an action to be performed.
• the method may involve responsive to (i) the exit terminal 108 receiving the indication that the fee has been paid, and (ii) the exit terminal 108 determining that the countdown timer has not expired, the exit terminal causing the action to be performed.
• the application server 102 may determine and transmit to the mobile device 106 an additional fee, and the mobile device 106 may authorize payment of that fee in a manner similar to that described above in connection with the original fee.
• the exit terminal 108 causing an action to be performed may involve the exit terminal 108 causing an access control device to be moved.
• the exit terminal 108 may cause the boom to be raised thereby permitting vehicles to exit the parking lot.
• the exit terminal 108 may cause other actions to be performed.
• the exit terminal 108 may cause tire spikes to be retracted, thereby permitting vehicles to exit the parking lot.
• the user profile 1 14 may be stored on the mobile device 106 and on the application server 102.
• the capturing app 164 on the mobile device 106 may synchronize changes to the user profile 1 14 with the copy of the profile on the application server 102 as the changes occur, or periodically, or explicitly under user command.
• the copy of the user profile on the application server 102 can then be imported to a different mobile device 106, for example when the user changes mobile devices or in the event the user loses or damages the mobile device 106.
• transmission of any of the data described herein can be encrypted.
• the application server 102 instead of the application server 102 sending the particulars of the financial transaction (for example, the fee and the payment details) to the payment processing server 110 for processing, the application server 102 can process the payment itself.
• the only user action required to effect payment of the fee is selecting a payment instrument from the payment data associated with the user profile 114 or otherwise entering information regarding a payment instrument.
• codes such as QR codes can enable payment of a parking lot fee to be conducted more efficiently than is possible by means of known prior art methods.
• the user need only capture, by means of the mobile device 106, a code disposed on a medium in order to effect payment of the parking lot fee.
• the user is spared the tedium of having to locate a payment terminal in the parking lot, having to wait in line to use the payment terminal, and having to tender cash or a physical payment instrument such as a credit or debit card for payment.
• the user does not face the risk of the payment terminal being out of order or out of change.
• the user can pay the parking fee just before arriving back at the user's vehicle in the parking lot or, alternatively, when safely seated in the user's vehicle, with a clear indication of how much time remains before expiry of a countdown timer within which to exit the parking lot without an additional payment. It is anticipated that the disclosed system and method for paying parking lot fees will reduce the tedium of such payments.
• the application server 102 can provide the exit terminal 108, prior to the exit terminal 108 receiving the code or medium with the code for a driver to exit the parking lot, the session identifier, an indication the fee has been paid, and data identifying the countdown timer associated with the fee payment for the session identifier. Providing those items to the exit terminal 108 in this manner can allow the exit terminal 108 to confirm successful payment and timely provision of the code or the medium for the parking session more quickly.
• an example application of the system 100 allows a user to pay a parking lot fee.
• the system 100 may be used in connection with users who wish to pay other types of fees as well.
• the system may allow a user to pay a fee for a travel session associated with a toll road.
• the fee may be a function of at least a distance between a first location (e.g., where a dispenser terminal is located) and a second location (e.g., where an exit terminal is located).
• the application server 102 may determine the first and/or second locations based on a location of the dispenser terminal 104, a location of the exit terminal 108, and/or a location of the mobile device 106, any of which may transmit such locations to the application server 102 for use in determining the fee.
• a method comprising:
• a mobile device (106) capturing a code disposed on a medium, wherein the code encodes an identifier
• the mobile device (106) decoding the captured code to recover the identifier
• the mobile device (106) transmitting to a server (102) via a communication network (1 16) the recovered identifier;
• the mobile device (106) receiving from the server (102) via the communication network (1 16) a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time;
• the mobile device (106) decoding the code to recover the first time
• the mobile device (106) transmitting to the server (102) via the communication network (116) payment data to facilitate payment of the received fee.
• FIGGS. 1 , 3, 4, and 5A-5C The mobile device (106) transmitting to the server (102) via the communication network (116) payment data to facilitate payment of the received fee.
• the mobile device (106) transmitting to the server (102) via the communication network (1 16) a second identifier;
• the mobile device (106) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier. (FIGS. 1 , 3, 4, and 5A-5C).
• the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder.
• the mobile device (106) receiving from the server (102), an indication that the fee was paid;
• the mobile device (106) responsive to the mobile device (106) receiving the indication that the fee was paid, the mobile device (106) displaying an indication that the fee was paid. (FIGS. 1 , 3, 4, and 5A-5C).
• FIGS. 1 , 3, 4, and 5A-5C providing the code displayed on the medium to a capturing device.
• the mobile device (106) determining that the captured code has a particular property
• the mobile device (106) responsive to the mobile device (106) determining that the captured code has the particular property, the mobile device (106) launching an application to facilitate payment of the received fee. (FIGS. 1 , 3, 4, and 5A-5C).
• a mobile device (106) configured for performing the functions recited of examples 1-23. (FIGS. 1 , 3, 4, and 5A-5C).
• a method comprising:
• a server (102) receiving from a mobile device (106) via a communication network (1 16) the identifier; responsive to the server (102) receiving the identifier, the server (102) determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time;
• the server (102) transmitting to the mobile device (106) via the communication network (116) the determined fee;
• the server (102) receiving from the mobile device (106) via the communication network (116) authorization to pay the determined fee;
• the server (102) responsive to the server (102) determining that the determined fee has been paid, the server (102) transmitting an indication that the determined fee has been paid. (FIGS. 1 , 3, 4, and 5A-5C).
• the server (102) receiving from the mobile device (106) via the communication network (116) payment data to facilitate payment of the determined fee;
• the server (102) causing the determined fee to be paid using the payment data.
• the server (102) receiving from the mobile device (106) via the communication network (116) a second identifier
• the server (102) causing the determined fee to be paid using payment data associated with the second identifier. (FIGS. 1 , 3, 4, and 5A-5C).
• the server (102) transmitting to the mobile device (106) via the communication network (116) an indication that the fee was paid. (FIGS. 1 , 3, 4, and 5A-5C).
• the server (102) transmitting to an exit terminal (108) an indication that the fee was paid, wherein the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed.
• the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed.
• causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a parking lot.
• a method comprising:
• a mobile device (106) capturing a code disposed on a medium, wherein the code encodes an identifier
• the mobile device (106) decoding the captured code to recover the identifier
• the mobile device (106) transmitting to a server (102) via a communication network (1 16) the recovered identifier;
• the mobile device (106) receiving from the server (102) via the communication network (1 16) a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location;
• the method of one of examples 44-49, wherein the mobile device (106) capturing the code comprises a camera (156) of the mobile device (106) capturing the code. (FIGS. 1 , 3, 4, and 5A-5C). 51. The method of one of examples 44-50, wherein the mobile device (106) capturing the code comprises the mobile device (106) scanning the code. (FIGS. 1 , 3, 4, and 5A-5C).
• the mobile device (106) decoding the code to recover the first location; and the mobile device (106) transmitting to the server (102) via the communication network (116) the first location.
• the server (102) via the communication network (116) the first location.
• the mobile device (106) transmitting to the server (102) via the communication network (1 16) a second identifier;
• the mobile device (106) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier. (FIGS. 1 , 3, 4, and 5A-5C).
• the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder.
• the mobile device (106) receiving from the server (102), an indication that the fee was paid;
• the mobile device (106) responsive to the mobile device (106) receiving the indication that the fee was paid, the mobile device (106) displaying an indication that the fee was paid. (FIGS. 1 , 3, 4, and 5A-5C).
• the mobile device (106) displaying the captured code; and providing the code displayed on the medium to a capturing device. (FIGS, and 5A-5C).
• the mobile device (106) determining that the captured code has a particular property
• the mobile device (106) responsive to the mobile device (106) determining that the captured code has the particular property, the mobile device (106) launching an application to facilitate payment of the received fee. (FIGS. 1 , 3, 4, and 5A-5C).
• a mobile device (106) configured for performing the functions recited in one of examples 44-66. (FIGS. 1 , 3, 4, and 5A-5C).
• a method comprising:
• a server (102) receiving from a mobile device (106) via a communication network (1 16) the identifier;
• the server (102) responsive to the server (102) receiving the identifier, the server (102) determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is a different from the first location;
• the server (102) transmitting to the mobile device (106) via the communication network (116) the determined fee; the server (102) receiving from the mobile device (106) via the communication network (116) authorization to pay the determined fee;
• the server (102) responsive to the server (102) determining that the determined fee has been paid, the server (102) transmitting an indication that the determined fee has been paid.
• identifier comprises a unique identifier of a travel session associated with a toll road
• fee comprises a fee for the travel session.
• (1 16) comprises a wide-area network. (FIGS. 1 , 3, 4, and 5A-5C).
• the server (102) receiving from the mobile device (106) via the communication network (116) payment data to facilitate payment of the determined fee;
• the server (102) receiving from the mobile device (106) via the communication network (116) a second identifier
• the server (102) causing the determined fee to be paid using payment data associated with the second identifier. (FIGS. 1 , 3, 4, and 5A-5C).
• the server (102) transmitting to an exit terminal (108) an indication that the fee was paid, wherein the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed.
• the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed.
• causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a toll booth.
• causing the action to be performed comprises causing an access control device in the toll booth lot to be moved. (FIGS. 1 , 3, 4, and 5A-5C).
• a server (102) configured for performing the functions recited in one of examples 69-83.
• FIGGS. 1 , 3, 4, and 5A-5C A server (102) configured for performing the functions recited in one of examples 69-83.
• FIGS. 1 , 3, 4, and 5A-5C A server (102) configured for performing the functions recited in one of examples 69-83.
• FIGS. 1 , 3, 4, and 5A-5C A server (102) configured for performing the functions recited in one of examples 69-83.
• FIGS. 1 , 3, 4, and 5A-5C 85.
• a mobile device (106) comprising:
• a capturing device configured to capture a code
• a network interface configured for facilitating communication between the mobile device (106) and a server (102);
• a server (102) comprising:
• a network interface (184) configured for facilitating communication between the server (102) and another device;
• each step, block and/or communication can represent a processing of information and/or a transmission of information in accordance with example embodiments.
• Alternative embodiments are included within the scope of these example embodiments.
• functions described as steps, blocks, transmissions, communications, requests, responses, and/or messages can be executed out of order from that shown or discussed, including in substantially concurrent or in reverse order, depending on the functionality involved.
• more or fewer steps, blocks and/or functions can be used with any of the message flow diagrams, scenarios, and flow charts discussed herein, and these message flow diagrams, scenarios, and flow charts can be combined with one another, in part or in whole.
• a step or block that represents a processing of information can correspond to circuitry that can be configured to perform the specific logical functions of a herein- described method or technique.
• a step or block that represents a processing of information can correspond to a module, a segment, or a portion of program code (including related data).
• the program code can include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique.
• the program code and/or related data can be stored on any type of computer-readable medium such as a storage device including a disk or hard drive or other storage media.
• the computer-readable medium can include non-transitory computer-readable media such as computer-readable media that stores data for short periods of time like register memory, processor cache, and/or random access memory (RAM).
• the computer- readable media can include non-transitory computer-readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, and/or compact-disc read only memory (CD-ROM), for example.
• the computer-readable media can be any other volatile or non-volatile storage systems.
• a computer-readable medium can be considered a computer-readable storage medium, for example, or a tangible storage device. Any data identified as being stored within a data storage device or transmitted to a device for storage within a data storage device can comprise a computer data signal embodied in a carrier wave.
• a step or block that represents one or more information transmissions can correspond to information transmissions between software and/or hardware modules in the same physical device.
• other information transmissions can be between software modules and/or hardware modules in different physical devices.

Landscapes

• General Physics & Mathematics (AREA)
• Business, Economics & Management (AREA)
• Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Accounting & Taxation (AREA)
• Computer Networks & Wireless Communication (AREA)
• Finance (AREA)
• Strategic Management (AREA)
• General Business, Economics & Management (AREA)
• Theoretical Computer Science (AREA)
• Devices For Checking Fares Or Tickets At Control Points (AREA)
• Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
• Meter Arrangements (AREA)
• Control Of Vending Devices And Auxiliary Devices For Vending Devices (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Applications Claiming Priority (4)

Publications (1)

Family

ID=53178567

Family Applications (1)

Country Status (4)

Families Citing this family (3)

Citations (3)

Family Cites Families (4)

• 2013
  • 2013-11-12 EP EP13795286.7A patent/EP2917888A1/en not_active Ceased
  • 2013-11-12 MX MX2015005856A patent/MX354155B/es active IP Right Grant
  • 2013-11-12 JP JP2015541238A patent/JP6146750B2/ja active Active
  • 2013-11-12 CA CA2890815A patent/CA2890815C/en active Active

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events