With advancements in machine and product development, more and more machines and products are being interconnected via internet channels. The expansion of the internet-of-things to encompass smart systems and devices in home, industrial, and other business contexts raise technical challenges including the need to consolidate and aggregate data across devices associated with the user, the need to control and manage the flow of information from devices to third parties (privacy, filtering, protection), and the need to easily track and refresh a user's inventory of smart devices in a manner that allows key data to remain associated with the user while the user's inventory, device associations, and personal/business associations change over time.
The following presents a simplified summary of one or more embodiments of the invention 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 these and/or other needs by providing an innovative system, method and computer program product for aggregation of machine-initiated resource distribution. Thus fixing the technical challenges within the current network including the need to consolidate and aggregate data across devices associated with the user, the need to control and manage the flow of information from devices to third parties (privacy, filtering, protection), and the need to easily track and refresh a user's inventory of smart devices in a manner that allows key data to remain associated with the user while the user's inventory, device associations, and personal/business associations change over time.
The expansion of smart devices to encompass systems and devices in home, industrial, and other business contexts raise technical challenges that the invention system is capable of addressing. This technical challenges that the system alleviates includes: (1) the need to consolidate and aggregate data across devices associated with the user; (2) the need to control and manage the flow of information from devices to third parties (privacy, filtering, protection); and (3) the need to easily track and refresh a user's inventory of smart devices in a manner that allows key data to remain associated with the user while the user's inventory, device associations, and personal/business associations change over time.
In some embodiments, the technical challenges are solved by the system through the generation and presentation of an interactive portal. The portal may be associated with a trusted entity or financial institution. In this way, as a trusted technology partner, the system can generate a portal and associated interfaces available to a user such that the user can identify and register smart devices, manage passwords, identify and implement user preferences for privacy and identify third parties with whom data can be shared and with whom financial transactions may be performed.
Specific use examples include developing an automation of traditionally human intensive tasks, such as warranty registration and service. In an example embodiment, an owner of a smart device registers the device with the portal, which in turn transmits the information necessary to register a warranty with the manufacturer of the device. When the device transmits data associated with a failure of the device, the portal allows for the user to be notified of the warranty status of the device and/or initiates service of the device covered by the warranty.
In some embodiments, the system selective release of data to different third parties. Similarly, devices registered with the portal can be added to insurance company records, such that when a device is lost or stolen, the device can be recovered and/or an insurance claim can be initiated and paid. The data compilation, aggregation, and correlation made possible by the portal also permits the financial institution to package and market packaged data to third parties, and to acquire data that may not be available to or from public utilities and other entities with information needs. The system also allows a user to authenticate devices to them and authenticate service providers to create authenticated communication and payment channels.
Embodiments of the invention relate to systems, methods, and computer program products for aggregated portal generation of smart devices with limiting communication code, the invention comprising: identifying one or more smart device systems associated with a user; uplinking the one or more smart device systems to the portal and store the one or more smart device systems information in the portal associated with the user; generating communicable linkage with the one or more smart device systems and the portal for receive signals from the one or more smart devices via the communicable linkage; communicating a data packet to the one or more smart device systems and store the data packet on the one or more smart device systems, wherein the data packet includes code preventing or limiting communication transmissions from the one or more smart device systems to third party systems without use of the portal; presenting, to the user, an interactive interface for one or more smart device systems proposals based on triggering event occurrence, wherein the proposals comprise data dissemination and resource allocation requirements; identifying the triggering event occurring; selecting release data from the one or more smart device systems to one or more third party systems based on the triggering event occurrence; and providing resource distribution to the one or more third party systems.
In some embodiments, selective release of data from the one or more smart device systems further comprises releasing a first data packet of information about a smart device system to a first third party system and releasing a different second data packet of information about the smart device system to a second third party system, wherein the data packets are generated based on the type of entity associated with the third party system.
In some embodiments, the triggering event is identified based on a communication from the one or more smart device systems to the portal identifying a maintenance or material requirement for the product associated with the one or more smart device systems.
In some embodiments, the third party is a materials provider, maintenance provider, insurance provider, or warrantee provider providing service to the product associated with the one or more smart device systems.
In some embodiments, identifying one or more smart device systems associated with the user further comprises identifying a geographic location of the project using GPS and identifying transmitting signals associated with smart device systems from within the geographic location.
In some embodiments, the one or more smart device systems further comprise products or machinery with transmitting signals associated with the product or machinery capable of transmitting a status and use of the product or machinery.
In some embodiments, the invention further comprises blocking communication from external sources to the one or more smart device systems and preventing the one or more smart device systems from communicating data to third party systems without portal approval, wherein the portal allows for authentication of third party systems for creation of authenticated communication and resource distribution channels directly from the portal for the one or more smart device systems.
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 to 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 elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein.
A “user” as used herein may refer to any entity or individual associated with a smart system at a home or business. In some embodiments, identities of an individual may include online handles, usernames, aliases, family names, maiden names, nicknames, or the like. For purposes of this invention, the term “user” and “user” may be used interchangeably. Furthermore, as used herein the term “user device” or “mobile device” may refer to mobile phones, personal computing devices, tablet computers, wearable devices, and/or any portable electronic device capable of receiving and/or storing data therein.
As used herein, a “user interface” generally includes a plurality of interface devices and/or software that allow a customer to input commands and data to direct the processing device to execute instructions. For example, the user interface may include a graphical user interface (GUI) or an interface to input computer-executable instructions that direct the processing device to carry out specific functions. Input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users.
A “transaction” or “resource distribution” refers to any communication between a user and the financial institution or other entity monitoring the user's activities to transfer funds for the purchasing or selling of a product. A transaction may refer to a purchase of goods or services, a return of goods or services, a payment transaction, a credit transaction, or other interaction involving a user's account. In the context of a financial institution, a transaction may refer to one or more of: a sale of goods and/or services, initiating an automated teller machine (ATM) or online banking session, an account balance inquiry, a rewards transfer, an account money transfer or withdrawal, opening a bank application on a user's computer or mobile device, a user accessing their e-wallet, or any other interaction involving the user and/or the user's device that is detectable by the financial institution. A transaction may include one or more of the following: renting, selling, and/or leasing goods and/or services (e.g., groceries, stamps, tickets, DVDs, vending machine items, and the like); making payments to creditors (e.g., paying monthly bills; paying federal, state, and/or local taxes; and the like); sending remittances; loading money onto stored value cards (SVCs) and/or prepaid cards; donating to charities; and/or the like.
In some embodiments, smart devices be associated with a network of physical objects such as products, buildings and other items embedded with network connectivity that allow for the objects to collect and exchange data. This exchange allows for objects to be sensed and monitored remotely for maintenance, predictive failures, updates or the like. In this way, creating opportunities for more direct integration of the physical world into computer-based systems, and resulting in improved efficiency, accuracy and economic benefit. When products are augmented with sensors and actuators, the technology allows products to be interoperate within the existing internet infrastructure.
The expansion of smart devices to encompass systems and devices in home, industrial, and other business contexts raise technical challenges that the invention system is capable of addressing. This technical challenges that the system alleviates includes: (1) the need to consolidate and aggregate data across devices associated with the user; (2) the need to control and manage the flow of information from devices to third parties (privacy, filtering, protection); and (3) the need to easily track and refresh a user's inventory of smart devices in a manner that allows key data to remain associated with the user while the user's inventory, device associations, and personal/business associations change over time.
In some embodiments, the technical challenges are solved by the system through the generation and presentation of an interactive portal. The portal may be associated with a trusted entity or financial institution. In this way, as a trusted technology partner, the system can generate a portal and associated interfaces available to a user such that the user can identify and register smart devices, manage passwords, identify and implement user preferences for privacy and identify third parties with whom data can be shared and with whom financial transactions may be performed.
Specific use examples include developing an automation of traditionally human intensive tasks, such as warranty registration and service. In an example embodiment, an owner of a smart device registers the device with the portal, which in turn transmits the information necessary to register a warranty with the manufacturer of the device. When the device transmits data associated with a failure of the device, the portal allows for the user to be notified of the warranty status of the device and/or initiates service of the device covered by the warranty.
In some embodiments, the system selective release of data to different third parties. Similarly, devices registered with the portal can be added to insurance company records, such that when a device is lost or stolen, the device can be recovered and/or an insurance claim can be initiated and paid. The data compilation, aggregation, and correlation made possible by the portal also permits the financial institution to package and market packaged data to third parties, and to acquire data that may not be available to or from public utilities and other entities with information needs. The system also allows a user to authenticate devices to them and authenticate service providers to create authenticated communication and payment channels.
Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for generation a portal for aggregation and activation of machine-initiated resource distribution.
As illustrated in
The network 201 may be a system specific distributive network receiving and distributing specific network feeds and identifying specific network associated triggers. The network 201 may also be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. The network 201 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on the network 201.
In some embodiments, the user 202 is an individual or entity that has one or more smart device systems 208 associated with the user 202, user's home, or user's business. In some embodiments, the user 202 has a user device, such as a mobile phone, tablet, computer, or the like.
The user device 204 comprises computer-readable instructions 220 and data storage 218 stored in the memory device 216, which in one embodiment includes the computer-readable instructions 220 of a user application 222. In some embodiments, the user application 222 allows a user 202 to send and receive communications with the portal system 206.
As further illustrated in
The processing device 248 is operatively coupled to the communication device 246 and the memory device 250. The processing device 248 uses the communication device 246 to communicate with the network 201 and other devices on the network 201, such as, but not limited to the smart device systems 208, the third party server 207, and the user device 204. As such, the communication device 246 generally comprises a modem, server, or other device for communicating with other devices on the network 201.
As further illustrated in
In one embodiment of the portal system 206 the memory device 250 stores a portal application 258. In one embodiment of the invention, the portal application 258 may associate with applications having computer-executable program code that generate and code a tag for implementation onto a product. Furthermore, the portal system 206, using the processing device 248 codes certain communication functions described herein. In one embodiment, the computer-executable program code of an application associated with the portal application 258 may also instruct the processing device 248 to perform certain logic, data processing, and data storing functions of the application.
The processing device 248 is configured to use the communication device 246 to communicate with and ascertain data from one or more smart device systems 208.
In the embodiment illustrated in
As illustrated in
As illustrated in
The smart device systems 208 may generally include a processing device 310 communicably coupled to devices as a memory device 320, output devices 336, input devices 340, a network interface 360, a power source 315, a clock or other timer 350, a camera 370, a positioning system device 375, one or more chips 380, and the like.
The processing device 310 is operatively coupled to the network communication interface 360 and the memory device 320. The smart device may also have a control system for controlling the physical operation of the device. The control system may comprise one or more sensors for detecting operating conditions of the various mechanical and electrical systems that comprise the smart device or of the environment in which the smart device is used. The sensors may communicate with the processing device 310 to provide feedback to the operating systems of the device. The control system may also comprise metering devices for measuring performance characteristics of the smart device. The control system may also comprise controllers such as programmable logic controllers (PLC), proportional integral derivative controllers (PID) or other machine controllers. The smart device may also comprise various electrical, mechanical, hydraulic or other systems that perform various functions of the smart device. These systems may comprise, for example, electrical circuits, motors, compressors, or any system that enables functioning of the smart device
The processing device 310 may include functionality to operate one or more software programs or applications, which may be stored in the memory device 320. For example, the processing device 310 may be capable of operating a connectivity program, such as a web browser application 322. The web browser application 322 may allow for communication with the portal system 206 for providing data about the product for identification of the stage of a project. In this way, the smart device systems 208 may transmit and receive web content, such as, for example, product valuation, location-based content, and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like.
The processing device 310 may also be capable of operating applications, such as a stage application 325 and/or a presentment application 321. The stage application 325 and/or presentment application 321 may be downloaded from a server and stored in the memory device 320 of the smart device systems 208. Alternatively, the stage application 325 and/or presentment application 321 may be pre-installed and stored in a memory in the chip 380.
In such an embodiment, the smart device systems 208 may previously store the stage application 325 and/or presentment application 321 prior to affixing the smart device systems 208 to the product. In this way the stage application 325 and/or presentment application 321 may remain and be stored on the smart device systems 208.
The stage application 325 provides the smart device systems 208 with a determination module for the data that the smart device system 208 should communicate to the portal system 206.
The presentment application 321 provides the smart device systems 208 with communication abilities to present the data to the portal system 206. The presentment application 321 may communicate with the other devices on the network 201 to provide real-time status of the smart device as permitted by the portal system 206 based on triggers and user 202 preferences.
In some embodiments, the smart device systems 208 access one or more databases or datastores (not shown) to search for and/or retrieve information related to the device. In some embodiments, the smart device systems 208 access both a memory and/or datastore local to the smart device systems 208 as well as a datastore remote from the smart device systems 208.
The chip 380 may include the necessary circuitry to provide data gathering and presentation functionality to the smart device systems 208. Generally, the chip 380 will include data storage 371 which may include data associated with the products that the smart device systems 208. The tag chip 380 and/or data storage 371 may be an integrated circuit, a microprocessor, a system-on-a-chip, a microcontroller, or the like. In this way, the chip 308 will included data storage 371 which may include data associated with the presentment application 321.
Of note, while
The processing device 310 may be configured to use the network interface 360 to communicate with one or more other devices on a network 201. In this regard, the network interface 360 may include an antenna 376 operatively coupled to a transmitter 374 and a receiver 372 (together a “transceiver”). The processing device 310 may be configured to provide signals to and receive signals from the transmitter 374 and receiver 372, respectively. The signals may include signaling information in accordance with the air interface standard of the applicable cellular system of the wireless telephone network that may be part of the network 201. In this regard, the smart device systems 208 may be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the smart device systems 208 may be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like. For example, the smart device systems 208 may be configured to operate in accordance with second-generation (2G) wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and/or IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols, and/or the like. The smart device systems 208 may also be configured to operate in accordance with non-cellular communication mechanisms, such as via a wireless local area network (WLAN) or other communication/data networks.
The network interface 360 may also include an application interface 373 in order to allow a user 202 to execute some or all of the above-described processes with respect to the presentment application 321 and/or the chip 380. The application interface 373 may have access to the hardware, e.g., the transceiver, and software previously described with respect to the network interface 360. Furthermore, the application interface 373 may have the ability to connect to and communicate with an external data storage on a separate system within the network 201.
The smart device systems 208 may have an interface that includes user output devices 336 and/or input devices 340. The output devices 336 may include a display 330 (e.g., a liquid crystal display (LCD) or the like) and a speaker 332 or other audio device, which are operatively coupled to the processing device 310. The input devices 340, which may allow the smart device systems 208 to receive data from a user 202, may include any of a number of devices allowing the smart device systems 208 to receive data from a user 202, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s).
The smart device systems 208 may further include a power source 315. Generally, the power source 315 is a device that supplies electrical energy to an electrical load. In some embodiment, power source 315 may convert a form of energy such as solar energy, chemical energy, mechanical energy, or the like to electrical energy. Generally, the power source 315 in a smart device systems 208 may be a battery, such as a lithium battery, a nickel-metal hydride battery, or the like, that is used for powering various circuits, e.g., the transceiver circuit, and other devices that are used to operate the mobile device 204. Alternatively, the power source 315 may be a power adapter that can connect a power supply from a power outlet to the smart device systems 208. In such embodiments, a power adapter may be classified as a power source “in” the smart device systems 208.
The smart device systems 208 may also include a memory device 320 operatively coupled to the processing device 310. As used herein, memory may include any computer readable medium configured to store data, code, or other information. The memory device 320 may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory device 320 may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like.
The memory device 320 may store any of a number of applications or programs which comprise computer-executable instructions/code executed by the processing device 310 to implement the functions of the smart device systems 208 described herein. For example, the memory device 320 may include such applications as a presentment application 321, stage application 325, a web browser application 322, an SMS application 323, an email application 324, or the like.
In some embodiments, the smart device systems 208 may identify the activity or use of the product associated with the smart device system 208. The smart device systems 208 may do this via the positioning system device 375, camera 370, and the like. As such, the smart device systems 208 may identify when the product is being used, how often it is being used, and the like. Furthermore, the smart device systems 208 may identify when maintenance may be required based on an identification of the product and regular maintenance required for that product to be maintained.
As discussed in further detail above with respect to
As such, the smart device systems 208 may communicate information about the status of the device which may aid the portal system 206 in determining the stage of the product lifecycle or the like for resource distribution management. This information communicated may include use of products, machine run time, materials available, communication requirements, maintenance status, resource requirements, third party access, and/or the like.
The portal system 206 may gather the information and data from the various one or more smart device systems 208 in order to trigger identification of any predetermined preferences or triggering events that lead to communication allocation to third parties or purchasing of materials for the product associated with the one or more smart device systems 208.
The portal system 206, once the step completion is identified, may communicate the necessary information to third parties and the user based on need, preferences, or triggering points. In some embodiments, the portal system 206 may communicate to third party servers 207, such as material providers, resource managers for release of resources for continued project development, insurance companies for added or additional insurance requirements based on the completion of the step or the like. Furthermore, the portal system 206 may communicate the step completion to the user device 204 for the user to identify and recognize in real-time the status of the smart device systems 208.
Once the portal has been generated, the process 100 continues by creating a user interface for interaction with the portal. In this way, the user interface may be a user facing interface that may be configured to be readable and presentable onto a user device, such as a mobile phone, tablet, or the like. Furthermore, the portal may receive and translate the format of any preferences the user may implement for his/her associated smart devices via the interface into the portal processing protocol.
Next, as illustrated in block 106, the system may link the smart devices associated with the user in the portal. In this way, the portal may correlate and aggregate the data from the smart devices associated with the user. The portal may aggregate the data, passwords, authentications, and the like required for each smart device operation. Furthermore, the system may, once the smart devices are associated with the portal, prevent the smart devices from external communication without first communicating a request to the portal for the external communication. In this way, the smart devices may not be breached by or be able to transmit data to or from a third party device not authorized, thus providing security for the smart devices and the user.
As illustrated in block 108, the process 100 continues by allowing for user management of all smart devices via the single portal for the user, including allowing preference setting and password protected access to the group of user associated smart devices. In this way, the user may set smart device preferences, the user may set one password for accessing all smart devices, manage the external communication parameters for the smart devices, prevent external communication into the smart devices for data extraction, a single review location for reviewing the status of all smart devices at the portal location, and manage material requirements desired by the smart devices. In this way, the portal provides a single access point for management, maintenance, and signal controlling of all smart devices associated with a user.
Next, as illustrated in block 110, the process continues by preventing transmission of signals from the smart devices to third parties based on preferences. In some embodiments, the preferences may be provided by the system. In other embodiments, the user may input the preferences via a portal interface. The preferences may include trigger events that may trigger the communication from the smart device to the user and/or a third party. This may include a requirement from the smart device for material, maintenance, or the like. The preferences may also include when the smart device may be allowed to transmit or receive signals from a third party and the specific third parties the smart device may communicate with. In some embodiments, the portal may prevent the smart device from receiving any communications from a third party system. In some embodiments, the portal may prevent the smart device from transmitting communications to a third party system. In some embodiments, the portal may limit the smart device from receiving communications from a third party system depending on the type of third party, such as a manufacture of the smart device, material provider for the smart device, maintenance provider for the smart device, asset allocator for the smart device, or the like. In some embodiments, the portal may limit the smart device communication to third party systems depending on the type of third party, such as a manufacture of the smart device, material provider for the smart device, maintenance provider for the smart device, asset allocator for the smart device, or the like.
The process 100 is completed by providing a resource allocation to a third party from the smart devices based on portal recognition and authentication of the third party, as illustrated in block 112. In some embodiments, the system may have a resource account provided by the user for use by the system. In other embodiments, the system itself may generate a token for the payment, where the token is directed from the system and does not have any account or other information about the user. As such, the third party will not see any information about the user purchasing an item from the third party.
In this way, the portal may comprise one or more resource accounts holding resources for purchasing maintenance, materials, or the like for the products associated with the smart devices. As such, the portal may control the distribution of the resources to one or more third parties. The portal, as associated with a financial institution, may recognize approved third parties for resource distribution based on an identification of the third parties that do not or have not misappropriate funds in the past for other financial institution resources. Upon portal recognition of an approved third party and user authentication for resource distribution, the portal may transmit the resource to the third party system.
Next, as illustrated in block 506, the process 500 continues by storing preferences and triggers for the smart device. The preferences may be user or portal directed. The preferences may include which, if any, third parties the smart device may communicate with through the portal. The preferences may include resource allocation preferences, such as when and to which third party the portal may provide resources to for the smart device. Preferences may also include the purchasing of maintenance, materials, or the like required by the product associated with the smart device. In some embodiments, triggers may be user, portal, or smart device selected. The triggers may be times, uses, amounts of material remaining, or the like that may trigger a maintenance request, material purchase request, sale, or the like of a product associated with the smart device. The portal may store these preferences and triggers for each smart device. In some embodiments, the smart devices may communicate the triggering of a trigger event or preference to the portal. In other embodiments, the portal may recognize the preference or triggering event.
Furthermore, the preferences may include a profile of data. In this way, the user may select public, private, protected, semi-private, or the like data and allow the system to allows block or always allow the dissemination of the data based on the data fitting into a profile of data. In this way, the user may identify that one or more private data points, such as social security numbers, account numbers, or the like and allows the user to select this profile of data as never been allowed to be pushed to a third party.
As illustrated in block 508, the process 500 continues by communicating the required activation and implementation processes to third parties. In this way, the portal may communicate the requirements and triggers to third parties. In this way, the portal may communicate the activations and implementation processes to the third party systems for the smart devices. As such, the smart devices may not communicate directly with the third party systems, preventing misappropriation by communication of resources, data, or statistics to unauthorized third parties and prevention of third party unauthorized access of the data on the smart device.
As illustrated in block 510, the process 500 continues by identifying functional or material requirements for the smart device. In this way, the portal may identity the needs of the product associated with the smart device, such as material needs, functional requirements, maintenance needs, or the like. Furthermore, the portal may identify the timing for the requirements and set calendaring for the purchase of the requirements for the products associated with the smart devices. As illustrated in block 512, the process continues by notifying the user of the functional and/or material requirements. The portal may communicate to the user, via the user device, via text message, email, voice communication, or the like. The notification may require user input in order to process the functional or material requirements, such as purchasing the materials with one or more resources. In other embodiments, the portal may automatically purchase the materials with one or more user resources without authorization from the user. Finally, as illustrated in block 514, the process is completed by transmitting the necessary information to a third party for smart device requirement satisfaction. In this way, the portal may provide the information, such as a product type, a material type, or the like to the third party for requirement satisfaction for the product associated with the smart device to be running.
In some embodiments, the portal may provide warranty registration and services. In other examples, the portal may transmit information necessary to register a warranty with the manufacturer of the product. The portal may transmit data associated with the product or failure of the product and notify the user. Furthermore, the portal may provide selective release of data to different third parties. For example, a mechanic may be automatically supplied with a set of pertinent data about the vehicle that is not otherwise public, while the insurance company may be provided with a completely different set of pertinent data. In this way, the portal may determine the pertinent data required by each of the different third parties and provide the pertinent data to the third party upon authorization and necessity.
In some embodiments, the smart device registered with the portal can be added to insurance company records, such that when a product is lost or stolen, the product with the smart device can be recovered and/or an insurance claim can be initiated and paid. The data compilation, aggregation, and correlation made possible by the portal also permits the financial institution to package and market packaged data to third parties, and to acquire data (such as power usage patterns or the like) that may not be available to or from public utilizes and other entities with informational needs. The portal may also allow a user to authenticate the portal to allow for payment rail usage and payment completion via resources.
Next, as illustrated in block 606, the process 600 continues by storing preferences and triggers for the smart device. The preferences may be user or portal directed. The preferences may include which, if any, third parties the smart device may communicate with through the portal. The preferences may include resource allocation preferences, such as when and to which third party the portal may provide resources to for the smart device. Preferences may also include the purchasing of maintenance, materials, or the like required by the product associated with the smart device. In some embodiments, triggers may be user, portal, or smart device selected. The triggers may be times, uses, amounts of material remaining, or the like that may trigger a maintenance request, material purchase request, sale, or the like of a product associated with the smart device. The portal may store these preferences and triggers for each smart device. In some embodiments, the smart devices may communicate the triggering of a trigger event or preference to the portal. In other embodiments, the portal may recognize the preference or triggering event.
Next, as illustrated in block 608, the process 600 continues by generating code to transmit to the smart device to lock the communications of the smart device to third parties. In this way, the portal generates code that may be transmitted to and stored in the smart device that may limit the smart device from communicating with any external device other than the portal. As such, the portal may control the communication, both received and transmitted, from the smart devices. In this way, all smart device data and communications may be transmitted to the portal, which in turn may provide communications to any third parties if necessary based on preferences, triggers, or requirement satisfaction.
As illustrated in block 610, the process 600 continues by identifying the preferences and triggers for communication transmission. As such, the portal may reach out to the user, via portal interface, to receive user preferences and triggers for resource distribution, material purchase, maintenance, or the like. In some embodiments, the portal may determine the preferences and triggers based on the type of product associated with the smart device.
Finally, as illustrated in block 612, the process 600 is completed by communicating the specific data packets to a third party based on the preferences and/or triggering events.
As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, and the like), an entirely hardware embodiment, 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 that includes a computer-readable storage medium having computer-executable program code portions stored therein. As used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more special-purpose circuits perform the functions by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or having one or more application-specific circuits perform the function. As such, once the software and/or hardware of the claimed invention is implemented the computer device and application-specific circuits associated therewith are deemed specialized computer devices capable of improving technology associated with the in authorization and instant integration of a new credit card to digital wallets.
It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random 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), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.
It will also be understood that one or more computer-executable program code portions for carrying out the specialized operations of the present invention may be required on the specialized computer include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.
It will further be understood that some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of systems, methods, and/or computer program products. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a special purpose computer for the authorization and instant integration of credit cards to a digital wallet, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
It will also be understood that the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, and the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.
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 will 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 |
---|---|---|---|
5717923 | Dedrick | Feb 1998 | A |
5761648 | Golden et al. | Jun 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 |
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 |
6505168 | Rothman et al. | Jan 2003 | B1 |
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 |
6865545 | Epstein et al. | Mar 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 |
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 |
7433874 | Wolfe | 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 |
7860792 | Magruder et al. | Dec 2010 | B1 |
7925579 | Flaxman et al. | Apr 2011 | B1 |
8042178 | Fisher et al. | Oct 2011 | B1 |
8234194 | Mele et al. | Jul 2012 | B2 |
8301558 | Marshall et al. | Oct 2012 | B2 |
8442894 | Blackhurst et al. | May 2013 | B2 |
8495072 | Kapoor et al. | Jul 2013 | B1 |
8930265 | Blackhurst et al. | Jan 2015 | B2 |
8984113 | Li et al. | Mar 2015 | B2 |
9009828 | Ramsey et al. | Apr 2015 | B1 |
9032077 | Klein et al. | May 2015 | B1 |
9106615 | Grossman | Aug 2015 | B2 |
9338181 | Burns et al. | May 2016 | B1 |
9411982 | Dippenaar et al. | Aug 2016 | B1 |
9743272 | Ogrinz et al. | Aug 2017 | B1 |
9775131 | Winand et al. | Sep 2017 | B2 |
9843624 | Taaghol | Dec 2017 | 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 |
20040122736 | Strock et al. | Jun 2004 | A1 |
20040192339 | Wilson | Sep 2004 | A1 |
20040226995 | Smith | Nov 2004 | A1 |
20040230593 | Rudin et al. | Nov 2004 | A1 |
20040249768 | Kontio et al. | Dec 2004 | A1 |
20050015624 | Ginter et al. | Jan 2005 | A1 |
20050075975 | Rosner et al. | Apr 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 |
20070127470 | Gaedeken | Jun 2007 | A1 |
20070136418 | Wolfe | Jun 2007 | A1 |
20070255620 | Tumminaro et al. | Nov 2007 | A1 |
20070260532 | Blake, III | Nov 2007 | A1 |
20070299677 | Maertz | Dec 2007 | A1 |
20080009268 | Ramer et al. | Jan 2008 | A1 |
20080021767 | Benson et al. | Jan 2008 | A1 |
20080040417 | Juncker | Feb 2008 | A1 |
20080091535 | Heiser, II et al. | Apr 2008 | A1 |
20080133336 | Altman et al. | Jun 2008 | A1 |
20080162224 | Coon et al. | Jul 2008 | A1 |
20080162316 | Rampell et al. | Jul 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 |
20090006175 | Maertz | Jan 2009 | A1 |
20090043629 | Price | Feb 2009 | A1 |
20090094125 | Killian et al. | Apr 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 |
20090319638 | Faith et al. | Dec 2009 | A1 |
20100106568 | Grimes | Apr 2010 | A1 |
20100131395 | Allin et al. | May 2010 | A1 |
20100250538 | Richards et al. | Sep 2010 | A1 |
20100274731 | Tsitsis | Oct 2010 | A1 |
20100306763 | Lambert et al. | Dec 2010 | A1 |
20110087547 | Amaro et al. | Apr 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 |
20110270773 | Siekman et al. | Nov 2011 | A1 |
20120030092 | Marshall et al. | Feb 2012 | A1 |
20130132854 | Raleigh | May 2013 | A1 |
20130298242 | Kumar et al. | Nov 2013 | A1 |
20140047322 | Kim et al. | Feb 2014 | A1 |
20140115324 | Buer | Apr 2014 | A1 |
20140226010 | Molin | Aug 2014 | A1 |
20140244834 | Guedalia et al. | Aug 2014 | A1 |
20150094026 | Martin | Apr 2015 | A1 |
20150227406 | Jan et al. | Aug 2015 | A1 |
20150358317 | Deutschmann et al. | Dec 2015 | A1 |
20160087933 | Johnson et al. | Mar 2016 | A1 |
20160164919 | Satish et al. | Jun 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 |
20160342982 | Thomas et al. | Nov 2016 | A1 |
20170041296 | Ford et al. | Feb 2017 | A1 |
20170235454 | Selfridge et al. | Aug 2017 | A1 |
20170244618 | DeLuca et al. | Aug 2017 | A1 |
20170278133 | Corrado et al. | Sep 2017 | A1 |
20170366422 | Castinado | Dec 2017 | A1 |
Number | Date | Country |
---|---|---|
104283967 | Jan 2015 | CN |
Entry |
---|
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. |
Friedman, Jack P., Dictionary of Business Terms, 2000, Barron's Educational Series, Inc., 3rd edition, 225. |
Number | Date | Country | |
---|---|---|---|
20170366422 A1 | Dec 2017 | US |