US7233960B1 - System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application - Google Patents
System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application Download PDFInfo
- Publication number
- US7233960B1 US7233960B1 US10/281,481 US28148102A US7233960B1 US 7233960 B1 US7233960 B1 US 7233960B1 US 28148102 A US28148102 A US 28148102A US 7233960 B1 US7233960 B1 US 7233960B1
- Authority
- US
- United States
- Prior art keywords
- project
- data capture
- data
- merchant
- objects
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 87
- 238000013481 data capture Methods 0.000 title claims abstract description 78
- 238000012545 processing Methods 0.000 title claims abstract description 62
- 238000009826 distribution Methods 0.000 title description 41
- 230000008569 process Effects 0.000 claims abstract description 51
- 230000002730 additional effect Effects 0.000 claims 3
- 238000013479 data entry Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 17
- 238000013461 design Methods 0.000 description 16
- 239000000463 material Substances 0.000 description 12
- 238000007726 management method Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000003860 storage Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 9
- 230000007723 transport mechanism Effects 0.000 description 9
- 229920001690 polydopamine Polymers 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 230000008520 organization Effects 0.000 description 6
- 230000001413 cellular effect Effects 0.000 description 5
- 230000033001 locomotion Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 238000013519 translation Methods 0.000 description 5
- 230000014616 translation Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000013480 data collection Methods 0.000 description 4
- 230000006872 improvement Effects 0.000 description 4
- 230000002452 interceptive effect Effects 0.000 description 4
- 238000012552 review Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 238000000275 quality assurance Methods 0.000 description 2
- 210000004927 skin cell Anatomy 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- SPNQRCTZKIBOAX-UHFFFAOYSA-N Butralin Chemical compound CCC(C)NC1=C([N+]([O-])=O)C=C(C(C)(C)C)C=C1[N+]([O-])=O SPNQRCTZKIBOAX-UHFFFAOYSA-N 0.000 description 1
- 208000015976 Corneal dystrophy-perceptive deafness syndrome Diseases 0.000 description 1
- 206010029412 Nightmare Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 239000011449 brick Substances 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 210000004027 cell Anatomy 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 239000004570 mortar (masonry) Substances 0.000 description 1
- COCAUCFPFHUGAA-MGNBDDOMSA-N n-[3-[(1s,7s)-5-amino-4-thia-6-azabicyclo[5.1.0]oct-5-en-7-yl]-4-fluorophenyl]-5-chloropyridine-2-carboxamide Chemical compound C=1C=C(F)C([C@@]23N=C(SCC[C@@H]2C3)N)=CC=1NC(=O)C1=CC=C(Cl)C=N1 COCAUCFPFHUGAA-MGNBDDOMSA-N 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 239000002244 precipitate Substances 0.000 description 1
- 108090000623 proteins and genes Proteins 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 239000012925 reference material Substances 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/912—Applications of a database
- Y10S707/95—Financial
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/954—Relational
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/955—Object-oriented
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
Definitions
- the present invention relates to systems and methods to apply for processing accounts and, more particularly, to enable a merchant to apply for a credit card processing account using a small form factor computing device such as a handheld computer with modem, PDA with modem, or phone connecting to a server through a communications medium.
- a small form factor computing device such as a handheld computer with modem, PDA with modem, or phone connecting to a server through a communications medium.
- Merchants are located in many different places across the globe and the sales force that visits them covers a large territory. Organizing and tracking the collected merchant applications, distributing and reporting the data to the proper parties, and distributing the merchant number that signals the approval for services for card processing is a daunting task of data distribution and logistics management that spans across several organizations. Sales representatives are required to learn the complex process of completing a merchant application, which requires coordinating pricing models (which change very frequently), and discounts available along with a complete listing of hardware and software that the merchant can choose from to process cards at the store.
- the sales rep must also know the rules for making a decision about which combination of hardware is best suited for the merchant and which software is configured for that hardware. Often the merchant application is completed and approved only to be delayed by the delivery of the incorrect hardware and software for “card swiping” or credit entry. A delay in getting the right solution to the customer delays the realization of financial services organization revenue for transactions and merchant revenue for card use by the customer. Some sales reps, in an effort to avoid all the inconvenience of the process, have the merchant sign the application in blank, for later input into a laptop system. Relying on human memory leads to errors, or at best, makes the process of completing a merchant card processing application redundant.
- Typical methods for merchant card processing applications are solutions that automate and allow for electronic data capture for certain portions of the sale and merchant application process.
- Some sales representatives who visit a merchant location to collect data for the merchant's application use laptop solutions.
- a laptop solution, or a laptop with a handheld device that connects to it, eliminates the need for manual completion of paperwork associated with the process, yet requires sales representatives to carry a heavy laptop into a sales call with a merchant.
- These laptops are expensive and easily damaged or stolen and cumbersome to set up in a retail store where space is very valuable.
- the laptop solution is also lacking a mechanism for sales representatives to receive information about potential customers who have notified a bank of their interest in signing up for card processing services.
- the solution provided to a sales force is usually a piecemeal combination of hardware, software and connectivity that is not easily updated if and when frequent changes are implemented in a merchant application.
- completing a credit processing application using a laptop system is cumbersome for data entry and is obtrusive to the merchant.
- Connecting to a server for delivery of the data from the laptop is a complicated process of sign-on and requires constant connectivity to the database during the process. Sales reps and merchant are alienated as a result of the complex system of software and laptop to make the solution work.
- a merchant must purchase and install or must have available to them a computer with browser software and Internet connectivity. Then the merchant must install the hardware, software and connectivity and maintain the system.
- the present invention solves each of those problems and is a significant improvement over a laptop solution.
- a computer system for portable digital data capture and data distribution This system will manage the design and assembly of the complex components that make up the entire application process. This includes the logistics management of card processing hardware and software inventory, configuration for the merchant and delivery of the desired solution.
- a set of specialized programs that consist of interfaces, logic and edit checks on handheld computing devices or phones that enable a user to enter and view data, assignments, help text, answer choices, and other items and help the user calculate the needs of the customer based on input made in the interface.
- a set of specialized tools that enable a user to make changes to data and information that will be revealed to the user of the handheld device and to enable other users to distribute and view data collected with the devices.
- An example of this is the delivery of the merchant number, which designates the approval of the merchant's card processing account or the delivery of a request for additional information.
- the advantage of this is that it speeds time to revenues for both the financial service organization and the merchant.
- a mobile electronic merchant application is used to capture and distribute different data within the project. It may also be used to capture and distribute different data between projects. For example, within the project, one sales rep may serve the needs of the lodging merchants with all the associated questions, pricing models and hardware and software for “card swiping”, while another sales rep may serve the restaurant merchants with a different set of information required for them. Within the project, the two different sales reps would receive a different directory of data capture objects on their handheld device that will enable them to view and enter data without sorting through questions and screens that do not pertain to their work. In addition, different questions might be required across different sales forces and/or different financial service firms.
- the merchant application process requires the entry of a large number of data elements (questions). On average, there are 1,000-1,500 questions for data capture in a merchant application. Merchants and the sales rep must answer demographic information about the business and other business locations, and about the owners of the business. There are questions about bank references, credit references, expected sales and type of goods sold. There is legal information needed regarding bankruptcies, credit history and other businesses. Then there are questions about the services that the merchant will require for card processing, for example, is a PIN Pad for entry of a PIN needed, a barcode scanner for check reading, or does the merchant want VISA, MasterCard and AMEX.
- the screen On a handheld computing device or a phone, the screen is small and not easily visualized so that it would be necessary to present multiple questions on an individual screen without crowding the screen with information and making it difficult to visualize.
- the device does not have the computing capabilities of a laptop or desktop PC. It is therefore important to present the questions in a simple computing format so that complex calculations, logic that sorts through and presents screens, navigation and edit checks might be included in each of the questions.
- HTML pages in U.S. Pat. No. 6,135,349 requires that the HTML pages with answers input by the merchant be returned to the server and then returned to the device if the answers are not completely filled out. This would be similar with Wireless Markup Language (WML) pages or with the presentation of a form on a device. Waiting for a message that the page is not completely filled would take time and would require a constant connection to the server. The constant connectivity needed for pages and forms may be impossible with the short supply of bandwidth and with the drop off of connectivity in wireless networks.
- WML Wireless Markup Language
- the requirements for a mobile wireless merchant application system should include a store and forward architecture that enables objects to be delivered to the handheld computer and enables the user to work “offline” and then connect to the server to transmit data that has been collected and verified as accurate by the objects on the device.
- Being tethered to an Internet connection in order to perform work is not a mobile solution. Neither is a solution that requires the user to synchronize with the desktop or laptop. In comparison, this would be like a mobile phone that requires one to return to a desk station to connect and receive all calls. This is not a truly mobile solution.
- To utilize an Internet connection with HTML pages would limit the mobile capabilities of the device and limit the benefits for a mobile workforce.
- object-based architecture where each of the individual screens or questions is an object that is forwarded to the device for use while not connected, creates additional flexibility and mobility for the sales rep.
- architecture such as described above, there is one point of entry for the changes, which are forwarded to all users. Changes to the application, pricing, or product availability can be immediately forwarded to all users in the field, eliminating the need to return to a central location for updates.
- the lost objects can be immediately remotely forwarded to the device during a connection with the server.
- Information, as well as data capture objects can be forwarded. For example, the in-house sales group that has obtained sales leads can forward the merchant application that was started over the phone to the appropriate sales rep.
- a mobile wireless merchant card processing application system provides for the capture and distribution of an organization's mission critical data.
- An important requirement for this solution is to provide this functionality via wireless devices with no drop-off despite the narrow bandwidth available today.
- Bandwidth cannot be a primary concern with the need for large sets of answers and other information transmitted to and from the handheld device.
- Meticulous organization tracking and delivery of project subsets using a system such as disclosed in U.S. patent application Ser. No. 09/724,541 eliminates the need for a lot of bandwidth required during transmission of the objects with any standard operating system including Palm OS, Win CE and RIM.
- Telecommunications carriers use a host of network options for connectivity such as CDMA, CDPD, TDMA, GSM and 802.11 networks.
- a system will need to optimize the use of the spectrum by using both circuit switched and packet-switched data services.
- Store and forward technology in combination with the efficient use of bandwidth enables the user to enter data in the handheld device or phone without a constant connection to a wireless network.
- Data organized and communicated by a system such as disclosed in U.S. patent application Ser. No. 09/724,541 during transmission to make the most efficient use of bandwidth provides communications that are relatively short and tightly controlled. This flexibility gives users a choice regarding the best possible communications mechanism.
- the network, the carrier, the bandwidth should not be a concern and there should not be a problem with stopped data due to bandwidth limitations.
- Sensitive financial information is collected during data input by a sales rep and it is essential to maintain control with user ID and PIN so that information is available to only those with permission to view it.
- User ID and PIN is in addition to the security of the server that recognizes only devices approved for access. Encryption on the device and during transmission and transmissions of answers only (not questions with answers) is necessary so that interrupted transmissions are not read. When transmissions are interrupted, the system needs to prevent loss of data.
- the ability to collect the signature of the merchant is an essential part of the application. There may be additional functionality requirements among the different user groups/sales force that will need the ability to add new sets of objects that automate other aspects of the sales process, such as the presales encounter and sales encounter process, among others.
- Reporting also includes the ability to translate and distribute data returned to the project database into other databases and the ability to translate and return data from other databases to the project database to be forwarded as a subset of objects to a specific user's device.
- a computer system and method for processing mobile wireless merchant card service applications wherein the computer system has a storage device; first and second platforms; a merchant credit card processing project; a means to forward a project subset during synchronous reconciliation between the first and second platform; a means to translate data between the project subset and other storage devices; and a means to incorporate changes to the project subset and translate them to a form acceptable to the communication medium and/or first platform and update the project subset as a result, and then forward the changed project subset to the first platform.
- the present invention relates to a system and method to assemble a mobile wireless electronic merchant card processing application, which may use a computer system for portable digital data capture and distribution, such as disclosed in U.S. patent application Ser. No.
- the present invention is related to an object-oriented computerized data capture and data distribution system that is used to construct an electronic credit card processing application with specialty GUIs from a set of component objects and the like; forward subsets of data capture objects from a project database to a small mobile wireless handheld computing device or cellular phone for the purpose of capturing data and registering transactions; persistently save, recall, reconcile, share and distribute the project and information from other databases/tables; and forward additional object subsets to the device in response from input from those databases and in response to queries designed by the user by means of the objects on the device.
- This mobile wireless system for merchant card processing provides services that include: retrieving the merchant application project from the storage device; manipulating the merchant application project by adding, redefining and removing persistent objects; marking the merchant application project for forwarding to the first platform; persistently saving the project to the storage device, reconciling versions, and adding data to the project that has been reconciled with other storage devices; and marking the project for distribution on the Internet and to the first platform.
- the present invention includes the following steps in a mobile wireless merchant card service application process:
- FIG. 1 is a comparison diagram depicting the time spent and workflow of the conventional (prior art) process for a merchant card processing application system vs. a system in accordance with one preferred embodiment of the present invention.
- FIG. 2 is a diagram depicting the flow of the steps of the present invention showing data flowing through the translator in the project database between the salesperson or merchant and the Bank or financial services institution.
- FIG. 3 is a diagram representing the process workflow using one preferred embodiment of the present invention.
- FIG. 4 is a more detailed block diagram of the present invention that shows elements included of the EDC system for merchant card processing applications as it relates to the components of the framework and the kernel.
- FIG. 5 is a network architecture diagram for one preferred embodiment of the invention wherein handheld computers connect through a communication network to the project database
- FIG. 6 is an entity relationship diagram illustrating the tables and relationships in the project database that manage the design and assembly of the objects used in the project database in accordance with the present invention.
- FIG. 7 is an entity relationship diagram illustrating the tables and relationships in the project database that manage the logistics of delivery of objects and data to the devices of specific users in accordance with the present invention.
- FIG. 8 is a detailed data level flowchart showing the movement of data and objects between the project subset.
- FIG. 9 is a block diagram illustrating the cycle of information flow from the translator, to the project subset to the hardware and back to the project subset for delivery through the translator.
- FIG. 10 is a data flow diagram illustrating the movement of data through the translator to other databases.
- FIG. 11 is a set of screen shots that are the interface for data entry on a handheld computer or cellular phone.
- FIG. 12 is a screen shot of the portal interface where a user may access the reports from a desktop based on data collected by the handheld computer.
- FIG. 13 is a sample report screen for the portal of FIG. 12 .
- a mobile wireless system and method to collect and process merchant card processing applications is provided that would enable a merchant to apply for a credit card processing account using a small portable computer such as a PDA with a modem or phone.
- This system and method includes a wire line or cellular network communication link between the portable computer and a server.
- On the PDA or phone resides a subset of data capture objects that has been forwarded from a project database residing on the server.
- This set of objects form an interactive software application on the device which prompts the user to input data into a set of Graphical User Interfaces.
- the PDA with modem or phone device connects to the server where the project database resides, through a cellular or wire line connection, and is recognized by the server, which then delivers the captured data into tables in the project database.
- the project database on the server distributes data to other servers that process the credit card processing account information to determine whether to grant the merchant a credit card processing account. Information about approval is distributed through the same mechanism back to the PDA, or phone, to be revealed in the application on the PDA or phone of the person who has requested the information.
- One of the novel concepts of the present invention is to use a portable digital data capture and distribution system and related project database, such as disclosed in U.S. patent application Ser. No. 09/724,541, to assemble and manage the delivery of a specific set of data capture objects that are specifically designed and used to capture merchant card processing application data.
- the project database contains data capture objects specific to the task of automating the collecting and distribution of merchant application data between multiple databases.
- the project database includes a plurality of project subsets. Each specific group of users or individual users gets a project subset forwarded from the project database.
- the present invention includes the delivery in the project database of data translated from one or more databases outside the project database after a procedure of translation.
- the object oriented nature of the smallest data element or individual field and the table structure to designate the characteristics and functionality of the elements enable expansion and scalability to add additional functionality without the need to completely redesign of the entire system. For example, encryption o hardware may be added, or the distribution of data may be extended to multiple databases without the need for any system redesign.
- Another important feature of the present invention is the use of answer tables containing incomplete records as part of the project subset. These incomplete records in relationship to the data capture objects are forwarded to the handheld device to give the user specific information and enable the user to respond with answers to questions within the record.
- the conventional method of data capture and distribution for merchant card application processing has consisted of using a web browser or a form loaded onto a device from a desktop cradle for view or data entry into a database. This requires that a device gain access to the corporate database or a mirrored database as a window into the database.
- problems with this method that make it very difficult for an end user with a small mobile computing device to access the data that pertains only to them and to view it or make changes to the content in an efficient, user friendly manner.
- the preferred object-based embodiment of the present invention is a considerable improvement on current methods of electronic data capture.
- Objects are suited for a small computing format and screen and are easily processed by a small computing device. Instead of a form on the device, there is a program that allows the sales rep to custom-build his or her own forms and queries for the database only within the confines of the project. This eliminates searching through the entire database and provides protection for the rest of the data in the database.
- the objects in the program used in the present invention organize the individual fields into a table on the small computing device and set them in motion by determining or selecting configurations and complex characteristics marked in tables in an application server, and coordinating their reference to other tables.
- the preferred embodiment of the present invention has baked in the best experience of how the questions for the sales encounter and the equipment calculator can be most easily answered.
- the question and answer format creates a query that the translator carries to other databases to then find and transport information back into the project. The translator forwards the retrieved information into any type of mobile computing device. Accordingly, a sales rep is not simply getting access to look around inside a huge mirrored database which is a process that takes time and requires a continuous connection.
- the conventional methods of data capture and distribution thus present a security risk and are not efficient.
- the present invention automates the entire process of merchant application processing.
- the mobile workers who interact with the merchants use devices which are easy to carry and use, do not require continuous connectivity to the server, can be managed and loaded with all appropriate data capture objects remotely, allow for two-way synchronization, and include objects that enable the calculation of software and hardware needs of the merchant for “in store” electronic card processing.
- Another embodiment of the present invention is to use the systems and devices described in U.S. Pat. No. 6,298,347 in combination with the components discussed in this document.
- One preferred embodiment of the present invention uses the system and methods in U.S. application Ser. No. 09/724,541.
- Another embodiment of the present invention uses the system and methods in U.S. Pat. No. 6,298,347. This would provide a less dynamic system of automation than the preferred embodiment, but would still be a significant improvement over the scheme disclosed in U.S. Pat. No. 6,135,349.
- FIG. 1 illustrates the workflow for the prior art 18 in comparison to the workflow for the preferred embodiment of the invention 17 .
- the diagram is depicted in a circular manner in order to represent the time element involved in the process with prior art 18 vs. the preferred embodiment of the invention 17 .
- the prior art 18 requires the use of several different types of individuals 1 , 3 , 5 , and 12 interacting with different sets of paperwork/phone/and electronic data entry 2 , 4 and 6 shown with arrows connecting them in the direction of information flow. These sets are entered or retrieved from a number of different databases depicted in FIG. 1 as DB 7 , DB 9 , and DB 11 .
- U.S. Pat. No. 6,135,349 merely delivers an electronic means to collect the merchant materials 2 and to submit these to DB 7 by means of the Internet. Although this has offered a valuable service for eliminating the need for completing paper forms and then performing data entry using those forms, it has done little to eliminate the errors and inconvenience associated with data entry from a desktop with a browser and it has only eased the burden of data entry into one database as seen in FIG. 2 of U.S. Pat. No. 6,135,349. This is because the prior art uses pages exchanged with a server over the Internet and is not object-based and thus not capable of interactive functionality that objects are capable of.
- the prior art process has also done little to automate the rest of the complex logistics and data entry requirements needed to deliver the necessary data to a number of disparate databases in order to get approval for, and the right equipment to, the merchant 12 , thereby giving them the means to process sales from customers using credit and bank cards.
- the prior art does not automate the management of the sales force (track and deliver assignments, produce new electronic forms as needed) on both a web-browser and a mobile computing device.
- the prior art has only decreased the time involved in some of the steps and the movement of data between the different parts of the process rather than consider the process, as a whole to eliminate steps in the process and speed up the entire process.
- the prior art does not allow or enable the automatic aggregation of collected data into reports.
- the preferred embodiment of the present invention 17 offers a solution to automate all the steps involved in a merchant card processing application and approval process, and to directly collect and exchange data using a mobile wireless computing device shown in FIG. 1 as a handheld with a project subset 116 between groups of individuals, shown in FIG. 1 as sales representatives 1 and the merchant 12 , although this information can be exchanged with a number of different groups of individuals.
- the present invention is an improvement on the data collection component in that it simplifies and speeds the flow of data between a mobile computing device, such as a handheld hardware 34 , through the framework 56 , to a project database 60 and enables the data to be changed into multiple formats for forwarding between multiple databases, DB 8 and DB 10 by means of the translator 15 .
- FIG. 2 shows a more detailed diagram of the automation of data flow in the present invention.
- a handheld computing device is forwarded a project subset 116 which consists of a specific set of project schema 100 , assembled and managed by the system in U.S. patent application Ser. No. 09/724,541, from a component of the present invention called a project database 60 .
- the user can collect basic merchant information, order the hardware and software needed for the merchant to process credit and bankcards, as well as receive a merchant account number designating approval from the bank 17 .
- This project subset 116 is not limited to this functionality. The user can even receive a message that additional information is required from the merchant in order to give approval.
- the data collected 13 is transmitted from the objects in the project subset 116 across a communications network into the project database 60 based on configurations set for the Merchant Application EDC System 58 within the CDCDS 70 .
- the translator will organize the collected data 13 in a format that is readable by the DB 10 and DB 8 of the bank/FS institution 17 and forward the data to these databases.
- the forwarded data acts as a query sent by the translator 15 which requests the return of data to the translator 15 where it is formatted within the object schema 100 for forwarding to the project subset 116 .
- the project subset 116 will contain the merchant number 14 , or a message “approval is not available yet”, or “more information needed”.
- FIG. 3 is a diagrammatic representation of the workflow and responsibilities of the CDCDS 70 in U.S. patent application Ser. No. 09/724,541 with regard to the Merchant Application EDC System 58 .
- the Merchant Application EDC System 58 is the Portable Digital Data Capture and Data Distribution Project 58 of the CDCDS 70 in FIG. 2 of U.S. patent application Ser. No. 09/724,541.
- the Merchant Application EDC System 58 allows managers 22 , merchant 12 , sales representative 1 , and others 86 to use a device 52 capable of measuring and inputting data, and sharing and accessing the Merchant Application EDC System 58 through a customizable interaction 54 that is part of the framework 56 of the CDCDS 70 .
- a customizable interaction 54 that is part of the framework 56 of the CDCDS 70 .
- the framework 56 performs project design logic, passes messages between project components and/or individuals, manages project interactions, reconciles project versions, forwards project changes, tracks and organizes project logistics. In essence, the framework 56 automates certain tasks in order to free users to perform higher level tasks, remove redundancies and errors from the system, reduce time and costs, and produce better quality information.
- a CDCDS 70 of FIG. 2 of U.S. application Ser. No. 09/724,541 many of the tasks and requisite staff in the prior art system 10 of data capture and data/report distribution (shown in FIG. 1 of U.S. application Ser. No. 09/724,541) are absent. With the CDCDS 70 , shown in FIG. 2 of U.S. application Ser. No.
- the CDCDS 70 shown in FIG. 2 of U.S. application Ser. No. 09/724,541 eliminates the ongoing need for skilled programmers 32 to develop, update, modify and track version control of the data entry interface 44 , logistics report interface 48 , and report interface 50 of FIG. 1 .
- a CDCDS 70 user that has minimal technical training can access the framework 56 to access the object schema store 62 in the project database 60 .
- Eliminated are some managers 22 performing logic 24 about managerial functions, modification report request 80 , redo of project report request 76 , and delivery of reports loop 74 , that routinely recur related to programmers 32 , along with attendant couriers 30 and data entry 42 as seen in FIG. 1 of U.S. application Ser. No. 09/724,541.
- the CDCDS 70 in FIG. 2 of U.S. application Ser. No. 09/724,541 eliminates the need for numerous managers 22 that perform logic 24 in the sub-process of logistics 14 , quality assurance logic 24 QA, in the sub-process of data collection 16 , and form design logic 24 FD, in the sub-process of design/development 12 of the system 10 of data capture and data/report distribution of FIG. 1 of U.S. application Ser. No. 09/724,541.
- Managerial functions such as the design/development redo loop 82 , and redo of an assignment request 84 of FIG. 1 of U.S. application Ser. No. 09/724,541 are eliminated along with the attendant couriers 30 , printer admin 38 and field workers 36 involved. As shown in FIG. 2, of U.S.
- the framework 56 of a CDCDS 70 is set to perform these tasks automatically and eliminate the trivial and repetitive work (see FIG. 1 of U.S. application Ser. No. 09/724,541) of logic 24 , quality assurance logic 24 QA and form design logic 24 FD.
- This automation occurs as a result of the CDCDS 70 user integrating specific items in object schema store 62 already available in the project database 60 to be forwarded as part of a project subset 116 to field workers 36 and others.
- managers 22 are able to design a project, request all report parameters at the time of project design, view various reports on input from field workers 36 , and connect with a main database 20 to verify data against input from the field.
- the CDCDS 70 gives users the scalability to ramp up or ramp down a project as well as add new projects without the geometric increase in work.
- a CDCDS 70 is shown having an architecture of layers that include a portable digital data capture and data/report distribution project 58 consisting of object schema store 62 of a project database 60 , a dynamic framework 56 , and a kernel 92 connected to the underlying platform 94 . These layers are each made with different tools and are meant to perform different functions. It is the architecture that allows the portability and the flexibility to expand, add functionality, and add increasing automation to the CDCDS 70 .
- the kernel 92 provides the services necessary to load/execute the higher levels and to provide an interface to the system-dependent services of the underlying platform 94 which consists of the operating system 96 and the hardware 34 .
- the hardware 34 has memory such as RAM in which the kernel 92 , the framework 56 and a portion of the portable digital data capture and data/report distribution project 58 reside at run-time.
- There is at least one storage device such as a hard drive in which the portable digital data capture and data/report distribution project 58 is stored.
- the kernel 92 is written in C++ (although not limited to C++), which is a well-known programming language that is compiled using vendor tools that are appropriate to that platform 94 , thus platform specific for each of several platforms.
- the kernel 92 uses a function call-based programmer interface (“API”), the kernel 92 performs services for the higher levels.
- the API's native code functions are accessed via direct calls from the framework 56 .
- the kernel 92 is not portable but can be extended by loading additional modules with associated DSL files.
- FIG. 3 illustrates several components to the CDCDS 70 that are in addition to the components of the invention discussed in U.S. application Ser. No. 09/724,541.
- a specialized set of answer tables 64 in the project database 60 connected to a translator 15 that move data to and from external databases DB 8 and DB 10 by means of a specialized stored procedure 65 .
- the combination of the translator 15 in connection with the answer tables 64 as part of the CDCDS 70 enables the delivery of partially completed field input form 219 , which unlike the HTML pages of U.S. Pat. No. 6,135,349, can be presented to the user as content with the ability to edit the content as well as view the content.
- the advantage of this methodology is that the user, such as the sales representative 1 , can directly update the content with the most recent information available with the merchant 12 data. All users that access the system from other points will have access to this information as allowed by the CDCDS 70 . In prior art schemes, the user would be able to view the content but would be required to complete other or additional forms to update the content, often slowing the process of information flow. To eliminate the potential for unwanted information flowing into the system, the Merchant Application EDC System 58 is configured with Object schema store 62 that will have only the functionality allowed by the Merchant Application EDC System 58 .
- a specific object schema store 62 might include objects in the project database 60 that enable users to view data only and not edit data.
- There can be specialized data capture objects such as a signature capture objects and hardware/software calculator objects that are included in the libraries of data capture objects available in the project database 60 .
- These specialized objects are specific to use in a project such as the Merchant Application EDC system 58 in FIG. 2 .
- this project database 60 of FIG. 1 is connected through a translator 15 , which is commanded to manage the distribution and receipt of data to, and the translation of the data between, more than one databases.
- the translator 15 connects with DB 8 and DB 10 , which represent databases at the financial service institutions and banks that warehouse credit information and transaction information with regard to the merchant 12 .
- the kernel 92 consists of the support libraries 98 that are necessary for the CDCDS programs. These include libraries for file and resource I/O, configuration management, memory management and diagnostics. These support libraries can be changed when the platform of choice for the project is changed.
- the kernel 92 manages part of the transport of objects when connections are made to the field.
- the framework 56 provides the visual interfaces between the CDCDS and the CDCDS users.
- the framework 56 consists of the Internet portal 186 , project creator/report generator 108 , report forms 118 , logistics manager 110 , system messages 122 , and the project subset that includes the transport mechanism 104 , field input interface 112 , and field input forms 120 along with other subsystems. In the preferred embodiment of the present invention this is also true and in addition, the framework 56 includes the translator 15 . As described in U.S. application Ser. No. 09/724,541, the framework 56 provides access and incorporates the necessary CDCDS logic to the project and to the project subset 116 forwarded to the hardware 34 .
- the project subset 116 is designated as a specific field input interface 112 referenced to the project schema 100 of the portable digital data capture and data/report distribution project 58 .
- This project subset 116 is named by the CDCDS user to be forwarded by the transport mechanism 104 to a specific hardware 34 .
- the framework 56 is written in C, C++, Visual Basic, and HTML (although it need not be limited to these languages) for maintainability and extensibility, although Java and XML could be implemented at any time.
- the framework 56 is not necessarily portable and may perform differently on different platforms 94 .
- the project schema 100 relate to the appropriate Project Answer Tables 101 within the Merchant Application EDC System 58 , which is specific to the present invention, whereas U.S. application Ser. No. 09/724,541 discusses other types of Portable Digital Data Capture Report Distribution Projects.
- FIG. 6 and FIG. 7 illustrate the relationships of the answer tables 101 and the project schema 100 within the project database 60 .
- the Appendix is the “code” (configuration of data elements) of the project database 60 which is required for the Merchant Application EDC System 58 project schema 100 .
- the preferred embodiment of the present invention includes the project subset 116 where the framework 56 queries to access the current state of the project.
- the project subset references the project schema 100 , which references the project answer table 101 that is part of the Merchant Application EDC System 58 , which is a type of portable digital data capture and data distribution project that requires a specific combination of objects related to the financial services domain.
- the advantage of having project answer tables 101 is that it enables the forwarding of specific data within the field input interface 112 of the project subset 116 .
- the preferred embodiment of the present invention includes the functionality shown in FIG. 5 of U.S. application Ser. No.
- Report forms 118 and field-input forms 120 are employed as the interface between the user and the CDCDS 70 .
- Field-input forms 120 and report forms 118 are implemented using the services of the API of the kernel 92 and are notified when an event occurs either as a result of input or as a result of other program events.
- Report forms 118 receive input from CDCDS users during the initial design or when changes are made to a CDCDS portable digital data capture and data/report distribution project 58 and changes are available immediately throughout the project.
- Logic has been programmed into the project creator/report generator 108 to remove the burden of logic from human users.
- the project creator/report generator 108 returns system messages 122 to the user such as a reminder that a particular object is unable to be integrated into a project without including the object's functions, as well as supplying other system messages 122 .
- the process of creating or manipulating objects in a project requires a series of actions that precipitate visual feedback, confirmation and qualification of inputs. Therefore the “state information” must be maintained while a user is making changes to the project.
- the project creator/report generator 108 controls the process of manipulating the portable digital data capture and data/report distribution project 58 by a set of queries (not shown).
- the project creator/report generator 108 has an expected set of inputs, which bring about predictable results.
- the CDCDS 70 allows users with specific permissions to mark and integrate the functions of objects that are part of the field input forms 120 to respond in a particular ordered fashion in the portable digital data capture and data/report distribution project 58 . It is because of this that the CDCDS 70 of the present embodiment allows the user access through the project creator/report generator 108 .
- the project creator/report generator 108 exhibits a system message 122 to the CDCDS user that input has been accepted, or why it has not been accepted and then reveals the result of the input. If the CDCDS user is not satisfied with the result of the input, then, the CDCDS user is able to make additional input to change the results.
- the portable digital data capture and data/report distribution project 58 consists of one or more project schemas 100 , or any other domain specific schemas.
- FIG. 6 of U.S. application Ser. No. 09/724,541 shows that in the preferred embodiment of the present invention, a project schema 100 consists of a set of project objects 114 that are relevant to a particular project or to a particular discipline existing in an object schema store 62 . Multiple objects 114 integrated into multiple project schemas 100 as part of the object schema store 62 can be combined to form a portable digital data capture and data/report distribution project 58 as shown in FIG. 4 of U.S. application Ser. No. 09/724,541.
- FIG. 6 of U.S. application Ser. No. 09/724,541 shows that in the preferred embodiment of the present invention, a project schema 100 consists of a set of project objects 114 that are relevant to a particular project or to a particular discipline existing in an object schema store 62 . Multiple objects 114 integrated into multiple project schemas 100 as part of the object
- the addition of answer tables 101 with the project schema enable the translator 15 with query parameters when sending and retrieving data from the external databases. This greatly simplifies and speeds a query process in that the answer table 101 is recognized as belonging to a particular user with a particular project subset 116 .
- the query response can therefore be returned to that particular project subset 116 and thus returned to the user field input interface 112 during the next connection through the framework 56 . Then, the user can enter additional data that will define the query further.
- FIG. 5 is a high level schematic diagram of a network configuration showing components of hardware 34 , telecommunications network 35 and firewall software 36 that are suitable for use in the preferred embodiment of the present invention.
- a key factor of the present invention is its object-oriented nature in every aspect of the invention, enabling the easy insertion or deletion of combinations of hardware 34 , software 36 and networks 35 that will offer the best possible benefits. For example, as the telecommunications networks expand to the use of 3G or if a customer requires a local wireless network to accommodate requirements outside the project such as the need to connect users within a setting where 3G service coverage is sporadic.
- FIGS. 6 and 7 are entity relationship diagrams showing all the tables 400 with their structures and attributes, as they are part of the object schema store 62 in the project database 60 shown in FIG. 3 .
- These tables 400 show the characteristics and parameters of all the objects that are available for integrating into the project schema 100 of FIG. 4 .
- the relationships shown in this diagram are a configuration of the present invention that enables a user to access the Merchant Application EDC system 58 by opening the project creator 108 in the framework 56 so that the user can choose items in these tables 400 to be part of a specific project schema 100 .
- the relationships in these tables will automatically manage the relationships of the items in the project schema 100 . It is here that the definitions and configurations are set for each of the project subset 116 with their attendant field input interface 112 shown in FIG. 4 .
- logistics management is the organization, tracking and delivery of the correct information to the correct people, accurately, and on time.
- the user names the owner 300 and the surveys 220 , the groups 394 , and all the characteristics of each of the items in the related tables 400 . This is similar to the way that logistics are managed in U.S. application Ser. No. 09/724,541 where the relationships are described in more detail below.
- Section a of FIG. 7A in U.S. application Ser. No. 09/724,541 shows that owner 300 consists of a unique ownerID 402 (an automatically assigned number) and a name 404 (a short text description that signifies the CDCDS user or group 394 of users).
- Section a also includes the related survey 220 which consists of the SurveyID 284 , OwnerID 402 , a name 324 (a short text description that describes the set of field input forms 120 ), type 286 (either a FormDB 208 or a fixed 214 ), title 362 (a short text as it appears on the field input interface 112 on the hardware), howtosync 288 (signifies the way the data from this survey 220 is transported between the field and the server), nextsurvey 290 (signifies and identifies the survey 220 that is to follow this one), questionstocopy 294 (signifies all the field input form 120 marked key 322 whose input should be copied to the next instance of this survey 220 ), reservedone 370 (signifies the score group of the report that this survey 220 is part of), reserved two 372 (signifies the report group this survey 220 is part of for aggregation) in a not enforced, One-To-Many relationship.
- a name 324 a short text description that describes the set of
- Section b of FIG. 7A in U.S. application Ser. No. 09/724,541 has owner 300 (same as in section a) related to groups 394 , which consists of ownerID 402 , name 406 (a short text description that signifies the set of users that will be performing the specific type of data collection for an owner 300 ), groupID 420 , and directoryID 410 in a not enforced, One-To-Many relationship.
- Section c of FIG. 7A in U.S. application Ser. No. 09/724,541 has surveys 220 (same as in section a) related to directory entries 396 which consist of directoryID 410 (an automatically assigned number) and surveyID 284 in an enforced, One-To-Many relationship.
- Section d of FIG. 7A in U.S. application Ser. No. 09/724,541 has surveys 220 (same as in section a) related to survey questions (known as field input forms 120 ) which consists of surveyID 284 , FieldID 320 (a unique number assigned by the CDCDS user), Key 322 (set by the CDCDS user to designate status of the field), fieldname 356 (short text description of an individual field input form 120 that are referenced by other projects to aggregate normative information-unique for each field input form 120 that is part of a survey 220 but not unique across surveys 220 ), type 326 (signifies the nature of the field-input forms 120 referring to an example of a field types 114 A supported), length 328 (denotes the number of character length for a text field-input form 120 ), format 330 (nature of field-input forms 120 that uses specific parameters) help 332 (denotes a section of the field-input form 120 that describes in some detail reference material shown on the screen for the field
- Section e of FIG. 7B in U.S. application Ser. No. 09/724,541 has group 394 (as seen in section b) related to group membership 392 which consists of groupID 420 (as seen in section b) and a unique userID 412 (an assigned number that signifies a particular hardware) in a not enforced, One-To-Many relationship.
- Section f of FIG. 7B in U.S. application Ser. No. 09/724,541 has directories 218 which consist of a directoryID 410 (as seen in section b) and a unique joinID 416 (an assigned number that signifies a connection between two items). This is related to group 394 (as seen in section b) in a not enforced, One-To-Many relationship.
- Section g of FIG. 7B in U.S. application Ser. No. 09/724,541 has directories 218 (as seen in section f) and directory entries 396 , which consists of directoryID 410 and surveyID 284 in an enforced, One-To-Many relationship.
- Section h of FIG. 7B in U.S. application Ser. No. 09/724,541 has join entries 308 which consists of JoinID 416 (as seen in section f), survey 1 ID 284 b (signifies the first survey 220 that will be connected to the second survey 220 ), field 1 ID 320 b (signifies the connection point of the second survey 220 ), survey 2 ID 284 a (signifies the second survey 220 that is connected), field 2 ID 320 a (signifies the connection point of the second survey 220 ) related to directories 218 in an indeterminate relationship.
- Section i of FIG. 7B in U.S. application Ser. No. 09/724,541 has mobile users 390 which consists of a userID 412 (as seen in section e) hardware name 428 (signifies the nature of a hardware 34 that will be connecting through the framework 56 into the project database 60 ), last name 422 (the surname of the field worker 36 that will be using this hardware 34 ), first name 424 (the field worker 36 first name), initials 426 of the field worker 36 ) related to group membership 392 (as seen in section e) in an enforced, One-To-Many relationship.
- a userID 412 as seen in section e
- hardware name 428 signalsifies the nature of a hardware 34 that will be connecting through the framework 56 into the project database 60
- last name 422 the surname of the field worker 36 that will be using this hardware 34
- first name 424 the field worker 36 first name
- initials 426 of the field worker 36 related to group membership 392 (as seen in section e) in an enforced
- the answer table 101 is part of the directory entries table 396 , which has a relationship to the table survey 220 , survey questions 120 , and the distribution table 601 of the translator 15 .
- the value 358 of each of the records in the table can be treated as an object that by relationship can be given a defined translation value 359 for a new field 600 within a table N 601 of any other database.
- FIG. 8 is a block diagram depicting a particular combination of configured elements in the tables of FIG. 6 and FIG. 7 that will combine as a particular project subset 116 A.
- the translator 15 with a configured relationship marked in Table N 601 will use a stored procedure to retrieve or send data between DB 8 and DB 9 and the input 310 and project answer tables 101 that are part of a particular project subset 116 A.
- the particular combination of joins 216 , survey 220 , field input forms 120 as part of the directory 218 of a group 394 will enable the delivery of the project subset 116 A by means of a directory query along with the delivery of partially completed forms.
- FIG. 14 of U.S. application Ser. No. 09/724,541 is a flow diagram showing the project subset 116 that is forwarded during connection with the hardware A 34 .
- the CDCDS user designates the initial project design by signifying items in the groups 394 table (for logistics management) and designates items included in the directory 218 (information of what project schema 100 is included).
- the user will designate in the directory 218 details on the survey 220 (field input forms 120 not shown), the creation of the input tables 310 and choice tables 312 , and the joins 216 (if included in the project). These designations made in the tables will be forwarded to the hardware A 34 by a query of the directory in the project subset A 116 .
- a field worker 36 with a particular mobile user designation of a last name 422 and hardware name 428 (not shown) will connect to the project database 60 with certain hardware 34 .
- the field worker 36 with this hardware 34 during the connection will be recognized by what group membership 392 is associated with this hardware 34 making it possible for the hardware 34 to be forwarded the appropriate project subset 116 of this field worker 36 .
- This is performed using ODBC with the transport mechanism 104 (see FIG. 4 of U.S. application Ser. No. 09/724,541), and based on the designations group membership 392 and mobile user 390 (see FIG. 7A of U.S. application Ser. No. 09/724,541) related to owner 300 in a group 394 , the appropriate project subset 116 is forwarded to the field worker 36 .
- any manipulation of the project is reconciled between versions of the project.
- the hardware A 34 will have initiated the transport protocol 540 at which time the very specific directory 218 for this hardware A 34 will be available for a long-term transaction, disconnected from the project database 60 .
- This allows the system of a queried directory available on the hardware 34 for the purpose of a long-term transaction since staying connected to the project database 60 may not be feasible with current hardware and data communication services.
- reconciliation occurs between the project database 60 and the project subset 116 regardless of the hardware 34 or how a user has changed the specifics of the project subset 116 .
- the field-input interface 112 is what appears on the hardware 34 . Data is entered into the field-input forms 120 and then the transport protocol 540 is initiated.
- the field-input interface 112 is designed to reveal one field-input form 120 per screen with a limited but adequate number of input choices on that same screen.
- the field worker 36 makes the input into the field-input form 120
- the data is temporarily stored and a new field-input form 120 appears on the screen. If necessary, the logic is already programmed into the field input interface 112 so there is no chance of omitting a response or inputting a frivolous response.
- the data is ready to be returned to the project database 60 through whatever transport mechanism 104 needed.
- FIG. 15 of U.S. application Ser. No. 09/724,541 is a block diagram providing more detail on the present invention as it forwards a project subset 116 from the project database 60 for transport to the specific hardware 34 of the field worker 36 .
- This illustration shows the CDCDS user has designated the forwarding of a project subset 116 as the CDCDS user programmed it. Should the CDCDS user program the project subset 116 and its items differently, then the project would behave differently.
- An average project subset 116 consists of one or more schema 100 .
- FIG. 8C and FIG. 8D of U.S. application Ser. No. 09/724,541 were examples of different project schema 100 .
- a project schema 100 is built with the programming language 124 as shown in FIG. 8A of U.S.
- a project schema 100 also includes at least one survey 220 with all survey characteristics 520 designated and this survey 220 is related to an instance 532 of field input forms 120 with all of their characteristics designated.
- the project schema 100 includes at least one accompanying input table 310 .
- the project schema 100 may or may not include joins 216 , which will need one or more accompanying, join entries 308 and one or more choice tables 312 as seen in the illustration of a project schema 100 with a joinID 416 in FIG. 8D of U.S. application Ser. No. 09/724,541.
- the object-oriented nature of the field input forms 120 enable the schema to be launched for the purpose of edit and view 217 or the schema is launched to input data in the field input form 120 .
- This structure enables the user to define a type of query 219 that will be exchanged with the project database 60 during transport. This query will be forwarded through the translator 15 and return additional data to the project subset 116 A for return to the user either in the form of an approved merchant number or additional request for information. This is unlike U.S. Pat. No. 6,135,349 where the information is not automatically returned when the HTML page is completed. In the prior art, a user must make an additional request for that information, or after human intervention, the information will be forwarded to the user.
- FIG. 9 of the present invention depicts the project subset 116 in several different configurations of surveys 220 and tables 310 , 312 , 101 that will enable different users to receive very specific applications and forms that relate to the work of each of the individual users.
- the project subset 116 forwarded by means of the transport mechanism 104 assembles as an electronic form of the sections of a merchant credit card processing application.
- the electronic form is an interactive field input interface 112 on the handheld hardware 34 .
- This interactive application guides the user through a set of input forms 120 only presenting the appropriate input form 120 based on input in a previous one. This removes a tremendous amount of error in data entry and reduces the time of data entry.
- U.S. Pat. No. 6,135,349 the user must review all data entry fields shown in FIGS. 3-6 of this patent and make a decision about what requires input, or receive a message after the page has been delivered to the Internet server and returned with a message that the entry was not complete.
- This electronic application may consist of several components such as an interface for the collection of “presales/sales encounter” data, an equipment calculator that enables the user to enter information about the merchant's equipment needs into the device and then receive an automatic estimation of the correct hardware and software choices for the merchant, and merchant information needed by the financial institution to make a decision about account approval.
- Other components may be easily added to accommodate the needs of the sales force or the bank.
- These components of the electronic application must also provide the user with the ability to navigate through the components or sections of the components, or through individual screens so that the electronic application does not hinder the process of merchant sign up.
- the handheld component must have the capabilities to provide GUIs with “touch screen” or “one button push” data entry.
- the nature of the Financial Services and credit card industry is that security of data and transactions are vital to the safety of commerce using the Internet or wireless communications.
- the encryption that is added to the first and second platform aids in the security of data and information flow.
- there is an additional type of security in that the delivery of project subsets 116 and the automatic management of the data through the mechanism of the table relationships eliminates the need for users to gain access to the database for retrieval of content information. Instead, only the relevant content is delivered to the user as part of the project subset 116 marked for that user.
- FIG. 10 illustrates the movement of data from the hardware 34 through the translator 15 to the external database 8 and 10 .
- a mobile computing platform such as a PDA or a mobile phone
- a program must reside in the middle between the hardware and the database that will enable a connection and enable the transfer of data. This is not an unusual concept, but is often referred to as middleware.
- middleware One important feature of the present invention is not to use middleware to push the database information onto the mobile computing platform or to not offer the middleware as a window into the database to review content.
- the present invention uses the middleware type program to translate the information between databases by a means of marking the data in tables to relate to other data in such a way as to deliver it into specific project subsets 116 that will then carry the data to the mobile computing hardware.
- biogenetics gene fragments are connected in a very particular structure that is the result of a reconfigured combination that enable a skin cell to map its characteristics to a reproduced skin cell. This occurs in a complex transfer process between the strands of DNA within the cells.
- answers are mapped for distribution to a particular database outside the Merchant Application EDC System 58 by means of the configuration of the data elements set by the CDCDS 70 at the design of the project.
- the program that resides in the CDCDS 70 builds a connection to the customer server to get a specific set of data, yet not have access to all data.
- the launch of the program can be set in particular time intervals or can synchronize at any time.
- Data is retrieved into a distribution database 601 with a value 359 and a new field name 600 that is configured in relationship to the answer table 101 where the data is now translated into a value 358 with a field name 356 that is known by the project database 60 (see FIGS. 6 and 7 ) that will forward it in a manner acceptable to the hardware 34 .
- Conversions such as these can be simple or complex, can include multiple translations and will be set for automatic translation in the Merchant Application EDC System 58 .
- FIG. 11 is a screen shot of the first screen of the web interface Internet Portal 186 where a user given a set of permissions within the Merchant Application EDC System 58 can access the project database 60 to view report information, manage assignment logistics, and change list choices in the choice table 312 of the project subset.
- This interface gives users a chance to look into the palm of the sales representative 1 in order to manage the pipeline of customer hardware needs and service needs, which was not readily available prior to the present invention.
- the Sales representative 1 would start out at the office where they picked up merchant materials 2 , consisting of leads that the telesales group had for them, copies of the blank applications, updated pricing models, hardware and software in inventory, requests from the banking institution for additional information from the merchant, requests from corporate headquarters for corrections on previously submitted applications, and information on merchant approval, which the sales rep will communicate with the merchant.
- Sales representative 1 who are new to the merchant materials 2 often have a difficult time getting familiarized with all the materials, while those with experience know how to complete the work in a more efficient manner.
- the sales rep 2 complete all the merchant materials 2 , they return to the office to key in data collected into the corporate database 7 , or they key it in on their laptop, which connects to the corporate database 7 .
- All of this data is forwarded to the processing database 8 by the data processing staff 3 .
- the data processing staff must forward the data to the inventory/solution delivery database 9 , which generates warehouse-shipping materials 4 .
- the data processing staff 3 will return all data that is incorrect or incomplete as rejected merchant materials 2 , which will require completion by the sales representative 1 .
- data is forwarded to the Banking database 10 , where the bank processors 5 review the data. If all information was complete, and the merchant was approved for card processing, the Bank processors 5 forward the information to the approval database 11 , where the approved merchant materials 6 are produced and sent to the Merchant 12 .
- ACME FS decided to implement the preferred embodiment of the present invention 17 depicted in FIG. 1 .
- a portable digital data capture and data distribution system described in U.S. application Ser. No. 09/724,541 was used to design and assemble an EDC System for a Merchant Credit Card Processing Application 58 as shown in FIG. 3 of the present invention.
- the sales representative 1 was given a piece of hardware with a project subset 116 with a subset of objects that formed an interface for entry into a Merchant Application schema, Sales Encounter, and Equipment calculator Schema 62 shown in FIG. 3 .
- These schemas 62 were forwarded from the project database 60 to the device to be revealed to the user as field input interfaces 112 shown in FIG. 4 .
- the sales representative 1 would view these as screen shots depicted in FIG. 11 .
- the main menu 40 screens depict the first screen of the electronic document formed by the project subset 116 in FIG. 1 .
- Screen 41 shows the navigation functionality that would allow someone using the device to access in order to move through the sections 41 A retail feature codes, during a meeting with the merchant 12 .
- Screen 42 is what someone using the device would see if they wanted to jump to a specific question 42 A legal name.
- Screen 43 illustrates a sample of how a field input interface 112 of the project schema 100 in FIG. 4 would appear to the user after they have been forwarded to the device by the transport mechanism 104 .
- Each of the fields 43 A represents an object that can be designated by the CDCDS 70 of FIG. 3 .
- Screen 44 shows a field input interface 112 that will appear to the user as a list of items to choose from.
- This input interface 112 can be designated to appear to the sales representative 1 in a broad variety by entering parameters in the table survey questions 120 in FIG. 7A.
- screen 45 shows a numeric object that would be available as a field input interface 112 by entering a particular value for 330 in the survey questions table 120 through the Project creator 108 seen in FIG. 4 .
- the individual input interface 112 can be set with parameters but an entire set of these, such as the Merchant Application 40 A, can be designated with functionality as seen in screen 46 that shows a message “All questions not answered” 46 A that can be set with a functionality. This occurs by entering a value in the table Survey 220 through the Project creator 108 .
- the sales representative 1 taps on the designated input section of the screen to answer the question.
- the box 47 A is the input area which will record in the device a particular value that when transmitted to the project database 60 by the transport mechanism 104 , is received as a value in the answer table 400 of FIG. 7A. From there, the value is changed and forwarded by the translator 15 to the appropriate corporate database 8 and the bank database 10 .
- a stored procedure in the translator 15 pulls the data from the bank database 10 and places it in the answer table 401 .
- a set of field input forms 120 are returned with a partially answered form 48 A as seen on screen 48 . This will contain the merchant number 21 , or a message 22 , or additional data needed 23 .
- the sales representative 1 can use the Equipment calculator 40 B to establish and order the exact requirements of hardware and software 4 for the merchant 12 right during the same scheduled visit.
- Screens 44 , and 49 - 51 shows some of the type of data collected by this project schema 3 100 . These screens also show how the field input forms 120 will be revealed based on values in the table survey questions 120 in the fields skip 344 , skip relative 354 , skip value 346 , and skip method 348 . For example, screen 49 asks what type of business. If retail is chosen, screen 50 appears with the choices of retail feature codes. Based on the input here, screen 44 is shown with a list of features for this feature code chosen in screen 50 . Based on the input in screen 44 , screen 51 is revealed that has a list of printer code options for the features chosen in screen 44 . All input is forwarded through the transport mechanism 104 as mentioned in the previous paragraph.
- FIG. 11 is a screen shot of the Internet portal 186 where summary information and logistics information is available regarding the data and information in the merchant application EDC system 58 .
- the present invention may be implemented with any combination of hardware and software. If implemented as a computer-implemented apparatus, the present invention is implemented using means for performing all of the steps and functions described above.
- the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer useable media.
- the media has embodied therein, for instance, computer readable program code means for providing and facilitating the mechanisms of the present invention.
- the article of manufacture can be included as part of a computer system or sold separately.
Abstract
Description
Claims (9)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/281,481 US7233960B1 (en) | 2001-10-31 | 2002-10-25 | System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US33996401P | 2001-10-31 | 2001-10-31 | |
US10/281,481 US7233960B1 (en) | 2001-10-31 | 2002-10-25 | System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application |
Publications (1)
Publication Number | Publication Date |
---|---|
US7233960B1 true US7233960B1 (en) | 2007-06-19 |
Family
ID=38157173
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/281,481 Expired - Lifetime US7233960B1 (en) | 2001-10-31 | 2002-10-25 | System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application |
Country Status (1)
Country | Link |
---|---|
US (1) | US7233960B1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080097810A1 (en) * | 2006-10-20 | 2008-04-24 | Tsys Acquiring Solutions, L.L.C. | System and Method of Managing Workflow for Express Creation and Initialization of Merchant Accounts |
US20080097897A1 (en) * | 2006-10-20 | 2008-04-24 | Tsys Acquiring Solutions, L.L.C. | System and Method of Express Creation and Initialization of Merchant Accounts |
US20100063889A1 (en) * | 2008-09-08 | 2010-03-11 | Proctor Jr James Arthur | Visual identification information used as confirmation in a wireless communication |
US20120254249A1 (en) * | 2010-03-18 | 2012-10-04 | Nuodb Inc. | Database Management System |
US8781973B1 (en) * | 2004-09-24 | 2014-07-15 | Bank Of America Corporation | Event marketing automated system |
US9501363B1 (en) | 2013-03-15 | 2016-11-22 | Nuodb, Inc. | Distributed database management system with node failure detection |
US10037348B2 (en) | 2013-04-08 | 2018-07-31 | Nuodb, Inc. | Database management system with database hibernation and bursting |
US10067969B2 (en) | 2015-05-29 | 2018-09-04 | Nuodb, Inc. | Table partitioning within distributed database systems |
US10180954B2 (en) | 2015-05-29 | 2019-01-15 | Nuodb, Inc. | Disconnected operation within distributed database systems |
US10740323B1 (en) | 2013-03-15 | 2020-08-11 | Nuodb, Inc. | Global uniqueness checking in distributed databases |
US20200364729A1 (en) * | 2014-01-28 | 2020-11-19 | Mastercard International Incorporated | Systems and methods for determining and analyzing characteristics of devices used in payment transactions |
US10884869B2 (en) | 2015-04-16 | 2021-01-05 | Nuodb, Inc. | Backup and restore in a distributed database utilizing consistent database snapshots |
US11176111B2 (en) | 2013-03-15 | 2021-11-16 | Nuodb, Inc. | Distributed database management system with dynamically split B-tree indexes |
US11573940B2 (en) | 2017-08-15 | 2023-02-07 | Nuodb, Inc. | Index splitting in distributed databases |
Citations (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4905080A (en) | 1986-08-01 | 1990-02-27 | Video Research Ltd. | Apparatus for collecting television channel data and market research data |
US5379213A (en) | 1992-01-28 | 1995-01-03 | Fleetwood Furniture Company, Inc. | Test scoring system and method |
US5437027A (en) | 1990-05-30 | 1995-07-25 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US5570415A (en) | 1991-08-29 | 1996-10-29 | Sasktel | Video programming and storage control using the telephone network |
US5615112A (en) | 1993-01-29 | 1997-03-25 | Arizona Board Of Regents | Synthesized object-oriented entity-relationship (SOOER) model for coupled knowledge-base/database of image retrieval expert system (IRES) |
US5704029A (en) * | 1994-05-23 | 1997-12-30 | Wright Strategies, Inc. | System and method for completing an electronic form |
US5857201A (en) * | 1996-06-18 | 1999-01-05 | Wright Strategies, Inc. | Enterprise connectivity to handheld devices |
US5870765A (en) | 1996-10-09 | 1999-02-09 | Oracle Corporation | Database synchronizer |
US5873086A (en) | 1994-05-10 | 1999-02-16 | Fujitsu Limited | Communications control apparatus and client/server computer system |
US5899998A (en) | 1995-08-31 | 1999-05-04 | Medcard Systems, Inc. | Method and system for maintaining and updating computerized medical records |
US5950173A (en) | 1996-10-25 | 1999-09-07 | Ipf, Inc. | System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents |
US5970490A (en) | 1996-11-05 | 1999-10-19 | Xerox Corporation | Integration platform for heterogeneous databases |
US5995965A (en) | 1996-11-18 | 1999-11-30 | Humetrix, Inc. | System and method for remotely accessing user data records |
US5999908A (en) | 1992-08-06 | 1999-12-07 | Abelow; Daniel H. | Customer-based product design module |
US6012067A (en) | 1998-03-02 | 2000-01-04 | Sarkar; Shyam Sundar | Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web |
US6035297A (en) | 1996-12-06 | 2000-03-07 | International Business Machines Machine | Data management system for concurrent engineering |
US6058393A (en) | 1996-02-23 | 2000-05-02 | International Business Machines Corporation | Dynamic connection to a remote tool in a distributed processing system environment used for debugging |
US6063128A (en) | 1996-03-06 | 2000-05-16 | Bentley Systems, Incorporated | Object-oriented computerized modeling system |
US6065008A (en) | 1997-10-01 | 2000-05-16 | Microsoft Corporation | System and method for secure font subset distribution |
US6067523A (en) | 1997-07-03 | 2000-05-23 | The Psychological Corporation | System and method for reporting behavioral health care data |
US6084585A (en) * | 1998-07-29 | 2000-07-04 | International Business Machines Corp. | System for directly accessing fields on electronic forms |
US6112206A (en) | 1991-08-21 | 2000-08-29 | Intermec Technologies Corporation | Data collection and dissemination system |
US6135349A (en) | 1999-02-01 | 2000-10-24 | First Data Corporation | System and method for enabling a merchant to apply for a credit card processing account using the internet |
US6170057B1 (en) * | 1996-10-16 | 2001-01-02 | Kabushiki Kaisha Toshiba | Mobile computer and method of packet encryption and authentication in mobile computing based on security policy of visited network |
US6193152B1 (en) | 1997-05-09 | 2001-02-27 | Receiptcity.Com, Inc. | Modular signature and data-capture system and point of transaction payment and reward system |
US6298347B1 (en) | 1998-08-25 | 2001-10-02 | Numoda Corporation | System and method for remote data entry |
WO2001073612A1 (en) | 2000-03-24 | 2001-10-04 | Numoda Corporation | Computer system for portable digital data capture and data distribution |
US20010056475A1 (en) * | 1995-12-20 | 2001-12-27 | Anderson William P. | System for on-line financial services using distributed objects |
US20020026410A1 (en) * | 2000-03-01 | 2002-02-28 | Prosecute | Paperless online merchant account approval and provisioning system and method therefor |
US20020052835A1 (en) * | 2000-04-28 | 2002-05-02 | Toscano Paul James | On line loan process |
US20020077964A1 (en) * | 1999-12-15 | 2002-06-20 | Brody Robert M. | Systems and methods for providing consumers anonymous pre-approved offers from a consumer-selected group of merchants |
US20020083044A1 (en) * | 2000-11-09 | 2002-06-27 | Kaplan Arl D. | Method and system for wireless database management |
US20020138414A1 (en) * | 2001-03-26 | 2002-09-26 | Baker Charles Pitman | Method and system and article of manufacture for a rules based automated loan approval system |
US20020138411A1 (en) * | 2001-03-22 | 2002-09-26 | Monlux Clifford John | On-line financing application services including financing application completion and processing |
US6494367B1 (en) * | 1999-10-15 | 2002-12-17 | Ajit Kumar Zacharias | Secure multi-application card system |
US20020194068A1 (en) * | 2001-02-26 | 2002-12-19 | Fred Bishop | System and method for securing data through a PDA portal |
US20020198822A1 (en) * | 2001-06-21 | 2002-12-26 | Rodrigo Munoz | Method and apparatus for evaluating an application for a financial product |
US20030014330A1 (en) * | 1999-04-27 | 2003-01-16 | Showghi Robert S. | Remote ordering system |
US20030033209A1 (en) * | 2001-08-13 | 2003-02-13 | Brian Minear | System and method for providing subscribed applications on wireless devices over a wireless network |
US20030046222A1 (en) * | 2001-06-15 | 2003-03-06 | Bard Keira Brooke | System and methods for providing starter credit card accounts |
US20030083944A1 (en) * | 2001-09-04 | 2003-05-01 | Ncr Corporation | Methods and apparatus for managing sequencing of data received from devices in a retail point of sale system |
US20030120586A1 (en) * | 2001-12-21 | 2003-06-26 | Charles J. Litty | Systems and methods to facilitate analysis of commercial credit customers |
US20030163412A1 (en) * | 2001-03-22 | 2003-08-28 | Monlux Clifford John | On-line financing application services including financing program offering creation |
US20030177066A1 (en) * | 2001-04-12 | 2003-09-18 | Computer Sciences Corporation, A Nevada Corporation, | Integrated marketing promotion system and method |
US6944866B1 (en) * | 2000-11-16 | 2005-09-13 | International Business Machines Corporation | System and method for coordinating operator efforts using action diaries |
-
2002
- 2002-10-25 US US10/281,481 patent/US7233960B1/en not_active Expired - Lifetime
Patent Citations (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4905080A (en) | 1986-08-01 | 1990-02-27 | Video Research Ltd. | Apparatus for collecting television channel data and market research data |
US5437027A (en) | 1990-05-30 | 1995-07-25 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
US6112206A (en) | 1991-08-21 | 2000-08-29 | Intermec Technologies Corporation | Data collection and dissemination system |
US5570415A (en) | 1991-08-29 | 1996-10-29 | Sasktel | Video programming and storage control using the telephone network |
US5379213A (en) | 1992-01-28 | 1995-01-03 | Fleetwood Furniture Company, Inc. | Test scoring system and method |
US5999908A (en) | 1992-08-06 | 1999-12-07 | Abelow; Daniel H. | Customer-based product design module |
US5615112A (en) | 1993-01-29 | 1997-03-25 | Arizona Board Of Regents | Synthesized object-oriented entity-relationship (SOOER) model for coupled knowledge-base/database of image retrieval expert system (IRES) |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US5873086A (en) | 1994-05-10 | 1999-02-16 | Fujitsu Limited | Communications control apparatus and client/server computer system |
US5704029A (en) * | 1994-05-23 | 1997-12-30 | Wright Strategies, Inc. | System and method for completing an electronic form |
US5899998A (en) | 1995-08-31 | 1999-05-04 | Medcard Systems, Inc. | Method and system for maintaining and updating computerized medical records |
US20010056475A1 (en) * | 1995-12-20 | 2001-12-27 | Anderson William P. | System for on-line financial services using distributed objects |
US6058393A (en) | 1996-02-23 | 2000-05-02 | International Business Machines Corporation | Dynamic connection to a remote tool in a distributed processing system environment used for debugging |
US6063128A (en) | 1996-03-06 | 2000-05-16 | Bentley Systems, Incorporated | Object-oriented computerized modeling system |
US5857201A (en) * | 1996-06-18 | 1999-01-05 | Wright Strategies, Inc. | Enterprise connectivity to handheld devices |
US5870765A (en) | 1996-10-09 | 1999-02-09 | Oracle Corporation | Database synchronizer |
US6170057B1 (en) * | 1996-10-16 | 2001-01-02 | Kabushiki Kaisha Toshiba | Mobile computer and method of packet encryption and authentication in mobile computing based on security policy of visited network |
US5950173A (en) | 1996-10-25 | 1999-09-07 | Ipf, Inc. | System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents |
US5970490A (en) | 1996-11-05 | 1999-10-19 | Xerox Corporation | Integration platform for heterogeneous databases |
US5995965A (en) | 1996-11-18 | 1999-11-30 | Humetrix, Inc. | System and method for remotely accessing user data records |
US6035297A (en) | 1996-12-06 | 2000-03-07 | International Business Machines Machine | Data management system for concurrent engineering |
US6193152B1 (en) | 1997-05-09 | 2001-02-27 | Receiptcity.Com, Inc. | Modular signature and data-capture system and point of transaction payment and reward system |
US6067523A (en) | 1997-07-03 | 2000-05-23 | The Psychological Corporation | System and method for reporting behavioral health care data |
US6065008A (en) | 1997-10-01 | 2000-05-16 | Microsoft Corporation | System and method for secure font subset distribution |
US6012067A (en) | 1998-03-02 | 2000-01-04 | Sarkar; Shyam Sundar | Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web |
US6084585A (en) * | 1998-07-29 | 2000-07-04 | International Business Machines Corp. | System for directly accessing fields on electronic forms |
US6298347B1 (en) | 1998-08-25 | 2001-10-02 | Numoda Corporation | System and method for remote data entry |
US6135349A (en) | 1999-02-01 | 2000-10-24 | First Data Corporation | System and method for enabling a merchant to apply for a credit card processing account using the internet |
US20030014330A1 (en) * | 1999-04-27 | 2003-01-16 | Showghi Robert S. | Remote ordering system |
US6494367B1 (en) * | 1999-10-15 | 2002-12-17 | Ajit Kumar Zacharias | Secure multi-application card system |
US20020077964A1 (en) * | 1999-12-15 | 2002-06-20 | Brody Robert M. | Systems and methods for providing consumers anonymous pre-approved offers from a consumer-selected group of merchants |
US20020026410A1 (en) * | 2000-03-01 | 2002-02-28 | Prosecute | Paperless online merchant account approval and provisioning system and method therefor |
WO2001073612A1 (en) | 2000-03-24 | 2001-10-04 | Numoda Corporation | Computer system for portable digital data capture and data distribution |
US6834285B1 (en) * | 2000-03-24 | 2004-12-21 | Numoda Corporation | Computer system for portable digital data capture and data distribution |
US20020052835A1 (en) * | 2000-04-28 | 2002-05-02 | Toscano Paul James | On line loan process |
US20020083044A1 (en) * | 2000-11-09 | 2002-06-27 | Kaplan Arl D. | Method and system for wireless database management |
US6944866B1 (en) * | 2000-11-16 | 2005-09-13 | International Business Machines Corporation | System and method for coordinating operator efforts using action diaries |
US20020194068A1 (en) * | 2001-02-26 | 2002-12-19 | Fred Bishop | System and method for securing data through a PDA portal |
US20020138411A1 (en) * | 2001-03-22 | 2002-09-26 | Monlux Clifford John | On-line financing application services including financing application completion and processing |
US20030163412A1 (en) * | 2001-03-22 | 2003-08-28 | Monlux Clifford John | On-line financing application services including financing program offering creation |
US20020138414A1 (en) * | 2001-03-26 | 2002-09-26 | Baker Charles Pitman | Method and system and article of manufacture for a rules based automated loan approval system |
US20030177066A1 (en) * | 2001-04-12 | 2003-09-18 | Computer Sciences Corporation, A Nevada Corporation, | Integrated marketing promotion system and method |
US20030046222A1 (en) * | 2001-06-15 | 2003-03-06 | Bard Keira Brooke | System and methods for providing starter credit card accounts |
US20020198822A1 (en) * | 2001-06-21 | 2002-12-26 | Rodrigo Munoz | Method and apparatus for evaluating an application for a financial product |
US20030033209A1 (en) * | 2001-08-13 | 2003-02-13 | Brian Minear | System and method for providing subscribed applications on wireless devices over a wireless network |
US20030083944A1 (en) * | 2001-09-04 | 2003-05-01 | Ncr Corporation | Methods and apparatus for managing sequencing of data received from devices in a retail point of sale system |
US20030120586A1 (en) * | 2001-12-21 | 2003-06-26 | Charles J. Litty | Systems and methods to facilitate analysis of commercial credit customers |
Non-Patent Citations (5)
Title |
---|
Fulton, "Sams Tech Yourself Microsoft Excel in 10 minutes", Apr. 30, 1999, Sams Publishing, "Lesson 28: Working with a database". * |
Hester, "FileMaker Pro 5.5 for Windows and Macintosh: Visual QuickStart Guide", Dec. 28, 2001, Copyright 2000, Peachpit Press, "Chapter 2: Database Basics". * |
International Search Report for PCT/US01/09227, dated Jun. 12, 2001, 1 page. |
Peterson, "Absolute Beginner's Guide to Databases", Mar. 5, 2002, Que, "Chapter 1: An Introduction to Databases". * |
Yamagishi et al., A Multi-Representational Design Data Capture System, IEEE Custom Integrated Circuits Conference, 1993, pp. 13.2.1-13.2.4 (4 pages). |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8781973B1 (en) * | 2004-09-24 | 2014-07-15 | Bank Of America Corporation | Event marketing automated system |
US20080097897A1 (en) * | 2006-10-20 | 2008-04-24 | Tsys Acquiring Solutions, L.L.C. | System and Method of Express Creation and Initialization of Merchant Accounts |
US20080097810A1 (en) * | 2006-10-20 | 2008-04-24 | Tsys Acquiring Solutions, L.L.C. | System and Method of Managing Workflow for Express Creation and Initialization of Merchant Accounts |
US8385896B2 (en) | 2008-09-08 | 2013-02-26 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
US20100062758A1 (en) * | 2008-09-08 | 2010-03-11 | Proctor Jr James Arthur | Using a first wireless link to exchange identification information used to communicate over a second wireless link |
US20100063889A1 (en) * | 2008-09-08 | 2010-03-11 | Proctor Jr James Arthur | Visual identification information used as confirmation in a wireless communication |
US8370955B2 (en) | 2008-09-08 | 2013-02-05 | Proxicom Wireless, Llc | Enforcing policies in wireless communication using exchanged identities |
US8385913B2 (en) | 2008-09-08 | 2013-02-26 | Proxicom Wireless, Llc | Using a first wireless link to exchange identification information used to communicate over a second wireless link |
US11074615B2 (en) | 2008-09-08 | 2021-07-27 | Proxicom Wireless Llc | Efficient and secure communication using wireless service identifiers |
US11334918B2 (en) | 2008-09-08 | 2022-05-17 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
US8090616B2 (en) * | 2008-09-08 | 2012-01-03 | Proctor Jr James Arthur | Visual identification information used as confirmation in a wireless communication |
US8849698B2 (en) | 2008-09-08 | 2014-09-30 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
US9038129B2 (en) | 2008-09-08 | 2015-05-19 | Proxicom Wireless, Llc | Enforcing policies in wireless communication using exchanged identities |
US9161164B2 (en) | 2008-09-08 | 2015-10-13 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
US11687971B2 (en) | 2008-09-08 | 2023-06-27 | Proxicom Wireless Llc | Efficient and secure communication using wireless service identifiers |
US11443344B2 (en) | 2008-09-08 | 2022-09-13 | Proxicom Wireless Llc | Efficient and secure communication using wireless service identifiers |
US8504523B2 (en) * | 2010-03-18 | 2013-08-06 | Nuodb Inc. | Database management system |
US20120254249A1 (en) * | 2010-03-18 | 2012-10-04 | Nuodb Inc. | Database Management System |
US11176111B2 (en) | 2013-03-15 | 2021-11-16 | Nuodb, Inc. | Distributed database management system with dynamically split B-tree indexes |
US10282247B2 (en) | 2013-03-15 | 2019-05-07 | Nuodb, Inc. | Distributed database management system with node failure detection |
US9501363B1 (en) | 2013-03-15 | 2016-11-22 | Nuodb, Inc. | Distributed database management system with node failure detection |
US11561961B2 (en) | 2013-03-15 | 2023-01-24 | Nuodb, Inc. | Global uniqueness checking in distributed databases |
US10740323B1 (en) | 2013-03-15 | 2020-08-11 | Nuodb, Inc. | Global uniqueness checking in distributed databases |
US10037348B2 (en) | 2013-04-08 | 2018-07-31 | Nuodb, Inc. | Database management system with database hibernation and bursting |
US11016956B2 (en) | 2013-04-08 | 2021-05-25 | Nuodb, Inc. | Database management system with database hibernation and bursting |
US20200364729A1 (en) * | 2014-01-28 | 2020-11-19 | Mastercard International Incorporated | Systems and methods for determining and analyzing characteristics of devices used in payment transactions |
US10884869B2 (en) | 2015-04-16 | 2021-01-05 | Nuodb, Inc. | Backup and restore in a distributed database utilizing consistent database snapshots |
US10180954B2 (en) | 2015-05-29 | 2019-01-15 | Nuodb, Inc. | Disconnected operation within distributed database systems |
US11222008B2 (en) | 2015-05-29 | 2022-01-11 | Nuodb, Inc. | Disconnected operation within distributed database systems |
US11314714B2 (en) | 2015-05-29 | 2022-04-26 | Nuodb, Inc. | Table partitioning within distributed database systems |
US10067969B2 (en) | 2015-05-29 | 2018-09-04 | Nuodb, Inc. | Table partitioning within distributed database systems |
US11573940B2 (en) | 2017-08-15 | 2023-02-07 | Nuodb, Inc. | Index splitting in distributed databases |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9313209B2 (en) | Loan origination software system for processing mortgage loans over a distributed network | |
Sherman | Business intelligence guidebook: From data integration to analytics | |
US7761591B2 (en) | Central work-product management system for coordinated collaboration with remote users | |
US9253050B2 (en) | Method and apparatus for implementing an active information model | |
US8234222B2 (en) | Benefit management system and method | |
US7516103B1 (en) | Method and apparatus for facilitating electronic acquisition and maintenance of goods and services via the internet | |
US7343348B2 (en) | System for performing real-estate transactions over a computer network using participant templates | |
US7890405B1 (en) | Method and system for enabling collaboration between advisors and clients | |
US11631051B2 (en) | Data processing system and method for managing enterprise information | |
US7275038B1 (en) | Web enabled business to business operating system for rental car services | |
US20090144097A1 (en) | Real estate management system and method | |
US20060143220A1 (en) | Software application framework using meta-data defined object definitions | |
US7233960B1 (en) | System and method for mobile wireless electronic data capture and distribution of a merchant card-processing application | |
KR19990064318A (en) | Sales Process Support System and Method | |
US20100241466A1 (en) | Cash balance pension administration system and method | |
EP0856178A2 (en) | Sales process support system and method | |
McKeen et al. | New developments in practice II: enterprise application integration | |
Pathak | Information technology auditing: an evolving agenda | |
TW486635B (en) | A system, method and article of manufacture for advanced mobile health care processing | |
WO2000030000A2 (en) | Centralized system and method for managing enterprise operations | |
PriceWaterhouseCoopers LLP et al. | The e-business workplace: Discovering the power of enterprise portals | |
Malik | Management information systems | |
KR20230029479A (en) | A system for process coordination and interoperability between different systems, platforms, or enterprises. | |
WO2009051877A1 (en) | Air travel coordination, communication and documentation system, method and computer program | |
Fatehi et al. | International information systems management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NUMODA CORPORATION, PENNSYLVANIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BORIS, ANN S.;WALL, ROSEMARY;REEL/FRAME:013439/0379 Effective date: 20021023 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: NUMODA TECHNOLOGIES, INC., PENNSYLVANIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NUMODA CORPORATION;REEL/FRAME:020218/0902 Effective date: 20071206 |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: LTOS); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: FIRST NIAGARA BANK, N.A.,NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:NUMODA TECHNOLOGIES, INC.;REEL/FRAME:024505/0381 Effective date: 20100608 Owner name: FIRST NIAGARA BANK, N.A., NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:NUMODA TECHNOLOGIES, INC.;REEL/FRAME:024505/0381 Effective date: 20100608 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 8 |
|
SULP | Surcharge for late payment |
Year of fee payment: 7 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2553); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 12 |