CN116917223A - Beverage Dispensing Prevention - Google Patents

Abstract

A system is provided, said system comprising a plurality of reusable portable beverage containers, said system further comprising at least one beverage dispensing station adapted to support one of the beverage containers and connected to the beverage container such that it can A beverage is dispensed from the container, the beverage dispensing station includes an identity tag reader configured to read an identity tag of the beverage container, the beverage dispensing station further includes a wireless network interface, the beverage dispensing station has an anti-dispensing device, the anti-dispensing device prevents A user dispenses a beverage from the dispenser, the system further comprising a server in communication with the beverage dispensing station, the server having stored a data set including the identity of each of a plurality of beverage containers, wherein the beverage containers may be tagged in the data set to activate the anti-dispensing device, and the system is configured to activate the anti-dispensing device of the dispensing station when the beverage container is marked to activate the beverage anti-dispensing device.

Description

Beverage Dispensing Prevention

Technical field

The present invention relates to beverage dispensing systems and methods, and more particularly to beverage dispensing systems and methods using individually traceable containers.

Background technique

Although most countries already have centralized water supplies ("tap water"), at least in densely populated areas, this water is often not suitable for human consumption. Instead, drinking water is produced centrally and packaged (bottled), and then a fleet of trucks or other vehicles is used to deliver single-use containers/bottles to stores (e.g. grocery stores) for sale. Grocery stores also offer other beverages besides water, such as beer and soda.

There are many disadvantages to this form. First, since people need to consume a large amount of drinking water, it is very troublesome to purchase and carry the necessary amount of drinking water (or other beverages). Furthermore, disposable containers need to be produced. After use, single-use containers can at best be recycled and used as fuel in waste incineration plants. In the worst-case scenario, single-use containers become part of an increasingly disturbing global waste problem.

Contents of the invention

According to a first aspect of the present invention, a system is provided, the system comprising:

a plurality of reusable portable beverage containers, wherein each of the plurality of beverage containers carries a unique identification tag,

The system also includes:

At least one beverage dispensing station adapted to support one of said beverage containers and connected to said beverage container such that a beverage can be dispensed from said container, said beverage dispensing station comprising a device configured to read a beverage container an identity tag reader for the identity tag, the beverage dispensing station further comprising a wireless network interface,

wherein said beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from said dispenser,

The system also includes a server in communication with the beverage dispensing station, the server having stored a data set including the identity of each of the plurality of beverage containers, wherein the beverage containers can be tagged in the data set to activate the anti-dispensing device, and the system is configured to activate the anti-dispensing device of the dispensing station when a beverage container is marked to activate the beverage anti-dispensing device.

The systems, devices, and methods described herein provide beverages in a reliable and safe manner. Production and delivery of beverages can be timed and fine-tuned to suit demand and consumption at an individual or group level. Beverage production can be fine-tuned to achieve a "virtual pipeline" of beverages.

Beverage production is not perfect and in rare cases may produce water that tastes bad or is slightly contaminated, or even water that is harmful to health.

It is known that the contents of a beverage container or set of beverage containers are not suitable for consumption and beverage dispensing devices can be used to prevent the end user from consuming the beverage.

The anti-dispensing device may be a light or audible warning signal to the user, or may prevent the beverage from being dispensed from the dispensing station. For example, when the dispensing station has a faucet, the anti-dispensing device may lock the faucet.

The identification tag may be a near field identification (NFC) tag.

According to a second aspect of the invention there is provided a beverage dispensing station adapted to support a portable beverage container and connected to the beverage container such that a beverage can be dispensed from the container, the beverage dispensing station comprising an identity tag reader configured to read an identity tag of the beverage container, the beverage dispensing station further comprising a wireless network interface,

wherein the beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from the dispenser, and wherein the dispensing station is configured to when receiving a signal from a server via the wireless network interface Activate the anti-dispensing device.

The tag reader is an NFC tag reader. The wireless communication interface may be a cell network interface, which may enable the beverage dispensing station to function as user equipment in a cell network.

According to a third aspect of the present invention, there is provided a method involving a system, the system comprising:

a plurality of reusable portable beverage containers, wherein each of the plurality of beverage containers carries a unique identification tag,

The system also includes:

a plurality of beverage dispensing stations adapted to support one of the beverage containers and connected to the beverage container such that beverages can be dispensed from the container, the beverage dispensing station including a beverage dispensing station configured to read the identity of the container tag identification tag reader, the beverage dispensing station also includes a wireless network interface,

The system also includes a server in communication with the beverage dispensing station, the server having stored a data set including an identity of each of the plurality of beverage containers, the identity of the beverage container being consistent with the identity of the beverage dispensing station. In association, wherein the beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from the dispenser, the method includes the following steps:

a) the server detects a flag for activating an anti-dispensing device for a beverage container in the data set,

b) the server identifies in the data set the dispensing station associated with the marked beverage container,

c) the server provides a signal to the distribution station identified in step b) to activate the anti-distribution device,

d) The distribution station activates the anti-dispensing device.

Description of the drawings

The accompanying drawings, which constitute a part of the specification, illustrate schematically preferred embodiments of the invention and serve to explain the principles of the invention.

Figure 1 is a schematic diagram of the system.

Figure 2 is a schematic diagram of the system.

Figures 3a and 3b are schematic diagrams of beverage containers.

Figure 4 shows a beverage container.

Figure 5 is a schematic diagram of a beverage dispensing station.

Figure 6 shows a beverage dispensing station.

Figure 7 is an inverted beverage container attached to the faucet of a beverage dispensing station.

Figure 8 is a beverage container supported and connected to a beverage dispensing station.

Figure 9 is a cross-sectional view of a beverage container and beverage dispensing station.

Figures 10-11 are schematic top views of a beverage dispensing station and beverage container.

Figure 12 is a schematic diagram of the components of the beverage dispensing station.

Figures 13-18 are flowcharts illustrating methods.

Figure 19 is a schematic diagram of the control circuit.

Detailed ways

The systems, methods and devices provided herein safely and reliably provide beverages at the point of consumption in a "virtual pipeline" manner. As a result, beverages can be produced and distributed to consumers in a safe and timely manner. Traceable containers and smart distribution stations allow high-level monitoring of System 1 and its various components.

Referring to Figure 1, a system 1 includes a plurality of beverage containers 2 and a server 3. The beverage container 2 is preferably reusable. The beverage container 2 is preferably portable. The beverage container 2 is preferably reusable and portable. System 1 may also include one or more beverage filling stations 4 , one or more identification tag readers 10 and one or more beverage dispensing stations 50 . Beverage dispensing station 50 may also be referred to herein as "dispensing station 50." The beverage dispensing station 50 is located, for example, in an end user's home, or in a restaurant, bar, school, hospital, office or other workplace, sports facility or other location where beverages may be served. Figure 1 also shows a cell network 16 and a wide area network 17, such as the Internet.

The system 1 may comprise at least one beverage filling station 4 configured to fill beverages into reusable beverage containers 2 . The beverage filling station 4 can thus have means for producing, storing and filling beverages in the containers 2 as well as means for cleaning and storing the containers 2 . Therefore, the beverage filling station 4 may comprise a beverage production unit. The beverage production unit may comprise a water purification unit 5 capable of purifying water using any suitable technology, such as filters, heating, UV light or chemical means. The beverage filling station 4 will be described in detail below. In various embodiments, system 1 may also receive prefilled containers 2 from an external source, and system 1 may further include beverage container storage 22 .

The beverage dispensed in system 1 is preferably water or beer. In various embodiments, the beverage is drinking water. In other embodiments, the beverage is beer.

Referring to Figure 2, the system 1 may comprise a plurality of beverage filling stations 4, for example two, three, four, five or more filling stations 4, as will be described in detail below. Each beverage container 2 can be logically associated in the data set 15 with a certain filling station 4, so that each filling station 4 has a "fleet" of beverage containers 2 and dispensing stations 50 (see below), such as As shown in Figure 2. Figure 2 is a schematic diagram showing how three different filling stations 4a, 4b, 4c are associated with a queue 70a, 70b, 70c of containers 2 and a separate queue 71a, 71b, 71c of the distribution station 50 respectively.

Referring to FIGS. 1 and 2 , the beverage filling station 4 may have a computer 19 in network communication with the server 3 . In various embodiments, the filling station 4 computer 19 provides information to the filling station user and enables the filling station user to monitor and manage his/her fleet of beverage containers 2 and the dispensing station 50 . Such users can only access certain functions of System 1.

Server 3 includes or has access to data set 15, which will be described in detail below. The server 3 may provide the computer 19 with instructions for beverage production and filling of the beverage into the container 2 . The server 3 can use the data set 15 to predict beverage consumption in the system 1 and use this prediction to provide instructions to the beverage filling station 4 as to how many beverages should be produced or how many filled beverage containers 2 should be produced. For example, when demand is predicted to increase, production can be increased. The server 3 may also include a pricing mechanism for determining the price of a filled beverage container 2 .

The system 1, such as the server 3, may comprise resources for ordering beverage containers 2, such as replacement of empty beverage containers 2, payment, booking of transport resources and pricing mechanisms. For example, an end user can log into system 1 using a user account and order beverage container 2 using a mobile device. Furthermore, the server 3 may include logic to automatically transport beverage containers 2 to the dispensing station 50 when required (beverage consumption tracking module).

The beverage is stored in the tank 6 of the beverage filling station 4 . The beverage filling station 4 may also include a tap 14 and one or more areas for storing beverage containers 2 . The beverage filling station 4 can also have a washing station 7 . The washing station 7 can be used for washing the beverage container 2 eg using hot water or detergent. Therefore, the washing station may comprise at least one sprayer for spraying hot water or detergent onto the beverage container 2 . A water purification unit 5 can be connected to the inlet 8 for obtaining non-purified water from some water supply system such as a lake, river or water utility. The filling station 4 and in particular the beverage filling station container 21 may have an inlet or a door (or both) to receive or eject the beverage container 2 . The beverage filling station 4 will be described in more detail at the end of the description.

In the filling station 4 , the beverage container 2 is filled with beverage. Preferably, the beverage container 2 is cleaned in the washing station 7 , preferably before filling the container 2 . The container 2 then leaves the filling station 4 for distribution to the end user.

The end user typically has one or more beverage dispensing stations 50. The beverage container 2 can be picked up by the end user at the filling station 4 or, more preferably, the container 2 can be delivered to the end user. In FIG. 1 , T represents the beverage container 2 transferred from the filling station 4 to the dispensing station 50 . W represents the beverage container 2 that has just left the washing station 7 . S represents a storage of filled beverage containers 2 awaiting transport to the end user (beverage dispensing station 50). The washing station 7 can be organized as a processing line in which the beverage containers 2 enter the filling station 4 , are washed in the washing station 7 and then leave the washing station 7 . The filling station 4 can thus have dedicated areas for storing the containers 2 , cleaning the containers 2 and filling the containers 2 . The washing station 7 can be fully automatic or semi-automatic.

As used herein, "end user" refers to the user who operates the beverage dispensing station 50. The end user can purchase the filled beverage container 2 or have the filled beverage container delivered to him/her. The end user can order filled beverage containers 2 .

"Server User" refers to a user who administers System 1 in some respect. Server users may access Server 3 or portions thereof using the user interface. Server users can have different permissions such that some server users have control over the entire system 1, whereas other server users have more limited access. Some users are only allowed to control one or some beverage filling stations (4a, 4b, 4c), as the system 1 may comprise more than one filling station 4, or a subset of beverage containers 2 (70a, 70b, 70c), or Subsets (71a, 71b, 71c) of beverage dispensing stations 50, see Figure 2.

The end user or server user can use a mobile phone, such as an iPhone, to send information to and receive information from the server 3 . A mobile phone (also referred to as a "mobile device" in this article) may, for example, be configured with an application program so that the mobile phone can communicate with the server 3 over the network. An example of a smartphone is the iPhone. The server may, for example, cause the message to be displayed on the display of the mobile phone.

Each reusable beverage container 2 in the system 1 has a unique identification tag 9 . The identity of the identification tag 9 is unique to each beverage container 2 . Of course, due to errors, there may be two or more containers 2 with the same identity, but the intention is that each beverage container 2 has a unique identity. Therefore, at least some of the plurality of beverage containers 2 have a unique identity. An identity can be a unique combination of symbols such as numbers or letters, such as numbers.

The tag reader 10 can read the identity stored in the identification tag 9 . Generally speaking, the identification tag reader 10 may be of various types and adapted to the type of identification tag 9 used for the beverage container 2 . For example, tag reader 10 may use induction to induce a current in the circuit of tag 9 so that tag 9 sends a signal that can be detected by tag reader 10 . Preferably, the identification tag 9 is an RFID tag, in particular of the type that can be read by means of NFC (Near Field Communication) technology. The unique identification tag 9 may be, for example, an RFID tag read by an RFID tag reader 10 . Alternatively, the identification tag 9 may be a barcode readable by a barcode reader. The identification tag 9 and the identification tag reader 10 may also be implemented using 5G technology, in which case the identification tag 9 includes a battery or other energy storage. Preferably, however, the identification tag does not include a battery.

Figures 3a and 3b are schematic views of the beverage container 2. Non-limiting examples of containers 2 made of stainless steel are shown in Figures 4 and 7-9.

The volume of the plurality of reusable beverage containers 2 is preferably from 2 to 100 liters, more preferably from 3 to 30 liters, even more preferably from 8 to 25 liters. When filled with beverages, the container 2 is preferably portable. For example, the container 2 has a handle 11 for carrying the container (Fig. 4). The container 2 is preferably made of metal, such as stainless steel or aluminum, or of a polymer material, such as plastic, for example polycarbonate, which may be reinforced, for example, with glass fibers or carbon fibres. However, stainless steel is the preferred material. Materials can be opaque. The container 2 may have any suitable shape, for example cylindrical.

Different suitable shapes and sizes could be the types of containers used in "water fountains" commonly found in office spaces and the like. Beverage containers 2 are generally not designed for direct drinking.

The container 2 should preferably be easy to clean and should preferably be lightweight and durable to allow multiple uses. For a single container 2, the number of cycles of use is preferably predicted to be between 10 and 1000 times, wherein each cycle consists of once filling the container 2 with at least some beverage and providing the container 2 to the end user. Therefore, the container 2 is preferably suitable for repeated filling and distribution to the end user.

The identification label 9 is attached to or otherwise included in the container 2 . For example, an NFC tag can be stuck on the container 2, or a barcode can be affixed to the outer surface of the container 2 in the form of an adhesive sticker. The label 9 can also be inserted into the container 2 during production, for example during the casting process of the container 2 made of polymer material.

The identification label 9 is preferably permanently attached to the container 2 . However, disposable labels or time-limited labels 9 may also be used.

The "permanent" attachment of the identification label 9 means that the identification label is intended to be attached to the beverage container 2 for the entire expected life of the beverage container.

The label 9 is preferably lightweight and small in size. The weight of the label 9 is preferably negligible compared to the weight of the container 2 . The same is true for the second tag 18 detailed below. The weight of the identification label 9 or the second label 18 is preferably less than 50 grams, even more preferably less than 10 grams, most preferably less than 1 gram.

The beverage container 2 has at least one opening 12 for filling and pouring the beverage. The opening 12 can be closed, for example, with a cover 13 . Cover 13 may be disposable or reusable. The beverage can be poured from the opening 12 which then serves as a spout. Alternatively, the beverage container 2 is connected to the beverage dispensing station 50 and the beverage is dispensed from the dispensing station 50, as described in more detail below.

System 1 includes a plurality of reusable beverage containers 2 . The number of beverage containers may be at least 100, preferably at least 1000.

The tag reader 10 is arranged to detect the identity tag 9 from a suitable distance. As mentioned, the tag reader 10 is preferably an RFID tag reader or an NFC tag reader, and thus includes suitable hardware known in the art. The tag reader 10 may be configured not to detect tags 9 beyond a certain distance, which may be 10m, preferably 5m, 1m or 20cm, more preferably 10cm, most preferably 5cm, even more preferably 2cm. Therefore, tag reader 10 may have detection distance limitations. By using directional antennas in the tag reader 10, the specificity of the tag reader 10 can be increased, as described in more detail below with reference to Figures 10 and 11.

For example, the dispensing station may have a directional antenna that directs the detection area 57 to the desired location of the beverage container 2 on the dispensing station.

System 1 may include at least two different tag readers 10 . The geographical locations of at least two tag readers 10 may be different, meaning that the two tag readers 10 are at least 20 meters apart, more preferably at least 100 meters apart. For example, a first tag reader 10 may be located at the filling station 4 or beverage container storage 22 , while a second tag reader may be located at the dispensing station 50 . For example, tag readers 10 may be present in distribution stations 50 at different geographical locations within a geographical area, such as a city, such as in different homes of an end user. Therefore, tag reader 10 may be located at a fixed geographic location. However, the tag reader 10 may also be carried by a truck or car used to distribute the beverage containers 2 or manually by a person involved in distributing the beverage containers 2 .

The geographical location is preferably a known geographical location. For example, the geographical location can be known by storing coordinates or addresses in the data set 15 . However, it is not necessary to know the geographical location. For example, the location may be obtained automatically by using positioning services (GPS), a known address of the end user from the client register in System 1, or by manually entering the location. For example, in the machine learning application of Figure 17, it may be sufficient to know the distances between various geographical locations, such as the distances between the beverage filling station 4 and the various beverage dispensing stations 50.

In various embodiments, one or more beverage dispensing stations 50 include at least one tag reader 10 . The tag reader 10 may be used by the system 1 to detect the presence of a beverage container 2 in one of the tag readers 10 , for example in one of the dispensing stations 50 . The tag reader 10 may be used in the system 1 to detect the presence of a beverage container 2 in, supported by, or connected to a certain dispensing station 50 .

The tag reader 10 communicates digitally with the server 3 . The system 1 can use the tag reader 10 to collect useful information about a certain beverage container 2 in the data set 15 . The information is at least that the beverage container 2 is present in the tag reader 10 . The system 1 may also use the tag reader 10 to record the status of a certain beverage container 2, for example whether the beverage container 2 is in a "cleaned" state, a "present in beverage station" state or similar. This state is preferably stored in data set 15.

The tag reader 10 is arranged for detecting the presence of a beverage container 2 in one of the tag readers 10 , for example at a beverage dispensing station 50 , and providing this information to the server 3 . This may preferably be stored in the data set 15 together with the detection time point.

The tag reader 10 is preferably part of the beverage dispensing station 50 , or is provided in the beverage filling station 4 , and the tag reader 10 can communicate with the server 3 using the hardware and software of those components. However, the tag reader 10 may also be independent of the filling station 4 or the beverage dispensing station 50 , for example the tag reader 10 may be present at a distribution center including the beverage container storage 22 , or in a vehicle or by It is carried by a person, for example a person dispensing beverage containers 2 . Each individual tag reader 10 may include a battery or other power source, a processor, memory, a wireless network interface, and control circuitry (Fig. 19), and may communicate with the server 3. A mobile phone with NFC function, such as an iPhone, can be used.

The filling station 4 may have one or more tag readers 10 . For example, the tag reader 10 may be located on a door frame of the beverage filling station 4 to detect movement in and out of the beverage filling station 4, particularly movement in and out of the beverage filling station container 21. As another example, the tag reader 10 may be located at the exit of the washing station 7 . All the various components of the beverage filling station 4 have dedicated workflows such that the beverage container 2 moves from one component to the next, e.g. into the filling station 4, through the washing station 7, to filling at the tap 14 is filled, stored and then leaves the filling station 4, and the tag reader 10 is arranged to detect the presence of the container 2 in the various stations or in the area of the beverage filling station 4.

The tag reader 10 may for example be arranged such that it detects when the beverage container 2 leaves the washing station 7 and is therefore considered clean. For example, when the tag 9 is an NFC tag, the tag reader 10 is an NFC reader at a suitable distance from the exit of the washing station 7 so that the beverage container 2 (and not other beverage containers 2) that has been cleaned passes through the washing station. 7 is detected when exiting. A similar setup applies when tag reader 10 is placed in system 1 . Therefore, a tag reader 10 is placed in the system 1 to ensure that the detected status can be determined to a certain extent.

Accordingly, one or more tag readers 10 may be provided to detect beverage containers 2 as they pass through various components of the system 1 and provide data relating thereto to the server 3 which may This information is stored in dataset 15. The server 3 receives information from the tag reader 10 and uses said information to change the status of the individual beverage containers 2 in the data set 15 .

The server 3 may combine information from the tag readers 10 (eg the identity of the beverage container 2) with predetermined information associated with a certain tag reader 10. For example, an identity read from a certain tag reader 10 can always determine a certain predetermined status of the container 2 . For example, the identity read from a certain tag reader 10 can change the status of container 2 from "uncleaned" to "cleaned", or from "in station" to "out of station" ("uncleaned"). ” may also be referred to as “Entered Station”), as detailed below.

Therefore, tag reader 10 may have an identity in system 1 . When a tag reader is part of a distribution station 50, the identity of the tag reader is preferably the same as that of the distribution station.

For example, when tag reader 10 detects tag 9 of beverage container 2, server 3 will set the status of beverage container 2 in data set 15 to one of the following states:

a) Container 2 has entered the beverage filling station 4, in particular beverage filling station container 21,

b) Container 2 has been cleaned,

c) Container 2 has been filled with beverage at beverage filling station 4,

d) the container 2 has left the beverage filling station 4, in particular the beverage filling station container 21,

e) Container 2 is being delivered,

f) Container 2 has followed the end user of the beverage dispensing station 50,

g) Container 2 is present at beverage dispensing station 50,

h) Container 2 is not present at any beverage dispensing station 50 .

States can be exclusive, such that a single container 2 can only have one state at a time. For example, container 2 cannot be present in beverage dispensing station 50 , or in any beverage dispensing station 50 . This can be provided using logic in Server 3 (e.g. dataset logic). Error detection logic can be set up in Server 3 to detect erroneous state transitions.

The first tag reader 9 can detect a first state selected from a) to h), and the second tag reader 9 can detect a second state selected from b) to h). Select in step. The first tag reader and the second tag reader can provide this information to the server 3 .

The tag reader 10 can read multiple tags 9 simultaneously or within a short period of time. For example, if a truck is loaded with multiple beverage containers 2, the RFID tag reader 10 can be set up to read the tags 9 of all beverage containers 2 in the truck when the truck passes the RFID tag reader 10.

Turning to Figure 1, system 1 includes server 3. As discussed below, Server 3 may be a virtual server. The server 3 maintains or includes a digitally stored data set 15, which may be in the form of a database. Any suitable form of database schema may be used, such as a SQL database. The identity of each beverage container 2 is stored in the data set 15 . The data set 15 may hold information specific to an individual beverage container 2, such as information on when the container 2 was put into service in the system 1, number of filling cycles, date of production, manufacturing information, etc. This information is associated with the identity of the beverage container 2 . The data set 15 may also include information related to the current status of the beverage container 3, such as the information recorded in the tag reader 10 described above.

The server user can also add container 2 to the database and then logically associate container 2 with a specific filling station 4. Information can also be automatically entered into the data set 15, for example if a certain beverage container 2 is damaged and/or must be taken out of service.

The server 3 is therefore configured to store data relating to a plurality of reusable beverage containers 2 in a digitally stored data set 15 . Preferably, the server 3 may also be configured to store data related to a plurality of distribution stations 50 in the data set 15 .

Server 3 includes suitable logic components and software to implement the methods described herein, such as, but not limited to: beverage consumption tracking module, beverage container tracking module, error detection logic, container error flagging module, anti-dispensing device activation module, beverage production Control logic, database interface, network interface and operating system.

For example, the following information may be associated with the identity of certain beverage containers 2 in the data set 15 (some of which will be explained in detail below): type of beverage, beverage containers 2 that have been filled, amount of beverage remaining in the beverage container 2 , number of filling cycles, production date, current location, information that the beverage in container 2 should not be consumed, identity of the second tag 18 (tampered tag), status of the second tag 18, container 2 has entered the beverage filling station 4 , container 2 has been cleaned in the beverage filling station 4, container 2 has been filled with beverage at the beverage filling station 4, container 2 has left the beverage filling station 4, container 2 is being distributed, container 2 has followed the beverage distribution The user of the station 50 leaves, the container 2 is present in the beverage dispensing station 50, the identity of the filling station 4 to which the beverage container 2 belongs, the container 2 is not present in any beverage dispensing station 4, the previous dispensing station associated with the beverage container 2 50’s identity, the date of a previous filling cycle, the date and time of a tag read, beverage dispensing events, weight data, or beverage consumption data. These are non-limiting examples.

For example, the following information may be associated with the identity of the dispensing station 50 in the data set 15: the identity of the current beverage container 2 present in the dispensing station 50, the absence of a beverage container 2, sensor data, temperature sensor data, weight data, or Beverage consumption data, communication records, flags that have not changed since the last communication session, anti-dispensing device 65 to be activated, anti-dispensing device 65 already activated, error messages, battery status, beverage dispensing events, sensor data, associated with the dispensing station 50 The identity of the associated filling station 4, the identity and contact information of the end user, the end user’s login details, order status, etc. These are non-limiting examples.

Details of the communication processing between the server 3 and the mobile phone of the end user associated with the beverage dispensing station 50 may also be included in the data set. This can also be used by Server 3 to push information to end users of specific beverage dispensing stations. The information may include shipping information, weight data or beverage consumption data, how much beverage is still present in the beverage container 2, or a message that the contents of a certain beverage container 2 should not be consumed.

All data of previous events can be stored, so that the history of each beverage container 2 and dispensing station 50 is stored in the data set 15 .

The server 3 may include logic to detect errors regarding the beverage container 2 or the beverage dispensing station. Therefore, a single beverage container 2 cannot directly change the status from "not cleaned" to "filled". Such a change (change from "Uncleaned" to "Filled") is only possible when container 2 has changed from "Uncleaned" status to "Cleaned" status. If the tag reader 9 provides such conflicting information, an error exists. This error may be detected by software in server 3, for example by database software. Database software may, for example, be adapted to generate error flags. Errors can be detected through other means, such as through the machine learning method in Figure 17. An error related to container 2 may result in an error being reported by server 3, or may result in container 2 being excluded from delivery. For example, exclusions can be performed such that a certain container 2 is marked not to be filled or distributed to the end user. The warning may be provided as an audible signal, or in a display or flashing light in the filling station 4, to provide a message to the end user or server user, or to activate the anti-dispensing device 65 (see below).

Referring to Figures 1-2 and 5-11, system 1 preferably includes one or more beverage dispensing stations 50. The dispensing station 50 is used for dispensing beverages from beverage containers 2 .

Beverage dispensing station 50 can be designed in a number of different ways. The beverage dispensing station 50 in Figures 6 to 9 includes a separate housing 51 supporting a beverage container 2 placed on top of the housing 51 with its opening 12 pointing downwards. A separate faucet 52 is attached to the opening 12 and is used to control dispensing by the end user. Beverages can be dispensed using gravity flow. Faucet 52 includes a valve (not shown), a handle 66 for operating the valve, and a connector 54. Faucet 52 may physically interact with housing 51 . For example, as shown in FIG. 8 , the faucet 52 is placed in the V-shaped notch 53 of the housing 51 . Again, this is just an example and the faucet 52 may be integrated with the housing 51 as well. In general, the faucet 52 of the beverage dispensing station 50 may be operated by any suitable means, such as using a push button, or any other suitable device for controlling a valve. Faucet 52 may, for example, include an electronically controlled valve for dispensing beverages.

Generally speaking, the housing 51 may include a control circuit and various sensors, such as a weight determination device 55, an accelerometer 56, a battery 63, an LED light 64, and a wireless network interface 58 described below.

The distribution station 50 can be designed in numerous ways. Other possible designs include something similar to the "water fountain" often seen in office workplaces.

The dispensing station 50 may be adapted to stand on a bar, table or countertop, or the dispensing station 50 may be designed to be free standing on the floor or ground. The beverage dispensing station 50 can also be integrated into furniture, particularly suitable for kitchens, restaurants and bars. The dispensing station 50 can also be integrated in the refrigerator.

The beverage can be dispensed from the dispensing station 50 as a flowing beverage by using gravity flow or by providing pressure within the container 2 . Figures 6-9 illustrate a beverage dispensing station 50 adapted to dispense beverages with gravity flow. Beverage is preferably dispensed from the beverage container 2 when mechanically connected to the beverage dispensing station 50 or when supported by the beverage dispensing station 50 .

When pressure is used, as is the case with beer, the dispensing station 50 may include means known in the art for pressurizing the beverage container 2 . Typically, the beverage dispensing station 50 then includes means for supplying pressurized carbon dioxide (other inert gas) into the beverage container 2 . The means for providing carbon dioxide may comprise a first conduit inserted into the container 2 and providing pressurized carbon dioxide to expel the beverage from the container 2 from a second conduit. The dispensing station 50 for beer can be designed so that the opening 12 of the container 2 points upward, and the dispensing station 50 or a part thereof can be designed to be placed on top of the container 2 . In particular, connectors for the pipes and means for supplying carbon dioxide may be placed on top of the opening 12 .

The valve may allow ambient air to flow into the beverage container 2 when gravity flow is used to dispense the beverage.

The dispensing station 50 may be configured to mechanically support the beverage container 2 . Therefore, part or all of the weight of the beverage container 2 rests on the dispensing station 50 . The dispensing station 50 or a part thereof may be configured to mechanically receive the beverage container 2 . The beverage container 2 may be mechanically connected to the dispensing station 50, such as by using lugs, bayonet fittings, click or threads, or other connection means. The dispensing station 50 is engageable with the beverage container 2 . Preferably, the dispensing station 50 is such that only one beverage container 2 is supported by or connected to the beverage dispensing station 50 . Therefore, preferably the beverage dispensing station can be mechanically supported, mechanically received or mechanically connected to, or engaged with, an individual beverage container 2 .

The container 2 can be mechanically connected to the dispensing station 50 so that beverage can be dispensed from the container 2 . Beverages are preferably dispensed through a portion of the dispensing station 50 . For example, the dispensing station 50 may have a connector 54 connected to the opening 12 of the beverage container 2 .

The system 1 preferably includes a plurality of distribution stations 50, such as two, three, four or more distribution stations 50, such as at least ten or at least 100 distribution stations 50. Each distribution station 50 may have a unique identity within system 1 . This identity is stored in dataset 15. For example, in data set 15, the beverage dispensing station 50 may be logically connected to a specific beverage filling station 4, as shown in Figure 2. This logical connection can be in data set 15.

The beverage containers 2 can be switched such that a first beverage container 2 mechanically connected to or supported by the dispensing station 50 can be replaced by a second beverage container 2 which, after replacement, becomes mechanically Ground is connected to the distribution station 50 or is supported by the distribution station 50 .

Referring to FIG. 12 , the beverage dispensing station 50 has or includes control circuitry including a memory 60 , a processor 61 and a bus 62 . The control circuit may be partially provided in a printed circuit board (PCB). The control circuit is electrically connected to the various sensors, tag reader 10, wireless communication interface 58, battery 63, LED 64 and anti-dispensing device 65. Control circuitry may include timers and alarm clocks. Memory 60 stores software for participating in or performing the various methods described herein.

In addition, the distribution station 50 also includes a battery 63 for powering various electrical and electronic components of the distribution station 50, such as control circuitry, sensors, wireless network interface 58, tag reader 10, and Dispensing device 65. Power may also or alternatively be supplied by a connector and a conventional power socket.

Beverage dispensing station 50 preferably has one or more sensors. The sensor of the beverage dispensing station 50 may be, for example, a weight determination device 55, an accelerometer 56 or a beverage flow sensor. In a preferred embodiment, the dispensing station 50 has at least a weight determination device 55 and an accelerometer 56 .

The beverage dispensing station 50 has at least two sensors, wherein a first sensor is capable of waking the control circuit from a sleep state to a wake-up state, and a second sensor is capable of determining the amount of beverage consumed. The first type of sensor is able to wake up the processor 61 using the interrupt pin of the processor 61 by providing a signal to the interrupt pin of the processor 61 . In a preferred embodiment, the second sensor is weight determining device 55 . In a preferred embodiment, the first sensor is an accelerometer 56 and the second sensor is a weight determining device 55 .

In one embodiment, the first sensor is a sensor capable of detecting the presence of a person, such as a proximity sensor. For example, the sensor can detect people approaching the beverage dispensing station 50. The detection threshold distance may be, for example, 0.25-1 meter. Examples of such sensors include proximity sensors or inductive presence sensors based on infrared light (IR) detection.

Turning to FIGS. 5-12 , the distribution station 50 preferably has a tag reader 10 . The tag reader 10 is arranged to detect the identity of the beverage container 2 present at the beverage dispensing station 50 . Preferably, the tag reader 10 is arranged to detect a beverage container 2 supported by or mechanically connected to the dispensing station 50 . Preferably, the tag reader 10 of the dispensing station 50 only detects a tag for a particular beverage container 2 if the beverage container 2 is supported by or mechanically connected to the dispensing station 50 such that a beverage can be dispensed from the dispensing station 50 .

The tag reader in Figures 10 and 11 shows how the tag reader 10 is arranged in a beverage dispensing station 50 (shown schematically from above) and detects only the beverage containers 2 supported by the dispensing station 50. Two different examples. In Figures 10 and 11, a beverage container 50 is placed on a dispensing station 50.

For example, the tag reader 10 may be an NFC tag reader 10 that reads at a short distance and in a certain direction, forming a detection field 57 directed toward the location of the beverage container 2 on the dispensing station 50 , see FIG. 10 . Tags 9 outside the detection field 57 are not detected by the tag reader 10 . The detection range of the tag reader 10 of Figure 11 is smaller and the tag 9 is only detected when the beverage container 2 is oriented in the correct way so that the tag 9 faces the tag reader 10. This can be achieved by an directional fit between the beverage container 2 and the dispensing station 50 . For example, correct orientation can be achieved by keying between the beverage container 2 and the dispensing station 50 . The settings of Figures 10 and 11 are examples only.

The tag reader 10 may be activated in various ways via the control circuitry of the distribution station 50 . For example, the tag reader 10 may read the tag 9 of the beverage container 2 at least every predetermined period of time, such as at least every 5 seconds, at least every hour, or every day. As described herein, the tag reader 10 may also be activated by various means, such as by an accelerometer 56 or a weight determination device 55 .

Furthermore, if the weight determination device 55 detects the weight but cannot detect the label 9, this indicates that the wrong beverage container 2 is being supported by the dispensing station 50. If this situation occurs, the beverage dispensing station 50 can report this situation to the server 3. This information may be stored in the data set 15 in association with the identity of the beverage dispensing station. The beverage anti-dispensing device 65 can be activated or a message can be sent to the end user's mobile phone.

The beverage dispensing station 50 may be in data communication with the server 3, preferably using at least partially wireless data communication. The distribution station 50 therefore has a wireless communication interface 58 . Wireless data communications may preferably be provided by a distribution station 50 acting as a user equipment in a cell network 16, such as a 3G, 4G or 5G cell network 16. However, other standards such as LoRa may also be used. Therefore, the distribution station 50 may have an antenna as part of the wireless network interface 58, suitable for cell network communications, particularly for acting as user equipment. The beverage dispensing station 50 may provide data from the sensors to the server 3, for example from the tag reader 10, the weight determination device 55, the accelerometer 56, the temperature sensor, using a data connection, in particular the wireless network interface 58, as described below. 59 or flow sensor provided to server 3.

The control circuit of the distribution station 50 can have a sleep state and a wake-up state, wherein in the sleep state the energy consumption is preferably particularly low. The energy consumption in the sleeping state may be up to 30%, more preferably up to 10%, of the energy consumption in the waking state. The control circuit can be awakened from the sleep state by means of a sensor, in particular a first sensor, for example. The control circuitry enters the sleep state after a period of inactivity, for example, after more than 15 minutes of inactivity. The control circuitry of the dispensing station 50 may be configured to wake from the sleep state when a dispensing is detected by, for example, the accelerometer 56 or the weight determination device 55 . The weight determination device 55 can be connected to an amplifier which amplifies the signal for this purpose. The first sensor can be connected to an amplifier which amplifies the signal for this purpose.

FIG. 13 depicts a communication session between the dispensing station 50 and the server 3 involving the reading of the tag 9 of the beverage container 2 by the tag reader 10 . The tag reader 10 as part of the filling station 4 or as a stand-alone tag reader 10 performs a communication session with the server 3 in a similar manner. In step 100 , the tag reader 10 , in particular the tag reader of the dispensing station 50 , detects the tag 9 of the individual beverage container 2 . This involves reading the identity of the tag 9 which is also the identity of the beverage container 2 . Said identity is preferably stored in the memory 60 of the distribution station 50 together with the time point of detection. Preferably, other sensor data may also be determined and stored, such as data from the weight determination device 55 or the accelerometer 56, as described below. Step 100 may be initiated by, for example, a first sensor (eg, accelerometer 56 or weight determination device 55) that wakes the control circuitry of the dispensing station 50 from a sleep state or otherwise provides the control circuitry with the tag read. The signal of the tag 9 being read by the device 10. Step 100 may also be initiated by an end user interacting with the beverage dispensing station 50, such as by turning on the beverage dispensing station using an on-off switch.

In step 101, the identity of container 2 is provided to server 3. Preferably, the beverage dispensing station 50 uses the wireless network interface 58 to establish the data connection with the server 3 . Preferably, the identity of the distribution station 50 is also provided to the server 3 . Communications can be encrypted.

In step 102 the data is stored in the data set 15 and is associated in the data set 15 with the identity of the appropriate beverage container 2 and preferably with the appropriate dispensing station 50 . Preferably, the identity of the beverage container 2 is associated with the identity of the distribution station 50 in the data collection. The server 3 can then verify the identity of the beverage container 2 . For example, the beverage container identity exists in data set 15 and does not exist in any other beverage dispensing station 50 . If an error is detected, an error message may be sent to the server user or end user, or the anti-allocation device 65 may be activated, as described below.

The data may also include messages from the distribution station 50 indicating that the distribution station 50 is operating as expected. This check may be performed by the control circuitry of the beverage dispensing station 50 upon wake-up or on schedule. In one embodiment, the data passed includes the identity of the dispensing station 50, the identity of the beverage container 2 and the system confirmation message. This may be provided, for example, as a text message (SMS message) from the beverage dispensing station 50 .

The communication session between the distribution station 50 and the server 3 may include one or more of the following: identity of the distribution station 50, identity of the current container 2, battery status, dispensing events, weight, consumption data, other sensor data (such as from accelerometer data), temperature data, or a message indicating that nothing has changed since the last session. "No changes" messages are an effective way to save data traffic and power. Sensor data such as accelerometer data, temperature data or data from the weight determination device 55 may be associated with the detection time point stored in the memory 60 of the beverage dispensing station 50 and thus also included in the data communication session.

Communication between distribution station 50 and server 3 may occur on any suitable schedule. For example, distribution station 50 may be configured to connect to server 3 at least every predetermined time interval (eg, at least every few seconds, hourly, daily, or weekly).

Table 1 below shows a highly simplified schematic example of a data set 15 showing the identities of three different containers 2 and three different distribution stations 50 . As described herein, data set 15 may include many other types of data that are omitted in this example. Table 1 shows how the same table is used for the beverage container 2 and the beverage dispensing station 50, but of course two or more tables that are cross-referenced may be used as the data set 15 may be structured in any suitable way.

Table 1

In the data set of Table 1, beverage container 2 with identity 5647 is associated with beverage dispensing station 50 with identity 2354. Beverage container 2 with identity 2355 is an example of a beverage dispensing station 50 that currently does not have a beverage container 2 . Beverage container 1002 is an example of a beverage container 2 that is not currently associated with any beverage dispensing station 50 .

In various embodiments, distribution station 50 has an accelerometer 56 . Accelerometer 56 may be any type of useful accelerometer. The accelerometer may, for example, be of the type used in mobile phones such as the iPhone. The accelerometer 6 can detect dispensing or movement of the dispensing station, such as a shock or vibration, or a change in orientation or impact, such as if the dispensing station 50 is dropped from a table to the floor. The accelerometer 56 can also detect tampering issues. An accelerometer reading above a certain threshold may indicate an impact due to the drop of the distribution station 50 . Such accelerometer readings may trigger self-testing of the distribution station 50 and may also trigger reporting to the server 3 . The accelerometer 56 may have a threshold for detecting movement such that background movement such as traffic does not trigger a signal from the accelerometer 56 .

A signal from the accelerometer 56, for example a signal sent to an interrupt pin on the processor 61 of the control circuit, may be used to wake the control circuit from a sleep state. The signal from the accelerometer 56 may be used to activate the wireless network interface 58 or to activate the weight determination device 55 .

The signal from accelerometer 56 may be configured to cause tag reader 10 to read tag 9, such as shown in steps 100-102 in Figure 13. The accelerometer 56 provides a signal to the control circuit, which in turn activates the tag reader 10 which in step 100 reads the tag 9 of the beverage container and stores the identity at the beverage dispensing station 50 in the memory 60 of the control circuit. For example, this can be used to detect whether the beverage container 2 has been replaced. A slight vibration of the dispenser during replacement activates the accelerometer 56. If the beverage container 2 has been replaced, the identity of the new container 2 read by the tag reader 10 is associated with the identity of the beverage dispensing station 50 in the data set 15 . The identities of previous beverage containers 2 associated with a particular dispensing station 50 in the data set 15 may be discarded.

The accelerometer data may preferably be stored in the memory 60 of the distribution station 50 together with the detection time point.

In various embodiments, the dispensing station 50 has weight determining means 55 for determining the weight of the beverage container 2 supported by the dispensing station 50 . The weight determining device 55 may be of any suitable type. For example, strain gauge types or load cells can be used. Any suitable type of weight sensor may be used. For example, a metal beam supporting a beverage container 2 is equipped with strain gauges, which typically detect strain in the beam using elongated conductive elements that change their electrical resistance when bent. The elongated conductive element is usually oriented so that the weight of the beverage container 2 acts perpendicularly to the elongated axis of the strain gauge. The weight determining device 55 may alternatively comprise a piezoelectric crystal which provides a voltage when a change in mass provides a change in stress in the crystal.

The weight determination device 55 can be used to determine the amount of beverage in the container 2 . This information can be used by server 3 to determine when to replace container 2. For example, when the weight of the beverage container 2 supported by the dispensing station 50 is below a threshold weight, the newly filled container 2 is automatically transported to the user of the dispensing station 50 . The server 3 may include logic (beverage consumption tracking module) that compares the current filling level (weight) of the beverage container 2 with a threshold weight and automatically provides the order to the filling station when the weight is below the threshold weight 4 to produce and ship new beverage containers2.

Consumption information at dispensing stations 50 may also be used in an aggregated manner to track beverage consumption from multiple dispensing stations 50 . For example, the consumption of a subset 70a of distribution stations 50 may be compared to the consumption of a different subset 70b of distribution stations 50 (as shown in Figure 2). Subsets can be selected based on geographic location, demographics, etc. This information can be used to make decisions in the server 3 regarding the production of the beverage in the beverage filling station 4 .

Beverage consumption data or weight data may also be used as described elsewhere herein (eg regarding machine learning, see below). It should be noted that a flow meter in the beverage dispensing station can be used instead of the weight determining device 55.

Beverage consumption can be determined via a control circuit in the dispensing station 50 or via the server 3 . For example, the distribution station 50 provides weight data to the server 3 which calculates consumption. Generally speaking, the weight after the most recent dispensing event is subtracted from the weight after the previous dispensing event to get the weight difference. The difference is used as the drink consumption for the dispensing event. Alternatively, the distribution station 50 performs calculations and provides consumption data to the server 3 . Alternatively, the distribution station 50 only reports weights below a threshold weight. The weight data can be filtered so that only differences above a certain threshold are used, thereby filtering out the noise. This may be an advantage if the consumption or filling level is determined by the dispensing station 50 rather than the server 3, to reduce data traffic in the system 1 and data processing by the server 3.

Below is an example of beverage consumption calculation.

Initial total weight: 11kg

Smaller tare weight: (container may be unscrewed, as shown in Figure 7): 1kg

Weight after peeling: 10kg

First measurement: 9.8kg

First consumption: 0.2kg.

The tare weight may be pre-stored in the memory 60 of the beverage dispensing station 50 . The use of tare weight is optional and is not necessary if it can be assumed that the initial weight is known, for example from the filling station 4.

Temperature data from temperature sensor 59 may be used to calibrate weight determining device 55 . This can be done in the beverage dispensing station 50 or in the server 3 . The server 3 may receive the temperature read from the beverage dispensing station 50 and use the temperature to correct or calibrate the weight value or beverage consumption data. Temperature data can be provided along with weight data or beverage consumption data.

Thus, the server 3 may be provided with weight data, such as weight data, the amount of beverage remaining in the container 2 , the amount of beverage dispensed, or data that a weight below a threshold weight has passed, or data that triggers the delivery of a new container 2 . All of these are referred to herein as "weight data or beverage consumption data".

The weight determining device 55 may be configured to determine the weight at least every predetermined time interval. For example, the weight determining device 55 may be configured to determine the weight at least weekly, daily, hourly, minutely, or every second.

Dispensing station 50 may be configured to determine weight or consumption at the time of dispensing. Dispensing may be detected using a separate sensor, such as a flow sensor, or a mechanical switch that detects the position of the faucet 52. In a preferred embodiment, accelerometer 56 may be used to detect dispensing. Therefore, the signal from the accelerometer can activate the weight determination device 55 . The first sensor can also activate the weight determination device 55 .

The accelerometer 56 is preferably provided in the dispensing station 50 such that dispensing a beverage from the beverage container 2 activates the accelerometer 56 . The signal from the accelerometer 56 may be used to wake up the control circuit to activate the weight determining device 55, for example by activating the weight determining device 55 using an interrupt pin on the processor 61 of the control circuit. The accelerometer 56 may, for example, detect movement of the beverage dispensing station 50, beverage flow, movement of the faucet 52 or bucket detector. In a preferred embodiment, the accelerometer 56 detects movement of the dispensing station 50 itself, or of a beverage container 2 attached to or supported by the dispensing station 50 . For example, an accelerometer 56 may be attached to the housing 51 to detect vibration or movement of the housing 51 indicative of dispensing.

System 1 may be configured to determine allocation events. A “dispensing event” includes at least information regarding the amount of beverage dispensed by a certain beverage container 2 currently supported by or connected to the beverage dispensing station 50 or weight data of the beverage container 2 Stand 50. The presence of the beverage container 2 in the beverage dispensing station is detectable by the tag reader 10 of the beverage dispensing station 10 . A weight determination device 55 or a flow meter may be used to determine a "dispensing event". Dispensing events may be stored in the memory 60 of the control circuit of the distribution station 50 . Allocation events can be stored with allocation time points. Assigning events can trigger timers.

It should be noted that "detecting an assignment" herein means that an assignment occurs or may occur and is detectable, for example, by the accelerometer 56, and does not necessarily equate to a "dispensing event."

The weight data or beverage consumption data may be provided to the server 3 from the dispensing station 50 at any suitable intervals, such as at least every predetermined time interval, such as at least weekly, daily, hourly or minutely. This is an advantage if as little communication as possible is required to save the battery 63 of the distribution station 50 and to keep data traffic to a minimum.

In a preferred embodiment, the weight determining device 55 is activated by a first sensor. The distribution station 50 may be configured to activate the weight determination device 55 after a predetermined waiting time. The predetermined time is more preferably at least 10 seconds, even more preferably at least 1 minute, even more preferably at least 5 minutes. Therefore, the wake-up of the control circuit can start the timer. This may be advantageous because the weight determining device 55 preferably determines the weight of the beverage container 2 once dispensing is completed, which may only take a few seconds to complete. Additionally, to reduce data processing in System 1, it may be desirable to store dispenses to two or more glasses as one dispense event.

The beverage dispensing station 50 may further be configured to establish a data connection and provide weight data or consumption data to the server 3 after waking up, preferably after a predetermined waiting time after waking up. The waiting time may be calculated from the wake-up control circuit or from the determination by the weight determination device 55 and may for example be at least 10 seconds, even more preferably at least 1 minute, even more preferably at least 5 minutes. Therefore, waking up the control circuit or determining the weight by the weight determining means may start the timer.

Weight data or beverage consumption data may preferably be provided to the server 3 together with the identity of the beverage container 2 . Weight data or beverage consumption data may preferably be provided to the server 3 together with the identity of the dispensing station 50 . The dispensing station 50 may be configured to activate the tag reader 10 and read the beverage container 2 every time the control circuit wakes up from sleep, every time a dispensing event occurs or every time a weight is determined, or every time a communication session takes place. Label 9.

Figure 14 illustrates a method involving a beverage dispensing station 50. It should be noted that this method illustrates specific embodiments, and the steps of Figure 14 may include various specific embodiments of the present disclosure, and the various embodiments may be combined together in a suitable manner. For example, the first waiting step and the second waiting step are separate embodiments. Furthermore, it should be noted that the tag reader 10 can be activated in any of the steps 201 to 204 to read the tag 9 of the beverage container 2 . The control circuit may also perform other checks on the circuit of the distribution station 50, such as checking battery status, detecting temperature, etc. in any of steps 201 to 204.

In optional step 201, the first sensor wakes the control circuit from sleep. The first sensor is preferably the accelerometer 56 which detects movement in step 200 .

202 is an optional first waiting step for the allocation to complete. As described herein, the control circuit may have a timer. The predetermined time may be at least 10 seconds, more preferably at least one minute, even more preferably at least 5 minutes after detection of allocation or wake-up. A longer wait time ensures that the allocation has been completed and can also be used to catch allocations made by the second person, which saves energy and computing power. However, it may be useful to have shorter wait times to have more granularity in distributing data.

In step 203 , the control circuit activates a second sensor, preferably the weight determination device 55 . The weight of the beverage container 2 is determined and stored, and preferably the beverage consumption is calculated and stored in the memory 60 . Weight or consumption data can be stored as beverage dispensing events. The event can be stored together with the assigned time point. The second sensor may also be a flow sensor, in which case the first waiting step 202 is preferably ignored.

Step 204 is an optional second waiting step. During step 204, any additional consumption events are stored in memory 60. For example, additional dispensing events can be detected by the accelerometer 56 , which again activates the weight determination device 55 . The waiting period is more preferably at least 10 seconds, even more preferably at least 1 minute, even more preferably at least 5 minutes.

In step 205, the control circuit provides beverage consumption data or weight data to the server 3. Therefore, any previously unreported allocation events may be reported to server 3. Other data may also be provided to the server 3, such as the identity of the beverage container 2, the identity of the dispensing station 50 or other sensor data. In the same session, other data can be transmitted to the server 3, such as temperature, battery status, system confirmation messages, etc. related to the beverage dispensing station. Server 3 stores data in data set 15. During the communication session, the beverage dispensing station 50 may also receive information from the server 3, such as activation of the anti-dispensing device 65, software updates, etc. The wireless network interface 58 may be activated in this step or a previous step, for example, in step 201 .

The method of Figure 14 may use one, two optional wait steps or no optional wait steps. After a certain period of inactivity, wireless network interface 58 may be set to sleep.

Assignment events are received by server 3 and stored in data set 15 .

Thus, the server 3 may, for example, track the consumption of beverages using a beverage consumption tracking module. Thresholds stored in the server 3 or dispensing station 50 may be used to trigger automatic delivery of new beverage containers 2 to end users of a certain dispensing station 50 . Delivery thresholds can be determined based on transit time and consumption rate. The consumption rate may be calculated using the dispensing events for the dispensing station 50 or dispensing stations 50 in the data set 15 . For example, average consumption over time can be used to calculate consumption rate.

The beverage dispensing station 50 may have a temperature sensor 59 to detect the temperature of the beverage container 2 or the ambient temperature in the vicinity of the beverage dispensing station 50 . This temperature can be used to trigger delivery of a new container 2. A temperature tracking module stored in the memory 60 of the beverage dispensing station 50 or in the server 3 may track the temperature detected by the temperature sensor 59 and compare the temperature to a temperature threshold. For example, if a beverage container 2 containing a beverage is exposed to high temperatures for longer than a threshold time, this may trigger activation of the anti-dispensing device 6 or the delivery of a new beverage container 2 . A message can be sent to the end user's mobile phone to prevent consumption of the beverage in the beverage container 2 . Temperature data may be stored in memory 60 of the control circuit. The distribution station 50 may be configured to determine the temperature at least every predetermined time interval (eg, at least hourly or at least daily). The temperature data may preferably be stored in the memory 60 of the distribution station 50 together with the detection time point. Reading the temperature can also be triggered by an assigned event, a first sensor, an accelerometer 56 or a weight determination device 55 .

The dispensing station 50 may have an anti-dispensing device 65 . To an extent, the anti-dispensing device 65 prevents the beverage from being dispensed from the beverage container 2 currently supported by or connected to the dispensing station 50 . The beverage anti-dispensing device 65 is remotely controlled by the server 3 through the control circuit of the dispensing station 50 .

The anti-dispensing device 65 may provide a warning signal to the user of the dispensing station 50 . The warning signal can be any type of signal, such as a visible, audible or tactile signal. The warning signal can be, for example, a light outside the distribution station, for example an LED 64. For example, it could be a red light or a flashing light.

In one embodiment, the dispensing station 50 does not have an anti-dispensing device 65 . Instead, the message may be sent to a smartphone associated with the user of distribution station 50 . The message may be that the contents of the current beverage container 2 should not be consumed.

The anti-dispensing device 65 may also lock the dispensing station 50 by, for example, locking the faucet 52 so that beverage cannot be dispensed from the dispensing station 50 . For example, when the faucet 52 includes a handle 66, the handle 66 may be locked in the closed position. For example, an electromagnetic actuator may be used to move the locking member from an unlocked position to a locked position such that handle 66 cannot move.

If the contents of a certain beverage container 2 are unfit for consumption, as detected manually or automatically by the system 1 , the anti-dispensing device 65 can be activated. For example, a server user may know that certain batches of beverages do not taste good or are contaminated in some way. The system 1 may detect a faulty container 2 by any suitable method, such as the method described herein with reference to the machine learning method of Figure 17, a temperature sensor 59, a second tag 18 or error detection logic. For example, the presence of a faulty container 2 is indicated by the fact that an unauthorized container is attached to the dispensing station, e.g. if the server 3 detects that the beverage container identity received from the dispensing station 50 does not exist in the data set 15; or a second Tag 18 (tamper device) indicates that the beverage container 2 has been tampered with.

Furthermore, the temperature data from the dispensing station 50 can be used to determine that the contents of an individual beverage container 2 are not suitable for consumption. Temperature data from temperature sensor 59 is reported to server 3 which may use this data to determine that beverage container 2 should be marked as non-consumable, for example if the temperature detected by temperature sensor 59 has been high for a certain threshold time is less than the threshold temperature.

Therefore, in the data set 15, one or more beverage containers 2 may be marked as non-consumable. This can be done manually or automatically as described above. The non-consumption mark can automatically trigger the activation of the anti-dispensing device 65 in the beverage dispensing station 50 in which the marked container 2 is present.

In step 400 of Figure 15, server 3 detects markers in data set 15. For example, logic at server 3 (anti-dispensing device activation module) may repeatedly scan data set 15 for flagged containers 2 . The server 3 identifies in the data set 15 the distribution station 50 currently being used by the marked container 2 (step 401). The server 3 then provides an activation signal to the anti-dispensing device 65 of the distribution station 50 using the wireless network interface 58 of the distribution station 50 (step 402), and the distribution station 50 then activates the anti-dispensing device 65 (step 403). The server 3 therefore provides the activation signal via the network connection to the beverage dispensing module 50 , which includes the wireless network interface 58 of the beverage dispensing station 50 . In the event that server 3 is unable to initiate communication with distribution station 50 , server 3 may have to wait for a communication event from distribution station 50 .

As mentioned above, the beverage container 2 has an identification tag 9 permanently attached thereto. In this document, the permanent tag 9 is also referred to as the "first tag 9". The first tag 9 is preferably an RFID tag or an NFC tag. The first tag 9 stores the identity of the beverage container 2 .

In various embodiments, the beverage container 2 has a second tag 18, preferably an RFID tag or an NFC tag. In a preferred embodiment, both the first tag 9 and the second tag 18 are NFC tags. The second tag 18 is a tamper-resistant device arranged to detect whether the beverage container 2 has been tampered with. Preferably, each of tags 9 and 18 includes at least one NFC antenna. Typically, the second label 18 is a disposable label.

The second label 18 has at least two states and is attached to the beverage container 2 such that the opening 12 of the beverage container 2 places the second label 18 in the second state in an irreversible manner. At least the first state can be detected via the tag reader 10 . The second state may be a state in which the second tag 18 cannot be detected by the tag reader 10, or a state in which the signal from the second tag 18 is altered in some manner relative to the first state.

The second label 18 is attached to the opening 12 of the filled beverage container 2 such that the opening 12 of the beverage container 2 must change the state of the second label 18 in an irreversible manner. For example, removing the cover 13 requires placing the second tag 18 in the second state. The second tag 18 may for example have an antenna which breaks when the opening 12 is opened (for example when the cover 13 is removed). For example, the antenna broke into two parts. For example, the second tag 18 may be in the form of a sticker with an NFC antenna placed on the lid 13 and a portion of the container 2 such that removing the lid 13 requires damaging the NFC antenna (Fig. 3b).

Regarding the term "irreversible," it should be noted that in some cases, a highly skilled expert with the correct tools and equipment may be able to restore the second label 18 to the first condition, but said second label 18 is still considered "irreversible." 's" because the average end user can't do that.

The second label 18 may be in the form of a sticker or a ring, for example. A portion of the second tag 18 may be made of a polymer material with the NFC antenna integrated into the polymer material. An example of such a system is the Circus ^™ Tamper-Resistant Ring offered by Avery Dennison. The second tag 18 may be of a completely destroyed type such that the NFC tag reader 10 does not receive any signal from the second tag 18 . Alternatively, the second tag 18 may be of a type in which the signal is changed but remains in the second state. This can be achieved by a second tag 18 having two antennas, one of which is broken in the second state, while the other antenna is still functional in the second state. This increases reliability because the still functioning antenna serves as control so that, for example, the tag reader 10 works as expected.

The second tag 18 may store the identity of the second tag 18 . The identity of the second tag 18 may be stored in the data set 15 together with the identity of the beverage container 2 (first tag identity). Therefore, any tampered information will be associated with the identity of the beverage container 2. For example, when delivering a beverage container 2, it is useful to know that the container 2 was delivered in an untampered state and that a particular container 2 is now connected to the beverage dispenser 50. This is particularly useful when the second tag 18 is completely destroyed (quiet) in the second state, as it would otherwise be difficult to know that the container 2 delivered to the end user in an untampered state is now connected to the beverage dispenser 50 . For machine learning assisted tracking of beverage containers 2, it would also be very useful to know whether a subset of containers (eg associated with a certain beverage filling station 4) has been tampered with.

The second label 18 may be applied to the container 2 using the method shown in Figure 16 . In step 700, an empty beverage container 2 is provided. The beverage container 2 has an opening 12 which can be closed as described above. The beverage container 2 has a permanently attached first tag 9 and the first tag 9 stores the identity of the beverage container 2 . Preferably, the container 2 is clean and in a "washed" state. In step 701, the beverage container 2 is filled such that the beverage container 2 contains at least some beverage. The container 2 is then closed, for example by attaching a lid 13 . In step 702, the second label 18 in the first state is attached to the beverage container 2 such that the opening 12 of the beverage container 2 irreversibly places the second label 18 in the second state. This is preferably done in a controlled environment so that no tampering can occur between the two. In step 703 , the state of the second tag 18 , which is now usually in the first state, is stored in the data set 15 . This status is stored together with the identity of the first NFC tag 9 (for example the identity of the beverage container 2). In step 704 , which may occur before, after or simultaneously with step 703 , the identity of the second tag 18 is stored in the data set 15 together with the identity of the beverage container 2 . The beverage container 2 is then transported to the end user.

Tag readers 10, such as portable tag readers 10 used by delivery services, can be used to confirm that untampered containers have been delivered to the end user. Tag reader 10 can provide this information to server 3, which stores this information in a data set. This provides information that an untampered container 2 has been delivered to the end user. Delivery may be confirmed by the end user via various means, for example, by a signature (eg, electronic signature). If the second label 18 is in the second state, the new container 2 can be automatically shipped via the server 3 to the end user.

The end user then installs the container 2 at the distribution station 50 so that the first label 9 and the second label 18 can be read by the label reader 10 of the distribution station. The tag reader 10 of the distribution station 50 can then read the identity of the first tag 9, confirm that the second tag 18 is in the second state (or first state), and report this to the server 3. The tag reader 10 of the distribution station 50 can read the second tag 18 and store the status in the memory 60 of the distribution station 50 . The tag reader 10 of the distribution station 50 can store the identity of the first tag 9 and the identity of the second tag 18 (if the second tag 18 has an identity) and combine these identities together with the status (first status/second status) stored in memory 60. If the second tag is not detected and the second tag 18 is of a type automatically damaged by the tag reader 10, the distribution station may store information that the second tag 18 is in the second state if the tag is not detected. Therefore, the tag reader 10 attempts to read the second tag 18, but does not get a reply, thereby assuming that the second tag 18 is in the second state.

The method may include, if the tampered container 2 has been delivered, marking the container 2 as unused in the data set 15 . Therefore, there may be logic in the server 3 that allows only containers 2 that have been delivered in an untampered state (in the first state) to be associated with the distribution station 50 . If such a container 2 is present at the dispensing station 50, when the dispensing station 50 reports the identity of the beverage container 2 to the server, the server 3 will receive said identity as described elsewhere (eg with reference to Figure 13).

If the server 3 detects the presence of a tampered container 2 at the distribution station 50, the server 3 may be configured to take different actions. For example, anti-dispensing device 65 may be activated. A message about the tampering can be sent to the end user, for example, so that the end user does not consume the content.

The tag reader 10 of the distribution station 50 is preferably able to read the second tag 18 in the same way as the identification tag 9 is read. For example, the embodiment shown in Figures 10-11 may be used with the second tag 18 as well as the first tag 9.

Server 3 may include or be in digital communication with machine learning service 20 . Machine learning service 20 can apply machine learning to data set 15 to obtain decision rules. The machine learning service 20 is capable of detecting patterns to generate decision rules useful to the management system 1, for example regarding: a) beverage requirements; b) logical requirements, such as dispensing beverage containers 2; c) system 1 or system errors or bottlenecks in the various components of 1; e) determining the service life of beverage containers 2; and f) detecting beverage containers 2 that should not be consumed by the end user. Users of Server 3 can use machine learning to predict the behavior of System 1 and its (sub)users.

Many possibilities exist. Here are some hypothetical examples:

1. There is always a surge in demand for drinks on Wednesdays. This can be used to increase the throughput of filled beverage containers 2 in advance.

2. Beverage containers continue to malfunction at one particular filling station 4. This information can be used to access the filling station 4 to resolve the issue.

3. Specific user patterns of the beverage container 2 (such as the number of filling cycles, transportation length or other parameters) cause the beverage container 2 to break earlier than other containers. Beverage containers 2 that meet these criteria (eg multiple filling cycles or total length of transport) can be detected and taken out of service before they break.

4. An individual beverage container 2 deviates from a pattern. This may indicate that Container 2 has been tampered with or is a counterfeit container provided by an unauthorized source. For example, a fake container ID has been created, or the ID of the "real" container 2 has been cloned, and the container 2 has then been inserted into the system 1 , for example has been attached to the beverage dispenser 50 . Therefore, decision rules can also be used to detect fraud.

Parameters useful for and included in Data Set 15 include: number of filling cycles, length of shipment, length of time the container 2 spends at the end user, production date of the beverage container 2, production lot number of the beverage container 2, storage Time, data from sensors of the distribution station 50 (eg weight determination device 55, temperature sensor 59 or accelerometer 56), manually or automatically recorded errors or malfunctions of the container 2 and the distribution station 50, transport means and combinations thereof. Any data from dataset 15 can be used. Information used for machine learning can also be provided by external information providers, for example, information about the weather, temperature, humidity, etc. at the end user or during transportation or storage. These are only non-limiting examples as there are many possibilities.

In particular, machine learning can be used to determine a statistical model and to detect behavior of individual beverage containers 2 that deviates from the statistical model. This may indicate that the beverage container 2 has been tampered with, causing the identity of the beverage container 2 to be forged, or that the identity of the beverage container 2 has been cloned or stolen.

The following is a hypothetical example illustrating how to use machine learning to identify strangely behaving beverage containers2:

- Abnormal transport speed of beverage container 2 to dispensing station 50 (too short a time indicates too many IDS, too long a time indicates the beverage dispenser has been tampered with)

- Beverage container 2 was not in the system for an extended period of time (possibly indicating tampering)

- Abnormal accelerometer data (may indicate tampering)

However, it should be remembered that the decision rules can be considered as "black boxes" and it is difficult to speculate which parameters are predictive parameters for indicating tampering or other malfunctions in the beverage container 2, and even making such speculation may be meaningless. The machine learning predictions are improved when the data set 15 includes information about a large number of beverage containers 2 accumulated over time (the training data set). Machine learning improves when containers 2 are similar or identical or at least equivalent. The same applies to the filling station 4 or the distribution station 50 . Machine learning may be provided by a machine learning service 20 such as Amazon, or may be provided in a server 3. Any useful type of machine learning can be used, such as machine learning that implements Bayes' theorem. Guidance can be found in US2014/0012784, US2008/0059120 and US8819498.

Applying machine learning can produce statistical models for the behavior of multiple beverage containers. The decision rule can be that any container 2 that deviates from the behavior should be taken out of service. The decision rule can be that any container 2 that deviates from the statistics beyond the allowed range should be stopped. There may be a threshold for how much container 2 may deviate from the statistical model before being taken out of service. The threshold can be predetermined or determined by the server user. Binary classification can be used to classify beverage containers 2 that should be taken out of service and beverage containers 2 that should not be taken out of service.

Referring to Figure 17, the method may include the steps of step 800, that is, applying machine learning to the data set 15 to obtain decision rules. Decision rules can be updated by applying machine learning at any useful interval, such as daily, weekly, or monthly. Therefore, in step 800, data set 15 is used as a training data set to obtain decision rules. In step 801, decision rules are applied to the data set 15. This is also performed at any suitable interval, but usually more frequently than the decision rule is updated, such as hourly or daily. Decision rules may be applied to a portion of the data set 15. For example, machine learning could be applied to data on beverage containers 2 that have been taken out of use, while decision rules are applied to beverage containers 2 that are currently only in use. The data set 15 is updated frequently, preferably in real time. Therefore, the data set 15 changes over time. In step 802, a decision is made. This may be a decision regarding an individual beverage container 2 , for example a certain beverage container 2 should be taken out of service or the contents of a beverage container 2 should not be consumed. A single container 2 can be marked out of service in the dataset. This can trigger a manual alert at Server 3 to the server user. This may also trigger activation of the anti-dispensing device 65 . Thus, in one embodiment, the beverage dispensing station has an anti-dispensing device 65 which the server 3 may be configured to activate when a beverage container 2 is marked out of service.

In some embodiments, the method may include making a decision regarding the removal of an individual beverage container 2 from service by providing data associated with the beverage container 2 to a decision rule that includes a statistical model, wherein the statistical model is obtained by: a) receiving a training data set comprising data for beverage containers 2, said data comprising information on a large number of beverage containers 2 accumulated over time, wherein said data set includes beverages that have been discontinued Container 2; and b) apply machine learning to the data set to generate decision rules including statistical models.

The training data set may include information on a large number of beverage containers 2 that have been out of use within a predetermined time period (such as damaged beverage containers 2), or information on a large number of beverage containers 2 that have not been out of use within a predetermined time period, or about both. information of the person. Decision rules may be used to identify beverage containers that are currently in use but are highly similar to beverage containers 2 that were discontinued before a predetermined time, to containers 2 that are still in use after a predetermined time, or to both.

Machine learning can be used to generate a statistical model describing how a beverage container 2 typically behaves in the system 1 (eg with respect to transport speed), and any beverage container that deviates from the statistical model can be marked out of use. This could be used, for example, to identify beverage containers that have been tampered with in some way.

Decision rules may be stored in machine learning service 20. The server 3 may include one or more of the following software components that use decision rules in the machine learning service 20: a beverage container tracking module and a container error flagging module. For example, a container tracking module may provide data associated with a single beverage container 2 to a decision rule. If the decision rule logic makes a decision regarding an individual beverage container 2 being out of service, information related thereto is provided from the decision rule logic to the container error flagging module, which flags the individual container 2 as being out of service.

Machine learning is applied to data set 15 in the same way to predict errors at beverage dispensing stations 50.

The system 1 may comprise one or more beverage filling stations 4 for filling beverage containers with beverages. The beverage filling station 4 can be located, for example, in a suitable building. However, in certain embodiments, the beverage filling station 4 may be located entirely or partially within the filling station container 21 . This provides for rapid expansion of systems in which one or more filling station containers 21 equipped with filling stations 4 are deployed.

The filling station 4 may comprise a beverage production unit. The beverage production unit may be computer controlled such that the computer 19 controls the tanks, dispensers, valves, pumps, heaters and coolers in a predetermined sequence to provide an automated brewing or beverage production process. The computer 19 can also control the cleaning process (clean in place) when the beverage has been prepared or according to a predetermined schedule.

The beverage production unit may be adapted to provide any type of beverage, such as drinking water, beer or soda, or cider. In a preferred embodiment, the beverage is beer. In a preferred embodiment, the beverage is drinking water.

The beverage production unit may include a water purification unit 5 . The water purification unit 5 may use any suitable technology such as filters, heating, UV radiation or the addition of chemicals such as chlorine. The beverage production unit may also include a desalination device for removing salt from the water.

The beverage production unit may also provide units for adding various ingredients, such as flavorings (eg syrup for providing soda water) and carbon dioxide. Beverages can be produced continuously or in batches and stored in tanks 6.

The beverage production unit preferably has at least one sensor for sensing eg flow, temperature, pressure or level in the beverage production unit. Generally speaking, the sensors may provide data to the computer 19 and server 3 . Sensor data and production data can be stored in data sets 15. The computer 19 of the beverage filling station 4 may be connected to a data network communication device capable of data communication with the server 3 . Computer 19 may also include memory, a processor, and a bus. The computer 19 is preferably connected to the tag reader 10 of the beverage filling station 4 .

The memory of the computer 19 of the beverage filling station 4 may have at least one set of instructions for producing a digital form of the beverage. The computer 19 has access to a plurality of instructions, one for each type of beverage, such as a different type of beer. Digital instructions (recipes) can be provided from the server 3 to the computer 19 . The computer 19 may have a user interface that a user may use, for example, to start or terminate a brewing program. User interfaces may include display and input devices such as keyboards, mice, joysticks, touch screens, and the like. Alternatively, the user of the beverage filling station 4 can use a mobile phone as an interface, for example by connecting to the computer 19 via the server 3 or by connecting directly to the computer 19 .

For example if the server 3 detects or predicts a demand for a drink, the computer 19 may receive an order from the server 3 to produce the drink. Thus, the computer 19 can activate the beverage production unit, for example, to produce beer or drinking water.

In a preferred embodiment, the beverage filling station 4 is arranged such that the tag reader 10 is positioned relative to the washing station 7 so that the label 9 of the beverage container 2 is only detected when the beverage container 2 has passed the washing station 7 . For example, the tag reader 10 is placed close to the exit of the washing station 7 . This provides automatic tracking of cleaned containers 2 and ensures that only cleaned containers 2 are marked as "cleaned".

Referring to FIG. 18 , the method may include step 900 , that is, detecting the beverage container 2 , and the method may further include step 901 , that is, the tag reader 10 providing the identity of the beverage container 2 to the server 3 . This is achieved by a computer 19 in network communication with the server 3 . In step 902, the server 3 sets the status of the beverage container 2 in the data set 15 to "cleaned". Server 3 may set the status to "Cleaned" because tag reader 10 is associated with that status at server 3 such that the identity of tag reader 10 is associated with the cleaned status in data set 15 . Alternatively, the ability to set the cleaned status is stored with the tag reader 10 which provides the cleaned status message to the server 3 together with the identity of the beverage container 2 .

Similar rules may apply wherever rules are useful in the system, and may for example involve two or more tag readers 10 .

In an even more preferred embodiment, the system 1, in particular the filling station 4, provides at least three tag readers 10: one tag reader 10 provides the "not cleaned" status (or "entered station" status) , one tag reader 10 provides a "cleaned" status, and one tag reader 10 provides a third status that may be a "filled/ready for delivery" status.

As mentioned above, the server 3 may have logic to detect errors such as an erroneous transition from the "uncleaned" state to the "filled" state without passing through the "cleaned" state. When an error has occurred, the individual beverage containers 2 can be marked out of service in the data set 15 or reprocessed, for example brought back to the beverage filling station 4 to be cleaned and filled again. Likewise, if the container 2 is delivered to the dispensing station 50 in some manner, the beverage anti-dispensing device 65 of the dispensing station 50 may be activated.

The filling station 4 may be included in a filling station container 21 . The dimensions of the filling station container 21 are preferably such that the beverage filling station 4 can be transported using a truck or trailer or similar equipment. Therefore, the filling station container 21 is movable. For example, the filling station container 21 may have the dimensions of a prefabricated transport container. The filling station container 21 may have the dimensions of a standard intermodal shipping container. Standard ISO shipping containers are 8 feet (2.43 meters) wide and 8.5 feet (2.59 meters) high, and come in two lengths: 20 feet (6.06 meters) and 40 feet (12.2 meters). The filling station container 21 may be made of steel or other solid material, such as aluminum, fiberglass, plastic, plywood or similar materials. The filling station container 21 is preferably self-supporting. The filling station container 21 may have any suitable shape, with a rectangular block shape or a similar shape being preferred. The rectangular block may have approximately the following dimensions: height 2-3 meters, width 2-3 meters, length 3-12 meters. The user may enter the filling station container 21 , for example by walking into the filling station container, to service the beverage preparation unit or to make inputs to the computer 19 .

The filling station container 21 may be adapted to be placed on the ground or on the floor. The filling station container 21 may have a substantially flat underside for placing the filling station container 21 on a flat ground or floor, but the filling station container 21 may be provided with feet for placing on uneven surfaces or track.

The filling station container 21 may have suitable arrangements for lifting the filling station container 21 by a crane or otherwise moving the filling station container 21 . Therefore, the filling station container 21 can be transported to the desired location and easily connected and served with beverages in a short time.

The filling station container 21 is preferably suitable for placement outdoors. Therefore, in order to protect the various components of the filling station container 21 or to provide a controlled environment for beverage production, the filling station container 21 may have appropriate protection against one or more of: heat, cold temperatures, rain, lightning, Snow or strong winds. The walls of the filling station container 21, including the top and bottom, may be thermally insulated. These walls protect against both rain and wind. The bottom of the filling station container 21 is suitable for being placed on the ground and is rainproof and water-proof. The total thickness of the walls of the filling station container 21 (including the insulation layer) may be at least 2 cm, more preferably at least 4 cm, most preferably at least 6 cm. In one embodiment, the filling station container 21 is a conventional intermodal shipping container with internal insulation. The filling station container 21 may be provided with means for proving controlled temperature and humidity within the filling station container 21, such as a heater, a cooler, an air conditioner, a humidifier or a dehumidifier. The computer may be configured to control the internal conditions of the filling station container 21 and maintain, for example, the temperature or humidity within a predetermined range.

The tag reader 10 may be arranged to detect that a beverage container 2 has entered the beverage filling station 4 , in particular has entered the beverage filling station container 21 .

The filling station container 21 is preferably connectable to external power, water and sewer, and may preferably be provided with suitable piping and wiring to facilitate connection. The walls of the filling station container 21 may have suitable bushings for various connections or ports for various utilities such as electricity, water, sewage and data communications. The filling station container 21 may have a pump for providing suction to supply water from a water source such as the sea or a lake or river. The walls of the filling station container 21 may have suitable sleeves for various connections or ports for various utilities such as electricity, water, sewage and data communications.

The beverage filling station container 21 is preferably connected to external power, water and sewage, and may preferably be provided with appropriate piping and wiring to facilitate connection.

The beverage filling station container 21 is preferably connectable to external power, water and sewer, and may preferably be provided with suitable plumbing and wiring to facilitate connection.

The filling station container 21 may in particular comprise a water purification unit 5 , a beverage production unit, a beverage tank 6 , one or more tag readers 10 , a computer 19 and a washing station 7 .

It will be understood that the methods, systems and apparatus of the present invention may be implemented in part by a computer via digital computer equipment. Various embodiments and components described herein (eg, server 3, beverage dispensing station 50, tag reader 10, filling station 4, computer 19, machine learning service 20, mobile phone, and communications between these components) use digital computers technology and suitable hardware and software to store and process digital information and signals, where suitable hardware and software include, for example, suitable digital processors, digital memories, input devices, output devices, buses and communication interfaces. The user can input using, for example, a keyboard, mouse, or touch screen. The output can be provided on a display, for example.

Various components such as server 3 and computer 19 may each have an operating system. The server 3 may have a user interface such that the user of the server can use the user interface to add new beverage containers 2, analyze data, etc. Referring to FIG. 19 , each of the tag reader 10 , the server 3 , the computer 19 , the mobile phone, and the machine learning service 20 may include a control circuit including a memory 80 , a processor 81 , a bus 82 and a communication interface. 83. The tag reader 10, server 3 and machine learning service 20, and beverage dispensing station 50 may each have suitable hardware and software for communicating over a data network such as the Internet.

Server 3 may be a physical server or may be a virtual server. Therefore, the functionality of server 3 can be distributed across multiple physical entities. Data, such as data set 15, may be stored in the database shown in Figure 1 or in server 3. Data set 15 may be stored in a distributed database including multiple nodes.

The methods described herein may be implemented by any suitable combination of software and hardware. Any suitable programming language may be used in the software units and methods described. Data communication in System 1 can be achieved using suitable network technologies and protocols, giving rise to cellular communications such as 3G, 4G and 5G, LoRa, Wi-Fi or Bluetooth or Ethernet. Data communication may be wireless communication or wired communication. Information may be exchanged over a wide area network such as the Internet 17. Data communications in System 1 can be encrypted. Wireless communications in System 1 can be performed using suitable transmitters and receivers. Tag reader 10 may have suitable transmitters and receivers to detect NFC tags or RFID tags.

The respective identities of the beverage container 2 and the dispensing station 50 may include any suitable combination of numbers, letters or other symbols suitable for digital data processing. Each filling station 4 in system 1 also has an identity.

Communications in system 1 and updates to data sets 15 may be performed using any suitable schedule. The tag reader 10 and the dispensing station 50 can provide information to the rest of the system 1 , in particular the server 3 , for example immediately when the tag reader 10 detects a beverage container 2 or when a sensor of the dispensing station 50 detects a value. . Alternatively, the communication session may be scheduled to be performed at suitable intervals, such as at least every predetermined interval, such as at least every second, at least every minute, at least every hour, or every day.

It will be appreciated that what has been described in connection with one embodiment is fully compatible with other embodiments. The invention is therefore not limited to the embodiments described but may vary within the scope of the appended claims. While the invention has been described with reference to specific exemplary embodiments, the description is generally intended to illustrate the concepts of the invention and should not be construed as limiting the scope of the invention. The invention is generally defined by the claims.

The invention may be protected in the additional aspects set forth below:

In another aspect of the invention, a beverage dispensing system is provided, comprising: a plurality of beverage containers, wherein each beverage container is reusable and portable, and wherein each of the plurality of beverage containers Each includes an identity tag with a unique identity,

a plurality of beverage dispensing stations adapted to be mechanically connected to the beverage containers such that beverages can be dispensed from the beverage containers when the beverage containers are mechanically connected to the beverage dispensing stations,

a server that has stored the identity of each of the plurality of beverage containers in the data set,

Each of the beverage dispensing stations includes an accelerometer, the beverage dispensing station further includes an identification tag reader, a wireless network interface, and control circuitry, wherein the dispensing station is configured to activate the accelerometer when the accelerometer detects movement. The tag reader thereby reads the identity tag of the beverage container and is configured to provide the identity of the beverage container to a server using the wireless network interface, the server being configured to receive the identity of the beverage container and store the identity of the beverage container in the data concentrated.

Using accelerometers in beverage dispensing stations serves a variety of purposes. For example, an accelerometer can detect when a user switches drink containers. This is an appropriate time to report the identity of the beverage container. This keeps the server updated while keeping data transfer and power usage in the beverage dispensing station to a minimum.

The identity of the beverage container may be provided along with at least one of the following: beverage consumption data or weight data, temperature readings, battery status, or accelerometer data. As described in this article, this data can be used to provide users with a safer and better experience.

In another aspect of the invention there is a beverage dispensing station adapted to be mechanically connected to a beverage container such that beverage is dispensed from said beverage container, the beverage dispensing station comprising an identity tag reader, a wireless network interface and an accelerometer, said The beverage dispensing station also includes a control circuit having a memory, wherein the beverage dispensing station is configured to read an identity tag of a beverage container currently connected to the dispensing station when the accelerometer detects movement and store the identity tag in in the memory of the control circuit.

When this number has been stored in memory, the beverage dispensing station can choose whether to send the identity. For example, if a new beverage container identity exists, the beverage dispensing station can send that identity to the server. If the identity is the same as the previous identity, the beverage dispensing station may take no action.

The beverage dispensing station may be configured to connect to the server using the wireless network interface and provide the identity of the beverage container to the server.

The beverage dispensing station may be configured to provide accelerometer data to the server. This can be used to detect tampering or if the beverage dispensing station has been damaged, such as being dropped on the floor.

The control circuitry of the beverage dispensing station may have a wake state and a sleep state, and the beverage dispenser may be configured such that movement detection by the accelerometer wakes the control circuitry from the sleep state. This saves electricity at the beverage dispensing station. The accelerometer can also activate the wireless network interface.

The beverage dispensing station may have a weight determining device activated by movement detection by an accelerometer. The weight determining device may be used to determine beverage consumption and provide beverage consumption data to the server. The weight determination device cannot be used to wake the control circuit from sleep.

According to another aspect of the invention, there is provided a method involving a system including a plurality of beverage containers, wherein each of said beverage containers is reusable and portable, and wherein said plurality of beverage containers Each beverage container in the container includes a unique identification tag,

a plurality of beverage dispensing stations adapted to be mechanically connected to the beverage containers such that beverages are dispensed from the beverage containers,

a server that has stored the identity of each of the plurality of beverage containers in a data set, each of said beverage dispensing stations including an accelerometer, said beverage dispensing stations further including an identity tag reader, a wireless network Interface and control circuit, the method includes the following steps:

The accelerometer detects movement, which activates the tag reader to read the beverage container's ID tag, which then,

The beverage dispensing station provides the identity of the beverage container to the server using the wireless network interface, and the server then receives the identity of the beverage container and stores the identity of the beverage container in the data set.

In one embodiment, the beverage dispensing station has a weight determining device, and wherein the weight determining step is performed before step b), said step comprising using the weight determining device of the beverage dispensing station to determine the beverage container currently supported by the dispensing station. of weight, wherein weight data or beverage consumption data are provided to the server in step b).

According to another aspect of the present invention, there is provided a beverage container that is reusable and portable, the container having a closable opening, the beverage container containing a beverage and having two near field communication (NFC) tags,

The two NFC tags are:

a first NFC tag permanently attached to the beverage container and storing the identity of the beverage container, and

a second NFC tag having at least two states, the second NFC tag being in a first state and attached to the beverage container such that opening the opening of the beverage container irreversibly places the second NFC tag in the first state Two states.

The first label provides traceability of the containers in the system. The second tag ensures that the container that has been delivered to the user has not been tampered with. This will provide additional security for users of the beverage container.

The second tag may store a second identity. The second label may be a disposable label.

According to another aspect of the present invention, a method is provided, the method comprising:

a) providing an empty beverage container, the beverage container being reusable and portable, wherein the beverage container has a closable opening, and wherein the beverage container has a first NFC tag permanently attached to the beverage container, and wherein , the first NFC tag to store the identity of a beverage container,

b) Fill the container with beverage so that there is at least some beverage in the container and close the opening of the container,

c) Attaching a second NFC tag to the container, said second NFC tag having at least two states, said second NFC tag being in a first state and being attached to the beverage container such that the opening of the beverage container is opened irreversibly Put the second NFC tag into the second state.

The method may additionally involve a digitally stored data set comprising the identities of a plurality of beverage containers, and wherein the method additionally includes step d) performed after step c), said step d) being The status of the second NFC tag of the beverage container is stored in the data set together with the identity of the first NFC tag.

The second NFC tag may store a second identity, and the method may include the step of storing the identity of the second NFC tag together with the identity of the first NFC tag in the data set.

Connections in the data set provide traceability of containers in the system. For example, it would be useful to know the location of a tampered container.

When the server stores the data set, the method may further involve a beverage dispensing station being adapted to be mechanically connected to the beverage container such that a beverage can be dispensed from the beverage container, the beverage dispensing station including an identification tag reader, the beverage dispensing station including a A wireless network interface for communicating with the server,

The method also includes the following steps:

d) the tag reader of the dispensing station reads the first tag of the beverage container and the tag reader of the dispensing station reads or attempts to read the status of the second tag,

e) The beverage dispensing station provides the identity of the beverage container and the status of the second tag to the server, and then

f) The server stores the identity of the beverage container event associated with the identity of the dispensing station in the data set.

According to another aspect of the invention, there is provided a system comprising a plurality of beverage containers according to the above aspect of the invention and a server, wherein the server stores the identity of each of the plurality of beverage containers in a data set , where the status of each second tag is stored in the data set and associated with the identity of the beverage container.

Connections in the data set provide traceability of containers in the system. For example, it would be useful to know the location of a tampered container.

The system may additionally include a tag reader. The system may additionally include a beverage dispensing station configured to be connected to a beverage container such that beverage is dispensed from the container, the beverage dispensing station including a tag reader.

According to another aspect of the invention, a beverage delivery system is provided, comprising:

a beverage filling station configured to fill beverage containers with a beverage, the beverage filling station including at least one identification tag reader,

a plurality of beverage containers that are reusable and portable, wherein each of the plurality of beverage containers carries a unique identification tag,

A server connected to an identification tag reader, the server configured to store a status of a reusable beverage container in a data set using information from the tag reader and the identification tag.

The system provides a collection of information about beverage containers and centralized control of the containers. This improves security.

The beverage filling station may be a washing station, wherein the identification tag reader is arranged in the washing station such that the identification tag reader only reads the identification tags of beverage containers that have passed through the washing station. Beverage filling stations can produce beverages.

It is important to keep track of which beverage containers have been cleaned and which have not.

The system may include a plurality of beverage filling stations, wherein each filling station provides data to a data set, and wherein each beverage container is logically associated with a certain beverage filling station in the data set.

At least one identification tag reader of the system is configured to register the status of a reusable container selected from the following containers:

a) The container has entered the beverage filling station,

b) the container has been cleaned in the beverage filling station,

c) the container has been filled with beverage in the beverage filling station,

d) The container has left the beverage filling station.

According to another aspect of the invention, a method of a beverage delivery system is provided, the beverage delivery system comprising:

a beverage filling station configured to fill a reusable beverage container with a beverage, the beverage filling station including at least one identification tag reader,

a plurality of beverage containers that are reusable and portable, wherein each of the plurality of beverage containers carries a unique identification tag,

a server connected to the identification tag reader, the server configured to store the status of the reusable beverage container in a digitally stored data set using the identification tag, wherein the beverage filling station includes a washing station, wherein, The identification tag reader is arranged in the washing station so that the identification tag reader only reads the identification tags of beverage containers that have passed through the washing station. The method includes the following steps:

a) A tag reader reads the identification tag on an individual beverage container,

b) the tag reader provides the identity of the beverage container to the server,

c) The server stores information that a single beverage container has been cleaned.

Claims (10)

1. A system consisting of: a plurality of portable beverage containers, wherein each beverage container of the plurality of beverage containers carries a unique identification tag, The system also includes: At least one beverage dispensing station adapted to support one of said beverage containers and connected to said beverage container such that a beverage can be dispensed from said container, said beverage dispensing station comprising an identity tag configured to read an identity tag of a beverage container a reader, the beverage dispensing station further comprising a wireless network interface, wherein the beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from the dispenser, The system also includes a server in communication with the beverage dispensing station, the server having stored a data set including the identity of each of the plurality of beverage containers, wherein the beverage containers can be tagged in the data set to The anti-dispensing device is activated, and the system is configured to activate the anti-dispensing device of the dispensing station when a beverage container is marked to activate the beverage anti-dispensing device. 2. The system of claim 1, wherein the anti-dispensing device is a light or audible warning signal to the user. 3. The system of claim 1, wherein the anti-dispensing device prevents beverage dispensing from the dispensing station. 4. The system of claim 3, wherein the dispensing station has a faucet and the anti-dispensing device locks the faucet. 5. The system of any one of claims 1 to 4, wherein the identification tag is a near field identification (NFC) tag. 6. A system according to any one of claims 1 to 5, wherein the beverage container is reusable. 7. A beverage dispensing station adapted to support a portable beverage container and connected to the beverage container such that a beverage can be dispensed from the container, the beverage dispensing station including a portable beverage container configured to read the beverage container an identification tag reader, the beverage dispensing station also includes a wireless network interface, wherein the beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from the dispenser, and wherein the dispensing station is configured to when receiving a signal from a server via the wireless network interface Activate the anti-dispensing device. 8. The beverage dispensing station of claim 7, wherein the tag reader is an NFC tag reader. 9. A beverage dispensing station according to claim 7 or 8, wherein the wireless communication interface is a cell network interface enabling the beverage dispensing station to function as a user equipment in a cell network. 10. A method involving a system comprising: a plurality of portable beverage containers, wherein each beverage container of the plurality of beverage containers carries a unique identification tag, The system also includes: A plurality of beverage dispensing stations adapted to support one of said beverage containers and connected to said beverage container to enable dispensing of beverages from said container, said beverage dispensing station comprising an identification tag reader configured to read an identification tag of the container. dispenser, the beverage dispensing station also includes a wireless network interface, The system also includes a server in communication with the beverage dispensing station, the server having stored a data set including an identity of each of the plurality of beverage containers, the identity of the beverage container being consistent with the identity of the beverage dispensing station. Identity association, wherein the beverage dispensing station has an anti-dispensing device that prevents a user from dispensing a beverage from the dispenser, the method comprising the following steps: a) the server detects in the data set a flag for activating an anti-dispensing device for a certain beverage container, b) the server identifies in the data set the dispensing station associated with the marked beverage container, c) the server provides a signal to the distribution station identified in step b) to activate the anti-distribution device, d) The distribution station activates the anti-dispensing device.