Toll payment collection with communication device

Implementations include actions of receiving an image of a vehicle using a toll road facility, processing the image to determine a vehicle identifier, and determining that the vehicle identifier is provided in a database, the database associating vehicle identifiers to respective device identifiers, and in response: determining a device identifier associated with the vehicle identifier from the database, transmitting a first message to a device associated with the device identifier, the first message including a request for approval to collect a toll payment, and receiving a second message from the device, the second message indicating approval of the toll payment, and in response: transmitting a payment request to a service provider, the service provider providing data transfer services for the device, and receiving the toll payment from the service provider.

BACKGROUND

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.

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

Implementations of the present disclosure include computer-implemented methods for collecting toll fee for use of a toll road facility. In some implementations, methods include actions of receiving a first image of a first vehicle using the toll road facility, processing the first image to determine a first vehicle identifier, and determining that the first vehicle identifier is provided in a first database, the first database associating vehicle identifiers to respective device identifiers, and in response: determining a first device identifier associated with the first vehicle identifier from the first database, transmitting a first message to a first device associated with the first device identifier, the first message including a request for approval to collect a first toll payment, and receiving a second message from the first device, the second message indicating approval of the first toll payment, and in response: transmitting a first payment request to a first service provider, the first service provider providing data transfer services for the first device, and receiving the first toll payment from the first service provider. 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.

These and other implementations may each optionally include one or more of the following features: the first message is a text message; the text message is one of a short message service (SMS) message and a multimedia message service (MMS) message; the first service provider is a communications service provider (CSP); actions further include executing a registration protocol to register the first device identifier and the first vehicle identifier; the registration protocol includes: receiving the first vehicle identifier from the user, receiving the first device identifier from the user, and determining that the first service provider is provided in a service provider database, and in response, registering the first device identifier and the first vehicle identifier; actions further include receiving a second image of the first vehicle, the second image being processed to determine the first vehicle identifier; actions further include receiving the second image of the first vehicle in a message from the first device, the message including the first device identifier; actions further include: transmitting a third message to the first device, the third message including a request for confirming the first vehicle identifier, and receiving a fourth message from the first device, the fourth message indicating confirmation of the first vehicle identifier; actions further include: receiving a first signal, the first signal indicating that a second vehicle using the toll road facility is equipped with an identification device, the identification device associated with a balance account, and determining that the identification device is valid, and in response, collecting a second toll payment from the balance account; actions further include: receiving a second signal, the second signal indicating a second vehicle using the toll road facility is not equipped with a valid identification device, receiving a second image, the second image depicting the second vehicle, and processing the second image to determine a second vehicle identifier; actions further include: determining that the second vehicle identifier is provided in the first database, and in response: determining a second device identifier associated with the second vehicle identifier from the first database, transmitting a third message to a second device associated with the second device identifier, the third message including a request for approval to collect a second toll payment, and receiving a fourth message from the second device, the fourth message indicating disapproval of the second toll payment, and in response, receiving information associated with a registered owner of the second vehicle associated with the second vehicle identifier, and sending the owner an invoice; actions further include: receiving a fifth message from a second device of the owner, the fifth message indicating a registration request, and associating the second vehicle identifier with a second device identifier of the second device in the first database; actions further include detecting the first vehicle using the toll road facility; the first toll payment includes a plurality of unpaid toll fees; and the first device is associated with an account by the first service provider, the account being a prepaid and refillable account.

DETAILED DESCRIPTION

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 schema) that enables toll road users 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 schema of the present disclosure enable the TRO to collect toll fees from a service provider that provides data transfer services for the communication device.

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).

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.

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.

FIG. 1depicts an example system architecture100in accordance with implementations of the present disclosure. The example system architecture100includes a user102and a user-side device104, server systems106,112,114and a network108. In some examples, the device104can 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 ofFIG. 1, and as used by way of example throughout the remainder of the present disclosure, the user-side device104is provided as a MCD, such as a cellular telephone and/or a smartphone.

In some examples, the user-side device104and the server systems106,112,114communicate with one another over the network108. In some examples, the network108can 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.

In some examples, each server system106,112,114can include one or more computing devices and one or more machine-readable repositories, or databases. In the depicted example, the server system106is associated with a CSP, the server system112is 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 system114is 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 system106,112,114can include one or more computing devices and one or more machine-readable repositories, or databases.

For purposes of illustration, the depicted example includes a single TRO, a single VRA, a single CSP and a single user-side device104. 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.

With continued reference toFIG. 1, the user102can be a user of a vehicle110. In some examples, the vehicle110is 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 vehicle110. In some examples, and the VRA associates the vehicle identifier with the vehicle owner information (e.g., in a database provided with the server system112).

In some examples, the CSP provides communication and/or data transfer services for the user-side device104. In some examples, the user-side device104is associated with one or more unique device identifiers. An example, the device identifier can include a cellular telephone number. In some examples, the user102has 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 user102for charges incurred. In some examples, the user102pays 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, 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.

With continued reference toFIG. 1, a toll road facility (TRF)116is provided. In some examples, the TRF116is associated with the TRO (e.g., the TRO owns and/or operates the TRF116). 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 TRF116includes one or more cameras to capture images of vehicles using the free flow lanes and can transmit image files to the server system114for processing, as discussed in further detail herein. In some examples, the image files can be transmitted over a facility-specific network115(e.g., a LAN) and/or the network108.

In some implementations, the TRF116includes one or more sensing devices for detecting vehicle passage through the TRF116(e.g., through a free flow lane). In some examples, vehicles can be equipped with identification devices), which uniquely identify associated balance accounts for charging toll fees. Example identification devices can include radio frequency identification devices (RFIDs) (or “tags). 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.

As discussed in further detail herein, implementations of the present disclosure provide a protocol that includes a messaging scheme 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.

Referring now toFIGS. 2 and 3, implementations of the present disclosure will be described in further detail. For purposes of illustration, labels corresponding to the example system architecture100ofFIG. 1are used to present corresponding devices and/or systems.

FIG. 2depicts an example process200that can be executed in accordance with implementations of the present disclosure. In some examples, the example process200can be provided using one or more computer-executable programs executed using one or more computing devices (e.g., the server system114ofFIG. 1).

In some implementations, of the example process200includes 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.

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)).

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).

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.

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 schema). 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.

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.

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 456If OK & you accept terms, message: 12If 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.

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.

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.

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.

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.

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.

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.

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).

With continued reference toFIG. 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 toFIG. 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 toFIG. 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).

FIG. 3depicts an example process300that can be executed in accordance with implementations of the present disclosure. In some implementations, the example process300can be provided by one or more computer-executable programs executed using one or more computing devices (e.g., the server system114ofFIG. 1).

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 at320.

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 process300). 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).

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.

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.

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.

An example collection request message can include:Toll Passages: Mar. 22, 201310:02 am NB SH130@IH-10: $1.8015:47 pm SB SH130@IH-10: $1.80Total: $3.60To approve text 91, to reject text 96

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.

It is determined whether the collection request has been approved (312). If the collection request has not been approved, the example process300continues at320. 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.

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 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.

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.

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.

With continued reference toFIG. 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 retrieve based on the vehicle identifier and can include a registered owner of the vehicle associated with the vehicle identifier.

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 collection schema.

In some examples, 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 toFIG. 2). In some example, it can be determined that the RVO elects to pay by MCD, by receiving a vehicle image (e.g.,202ofFIG. 2).

In some implementations, the example process300depicted inFIG. 3includes 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.

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 process300proceeds 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).

Referring now toFIG. 4, a schematic diagram of an example computing system400is provided. The system400can be used for the operations described in association with the implementations described herein. For example, the system400may be included in any or all of the server components discussed herein. The system400includes a processor410, a memory420, a storage device430, and an input/output device440. Each of the components410,420,430, and440are interconnected using a system bus450. The processor410is capable of processing instructions for execution within the system400. In one implementation, the processor410is a single-threaded processor. In another implementation, the processor410is a multi-threaded processor. The processor410is capable of processing instructions stored in the memory420or on the storage device430to display graphical information for a user interface on the input/output device440.

The memory420stores information within the system400. In one implementation, the memory420is a computer-readable medium. In one implementation, the memory420is a volatile memory unit. In another implementation, the memory420is a non-volatile memory unit. The storage device430is capable of providing mass storage for the system400. In one implementation, the storage device430is a computer-readable medium. In various different implementations, the storage device430may be a floppy disk device, a hard disk device, an optical disk device, or a tape device. The input/output device440provides input/output operations for the system400. In one implementation, the input/output device440includes a keyboard and/or pointing device. In another implementation, the input/output device440includes a display unit for displaying graphical user interfaces.