Claims:CLAIMS
We claim:
1. A system for determining change in weight of items, the system comprising:
at least two platforms (102A-N), each of the platforms (102A-N) configured to receive one or more containers (104A-N) comprising a machine-readable member, each of the platforms (102A-N) comprising:
a load cell (202) configured to determine a total load on the platform; and
a near-field reader (204) configured to read the machine-readable member associated with the one or more containers (104A-N) placed on the platform; and
a controller (110) communicatively coupled with the at least two platforms (102A-N), the controller (110) configured to:
receive information corresponding to the load from each of the platforms (102A-N);
receive information corresponding to the machine-readable members from each of the platforms (102A-N);
identify containers, and thereby corresponding items, present on each of the platforms (102A-N); and
determine change in weight of the one or more containers (104A-N), and thereby the corresponding items, based on the load information from each of the platforms (102A-N) and the containers identified to be present on each of the platforms (102A-N).
2. The system of claim 1, wherein the near-field reader is an RFID reader and the machine-readable members are RFID tags.
3. The system of claim 1, further comprising an electronic device (114), which is associated with a user (116), communicatively coupled with the controller (110), wherein the controller (110) is equipped to:
receive, from the electronic device (114), information correlating an item with each of the machine-readable members, and thereby the respective containers; and
receive, from the electronic device (114), information about the weight of the containers (104A-N) or at least information that enables determination of weight of each of the containers (104A-N).
4. The system of claim 3, wherein,
the controller (110) is configured to communicate, to the electronic device (114), a human readable code associated with the machine-readable code recognized by at least one of the platforms (102A-N);
the electronic device (114) is configured to enable selection of an item for correlation with the human readable code, and thereby the machine-readable code, and communicate the selection to the controller (110); and
the controller (110) is configured to maintain the correlation between the item and the respective machine-readable code.
5. The system of claim 1, wherein a controller (110) is configured to:
receive from a first platform (102a) among the two platforms, information indicating absence of a machine-readable member, which was previously present on the first platform (102a);
receive from the first platform (102a), information indicating load on the first platform (102a), immediately after identifying absence of the machine-readable member from the first platform (102a);
determine change in load on the first platform (102a);
receive from a second platform (102b) among the two platforms, information indicating introduction of the machine-readable member, which was previously absent on the second platform (102b);
receive from the second platform (102b), information indicating load on the second platform (102b), immediately after identifying introduction of the machine-readable member on the second platform (102b);
determine change in load on the second platform (102b); and
determine change in weight of the item corresponding to introduced machine-readable member based on the change in load on the first platform (102a) and the second platform (102b).
6. The system of claim 1, further comprising an electronic device (114) communicatively coupled with the controller (110), wherein the controller (110) communicates information indicating change in weight of one or more of the items to the electronic device (114).
7. The system of claim 1, wherein the controller (110) is configured to initiate a digital notification when weight of an item, among the items, based on a threshold or range of threshold.
8. The system of claim 1, further comprising a hub (106), wherein,
the hub (106) is an intermediary between the platforms (102A-N) and the controller (110);
the platforms (102A-N) communicate with the hub (106); and
the hub (106) wirelessly communicates with the controller (110), wherein the controller (110) is remotely located from the platforms (102A-N) and the hub (106).
9. The system of claim 1, wherein the hub (106) communicates with the platforms (102A-N) using local area network.
10. The system of claim 1, wherein the controller (110) is further configured to:
receive information relating to signal strength corresponding to the machine-readable members from each of the platforms (102A-N); and
detect a platform, among the platforms (102A-N), on which one of the machine-readable members is present, based on the signal strength, wherein information corresponding to detection of said machine-readable member is received from at least two platforms (102A-N).
11. The system of claim 1, wherein the controller (110) is further configured to:
receive a selection of an item from an electronic device (114);
communicate instruction to a platform among the platforms (102A-N) to generate an alert, based on which among the platforms (102A-N) is carrying the item.
12. A method for determining change in weight of items, the method comprising:
providing at least two platforms (102A-N) for receiving one or more containers (104A-N) comprising a machine-readable member;
receiving information corresponding to load from each of the platforms (102A-N);
receiving information corresponding to the machine-readable members from each of the platforms (102A-N);
identifying containers (104A-N), and thereby corresponding items, present on each of the platforms (102A-N) based on the information corresponding to the machine-readable members from each of the platforms (102A-N); and
determining change in weight of the one or more containers (104A-N), and thereby the corresponding items, based on the load information from each of the platforms (102A-N) and the containers (104A-N) identified to be present on each of the platforms (102A-N).
13. The method of claim 11, further comprising:
receiving, from a first platform (102a) among the at least two platforms, information indicating absence of a machine-readable member, which was previously present on the first platform (102a);
receiving, from the first platform (102a), information indicating load on the first platform (102a), immediately after identifying absence of the machine-readable member from the first platform (102a);
determining change in load on the first platform (102a);
receiving, from a second platform (102b) among the at least two platforms, information indicating introduction of the machine-readable member, which was previously absent on the second platform (102b);
receiving, from the second platform (102b), information indicating load on the second platform (102b), immediately after identifying introduction of the machine-readable member on the second platform (102b);
determining change in load on the second platform (102b); and
determining change in weight of the item corresponding to the introduced machine-readable member based on the change in load on the first platform (102a) and the second platform (102b).
Dated, this 27th day of November 2018
(Digitally signed)
Kartik PUTTAIAH
Patent Agent-IN/PA-1809
, Description:BACKGROUND
Field of invention:
[001] The subject matter in general relates to the field of platforms equipped with load cells. More particularly, but not exclusively, the subject matter relates to network of platforms equipped with load cells and near field readers.
Discussion of related art:
[002] Inventory management has become increasingly popular over the years. For example, inventory management may be applied for kitchen or household items. Kitchens may typically include storage areas for storing products/goods, including, but not limited to rice, wheat, fruits, vegetables, flour, milk, and the like. The products/goods may be kept on shelves within the storage area of the kitchen.
[003] Conventional kitchen inventory systems have been proposed that manage products/goods stored within the kitchen or a warehouse. However, due to an ample number of products/goods stored in the kitchen or warehouse, it becomes difficult to track the quantum of each product/good. There may be instances that a product/good is misplaced or not kept at its proper location, there are shortages of products/goods, and the like. Conventional kitchen inventory systems may not be able to intimate the product/good conditions to users at regular intervals. Therefore, users will not be able to receive constant updates.
[004] Thus, the conventional systems failed to solve the above problems resulting in inconsistent inventory monitoring of products/goods in the kitchens or warehouses, which may not be desirable.
[005] In view of the foregoing discussion, there is a need to overcome the above problems.
SUMMARY
[006] Accordingly, an improved technique to overcome the above problems is needed. To fulfill this need, a system and method for determining change in weight of items is disclosed.
[007] In one embodiment, a system for determining change in weight of items is disclosed. The system comprises at least two platforms that are configured to receive one or more containers comprising a machine-readable member. Each of the platforms comprise a load cell and a near-field reader. The load cell may be configured to determine a total load on the platform. The near-field reader may be configured to read the machine-readable member associated with the one or more containers placed on the platform. The system further comprises a controller communicatively coupled with the at least two platforms. The controller may be configured to receive information corresponding to the load from each of the platforms. The controller may be further configured to receive information corresponding to the machine-readable members from each of the platforms. The controller may be further configured for identifying containers, and thereby corresponding items, present on each of the platforms. In addition, the controller may be configured to determine a change in weight of the one or more containers, and thereby the corresponding items, based on the load information from each of the platforms and the containers identified to be present on each of the platforms.
[008] In another embodiment, a method for determining change in weight of items is disclosed. The method comprises providing at least two platforms, wherein each of the platforms receive one or more containers comprising a machine-readable member. The method further comprises receiving information corresponding to the load from each of the platforms. The method further comprises receiving information corresponding to the machine-readable members from each of the platforms. The method further comprises identifying containers, and thereby corresponding items present on each of the platforms. In addition, the method comprises determining change in weight of the one or more containers, and thereby the corresponding items, based on the load information from each of the platforms and the containers identified to be present on each of the platforms.
[009] Other objects, features, and advantages of the present invention will become apparent from the following detailed description. It should be however understood that the detailed description and specific examples, while indicating preferred embodiments of the present invention, are given by way of illustration only and various modifications may naturally be performed without deviating from the present invention.
BRIEF DESCRIPTION OF DIAGRAMS
[010] This disclosure is illustrated by way of example and not limitation in the accompanying figures. Elements illustrated in the figures are not necessarily drawn to scale, in which like references indicate similar elements and in which:
[011] FIG. 1 is an exemplary architecture of a system 100 for determining change in weight of items, in accordance with an embodiment;
[012] FIG. 2 is an exemplary system architecture of a platform 102, in accordance with an embodiment;
[013] FIG. 3 illustrates an exemplary system architecture of the controller 110, in accordance with an embodiment;
[014] FIG. 4 illustrates an exemplary method 400 illustrating a flowchart for correlating an RFID tag with an item present in the one or more containers 104A-N, in accordance with an embodiment;
[015] FIG. 5 illustrates an exemplary method 500 illustrating a flowchart for determining change in weight of an item present in one or more containers 104A-N, in accordance with an embodiment;
[016] FIG. 6A is an exemplary diagram 600 illustrating machine-readable members placed on the first platform 102a among the at least two platforms and the second platform 102b among the at least two platforms, in accordance with an embodiment;
[017] FIG. 6B is an exemplary diagram 600 illustrating an absence of the machine-readable member on the first platform 102a, in accordance with an embodiment;
[018] FIG. 6C is an exemplary diagram 600 illustrating an introduction of the machine-readable member, which was previously absent on the second platform 102b, in accordance with an embodiment;
[019] FIG. 7 is an exemplary diagram 700 illustrating a possible detection of a container 104 by multiple platforms 102, in accordance with an embodiment;
[020] FIG. 8 illustrates an exemplary method 800 illustrating a flowchart for determining a correct platform 102 on which a container 104 is placed based on signal strength information, in accordance with an embodiment; and
[021] FIG. 9 illustrates an exemplary method 900 illustrating a flowchart for determining a correct platform 102 on which a container 104 is placed based on missing information, in accordance with an embodiment.
DETAILED DESCRIPTION OF THE INVENTION
[022] The following detailed description includes references to the accompanying drawings, which form part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments are described in enough details to enable those skilled in the art to practice the present subject matter. However, it will be apparent to one of ordinary skill in the art that the present invention may be practised without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to unnecessarily obscure aspects of the embodiments. The embodiments can be combined, other embodiments can be utilized or structural and logical changes can be made without departing from the scope of the invention. The following detailed description is, therefore, not to be taken as a limiting sense.
[023] In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a non-exclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.
[024] It should be understood that the capabilities of the invention described in the present disclosure and elements shown in the figures may be implemented in various forms of hardware, firmware, software, non-transitory computer readable medium or combinations thereof.
[025] FIG. 1 is an exemplary architecture of a system 100 for determining change in weight of items, in accordance with an embodiment. As shown, the system 100 may include one or more platforms 102A-N, one or more containers 104A-N, a hub 106, a first network 108, a controller 110, a second network 112, an electronic device 114, and a user 116 associated with the electronic device 114. Each component is described in further detail below.
[026] In one embodiment, the one or more platforms 102A-N (may be referred to as “platform 102” individually) are configured to receive one or more containers 104A-N (may be referred to as “container 104” individually) comprising a machine-readable member. The one or more containers 104A-N may store products/goods including, but not limited to, rice, wheat, fruits, vegetables, flour, and the like. The hub 106 may be an intermediary between the one or more platforms 102A-N and the controller 110. The one or more platforms 102A-N may communicate with the hub 106. The hub 106 may communicate with the controller 110, wired or wirelessly, via the first network 108. The hub 106 may also communicate with the one or more platforms 102A-N using a local area network (LAN).
[027] In one embodiment, the controller 110 may be communicatively coupled to the at least two platforms 102A-N. The electronic device 114 is communicatively coupled with the controller 110, via the second network 112. The electronic device 114 may include, but not be limited to, a mobile, a smartphone, a tablet, a laptop, a computer, a personal digital assistant (PDA), and the like.
[028] The first network 108 and the second network 112 may be a wired network, a wireless network or a combination thereof. Furthermore, the first network 108 and the second network 112 may include a wide area network (WAN) (e.g., the Internet), or other interconnected data paths across which multiple devices and/or entities may communicate. In some implementations, the first network 108 and the second network 112 may include a peer-to-peer network. The first network 108 and the second network 112 may also include a mobile data network that may include third-generation (3G), fourth-generation (4G), long-term evolution (LTE), long-term evolution advanced (LTE-A), Voice-over-LTE (“VoLTE”) or any other mobile data network or combination of mobile data networks.
[029] FIG. 2 is an exemplary system architecture of a platform 102, in accordance with an embodiment. As shown, the platform 102 includes a load cell 202, a near field reader 204 (such as an RFID reader), a processor 206, a memory 208, a communication unit 210, a U/I 212, and a bus 214. Each component is described in further detail below.
[030] In one embodiment, the load cell 202 is configured to determine a total load on the platform 102.
[031] The near-field reader 204 is configured to read the machine-readable member associated with the one or more containers placed on the platform 102. The near-field reader 204 may be a radio-frequency identification (RFID) reader and the machine-readable members may be RFID tags.
[032] In general, the processor 206 may include any suitable special-purpose or general-purpose computer, computing entity, or processing device including various computer hardware or software modules and may be configured to execute instructions stored on any applicable computer-readable storage media. For example, the processor 206 may include a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or any other digital or analog circuitry configured to interpret and/or to execute program instructions and/or to process data.
[033] The memory 208 may include computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable storage media may be any available media that may be accessed by a general-purpose or special-purpose computer, such as the processor 206. By way of example, and not limitation, such computer-readable storage media may include tangible or non-transitory computer-readable storage media including Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory devices (e.g., solid state memory devices), or any other storage medium which may be used to carry or store desired program code in the form of computer-executable instructions or data structures and which may be accessed by a general-purpose or special-purpose computer.
[034] The communication unit 210 may be a wired network or a wireless network. Furthermore, the communication unit 210 may include a local area network (LAN), a wide area network (WAN) (e.g., the Internet), or other interconnected data paths across which multiple devices and/or entities may communicate.
[035] The U/I (user interface) 212 may provide an interaction mechanism between a user and the platform 102.
[036] The load cell 202, the near field reader 204, the processor 206, the memory 208, the communication unit 210, and the U/I 212 may all be interconnected via the bus 214. The bus 214 may be a communication system that transfers data/information between each component.
[037] FIG. 3 illustrates an exemplary system architecture of the controller 110, in accordance with an embodiment. As shown, the system 300 may include a processor 302, a memory 304, a communication unit 306, an I/O 308, and a bus 310. Each component is described in further detail below.
[038] In general, the processor 302 may include any suitable special-purpose or general-purpose computer, computing entity, or processing device including various computer hardware or software modules and may be configured to execute instructions stored on any applicable computer-readable storage media. For example, the processor 302 may include a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or any other digital or analog circuitry configured to interpret and/or to execute program instructions and/or to process data.
[039] The memory 304 may include computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable storage media may be any available media that may be accessed by a general-purpose or special-purpose computer, such as the processor 302. By way of example, and not limitation, such computer-readable storage media may include tangible or non-transitory computer-readable storage media including Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory devices (e.g., solid state memory devices), or any other storage medium which may be used to carry or store desired program code in the form of computer-executable instructions or data structures and which may be accessed by a general-purpose or special-purpose computer.
[040] The communication unit 306 may be a wired network or a wireless network. Furthermore, the communication unit 306 may include a local area network (LAN), a wide area network (WAN) (e.g., the Internet), or other interconnected data paths across which multiple devices and/or entities may communicate.
[041] The I/O (input/output) 308 may provide communication between the processor 302, the memory 304, and the communication unit 306. The processor 302, the memory 304, the communication unit 306, and the I/O 308 may all be interconnected via the bus 310.
[042] The bus 310 may be a communication system that transfers data/information between each component. The system architecture of the hub 106 may be like the system architecture of the controller 110, as described above.
[043] FIG. 4 illustrates an exemplary method 400 illustrating a flowchart for correlating an RFID tag with an item present in the one or more containers 104A-N, in accordance with an embodiment. Notably, the RFID tag may be affixed to a container 104, which may accommodate the item that is correlated. Steps 402 – 412 may be executed by the controller 110, in coordination with the platform 102, the hub 106 and the electronic device 116. Each step is explained in further detail below.
[044] At step 402, the controller 110 may be configured to receive information corresponding to the load determined by the load cell 202 of the platform 102. The information may be communicated by the communication unit 210 of the platform 102 to the hub 106, which may in turn communicate the information to the controller 110. The load on the platform 102 may be resulting from one or more container 104 placed on the platform 102.
[045] At step 404, the controller 110 receives information corresponding to one or more machine-readable members from the platform 102. The machine-readable member may be an RFID tag associated/affixed to container 104 placed on the platform 102. Each container 104 may have individual machine-readable member associated/affixed to it. The near field reader 204 of the platform 102 recognizes the machine-readable member(s) disposed on the platform 102. The information obtained from the recognized machine-readable member(s) may be communicated by the communication unit 210 of the platform 102 to the hub 106, which may in turn communicate the information to the controller 110. The recognition of the machine-readable member(s) by the platform 102 may be resulting from one or more container 104, with machine readable member(s) affixed therein, placed on the platform 102.
[046] At step 406, the controller 110 may be configured to check whether each of the machine-readable member(s), from the previous step, correlate with an item. As an example, the controller 110 may receive information from the platform 102 corresponding to a couple of machine readable members. The controller 110 verifies whether each one of the machine-readable members are associated with an item or not.
[047] In case the assessment at step 406 is positive, then at step 408, the controller 110 may maintain the correlation between the item and the respective machine-readable member/code or check for/enable change in correlation. As an example, one among the couple of machine readable members, from the above example, may be correlated with an item (e.g., rice), whereas another machine-readable member may not be correlated with any item. In such a scenario, the controller 110 may maintain the correlation between the item and the respective machine-readable member/code or check for/enable change in correlation, for the machine-readable member for which correlation exists.
[048] In case the assessment at step 406 is negative, then at step 410, the controller 110 may send a notification to the electronic device 114 and enable correlation between the machine-readable member and an item of user’s choice. Referring to the previous example, the machine-readable member for which correlation was absent is picked up for correlation in step 410. In an embodiment, the controller 110 may include a database mapping code derived from reading the machine-readable members to human readable codes. The controller 110, on determining absence of correlation corresponding to a machine-readable code, may communicate associated human readable code (which is also displayed on the machine-readable code) to the electronic device 114, thereby enabling a user to refer to the container 104 comprising the machine-readable member, with human readable code displayed therein, and select an item for association accordingly.
[049] In an embodiment, the controller 110 receives, from the electronic device 114, information about the weight of the container 104 or at least information that enables determination of weight of each of the containers 104. It may be noted that, this information may be important to determine the weight of the item, which is or may be placed in the container 104.
[050] At step 412, the controller 110 may receive the selection of the item, from the electronic device 114, to be correlated with the machine-readable member, and correlates accordingly. The correlation between machine readable members and items may be maintained in a database by the controller 110.
[051] FIG. 5 illustrates an exemplary method 500 illustrating a flowchart for determining change in weight of an item present in one or more containers 104A-N, in accordance with an embodiment. Step 502 and step 504 may be executed by a first platform 104a among the one or more platforms 102A-N, step 506 and step 508 may be executed by the executed by a second platform 104b among the one or more platforms 102A-N, and steps 503, 505, 507, 509 and 510 – 516 may be executed by the controller 110. Each step is explained in further detail below.
[052] At step 502, the first platform 104a communicates information that indicates an absence of a previously present (on the first platform 104a) machine-readable member. Each container 104 of the first platform 104a may have individual machine-readable member associated/affixed to it. The near field reader 204 of the first platform 104a recognizes the absence of the machine-readable member previously disposed on the first platform 104a. This absence information obtained may be communicated by the communication unit 210 of the first platform 104a to the hub 106, which may in turn communicate the information to the controller 110. In an embodiment, as soon as the near field reader 204 of the first platform 104a senses that a machine-readable member, which was within its purview, is no more within its purview, may send information about such machine-readable member to the controller 110. On the other hand, in such a scenario, the first platform 104a may send information about the machine-readable member(s), which are still under its purview, wherein such information can be used by the controller 110 to determine which machine-readable member, and therefore the container, and therefore the item, has been taken off the first platform 104a. The information communicated by the first platform 104a is received and recorded by the controller 110, at step 503.
[053] At step 504, the load on the first platform 104a is immediately determined after identifying the absence of the machine-readable member. The load cell 202 of the first platform 104a determines the load. The load determined may be communicated by the communication unit 210 of the first platform 104a to the hub 106, which may in turn communicate the information to the controller 110. In an embodiment, the first platform 104a may communicate load information whenever there is change in load on the first platform 104a. The information communicated by the first platform 104a is received and recorded by the controller 110, at step 505.
[054] At step 506, the second platform 104b communicates information that indicates the introduction of the machine-readable member. The near field reader 204 of the second platform 104b recognizes the introduction of the machine-readable member, which previously disposed on (and then taken off) the first platform 104a, which is now disposed on the second platform 104b. This introduction information obtained may be communicated by the communication unit 210 of the second platform 104b to the hub 106, which may in turn communicate the introduction information to the controller 110. In an embodiment, as soon as the near field reader 204 of the second platform 104b senses that a machine-readable member, which was not within its purview, is now within its purview, may send information about such machine-readable member to the controller 110. On the other hand, in such a scenario, the second platform 104b may send information about the machine-readable member(s), which are under its purview, wherein such information can be used by the controller 110 to determine which machine-readable member, and therefore the container, and therefore the item, has been introduced on the second platform 104b. The information communicated by the second platform 104b is received and recorded by the controller 110, at step 507.
[055] At step 508, the load on the second platform 104b is determined after identifying the introduction of the machine-readable member. The load cell 202 of the second platform 104b determines the load. The load determined may be communicated by the communication unit 210 of the second platform 104b to the hub 106, which may in turn communicate the information to the controller 110. In an embodiment, the second platform 104b may communicate load information whenever there is change in load on the second platform 104b. The information communicated by the second platform 104b is received and recorded by the controller 110, at step 509.
[056] At step 510, the controller 110 may be configured to determine change in load on the first platform 104a, based on previously recorded load and the load being reported in step 503. In an embodiment, the controller 110 may include a load database storing previously determined loads on the one or more platforms 102A-N. The controller 110 refers to the previous load stored in the load database pertaining to the first platform 104a and obtains a difference between the previous load with the new load. This difference determined between the previous load and the new load, is the change in load of the first platform 104a.
[057] Likewise, at step 512, the controller 110 may be configured to determine change in load of the second platform 104b. The controller 110 receives the new load determined by the load cell 202 of the second platform 104b from the hub 106, upon introduction of the new machine-readable member. The controller 110 refers to the previous load stored in the load database pertaining to the second platform 104b and obtains a difference between the previous load with the new load. This difference determined between the previous load and the new load, is the change in load of the second platform 104b.
[058] At step 514, the controller 110 may be configured to determine change in weight of the item corresponding to the introduced machine-readable member based on the change in load on the first platform 104a and the second platform 104b. In an embodiment, the controller 110 may include a weight database storing previous weights of one or more items present on the one or more platforms 102A-N. The controller 110 refers to the previous weight stored in the weight database pertaining to the one or more items on the first platform 104a and the second platform 104b. The controller 110 obtains a difference between the previous weight with the new weight. This difference determined between the previous weight and the new weight, is the change in weight of the item(s).
[059] At step 516, the controller 110 may be configured to communicate information indicating change in weight of the one or more items to the electronic device 114. The electronic device 114 may be communicatively coupled to the controller 110 via the second network 112. The controller 110 may be configured to initiate a digital notification when weight of an item, among the one or more items, based on a threshold or range of threshold.
[060] FIG. 6A is an exemplary diagram 600 illustrating machine-readable members placed on the first platform 102a among the at least two platforms and the second platform 102b among the at least two platforms, in accordance with an embodiment. One or more containers 104A-N are disposed on the first platform 102a and the second platform 102b. As shown in the diagram 600, the containers 104a, 104b, 104c, 104d, and 104e are disposed on the first platform 102a. The containers 104f, 104g, 104h, and 104i are disposed on the second platform 102b. Notably, the containers 104a-104i are equipped with machine-readable members.
[061] FIG. 6B is an exemplary diagram 600 illustrating an absence of the machine-readable member on the first platform 102a, in accordance with an embodiment. As shown in the diagram 600, the containers 104b, 104d, 104d, and 104e are disposed on the first platform 102a. The containers 104f, 104g, 104h, and 104i are disposed on the second platform 102b. The container 104a has been removed from the first platform 102a. As soon as the near field reader 204 of the first platform 104a senses that a machine-readable member, which was within its proximity, is no more within its purview, may send information about such machine-readable member to the controller 110. On the other hand, in such a scenario, the first platform 104a may send information about the machine-readable member(s), which are still under its proximity, wherein such information can be used by the controller 110 to determine which machine-readable member, and therefore the container, and therefore the item, has been taken off the first platform 104a.
[062] The controller 110 may be configured to determine change in load of the first platform 104a. The controller 110 receives the new load determined by the load cell 202 of the first platform 104a from the hub 106, upon absence of the machine-readable member. The controller 110 refers to the previous load stored in the load database pertaining to the first platform 104a and obtains a difference between the previous load with the new load. This difference determined between the previous load and the new load, is the change in load of the first platform 104a.
[063] FIG. 6C is an exemplary diagram illustrating an introduction of the machine-readable member, which was previously absent on the second platform 102b, in accordance with an embodiment. As shown in the diagram 600, the containers 104b, 104c, 104d, and 104e are disposed on the first platform 102a. The containers 104a, 104f, 104g, 104h, and 104i are disposed on the second platform 102b. The container 104a has been removed from the first platform 102a, and now disposed on the second platform 102b. As soon as the near field reader 204 of the second platform 102b senses that a machine-readable member is within its proximity, then it may send information about such machine-readable member to the controller 110.
[064] The controller 110 may be configured to determine change in load of the second platform 104b. The controller 110 receives the new load determined by the load cell 202 of the second platform 104b from the hub 106, upon introduction of the machine-readable member. The controller 110 refers to the previous load stored in the load database pertaining to the second platform 104b and obtains a difference between the previous load with the new load. This difference determined between the previous load and the new load, is the change in load of the second platform 104b.
[065] FIG. 7 is an exemplary diagram 700 illustrating a possible detection of a container 104 on multiple platforms 102, in accordance with an embodiment. As shown, an example scenario 700 may include a first platform 102a, a second platform 102b, a third platform 102c, a fourth platform 102d, and a container 104 placed on the first platform 102a.
[066] In an embodiment, the container 104 may be placed on the edge of platform 102a, which may be close to the edge of platform 102B. Platform 102a and platform 102b may be placed near each other. Due to this, the near field reader 204 of the first platform 102a detects the container 104, and the near field reader 204 of the second platform 102b also detects that the container 104. Hence, the controller, having received information about the container 104 from platforms 102a and 102b must determine, on which one of those platforms 102a, 102b the container 104 is actually placed.
[067] The problem described above is solved by configuring the near field reader 204 of the platforms 102 to determine signal strengths corresponding to the containers 104 (machine readable members of the respective containers in essence) in addition to reading the machine-readable members of the containers. Therefore, in the above example, the first platform 102a and the second platform 102b, in addition to communicating the information of the detected machine-readable members, also communicate the corresponding signal strength, to the controller 110, via the hub 106. The controller 110 may then be configured to determine the platform 102 on which the container 104 may be placed based on the received signal information. The platform 102 having the greater signal strength indicates the correct platform 102 on which the container 104 may be placed on. For example, if the signal strength of the first platform 102a is greater than the signal strength of the second platform 102b, then the controller 110 may be configured to determine that the container 104 may be placed on the first platform 102a.
[068] FIG. 8 illustrates an exemplary method 800 illustrating a flowchart for determining a correct platform 102 on which a container 104 is placed on based on signal strength information, in accordance with an embodiment. Each step is explained in further detail below.
[069] At step 802, the presence of the container 104 on the platforms 102A-N is detected. For example, the near field reader 204 of the first platform 102a detects the container 104 may be present on the first platform 102a, and the near field reader 204 of the second platform 102b detects that the container 104 may be present on the second platform 102b. Here, there is a possibility that the container 104 may be placed on the first platform 102a or the second platform 102b. The container 104 may be placed on the edge of platform 102a, which is close the edge of platform 102B. Platform 102a and platform 102b may be placed near each other.
[070] At step 804, the near field reader 204 may be configured to determine signal strengths corresponding to the container 104. For example, the controller 110 may be configured to receive the signal strength of the container 110 at the first platform 102a and the signal strength of the container 110 at the second platform 102b.
[071] At step 806, the controller 110 may be configured to determine the platform 102 on which the container 104 may be placed based on the received signal information from the near field reader 204 (for example the near field reader 204 of the first platform 102a and the near field reader 204 of the second platform 102b as mentioned above). The platform 102 having the greater signal strength indicates the correct platform 102 on which the container 104 may be placed on. For example, if the signal strength of the first platform 102a is greater than the signal strength of the second platform 102b, then the controller 110 may be configured to determine that the container 104 may be placed on the first platform 102a.
[072] FIG. 9 illustrates an exemplary method 900 illustrating a flowchart for determining a correct platform 102 on which a container 104 is placed on based on missing information, in accordance with an embodiment. Each step is explained in further detail below.
[073] At step 902, the presence of the container 104 on the platforms 102A-N is detected. For example, the near field reader 204 of the first platform 102a detects the container 104 may be present on the first platform 102, and the near field reader 204 of the second platform 102b detects that the container 104 may be present on the second platform 102b. Here, there is a possibility that the container 104 may be placed on the first platform 102a or the second platform 102b. The container 104 may be placed on the edge of platform 104, which is close the edge of platform 102B. Platform 102a and platform 102b may be placed near each other.
[074] At step 904, the controller 110 may be configured to determine missing information corresponding to the container 104. Missing information relates to scenarios where the container 104 may have been placed removed/added on one or more platforms 102A-N. For example, the container 104 may have been placed first on platform 102a, then removed from platform 102a, and then added/placed on platform 102b. Along with signal strength information as described in FIG. 8, load information of the platforms 102A-N may also have communicated to the controller 110.
[075] At step 906, the controller 110 may be configured to determine the correct platform 102 the container 104 may have been placed on, based on the missing information. As mentioned in the above example, the container 104 may be removed from platform 102a and placed on platform 102b. The load cell 202 of the first platform 102a determines the total load of the first platform 102a and the load cell 202 of the second platform 102b determines the total load on the second platform 102b. Due to the removal of the container 110 on the first platform 102a, the load of the first platform 102a decreases, as determined by the load cell 202 of the second platform. Due to the addition of the container 110 on the second platform 102b, the load of the second platform 102b increases, as determined by the load cell 202 of the second platform. The load determined by the load cell 202 of the first platform 102a and the load determined by the second platform 102b may then be communicated to the controller 110, via the hub. Hence, due to the change in load, the controller 110 may then be configured to determine that the container is now currently placed on the second platform 102b.
[076] In an embodiment, the user 116 may browse through one or more items using an application installed on the mobile device 114. When the user selects at least one item (for example rice), the controller 110 may send a notification to the corresponding platform 102 in which the item is held, via the hub 106. The platform 102 may include an alarm that beeps immediately once the notification from the controller 110 is received. Hence, one can approach the platform 102, and maybe pick the item.
[077] It shall be noted that the processes described above are described as sequence of steps; this was done solely for the sake of illustration. Accordingly, it is understood that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, or some steps may be performed simultaneously.
[078] It may be noted that some of the functions of the platform, hub, controller and the electronic device may be interchanged or shared with one more members of the system.
CONCLUSION
[079] The forgoing disclosure overcomes the drawbacks of the conventional inventory management system. Thus, the present invention as discussed in this document with respect to different embodiments will be advantageous at least for improving the management of products/goods within a kitchen or warehouse. Furthermore, the system and method are also advantageous as the product/good weights of the containers, along with the weights of the platforms are continuously updated to the electronic device associated with the user. Additional advantages not listed may be understood by a person ordinary skilled in the art in view of the embodiments disclosed above.
[080] In the foregoing detailed description, numerous specific details, examples, and scenarios are explained in order to facilitate a thorough understanding of the present disclosure. However, the embodiments of the disclosure may be practiced without such specific details. Further, such examples and scenarios are provided for illustration, and are not intended to limit the disclosure in any way. Those of ordinary skill in the art, with the included descriptions, should be able to implement appropriate functionality without undue experimentation. Thus, the scope of the invention should be determined by the appended claims and their legal equivalents rather than by details, examples, and scenarios provided.
[081] Although embodiments have been described with reference to specific example embodiments, it will be evident that various combinations, modifications, additions, and omissions may be made to these embodiments without departing from the broader spirit and scope of the foregoing disclosure and appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense.
[082] It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation.