Facilitating guaranty provisioning for an exchange
Disclosed herein are example embodiments for facilitating guaranty provisioning for an exchange. For certain example embodiments, at least one device, such as a mobile device or a server device or an electronic apparatus: (i) may facilitate a matching of at least one proffered guaranty transaction with one or more proffered transaction characteristics; or (ii) may participate in at least one guaranty transaction marketplace to produce at least one guaranty transaction associated with at least one guaranty for a proposed product transaction.
Latest Elwha LLC Patents:
- Thermal signature control structures
- Methods for fabricating and etching porous silicon carbide structures
- Systems and methods for acoustic mode conversion
- Beamforming via sparse activation of antenna elements connected to phase advance waveguides
- Nerve stimulation system, subsystem, headset, and earpiece
The present application is related to and/or claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Priority applications”), if any, listed below (e.g., claims earliest available priority dates for other than provisional patent applications or claims benefits under 35 USC § 119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Priority application(s)). In addition, the present application is related to the “Related applications,” if any, listed below.
PRIORITY APPLICATIONSNone
RELATED APPLICATIONSNone
The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation, continuation-in-part, or divisional of a parent application. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003. The USPTO further has provided forms for the Application Data Sheet which allow automatic loading of bibliographic data but which require identification of each application as a continuation, continuation-in-part, or divisional of a parent application. The present Applicant Entity (hereinafter “Applicant”) has provided above a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization, such as “continuation” or “continuation-in-part,” for claiming priority to U.S. patent applications. Notwithstanding the foregoing, Applicant understands that the USPTO's computer programs have certain data entry requirements, and hence Applicant has provided designation(s) of a relationship between the present application and its parent application(s) as set forth above and in any ADS filed in this application, but expressly points out that such designation(s) are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
If the listings of applications provided above are inconsistent with the listings provided via an ADS, it is the intent of the Applicant to claim priority to each application that appears in the Priority applications section of the ADS and to each application that appears in the Priority applications section of this application.
All subject matter of the Priority applications and the Related applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Priority applications and the Related applications, including any priority claims, is incorporated herein by reference to the extent such subject matter is not inconsistent herewith.
If an Application Data Sheet (ADS) has been filed on the filing date of this application, it is incorporated by reference herein. Any applications claimed on the ADS for priority under 35 U.S.C. §§119, 120, 121, or 365(c), and any and all parent, grandparent, great-grandparent, etc. applications of such applications, are also incorporated by reference, including any priority claims made in those applications and any material incorporated by reference, to the extent such subject matter is not inconsistent herewith.
In accordance with 37 C.F.R. 1.84(h)(2),
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
In a commercial realm, two or more parties may engage in a transaction in which goods or services are exchanged for consideration, such as other goods or services, an accepted monetary unit (e.g., dollars, BitCoins, yuan/renminbi, or a combination thereof, etc.), a credit obligation (e.g., a promise to pay in the future a good, a service, a monetary unit, or a combination thereof, etc.), some combination thereof, or so forth. For example, a person may exchange $5.45 for a caffeinated beverage. In a financial arena, a first party's credit obligation to a second party may be guaranteed by a third party. For example, a parent may agree to make payments on a car loan if a child fails to do so. A guarantee for a credit obligation at least apparently attributable to a first party may be offered to reassure a second party that it is sufficiently likely to be paid so that a credit-extending transaction between the first party and the second party may be consummated. In an event that a first party fails to meet a credit obligation to a second party (e.g., due to fraud by a fourth party, due to insolvency or recalcitrance of the first party, due to a misunderstanding by any party, or a combination thereof, etc.), the second party may be able to rely on the guaranteeing third party to meet the credit obligation established by the first party.
For certain example embodiments, a guarantor may provide a guaranty on behalf of a first entity, such as a purchaser, to a second entity, such as a store owner. For certain example implementations, provision of a guaranty may be at least partially dependent on data obtained by a guarantor independent of the second entity. For example, one or more characteristics of a proposed transaction between a first entity and a second entity may be sent to a potential guarantor. A potential guarantor may already possess or may obtain one or more indicia associated with a first entity that corroborate, support, lend credence to, abide by a behavioral fingerprint that comports with, or a combination thereof, etc. a likelihood that the first entity is or would be desirous of engaging in a proposed transaction including the first entity and a second entity or of procuring a product appurtenant to a proposed transaction. For certain example implementations, a potential guarantor may obtain one or more indicia from a data stream associated with a first entity, such as a data stream produced by or accessible via a mobile device of the first entity. For example, a potential guarantor may have access to a search history, a current location, a social network posting, or a combination thereof, etc. corresponding to a first entity. If a likelihood that a first entity is or would be desirous of engaging in an identified proposed transaction is determined to be sufficiently high (e.g., meets a determined threshold, matches a certain number of characteristics, comports with a behavioral fingerprint, or a combination thereof, etc.), then a potential guarantor may signal to a second entity a willingness to provide a guaranty for the proposed transaction on behalf of the first entity with the second entity as a beneficiary. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, or so forth.
For certain example embodiments, a guarantor may provide a guaranty on behalf of a first entity, such as a dining guest, to benefit a second entity, such as a restaurant or credit card company. For certain example implementations, a server device of a potential guarantor may receive a message from a server device of a credit card company. A message from a server device of a credit card company may identify at least one characteristic of a proposed credit transaction between a first entity and a second entity. For example, a credit card company may identify an identity of a first entity and a location of a second entity. In response to a message from a server device of a credit card company, a potential guarantor, which is able to secure at least one indication that a mobile device of an identified first entity is present at a location of a second entity, may proffer a guaranty to the credit card company. For certain example implementations, a proffered guaranty may be contingent at least partially on at least one identified transaction characteristic being falsified. For example, a guarantor may become responsible for paying at least a portion of a valuation of a transaction after data has been presented evidencing a falsity of a contingent transaction characteristic. For instance, a guarantor may be responsible for paying a total cost for a meal at a restaurant if an identified first entity or a credit card company presents evidence that the identified first entity was in a different city than a city of the restaurant at the time a meal of a guaranteed transaction was served. For such a contingent example, a guarantor may not be responsible to a second entity or to a credit card company if an identified first entity was present at a restaurant of the second entity at a time of a guaranteed transaction but subsequently declines to pay for a meal. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, or so forth.
For certain example embodiments, a merchant 1012 (e.g., of
Multiple and various independent or interrelated example embodiments are described herein below with reference to one or more of any of
With reference to
With reference to
With reference to
For certain example implementations, a transaction characteristic 1026 may comprise or include or be associated with at least one party identifier 1020 (e.g., a name, a code, a number, a picture, a username, an email address, a credit card number, a store number, a company title, an account identifier, or a combination thereof, etc.), at least one product identification 1022 (e.g., a name, a code, a number, an image, a stock keeping unit (SKU), a description, a catalog number, a make or model, or a combination thereof, etc.), at least one valuation 1024 (e.g., a monetary value, a trade value, a number of units, a bartering equivalence, or a combination thereof, etc.), at least one other transaction characteristic 1026O (e.g., a product category, a number of people served, special requests, delivery terms, contingencies, a guaranty indication (e.g., a code, a signal, a positive bit in a field of a message, or a combination thereof, etc. to indicate that a product transaction may be consummated in relation to at least one guaranty, such as an indication that pursing a guaranty is acceptable or is requested, an indication of a preferred or likely guarantor, an indication of an appropriate guaranty transaction marketplace, one or more requested terms for a guaranty, or a combination thereof, etc.), a transaction identification, a characteristic not shown, or a combination thereof, etc.), at least one transaction location 1028 (e.g., a physical location, a virtual location, an address, a city, a store name, a URL, at least one satellite positioning system (SPS) coordinate, a neighborhood, a website name, or a combination thereof, etc.), at least one transaction type 1030 (e.g., buying, leasing, borrowing, acquiring a partial interest in, bartering, acquiring access to at least a share of, in-person, identification presented, via the internet, or a combination thereof, etc.), some combination thereof, or so forth. By way of example but not limitation, a party identifier 1020 may comprise or include at least one customer identifier 1020C, at least one vendor identifier 1020V, some combination thereof or so forth. By way of example but not limitation, a transaction location 1028 may comprise or include at least one customer location 1028C, at least one vendor location 1028V, at least one product location 1028P, some combination thereof, or so forth.
With reference to
With reference to
With continuing reference to
For certain example embodiments, a guaranty transaction marketplace 1040 may enable at least one negotiation 1048 (e.g., presentation of an offer, presentation of a counter-offer, discussion of one or more terms, an acceptance, a refusal, suggested term alterations, bidding, an auction, a reverse auction, or a combination thereof, etc.) to be conducted, accomplished, effectuated, or a combination thereof, etc. via at least one API 1046. At least a portion of an API 1046 may be realized, constituted, implemented, or a combination thereof, etc. at least partially at, by, or using a server device 1036 of a financier 1034, a server device 1056 of a market maker 1058, a server device 1060 of a guarantor 1062, a server device 1106 of a combination financier and guarantor (e.g., of
With reference to
With reference to
With reference to
In another illustrated example, a guarantor 1062 (e.g., of
With reference to
For certain example embodiments, a guaranty transaction 1068, a proffered transaction characteristic 1052, a proffered guaranty transaction 1050, or a combination thereof, etc. may correspond to or at least reference at least one guarantee type 1074, which may define, categorize, describe, indicate, or a combination thereof, etc. a type of guaranty 1054 ascribed to at least guaranty transaction 1068. Examples of a guarantee type 1074 may comprise or include, but are not limited to, a non-contingent guarantee type 1074N, a contingent guarantee type 1074C, some combination thereof, or so forth. For certain example implementations, a non-contingent guarantee 1074N may obligate a guarantor 1062 to ensure that a merchant 1012 or a financier 1034 is paid or made whole regardless of a reason for non-payment by a customer 1002 (e.g., of
For certain example embodiments, one or more terms 1070, such as a contingent 1074C or a non-contingent 1074N guarantee type 1074, may be negotiated as part of at least one negotiation 1048 between or among at least one financier 1034 and one or more potential guarantors 1062. One or more additional or alternative terms 1070 may be subject to negotiation 1048. Examples for at least one term 1070 may comprise or include, but are not limited to, a fee 1072 (e.g., size, delivery mode, delivery timing, type, or a combination thereof, etc.), amount of reimbursement or payment (e.g., percentage of valuation 1024 (e.g., of
For certain example implementations, a negotiation 1048 may include, entail, facilitate, or a combination thereof, etc. the communicating, making, providing, accepting, establishing, presenting, or a combination thereof, etc. of at least one offer 1076O, at least one counter-offer 1076CO, at least one offer 1076 (not explicitly shown, but which may include at least one offer 1076O or at least one counter-offer 1076CO), at least one acceptance 1078, some combination thereof, or so forth. By way of example only, an acceptance 1078 of an offer 1076O or a counter-offer 1076CO may result in or establish a guaranty transaction 1068. For certain example implementations, a negotiation 1048 may include or utilize at least one auction 1080 (e.g., including a traditional auction or a reverse auction) if multiple financiers 1034 or multiple potential guarantors 1062 are attempting to establish a guaranty transaction 1068. An auction 1080 may include one or more bids 1082 (e.g., from one or more potential guarantors 1062, from one or more financiers 1034 intending to attain some level of assurance with respect to at least one product transaction, or a combination thereof, etc.) with differing terms 1070, such as a reduced fee 1072 or a guaranty 1054 having one or more terms that are more favorable to a financier 1034 (e.g., more data disclosure by a guarantor or a lower probative bar to paying on a contingent guaranty).
For certain example implementations, an API 1046b may expose any one or more of a number of facets or inputs or outputs or calls for a guaranty transaction marketplace 1040. Examples of exposed interfaces may comprise or include, but are not limited to, confirmation, information, payment, result, fee, some combination thereof, or so forth. By way of example only, a confirmation call may relate to or pertain to a situation in which a financier 1034 (e.g., of
With reference to
For certain example embodiments, a guarantor 1062 may be, as part of an obligation arising from at least one guaranty 1054 (e.g., of
With reference to
With reference to
With reference to
With reference to
With reference to
With reference to
For certain example implementations, at least one data stream 1090 may include data from multiple different data stream environments 1092 (not explicitly shown separately). Example data stream environments 1092 may comprise or include, but are not limited to, at least one mobile device environment 1092M, at least one internet environment 1092I, at least one wireless network environment 1092W, some combination thereof, or so forth. For certain example implementations, at least one data stream 1090 may include mobile device data 1094, cloud data 1096, mobile service data 1098, some combination thereof, or so forth. By way of example but not limitation, cloud data 1096 may include social network data 1096SN. For certain example implementations, mobile device data 1094 may be obtained via at least one mobile device environment 1092M; cloud data 1096 may be obtained via at least one internet environment 1092I; and mobile service data 1098 may be obtained via at least one wireless network environment 1092W. By way of example but not limitation, mobile device data 1094 may comprise or include data that is detected at a mobile device from a sensor (e.g., an inertial measurement unit (IMU), a satellite positioning system (SPS) unit, a radio, a camera, a magnetometer, or a combination thereof, etc.) or a user input feature (e.g., a touchscreen, a keyboard, a microphone, a camera, or a combination thereof, etc.), such as SPS coordinates, radio signals, keyboard input, user motions, some combination thereof, or so forth. By way of example but not limitation, cloud data 1096 may comprise or include data that is sent over or stored at a cloud-based server or service, such as social network data, search data, remotely-accessed media, app data, some combination thereof, or so forth. By way of example but not limitation, social network data 1096SN may comprise or include data sent to or received from at least one social network (e.g., Facebook, Google+, LinkedIn, MySpace, Pinterest, Classmates[dot]com, Foursquare, Orkut, Twitter, Flickr, Instagram, or a combination thereof, etc.), such as a public or private message, a posting, text, a link, an image, a tweet, some combination thereof, or so forth. By way of example but not limitation, mobile service data 1098 may comprise or include data that may be obtained by a wireless service provider from network infrastructure information or by providing a conduit to the internet, such as a location from trilateration using multiple cell towers, dialed or texted numbers, plain text wireless communications, detected internet communications, some combination thereof, or so forth.
With reference to
With reference to
With reference to
For certain example embodiments, at least one network element 1104 may directly or indirectly communicate with at least one mobile device 1004 via at least one wireless link 1110, with or without one or more wireline or wired links (not explicitly shown) over at least one network, such as a wired portion or implementation of a network 1042 (e.g., of
With reference to
With reference to
With reference to
With reference to
For certain example embodiments, a mobile device 1004 may make one or more observations 1116 under control of at least one operating system 1112 or at least one application 1114. Observations 1116 may be made substantially continuously (e.g., at a rate that an input component is capable of operating), intermittently, at regular intervals, irregularly, randomly, in response to a stimulus, on-demand (e.g., in response to an inquiry received, such as from a potential guarantor 1062), when an app is accessed, in accordance with a geofence, in accordance with a schedule, some combination thereof, or so forth. For certain example implementations, an observation 1116 may comprise or include observations of user input 1116U, observations of sensor detection 1116S, some combination thereof, or so forth. By way of example but not limitation, a user input observation 1116U may comprise or include data acquired (e.g., detected) as a result of keyboard (e.g., physical or virtual) input, other touch input, microphone input, gesture or eye movement input, shaking or twisting input, some combination thereof, or so forth. Data of a user input observation 1116U may comprise or include, for example, spoken or typed words, websites visited, social network members interacted with, social network posts made or presented (e.g., viewed, played, read, or a combination thereof, etc.), people contacted, search terms, some combination thereof, or so forth. By way of example but not limitation, a sensor detection observation 1116S may comprise or include data acquired as a result of a satellite positioning system (SPS) unit, a radio or transceiver, a camera, a microphone, a touchscreen, an inertial measurement unit (IMU)—such as an accelerometer, a gyroscope, a compass, or a combination thereof, etc.—, a thermometer, some combination thereof, or so forth. Data of a sensor detection observation 1116S may comprise or include, for example, an SPS coordinate, a Wi-Fi service set identifier (SSID), a gravitational direction, an acceleration magnitude or direction, a velocity, a sound file, a photographic image, some combination thereof, or so forth.
For certain example implementations, one or more observations 1116 that are acquired by a mobile device 1004 may be provided (e.g., forwarded, propagated, or a combination thereof, etc.) to at least one data stream 1090 (e.g., of
With reference to
For certain example implementations, a mobile device 1004, such as an operating system 1112 or an application 1114 thereof, may obtain requested data in response to an inquiry 1120 using, for example, at least one user input observation 1116U, at least one sensor detection observation 1116S, some combination thereof, or so forth. By way of example but not limitation, an answer to an inquiry 1120 may be returned from a mobile device 1004 to a server device 1060 as at least one inquiry response 1122. For certain example implementations, an inquiry 1120 or an inquiry response 1122 may additionally or alternatively be accomplished using one or more protocols, mechanisms, communication avenues, or a combination thereof, etc. that are available as part of a data stream 1090 (e.g., of
For certain example implementations, as indicated at a blurb 2036, a guarantor 1062 (e.g., of
With reference to
For certain example implementations, at least one background check provider server device 1124 may communicate with one or more of a guarantor server device 1060 (e.g., of
With reference to
For certain example embodiments, a device 1500 may include or comprise at least one electronic device. A device 1500 may include, for example, a computing platform or any electronic device having at least one processor or memory. A processor 1502 may include, by way of example but not limitation, any one or more of a general-purpose processor, a specific-purpose processor, a digital signal processor (DSP), a processing unit, some combination thereof, or so forth. A processing unit may be implemented, for example, with one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors generally, one or more processing cores, discrete/fixed logic circuitry, controllers, micro-controllers, microprocessors, some combination thereof, or so forth. A medium 1504 may bear, store, contain, include, provide access to, or a combination thereof, etc. one or more instructions 1510, which may be executable by a processor 1502. Instructions 1510 may include or comprise or facilitate implementation of, by way of example but not limitation, a program, a module, an application or app (e.g., that is native, that runs in a browser, that runs within a virtual machine, or a combination thereof, etc.), an operating system, or a combination thereof, etc. or portion thereof; operational data structures; source code, object code, just-in-time (JIT) compiled code, or a combination thereof, etc.; processor-executable instructions; other code; some combination thereof; or so forth. A medium 1504 may include, by way of example but not limitation, processor-accessible or non-transitory media (e.g., memory, random access memory (RAM), read only memory (ROM), flash memory, hard drives, disk-based media, disc-based media, magnetic storage, optical storage, volatile memory, nonvolatile memory, or a combination thereof, etc.) that is capable of bearing instructions or data.
For certain example embodiments, execution of instructions 1510 by one or more processors 1502 may transform at least a portion of at least one device 1500 into a special-purpose computing device, apparatus, platform, machine, some combination thereof, or so forth. Instructions 1510 may include, for example, instructions that are capable of realizing at least a portion of one or more flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, or a combination thereof, etc. that are described herein or illustrated in the accompanying drawings.
For certain example embodiments, circuitry 1508 may include hardware, software, firmware, discrete/fixed logic circuitry, or a combination thereof, etc. that is capable of performing or facilitating performance of flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, or a combination thereof, etc. that are described herein or illustrated in the accompanying drawings, wherein circuitry 1508 includes at least one physical or hardware component or aspect. By way of example only, circuitry 1508 may be formed if one or more instructions 1510 configure or reconfigure at least one processor 1502 to enable at least one processor 1502 to perform one or more operations during execution of one or more instructions 1510.
For certain example embodiments, one or more communication interfaces 1506 may provide one or more interfaces between device 1500 and another device or a person/operator/entity directly or indirectly. With respect to a person/operator, a communication interface 1506 may include, by way of example but not limitation, a screen, a speaker, a keyboard or keys, a microphone, a camera, or other person-device input/output apparatuses. A wireless communication interface or a wired communication interface may also or alternatively include, by way of example but not limitation, a transceiver (e.g., a transmitter or a receiver), a radio, an antenna, a wired interface connector or other similar apparatus (e.g., a network connector, a universal serial bus (USB) connector, a proprietary connector, a Thunderbolt® or Light Peak® connector, or a combination thereof, etc.), a physical or logical network adapter or port, a frequency converter, a baseband processor, a photoreceptor, an infrared port, an Internet or telecommunications backbone connector, a fiber optic connector, a storage area network (SAN) connector, a local area network (LAN) connector, or a combination thereof, etc. to communicate wireless signals or wired signals via one or more wireless communication links or wired communication links, respectively, such as over at least one communication channel. Communications with at least one communication interface 1506 may enable transmitting, receiving, or initiating of transmissions, just to name a few examples.
For certain example embodiments, at least one power source (not explicitly shown) may provide power to one or more components of a device 1500. A power source may include, by way of example but not limitation, at least one battery, at least one power connector for a wall socket, at least one solar power source, at least one solar-powered charger, a mechanical power source or charger, a fuel source or cell, a power connector for accessing an electrical grid, some combination thereof, or so forth. For certain example embodiments, at least one sensor (not explicitly shown) may sense, produce, or otherwise provide at least one sensor value. A sensor may include, by way of example only, a camera, a microphone, an accelerometer, a thermometer, a satellite positioning system (SPS) sensor, a barometer, a humidity sensor, a compass, an altimeter, a gyroscope, a magnetometer, a pressure sensor, an oscillation detector, a light sensor, an inertial measurement unit (IMU), a tactile sensor, a touch sensor, a flexibility sensor, a microelectromechanical system (MEMS), some combination thereof, or so forth. Values provided by at least one sensor may include, by way of example but not limitation, an image/video, a sound recording, an acceleration value, a temperature, one or more SPS coordinates, a barometric pressure, a humidity level, a compass direction, an altitude, a gyroscopic value, a magnetic reading, a pressure value, an oscillation value, an ambient light reading, inertial readings, touch detections, finger placements, flex detections, some combination thereof, or so forth.
With respect to certain example embodiments, an example applicable scenario is described with reference to multiple example annotations 2502 to 2538, which annotations are depicted by curly brackets or braces (e.g., “{ }”) in
For an example annotation 2506 (e.g., of
For an example annotation 2510 (e.g., of
For an example annotation 2514 (e.g., of
For an example annotation 2520 (e.g., of
For an example annotation 2522 (e.g., of
For an example annotation 2524 (e.g., of
For an example annotation 2526 (e.g., of
For an example annotation 2530 (e.g., of
For an example annotation 2534 (e.g., of
For an example annotation 2538 (e.g., of
Those skilled in the art will appreciate that the foregoing specific exemplary processes and/or devices and/or technologies are representative of more general processes and/or devices and/or technologies taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.
The claims, description, and drawings of this application may describe one or more of the instant technologies in operational/functional language, for example as a set of operations to be performed by a computer. Such operational/functional description in most instances would be understood by one skilled the art as specifically-configured hardware (e.g., because a general purpose computer in effect becomes a special purpose computer once it is programmed to perform particular functions pursuant to instructions from program software).
Importantly, although the operational/functional descriptions described herein are understandable by the human mind, they are not abstract ideas of the operations/functions divorced from computational implementation of those operations/functions. Rather, the operations/functions represent a specification for massively complex computational machines or other means. As discussed in detail below, the operational/functional language must be read in its proper technological context, i.e., as concrete specifications for physical implementations.
The logical operations/functions described herein are a distillation of machine specifications or other physical mechanisms specified by the operations/functions such that the otherwise inscrutable machine specifications may be comprehensible to a human reader. The distillation also allows one of skill in the art to adapt the operational/functional description of the technology across many different specific vendors' hardware configurations or platforms, without being limited to specific vendors' hardware configurations or platforms.
Some of the present technical description (e.g., detailed description, drawings, claims, etc.) may be set forth in terms of logical operations/functions. As described in more detail herein, these logical operations/functions are not representations of abstract ideas, but rather are representative of static or sequenced specifications of various hardware elements. Differently stated, unless context dictates otherwise, the logical operations/functions will be understood by those of skill in the art to be representative of static or sequenced specifications of various hardware elements. This is true because tools available to one of skill in the art to implement technical disclosures set forth in operational/functional formats-tools in the form of a high-level programming language (e.g., C, java, visual basic), etc.), or tools in the form of Very high speed Hardware Description Language (“VHDL,” which is a language that uses text to describe logic circuits)—are generators of static or sequenced specifications of various hardware configurations. This fact is sometimes obscured by the broad term “software,” but, as shown by the following explanation, those skilled in the art understand that what is termed “software” is a shorthand for a massively complex interchaining/specification of ordered-matter elements. The term “ordered-matter elements” may refer to physical components of computation, such as assemblies of electronic logic gates, molecular computing logic constituents, quantum computing mechanisms, etc.
For example, a high-level programming language is a programming language with strong abstraction, e.g., multiple levels of abstraction, from the details of the sequential organizations, states, inputs, outputs, etc., of the machines that a high-level programming language actually specifies. See, e.g., Wikipedia, High-level programming language, http://en [dot] wikipedia [dot] org/wiki/High-level_programming_language (as of Jun. 5, 2012, 21:00 GMT). In order to facilitate human comprehension, in many instances, high-level programming languages resemble or even share symbols with natural languages. See, e.g., Wikipedia, Natural language, http://en [dot] wikipedia [dot] org/wiki/Natural_language (as of Jun. 5, 2012, 21:00 GMT).
It has been argued that because high-level programming languages use strong abstraction (e.g., that they may resemble or share symbols with natural languages), they are therefore a “purely mental construct” (e.g., that “software”—a computer program or computer programming—is somehow an ineffable mental construct, because at a high level of abstraction, it can be conceived and understood by a human reader). This argument has been used to characterize technical description in the form of functions/operations as somehow “abstract ideas.” In fact, in technological arts (e.g., the information and communication technologies) this is not true.
The fact that high-level programming languages use strong abstraction to facilitate human understanding should not be taken as an indication that what is expressed is an abstract idea. In fact, those skilled in the art understand that just the opposite is true. If a high-level programming language is the tool used to implement a technical disclosure in the form of functions/operations, those skilled in the art will recognize that, far from being abstract, imprecise, “fuzzy,” or “mental” in any significant semantic sense, such a tool is instead a near incomprehensibly precise sequential specification of specific computational machines—the parts of which are built up by activating/selecting such parts from typically more general computational machines over time (e.g., clocked time). This fact is sometimes obscured by the superficial similarities between high-level programming languages and natural languages. These superficial similarities also may cause a glossing over of the fact that high-level programming language implementations ultimately perform valuable work by creating/controlling many different computational machines.
The many different computational machines that a high-level programming language specifies are almost unimaginably complex. At base, the hardware used in the computational machines typically consists of some type of ordered matter (e.g., traditional electronic devices (e.g., transistors), deoxyribonucleic acid (DNA), quantum devices, mechanical switches, optics, fluidics, pneumatics, optical devices (e.g., optical interference devices), molecules, etc.) that are arranged to form logic gates. Logic gates are typically physical devices that may be electrically, mechanically, chemically, or otherwise driven to change physical state in order to create a physical reality of logic, such as Boolean logic.
Logic gates may be arranged to form logic circuits, which are typically physical devices that may be electrically, mechanically, chemically, or otherwise driven to create a physical reality of certain logical functions. Types of logic circuits include such devices as multiplexers, registers, arithmetic logic units (ALUs), computer memory, etc., each type of which may be combined to form yet other types of physical devices, such as a central processing unit (CPU)—the best known of which is the microprocessor. A modern microprocessor will often contain more than one hundred million logic gates in its many logic circuits (and often more than a billion transistors). See, e.g., Wikipedia, Logic gates, http://en [dot] wikipedia [dot] org/wiki/Logic_gates (as of Jun. 5, 2012, 21:03 GMT).
The logic circuits forming the microprocessor are arranged to provide a microarchitecture that will carry out the instructions defined by that microprocessor's defined Instruction Set Architecture. The Instruction Set Architecture is the part of the microprocessor architecture related to programming, including the native data types, instructions, registers, addressing modes, memory architecture, interrupt and exception handling, and external Input/Output. See, e.g., Wikipedia, Computer architecture, http://en [dot] wikipedia [dot] org/wiki/Computer_architecture (as of Jun. 5, 2012, 21:03 GMT).
The Instruction Set Architecture includes a specification of the machine language that can be used by programmers to use/control the microprocessor. Since the machine language instructions are such that they may be executed directly by the microprocessor, typically they consist of strings of binary digits, or bits. For example, a typical machine language instruction might be many bits long (e.g., 32, 64, or 128 bit strings are currently common). A typical machine language instruction might take the form “11110000101011110000111100111111” (a 32 bit instruction).
It is significant here that, although the machine language instructions are written as sequences of binary digits, in actuality those binary digits specify physical reality. For example, if certain semiconductors are used to make the operations of Boolean logic a physical reality, the apparently mathematical bits “1” and “0” in a machine language instruction actually constitute a shorthand that specifies the application of specific voltages to specific wires. For example, in some semiconductor technologies, the binary number “1” (e.g., logical “1”) in a machine language instruction specifies around +5 volts applied to a specific “wire” (e.g., metallic traces on a printed circuit board) and the binary number “0” (e.g., logical “0”) in a machine language instruction specifies around −5 volts applied to a specific “wire.” In addition to specifying voltages of the machines' configurations, such machine language instructions also select out and activate specific groupings of logic gates from the millions of logic gates of the more general machine. Thus, far from abstract mathematical expressions, machine language instruction programs, even though written as a string of zeros and ones, specify many, many constructed physical machines or physical machine states.
Machine language is typically incomprehensible by most humans (e.g., the above example was just ONE instruction, and some personal computers execute more than two billion instructions every second). See, e.g., Wikipedia, Instructions per second, http://en [dot] wikipedia [dot] org/wiki/Instructions_per_second (as of Jun. 5, 2012, 21:04 GMT). Thus, programs written in machine language—which may be tens of millions of machine language instructions long—are incomprehensible to most humans. In view of this, early assembly languages were developed that used mnemonic codes to refer to machine language instructions, rather than using the machine language instructions' numeric values directly (e.g., for performing a multiplication operation, programmers coded the abbreviation “mult,” which represents the binary number “011000” in MIPS machine code). While assembly languages were initially a great aid to humans controlling the microprocessors to perform work, in time the complexity of the work that needed to be done by the humans outstripped the ability of humans to control the microprocessors using merely assembly languages.
At this point, it was noted that the same tasks needed to be done over and over, and the machine language necessary to do those repetitive tasks was the same. In view of this, compilers were created. A compiler is a device that takes a statement that is more comprehensible to a human than either machine or assembly language, such as “add 2+2 and output the result,” and translates that human understandable statement into a complicated, tedious, and immense machine language code (e.g., millions of 32, 64, or 128 bit length strings). Compilers thus translate high-level programming language into machine language.
This compiled machine language, as described above, is then used as the technical specification which sequentially constructs and causes the interoperation of many different computational machines such that useful, tangible, and concrete work is done. For example, as indicated above, such machine language—the compiled version of the higher-level language—functions as a technical specification which selects out hardware logic gates, specifies voltage levels, voltage transition timings, etc., such that the useful work is accomplished by the hardware.
Thus, a functional/operational technical description, when viewed by one of skill in the art, is far from an abstract idea. Rather, such a functional/operational technical description, when understood through the tools available in the art such as those just described, is instead understood to be a humanly understandable representation of a hardware specification, the complexity and specificity of which far exceeds the comprehension of most any one human. With this in mind, those skilled in the art will understand that any such operational/functional technical descriptions—in view of the disclosures herein and the knowledge of those skilled in the art—may be understood as operations made into physical reality by (a) one or more interchained physical machines, (b) interchained logic gates configured to create one or more physical machine(s) representative of sequential/combinatorial logic(s), (c) interchained ordered matter making up logic gates (e.g., interchained electronic devices (e.g., transistors), DNA, quantum devices, mechanical switches, optics, fluidics, pneumatics, molecules, etc.) that create physical reality of logic(s), or (d) virtually any combination of the foregoing. Indeed, any physical object which has a stable, measurable, and changeable state may be used to construct a machine based on the above technical description. Charles Babbage, for example, constructed the first mechanized computational apparatus out of wood, with the apparatus powered by cranking a handle.
Thus, far from being understood as an abstract idea, those skilled in the art will recognize a functional/operational technical description as a humanly-understandable representation of one or more almost unimaginably complex and time sequenced hardware instantiations. The fact that functional/operational technical descriptions might lend themselves readily to high-level computing languages (or high-level block diagrams for that matter) that share some words, structures, phrases, etc. with natural language should not be taken as an indication that such functional/operational technical descriptions are abstract ideas, or mere expressions of abstract ideas. In fact, as outlined herein, in the technological arts this is simply not true. When viewed through the tools available to those of skill in the art, such functional/operational technical descriptions are seen as specifying hardware configurations of almost unimaginable complexity.
As outlined above, the reason for the use of functional/operational technical descriptions is at least twofold. First, the use of functional/operational technical descriptions allows near-infinitely complex machines and machine operations arising from interchained hardware elements to be described in a manner that the human mind can process (e.g., by mimicking natural language and logical narrative flow). Second, the use of functional/operational technical descriptions assists the person of skill in the art in understanding the described subject matter by providing a description that is more or less independent of any specific vendor's piece(s) of hardware.
The use of functional/operational technical descriptions assists the person of skill in the art in understanding the described subject matter since, as is evident from the above discussion, one could easily, although not quickly, transcribe the technical descriptions set forth in this document as trillions of ones and zeroes, billions of single lines of assembly-level machine code, millions of logic gates, thousands of gate arrays, or any number of intermediate levels of abstractions. However, if any such low-level technical descriptions were to replace the present technical description, a person of skill in the art could encounter undue difficulty in implementing the disclosure, because such a low-level technical description would likely add complexity without a corresponding benefit (e.g., by describing the subject matter utilizing the conventions of one or more vendor-specific pieces of hardware). Thus, the use of functional/operational technical descriptions assists those of skill in the art by separating the technical descriptions from the conventions of any vendor-specific piece of hardware.
In view of the foregoing, the logical operations/functions set forth in the present technical description are representative of static or sequenced specifications of various ordered-matter elements, in order that such specifications may be comprehensible to the human mind and adaptable to create many various hardware configurations. The logical operations/functions disclosed herein should be treated as such, and should not be disparagingly characterized as abstract ideas merely because the specifications they represent are presented in a manner that one of skill in the art can readily understand and apply in a manner independent of a specific vendor's hardware implementation.
Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware, software, and/or firmware implementations of aspects of systems; the use of hardware, software, and/or firmware is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware in one or more machines, compositions of matter, and articles of manufacture, limited to patentable subject matter under 35 USC 101. Hence, there are several possible vehicles by which the processes and/or devices and/or other technologies described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware.
In some implementations described herein, logic and similar implementations may include computer programs or other control structures. Electronic circuitry, for example, may have one or more paths of electrical current constructed and arranged to implement various functions as described herein. In some implementations, one or more media may be configured to bear a device-detectable implementation when such media hold or transmit device detectable instructions operable to perform as described herein. In some variants, for example, implementations may include an update or modification of existing software or firmware, or of gate arrays or programmable hardware, such as by performing a reception of or a transmission of one or more instructions in relation to one or more operations described herein. Alternatively or additionally, in some variants, an implementation may include special-purpose hardware, software, firmware components, and/or general-purpose components executing or otherwise invoking special-purpose components. Specifications or other implementations may be transmitted by one or more instances of tangible transmission media as described herein, optionally by packet transmission or otherwise by passing through distributed media at various times.
Alternatively or additionally, implementations may include executing a special-purpose instruction sequence or invoking circuitry for enabling, triggering, coordinating, requesting, or otherwise causing one or more occurrences of virtually any functional operation described herein. In some variants, operational or other logical descriptions herein may be expressed as source code and compiled or otherwise invoked as an executable instruction sequence. In some contexts, for example, implementations may be provided, in whole or in part, by source code, such as C++, or other code sequences. In other implementations, source or other code implementation, using commercially available and/or techniques in the art, may be compiled/implemented/translated/converted into a high-level descriptor language (e.g., initially implementing described technologies in C or C++ programming language and thereafter converting the programming language implementation into a logic-synthesizable language implementation, a hardware description language implementation, a hardware design simulation implementation, and/or other such similar mode(s) of expression). For example, some or all of a logical expression (e.g., computer programming language implementation) may be manifested as a Verilog-type hardware description (e.g., via Hardware Description Language (HDL) and/or Very High Speed Integrated Circuit Hardware Descriptor Language (VHDL)) or other circuitry model which may then be used to create a physical implementation having hardware (e.g., an Application Specific Integrated Circuit). Those skilled in the art will recognize how to obtain, configure, and optimize suitable transmission or computational elements, material supplies, actuators, or other structures in light of these teachings.
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof, limited to patentable subject matter under 35 U.S.C. 101. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, limited to patentable subject matter under 35 U.S.C. 101, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link (e.g., transmitter, receiver, transmission logic, reception logic, etc.), etc.).
The term module, as used in the foregoing/following disclosure, may refer to a collection of one or more components that are arranged in a particular manner, or a collection of one or more general-purpose components that may be configured to operate in a particular manner at one or more particular points in time, and/or also configured to operate in one or more further manners at one or more further times. For example, the same hardware, or same portions of hardware, may be configured/reconfigured in sequential/parallel time(s) as a first type of module (e.g., at a first time), as a second type of module (e.g., at a second time, which may in some instances coincide with, overlap, or follow a first time), and/or as a third type of module (e.g., at a third time which may, in some instances, coincide with, overlap, or follow a first time and/or a second time), etc. Reconfigurable and/or controllable components (e.g., general purpose processors, digital signal processors, field programmable gate arrays, etc.) are capable of being configured as a first module that has a first purpose, then a second module that has a second purpose and then, a third module that has a third purpose, and so on. The transition of a reconfigurable and/or controllable component may occur in as little as a few nanoseconds, or may occur over a period of minutes, hours, or days.
In some such examples, at the time the component is configured to carry out the second purpose, the component may no longer be capable of carrying out that first purpose until it is reconfigured. A component may switch between configurations as different modules in as little as a few nanoseconds. A component may reconfigure on-the-fly, e.g., the reconfiguration of a component from a first module into a second module may occur just as the second module is needed. A component may reconfigure in stages, e.g., portions of a first module that are no longer needed may reconfigure into the second module even before the first module has finished its operation. Such reconfigurations may occur automatically, or may occur through prompting by an external source, whether that source is another component, an instruction, a signal, a condition, an external stimulus, or similar.
For example, a central processing unit of a personal computer may, at various times, operate as a module for displaying graphics on a screen, a module for writing data to a storage medium, a module for receiving user input, and a module for multiplying two large prime numbers, by configuring its logical gates in accordance with its instructions. Such reconfiguration may be invisible to the naked eye, and in some embodiments may include activation, deactivation, and/or re-routing of various portions of the component, e.g., switches, logic gates, inputs, and/or outputs. Thus, in the examples found in the foregoing/following disclosure, if an example includes or recites multiple modules, the example includes the possibility that the same hardware may implement more than one of the recited modules, either contemporaneously or at discrete times or timings. The implementation of multiple modules, whether using more components, fewer components, or the same number of components as the number of modules, is merely an implementation choice and does not generally affect the operation of the modules themselves. Accordingly, it should be understood that any recitation of multiple discrete modules in this disclosure includes implementations of those modules as any number of underlying components, including, but not limited to, a single component that reconfigures itself over time to carry out the functions of multiple modules, and/or multiple components that similarly reconfigure, and/or special purpose reconfigurable components.
In a general sense, those skilled in the art will recognize that the various embodiments described herein can be implemented, individually and/or collectively, by various types of electro-mechanical systems having a wide range of electrical components such as hardware, software, firmware, and/or virtually any combination thereof, limited to patentable subject matter under 35 U.S.C. 101; and a wide range of components that may impart mechanical force or motion such as rigid bodies, spring or torsional bodies, hydraulics, electro-magnetically actuated devices, and/or virtually any combination thereof. Consequently, as used herein “electro-mechanical system” includes, but is not limited to, electrical circuitry operably coupled with a transducer (e.g., an actuator, a motor, a piezoelectric crystal, a Micro Electro Mechanical System (MEMS), etc.), electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of memory (e.g., random access, flash, read only, etc.)), electrical circuitry forming a communications device (e.g., a modem, communications switch, optical-electrical equipment, etc.), and/or any non-electrical analog thereto, such as optical or other analogs (e.g., graphene based circuitry). Those skilled in the art will also appreciate that examples of electro-mechanical systems include but are not limited to a variety of consumer electronics systems, medical devices, as well as other systems such as motorized transport systems, factory automation systems, security systems, and/or communication/computing systems. Those skilled in the art will recognize that electro-mechanical as used herein is not necessarily limited to a system that has both electrical and mechanical actuation except as context may dictate otherwise.
In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, and/or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of memory (e.g., random access, flash, read only, etc.)), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, optical-electrical equipment, etc.). Those having skill in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.
Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into an image processing system. Those having skill in the art will recognize that a typical image processing system generally includes one or more of a system unit housing, a video display device, memory such as volatile or non-volatile memory, processors such as microprocessors or digital signal processors, computational entities such as operating systems, drivers, applications programs, one or more interaction devices (e.g., a touch pad, a touch screen, an antenna, etc.), control systems including feedback loops and control motors (e.g., feedback for sensing lens position and/or velocity; control motors for moving/distorting lenses to give desired focuses). An image processing system may be implemented utilizing suitable commercially available components, such as those typically found in digital still systems and/or digital motion systems.
Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into a data processing system. Those having skill in the art will recognize that a data processing system generally includes one or more of a system unit housing, a video display device, memory such as volatile or non-volatile memory, processors such as microprocessors or digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices (e.g., a touch pad, a touch screen, an antenna, etc.), and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A data processing system may be implemented utilizing suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into a mote system. Those having skill in the art will recognize that a typical mote system generally includes one or more memories such as volatile or non-volatile memories, processors such as microprocessors or digital signal processors, computational entities such as operating systems, user interfaces, drivers, sensors, actuators, applications programs, one or more interaction devices (e.g., an antenna USB ports, acoustic ports, etc.), control systems including feedback loops and control motors (e.g., feedback for sensing or estimating position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A mote system may be implemented utilizing suitable components, such as those found in mote computing/communication systems. Specific examples of such components entail such as Intel Corporation's and/or Crossbow Corporation's mote components and supporting hardware, software, and/or firmware.
Those skilled in the art will recognize that it is common within the art to implement devices and/or processes and/or systems, and thereafter use engineering and/or other practices to integrate such implemented devices and/or processes and/or systems into more comprehensive devices and/or processes and/or systems. That is, at least a portion of the devices and/or processes and/or systems described herein can be integrated into other devices and/or processes and/or systems via a reasonable amount of experimentation. Those having skill in the art will recognize that examples of such other devices and/or processes and/or systems might include—as appropriate to context and application—all or part of devices and/or processes and/or systems of (a) an air conveyance (e.g., an airplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., a car, truck, locomotive, tank, armored personnel carrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.), (d) an appliance (e.g., a refrigerator, a washing machine, a dryer, etc.), (e) a communications system (e.g., a networked system, a telephone system, a Voice over IP system, etc.), (f) a business entity (e.g., an Internet Service Provider (ISP) entity such as Comcast Cable, Qwest, Southwestern Bell, Verizon, AT&T, etc.), or (g) a wired/wireless services entity (e.g., Sprint, AT&T, Verizon, etc.), etc.
In certain cases, use of a system or method may occur in a territory even if components are located outside the territory. For example, in a distributed computing context, use of a distributed computing system may occur in a territory even though parts of the system may be located outside of the territory (e.g., relay, server, processor, signal-bearing medium, transmitting computer, receiving computer, etc. located outside the territory).
A sale of a system or method may likewise occur in a territory even if components of the system or method are located and/or used outside the territory. Further, implementation of at least part of a system for performing a method in one territory does not preclude use of the system in another territory.
All of the above U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in any Application Data Sheet, are incorporated herein by reference, to the extent not inconsistent herewith.
One skilled in the art will recognize that the herein described components (e.g., operations), devices, objects, and the discussion accompanying them are used as examples for the sake of conceptual clarity and that various configuration modifications are contemplated. Consequently, as used herein, the specific exemplars set forth and the accompanying discussion are intended to be representative of their more general classes. In general, use of any specific exemplar is intended to be representative of its class, and the non-inclusion of specific components (e.g., operations), devices, and objects should not be taken limiting.
Although user/customer 1002, merchant/vendor 1012, financier 1034, guarantor 1062, market maker 1058, data provider 1102, or combined funding source and wireless service provider 1108 may be shown/described herein as a single illustrated figure of a person or building, those skilled in the art will appreciate that user/customer 1002, merchant/vendor 1012, financier 1034, guarantor 1062, market maker 1058, data provider 1102, or combined funding source and wireless service provider 1108 may be representative of a human user, a robotic user (e.g., computational entity), a legal entity, and/or substantially any combination thereof (e.g., a user may be assisted by one or more robotic agents) unless context dictates otherwise. Those skilled in the art will appreciate that, in general, the same may be said of “sender” and/or other entity-oriented terms as such terms are used herein unless context dictates otherwise.
With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations are not expressly set forth herein for sake of clarity.
The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled,” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable,” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components, and/or wirelessly interactable, and/or wirelessly interacting components, and/or logically interacting, and/or logically interactable components.
In some instances, one or more components may be referred to herein as “configured to,” “configured by,” “configurable to,” “operable/operative to,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Those skilled in the art will recognize that such terms (e.g. “configured to”) generally encompass active-state components and/or inactive-state components and/or standby-state components, unless context requires otherwise.
For the purposes of this application, “cloud” computing may be understood as described in the cloud computing literature. For example, cloud computing may be methods and/or systems for the delivery of computational capacity and/or storage capacity as a service. The “cloud” may refer to one or more hardware and/or software components that deliver or assist in the delivery of computational and/or storage capacity, including, but not limited to, one or more of a client, an application, a platform, an infrastructure, and/or a server The cloud may refer to any of the hardware and/or software associated with a client, an application, a platform, an infrastructure, and/or a server. For example, cloud and cloud computing may refer to one or more of a computer, a processor, a storage medium, a router, a switch, a modem, a virtual machine (e.g., a virtual server), a data center, an operating system, a middleware, a firmware, a hardware back-end, a software back-end, and/or a software application. A cloud may refer to a private cloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloud may be a shared pool of configurable computing resources, which may be public, private, semi-private, distributable, scaleable, flexible, temporary, virtual, and/or physical. A cloud or cloud service may be delivered over one or more types of network, e.g., a mobile communication network, and the Internet.
As used in this application, a cloud or a cloud service may include one or more of infrastructure-as-a-service (“IaaS”), platform-as-a-service (“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service (“DaaS”). As a non-exclusive example, IaaS may include, e.g., one or more virtual server instantiations that may start, stop, access, and/or configure virtual servers and/or storage centers (e.g., providing one or more processors, storage space, and/or network resources on-demand, e.g., EMC and Rackspace). PaaS may include, e.g., one or more software and/or development tools hosted on an infrastructure (e.g., a computing platform and/or a solution stack from which the client can create software interfaces and applications, e.g., Microsoft Azure). SaaS may include, e.g., software hosted by a service provider and accessible over a network (e.g., the software for the application and/or the data associated with that software application may be kept on the network, e.g., Google Apps, SalesForce). DaaS may include, e.g., providing desktop, applications, data, and/or services for the user over a network (e.g., providing a multi-application framework, the applications in the framework, the data associated with the applications, and/or services related to the applications and/or the data over the network, e.g., Citrix). The foregoing is intended to be exemplary of the types of systems and/or methods referred to in this application as “cloud” or “cloud computing” and should not be considered complete or exhaustive.
This application may make reference to one or more trademarks, e.g., a word, letter, symbol, or device adopted by one manufacturer or merchant and used to identify and/or distinguish his or her product from those of others. Trademark names used herein are set forth in such language that makes clear their identity, that distinguishes them from common descriptive nouns, that have fixed and definite meanings, or, in many if not all cases, are accompanied by other specific identification using terms not covered by trademark. In addition, trademark names used herein have meanings that are well-known and defined in the literature, or do not refer to products or compounds for which knowledge of one or more trade secrets is required in order to divine their meaning. All trademarks referenced in this application are the property of their respective owners, and the appearance of one or more trademarks in this application does not diminish or otherwise adversely affect the validity of the one or more trademarks. All trademarks, registered or unregistered, that appear in this application are assumed to include a proper trademark symbol, e.g., the circle R or bracketed capitalization (e.g., [trademark name]), even when such trademark symbol does not explicitly appear next to the trademark. To the extent a trademark is used in a descriptive manner to refer to a product or process, that trademark should be interpreted to represent the corresponding product or process as of the date of the filing of this patent application.
While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to claims containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that typically a disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms unless context dictates otherwise. For example, the phrase “A or B” will be typically understood to include the possibilities of “A” or “B” or “A and B.”
With respect to the appended claims, those skilled in the art will appreciate that recited operations therein may generally be performed in any order. Also, although various operational flows are presented in a sequence(s), it should be understood that the various operations may be performed in other orders than those which are illustrated, or may be performed concurrently. Examples of such alternate orderings may include overlapping, interleaved, interrupted, reordered, incremental, preparatory, supplemental, simultaneous, reverse, or other variant orderings, unless context dictates otherwise. Furthermore, terms like “responsive to,” “related to,” or other past-tense adjectives are generally not intended to exclude such variants, unless context dictates otherwise.
While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
1. A method for facilitating guaranty provisioning for an exchange, the method being at least partly implemented by at least one device, the method comprising:
- associating at least one point-of-sale payment tool with at least one product transaction that is related to at least one customer and at least one vendor;
- determining at least one sale location associated with the at least one point-of-sale payment tool;
- verifying that the at least one customer is in a location that corresponds to the at least one sale location, including at least: detecting at least one social media entry on a social media account associated with the at least one customer, the at least one social media entry proximate in time to the at least one product transaction; determining whether the social media account is associated with at least one social media application operational on at least one mobile device associated with the at least one customer, including at least determining, via image recognition, whether the at least one customer is identified in at least one image posted to the at least one social media account; and verifying, via the detected at least one social media entry, that the at least one mobile device associated with the at least one customer is in the location that corresponds to the determined at least one sale location, including at least detecting whether at least some data associated with the at least one image indicates that the at least one image was posted from the location that corresponds to the determined at least one sale location;
- requesting at least one guaranty to be associated with the at least one point-of-sale payment tool based at least partly on the verified location of the at least one customer; and
- facilitating establishment of the requested at least one guaranty by at least one guarantor to the at least one vendor on behalf of the at least one customer,
- wherein at least one of the associating, receiving, or facilitating is at least partly implemented using at least one processing device.
2. A system for facilitating guaranty provisioning for an exchange, the system comprising:
- circuitry configured for associating at least one point-of-sale payment tool with at least one product transaction that is related to at least one customer and at least one vendor;
- circuitry configured for determining at least one sale location associated with the at least one point-of-sale payment tool;
- circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location, including at least: circuitry configured for detecting at least one social media entry on a social media account associated with the at least one customer, the at least one social media entry proximate in time to the at least one product transaction; circuitry configured for determining whether the social media account is associated with at least one social media application operational on at least one mobile device associated with the at least one customer, including at least circuitry configured for determining, via image recognition whether the at least one customer is identified in at least one image posted to the at least one social media account; and circuitry configured for verifying, via the detected at least one social media entry, that the at least one mobile device associated with the at least one customer is in the location that corresponds to the determined at least one sale location, including at least circuitry configured for detecting whether at least some data associated with the at least one image indicates that the at least one image was posted from the location that corresponds to the determined at least one sale location;
- circuitry configured for associating at least one requested guaranty with the at least one point-of-sale payment tool based at least partly on the verified location of the at least one customer; and
- circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to the at least one vendor on behalf of the at least one customer.
3. The system of claim 2, wherein the circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer comprises:
- circuitry configured for transmitting one or more messages with respect to at least one guaranty by the at least one guarantor.
4. The system of claim 2, further comprising:
- circuitry configured for obtaining, via the at least one point-of-sale payment tool, one or more transaction characteristics of at least one product transaction that is related to the at least one customer; and
- circuitry configured for generating, via the at least one point-of-sale payment tool, one or more messages to pursue purchase permission with respect to the at least one customer and with at least one guaranty corresponding to the at least one product transaction.
5. The system of claim 4, wherein the circuitry configured for generating, via the at least one point-of-sale payment tool, one or more messages to pursue purchase permission with respect to the at least one customer and with at least one guaranty corresponding to the at least one product transaction comprises:
- circuitry configured for transmitting, from the at least one vendor to the at least one financier, one or more messages to pursue purchase permission.
6. The system of claim 2, further comprising:
- circuitry configured for detecting, via at least one social network server device, at least one pre-qualified proffered guaranty transaction that is associated with the at least one social media account associated with the at least one customer;
- circuitry configured for determining whether the at least one pre-qualified proffered guaranty transaction corresponds to the determined at least one sale location;
- circuitry configured for associating the at least one pre-qualified proffered guaranty transaction with the at least one mobile device based at least partly on the at least one social media account and based at least partly on the circuitry for determining whether the social media account is associated with at least one social media application operational on the at least one mobile device associated with the at least one customer; and
- circuitry configured for proffering, via the at least one social network server device, at least one guaranty based at least partly on at least one social network account associated with the at least one mobile device and based at least partly on the circuitry for verifying that the at least one customer is in a location that corresponds to the at least one sale location.
7. The system of claim 6, wherein the circuitry configured for detecting, via at least one social network server device, at least one proffered guaranty transaction that is associated with at least one product transaction comprises:
- circuitry configured for detecting at least one proffered guaranty transaction via at least one application programming interface (API) exposed by at least one financier.
8. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for receiving at least one activity indicium from at least one wireless service data stream;
- circuitry configured for determining a location of the at least one activity indicium; and
- circuitry configured for determining whether the at least one activity indicium location corresponds to the location of the at least one product transaction.
9. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale comprises:
- circuitry configured for monitoring at least one wireless service data stream to ascertain at least one location that corresponds to the at least one mobile device, the wireless service data stream including data associated with the at least one social media application operational on the at least one mobile device.
10. The system of claim 2, further comprising:
- circuitry configured for obtaining, via the at least one mobile device, at least one transaction characteristic of at least one product transaction that is related to the at least one customer;
- and
- circuitry configured for communicating, via the at least one mobile device, one or more messages to support a provisioning of at least one guaranty corresponding to the at least one product transaction.
11. The system of claim 10, wherein the circuitry configured for communicating, via the at least one mobile device, one or more messages to support a provisioning of at least one guaranty corresponding to the at least one product transaction comprises:
- circuitry configured for communicating with respect to at least one guaranty that is contingent at least partly on verification of at least one transaction characteristic.
12. The system of claim 2, wherein the circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer comprises:
- circuitry configured for notifying, via the at least one social media account and prior to the initiation of the at least one product transaction, at least one potential guarantor of a likely activity or purchase.
13. The system of claim 2, wherein the circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer comprises:
- circuitry configured for communicating with the at least one guarantor via the at least one mobile device.
14. The system of claim 2, further comprising:
- circuitry configured for discovering, via at least one financier server device, at least one authorization request corresponding to at least one product transaction; and
- circuitry configured for providing, via the at least one financier server device, at least one proffered guaranty transaction to the at least one guarantor.
15. The system of claim 14, wherein the circuitry configured for discovering, via at least one financier server device, at least one authorization request corresponding to at least one product transaction comprises:
- circuitry configured for discovering at least one authorization request that includes at least a reference to at least one transaction characteristic corresponding to at least one product transaction.
16. The system of claim 14, wherein the circuitry configured for providing, via the at least one financier server device, at least one proffered guaranty transaction to the at least one guarantor comprises:
- circuitry configured for transmitting at least one proffered guaranty transaction to the at least one guarantor.
17. The system of claim 14, wherein the circuitry configured for providing, via the at least one financier server device, at least one proffered guaranty transaction to the at least one guarantor comprises:
- circuitry configured for providing at least one proffered guaranty transaction that includes at least a reference to at least one transaction characteristic.
18. The system of claim 2, wherein the circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer comprises:
- circuitry configured for detecting, via at least one data provider server device, at least one guaranty opportunity that corresponds to at least one user;
- circuitry configured for receiving, via the at least one data provider server device, at least one data stream event that is associated with the at least one user.
19. The system of claim 18, wherein the circuitry configured for receiving, via the at least one data provider server device, at least one data stream event that is associated with the at least one user comprises:
- circuitry configured for proffering at least one location associated with the at least one user device; and
- circuitry configured for verifying that the location is associated at least one past data stream event.
20. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for searching the at least one social media account via at least one application programming interface (API) exposed by at least one social media network.
21. The system of claim 2, wherein the circuitry configured for facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer comprises:
- circuitry configured for pre-notifying at least one potential would-be guarantor of at least one anticipated location associated with the at least one customer; and
- circuitry configured for signaling agreement to provide at least one guaranty on behalf of the at least one customer.
22. The system of claim 21, wherein the circuitry configured for pre-notifying at least one potential would-be guarantor of at least one anticipated location associated with the at least one customer comprises: circuitry configured for establishing, prior to initiation of the at least one transaction, at least one method of verifying, via the at least one social media application operational on the at least one mobile device associated with the at least one customer, that the at least one customer is present in the at least one sale location.
- circuitry configured for establishing at least one pre-arranged product transaction in the at least one sale location; and
23. The system of claim 21, wherein the circuitry configured for signaling agreement to provide at least one guaranty on behalf of the at least one customer comprises:
- circuitry configured for signaling agreement to provide at least one guaranty on behalf of the at least one customer based at least partly on one or more pre-notified anticipated locations.
24. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location further comprises:
- circuitry configured for obtaining, via at least one background check provider server device, one or more transaction characteristics of at least one product transaction and at least one customer identifier; and
- circuitry configured for checking the one or more transaction characteristics of the at least one product transaction with respect to at least one customer that is identified by the at least one customer identifier.
25. The system of claim 24, wherein the circuitry configured for obtaining, via at least one background check provider server device, one or more transaction characteristics of at least one product transaction and at least one customer identifier comprises:
- circuitry configured for receiving one or more transaction characteristics from the at least one guarantor.
26. The system of claim 24, wherein the circuitry configured for checking the one or more transaction characteristics of the at least one product transaction with respect to at least one customer that is identified by the at least one customer identifier comprises:
- circuitry configured for comparing one or more obtained transaction characteristics to one or more independently-acquired transaction characteristics.
27. The system of claim 2, further comprising:
- circuitry configured for discovering, via at least one combined financier and guarantor server device, at least one authorization request corresponding to at least one product transaction; and
- circuitry configured for instituting, by the at least one combined financier and guarantor server device, at least one guaranty based at least partly on at least one data stream.
28. The system of claim 27, wherein the circuitry configured for discovering, via at least one combined financier and guarantor server device, at least one authorization request corresponding to at least one product transaction comprises:
- circuitry configured for discovering, via at least one past data stream event, that the at least one customer has a relationship that extends beyond a customer-financier relationship.
29. The system of claim 2, wherein the at least one mobile device comprises:
- at least one of a tablet computer or a smartphone.
30. The system of claim 2, wherein the circuitry configured for associating at least one point-of-sale payment tool with at least one product transaction that is related to at least one customer and at least one vendor comprises:
- circuitry configured for detecting that at least one smartphone is being used as at least one payment authorization apparatus, and
- wherein circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location includes at least: circuitry configured for receiving at least one indication that the at least one smartphone is in the possession of at least one authorized user.
31. The system of claim 30, wherein the circuitry configured for receiving at least one indication that the at least one smartphone is in the possession of at least one authorized user comprises:
- circuitry configured for receiving at least one sensor observation associated with the at least one authorized user.
32. The system of claim 31, wherein the circuitry configured for receiving at least one sensor observation associated with the at least one authorized user comprises:
- circuitry configured for receiving at least one of a voice input or an image input associated with the at least one authorized user.
33. The system of claim 30 wherein the circuitry configured for receiving at least one indication that the at least one smartphone is in the possession of at least one authorized user comprises:
- circuitry configured for receiving at least one verbal input associated with the at least one authorized user.
34. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for receiving at least one of a password or code via a user interface.
35. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for receiving at least one indication that the at least one product transaction is associated with at least one product search history associated with the at least one customer.
36. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for receiving at least one indication that the at least one product transaction corresponds to at least one product interest associated with the at least one customer based at least partly on at least one social network post.
37. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for determining at least one social network connection with at least one particular relationship to the at least one customer;
- circuitry configured for detecting at least one location associated with at least one social network data stream event of the at least one social network connection; and
- circuitry configured for determining whether the at least one location corroborates the determined at least one sale location associated with the at least one point-of-sale payment tool.
38. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for detecting that at least one payment application has been activated on at least one mobile device;
- circuitry configured for associating the at least one payment application with the at least one social media application operational on the at least one mobile device;
- and
- circuitry configured for determining whether the at least one customer location associated with the at least one mobile device corresponds to the at least one sale location associated with the at least one point-of-sale payment tool.
39. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location comprises:
- circuitry configured for detecting at least one location associated with at least one social media entry made via the at least one social media application operational on the at least one mobile device, the at least one social media entry implicating that the at least one customer was in the at least one location within a pre-determined timeframe prior to initiation of the at least one product transaction.
40. The system of claim 2, wherein the circuitry configured for determining whether the social media account is associated with at least one social media application operational on at least one mobile device associated with the at least one customer comprises:
- circuitry configured for determining, via image recognition, whether the at least one customer is identified in at least one image posted to the at least one social media account; and
- circuitry configured for determining whether the at least one image was uploaded to the at least one social media account via the at least one application operational on the at least one mobile device associated with the at least one customer.
41. The system of claim 2, wherein the circuitry configured for determining whether the social media account is associated with at least one social media application operational on at least one mobile device associated with the at least one customer comprises:
- circuitry configured for determining whether the at least one social media entry on the social media account associated with the at least one customer was made via the at least one social media application operational on the at least one mobile device, and
- wherein the circuitry configured for verifying, via the detected at least one social media entry, that the at least one mobile device associated with the at least one customer is in the location that corresponds to the determined at least one sale location includes at least: circuitry configured for identifying whether at least one word of the at least one social media entry corresponds to the determined at least one sale location.
42. The system of claim 2, wherein the circuitry configured for verifying that the at least one customer is in a location that corresponds to the at least one sale location-comprises:
- circuitry configured for searching public posts on the at least one social media account via at least one data stream of at least one social media network.
43. An arrangement for facilitating guaranty provisioning for an exchange, the arrangement comprising:
- at least one processing device; and
- at least one memory device operatively coupled to the at least one processing device the at least one memory device bearing one or more instructions that when executed by the at least one processing device configure the at least one processing device to perform on or more operations including at least:
- associating at least one point-of-sale payment tool with at least one product transaction that is related to at least one customer and at least one vendor;
- determining at least one sale location associated with the at least one point-of-sale payment tool;
- verifying that the at least one customer is in a location that corresponds to the at least one sale location, including at least: detecting at least one social media entry on a social media account associated with the at least one customer, the at least one social media entry proximate in time to the at least one product transaction; determining whether the social media account is associated with at least one social media application operational on at least one mobile device associated with the at least one customer, including at least means for determining, via image recognition, whether the at least one customer is identified in at least one image posted to the at least one social media account; and verifying, via the detected at least one social media entry, that the at least one mobile device associated with the at least one customer is in the location that corresponds to the determined at least one sale location, including at least means for detecting whether at least some data associated with the at least one image indicates that the at least one image was posted from the location that corresponds to the determined at least one sale location;
- associating at least one requested guaranty with the at least one point-of-sale payment tool based at least partly on the verified location of the at least one customer; and
- facilitating establishment of at least one guaranty by at least one guarantor to at least one of at least one financier or the at least one vendor on behalf of the at least one customer.
| 6226619 | May 1, 2001 | Halperin et al. |
| 6405177 | June 11, 2002 | DiMattina |
| 7415435 | August 19, 2008 | Weiss et al. |
| 7698227 | April 13, 2010 | Hamilton |
| 7725331 | May 25, 2010 | Schurenberg et al. |
| 7747535 | June 29, 2010 | Mikan et al. |
| 7801808 | September 21, 2010 | Mattison et al. |
| 7917437 | March 29, 2011 | Glasberg |
| 8166068 | April 24, 2012 | Stevens |
| 8290513 | October 16, 2012 | Forstall et al. |
| 8374917 | February 12, 2013 | Trandal et al. |
| 8428964 | April 23, 2013 | Picken |
| 8473382 | June 25, 2013 | Jung et al. |
| 8554670 | October 8, 2013 | Blank et al. |
| 8660943 | February 25, 2014 | Chirehdast |
| 8706648 | April 22, 2014 | Bhola et al. |
| 9119027 | August 25, 2015 | Sharon et al. |
| 9167304 | October 20, 2015 | McDevitt |
| 9300676 | March 29, 2016 | Madhu et al. |
| 20010049636 | December 6, 2001 | Hudda et al. |
| 20020040344 | April 4, 2002 | Preiser et al. |
| 20020178112 | November 28, 2002 | Goeller et al. |
| 20030023541 | January 30, 2003 | Black et al. |
| 20030036993 | February 20, 2003 | Parthasarathy |
| 20030065805 | April 3, 2003 | Barnes, Jr. |
| 20030183689 | October 2, 2003 | Swift et al. |
| 20030187796 | October 2, 2003 | Swift et al. |
| 20040024692 | February 5, 2004 | Turbeville et al. |
| 20040073519 | April 15, 2004 | Fast |
| 20040210527 | October 21, 2004 | Woda et al. |
| 20040215560 | October 28, 2004 | Amalraj et al. |
| 20050049979 | March 3, 2005 | Collins et al. |
| 20050149438 | July 7, 2005 | Williams |
| 20050192884 | September 1, 2005 | Raines |
| 20050246252 | November 3, 2005 | Wallace et al. |
| 20050279827 | December 22, 2005 | Mascavage et al. |
| 20070033113 | February 8, 2007 | Trew |
| 20070067373 | March 22, 2007 | Higgins et al. |
| 20070087756 | April 19, 2007 | Hoffberg |
| 20070174164 | July 26, 2007 | Biffle et al. |
| 20070174208 | July 26, 2007 | Black et al. |
| 20070192144 | August 16, 2007 | Hauer et al. |
| 20070220575 | September 20, 2007 | Cooper et al. |
| 20070266421 | November 15, 2007 | Vaidya et al. |
| 20080052224 | February 28, 2008 | Parker |
| 20080052235 | February 28, 2008 | Mascavage et al. |
| 20080071664 | March 20, 2008 | Silverman et al. |
| 20080109296 | May 8, 2008 | Leach et al. |
| 20080133391 | June 5, 2008 | Kurian et al. |
| 20080133402 | June 5, 2008 | Kurian et al. |
| 20080154625 | June 26, 2008 | Serbanescu |
| 20080162346 | July 3, 2008 | Aaron et al. |
| 20080208681 | August 28, 2008 | Hammad et al. |
| 20080215481 | September 4, 2008 | Schnall |
| 20080221947 | September 11, 2008 | Megdal et al. |
| 20080222038 | September 11, 2008 | Eden et al. |
| 20080262956 | October 23, 2008 | De La Motte |
| 20080281726 | November 13, 2008 | Gupta |
| 20080288299 | November 20, 2008 | Schultz |
| 20090012898 | January 8, 2009 | Sharma et al. |
| 20090030832 | January 29, 2009 | Chien |
| 20090117883 | May 7, 2009 | Coffing et al. |
| 20090228307 | September 10, 2009 | Sorbe |
| 20090271287 | October 29, 2009 | Halpern |
| 20090271342 | October 29, 2009 | Eder |
| 20090289106 | November 26, 2009 | Bishop et al. |
| 20090307778 | December 10, 2009 | Mardikar |
| 20100005021 | January 7, 2010 | Ezekiel et al. |
| 20100042534 | February 18, 2010 | Moran |
| 20100228651 | September 9, 2010 | Becerra et al. |
| 20100250424 | September 30, 2010 | Torres |
| 20100276484 | November 4, 2010 | Banerjee et al. |
| 20100287103 | November 11, 2010 | Mason |
| 20100289659 | November 18, 2010 | Verbil |
| 20100323715 | December 23, 2010 | Winters |
| 20110035318 | February 10, 2011 | Hargrove |
| 20110040691 | February 17, 2011 | Martinez et al. |
| 20110072497 | March 24, 2011 | Vishik et al. |
| 20110112957 | May 12, 2011 | Ingram et al. |
| 20110162038 | June 30, 2011 | Chunilal |
| 20110191150 | August 4, 2011 | Blackhurst et al. |
| 20110191160 | August 4, 2011 | Blackhurst et al. |
| 20110191162 | August 4, 2011 | Blackhurst et al. |
| 20110208822 | August 25, 2011 | Rathod |
| 20110246306 | October 6, 2011 | Blackhurst et al. |
| 20110251922 | October 13, 2011 | Cavagnaro |
| 20110258118 | October 20, 2011 | Ciurea |
| 20110276396 | November 10, 2011 | Rathod |
| 20110320341 | December 29, 2011 | Kremen |
| 20110320342 | December 29, 2011 | Kremen |
| 20120011056 | January 12, 2012 | Ward et al. |
| 20120022944 | January 26, 2012 | Volpi |
| 20120029990 | February 2, 2012 | Fisher |
| 20120030109 | February 2, 2012 | Dooley Maley et al. |
| 20120030110 | February 2, 2012 | Prakash et al. |
| 20120066128 | March 15, 2012 | Mumm |
| 20120072311 | March 22, 2012 | Khan |
| 20120078727 | March 29, 2012 | Lee |
| 20120084131 | April 5, 2012 | Bergel et al. |
| 20120084349 | April 5, 2012 | Lee et al. |
| 20120157062 | June 21, 2012 | Kim et al. |
| 20120159647 | June 21, 2012 | Sanin et al. |
| 20120166261 | June 28, 2012 | Velusamy et al. |
| 20120191594 | July 26, 2012 | Welch et al. |
| 20120215681 | August 23, 2012 | Jenkins |
| 20120215717 | August 23, 2012 | Arnott et al. |
| 20120221357 | August 30, 2012 | Krause et al. |
| 20120233009 | September 13, 2012 | Fougner et al. |
| 20120245971 | September 27, 2012 | Reichman et al. |
| 20120253913 | October 4, 2012 | Postrel |
| 20120259776 | October 11, 2012 | Bajaj et al. |
| 20120270560 | October 25, 2012 | Moshir et al. |
| 20120271692 | October 25, 2012 | Huang et al. |
| 20120271946 | October 25, 2012 | Choti et al. |
| 20120290329 | November 15, 2012 | Ross |
| 20120290389 | November 15, 2012 | Greenough et al. |
| 20120295580 | November 22, 2012 | Corner |
| 20120302256 | November 29, 2012 | Pai et al. |
| 20120303425 | November 29, 2012 | Katzin et al. |
| 20120310836 | December 6, 2012 | Eden et al. |
| 20130006844 | January 3, 2013 | Kremen |
| 20130006845 | January 3, 2013 | Kremen |
| 20130031162 | January 31, 2013 | Willis et al. |
| 20130036001 | February 7, 2013 | Wegner et al. |
| 20130046561 | February 21, 2013 | Sorbe |
| 20130046692 | February 21, 2013 | Grigg et al. |
| 20130054447 | February 28, 2013 | Ross et al. |
| 20130073387 | March 21, 2013 | Heath |
| 20130085877 | April 4, 2013 | Ruhrig |
| 20130091058 | April 11, 2013 | Huster |
| 20130103577 | April 25, 2013 | Lawson et al. |
| 20130110597 | May 2, 2013 | Blair et al. |
| 20130110598 | May 2, 2013 | Blair et al. |
| 20130117832 | May 9, 2013 | Gandhi |
| 20130144785 | June 6, 2013 | Karpenko et al. |
| 20130151415 | June 13, 2013 | Ruckart |
| 20130185189 | July 18, 2013 | Stewart |
| 20130185206 | July 18, 2013 | Leggett et al. |
| 20130191247 | July 25, 2013 | Huang et al. |
| 20130212004 | August 15, 2013 | Itwaru |
| 20130218753 | August 22, 2013 | Oikonomidis |
| 20130226687 | August 29, 2013 | Perry et al. |
| 20130226798 | August 29, 2013 | Orttung et al. |
| 20130239185 | September 12, 2013 | Orttung et al. |
| 20130239217 | September 12, 2013 | Kindler et al. |
| 20130282546 | October 24, 2013 | Kadiwar |
| 20130297493 | November 7, 2013 | Linden et al. |
| 20140040086 | February 6, 2014 | Abbatiello et al. |
| 20140067650 | March 6, 2014 | Gardiner et al. |
| 20140067656 | March 6, 2014 | Cohen Ganor et al. |
| 20140081729 | March 20, 2014 | Ocher |
| 20140081750 | March 20, 2014 | Hosp |
| 20140122225 | May 1, 2014 | Vashtimal et al. |
| 20140164058 | June 12, 2014 | Hammock et al. |
| 20140172679 | June 19, 2014 | Shimko |
| 20140201100 | July 17, 2014 | Rellas et al. |
| 20140214819 | July 31, 2014 | Aitchison |
| 20140274122 | September 18, 2014 | Tseng et al. |
| 20140279543 | September 18, 2014 | Ruhrig |
| 20150120530 | April 30, 2015 | Jung et al. |
| 20150278773 | October 1, 2015 | Rolf et al. |
| 20170286953 | October 5, 2017 | Hammad et al. |
| 20170323354 | November 9, 2017 | Martell |
| 2004-341597 | December 2004 | JP |
| 2012/0010869 | February 2012 | KR |
| WO 2013/124290 | August 2013 | WO |
- Fodor's Travel Forums “Do you notify your credit card company when you travel?” Posted Sep. 22-24, 2006.
- Google Wallet training video available at https://www.youtube.com/watch?v=hLbmy4XQsMo, Sep. 21, 2011.
- Web Photos That Reveal Secrets, Like Where You Live, Kate Murphy, Aug. 11, 2010 (Year: 2010).
- Could you fall victim to crime simply by geotagging location info to your photos? By Bill Schiffner—Posted on Jul. 22, 2013 (Year: 2013).
- PCT International Search Report; International App. No. PCT/US2014/062648; dated Jan. 27, 2015; pp. 1-4.
- PCT International Search Report; International App. No. PCT/US2014/062639; dated Feb. 5, 2015; pp. 1-4.
- Extended European Search Report; European App. No. EP 14 85 9208; dated Mar. 17, 2017 (Mar. 24, 2017) pp. 1-7.
Type: Grant
Filed: Oct 29, 2013
Date of Patent: Apr 3, 2018
Patent Publication Number: 20150120500
Assignee: Elwha LLC (Bellevue, WA)
Inventors: Edward K. Y. Jung (Bellevue, WA), Richard T. Lord (Tacoma, WA), Robert W. Lord (Seattle, WA)
Primary Examiner: Ethan D Civan
Assistant Examiner: Ming Shui
Application Number: 14/066,580
International Classification: G06Q 30/06 (20120101); G06Q 20/12 (20120101);
