WO2018111377A1

WO2018111377A1 - Methods for tracking url sharing history of a user

Info

Publication number: WO2018111377A1
Application number: PCT/US2017/054008
Authority: WO
Inventors: Sabharipriya ARUMUGAM
Original assignee: Individual
Current assignee: Individual
Priority date: 2016-12-15
Filing date: 2017-09-28
Publication date: 2018-06-21
Anticipated expiration: 2019-06-15
Also published as: CN109074591A

Abstract

This invention relates to methods for tracking a user's history of URL/link sharing and compensating the user for shared URL/link derived revenue. Previously none of the users who have shared the URL are ever paid any portion of the revenue generated from the link shared. Embodiments of the present invention create a customized URL when a user shares a URL. This enables tracking of the user's shared URL and compensation for the user if revenue is generated from the URL.

Description

METHODS FOR TRACKING URL SHARING HISTORY OF A USER

TECHNICAL FIELD

[0001] Embodiments of the invention described in this specification relate generally to tracking user activity online, and more particularly, to methods for tracking a user's history of URL/link sharing and compensating the user for shared URL/link derived revenue.

BACKGROUND ART

[0002] Many people enjoy sharing information or resources from online websites. For example, a person (or "user") who searches online for cooking techniques, recipes, or other matters related to cooking may find a particular recipe that the user would like to share with others. Users typically just share the URL/link (hereinafter referred to as "URL") with others via email, social media, or some other manner.

[0003] While URL sharing is common for many users, there are times when shared URLs lead to revenue generation for another entity. However, none of the users who have shared the URL are ever paid any portion of the revenue, despite an arguable case that their URL sharing activity somehow played a part in the newly generated revenue. Nothing exists for tracking URL sharing by users in a way that focuses on revenue generation and distribution.

[0004] Therefore, what is needed is a way to track a user's history of URL sharing and to compensate the user for their URL sharing which leads to revenue generation.

DISCLOSURE OF THE INVENTION

[0005] Some embodiments of the invention include novel methods for tracking URL sharing history of a user and compensating the user for revenue derived, at least in part, from the URL sharing by the user. In some embodiments, when a shared URL results in revenue generation, the revenue is shared with the users that shared the URL, in a way that tracks a chain of sharing the URL from a first sharing of the URL by a first user through a plurality of subsequent sharing of the URL by a plurality of other users.

[0006] In some embodiments, the method for tracking URL sharing history includes receiving an initial URL to share and generating a tracking URL comprising information that identifies the initial URL and information that identifies the sharing user. In some embodiments, the method for tracking URL sharing history includes formatting the tracking URL. In some embodiments, the tracking URL is formatted according to one of several tracking URL formats. In some embodiments, the information that identifies the sharing user is indecipherable to a human reader. In some embodiments, the indecipherable information includes a unique identifier of a sharing user. In some embodiments, one of the tracking URL formats includes semi-obfuscation of the tracking URL.

[0007] In some embodiments, the method for compensating includes compensating a plurality of users who each shared a URL which resulted in revenue generation or another recognizable benefit. In other words, when a shared URL ends up in revenue generation or another recognizable benefit, the method for compensating shares the revenue (or other recognizable benefit) with those users who shared the URL.

[0008] The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this specification. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description, and Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description, and Drawings, but rather are to be defined by the appended claims, because the claimed subject matter can be embodied in other specific forms without departing from the spirit of the subject matter.

BRIEF DESCRIPTION OF THE FIGURES

[0009] Having thus described the invention in general terms, reference is now made to the accompanying drawings, which are not necessarily drawn to scale, and which show different views of different example embodiments.

[0010] Figure 1 conceptually illustrates a high level process for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity in some embodiments.

[0011] Figure 2 conceptually illustrates a detailed URL history tracking and compensation sharing process for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity in some embodiments. [0012] Figure 3 includes a block diagram that conceptually illustrates tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity in some embodiments.

[0013] Figure 4 conceptually illustrates an electronic system with which some embodiments of the invention are implemented.

BEST MODE OF THE INVENTION

[0014] In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention can be adapted for any of several applications.

[0015] Some embodiments include a method for tracking URL sharing history of a user. In some embodiments, the method for tracking URL sharing history includes receiving an initial URL to share and generating a tracking URL comprising information that identifies the initial URL and information that identifies the sharing user. In some embodiments, the method for tracking URL sharing history includes formatting the tracking URL. In some embodiments, the tracking URL is formatted according to one of several tracking URL formats. In some embodiments, the information that identifies the sharing user is indecipherable to a human reader. In some embodiments, the indecipherable information includes a unique identifier of a sharing user. In some embodiments, one of the tracking URL formats includes semi-obfuscation of the tracking URL.

[0016] Some embodiments include a method for compensating a user for revenue derived, at least in part, from URL sharing by the user. In some embodiments, the method for compensating includes compensating a plurality of users who each shared a URL which resulted in revenue generation. In other words, when a shared URL ends up in revenue generation, the method for compensating shares the revenue with those users who shared the URL.

[0017] In some embodiments, when a shared URL results in revenue generation, the revenue is shared with the users that shared the URL, in a way that tracks a chain of sharing the URL from a first sharing of the URL by a first user through a plurality of subsequent sharing of the URL by a plurality of other users.

[0018] In this specification, there are descriptions of processes or methods that are performed by software running on one or more computing devices (e.g., a desktop computer, a server, a laptop, a tablet computing device, a smartphone, a distributed network of computing devices, a customized computer architecture augmented by a specialized software application, etc.) to track URL sharing history of users and compensate the users for revenue derived from the URL sharing activity. In some cases, multiple software modules are deployed on multiple computing devices (both locally networked and inter-networked via distributed computing and/or cloud computing services). For the purposes of the embodiments described in this specification, the word "method" is used interchangeably with the word "process". Methods are described, therefore, by reference to example processes that conceptually illustrate process steps for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity.

[0019] Several more detailed embodiments are described below. Section I describes several processes for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity. Section II describes an electronic system that implements some embodiments of the invention.

I. TRACKING URL SHARING HISTORY AND SHARING REVENUE DERIVED FROM URL SHARING ACTIVITY

[0020] As stated above, many users enjoy sharing online information that can be referenced by a URL. While such users have several manners and methods to share URLs, nothing exists to track URL sharing history of a user and compensate the user for URL sharing when the shared URL leads to generation of revenue. Embodiments of the methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived, at least in part, from the URL sharing by the user described in this specification solve such problems by technical improvements that allow for sharing an original URL by generation of a new URL based on changing the original URL with semi- obfuscated information about the sharing user and about the original URL (and about intervening sharing users, if any). The semi-obfuscated information is indecipherable to a human reader, but can be understood by a computing device architecture that is, at least in part, customized by one or more computer program implementations of methods and processes described in this specification. In this way, the new URL can be used to find out who shared the original URL.

[0021] By way of example, Figure 1 conceptually illustrates a high level process 100 for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity in some embodiments. As shown in this figure, the high level process 100 starts when a user shares (at 110) a URL or address of an Intemet resource (referred to as the "shared item" in the description of Figure 1). The user may share the shared item automatically via a program or manually. After the shared item is shared, the process 100 proceeds to the next step at which the shared item is shown to or received by (at 120) another user. As described above, the URL sharing occurs at some starting point, such as from a content publishing user. However, for the purposes of this example, any user— whether the publishing user or not— can initiate the sharing of the URL in the context of URL tracking and sharing compensation for downstream revenue generation.

[0022] Next, the high level process 100 of some embodiments determines (at 130) whether the receiving user of the shared item has performed some action via the shared item. For instance, the receiving user may have donated money to a campaign at a campaign website hosted at the shared URL or purchased a product at an e-commerce website hosted at the shared URL. When the high level process 100 negatively determines (at 130) that the receiving user has not performed an action via the shared item, then the process 100 transitions to step 160, which is described in detail below.

[0023] On the other hand, when the high level process 100 affirmatively determines (at 130) that the receiving user has performed an action via the shared item, then the high level process 100 proceeds to the next step to determine (at 140) whether the action performed via the shared item resulted in revenue generation. When the high level process 100 negatively determines (at 140) that the action performed via the shared item did not result in revenue generation, then the process 100 transitions to step 160, which is described in detail below. For example, the action by the receiving user may have been to donate money to a campaign or time to a charitable cause, which does not result in revenue generation.

[0024] However, when the high level process 100 affirmatively determines (at 140) that the action performed by the receiving user via the shared item resulted in revenue, then the high level process 100 continues to the next step at which the user who shared the shared item gets (at 150) a share of the revenue. For example, the action by the receiving user may have been to purchase a product through an e-commerce website hosted at the URL of the shared item, resulting in revenue generation for the owner of the e-commerce website. In this case, the user who shared the shared item with the receiving user (who performed the action which resulted in revenue generation) receives a share of the revenue generated.

[0025] The receiving user also has a chance to share in revenue that is generated downstream from his or her own transaction. In other words, the receiving user can also forward (or rather, "re-share") the shared item to one or more other users who may engage in some revenue generating action in relation to the re-shared item. In some embodiments, the high level process 100 checks for this by determining (at 160) whether the receiving user has re-shared the shared item. When the high level process 100 affirmatively determines (at 160) that the receiving user has re-shared the shared item with at least one other user, then the high level process 100 returns to step 120 where the re-shared item is shown to/received by the other user(s). The process 100 then proceeds according to the steps described above. On the other hand, when the high level process 100 negatively determines (at 160) that the receiving user has not re-shared the shared item with any other user, then the process 100 ends.

[0026] Embodiments of the methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived, at least in part, from the URL sharing by the user described in this specification differ from and improve upon currently existing options. In particular, some embodiments differ because the existing methods can be easily altered to include any other user than the original user who shares an URL. This would defeat one of the primary advantages in revenue sharing systems, being that accurate tracking of who gets part of the revenue would not be possible. In contrast, the format of the new URL created by the methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived from the URL sharing by the user when a user shares the URL with others is indecipherable to a human user and would not be able to be altered in a way that replaces original and/or sharing users with other users.

[0027] The methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived from the URL sharing by the user of the present disclosure may be comprised of the following steps. This list of possible constituent steps is intended to be exemplary only and it is not intended that this list be used to limit the methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived from the URL sharing by the user of the present application to just these steps. Persons having ordinary skill in the art relevant to the present disclosure may understand there to be equivalent steps that may be substituted within the present disclosure without changing the essential function or operation of the methods and processes for tracking URL sharing history of a user and compensating the user for revenue derived from the URL sharing by the user.

[0028] 1. Content owner publishes content.

[0029] 2. A first user visits the published content.

[0030] 3. The first user shares a URL to the published content.

[0031] 4. A new URL is created that references the original URL and includes information about the first user.

[0032] 5. A second user visits the published content via the new URL.

[0033] 6. The second user performs a revenue-generating activity.

[0034] 7. Content owner is distributed portion of the revenue and the first user is distributed another portion of the revenue for the URL sharing activity (or generally, one or more "parties" involved in the transaction).

[0035] 8. The second user shares the new URL to the published content.

[0036] 9. A new renewed URL is created that references the original URL and includes information about the first user and the second user.

[0037] 10. A third user visits the published content via the new renewed URL.

[0038] 11. The third user performs a revenue-generating activity.

[0039] 12. Content owner is distributed portion of the revenue and the first user and second user are also distributed portions of the revenue for their URL sharing activity (or generally, one or more "parties" involved in the transaction).

[0040] The following descriptive example of tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity demonstrates the effectiveness of tracking URL sharing history when compensation can be shared. In this example, let us assume there is a recipe application, where a content owning and publishing user ("Content Owner 1 ") publishes new content— in this example, a recipe accessible via a unique URL. After publication of the recipe at the unique URL, a viewing and sharing user ("Userl ") sees it and shares it with others (e.g., via email, instant message, social network, etc). During the sharing process a new URL is generated. The newly generated URL will have information that relates back to the original unique URL and information to track Userl who shared the original unique URL.

[0041] Now some other user ("User2") receives/views the newly generated URL that was shared by Userl, clicks on the newly generated URL (which is merely a shared URL from the perspective of User2) to view/get the details of the recipe. After accessing the recipe via the newly generated URL, User2 performs a revenue-generating action, such as buying the recipe or clicking on an advertisement displayed nearby the recipe. While the shared URL can be viewed without triggering a commercial transaction or revenue generation, we can see in this example that User2 has gone beyond mere viewing of the recipe to actually perform some action that results in revenue generation. Since Userl shared the recipe URL with User2, it is Userl who played an instrumental role in generation of the revenue when User2 made the revenue-generating action. This is precisely the point of tracking the URL sharing history of a user and sharing a portion of the revenue with the user who shared the URL associated with the recipe. In other words, since User2 was brought to the original URL via the newly generated URL that was shared by Userl, the content owner or the website/application owner shares a portion/percentage of the revenue with Userl.

[0042] The same process can be repeated for re-sharing and regeneration of the URL over and over again. For example, User2 may re-share the URL, in which case a new/renewed URL will be generated once again. This new/renewed URL will have enough info to retrieve all of the prior sharing users' history (i.e., Userl and User2) and will include information about the original URL of the site at which the original recipe was published by Content Owner 1. Then, when another user ("User3") accesses the new/renewed URL, the recipe is viewed. If User3 performs a commercial transaction or a revenue-generating action, the Content Owner 1 benefits by receiving the revenue, but also a percentage of the revenue would then be shared with Userl and/or User2. In some implementations, constraints may be set which limit the number of times the process can be repeated after prior sharing and regeneration of the URL. For example, the regenerated URL tracks a limit of the first N users to share the URL, or the last N users to share the URL.

[0043] By way of example, Figure 2 conceptually illustrates a detailed URL history tracking and compensation sharing process 200 for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity in some embodiments. The steps of the detailed URL history tracking and compensation sharing process 200 are described by reference to Figure 3, which includes a block diagram 300 that conceptually illustrates tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity.

[0044] In some embodiments, the URL history tracking and compensation sharing process 200 starts when a content owner publishes (at 210) content in relation to some URL or Internet-accessible resource. The published content is made accessible to other users by its address, specifically, its URL.

[0045] Turning to Figure 3, the block diagram 300 includes a content owner 305, a first user 310, a second user 315, a third user 320, a plurality of websites/applications 325, an original URL 325a of a website with the published content, a shared URL 325b of the website, and a re-shared URL 325c of the website with the published content. As shown in this figure, the content owner 305 publishes (along arrow 330) the content to the website that is accessible via the original URL 325a. The original URL 325a of the website with the published content includes identifying information of the content owner. The shared URL 325b of the website with the published content includes the identifying information of the content owner and identifying information of the second user 315 sharing the URL. The re- shared URL 325 c of the website with the published content includes the identifying information of the content owner, the identifying information of the second user 315 who shared the URL, and identifying information of the third user 320 re-sharing the URL.

[0046] As shown in Figure 3, the content owner 305 publishes (along arrow 330) the content to the website that is accessible via the original URL 325a. As the block diagram 300 demonstrates, identifying information of the content owner and users who share the URL is instrumental to tracking the URL sharing history.

[0047] Turning back to Figure 2, the URL history tracking and compensation sharing process 200 includes identifying information about the sharing user and includes the identifying information in the shared URL. This is shown by the URL history tracking and compensation sharing process 200 when a first user ("USER 1") visits the website with the content via the original URL and then generates (at 220) a new URL with USER l's identifying information included in the new URL. In some embodiments, the URL history tracking and compensation sharing process 200 then proceeds to the next step in which USER 1 shares (at 230) the newly generated URL in a format that includes USER l's identifying information (and retains the identifying information of the content publisher). The newly generated URL is shared by USER 1 with at least USER 2, but possibly several other users. However, for purposes of this example and so as not to obscure the description of the process 200 with unnecessary detail, the following steps of the process 200 are described by reference to a specific receiving user of the URL generated by USER l's sharing, namely, USER 2.

[0048] The URL history tracking and compensation sharing process 200 follows with a step in which USER 2 accesses (at 240) the URL that USER 1 shared ("shared URL"). At the next step of the URL history tracking and compensation sharing process 200, USER 2 uses the shared URL to reach (at 250) the original website/resource. Any revenue generating activity by USER 2 in relation to the original content on the original website/resource accessed by the shared URL results in revenue payment to the content owner. In addition, as shown at the next step of URL history tracking and compensation sharing process 200, the content owner (or publisher or website that received the revenue) shares a portion of the revenue (at 255) with USER 1 in compensation for sharing the original URL with USER 2 who generated revenue.

[0049] Now referring to Figure 3, after the content owner 305 publishes (along arrow 330) the original content to the website referenced by original URL 325a, the first user 310 accesses (shown along arrow 335) the original content via the original URL 325a. If the first user 310 engages in some revenue generating activity in relation to the original content on the original website, the content owner 305 would then receive the full revenue.

[0050] The first user 310 then shares the original content of the website (the original URL 325a) with the second user 315. This sharing action by the first user 310 automatically triggers the generation (shown along arrow 340) of a new shared URL 325b which the second user 315 receives (instead of the original URL 325a) when the first user 310 shares the original URL 325a. The newly generated shared URL 325b refers back to the original content published by the content owner 305, but also includes identifying information of the first user 310, along with identifying information of the content owner.

[0051] Upon receiving the shared URL 325b (or shortly thereafter), the second user 315 uses the shared URL 325b (shown along arrow 345) to access the original content on the website (shown along arrow 350). If the second user 315 performed some action that generated revenue in relation to the original content, then the first user 310 would receive a portion of the revenue payed to the content owner 305, simply because the sharing action of the first user 310 could be tracked back from the shared URL 325b to the original URL 325a based on the second user 315 accessing the original content via the shared URL 325b.

[0052] Referring to Figure 2 again, the next step of the URL history tracking and compensation sharing process 200 is when USER 2 shares a newly generated URL that refers to the published content. USER 2 shares the newly generated URL with at least USER 3 and possibly other users. However, for purposes of this example and so as not to obscure the description of the process 200 with unnecessary detail, the following steps of the process 200 are described by reference to a specific receiving user of the URL generated by USER 2's sharing, namely, USER 3. Also, the newly generated URL is generated in one of the suitable formats (either based on the original URL alone or based on the shared URL received from USER 1). When USER 2 shares the newly generated URL with USER 3 (and other users), identifying information for USER 2 will automatically be added to the newly generated URL, such that USER 2's sharing of the newly generated URL can be traced back if USER 3 (or another user) performs revenue generating actions in relation to the original content. Therefore, the newly generated URL will only include identifying information of the content owner and USER 2 if the newly generated URL was based on the original URL, but will include identifying information of the content owner, USER 1, and USER 2 if based on the shared URL which USER 2 received from USER 1.

[0053] At the next step of the URL history tracking and compensation sharing process 200, USER 3 accesses (at 270) the newly generated URL received from USER 2. The USER 3 is able to reach the original content via the newly generated URL (at 280). If USER 3 performs actions that generate revenue in relation to the content, then payment would be made to the content owner. The next step of the URL history tracking and compensation sharing process 200 includes sharing revenue (at 285) between the content owner, publisher, or the website and USER 2 (and possibly USER 1). Specifically, the content owner, publisher, or website shares a portion of the received revenue with at least USER 2 and, if the newly generated URL was from USER l's sharing, USER 1. Then the URL history tracking and compensation sharing process 200 ends.

[0054] Turning back to Figure 3, the second user 315 shares the original content of the website with the third user 320 by sharing either the original URL 325a or the shared URL 325b. Again, the sharing action of the second user 315 automatically triggers the generation (shown along arrow 355) of another new shared URL 325c which the third user 320 receives (instead of the original URL 325a or the shared URL 325b). The new shared URL 325c refers back to the original content published by the content owner 305. Also, depending on whether the second user 320 shares the original URL 325a or the shared URL 325b, the new shared URL 325c either includes identifying information of the content owner and the second user 315 only (when the second user 315 has shared the original URL 325a) or includes identifying information of the content owner, the first user 310, and the second user 315 (when the second user 315 has shared the shared URL 325b).

[0055] Upon receiving the new shared URL 325c (or shortly thereafter), the third user 320 uses the new shared URL 325c (shown along arrow 360) to access the original content on the website (shown along arrow 365). If the third user 320 performed some action that generated revenue in relation to the original content, then the content owner 305 would receive the revenue and a portion of the revenue would be shared. Specifically, a portion of the revenue would be shared only with the second user 315 when the third user 320 accessed the content via the shared URL link from the second user 315 that was based on the original URL 325a. However, portions of the revenue would be shared with the first user 310 and the second user 315 when the third user 320 accessed the content via the shared URL link from the second user 315 that was based on the shared URL 325b received from the first user 310. II. ELECTRONIC SYSTEM

[0056] Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium or machine readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.

[0057] In this specification, the term "software" is meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.

[0058] Figure 4 conceptually illustrates an electronic system 400 with which some embodiments of the invention are implemented. The electronic system 400 may be a computer, phone, PDA, or any other sort of electronic device. Such an electronic system includes various types of computer readable media and interfaces for various other types of computer readable media. Electronic system 400 includes a bus 405, processing unit(s) 410, a system memory 415, a read-only 420, a permanent storage device 425, input devices 430, output devices 435, and a network 440.

[0059] The bus 405 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 400. For instance, the bus 405 communicatively connects the processing unit(s) 410 with the read-only 420, the system memory 415, and the permanent storage device 425.

[0060] From these various memory units, the processing unit(s) 410 retrieves instructions to execute and data to process in order to execute the processes of the invention. The processing unit(s) may be a single processor or a multi-core processor in different embodiments.

[0061] The read-only-memory (ROM) 420 stores static data and instructions that are needed by the processing unit(s) 410 and other modules of the electronic system. The permanent storage device 425, on the other hand, is a read-and- write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 400 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 425.

[0062] Other embodiments use a removable storage device (such as a floppy disk or a flash drive) as the permanent storage device 425. Like the permanent storage device 425, the system memory 415 is a read-and- write memory device. However, unlike storage device 425, the system memory 415 is a volatile read-and-write memory, such as a random access memory. The system memory 415 stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 415, the permanent storage device 425, and/or the read-only 420. For example, the various memory units include instructions for processing appearance alterations of displayable characters in accordance with some embodiments. From these various memory units, the processing unit(s) 410 retrieves instructions to execute and data to process in order to execute the processes of some embodiments.

[0063] The bus 405 also connects to the input and output devices 430 and 435. The input devices enable the user to communicate information and select commands to the electronic system. The input devices 430 include alphanumeric keyboards and pointing devices (also called "cursor control devices"). The output devices 435 display images generated by the electronic system 400. The output devices 435 include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some embodiments include devices such as a touchscreen that functions as both input and output devices.

[0064] Finally, as shown in Figure 4, bus 405 also couples electronic system 400 to a network 440 through a network adapter (not shown). In this manner, the computer can be a part of a network of computers (such as a local area network ("LAN"), a wide area network ("WAN"), or an intranet), or a network of networks (such as the Internet). Any or all components of electronic system 400 may be used in conjunction with the invention.

[0065] These functions described above can be implemented in digital electronic circuitry, in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be packaged or included in mobile devices. The processes may be performed by one or more programmable processors and by one or more set of programmable logic circuitry. General and special purpose computing and storage devices can be interconnected through communication networks.

[0066] Some embodiments include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine- readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra-density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

[0067] While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. For instance, Figures 1 and 2 conceptually illustrates processes for tracking URL sharing history of users and compensating the users for revenue derived from the URL sharing activity. The specific operations of each process may not be performed in the exact order shown and described. Specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Furthermore, each process could be implemented using several sub-processes, or as part of a larger macro process. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.

INDUSTRIAL APPLICABILITY

[0068] Embodiments of the disclosed invention can be useful for storing a URL history tracking and revenue compensation sharing program which, when executed by a processor of a computing device, tracks URL sharing history of users and compensates the users for revenue derived from the URL sharing activity.

Claims

WHAT IS CLAIMED IS :

1. A non-transitory computer readable medium storing a URL history tracking and revenue compensation sharing program which, when executed by a processor of a computing device, tracks URL sharing history of users and compensates the users for revenue derived from the URL sharing activity, said URL history tracking and revenue compensation sharing program comprising sets of instructions for:

receiving an action from a first user to share content published by a content owner and associated with an original URL;

generating a first shared URL comprising information related to the original URL and information that identifies the first user;

receiving a revenue-generating action from a second user who accessed the content by way of the first shared URL; and

compensating the content owner and the first user based on the revenue-generating action from the second user.

2. The non-transitory computer readable medium of claim 1, wherein the set of instructions for generating the first shared URL comprises sets of instructions for:

generating a unique identifier associated with the first user; and

adding the unique identifier to the original URL.

3. The non-transitory computer readable medium of claim 2, wherein the set of instructions for generating the unique identifier associated with the first user comprises a set of instructions for obfuscating the unique identifier.

4. The non-transitory computer readable medium of claim 3, wherein the obfuscated unique identifier associated with the first user is indiscernible to a human reader.

5. The non-transitory computer readable medium of claim 1 , wherein the URL history tracking and revenue compensation sharing program further comprises sets of instructions for:

receiving an action from the second user to share the content published by the content owner and associated with the first shared URL and the original URL; and

generating a second shared URL comprising information related to the original URL, information related to the first shared URL, information that identifies the first user, and information that identifies the second user.

6. The non-transitory computer readable medium of claim 5, wherein the URL history tracking and revenue compensation sharing program further comprises sets of instructions for:

receiving a revenue-generating action from a third user who accessed the content by way of the second shared URL; and

compensating the content owner, the first user, and the second owner based on the revenue-generating action from the third user.

7. The non-transitory computer readable medium of claim 1, wherein the revenue-generating action from the second user comprises a selection of an advertisement.

8. The non-transitory computer readable medium of claim 1, wherein the revenue-generating action from the second user comprises a payment to the content owner.

9. The non-transitory computer readable medium of claim 1, wherein the URL history tracking and revenue compensation sharing program further comprises sets of instructions for:

receiving an action from a third user to share the content published by the content owner and associated with the original URL;

generating a third shared URL comprising information related to the original URL and information that identifies the third user;

receiving a revenue-generating action from a fourth user who accessed the content by way of the third shared URL; and

compensating the content owner and the third user based on the revenue-generating action from the third user.

10. The non-transitory computer readable medium of claim 1, wherein the URL history tracking and revenue compensation sharing program further comprises a set of instructions for limiting a number of times that the URL can be shared with others.

11. The non-transitory computer readable medium of claim 1, wherein the content owner is a product vendor; wherein the revenue-generating action is purchasing a product from the product vendor.

12. The non-transitory computer readable medium of claim 11, wherein the product is at a URL owned by the content owner than the first shared URL.

13. The non-transitory computer readable medium of claim 1, wherein the revenue-generating action is loading content of the content owner.

14. The non-transitory computer readable medium of claim 1, wherein the revenue-generating action is viewing a video advertisement.

15. The non-transitory computer readable medium of claim 14, wherein the video advertisement is viewed on a remote device from the device displaying the first URL; wherein the process further comprises: creating a first code on the device that is communicated to the remote device; creating a second code on the remote device that is communicated to the device; and authenticating the first code on the remote device while authenticating the second code on the device.

16. The non-transitory computer readable medium of claim 1, wherein the revenue-generating action is listening to an audio advertisement.

17. The non-transitory computer readable medium of claim 1, wherein the audio advertisement is viewed on a remote device from the device displaying the first URL; wherein the process further comprises: creating a first code on the device that is communicated to the remote device; creating a second code on the remote device that is communicated to the device; and authenticating the first code on the remote device while authenticating the second code on the device.

18. The non-transitory computer readable medium of claim 1, wherein the first user is compensated with a voucher.

19. The non-transitory computer readable medium of claim 18, wherein the voucher is converted into a credit for services.

20. The non-transitory computer readable medium of claim 18, wherein the voucher is converted into cash.

21. The non-transitory computer readable medium of claim 18, wherein the voucher is points based award credit.