The present invention relates to distribution channel manipulation for distributing resources, and more particularly to improving the processing capability, memory, and processing speed of the systems that are utilized for distributing resources.
Resources are distributed to entities in a number of different ways depending past distributions and/or the convenience of the entities involved. Disparate storage of the resource distributions and the differences in resource distribution for various entities reduce the processing capacity, increase memory requirements, and reduce the processing speed needed to distribute the resources. Improved systems, processes, and computer program products are needed to increase the capacity, reduce memory requirements, and increase the processing speed associated with resource distribution between entities.
The following presents a simplified summary of one or more embodiments of the present 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 of the present invention in a simplified form as a prelude to the more detailed description that is presented later.
Generally, systems, computer products, and methods are also described herein that provide for improving the delivery of resources to a recipient entity (e.g., a business, an individual user, or the like) when the recipient entity is involved in an interaction with a provider entity. The present invention provides one or more application programming interfaces (APIs) that are utilized to identify delivery channels, and potentially substitute an original delivery channel with an alternate delivery channel that is preferred by the recipient entity. The present invention utilizes entity information (e.g., a recipient entity identifier, and/or other entity information), which will be described in further detail later, in order to determine recipient entity delivery preferences from a stored preference or from communications with the recipient entity. After the delivery preferences are determined, the system provides the resources to the recipient entity according to the preferences identified. The present invention provides a more efficient delivery of resources to the recipient entity improving the capacity, memory, and processing speed of the delivery systems and improving the ability to identify the identity of the recipient entity before the resources are delivered to the recipient entity.
Additionally, systems, computer products, and methods are described herein that provide for improved validation of a recipient entity (e.g., a business, an individual user, or the like) when the recipient entity is involved in an interaction with a provider entity. The present invention provides one or more application programming interfaces (APIs) that are utilized to validate the recipient entity. The present invention further utilizes recipient entity information (e.g., a recipient entity identifier, and/or other entity information), and communicates the entity information to the resource systems to more efficiently validate the recipient entity in order to improve the processing capacity, reduce memory requirements, and improve processing speeds for validating the recipient entity for an interaction. Moreover, the present invention provides a more accurate determination of the actual identity of the recipient entity, thus improving the security of the interaction between the entities and reducing the potential for misappropriation of the resources involved in the interactions. The present invention solves at least the technical problems of improving the capacity, memory, and processing speed of the validation systems and improving the ability to identify the identity of the recipient entity.
Embodiments of the invention comprise systems, methods, and computer program products for determining resource distribution channel manipulation. The invention comprises receiving a delivery preference request from a provider entity through one or more application programming interfaces (API) for a delivery channel for providing resources to a recipient entity. The delivery preference request includes recipient entity information, and the request is received through a provider entity computer system. The invention further comprises determining a recipient entity delivery preference for the delivery channel, and sending the resources through the delivery channel according to the recipient entity delivery preference.
In further accord with embodiments of the invention, the delivery preference request for the delivery channel comprises a request for an alternative delivery channel to replace an original delivery channel.
In other embodiments of the invention, a notification is sent to the providing entity with the recipient entity delivery preference for the delivery channel.
In still other embodiments of the invention, the recipient entity delivery preference is determined by accessing a delivery preference database, determining when the recipient entity information meets stored recipient entity information for a stored recipient entity, and determining the recipient entity delivery preference for the stored recipient entity.
In yet other embodiments of the invention, the delivery preference database is controlled by a third-party system.
In further accord with embodiments of the invention, the recipient entity delivery preference is determined by sending a notification to the recipient entity based on the recipient entity information, wherein the notification requests the recipient entity delivery preference, and thereafter receiving the recipient entity delivery preference from the recipient entity.
In other embodiments of the invention, the original delivery channel is a physical resource delivery and wherein the alternative delivery channel is a digital resource pool delivery.
In still other embodiments of the invention, the invention further comprises receiving a resource delivery request from the provider entity through the one or more APIs to deliver the resources to a resource pool of the recipient entity, wherein the resource delivery request includes the recipient entity information comprising at least a recipient entity identifier, and wherein the resource delivery request is received through the provider entity computer system. The invention further comprises validating the recipient entity using the recipient entity information, including at least the recipient entity identifier. Moreover, sending the resources through the delivery channel comprises sending the resources to the resource pool of the recipient entity when the recipient entity is validated, wherein the resources are delivered by communicating with a resource system.
The yet other embodiments of the invention, validating the recipient entity comprises communicating at least the recipient entity identifier to the resource system, and receiving a validation response from the resource system. The validation response comprises a validation confirmation that the recipient entity is validated when the resource pool of the recipient entity is identified within the resource system, and an indication of multiple resource pools when two or more recipient entities or two or more resource pools for the recipient entity are identified.
In further according with embodiments of the invention, in response to receiving the validation confirmation, the resources are delivered to the resource pool of the recipient entity. Alternatively, in response to receiving the indication of multiple resource pools sending an information request to the providing entity or the recipient entity. The information request comprises a selection of one of the multiple resource pools to deliver the resources, and the information request is sent to the provider entity computer system or a recipient entity computer system.
In other embodiments of the invention, validating the recipient entity comprises accessing a validation database, wherein the validation database comprises stored validations for a plurality of recipient entities comprising stored recipient entity information. The recipient entity information is compared with the stored recipient entity information. The recipient entity is validated when the recipient entity information meets the stored recipient entity information. The recipient entity information is communicated to the resource system when the recipient entity information does not meet the stored recipient entity information.
In still other embodiments of the invention, validating the recipient entity further comprises determining that the recipient entity information meets validation requirements, wherein the validation requirements comprise at least a past validation of the recipient entity within a past time period.
In yet other embodiments of the invention, validating the recipient entity comprises pinging the resource system to determine existence of the resource pool for the recipient entity identifier without having to enter resource validation interactions.
In further according with embodiments of the invention, the recipient entity identifier comprises an electronic communication address or a mobile device number of the recipient entity, and the validation occurs without utilizing a resource pool number of the recipient entity.
In other embodiments of the invention, the recipient entity information further comprises a resource pool entity of the recipient entity, wherein the resource pool entity comprises a digital wallet of the recipient entity.
In yet other embodiments of the invention, the recipient entity information comprises at least a name of the recipient entity and an address of the recipient entity.
To the accomplishment the foregoing and the related ends, the one or more embodiments comprise the features hereinafter described and particularly pointed out in the claims. The following description and the annexed drawings set forth certain illustrative features of the one or more embodiments. These features are indicative, however, of but a few of the various ways in which the principles of various embodiments may be employed, and this description is intended to include all such embodiments and their equivalents.
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, and wherein:
Embodiments of the 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. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It may be evident; however, that such embodiment(s) may be practiced without these specific details. Like numbers refer to like elements throughout.
Systems, methods, and computer program products are herein disclosed that provide for improving the delivery of resources to a recipient entity (e.g., a business, an individual user, or the like) when the recipient entity is involved in an interaction with a provider entity. The present invention provides one or more application programming interfaces (APIs) that are utilized to identify delivery channels, and potentially substitute an original delivery channel with an alternate delivery channel that is preferred by the recipient entity. The present invention utilizes entity information (e.g., a recipient entity identifier, and/or other entity information), which will be described in further detail later, in order to determine recipient entity delivery preferences from a stored preference or from communications with the recipient entity. After the delivery preferences are determine, the system provides the resources to the recipient entity according to the preferences identified. The present invention provides a more efficient delivery of resources to the recipient entity improving the capacity, memory, and processing speed of the delivery systems and improving the ability to identify the identity of the recipient entity and/or the associated resource pool before the resources are delivered to the recipient entity.
Systems, methods, and computer program products are herein further disclosed that provide for improving the validation of a recipient entity (e.g., a business, an individual user, or the like) when the recipient entity is involved in an interaction with a provider entity. The present invention provides one or more application programming interfaces (APIs) that are utilized to validate the recipient entity. The present invention further utilizes recipient entity information (e.g., a recipient entity identifier, and/or other entity information), which will be described in further detail later, and communicates the entity information to the resource systems to more efficiently validate the recipient entity and/or the recipient entity's resource pool in order to improve the processing capacity, reduce memory requirements, and improve processing speeds for validating the recipient entity for an interaction. Moreover, the present invention provides a more accurate determination of the actual identity of the recipient entity, thus improving the security of the interaction between the entities and reducing the potential for misappropriation of the resources involved in the interactions. The present invention solves at least the technical problems of improving the capacity, memory, and processing speed of the validation systems and improving the ability to identify the identity of the recipient entity and/or the associated resource pool.
The organization systems 10 may facilitate interactions between provider entities 6 and recipient entities 4 by communicating with the entity computer systems 20, the digital resource systems 30, the third-party systems 40, and/or other systems through the network 2. The network 2 may 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 2 may provide for wireline, wireless, or a combination of wireline and wireless communication between systems, services, components, and/or devices on the network 2.
As illustrated in
The one or more processing components 14 use the one or more communication components 12 to communicate with the network 2 and other components on the network 2, such as, but not limited to, the components of the one or more entity computer systems 20, the one or more digital resource systems 30, the one or more third-party systems 40, and/or other systems. As such, the one or more communication components 12 generally comprise a wireless transceiver, modem, server, electrical connection, electrical circuit, or other component for communicating with other components on the network 2. The one or more communication components 12 may further include an interface that accepts one or more network interface cards, ports for connection of network components, Universal Serial Bus (USB) connectors and the like.
As further illustrated in
As illustrated in
The one or more processing components 24 are operatively coupled to the one or more communication components 22, the one or more image capture components 25, and the one or more memory components 26. The one or more processing components 24 use the one or more communication components 22 to communicate with the network 2 and other components on the network 2, such as, but not limited to, the organization systems 10, the resource systems 30, the third-party systems 40, and/or other systems. As such, the one or more communication components 22 generally comprise a wireless transceiver, modem, server, electrical connection, or other component for communicating with other components on the network 2. The one or more communication components 22 may further include an interface that accepts one or more network interface cards, ports for connection of network components, Universal Serial Bus (USB) connectors and the like. Moreover, the one or more communication components 22 may include a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer component, button, soft key, and/or other input/output component(s) for communicating with the entities 4, 6.
As illustrated in
As illustrated in
As illustrated in
Moreover, as illustrated in
As illustrated by the one or more APIs 210 (or portions thereof) in
In other embodiments, there may be additional APIs as needed. It should be understood that the one or more APIs 210 allow for the communication between the various systems described herein in a simplified way for all of the entities and organizations regardless of the differences in the systems used by the entities and organizations. Moreover, the one or more APIs 210 (or a portion thereof) may be stored and/or controlled by the organization through the organization systems 10, or the one or more APIs 210 (or a portion thereof) may be stored and/or controlled by a third-party through the third-party systems 40. As such, the validation systems may be a part of the one or more organization systems 10 or may be operated by a third-party system 40 in order to be a universal system for all of the organizations and/or entities.
Block 120 of
As illustrated in
As illustrated by block 130 in
The validation processing entity 220 may access validation requirements 230 in order to determine the recipient entity information needed to validate the recipient entity 4. Depending on the third-party that is responsible for the resources systems 30 that hold the resource pool of the receiving entity 4, each third-party may have different validation requirements. As such, the validation processing engine 220 may determine if the information received in the validation request, or in subsequent communications, is enough to validate the receiving entity 4 through the resource systems 30 based on the validation requirements for each third-party. For example, different resource systems 30 operated by different third-parties (e.g., different third-parties operating different digital wallet systems), may require only the electronic communication address, only the mobile device number, both the electronic communication address and mobile device number, and/or combinations of other recipient information (e.g., entity name, mailing address, or the like).
Block 140 of
As illustrated in
Block 150 of
As illustrated in
Block 160 of
In some embodiments, it should be understood that the provider entity 6 may be a customer of the organization. The organization may be a financial institution, digital wallet organization, or any other organization through which the provider entity 6 has a resource pool (e.g., a type of account, such as a credit or debit account, that has associated funds available). The recipient entity 4 may be a user that is receiving resources for the provider entity 6, and the recipient entity 4 may have a resource pool (e.g., digital wallet account) that is stored by a third-party that is responsible for the resource systems 30 that manages the resource pool of the recipient entity 4.
It should be understood that the embodiments of the invention described with respect to
In addition to validating the recipient entity 4, embodiments of the invention may also include determining if and when an original delivery channel should or can be substituted by an alternate delivery channel.
Block 320 of
As illustrated by block 340 in
It should be understood that with respect to blocks 320, 330, 340, and 350 before the original delivery channel is identified, before the delivery preference database is accessed, and/or before or after the notification is sent to the recipient entity requesting the recipient delivery preference, the resource delivery processing engine 420 may access the delivery requirements 430 in order to determine if the delivery processing engine 420 has the recipient entity information necessary in order to determine the recipient delivery preference. The recipient entity information may be the same information as previous described herein (e.g., recipient name, identifier, delivery channel options, address, or the like).
Block 360 of
Block 370 further illustrates that resources may be delivered according to the original delivery channel. For example, when the recipient delivery preference of the recipient entity 4 is the same as the original delivery channel, the resource delivery is processed according to the original delivery channel. In some embodiments, this may be a physical resource transfer (e.g., paper checks, or other like physical resource transfers). However, in some embodiments the original delivery channel may be any other channel through which the resources may be provided to the recipient entity, such as a push to a card account, an account deposit, a balance payoff, or the like.
Block 390 of
Moreover, as illustrated in
It should be understood that the embodiments of the invention described with respect to
As described briefly above, the one or more APIs allow for a centralized location for the entities and/or organization to access in order to carry out the processes described herein. That is, the present invention provides a single location that the provider entity may access in order to validate a recipient entity and/or determine a delivery preference for the recipient entity. This central location (e.g., including the potential central location for the validation database or recipient preference database) allows the providing entity to access a single interface location, while the organization and/or a third-party that controls the interface does the work in reaching out to the resource systems, the third-parties, and/or recipient entities in order to validate and/or determine a delivery preference of the recipient entity. In this way, the providing entity does not have to access the various resource systems, the third-parties, and/or the recipient entities each time the providing entity enters into an interaction with a recipient entity and/or transfers resources to the recipient entity. Since the organizations and/or third-parties are more regularly handling the resource transfers controlling the validation and/or delivery preference from a centralized location (e.g., including centralized databases) this improves processing times, reduces memory requirements, and increases the processing capacity of the providing entities, the organizations, the resource entities, and/or third-parties. That is, for example, the parties involved do not each have to store redundant information for validation and/or delivery preferences of each of the resource entities. For example, a first providing entity and a second providing entity do not have to store the same information (e.g., in two validation databases and/or delivery preference databases), and instead a centralized location is used to store all the information. Additionally, the present inventions expands the access to stored validations and/or delivery preferences of recipient entities to which a single provider entity might not otherwise have (e.g., all of the information stored for each recipient entity of various organizations and/or providing entities is aggregated in a single location and/or accessing through a single location).
It should be understood, that the systems described herein may be configured to establish a communication link (e.g., electronic link, or the like) with each other in order to accomplish the steps of the processes described herein. The link may be an internal link within the same entity (e.g., within the same financial institution) or a link with the other entity systems. In some embodiments, the one or more systems may be configured for selectively monitoring the resource usage and availability. These feeds of resource usage and availability may be provided via wireless network path portions through the Internet. When the systems are not providing data, transforming data, transmitting the data, and/or creating the reports, the systems need not be transmitting data over the Internet, although it could be. The systems and associated data for each of the systems may be made continuously available, however, continuously available does not necessarily mean that the systems actually continuously generate data, but that a systems are continuously available to perform actions associated with the systems in real-time (i.e., within a few seconds, or the like) of receiving a request for it. In any case, the systems are continuously available to perform actions with respect to the data, in some cases in digitized data in Internet Protocol (IP) packet format. In response to continuously monitoring the real-time data feeds from the various systems, the systems may be configured to update activities associated with the systems, as described herein.
Moreover, it should be understood that the process flows described herein include transforming the data from the different systems (e.g., internally or externally) from the data format of the various systems to a data format associated with one or more displays. There are many ways in which data is converted within the computer environment. This may be seamless, as in the case of upgrading to a newer version of a computer program. Alternatively, the conversion may require processing by the use of a special conversion program, or it may involve a complex process of going through intermediary stages, or involving complex “exporting” and “importing” procedures, which may convert to and from a tab-delimited or comma-separated text file. In some cases, a program may recognize several data file formats at the data input stage and then is also capable of storing the output data in a number of different formats. Such a program may be used to convert a file format. If the source format or target format is not recognized, then at times a third program may be available which permits the conversion to an intermediate format, which can then be reformatted.
As will be appreciated by one of skill in the art in view of this disclosure, embodiments of the 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 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 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 (e.g., a non-transitory medium, or the like).
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 (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 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), or other tangible optical or magnetic storage device.
Computer program code/computer-readable instructions for carrying out operations of embodiments of the invention may be written in an object oriented, scripted or unscripted programming language such as Java, Pearl, Python, 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 invention described above, with reference to flowchart illustrations and/or block diagrams of methods or apparatuses (the term “apparatus” including systems and computer program products), will be understood to include 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 via 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.
Specific embodiments of the invention are described herein. Many modifications and other embodiments of the invention set forth herein will come to mind to one skilled in the art to which the invention pertains, having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments and combinations of embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:
Number | Name | Date | Kind |
---|---|---|---|
5963924 | Williams | Oct 1999 | A |
6016484 | Williams | Jan 2000 | A |
6401079 | Kahn | Jun 2002 | B1 |
6721783 | Blossman | Apr 2004 | B1 |
6752313 | Caviles et al. | Jun 2004 | B1 |
7032031 | Jungck et al. | Apr 2006 | B2 |
7110969 | Bennett et al. | Sep 2006 | B1 |
7114008 | Jungck et al. | Sep 2006 | B2 |
7440915 | Ulrich | Oct 2008 | B1 |
7676431 | OLeary et al. | Mar 2010 | B2 |
7680735 | Loy | Mar 2010 | B1 |
7680737 | Smith, Jr. et al. | Mar 2010 | B2 |
7693783 | Balasubramanian et al. | Apr 2010 | B2 |
7801814 | Cataline et al. | Sep 2010 | B2 |
7822656 | Knight et al. | Oct 2010 | B2 |
7822688 | Labrou et al. | Oct 2010 | B2 |
8001025 | Vadhri | Aug 2011 | B2 |
8005754 | McCoy et al. | Aug 2011 | B2 |
8010424 | Hamilton et al. | Aug 2011 | B1 |
8121945 | Rackley, III et al. | Feb 2012 | B2 |
8140429 | Balasubramanian et al. | Mar 2012 | B2 |
8254658 | Hamilton | Aug 2012 | B2 |
8255324 | Bercy et al. | Aug 2012 | B2 |
8285641 | Cataline et al. | Oct 2012 | B2 |
8290862 | Sheehan et al. | Oct 2012 | B2 |
8328095 | Oder, II et al. | Dec 2012 | B2 |
8407140 | Ayala | Mar 2013 | B2 |
8438086 | Rosko | May 2013 | B2 |
8458070 | Rosko | Jun 2013 | B2 |
8473324 | Alvarez et al. | Jun 2013 | B2 |
8484142 | Pinckney | Jul 2013 | B2 |
8645266 | Balasubramanian et al. | Feb 2014 | B2 |
8650118 | Balasubramanian et al. | Feb 2014 | B2 |
8768838 | Hoffman | Jul 2014 | B1 |
8875990 | Bishop et al. | Nov 2014 | B2 |
8924294 | Lynch et al. | Dec 2014 | B2 |
9215231 | Bowen | Dec 2015 | B1 |
9367753 | Li et al. | Jun 2016 | B2 |
9495680 | Oder, II et al. | Nov 2016 | B2 |
9691278 | Poomachandran et al. | Jun 2017 | B2 |
9779392 | Prasad | Oct 2017 | B1 |
9959531 | Purves | May 2018 | B2 |
10154084 | Kalgi | Dec 2018 | B2 |
10157436 | Samocha et al. | Dec 2018 | B2 |
10320662 | Ahuja | Jun 2019 | B1 |
10530780 | Henry | Jan 2020 | B2 |
20030099237 | Mitra et al. | May 2003 | A1 |
20030182227 | Guzman | Sep 2003 | A1 |
20040148252 | Fleishman | Jul 2004 | A1 |
20050065678 | Smith et al. | Mar 2005 | A1 |
20050097046 | Singfield | May 2005 | A1 |
20060161604 | Lobo | Jul 2006 | A1 |
20060206425 | Sharma | Sep 2006 | A1 |
20090262741 | Jungck et al. | Oct 2009 | A1 |
20100103837 | Jungck et al. | Apr 2010 | A1 |
20100280909 | Zhang et al. | Nov 2010 | A1 |
20110055077 | French | Mar 2011 | A1 |
20110270733 | Chazen | Nov 2011 | A1 |
20120222032 | Ferdous | Aug 2012 | A1 |
20120233066 | Vallabhaneni | Sep 2012 | A1 |
20120259777 | Rosko | Oct 2012 | A1 |
20130024364 | Shrivastava | Jan 2013 | A1 |
20130103582 | Singfield | Apr 2013 | A1 |
20130110709 | Hodge | May 2013 | A1 |
20130163746 | Wick et al. | Jun 2013 | A1 |
20130173437 | Capparell et al. | Jul 2013 | A1 |
20130208879 | Rosenhaft | Aug 2013 | A1 |
20130346302 | Purves | Dec 2013 | A1 |
20140201070 | Liberty | Jul 2014 | A1 |
20140214649 | DuCharme et al. | Jul 2014 | A1 |
20140244500 | Elias | Aug 2014 | A1 |
20140279404 | Kallimani et al. | Sep 2014 | A1 |
20140297520 | Levchin et al. | Oct 2014 | A1 |
20140372751 | Silverstone | Dec 2014 | A1 |
20150032605 | Williams et al. | Jan 2015 | A1 |
20160055583 | Liberty | Feb 2016 | A1 |
20160086184 | Carpenter et al. | Mar 2016 | A1 |
20160110721 | Russell et al. | Apr 2016 | A1 |
20160148185 | Andrews | May 2016 | A1 |
20160232518 | Butler | Aug 2016 | A1 |
20160247037 | Li et al. | Aug 2016 | A1 |
20160253639 | Sharma | Sep 2016 | A1 |
20160328711 | Elischer | Nov 2016 | A1 |
20160379192 | Purves | Dec 2016 | A1 |
20170032352 | Koeppen et al. | Feb 2017 | A1 |
20170091791 | Srinivasan et al. | Mar 2017 | A1 |
20170091873 | Cole et al. | Mar 2017 | A1 |
20170109717 | Vafeas | Apr 2017 | A1 |
20170134479 | Kalgi | May 2017 | A1 |
20170169420 | Setlur et al. | Jun 2017 | A1 |
20170178110 | Swanson | Jun 2017 | A1 |
20170178126 | Liu et al. | Jun 2017 | A1 |
20180025166 | Daniel | Jan 2018 | A1 |
20180039515 | Crea | Feb 2018 | A1 |
20180129945 | Saxena et al. | May 2018 | A1 |
20180129952 | Saxena et al. | May 2018 | A1 |
20180129953 | Saxena et al. | May 2018 | A1 |
20180129954 | Saxena et al. | May 2018 | A1 |
20180129955 | Saxena et al. | May 2018 | A1 |
20180129956 | Saxena et al. | May 2018 | A1 |
20180129957 | Saxena et al. | May 2018 | A1 |
20180129958 | Saxena et al. | May 2018 | A1 |
20180143975 | Casal et al. | May 2018 | A1 |
20180165416 | Saxena et al. | Jun 2018 | A1 |
20180165585 | Saxena et al. | Jun 2018 | A1 |
20180165586 | Saxena et al. | Jun 2018 | A1 |
20180165588 | Saxena et al. | Jun 2018 | A1 |
20180165598 | Saxena et al. | Jun 2018 | A1 |
20180165611 | Saxena et al. | Jun 2018 | A1 |
20180165612 | Saxena et al. | Jun 2018 | A1 |
20180165758 | Saxena et al. | Jun 2018 | A1 |
20180189756 | Purves | Jul 2018 | A1 |
20180197167 | Ganesan | Jul 2018 | A1 |
20180247544 | Mustafic et al. | Aug 2018 | A1 |
20190012646 | Seidl | Jan 2019 | A1 |
20190057378 | Rudnick | Feb 2019 | A1 |
20190075156 | Kalgi | Mar 2019 | A1 |
Number | Date | Country | |
---|---|---|---|
20190108062 A1 | Apr 2019 | US |