Patent Application
20100325024
1. Technical Field
This invention relates generally to wireless communication devices, and more particularly to an obligation management system and corresponding method suitable for use with wireless communication devices.
2. Background Art
People enjoy socializing. Groups of friends routinely get together to exchange stories, catch up on each other's lives, and generally enjoy the companionship of congenial friends. For example, it is not uncommon for a group of friends to get together in a restaurant once a week to share stories and a meal.
A problem associated with such outings occurs when the bill arrives. Dividing the bill can be troublesome. It can be almost impossible without the assistance of a calculator. One friend will have soup and a salad only, while another friend enjoys the four-course chef's tasting menu, complete with wine pairings. Even if the group successfully divides the bill, payment of each person's share can still be problematic. One friend has no cash and wants to pay by credit card, while another only has travelers cheques. Seldom will a member of the group have exact change. For instance, a member with a small tab might not have anything smaller than a $100 bill, thereby requiring change.
To solve this problem, one friend in the group might decide to pick up the tab one week, allowing another to pick up the tab the next week. This process works well, provided that the members can remember who paid when. Remembering the details week to week can be difficult. This difficulty can be further compounded when the group changes venue from week to week. A friend picking up the tab at a restaurant having two Michelin® stars one week may not feel fully remunerated when another friend picks up the tab at a burger joint the next week.
There is thus a need for a system and method of tracking obligations undertaken and fulfilled by members of a group.
Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
Before describing in detail embodiments that are in accordance with the present invention, it should be observed that the embodiments reside primarily in combinations of method steps and apparatus components related to tracking obligations incurred by a group and determining which member or members will fulfill a current obligation based upon an obligation fulfillment history. Embodiments of the invention are operable with electronic devices, such as wireless communication devices. Embodiments of the invention work in conjunction with data and files stored in computer readable media. The method steps described herein can thus be used to transform memory states of storage devices and computer readable media by transforming gates, switches, and storage devices, and therefore the physical state of the data and files, from a first state to a different second state.
It will be appreciated that embodiments of the invention described herein may be comprised of one or more conventional processors, computer readable media, and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of managing obligations and determining which member or members of a group will fulfill a new obligation as described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. The computer readable media can include electromagnetic storage, optical storage, or other data storage devices. As such, the functions described herein may be interpreted as steps of a method to perform obligation management in a wireless communication device. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits, in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used. It is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and circuits with minimal experimentation.
Embodiments of the invention are now described in detail. Referring to the drawings, like numbers indicate like parts throughout the views. As used in the description herein and throughout the claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise: the meaning of “a,” “an,” and “the” includes plural reference, the meaning of “in” includes “in” and “on.” Relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, reference designators shown herein in parenthesis indicate components shown in a figure other than the one in discussion. For example, talking about a device (10) while discussing figure A would refer to an element, 10, shown in figure other than figure A.
Embodiments of the present invention provide a method and system in a wireless communication device for tracking and sharing obligations incurred by a group. For example, where a group routinely goes to lunch at restaurants only accepting cash, embodiments of the invention provide systems and methods for tracking which member or members of the group pays the bill. As such, embodiments of the invention can assist in selecting the next person to pay based upon the group's obligation fulfillment history.
In one embodiment, the system and method determines who is a member of the group. The system and method then tracks who fulfills obligations of the group and when those obligations are fulfilled. The system and method then maintains a virtual “obligations due” account, which can be stored on one or more wireless communication devices belonging to the members or alternatively on a remote server or computer.
When the group undertakes an obligation, such as going to another group lunch, the system and method compares the obligation to an obligation register containing an obligation fulfillment history corresponding to the group. The system and method then determines which member or members should fulfill the current obligation. For example, in one embodiment, the system and method can consider who paid the lunch tab most recently, or which member has not fulfilled the group obligation for the longest period of time. Alternatively, in another embodiment, the system and method can consider which member of the group “owes” the most to other members of the group.
Embodiments of the invention are not limited to monetary transactions. Other types of obligations can also be monitored. For example, if members of a group frequently barter, the system and method can track these barter transactions. Similarly, if members of a group routinely have “covered dish suppers” at each others' homes, the system and method can track obligations such as which members home should be used next or which member should be responsible for the entree.
Turning now to
The wireless communication device 100 may be a mobile wireless handset, such as a mobile telephone. For example, the wireless communication device 100 may be a CDMA, GSM/GPRS, or some other type of mobile communications device. While a mobile telephone is shown in the illustrative embodiment of
In the illustrative embodiment of
The processor 102 can include other processing units dedicated to performance of specific functions. For example, an integrated or stand-alone digital signal processor (DSP) may handle the processing of incoming signals or data. In the illustrative embodiment of
In one embodiment, the processor 102 executes code comprising one or more routines stored either in the memory 103, which may comprise one or more memories. The memory 103 may comprise a separate and distinct integrated circuit connected and operable with the processor via a data bus (not shown). The memory 103 may include one or more read-only memories, dynamic or static random-access memory, or any other type of programmable memory, such as one or more EPROMs, EEPROMs, registers, and the like. In some embodiments, the memory 103 can comprise non-traditional storage devices, such as a SIM, USIM, R-UIM, NVM, etc. The routines stored in the memory 103 can be stored in the form of executable software, firmware, or in any other fashion known to those skilled in the art. The processor 102 is configured to execute instructions stored in the memory 103 to provide the functionality of the wireless communication device 100.
In addition to the executable code operable with the processor 102, the memory 103 may further store information received from another device via the wireless communication circuit 104, or information generated by the user through the user input 106. The information from the other devices may include identification of the members of a group, information regarding obligations undertaken, and so forth.
The processor 102 is also coupled to and operable with a wireless communication circuit 104, such as the radio transceiver shown in
The processor 102 is additionally operable with a user interface, which can include a display and user input 106. One example of a user input 106 is the keypad shown in
In one embodiment, the wireless communication device 100 includes an obligation manager 101, which may be configured as executable code and stored in the memory 103. Alternatively, it can be configured in hardware as programmable logic. The obligation manager 101 is operable with the processor 102 and is configured to track a plurality of obligations incurred by one or more groups. Further, the obligation manager 101 is configured to keep an accounting of the members of the group that fulfill those obligations, so as to assist a user in determining which member or members should fulfill a current obligation. The obligations can take many forms, including billed amounts for goods, quantities and types of goods or services received by a group, information corresponding to barter transactions, and so forth.
As will be shown in more detail in
Consider the situation where members of a group gather for lunch. The obligation manager 101 is initially configured to determine 108 which members of the group are present. This can be done in a variety of ways. In one simple embodiment, the user of the wireless communication device 100 having the obligation manager 101 operable therewith may enter information identifying the members present from the user interface 106. The user may type the member's names in or, alternatively, select the members from an address book, contact list, or other list of people stored in the memory 103. In another embodiment, such as where each member of the group has a wireless communication device, the obligation manager of the wireless communication device 100 can be configured to automatically detect the presence of the other devices through a local area communication network such as Bluetooth® or wide area communication network as is known in the art.
Once the members of the group are known, the user, in one embodiment, can configure how the obligation manager 101 selects the member or members who will be responsible for future obligations via the user interface 106. For example, the user may program the obligation manager 101 to select the member fulfilling the obligation on a round-robin basis. Alternatively, the user may program the obligation manager 101 to select the member fulfilling the obligation based upon which member has gone the longest without fulfilling a group obligation. Similarly, the user may program the obligation manager 101 to select the member fulfilling the obligation so as to reduce the largest amount owed to another member. In one embodiment, the user can defer to the obligation manager 101 to select the member fulfilling the obligation on an optimized basis. It will be clear to those of ordinary skill in the art having the benefit of this disclosure that the invention is not so limited. Other means for selecting the member to fulfill the obligation can also be used.
The obligation manager 101 determines 109 that a current obligation is due. In one embodiment, this can be done by receiving data via the wireless communication circuit 104. For instance, a merchant can transmit an amount due from a computer or cash register having wireless communication capabilities. In another embodiment, the user may input the details of the obligation via the user interface 106. The obligation manager 101 may then optionally notify the members of the group of the obligation. This notification can be done directly, such as through a local area network communication circuit. Alternatively, this can be done through a wide area network communication circuit, such as via an instant message or text message.
Once the debt is determined, in one embodiment, the obligation manager 101 retrieves 110 an obligation register (one example of which is shown in
Once retrieved, the obligation manager 101 compares 111 the obligation due with the obligation register to determine 115 which members of the group should be responsible for fulfilling the current obligation. As noted above, this can be done in a variety of ways, including by largest amount owed 112, round robin 113, most recently or least recently fulfilling an obligation 114, and so forth. Continuing with the lunch example above, the obligation manager may consider which member of the group has least recently paid for lunch for the group, and may select that member to pay for the current lunch tab.
A communication module 116, operable with the processor 102 and the wireless communication circuit 104, can then be configured to notify the one or more members to fulfill the obligation for the group. For instance, the communication module 116 may transmit a text message to the members informing them that it is their turn to pay for lunch. Alternatively, the communication module 116 may directly transmit a data file to obligation managers of other devices indicating the results of the fulfillment determination process so that the other members' devices can likewise be updated.
The obligation manager 101 then performs an accounting 117 by updating the obligation register in accordance with the member selection. In one embodiment, the obligation manager is configured to complete this task by recording an obligation due for the members not fulfilling the current obligation, and by subtracting an amount due by the members fulfilling the current obligation from a value owed by the one or more members fulfilling the current obligation.
Using a simple example, consider the situation when Tom, Fred, and George go to lunch. If the tab is $12, and George pays, the obligation manager 101 may record an obligation due by Fred and George of $4 each. When the three go to lunch the next time, and the tab is $15, and Tom pays, the obligation manager 101 can record this fulfillment such that George now has an obligation due of $1, while Fred has an obligation due of $9.
Embodiments of the invention can be used to itemize obligations due by the amount of a debt incurred by members of the group. This is simply performed when the obligation manager 101 determines 109 the obligation is due electronically. The merchant may simply transmit an itemized bill to the obligation manager 101 via the wireless communication circuit 104. Alternatively, the user may enter an itemized bill via the user interface 106.
Using the simple example of Tom, Fred, and George, suppose in the $12 check, Tom is responsible for $2, Fred for $5, and George for $5. When George pays, the obligation manager 101 may record an obligation due by Fred of $5 to George, and another obligation due by Tom to George of $2. Now suppose that in the $15 check, George, Tom, and Fred are each responsible for $5. When Tom pays, the obligation manager 101 can record this fulfillment such that George now has an obligation due of $3 to Tom, while Fred has an obligation due of $5 to Tom and $5 to George.
In one embodiment, an optional negotiation can occur via a negotiation module 118. The negotiation module 118 can be configured to receive one or more offers from the group to fulfill the obligation independent of the selection made by the obligation manager 101. Where this offer is accepted, the obligation manager 101 can, in response, record the accepted offer as a fulfillment in the obligation register.
For instance, even though the obligation manager 101 selects one or more members to fulfill a current obligation, another member may volunteer to pay. By way of example, if the obligation manager 101 selects Tom to pay, and its Tom's birthday, George may elect to pay for Tom. The obligation manager 101 can be configured to account for this in a variety of ways. In one embodiment, this can be considered a gratis gift of George, which would not cause Tom to incur an obligation due. Alternatively, Tom may want to pay for George on his birthday, and so this particular transaction can be accounted accordingly. Additionally, one member may want to “square up” with the group. In such a situation, the negotiation module 118 may relay an offer from that member to clear all obligations due. The obligation manager may then compute a total amount due by that member, and may inform that member of this amount.
There may be some situations in which a method of selection has been configured by the user that results in a tie. For instance, a user may configure the obligation manager 101 to select a member to fulfill an obligation by determining which member has gone the longest without fulfilling an obligation. It is possible that a tie will result. In one embodiment, the obligation manager is configured to break ties by random choice.
Turning now to
At step 201, the method 200 determines the members of the group. As noted above, this step 201 can be accomplished in several ways. The user may employ a user interface (106) to enter the members of a group, such as selecting members from an address book. Alternatively, the method 200 may determine the members electronically, such as through a local or wide area network wireless communication circuit.
Note as well that the method can be used for multiple groups. For example, a particular user may play golf with one group, go to business lunches with another group, and go to movies with yet another group. Members of these groups can overlap. As such, one person may be a member of two groups. Tom, for example, may be a member of the “golf group” and the “lunch group.”
At step 202, the method 200 determines that an obligation is due. In one embodiment, this determination is accomplished by receiving data through the wireless communication circuit (104). In another embodiment, the user may manually enter data relating to the obligation through the user interface (106). At this step 202, the method 200 may further determine a portion of the obligation that is attributable to each of the members where itemized accounting is desired.
Upon detecting the obligation at step 202, the method 200 accesses an obligation register from a memory device at step 203. In one embodiment, the obligation register includes an accounting of at least one member fulfilling at least one past obligation. For example, the accounting for the “lunch group” may track dollars spent for lunch, who has paid these dollars for the group, and amounts owed to or from each member of the group. Similarly, the “golf group” may track rounds of golf paid for by each member, as well as dollars owed from gentlemanly wagering such as the dollar Nassau engaged by the members.
As briefly mentioned above, embodiments of the invention are not limited to monetary transactions. For example, in one embodiment, the method 200 can track obligations owed that result from barter transactions. In these scenarios, the method 200 can be optionally configured to allow a user to set a monetary equivalent or other valuation for the barter or non-monetary transaction.
At step 204, the method 200 compares the obligation register with the current obligation to determine, at step 205, which one or more members of the group should fulfill the obligation that is currently due. As mentioned above, there are a variety of factors that can be used by the method 200 to make this determination. In one embodiment, step 205 includes determining recently fulfilling members 209 who have fulfilled recent obligations of the group. In another embodiment, this step 205 includes determining one or more members who have obligations due 210 that are greater than those owed by other members of the group. Other factors 211 may also be used.
At step 206, the method 200 notifies the one or more members who are to be responsible for fulfillment of the obligation. Alternatively, the method 200 can simply notify each member of the group of the determination of step 205. Optionally, the method 200 can notify the members not responsible for fulfilling the current obligation that the one or more will be responsible for fulfilling the obligation at step 206.
This notification step 206 can occur in a variety of ways. For example, in one embodiment, the method 200 may present the result on the display. Alternatively, the method 200 can transmit a message to the other members via the wireless communication circuit (104) and the communication module (116) indicating the results of the determination. In another embodiment, the method 200 may simply announce the result over a speaker. It will be clear to those of ordinary skill in the art having the benefit of this disclosure that numerous other means of communication between wireless communication devices known in the art can be used, and embodiments of the invention are not to be limited in this respect.
At step 207, negotiation of the selection may occur. In one embodiment, the method 200 receives a negotiation communication from one or more of the members in response to notifying them to fulfill the obligation. For instance, a member may dispute the amount owed. In another scenario, the selected member may have forgotten to bring cash to the event, and accordingly may ask the group's indulgence to pass on this selection and pay the next time. Alternatively, the negotiation communication may be from members other than those selected at step 205. This may be the case in the birthday example described above.
Turning briefly to
At decision 402, the method (200) determines whether to override the selection (made at step 205 of
Where the offer is accepted, the method (200) determines whether the offer is a “clear the register” offer at decision 403. Where it is not, the method (200) accounts for the obligation fulfillment normally at step 404. This accounting, in one embodiment, comprises removing the recording of the fulfillment of the obligation by the one or more selected members in the obligation register and recording another fulfillment of the obligation for the offering member.
Where it is a “clear the register” transaction, the method (200) provides the offering member with a total amount due, or a value corresponding to the obligations owed, at step 405. The method (200) then receives confirmation that the current obligation is fulfilled at step 406.
Turning back to
Turning now to
In one embodiment, the obligation register 300 has stored therein an obligation fulfillment history. The obligation fulfillment history is comprised of a plurality of fulfillment entries 301,302,303. The fulfillment entries 301,302,303 are records of past obligations of the group and identification of members 307,308,309 fulfilling those obligations. Additionally, the obligation register 300 may include obligation entries 304,305,306 that indicate obligations owed to the group or to individual members.
In the illustrative embodiment of
The illustrative embodiment of
In this illustrative embodiment, the members 307,308,309 have set the obligation manager (101) to track obligations with itemization. Given this configuration, each member entry has an obligation entry 304,305,306 that indicates an obligation due to other members. Due to the members present at each outing, some members 307,309 have obligations due to only one member. Other members 308 have obligations due to multiple members.
Using the obligation register 300 of
Turning now to
Each member is represented by a portable communication device 501,502,503,504,505,506 that they carry. These portable communication devices 501,502,503,504,505,506 can communicate with each other either through a network 507, such as with a wireless transceiver, or directly 508 via a local area wireless communication capabilities.
As indicated at step 601, the six members of the group have met for lunch. In this illustrative embodiment, portable communication devices 501,502,503,504, and 505 are equipped with an embodiment of an obligation manager, while portable communication device 506 does not.
As indicated at step 602, the group finishes lunch and the bill 509, which represents the obligation undertaken by the group in this illustration, arrives. While the bill 509 could be transmitted to the obligation manager electronically, in this illustrative embodiment the bill 509 arrives in paper form. The user with portable communication device 501 picks up the bill and launches the obligation manager on his portable communication device 501.
As indicated at step 603, the obligation manager of portable communication device 501 electronically detects the presence of portable communication devices 502,503,504, and 505 by communicating directly 508 with these devices via a wireless local area network communications circuit disposed in each device. As portable electronic device 506 does not include this capability, the user of portable communication device 501 selects this member from an address book stored in portable communication device 501 via its user interface. The members of the group are now identified for the obligation manager of portable communication device 501.
As indicated at step 604, the user of portable communication device 501 enters the amount of the bill into the obligation manager. The user may optionally add in a gratuity amount. Also, the user may optionally itemize the bill for each member as well. The communication module of portable communication device 501 then transmits 510 this information electronically to portable communication devices 502,503,504, and 505. The user of portable communication device 506 can review the information on the display of portable communication device 501.
As indicated at decision 605, the members can accept the data or can request an alternate amount. A member may request an alternate amount due to a typographical error or omission. As indicated at step 606, once the members have all accepted, the user of portable communication device 501 can then fulfill the obligation for the group. The obligation manager of portable communication device 501 then records this fulfillment in its obligation register. Similarly, the obligation managers of portable communication devices 502,503,504, and 505 may enter fulfillment entries, and corresponding obligation entries, in their obligation registers. This data can be used to select the member fulfilling the obligation the next time, as previously described herein.
As illustrated and described, embodiments of the invention can be used for a group that consumes a service, item, or other consumable on a regular basis. When members of the group are out consuming the service or purchasing the items, members of the group can be electronically discovered or manually entered through a user interface. An obligation manager can then suggest which member should fulfill the obligation for the group. The obligation manager can further track obligation fulfillment records in an obligation register.
In the foregoing specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Thus, while preferred embodiments of the invention have been illustrated and described, it is clear that the invention is not so limited. Numerous modifications, changes, variations, substitutions, and equivalents will occur to those skilled in the art without departing from the spirit and scope of the present invention as defined by the following claims. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims.
