Abstract: A method for home delivering cash to a user is disclosed. The method comprises generating a cash delivery request for a user associated with a mobile device in response to an input from a user. The method comprises selecting delivery persons for transmitting cash delivery request based on location of the mobile device, a real-time location associated with the delivery persons and cash available with the delivery persons. The method comprises transmitting a private key to a POS cash delivery device associated with the delivery person. The method comprises initiating an electronic debit transaction equivalent to amount of cash in cash delivery request to merchant of POS cash delivery device. The delivery person in response to successful electronic debit transaction provides requested cash to user. The method comprises providing a confirmation of receipt of the amount of cash as requested in the cash delivery request to POS cash delivery device. Fig. 3
Claims:Claims
I/We claim:
1. A mobile application installed in a mobile device for delivering cash to a user, the mobile device comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to:
generating, by a mobile device, a cash delivery request for a user associated with the mobile device in response to an input from the user, wherein the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user;
selecting, by the mobile device, one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons, wherein the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server;
transmitting, by the mobile device, the generated cash delivery request to the selected one or more delivery persons;
receiving, by the mobile device, a confirmation from a delivery person from the selected one or more delivery persons, wherein the confirmation is indicative of the cash delivery request being served by the delivery person;
generating, by the mobile device, a private key and an encrypted public key associated with the cash delivery request, wherein the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received;
transmitting, by the mobile device, the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies, wherein the private key is transmitted to the POS cash delivery device when the delivery person is at the location of the mobile device, wherein the private key is used to decrypt the public key and verify the cash delivery request;
initiating, by the mobile device, an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request, wherein the delivery person provides the amount of cash in the cash delivery request to the user at the location of the mobile device in response to a successful electronic debit transaction; and
providing, by the mobile device, a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device.
2. The mobile device of claim 1, wherein before the amount of cash in the cash delivery request is provided to the user at the location of the mobile device, the user of the mobile device is verified based on at least one of the image of the user or biometrics of the user in the cash delivery request.
3. The mobile device of claim 1, wherein a blockchain record is maintained for each of the one or more delivery persons within the blockchain network, wherein the blockchain record comprises delivery person id, delivery person’s location information, cash delivery request id, cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, delivery status, type of transaction, a unique number associated with each fiat currency available with the delivery person, and a trust rating of the delivery person.
4. The mobile device of claim 3, wherein when the delivery person provides a confirmation to serve the cash delivery request, the blockchain record associated with the delivery person updates the cash delivery request id, the associated public key received from the mobile device and the delivery status of the cash delivery request.
5. The mobile device of claim 1, wherein when the private key is received from the mobile device by the POS cash delivery device, the POS cash delivery device retrieves the public key associated with the cash delivery request id from the blockchain record, wherein the POS cash delivery device compares the public key retrieved from the blockchain network and the user to ensure that there is no malicious cash request being generated.
6. The mobile device of claim 1, wherein the POS cash delivery device after the successful electronic debit transaction, updates the blockchain record of the delivery person, wherein the updates comprises cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, and delivery status.
7. The mobile device of claim 1, wherein the POS cash delivery device identifies one or more fake fiat currency notes to be delivered to the user based on pre-determined plurality of parameters, wherein the plurality of parameters comprises a unique number associated with each fiat currency, size of note etc.
8. The mobile device of claim 1, wherein the delivery person who has confirmed to deliver the cash is within a pre-defined distance from the location (L1) of the mobile device of the user, and wherein the delivery person has an amount of cash at least equal to or greater than that of the amount requested by the user.
9. The mobile device of claim 8, wherein if individually each of the one or more delivery persons within the pre-defined distance from the location (L1) of the mobile device of the user do not have the amount of cash to be delivered to user within a pre-defined time, then cash available individually with each of one or more delivery persons is collated by a single delivery person and then delivered to the user after a successful verification.
10. The mobile device of claim 8, wherein the processor is further configured to splitting the cash delivery request into a plurality of cash delivery requests if individually each of one or more delivery persons within the pre-defined distance from the location (L1) of the mobile device of the user do not have the amount of cash to be delivered to user within the pre-defined time interval, wherein each of the plurality of cash delivery requests are individually served by the one or more delivery persons.
11. The mobile device of claim 1, wherein the blockchain record of each one or more delivery persons is updated to reflect a A-A transaction that indicates a cash exchange transaction between delivery persons, and wherein a A-C type transaction indicates a cash exchange transaction between a delivery person and a user.
12. The mobile device of claim 1, wherein the private key is generated based on at least an IP address of the mobile device and IMEI number of the mobile device, and wherein the public key is generated based on at least the cash request id, amount of cash to be delivered, location (L1) of the device by using one or more encryption techniques.
13. The mobile device of claim 1, wherein the generated cash delivery request is cancelled by the user, and in response to the cancellation, dynamically calculating a penalty amount to be imposed on the user based on one or more rules, wherein such penalty amount is collected from the user using one or more electronic payment modes.
14. The mobile device of claim 1, wherein the availability of cash with each of the one or more delivery persons is based on a historic patterns and metadata associated with a geography, and wherein dynamically redistributing the cash availability at each of the one or more delivery persons based on historic patterns, and metadata associated with a geography.
15. A POS cash delivery device for delivering cash to a user, the POS cash delivery device comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to:
receiving, by a POS cash delivery device being operated by a delivery person, a cash delivery request from a user associated with a mobile device, wherein the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user;
providing, by the POS cash delivery device, a confirmation based on an input from the delivery person, wherein the confirmation is indicative of the cash delivery request being served by the delivery person, wherein after providing the confirmation, a blockchain record associated with the delivery person updates the cash delivery request id, the associated public key received from the mobile device and the delivery status of the cash delivery request;
receiving, by the POS cash delivery device, an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device;
receiving, by the POS cash delivery device, a private key from the mobile device using one or more Near Field Communication technologies when the delivery person is at the location of the mobile device, wherein the private key is used to decrypt the public key and verify the cash delivery request;
comparing, by the POS cash delivery device, the K1 and K2 to ensure that there is no malicious cash request being serviced, wherein before the amount of cash in the cash delivery request is provided to the user at the location (L1) of the mobile device, the user of the mobile device is verified based on at least one of the image of the user or biometrics of the user in the cash delivery request;
receiving, by the POS cash delivery device, a confirmation indicating a successful electronic debit transaction, wherein the electronic debit transaction comprises transfer of an amount equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods;
providing, by the POS cash delivery device, the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device in response to the confirmation; and
receiving, by the POS cash delivery device, a confirmation of receipt of the amount of cash as requested in the cash delivery request from the mobile device, wherein the POS cash delivery device after a successful electronic debit transaction, updates the blockchain record of the delivery person, wherein the updates comprises cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, and delivery status.
16. A method for delivering cash to a user, the method comprising:
generating, by a mobile device, a cash delivery request for a user associated with the mobile device in response to an input from the user, wherein the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user;
selecting, by the mobile device, one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons, wherein the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server;
transmitting, by the mobile device, the generated cash delivery request to the selected one or more delivery persons;
receiving, by the mobile device, a confirmation from a delivery person from the selected one or more delivery persons, wherein the confirmation is indicative of the cash delivery request being served by the delivery person;
generating, by the mobile device, a private key and an encrypted public key associated with the cash delivery request, wherein the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received;
transmitting, by the mobile device, the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies, wherein the private key is transmitted to the POS cash delivery device when the delivery person is at the location of the mobile device, wherein the private key is used to decrypt the public key and verify the cash delivery request;
initiating, by the mobile device, an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request, wherein the delivery person provides the amount of cash in the cash delivery request to the user at the location of the mobile device in response to a successful electronic debit transaction; and
providing, by the mobile device, a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device.
, Description:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)
TITLE OF INVENTION:
“A METHOD, MOBILE DEVICE, AND POS DEVICE FOR DELIVERING CASH TO A USER”
APPLICANT
Saraswat Infotech Private Limited
Kamdhenu Building. Business Bay, 901/902, 9th Floor. Plot no. 51, Sector 1, Nerul, Navi Mumbai – 400706
The following specification particularly describes the invention and the manner in which it is to be performed.
A METHOD, MOBILE DEVICE, AND POS DEVICE FOR DELIVERING CASH TO A USER
Technical Field
[0001] The present subject matter is related, in general to a cash home delivery system, and more particularly, but not exclusively to a method and a system for secure delivery of cash to a user using a blockchain network.
Background
[0002] Currently, users have to go to the ATM machine to withdraw cash. Maintenance of ATM machines and other ATM machine related issues such as, security, overhead cost, and network connectivity are a major problem. With the advent of technology, financial institutions have come out with a concept called Miro ATM. The financial institutions need not deploy ATM for delivering cash to customers. Instead POS devices may be deployed with business correspondents, franchises, business agents of the financial institution provided the financial institution has approved business correspondent policy. However, drawback of the Micro ATM solution is that it is deployed through Patpedhis and other payment aggregators. All the patpedhis and agents of aggregators are having static places. Thu, the customer has to come to these agents for withdrawing cash. This is again similar to going to an ATM for withdrawing cash. Further, one or more problem is that currently the customer is not aware of the where he/she can find a Micro ATM deployed by such payment aggregators and hence reachability is an issue.
[0003] In the existing environment, everyone has been talking about home delivery. From pin to piano, breakfast to dinner everyone can have delivery at home from the chosen vendor. However, current solutions do not offer any home delivery of cash in a secure manner. Implementing home delivery of cash has been a long standing challenge because one of one major issue of authenticity and verification. Various hackers try to tweak the system and phishing attacks are used to divert money from one account to another. Further, identifying the appropriate delivery person who can deliver the requested amount of cash within a specified period of time has also been a technical challenge. Nowadays while exchanging cash there is no technical method of verifying whether the cash request was generated by an authenticated person and whether the receiving person is authorized to get the cash thereby leading to financial frauds.
[0004] Currently traceability of cash transactions is a major technical issue. Existing ERP systems accept cash deposits and provide cash withdrawal facilities. Customers may have several accounts and may just keep on transferring/rotating cash within multiple accounts. None of the existing ERP systems keep a track of such activities when cash is provided to the customer. The proposed solution overcomes challenges in the existing ERP system.
[0005] Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of described systems with some aspects of the present disclosure, as set forth in the remainder of the present application and with reference to the drawings.
Summary
[0006] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
[0007] According to embodiments illustrated herein, there may be provided a method for delivering cash to a user. The method comprises generating a cash delivery request for a user associated with the mobile device in response to an input from the user. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user. The method further comprises selecting one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. In an embodiment, the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server. The method further comprises transmitting the generated cash delivery request to the selected one or more delivery persons. The method further comprises receiving a confirmation from a delivery person from the selected one or more delivery persons. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. The method further comprises generating a private key and an encrypted public key associated with the cash delivery request. In an embodiment, the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received. The method further comprises transmitting the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies. In an embodiment, the private key is transmitted to the POS cash delivery device when the delivery person is at the location of the mobile device. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. The method further comprises initiating an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request. In an embodiment, the delivery person provides the amount of cash in the cash delivery request to the user at the location of the mobile device in response to a successful electronic debit transaction. The method further comprises providing a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device.
[0008] According to embodiments illustrated herein, there may be provided a mobile application installed in a mobile device for delivering cash to a user. The mobile device comprises a processor and a memory communicatively coupled to the processor. The memory stores processor instructions, which, on execution, causes the processor to generate a cash delivery request for a user associated with the mobile device in response to an input from the user. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user. The processor may be further configured to select one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. In an embodiment, the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server. The processor may be further configured to transmit the generated cash delivery request to the selected one or more delivery persons. The processor may be further configured to receive a confirmation from a delivery person from the selected one or more delivery persons. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. The processor may be further configured to generate a private key and an encrypted public key associated with the cash delivery request. In an embodiment, the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received. The processor may be further configured to transmit the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies. In an embodiment, the private key is transmitted to the POS cash delivery device when the delivery person is at the location of the mobile device. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. The processor may be further configured to initiate an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request. In an embodiment, the delivery person provides the amount of cash in the cash delivery request to the user at the location of the mobile device in response to a successful electronic debit transaction. The processor may be further configured to provide a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device.
[0009] According to embodiments illustrated herein, there may be provided a POS cash delivery device for delivering cash to a user. The POS cash delivery device comprises a processor and a memory communicatively coupled to the processor. The memory stores processor instructions, which, on execution, causes the processor to receive a cash delivery request from a user associated with a mobile device. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user. The processor may be further configured to provide a confirmation based on an input from the delivery person. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. In an embodiment, after providing the confirmation, a blockchain record associated with the delivery person updates the cash delivery request id, the associated public key received from the mobile device and the delivery status of the cash delivery request. The processor may be further configured to receive an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device. The processor may be further configured to receive a private key from the mobile device using one or more Near Field Communication technologies when the delivery person is at the location of the mobile device. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. The processor may be further configured to compare the K1 and K2 to ensure that there is no malicious cash request being serviced. In an embodiment, before the amount of cash in the cash delivery request is provided to the user at the location (L1) of the mobile device, the user of the mobile device is verified based on at least one of the image of the user or biometrics of the user in the cash delivery request. The processor may be further configured to receive a confirmation indicating a successful electronic debit transaction. In an embodiment, the electronic debit transaction comprises transfer of an amount equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods. The processor may be further configured to provide the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device in response to the confirmation. The processor may be further configured to receive a confirmation of receipt of the amount of cash as requested in the cash delivery request from the mobile device. In an embodiment, the POS cash delivery device after a successful electronic debit transaction, updates the blockchain record of the delivery person. In an embodiment, the updates comprises cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, and delivery status.
Brief Description of the Accompanying Drawings
[0010] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
[0011] FIG. 1 is a diagram that illustrates an environment in which various embodiments of the method and the system may be implemented;
[0012] FIG. 2 is a block diagram that illustrates a mobile device that is configured to deliver cash to a user, in accordance with some embodiments of the present disclosure;
[0013] FIG. 3 is a block diagram that illustrates a POS cash delivery device that is configured to deliver cash to a user, in accordance with some embodiments of the present disclosure;
[0014] FIG. 4 is an interaction diagram that illustrates an exemplary scenario for delivering cash to the user, in accordance with some embodiments of the present disclosure;
[0015] FIG. 5 is a flowchart illustrating a method for delivering cash using a mobile device, in accordance with some embodiments of the present disclosure;
[0016] FIG. 6 is a flowchart illustrating a method for delivering cash using a POS cash delivery device, in accordance with some embodiments of the present disclosure; and
[0017] FIG. 7 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
[0018] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0019] The present disclosure may be best understood with reference to the detailed figures and description set forth herein. Various embodiments are discussed below with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions given herein with respect to the figures are simply for explanatory purposes as the methods and systems may extend beyond the described embodiments. For example, the teachings presented and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond the particular implementation choices in the following embodiments described and shown.
[0020] References to “one embodiment,” “at least one embodiment,” “an embodiment,” “one example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure, characteristic, property, element, or limitation. Further, repeated use of the phrase “in an embodiment” does not necessarily refer to the same embodiment.
[0021] Definitions: The following terms shall have, for the purposes of this application, the respective meanings set forth below. The glossary of terms described below relate to the conceptual, architectural and functional elements within the scope of work on delivering cash to a user.
[0022] Mobile device may refer to a computing device such as a computer, a device including a processor/microcontroller and/or any other electronic component, device or system that performs one or more operations according to one or more programming instructions. Examples of the mobile device include, but are not limited to, a desktop computer, a laptop, a personal digital assistant (PDA), a Smartphone, or the like. The mobile device is capable of accessing (or being accessed over) a network (e.g., using wired or wireless communication capabilities).
[0023] Mobile application refers to applications that can be instantiated on a mobile device. A mobile application, most commonly referred to as an app, is a type of application software designed to run on the mobile device, such as a smartphone or tablet computer. Mobile applications frequently serve to provide users with similar services to those accessed on PCs. Apps are generally small, individual software units with limited function. The mobile application referred to herein is used to initiate manage the request for cash to be delivered at a location of the mobile device.
[0024] POS cash delivery device may refer to a computing device that is a combination of software and hardware that allows a user/delivery person to accept card payments without updating their cash registers to read cards directly. Payments may be made via the POS cash delivery device using magnetic strip cards, electronic chip cards, NFC cards and the like.
[0025] Blockchain Network: Blockchain or a blockchain network refers to a type of data structure that enables identifying and tracking transactions digitally and sharing this information across a distributed network of computers/nodes, creating in a sense a distributed trust network. The distributed ledger technology offered by blockchain provides a transparent and secure means for tracking the ownership and transfer of assets.
[0026] Blockchain record: The blockchain network tracks digital transactions in a data structure that is made up of a series of “blocks” which are referred to herein as a blockchain record. For the sake of implementation, the blockchain record mentioned herein is used to store the transaction performed between each user and each delivery person. A user is a person who has request for cash to be delivered at a location of the mobile device. A delivery person is the person who delivers the cash to the user at the requested location.
[0027] FIG. 1 is a diagram that illustrates a system environment 100 in which various embodiments of the method and the system may be implemented. The system environment 100 may include a mobile device 102, a POS cash delivery device 104, a blockchain network 106, and a communication network 108. The mobile device 102 may be communicatively coupled to the POS cash delivery device 104, the blockchain network 106, via the communication network 108.
[0028] The mobile device 102 may refer to a computing device used by a user 110. The mobile device 102 may comprise of one or more processors and one or more memories. The one or more memories may include computer readable code that may be executable by the one or more processors to perform predetermined operations. In an embodiment, the mobile device 102 may be configured to generate a cash delivery request for a user associated with the mobile device in response to an input from the user. Further, the mobile device 102 may be configured to select one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device 102, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. Further, the mobile device 102 may be configured to transmit the generated cash delivery request to the selected one or more delivery persons.
[0029] Further, the mobile device 102 may be configured to receive a confirmation from a delivery person from the selected one or more delivery persons. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. Further, the mobile device 102 may be configured to generate a private key and an encrypted public key associated with the cash delivery request. Further, the mobile device 102 may be configured to transmit the private key to a POS cash delivery device 104 associated with the delivery person using one or more Near Field Communication technologies.
[0030] Further, the mobile device 102 may be configured to initiate an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device 104 by using one or more electronic payment methods in response to successful verification of the cash delivery request. Further, the mobile device 102 may be configured to provide a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device 104. Further, the mobile device 102 may be configured to present a user-interface to the user to provide the user input. Further, the mobile device 102 may be configured to display the request status and other information related to the cash delivery request.
[0031] POS cash delivery device 104 may refer to a computing device used by a user. The POS cash delivery device 104 may comprise of one or more processors and one or more memories. The one or more memories may include computer readable code that may be executable by the one or more processors to perform predetermined operations. In an embodiment, the POS cash delivery device 104 may receive a cash delivery request from a user associated with a mobile device 102.
[0032] Further, the POS cash delivery device 104 may be configured to provide a confirmation based on an input from the delivery person. In an embedment, the confirmation is indicative of the cash delivery request being served by the delivery person. Further, the POS cash delivery device 104 may update a blockchain record associated with the delivery person comprising the cash delivery request id, the associated public key received from the mobile device 102 and the delivery status of the cash delivery request. Further, the POS cash delivery device 104 may be configured to receive an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device 102.
[0033] Further, the POS cash delivery device 104 may be configured to receive a private key from the mobile device 102 using one or more Near Field Communication technologies when the delivery person is at the location of the mobile device 102. Further, the POS cash delivery device 104 may be configured to compare the K1 and K2 to ensure that there is no malicious cash request being serviced. In an embodiment, the before the amount of cash in the cash delivery request is provided to the user at the location (L1) of the mobile device 102, the user of the mobile device 102 is verified by the POS cash delivery device 104 based on at least one of the image of the user or biometrics of the user in the cash delivery request.
[0034] Further, the POS cash delivery device 104 may be configured to receive a confirmation indicating a successful electronic debit transaction. Further, the POS cash delivery device 104 may be configured to provide the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device 102 in response to the confirmation. Further, the POS cash delivery device 104 may be configured to receive a confirmation of receipt of the amount of cash as requested in the cash delivery request from the mobile device 102. Further, the POS cash delivery device 104 may be configured to present a user-interface to the delivery person to provide the user input, such as providing a confirmation to service a cash delivery order. Further, the POS cash delivery device 104 may be configured to display the location (L1) of the mobile device 102 where the cash is to be delivered and various other information related to the cash delivery request.
[0035] In an embodiment, the blockchain network 106 refers to a type of data structure that enables identifying and tracking transactions, such as the cash delivery request, digitally and sharing this information across a distributed network of computers/nodes, creating in a sense a distributed trust network. The distributed ledger technology offered by blockchain provides a transparent and secure means for tracking the ownership and transfer of assets. The POS cash delivery device 104 and the mobile device 102 are connected to the blockchain network to update the one or more fields in the blockchain record associated with the delivery person comprising the cash delivery request id, the associated public key received from the mobile device 102 and the delivery status of the cash delivery request. Further, the blockchain network 106 may be configured to store the encrypted public key associated with the cash delivery request that is received from the mobile device 102.
[0036] In an embodiment, the communication network 108 may correspond to a communication medium through which the mobile device 102, the POS cash delivery device 104, and the blockchain network 106 may communicate with each other. Such a communication may be performed, in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared (IR), IEEE 802.11, 802.16, 2G, 3G, 4G cellular communication protocols, and/or Bluetooth (BT) communication protocols. The communication network 108 may include, but is not limited to, the Internet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a telephone line (POTS), and/or a Metropolitan Area Network (MAN).
[0037] FIG. 2 is a block diagram that illustrates a mobile device 102 that is configured to deliver cash to a user, in accordance with some embodiments of the present disclosure;
[0038] The mobile device 102 further comprises a processor 202, a memory 204, a transceiver 208, an input/output unit 210, a request generation unit 212, a selection unit 214, and a validation unit 216. The processor 202 may be communicatively coupled to the memory 204, the transceiver 208, the input/output unit 210, the request generation unit 212, the selection unit 214, and the validation unit 216.
[0039] The processor 202 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to execute a set of instructions stored in the memory 204. The processor 202 may be implemented based on a number of processor technologies known in the art. Examples of the processor 202 include, but not limited to, an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processor.
[0040] The memory 204 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to store the set of instructions, which may be executed by the processor 202. In an embodiment, the memory 204 may be configured to store one or more programs, routines, or scripts that may be executed in coordination with the processor 202. The memory 204 may be implemented based on a Random Access Memory (RAM), a Read-Only Memory (ROM), a Hard Disk Drive (HDD), a storage server, and/or a Secure Digital (SD) card.
[0041] The transceiver 208 comprises of suitable logic, circuitry, interfaces, and/or code that may be configured to transmit the generated cash delivery request to the selected one or more delivery persons. The transceiver 208 may be configured to receive a confirmation from a delivery person from the selected one or more delivery persons. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. The transceiver 208 may be further configured to transmit the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received. The transceiver 208 may be further configured to transmit the private key to a POS cash delivery device 104 associated with the delivery person using one or more Near Field Communication technologies. In an embodiment, the private key is transmitted to the POS cash delivery device 104 when the delivery person is at the location of the mobile device 102. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. The transceiver 208 may be further configured to transmit a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device 104.
[0042] The transceiver 208 may implement one or more known technologies to support wired or wireless communication with the communication network. In an embodiment, the transceiver 208 may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a Universal Serial Bus (USB) device, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer. The transceiver 208 may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS)
[0043] The Input/ Output (I/O) unit 210 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to receive an input or transmit an output. The input/output unit 210 comprises of various input and output devices that are configured to communicate with the processor 202. Examples of the input devices include, but are not limited to, a keyboard, a mouse, a joystick, a touch screen, a microphone, and/or a docking station. Examples of the output devices include, but are not limited to, a display screen and/or a speaker.
[0044] The request generation unit 212 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to generate a cash delivery request for a user associated with the mobile device 102 in response to an input from the user. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device 102, an image of the user, and biometrics of the user. In an embodiment, the request generation unit 212 may be configured to generate a private key and an encrypted public key associated with the cash delivery request. In an embodiment, the encrypted public key may be transmitted to a blockchain network and the delivery person from whom the confirmation has been received.
[0045] The selection unit 214 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to select one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device 102, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. In an embodiment, the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server.
[0046] The validation unit 216 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to initiate an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device 104 by using one or more electronic payment methods in response to successful verification of the cash delivery request performed by the POS cash delivery device 104.
[0047] FIG. 3 is a block diagram that illustrates a POS cash delivery device 104 that is configured to deliver cash to a user, in accordance with some embodiments of the present disclosure. The POS cash delivery device 104 further comprises a processor 302, a memory 304, a transceiver 308, an input/output unit 310, a verification unit 312, and a cash delivery unit 314. The processor 202 may be communicatively coupled to the memory 304, the transceiver 308, the input/output unit 310, the verification unit 312, and the cash delivery unit 314.
[0048] The processor 302 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to execute a set of instructions stored in the memory 304. The processor 302 may be implemented based on a number of processor technologies known in the art. Examples of the processor 302 include, but not limited to, an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processor.
[0049] The memory 304 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to store the set of instructions, which may be executed by the processor 302. In an embodiment, the memory 304 may be configured to store one or more programs, routines, or scripts that may be executed in coordination with the processor 302. The memory 204 may be implemented based on a Random Access Memory (RAM), a Read-Only Memory (ROM), a Hard Disk Drive (HDD), a storage server, and/or a Secure Digital (SD) card.
[0050] The transceiver 308 comprises of suitable logic, circuitry, interfaces, and/or code that may be configured to receive a cash delivery request from a user associated with a mobile device 102. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device 102, an image of the user, and biometrics of the user. The transceiver 208 may be further configured to transmitting a confirmation based on an input from the delivery person. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. The transceiver 308 may be further configured to receive an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device 102. The transceiver 308 may be further configured to receive a private key from the mobile device 102 using one or more Near Field Communication technologies when the delivery person is at the location of the mobile device 102. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. The transceiver 308 may be further configured to receive a confirmation indicating a successful electronic debit transaction. In an embodiment, the electronic debit transaction comprises transfer of an amount equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device 104 by using one or more electronic payment methods. The transceiver 308 may be further configured to receive a confirmation of receipt of the amount of cash as requested in the cash delivery request from the mobile device 102.
[0051] The transceiver 308 may implement one or more known technologies to support wired or wireless communication with the communication network. In an embodiment, the transceiver 308 may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a Universal Serial Bus (USB) device, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer. The transceiver 308 may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
[0052] The Input/ Output (I/O) unit 310 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to receive an input or transmit an output. The input/output unit 310 comprises of various input and output devices that are configured to communicate with the processor 302. Examples of the input devices include, but are not limited to, a keyboard, a mouse, a joystick, a touch screen, a microphone, and/or a docking station. Examples of the output devices include, but are not limited to, a display screen and/or a speaker.
[0053] The verification unit 312 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to compare the K1 and K2 to ensure that there is no malicious cash request being serviced. In an embodiment, before the amount of cash in the cash delivery request is provided to the user at the location (L1) of the mobile device 102, the user of the mobile device 102 is verified based on at least one of the image of the user or biometrics of the user in the cash delivery request.
[0054] The cash delivery unit 314 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to provide the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device 102 in response to the confirmation. The cash delivery unit 34 may be further configured to update the blockchain record of the delivery person after a successful electronic debit transaction. In an embodiment, the updates comprises cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, and delivery status. The cash delivery unit 314 may be further configured to identify one or more fake fiat currency notes to be delivered to the user based on pre-determined plurality of parameters. In an embodiment, the plurality of parameters comprises a unique number associated with each fiat currency, size of note etc.
[0055] FIG. 4 is an interaction diagram 400 that illustrates an exemplary scenario for delivering cash to the user, in accordance with some embodiments of the present disclosure. Referring to FIG. 4, the various entities involved in the communication are the mobile device 102, the POS cash delivery device 104, and the blockchain network 106 for delivering cash to the user. At step 402, a mobile application may be installed in a mobile device for delivering cash to a user.
[0056] At step 404 illustrates that the user may use the mobile application installed in the mobile device for generating a cash delivery request for the user associated with the mobile device. In an embodiment, the cash delivery request may comprise an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user. For example, the User A may raise a request for getting INR 10,000 to be delivered at location XYZ. Further, while generating the request, the application may capture an image of the user that may be used for verification during delivery of the cash to the user. Additionally, biometric data such as an iris scan may be performed using the imaging device, such as a camera which is in the mobile device. In an embodiment, if the generated cash delivery request is cancelled by the user, and in response to the cancellation, the mobile device dynamically calculates a penalty amount to be imposed on the user based on one or more rules. In and embodiment, such penalty amount is collected from the user using one or more electronic payment modes.
[0057] At step 406, the mobile device may select one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. In an embodiment, the real-time location (L2) associated with each of the one or more delivery persons is retrieved from a centralized server. In an embodiment, the availability of cash with each of the one or more delivery persons is based on a historic patterns and metadata associated with a geography. In an embodiment, the cash may be dynamically redistributed amongst the one or more delivery persons based on historic patterns, and metadata associated with a geography.
[0058] In the above example, the mobile device may retrieve the real-time location (L2) of delivery persons available within a distance of 5km from the mobile device. Consider that 5 delivery persons are within a distance of 5km of the mobile device. Further, the mobile device checks whether the cash available with each of the 5 delivery persons is at least INR 10,000. The mobile device may selects only 3 delivery persons (delivery person A, delivery B, and delivery person C) for transmitting the cash delivery request as only delivery person A, delivery B, and delivery person C have sufficient cash to service the cash delivery request and are also within the 5km distance from the mobile device.
[0059] In an embodiment, the mobile device retrieves the information associated with the delivery persons from the blockchain network. In an embodiment, a blockchain record is maintained for each of the one or more delivery persons within the blockchain network. In an embodiment, the blockchain record comprises delivery person id, delivery person’s location information, cash delivery request id, cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, delivery status, type of transaction, a unique number associated with each fiat currency available with the delivery person, and a trust rating of the delivery person. For the above example, the blockchain record of delivery person A may include DEL_A_123 (delivery person id), latitude 0.123, longitude 1.567 (location), INR 20, 000 (cash available with the delivery person), K2 (encrypted public key), available for delivery (delivery status), A-C transaction (type of transaction), a unique number associated with each fiat currency available with the delivery person, and 4.3 (a trust rating of the delivery person).
[0060] At step 408, the mobile device may transmit the generated cash delivery request to the selected one or more delivery persons, such as the delivery person A, delivery person B, and delivery person C. At step 410 the POS cash delivery device being operated by each of the corresponding delivery persona may receive the cash delivery request. In an embodiment, the cash delivery request comprises an amount of cash required by the user, a location (L1) of the mobile device, an image of the user, and biometrics of the user. In the above example, each of the delivery person A, delivery person B, and delivery person C who have a POS cash delivery device with them may receive the cash delivery request.
[0061] At step 412, in response to receiving the cash delivery request, one of the delivery persons, for example, the delivery person A may provide/transmit a confirmation using the POS cash delivery device. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. A.
[0062] In an embodiment, the delivery person who has confirmed to deliver the cash is within a pre-defined distance from the location (L1) of the mobile device of the user. In an embodiment, the delivery person has an amount of cash at least equal to or greater than that of the amount requested by the user. In an embodiment, if individually each of the one or more delivery persons within the pre-defined distance from the location (L1) of the mobile device of the user do not have the amount of cash to be delivered to user within a pre-defined time, then cash available individually with each of one or more delivery persons is collated by a single delivery person and then delivered to the user after a successful verification. For example, if the cash delivery request is for INR 50,000 and the delivery person A has INR 20,000, delivery person B has INR 25,000 and the delivery person C has INR 10,000. Then in such a scenario the delivery person A may collate INR 50,000 from delivery person B and delivery person C and then server the cash delivery request of the user. In an embodiment, the blockchain record of each one or more delivery persons is updated to reflect a A-A transaction that indicates a cash exchange transaction between delivery persons, and a A-C type transaction indicates a cash exchange transaction between a delivery person and a user.
[0063] In an alternate embodiment, if individually each of one or more delivery persons within the pre-defined distance from the location (L1) of the mobile device of the user do not have the amount of cash to be delivered to user within the pre-defined time interval then the cash delivery request is split into a plurality of cash delivery requests. In an embodiment, each of the plurality of cash delivery requests are individually served by the one or more delivery persons.
[0064] At step 414, after providing the confirmation, the POS cash delivery device updates a blockchain record associated with the delivery person. In an embodiment, the updates comprise updating the cash delivery request id, the associated public key received from the mobile device and the delivery status of the cash delivery request. At step 416, the mobile device may receive the confirmation from a delivery person from the selected one or more delivery persons. In an embodiment, the confirmation is indicative of the cash delivery request being served by the delivery person. For example, the mobile device may receive the confirmation that delivery person A will be serving the cash delivery request.
[0065] At step 418, the mobile device may generate a private key and an encrypted public key associated with the cash delivery request. In an embodiment, the encrypted public key is transmitted to a blockchain network and the delivery person from whom the confirmation has been received. In an embodiment, the private key is generated based on at least an IP address of the mobile device and IMEI number of the mobile device. In an embodiment, the public key is generated based on at least the cash request id, amount of cash to be delivered, location (L1) of the device by using one or more encryption techniques. At step 420, the POS cash delivery device may receive an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device. At step 422, the mobile device may transmit the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies. In an embodiment, the private key is transmitted to the POS cash delivery device when the delivery person is at the location of the mobile device. In an embodiment, the private key is used to decrypt the public key and verify the cash delivery request. In the above example, when the delivery person A reaches the location of the mobile device then the user may transmit the private key to the POS cash delivery device associated with the delivery person A using one or more Near Field Communication technologies.
[0066] At step 424, the POS cash delivery device may receive the private key from the mobile device. At step 426, the POS cash delivery device may compare the K1 and K2 to ensure that there is no malicious cash request being serviced. At step 428, the POS cash delivery device may, perform verification before the amount of cash in the cash delivery request is provided to the user at the location (L1) of the mobile device, based on at least one of the image of the user or biometrics of the user in the cash delivery request. For example, the POS device may capture an image of the user A and the image of the user A that was captured when the cash request was raised is used to verify the user.
[0067] At step 430, after the verification is successful, the mobile device may initiate an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request. At step 432, the POS cash delivery device may receive a confirmation indicating a successful electronic debit transaction. In an embodiment, the electronic debit transaction comprises transfer of an amount equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods.
[0068] At step 434, the POS cash delivery device is used to provide the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device in response to the confirmation. For example, the delivery person provides the amount of cash in the cash delivery request to the user A at the location XYZ of the mobile device in response to a successful electronic debit transaction. In the above example, the delivery person A provides INR 10,000 to the user A after the verification and successful electronic debit transaction. In an embodiment, the POS cash delivery device may identify one or more fake fiat currency notes to be delivered to the user based on pre-determined plurality of parameters. In an embodiment, the plurality of parameters comprises a unique number associated with each fiat currency, size of note and the like.
[0069] At step 436, the mobile device may provide/transmit a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device. At step 438, the POS cash delivery device may receive the confirmation of receipt, from the mobile device, of the amount of cash as requested in the cash delivery request. At step 440, the POS cash delivery device may after the successful electronic debit transaction and the receipt of the confirmation, update the blockchain record of the delivery person. In an embodiment, the updates comprises cash available with the delivery person, denomination of cash available with the delivery person, encrypted public key, and delivery status. For the above example, the blockchain record of the delivery person A may be updated. If the delivery person had initially INR 20,000 then the updated amount with the delivery person A is INR 10,000 and the delivery status of the cash delivery request may be changed to delivered.
[0070] FIG. 5 is a flowchart illustrating a method 500 for delivering cash using a mobile device 102, in accordance with some embodiments of the present disclosure. The method starts at step 502 and proceeds at step 504.
[0071] At step 504, the mobile device may generate a cash delivery request for a user associated with the mobile device in response to an input from the user. At step 506, the mobile device may select one or more delivery persons for transmitting the generated cash delivery request based on the location (L1) of the mobile device, a real-time location (L2) associated with each of the one or more delivery persons and cash available with each of the one or more delivery persons. At step 508, the mobile device may transmit the generated cash delivery request to the selected one or more delivery persons. At step 510, the mobile device may receive a confirmation from a delivery person from the selected one or more delivery persons. At step 512, the mobile device may generate a private key and an encrypted public key associated with the cash delivery request. At step 514, the mobile device may transmit the private key to a POS cash delivery device associated with the delivery person using one or more Near Field Communication technologies. At step 516, the mobile device may initiate an electronic debit transaction equivalent to the amount of cash in the cash delivery request to a merchant of the POS cash delivery device by using one or more electronic payment methods in response to successful verification of the cash delivery request. At step 518, the mobile device may provide a confirmation of receipt of the amount of cash as requested in the cash delivery request to the POS cash delivery device. Control passes to end step 520.
[0072] FIG. 6 is a flowchart illustrating a method 600 for delivering cash using a POS cash delivery device 104, in accordance with some embodiments of the present disclosure. The method starts at step 602 and proceeds at step 604.
[0073] At step 604, the POS cash delivery device may receive a cash delivery request from a user associated with a mobile device. At step 606, the POS cash delivery device may provide a confirmation based on an input from the delivery person and further update a blockchain record associated with the delivery person. At step 608, the POS cash delivery device may receive an encrypted public key (K1) from a blockchain network and an encrypted public key (K2) from the mobile device. At step 610, the POS cash delivery device may receive a private key from the mobile device using one or more Near Field Communication technologies when the delivery person is at the location of the mobile device. At step 612, the POS cash delivery device may compare the K1 and K2 to ensure that there is no malicious cash request being serviced. At step 614, the POS cash delivery device may receive a confirmation indicating a successful electronic debit transaction. At step 616, the POS cash delivery device may provide the amount of cash in the cash delivery request to the user at the location (L1) of the mobile device in response to the confirmation. At step 618, the POS cash delivery device may receive a confirmation of receipt of the amount of cash as requested in the cash delivery request from the mobile device. Control passes to end step 620.
[0074] FIG. 7 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
[0075] Variations of computer system 701 may be used for generating a plurality of structured relations between a plurality of words. The computer system 701 may comprise a central processing unit (“CPU” or “processor”) 702. Processor 702 may comprise at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as such as those included in this disclosure, or such a device itself. The processor may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc. The processor may include a microprocessor, such as AMD ATHLON, DURON OR OPTERON, ARM’S application, embedded or secure processors, IBM POWERPC, INTEL’S CORE, ITANIUM, XEON, CELERON or other line of processors, etc. The processor 502 may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.
[0076] Processor 702 may be disposed in communication with one or more input/output (I/O) devices via I/O interface 703. The I/O interface 703 may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WIMAX, or the like), etc.
[0077] Using the I/O interface 703, the computer system 701 may communicate with one or more I/O devices. For example, the input device 704 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc. Output device 705 may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like), audio speaker, etc. In some embodiments, a transceiver 706 may be disposed in connection with the processor 702. The transceiver may facilitate various types of wireless transmission or reception. For example, the transceiver may include an antenna operatively connected to a transceiver chip (e.g., TEXAS INSTRUMENTS WILINK WL1283, BROADCOM BCM4750IUB8, INFINEON TECHNOLOGIES X-GOLD 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, BLUETOOTH, FM, GLOBAL POSITIONING SYSTEM (GPS), 2G/3G HSDPA/HSUPA COMMUNICATIONS, etc.
[0078] In some embodiments, the processor 702 may be disposed in communication with a communication network 708 via a network interface 707. The network interface 707 may communicate with the communication network 708. The network interface may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network 708 may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface 707 and the communication network 708, the computer system 701 may communicate with devices 709, 710, and 711. These devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., APPLE IPHONE, BLACKBERRY, ANDROID-based phones, etc.), tablet computers, eBook readers (AMAZON KINDLE, NOOK, etc.), laptop computers, notebooks, gaming consoles (MICROSOFT XBOX, NINTENDO DS, SONY PLAYSTATION, etc.), or the like. In some embodiments, the computer system 701 may itself embody one or more of these devices.
[0079] In some embodiments, the processor 702 may be disposed in communication with one or more memory devices 715 (e.g., RAM 713, ROM 714, etc.) via a storage interface 712. The storage interface may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-1394, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc.
[0080] The memory devices may store a collection of program or database components, including, without limitation, an operating system 716, user interface application 717, web browser 718, mail server 719, mail client 720, user/application data 721 (e.g., any data variables or data records discussed in this disclosure), etc. The operating system 716 may facilitate resource management and operation of the computer system 701. Examples of operating systems include, without limitation, APPLE MACINTOSH OS X, UNIX, UNIX-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., RED HAT, UBUNTU, KUBUNTU, etc.), IBM OS/2, MICROSOFT WINDOWS (XP, VISTA/7/8, ETC.), APPLE IOS, GOOGLE ANDROID, BLACKBERRY OS, or the like. User interface 717 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 501, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical user interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems’ AQUA, IBM OS/2, MICROSOFT WINDOWS (e.g., Aero, Metro, etc.), UNIX X-WINDOWS, web interface libraries (e.g., ACTIVEX, JAVA, JAVASCRIPT, AJAX, HTML, ADOBE FLASH, etc.), or the like.
[0081] In some embodiments, the computer system 701 may implement a web browser 718 stored program component. The web browser 718 may be a hypertext viewing application, such as MICROSOFT INTERNET EXPLORER, GOOGLE CHROME, MOZILLA FIREFOX, APPLE SAFARI, etc. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), etc. Web browsers may utilize facilities such as AJAX, DHTML, ADOBE FLASH, JAVASCRIPT, JAVA, application programming interfaces (APIs), etc. In some embodiments, the computer system 701 may implement a mail server 719 stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ACTIVEX, ANSI C++/C#, MICROSOFT .NET, CGI SCRIPTS, JAVA, JAVASCRIPT, PERL, PHP, PYTHON, WEBOBJECTS, etc. The mail server may utilize communication protocols such as internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like. In some embodiments, the computer system 701 may implement a mail client 720 stored program component. The mail client may be a mail viewing application, such as APPLE MAIL, MICROSOFT ENTOURAGE, MICROSOFT OUTLOOK, MOZILLA THUNDERBIRD, etc.
[0082] In some embodiments, computer system 701 may store user/application data 721, such as the data, variables, records, etc. as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as ORACLE OR SYBASE. Alternatively, such databases may be implemented using standardized data structures, such as an array, hash, linked list, struct, structured text file (e.g., XML), table, or as object-oriented databases (e.g., using OBJECTSTORE, POET, ZOPE, etc.). Such databases may be consolidated or distributed, sometimes among the various computer systems discussed above in this disclosure. It is to be understood that the structure and operation of the any computer or database component may be combined, consolidated, or distributed in any working combination.
[0083] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
[0084] The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise. The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise. The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.
ADVANTAGES
[0085] The proposed approach provides a complete technical solution for home delivery of cash.
The disclosed method and system provides an end to end tracing of money transfer. Further, the immutable records of the blockchain network ensure that the data is not tampered with and hence money transfer trace is clean. Further, the disclosed method and system reduces the risk of cash theft/risk of being transferred to someone else as all the transactions are now traceable. The disclosed method and system tries to overcome to the technical problem of traceability of cash transactions during home delivery of cash. Further, the disclosed method and system verifies whether the cash request was generated by an authenticated person and whether the receiving person is authorized to get the cash thereby avoiding financial frauds. Conventional ERP systems fail to maintain cash traceability especially for cash for home delivery transactions.
[0086] In light of the above mentioned advantages and the technical advancements provided by the disclosed method and system, the claimed steps as discussed above are not routine, conventional, or well understood in the art, as the claimed steps enable the following solutions to the existing problems in conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the device itself as the claimed steps provide a technical solution to a technical problem.
[0087] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.
[0088] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
[0089] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
[0090] The present disclosure may be realized in hardware, or a combination of hardware and software. The present disclosure may be realized in a centralized fashion, in at least one computer system, or in a distributed fashion, where different elements may be spread across several interconnected computer systems. A computer system or other apparatus adapted for carrying out the methods described herein may be suited. A combination of hardware and software may be a general-purpose computer system with a computer program that, when loaded and executed, may control the computer system such that it carries out the methods described herein. The present disclosure may be realized in hardware that comprises a portion of an integrated circuit that also performs other functions.
[0091] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.
[0092] Those skilled in the art will appreciate that any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like. The claims can encompass embodiments for hardware and software, or a combination thereof.
[0093] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.
| # | Name | Date |
|---|---|---|
| 1 | 201921052458-STATEMENT OF UNDERTAKING (FORM 3) [17-12-2019(online)].pdf | 2019-12-17 |
| 2 | 201921052458-REQUEST FOR EXAMINATION (FORM-18) [17-12-2019(online)].pdf | 2019-12-17 |
| 3 | 201921052458-POWER OF AUTHORITY [17-12-2019(online)].pdf | 2019-12-17 |
| 4 | 201921052458-FORM 18 [17-12-2019(online)].pdf | 2019-12-17 |
| 5 | 201921052458-FORM 1 [17-12-2019(online)].pdf | 2019-12-17 |
| 6 | 201921052458-FIGURE OF ABSTRACT [17-12-2019(online)].pdf | 2019-12-17 |
| 7 | 201921052458-DRAWINGS [17-12-2019(online)].pdf | 2019-12-17 |
| 8 | 201921052458-DECLARATION OF INVENTORSHIP (FORM 5) [17-12-2019(online)].pdf | 2019-12-17 |
| 9 | 201921052458-COMPLETE SPECIFICATION [17-12-2019(online)].pdf | 2019-12-17 |
| 10 | Abstract1.jpg | 2020-01-01 |
| 11 | 201921052458-FER.pdf | 2021-10-19 |
| 1 | SearchHistoryE_09-08-2021.pdf |