Patent Grant
9953334
This application for letters patent disclosure document describes inventive aspects directed at various novel innovations (hereinafter “disclosure”) and contains material that is subject to copyright, mask work, and/or other intellectual property a protection. The respective owners of such intellectual property have no objection to the facsimile reproduction of the disclosure by anyone as it appears in published Patent Office file/records, but otherwise reserve all rights.
The present innovations are directed generally to electronic payment, and more particularly, to ELECTRONIC COUPON ISSUANCE AND REDEMPTION APPARATUSES, METHODS AND SYSTEMS.
Consumers may use a coupon to purchase products with a merchant. For example, a consumer may present a paper coupon to a cashier at a point of sale (POS) terminal at a merchant store in order to get a discount on a purchase. The cashier may a charge the consumer an amount equivalent to the original price of the product minus a discount amount specified by the coupon. The merchant store may recover the discounted amount from a coupon provider.
The accompanying appendices and/or drawings illustrate various non-limiting, example, innovative aspects in accordance with the present descriptions:
The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number lot would be found and/or introduced in
ELECTRONIC COUPON ISSUANCE AND REDEMPTION APPARATUSES, METHODS AND SYSTEMS (hereinafter “ECIR”) transforms user coupon purchase and redemption request inputs via ECIR components into coupon issuance, transaction, and analytics outputs. The ECIR also provides a platform for social network coupon issuance, redemption, authentication, and payment authorization, clearance, and settlement.
In one embodiment, coupons, offers, rewards, and/or the like (“coupon”), issued by different entities (e.g., group buying companies, social network program, and/or the like (“GBC”)) may require consumers to pay in advance to purchase the coupon before the coupon can be redeemed at a merchant store. For example, a consumer may see an advertisement at a group buying company's (“GBC”) website for “pay only $6 for a $12 movie ticket at Movie Theatre ABC,” and may pay a fee to purchase the coupon to redeem it later at the theatre. Upon paying the $6, the consumer may receive the coupon via emails which includes the details of the coupon. When redeeming the coupon at the merchant, the theatre may type in the details of the coupon into the merchant's client devices (e.g., a Point of Sale (“POS”) terminal). If the coupon has not been redeemed before, the merchant may receive an approval and the consumer may receive the movie ticket. In some implementations, the coupon may be text-messaged to the consumer, sent to the consumer's mobile device application, and/or mailed to the consumer's address in paper or in other physical forms (e.g., cards). In some implementations, a coupon may be displayed in a newspaper, magazine, website, video content, and/or the like. The coupon may include a Quick-Response (QR), barcode and/or like code encoding information about the coupon (e.g., merchant name, product type, offer details, expiry date, redeemable stores, conditions for redemption, and/or the like). A consumer desiring to acquire the coupon may utilize a consumer device (e.g., smartphone, laptop, tablet computer, etc.) including an image capture device (e.g., camera, webcam, etc.) to snap a picture of the code. The consumer device may, in some implementations, extract the information embedded in the code. In some implementations, the consumer device may be associated with a virtual wallet account of the consumer. In such implementations, the consumer device may add the coupon to the virtual wallet account of the consumer, for immediate or later use, for sharing with others, to use as a seed for searching for other relevant coupons, etc.
In one embodiment, the ECIR server may generate a prepaid account associated with each coupon. The prepaid account may be in the form of an account number (e.g., a Virtual Payment System (“VPS”) number, a barcode, a Quick Response (“QR”) code, etc.), a physical card with an account number, a physical card with magnetic stripe, a physical card with Radio-frequency Identification (“RFID”), and/or the like (“account”, “prepaid account”, “prepaid coupon account” or “coupon account”). When the consumer receives the coupon, which may be electronic, in paper, or by mail, it may also include the prepaid account information.
In one embodiment, the prepaid account may be associated with a specific consumer and used for different coupons with different merchants. In another embodiment, the prepaid account may be unique for each coupon and each consumer. It may be redeemed only once.
In one embodiment, when the consumer redeems the coupon at the merchant for goods and/or services, merchant employees may type the prepaid account VPS number (or swipe the card if the physical card has a magnetic stripe) into the POS terminal or other merchant devices. If the value associated with the offer hasn't yet been redeemed, the merchant may receive an approval through the ECIR payment system and funds may be transferred from the prepaid account to the merchant, in which way real-time payments, settlement and reporting may be facilitated.
In an alternative embodiment, the consumer may use a camera-enabled mobile phone to scan the QR code or the barcode associated with the coupon. The QR code or the barcode may be provided when coupon is made available electronically, in paper, and/or the like. Upon scanning the code, the consumer's mobile phone may retrieve the information related to the coupon and redeem the coupon by providing the mobile phone page to the merchant.
In another embodiment, the consumer may choose not to deposit fund into the prepaid account. The coupon may be delivered to the consumer free of charge. Upon redemption, merchant may swipe the consumer's personal charge card (e.g., credit card, debit card, gift card, etc.) and type into the discretionary field the amount of the discounted value in the coupon. Therefore, the consumer may be charged only by the amount in difference. In the example of the movie ticket coupon, the consumer may receive the coupon free of charge and present the coupon to the movie theatre employee. The employee may charge the consumer's credit card for the $12 movie ticket. In the discretionary field of the payment processing user interface, the employee may type in the discounted amount of $6. The consumer's credit card may be charged a net amount of $6 for the movie ticket.
In yet another embodiment, the consumer may receive the coupon free of charge. The prepaid account associated with the coupon may be deposited with a value by the coupon issuer entity and/or the like. The merchant may charge the original value (e.g., $12 for the movie ticket) to the consumer's personal charge card. The merchant may type the prepaid account VPS number (or swipe the card if the physical card has a magnetic stripe) into the POS terminal, and credit the coupon value (e.g., $6) back to the consumer's personal charge card.
In one embodiment, if customers choose to participate and enroll, the ECIR may facilitate the GBC or other coupon issuer companies assessing customers' purchasing habits associated with the coupon issuance event. In one implementation, the ECIR may identify the customer's personal charge card based on the customer's name provided when purchasing the coupon, and/or the personal charge card used to purchase the coupon. ECIR may analyze customer's transaction data associated with their personal charge card and compare the statistics before and post the coupon redemption date, e.g., No. of transactions made at a specific merchant, total amount spent at a specific merchant. The analysis may provide the merchant and/or coupon issuing company a report of the loyalty of customers, i.e., how often the customer returns to the merchant after the customer redeems the coupon, etc. The analytics may also generate other uses, for example, the ECIR may facilitate the coupon issuing companies tailoring specific coupons and/or offers based on customer's spending history; the ECIR may utilize the purchase data of enrolled consumers to determine the location of the consumer's purchase and to trigger alerts of coupons and/or offers through email, messages, and/or mobile applications; and the ECIR may enable improved participation of merchants by utilizing the transaction data of enrolled consumers to control distribution of offer/and coupons.
In some embodiments, the ECIR server may facilitate with the coupon redemption process. The consumer 102 may bring the coupon 107 to the merchant 104 to redeem the coupon. The merchant employee may type in the VPS # and the expiration date on the coupon to verify the validity of the coupon (e.g., if the coupon has been redeemed before, etc.) and to authorize the coupon 1008. The consumer may receive the goods and/or services upon the authorization. In some implementations, the merchant employee may scan the coupon if it contains a barcode, a QR code or RFID. The coupon may also be swiped if a magnetic stripe is present.
In some embodiments, when redeeming the coupon at the merchant store 131, the consumer may present the printed coupon (or the physical card) to the merchant employee, or the consumer may also present coupon via mobile device applications. The ECIR may query the database and verify that the coupon has not been used before, and/or it is not an expired coupon 132. Upon verification, the ECIR server may authorize the redemption and process the transaction 133. In some embodiments, the ECIR server may also settle the funds distribution based on the pre-determined group buying company and merchant agreement 134.
In some embodiments, the ECIR server may provide a prepayment and authentication platform for social network coupon offers, which may associate a ECIR account number with a social network coupon offer and may verify the validity of the social network coupon offer.
In one embodiment, a consumer may pay a group buying company and/or a social network program to participate in offers and/or rewards with a specific merchant. For example, the consumer may see an advertisement in the newspaper for “Join us for $1.99 per month and enjoy free-shipping any purchase on buygoods.com,” and may pay a monthly fee to the advertisement sponsor to redeem free-shipping services on the specified merchant “buygoods.com.” Within implementations, upon joining the program, the consumer may receive an offer via a print-at-home paper offer or via a mobile web page/text message. For example, a paper free-shipping coupon may be mailed to the consumer, and/or a free-shipping code may be emailed, text-messaged to the consumer.
In one embodiment, the offer may be a private coupon with a private label, e.g., a ECIR account number registered by the ECIR platform with a group buying company. The ECIR may receive an indication of the coupon issuance and associate an account number with the issued coupon. For example, the ECIR may request the consumer open an ECIR in order to redeem the coupon. For another example, the ECIR may associate a consumer's bank account number with the issued coupon. For another example, the ECIR may request the consumer provide a unique password to be associated with the coupon.
In one embodiment, the issued offer coupon may be redeemed for goods and/or services from the merchant for an agreed upon amount between the group buying company and the merchant. The merchant may authenticate the offer by a entering the account number into their POS. If the value associated with the offer hasn't yet been redeemed, the merchant will receive an approval via the offer program manager through the ECIR payment system and then the merchant would be paid, in which way real-time payments, settlement and reporting may be facilitated.
As shown in
For example, in one implementation, a Consumer 142 may select a group buying offer for a merchant, and provide a financial account number (e.g., a ECIR account number, a credit card number, a debit card number, etc.) to purchases the offer. In one implementation, the card number and the purchased coupon may be submitted to a group buying company 170.
In one embodiment, the ECIR platform 160 may query its database 119 to determine whether the offer has been redeemed by verifying the coupon amount associated with the consumer account number with an offer issuer 155.
In one implementation, the offer issuer may generate reports summarizing the issued offers and redemption of the offers with a group buying company 170. For example, the issuer may notify the group buying company 170 about the number of consumers participating in a group buying program, the amount of purchased products, and/or the like, on a periodic basis.
In one implementation, for each issued offer, the group buying company 170 may send a “Get Inventory Control Request” to obtain an account number, e.g., 16 digit account number from the ECIR server. The ECIR server may generate an account number and other information to an offer issuer 172.
In an alternative implementation, the group buying company 130 may send a “Get Instant Issue Request” to get standardized cardholder address and verify the account number from the ECIR server 160, wherein the ECIR server may send information comprising a standardized address and account number verification to an offer issuer.
In another implementation, the group buying company may send an “Offer Issuance Request” 173 with buyer and cardholder information (including standardized address) to have the ECIR issue active virtual cards comprising coupon offers. The ECIR server may in turn send the Offer Issuance Request 174 to an offer issuer with one of the following: 1) Limit error message or 2) Buyer and cardholder Alias ID's and other information indicating successful issuance.
In one embodiment, through the above interface between the group buying company and the ECIR server, the group buying company may provide the merchant ID for that range of issued accounts.
In one implementation, a consumer may obtain a voucher via the internet/browser, mobile message, emails, and/or the like, from the group buying company that contains the offer terms and conditions, and also contains the 16 digit account number, expiration date and the transaction amount of the value of each offer, a e.g. merchant offers to the consumer for $30 the opportunity to receive Tea for Two Of $30, group buying company keeps $5. On the coupon certificate with the account number is instruction for merchant to enter $25 for purchase amount in their POS system at time of purchase.
In one implementation, the consumer 142 may submit an offer redemption request 175, e.g., at a POST terminal with the merchant store. The merchant 145 may initiate authorization of the discount amount specified by the offer 176.
Within implementations, authorization request may be routed through ECIR server which may check available balance associated with the account number 177 and merchant information to ensure the offer is being used at the participating merchant, and has not been used before. If the merchant information is correct, and the balance is sufficient, the offer is approved 179. Otherwise, if the merchant information does not match the stored record, or the offer has already been redeemed, the ECIR server may send a notification to direct to customer service 178. The group buying company may confirm the received information of payment transaction 180.
At the end of the day the merchant may submit this transaction in their clearing file with the rest of their ECIR purchases for offer redemptions.
In a further implementation, the ECIR may include API feature that the group buying company may utilize to obtain a new account number to put on each certificate as they render them. The ECIR may provide web services to allow configurations which facilitate the group buying company to interact with the ECIR server.
In a further implementation, selective acceptance may be performed by the ECIR server during the offer authentication. For example, the ECIR may apply restrictive authorization procedures built into the server including merchant ID filtering, Merchant Category Code (MCC), and limits/thresholds that can be set.
In a further implementation, an issue BIN may be installed at the ECIR to support the virtual card account activity, and track balances. An API may be provided to the group buying company for certificate rendering.
In a further implementation, the ECIR may keep track of transactions of a consumer and qualify the consumer for a loyalty program, e.g., special promotions for brand products.
In some implementations, the client may generate a coupon purchase order message, e.g., 212, and provide, e.g., 213, the generated coupon purchase order message to the GBC server. For example, a browser application executing on the client may provide, on behalf of the user, a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) GET message including the product order details for the GBC server in the form of data formatted according to the eXtensible Markup Language (“XML”). Below is an example HTTP(S) GET message including an XML-formatted purchase order message for the GBC server:
In some implementations, the GBC server may obtain the purchase order message from the client, and may parse the purchase order message to extract details of the purchase order from the user. The GBC server may generate an account issuance request, e.g., 214 to issue a prepaid account and/or a VPS #. In one implementation, the account issuance request may be sent 215 to an issuer server 204. For example, an issuer server may be a server of an issuer financial institution (“issuer”) maintaining an account of the GBC. For example, a browser application executing on the GBC server may provide a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) GET message including the coupon details for the GBC server in the form of data formatted according to the eXtensible Markup Language (“XML”). Below is an example HTTP(S) GET message including an XML-formatted account issuance message for the GBC server:
The issuer server may process the account issuance request 216 to comply with the issuer's rules and regulations. The account issuance request may be sent to the ECIR server 217. The ECIR server 205 may generate 218 the account and an account issuance message 220. In some implementations, the account issuance message may include details such as, but not limited to: account details of the user, user billing and/or shipping information, coupon details, and/or the like. For example, the ECIR server may provide a HTTP(S) POST message including an XML-formatted account issuance message similar to the example listing provided below:
In one embodiment, the user data and the account data may be stored 219 in a user profile database 206. The generated account issuance message may be sent back to the issuer server 220 and GBC server 221. The GBC server may composite coupon with the generated account information, e.g., VPS #, and generate coupon activation message 222 (e.g., Email, SMS, wallet notification, etc.), which may be sent 223 back to the client device for display 224.
In another embodiment, the account issuance request may be sent to the ECIR server directly 215b. The ECIR generated account issuance message may be sent to the GBC server directly 221b.
In some embodiments, the ECIR may generate an account activation request 315 and send to the GBC server. The GBC server may obtain and parse account activation request 316 to composite coupon with the account information 317. The details of the composition process are discussed in
In some embodiments, the GBC generated account issuance request 306 may be sent directly to the ECIR server 309.
In some embodiments, if not enough people has signed up for the coupon but the coupon is still in its active time window 321, the GBC may generate “on hold” message 327 to inform the user that there has not been enough people signing up for the coupon. In some implementations, the user may choose to wait till the minimum number of people has reached and continue with the coupon process. In some implementations, the user may choose to withdraw and charged funds may be credited back to the user. The “on-hold” message may be sent to the user/client to display 328. In some embodiments, if the user chooses to wait for other people to sign-up and continue with purchasing the coupon, the GBC server may check periodically if the number of people has reached the minimum. If the minimum has been reached 330, the GBC may continue with the account issuance process to generate an account issuance request 306 as discussed in
In some embodiments, the issuer server may generate an account query request, e.g., 374, to determine whether the transaction can be processed. For example, the issuer server may process the transaction only if the account has sufficient funds to pay for the purchase in the account provided. The issuer server may obtain and parse the account query request 375, and generate an account authorization request, e.g., 376, using the obtained account query request, and provide the account authorization request to the ECIR server. In some implementations, the ECIR server may obtain the account authorization request from the issuer server, and may parse the account authorization request to extract details of the request 377. Using the extracted fields and field values, the ECIR server may generate a query, e.g., 378, for the GBC's issuer server corresponding to the account. In response to obtaining the GBC's issuer server query the pay network database may provide, e.g., 379, the requested issuer server data to the ECIR server. In some implementations, the ECIR server may utilize the GBC's issuer server data to generate a forwarding account authorization request, e.g., 380, to redirect the account authorization request from the ECIR server to the GBC's issuer server. The ECIR server may provide the account authorization request to the issuer server 381. Upon receiving an authorization message from the issuer server 382, the ECIR server may parse the authorization message to extract the transaction data, and generate a transaction data record, e.g. 383. The ECIR server may provide the transaction data record for storage, e.g., 384, to a database. Using the extracted transaction data, the ECIR server may charge the fund the GBC's issuer server 385 to the prepaid account. The ECIR server may generate a “funds transferred” message to the GBC server. The client may render and display, e.g., 386, the message.
In some embodiments, if the coupon is delivered as a print-out by mail 341, the GBC server may generate a QR code or a barcode including the obtained fields 342, and composite fields with the QR/barcode into the retrieved template 343, which may enable quick identification of the coupon and user's information during redemption. The GBC server may query the user profile database to retrieve the user's mailing address 344 and print and mail the coupon to the user 345.
In some embodiments, if the coupon is delivered as a physical card by mail 346, the GBC server may determine if a magnetic stripe or an RFID is required 347. If a magnetic stripe or an RFID is required, the GBC server may encode obtained fields (e.g., user name, coupon contents, merchant, VSP#, etc.) into the magnetic stripe or RFID 348. The GBC server may query the user profile database to retrieve the user's mailing address 349 and produce and mail the card to the user 350. If a magnetic strip or an RFID is not required, the GBC server may generate a QR code or a barcode including the obtained fields 392, and composite fields with the QR/barcode into the retrieved template 393, which may enable quick identification of the coupon and user's information during redemption. The GBC server may query the user profile database to retrieve the user's mailing address 394 and print and mail the coupon to the user 395.
In some embodiments, once the GBC server produces and delivers the coupon, the user's client may receives and displays coupon activation message 318, as discussed
In some embodiments, if the coupon does not have any of the categories, the GBC server may generate “no coupon category available” message 391.
In some implementations, the merchant's client may generate a coupon redemption message, e.g., 412, and provide, e.g., 413, the generated coupon redemption message to the merchant server. For example, a browser application executing on the client may provide, on behalf of the user, a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) GET message including the coupon details for the merchant server in the form of data formatted according to the eXtensible Markup Language (“XML”). Below is an example HTTP(S) GET message including an XML-formatted coupon redemption message for the merchant server:
In some implementations, the merchant server may obtain the coupon redemption message from the client, and may parse the coupon redemption message to extract details of the coupon from the user. The merchant server may generate an authentication request, e.g., 414 to determine whether the transaction can be processed. For example, the merchant server may attempt to determine whether the user has sufficient funds to pay for the purchase in an account provided with the coupon redemption. The merchant server may provide the authorization request, e.g., 415, to an acquirer server, e.g., 404. For example, the acquirer server may be a server of an acquirer financial institution (“acquirer”) maintaining an account of the merchant. For example, the proceeds of transactions processed by the merchant may be deposited into an account maintained by the acquirer. In some implementations, the account query request may include details such as, but not limited to: the costs to the user involved in the transaction, account details of the user, user billing and/or shipping information, and/or the like.
In some implementations, the acquirer server may generate an account authorization request, e.g., 416, using the obtained account query request, and provide the account authorization request, e.g., 417, to the ECIR server, e.g., 405. For example, the acquirer server may redirect the HTTP(S) POST message in the example above from the merchant server to the ECIR server.
In some implementations, the ECIR server may obtain the account authorization request from the acquirer server, and may parse the account authorization request to extract details of the request. Using the extracted fields and field values, the ECIR server may generate a query, e.g., 418, for an issuer server corresponding to the user's account. For example, the user's account, the details of which the user may have provided via the coupon redemption message, may be linked to an issuer financial institution (“issuer”), such as a banking institution, which issued the account for the user. An issuer server, e.g., 406, of the issuer may maintain details of the user's account. In some implementations, a database, e.g., pay network database 407, may store details of the issuer servers and account numbers associated with the issuer servers. For example, the database may be a relational database responsive to Structured Query Language (“SQL”) commands. The ECIR server may execute a hypertext preprocessor (“PHP”) script including SQL commands to query the database for details of the issuer server. An example PHP/SQL command listing, illustrating substantive aspects of querying the database, is provided below:
In response to obtaining the issuer server query, e.g., 419, the pay network database may provide, e.g., 420, the requested issuer server data to the ECIR server. In some implementations, the ECIR server may utilize the issuer server data to generate a forwarding account authorization request, e.g., 421, to redirect the account authorization request from the acquirer server to the issuer server. The ECIR server may provide the account authorization request, e.g., 422, to the issuer server. In some implementations, the issuer server, e.g., 406, may parse the account authorization request, and based on the request details may query a database, e.g., user profile database 408, for data of the user's card account. For example, the issuer server may issue PHP/SQL commands similar to the example provided below:
In some implementations, on obtaining the user data, e.g., 425, the issuer server may validate the account by determining whether the user can pay for the transaction using funds available in the account, and/or whether the coupon has been used before, e.g., 426. For example, the issuer server may determine whether the user has a sufficient balance remaining in the account, sufficient credit associated with the account, and/or the like. If the issuer server determines that the user can pay for the transaction using the funds available in the account, the server may generate 429 and provide an authorization message, e.g., 430, to the ECIR server. For example, the server may provide a HTTP(S) POST message similar to the examples above.
In some implementations, the ECIR server may obtain the authorization message, and parse the message to extract authorization details. Upon determining that the user possesses sufficient funds for the transaction, the ECIR server may generate a a transaction data record, e.g., 431, from the account authorization request it received, and store, e.g., 432, the details of the transaction and authorization relating to the transaction in a database, e.g., transactions database 410. For example, the ECIR server may issue PHP/SQL commands similar to the example listing below to store the transaction data in a database:
In some implementations, the ECIR server may forward the authorization message, e.g., 433, to the acquirer server, which may in turn forward the authorization message, e.g., 434, to the merchant server. The merchant may obtain the authorization as message, and determine from it that the user possesses sufficient funds in the account to conduct the transaction. The merchant server may add a record of the transaction for the user to a batch of transaction data relating to authorized transactions. For example, the merchant may append the XML data pertaining to the user transaction to an XML data file comprising XML data for transactions that have been authorized for various users, e.g., 435, and store the XML data file, e.g., 436, in a database, e.g., merchant database 409. For example, a batch XML data file may be structured similar to the example XML data structure template provided below:
In some implementations, the server may also generate a purchase receipt, e.g., and provide the purchase receipt to the client 437. The client may render and display, e.g., 438, the purchase receipt for the user. For example, the client may render a webpage, electronic message, text/SMS message, buffer a voicemail, emit a ring tone, and/or play an audio message, etc., and provide output including, but not limited to: sounds, music, audio, video, images, tactile feedback, vibration alerts (e.g., on vibration-capable client devices such as a smartphone etc.), and/or the like.
In some embodiments, the authentication 415 may optionally be filtered through fraudulent detection (e.g., cyber source, etc.) 452.
In some embodiments, the ECIR Real-Time Messaging (“RTM”) server 450 may optionally sends RTM notifications to the user 451. The RTM notifications may include customized offers issued to customers based on the spend history of their financial card, and/or the like. Details are discussed in
In some implementations, the ECIR server may obtain the authorization message, and parse the message to extract authorization details 531. Upon determining that the coupon is valid and/or the user possesses sufficient funds for the transaction (e.g., 532, option “Yes”), the ECIR server may extract the transaction card from the authorization message and/or account authorization request, e.g., 533, and generate a transaction data record, e.g., 534, using the account transaction details. The ECIR server may provide the transaction data record for storage, e.g., 535, to a database. In some implementations, the ECIR server may forward the authorization message, e.g., 536, to the acquirer server, which may in turn forward the authorization message, e.g., 537, to the merchant server. The merchant may obtain the authorization message, and parse the authorization message o extract its contents, e.g., 538. The merchant server may determine whether the user possesses sufficient funds in the account to conduct the transaction. If the merchant server determines that the user possess sufficient funds, e.g., 539, option “Yes,” the merchant server may add the record of the transaction for the user 542 to a batch of transaction data relating to authorized transactions, e.g., 543. The merchant server may also generate a purchase receipt, e.g., 544, for the user. If the merchant server determines that the user does not possess sufficient funds, e.g., 539, option “No,” the merchant server may generate an “authorization fail” message, e.g., 540. The merchant server may provide the purchase receipt or the “authorization fail” message to the client. The client may render and display, e.g., 541, the purchase receipt for the user.
In an alternative embodiment, upon inputting the user's personal account information into the merchant device, the ECIR server may query the database and determine if there is an active coupon associated with the user, without entering the coupon account information. For example, the user may swipe personal credit card at a merchant POS to purchase a product. The credit card information may be provided to the ECIR server to process the transaction. The ECIR server may parse the credit card account information to retrieve the user name or other account information. The ECIR server may query database for coupon information that user has purchased that relates to the merchant. If a related coupon is identified, the ECIR server may automatically process the coupon account information so that the user may receive the purchased product at a discounted price that the coupon provides.
With reference to
In some implementations, the client may generate a purchase order message, and provide the generated purchase order message to the merchant server. For example, a browser application executing on the client may provide, on behalf of the user, a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) GET message including the product order details for the merchant server in the form of data formatted according to the eXtensible Markup Language (“XML”). Below is an example HTTP(S) GET message including an XML-formatted purchase order message for the merchant server:
The ECIR server may determine a payment amount based on the retrieved agreement data, and generate an individual payment request, e.g., 748, for each transaction for which it has extracted transaction data, and provide the individual payment request, e.g., 749, to the issuer server, e.g., 706. For example, the ECIR server may provide a HTTP(S) POST request similar to the example below:
In some implementations, the issuer server may generate a payment command, e.g., 750. For example, the issuer server may issue a command to deduct funds from the user's account (or add a charge to the user's credit card account). The issuer server may issue a payment command, e.g., 751, to a database storing the user's account information, e.g., user profile database 708. The issuer server may provide a funds transfer message, e.g., 752, to the ECIR server, which may forward, e.g., 753, the funds transfer message to the acquirer server. An example HTTP(S) POST funds transfer message is provided below:
In some implementations, the acquirer server may parse the funds transfer message, and correlate the transaction (e.g., using the request_ID field in the example above) to the merchant. The acquirer server may then transfer the funds specified in the funds transfer message to an account of the merchant, e.g., 754.
In some implementations, the issuer server may obtain the individual payment request, and parse, e.g., 844, the individual payment request to extract details of the request. Based on the extracted data, the issuer server may generate a coupon data query 845 to retrieve the coupon issuance agreement between the merchant and the GBC. Upon receiving the coupon data from the coupon database 846, the issuer server may generate a payment command, e.g., 847. For example, the issuer server may issue a command to deduct funds from the user's account (or add a charge to the user's credit card account). The issuer server may issue a payment command, e.g., 848, to a database storing the user's account information. In response, the database may update a data record corresponding to the user's account to reflect the debit/charge made to the user's account. The issuer server may provide a funds transfer message, e.g., 849, to the ECIR server after the payment command has been executed by the database.
In some implementations, the ECIR server may check whether there are additional transactions in the batch that need to be cleared and funded. If there are no additional transactions, the ECIR server may generate, e.g., 850, an aggregated funds transfer message reflecting transfer of all transactions in the batch, and provide, e.g., 851, the funds transfer message to the acquirer server. The acquirer server may, in response, transfer the funds specified in the funds transfer message to an account of the merchant, e.g., 852.
In one embodiment, the ECIR server may facilitate a “full dollar” model when issuing the coupon. Under the “full dollar” model, the prepaid coupon account may be funded upon issue with the net amount due to the merchant. When the coupon a is redeemed, the merchant may discount the purchase price for the gross coupon amount and key-in the account number, expiration date, and/or any other values through their existing POS application. For example, under a $25 coupon for $50 value model, if the consumer pays $25 for the coupon, the prepaid coupon account may be deposited with $25. The merchant may initiate the transaction for $25. The merchant may receive $25 from the transaction within their daily settlement file. In another example, if the consumer pays $25 for the coupon, the GBC may keep $10 and pays the merchant $15. Thus the prepaid coupon account may be funded with $15 and the merchant may initiate the transaction for $15. The merchant may receive $15 from this transaction within their daily settlement file. This model may eliminates the need for GBC remit separate payments to the merchant.
In an alternative embodiment, the ECIR server may facilitate a “nominal dollar” model. Under this model, the prepaid coupon account may be funded upon issue with a nominal dollar amount due to the merchant. For example, in a $25 coupon for $50 value model, the prepaid coupon account may be funded with $0.10. When the coupon is redeemed, the merchant may discount the purchase price for the gross coupon amount and key-in the agreed nominal amount of $0.10, account number, expiration date, and/or any other values through their existing POS application. The merchant may receive $0.10 from this transaction within their daily settlement file. GBC may settle the rest of the fund with the merchant at a later time.
In some embodiments, with the analytics data, the ECIR server may facilitate the coupon issuer company (e.g., GBC) and/or the merchant to tailor the coupons in the future to help improve sales. The ECIR server may provide analysis may include, but not limited to: how often a consumer comes back to the merchant after a coupon is redeemed at the merchant; how quickly a consumer goes to the merchant to redeem the coupon, and/or the like. The ECIR server may also provide analysis such as tailoring specific offers sent to customers based on the spend history of the enrolled card to help improve sales; utilizing the live card purchase data of enrollees to determine the location (or other triggering factors) of the consumer's purchase and to trigger alerts of coupons through SMS, Email or Mobile Applications; enabling improved participation of merchants by utilizing the transaction data of enrolled consumers to control distribution to control distribution of offers and to create offers tailored to consumers spend with merchant on the enrolled card; providing aggregated post coupon redemption sale data on enrolled cards at merchant to determine customer loyalty (e.g., does the customer transact again?) and to determine up sell beyond the original amount by reviewing average ticket size; and/or the like.
For example, if the merchant has a 100% increase in revenue since last coupon issuance 921, the ECIR server may increase the number of coupons by different amount depending on the cost of the coupon. If the coupon cost 922 is larger than $1,000,000, the ECIR server may increase the number of coupons by 10% 923. If the couple cost 924 is smaller than or equal to $1,000,000 but larger than $500,000, then the ECIR server may increase the number of coupons by 50% 925. If the couple cost 926 is smaller than or equal to $500,000 but larger than $1,000, then the ECIR server may a increase the number of coupons by 75% 927. If the couple cost 928 is smaller than or equal to $1,000 but larger than $1, the ECIR server may increase the number of coupons by 100% 929. If the coupon cost is less than $1, the ECIR server may also increase the number of coupons by 100%. If there is not a 100% increase in revenue, the ECIR server may determine whether there is a 50% increase in revenue. If there is a 50% increase in revenue 931, the ECIR server may increase the number of coupons by different amount depending on the cost of the coupon. If the coupon cost 932 is larger than $1,000,000, the ECIR server may increase the number of coupons by 5% 933. If the couple cost 934 is smaller than or equal to $1,000,000 but larger than $500,000, the ECIR server may increase the number of coupons by 25% 935. If the couple cost 936 is smaller than or equal to $500,000 but larger than $1,000, the ECIR server may increase the number of coupons by 37.5% 937. If the couple cost 938 is smaller than or equal to $1,000 but larger than $1, the ECIR server may increase the number of coupons by 50% 939. If there is not a 50% increase in revenue, the ECIR server may determine whether there is a 10% increase in revenue. If there is a 10% increase in revenue 941, the ECIR server may increase the number of coupons by different amount depending on the cost of the coupon. If the coupon cost 942 is larger than $1,000,000, the ECIR server may increase the number of coupons by 2.5% 943. If the couple cost 944 is smaller than or equal to $1,000,000 but larger than $500,000, the ECIR server may increase the number of coupons by 12.5% 945. If the couple cost 946 is smaller than or equal to $500,000 but larger than $1,000, the ECIR server may increase the number of coupons by 18% 947. If the couple cost 948 is smaller than or equal to $1,000 but larger than $1, the ECIR server may increase the number of coupons by 30% 949. If there is not a 10% increase in revenue, the ECIR server may stop issuing coupons 950. When the said information is generated, the ECIR server may generate a report providing the analytics of customer purchase information 910, which may be sent to the user for display 911.
With reference to
As shown, the user may enter a search term (e.g., bills) in the search bar 2121. The user may then identify in the tab 1122 the receipt 1123 the user wants to reallocate. Alternatively, the user may directly snap a picture of a barcode on a receipt, and the snap mode may generate and display a receipt 1123 using information from the barcode. The user may now reallocate 1125. In some implementations, the user may also dispute the transaction 1124 or archive the receipt 1126.
In one implementation, when the reallocate button 1125 is selected, the wallet application may perform optical character recognition (OCR) of the receipt. Each of the items in the receipt may then be examined to identify one or more items which could be charged to which payment device or account for tax or other benefits such as cash back, reward points, etc. In this example, there is a tax benefit if the prescription medication charged to the user's Visa card is charged to the user's FSA. The wallet application may then perform the reallocation as the back end. The reallocation process may include the wallet contacting the payment processor to credit the amount of the prescription medication to the Visa card and debit the same amount to the user's FSA account. In an alternate implementation, the payment processor (e.g., Visa or MasterCard) may obtain and OCR the receipt, identify items and payment accounts for reallocation and perform the reallocation. In one implementation, the wallet application may request the user to confirm reallocation of charges for the selected items to another payment account. The receipt 1127 may be generated after the completion of the reallocation process. As discussed, the receipt shows that some charges have been moved from the Visa account to the FSA.
With reference to
In one implementation, the user may decide to pay with default 1134. The wallet application may then use the user's default method of payment, in this example the wallet, to complete the purchase transaction. Upon completion of the transaction, a receipt may be automatically generated for proof of purchase. The user interface may also be updated to provide other options for handling a completed transaction. Example options include social 1137 to share purchase information with others, reallocate 1138 as discussed with regard to
With reference to
In one implementation, after the offer or coupon 1146 is applied, the user may have the option to find qualifying merchants and/or products using find, the user may go to the wallet using 1148, and the user may also save the offer or coupon 1146 for later use.
With reference to
Typically, users, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors 1203 may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 1229 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.
In one embodiment, the ECIR controller 1201 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 1211; peripheral devices 1212; an optional cryptographic processor device 1228; and/or a communications network 1213.
Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term “server” as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.” The term “client” as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a “node.” Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a “router.” There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.
The ECIR controller 1201 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 1202 connected to memory 1229.
A computer systemization 1202 may comprise a clock 1230, central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 1203, a memory 1229 (e.g., a read only memory (ROM) 1206, a random access memory (RAM) 1205, etc.), and/or an interface bus 1207, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 1204 on one or more (mother)board(s) 1202 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc. The computer systemization may be connected to a power source 1286; e.g., optionally the power source may be internal. Optionally, a cryptographic processor 1226 and/or transceivers (e.g., ICs) 1274 may be connected to the system bus. In another embodiment, the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 1212 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s) 1275, thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing ECIR controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like. The system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways. The clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. It should be understood that in alternative embodiments, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.
The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 1229 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the ECIR controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed ECIR), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed.
Depending on the particular implementation, features of the ECIR may be achieved by implementing a microcontroller such as CAST's R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the ECIR, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology. For example, any of the ECIR component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the ECIR may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.
Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, ECIR features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the ECIR features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the ECIR system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGA's logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the ECIR may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate ECIR controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the ECIR.
The power source 1286 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 1286 is connected to at least one of the interconnected subsequent components of the ECIR thereby providing an electric current to all subsequent components. In one example, the power source 1286 is connected to the system bus component 1204. In an alternative embodiment, an outside power source 1286 is provided through a connection across the I/O 1208 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.
Interface bus(ses) 1207 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 1208, storage interfaces 1209, network interfaces 1210, and/or the like. Optionally, cryptographic processor interfaces 1227 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.
Storage interfaces 1209 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 1214, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
Network interfaces 1210 may accept, communicate, and/or connect to a communications network 1213. Through a communications network 1213, the ECIR controller is accessible through remote clients 1233b (e.g., computers with web browsers) by users 1233a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed ECIR), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the ECIR controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 1210 may be used to engage with various communications network types 1213. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.
Input Output interfaces (I/O) 1208 may accept, communicate, and/or connect to user input devices 1211, peripheral devices 1212, cryptographic processor devices 1228, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).
User input devices 1211 often are a type of peripheral device 512 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina a readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
Peripheral devices 1212 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the ECIR controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 528), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras).
It should be noted that although user input devices and peripheral devices may be employed, the ECIR controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.
Cryptographic units such as, but not limited to, microcontrollers, processors 1226, interfaces 1227, and/or devices 1228 may be attached, and/or communicate with the ECIR controller. A MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used. Other commercially available specialized cryptographic processors include: Broadcom's CryptoNetX and other Security Processors; nCipher's nShield; SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.
Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 1229. However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the ECIR controller and/or a computer systemization may employ various forms of memory 1229. For example, a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card a mechanism; however, such an embodiment would result in an extremely slow rate of operation. In a typical configuration, memory 1229 will include ROM 1206, RAM 1205, and a storage device 1214. A storage device 1214 may be any conventional computer a system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory.
The memory 1229 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 1215 (operating system); information server component(s) 1216 (information server); user interface component(s) 1217 (user interface); Web browser component(s) 1218 (Web browser); database(s) 1219; mail server component(s) 1221; mail client component(s) 1222; cryptographic server component(s) 1220 (cryptographic server); the ECIR component(s) 1235; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although non-conventional program components such as those in the component collection, typically, are stored in a local storage device 1214, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.
The operating system component 1215 is an executable program a component facilitating the operation of the ECIR controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like. The operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 2000/2003/3.1/95/98/CE/Millennium/NT/Vista/XP (Server), Palm OS, and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the ECIR controller to communicate with other entities through a communications network 1213. Various communication protocols may be used by the ECIR controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.
An information server component 1216 is a stored program component that is executed by a CPU. The information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an a HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the ECIR controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.” Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the ECIR database 1219, operating systems, other program components, user interfaces, Web browsers, and/or the like.
Access to the ECIR database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the ECIR. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in a standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the ECIR as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser.
Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millennium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.
A user interface component 1217 is a stored program component that is executed by a CPU. The user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
A Web browser component 1218 is a stored program component that is executed by a CPU. The Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the ECIR enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.
A mail server component 1221 is a stored program component that is executed by a CPU 1203. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the ECIR.
Access to the ECIR mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.
Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
A mail client component 1222 is a stored program component that is executed by a CPU 1203. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages.
A cryptographic server component 1220 is a stored program component that is executed by a CPU 1203, cryptographic processor 1226, cryptographic processor interface 1227, cryptographic processor device 1228, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the ECIR may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component a facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the ECIR component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the ECIR and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
The ECIR database component 1219 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship.
Alternatively, the ECIR database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the ECIR database is implemented as a data-structure, the use of the ECIR database 1219 may be integrated into another component such as the ECIR component 1235. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.
In one embodiment, the database component 1219 includes several tables 1219a-o. A Users table 1219a may include fields such as, but not limited to: user_id, ssn, dob, first_name, last name, age, state, address_firstline, address_secondline, zipcode, a devices_list, contact_info, contact type, alt contactinfo, alt_contact type, coupon_id, and/or the like. The Users table may support and/or track multiple entity accounts on a ECIR. A Devices table 1219b may include fields such as, but not limited to: device_ID, device name, device_IP, device_MAC, device_type, device_model, device_version, device_OS, deviceapps_list, device_securekey, wallet app_installed_flag, and/or the like. An Apps table 1219c may include fields such as, but not limited to: app_ID, app_name, app_type, app_dependencies, and/or the like. An Accounts table 1219d may include fields such as, but not limited to: account_number, account_securitycode, account_name, issuer_acquirer_flag, issuer_name, acquirer name, account_address, routing_number, access_API_call, linked_wallets_list, coupon_id, and/or the like. A Merchants table 1219e may include fields such as, but not limited to: merchant_id, merchant_name, merchant_address, ip_address, mac_address, auth_key, port_num, security_settings_list, coupon_id, and/or the like. An Issuers table 1219f may include fields such as, but not limited to: issuer_id, issuer_name, issuer_address, ip_address, mac_address, auth_key, port_num, security_settings_list, coupon_id, and/or the like. An Acquirers table 1219g may include fields such as, but not limited to: account_firstname, account_lastname, account_type, account_num, account_balance_list, billingaddress_line1, billingaddress_line2, billing_zipcode, billing_state, shipping_preferences, shippingaddress_line1, shippingaddress_line2, shipping_zipcode, shipping_state, and/or the like. A Pay Gateways table 1219h may include fields such as, but not limited to: gateway_id, gateway_ip, gatewaysecure_key, gateway API_list, gatewayservices_list, and/or the like. A Transactions table 1219i may include fields such as, but not limited to: order_id, user_id, timestamp, transaction_cost, a purchase_details_list, num_products, products_list, product_type, product_params_list, product_title, product_summary, quantity, user_id, client_id, client_ip, client_type, client_model, operating_system, os_version, app_installed_flag, user_id, account_firstname, account_lastname, account_type, account_num, account_priority_account_ratio, billingaddress_line1, billingaddress_line2, billing_zipcode, billing_state, shipping_preferences, shippingaddress_line1, shippingaddress_line2, shipping_zipcode, shipping_state, merchant_id, merchant_name, merchant_auth_key, coupon_id, and/or the like. A Batches table 1219j may include fields such as, but not limited to: batch_id, transaction_id_list, timestamp_list, cleared_flag_list, clearance_trigger_settings, and/or the like. A Ledgers table 1219k may include fields such as, but not limited to: request_id, timestamp, deposit_amount, batch_id, transaction_id, clear_flag, deposit account, transaction_summary, payor_name, payor_account, and/or the like. A Products table 1219l may include fields such as, but not limited to: product_ID, product_title, product_attributes_list, product_price, tax_info_list, related_products_list, offers_list, discounts_list, rewards_list, merchants_list, merchant_availability_list, coupon_id, and/or the like. A Coupon table 1219m may include fields such as, but not limited to: coupon_id, merchant_id, issuer_id, user_id, coupon_title, coupon_attributes_list, coupon_price, coupon_expiry, related_products_list, discounts_list, rewards_list, merchants_list, merchant_availability_list, coupon_barcode, coupon_magnetic_stripe, coupon_RFID, coupon_delivery_method, coupon_templates, and/or the like. A Templates table 1219n may include fields such as, but not limited to: coupon_id, timestamp, transaction_cost, merchant_params_list, merchant_id, merchant_name, merchant_auth_key, merchant_products_list, num_products, product_list, product_type, product_name, class_labels_list, product_quantity, unit_value, sub_total, comment, user_account_params, account_name, account_type, account_num, billing_line1, billing_line2, zipcode, state, country, phone, sign, and/or the like. An Analytics table 12190 may include fields such as, but not limited to: analytics_report_id, merchant_id, timestamp, analytics_params_list, analytics_regression_models_list, analytics_regression_equations_list, analytics_regression_coefficients_list, analytics_fit_goodness_list, lsm_values_list, and/or the like.
In one embodiment, the ECIR database may interact with other database systems. For example, employing a distributed database system, queries and data access by search ECIR component may treat the combination of the ECIR database, an integrated data security layer database as a single database entity.
In one embodiment, user programs may contain various user interface primitives, which may serve to update the ECIR. Also, various accounts may require custom database tables depending upon the environments and the types of clients the ECIR may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 1219a-o. The ECIR may be configured to keep track of various a settings, inputs, and parameters via database controllers.
The ECIR database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the ECIR database communicates with the ECIR component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.
The ECIR component 1235 is a stored program component that is executed by a CPU. In one embodiment, the ECIR component incorporates any and/or all combinations of the aspects of the ECIR that was discussed in the previous figures. As such, the ECIR affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.
In some embodiments, the ECIR transforms user coupon purchase and redemption request inputs, via ECIR components (e.g., coupon issuance 1247, coupon funds loading 1248, coupon generation 1249, coupon redemption 1250, coupon funds settlement 1251, and, customer purchase analytics 1252), into coupon issuance, transaction, and analytics outputs.
The ECIR component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the ECIR server employs a cryptographic server to encrypt and decrypt communications. The ECIR component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the ECIR component communicates with the ECIR database, operating systems, other program components, and/or the like. The ECIR may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
The structure and/or operation of any of the ECIR node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.
The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.
The configuration of the ECIR controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.
If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other component components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), a Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.
For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:
where Value1 is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable “Value1” may be inserted into an “http://” post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed a to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.
For example, in some implementations, the ECIR controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below:
Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation:
and other parser implementations:
all of which are hereby expressly incorporated by reference.
In order to address various issues and advance the art, the entirety of this application for ELECTRONIC COUPON ISSUANCE AND REDEMPTION APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices, and otherwise) shows, by way of illustration, various embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed a alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations including the right to claim such innovations, file additional applications, a continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a ECIR individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the ECIR, may be implemented that enable a great deal of flexibility and customization. For example, aspects of the ECIR may be adapted for electronic payment, e-commerce payment, promotion offerings, mobile payment, revenue forecasting, and/or the like. While various embodiments and discussions of the ECIR have been directed to coupon issuance and redemption, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.
This application is a National Stage Entry entitled to and hereby claims priority under 35 S U.S.C. §§ 371 to corresponding PCT Application No. PCT/US12/24772, entitled “Electronic Coupon Issuance And Redemption Apparatuses Methods and Systems,”, filed Feb. 10, 2012, which in turn claims priority under 35 USC § 119 for U.S. provisional patent application Ser. No. 61/441,555 filed Feb. 10, 2011, entitled “Electronic Coupon Issuance And Redemption Apparatuses, Methods and Systems.” The entire contents of the aforementioned applications are herein expressly incorporated by reference.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/US2012/024772 | 2/10/2012 | WO | 00 | 1/23/2013 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2012/109628 | 8/16/2012 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 789106 | Seymour | May 1905 | A |
| 5237164 | Takada | Aug 1993 | A |
| 5311594 | Penzias | May 1994 | A |
| 5446890 | Renslo et al. | Aug 1995 | A |
| 5459656 | Fields et al. | Oct 1995 | A |
| 5510777 | Pilc et al. | Apr 1996 | A |
| 5521362 | Powers | May 1996 | A |
| 5530438 | Bickham et al. | Jun 1996 | A |
| 5536045 | Adams | Jul 1996 | A |
| 5615110 | Wong | Mar 1997 | A |
| 5615264 | Kazmierczak et al. | Mar 1997 | A |
| 5649118 | Carlisle et al. | Jul 1997 | A |
| 5815657 | Williams et al. | Sep 1998 | A |
| 5850446 | Berger et al. | Dec 1998 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5903830 | Joao et al. | May 1999 | A |
| 5943624 | Fox et al. | Aug 1999 | A |
| 5963924 | Williams et al. | Oct 1999 | A |
| 6064990 | Goldsmith | May 2000 | A |
| 6092053 | Boesch et al. | Jul 2000 | A |
| 6202052 | Miller | Mar 2001 | B1 |
| 6202933 | Poore et al. | Mar 2001 | B1 |
| 6263447 | French et al. | Jul 2001 | B1 |
| 6267292 | Walker et al. | Jul 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6473500 | Risafi et al. | Oct 2002 | B1 |
| 6529725 | Joao et al. | Mar 2003 | B1 |
| 6535855 | Cahill et al. | Mar 2003 | B1 |
| 6601761 | Katis | Aug 2003 | B1 |
| 6735572 | Landesmann | May 2004 | B2 |
| 6853982 | Smith et al. | Feb 2005 | B2 |
| 6857073 | French et al. | Feb 2005 | B2 |
| 6873974 | Schutzer | Mar 2005 | B1 |
| 6898598 | Himmel et al. | May 2005 | B2 |
| 6934528 | Loureiro et al. | Aug 2005 | B2 |
| 6999943 | Johnson et al. | Feb 2006 | B1 |
| 7024383 | Mancini et al. | Apr 2006 | B1 |
| 7028052 | Chapman et al. | Apr 2006 | B2 |
| 7047041 | Vanska et al. | May 2006 | B2 |
| 7051002 | Keresman, III et al. | May 2006 | B2 |
| 7089208 | Levchin et al. | Aug 2006 | B1 |
| 7096003 | Joao et al. | Aug 2006 | B2 |
| 7111789 | Rajasekaran et al. | Sep 2006 | B2 |
| 7155411 | Blinn et al. | Dec 2006 | B1 |
| 7177848 | Hogan et al. | Feb 2007 | B2 |
| 7194437 | Britto et al. | Mar 2007 | B1 |
| 7206847 | Alberth et al. | Apr 2007 | B1 |
| 7212979 | Matz et al. | May 2007 | B1 |
| RE39736 | Morrill, Jr. | Jul 2007 | E |
| 7268667 | Beenau et al. | Sep 2007 | B2 |
| 7268668 | Beenau et al. | Sep 2007 | B2 |
| 7290704 | Ball et al. | Nov 2007 | B1 |
| 7318049 | Iannacci | Jan 2008 | B2 |
| 7337119 | Geschwender et al. | Feb 2008 | B1 |
| 7337144 | Blinn et al. | Feb 2008 | B1 |
| 7343149 | Benco et al. | Mar 2008 | B2 |
| 7343351 | Bishop et al. | Mar 2008 | B1 |
| 7349885 | Gangi | Mar 2008 | B2 |
| 7356505 | March | Apr 2008 | B2 |
| 7357310 | Calabrese et al. | Apr 2008 | B2 |
| 7359880 | Abel et al. | Apr 2008 | B2 |
| 7373669 | Eisen et al. | May 2008 | B2 |
| 7379899 | Junger | May 2008 | B1 |
| 7392222 | Hamilton et al. | Jun 2008 | B1 |
| 7395242 | Blinn et al. | Jul 2008 | B2 |
| 7398250 | Blinn et al. | Jul 2008 | B2 |
| 7413113 | Zhu | Aug 2008 | B1 |
| 7450966 | Vanska et al. | Nov 2008 | B2 |
| 7477780 | Boncyk et al. | Jan 2009 | B2 |
| 7499889 | Golan et al. | Mar 2009 | B2 |
| 7500607 | Williams | Mar 2009 | B2 |
| 7533064 | Boesch | May 2009 | B1 |
| 7536360 | Salvotore et al. | May 2009 | B2 |
| 7571139 | Giordano et al. | Aug 2009 | B1 |
| 7571140 | Weichert et al. | Aug 2009 | B2 |
| 7593858 | Matz et al. | Sep 2009 | B2 |
| 7603311 | Yadav-ranjan | Oct 2009 | B1 |
| 7630937 | Mo et al. | Dec 2009 | B1 |
| 7634295 | Hayaashi et al. | Dec 2009 | B2 |
| 7644037 | Ostrovsky | Jan 2010 | B1 |
| 7644859 | Zhu | Jan 2010 | B1 |
| 7660749 | Koski | Feb 2010 | B2 |
| 7676434 | Evans | Mar 2010 | B2 |
| 7685067 | Britto et al. | Mar 2010 | B1 |
| 7698221 | Blinn et al. | Apr 2010 | B2 |
| 7707113 | Dimartino et al. | Apr 2010 | B1 |
| 7708194 | Vawter | May 2010 | B2 |
| 7708198 | Gangi | May 2010 | B2 |
| 7712658 | Gangi | May 2010 | B2 |
| 7739194 | Blinn et al. | Jun 2010 | B2 |
| 7742984 | Mohsenzadeh | Jun 2010 | B2 |
| 7774076 | Skowronek | Aug 2010 | B2 |
| 7783569 | Abel et al. | Aug 2010 | B2 |
| 7784684 | Labrou et al. | Aug 2010 | B2 |
| 7801829 | Gray et al. | Sep 2010 | B2 |
| 7802719 | Johnson et al. | Sep 2010 | B2 |
| 7810720 | Lovett | Oct 2010 | B2 |
| 7819307 | Lyons et al. | Oct 2010 | B2 |
| 7828206 | Hessburg et al. | Nov 2010 | B2 |
| 7828992 | Kilickiran et al. | Nov 2010 | B2 |
| 7837125 | Biskupski | Nov 2010 | B2 |
| 7844530 | Ziade et al. | Nov 2010 | B2 |
| 7849014 | Erikson | Dec 2010 | B2 |
| 7870027 | Tannenbaum | Jan 2011 | B1 |
| 7877299 | Bui | Jan 2011 | B2 |
| 7878400 | Harris | Feb 2011 | B2 |
| 7890370 | Whitsitt et al. | Feb 2011 | B2 |
| 7895119 | Praisner | Feb 2011 | B2 |
| 7899744 | Bishop et al. | Mar 2011 | B2 |
| 7904360 | Evans | Mar 2011 | B2 |
| 7908227 | Zizzimopoulos et al. | Mar 2011 | B2 |
| 7926714 | Zhu | Apr 2011 | B1 |
| 7933779 | Rooks et al. | Apr 2011 | B2 |
| 7942337 | Jain | May 2011 | B2 |
| 7962418 | Wei et al. | Jun 2011 | B1 |
| 7967196 | Bierbaum et al. | Jun 2011 | B1 |
| 7971782 | Shams | Jul 2011 | B1 |
| 7996259 | Distefano, III | Aug 2011 | B1 |
| 8016192 | Messerges et al. | Sep 2011 | B2 |
| 8020763 | Kowalchyk et al. | Sep 2011 | B1 |
| 8024260 | Hogl et al. | Sep 2011 | B1 |
| 8028041 | Olliphant et al. | Sep 2011 | B2 |
| 8032438 | Barton et al. | Oct 2011 | B1 |
| 8041338 | Chen et al. | Oct 2011 | B2 |
| 8050997 | Nosek et al. | Nov 2011 | B1 |
| 8060413 | Castell et al. | Nov 2011 | B2 |
| 8074876 | Foss et al. | Dec 2011 | B2 |
| 8108261 | Carlier et al. | Jan 2012 | B2 |
| 8127982 | Casey et al. | Mar 2012 | B1 |
| 8140418 | Casey et al. | Mar 2012 | B1 |
| 8145188 | Park et al. | Mar 2012 | B2 |
| 8145561 | Zhu et al. | Mar 2012 | B1 |
| 8145566 | Ahuja et al. | Mar 2012 | B1 |
| 8145569 | Gong | Mar 2012 | B2 |
| 8145898 | Kamalakantha | Mar 2012 | B2 |
| 8150767 | Wankmueller | Apr 2012 | B2 |
| 8150772 | Mardikar et al. | Apr 2012 | B2 |
| 8151328 | Lundy | Apr 2012 | B1 |
| 8151330 | Vishik et al. | Apr 2012 | B2 |
| 8151336 | Savoor | Apr 2012 | B2 |
| 8155999 | De Boer et al. | Apr 2012 | B2 |
| 8156000 | Thompson | Apr 2012 | B1 |
| 8156026 | Junger et al. | Apr 2012 | B2 |
| 8156042 | Winkleman, III et al. | Apr 2012 | B2 |
| 8156549 | Rice et al. | Apr 2012 | B2 |
| 8157178 | Dewan et al. | Apr 2012 | B2 |
| 8157181 | Bates et al. | Apr 2012 | B2 |
| 8160935 | Bui | Apr 2012 | B2 |
| 8160959 | Rackley, III et al. | Apr 2012 | B2 |
| 8165961 | Dimartino et al. | Apr 2012 | B1 |
| 8166068 | Stevens | Apr 2012 | B2 |
| RE43351 | Jordan, Jr. | May 2012 | E |
| 8170921 | Stocker | May 2012 | B2 |
| 8175235 | Mumford et al. | May 2012 | B2 |
| 8175965 | Moore et al. | May 2012 | B2 |
| 8175967 | O'Leary et al. | May 2012 | B2 |
| 8175968 | O'Leary et al. | May 2012 | B2 |
| 8175975 | Cai et al. | May 2012 | B2 |
| 8175979 | Baentsch et al. | May 2012 | B2 |
| 8176416 | Williams et al. | May 2012 | B1 |
| 8179563 | King et al. | May 2012 | B2 |
| 8180289 | Glickman | May 2012 | B1 |
| 8180705 | Kowalchyk et al. | May 2012 | B2 |
| 8190513 | Felger | May 2012 | B2 |
| 8191775 | Hildred | Jun 2012 | B2 |
| 8195233 | Morikuni et al. | Jun 2012 | B2 |
| 8195544 | Horsfall | Jun 2012 | B2 |
| 8195547 | Aaltonen et al. | Jun 2012 | B2 |
| 8195565 | Bishop et al. | Jun 2012 | B2 |
| 8195576 | Grigg et al. | Jun 2012 | B1 |
| 8196131 | Von Behren et al. | Jun 2012 | B1 |
| 8200582 | Zhu | Jun 2012 | B1 |
| 8204774 | Chwast et al. | Jun 2012 | B2 |
| 8204829 | Alvarez et al. | Jun 2012 | B2 |
| 8209245 | Dennes | Jun 2012 | B2 |
| 8209744 | Zhu et al. | Jun 2012 | B2 |
| 8214288 | Olliphant et al. | Jul 2012 | B2 |
| 8214289 | Scipioni | Jul 2012 | B2 |
| 8214291 | Pelegero et al. | Jul 2012 | B2 |
| 8214292 | Duggal et al. | Jul 2012 | B2 |
| 8214293 | Powell | Jul 2012 | B2 |
| 8214886 | Foley et al. | Jul 2012 | B2 |
| 8215546 | Lin et al. | Jul 2012 | B2 |
| 8219411 | Matz et al. | Jul 2012 | B2 |
| 8219474 | Sutton et al. | Jul 2012 | B2 |
| 8219490 | Hammad et al. | Jul 2012 | B2 |
| 8220047 | Soghoian et al. | Jul 2012 | B1 |
| 8224702 | Mangerink et al. | Jul 2012 | B2 |
| 8224754 | Pastusiak et al. | Jul 2012 | B2 |
| 8224773 | Spiegel | Jul 2012 | B2 |
| 8225997 | Bierbaum et al. | Jul 2012 | B1 |
| 8227936 | Folk et al. | Jul 2012 | B1 |
| 8229354 | Sklovsky et al. | Jul 2012 | B2 |
| 8229808 | Heit | Jul 2012 | B1 |
| 8229844 | Felger | Jul 2012 | B2 |
| 8229851 | Doran et al. | Jul 2012 | B2 |
| 8229854 | Stephen et al. | Jul 2012 | B2 |
| 8233841 | Griffin et al. | Jul 2012 | B2 |
| 8234183 | Smith | Jul 2012 | B2 |
| 8239276 | Lin et al. | Aug 2012 | B2 |
| 8244580 | Mankoff et al. | Aug 2012 | B2 |
| 8249965 | Tumminaro | Aug 2012 | B2 |
| 8255278 | Young et al. | Aug 2012 | B1 |
| 8255323 | Casey et al. | Aug 2012 | B1 |
| 8255324 | Bercy et al. | Aug 2012 | B2 |
| 8275704 | Bishop et al. | Sep 2012 | B2 |
| 8280777 | Mengerink et al. | Oct 2012 | B2 |
| 8281998 | Tang et al. | Oct 2012 | B2 |
| 8282002 | Shams | Oct 2012 | B2 |
| 8285640 | Scipioni | Oct 2012 | B2 |
| 8285820 | Olliphant et al. | Oct 2012 | B2 |
| 8285832 | Schwab et al. | Oct 2012 | B2 |
| 8286875 | Tang et al. | Oct 2012 | B2 |
| 8290433 | Fisher et al. | Oct 2012 | B2 |
| 8290819 | Bawcutt | Oct 2012 | B2 |
| 8290829 | Katz et al. | Oct 2012 | B1 |
| 8295898 | Ashfield et al. | Oct 2012 | B2 |
| 8296187 | Light et al. | Oct 2012 | B2 |
| 8296204 | Templeton et al. | Oct 2012 | B2 |
| 8296228 | Kloor | Oct 2012 | B1 |
| 8296231 | Britto et al. | Oct 2012 | B2 |
| 8301500 | Pharris | Oct 2012 | B2 |
| 8301510 | Boesch | Oct 2012 | B2 |
| 8301556 | Hogl et al. | Oct 2012 | B2 |
| 8311520 | Choi et al. | Nov 2012 | B2 |
| 8312096 | Cohen et al. | Nov 2012 | B2 |
| 8321267 | Hoerenz et al. | Nov 2012 | B2 |
| 8321294 | Carlier et al. | Nov 2012 | B2 |
| 8321315 | Abel et al. | Nov 2012 | B2 |
| 8321338 | Baumgart et al. | Nov 2012 | B2 |
| 8321343 | Ramavarjula et al. | Nov 2012 | B2 |
| 8326756 | Egendorf | Dec 2012 | B2 |
| 8326769 | Weisman | Dec 2012 | B1 |
| 8326770 | Weisman | Dec 2012 | B1 |
| 8327450 | Clement et al. | Dec 2012 | B2 |
| 8332272 | Fisher | Dec 2012 | B2 |
| 8332275 | Poon et al. | Dec 2012 | B2 |
| 8332323 | Stals et al. | Dec 2012 | B2 |
| 8335720 | Juang et al. | Dec 2012 | B2 |
| 8335726 | Ling et al. | Dec 2012 | B1 |
| 8335822 | Ahmed et al. | Dec 2012 | B2 |
| 8335921 | Von Behren et al. | Dec 2012 | B2 |
| 8335932 | Von Behren et al. | Dec 2012 | B2 |
| 8340666 | Ramer et al. | Dec 2012 | B2 |
| 8341029 | Ramalingam et al. | Dec 2012 | B1 |
| 8346643 | Boyer et al. | Jan 2013 | B2 |
| 8346659 | Mohsenzadeh | Jan 2013 | B1 |
| 8346663 | Kawan | Jan 2013 | B2 |
| 8352323 | Fisher | Jan 2013 | B2 |
| 8352362 | Mohsenzadeh | Jan 2013 | B2 |
| 8352499 | Bharat et al. | Jan 2013 | B2 |
| 8352749 | Von Behren et al. | Jan 2013 | B2 |
| 8355987 | Hirson et al. | Jan 2013 | B2 |
| 8359070 | Zhu | Jan 2013 | B1 |
| 8364587 | Nuzum et al. | Jan 2013 | B2 |
| 8364590 | Casey et al. | Jan 2013 | B1 |
| 8370264 | Wei et al. | Feb 2013 | B1 |
| 8371502 | Galit | Feb 2013 | B1 |
| 8380177 | Laracey | Feb 2013 | B2 |
| 8401904 | Simakov et al. | Mar 2013 | B1 |
| 8412586 | Foulser et al. | Apr 2013 | B1 |
| 8412630 | Ross et al. | Apr 2013 | B2 |
| 8417633 | Chmara et al. | Apr 2013 | B1 |
| 8423462 | Amacker et al. | Apr 2013 | B1 |
| 20010037297 | McNair | Mar 2001 | A1 |
| 20010056359 | Abreu | Dec 2001 | A1 |
| 20020010627 | Lerat | Jan 2002 | A1 |
| 20020040325 | Takae et al. | Apr 2002 | A1 |
| 20020077976 | Meyer et al. | Jun 2002 | A1 |
| 20020107755 | Steed et al. | Aug 2002 | A1 |
| 20020112014 | Bennett et al. | Aug 2002 | A1 |
| 20020116271 | Mankoff | Aug 2002 | A1 |
| 20020143614 | MacLean et al. | Oct 2002 | A1 |
| 20030014307 | Heng | Jan 2003 | A1 |
| 20030026404 | Joyce et al. | Feb 2003 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030080185 | Werther | May 2003 | A1 |
| 20030097318 | Yu et al. | May 2003 | A1 |
| 20030101134 | Liu et al. | May 2003 | A1 |
| 20030174823 | Justice et al. | Sep 2003 | A1 |
| 20030177361 | Wheeler et al. | Sep 2003 | A1 |
| 20030191711 | Jamison et al. | Oct 2003 | A1 |
| 20030200142 | Hicks et al. | Oct 2003 | A1 |
| 20030200184 | Dominguez et al. | Oct 2003 | A1 |
| 20030212642 | Weller et al. | Nov 2003 | A1 |
| 20040078332 | Ferguson et al. | Apr 2004 | A1 |
| 20040103037 | Wetmore et al. | May 2004 | A1 |
| 20040128197 | Bam et al. | Jul 2004 | A1 |
| 20040138999 | Friedman et al. | Jul 2004 | A1 |
| 20040148255 | Beck et al. | Jul 2004 | A1 |
| 20040215963 | Kaplan | Oct 2004 | A1 |
| 20040230536 | Fung et al. | Nov 2004 | A1 |
| 20040236646 | Wu et al. | Nov 2004 | A1 |
| 20040254891 | Blinn et al. | Dec 2004 | A1 |
| 20040267608 | Mansfield, Jr. | Dec 2004 | A1 |
| 20050010483 | Ling | Jan 2005 | A1 |
| 20050037735 | Coutts | Feb 2005 | A1 |
| 20050037779 | Ma | Feb 2005 | A1 |
| 20050065819 | Schultz | Mar 2005 | A1 |
| 20050080747 | Anderson et al. | Apr 2005 | A1 |
| 20050080821 | Breil et al. | Apr 2005 | A1 |
| 20050097320 | Golan et al. | May 2005 | A1 |
| 20050102227 | Solonchev | May 2005 | A1 |
| 20050137969 | Shah | Jun 2005 | A1 |
| 20050171894 | Traynor | Aug 2005 | A1 |
| 20050192893 | Keeling et al. | Sep 2005 | A1 |
| 20050192895 | Rogers et al. | Sep 2005 | A1 |
| 20050220326 | Sim | Oct 2005 | A1 |
| 20050234817 | VanFleet et al. | Oct 2005 | A1 |
| 20050246278 | Gerber et al. | Nov 2005 | A1 |
| 20050254714 | Anne | Nov 2005 | A1 |
| 20050261967 | Barry et al. | Nov 2005 | A1 |
| 20060053056 | Alspach-goss et al. | Mar 2006 | A1 |
| 20060085328 | Cohen et al. | Apr 2006 | A1 |
| 20060085477 | Phillips et al. | Apr 2006 | A1 |
| 20060124729 | Martin | Jun 2006 | A1 |
| 20060129427 | Wennberg | Jun 2006 | A1 |
| 20060163349 | Neugebauer | Jul 2006 | A1 |
| 20060178986 | Giordano et al. | Aug 2006 | A1 |
| 20060190347 | Cuervo | Aug 2006 | A1 |
| 20060226216 | Keithley | Oct 2006 | A1 |
| 20060277143 | Almonte et al. | Dec 2006 | A1 |
| 20060293947 | Nicholson | Dec 2006 | A1 |
| 20070011025 | Cracchiolo et al. | Jan 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070055571 | Fox et al. | Mar 2007 | A1 |
| 20070087820 | Van Luchene et al. | Apr 2007 | A1 |
| 20070094066 | Kumar et al. | Apr 2007 | A1 |
| 20070100691 | Patterson | May 2007 | A1 |
| 20070100728 | Rotman et al. | May 2007 | A1 |
| 20070106607 | Seib et al. | May 2007 | A1 |
| 20070113289 | Blumenau | May 2007 | A1 |
| 20070143204 | Claus et al. | Jun 2007 | A1 |
| 20070150413 | Morgenstern | Jun 2007 | A1 |
| 20070180119 | Khivesara et al. | Aug 2007 | A1 |
| 20070208662 | Jeronimus et al. | Sep 2007 | A1 |
| 20070214078 | Coppinger | Sep 2007 | A1 |
| 20070214250 | Ahmed et al. | Sep 2007 | A1 |
| 20070226152 | Jones | Sep 2007 | A1 |
| 20070233590 | Hardison, III | Oct 2007 | A1 |
| 20070239502 | Babu | Oct 2007 | A1 |
| 20070276765 | Hazel et al. | Nov 2007 | A1 |
| 20080004116 | Van Luchene et al. | Jan 2008 | A1 |
| 20080004952 | Koli | Jan 2008 | A1 |
| 20080010096 | Patterson et al. | Jan 2008 | A1 |
| 20080021829 | Kranzley | Jan 2008 | A1 |
| 20080077489 | Gilley et al. | Mar 2008 | A1 |
| 20080086365 | Zollino et al. | Apr 2008 | A1 |
| 20080091553 | Koski | Apr 2008 | A1 |
| 20080091616 | Helwin et al. | Apr 2008 | A1 |
| 20080097856 | Blagg et al. | Apr 2008 | A1 |
| 20080114737 | Neely et al. | May 2008 | A1 |
| 20080126145 | Racklet, III et al. | May 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080140568 | Henry | Jun 2008 | A1 |
| 20080147883 | Philyaw | Jun 2008 | A1 |
| 20080162361 | Sklovsky et al. | Jul 2008 | A1 |
| 20080167965 | Von Nothaus et al. | Jul 2008 | A1 |
| 20080172274 | Hurowitz et al. | Jul 2008 | A1 |
| 20080172331 | Graves et al. | Jul 2008 | A1 |
| 20080177574 | Lara Gonzalez et al. | Jul 2008 | A1 |
| 20080177672 | Brunner et al. | Jul 2008 | A1 |
| 20080223918 | Williams et al. | Sep 2008 | A1 |
| 20080270300 | Jones et al. | Oct 2008 | A1 |
| 20080272188 | Keithley et al. | Nov 2008 | A1 |
| 20080319905 | Carlson | Dec 2008 | A1 |
| 20090006181 | Ghosh et al. | Jan 2009 | A1 |
| 20090024527 | Sellen et al. | Jan 2009 | A1 |
| 20090037255 | Chiu et al. | Feb 2009 | A1 |
| 20090048934 | Haddad et al. | Feb 2009 | A1 |
| 20090061884 | Rajan et al. | Mar 2009 | A1 |
| 20090063261 | Scribner et al. | Mar 2009 | A1 |
| 20090064056 | Anderson et al. | Mar 2009 | A1 |
| 20090076953 | Saville et al. | Mar 2009 | A1 |
| 20090076966 | Bishop et al. | Mar 2009 | A1 |
| 20090089176 | Mccabe | Apr 2009 | A1 |
| 20090089193 | Paintin | Apr 2009 | A1 |
| 20090104888 | Cox | Apr 2009 | A1 |
| 20090106151 | Nelsen et al. | Apr 2009 | A1 |
| 20090119176 | Johnson | May 2009 | A1 |
| 20090119211 | Johnson | May 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090132395 | Lam et al. | May 2009 | A1 |
| 20090144104 | Johnson | Jun 2009 | A1 |
| 20090164344 | Shiftan et al. | Jun 2009 | A1 |
| 20090171778 | Powell | Jul 2009 | A1 |
| 20090182664 | Trombley | Jul 2009 | A1 |
| 20090210300 | Cansler et al. | Aug 2009 | A1 |
| 20090222347 | Whitten | Sep 2009 | A1 |
| 20090233579 | Castell et al. | Sep 2009 | A1 |
| 20090234751 | Chan et al. | Sep 2009 | A1 |
| 20090241159 | Campagna et al. | Sep 2009 | A1 |
| 20090254471 | Seidel et al. | Oct 2009 | A1 |
| 20090254479 | Pharris | Oct 2009 | A1 |
| 20090254535 | Eickelmann et al. | Oct 2009 | A1 |
| 20090265274 | Hahn-Carlson et al. | Oct 2009 | A1 |
| 20090271265 | Lay et al. | Oct 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090307135 | Gupta et al. | Dec 2009 | A1 |
| 20090313132 | McKenna et al. | Dec 2009 | A1 |
| 20090327045 | Olives et al. | Dec 2009 | A1 |
| 20090327088 | Puthupparambil et al. | Dec 2009 | A1 |
| 20100004989 | Bonalle et al. | Jan 2010 | A1 |
| 20100005025 | Kumar | Jan 2010 | A1 |
| 20100009663 | Chang | Jan 2010 | A1 |
| 20100010964 | Skowronek et al. | Jan 2010 | A1 |
| 20100023386 | Avisar et al. | Jan 2010 | A1 |
| 20100023455 | Dispensa et al. | Jan 2010 | A1 |
| 20100036741 | Cleven | Feb 2010 | A1 |
| 20100036775 | Edens | Feb 2010 | A1 |
| 20100042456 | Stinchcombe et al. | Feb 2010 | A1 |
| 20100042537 | Smith et al. | Feb 2010 | A1 |
| 20100042540 | Graves et al. | Feb 2010 | A1 |
| 20100049613 | Angles | Feb 2010 | A1 |
| 20100049879 | Leavitt et al. | Feb 2010 | A1 |
| 20100063903 | Whipple et al. | Mar 2010 | A1 |
| 20100076873 | Taylor et al. | Mar 2010 | A1 |
| 20100078471 | Lin et al. | Apr 2010 | A1 |
| 20100078472 | Lin et al. | Apr 2010 | A1 |
| 20100082444 | Lin et al. | Apr 2010 | A1 |
| 20100082445 | Hodge et al. | Apr 2010 | A1 |
| 20100082447 | Lin et al. | Apr 2010 | A1 |
| 20100082455 | Rosenblatt et al. | Apr 2010 | A1 |
| 20100082480 | Korosec | Apr 2010 | A1 |
| 20100082481 | Lin et al. | Apr 2010 | A1 |
| 20100082485 | Lin et al. | Apr 2010 | A1 |
| 20100082490 | Rosenblatt et al. | Apr 2010 | A1 |
| 20100082491 | Rosenblatt et al. | Apr 2010 | A1 |
| 20100088188 | Kumar et al. | Apr 2010 | A1 |
| 20100094730 | Koski | Apr 2010 | A1 |
| 20100100480 | Altman et al. | Apr 2010 | A1 |
| 20100121707 | Goeldi | May 2010 | A1 |
| 20100125492 | Lin et al. | May 2010 | A1 |
| 20100125495 | Smith et al. | May 2010 | A1 |
| 20100125803 | Johnson | May 2010 | A1 |
| 20100131347 | Sarptipi | May 2010 | A1 |
| 20100131415 | Sartipi | May 2010 | A1 |
| 20100155470 | Woronec | Jun 2010 | A1 |
| 20100161433 | White | Jun 2010 | A1 |
| 20100174599 | Rosenblatt et al. | Jul 2010 | A1 |
| 20100185505 | Sprogoe et al. | Jul 2010 | A1 |
| 20100185531 | Van Luchene | Jul 2010 | A1 |
| 20100191578 | Tran et al. | Jul 2010 | A1 |
| 20100191622 | Reiss et al. | Jul 2010 | A1 |
| 20100191770 | Cho et al. | Jul 2010 | A1 |
| 20100198626 | Cho et al. | Aug 2010 | A1 |
| 20100211445 | Bodington | Aug 2010 | A1 |
| 20100211452 | D'Angelo et al. | Aug 2010 | A1 |
| 20100211499 | Zanzot et al. | Aug 2010 | A1 |
| 20100217682 | Chan | Aug 2010 | A1 |
| 20100250351 | Gillenson et al. | Sep 2010 | A1 |
| 20100276484 | Banerjee et al. | Nov 2010 | A1 |
| 20100305848 | Stallman | Dec 2010 | A1 |
| 20100306075 | Drance et al. | Dec 2010 | A1 |
| 20100306113 | Grey et al. | Dec 2010 | A1 |
| 20100312635 | Cervenka | Dec 2010 | A1 |
| 20100312645 | Niekadlik et al. | Dec 2010 | A1 |
| 20100312676 | Muthukumaran | Dec 2010 | A1 |
| 20100332262 | Horvitz et al. | Dec 2010 | A1 |
| 20100332283 | Ng et al. | Dec 2010 | A1 |
| 20110029363 | Gillenson et al. | Feb 2011 | A1 |
| 20110047075 | Fourez | Feb 2011 | A1 |
| 20110054993 | Marshall et al. | Mar 2011 | A1 |
| 20110078082 | Gupta | Mar 2011 | A1 |
| 20110082789 | Boyd | Apr 2011 | A1 |
| 20110099057 | Tenyer | Apr 2011 | A1 |
| 20110105183 | Hsiao et al. | May 2011 | A1 |
| 20110106698 | Issacson et al. | May 2011 | A1 |
| 20110137742 | Parikh | Jun 2011 | A1 |
| 20110178896 | Nakajima et al. | Jul 2011 | A1 |
| 20110184827 | Hubert | Jul 2011 | A1 |
| 20110191166 | Joa et al. | Aug 2011 | A1 |
| 20110215146 | Shams | Sep 2011 | A1 |
| 20110218870 | Shams et al. | Sep 2011 | A1 |
| 20110246290 | Howard et al. | Oct 2011 | A1 |
| 20110258123 | Dawkins et al. | Oct 2011 | A1 |
| 20110296508 | Os et al. | Dec 2011 | A1 |
| 20110320344 | Faith et al. | Dec 2011 | A1 |
| 20120011063 | Killian et al. | Jan 2012 | A1 |
| 20120022943 | Howard et al. | Jan 2012 | A1 |
| 20120023026 | Chen et al. | Jan 2012 | A1 |
| 20120030101 | Boyd | Feb 2012 | A1 |
| 20120036071 | Fulton et al. | Feb 2012 | A1 |
| 20120084204 | Castell et al. | Apr 2012 | A1 |
| 20120095895 | Aston | Apr 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120116966 | Tan | May 2012 | A1 |
| 20120118950 | Belk | May 2012 | A1 |
| 20120123838 | Sparks | May 2012 | A1 |
| 20120136780 | El-Awady et al. | May 2012 | A1 |
| 20120158474 | Fahner et al. | Jun 2012 | A1 |
| 20120166333 | von Behren et al. | Jun 2012 | A1 |
| 20120173431 | Ritchie et al. | Jul 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120215640 | Ramer et al. | Aug 2012 | A1 |
| 20120215650 | Oba et al. | Aug 2012 | A1 |
| 20120221421 | Hammad | Aug 2012 | A1 |
| 20120221502 | Jerram et al. | Aug 2012 | A1 |
| 20120231844 | Coppinger | Sep 2012 | A1 |
| 20120259763 | Pessin | Oct 2012 | A1 |
| 20120271697 | Gilman et al. | Oct 2012 | A1 |
| 20120304273 | Bailey et al. | Nov 2012 | A1 |
| 20120310826 | Chatterjee | Dec 2012 | A1 |
| 20120316949 | Chen | Dec 2012 | A1 |
| 20120323664 | Klems | Dec 2012 | A1 |
| 20130090750 | Herrman et al. | Apr 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 0855659 | Nov 2007 | EP |
| 08-545210 | Dec 2008 | JP |
| 10-0432430 | May 2004 | KR |
| 06-0117177 | Nov 2006 | KR |
| 07-0104087 | Oct 2007 | KR |
| WO01065502 | Sep 2001 | WO |
| WO03023674 | Apr 2004 | WO |
| WO10148737 | Dec 2010 | WO |
| Entry |
|---|
| David Breitkopf, “ACS To Take Over Mich. WC Distribution Program”, American Banker, New York, NY: Jul. 20, 2006, vol. 171. Issue 138, p. 6. |
| Business Wire, “New York State Department of Labor Selects JPMorgan Chase to Provide New Banking Services for Unemployment Insurance Benefits; JPMorgan Chase Electronic Services to Help Speed Benefit Payments”, Business Wire, New York, Aug. 4, 2006, p. 1. |
| Gopalan, NP & Selvan, B Siva. TCP/IP Illustrated. Prentice-Hall. 2008. pp. 101-102, 175-176 and 235. |
| Shadrach, D.C. “A Weighted Metric Based Adaptive Algorithm for Web Server Load Balancing.” 2009 Third International Symposium on Intelligenr Information Technology Application, http://ieeexplore.ieee.org/xpl/articleDetails.jsp?amumber=5369384, pp. 449-452. |
| International Search Report and Written Opinion for PCT/US09/54921 dated Oct. 21, 2009. |
| International Search Report and Written Opinion for PCT/US2010/048344 dated Nov. 15, 2010. |
| International Search Report and Written Opinion for PCT/US2010/033861 dated Dec. 9, 2010. |
| International Search Report and Written Opinion for PCT/US2010/033547 dated Dec. 14, 2010. |
| International Preliminary Report on Patentability for PCT/US2010/033229 dated Dec. 29, 2010. |
| International Search Report and Written Opinion for PCT/US2010/041860 dated Feb. 1, 2011. |
| International Search Report and Written Opinion for PCT/US2010/045445 dated Feb. 24, 2011. |
| International Search Report and Written Opinion for PCT/US2010/045500 dated Mar. 29, 2011. |
| International Search Report and Written Opinion for PCT/US2011/024941 dated Apr. 19, 2011. |
| International Search Report and Written Opinion for PCT/US2010/046833 dated Apr. 26, 2011. |
| International Search Report and Written Opinion for PCT/US2011/26734 dated Apr. 29, 2011. |
| International Search Report and Written Opinion for PCT/US2011/29790 dated May 19, 2011. |
| International Search Report and Written Opinion for PCT/US2011/035268 dated Aug. 5, 2011. |
| International Search Report and Written Opinion for PCT/US2011/032093 dated Aug. 24, 2011. |
| International Search Report and Written Opinion for PCT/US11/39178 dated Sep. 16, 2011. |
| International Search Report and Written Opinion for PCT/US2011/42062 dated Sep. 29, 2011. |
| International Search Report for PCT/US11/49393 dated Dec. 5, 2011. |
| International Search Report and Written Opinion for PCT/US11/57179 dated Jan. 5, 2012. |
| International Search Report and Written Opinion for PCT/US11/57173 dated Mar. 15, 2012. |
| International Search Report and Written Opinion for PCT/US11/57180 dated Mar. 15, 2012. |
| International Search Report for PCT/US12/2l000 dated May 15, 2012. |
| International Search Report for PCT/US11/65305 dated Apr. 16, 2012. |
| International Search Report for PCT/US12/26205, dated May 29, 2012. |
| International Search Report for PCT/US12/23856 dated Jun. 6, 2012. |
| International Search Report and Written Opinion for PCT/US2012/027043 dated Jul. 13, 2012. |
| International Search Report for PCT/US12/24772 dated Jul. 24, 2012. |
| International Search Report for PCT/US12/25530 dated Aug. 7, 2012. |
| International Search Report PCT/US12/27620 dated Aug. 10, 2012. |
| International Search Report and Written Opinion for PCT/US12/41437 dated Aug. 24, 2012. |
| International Search Report and Written Opinion for PCT/US12/37597 dated Sep. 21, 2012. |
| International Search Report for PCT/US12/39638 dated Sep. 24, 2012. |
| International Search Report for PCT/US12/45875 dated Nov. 16, 2012. |
| International Search Report for PCT/US12/47092 dated Nov. 26, 2012. |
| International Search Report for PCT/US12/57577 dated Nov. 29, 2012. |
| International Search Report and Written Opinion for PCT/US12/55636 dated Nov. 30, 2012. |
| International Search Report for PCT/US12/57528 dated Dec. 17, 2012. |
| International Search Report and Written Opinion for PCT/US2012/045601 dated Feb. 1, 2013. |
| International Search Report for PCT/US12/66898 dated Feb. 11, 2013. |
| International Search Report and Written Opinion for PCT/US2012/069557 dated Feb. 22, 2013. |
| International Search Report for PCT/US12/56759 dated Feb. 25, 2013. |
| International Search Report and Written Opinion for PCT/US12/65738 dated Apr. 19, 2013. |
| International Search Report and Written Opinion for PCT/US2013/020411 dated May 21, 2013. |
| International Search Report and Written Opinion for PCT/US2013/024538, dated May 31, 2013. |
| International Search Report and Written Opinion, dated Jul. 24, 2012 for PCT/US12/24772, filed Feb. 10, 2012. |
| Number | Date | Country | |
|---|---|---|---|
| 20130211890 A1 | Aug 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61441555 | Feb 2011 | US |
