Abstract:
A product registration system that enables manufacturers to track products, log user interactions with the products, and provide services to those users interacting with products. This is handled by provisioning a Uniform Resource Identifier (URI), which is embedded on products a manufacturer would like to track and service. Interrogation of the URIs by users are logged and services provided over the network based on the manufacturer&#39;s needs.

Description:
RELATED APPLICATIONS 
       [0001]    This application claims priority to U.S. Provisional Patent Application No. 62/276,500, filed Jan. 8, 2016, which is hereby incorporated by reference herein in its entirety. 
     
    
     FIELD OF THE INVENTION 
       [0002]    The invention relates to the field of product identification. More particularly, the invention relates to techniques for labeling products with web addresses for product identification and for delivery of product services. 
       BACKGROUND OF THE INVENTION 
       [0003]    There are multiple methods of identifying manufactured goods. Many such goods are labelled with a Universal Product Code (UPC). A UPC contains a Manufacturer&#39;s identification number and an item number. This enables appropriately configured UPC readers to identify a given product&#39;s type and manufacturer, but no additional information directly. Following the adoption of UPC, a new standard was developed: the Electronic Product Code (EPC). The principle advantage of EPC over UPC is its capacity. An EPC, with maximum size of 256 bits, can uniquely identify several orders of magnitude more items than UPC. EPC codes are often embedded in Radio Frequency Identification (RFID) tags. An EPC typically encodes a product&#39;s serial number in addition to product type and manufacturer. This information, once captured by an appropriately configured reader, may be used to lookup the associated product&#39;s data in a product database. 
         [0004]    Unfortunately, there are limitations with these methods. Principally:
       1. There is no commonly accepted network to lookup EPC tag information. If a company scans a product&#39;s RFID tag with EPC data encoded on it, the data is useless unless the company has a record of the product&#39;s EPC.   2. Specialized hardware is required to scan EPC codes embedded on RFID tags. The general public cannot identify EPC codes with technologies they have everyday access to.       
 
         [0007]    In addition to limitations with EPC-based product identification, there are associated limitations with users&#39; information technology systems. Specifically:
       1. Product data associated with an EPC code is stored in restricted-access networks. If a company wants to share certain product data with individuals or companies outside their network, they must implement idiosyncratic integrations or serve their data openly outside their network. The same is true in the reverse case (that is, users outside the network want to share data with the originating company).   2. There is no platform that links EPC or other identifying product codes across manufacturers, in order to deliver common services (for example, warranty claims) to users that interface with products from multiple manufacturers.       
 
         [0010]    In summary, there is no known platform that can provision identifying product codes, manage product related data and services, and maintain user information and access rights. 
       SUMMARY OF THE DISCLOSURE 
       [0011]    In one embodiment, techniques disclosed herein may be realized as a web-based platform for facilitating product identification and service delivery. The web-based platform may comprise one or more computer processors executing instructions. The one or more computer processors may be configured to store, in a database, data indicative of an identifier associated with a product unit and a set of data specific to the product unit. The set of data may comprise first data available to all users and second data only available to authorized users. The one or more computer processors may further be configured to receive a user request to access data associated with the product unit from a user. The request may comprise data indicative of the identifier. The one or more computer processors may further be configured to determine a level of authorization for the user. The level of authorization may indicate that the user is authorized to access only the first data associated with the product unit identified by the identifier. The one or more computer processors may be configured to transmit the first data to the user. 
         [0012]    In accordance with other aspects of this embodiment, the second data specific to the product unit comprises a real-time operation status of the product unit, real-time operational data of the product unit, or both. 
         [0013]    In accordance with other aspects of this embodiment, the one or more computer processors may further be configured to log user interactions with the product unit through the web-based platform. 
         [0014]    In accordance with other aspects of this embodiment, the one or more computer processors may further be configured to receive a second user request to access data associated with the product unit from a second user. The second request may comprise data indicative of the identifier. The one or more computer processors may further be configured to determine a second level of authorization for the user. The level of authorization may indicate that the second user is authorized to access both the first data and the second data associated with the product unit identified by the identifier. The one or more computer processors may further be configured to transmit the first data and the second data to the user. 
         [0015]    In accordance with other aspects of this embodiment, the one or more computer processors may further be configured to manage user credentials to access the first data, the second data, or both, associated with the product unit. 
         [0016]    In accordance with other aspects of this embodiment, the identifier may be attached to the product unit in a Uniform Resource Identifier (URI). 
         [0017]    In accordance with other aspects of this embodiment, the identifier may be embedded in at least one of a Near Field Communication chip or a Quick Response code. 
         [0018]    In accordance with other aspects of this embodiment, the first data may not comprise any data, such that no data is available to public users. 
         [0019]    In another embodiment, techniques disclosed herein may be realized as a method based on a web-based platform for facilitating product identification and service delivery. According to the method, data indicative of an identifier associated with a product unit and a set of data specific to the product unit may be stored in a database. The set of data may comprises first data available to all users and second data only available to authorized users. A user request to access data associated with the product unit from a user may be received. The request may comprise data indicative of the identifier. A level of authorization for the user may be determined. The level of authorization may indicate that the user is authorized to access only the first data associated with the product unit identified by the identifier. The first data to the user may be transmitted. 
         [0020]    In still another embodiment, techniques disclosed herein may be realized as a non-transitory computer readable medium storing a computer-readable program for a web-based platform for facilitating product identification and service delivery. The program may include computer-readable instructions to store, in a database, data indicative of an identifier associated with a product unit and a set of data specific to the product unit. The set of data may comprise first data available to all users and second data only available to authorized users. The program may further include computer-readable instructions to receive a user request to access data associated with the product unit from a user. The request may comprise data indicative of the identifier. The program may further include computer-readable instructions to determine a level of authorization for the user. The level of authorization may indicate that the user is authorized to access only the first data associated with the product unit identified by the identifier. The program may further include computer-readable instructions to transmit the first data to the user. 
         [0021]    The present disclosure will now be described in more detail with reference to particular embodiments thereof as shown in the accompanying drawings. While the present disclosure is described below with reference to particular embodiments, it should be understood that the present disclosure is not limited thereto. Those of ordinary skill in the art having access to the teachings herein will recognize additional implementations, modifications, and embodiments, as well as other fields of use, which are within the scope of the present disclosure as described herein, and with respect to which the present disclosure may be of significant utility. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0022]    For a more complete understanding of the invention, reference is made to the following description and accompanying drawings, in which: 
           [0023]      FIG. 1  is an overview of the system described, including the transaction and indexing systems; 
           [0024]      FIG. 2  is a detailed view of the transaction system; 
           [0025]      FIG. 3  is a detailed view of the indexing system; 
           [0026]      FIG. 4  is an example user interaction with the system; and 
           [0027]      FIG. 5  is an example tag appended to the manufacturer&#39;s product. 
       
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
       [0028]    One embodiment of the system is illustrated in  FIG. 1 . The Transaction System [ 102 ] and the Indexing System [ 103 ] are described in detail in  FIG. 2  and  FIG. 3 , respectively. Both are software programs. In the preferred embodiment, they are deployed as web applications. However, they may also be deployed on a local network. In the preferred embodiment, the Network [ 104 ] is the Internet, but can be any network, public or private. 
         [0029]    The Manufacturing System [ 106 ] is connected to the Network [ 104 ]. This is required for communication between Manufacturing System [ 106 ] and the Indexing System [ 103 ]. It is managed by the manufacturer of the materials to be identified via the system. 
         [0030]    Client Device  1  [ 112 ] and Client Device  2  [ 114 ] are devices used to access and exchange data with the system via the Network [ 104 ]. In this embodiment, Client Device  1  [ 112 ] is used by an employee of the manufacturer and Client Device  2  [ 114 ] is used by the tagged product&#39;s end user. In other examples, Client Device  1  [ 112 ] and Client Device  2  [ 114 ] could be used by resellers, logistics providers, members of the public, distributors, retailers, service engineers, or other individuals who might interface with the tagged product. 
         [0031]    Much of the product, user, and transactional data is handled by the Transaction System [ 102 ] detailed in  FIG. 2 . Client Device  1  [ 112 ] or any other client device interfaces with Transaction System [ 102 ] through the Network [ 104 ]. Data is exposed to the client via the Front End Server [ 220 ], which is in turn sent data from the Presentation System [ 216 ]. The Presentation System [ 216 ] receives data from, and pushes client submitted data to three principal databases. These are the Product Data Storage [ 210 ], the Transaction Data Storage [ 212 ], and the User Data Storage [ 214 ]. User Data Storage [ 214 ] is also connected to the Authentication System [ 218 ] to provide user permissions and verify user credentials. 
         [0032]    The principal application of Indexing System [ 103 ], detailed in  FIG. 3 , is to provision one or more Uniform Resource Identifiers (URIs) to the Manufacturing System [ 106 ]. It is connected to and interfaces with the Manufacturing System [ 106 ] through the Network [ 104 ]. It has access to many of the same resources available to the Transaction System [ 102 ]. Specifically, components of Product Data Storage [ 210 ], Transaction Data Storage [ 212 ], User Data Storage [ 214 ], the Authentication System [ 218 ], and the Front End Server [ 220 ] are shared. The Administrator System [ 304 ] is the principal system for the Manufacturing System [ 106 ] to request URIs from the URI Registration System [ 302 ]. It also is connected to the three data storage systems, enabling the manufacturer to access and update product-related data, transaction data and user data. It is connected to the Authentication System [ 218 ] to ensure data accessed and exchanged is between authorized parties only. Data is served back to the client via the Front End Server [ 220 ]. 
         [0033]    To associate a URI with a product, the URI must be embedded, etched, attached, or otherwise associated with a manufactured good. One way to do this is with an adhesive sticker. An example is shown in  FIG. 5 . Here, the Tag [ 502 ] is a example means of associating the URI with a product. The tag would be appended by the manufacturer, retailer, service shop, or any other user who would interface with the product. The URI is embedded in this example using a Near Field Communication (NFC) chip and a Quick Response (QR) code, but any auto-identification technology capable of embedding a URI may be used. The URI could also be represented visually. The Tag [ 502 ] might also include data about the product, manufacturer, or other identifying information. 
         [0034]    There are two distinct interactions with this system. The first is that of the manufacturer requesting one or more URIs for appending on one or more products. The second is the interaction between a client and the Transaction System [ 102 ], which occurs following interrogation of the URI by Client Device  1  [ 112 ]. 
         [0035]    First, when a manufacturer would like to track a given product, their Manufacturing System [ 106 ] accesses the Indexing System [ 103 ] over the Network [ 104 ]. The Authentication System [ 218 ] validates the permissions and identify of the manufacturer. The manufacturer then has access to the Administrator System [ 304 ]. Here they can request one or more URIs via the URI Registration System [ 302 ]. The assignment of URIs to manufacturers and to specific products are indexed in the URI Registration System [ 302 ]. Data in Product Data Storage [ 210 ], Transaction Data Storage [ 212 ], and User Data Storage [ 214 ] are all mapped to this index. 
         [0036]    The Administrator System [ 304 ] also allows the manufacturer to upload product data, user permissions, user data and other data types to the appropriate data stores within the Indexing System [ 103 ]. Manufacturer activity within the Indexing System [ 103 ] is logged in Transaction Data Storage [ 212 ]. For example, URI generation requests, updating user permissions, managing product data, and any other activity that might be relevant for application management could be logged. Using the Front End Server [ 220 ] or accessing the data stores via an Application Programming Interface (API), the manufacturer may download data related to interactions with their provisioned URIs and associated products. For example, the manufacturer could see which users had interrogated which product URIs, at what time, the nature of the interaction, and data from the Client Device  1  [ 112 ] such as location information, Internet Protocol (IP) address, media access control (MAC) addresses, and any other data that might be captured from the client device. The manufacturer and other authorized users may also view product sensor data that is sent to the Transaction System [ 102 ]. Sensor data, including streaming sensor data, can be linked directly to the application via TCP/IP or related protocols. Example sensors include GPS, accelerometer, pressure, temperature, and conductivity, but the application may include any sensor type. This sensor data may be sent to the application and made available to users in real-time or close to real-time. 
         [0037]    The second interaction is between a client interfacing with the URI (embedded on the manufacturer&#39;s product via a Tag [ 502 ]) and the Transaction System [ 102 ]. An example interaction is depicted in  FIG. 4 . Here a user in [ 402 ] interrogates the URI specific to the product the individual is interfacing with using Client Device  1  [ 112 ]. The client is served with the appropriate product data via the Front End Server [ 220 ]. The Authentication System [ 218 ] will then authenticate the user [ 404 ]. If the user&#39;s credentials are recognized [ 406 ], then the Presentation System [ 216 ] will serve the product data to be served to the identified user type [ 410 ]. If the user&#39;s credentials are not recognized, then the Presentation System [ 216 ] will pass publicly accessible product data and login or registration methods to the user [ 408 ] via Front End Server [ 220 ].