US20240070233A1

US20240070233A1 - System for verifying digital representation of objects and events

Info

Publication number: US20240070233A1
Application number: US17/983,033
Authority: US
Inventors: Jeremy BLACKBURN; Justin Southward; W. Kurt Taylor; Karl David; Austi Critchfield; Michael Lu; Tim McVicker; Bryan McArdle
Original assignee: Scientia Potentia Est II LLC
Current assignee: Scientia Potentia Est II LLC
Priority date: 2022-11-08
Filing date: 2022-11-08
Publication date: 2024-02-29

Abstract

A system for reporting digital data representing objects or events comprising: a capture device in communication with an immutable storage system; computer instructions adapted to: capture a digital asset identification; retrieve digital asset registration from the immutable storage system according to the digital asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information, a temporal information, an individual information, an object information, an asset type, a creation information, a description, and any combination thereof, displaying a graphical representation of the location, the temporal information includes a date and time the digital asset registration was recorded on the storage system, wherein the creation information includes a validation type, individual information, and a storage type, and, calculate a digital asset rating level according to the validation type, individual information, and storage type, and associate the digital asset rating level with the digital asset registration.

Description

RELATED APPLICATIONS

This application is a continuation in part of U.S. patent application Ser. No. 17/959,923 filed Oct. 4, 2022 which is a continuation in part of U.S. patent application Ser. No. 17/900,624 filed Aug. 31, 2022, which is a continuation in part of U.S. patent application Ser. No. 17/866,256 filed Jul. 18, 2022, which is a continuation in party of U.S. patent application Ser. No. 17/697,839 filed Mar. 17, 2022, which is a continuation in part of Ser. No. 17/686,502 filed Mar. 4, 2022, which is a continuation in part of U.S. patent application Ser. No. 17/566,957 filed Dec. 31, 2021 which is in turn a continuation in part of U.S. patent application Ser. No. 17/561,827 filed Dec. 24, 2021 which is in turn a continuation in part of U.S. application Ser. No. 17/531,746 filed Nov. 20, 2021 which is in turn a continuation in part of U.S. application Ser. No. 17/531,598 filed Nov. 19, 2021 which in turn is a continuation in part of U.S. application Ser. No. 17/344,043 filed Jun. 10, 2021 which in turn is a continuation in part of U.S. application Ser. No. 17/230,911 filed Apr. 14, 2021 which in turn is a continuation in part of U.S. application Ser. No. 17/176,056 filed Feb. 15, 2021 which in turn is a continuation in part of U.S. application Ser. No. 17/128,084 filed Dec. 19, 2020 which in turn is a continuation in part of U.S. application Ser. No. 16/997,840 filed Aug. 19, 2020, which is a continuation in part of U.S. application Ser. No. 16/994,585 filed Aug. 15, 2020 (now U.S. patent Ser. No. 11/232,652 issued Jan. 25, 2022) which in turn is a continuation in part of U.S. patent application Ser. No. 16/991,916 filed on Aug. 12, 2020 (now U.S. patent Ser. No. 11/216,823 issued Jan. 4, 2022) which in turn is a continuation in part of U.S. patent application Ser. No. 16/876,080 filed May 17, 2020 which in turn is a continuation in part of U.S. patent application Ser. No. 16/810,782 filed on Mar. 5, 2020 (now U.S. patent Ser. No. 11/216,781 issued Jan. 4, 2022) which in turn is a continuation in part of U.S. patent application Ser. No. 16/510,634 filed on Jul. 12, 2019 (now U.S. Pat. No. 10,713,737 issued Jul. 14, 2020) and U.S. patent application Ser. No. 16/510,642 filed on Jul. 12, 2019 (now U.S. patent Ser. No. 11/216,772 issued Jan. 4, 2022), which are all incorporated by reference. Patent Application Nos. 16,510,542 and 16,510,634 are both continuations of U.S. patent application Ser. No. 16/452,076 filed Jun. 25, 2019, which all are incorporated by reference.

BACKGROUND

1) Field of the System

A system for immutability verifying, recording, and storing digital representation of physical object and events including associating the object or event with an identifier which can include a unique identifier that is received by the system or created by the system.

2) Background

With the increasing use of technology, all industries face risk and compliance challenges both with authentication of digital information as well as authentication of such digital information. This is especially true with the increased use of digital technologies such as paperless transactions, financial institution systems, property ownership records, crypto-currencies, digital art, NFT's, tokens, digital assets, digital information, and the like. Further, technologies such as blockchain that are designed to allow for distributed storage is data without modification to the data are being used for cryptocurrency to increase security reduce risk in alteration of the data as well as to provide for non-fungible tokens (NFT) where the NFT can be associated with a digital art and other digital assets.
These new technologies has led to an increased focus on systems that are designed to manage governmental, risk, audit, and compliance (GRC). For example, digitizing governance materials allows access in real-time to industry and competitor data and can assist an organization to act timely on opportunities. Due to the importance of GRC data, secure storage and communications is needed while also allowing the sharing of specific information, both confidentially and publicly, with third parties. While GRC systems are designed to provide for entities to reach key objectives, analyze and evaluate data, proactively spot risks, and take advantage of opportunities in a timelier fashion, they rely on the data that is received without verifications or authentications.
Further, there is a trend for digitization that includes attempts to create digital representations of physical objects so that the physical objects can be properly and accurately represented. Historically, digitization focused on creating a digital scan of a physical object so that the digital information can be manipulated by information systems and stored on a database. For example, a bank balance can be the digital representation of the fiat currency that is in the possession of the bank account holder. A digital photo can be a representation of an oil painting. While these systems are sufficient for fungible objects such as currency, there is a challenge when the object is not fungible. For example, during the manufacturing of a good, components for that good can be specific to that good and are not readily substituted between different goods. Another example is when the digital representation is of a physical object that has unique significance such as sports memorabilia (e.g., the XXXth homerun ball). Therefore, traditional methods of tracking objects such as with barcodes are not sufficient. The barcode, for example, does not necessarily capture the changes to the object nor transactions or events that are associated with the object. The barcode cannot record events that are associated with an object such as repairs. This disadvantage is evident when a replacement part is used that, while using the same barcode, the replacement part is recorded as the original part losing valuable information about the object.
Another disadvantage of blockchain is that the inability to verify transactions is generally limited to miners wherein the mining process is essentially the verification of a transaction. A transaction is the verification of preceding data blocks as well as confirmation of the current block. There have been some attempts to create verification systems, but none has proven to have sufficient accuracy needed for commercialization of these systems. For example, U.S. Patent Application 10,790,963 uses a pattern count calculator that calculates the number of transaction patterns for a generating party using the blockchain generation apparatus. This requires that an identifier of the generating party is used with a block generation condition checker to determine whether the generating party is qualified to generate the new blockchain data.
Proper digitization involves the digital information representing the physical asset. The current state of the art only includes electronic scanning of physical assets which is not authentication or verifications. Electronic scanning simply creates a digital copy that is separate from the physical object and becomes an independent object itself. Despite the illegality of this example, the digital scan of US currency and the US currency itself are not equivalent. The US currency can be spent without reference or modification of the digital scan and the digital scan can be manipulated without reference or modifications to the US currency. The inability to pair (e.g., provide a logical and virtual connection between the two that can be verified, including immutable verification) the digital representation with physical object makes traditional digitization of physical objects challenging as the digital object and the digital representation are not functional equivalents and therefore inadequate.
There is also a need to verify past and current transactions that are stored on an immutable ledger. Currently, there is a lack of accountability, verification and reliability between physical objects and digital representations. Further, there is no ability to determine the confidence of a immutable storage system or its use and the industry treats each immutable system (e.g., blockchain) equally. Unfortunately, this is not the case. The inability to rate the storage system and therefore the information stored thereon is a need in the industry.
Current systems do not rate the storage system, or the data stored thereon. The inability to audit, verify and rate the system and data is a need in the industry. Further, previous attempts to verify transactions fail to pair a physical object with a digital representation, disadvantages that can be seen in United States Patent Application Publication 20190303919.
It would be an advantage to have a system that can audit, rate and verify the immutable system, the storage process and the data stored thereon.
It would be advantageous to have a system that can provide for multiply ratings of the system, storage process and data stored thereon.

SUMMARY OF THE SYSTEM

The computerized system can include a system for reporting a digital asset representing objects or events comprising: a capture capture device in communication with an immutable storage system; a set of computer readable instructions that when processed by the capture device are adapted to: capture a digital asset identification; retrieve digital asset registration from the immutable storage system according to the digital asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information, a temporal information, an individual information, an object information, an asset type, a creation information, and any combination thereof, displaying a graphical representation of the location information, wherein the temporal information includes a date and time the digital asset registration was recorded on the immutable storage system, wherein the creation information includes a validation type, individual information, and a storage type, and, calculate a digital asset rating level according to the validation type, individual information, and storage type, and associate the digital asset rating level with the digital asset registration.
The system can include a blockchain system and the creation information can include a blockchain location where the digital asset registration is stored. The system can include the storage location of data, data unit and data block on a storage system including a immutable storage system. The system can include a remote database is communications with the set of computer readable instructions and the object information is a digital token, and the set of computer readable instructions are configured to retrieve a secondary object information from the remote database according to the digital token and display the secondary object information to a user. A validation type can be determined from hardware classification and software type associated with a creation of the digital asset registration and the validation of the creation of the digital representation. The identification level can impact a data asset rating level and can be taken from the group consisting of government witness, government identification, secondary identification, witness configuration, user interaction events and any combination thereof. The system can receive user identification information, user temporal information and user location information. The digital asset registration can include a digital representation of a physical object, service, or event or can be a representation of digital asset such as digital art.
The immutable storage system can be a blockchain system and the storage type that can impact the digital asset rating level can include information taken from the group consisting of number of nodes, number of active nodes, number of transactions, time between transactions, time between clock confirmation, staking value, blockchain type, storage latency, and any combination thereof. The individual information includes individual metadata according to user identification information, user location information, and user temporal information. The remote database can be in communication with the set of computer readable instructions and the digital asset registration includes a token associated with a linked information taken from the group consisting of an image, a video, a document, description, and any combination thereof and the set of computer readable instructions are configured to retrieve the linked information from the remote database.
The digital asset rating level can be calculated according to a digital asset registration record type taken from the group consisting of genesis record, product record, witness record, creator record, industry record, immutable storage system type, storage record type, and any combination thereof. The digital asset identification cam be configured to be immutable associated with a digital asset registration using a non-fungible token stored on the immutable storage system. The location information can be created according to a global positioning service, wireless access point, cell tower, IP address and any combination thereof. The system can include receiving, storing and otherwise using validation information from a user and associating the validation information with the digital asset registration.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A through 1D are diagrams of aspects of the system;

FIG. 2 is a diagram of aspects of the system;

FIG. 3 is a diagram of aspects of the system;

FIGS. 4A and 4B are schematics of aspects of the system;

FIG. 4B is a schematic of aspects of the system;

FIG. 5 is a diagram of aspects of the system;

FIG. 6 is a diagram of aspects of the system;

FIG. 7 is a diagram of aspects of the system;

FIG. 8 is a schematic of aspects of the system;

FIG. 9 is a schematic of aspects of the system;

FIG. 10 is a diagram of aspects of the system;

FIGS. 11A and 11B are schematics of aspects of the system;

FIG. 12 is a schematic of aspects of the system;

FIGS. 13A and 13B are schematics of aspects of the system;

FIGS. 14A through 14E are flowcharts of aspects of the system;

FIG. 15 is a flowchart of aspects of the system;

FIG. 16 is an illustration of aspects of the system;

FIGS. 17A and 17B are schematics of aspects of the system.

DETAILED DESCRIPTION

The present system provides for verified pairing of a physical object with a digital representation. The system can include a computer device, capture device and computer readable instructions that can provide computer systems that can be in communications with an internal database, a second database, a immutable storage system and any combination. Each of the data storage systems can be centralized, decentralized, immutable, distributed, local, remote, shared, private, virtual and any combination. The first data storage system can differ from the second data storage system. The first and second data storage systems can be immutable and persistent so that the information stored on the data system, once storage, cannot be changed. The data systems can include a plurality of computer systems where data can be copied onto each computer system. Examples of data storage platforms include hard drives, solid state drives, tapes, and cloud storage systems. The immutable data storage system can use blockchain, crypto-shredding, WORM, append only, distributed ledger technology, immutable cloud storage, immutable record retention (e.g., Oracle Cloud Infrastructure Object Storage, Quantum Ledger Database, and any combination thereof). In one embodiment the immutability is accomplished by the data storage system only allowing records to be appended to the storage media without the ability to modify the record once written. One such system includes blockchain.
Referring to FIGS. 1A through 1C, computer device 102 can be in communication with a database 103. A first record 114 can be associated with a first object or event 116 a and a second record 120 can be associated with a second event 116 b. The system can also capture and store user information, object information and event information which can be in the form of records. The captured information can be performed at a first time represented by 112 a and at a second time represented by 112 b. Additional computer device and capture device 110 and 118 can be used to capture information in this system.
In one embodiment, the order in which the first record and the second record are written on the immutable storage can be used to show that some period of time elapsed between the first record and the second record. This functionality can add to the verification process as attempts to improperly tamper with the immutable storage may be discovered when the first record and the second record are not in chronological order. This functionality can also apply to, include, and verify items, people, places, association, activities, events as well as confirm previous recording and storage of such information. For example, the system can capture user information, object information, event information and any combination such as capturing a digital representation of a physical object. The system can create a capture record representing the verified association of the digital representation with the physical object. The system can capture and record subsequent information about the object or event such as a subsequent transaction (e.g., in person authentication). A second capture record can be created and associated with the first capture record creating a history of objects and events. When this information is captured and stored, attempts to improperly tamper with the immutable storage can be discovered when the metadata of the first record and the second record are inconsistent with the first record and the second record as stored.
The first event record can be associated with a first event and the second event record can be associated with a second event. The data associated with these events can be retrieved from the capture device and used in creating and writing the associated event record. If the date and time setting of the computer device are incorrect, this discrepancy can be identified by comparison with the event record created and compared to related records in the immutable storage. In one embodiment, metadata integrity used by the system can be designed to identify inconsistencies with date and time. For example, a capture sensor or capture device can include a camera, scanner or other input device can be used to capture one or more images from an object or project, such as materials at a construction site. The data can include metadata associated with user, object, or event. Any error or inconsistency in the respective metadata can be identified by comparing the metadata and the hash/block time of the metadata that was committed to the immutable storage system. The difference can be a discrete comparison or can be a determination that the information is within a range. The verification can be used to create a verification record. When there are inconsistencies, notifications can be sent to a user. This notification allows the users to remedy any consistencies as well as determine authentication and verifications. and mitigate such errors in the future.
The first event can differ from the second event by time, activity, process, location, or any combination. In one embodiment, metadata associated with the event and event record and a ledger hash time, representing when the event record is stored (e.g., committed) to the immutable storage can be used to validate the metadata provided from the computer device. If the computer has an incorrect time, a comparison of the ledger hash time with the metadata from the computer device can identify an error. Identifying an error can be used to alert users to computer device issues and can indicate that the computer device needs to be serviced or replaced prior to its next use.
In one embodiment, the metadata that can be associated with the capture device can include weather conditions, which can include a sun angle, which can be compared with environmental weather conditions to approximate the data capture time. Metadata associated with an image of video can be used to verify weather conditions in the image or video. Time and location metadata can be retrieved from public sources or remote sources and captured with the device metadata to determine of the captured weather in the image or video is the same as being reported locally on that day and at that time.
In one example, a camera included in a computer device can be the capture device and images, or video captured from the computer device of a physical object can show the object at a time and location. In the event that the image or footage is disputed, metadata that can include location, date and time and comparing weather visible in the image or footage to reported weather conditions to add verification to the metadata. In one example, data associated with a worker, such as a vehicle, license plate, of other indicia can be captured by the computer device and capture device. For example, if a license plate can be captured, the license plate information can be compared with public data and the attendance of the worker at a location or physical object can be verified.
The metadata that is captured can be dependent upon the device and can include metadata associated with a worker, equipment, weather, enterprise software, security hardware and software, material, indicia, smart contracts, public records, authentication information, date, time, location, entity, and any combination of these examples. The biometric data may include facial recognition, an iris/retinal scan, a fingerprint scan, a hand scan, a voice print, or heart rate signature and any combination.
In one embodiment, an image or video captured can be used to identify an approximate object, event, time, location, and other data. The computer device can capture data in response to an event associated with the physical object. For example, if the physical object changes location, is modified, transferred, integrated, or other action, process or procedure associated with the physical object can signify an event.
A location can include a manufacturing place, construction site, business providing services, origination site, delivery site, event site, or other location where an object or materials will be used including the creation, collection, maintenance, repair, use, or integration of the object or material.
Verification, including verification of an event, can include verifying that the physical object and the digital representation match and can be accomplished in a variation of methods including interaction with identification elements such as a sticker, tag, label, physical features and the like, capturing an image of the object or event, capturing a video of the object or event, capturing indicia such as a tag physically affixed or otherwise associated with the material, human visual inspection, and any combination. Identification of an individual performing or otherwise associated with an event can be captured by identification devices (e.g., cards, tags, RF ID) and biometrics including visual capture (e.g., facial recognition), voice recognition, iris scan, fingerprint, palm print, weight, dimensions, change in weight, dimensions or other attributes, and any combination. Examples of verification processes can include having stored data about the physical object and comparing the physical object with the date, using machine learning process video, using imagery, audio clips and other media to and any combination. Individual human inspectors can be used to verify physical objects and events onsite and offsite. Individuals can process video, imagery, audio clips and other media to verify assets and events and provide the verification to the system at one or more events. Upon verification of an event, smart contracts can be executed according to verification of the physical object and event.
The first computer device can also capture object data associated with the physical object. Object data can include an image of the physical object, tag, label, RFID, weight, dimensions, and other indicia and any combination thereof. The object data can be captured at a first event that can include a change in state of the physical object, change in location, change in time or any combination thereof. When an event occurs, which can be a second event, a second computer device can have a second capture device metadata originating from the data device that can be included in the second record. The second computer device can also capture object data associated with the physical object at the second event.
The first capture device metadata and object data can be used to create the first record which can be a first event record. The first event record can be stored on the immutable storage. The second capture device metadata and object data captured by the second computer device can be used to create the second record which can be a second event record. The second event record can be stored on the immutable storage. Immutable storage can be a storage medium or system where the data or object being stored cannot be changed or modified after its storage.
During data capture by the first computer device, object indicia can be capture where the object indicia is associated with the object. The object indicia can include a still image of the object, a label affixed to the object, a radio frequency identification (RFID) tag, an ultra-high frequency (UHF) tag, a bar code, a QR code, a Bluetooth beacons, alpha-numeric characters, and any combination thereof. The object indicia can be included in the first event record and stored on the immutable storage. When a change in time, location or other event occurs the second computer device can capture the object indicia. Once captured, the object indicia can be compared to the object indicia in the first event record and if the two matches, then verification exists that the physical object associated with the second event is the same physical object that was present at the first event. In one embodiment, the second capture device can capture data, transmit the data to the computer system 102 and computer readable instructions on the computer system can perform the comparison of the object indicia capture as the second event with the object indicia included in the first event record.
Computer readable instructions on the computer device can capture the user information, object information and event information. The user can include the username and password. In one embodiment, the user can be associated with digital storage such as a digital wallet. The user information that is received can be used for verification of the identity of the user. The user can provide biometric information that can be compared to a local or remote database of identification information and the user using the computer device verified. The object information can be captured and can include metadata related to the object including file types, creation dates, file attributes (e.g., format, compression, protocol, and the like), names, headings, and other data about the object and object information. The object information and the event information, along with its metadata can be compared metadata such as location and time to verify that the object information and the event information are authentic. The system can create a capture record which can be information about the capture of the object and event information and the capture record can be stored on the immutable storage system. Therefore, the capture record can be subsequently retrieved and compared with the original or subsequent object and event information for validation. The object information and the capture information can include an unique identifier associated with the object or event.
The system can retrieve a first capture record and a second capture record and compare the respective records to determine of the physical object is the same physical object at the first event and the second event. If the capture record does not include consistent information, a notification can be provided indicating that the physical object has been changed, modified or otherwise different between the first event and the second event.
In one embodiment, a first computer device can capture user information, object information and event information, create a first capture record, and store the first capture record on the immutable storage system. A second computer device can retrieve the first capture record from the immutable storage and compare object information captured by the second computer device with the first capture record and first object information to validate the digital representation of the physical object. The first computer device and the second computer device can be the same device.
The system can therefore pair the physical object with a digital representation, such as a unique identifier, and verify among objects and events that the physical object has not been improperly changed. This system can provide for verification at each event that the physical object has not been replaced, modified, or otherwise changes. An event record created with this process can have a verification code associated with is so that validity of the event record can be determined.
Referring to FIG. 1D, a digital asset 126 can be created digitally and can be associated with a digital asset identification 128. A digital asset can include a digital representation of a physical object, originally created digital information and other digital data, records and information. The digital asset can be digital artwork, for example. The digital asset can be stored on an immutable storage system 130 with metadata 132 and associated with the digital asset identification so that the digital asset identification can be used to retrieve the stored data. The stored data can include a token 134 that can be used to reference data that is stored on another storage system 136. The token can be an object token that is stored in a first location and references to data or other digital information stored at a second location. The token can be verifiably paired with the data or other digital information. Therefore, data associated with the digital asset identification can be stored “off chain” as well as with the data on the immutable storage. This allows data that is stored on storage system 136 to be deleted even when a portion of the data associated with the digital asset at stored on an immutable storage system. In one embodiment, the capture device 124 can be used to capture a digital representation 138 of a physical object 140. The digital asset identification 128 can be associated with the digital representation as well as can be associated with the physical object. In one embodiment, the digital asset identification 128 b can be a physical object (e.g., QR sticker or integrated into the physical object) which can be digitally captured as 128 a. The data stored as described herein can be referred to as the digital asset registration. The digital asset registration can include information 138 such as who created or captured the information that is stored on the immutable storage. This information can include the identify of individuals including the creator of the digital asset registration, an individual that validates the creation and storage of the digital asset registration, inspector of the physical object, digital representation and the digital asset registration and the information (e.g., metadata) that is associated with the digital asset registration. The information included with or associated with the digital asset registration can include one or more locations associated with the digital asset registration such as the location where the digital representation was created, the location of an event that is associated with the digital asset registration such as a sporting event, transaction including a transfer of possession and ownership, verification of the pairing of the physical object with a digital representation, the creation of a digital asset (e.g., digital art), and the like. The information included with or associated with the digital asset registration can include a date and time. One or more dates and times can be included and can represent activity and events such as the date and time the digital representation is created, the date and time the digital asset registration is stored, verified, transferred, stored and the like. The information included with or associated with the digital asset registration can include the storage platform for data including the digital representation and the digital asset registration. For example, the digital asset registration can be on an immutable storage system such as Avalanche, Cardano®, Chainalysis KYT, Ethereum®, Hyperledger Fabric, Hyperledger Sawtooth, IBM Blockchain®, Polkadot® and others and in any combination. The digital asset registration can include a digital representation of a physical object or a digital object that can include a storage location on a storage system, including an immutable storage system.
Referring to FIG. 2 , one embodiment the user of a computer device can be verified at 202 so that the user can be authorized to use the computer device or to perform data capture at the first event. The computer device can be authenticated at 204 representing the computer device is the correct computer device and is in working order. The metadata that can be captured by the computer device can include a location, a time and additional metadata shown as 206. The user can be a first user and in one embodiment a second user of a computer device can be verified at 208 so that the user can be authorized to use the computer device or to perform data capture at the first event. A second computer device can be authenticated at 210 representing the computer device is the correct computer device and is in working order. The metadata that can be captured by the computer device can include a location, a time and additional metadata shown as 212. In one embodiment, the first event record and the second event record can be committed to immutable storage such as blockchain using validation nodes included in the immutable storage structure. A validation 214 can be created and stored. The event record E₁, which can be represented by data taken from U₁, D₁, L₁, M₁, T₁, or other data, can have a validation code V₁. When the even record is retrieved, a second validation code Via can be determined and compared with V₁. If these validation codes match or are within an acceptable range, validity of the data from storage to retrieval can be determined.
Referring to FIG. 3 , in one embodiment the second event record 304 can be linked to the first event record 302 to create a digital audit trail 300 that includes object indicia verifying that the physical object remains the same physical object throughout a process or where the physical object was modified, changed or otherwise different during the process. A validation record can be created for the first event, the second event, the first plus second event and any combination including the inclusion of n additional records. The system can also record changes in the event or object including changes in the locations, time biometrics of an associated individual, thereby providing an audit trail of the changes.
One example of the invention can include when a material is selected for transport by the supplier, a shipping company can be sent a shipping order representing the material to be transported, an origin and destination. The shipping order can be provided directly to the shipping company or can be retrieved from the immutable storage. Once the shipping company receives the shipping order, it can travel to the origin and receive the material which can represent a first event, and capture data associated with the first event. A first event record can be created representing that the shipping company received the materials and pair the received material with object indicia. In one embodiment, verification that the material is associated with the object indicia can be performed by an individual receiving the material.
Once that material is delivered to the destination, the shipping company can unload the material, a second event, a second verification can occur verify that the material that was delivered to the destination was the same material received at the origin. A second event record can be created representing that the material was delivered and that the material matches the material at the origin and described on the shipping order. The second event record can include the environmental conditions when the material was delivered, delivery notes and the like. The destination can be a receiving entity that can create a third event record representing that the material ordered was received. The receiving entity can use a third computer device to capture the object indicia and create a third event record. The computer system second computer device and third capture device can verify that the delivered material matches the ordered material, and that the material has not been modified, changed, substituted, or otherwise different from the origin to the destination.
The receiving entity can use a computer device that can include biometrics or other indicia to verify that workers using the material are authorized and have the necessary licenses, work certifications, experience, authorizations as well as for verified payroll and insurance coverage. The verification can be through biometric identification devices such as a camera or other image capture device, facial recognition, voice recognition, retinal scans, fingerprint scanners, hand scanners, and other biometric devices. In one embodiment, the computing logic may allow authorized individuals to manually enter the presence of another authorized individual, including on the controller at the project location or through a remote device that can be determined to be at the project location, within a boundary associated with the project location, in proximity to the system. In one embodiment, individuals may be verified and paired with a digital representation using two-factor authentication.
The receiving entity can be uniquely associated with a location. A location marker can be affixed at the receiving entity and uniquely identify the receiving entity and in one embodiment, a project location. The location marker can be read by a computer device and provided to the computer system and the immutable storage. In one embodiment, the receiving entity can receive metadata such as a shipping identifier associated with the delivery, including a truck, trailer, pallet, or other container so that the materials are known to be received at the project location.
In another example, the system can be used for the recording, authenticating and validation of objects and events such as sporting events and the objects that may be assisted with such an event. For example, a sports fan can obtain an object (e.g., catch the xxxth homerun ball) as the event. The system can be used to record the object (e.g., ball), the date, time, location, and the sports fan. A unique identifier can be created or capture that is associated with the object, such as a tag or label. And digitally record with the associated metadata. The event (e.g., sports game) can also be captured including a image or video of the event, date, time, location and sports fan. This information can also be recorded. A capture record can be created including the user information, object information, event information and any combination can be recorded on the immutable ledger. A identifier, such as a barcode or QR code, can be created or captured and associated with the capture record so that when the identifier is capture (e.g., scanned or imaged), the capture record can be retrieved and the digital representation of the physical object or event can be verified by compression of the data in the capture record with the p[physical object or event.
The computer system can be contained in a housing such as a kiosk and can be physically associated with a project location. The project location can be defined by a boundary representing the perimeter of the physical location. The system can include a sensor and reader which can be selected from the group consisting of radio frequency identification (RFID) detector, ultra-high frequency (UHF) detector, a bar code scanner, a QR code scanner, near frequency communication (NFC) device; Bluetooth beacons, an optical character recognition (OCR) device and any combination thereof. An environmental sensor, such as a weather sensor or weather station, can be in communications with the or included in the housing and configured to record the weather and other environmental conditions at the location and at different times during the project. If the environmental sensor detects a change in the environmental condition, it can represent an event.
The system may record the date and time of events such as the arrival and departure of materials, individuals, workers, supplies, third parties, inspections, and the like to and from the project location, the date and time associated with environmental conditions including weather. The environmental conditions can be used to modify the schedule for workers so that workers are not working during inclement weather, tasks are not preformed outside specified environmental conditions, and materials are delivered and installed during specified environmental conditions.
The system may track the movement of material at a project location or during a process or to and from the project location thereby creating an audit trail associated with the material. Scanning technology such as RFID readers, UHF readers and/or the like may be utilized to assist the location tracking for tools, equipment, materials and even workers. Tracking the material assists with reducing the risk of loss, theft, mis-delivery, and the like. For example, the tracking solution may indicate instances of possible theft, such as when the materials are leaving the project location when the removal of the materials is not proper.
The system may allow for the establishment of one or more geofenced zones that can be associated with delivery areas, worker entrance exit areas, task areas, storage areas, assembly areas, distribution areas and any combination thereof. These areas could be monitored and established with access allowances or restrictions to control movement of material, individuals, and equipment to assist with the prevention of loss, mistakes, inefficiencies, and damage. The system can assist with verification that materials stored-on locations are consistent with specifications associated with the materials. A first event can be the material being deposited at a location in a first zone and a second event can be the material being deposited at a second zone. The first event can be associated with the object at a first zone and a second event can be associated with the object in the same zone, at a later time.
The system can also use smart contracts associated with events and stored on the immutable storage that can be self-executing upon satisfaction and verification of contractual terms and objects associated with an event. For example, when an object is delivered from a shipper to the receiving entity and the receiving entity verifies that the object was properly delivered, a smart contact that instigates payment to the shipper can be performed.
Referring to FIGS. 4A and 4B, in one embodiment the computer system can be contained in a housing 404 can be physically associated with the project location, virtually associated with the project location or both. The housing can be a kiosk in one embodiment. A unique location marker can be disposed at the project location to uniquely identify the project location. For example, a transmitter such as a RFID can be associated with the project location by embedding it is a permanent fixture such as a concrete slab, foundation, structure, and the like. The system can read the information from the location marker and associate its actual location with the project location. The location marker can include alpha, numeric, or graphical information such as a number, letters, barcodes, QR code, physical or geographic coordinates (e.g., GPS coordinates), passive transmitter, active transmitter and the like. Each system can have a unique identifier and each project location can have a unique identifier.
A first side of the system can include a camera 402 for obtaining images of materials, equipment, individuals, or other items entering or leaving the project location as well as images of individuals along a perimeter. The camera 402 may capture biometric images upon which biometric recognition may be performed. Multiple cameras may be placed on or around the housing. The cameras may have biometric recognition and motion detection capabilities. System 400 may include one or more cameras 402 that can be used as biometric-based identification devices to confirm the identity of individuals entering, leaving or on the perimeter of the project location. The system 400 may include an antenna 406 for communicating with a network including a wireless network, Wi-Fi network, Bluetooth, quantum networks, cellular network (e.g., 4G or 5G network) and any combination. The system 400 may include a housing 404 made of suitable weather resistant material, appropriately sealed to protect the internal hardware. The system 400 may include a display 416, such as a touchscreen display, upon which information may be displayed and entered. The display 416 may include an integrated camera that may be used to capture images and that may be used in performing facial recognition of individuals. The display may also include or operatively associate with one or more integrated speakers for providing audio output, a microphone for receiving audio information to facilitate two-way communications to a remote location. The system 400 may include a scanner 412 for scanning items, such as deliveries, as will be explained in more detail below. The scanner 412 may be, for example, a QR scanner, barcode scanner, an Optical Character Recognition (OCR) or another scanner 411 in some instances. Actuators such as button 410 can be carried by the housing and connected to a controller, computer medium, computer of other information processing device. One side of the system 400 can be used for deliveries and inspections. A delivery person may scan delivered materials, equipment, or other items via the scanner 411 or 412 and may interface with the system using the touch screen display 416. An inspector may scan or take images of inspection documents via the scanner 411 or 412 or camera and may interface with the system using the touch screen display 416. In some embodiments, there may be fewer sides in which to interact with the system for all authorized personnel. An overhang may be provided to assist in decreasing glare and protecting some of the items on the housing from the weather.
Another side can include a touch screen display as well as a scanner 412. Display 416 may include or be operatively associated with an integrated camera for capturing images, speakers for providing audio output and a microphone to facilitate two-way communications with a remote location. Still further, this side of the system may include data ports. The system may be accessed to gain access to equipment, tools and to sign in or sign out when leaving or entering the project location, as will be described below.
Another side of the system can include location 420 where information such as permits, specifications, instructions, tax information, plans, and the like and may be displayed. In some embodiments, the information displayed may assume electronic form so that a video display is provided in the housing. A tax map submap (TMS) number for the project location may be displayed on the housing. Other location identifying information can be displayed such as location number, store number, assembly number, area within the project location and the like. In addition, the site address may be displayed on the system. The site address may refer to both the mailing address for the project location and/or other physically identifying information associated with the location.
Another side of the system can include an access panel 422 may be provided to access a breaker box for the system. An additional access panel 424 may also be provided to access internal components of the system. Still further, access panel 424 may be provided to gain access to a power source for providing power at the project location. The access panel 418 may be under programmatic control in some instances to regulate access to the power source. If access is granted, the panel is unlocked, whereas if access is denied, access panel 418 is locked. In some embodiments, access to the power supply may be controlled by controlling the flow of power to the power source under programmatic control from the controller. These control mechanisms may be used separately or in conjunction.
Referring to FIGS. 4A and 4B, housing 404 can include a worker side that is configured to be used by a worker at the project location. The housing can include an alarm indicator 407 that can be actuated as described herein. The housing can include a weather station 405 that can include an integrated or separate fluid (e.g., rain) collector. Biometric reader 414 can include an iris scanner, fingerprint scanner, palm print scanner, facial scanner, or some combination. Display 416 can be proximity to input assemblies such as buttons 410. The housing can include a field receiver 430, lights 432 and camera 434. One or more cameras can provide a 360° field of view and include a wireless connection for transmitting images to a remote computer device. The images can also be used for input to the system including input allowing the system to identify delivered materials. The system can include one or more second cameras 440 such as webcams disposed at various locations around the system for capturing images. The lights can include motion activation and photoelectric activation. Speakers 436 can be included to provide audio information to a user, worker, inspector, or other party using or near the system. The audio information can include instructions, alarms, and the like. Power junction can include a shut off switch that can be used in emergency and non-emergency situations. The system can include a secondary power source, such as a battery, so that when the main power is shut off, an alarm can sound, notification send to a remote computer device or other indication that the system or power source has been powered down. The system can include a hand scanner (not shown) that can be protected by a hand scanner access door. A document scanner 412 can be included in the system for receiving physical documents, converting the physical document into a digital representation, and storing the digital representation on the computer readable medium or the immutable storage. The system or housing can include electrical outlets 418 for providing power to various tools and equipment at the project location including recharging batteries. The system can include a wired connection to remote computer devices of a transceiver to provide a wireless connection to remote computer devices.
Referring to FIG. 4C, the computer device and the capture device can be mobile devices. In this example, the capture device 440 is attached to the computer device 442. The computer device can include a camera 444, display 446 and microphone 448 and speakers 450.
FIG. 5 depicts components that may be included in the system of exemplary embodiments even when not included in a housing. The system may include a computing device 502. The computing device 502 may take many different forms indicating a desktop computing device, a laptop computing device, a mobile computing device, an embedded system, a smartphone, special computer device, custom computer device, or the like. A display 504 may be integrated with the computing device 502 or as a separate device, such as a liquid crystal display (LCD) device, a light emitting diode (LED) display device or other types of display devices on which computer information may be displayed. One or more biometric-based identification devices 506 may be provided. As will be explained in more detail below, multiple biometric-based identification devices may be used. Network interfaces and modem 508 may be provided. The network interfaces may interface the computing device 502 with a local area network or a wide area network wherein the networks may be wired or wireless. A modem may be provided to communicate telephonically or over cable lines with remote computing devices.
The system 500 may include various scanners and readers 514, such as those described above relative to housing. The system 500 may include a utility supply and control 516 and a mechanism for turning the utilities, such as power, gas and/or water, on and off under a programmatic control. The system 500 may include an internet data supply control 518 and a mechanism for turning the access to this service on and off under a programmatic control. Programmatic control may be provided to grant or deny access to such resources. The system 500 may include an antenna 520 for wireless communications signals to receive and transmit. The system 500 may include a gyroscope 522 to monitor any moving of the system. The gyroscope 522 may indicate motion indicative of whether someone is trying to move or tilt the housing or other component of the system. Logic may be provided to send a notification in such an event where the gyroscope indicates substantial enough movement. The system 500 may include a weather station 524 to measure current weather conditions, such as temperature, air movement, humidity, precipitation, barometric pressure, direct sunlight, and the like. Input from the weather station 524 may be used to inform decision making by the system in some instances. Alternatively, the weather may be collected via software, such as from a weather service or other weather source. Similarly, system 500 may include a weather sensor 512. The sensor can be a wet bulb globe temperature adapted to measure, among other things, heat stress in direct sunlight, which accounts for temperature, humidity, air movement (direction and speed), sun angle and cloud cover (solar radiation).
FIG. 6 shows an example of a computing device 600 for the system. The computing system may include processing logic 602, such as microprocessors, controllers, field programmable gate arrays (FPGA), application specific integrated circuits (ASICs) electronic circuitry, and other types of logic. The processing logic performs the operations of the computing device 602. A storage device 604 may also be provided. The computer readable medium and/or data storage device 604 may take various forms, including magnetic storage, optical storage, etc. Storage capability 604 may include computer-readable media, including removable computer readable media, such as disks, thumb drives and the like, or disk drives, solid state memory, random access memory (RAM), read only memory (ROM) and other types of storage. The computing device may include a display 606, such as an LCD display, an LED display, or other types of display devices on which video information may be displayed. The computing device 600 may include a network adapter 608 for interfacing with networks and a modem 610 for communicating wirelessly, over telephone lines or cable lines with remote devices. The processing logic 602 may use information stored in the storage device 604. In particular, the processing logic 602 may execute programs 614 stored in the storage and may access and store data 616 relative to the storage device 604. The computational functionality of the system described herein may be realized by the processing logic 602 executing the programs 614.
FIG. 7 shows an example of a user interface on one or more displays. The user interface may include activatable elements. A user may depress these activatable elements or select these activatable elements using an input device, such as a mouse, keyboard, touchscreen, or the like, to activate the components. The display may include a help element 702 that may be activated to obtain help information regarding use of the housing. It may also contain real time projects or process plans. It may also include “how to” assistance including videos related to the various projects, stages, processes, and tasks performed at the project location. The user interface on a display may also include a call center activatable element 704. Selection of the call center activatable element 704 may cause a call to be initiated with a call center so that the individual using the system may have a telephone and or video conference with personnel at the call center. The user interface on the display may also include a tutorial activatable element 706. Selection of the tutorial activatable element causes a tutorial to be displayed to teach the individual about operation of the housing.
The system 700 may include software which allows each tool to be coded or assigned to authorized personnel. Each tool can have a verifiably paired digital representation associating the specific tool with the digital representation. This can be verified by the system through recognition of the tool from a reader or sensor. The tool supplier record can be created by the tool supplier and include a digital representation associated with the tool and store the digital representation paired with the tool on the immutable storage. When the tool arrives at the project location, the system can retrieve the tool supplier record and determine of the tool requested if the actual tool that arrived. A tool verification record can be created and stored on the immutable storage representing that the tool delivered and received matches the tool supplier record. Shipping or delivery company personnel may activate the delivery activatable element. This causes a delivery functionality to be displayed where delivery notes may be added and where information may be gathered from the delivery person regarding a particular delivery.
An inspector activatable element 712, may be activated to cause the inspector functionality to be activated. The inspector functionality may enable an inspector to add inspection notes, provide electronic inspection certificates and the like. The system can provide reports that can be automatically generated from the existing data described herein as well as notes manually added during the construction process. The reports can be generated at predetermined times such as daily or upon completion of specific tasks.
As shown in FIG. 8 , the exemplary embodiments may be implemented in a decentralized computing environment 800, that may include distributed systems and cloud computing. FIG. 8 shows one or more systems 802 that may be in communication with a remote cluster 806 via a network 804. The cluster 806 may store information received from the system 802 and provide added computational functionality. The network may be a wired network or a wireless network or a combination thereof. The network 804 may be a secure internet connection extending between the system 802 and the cluster 806, such as a virtual private cloud (VPC). The server may be a computing device and can be in communication with the site computer device. The cluster 806 may include access to storage 808. The storage 808 may include a database 810 in which information regarding a project location is stored in a consistent manner.
FIG. 9 shows diagram 900 of an example of a peer-based network where an immutable storage 902 is broadcast and shared among the nodes 904. This network may be resident in the VPC cluster 806 (FIG. 8 ) or in a network for example. The nodes 904 may represent computing resources, such as server computer systems or other computing systems, residents at the parties identified in FIG. 9 , for example. Each node that has access to a copy of the immutable storage system 902.
The various computer devices, including the server and site computer device (e.g., system, controller, and any combination), can be in communications with immutable storage. The immutable storage can include a distributed ledger, immutable database, block-chain structure, and the like. The communications between the various computer device, including the server and the site computer device and immutable storage can be a global communications network, wide area network, or local area network, delivered to a computer readable medium from one device to another (e.g., USB drive, CD, DVD) and can be wired or wireless.
Referring to FIG. 10 , the biometric data 1002 that may be obtained by biometric-based identification devices at the project location to attempt to identify individuals. Biometric data may include facial recognition 1004, an iris/retinal scan 1006, a fingerprint scan 1008, a hand scan 1010, a voice print 1012 or heart rate signature 1016 or other input or sensor 1014. It should be noted that other types of biometric data may also be used in exemplary embodiments to help identify individuals uniquely. Also, an individual may be required to provide multiple types of biometric data in some instances.
To help illustrate an example of geofencing, FIG. 11A shows an illustrative project location 1100. The project location 1100 may include a housing 1102 for the system as well as storage location 1104 that can be a building, trailer, shed or the like. The storage location 1104 may hold tools, equipment, wearables and/or materials. The project location 1100 may also include a task location 1106. The task location may be where tasks are performed using materials to produce a good or offer a service.
FIG. 11B shows an example of different areas that may be established for geofencing at project location 1100. Area A shown a boundary 1108 may include the entirety of the project that is under construction. Area B 1110 may be a portion of the project, such as the kitchen. Another area may be a shed and another area may be the entire project location. Individuals may have access to none of these areas or to a subset of these areas, including all areas.
Referring to FIG. 11 , computer device 1102 can be in communications with a network 1104 and immutable storage system 1106. The computer device can include ca capture device that can be included in the computer device, connected to the computer device or is communications with the computer device. The computer device can obtain information from other sources 1108 such as third-party time and date information (e.g., atomic and nuclear clock operators, weather information). The computer device 1110 can be mobile 1102 of stationary 1112 so that the computer device can be disposed at a user, object, or event location. Once user information, object information, event information, capture information is stored, another mobile computer device 1114 or other computer device 1116 can retrieve the stored information. The information can include a identifier that can be a physical identifier or digital identifier such as a QR code that can be affixed to the object or associated with an event. When the identifier is scanned, the various information and records can be retrieved. The system can include verification of an object and event with its digital representation with a subsequent computer device 1118.
Referring to FIG. 12A, when a user wishes to use a computer device, the computer device and capture device can obtain biometric information from the user as 1202. A determination can be made at 1206 if the information from the user can be verified. If not, an alternative authentication process can be used at 1216. If the alternative method for user authentication is used, the system can determine if a predetermined number of tries are attempted at 1206 and if so, deny access at 1208 or retrieve the permissions for the users at 1212. IF the user is permitted access at 1214, access is granted at 1418, otherwise a notification that the user attempted to access the system can be created at 1410.
Referring to FIG. 12B, the image of the user can be captured at 1220. Features can be extracted from the captured image at 1222. The comparison 1224 can results bs used to determine if there are similarities and to determine if there is a match at 1226.
FIGS. 13A and 13B are examples of the system in user is shown as it applies to an event where objects can be associated. A database of objects (e.g., sporting equipment, restaurant meals, supplies, and any physical object) is shown as 1310. The database may hold event information 1322, such as GPS data and addresses, times, attendees, event type, and other project or process properties. The database 1310 may store an object requirement record hash notification 1324 from the immutable storage 1302, indicating that the hash value for the object or event information has been referenced on the immutable storage 1302. Information 1326 tracking the object information or record may be stored in the database. The supply company may analyze and process the design to develop the object or event for the project or process. A hash value 1328 resulting from passing the design information through a secure hash function is stored in the database 1310, transferred to the database 1304 and referenced on the immutable storage 1302.
The database 1310 may also store inventory management information 1330, such as quantity and the particulars of material inventory and material warranty information for such materials. The warranty information for materials may be hashed into a value 1334 and the resulting hash value may be stored in storage in the database 1310. The hashed value 1334 may be passed to the database 1304 and then referenced on the immutable storage 1302. The database 1310 may also store shipping or storage information 1336. This may include bill of lading histories 1338 and barcode, RFID values, UHF values and/or QR code scan histories 1340. The material list (such as a bills of lading) for an assembly project and the barcode/QR scan codes for delivered items for the projects may be hashed and the resulting hash value(s) passed to the database 1304 for reference on the immutable storage 1302. Further, confirmation of what was specified by designers was delivered to the event or object location and stored or used according to specifications so that a project or process can be placed under warranty or other follow-on benefit.
A database may store object or event information, such as TMS #'s, GPS data, event activity, users, locations and the like. The database may also hold scheduling information 1348 for the object or event. This may include detail regarding event activities (e.g., workflow and timing). A hash value of the event 1350 may be stored on the database, passed to database 1304 and referenced on the immutable storage 1302. The database may store user information 1352. The user information 1352 may include identification information 1354 for users involved in events or with objects (e.g., storage, security, inventory, user). This user information 1354 may include information regarding licenses for user 1356, hire dates for users 1358, employment end dates for users 1360 and other information, such as names, photos, etc. The user information can include information that the user is in compliance with applicable laws (including federal and state), in compliance with contractual obligations, properly licensed, of legal status, of sufficient experience, within application restrictions such as a limit on hours worked during a 24-hour period, authorized for the event and its location and any combination. The user information may be sortable by tokens or keys such as TMS # to identify participants for an event. The database 1312 may also store scheduling information for users. This information may be used to develop a sequencing proposal that is hashed 1366 and the resulting hash value stored in the database 1312. The hash value 1366 may be passed to the database 1304 and referenced on the immutable storage 1302. User and event sequencing data once a task or event is completed, the information may be hashed, and the resulting hash value stored in the database 1312 for a project. This hash value 1368 may be passed to the database 1304 and referenced on the immutable storage 1302.
Task information 1370 may also be stored in the database 1312. The task information 1370 may include a hash of the tasks for an event and a hash of tasks releases for an event 1372. These hash values 1371 and 1372 may be passed to the database 1304 and referenced on the immutable storage 1302. The task information can be used for a determination of warranty requirement compliance for the event, object, user and associated information.
The captured information can be accomplished using various scanning and reader technology. A machine vision system may be provided. The machine vision system may capture an image of objects and events and process the image to determine the nature of the objects as well as the quantity. Moreover, the machine vision system may capture an archival image that may be indicative of the state of the objects at any given time. A QR code scanner may be used where QR codes are on an object. Similarly, a bar code scanner may be used where bar codes are on the items or on documentation delivered with the items. Still further, an RFID reader may be provided to gather information regarding the delivered items.
In one embodiment, a user can be an inspector or other official that can interface with the system and perform steps that may be performed in such an interaction. Initially, the identity of the inspector may be confirmed using the biometric data or manually using the touchscreen on the system. The inspector then performs the inspection of the appropriate portion of the project location. The inspector then accesses the system, such as through the system at. The inspector then may record notes and/or post certificates or notices at the system. Additionally, the inspector may use technology available via the system such as OCR scanner or the like to capture appropriate information the inspector may have written during fulfillment of the reason for being on the site.
Systems at adjacent locations may be used in conjunction with each other. For example, in the event that there are multiple smart indicia on one or more physical objects, the proximity of the indicium to each other can be used to verify the status, disposition and location of one or more physical objects. In one indicium moves a certain distance from another, it can indicate a change in status that can be associated with an event record and the physical object.
The steps that may be performed by image capture devices, such as still cameras or video cameras, from multiple adjacently situated systems can be used in conjunction. Video feeds or still images may be obtained from the image capture devices from multiple systems. The video feeds or images may then be processed, such as by the cluster described above, using software such as motion detection software, thermal image analysis or other image analysis software to identify activity that may warrant a response. When a motion is detected, it can trigger data capture for that event.
As has been mentioned above, a great deal of information may be collected and stored about an object and event during or after an event. The information obtained during the project from many different sources may be stored on or referenced from immutable storage. The information may be stored on an ongoing fashion, in databases as described below, and may be referenced in an immutable fashion on the storage. This information may help resolve disputes between parties involved with objects or events. For example, suppose a buyer asserts that the wrong objects were delivered. Since there is a complete record reference on the immutable storage of all events, these records may be accessed to resolve the dispute. Disputes regarding pay among workers may be resolved by checking the recorded hours on a location to determine the appropriate pay for the workers. Inspection records may be accessed to confirm that proper inspections were carried out and passed.
The information referenced in the immutable storage may also be accessed from a computing device of an owner, end user, customer, integrated and the like at. The computing device may be, for example, part of a home maintenance system that manages and controls home systems, such as heating, air conditioning, lighting, an alarm system, or the like. The computing device may be part of a smart home controller and may interface with appliances and other items that are interconnected via a home control network. The computing device may include a document management system for securely storing the transferred information. The computing device may be a facilities management system, or operations system associated with the project location.
Items may be affixed, such as barcodes, QR codes, RFID identification, Bluetooth beacons and/or UHF identification when the items arrive at the supply company. Stickers may be affixed to the items to associate the codes with the items. The items in each package may be scanned to record what items are included in the packages. The packages may be wrapped as needed and a QR code sticker may be affixed to the outside of each package. The QR code for each package is scanned. The process may then generate a material list for each delivery.
Interactions relating to a smart contract for the project or process can be implemented using the system. For example, suppose that the supply company makes a delivery to the project location. Further suppose that the delivery is confirmed by information such as that gathered by the system as discussed above. The lender then releases payment to the supply company. Payments can be made through third party funding, factoring, credit lines, loans, or other financial options to assist with financing and cash flow management.
The payment may be made electronically, such as through crypto currencies, like Bitcoin or Ether, or via a stable coin whose value is pinned to an item like a paper currency or the like. A cryptocurrency is a digital currency built with cryptographic protocols that make transactions secure and difficult to forge. Other Suitable forms of electronic payment includes Automated Clearing House (ACH) payment, Electronic Funds Transfer (EFT), card payments, other types of bank transfers or other types of electronic wallet transfer. In the case where crypto-currency is used, the crypto-currency may be delivered to the digital wallet of the supply company at a specified wallet address or account. The ledger may be updated to show that the contract is complete. Payment requires that the lender has sufficient funding in their digital wallet. If not, the smart contract will not be written on the immutable storage. If there is sufficient funding, payment is made, and the contract is written onto the persistence storage as complete at 3320.
There can be a relationship between the smart contracts and the project, process, or event. Initially, a schedule can be received. For example, the assembler can create the project schedule based in part on the design and material requirement record. Based on the project schedule, smart contracts may be constructed that use the immutable storage for contractual arrangements associated with the project or process. The smart contracts are implemented in software and in this case are used to provide electronic payments to parties for activities relating to the project or process using, for example, electronic payments, crypto currencies, fiat currencies and other forms of payments. The smart contracts may specify the conditions required for payment and may specify the amounts of payment. Smart contracts may also play a role with deliveries. Delivery and/or materials information is obtained regarding delivery to the project location for the project or process. The information obtained can include if the materials delivered match the material requirement record, manufacturer, and/or supplier which can be confirmed by multiple parties.
The delivery information is hashed, and the resulting hash value is referenced on the blockchain-based immutable storage. A smart contract is provided that uses the immutable storage. A determination is made whether the conditions specified in the smart contract are satisfied. If the conditions are satisfied, electronic payment for the delivery is realized. If the conditions are not satisfied, notice of outstanding issues are sent and the delivery worker may attempt to remedy the issues. The process may then be repeated beginning with step until the conditions are satisfied.
To pair a material with its digital representation the system captures events at various points of transition of the material. Pairing the physical material with the digital representation can include several elements or components. Included in the pairing process can be the physical observation of the physical material and then associate the physical material with a digital representation so that the physical material is properly associated with the digital representation. This verification provides trust that the digital representation is accurately associated with the physical material as a factor rather than simply trusting that the digital representation is accurate. This system can use manual or automated processes to physically observe the material and associate the material with the digital representation during various events from raw material to final deliverables. Verification can also use the metadata that is associated with the interaction of physical items by individuals and electronics when the item is created, transported, installed, activated, and destroyed. The metadata that can be captured and placed into immutable storage can provide stakeholders with an audit trail of history for their physical asset using a verified paired digital representation. A similar process as described herein can be used for pairing a biometric identifier with an individual.
For example, when raw material is harvested, a harvesting record can be created that captures the harvesting event and can include metadata concerning the event and verification that the raw material is associated with the harvesting record. For example, a digital image of the raw material can be captured, and the images and its metadata of the image captured can be included in the digital representation. The capture device and its metadata can also be captured and included in the harvesting record. For example, a sensor having a GPS transponder, camera and transceiver can be used to capture the harvesting event. The metadata of the harvesting event can include date, time, location (e.g., GPS coordinates), harvesting image, harvesting entity, harvesting worker, harvesting equipment and any combination. Once harvested, raw material can be loaded on a transport (e.g., vehicle, plane, ship, and the like). By capturing the harvesting event and verifying that the raw material and the digital representation are paired, and stored on the immutable storage, the physical material and the digital representation are paired allowing for reliance upon the digital record to accurately represent the physical material.
In one embodiment, the verification of the physical object can be performed using the weight or dimensions of the physical object captured throughout a process. The weight and dimensions can be combined with one or more images of the physical object where the capture device can be a scale, scanner, or other device. The capture device can be a combination of a camera and scale to provide for data streams during the process and at and between events.
By verifiably pairing the physical asset with a virtual presentation, the risk of unintentional or impermissible rehypothecation can be reduced or eliminated. The paired asset can be verified by multiparty chronological metadata streams that can be associated with a physical location. Because verifications using these streams are chronological, altering the information could require alteration of the metadata prior to and after the altered record. Therefore, the altered record would be inconsistent with the associated records potentially both temporally and geographically and an attempt to alter the record would be discovered. The use of one or more immutable storage systems further reduces the risk of alterations of records as well as increasing the verification of information. Further, pairing assets associated with the event, involving the asset, interactions with the asset and the associated metadata provide for a substantiated digital asset, reduce, or eliminate risk and improve capital efficiency. Further, the pairing of assets facilitates commerce by allowing electronic transactions with assurances that the digital representation used in the electronic transaction is paired with the physical asset.
Verification, including verification of an event, can include verifying that the physical material and the digital representation match and can be accomplished in a variation of methods including interaction with identification elements such as a tag, label, and the like, capturing an image of the material, capturing a video of the material, capturing indicia such as a tag physically affixed or otherwise associated with the material, human visual inspection, weight measurements at and between events, capturing the dimensions of the physical object at and between events, and any combination. Identification of an individual performing or otherwise associated with an event can be captured by identification devices (e.g., cards, tags, RF ID. smart dust, beacons) and biometrics including visual capture (e.g., facial recognition), voice recognition, iris scan, fingerprint, palm print and any combination.
The system can retrieve object and event information such as harvesting record, receive verification that the raw material delivered to a shipper is the same that was harvested and create a shipping record. A verification that the physical material and the retrieved digital representation match can be performed using a capture device, worker verification and a combination. The metadata associated with delivering the raw material to the shipper can be captured and included in the shipping record. The shipping record can include information about the shipper and the worker delivering the raw material to the shipper. The shipping record can include information about the destination of the raw material. By capturing the shipping event and verifying that the raw material harvest delivered to the shipper and the digital representation are paired, and stored on the immutable storage, the physical material and the digital representation are paired from harvesting the delivery to the shipper allowing for reliance upon the digital record to accurately represent the physical material and its disposition.
The system can retrieve event information such as a shipping record, receive verification that objects such as raw material is delivered by the shipper to a processor (e.g., manufacturer), is the same that was harvested, shipped, and received. The metadata associated with delivering the raw material to the processor can be captured and included in a delivery record. The delivery record can include information about the shipper, processor, worker and any combination. The delivery record can include information about the processor, location, and other information. By capturing the delivery event and verifying that the raw material harvest delivered to the processor and the digital representation are paired, and stored on the immutable storage, the physical material and the digital representation are paired from harvesting the delivery to the processor allowing for reliance upon the digital record to accurately represent the physical material and its disposition.
Once the processor processes the raw material to form a processes material, the system can create a processor record including that the raw material delivered to the processor is integrated into a processed material and is the same raw material that was harvested, shipped, and received. The metadata associated with processing the raw material can be captured and included in a processing record. The processing record can include information about the harvesting, shipping, processor, worker, and any combination. By capturing the processing event and verifying that the raw material harvested delivered to the processor and the digital representation are paired, and stored on the immutable storage, the physical material and the digital representation are paired from harvesting to processing allowing for reliance upon the digital record to accurately represent the physical material and its disposition.
Once processed, the processed material can be further shipped to be included as a component in another material. For example, the raw material can be aggregates, rocks, Portland cement and water. The processed material can be concrete. When an article (material) is made from the concrete, the article can be associated with a digital representation that allows pairing of the article with the raw material and the events through the article process. Therefore, the physical article and the digital representation are paired from harvesting to article creation allowing for reliance upon the digital record to accurately represent the physical article (material) and its disposition.
Referring to FIG. 13C a location 1394 can include the computer device 1395 disposed at a stationary location or the computer device can be portable and disposed at the location. An object 1396 can be at an inventory location 1397 and when used, taken to an event location 1998. The system can record the object and the event wherein the event can include the receipt of the object at the storage locations, use of the object at the event area and a transaction or other event that occurs involving the location or the object. The location 1394 can be geofenced so that the location of an object or event can be compared with the physical location.
Referring to FIG. 14A through 14E, a user 1402 using a computer system can create object information 1404. The object information and its metadata 1408 can be stored on immutable storage system 1400. A user of the computer device 1410, can select or otherwise acquire object information such 1416 from the immutable storage. The user can verify that the digital representation matches the object information or record, and the system can capture this as an event. The user can also use computer device 1410 and capture an event that can be associated with the object or can stand alone and store the event information 1418 on the immutable storage 1400. For example, one method of associating the object with a digital representation is using an indicia 1420 a (I₁) placed on the material. The indicia is then physically verified to be associated with the material from the material list or the material requirement record. Therefore, the physical material and the digital representation (V₁) are paired by recording this event and associating the physical material, I₁, and V₁. In one embodiment, the indicia can include the following information:


Description	Digits	Information

Locations	19-20	GPS XX.XXXXXX XXX.XXXXXX
User ID
	8	SSN XXXX + Initials XX + Gender X
Date
	10	XX/XX/XXXX
Time
	7	Zulu XXXX:XX
Material
	12	UPC/Barcode XXXXXXXXXXXX

An event record such as shipping, activity, task or other events 1418 can be created and stored on the immutable storage. The capture event can include a unique number and include the user or object ID, date and time, location, object ID, status, and any combination. The object ID can be from an original manufacturer, the supplier, user, or created by the system. The status can include that the material has been gathered, packaged, ordered, is in stock or on back order, shipping information, transferred, obtained, and the like and in any combination.
A user such as an inspector can retrieve information from the immutable storage identifying the user location, object location and event location. The information can also include task, event, activity, occupants, attendees, origination, destination, pick time, delivery time, and other information concerning the object. The user can verify that the object matches the digital representation of the retrieved record. If the object is verified, the user can physically capture the event, for example, by affixing its indicia 1420 b (I₂) to the object representing this verification. A system can create a record 1424 that can be stored on the immutable storage system. This record can include project, shipper, material, status, date, time, location, and any combination. The mode of transportation of the material can also be tracked and stored on the immutable storage. For example, if a shipper uses a vehicle, the date, time, location, and other metadata associated with the vehicle can be gathered along the route and stored on the immutable storage. Verification can be provided using the metadata of the various events. For example, if the date, time, and location of the object and event record is within a certain range of values of the date, time and location of the pickup event, there will be verification that the proper objects were physically transmitted from a supplier to a shipper, for example.
Using the shipping example, the shipper as a user can deliver the material (e.g., object) to the destination such as a project location. When the shipper delivers the materials to the project location, the shipper can capture this event by creating a supplier shipping delivery 1428 record using a shipper computer system. The shipper can verify the event by methods including adding an indicia 1420 c (I₃) representing that the proper materials were delivered to the proper location. The project location computer system 1432 can be used to verify that the materials were properly delivered by retrieving the material record 1430 from the immutable storage and using the record to match the physical materials delivered. In one embodiment, the shipper can use the tags that are part of the digital representation to match I₃with the material and the information stored on the immutable storage to capture and verify the event. When the material is delivered, the project location can use a project computer system 1432 to retrieve the material record from the immutable storage and match the material delivered with the material record. The project location can add an indicia 1420 d (I₄) to the material to capture this event. The project location can create a project location material received record 1434 that can include the project, material, digital representation (V₄), status, date, time, location, other metadata, and any combination. The shipper, worker at the project location, or both can physically inspect the material and verify that it matches the digital representation stored on the immutable storage. This verification can be included in the information that is stored on the immutable storage by the shipper and a worker or system at the project location.
Referring to FIG. 14C, and using assembler as a user, materials as objects and the assembly as an event, the project location can be an assembler, or the assembler can be at a separate location from the project. For example, in the manufacturing of a vehicle, the project location can be the assembly line for the vehicle and multiple assembly locations can be involved. The main assembly line can be the project location and the assembler can be a component or sub-component of the manufacturing process. This system can be used for the project, or sub-project that are included in the overall project. Further a sub-project can be treated as a project as discussed herein.
An assembler computer system 1436 can be used to retrieve the material record from the immutable storage. The material record can be used to match the materials delivered to the assembler to verify that the proper materials were received by the assembler. The assembler can add indicia 1420 d (I₅) to the material, or use other verification methods described herein, to capture the event. The assembler can also capture the material used and the assembly 1438 by adding a indicia 1440 a (A₁) to the assembly. An assembler record 1442 can be created and stored on the immutable storage. The assembler record can include the project, assembly description and other information, assembler, material(s) used, digital representation, shipping information date, time, location of the assembly, other metadata, and any combination.
One verification can be the comparison of an image of the physical object taken at the first event and the image of the physical object taken at the second event. In one embodiment, the determination if the two images represent the same physical object can be made by comparison the distance between the images. The distance between the images of the two object captures do not have to be identical but can be defined by the “closeness” between the images. In one embodiment, the distance can use the Euclidean distance between the I^thand j^thphysical object. Distance between the p-dimensional vectors can be represented as:
d _E(i,j)=√{square root over ((Σ_k=1 ^p(x _ik −x _jk)²))} (1)
or by using the weighted Euclidean distance that can be represented as:
d _E(i,j)=√{square root over ((Σ_k=1 ^p w _k(x _ik −x _jk)²))} (2)
Where d_E=distance, i=first image, j=second image, and w=weight between kth measure which can be subject to the following
0<w _i<1 and Σ_i=1 ⁿ1 (3)
In one embodiment, the verification process can include an individual retrieving the first image of the physical object and comparing the first image with the physical object in proximity of the individual. The individual can review the first event record and the second event record to also make a determination of the physical object has remained the same from the first event to the second event. Information. In one embodiment, multiple individuals and computer system can make the comparison. The comparison can also be crowd sourced so that multiple verifications are made from an individual computer system and any combination.
Once completed, the assembly may need to be delivered to another location. The assembler record can include shipping information, or an assembly shipping record can be created and stored on the persistent record. If the assembly needs to be delivered, a second shipper can use a second shipper computer system 1444 to retrieve the shipping record, assembler record or other shipping information that is used to identify the origin, locations, assembly, pick up time, delivery time and other information associated with the transportation of the assembly from one location to another. The assembly can be received by the second shipper and the second shipper can capture the event such as with a indicia 1440 b (A₂) to the assembly representing that the assembly has been verified by the second shipper as properly provided and received by the shipper. A second shipper pick up record 1446 can be created and stored on the immutable storage.
Referring to FIG. 14D, the second shipper can deliver the assembly to a retailer, distributor, or customer. The assembly can be a component to be further used or a final product. When the second shipper delivers the assembly to a retailer or distributor, the second shipper can create a second shipper delivery record 1448 using a second shipper computer system 1444. The second shipper can capture the event such as using a indicia 1440 c (A₃) representing that the proper assembly was delivered to the proper location. The second shipper can use the verifications that are part of the digital representation to match A₃with the material and the information stored on the immutable storage.
The retailer or distributor computer system 1450 can be used to verify that the materials were properly delivered by retrieving the assembly record 1452 or second shipper record 1448 from the immutable storage and using the record to match the physical assembly delivered. The retailer or distributor can capture the event and can add an indicia 1440 d (A₄) representing that the proper assembly was received at the proper location. A retailer distributor record 1454 can be created and stored on the immutable storage.
Referring to FIG. 14E, a user (e.g., customer, buyer and sports fan) can receive an object and by using a computer system 1456 retrieve or otherwise receive the object or capture record 1458 from the immutable storage or other system. The user can be provided with the object using the system as described herein with a user performing the steps and the system performing the steps associated with the transfer of the object. Another user can create a subsequent event record representing a third shipper pickup and delivery record that can be stored on the immutable storage verifying that the assembly was properly provided from the supplier. The user may capture the event and can add an indicia 1440 e (A₅) to the object that can be associated with the digital representation (V₈). A capture record 1460 can be stored on the immutable storage reflecting the object and event.
Using this system, the user can be assured that the object was independently verified and authenticated from the design to the delivery to the user and that the digital representation of the assembly and its components (e.g., materials) are paired.
In one embodiment, where the event can be a repair request 1462 can be created and stored on the immutable storage system. The repair request can be associated with the assembly and retrieved by a repair computer system 1464. The repair company can receive a part using the system described herein, perform a repair or replacement action, and capture the event such as by using a indicia 1440 f (A₆) to the assembly indicating that the assembly has had a part repaired or replaced. The repair part can also have a preexisting indicium from the use of the system herein and the repair company can capture the event such as by using a indicia (I_x). A repair record 1466 can be created and stored on the immutable storage.
The system described herein can pair the physical material and/or assembly with a digital representation. Failure to pair the physical material or assembly with the digital representation can negatively impact areas such as regulatory requirements. Regulatory requirements are a set of rules that can specify the standards for a project. Regulatory requirements impact designs, materials, worker's license and experience needed for the project and process. For example, a building code may require that construction materials be installed in accordance with manufacturer's specifications and warranty regulations. Failure to follow the building codes can result in the project not being approved, errors, lack of customer satisfaction, insurance claims, injury, litigation, and other negative ramifications. Tracking, management, and verification of materials to ensure compliance with regulatory requirements and proper installation according to applicable specifications is an important aspect to many projects and processes. Tracking and record keeping during the project or process can be beneficial, as it can be difficult to perform these tasks after project or process completion because the materials can be hidden from view or otherwise inaccessible. For example, electrical wiring in a project or process can be hidden behind walls and ceilings once the project is complete.
Systems at multiple locations may be interconnected using image capture devices, RFID, QR codes, barcodes, biometric scanners, still cameras, video cameras, and the like to identify individuals or machines that are performing verifications during the process. Further, multiple individuals or machines are performing verifications so that there is not a reliance upon any one entity for verifications. The processing of capturing data, including images, from the multiple systems at multiple locations can be used to improve the verification of proper materials and assemblies as well as to pair the physical items with the digital representation.
Verification of processes, inspections, completions and deliveries with adjustments and notifications (manual and automated) with confirmation would ensure increased productivity, especially if accessible in real time at the location. Real time processes and procedures planned with corresponding training and manuals would improve quality control and efficiency. This has been a long felt need in the prior art that has not been satisfied with a controller that is uniquely associated with an asset location.
Automated verification of quantities, quality, and correct product deliveries along with after delivery tracking of materials with accountability is seldom used. Designated delivery areas with geofenced control and tracking of materials once delivered would help prevent loss. Confirmation of products integrated at the asset location provides transparency regarding sourcing, warranties, as well as future reference during the structure and individual product's life of use.
By using the various tags and digital representations, each entity in the process can verify that the physical materials match any record the precedes that entity.
This process can include internal and external individuals and machines for performing inspections (e.g., verifications). For example, the system can receive a set of internal inspection information entered into the system from an internal inspector representing an internal physical inspection of the project, material or assembly. As the items travel, an internal inspector can provide inspection information representing the stages of the project. The system can also receive a set of external inspection information from an external inspector and an external inspection computer device representing a third-party physical inspection of the project at predetermined stages of the project. Based upon the internal inspection, external inspection or both, an inspection record can be created and stored on the immutable storage.
The verified pairing described herein can also be used to verifiable pair physical assets with installation instructions, storage instructions, warranties, ownership, service, maintenance, and any combination thereof.
The system can also facilitate the use of digital wallets or other digital storage technologies. The information that is contained on the digital wallet can be paired with a physical object so that transactions associated with the physical object can be conducted with verification that the digital representation in the digital wallet represents the physical object, whether the physical object is fungible or unique.
The computer system having computer readable instructions can be in communication with an immutable storage; a first computer device in communications with the computer system; a second computer device in communications with the computer system; a set of computer readable instructions included in the computer system configured for: receiving an event record (E₁) from the first computer device including a first location (L₁), a first time (T₁) and a first set of metadata (M₁) wherein the first set of metadata includes an original digital representation captured by the first computer device of the physical object, receiving a subsequent event record (E₂) from the second computer device including a second location (L₂), a second time (T₂) temporally subsequent to the first time and a second set of metadata (M₂) wherein the second set of metadata includes a subsequent digital representation captured by the second computer device of the physical object, and, determining if the original digital representation is equivalent to the subsequent digital representation thereby providing for verification that the same physical object transitioned from an originating event to a subsequent event.
The event record can include a verification code that can be used to verify that the data in the event record remains accurate from its creation of from another time. The verification can have several constructions including checksum. A checksum can be a small block of data, usually digital, derived from another block of digital data configured for use for detecting errors that can occur transmission, storage or unintentional or intentional tampering with the data. A first record can have a first checksum. A second record can have a second checksum. The second checksum can be derived from the first and the second record so that alteration of the first or second record can be detected with the second checksum.
The verification can be a hash. A hash can be a mathematical function that is configured to converts an input, such as a data record, into an encrypted output, typically having a fixed length. Therefore, a unique hash can be the same size regardless of the size of amount of the input (e.g., data). Further, the hash can be configured to prevent reverse-engineering of the input because the hash functions is a one-way function. When analyzing a record, such as an event record, comparing a first hash that can be created and stored with the event record and a second hash calculated when the event record is retrieved can provide validation that the data is unaltered from storage to retrieval. The verification code can be the hash.
The event record can also include the validation code that is created according to a set of validation rules. These rules can control what information can be included in a record and verification that the record includes data or at least the type of data that is contained in the record. Validation rules can include data type, code type, range check, format check, consistency check and uniqueness check. These rules can be used to both assist with the type of data inputted and whether the data has been altered from storage to retrieval. Validation can also be performed with sampling a subset of data or records from a database and extrapolating accuracy of the data from origin creation to storage through retrieval.
In one example, a data record is an input that is processed with computer readable instructions configured with a hashing algorithm that can include a secure hashing algorithm, message digest algorithm, Keccak, RACE integrity primitives evaluation message digest, Whirlpool, BLAKE, and the like and any combination. The output can be a first verification code and that first verification code is stored on an immutable ledger or other secure location. The hashing algorithm can be deterministic so that the input will results in the same output. The hashing algorithm can be configured to prevent the ability to see or read the data that is the original input. The hashing algorithm can be configured so that a small change, even one byte, will change the output. Therefore, the first output of the data will not match the second output if the data is changed between when the first data and the second data is determined.
The set of computer readable instructions can include instructions for determining if a similarity between the original digital representation and the subsequent digital representation is within a predetermine range. The first computer device can be remote from the computer system. The subsequent event record can include verification data representing that verification of the physical object subject to the subsequent event is the same physical object associated with the originating event according to the first event record. The set of computer readable instructions can include storing the first event record on the immutable storage and the set of computer readable instructions for determining if the first digital representation is equivalent to the subsequent digital representation includes retrieving the first event record from the immutable storage. The subsequent event record can include verification data representing that an individual viewed the metadata of the first event record and compared it with the physical object. The second set of metadata is taken from sources from the group consisting of public records, enterprise software, computer devices or any combination thereof.
The computerized system can include a computer system in communication with an immutable storage; a set of computer readable instructions included in the computer system configured for: retrieving a first event record (E₁) from the immutable storage wherein the first event record includes first location (L₁), a first time (T₁) and a first set of metadata (M₁) wherein the first set of metadata includes a first digital representation captured by a first computer device of the physical object, retrieving a subsequent event record (E₂) from the immutable storage including a second location (L₂), a second time (T₂) temporally subsequent to the first time and a second set of metadata (M₂) wherein the second set of metadata includes a subsequent digital representation captured by a second computer device of the physical object, and, determining if a similarity exists between the original digital representation and the subsequent digital representation is within a predetermine range.
The set of computer readable instructions can include instructions for determining if the physical object is the same physical object represented by the first digital representation during an occurrence of a second event. The subsequent event record can include verification data representing that verification of the physical object subject to the subsequent event is the same physical object associated with the first event. The subsequent event record can include verification data representing that an individual viewed the metadata of the first event record and compared it with the physical object. The first computer device can be a remote from the computer system and the second computer device.
The system can include for verifiably pairing a physical object with a digital representation comprising: a computer system in communication with an immutable storage; a computer device in communications with the computer system; a set of computer readable instructions included in the computer system configured for: retrieving a first event record (E₁) from the immutable storage wherein the first event record includes a first location (L₁), a first time (T₁) and a first set of metadata (M₁) wherein the first set of metadata includes a first digital representation captured by a first computer device of the physical object, creating a subsequent event record (E₂) from the computer device including a second location (L₂), a second time (T₂) temporally subsequent to the first time and a second set of metadata (M₂) wherein the second set of metadata includes a second digital representation captured by the computer device of the physical object, and, determining if a similarity between the first digital representation and the second digital representation exists.
The computer readable instructions can include instruction for determining if the similarity is within a predetermine range. The computer readable instruction can include instructions for determining if a similarity between the first digital representation and the second digital representation exists includes retrieving the first event record from the immutable storage. The subsequent event record includes verification data representing that verification of the physical object subject to the subsequent event is the same physical object associated with the first event according to the first event record. The computer device can be a first computer device; and the computer readable instruction can include instructions for determining if a similarity between the first digital representation and the second digital representation exists includes retrieving a first image of the physical object, comparing the image to a second image captured by a second computer device and determining if the images represent the same physical object. The instructions can determine if a similarity between the first digital representation and the second digital representation exists includes capturing an object indicium affixed to the physical object, comparing the indicium on the object at the subsequent event to a digital indicium included in the first event record. The subsequent event record can include verification data representing that an individual viewed the object indicium and compared it with the digital indicium retrieved from the immutable storage and included in the first event record.
In one embodiment, the system can provide a hashed event record where the event record can include metadata associated with a capture device as well as indicium associated with the physical object and store the record on a blockchain platform including the platforms associated with Bitcoin, Ethereum and the like.
Referring to FIG. 15 , one embodiment of the system is shown. A capture device can include a computer processor, computer readable instructions and a scanner. The scanner can be a camera, optical scanner, or other device configured to read shapes and symbols including barcodes, QR codes, RF tags, and the like. In use, the capture device can be used to read a digital asset identification at 1500. If a digital asset identification (e.g., QR code) is discovered at 1502, the system can retrieve use the digital asset identification or portion thereof and attempt to retrieve a digital asset registration from the immutable storage system at 1504. If digital asset registration is found at 1506, the digital asset registration can be used to retrieve data associated with the digital asset identification and the digital asset registration at 1508. The data can be retrieved from an immutable storage system and a separate system by use of a token associated with the digital asset registration and the digital asset identification. A determination can be made at 1510 if the retrieved information is encrypted. If so, the information can be decrypted at 1512. In the event that the digital asset registration has or is associated with a token, the token can be used to retrieve data from a second database at 1516.
Referring to FIG. 16 , the system can display the retrieved information. Once the digital asset identification is scanned or read, the digital asset registration and data is retrieved. The digital asset registration can include a digital image 1602 of the asset including several views including a view that can include the digital asset identification 1604. Information associated with the asset can be displayed at 1606 and can include alpha numeric information. Location information (e.g., where) can be displayed by geographic coordinates 1608 and can include a graphical map with a location indicator, surrounding information such as a listing of businesses 1610 at that location, landmarks, and the like. In the provided example, the asset can be a physical baseball card and the location can be a retail location where baseball cards are sold. Therefore, the user of the system can increase the confidence that the baseball card digital representation is property paired with the physical object.
The digital asset registration can include date and time information 1612 that can include when the digital asset registration was stored on an immutable storage 1614. The blockchain location can be provided as well to the user. Individuals that performed various tasks, activities and events can be shown at 1616. One or more individuals can be retrieved and displayed. The digital asset registration can include a unique identifier for the digital asset at 1618. The digital asset registration can also include the asset level which can represent a confidence level of the accuracy of the digital information displayed. The system can use digital asset identification to retrieve information from one or more immutable storage systems or other databases and storage systems.
The system can provide for a digital asset rating level that can be determined using a variety of factors. In one embodiment, the type of validator can be used to assign a validator identification level to the hardware used for creation, transacting, validation, authentication and other functions. A stational kiosk, one hardware classification, can be a trusted kiosk which can be controlled, monitored, and maintained by a validating entity. The hardware can be known and controlled so that when a digital asset registration is created and stored, it is done so from the trusted validator. In one embodiment, this can be the highest level of trust of confidence. A validator can be the hardware and software that is used to capture the digital representation of a physical object and associate that digital representation with a physical object thereby pairing the digital representation with the physical object. The stationary kiosk originating from a trusted source (e.g., manufacturer, distributor, operator and the like) can have the highest validation type. In one embodiment, the validation type can be assigned a numeric value. A validator can also be hardware and software that is mobile or portable. The validation type of this hardware and software can be assigned a numeric value that is the same or less than that of a stational validator. The validator can be in communication with a trusted network and have an approved operating system and software. When a digital representation is created, it can be associated with the location of the validator so that the confidence level of the stored information can be higher. A validator can also be a computer device that is known to an entity, but not necessarily provided by that entity. The computer device can be recognized as a trusted validator, but the validation type may not be as high as that discussed above. The computer device can include the ability to capture the individual identification information (e.g., the user) through biometrics. Biometrics can be used to determine the user and a known and trusted user can increase the validation type level. For example, an employee of a trusted entity may raise the validation type which an unknown or first-time user may lower the validation type. The validation type may also be impacted by the number of verifications of physical objects to digital representation that have been performed by the validator. In one embodiment, the more verifications performed, the higher the validation type. A validator can also be a computing device that is not known. In this case, the computing device is not associated with a trusted user, has little or no historical validations, and is not a trusted computer to the system. This computing device may have the lowest validation type value.
The digital asset rating level can also be impacted by the individua information that can be associated with the creation, verifications, storage or other associated with the digital representation, digital asset identification and digital asset registration. In one embodiment, the individual can increase the digital asset rating level is that individual's identity is verified through a trusted, regulatory, or governmental process. For example, an individual can be present in front of a trusted, regulatory, or governmental agent and have the identity of that individual verified that can result in the highest contribution to the digital asset rating level. Another contribution to the digital asset rating level can results by the user presenting or the system scanning and verifying a government issued identification (e.g., passport, driver's license, birth certificate, social security card, military identification and the like). The contribution to the digital asset rating level from a government issued identification can be less than that of a trusted, regulatory, or governmental process. In one embodiment, the government issued identification type can impact the contribution to the digital asset rating level. For example, a passport may contribute to the digital asset rating level more than a social security card given that a passport can includes a image of the individual ans is more difficult to forge. The presents of a witness to the creation, storage, verification of the digital representation and the association (pairing) to a physical object or digital object can also contribute to the digital asset rating level. When a second individual is present, that second individual can witness, review, observe and verify aspects of the creation of the digital asset identification and the digital asset registration. The presence of a witness can raise the digital asset rating level. When the individual has used the system and created, validated, reviewed, verified or other activities associated with digital asset registration, the increased use of the system of that individual can raise the digital asset rating level. As more activity occurs, the contribution to the digital asset rating level can increase.
The digital asset rating level can also be increased by the immutable storage type and the storage process of the immutable storage type. For example, if the immutable storage system relies upon multiple nodes, such as blockchain, the larger the number of nodes, the higher the contribution to the digital asset rating level can be. For example, a blockchain structure with 100 nodes would be less secure than one with 1000 nodes. Further, the type of nodes can impact the contribution to the digital asset rating level. For example, the higher the number of full nodes, the higher the contribution to the digital asset rating may be higher. Full nodes can be nodes that store all transactions on the associated device. Full nodes also can validate storage units (e.g., blocks) and the transactions. Further, if the node is an online node the contribution to the digital asset rating may be higher as opposed to an offline node. Further, the time between storing data (e.g., blocks in one immutable system) can impact the digital asset rating level. The shorter the time between storing data and data units, the higher the digital asset rating level can be. In one embodiment, the impact on the digital asset rating level can be shown with the following formula that can be embodied in computer readable instructions.
D _l =H+S+N+H _f+1+I _f +S+S _n +S _f
where D_lis the digital asset rating level, H is the hardware used for the validator, S is the software used for the validator, N is communications network that is in communications with the validator, H_fis the frequency that the hardware and software creates, stores, reviews, analyzes, validates, verifies or performs some other action associated with a digital representation, digital asset identification and digital asset registration, I is the individual that is user the system or otherwise engaging with the system (e.g., inspector, witness and the like), I_fis the frequency that the individual engages with the system, S is the storage system type including the type of nodes, S_nis the number of storage system nodes including active and nonactive nodes, and S_fis the frequency that the storage system creates, stores, reviews, analyzes, validates, verifies or performs some other action associated with a digital representation, digital asset identification and digital asset registration. S_fcan also include the time between the storing of data on the storage system.
Referring to FIGS. 17A and 17B, one embodiment of the implementation of the digital asset levels is shown. In this embodiment, the individual validation combined with the hardware classification results in a rating that can be represented with lettering and modifiers (e.g., “+” and “−”). A rating of “A+” can represent the highest rating and therefore the highest level of confidence and “C−” can represent the lowest.
The storage system can include those passed upon proof of work or proof of stake.
The description of the system herein may be embodied as an apparatus including, for example, a system, a machine, a device, a computer program product, and/or the like, as a method including, for example, a business process, a computer-implemented process, and the like, or any combination thereof. Embodiments of the system may be entirely software, entirely hardware, or a combining. The system may take the form of a computer program product that includes a computer-readable medium having computer readable instructions that can be actuated by a processor. A processor may be “configured to” perform a certain function in a variety of ways including using circuits that perform the functions herein by executing one or more computer readable instructions that can be stored on a computer readable medium.
The computer readable medium may include a non-transitory computer-readable medium and semiconductor system, apparatus, and device. In some embodiments, the non-transitory computer-readable medium can be a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), universal serial bus (USB) drive, a compact disc read-only memory (CD-ROM), and some other tangible optical and magnetic storage device.
References to flowchart illustrations and block diagrams of systems, methods, and/or computer program products can represent computer readable instructions, processes and the operation of the system that can include hardware and software. Blocks may be implemented by one or more computer readable instructions. These computer readable instructions may be provided to a processor of a general-purpose computer, special purpose computer, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer readable instructions or portions, which when executed by a processor, create systems and machines for implementing the steps and functions represented by the flowcharts and diagram blocks.
Computer readable instructions can be stored in a transitory or non-transitory computer readable medium that can direct a computer and other programmable data processing machines and apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instructions which implement the steps and functions specified in the flowcharts diagram blocks.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention is not limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications, and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.

Claims

1. A system for reporting digital data representing objects or events comprising:

a capture device in communication with an immutable storage system having a computer readable medium and a capture device processor;

a set of computer readable instructions stored on the computer readable medium that when processed by the capture device processor are adapted to:

capture a digital asset identification;

retrieve digital asset registration from the immutable storage system according to the digital asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information represented by GPS information, a temporal information, an individual information, an object information, an asset type, a creation information, a description, and any combination thereof,

display a graphical representation of the location information,

wherein the temporal information includes a date and time the digital asset registration was recorded on the immutable storage system,

wherein the creation information includes a validation type, individual information, and a storage type, and,

calculate a digital asset rating level according to the validation type, individual information, and storage type, and

associate the digital asset rating level with the digital asset registration.

2. The system of claim 1 wherein the immutable storage system is a blockchain system and the creation information includes a blockchain location where the digital asset registration is stored.

3. The system of claim 1 including a remote database is communications with the set of computer readable instructions and the object information is a digital token, and the set of computer readable instructions are configured to retrieve a secondary object information from the remote database according to the object token and display the secondary object information to a user.

4. The system of claim 1 wherein the validation type includes a hardware classification associated with a creation of the digital asset registration.

5. The system of claim 1 wherein the individual information includes an identification level.

6. The system of claim 5 wherein the identification level is taken from the group consisting of government witness, government identification, secondary identification, witness configuration, user interaction events and any combination thereof.

7. The system of claim 1 wherein the immutable storage system is a blockchain system and the creation information includes a blockchain location associated with the digital asset registration.

8. The system of claim 1 wherein the set of computer readable instructions are adapted to receive user identification information, user temporal information and user location information.

9. The system of claim 1 wherein digital asset registration represents a digital asset.

10. The system of claim 1 wherein the digital asset registration is a digital representation of a physical object, service, or event.

11. The system of claim 1 wherein the immutable storage system is a blockchain system and the storage type includes information taken from the group consisting of number of nodes, number of active nodes, number of transactions, time between transactions, time between clock confirmation, staking value, blockchain type, storage latency, and any combination thereof.

12. The system of claim 1 wherein the individual information includes individual metadata according to a user identification information, a user location information, and a user temporal information.

13. The system of claim 1 including a remote database is communications with the set of computer readable instructions and the digital asset registration includes a token associated with a linked information taken from the group consisting of an image, a video, a document, description, and any combination thereof and the set of computer readable instructions are configured to retrieve the linked information from the remote database.

14. The system of claim 1 wherein the digital asset rating level is calculated according to a digital asset registration record type taken from the group consisting of genesis record, product record, witness record, creator record, industry record, immutable storage system type, storage record type, and any combination thereof.

15. The system of claim 1 wherein the digital asset identification is configured to be immutably associated with a digital asset registration using a token stored on the immutable storage system.

16. The system of claim 1 wherein the location information is created according to a global positioning service, wireless access point, cell tower, IP address and any combination thereof.

17. The system of claim 1 wherein the set of computer readable instructions are adapted to receive validation information from a user and associate the validation information with the digital asset registration.

18. A system for reporting a digital asset representing objects, services, or events comprising:

capture a digital asset identification;

retrieve digital asset registration from the immutable storage system according to the digital asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information, a temporal information, an individual information, an object information, service information, event information, an asset type, a creation information, and any combination thereof,

displaying a graphical representation of the location information,

retrieve a digital asset rating level from the immutable storage system wherein a digital asset rating is created according to validation type, individual information, and storage type, and

display the digital asset registration and digital asset rating level graphically to a user.

19. The system of claim 18 wherein the digital asset identification is configured to be immutably associated with the digital asset registration using a non-fungible token stored on the immutable storage system.

20. The system of claim 18 wherein the digital asset rating level is calculated according to a digital asset registration record type taken from the group consisting of a genesis record, product record, witness record, creator record, industry record, immutable storage system type, storage record type, and any combination thereof.

21. The system of claim 17 including a remote database is communications with the set of computer readable instructions and the object information is an object token representing a digital object, and the set of computer readable instructions are confirmed to retrieve a secondary object information from the remote database according to the object token and display the secondary object information to a user.

22. A system for reporting a digital asset representing objects or events comprising:

capture a digital asset identification;

retrieve digital asset registration from the immutable storage system according to the digital asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information, a temporal information, an individual information, an object information, an asset type, a creation information, and any combination thereof,

wherein the creation information includes a validation type, individual information, and a storage type,

provide a digital asset rating level representing a validation type, an individual information, and a storage type.

23. The system of claim 22 wherein the set of computer readable instructions are configured to provide a digital asset rating level by creating the digital asset rating level according to validation type, individual information, and storage type.

24. The system of claim 22 wherein the individual information includes user biometric information, user location information and user temporal information representing a user that verified an association of the digital asset registration with a physical object.

25. The system of claim 22 wherein the digital asset rating level includes a ranking of a user that verified an association of the digital asset registration with a physical object.

26. The system of claim 22 wherein the immutable storage system includes a set of active nodes and a storage latency.

27. The system of claim 22 wherein the validation type includes a hardware classification of a hardware used to create and store the digital asset registration.

28. The system of claim 27 wherein the hardware classification is taken from the group consisting of a trusted network stationary device, a trusted network mobile device, a trusted network node, a trusted network, a known computer device and an unknown computing device.

29. A system for reporting a digital asset representing objects or events comprising:

retrieve digital asset registration according from the immutable storage system according to an asset identification wherein the digital asset registration includes metadata taken from the group consisting of a location information, a temporal information, an individual information, an object information, an asset type, a creation information, and any combination thereof,

30. The system of claim 29 wherein the digital asset rating level is a first digital asset rating level and the set of computer readable instructions are adapted to create a second asset rating level and display a comparison of the a first digital asset rating level with a second digital asset rating level.