System and method for tire RFID authentication using permanently locked memory

Abstract

Systems and methods are disclosed for secure authentication of identification information of a tire having an associated RFID tag. Identification information from a tire source (e.g., manufacturer) is securely stored, and includes first and second codes associated with respective first and second memory areas, wherein at least the second memory area is permanently locked at the tire source such that the second code is persistent. Upon receiving a tire authentication request at a hosted server platform, the request comprising first and second codes identified via an RFID reader device, a matching first code is automatically identified in data storage, wherein the corresponding second code is retrieved from data storage and compared with the second code of the request to ascertain an authentication status of an RFID tag read by the RFID reader. Messages comprising the authentication status are then transmitted in real time with respect to authentication request.

Description

SYSTEM AND METHOD FOR TIRE RFID AUTHENTICATION USINGPERMANENTLY LOCKED MEMORYFIELD OF THE INVENTION

[0001] The present invention relates generally to authentication of products having radio frequency identification (RFID) tags, and more particularly to anti-counterfeiting measures for products such as tires using two-factor or three-factor authentication via a secure remote serverbased (e.g., cloud) computing and storage platform.BACKGROUND

[0002] Conventional applications are known wherein RFID tags are integrated with or otherwise mounted on tires, for example enabling the identification and tracking of individual tires across maintenance hubs and other facilities throughout their respective lifetimes.

[0003] A passive RFID tag as known in the art includes different memory areas, which may include at least Electronic Product Code (EPC) memory and tag identifier (TID) memory. In some cases, additional memory areas may include reserved (access) memory, and / or user memory. TID memory is conventionally used only to store a unique tag ID number by the manufacturer, which is permanent in nature. Reserved memory may store an access password, for example of 32 bits, to lock and unlock the write capabilities of an RFID tag. The EPC memory is where an SGTIN- 96 encoding scheme is implemented. The SGTIN-96, after being converted from hex to numeric, offers a twelve-digit number to be filled with a serial number formatted by the manufacturer.

[0004] Unfortunately, any tire can theoretically be copied, and then re-written to another tag or tire, wherein it would substantially appear to be an original equipment manufacturer (OEM) tire. As the market evolves, for example, it is possible that forgers could have access to third party chip manufacturers who are willing to re-create TID serial numbers on the chip.

[0005] It would therefore be desirable to provide anti -counterfeiting or associated authentication techniques to proactively counter such challenges.BRIEF SUMMARY

[0006] A system and method as disclosed herein may address the above-referenced problems in conventional applications for authenticating a tire RFID tag, at least by remotely analyzing a received RFID serial number (TID) in addition to the stored EPC product information. Such a practice, utilizing centralized access to a secure data storage including the RFID information, may ensure the physical chip being locally scanned is also the chip used during manufacturingimproving upon conventional anti-counterfeiting techniques by adding an additional layer of complexity and authentication. The TID is locked by the chip manufacturer prior to being sent out for assembly.

[0007] In some embodiments, a three-factor identification could be implemented, using for example hidden user memory that is only readable if given the access password for that specific chip, etc., in addition to the two-factor authentication techniques otherwise disclosed herein.

[0008] In some embodiments, manufacturers or third party data aggregators may provide data relating to events for a specific tire, wherein a system and method as disclosed herein may include determining whether a scanned EPC is likely in the given location, is in another location, not yet sold, or is no longer an active tire, e.g., has been scrapped. This authentication type may be usedin conjunction with multi-factor authentication to gauge a confidence level in the authentication determination and further ensure a single tire is not forged and registering events in two locations.

[0009] A system and method as disclosed herein accordingly may reduce the potential for forgery to near zero and provide a method to authenticate tires to their manufacturer. If there is concern that a QR code can be copied and re-produced, then logically, a RFID TAG EPC can also be copied and duplicated in the same method. Confirming the tag's physical chip, which is locked during manufacturing by the chip builder, mitigates this and ensures a correct authentication protocol.

[0010] An embodiment of a method as disclosed herein for secure authentication of identification information of a tire may include providing in data storage, for each of one or more tires having an RFID tag associated therewith, respective identification information from a tire source and comprising a first code associated with a first memory area and a second code associated with a second memory area, wherein at least the second memory area is permanently locked at the tire source such that the second code is persistent. Upon receiving a tire authentication request at a hosted server platform, the request comprising a first code and a second code identified via an RFID reader device, a first code may automatically be identified in data storage as matching the first code of the request, the corresponding second code is retrieved from the data storage and compared with the second code of the request to ascertain an authentication status of an RFID tag read by the RFID reader. A message comprising the authentication status is generated and transmitted from the hosted server platform, substantially in real time with respect to receipt of the tire authentication request.

[0011] In one exemplary aspect according to the above-referenced embodiment, the tire authentication request may be received, and the message comprising the authentication status transmitted, via an interface selectively initiated between the hosted server platform and the RFID reader device.

[0012] In another aspect according to the above-referenced embodiment, and optionally one or more above-referenced aspects thereof, the identification information for each tire may be received from the respective tire source via a second interface selectively initiated between the hosted server platform and the tire source.

[0013] In another aspect according to the above-referenced embodiment, and optionally one or more above-referenced aspects thereof, the tire authentication request may further comprise current values for each of one or more tire characteristics, and the authentication status may be further ascertained based on a comparison of the current values with respect to historical values in the data storage for the one or more tire characteristics and associated with the first code.

[0014] In another aspect according to the above-referenced embodiment, and optionally one or more above-referenced aspects thereof, the method may comprise iterative training of one or more models to correlate sequences of values for each of the one or more tire characteristics with a probability that the values are provided with respect to the same tire.

[0015] In other aspects according to the above-referenced embodiment, and optionally one or more above-referenced aspects thereof, the one or more tire characteristics may comprise a location of the RFID reader device, and / or a vehicle-tire combination, and / or manufacturing and / or sales data, and / or a signal strength measured in association with the tire RFID tag by the RFID reader device.

[0016] In another aspect according to the above-referenced embodiment, and optionally one or more above-referenced aspects thereof, upon comparing the retrieved second code with the second code of the request to initially authenticate the RFID tag read by the RFID reader, a first message may be generated and transmitted from the hosted server platform comprising a password from the data storage and associated with the first code of the request, substantially in real time with respect to receipt of the tire authentication request.

[0017] Upon further receiving at the hosted server platform a third code associated with a third memory area accessed using the password, and authenticating the third code against the stored identification information, the message comprising the authentication status may be further generated and transmitted from the hosted server platform as a second message.

[0018] In another embodiment as disclosed herein, a system for secure authentication of identification information of a tire may include data storage having provided therein, for each of one or more tires having an RFID tag associated therewith, respective identification information from a tire source and comprising a first code associated with a first memory area and a second code associated with a second memory area, wherein at least the second memory area is permanently locked at the tire source such that the second code is persistent. A hosted server platform may be configured to direct the performance of steps in a method according to the abovereferenced embodiment and optionally one or more of the above-referenced aspects thereof.

[0019] Numerous objects, features and advantages of the embodiments set forth herein will be readily apparent to those skilled in the art upon reading of the following disclosure when taken in conjunction with the accompanying drawings.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0020] Fig. 1 is a block diagram representing an exemplary embodiment of a system as disclosed herein.

[0021] Fig. 2 is a flowchart representing an exemplary embodiment of a method as disclosed herein.DETAILED DESCRIPTION

[0022] Referring generally to Figs. 1 and 2, various exemplary embodiments of an invention may now be described in detail. Where the various figures may describe embodiments sharing various common elements and features with other embodiments, similar elements and features are given the same reference numerals and redundant description thereof may be omitted below.

[0023] Various embodiments of a system as disclosed herein may include centralized computing nodes (e.g., a hosted cloud server) in functional communication with one or more confirmed data sources (e.g., manufacturers or other entities providing information by which a tire RFID tag may be authenticated) and a plurality of distributed client devices or computing nodes providing scanned information from tire RFID tags in the field and requesting authentication (e.g., associated with fleet management entities, service personnel, wholesalers, retailers, and the like) for effectively, securely, and reliably authenticating the scanned tire RFID tag.

[0024] Referring initially to Fig. 1, an exemplary embodiment of such a system 100 includes at least a server network 110 (e.g., cloud-based computing platform) including one or more processors 112 and a data storage network 114, and further includes or is functionally linked to one or more data sources 120, such as for example one or more tire manufacturer computers, public tire data sources, etc. The server network 110 is further communicatively linked to one or more client entities including reading devices 130 such as RFID transceivers capable of scanninginformation from a tire RFID tag 126 associated with a tire 124 in the field and transmitting messages 140 including authentication requests to the hosted server network and receiving messages 142 including a determined authentication status from the hosted server network.

[0025] One or more of the aforementioned components may be connected or otherwise functionally linked via a communications network (not expressly shown) which in various embodiments may include, in whole or in part, the Internet, a public network, a private network, or any other communications medium capable of conveying electronic communications. Different data source entities 120 may be communicatively linked to the server network 110 via respective interfaces 122, for example wherein manufacturers may securely transmit information via selectively initiated communications. Client entities 130 may be communicatively linked directly to the server network 110 via interfaces 132 such as for example application programming interfaces (APIs). A client entity 130 may communicate with the hosted server network 110 via a third party tire information service such as for example the Global Data Service Organisation for Tyres and Automotive Components (GDSO) and respective APIs. Such channels are conventionally known for directing the communication of tire specifications between manufacturers and customers, and may be utilized in part for additional authentication methods as disclosed herein.

[0026] In various exemplary embodiments, some or all of the data sources 120 and / or client entities 130 may include or otherwise be associated with at least one of a server computer, a server device, a desktop computer, a laptop computer, a smart phone, or other equivalent electronic device capable of executing program instructions.

[0027] The data storage network 114 as shown in Fig. 1 may include for example one or more databases or equivalent storage media for retrievably storing look-up tables 116, and in some embodiments models and input data for development thereof. Data from prior scans in the field, data from the tire data sources 120, and the like, once transmitted via a communications network to the hosted server network 1 10, may accordingly be stored as or in association with tire characteristics to be utilized as further described below, for example in a database associated therewith.

[0028] It should be noted that an embodiment of a system 100 as represented in Fig. 1 is not limiting on the scope of a system or method 200 as disclosed herein, unless otherwise expressly provided. For example, the hosted server network 110 may be integrated or otherwise associated with a tire manufacturer network such that a secure interface 122 is unnecessary to obtain and retrievably store the relevant tire RFID tag information. As another example, the tire RFID tag information may be obtained from a third party having programmed the tag itself but prior to manufacturing of the tire, wherein additional communication channels are not illustrated but nonetheless utilized as may be understood by one of skill in the art.

[0029] Referring next to Fig. 2, a method 200 according to the present disclosure may now be described. The description below is intended to inform the reader regarding various steps according to the method 200, but it should be noted that not all steps may be required for any given iteration, for example responsive to each authentication request that is received, and further that additional steps may inherently or optionally be performed within the scope of the present disclosure and without requiring explicit detail therefor.

[0030] While the method 200 may be described with reference to elements of the system 100 as noted above, the various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps may be described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

[0031] The steps or algorithms of the method 200 as described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of computer-readable medium known in the art. An exemplary computer-readable medium can be coupled to the processor such that the processor can read information from, and write information to, the memory / storage medium. In the alternative, the medium can be integral to the processor. The processor and the medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the medium can reside as discrete components in a user terminal.

[0032] The illustrated method 200 begins with the receiving and storing of tire data (step 210) from one or more tire sources 202 and / or from client entities with respect to prior scans 204 of anRFID tag associated with tires. As noted above, the tire data 202, 204 may be stored as or in association with tire characteristics in secure databases associated with the hosted server network110. The input tire data may in embodiments as disclosed herein include at least a unique 12- character serial number that has been stored in the tire RFID tag EPC memory, and a manufacturer- locked TID serial number for the same tire.

[0033] In an optional embodiment, the method 200 may further include training one or more models (step 215) based on some or all of the input data 202, 204, wherein the input data may be correlated in any of various known techniques with authentication of an associated tire. For example, if the input data comprises a date on which the tire RFID tag data was received, an event associated with the input (e.g., mounting or removal of an associated tire, changing of position on an associated vehicle, retread, scrap), sales data, or the like, the models may be iteratively developed to infer or predict with high accuracy whether a new / subsequent input data set allegedly corresponding to a same tire is likely valid or invalid. This may include probabilistically determining as to whether an REIS tag having a scanned first (e.g., EPC) code is likely in the given location, is in another location, not yet sold, or is no longer an active tire, e g., has been scrapped.

[0034] Accordingly, relevant tire characteristics as determined from the input data 202, 204 may include sequences of data representing historical locations of the RFID reader device scanning the RFID tag, historical vehicle-tire combinations, manufacturing data, sales data, etc. In an embodiment, the historical data may represent a measured signal strength for various RFID scans over time, wherein a model may be developed to predict a range of signal strength to be expected for a current RFID scan and compared therewith.

[0035] This authentication type may be used in conjunction with multi-factor authentication as further described below to gauge a confidence level in the authentication determination and further ensure a single tire is not forged and registering events in two locations, wherein the one or more tire characteristics comprise a location of the RFID reader device.

[0036] The illustrated method 200 continues in step 220 with the receipt at the hosted server network of an authentication request corresponding to an RFID tag scan from a client entity (e.g., via or otherwise originating with an output from an RFID reader device). The authentication request may be provided in substantially real time with respect to a current scan, or may be delayed where for example scans of multiple tires are performed and then transmitted together or in sequence after the scanning operation is complete. The authentication request 140 may be provided in a message via interface(s) 132 and may include, using the example shown in Fig. 1, a first code (corresponding to EPC SGTIN-96 encoding in a first memory area) of ‘ 1000’ and a second code (corresponding to TID serial number in a second memory area) of ‘999’.

[0037] In accordance with the optional embodiment including step 215 as noted above, the method 200 may further include selective retrieval of at least one model based on input data received with the authentication request in step 220, and determining a level of confidence (or lack thereof) as to whether the input data of the authentication request could be provided with respect to the asserted RFID tag. Although step 225 is illustrated prior to step 230 in Fig. 2, matching of the first code in the authentication request with a stored first code may in various embodiments be a preliminary step for identifying the asserted RFID tag and retrieving any auxiliary data.

[0038] Upon matching the first codes (e.g., EPC ‘ 1000’ using the example shown in Fig. 1) in step 230, the method 200 continues in step 240 with retrieval of the second code stored inassociation with the RFID tag having the first code. In the example shown in Fig. 1, this second code is retrieved from the look-up table as ‘ 123’. As the second code of ‘ 123’ for the actual RFID tag manufactured with first code ‘ 1000’ does not match the second code of ‘999’ provided in the authentication request (i.e., “no” in response to the query in step 242), the scanned RFID tag is not authenticated (step 260) and the hosted server network in step 280 generate an API response to the client entity with a message having an included response line informing of non-authentication. Such a response may preferably be generated substantially in real time with respect to receipt of the authentication request, for example within milliseconds or otherwise as limited only by the practical realities of the various processors and communications networks.

[0039] In the event that the second code as retrieved from data storage in step 240 did match the second code provided in the authentication request of step 220 (i.e., “yes” in response to the query in step 242), in an embodiment wherein no further authentication steps are required the RFID tag is authenticated (step 270) and the hosted server network in step 280 may simply generate an API response to the client entity with a message having an included response line informing of authentication. Such a response may preferably be generated substantially in real time with respect to receipt of the authentication request, for example within milliseconds or otherwise as limited only by the practical realities of the various processors and communications networks.

[0040] In another optional embodiment, however, three-factor authentication may be required (i.e., “yes” in response to the query in step 250), wherein the hosted server network provides an access password to the client entity (step 252).

[0041] In such an embodiment, a tire manufacturer may for example generate a unique user memory access password for a specific tire, and further assign an encryption key which isconfidential and rotates within timelines that may further be specified by the manufacturer. An encrypted version of the access password may be created and written to user memory, which is locked using the decrypted access password. The reserve memory (including the access password) may then be locked. Through use of the encryption key, the decrypted value is the “access password” for the user memory. Once the access password is written and locked, it is not readable by external reader devices but the user memory can always be read.

[0042] This provides two primary methods for authenticating: by locally decrypting user memory; or by sending the EPC to the manufacturer or an equivalent who will relay the access password for the tire to do a unlock / lock test.

[0043] In the first of the above-referenced methods for three-factor authentication, whether through cross-platform integration or a hosted solution that is secured and maintained locally, a trusted party may be provided with a maintained list of decryption keys by plant and date, to locally decrypt the access password from the user memory after reading, matching the date of manufacture to relevant decryption key, and attempt the unlock / lock protocol of three-factor authentication with one less call. This method may be the faster of the two, but may also lack scalability for customer solution builds wherein a single party would be obligated to store all past encryption keys.

[0044] In the second of the above-referenced methods for three-factor authentication, the client entity scans the EPC and sends it to the host, wherein the host provides the secret access password for that unique tire, which the client entity may then attempt to unlock / lock using the access password. If the tire has previously been unlocked and has the password exposed, and cannot be locked with the password, then it can be deemed a forged or otherwise tampered tire. If the tirecannot be unlocked, it may be deemed forged. If the tire is successfully unlocked and locked, on the other hand, it may be deemed authentic.

[0045] Accordingly, in one example by referenced back to Figure 2, the access password may be provided in a first response, wherein the RFID reader device of the client entity utilizes the password to retrieve a third code which is inaccessible without the password, and provides the third code to the hosted server network for further authentication. If the third code is determined to match a third code provided by the tire RFID tag data source 120 (i.e., “yes” in response to the query in step 254) the RFID tag is authenticated (step 270) and the hosted server network in step 280 generates a second response to the client entity with a message informing of authentication.

[0046] In another example according to such an embodiment, the access password may be provided in the response along with the actual third code, wherein the RFID reader device (alone or in association with one or more other computing devices, etc.) of the client entity utilizes the password to retrieve and compare the third code associated with the scanned RFID tag. If the respective third codes are determined to match each other (i.e., “yes” in response to the query in step 254) the RFID tag is authenticated (step 270) without further communications to and from the hosted server network. In some embodiments, a subsequent message may nonetheless be generated to the hosted server network to acknowledge authentication based on the third code.

[0047] Either of the preceding examples including implementation of three-factor authentication may potentially be more robust than a two-factor authentication embodiment and cannot be forged, but likely more intrusive and time-consuming during interrogation- requiring a tire RFID tag to be read, accessed, written, read, and re-locked. It also requires the use of tags with user memory, which may not otherwise be required for other embodiments within the scopeof the present disclosure. The use of secure reader middleware may also be preferred to hide the values used during a three-factor protocol as disclosed herein.

[0048] Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context dictates otherwise. The meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. The meaning of “a,” “an,” and “the” may include plural references, and the meaning of “in” may include “in” and “on.” The phrase “in one embodiment,” as used herein does not necessarily refer to the same embodiment, although it may. As used herein, the phrase “one or more of,” when used with a list of items, means that different combinations of one or more of the items may be used and only one of each item in the list may be needed. For example, “one or more of’ item A, item B, and item C may include, for example, without limitation, item A or item A and item B. This example also may include item A, item B, and item C, or item B and item C.

[0049] Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and / or states. Thus, such conditional language is not generally intended to imply that features, elements and / or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and / or states are included or are to be performed in any particular embodiment.

[0050] The previous detailed description has been provided for the purposes of illustration and description. Thus, although there have been described particular embodiments of a new and usefulinvention, it is not intended that such references be construed as limitations upon the scope of this invention except as set forth in the following claims.

Claims

CLAIMSWhat is claimed is:

1. A method for secure authentication of identification information of a tire, the method comprising: providing in data storage, for each of one or more tires having an RFID tag associated therewith, respective identification information from a tire source and comprising a first code associated with a first memory area and a second code associated with a second memory area, wherein at least the second memory area is permanently locked at the tire source such that the second code is persistent; receiving a tire authentication request at a hosted server platform, the request comprising a first code and a second code identified via an RFID reader device; automatically identifying a first code in data storage matching the first code of the request, retrieving the corresponding second code from the data storage, and comparing the retrieved second code with the second code of the request to ascertain an authentication status of an RFID tag read by the RFID reader; and generating and transmitting from the hosted server platform a message comprising the authentication status, substantially in real time with respect to receipt of the tire authentication request.

2. The method according to claim 1, wherein the tire authentication request is received, and the message comprising the authentication status is transmitted, via an interface selectively initiated between the hosted server platform and the RFID reader device.

3. The method according to claim 2, wherein the identification information for each tire is received from the respective tire source via a second interface selectively initiated between the hosted server platform and the tire source.

4. The method according to claim 1, wherein the tire authentication request further comprises current values for each of one or more tire characteristics, and the authentication status is further ascertained based on a comparison of the current values with respect to historical values in the data storage for the one or more tire characteristics and associated with the first code.

5. The method according to claim 4, comprising iterative training of one or more models to correlate sequences of values for each of the one or more tire characteristics with a probability that the values are provided with respect to the same tire.

6. The method according to claim 4, wherein the one or more tire characteristics comprise a location of the RFID reader device.

7. The method according to claim 4, wherein the one or more tire characteristics comprise a vehicle-tire combination.

8. The method according to claim 4, wherein the one or more tire characteristics comprise manufacturing and / or sales data.

9. The method according to claim 4, wherein the one or more tire characteristics comprise a signal strength measured in association with the tire RFID tag by the RFID reader device.

10. The method according to claim 1, comprising: upon comparing the retrieved second code with the second code of the request to initially authenticate the RFID tag read by the RFID reader, generating and transmitting from the hosted server platform a first message comprising a password from the data storage and associated withthe first code of the request, substantially in real time with respect to receipt of the tire authentication request; upon further receiving at the hosted server platform a third code associated with a third memory area accessed using the password, and authenticating the third code against the stored identification information, further generating and transmitting from the hosted server platform the message comprising the authentication status as a second message.

11. A system for secure authentication of identification information of a tire, the system comprising: data storage having provided therein, for each of one or more tires having an RFID tag associated therewith, respective identification information from a tire source and comprising a first code associated with a first memory area and a second code associated with a second memory area, wherein at least the second memory area is permanently locked at the tire source such that the second code is persistent; a hosted server platform configured to direct the performance of steps in a method according to one of claims 1 to 10.

Images