US20180095956A1 - System and Method for Retrieving and Consolidating Data According to Apportionment Rules - Google Patents
System and Method for Retrieving and Consolidating Data According to Apportionment Rules Download PDFInfo
- Publication number
- US20180095956A1 US20180095956A1 US15/720,414 US201715720414A US2018095956A1 US 20180095956 A1 US20180095956 A1 US 20180095956A1 US 201715720414 A US201715720414 A US 201715720414A US 2018095956 A1 US2018095956 A1 US 2018095956A1
- Authority
- US
- United States
- Prior art keywords
- data
- entity
- computing system
- consolidated
- data source
- 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.)
- Abandoned
Links
Images
Classifications
-
- G06F17/30011—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
- G06F16/24554—Unary operations; Data partitioning operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/43—Querying
- G06F16/435—Filtering based on additional data, e.g. user or group profiles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
-
- G06F17/30002—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/105—Human resources
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- 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
-
- 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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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/14—Payment architectures specially adapted for billing systems
-
- 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/38—Payment protocols; Details thereof
-
- 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
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
- H04W12/086—Access security using security domains
-
- 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/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
-
- 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
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/22—Social work
Definitions
- the specification relates generally to the retrieval and consolidation of data for transmission, and specifically to systems and methods for retrieving and consolidating data in accordance with at least one apportionment rule.
- a computing system associated with one entity such as a government department
- a computing system associated with another entity such as a private hospital
- data that is accessible to the computing system associated with one entity may not be accessible to the computing system associated with the other entity.
- Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system to a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks performing such data retrieval and transmission activities may be more complex.
- an entity computing system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system.
- the entity computing system comprises: a memory storing computer-executable instructions, and processing device(s) coupled to the memory.
- the computer-executable instructions when executed by the processing device(s) cause the processing device(s) to: receive, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determine which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieve data according to the apportionment rule in respect of each one of the plurality of data sources associated with the entity computing system; store the retrieved data in a consolidated data source; and transmit, via a secure intermediary network, one of the consolidated data source and data stored in the consolidated data source for receipt by the second entity computing system.
- At least one of the plurality of records comprises a third entity system record and at least one of the plurality of data sources comprises a corresponding third entity system data source
- the computer-executable instructions when executed by the processing device(s) cause the processing device(s) to, in respect of each third entity system record: generate a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and corresponding third entity system data source, transmit (via either the secure intermediary network or another secure intermediary network) the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receive (from the third entity computing system via either the secure intermediary network or the another secure intermediary network) third entity data of the corresponding third entity system data source responsive to the first entity data request, and store the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.
- each one of the plurality of records comprises a transaction account
- the at least one request is in respect of payment of an invoice associated with the second entity computing system
- the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account
- the payment is comprised of funds from each transaction account according to the apportionment rule
- the retrieved data comprises funds retrieved from the transaction accounts associated with the entity computing system
- the storage of the retrieved data in the consolidated data source comprises storing the retrieved funds in a consolidated transaction account
- the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
- each one of the plurality of records comprises a transaction account in which each third entity system record corresponds to a third entity transaction account
- the at least one request is in respect of payment of an invoice associated with the second entity computing system
- the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account (including the third entity transaction account)
- the payment is comprised of funds from each transaction account according to the apportionment rule
- the retrieved data comprises funds retrieved from each of the transaction accounts associated with the entity computing system
- the third entity data comprises third entity funds from the third entity transaction account, received from the third entity computing system by electronic funds transfer
- the storage of the retrieved data and the third entity data in a consolidated data source comprises storing the retrieved funds and the third entity funds in a consolidated transaction account
- the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and third entity funds from the consolidated transaction account to the second entity computing system by electronic funds transfer
- At least one of the secure intermediary network and the another secure intermediary network includes a payment network.
- the entity computing system further comprises a payment module, wherein the one of the consolidated data source or data stored in the consolidated data source is transmitted for receipt by the second entity computing system via the payment module.
- a non-transitory computer-readable medium for retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system a second entity computing system.
- the computer-readable medium comprises computer-executable instructions for: receiving, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determining which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieving data according to the apportionment rule in respect of each one of the plurality of data sources associated with the first entity computing system; storing the retrieved data in a consolidated data source; and transmitting, via a secure intermediary network, one of the consolidated
- FIG. 1 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to non-limiting aspects of the application;
- FIG. 2 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to another set of non-limiting aspects of the application;
- FIG. 3 depicts a flowchart illustrating a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application;
- FIG. 4 depicts an aspect of a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application.
- X, Y, and Z or “one or more of X, Y, and Z” language can be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XYY, YZ, ZZ).
- components may be described as being “configured to” or “enabled to” perform one or more functions.
- a component that is configured to or enabled to perform a function is configured to or enabled to perform the function, or is suitable for performing the function, or is adapted to perform the function, or is operable to perform the function, or is otherwise capable of performing the function.
- a computing system associated with one entity such as a government department
- a computing system associated with another entity such as a private hospital
- data that is accessible to the computing system(s) associated with one entity may not be accessible to the computing system(s) associated with the other entity.
- Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system and transmitted for receipt by a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks, and the like, performing such data retrieval and transmission tasks may be more complex.
- a computing system associated with one entity or a governmental authority may impose particular restrictions or requirements for receiving data from computing systems associated with other entities, such as format, size and type. Those requirements may dictate that data is to be transmitted in a consolidated format, such as, for example, a single data packet or specified number of data packets.
- FIG. 1 depicts first entity computing system 100 for retrieving and consolidating data for transmission to second entity computing system 102 .
- First entity computing system 100 is associated with a first entity and second entity computing system 102 is associated with another entity (also referred to herein as a second entity).
- the first entity and second entity may comprise one or more of an organization, institution and enterprise.
- the data to be retrieved and consolidated is associated with a plurality of records (not shown).
- the data to be retrieved may be associated with a plurality of property records, a plurality of inventory records for different products or a plurality of transaction accounts.
- First entity computing system 100 comprises at least one memory 104 and at least one processing device 106 .
- Memory 104 can comprise any suitable memory device, including but not limited to any suitable one of, or combination of, a local and/or remote volatile memory, non-volatile memory, random access memory (RAM), read-only memory (ROM), hard drive, optical drive, buffer(s), cache(s), flash memory, magnetic computer storage devices (e.g. hard disks, floppy disks, and magnetic tape), optical memory ((e.g., CD(s) and DVD(s)), and the like. Other suitable memory devices are within the scope of the application.
- memory may comprise a tangible and non-transitory computer-readable medium (i.e., a medium which does not comprise only a transitory propagating signal per se) comprising or storing computer-executable instructions, such as computer programs, sets of instructions, code, software, and/or data for execution of any method(s), step(s) or process(es) described herein by any processing device(s) and/or microcontroller(s) described herein.
- Memory 104 comprises or is enabled to store computer-executable instructions 108 for execution by at least one processing device, including processing device 106 .
- Processing device 106 is coupled to memory 104 and is enabled to control at least some of the operations first entity computing system 100 .
- the terms “processing device”, “processing devices”, “processing device(s)”, “processor”, “processors” or “processor(s)” may refer to any combination of processing devices, and the like, suitable for carrying out the actions or methods described herein.
- processing device 106 may comprise any suitable processing device, or combination of processing devices, including but not limited to a microprocessor, a central processing unit (CPU) and the like. Other suitable processing devices are within the scope of the application.
- first entity computing system 100 is depicted as a single computing system, it is understood that according to some aspects of the application first entity computing system 100 may comprise multiple computing systems and/or computing devices in which one or more of the computing systems and/or computing devices may be remote from each other (e.g., one or more servers, mobile devices and other suitable computing devices).
- First entity computing system 100 is enabled to communicate with at least one computing device 110 via secure network 112 .
- first entity computing system 100 comprises communication module 114 coupled to processor 106 .
- Communication module 114 is enabled to access secure network 112 via, for example, communication link 116 .
- Communication module 114 comprises any communication device(s) and/or application(s), or combination thereof, suitable for performing the communications with computing device 110 described herein.
- Communication link 116 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof.
- Communication module 114 is also enabled to communicate according to any suitable protocol which is compatible with secure network 112 .
- Non-limiting examples of suitable protocols which may be compatible with secure network 112 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS).
- Communication module 114 is enabled to process data for transmission between first entity computing system 100 and computing device 110 in accordance to security protocols associated with secure network 112 .
- communication module 114 is enabled to encrypt data for transmission to computing device 110 and decrypt data received from computing device 110 via secure network 112 .
- processing device 106 is enabled similarly to communication module 114 such that processing device 106 performs at least some of the communications with computing device 110 described herein rather than communication module 114 .
- Computing device 110 is enabled to access secure network 112 to communicate with first entity computing system 100 .
- computing device 110 is enabled to access secure network 112 via communication link 118 .
- Computing device 110 may comprise a communication module suitable for performing the communications with first entity computing system 100 described herein.
- Communication link 118 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof.
- computing device 110 comprises any suitable computing device, including but not limited to one or more portable electronic devices, mobile computing devices, portable computing devices, tablet computing devices, laptop computing devices, PDAs (personal digital assistants), cellphones, smartphones, computer terminals and the like. Other suitable computing devices are within the scope of the application. For the sake of simplicity a single computing device 110 is shown in FIG. 1 . However, according to some aspects, more than one computing device 110 is enabled to access secure network 112 to communicate with first entity system 100 in a manner similar to computing device 110 .
- First entity computing system 100 is enabled to access a plurality of data sources, such as two or more of data source 120 - 1 , data source 120 - 2 and data source 120 - 3 (referred to collectively as data sources 120 or plurality of data sources 120 , and individually as data source 120 - 1 , data source 120 - 2 , data source 120 - 3 ).
- Data sources 120 are associated with the plurality of records and each one of data sources 120 is associated with a respective one of the plurality of records.
- each one of the plurality of data sources 120 - 1 to 120 - 3 corresponds to each one of the plurality of records (e.g., data source 120 - 1 corresponds to record 1 , data source 120 - 2 corresponds to record 2 , data source 120 - 3 corresponds to record 3 ).
- Data sources 120 comprise any suitable type of data source or combination thereof.
- data sources 120 comprises one or more of a data structure, a database, a data storage device and a data file.
- at least one of data sources 120 is remote from first entity computing system 100 .
- first entity computing system 100 is enabled to access data sources in addition to data sources 120 .
- processing device 106 is enabled to receive, from computing device 110 via secure network 112 , at least one request 122 to retrieve and consolidate data from data sources 120 .
- Request 122 is in any format suitable for processing by processing device 106 .
- Request 122 comprises an apportionment rule that indicates data that is to be retrieved from each one of data sources 120 .
- the apportionment rule may indicate that a first data portion 124 - 1 is to be retrieved from data source 120 - 1 , a second data portion 124 - 2 is to be retrieved from data source 120 - 2 and a third data portion 124 - 3 is to be retrieved from data source 120 - 3 .
- the apportionment rule also indicates that the retrieved data (e.g., first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 ) is to be consolidated for transmission from first entity computing system 100 to second entity computing system 102 .
- second entity computing system 102 may be configured to receive data associated with the request 122 as a consolidated data packet. Additionally, transmitting data retrieved from data sources 120 in consolidated form as opposed to separate transmissions of data from each one of data sources 120 may reduce processing time and drain on processing resources of first entity system 100 in managing data requests, such as request 122 .
- processing device 106 is enabled to determine which of the plurality of records and the plurality of data sources of request 122 is associated with first entity computing system 100 .
- at least one of the plurality of records is associated with a third entity computing system and at least one of the plurality of data sources of request 122 is a corresponding third entity system data source.
- first entity computing system 100 is unable to access the corresponding third entity data source.
- the corresponding third entity computing system may control retrieval and transmission of data from the corresponding data source. Additional discussion about such aspects is provided further below.
- each one of the plurality of records and the plurality of data sources of the request(s) are associated with the third entity.
- processing device 106 may determine which of the plurality of records and the plurality of data sources 120 is associated with first entity computing system 100 using a variety of means.
- first entity computing system 100 may be a computing system of a medical clinic and each one of the plurality of records may be medical records of patients of the medical clinic, and data source 120 - 1 , data source 120 - 2 , data source 120 - 3 may comprise data pertaining to those patients.
- request 122 may comprise an indication that one or more portions of the data to be retrieved from data sources 120 is associated with either a third entity record and a third entity data source.
- the apportionment rule comprises such an indication.
- Processing device 106 is further enabled to retrieve data according to the apportionment rule in respect of each one of data sources 120 that is associated with first entity computing device 100 .
- processing device 106 may determine that each one of data sources 120 , data source 120 - 1 , data source 120 - 2 and data source 120 - 3 , is associated with first entity computing device 100 .
- the apportionment rule of request 122 may indicate that a first data portion 124 - 1 is to be retrieved from data source 120 - 1 , a second data portion 124 - 2 is to be retrieved from data source 120 - 2 and a third data portion 124 - 3 is to be retrieved from data source 120 - 3 .
- processing device 106 is enabled to, prior to retrieving first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 , determine a first data source state of each one of data sources 120 associated with first entity computing system 100 and whether the determined first data source state conflicts with the apportionment rule of request 122 .
- the first data source state may comprise an indication of at least one of a data format, a data size and a data type associated with each one of data sources 120 .
- processing device 106 may be enabled to determine at least one data retrieval parameter indicated in the apportionment rule, such as a data format, a data size and data type of the data to be retrieved from each one of the plurality of data sources, such as data sources 120 , according to request 122 .
- the processing device 106 may then interrogate each one of data sources 120 for data indicative of a first data source state corresponding to the at least one data retrieval parameter.
- the at least one data retrieval parameter comprises a requested data size for each one of first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3
- data source 120 - 1 , data source 120 - 2 and data source 120 - 3 may each return an interrogation response comprising an indication of a current size of data stored at the respective one of data sources 120 .
- processing device 106 may generate and transmit alert data 126 for receipt by computing device 110 via secure network 112 .
- Alert data 126 may comprise an alert message for display at a Graphical User Interface (GUI) of computing system 110 .
- processing device 106 may wait for alert response data 128 from computing device 110 indicative of a response to alert data 126 before proceeding to retrieve data from data sources 120 .
- alert response data 128 comprises a revised request to retrieve and consolidate data from data sources 120 .
- processing device 106 after retrieving the requested data (e.g., first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 ), processing device 106 is enabled to determine a second data source state of each one of data sources 120 associated with first entity computing system 100 . According to some aspects, processing device 106 stores the determined second data source state of each one of data sources 120 associated with first entity computing system 100 at memory 104 or another suitable device, module or data source.
- At least one reconciliation data source such as reconciliation data source 130
- reconciliation data source 130 comprises one or more of a data structure, a database, a data storage device and a data file.
- Processing device 106 is enabled to store the retrieved data, first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 in the present non-limiting aspect, in consolidated data source 132 .
- Consolidated data source 132 comprises any suitable type of data source or combination thereof.
- consolidated data source 132 comprises one or more of a data structure, a database, a data storage device and a data file.
- consolidated data source 132 is depicted as a data source separate from data sources 120 and reconciliation data source 130 , according to some aspects one or more of data sources 120 and reconciliation data source 130 comprise consolidated data source 132 (or data to be stored in consolidated data source).
- data to be stored at consolidated data source 132 is stored at a data source that may also store other data.
- data source 120 - 1 , data source 120 - 2 and data source 120 - 3 comprises consolidated data source 132 (or data stored in consolidated data source).
- Processing device 106 is enabled to transmit, via secure intermediary network 134 , one of the consolidated data source 132 or data stored in the consolidated source 132 for receipt by second entity computing system 102 according to any suitable protocol which is compatible with secure intermediary network 134 .
- suitable protocols compatible with secure intermediary network 134 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS).
- WEP Wired Equivalent Privacy
- WPA Wi-Fi Protected Access
- SSL Secure Sockets Layer
- TLS Transport Layer Security
- Suitable communication protocols for secure intermediary network 134 may be based on or dictated by, for example, the type of data being transmitted between first entity computing system 100 and second entity computing system 102 , the type of entity associated with either first entity computing system 100 or second entity computing system 102 , system requirements or data transmission policies of first entity computing system 100 and second entity computing system 102 , and/or policies of a relevant governmental authority.
- one of the consolidated data source 132 or data stored in the consolidated source 132 is transmitted via communication module 114 , or other computing module of first entity computing system 100 suitable for transmitting one of the consolidated data source 132 or data stored in the consolidated source 132 via secure intermediary network 134 .
- First entity computing system 100 and second entity computing system 102 communicate with each other via secure intermediary network 134 using communication links 136 and 138 .
- Communication links 136 and 138 comprise any suitable wired and/or wireless communication link(s), or suitable combination thereof.
- FIG. 2 depicts a first entity computing system 200 for retrieving and consolidating data associated with a plurality of records for transmission to second entity computing system 102 , according to another exemplary aspect of the application and in which like or similar elements are denoted by like or similar numbers in FIG. 1 .
- discussion of the systems and devices depicted in FIG. 2 will focus on certain similarities and differences from those depicted in FIG. 1 .
- first entity computing system 200 comprises memory 104 coupled to processing device 106 .
- Memory 104 stores computer-executable instructions 208 which is similar to computer-executable instructions 108 , aside from the differences described further below.
- First entity computing system 200 is also enabled to access a plurality of data sources 120 associated with a plurality of records.
- first entity computing system 200 is also enabled to communicate with a computing system associated with a third entity, such as third entity computing system 240 , via secure intermediary network 242 according to any protocol compatible with second secure intermediary network 242 and suitable for communications between first entity computing system 200 and third entity computing system 240 .
- the communication protocols for second secure intermediary network 242 may be similar to the communication protocols for secure intermediary network 134 .
- Communications between first entity computing system 200 and third entity computing system 240 via second secure intermediary network 242 utilize communication links 244 and 246 .
- Communication links 244 and 246 comprise any suitable wired and/or wireless communication link(s), or suitable combination thereof.
- third entity computing system 240 is enabled to communicate with first entity computing system 200 via secure intermediary network 134 and/or second secure intermediary network 242 .
- Third entity computing system 240 is associated with third entity system record(s) (not shown).
- the third entity system record(s) is associated with at least one corresponding third entity data source, such as corresponding third entity data source 248 , that is accessible and/or controlled by third entity computing system 240 .
- third entity computing system 240 is configured to access the third entity system record and corresponding third entity system data source(s) 248 .
- corresponding third entity system data source(s) 248 is not accessible to or controlled by first entity computing system 200 .
- processing device 106 of first entity computing system 200 is enabled to receive, from computing device 110 via secure network 112 , requests to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records in accordance with computer-executable instructions stored at memory 104 .
- processing device 106 may be enabled to receive request 222 from computing device 110 to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records, in which at least one of the plurality of records includes a third entity system record and at least one of the plurality of data sources includes a corresponding third entity system data source, such as third entity system data source(s) 248 .
- request 222 comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources, such as data source 120 - 1 , data source 120 - 2 , data source 120 - 3 and corresponding third entity data source 248 , and consolidated for transmission to second entity computing system 102 .
- Processing device 106 is also enabled to, in accordance with computer-executable instructions 208 , to determine which of the plurality of records and the plurality of data sources is associated with first entity computing system 200 in a manner similar to that described in reference to first entity computing system 100 and computer-executable instructions 108 .
- processing device 106 is enabled to, in accordance with computer-executable instructions 208 , to determine which of the plurality of records and the plurality of data sources is associated with third entity system record(s) and corresponding third entity system data source(s) 248 .
- request 222 may comprise an indication that one or more portions of the data to be retrieved from the plurality of data sources, data source 120 - 1 , data source 120 - 2 , data source 120 - 3 and corresponding third entity data source 248 , is associated with third entity records(s) and/or corresponding third entity data source 248 .
- the apportionment rule comprises such an indication.
- the apportionment rule of request 222 may indicate that first data portion 124 - 1 is to be retrieved from data source 120 - 1 , second data portion 124 - 2 is to be retrieved from data source 120 - 2 , third data portion 124 - 3 is to be retrieved from data source 120 - 3 and a fourth data portion 250 is to be retrieved from third entity computing system 240 and/or corresponding third entity data source 248 .
- first entity computing system 200 Since corresponding third entity data source 248 is inaccessible or otherwise outside the control of first entity computing system 200 , first entity computing system 200 must request fourth data portion 250 from third entity computing system 240 .
- Processing device 106 is enabled to, according to computer-executable instructions 208 , generate a first entity data request 252 comprising authentication data and data indicative of request 222 in respect of third entity system record(s) and third entity record(s) and/or corresponding third entity system data source 248 .
- the authentication data comprises any data suitable for authenticating request 222 to third entity computing system 240 in respect of the third entity.
- the authentication data may comprise credentials associated with computing device 110 , a profile associated with computing device 110 and/or received by a suitable input device of computing device 110 that are associated with at least one of the third entity system record(s) and corresponding third entity system data source 248 .
- processing device 106 is enabled to transmit first entity data request 252 via second secure intermediary network 242 for receipt by third entity computing system 240 .
- Processing device 106 is also enabled to receive, from third entity computing system 240 via second secure intermediary network 242 , third entity data of corresponding third entity system data source 248 responsive to first entity data request 252 , such as fourth data portion 250 .
- Processing device 106 is further enabled to store the third entity data of corresponding third entity system data source 248 , fourth data portion 250 in the present example, in consolidated data source 132 such that the consolidated data source comprises the data retrieved from data sources 120 (associated with first entity computing system 200 ) and the third entity data, such as fourth data portion 250 .
- processing device 106 of the exemplary aspect depicted in FIG. 2 is enabled to transmit, via secure intermediary network 134 , one of the consolidated data source 132 or data stored in the consolidated source 132 for receipt by second entity computing system 102 .
- FIGS. 3 and 4 depict a flowchart of a method 300 of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application.
- method 300 is performed using either first entity computing system 100 or first entity computing system 200 , as indicated.
- first entity computing system 100 and first entity computing system 200 will lead to a further understanding of first entity computing system 100 and first entity computing system 200 , and the various components of those systems.
- first entity computing system 100 , first entity computing system 200 and/or method 300 can be varied, and need not work exactly as discussed herein in conjunction with each other, and that such variations are within the scope of present implementations.
- method 300 is implemented by first entity computing system 100 or first entity computing system 200 by processing device 106 .
- method 300 is one way in which first entity computing system 100 or first entity computing system 200 may be configured. It is to be emphasized, however, that method 300 need not be performed in the exact sequence as shown, unless otherwise indicated; and likewise various blocks may be performed in parallel rather than in sequence; hence the elements of method 300 are referred to herein as “blocks” rather than “steps”. It is also to be understood, however, that method 300 can be implemented on variations of first entity computing system 100 and first computing system 200 as well.
- At block 302 at least one processing device of first entity computing system 100 or first entity computing system 200 , such as processing device 106 , receives at least one request, such as request 122 or request 222 , to retrieve and consolidate data from a plurality of data sources associated with a plurality of records.
- the plurality of data records may be associated with data sources 120 .
- the plurality of data records may be associated with data sources 120 and data source 248 .
- the request(s) to retrieve and consolidate data comprises an apportionment rule that indicates data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system, such as second entity computing system 102 .
- the at least one processing device determines which of the plurality of records and plurality of data sources is associated with the first entity computing system. According to some aspects, processing device 106 determines that data sources 120 (data source 120 - 1 , data source 120 - 2 and data source 120 - 3 ) are associated with the first entity computing system 100 .
- At least one of the plurality of records may be a third entity system record and at least one of the plurality of data sources is a corresponding third entity system data source, such as corresponding third entity system data source 248 .
- processing device 106 generates a first entity data request, such as first entity data request 252 , comprising authentication data and data indicative of the at least one request, such as request 222 , in respect of the third entity system record and corresponding third entity system data source, such as corresponding third entity system data source 248 .
- the at least one processing device transmits the first entity data request, such as first entity data request 252 , for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, such as third entity computing system 240 configured to access corresponding third entity system data source 248 .
- first entity data request 252 is transmitted via second secure intermediary network 242 .
- third entity computing system 240 is configured to communicate with first entity computing system 200 via secure intermediary network 134
- first entity data request 252 is transmitted via secure intermediary network 134 .
- the at least one processing device receives third entity data of the corresponding third entity system data source responsive to the first entity data request.
- processing device 106 receives fourth data portion 250 of corresponding third entity system data source 248 , which is responsive to first entity data request 252 .
- processing device 106 receives third entity data via second secure intermediary network 242 .
- processing device 106 receives the third entity data, such as fourth data portion 250 , via secure intermediary network 134 .
- the at least one processing device stores the third entity data in a consolidated data source.
- processing device 106 stores fourth data portion 250 in consolidated data source 132 .
- the at least one processing device retrieves data according to the apportionment rule in respect of data sources associated with the first entity computing system. For example, according to some aspects, processing device 106 retrieves first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 from data source 120 - 1 , data source 120 - 2 and data source 120 - 3 , respectively.
- the at least one processing device stores the data retrieved in accordance with the apportionment rule in a consolidated data source.
- processing device 106 stores first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 in consolidated data source 132 .
- processing device 106 stores first data portion 124 - 1 , second data portion 124 - 3 , third data portion 124 - 3 and fourth data portion 250 at consolidated data source 132 such that the data stored at consolidated data source comprises data retrieved from data sources 120 and third entity system data source 248 .
- At block 318 at least one processing device transmits, via the secure intermediary network, one of the consolidated data source and the data stored in the consolidated data source for receipt by the second entity computing system.
- processing device 106 transmits first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 .
- processing device 106 transmits first data portion 124 - 1 , second data portion 124 - 3 , third data portion 124 - 3 and fourth data portion 250 .
- the at least one processing device transmits one of the consolidated data source and the data stored in the consolidated data source to an intermediary module enabled to transmit data, via the secure intermediary network, from the first entity computing system for receipt by the second entity computing system.
- the intermediary module may perform additional processing to the consolidated data source or data stored in the consolidated data source prior to transmission via the secure intermediary network for receipt by the second entity computing system.
- Such additional processing may, according to some aspects, be performed to enhance the suitability of the data to be transmitted via the secure intermediary network for receipt by the second entity computing system.
- the additional processing may comprise one or more of encryption and compression.
- communication module 114 is enabled to transmit data, via the secure intermediary network 134 , for receipt by second entity computing system 102 .
- processing device 106 transmits one of the consolidated data source 132 and the data stored in the consolidated data source 132 to communication module 114 , which transmits the received one of the consolidated data source 132 and the data stored in the consolidated data source 132 via secure intermediary network 134 .
- communication module 114 comprises at least one processing device suitable configured to carry out such communication tasks.
- first entity computing system 100 and first entity computing system 200 are computing system(s) operated by a financial institution, such as a bank
- second entity computing system 102 is a computing system operated by an entity separate from the financial institution, such as a merchant, utility provider or government entity, and which issues at least one invoice for payment by a user with access to or who is otherwise associated with computing device 110 (also referred to herein as an “issuing entity”).
- request 122 and request 222 are in respect of payment of an invoice associated with the second entity computing system 102 .
- the payment of the invoice is comprised of funds from each one of the plurality of transaction accounts according to the respective apportionment rule.
- request 122 and request 222 each comprise a request to retrieve and consolidate data from a plurality of data sources associated with a plurality of records.
- each one of the plurality of records comprises a transaction account, such as a debit card, a credit card account, a checking account and a line of credit account, and each one of the data sources is associated with each transaction account provided by the first entity, such as data source 120 .
- data source 120 - 1 is associated with a debit card account
- data source 120 - 2 is associated with a credit card account
- data source 120 - 3 is associated with a checking account associated with the first entity and which are transaction accounts held by a user with access to or who otherwise associated with computing device 110 .
- At least one of the transaction accounts is associated with a third entity.
- third entity computing system 240 is operated by another financial institution, separate from the financial institution of the first entity, and corresponding third entity system data source 248 is associated with a line of credit provided to the user by the other financial institution.
- the data indicated by request 122 and request 222 to be retrieved from the transaction account(s) according to the apportionment rule comprises funds associated with each transaction account indicated in the respective request.
- the apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction account(s).
- the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided only by the first entity, such as the debit card account associated with data source 120 - 1 , the credit card account associated with data source 120 - 2 and the checking account associated with data source 120 - 3 .
- the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided by both the first entity and the second entity, such as the debit card account associated with data source 120 - 1 , the credit card account associated with data source 120 - 2 , the checking account associated with data source 120 - 3 and the line of credit associated with corresponding third entity system data source 248 . Additionally, the apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction accounts indicated in request 122 or request 222 .
- the data retrieved in accordance with the apportionment rule comprises funds to be retrieved from the transaction accounts associated with the first entity computing system 100 , first entity computing system 200 and, in respect of the apportionment rule of request 222 , also comprises funds to be retrieved from the transaction account(s) associated with the third entity computing system 240 (also referred to herein as “third entity funds”).
- the third entity data provided in response to the first entity data request 252 comprises funds from the third entity transaction account transferred by Electronic Funds Transfer (ETF), such as Direct Deposit and/or InteracTM e-transfer, or any other suitable manner of transferring the third entity funds for receipt by first entity computing system 200 .
- ETF Electronic Funds Transfer
- storing the retrieved data and/or the third entity data in a consolidated data source comprises storing the funds retrieved from the transaction account(s) according to the apportionment rule in a consolidated transaction account, such as in least one consolidated transaction account associated with consolidated data source 132 .
- consolidated data source 132 and the at least one consolidated transaction account, is not a separate data source or transaction account, but comprises a portion or subset of another data source or transaction account.
- funds that are to be stored in the at least one consolidated transaction account as described above are stored in a central account of the first entity or a ledger account associated with treasury funds of the first entity.
- the data to be stored at consolidated data source 132 e.g., the retrieved data and/or the third entity data
- the funds to be stored in the at least one consolidated transaction account are stored in at least one other data source or transaction account operated by the first entity that is not necessarily dedicated to only storing the retrieved data and/or the third entity data or the retrieved funds and/or third entity funds.
- the retrieved data and/or the third entity data, or the retrieved funds and/or third entity funds are stored with an indication that the data or funds are to be transmitted or transferred as a consolidated payment or a consolidated data transmission (e.g., single data packet).
- the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and/or third entity funds from the consolidated transaction account to the second entity computing system by ETF, or other any other suitable manner of transferring the retrieved funds and/or third entity funds for receipt by second computing entity system 102 .
- first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 comprise funds retrieved in accordance with the apportionment rule and stored at a consolidation transaction account associated with consolidated data source 132 .
- Transmitting first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 via secure network 134 for receipt by second entity computing system 102 may comprise transferring funds from the consolidated transaction account(s) to second entity computing system 102 by ETF.
- one of the consolidated data source 132 or data stored in the consolidated source 132 may be transmitted via communication module 114 , or another suitable computing module of first entity computing system 100 , for receipt by second entity computing system 102 via secure intermediary network 134 .
- communication module 114 or the other suitable computing module described above, may comprise a payment module enabled to process and transmit data in respect of payments of invoices from an issuing entity via secure intermediary network 134 .
- At least one of secure intermediary network 134 and second secure intermediary network 242 is a payment network that may be enabled to transmit data associated with payments to second entity computing system 102 .
- at least one of secure intermediary network 134 and second secure intermediary network 242 may comprise or otherwise be enabled to access an Automated Clearing House (ACH) network or other network(s) suitable and/or specifically enabled to receive, track and/or transmit data associated with payments.
- ACH Automated Clearing House
- At least one of secure intermediary network 134 and second secure intermediary network 242 may operate in accordance with laws and/or guidelines associated with at least one relevant governmental authority in compliance with which one or more of first entity computing system 100 , first entity computing system 200 may operate.
- processing device 106 is enabled to store data indicative of the determined second data source state and/or state change data indicative of any changes between the first data source state and the second data source state for one or more of data sources 120 in reconciliation data source 130 .
- the first data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120
- the second data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120 after the retrieval of first data portion 124 - 1 , second data portion 124 - 2 and third data portion 124 - 3 , and the funds associated therewith.
- state change data stored at reconciliation data source 130 comprises an indication of changes in the amount of funds available at the transaction account(s) associated with first entity computing system 100 , first entity computing system 200 , which may assist in generating data for a ledger of the first entity.
- first entity computing system 100 can be implemented using pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), etc.), or other related components.
- ASICs application specific integrated circuits
- EEPROMs electrically erasable programmable read-only memories
- the functionality of first entity computing system 100 , first entity computing system 200 and method 300 can be achieved using a computing apparatus that has access to a code memory (not shown) which stores computer-readable program code for operation of the computing apparatus.
- the computer-readable program code could be stored on a computer readable storage medium which is fixed, tangible and readable directly by these components, (e.g., removable diskette, CD-ROM, ROM, fixed disk, USB drive). Furthermore, it is appreciated that the computer-readable program can be stored as a computer program product comprising a computer usable medium. Further, a persistent storage device can comprise the computer readable program code. It is yet further appreciated that the computer-readable program code and/or computer usable medium can comprise a non-transitory computer-readable program code and/or non-transitory computer usable medium. Alternatively, the computer-readable program code could be stored remotely but transmittable to these components via a modem or other interface device connected to a network (including, without limitation, the Internet) over a transmission medium.
- the transmission medium can be either a non-mobile medium (e.g., optical and/or digital and/or analog communications lines) or a mobile medium (e.g., microwave, infrared, free-space optical or other transmission schemes) or a
Abstract
Description
- The present application claims priority from U.S. Provisional Patent Application No. 62/402,529 filed on Sep. 30, 2016, the contents being incorporated herein by reference.
- The specification relates generally to the retrieval and consolidation of data for transmission, and specifically to systems and methods for retrieving and consolidating data in accordance with at least one apportionment rule.
- Situations may arise in which a computing system associated with one entity, such as a government department, must retrieve data from a computing system associated with another entity, such as a private hospital, in order to fulfill a data request. Since the computing systems are associated with different entities, data that is accessible to the computing system associated with one entity may not be accessible to the computing system associated with the other entity. Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system to a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks performing such data retrieval and transmission activities may be more complex.
- In an aspect of the present application, there is provided an entity computing system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system. The entity computing system comprises: a memory storing computer-executable instructions, and processing device(s) coupled to the memory. The computer-executable instructions when executed by the processing device(s) cause the processing device(s) to: receive, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determine which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieve data according to the apportionment rule in respect of each one of the plurality of data sources associated with the entity computing system; store the retrieved data in a consolidated data source; and transmit, via a secure intermediary network, one of the consolidated data source and data stored in the consolidated data source for receipt by the second entity computing system.
- According to some aspects, at least one of the plurality of records comprises a third entity system record and at least one of the plurality of data sources comprises a corresponding third entity system data source, and the computer-executable instructions when executed by the processing device(s) cause the processing device(s) to, in respect of each third entity system record: generate a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and corresponding third entity system data source, transmit (via either the secure intermediary network or another secure intermediary network) the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receive (from the third entity computing system via either the secure intermediary network or the another secure intermediary network) third entity data of the corresponding third entity system data source responsive to the first entity data request, and store the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.
- According to some aspects, each one of the plurality of records comprises a transaction account, the at least one request is in respect of payment of an invoice associated with the second entity computing system, the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account, the payment is comprised of funds from each transaction account according to the apportionment rule, the retrieved data comprises funds retrieved from the transaction accounts associated with the entity computing system, the storage of the retrieved data in the consolidated data source comprises storing the retrieved funds in a consolidated transaction account, and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
- According to some aspects, each one of the plurality of records comprises a transaction account in which each third entity system record corresponds to a third entity transaction account, the at least one request is in respect of payment of an invoice associated with the second entity computing system, the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account (including the third entity transaction account), the payment is comprised of funds from each transaction account according to the apportionment rule, the retrieved data comprises funds retrieved from each of the transaction accounts associated with the entity computing system, the third entity data comprises third entity funds from the third entity transaction account, received from the third entity computing system by electronic funds transfer, the storage of the retrieved data and the third entity data in a consolidated data source comprises storing the retrieved funds and the third entity funds in a consolidated transaction account, and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and third entity funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
- According to some aspects, at least one of the secure intermediary network and the another secure intermediary network includes a payment network.
- According to some aspects, the entity computing system further comprises a payment module, wherein the one of the consolidated data source or data stored in the consolidated data source is transmitted for receipt by the second entity computing system via the payment module.
- According to some aspects, there is provided a non-transitory computer-readable medium for retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system a second entity computing system. The computer-readable medium comprises computer-executable instructions for: receiving, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determining which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieving data according to the apportionment rule in respect of each one of the plurality of data sources associated with the first entity computing system; storing the retrieved data in a consolidated data source; and transmitting, via a secure intermediary network, one of the consolidated data source or data stored in the consolidated data source for receipt by the second entity computing system.
- For a better understanding of the various aspects of the application described herein and to show more clearly how they may be carried into effect, reference will now be made, by way of example only, to the accompanying drawings in which:
-
FIG. 1 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to non-limiting aspects of the application; -
FIG. 2 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to another set of non-limiting aspects of the application; -
FIG. 3 depicts a flowchart illustrating a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application; and -
FIG. 4 depicts an aspect of a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application. - Herein described are systems and methods for retrieving and consolidating data associated with a plurality of records for transmission between computing systems associated with different entities. It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the exemplary aspects of the present application described herein. However, it will be understood by those of ordinary skill in the art that the exemplary aspects described herein may be practised without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the exemplary aspects described herein. Also, the description is not to be considered as limiting the scope of the exemplary aspects described herein. Any systems, method steps, components, parts of components, and the like described herein in the singular are to be interpreted as also including a description of such systems, method steps, components, parts of components, and the like in the plural, and vice versa.
- It will also be understood that for the purposes of this application, “at least one of X, Y, and Z” or “one or more of X, Y, and Z” language can be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XYY, YZ, ZZ).
- In the present application, components may be described as being “configured to” or “enabled to” perform one or more functions. Generally, it is understood that a component that is configured to or enabled to perform a function is configured to or enabled to perform the function, or is suitable for performing the function, or is adapted to perform the function, or is operable to perform the function, or is otherwise capable of performing the function.
- As alluded to above, situations may arise in which a computing system associated with one entity, such as a government department, requires data from a computing system associated with another entity, such as a private hospital, to fulfill data requests. Since the two computing systems are associated with different entities, data that is accessible to the computing system(s) associated with one entity may not be accessible to the computing system(s) associated with the other entity. Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system and transmitted for receipt by a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks, and the like, performing such data retrieval and transmission tasks may be more complex.
- Furthermore, a computing system associated with one entity or a governmental authority may impose particular restrictions or requirements for receiving data from computing systems associated with other entities, such as format, size and type. Those requirements may dictate that data is to be transmitted in a consolidated format, such as, for example, a single data packet or specified number of data packets.
-
FIG. 1 depicts firstentity computing system 100 for retrieving and consolidating data for transmission to secondentity computing system 102. Firstentity computing system 100 is associated with a first entity and secondentity computing system 102 is associated with another entity (also referred to herein as a second entity). By way of non-limiting example, the first entity and second entity may comprise one or more of an organization, institution and enterprise. The data to be retrieved and consolidated is associated with a plurality of records (not shown). For example, the data to be retrieved may be associated with a plurality of property records, a plurality of inventory records for different products or a plurality of transaction accounts. - First
entity computing system 100 comprises at least onememory 104 and at least oneprocessing device 106.Memory 104 can comprise any suitable memory device, including but not limited to any suitable one of, or combination of, a local and/or remote volatile memory, non-volatile memory, random access memory (RAM), read-only memory (ROM), hard drive, optical drive, buffer(s), cache(s), flash memory, magnetic computer storage devices (e.g. hard disks, floppy disks, and magnetic tape), optical memory ((e.g., CD(s) and DVD(s)), and the like. Other suitable memory devices are within the scope of the application. As such, it is understood that the term “memory”, or any variation thereof, as used herein may comprise a tangible and non-transitory computer-readable medium (i.e., a medium which does not comprise only a transitory propagating signal per se) comprising or storing computer-executable instructions, such as computer programs, sets of instructions, code, software, and/or data for execution of any method(s), step(s) or process(es) described herein by any processing device(s) and/or microcontroller(s) described herein.Memory 104 comprises or is enabled to store computer-executable instructions 108 for execution by at least one processing device, includingprocessing device 106. -
Processing device 106 is coupled tomemory 104 and is enabled to control at least some of the operations firstentity computing system 100. As used herein, the terms “processing device”, “processing devices”, “processing device(s)”, “processor”, “processors” or “processor(s)” may refer to any combination of processing devices, and the like, suitable for carrying out the actions or methods described herein. For example,processing device 106 may comprise any suitable processing device, or combination of processing devices, including but not limited to a microprocessor, a central processing unit (CPU) and the like. Other suitable processing devices are within the scope of the application. - Although first
entity computing system 100 is depicted as a single computing system, it is understood that according to some aspects of the application firstentity computing system 100 may comprise multiple computing systems and/or computing devices in which one or more of the computing systems and/or computing devices may be remote from each other (e.g., one or more servers, mobile devices and other suitable computing devices). - First
entity computing system 100 is enabled to communicate with at least onecomputing device 110 viasecure network 112. For example, in some aspects, firstentity computing system 100 comprisescommunication module 114 coupled toprocessor 106.Communication module 114 is enabled to accesssecure network 112 via, for example,communication link 116.Communication module 114 comprises any communication device(s) and/or application(s), or combination thereof, suitable for performing the communications withcomputing device 110 described herein.Communication link 116 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof.Communication module 114 is also enabled to communicate according to any suitable protocol which is compatible withsecure network 112. Non-limiting examples of suitable protocols which may be compatible withsecure network 112 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS).Communication module 114 is enabled to process data for transmission between firstentity computing system 100 andcomputing device 110 in accordance to security protocols associated withsecure network 112. For example, in some aspects,communication module 114 is enabled to encrypt data for transmission tocomputing device 110 and decrypt data received fromcomputing device 110 viasecure network 112. In some aspects,processing device 106 is enabled similarly tocommunication module 114 such thatprocessing device 106 performs at least some of the communications withcomputing device 110 described herein rather thancommunication module 114. -
Computing device 110 is enabled to accesssecure network 112 to communicate with firstentity computing system 100. For example,computing device 110 is enabled to accesssecure network 112 viacommunication link 118.Computing device 110 may comprise a communication module suitable for performing the communications with firstentity computing system 100 described herein.Communication link 118 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof. In general,computing device 110 comprises any suitable computing device, including but not limited to one or more portable electronic devices, mobile computing devices, portable computing devices, tablet computing devices, laptop computing devices, PDAs (personal digital assistants), cellphones, smartphones, computer terminals and the like. Other suitable computing devices are within the scope of the application. For the sake of simplicity asingle computing device 110 is shown inFIG. 1 . However, according to some aspects, more than onecomputing device 110 is enabled to accesssecure network 112 to communicate withfirst entity system 100 in a manner similar tocomputing device 110. - First
entity computing system 100 is enabled to access a plurality of data sources, such as two or more of data source 120-1, data source 120-2 and data source 120-3 (referred to collectively as data sources 120 or plurality of data sources 120, and individually as data source 120-1, data source 120-2, data source 120-3). Data sources 120 are associated with the plurality of records and each one of data sources 120 is associated with a respective one of the plurality of records. For example, if the plurality of records comprises records 1 to 3, then each one of the plurality of data sources 120-1 to 120-3 corresponds to each one of the plurality of records (e.g., data source 120-1 corresponds to record 1, data source 120-2 corresponds to record 2, data source 120-3 corresponds to record 3). Data sources 120 comprise any suitable type of data source or combination thereof. For example, in some aspects, data sources 120 comprises one or more of a data structure, a database, a data storage device and a data file. In some aspects of the application, at least one of data sources 120 is remote from firstentity computing system 100. In some aspects, firstentity computing system 100 is enabled to access data sources in addition to data sources 120. - In accordance with computer-
executable instructions 108,processing device 106 is enabled to receive, from computingdevice 110 viasecure network 112, at least onerequest 122 to retrieve and consolidate data from data sources 120.Request 122 is in any format suitable for processing byprocessing device 106.Request 122 comprises an apportionment rule that indicates data that is to be retrieved from each one of data sources 120. For example, the apportionment rule may indicate that a first data portion 124-1 is to be retrieved from data source 120-1, a second data portion 124-2 is to be retrieved from data source 120-2 and a third data portion 124-3 is to be retrieved from data source 120-3. The apportionment rule also indicates that the retrieved data (e.g., first data portion 124-1, second data portion 124-2 and third data portion 124-3) is to be consolidated for transmission from firstentity computing system 100 to secondentity computing system 102. For example, secondentity computing system 102 may be configured to receive data associated with therequest 122 as a consolidated data packet. Additionally, transmitting data retrieved from data sources 120 in consolidated form as opposed to separate transmissions of data from each one of data sources 120 may reduce processing time and drain on processing resources offirst entity system 100 in managing data requests, such asrequest 122. - In accordance with computer-
executable instructions 108,processing device 106 is enabled to determine which of the plurality of records and the plurality of data sources ofrequest 122 is associated with firstentity computing system 100. In some aspects, as discussed further below, at least one of the plurality of records is associated with a third entity computing system and at least one of the plurality of data sources ofrequest 122 is a corresponding third entity system data source. In such aspects, firstentity computing system 100 is unable to access the corresponding third entity data source. For example, the corresponding third entity computing system may control retrieval and transmission of data from the corresponding data source. Additional discussion about such aspects is provided further below. - It is also understood that, according to some aspects, each one of the plurality of records and the plurality of data sources of the request(s) are associated with the third entity.
- Returning to
FIG. 1 ,processing device 106 may determine which of the plurality of records and the plurality of data sources 120 is associated with firstentity computing system 100 using a variety of means. For example, firstentity computing system 100 may be a computing system of a medical clinic and each one of the plurality of records may be medical records of patients of the medical clinic, and data source 120-1, data source 120-2, data source 120-3 may comprise data pertaining to those patients. However, in some aspects,request 122 may comprise an indication that one or more portions of the data to be retrieved from data sources 120 is associated with either a third entity record and a third entity data source. In some aspects, the apportionment rule comprises such an indication. -
Processing device 106 is further enabled to retrieve data according to the apportionment rule in respect of each one of data sources 120 that is associated with firstentity computing device 100. For example,processing device 106 may determine that each one of data sources 120, data source 120-1, data source 120-2 and data source 120-3, is associated with firstentity computing device 100. The apportionment rule ofrequest 122 may indicate that a first data portion 124-1 is to be retrieved from data source 120-1, a second data portion 124-2 is to be retrieved from data source 120-2 and a third data portion 124-3 is to be retrieved from data source 120-3. - According to some aspects,
processing device 106 is enabled to, prior to retrieving first data portion 124-1, second data portion 124-2 and third data portion 124-3, determine a first data source state of each one of data sources 120 associated with firstentity computing system 100 and whether the determined first data source state conflicts with the apportionment rule ofrequest 122. According to some aspects, the first data source state may comprise an indication of at least one of a data format, a data size and a data type associated with each one of data sources 120. For example,processing device 106 may be enabled to determine at least one data retrieval parameter indicated in the apportionment rule, such as a data format, a data size and data type of the data to be retrieved from each one of the plurality of data sources, such as data sources 120, according torequest 122. Theprocessing device 106 may then interrogate each one of data sources 120 for data indicative of a first data source state corresponding to the at least one data retrieval parameter. For example, according to some aspects, if the at least one data retrieval parameter comprises a requested data size for each one of first data portion 124-1, second data portion 124-2 and third data portion 124-3, then in response to the interrogation byprocessing device 106 in respect of a current size of data stored at each one of data sources 120, data source 120-1, data source 120-2 and data source 120-3 may each return an interrogation response comprising an indication of a current size of data stored at the respective one of data sources 120. - According to some aspects, if processing
device 106 determines that first data source state conflicts with the apportionment rule of request 122 (e.g., current size of data of any one of data sources 120 conflicts with the respective requested data size), then processingdevice 106 may generate and transmitalert data 126 for receipt by computingdevice 110 viasecure network 112.Alert data 126 may comprise an alert message for display at a Graphical User Interface (GUI) ofcomputing system 110. According to some aspects,processing device 106 may wait foralert response data 128 fromcomputing device 110 indicative of a response toalert data 126 before proceeding to retrieve data from data sources 120. In some aspects,alert response data 128 comprises a revised request to retrieve and consolidate data from data sources 120. - According to some aspects, after retrieving the requested data (e.g., first data portion 124-1, second data portion 124-2 and third data portion 124-3),
processing device 106 is enabled to determine a second data source state of each one of data sources 120 associated with firstentity computing system 100. According to some aspects,processing device 106 stores the determined second data source state of each one of data sources 120 associated with firstentity computing system 100 atmemory 104 or another suitable device, module or data source. For example, according to some aspects, at least one reconciliation data source, such asreconciliation data source 130, may be accessible to firstentity computing system 100 such thatprocessing device 106 is enabled to store data indicative of the determined second data source state and/or state change data indicative of any changes between the first data source state and the second data source state for one or more of data sources 120 inreconciliation data source 130. According to some aspects,reconciliation data source 130 comprises one or more of a data structure, a database, a data storage device and a data file. -
Processing device 106 is enabled to store the retrieved data, first data portion 124-1, second data portion 124-2 and third data portion 124-3 in the present non-limiting aspect, inconsolidated data source 132.Consolidated data source 132 comprises any suitable type of data source or combination thereof. According to some aspects,consolidated data source 132 comprises one or more of a data structure, a database, a data storage device and a data file. Althoughconsolidated data source 132 is depicted as a data source separate from data sources 120 andreconciliation data source 130, according to some aspects one or more of data sources 120 andreconciliation data source 130 comprise consolidated data source 132 (or data to be stored in consolidated data source). According to some aspects, data to be stored atconsolidated data source 132 is stored at a data source that may also store other data. For example, according to some aspects, at least one of data source 120-1, data source 120-2 and data source 120-3 comprises consolidated data source 132 (or data stored in consolidated data source). -
Processing device 106 is enabled to transmit, via secureintermediary network 134, one of theconsolidated data source 132 or data stored in theconsolidated source 132 for receipt by secondentity computing system 102 according to any suitable protocol which is compatible with secureintermediary network 134. Non-limiting examples of suitable protocols compatible with secureintermediary network 134 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS). Suitable communication protocols for secureintermediary network 134 may be based on or dictated by, for example, the type of data being transmitted between firstentity computing system 100 and secondentity computing system 102, the type of entity associated with either firstentity computing system 100 or secondentity computing system 102, system requirements or data transmission policies of firstentity computing system 100 and secondentity computing system 102, and/or policies of a relevant governmental authority. According to some aspects, one of theconsolidated data source 132 or data stored in theconsolidated source 132 is transmitted viacommunication module 114, or other computing module of firstentity computing system 100 suitable for transmitting one of theconsolidated data source 132 or data stored in theconsolidated source 132 via secureintermediary network 134. - First
entity computing system 100 and secondentity computing system 102 communicate with each other via secureintermediary network 134 usingcommunication links Communication links - Attention is directed to
FIG. 2 , which depicts a firstentity computing system 200 for retrieving and consolidating data associated with a plurality of records for transmission to secondentity computing system 102, according to another exemplary aspect of the application and in which like or similar elements are denoted by like or similar numbers inFIG. 1 . For simplicity and ease of understanding, discussion of the systems and devices depicted inFIG. 2 will focus on certain similarities and differences from those depicted inFIG. 1 . - Similar to first
entity computing system 100, firstentity computing system 200 comprisesmemory 104 coupled toprocessing device 106.Memory 104 stores computer-executable instructions 208 which is similar to computer-executable instructions 108, aside from the differences described further below. Firstentity computing system 200 is also enabled to access a plurality of data sources 120 associated with a plurality of records. - However, first
entity computing system 200 is also enabled to communicate with a computing system associated with a third entity, such as thirdentity computing system 240, via secureintermediary network 242 according to any protocol compatible with second secureintermediary network 242 and suitable for communications between firstentity computing system 200 and thirdentity computing system 240. According to some aspects, the communication protocols for second secureintermediary network 242 may be similar to the communication protocols for secureintermediary network 134. Communications between firstentity computing system 200 and thirdentity computing system 240 via second secureintermediary network 242 utilizecommunication links Communication links - According to some aspects, third
entity computing system 240 is enabled to communicate with firstentity computing system 200 via secureintermediary network 134 and/or second secureintermediary network 242. - Third
entity computing system 240 is associated with third entity system record(s) (not shown). The third entity system record(s) is associated with at least one corresponding third entity data source, such as corresponding thirdentity data source 248, that is accessible and/or controlled by thirdentity computing system 240. In other words, thirdentity computing system 240 is configured to access the third entity system record and corresponding third entity system data source(s) 248. To be understood, corresponding third entity system data source(s) 248 is not accessible to or controlled by firstentity computing system 200. - Similarly to first
entity computing system 100,processing device 106 of firstentity computing system 200 is enabled to receive, from computingdevice 110 viasecure network 112, requests to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records in accordance with computer-executable instructions stored atmemory 104. In accordance with computer-executable instructions 208,processing device 106 may be enabled to receiverequest 222 fromcomputing device 110 to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records, in which at least one of the plurality of records includes a third entity system record and at least one of the plurality of data sources includes a corresponding third entity system data source, such as third entity system data source(s) 248. - Similarly to request 122,
request 222 comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources, such as data source 120-1, data source 120-2, data source 120-3 and corresponding thirdentity data source 248, and consolidated for transmission to secondentity computing system 102.Processing device 106 is also enabled to, in accordance with computer-executable instructions 208, to determine which of the plurality of records and the plurality of data sources is associated with firstentity computing system 200 in a manner similar to that described in reference to firstentity computing system 100 and computer-executable instructions 108. According to some aspects of the application,processing device 106 is enabled to, in accordance with computer-executable instructions 208, to determine which of the plurality of records and the plurality of data sources is associated with third entity system record(s) and corresponding third entity system data source(s) 248. According to some aspects,request 222 may comprise an indication that one or more portions of the data to be retrieved from the plurality of data sources, data source 120-1, data source 120-2, data source 120-3 and corresponding thirdentity data source 248, is associated with third entity records(s) and/or corresponding thirdentity data source 248. In some aspects, the apportionment rule comprises such an indication. - For example, the apportionment rule of
request 222 may indicate that first data portion 124-1 is to be retrieved from data source 120-1, second data portion 124-2 is to be retrieved from data source 120-2, third data portion 124-3 is to be retrieved from data source 120-3 and afourth data portion 250 is to be retrieved from thirdentity computing system 240 and/or corresponding thirdentity data source 248. - Since corresponding third
entity data source 248 is inaccessible or otherwise outside the control of firstentity computing system 200, firstentity computing system 200 must requestfourth data portion 250 from thirdentity computing system 240.Processing device 106 is enabled to, according to computer-executable instructions 208, generate a first entity data request 252 comprising authentication data and data indicative ofrequest 222 in respect of third entity system record(s) and third entity record(s) and/or corresponding third entitysystem data source 248. The authentication data comprises any data suitable for authenticatingrequest 222 to thirdentity computing system 240 in respect of the third entity. According to some aspects, the authentication data may comprise credentials associated withcomputing device 110, a profile associated withcomputing device 110 and/or received by a suitable input device ofcomputing device 110 that are associated with at least one of the third entity system record(s) and corresponding third entitysystem data source 248. - According to computer-
executable instructions 208,processing device 106 is enabled to transmit first entity data request 252 via second secureintermediary network 242 for receipt by thirdentity computing system 240.Processing device 106 is also enabled to receive, from thirdentity computing system 240 via second secureintermediary network 242, third entity data of corresponding third entity system data source 248 responsive to firstentity data request 252, such asfourth data portion 250.Processing device 106 is further enabled to store the third entity data of corresponding third entitysystem data source 248,fourth data portion 250 in the present example, inconsolidated data source 132 such that the consolidated data source comprises the data retrieved from data sources 120 (associated with first entity computing system 200) and the third entity data, such asfourth data portion 250. - Similarly to
first entity system 100,processing device 106 of the exemplary aspect depicted inFIG. 2 is enabled to transmit, via secureintermediary network 134, one of theconsolidated data source 132 or data stored in theconsolidated source 132 for receipt by secondentity computing system 102. - Attention is now directed to
FIGS. 3 and 4 which depict a flowchart of amethod 300 of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application. In order to assist in the explanation ofmethod 300, it will be assumed thatmethod 300 is performed using either firstentity computing system 100 or firstentity computing system 200, as indicated. Furthermore, the following discussion ofmethod 300 will lead to a further understanding of firstentity computing system 100 and firstentity computing system 200, and the various components of those systems. However, it is to be understood that firstentity computing system 100, firstentity computing system 200 and/ormethod 300 can be varied, and need not work exactly as discussed herein in conjunction with each other, and that such variations are within the scope of present implementations. - It is appreciated that, in some aspects,
method 300 is implemented by firstentity computing system 100 or firstentity computing system 200 by processingdevice 106. Indeed,method 300 is one way in which firstentity computing system 100 or firstentity computing system 200 may be configured. It is to be emphasized, however, thatmethod 300 need not be performed in the exact sequence as shown, unless otherwise indicated; and likewise various blocks may be performed in parallel rather than in sequence; hence the elements ofmethod 300 are referred to herein as “blocks” rather than “steps”. It is also to be understood, however, thatmethod 300 can be implemented on variations of firstentity computing system 100 andfirst computing system 200 as well. - At
block 302, at least one processing device of firstentity computing system 100 or firstentity computing system 200, such asprocessing device 106, receives at least one request, such asrequest 122 orrequest 222, to retrieve and consolidate data from a plurality of data sources associated with a plurality of records. As discussed above, according to some aspects, the plurality of data records may be associated with data sources 120. According to some aspects, the plurality of data records may be associated with data sources 120 anddata source 248. - The request(s) to retrieve and consolidate data comprises an apportionment rule that indicates data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system, such as second
entity computing system 102. - At
block 304, the at least one processing device, such asprocessing device 106, determines which of the plurality of records and plurality of data sources is associated with the first entity computing system. According to some aspects,processing device 106 determines that data sources 120 (data source 120-1, data source 120-2 and data source 120-3) are associated with the firstentity computing system 100. - As discussed above, according to some aspects, at least one of the plurality of records may be a third entity system record and at least one of the plurality of data sources is a corresponding third entity system data source, such as corresponding third entity
system data source 248. Referring toFIG. 4 , atblock 306, in respect of each third entity system record,processing device 106 generates a first entity data request, such as firstentity data request 252, comprising authentication data and data indicative of the at least one request, such asrequest 222, in respect of the third entity system record and corresponding third entity system data source, such as corresponding third entitysystem data source 248. - At
block 308, in respect of each third entity system record, the at least one processing device, such asprocessing device 106, transmits the first entity data request, such as firstentity data request 252, for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, such as thirdentity computing system 240 configured to access corresponding third entitysystem data source 248. According to some aspects, firstentity data request 252 is transmitted via second secureintermediary network 242. According to some aspects, as discussed above, thirdentity computing system 240 is configured to communicate with firstentity computing system 200 via secureintermediary network 134, and firstentity data request 252 is transmitted via secureintermediary network 134. - At
block 310, in respect of each third entity system record, the at least one processing device, such asprocessing device 106, receives third entity data of the corresponding third entity system data source responsive to the first entity data request. For example, according to some aspects,processing device 106 receivesfourth data portion 250 of corresponding third entitysystem data source 248, which is responsive to firstentity data request 252. According to some aspects,processing device 106 receives third entity data via second secureintermediary network 242. According to some aspects,processing device 106 receives the third entity data, such asfourth data portion 250, via secureintermediary network 134. - At
block 312, the at least one processing device, such asprocessing device 106, stores the third entity data in a consolidated data source. For example, according to some aspects,processing device 106 storesfourth data portion 250 inconsolidated data source 132. - Referring to
FIG. 3 , atblock 314, the at least one processing device retrieves data according to the apportionment rule in respect of data sources associated with the first entity computing system. For example, according to some aspects,processing device 106 retrieves first data portion 124-1, second data portion 124-2 and third data portion 124-3 from data source 120-1, data source 120-2 and data source 120-3, respectively. - At
block 316, the at least one processing device stores the data retrieved in accordance with the apportionment rule in a consolidated data source. For example, according to some aspects,processing device 106 stores first data portion 124-1, second data portion 124-2 and third data portion 124-3 inconsolidated data source 132. For example, according to some aspects,processing device 106 stores first data portion 124-1, second data portion 124-3, third data portion 124-3 andfourth data portion 250 atconsolidated data source 132 such that the data stored at consolidated data source comprises data retrieved from data sources 120 and third entitysystem data source 248. - At
block 318, at least one processing device transmits, via the secure intermediary network, one of the consolidated data source and the data stored in the consolidated data source for receipt by the second entity computing system. For example, according to some aspects,processing device 106 transmits first data portion 124-1, second data portion 124-2 and third data portion 124-3. For example, according to some aspects,processing device 106 transmits first data portion 124-1, second data portion 124-3, third data portion 124-3 andfourth data portion 250. - According to some aspects, the at least one processing device transmits one of the consolidated data source and the data stored in the consolidated data source to an intermediary module enabled to transmit data, via the secure intermediary network, from the first entity computing system for receipt by the second entity computing system. According to some aspects, the intermediary module may perform additional processing to the consolidated data source or data stored in the consolidated data source prior to transmission via the secure intermediary network for receipt by the second entity computing system. Such additional processing may, according to some aspects, be performed to enhance the suitability of the data to be transmitted via the secure intermediary network for receipt by the second entity computing system. By way of non-limiting example, the additional processing may comprise one or more of encryption and compression. For example, according to some aspects,
communication module 114 is enabled to transmit data, via the secureintermediary network 134, for receipt by secondentity computing system 102. According to some related aspects,processing device 106 transmits one of theconsolidated data source 132 and the data stored in theconsolidated data source 132 tocommunication module 114, which transmits the received one of theconsolidated data source 132 and the data stored in theconsolidated data source 132 via secureintermediary network 134. According to some related aspects,communication module 114 comprises at least one processing device suitable configured to carry out such communication tasks. - The systems, devices and methods described herein are applicable in a variety of contexts in which management of data transmission between multiple computing systems associated with multiple separate entities is to be performed. As such, it is understood that the aspects described below are non-limiting and that the technical advantages of the described systems, devices and methods may be realized in a variety of data management contexts and applications.
- Referring to
FIGS. 1 and 2 , according to some aspects, firstentity computing system 100 and firstentity computing system 200 are computing system(s) operated by a financial institution, such as a bank, and secondentity computing system 102 is a computing system operated by an entity separate from the financial institution, such as a merchant, utility provider or government entity, and which issues at least one invoice for payment by a user with access to or who is otherwise associated with computing device 110 (also referred to herein as an “issuing entity”). - According to some aspects,
request 122 andrequest 222 are in respect of payment of an invoice associated with the secondentity computing system 102. The payment of the invoice is comprised of funds from each one of the plurality of transaction accounts according to the respective apportionment rule. As discussed above,request 122 andrequest 222 each comprise a request to retrieve and consolidate data from a plurality of data sources associated with a plurality of records. According to some aspects, each one of the plurality of records comprises a transaction account, such as a debit card, a credit card account, a checking account and a line of credit account, and each one of the data sources is associated with each transaction account provided by the first entity, such as data source 120. For example, according to some aspects, data source 120-1 is associated with a debit card account, data source 120-2 is associated with a credit card account and data source 120-3 is associated with a checking account associated with the first entity and which are transaction accounts held by a user with access to or who otherwise associated withcomputing device 110. - According to some aspects, at least one of the transaction accounts is associated with a third entity. For example, according to some aspects, third
entity computing system 240 is operated by another financial institution, separate from the financial institution of the first entity, and corresponding third entitysystem data source 248 is associated with a line of credit provided to the user by the other financial institution. - The data indicated by
request 122 andrequest 222 to be retrieved from the transaction account(s) according to the apportionment rule comprises funds associated with each transaction account indicated in the respective request. The apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction account(s). For example, in respect ofrequest 122, the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided only by the first entity, such as the debit card account associated with data source 120-1, the credit card account associated with data source 120-2 and the checking account associated with data source 120-3. As another example, in respect ofrequest 222, the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided by both the first entity and the second entity, such as the debit card account associated with data source 120-1, the credit card account associated with data source 120-2, the checking account associated with data source 120-3 and the line of credit associated with corresponding third entitysystem data source 248. Additionally, the apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction accounts indicated inrequest 122 orrequest 222. - According to some aspects, the data retrieved in accordance with the apportionment rule comprises funds to be retrieved from the transaction accounts associated with the first
entity computing system 100, firstentity computing system 200 and, in respect of the apportionment rule ofrequest 222, also comprises funds to be retrieved from the transaction account(s) associated with the third entity computing system 240 (also referred to herein as “third entity funds”). In respect ofrequest 222, since the funds to be retrieved from the transaction account(s) associated with corresponding third entitysystem data source 248 are to be retrieved from an entity computing system separate from firstentity computing system 200, the third entity data provided in response to the firstentity data request 252, such asfourth data portion 250, comprises funds from the third entity transaction account transferred by Electronic Funds Transfer (ETF), such as Direct Deposit and/or Interac™ e-transfer, or any other suitable manner of transferring the third entity funds for receipt by firstentity computing system 200. - According to some aspects, storing the retrieved data and/or the third entity data in a consolidated data source comprises storing the funds retrieved from the transaction account(s) according to the apportionment rule in a consolidated transaction account, such as in least one consolidated transaction account associated with
consolidated data source 132. According to some aspects,consolidated data source 132, and the at least one consolidated transaction account, is not a separate data source or transaction account, but comprises a portion or subset of another data source or transaction account. For example, according to some aspects, funds that are to be stored in the at least one consolidated transaction account as described above are stored in a central account of the first entity or a ledger account associated with treasury funds of the first entity. In other words, according to some aspects, the data to be stored at consolidated data source 132 (e.g., the retrieved data and/or the third entity data) and the funds to be stored in the at least one consolidated transaction account (e.g., the retrieved funds and/or the third entity funds) are stored in at least one other data source or transaction account operated by the first entity that is not necessarily dedicated to only storing the retrieved data and/or the third entity data or the retrieved funds and/or third entity funds. According to some related aspects, the retrieved data and/or the third entity data, or the retrieved funds and/or third entity funds, are stored with an indication that the data or funds are to be transmitted or transferred as a consolidated payment or a consolidated data transmission (e.g., single data packet). - According to some aspects, the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and/or third entity funds from the consolidated transaction account to the second entity computing system by ETF, or other any other suitable manner of transferring the retrieved funds and/or third entity funds for receipt by second
computing entity system 102. For example, in respect ofrequest 122, first data portion 124-1, second data portion 124-2 and third data portion 124-3 comprise funds retrieved in accordance with the apportionment rule and stored at a consolidation transaction account associated withconsolidated data source 132. Transmitting first data portion 124-1, second data portion 124-2 and third data portion 124-3 viasecure network 134 for receipt by secondentity computing system 102 may comprise transferring funds from the consolidated transaction account(s) to secondentity computing system 102 by ETF. - As discussed above, one of the
consolidated data source 132 or data stored in theconsolidated source 132 may be transmitted viacommunication module 114, or another suitable computing module of firstentity computing system 100, for receipt by secondentity computing system 102 via secureintermediary network 134. According to some aspects,communication module 114, or the other suitable computing module described above, may comprise a payment module enabled to process and transmit data in respect of payments of invoices from an issuing entity via secureintermediary network 134. - According to some aspects, at least one of secure
intermediary network 134 and second secureintermediary network 242 is a payment network that may be enabled to transmit data associated with payments to secondentity computing system 102. For example, at least one of secureintermediary network 134 and second secureintermediary network 242 may comprise or otherwise be enabled to access an Automated Clearing House (ACH) network or other network(s) suitable and/or specifically enabled to receive, track and/or transmit data associated with payments. At least one of secureintermediary network 134 and second secureintermediary network 242 may operate in accordance with laws and/or guidelines associated with at least one relevant governmental authority in compliance with which one or more of firstentity computing system 100, firstentity computing system 200 may operate. - As discussed above, according to some aspects,
processing device 106 is enabled to store data indicative of the determined second data source state and/or state change data indicative of any changes between the first data source state and the second data source state for one or more of data sources 120 inreconciliation data source 130. For example, according to some aspects, the first data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120, and the second data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120 after the retrieval of first data portion 124-1, second data portion 124-2 and third data portion 124-3, and the funds associated therewith. According to some aspects, state change data stored atreconciliation data source 130 comprises an indication of changes in the amount of funds available at the transaction account(s) associated with firstentity computing system 100, firstentity computing system 200, which may assist in generating data for a ledger of the first entity. - Those skilled in the art will appreciate that in some implementations, the functionality of first
entity computing system 100, firstentity computing system 200 andmethod 300 can be implemented using pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), etc.), or other related components. In other implementations, the functionality of firstentity computing system 100, firstentity computing system 200 andmethod 300 can be achieved using a computing apparatus that has access to a code memory (not shown) which stores computer-readable program code for operation of the computing apparatus. The computer-readable program code could be stored on a computer readable storage medium which is fixed, tangible and readable directly by these components, (e.g., removable diskette, CD-ROM, ROM, fixed disk, USB drive). Furthermore, it is appreciated that the computer-readable program can be stored as a computer program product comprising a computer usable medium. Further, a persistent storage device can comprise the computer readable program code. It is yet further appreciated that the computer-readable program code and/or computer usable medium can comprise a non-transitory computer-readable program code and/or non-transitory computer usable medium. Alternatively, the computer-readable program code could be stored remotely but transmittable to these components via a modem or other interface device connected to a network (including, without limitation, the Internet) over a transmission medium. The transmission medium can be either a non-mobile medium (e.g., optical and/or digital and/or analog communications lines) or a mobile medium (e.g., microwave, infrared, free-space optical or other transmission schemes) or a combination thereof. - Persons skilled in the art will appreciate that there are yet more alternative aspects and modifications possible, and that the above examples are only illustrations of one or more aspects of the application. The scope, therefore, is only to be limited by the claims appended hereto.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/720,414 US20180095956A1 (en) | 2016-09-30 | 2017-09-29 | System and Method for Retrieving and Consolidating Data According to Apportionment Rules |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662402529P | 2016-09-30 | 2016-09-30 | |
US15/720,414 US20180095956A1 (en) | 2016-09-30 | 2017-09-29 | System and Method for Retrieving and Consolidating Data According to Apportionment Rules |
Publications (1)
Publication Number | Publication Date |
---|---|
US20180095956A1 true US20180095956A1 (en) | 2018-04-05 |
Family
ID=61757075
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/618,524 Active 2038-02-17 US10410017B2 (en) | 2016-09-30 | 2017-06-09 | Device lock bypass on selectable alert |
US15/720,688 Abandoned US20180095857A1 (en) | 2016-09-30 | 2017-09-29 | Devices and Method for Detecting and Addressing Anomalies in Data Retrieval Requests |
US15/720,414 Abandoned US20180095956A1 (en) | 2016-09-30 | 2017-09-29 | System and Method for Retrieving and Consolidating Data According to Apportionment Rules |
US15/720,549 Active 2041-04-01 US11443066B2 (en) | 2016-09-30 | 2017-09-29 | Devices, systems and methods for determining suggested action initiation times for interactions |
US15/720,543 Active 2039-04-21 US11354442B2 (en) | 2016-09-30 | 2017-09-29 | Automatic historical analysis of data exchange |
US15/720,651 Active 2038-07-06 US10846435B2 (en) | 2016-09-30 | 2017-09-29 | Dynamic user interface for data exchange split |
US16/528,715 Active US10936755B2 (en) | 2016-09-30 | 2019-08-01 | Device lock bypass on selectable alert |
US16/900,447 Active 2037-12-28 US11604899B2 (en) | 2016-09-30 | 2020-06-12 | Dynamic user interface for data exchange split |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/618,524 Active 2038-02-17 US10410017B2 (en) | 2016-09-30 | 2017-06-09 | Device lock bypass on selectable alert |
US15/720,688 Abandoned US20180095857A1 (en) | 2016-09-30 | 2017-09-29 | Devices and Method for Detecting and Addressing Anomalies in Data Retrieval Requests |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/720,549 Active 2041-04-01 US11443066B2 (en) | 2016-09-30 | 2017-09-29 | Devices, systems and methods for determining suggested action initiation times for interactions |
US15/720,543 Active 2039-04-21 US11354442B2 (en) | 2016-09-30 | 2017-09-29 | Automatic historical analysis of data exchange |
US15/720,651 Active 2038-07-06 US10846435B2 (en) | 2016-09-30 | 2017-09-29 | Dynamic user interface for data exchange split |
US16/528,715 Active US10936755B2 (en) | 2016-09-30 | 2019-08-01 | Device lock bypass on selectable alert |
US16/900,447 Active 2037-12-28 US11604899B2 (en) | 2016-09-30 | 2020-06-12 | Dynamic user interface for data exchange split |
Country Status (2)
Country | Link |
---|---|
US (8) | US10410017B2 (en) |
CA (6) | CA2970088C (en) |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120124496A1 (en) | 2010-10-20 | 2012-05-17 | Mark Rose | Geographic volume analytics apparatuses, methods and systems |
US10438176B2 (en) | 2011-07-17 | 2019-10-08 | Visa International Service Association | Multiple merchant payment processor platform apparatuses, methods and systems |
US10318941B2 (en) | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
US10096022B2 (en) * | 2011-12-13 | 2018-10-09 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
US9041727B2 (en) | 2012-03-06 | 2015-05-26 | Apple Inc. | User interface tools for selectively applying effects to image |
US9131192B2 (en) * | 2012-03-06 | 2015-09-08 | Apple Inc. | Unified slider control for modifying multiple image properties |
US20130239051A1 (en) | 2012-03-06 | 2013-09-12 | Apple Inc. | Non-destructive editing for a media editing application |
US11216468B2 (en) | 2015-02-08 | 2022-01-04 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
US10185817B2 (en) * | 2016-06-16 | 2019-01-22 | International Business Machines Corporation | Device security via swipe pattern recognition |
US10410017B2 (en) | 2016-09-30 | 2019-09-10 | The Toronto-Dominion Bank | Device lock bypass on selectable alert |
WO2018119302A1 (en) * | 2016-12-23 | 2018-06-28 | Dmitri Boutoussov | Dental system and method |
US10469482B2 (en) * | 2017-09-05 | 2019-11-05 | Masergy Communications, Inc. | Encrypted data retrieval systems and methods to provide access to encrypted data |
US10445422B2 (en) * | 2018-02-09 | 2019-10-15 | Microsoft Technology Licensing, Llc | Identification of sets and manipulation of set data in productivity applications |
US11012319B2 (en) * | 2018-07-24 | 2021-05-18 | International Business Machines Corporation | Entity selection in a visualization of a network graph |
US11610203B2 (en) * | 2018-10-09 | 2023-03-21 | Wells Fargo Bank, N.A. | Value transfer via facial recognition |
US11521247B2 (en) * | 2019-01-22 | 2022-12-06 | Oracle International Corporation | Determining a criticality of an invoice, and presenting information related thereto on a graphical user interface |
JP6879316B2 (en) * | 2019-02-07 | 2021-06-02 | カシオ計算機株式会社 | Information processing equipment, graph display method and program |
CN110347569A (en) * | 2019-06-28 | 2019-10-18 | 浙江吉利控股集团有限公司 | A kind of performance data of server acquisition method and device |
US10963828B2 (en) * | 2019-07-19 | 2021-03-30 | Capital One Services, Llc | Identifying and managing enterprise product availability |
US20210084070A1 (en) * | 2019-09-16 | 2021-03-18 | The Toronto-Dominion Bank | Systems and methods for detecting changes in data access pattern of third-party applications |
KR102451495B1 (en) * | 2019-09-29 | 2022-10-06 | 애플 인크. | Account Management User Interfaces |
USD1018575S1 (en) * | 2019-12-09 | 2024-03-19 | Caterpillar Inc. | Display screen having a graphical user interface |
CN111857458B (en) * | 2020-06-23 | 2023-03-31 | 北京芙睿特无限科技发展有限公司 | Freight order generation method and device, electronic equipment and storage medium |
US11631073B2 (en) | 2020-07-01 | 2023-04-18 | Capital One Services, Llc | Recommendation engine for bill splitting |
US11481101B2 (en) * | 2020-11-13 | 2022-10-25 | Capital One Services, Llc | Presentation and control of user interaction with an arc-shaped user interface element |
US11334293B1 (en) * | 2021-01-28 | 2022-05-17 | EMC IP Holding Company LLC | Facilitating the implementation of cluster counters on lock value blocks in distributed file systems |
US20220342536A1 (en) * | 2021-04-26 | 2022-10-27 | Bushel, Inc. | User interface for adjusting component proportions |
US11762857B2 (en) * | 2022-02-18 | 2023-09-19 | Capital One Services, Llc | Methods and systems for searching data exchanges that comprise information on assets with non-homogenous functionality and non-standardized data descriptions |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120072534A1 (en) * | 2009-04-10 | 2012-03-22 | Research In Motion Limited | Method and System for the Exposure of Simplified Data-Service Facades Through a Context Aware Access Layer |
US20130041796A1 (en) * | 2011-08-08 | 2013-02-14 | Bank Of America Corporation | Application governance process and tool |
US20180060601A1 (en) * | 2016-08-31 | 2018-03-01 | Microsoft Technology Licensing, Llc | Location-based access control of secured resources |
US20190205309A1 (en) * | 2016-08-02 | 2019-07-04 | Hexanika | System and method for collecting, consolidating and processing data |
Family Cites Families (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016870B1 (en) * | 1997-12-02 | 2006-03-21 | Financial Engines | Identifying a recommended portfolio of financial products for an investor based upon financial products that are available to the investor |
US20060074727A1 (en) * | 2000-09-07 | 2006-04-06 | Briere Daniel D | Method and apparatus for collection and dissemination of information over a computer network |
US20020103753A1 (en) * | 2001-01-31 | 2002-08-01 | Michael Schimmel | Charge splitter application |
US20100191602A1 (en) | 2001-06-27 | 2010-07-29 | John Mikkelsen | Mobile banking and payment platform |
US7930248B1 (en) * | 2003-06-30 | 2011-04-19 | Checkfree Corporation | Technique for calculating payee specific time to payment completion |
US7578436B1 (en) | 2004-11-08 | 2009-08-25 | Pisafe, Inc. | Method and apparatus for providing secure document distribution |
US8532628B2 (en) | 2006-06-16 | 2013-09-10 | Fmr Llc | Registering actionable alerts |
EP2103019A4 (en) | 2007-01-09 | 2012-07-11 | Visa Usa Inc | Contactless transaction |
US8910299B2 (en) * | 2008-02-08 | 2014-12-09 | Steven Charles Michalske | Emergency information access on portable electronic devices |
US7840457B2 (en) | 2008-03-24 | 2010-11-23 | Intuit Inc. | System and method for automated transaction splitting |
US20090287603A1 (en) * | 2008-05-15 | 2009-11-19 | Bank Of America Corporation | Actionable Alerts in Corporate Mobile Banking |
US8744959B2 (en) * | 2008-08-13 | 2014-06-03 | Moneygram International, Inc. | Electronic bill payment with variable payment options |
US8352347B2 (en) * | 2008-12-29 | 2013-01-08 | Athenainvest, Inc. | Investment classification and tracking system using diamond ratings |
US9230259B1 (en) | 2009-03-20 | 2016-01-05 | Jpmorgan Chase Bank, N.A. | Systems and methods for mobile ordering and payment |
US8275685B2 (en) * | 2010-01-04 | 2012-09-25 | Bank Of America Corporation | Determining a payment strategy |
US8781963B1 (en) * | 2010-04-16 | 2014-07-15 | Jpmorgan Chase Bank, N.A. | Systems and methods for providing a mobile financial platform |
US20110283241A1 (en) | 2010-05-14 | 2011-11-17 | Google Inc. | Touch Gesture Actions From A Device's Lock Screen |
US8811948B2 (en) | 2010-07-09 | 2014-08-19 | Microsoft Corporation | Above-lock camera access |
US20120214416A1 (en) * | 2011-02-23 | 2012-08-23 | Jonathan Douglas Kent | Methods and apparatuses for communication between devices |
US9606643B2 (en) | 2011-05-02 | 2017-03-28 | Microsoft Technology Licensing, Llc | Extended above the lock-screen experience |
AU2012268312B2 (en) * | 2011-06-05 | 2016-02-18 | Apple Inc. | Systems and methods for displaying notifications received from multiple applications |
US9390414B2 (en) | 2011-09-18 | 2016-07-12 | Google Inc. | One-click offline buying |
GB201119375D0 (en) * | 2011-11-10 | 2011-12-21 | Merburn Ltd | Financial transaction processing system and method |
JP5550630B2 (en) * | 2011-12-28 | 2014-07-16 | 楽天株式会社 | Electronic money server, electronic money processing method, and electronic money processing program |
US20130187753A1 (en) | 2012-01-20 | 2013-07-25 | Research In Motion Limited | Predictive Context-Aware Dynamic Lock Screen |
WO2013165759A1 (en) | 2012-05-04 | 2013-11-07 | Paytel, Inc. | Quick transaction completion using mobile device |
US9052197B2 (en) * | 2012-06-05 | 2015-06-09 | Apple Inc. | Providing navigation instructions while device is in locked mode |
AU2013206449A1 (en) * | 2012-06-20 | 2014-01-16 | Visa International Service Association | Multi-channel remote payment apparatuses, methods and systems |
WO2014159563A1 (en) | 2013-03-13 | 2014-10-02 | University Of Pittsburgh Of The Commonwealth System Of Higher Education | Usage modeling |
US10216266B2 (en) | 2013-03-14 | 2019-02-26 | Qualcomm Incorporated | Systems and methods for device interaction based on a detected gaze |
US9741008B2 (en) * | 2013-05-03 | 2017-08-22 | Consumer Product Recovery And Finance Company, Inc. | Apparatus and method for finding and reporting lost items |
WO2014193824A1 (en) | 2013-05-28 | 2014-12-04 | Pulletikurty Ravi | System having a miniature portable electronic device for command and control of a plurality of wireless devices |
US9645721B2 (en) * | 2013-07-19 | 2017-05-09 | Apple Inc. | Device input modes with corresponding cover configurations |
US20150026057A1 (en) | 2013-07-19 | 2015-01-22 | Bank Of America Corporation | Completing mobile banking transaction with different devices |
US9923953B2 (en) * | 2013-07-31 | 2018-03-20 | Adenda Media Inc. | Extending mobile applications to the lock screen of a mobile device |
JP2016532979A (en) * | 2013-09-09 | 2016-10-20 | ヨードリー,インコーポレーテッド | Joint financial management |
US9898642B2 (en) * | 2013-09-09 | 2018-02-20 | Apple Inc. | Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs |
US9830659B2 (en) * | 2013-10-02 | 2017-11-28 | Retireup, Inc. | Method and system for determining an optimum plan for retirement income |
US9753796B2 (en) | 2013-12-06 | 2017-09-05 | Lookout, Inc. | Distributed monitoring, evaluation, and response for multiple devices |
US10290059B2 (en) * | 2014-01-20 | 2019-05-14 | Fmr Llc | Dynamic portfolio simulator tool apparatuses, methods and systems |
US9317674B2 (en) * | 2014-02-07 | 2016-04-19 | Bank Of America Corporation | User authentication based on fob/indicia scan |
US20150261948A1 (en) | 2014-03-12 | 2015-09-17 | Cognitas Technologies, Inc. | Two-factor authentication methods and systems |
EP3128913B1 (en) | 2014-04-10 | 2019-05-08 | Dexcom, Inc. | Determining a user's urgency index associated with a physiological condition |
US9887949B2 (en) | 2014-05-31 | 2018-02-06 | Apple Inc. | Displaying interactive notifications on touch sensitive devices |
US9589263B2 (en) | 2014-06-27 | 2017-03-07 | Paypal, Inc. | Automatic payment code display system |
WO2016014593A1 (en) * | 2014-07-22 | 2016-01-28 | Viasat, Inc. | Mobile device security monitoring and notification |
EP2980733A1 (en) | 2014-07-31 | 2016-02-03 | Samsung Electronics Co., Ltd | Message service providing device and method of providing content via the same |
US9639888B2 (en) | 2014-09-08 | 2017-05-02 | Adobe Systems Incorporated | Providing interactive notifications for completing online transactions |
US20160117651A1 (en) * | 2014-10-27 | 2016-04-28 | Facebook, Inc. | Facilitating sending and receiving of payments between users in a group |
US20160196419A1 (en) * | 2015-01-06 | 2016-07-07 | Google Inc. | Multi-action lock screen |
US11120110B2 (en) | 2015-01-26 | 2021-09-14 | Microsoft Technology Licensing, Llc. | Authenticating a user with a mobile apparatus |
KR20160099397A (en) | 2015-02-12 | 2016-08-22 | 삼성전자주식회사 | Method and Apparatus for Performing Payment Function in Limited State |
CA2978461C (en) | 2015-03-06 | 2020-10-27 | Mastercard International Incorporated | Secure mobile remote payments |
WO2016179543A1 (en) * | 2015-05-06 | 2016-11-10 | Paydatum Co. | Digital receipt processing and analytics system |
US20160353406A1 (en) | 2015-05-26 | 2016-12-01 | Trumpit, Inc. | Media information sharing between networked mobile devices |
US10200824B2 (en) * | 2015-05-27 | 2019-02-05 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
US20160364600A1 (en) | 2015-06-10 | 2016-12-15 | Microsoft Technology Licensing, Llc | Biometric Gestures |
US10853786B2 (en) | 2015-06-30 | 2020-12-01 | Apple Inc. | Multi-factor identity authentication |
KR20170011181A (en) | 2015-07-21 | 2017-02-02 | 엘지전자 주식회사 | Mobile terminal and paying method using extended display and finger scan thereof |
US20170046496A1 (en) | 2015-08-10 | 2017-02-16 | Social Health Innovations, Inc. | Methods for tracking and responding to mental health changes in a user |
US20170193468A1 (en) * | 2015-12-30 | 2017-07-06 | Paypal, Inc. | Peer-to-peer mobile transaction device |
US10387878B2 (en) * | 2016-02-22 | 2019-08-20 | Bank Of America Corporation | System for tracking transfer of resources in a process data network |
US20170249661A1 (en) * | 2016-02-25 | 2017-08-31 | International Business Machines Corporation | Generating Actionable Information from Customer-Related Data and Customer Labels |
US10410017B2 (en) | 2016-09-30 | 2019-09-10 | The Toronto-Dominion Bank | Device lock bypass on selectable alert |
-
2017
- 2017-06-09 US US15/618,524 patent/US10410017B2/en active Active
- 2017-06-09 CA CA2970088A patent/CA2970088C/en active Active
- 2017-09-29 US US15/720,688 patent/US20180095857A1/en not_active Abandoned
- 2017-09-29 CA CA2993310A patent/CA2993310A1/en active Pending
- 2017-09-29 US US15/720,414 patent/US20180095956A1/en not_active Abandoned
- 2017-09-29 US US15/720,549 patent/US11443066B2/en active Active
- 2017-09-29 CA CA2980841A patent/CA2980841A1/en not_active Abandoned
- 2017-09-29 US US15/720,543 patent/US11354442B2/en active Active
- 2017-09-29 CA CA2980903A patent/CA2980903C/en active Active
- 2017-09-29 CA CA2980881A patent/CA2980881C/en active Active
- 2017-09-29 US US15/720,651 patent/US10846435B2/en active Active
- 2017-09-29 CA CA2980848A patent/CA2980848A1/en not_active Abandoned
-
2019
- 2019-08-01 US US16/528,715 patent/US10936755B2/en active Active
-
2020
- 2020-06-12 US US16/900,447 patent/US11604899B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120072534A1 (en) * | 2009-04-10 | 2012-03-22 | Research In Motion Limited | Method and System for the Exposure of Simplified Data-Service Facades Through a Context Aware Access Layer |
US20130041796A1 (en) * | 2011-08-08 | 2013-02-14 | Bank Of America Corporation | Application governance process and tool |
US20190205309A1 (en) * | 2016-08-02 | 2019-07-04 | Hexanika | System and method for collecting, consolidating and processing data |
US20180060601A1 (en) * | 2016-08-31 | 2018-03-01 | Microsoft Technology Licensing, Llc | Location-based access control of secured resources |
Also Published As
Publication number | Publication date |
---|---|
US20180096036A1 (en) | 2018-04-05 |
US20180096156A1 (en) | 2018-04-05 |
CA2980841A1 (en) | 2018-03-30 |
US10936755B2 (en) | 2021-03-02 |
CA2970088C (en) | 2022-02-08 |
US20180096311A1 (en) | 2018-04-05 |
CA2980903A1 (en) | 2018-03-30 |
US10410017B2 (en) | 2019-09-10 |
US11604899B2 (en) | 2023-03-14 |
CA2970088A1 (en) | 2018-03-30 |
US10846435B2 (en) | 2020-11-24 |
US20200311292A1 (en) | 2020-10-01 |
US11443066B2 (en) | 2022-09-13 |
US20190354707A1 (en) | 2019-11-21 |
US20180095857A1 (en) | 2018-04-05 |
CA2980881A1 (en) | 2018-03-30 |
CA2980848A1 (en) | 2018-03-30 |
US11354442B2 (en) | 2022-06-07 |
US20180096321A1 (en) | 2018-04-05 |
CA2980903C (en) | 2023-06-20 |
CA2993310A1 (en) | 2018-03-30 |
CA2980881C (en) | 2023-04-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20180095956A1 (en) | System and Method for Retrieving and Consolidating Data According to Apportionment Rules | |
AU2021204210B2 (en) | Method and system for validation of hashed data via acceptance frames | |
US20220240086A1 (en) | Identity authentication | |
KR101781522B1 (en) | System and method for using multiple payment accounts using a single payment device | |
US20180068290A1 (en) | Transaction scheme for offline payment | |
WO2018236479A1 (en) | Method and system for indexing consumer enrollment using blockchain | |
US9799029B2 (en) | Securely receiving data input at a computing device without storing the data locally | |
CN104067287B (en) | Method, apparatus, system and machine readable media for data integrity protection | |
US9218479B2 (en) | Method and system for computing code management platform | |
US11316862B1 (en) | Secure authorization of access to user accounts by one or more authorization mechanisms | |
US20140372315A1 (en) | Method and system for managing data and enabling payment transactions between multiple entities | |
US10581814B2 (en) | Re-programmable secure device | |
US11924270B2 (en) | Method and system for transferring data | |
US20210185091A1 (en) | Advanced Security System for Implementation in an Internet of Things (IOT) Blockchain Network | |
CN113034118B (en) | Business auditing method, system, readable storage medium and computer program product | |
US20220222636A1 (en) | User configurable direct transfer system | |
AU2016262692A1 (en) | Using limited life tokens to ensure PCI compliance | |
US20200193449A1 (en) | System and method of authenticating conformity to specification using a distributed ledger | |
CA3125338A1 (en) | Private blockchain ecosystems for enabling secure computing operations | |
US20210217003A1 (en) | System and method for managing merchant terms and conditions applicable to a payment transaction | |
US11429961B2 (en) | Masking a primary account number between a party and a service provider | |
US20160071091A1 (en) | Method and system for real time consumer transaction tracking | |
US11593012B1 (en) | Partial pass-through data transfer system | |
US11695772B1 (en) | System and method for enabling multiple auxiliary use of an access token of a user by another entity to facilitate an action of the user | |
US20210329036A1 (en) | Reconciliation Digital Facilitators in a Distributed Network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: THE TORONTO-DOMINION BANK, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SARIR, NASIM;THOMAS, JOHN WILLIAM;HEATH, SIMONA;AND OTHERS;SIGNING DATES FROM 20171201 TO 20181210;REEL/FRAME:048573/0773 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |