BACKGROUND OF THE INVENTION

[001] Technical Field

[002] The present disclosure relates to retail systems and more specifically to providing enhanced user experience in restaurant environments.

[003] Related Art

[004] With advent of smart portable devices like smart phones, touch based PDA (personal digital assistant), etc., many new user experiences are being created, in particular, in restaurant environments. For example, there are many applications available for smart portable devices that help users to design a new (or a modified) desired food/beverage item (referred hereafter to as a "FB item"). The applications present information of the ingredients needed for a given FB item and the method of mixing the ingredients to create different desired FB items.

[005] The primary motivation of these applications (some of which are mere extended versions of the similar applications such as Cocktail Maker available from Playsstos Entertainment, currently available on the Internet) is to help the end user to design well know FB items by reading presented information and method. In other words, a user reads the presented information (in an interactive manner), deriving a better user experience than designing FB items by reading a textual description e.g. book or web portal. The applications also facilitate a user to select additional and/or alternative ingredients and also the manner/order in which the selected ingredients are to be mixed, thereby enabling the user to design his/her desired FB item.

[006] However, such applications are generally rudimentary and do not provide a rich/enhanced user experiences of designing FB items. For example, current applications do not show true colors of the FB item (e.g., a cocktail or a dessert) while presenting a visual interface. As such, when a user selects to mix two liquids such as vodka (which has almost the same color of water) and an orange juice, the resultant mixture is not displayed with a lighter orange color (as would be result of the liquids noted above). Accordingly, if such an application is presented in a restaurantular for usage by the guests, the guest may not know how the final FB item (cocktail/dessert) will really looks like especially there is an opportunity to change any ingredients.

[007] There is a general need to provide enhanced user experience in restaurant environments, in particular, when the user is designing desired FB items.

SUMMARY OF THE INVENTION

[008] An aspect of the present invention facilitates guests/ users to order personally designed FB items in a restaurant environment. In one embodiment, a user uses a his/her personal computational/communication device or similar devices provided by the restaurants to design his/her own desired FB items by selecting desired combination of building blocks provided on a visual interface. For example, the user may design personal cocktails using building blocks such as different alcoholic drinks, non-alcoholic drinks, fruit juices, ice cube, crushed ice, many different spices, sugar, salts etc. Alternatively, the user may design their own ice-cream based desserts using building blocks like scoops of different ice-creams, fruits (cut or whole), candies, chocolate, syrups of different colors and taste, fruits pulps or juices, sodas or other drinks (alcoholic or non-alcoholic), etc. A visualization of the desired FB item (being designed) based on the resulting combination of the building blocks is then displayed to the user. [009] Another aspect of the present invention enables the users to indicate the manner in which the personal FB item is to be prepared, for example, by specifying constraints on the building blocks. Example of constraints are the specific quantities and qualities of each of the building blocks to be included in the FB item, the specific container in which the FB item is to be served, the placement of the building blocks in the container (e.g., when they are solids), the order in which the building blocks are to be added to the FB item (e.g., typically when the selected blocks are liquids/gases), etc.

[010] Yet another aspect of the present invention computes various characteristics of the personalized FB item (being designed) based on the combination of building blocks and corresponding constraints specified by the user. The computed characteristics are then displayed along with the visualization of the FB item. Examples of characteristics include but are not limited to a resultant taste of the FB item, an alcohol content of the FB item, a number of calories present in the FB item and an expected cost of the FB item.

[011] A system provided according to the invention captures such information (for example, in the form of a list of instructions) and ensures that the manner of preparation is followed, when the personal FB item is actually prepared (by the restaurant). For example, a chef preparing the personal FB item may be shown at any time instance, only one of the instructions from the list, with the next instruction shown only when a previously displayed instruction has been completed. Such "walk-through" (or single stepping) of the list ensures that the personal FB item is prepared as per the manner desired by the user.

[012] One more aspect of the present invention facilitates the preparation of the personal FB items in an automated manner. In one embodiment, the manner of preparation as indicated by the end user is captured as data according to a machine readable format, and such captured data is provided to an automated machine for preparation of the personal FB item. For example, an automated cocktail making machine may be provided with the specific instructions received from the user, to enable the personal cocktail to be made in an automated manner.

[013] Several aspects of the invention are described below with reference to examples for illustration. However, one skilled in the relevant art will recognize that the invention can be practiced without one or more of the specific details or with other methods, components, materials and so forth. In other instances, well-known structures, materials, or operations are not shown in detail to avoid obscuring the features of the invention. Furthermore, the features/aspects described can be practiced in various combinations, though only some of the combinations are described herein for conciseness.

BRIEF DESCRIPTION OF THE DRAWINGS

[014] Example embodiments of the present invention will be described with reference to the accompanying drawings briefly described below.

[015] FIG. 1 is a block diagram illustrating an example environment in which various aspects of the present invention can be implemented.

[016] FIG. 2A is a flow chart illustrating the manner in which a user is enabled to design and place an order for a desired food/beverage item in one embodiment.

[017] FIG. 2B is a flow chart illustrating a manual approach to satisfying an (user) order for a desired food beverage item in one embodiment.

[018] FIG. 2C is a flow chart illustrating an automated approach to satisfying an (user) order for a desired food/beverage item in one embodiment.

[019] FIG.s 3A-3D depicts the manner in which user experience for designing a personal food/beverage item is enhanced in one embodiment.

[020] FIG. 4A depicts an example implementation of the manual approach to satisfying an (user) order for a desired food/beverage item.

[021] FIG. 4B depicts an example implementation of the automated approach to satisfying an (user) order for a desired food/beverage item.

[022] FIG. 5 depicts sample portions of a transcript generated for capturing the manner of preparation of a personal food/beverage item in one embodiment.

[023] FIG. 6 is a block diagram illustrating the details of a digital processing system in which various aspects of the present invention are operative by execution of appropriate execution modules.

[024] In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number.

DETAILED DESCRIPTION OF THE INVENTION

[025] 1. Example Environment

[026] FIG. 1 is a block diagram illustrating an example environment in which various aspects of the present invention can be implemented. The block diagram is shown containing client devices 11a-11c, network 12, food and beverage (FB) server 15, dispensing machine 17 and data store 18. Merely for illustration, only representative number/type of systems is shown in FIG. 1. Many computing systems often contain many more systems, both in number and type, depending on the purpose for which the computing system is designed. Each system/ device of FIG. 1 is described below in further detail.

[027] Network 12 provides connectivity between client devices 11a-11c, FB server 15 and dispensing machine 17. Network 12 may represent Wireless/LAN networks implemented using protocols such as Transport Control Protocol/Internet Protocol (TCP/IP), or circuit switched network implemented using protocols such as GSM, CDMA, etc. as is well known in the relevant arts.

[028] In general, network 12 provides transport of packets, with each packet containing a source address (as assigned to the specific system from which the packet originates) and a destination address, equaling the specific address assigned to the specific system to which a packet is destined/targeted. The packets would generally contain the requests and responses between the client devices 1 la-1 Ic, FB server 15 and dispensing machine 17 as described below. [029] Data store 18 represents a non-volatile storage, facilitating storage and retrieval of a collection of data by FB server 15. Data store 18 may maintain information such as user data received from client devices 11a-11c, modes of communication supported by each type of client device, the details of the personal FB (food/beverage) items created previously/currently by each user using client devices 1 la-1 Ic, etc.

[030] In one embodiment, data store 18 is implemented using relational database technologies and provides storage and retrieval of data using structured queries such as SQL (Structured Query Language), as is well known in the relevant arts. Alternatively, data store 18 may be implemented as a file server and store data in the form of one or more files organized in the form of a hierarchy of directories, as is well known in the relevant arts.

[031] Each of client devices 11a-11c represents a system such as a personal computer, workstation, mobile phones (e.g. iPhone available from Apple Corporation), tablets, portable devices (also referred to as "smart" devices") that operate with a generic operating system such as Android operating system available from Google Corporation, etc., used by users to send (client) requests to FB server 15.

[032] The client requests may be for designing of the personal FB item (for example, to add or remove a building block, change the quantity of a building block forming the FB item, etc,), for placing orders for previously or currently designed personal FB items, for tracking the history of the personal FB items designed/ordered, etc. The client requests may be generated using appropriate user interfaces. In general, a client device enables a user to send client requests for performing desired tasks to FB server 15 and to receive corresponding responses containing the results of performance of the requested tasks.

[033] FB server 15 represents a system, such as a web and/or application server, executing various software applications designed to perform tasks (such as storing user requested orders for personal FB items, the details of the personal FB items, etc.) requested by users using client devices 11a-11c. The applications may perform the tasks using data maintained internally FB server 15 or on external data (e.g. maintained in data store 18). The results of performance of the tasks may then be sent as corresponding responses to the requesting client device.

[034] In one embodiment, the users/guests in a restaurant are provided with a software application running in their personal phone or other computation devices, which each guest can use to design their own desired personal FB items. The software application may be downloaded from FB server 15 (by sending appropriate client requests) or from third party systems such as App Store available from Apple Corporation, Android Apps available from Google Corporation. The software application may be downloaded along with the building blocks (as offered by the restaurants) that can be used to design the personal FB item (such as a cocktail or dessert). [035] In an alternative embodiment, a restaurant or any other equivalent place where such food and beverages are served may provide the guests with a smart device pre-loaded with the software application (and also the building blocks) needed for the designing the personal FB item. Thus, a user may first design the desired personal FB item using the software application provided on his/her personal device or the smart device located at the restaurant, and thereafter send a request with the details of the newly designed personal FB item along with an order for the desired quantity of the item to FB server 15.

[036] Dispensing machine 17 represented an automated dispensing machine that is capable of mixing and creating FB items such as cocktails and desserts in an automated manner (that is, without any human intervention after the ingredients/building blocks are loaded). In one embodiment, dispensing machine 17 is designed to receive a list of instructions in a machine readable format (such as XML) and to perform the instructions in the order specified in the list to create the corresponding personal FB item.

[037] FB server 15 provides for enhanced user experience according to several aspects of the present invention, in particular when the user is designing personal FB items. The manner in which FB server 15 enhances user experience is described below with examples.

[038] 2. General Flow

[039] FIG. 2A is a flow chart illustrating the manner in which a user is enabled to design and place an order for a desired food/beverage item in one embodiment. The flowchart is described with respect to Figure 1 merely for illustration. However, various features can be implemented in other environments also without departing from the scope and spirit of various aspects of the present invention, as will be apparent to one skilled in the relevant arts by reading the disclosure provided herein. In addition, some of the steps may be performed in a different sequence than that depicted below, as suited in the specific environment, as will be apparent to one skilled in the relevant arts. Many of such implementations are contemplated to be covered by several aspects of the present invention.

[040] In step 21, a user (such a guest visiting a restaurant or bar) designs a desired FB item using a "Virtual Food Creator" application, the interface of which is described in detail below with respect to FIG.s 3A-3D. In particular, the application enables the user to select a desired combination of building blocks from a plurality of building blocks provided on a visual interface.

[041] In addition to the desired combination of building blocks, the user may specify constraints such as a corresponding quantity of each of the combination of building blocks, a specific container in which the desired FB item is to be served, a placement of at least some of the combination of building blocks in the specific container, and an (sequential) order in which a subset of the combination of building blocks are to be added to the desired FB item. In other words, the specified combination and constraints specify a manner of preparation of the desired FB item.

[042] In step 22, the application displays the resultant FB item's visualization based on the selected combination of building blocks and the user specified constraints. In step 23, the application also computes characteristics of the FB item such as a resultant taste, alcohol content, the number of calories present and an expected cost/price of the user personalized FB item. In one embodiment, the computed characteristics are also displayed along with the FB item's visualization displayed in step 22.

[043] Steps 21-23 may be repeatedly performed until the user designs the desired FB item. Once the user is satisfied with the design, the user in step 24, places an order for the designed FB item. The order is placed with FB server 15 by sending a client request containing data representing the order and also the details of the manner of preparation of the personal FB item.

[044] In step 25, a list of instructions representing the manner of preparation (the user specified combination of building blocks and the associated user specified constraints) of the personal FB item is generated. The list may be generated by FB server 15, or by the software application executing in client devices 11 a-He (and later sent to FB server 15 as part of the order request). The list may be generated in any convenient format, and stored in data store 18. In one embodiment, the list of instructions is generated in the form of a transcript according to extensible Markup Language (XML), a sample portion of which is shown in Figure 5.

[045] In response to receiving the order for the personal FB item, FB server 15, may process the order in either a manual or automated manner. Each of FIG. 2B and 2C illustrate respectively a manual and automated approach to satisfying an (user) order for a desired FB item, in one embodiment. The prepared personal FB item is then served to the user.

[046] Referring to FIG. 2B, in step 27a, the list of instructions (generated in step 25) is presented to a human creator (such as a bartender, a chef, etc.) in a humanly readable format. In step 27b, the human creator creates the personal FB item accordingly the manner of preparation specified by the list of instructions. For example, the human creator may use the user specified quantities for each of the combination of building blocks and then add them to the user specified specific container according to the sequential order or placement specified by the user. In step 27c, the manual preparation of the personalized FB item (as specified/designed by the user) is completed and the FB item is ready for serving.

[047] Referring to FIG. 2C, in step 28a, the list of instructions (generated in step 25) is fed into (or sent over network 12) an automated dispenser (such as dispensing machine 17) in a machine readable format, for example, according to XML. In step 28b, the automated dispenser (dispensing machine 17) creates the personal FB item by adding each ingredient/building block according to the quantity, placement and the sequential order specified by the list of instructions. In step 28c, the automated preparation of the personalized FB item (as specified/designed by the user) is completed and the FB item is ready for serving.

[048] It should be appreciated that that irrespective of the manual or automated approach, the personal FB item is prepared exactly in the manner in which user specified using the interfaces of the "Virtual Food Creator" application. In other words, the XML transcript is generated in step 25 to capture the specific sequence of operations to be performed as part of the preparation of the personal FB item and FB server 150 ensures that the same sequence is followed during the manual/automated preparation of the FB item. The manner in which the steps of FIG.s 2A-2C provide an enhanced user experience is described below with examples.

[049] 3. Enhanced User Experience

[050] FIG.s 3A-3D depicts the manner in which user experience for designing a personal food/beverage item is enhanced in one embodiment. The description is continued assuming that the "Virtual Food Creator" application is executing in FB server 15, and that the portions of the user interfaces shown in FIG.s 3A-3D are provided on a display unit associated with one of client devices 11 a-lie (in response to client requests received from the one client device). As noted above, in alternative embodiments, the application may be executing in users' personal device or restaurant's smart device and provide similar interfaces.

[051] Visual interfaces 30 of FIG.s 3A-3D enables user to designing of a FB item to be started in two different ways. In one approach, it starts with the user selecting one of the many FB items offered in the menu as exposed by the application (for example, after selecting the "Edit One" button 33 in FIG. 3B, where the interface of FIG. 3B is displayed in response to the user selecting the "Create Cocktail" button 31 in FIG. 3A). The interface of FIG. 3C may be shown in response to the user selecting/clicking button 33.

[052] FIG. 3C depicts an user interface providing various FB items previously created by other users and stored/exposed by the application to the current user. The FB items are shown provided as preconfigured menu options (in display area 34) such as Top of the Day, Best of the month. Best so far, Sweet ones, Salted, etc. Upon the user selecting a menu option such as Top of the Day, the corresponding FB item (or in some scenarios, multiple FB Items) is displayed to the user. For example, FIG. 3C is shown displaying the FB item named "Blue Angel" in display area 35 in response to the user selecting the Top of the Day menu option.

[053] The application also allows the user to change some of the building blocks by selecting "Change" button 36a. For each of the building blocks, the user then can change in to another type of the same building blocks. For example, a user may change one alcoholic drink with another drink of any nature (e.g. Vodaka with Rum or Sprite) or change one coloring agents with another equivalent, etc. When designing desserts, the user may change one ice-cream scoop with another ice-cream scoop (e.g. vanilla with butterscotch) or change one syrup with another equivalent (e.g. Chocolate syrup with Mango pulp) etc.

[054] The display may accordingly change to reflect the final outcome of the mixed FB item, as shown in display area 35. After the user is satisfied with the resultant FB item, the user may select/click on "Order" button 36b to place an order for the personalized FB item. In response to the user selecting the "Order" button, FB server 15 may generate the list of instructions capturing the user specified combination of building blocks and constraints and forward the generated list for manual/automated preparation of the personalized FB item (as described above with respect to FIG.s 2B and 2C). Also, the application may wait for payment confirmation before executing the order (for example, due to the policies enforced by the restaurant).

[055] In another approach (for example, by selecting the "Create From Scratch" button 32 in FIG. 3B), the users are enabled create from scratch their own FB item using all the building blocks offered in the application. For this embodiment, the building blocks needed for starting the design of a FB item typically are provided to the user and the user may be guided regarding the design process. An example visual interface for creating a new FB item (named "Red Devil") is shown in FIG. 3D, with the user being guided based on the menu options shown in display area 37a.

[056] The design process usually starts with selection of serving container (such as a bowl, glass, goblet of a desired shape/size) in which the prepared FB item is sought to be served. The shape and capacity of the container is also used in the design consideration (as well as the visual presentation) of the personal FB item. For example, while an broader (in terms of surface) container may allow one to design a FB item commonly known as "Banana Split Ice-cream", a tall glass may allow stacking of 5-6 scoops of ice-cream but may not allow a banana inside as it is inconvenient for the guest eat the same. Thus, the application guides the user regarding the selection of the specific containers needed for a given design.

[057] The information on the various containers may be maintained as an XML map of the container names and their different size factors like length, width, diameter, height, volume. This XML file is editable in real time by the restaurant staff to add new containers or remove one or more existing containers or edit one or more parameters as needed.

[058] The application may offer a visual display of all the available containers which guests can touch to select, for example, as shown in display area 37b. Each of the images of the container may give actual dimensions of the container which may or may not help guest to appreciate actual size. So alternatively the application may also display a sample FB item design instead of displaying a bare image of the container image. As the primary building block is scoops of ice cream when designing a dessert, the size in terms of maximum number of scoops of ice-cream allowed in a given container may be described along with the images and other dimension. [059] Upon selection of the said container or the bowl, the application allows the guests to design the desired FB item using all available building blocks such as ice-cream scoops, candies, syrups, cut or whole fruits, fruit pulps or juices, other condiments, coloring agents, decorative pieces made of edible (biscuits etc) or even non-edible materials (paper artifacts, straws etc). Only a few sample building blocks such as juices, masalas, coloring are shown in display area 37a and are described here for conciseness, though in a real time application, the number and/or type of building blocks will be in the order of hundreds, as will be readily appreciated by one skilled in the relevant arts.

[060] The application builds a XML list of all building blocks containing parameters like type, state, edibility, volume, color, taste, no-used-over, no-used-under, layer-position, price for each of the building blocks offered through the application. Table contains meaning and usage of each of the parameters:

Parameter Meaning

Type Type of the building block - ice-cream, syrups, candies, juices,
colas, umbrellas, fruits
State Solid or Liquid or semi-solid
Edibility Whether it is edible or not
Volume Volume in CC
Color Color of the block
Taste Taste of the block - sweat(+/-_, sour(+/-), none, fuzz,
No-Use-over Cannot be use over this block
No-Used-under Cannot be use under this block
Layer-position To be used only at this layer position - top, bottom or number
Price Price of each scoop or serving as the case may be

Calorie Calorie value of the item

[061] The application consider each of the building block including the container in three dimensions making a near realistic calculation of volume occupied and left upon using size parameter of each of the building blocks. Using these actual dimensions of the building blocks, the application calculates actual volume occupied by each building block inside the container and also know how much is left. So the application can tell how many more building blocks can further be used.

[062] Application may offer many different user interfaces to enable this user experience. In one embodiment, the user may touch appropriate icons of the building block to add the same into the container. Removal of an item from the container may be done by going to a deletion menu option and then touching items that need to be taken out.

[063] For solid items, once a solid item (e.g. ice-cream) is in the container, the guest can adjust the position within the container honoring the dimension of the items. The application can then allow a solid item to be stacked upon the previous solid one and allow guest to adjust the position within allowable limit of dimension of the container including over sizing needs. [064] For liquids items, the application may try to simulate actual spreading based on well know principle of physics. The simulation may focus on creating the true visual experience that the final cocktail will have enabling the guests to recognize the served cocktail as their own creation. The application also would simulate the mixing of ice cube or crashed ice. However this simulated handling of spreading of liquid in the application on the screen and actual dessert while served may not be exactly the same though guests should be able to recognize the served dessert is their own creation.

[065] In an alternative embodiment, the same experience can be enabled by dragging and dropping an icon into the container to add the same or position at appropriate place on the container or dragging out from the container to remove it. [066] The application may use the color parameter to visualize the color of the resultant personal FB item. In case of multiple liquids poured in the container, the application computes spreading for each of the layer separately and calculates resultant where the liquids are overlapped. The resultant visualization of the FB item is then displayed to the user in display area 38.

[067] As the items are put inside the container, the application calculates the overall taste of the FB item using simple pre configured rules. For example, one scoop of sour ice-cream along with 2 scoops of sweet ice-cream may be treated sweet. Similarly, one serving of sour tasting liquid (lime juice) along with 2 servings of sweet liquid (e.g. white wine, sugar syrup) will make the resultant cocktail 'sweet and sour'. If a user tries to add too much of the sweet or salt or any other ingredients, the application may alert the user or even may not allow the user to add them to the FB item.

[068] In the same manner, the application may calculate other characteristics such as the total price/cost and the calorie counts of the designed FB item. The computed characteristics are also displayed in display area 38 along with the visualization of the FB item. The user may then select the "Done" button to indicate that the FB item "Red Devil" has been created as per the personal desires of the user. The user may then proceed to place an order for the personalized FB item, for example, using the "Order" button 36b of FIG. 3C.

[069] Once the order is placed and accepted for delivery, the order is visible to the respective section of the restaurant. The experts (such as chefs and bar tenders) in the restaurant, not only see the visuals created by the guest but also reads the instructions steps displayed by the application to recreate the FB item. The instructions are given step by step and at completion of each step, the expert has to press a button/menu option to move to the next step. Once the personal FB item is created, the FB item may be served without further wait as the simulation environment does not include the effect melting of ice-cream etc. due to atmospheric heating or does not consider impact of the fluid flow for longer wait. A quick delivery/serving will ensure the visuals of the created FB item on display and on the table has similar look and feel.

[070] In one embodiment, the created FB item is prepared by an automatic dispensing machine (such as dispensing machine 17) based on machine readable XML transcripts. It may be appreciated that some of the steps which cannot be done by the automatic dispenser (e.g. it is not capable by design or not functioning for some reason) it will alert for human interference in completing those steps. Once an appropriate expert (chef/bar tender) completes the steps requiring manual intervention, a button or menu option can be pressed to indicate the machine to continue from the next step. Once all steps are complete, dispensing machine 17 may attract human attention to initiate delivery of the FB item to the user/guest (who placed the order).

[071] According to one aspect of the invention, once a FB item is designed and the application finds it unique in constituent, the guest may be allowed to give it a name (for example, "Red Devil". The details of preparation of the FB item may be stored (for example, in data store 18) against the chosen name or guest name or a combination of both for future referral or repeat ordering. For the need of saving the dish, the name of the FB item or the combination of guest name and FB item name has to be unique. In case such names are not unique, the application may chose to append random text to make it unique or suggest some other interesting names.

[072] Alternatively guest may be allowed to store any FB item (unique or not) against some unique identifier (for example the phone number of the guest) for future referral by the same guest. A stored FB item (designed by one user) may be made visible to other guests/users for their usage or ordering. The application may also allow the other user/guest or restaurant staff to publish the details of personal FB items on public portals or social networking sites. The application may also track reordering of such guest created FB items and may send congratulation messages to the creator if the FB items become quite popular.

[073] In one embodiment, a mechanism of competition is provided in which guests/users can take part by publishing their own designed personal FB items. Such published FB items are available for others to download from any restaurant or bar and order the same FB items and then can give feedback to the competition (for example, a rating or points). The user/guest whose FB item gets the best feedback (for example, best rating, maximum points, etc.) may be declared as the winner of the competition and may earn physical/virtual rewards.

[074] The manner in which the user interfaces described above and the corresponding enhanced user experience is provided is described below with examples.

[075] 4. Example Implementation

[076] FIG. 4A depicts an example implementation of the manual approach to satisfying an (user) order for a desired food/beverage item. Each of the blocks of the FIG. 4A is described in detail below.

[077] User Interface block provides the user interface to the overall system. It can be a touch-based or click-based or a combination. Container Selection block allows selection of a container and indicates the user through the user interface max volume of FB item that it can hold. It also can help user to understand how much max FB items it can hold including overflow situation. For example, for ice-cream, one can overflow easily without creating any problem. However, for liquids like cocktails, overflow may not be allowed.

[078] Liquid Handler block allows user to select one of the many liquid at a time and allows pouring of liquid into the container as needed. The Volumetric flow controller block offers flow control in volume measures including drops as needed for different item. As in cocktail kind of items where multiple liquids are mixed, the Fluid Dynamics Engine simulates the mixing of multiple liquid of different colors, textures, density. It also simulates the visual of mixing of liquids that are not really mixable e.g. water with oil.

[079] Solid Handler block allows user to select solid food items (e.g. scoop of ice-cream, sugar granules/cubes) or coloring agents which may be solid. This uses the dispenser functionality to pick up appropriate amount of the solid by weight or other measures. The solid-liquid interaction component then simulates the mixing of the solid (if mixable) in the liquid or show the position of the solid in the container if non-mixable.

[080] Taste Estimator block estimates the overall taste of the resultant FB item in approximate manner. Calories Estimator block calculates the overall calorific value of (the total number of calories in) the resultant FB item. Price Estimator block computes the prices/costs based of the overall FB item by simply adding cost of each individual item clubbed with design charge, container specific cost and other issues (e.g. taxation).

[081] Recipe Storing block allows guests to store recipes, that is, the constituents of the designed FB item along against some unique identity by collecting some user input and some system generated parameter. It also stores time/date of the creation and creators details (if provided by the user). Recipe Search Engine allows a user to search for a stored personal or other recipe and edit this recipe to personalize as desired. The search may be local (for example, only the recipes stored by a restaurant or bar) or global (for example, all the stored recipe in the database of the Social Competition Engine).

[082] Virtual Food Creator/Editor represents the central part of this system which allows creation of new FB item from scratch or editing of an existing item to personalize by a user by providing the interfaces of FIG.s 3A-3D. Transcript generator block is generates a human readable description of the recipe with detail description of steps/mechanism to prepare the personal FB items. It is contains multimedia instructions such that user designed FB items and the manually/automated prepared physical item are close in visual experience and taste.

[083] Social Publication engine allows users to upload created or personalized recipe in a social environment provided by the Social Competition Engine which then can be visible to public at large once they log into such social environment. Social Competition Engine stores all recipes which different users have published. A user can download recipe from the database of the component and consume the same in a restaurant. Upon completion of such consumption, the user can vote for such recipe. This component organizes a competition in regular intervals to reward the recipe creator in a virtual or physical manner. This component runs in the cloud environment allowing access from any restaurants by any user after registration through appropriate mechanism.

[084] FIG. 4B depicts an example implementation of an automated approach to satisfying an (user) order for a desired food/beverage item. Such an automated approach may be implemented in dispensing machine 17 of FIG. 1, for preparation of the personal FB items. The description is continued assuming that the instructions to prepare the personal FB items is provided to dispensing machine 17 in the form of a XML transcript. Each of the blocks of the FIG. 4B is described in detail below.

[085] Controller block represents the core logic layer of the Dispenser (e.g., dispensing machine 17) which make the over system works. This Controller component tightly works with the "XML Transcripts reader" to read each step and translates into actual actions needed for completion of the actual job described by the step. For example, a step may be to pick a scoop of ice-cream to be put inside a selected container which would need to select right ice-cream from the ice-creme bank which is part of "Solid Ingredient Bank".

[086] User Interface block expose all the human interactions needed to complete the job. When this automated dispenser is used in ice-cream parlor, this user interface is where the user interacts to create their choice of ice-cream. In full-fledged restaurant, this user interface may also be separated physically and may be presented in the hand of the guest who can design the ice-cream remotely. It is also possible that this remote user interface may be presented along with the local (attached to the machine) and may or may not have exactly same set of functionalities.

[087] Container Bank holds all the containers and comes attached with a temperature controller to keep containers in required temperatures. Container Selector block reads the XML instructions and select appropriate containers from the container bank and arrange to pick it and place it at the appropriate place. Robotic Hand works just not to pick up selected component from the bank but also optionally holds out the same when ready just that human can take it out. [088] Solid/Liquid Ingredient Bank block stores all the solid/liquid ingredients at appropriate temperatures with the help of the temperature controllers. For example, ice-creams are kept at very low temperature and sugar may be kept at normal temperature. Solid/Liquid Ingredient Selector selects the needed solid, semi-solid or liquid items including amount by weight/volume or other measures (e.g. ice-cream scoop, large shot). It then activates services of the Solid/Liquid Dispenser to deliver the right amount in the selected container. Solid Dispenser works along with the Solid Ingredient Selectors and deliver exact and required amount/weight of the selected solids. Similarly, Liquid Dispenser works along with the Liquid Ingredient Selectors and deliver exact and required amount/volume of the selected liquids.

[089] Decorative Ingredient Bank holds all the decorative items needed for decorating a FB item. Like other banks, this bank also has one or more temperature controllers needed to keep different items at different temperatures. Decoration Selection selects the needed decoration materials per the user choice of design. Manual Instruction block displays human readable/understandable information/instructions on the placement of the selected decoratives.

[090] As noted above, irrespective of the manual or automated approach, the personal FB item is prepared exactly in the user specified manner by generating a list of instructions (XML transcript) capturing the user specified combination of building blocks and constraints. FIG. 5 depicts sample portions of an XML transcript generated for capturing the manner of preparation of a personal food beverage item in one embodiment. It may be observed that the XML transcripts contains various tags such as "" indicating the name "Blue Angel" of the FB item, "" indicating the name/type of container to be used, "" indicating the liquids to be used in the personalized FB items, etc. [091] It should be appreciated that the above noted features can be implemented in various embodiments as a desired combination of one or more of hardware, execution modules and firmware. The description is continued with respect to one embodiment in which various features are operative when execution modules are executed.

[092] 5. Digital Processing System

[093] FIG. 6 is a block diagram illustrating the details of digital processing system 60 in which various aspects of the present invention are operative by execution of appropriate execution modules. Digital processing system 60 may correspond to one of client devices 1 la-11c or to FB server 15.

[094] Digital processing system 60 may contain one or more processors (such as a central processing unit (CPU) 61), random access memory (RAM) 62, secondary memory 63, graphics controller 66, display unit 67, network interface 68, and input interface 69. All the components except display unit 67 may communicate with each other over communication path 65 which may contain several buses as is well known in the relevant arts. The components of FIG. 6 are described below in further detail.

[095] CPU 61 may execute instructions stored in RAM 62 to provide several features of the present invention. CPU 61 may contain multiple processing units, with each processing unit potentially being designed for a specific task. Alternatively, CPU 610 may contain only a single general purpose processing unit. RAM 62 may receive instructions from secondary memory 63 using communication path 65.

[096] Graphics controller 66 generates display signals (e.g., in RGB format) to display unit 67 based on data/instructions received from CPU 61. Display unit 67 contains a display screen to display the images defined by the display signals (e.g. the portions of the user interfaces of FIG. 3A-3D). Input interface 69 may correspond to a keyboard and a pointing device (e.g., touch-pad, mouse), which enable the various inputs to be provided (such as the quality and/or quantity of the desired building blocks of the personal FB item using the user interfaces of FIG. 3A-3D).

[097] Network interface 68 provides connectivity to a network (e.g., using Internet Protocol), and may be used to communicate with other connected systems (e.g. client devices 11 a-lie, dispensing machine 17, FB server 15 of FIG. 1). Network interface 68 may provide such connectivity over a wire (in the case of TCP/IP based communication) or wirelessly (in the case of WIFI, Bluetooth based communication).

[098] Secondary memory 630 may contain hard drive 63a, flash memory 63b, and removable storage drive 63c. Secondary memory 63 may store the data (e.g., the XML transcript of FIG. 5, the various parameters of the building blocks) and software instructions (e.g., for implementing the programming logic of FIG. 2A-2C), which enable digital processing system 60 to provide several features in accordance with the present invention.

[099] Some or all of the data and instructions may be provided on removable storage unit 64, and the data and instructions may be read and provided by removable storage drive 63c to CPU 61. Floppy drive, magnetic tape drive, CD-ROM drive, DVD Drive, Flash memory, removable memory chip (PCMCIA Card, EPROM) are examples of such removable storage drive 63c.

[0100] Removable storage unit 64 may be implemented using storage format compatible with removable storage drive 63c such that removable storage drive 63c can read the data and instructions. Thus, removable storage unit 64 includes a computer readable storage medium having stored therein computer software (in the form of execution modules) and/or data.

[0101] However, the computer (or machine, in general) readable storage medium can be in other forms (e.g., non-removable, random access, etc.). These "computer program products" are means for providing execution modules to digital processing system 60. CPU 61 may retrieve the software instructions (forming the execution modules), and execute the instructions to provide various features of the present invention described above.

[0102] Reference throughout this specification to "one embodiment", "an embodiment", or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment", "in an embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0103] It should be understood that the figures and/or screen shots illustrated in the attachments highlighting the functionality and advantages of the present invention are presented for example purposes only. The present invention is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown in the accompanying figures.

I WE CLAIM:

1. A method of facilitating a user to order a personally designed food beverage item in a restaurant environment, said method being performed by a digital processing system comprising a processor and a memory, said method comprising:

providing on a visual interface, a plurality of building blocks for designing desired food/beverage items;

receiving from said user, a first combination of building blocks selected from said plurality of building blocks using said visual interface, wherein said first combination of building blocks corresponds to a desired food/beverage item; and

displaying a visualization of said desired food/beverage item based on said first combination of building blocks.

2. The method of claim 1, wherein said receiving also receives from said user one or more of a plurality of constraints, wherein said plurality of constraints comprises a corresponding quantity of each of said first combination of building blocks, a specific container in which said desired food/beverage item is to be served, a placement of at least some of said first combination of building blocks in said specific container, and an order in which a subset of said first combination of building blocks are to be added to said desired food/beverage item.

3. The method of claim 2, further comprising computing a plurality of characteristics based on said first combination of building blocks and said one or more of said plurality of constraints,

wherein said displaying also displays a plurality of characteristics of said desired food/beverage item in addition to said visualization.

4. The method of claim 3, wherein said plurality of characteristics comprises a resultant taste of said desired food/beverage item, an alcohol content of said desired food^everage item, a number of calories present in said desired food/beverage item and an expected cost of said desired food/beverage item.

5. The method of claim 1, further comprising:

placing, by said user, an order for said desired food/beverage item; generating a list of instructions capturing said first combination of building blocks and said one or more of said plurality of constraints; and

ensuring that said desired food beverage item is prepared according to said list of

instructions such that the prepared food/beverage item has a similar appearance to said visualization,

wherein said generating and said ensuring are performed in response to said placing of said order by said user.

6. The method of claim 5, wherein said ensuring comprises displaying to a person responsible for preparing said desired food/beverage item in response to said placing of said order, each of said list of instructions in a sequence such that a next instruction is displayed to said chef only after a previously displayed instruction has been completed.

7. The method of claim 5, wherein ensuring comprises providing said list of instructions in a machine readable format to an automated dispensing machine designed to prepare food/beverage items..

8. The method of claim 5, wherein said plurality of building blocks comprises one or more number and/or type of alcoholic drinks, non-alcoholic drinks, fruit juices, ice cube, crushed ice, spices, sugar, and salts, wherein said desired food/beverage item comprises a cocktail drink.

9. The method of claim 5, wherein said plurality of building blocks comprises one or more number and/or type of ice-creams, cut fruits, whole fruits, candies, chocolate, syrups, fruits pulps/juices, sodas, and other alcoholic or non-alcoholic tricks, wherein said desired food beverage item comprises an ice-cream based dessert.

10. The method of claim 1, wherein said digital processing system comprises a personal computational/communication device belonging to said user.