U.S. patent application number 13/357474 was filed with the patent office on 2012-09-20 for statement portal with receipt tagging and associated enhanced benefit messaging.
Invention is credited to Allen Cueli, Lori D. VanDeloo.
Application Number | 20120239477 13/357474 |
Document ID | / |
Family ID | 46581364 |
Filed Date | 2012-09-20 |
United States Patent
Application |
20120239477 |
Kind Code |
A1 |
Cueli; Allen ; et
al. |
September 20, 2012 |
Statement Portal With Receipt Tagging And Associated Enhanced
Benefit Messaging
Abstract
Systems and methods are presented for providing a statement
portal with receipt tagging and associated enhanced benefit
messaging. In one potential embodiment, a method involves receiving
transaction information from the payment processing network, where
the transaction information is associated with a purchase
transaction, and receiving a photograph of a receipt. The
photograph is associated, using a processor of the statement portal
computer, with the purchase transaction. The system may then
receive benefit information, associate the benefit information with
the purchase transaction; and communicate the benefit information
to a communication device to inform the consumer associated with
the transaction about the benefit information. In various
embodiments the benefit information communicated to the consumer
may be a warranty expiration date. or an extended warranty
offer.
Inventors: |
Cueli; Allen; (Miami Lakes,
FL) ; VanDeloo; Lori D.; (Los Altos, CA) |
Family ID: |
46581364 |
Appl. No.: |
13/357474 |
Filed: |
January 24, 2012 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61435771 |
Jan 24, 2011 |
|
|
|
Current U.S.
Class: |
705/14.23 |
Current CPC
Class: |
G06Q 20/12 20130101;
G06Q 30/00 20130101; G06Q 20/047 20200501; G06Q 30/02 20130101;
G06Q 20/027 20130101 |
Class at
Publication: |
705/14.23 |
International
Class: |
G06Q 30/02 20120101
G06Q030/02 |
Claims
1. A method comprising: receiving transaction information at a
statement portal computer, wherein the transaction information is
associated with a purchase transaction; receiving a photograph of a
receipt at the statement portal computer; associating, using a
processor of the statement portal computer, the photograph of the
receipt with the purchase transaction; receiving benefit
information; associating the benefit information with the purchase
transaction; and communicating the benefit information to a
communication device.
2. The method of claim 1 further comprising: receiving, at the
statement portal computer, registration information associated with
a user account and user messaging preferences for the user
account.
3. The method of claim 2 further comprising: associating the
transaction information with the user account and verifying that
the purchase transaction corresponds with the user messaging
preferences for the account.
4. The method of claim 3 further comprising: communicating an alert
message to a communication device associated with the user account
when the purchase transaction corresponds with the user messaging
preferences for the account.
5. The method of claim 4 wherein communicating the alert message
comprises verifying the benefit information associated with the
transaction and communicating the benefit information with at least
a portion of the transaction information to the communication
device associated with the user account.
6. The method of claim 5 wherein verifying the set of benefit
information comprises: communicating at least a portion of the
transaction details to a third party service provider system; and
receiving a response identifying at least a portion of the set of
benefits from the third party service provider system.
7. The method of claim 5 wherein the set of benefit information
comprises an item return policy associated with a merchant, wherein
the merchant is identified by the transaction information.
8. The method of claim 4 wherein receiving the photograph of the
receipt further comprises receiving a set of benefit information
from the user in response to the alert message.
9. The method of claim 6 wherein the set of benefit information
comprises a warranty expiration date.
10. The method of claim 1 further comprising communicating a
supplemental benefit offer associated with the benefit information
after communicating the photograph of the receipt, the transaction
information, and the benefit information to a user based on a
deadline derived from the benefit information.
11. The method of claim 10 wherein the supplemental benefit offer
is an extended warranty offer associated with the purchase
transaction.
12. A statement portal computer for managing device data
comprising: a database comprising: transaction information received
from a payment processing network, wherein the transaction
information is associated with a purchase transaction; a photograph
received from a registered system user, wherein the photograph
comprises a receipt photograph associated with the purchase
transaction; and benefit information associated with the purchase
transaction; and a processor and a computer-readable medium coupled
to the processor, the computer-readable medium comprising code
executable by the processor for performing a method of receiving
the transaction information from the payment processing network,
receiving the photograph from the registered system user, receiving
the benefit information, and generating an alert message using the
transaction information and the benefit information.
13. The statement portal of claim 12 wherein the set of benefit
information comprises a bonus points expiration date.
14. The statement portal of claim 12 wherein the database further
comprises: a set of user registration information and a set of user
messaging preferences, wherein the set of user messaging
preferences is accessed by the processor to control the generating
an alert message using the transaction information and the benefit
information.
15. The statement portal of claim 12 wherein the set of user
registration information is further accessed by the processor to
control the receiving the transaction information from the payment
processing network, the receiving the photograph from the
registered system user, and the receiving the benefit
information.
16. A method comprising: transmitting, from a mobile device to a
statement portal computer, registration information associated with
a user account and user messaging preferences for the user account;
initiating, via a portable consumer device associated with the
mobile device, a transaction involving a payment processing
network, to create a set of transaction information; receiving, at
the mobile device, a transaction alert based at least in part on
the transaction information; transmitting, from the mobile device
to a statement portal, a receipt associated with the transaction
information; and receiving, at the mobile device, at least a
portion of the transaction information, a copy of photograph of the
receipt, and a benefit information alert for a benefit associated
with the transaction.
Description
CROSS-REFERENCES TO RELATED APPLICATIONS
[0001] The present application claims benefit under 35 U.S.C.
.sctn.119(e) of U.S. Provisional Patent Application No. 61/435,771,
entitled "Portable Device Data management," filed on Jan. 24, 2011,
the entire disclosure of which is incorporated herein by reference
for all purposes.
BACKGROUND
[0002] Warranties, bonus points, supplemental insurance, and other
such benefits are frequently provided to a user of a credit card or
other financial services. In other cases, such benefits are not
provided as a result of a consumer's use of a financial service,
but are nevertheless associated with products and services that a
consumer purchases using a credit or debit card. Frequently,
however, the existence of the benefit is forgotten by a consumer,
and the benefit is therefore lost. Alternatively, even when the
consumer has the correct information for a benefit, a benefit may
require a proof of purchase or some evidence that the consumer is
entitled to the benefit, and the required evidence is lost or
difficult to obtain.
BRIEF SUMMARY
[0003] Various embodiments according to the present innovations may
exist to provide a statement portal with receipt tagging and
associated enhanced benefit messaging. In one particular
non-limiting embodiment, a method involves receiving transaction
information from a payment processing network, where the
transaction information is associated with a purchase transaction,
and receiving a photograph of a receipt. The photograph is
associated, using a processor of the statement portal computer,
with the purchase transaction. The system may then receive benefit
information, associate the benefit information with the purchase
transaction; and communicate the benefit information to a
communication device to inform the consumer or user associated with
the transaction about the benefit information.
[0004] In various alternative methods, the system may implement a
method of receiving, at the statement portal computer, registration
information associated with a user account and user messaging
preferences for the user account associating the transaction
information with the user account. The method may further involve
verifying that the purchase transaction corresponds with the user
messaging preferences for the account or communicating an alert
message to a communication device associated with the user account
when the purchase transaction corresponds with the user messaging
preferences for the account.
[0005] Additional embodiments may involve a system including a
database. The database may include transaction information received
from a payment processing network, wherein the transaction
information is associated with a purchase transaction; a photograph
received from a registered system user, wherein the photograph
comprises a receipt photograph associated with the purchase
transaction; and benefit information associated with the purchase
transaction. Further, the system may include a messaging module
coupled to the database, wherein the notification module comprises
a processor and a computer-readable medium coupled to the
processor, the computer-readable medium comprising code executable
by the processor for performing a method of receiving the
transaction information from the payment processing network,
receiving the photograph from the registered system user, receiving
the benefit information, and generating an alert message using the
transaction information and the benefit information.
[0006] An additional possible implementation according to the
innovations presented herein includes a method of managing user
purchase benefit information in conjunction with a payment
processing network. The network may have enhanced messaging
capabilities. In certain embodiments the method performed by the
system includes transmitting, from a communication device to a
statement portal computer, registration information associated with
a user account and user messaging preferences for the user account;
initiating, via a portable consumer device associated with the
communication device, a transaction involving a payment processing
network, to create a set of transaction information; receiving, at
the communication device, a transaction alert based at least in
part on the transaction information; transmitting, from the
communication device to a statement portal, a receipt associated
with the transaction information; and receiving, at the
communication device, at least a portion of the transaction
information, a copy of photograph of the receipt, and a benefit
information alert for a benefit associated with the
transaction.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] FIG. 1 shows a system, according to one potential embodiment
of the innovations herein.
[0008] FIG. 2A shows a system, according to one potential
embodiment of the innovations herein.
[0009] FIG. 2B illustrates a transaction method that operates
according to an embodiment of the innovations herein.
[0010] FIG. 3A illustrates an example of an interface, according to
an embodiment of the innovations herein.
[0011] FIG. 3B illustrates an example of an interface, according to
an embodiment of the innovations herein.
[0012] FIG. 3C illustrates an example of an interface, according to
an embodiment of the innovations herein.
[0013] FIG. 3D illustrates an example of an interface, according to
an embodiment of the innovations herein.
[0014] FIG. 4 illustrates a transaction method that operates
according to an embodiment of the innovations herein.
[0015] FIG. 5A illustrates one potential embodiment of a
communication device or system that may make up elements of or be
used with various embodiments of the innovations presented
herein.
[0016] FIG. 5B illustrates one potential embodiment of a portable
consumer device that may be used with various embodiments of the
innovations presented herein.
[0017] FIG. 6 illustrates one potential embodiment of a computing
device or system that may make up elements of or be used with
various embodiments of the innovations presented herein.
[0018] FIG. 7 illustrates one potential embodiment of a computing
device or system that may make up elements of or be used with
various embodiments of the innovations presented herein.
DETAILED DESCRIPTION
[0019] Embodiments of the innovations disclosed herein include
systems and methods for providing enhanced personal portfolio data
management in conjunction with a payment processing network and a
portable device. More specifically, a system and method for storing
benefit information and associated proof of payment information
such as receipt information is provided, along with messaging
regarding benefit timing and expiration.
[0020] Although embodiments will be illustrated with reference to
specific implementations, a person of ordinary skill in the art
will understand that these implementations describe innovations
which may have broad use other than the specifically described
implementations. As described below, enhanced personal portfolio
management comprises systems and methods for a variety of
functions, including a statement portal with receipt tagging and
enhanced messaging. In one particular embodiment, photos of
receipts may be uploaded to the portal and associated with
particular transactions. Further, warranties or other benefits
requiring receipt data may further be associated with the receipt
and/or transaction, with associated deadlines and important dates.
The system may then use enhanced messaging to remind a user of
warranty or benefit deadlines.
[0021] Such a system includes advantages over systems currently
known in the art. Such advantages include an improved consumer
experience for transactions benefits such that users avoid the
experience of having a benefits go unused or unrecognized due to
lack of customer information. Users also may benefit from storage
of receipt information required by a benefit, to avoid loss of the
benefit or problems that may be associated with recovering proof of
payment information. Merchants and service providers may further
benefit from improved visibility of offered services and improved
customer satisfaction associated with the user of such
services.
[0022] Technical advantages may include increased integration and
interoperability between transaction record systems. Specifically,
receipt record information may be designed for specific and
automatic interoperability with transaction data from a payment
processing service or issuer computer, and my include further
interoperability between benefit timing and expiration records and
messaging services associated with a payment processing service or
issuer computer.
[0023] FIG. 1 illustrates a system 100 for performing an electronic
payment transaction in conjunction with a user according to an
embodiment of the invention. System 100 includes user 110, portable
consumer device 112, communication device 120, merchant computer
130, acquirer computer 140, payment processing network 150, IP
Gateway 170, issuer computer 160, third part provider system(s)
195, and statement portal computer 198.
[0024] Systems according to the present invention which include
communication between payment processing network 150, issuer
computer 160, and statement portal computer 198 may include
additional structures and methods for providing enhanced account
statements. In one potential embodiment, statement portal computer
198 comprises, stores, and/or manipulates receipt data associated
with an account of user 110. Receipt data may be provided to
statement portal computer by user 110 photographing a physical
receipt using communication device 120, and transmitting the photo
to statement portal computer 198. Alternatively, either payment
processing network 150 or issuer computer 160 may receive
electronic copies of such a receipt, and provide the receipt to
statement portal computer 198. The receipt may then be integrated
into an account statement that may be accessed later by user 110.
Further, the receipt may be in any suitable form including a JPEG
file, a GIP file, a PDF file, etc.
[0025] Third party provider systems 195 may include single or
multiple computing devices controlled by one or more third parties,
and may provide details for benefits that are associated with
particular payment transactions. Third party provider system 195
may include one or more computing devices associated with one or
more third party benefit providers. Such benefit providers may
manage benefits associated with portable consumer device 112 or
with transactions or items purchased by user 110 using portable
consumer device 112. For example, when user 110 purchases a device
having an associated warranty, and the device fails in a manner
covered by the warranty, the verification and compensation provided
by the warranty may be managed by a third party service provider,
and receiving the benefit of the warranty may require user 110 to
interact with third party service provider system 195.
[0026] In one potential embodiment, a receipt is associated with
tagging data. FIG. 4 includes one potential implementation of a
user interface for tagging of a receipt. User 110 may tag a receipt
with identifying category data prior to sending a copy of the
receipt from communication device 120 to statement portal computer
198. For example, a receipt for the purchase of food at a grocery
store may be tagged with a receipt tag corresponding to the
category "groceries." Alternatively, user 110 may access statement
portal computer 198 and add a receipt tag to the receipt already
contained in statement portal computer 198. In an alternative
embodiment, payment processing network 150 or issuer computer 160
may receive receipt data in a recognizable form from a merchant
computer 130 or acquirer computer 140. Payment processing network
150 or issuer computer 160 may analyze the receipt and add a
receipt tag prior to transmitting the receipt to statement portal
computer 198. In an alternative embodiment, statement portal
computer 198 may receive receipt data and perform optical character
recognition on the receipt to transform the receipt data into a
recognizable electronic format. Statement portal may then analyze
the receipt and add a receipt tag prior.
[0027] In one alternative embodiment, statement portal computer 198
may function as a repository for warranty receipts. In such an
embodiment, statement portal computer 198 receives only warranty
receipts with additional tagging information related to the
receipt. Statement portal computer 198 may then provide a
searchable statement to user 110 related to warranties of purchases
made by user 110. Statement portal computer 198 may additionally
provide warranty related messaging, such as a message to
communication device 120 when a warranty associated with a receipt
held by statement portal computer 198 is about to expire.
[0028] User 110 refers to an individual or organization such as a
business that is capable of purchasing goods or services or making
any suitable payment transaction with merchant computer 130.
[0029] As described herein electronic data and information may be
associated with a transaction by being created as part of an
electronic process of the transaction. For example, in a computer
process that creates and transmits a signal, the signal is
associated both with the device that created the signal and the
process that created the signal. Further, data or electronic
signals or storage records may further be associated with other
signals or computer readable data in a recording medium or database
by addition of association data to a database record. In one
potential example, a first set of data may be analyzed with a text
parser to identify the characters of the first set of data, a
second set of data may be analyzed with a text parser to identify
the characters of the second set of data, and a comparison process
or processor may electronically compare the characters of the data.
If the characters are similar, or meet association rules of the
process, then information may be appended to either set of data
indicating the results of the comparison.
[0030] Portable consumer device 112 refers to any suitable device
that allows the payment transaction to be conducted with merchant
computer 130. Portable consumer device 112 may be in any suitable
form. For example, suitable portable consumer devices 112 can be
hand-held and compact so that they can fit into a consumer's wallet
and/or pocket (e.g., pocket-sized). They may include smart cards,
magnetic stripe cards, keychain devices. Other examples of portable
consumer devices 112 include cellular phones, personal digital
assistants (PDAs), pagers, payment cards, security cards, access
cards, smart media, transponders, and the like. In some cases,
portable consumer device 112 may be associated with an account of
user 110 such as a bank account.
[0031] Communication device 120 may be in any suitable form. In
certain embodiments, communication device 120 may be a mobile
device or mobile phone. For example, suitable communication device
120 can be hand-held and compact so that they can fit into a
consumer's wallet and/or pocket (e.g., pocket-sized). Some examples
of communication device 120 include desktop or laptop computers,
cellular phones, personal digital assistants (PDAs), pagers,
payment cards, security cards, access cards, smart media,
transponders, and the like. In some embodiments, communication
device 120 and portable consumer device 112 are embodied in the
same device. In alternative embodiments, communication device may
be a desktop computer or laptop personal computer with internet
access. In further alternative embodiments, communication device
120 may be any device which allows user 110 to communicate
electronically with statement portal 196. Communication device 120
may communicate with computers such as merchant computer 130,
issuer computer 160, or IP Gateway 170 via any acceptable
communication medium and protocol, such as mobile phone standard
such as 3GPP, a wireless network 802.11 connection via gateway
connection to the internet, a wired connection to an additional
computer or computing device, or any other method or system.
[0032] Merchant computer 130 refer to a computer operated by any
suitable entity or entities (e.g., a merchant) that make a payment
transaction with user 110. The merchant computer 130 may use any
suitable method to make the payment transaction. For example,
merchant computer 130 may use an e-commerce business to allow the
payment transaction to be conducted by merchant computer 130 and
user 110 through the Internet. Alternatively, merchant computer 130
may comprise a point of sale (POS) device that is specifically
designed to accept data from portable consumer devices such as
portable consumer device 112, and to communicate with acquirer
computer 140 as part of a transaction authorization. Other examples
of merchant computer 130 include a department store, a gas station,
a drug store, a grocery store, or other suitable business.
[0033] Acquirer refers to any suitable entity that has an account
with merchant computer 130. In some embodiments an issuer may be
the same entity as an acquirer in a transaction, and thus, issuer
computer 160 may also be the same computer, system, or device as
acquirer computer 140.
[0034] Payment processing network (PPN) 150 refers to a network of
suitable entities that have information related to an account
associated with portable consumer device 112. This information
includes data associated with the account on portable consumer
device 112 such as profile information, data, and other suitable
information.
[0035] Payment processing network 150 may have or operate a server
computer and may include a database. The database may include any
hardware, software, firmware, or combination of the preceding for
storing and facilitating retrieval of information. Also, the
database may use any of a variety of data structures, arrangements,
and compilations to store and facilitate retrieval of information.
The server computer may be coupled to the database and may include
any hardware, software, other logic, or combination of the
preceding for servicing the requests from one or more client
computers. Server computer may comprises one or more computational
apparatuses and may use any of a variety of computing structures,
arrangements, and compilations for servicing the requests from one
or more client computers. In one potential embodiment, server
computer may be described by the computing device of FIG. 3. In
another potential embodiment, a server computer for use with the
present innovations may comprise only a portion of the elements of
FIG. 3.
[0036] Payment processing network 150 may include data processing
subsystems, networks, and operations used to support and deliver
authorization services, exception file services, and clearing and
settlement services. An exemplary payment processing network 150
may include VisaNet.TM.. Networks that include VisaNet.TM. are able
to process credit card transactions, debit card transactions, and
other types of commercial transactions. VisaNet.TM., in particular,
includes a integrated payments system (Integrated Payments system)
which processes authorization requests and a Base II system which
performs clearing and settlement services. Payment processing
network 150 may use any suitable wired or wireless network,
including the Internet.
[0037] IP Gateway 170 refers to an entity that includes one or more
servers and databases, and have access to various issuer data,
transaction data and user data used to generate and deliver
notifications and alert messages to various delivery channels. IP
Gateway 170 may be part of the payment processing network 150 or
may be a separate entity in communication with payment processing
network 150. In certain embodiments, statement portal computer 198
may integrate messaging to user 110 through IP gateway 170 and/or
payment processing network 150 to enable real time or near real
time messaging with communication device 120 regarding an in
process or recently completed purchase transaction.
[0038] Issuer refers to any suitable entity that may open and
maintain an account associated with portable consumer device 112
for user 110. Some examples of issuers may be a bank, a business
entity such as a retail store, or a governmental entity. In many
cases, an issuer may also issue portable consumer device 112
associated with the account to user 110.
[0039] Statement portal computer 198 comprises a computing device
that functions to provide statement information to user 110 in
accordance with the various embodiments described herein. In
certain embodiments, statement portal computer may be wholly or
partially implemented as part of payment processing network 150 or
issuer computer 160.
[0040] Transaction information or transaction data includes any
details from a financial transaction, such as payment amount, user
account information, payment time information, and similar such
information. Transaction data may include merchant identifier or
MCC data as discussed in more detail further below. Additional
examples of transaction information are discussed in various
embodiments of the innovations discussed herein.
[0041] Benefit information comprises any agreement or benefit
provided to a user as part of a transaction, and any associated
details such as expiration dates, benefit limits, replacement
policies, and the like. Further examples of benefit information
includes details related to item return policies, warranty
policies, reward points offered to a user as a result of a
particular transaction, and evidence requirements such as proof of
payment policies for use of any related benefit.
[0042] Transaction information may be associated with benefit
information according to various embodiments of the present
innovations. The transaction data may include information
corresponding to user's purchases, such as a description code
(e.g., NAICS: North American Industry Classification System)
associated with purchased items, cost of purchased items, and
transactions. The transaction data may further include, but not
limited to, a description of the purchased items, the payment
accounts used, an indication of whether the purchase was made
online, a confirmation number, a shipment status (e.g., order being
processed, shipped, delivered, on back order, etc.), a delivery
tracking number, a cancellation notice, updates, and/or the like.
Still further, the transaction data may include information
regarding one or more of the user's communication devices such as,
but not limited to, the device name (e.g., Apple iPhone.TM.,
Motorola Droid.TM., etc.), means of communication adopted by each
device (e.g., SMS message, Email, etc.), and a user-determinable
device preference (e.g., Apple iPhone.TM. device) for establishing
communications.
[0043] FIG. 2A shows one potential embodiment of a statement portal
computer 198 that may function in various systems in accordance
with the innovations presented herein. FIG. 2B details statement
portal computer 298, user communication device 220, third party
benefit systems 295, payment processing network 250, and issuer
computer 260. The function of the just previously listed computers
and devices may operate as described above fore the corresponding
elements of FIG. 1. FIG. 2A further discloses details of one
potential embodiment of a statement portal computer shown as
statement portal computer 298. Statement portal computer 298
comprises benefit tracking module 212, user messaging and alert
module 214, benefit identification module 216, transaction data
receiving module 218, third party benefit communication module 222,
and data management and storage module 224. All of the above listed
modules which are further described below may function as software
modules stored by computer readable storage 203 and executed by
processor 201 as part of statement portal computer 298.
Alternatively, the modules may be hardware implemented control
modules, or any acceptable combination of hardware and software
functioning within statement portal computer 298 to implement the
functions of the innovations described herein.
[0044] FIG. 2A includes transaction data receiving module 218 for
receiving transaction data. During operation of a payment
processing network such as VisaNet.TM., the payment processing
network may process a large volume of transactions that may process
many thousands of transactions in fractions of a second. In certain
embodiments, transaction data receiving module may communicate with
payment processing network 250 to identify a subset of the
transactions processed by payment processing network 250. The
subset of transactions that are requested for a statement portal as
data associated with statement portal users may be identified and
routed by the payment processing network 250. Alternatively the
transaction data receiving module 218 may have access to all
transaction data passing through payment processing network 250,
and may select data associated with registered statement portal
users while discarding or deleting data not associated with
statement portal users.
[0045] Alternatively, transaction data receiving module 218 may
interact with issuer computer 260. Such an interaction may be
particularly structured where a statement portal service is
provided to a user of an account associated with the issuer.
Transaction information for the issuer computer 260 may be
forwarded to transaction data receiving module 218 if the issuer
computer 260 identifies an account associated with the transaction
data as being registered to use a statement portal service.
[0046] As part of the operation of statement portal computer,
benefit identification module 216 may parse data from individual
transactions and implement data queries to determine whether or not
benefit information should be associated with a particular
transaction. Individual transactions may have no benefits or
benefit information associated, or may have benefit information
associated for multiple benefits. For example, a single transaction
may have a warranty benefit with a warranty expiration date, a
purchase price protection plan with a 30 day limit to identify an
identical product with a lower price, and associated rewards points
with a two year expiration date. Benefit identification module may
receive the transaction data with some or no benefit information
associated, and function to determine whether the benefit
information exists by querying third party benefit systems 295,
user communication devices 220, or any other resource such as a
standard benefit for a merchant identified by the transaction data.
When benefits are identified by benefit identification module,
benefit tracking module 212 may function as a scheduler that
manages benefit related information that is associated with users,
and the communication of benefit information such as expiration
deadlines to the user.
[0047] Third party benefit communication module 222 may manage a
communication link and a directory that allows statement portal
computer 298 to interact with a plurality of third party benefit
systems 295. For example, if statement portal computer 298 relies
on an information sharing agreement with any particular benefit
system 295, third party benefit communication module 222 may
function to insure that statement portal computer 298 complies with
the terms of the agreement. Similarly, user messaging and alert
module 214 may function to enable communication with any number of
user communication devices 220. User messaging and alert module 214
may additionally function as a secondary check on user preferences
to insure that a particular user has agreed to receive particular
messages from statement portal computer 298.
[0048] In addition to standard text messages or text data
interaction with applications functioning on user communication
devices 220, user messaging and alert module 214 may include
specialized functionality for receiving photographic data of
receipts that may be stored in benefit and receipt information 246
of database 226.
[0049] Finally, data management and storage module 224 may function
to manage access by other modules to statement portal database 226,
and to insure that transaction data, benefit information, and any
other data used by the system is properly stored for future use and
analysis.
[0050] The information managed by statement portal database 226 may
include user registration data 228 for individual users, as well as
any structure and function information required to maintain
database 226. The registered user data 228 may include user
messaging preferences 232 indicating when a user would or would not
like to receive messages from the system, a history of user
messaging responses 234 including copies of messages and user
responses. Such data may or may not be associated with particular
transactions, and may include preference update histories as well
as responses to various requests for receipts or supplemental
offers. The registration data may include any suitable information
including any suitable combination of the following: a PAN (Primary
Account Number) associated with a portable consumer device (e.g.,
payment card), a ZIP code, a mobile device identifier (e.g., mobile
phone number or phone number alias), an electronic serial number
(ESN), an International Mobile Equipment Identity (IMEI), a digital
certificate, an application identifier, and merchant website
account information (e.g., username, password, security
questions).
[0051] In certain embodiments, the system can include one or more
databases. The location of the database(s) is discretionary: merely
by way of example, a database 226 of FIG. might reside on a storage
medium local to (and/or resident in) a server (and/or a user
computer). Alternatively, a database 226 can be remote from any or
all of the computer 298 so long as the database can be in
communication (e.g., via the network) with one computer 298. In a
particular set of embodiments, a database 226 can reside in a
storage-area network ("SAN") familiar to those skilled in the art.
(Likewise, any necessary files for performing the functions
attributed to the computers or servers can be stored locally on the
respective computer and/or remotely, as appropriate.) In one set of
embodiments, the database 226 can be a relational database, such as
an Oracle.TM. database, that is adapted to store, update, and
retrieve data in response to SQL-formatted commands. The database
might be controlled and/or maintained by a database server, as
described above, for example.
[0052] Statement portal database 226 may further include data for
display as part of a user statement portal, saved as statement data
242. Statement data 242 may include transaction data storage 244
that includes data received from payment processing network 250 or
issuer computer 260, benefits information identified by benefits
identification module 216 as described above, and any associated
offers 248. Associated offers 248 may include data of offers that
may be scheduled for presentation to a user along with other
information or based on user selection offers. For example, if a
user has a preference requesting to be notified when a warranty has
10 days remaining before expiration of the warranty, associated
offers 248 may provide an offer from a third party benefit system
for the user to purchase an extended warranty. Similar offers may
be communicated to a user at the time of the transaction, or at any
other time accepted by the user where an offer is available for
presentation. Associated offers 248 may be identified by benefit
identification module 216 when queries are being presented to
various sources about the existence of benefits.
[0053] Thus, in certain embodiments, if benefit identification
module 216 creates a benefit query that is communicated to a third
party benefit system 295 by third party benefit communication
module 222, a response may include an indication the transaction
does or does not have an associated benefit, and may further
include an offer associated with the transaction.
[0054] In alternative embodiments, benefit identification module
216 may receive transaction data from transaction data receiving
module 218. Benefit identification module 216 may include a text
parser that operates using processor 201 to parse text data of any
received transaction data in order to identify account IDs or other
identifying information from the transaction data. Benefit
identification module 216 may then formulate a database query using
the ID or similar text string from the text parser. When the
database query is responded to, the benefit identification module
forward the transaction data forward the received data to another
module or may perform a comparison between the database information
received and another part of the transaction data to determine
whether there is an associated benefit for the transaction
data.
[0055] FIG. 2B provides one potential example of a method of
improved data device management for use in accordance with
embodiments of the innovations presented herein. In step S202, a
user 110 registers with statement portal computer 198 and
communicates user registration and associated account information
to the registration portal. In various embodiments, the
registration may occur in a communication from communication device
120 to statement portal computer 198, or from any other computing
device operated by user 110. In alternative embodiments, user 110
may interact with issuer computer 160 to create a user account with
statement portal computer 198 for user 110. In such a case the
information may be routed through issuer computer 160, or may occur
in parallel with communications to statement portal computer 198
and issuer computer 160 from user 110.
[0056] In step S204, the user 110 makes a purchase using an account
associated with the statement portal. In a typical payment
transaction process, user 110 purchases goods or services by
presenting his portable consumer device 112 to the merchant
computer 130, merchant computer 130 generates an authorization
request that includes, among other data, the data received from the
portable consumer device 112. Merchant computer 130 sends the
authorization request to the acquirer computer 140. Acquirer
computer 140 sends the authorization request to the payment
processing network 150 which passes the authorization request to
the issuer computer 160. Issuer computer 160 generates an
authorization response that indicates whether the transaction is
approved or declined. The authorization response is sent to the
payment processing network 150. Payment processing network 150
sends a copy of the authorization response the merchant computer
130 for presentation of an authorization or denial to user 110.
[0057] As part of the transaction of step S204, transaction data
from the transaction is passed to the statement portal. In one
embodiment, this data may be communicated to the statement portal
computer 198 from payment processing network 150 via IP Gateway 170
as detailed further below. In an alternative embodiment, the
transaction information may be communicated to the statement portal
computer 198 via issuer computer 160.
[0058] In step S206, the user 110 takes a photograph of a receipt
or proof of purchase document and uploads the photograph to the
statement portal along with warranty or other benefit information
and associated deadlines. In certain embodiments, only the receipt
information is provided by the user, and the benefit information
including expiration information is obtained automatically by the
system. In certain embodiments, the photograph is taken with
communication device 120. In certain other embodiments, enhanced
messaging may be used to communicate a message to a user with an
indication that a benefit is associated with a transaction, and
that expiration deadline and proof of payment records may be
beneficial for taking advantage of the benefit. The message may
serve as a prompt to user 110 to photograph and upload receipt
data. The message may also serve as a privacy control that allows
user 110 to select whether the user wants to be notified by a
message in the future regarding details of the benefit.
[0059] Further still, either as part of the prompt, or in response
to a user upload of receipt or deadline information from user 110,
the system may message user 110 with offers related to the benefit
such as extended warranty options, or options for bonus points or
bonus point expiration extensions. Such messaging may occur at or
near the time of purchase. Options related to such messaging may
further be controlled by user preference and registration settings
stored at statement portal computer 198.
[0060] In step S208, the statement portal identifies a messaging
trigger, such as a warranty expiration that is occurring within a
predetermined time period. When the messaging trigger is
identified, the system communicates an alert or reminder message to
user 110 with the warranty or benefit expiration information. Just
as above, the message may include associated offers such as benefit
extension or extended warranty offers, and settings for messages
associated with a messaging trigger may be set in statement portal
registration settings along with the settings for the messaging
associated with a new transaction discussed above.
[0061] Finally, in step S110, the statement portal computer 198 may
include a record of messages sent from statement portal computer
198 to user 110, including a list of expiration reminders, related
offers, and any related acceptances from the user. For example, if
an extended warranty offer is communicated to user 110 for a
transaction in statement portal computer 198, and the user 110
communicates an acceptance of the extended warranty offer, the
record of the acceptance may be associated with the original
transaction and stored at statement portal computer 198.
[0062] FIGS. 1 and 2A include various communication modules and
gateways for implementing messaging and alerts between statement
portals and user or third party systems. One potential messaging
system involves alert messages using an IP gateway such as IP
Gateway 170 of FIG. 1 or user messaging and alert module 214 of
FIG. 2A. The IP Gateway 170 or alert module 214 may includes a
notification server computer having a computer-readable medium
(CRM) 172, and a processor (not shown) that is coupled to the CRM.
The notification server computer may house more than one CRM as
needed to handle expanding volumes of messages. The notification
server computer may be in communication with a database such as
database 226 of FIG. 2A. Database 226 may contain benefit
information that is monitored by benefit tracking module 212 which
is father used generate an alert messages. The alert data may
simply include benefit information such as a warranty expiration
data, but may additionally include associated transaction data,
cardholder enrollment data, and issuer data, associated offers, or
any other information.
[0063] Messages to user communication devices 220 may function
using a variety of communication paths. In one embodiment, alert
messages with benefit information may be communicated via e-mail
servers which are server computers configured to receive an e-mail
from a network connection and store the e-mail in memory for future
retrieval. Mobile device carriers or communication device carriers
refer to entities that provide wireless infrastructures for
wireless data transfer and communication via cellular phone or
other mobile devices. These may also function as communication
paths. Example of such entities are AT&T.TM., Verizon
Wireless.TM., T-Mobile.TM., etc. Any other acceptable communication
format or path, including SMS messaging, telephone voice messaging,
or custom messaging may be used.
[0064] FIGS. 3A and 3B show potential examples of a user interfaces
to enable a communication device 120 to communicate with statement
portal computer 198 of FIGS. 1A and 1C. Such a user interface may
be enabled on communication device 120 as part of a device
application for communicating with statement portal computer 198.
Alternatively, the interface may be presented to communication
device 120 as part of an alert message following a transaction such
as the transaction in step S204 of FIG. 1 B. The message can be
generated using rules that generate certain messages and message
formats depending upon the values of certain data elements in the
transaction data 174. Such data elements can include: the merchant
identifier (e.g., the MCC), the amount of the transaction, and the
location of the transaction. In the case of the merchant
identifier, different classes of messages may be generated based on
the data indicating the type of merchant or data identifying the
specific merchant. For example, transaction data that indicates
that a transaction is being conducted at a department store may
send an intelligent alert message that indicates the name of the
merchant, the amount of the purchase and the date of the purchase.
In a department store transaction, the amount of the transaction is
known when a point of sale terminal at the store receives data from
the user's portable consumer device. Thus, in embodiments of the
invention, the content in the intelligent alert message may vary
depending on one or more of the following pieces of information in
or information derived from an authorization request message or
other data source. Such information may include or be derived from:
an account number, the date, a transaction amount, and a merchant
identifier (e.g., MCC, store number, merchant ID), or terminal
ID.
[0065] Continuing with the department store example, a message may
further include details of the store return policy, including
return deadlines and proof of payment requirements, as shown in
FIG. 2B. An alert message following a purchase may thus present
return information, benefit information, information related to
proof of payment requirements for return and benefit options; and a
prompt to upload a receipt. In certain embodiments, a message
and/or a receipt upload prompt may only be presented to user 110 in
predetermined circumstances, such as when proof of payment is
required to receive a benefit.
[0066] FIGS. 3C and 3D father show examples of user interfaces that
may function as part of the present innovations. FIG. 3C discloses
one potential embodiment of a registration interface for accepting
registration and user messaging preference data from a user. FIG.
3D discloses an example of a statement data interface. Statement
data interface may disclose transaction data such as purchase
amount, time, and associated accounts. Statement data interface may
additionally show benefit information such as a remaining time
allowed for return of the item purchased as part of a transaction,
whether an item purchased has an associated warranty, and whether
any other benefits are associated with the transaction. Many other
potential implementations of FIGS. 3C and 3D exist. For example,
the statement data interface may include a direct option for
uploading or replacing receipt data stored as part of a statement
portal computer and service.
[0067] FIG. 4 describes an additional alternative embodiment that
functions according to aspects of the present innovations. In step
S302, the statement portal computer 198 receives user registration
and associated account information. The registration information
may include any user preferences on messaging, privacy, and data
storage. In step S304, statement portal computer 198 receives
transaction information from a payment processing service, issuer,
or other source for an account associated with a user.
[0068] In step S306, the statement portal computer 198 Statement
portal identifies benefit or warranty information associated with
the transaction from uploaded receipt information, information
provided directly by user, or information obtained from a third
party service provider. Associated deadlines are identified and
recorded automatically by the system based on user preferences
identified as part of registration or user preference information
provided to the statement portal computer 198. In step S308, the
statement portal computer 198 messages user 110 with information
such as warranty, benefit, or reward points expiration. The message
may include associated offers such as benefit extension or extended
warranty offers. Finally, in step S310, the statement portal
computer 198 receives user messages or responses, and messaging and
user response information is updated and stored in the statement
portal. In certain embodiments, failures by the user to respond to
messages may additionally be recorded in statement portal computer
198 and presented as transaction data to the user when the user
reviews information in statement portal computer 198.
[0069] In one additional potential embodiment, statement portal
computer 198 may function in conjunction with an additional
computing service comprising Visa Feature Select (VFS) computing
systems that include communication links with third party provider
systems 195. In such an embodiment, VFS systems may include links
to third part provider systems 195 while issuer computer 160 does
not include a link to third party provider systems 195. In such a
system transaction information may be provided to VFS systems by
issuer computer 160, and queries communicated from VFS systems to a
plurality of third party provider systems 195 to determine any
benefits associated with the transactions identified. The third
party provider systems return the benefit information to VFS
systems, and any associated benefits are communicated to issuer
computer 160 or statement portal computer 198. In alternative
embodiments, the information may first be communicated to issuer
computer 160 from VFS systems and then to statement portal computer
198 form issuer computer 160.
[0070] FIG. 5(a) shows a block diagram of one potential example of
a mobile phone in phone 32 that can be used in embodiments of the
invention. Particularly, in certain embodiments input element 32(e)
of phone 32 may comprise a CCD camera or any other imaging device
that may be used to create receipt information that may be uploaded
to a statement portal computer to be associated with a transaction
as proof of payment benefit information or transaction information.
Additional details of phone 32 include that non-limiting example
presented by phone 32 may comprise a computer readable medium and a
body as shown in FIG. 5(a). The computer readable medium 32(b) may
be present within the body 32(h), or may be detachable from it. The
body 32(h) may be in the form a plastic substrate, housing, or
other structure. The computer readable medium 32(b) may be in the
form of (or may be included in) a memory that stores data (e.g.,
issuer account numbers, loyalty provider account numbers, and other
elements of split payment data) and may be in any suitable form
including a magnetic stripe, a memory chip, etc. The memory
preferably stores information such as financial information,
transit information (e.g., as in a subway or train pass), access
information (e.g., as in access badges), etc. Financial information
may include information such as bank account information, loyalty
account information (e.g., a loyalty account number), a bank
identification number (BIN), credit or debit card number
information, account balance information, expiration date, consumer
information such as name, date of birth, etc. Any of this
information may be transmitted by the phone 32.
[0071] The phone 32 may further include a contactless element
32(g), which is typically implemented in the form of a
semiconductor chip (or other data storage element) with an
associated wireless transfer (e.g., data transmission) element,
such as an antenna. Contactless element 32(g) is associated with
(e.g., embedded within) phone 32 and data or control instructions
transmitted via a cellular network may be applied to contactless
element 32(g) by means of a contactless element interface (not
shown). The contactless element interface functions to permit the
exchange of data and/or control instructions between the mobile
device circuitry (and hence the cellular network) and an optional
contactless element 32(g).
[0072] Contactless element 32(g) is capable of transferring and
receiving data using a near field communications ("NFC") capability
(or near field communications medium) typically in accordance with
a standardized protocol or data transfer mechanism (e.g., ISO
14443/NFC). Near field communications capability is a short-range
communications capability, such as RFID, Bluetooth.TM., infra-red,
or other data transfer capability that can be used to exchange data
between the phone 32 and an interrogation device. Thus, the phone
32 is capable of communicating and transferring data and/or control
instructions via both cellular network and near field
communications capability.
[0073] The phone 32 may also include a processor 32(c) (e.g., a
microprocessor) for processing the functions of the phone 32 and a
display 32(d) to allow a consumer to see phone numbers and other
information and messages. The phone 32 may further include input
elements 32(e) to allow a consumer to input information into the
device, a speaker 32(f) to allow the consumer to hear voice
communication, music, etc., and a microphone 32(i) to allow the
consumer to transmit her voice through the phone 32. The phone 32
may also include an antenna 32(a) for wireless data transfer (e.g.,
data transmission).
[0074] In some embodiments, information in the memory may also be
in the form of data tracks that are traditionally associated with
credits cards. Such tracks include Track 1 and Track 2. Track 1
("International Air Transport Association") stores more information
than Track 2, and contains the cardholder's name as well as account
number and other discretionary data. Track 2 ("American Banking
Association") is currently most commonly used. This is the track
that is read by ATMs and credit card checkers. The ABA (American
Banking Association) designed the specifications of this track and
all world banks must abide by it. It contains the cardholder's
account, encrypted PIN, plus other discretionary data. Such data
may be used by the system as transaction data.
[0075] FIG. 5B shows an embodiment of a portable consumer device.
Portable consumer device 33 may include a magnetic stripe 33(n)
that has a recording of track data as described above. Portable
consumer device 33 further may include customer information 33(m)
including account information for an account or a primary account
associated with the device and the data stored by the device.
Portable consumer device 33 may additional include a contactless
element 33(o) that stores track data in an element capable of
communicating with a point of sale or other access device
wirelessly.
[0076] FIG. 6 shows a block diagram of one potential example of a
point of sale or access device that may be used with various
embodiments that function according to the innovations presented
herein. The access device 34 comprises a processor 34(c)
operatively coupled to a computer readable medium 34(d) (e.g., one
or more memory chips, etc.), input elements 34(b) such as buttons,
a touchscreen display, or a combination of such interfaces, a
reader 34(a) (e.g., a contactless reader, a magnetic stripe reader,
etc.), an output device 34(e) (e.g., a display, a speaker, etc.)
and a network interface 34(f). The computer readable medium may
comprise instructions or code, executable by a processor. The
instructions may include instructions sending and receiving
authorization requests and responses, and for sending and receiving
transaction interrupt queries and responses.
[0077] In addition to the embodiments of various participants and
elements of the system shown in FIGS. 4-6, the computer, device,
and system elements of FIGS. 1-3 may operate one or more computer
apparatuses to facilitate the functions described herein. Any of
the elements in the figures may thus use any suitable number of
subsystems to facilitate the functions described herein. Examples
of one potential embodiment including such subsystems or components
are shown in FIG. 7. The subsystems shown in FIG. 7 are
interconnected via a system bus 775. Additional subsystems such as
a printer 774, keyboard 778, fixed disk 779 (or other memory
comprising computer readable media), monitor 776, which is coupled
to display adapter 782, and others are shown. Peripherals and
input/output (I/O) devices, which couple to I/O controller 771, can
be connected to the computer system by any number of means known in
the art, such as serial port 777. For example, serial port 777 or
external interface 781 can be used to connect the computer
apparatus to a wide area network such as the Internet, a mouse
input device, or a scanner. The interconnection via system bus
allows the central processor 773 to communicate with each subsystem
and to control the execution of instructions from system memory 772
or the fixed disk 779, as well as the exchange of information
between subsystems. The system memory 772 and/or the fixed disk 779
may embody a computer readable medium.
[0078] Given the above description, one potential embodiment may
describe a method comprising: receiving transaction information
from a payment processing network at a statement portal computer,
wherein the transaction information is associated with a purchase
transaction; receiving a photograph of a receipt at the statement
portal computer; associating, using a processor of the statement
portal computer, the photograph of the receipt with the purchase
transaction; receiving benefit information; associating the benefit
information with the purchase transaction; and communicating the
benefit information to a communication device.
[0079] Another embodiment may describe a method comprising:
receiving transaction information from an issuer computer at a
statement portal computer, wherein the transaction information is
associated with a purchase transaction; receiving a photograph of a
receipt at the statement portal computer; associating, using a
processor of the statement portal computer, the photograph of the
receipt with the purchase transaction; receiving benefit
information; associating the benefit information with the purchase
transaction; and communicating the benefit information to a
communication device.
[0080] Another embodiment may describe a method comprising:
receiving transaction information at an issuer computer, wherein
the transaction information is associated with a purchase
transaction; receiving a photograph of a receipt at the issuer
computer; associating, using a processor of the issuer computer,
the photograph of the receipt with the purchase transaction;
receiving benefit information at the issuer computer; associating
the benefit information with the purchase transaction using a
processor of the issuer computer; and communicating the benefit
information to a communication device associated with a user.
[0081] Another embodiment may describe a method comprising:
receiving transaction information at an payment processing network,
wherein the transaction information is associated with a purchase
transaction; receiving a photograph of a receipt at the payment
processing network; associating, using a processor of the payment
processing network, the photograph of the receipt with the purchase
transaction; receiving benefit information at the payment
processing network; associating the benefit information with the
purchase transaction using a processor of the payment processing
network; and communicating the benefit information to a
communication device associated with a user.
[0082] Further, in any of the above described embodiments may be
implemented as machine implemented instructions for performing the
listed processes, or as computer readable instructions recorded in
a computer readable instruction medium, using any of the electronic
computer hardware or computer systems described herein.
[0083] The software components or functions described in this
application may be implemented as software code to be executed by
one or more processors using any suitable computer language such
as, for example, Java, C++ or Perl using, for example, conventional
or object-oriented techniques. The software code may be stored as a
series of instructions, or commands on a computer-readable medium,
such as a random access memory (RAM), a read-only memory (ROM), a
magnetic medium such as a hard-drive or a floppy disk, or an
optical medium such as a CD-ROM. Any such computer-readable medium
may also reside on or within a single computational apparatus, and
may be present on or within different computational apparatuses
within a system or network.
[0084] The present invention can be implemented in the form of
control logic in software or hardware or a combination of both. The
control logic may be stored in an information storage medium as a
plurality of instructions adapted to direct an information
processing device to perform a set of steps disclosed in
embodiments of the present invention. Based on the disclosure and
teachings provided herein, a person of ordinary skill in the art
will appreciate other ways and/or methods to implement the present
invention.
[0085] The uses of individual numerical values are stated as
approximations as though the values were preceded by the word
"about" or "approximately." Similarly, the numerical values in the
various ranges specified in this application, unless expressly
indicated otherwise, are stated as approximations as though the
minimum and maximum values within the stated ranges were both
preceded by the word "about" or "approximately." In this manner,
variations above and below the stated ranges can be used to achieve
substantially the same results as values within the ranges. As used
herein, the terms "about" and "approximately" when referring to a
numerical value shall have their plain and ordinary meanings to a
person of ordinary skill in the art to which the particular subject
matter is most closely related or the art relevant to the range or
element at issue. The amount of broadening from the strict
numerical boundary depends upon many factors. For example, some of
the factors which may be considered include the criticality of the
element and/or the effect a given amount of variation will have on
the performance of the claimed subject matter, as well as other
considerations known to those of skill in the art. As used herein,
the use of differing amounts of significant digits for different
numerical values is not meant to limit how the use of the words
"about" or "approximately" will serve to broaden a particular
numerical value. Thus, as a general matter, "about" or
"approximately" broaden the numerical value. Also, the disclosure
of ranges is intended as a continuous range including every value
between the minimum and maximum values plus the broadening of the
range afforded by the use of the term "about" or "approximately."
Thus, recitation of ranges of values herein are merely intended to
serve as a shorthand method of referring individually to each
separate value falling within the range, unless otherwise indicated
herein, and each separate value is incorporated into the
specification as if it there individually recited herein.
[0086] It is to be understood that any ranges, ratios and ranges of
ratios that can be formed by, or derived from, any of the data
disclosed herein represent further implementations of the present
disclosure and are included as part of the disclosure as though
they were explicitly set forth. This includes ranges that can be
formed that do or do not include a finite upper and/or lower
boundary. Accordingly, a person of ordinary skill in the art most
closely related to a particular range, ratio or range of ratios
will appreciate that such values are unambiguously derivable from
the data presented herein.
[0087] The use of the terms "a" and "an" and "the" and similar
referents in the context of this disclosure (especially in the
context of the following claims) are to be construed to cover both
the singular and the plural, unless otherwise indicated herein or
clearly contradicted by context. All methods described herein can
be performed in any suitable order unless otherwise indicated
herein or otherwise clearly contradicted by context.
[0088] The use of any and all examples, or exemplary language
(e.g., such as, preferred, preferably) provided herein, is intended
merely to further illustrate the content of the disclosure and does
not pose a limitation on the scope of the claims. No language in
the specification should be construed as indicating any non-claimed
element as essential to the practice of the claimed invention.
[0089] For figures and descriptions describing various embodiments
of the innovations presented herein further understanding of the
nature and advantages of the present invention herein may be
realized by reference to the remaining portions of the
specification and the attached drawings. References to "steps" of
the present invention or innovations in the figures or detailed
description should not be construed as limited to "step plus
function" means, and are not intended to refer to a specific order
for implementing the invention.
[0090] Use of the phrase `the invention` or `the present invention`
is not meant to limit the claims in any manner and no conclusion
should be drawn that any description or argument associated with a
particular use of the phrase `the invention` or `the present
invention` applies to each and every claim. The use of the phrase
`the invention` or `the present invention` has been used solely for
linguistic or grammatical convenience and not to effect a
limitation of any nature on any of the claims.
[0091] Alternative implementations invention are described herein,
including the best mode known to the inventors for carrying out the
claimed invention. Of these, variations of the disclosed
implementations will become apparent to those of ordinary skill in
the art upon reading the foregoing disclosure. The inventors expect
skilled artisans to employ such variations as appropriate, and the
inventors intend for the claimed invention to be practiced
otherwise than as specifically described herein. Accordingly, the
claimed invention includes all modifications and equivalents of the
subject matter recited in the claims appended hereto as permitted
by applicable law. Moreover, any combination of the above-described
elements in all possible variations thereof is encompassed by the
claimed invention unless otherwise indicated herein or otherwise
clearly contradicted by context.
* * * * *