Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
  • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/22—Payment schemes or models
  • G06Q20/28—Pre-payment schemes, e.g. "pay before"
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/327—Short range or proximity payments by means of M-devices
  • G06Q20/3278—RFID or NFC payments by means of M-devices
• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
  • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
  • G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
  • G07B15/063—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems using wireless information transmission between the vehicle and a fixed station

Definitions

• RFID RFID Applications, and more specifically to applications that allow for improved management and recharging of prepaid accounts.
• RFID is a technology that allows companies to develop applications in a variety of areas. At its core, RFID is a technology that allows for the identification of objects or people and to communicate information related to associated objects or people. Some of the major areas that RFID is enabling new applications include asset tracking, companies can put RFID tags on assets that are lost or stolen often, that are underutilized or that are just hard to locate at the time they are needed; manufacturing, RFID has been used in manufacturing plants for more than a decade.
• An RFID system comprises one or more tags or transponders that are somehow associated with an object or objects, and one or more readers or interrogators configured to read information out of the tag.
• the reader reads information by broadcasting a Radio Frequency (RF) signal over certain range.
• RF Radio Frequency
• a tag When a tag is within range of the reader and receives the signal, it can reflect that signal back to the reader in order to communicate with the reader.
• the reader may put certain commands on the RF signal, and the tag can respond by putting information stored in the tag onto the signal that is reflected back to the reader.
• RFID systems can employ various types of technology including active technology, semi-active technology and passive technology.
• Active and semi-active systems include a battery within the tag. In passive systems, no battery is included in the tag. Rather, the tag receives all the energy it needs from the received RF signal. Because passive tags do not include a battery, they can be made smaller, are less expensive than active or semi-active tags, and can also provide much more flexibility to design tags to meet various application and environmental requirements. While passive tags typically cannot communicate over as long a distance, the size, cost, and flexibility provided by passive tags make them much more attractive for many applications.
• RFID systems can also operate over many frequency ranges and in accordance with several communication protocols.
• a couple of the most common frequency ranges are the High Frequency (HF) band (13.56 MHz) and Ultra-High Frequency (UHF) band (865-928 MHz).
• HF systems can operate over shorter ranges, e.g., lOcm-lm, and at lower data rates, whereas the UHF systems can operate over longer ranges l-12m, and at higher data rates.
• NFC Near Field Communication
• HF Frequency Fidelity
• NFC is a set of standards for smartphones and similar devices to establish radio communication with each other by touching them together or bringing them into proximity, usually no more than a few inches.
• Present and anticipated applications include contactless transactions, data exchange, and simplified setup of more complex communications such as Wi-Fi.
• Communication is also possible between an NFC device and an unpowered NFC chip in a tag.
• NFC standards cover communications protocols and data exchange formats, and are based on existing radio-frequency identification (RFID) standards including ISO/IEC 14443 and FeliCa.
• RFID radio-frequency identification
• the standards include ISO/IEC 18092[4] and those defined by the NFC Forum, which was founded in 2004 by Nokia, Philips and Sony, and now has more than 160 members.
• the Forum also promotes NFC and certifies device compliance. It fits the criteria for being considered a personal area network.
• NFC builds upon RFID systems by allowing two-way communication between endpoints, where earlier systems such as contact-less smartcards were one-way only.
• NFC devices can also be used in contactless payment systems, similar to those currently used in credit cards and electronic ticket smartcards, and allow mobile payment to replace or supplement these systems.
• Google Wallet allows consumers to store credit card and store loyalty card information in a virtual wallet and then use an NFC-enabled device at terminals that accepts, for example, MasterCard PayPass transactions.
• the NFC Forum also promotes the potential for NFC-enabled devices to act as electronic identity documents and keycards. As NFC has a shorter range and supports encryption, it is generally better suited than earlier, less private RFID systems for exchanging sensitive data such as personal finance and identification.
• UHF technologies While there are many uses for HF technologies such as NFC, UHF technologies typically support longer range communication and higher data rates. Thus, UHF technology tends to excel in applications that include but is not limited to tolling and electronic vehicle registration, asset supervision, and supply chain management.
• a RFID system comprising a dual frequency RFID transponder.
• FIG. 1 A illustrates an embodiment of a system in which an account is managed
• FIG. IB illustrates an embodiment of a process in which an account is managed
• FIG. 2 illustrates an embodiment of a process for replenishing an account using a virtual wallet
• FIG. 3 illustrates an embodiment of a system in which an account is managed
• FIG. 4 illustrates an embodiment of a transponder used to manage an account
• FIG. 5 illustrates an embodiment of a UHF system
• FIG. 6 illustrates an embodiment of a HF system
• FIG. 7A illustrates the top view of an embodiment of a RFID-enabled license plate
• FIG. 7B illustrates the top view of an embodiment of a RFID-enabled license plate
• FIG. 7C illustrates the top view of an embodiment of a RFID-enabled license plate
• FIG. 8 illustrates the top view of an embodiment of a RFID-enabled license plate
• FIG. 9 illustrates an embodiment of a vehicle registration sticker that is used in conjunction with a RFID-enabled license plate
• FIG. 10 illustrates an embodiment of the placement of a reader with respect to a
• FIG. 11 illustrates an embodiment of a universal transponder.
• the embodiments disclosed herein can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
• these example embodiments, or any other implementations may be referred to as techniques.
• the order of the steps of disclosed processes may be altered.
• a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
• the term 'processor' refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
• Various embodiments of the systems and methods described herein are directed toward applications for a multi -frequency transponder.
• the various embodiments of the systems and methods described herein are directed toward applications for a dual frequency transponder that incorporates both UHF and HF capabilities, and is therefore able to operate over both the UHF band (e.g., 865-928 MHz) and the HF band (e.g., 13.56 MHz).
• a dual frequency transponder is used to enable immediate and on-the-spot prepayment of road tolls enforced through Electronic Toll Collection (ETC) systems.
• ETC Electronic Toll Collection
• ETC systems eliminate traffic delays on toll roads by automating toll collection and obviating protracted stops at manual toll booths.
• ETC billing mechanism i.e., billed to users periodically and/or a later date
• ETC billing mechanism is to automatically deduct the toll charges from prepaid debit accounts.
• an ETC system must first identify a passing vehicle before it can electronically debit the account of registered vehicle owner. For vehicle identification, most ETC systems operating today (e.g., E-ZPass®) rely on RFID technology.
• ETC systems issue RFID transponders or tags that are then registered or activated to link to specific vehicle owner accounts. For instance, in order for a user, Alice, to gain access to an ETC service, she will initially have to set up a toll account with an appropriate transit or toll authority (e.g., FasTrak® in the San Francisco Bay Area), and then carry a registered or activated RFID transponder in or on her vehicle. Meanwhile, most toll plazas have RFID reader equipment installed on at least some toll gates. As Alice's vehicle passes through a toll gate on the San Francisco-Oakland Bay Bridge, the onboard FasTrak® transponder communicates to a RFID toll reader a unique radio signature identifying the vehicle. Based on this unique radio signature, the ETC system can then determine the account (i.e., Alice's) from which to deduct the amount of the toll.
• an appropriate transit or toll authority e.g., FasTrak® in the San Francisco Bay Area
• toll plazas have RFID reader equipment installed
• Some prepaid toll accounts are set up to be automatically replenished whenever the balance falls below a certain threshold. For example, if Alice subscribes to a FasTrac® credit card account, a replenishment amount equaling her average monthly usage (determined based on the previous 90 days of use) is charged to the credit card linked to the account whenever the account's balance falls below a threshold of $15. Most users, however, wants autonomy over their prepaid toll account balances and would prefer to recharge their prepaid toll account at their own discretion. Control over when and how much to recharge a toll account is especially attractive to users who incur toll charges on an infrequent, intermittent, or irregular basis.
• NFC Near Field Communication
• the resulting dual frequency transponder in various embodiments, is capable of communicating with NFC-enabled devices as well as UHF RFID readers.
• the dual frequency transponder when implemented as a toll transponder for use in an ETC system, can communicate with both a user's NFC-enabled device (e.g., smartphone) and the typical UFIF RFID reader equipment found at toll gates.
• NFC-enabled smartphone is equipped with an embedded NFC reader module that can communicate with other NFC devices, including but not limited to other NFC-enabled smartphones, NFC POS terminals, and NFC transponders and tags.
• NFC devices including but not limited to other NFC-enabled smartphones, NFC POS terminals, and NFC transponders and tags.
• Bluetooth® which generally require manual device discovery and/or pairing
• two NFC devices can detect and automatically initiate a connection with one another as soon as they are within range (e.g., 4cm or less).
• an unlocked Google Android® smartphone will scan for NFC tags, analyze any discovered NFC tags, categorize data from the NFC tags, and then launch the appropriate application(s) to handle each NFC tag.
• FIG. 1A illustrates an embodiment of a System 100 in which an account is managed.
• System 100 includes a Transponder 110.
• Transponder 110 is a dual frequency transponder that communicates with Device 120 and Reader 130 using different frequency bands.
• Transponder 110 is a dual frequency transponder that can operate over both the HF and UHF band.
• Transponder 110 can be embedded, integrated, or otherwise included in a vehicle license plate.
• Transponder 110 is an active or semi-active device that relies on a built-in power source (e.g., batteries) to transmit its signals.
• Transponder 110 is a passive device that collects energy from interrogating signals from Device 120 and Reader 130.
• Transponder 110 communicates with Device 120.
• Device 120 is a NFC-enabled device (e.g., Android® smartphone) and Transponder 110 communicates with Device 120 using the HF band.
• Transponder 110 also communicates with Reader 130.
• Reader 130 is a UHF RFID reader device and Transponder 110 communicates with Reader 130 using the UFH band.
• Reader 130 can be a type of RFID reader device that is typically installed at an electronic toll gate.
• Reader 130 is preferably placed in the road, underneath passing vehicles as opposed to in an overhead gantry.
• Device 120 communicates with Transponder 110 in order to manage a toll account, and to recharge the toll account instantaneously and on-the-spot.
• Application 121 is installed on Device 120.
• physical interactions between Transponder 110 and Device 120 triggers or activates Application 121.
• touching or tapping Transponder 110 and Device 120 together immediately opens Application 121 on Device 120.
• Application 121 opens immediately when Device 120 is brought within close proximity of Transponder 110.
• physical interactions between Transponder 110 and Device 120 further allow Device 120 to scan, read, or otherwise retrieve information stored on Transponder 110.
• Device 120 by touching, tapping, or otherwise positioning Transponder 110 and Device 120 together, Device 120 is able to read the information that is stored on Transponder 110.
• Device 120 determines to launch Application 121 automatically based on at least some of the information read from Transponder 110.
• physical interaction between Device 120 and Transponder 110 will initiate an authentication process.
• a user before Device 120 is able to access, for example, prepaid toll account information, a user must provide the proper credentials (e.g., biometrics, username, password).
• Application 121 is able to use at least some of the information read from Transponder 110 to obtain information associated with the toll account, including but not limited to account status and account balance.
• Application 121 communicates with ETC Server 170 over Network 140.
• Network 140 comprises one or more of a wired network, a wireless network, a local area network, a wide area network, the Internet, or any other appropriate network.
• Application 121 uses web or application services provided by ETC Server 170 in order to obtain prepaid toll account information such as account status and balance.
• ETC Server 170 comprises one or more of a wired network, a wireless network, a local area network, a wide area network, the Internet, or any other appropriate network.
• Application 121 uses web or application services provided by ETC Server 170 in order to obtain prepaid toll account information such as account status and balance.
• a user can gain immediate access to latest prepaid toll account information (e.g., status, balance).
• Application 121 additionally provides a user interface for recharging a toll account.
• Application 121 provides one or more GUI components (e.g., text areas or fields, radio buttons, checkboxes, drop-down menu) allowing a user to select or to input, for example, an recharge amount, a payment method (e.g., a credit card selection), and security or authentication credentials for the virtual wallet.
• Application 121 is integrated with a virtual wallet (e.g., Google WalletTM) feature on Device 120.
• Application 121 interacts with the virtual wallet (e.g., Google WalletTM) to replenish the user's prepaid toll account.
• Application 121 also communicates with both E-Wallet Server 150 and Payment Processor Server 160 over Network 140.
• Application 121 requests payment information (e.g., a credit card number) from E-Wallet Server 150 so that it can then request Payment Processor Server 160 to submit an appropriate recharge amount to ETC Server 170 to replenish the user's prepaid toll account.
• payment information e.g., a credit card number
• the systems and the methods described herein enable prepaid toll accounts to be managed and replenished instantaneously and on-the-spot. For instance, in various embodiments, a user is no longer required to seek out a POS station but can instead recharge his or her prepaid toll account while on the road and from inside the vehicle.
• Transponder 110 also communicates with Reader 130.
• Reader 130 comprises a UHF RFID reader that is capable of reading information stored on Transponder 110 using the UHF (865-928 MHz) band. As shown in FIG. 1A, in various embodiments, Reader 130 is a RFID reader installed at a toll gate. Furthermore, as FIG. 1A shows, Reader 130 communicates with ETC Server 170 over Network 140. In some embodiments, information that Reader 130 reads from Transponder 110 is transmitted to ETC Server 170 via Network 140. As will be described in more detail below, in various embodiments, information stored on Transponder 110 can link, correspond, or otherwise provide access to other information, such as information that is stored elsewhere and remotely on a network server. For example, in various embodiments, ETC Server 170 uses the information from Transponder 110 to identify the vehicle and to apply a toll charge to the correct account.
• FIG. IB illustrates an embodiment of a Process 100 in which an account is managed.
• Process 100 is performed as a result of physical interactions between Transponder 110 and Device 120 described with respect to FIG. 1 A.
• a NFC-enabled device such as Device 120 (e.g., Android® smartphone) is able to read the information stored on Transponder 110.
• Device 120 e.g., Android® smartphone
• a UHF RFID toll reader such as Reader 130 is also able to read the information stored on Transponder 110.
• account information is accessed based on the information stored on the dual -frequency transponder.
• the information stored on Transponder 110 links, corresponds, or otherwise provides access to account information.
• the information stored on Transponder 110 links corresponds, or otherwise provides access to account information that is stored at a remote server.
• the information stored at the remote server includes prepaid toll account information including but not limited to account status and balance.
• action includes communicating the account information stored at the remote server (e.g., account status, account balance) to a user of Device 120 via Application 121.
• account information stored at the remote server e.g., account status, account balance
• the user of Device 120 can also use Application 121 to recharge the toll account.
• the user of Device 120 can replenish the toll account through a virtual wallet that is integrated with Application 121.
• a UFIF RFID toll reader is also able to read the information stored on Transponder 110.
• the UHF RFID toll reader can be configured to provide some or all of this information to a ETC system.
• the ETC system can determine the account from which to deduct a toll charge.
• the recharging process can be initiated by simply bringing an NFC-enabled device (e.g., Device 120) within the range of a dual frequency transponder (e.g., Transponder 110).
• the NFC-enabled device e.g., Device 120
• the NFC-enabled device immediately launches an application (e.g., Application 121) that is integrated with a virtual wallet (e.g., Google WalletTM).
• an application e.g., Application 121
• a virtual wallet e.g., Google WalletTM
• scanning a dual frequency toll transponder with a NFC-enabled device triggers an application that is configured to interact directly with the virtual wallet.
• the application provides a user interface for a user to select or input various options (e.g., amount, credit card, credentials) to recharge a toll account.
• functions and features of the virtual wallet are integrated into the application using one or more appropriate Application Programming Interfaces (APIs).
• APIs Application Programming Interfaces
• Google WalletTM the Android® Software Development Kit (SDK) offers the following three basic APIs: Google Wallet online commerce API, Google Wallet for digital goods API, and Google Checkout API.
• FIG. 2 illustrates an embodiment of a Process 200 for recharging a toll account using a virtual wallet.
• Process 200 is performed by an application, such as Application 121 described with respect to FIG. 1A.
• Process 200 is performed at 106 of Process 100 described with respect to FIG. IB.
• Process 200 can be performed by the application to recharge a toll account using payment information obtained directly from Google WalletTM.
• the application is configured to exchange payment information with the Google WalletTM backend server.
• the application and the Google WalletTM backend server exchange payment information using signed JavaScript Object Notation (JSON) data objects called JSON Web Tokens (JWTs).
• JSON JavaScript Object Notation
• the application can offer users the option to recharge their prepaid toll account using Google WalletTM.
• using a virtual wallet such as Google WalletTM further expedites the recharging process since users are able to avoid manually inputting payment information (e.g., credit card number, billing address, etc.).
• payment information e.g., credit card number, billing address, etc.
• Bob indicates that he would like to recharge his prepaid toll account by adding $10 to the account, he can then select or click on a "Buy with Google" button to complete or finalize the recharging transaction almost instantaneously.
• selecting to pay with a virtual wallet such as by clicking on the "Buy with Google" button triggers Process 200.
• masked wallet information is requested.
• the application sends to the Google WalletTM backend server a masked wallet request JWT.
• masked wallet information comprises a Java object containing a masked or partially hidden version of Bob's credit card number.
• masked wallet information can further include Bob's shipping address.
• a masked wallet object is received.
• the Google WalletTM backend server in response to the request from the application, the Google WalletTM backend server returns to the application a masked wallet response JWT.
• the application can display an order review page or screen to Bob based on the masked wallet information.
• a full wallet is requested.
• the application after receiving the masked wallet object at 204, the application will then need full wallet information to complete Bob's order. As such, in some embodiments, the application then sends to the Google WalletTM backend server a full wallet request JWT. At 208, full wallet information is received. In various embodiments, the Google WalletTM backend server responds to the request by providing a full wallet response JWT to the application. In various embodiments, the full wallet information includes details of a single-use virtual credit card for the transaction. At 210, the single-use virtual credit card is transmitted. In various embodiments, the application passes the single-use virtual credit card provided by Google WalletTM in the full wallet to a merchant server (e.g., Payment Processor Server 160 described with respect to FIG.
• a merchant server e.g., Payment Processor Server 160 described with respect to FIG.
• transaction status is received.
• the merchant server processes the payment and notifies the application of the status of the transaction (e.g., success or failure).
• a status notification object is transmitted.
• the application based on the status notification from the merchant server (e.g., success or failure), the application then creates and sends a transaction status JWT to the Google WalletTM backend server.
• the application displays a confirmation screen informing Bob that $10 has been added to his prepaid toll account.
• the various embodiments of the methods and systems described herein are directed toward using a dual frequency transponder to manage and replenish a toll account.
• the dual frequency transponder can communicate with both a NFC-enabled device and a UHF RFID reader.
• data stored on the dual frequency transponder links corresponds, or otherwise provide access to a toll account.
• both NFC-enabled devices e.g., Android® smartphones
• UHF RFID readers e.g., common types of toll readers
• various embodiments of the systems and methods enable an account to be managed and recharged instantly and on-the-spot.
• bringing an NFC-enabled device e.g., Device 120
• a dual frequency transponder e.g., Transponder 110
• the application can provide the latest prepaid toll account information (e.g., status, balance).
• the application is integrated with a virtual wallet (e.g., Google WalletTM) thereby enabling a user to recharge the toll account instantly and on-the-spot.
• Bob uses his Android® smartphone to scan the dual frequency transponder and is subsequently able to add $10 to his prepaid toll account.
• the information stored in the dual frequency transponder links, corresponds, or otherwise provides access to an account.
• a NFC- enabled device reads data that is stored on an RFID data storage medium (e.g., a dual frequency transponder) and then uses this data to access additional data that is stored at a remote server.
• reading or scanning the information stored in the dual frequency transponder enables the application to access a designated memory area at a remote server (e.g., ETC Server 170).
• the application is then able to retrieve, for example, prepaid toll account information from the remote server.
• the application is also able to update the toll account information stored at the remote server, including but not limited to by submitting a recharge payment that alters the status or balance of the toll account.
• FIG. 3 illustrates an embodiment of a System 300 in which an account is managed.
• User 32 operates Device 10, which is a NFC-enabled device such as an Android® smartphone.
• Application 30 is an application that permits User 32 to manage and replenish a toll account, including by providing current account information (e.g., status, balance) and options to replenish the toll account.
• Device 10 includes a NFC RFID Reader 8 that is capable of reading data stored in RFID Storage Medium 4.
• RFID Storage Medium 4 is a dual frequency transponder such as Transponder 110 described with respect to FIG. 1A or Transponder 400 described with respect to FIG. 4.
• Application 30 is installed on Device 10.
• NFC RFID Reader 8 when NFC RFID Reader 8 reads or scans data from RFID Storage Medium 4, Device 10 can launch Application 30 automatically based on this data. Otherwise stated, in some embodiments, Application 130 can be launched when User 32 brings Device 10 within sufficient range of RFID Storage Medium 4 for NFC RFID Reader 8 to read or scan data from RFID Storage Medium 4. In other embodiments, Application 130 is not already installed on Device 10. In those embodiments, data read or scanned from RFID Storage Medium 4 directs Device 10 to a link to download and install Application 130.
• RFID Storage Medium 4 includes a
• NFC RFID Reader 8 is configured to read or scan the data stored on RFID Data Record 24.
• NFC RFID Reader 8 directs a request to RFID Storage Medium 4.
• RFID Storage Medium 4 releases the data stored on RFID Data Record 24 to NFC RFID Reader 8, In some embodiments.
• User 32 must be authenticated (e.g., biometrics, username, password) before RFID Storage Medium 4 releases its data to NFC RFID Reader 8.
• Application 30 generates uses the data released from RFID Data Record 24 to generate access rights for Additional Data 22 that stored in Data Memory Area 20 of a Remote Server 18.
• Additional Data 22 can include account information (e.g., status, balance) with respect to the toll account.
• Remote Server 18 can be a server associated with an ETC system, such as ETC Server 170 described with respect to FIG. 1 A.
• Application 30 requests for Additional Data 22 from Remote Server 18 by sending, for example, access rights to Remote Server 18 over Network 16.
• Remote Server 18 transmits Additional Data 22 to Device 10 via Network 16.
• Application 30 can then provide, with or without further processing or analysis, Additional Data 22 to User 32.
• FIG. 4 illustrates an embodiment of a Transponder 400 used to manage an account.
• Transponder 400 is a multi -frequency or frequency- independent transponder.
• Transponder 400 is a dual frequency transponder that operates over both the HF (e.g., 13.56 MHz) and UHF (e.g., 865-928 MHz) band.
• HF e.g., 13.56 MHz
• UHF e.g., 865-928 MHz
• Transponder 400 shown in FIG. 4 can be used to implement Transponder 110 described with respect to FIG. 1A.
• Transponder 400 is capable of communicating with both a NFC-enabled device and a UHF RFID reader.
• Transponder 400 when a NFC-enabled device such as an Android® smartphone is brought within the range of Transponder 400, the NFC-enabled device can respond by automatically launching an application (e.g., Application 121 described with respect to FIG. 1 A) that enables a quick and on-the-spot recharge of a toll account.
• an application e.g., Application 121 described with respect to FIG. 1 A
• a UHF RFID reader installed at a toll gate can use information scanned from Transponder 400 to determine the correct prepaid toll account from which to deduct a toll charge.
• Transponder 400 includes a base layer and at least one radio frequency device disposed upon the base layer.
• the radio frequency device comprises at least one chip and at least one antenna that are in electrically coupled with the chip.
• Transponder 400 can include a frequency-independent chip.
• Transponder 400 can include a single manufactured silicon chip that is configured, through proper connections and match to an appropriate antenna, to operate using any of the relevant frequencies (e.g., 13.56 MHz and 915 MHz) assigned to Transponder 400.
• Transponder 400 can include a multi -frequency (e.g., dual frequency) chip.
• Transponder 400 includes a chip that is designed and characterized to operate with a specific antenna at several (e.g., two) different frequencies.
• Transponder 400 further includes an
• Analog Control Unit 410 which is a dual interface with a combination of two frequencies.
• Analog Control Unit 410 includes a HF System 411 and a UHF System 412, both described in more detail below.
• UHF System 412 operates over the 915 MHz band and is used for communicating with UHF RFID readers, including but not limited to conventional UHF RFID toll readers.
• UHF System 412 includes Antenna 413, which can be a dipole antenna.
• HF System 411 is used for communicating with NFC- enabled devices, such as Android® smartphones.
• the HF System 411 includes Antenna 414, which can be a coil antenna constructed from a helix of insulated wire.
• Transponder 400 can further include Digital Control
• Analog Control Unit 401 comprises a continuous-time system. That is, in various embodiments, Analog Control Unit 401 comprises a system that is continuous in both time and magnitude. Furthermore, in various embodiments, Analog Control Unit 401 inputs and outputs analog signals. A signal is considered analog if it is defined for every point in time (i.e., continuous-time) and is able to take any real magnitude value within its range.
• Digital Control Unit 420 comprises a discrete-time and quantized system. In various embodiments, Digital Control Unit 420 takes in digital input signals and produces digital output signals.
• a digital signal is only defined for particular points in time (i.e., discrete-time) and can only take on certain quantized values (e.g., 0s and Is in a binary system).
• Analog Control Unit 410, Digital Control Unit 420, and Memory 430 are all components on a single integrated RFID circuit chip.
• FIG. 5 illustrates an embodiment of an UHF System 500.
• UHF System 500 can be used to implement UHF System 412 described with respect to FIG. 4.
• UHF System 500 can be used to implement the UHF component of a dual frequency transponder, such as Transponder 110 described with respect to FIG. 1A.
• UHF System 500 operates over a UHF (865-928 MHz) band. As shown in FIG. 5, UHF System 500 uses the 915 MHz or 2.45 GHz band.
• a dual frequency transponder that incorporates UHF System 500 is capable is interacting with a UHF RFID reader. Many ETC systems have UHF RFID readers installed at toll gates.
• data transmitted to the UHF RFID reader includes data (e.g., a unique radio signature) that links, corresponds, or otherwise provides access to the toll account associated with each passing vehicle. As such, in various embodiments, this data enables the ETC system to identify or determine the toll account to which to apply the toll charge.
• UHF System 500 includes AC/DC Converter 510, Power
• AC/DC Converter 510 receives an alternating current (AC) and converts it to a direct current (DC).
• Power Supply Control Unit 520 is configured to regulate voltage and current to protect UHF System 500 fluctuations in power (e.g., power surge).
• Instruction Sequencer 530 queues instructions that are directed to Memory 540.
• Memory 540 comprises an EEPROM (Electrically Erasable Programmable Read-Only Memory) that stores data, such as instructions from Instruction Sequencer 530.
• EEPROM Electrical Erasable Programmable Read-Only Memory
• FIG. 6 illustrates an embodiment of a HF System 600.
• HF System 600 In various embodiments,
• HF System 600 can be used to implement HF System 411 described with respect to FIG. 4. Furthermore, in various embodiments, HF System 600 can be used to implement the HF component of a dual frequency transponder, such as Transponder 110 described with respect to FIG. 1A. As shown in FIG. 6, HF System 600 uses the 13.56 MHz band.
• a dual frequency transponder that incorporates HF System 600 is capable of interacting with a NFC-enabled device (e.g., Android® smartphone) when the dual frequency transponder touches, taps, or is otherwise brought within the range of the NFC-enabled device. For example, bringing an Android® smartphone within the range of the dual frequency transponder activates an Android BeamTM feature on the smartphone.
• a NFC-enabled device e.g., Android® smartphone
• the Android BeamTM feature allows data to be transferred one NFC-enabled device to another NFC-enabled device via NFC.
• Android BeamTM allows data to be transferred from the dual frequency transponder to an Android® smartphone via NFC.
• data from the dual frequency transponder triggers the launch of an appropriate application on the Android® smartphone to handle the data.
• a NFC-enabled device e.g., Android® smartphone
• an integrated HF component e.g., HF System 600
• an application to recharge a toll account launches automatically.
• data read from the dual frequency transponder links corresponds, or otherwise provide access to a toll account.
• the toll account has a deficient balance and needs to be recharged before a corresponding vehicle can pass through an ETC toll gate.
• the application through integration with a virtual wallet (e.g., Google WalletTM), enables the toll account to be recharged instantly and on-the-spot.
• a virtual wallet e.g., Google WalletTM
• HF System 600 includes Modulator 610, AC/DC Converter
• Modulator 610 is configured to receive baseband signals from an antenna, such as coil Antenna 414 described with respect to FIG. 4.
• AC/DC converter 612 is configured to receive and convert an alternating current (AC) to a direct current (DC).
• Codifier 614 is configured to encode the baseband signals received by Modulator 610 so that the signals can be utilized by another device or protocol, including Instruction Sequencer 620.
• Decoder 616 is configured to decode information from Codifier 614 so that it may be used by another device or display.
• Instruction Sequencer 620 is configured to queue instructions destined for Memory 626.
• Security Administrator 622 is configured to validate the cryptographic keys sent to Cryptographic Block 624.
• Cryptographic Block 624 or Memory 626 can be configured store the security keys that, for example, have been validated by Security Administrator 622 and that can be used to control (e.g., grant, deny) access to the dual frequency transponder's memory or certain content therein.
• Power Supply Control Unit 618 is configured to regulate voltage and current in order to protect HF System 600 from power fluctuations (e.g., power surges).
• the various embodiments of the systems and methods described herein are directed toward the use of a dual frequency transponder (e.g., Transponder 110 described with respect to FIG. 1A and Transponder 400 described with respect to FIG. 4) to manage and recharge an account.
• the dual frequency transponder provides information that enables the application of both toll charges and reload payments to the appropriate prepaid toll account.
• the dual frequency transponder is configured to interact both with the UHF RFID toll readers and with a user's NFC-enabled device, the dual frequency transponder should preferably be set in a location that is convenient and accessible for scanning by both the UHF RFID toll readers and the user's NFC-enabled device.
• the dual frequency transponder can be a sticker (e.g., a self-adhesive decal that can be placed on an automobile window, windshield, or license plate), a clamshell card, or an encapsulated device (e.g., in the housing of a rear-view mirror, headlights or taillights, the vehicle's front or rear bumpers, or in any non-conductive component of the vehicle).
• a sticker e.g., a self-adhesive decal that can be placed on an automobile window, windshield, or license plate
• a clamshell card e.g., a clamshell card
• an encapsulated device e.g., in the housing of a rear-view mirror, headlights or taillights, the vehicle's front or rear bumpers, or in any non-conductive component of the vehicle.
• the dual frequency transponder can also be embedded in the vehicle's license plate.
• vehicle license plates are most commonly made from metal (e.g., aluminum). Direct and uninsulated contact between a transponder (single or multi- frequency) and a metal license plate (e.g., applying the transponder directly onto the metal license plate) can short or severely detune the transponder's antenna(s) (e.g., Antenna 413 and Antenna 414 described with respect to FIG. 4), rendering the transponder virtually unreadable.
• a transponder is embedded in a metal license plate in ways that neither compromise the performance of the transponder's antenna(s) nor add undesirable bulk to the license plate's usual dimensions.
• a RFID-enabled license plate is configured to resonate at multiple frequencies (e.g., HF and UHF bands).
• a resonator for the transponder is formed from the license plate itself if the license plate is metal. In other embodiments, whether the plate is metal or non-metal, the resonator can also be formed from a metalized layer (e.g., retro-reflective material, holographic foil, or any other appropriate metallic substrate) covering the license plate.
• FIG. 7A illustrates the top view of an embodiment of a RFID-Enabled License
• RFID-Enabled License Plate 700 includes a metal Plate 710. In various embodiments, RFID-Enabled License Plate 700 can be configured to include one or more slots, which are open areas that are cut or punched out of Plate 710. In some embodiments, RFID-Enabled License Plate 700 can be configured to include multiple slots. As shown in FIG. 7A, in some embodiments, RFID-Enabled License Plate 700 includes Slot 720 and Slot 730. In various embodiments, both Slot 720 and Slot 730 can be filled with a non-metal material. In various embodiments, the non-metal material can be stuffed, extruded, or otherwise deposited into Slot 720 and Slot 730.
• a RFID Strap 740 can be positioned across Slot 730 as illustrated.
• RFID Strap 740 includes a RFID chip as well as contacts that are connected to or capacitively coupled with Plate 710.
• RFID Strap 740 can include a RFID chip and an antenna, wherein the antenna is inductively coupled with Plate 710.
• the respective and relative dimensions, spacing, and location of Slots 720 and 730 are configured such that the slot antenna formed from Plate 710, Slots 720 and 730, and Strap 740 will resonate at multiple desired frequencies.
• a RFID- enabled license plate can also include just a single slot configured to resonate at a single frequency.
• FIG. 7B illustrates the top view of another embodiment of an RFID-Enabled
• RFID-Enabled License Plate 700 includes a Plate 710 that is constructed out of metal. As shown in FIG. 7B, in various embodiments, RFID- Enabled License Plate 700 can be configured to include a single Slot 720, which is cut or punched out of Plate 710. In various embodiments, Slot 720 can be stuffed, extruded, or otherwise deposited with a non-metal material that remains flush with respect to both the front and rear surfaces of Plate 710. In the embodiment shown in FIG. 7B, an RFID Strap 730 is positioned over Slot 720. In various embodiments, RFID Strap 730 includes a RFID Chip 740 and Contacts 750.
• Contacts 750 can be connected to Plate 710 through solder, adhesive paste, or both. In some embodiments, Contacts 750 are capacitively coupled with Plate 710. Depending on the embodiment, RFID Strap 730 can be placed on either the front surface or the rear surface of Plate 710. Configured according to FIG. 7B, the entire Plate 710 becomes a slot antenna coupled with the RFID Chip 740, which is less sensitive to the detuning effects of a metal car frame.
• FIG. 7C illustrates the top view of another embodiment of RFID-Enabled License
• RFID-Enabled License Plate 700 comprises a metal Plate 710 that includes a Slot 720, which is an open area that has been cut or punched out of Plate 710.
• an RFID strap e.g., RFID Strap 740 described with respect to FIG. 7A and 7B
• RFID Transponder Module 730 is placed directly inside of Slot 720 as shown in FIG. 7C.
• RFID Transponder Module 730 includes an RFID Chip 740 that is coupled with a Feeding Loop 750.
• Slot 720 is positioned such that Feeding Loop 750 is either capacitively coupled with Plate 710.
• Feeding Loop 750 can be inductively coupled with Plate 710.
• RFID Transponder Module 730 can be made sufficiently thin such that even when RFID Transponder 730 is installed within Slot 720, it creates a substantially planar surface with respect to Plate 710.
• a RFID-enabled license plate can include a transponder that will not function absent a valid and properly positioned vehicle registration sticker.
• the transponder can be intentionally tuned to a lower frequency (e.g., less than 915 MHz) and therefore cannot be properly read by a UHF RFID reader.
• applying a valid vehicle registration sticker in the correct position on the RFID-enabled license plate tunes the transponder to the correct and operational frequency (e.g., 915 MHz) so that the transponder can be read by a UHF RFID reader.
• the vehicle registration sticker is fabricated from or otherwise includes one or more metallic or other conductive materials.
• FIG. 8 illustrates an embodiment of a RFID-Enabled License Plate 800.
• RFID-Enabled License Plate 800 includes a metal Plate 810 and a RFID Module 820.
• RFID-Enabled License Plate 800 comprises an RFID Booster 830.
• RFID Booster 830 can be a slot antenna formed from Plate 810, RFID Module 820, and one or more properly sized and positioned slots in Plate 810.
• RFID Module 820 is intentionally tuned to a lower, inoperable frequency.
• a valid Vehicle Registration Sticker 840 must be applied in a proper location on Plate 810 in order for RFID Module 820 to function properly (e.g., to be scanned or read by a UHF RFID toll reader). As will be described in more detail below, applying Vehicle Registration Sticker 840 in the correct location on RFID-Enabled License Plate 800 tunes RFID Module 820 to the proper frequency band.
• FIG. 9 illustrates an embodiment of Vehicle Registration Sticker 900 which is used in conjunction with RFID-Enabled License Plate 800 as described in FIG. 8.
• Vehicle Registration Sticker 900 can be used to implement Vehicle Registration Sticker 840 described with respect to FIG. 8.
• the back of Vehicle Registration Sticker 900 includes a Loop 910.
• Loop 910 couples to a RFID transponder and tunes the RFID transponder to the proper frequency band for operation.
• Vehicle Registration Sticker 900 can comprise RFID Module 820 (i.e., a chip and an antenna). In those embodiments, placement of the Vehicle Registration Sticker on RFID-Enabled License Plate 800 couples Vehicle Registration Sticker 900 with RFID Booster 830.
• Vehicle Registration Sticker 900 can include a single frequency (e.g., HF or NFC) transponder.
• FIG. 8 shows that Vehicle Registration Sticker 900 is placed directly over RFID Module 820, in embodiments where Vehicle Registration Sticker 900 is composed of or otherwise includes conductive material, RFID Module 820 do not have to be directly underneath Vehicle Registration Sticker 900.
• a vehicle registration sticker that is used in conjunction with a RFID-enabled license plate can further include or be constructed out of a material that gradually degrades as the vehicle's registration approaches expiration. In this manner, an up-to-date vehicle registration sticker is able to tune a RFID transponder in the RFID-enabled license plate to the proper frequency while an expired vehicle registration sticker cannot. Consequently, a vehicle cannot successfully pass through a checkpoint unless the vehicle is also properly registered and is displaying a current vehicle registration sticker.
• Vehicle registration stickers are very often made out of a metallic material (e.g., retro-reflective foil). Therefore, in some embodiments, the vehicle registration sticker can be made out of a retro-reflective material that degrades over time. In another embodiment, the loop on the back of the vehicle registration sticker can be made out of a material that degrades over time. Finally, in some embodiments, the adhesive used to bond the vehicle registration sticker to a RFID-enabled license plate can degrade over time.
• a RFID-enabled license plate e.g., RFID-Enabled
• License Plate 700 and 800 comprises a dual frequency transponder (e.g., Transponder 110, Transponder 400), the RFID-Enabled license plate is able to communicate with a NFC-enabled device and with a UHF RFID reader device.
• the RFID- enabled license plate is designed to be read as a vehicle passes through a toll gate.
• the dual frequency transponder is embedded, integrated, or otherwise included in the vehicle's license plate, it would be preferable to install or place the toll readers in the road, rather than in overhead gantries as in conventional ETC systems.
• FIG. 10 illustrates an embodiment of the placement of a Reader 1000 with respect to a RFID-enabled license plate.
• the maximum height from which a transponder can be read is approximately 3.5 feet above the surface of the pavement.
• Reader 1000 is embedded at least 4 inches below the surface of the pavement.
• the transponder in a RFID-enabled license plate needs to include a 192-bit Tag Identification (TID) memory.
• TID Tag Identification
• the maximum speed at which Reader 1000 can successfully read a dual frequency transponder with a 192-bit TID memory that is embedded in a license plate attached to a passing vehicle is 140 kilometers or 87 miles per hour.
• FIG. 11 illustrates an embodiment of a universal transponder 1100. Referring to
• the universal transponder 1100 can provide multiple functionalities including, for example, but not limited to, short range connectivity (e.g., NFC, Bluetooth®) with another device (e.g., smartphone), camera, credit card reader (e.g., Square®), audio speaker, and remote control (e.g., garage door opener).
• the universal transponder 1100 can have a metal casing that can act as an antenna (e.g., in the UHF band).
• the universal transponder is able to interface with both NFC/HF and UHF systems, and can be used to manage an account.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Accounting & Taxation (AREA)
• Strategic Management (AREA)
• General Business, Economics & Management (AREA)
• Finance (AREA)
• Devices For Checking Fares Or Tickets At Control Points (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=57072941

Family Applications (1)

Country Status (3)

Families Citing this family (1)

Family Cites Families (2)

• 2016
  • 2016-04-11 MX MX2017012923A patent/MX2017012923A/es unknown
  • 2016-04-11 WO PCT/US2016/026983 patent/WO2016164924A2/fr active Application Filing
  • 2016-04-11 EP EP16777505.5A patent/EP3281152A4/fr not_active Withdrawn

Also Published As

Similar Documents

Legal Events