GB2528238A

GB2528238A - Electronic distribution of entitlements to goods and services

Info

Publication number: GB2528238A
Application number: GB1409283.7A
Authority: GB
Inventors: Paul Makin; Susie Lonie
Original assignee: HYPERION SYSTEMS Ltd
Current assignee: HYPERION SYSTEMS Ltd
Priority date: 2014-05-23
Filing date: 2014-05-23
Publication date: 2016-01-20
Also published as: ZA201404902B; GB201409283D0

Abstract

Systems and methods for electronically distributing entitlements to goods and/or services in an environment, such as a rural area, where there is poor and/or unreliable access to wireless data communications networks (e.g. areas where there is limited infrastructure such as few wireless base stations or access points). The method includes implementing a people-powered mesh network where individual people physically transport mobile devices 104, 106 from a first area 124 (in coverage of a data communications network) to another area 112, 114 (in which no or little data communications infrastructure exists) to exchange data with remote devices 108, 110. A central server 102 maintains information about entitlements to goods and/or services that can be distributed to one or more remote users 108, 110. Entitlements to goods and/or services may be in the form of electronic vouchers / coupons, e.g. e-coupons, which can be transferred / shared between devices using a delay tolerant networking (DTN) technique such as store-carry-forward, employing a short range communications protocol such as BluetoothTM to transfer data relating to an entitlement between devices.

Description

ELECTRONIC DISTRIBUTION OF ENTITLEMENTS TO GOODS AND SERVICES IN

RURAL AREAS

Background

[00011 For a mobile computing device, such as a mobile phone or tablet, to be able to exchange data with a remote device, the mobile device typically must connect to a wireless communications network (e.g. a mobile or cellular network, or a WiFiTM network) via a wireless base station or access point. Accordingly, a mobile device can only exchange data with a remote device when the mobile device is within range of a wireless base station. This means that in places where there are few wireless base stations it may be difficult to obtain a connection to a wireless network. This problem is exacerbated by the fact that the range of a base station (the area covered by a base station) is related to the number of mobile devices using the base station. The more users, the smaller the area covered by the base station.

[0002] Conventional mesh networking changes this model by allowing mobile devices to communicate directly with each other. This allows a mobile device that is not within range of a wireless base station to send data to a mobile device that is within range of a wireless base station. The receiving mobile device then passes the data along to the ultimate recipient via the wireless base station. This can be extended so that there are many intermediary devices (e.g. mobile devices) between a sending mobile device and the wireless base station. This allows mobile devices that are not within range of a wireless base station to communicate with remote devices. However, conventional mesh networking relies on a good concentration of mobile devices that are configured to support mesh networking.

[0003] Accordingly, it is difficult for mobile devices in, for example, rural areas, with poor wireless network coverage (e.g. a small or limited number of wireless base stations) and few, if any, mesh networking enabled mobile devices to reliably exchange data with remote devices.

[00041 The embodiments described below are not limited to implementations which solve any or all of the disadvantages of known mobile device communication systems.

Summary

L00051 This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0006] Described herein are systems and methods for electronically distributing entitlements to goods and/or services in an environment, such as a rural area, where there is poor andlor unreliable access to wireless data communications networks (e.g. areas where there are few or limited wireless base stations or access points). The method includes implementing a people-powered mesh network where individual people physically transport mobile devices from one point to another to exchange data with another device. In some examples, a central server maintains information about entitlements to goods and/or services that can be distributed to one or more remote users.

L00071 A first aspect provides a method of distributing entitlements to goods and/or services to users in a remote area, the method comprising: generating an entitlement to a good or service at a central server, the central server being located in a first area; allocating the entitlement to a user based on allocation criteria associated with the entitlement at the central server; in response to establishing a data communications connection between the central server and a mobile device, transferring data indicating the entitlement has been allocated to the user from the central server to the mobile device; physically transporting the mobile device to a second area, the second area being remote from the first area; transferring the data from the mobile device to a remote device enabling the user to redeem the entitlement via the remote device.

[0008] The methods described herein may be performed by a computer configured with software in machine readable form stored on a tangible storage medium e.g. in the form of a computer program comprising computer readable program code for configuring a computer to perform the constituent portions of described methods or in the form of a computer program comprising computer program code means adapted to perform all the steps of any of the methods described herein when the program is run on a computer and where the computer program may be embodied on a computer readable storage medium. Examples of tangible (or non-transitory) storage media include disks, thumb drives, memory cards etc. and do not include propagated signals. The software can be suitable for execution on a parallel processor or a serial processor such that the method steps may be carried out in any suitable order, or simultaneously.

[00091 The hardware components described herein may be generated by a non-transitory computer readable storage medium having encoded thereon computer readable program code.

[00101 This acknowledges that firmware and software can be separately used and valuable.

It is intended to encompass software, which runs on or controls "dumb" or standard hardware, to carry out the desired functions. It is also intended to encompass software which "describes" or defines the configuration of hardware, such as HDL (hardware description language) software, as is used for designing silicon chips, or for configuring universal programmable chips, to carry out desired functions.

[0011] The preferred features may be combined as appropriate, as would be apparent to a skilled person, and may be combined with any of the aspects of the invention.

Brief Description of the Drawings

[0012] Embodiments of the invention will be described, by way of example, with reference to the following drawings, in which: [0013] FIG. 1 is a schematic diagram of an example system for electronically distributing entitlements to goods and/or services; [0014] FIG. 2 is a schematic diagram of exemplary entitlement data of FIG. 1; [0015] FIG. 3 is a flowchart of an example method for electronically distributing entitlements to goods and/or services; [0016] FIG. 4 is a schematic diagram illustrating an example of data flow for enrolling a user in the system of FIG. 1; [0017] FIG. 5 is a flowchart of an example method of enrolling a user in the system of FIG. 1; [0018] FIG. 6 is a schematic diagram illustrating an example of data flow when transferring data from the central server to a remote device; [0019] FIG. 7 is a flowchart of an example method for transferring voucher allocation data from the central server to a remote device; [0020] FIG. 8 is a schematic diagram illustrating an example of data flow when a user redeems a voucher; [0021] FIG. 9 is a flowchart of an example method of redeeming a voucher in the system of FIG. 1; and [0022] FIG. 10 is a block diagram of an example computing device.

[0023] Common reference numerals are used throughout the figures to indicate similar features.

Detailed Descrirtion [0024] Embodiments of the present invention are described below byway of example only.

These examples represent the best ways of putting the invention into practice that are currently known to the Applicant although they are not the only ways in which this could be achieved. The description sets forth the functions of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.

[0025] Embodiments described herein relate to systems and methods for electronically distributing entitlements to goods and/or services in an environment, such as a rural area, where there is poor and/or unreliable access to wireless data communications networks (e.g. areas where there are few or limited wireless base stations or access points). The method includes implementing a people-powered mesh network where individual people physically transport mobile devices from one point to another to exchange data with another device.

[0026] In some examples, a central server maintains information about entitlements to goods and/or services that can be distributed to one or more remote users. When a first mobile device has established a data communications connection (e.g. wired or wireless) with the central server (via, e.g. a wired or wireless network), the central server securely transfers information related to the entitlements to the first mobile device. Once the first mobile device has received the information a user physically transports the first mobile device to a remote location where it comes within range of another device (mobile or not). Once within range of the other device the mobile device securely transfers all or a subset of the information related to the entitlements to the other device to enable a user to redeem entitlements they have been allocated via that device.

[0027] Such a system may be used, for example, in a third world country to reliably and securely distribute entitlements to financial subsidies for items, or to items themselves such as fertilizer, vaccinations, mosquito nets and training courses etc. to entitled individuals in remote areas. Other systems that have been implemented to distribute entitlements in remote areas have struggled with means for distributing the entitlement securely to ensure that only entitled individuals are able to redeem or access the entitlements; monitoring voucher redemption (both to ensure effectiveness of the distribution and preventing multiple redemptions of the same entitlement); and linking entitlements overtime. By using the people-powered mesh network described herein entitlements can be securely distributed to remote areas to ensure the right people get the rights entitlements. The system described herein also allows an accurate record of the redemptions to be maintained to ensure the system is working effectively and to prevent fraud (e.g. to prevent someone who has not been allocated an entitlement from being able to redeem an entitlement).

[0028] Reference is now made to FIG. 1 which illustrates an example system 100 for electronically distributing entitlements to goods and/or services to users in an environment with poor or limited access to wireless data communications networks in a secure manner.

The system comprises a central server 102 for storing and managing data related to the allocation and redemption of entitlements to goods and/or services. An entitlement may, for example, entitle the user to a good or service (e.g. a vaccination, mosquito net, pesticides, or a training course) orto a financial subsidy on a good and service (e.g. reduction in the price of an item). The system 100 also comprises one or more mobile devices 104, 106 for transporting and securely transferring entitlement data between the central server 102 and one or more remote devices 108, 110 located in a remote area 112 or 114. This allows users 116, 118, 120 to redeem their entitlement(s) in remote areas 112 or 114 where there is poor or limited access to wireless data communications networks.

[0029] The central server 102 is a computer-implemented device capable of maintaining entitlement data to facilitate the secure distribution and redemption of entitlements to goods and/orservicesto appropriate users 116, 118, 120. The entitlement data may comprise, for example, information related to users 116, 118, 120 who are enrolled or registered in the system (e.g. name, date of birth, address, number of dependents, crops grown, etc.), information defining the goods and/services that are available, criteria for determining which of the enrolled or registered users 116, 118, 120 are entitled to which goods and/or services, and a record of which users in remote areas 112, 114 have been allotted which goods and/or services and which of the allocated entitlements have been redeemed. The entitlement data may be stored by the central server 102 itself or it may be stored by another device, such as a dedicated database server 122 that is accessible by the central server 102.

[0030] In some cases the goods and/or services that can be allocated or awarded to registered users are defined by vouchers. Each voucher defines what good or service the recipient is entitled to, herein referred to as an "entitlement". For example, the entitlement rilay specify that the recipient is entitled to 50% off fertilizer or is entitled to a specific training course. In some cases the voucher may also define one or more other characteristics related to redemption of the entitlement. For example, the voucher may specify a range of dates for which the entitlement is valid, the geographical area in which the entitlement can be redeemed, and/or a specific retailer or list of retailers in which the entitlement can be redeemed.

[0031] In some cases vouchers may be linked. For example, a voucher for training course B may only be available if training course A has been completed; or a voucher for a mosquito net may only be available if vouchers for AIDS medication have been regularly redeemed.

[0032] Vouchers may also be automatically generated. For example, a woman who presents for ante-natal care can have a series of vouchers generated, each being made available only at an appropriate time, for further ante-natal care, care during delivery, and post-natal care. In some cases, a whole new registered user may be created automatically when the child is born with vouchers for vaccinations delivered at the appropriate time, or for a mosquito net or a subsidy on the payment of school fees.

[0033] In some cases, vouchers may be grouped together in an "entitlement package". This allows multiple vouchers to be easily allocated to multiple users without having to specifically allocate each individual voucher in the entitlement package to multiple users. The discussion below refers to allocation and redemption of vouchers, however, it equally applies to the allocation and distribution of entitlement packages.

[0034] Once a voucher has been defined the criteria for determining which of the enrolled or registered users are entitled to the goods and/or services specified by the voucher are used by the server 102 to match the voucher to one or more registered users 116, 118, 120. The criteria for determining which of the enrolled or registered users are entitled to the goods and/or services specified by the voucher may relate to any user data forming the entitlement data. For example, the criteria may specify an age range, location of residence, male/female, etc. [0035] Each user 116, 118, 120 identified as matching criteria for a particular voucher is allocated or assigned the voucher. Once a user 116, 118, 120 has been allocated or assigned a voucher they can redeem the voucher at a participating retailer or service provider. For example, if the voucher is for fertilizer or a reduced price on fertilizer the central server 102 may identify registered farmers in a certain region that may potentially benefit from free or reduced price fertilizer, based on, for example, the crops they are known to grow.

Each identified farmer may then be allocated or assigned a voucher which they can redeem as described below. In particular, FIGS. 8 and 9 describe an example method for redeeming a voucher.

[0036] The central server 102 may also be configured with the ability to generate reports on the entitlement data. For example, it may be able to generate a report that indicates what vouchers have been allocated to a user, when and where the vouchers were redeemed. It also may be able to generate reports on how well the people-powered mesh network is operating.

[0037] Each mobile device 104 and 106 is a portable computer-implemented device that is capable of communicating with other computer devices (mobile or otherwise) via a wireless communications network (e.g. a mobile communications network such as a cellular network, or a Wi-FiTM network). The mobile devices 104 and 106 may be, for example, but are not limited to, mobile phones, smart phones, tablet computers, laptop computers and the like.

The mobile devices 104 and 106 are responsible for transferring entitlement data between the central server and remote locations to enable registered users to access and redeem their entitlements.

[0038] In the simplest case there may be one mobile device 104 which is used to transfer entitlement data between the central server 102 and a remote device 110. When the mobile device 104 is in a location or area 124 where it can establish a data communications connection with the central server 1 02 via a data communications network 126 (e.g. it is in range of a mobile or cellular network or another wireless network (e.g. a WiFiTM network); or it is physically connected to a wired network, such as an EthernetTM or Token Ring network) the central server 102 securely transfers entitlement data to the mobile device 104. In some cases, the central server 102 only transfers a subset of the entitlement data it has access to.

For example, the central server 102 may be configured to only send the mobile device 104 entitlement data: (i) that has changed since the last exchange of data with the mobile device 104; (U) related to a specific geographical area; (iH) related to a subset of users; (iv) related to specific types of goods and/or services; and/or (v) vouchers that have become valid (e.g. based on start date) since the last data transfer.

[0039] Once the mobile device 104 has established a connection with the central server 102, the mobile device 104 may also provide the central server 102 with any entitlement data it has obtained from a remote area 112 since it last established communication with the central server 102.

[0040] Once the mobile device 104 has received the entitlement data from the server 102 the mobile device 104 is physically transported to a remote location 112 where it is brought into close proximity with a remote device 110. The mobile device 104 establishes a data communications connection (e.g. via a wireless protocol, such as WiFiTM, BluetoothTM, NFC or the like) with the remote device 110. The mobile device 104 and the remote device 110 then securely exchange entitlement data. The connection may be established automatically or it may be triggered upon receiving specified input from an operator of the mobile device 104.

[0041] In some cases the mobile device 104 may be configured to only provide the remote device 110 with a subset of the entitlement data that it has access to. For example, the mobile device 104 may be configured to only provide the remote device 110 with entitlement data that (i) has changed since the last exchange of entitlement data with the remote device 110; (ii) is related to the specific geographic area in which the remote device is located; (iii) is related to the specific merchant associated with the remote device 110; and/or (iv) is related to the specific goods and/or services that can be redeemed via the remote device 110 (e.g. goods and/or services that are offered by the merchant associated with the remote device 110).

[0042] Similarly, the remote device 110 may be configured to only provide the mobile device 104 with a subset of the electronic goods and/or services data that it has access to. For example, the remote device 110 may be configured to only provide the mobile device 104 with electronic goods and/or service data that has changed since the last exchange of data with the mobile device 104.

[0043] In other more complicated cases there may be layers or a mesh of mobile devices 104, 106 that are used to exchange entitlement data between the remote device 108 and the server 102. For example, a first mobile device 104 may be configured to exchange entitlement data with the central server 102 directly when it is in a location 124 that enables it to establish a data communications with the server 102. The first mobile device 104 is then physically transported to a first remote area or location 112 where it is brought into close proximity with a second mobile device 106. The first mobile device 104 and the second mobile device 106 establish a data communication connection (e.g. via a wireless protocol, such as Wi-FiTM, BluetoothTM, NFC or the like) and securely exchange entitlement data. The second mobile device 106 is then physically transported to a second remote area or location 114 where it is brought into close proximity with a remote device 108. The second mobile device 106 and the remote device 108 establish a data communication connection (e.g. via a wireless protocol, such as WiFiTM, BluetoothTM, NFC or the like) and securely exchange entitlement data.

[0044] Although only two mobile devices 104 and 106 are shown in FIG. 1, the methods and principles described herein may be applied to systems comprising more than two mobile devices 104 and 106.

[0045] Each remote device 108, 110 is a computer-implemented device situated in an area 112 or 114 that may have poor or no access to a wireless data communications network.

Each remote device 108, 110 maintains entitlement data received from the central server 102 (via one or more mobile devices 104, 106) to allow registered users to redeem entitlements for specific goods and/or services. The entitlement data received and stored by the remote devices may be limited to entitlement data that relates to a particular area (e.g. limited to entitlement data to people who live within a certain region of the remote device 108, 110).

[0046] In some cases the remote device 108, 110 is associated with a merchant or service provider that offers particular goods and/or services. In these cases, the entitlement data received and stored may be limited to entitlement data that relates to the particular merchant.

For example the entitlement data received and stored by the remote device 108, 110 maybe limited to goods and/or services that can be redeemed by the merchant (e.g. the merchant offers or sells the goods and/or services). In other cases the remote device 108, 110 may be associated with another entity such as a medical centre or a training facility or school.

[0047] Each remote device 108, 110 is configured to receive requests from a user to redeem an entitlement or part of an entitlement and use the stored entitlement data to determine whether the user is allowed to redeem the requested entitlement. In some cases the user may have to go through a registration process to become a registered user. During that registration process the user provides personal data to the registrar and in exchange the user may be given an identification card 128. In these cases, the user may have to present their identification 128 card to the remote device 108, 110 or an operator of the remote device 108, to confirm their identity before they can redeem a voucher/entitlement. An example registration process is described below with reference to FIGS. 4 and 5. In other cases, user data may be obtained and input into the system via other means.

[0048] Reference is now made to FIG. 2 which shows an example of entitlement data which may be used in the system of FIG. 1. In FIG. 2, the entitlement data is divided into three tables of information -a vouchers table 202; an entitlement criteria table 204; and a registered users table 206. It will be evident to a person of skill in the art that this is an example only and in other examples the data may be arranged in a different manner and/or different data may be stored.

[0049] The vouchers table 202 lists the vouchers that are available to the registered users.

As described above, each voucher specifies an entitlement to a good and/or service. The entitlement may, for example, entitle the user to the good and/or service (e.g. "10 bags of fertilizer", "TB vaccination"; Seed planting course"; bag of maize seed); or entitle the user to a discount on the good and/or service (e.g. "50% off fertilizer"). As shown in FIG. 2, each voucher may be assigned an identification number or code so that it can be easily referred to.

[0050] A voucher may also comprise additional information or conditions defining the terms of use/redemption of the entitlement. For example, as shown, in FIG. 2, a voucher may specify a time period in which the entitlement may be redeemed (e.g. start and end dates may be specified), or it may specify that it may only be redeemed in a predefined region or area (e.g. "North"). Other conditions may also be placed on redemption of the entitlement. For example the voucher may specify that it only can be redeemed at certain retailers.

[0051] The entitlement criteria table 204 lists the criteria for allocating vouchers to registered users. As shown in FIG. 2, the voucher may be identified by its identification number or code and the criteria are associated with the identification number. The criteria may, for example, specify that the voucher is to be allocated to registered users that live in a specified region, are a targeted gender (e.g. Female), are above or below a certain age (e.g. >18; or <10).

However, other suitable criteria may be used to allocate vouchers to registered users. For example, a voucher for maize seed may only be allocated to users that grow maize. In some cases the criteria may take into account external information. For example, if maize in a particular region is known to be suffering from an outbreak of aphids, then a voucher for the appropriate pesticide may be automatically created and allocated to all farmers in that region who grow maize.

[0052] The registered users table 206 lists the users that are registered with the system. As described above, in some cases a user must go through a registration process to be registered with the system. This may involve the user providing certain person details (e.g. name, address, date of birth) to a registrar. Once registered the user may be provided with an identification card 128 that can be used to redeem any allocated vouchers. An example registration process is described below with reference to FIGS. 4 and 5.

[0053] As shown in FIG. 2 the registered users table 206 may comprise a unique identification number or code for each user along with the personal details (e.g. name, sex, date of birth, address, etc.) provided during registration. Where users are given identification cards 128 during registration the identification number or code assigned to the user may match a number printed or assigned to their identification card 128.

[0054] In some cases, as shown in FIG. 2, the registered users table 206 may also comprise information about which vouchers have been allocated to which users and the status of the allocated voucher (e.g. whether or not it has been redeemed or partially redeemed). For example, FIG. 2 shows that the registered user 1 has been allocated vouchers 1 and 4; voucher 1 is available ("A"), but voucher 4 has been redeemed ("R"). In other cases, the information regarding allocation of vouchers to users and/or the status of the allocated voucher is recorded elsewhere (e.g. in a separate table).

[0055] Where entitlement packages are used, the entitlement data may also comprise an entitlement package table (not shown) that links or groups multiple vouchers together. In these cases the voucher criteria table may be replaced with an entitlement package table which specifies the criteria for determining which users are allocated which entitlement packages. The registered users table may then include a list of entitlement packages that have been allocated to the users. Alternatively there may be another table that links the users to the entitlement packages.

L00561 Reference is now made to FIG. 3 which illustrates an exemplary method for electronically distributing entitlements to goods and/or services to users in remote areas where there is poor or no access to data communications systems. At block 302 a user is registered with the system. This may involve a registrar visiting a remote area (e.g. remote area 112 or 114) where the user works or lives: for example. The user provides personal data (e.g. name, address, sex, date of birth) and the registrar creates a new register user record in a mobile device (e.g. mobile device 104 or 106) and populates it with the personal information provided by the user. In some cases the registrar then provides the user with an identification card 128 bthat will allow them to redeem any voucher allocated to them.

[00571 The registrarthen transfers the new user record to the central server (e.g. central server 102) stored on the mobile device (mobile device 104 or 106) using the people-powered mesh network described with reference to FIG. 1. For example, the registrar may physically take the mobile device 104 from the remote area 112 or 114 to an area 124 where it can establish a connection with a data communications network 126. The mobile device 104 then establishes a data communication connection with the central server and transfers the new user record to the central server 102. In other examples, the transfer is made via more than one other mobile device. For example, the registrar may physically take the mobile device 106 to another remote area 112 where it establishes a wireless data communications connection with another mobile device 104. That mobile device is then transported to an area where it can communicate with the central server 102 and provide it with the new user record.

Once the new user record has been received by the central server it is stored as part of the entitlement data (e.g. a new user record is created in the registered users table 206). An example registration process will be described in more detail with reference to FIGS. 4 and 5.

Once the user has been registered, the method 300 proceeds to block 304.

[00581 At block 304, the central server 102 uses the entitlement criteria to determine if the user should be allocated one or mole of the vouchers in the system. If the central seivel 102 determines that the user is to be allocated one or more vouchers then the central server 102 updates the entitlement data (e.g. as described with respect to FIG. 2, the central server may update the registered users table 206 to indicate which voucher(s) the user has been allocated). Once a voucher has been allocated to the new user, the method 300 proceeds to block 306.

[0059] At block 306, the central server 302 transfers information indicating the user has been allocated the voucher to a remote device 108 or 110 in a remote area 112 or 114 using the people-powered mesh network described with reference to FIG. 1. For example, the central server 302 may transfer the information related to the allocated voucher to a mobile device 104 when the mobile device is in an area where it can establish a data communications connection with the central server. The mobile device 104 is then physically transported to a remote area 112 where it establishes a data communication connection with another mobile device 106 ora remote device 110, or both devices. Once the connection is established the mobile device 104 transfers the information indicating the user has been allocated the voucher to the other device or devices (mobile device 106 and/or remote device 110). In some cases (e.g. where the voucher is limited to a specific area or retailer) the mobile device 104 only transfers the information indicating allocation of the voucher if the voucher can be redeemed by the user in the area where the remote device 110 is situated.

[0060] Where the information indicating the user has been allocated the voucher is transferred to the remote device 110 the user can then redeem the voucher via the remote device 110. Where the information indicating the user has been allocated the voucher is transferred to another mobile device 106, that other mobile device 106 may be physically transported to another area 114 where the information indicating the user has been allocated the voucher may be transferred to another mobile device or transferred to a remote device 108. An example method for transferring data from the central server 102 to a remote device will be described in reference to FIGS. 6 and 7. Once the information indicating the user has been allocated the voucher is transferred to one or more remote devices 108, 110 the method 300 proceeds to block 308.

[0061] At block 308, the user redeems the voucher via a remote device 108 or 110. In some cases, the user goes to a merchant shop that is known to offer voucher redemption. The user may present his identification card to the merchant who verifies the identity of the user using the identification card. In some cases the merchant presents the user's identification card to the remote device 108 or 110 which causes the remote device 108 or 110 (or an associated display device) to display an image of the user. The merchant then verifies the user's identity using the displayed image.

[0062] Once the user's identity has been verified, the merchant uses the remote device 108 or 110 to determine whetherthe user has been allocated any vouchers. If the user has been allocated at least one voucher the merchant may ask the user if they wish to redeem all or part of their voucher. For example, if the voucher entitles the user to 10 bags of fertilizer the merchant may query the user to determine whether they wish to redeem all 10 bags or only one or two. If the user does decide to redeem all or part of a voucher, the merchant provides the user with the goods and/or services (if possible) and updates the entitlement data stored on the remote device 108 or 110 to indicate what portion of the voucher the user has redeemed. An example method for a user to redeem a voucher is described with reference to FIGS. 8 and 9. Once the user has redeemed at least part of a voucher, the method 300 proceeds to block 310.

[0063] At block 310, information indicating the user has redeemed all or part of the voucher is transferred from the remote device 108 or 110 to the central server 102 using the people-powered mesh network described with reference to FIG. 1. For example, the remote device 108 or 110 may transfer the information indicating the user has redeemed all or part of the voucher to a mobile device 104 or 106 when the mobile device 104 or 106 has established a data communication connection with the remote device 108 or 110. The remote device then transfers the information indicating the user has redeemed all or part of the voucher to the central server either by being physically transported to another area 124 where the remote device 104 or 106 can establish a data communications connection with the central server 102 directly or to an area 112 where the remote device can establish a data communication connection with another remote device 104 which will later be in an area where it can establish a data communications connection with the central server 102. An example method for transferring data from a remote device to the central server 102 will be described with reference to FIGS. 8 and 9. Once the server has received the information indicating the user has redeemed all or part of the voucher, the method 300 proceeds to block 312.

[0064] At block 312, the central server 102 updates the entitlement data to indicate that all or part of the voucher for the specified user has been redeemed (e.g. the central server 102 may update the registered user table 206 to indicate that all or part of the voucher has been redeemed). The central server 102 may then send an acknowledgement to the remote device 108 or 110 to confirm that the central server 102 received the voucher redemption information. This may be transferred via the people-powered mesh network described with reference to FIG. 1. In particular, the acknowledgement may be transferred to the remote device in a similar manner to that described with respect to block 306 for transferring entitlement/voucher information from the central server 102 to the remote device 108 or 110.

Upon receipt of the acknowledgement the remote device 108 or 110 may (if the complete voucher was redeemed) delete the record of the voucher.

[0065] Reference is now made to FIGS. 4 and 5 which illustrate an example method for registering a user with the system 100. In particular, FIG. 4 is a schematic diagram showing the exchange of data between the user 120, mobile device 104, and the central server 102 during registration of a user 120. FIG. 5 is a flowchart of the method 500 for registering a user 120 with the system.

[0066] At block 502, an operator of the mobile device 104 located at a remote area 112 receives personal information or data from the user 120 (see also FIG. 4A). The personal data may include, for example, basic personal information such as name, sex, date of birth, address etc. The personal data may also include demographic information based on what type of application the system is being used for. For example, where the system is being used to distribute goods andlor services to farmers, the personal data may include what crops the farmer grows; how big the farm is; what medication the person needs; what training they need etc. The personal information may be received from the user verbally or otherwise (e.g. in written form). In some cases an operator may also obtain a photograph of the user. Once the personal information has been obtained, the method 500 proceeds to block 504.

[0067] A block 504 a new user record 402 is generated on the mobile device 104 and populated with the personal information received from the user (see FIG. 48). The personal data from the user may be manually entered by the user or through any other available means. Where a photograph of the user has also been obtained the photograph may be stored in association with or as part of the user record 402. Once the new user record 402 has been generated the method 500 proceeds to block 506 or 508.

[0068] At block 506, the user is provided with an identity card 128 which allows them to redeem any vouchers (see FIG. 4B). As described above, the identity card 128 may be a passive card that simply has information printed on it, or it may be an active card that can actively transfer information stored on the card. Once the user has been provided with an identity card 128 the method proceeds to block 508.

[0069] At block 508, the mobile device 104 is physically transported to another area 124 where the mobile device is able to establish a connection to a data communication network 126. In some cases, as described above, instead of the mobile device 104 being transported to an area where it can establish a connection to a data communications network, the mobile device 104 may be transported to an area where it can establish a data communication connection with another mobile device. The new user registration information is transferred to the other mobile device. This process can be repeated through a series of mobile devices until a final mobile device is physically transported to an area where it is able to establish a connection to a data communication network 126. Once the mobile device (or a subsequent mobile device in the chain) is moved to a location where it is able to establish a connection to a data communications network the method 500 proceeds to block 510.

[0070] At block 510, the mobile device 104 establishes a data communications connection with the central server 102. Once a connection has been established the method proceeds to block 512.

[0071] At block 512, the mobile device transfers registration information 404 to the central server 102 for the new user (See FIG. 4C). The registration information 404 may comprise, for example, information identifying the user, the personal information provided by the user and/or the photograph of the user. Once the central server 102 receives the registration information 404 the central server creates a new record 406 in the entitlement data for the new user (e.g. the central server 102 creates a new record in the registered users table 206 (See Figure 4D)). The central server 102 may then send an acknowledgment 408 (See Figure 4D). The method 500 then proceeds to block 514 or optionally the method ends here.

[0072] At block 514 the mobile device 514 determines whether it has received an acknowledgement 408. Once it has received an acknowledgement, the method 500 proceeds to block 516.

[0073] At block 516, the mobile device removes the new user record so as to save space.

[0074] Reference is now made to FIGS. 6 and 7 which illustrate a method for transferring entitlement data from the central server 102 to a remote device 108 or 110 using the system of FIG. 1. In particular, FIG. 6 is a schematic diagram showing the exchange of data between the central server 102, the mobile device 104 and the remote device 110. FIG. 7 is a flowchart of a method 700 for transferring entitlement data from the central server 102 to a remote device 110. The following method may be executed after the central server 102 has allocated a new voucher 602 to a user.

[0075] At block 702, a mobile device 104 is situated in an area 124 where it is able to establish a connection with a data communications network 126. The mobile device 104 establishes a connection with the central server 102 and makes a request for the latest entitlement data. As described above, in response to the request, the central server 102 may send the mobile device 104 all of the entitlement data that has changed since the last time the mobile device 104 requested an update from the central server 102 or only a subset of the changed entitlement data (e.g. data specific to a particular area/region; related to particular retailers etc.). In this specific example (where the central server 102 has recently allocated a voucher to a user) the central server will send, and the mobile device will receive, at least information regarding the new voucher allocation 604 (see FIG. 6A). The new voucher allocation 604 may specify, for example, the voucher that has been allocated and the user that has been allocated the voucher. At the same time the mobile device 104 may provide the central server 102 with any updates or changes to the entitlement data that it is aware of (e.g. vouchers that have been redeemed). Once the mobile device 104 receives the new voucher allocation 604 the method 700 proceeds to block 704.

[0076] At block 704, the mobile device 104 creates a record 606 of the new voucher allocation 604 received from the central server 102 (see FIG. 6B). Once the mobile device 104 has created a local record 606 of the new voucher allocation, the mobile device 104 may send an acknowledgement 608 back to the central server 102 to confirm receipt of the new allocation 604. In response to receiving the acknowledgement 608, the central server 102 may update the entitlement data to indicate that the voucher allocation 604 has been successfully transmitted to the mobile device 104. This may be used by the central server 102 to ensure that the central server 102 does not send this information to the mobile device 104 again the next time the mobile device 104 connects to the central server 102. Once the mobile device has created a record of the new voucher allocation, the method 700 proceeds to block 706.

[0077] At block 706, the mobile device 104 is physically transported to a remote area 112.

Once in the remote area 112, the method 700 proceeds to block 708.

[0078] At block 708, the mobile device 104 establishes a data connection with another device to enable the new voucher allocation information stored in the record 606 to be transferred to a remote device 110 or 108. In some cases the other device is the remote device 110. In other cases the other device is an intermediary device (e.g. another mobile device 106) that is responsible for transferring the new voucher allocation received from the mobile device 104. As described above, the intermediary device may do this by transferring the new voucher allocation to another intermediary device (e.g. another mobile device) or by transferring the new voucher allocation to the remote device 110. Once the mobile device 104 has established a data connection with the other device the method 700 proceeds to block 710.

[0079] At block 710, the mobile device sends the new voucher allocation information 610 stored in the record 606 to the other device (e.g. the remote device 110 or mobile device 106) (See FIG. 6C). The other device then stores the new voucher allocation information 610 in a new record 612. Where the other device is the remote device 110 the user whom was allocated the new voucher can now redeem the voucher via the remote device 110. For example, the user may be able to redeem the voucher for the goods and/or services or discount on the goods and/or services at a merchant or retailer where the remote device 110 is situated.

[0080] In some cases, the other device (e.g. the remote device 110 or mobile device 106) may also transfer any new and/or changed entitlement data it is aware of (e.g. vouchers redeemed) to the remote device 104 (See FIG. 6C). The mobile device 104 then can provide this new and/or changed entitlement data to the central server 102 when the mobile device 104 next establishes a connection with the central server 102. Once the new entitlement allocation information 610 has been sent to the other device (e.g. remote device 110 or mobile device 106) the method 700 proceeds to block 712.

[0081] At block 712, the mobile device 104 waits until it receives an acknowledgement 614 from the other device that it has successfully received the new entitlement allocation information (See FIG. 6D). Where the mobile device 104 has also received entitlement data from the other device the mobile device 104 may send its own acknowledgement to the other device. Once an acknowledgement has been received the method 700 ends 714.

[00821 Reference is now made to FIGS. 8 and 9 which illustrate a method for a user to redeem a voucher in a remote area 112 using the system 100 of FIG. 1. In particular, FIG. 8 is a schematic diagram showing the exchange of data between the central server 102, the mobile device 104 and the remote device 110 when a user redeems a voucher. FIG. 9 is a flowchart of a method 900 for redeeming a voucher. The following method may be executed after the remote device 110 has received voucher allocation information from the central server 102 in accordance, for example, with the method of FIG. 7.

[0083] At block 902, the remote device 110 receives information identifying the user 120 attempting to redeem a voucher (See FIG. 8A). In some cases the user 120 presents the identity card 128 that they received during registration to an operator of the remote device 110. Where the identity card 128 is capable of transferring information to another device (e.g. the identity card is an NFC card) the identity card 128 may be presented to a reader that is part of, or in communication with, the remote device 110 so that the information on the identity card 128 is provided to the remote device. Where the identity card 128 is not, however, able to automatically transfer information to another device such as a remote device 110 (e.g. where the identity card 128 has no active components), an operator of the remote device 110 may manually enter the identity information into the remote device 110. Once the remote device 110 has received the identifying information, the method 900 proceeds to block 904.

[0084] At block 904, it is determined whether the identity of the user 120 is confirmed (See FIG. SB). In some cases, the identifying information received in block 902 is used by the remote device to retrieve a photograph of the user. The photograph may be displayed to an operator of the remote device who compares the photograph to the user 120. It will be evident that this is an example only, and other suitable methods may be used to confirm the user's identity. If the user's identity is not confirmed then the method 900 proceeds to block 906 where the user is notified of the fact that their identity has not been confirmed. The remote device 110 may also annotate the user's record to indicate that someone other than the user has attempted to redeem the user's vouchers. This may result in the user's account being shutdown etc. If, however, the user's identity is confirmed then the method 900 proceeds to block 908.

[0085] At block 908, once the user's identity is confirmed the identity information is used to identify the vouchers that the user has been allocated and the status of each allocated voucher 802 (see FIG. 8B). This information may be then provided to the user. In some cases the voucher information is provided to the user visually. For example the vouchers allocated to the user and/or their status may be displayed on a display screen associated with the remote device 110. In other cases the voucher information may be verbally provided to the user by an operator of the remote device 110 or by an audio output component of the remote device 110. In yet other cases the voucher information may be provided to the user both visually and audibly. Once the user 120 has been provided with the vouchers that they have been allocated, the method 900 proceeds to block 910.

[0086] At block 910, the remote device 110 receives information from the user indicating whether they would like to redeem all or part of a voucher that they have been allocated (See FIG. BC). If the user indicates that they are not interested in redeeming any of the vouchers that they have been allocated then the method proceeds to block 912 where the merchant or retailer processes any transaction without the vouchers/entitlements (e.g. the user 120 pays full price for the goods and/or services). If, however, the user indicates that they wish to redeem all or part of a voucher then the method 900 proceeds to block 914.

[0087] At block 914, the selected voucher is applied to a transaction (e.g. the purchase of goods and or services) (See FIG. 8D). This may involve supplying the user 120 with the requested goods and/or service 808. In some cases the voucher is only applied the transaction if the merchant validates the transaction. This may be done by the merchant or retailer, for example, by providing or tapping their identification card to a reader associated with the remote device 110. Once the voucher has been applied to the transaction, the method 900 proceeds to block 916.

[0088] At block 916, the remote device 110 updates its entitlement data 802 to reflect the fact that all or part of the voucher has been redeemed (see FIG. SD, for example, which shows a checkmark beside the record to indicate the voucher has been redeemed). Once the entitlement data 802 has been updated, the method 900 proceeds to block 918.

[0089] At block 918, the remote device 110 waits for a data communications connection from a mobile device 104 (see FIG. SE). Once it establishes a data communications connection with a mobile device 104, the method 900 proceeds to block 920.

[0090] At block 920, the remote device 110 transfers information indicating which voucher has been redeemed, how much of the voucher has been redeemed and by whom (e.g. a transaction record 810) to the mobile device 104 (See FIG. 8E).

[0091] Once the mobile device 104 has received the transaction record 810 it stores a local copy 812 and then uses the people-powered mesh network described above to transfer the transaction record 810 or the information contained therein to the central server 102. For example, as shown in FIG. 8, once the mobile device 104 has obtained the transaction information from the remote device 110, the mobile device 104 may be physically transported to another area 124 where it is able to establish a data communications connection with central server 102. The mobile device 104 then transfers the transaction information 814 to the central sever 102. The central server 102 then updates the entitlement data 816 based on the received transaction information 814 (See FIG. 8F).

[0092] Once the central server 102 has received the transaction information 814 and updated the entitlement data 816 it may send an acknowledgement 818 to the mobile device (See FIG. 8G). This acknowledgement 818 may trigger the mobile device 104 to delete the transaction data. The mobile device 104 also may store the acknowledgement so that it can ultimately be passed to the remote device 110 which may trigger the remote device 110 to delete the information related to the voucher and its redemption.

[0093] FIG. 10 illustrates various components of an exemplary computing-based device 1000 which may be implemented as any form of a computing and/or electronic device, and in which embodiments of the central server 102, mobile devices 104, 106 and remote devices 108, 110 may be implemented.

[0094] Computing-based device 1000 comprises one or more processors 1002 which may be microprocessors, controllers or any other suitable type of processors for processing computer executable instructions to control the operation of the device in order to exchange data with other devices in the system. In some examples, for example where a system on a chip architecture is used, the processors 1002 may include one or more fixed function blocks (also referred to as accelerators) which implement a part of the described methods in hardware (rather than software or firmware). Platform software comprising an operating system 1004 or any other suitable platform software may be provided at the computing-based device to enable application software 1006 to be executed on the device.

[0095] The computer executable instructions may be provided using any computer-readable media that is accessible by computing based device 1000. Computer-readable media may include, for example, computer storage media such as memory 1008 and communications media. Computer storage media (i.e. non-transitory machine readable media), such as memory 1008, includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanism. As defined herein, computer storage media does not include communication media. Although the computer storage media (i.e. non-transitory machine readable media, e.g. memory 1008) is shown within the computing-based device 1000 it will be appreciated that the storage may be distributed or located remotely and accessed via a network or other communication link (e.g. using communication interface 1 01 0).

[0096] The computing-based device 1000 also comprises an input/output controller 1012 arranged to output display information to a display device 1014 which may be separate from or integral to the computing-based device 1000. The display information may provide a graphical user interface. The input/output controller 1012 is also arranged to receive and process input from one or more devices, such as a user input device 1016 (e.g. a mouse or a keyboard). This user input may be used to, for example, enter the personal data supplied by a user during registration. In an embodiment the display device 1014 may also act as the user input device 1016 if it is a touch sensitive display device. The input/output controller 1012 may also output data to devices other than the display device, e.g. a locally connected printing device (not shown in FIG. 10).

[0097] The term processor' and computer are used herein to refer to any device, or portion thereof, with processing capability such that it can execute instructions. The term processor' may, for example, include central processing units (CPUs), graphics processing units (GPU5 or VPU5), physics processing units (PPU5), digital signal processors (DSP5), general purpose processors (e.g. a general purpose GPU), microprocessors, any processing unit which is designed to accelerate tasks outside of a CPU, etc. Those skilled in the art will realize that such processing capabilities are incorporated into many different devices and therefore the term computer includes set top boxes, media players, digital radios, PCs, servers, mobile telephones, personal digital assistants and many other devices.

[0098] Those skilled in the art will realize that storage devices utilized to store program instructions can be distributed across a network. For example, a remote computer may store an example of the process described as software. A local or terminal computer may access the remote computer and download a part or all of the software to run the program.

Alternatively, the local computer may download pieces of the software as needed, or execute some software instructions at the local terminal and some at the remote computer (or computer network). Those skilled in the art will also realize that by utilizing conventional techniques known to those skilled in the art that all, or a portion of the software instructions may be carried out by a dedicated circuit, such as a DSP, programmable logic array, orthe like.

(0099] Memories storing machine executable data for use in implementing disclosed aspects can be non-transitory media. Non-transitory media can be volatile or non-volatile. Examples of volatile non-transitory media include semiconductor-based memory, such as SRAM or DRAM. Examples of technologies that can be used to implement non-volatile memory include optical and magnetic memory technologies, flash memory, phase change memory, resistive RAM.

(00100] A particular reference to "logic" refers to structure that performs a function or functions. An example of logic includes circuitry that is arranged to perform those function(s).

For example, such circuitry may include transistors and/or other hardware elements available in a manufacturing process. Such transistors and/or other elements may be used to form circuitry or structures that implement and/or contain memory, such as registers, flip flops, or latches, logical operators, such as Boolean operations, mathematical operators, such as adders, multipliers, or shifters, and interconnect, by way of example. Such elements may be provided as custom circuits or standard cell libraries, macros, or at other levels of abstraction.

Such elements may be interconnected in a specific arrangement. Logic may include circuitry that is fixed function and circuitry can be programmed to perform a function or functions; such programming may be provided from a firmware or software update or control mechanism.

Logic identified to perform one function may also include logic that implements a constituent function or sub-process. In an example, hardware logic has circuitry that implements a fixed function operation, or operations, state machine or process.

(00101] Any range or device value given herein may be extended or altered without losing the effect sought, as will be apparent to the skilled person.

[00102] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages.

[001 03] Any reference to an' item refers to one or more of those items. The term comprising' is used herein to mean including the method blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and an apparatus may contain additional blocks or elements and a method may contain additional operations or elements.

Furthermore, the blocks, elements and operations are themselves not impliedly closed.

[00104] The steps of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. The arrows between boxes in the figures show one example sequence of method steps but are not intended to exclude other sequences or the performance of multiple steps in parallel. Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and scope of the subject matter described herein. Aspects of any of the examples described above may be combined with aspects of any of the other examples described to form further examples without losing the effect sought. Where elements of the figures are shown connected by arrows, it will be appreciated that these arrows show just one example flow of communications (including data and control messages) between elements. The flow between elements may be in either direction or in both directions.

[00105] It will be understood that the above description of a preferred embodiment is given by way of example only and that various modifications may be made by those skilled in the art.

Although various embodiments have been described above with a certain degree of particularity, orwith reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of this invention.