Portfolio system for coupling to a transaction system to maintain a shadow portfolio

Abstract

A portfolio system for coupling to one or more transaction systems to maintain a shadow portfolio and a method of maintaining a shadow portfolio are provided. The portfolio system includes an input module configured to receive one or more transaction records; a portfolio module coupled to the input module, the portfolio module configured to maintain a shadow portfolio, the portfolio module further configured to update the shadow portfolio with a portfolio value, the update based on reward information included in the one or more transaction records, and the portfolio value maintaining asset support for the shadow portfolio; and a supporter module coupled to the portfolio module, the supporter module configured to facilitate an increment of the portfolio value.

Description

Technical Field

[0001] The present disclosure relates broadly to a portfolio system for coupling to a trading system to maintain a shadow portfolio and to a method of maintaining a shadow portfolio for a trading system. Background Art

[0002] As advances in communications and internet technology have led to a growing global reach for sellers of goods and services, the number of e-commerce stores has been increasing, and the amount of digital marketing effort expended by these sellers / organizations has been rising. Consequently, organizations are investing resources, including financial resources, to acquire and retain new customers / clients while competing against competitors. Consequently, customer acquisition costs for e-commerce have been increasing.

[0003] One existing method of acquiring and retaining customers is through the provision of incentives and similar initiatives. One such initiative is typically the provision of a customer loyalty program / system. A customer loyalty program / system may include a reward / award system that provides rewards or prizes awarded or earned by users for spending on goods and / or services. It is recognized that the success of a reward program / system generally depends on the amount of rewards / awards (such as loyalty points) that a user / customer can accumulate, as well as the ease with which the user / customer can accumulate that amount of rewards / awards.

[0004] However, the inventor(s) have also recognized that organizations that implement such reward / award systems often set expiration dates for accumulated rewards / awards to avoid the significant risk of users / customers / members eventually accruing a significant number of rewards / awards over time. Such actions often result in decreased interest, engagement, loyalty, etc. among users / members of these reward / award systems. Over time, the cost of acquiring customers often increases.

[0005] In addition, the inventor(s) have recognized that, due to identified deficiencies in existing reward / award systems, it is difficult for existing reward / award systems to facilitate or establish communication or linkage with other systems, such as potential partners for rewards / awards. For example, such other systems may belong to merchants and other companies. For example, due to decreased interest, decreased engagement, decreased loyalty, etc. from users / members of these reward / award systems, potential partners may find it unattractive or easy to link with existing reward / award systems.

[0006] In view of the foregoing, there is a need for a portfolio system for coupling to a trading system to maintain a shadow portfolio and a method of maintaining a shadow portfolio for a trading system that seeks to address at least one of the above-mentioned problems. Summary of the Invention

[0007] According to one aspect of the present disclosure, a portfolio system for coupling to one or more trading systems to maintain a shadow portfolio is provided, the portfolio system comprising an input module configured to receive one or more trading records; a portfolio module coupled to the input module, the portfolio module configured to maintain the shadow portfolio, the portfolio module further configured to update the shadow portfolio with a portfolio value, the update being based on reward information included in the one or more trading records, wherein the portfolio value maintains asset backing for the shadow portfolio; and a backer module coupled to the portfolio module, the backer module configured to facilitate increments in the portfolio value.

[0008] The increments in the portfolio value may include positive or negative increments.

[0009] The portfolio module may be configured to update the shadow portfolio with the portfolio value based on a predetermined relationship rule between the reward value of the reward information and the asset value.

[0010] If the increase in portfolio value is a positive increase, the portfolio module may be configured to extract an amount of asset backing to increase the asset backing, the extraction being made to the portfolio module via the backer module.

[0011] If the increment in portfolio value is a negative increment, the portfolio module may be configured to withdraw an amount of the asset backing to reduce the asset backing, the withdrawal being made from the portfolio module via the backer module.

[0012] A shadow portfolio can be associated with one or more trading systems.

[0013] A shadow portfolio can be associated with one or more users of the trading system.

[0014] The input module may also be configured to receive interest information indicating a calculated interest yield, and upon receiving the interest information, the portfolio module may be configured to update the portfolio value with the calculated interest yield, wherein updating the portfolio value with the calculated interest yield may include extracting interest on the interest amount of the asset backing to increase the asset backing, the interest extraction being performed on the portfolio module via the backer module.

[0015] The portfolio module may be configured to utilize assets to back transfers to one or more merchants, the transfers being based on one or more transaction records.

[0016] The portfolio module may be configured to utilize asset backing to perform currency conversions based on one or more transaction records.

[0017] The backer module may be configured to receive an injection of assets and the backer module may be further configured to generate a corresponding injected reward value based on the injection of assets, and wherein the input module may be further configured to transmit the injected reward value for use external to the portfolio system.

[0018] The portfolio module may also be configured to update the shadow portfolio with a portfolio value, the update being based on reward information associated with the injected reward value, the reward information being included in the one or more transaction records, and the portfolio value may maintain asset backing for the shadow portfolio by increasing the asset backing as assets are injected.

[0019] According to another aspect of the present disclosure, a method for maintaining a shadow portfolio is provided, the method comprising: providing a portfolio module to maintain the shadow portfolio; providing a backer module; receiving one or more transaction records from one or more transaction systems; updating the shadow portfolio with a portfolio value, the update being based on reward information included in the one or more transaction records; using the backer module to facilitate increments in the portfolio value; and maintaining asset backing for the shadow portfolio with the portfolio value.

[0020] The increments in the portfolio value may include positive or negative increments.

[0021] The step of updating the shadow portfolio with the portfolio value may also be based on a predetermined relationship rule between the reward value of the reward information and the asset value.

[0022] If the increment in portfolio value is a positive increment, then updating the shadow portfolio with the portfolio value may include withdrawing an amount of asset backing to increase the asset backing, the withdrawal being performed via the backer module to the portfolio module.

[0023] If the increment in portfolio value is a negative increment, then updating the shadow portfolio with the portfolio value may include withdrawing an amount of asset backing to reduce the asset backing, the withdrawal being made from the portfolio module via the backer module.

[0024] The method may further include associating the shadow portfolio with one or more trading systems.

[0025] The method may also include associating the shadow portfolio with one or more users of the trading system.

[0026] The method may further include receiving interest information indicating a calculated interest yield; and the step of updating the shadow portfolio with the portfolio value may include extracting interest on the interest amount of the asset backing to increase the asset backing, the interest extraction being performed on the portfolio module via the backer module.

[0027] The method may also include utilizing the asset backing to transfer to one or more merchants, the transfer being based on the one or more transaction records.

[0028] The method may also include performing a currency conversion using the asset backing, the currency conversion being based on the one or more transaction records.

[0029] The method may also include: receiving an injection of assets via the backer module; generating a corresponding injected reward value based on the injection of assets; and transmitting the injected reward value for use at one or more transaction systems.

[0030] The method may further include receiving reward information associated with the injected reward value, the reward information included in the one or more transaction records; and increasing asset support based on the injection of assets.

[0031] According to another aspect of the present disclosure, a non-transitory tangible computer-readable storage medium having software instructions stored thereon is provided, which, when executed by a computer processor of an investment portfolio system to maintain a shadow investment portfolio, causes the computer processor to perform a method of maintaining a shadow investment portfolio by performing the following steps, the steps comprising: providing a portfolio module to maintain the shadow investment portfolio; providing a backer module; receiving one or more transaction records from one or more trading systems; updating the shadow investment portfolio with a portfolio value, the update being based on reward information included in the one or more transaction records; facilitating an increase in the portfolio value using the backer module; and maintaining asset backing for the shadow investment portfolio with the portfolio value. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Exemplary embodiments of the present invention will be better understood and will become apparent to those skilled in the art from the following written description, given by way of example only, taken in conjunction with the accompanying drawings, in which:

[0033] Figure 1 is a schematic diagram of a portfolio system that maintains a shadow portfolio in an exemplary embodiment.

[0034] Figure 2 is a schematic diagram of a system framework for maintaining a shadow investment portfolio in another exemplary embodiment.

[0035] Figure 3 is a schematic flow chart illustrating a method of maintaining a shadow portfolio in an exemplary embodiment.

[0036] Figure 4A is a schematic block diagram illustrating an example supporter module in an exemplary embodiment.

[0037] Figure 4Bis a schematic block diagram illustrating an example supporter module in another example embodiment.

[0038] Figure 5 is a schematic diagram of a system framework for maintaining a shadow investment portfolio in another exemplary embodiment.

[0039] Figure 6 is a schematic diagram of a computer system suitable for implementing the exemplary embodiments. DETAILED DESCRIPTION

[0040] Example embodiments described herein may provide a portfolio system for coupling to one or more trading systems to maintain a shadow portfolio and a method of maintaining a shadow portfolio for a trading system.

[0041] In an exemplary embodiment, a portfolio system may be provided for coupling to one or more trading systems to maintain a shadow portfolio. The portfolio system includes an input module configured to receive one or more transaction records. The transaction records may be transmitted from the coupled trading system. The portfolio system also includes a portfolio module coupled to the input module. The portfolio module is configured to maintain the shadow portfolio. The portfolio module is further configured to update the shadow portfolio with a portfolio value. The portfolio value is updated using reward information included in the one or more transaction records. The reward information may include a reward value that notifies the portfolio module to increase or decrease the portfolio value. The portfolio value maintains the asset backing for the shadow portfolio. This asset backing may include monetary assets, cash reserves, or any material with equivalent monetary value. For example, as the portfolio value increases, the monetary assets or cash reserves may increase as the asset backing for the shadow portfolio increases. For example, as the portfolio value decreases, the monetary assets or cash reserves may decrease / withdraw as the asset backing for the shadow portfolio decreases. In an exemplary embodiment, the portfolio system also includes a backer module coupled to the portfolio module. The backer module is configured to facilitate the increase in portfolio value. For example, the backer module may be an interface between the portfolio system and a financial entity system. The backer module may allow for the inflow and outflow of assets, asset backing (such as monetary assets).

[0042] In an exemplary embodiment, a shadow portfolio can be associated with a corresponding trading system. Additionally or alternatively, a shadow portfolio can be associated with a corresponding user of the coupled trading system. In such a case, the shadow portfolio or the corresponding portfolio value can be considered a designated account of the trading system and / or user.

[0043] In an exemplary embodiment, the portfolio module can utilize asset-backed transfers to one or more merchants based on reward information. For example, if a user redeems a certain number of reward points for goods and / or services within the transaction system, the asset-backed transfer can be used to pay the merchant of the goods and / or services via the portfolio system. This payment can be based on reward information included in the transaction record and sent to the portfolio system.

[0044] In an exemplary embodiment, the portfolio module can utilize asset backing to perform currency conversions based on reward information. For example, if a user redeems a certain amount of reward points for cash in a transaction system, the asset backing can be used for cash conversion via the portfolio system. This conversion can be based on reward information included in the transaction record and sent to the portfolio system.

[0045] Figure 1 FIG2 is a schematic diagram of an exemplary embodiment of a portfolio system for maintaining a shadow portfolio. The portfolio system 100 can be coupled to one or more trading systems. Such coupling can be via any wired and / or wireless connection.

[0046] In the exemplary embodiment, the portfolio system 100 includes an input module 102. In the exemplary embodiment, the input module 102 is configured to receive one or more trade records from a trading system (not shown).

[0047] In an exemplary embodiment, the portfolio system 100 also includes a portfolio module 104 coupled to the input module 102. In an exemplary embodiment, the portfolio system 100 also includes a backer module 106 coupled to the portfolio module 104. In some exemplary embodiments, the components of the portfolio system 100 may be coupled to a processing module that may direct and control the operation of the portfolio system 100.

[0048] In an exemplary embodiment, portfolio module 104 is configured to maintain a shadow portfolio and update the shadow portfolio with a portfolio value. Thus, portfolio module 104 is configured to update the portfolio value. The portfolio value may be, for example, a value indicating or related to the amount of monetary assets available to a coupled trading system. Thus, the portfolio value maintains the asset backing of the shadow portfolio. Portfolio module 104 is configured to update the portfolio value based on one or more transaction records received by input module 102.

[0049] In an exemplary embodiment, the backer module 106 is configured to facilitate the increase in portfolio value. The backer module 106 may serve as an interface between the portfolio system 100 and a financial institution. That is, the portfolio system 100 may also be connected to or coupled to a financial institution system, such as a bank. This connection may be facilitated via a wired or wireless connection, or a combination of both types of connections. In an exemplary embodiment, the backer module 106 may be coupled to databases, accounts, and / or deposit components, etc., that are linked to a financial institution, such as a banking entity.

[0050] In some exemplary embodiments, the backer module 106 may also store and update a backer value. For example, the backer value may be a value indicating the amount of monetary assets available to a backer (e.g., total cash reserves) or a value related to the amount of monetary assets (e.g., total cash value). The backer value may also include the planned outflow of monetary assets (e.g., assets stored in a first buffer of the backer module 106) from the portfolio module 104, which serves as a holding platform for scheduled payments to, for example, one or more merchants.

[0051] In an exemplary embodiment, each transaction record is based on a reward / award process. For example, the transaction system can implement a reward / award process based on, for example, the consumption and / or expenditure (i.e., transactions) of goods and / or services of one or more users / members of the transaction system. In an exemplary embodiment, each transaction record can include reward / award information indicating a positive or negative increment of the reward / award value. This reward value can be any form of reward or award based on one or more transactions that have been executed at the transaction system. Some forms can include, but are not limited to, reward points, loyalty points, coupons, etc. The reward value can be determined based on the value of one or more transactions that have been executed at the transaction system, for example.

[0052] In an exemplary embodiment, the portfolio module 104 is configured to update the portfolio value based on the reward information for each transaction record.

[0053] In use, input module 102 receives transaction records from a coupled trading system. Input module 102 transmits the transaction records to portfolio module 104. Portfolio module 104 processes the transaction records to determine a positive or negative increment in reward value. If there is a positive increment (or increase) in reward value, portfolio module 104 increases the portfolio value associated with the trading system. Portfolio module 104 determines the portfolio value based on predetermined relationship rules. In this exemplary embodiment, the increase in portfolio value is based on withdrawing the amount of monetary assets indicated by portfolio module 104 from a financial institution via backer module 106 to portfolio module 104. In some other exemplary embodiments, this withdrawal results in a decrease in the backer value (i.e., the total cash reserves from backers) stored in backer module 106.

[0054] On the other hand, if there is a negative increase (or decrease) in reward value, the portfolio module 104 decreases the portfolio value associated with the trading system. In an exemplary embodiment, the decrease in portfolio value is based on the withdrawal of an amount of monetary assets indicated by the portfolio module 104 from the portfolio module 104 via the backer module 106. In some other exemplary embodiments, such withdrawals via the backer module 106 may result in an increase in the backer value stored in the backer module 106, for example, as an amount paid to one or more merchants. In such exemplary embodiments, the backer module 106 increases or decreases the backer value based on the corresponding withdrawal of a certain amount of monetary assets from the portfolio module 104 or the withdrawal of a certain amount of monetary assets to the portfolio module 104 via the backer module 106. In an exemplary embodiment, the portfolio value thus maintains the asset backing of the shadow portfolio of the trading system based on the monetary assets. In an exemplary embodiment, the input module 102 receives the transaction record once. This time may be, for example, but not limited to, a periodic interval, real-time, a system-prompted activation time, or a user-prompted activation time.

[0055] Therefore, in an exemplary embodiment, the reward value of the trading system is backed by a monetary value. Therefore, the trading system has an associated shadow portfolio that shadows / tracks the reward value of the trading system. In an exemplary embodiment, the portfolio value is associated with the trading system as a whole.

[0056] In certain example embodiments, the portfolio value may be subject to earning interest and thus may increase over time due to interest income. Additionally, in certain other example embodiments, the backer value may be subject to reduction due to external reimbursements, for example, as payment to one or more merchants for providing goods and / or services associated with use of the trading system.

[0057] In some exemplary embodiments, an audit module may be added to the portfolio system 100 such that one or more audit processes may be performed on the portfolio module 104 and / or the portfolio value to detect any anomalies in the operation of the portfolio module.

[0058] In some exemplary embodiments, the investment portfolio system 100 may be connected to or coupled to more than one trading system. Each trading system may be configured to generate one or more trade records based on one or more trades executed at the respective trading system and transmit the trade records to the input module 102 of the system 100.

[0059] In such exemplary embodiments, each transaction record may additionally include transaction system information. The transaction system information may include an identifier for identifying the respective transaction system from which each transaction record was generated and transmitted. As an example, such an identifier may be tagged / attached / encrypted to the reward information.

[0060] In such exemplary embodiments, the different respective portfolio values ​​may be stored in the portfolio system 100, e.g., in a portfolio database included in the portfolio module 104. Thus, each trading system may be matched with its respective portfolio value and, therefore, with a respective shadow portfolio.

[0061] Figure 2 FIG. 1 is a diagram of a system framework for maintaining a shadow portfolio in another exemplary embodiment. In this exemplary embodiment, the system framework provides a portfolio system 200, which has the same functions as referenced Figure 1 The described portfolio system 100 is substantially similar. For ease of reference, similar reference numbers and / or naming conventions are used for exemplary embodiments of similar modules, such as in Figure 1 and Figure 2 Described in .

[0062] In the exemplary embodiment, portfolio system 200 is coupled to transaction system 202 and merchant system 204 .

[0063] In some exemplary embodiments, the portfolio system 200, the transaction system 202, and the merchant system 204 may each include a processing module configured to execute a reference Figure 2 Describe the steps.

[0064] In an exemplary embodiment, transaction system 202 can facilitate transactions. By way of example only, transaction system 202 can facilitate the purchase of product A (see number 206A), product B (see number 206B), and product C (see number 206C). Transaction system 202 is configured to implement a reward / award process. Based on the expenditures / consumption of the three transactions 206A, 206B, and 206C, transaction system 202 can calculate an amount of reward points as a reward value. Such reward points can be referred to as member points, e.g., rewards / awards for one or more users / members who participate in the reward / award process of transaction system 202. See reference numeral 208. In this case, there is a positive increment (or increase) in the reward value.

[0065] In an exemplary embodiment, the transaction system 202 may be configured to update (or increase) the accumulated / statistical amount of member points. See reference numeral 210. In some exemplary embodiments, the statistics of member points may be stored in a user / member database included in the transaction system 202. The statistics of member points may be separated into the corresponding individual member accounts maintained at the transaction system 202.

[0066] In an exemplary embodiment, at a first time, transaction system 202 is configured to generate a transaction record that includes reward information indicating a positive increment or a negative increment in the reward value.

[0067] In some exemplary embodiments, transaction system 202 may be configured to also include in the transaction record an identifier for identifying the transaction system from which the transaction record was generated. In some exemplary embodiments, the transaction record may also include user information (e.g., information identifying each user / member in the transaction record associated with the reward value of the transaction record). In such exemplary embodiments, by way of example only, the user information may be tagged / appended / encrypted to the reward information.

[0068] In an exemplary embodiment, trading system 202 may be configured to transmit the trade records to portfolio system 200 after generating the trade records.

[0069] In an exemplary embodiment, the portfolio system 200 may include an input module, a portfolio module, and a backer module. Figure 1 The portfolio system 100 includes an input module 102 , a portfolio module 104 , and a backer module 106 .

[0070] In an exemplary embodiment, the portfolio system 200 may be further coupled to a financial institution, such as a banking entity, via a backer module. In an exemplary embodiment, the input module of the portfolio system 200 is configured to receive one or more transaction records transmitted by the transaction system 202 .

[0071] After receiving a transaction record including a positive increment of the reward value, the portfolio module is configured to calculate the amount of monetary assets corresponding to the positive increment (i.e., increase) of the reward value indicated in the received transaction record based on a predetermined relationship rule. Figure 1 The portfolio module 104 is configured to indicate the calculated amount of monetary assets via the backer module and withdraw them to the portfolio module. The withdrawn amount of monetary assets is used to update the portfolio value associated with the trading system 202, i.e., to increase the portfolio value. This can be considered or referred to as a replenishment 218 of the currency or cash reserve as a replenishment of the assets or monetary backing of the shadow portfolio of the trading system 202. See reference numeral 218.

[0072] In an exemplary embodiment, the portfolio system 200 is configured to update (increase and / or decrease, respectively) the portfolio value stored in the portfolio module based on any withdrawal and / or withdrawal of monetary assets from the portfolio module as directed by the portfolio module via the backer module. Thus, this can be viewed or referred to as an update 220 of the currency or cash reserve that serves as the asset backing the shadow portfolio of the trading system 202. See reference numeral 220.

[0073] Thus, the portfolio value maintains the asset backing of the shadow portfolio.Thus, the backer module is configured to facilitate an increase (either positive or negative) in the portfolio value.

[0074] In an exemplary embodiment, one or more members participating in the rewards / award process of trading system 202 may be allowed to use their respective membership points. For example, at a second time (or at any time independent of the operation of portfolio system 200), trading system 202 may be configured to prompt and inquire of the member / user as to whether the user wishes to claim (or redeem or use) any amount of the user's accumulated membership points. For example, at a second time (or at any time independent of the operation of portfolio system 200), the member / user voluntarily decides or wishes to claim (or redeem or use) any amount of the user's accumulated membership points. See reference numeral 212. In some exemplary embodiments, trading system 202 may be provided with an input module / device, such as, but not limited to, a touch-sensitive screen, configured to receive such user input.

[0075] In an exemplary embodiment, if the user input indicates that the user does not wish to claim any of the user's loyalty points, then the transaction system 202 may take no further action.

[0076] In an exemplary embodiment, if the user input indicates that the user wishes to claim some or all of the user's accumulated loyalty points, the transaction system 202 may select from a set of predetermined units of loyalty points for claiming (e.g., 5 points, 10 points, 20 points, etc.). Alternatively or additionally, the user may be allowed to provide user input regarding the desired amount of loyalty points to claim.

[0077] In an exemplary embodiment, after the claim (or redemption or use) of the member points is settled, the transaction system 202 is configured to update (or reduce) the accumulated / statistical amount of the member points (see reference numeral 216 ).

[0078] In the exemplary embodiment, at a third time (or any time independent of the operation of the portfolio system 200 ), the trading system 202 is configured to generate a transaction record including reward information indicating a negative increment in the reward value. The transaction record is transmitted to the portfolio system 200 .

[0079] At the portfolio system 200, upon receiving a transaction record including a negative increment in the reward value, the portfolio module is configured to calculate, based on predetermined relationship rules, the amount of monetary assets corresponding to the negative increment (i.e., decrease) in the reward value indicated in the received transaction record. The portfolio system 200 (or the portfolio module) is configured to withdraw the calculated amount of monetary assets indicated by the portfolio module from the portfolio module via the backer module. This can be viewed or referred to as a withdrawal 224 of currency or cash reserves as a withdrawal of assets or currency backing to the shadow portfolio of the trading system 202. See reference numeral 224. In an exemplary embodiment, withdrawals such as those described above result in an update to the portfolio value, and thus to the asset backing. See also the description associated with reference numeral 220.

[0080] In an exemplary embodiment, a user can claim, redeem, or use the user's accumulated reward points, for example, to redeem products (items, vouchers, etc.) and / or services from merchant(s). In an exemplary embodiment, portfolio system 200, when coupled to merchant system 204, can be configured to receive a transaction record that includes information indicating a negative increment in reward value and also includes claim information and destination information. For example, the claim information and destination information can be tagged / appended / encrypted to the reward information. The claim information can indicate whether transaction system 202 is to withdraw 224 an asset backing, such as currency / cash reserves, and the destination information (e.g., a merchant's destination bank account details) can indicate the destination(s) to which the asset backing (e.g., monetary assets) will be transferred in order to execute the redemption from the merchant(s). In an exemplary embodiment, upon receiving a transaction record including request information and destination information, portfolio system 200 is configured to withdraw the calculated asset value from a designated bank account of trading system 202, i.e., withdraw from the asset backing, such as currency / cash reserves of trading system 202 (see reference numeral 224), transfer the calculated asset value to a designated destination (e.g., a bank account of a merchant(s)), and settle payment to the merchant(s) (see reference numeral 226). For example, the withdrawal is directed by the portfolio module and facilitated via the backer module. In such cases, the shadow portfolio of trading system 202 is considered or referred to as the designated bank account of trading system 202.

[0081] In an exemplary embodiment, currency / cash reserves (or portfolio value) can earn interest. For example, the input module of the portfolio system 200 can periodically (monthly, annually, etc.) receive interest information from the financial entity / system to which the portfolio system 200 is coupled. The interest information can indicate an interest yield. See reference numeral 222. The interest yield can be calculated based on the amount of monetary assets available in each portfolio or the portfolio value stored in the portfolio module. Any suitable interest rate can be used for this purpose.

[0082] In an exemplary embodiment, based on the interest income calculated in the interest information, the financial entity / system may deposit the calculated interest income into the investment portfolio of the trading system 202 , ie, to replenish 218 the cash reserve.

[0083] In an exemplary embodiment, based on the cash reserve replenishment 218, the portfolio system 200 and the portfolio module may be configured to update 220 (or increase) the portfolio value of the trading system 202. See reference numeral 220.

[0084] In an exemplary embodiment, a reward system may be provided that is backed by assets (e.g., currency / cash reserves) in, for example, a separate designated bank account (or shadow portfolio). For example, if it is predetermined that each (1) reward point corresponds to a monetary value of $0.10, then for each increment of 100 reward points detected (i.e., based on transactions from a trading system recorded in the portfolio module), the portfolio module of the portfolio system may be configured to direct a deposit of $10.00 into the portfolio value associated with the relevant trading system. The withdrawal of such an amount may be directed by the portfolio module and via the backer module of the portfolio system, which in turn is associated with a bank account of the backer (e.g., the entity operating the portfolio system). Thus, the shadow portfolio and its portfolio value may be considered a designated bank account of the trading system. Thus, a shadow portfolio is provided that tracks / projects the value of rewards (whether increasing or decreasing) from the trading system.

[0085] In an exemplary embodiment, the asset backing (e.g., currency / cash reserves) in the designated bank account of the trading system cannot be withdrawn unless, for example, a member / user of the trading system instructs to use the member's accumulated reward points, such as to redeem or consume products and / or services, or even requests a cash conversion (from reward points). In other words, the asset backing (e.g., currency / cash reserves) can only be used to pay cash to fulfillment center suppliers / vendors and / or members / users.

[0086] In some exemplary embodiments, the amount of assets (eg, currency / cash reserves) in a designated bank account may be periodically audited to provide confidence and transparency.

[0087] In some exemplary embodiments, the data stored in the portfolio module (compare Figure 1 Each portfolio value in the portfolio module 104 of the portfolio system can indicate the total amount of asset support (e.g., currency / cash support) available for each trading system to which the portfolio system is connected / coupled. In such exemplary embodiments, asset support is associated with each trading system. Therefore, in these exemplary embodiments, accounting for asset support (e.g., currency / cash support) associated with each user / member of each trading system is performed within each trading system.

[0088] In some other exemplary embodiments, the portfolio value may also indicate the total amount of asset backing available to each user / member. That is, the accounting of asset backing (e.g., currency / cash backing) associated with each member of the trading system(s) coupled to the portfolio system is instead performed at the portfolio system.

[0089] In such exemplary embodiments, via the input module (compare Figure 1Input module 102) is transmitted to the portfolio system (comparison Figure 1 Transaction records of the investment portfolio system 100 may additionally include user information. The user information is used to identify each user (e.g., using a unique serial ID assigned to each user). As an example, the user information may be tagged / attached / encrypted to the reward information. In such exemplary embodiments, the investment portfolio module of the investment portfolio system may be configured to extract the user information from each received transaction record.

[0090] In such exemplary embodiments, the portfolio module is configured to update the respective portfolio values ​​(e.g., each individual shadow account / portfolio) belonging to the respective user / member. Thus, a portfolio database may be provided at the portfolio module to store different portfolio values ​​associated with different users / members. Thus, in such exemplary embodiments, the updating of the portfolio values ​​is substantially similar to other exemplary embodiments, i.e., based on increments or decrements and based on each received transaction record (and further based on user information to identify the respective shadow portfolio and / or portfolio value).

[0091] Thus, an exemplary embodiment can be provided that operates a shadow portfolio associated with a user / member rather than the entire trading system. Aspects such as exchange, interest income, etc. can also be applied to the individual portfolio values ​​of different users / members.

[0092] In the exemplary embodiments described herein, by providing a portfolio system as described for coupling to one or more trading systems, such a portfolio system can provide technical scalability to work with existing trading systems. For example, the portfolio system can be coupled to one or more trading systems as needed, and additional couplings can be added to more trading systems as the portfolio system-trading system ecosystem grows to a larger scale. Furthermore, in the exemplary embodiments described herein, the described portfolio system can provide increased reliability and integrity because a shadow portfolio with a portfolio value is provided, and this portfolio value is used to maintain real and reliable asset backing for the shadow portfolio. With asset backing known to the coupled trading system or systems and / or one or more users of the trading system or systems, coupling with such a portfolio system can be relatively more trustworthy.

[0093] In the described exemplary embodiment, the portfolio module may be configured to update the portfolio value based on predetermined relationship rules between reward information (in received transaction records) and asset value. Asset value may refer to a value associated with or indicative of an amount of a monetary asset.

[0094] In a preferred embodiment, the asset value may be a value proportional to the reward value indicated in the reward information of the transaction record. For example, the predetermined relationship rule may be a ratio for updating the portfolio value based on the increment or decrement of X reward points to a value $Y (asset value) indicated in the reward information. The ratio of X:Y (reward value:asset value) may be, for example, 100:1, 1:1, or 1:5. It will be appreciated that exemplary embodiments are not limited to the above ratios and other ratios may be used.

[0095] In an exemplary embodiment, if there is a positive increment in the reward value, the portfolio module is configured to increase the portfolio value by a value (asset value) proportional to the positive increment. For example, for each positive increment of X reward points, the portfolio module is configured to increase the portfolio value by $Y according to a predetermined ratio.

[0096] In some exemplary embodiments, for accounting purposes of the backer's total cash reserves, the backer value stored in the backer module decreases correspondingly with increases in the portfolio value as monetary assets are withdrawn via the backer module into the portfolio module for the shadow portfolio.

[0097] Conversely, if there is a negative increment (or decrease) in the reward value, the portfolio value is reduced accordingly using this ratio. For example, for each negative increment of X reward points, the portfolio module is configured to reduce the portfolio value by $Y according to a predetermined ratio.

[0098] In some exemplary embodiments, for accounting purposes of payments to one or more merchants, e.g., for goods and / or services redeemed / consumed at a transaction system, the backer value stored in the backer module increases correspondingly with decreases in the portfolio value due to withdrawal of monetary assets from the portfolio module (from the shadow portfolio) via or toward the backer module.

[0099] In the exemplary embodiments described above, it is recognized that each portfolio or each portfolio value can therefore usefully reflect the transaction records of each trading system and / or each user / member of one or more trading systems. Accordingly, a corresponding shadow portfolio is provided that tracks the transaction records (and corresponding reward values) and thereby maintains asset support, such as currency / cash support, for the trading system(s) and / or user(s).

[0100] In the described exemplary embodiment, a portfolio system is provided in which each reward point (or more broadly, reward value) awarded to a member / user can be effectively backed by an equal or corresponding / proportional amount of assets (e.g., monetary assets or cash) held in a designated cash reserve account (or shadow portfolio) associated with the trading system in which the member / user participates. In the described exemplary embodiment, the amount in the designated bank account may not belong to the entity / organization operating the trading system, but rather be an asset backing for all members (or reward point owners) separately. The asset backing (e.g., currency / cash reserve) can be held in trust and audited from time to time to achieve a relatively high level of transparency. In addition, any interest that may be generated by the assets (e.g., cash reserves in the designated bank account) can also be reinvested / deposited into the designated bank account (or shadow portfolio). The inventor(s) have recognized that this can create the potential for generating more value for the reward points accumulated by members.

[0101] In the described exemplary embodiments, by providing a reward system backed by assets (e.g., currency / cash reserves), an entity / organization can no longer worry about members (or users) of the entity's trading system accumulating too many reward points. For example, if the trading system is combined with a referral program (e.g., providing members with additional reward value or points when they successfully introduce new users / members to the trading system), members can accumulate reward points more quickly with the additional assurance that the reward points they accumulate are backed by assets (e.g., monetary assets / cash) and are valid (e.g., do not expire). Members can even redeem accumulated points for cash at any time. This can incentivize members to refer more new members, thereby potentially and usefully reducing the cost of customer acquisition for the entity / organization using the trading system.

[0102] In the exemplary embodiment described, the portfolio system can be licensed to various entities / companies to improve their respective customer loyalty programs and ultimately reduce their overall marketing costs. Alternatively or additionally, the portfolio system can even be used to manage such company's loyalty program. Any company / entity / organization that wishes to improve its customer loyalty program(s) can become a target licensee.

[0103] The inventor(s) have recognized that the cost of acquiring new members / users / customers can be five times the cost of retaining current members / users / customers. The inventor(s) have therefore recognized that by having a successful customer loyalty program (i.e., implemented using the portfolio system of the exemplary embodiments), an entity / organization (of a trading system) may be able to save on customer acquisition costs. Based on the described exemplary embodiments, because the reward value or points are backed by assets (e.g., currency / cash reserves), more possibilities become available in terms of how the reward points can be used. By way of example only, an entity or company may allow members to use reward points to purchase stock options before the company's initial public offering (IPO) as an incentive to create more customer loyalty.

[0104] In the exemplary embodiments described, the investment portfolio system may additionally incorporate blockchain technology to increase the reliability and transparency of the system. For example, when blockchain technology is incorporated into the investment portfolio system, the portfolio modules and portfolio values ​​of the investment portfolio system may be used to serve as the ledgers of the investment portfolio system.

[0105] Through various exemplary embodiments, the portfolio system can provide economic benefits to an entity / company by providing a means to at least reduce customer acquisition costs. Since the entity / company utilizes or integrates the portfolio system with one or more existing trading systems, this can also facilitate or establish communication or links with existing systems belonging to new potential partners so that members can obtain rewards / incentives. Such new potential partners may be more willing to collaborate with the entity / company because users / members of the trading system may be more interested in participating in the trading system due to the asset backing provided for the reward value or reward points. New potential partners may include merchants, fulfillment center providers, and other companies.

[0106] In various exemplary embodiments, the issue raised by an entity / company regarding imposing an expiration date on member reward value or points, for example, for reasons such as cash flow protection, when a member's accumulated reward points become excessive and could expose the entity / company to a large current liability, can be alleviated. That is, because the reward points are backed by assets (e.g., monetary assets or cash reserves), the entity / company can guarantee cash flow and thus may no longer deem it necessary to impose an expiration date on the member reward value or points.

[0107] Through various exemplary embodiments, the portfolio system can also reduce the likelihood that an entity / organization will arbitrarily reduce the number of reward points that can be earned and / or increase the number of reward points required to redeem / consume goods and / or services. Such actions could otherwise be considered unfair to consumers / members / users because such actions would devalue the reward points accumulated by members over time and for loyalty members. In other words, because reward points are backed by assets (e.g., monetary assets or cash reserves), the entity / company can guarantee cash flow and, therefore, may no longer be deemed to need to arbitrarily reduce the number of reward points and / or increase the number of reward points required to redeem / consume goods and / or services.

[0108] Figure 5 FIG. 1 is a schematic diagram of a system framework for maintaining a shadow portfolio in another exemplary embodiment. In this exemplary embodiment, the system framework provides a Figure 2 The described portfolio system 200 functions substantially similarly to the portfolio system 500. For ease of reference, similar numbers and / or naming conventions are used for exemplary embodiments of similar modules, such as in Figure 1 、 Figure 2 and Figure 5 Described in .

[0109] In an exemplary embodiment, assets can be injected into the portfolio system 500. In an exemplary embodiment, injected reward value can be generated corresponding to the injection of assets and can be used, for example, for awarding / distribution outside of the portfolio system 500 (or, for example, for sale). For example, by injecting assets into the portfolio system 500, injected reward value (e.g., a corresponding amount of injected / floating membership or reward points) can be generated and, for example, awarded / distributed (or, for example, for sale) on one or more coupled trading systems. The injected assets are included in the portfolio system 500. In this example, after the sale or award of floating reward points, the coupled trading system(s) can transmit one or more transaction records, which include reward information associated with the sale or award of the injected reward points, i.e., reward information associated with the injected reward value. The portfolio module updates the shadow portfolio with the portfolio value, which is based on the reward information associated with the sale or award of the floating reward points. The portfolio value maintains the asset backing for the shadow portfolio, which is based on the injected assets transmitted to the portfolio module. Thus, in this exemplary embodiment, assets (e.g., monetary assets) are already injected / contained in the portfolio system 500 and are used to increase asset backing when reward information associated with injected reward value is received, for example, when transaction record(s) indicate that corresponding injected reward points have been awarded or sold, for example.

[0110] In an exemplary embodiment, portfolio system 500 may include a backer module, which is further configured to allow assets to be injected 502 into the portfolio module via the backer module. The injection 502 of assets may be performed at a fourth time (or at any time independent of the operation of portfolio system 500 and / or coupled trading system(s)). In an exemplary embodiment, the injection 502 of assets may come from a backer, e.g., the entity operating portfolio system 500 and / or another backer. If another backer (e.g., an entity other than the entity operating portfolio system 500) is providing the injection 502 of assets, the backer module may serve as an interface to the other backer's financial institution. In an exemplary embodiment, the injected assets may be stored in a second buffer of the backer module, which serves as a holding platform for increasing asset backing for the shadow portfolio. The injection 502 of assets may be specified for one or more shadow portfolios, e.g., associated with a corresponding trading system or systems. By way of example, the injection 502 may be accompanied by a destination shadow portfolio and its corresponding portfolio value.

[0111] In an exemplary embodiment, the backer module can be configured to calculate an equivalent / corresponding amount of injected asset backing corresponding to the injected / received assets. The calculated amount of asset backing (or a predetermined value thereof) can then be used by the backer module to further calculate a corresponding injected reward value (e.g., membership or reward points) using predetermined relationship rules. In an exemplary embodiment, the calculated injected reward value (e.g., membership or reward points) can be used to reward / distribute (or, for example, sell) 504 to users / members of (one or more) trading systems (e.g., 508) coupled to the portfolio system 500.

[0112] For example, under predetermined relationship rules, in an exemplary embodiment, each reward point may represent a value of $0.10. When a total of 1 kg of gold (i.e., an example of an injected excess asset in this case) is injected into the portfolio system 500 as additional / excess assets, the portfolio module may calculate an equivalent / corresponding injected asset backing (e.g., monetary assets / value), e.g., $80,000 in this example. Thus, for example, under predetermined relationship rules, a total of 800,000 injected membership or reward points may be available for reward / distribution / sale to users / members of the coupled trading system(s) (e.g., 508).

[0113] Thus, asset injection 502 may provide injected reward value (e.g., reward points) that may be used by the coupled trading system(s) (e.g., 508). In an exemplary embodiment, the input module of the portfolio system 500 may also function as an output module. In such an exemplary embodiment, the input module may alternatively be named a transceiver module (compare Figure 1 The injected reward value to be used by the coupled trading system(s) (e.g., 508) may be transmitted from the portfolio system 500 (indicated by the portfolio module) via the transceiver module to the coupled trading system(s) (e.g., 508).

[0114] In an exemplary embodiment, ownership of the injected reward value is to the backer who provided the injection 502 of assets before the injected reward value is awarded / distributed / sold.

[0115] In this exemplary embodiment, the awarding / distribution / selling of the injected reward value (eg, reward points) may be performed via a user / member interface at the coupled transaction system(s) (eg, 508).

[0116] In an exemplary embodiment, the awarding / distribution / sale of injected reward value (e.g., reward points) is reflected in one or more transaction records and transmitted to the investment portfolio system 500. For example, the transaction system(s) (e.g., 508) may sell (i.e., trade) injected reward value (e.g., reward points) to one or more users / members of the transaction system(s) (e.g., 508). In an exemplary embodiment, each transaction record may include reward information indicating a positive increment in reward value and additionally indicating that the reward value is injected reward value.

[0117] In further use, the transceiver module (compare Figure 1The input module 102 of the system receives transaction records from a coupled trading system (e.g., 508). The transceiver module transmits the transaction records to the portfolio module. The portfolio module processes the transaction records to determine a positive or negative increment in reward value. In an exemplary embodiment, upon awarding / distributing an injected reward value (e.g., through a sale), the portfolio module determines that there is a positive increment (or increase) in reward value and that the reward value is the injected reward value. The portfolio module increases the portfolio value associated with the trading system (e.g., 508). The portfolio module determines the portfolio value based on predetermined relationship rules. Therefore, by way of example only, the trading system (e.g., 508) may only use a portion of the injected reward value. In an exemplary embodiment, since the reward value is the injected reward value, the increase in portfolio value is based on the withdrawal of the monetary asset amount indicated by the portfolio module via the backer module, i.e., from the backer module's second buffer containing asset injections 502. The backer module is therefore configured to facilitate an increase in portfolio value (in this exemplary embodiment, a positive increase). This can be viewed or referred to as an update of the cash / asset reserve balance in the portfolio module 506, or as a replenishment / update of the assets backing the shadow portfolio 506. Thus, the portfolio value maintains the assets backing the shadow portfolio of the trading system (e.g., 508). In an exemplary embodiment, the portfolio value is associated with the trading system (e.g., 508) as a whole.

[0118] In some alternative exemplary embodiments, portfolio value is associated with one or more users of a trading system (e.g., 508). When the reward or sale of the injected reward value is completed, the portfolio system 500 can track the rewarded / sold injected reward value (e.g., user / membership points) via a portfolio database provided therein. In such exemplary embodiments, the coupled trading system(s) (e.g., 508) can transmit reward information included in one or more transaction records. This reward information can also additionally indicate that the corresponding injected asset backing is allocated to one or more users identified in the one or more transaction records. In this case, the portfolio module determines that the received reward information is associated / correlated with the injected reward value (e.g., injected membership or reward points) and updates the shadow portfolio associated with the one or more users with the corresponding asset backing from the injected assets already contained in the portfolio system 500 (e.g., extracted from the second buffer of the backer module).

[0119] Thus, in the exemplary embodiments described above, it is recognized that each portfolio or each portfolio value can usefully reflect the transaction history of each trading system and / or each user / member of one or more trading systems. Accordingly, a corresponding shadow portfolio is provided that tracks the transaction history (and corresponding reward value) and, in turn, maintains asset backing (e.g., currency / cash backing) for the trading system(s) and / or user(s). The asset backing can come from previous asset injections, and the reward value can be based on the reward value of the injection further based on the asset injection.

[0120] Figure 4A is a schematic block diagram illustrating an example supporter module in an exemplary embodiment.

[0121] The supporter module of this exemplary embodiment is referenced Figure 1 An example of a supporter module 106 of a portfolio system is described.

[0122] In an exemplary embodiment, the supporter module 400 is configured to promote the increase in the value of the portfolio. For example, in an exemplary embodiment, in use, in the portfolio module (compare Figure 1 After the portfolio module 104 (see reference numeral 404) processes the transaction record to determine a positive increment in reward value (based on the reward / reward information in the transaction record), as shown in the figure, the supporter module 400 can assist the portfolio module in increasing the portfolio value by withdrawing a certain amount of monetary assets from the financial institution (see reference numeral 402) to the portfolio module (see reference numeral 404) via the supporter module 400. As another example, the supporter module 400 is configured to allow assets to be injected from the financial institution (see reference numeral 402) to the portfolio module (see reference numeral 404).

[0123] In an exemplary embodiment, the backer module 400 may also be configured to store and update a backer value. That is, in an exemplary embodiment, the backer module 400 may also be configured to reduce the backer value based on the amount of monetary assets withdrawn from the financial institution to the portfolio module. In an exemplary embodiment, the reduction in backer value may be a reduction in a value indicating the amount of monetary assets (e.g., total cash reserves) available to the backer (e.g., the entity operating the portfolio system) or a reduction in a value related to the amount of monetary assets (e.g., total cash value).

[0124] Figure 4B is a schematic block diagram illustrating an example supporter module in another example embodiment.

[0125] The supporter module of this exemplary embodiment is referenced Figure 1 Another example of a supporter module 106 is described.

[0126] In an exemplary embodiment, the supporter module 401 is configured to promote the increase in the value of the portfolio. For example, in use, in the portfolio module (compare Figure 1 After the portfolio module 104 processes the transaction record to determine a negative increment in reward value (based on the reward / award information in the transaction record), the supporter module 401 can withdraw a certain amount of monetary assets from the portfolio module via the supporter module 401 to help the portfolio module reduce the portfolio value. See reference numeral 406.

[0127] In an exemplary embodiment, the backer module 401 can also be configured to transfer a certain amount of monetary assets to another party (e.g., one or more merchants or partners). See reference numeral 408. As an example, the backer module 401 can be configured to increase the backer value stored in the backer module 401 based on the amount of monetary assets withdrawn from the portfolio module via the backer module 401. In this scenario, the backer value can serve as a buffer. That is, the backer value can include the planned outflow of monetary assets from the portfolio module via the backer module 401. For example, the backer module 401 can serve as a holding platform for scheduled payments to, for example, one or more merchants. See reference numeral 408 again.

[0128] refer to Figure 3 An exemplary method for maintaining a shadow portfolio is described.

[0129] Figure 3 is a schematic flow chart illustrating a method of maintaining a shadow portfolio in an exemplary embodiment. Figure 1 The described portfolio system 100 can implement method 300. In an exemplary embodiment, at step 302, a portfolio module is provided to maintain a shadow portfolio. At step 304, a backer module is provided. At step 306, one or more transaction records are received from one or more trading systems. At step 308, the shadow portfolio is updated with a portfolio value based on reward information included in the one or more transaction records. At step 310, the backer module is used to facilitate an increase in the portfolio value. At step 312, the asset backing for the shadow portfolio is maintained using the portfolio value.

[0130] In another exemplary embodiment, a non-transitory, tangible computer-readable storage medium having software instructions stored thereon may be provided. The instructions, when executed by a computer processor of an investment portfolio system to maintain a shadow investment portfolio, cause the computer processor to perform a method for maintaining a shadow investment portfolio by performing the following steps, including: providing a portfolio module to maintain the shadow investment portfolio; providing a backer module; receiving one or more transaction records from one or more trading systems; updating the shadow investment portfolio with a portfolio value, the update based on reward information included in the one or more transaction records; facilitating an increase in the portfolio value using the backer module; and maintaining asset backing for the shadow investment portfolio with the portfolio value. It will be appreciated that the steps described herein may be non-sequential and may not be arranged in the order listed.

[0131] The various exemplary embodiments may be implemented in the context of data structures, program modules, programs, and computer instructions that are executed in a computer-implemented environment. A general computing environment is briefly disclosed herein. One or more exemplary embodiments may be embodied in one or more computer systems, such as in Figure 6 Schematically shown in .

[0132] One or more exemplary embodiments may be implemented as software (such as a computer program that executes within the computer system 600 and instructs the computer system 600 to perform the methods of the exemplary embodiments).

[0133] Computer system 600 includes a computer unit 602, input modules (such as a keyboard 604 and a pointing device 606), and a plurality of output devices (such as a display 608 and a printer 610). A user can interact with computer unit 602 using the above devices. The pointing device can be implemented using a mouse, a trackball, a pen device, or any similar device. One or more other input devices (not shown) (such as a joystick, a game pad, a satellite dish, a scanner, a touch screen, etc.) can also be connected to computer unit 602. Display 608 can include a cathode ray tube (CRT), a liquid crystal display (LCD), a field emission display (FED), a plasma display, or any other device that produces an image that can be viewed by a user.

[0134] The computer unit 602 can be connected to a computer network 612 via a suitable transceiver device 614 to enable access to, for example, the Internet or other network systems (such as a local area network (LAN) or a wide area network (WAN) or a personal network). The network 612 may include servers, routers, network personal computers, peer devices or other public network nodes, wireless phones or wireless personal digital assistants. Networking environments can be found in offices, enterprise-wide computer networks, home computer systems, etc. The transceiver device 614 can be a modem / router unit located internal or external to the computer unit 602 and can be any type of modem / router (such as a cable modem or a satellite modem).

[0135] It will be appreciated that the network connections shown are exemplary and that other means of establishing a communication link between the computers can be used. Any of a variety of protocols (such as TCP / IP, Frame Relay, Ethernet, FTP, HTTP, etc.) are assumed to be present, and the computer unit 602 can operate in a client-server configuration to allow a user to retrieve web pages from a web-based server. In addition, any of a variety of web browsers can be used to display and manipulate data on the web pages.

[0136] The computer unit 602 in this example includes a processor 618, a random access memory (RAM) 620, and a read-only memory (ROM) 622. The ROM 622 may be system memory that stores basic input / output system (BIOS) information. The RAM 620 may store one or more program modules (such as an operating system, application programs, and program data).

[0137] The computer unit 602 also includes a plurality of input / output (I / O) interface units, such as an I / O interface unit 624 to the display 608 and an I / O interface unit 626 to the keyboard 604. The components of the computer unit 602 typically communicate and interface / couple via an interconnected system bus 628 and in a manner known to those skilled in the relevant art. The bus 628 can be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.

[0138] It will be appreciated that other devices may also be connected to the system bus 628. For example, a universal serial bus (USB) interface may be used to couple a video or digital camera to the system bus 628. An IEEE 1394 interface may be used to couple additional devices to the computer unit 602. Other manufacturer interfaces are also possible, such as FireWire developed by Apple and i.Link developed by Sony. Devices may also be coupled to the system bus 628 via a parallel port, a game port, a PCI board, or any other interface used to couple input devices to a computer. It will also be appreciated that, although components are not shown, sound / audio may be recorded and reproduced using a microphone and speakers. A sound card may be used to couple a microphone and speakers to the system bus 628. It will be appreciated that several peripheral devices may be coupled to the system bus 628 simultaneously via alternative interfaces.

[0139] Application programs can be provided to users of the computer system 600 so as to be encoded / stored on a data storage medium such as a CD-ROM or a flash memory carrier. Application programs can be read using the corresponding data storage medium drive of the data storage device 630. The data storage medium is not limited to being portable and can include instances embedded in the computer unit 602. The data storage device 630 can include a hard disk interface unit and / or a removable memory interface unit (neither of which is shown in detail) that couples a hard disk drive and / or a removable memory drive to the system bus 628, respectively. This can enable reading / writing data. Examples of removable memory drives include magnetic disk drives and optical disk drives. The drive and its associated computer-readable medium (such as a floppy disk) provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computer unit 602. It will be appreciated that the computer unit 602 can include several such drives. In addition, the computer unit 602 can include drives for interfacing with other types of computer-readable media.

[0140] The application program is read and controlled by the processor 618 during its execution. Intermediate storage of program data can be implemented using RAM 620. The method(s) of the exemplary embodiments can be implemented as computer-readable instructions, computer-executable components, or software modules. One or more software modules can be used instead. These can include executable programs, data link libraries, configuration files, databases, graphic images, binary data files, text data files, object files, source code files, etc. When one or more computer processors execute one or more of the software modules, the software modules interact so that one or more computer systems perform according to the teachings of this document.

[0141] The operation of the computer unit 602 can be controlled by a variety of different program modules. Examples of program modules are routines, programs, objects, components, data structures, libraries, etc. that perform specific tasks or implement specific abstract data types. The exemplary embodiments can also be practiced using other computer system configurations, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, personal digital assistants, mobile phones, etc. In addition, the exemplary embodiments can also be practiced in distributed computing environments, where tasks are performed by remote processing devices linked through wireless or wired communication networks. In a distributed computing environment, program modules can be located both locally and in remote memory storage devices.

[0142] The exemplary embodiments may also be implemented using other computer system configurations, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, personal digital assistants, mobile phones, and the like. Furthermore, the exemplary embodiments may also be practiced in distributed computing environments, where tasks are performed by remote processing devices that are linked through wireless or wired communications networks. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0143] As used in this description, the terms "coupled" or "connected" are intended to cover both direct connections and connections through one or more intermediate components, unless otherwise specified. The terms "configured to (perform a task / action)", "configured for (performing a task / action)", etc. used in this specification include programmable, programmed, connectable, wired, or otherwise constructed to have the ability to perform a task / operation when arranged or installed as described herein. The terms "configured to (perform a task / action)", "configured for (performing a task / action)", etc. are intended to encompass "when in use, performing a task / action", for example, specifically and / or specifically configured and / or specifically arranged to perform a task / operation.

[0144] The description herein may be described in some parts, explicitly or implicitly, as algorithms and / or functional operations for operating on data in a computer memory or electronic circuit. These algorithmic descriptions and / or functional operations are typically used by those skilled in the art of information / data processing for efficient description. An algorithm generally involves a self-consistent sequence of steps leading to a desired result. Algorithmic steps may include physical manipulations of physical quantities, such as electrical, magnetic, or optical signals that can be stored, sent, transmitted, combined, compared, and otherwise manipulated.

[0145] In addition, unless specifically stated otherwise, and as will generally be apparent from the following, those skilled in the art will recognize that throughout this specification, discussions utilizing terms such as "scan," "calculate," "determine," "replace," "generate," "initialize," "output," etc., refer to the actions and processes of an instruction processor / computer system or similar electronic circuit / device / component that manipulates / processes and transforms data represented as physical quantities in the described system into data similarly represented as other physical quantities in the system or other information storage, transmission or display device, etc.

[0146] This description also discloses related equipment / devices for performing the steps of the method. Such equipment may be specifically constructed for the method, or may include a general-purpose computer / processor or other device selectively activated or reconfigured by a computer program stored in a storage member. The algorithms and displays described herein are not inherently associated with any particular computer or other device. It is understood that general-purpose equipment / machines may be used in accordance with the teachings of this document. Alternatively, the construction of dedicated equipment / devices for performing the method steps may be desired.

[0147] In addition, it is believed that the present description also implicitly covers computer programs, as it will be clear that the steps of the methods described herein can be practiced by computer code. It will be appreciated that a large number of programming languages ​​and encodings can be used to implement the teachings described herein. Moreover, the computer programs are not limited to any particular control flow and different control flows can be used, if applicable, without departing from the scope of the present invention.

[0148] In addition, if applicable, one or more steps of the computer program can be executed in parallel and / or serially. If applicable, such computer program can be stored on any computer-readable medium. Computer-readable media can include storage devices, such as magnetic or optical disks, memory chips, or other storage devices suitable for interface with suitable readers / general-purpose computers. In this case, computer-readable storage media are non-transient. Such storage media also covers all computer-readable media, for example, media that only store data for a short period of time and / or only when there is power, such as register memory, processor cache, and random access memory (RAM). Computer-readable media can even include wired media (such as those exemplified in Internet systems) or wireless media (such as those exemplified in Bluetooth technology). When loaded and executed on a suitable reader, the computer program effectively causes a device that can implement the steps of the method.

[0149] The exemplary embodiments may also be implemented as hardware modules. A module is a functional hardware unit designed to be used in conjunction with other components or modules. For example, a module may be implemented using digital or discrete electronic components, or it may form part of an entire electronic circuit such as an application specific integrated circuit (ASIC). Those skilled in the art will appreciate that the exemplary embodiments may also be implemented as a combination of hardware and software modules.

[0150] In addition, when describing some embodiments, the present disclosure may have disclosed methods and / or processes as a specific sequence of steps. However, unless otherwise required, it will be appreciated that the method or process should not be limited to the specific sequence of steps disclosed. Other step orders are also possible. The specific order of the steps disclosed herein should not be construed as unduly limiting. Unless otherwise required, the methods and / or processes disclosed herein should not be limited to the steps performed in the order written. The order of the steps can be varied and still be within the scope of the present disclosure.

[0151] Additionally, throughout the description herein, whenever the term "substantially" is used, it is understood to include, but is not limited to, "entirely" or "completely." Furthermore, whenever used, terms such as "comprising" are intended to be non-limiting, descriptive language, as they broadly encompass the elements / components listed following such terms, as well as other components not expressly stated. For example, when "comprising" is used, reference to "a" feature is also intended to be a reference to "at least one" of that feature. Terms such as "consisting of" can be considered subsets of terms such as "comprising" in appropriate contexts. Therefore, in embodiments disclosed herein that use terms such as "comprising," it should be understood that these embodiments use terms such as "consisting of" to provide the teachings of the corresponding embodiments. Additionally, whenever used, terms such as "approximately" and "about" generally mean reasonable variations, such as a + / - 5% variation from the disclosed value, a 4% variation from the disclosed value, a 3% variation from the disclosed value, a 2% variation from the disclosed value, or a 1% variation from the disclosed value.

[0152] In addition, in the description herein, certain values ​​may be disclosed as ranges. The values ​​indicating the end points of a range are intended to illustrate a preferred range. Whenever a range is described, the range is intended to cover and teach all possible subranges and individual values ​​within that range. That is, the end points of a range should not be interpreted as rigid limitations. For example, a description of a range of 1% to 5% is intended to have specifically disclosed subranges of 1% to 2%, 1% to 3%, 1% to 4%, 2% to 3%, and so on, as well as individual values ​​within that range, such as 1%, 2%, 3%, 4%, and 5%. The above specifically disclosed intentions apply to ranges of any depth / breadth.

[0153] In the exemplary embodiment, it is described that the determination of an asset value proportional to the reward value indicated in the reward information of a transaction record based on a predetermined relationship rule (e.g., a ratio) can be performed at the portfolio system. However, it will be appreciated that such determination is not limited to this. That is, the determination (e.g., how much asset backing is to be moved into or out of the shadow portfolio and / or the portfolio value) can be performed at the transaction system, and the transaction record can instead contain instructions, e.g., tagged / attached / encrypted with reward information, to increase or decrease the associated portfolio value.

[0154] In some exemplary embodiments, a user may utilize the user's accumulated reward points as a redemption for cash, in addition to or in lieu of redeeming / consuming goods and / or services. Such cash conversion may be based on a ratio (i.e., a reward points:cash ratio). The cash conversion may be via electronic means to a user's personal bank account and / or actual cash. For example, the portfolio system may be configured to instruct the financial system via the backer module to withdraw a calculated asset value or amount of asset backing (or portfolio value in the case of a shadow portfolio or portfolio module) associated with the corresponding trading system or associated user from a designated bank account based on a calculated cash conversion amount determined by the ratio, i.e., from the asset backing (e.g., currency / cash reserves) (e.g., comparison Figure 2 The calculated asset value is withdrawn (reference numeral 224 in the figure) and deposited into an indicated destination, such as a personal bank account of the user requesting the cash conversion. Such instructions may be provided, for example, in the user information, request information, destination information, etc., of the transaction record transmitted to the asset portfolio system.

[0155] In an exemplary embodiment, the portfolio system may maintain a shadow portfolio associated with a corresponding trading system. However, it will be appreciated that maintaining a shadow portfolio may also include generating a shadow portfolio, for example, when a trading system is newly coupled to the portfolio system, and updating the generated shadow portfolio.

[0156] In yet other exemplary embodiments, a shadow portfolio can be associated with more than one trading system. For example, a shadow portfolio can be shared among more than one trading system. Updates to the shadow portfolio can then be based on reward information included in one or more transaction records transmitted to the portfolio system by one or more trading systems.

[0157] In an exemplary embodiment, the backer providing asset support to one or more shadow portfolios may be the entity operating the portfolio system. However, it will be appreciated that exemplary embodiments are not limited thereto. For example, the backer may be separate from the entity operating the portfolio system. Furthermore, provision may be made for multiple backers to be registered to provide asset support via the portfolio system.

[0158] In an exemplary embodiment, the operation of the trading system(s) may be independent of the operation of the portfolio system. For example, the time or instance of transmitting one or more trade records from the trading system(s) to the portfolio system may be determined within the trading system(s) and independent of the portfolio system. For example, the time or instance of transmitting the one or more trade records may be determined at the trading system(s), such as, but not limited to, at one or more periodic intervals, during real-time operation, at one or more system-prompted activation times, or at one or more user-prompted activation times at the trading system(s).

[0159] In an exemplary embodiment, the transaction record may include reward information, which may include other information such as reward value, user information, request information, destination information, etc. However, it will be appreciated that the exemplary embodiment is not limited to such specific forms of information. The exemplary embodiment may operate broadly as long as there is sufficient reward information to provide the functionality to update one or more shadow portfolios and / or portfolio values. In an exemplary embodiment, the asset backing may have an equivalent monetary value and may be one or a combination of assets such as cash, cryptocurrency, precious metals, commodities, etc. That is, the asset backing is intended to cover any form of substance or asset that can provide support, collateral, etc. for a shadow portfolio. That is, such assets may even include precious metals such as gold, silver, rare elements, etc. In the description, references to monetary assets are also intended to mean the above, i.e., any substance that has an equivalent monetary value.

[0160] In the exemplary embodiment, a financial institution is used as a bank entity. It will be appreciated that the scope of such institutions is broad, as long as they can provide asset backing for shadow portfolios. For example, such institutions can include other types of entities, such as cryptocurrency exchanges and wallets. In such cases, the assets can be pegged to a monetary value and can be cryptocurrencies.

[0161] In an exemplary embodiment, predetermined relationship rules are used to determine a reward value associated with an asset value. For example, a reward value received in one or more transaction records can determine how much the asset value is to be increased or decreased in the portfolio module (i.e., for asset backing of a shadow portfolio). For example, the injection amount of an asset having the asset value can determine how much reward value is to be injected (e.g., for distribution / reward / sale at one or more coupled trading systems). It will be appreciated that the predetermined relationship rules can be the same for positive increments of asset backing, for negative increments of asset backing, and / or for injections of reward value. It will also be appreciated that the predetermined relationship rules can be different for the above-mentioned actions and / or different for different trading system(s) and / or different one or more users of the trading system(s).

[0162] Those skilled in the art will recognize that other changes and / or modifications may be made to the specific embodiments without departing from the scope of the invention as broadly described. For example, in the description herein, features of different exemplary embodiments may be mixed, combined, interchanged, merged, adopted, modified, included, etc. across different exemplary embodiments. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive.

Claims

1. A portfolio system for coupling to one or more trading systems to maintain a shadow portfolio, the portfolio system comprising: an input module configured to receive one or more transaction records from the one or more transaction systems; a portfolio module coupled to the input module, the portfolio module configured to maintain a shadow portfolio, the portfolio module further configured to update the shadow portfolio with a portfolio value, the update being based on reward information included in the one or more transaction records, and the portfolio value maintaining assets backing the shadow portfolio; as well as a backer module coupled to the portfolio module, the backer module being configured to facilitate increments in portfolio value, the backer module being arranged to be coupled to one or more financial institutions, the backer module being further configured to allow inflows and outflows of asset backing relative to the portfolio module; and wherein the portfolio module maintains the asset backing for the shadow portfolio after increments in portfolio value.

2. The investment portfolio system of claim 1, wherein the increment of the investment portfolio value comprises a positive increment or a negative increment.

3. The investment portfolio system according to claim 1 or 2, further comprising the investment portfolio module being configured to update the shadow investment portfolio with the investment portfolio value based on a predetermined relationship rule between the reward value of the reward information and the asset value.

4. The investment portfolio system of claim 2, wherein if the increment in portfolio value is a positive increment, the portfolio module is configured to extract an amount of asset backing to increase the asset backing, the extraction being performed on the portfolio module via the backer module.

5. The investment portfolio system of claim 2, wherein if the increment in portfolio value is a negative increment, the portfolio module is configured to withdraw an amount of asset backing to reduce the asset backing, the withdrawal being performed from the portfolio module via the backer module.

6. The investment portfolio system of claim 1 or 2, wherein a shadow investment portfolio is associated with the one or more trading systems.

7. The investment portfolio system of claim 1 or 2, wherein a shadow portfolio is associated with a user of the one or more trading systems.

8. The investment portfolio system of claim 1 or 2, wherein the input module is further configured to receive interest information indicating a calculated interest yield, and upon receiving the interest information, the investment portfolio module is configured to update the investment portfolio value with the calculated interest yield. Updating the portfolio value with the calculated interest income includes extracting interest from the interest amount of the asset backing to increase the asset backing, the interest extraction being performed on the portfolio module via the backer module.

9. The investment portfolio system of claim 1 or 2, wherein the investment portfolio module is configured to utilize asset backing to transfer to one or more merchants, the transfer being based on the one or more transaction records.

10. The investment portfolio system of claim 1 or 2, wherein the investment portfolio module is configured to perform currency conversion using asset backing, the currency conversion being based on the one or more transaction records.

11. The investment portfolio system of claim 1 or 2, wherein the backer module is configured to receive an injection of assets and the backer module is further configured to generate a corresponding injected reward value based on the injection of assets, and wherein the input module is further configured to transmit the injected reward value for use outside the investment portfolio system.

12. The investment portfolio system of claim 11 , wherein the portfolio module is further configured to update the shadow portfolio with a portfolio value, the update being based on reward information associated with the injected reward value, the reward information being included in the one or more transaction records, and the portfolio value is increased by asset backing based on the injection of assets to maintain asset backing for the shadow portfolio.

13. A method of maintaining a shadow portfolio, the method comprising: Provides a portfolio module of the portfolio system to maintain shadow portfolios; providing a supporter module for said portfolio system; coupling a backer module of the portfolio system with one or more financial institutions; receiving one or more transaction records from one or more transaction systems; updating a shadow portfolio with a portfolio value, the updating being based on reward information included in the one or more transaction records; Use the Supporter Module to drive incremental portfolio value; and maintaining the asset backing of the shadow portfolio with the portfolio value after said increment; and The backer module allows the inflow and outflow of the asset support relative to the portfolio module.

14. The method of claim 13, wherein the increment in portfolio value comprises a positive increment or a negative increment.

15. The method of claim 13 or 14, wherein the step of updating the shadow investment portfolio with the investment portfolio value is further based on a predetermined relationship rule between the reward value of the reward information and the asset value.

16. The method of claim 14, wherein if the increment in portfolio value is a positive increment, then updating the shadow portfolio with the portfolio value comprises extracting an amount of asset backing to increase the asset backing, the extracting being performed via the backer module to the portfolio module.

17. The method of claim 14, wherein if the increment in portfolio value is a negative increment, then updating the shadow portfolio with the portfolio value comprises withdrawing an amount of asset backing to reduce the asset backing, the withdrawal being performed from the portfolio module via the backer module.

18. The method of claim 13 or 14, further comprising associating a shadow portfolio with the one or more trading systems.

19. The method of claim 13 or 14, further comprising associating a shadow portfolio with a user of the one or more trading systems.

20. The method of claim 13 or 14, further comprising receiving interest information indicating the calculated interest yield; and The step of updating the shadow portfolio with the portfolio value includes extracting interest on the interest amount of the asset backing to increase the asset backing, the interest extraction being performed on the portfolio module via the backer module.

21. The method of claim 13 or 14, further comprising utilizing asset backing to transfer to one or more merchants, the transfer being based on the one or more transaction records.

22. The method of claim 13 or 14, further comprising performing a currency conversion using asset backing, the currency conversion being based on the one or more transaction records.

23. The method of claim 13 or 14, further comprising: Receive asset injections via the supporter module; Generate corresponding reward value based on asset injection; as well as The injected reward value is transmitted for use at the one or more transaction systems.

24. The method of claim 23, further comprising: receiving reward information associated with the injected reward value, the reward information included in the one or more transaction records; as well as Increase asset support based on asset injection.

25. A non-transitory tangible computer-readable storage medium having stored thereon software instructions, said software instructions, when executed by a computer processor of an investment portfolio system to maintain a shadow investment portfolio, causes the computer processor to perform a method of maintaining a shadow investment portfolio by performing the following steps, the steps comprising, Provides a portfolio module of the portfolio system to maintain shadow portfolios; providing a supporter module for said portfolio system; coupling a backer module of the portfolio system with one or more financial institutions; receiving one or more transaction records from one or more transaction systems; updating a shadow portfolio with a portfolio value, the updating being based on reward information included in the one or more transaction records; Use the Supporter Module to drive incremental portfolio value; and maintaining the asset backing of the shadow portfolio with the portfolio value after said increment; and The backer module allows for inflows and outflows of asset backing relative to the portfolio module.

Images