FIELD

[0001] The present application relates generally to computers and computer applications, and more particularly to a machine readable system such as a quick response code system.

BACKGROUND

[0002] While machine readable codes such as bar codes and QR codes can be provided associated with a product, such codes are static in nature. For example, scanning such bar codes and/or QR codes can lead to displaying or presentation of data, but does not provide an ability to a user to interact with another component such as a computer system providing the data. Currently, use of such codes also do not allow for uniquely identifying and/or processing a specific instance of a product.

BRIEF SUMMARY

[0003] The summary of the disclosure is given to aid understanding of an apparatus, computer system, computer architectural structure, machine readable code system and methods of thereof, and not with an intent to limit the disclosure or the invention. It should be understood that various aspects and features of the disclosure may advantageously be used separately in some instances, or in combination with other aspects and features of the disclosure in other instances. Accordingly, variations and modifications may be made to the computer system, the architectural structure, processor, register files, and/or their method of operation to achieve different effects.

[0004] In an aspect, an apparatus may include a container or a vial having a machine-readable code. The machine-readable code includes a specific code representing a specific instance of a product contained by the container. The machine-readable code also includes a link to information associated with the specific instance of the product. [0005] In an aspect, the machine -readable code, responsive to being scanned, is configured to cause a machine scanning the machine-readable code to automatically navigate to a web site page, allowing a user to interact with the web site page, for example, register and tract data associated with the specific instance of the product, and/or access or link to other information associated with the product.

[0006] In an aspect, a computer-implemented method can include generating a machine readable code to be associated with a container, the machine readable code uniquely identifying a specific instance of a product contained by the container. The method can also include creating in a data store an entry associated with the machine readable code, the data store being accessible by at least one microservice to provide information associated with the specific instance of the product, the entry further including a state associated with the machine readable code. The method can also include, responsive to receiving a scan of the machine readable code, performing an action based on the state. The state can automatically change based on the action taken associated with the container.

[0007] In an aspect, the method can include, responsive to receiving a scan of the machine readable code, causing a web page to be displayed for allowing a user to input data for performing the action. The action can include registering a user and associating the user with the data store entry associated with the machine readable code. The action includes allowing the user to access the information associated with the specific instance of the product.

[0008] In an aspect, the information associated with the specific instance of the product provided via the at least one microservice can include at least one of: product sales data, scientific facts regarding the specific instance of the product, publications associated with the specific instance of the product, account and customer data associated with the specific instance of the product, and web pages associated with the specific instance of the product.

[0009] A computer system and/or a computer readable storage medium storing a program of instructions executable by a machine to perform one or more methods described herein also may be provided. [0010] Further features as well as the structure and operation of various embodiments are described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Fig. 1 illustrates an example apparatus in an embodiment.

[0012] Fig. 2 is a diagram illustrating a system context of a QR code system in an embodiment. [0013] Fig. 3 is a diagram illustrating state transitions in an embodiment.

[0014] Fig. 4 is another diagram illustrating QR code system components in an embodiment. [0015] Fig. 5 illustrates a data model for QR codes in an embodiment.

[0016] Fig. 6 illustrates QR code integration with a plurality of applications in an embodiment. [0017] Fig. 7 illustrates a system overview in an embodiment.

[0018] Fig. 8 is a diagram showing example components of a computer in one embodiment which can perform one or more functions in managing QR codes.

DETAILED DESCRIPTION

[0019] In various embodiments, system, method, apparatus and techniques are provided for a machine readable code, such as a quick response (QR) code or the like. A system, in one or more embodiments, provides a unique QR code for an item or like machine readable code, to be able to monitor that particular item throughout its usage cycle. [0020] Fig. 1 illustrates an example apparatus in an embodiment. A container 102 such as, but not limited to, a vial, is labeled with a machine-readable code 104, for example, a QR code or a matrix barcode image. Throughout the description, QR code is described as an example machine-readable code. However, it should be understood that another like code, for example, with similar functionality or configuration can also be used. The machine-readable code (e.g., QR code) 104 is a unique code for this particular container 102, and is a specific code representing a specific instance of a product contained by the container. The machine-readable code 104 includes a link to information associated with the specific instance of the product. The link can be a uniform resource locator (URL) link. For example, the machine-readable code, responsive to being scanned, is configured to cause a machine that scanned the machine-readable code (or a machine that is coupled or connected to a scanner device) to automatically navigate to a web site page specified by the URL link. By way of example, the machine can be a mobile device 106 running a mobile app, or another computer device. The web site page can be presented automatically, which allows a user to register, enter information, and further allows for keeping track of data associated with the specific instance of the product.

[0021] In an embodiment, the QR code is designed as a serialized code with a web URL. Each vial has a unique code that only belongs to that vial. In an embodiment, once a code has been generated it is not reused again. By way of example, the codes follow the format “http://company.codes/H7GK89N3”, which is a web address that belongs to “company” and maps to a “company” web server, and a string composed of a number of characters, for example, an 8 digit alphanumeric string. The QR code infrastructure built into cell phones or other computer devices, and for example, mobile apps, understands the URL format and offers the user the option to open the address.

[0022] In an embodiment, there is a specific code for each specific instance of each product. In an embodiment, the design of the code allows for codes to cover a number of years of expected product demands. It can be expanded any time to allow more digits - and a far greater namespace. In an embodiment, the length of the string that is encoded drives the size of the code image. The size may be set based on the space on the label. For instance, the shorter the encoded string, the easier the code image may be recognized by a scanner such as a cell phone camera since the pixels can be made larger. An example code (or QR code) can be “C5TR00L5”. That example includes 8 alphanumeric characters, A-Z plus 0-9, providing for unique 2.8 trillion potential QR codes (36*36*36*36*36*36*36*36). A database 208 can store the generated QR codes. In an aspect, the codes can be generated in random order or manner, for instance, to maximize unpredictability and/or security. In an embodiment, the code or QR code can be affixed on any part or surface of the container or vial, and may be scanned from any position.

For example, on a cylindrical vial, a label with the QR code can be wrapped around the cylindrical surface of the vial. The label can be affixed or attached on other parts of the vial.

[0023] Fig. 2 is a diagram illustrating a system context of a QR code system in an embodiment.

In CST Packaging/Fulfillment module 202, users can use an application, e.g., referred to as “Logistics (Discrete Manufacturing)” application, to print labels for product vials that have a QR code printed on them. As part of the printing, the user (e.g., user of the packaging/fulfillment module) may provide information on the product: the product SKU (such as “4060S”) and the lot number (such as “16”, lot number “12”, vial number “3004”). The tracking meta data can also be stored (e.g., print date, fill date, operator name). The tracking code can also be associated with a specific shipment to a specific customer. In an aspect, an automated system may provide such information. This information is stored, e.g., in the “QR Code Data Store” 204 and is from that point kept as a permanent record that the physical vial has the code that is encoded in the QR code image. The QR code also includes a web site address, a URL, which opens a web portal, for example, for allowing users to interact with the system among others. In an embodiment, the length of the URL can be shortened or reduced using a short URL service (e.g., shown at 218).

In an embodiment, an application, e.g., “Logistics (Discrete Manufacturing)” application at 202 can provide an electronic portal to packaging and fulfillment functionalities in the system.

[0024] In an embodiment, the “QR Code Data Store” 204 can be accessed via microservices and caches 206 to provide encapsulation and fast access. In an embodiment, the “QR Code Data Store” 204 has the ability to store additional information, such as the state of the code encoded in the QR code image, and other related information that allows the code to be linked to other entities. [0025] End users 208 may receive vials with products that have the label with the QR code.

They scan the QR code with a device such as a cell phone and/or another device. For example, most cell phones are equipped to recognize that a QR code is part of an image, and automatically decode the image into the code. They recognize that the encoded string is an URL and ask the user whether the website should be accessed. End users 208 also use another device with like applications running on the device for scanning the QR code and invoking the website access.

[0026] For example, responsive to the end users 208 confirming the web access, a web browser 210 (or another application or app) on the phone (or another device) sends a web http request (e.g., http://company.codes/H7GK89N3). The server “company. codes” may run a code, e.g., owned, developed, or maintained by the “company.” The code retrieves the alphanumeric code and looks the code up in the QR Code Datastore 204, e.g., via one or more of the QR code microservices 206. User application or web browser 210 can provide an electronic portal to the system in an embodiment to users.

[0027] In an embodiment, the QR Code Datastore 204 only contains codes that are already associated with a manufactured product vial, and each code has a state in addition to identifying information about who has registered the code, e.g., a customer identification (ID).

[0028] Fig. 3 illustrates the different states and system responses related to “Code States” in an embodiment. The different states, for example, can be stored in the data, associated to the particular container with the code.

[0029] At 302, a new code is requested. For example, a QR code image can be requested for the code to print a label (e.g., shown 202 in Fig. 4, as packaging and/or fulfillment). For instance, a packaging and/or fulfillment component or module of a system can receive such request for the code. A state of “NEW” 304, e.g., which can be represented by “0” and/or another representation or code is entered into the datastore. In an aspect, at this state, the code is not yet mapped to a product container or product vial. In an aspect, if a code is scanned by a user and the scanned code has this state, it is treated like an invalid code. The system, e.g., in response to receiving the request for a new code, generates a new code and stores it in the datastore, for example, a database, and returns the generated code to the requester or requesting application. The system also can generate a code image such as the QR code image.

[0030] At 306, the code is associated with a container, e.g., a vial. The status of the code is set to “ASSOCIATED” and/or “1” (or another representation) 308, which indicates that the code is associated with a specific, physical container or vial with a product. This is now a valid code and the system expects as a next step that a user or customer scans the code. As part of this information the product (SKU, Lot) in the vial is recorded. This can be done via a call to an API that makes the update. The system updates the data portion from the code with the supplied information.

[0031] At 310, a user or customer scans the code (e.g., QR code). For example, a user (e.g., customer) has interacted with the QR code, e.g., by scanning it or typing the code string into the system’s QR code registration page. The update is made in the database when QR code web page (e.g., mobile web page) makes a call to the appropriate API. In an aspect, in response to the user scanning a code that does not exist in the datastore, or is invalid, the user is prompted for information so that a service such as a customer service can follow up to help with anomalies in the label such as smudges, incorrect or possibly counterfeited codes. For instance, a user scanning a code, which does not exist in the datastore can indicate that the product in the container or vial the user is scanning is not an authentic product.

[0032] In an embodiment, when the user scans a well formed, valid code, the following actions are taken, per the state of the code in the datastore. The user is prompted to provide authentication information and other information about any intended use. For example, when the user scans such as code the user is prompted to identify himself/herself to the system. In an embodiment, for web browser based access the usual SSO login mechanisms can be used to identify the user. Other login or authentication method can be implemented. Upon successful login the user ID is associated with the QR Code in the datastore, and the code state is set to “SCANNED” and/or “3” (or another representation) 312. [0033] While the state is in “SCANNED” mode, the QR code system proceeds to ask the user for additional information, such as information on their institution or workplace. This information is stored in the datastore.

[0034] At 314, the user completes registration. For example, a customer has successfully completed registration as a user for the scanned vial. The update is made in the database when the QR code web page (e.g., mobile web page) makes a call to the appropriate API. The customer may be presented with a registration confirmation and is given access to information to enable success with the new product.

[0035] Upon full registration the state is set to “REGISTERED” and/or “4” (or another representation) 316. In an embodiment, there can be two states (“SCANNED”) and (“REGISTERED”) to capture as much information as possible, even if the user does not choose to fully complete the product registration.

[0036] In the “REGISTERED”, e.g., responsive to a scan, the user can be prompted to log in (or may be logged in from a previous use) and the login information is matched with the login information of the code in the datastore. If the IDs match, the user is given access to proceed in the context of the scanned product vial. In an embodiment, the location and domain of the user may be read from the browser origin information and stored in the database. In an embodiment, maintaining states and information associated with the product or vial can allow for detecting possible counterfeit or grey market goods. For instance, if a location of an authenticated product or container is last logged as being at one location, and the system receives a scan of a product with the same code, but from a different location (e.g., within a threshold of time), the system may infer that a counterfeit or grey market good is being scanned in.

[0037] At 318, if another individual attempts to register the same code, an error is flagged and the state may transition to “REGISTERED_CONFLICT” and/or “5” (or another representation) 320. For example, if a first user scans the code and registers, and a subsequent registration attempt is made by another user, for example, a user with a different ID and/or a different location (e.g., country, state or province), the state is set to REGISTERED_CONFLICT. For instance, a second scanning is performed on the same code and the system is unable to map it to the already registered customer. The update is made when, e.g., the mobile QR code web page calls the scan API. Information on all users is stored in the datastore and customer service can use this information to follow up with customers to investigate scanning errors, or possibly counterfeited products. For example, the second user is prompted to call a customer support. An alert via e-mail can be generated in the system to allow follow-up.

[0038] Additional states can be implemented, for example, for full providence and/or manufacturing of the product, and/or others.

[0039] A benefit of the QR code is that it allows the end user to get information for exactly their product, while sources of human error are largely eliminated. There can be products such as antibody products, which are “analog” products. New lots of products are produced all the time and different lots may have differences in behavior. Since the QR codes are linked to specific vials and lots, the customer can be presented with lot specific information. Since the information is accessed via scanning, human errors like input errors are reduced. The QR code system can provide resources and technical support, for example, such as but not limited to, tracking, shipping information, product authentication or verification, product information, protocol information, technical tips, information to run experiments, setting up experiments, new product and application information, tailored product, kit and lists, promotional trials, feedbacks, and tailored promotions, to help customers with specific information, specifically geared to the particular instance of the product the customer has. For instance, a customer can readily access product information such critical information by application lot-specific information, protocols, technical tips, scientific resources, product authenticity, promotions and more.

[0040] Authentication component or module 216 provides user identification validation or authentication processing, for instance, for user logins. In an embodiment, a user login page or web page may automatically open responsive to a user scanning a QR code on a vial. In an aspect, the authentication component or module 216 may utilize or interface with external services in authenticating the user. [0041] Referring back to Fig. 2, Graph/Marketing Specialist 212 include business users who may use the information in the QR code system in context with other information. In an embodiment, a “Graph / Data Analytics Platform” 214 is a system that allows the real time linking of data across many data sources at large scale. In an embodiment, as an underlying technology it 214 uses a data lake with uniform, microservices based data access, and a graph database. In an embodiment, the “Graph / Data Analytics Platform” 214 may interface with one or more external or third party vendor services for providing analysis.

[0042] In an embodiment, the information available in this platform includes, but is not limited to: product sales data; Scientific facts, e.g., related to the product, e.g., scientific facts of antibodies, including biological interactions; Publications, with authors; Publically available competitor product data; account and customer data; Web visits to any page on any system web property. User entered data can also be accessed (e.g., freezer number and rack number where the vial has been stored in the laboratory).

[0043] Once the QR code scanning is also made available to be linked with all of these data sources, at least the following use cases become possible:

1. Users scan and register their product, while providing information on what they do with the product. This allows a real time understanding of what customers of the product actually do.

2. Customers visit QR code web pages alongside other company web pages. Via the use of visitor tracking (e.g., given the user permission) this converts anonymous visits across web properties to visits by identified users.

3. In indirect markets a company often may not have information on the users who use the product. Products are sold through channels and the channel partners have the account and/or end customer information. The QR code enables a direct interaction between the company and the customer. The graph can associate scanned product vials with supply chains, shipments, and orders.

4. Even in direct markets a company may often lack that information as products are bought via procurement employees who are different from the scientists who use the product. With the graph scanned vials can be associated with institutions, accounts, intended use, and possibly publications.

5. Many different statistics can be captured and used for the creation of marketing and other campaigns: product registrations and uses in different markets and regions, different degrees of registrations, different degrees of conflicting registrations - indicating fraudulent behaviors in different regions, and many more.

[0044] Fig. 4 is a diagram illustrating QR code system components in an embodiment. The figure illustrates the software architecture of the system in an embodiment. The components shown at 402 box are associated with the web side of the system; the components shown at 404 box are associated with the backend, e.g., logistics or lab systems.

[0045] In an embodiment, the architecture includes micro services that provide representational state transfer application programming interfaces (REST APIs) to access data and/or to modify the system state. In an embodiment, the data is stored in NoSQL databases. In an embodiment, the data, which may already be available in systems (e.g., a company’s product development platform), can be loaded into the NoSQL databases or other types of databases for fast access and encapsulation. In an embodiment, a cloud-based platform can be implemented for provide web services. In an embodiment, services written in Python or JavaScript can be deployed to implement the microservices.

[0046] By way of example, a computer node (e.g., computer container) at 406 can store databases. For example, there can be a citations data store, protocols data store, lot information data store, product information data store, user information data store, and product registration data store. Another computer node at 408 can include or perform microservices such as product code management service and QR code label printing service, and/or others. The QR code label printing service, e.g., can interact with a manufacturing application component (e.g., on yet another computer node 410) which allows for printing of the labels (e.g., described above with reference to 202 in Fig. 2). The product code management service can interact with the product registration data store. [0047] The web side of the system 402 can provide services, for example, via microservices implementation, such as citations data service, protocols data service, lot information data service, product information data service, user information data service, product registration service, and/or others. A computer node at 412, for example, can provide such web microservices, e.g., interacting with a computer node at 414 (which can represent a user device or computer accessing the services via a web browser or another client application). The web side of the system 402 can include web infrastructure to support short URLs 416 and serve web content 418.

[0048] Fig. 5 illustrates a data model for QR codes in an embodiment. The data model is shown as an example. Other data models can be implemented. A Product 502 may be filled from one or more different Lots 504. A Product 502 represents a company’s product, e.g., as identified by the product SKU. A Lot 504 represents a lot from which a vial (or physical container) is filled. The vial can be identified by a combination of product SKU and lot number. For example, a Vial 512 can be identified by label on the vial that has the QR code generated by the system and can be stored in the database.

[0049] A Protocol 506 is Lot specific. A Protocol 506 can represent a company approved protocol, and may come from protocols.io. The same Product may have multiple Protocols.

Each product application 514 may have one or more protocols associated with it. In an embodiment, the combination of a product/lot and intended application determines the protocol to be used.

[0050] A Customer record in the QR Code system can be made “very thin”, e.g., it is sufficient to store some ID or token that can be combined with additional information (such as e-mail addresses) that are stored outside of the QR code system. Such implementation can comply with privacy standards. A Customer 508 can have an account 510 on the company’s web site. The account information may store order history and preferred protocols for the customers. [0051] The Vial 512 can be associated with an Order 516. Order 516 is associated with an Account 518. The Account 518 can be associated with an Organization 520. The Customer 508 can be associated with the Organization 520.

[0052] Fig. 6 illustrates QR code integration with a plurality of applications in an embodiment. QR Code Mobile Pages component 602 can enable single sign-on (SSO) capability across QR code pages and web pages. This component may rely on QR code images 604, for example, received via a scan, to identify and open the appropriate web site, and also a SSO service 606 for web pages. The SSO service 606 may connect to a component providing user profile services 608, which may leverage an existing third party service 610, for example, for authenticating and managing user services, e.g., for web applications.

[0053] MyAccount Pages component 612 may provide for a continuous experience across mobile and desktop/laptop (or another device). This component may also utilize or interface with an existing third party service 610, which can provide user authentication, authorization, data synchronization and access, for example, for web and/or mobile applications.

[0054] QR Code Label Printing component 614 may provide functionality that enables printing of labels with QR codes. This component may interface with ePortal Application Refactoring for label printing 616, which can interface with a database or database infrastructure 618, which stored QR code information.

[0055] QR Code Info Pages component 620 may provide data required for QR code pages. The data, for example, can be retrieved from data sources 622, e.g., in laboratory systems for protocols and/or lots.

[0056] QR Code Tracker Service 624 may provide a service with one or more databases to track codes, the state of the codes, and related information. Such information can be retrieved from Document DB Infrastructure. For example, the component 624 may interface with the database infrastructure 618, in providing its functionality. [0057] Fig. 7 illustrates a system overview in an embodiment. An electronic portal (ePortal) 702 can be an application or web application, which can provide access to system services such as printing services 704. Order, shipping and inventory services 706 can also be provided via the ePortal 702. Also via the ePortal 702, a user can perform QR code management, for example, using QR Code Management component 708, which can perform management functions and access the QR code related datastores.

[0058] Web Ecommerce QR Code Mobile Pages component 710 can provide QR code related services to a customer user 712, for example, via interfacing with the QR Code Management component 708 and/or the Order, shipping and inventory services 706. For example, the customer user 712 can scan a vial (with QR code), view product information associated with the vial, view lot information associated with the vial, view use information associated with the vial, and gain access to links to other information or sites providing information associated with the product.

[0059] The components shown above in computer architecture and computer system diagrams include computer-implemented components, for instance, implemented and/or run on one or more hardware processors, or coupled with one or more hardware processors. One or more hardware processors, for example, may include components such as programmable logic devices, microcontrollers, memory devices, and/or other hardware components, which may be configured to perform respective tasks described in the present disclosure. Coupled memory devices may be configured to selectively store instructions executable by one or more hardware processors.

[0060] A processor may be a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), another suitable processing component or device, or one or more combinations thereof. The processor may be coupled with a memory device. The memory device may include random access memory (RAM), read-only memory (ROM) or another memory device, and may store data and/or processor instructions for implementing various functionalities associated with the methods and/or systems described herein. The processor may execute computer instructions stored in the memory or received from another computer device or medium. [0061] Fig. 8 is a diagram showing example components of a computer in one embodiment which can perform one or more functions for managing QR codes, for example, described above. One or more hardware processors 802 such as a central processing unit (CPU), a graphic process unit (GPU), and/or a Field Programmable Gate Array (FPGA), an application specific integrated circuit (ASIC), and/or another processor, may be coupled with a memory device 804, and provide functionalities described here. A memory device 804 may include random access memory (RAM), read-only memory (ROM) or another memory device, and may store data and/or processor instructions for implementing various functionalities associated with the methods and/or systems described herein. One or more processors 802 may execute computer instructions stored in memory 804 or received from another computer device or medium. A memory device 804 may, for example, store instructions and/or data for functioning of one or more hardware processors 802, and may include an operating system and other program of instructions and/or data. In one aspect, data can be stored in a storage device 806 or received via a network interface 808 from a remote device, and may be temporarily loaded into a memory device 804 for processing. One or more hardware processors 802 may be coupled with interface devices such as a network interface 808 for communicating with remote systems, for example, via a network, and an input/output interface 810 for communicating with input and/or output devices such as a keyboard, mouse, display, and/or others. The system can include other hardware and software components not shown in the figure. One or more methods or techniques described herein may be implemented using computer languages such as JAVA, and JavaScript, but not limited to those languages. In one aspect, the functionalities and modules of the system and methods of the present disclosure may be implemented or carried out in distributed manner on different processing systems or on any single platform, for instance, accessing data stored locally or in distributed manner on a computer network. A cloud-based computing environment can also be utilized.

[0062] Various aspects of the present disclosure may be embodied as a program, software, or computer instructions embodied or stored in a computer or machine usable, readable or executable medium, which causes the computer or machine to perform the steps of the method when executed on the computer, processor, and/or machine. For instance, a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform various functionalities and methods described in the present disclosure may be provided.

[0063] The system and method of the present disclosure may be implemented and run on a general-purpose computer or special-purpose computer system (or device). The computer system may be any type of known or will be known systems and may include a hardware processor, memory device, a storage device, input/output devices, internal buses, and/or a communications interface for communicating with other computer systems in conjunction with communication hardware and software, etc. Some of the techniques described herein may also be implemented and/or run on a mobile device or the like.

[0064] In one or more embodiments, the present invention may be embodied as a computer program product that may include a computer readable storage medium (or media) and/or a computer readable storage device. Such computer readable storage medium or device may store computer readable program instructions for causing a processor to carry out one or more methodologies described here. In one embodiment, the computer readable storage medium or device includes a tangible device that can retain and store instructions for use by an instruction execution device. Examples of the computer readable storage medium or device may include, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof, for example, such as a 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), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, but not limited to only those examples.

[0065] The terms “computer system” as may be used in the present application may include a variety of combinations of fixed and/or portable computer hardware, software, peripherals, mobile, and storage devices. The computer system may include a plurality of individual components that are networked or otherwise linked to perform collaboratively, or may include one or more stand-alone components. The hardware and software components of the computer system of the present application may include and may be included within fixed and portable devices such as desktop, laptop, and/or server. A module may be a component of a device, software, program, or system that implements some “functionality”, which can be embodied as software, hardware, firmware, electronic circuitry, or etc.

[0066] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the term “or” is an inclusive operator and can mean “and/or”, unless the context explicitly or clearly indicates otherwise. It will be further understood that the terms "comprise", "comprises", "comprising", "include", "includes", "including", and/or "having," when used herein, can specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the phrase “in an embodiment” does not necessarily refer to the same embodiment, although it may. As used herein, the phrase “in one embodiment” (or “in an embodiment” or like) does not necessarily refer to the same embodiment, although it may. As used herein, the phrase “in another embodiment” (or “in an embodiment” or like) does not necessarily refer to a different embodiment, although it may. Further, embodiments and/or components of embodiments can be freely combined with each other unless they are mutually exclusive.

[0067] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements, if any, in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.