PRIORITY CLAIM

[0001] This application claims priority to U.S. Provisional Patent Application No. 62/067,854, entitled "TOLL PAYMENT COLLECTION WITH COMMUNICATION DEVICE," filed October 23, 2014, the entire contents of which are hereby incorporated by reference.

BACKGROUND

[0002] Facility operators collect use fees for pay-for-use facilities. In some applications, the facility operators employ electronic fee collection technologies. For example, toll road operators (TROs) use electronic toll collection technologies to collect toll fees. In some examples, TROs offer free flow (e.g., non-stop) lanes in toll roads for use by vehicles equipped with identification devices. In some examples, identification devices identify the vehicles and are associated with user balance accounts of the vehicle users. The TROs collect the toll fees from the associated user balance accounts.

[0003] In some examples, TROs capture images of vehicles using toll roads. For vehicles equipped with identification devices, the TROs collect the toll fees from the associated user balance accounts. For vehicles equipped without identification devices, TROs can use image-based transactions (IBTs) to attempt to collect toll payments. For example, IBTs can include using captured vehicle images to identify the vehicle registrants and collect toll fees from the vehicle registrants.

SUMMARY

[0004] Implementations of the present disclosure include computer-implemented methods for collecting toll fees for use of a toll road facility. In some implementations, methods include actions of receiving a first message, the first message including information associated with an invoice, obtaining an invoice number assigned to the invoice based on the information, obtaining a vehicle identifier based on the invoice number, registering a device for electronic payment of toll fees at least partially based on the vehicle identifier, and transmitting a request for payment of at least a toll fee that is identified in the invoice. Other implementations of these aspects include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.

[0005] These and other implementations may each optionally include one or more of the following features: the information includes the invoice number; the information includes an image of a machine-readable code printed on the invoice, the image being processed to determine the invoice number encoded in the machine-readable code;

obtaining a vehicle identifier based on the invoice number includes cross-referencing a database using the invoice number, the database storing the vehicle identifier and associating the invoice number with the vehicle identifier; the vehicle identifier is determined based on a transaction, and is stored in the database based on the transaction; the transaction includes a use of the toll road facility by a vehicle associated with the vehicle identifier; registering a device for electronic payment of toll fees includes transmitting a second message to the device, the second message requesting confirmation of registration for toll-text payment; and the first message is received from the device.

[0006] The present disclosure also provides a computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations in accordance with implementations of the methods provided herein.

[0007] The present disclosure further provides a system for implementing the methods provided herein. The system includes one or more processors, and a computer- readable storage medium coupled to the one or more processors having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations in accordance with implementations of the methods provided herein.

[0008] It is appreciated that methods in accordance with the present disclosure can include any combination of the aspects and features described herein. That is, methods in accordance with the present disclosure are not limited to the combinations of aspects and features specifically described herein, but also include any combination of the aspects and features provided. [0009] The details of one or more implementations of the present disclosure are set forth in the accompanying drawings and the description below. Other features and advantages of the present disclosure will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

[0010] FIG.l depicts an example system architecture in accordance with

implementations of the present disclosure.

[0011] FIG. 2 depicts an example process that can be executed in accordance with implementations of the present disclosure.

[0012] FIG. 3 depicts an example process that can be executed in accordance with implementations of the present disclosure.

[0013] FIG. 4 depicts an example process that can be executed in accordance with implementations of the present disclosure.

[0014] FIG. 5 depicts a schematic diagram of an example computing system that can be used to execute implementations of the present disclosure.

[0015] Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

[0016] Implementations of the present disclosure are generally directed to a payment collection system for pay-per-use facilities. More particularly, implementations of the present disclosure provide a collection schema (e.g., a toll-text scheme) that enables toll road users (TRUs) to register with a toll road operator (TRO) and to pay toll fees based on messaging between a system associated with a TRO and a communication device associated with the toll road user. In this manner, a toll road user is able to easily and efficiently register with the TRO, and the TRO is able to easily and efficiently collect toll fees for a vehicle using the toll road facility. As discussed in further detail herein, implementations of the toll-text scheme of the present disclosure enable the TRO to collect toll fees from a service provider that provides data transfer services for the communication device. [0017] Implementations of the present disclosure include a mutual message communication schema. In some examples, a TRO system associated with a TRO receives an image of a vehicle using a toll road facility. For example, a digital image of the vehicle can be captured and a digital image file can be received by the TRO system. In some examples, the TRO system associated with the TRO is an on-premise system that is owned and operated by the TRO (e.g., on one or more servers of the TRO). In some examples, the TRO system associated with the TRO is an off-premise system that is operated on behalf of the TRO by a service provider (e.g., on one or more servers of a cloud service provider). In some examples, the TRO system processes the image to determine a vehicle identifier of the vehicle. In some examples, the vehicle identifier includes a license plate number (LPN) of the vehicle. In some examples, processing of the image can include optical character recognition (OCR) and/or vehicle signature recognition. In some examples, and the TRO system determines that the vehicle identifier is associated with a device identifier of a communication device. For example, the TRO system can access a database that associates vehicle identifiers to one or more device identifiers, each device identifier being unique to a respective communication device. In some examples, a communications device can include a mobile communications device (MCD) (e.g., a cellular telephone).

[0018] In some implementations, the TRO system transmits a message to the communication device to request approval for collecting one or more toll payments. In some examples, the TRO system receives a message from the communication device, which indicates approval to collect the toll payment(s). In some examples, in response to the message from the communication device, the TRO system transmits a payment request to a payment system. In some examples, the payment system is associated with a communications service provider (CSP) that is associated with the communication device. In some examples, the CSP can provide telephone and/or data transfer services for the communication device identifier. Example CSPs can include, but are not limited to, AT&T, Verizon, Sprint, T-Mobile, and Virgin Mobile. In some examples, the payment system associated with the CSP is an on-premise system that is owned and operated by the CSP (e.g., on one or more servers of the CSP). In some examples, the payment system associated with the CSP is an off-premise system that is operated on behalf of the CSP by a service provider (e.g., on one or more servers of a cloud service provider). The TRO collects the toll payment(s) from the CSP. The CSP collects the toll payment(s) and/or service charges from the user. Example payment methods can include monthly CSP invoicing to the user, subtraction from a user's CSP prepaid account balance, and/or an E- wallet or other payment methods (e.g., credit / debit bank accounts) managed by the CSP.

[0019] In some implementations, message communication between the TRO and the MCD is provided using one or more messaging services and/or protocols. Example messaging services and/or protocols can include multimedia service (MMS), short message service (SMS), transmission control protocol / Internet protocol (TCP/IP), and/or electronic mail (email). In some examples, an application (APP) can be installed on and executed by the MCD, where message communication between the TRO and the MCD is facilitated by the application.

[0020] FIG.l depicts an example system architecture 100 in accordance with implementations of the present disclosure. The example system architecture 100 includes a user 102 and a user-side device 104, server systems 106, 112, 114 and a network 108. In some examples, the device 104 can include any appropriate type of device such as a handheld computer, a tablet computing device, a personal digital assistant (PDA), a cellular telephone, a network appliance, a camera, a smart mobile phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, an email device, a text message device, a game console, or any appropriate combination of any two or more of these data processing devices or other data processing devices. In the example of FIG. 1, and as used by way of example throughout the remainder of the present disclosure, the user-side device 104 is provided as a MCD, such as a cellular telephone and/or a smartphone.

[0021] In some examples, the user-side device 104 and the server systems 106, 112, 114 communicate with one another over the network 108. In some examples, the network 108 can include a large computer network, such as a local area network (LAN), a wide area network (WAN), the Internet, a cellular network, or a combination thereof connecting any number of communication devices, computing devices, and/or server systems.

[0022] In some examples, each server system 106, 112, 114 can include one or more computing devices and one or more machine-readable repositories, or databases. In the depicted example, the server system 106 is associated with a CSP, the server system 112 is associated with a vehicle registration authority (VRA) (e.g., a Secretary of State and/or a Department of Transportation for a particular state), and the server system 114 is associated with a TRO. In some examples, a server system can be associated with an entity (e.g., CSP, TRO, VRA) by being owned and operated by the entity. In some examples, a server system can be associated with an entity (e.g., CSP, TRO, VRA) by being provided on behalf of the entity (e.g., by a cloud service provider). In some examples, each server system 106, 112, 114 can include one or more computing devices and one or more machine-readable repositories, or databases.

[0023] For purposes of illustration, the depicted example includes a single TRO, a single VRA, a single CSP and a single user-side device 104. It is appreciated, however, that implementations of the present disclosure can be realized with any appropriate number of TROs, VRAs (e.g., for different states), CSPs and user-side devices.

[0024] With continued reference to FIG. 1, the user 102 can be a user of a vehicle 110. In some examples, the vehicle 110 is registered with a VRA, and an underlying vehicle registration can be associated vehicle owner information (e.g., vehicle owner name and mailing address). In some examples, the VRA issues a vehicle identifier (e.g., a license plate displaying an LPN) that is unique to the vehicle 110. In some examples, and the VRA associates the vehicle identifier with the vehicle owner information (e.g., in a database provided with the server system 112).

[0025] In some examples, the CSP provides communication and/or data transfer services for the user-side device 104. In some examples, the user-side device 104 is associated with one or more unique device identifiers. An example, the device identifier can include a cellular telephone number or other RFID devices. In some examples, the user 102 has an account established with the CSP to effect payment of telephone service charges and/or data transfer service charges. In accordance with implementations of the present disclosure, the account can be used to effect payment of toll fees, as discussed in further detail herein. In some examples, the CSP periodically (e.g., weekly or monthly) invoices the user 102 for charges incurred. In some examples, the user 102 pays for incurred charges with a user payment account. In some examples, the user payment account can be a bank account, a credit card account, a debit card account, a CSP account (e.g., an account maintained with the CSP) and/or an electronic wallet (e-wallet) account. In some examples, the account is a pre-paid account, where the CSP can deduct funds to pay for incurred charges. In some examples, the pre-paid account can be an anonymous account.

[0026] With continued reference to FIG. 1, a toll road facility (TRF) 116 is provided. In some examples, the TRF 116 is associated with the TRO (e.g., the TRO owns and/or operates the TRF 116). In some examples, the TRF provides a toll road with free flow (e.g., non-stop) lanes for use by vehicles. In some examples, the TRF 116 includes one or more cameras to capture images of vehicles using the free flow lanes and can transmit image files to the server system 114 for processing, as discussed in further detail herein. In some examples, the image files can be transmitted over a facility-specific network 115 (e.g., a LAN) and/or the network 108.

[0027] In some implementations, the TRF 116 includes one or more sensing devices for detecting vehicle passage through the TRF 116 (e.g., through a free flow lane). In some examples, vehicles can be equipped with identification devices, which uniquely identify associated toll-text scheme and or balance accounts for charging toll fees.

Example identification devices can include radio frequency identification devices (RFIDs) (or "tags"), and MCDs. In some examples, balance accounts are linked to user payment accounts for automated replenishment at a TRO back office system (BOS). In some examples, the one or more sensing devices can include a sensor, a detector, an RFID reader, a tag reader or a logic unit/controller deployed at the TRF. In some examples, the one or more sensing devices can include motion detectors.

[0028] As discussed in further detail herein, implementations of the present disclosure provide a protocol that includes a messaging schema for easily and efficiently collecting fees (e.g., toll fees) for pay-to-use facilities (e.g., TRFs). In short, a user that intends to use, or that has used a TRF can register a communication device identifier and a vehicle identifier tuple (e.g., [MCDID, VEHID]) with a TRO system associated with a TRO, and the registered information can be used to collect toll fees from a CSP associated with the communication device. [0029] Referring now to FIGs. 2 and 3, implementations of the present disclosure will be described in further detail. For purposes of illustration, labels corresponding to the example system architecture 100 of FIG. 1 are used to present corresponding devices and/or systems.

[0030] FIG. 2 depicts an example process 200 that can be executed in accordance with implementations of the present disclosure. In some examples, the example process 200 can be provided using one or more computer-executable programs executed using one or more computing devices (e.g., the server system 114 of FIG. 1).

[0031] In some implementations, of the example process 200 includes a registration protocol for a user to register a vehicle and a MCD with a TRO system. In accordance with implementations of the present disclosure, the user takes an image of the vehicle. In some examples, the user can use a camera of the MCD or another camera to take the image. In some examples, the image can include a rear-view of the vehicle and/or a front- view of the vehicle. In some examples, the image depicts the LPN of the vehicle. In some examples, the image includes vehicle fingerprint characteristics (e.g., the shape, color, and/or brand/model emblem of the vehicle). In some examples, a shape of the vehicle can be derived to provide profile information representative of the vehicle. For example, a large van will have a larger profile than a small sports car. The user transmits the image to the TRO system.

[0032] In some implementations, the user provides the vehicle LPN and region (e.g., state) of issuance, as well as the MCD identifier. In some examples, the MCD identifier can include an identifier associated with the user (e.g., a mobile subscriber integrated services digital network-number (MSISDN) and/or a subscriber identity module (SIM)). In some examples, the identifier associated with the user is a telephone number. In some examples, the MCD identifier can include a unique serial number (e.g., mobile equipment identity (MEI/IMEI)).

[0033] In some implementations, the user uses the MCD to transmit the image to the TRO system using a messaging service and/or communication protocol. In this manner, the image and the MCD identifier can be provided to the TRO system. For example, a telephone number can be associated with a registration process (e.g., 888-729-8655 (PAY-TOLL)) and the user can transmit the image using the telephone number. In some implementations, the user uses a computing device (e.g., a desktop computer) to transmit the image and a MCD identifier (e.g., MCD ID) to the TRO system (e.g., by email, through a web portal provided by the TRO system). In any case, the TRO system receives the image and/or data that can be processed to identify the vehicle and the MCD identifier (e.g., associated with the user by the CSP system).

[0034] A vehicle image is received (202). In some examples, the TRO system receives the vehicle image from a user and is associated with a MCD. In some examples, the MCD ID is determined, and the MCD ID and vehicle image are stored (204). In some examples, the TRO system stores the MCD ID and the vehicle image in a registration database.

[0035] A CSP that provides communication and/or data transfer services for the MCD is determined (206). In some examples, a registry of CSPs can be cross-referenced based on the MCD ID to identify the CSP that provides communication and/or data transfer services for the MCD. It can be determined whether the CSP is a valid CSP (208). In some examples, a CSP can be determined to be a valid CSP, if the CSP is included in the registry of CSPs. In some examples, a CSP is a valid CSP, if the CSP supports message-based payment protocols (e.g., toll-text scheme). If it is determined that the CSP is not a valid CSP, the TRO system transmits a rejection message (210). In some examples, the rejection is transmitted using the same channel (e.g., SMS message, MMS message, email or application-based message) used to provide the vehicle image and the MCD ID to the TRO system.

[0036] If the CSP is a valid CSP, the LPN of the vehicle is determined (212). In some examples, the TRO system processes the image to determine the LPN (212). In some examples, the TRO system processes the image using image analysis processes. An example image analysis process can include OCR. In some examples, the TRO system also processes the image to provide vehicle fingerprint characteristics from the vehicle. In some examples, the TRO system can determine a region (e.g., state, province) of registration. For example, a state where the vehicle is registered and that issued the LPN can be determined. In some examples, the region can be provided in the LPN itself. In some examples, the region can be identified on the license plate and can be determined based on image processing of the vehicle image. [0037] Information is transmitted to the user (214). In some examples, the TRO system transmits a message (e.g., SMS message, MMS message, email or application- based message) to the MCD based on the MCD identifier. In some examples, the message includes the LPN and the state of issuance. In some examples, the message can include a request for the user to verify the information. In some examples, the message indicates that, if the information of the LPN and the region of registration are correct, the user is to transmit back a positive acceptance code in a response message. An example message can include:

TX 123 456

If OK & you accept terms, message: 12

If incorrect, message 13 + state & LPN

In this example, the message indicates that the registration region was determined to be the state of Texas (TX) and the LPN was determined to be 123 456. Further, the example message asks the user to confirm accuracy of the information and their participation in the payment scheme by sending a response message including the number 12 (e.g., acceptance code). The example message also asks the user to send a response message including the number 13 (e.g., rejection code), the registration state and the LPN, if the provided information is incorrect.

[0038] A response message is received (216). In some examples, the TRO system receives the response message. It is determined whether to update the information of the LPN and/or the registration region (218). For example, if the response message includes corrected information and/or a rejection code (e.g., "13"), the TRO system determines that the information is to be updated. In some examples, the information can be updated based on information provided in the response message and/or based on re-processing the vehicle image. If the response message includes an acceptance code (e.g., "12"), the TRO system determines not to update the information, and a confirmation message is transmitted to the user (220). In some examples, the TRO system transmits the confirmation message (e.g., SMS message, MMS message, email or application-based message) to the MCD based on the MCD identifier.

[0039] In some examples, the confirmation message includes information notifying the user that the registration is complete and/or that the user will be contacted to approve charges for using the subject TRF. In some examples, the confirmation message can explain the user's obligation to approve or refuse payment of toll fees. In some examples, the confirmation message can inform the user that the registration will be cancelled and/or that alternative collection methods will be adopted if the user refuses to approve payment of or fails to respond to a payment request. In some implementations, alternative collection methods can include a standard pay-by-mail collection method (e.g., sending an invoice by mail to the registered vehicle owner, as determined from the VRA). In some examples, the pay-by-mail collection method incurs higher payment charged to the user due to higher collection costs and/or administrative costs.

[0040] In some examples, the confirmation message can instruct the user to visit a website for details of a payment agreement between the TRO and the user. In some examples, the registration process can include requiring the user to visit a website and confirm that the user has read and agreed to terms of service. In some examples, user confirmation can be provided by the user entering the MCD ID and the LPN to the website. In some examples, the user is required to visit such a website within a threshold time (e.g., 2 days) of having received the confirmation message. In some examples, the confirmed payment agreement and/or the terms of service ("confirmation information") enable the TRO to request payment from the CSP associated with the MCD. In some examples, the TRO can provide confirmation information to the CSP. In some examples, the confirmation information includes the user's permission for the CSP to function as a payment agent and to charge the user's CSP account. In some examples, as discussed in further detail herein, the inclusion of financial transactions into the CSP billing process can occur after the TRO has notified the user of any unpaid detected and recorded transactions related to use of the TRF and the user has approved the charges for inclusion into the TSP billing process.

[0041] In some examples, and in response to receiving the response message, the TRO system associates the vehicle identifier (e.g., LPN) with the device identifier (e.g., MCD ID) in the registration database (e.g., LPN-MCD database). Once the registration is completed, the TRO can scan unpaid transactions charged to the vehicle identifier and notify the user to pay. [0042] In some implementations, a device identifier can be associated with a plurality of vehicle identifiers in the registration database. In this manner, a user can register multiple vehicles for the collection scheme. For example, when a user registers, the CSP system can determine that another MCD identifier is already associated with the particular LPN. In such cases, the CSP system can confirm with the user whether the user would like to register a second MCD identifier with the same LPN.

[0043] In some examples, a vehicle identifier is associated with one device identifier (e.g., to avoid notification and billing ambiguity or potential multiple billing for a single toll fee). In some examples, a vehicle identifier is associated with multiple device identifiers. For example, a toll fee approval request, discussed in further detail below, can be provided to multiple MCDs, and an approval from one of the MCDs can result in collection for the toll fee being made to the CSP associated with the responding MCD.

[0044] In some implementations, the TRO and/or the user can de-register the vehicle identifier with the device identifier. For example, the user can de-register when the user sells the vehicle, has a different LPN associated with the vehicle, when the user changes the MCD ID, and/or when the user enrolls in another payment scheme (e.g., a tag account system).

[0045] With continued reference to FIG. 2, it can be determined whether any unpaid transactions have already been incurred for the vehicle (222). For example, and as discussed in further detail below with reference to FIG. 3, the user can use the TRF before having registered for the payment scheme. Consequently, the TRO system can already include a record for use of the TRF by the vehicle associated with the LPN that the user just registered. If it is determined that there are unpaid transactions, a payment approval request can be transmitted to the user (226) (discussed in further detail below with reference to FIG. 3). If it is determined that there are no unpaid transactions, the TRO system waits for a transaction to occur (e.g., the vehicle to pass through the TRF).

[0046] FIG. 3 depicts an example process 300 that can be executed in accordance with implementations of the present disclosure. In some implementations, the example process 300 can be provided by one or more computer-executable programs executed using one or more computing devices (e.g., the server system 114 of FIG. 1). [0047] A vehicle image is captured (302). For example, when a vehicle uses a TRF, the TRF detects the vehicle passing and captures an image. In some examples, the TRF captures the image as part of a toll transaction. In some examples, a toll transaction includes the vehicle image, a toll point location identifier, direction of travel, time/date, vehicle class, and/or transponder identifier (e.g., if the vehicle also includes a

transponder). In some examples, the TRF provides the image to the TRO system. An LPN is determined (304). In some examples, the TRO system receives the image, and processes the image to determine the LPN. It is determined whether the vehicle is registered for the collection schema of the present disclosure (306). For example, the TRO system references a registration database (e.g., LPN-MCD database) that associates vehicle identifiers to respective device identifiers (e.g., MCD ID). If it is determined that the vehicle is not registered (e.g., the vehicle identifier is not provided in the database), the example process continues at 320.

[0048] If it is determined that the vehicle is registered (e.g., the vehicle identifier is provided in the database), unpaid transactions associated with the LPN are collected (308). In some examples, an unpaid transaction can include a current transaction (e.g., that triggered the example process 300). In some examples, an unpaid transaction can include a previous transaction (e.g., previous use of the TRF, for which payment has not yet been requested and/or approved).

[0049] A collection request message is transmitted to the MCD that is associated with the determined LPN (310). In some examples, the TRO system transmits the collection request message as an electronic message (e.g., SMS message, MMS message, or application-based message) to the device (310). In some examples, the collection request message includes a request for approval to collect payment for one or more toll fees from the CSP. In some examples, the collection request is provided for a single toll fee (e.g., for a single use of the TRF). In some examples, the collection request is provided for a plurality of tolls fees associated with the LPN.

[0050] In some implementations, the TRO system provides collection requests for each transaction. In some examples, the TRO system provides batch collection requests. For example, the TRO system can accumulate a plurality of unpaid transactions or toll fees charged to the device identifier within a period of time. In some examples, the period of time can be a logical billing cycle (e.g., daily, weekly, monthly). In this manner, the number of collection messages sent to users can be reduced.

[0051] In some examples, the TRO system bundles the plurality of unpaid

transactions into groups (e.g., entry and exit transactions, short and long trip transactions, round trip transactions). In some examples, the TRO system can provide a plurality of toll products to TRF users (e.g., long trip discounts, trip caps, round trip discounts). In some examples, the TRO system can process the plurality of toll products to the corresponding groups of unpaid transactions to calculate a total toll payment for the plurality of unpaid transactions.

[0052] An example collection request message can include:

LPN: TX 123 456

Toll Passages: Mar 22, 2013

10:02 am NB SH130 @ IH-10: $1.80

15:47 pm SB SH130 @ IH-10: $1.80

Total: $3.60

To approve text 91, to reject text 96

[0053] In some examples, sending a collection request message can be optional. For example, the user can provide pre-approval for collection requests. In this manner, the TRO system can automatically proceed to collecting toll fees from a CSP system (as discussed herein) without sending a collection request message to and/or receiving an approval message from the user.

[0054] It is determined whether the collection request has been approved (312). If the collection request has not been approved, the example process 300 continues at 320. In some examples, the user can text a rejection code (e.g., 96). In some examples, if a response is not received within a pre-determined period of time, rejection of the collection request is assumed. In some examples, the approval message can indicate a specified period of time for the user to respond. In some examples, if the TRO system has not received a response within the specified period of time, rejection is assumed.

[0055] If the collection request has been approved, a confirmation message is transmitted to the MCD (314). For example, the TRO system can receive an approval message from the MCD with an approval code (e.g., 91), indicating that the user approves the toll payment(s). In response, the TRO system transmits a confirmation message (e.g., SMS message, MMS message or application-based message) to the device. In some examples, the confirmation message includes a payment receipt of the toll payment(s). In some examples, the payment receipt can include additional information (e.g., advertisement information, discount information). In some examples, when a collection request message is not needed (e.g., the user has pre-approved toll charges), the payment receipt is anyway sent.

[0056] A payment request is transmitted to the CSP system (316). In some examples, the TRO system provides a payment request to the CSP system. In some examples, the payment request includes data confirming the user's approval to the collection request (e.g., the approval response from the MCD), and/or details of the transaction(s). Payment is collected from the CSP (318). For example, the TRO system receives payment from the CSP (e.g., the CSP transfers funds to the TRO). In some examples, the TRO uses an agent to collect the first toll payment from the CSP. In some examples, batch payments can be made from the CSP to the TRO. For example, a payment from the CSP to the TRO can include payment for transactions incurred by multiple users that the CSP is a service provider for.

[0057] In some examples, the CSP can charge a fee to the user for functioning as a payment agent for collection of pay-per-use fees. In some examples, the user can pay charges from the CSP using a user payment account (e.g., at the end of a billing cycle). In some examples, the CSP provides payment to the TRO after the user has paid the CSP.

[0058] With continued reference to FIG. 3, registered vehicle owner (RVO) processing is conducted (320). For example, if the LPN is not registered (306) or the user does not approve the collection request (312), RVO processing is conducted in an effort to collect payment of the transaction fee(s). In some examples, the TRO system can request or access vehicle registration information (e.g., provided by one or more VRAs). In some examples, RVO information can be retrieved based on the vehicle identifier and can include a registered owner of the vehicle associated with the vehicle identifier.

[0059] In some examples, the TRO prints and sends an invoice indicating a charge to the RVO based on the RVO information (e.g., mailing address). In some examples, the invoice can include information informing the RVO of the collection schema to pay the toll charge(s) through a device (e.g., MCD) by registering with the TRO. In some examples, the information can include a registration protocol and can instruct the RVO to transmit an image of the vehicle to the TRO to start the registration protocol with the TRO. In some examples, the invoice can include information notifying the RVO that payment of the charge(s) can be made with another user payment account (e.g., a bank account, a credit card account, a debit card account, or an E-wallet account), if the RVO does not want to pay using the toll-text scheme.

[0060] In some examples, it is determined whether the RVO elects to pay by MCD (322). In some examples, if the TRO has not received a response to the paper invoice within a specified period of time, it can be determined that the RVO has not elected to pay by MCD. As another example, if payment has been collected by another payment channel (e.g., a bank account, a credit card account, a debit card account, or an E-wallet account), it can be determined that the RVO has not elected to pay by MCD. If it is determined that the RVO has not elected to pay by MCD, and the user has not paid the invoice, other collection channels can be pursued (326). If it is determined that the RVO does elect to pay by MCD, registration can be performed (e.g., as discussed above with reference to FIG. 2). In some example, it can be determined that the RVO elects to pay by MCD, by receiving a vehicle image (e.g., 202 of FIG. 2).

[0061] In some implementations, the example process 300 depicted in FIG.3 includes additional operations. In some examples, it can be determined whether a tag is detected for a vehicle passing through the TRF (328). In some examples, the TRF can includes a sensing device to detect whether there is an identification device equipped with the vehicle using the TRF (e.g., RFID tag), which identifies the vehicle and has been associated with a balance account. The balance account is linked to user payment accounts for automated replenishment at a TRO BOS. Consequently, a collection process can be executed based on the balance account (330). For example, the TRO system receives a signal from the TRF to determine whether there is a valid identification device (e.g., tag) equipped with the vehicle. In some examples, the TRO system determines that there is a valid identification device equipped with the vehicle, the TRO system processes the transaction as an identification device transaction, and collects a toll fees from the balance account associated with the identification device. [0062] In some examples, if it is determined that a tag is not detected for a vehicle passing through the TRF, the LPN can be determined (304), as discussed above. In some examples, it is determined whether the LPN is associated with an identification device (e.g., a tag account) (332). In some examples, the TRO system can cross-reference the LPN with a tag database (e.g., LPN-Tag database). If it is determined that the LPN is not associated with a tag account, the example process 300 proceeds as discussed above. If it is determined that the LPN is associated with a tag account, collection process can be executed based on the balance account (330).

[0063] Implementations of the present disclosure are further directed to enabling TRUs to register with a TRO based on RVO invoicing. More particularly, and as described above with reference to FIG. 3, the TRO system can request or access vehicle registration information (e.g., provided by one or more VRAs). For example, the TRO system can process an image of a vehicle to determine a vehicle identifier (e.g., LPN), and RVO information can be retrieved based on the vehicle identifier. In some examples, the RVO information includes the name and address of a registered owner of the vehicle captured in the image, from which the vehicle identifier is determined. In some examples, and as also described above, the TRO prints and sends an invoice indicating a charge to the RVO based on the RVO information (e.g., name, mailing address). In some examples, the invoice includes transaction information associated with a use of a TRF by a vehicle of the RVO. Example transaction information can include time, date, location, duration, cost, and any other appropriate information, as described herein.

[0064] In accordance with implementations of the present disclosure, the invoice can include ancillary information. Example ancillary information can include an invoice number. In some examples, the invoice number is printed on the invoice as human- readable text (e.g., letters, numbers, symbols, punctuation marks). An example invoice number can be in the form LL-NNNN, where L indicates a letter (e.g., A-Z) and N indicates a number (e.g., 0-9). For example, an invoice can include the following example invoice number printed thereon:

Invoice No. TX-1234

where TX-1234 is the invoice number. In some examples, the invoice number is printed on the invoice as machine-readable code (e.g., barcode, QR-code). In some examples, the machine-readable code encodes the invoice number, and can be read by a device (e.g., MCD). For example, a MCD can include an application executing thereon, which can process an image of a machine-readable code to decode information encoded therein. For example, the application can process the image of the machine-readable code to provide the invoice number in human-readable form. In some examples, the machine -readable code can encode instructions. In some examples, the instructions can be automatically executed. For example, the application can process the image of the machine-readable code to determine the invoice number, and to automatically (without requiring user input/command) transmit the invoice number (and any other relevant information) to a computing device (e.g., the server system 114 of FIG. 1, which is associated with the TRO).

[0065] In accordance with implementations of the present disclosure, the invoice can include information informing the RVO of a collection schema to pay the toll charge(s) through a device (e.g., MCD) by registering with the TRO. In some implementations, the user (e.g., TRU) is instructed to provide the invoice number to the TRO to initiate a registration procedure. In some examples, the invoice number is provided in human- readable form, and the user is instructed to text the invoice number to a particular telephone number. For example, the invoice can include the following example text:

To register to pay fees by text, please text the invoice number (in

the format LL-NNNN) to 56789 using your mobile device.

In response to the instructions, the user can use their MCD to text the invoice number to the TRO and/or the CSP (e.g., to the server system 114 and/or the server system 106). That is, the user can use the MCD to text the invoice number and the invoice number is provided to the server system 114 and/or the server system 106, from which the LPN can be ascertained and use in the standard registration process. In some examples, the invoice number is provided in human-readable form, and the user is instructed to respond. For example, the invoice can include the following example text:

Actor Action

TRU Send text (SMS) LL-NNNN ^: TRO Reads User's SMS looks up Invoice and queries the TRO database to extract the Invoice Total and the associated LPN

TRO sends response text:

"Invoice no. LL-NNNN for License Plate TX 123456 for $xx.xx was found. If the information is correct and you wish to register into the toll text program respond Y or N"

TRU "Y"

TRO "Do you agree to register LPN TX 123 456, pay invoice LL-NNN for $xx.xx and agree to the Toll Text terms and conditions provided in the Pay-by-Mail invoice and or www. T-Txt. terms - Respond "Y or N" .

TRU "Y"

In some examples, in response to the instructions, the user can visit the specified website and can provide requested information (e.g., invoice number, MCD ID). In some examples, a secure session is established between a computing device of the user and the website (e.g., the server hosting the website) to protect user-provided information (e.g., SSL, TSL).

[0066] In some examples, the invoice number is provided in machine-readable code that is printed on the invoice, and the user is instructed to capture an image of the machine readable code, and to send the image to a defined destination (e.g., text to a particular number, send by email to a particular email address). For example, the invoice can include the following example text:

To register to pay fees by text, take a picture of the code (above)

and text the picture to 56789 using your mobile device.

In response to the instructions, the user can use their MCD to take a picture of the code and send (e.g., by text or email) the picture to the TRO and/or the CSP (e.g., to the server system 114 and/or the server system 106). In some examples, the server system that receives the picture can process the picture to decode the machine-readable code and determine the invoice number. [0067] In some examples, the invoice number is provided in machine-readable code that is printed on the invoice, and the user is instructed to capture an image of the machine readable code using a particular application that is executed on the MCD. For example, the invoice can include the following example text:

To register to pay fees by text, take a picture of the code (above)

using the "Toll Road Payment" application available at

www. appstore. com/to ll_road_payment.

In response to the instructions, the user can use their MCD to open the application and take a picture of the code. In some examples, the application can execute functionality, such that, in response to the picture being taken, the picture is processed to determine the invoice number, and the invoice number is sent to the TRO and/or the CSP (e.g., to the server system 114 and/or the server system 106).

[0068] Although several examples for providing the invoice number and/or picture to the TRO and/or the CSP are described herein, it is appreciated that implementations of the present disclosure encompass any appropriate technique for providing the invoice number and/or picture to the TRO and/or the CSP.

[0069] In some implementations, the MCD ID is also provided to the TRO and/or the CSP. For example, if the user texts the invoice number, the text message includes the invoice number and the MCD ID of the MCD used to text the invoice number. In this manner, the TRO and/or the CSP receive a data set including the invoice number and MCD ID (e.g., (Invoice Number, MCD ID). In some examples, and as described herein, the transaction(s) identified in the particular invoice can be mapped to the MCD ID.

[0070] FIG. 4 depicts an example process 400 that can be executed in accordance with implementations of the present disclosure. In some implementations, the example process 400 can be provided by one or more computer-executable programs executed using one or more computing devices (e.g., the server system 114 of FIG. 1). In some examples, the process 400 can be executed to collect toll fees after registered vehicle owner (RVO) processing is conducted (e.g., step 320 of FIG. 3).

[0071] An invoice number and MCD ID are obtained (402). For example, the invoice number and MCD ID are received by the TRO (e.g., the server system 114) through at least one of the channels described above (e.g., text, email, website, application). In response to receiving (or determining) the invoice number and the MCD ID, a registration process is executed to register the user for a toll-text scheme. An LPN of the underlying invoice number is obtained (404). In some examples, transaction information of one or more transactions that are identified in the underlying invoice can be retrieved (e.g., from a database). In some examples, a database can include an index of

transactions, each transaction being associated with an invoice number. In some examples, multiple transactions can be associated with the same invoice number. In some implementations, each transaction can include a transaction identifier (TXN ID) that uniquely identifies an occurrence of a toll road use. For example, a TXN ID uniquely identifies respective occurrences of a particular vehicle passing through one or more TRFs. For example, when a vehicle enters a toll road, the vehicle passes through a first TRF, and when the vehicle exits the toll road, the vehicle passes through a second TRF. In some examples, a single transaction includes entrance of the vehicle to the toll road through the first TRF, and exiting of the vehicle from the toll road through the second TRF, and is associated with a unique TXN ID.

[0072] In some implementations, each transaction is associated with one or more images, one or more dates, one or more times, and an LPN. For example, one or more first images of a vehicle (e.g., a front image, a rear image) can be captured when the vehicle passes through the first TRF at a first date and time, and one or more second images of a vehicle (e.g., a front image, a rear image) can be captured when the vehicle passes through the second TRF at a second date and time (e.g., later than the first date and time). In some examples, the LPN of the vehicle can be determined from the one or more images, as described herein.

[0073] In accordance with implementations of the present disclosure, and for each transaction (e.g., unique TXN ID), the one or more images, the LPN, the TXN ID and the invoice number are stored in a database. In this manner, the LPN, the one or more images and/or the TXN ID can be retrieved based on the invoice number, as described in detail herein.

[0074] In some implementations, it is determined whether the MCD ID is already registered for the toll-text scheme (406). For example, the TRO system references a registration database (e.g., LPN-MCD database) that associates vehicle identifiers to respective device identifiers (e.g., MCD ID). In some examples, if the MCD ID is not included in the registration database, it is determined that the MCD ID is not registered. In response to determining that the MCD ID is not registered, it can be determined whether the CSP is a valid CSP (408). In some examples, a CSP can be determined to be a valid CSP, if the CSP is included in the registry of CSPs, described herein. In some examples, a CSP is a valid CSP, if the CSP supports message-based payment protocols (e.g., toll-text scheme). If it is determined that the CSP is not a valid CSP, the TRO system transmits a rejection message (410). In some examples, the rejection message is transmitted using the same channel (e.g., SMS message, MMS message, email, website or application-based message) used to provide the invoice number and the MCD ID to the TRO system. In some examples, the rejection message instructs the user that their CSP does not support payment of tolls through text, and provides other options for payment of the invoice (e.g., online credit card payment, mail in check). In some examples, the TRO system transmits a message (e.g., SMS message, MMS message, email or application- based message) to the MCD based on the MCD ID (412). In some examples, the message includes the LPN and a request to confirm registration for the toll-text scheme. In some examples, the message can include a request for the user to verify the information. An example message can include:

Register TX 123 456 for toll-text payment.

If you accept terms, message: 12

If you reject the terms, message: 13

[0075] In this example, the message indicates that the registration region was determined to be the state of Texas (TX) and the LPN was determined to be 123 456. The example message asks the user to send a response message including the number 12 (e.g., acceptance code) or the number 13 (e.g., rejection code), to respectively indicate acceptance or rejection of registration in the toll-text scheme for the indicated LPN. It is determined whether registration is confirmed (i.e., accepted) (414). For example, in response to the message above, the user can transmit (e.g., using the MCD) an acceptance or rejection of the registration. If the registration is confirmed by the user, and in some examples, the process 400 continues to (220) of FIG. 2, described above, to confirm registration (e.g., by the system) and to illicit payment of any outstanding toll fees (e.g., including the toll fees addressed in the invoice). If the registration is not confirmed by the user, a message is transmitted to the user. For example, the message can indicate that the MCD and LPN have not been registered for the toll-text scheme.

[0076] In some examples, if the MCD ID is registered (406) (i.e., the MCD ID is included in the registration database), a list of LPNs that are associated with the MCD ID in the registration database is received (418). For example, the TRO system receives the list of LPNs from the registration database. In some examples, the list of LPNs include one or more LPNs. In some implementations, the LPN determined from the transaction information obtained base on the invoice number is compared to the list of LPNs. It is determined whether the LPN is included in the list of LPNs (420).

[0077] In some examples, if the LPN is included in the list of LPNs, it is determined that the particular MCD ID and LPN pair is already registered for the toll-text scheme. This may be the case, for example, if the user registered the MCD ID and LPN pair after a toll road transaction, but before receiving the invoice. In some examples, the process 400 continues as described above with reference to FIG. 3. For example, and referencing FIG. 3, any unpaid transactions are determined (310). In some examples, the process 300 continues, as described above, to collect any outstanding toll fees.

[0078] In some examples, if the LPN is not included in the list of LPNs, it is determined that the particular MCD ID and LPN pair is not already registered for the toll- text scheme. This can be the case, for example, if the user has registered the MCD ID with one or more other LPNs (e.g., the user has registered for toll-text payment for another LPN, but has not yet registered for toll-text payment for the LPN that is the subject of the invoice). If the particular MCD ID and LPN pair is not already registered for the toll-text scheme, the registration process continues as described above.

[0079] In some implementations, discounts and/or offers can be made to users to motivate users for registration in the toll-text scheme. In some examples, a user can be offered a discount of toll fees and/or any ancillary fees, if the user registers for the toll- text scheme. For example, the invoice, described above, can instruct a user that, if the user registers to pay the therein described toll fees, an X% (e.g., 10%) discount will be applied to the toll fees. In some examples, in response to user registration, the discount is applied to the toll fees (e.g., in response to receiving confirmation from the user for registration (414) of FIG. 4). In some examples, a user can be offered a payment plan for payment of past due fees, if the user registers for the toll-text scheme. For example, the invoice, described above, can instruct a user that, if the user registers to pay the therein described toll fees, payment for past due toll fees can be pro-rated over the next Y months (e.g., 6 months). In some examples, in response to user registration, the payment plan is put into effect for payment of the toll fees (e.g., in response to receiving confirmation from the user for registration (414) of FIG. 4).

[0080] Referring now to FIG. 5, a schematic diagram of an example computing system 500 is provided. The system 500 can be used for the operations described in association with the implementations described herein. For example, the system 500 may be included in any or all of the server components discussed herein. The system 500 includes a processor 510, a memory 520, a storage device 530, and an input/output device 540. Each of the components 510, 520, 530, and 540 are interconnected using a system bus 550. The processor 510 is capable of processing instructions for execution within the system 500. In one implementation, the processor 510 is a single-threaded processor. In another implementation, the processor 510 is a multi-threaded processor. The processor 510 is capable of processing instructions stored in the memory 520 or on the storage device 530 to display graphical information for a user interface on the input/output device 540.

[0081] The memory 520 stores information within the system 500. In one

implementation, the memory 520 is a computer-readable medium. In one

implementation, the memory 520 is a volatile memory unit. In another implementation, the memory 520 is a non-volatile memory unit. The storage device 530 is capable of providing mass storage for the system 500. In one implementation, the storage device 530 is a computer-readable medium. In various different implementations, the storage device 530 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device. The input/output device 540 provides input/output operations for the system 500. In one implementation, the input/output device 540 includes a keyboard and/or pointing device. In another implementation, the input/output device 540 includes a display unit for displaying graphical user interfaces. [0082] The features described can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The apparatus can be implemented in a computer program product tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by a programmable processor; and method steps can be performed by a programmable processor executing a program of instructions to perform functions of the described implementations by operating on input data and generating output. The described features can be

implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0083] Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks. The processor and the memory can be supplemented by, or incorporated in, ASICs (application- specific integrated circuits). [0084] To provide for interaction with a user, the features can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer.

[0085] The features can be implemented in a computer system that includes a back- end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Examples of communication networks include, e.g., a LAN, a WAN, and the computers and networks forming the Internet.

[0086] The computer system can include clients and servers. A client and server are generally remote from each other and typically interact through a network, such as the described one. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0087] In addition, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps may be provided, or steps may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other

implementations are within the scope of the following claims.

[0088] A number of implementations of the present disclosure have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the present disclosure. Accordingly, other implementations are within the scope of the following claims.