Patent Application
20250148475
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Trademarks used in the disclosure of the invention, and the applicants, make no claim to any trademarks referenced.
The invention relates in general to the field of finance and more specifically to a delivery process for sending and receiving monetary assets.
Currently the state of the art includes Embodiments of the invention described in this specification relate generally to money delivery systems, and more particularly, to a non-financial monetary delivery system.
Many people would like to transfer money to friends or family in a different country, however, many of the intended recipients of such transferred money cannot afford to go to a financial institution to collect the money.
Current money delivery infrastructure expects person to either travel to financial institution location to collect money or own an account in financial institution.
Therefore, what is needed is a way to eliminate the need for an individual to own an account with financial institution in order to deliver and receive money on demand at doorstep in respective foreign currency.
Bearing in mind the problems and deficiencies of the prior art, it is therefore an object of the present invention to provide a delivery process for sending and receiving monetary assets.
It is another object of the present invention to provide a system which includes software for the delivery process for sending and receiving monetary assets.
Still other objects and advantages of the invention will in part be obvious and will in part be apparent from the specification.
The above and other objects, which will be apparent to those skilled in the art, are achieved in the present invention which is directed to a computer readable medium comprising instructions which, when executed by a processor, cause the computer readable medium to carry out steps of a delivery process for requesting and receiving money. The steps for the delivery process include a user accessing a login and signup screen and the system creating a subscriber profile with a subscriber type. If the subscriber profile is not complete, sending at least one reminder until the subscriber completes the subscriber profile. If the subscriber type is a service provider, capturing the subscriber consent to execute a background check. If the background check is passed from checking agency, updating the status of subscriber profile with a background check status; and returning the user to the login and signup screen. If the background check is not passed from the checking agency, declining subscription to the user and send an email to the user. If the subscriber type is not a service provider and if the user intends to initiate a transaction and if the user want to send money, the money sender subscriber initiate this transaction. The delivery process includes choosing a money receiver subscriber mapped to a money sender subscriber. If the money receiver subscriber is not found, creating a money receiver subscriber profile. The delivery process includes initiating a send money transaction and depositing the money sent in a system administrator bank account. The delivery process includes the money sender and money receiver receiving a system generated transaction code and performing a broadcast transaction. The delivery process includes the money receiver subscriber initiating a transaction, linking the money sender subscriber to the money receiver subscriber, initiating a request for a money transaction 38 and routing the money transaction to a designated money sender subscriber. The delivery process includes the money sender subscriber reviewing the transaction and, if the money transfer is approved, process the send money transaction. If the money transfer is not approved, declining the money transaction and switching the money transaction status to declined and skipping to the end program step. The delivery process includes broadcasting the transaction to service providers who covers the money receiver zip code and, if the service provider accepts transaction the service provider subscriber accepts the transaction, linking money transaction to service provider who accepted transaction and marking the transaction as reserved. The delivery process includes removing the money transaction from the broadcast, the service provider delivering money to money receiver, the service provider keying in transaction code shared by money receiver subscriber, a system administrator validating the transaction code and, if the code is valid, transferring money to service provider account and marking the transaction as completed and ending program, and if the code is not valid, declining the transfer to service provider and increment number of attempts by 1, and if the number of attempts is less than 3, then returning to checking if the code is valid, and if the number of attempts is not less than 3, GOTO Broadcast transaction to service providers who covers the money receiver zip code. The delivery process steps include ending the program.
A non-financial monetary delivery system and a non-financial monetary delivery process are disclosed which eliminate the need for an individual to own an account with a financial institution in order to request, have delivered, and receive money on demand at a location of the individual (virtual doorstep) in a respective foreign currency.
The preceding summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this specification. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description, and Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description, and Drawings, but rather are to be defined by the appended claims, because the claimed subject matter can be embodied in other specific forms without departing from the spirit of the subject matter.
A further understanding of the nature and advantages of particular embodiments may be realized by reference to the remaining portions of the specification and the drawings, in which like reference numerals are used to refer to similar components. When reference is made to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components.
Corresponding reference characters indicate corresponding parts throughout the several views. The exemplifications set out herein illustrate embodiments of the invention and such exemplifications are not to be construed as limiting the scope of the invention in any manner.
While various aspects and features of certain embodiments have been summarized above, the following detailed description illustrates a few exemplary embodiments in further detail to enable one skilled in the art to practice such embodiments. The described examples are provided for illustrative purposes and are not intended to limit the scope of the invention.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the described embodiments. It will be apparent to one skilled in the art however that other embodiments of the present invention may be practiced without some of these specific details. Several embodiments are described herein, and while various features are ascribed to different embodiments, it should be appreciated that the features described with respect to one embodiment may be incorporated with other embodiments as well. By the same token however, no single feature or features of any described embodiment should be considered essential to every embodiment of the invention, as other embodiments of the invention may omit such features.
In this application the use of the singular includes the plural unless specifically stated otherwise and use of the terms “and” and “or” is equivalent to “and/or,” also referred to as “non-exclusive or” unless otherwise indicated. Moreover, the use of the term “including,” as well as other forms, such as “includes” and “included,” should be considered non-exclusive. Also, terms such as “element” or “component” encompass both elements and components including one unit and elements and components that include more than one unit, unless specifically stated otherwise.
Lastly, the terms “or” and “and/or” as used herein are to be interpreted as inclusive or meaning any one or any combination. Therefore, “A, B or C” or “A, B and/or C” mean “any of the following: A; B; C; A and B; A and C; B and C; A, B and C.” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.
As this invention is susceptible to embodiments of many different forms, it is intended that the present disclosure be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described.
Some embodiments of the invention include non-financial monetary delivery system that eliminates the need for an individual to own an account with a financial institution in order to request, have delivered, and receive money on demand at a location of the individual (virtual doorstep) in a respective foreign currency, and some embodiments include a non-financial monetary deliver process for the same. In some embodiments, the non-financial monetary delivery system includes a banking information module, a subscriber information module, a money transaction module, money-in module, a money-out module, a mapping terminal module, a geo-locator module, and a subscriber type categorization module which individually and collectively support money transfer transactions between a money sender subscriber and a money receiver subscriber by way of a service provider subscriber.
In some embodiments, the non-financial monetary delivery process includes several steps for completing a money transfer transaction between a money sender subscriber and a money receiver subscriber by way of a service provider subscriber, whereby (i) the money receiver subscriber requests money via the money-in module, (ii) the mapping terminal module is used to determine mappings between the money receiver subscriber, the money sender subscriber, and a list of service provider subscribers which can be routed through a global banking account upon funding of an amount of money by the money sender subscriber, (iii) delegating a money out request from the money sender subscriber to the list of service provider subscribers, (iv) accepting the money out request by a particular service provider subscriber in the list of service provider subscribers, (v) delivering the money to the money receiver subscriber by the particular service provider subscriber, (vi) receiving a money-in code for the particular service provider subscriber to enter upon delivery of the money to the money receiver subscriber, and (vii) transferring the amount of money, which covers the money delivered and an associated service provider subscriber fee, to the particular service provider subscriber from the global banking account as funded by the money sender subscriber for delivery of the money to the money receiver subscriber.
Embodiments of the non-financial monetary delivery system and the non-financial monetary deliver process described in this specification solve the problems noted above by implementation of software that runs on a computing device, such as implementation of an app (e.g., a mobile app that runs on a smartphone) and/or website cloud service, in which subscribers (money sender subscribers) of the app/website can send money to family (money receiver subscribers) in a different country by generating a code with intent to send money and giving the code to a target family member (money receiver subscriber), followed by broadcasting the intent of transfer to service provider subscribers in the target country area. The target country service provider subscriber who volunteers to go to the home (or other specified location) of and give the money to the targeted family member (money receiver subscriber) will get the code and enter it (e.g., into the mobile app) to get money transferred from the source money sender subscriber's account or from a global banking account funded by the money sender subscriber, thereby making transferring and delivering money to family members in foreign countries easier since there is no need for the money receiver subscriber (e.g., family members or others) to have an individual bank account. This also makes money readily available for family members in foreign countries who may not have resources to accept money in a bank (without a bank account) or travel to a remote location and collect money from the receiving financial institution.
In addition, some embodiments of the non-financial monetary delivery system and the non-financial monetary deliver process improve upon the currently existing options which operate based on the fundamental assumption that everyone in foreign country has account with a financial institution, which is not true for all countries which are still in a developing phase (e.g., countries in Africa or India). However, the non-financial monetary delivery system and the non-financial monetary deliver process remedy this problem by eliminating the need for an individual to own an account with a financial institution, by delivering money to them on demand at their doorstep in the respective foreign currency.
The non-financial monetary delivery system and the non-financial monetary delivery process of the present disclosure may be comprised of the following elements and carry out the following steps.
1. Subscribers include money delivery drivers/individuals (service provider subscribers in the app), source of money transfer individuals/entities (money sender subscribers in the app), and target money transfer individuals/families for delivery of the money (money receiver subscribers in the app).
2. Source (money sender) and target (money receiver) are mapped m a mapping table, via a mapping terminal module, at the time of subscription in the app.
3. Money delivery drivers subscribe in the app with bank account details to become service provider subscribers.
4. When target money receiver subscriber initiates a request for money, a money-in request is transmitted by a money-in module to go immediately and directly to the mapped source money sender subscriber automatically.
5. The source money sender subscriber accepts the money-in request and gets a system generated code that it shares with the target money receiver subscriber to (subsequently) share only with a service provider subscriber (e.g., delivery driver) who delivers the money to the location of the target money receiver subscriber.
6. The source money sender subscriber then uses geo-search by geography of the target money receiver subscriber to broadcast the intent to transfer the money to all service provider subscriber delivery drivers in that area. The service provider subscriber who accepts and delivers the money to the target money receiver subscriber (e.g., at the doorstep of the target or other specified location) then gets the code from the target money receiver subscriber.
7. The service provider subscriber who delivered the money to the target money receiver subscriber inputs, enters, or confirms the code to the source money sender subscriber (via the mobile app) and then the source money sender subscriber transfers the money to the bank account of the service provider subscriber. Alternatively, the source money sender subscriber provides the money to a global banking account in advance of the service provider subscriber delivering the money to the target money receiver subscriber, and when the service provider subscriber enters the code after delivery of the money to the target money receiver subscriber, the global banking account triggers the automatic release and transfer of the money to the bank account of the service provider subscriber.
8. A money transaction record is created in the database with the code and amount of money transferred between the source money sender subscriber, the target money receiver subscriber, and the service provider subscriber along with other details and a date and time stamp.
The non-financial monetary delivery system and the non-financial monetary deliver process of the present disclosure uses the subscriber module to create the different types of subscribers (e.g., money sender subscriber, money receiver subscriber, service provider subscriber). However, it is possible that a subscriber can be two or more different types of subscribers with respect to different mappings related to different subscribers. While both money sender subscribers and service provider subscribers need to have bank account details, payments and completion of transactions is always dependent upon money transfers from funded accounts. Also, the typical working use case involves the source and the target having many to many (M-M) mappings with each other in the database.
To make the non-financial monetary delivery system and carry out the non-financial monetary deliver process, application development may be involved to store various devices using a programming language or framework, such as the JavaScript framework. To use the non-financial monetary delivery system and the non-financial monetary deliver process, a person may download the app from an app store and subscribe to it free or cost. Additionally, the non-financial monetary delivery system and the non-financial monetary deliver process eventually can support card chips for subscribers which can be linked to their bank accounts for easy transfer of money between source and money delivery driver.
Referring now to the drawings
Turning to another example,
Now referring to another example,
By way of another example,
Turning to another example,
By contrast to the money-in module 500 described above,
Moving to another example,
While the subscriber information module 200, described above by reference to
While the money transaction module 300, described above by reference to
In another example,
By way of example,
On the other hand, when a mapping exists in the mapping terminal, the non-financial monetary delivery process 1100 routes the money-in request to the money sender subscriber (at 1125). Then, when the money sender subscriber accepts the money-in request (at 1130), the non-financial monetary delivery process 1100 proceeds to transfer the money from the money sender bank account to a global bank account (at 1135).
Next, the non-financial monetary delivery process 1100 routes the request to the geo-locator module (at 1140) which determines (at 1145) whether there is any service provider in the area in and around the destination address of the money receiver. For example, if there is no service provider subscriber in the area of the money receiver, then no mapping would exist and the transfer may not be completed. On the other hand, when a service provider subscriber exists in the area, then a mapping between the money sender and the service provider can be created with bank details of each, or, in the case where the money receiver is making a subsequent money-in request, the money sender and the service provider may already have been saved persistently by the mapping terminal. Thus, when no service provider subscriber exists within or around the area of the destination address of the money receiver, then the transaction is declined (at 1120) and the non-financial monetary delivery process 1100 ends.
On the other hand, when a service provider subscriber does exist in or around the area of the money receiver, then the non-financial monetary delivery process 1100 returns the list to the source subscriber with service fees (at 1150).
Turning now to
Next, after the request 1s approved for the first money sender, the non-financial monetary delivery process 1100 proceeds to the next step during which the first service provider subscriber travels to the money receiver subscriber's address (destination address) and delivers or hands over the money (at 1165). At the next step of the non-financial monetary delivery process 1100, the first service provider subscriber collects the money-in code from the recipient (at 1170), and then enters/inputs the code and confirms completion (at 1175). The non-financial monetary delivery process 1100 then proceeds to a step in which the money from the money sender is transferred to the first service provider subscriber's bank account from the global bank account (at 1180). Then the money-out request is closed and the money transaction is updated (at 1185), after which the non-financial monetary delivery process 1100 ends.
Now turning to another example,
Now turning to another example,
Now,
In another example,
Similarly,
Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium or machine readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
In this specification, the terms “software”, “module”, “application”, “app”, and “mobile app” (referred to below as “software”) are meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor, such as the processor of a mobile computing device or a mobile communication device, such as a smartphone, a hand-held computing device, or a tablet computing device (referred to simply as a “mobile device”), or the processor of a traditional computing device, such as a server computer, a desktop computer, or a laptop computer (referred to simply as a “computer”). Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
The bus 1805 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 1800. For instance, the bus 1805 communicatively connects the processing unit(s) 1810 with the read-only memory 1820, the system memory 1815, and the permanent storage device 1825.
From these various memory units, the processing unit(s) 1810 retrieves instructions to execute and data to process in order to execute the processes of the invention. The processing unit(s) may be a single processor or a multi-core processor in different embodiments.
The read-only-memory (ROM) 1820 stores static data and instructions that are needed by the processing unit(s) 1810 and other modules of the electronic system. The permanent storage device 1825, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 1800 is off Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 1825.
Other embodiments use a removable storage device (such as a floppy disk or a flash drive) as the permanent storage device 1825. Like the permanent storage device 1825, the system memory 1815 is a read-and-write memory device. However, unlike storage device 1825, the system memory 1815 is a volatile read-and-write memory, such as a random access memory. The system memory 1815 stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 1815, the permanent storage device 1825, and/or the read-only memory 1820. For example, the various memory units include instructions for processing appearance alterations of displayable characters in accordance with some embodiments. From these various memory units, the processing unit(s) 1810 retrieves instructions to execute and data to process in order to execute the processes of some embodiments.
The bus 1805 also connects to the input and output devices 1830 and 1835. The input devices enable the user to communicate information and select commands to the electronic system. The input devices 1830 include alphanumeric keyboards and pointing devices (also called “cursor control devices”). The output devices 1835 display images generated by the electronic system 1800. The output devices 1835 include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some embodiments include devices such as a touchscreen that functions as both input and output devices.
As shown in
One aspect of the present invention is directed to a computer readable medium including instructions which, when executed by a processor, cause the computer readable medium to carry out steps of performing a delivery process for requesting and receiving money. The delivery process includes a user accessing a login and signup screen 12 and the system creating a subscriber profile with a subscriber type 18. If the subscriber profile is not complete 20, sending at least one reminder until the subscriber completes the subscriber profile 16. If the subscriber type is a service provider 22, capturing the subscriber consent to execute a background check. If the background check is passed from checking agency 24, updating a status of subscriber profile with a background check status; and returning the user to the login and signup screen 26. If the background check is not passed from the checking agency, declining subscription to the user and send an email to the user 28. If the subscriber type is not a service provider and if the user intends to initiate a transaction 14 and if the user want to send money, the money sender subscriber initiate this transaction 30. The delivery process includes choosing a money receiver subscriber mapped to a money sender subscriber 54. If the money receiver subscriber is not found 56, creating a money receiver subscriber profile 58. The delivery process includes initiating a send money transaction 60 and depositing the money sent in a system administrator bank account 62. The delivery process includes the money sender and money receiver receiving a system generated transaction code 64 and performing a broadcast transaction 66. The delivery process includes the money receiver subscriber initiating a transaction 35, linking the money sender subscriber to the money receiver subscriber 36, initiating a request for a money transaction 38 and routing the money transaction to a designated money sender subscriber 40. The delivery process includes the money sender subscriber reviewing the transaction 42 and, if the money transfer is approved 44, process the send money transaction 46. If the money transfer is not approved, declining the money transaction 47 and switching the money transaction status to declined; 48 and skipping to the end program step 50. The delivery process includes broadcasting the transaction to service providers who covers the money receiver zip code 52 and, if the service provider accepts transaction 68 the service provider subscriber accepts the transaction 70, linking money transaction to service provider who accepted transaction and marking the transaction as reserved 72. The delivery process includes removing the money transaction from the broadcast 74, the service provider delivering money to money receiver 76, the service provider keying in transaction code shared by money receiver subscriber 78, a system administrator validating the transaction code 79 and, if the code is valid 80, transferring money to service provider account 92 and marking the transaction as completed 94 and ending program 96, and if the code is not valid, declining the transfer to service provider 82 and increment number of attempts by 1 [84], and if the number of attempts is less than 3 [86], then returning 90 to checking if the code is valid 80, and if the number of attempts is not less than 3, GOTO 88 Broadcast transaction to service providers who covers the money receiver zip code 68. The delivery process steps include ending the program.
Another aspect of the present invention is directed to a computer readable medium comprising instructions which, when executed by a processor, cause the computer readable medium to carry out steps of a delivery process for requesting and receiving money. The steps as shown in the flowchart of
In an example of a process for monetary delivery, the following are the instructions lines which follow the flowchart provided in
These functions described above can be implemented m digital electronic circuitry, in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be packaged or included in mobile devices. The processes may be performed by one or more programmable processors and by one or more set of programmable logic circuitry. General and special purpose computing and storage devices can be interconnected through communication networks.
Some embodiments include e electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, disc media (CDs, DVDs, Blu-Ray® discs, ultra density optical discs, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, and/or any other optical or magnetic media. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
In some embodiments the method or methods described above may be executed or carried out by a computing system including a tangible computer-readable storage medium, also described herein as a storage machine, that holds machine-readable instructions executable by a logic machine (i.e. a processor or programmable control device) to provide, implement, perform, and/or enact the above described methods, processes and/or tasks. When such methods and processes are implemented, the state of the storage machine may be changed to hold different data. For example, the storage machine may include memory devices such as various hard disk drives, CD, or DVD devices. The logic machine may execute machine-readable instructions via one or more physical information and/or logic processing devices. For example, the logic machine may be configured to execute instructions to perform tasks for a computer program. The logic machine may include one or more processors to execute the machine-readable instructions. The computing system may include a display subsystem to display a graphical user interface (GUI) or any visual element of the methods or processes described above. For example, the display subsystem, storage machine, and logic machine may be integrated such that the above method may be executed while visual elements of the disclosed system and/or method are displayed on a display screen for user consumption. The computing system may include an input subsystem that receives user input. The input subsystem may be configured to connect to and receive input from devices such as a mouse, keyboard or gaming controller. For example, a user input may indicate a request that certain task is to be executed by the computing system, such as requesting the computing system to display any of the above described information, or requesting that the user input updates or modifies existing stored information for processing. A communication subsystem may allow the methods described above to be executed or provided over a computer network. For example, the communication subsystem may be configured to enable the computing system to communicate with a plurality of personal computing devices. The communication subsystem may include wired and/or wireless communication devices to facilitate networked communication. The described methods or processes may be executed, provided, or implemented for a user or one or more computing devices via a computer-program product such as via an application programming interface (API).
Since many modifications, variations, and changes in detail can be made to the described embodiments of the invention, it is intended that all matters in the foregoing description and shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense. Furthermore, it is understood that any of the features presented in the embodiments may be integrated into any of the other embodiments unless explicitly stated otherwise. The scope of the invention should be determined by the appended claims and their legal equivalents.
In addition, the present invention has been described with reference to embodiments, it should be noted and understood that various modifications and variations can be crafted by those skilled in the art without departing from the scope and spirit of the invention. Accordingly, the foregoing disclosure should be interpreted as illustrative only and is not to be interpreted in a limiting sense. Further it is intended that any other embodiments of the present invention that result from any changes in application or method of use or operation, method of manufacture, shape, size, or materials which are not specified within the detailed written description or illustrations contained herein are considered within the scope of the present invention.
Insofar as the description above and the accompanying drawings disclose any additional subject matter that is not within the scope of the claims below, the inventions are not dedicated to the public and the right to file one or more applications to claim such additional inventions is reserved.
Although very narrow claims are presented herein, it should be recognized that the scope of this invention is much broader than presented by the claim. It is intended that broader claims will be submitted in an application that claims the benefit of priority from this application.
While this invention has been described with respect to at least one embodiment, the present invention can be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains and which fall within the limits of the appended claims.
This application is a Utility patent application claiming priority to U.S. patent application Ser. No. 17/164,451, filed Feb. 1, 2021, which claims priority to U.S. Provisional Patent Application 62/981,115, filed on Feb. 25, 2020, both of which are incorporated by reference herein in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62981115 | Feb 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17164451 | Feb 2021 | US |
| Child | 18441171 | US |
