WO2020102688A2

WO2020102688A2 - Computing systems for authenticating products using markers and related methods and devices

Info

Publication number: WO2020102688A2
Application number: PCT/US2019/061752
Authority: WO
Inventors: Wilfred P. SO; Lindsay SPARKS; Koichi Nishimura; Stuart Ogawa
Original assignee: Facet Labs, Llc
Priority date: 2018-11-16
Filing date: 2019-11-15
Publication date: 2020-05-22
Also published as: WO2020102688A3

Abstract

A product authentication system includes an authentication platform that stores product ID data and an ID installer in data communication with the authentication platform. The authentication platform sends encoded ID data to the ID installer and the ID installer installs the encoded ID into a marker in a product.

Description

COMPUTING SYSTEMS FOR AUTHENTICATING PRODUCTS USING MARKERS AND

RELATED METHODS AND DEVICES

CROSS-REFERENCE TO RELATED APPLICATION:

[0001] This patent application claims priority to United States Provisional Patent Application No. 62/768,629 filed on November 16, 2018 and titled“Computing Systems For Authentication Products Using Markers And Related Methods and Devices”, the entire contents of which are herein incorporated by reference.

TECHNICAL FIELD

[0002] The following generally relates to computing systems for authenticating products, including the related methods and devices.

DESCRIPTION OF THE RELATED ART

[0003] The origination of a product (e.g. a thing) is becoming more important to people, as they seek originality and authorship being manifested into a product. It is becoming more and more difficult for people to recognize originality and authorship of a product, since mass manufacturing allows for products to be more easily copied and distributed. This leads to confusion in the marketplace.

[0004] Labeling technologies are used to help improve the confirmation of authorship and originality. These approaches include adding a barcode or RFID tag onto the product.

In another approach, companies will place their stitch, print, engrave, or adhere a logo onto the product. However, these technical approaches are able to be duplicated by copyists.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Embodiments will now be described by way of example only with reference to the appended drawings wherein:

[0006] FIGs. 1 A and 1 B is a schematic diagram of a product authentication system and data flow, according to an example embodiment.

[0007] FIG. 2 is a flow diagram of executable instructions for providing an encoded ID for a given product, according to an example embodiment.

[0008] FIG. 3 is a flow diagram of executable instructions for determining authenticity of a given product, according to an example embodiment.

[0009] FIGs. 4A and 4B are schematic diagrams of installing a marker with an encoded ID during the a product build process, according to different example embodiments. [0010] FIGs. 5A and 5B are schematic diagrams of a dispenser that dispenses markers into product, and the dispenser is in data communication with an authentication platform, according to different example embodiments.

[0011] FIG. 6 is a flow diagram of a process for providing markers for product authentication, and the markers include DNA, according to an example embodiment.

[0012] FIG. 7 is a schematic diagram showing components and operations for integrally incorporating an encoded ID while 3D printing a product, according to an example embodiment.

[0013] FIG. 8 is a schematic diagram showing various owners and their user devices, and the flow of data to facilitate transfer of ownership, according to an example embodiment.

DETAILED DESCRIPTION

[0014] It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the example embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the example embodiments described herein. Also, the description is not to be considered as limiting the scope of the example embodiments described herein.

[0015] FIG. 1 A shows an example embodiment of a system for marking a product with an encoded ID, which can be later used to authenticate the product.

[0016] The system includes an authentication platform 101 , which is implemented by one or more server machines. For example, the authentication platform resides on cloud computing infrastructure. The authentication platform is also herein called an authentication server system. The authentication platform 101 includes, amongst other things, a product ID datastore 102, an ID encoder and decoder module 103, and an encoder and decoder library 104. The product ID datastore 102 stores data about each product. The library 104 stores different encoding algorithms, decoding algorithms, or parameters, or a combination thereof, which are associated with a given product ID or a given client entity, or both. It will be appreciated that a client entity is an organization, person, or other that wishes to have their product marked with an encoded ID using the authentication platform. [0017] The system also includes one or more upstream client devices 105, which act on behalf of one or more client entities. These one or more upstream client devices 105 are in data communication with the authentication platform 101. The authentication platform 101 is also in data communication an ID installer 106. The ID installer 106 installs or incorporates the encoded ID into one or more products 108, 109. In particular, the encoded ID is installed or incorporated into a physical marker 107, which is part of the product. The ID installer is a physical system that writes an encoded ID into a marker. The ID installer is also herein called an ID installer system. In an example aspect, the ID installer wirelessly transmits the encoded ID into a marker that has the ability to wirelessly receive write commands. In another example embodiment, the ID installer transmits write commands by wire to a marker, and the marker has a wired connection with the ID installer. In another example, the ID installer includes physical mechanisms for building a marker and, in the process of building the marker, encodes the encoded ID into the marker.

[0018] In an example operation (operation A), the upstream client device 105 sends data about a given product to the authentication platform 101 , and the platform 101 stores this data in the product ID datastore 102. The authentication platform selects the appropriate encoding algorithm or parameters (or both) from the library 104 and then computes an encoded ID that represents the product. At operation B, the authentication platform 101 sends the encoded ID to the ID installer 106. At operation C, the ID installer 106 installs the encoded ID into a marker 107 that is attached to or part of a given product (e.g. Product-1 108). This operation occurs during the manufacturing, assembly, or predelivery process.

[0019] The product is delivered to a customer. FIG. 1 B shows a downstream process after Product-1 108 has been delivered. A person or entity later wishes to confirm whether or not the product is authentic. This person or entity uses a downstream client device or devices 1 10 to (i) identify itself with the authentication platform and (ii) read the encoded ID from the marker 107 (operation D). These operations within operation D can be done in different sequences, or at the same time.

[0020] At operation E, the downstream client device 1 10 sends the read encoded ID to the authentication platform 101 , and the authentication platform confirms whether or not the product is authentic or not based on received encoded ID.

[0021] At operation F, the client downstream device receives and outputs the confirmation about the authenticity or inauthenticity of the product 108. In an example embodiment, if the product is authentic, then the downstream device 1 10 is provided permission to take action, such as read data from or write data to the product ID store 102 in association with the identified product 108.

[0022] In an example aspect, there is also a third-party device 1 1 1 data interacts with the downstream client device 110 (operation G). The device 1 1 1 is responsive to the downstream client device 1 10 confirming whether the product is authentic or not authentic. The response for example includes displaying an image, showing a light, emitting a sound, etc. In a further example aspect, the device 1 1 1 is further only responsive when it is in sufficiently close proximity to the marker 107.

[0023] In an example embodiment, there are different levels or scores associated with the product, and these can be used to vary the response outputted by the third-party device 1 1 1

[0024] In an example embodiment, the marker 107 includes a visual output device (e.g. a display, one or more lights) or an audio output device (e.g. a speaker), or both, and the marker provides a visual output or an audio output that confirms whether or not the product is authentic.

[0025] The devices and computing systems in FIG. 1 A and 1 B data communicate with each other via a data network, such as the Internet or a private network, or a combination thereof.

[0026] FIG. 2 describes an example process for installing or incorporating the encoded ID into a given product.

[0027] Block 201 : An Upstream Client Entity (via Client Device(s) 105) provides input information to the Authentication Platform 101 . Examples of input information include one or more of: product ID, product data, authorship data, media content, ownership data, digital signatures, encryption keys, etc. For example, the data could include images, videos, audio data, etc. showing the building of the product. The data also includes, for example, care and maintenance instructions. The data also includes authorship data or ownership data, or both, with data formats including one or more of: name, birthdate, contact information (e.g. phone number, email address, messaging account, etc.), video data, audio data, image data, and biological data (e.g. DNA sample, fingerprint data, eye scan or retinal scan data, etc.). This is provided during the manufacturing process of the product.

[0028] Block 202: Authentication Platform 101 selects the encoding algorithm or parameters or both that are associated with the given Client Entity. This selection is made from a library 104 of different encoding algorithms or parameters, or both. [0029] In an example aspect, different client entities are associated with different encoding and decoding algorithms or parameters, or both, which are proprietary to the respective client entities. For example, a first client entity is associated with a first encoding and decoding algorithm, or parameters, or both; a second client entity is associated with a second encoding and decoding algorithm, or parameters, or both; and these associations and encoding and decoding information are stored in the library 104. These associations are kept secret on the authentication platform so that other parties can attempt to replicate the encoding process. In another example, an encoding algorithm is randomly selected from a set of encoding algorithms in the library, and the randomly selected encoding algorithm and the corresponding decoding algorithm identifiers are stored in relation to the encoded ID on the authentication platform.

[0030] Block 203: Authentication Platform 101 generates an encoded ID using the selected encoding algorithm or parameters, or both. In particular, the product ID or other related product data is encoded to generate the encoded ID. For example, this computation is executed by the module 103.

[0031] Block 204: Authentication Platform 101 commands the ID installer 106 to install the encoded ID into the product.

[0032] Block 205: The ID installer 106 installs the encoded ID into the product.

[0033] Block 206: The product is shipped.

[0034] In an example embodiment, the marker 107 is a chip (e.g. a tiny edge device) or a radio frequency ID (RFID) tag that stores the encoded ID. The ID installer wirelessly flashes the marker with the encoded ID. The marker itself is, for example, placed in a hard- to-reach position on or in the product. For example, the marker is installed or incorporated into the product first, and then the encoded ID is wirelessly written onto the marker.

[0035] In an example embodiment, the marker is purposely limited to wirelessly communicate over a very short distance to a device (e.g. 10 centimeters or less, or the device and the marker must be almost touching). In an example embodiment, the marker uses near field communication (NFC) to transmit and receive data. In this way, wireless interaction between the marker and the device proves that the device is physically close to the marker.

[0036] In another example, the marker is 107 is a chip or a RFID tag that has stored on it the encoded ID. After the encoded ID is stored on the marker, the marker is installed or incorporated into the product. [0037] In another example, the marker 107 is a DNA sample, or DNA more generally. The marker can be encoded with DNA to represent the encoded ID. In another example, the DNA is first digitally characterized, and then the digital characterization of the DNA is used to represent the encoded ID that is associated with the product. The DNA marker is, for example, installed or incorporated into the product. In an example embodiment, the DNA marker material is produced as one or more fibers, and these fibers embedded with DNA are woven into the product. In another example, the DNA marker material is encapsulated and attached to or installed on the product. The ID installer includes mechanism that place the DNA or incorporate the DNA into a marker.

[0038] In another example, the marker 107 is a computing chip or memory chip that is 3D printed directly into the product, and the design of the chip is representative of the encoded ID. In other words, in this example, the 3D printer is an ID installer.

[0039] In another example, the marker 107 is an RFID tag that is 3D printed directly into the product, and the design of the RFID tag is representative of the encoded ID. In this example, the 3D printer is an ID installer.

[0040] In another example, the marker 107 is a marker structure that is 3D printed directly into the product, and the design of the structure is representative of the encoded ID. In this example, the 3D printer is an ID installer.

[0041] It will be appreciated that there are other methods of handling the data.

[0042] Turning to FIG. 3, these operations occur after the operations in FIG. 2.

[0043] Block 301 : Downstream client device and Authentication Platform communicate with each other to identify and authenticate the Downstream Client Device

[0044] Block 302: Downstream Client Device interacts with marker at the given product to read the encoded ID.

[0045] The mode of interaction depends on the marker. For example, if the marker is a chip or an RFID tag, the downstream client device digitally interacts with the marker. If the marker includes DNA material or biological material, then the downstream client device uses a biological sensing device to read the marker.

[0046] Block 303: Downstream Client Device sends the read encoded ID to the Authentication Platform

[0047] Block 304: Authentication Platform selects a decoding algorithm / parameters / both associated with the identified Downstream Client Device [0048] Block 305: Authentication Platform decodes the read encoded ID using a selected decoding algorithm / parameters / both, and executes comparison against Product ID Datastore

[0049] Block 306: The Authentication Platform determines: Are both the decoding process and the comparison process successful? If so, the process continues to block 307. If not, the process continues to 310.

[0050] Block 307: includes operation 308 or 309, or both

[0051] Block 308: Authentication Platform sends message that the product is authentic to the Downstream Client Device

[0052] Block 309: Authentication Platform permits the Downstream Client Device to take one or more actions in relation to the data of the given product in the Product ID Datastore

[0053] Examples of one or more actions, as per block 309, include: displaying the product data (e.g. text, audio, video, images, etc.) that is associated with the authenticated product; recording as part of the product data, observational data; recording as part of the product data, a transfer of ownership; triggering another third-party device 1 1 1 to take action.

[0054] For example, a third-party device includes lights that glow in a certain way (e.g. certain color, shape, brightness, etc.) after the client device 1 10 receives confirmation that the product is authentic. In another example, the third-party device includes a display (e.g. LED display, e-ink display, projector display, etc.) that shows a certain image after the client device 1 10 receives confirmation that the product is authentic. In another example, the third-party device includes an audio speaker that outputs a certain sound after the client device 1 10 receives confirmation that the product is authentic.

[0055] Block 310: includes operation 31 1 or 312, or both

[0056] Block 31 1 : Authentication Platform sends message that product is not authentic to Downstream Client Device

[0057] Block 312: Authentication Platform denies Downstream Client Device to take action with respect to the data of the given product in the Product ID Datastore

[0058] FIG. 4A shows an example of one or more upstream client devices transmitting recorded data that was recorded during the product’s build process to the authentication platform. This recorded data, for example, is evidence of the details about the building of the product. Recorded data includes, for example, images, video, manufacturing details, time stamps, machine identifiers, part numbers, composition details, batch numbers, involved personnel, etc. Different types of recorded data can be obtained along different phases of the build process, and this recorded data is associated with the encoded ID. For example, this recorded data forms part of the product related data. In FIG. 4A, the marker and the encoded ID are together installed into the product.

[0059] FIG. 4B is similar to FIG. 4A. However, the marker is installed or incorporated into the product first, and at a later time the encoded ID is installed or incorporated into the marker.

[0060] FIG. 5A shows an ID installer that is in the form of a tiny edge device (TED) dispenser 505 (e.g. an apparatus) is herein provided that dispenses or deploys TEDs. In an example embodiment, the TED dispenser deploys the TEDs like particles or granules.

[0061] A TED herein refers to very small computers with communication capabilities. For example, a TED is a type of loT device. A TED is also sometimes called a mote or smart dust. In an example embodiment, a TED is sized similar to a coin (e.g. 5cm X 5cm).

In an example embodiment, a TED is sized at approximately 1 cm x 1cm. In an example embodiment, a TED is sized at approximately 1 mm x 1 mm. In another example embodiment, a TED is sized at less than 0.5mm x 0.5mm. In an example embodiment, a TED is micro-sized. In another example embodiment, a TED is nano-sized. It will be appreciated that various dimensions of TEDs are applicable to the principles described herein. Smaller TEDs or larger TEDs may be desired to suit the application in which the TEDs operate.

[0062] A TED dispenser 505 includes a container 506 that stores the TEDs, which are the markers 107. The dispenser also includes a computing element 509 and a dispensing mechanism 508.

[0063] The authentication platform 101 is in data communication with the respective computing elements of the dispenser.

[0064] The platform 101 then sends the encoded ID to the computing element 509, and the computing element in turn wirelessly flashes one or more TEDs with the encoded ID(s). These one or more TEDs, which have stored thereon the encoded ID(s), are then dispensed by the dispensing mechanism for installation into the product. The dispensing mechanism 508 is just an example. It will be appreciated that the mechanical form and types of dispensing mechanisms can vary from what is shown.

[0065] FIG. 5B shows a similar embodiment, but a separate data writer 510 installs the encoded ID into the TED at a later time (t2). [0066] FIG. 6 shows a process in which DNA material is obtained from a person (block 601 ). A portion of this DNA material is stored in an Authentication Storage (block 602), which can be optionally used for later comparison. The Authentication Platform 101 also stores the digitized profile of the obtained DNA in association with the product ID (block 603). The DNA material itself is also stored into one or more markers (block 604). For example, the markers 107 shown in FIG. 6 include the DNA material. These markers are then installed or incorporated into the product (block 605).

[0067] In another example, the DNA is from another natural source (e.g. a human, an animal, a plant, etc.). In another example, the DNA is synthesized or modified DNA to provide a unique identifier.

[0068] In another example, a chemical material with a customized chemical composition is stored into one or more markers. To authenticate the marker, a chemical analyzer is used to identify the chemical composition of the chemical material in the marker.

[0069] FIG. 7 shows the authentication platform 101 generating a computer design file (e.g. a CAD filed) for a marker structure that represents an encoded ID (block 702). This computer design file is a derivative of the encoded ID. The ID installer includes a 3D printer 701 , and the computer design file is sent to the 3D printer 701 . The 3D printer prints this marker structure, based on the file 702, while the product is being produced. For example, a component of the product or the entire product itself is 3D printed and, during the 3D printing process, the marker structure is 3D printed to be integral with the component of the product or with the entire product itself. In an example embodiment, the marker structure (which is the marker 107) is 3D printed to be positioned within the body of the product, so that it is inaccessible to others. For example, the marker structure is within an internal cavity of the product. In another example, the marker structure is positioned onto an outer surface of the product. In an example embodiment, the product itself is 3D printed and this process 703 is part of the 3D printing process of the product.

[0070] In another example, the authentication platform 101 sends the encoded ID to the 3D printer 701 , and the 3D printer 701 uses the encoded ID to generate three-dimensional computer design data of the marker structure. This computer design data is then used to 3D print the marker structure.

[0071] In an example embodiment, the marker structure is a unique physical design to identify the encoded ID.

[0072] In another example embodiment, the marker structure reflects or emits radio waves, and is printed to reflect or emit a radio wave signal that corresponds to an encoded ID. In an example aspect, the marker structure includes metal material. In an example embodiment, the marker structure is an RFID tag that stores the encoded ID. The RFID tag can be a passive RFID tag, an active RFID tag, or a semi-active RFID tag.

[0073] In another example embodiment, the marker structure includes an electronic circuit that stores the encoded ID.

[0074] In another example embodiment, the marker structure includes a computer chip that stores the encoded ID.

[0075] FIG. 8 shows a downstream process, in which the product originator 801 transfers ownership to a first owner 803, and the first owner later transfers ownership of the product to a second owner 805. The transfer of ownership to the first owner 803, takes places between the originator account 802 and the first owner account 804, and the recordation of transfer is made with the authentication platform 101. Similarly, the transfer of ownership to the second owner takes place between the first owner account 804 and the second owner account 806, and the recordation of this later transfer is made with the authentication platform 101 .

[0076] In an example embodiment, the present owner (@t2 it is the first owner 803) is able to communicate with the originator 801 over a private communication channel (e.g. send messages back and forth to increase engagement about the product). At the time t3, the present owner is the second owner 805 and now the second owner 805 is able to communicate with the originator 801 over a private communication channel. At the time t3, the first owner 803 and the originator 801 are no longer able to communicate over the private communication channel, since the first owner is no longer an owner of the product.

[0077] Subsequent owners can see the history of ownership, manufacturing data, and other social media data that has been associated with the product.

[0078] In another example, observers 809 can interact with the product, such as by confirming authentication and associating media content with the product (block 81 1 a,

81 1 b). For example, after an observer account 810 is verified by the platform 101 to be in close proximity to the product, and after the product is confirmed to be authentic, then media content obtained by the observer 809 is sent to the platform 101 for storage in association with the given product. For example, a person sees or observes the product in question, authenticates the product by obtaining the encoded ID from the marker (e.g. wirelessly interacting with the marker if it is a wireless device or RFID), and then transmits the encoded ID to the authentication platform using an app or a website. If the obtained encoded ID confirms that the product in question is authentic, then a recorded observation taken using the person’s smartphone is sent back to the authentication platform and stored thereon as an authentic observation in association with the product ID of the product in question. The recorded observations from the person’s smartphone can include one or more of: videos of the product in question, pictures of the product in question, and messages (or other forms of social media) confirming that they have interacted with the product in question, which has been confirmed to be authentic. These observations are time stamped. In another example aspect, these observations are also location stamped (e.g. using local positioning services or GPS). These observations from other people form part of a digital ledger stored on the authentication platform with the product ID.

[0079] In an example embodiment, the authentication platform 813 is in data communication with a social media platform 813 (e.g. Facebook, Linkedln, Instagram, Pinterest, or the like). The authenticated observation is automatically turned into a social posting 812 that is posted from the authentication platform 101 to the social media platform 813. For example, the social posting 812 includes a confirmation that the person observed an authentic product and includes the person’s recorded picture or video of the product. The social posting 812 also include the person’s details (e.g. their social media name) and the observation details (e.g. the time of the observation, the location of the observation, etc.).

[0080] Below are general example embodiments.

[0081] In an example embodiment, a system includes an authentication server system that stores a given product ID, an ID encoder and decoder, and an encoder and decoder library that stores multiple encoder and decoder algorithms. The system also includes an ID installer system that is in data communication with the authentication server system. The authentication server system selects an encoding algorithm from the encoder and decoder library, uses the encoding algorithm and the given product ID to generate an encoded ID, and sends the encoded ID to the ID installer system. The ID installer system wirelessly flashes the encoded ID into a marker in a product, wherein the marker comprises a TED, wherein the TED has wireless communication ability.

[0082] In an example aspect, after the marker is already installed in the product, the ID installer system wirelessly writes the encoded ID into the marker.

[0083] In another example aspect, the ID installer system wirelessly writes the encoded ID into the marker before the marker is installed into the product.

[0084] In another example aspect, responsive to receiving the encoded ID and observation data from a downstream device, the authentication server system decodes the encoded ID to confirm the authenticity of the marker and stores the observation data in relation to the given product ID. [0085] In another example aspect, the observation data comprises video or a picture recorded by the downstream device.

[0086] In another example aspect, the authentication platform is in data communication with a social media platform and the authentication platform automatically generates a social posting that comprises the observation data and an indication that the observation data provided by the downstream device is authentic.

[0087] In another example aspect, the wireless communication ability is near field communication (NFC).

[0088] In another example aspect, the TED is approximately 5 cm x 5 cm or less.

[0089] In another example aspect, the TED is approximately 1 cm x 1 cm or less.

[0090] In another example aspect, the TED is approximately 0.5 cm x 0.5 cm or less.

[0091] In another example aspect, the ID installer system includes: a container that stores multiple markers that each comprise a TED, including the marker; a computing element that receives the encoded ID from the authentication platform and then wirelessly flashes at least the marker; and a dispenser mechanism that deploys the marker after it has been wirelessly flashed by the computing element.

[0092] In another example embodiment, a system is provided that includes an authentication server system that stores thereon at least a given product ID, an ID encoder and decoder, and an encoder and decoder library that stores multiple encoder and decoder algorithms. The system also includes an ID installer system that is in data communication with the authentication server system. The authentication server system selects an encoding algorithm from the encoder and decoder library, uses the encoding algorithm and the given product ID to generate an encoded ID, and sends the encoded ID or a derivative of the encoded ID to the ID installer system, and the ID installer system 3D prints a marker structure into a product, the marker structure representing the encoded ID.

[0093] In an example aspect, the marker structure reflects or emits radio waves, and the marker structure reflects or emits a radio wave signal that corresponds to the encoded ID.

[0094] In another example aspect, the marker structure is a radio frequency ID tag that stores the encoded ID.

[0095] In another example aspect, the marker structure comprises an electronic circuit that stores the encoded ID. [0096] In another example aspect, the marker structure is 3D printed to be positioned within a cavity of the product.

[0097] In another example aspect, the marker structure is 3D printed to be positioned on outward surface of the product.

[0098] In another example aspect, the authentication platform sends the derivative of the encoded ID to the ID installer system, wherein the derivative of the encoded ID comprises a computer design file of the marker structure, and the ID installer system uses the computer design file to 3D print the marker structure.

[0099] In another example aspect, the authentication platform sends the encoded ID to the ID installer system, and the ID installer system uses the encoded ID to generate a digital three-dimensional structure of the marker structure for 3D printing into the product.

[00100] In an example embodiment, a system is provided for authentically marking a product. The system includes an authentication server system that stores a digitized profile of DNA material in association with a product ID, the product ID identifying a product. The system also includes an ID installer system that stores the DNA material into a physical marker that is incorporated into the product.

[00101] In an example aspect, the physical marker comprises one or more fibers, and the one or more fibers are woven into the product.

[00102] In another example aspect, the physical marker comprises a capsule that stores the DNA material, and the capsule is embedded or attached to the product.

[00103] It will be appreciated that any module or component exemplified herein that executes instructions may include or otherwise have access to computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the servers or devices or accessible or connectable thereto. Any application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media.

[00104] It will be appreciated that different features of the example embodiments of the system and methods, as described herein, may be combined with each other in different ways. In other words, different devices, modules, operations, functionality and components may be used together according to other example embodiments, although not specifically stated.

[00105] The steps or operations in the flow diagrams described herein are just for example. There may be many variations to these steps or operations according to the principles described herein. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified.

[00106] It will also be appreciated that the examples and corresponding system diagrams used herein are for illustrative purposes only. Different configurations and terminology can be used without departing from the principles expressed herein. For instance, components and modules can be added, deleted, modified, or arranged with differing connections without departing from these principles.

[00107] Although the above has been described with reference to certain specific embodiments, various modifications thereof will be apparent to those skilled in the art without departing from the scope of the claims appended hereto.

Claims

Claims:

1 . A system comprising:

an authentication server system that stores thereon at least a given product ID identifying a product, an ID encoder and decoder, and an encoder and decoder library that stores multiple encoder and decoder algorithms;

and an ID installer system that is in data communication with the authentication server system ;

wherein the authentication server system selects an encoding algorithm from the encoder and decoder library, uses the encoding algorithm and the given product ID to generate an encoded ID, and sends the encoded ID to the ID installer system, and the ID installer system wirelessly flashes the encoded ID into a marker in the product, wherein the marker comprises a tiny edge device (TED) with wireless communication ability.

2. The system of claim 1 wherein after the marker is already installed in the product, the ID installer system wirelessly writes the encoded ID into the marker.

3. The system of claim 1 wherein the ID installer system wirelessly writes the encoded ID into the marker before the marker is installed into the product.

4. The system of claim 1 wherein, responsive to receiving the encoded ID and observation data from a downstream device, the authentication server system decodes the encoded ID to confirm the authenticity of the marker and stores the observation data in relation to the given product ID.

5. The system of claim 4 wherein the observation data comprises video or a picture recorded by the downstream device.

6. The system of claim 4 wherein the authentication platform is in data communication with a social media platform and the authentication platform automatically generates a social posting that comprises the observation data and an indication that the observation data provided by the downstream device is authentic.

7. The system of claim 1 wherein the wireless communication ability is near field

communication (NFC).

8. The system of claim 1 wherein the TED is approximately 5 cm x 5 cm or less.

9. The system of claim 1 wherein the TED is approximately 1 cm x 1 cm or less.

10. The system of claim 1 wherein the TED is approximately 0.5 cm x 0.5 cm or less.

1 1 . The system of claim 1 wherein the ID installer system comprises: a container that stores multiple markers that each comprise a TED, including the marker; a computing element that receives the encoded ID from the authentication platform and then wirelessly flashes at least the marker; and a dispenser mechanism that deploys the marker after it has been wirelessly flashed by the computing element.

12. A system comprising:

wherein the authentication server system selects an encoding algorithm from the encoder and decoder library, uses the encoding algorithm and the given product ID to generate an encoded ID, and sends the encoded ID or a derivative of the encoded ID to the ID installer system, and the ID installer system 3D prints a marker structure into the product, the marker structure representing the encoded ID.

13. The system of claim 12 wherein the marker structure reflects or emits radio waves, and the marker structure reflects or emits a radio wave signal that corresponds to the encoded ID.

14. The system of claim 12 wherein the marker structure is a radio frequency ID tag that stores the encoded ID.

15. The system of claim 12 wherein the marker structure comprises an electronic circuit that stores the encoded ID.

16. The system of claim 12 wherein the marker structure is 3D printed to be positioned within a cavity of the product.

17. The system of claim 12 wherein the marker structure is 3D printed to be positioned on outward surface of the product.

18. The system of claim 12 wherein the authentication platform sends the derivative of the encoded ID to the ID installer system, wherein the derivative of the encoded ID comprises a computer design file of the marker structure, and the ID installer system uses the computer design file to 3D print the marker structure.

19. The system of claim 12 wherein the authentication platform sends the encoded ID to the ID installer system, and the ID installer system uses the encoded ID to generate a digital three-dimensional structure of the marker structure for 3D printing into the product.

20. A system for authentically marking a product comprising:

an authentication server system that stores a digitized profile of DNA material in association with a product ID, the product ID identifying a product; and

an ID installer system that stores the DNA material into a physical marker that is incorporated into the product.

21 . The system of claim 20 wherein the physical marker comprises one or more fibers, and the one or more fibers are woven into the product.

22. The system of claim 20 wherein the physical marker comprises a capsule that stores the DNA material, and the capsule is embedded or attached to the product.