CROSS-REFERENCE TO RELATED APPLICATION

[00011 This application claims priority to U.S. Provisional Patent Application No. 63/313,370, filed February 24, 2022, the entire disclosure of which is incorporated herein by reference.

BACKGROUND

[0002] The present disclosure generally relates to a networked food preparation apparatus, and more particularly to a food preparation apparatus configured to communicate on a low power wireless mesh (e.g., Bluetooth mesh) network.

[0003] Food preparation establishments such as restaurants, including quick service or fast food restaurants, have kitchens including various food preparation apparatuses. Conventional techniques for controlling and managing such apparatuses present several challenges. For example, such kitchens often include food preparation apparatuses from several different manufacturers using different communications protocols that cannot securely communicate with each other and with a central kitchen management system.

SUMMARY

[0004] In an aspect, a kitchen network system comprises a plurality of food preparation apparatuses. Each of the food preparation apparatuses includes a single board computer communicatively coupled to a wireless mesh network. The mesh network has a plurality of nodes, wherein the single board computer is one of the nodes of the mesh network. The single board computer comprises a processor, a built-in antenna, and one or more memory devices communicatively coupled to the processor. The memory devices store a database containing provisioning and configuration data for at least two of the nodes of the mesh network. The memory devices further store processor-executable instructions that, when executed by the processor, transmit and receive data on the mesh network via the antenna. generate a control signal for controlling an operation of the food preparation apparatus, and communicate the control signal on a physical data bus according to a message-based protocol. The system also includes an input/output (I/O) circuit communicatively coupled to the single board computer via the physical data bus and configured to receive the control signal therefrom. The I/O circuit is responsive to the control signal for driving one or more components of the food preparation apparatus to perform the operation.

[0005] In another aspect, a method of managing a plurality of food preparation apparatuses comprises provisioning at least first and second single board computers as nodes on a mesh network. A first food preparation apparatus includes the first single board computer and a second food preparation apparatus includes the second single board computer. The method also includes storing provisioning and configuration data for each the nodes of the mesh network in a database associated with each of the first and second single board computers. The method further includes generating, by the first single board computer, a control signal for controlling an operation of the first food preparation apparatus associated therewith and communicating the control signal from the first single board computer to a corresponding I/O circuit of the first food preparation apparatus. The control signal is communicated via a physical data bus according to a message-based protocol, and the I/O circuit of the first food preparation apparatus is responsive to the control signal for driving one or more components of the first food preparation apparatus to perform the operation.

[0006] Other objects and features of the present invention will be in part apparent and in part pointed out herein.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a diagram of a kitchen network of food preparation apparatuses according to an embodiment of the present invention.

[0008] FIGS. 2A and 2B illustrate example food preparation apparatuses for use in the network of FIG. 1. [0009] FIGS. 3-5 and 6A-6C are diagrams illustrating further aspects of the example food preparation apparatuses of FIG. 2B.

[0010] Corresponding reference characters indicate corresponding parts throughout the drawings.

DETAILED DESCRIPTION

[0011] Referring to the drawings, FIG. 1 illustrates a plurality of food preparation apparatuses 100 embodying aspects of the present invention. In the illustrated example, each food preparation apparatus 100 is configured as a food preparation apparatus for use in a food preparation establishment, such as a restaurant or other commercial kitchen, including a quick service or "fast food" restaurant. In an aspect, food preparation apparatus 100 is part of a food preparation establishment network system used for "smart kitchen" purposes, such as forecasting or predicting food that will be ordered in the future, preparing food, monitoring food preparation and food inventory, providing indications and instructions regarding food preparation and food inventory, labor scheduling management, asset tracking, smart appliance communication, sensor network integration, global inventory control, facilitating communications between devices in the network for these and other purposes, and the like. Commonly assigned International Application No. PCT/US2021/022925, the entire disclosure of which is incorporated herein by reference, discloses a networked kitchen system in which aspects of the present disclosure may be used.

[0012] The food preparation apparatus 100 may include various food cooking devices. An example of one such cooking device is an oven, and it will be understood that other cooking devices, such as fryers, microwaves, conditioning cabinets (e.g. for dough, etc.), grills, and the like can be used without departing from the scope of the present invention. The food preparation apparatuses 100 may also include one or more food holding units adapted for holding food at a suitable temperature (e.g., cool temperature, ambient temperature, and/or warm temperature) such as refrigerated back counters (RBC), tri-channel cold pan counters, steam tables, infrared holding units, heat sink holding units, reach-in under-counter refrigerators or freezers (RUF), hot/cold/freeze or hot/cold/frost units, or other holding units, etc. The food preparation apparatus 100 may also include various other food handling apparatuses such as food washers, sanitizers, processors, pans equipped with position sensors, etc.

[0013] Referring further to FIG. 1, the apparatus 100 in the illustrated embodiment includes a single board computer 102, a touchscreen controller (not shown), and an I/O circuit 106. In an embodiment, the single board computer 102 includes a processor, a memory, and a data bus interface; the touchscreen controller includes a processor, a flash data memory (RAM), a data bus interface, and an electronically erasable programmable read-only memory (EEPROM); and the I/O circuit 106 includes a processor, a flash data memory, and a data bus interface. The single board computer 102, touchscreen controller, and I/O circuit 106 are communicatively coupled to each other through a physical data bus 108 via their respective data bus interfaces. In the illustrated embodiment, single board computer 102 is configured to execute the operations of the touchscreen controller. In another embodiment, single board computer 102, touchscreen controller, and/or I/O circuit 106 could be embodied on the same printed circuit board, in which case a physical data bus may not be used for communication between the components.

[0014] Commonly assigned International Application No. PCT/US2018/061844, the entire disclosure of which is incorporated herein by reference, discloses the single board computer 102 configured to bridge the physical data bus 108 with a virtual data bus, store recipes, and provide, via a web server, a graphical user interface (GUI) for enabling a user of a client computer to configure recipe settings and/or firmware settings for food preparation apparatus 100, as further described herein. The single board computer 102 provides a core app, a web server, a database, and a virtual communication bus via a software environment (e.g., processor 102A executing processor readable instructions stored on memory 102B, etc.), as further described herein. The single board computer 102 may be referred to as an embedded computing device, an embedded computer, an embedded control device, and/or an embedded controller in accordance with one or more aspects of the disclosure. [0015] The I/O circuit 106 is configured to control various loads (e.g., heaters, valves, fans, etc.) in apparatus 100 based on commands from single board computer 102. In an embodiment, I/O circuit 106 (referred to as IOA in FIG. 1) includes power, relays, switch inputs, a resistance temperature detector (RTD), or the like. The I/O circuit 106 is configurable with four DIP switches or jumpers, for example, to accommodate 16 different outputs.

[0016] The physical data bus 108 is configured to facilitate the exchange of data among the control components of apparatus 100, such as single board computer 102 and I/O circuit 106. The single board computer 102 and I/O circuit 106 are configured to publish messages (e.g., data) to the physical data bus 108 and subscribe to messages on the physical data bus 108. In this manner, single board computer 102 and I/O circuit 106 are configured to communicate via a publish/subscribe ("pub/sub") protocol. In an embodiment, physical data bus 108 is a Controller Area Network (CAN) bus.

[0017] FIG. 1 further illustrates one embodiment of a network system embodying aspects of the present invention that includes the food preparation apparatus 100, a router 112, and a local computer 114 communicatively coupled via a communications network 116. In the illustrated embodiment, the local computer 114 is a smartphone but could be embodied by a variety of computing devices. In an embodiment, the communications network 116 comprises at least in part a kitchen network. In another embodiment, the communications network 116 comprises at least in part a food preparation establishment network system used for "smart kitchen" purposes.

[0018] According to aspects of the present disclosure, the communications network 116 comprises a mesh network on which one or more food preparation apparatus 100, router 112, and local computer 114 are nodes. Those skilled in the art are familiar with mesh networks in which infrastructure nodes (e.g., bridges, switches, and other infrastructure devices) connect directly, dynamically, and non-hierarchically to as many other nodes as possible in a many-to-many relationship and cooperate with one another to efficiently route data from/to clients. For example, food preparation apparatus 100, router 112, and local computer 114 may all be physically located within the same food preparation establishment 118, such as a restaurant or other commercial kitchen, including a quick service or "fast food" restaurant. In an embodiment, a plurality of food preparation apparatuses 100 is communicatively coupled to the router 112 and/or local computer 114 via mesh network 116. The router 112 is configured to communicatively couple food preparation apparatus 100 and local computer 114 on mesh network 116 to an external communications network such as the internet.

[0019] In an embodiment, the single board computer 102 of one or more of the apparatuses 100 is configured for low energy communications in accordance with, for example, the Bluetooth Low Energy (BLE) standard and mesh network 116 comprises a Bluetooth mesh network. For example, single board computer 102 (referred to as IOCG in FIG. 1) has built-in Bluetooth and Wi-Fi capabilities. The single board computer 102 can function as a gateway thus eliminating the need for a separate Zigbee or similar gateway. Accordingly, the single board computer 102 in this embodiment can be a node on mesh network 116 and/or a wireless gateway. As nodes, the single board computers 102 of food preparation apparatuses 100 are configurable to receive firmware updates via mesh network 116. The local computer 114 is configurable to operate as a "master control" computer on the Bluetooth mesh network 116 for changing settings on devices, set auto schedules, update firmware, etc. In one example, the local computer 114 can be used to make updates to software, firmware, and/or operational settings of some or all of the apparatuses 100 in bulk (e.g., pushing updates/changes to all of the apparatuses in a group instead of updating each individual apparatus in separate processes). Via the mesh network 116, the local computer 114 can pair with all of the nodes in a "one-to-many" arrangement which has efficiency and other advantages over a "one-to-one" pairing arrangement.

[0020] Moreover, each apparatus 100 is configurable such that it has its own CAN bus network. For instance, I/O circuits 106 output messages to physical data bus 108, which is a CAN bus. The mesh network (i.e., communications network 116) connects to CAN bus networks within the store 118. A smartphone (i.e., local computer 114), can connect to the mesh network 116 via a proxy server. Connecting to the mesh network 116 enables connection to the CAN communications in apparatuses 100 as well as connection to a cloud-based to Internet of Things (loT) platform, such as the SousChef Cloud, which handles recipe management, operation management, equipment/asset management, etc. In other words, single board computer 102 functions to merge or bridge CAN bus and wireless networks. A user can pull diagnostics and/or maintenance information from every node on mesh network 116 via a mobile app executing on the smartphone. In this embodiment, local computer 114 need not be coupled directly to the mesh network 116, which prevents the risk of an outside maintenance person accessing the restaurant's internal network.

[0021] Aspects of the present disclosure permit layers of authentication keys for improved network security. A Bluetooth mesh network requires multiple layers of encryption. In an embodiment, the manufacturer ships a network key stored in single board computer 102 and maintains a master key. A mobile phone app stores a network key, which it receives from the manufacturer for authentication. The app mates with the food preparation apparatus 100 that was shipped with the same key to connect to the network 116. Encryption/authentication can be extended to third party devices from different vendors by having these devices on the master key and then having a second layer key specific to the first party manufacturer. Multiple vendors could communicate via the same Bluetooth mesh network, all encrypted/isolated in Bluetooth from each other or could share authentication keys (different levels to permit sharing).

[0022] FIG. 2A illustrates a kitchen network system in the form of a counter control system embodying aspects of the present disclosure. The system includes a plurality of networked counters 200, each embodying a food preparation apparatus 100. FIG. 2B illustrates the components of one of the counters 200 in greater detail. In the illustrated embodiment, each networked counter 200 includes a plurality of single board computers 102 (referred to as loT displays 202 in FIG. 2B). Each of the loT displays 202 in the embodiment of FIGS. 2A-2B includes an antenna (e.g., a multi-directional radiating element) and is configured to serve as a node on mesh network 116. In addition, each loT display 202 is coupled to, or paired with, a corresponding I/O circuit 106 via the physical data bus 108. As shown in FIG. 2B, each I/O circuit 106 is embodied by an IO control board 206 and the physical bus 108 is embodied by a CAN bus 208. Each loT display 202 has a unique address on the CAN bus 208, a unique media access control (MAC) address on the mesh network 116, and a unique serial number address.

[0023] The loT displays 202 each include a database 220 storing information about the mesh network 116 in each node as well as information related to the paired IO control boards 206. For example, the database 220 stores calibration offsets, serial number information, configuration data, physical addresses on CAN bus 208, and the like. In an embodiment, the databases 220 of loT displays 202 each store control serial number configuration data for their sibling loT displays so that each pair can be replicated on the mesh network 116. Moreover, because each database 220 stores provisioning data for its corresponding node as well as the other nodes, provisioning of mesh network 116 is more easily accomplished.

[0024] The IO control boards 206 each control one or more components of counter 200 (e.g., lights, pumps, temperature). For purposes of illustration, FIG. 2B shows each IO control board 206 coupled to a sensor 222 and an electrical load 224. By restricting the commands received by IO control board 206 to those communicated via the physical CAN bus 208, the counter control system of FIGS. 2A-2B improves overall security. In an embodiment, each of the loT displays 202 has a touchscreen coupled to it that is configured for interaction with a user to permit direct user control of the one or more components of counter 200. In addition, the touchscreen may be used for inputting a personal identification (PIN) code or the like to lock or unlock the paired IO control board 206.

[0025] In FIG. 3, the counter control system of FIG. 2B experiences a failed node. For example, when any individual loT display 202 (indicated at "loT Display #2" in FIG. 3) is destroyed or otherwise missing from the mesh network 116, the distributed system detects this state and allows for a sibling loT display 202 (indicated at "loT Display #4" in FIG. 3) to stand in as a controller thus providing redundant control of the IO control board 206 previously associated with the failed node. The loT displays 202 collect status information regarding their paired 10 control boards 206 via CAN bus 208 and provide the status information to each other using, for example, a Raft consensus algorithm. As shown in the example of FIG. 3, loT Display #2 is no longer on mesh network 116 and no longer communicates with its corresponding 10 control board 206. Instead, the loT Display #4 detects that its sibling loT Display #2 is missing and sends/receives data and commands via CAN bus 208 to provide for seamless control of the respective 10 control board 206 previously paired with loT Display #2. In an embodiment, a user designates which loT display 202 stands in for the failed controller and stores this information in database 220. According to aspects of the present disclosure, the stand-in loT display 202 replaces control rather than merely re-routing communications to avoid a failed node.

[0026] Referring now to FIG. 4, the counter control system of FIG. 2B again experiences a failed node (indicated at "loT Display #2" in FIG. 4). When the distributed system detects this state, a sibling loT display 202 (indicated at "loT Display #1" in FIG. 4) stands in as a controller. As shown in the example of FIG. 4, the local computer 114, such as a smartphone executing a mobile application, sends commands to the 10 control board 206 corresponding to the failed loT display 202 via the "closest" node in the mesh network 116 that is also connected on CAN bus 208. In the illustrated embodiment, local computer 114 connects to the mesh network 116 as a BLE proxy node and the closest node is loT Display #1. In this manner, the mobile application acts as a control element paired with the closest loT display 202 (i.e., loT Display #1). The mobile application executing on local computer 114 sends commands to and receives data from the respective 10 control board 206 previously paired with loT Display #2 via another one of the loT displays 202, namely, loT Display #1.

[0027] Referring now to FIG. 5, aspects of the present disclosure facilitate replacement of damaged loT displays 202. In the event one of the loT displays 202 (indicated at "loT Display #7" in FIG. 5) needs to be replaced in the field, the remaining loT displays 202 coupled to CAN bus 208 are configured to detect the new "bare" board. For example, FIG. 5 illustrates an embodiment in which loT Display #7 has been replaced and, thus, is a bare board. The new loT Display #7 is not yet configured to connect to mesh network 116 but it is recognized as a legitimate replacement because it is physically connected to CAN bus 208. One of the loT displays 202 (indicated at "loT Display #6" in FIG. 5) detects the new board and provides a set of steps for configuring the bare board. In the example of FIG. 5, loT Display #6 provides a set of steps to replace the BLE mesh secrets that the replaced loT Display #7 previously used for connecting to mesh network 116. In this regard, loT Display #6 stores the necessary encryption keys in a flash memory and reprograms the new loT Display #7 with the necessary security keys to communicate on mesh network 116. To avoid a loss of data for the IO control board 206 previously paired with the replaced loT display 202, loT Display #6 trains the replacement loT Display #7 based on the control serial number configurations from the sibling databases 220.

[0028] FIGS. 6A-6C illustrate an embodiment of the counter control system of FIG. 2B in which loT displays 202 of counters 200 are connected to not only mesh network 116 but also to a remote network 602 via router 112. In this embodiment, the loT displays 202 each have concurrent BLE mesh and WiFi capabilities and are configured to keep track of all WiFi service set identifier (SSID) names and correlated RF signal strength to these stations. The loT displays 202 share their WiFi signal strength information with each other so as to determine a collective "leader" gateway to elect as the shared WiFi client for the mesh network 116. In this manner, the elected leader serves as a gateway even though the counter control system is gateway-less. If the elected "leader" (e.g., loT Display #1 in FIGS. 6A-6C) fails, the nodes on mesh network 116, i.e., the other loT displays 202, will detect the missing leader, and elect another node having the next highest WiFi RF signal strength as the new "leader." FIG. 6C illustrates examples of relative signal strength at the various nodes of mesh 116. The effect of this system is that an IT network would only ever have one device on the WiFi network.

[0029] Embodiments of the present disclosure may comprise a special purpose computer including a variety of computer hardware, as described in greater detail herein.

[0030] For purposes of illustration, programs and other executable program components may be shown as discrete blocks. It is recognized, however, that such programs and components reside at various times in different storage components of a computing device, and are executed by a data processor(s) of the device.

[0031] Although described in connection with an example computing system environment, embodiments of the aspects of the invention are operational with other special purpose computing system environments or configurations. The computing system environment is not intended to suggest any limitation as to the scope of use or functionality of any aspect of the invention. Moreover, the computing system environment should not be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example operating environment. Examples of computing systems, environments, and/or configurations that may be suitable for use with aspects of the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

[0032] Embodiments of the aspects of the present disclosure may be described in the general context of data and/or processor-executable instructions, such as program modules, stored one or more tangible, non-transitory storage media and executed by one or more processors or other devices. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the present disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote storage media including memory storage devices. [0033] In operation, processors, computers and/or servers may execute the processor-executable instructions (e.g., software, firmware, and/or hardware) such as those illustrated herein to implement aspects of the invention.

[0034] Embodiments may be implemented with processor-executable instructions.

The processor-executable instructions may be organized into one or more processor-executable components or modules on a tangible processor readable storage medium. Also, embodiments may be implemented with any number and organization of such components or modules. For example, aspects of the present disclosure are not limited to the specific processor-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments may include different processor-executable instructions or components having more or less functionality than illustrated and described herein.

[0035] The order of execution or performance of the operations in accordance with aspects of the present disclosure illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of the invention.

[0036] When introducing elements of the invention or embodiments thereof, the articles "a," "an," "the," and "said" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements.

[0037] Not all of the depicted components illustrated or described may be required. In addition, some implementations and embodiments may include additional components. Variations in the arrangement and type of the components may be made without departing from the spirit or scope of the claims as set forth herein. Additional, different or fewer components may be provided and components may be combined. Alternatively, or in addition, a component may be implemented by several components.

[0038] The above description illustrates embodiments by way of example and not by way of limitation. This description enables one skilled in the art to make and use aspects of the invention, and describes several embodiments, adaptations, variations, alternatives and uses of the aspects of the invention, including what is presently believed to be the best mode of carrying out the aspects of the invention. Additionally, it is to be understood that the aspects of the invention are not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The aspects of the invention are capable of other embodiments and of being practiced or carried out in various ways. Also, it will be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.

[0039] It will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims. As various changes could be made in the above constructions and methods without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.

[0040] In view of the above, it will be seen that several advantages of the aspects of the invention are achieved and other advantageous results attained.

[0041] The Abstract and Summary are provided to help the reader quickly ascertain the nature of the technical disclosure. They are submitted with the understanding that they will not be used to interpret or limit the scope or meaning of the claims. The Summary is provided to introduce a selection of concepts in simplified form that are further described in the Detailed Description. The Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the claimed subject matter.