Methods for identifying, authenticating, and tracking physical assets

Abstract

PROVIDING A SYSTEM AND METHOD FOR AUTHENTICATING A PRODUCT - Patent application Such a system may include an asset verification system including an image comparison device and an image data store, an asset registration station in communication with the asset verification system, and an asset verification software application in a verification device in communication with the asset verification system. The product to be authenticated may be a tangible asset having at least one non-homogeneous visual characteristic, or a uniquely arranged, visually homogeneous collection of products.

Description

[Technical field]

[0001] Related Applications This application claims priority to U.S. Provisional Application No. 63 / 298,371, filed January 11, 2022, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to methods and systems for authentication of tangible assets, the tangible assets having heterogeneous visual characteristics. More particularly, the present disclosure is directed to comparing an image and / or machine-readable code associated with a tangible product with a previous image and / or code purportedly associated with the product.

[0003] There are stakeholder concerns regarding the authenticity of tangible assets. For example, food products such as beef are sometimes falsely advertised as having a particular origin. Similarly, leather products are frequently counterfeited. These concerns can result in loss of business for retailers, brand tarnishment for producers, and potential harm for consumers.

[0004] Thus, there exists an unmet need for identification, authentication, and tracking of tangible assets such as beef or leather. Accordingly, the present disclosure provides a system for storing images and machine readable codes associated with tangible assets, and methods of use thereof.

[0005] The present disclosure provides various embodiments of a method for authenticating a product, the method including storing, in an asset verification device, at least one image of a portion of a first product and at least one machine-readable code associated with the first product, the first product including a tangible asset having at least one heterogeneous visual feature or a combination of homogeneous features.

[0006] The method further includes scanning at least one of an image of a portion of a second product and a machine-readable code associated with the second product. The method further includes comparing the scanned image or machine-readable code to the at least one image or machine-readable code in the asset verification device. The method further includes providing an indication to a user if the asset verification device contains an image or machine-readable code that matches the scanned image or machine-readable code.

[0007] In some embodiments, storing at least one image of a portion of a first product and at least one machine-readable code associated with the first product includes creating the at least one machine-readable code associated with the first product and capturing the at least one image of a portion of the first product.

[0008] In some embodiments, the asset verification device is a system including a database and machine vision software. In some embodiments, the asset verification device further stores at least one of authentication credentials, operational data, location data, a timestamp associated with the capture of the at least one image, and a timestamp associated with the creation of the at least one machine readable code.

[0009] In some embodiments, the at least one machine readable code is affixed to the first product or to packaging on or around the first product, hi further embodiments, the at least one machine readable code is affixed in proximity to a portion of the first product captured in the at least one image.

[0010] In some embodiments, the method further includes storing at least one of location data and a timestamp associated with the scanned image or comparison of the machine-readable code on the asset verification device. In some embodiments, the machine-readable code is a Quick Response code, DataMatrix, Aztec, TrillCode, QuickMark, ShotCode, mCode, Beetagg, UPC code, or other such code, including proprietary / custom codes. In some embodiments, the scanning step is performed with a verification device.

[0011] In some embodiments, storing at least one image of the portion of the first product includes storing the image, a description of the image, or a combination thereof.

[0012] The present disclosure provides various embodiments of a system for authenticating a product. The system includes an asset verification system including an image comparison device and an image data store, the data store including at least one image of a portion of a first product and at least one machine-readable code associated with the first product, the first product including a tangible asset having at least one heterogeneous visual feature or a unique combination of a plurality of visually homogeneous tangible assets. The system further includes an asset registration station in communication with the asset verification system, and an asset verification software application in a verification device in communication with the asset verification system.

[0013] In some embodiments, the data store stores at least one of authentication credentials, operational data, location data, a timestamp associated with the capture of at least one image, and a timestamp associated with the creation of the at least one machine-readable code.

[0014] In some embodiments, the asset verification system includes an asset registration application program interface configured to index a new image of a portion of one or more products and a machine readable code associated with one or more products. In some embodiments, the asset verification system includes an asset verification application program interface configured to respond to a query from the verification device to authenticate a product.

[0015] In some embodiments, at least one machine readable code is affixed to the first product or to packaging on or around the first product, hi further embodiments, the at least one machine readable code is affixed in proximity to a portion of the first product captured in the at least one image.

[0016] In some embodiments, the asset registration station is configured to capture at least one image of a portion of each of one or more products and read at least one machine readable code associated with the one or more products, hi further embodiments, the asset registration station includes at least one camera, at least one light source, and a processor.

[0017] In some embodiments, the verification device is a smartphone, a smartwatch, augmented reality / virtual reality glasses / headset, or any device that includes a camera.

[0018] In some embodiments, the asset verification software application is configured to capture an image of a portion of one or more products and read a machine readable code associated with the one or more products. In further embodiments, the asset verification software application is configured to provide an indication in response to a user query if the database contains an image or machine readable code that matches the scanned image or machine readable code. In further embodiments, the asset verification software application is configured to capture time and / or location information associated with a user query.

[0019] In some embodiments, the at least one image of a portion of a first product includes an image, a description of an image, or a combination thereof.

[0020] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed. [Brief description of the drawings]

[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. [Figure 1] FIG. 1 is a block diagram illustrating a system for identifying and authenticating tangible assets according to some embodiments. [Diagram 2] FIG. 2 is a flow chart illustrating a method for storing an image and / or a machine-readable code associated with a tangible asset according to some embodiments. [Diagram 3] FIG. 3 is a flow chart illustrating a method for identifying and authenticating a tangible asset according to some embodiments. [Figure 4A] FIG. 4A is an image of an example machine-readable code applied to a tangible asset and an underlying asset window, according to some embodiments. [Figure 4B]FIG. 4B is an image of an exemplary machine-readable code, logo, and underlying asset window applied to a tangible asset, according to some embodiments. [Diagram 5] FIG. 5 is an image of an exemplary machine-readable code, logo, and borderless underlying window applied to a tangible asset, according to some embodiments. [Figure 6] FIG. 6 is an image of an exemplary machine-readable code and borderless underlying window applied to a tangible asset, according to some embodiments. [Figure 7] FIG. 7 is an image of an exemplary machine-readable code applied to tangible aquatic assets, according to some embodiments. [Figure 8] 8A and 8B are images of exemplary machine-readable code applied to tangible shellfish assets, according to some embodiments. [Figure 9] FIG. 9 is an image of an exemplary machine-readable code applied to a homogenous, unbranded medical asset, according to some embodiments. [Figure 10] FIG. 10 is an image of an exemplary machine-readable code applied to a homogenous marked medical asset, according to some embodiments. [Figure 11] FIG. 11 is an image of an exemplary machine-readable code applied to a homogenous pharmaceutical asset having a random orientation, according to some embodiments. [Figure 12] FIG. 12 is an image of an exemplary machine-readable code applied to a heterogeneous pharmaceutical asset having a random orientation, according to some embodiments. [Figure 13] FIG. 13 is an image of an exemplary etched machine-readable code applied to a leather asset, according to some embodiments. [Figure 14] FIG. 14 is an image of an exemplary machine-readable code applied to a wood grain asset, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Reference will now be made in detail to certain exemplary embodiments according to the present disclosure, some examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[0023] As used herein, the use of the singular includes the plural unless specifically stated otherwise. As used herein, the use of "or" means "and / or" unless specifically stated otherwise. Furthermore, the use of the term "including", as well as other forms such as "includes" and "included", is not limiting. Similarly, the use of the term "comprising", as well as other forms such as "comprises", is not limiting. Any range described herein is understood to include the endpoints and all values ​​between the endpoints.

[0024] The section headings used herein are for organizational purposes only and are not to be construed as limiting the subject matter described. All documents or portions of documents cited in this application, including but not limited to patents, patent applications, articles, books, and treatises, are expressly incorporated herein by reference in their entirety for all purposes.

[0025] According to some embodiments, a system for identifying, tracking, and authenticating tangible assets is provided. The invention provides a method for "smart labeling" products that have inherently heterogeneous visual attributes (e.g., meat marbling, wood grain) and allows a party to authenticate that the contents of the package match the package. The system keeps a record of images and machine-readable codes associated with one or more tangible assets. At any stage in the supply chain (warehouse, distribution, retail), a person can query the system for information about the material. For example, a customer can submit an image of an asset and / or an associated machine-readable code to the system, and the system provides information corresponding to the image or code.

[0026] A tangible asset with heterogeneous visual characteristics, such as veins, marbling, and grain in beef or leather, or a unique combination of multiple visually homogeneous tangible assets, can provide a unique identifier for the asset. Products that can be tracked and authenticated using the disclosed systems and methods can include any tangible asset with heterogeneous visual characteristics, such as cuts and products of red meat (beef, pork, lamb, etc.), whole seafood and associated processed products (salmon, tuna, lobster, shrimp, etc.), plant protein food products, leather and natural fiber assets, crafts and / or furniture made from wood grain materials, collectibles, or combinations of visually homogeneous assets such as pharmaceutical pills. For example, the natural marbling of red meat provides a unique visual fingerprint for each red meat asset.

[0027] The systems and methods described herein capture images of unique, non-homogeneous visual signatures to track and authenticate tangible assets. Fraudulent products can be identified because they do not contain the same visual signatures as products originally scanned into the system earlier in the supply chain.

[0028] 1 is a block diagram illustrating a system 100 for identifying and authenticating a tangible asset, according to some embodiments. In some embodiments, the system includes an asset verification device 110, an asset registration station 120, and a verification device 130. In some embodiments, the system 100 includes an asset verification device 110 and an asset registration station 120. The asset verification device 110 collects necessary information from the asset producer via the asset registration station 120 and provides authentication services to the party via an asset verification application 135 for the verification device 130.

[0029] The asset verification device 110 may include an image storage (data store 111) and an image comparison device 112. The asset verification device 110 is a secure storage device of asset registration records for asset producers and is configured to provide asset authentication services to parties. The asset verification device 110 may be a server or a collection of servers that provide two APIs (Application Programmatic Interfaces), one for asset registration 113 and one for asset verification 114. The asset verification device 110 may also provide two cloud-based applications for asset registration and asset verification.

[0030] The required information collected by the asset verification device 110 in the data store 111 may include an image of at least a portion of the asset, a description of the image, or a combination thereof. In some embodiments, the portion of the asset captured in the image includes non-homogeneous physical characteristics. For example, the image may depict the veining, marbling, or grain of beef or leather. In some embodiments, the portion of the asset captured in the image includes a unique combination of multiple visually homogeneous tangible assets. For example, the image may depict the physical configuration of pharmaceutical tablets within a bottle or blister pack.

[0031] The required information collected by the asset verification device 110 in the data store 111 may include a machine readable code associated with the asset. The machine readable code may be any of the following: a Quick Response code, DataMatrix, Aztec, TrillCode, QuickMark, ShotCode, mCode, Beetagg, UPC, or a proprietary / custom code. In some embodiments, at least one machine readable code is affixed to the asset or to packaging on or around the asset. The placement of the machine readable code is further described with reference to FIG. 4.

[0032] In some embodiments, the required information collected in the data store 111 may also include authentication credentials, operational data, location data, a timestamp associated with the capture of at least one image, and a timestamp associated with the creation of at least one machine-readable code.

[0033] The authentication credentials are associated with authenticating the asset registration station 120 with the asset verification device 110, and do not authenticate the tangible asset. The authentication credentials may include a username, a password, and / or a one-time code, etc.

[0034] The operational data may include a production line identifier associated with the tangible asset, an operator identifier associated with the production line, a product descriptor associated with the tangible asset, and environmental measurements such as temperature and humidity.

[0035] The location data may include information associated with the physical location of the asset. For example, when capturing an image of at least a portion of the asset, the geographic location of the camera capturing the image may be stored. As another example, the geographic location where a machine readable code on the asset was scanned may be stored.

[0036] The asset registration API 113 may be a protocol that allows a known secure asset registration station 120 to request a new asset to be registered with the asset verification device 110. The request from the asset registration station 120 includes a machine readable code and an image of at least a portion of the asset, and may further include secondary data such as authentication credentials, operational data, location data, a timestamp associated with the capture of the at least one image, and a timestamp associated with the creation of the at least one machine readable code.

[0037] The asset verification device 110 is configured to store data from the asset registration station 120 in a data store 111, indexed by a unique product identifier (UPI) contained within the machine-readable code data. In some embodiments, the index may be augmented with secondary data such as time and / or producer information.

[0038] In some embodiments, the data store 111 may be configured to automatically delete data after a set amount of time, which may vary by type of asset.

[0039] The asset verification API 114 is a protocol that allows a user of the verification device 130 to request verification of the authenticity of an asset. The request from the verification device 130 includes a machine-readable code and an image of the asset, and may optionally include secondary data as described above. The asset verification device 120 uses the machine-readable code data to quickly and efficiently retrieve an enrollment image associated with the asset. The enrollment image and the image in the verification request are then compared by the image comparison device 112. Other checks based on secondary data (location information, timestamp, etc.) may also be used. Depending on the output of these checks, the asset verification device 120 may send either a positive, negative, or inconclusive authentication message to the asset verification software 135 on the verification device 130. Any additional data associated with the asset, such as a recall notice, may also be sent to the asset verification software 135. In some embodiments, the additional data is displayed along with the authentication message.

[0040] The data store 111 may be a server-based application that maintains a current record of assets registered with the system 100, indexed by each asset's machine-readable code. The data store 111 maintains a record of registered assets' machine-readable codes, associated asset images, and any subsequent producer data. Producers can add records to the data store 111 via the asset registration station 120 through the asset registration API 113.

[0041] In some embodiments, the data store 111 may utilize one or more blockchain ledgers to store asset data. The blockchain may provide a transparent record of an asset as it moves in the supply chain from producer to retailer.

[0042] The image comparer 112 may be a server-based application that compares records in the data store 111 with records provided by a verification request from the verification device 130. In some embodiments, the records include images and machine-readable codes associated with the assets. The image comparer 112 is configured to perform a machine vision-based image comparison of the stored images with the images provided in the verification request. In some embodiments, the image comparer 112 may perform additional validity checks based on subsequent information such as the location of the parties and the time / date of the verification request.

[0043] The asset registration station 120 is configured to register one or more assets with the asset verification device 110. Registration involves reading a machine-readable code and taking a calibrated image of at least a portion of the asset. The machine-readable code data and the image are then transmitted to the asset verification device 110 along with any other required information, such as authentication credentials, operational data, and a timestamp.

[0044] In some embodiments, the asset registration station 120 is designed to be highly automated. An automated asset registration station 120 provides high unit throughput with minimal effort. For example, the asset registration station 120 may automate the process of scanning a machine-readable code and capturing an image of at least a portion of the asset, but require user interaction to initiate the process and / or approve the captured image. In some embodiments, the asset registration station 120 may include material handling equipment and controls (e.g., conveyor belts, actuators) for a higher degree of automation.

[0045] The asset registration stations 120 may include hardware and software deployed at the producer's packaging site. Each station 120 may include machine vision subsystems (e.g., cameras, lenses, focusing hardware, lighting), material handling equipment (e.g., conveyor belts, sorters), a processor running specialized software, and a user interface (e.g., touch screen, status traffic lights, voice announcements). The asset registration stations 120 may be able to communicate with the asset verification device 110 over the Internet or may have a dedicated data line to the asset verification device 110.

[0046] The asset registration station 120 may be configured to deregister an asset. For example, if an asset is determined to be counterfeit, a user may manually deregister the counterfeit asset. Similarly, if an asset is destroyed after being registered with the system 100, a user may manually deregister the asset.

[0047] In some embodiments, the asset registration station 120 can automatically determine that an asset is counterfeit. For example, if homogeneous characteristics indicative of counterfeit leather are evident in the captured image, the asset registration station 120, or the asset verification device 110, can remove the asset from the system and provide a notification to a user of the system 100.

[0048] In some embodiments, the asset registration station 120 is configured to augment data of registered assets associated with subsequently received information. For example, the asset registration station 120 may augment data taking into account received recall notices or promotional information. If the asset registration station 120 loses connectivity with the asset verification device 110, the asset registration station 120 may be configured to cache asset data until connectivity is restored.

[0049] The verification device 130 may include asset verification software 135. The role of the asset verification software 135 is to enable authentication of assets in real time. The asset verification software 135 may be a mobile software application configured to use the smartphone's camera, GPS, clock / calendar, and / or internet connectivity subsystem, as well as a touch screen for user interaction. For example, a user may point the smartphone's camera at the label of the asset, prompting an authentication query by the asset verification software 135.

[0050] In some embodiments, the asset verification software 135 may also record user identification information such as the smartphone make / model, serial number, etc. The recorded user data may be utilized to improve the performance of the system 100. For example, patches for the asset verification software 135 may be created based on the performance of the software on a particular smartphone make / model.

[0051] If the verification device 130 loses connectivity to other elements of the system 100, the asset verification software 135 is configured to provide a message to the user that verification is currently not possible due to the loss of connectivity.

[0052] 2 is a flow chart illustrating a method 200 of storing an image and / or a machine-readable code associated with a tangible asset having non-homogeneous characteristics or a group of tangible assets having homogeneous characteristics, according to some embodiments. The method begins in step 210 with creating a machine-readable code associated with the tangible asset or group of assets. The machine-readable code may be any of the following: Quick Response code, DataMatrix, Aztec, TrillCode, QuickMark, ShotCode, mCode, Beetagg, UPC, or a proprietary / custom code. In some embodiments, the code is printed as a physical label.

[0053] In step 220, a machine readable code is affixed to a tangible asset or group of assets. In some embodiments, the code is applied to the asset by the producer at the time of packaging. In some embodiments, the code is affixed in conjunction with an underlying asset window (UAW).

[0054] 4A is an image of an example machine readable code 420 and UAW 410 applied to a tangible asset 400, according to some embodiments. A physical label, such as a printed sticker, containing the code 420 may be added to the packaging on or around the tangible asset 400. The label may be imprinted directly onto the asset 400, for example as a laser etch, depending on the original asset. The label may be created dynamically (at the time of packaging) or statically (batch printing in advance).

[0055] The UAW 410 may be used by a user to verify the authenticity of the asset 400. The UAW 410 may or may not be designated by a visible perimeter that reinforces the machine-readable code 420. The visible perimeter may indicate an area of ​​the underlying asset that is used to inspect the asset. The visible perimeter may be functional or decorative for marketing purposes and may include a trademark or logo.

[0056] 4B is an image of an example machine-readable code 420, logo 430, and underlying asset window 410 applied to a tangible asset, according to some embodiments. As seen in FIG. 4B, the underlying asset window 410, machine-readable code 420, and logo 430 may all be positioned within a visible boundary.

[0057] FIG. 5 is an image of an exemplary machine-readable code 420, logo 430, and borderless UAW 410 applied to a tangible asset 400, according to some embodiments. The gray dashed border indicates the location of the UAW 410 that is not visually indicated by any physical markings on the packaging. In embodiments where a visible border does not designate the UAW 410, the visible border may indicate an area of ​​the underlying asset that is not used for inspection of the underlying asset. The actual UAW 410 may not be marked for security purposes. For example, the depicted label in FIG. 5 alludes to meat being inspected in a yellow border area, but the actual inspection is based on an invisible gray border area. The UAW 410 does not have to be a physical component of a physical label. The UAW 410 may be a "virtual" one whose location is resolved relative to the code 420.

[0058] 6 is an image of an exemplary machine-readable code 420 and borderless UAW 410 applied to a tangible asset 400, according to some embodiments. The gray dashed box indicates the location of the UAW 410 that is not visually indicated by any physical markings on the packaging. This instantiation eliminates the need for a physical label or a transparent window or visible border within the packaging, resulting in a simpler, lower-cost labeling solution.

[0059] The machine readable code 420 serves several functions. First, it allows for unique identification of the underlying asset 400 through a unique asset identifier. Second, it provides a known visual marking that can be used to indicate the location of the UAW 410. Third, it provides a mechanism for end users to easily obtain a mobile application for a smart phone to access the asset verification device 110.

[0060] In step 230, an image of a tangible asset or part of a group of assets is taken. In some embodiments, the image further includes a machine readable code. In some embodiments, a digital image of the product around the area of ​​the UAW may be taken by the producer of the asset as it is packaged. The image includes non-homogeneous physical characteristics of the asset or non-homogeneous arrangements within a homogeneous group of assets.

[0061] In step 240, the image is stored in a database. In some embodiments, the image stored in the database may be indexed to include a descriptor of the tangible asset, as described above. In some embodiments, the descriptor of the image is stored in the database. In some embodiments, only the descriptor is stored in the database, not the image itself.

[0062] 3 is a flow chart illustrating a method 300 for identifying and authenticating a tangible asset or group of assets, according to some embodiments. Prior to commencing the method 300, a database may be created, such as in the asset verification device described above. The database may be populated with images of the tangible assets and / or descriptors of the images of the tangible assets. The images may depict portions of tangible assets having heterogeneous physical characteristics, or heterogeneous arrangements within a homogeneous group of assets. The database may further be populated with machine readable codes associated with the tangible assets. Population of the database is described in more detail with reference to the flow chart of FIG. 2.

[0063] In some embodiments, the images and machine-readable codes stored in the database may be indexed by a unique product identifier. The database may include additional data such as the type of tangible asset (food, leather, etc.), the manufacturer of the asset, the age of the asset, the country of origin of the asset (or a particular region within the country of origin), or any other useful descriptor of the asset associated with the image or machine-readable code.

[0064] In step 210, a user scans an image of at least a portion of a tangible asset or group of tangible assets and / or scans a machine-readable code associated with the tangible asset. For example, a user may use a smartphone to scan a machine-readable code on the packaging of a piece of beef at a grocery store. As another example, a retailer may take an image of a leather handbag received from a warehouse.

[0065] An application on the smart phone may provide on-screen prompts for alignment of the phone's camera with the asset label. Once the camera and asset label are sufficiently aligned, an automatic shutter feature on the camera automatically captures an image of the code and underlying asset window (UAW). The code data and UAW image, along with time and location information, may be sent to a database for verification in step 220. The UAW is described in further detail above with reference to FIG. 4.

[0066] In step 220, the method includes searching the database for images and / or codes that match the image or machine-readable code scanned by the user in step 210. In some embodiments, the database is searched for images that are exactly similar to the scanned image. In some embodiments, the database is searched for images that are only partially similar to the scanned image, for example, 80%, 85%, 90%, 99%, 99.9% similar, or any percentage in between. In some embodiments, the database is searched for descriptors that match the description of the image scanned by the user.

[0067] The method continues at step 230 by providing an authentication indication to the user of step 220. The indication may include whether the scanned image or machine-readable code has a match in a database. If a match is found, the indication may include descriptors associated with the tangible asset or group of tangible assets, such as the manufacturer of the asset, the age of the asset, the country of origin of the asset (or a particular region within the country of origin), etc. If no match is found, the indication may include a message that the origin of the asset could not be confirmed. If the possibility of a match is uncertain, the indication may include a message that the origin of the asset is uncertain.

[0068] In some embodiments, the indication may include a message that authentication of the asset is currently not possible, for example because connectivity to the database has been lost. In some embodiments, steps 220 and / or 230 may be repeated once connectivity to the database is re-established.

[0069] The method described above may be employed with red meat products such as beef as depicted in Figures 4A, 4B, 5, and 6. Figures 7-14 depict other tangible assets that may be employed with the method.

[0070] 7 is an image of an exemplary machine-readable code 420 applied to a tangible seafood asset 400, according to some embodiments. Natural variations in the coloration of fish tissue, such as salmon, tuna, and many other species, provide a unique visual fingerprint for each asset. The machine-readable code 420 can be affixed in conjunction with a UAW 410 that identifies a particular area of ​​the coloration.

[0071] 8A and 8B are images of an exemplary machine-readable code 420 applied to a tangible shellfish asset 400, according to some embodiments. Shellfish such as lobsters and shrimp produce visually heterogeneous characteristics. Visual differences can be within the pigmentation of cooked meat, or raw shells. This can be at the level of a single item (e.g., a vacuum-packed half lobster as depicted in FIG. 8B) or a group of items, such as a pack of shrimp as depicted in FIG. 8A. The machine-readable code 420 can be affixed in conjunction with a UAW 410 that identifies specific areas of pigmentation.

[0072] The methods disclosed herein can also be used to authenticate homogenous products such as pharmaceutical tablets, where the tablets are bundled in a suitable package: the collective arrangement within the bundled package, such as a bottle or blister pack, can produce a non-homogeneous image, even though the individual tablets do not provide any of the required visual variety.

[0073] 9 is an image of an exemplary machine-readable code 420 applied to a homogenous, unbranded pharmaceutical asset 400, according to some embodiments. The unbranded identical tablets may be physically restrained at the time of packaging within an at least partially transparent container, with the transparent portion of the container acting as a UAW 410 for the contents of the container. The random arrangement of the homogenous product within the container creates a non-homogeneous image. Packaging within the container, such as bulk cotton, prevents the tablets from shifting during shipping and maintains the identical non-homogeneous image.

[0074] 10 is an image of an exemplary machine readable code 420 applied to a homogenous marked pharmaceutical asset 400, according to some embodiments. In some embodiments, the tablets can be marked with regular markings or with irregular patterns to add visual variety and increase the heterogeneity of the tablet image. As with FIG. 9, the tablets are similarly physically restrained at the time of packaging, with the transparent portion of the container acting as a UAW 410 for the contents of the container.

[0075] 11 is an image of an exemplary machine-readable code 420 applied to a homogenous pharmaceutical asset 400 with random orientation, according to some embodiments. In some embodiments, the tablets are provided in a blister pack. The heterogeneous image of the tablets may be achieved by random orientation of the homogenous tablets within the pack. The machine-readable code 420 may be placed in an area of ​​the packaging proximate to one or more tablets. The machine-readable code 420 may be affixed in conjunction with a UAW 410 that identifies one or more of the tablets.

[0076] 12 is an image of an exemplary machine readable code 420 applied to a heterogeneous pharmaceutical asset 400 having a random orientation, according to some embodiments. In an embodiment having heterogeneous tablets, the heterogeneous image is achieved by the random orientation of the tablets and the heterogeneous appearance of each tablet. The machine readable code 420 may be placed in an area of ​​the packaging between one or more tablets. The machine readable code 420 may be affixed in conjunction with a UAW 410 that identifies one or more of the tablets.

[0077] The grain of leather or wood can also be used to provide a unique visual image for authenticating leather or wood items. The machine readable code 420 can be applied to the leather or wood item in a temporary manner, such as with a sticker, or in a permanent manner, such as by chemically or laser etching the machine readable code 420 to the underlying asset. FIG. 13 is an image of an exemplary etched machine readable code applied to a leather asset 400, according to some embodiments. The leather asset 400 may be, for example, a handbag, wallet, or leather apparel. The machine readable code 420 may be applied in conjunction with a UAW 410 that identifies a particular area of ​​grain or veining.

[0078] 14 is an image of an exemplary machine-readable code 420 applied to a wood asset 400, according to some embodiments. The natural wood grain provides a non-uniform image that is used to identify either a finished wood product or a wood material. The wood asset 400 may be, for example, a raw building material, a cutting board, a decorative item, a shelf, or a piece of furniture. The machine-readable code 420 may be applied in conjunction with a UAW 410 that identifies a particular area of ​​the wood grain.

[0079] While the principles of the present disclosure have been described herein with reference to exemplary embodiments for particular applications, it should be understood that the present disclosure is not limited thereto. Those having ordinary skill in the art and access to the teachings described herein will recognize that additional modifications, applications, embodiments, and equivalent substitutions are all within the scope of the embodiments described herein. Thus, the present invention is not to be considered as limited by the foregoing description.

Claims

1. 1. A method for authenticating a product, comprising: storing, in the asset verification device, at least one image of at least one heterogeneous visual feature of a first animal or plant protein having at least one heterogeneous visual feature, or at least one image of at least one heterogeneous visual feature of a first group of animal or plant proteins having homogeneous visual features, and at least one machine-readable code associated with the first protein or the first group of proteins, wherein the at least one machine-readable code is located in proximity to the at least one heterogeneous visual feature; scanning at least one image of at least one heterogeneous visual feature of a second animal or plant protein having at least one heterogeneous visual feature or at least one image of at least one heterogeneous visual feature of a second group of animal or plant proteins having homogeneous visual features and at least one machine-readable code associated with said second protein or said second group of proteins; comparing the scanned image or the scanned machine-readable code with the at least one image or the at least one machine-readable code in the asset verification device; and If the asset verification device contains an image or machine-readable code that matches the scanned image or the scanned machine-readable code, then indicating this to the user. A method comprising:

2. The storing step includes: creating the at least one machine-readable code associated with the first protein or the first group of proteins; and capturing said at least one image of at least one heterogeneous visual feature of said first protein or said first group of proteins; 10. The method of claim 1, comprising:

3. The asset verification device databases; and Machine Vision Software The method of claim 1 , wherein the system comprises:

4. 10. The method of claim 1, wherein the asset verification device further stores at least one of authentication credentials, operational data, location data, a timestamp associated with capturing the at least one image, and a timestamp associated with creating the at least one machine-readable code.

5. 2. The method of claim 1, wherein the at least one machine-readable code is affixed to the first protein or the first group of proteins or to packaging on or around the first protein or the first group of proteins.

6. The method of claim 1 , further comprising storing at least one of location data and a timestamp associated with comparing the scanned image or the machine-readable code in the asset verification device.

7. 2. The method of claim 1, wherein the machine-readable code is a Quick Response code, DataMatrix, Aztec, TrillCode, QuickMark, ShotCode, mCode, Beetagg, UPC, or a custom / proprietary code.

8. The method of claim 1 , wherein the scanning step is performed using a verification device.

9. 2. The method of claim 1, wherein storing at least one image of at least one heterogeneous visual feature of the first protein or first group of proteins comprises storing the image, a description of the image, or a combination thereof.

10. 1. A system for authenticating a product, comprising:

1. An asset verification system including an image comparison device and an image data store, the data store storing at least one image of at least one heterogeneous visual feature of a first animal or plant protein or at least one image of at least one heterogeneous visual feature of a first group of food products comprising animal or plant proteins having homogeneous visual features, and at least one machine-readable code associated with the first protein or the first group of proteins, the at least one machine-readable code being located in proximity to the at least one heterogeneous visual feature; an asset registration station in communication with the asset verification system; and an asset verification software application in a verification device capable of communicating with the asset verification system; A system including:

11. 11. The system of claim 10, wherein the data store stores at least one of authentication credentials, operational data, location data, a timestamp associated with the capture of the at least one image, and a timestamp associated with the creation of the at least one machine-readable code.

12. 11. The system of claim 10, wherein the asset verification system includes an asset registration application program interface configured to index new images of at least one heterogeneous visual feature of one or more proteins or a first group of proteins and machine-readable codes associated with the one or more proteins or a first group of proteins.

13. The system of claim 10 , wherein the asset verification system includes an asset verification application program interface configured to respond to a query from the verification device to authenticate a protein or a first group of proteins.

14. 11. The system of claim 10, wherein the at least one machine-readable code is affixed to the first protein or the first group of proteins or to packaging on or around the first protein or the first group of proteins.

15. 11. The system of claim 10, wherein the asset registration station is configured to capture at least one image of at least one heterogeneous visual feature of each of the one or more proteins or first group of proteins and read at least one machine-readable code associated with the one or more proteins or first group of proteins.

16. said asset registration station: at least one camera; at least one light source; and Processor The system of claim 15, comprising:

17. 11. The system of claim 10, wherein the verification device is any device including a smartphone, a smartwatch, augmented reality / virtual reality glasses / headset, or a camera.

18. 11. The system of claim 10, wherein the asset verification software application is configured to capture an image of at least one heterogeneous visual feature of one or more proteins or a first group of proteins and read a machine-readable code associated with the one or more proteins or the first group of proteins.

19. 20. The system of claim 18, wherein the asset verification software application is configured to indicate a response to a user query if the database contains an image or machine-readable code that matches the scanned image or machine-readable code.

20. 20. The system of claim 19, wherein the asset verification software application is configured to capture time information, location information, equipment identifiers, and / or other data associated with the user query.

21. 11. The system of claim 10, wherein the at least one image of at least one heterogeneous visual feature of the first protein or first group of proteins comprises an image, a description of an image, or a combination thereof.

Images