DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1-20 are pending and have been examined.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. The claims recite the abstract idea which may be summarized as managing product ownership.
Step 1 Analysis
Applicants claims are directed to a process (claims 7-20) and machine (claims 1-6).
Step 2A, Prong 1 Analysis
Claim 1 recites the abstract idea/limitations of:
managing product ownership comprising:
a tag incorporated into a product, the tag having a tag ID;
a… certificate unique to the product;
and associate the… certificate with the tag;
and record ownership information of the product in the… certificate.
As drafted these limitations are a process that falls within the “Certain Methods of Organizing Human Activity grouping of abstract ideas; but for the recitation of generic computer components. If a claim limitation, under its broadest reasonable interpretation, recites performance of the limitation as commercial/legal interactions then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. By reciting/claiming a certain method of organizing human activity, Applicant’s claims are reciting an abstract idea.
Claim 7 recites the abstract idea/limitations of:
managing product ownership comprising:
scanning a… tag having a tag ID;
transmitting the tag ID;
matching the tag ID to a certificate associated with a product;
retrieving a product information and an ownership information based on the certificate;
transmitting the product information and the ownership information;
and displaying the product information and the ownership information.
As drafted these limitations are a process that falls within the “Certain Methods of Organizing Human Activity grouping of abstract ideas; but for the recitation of generic computer components. If a claim limitation, under its broadest reasonable interpretation, recites performance of the limitation as commercial/legal interactions then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. By reciting/claiming a certain method of organizing human activity, Applicant’s claims are reciting an abstract idea.
Claim 11 recites the abstract idea/limitations of:
managing product ownership comprising:
scanning a tag associated with a certificate unique to a product,
the tag having a tag ID and the product having a product ID;
associating an ownership information with the certificate;
and in response to a transfer of ownership, updating the ownership information to reflect a new owner of the product.
As drafted these limitations are a process that falls within the “Certain Methods of Organizing Human Activity grouping of abstract ideas; but for the recitation of generic computer components. If a claim limitation, under its broadest reasonable interpretation, recites performance of the limitation as commercial/legal interactions then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. By reciting/claiming a certain method of organizing human activity, Applicant’s claims are reciting an abstract idea.
Step 2A, Prong 2 Analysis
This judicial exception is not integrated into a practical application because the claims only recites system components for implementing the abstract idea and extra-solution activity. The claims recite the additional limitations of a system, an electronic certificate, a processor, a device, a server, an electronic tag, an interface, an electronic ledger, a blockchain, a near-field communication (NFC) tag; and they are recited at a high level of generality. These system components amount to no more than mere instructions to apply the exception using a generic computer. These limitations generally link the use of the judicial exception to a technological environment and are not indicative of integration into a practical application. The limitations of:
transmitting the tag ID;
transmitting the product information and the ownership information;
and displaying the product information and the ownership information.
as drafted are insignificant extra-solution activity. These steps are mere data gathering and storing of information and do not qualify as a practical application of the judicial exception. See MPEP 2106.05(g). These additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. The claims as a whole do not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. The claims are directed to an abstract idea without a practical application.
Step 2B Analysis
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception because, when considered separately and as an ordered combination, they do not add significantly more (also known as an “inventive concept”) to the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of a system, an electronic certificate, a processor, a device, an electronic tag, a server, an interface, an electronic ledger, a blockchain, a near-field communication (NFC) tag; amount to no more than mere components to implement the judicial exception using a generic computer components. For the same reason these elements are not sufficient to provide an inventive concept. Mere instructions to apply an exception using a generic computer component cannot provide an inventive concept. The limitations of:
transmitting the tag ID;
transmitting the product information and the ownership information;
and displaying the product information and the ownership information.
as drafted are insignificant extra-solution activity. These steps are mere data gathering and storing and do not qualify as significantly more than the judicial exception as they are well-understood, routine, and conventional activity when clamed in a merely generic manner (as it is here). See MPEP 2106.05(g). See Applicant’s specification paragraphs [0042-0050], about implementation of the abstract idea using general purpose or special purpose computing devices; and MPEP 2106.05(f) where applying a computer as a tool is not indicative of significantly more. Accordingly, these additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. Thus Applicant’s claims are not patent eligible.
Dependent Claims Analysis
As for dependent claims 5, 6, 8, 10, 12, 14, and 16-20 these claims recite limitations that further define the same abstract idea noted in independent claims 1, 7, and 11. Therefore, claims 5, 6, 8, 10, 12, 14, and 16-20 are considered ineligible subject matter for the reasons given above.
As for dependent claims 2-4, 9, 13 these claims recite limitations that further define the same abstract idea noted in independent claims 1, 7, and 11. In addition, the recite the additional elements of an electronic ledger, a blockchain, a near-field communication (NFC) tag. The components are recited at a high-level of generality such that it amounts to no more than mere instructions to apply the exception using a generic computer component. This is not indicative of a practical application or significantly more. Accordingly, these additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application and do not amount to significantly more than the abstract idea itself. Therefore, claims 2-4, 9, and 13 are considered ineligible subject matter.
As for dependent claims 15, these claims recite limitations that further define the same abstract idea noted in independent claim 11. In addition, the recite the additional elements of
receiving, by the second party, a notification indicating that a transfer of ownership of the product is pending;
This is considered insignificant extra-solution activity, because as drafted the limitations are mere data gathering and storing of information. These limitations do not qualify as a practical application of the judicial exception or significantly more. See MPEP 2106.05(g). Accordingly, these additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application and do not amount to significantly more than the abstract idea itself. Therefore, claim 15 are considered ineligible subject matter.
Thus, the dependent claims 2-6, 8-10, and 12-20 are not patent-eligible either.
Examiner Request
The Applicant is requested to indicate where in the specification there is support for amendments to claims should Applicant amend. The purpose of this is to reduce potential 35 USC 112(a) or 35 USC 112 first paragraph issues that can arise when claims are amended without support in the specification. The Examiner thanks the Applicant in advance.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by McKenzie, US Patent Application Publication NO 2021/0248653.
Regarding Claim 1;
A system for managing product ownership comprising:
a tag incorporated into a product, the tag having a tag ID;
an electronic certificate unique to the product; and
See McKenzie [0024] In some embodiments, the product authentication system relies on NFC tags attached to physical products and associated transactions issued on a blockchain. …. Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator. In this manner, the product authentication system issues a secure digital authenticity certification using the blockchain to store and manage identities and NFC tags and to link the NFC tags to corresponding products. Furthermore, an authentication flag in the product authentication data store can be updated by the seller for the tag to identify an authentic original product for a corresponding brand. Attaching a tamper-proof tag that certifies authenticity of a product and uniquely and digitally identifies a sold product reduces counterfeits both for tags and products. It also reduces authentication costs as the items are already identified and can be automatically authenticated once they re-enter the market. One of ordinary skill in the art will recognize that physical tags can be attached to products using any number of means for attaching including, for example, adhesives, sewing, stitching, gluing, ironing on, tying, buttoning, fastening, pinning, injecting, embedding, welding, stamping, silk screening, molding, screwing, nailing, and so on.
a processor configured to:
associate the electronic certificate with the tag; and
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on.
record ownership information of the product in the electronic certificate.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 2;
The system of claim 1, wherein the electronic certificate is stored in an electronic ledger.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 3;
The system of claim 2, wherein the electronic ledger is a blockchain.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 4;
The system of claim 1, wherein the tag is a near-field communication (NFC) tag.
See McKenzie [0024] In some embodiments, the product authentication system relies on NFC tags attached to physical products and associated transactions issued on a blockchain.
Regarding Claim 5;
The system of claim 1, wherein the processor is further configured to update the ownership information in the electronic certificate in response to a change in ownership of the product.
See McKenzie [0024] Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator. In this manner, the product authentication system issues a secure digital authenticity certification using the blockchain to store and manage identities and NFC tags and to link the NFC tags to corresponding products. Furthermore, an authentication flag in the product authentication data store can be updated by the seller for the tag to identify an authentic original product for a corresponding brand.
[0021] If the product is deemed to be authentic, a physical tag is attached to the product and the product is given a unique product identifier, each of which is used to track the product as it is sold and re-sold over the course of its life.
Regarding Claim 6;
The system of claim 1, wherein the processor is further configured to record a product ID, the tag ID, and a scan history of the tag in the electronic certificate.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
[0033] As another example, the product authentication store may include, for each authenticated product, a history of transactions involving that product or a list of previous owner of that product.
[0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership.
Regarding Claim 7;
A method for managing product ownership comprising:
scanning, by a device, an electronic tag having a tag ID;
See McKenzie [0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership. When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership.
transmitting, by the device, the tag ID to a server;
See McKenzie [0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership. When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership.
matching, by the server, the tag ID to a certificate associated with a product;
See McKenzie [0033] FIG. 3 is a data diagram illustrating a product authentication store in accordance with some embodiments of the disclosed technology. In this example, table 300 includes rows 340, each row corresponding to a different tagged product. Column 310 represents the identifier associated with the product, such as an identity token. Column 320 represents the unique identifier associated with the tag attached to the product. Column 325 stores an indication of the current owner of the authenticated product associated with the corresponding tag. Column 330 stores an indication of whether the product has been reported as having been tampered with, stolen, or lost. In this example, a value of True indicates that the product has been tampered with, stolen or lost, while a value of False indicates that the product has not been tampered with, stolen, or lost. Each of columns 331 store the date on which the corresponding authentication was performed. Each of columns 332 store a unique identifier for the authenticator that performed the corresponding authentication. Columns 331 and 332 represent various authentications for a product.
[0035] FIG. 5 is a flow diagram illustrating steps of an exchange component in accordance with some embodiments of the disclosed technology. The exchange component facilitates a transaction between a buyer and a seller. In block 511, the potential buyer sends a request for the product to the potential seller (e.g., an initial or original seller or reseller). In some examples, the request includes identification information for the potential buyer while in other examples the request can be anonymous. In this case, the potential buyer can provide identification information, for example, after the buyer and the seller have agree on terms. In block 521, the seller receives the request. In blocks 512 and 522 the potential buyer and seller negotiate over terms of the purchase, such as price, shipping, insurance, payment processing, timelines, etc. In some cases, the potential buyer and/or seller may have fixed terms and be unwilling to negotiate, in other cases the negotiate term may be prolonged. In decision blocks 513 and 523, if terms of the exchange are accepted, then the seller continues at block 524, else the component returns a value of false at block 531, indicating that the exchange was not successful. For example, the component may receive a message indication acceptance of an offer from the potential buyer or the seller. In block 524, the seller logs in to the scanner application to prove their identity (if they have not done so already) and scans the tag attached to the product to, for example, provide proof of ownership (verifiable via a secure, trusted tracking system, such as a blockchain, and/or the product authentication store) and proof of presence . In decision block 525, if the seller's scanner application confirms that the product's authentication is valid (by, for example, checking transactions in a blockchain or a product authentication data store) and that the product is owned by the seller, processing continues at block 526, else the component returns false. In block 526, the scanner application generates a transaction indicating that the seller is selling the tagged product to the potential buyer, the transaction including identification information for the product, the seller, and the buyer, such as a unique identifier associated with each, a public key associated with each, etc. and information about the transaction, such as the date and time of the transaction, the cost, an indication that the transaction is a transfer of ownership, etc.
retrieving, by the server, a product information and an ownership information based on the certificate;
See McKenzie [0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership. When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership.
transmitting, by the server, the product information and the ownership information to the device; and
See McKenzie [0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership. When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership.
displaying, by the device, the product information and the ownership information on an interface.
See McKenzie [0022] In some embodiments, the product authentication system uses tamper-proof tags or chips, such as NFC Integrated Circuits (ICs) or dual-frequency ICs tags with a Secure Unique NFC (SUN) mechanism that generates a secure unique NFC message authentication each time the tag is scanned or read, for example, for proof of presence, authentication, and ownership. When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership.
Regarding Claim 8;
The method of claim 7 further comprising:
associating the tag ID with the certificate;
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on.
associating the certificate with a current owner; and
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
registering the certificate in a ledger.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 9;
The method of claim 8, wherein the ledger includes a blockchain.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 10;
The method of claim 8 further comprising verifying, by the server, a tap token with the tag ID.
See McKenzie [0020] Systems and methods for authenticating products, such as products from original manufacturers and/or resellers, that provide a trusted and reliable mechanism for buyers and sellers to prove the authenticity of a product and for authenticators to establish an authentication that can be relied on during downstream transactions is provided. In some embodiments, a blockchain-based product authentication system is provided that allows entities within a chain of commerce (e.g., suppliers, manufacturers, distributors, retails, consumers, consignors, resellers) to verify the authenticity of items by way of trusted authenticators and trusted audit processes. The product authentication system enables users to rely on product authentications via off-channel sales with the use of cryptography, blockchain, digital assets, and tagging hardware and software such as Near Field Communication (NFC) or other technologies that supports the need to define a digital twin of a physical product, non-fungible tokens (e.g., ERC721 non-fungible tokens), and so on. Thus, the product authentication system provides a product authentication service that reduces the amount of repeated or duplicated effort in authenticating products, thereby saving valuable resources required for performing such activities. The product authentication system provides a more transparent, efficient, and accessible solution that connects businesses and consumers.
[0037] The NFC circuitry 713 can include digital storage elements that store information, for example, identification information, website URLs, and/or other information, including authentication codes, that can be used to identify the object 730, and/or the source of the object 730, and/or otherwise provide an authentication mechanism by which parties can confirm the authenticity of the object 730.
Regarding Claim 11;
A method for managing product ownership comprising:
scanning a tag associated with a certificate unique to a product, the tag having a tag ID and the product having a product ID;
See McKenzie [0022] When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership. Moreover, the transaction between the buyer and the seller can be recorded in a blockchain transaction to provide further proof of the transaction.
associating an ownership information with the certificate; and
See McKenzie [0022] When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership. Moreover, the transaction between the buyer and the seller can be recorded in a blockchain transaction to provide further proof of the transaction.
in response to a transfer of ownership, updating the ownership information to reflect a new owner of the product.
See McKenzie [0022] When a product is sold, the seller can scan the tag to provide proof of ownership and proof of presence and then ship the product to the buyer. When the buyer receives the product, the buyer can scan the tag to confirm and claim ownership. Moreover, the transaction between the buyer and the seller can be recorded in a blockchain transaction to provide further proof of the transaction.
Regarding Claim 12;
The method of claim 11, further comprising recording a first entry including the tag ID, the product ID, and the ownership information on a ledger.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 13;
The method of claim 12, wherein the ledger includes a blockchain.
See McKenzie [0024] Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on. Furthermore, information about the product and tag is issued on a blockchain, such as a tag id, current owner, date and time authenticated, authenticator, and so on using a transaction signed using a private key (of a public/private key pair) of the authenticator.
Regarding Claim 14;
The method of claim 12, wherein the updating the ownership information further comprising recording a second entry including the tag ID, the product ID, information pertaining to a new owner in the ledger.
See McKenzie [0024] In some embodiments, the product authentication system relies on NFC tags attached to physical products and associated transactions issued on a blockchain. Similarly, non-physical tags or tokens can be associated with non-physical goods, such as virtual goods and associated transactions issued on the blockchain. Initially, a product's authenticity is confirmed by one or more individuals trained to recognize authenticity, such as employees of a manufacturer, employees of a reseller, a third-party expert, etc. Once the product is authenticated, a uniquely-identifiable NFC tag is attached to, or associated with, the product, an identifier can be created for the product (such as an identity token), and the NFC Tag and identification information are associated in the product authentication system in, for example, a product authentication data store. The identifier created for the product can be a digital cryptographic identifier (e.g., a hash value generated using a secure hashing algorithm), a hash value generated from a description (or partial description) of the product and/or a serial number associated with the product, and so on.
Regarding Claim 15;
The method of claim 11 further comprising:
selecting, by a first party, a second party of whom to transfer an ownership of the product;
See McKenzie [0035] FIG. 5 is a flow diagram illustrating steps of an exchange component in accordance with some embodiments of the disclosed technology. The exchange component facilitates a transaction between a buyer and a seller. In block 511, the potential buyer sends a request for the product to the potential seller (e.g., an initial or original seller or reseller). In some examples, the request includes identification information for the potential buyer while in other examples the request can be anonymous. In this case, the potential buyer can provide identification information, for example, after the buyer and the seller have agree on terms. In block 521, the seller receives the request. In blocks 512 and 522 the potential buyer and seller negotiate over terms of the purchase, such as price, shipping, insurance, payment processing, timelines, etc. In some cases, the potential buyer and/or seller may have fixed terms and be unwilling to negotiate, in other cases the negotiate term may be prolonged. In decision blocks 513 and 523, if terms of the exchange are accepted, then the seller continues at block 524, else the component returns a value of false at block 531, indicating that the exchange was not successful. For example, the component may receive a message indication acceptance of an offer from the potential buyer or the seller. In block 524, the seller logs in to the scanner application to prove their identity (if they have not done so already) and scans the tag attached to the product to, for example, provide proof of ownership (verifiable via a secure, trusted tracking system, such as a blockchain, and/or the product authentication store) and proof of presence . In decision block 525, if the seller's scanner application confirms that the product's authentication is valid (by, for example, checking transactions in a blockchain or a product authentication data store) and that the product is owned by the seller, processing continues at block 526, else the component returns false. In block 526, the scanner application generates a transaction indicating that the seller is selling the tagged product to the potential buyer, the transaction including identification information for the product, the seller, and the buyer, such as a unique identifier associated with each, a public key associated with each, etc. and information about the transaction, such as the date and time of the transaction, the cost, an indication that the transaction is a transfer of ownership, etc.
receiving, by the second party, a notification indicating that a transfer of ownership of the product is pending;
See McKenzie [0035] In block 514, the buyer receives the product. In block 515, the buyer logs in to the scanner application to prove their identity and scans the tag attached to the product to confirm transfer of the product. In some examples, buyer's scanner application also finalizes payment to the seller.
scanning, by the second party, the tag; and
See McKenzie [0035] In block 514, the buyer receives the product. In block 515, the buyer logs in to the scanner application to prove their identity and scans the tag attached to the product to confirm transfer of the product. In some examples, buyer's scanner application also finalizes payment to the seller.
accepting, by the second party, the ownership of the product from the first party.
See McKenzie [0035] In block 514, the buyer receives the product. In block 515, the buyer logs in to the scanner application to prove their identity and scans the tag attached to the product to confirm transfer of the product. In some examples, buyer's scanner application also finalizes payment to the seller.
Regarding Claim 16;
The method of claim 15, wherein the selecting further comprising providing a first interface on a first device for the first party to select the second party.
See McKenzie [0035] In decision blocks 513 and 523, if terms of the exchange are accepted, then the seller continues at block 524, else the component returns a value of false at block 531, indicating that the exchange was not successful. For example, the component may receive a message indication acceptance of an offer from the potential buyer or the seller. In block 524, the seller logs in to the scanner application to prove their identity (if they have not done so already) and scans the tag attached to the product to, for example, provide proof of ownership (verifiable via a secure, trusted tracking system, such as a blockchain, and/or the product authentication store) and proof of presence . In decision block 525, if the seller's scanner application confirms that the product's authentication is valid (by, for example, checking transactions in a blockchain or a product authentication data store) and that the product is owned by the seller, processing continues at block 526, else the component returns false. In block 526, the scanner application generates a transaction indicating that the seller is selling the tagged product to the potential buyer, the transaction including identification information for the product, the seller, and the buyer, such as a unique identifier associated with each, a public key associated with each, etc. and information about the transaction, such as the date and time of the transaction, the cost, an indication that the transaction is a transfer of ownership, etc.
Regarding Claim 17;
The method of claim 15, wherein receiving further comprising providing a second interface including the notification on a second device to the second party.
See McKenzie [0035] In block 514, the buyer receives the product. In block 515, the buyer logs in to the scanner application to prove their identity and scans the tag attached to the product to confirm transfer of the product. In some examples, buyer's scanner application also finalizes payment to the seller.
Regarding Claim 18;
The method of claim 15, wherein the accepting further comprising providing a third interface on a second device to accept the ownership of the product.
See McKenzie [0035] For example, the component may receive a message indication acceptance of an offer from the potential buyer or the seller.
[Claim 2] 2. The method of claim 1, further comprising: receiving from a buyer an indication of the generated transaction; sending to the first owner an offer message offering to purchase the first product for an offer amount; receiving from the first owner an accept message; receiving from the first owner a scan of the physical tag, the scan verifying the authenticity of the first product; providing, for recordation in the secure tracking system, a transaction to transfer ownership of the first product to the buyer as a new owner of the first product; receiving from the new owner of the first product an acceptance message; and providing, for recordation in the secure tracking system, a transaction indicating acceptance of the first product by the new owner of the first product.
Regarding Claim 19;
The method of claim 11 further comprising providing a fourth interface to a first party of the product that the product is lost or missing.
See McKenzie [0023] The product authentication system includes several components for managing and verifying authentications, including a product authentication blockchain, tagging hardware and software, a scanner application, and/or cryptography and encryption. In some embodiments, the product authentication blockchain manages digital identities and NFC tags, maintains records of ownership of products, manages fees payments for transfer of ownership and product purchase through smart contracts, manages and authenticates buyers and sellers' identities, manages messaging system to log offers from potential buyers, manages and keeps record of products within a virtual marketplace or selling/trading platform, logs stolen, lost, and/or tampered-with products, etc.
[0033] FIG. 3 is a data diagram illustrating a product authentication store in accordance with some embodiments of the disclosed technology. In this example, table 300 includes rows 340, each row corresponding to a different tagged product. Column 310 represents the identifier associated with the product, such as an identity token. Column 320 represents the unique identifier associated with the tag attached to the product. Column 325 stores an indication of the current owner of the authenticated product associated with the corresponding tag. Column 330 stores an indication of whether the product has been reported as having been tampered with, stolen, or lost. In this example, a value of True indicates that the product has been tampered with, stolen or lost, while a value of False indicates that the product has not been tampered with, stolen, or lost.
Regarding Claim 20;
The method of claim 19 further comprising in response to the tag being scanned after the product has been reported as lost or missing, notifying the first party of the product.
See McKenzie [0023] The scanner application is a mobile application in communication with the product authentication system that reads NFC tags and serves as an interface between resellers, buyers, sellers, products, and the blockchain. Users of the product authentication system can use the application to authenticate and verify products, transfer ownership of products, connect to buyers and sellers of products through, for example, a messaging component, view products, flag products as stolen, personalized experiences can be displayed through a scan of the tag on the product, and products can be automatically uploaded to the online marketplace through scanning or tapping the NFC tag
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHAEL J WARDEN whose telephone number is (571)272-9602. The examiner can normally be reached M-F; 9-6 CDT.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Bennett M Sigmond can be reached at 303-297-4411. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MICHAEL J. WARDEN/
Examiner
Art Unit 3694
/GREGORY S CUNNINGHAM II/Primary Examiner, Art Unit 3694