The present invention relates to data communication amongst a system of inter-related communication devices in a distributed communication network and, more specifically, determining which of the inter-related communication devices are associated with an entity, receiving data associated with the communication devices, and performing predictive analysis on the data to predict future resource needs and, subsequently, determine resource acquisition schemes.
Systems for providing communications between and amongst devices are known where inter-related communication devices, often referred to as smart devices, may include communications modules, processors and applications that allow the devices to communicate with one another, and with other devices and/or systems, over a network. Such systems allow the devices to collect and exchange data and are commonly referred to as the Internet-of-Things (IoT).
The following presents a simplified summary of one or more embodiments in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments, nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.
Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatus, systems, computer program products, for predictive analysis of data received from inter-related communication devices, within a distributed communication network (e.g., Internet-of-Things (IoT)), which are determined to be associated with an entity. The predictive analysis resulting in a determination of future resource needs. Based on the predicted future resource needs, the present invention determines a resource acquisition scheme which serves to accommodate the predicted future resource needs.
In specific embodiments of the invention, the inter-related communication devices are determined to be associated with the entity by one of (i) accessing a trusted device list that associates known/authenticated communication devices with users, (ii) determining and accessing a gateway address associated with the entity, and/or (iii) determining and accessing a short-range wireless network (WI-FI® or the like) associated with the entity.
In other embodiments of the invention, data received from inter-related communication devices may identify the devices, such as type, brand, and the like. In such embodiments of the invention, analyzing the data may include analyzing the data to predict future entity resource needs based on the identity of the devices or, in some embodiments, analysis may include determining an entity level or classification for the entity based on the identity of the devices and predicting future entity resource needs based on the entity level/classification.
A system for predictive analysis for resource management defines first embodiments of the invention. The system includes a computer platform having a memory, a processor in communication with the memory, and a network communication device in communication with the processor. The system further includes a resource management module that is stored in the memory and executable by the processor. The resource management module is configured for communicating with a plurality of inter-related communication devices across a distributed communication network. Each of the inter-related communication devices include at least one sensor that captures data and communicates the data via the distributed communication network, in this regard the inter-related communication devices may be referred to as Internet-of-Things (Iot) devices. The resource management module is further configured for determining that one or more of the inter-related communication devices are associated with an entity. Such a determination may be made by (i) accessing a trusted device list that associates one or more of the inter-related communication devices with the entity, (ii) determining a gateway address associated with the entity, or (iii) determining a short-range wireless network associated with the entity.
The resource management module is further configured for, in response to determining that inter-related communication devices are associated with the entity, receiving, at least a portion of, the data communicated from the one or more of the plurality of devices and analyzing the data to predict future entity resource needs. The module is further configured for determining a resource acquisition scheme that accommodates the future entity resource needs.
In specific embodiments of the system, the data that is received from the inter-related communication devices includes data that identifies the devices (e.g., type, brand, model or the like). In such embodiments of the invention, the resource management module may be further configured for analyzing the data to predict future entity resource needs based on the identity of the inter-related communication devices. In other specific embodiments of the system, the resource management module may be further configured for analyzing the data to determine an entity level or classification based on the identity of the inter-related communication devices, and based on the entity level/classification, predict the future entity resource needs.
In further specific embodiments of the system, the data that is received from the inter-related communication devices includes performance data associated with the plurality of devices. In such embodiments of the system, the resource management module may be further configured for analyzing the data to determine at least one of (i) a current state of one or more of the inter-related communication devices, or (ii) a predicted life of one or more of the inter-related communication devices. In such embodiments of the system, the resource management module is further configured for determining the resource acquisition scheme for the future entity resource needs based on the current state and/or the predicted life of the inter-related communication devices.
In other specific embodiments of the system, the data that is received from the inter-related communication devices includes consumption data associated with consumable sub-devices/sub-components associated with the inter-related communication devices. In such embodiments of the system, the resource management module may be further configured for analyzing the consumption data to predict future entity resource needs. In still further embodiments of the system, the data that is received from the inter-related communication devices includes procurement data associated with items or services procured via the inter-related communication devices. In such embodiments of the system, the resource management module may be further configured for analyzing the procurement data to predict future entity resource needs.
In specific embodiments of the system, the resource management module is configured for determining, in real-time or near real-time, the resource acquisition scheme that accommodates the predicted future entity resource needs, and, in response to determining the resource acquisition scheme, electronically communicating the resource acquisition scheme to the entity.
In still further specific embodiments of the system, the resource management module is further configured for analyzing the data to predict future entity resource needs, in which the future entity resource needs are further defined as financial resources needed by the entity in the future. In such embodiments of the system, the resource management module is further configured for determining the resource acquisition scheme that accommodates the future entity resource needs, in which the resource acquisition scheme are one or more offers for financial products that serve to accommodate the financial resources needed by the entity in the future.
A method for predictive analysis for resource management defines second embodiments of the invention. The method includes communicating with a plurality of inter-related communication devices across a distributed communication network. Each of the inter-related communication devices include at least one sensor that captures data and communicates the data via the distributed communication network. The method further includes determining, by a computing device processor, that one or more of the inter-related communication devices are associated with an entity based on at least one of (i) accessing a trusted device list that associates one or more of the inter-related communication devices with the entity (ii) determining a gateway address associated with the entity, or (iii) determining a short-range wireless network associated with the entity.
The method additionally includes, in response to determining that one or more of the inter-related communication devices are associated with the entity, receiving, by a computing device processor, at least a portion of the data associated with the one or more of the plurality of inter-related communication devices and analyzing, by a computing device processor, the data to predict future entity resource needs. The method also includes determining, by a computing device processor, a resource acquisition scheme that accommodates the future entity resource needs.
A computer program product for predictive analysis for resource management including a non-transitory computer-readable storage medium defines third embodiments of the invention. The computer-readable storage medium includes computer-executable instructions for communicating with a plurality of inter-related communication devices across a distributed communication network. Each of the inter-related communication devices include at least one sensor that captures data and communicates the data via the distributed communication network. The instructions further include instructions for determining that one or more of the inter-related communication devices are associated with an entity based on at least one of (i) accessing a trusted device list that associates one or more of the inter-related communication devices with the entity, (ii) determining a gateway address associated with the entity, or (iii) determining a short-range wireless network associated with the entity. In addition, the instructions include instructions for, in response to determining that one or more of the inter-related communication devices are associated with the entity, receiving at least a portion of the data associated with the one or more of the plurality of devices and instructions for analyzing the data to predict future entity resource needs. Moreover, the instructions include instructions for determining a resource acquisition scheme that accommodates the future entity resource needs.
Thus, systems, apparatus, methods, and computer program products herein described in detail below provide for predictive analysis of data received from inter-related communication devices, within a distributed communication network (e.g., Internet-of-Things (IoT)), which are determined to be associated with an entity. The predictive analysis resulting in a determination of future resource needs. Based on the predicted future resource needs, the present invention determines a resource acquisition scheme which serves to accommodate the predicted future resource needs.
The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Having thus described embodiments of the invention in general terms, reference will now be made the accompanying drawings, wherein:
Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.
As will be appreciated by one of skill in the art in view of this disclosure, the present invention may be embodied as an apparatus (e.g., a system, computer program product, and/or other device), a method, or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product comprising a computer-usable storage medium having computer-usable program code/computer-readable instructions embodied in the medium.
Any suitable computer-usable or computer-readable medium may be utilized. The computer usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (e.g., a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires; a tangible medium such as a portable computer diskette, a hard disk, a time-dependent access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other tangible optical or magnetic storage device.
Computer program code/computer-readable instructions for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language such as JAVA, PERL, SMALLTALK, C++ or the like. However, the computer program code/computer-readable instructions for carrying out operations of the invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages.
Embodiments of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods or apparatuses (the term “apparatus” including systems and computer program products). It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the instructions, which execute by the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions, which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention.
In accordance with embodiments of the invention, the term “inter-related communication devices” refers to any “smart device” (i.e., a device or apparatus capable of communicating with and transmitting information or data to and/or receiving information or data from other devices, systems or apparatus over a network, such as the Internet or the like). The inter-related communication device may be for example, but not limited to, a machine such as an automobile, tractor trailer, airplane, manufacturing device, warehouse devices, material handling system, conveyor system, robotics or the like; appliances such as refrigerators, washer/dryers, dish washers, or the like; home entertainment devices or systems such as set top boxes, gaming systems, internet televisions, or the like; home or building systems such as home security systems, utility systems such as electrical, water, plumbing systems and apparatuses such as electric meters, water meters, hot water heaters, gas meters or the like; and personal devices such as mobile telephones, laptops, wearable devices such as internet capable fitness devices, watches, glasses or the like. The list of inter-related communication devices provided herein is not exhaustive such that the inter-related communication device may be any device that includes a communication interface or module, software and/or hardware that allow the device to communicate data and/or information related to the device with other devices and/or systems over a network.
Further, in accordance with embodiments of the invention an “entity” as used herein refers to an individual or a group (i.e., association, business or the like) that has control over, possesses or otherwise owns the inter-related communication devices. In this regard, the entity may possess the inter-related devices within their domicile or their place of association/business. Further, personal devices, such as mobile telephones, laptops, wearable devices or the like may be associated with the entity, such as an individual or one of the individuals associated with the group. Additionally, in accordance with embodiments of the invention a “user” as used herein refers to the group that executes the resource management module. In specific embodiments of the invention, a user may be a financial institution or another entity that provides financial product offers to individual or groups (i.e., businesses or the like).
According to embodiments of the invention described herein, various systems, apparatus, methods, and computer program products are herein described for predictive analysis of data received from inter-related communication devices disposed within a distributed communication network (e.g., Internet-of-Things (IoT)), which are determined to be associated with an entity. The predictive analysis results in a determination of future resource needs. Based on the predicted future resource needs, the present invention determines a resource acquisition scheme which serves to accommodate the predicted future resource needs.
In specific embodiments of the invention, the inter-related communication devices are determined to be associated with the entity by one of (i) accessing a trusted device list that associates known/authenticated communication devices with users, (ii) determining/accessing a gateway address associated with the entity, or (iii) determining/accessing a short-range wireless network (WI-FI® or the like) associated with the entity.
In other embodiments of the invention, the data received from inter-related communication devices may identify the devices, in terms of type, brand, model and the like. In such embodiments analyzing the data may include analyzing the data to predict future entity resource needs based on the identity of the devices or, in some embodiments, analysis may include determining an entity level or classification for the entity based on the identity of the devices and predicting future entity resource needs based on the entity level/classification.
Referring to
As previously discussed, the inter-related communication devices 300 may be devices located within an entity's domicile/residence or place of business, which connect to the distributed communication network 200 via a gateway device 210, otherwise referred to herein as a router device. The connection between the gateway/router 210 and the inter-related communication devices 3001-5 may be wireless, as shown in
In the illustrated embodiment of
Referring to
The apparatus 400 includes a computing platform 402 that can receive and execute algorithms, such as routines, and applications. Computing platform 402 includes memory 404, which may comprise volatile and non-volatile memory, such as read-only and/or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. Further, memory 404 may include one or more flash memory cells, or may be any secondary or tertiary storage device, such as magnetic media, optical media, tape, or soft or hard disk. Moreover, memory 404 may comprise cloud storage, such as provided by a cloud storage service and/or a cloud connection service.
Further, computing platform 402 also includes processor 406, which may be an application-specific integrated circuit (“ASIC”), or other chipset, processor, logic circuit, or other data processing device. Processor 406 or other processor such as ASIC may execute an application programming interface (“API”) 408 that interfaces with any resident programs, such as resources management module 410 and routines, sub-modules associated therewith or the like stored in the memory 404 of the apparatus 400.
Processor 406 includes various processing subsystems (not shown in
Computer platform 402 may additionally include communications module (not shown in
The memory 404 of apparatus 400 stores resources management module 410 which is configured to perform predictive analysis on data 302 received from inter-related communication devices 300 that are determined to be associated with an entity 422 to predict future resource needs 452 of the entity 422 and, based on the predicted future resource needs, determine, and provide to the entity 422, a resource acquisition scheme 462. As shown in
Resource management module 410 includes inter-related computing device association sub-module 420 that is configured to determine which of the inter-related communication devices 300 are associated with an entity 422. It should be noted that while
In specific embodiments of the invention, the entity 422 grants the user (i.e., the party executing or controlling the resource management module 410) rights in executing the resource management module 410 for their benefit. In other words, the entity 422 may provide the user authorization to predict their future resource needs 452 and to determine and provide them with associated resource acquisition scheme(s) 462. In such embodiments of the invention, the user may acquire, over time, a list 424 of trusted inter-related communication devices associated with the entity 422, which the entity 422 has used to communicate with the user (e.g., personal computers used to access the user's website, mobile devices used to call/contact the user or used to execute a user's mobile application or the like). Further, the entity 422 may grant the user general rights over the all data communicated from the inter-related communication devices 300 included on the trusted device list 424, specific rights over entity-specified data communicated from the devices 300 included on the trusted device list 424 and/or specific rights for the resource management module 400 to receive data (i.e., all data, or entity-specified data) from the inter-related communication devices 300 included on the trusted device list 424.
However, the trusted device list 424 may be limited to devices which the entity 422 uses to communicate with the user and, as such may not include all of the inter-related communication devices 300 associated with the entity 422. Thus, in other embodiments of the invention, the inter-related computing device association sub-module 420 may be configured to determine one or more gateways/routers 426 associated with the entity 422 and/or one or more short-range wireless networks 428 associated with the entity 422. Such determination may occur based on network communication received by the user from the entity 422 (e.g., user website communication, user mobile application communication and the like). For example, the entity 422 may communicate with the user via a router/gateway 426 and/or a short-range wireless network 428 at the entity's domicile or place of business. The gateway/router 426 and/or short-range wireless network 428 may be identified/determined based on one or more of a router/gateway identification number, Internet Protocol (IP) address, subnet mask identification number, domain name or the like.
In additional embodiments of the invention, the entity 422 may identify one or more of gateways/routers 426 and/or one or more short-range wireless networks 428 that are associated with the entity 422. In other words, the entity may provide the inter-related computing device association sub-module 420 with identification information (e.g., router/gateway identification number, Internet Protocol (IP) address, subnet mask identification number, domain name or the like) associated with the gateways/routers 426 and/or one or more short-range wireless networks 428 and provide the user access to all or a specified portion of the data 302 that the entity transmits via the gateway(s)/router(s) 426 and/or short-range wireless network(s) 428. In this regard, the inter-related computing device association sub-module 420 may be configured to “ping” or otherwise communicate with the gateway(s)/router(s) 426 and/or short-range wireless network(s) 428 to, at a minimum, determine which devices 300 are connected (i.e., transmitting data) to the distributed communication network and, in some embodiments, based on entity 422 authorization, receive or otherwise access the data 302 that is being transmitted from the inter-related communication devices 300 via the gateway(s)/router(s) 426 and/or short-range wireless network(s) 428. Having access to the gateway(s)/router(s) 426 and/or short-range wireless network(s) 428 not only provides the resource management module 410 with data being transmitted from inter-related communication devices 300 that would not otherwise communicate or transmit data to the entity 422, but also provides for identification and receipt of data from any new inter-related communication devices 300 that an entity 422 acquires or otherwise becomes associated with.
In other embodiments of the invention, the inter-related communication device association sub-module 420 may implement other 429 means to determine which inter-related communication device 300 are associated with the entity 422. In other instances, the entity 422 may configure the device settings of one or more of the inter-related communication devices 300 associated with the entity 422 to transmit data to the user/resource management module 410, thus, obviating the need for the inter-related communication device association sub-module 420 to determine that those inter-related communication devices 300 are associated with the entity 422.
The resources management module 410 further includes data collection sub-module 430 that is configured, in response to identifying/determining which inter-related communication devices 300 are associated with the entity 422, receive data 302 from the inter-related communication devices 300 determined to be associated with the entity 422. In specific embodiments of the invention, the data collection sub-module 430 may be configured to receive the data 302 on an ongoing continuous basis based on the unscheduled or scheduled data transmissions transmitted from the inter-connected communication devices 300. In other embodiments of the invention, the data collection sub-module 430 may be configured to “ping” or otherwise call-out the inter-connected communication devices 300 (and/or the gateway/routers) on an on-demand dynamic basis or a scheduled basis to retrieve specified data from the inter-related communication devices 300 or to access transmission logs stored in the inter-related communication devices 300 or elsewhere in the network to identify and/or retrieve data that has been transmitted.
The data 302 that is received/collected by the data collection sub-module 430 may comprise any data conventionally transmitted by inter-related communications devices 300 that is relevant to subsequent prediction analysis for the purpose of determining future resource needs 452 of the entity 422. In specific embodiments of the invention, the data 302 may include device identification data 432 that identifies the inter-related communications device 300 in terms of device type, device brand, device model or the like. In other embodiments of the invention, the data 302 may include performance data 434 that indicates the performance statistics/attributes associated with the inter-related communications devices 300 and/or sub-components of the inter-related communications device 300. Further, in other embodiments of the invention, the data 302 may include consumption data 436 that indicates a level of the useful life used and/or remaining in a consumable (i.e., replaceable) sub-component/sub-device of the inter-related communications device 300. In still further embodiments of the invention, the data 302 may include procurement data 438 that indicates specifics related to procurements (e.g., transactions for goods or services) conducted by or for the inter-related communications devices 300. The procurements may be related to the inter-related communications device 300 (e.g., procurements for consumable/exhaustible sub-component/sub-device of or related to the inter-related communications device 300), or procurements may be unrelated to the inter-related communications device 300 (e.g., general procurements for any good(s) or service(s) conducted through a personal device, such as a mobile telephone or the like). In addition, any other data 300 transmitted from the inter-related communication devices 300 that is relevant to predicting future resource needs of the entity 422 may be received and utilized by the resource management module 410.
In optional embodiments of the invention, in which the resource management module 410 relies on device identification data 432 to predict future resource needs 452 of the entity 422, the resource management module 410 may further include an entity level/classification sub-module 440 that is configured for determining an entity level/classification 442 for the entity 422 based on the device identification data 432. For example, the types, brands and/or models of inter-related communication devices 300 associated with an entity 422 may indicate an income level, wealth level, receipts/profit level associated with the entity 422, which may equate to a specific entity level/classification 442 for purposes of subsequent determination of predicted future resource needs 452.
Resource management module 410 additionally includes predictive analysis sub-module 450 that is configured for determining predicted future resource needs 452 of an entity 422 based, at least, on the data 302 received from the inter-related communication devices 300 associated with the entity 422. In specific embodiments of the invention, future resource needs may be further defined as future financial resource needs. Predictive analysis sub-module 450 may utilize logic and/or algorithms, for example, heuristic algorithms/logic or the like to predict future resource needs 422 for an entity 422 based on the data 302 received from the inter-related communication devices 300. In specific embodiments of the invention, in which the user has access to other data related to the entity, the user may incorporate other data, besides the data received from the inter-related communication devices 300, into the logical determination of the predicted future resource needs 422. For example, in those embodiments of the invention in which the user is a financial institution and the entity is a customer of the financial institution, the financial institution may rely on customer profile information, and/or customer transaction history data to determine the predicted future resource needs 452 of the entity 422.
In specific embodiments of the invention, in which the data 302 includes device identification data 432, the device identification data 432 may be used to predict future resource needs 452. For example, if the device identification data 432 indicates that the entity is associated with specific high-end/luxury devices, e.g., state-of-the art television, luxury vehicle or the like, the predictive analysis sub-module 450 may be configured to determine that the entity 422 has increased predicted future resource needs, i.e., increased predicted future finance needs 452 based on a propensity for high-end/luxury devices/items. In addition, if the device identification data 432 indicates a model name/number or model year, the predictive analysis sub-module 450 may be configured to determine that the entity 422 has imminent predicted future resource needs if the model or model year indicates that the device/vehicle is early model or early model year.
Additionally, in those embodiments of the invention in which the resource management module 410 includes an entity level/classification sub-module 440, the entity level classification 442 assigned to the entity 422 may define the predicted future resource needs 452 of the entity 422. For example, a higher entity level/classification 442 may equate to a higher/increased predicted future resource needs 452 or the like.
In other specific embodiments of the invention, in which the data 302 includes performance data 434, the performance data 434 may be used to predict future resource needs 452. Specifically, the performance data 452 may be analyzed to determine a current state of an associated inter-related communication device 300 and/or a predicted life for an associated inter-related communication device 300 (i.e., how much longer the device can be used). Thus, for example, if the current state and/or the predicted life indicates that the inter-related communication device 300 will need to be replaced in the near future or indicates a specific time in the future in which replacement will need to occur, the determination of the predicted future resource needs 452 may take into account such data; thereby increasing predicted imminent future resource needs 452 for devices requiring near future replacement and/or accurately scheduling predicted future resource needs 452 to accommodate the specific predicted time in the future in which replacement will need to occur.
In still further specific embodiments of the invention, in which the data 302 includes consumption data 436, the consumption data 436 may be used to predict future resource needs 452. Specifically, the consumption data 436 may be analyzed to determine that a consumable/exhaustible sub-device/sub-component of the inter-related communication device 300 needs replacement or prediction of the time in the future at which the sub-device/sub-component will need replacement. Thus, for example, if the sub-device/sub-component is the air conditioning (A/C) unit or heating unit associated with a smart thermostat, the consumption data 436 may indicate that the A/C or heating unit needs replacing (i.e., has exhausted its useful life) or may indicate a time period in the future at which the A/C or heating unit will need replacement. In such embodiments, the predictive analysis sub-module 450 may take such information into account and increase predicted imminent future resource needs 452 for devices requiring near future replacement and/or accurately scheduling predicted future resource needs 452 to accommodate the specific predicted time in the future in which replacement will need to occur.
Moreover, in other specific embodiments of the invention, in which the data 302 includes procurement data 438 (i.e., transactions conducted by or associated with the inter-related communication devices 300), the procurement data 438 may be used to predict future resource needs 452. Specifically, the predictive analysis sub-module 450 may take into account such information in predicting what other procurements that the entity will make in the future; such as, goods/services that are related to a previous procurement, sub-devices/sub-components of the goods/services that will require replacement in the future, the known useful life of the goods/services in the procurement and the like. As a result, the predictive analysis sub-module 450 may increase (or decrease) predicted future resource needs 452 based on the procurement data.
In addition, resource management module 410 includes resource management sub-module 460 that is configured to determine one or more resource allocation schemes 462 based on the predicted future resource needs 452. In specific embodiments of the invention, the resource allocation schemes 462 comprise specific offers for financial products and/or services that are uniquely tailored for the entity 422 based on the predicted future resource needs 452. In this regard, the resource allocation schemes 462 may be entity-specific as to types of financial products offered to the entity 422 (e.g., short term loan, standard loan, mortgage, re-financing of existing loan or the like) based on the predicted future resource needs 452 of the entity 422. In other embodiments of the invention, the resource allocation schemes 462 may be entity-specific (based on the predicted future resource 452 needs of the entity 442) as to other attributes related to the financial products offered (e.g., amounts, costs, rates and the like) or the timing for making the offers to the entity 422.
Additionally, resource management module 410 may, in optional embodiments, include communication sub-module 470 that is configured for electronically communicating the resource allocation scheme(s) 462 to the entity 422. In specific embodiments of the invention, the determination of the predicted future resource needs 452 and the resource acquisition scheme 462 and the generation and communication of the resource acquisition scheme may occur dynamically, in real-time or near real-time, in relation to receipt of the data 302 by the resource management module 410 from the inter-related communication devices 300.
Referring to
At Event 510, a determination is made that one or more of the inter-related communication devices are associated with an entity (i.e., an individual, group of individuals, organization, business or the like that has a desire to have resources managed). The determination is made based on at least on of (i) accessing a trusted device list that associated one or more known authenticated devices with the entity, (ii) determining a gateway/router device/address associated with the entity, and/or (iii) determining a short-range wireless network associated with the entity. As previously discussed, an entity desiring resource management may grant the user (i.e., the party in control or implementing the resource management module) access to data being transmitted from one or more of the inter-related devices associated with the entity. As such, the entity may provide the user with the identity of the one or more of the inter-related devices or the user may be tasked with determining which devices are associated with the user. In certain embodiments in which the entity and the user have a pre-existing relationship (i.e., such as in those embodiments in which the entity is a customer and the user is a financial institution), the user may have contacted the entity (e.g., website, call center, mobile application and the like) using various different communication devices (e.g., PC, laptop, mobile device and the like). Through proper authentication methods, such devices may become “trusted” devices in terms of their association with the entity. However, an entity may additionally have many other inter-related communication devices that are not used as normal means for communicating with the user (e.g., appliances, control units and the like). In order for the resource management module to receive data from such devices, either the devices have to be configured to send data to the user/resource management module or the resource management module has to be able to have the capability to recognize the presence of such devices and intercept or otherwise receive data transmissions from such devices. In this regard, if the user/resource management module has knowledge of the entity's gateway/router device and/or the short-range wireless network used to communicate with a gateway/router (IP address or the like included in data transmissions or the like), the user/resource management module may be configured to access the gateway/router to determine the data transmissions being routed through the gateway/router and, in some embodiments, intercept or reconfigure the data transmissions at the gateway to include the user/resource management module as a recipient of such data transmissions.
At Event 530, in response to determining that one or more of the inter-related communication devices are associated with the entity, at least a portion of the data being transmitted from such devices is received by the user/resource management module. In certain embodiments, the received data may be limited to identifying the device (in terms of the type of device, the brand, the model or the like). In specific embodiments of the invention, the identification of the devices may result in classifying the entity, for the sake of subsequent prediction of future resource need, based on the identification of the various devices they possess/own/control (e.g., more or higher value devices may equate to a higher entity classification). In other embodiments of the invention, the received data may include performance data, consumption data, procurement data and the like.
At Event 540, the received data is analyzed to predict future resource needs. In specific embodiments of the invention, the predicted future resource needs are predicted future financial resource needs, such as monetary funds that are predicted to be needed by the entity in the future. In alternate embodiments of the invention, in which the user and the entity have a pre-established relationship, other data may be additionally used in predicting future resource needs (e.g., in those embodiments in which the entity is a customer and the user is a business, the other data may include customer profile data, customer transaction history data and the like). In those embodiments in which the received data includes device identification data, the predicted future resource needs may be based on the identification of the devices or the classification/level assigned to the entity based on the identification of the devices. In other embodiments in which the data includes performance data, analyzing the data may include determining a current state of the device and/or a predicted useful remaining life of the device, such that determining the predicted future resource needs is based on the current state of the device(s) and/or the predicted useful remaining life of the device(s). In other embodiments in which the data includes consumption data, analyzing the data may include determining a time period for replacing the consumable sub-component/sub-device, such that determining the predicted future resource needs is based on the time period for replacing the consumable sub-component/device. In other embodiments in which the data includes procurement/transaction data, analyzing the data may include determining the identity of goods/services procured, the rate at which goods/services are procured and/or the cost of good/services procured, such that determining the predicted future resource needs is based on the identity of goods/services procured, the rate at which goods/services are procured and/or the cost of good/services procured.
At Event 550, a resource acquisition scheme is determined for the entity that accommodates the predicted future resource needs of the entity. In specific embodiments in which the resources are financial resources, the resource acquisition scheme may comprise one or more offers for financial products/services that serve to meet the predicted future financial resource needs of the entities. The financial products/services may include, but are not limited to, accounts, loans, mortgages or any other product or service that would serve to accommodate the predicted future financial resource needs of the entity. The offers may be specifically tailored for the entity based on the predicted future financial resource needs of the entity. For example, the terms, rates, amounts, lengths of the products/services may vary based on the predicted financial resource needs of the entity and any other relevant information related to the entity. Moreover, the timing of the offers may vary based on the timing related to the predicted future financial resource needs of the entity (i.e., time periods during which the entity is predicted to need the financial resources). In specific embodiments of the invention, in which one or more of receiving the data, analyzing the data to predict future financial needs and/or determining a resource acquisition scheme occur in real-time or near real-time, the resource acquisition schemes may be communicated to the entity in real-time or near real-time.
Thus, systems, apparatus, methods, and computer program products described above provide for predictive analysis of data received from inter-related communication devices, within a distributed communication network (e.g., Internet-of-Things (IoT)), which are determined to be associated with an entity. The predictive analysis resulting in a determination of future resource needs. Based on the predicted future resource needs, the present invention determines a resource acquisition scheme which serves to accommodate the predicted future resource needs.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible.
Those skilled in the art may appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
Number | Name | Date | Kind |
---|---|---|---|
5377309 | Sonobe et al. | Dec 1994 | A |
5717923 | Dedrick | Feb 1998 | A |
5729746 | Leonard | Mar 1998 | A |
5761648 | Golden et al. | Jun 1998 | A |
5801687 | Peterson et al. | Sep 1998 | A |
5842185 | Chancey et al. | Nov 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5870770 | Wolfe | Feb 1999 | A |
5907830 | Engel et al. | May 1999 | A |
5911135 | Atkins | Jun 1999 | A |
5933811 | Angles et al. | Aug 1999 | A |
6006252 | Wolfe | Dec 1999 | A |
6009411 | Kepecs | Dec 1999 | A |
6009413 | Webber et al. | Dec 1999 | A |
6018627 | Iyengar et al. | Jan 2000 | A |
6038393 | Iyengar et al. | Mar 2000 | A |
6041309 | Laor | Mar 2000 | A |
6055573 | Gardenswartz et al. | Apr 2000 | A |
6076069 | Laor | Jun 2000 | A |
6223163 | Van Luchene | Apr 2001 | B1 |
6263351 | Wolfe | Jul 2001 | B1 |
6282567 | Finch, II et al. | Aug 2001 | B1 |
6292786 | Deaton et al. | Sep 2001 | B1 |
6292813 | Wolfe | Sep 2001 | B1 |
6317718 | Fano | Nov 2001 | B1 |
6321208 | Barnett et al. | Nov 2001 | B1 |
6330543 | Kepecs | Dec 2001 | B1 |
6332126 | Peirce et al. | Dec 2001 | B1 |
6336099 | Barnett et al. | Jan 2002 | B1 |
6336131 | Wolfe | Jan 2002 | B1 |
6341305 | Wolfe | Jan 2002 | B2 |
6349290 | Horowitz et al. | Feb 2002 | B1 |
6385592 | Angles et al. | May 2002 | B1 |
6434534 | Walker et al. | Aug 2002 | B1 |
6493868 | DaSilva et al. | Dec 2002 | B1 |
6505168 | Rothman et al. | Jan 2003 | B1 |
6553563 | Ambrose et al. | Apr 2003 | B2 |
6611814 | Lee et al. | Aug 2003 | B1 |
6615184 | Hicks | Sep 2003 | B1 |
6622174 | Ukita et al. | Sep 2003 | B1 |
6678685 | McGill et al. | Jan 2004 | B2 |
6782370 | Stack | Aug 2004 | B1 |
6829232 | Takeda | Dec 2004 | B1 |
6851107 | Coad et al. | Feb 2005 | B1 |
6853291 | Aisa | Feb 2005 | B1 |
6865429 | Schneider et al. | Mar 2005 | B1 |
6865545 | Epstein et al. | Mar 2005 | B1 |
6906617 | Van der Meulen | Jun 2005 | B1 |
6925444 | McCollom et al. | Aug 2005 | B1 |
6937995 | Kepecs | Aug 2005 | B1 |
7024374 | Day et al. | Apr 2006 | B1 |
7043526 | Wolfe | May 2006 | B1 |
7096193 | Beaudoin et al. | Aug 2006 | B1 |
7099832 | Walker et al. | Aug 2006 | B2 |
7124096 | Dutta et al. | Oct 2006 | B2 |
7127414 | Awadallah et al. | Oct 2006 | B1 |
7127713 | Davis et al. | Oct 2006 | B2 |
7130880 | Burton et al. | Oct 2006 | B1 |
7162443 | Shah | Jan 2007 | B2 |
7181488 | Martin et al. | Feb 2007 | B2 |
7225167 | Hind et al. | May 2007 | B2 |
7231357 | Shanman et al. | Jun 2007 | B1 |
7236942 | Walker et al. | Jun 2007 | B1 |
7246310 | Wolfe | Jul 2007 | B1 |
7249058 | Kim et al. | Jul 2007 | B2 |
7254548 | Tannenbaum | Aug 2007 | B1 |
7257604 | Wolfe | Aug 2007 | B1 |
7299007 | Eskin | Nov 2007 | B2 |
7302429 | Wanker | Nov 2007 | B1 |
7302638 | Wolfe | Nov 2007 | B1 |
7315834 | Martineau et al. | Jan 2008 | B2 |
7324965 | Martineau et al. | Jan 2008 | B2 |
7340419 | Walker et al. | Mar 2008 | B2 |
7356490 | Jacobi et al. | Apr 2008 | B1 |
7386477 | Fano | Jun 2008 | B2 |
7398248 | Phillips et al. | Jul 2008 | B2 |
7412604 | Doyle | Aug 2008 | B1 |
7433874 | Wolfe | Oct 2008 | B1 |
7437712 | Brown et al. | Oct 2008 | B1 |
7464050 | Deaton et al. | Dec 2008 | B1 |
7472088 | Taylor et al. | Dec 2008 | B2 |
7490056 | Nash | Feb 2009 | B2 |
7512551 | Postrel | Mar 2009 | B2 |
7536385 | Wolfe | May 2009 | B1 |
7552080 | Willard et al. | Jun 2009 | B1 |
7578435 | Suk | Aug 2009 | B2 |
7593862 | Mankoff | Sep 2009 | B2 |
7599850 | Laor | Oct 2009 | B1 |
7606736 | Martineau et al. | Oct 2009 | B2 |
7644390 | Khodabandehloo et al. | Jan 2010 | B2 |
7694291 | Chen et al. | Apr 2010 | B2 |
7752606 | Savage | Jul 2010 | B2 |
7761848 | Chaffin | Jul 2010 | B1 |
7860792 | Magruder et al. | Dec 2010 | B1 |
7925579 | Flaxman et al. | Apr 2011 | B1 |
8001519 | Conallen et al. | Aug 2011 | B2 |
8042178 | Fisher et al. | Oct 2011 | B1 |
8234194 | Mele et al. | Jul 2012 | B2 |
8294747 | Weinberg | Oct 2012 | B1 |
8301558 | Marshall et al. | Oct 2012 | B2 |
8316237 | Felsher et al. | Nov 2012 | B1 |
8327351 | Paladino et al. | Dec 2012 | B2 |
8392912 | Davis et al. | Mar 2013 | B2 |
8442894 | Blackhurst et al. | May 2013 | B2 |
8495072 | Kapoor et al. | Jul 2013 | B1 |
8930265 | Blackhurst et al. | Jan 2015 | B2 |
8964113 | Kannermark et al. | Feb 2015 | B2 |
8984113 | Li et al. | Mar 2015 | B2 |
9009828 | Ramsey et al. | Apr 2015 | B1 |
9032077 | Klein | May 2015 | B1 |
9043879 | Reeves | May 2015 | B1 |
9047130 | Chen et al. | Jun 2015 | B2 |
9104189 | Berges Gonzalez et al. | Aug 2015 | B2 |
9106615 | Grossman | Aug 2015 | B2 |
9338181 | Burns et al. | May 2016 | B1 |
9411982 | Dippenaar et al. | Aug 2016 | B1 |
9693296 | Wan | Jun 2017 | B2 |
9743272 | Ogrinz et al. | Aug 2017 | B1 |
9775131 | Winand et al. | Sep 2017 | B2 |
9843624 | Taaghol et al. | Dec 2017 | B1 |
9874923 | Brown et al. | Jan 2018 | B1 |
9946571 | Brown et al. | Apr 2018 | B1 |
20020032626 | DeWolf et al. | Mar 2002 | A1 |
20020049624 | Ravels, Jr. | Apr 2002 | A1 |
20020052803 | Amidhozour et al. | May 2002 | A1 |
20020062249 | Iannacci | May 2002 | A1 |
20020072975 | Steele et al. | Jun 2002 | A1 |
20020091571 | Thomas et al. | Jul 2002 | A1 |
20020114433 | Katou et al. | Aug 2002 | A1 |
20020143564 | Webb et al. | Oct 2002 | A1 |
20020190118 | Davenport et al. | Dec 2002 | A1 |
20030115367 | Ohara | Jun 2003 | A1 |
20030135842 | Frey et al. | Jul 2003 | A1 |
20040010462 | Moon et al. | Jan 2004 | A1 |
20040122736 | Stock et al. | Jun 2004 | A1 |
20040192339 | Wilson et al. | Sep 2004 | A1 |
20040226995 | Smith | Nov 2004 | A1 |
20040230593 | Rudin et al. | Nov 2004 | A1 |
20040249768 | Kontio et al. | Dec 2004 | A1 |
20050015624 | Ginter | Jan 2005 | A1 |
20050018686 | Igarashi | Jan 2005 | A1 |
20050039053 | Walia | Feb 2005 | A1 |
20050075975 | Rosner et al. | Apr 2005 | A1 |
20050128969 | Lee | Jun 2005 | A1 |
20050171845 | Halfman et al. | Aug 2005 | A1 |
20050173517 | Suk et al. | Aug 2005 | A1 |
20050177437 | Ferrier | Aug 2005 | A1 |
20050221842 | Kaneko et al. | Oct 2005 | A1 |
20050286079 | Takagi | Dec 2005 | A1 |
20050288955 | Lewiss-Hachmeister | Dec 2005 | A1 |
20060151598 | Chen et al. | Jul 2006 | A1 |
20060217113 | Rao et al. | Sep 2006 | A1 |
20070005426 | Walker et al. | Jan 2007 | A1 |
20070092114 | Ritter et al. | Apr 2007 | A1 |
20070127470 | Gaedeken et al. | Jun 2007 | A1 |
20070136418 | Wolfe | Jun 2007 | A1 |
20070147320 | Sattari | Jun 2007 | A1 |
20070233899 | Aborn | Oct 2007 | A1 |
20070240102 | Bello et al. | Oct 2007 | A1 |
20070255620 | Tumminaro et al. | Nov 2007 | A1 |
20070260532 | Blake, III | Nov 2007 | A1 |
20070299677 | Maertz | Dec 2007 | A1 |
20080008117 | Alizadeh-Shabdiz | Jan 2008 | A1 |
20080009268 | Ramer et al. | Jan 2008 | A1 |
20080021767 | Benson et al. | Jan 2008 | A1 |
20080040417 | Juncker | Feb 2008 | A1 |
20080091535 | Heiser, II | Apr 2008 | A1 |
20080133336 | Altman et al. | Jun 2008 | A1 |
20080162224 | Coon et al. | Jul 2008 | A1 |
20080162316 | Rampell et al. | Jul 2008 | A1 |
20080192677 | Abusch-Magder et al. | Aug 2008 | A1 |
20080221986 | Soicher et al. | Sep 2008 | A1 |
20080228600 | Treyz et al. | Sep 2008 | A1 |
20080235130 | Malov et al. | Sep 2008 | A1 |
20080249936 | Miller et al. | Oct 2008 | A1 |
20080249941 | Cooper | Oct 2008 | A1 |
20080277465 | Pletz et al. | Nov 2008 | A1 |
20080289009 | Lee | Nov 2008 | A1 |
20080301779 | Garg | Dec 2008 | A1 |
20090006175 | Maertz | Jan 2009 | A1 |
20090043629 | Price | Feb 2009 | A1 |
20090094125 | Killian | Apr 2009 | A1 |
20090122797 | Thubert | May 2009 | A1 |
20090132366 | Lam et al. | May 2009 | A1 |
20090132415 | Davis et al. | May 2009 | A1 |
20090150238 | Marsh et al. | Jun 2009 | A1 |
20090170483 | Barnett et al. | Jul 2009 | A1 |
20090172728 | Shkedi et al. | Jul 2009 | A1 |
20090187436 | Shoen et al. | Jul 2009 | A1 |
20090187543 | Samborn | Jul 2009 | A1 |
20090271265 | Lay et al. | Oct 2009 | A1 |
20090292599 | Rampell et al. | Nov 2009 | A1 |
20090292647 | Porat et al. | Nov 2009 | A1 |
20090299865 | Budgen | Dec 2009 | A1 |
20090313106 | Taylor et al. | Dec 2009 | A1 |
20090316701 | Yoo | Dec 2009 | A1 |
20090319638 | Faith et al. | Dec 2009 | A1 |
20100070525 | Clark | Mar 2010 | A1 |
20100106568 | Grimes | Apr 2010 | A1 |
20100131395 | Allin et al. | May 2010 | A1 |
20100189227 | Mannar et al. | Jul 2010 | A1 |
20100250538 | Richards et al. | Sep 2010 | A1 |
20100274731 | Tsitsis | Oct 2010 | A1 |
20100306763 | Lambert et al. | Dec 2010 | A1 |
20100332251 | Yanak et al. | Dec 2010 | A1 |
20110040785 | Steenberg et al. | Feb 2011 | A1 |
20110087547 | Amaro et al. | Apr 2011 | A1 |
20110103392 | Fan | May 2011 | A1 |
20110116442 | Caldwell | May 2011 | A1 |
20110182280 | Charbit et al. | Jul 2011 | A1 |
20110191149 | Blackhurst et al. | Aug 2011 | A1 |
20110191150 | Blackhurst et al. | Aug 2011 | A1 |
20110191160 | Blackhurst et al. | Aug 2011 | A1 |
20110191173 | Blackhurst et al. | Aug 2011 | A1 |
20110191177 | Blackhurst et al. | Aug 2011 | A1 |
20110191180 | Blackhurst et al. | Aug 2011 | A1 |
20110191181 | Blackhurst et al. | Aug 2011 | A1 |
20110191184 | Blackhurst et al. | Aug 2011 | A1 |
20110191238 | Blackhurst et al. | Aug 2011 | A1 |
20110238499 | Blackhurst et al. | Sep 2011 | A1 |
20110238550 | Reich | Sep 2011 | A1 |
20110270773 | Siekman et al. | Nov 2011 | A1 |
20110302201 | Ogaz | Dec 2011 | A1 |
20120016803 | Tharp | Jan 2012 | A1 |
20120028635 | Borg et al. | Feb 2012 | A1 |
20120030092 | Marshall et al. | Feb 2012 | A1 |
20120180024 | Gonzalez et al. | Jul 2012 | A1 |
20120190386 | Anderson | Jul 2012 | A1 |
20120190455 | Briggs | Jul 2012 | A1 |
20120290230 | Berges Gonzalez et al. | Nov 2012 | A1 |
20130006813 | Carlin et al. | Jan 2013 | A1 |
20130046626 | Grigg | Feb 2013 | A1 |
20130079931 | Wanchoo et al. | Mar 2013 | A1 |
20130096857 | Chakradhar | Apr 2013 | A1 |
20130110621 | Gupta et al. | May 2013 | A1 |
20130132854 | Raleigh et al. | May 2013 | A1 |
20130185558 | Seibert | Jul 2013 | A1 |
20130223340 | Jeong | Aug 2013 | A1 |
20130260682 | Suzuki | Oct 2013 | A1 |
20130298242 | Kumar et al. | Nov 2013 | A1 |
20130307702 | Pal et al. | Nov 2013 | A1 |
20140006529 | Andreoli-Fang | Jan 2014 | A1 |
20140047322 | Kim et al. | Feb 2014 | A1 |
20140068721 | Ong | Mar 2014 | A1 |
20140095666 | Yampanis | Apr 2014 | A1 |
20140115324 | Buer | Apr 2014 | A1 |
20140136623 | Kvache | May 2014 | A1 |
20140226010 | Molin et al. | Aug 2014 | A1 |
20140244834 | Guedalia et al. | Aug 2014 | A1 |
20140278629 | Stephenson et al. | Sep 2014 | A1 |
20140344128 | Nikankin | Nov 2014 | A1 |
20150002271 | Lee et al. | Jan 2015 | A1 |
20150013001 | Lee et al. | Jan 2015 | A1 |
20150043516 | Liu | Feb 2015 | A1 |
20150081837 | Bernier | Mar 2015 | A1 |
20150081860 | Kuehnel | Mar 2015 | A1 |
20150094026 | Martin | Apr 2015 | A1 |
20150094093 | Pierce | Apr 2015 | A1 |
20150095478 | Zuerner | Apr 2015 | A1 |
20150154012 | Wolfram | Jun 2015 | A1 |
20150221039 | Johansson | Aug 2015 | A1 |
20150227406 | Jan et al. | Aug 2015 | A1 |
20150293574 | Ehsan et al. | Oct 2015 | A1 |
20150294553 | Logan et al. | Oct 2015 | A1 |
20150312348 | Lustgarten | Oct 2015 | A1 |
20150327071 | Sharma | Nov 2015 | A1 |
20150358317 | Deutschman et al. | Dec 2015 | A1 |
20160057051 | McAndrew | Feb 2016 | A1 |
20160065628 | Guo et al. | Mar 2016 | A1 |
20160071334 | Johnson et al. | Mar 2016 | A1 |
20160087933 | Johnson et al. | Mar 2016 | A1 |
20160110811 | Siu et al. | Apr 2016 | A1 |
20160132832 | Pinkovezky et al. | May 2016 | A1 |
20160164919 | Satish et al. | Jun 2016 | A1 |
20160205599 | Zhang | Jul 2016 | A1 |
20160210450 | Su | Jul 2016 | A1 |
20160217282 | Vecera et al. | Jul 2016 | A1 |
20160232336 | Pitschel et al. | Aug 2016 | A1 |
20160269411 | Malachi | Sep 2016 | A1 |
20160295410 | Gupta et al. | Oct 2016 | A1 |
20160300201 | Li et al. | Oct 2016 | A1 |
20160328282 | Rogati et al. | Nov 2016 | A1 |
20160337869 | Dai et al. | Nov 2016 | A1 |
20160342982 | Thomas | Nov 2016 | A1 |
20160343078 | Vaidyanathan et al. | Nov 2016 | A1 |
20160367415 | Hayes et al. | Dec 2016 | A1 |
20170003960 | Subramanian et al. | Jan 2017 | A1 |
20170004508 | Mansfield et al. | Jan 2017 | A1 |
20170006135 | Siebel et al. | Jan 2017 | A1 |
20170017354 | Wei | Jan 2017 | A1 |
20170041296 | Ford et al. | Feb 2017 | A1 |
20170061442 | Barlow et al. | Mar 2017 | A1 |
20170076408 | D'Souza | Mar 2017 | A1 |
20170122615 | Tang | May 2017 | A1 |
20170124642 | Barnett | May 2017 | A1 |
20170171513 | Nakamura | Jun 2017 | A1 |
20170178186 | Craft | Jun 2017 | A1 |
20170208079 | Cammarota et al. | Jul 2017 | A1 |
20170208139 | Li et al. | Jul 2017 | A1 |
20170228773 | Takayama | Aug 2017 | A1 |
20170235454 | Selfridge | Aug 2017 | A1 |
20170244618 | DeLuca et al. | Aug 2017 | A1 |
20170256157 | Johan | Sep 2017 | A1 |
20170278133 | Corrado et al. | Sep 2017 | A1 |
20170280459 | Ogrinz | Sep 2017 | A1 |
20170302669 | Chen et al. | Oct 2017 | A1 |
20170323345 | Flowers | Nov 2017 | A1 |
20170332228 | Oda | Nov 2017 | A1 |
20170352071 | Carey | Dec 2017 | A1 |
20170353859 | Idnani | Dec 2017 | A1 |
20170366422 | Castinado et al. | Dec 2017 | A1 |
20170374583 | Ogrinz et al. | Dec 2017 | A1 |
20180007131 | Cohn et al. | Jan 2018 | A1 |
20180295517 | Bicket | Oct 2018 | A1 |
Number | Date | Country |
---|---|---|
104283967 | Jan 2015 | CN |
Entry |
---|
Friedman, Jack P., Dictionary of Business Terms, 2000, Barron's Educational Series, Inc., 3rd edition, 225. |
Guagliardo, Joseph C. et al., “Blockchain: Preparing for Disruption Like Its the 90s”; Mar. 14, 2016, retrieved fr; Mar. 14, 2016, retrieved from http://www.law360.com/articles/77120CVprint?section=ip. |
Guagliardo, Joseph C. et al., “Blockchain: Preparing for Disruption Like Its the 90s”; Mar. 14, 2016, retrieved from http://www.law360.com/articles/77120CVprint?section=ip. |
International Preliminary Report on Patentability (IPRP) dated Jul. 31, 2012 for International Application No. PCT/US2011/022765. |
International Search Report and the Written Opinion of the International Searching Authority dated Mar. 25, 2011 for International Application No. PCT/US11/22781. |
International Search Report and the Written Opinion of the International Searching Authority dated Mar. 25, 2011 for International Application No. PCT/US11/22783. |
International Search Report and the Written Opinion of the International Searching Authority dated Mar. 28, 2011 for International Application No. PCT/US11/22771. |
International Search Report and the Written Opinion of the International Searching Authority dated Mar. 29, 2011 for International Application No. PCT/US11/22779. |
International Search Report and the Written Opinion of the International Searching Authority dated Mar. 29, 2011 for International Application No. PCT/US11/22785. |
International Search Report and the Written Opinion of the International Searching Authority dated Apr. 8, 2011 for International Application No. PCT/US11/22765. |
Number | Date | Country | |
---|---|---|---|
20170374583 A1 | Dec 2017 | US |