BACKGROUND OF THE INVENTION

THIS invention relates to a sanitizer dispenser system and method.

Hand sanitiser dispensers are used in various settings, such as entry to stores, airports, hospitals, malls and corporate buildings. Within and outside of pandemic conditions, most global infections tend to be spread by hand. The implementation of hand sanitation facilities has been amplified by the current global climate and the need for sanitiser dispensers and hand washing solutions has risen, in order to try and combat the impact caused by the spread of infectious pathogens. Automated dispenser solutions using embedded RFID technologies offer relief by collecting, what would otherwise be difficult to track, manual data entries of persons entering/leaving a structure/location. These solutions can permit agnostic surveying of the number of times a hand washing function has been performed.

The cost associated with sanitizer dispensers, tags and refills is however relatively high and usually borne by companies, in order to benefit individual clients, customers or employees.

A considerable amount of time is also spent on (i) implementing manual person-to-person sanitizer dispensing (e.g. by using a manually-operated dispensing bottle and spray) and (ii) the manual recording of persons sanitised at entry ways. In this regard, it has become more important for enterprises to be able to identify users/customers of their establishments, as industry is now heavily reliant on data sets provided by technology to be able to provide insights on how to enhance services, improve safety, increase customer engagement, increase personalised product offerings, and better integrate ERP systems.

SUMMARY OF THE INVENTION

In accordance with a first aspect of the invention there is provided a dispenser system which includes: a communication module which is configured to receive or retrieve information from a card with an embedded chip or from a mobile communication device, by utilising wireless communication, wherein the information includes information related to the specific card/mobile communication device and/or a specific person associated with the card/ mobile communication device; a dispenser which is configured to dispense a fluid; and a control module which is configured to receive information from the communication module and to control the dispensing of the dispenser.

More specifically, the dispenser system may be a sanitizer dispenser system. The dispenser may therefore be a sanitizer dispenser which is configured to dispense sanitizer fluid. The dispenser system may be a beverage dispenser system. The dispenser may therefore be a beverage dispenser.

The information received or retrieved from the mobile communication device may relate to a virtual card or to a digital version/representation of a physical card, preferably a physical card with an embedded chip.

The control module may be configured to dispense sanitizer fluid when the communication module receives or retrieves information from a particular card with an embedded chip or from a mobile communication device.

More specifically, the control module may be configured to dispense sanitizer fluid only if one or more conditions are met, wherein one of the conditions is that the communication module should have received or retrieved information from a particular card/mobile communication device, before dispensing sanitizer fluid.

The sanitizer dispenser may be a hand sanitizer dispenser. The sanitizer fluid may be a sanitizer liquid.

The communication module may be configured to receive or retrieve information from a card or mobile communication device by utilising nearfield communication (NFC). The communication module may therefore include a NFC module/device/unit.

The information received or retrieved from a card or mobile communication device may include identification information of a specific person associated with the card or mobile communication device (e.g. the card owner). The information may include the person’s name and/or a bank account which is associated with the card or mobile communication device.

The card may be a payment card (e.g. a debit or credit card). More specifically, the card may be an EMV card (EMV stands for “Europay, Mastercard and Visa”).

The control module may be configured to utilise the received/retrieved information and query a database on which information on a plurality of users which are registered with the dispenser system (hereinafter referred to as “registered users”) are stored, in order to determine whether the received/retrieved information matches information of a particular registered user. The system may include the database.

In one example, the control module may be configured to instruct the sanitizer dispenser to dispense sanitizer fluid only if the received/retrieved information matches information of a particular registered user. This may therefore be a condition which should be met, before the control module instructs the sanitizer dispenser to dispense sanitizer fluid. The system may include a registration module which is configured to receive registration information for one or more users/people via a communication network (e.g. a telecommunication network) and store the registration information on the database. The registration information may include information on a specific card which should be associated with the particular user/person.

The system may include at least one mobile communication device. The mobile communication device may be configured to allow a user/person to register with the system by submitting registration information to the registration module via a mobile telecommunication network. The mobile communication device may be a smart device. A mobile app may be installed on the smart device, wherein the app is configured to allow a user to submit registration information to the registration module.

The mobile communication device may include a near-field communication (NFC) module/unit which is configured to receive/retrieve card information from a card with embedded NFC capabilities, when the card is in range. The registration information may include the received/retrieved card information.

The communication module, sanitizer dispenser and control module may be incorporated/integrated in a single unit/device.

In accordance with a second aspect of the invention there is provided a method of dispensing fluid which includes:

(a) receiving or retrieving, via wireless communication, information from a card with an embedded chip or a mobile communication device, wherein the information includes information related to the specific card/mobile communication device and/or a specific person associated with the card/mobile communication device; and

(b) dispensing fluid, by using a dispenser once, or after, the information has been received or retrieved from the card. The method may more specifically be a method for dispensing sanitizer fluid. Step (b) may therefore more specifically include dispensing sanitizer fluid, by using a sanitizer dispenser once, or after, the information has been received or retrieved from the card.

The method may be a method for dispensing a beverage. Step (b) may therefore more specifically include dispensing a beverage once, or after, the information has been received or retrieved from the card.

The information received or retrieved from the mobile communication device may relate to a virtual card or to a digital version/representation of a physical card, preferably a physical card with an embedded chip.

The sanitizer dispenser may be a hand sanitizer dispenser. The sanitizer fluid may be a sanitizer liquid.

Step (a) may include receiving or retrieving the information via near-field communication (NFC).

The information received or retrieved from a card or mobile communication device may include identification information of a specific person associated with the card (e.g. the card owner). The information may include the person’s name and/or a bank card number which is associated with the card.

The card may be a payment card (e.g. a debit or credit card). More specifically, the card by be an EMV card (EMV stands for “Europay, Mastercard and Visa”).

The method may include querying a database on which information on a plurality of users which are registered with a sanitizer dispenser system (hereinafter referred to as “registered users”) is stored, in order to determine whether the received/retrieved information matches information of a particular registered user.

In one example, the method may include dispensing the fluid only if the received/retrieved information matches information of a particular registered user. This may therefore be a condition which should be met, before the dispensing sanitizer fluid.

The method may include receiving registration information for one or more users/people via a communication network (e.g. a telecommunication network) and storing the registration information on the database. The registration information may include information on a specific card which should be associated with the particular user/person.

The method may include capturing registration information by using a mobile communication device. The mobile communication device may be a smart device. The method may include capturing registration information via a mobile app installed on the smart device.

The mobile communication device may include a near-field communication (NFC) module/unit which is configured to receive/retrieve card information from a card with embedded NFC capabilities. The method may include using the NFC module/unit to receive/retrieve card information from a card with embedded NFC capabilities. The registration information may include the received/retrieved card information.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will now be described, by way of example, with reference to the accompanying drawings. In the drawings: Figure 1 shows a schematic flow diagram which illustrates a portion of the operation of a system in accordance with the invention;

Figure 2 shows a flow diagram which illustrates a registration process of the system in accordance with the invention;

Figure 3 shows a schematic layout of the system in accordance with the invention;

Figure 4 shows a schematic layout of the system shown in Figure 3, whereby sanitizer dispensers are installed at various locations;

Figure 5 shows a schematic flow diagram which illustrates the operation of the system shown in Figure 3; and

Figure 6 shows a three-dimensional view of an example of a sanitizer dispenser which forms part of the system shown in Figure 3.

DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention relates to a hand sanitiser dispenser system 10 which utilises noncontact EMV/NFC technology to dispense a controlled dose of sanitiser liquid 100 upon identifying/reading a registered user’s card 12 or mobile device 14. In a slight alternative embodiment, the sanitizer could be replaced with another type of liquid, such as a beverage liquid (e.g. water or a soda beverage).

The system 10 typically uses known NFC technology in the form of contactless EMV dual interface bank cards 12 and NFC capable Android/iOS mobile communication devices 14. The system 10 includes an NFC reader 16 positioned within a sanitiser dispenser 18 which can communicate with a registered card/device 12, 14 at an entry or exit of a physical structure (e.g. at entryways or doorways). By bringing the card 12 or mobile device 14 within proximity of the NFC sensor/reader 16 inside the dispenser 18, the user 20 triggers release of the sanitiser liquid 100 to wash their hands, which then triggers an entryway to open or close (i.e. the act of washing hands at an entryway/turnstile triggers a door/turnstile to open/release). The actual dispensing can be done by an internal dispenser unit 19 The system 100 then also records the transaction/incident on a server.

Communication between the server and the sanitiser dispensers 18 is done by using Wi-Fi or GSM communication. The dispensers 18 therefore include an internal Wi-Fi module 22 which can communicate with a wireless network of an enterprise/company. One of the purposes of the system 10 is to collect data on public safety, health standards and hand hygiene, to prevent infections spread by hand and to identify users. Using an EMV/NFC card reader application on their mobile communication device 14, a member of the public can onboard/register themselves onto an enterprise’s private network and grant themselves access to enter the facility/structure by means of hand sanitation.

In the past, when businesses or enterprises wanted to onboard their members and visitors onto their automated hand hygiene dispenser/monitoring systems, they needed to purchase, issue and program physical RFID/NFC tags onto their network themselves. In other instances, businesses which did not have these types of electronic systems or automated dispensers needed to perform the hand sanitation and entry/exit recording manually.

EMV chip embedded cards 12 provide reliable and unique programmed identifiers in the form of card numbers, issuer details, expiration dates and card AID which are stored as available public read data on the cards 12 themselves. This data is usually communicated between the card 12 and point of sale terminals when making contactless payments. When interacting with the system 10 of the present invention, a user 20 would link this card data to a profile created on a mobile application stored on a mobile communication device 14 which as a NFC feature/module. The user 20 would then confirm the information by means of captcha or OTP (One- Time Pin) and become a registered member on the network or with the system 10. Once registered, users 20 of the system 10 can present their EMV/NFC cards 12 or mobile communication devices 14 as means of entry and access to certain buildings or areas (e.g. associated with certain business enterprises), such as public spaces, shops, malls, corporate or industrial business parks and transport facilities (e.g. train stations). Additionally, NFC-enabled mobile communication devices 14 provide flexibility as they can both read and emulate NFC card properties. The activities and data collected by the dispenser devices can be visualised as readable data on a mobile application accessible and viewable by both enterprise and users 20.

The system 10 of the present invention can effectively provide an internet of things (IOT) system which comprises an EMV/NFC read-enabled sanitiser liquid dispenser 18 which is configured to dispense a controlled amount of liquid 100 for single use hand washing, (e.g liquid sanitiser, foam, soap, or gel). A user 20 will typically need to download an NFC/EMV reader mobile application onto their NFC capable mobile communication device 14. The user 20 then registers their contactless EMV card 12 and accepts, saves, synchronises, or refreshes their profile on the mobile application, which then synchronises with a cloud server. The NFC reader 16 within the dispenser device can then read EMV data from registered NFC chip embedded cards 12 and check the cloud server for confirmation that the card 12 is registered on the server. Communications can be done using internet connectivity, once the exchange is complete.

The system 10 can be configured such that the dispenser 18 may or may not dispense a contained liquid 100, based on one or more conditions, and thereafter record the incident/transaction on the same cloud server. The liquid is dispensed from a bottle 24 housed within the dispenser 18. The data is then aggregated and visualised to provide actionable insights on customer foot flow by location, track usage of consumables (e.g. volume of fluid used over a given period) and monitors/reports levels of hand hygiene standards compliance. This creates an IOT (internet of things) hand sanitiser dispenser network. As most service providers accept Visa/Mastercard and employ contactless payment technologies, compatibility issues faced by businesses who use or want to use RFID technology in their automated hand sanitiser dispenser systems would be greatly reduced. The sanitiser dispenser device may be powered from a domestic source plug or make use of batteries that may or may not be rechargeable.

In another embodiment, the sanitizer dispenser links hand washing data to a user’s personal health data and analyses it to monitor and prevent infections and outbreaks. (When the device is used, a single string of the event log with user details is recorded on the platform. This event log has an “+add note” option where a discussion board allows patients, clinicians and medical aid providers to hold conversations in a form of posted clinical and billing messages.)

In another embodiment, the system can be configured such that the dispenser may or may not dispense a contained liquid, based on one or more conditions, and thereafter record the incident on the same cloud server. The liquid may be a beverage liquid (or any other liquid of the same dimension) dispensed from a bottle housed within the dispenser. In other words, the system is identical to the sanitizer dispenser described earlier and further below, except that the sanitizer is replaced by a beverage container/bottle to dispense a beverage. The data is then aggregated and visualized to provide actionable insights on customer (beverage-sample) reactions by location, track usage of consumables (e.g. volume of fluid used over a given period). The device may have a cup-shaped design- that gives it its dual application in the healthcare industry and beverage industry. Which means it can hold and dispense liquid sanitizers and liquids from beverages of the same dimension.

In another embodiment, the application of the disclosed IOT system is coupled/linked to instore rewards programs, bolster customer retention efforts, diversify services and improve the customer experience, certain retailers offer rewards programs in the form of redeemable/convertible points or cash discounts. Others offer various financial services in the form of money markets and/or functional transaction accounts, charging small fees for withdrawals at till points. Users of the Android/iOS application can choose to link their instore rewards cards to their profile. Once this is done, they can opt to have a percentage or have their entire discount amount waived and directly deposited into a fixed account held by the retailer or bank (as savings). As an example, a user 20 named “Sally” registers an EMV chip embedded card 20 on the Android/iOS application, which permits access to a particular, favourite retailer. To enter the retailer, Sally will no longer need to manually record entry into any facility. By waving the EMV chip card 12 at the dispenser 18, entry is granted by means of sanitation. Sally can, for example, opt to waiver all cash discounts at this store and have them directly deposited into an instore savings account. Sally shops at this retailer/store once a week. In week 1 , Sally makes a purchase for (X) amount, once the discounts have been tallied, Sally is authorized to save/receive a discount of (Y) amount. Traditionally amount Y would be immediately deducted from the payable total, meaning that Sally’s new total is (Z) amount (X-Y=Z). However, because Sally has opted to have the discounts waived, Sally will pay (X) amount. The difference, which is amount (Y), will be deposited into a fixed account with a selected fixed term. Sally will keep making weekly purchases and amount (Y) would continue to be banked until such a time that term is finished and Sally either reinvests, withdraws or makes instore purchases with the accumulated deposits of amount (Y). Sally can also leave a balance in the account and continue to “bank” discounts by paying the full amount for items and eventually collecting the difference banked. By doing this, customers like Sally can choose to explore other savings offerings/options. Ultimately, Sally could choose to keep receiving direct cash discounts at the point of sale and simply use the application as a means of onboarding onto a retailer’s dispenser network and granting access/entry to facilities by means of hand sanitation. Should Sally choose to opt in to receive the discount/rewards banking service, parameters and thresholds can be set for controlling the percentages of the discount value to be banked. Sally will be afforded the flexibility of being able to change these settings at any time through the selected fixed savings term. In one embodiment, the system 10 and sanitiser dispenser device 18 may or may not allow for tapping, reading and dispensation to unregistered, first time users 20 or cards 12. In this embodiment, the user/member 20 of an establishment consents to having non-personal data recorded by the facility they wish to enter. In doing so, the user 20 authorises the storage/conversion and use of physical card data by public and private bodies for the purposes of preventing the spread of infectious pathogens among their members.

In another embodiment. The IOT based system is used as a means of onboarding members 20 of the public onto healthcare facility infection prevention and control systems/programs. Prevention of healthcare associated infections is a priority focus area for healthcare establishments. Effective hand hygiene is key to providing preventative and safe health care. As a result, healthcare establishments employ varying hand sanitiser dispensing methods and technologies. Using an NFC enabled Android/iOS device 14 (or a USSD menu or Whatsapp menu for users who do not have NFC enabled smart phones) and an NFC/EMV card reader application, a member of the public can read their bank issued contactless EMV card and create a profile for that card allowing them to onboard themselves onto a facility hand hygiene dispenser system/server 10. The profile is then stored on a cloud server and is accessible when an active reader 16 identifies the matching card 12. Once this is complete, the dispenser 18 releases a controlled dose of the contained fluid 100 and records the transaction on the same server.

This unique profile/ID can then be adapted to allow for the upload/scanning and verification of medical records/KYC (Know Your Client) or identification using the Android/iOS onboard camera, after which, given the permissions granted, the uploaded information can be viewed between enterprises (e.g. clinic to clinic, provided the user has granted sharing permissions) resulting in shorter waiting times and faster access/identification authorisations. Applying the use of mobile NFC technology as a means of access/identification and/or information sharing reduces inter enterprise compatibility issues between sanitiser dispenser systems, tags and devices and further reduces costs associated with roll outs of large-scale smart hand hygiene dispenser systems in healthcare environments. The data collected by the dispenser devices 18 provides insight on hand hygiene performance standards and presents the data on viewable dashboards, while the dispenser devices 18 provide automated personal protection against infections.

In one example, the user can add more than one EMV/NFC contactless card 12 and rewards cards to their profile. The Android/iOS application may or may not allow for manual entry of card details during the onboarding/registration process. For e-commerce environments, such as online food purchasing, the same conditions for registered members/users 20 would typically apply. The user 20 would still receive the option to customise their rewards banking services and would still receive their deposits for online purchases, the only difference being that the hand washing action is not recorded as there is no physical entry to the store.

Enterprise facing dashboards and user facing dashboards require the visualisation of different data sets. Thus, enterprise reports or enterprise data generated by the devices 18 would require unique logins and identifiers as enterprise visualisations represent larger volumes and broader sets of user data. Integration of the embodied dispenser system 10 provides enterprise/business insights on promotions uplift, foot traffic, conversion rate, average transaction value and customer lifetime value, key performance indicators, and metrics important for improving efficiency.

Figure 1 shows a flow diagram of the (loT-based) sanitiser dispenser system 10. The flow diagram shows the path of communication between the EMV/NFC embedded chip cards 12 and the mobile android/iOS device 14 (see the arrow indicated by reference numeral 26). The diagram also shows the synchronization of devices between the android device 14, cloud server 15 and the connected sanitiser dispensers 18 (see the arrow indicated by reference numeral 28). The dispensers 18 are positioned within rooms, at entryways, exits, in open spaces or at any point of service. The arrow indicated by reference numeral 30 shows the movement/depositing transfer of funds from the POS to the fixed account.

Figure 2 provides a representation of onboarding/registration steps on the Android/iOS EMV/NFC reader application. Communication between the card reader application and the EMV/NFC card 12 is made possible by electro-magnetic stimulation of the passive chip within the EMV chip card 12. Once active, the previously passive chip can communicate with the Android/iOS device 14.

Once the public read data stored on the chip card is identified/exchanged by the reader application on the Android/iOS mobile device 14, a user can then create a customised profile to represent personalised identifiers on the server.

Figure 3 illustrates a diagram of the components contained within a housing 32 of the sanitiser dispenser devices 18. Figure 3 also illustrates the communication between either an android/IOS device 14 or EMV/NFC chip card 12 and the internal EMV/NFC chip reader 16 located within the dispensing device 18.

Figure 4 shows a flow chart illustrating communication between a multiple sanitiser dispenser network at various locations 34.1-34.5 and the cloud server 15.

Figure 5 shows a flow diagram illustrating the features and functions of the sanitiser dispenser 18. More specifically, the diagram shows how information is relayed between the dispensers 18 and the cloud server 15. For example, when a sanitizer dispenser 18 is powered, a motion sensor is used to detect the presence of a person. If detected, all functions of the sanitizer dispenser 18 are activated and a battery 17 of the sanitizer dispenser 18 is checked to determine the battery level. If the battery level is low, then a processor unit 21 of the sanitizer dispenser 18 sends a notification to the cloud server 15 and a “battery low” LED is activated. A soap/sanitizer level is then checked (e.g. by a sensor). If the soap/sanitizer level is low, then the processor unit 21 of the sanitizer dispenser 18 sends a notification to the cloud server 15 and a “low soap/sanitizer level” LED is activated. The next step is then to detect the presence of an EMV card 12 by using the NFC sensor 16. If no card 12 is detected for a set period (e.g. 30 seconds), then all the functions of the sanitizer dispenser 18 is deactivated. If an EMV card 12 is detected then than the sanitizer dispenser is activated and, if a hand sensor 23 of the sanitizer dispenser 18 detects the presence of a hand, dispenses soap/sanitizer using the dispenser unit 19. Identification (ID) information on the specific sanitizer dispenser 18 and the detected card 12, was well as the current data and time, are sent by the processing unit 21 to the cloud server 15 for storage purposes.

Figure 6 shows an example of a sanitizer dispenser.

Reference is hereinafter specifically made to those parts/aspects marked in the drawings as “A” to “G”. In Figure 1, parts B and F illustrate the transfer of funds into a fixed savings account/pocket once the user 20 has completed an instore purchase. Data from A (i.e. the card 12) and B can be used to create a profile which is stored on the mobile device 14 (C). Once stored, then the mobile device 14 and the card 12 can communicate with a reader 16 via NFC communication (see parts A, C E). The mobile device 14, the cloud server 15 and the dispensers 18 can communicate by means of an internet connection (see parts C, D and E). Information stored on the cloud server 15 can be analysed and displayed on dashboards viewable on the mobile device 14 (see C).

In Figure 3, E1 illustrates a single dispensation/single wash performed by a user at a point of entry. Once a user has paired his card 12, mobile device 14 and account data (see A, B and C) and has successfully created a profile on mobile application (see G), the profile information is then transferred by means of wireless communication (e.g. mobile data/Wi-Fi) to the cloud server 15 (see D) and later retrieved by the dispenser device 18 (see E) to complete a dispensing action (see E1 ). When the dispensing action E1 is completed, the dispenser device 18 transmits the data by means of an internet connection to be recorded, analysed, and aggregated on the cloud server 15. Finally, the data is visualised on a dashboard viewable on the mobile devices 14. Alternatively, the devices 14 can store the collected data on an internal memory and upload the information at periodic intervals (e.g. hourly) to the cloud server 15. This can help in reducing power consumption.

From the above it should be clear that when an EMV/NFC chip embedded card 12 is brought within proximity of a reader 16 of the dispenser device 18, the reader 16 will stimulate the passive chip within the card 12. This then allows the chip to communicate with the device 18 and trigger release of a fluid 100 contained inside the dispenser device 18. Pre-registration of the card is required to be done on a mobile (e.g. Android/iOS) application so that the sanitiser dispenser devices 18 can recognise the user 20. Once registered, the card data is then stored on a cloud database/server 15. When the card 12 is presented to the internet connected dispenser 18, the dispenser 18 requests the data associated with the card 12. If the data associated with the card 12 is found on the database 15, the device 18 will then release a dose of the fluid 100 contained within and send a record of the dispensation back to the cloud database 15. Records of dispensation can include device location, device number, card ID, date, and times.

In another embodiment, the dispenser 18 may release fluid 100 to an unregistered card user. This is made possible due to the device 18 being able to recognise the card type and application or card identifiers/read data. Although there is no pre-registered “profile data” on the server 15 for the card 12 presented, the dispenser 18 may still release the fluid 100, create a temporary LD and record the details.

Users of the device 18 and mobile application have the option of linking their instore rewards program cards to the customised data profile assigned to the EMV/NFC card 12 to be used at sanitiser dispenser stations 18. By linking their rewards cards, the users 20 now have the option of participating in a bankable rewards program. It is important to note that the rewards banking account and the personal account associated with the user’s registered EMV/NFC card have no connection or links. In this regard, linking simply refers to the card registration/onboarding as disclosed in the embodiment herein. However, it would be evident to those skilled in the art that the possibility of transacting between the card accounts does exist.

Once the users’ devices 14 are registered on the system 10, the card ID may be used across multiple physical structures, buildings and locations within the same organisation or enterprise group. The user 20 may also permit the sharing of data between two establishments who do not operate within the same brand, group, or industry, such as between their gym and their favourite coffee shop. This would be suitable for organisations who have public or private partnership agreements and, public spaces where there are no access parameters for entry other than hand washing or disinfection of hands.

In one example, a user 20 can couple access control and sanitiser dispenser related identification systems with other forms of personal identification and benefit from having the ability to verify their identity, onboard, and grant themselves access to various locations, entryways, or service points. The users can choose to share or restrict the data exchanged during requests for authorisations/access/dispensing permissions between member associations and/or private/public spaces. Provisions for this are made within the mobile application settings.