DESC:This application is based on and derives the benefit of Indian Provisional Application 201621011915, the contents of which are incorporated herein by reference.

TECHNICAL FIELD
[001] The embodiments herein generally relate product authentication, and more particularly to tracking and authenticating a product item using a unique ID (UID) associated with that product item.

BACKGROUND
[002] In the manufacturing of various pieces of equipment, products and technology, it is common to have elements of items manufactured in remote or disparate locations and shipped for assembly to other locations, or as replacement parts for installation in the field. In many cases, the products may change hands a couple of times before they are eventually transferred to the end user. In some cases, an unauthorized transfer of products from primary sales such as manufacturers to secondary sales such as a retailer may occur. Unauthorized persons or organizations may also create counterfeit items and make them available to users in the market.
[003] Existing technology provide means to authenticate products based on a centralized database with information of the product and an end user device, which may be easily tracked by a third party. Further, the possibilities of the product being counterfeited also increases.

OBJECTS
[004] The principal object of the embodiments herein is to provide methods and systems for generating a unique ID (UID) and attaching the UID to a product item.
[005] Another object of the embodiments herein is to provide methods and systems for tracking the product item while distributing from primary sales to secondary sales.
[006] Another object of the embodiments herein is to provide methods and systems for checking genuineness of the product item.

BRIEF DESCRIPTION OF FIGURES
[007] The embodiments of this invention are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[008] FIG. 1 illustrates a unique ID (UID) generation system, according to embodiments as disclosed herein;
[009] FIG. 2 is a flow diagram illustrating a method for generating the UID, according to embodiments as disclosed herein;
[0010] FIG. 3 illustrates a UID authentication system, according to embodiments as disclosed herein;
[0011] FIG. 4 is a block diagram of a server, according to embodiments as disclosed herein; and
[0012] FIG. 5 is a flow diagram 500 illustrating a method for authenticating the product using the UID, according to embodiments as disclosed herein.

DETAILED DESCRIPTION
[0013] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0014] The embodiments herein provide methods and systems for generating a unique ID (UID), attaching the UID to a product item, and tracking and authenticating the product item using the UID. In an embodiment, a UID generation module generates the UID. The UID can be generated based on the territory of a distributor. Further, based on the territory of the distributor a short code can be prefixed in the UID. For example, the short code can be of two or more alphanumerical characters, used to generate the UID. In another embodiment, the UID can be attached to each product items during generation of invoicing. In another embodiment, a user can check genuineness of the product item through suitable means such as an application, a website, SMS (Short Messaging Service), IM (Instant Messaging), and so on.
[0015] Referring now to the drawings, FIG. 1 illustrates the UID generation system 100, according to embodiments as disclosed herein. In an embodiment, the UID generation system 100 can be present at a generating entity and includes an ID generation module 102, which receives details of the product and generates an UID as an output, based on the provided details. Examples of the entity can be, but not limited to, a manufacturer of the product, a distributor of the item, an exporter of the item, an importer of the item, and so on. A user and/or the entity can provide the details. The details can also be fetched from a pre-determined location, such as a database, the Cloud, a file server, a data server, a computing system, and so on. The term UID as used in this specification is unique with respect to a product item, which can be implemented physically in the form of at least one of a barcode, RFID tag, a sticker with the UID, etching, engraving, printing, or the like. Optionally, the product details can include but are not limited to, product name, model number, distributor name, shipping details, territory name, date of sell, date of manufacture, location of manufacture, name of manufacturer, the source who can use this product, the type of application where the product can be used (for example, consider that the product is a vehicle spare part, the detail can include the vehicle model and year details in which the product can be used) and so on. Further, the generated UID is stored in a database 104.
[0016] In an example herein, a short code of one or more alphanumeric character is given to each distributor so that all UIDs generated by the distributor will have a prefix same as of the distributor short code. Further, the short code is assigned based on the territory and district. For example, a short code of “BP” is given to “x Automobiles” and one of the UID generated by him is “AB123ADLK1” whose territory is Andhra Pradesh. Mechanics in all the districts of Andhra Pradesh will have prefix of “BP” in their registration code. For example, one of the mechanics registered by them in Andhra Pradesh is “BP4325”. So mechanics “BP4325” will only get the benefit of UIDs generated by “x Automobiles” with Prefix BP.
[0017] FIG. 2 is a flow diagram 200 illustrating a method for generating the UID, according to embodiments as disclosed herein. As shown, in step 201, the details are provided to generate the UID. The input can be provided manually. The input can also be fetched from a pre-defined location, such as a database. In step 202, the UID generation module 102 generates the UID. Further in steps 204 and 205, the generated UID is outputted, so that the UID can be attached to the product item. The UID can be outputted in at least one form such as a barcode, RFID tag, a sticker with the UID, etching, engraving, printing, a display, or the like. The various actions in method 200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.
[0018] FIG. 3 illustrates a UID authentication system 300, according to embodiments as disclosed herein. In an embodiment, the information regarding the UID of the product item is scanned through a suitable means such as a scanning device, including but not limited to a cellphone, a mobile phone, a tablet, a computer, a wearable computing device, a dedicated scanning device, or any other device equipped with a means to scan the UID. The information regarding the UID of each product item is produced and is transmitted to an authentication engine 302, via a communication means. The information regarding the UID can comprise of, but not limited to, product name, distributor name, shipping details, territory name, date of sell, date of manufacture and so on.
[0019] FIG. 4 is a block diagram of the authentication engine 302, according to embodiments as disclosed herein. The authentication engine 302 includes an authentication module 401, a memory module 402 and a communication interface module 403. The authentication module 401 can authenticate the UID by communicating with the database 104. The authentication module 401 compares the UID with the database 104 of valid UIDs. If the UID on the product item does not exist in the database, it is immediately flagged a forgery so that the buyer is warned. If the UID matches with the UID stored in the database 104, the system may return a message that the product item is authentic. In another embodiment, the result of the check is sent in addition to auxiliary information regarding the product item. For example, the system may return a message with the information of the product item wherein, the information can be the name of the product item, date of manufacturing, place of manufacturing, date of selling, to whom it was sold and so on.
[0020] The authentication engine 302 includes the memory module 402. The memory module 402 is configured to store and execute programming instructions in order to control various aspects of the operation of the UID generation system.
[0021] The authentication engine 302 includes a communication interface module 403. Different part of the UID generation system such as server, database, UID generation module, etc. of the UID generation system can communicate with each other through the communication interface 403. Further, the communication interface 403 can be wired or wireless.
[0022] FIG. 5 is a flow diagram 500 illustrating a method for authenticating the product using the UID, according to embodiments as disclosed herein. As shown, in step 501, the user scans the UID of the product. The UID is then sent to the authentication engine 302 for authentication. Additional details can be provided to the authentication engine 302, such as the location of the user scanning the UID, an identity associated with the user, and so on. In step 502, the authentication engine 302 authenticates the product. The authentication engine 302 can authenticate the product by comparing the UID with the database 104 of valid UIDs. The authentication engine 302 can determine that the product item passes the authentication process, if the UID matches with a UID stored in the database 104. The authentication engine 302 can determine that the product item is not authentic, if the UID does not match with a UID stored in the database 104. The authentication engine 302 can also check if the product is in the right area by checking if the user is authorized to access/use the product, and so on. If the authentication engine 302 is able to authenticate the product, in step 503, the authentication engine 302 sends an alert to the user confirming that the product is authentic. The success message can be provided using at least one a web browser, a mobile application, a pop-up, widget, an email, a SMS, an IM, and so on. In an embodiment herein, the authentication engine 302 can send additional information regarding the product (such as the manual, installation process, guides, manufacturing date, and so on). In step 504, the system gives a failure alert, if the authentication engine 302 is unable to determine that the product is authentic. The term ‘authentic’ can refer to at least one situation such as, but not limited to, the product being manufactured by an unauthorized manufacturer, the product being at a location/service center/workshop where the product is not supposed to be, and so on. The failure alert can be provided using at least one a web browser, a mobile application, a pop-up, widget, an email, a SMS, an IM, and so on. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.
[0023] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
,CLAIMS:CLAIMS
We claim:
1. A method for authenticating a product using a Unique Identity (UID) associated with the product, the method comprising
scanning the UID associated with the product by a user, wherein the UID is generated using product details comprising at least one of product name, model number, distributor name, shipping details, territory name, date of sell, date of manufacture, location of manufacture, name of manufacturer, the source who can use this product, and the type of application where the product can be used;
checking if the product is authentic using the scanned UID by the authentication engine (302), wherein checking if the product is authentic further comprises comparing the UID with a database (104) of valid UIDs; and if the product is in the right area by checking if the user is authorized to access/use the product; and
providing an alert to the user by the authentication engine (302) based on the results of the authentication.

2. The method, as claimed in claim 1, wherein the method further comprises sending an alert to the user that the product is authentic by the authentication engine (302), on determining that the product is authentic.
3. The method, as claimed in claim 2, wherein the method further comprises sending additional information about the product.

4. The method, as claimed in claim 1, wherein the method further comprises sending a failure alert to the user that the product is not authentic by the authentication engine (302), on determining that the product is not authentic.

5. An authentication engine (302) for authenticating a product using a Unique Identity (UID) associated with the product, the authentication engine (302) configured for
receiving a scanned UID associated with the product from a user, wherein the UID is generated using product details comprising at least one of product name, model number, distributor name, shipping details, territory name, date of sell, date of manufacture, location of manufacture, name of manufacturer, the source who can use this product, and the type of application where the product can be used;
checking if the product is authentic using the scanned UID, wherein checking if the product is authentic further comprises comparing the UID with a database (104) of valid UIDs; and if the product is in the right area by checking if the user is authorized to access/use the product; and
providing an alert to the user based on the results of the authentication.

6. The authentication engine, as claimed in claim 5, wherein the authentication engine (302) is further configured for sending an alert to the user that the product is authentic, on determining that the product is authentic.

7. The authentication engine, as claimed in claim 6, wherein the authentication engine (302) is further configured for sending additional information about the product.

8. The authentication engine, as claimed in claim 5, wherein the authentication engine (302) is further configured for sending a failure alert to the user that the product is not authentic, on determining that the product is not authentic.