SE2051541A1 - Beverage dispensing station with weight determining means - Google Patents

Beverage dispensing station with weight determining means

Info

Publication number
SE2051541A1
SE2051541A1 SE2051541A SE2051541A SE2051541A1 SE 2051541 A1 SE2051541 A1 SE 2051541A1 SE 2051541 A SE2051541 A SE 2051541A SE 2051541 A SE2051541 A SE 2051541A SE 2051541 A1 SE2051541 A1 SE 2051541A1
Authority
SE
Sweden
Prior art keywords
beverage
container
dispensing station
weight
dispensing
Prior art date
Application number
SE2051541A
Other versions
SE545375C2 (en
Inventor
Martin Renck
Mattias Liss
Niclas Emdelius
Ulf Stenerhag
Original Assignee
Wayout Int Ab
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wayout Int Ab filed Critical Wayout Int Ab
Priority to SE2051541A priority Critical patent/SE545375C2/en
Priority to IL303958A priority patent/IL303958A/en
Priority to US18/258,216 priority patent/US20240002209A1/en
Priority to US18/258,229 priority patent/US20240076178A1/en
Priority to JP2023561923A priority patent/JP2024503143A/en
Priority to PCT/EP2021/087377 priority patent/WO2022136587A1/en
Priority to AU2021405750A priority patent/AU2021405750A1/en
Priority to KR1020237025238A priority patent/KR20230136601A/en
Priority to PCT/EP2021/087388 priority patent/WO2022136595A1/en
Priority to PCT/EP2021/087386 priority patent/WO2022136593A2/en
Priority to EP21840632.0A priority patent/EP4268153A1/en
Priority to PCT/EP2021/087252 priority patent/WO2022136528A1/en
Priority to EP21844714.2A priority patent/EP4268154A1/en
Publication of SE2051541A1 publication Critical patent/SE2051541A1/en
Publication of SE545375C2 publication Critical patent/SE545375C2/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • G06Q10/0875Itemisation or classification of parts, supplies or services, e.g. bill of materials
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/06Electricity, gas or water supply
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B67OPENING, CLOSING OR CLEANING BOTTLES, JARS OR SIMILAR CONTAINERS; LIQUID HANDLING
    • B67DDISPENSING, DELIVERING OR TRANSFERRING LIQUIDS, NOT OTHERWISE PROVIDED FOR
    • B67D1/00Apparatus or devices for dispensing beverages on draught
    • B67D1/0003Apparatus or devices for dispensing beverages on draught the beverage being a single liquid
    • B67D1/0004Apparatus or devices for dispensing beverages on draught the beverage being a single liquid the beverage being stored in a container, e.g. bottle, cartridge, bag-in-box, bowl
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B67OPENING, CLOSING OR CLEANING BOTTLES, JARS OR SIMILAR CONTAINERS; LIQUID HANDLING
    • B67DDISPENSING, DELIVERING OR TRANSFERRING LIQUIDS, NOT OTHERWISE PROVIDED FOR
    • B67D1/00Apparatus or devices for dispensing beverages on draught
    • B67D1/0003Apparatus or devices for dispensing beverages on draught the beverage being a single liquid
    • B67D1/0004Apparatus or devices for dispensing beverages on draught the beverage being a single liquid the beverage being stored in a container, e.g. bottle, cartridge, bag-in-box, bowl
    • B67D1/0005Apparatus or devices for dispensing beverages on draught the beverage being a single liquid the beverage being stored in a container, e.g. bottle, cartridge, bag-in-box, bowl the apparatus comprising means for automatically controlling the amount to be dispensed
    • B67D1/0008Apparatus or devices for dispensing beverages on draught the beverage being a single liquid the beverage being stored in a container, e.g. bottle, cartridge, bag-in-box, bowl the apparatus comprising means for automatically controlling the amount to be dispensed based on weighing
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B67OPENING, CLOSING OR CLEANING BOTTLES, JARS OR SIMILAR CONTAINERS; LIQUID HANDLING
    • B67DDISPENSING, DELIVERING OR TRANSFERRING LIQUIDS, NOT OTHERWISE PROVIDED FOR
    • B67D1/00Apparatus or devices for dispensing beverages on draught
    • B67D1/08Details
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B67OPENING, CLOSING OR CLEANING BOTTLES, JARS OR SIMILAR CONTAINERS; LIQUID HANDLING
    • B67DDISPENSING, DELIVERING OR TRANSFERRING LIQUIDS, NOT OTHERWISE PROVIDED FOR
    • B67D1/00Apparatus or devices for dispensing beverages on draught
    • B67D1/08Details
    • B67D1/0878Safety, warning or controlling devices
    • B67D1/0882Devices for controlling the dispensing conditions
    • B67D1/0884Means for controlling the parameters of the state of the liquid to be dispensed, e.g. temperature, pressure
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01FMEASURING VOLUME, VOLUME FLOW, MASS FLOW OR LIQUID LEVEL; METERING BY VOLUME
    • G01F23/00Indicating or measuring liquid level or level of fluent solid material, e.g. indicating in terms of volume or indicating by means of an alarm
    • G01F23/20Indicating or measuring liquid level or level of fluent solid material, e.g. indicating in terms of volume or indicating by means of an alarm by measurement of weight, e.g. to determine the level of stored liquefied gas
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01GWEIGHING
    • G01G19/00Weighing apparatus or methods adapted for special purposes not provided for in the preceding groups
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083Shipping
    • G06Q10/0833Tracking
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

There is provided a beverage dispensing station adapted to support a portable beverage container, and connect to the beverage container such that beverage can be dispensed from said beverage container, said beverage dispensing station having weight determining means for determining the weight of a beverage container supported by said beverage dispensing station, the beverage dispensing station further comprising control circuitry comprising a memory and a wireless network interface, the dispensing station being configured to determine the weight of the reusable beverage container and to store the weight in the memory.

Description

Beverage dispensing station with weight determining means Field of the invention This invention relates to systems and methods for distribution of beverage, in particular using individually traceable containers.
Background Although centrally provided water ("tap water") is available most countries, at least indensely populated areas, the water is often not suitable for human consumption. lnstead,potable water is produced and packaged (bottled) centrally and single use containers/bot-tles are then distributed using a fleet of trucks or other vehicles to stores, for example gro-cery stores, where they are available for purchase. Other beverages than water, such as beer and soda are also provided in grocery stores.
This has several drawbacks. First, because a human consumes large amounts of drinkingwater, it is a hassle to shop and carry the necessary amounts of drinking water (or otherbeverage). I\/|oreover, single use containers need to be produced. After use, the single usecontainers are, at best, recycled and used as fuel in waste burning plants. At worst, single use containers becomes a part ofthe increasingly troubling world-wide trash problem.
Summary of invention The system devices and methods described herein provides beverage in a reliable and safemanner. Production and distribution of beverage can be timed and fine-tuned to suit de-mand and consumption at the individual or population level. Beverage production can be fine tuned to obtain a "virtual pipe" of beverage. ln a first aspect of the invention there is a beverage dispensing station adapted to support a portable beverage container, and connect to the beverage container such that beverage can be dispensed from said beverage container, said beverage dispensing station havingweight determining means for determining the weight of a beverage container supportedby said beverage dispensing station, the beverage dispensing station further comprisingcontrol circuitry comprising a memory and a wireless network interface, the dispensing sta-tion being configured to determine the weight of the reusable beverage container and to store the weight in the memory.
The system devices and methods described herein provides beverage in a reliable and safemanner. Production and distribution of beverage can be timed and fine-tuned to suit de-mand and consumption at the individual or population level. Beverage production can be fine-tuned to obtain a "virtual pipe" of beverage.
The weight determining means provide information about how much beverage is still in the container. This makes it easier to know when to switch the container.
The weight determining means comprises a strain gauge. A strain gauge is a reliable sensor for weight.
The beverage dispensing station may be configured to detect beverage dispensing, and con-figured to, to use the weight determining means to determine weight data or beverageconsumption data, when beverage dispensing has been detected. lt is more relevant to de-tect weight when dispensing has occurred. The beverage dispensing station may comprisean accelerometer and beverage dispensing may be detected by the accelerometer.
The beverage dispensing station may be configured to determine the weight after a prede-termined time period after beverage dispensing has been detected. This has the advantageof detecting when dispensing has finished. Also, a user may want to fill more than one glass.
This saves battery and memory space.
The beverage dispensing station may comprise an identity tag reader, configured to read an identity tag of a beverage container and to store the identity in the memory together with the weight data. A user may switch the beverage container. The tag reader ensures that theweight of one identified beverage container is determined.
The dispensing station may be configured to provide weight data or beverage consumptiondata to a server using the wireless network interface connection.
This allows for central coordination of deliver of beverage containers such that a server willknow when a container is about to run out of beverage. An order for a new container maythen be processed automatically by the server.
The beverage dispensing station may be configured to provide the weight data or the bev-erage consumption data to the server after a predetermined waiting time after beveragedispensing has been detected. lt is advantage if the beverage dispensing station uses as little power and data as possible.For example, a user may not want to replace a battery ofthe dispensing station. Also, datatraffic has a cost. Therefore, it is an advantage if several dispensing events can be commu- nicated to the server at the same time. The waiting time makes this possible.
The control circuitry of the beverage dispensing station may have a sleep state and a wakestate and may be configured to wake up from the sleep state when beverage dispensing is detected, and then to determine the weight of the beverage container. ln a second aspect of the invention there is provided a beverage distribution system com-prising: a plurality of beverage containers where each of the beverage containers are reus-able and portable and where each ofthe plurality of comprises an identity tag with a uniqueidentity, a server having stored, in a dataset, an identity of each of the plurality of beveragecontainers, a beverage dispensing station adapted to mechanically support one of the bev-erage containers, and connect to the beverage container such that beverage can be dis-pensed from the beverage container, said beverage dispensing station having weight deter-mining means, said beverage dispensing station further comprising an identity tag reader,and a wireless network interface, the dispensing station being configured to determine theweight ofthe beverage container presently supported by the dispensing station and furtherconfigured to use the identity tag reader to read the identity tag of a beverage container, and further configured to use the wireless network interface to provide the identity and the weight data or beverage consumption data to the server, the server being configured toreceive the weight data or beverage consumption data and the identity of the beveragecontainer and store the weight data or consumption data associated with the identity in thedataset.
This provides for centralized tracking and distribution of filled beverage containers. By ag-gregating data from a plurality of beverage dispensing stations, a central server is able to optimise beverage production or distribution. ln a third of the invention there is provided a method in a beverage dispensing stationadapted to mechanically support a portable beverage container, and connect to the bever-age container such that beverage can be dispensed from the beverage container,said beverage dispensing station having weight determining means, said beverage dispens-ing station further comprising an identity tag reader, and a wireless network interface, andan accelerometer, and control circuitry having a sleep state and a wake state, the methodcomprising the steps of:a) the accelerometer detecting movement, thereby waking up the control circuitry ofthe dispensing station from sleep, thenb) the weight determining means determining the weight of the beverage container,the tag reader reading the identity tag of the beverage container, and the controlcircuitry activating the wireless network interface, thenc) the beverage dispensing station providing weight data or beverage consumption data to the server using the wireless network interface.
The method provides for saving power in the beverage dispensing station while keeping the server updated about beverage consumption in the system.
Drawings The accompanying drawings form a part of the specification and schematically illustratepreferred embodiments of the invention and serve to illustrate the principles of the inven- tion.
Figs. 1 is a schematic drawing of a system.
Fig. 2 is a schematic drawing of a system.
Fig. 3a and 3b are schematic drawings of a beverage container.
Fig. 4 shows a beverage container.
Fig. 5 is a schematic drawing of a beverage dispensing station.
Fig. 6 shows a beverage dispensing station.
Fig. 7 is a beverage container in an upside-down position attached to a tap of a beveragedispensing station.
Fig. 8 is a beverage container supported to and connected to a beverage dispensing station.Fig. 9 is a cut away view of a beverage container and a beverage dispensing station.
Figs 10-11 are schematic top views of beverage dispensing station and beverage containers.Fig. 12 is a schematic drawing of parts of a beverage dispensing station.
Figs. 13-18 are flow charts showing methods.
Fig. 19 is a schematic drawing of control circuitry.
Detailed description The systems, methods and devices provided herein provide beverages at the point of con-sumption in a safe and reliable manner, in a "virtual pipe" manner. Hence safe beveragecan be produced and distributed to a consumer in a safe just-in time manner. Traceablecontainers and smart dispensing stations allow high-level monitoring of system 1 and its Va FlOUS COmpOHentS.
With reference to Fig. 1, the system 1 comprises a plurality of beverage containers 2 and a server 3. Beverage containers 2 are preferably reusable and portable. The system 1 may also comprise one or more beverage filling stations 4, one or more identification tag readers10, and one or more beverage dispensing stations 50. The beverage dispensing stations arefor example located in the homes of end-users, or at restaurants, bars, schools, hospitals,offices or other places of work, sporting facilities, or other places where it is useful to pro-vide beverage. Fig 1 also shows cell network 16 and wide area network 17, for example the internet.
The system 1 may comprise at least one beverage filling station 4 which is configured to fillreusable beverage containers 2 with beverage. Hence beverage filling station 4 may havemeans for producing, storing and filling beverage in containers 2 and for washing and stor-ing the containers 2. Hence beverage filling station 4 may comprise a beverage producingunit. The beverage producing unit may comprise a water purification unit 5 which is able topurify water using any suitable technology such as filters, heat, ultraviolet light or chemicalmeans. The beverage filling station 4 will be described in more detail below. ln various em-bodiment the system 1 may also receive pre-filled containers 2 from an outside source, and system may then comprise a beverage container storage 22 The beverage distributed in the system 1 is preferably water or beer. ln various embodiment the beverage is potable water. ln other embodiments the beverage is beer.
Looking at Fig. 2, the system 1 may comprise a plurality of beverage filling stations 4, suchas two, three, four, five or more filing stations 4, which will be described in more detail be-low. Each beverage container 2 may be logically associated in a dataset 15 with a certainfilling station 4 so that each filling station 4 has a "fleet" of beverage containers 2 and dis-pensing stations 50 (see below), as seen in Fig 2. Fig. 2 is a schematic drawing showinghow three different filling stations 4a, 4b 4c, each are associated with a fleet 70a, 70b, 70c of containers 2 and separate fleets 71a, 71b, 71c of dispensing stations 50.
With reference to Fig. 1 and 2, beverage filing station 4 may have a computer 19 that maybe in network communication with server 3. ln various embodiments computer 19 of filling station 4 provides information to a filling station user and may enable filling station user to monitor and manage his or her fleet of beverage containers 2 and dispensing stations 50.
Such a user may have access to only certain functions of the system 1.
Server comprises or has access to dataset 15, and dataset 15 will be described in more de-tail below. Server 3 may provide instructions to computer 19 regarding production of bev-erage and filling beverage into containers 2. Server 3 may be able to make predictions, us-ing data set 15, about beverage consumption in system 1 and use the predictions to pro-vide instructions to beverage filling station 4 regarding how much beverage should be pro-duced or how many filled beverage containers 2 should be produced. For example, whenan increase of demand is predicted, production may be increased. Server 3 may also com-prise a price determining mechanism for determining a price for a filled beverage con- tainer 2.
The system 1, for example server 3, may comprise resources for placing orders for bever-age containers 2, such as replacement of empty beverage containers 2, payment, bookingoftransport resources, and pricing determination mechanisms. End-users may be able tolog into system 1 with a user account and place an order for a beverage container 2 usinga mobile device, for example. Furthermore, server 3 may comprise logic that automatically ships beverage container 2 to a dispensing station 50 when needed.
Beverage is stored in tank 6 of beverage filling station 4. Beverage filling station 4 may alsocomprise a tap 14 and one or more areas for storage of beverage containers 2. Beveragefilling station 4 may also have a washing station 7. Water purification unit 5 may be con-nected to an inlet 8 for non-purified water from some water supply such as a lake, a riveror a utility that provides water. The filling station 4 may have an inlet or door (or both) foraccepting beverage containers 2 and for discharging them. The beverage filling station 4 is described in even more detail at the end of the description.
Beverage containers 2 are filled with beverage in filling station 4. Preferably they arewashed in washing station 7 before filing. The containers 2 then leave filling station 4 to be distributed to end-users.
End users typically have one more beverage dispensing stations 50. End-users may pick upbeverage containers 2 at filling station 4 or more preferably have the containers 2 deliveredto them. ln Fig. 1, T designates a beverage container 2 that is in transfer from filling station4 to a dispensing station 50. W designates a beverage container 2 that has just left thewashing station 7. S designates a storage of filled beverage containers 2 waiting fortransport to end-users (beverage dispensing stations 50). Washing station 7 may be orga-nized as a processing line where the beverage container 2 enters filling station 4, is washedin washing station 7 and then exits washing station 7. Hence filling station 4 may have ded-icated areas for storing containers 2, washing containers 2, and filling containers 2. Washing station 7 may be completely automatic or semi-automatic.
As used herein and "end-user" is a user that operates a beverage dispensing station 50. Enduser may buys filled beverage containers 2 or has filled beverage containers delivered to him/her. End-users may be able to order filled beverage containers.
A "server user" is a user that manages the system 1 in some respect. A server user has accessto the server 3 or parts thereof using a user interface. Server users may have different per-missions, such that some server users may have control over the entire system 1, whereasother server users have more limited access. Some users may only be allowed to controlone or a few beverage fillings stations (4a, 4b, 4c), as system 1 may comprise more than onefilling station 4, or a subset (70a, 70b, 70c) of beverage containers 2 or a subset (71a, 71b, 71c) of beverage dispensing stations 50 with reference to Fig. 2.
The reusable beverage containers 2 in the system 1 each have a unique identification tag9. The identity of the identification tag 9 is unique for each beverage container 2. Offcourse, by mistake there may be two or more containers 2 that have the same identity,but the purpose is that each beverage container 2 has a unique identity. Hence at leastsome ofthe plurality of beverage containers 2 have unique identities. The identity may be a unique combination of symbols such as digits or letters, for example a number.
A tag reader 10 is able to read the identity stored in the identification tag 9. In general,identification tag reader 10 can be of different kinds and is adapted to the kind of identifi-cation tag 9 used for the beverage container 2. For example, the tag reader 10 may beable to use induction to induce a current in circuits of the tag 9 to cause tag 9 to transmit asignal that can be detected by tag reader 10. It is preferred that the identification tag 9 isbe an RFID tag in particular of a type that can be read with the aid of NFC (Near Field com-munication) technology. The unique identification tag 9 may be for example a RFID tagwhich can be read by a RFID tag reader 10. Or the identification tag 9 may be a bar codethat can be read by a bar code reader. The identification tag 9 and the identification tagreader 10 may also be implemented using 5G technology, in which case the identificationtag 9 com prises a battery or other energy storage. It is preferred; however, the identifica- tion tag does not comprise a battery.
A schematic drawing of a beverage container 2 is seen in Figs 3a and 3b. A non-limiting ex- ample ofa container 2 made of stainless steel is shown in Fig. 4, and Figs. 7-9.
The plurality of reusable beverage containers 2 preferably have a volume of from 2 to 100litres, more preferably 3-30 litres and even more preferably 8 - 25 litres. The containers 2are preferably portable when filled with beverage. For example, the container 2 may havea handle 11 (Fig. 4) for carrying the container. The containers 2 are preferably made of stainless steel or a polymer material such as plastic. The material may be non-transparent.
The container 2 may have any suitable shape, for example a cylindric shape.
A different suitable shape and size may be the type of container used in "water coolers"frequently found in office spaces etc. The beverage container 2 is typically not designed to drink directly from.
The containers 2 should be easy to clean and have a low weight and be durable to allowuse many times. The number of use cycles is preferably predicted to be from 10 - 1000 foran individual container 2, where each cycle includes one filling the container 2 with at least some beverage and providing it to an end user.
The identification 9 is attached to the container 2 or is otherwise comprised in container2. For example, an NFC tag may be glued to the container 2 or a bar code may be in theform of an adhesive sticker attached to the outer surface ofthe container 2. A tag 9 mayalso be inserted into container 2 at production, for example during casting of a container 2 made of a polymer material.
The identification tag 9 is preferably attached to the container 2 in a permanent manner.
However, single use tags or limited time use tags 9 may also be used.
That the identification tag 9 is attached in a "permanent manner" means that it is in-tended to be attached to the beverage container 2 for the duration of the expected life- time of the beverage container.
The tag 9 preferably has a low weight and a small size. The weight of tag 9 is preferablynegligible compared to weight of container 2. This is also true for second tag 18 describedin more detail below. The weight of the identification tag 9 or second tag 18 is preferablyless than 50 grams, even more preferably less than 10 grams and most preferably less than 1 gram.
The beverage container 2 has at least one opening 12 for filling and tapping beverage. Theopening 12 is closable, for example with a lid 13. The lid 13 may be disposable or reusable.lt may be possible to pour beverage from the opening 12 which is then used as a spout.Alternatively, the beverage container 2 is attached to a beverage dispensing station 50 and beverage dispensed from the station 50, as described in more detail below.
The system 1 comprises a plurality of reusable beverage containers 2. The number of bev- erage 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. The tag reader 10, is preferably, as mentioned, an RFID or NFC tag reader and hence comprises 11 suitable hardware as is known in the art. The tag reader 10 may be arranged not to detecttags 9 that are beyond a certain distance, which may be 10 m, preferably 5 meters, 1 me-ter or 20 cm, more preferably 10 cm and most preferably 5 cm. Hence the tag reader 10may have detection distance limit. The specificity ofthe tag reader 10 may be increased byusing a directional antenna in the tag reader 10, as described in more detail below with reference to Figs. 10 and 11.
For example, the dispensing station may have a directional antenna that directs the zoneof detection 57 towards the intended position of the beverage container 2 on the dispens- ing station.
System 1 may comprise at least two different tag readers 10. The at least two tag readers10 may have different geographical locations, meaning that they are at least 20, morepreferably at least 100 meters apart. For example, one tag reader 10 may be at a fillingstation 4 or a beverage container storage 22 whereas one tag reader may be at a dispens-ing station 50. For example, tag readers 10 may be present in dispensing stations 50 at dif-ferent geographical locations in a geographical area such as a city, for example differenthomes of end-users. Hence the tag readers 10 may be present at stationary geographicalpositions. However, tag readers 10 may also be carried in trucks or cars used for distribu-tion of beverage containers 2 or manually carried by personnel involved in distribution of beverage containers 2.
The geographical position is preferably a known geographical position. The geographicalposition may be known by for example, storing the coordinates or an address in the dataset15. However, geographical positions are not necessarily known. Positions may be obtainedfor example, automatically by using positioning services (GPS), addresses of end users asknown from client registers in system 1, or by manually entering the positions. lt may besufficient, for example in the machine learning application of Fig. 17, to know the distancebetween various geographical positions, for example distances between a beverage filling station 4 and various beverage dispensing stations 50. 12 ln various embodiments at least one tag reader 10 is comprised in one or more a beveragedispensing stations 50. The tag readers 10 may be used by system 1 to detect that a bever-age container 2 is present at one of tag readers 10, for example present at the one of thedispensing stations 50. The tag reader 10 may be used in system 1 to detect that a bever-age container 2 is present at, supported by or connected to a certain dispensing station 50.
Tag reader 10 is in digital communication with the server 3. System 1 may use tag reader 10to gather useful information in dataset 15 about a certain beverage container 2. 1The infor-mation is at least that the beverage container 2 is present at the tag reader 10. The system1 may also use a tag reader 10 to record the state of a certain beverage container 2, forexample that a beverage container 2 is in a "washed" state, "present at beverage station" state or similar.
A tag reader 10 may be arranged to detect that a beverage container 2 is present at one ofthe tag readers 10, for example at beverage dispensing station 50, and provide that infor-mation to the server 3. This may be stored in dataset 15, preferably together with a time point for detection.
The tag reader 10 is preferably a part of a beverage dispensing station 50 or provided in abeverage filling station 4, and the tag reader 10 may use hardware and software ofthosecomponents to communicate with the server 3. However, tag reader 10 may also be inde-pendent from a filling station 4 or a beverage dispensing stations 50 such as the case maybe with a tag reader present at distribution centre comprising a beverage container stor-age 22 or present in a vehicle or carried by a person, such as a person that distributes bev-erage containers 2. Such independent tag reader 10 may each comprise a battery or otherpower source, a processor, a memory, and a wireless network interface, and control cir- cuitry (Fig. 19), and are capable of communicating with server 3. 13 Filling station 4 may have one or more tag readers 10. For example, a tag reader 10 maybe located in a frame on a door on beverage filing station 4 to detect movement in or outfrom the beverage filling station 4. As a further example, a tag reader 10 may be located atthe exit of the washing station 7. Various parts of all of beverage filling station 4 may havea dedicated Workflow so that a beverage container 2 moves from one part to the next, forexample, entering filling station 4, going through washing station 7, being filled at tap 14,being stored, and then exiting filling station 4 and tag reader 10 may be arranged to detectthe presence of the container 2 at the various stations or areas of beverage filling station 4.
The tag reader 10 may be for example be arranged so that is able to detect when a bever-age container 2 has left the washing station 7 and hence can be assumed to be clean. Forexample, when the tag 9 is an NFC tag the tag reader 10 is an NFC reader arranged at asuitable distance from exit of washing station 7 so that beverage containers 2 that havebeen washed (and not other beverage containers 2) are detected as the pass the exit ofwashing station 7. Similar arrangements may apply wherever tag reader 10 is placed in thesystem 1. Hence a tag reader 10 is placed in system 1 to ensure that the detected state can be determined with some certainty.
Tag reader 10 or a plurality of tag readers 10 may thus be arranged to detect beveragecontainer 2 as it passes various parts of system 1 and provide data about this to server 3,and server 3 may store such information in dataset 15. The server 3 receives the infor-mation from the tag reader 10 and may use the information to change a state of an indi- vidual beverage container 2 in dataset 15.
The server 3 may be able to combine the information (i.e., the identity of the beverage container 2) from the tag reader 10 with a predetermined piece of information associatedwith a certain tag reader 10. For example, an identity reading from a certain tag reader 10always determines a certain predefined state for a container 2. For example, reading from a certain tag reader 10 may change the state ofthe container 2 from "unwashed" to 14 "washed" for example, or from "in station" to "have left station" ("unwashed" may also be referred to "have entered station"), as described in further detail below.
Hence a tag reader 10 may have an identity in system 1. When the tag reader is part ofdispensing station 50, the identity ofthe tag reader is preferably the same as the identity of the dispensing station.
Detection of a tag 9 of a beverage container 2 by a tag reader 10 may for example result in the server 3 setting the state of the beverage container 2 in the dataset 15 to one ofthe following: a) the container 2 has entered the beverage filling station 4. b) the container 2 has been washed, c) the container 2 has been filled with beverage in the beverage filling station 4,d) the container 2 has left the beverage filling station 4, e) the container 2 is in distribution, f) the container 2 has been left with an end user of a beverage dispensing station50,g) the container 2 is present at a beverage dispensing station 50, h) the container 2 is not present at any beverage dispensing station 50.
States may be exclusive such that an individual container 2 can only have one state at atime. For example, a container 2 should not be able to be present at a beverage dispens-ing station 50 and not present at any beverage dispensing station 50. This may be pro- vided with logic in server 3, for example database logic.
The tag reader 10 may be able to read a plurality of tags 9 simultaneously or during ashort time. For example, if a truck loaded with a number of beverage containers 2, an RFIDtag reader 10 may be arranged to read the tags 9 of all the beverage containers 2 in the truck as the truck passes the RFID tag reader 10.
Returning to Fig 1, system 1 comprises server 3. As described below, server 3 may be a vir-tual server. Server 3 maintains or comprises a digitally stored dataset 15, which may be inthe form of a database. Any suitable form of database architecture, such as an SQL data-base, may be used. The identity of each beverage container 2 is stored in dataset 15. Da-taset 15 may maintain information that is particular to an individual beverage container 2such as for example information about when a container 2 was put into use in system 1,number of filling cycles, date of manufacture, make, etc. This information is associatedwith the identity of the beverage container 2. The dataset 15 may also comprise infor-mation about the current state ofthe beverage container 3 as recorded by tag reader 10 as described above. lt may also be possible, for a server user, to add containers 2 to database and then logi-cally associate them with a particular filling station 4. lt may also be possible to manuallyenter information into dataset 15, for example if a certain beverage container 2 is broken and/or has to be taken out of service.
Hence, the server 3 is configured to store data relating to the plurality of reusable bever-age containers 2 in a digitally stored dataset 15. Preferably the server 3 is also configured to store data relating to the plurality dispensing stations 50 in the dataset 15.
Server 3 comprises suitable logic components and software to carry out the methods asdescribed herein, such as but not limited to: a beverage consumption tracking module,beverage container tracking module, error detection logic, container error flagging mod-ule, dispensing prevention means 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 bev-erage container 2 in the dataset 15 (some of these will be explained in more detail below):type of beverage, beverage container 2 has been filled, amount of beverage left in bever-age container 2, number of filling cycles, date of manufacture, current position, beverage in container 2 should not be consumed, identity of second tag 18 (tampering tag), state of 16 second tag 18, the container 2 has entered the beverage filling station 4, the container 2has been washed in the beverage filling station 4, the container 2 has been filled with bev-erage in the beverage filling station 4, the container 2 has left the beverage filling station4, the container 2 is in distribution, the container 2 has been left with a user of a beveragedispensing station 50, the container 2 is present at a beverage dispensing station 50, iden-tity of filling station 4 to which the beverage container 2 belongs, the container 2 is notpresent at any beverage dispensing station 4, identity of a previous dispensing station 50the beverage container 2 has been associated with, dates of previous filing cycles, dateand time of tag readings, beverage dispensing events, beverage consumption data. These are non-limiting examples.
For example the following information may be associated with the identity of a dispensingstation 50 in the dataset 15: identity of current beverage container 2 present at dispensingstation 50, no beverage container 2 present, sensor data, beverage consumption data,communication log, flag for no changes since previous communication session, dispensingprevention means 65 are to be activated, dispensing prevention means 65 have been acti-vated, error messages, battery status, beverage dispensing events, sensor data, identity offilling station 4 to which the dispensing station 50 is associated, identity and contact de-tails of end user, log in details for end-user, order status etc. These are non-limiting exam- ples.
All data may be stored for previous events so that a history for each beverage container 2 and dispensing station 50 is stored in dataset 15.
Server 3 may comprise logic that detects errors with regard to a beverage container 2 or abeverage dispensing station. Hence an individual beverage container 2 should not be ableto change state directly from "unwashed" to "filled". Such a change (from "unwashed" to"filled") should only be allowed ifthe container 2 has been in the state "washed" after"unwashed". lf tag readers 9 provides such conflicting information, there is an error. Theerror may be detected by software in the server 3, for example by database software. The database software may for example be adapted to generate an error flag. Errors can be 17 detected in other ways for example the machine learning method of Fig. 17. An error re-garding a container 2 may lead to the generation of an error report by server 3 or maylead to that the container 2 is excluded from distribution. Exclusion may for example becarried out such that a certain container 2 is flagged to not be filled or not to be distrib-uted to an end-user. Warning may be provided as sound signals, or in a display or a flash-ing light in filling station 4, a message to end user or server user or activation of dispensing prevention means 56 (see below).
With reference to Figs. 1-2 and Figs. to 5-11, system 1 preferably comprises one or morebeverage dispensing stations 50. The dispensing station 50 is used for dispensing beverage from a beverage container 2.
Many different designs for the beverage dispensing station 50 are possible. The beveragedispensing station 50 of Figs. 6-9 comprises a free-standing housing 51 that supports thebeverage container 2 which is placed on top of the housing 51 with the opening 12 down-wards. A separate tap 52 is attached to the opening 12 and is used to control dispensingby the end user. Beverage may then be dispensed using gravity flow. Tap 52 comprises avalve (not shown), handle 66 for operating the valve and connector 54. The tap 52 rests ina V-shaped notch 53 of the housing 51. Again, this is just an example and tap 52 may alsobe integrated with housing 51. ln Figs. ln general, a tap 52 of a beverage dispensing station50 may be operated in any suitable way such as for example with by a push button, or anyother suitable means for controlling a valve. Tap 52 may for example comprise an elec- tronically controlled valve for dispensing beverage. ln general, the housing 51 may comprise control circuitry and various sensors such asweight determining means 55, accelerometer 56, battery 63, a LED light 64 and wireless network interface 58 as described below.
There are numerous possibilities for the design of dispensing station 50. Other possible designs include a design similar to a "water cooler" frequently found in office workspaces. 18 The dispensing station 50 may be suitable to stand on a bar, a table or a bench top or itmay be designed to be free standing on a floor or on the ground. The beverage dispensingstation 50 may also be integrated into furniture, in particular furniture suitable for kitch- ens, restaurants, and bars. The dispensing station 50 may also be integrated into a fridge.
Beverage may be dispensed from the dispensing station 50 as flowing beverage usinggravity flow or by providing pressure inside container 2. Figs. 6-9 show a beverage dis-pensing station 50 suitable for dispensing beverage with gravity flow. The beverage ispreferably dispensed from the beverage container 2 while being connected to the bever- age dispensing station 50, or while being supported to the beverage dispensing station 50.
When pressure is used, as may be the case with beer, the dispensing station 50 may com-prise means for pressurising the beverage container 2 as is known in the art. Typically, thebeverage dispensing station 50 then comprises means for providing pressurized carbon di-oxide (other inert gas) into the beverage container 2. The means for providing carbon di-oxide may comprise a first pipe that is inserted into the container 2 and provides pressur-ised carbon dioxide to drive the beverage out from the container 2 from a second pipe.The dispensing station 50 with use for beer may be designed so that the opening 12 ofcontainer 2 is directed upwards, and the dispensing station 50 or a part thereof may thenbe designed to rest on top of the container 2. ln particular, a connector for piping and means for providing carbon dioxide may rest on top ofthe opening 12.
Dispensing station 50 may be configured to mechanically support a beverage container 2.Hence, a part or the entire weight of beverage container 2 may rest on dispensing station50. Dispensing station 50 or a part thereof may be arranged to mechanically receive a bev-erage container 2. The beverage container 2 may be able to be mechanically connected tothe dispensing station 50, for example with the use of lugs, bayonet coupling, click-on orthreads or other connection means. The dispensing station 50 may be able to engage withthe beverage container 2. Preferably the dispensing station 50 is such that only one bever- age container 2 is supported by or connected to beverage dispensing station 50. 19 The container 2 can be mechanically connected to the dispensing station 50 such that bev-erage can be dispensed from the container 2. The dispensing of beverage preferably oc-curs through a part ofthe dispensing station 50. For example, the dispensing station 50 may have a connector 54 which connects to the opening 12 of the beverage container 2.
System 1 preferably comprises a plurality of dispensing stations 50, such as two, three,four or more dispensing stations 50, such at least ten or at least 100 dispensing stations50. Each dispensing station 50 may have a unique identity in system 1. The identity isstored in the dataset 15. A beverage dispensing station 50 is may be logically connectedto one certain beverage filling station 4, for example in dataset 15, as shown in Fig. 2. The logical connection may be in the dataset 15.
The beverage container 2 may be switched such that a first beverage container 2 that ismechanically connected to or supported by the dispensing station 50 is be replaced with asecond beverage container 2 which then becomes mechanically connected to, or sup- ported by, the dispensing station 50.
Looking at Fig. 12, beverage dispensing station 50 has control circuitry comprising amemory 60, a processor 61, and a bus 62. The control circuitry may be partly arranged ona printed circuit board (PCB). The control circuitry is electrically connected to the varioussensors, the tag reader 10, the wireless communication interface 58, the battery 63, theLED 64 and the dispensing prevention means 65, and. The control circuitry may comprise atimer and a clock. I\/|emory 60 stores software for pa rticipating in various methods de- scribed herein.
The dispensing station 50 furthermore may further comprise a battery 63 for poweringthe various electric and electronic components of the dispensing station 50 such as thecontrol circuitry, the sensors, the wireless network interface 58, tag reader 10 and the dis-pensing prevention means 65. Power may also be provided by a connector and a regular power outlet.
Beverage dispensing station 50 preferably has one or more sensors. The sensor ofthebeverage dispensing station 50 may for example be a weight determining means 55, anaccelerometer 56, or a beverage flow sensor. ln a preferred embodiment the dispensing station 50 has at least a weight determining means 55 and an accelerometer 56.
The beverage dispensing station 50 may have at least two sensors, a fist sensor that is ableto wake up the control circuitry from a sleep state to a wake state and second sensor thatdetermines the amount of beverage that is consumed. The first type of sensor may beable to wake up processor 61 with the use of an interrupt pin of processor 61, by provid-ing a signal to the interrupt pin. ln a preferred embodiment the first type of sensor is an accelerometer 56, and the second type of sensor is weight determining means 55.
Returning to Figs. 5 to 12, the dispensing station 50 preferably has a tag reader 10. The tagreader 10 is arranged to detect the identity of the beverage container 2 that is present atthe beverage dispensing station 50. Preferably the tag reader 10 is arranged to detect abeverage container 2 that is supported by or mechanically connected to the dispensingstation 50. Preferably the tag reader 10 of a dispensing station 50 only detects the tag of acertain beverage container 2 if the beverage container 2 is supported by the dispensingstation 50 or mechanically connected to the dispensing station 50 such that beverage can be dispensed from it.
The tag readers of Figs. 10 and 11 shows two different examples of how the tag reader 10can be arranged in a beverage dispensing station 50 (schematically shown from above)and only detects a beverage container 2 supported by the dispensing station 50. ln Figs 10 and 11 the beverage container 50 rests on dispensing station 50.
For example, the tag reader 10 may be NFC tag reader 10 that reads at a short distanceand in a certain direction, forming a field of detection 57 directed to the site where thebeverage container 2 is located on the dispensing station 50, see Fig. 10. A tag 9 outsidethe field of detection 57 is not detected by tag reader 10. The tag reader 10 of Fig. 11 has an even shorter range of detection, and only detects the tag 9 when the beverage 21 container 2 is oriented in the correct manner so that the tag 9 faces the tag reader 10. Thismay be achieved with the use of a directional fit between the beverage container 2 andthe dispensing station 50. For example, the correct orientation may be achieved with useof keying between the beverage container 2 and the dispensing station 50. The arrange- ments of Figs. 10 and 11 are examples only.
The tag reader 10 may be activated in various manners by the control circuitry ofthe dis-pensing station 50. For example, the tag reader 10 may read the tag 9 of the beverage container 2 at least every predetermined time period such as at least once every hour orevery day. The tag reader 10 may also be activated in various manners, such as by the ac- celerometer 56, or weight determining means 55, as described herein.
Furthermore, ifthe weight determining means 55 detects a weight but no tag 9 can be de-tected it may indicate that a false beverage container 2 is supported by dispensing station 50.
The beverage dispensing station 50 is in data communication with server 3, preferably us-ing at least partly wireless data communication. Hence the dispensing station has a wire-less communication interface 58. The wireless data communication may preferably beprovided by the dispensing station 50 acting as user equipment in cell network 16, such asa 3G, 4G or 5G cell network 16. However, other standards such as LoRa may be used.Hence the dispensing station 50 may have an antenna as a part ofthe wireless networkinterface 58 suitable for cell network communication, particular for acting as user equip-ment. Beverage dispensing station 50 may provide data from a sensor to the server 3,such as data from the tag reader 10, weigh determining means 55 accelerometer 56, tem-perature sensor 59 or flow sensor to server 3, as described below, using the data connec- tion.
The control circuitry ofthe dispensing station 50 may have a sleep state and a wake state,where the energy consumption is substantially lower in the sleep state. The control cir- cuitry may be woken up from the sleep state for example by a sensor, in particular the 22 first sensor. The control circuitry may go to sleep after a time of inactivity, for example af-ter more than 15 minutes of inactivity. The control circuitry ofthe dispensing station 50may be configured to wake up from sleep when dispensing is detected, for example by theaccelerometer 56 or the weight determining means 55. Weight determining means may be connected to an amplifier that amplifies the signal for this purpose.
Fig. 13 describes a communication session between a dispensing station 50 and server 3involving a tag reader 10 reading the tag 9 of a beverage container 2. A tag reader 10 thatis a part of the filling station 4 or an independent tag reader 10 carries out a communica-tion session with server 3 in a similar manner. ln step 100 the tag reader 10 in particular atag reader of a dispensing station 50, detects the tag 9 of an individual beverage container2. This involves reading the identity of the tag 9 which is also the identity of the beveragecontainer 2. The identity is stored in the memory 60 of the dispensing station 50, prefera-bly together with a time point for detection. Preferably other sensor data, such as datafrom weight determining means 55 or accelerometer 56 is also determined and stored,see below. Step 100 may be initiated by for example first sensor, such accelerometer 56or weight determining means 55, that wakes up the control circuitry of the dispensing sta-tion 50 from sleep or otherwise provides a signal to control circuitry that causes tag reader10 to read the tag 9. Step 100 may also by initiated by the end-user interacting with thebeverage dispensing station 50, for example switching on the beverage dispensing station with use of an on/off switch. ln step 101, the identity ofthe container 2 is provided to the server 3. Preferably the bev-erage dispensing station 50 uses the wireless network interface 58 for establishing a dataconnection to server 3. Preferably the identity of the dispensing station 50 is also provided to the server 3. The communication may be encrypted. ln step 102 the data is stored in the dataset 15 and associated in the dataset 15 with theappropriate beverage container 2 and dispensing station 50. Preferably the identity of thebeverage container 2 is associated with the identity of the dispensing station 50 in the da- taset. The server 3 may then verify the identity of the beverage container 2. For example, 23 that the beverage container identity is present in dataset 15 and not present at any otherbeverage dispensing station 50. An error message may be sent to a server user or a end-user if an error is detected, or the dispensing prevention means 65 may be activated, see below.
The data may also comprise a message from dispensing station 50 indicating that the dis-pensing station 50 works as intended. Such a check may be carried out by control circuitryofthe beverage dispensing station 50 at wake up or as scheduled. ln one embodiment thetransferred data comprises the identity of the dispensing station 50, the identity of thebeverage container 2 and a systems ok message. This may for example be provided as a text message (SMS message) from beverage dispensing station.
A communication session between the dispensing station 50 and the server 3 may com-prise one or mor ofthe following: dispensing station 50 identity, present container 2 iden-tity, battery status, dispensing events, weight, consumption data, other sensor data suchas data from accelerometer, temperature data, or a message that indicates no changesince previous session. A "no change" message is an efficient way of saving data traffic andpower. Sensor data such as accelerometer data, temperature data or data from weightdetermining means 55 may be associated with a time point for detection which is stored in the memory 60 ofthe beverage dispensing station 50.
Communication between dispensing station 50 and server 3 may be carried out at anysuitable schedule. For example, the dispensing station 50 may be configured to connect tothe server 3 at least every predetermined time interval such as, for example, at least every hour, every day or every week.
Table 1 below show a highly simplified and schematic example of dataset 15 showing theidentities of three different containers 2 and three different dispensing stations 50. Asmentioned, the dataset 15 may include many other types of data that are left out in this example. Table 1 shows how the same table is used for beverage containers 2 and 24 beverage dispensing station 50, but two or more tables with cross references may off course be used as the dataset 15 may be structured in any suitable manner.
ActivateIdentity of Remain- Last dis- disp. pre-Identity of bever- dispensing ing pensing vention Fillingage container station amount Battery status event means station10:55. Nov26, 2020,5647 2354 40% 73% 10:55 no 116:03, Nov1225 0122 83% 14% 10, 2020 no 107:32, Octnone 2355 n/a 99% 22, 2020 no 21002 none 100% n/a n/a n/a 2Table 1 2355 is an example of a beverage dispensing station that does not presently have a bever-age container 2. Beverage container 1002 is an example of a beverage container 2 that is presently not associated with any beverage dispensing station. ln various embodiments the dispensing station 50 comprises an accelerometer 56. The ac-celerometer 56 may be any type of useful accelerometer. The accelerometer may for ex-ample be of the type used in mobile phones, such as the iPhone. The accelerometer 56may be able to detect dispensing or movement of the dispensing station such as jolts orvibrations or changes in orientation or impact, such as ifthe dispensing station 50 falls tothe floor from a table. The accelerometer 56 may also be able to detect tampering. Accel-erometer readings above a certain threshold may indicate impact, caused by the dispens-ing station falling. Such accelerometer readings may trigger a self-test of dispensing sta-tion 50, and also a report to the server 3. The accelerometer 56 may have a threshold fordetecting movement so that background movements such as traffic does not trigger a sig- nal from the accelerometer 56.
A signal from the accelerometer 56 may be used to wake up the control circuity from sleep, for example a signal to an interrupt pin on the processor 61 ofthe control circuitry.
A signal from the accelerometer 56 may be used to active the wireless network interface 58 or to activate the weight determining means 55.
A signal from the accelerometer 56 may be configured to cause the tag reader 10 to readtag 9, for example as shown in steps 100-102 of Fig. 13. The accelerometer 56 provides asignal to the control circuitry that in turn activates the tag reader 10, which reads the tag 9ofthe beverage container in step 100, and stores the identity in the memory 60 ofthecontrol circuitry of the beverage dispenser 50. For example, this may be used to detect if abeverage container 2 has been replaced. lf a beverage container 2 has been replaced, theidentity of the new container 2 read by tag reader 10 is associated with the identity of the beverage dispensing station 50 in the dataset 15.
Accelerometer data may be stored in the memory 60 ofthe dispensing station 50, prefera- bly together with a time point for detection. ln various embodiments, the dispensing station 50 has weight determining means 55 fordetermining the weight of a beverage container 2 that is supported by the dispensing sta-tion 50. The weight determining means 55 may be of any suitably type. For example, astrain gauge type or a load cell may be used. Any suitable type of weight sensor may beused. For example, a metal beam that supports the beverage container 2 is fitted withstrain gauge that detects the strain in the beam. The weight determining means 55 mayalso comprise a piezoelectric crystal that provides voltage when a mass change provides a change in stress of the crystal.
The weight determining means 55 may be used to determine the amount of beverage incontainer 2. This information may be used by server 3 to determine when a container 2should be replaced. For example, when the weight of beverage container 2 supported bya dispensing station 50 is below a threshold weight, a new full container 2 is automaticallyshipped to the user of the dispensing station 50. Server 3 may comprise logic that com- pares the current filling level (weight) of a beverage container 2 with a threshold weight 26 and automatically provides an order to filling station 4 to produce and ship a new bever- age container 2 when the weight is below the threshold weight.
Information about consumption in dispensing stations 50 may also be used in an aggre-gated manner to track consumption of beverage from a plurality of dispensing stations 50.For example, the consumption for a subset 100a of dispensing station can be comparedwith the consumption of a different subset 100b (Fig. 2) of dispensing stations. Subsets may be selected based on geographical location, demography, or the like.
Beverage consumption data or weight data may also be used as described elsewhereherein for example in relation to machine learning, see below. lt should be noted that in-stead of weight determining means 55 a flow meter in the beverage dispensing station may be used.
Beverage consumption may be determined by control circuitry in dispensing station 50 orby server 3. For example, the dispensing station 50 may provide weight data to server 3which calculates the consumption. Typically, a weight after the latest dispensing event issubtracted from the weight after the previous dispensing event, to determine the differ-ence in weight. The difference is used as the beverage consumption of the dispensingevent. Or the dispensing station 50 may do the calculation and provide consumption datato the server 3. Or the dispensing station 50 may only report that the weight is below athreshold weight. Weight data may be filtered such that only differences above a certainthreshold is used in order to filter out noise. lt may be an advantage ifthe consumption orfiling level is determined by dispensing station 50 rather than server 3 in order to reduce data traffic in system 1 and data handling by server 3.
The following is an example of calculation of beverage consumption.
Initial total weight 11 kg Less tare weight: (container possibly tap shown in Fig.7): 1 kg Tared weight 10 kg 27 1st measurement: 9.8 kg * consumption: 0.2 kg.
Tare weight may be prestored in memory 60 of beverage dispensing station 50. The use ofa tare weight is optional, it may not be needed if it can be assumed that the initial weight is known, for example from the filling station 4.
Hence the weight data may be provided to the server 3 such as weight data, amount ofbeverage remaining in container 2, amount of beverage dispensed, or that that the weightis below a threshold weight has been passed or by triggering the delivery of a new con- tainer 2. All this is referred to as "weight data or beverage consumption data" herein.
The weight determining means 55 may be configured to determine the weight at leastevery predetermined time interval. For example, the weight determining means 55 maybe configured to determine the weight at least every week, every day, every hour, every minute or every second.
The dispensing station 50 may be configured to determine the weight or consumptionwhen dispensing has occurred. Dispensing may be detected with a separate sensor, suchas a flow sensor, or a mechanical switch that detects the position of tap 52. ln a preferredembodiment dispensing is detected with accelerometer 56. Hence a signal from the accel-erometer may activate the weight determining means 55. First sensor may also activate the weight determining means 55.
The accelerometer 56 is preferably arranged in dispensing station 50 such that dispensingbeverage from the beverage container 2 activates the accelerometer 56. The signal froman accelerometer 56 may be used to wake up the control circuitry to activate the weightdetermining means 55, for example by using an interrupt pin on a processor 61 of controlcircuitry. The accelerometer 56 may for example detect movement ofthe beverage dis-pensing station 50, beverage flow, movement of tap 52 or a cup detector. ln a preferred embodiment the accelerometer 56 detects movements of the dispensing station 50 itself 28 or the beverage container 2 attached to, or supported by, the dispensing station 50. Forexample, the accelerometer 56 may be attached to the housing 51 in order to detect vi- bration or movement of housing 51 that indicates dispensing.
System 1 may be configured to determine a dispensing event. A "dispensing event" com-prises at least information about an amount of beverage that has been dispensed from acertain beverage container 2 presently supported by or connected to a beverage dispens-ing station 50 or weight data for the beverage container 2. That the beverage container 2is present at beverage dispensing station may be detected by tag reader 10 of beveragedispensing station 10. Weight determining means 55 or a flow meter may be used for de-termining an "dispensing event". The dispensing event may be stored in the memory 60 ofthe control circuitry of the dispensing station 50. The dispensing event may be stored to- gether with a time point for dispensing. The dispensing event may trigger a timer. lt should be noted that "dispensing" means, herein, the fact that dispensing occurs orlikely occurs and may be detected with for example an accelerometer 56 and may not amount to a "dispensing event".
Weight data may be provided from the dispensing station 50 to the server 3 at any suita-ble interval, such at least every predetermined time interval, such as, for example, at leastevery week, every day, every hour or every minute. lt is an advantage if communicationtakes place as little as possible in order to save the battery 63 of dispensing station 50 and keep data traffic at a minimum. ln a preferred embodiment the weight determining means 55 is activated by the first sen-sor. The dispensing station 50 may be configured to activate the weight determiningmeans 55 after a predetermined waiting time. The predetermined time may be at morepreferably at least 10 seconds and even more preferably at least 1 minute and even morepreferably at least 5 minutes. This may be advantageous because the weight determiningmeans 55 preferably determines the weight of the beverage container 2 once dispensing has finished, which may take few seconds. Also, it may be desirable to store dispensing 29 into two mor more several glasses as one dispensing event, in order to reduce data han- dling in system 1.
The beverage dispensing station 50 may be further configured to establish a data connec-tion and provide weight data or consumption data to the server 3 after waking up, prefer-ably after a predetermined waiting time after waking up. The waiting time may be calcu-lated from wake up of the control circuitry or from the determination of the weight deter-mining means 55 and may be for example at least 10 seconds and even more preferably at least 1 minute and even more preferably at least 5 minutes.
The weight data or beverage consumption data is preferably provided to the server 3 to-gether with the identity of the beverage container 2 and the identity of the dispensing sta-tion 50. The dispensing station 50 may be configured to activate the tag reader 10 andread the tag 9 of the beverage container 2 each time the control circuitry is woken upfrom sleep, each dispensing event or each time the weight is determined, or each commu- nication session.
Fig. 14 shows a method involving a beverage dispensing station 50. lt should be notedthat the method shows a specific embodiment and that the steps of Fig.14 may comprisevarious separate embodiments of the current disclosure, and that the various embodi-ments may be combined in any suitable manner. For example, the first and second waitingsteps are separate embodiments. Furthermore, it should also be noted that that the tagreader 10 may be activated in any of steps 201 to 204 to read the tag 9 of the beveragecontainer 2. The control circuitry may also carry out other checks of the circuitry of dis-pensing station 50 such as check battery status, detect temperature etc. in any of steps 201 to 204. ln step 200 the first sensor wakes up the control circuitry from sleep. The fist sensor is preferably is an accelerometer 56 that detects movement. 202 is an optional first waiting step that awaits completion of dispensing. As describedherein, the control circuitry may have a timer. The predetermined time may be at least 10seconds, more preferably at least 1 minute and even more preferably at least 5 minutes.A longer waiting time ensures that dispensing has finished and may also be used to catch adispensing event made by a second person, which saves energy and computing power.However, it may be useful to have short waiting time to have more granularity in the dis- pensing data. ln step 203 the control circuitry activates the second sensor which preferably is weight de-termining means 55. The weight ofthe beverage container 2 is determined and stored andpreferably beverage consumption is calculated and stored in memory 60. The weight orconsumption data may be stored as a beverage dispensing event. The event may bestored together with a time point for dispensing. The second sensor may also be flow sen- sor, in which case the first waiting step 202 preferably is omitted.
Step 204 is an optional second waiting step. During step 204 any additional consumptionevents are stored in memory 60. The additional dispensing events may be detected, forexample, by the accelerometer 56 again activating the weigh determination means 55.The waiting period is more preferably at least 10 seconds and even more preferably at least 1 minute and even more preferably at least 5 minutes. ln step 205 the control circuitry provides the beverage consumption data or weight datato the server 3. Hence any previously non-reported dispensing evens are reported toserver 3. Other data may be provided to the server 3 such as the identity of the beveragecontainer 2, the identity ofthe dispensing station 50, and other sensors data. ln the samesession, other data may be transferred to the server 3 such as temperature, battery sta-tus, system ok message regarding beverage dispensing station, etc. The server 3 stores thedata in the dataset 15. The beverage dispensing station 50 may also, in the communica-tion session, receive information from server 3, such as activation ofthe dispensing pre-vention means 65, software updates etc. The wireless network interface 58 may be acti- vated at this step or in a previous step, for example step in step 201. 31 The method of Fig. 14 may use one or both or none of the optional waiting steps. Thewireless network interface 58 may be arranged to go to sleep after a certain time of inac- tivity.
The dispensing events are received by the server 3 and stored in the dataset 15. Theserver 3 hence can keep track of consumption of beverage. A threshold stored in server 3or in dispensing station 50 may be used to trigger the automatic delivery of a new bever-age container 2 to the end- user of a certain dispensing station 50. The threshold for deliv-ery may be determined based on shipping time and the speed of consumption. The speedof consumption may be calculated using dispensing events in dataset 15 for the dispensingstation 50 or a plurality of dispensing stations 50. For example, the average consumption for a time period may be used.
The beverage dispensing station 50 may have a temperature sensor 59 for detecting thetemperature of the beverage container 2 or ambient temperature in the vicinity of thebeverage dispensing station 50. The temperature may be used for triggering delivery of anew container 2. For example, if a beverage container 2 with beverage has been subjectfor high temperature for at time that is longer than a threshold time, this may trigger acti-vation ofthe dispensing prevention means 65 or delivery of a new beverage container 2.Temperature data may be stored in memory 60 of the control circuitry. The dispensingstation 50 may be configured to determine the temperature at least every predeterminedtime interval such as for example at least every hour, or at least every day. Temperaturedata may be stored in the memory 60 ofthe dispensing station 50, preferably togetherwith a time point for detection. Temperature readings may also be triggered by a dispens- ing event, first sensor, accelerometer 56 or weight determining means 55.
The dispensing station 50 may have a dispensing prevention means 65. The dispensingprevention means 65 prevents, to some extent, the dispensing of beverage from the bev- erage container 2 currently supported or connected to the dispensing station 50. The 32 beverage dispensing prevention means 65 is remotely controlled by server 3 via the con- trol circuitry of the dispensing station 50.
The dispensing prevention means 65 may provide a warning signal to a user of the dis-pensing station 50. The warning signal may be of any type such as visible, audible or tactilesignal. The warning signal may for example be a light on the exterior of the dispensing sta- tion, such as a LED 64. For example, a red light, or a flashing light.
The dispensing prevention means 65 may also lock the dispensing station 50 such thatbeverage cannot dispensed from it, such as locking the tap 52. For example, when the tap 52 includes a handle 66 the handle 66 may be locked in a closed position.
The dispensing prevention means 65 may be activated contents of a certain beverage con-tainer 2 is unsuitable for consumption, as detected manually or in an automatic mannerby system 1. For example, a server user may know that certain batches of beverage have anon-pleasant taste or is contaminated in some manner. System 1 may be able to detectfaulty containers 2 with any suitable method, for example the methods describes hereinwith reference to the machine learning method shown in Fig 17, temperature sensor 59,second tag 18 or error detection logic. For example, the fact that a that a non-authorizedcontainer is attached to the dispensing station, for example if the server 3 detects thatthat a beverage container identity received from a dispensing station 50 is not present inthe dataset 15, or the fact that a second tag 18 (tampering device) indicates that a bever- age container 2 has been tampered with.
I\/|oreover, temperature data from dispensing station 50 may be used to determine thatthe contents of an individual beverage container 2 is unsuitable for consumption. Temper-ature data from temperature sensor 59 may be reported to server 3 which may use thedata to determine that a beverage container 2 should be flagged for non-consumption.For example, ifthe temperature detected by temperature sensor 59 has been above a threshold temperature for a certain threshold time. 33 Thus, one or a plurality of beverage containers 2 may be flagged for non-consumption inthe dataset 15. This may be done manually or automatically as described above. The non-consumption flag may automatically trigger activation of dispensing prevention means 65 in the beverage dispensing stations 50 where flagged containers 2 are present.
The flag in dataset 15 is detected by server 3 in step 400 of Fig. 15. For example, logic atserver 3 may repeatedly scan dataset 15 for flagged containers 2. The server 3 identifies,in the dataset 15, the dispensing station 50 where a flagged container 2 is currently in use(step 401). The server 3 then uses the wireless network interface 58 of the dispensing sta-tion 50 to provide an activation signal to the dispensing prevention means 65 of the dis-pensing station 50, (step 402) which then activates the dispensing prevention means 65(step 403). The server 3 may have to wait for a communication event from dispensing sta-tion 50 in case the server 3 cannot be able to initiate communication with dispensing sta- tion 50.
As discussed above, the beverage container 2 has an identification tag 9 permanently at-tached to it. The permanent tag 9 is also referred to as "first tag 9" herein. The first tag 9 ispreferably an RFID or NFC tag. The first tag 9 stores the identity of the beverage container2. ln various embodiments, the beverage container 2 may have a second tag 18, which pref-erably is an RFID or an NFC tag. ln a preferred embodiment both first tag 9 and secondtags 18 are NFC tags. The second tag 18 is an antitampering device, arranged to detect if abeverage container 2 has been tampered with. Preferably each of the tags 9, 18 comprises at least one NFC antenna. Typically, the second tag 18 is disposable.
The second tag 18 has at least two states and can be attached to a beverage container 2 insuch a manner that opening the opening 12 ofthe beverage container 2 puts the secondtag 18 in the second state in a non-reversible manner. At least the first state can be de- tected by a tag reader 10. The second state can be a state where the second tag 18 cannot 34 be detected by tag reader 10 or where the signal from second tag 18 is altered in some way in relation to the first state.
The second tag 18 is attached to the opening 12 of a filled beverage container 2 in such amanner that opening the opening 12 of beverage container 2 necessitates altering thestate of the second tag 18 in a non-reversible manner. For example, removing the lid 13necessitates putting the second tag 18 in the second state. The second tag 18 may for ex-ample have an antenna that breaks when the opening 12 is opened, for example when thelid 13 is removed. For example, the antenna is broken in two parts. For example, the sec-ond tag 18 may be in the form of a sticker with an NFC antenna that is placed across thelid 13 and a part of container 2 so that removing the lid 13 necessities breaking the NFC antenna (Fig. 3b).
Regarding the term "non-reversible" it should be noted that, in some cases, a highly skilledexpert with access to the correct tools and equipment may be able to restore the secondtag 18 to the fist state, but it is still to be regarded as "non-reversible" because an average end user is not able to do that.
The second tag 18 may for example be in the form of a sticker or a loop. Part of the sec-ond tag 18 may be made from a polymer material into which an NFC antenna is inte-grated. An example of such a system is the CircusW' tamper loop provided by Avery Den-nison. The second tag 18 may be of a type that is completely destroyed such that an NFCtag reader 10 does not receive any signal from the second tag 18. Or the second tag 18may be of a type where the signal is altered but still present in the second state. This maybe achieved by the second tag 18 having two antennas, one which is broken in the secondstate and one which is still functioning in the second state. This increases the reliability be-cause the still-functioning antenna serves as a control that, for example, tag reader 10 works as intended.
The second tag 18 may store an identity of the second tag 18. The identity of the second tag 18 may be stored together with the identity of the beverage container 2 (first tag identity) in the dataset 15. Hence any tampering information will be associated to theidentity ofthe beverage container 2. For example, when a beverage container 2 is deliv-ered, it is useful to known that the container 2 was delivered in a non-tampered state, andthat the specific container 2 is now connected to the beverage dispenser 50. This is partic-ularly useful when a second tag 18 that is completely destroyed (quiet) in the second statebecause otherwise it is difficult to known that that a container 2 that was delivered in anon-tampered state to the end-user is now connected to the beverage dispenser 50. Formachine learning-assisted tracking of beverage containers 2 it is also useful to know if asubset of containers (associated with a certain beverage filling station 4, for example) are tampered with.
The second tag 18 may be applied to a container 2 with the use of the method shown inFig. 16. ln step 700 an empty beverage container 2 is provided. The beverage container 2has an opening 12 that can be closed as described above. The beverage container 2 has afirst tag 9 permanently attached, and the first tag 9 stores an identity of the beverage con-tainer 2. Preferably the container 2 is clean and the "washed" state. ln step 701 the bever-age container 2 is filled so that it contains at least some beverage. The container 2 is thenclosed, for example by attaching the lid 13. ln step 702 the second tag 18, in the first state,is attached to the beverage container 2 in such a manner that opening the opening 12 ofthe beverage container 2 non-reversibly puts the second tag 18 in the second state. Thisis preferably done in a controlled environment so that no tampering occurs in between. lnstep 703 the state of the second tag 18, which typically is now in the first state, is stored inthe dataset 15. The state is stored together with the identity of the first NFC tag 9, i.e. theidentity ofthe beverage container 2. ln step 704, which may be carried out before, afteror simultaneously with step 703, an identity of the second tag 18 is stored, in the dataset15, together with the identity of the beverage container 2. The beverage container 2 may then be shipped to end-users.
A tag reader 10, for example a portable tag reader used by delivery service may be used toconfirm that a non-tampered container is delivered to an end user. The tag reader 10 may provide this information to server 3 which stores the information in the dataset. This 36 provides information that a non-tampered container 2 has been delivered to the end-user.
Delivery may be confirmed by the end-user by various means such as signature, for exam-ple an electronic signature. lf the second tag 18 is the second state, a new container 2 may be automatically shipped to the end user by server 3.
The end user may then install the container 2 at the dispensing station 50, such that thetag reader 10 of the dispensing station can read the first tag 9 and the second tag 18. Thetag reader 10 of the dispensing station 50 may then read the identity of the first tag 9 andconfirm that the second tag 18 is in the second state, and report this to the server 3. Thetag reader 10 of the dispensing station 50 may read the second tag 18 and store the statein the memory 60 ofthe dispensing station 50. The tag reader 10 of dispensing station 50may store the identity of the first tag 9 and the identity of the second tag 18 (if second tag18 has an identity) and store these together with the state (first/second) in memory 60. lfthe second tag is not detected and the second tag 18 is of the type that is automaticallydestroyed by the tag reader 10, the dispensing station may store information that the sec-ond tag 18 is in the second state if no tag is detected. Hence, the tag reader 10 attemptsto read second tag 18 but does not get a reply and thereby assumes that second tag 18 is in the second state.
The method may comprise the step, if a tampered container 2 has been delivered, to flagthe container 2 for non-use in the dataset 15. Hence there may be logic in server 3 thatdetermines that allows only containers 2 that have been delivered in a non-temperedstate (in the first state) to be associated with dispensing station 50. lf such a container 2 ispresent at a dispensing station 50 the server 3 will receive the identity as described else-where, as a dispensing station 50 reports the identity of the beverage container 2 to the Se FVeF. lf a server 3 detects that tampered container 2 is present at a dispensing station 50, theserver 3 may be configured to take different actions. For example, the dispensing preven-tion means 65 may be activated. A message may be sent to the end-user about the tam- pering, for example that the end-user should not consume the contents. 37 Tag reader 10 of dispensing station 50 is preferably able to read the second tag 18 in thesame manner as it can read the identification tag 9. For example, the embodiments shown in Figs. 10-11 may be used for the second tag 18 as well as the first tag 9.
Server 3 may comprise or be in digital communication with machine learning service 20.I\/|achine learning service 20 may apply machine learning to the dataset 15 to obtain a de-cision rule. I\/|achine learning service 20 is able to detect patterns to produce a decisionrule that is useful for managing the system 1, for example with regard to: a) demand forbeverage, b) demand of logistics, i.e., distribution of beverage containers 2, c) errors orbottlenecks in system 1 or various components of system 1, e) determine end of life forbeverage containers and f) detecting beverage containers 2 that should not be consumedby an end-user. A user of server 3 may use machine learning to forecast behaviour of sys- tem 1 and their (sub)-users.
There are many possibilities. Here are a few hypothetical examples: 1. There is always a surge in beverage demand on Wednesdays. This can be used toincrease production of filled beverage containers 2 beforehand. 2. Beverage containers keep breaking down at one certain filling station 4. This infor-mation can be used to visit this filling station 4 to take care ofthe problem. 3. A certain user pattern for beverage containers 2, for example number of filling cy-cles, length of transportation, or other parameter, makes them break earlier thanother containers. Beverage containers 2 that fulfil these criteria, for example anumber of filling cycles, or total length of transport, may be detected and takenout of use before they break. 4. One individual beverage container 2 departs from a pattern. This may indicate thatthe container 2 has been tampered with or is a fake container, provided by a non-authorized source. For example, a fake container ID has been created or the ID of a "true" container 2 has been cloned and the container 2 has then been inserted in 38 the system 1, for example been attached to a beverage dispenser 50. Hence, the decision rule may also be used for detecting fraudulent behaviour.
Parameters that may be useful and to be included in the data set 15 include: number offilling cycles, length of transportation, length of time that container 2 spends at an end-user, date of manufacture of beverage container 2, production batch number of beveragecontainer 2, time spent in storage, data from sensors (such as weight determining means55 or accelerometer 56) of dispensing stations 50, manually or automatic recorded errorsor failures of containers 2 and dispensing stations 50, means of transportation and combi-nations ofthese. Any data in dataset 15 may be used. Information for machine learningmay also be provided from external information providers, for example information aboutweather, temperature at end-users, or during transport or during storage, humidity etc.
These are just non-limiting examples, as there are many possibilities. ln particular the decision rule may be used to determine a statistical model and to detect abehaviour of an individual beverage container 2 that departs from the statistical model.This may indicate that the beverage container 2 has been tampered with, that the identityofthe beverage container 2 is fake, or that an identity of a beverage container 2 has been cloned or stolen.
The following are hypothetical examples used to illustrate how machine learning may beused to identify strange behaving beverage containers 50: - Abnormal shipping speeds for beverage container 2 to dispensing station 50 (tooshort times may indicate multiple IDS, too long time may indicate that the bever-age dispenser has been tampered with) - Beverage container 2 is absent from system for a prolonged time (may indicatetampering) - Abnormal accelerometer data (may indicate tampering) 39 However, it should be kept in mind that the decision rule may be considered as a "blackbox" and it is difficult and maybe not even meaningful to speculate in which parameters are predictive for indicating tampering or other faults in beverage containers 2.
I\/|achine learning predictions are improved when the dataset 15 comprises informationabout a large number of beverage containers 2 that have been accumulated over time.I\/|achine learning is improved when the containers 2 are similar or identical, or at leastcomparable. The same is true of filling stations 4 or dispensing stations 50. I\/|achine learn-ing may be provided from a machine learning service 20 such as Amazon or may be pro-vided in the server 3. Any useful type of machine learning may be used, such as for exam- ple machine learning implementing Bayes' theorem.
Applying machine learning may result in a statistical model for behaviour for the pluralityof beverage containers. The decision rule may be that any container 2 that departs fromthe behaviour should be taken out of service. There may be a threshold for how much a container 2 may depart from the statistical model before being taken out of service.
With reference to Fig. 17 a method may comprise the steps of step 800: applying machinelearning to the dataset 15 to obtain a decision rule. The decision rule can be updated byapplying machine learning at any useful interval, such as for example daily, weekly ormonthly. ln step 801 the decision rule is applied to the dataset 15. This is also carried outat any suitable time interval but typically more often than the decision rule is updated,such as hourly or daily. The decision rule may be applied to a part of dataset 15. For ex-ample, machine learning may be applied on data for beverage containers 2 that has beentaken out of use whereas the decision rule is applied to beverage containers 2 that arecurrently in service only. The dataset 15 is typically updated often, preferably in real time.So, the dataset 15 will change over time. ln step 802 a decision is taken. lt may be a deci-sion with regard to an individual beverage container 2, for example that a certain bever-age container 2 should be taken out of service, or that the contents ofthe beverage con- tainer 2 should not be consumed. An individual container 2 may be flagged in the dataset for taking out of service. This may trigger manual alarm at the server 3 to a server user.
This may also trigger activation ofthe dispensing prevention means 65. ln the same manner machine learning may be applied to the dataset 15 to predict errors of beverage dispensing stations 50.
System 1 may comprise one or more beverage fillings stations 4 for filling beverage con-tainers with beverage. The beverage filling station 4 may for example be located in a suita-ble building. However, in certain embodiments, beverage filling station 4 may wholly orpartly be located in a filling station container 21. This provides for fast expansion of thesystem, where one or more filling station containers 21 fitted with filling stations 4 are de- ployed.
The filling station 4 may comprise a beverage production unit. The beverage production unitmay be computer controlled such that a computer 19 controls tanks, dispensers, valves,pumps, heaters, and coolers in a predetermined sequence to provide an automatic brewingor beverage production process. Computer 19 may also control a cleaning process when the beverage has been prepared or on a predetermined schedule (Clean-in-place).
The beverage production unit may be adapted to provide any type of beverage such as po-table water, beer or soda, or cider. ln one preferred embodiment the beverage is beer. ln one preferred embodiment the beverage is potable water.
The beverage production unit may comprise water purification unit 5. The water purifica-tion unit 5 may use any suitable technology such as filters, heating, UV irradiation or addi-tion of chemicals such as chlorine. The beverage production unit may also comprise a de- salination unit for removing salt from the water.
The beverage production unit may also provide a unit for adding various ingredients suchas flavouring, such as syrup for providing a soda, and carbon dioxide. Beverage may be pro- duced continuously or in a batch process and stored in tank 6. 41 Beverage production unit preferably has at least one sensor for sensing for example, flow,temperature, pressure, or level in the beverage production unit. ln general, the sensor maybe able to provide data to computer 19 and to server 3. Sensor data and production datamay be stored in dataset 15. Computer 19 of beverage filling station 4 may be connected toa data network communication device which enables data communication with server 3.Computer 19 may also comprise memory, processor and bus. Computer 19 is preferably connected to tag reader 10 of beverage filling station 4.
The memory of computer 19 of the beverage filling station 4 may have at least one set ofinstructions in digital form for producing a beverage. The computer 19 may have access toa plurality of instructions, one for each type of beverage, such as different types of beer.The digital instructions (recipes) may be provided from server 3 to computer 19. Computer19 may have a user interface, which a user may use to, for example, start or stop brewingprocedures. The user interface may comprise a display and input means, such as a keyboard,a mouse, joystick, touchscreen, or the like. Alternatively, a user of beverage filling station 4may be able to use a mobile phone as interface for example by connecting to computer 19 via server 3 or directly connecting to computer 19.
Computer 19 may be able to receive an order from server 3 to produce beverage, for exam-ple if server 3 detects or predicts a demand for beverage. Hence computer 19 may be able to activate the beverage production unit, for example to produce beer or potable water. ln a preferred embodiment the beverage filling station 4 is arranged such that a tag reader10 is arranged in relation to the washing station 7 to detect the tag 9 of a beverage con-tainer 2 only when the beverage container 2 has passed through the washing station 7.For example, the tag reader 10 is placed in close proximity to the exit of the washing sta-tion 7. This provides automatic tracking of washed containers 2 and makes sure that only washed containers 2 are flagged with the "washed" state.
With reference to Fig. 18 the method may comprise the steps of 900, detecting the bever- age container 2, step 901 the tag reader 10 providing the identity ofthe beverage container 42 2 to the server 3. This is done via computer 19 which is in network communication withserver 3. ln step 902 the server 3 sets the state of the beverage container 2 to "washed" inthe dataset 15. The server 3 may set the state to "washed" because the tag reader 10 isassociated with this state at sever 3 such that an identity of the tag reader 10 is associatedwith the washed state in the dataset 15. Or, the ability to set the washed state is storedwith the tag reader 10, which provides a washed state message to the server 3 together with the identity of the beverage container 2.
Similar rules may be applied anywhere in the system where they are useful and may for example involve two or more tag readers 10. ln an even more preferred embodiment, system 1, in particular filling station 4 provides atleast three tag readers 10: one that provides an "unwashed" state (or "entered station"state), one that provides "washed" state, and one that provides a third state that may be "filled/ready to deliver" state.
As mentioned, server 3 may have logic that detects errors such as erroneous transfer from"unwashed" state to the "filled" state without passing "washed" state. When an error hasoccurred, an individual beverage container 2 may be flagged in dataset 15 to be taken outof service or to be reprocessed, for example to be taken back to beverage filling station 4to be washed and filled again. Also, beverage dispensing prevention means 65 of dispensingstation 50 may be activated ifthe containers 2somehow is delivered to a dispensing station 50.
The filling station 4 may be contained in a filling station container 21. The filling stationcontainer 21 is preferably ofa size such that the beverage filling station 4 can be transportedusing a truck or trailer, or similar. Hence the filling station container 21 may be movable.For example, it may have the dimensions of a prefabricated shipping container. The fillingstation container 21 may have the dimensions of a standard intermodal shipping container.Standard ISO shipping containers are 8ft (2.43m) wide, 8.5ft (2.59m) high and come in twolengths; 20ft (6.06m) and 40ft (12.2m). The filling station container 21 may be made of steel 43 or other strong material such as aluminium, glass fiber, plastic, plywood, or similar material.The filling station container 21 is preferably self-supporting. Filling station container 21 mayhave any suitable shape where a rectangular block shape or approximately such a shape ispreferred. The rectangular block may have dimension that are approximately: height 2-3 m,width 2-3 m and length 3-12 m. lt may be possible for a user to enter into the filling stationcontainer 21, for example by walking into the filling station container, in order to service the beverage preparation unit or to make input into computer 19.
The filling station container 21 may be adapted to be placed on the ground or on a floor.The filling station container 21 may have an essentially flat underside for placing the fillingstation container 21 on flat ground or on a floor, but filing station container 21 may be provided with feet or rails for placing on an uneven surface.
Filling station container 21 may have a suitable arrangement for lifting the filling stationcontainer 21 by a crane or otherwise moving the filling station container 21 Hence, the fillingstation container 21 can be transported to the intended location and easily become con- nected and provide beverage in a short time.
Filling station container 21 is preferably suitable for being placed outdoors. Hence the fillingstation container 21 may have suitable proofing against one or more ofthe following: heat,cold temperatures, rain, lightning, snow or strong winds, in order to protect the variouscomponents of the filling station container 21 or provide a controlled environment for bev-erage production. The walls (including roof and bottom) of filling station container 21 mayhave thermal insulation. The walls may be rainproof and windproof. The bottom of thefilling station container 21 is suitable for being placed on the ground and may be proofedagainst rain and water seepage. The walls of the filling station container 21 may have a totalthickness, including insulation, of at least 2, cm more preferably at least 4 cm and mostpreferably at least 6 cm. ln one embodiment the filling station container 21 is a regularintermodal shipping container provided with internal thermal insulation. Filling station con-tainer 21 may be provided with arrangements for proving a controlled temperature and humidity inside the filling station container 21, such as a heater, cooler, air conditioner, 44 humidifier or dehumidifier. The computer may be arranged to control the internal condi-tions of filling station container 21 and keep for example temperature or humidity within a predetermined range.
The filling station container 21 is preferably connectable to external power supply, a watersupply and sewage and may preferably be provided with suitable pipes and wiring to enableeasy connectivity. Walls of filling station container 21 may have suitable bushings for vari-ous connections or ports for various utilities such as electricity, water, sewage and datacommunication. The filling station container 21 may have a pump for providing suctionfrom a water source such as, the sea or a lake or a river to provide water. Walls of fillingstation container 21 may have suitable bushings for various connections or ports for various utilities such as electricity, water, sewage, and data communication.
The beverage filling station container 21 is preferably connectable to external power supply,a water supply and sewage and may preferably be provided with suitable pipes and wiring to enable easy connectivity.
Filling station container 21 may in particular comprise water purification unit 5, beverageproduction unit, beverage tank 6, one or more tag readers 10, computer 19 and washing station 7. lt is understood that the present methods, systems and devices are partly computer-imple-mented, using digital computer equipment. The various embodiments and components de-scribed herein such as server 3, beverage dispensing station 50, tag reader 10, filling station4, computer 19, machine learning service 20 and communication between these compo-nents uses digital computer technology for storing and handling digital information and sig-nals as well as suitable hardware and software, including for example suitable digital pro-cessors, digital memories, input means, output means, buses and communications inter-faces. A user may be able to make input using for example a keyboard, a mouse or a touch screen. Output may be provided on for example a display.
The various components, such as server 3 and computer 19 may each have an operatingsystem. The server 3 may have a user interface that a server user can use to add new bev-erage containers 2, analyse data etc. With reference to Fig. 19 each of tag reader 10, server3, computer 19 and machine learning service 20 may comprise control circuitry comprising a memory 80, a processor 81 a bus 82 and a communication interface 83.
Server 3 may be one physical server or may be a virtual server. Function of sever 3 mayhence be distributed across several physical entities. Data, such as dataset of dataset 15may be stored in a datastore or in server 3. Dataset 15 may be stored in a distributed data- base comprising several nodes.
The methods herein can be implemented any suitable combination of software and hard-ware. Any suitable programming language may be used for the software units and methodsdescribed. Data communication in system 1 may be implemented using suitable networkingtechnologies and protocols, inducing cellular communication such as 3G, 4G and 5G, LoRa,Wi-Fi or Bluetooth, or Ethernet. Data communication can be wireless, or wire bound. Infor-mation may be exchanged over a wide area net such as internet 17. Data communication in system 1 may be encrypted.
The identity of the each of the beverage containers 2 and the dispensing stations 50 maycomprise any suitable combination of numbers, letters or other symbols suitable for digital data processing. Each of filling station 4 in system 1 may also have an identity.
Communication in system 1 and update of dataset 15 may be carried out using any suitableschedule. Tag readers 10 and dispensing station 50 may provide information to rest of sys-tem 1 in particular sever 3, for example immediately when a beverage container 2 is de-tected by tag reader 10 or when a sensor of dispensing station 50 detects a value. Commu-nication sessions may alternatively be scheduled to be carried out at a suitable interval, forexample at least every predetermined interval such as at least every second, at least every minute, at least every hour or every day 46 lt is realized that everything which has been described in connection to one embodiment isfully applicable to other embodiments, as compatible. Hence, the invention is not limitedto the described embodiments, but can be varied within the scope of the enclosed claims.While the invention has been described with reference to specific exemplary embodiments,the description is in general only intended to illustrate the inventive concept and should notbe taken as limiting the scope of the invention. The invention is generally defined by the claims.

Claims (6)

1. A beverage dispensing station adapted to support a portable beverage container,and connect to the beverage container such that beverage can be dispensed fromsaid beverage container, said beverage dispensing station having weight determin-ing means for determining the weight of a beverage container supported by saidbeverage dispensing station, the beverage dispensing station further comprisingcontrol circuitry comprising a memory and a wireless network interface, the dis-pensing station being configured to determine the weight of the reusable beverage container and to store the weight in the memory.
2. The beverage dispensing station according to c|aim 1 where the weight determin- ing means comprises a strain gauge.
3. The beverage dispensing station according to any one of c|aims 1 to 2 configuredto detect beverage dispensing, and configured to, to use the weight determiningmeans to determine weight data or beverage consumption data, when beverage dispensing has been detected.
4. The beverage dispensing station according to c|aim 3 comprising an accelerometer and where beverage dispensing is detected by the accelerometer.
5. The beverage dispensing station according to any one of c|aims 3 or 4 configuredto determine the weight after a predetermined time period after beverage dis- pensing has been detected.
6. The beverage dispensing station according to any of c|aims 1 to 5 comprising anidentity tag reader, configured to read an identity tag of a beverage container and to store the identity in the memory together with the weight data.The dispensing station according to claim 1 which is configured to provide weightdata or beverage consumption data to a server using the wireless network inter- face connection. The beverage dispensing station according to claim 7 configured to provide theweight data or the beverage consumption data to the server after a predetermined waiting time after beverage dispensing has been detected. The beverage dispensing station according to any of claims 1 to 8, where the con-trol circuitry has a sleep state and a wake state, where the control circuitry is con-figured to wake up from the sleep state when beverage dispensing is detected, and then to determine the weight of the beverage container. A beverage distribution system comprising: a plurality of beverage containers where each of the beverage containers are reus-able and portable and where each of the plurality of comprises an identity tag witha unique identity, a server having stored, in a dataset, an identity ofeach of the plurality of beveragecontainers, a beverage dispensing station adapted to mechanically support one of the bever-age containers, and connect to the beverage container such that beverage can bedispensed from the beverage container, said beverage dispensing station having weight determining means, said beveragedispensing station further comprising an identity tag reader, and a wireless net-work interface, the dispensing station being configured to determine the weight ofthe beverage container presently supported by the dispensing station and furtherconfigured to use the identity tag reader to read the identity tag of a beveragecontainer, and further configured to use the wireless network interface to provide the identity and the weight data or beverage consumption data to the server,the server being configured to receive the weight data or beverage consumptiondata and the identity ofthe beverage container and store the weight data or con- sumption data associated with the identity in the dataset. A method in a beverage dispensing station adapted to mechanically support aportable beverage container, and connect to the beverage container such that bev-erage can be dispensed from the beverage container, said beverage dispensing station having weight determining means, said beveragedispensing station further comprising an identity tag reader, and a wireless net-work interface, and an accelerometer, and control circuitry having a sleep stateand a wake state, the method comprising the steps of: a) the accelerometer detecting movement, thereby waking up the control cir-cuitry of the dispensing station from sleep, then the weight determining means determining the weight of the beverage con-tainer, the tag reader reading the identity tag of the beverage container, andthe control circuitry activating the wireless network interface, then the beverage dispensing station providing weight data or beverage consump- tion data to the server using the wireless network interface.
SE2051541A 2020-12-22 2020-12-22 Beverage dispensing station with weight determining means SE545375C2 (en)

Priority Applications (13)

Application Number Priority Date Filing Date Title
SE2051541A SE545375C2 (en) 2020-12-22 2020-12-22 Beverage dispensing station with weight determining means
IL303958A IL303958A (en) 2020-12-22 2021-12-22 Beverage dispensing prevention
US18/258,216 US20240002209A1 (en) 2020-12-22 2021-12-22 Beverage dispensing prevention
US18/258,229 US20240076178A1 (en) 2020-12-22 2021-12-22 Machine learning in a beverage distribution system
JP2023561923A JP2024503143A (en) 2020-12-22 2021-12-22 Beverage distribution prevention
PCT/EP2021/087377 WO2022136587A1 (en) 2020-12-22 2021-12-22 Machine learning in a beverage distribution system
AU2021405750A AU2021405750A1 (en) 2020-12-22 2021-12-22 Beverage dispensing prevention
KR1020237025238A KR20230136601A (en) 2020-12-22 2021-12-22 No provision of beverages
PCT/EP2021/087388 WO2022136595A1 (en) 2020-12-22 2021-12-22 Beverage dispensing prevention
PCT/EP2021/087386 WO2022136593A2 (en) 2020-12-22 2021-12-22 Beverage dispensing station with weight determining means
EP21840632.0A EP4268153A1 (en) 2020-12-22 2021-12-22 Machine learning in a beverage distribution system
PCT/EP2021/087252 WO2022136528A1 (en) 2020-12-22 2021-12-22 System with smart beverage dispensing stations
EP21844714.2A EP4268154A1 (en) 2020-12-22 2021-12-22 Beverage dispensing prevention

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
SE2051541A SE545375C2 (en) 2020-12-22 2020-12-22 Beverage dispensing station with weight determining means

Publications (2)

Publication Number Publication Date
SE2051541A1 true SE2051541A1 (en) 2022-06-23
SE545375C2 SE545375C2 (en) 2023-07-25

Family

ID=82402572

Family Applications (1)

Application Number Title Priority Date Filing Date
SE2051541A SE545375C2 (en) 2020-12-22 2020-12-22 Beverage dispensing station with weight determining means

Country Status (1)

Country Link
SE (1) SE545375C2 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150109143A1 (en) * 2012-05-24 2015-04-23 SteadyServ Technologies, LLC Draft beer supply chain systems and methods
CA2928939A1 (en) * 2016-04-29 2017-10-29 SteadyServ Technologies, LLC Sensing devices and systems including examples of pairing sensing devices to containers
ES2724776A1 (en) * 2018-03-09 2019-09-16 Elortegui Josu Larrauri System for the management and control of bottles or water bottles (Machine-translation by Google Translate, not legally binding)
US20200056919A1 (en) * 2016-05-20 2020-02-20 KegSpeed, LLC Radio transmitter device for use in method and system for monitoring, controlling and optimizing flow of products
US20200172387A1 (en) * 2013-11-03 2020-06-04 Rbe Investments, Llc Draft beer supply chain systems and methods

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150109143A1 (en) * 2012-05-24 2015-04-23 SteadyServ Technologies, LLC Draft beer supply chain systems and methods
US20200172387A1 (en) * 2013-11-03 2020-06-04 Rbe Investments, Llc Draft beer supply chain systems and methods
CA2928939A1 (en) * 2016-04-29 2017-10-29 SteadyServ Technologies, LLC Sensing devices and systems including examples of pairing sensing devices to containers
US20200056919A1 (en) * 2016-05-20 2020-02-20 KegSpeed, LLC Radio transmitter device for use in method and system for monitoring, controlling and optimizing flow of products
ES2724776A1 (en) * 2018-03-09 2019-09-16 Elortegui Josu Larrauri System for the management and control of bottles or water bottles (Machine-translation by Google Translate, not legally binding)

Also Published As

Publication number Publication date
SE545375C2 (en) 2023-07-25

Similar Documents

Publication Publication Date Title
CN105069923B (en) Go-no-go is self-service checks and accepts system and device for logistics parcel intelligence
CN110889662A (en) Dangerous chemical management system and management method
US20070214055A1 (en) System for beverage dispensing and sales tracking
EP2114817B1 (en) Vehicle identification tag reader
US9751745B2 (en) Combination of dispenser and container for a plurality of containers, having a system for the correct placing
CN107393151A (en) Second-hand article self-service dealing cabinet
US20060123806A1 (en) Refrigerator and system of refrigerators
US20240002209A1 (en) Beverage dispensing prevention
CN106006524B (en) For the mouth that falls from bottle distribution drink
US20190016584A1 (en) Fuel pump
SE2051541A1 (en) Beverage dispensing station with weight determining means
GB2588189A (en) Bottle sterilization and refill
SE2051542A1 (en) Beverage dispensing station with accelerometer
SE2051543A1 (en) Reusable beverage container with multiple tags
SE2051547A1 (en) Tracking beverage containers in a filling station
SE2051545A1 (en) Beverage dispensing prevention
SE2051546A1 (en) Machine learning in a beverage distribution system
SE2051540A1 (en) System with smart beverage dispensing stations
Rao et al. Centralized automation of petrol bunk management and safety using RFID and GSM technology
CN205722206U (en) A kind of new media pointing out gift storage capacity promotes machine
CN206921214U (en) A kind of novel straight drinking water dispenser
EP3049365A1 (en) Combination of dispenser and container for a plurality of containers, having a system for the correct placing
CA2875968A1 (en) Gas meter reading system and meter reading method
CN102298753A (en) Anti-counterfeiting system for product
CN114222706A (en) System and method for supplying and/or retrieving bulk products