[go: up one dir, main page]

WO2018111377A1 - Procédés de suivi d'historique de partage d'url d'un utilisateur - Google Patents

Procédés de suivi d'historique de partage d'url d'un utilisateur Download PDF

Info

Publication number
WO2018111377A1
WO2018111377A1 PCT/US2017/054008 US2017054008W WO2018111377A1 WO 2018111377 A1 WO2018111377 A1 WO 2018111377A1 US 2017054008 W US2017054008 W US 2017054008W WO 2018111377 A1 WO2018111377 A1 WO 2018111377A1
Authority
WO
WIPO (PCT)
Prior art keywords
url
user
revenue
computer readable
shared
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2017/054008
Other languages
English (en)
Inventor
Sabharipriya ARUMUGAM
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to CN201780017356.8A priority Critical patent/CN109074591A/zh
Publication of WO2018111377A1 publication Critical patent/WO2018111377A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0214—Referral reward systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0277—Online advertisement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • 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.
  • 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.
  • 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.
  • 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.
  • the method for tracking URL sharing history includes formatting the tracking URL.
  • the tracking URL is formatted according to one of several tracking URL formats.
  • the information that identifies the sharing user is indecipherable to a human reader.
  • the indecipherable information includes a unique identifier of a sharing user.
  • one of the tracking URL formats includes semi-obfuscation of the tracking URL.
  • the method for compensating includes compensating a plurality of users who each shared a URL which resulted 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 conceptually illustrates an electronic system with which some embodiments of the invention are implemented.
  • Some embodiments include a method for tracking URL sharing history of a user.
  • 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.
  • the method for tracking URL sharing history includes formatting the tracking URL.
  • the tracking URL is formatted according to one of several tracking URL formats.
  • the information that identifies the sharing user is indecipherable to a human reader.
  • the indecipherable information includes a unique identifier of a sharing user.
  • one of the tracking URL formats includes semi-obfuscation of the tracking URL.
  • Some embodiments include a method for compensating a user for revenue derived, at least in part, from URL sharing by the user.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • the process 100 proceeds to the next step at which the shared item is shown to or received by (at 120) another user.
  • the URL sharing occurs at some starting point, such as from a content publishing user.
  • 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.
  • 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.
  • the process 100 transitions to step 160, which is described in detail below.
  • 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.
  • the process 100 transitions to step 160, which is described in detail below.
  • 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.
  • 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.
  • 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.
  • 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.
  • the receiving user also has a chance to share in revenue that is generated downstream from his or her own transaction.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a new URL is created that references the original URL and includes information about the first user.
  • the second user performs a revenue-generating activity.
  • 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).
  • a new renewed URL is created that references the original URL and includes information about the first user and the second user.
  • a third user visits the published content via the new renewed URL.
  • the third user performs a revenue-generating activity.
  • 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).
  • 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.
  • User2 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.
  • a revenue-generating action such as buying the recipe or clicking on an advertisement displayed nearby the recipe.
  • 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.
  • the same process can be repeated for re-sharing and regeneration of the URL over and over again.
  • 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.
  • 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.
  • constraints may be set which limit the number of times the process can be repeated after prior sharing and regeneration of the URL.
  • the regenerated URL tracks a limit of the first N users to share the URL, or the last N users to share the URL.
  • 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.
  • 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.
  • 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.
  • 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.
  • the content owner 305 publishes (along arrow 330) the content to the website that is accessible via the original URL 325a.
  • identifying information of the content owner and users who share the URL is instrumental to tracking the URL sharing history.
  • 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.
  • 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").
  • 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.
  • the content owner or publisher or website that received the revenue
  • shares a portion of 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.
  • 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.
  • the second user 315 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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).
  • the third user 320 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.
  • 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.
  • multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions.
  • multiple software inventions can also be implemented as separate programs.
  • any combination of separate programs that together implement a software invention described here is within the scope of the invention.
  • 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.
  • FIG. 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.
  • the bus 405 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 400.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the invention's processes are stored in the system memory 415, the permanent storage device 425, and/or the read-only 420.
  • 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.
  • 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.
  • CTR cathode ray tubes
  • LCD liquid crystal displays
  • bus 405 also couples electronic system 400 to a network 440 through a network adapter (not shown).
  • 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.
  • 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).
  • 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).
  • 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.
  • RAM random access memory
  • ROM read-only compact discs
  • CD-R recordable compact discs
  • CD-RW rewritable compact discs
  • read-only digital versatile discs e.g., DVD-ROM, dual-layer DVD-ROM
  • flash memory e.g., SD
  • 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.
  • 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.
  • each process could be implemented using several sub-processes, or as part of a larger macro process.
  • the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.
  • 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Game Theory and Decision Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne des procédés de suivi de l'historique d'un utilisateur de partage d'URL/liaison et de compensation de l'utilisateur pour un revenu dérivé d'URL/liaison partagé. Auparavant, aucun des utilisateurs qui ont partagé l'URL n'est toujours payé n'importe quelle partie du revenu généré à partir de la liaison partagée. Des modes de réalisation de la présente invention créent une URL personnalisée lorsqu'un utilisateur partage une URL. Ceci permet le suivi de l'URL partagée de l'utilisateur et la compensation pour l'utilisateur si un revenu est généré à partir de l'URL.
PCT/US2017/054008 2016-12-15 2017-09-28 Procédés de suivi d'historique de partage d'url d'un utilisateur Ceased WO2018111377A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780017356.8A CN109074591A (zh) 2016-12-15 2017-09-28 用于追踪用户的url分享历史的方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662434800P 2016-12-15 2016-12-15
US62/434,800 2016-12-15
US201715499699A 2017-04-27 2017-04-27
US15/499,699 2017-04-27

Publications (1)

Publication Number Publication Date
WO2018111377A1 true WO2018111377A1 (fr) 2018-06-21

Family

ID=62559049

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/054008 Ceased WO2018111377A1 (fr) 2016-12-15 2017-09-28 Procédés de suivi d'historique de partage d'url d'un utilisateur

Country Status (2)

Country Link
CN (1) CN109074591A (fr)
WO (1) WO2018111377A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10474323B2 (en) 2016-10-25 2019-11-12 Microsoft Technology Licensing Llc Organizational external sharing of electronic data
US10547621B2 (en) 2016-11-28 2020-01-28 Microsift Technology Licensing, Llc Persistent mutable sharing of electronic content
US11283799B2 (en) 2018-12-28 2022-03-22 Microsoft Technology Licensing, Llc Trackable sharable links
WO2023272734A1 (fr) * 2021-07-02 2023-01-05 叶立三 Procédé et appareil de transfert de valeur de nombre de parts d'un matériel protégé par le droit d'auteur, dispositif électronique et support de stockage

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114745421B (zh) * 2022-03-30 2023-10-10 北京奇艺世纪科技有限公司 裂变路径数据的记录方法、装置、服务器及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070219863A1 (en) * 2006-03-20 2007-09-20 Park Joseph C Content generation revenue sharing
US20120059722A1 (en) * 2010-09-02 2012-03-08 Yahoo! Inc. System and method for monetizing user-generated web content
US20140100944A1 (en) * 2012-10-09 2014-04-10 Share This Inc. Method and system for online campaign optimization
US20160021201A1 (en) * 2014-07-15 2016-01-21 Aol Inc. Systems and methods for tracking sharing of web content
US20160316032A1 (en) * 2015-04-27 2016-10-27 International Business Machines Corporation Tracking content sharing across a variety of communications channels

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070294088A1 (en) * 2006-05-31 2007-12-20 Big Fish Games, Inc Network Service Recruitment Architecture
CN102360480B (zh) * 2011-10-06 2017-06-16 浙江易网科技股份有限公司 一种链接网上支付及记录链接的方法和系统
CN103854207A (zh) * 2014-03-11 2014-06-11 马云起 一种网络报酬分配系统及方法
CN104200377A (zh) * 2014-08-28 2014-12-10 北京金和软件股份有限公司 用于从移动应用中产生收益和分享收益的方法
CN105741141A (zh) * 2016-02-02 2016-07-06 吴锦锋 一种基于互联网的广告推广方法及其装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070219863A1 (en) * 2006-03-20 2007-09-20 Park Joseph C Content generation revenue sharing
US20120059722A1 (en) * 2010-09-02 2012-03-08 Yahoo! Inc. System and method for monetizing user-generated web content
US20140100944A1 (en) * 2012-10-09 2014-04-10 Share This Inc. Method and system for online campaign optimization
US20160021201A1 (en) * 2014-07-15 2016-01-21 Aol Inc. Systems and methods for tracking sharing of web content
US20160316032A1 (en) * 2015-04-27 2016-10-27 International Business Machines Corporation Tracking content sharing across a variety of communications channels

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10474323B2 (en) 2016-10-25 2019-11-12 Microsoft Technology Licensing Llc Organizational external sharing of electronic data
US10547621B2 (en) 2016-11-28 2020-01-28 Microsift Technology Licensing, Llc Persistent mutable sharing of electronic content
US11283799B2 (en) 2018-12-28 2022-03-22 Microsoft Technology Licensing, Llc Trackable sharable links
WO2023272734A1 (fr) * 2021-07-02 2023-01-05 叶立三 Procédé et appareil de transfert de valeur de nombre de parts d'un matériel protégé par le droit d'auteur, dispositif électronique et support de stockage

Also Published As

Publication number Publication date
CN109074591A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
US11023941B2 (en) Managing ecommerce messages via a social networking system
JP6991211B2 (ja) デバイスおよびシステムに依存しない電子支払トークンの提供
JP5849300B2 (ja) 口座管理方法、口座管理システム、および記録媒体
WO2018111377A1 (fr) Procédés de suivi d'historique de partage d'url d'un utilisateur
US20210166259A1 (en) System and method for providing enhanced rewards to customers
US9430784B1 (en) System for E-commerce accessibility
US10521819B2 (en) Systems and methods for analytics in a cooperative data exchange
US20120323695A1 (en) Lead Generation Platform
US20130282455A1 (en) Method, system, and computer program for referring goods and services via a social media feed
US10970356B2 (en) Autonomous and dynamic generation of a living website for continuous user engagement
KR20170129706A (ko) 소셜 네트워킹 시스템을 통한 판매자와의 사용자 통신
JP2007226794A (ja) インスタント・メッセージング環境で安全な金融取引を行なう装置および方法、ならびにそのためのコンピュータ・プログラム
US11288642B1 (en) Systems and methods for online payment transactions
US12242645B2 (en) Data privacy architecture, systems, and methods
US10762554B2 (en) Framed implementation for payment widgets
KR102514322B1 (ko) 다중 상환 체계의 세분화
US20140351096A1 (en) Techniques for facilitating acquisition and exchange of ebook and other digital content via a computer network
US20140108129A1 (en) Determining the effectiveness of an advertisement on a website or mobile device
US20140089072A1 (en) Posting purchase information
US10832357B1 (en) Real estate transaction facilitating process and incoming property offer notification system
US20150170227A1 (en) Assessing ratings using tip patterns
WO2019135851A1 (fr) Accès en temps réel sécurisé à une base de données de mesures incitatives
US20180336601A1 (en) Securitization of Virtual Objects
US11328374B1 (en) System and process for converting an unbranded virtual tour of a real estate listing into a branded virtual tour of the real estate listing enhanced with branding, contact, and marketing information
Hanoglu A Cookieless Future: Solving the UX Problems Caused by the Privacy Protections Method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17880711

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17880711

Country of ref document: EP

Kind code of ref document: A1