INSTRUMENT-BASED TRIGGER EVENTS ARCHITECTURE
A method is disclosed herein in accordance with an embodiment of the present invention. The method may include deriving at a mobile transaction platform a multi-dimensional context from one or more user transactions and determining at least one life occurrence based, at least in part, on the multi-dimensional context. The one or more user transactions may be conducted through the mobile transaction platform. The one or more user transactions may be stored on a third-party source. In an aspect, the at least one life occurrence has yet to occur. In another aspect of the invention, the life occurrence has already occurred. The multi-dimensional context may include at least one of user location information and life occurrence location information. The multi-dimensional context may include at least one of a time of life occurrence and a current time.
1 . A non-transitory computer readable medium with an executable program stored thereon, wherein the program instructs a microprocessor to perform the following steps of an instrument-based method of potential life occurrence alert, comprising:
determining possible resolution actions to take in advance of a user's potential life occurrence based, at least in part, on a multidimensional context derived from analysis of the user's transactions performed with a mobile device via a mobile transaction platform server and third-party sourced data related to the user;
determining trigger-event context, based on metadata that describes aspects of the potential life occurrence, of trigger-event conditions for each resolution action;
monitoring trigger-event context;
when trigger-event conditions are met, presenting in an electronic display of the user's mobile device resolution actions that include life occurrence context that is relevant to the user making a decision about accepting the resolution action;
preparing a digital instrument to facilitate executing at least one of an action and a transaction for each of the presented resolution actions; and
adapting the digital instrument to include metadata that identifies a transaction type accessible by a server and user information required to use the digital instrument when a resolution action is accepted by the user.
3 . The computer readable medium of claim 1 , wherein the action is a mobile device action.
4 . The computer readable medium of claim 1 , wherein preparing the instrument comprises configuring the user's mobile device to access an ecosystem service provider, an electronic wallet on the user's mobile device, a secure element of the mobile device.
5 . The computer readable medium of claim 1 , wherein preparing the instrument comprises configuring the user's mobile device to follow user preferences for form of payment, receipt handling, and delivery/contact details to facilitate service delivery that effects the action/transaction without requiring user input for at least one of the presented resolution actions.
6 . The computer readable medium of claim 1 , wherein the life occurrence node is a mobile device.
7 . The computer readable medium of claim 1 , wherein the trigger-event context sources comprise at least one of a GPS, a clock, a calendar, an alert, an e-mail, a message, a call, and a bookmark.
8 . The computer readable medium of claim 1 , wherein the life occurrence container comprises at least one electronic wallet, resolution action, context monitor, trigger event detector, and an enabling layer.
9 . The computer readable medium of claim 1 , wherein the trigger-event context sources comprise a time, a location, and at least one of a transaction detail, an urgency, an importance, the status of a credit card or account, mobile device use history, payment source, wallet state, type of transaction, product/service, vendor, delivery method, delivery arrangements, tax status, transaction participant, user preferences, the presence of a network or a particular account, user associations with a non-vendor third-party, presence of vouchers and promotions, loyalty points, third-party user-related data, social network information, and calendar information.
10 . A method comprising:
determining possible resolution actions to take in advance of a user's potential life occurrence based, at least in part, on a multidimensional context derived from analysis of the user's transactions performed with a mobile device registered to the user via a mobile transaction platform server and third-party sourced data related to the user;
determining trigger-event context, based on metadata that describes aspects of the potential life occurrence, of trigger-event conditions for each resolution action;
monitoring trigger-event context;
when trigger-event conditions are met, presenting in an electronic display of the user's mobile device resolution actions that include life occurrence context that is relevant to the user making a decision about accepting the resolution action;
preparing a digital instrument to facilitate executing at least one of an action and a transaction for each of the presented resolution actions; and
adapting the digital instrument to include metadata that identifies a transaction type accessible by a server and user information required to use the digital instrument when a resolution action is accepted by the user.
11 . The method of claim 10 , wherein the action is a mobile device action.
12 . The method of claim 10 , wherein preparing the instrument comprises configuring the user's mobile device to access an ecosystem service provider, an electronic wallet on the user's mobile device, a secure element of the mobile device.
13 . The method of claim 10 , wherein preparing the instrument comprises configuring the user's mobile device to follow user preferences for form of payment, receipt handling, and delivery/contact details to facilitate service delivery that effects the action/transaction without requiring user input for at least one of the presented resolution actions.
14 . The method of claim 10 , wherein the life occurrence node is a mobile device.
15 . The method of claim 10 , wherein the trigger-event context sources comprise at least one of a GPS, a clock, a calendar, an alert, an e-mail, a message, a call, and a bookmark.
16 . The method of claim 10 , wherein the life occurrence container comprises at least one electronic wallet, resolution action, context monitor, trigger event detector, and an enabling layer.
17 . The method of claim 10 , wherein the trigger-event context sources comprise a time, a location, and at least one of a transaction detail, an urgency, an importance, the status of a credit card or account, mobile device use history, payment source, wallet state, type of transaction, product/service, vendor, delivery method, delivery arrangements, tax status, transaction participant, user preferences, the presence of a network or a particular account, user associations with a non-vendor third-party, presence of vouchers and promotions, loyalty points, third-party user-related data, social network information, and calendar information.