US20130198062A1 - Value determination for mobile transactions - Google Patents

Abstract

Various embodiments provide techniques for determining a value share of a mobile transaction for one or more entities associated with the mobile transaction. Examples of mobile transactions include purchases of content such as applications, games, video, audio, graphics, and so on. In one or more embodiments, value share rules can be created and reconfigured. The value share rules specify a share of a transaction value (e.g., a percentage of revenue generated from a purchase of content) that an entity involved in a particular mobile transaction is credited with. In one example scenario, a user of a mobile device purchases an application for the mobile device. A value share rule can be applied to the application purchase amount to determine a share of the application purchase amount that is to be credited to a mobile operator that provides service for the mobile device.

Description

RELATED APPLICATIONS
• This application is a divisional application of and claims priority to U.S. application Ser. No. 12/701,192, filed on Feb. 5, 2010, and entitled “Value Determination for Mobile Transactions,” the disclosure of which is incorporated in its entirety by reference herein.
BACKGROUND
• Mobile devices present an increasingly common platform for a variety of different functions, such as communication, computing, business, and entertainment. To assist in the performance of these functions, a mobile device can include content that can be experienced via the mobile device. Examples of content can include applications, games, video, audio, graphics, and so on. While some mobile devices can be purchased with pre-loaded content, a burgeoning market has arisen for content that can be purchased and loaded by users of mobile devices.
• Several different entities may cooperate to provide access to a mobile marketplace that enables users to locate, select, purchase, and receive content. These entities can include a content producer, a mobile operator, and a mobile marketplace host. The content producer originates or generates content, and can include an entity such as an independent software vendor. The mobile operator provides infrastructure and services to enable wireless communication and data transfer. The mobile operator can include an entity such as a cell phone service provider. The mobile marketplace host provides a market platform whereby content can be presented to users of a mobile device. For example, the mobile marketplace host can include a web-based marketing and purchasing resource (e.g., a website) or other wireless-accessible resource that can present content to users and enable the users to purchase the content.
• In one example scenario, a cell phone user subscribes to a cell phone service provided by a particular mobile operator. The cell phone user utilizes a cell phone to run a mobile marketplace application and access a mobile marketplace service via the Internet. The cell phone user then views instances of content presented via the mobile marketplace service and purchases an instance of the content by interacting with the service. The instance of the content was originally generated by a particular content producer and was then marketed and made available for purchase by the mobile marketplace service. The cell phone user then receives and consumes the content on his or her cell phone.
• While cooperation of these different entities in creating and maintaining the mobile marketplace can provide a tremendous marketing and purchasing resource, allocating revenue resulting from mobile marketplace transactions can be challenging. Current ways of revenue allocation are typically based on an agreement between the various mobile marketplace entities and simply utilize a static percentage-of-transaction allocation for each of the entities. Such ways of revenue allocation typically cannot account for variations in transaction details or for changes in a revenue allocation agreement between particular mobile marketplace entities.
SUMMARY
• This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
• Various embodiments provide techniques for determining a value share of a mobile transaction for one or more entities associated with the mobile transaction. Examples of mobile transactions include purchases of content such as applications, games, video, audio, graphics, and so on. In one or more embodiments, value share rules are created that each specify a share of a transaction value (e.g., a percentage of revenue generated from a purchase of content) that an entity involved in a particular mobile transaction is credited with. In one example scenario, a user of a mobile device purchases an application for the mobile device. A value share rule can be applied to the application purchase amount to determine a share of the application purchase amount that is to be credited to a mobile operator that provides service for the mobile device.
BRIEF DESCRIPTION OF THE DRAWINGS
• The same numbers are used throughout the drawings to reference like features.
• FIG. 1 illustrates an operating environment in which the inventive principles can be employed in accordance with one or more embodiments.
• FIG. 2 illustrates an example user interface in accordance with one or more embodiments.
• FIG. 3 illustrates an example application of a value share rule in accordance with one or more embodiments.
• FIG. 4 illustrates an example parameter hierarchy table in accordance with one or more embodiments.
• FIG. 5 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
• FIG. 6 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
• FIG. 7 is a block diagram of a system in accordance with one or more embodiments.
DETAILED DESCRIPTIONOverview
• Various embodiments provide techniques for determining a value share of a mobile transaction for one or more entities associated with the mobile transaction. Examples of mobile transactions include purchases of content such as applications, games, video, audio, graphics, and so on. In one or more embodiments, value share rules are created that each specify a share of a transaction value (e.g., a percentage of revenue generated from a purchase of content) that an entity involved in a particular mobile transaction is credited with. In one example scenario, a user of a mobile device purchases an application for the mobile device. A value share rule can be applied to the application purchase amount to determine a share of the application purchase amount that is to be credited to a mobile operator that provides service for the mobile device.
• In some embodiments, value share rules can be created based on a variety of different mobile transaction parameters. Examples of mobile transaction parameters include a payment method used for a mobile transaction, a particular mobile operator involved with the mobile transaction, a purchase channel used to complete the mobile transaction (e.g., a mobile device, a desktop computer, and so on), a type of content purchased via the mobile transaction, and so on. Thus, for a mobile transaction that includes a specific set of mobile transaction parameters, a particular value share rule can be applied to allot to a particular entity a share of the transaction value.
• Various techniques discussed herein can be enabled by a transaction processor that receives mobile transaction information for a particular mobile transaction and applies a value share rule to the transaction information to determine a value share for the particular mobile transaction. According to some embodiments, the transaction processor can provide a dynamic and extensible way to configure value share rules based on value share terms negotiated between entities associated with mobile transactions. These entities can include a mobile operator (e.g., a cell phone and/or wireless data service carrier), a mobile marketplace host (e.g., a mobile marketplace website), a content provider (e.g., an application software vendor), and so on. In some embodiments, the transaction processor can serve as an intermediary between these entities to determine value shares of mobile transactions for each of the entities based on a value share rule.
• In the discussion that follows, a section entitled “Operating Environment” describes but one environment in which the various embodiments can be employed. Following this, a section entitled “Example User Interface” describes one example user interface in accordance with one or more embodiments. Next, a section entitled “Example Application of Value Share Rules” describes example value share rules and how the rules can be applied to mobile transactions in accordance with one or more embodiments. Following this, a section entitled “Example Methods” describes example methods in accordance with one or more embodiments. Last, a section entitled “Example System” is provided and describes an example system that can be used to implement one or more embodiments.
Operating Environment
• FIG. 1 illustrates an operating environment in accordance with one or more embodiments, generally at100.Environment100 includes amobile device102 and amobile marketplace application104 that resides on the mobile device and is configured to run on the mobile device. According to some embodiments, themobile device102 is configured to access anetwork106 via a mobile service provided by amobile operator108. Examples of themobile device102 can include a cell phone, a smart phone, a personal digital assistant, a netbook, a laptop computer, and so on. Thenetwork106 can include any wireless and/or wired network, such as the internet.
• Theenvironment100 also includes amobile marketplace host110 that hosts amarketplace website112. While themobile marketplace host110 is discussed with respect to themarketplace website112, this is not intended to be limiting, and the mobile marketplace website can provide marketplace services directly to themobile device102 without requiring the mobile device to access themarketplace website112.
• In some embodiments, themobile marketplace host110 can offer a variety of content for purchase (e.g., via themarketplace website112 or other marketplace service), such as content created and/or generated by acontent provider114. Thecontent provider114 can include an entity such as a software developer, a media vendor (e.g., video and/or audio), a game developer, and so on. In one example scenario, themobile device102 can access themarketplace website112 and view a selection of content that can be purchased. When an instance of content is purchased from themarketplace website112 as part of a purchase transaction, the instance of content can then be transferred (e.g., downloaded) to themobile device102.
• As part of the purchase transaction, acharging gateway116 receives information about the purchase transaction and applies a charge to an account associated with themobile device102 and/or a user of themobile device102. Examples of an account can include a bank account, a credit card account, a debit account, an e-commerce account (e.g., PayPal®), and so on. The information about the purchase transaction can then be stored at atransaction store118. Thetransaction store118 can store transaction information for a variety of different entities, such as themobile operator108, themobile marketplace host110, and so on.
• Theenvironment100 also includes atransaction processor120 that is configured to receive transaction information, e.g., from thetransaction store118. Thetransaction processor120 also includes aconfiguration user interface122 that can be used to configure thetransaction processor120 with value share rules124. A particular value share rule of the value share rules124 can be applied to a purchase transaction to determine a value share amount of the purchase transaction to be allotted to a particular entity, such as themobile operator108, themobile marketplace host110, thecontent provider114, and so on.
• In one example implementation, themobile operator108 and themobile marketplace host110 negotiate a value share agreement regarding mobile transactions that involve themobile operator108 and themobile marketplace host110, such as the purchase of content from themarketplace website112 via themobile device102. Included in the value share agreement are business terms that specify a revenue share of purchase transactions for eachmobile operator108 and themarketplace host110. According to some embodiments, thetransaction processor120 is configured with the business terms (e.g., via the configuration user interface122) to generate the value share rules124.
• Further to this example implementation, when content is purchased from themarketplace website112 as part of a purchase transaction, thetransaction processor120 receives information about the purchase transaction and applies one or more of thevalue share rules124 to the purchase transaction to determine a revenue share amount of the purchase transaction for eachmobile operator108 and themobile marketplace host110. According to some embodiments, eachmobile operator108 and themobile marketplace host110 can then be credited with its respective revenue share amount. This particular implementation is presented for purposes of example only, and in some embodiments a value share rule can specify value share for any type and number of entities. Further, value share rules are not limited to revenue share, but may also be configured to determine other value-based properties such as tax rates, regulatory fees, and so on.
• While not explicitly illustrated here, but as noted above with respect to thetransaction processor120, one or more of the entities included as part of the operatingenvironment100 can be implemented in connection with one or more computing devices. One specific example of a computing device is shown and described below inFIG. 7. For example, thetransaction processor120 and its components can be embodied as computer-executable instructions stored on one or more computer-readable storage media and executable by one or more processors to implement various techniques discussed herein.
• Having considered an example operating environment, consider now a discussion of an example user interface for implementing one or more of the techniques discussed herein. The example user interface is discussed with reference toenvironment100 above.
Example User Interface
• FIG. 2 illustrates one example of theconfiguration user interface122 discussed inFIG. 1 in accordance with one or more embodiments. According to some embodiments, theconfiguration user interface122 can be associated with one or more of a variety of different applications (e.g., a web browser) and can be displayed by a computing device, such as the computing device shown and described below inFIG. 7.
• According to some embodiments, theconfiguration user interface122 can be utilized to configure value share rules for one or more entities associated with mobile transactions. Theconfiguration user interface122 includes anentity menu200 that is configured to be populated with an entity associated with mobile transactions. For example, particular entities (e.g., themobile operator108 and the mobile marketplace host110) can enter into a value share agreement for mobile transactions. Thus, according to some embodiments, theentity menu200 can be populated with an entity or entities that are parties to the value share agreement to enable value share rules to be set up according to the value share agreement.
• Also in some example embodiments, theconfiguration user interface122 can be utilized to configure value share rules for a variety of different entities and different sets of entities. For example, a host entity (e.g., the mobile marketplace host110) can enter into a different value share agreement with each of several different mobile operators. In some embodiments, theconfiguration user interface122 can be used to configure a unique set of value share rules based on each of the different value share agreements. Thus, theconfiguration user interface122 can be utilized to configure, reconfigure, and manage multiple different sets of value share rules.
• Theconfiguration user interface122 also includes a rules table202 that can receive information used to create value share rules. In the illustrated example embodiment, the rules table202 includes a column for each of a number of rule parameters. Each of the columns includes data fields that can be populated with rule parameter values that can be used to determine value shares of mobile transactions. Rule parameter values can include features and/or characteristics of mobile transactions that can be used to categorize mobile transactions for purposes of determining value share. According to some embodiments, the data fields included as part of the rules table202 can be populated by direct entry of data (e.g., via a keyboard or other input device) and/or the data fields may include drop-discussion down menus that offer selections of particular rule parameter values. A brief of each of the rule parameters of the rules table204 is presented below.
• Rule ID Parameter204: This parameter includes an identifier for each of the rules in the rules table202. The use of letters is for purposes of example only, and any type of identifier can be utilized.
• Category Parameter206: This parameter allows categories to be specified for transactions. According to some embodiments, a category can refer to a particular content market and/or a specific business (e.g., ABC Application Store) in which content is offered for purchase.
• Mobile Operator Parameter208: This parameter allows a particular mobile operator to be specified for a value share rule.
• Payment Type Parameter210: This parameter allows a particular payment type to be specified for a value share rule. Examples of a payment type include credit card, debit card, an e-commerce account (e.g., PayPal®), bank account transfer, and so on. Payment type can also indicate a charge to a mobile operator, which indicates that content can be purchased by charging a mobile service account (e.g., a user's cell phone account) for all or part of the content purchase price.
• Channel Parameter212: This parameter allows a purchase channel to be specified for a value share rule. In some embodiments, the purchase channel can include a device that was used to transact a purchase of content. For example, the device may be a mobile device for which a particular mobile operator provides service. According to some embodiments, other devices may also be utilized, such as a desktop PC or other computing device to which a mobile device can be tethered.
• Item Type Parameter214: This parameter allows an item type to be specified for a value share rule. For example, item type can include a particular category of content that can be purchased, such as applications, games, audio, video, and so on.
• Item Identifier Parameter216: This parameter allows a specific item identifier to be specified for a value share rule. For example, an identifier can be specified for a particular application, game, or other instance of content.
• Value Share Code Parameter218: This parameter allows a value share code to be specified for a value share rule. A value share code can be associated with a promotional program for a particular product, type of product, product source (e.g., a retailer), and so on.
• Value Share Rate Parameter220: This parameter allows a value share rate to be specified for a value share rule. In the illustrated example, the value share rate includes a specific percentage of value for each value share rule. Thus, according to some embodiments, if a value share rule is applied to a transaction, the value share rate can be applied to the transaction amount to determine a share of the transaction amount for a particular entity. Additionally or alternatively, in some embodiments the valueshare rate parameter220 can include a flat value amount that is credited to a particular entity for a mobile transaction that qualifies for a particular value share rule.
• While not expressly illustrated here, according to some embodiments a value share rule can also include an effective date parameter. The effective date parameter can specify a start date and/or an end date for a value share rule. Thus, in some embodiments, a different value share rule can apply to a particular mobile transaction depending on a transaction date of the particular mobile transaction.
• The rule parameters illustrated in the rules table202 are for purposes of example only, and in some embodiments a variety of other rule parameters may be utilized. Examples of other rule parameters include, by way of example and not limitation, a location where a mobile transaction occurs (e.g., a country, a state, or other geographical zone), a currency utilized in the mobile transaction, a user identifier associated with the mobile transaction and/or a mobile device, and so on.
• Theconfiguration user interface122 also includes an applybutton222. When a value share rule from the rules table204 is created or reconfigured, the applybutton222 can be activated to cause the new rule or the reconfigured rule to be available to be applied to mobile transactions.
Example Application of Value Share Rules
• FIG. 3 illustrates one example of an application of value share rules to mobile transactions in accordance with one or more embodiments. According to some embodiments, the acts discussed with respect toFIG. 3 can be implemented by a computing device, such as the computing device shown and described below inFIG. 7. With reference toenvironment100 discussed above and in accordance with some embodiments, the acts discussed with respect toFIG. 3 can be implemented by thetransaction processor120.
• For illustration purposes,FIG. 3 includes the rules table202 discussed above.FIG. 3 also includes a transaction table300 that lists transaction parameters and transaction parameter values for several example mobile transactions. Transaction table300 includes atransaction identifier column302 and arules column304. The fields included as part of thetransaction identifier column302 each include an identifier for a particular mobile transaction. The fields included as part of therules column304 each include a rule that is applied to determine a value share for a particular mobile transaction. The transaction table300 also includes a valueshare rate column306 that indicates value share rates that are applied to each of the mobile transactions described in the transaction table300. The remaining columns include transaction parameters for each of the transactions included in the transaction table300.
• According to some embodiments, a null value for a particular rule parameter value in a value share rule can be interpreted as allowing any value for a particular mobile transaction. For example, with reference to Rule A of the rules table202, the rule parameter value for theitem type parameter214 is null (e.g., blank). Thus, a particular mobile transaction may be for the purchase of any item type (e.g., games, applications, video, and so on) and still qualify for Rule A.
• In some embodiments, a determination of which value share rule to apply to a particular mobile transaction is made based on the most specific match of transaction parameter values to rule parameter values. This aspect of value share determination is discussed in more detail below in the discussion ofFIG. 4.
• For illustration purposes and in accordance with some embodiments, atransaction308 included as part of the transaction table300 will be discussed to explain one example of how a value share rule can be applied to a mobile transaction. Value share rules can be applied to the remaining mobile transactions in the transaction table300 using a similar process as that discussed below with respect to thetransaction308.
• Thetransaction308 includes “Marketplace” and “ABC” transaction parameter values, which match all of the rule parameter values for the “Category” and “MO” rule parameters, respectively, in the rules table204. Thetransaction308 also includes a “Mobile” transaction parameter value for the “Payment Type” transaction parameter, which matches the rule parameter values for Rules D and H because their payment type rule values are set to “Mobile,” and Rules A and F because their payment type rule values are null and thus allow for any transaction parameter value. Thetransaction308 indicates a transaction parameter value of “255” for the “Item ID” transaction parameter. This particular value eliminates Rules D, F, and H, since these rules includes a different rule parameter value for their respective “Item ID” rule parameters. In this example, Rule A is applied to thetransaction308 since its “Item ID” rule parameter value is null and thus allows any item ID value.
• Thus, Rule A is the most specific match to the transaction parameter values of thetransaction308. As indicated by Rule A, a value share rate of 10% is applied to thetransaction308. According to some embodiments, the mobile operator ABC would be credited with 10% of the purchase price of content associated with thetransaction308.
• FIG. 4 illustrates generally at400 an example parameter hierarchy table in accordance with one or more embodiments. The parameter hierarchy table400 includes atransaction parameter column402, anexample value column404, and animpact column406. Thetransaction parameter column402 includes example transaction parameters that can be used to determine a value share rule that applies to a particular mobile transaction. Theexample value column404 includes example transaction parameter values and theimpact column406 includes examples of how the transaction parameters in thetransaction parameter column402 can be used to create value share rules.
• As mentioned above, in some embodiments a determination as to which value share rule applies to a particular mobile transaction is made based on the most specific match of transaction parameter values to rule parameter values. In the parameter hierarchy table400, the transaction parameters in thetransaction parameter column402 are presented in descending order from the most general (“Category”) to the most specific (“Item ID”).
• For an example application of this concept, see transaction table300 ofFIG. 3, specificallytransaction2. Using the example technique discussed above for applying value share rules to a mobile transaction, Rules A and B could be applied totransaction2. However, consider embodiments in which the most specific match of transaction parameter values to rule parameter values is used to determine which rule to apply. With reference to Rule A,transaction2 matches the “Category” and “MO” rule parameter values. With reference to Rule B, however,transaction2 matches the “Category,” “MO,” and “PmtType” rule parameter values. Thus, Rule B is the more specific match and is applied totransaction2.
Example Methods
• FIG. 5 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof In at least some embodiments, the method can be implemented by software executing or executable to configure value share rules. For example, the method can be implemented in some embodiments via data entry into theconfiguration user interface122 via the example computing device shown and described below inFIG. 7.
• Step500 receives rule parameters and rule parameter values for a value share rule. Example rule parameters, rule parameter values, and value share rules are discussed above. Step502 receives a value share rate for the value share rule. Step504 generates the value share rule using the rule parameters, rule parameter values, and the value share rate. According to some embodiments, the value share rule can be configured by activating the applybutton222 of theconfiguration user interface122. Step506 processes mobile transactions using the value share rule. According to some embodiments, a mobile transaction can be processed using one or more of the techniques discussed above to determine a value share rate and/or amount for the mobile transaction.
• Step508 reconfigures the value share rule. In some embodiments, a value share rule can be reconfigured via input to a graphical interface (e.g., the configuration user interface122) and/or by changing one or more of the rule parameters, the rule parameter values, or the value share rate for the value share rule. Thus, in some embodiments, a value share rule can be dynamically reconfigured “on-the-fly” without having to remove the value share rule from service during the reconfiguration process. Step510 processes mobile transactions based on the reconfigured value share rule.
• FIG. 6 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof In at least some embodiments, the method can be implemented by software executing or executable (e.g., utilizing the transaction processor120) to process mobile transactions.
• Step600 receives information about a mobile transaction. According to some embodiments and with reference toenvironment100 discussed above, thetransaction processor120 can receive information about a mobile transaction by pulling the information from thetransaction store118. Step602 analyzes the information about the mobile transaction to determine transaction parameter values for the mobile transaction. Step604 determines an appropriate value share rule to apply to the mobile transaction based on the transaction parameter values. Example ways of determining an appropriate value share rule for a particular mobile transaction are discussed above.
• Step606 applies the appropriate value share rule to the mobile transaction based on the transaction parameter values to determine a value share rate. Example ways of applying an appropriate value share rule to a particular mobile transaction are discussed above. While the embodiments mentioned above are discussed with reference to a single value share rate and/or a value share for a single entity, this is not intended to be limiting. In some embodiments, a value share rule can specify multiple different value share rates for multiple entities. Step608 determines a value share amount for an entity based on the value share rate. For example, in some embodiments the value share rate represents a percentage value. In these embodiments, the percentage value can be applied to a purchase amount for the mobile transaction to determine the value share amount (e.g., a percentage of the purchase amount) for an entity.
• Step610 reports the value share amount for the entity. For example, according to some embodiments the value share amount can be reported to a financial service or financial institution which can credit the entity with the value share amount.
Example System
• FIG. 7 illustrates anexample computing device700 that can implement various embodiments described above.Computing device700 includes one or more processors orprocessing units702, one or more memory and/orstorage components704, one or more input/output (I/O)devices706, and abus708 that allows the various components and devices to communicate with one another.Bus708 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.Bus708 can include wired and/or wireless buses.
• Memory/storage component704 represents one or more computer storage media.Component704 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth).Component704 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).
• One or more input/output devices706 allow a user to enter commands and information tocomputing device700, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a touch input device (e.g., a touch screen), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.
• Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer storage media”.
• “Computer storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. The term “computer storage media” expressly excludes signals per se.
Conclusion
• Various embodiments provide techniques for determining a value share of a mobile transaction for one or more entities associated with the mobile transaction. Examples of mobile transactions include purchases of content such as applications, games, video, audio, graphics, and so on. In one or more embodiments, value share rules are created that each specify a share of a transaction value (e.g., a percentage of revenue generated from a purchase of content) that an entity involved in a particular mobile transaction is credited with. In one example scenario, a user of a mobile device purchases an application for the mobile device. A value share rule can be applied to the application purchase amount to determine a share of the application purchase amount that is to be credited to a mobile operator that provides service for the mobile device.
• Although the subject matter has been described in language specific to structural features and/or methodological steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as example forms of implementing the claimed subject matter.

Claims (20)

1. A computer-implemented method comprising:

receiving rule parameters and rule parameter values;

receiving a value share rate; and

generating a value share rule using the rule parameter values and the value share rate, the value share rule indicating a value share for a mobile transaction.

2. A computer-implemented method as recited inclaim 1, wherein one or more of the rule parameters, the rule parameter values, or the value share rate are received via user input to a graphical user interface.

3. The computer-implemented method ofclaim 2, wherein the graphical interface is configured to manage value share rules for multiple different entities.

4. The computer-implemented method ofclaim 3, wherein the multiple different entities comprise a plurality of different mobile operators and a mobile marketplace host.

5. The computer-implemented method ofclaim 1, wherein the mobile transaction comprises a purchase of content via a mobile device.

6. The computer-implemented method ofclaim 5, wherein the content comprises one or more of an application, a game, video content, or audio content.

7. The computer-implemented method ofclaim 1, wherein the value share comprises a revenue share amount of a purchase of content as part of the mobile transaction.

8. The computer-implemented method ofclaim 1, further comprising:

receiving one or more mobile transaction parameters associated with the mobile transaction; and

determining the value share of the mobile transaction by applying the value share rule to the one or more mobile transaction parameters.

9. The computer-implemented method ofclaim 8, wherein the one or more mobile transaction parameters comprise one or more of a mobile operator associated with the mobile transaction, a payment type associated with the mobile transaction, or a category of content purchased as part of the mobile transaction.

10. A system comprising:

one or more processors; and

one or more computer-readable storage media storing computer-executable instructions that are executable by the one or more processors to cause the system to perform operations comprising:

receiving rule parameters, rule parameter values, and a value share rate via input to a graphical interface; and

generating a value share rule using the rule parameters, the rule parameter values, and the value share rate, the value share rule indicating a value share for a mobile transaction and the graphical interface being configured to enable the value share rule to be dynamically reconfigured.

11. The system ofclaim 10, wherein the mobile transaction comprises a purchase of content via a mobile device.

12. The system ofclaim 11, wherein the content comprises one or more of an application, a game, video content, or audio content.

13. The system ofclaim 10, wherein the value share comprises a revenue share amount of a purchase of content as part of the mobile transaction.

14. The system ofclaim 10, wherein the operations further comprise:

receiving one or more mobile transaction parameters associated with the mobile transaction; and

determining the value share of the mobile transaction by applying the value share rule to the one or more mobile transaction parameters.

15. The system ofclaim 14, wherein the one or more mobile transaction parameters comprise one or more of a mobile operator associated with the mobile transaction, a payment type associated with the mobile transaction, or a category of content purchased as part of the mobile transaction.

16. One or more computer-readable storage media storing computer-executable instructions that are executable by one or more processors to perform operations comprising:

receiving a change to one or more of a rule parameter, a rule parameter value, or a value share rate via input to a graphical interface; and

reconfiguring an existing value share rule for mobile transactions based on the change.

17. The one or more computer-readable storage media ofclaim 16, wherein one or more of the mobile transactions comprise a purchase of content via a mobile device.

18. The one or more computer-readable storage media ofclaim 16, wherein the reconfigured value share rule is applicable to determine a revenue share amount of a purchase of content as part of the mobile transaction.

19. The one or more computer-readable storage media ofclaim 16, wherein the operations further comprise:

receiving one or more mobile transaction parameters associated with a mobile transaction; and

determining a value share of the mobile transaction by applying the reconfigured value share rule to the one or more mobile transaction parameters.

20. The one or more computer-readable storage media ofclaim 19, wherein the one or more mobile transaction parameters comprise one or more of a mobile operator associated with the mobile transaction, a payment type associated with the mobile transaction, or a category of content purchased as part of the mobile transaction.

Images