When a person makes a trip, for example, a business trip from San Francisco to New York, he may decide to take a side trip on personal business, such as, to continue the above example, a side trip from New York to Philadelphia to visit family, or perhaps a side trip to Boston to take in a baseball game. In most cases the traveler would find it advantageous to book this side trip as part of his business trip, and, depending on the company policies, he would then be required to reimburse the company for the costs incurred during the side trip (e.g., hotel and transportation). However, in some cases, the traveler may also prefer that the side trip is not visible to the company.
What is clearly needed is a system and method that allows a user to make one complex, multi-part booking or transaction in which some components may be purchased using one purchasing profile, and other components may be purchased using one or more different purchasing profiles.
What is further clearly needed in a multi-profile system as known to the inventor, where a user can have multiple profiles, is a system and method for automatic rights management during booking for the various profiles. Furthermore, what is clearly needed is a system and method for transferring rights or whole personas between different domains of use.
A method for core identity with personas across multiple domains with permissions on profile data based on rights of domain, is described. In one embodiment, the method is to be implemented on a system. In one embodiment the method comprises receiving travel selections for a first leg of an itinerary; receiving a selection of a first profile to be assigned for the travel selections of the first leg, the first profile to be selected from a group of profiles corresponding to a user; receiving travel selections for a second leg of the itinerary; receiving a selection of a second profile to be assigned for the travel selections of the second leg, the second profile to be selected from the group of profiles corresponding to the user; automatically determining whether to replace the first profile for the first leg of the itinerary with a selection of a separate profile from the group of profiles, the determination made based on a predetermined criteria; and billing for the first and second legs of the itinerary as a single multi-leg travel itinerary, and billing the first leg of the itinerary to a profile assigned for the first leg and billing the second leg of the itinerary to a profile assigned for the second leg.
In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, functional, and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
If there are no more legs (no), the process moves to process 204, where the transaction is finalized (including payment terms, delivery if appropriate, corporate policy status and description, etc.), and then to process 205, where the process ends. If, however, the user wishes to book more legs of the transaction (yes), the process moves to process 206, where x is set at 2, so in process 207 the user may book leg Lx, where x=2, of the transaction.
The process then moves to process 208, where it again branches, with the same alternatives are process 203—that is, to finalize the transaction or to book more transaction legs. If the user again wishes to book more transactions (yes), the process moves to process 209, where x increments to x+1, and loops back to process 207, where the user again books leg Lx. This process continues until, in process 208, the user no longer wishes to book more legs of the transaction (no). The process then moves to process 204 and proceeds as described above.
In process 203, the process branches, depending on whether the user wishes to book more legs of the transaction. If there are no more legs (no), the process moves to process 304, where the transaction is finalized (see below for a more detailed description of the processes of process 304), and then to process 205, where the process ends. If, however, the user wishes to book more legs of the transaction (yes), the process moves to process 206, where x is set at 2, so in process 307 the user may book leg Lx, where x=2, of the transaction. In process 307, when the user selects the next leg Lx of the transaction, he also selects the preferred profile for this leg.
The process then moves to process 208, where it again branches, with the same alternatives are process 203—that is, to finalize the transaction or to book more transaction legs. If the user again wishes to book more transactions (yes), the process moves to process 209, where x increments to x+1, and loops back to process 307, where the user again books leg Lx and selects the preferred profile. This process continues until, in process 208, the user no longer wishes to book more legs of the transaction (no). The process then moves to process 304. In process 304, when the user finalizes the entire transaction, he then finalizes the details for each leg of the transaction by choosing a profile 1-n to use for that part.
Each profile contains information about payment mechanism, corporate policy applicability and terms, service preferences such as preferred rental car type (midsize, etc), loyalty program information (e.g. United frequent flyer program number), type of fare to book (first class, coach class unrestricted, etc) and other information. However, the entire transaction is booked as a whole, thus accruing to the user the savings of one multi-leg flight, for example, and the convenience of one set of reservations.
In this example, the rights shown allow use of the account in Profile 1402 for business and private travel and lodging, but for business only for rental cars. This last rights limitation may be, for example, due to insurance coverage available only for business usage, instead of for both business and personal use. Thus, to limit their potential liability, the company may decide not to extend personal use rights to rental cars.
Additional profiles may be used, for example, in cases where a consulting company is doing work for a client. In such an exemplary case, the client company may extend rights for travel expenses to the consulting personnel working for the client. In some cases, it may be more cost-effective for the consulting company to book travel arrangements for its personnel who are consulting with the client through the client corporation than to book its own travel arrangements and pass the costs on to the client. In some cases, the same flight may be booked through a different contract, which could result in lower prices. Or the same hotel, booked through the client's account, may cost less, due to the client's volume, compared to the consulting company's account. In other cases, certain functions or features may be less expensive or more readily available. In such cases, it may be necessary to override bookings under airline profile or credit card profile, etc. For example, if a traveler books a trip under his credit card, due to a promotion, it may be less expensive than booking it with the airline itself.
Price determinations may be accomplished by comparing pricing using various profiles, such as Profile 2403, Profile 3404, etc. In addition, in some cases the person's relationship with a supplier can be embodied through one or more of these profiles, allowing the user to accrue specific benefits as part of that relationship when using that profile to make purchases or reservations. For example, the user's business profile may contain his loyalty program account information which entitles him to a free upgrade on all rental cars when using this profile.
However, in other cases, the multi-part transactions may concern any of a great variety of services and products that are not necessarily limited to travel and transportation. In process 603, the process branches, depending on whether the user wishes to book more legs of the transaction.
If there are no more legs (no), the process moves to process 611, where the transaction is finalized as described below. If, however, the user wishes to book more legs of the transaction (yes), the process moves to process 606, where x is set at 2, so in process 307 the user may book leg Lx, where x=2, of the transaction. In process 607, when the user selects the next leg Lx of the transaction, he also selects the preferred profile for this leg.
The process then moves to process 608, where it again branches, with the same alternatives are process 603—that is, to finalize the transaction or to book more transaction legs. If the user again wishes to book more transactions (yes), the process moves to process 609, where x increments to x+1, and loops back to process 607, where the user again books leg Lx and selects the preferred profile. This process continues until, in process 608, the user no longer wishes to book more legs of the transaction (no).
The process then moves to process 611, where, when the booking entry is completed, the system goes back and selects available profiles and rights, if such profiles may be substituted for profiles the user selected, if they would result in a better cost, better quality, better service, or combinations thereof for the selected goods and services.
This process of price optimization may require a repetitive execution, because some bookings may affect other bookings. For example, an airline may have a promotion on certain hotel rooms, so by changing the airline through a certain account, a different hotel may need to be selected. In some cases, such changes may also require a reconfirmation with the user that these changes are acceptable to him; in other cases, these changes may be required by the company rules, for example, as a cost savings. Once the lowest bidders are found for each leg in process 612, a new package is assembled, and the booking is finalized in process 613, upon which the process ends in process 614.
It is clear that many modifications and variations of this invention may be made by one skilled in the art without departing from the spirit of the novel art of this disclosure. For example, a user may wish to include in his profiles a credit card for his college-age child, in which case the person in the profile would be, for example, Susan Doe, while the credit card and address details would be the same.
At least some embodiments, and the different structure and functional elements described herein, can be implemented using hardware, firmware, programs of instruction, or combinations of hardware, firmware, and programs of instructions.
In general, routines executed to implement the embodiments can be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations to execute elements involving the various aspects.
While some embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that various embodiments are capable of being distributed as a program product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others.
A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data can be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data can be stored in any one of these storage devices.
In general, a machine readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
Some aspects can be embodied, at least in part, in software. That is, the techniques can be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache, magnetic and optical disks, or a remote storage device. Further, the instructions can be downloaded into a computing device over a data network in a form of compiled and linked version.
Alternatively, the logic to perform the processes as discussed above could be implemented in additional computer and/or machine readable media, such as discrete hardware components as large-scale integrated circuits (LSI's), application-specific integrated circuits (ASIC's), or firmware such as electrically erasable programmable read-only memory (EEPROM's).
In various embodiments, hardwired circuitry can be used in combination with software instructions to implement the embodiments. Thus, the techniques are not limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
In this description, various functions and operations are described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize what is meant by such expressions is that the functions result from execution of the code by a processor, such as a microprocessor.
Although some of the drawings illustrate a number of operations in a particular order, operations which are not order dependent can be reordered and other operations can be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art and so do not present an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications can be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
4862357 | Ahlstrom et al. | Aug 1989 | A |
5513126 | Harkins et al. | Apr 1996 | A |
5832454 | Jafri et al. | Nov 1998 | A |
5892909 | Grasso et al. | Apr 1999 | A |
5966658 | Kennedy et al. | Oct 1999 | A |
5991735 | Gerace | Nov 1999 | A |
6009408 | Buchanan | Dec 1999 | A |
6091956 | Hollenberg | Jul 2000 | A |
6249252 | Dupray | Jun 2001 | B1 |
6253369 | Cloud et al. | Jun 2001 | B1 |
6292830 | Taylor et al. | Sep 2001 | B1 |
6317686 | Ran | Nov 2001 | B1 |
6336072 | Takayama et al. | Jan 2002 | B1 |
6374237 | Reese | Apr 2002 | B1 |
6397191 | Notaini et al. | May 2002 | B1 |
6591263 | Becker et al. | Jul 2003 | B1 |
6837427 | Overhultz et al. | Jan 2005 | B2 |
6847969 | Mathai et al. | Jan 2005 | B1 |
6853982 | Smith et al. | Feb 2005 | B2 |
6901424 | Wiinn | May 2005 | B1 |
6980993 | Horvitz et al. | Dec 2005 | B2 |
6993495 | Smith et al. | Jan 2006 | B2 |
6993554 | O'Donnell | Jan 2006 | B2 |
7013149 | Vetro et al. | Mar 2006 | B2 |
7013290 | Ananian | Mar 2006 | B2 |
7035811 | Gorenstein | Apr 2006 | B2 |
7072886 | Salmenkaita et al. | Jul 2006 | B2 |
7124024 | Adelaide et al. | Oct 2006 | B1 |
7139978 | Rojewski | Nov 2006 | B2 |
7194417 | Jones | Mar 2007 | B1 |
7280823 | Ternullo et al. | Oct 2007 | B2 |
7283970 | Cragun et al. | Oct 2007 | B2 |
7284002 | Doss et al. | Oct 2007 | B2 |
7289812 | Roberts et al. | Oct 2007 | B1 |
7296017 | Larcheveque et al. | Nov 2007 | B2 |
7305436 | Willis | Dec 2007 | B2 |
7330112 | Emigh et al. | Feb 2008 | B1 |
7330890 | Partovi et al. | Feb 2008 | B1 |
7346668 | Willis | Mar 2008 | B2 |
7370276 | Willis | May 2008 | B2 |
7376735 | Straut et al. | May 2008 | B2 |
7394900 | Gerber et al. | Jul 2008 | B1 |
7426537 | Lee et al. | Sep 2008 | B2 |
7430724 | Othmer | Sep 2008 | B2 |
7441203 | Othmer et al. | Oct 2008 | B2 |
7565615 | Ebert | Jul 2009 | B2 |
7634463 | Katragadda et al. | Dec 2009 | B1 |
7672881 | Steury et al. | Mar 2010 | B2 |
20010029425 | Myr | Oct 2001 | A1 |
20010034623 | Chung | Oct 2001 | A1 |
20020007327 | Steury et al. | Jan 2002 | A1 |
20020010604 | Block | Jan 2002 | A1 |
20020026356 | Bergh et al. | Feb 2002 | A1 |
20020049644 | Kargman | Apr 2002 | A1 |
20020072938 | Black et al. | Jun 2002 | A1 |
20020077871 | Udelhoven et al. | Jun 2002 | A1 |
20020099613 | Swart et al. | Jul 2002 | A1 |
20020116266 | Marshall | Aug 2002 | A1 |
20020143655 | Elston et al. | Oct 2002 | A1 |
20020161779 | Brieley | Oct 2002 | A1 |
20020178034 | Gardner et al. | Nov 2002 | A1 |
20030023499 | Das et al. | Jan 2003 | A1 |
20030028390 | Stern et al. | Feb 2003 | A1 |
20030033164 | Faltings et al. | Feb 2003 | A1 |
20030050964 | Debaty et al. | Mar 2003 | A1 |
20030065558 | Shaw et al. | Apr 2003 | A1 |
20030115093 | Lim et al. | Jun 2003 | A1 |
20030120530 | Casati et al. | Jun 2003 | A1 |
20030126095 | Allen | Jul 2003 | A1 |
20030135565 | Estrada | Jul 2003 | A1 |
20030187705 | Schiff et al. | Oct 2003 | A1 |
20030200146 | Levin et al. | Oct 2003 | A1 |
20030208754 | Sridhar et al. | Nov 2003 | A1 |
20030217332 | Smith et al. | Nov 2003 | A1 |
20030220835 | Barnes, Jr. | Nov 2003 | A1 |
20030229900 | Reisman | Dec 2003 | A1 |
20040002876 | Sommers et al. | Jan 2004 | A1 |
20040088107 | Seligmann | May 2004 | A1 |
20040117275 | Billera | Jun 2004 | A1 |
20040128156 | Beringer et al. | Jul 2004 | A1 |
20040128196 | Shibuno | Jul 2004 | A1 |
20040133463 | Benderev | Jul 2004 | A1 |
20040141003 | Nivers et al. | Jul 2004 | A1 |
20040193432 | Khalidi | Sep 2004 | A1 |
20040215517 | Chen et al. | Oct 2004 | A1 |
20040225540 | Waytena et al. | Nov 2004 | A1 |
20040236616 | Daughtrey | Nov 2004 | A1 |
20050010472 | Quatse et al. | Jan 2005 | A1 |
20050038869 | Zimler et al. | Feb 2005 | A1 |
20050043974 | Vassilev et al. | Feb 2005 | A1 |
20050071245 | Norins et al. | Mar 2005 | A1 |
20050138187 | Breiter et al. | Jun 2005 | A1 |
20050203884 | Allen et al. | Sep 2005 | A1 |
20050204276 | Hosea et al. | Sep 2005 | A1 |
20050209772 | Yoshikawa et al. | Sep 2005 | A1 |
20050227712 | Estevez et al. | Oct 2005 | A1 |
20050228876 | Malik | Oct 2005 | A1 |
20050273373 | Walker et al. | Dec 2005 | A1 |
20050288973 | Taylor et al. | Dec 2005 | A1 |
20060004511 | Yoshikawa et al. | Jan 2006 | A1 |
20060020496 | Azzarello et al. | Jan 2006 | A1 |
20060020565 | Rzevski et al. | Jan 2006 | A1 |
20060041477 | Zheng | Feb 2006 | A1 |
20060089194 | Joshi et al. | Apr 2006 | A1 |
20060111956 | Whitesage | May 2006 | A1 |
20060206412 | Van Luchene et al. | Sep 2006 | A1 |
20060235754 | Walker et al. | Oct 2006 | A1 |
20060247954 | Hunt | Nov 2006 | A1 |
20060259632 | Crawford et al. | Nov 2006 | A1 |
20060271552 | McChesnery et al. | Nov 2006 | A1 |
20070016514 | A-Abdulqader et al. | Jan 2007 | A1 |
20070071208 | Morris | Mar 2007 | A1 |
20070073706 | Ebie et al. | Mar 2007 | A1 |
20070143153 | Ashby et al. | Jun 2007 | A1 |
20070162301 | Sussman et al. | Jul 2007 | A1 |
20070162328 | Reich | Jul 2007 | A1 |
20070198937 | Paris | Aug 2007 | A1 |
20070276708 | Steury et al. | Nov 2007 | A1 |
20080046298 | Ben-Yehuda et al. | Feb 2008 | A1 |
20080287095 | Pousti | Nov 2008 | A1 |
20080301166 | Sugiyama et al. | Dec 2008 | A1 |
20090030609 | Orttung | Jan 2009 | A1 |
20090030742 | Orttung | Jan 2009 | A1 |
20090030769 | Orttung | Jan 2009 | A1 |
20090101710 | Chakravarthy | Apr 2009 | A1 |
20090167553 | Hong et al. | Jul 2009 | A1 |
Number | Date | Country |
---|---|---|
1622060 | Feb 2006 | EP |
Number | Date | Country | |
---|---|---|---|
20080004918 A1 | Jan 2008 | US |