CA2682967A1 - Consumership-based distribution - Google Patents
Consumership-based distribution Download PDFInfo
- Publication number
- CA2682967A1 CA2682967A1 CA2682967A CA2682967A CA2682967A1 CA 2682967 A1 CA2682967 A1 CA 2682967A1 CA 2682967 A CA2682967 A CA 2682967A CA 2682967 A CA2682967 A CA 2682967A CA 2682967 A1 CA2682967 A1 CA 2682967A1
- Authority
- CA
- Canada
- Prior art keywords
- entity
- distributorship
- action
- acquiring
- distribution
- 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.)
- Abandoned
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/06—Buying, selling or leasing transactions
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A method of distribution comprises providing a distributorship data storage for storing a plurality of consumer distributorship records and providing an order processing unit for processing each consumership acquiring order which involves a distributing member, a distributee and a distributed product or service entity and causes the consumership of said entity to be distributed from said distributing member to said distributee, wherein said order is processed by affirming said distributee's consumer distributorship of said distributed entity and making a commission payment to said distributing member if said distributing member is a distributor of said distributed entity.
Description
CONSUMERSHIP-BASED DISTRIBUTION
1. FIELD OF INVENTION
The present invention relates to distribution, and more particularly, consumership-based distribution.
1. FIELD OF INVENTION
The present invention relates to distribution, and more particularly, consumership-based distribution.
2. BACKGROUND
Ownerships and userships are two major categories of consumerships.
Conventionally, neither ownerships nor userships have any inherent connections with distributorships.
A person's ownership of a product is deemed when the person makes a purchase of the product or receives the product as a gift, but such ownership is not automatically equated with the person's commissioned distributorship of the product. A person's usership of a product or service is deemed when the person pays for the usage of the product or service or receives the usage right of the product or service as a gift, but such usership is not automatically equated with the person's commissioned distributorship of the product or service. Thus far, none of the existing e-commerce systems, gifting systems and service provisioning systems automatically equates consumerships with commissioned consumer distributorships.
On the contrary, this invention equates authentic consumerships with corresponding commissioned consumer distributorships. More specifically, this invention equates authentic ownerships with corresponding owner distributorships and authentic userships with corresponding user distributorships.
The main object of this invention is to provide a computer-implemented mechanism of consumership-based distribution in which, for each consumership acquiring distribution of a product or service from a distributing member to a distributee, the distributee is affirmed a consumer distributorship of said product or service, and the distributing member is paid a commission if said distributing member is a distributor of said product or service. Accordingly, several advantages of this invention are:
(a) Consumer distributorships provide each authentic owner or user a moneymaking opportunity for each authentically owned or used product or service. Thus a passive product or service being authentically purchased, gifted or used becomes an active money-growing asset for commissioned distributions.
(b) Consumer distributorships are permanent during the life cycles of the associated products or services. Thus a product or service consumership is acquired once and distributed repeatedly.
(c) Consumership-based distribution enables a new and efficient distribution framework for distributing products and services, in which suppliers can reach new consumers either directly or via distributors who are existing consumers, thus cutting out all the middlemen and intermediaries.
Further objects and advantages of this invention will become apparent from a consideration of the drawings and ensuring description.
Ownerships and userships are two major categories of consumerships.
Conventionally, neither ownerships nor userships have any inherent connections with distributorships.
A person's ownership of a product is deemed when the person makes a purchase of the product or receives the product as a gift, but such ownership is not automatically equated with the person's commissioned distributorship of the product. A person's usership of a product or service is deemed when the person pays for the usage of the product or service or receives the usage right of the product or service as a gift, but such usership is not automatically equated with the person's commissioned distributorship of the product or service. Thus far, none of the existing e-commerce systems, gifting systems and service provisioning systems automatically equates consumerships with commissioned consumer distributorships.
On the contrary, this invention equates authentic consumerships with corresponding commissioned consumer distributorships. More specifically, this invention equates authentic ownerships with corresponding owner distributorships and authentic userships with corresponding user distributorships.
The main object of this invention is to provide a computer-implemented mechanism of consumership-based distribution in which, for each consumership acquiring distribution of a product or service from a distributing member to a distributee, the distributee is affirmed a consumer distributorship of said product or service, and the distributing member is paid a commission if said distributing member is a distributor of said product or service. Accordingly, several advantages of this invention are:
(a) Consumer distributorships provide each authentic owner or user a moneymaking opportunity for each authentically owned or used product or service. Thus a passive product or service being authentically purchased, gifted or used becomes an active money-growing asset for commissioned distributions.
(b) Consumer distributorships are permanent during the life cycles of the associated products or services. Thus a product or service consumership is acquired once and distributed repeatedly.
(c) Consumership-based distribution enables a new and efficient distribution framework for distributing products and services, in which suppliers can reach new consumers either directly or via distributors who are existing consumers, thus cutting out all the middlemen and intermediaries.
Further objects and advantages of this invention will become apparent from a consideration of the drawings and ensuring description.
3. LIST OF FIGURES
Fig 1 illustrates consumer distributorship data storage, access and usage.
Fig 2 illustrates a consumership-based distribution platform.
Fig 3 illustrates order processing in consumership-based distribution.
Fig 4 illustrates store presentations in consumership-based distribution.
Fig 1 illustrates consumer distributorship data storage, access and usage.
Fig 2 illustrates a consumership-based distribution platform.
Fig 3 illustrates order processing in consumership-based distribution.
Fig 4 illustrates store presentations in consumership-based distribution.
4. SUMMARY
This specification discloses a computer-implemented consumership-based distribution mechanism which equates authentic ownerships with corresponding owner distributorships and authentic userships with corresponding user distributorships. In a consumership-based distribution of a product or service from a distributing member to a distributee, the distributee is affirmed a consumer distributorship of said product or service, the distributing member is paid a commission if the distributing member has a consumer distributorship of said product or service.
This specification covers the description of distributorship storage, access and usage for enabling consumership-based distribution, the description of a consumership-based distribution platform and the description of store presentations for carrying out consumership-based distribution transactions.
These and other features, aspects, and advantages of the present invention will become better understood with reference to the following description and claims.
This specification discloses a computer-implemented consumership-based distribution mechanism which equates authentic ownerships with corresponding owner distributorships and authentic userships with corresponding user distributorships. In a consumership-based distribution of a product or service from a distributing member to a distributee, the distributee is affirmed a consumer distributorship of said product or service, the distributing member is paid a commission if the distributing member has a consumer distributorship of said product or service.
This specification covers the description of distributorship storage, access and usage for enabling consumership-based distribution, the description of a consumership-based distribution platform and the description of store presentations for carrying out consumership-based distribution transactions.
These and other features, aspects, and advantages of the present invention will become better understood with reference to the following description and claims.
5. DETAILED DESCRIPTIONS
Ownerships and userships are two major categories of consumerships. This invention uses authentic ownerships and authentic userships for distribution purpose. Authentic ownerships are authenticated upon actual ownership acquiring actions and authentic userships are authenticated upon actual usership acquiring actions. This invention equates authentic ownerships with corresponding commissioned distributorships hereinafter referred to as owner distributorships and authentic userships with corresponding commissioned distributorships hereinafter referred to as user distributorships. Owner distributorships and user distributorships are hereinafter collectively referred to as consumer distributorships.
Fig 1 illustrates distributorship storage, access and usage for enabling consumership-based distribution. The distributorship module 100 comprises a distributorship database 101 for storing distributorship data records and a distributorship data access interface 102 for inserting and accessing stored distributorship data. The distributorship database 101 stores a plurality of distributorship records in one or more computer-readable storage media. Each distributorship record represents a distributorship relationship between a managed member and a managed product or service entity provisioned for distribution. Each distributorship record comprises data fields (uid, eid, type), wherein the uid field is for storing a unique member identifier of the distributor, the eid field is for storing a unique entity identifier of the product or service entity distributable by the distributor, the type field is for storing the unique type code identifying the type of the distributorship, in which one type code value indicates owner distributorship 105 and another type code value indicates user distributorship 106. An alternative to using a type field for distinguishing distributorship types is to store owner distributorships and user distributorships in separate databases. The distributorship data access interface 102 comprises query functions 103 and affirmation functions 104. The query functions 103 are used for retrieving data stored in the distributorship database 101. The affirmation functions 104 are used for creating and storing distributorship records into the distributorship database 101. The following are some example functions in the distributorship data access interface 102. There may be other functions with varied inputs, outputs and functionalities.
(1) query] (uid, type) 103 - This function takes uid and type as input parameters and returns a list of entity identifiers of all the product and service entities that the member identified by the given identifier uid has the given type of distributorships stored in the distributorship database. When the type parameter value is zero, it means any types.
(2) query2(uid, type) 103 - This function takes uid and type as input parameters and returns the distributorship records that the distributor identified by the given identifier uid has distributorships of the given type stored in the distributorship database.
When the type parameter value is zero, it means any types.
(3) query3(uid, eid, type) 103 - This function takes uid, eid and type as input parameters and validates the existence of a distributorship between the distributor identified by the given identifier uid and the product or service entity identified by the given identifier eid, wherein the distributorship is of the type given in the type parameter. When the type parameter value is zero, it means any types.
(4) affirm(uid, eid, type) 104 - This function takes uid, eid and type as input parameters, constructs a distributorship record using the input values and inserts it into the distributorship database if it is not already existent in said distributorship database.
Consumer distributorships are stored in the distributorship database. Each stored consumer distributorship may be an owner distributorship 105 or a user distributorship 106, wherein:
(1) A member's owner distributorship 105 of a product entity is equated with the member's corresponding authentic ownership of the entity. It is affirmed for the member when an ownership acquiring action from a distributing member's presentation of the entity is initiated and causes the entity to be distributed from the distributing member to the member.
As the result of the affirmation, the member becomes an authorized distributor of the entity for making commissions pertaining to the affirmed owner distributorship when further distributing the entity to other members.
(2) A member's user distributorship 106 of a product or service entity is equated with the member's corresponding authentic usership of the entity. It is affirmed for the member when a usership acquiring action from a distributing member's presentation of the entity is initiated and causes the usership of the entity to be distributed from the distributing member to the member, thus the member automatically becomes the distributor of the entity for making commissions pertaining to the affirmed user distributorship when further distributing the entity to other members.
A distributing member makes a product or service entity available for consumership-based distribution via an entity presentation unit 107 in a store presentation. An entity presentation unit 107 comprises the entity description 108 and the associated consumership acquiring action means 109 for users to acquire consumerships of the presented entity. The distributing member may be the supplier of the presented entity or a distributor of the presented entity. The consumership acquiring action means 109 may be an ownership acquiring action 110 or a usership acquiring action 111 or a combination of both.
Action 110 is an ownership acquiring action for the distributee to acquire the ownership right of the presented entity 108, which causes an owner distributorship 105 of the presented entity to be affirmed for the distributee. For each distribution of the presented entity 108 triggered by an ownership acquiring action means 110, the distributee is affirmed the owner distributorship 105 of the presented entity, the distributing member is paid a commission if the distributing member is a distributor of the presented entity and the supplier of the entity is paid a profit.
The ownership acquiring action means 110 is further classified into three categories:
(1) Ownership acquiring purchasing action 112 - A purchasing action in this category involves a buying member making a purchase of a product entity from a distributing member who may be a distributor of the entity or the supplier of the entity, in which the buying member is affirmed the owner distributorship of the purchased entity, the distributing member is paid a commission if the distributing member is a distributor of the entity, and the supplier of the purchased entity is paid a profit.
(2) Ownership acquiring gifting action with purchasing 113 - A gifting action in this category involves a gift giver gifting a purchased product entity to a gift recipient, in which the gift giver pays for the purchase, the gift recipient (the distributee) is affirmed the owner distributorship of the gifted entity, the distributing member (the seller) is paid a commission if the distributing member is a distributor of the entity, and the supplier of the purchased entity is paid a profit.
(3) Ownership acquiring gifting action without purchasing 114 - A gifting action in this category involves a member gifting a product entity to another member without requiring a purchase of the entity. In a distribution of a product entity triggered by such action, the gift recipient is affirmed the owner distributorship of the gifted entity.
Action 111 is avsership acquiring action for the distributee to acquire the usership right of the presented product or service entity, which causes a user distributorship 106 of the entity to be affirmed for the distributee. For each distribution of the presented entity 108 triggered by a usership acquiring action means 111, the distributee is affirmed the user distributorship 106 of the presented entity, the distributing member is paid a commission if the distributing member is a distributor of the presented entity, and the supplier of the entity is paid a profit.
The usership acquiring action means 111 may be further classified into the following categories:
(1) Usership acquiring purchasing action 115 - A purchasing action in this category involves a buying member purchasing the usage right of a product or service entity from a distributing member, in which the buying member is affirmed the user distributorship of the entity, the distributing member is paid a commission if the distributing member is a distributor of said entity and the supplier of the entity is paid a profit.
(2) Usership acquiring gifting action with purchasing 116 - A gifting action in this category involves a first member paying for the purchase of the usership right of a product or service entity for a second member, in which the first member pays for the purchase of the entity, the second member is affirmed the user distributorship of the entity, the distributing member is paid a commission if the distributing member is a distributor of the entity and the supplier of the entity is paid a profit.
(3) Usership acquiring gifting action without purchasing 117 - A gifting action in this category involves a member giving away the usership right of a product or service entity to another member, in which the recipient is affirmed the user distributorship of the entity.
Fig 2 illustrates the architecture of a consumership-based distribution platform that utilizes the consumership-based distribution mechanism illustrated in Fig 1. The distribution platform operates in the environment comprising a plurality of managed members for participating in distribution, a plurality of managed product or service entities provisioned for distribution, and a plurality of store presentations for carrying out distribution transactions. A managed member may be a business member or an individual member. A managed member may enroll product or service entities for distribution or distribute product or service entities that the member has distributorships or direct-sell self-enrolled product or service entities.
Ownerships and userships are two major categories of consumerships. This invention uses authentic ownerships and authentic userships for distribution purpose. Authentic ownerships are authenticated upon actual ownership acquiring actions and authentic userships are authenticated upon actual usership acquiring actions. This invention equates authentic ownerships with corresponding commissioned distributorships hereinafter referred to as owner distributorships and authentic userships with corresponding commissioned distributorships hereinafter referred to as user distributorships. Owner distributorships and user distributorships are hereinafter collectively referred to as consumer distributorships.
Fig 1 illustrates distributorship storage, access and usage for enabling consumership-based distribution. The distributorship module 100 comprises a distributorship database 101 for storing distributorship data records and a distributorship data access interface 102 for inserting and accessing stored distributorship data. The distributorship database 101 stores a plurality of distributorship records in one or more computer-readable storage media. Each distributorship record represents a distributorship relationship between a managed member and a managed product or service entity provisioned for distribution. Each distributorship record comprises data fields (uid, eid, type), wherein the uid field is for storing a unique member identifier of the distributor, the eid field is for storing a unique entity identifier of the product or service entity distributable by the distributor, the type field is for storing the unique type code identifying the type of the distributorship, in which one type code value indicates owner distributorship 105 and another type code value indicates user distributorship 106. An alternative to using a type field for distinguishing distributorship types is to store owner distributorships and user distributorships in separate databases. The distributorship data access interface 102 comprises query functions 103 and affirmation functions 104. The query functions 103 are used for retrieving data stored in the distributorship database 101. The affirmation functions 104 are used for creating and storing distributorship records into the distributorship database 101. The following are some example functions in the distributorship data access interface 102. There may be other functions with varied inputs, outputs and functionalities.
(1) query] (uid, type) 103 - This function takes uid and type as input parameters and returns a list of entity identifiers of all the product and service entities that the member identified by the given identifier uid has the given type of distributorships stored in the distributorship database. When the type parameter value is zero, it means any types.
(2) query2(uid, type) 103 - This function takes uid and type as input parameters and returns the distributorship records that the distributor identified by the given identifier uid has distributorships of the given type stored in the distributorship database.
When the type parameter value is zero, it means any types.
(3) query3(uid, eid, type) 103 - This function takes uid, eid and type as input parameters and validates the existence of a distributorship between the distributor identified by the given identifier uid and the product or service entity identified by the given identifier eid, wherein the distributorship is of the type given in the type parameter. When the type parameter value is zero, it means any types.
(4) affirm(uid, eid, type) 104 - This function takes uid, eid and type as input parameters, constructs a distributorship record using the input values and inserts it into the distributorship database if it is not already existent in said distributorship database.
Consumer distributorships are stored in the distributorship database. Each stored consumer distributorship may be an owner distributorship 105 or a user distributorship 106, wherein:
(1) A member's owner distributorship 105 of a product entity is equated with the member's corresponding authentic ownership of the entity. It is affirmed for the member when an ownership acquiring action from a distributing member's presentation of the entity is initiated and causes the entity to be distributed from the distributing member to the member.
As the result of the affirmation, the member becomes an authorized distributor of the entity for making commissions pertaining to the affirmed owner distributorship when further distributing the entity to other members.
(2) A member's user distributorship 106 of a product or service entity is equated with the member's corresponding authentic usership of the entity. It is affirmed for the member when a usership acquiring action from a distributing member's presentation of the entity is initiated and causes the usership of the entity to be distributed from the distributing member to the member, thus the member automatically becomes the distributor of the entity for making commissions pertaining to the affirmed user distributorship when further distributing the entity to other members.
A distributing member makes a product or service entity available for consumership-based distribution via an entity presentation unit 107 in a store presentation. An entity presentation unit 107 comprises the entity description 108 and the associated consumership acquiring action means 109 for users to acquire consumerships of the presented entity. The distributing member may be the supplier of the presented entity or a distributor of the presented entity. The consumership acquiring action means 109 may be an ownership acquiring action 110 or a usership acquiring action 111 or a combination of both.
Action 110 is an ownership acquiring action for the distributee to acquire the ownership right of the presented entity 108, which causes an owner distributorship 105 of the presented entity to be affirmed for the distributee. For each distribution of the presented entity 108 triggered by an ownership acquiring action means 110, the distributee is affirmed the owner distributorship 105 of the presented entity, the distributing member is paid a commission if the distributing member is a distributor of the presented entity and the supplier of the entity is paid a profit.
The ownership acquiring action means 110 is further classified into three categories:
(1) Ownership acquiring purchasing action 112 - A purchasing action in this category involves a buying member making a purchase of a product entity from a distributing member who may be a distributor of the entity or the supplier of the entity, in which the buying member is affirmed the owner distributorship of the purchased entity, the distributing member is paid a commission if the distributing member is a distributor of the entity, and the supplier of the purchased entity is paid a profit.
(2) Ownership acquiring gifting action with purchasing 113 - A gifting action in this category involves a gift giver gifting a purchased product entity to a gift recipient, in which the gift giver pays for the purchase, the gift recipient (the distributee) is affirmed the owner distributorship of the gifted entity, the distributing member (the seller) is paid a commission if the distributing member is a distributor of the entity, and the supplier of the purchased entity is paid a profit.
(3) Ownership acquiring gifting action without purchasing 114 - A gifting action in this category involves a member gifting a product entity to another member without requiring a purchase of the entity. In a distribution of a product entity triggered by such action, the gift recipient is affirmed the owner distributorship of the gifted entity.
Action 111 is avsership acquiring action for the distributee to acquire the usership right of the presented product or service entity, which causes a user distributorship 106 of the entity to be affirmed for the distributee. For each distribution of the presented entity 108 triggered by a usership acquiring action means 111, the distributee is affirmed the user distributorship 106 of the presented entity, the distributing member is paid a commission if the distributing member is a distributor of the presented entity, and the supplier of the entity is paid a profit.
The usership acquiring action means 111 may be further classified into the following categories:
(1) Usership acquiring purchasing action 115 - A purchasing action in this category involves a buying member purchasing the usage right of a product or service entity from a distributing member, in which the buying member is affirmed the user distributorship of the entity, the distributing member is paid a commission if the distributing member is a distributor of said entity and the supplier of the entity is paid a profit.
(2) Usership acquiring gifting action with purchasing 116 - A gifting action in this category involves a first member paying for the purchase of the usership right of a product or service entity for a second member, in which the first member pays for the purchase of the entity, the second member is affirmed the user distributorship of the entity, the distributing member is paid a commission if the distributing member is a distributor of the entity and the supplier of the entity is paid a profit.
(3) Usership acquiring gifting action without purchasing 117 - A gifting action in this category involves a member giving away the usership right of a product or service entity to another member, in which the recipient is affirmed the user distributorship of the entity.
Fig 2 illustrates the architecture of a consumership-based distribution platform that utilizes the consumership-based distribution mechanism illustrated in Fig 1. The distribution platform operates in the environment comprising a plurality of managed members for participating in distribution, a plurality of managed product or service entities provisioned for distribution, and a plurality of store presentations for carrying out distribution transactions. A managed member may be a business member or an individual member. A managed member may enroll product or service entities for distribution or distribute product or service entities that the member has distributorships or direct-sell self-enrolled product or service entities.
The distribution platform comprises a distribution server 200 which supports a plurality of clients 208. The distribution server 200 is responsible for providing consumership-based distribution services and related data services. It comprises distributorship module 100 (Fig 1), account module 201, entity module 202, event module 203, transaction processing unit 204, order processing unit 205, event processing unit 206 and server control 207. The distributorship module 100 provides storage, affirmation and retrieval of distributorship data. The account module 201 provides storage, registration, update and retrieval of managed member account data. The entity module 202 provides storage, enrollment, update and retrieval of managed product and service entity data. The event module 203 provides storage and retrieval of historical transactional records.
The transaction processing unit 204 is responsible for processing each transaction which comprises one or more consumership acquiring orders, the order processing unit 205 is responsible for processing a single consumership acquiring order and the event processing unit 206 is responsible for processing transactional event logging and notification. The server control 207 is responsible for receiving service requests from clients 208 and directing the requests to related server components for processing and returning responses to the clients that initiated the service requests. The components of the distribution server 200 may reside on a same server machine or scatter into a computing cloud.
The account module 201 comprises an account database and an account data access interface. The account database stores a plurality of member account records in one or more computer-readable storage media. The account data access interface provides functions for creating, accessing and managing the stored account records. A member's account record comprises the member's unique identifier, contact data, the member's social friends, and supplier's default consumer distributorship commission setups for owner distributorship and/or user distributorship, each commission setup is either a percentage of entity pricing or a fixed value and is applicable to all the product or service entities that enrolled by the member. The account data access interface comprises registry functions for registering a member account based on user supplied data which creates an account record in the account database; update functions for updating a member's account data; and retrieval functions for accessing one or a selection of members' account data.
The entity module 202 comprises an entity database and an entity data access interface. The entity database stores a plurality of entity data records in one or more computer-readable storage media.
Each entity is either a product entity or a service entity enrolled for distribution by its supplier. Each entity data record comprises a unique entity identifier, a supplier's member identifier, entity title, description, price, entity level commission setups for owner distributorship and/or user distributorship, etc. An entity level commission setup is either a percentage of entity pricing or a fixed value and takes the precedence over its corresponding supplier's default commission setup.
The entity data access interface comprises entity enrollment function for enrolling a product or service entity into entity database for joining distribution by managed members; entity data retrieval function for retrieving detailed entity data of a given entity or a selection of entities; entity data update function for updating the entity data for a given entity or a selection of entities. Once a product or service entity is enrolled with the platform, the entity is ready for distribution by managed members.
The event module 203 comprises an event database and an event data access interface. The event database stores a plurality of event records in one or more computer-readable storage media. Each event record captures the essential historical data of a consumership acquiring order. Each event record comprises the timestamp of the event, the distributing member's identifier, the distributee's identifier, the identifier of the entity being distributed, the quantity of the entity being distributed, the type of triggering action, etc. The event data access interface comprises event insertion function for inserting a new event record into event database and event data retrieval functions for retrieving stored event data.
The transaction processing unit 204 processes each transaction initiated from a store presentation 209. Each transaction contains one or more consumership acquiring orders. Each order in a transaction is processed by order processing unit 205. Both transaction processing unit 204 and order processing unit 205 can be directly used for processing single order transaction initiated from a client store presentation. The order processing unit 205 is further illustrated in Fig 3.
The event processing unit 206 is invoked upon the completion of each order processing and is effective to that order. The event processing unit further comprises the means of. (1) event logging for creating an event record for each consumership acquiring order and storing it in the event database 203; (2) event notification for dispatching an event notification to one or more subscribing applications 210. An application may subscribe the event notification service with predefined event filter to define the attributes of the events that the application is interested in receiving.
The transaction processing unit 204 is responsible for processing each transaction which comprises one or more consumership acquiring orders, the order processing unit 205 is responsible for processing a single consumership acquiring order and the event processing unit 206 is responsible for processing transactional event logging and notification. The server control 207 is responsible for receiving service requests from clients 208 and directing the requests to related server components for processing and returning responses to the clients that initiated the service requests. The components of the distribution server 200 may reside on a same server machine or scatter into a computing cloud.
The account module 201 comprises an account database and an account data access interface. The account database stores a plurality of member account records in one or more computer-readable storage media. The account data access interface provides functions for creating, accessing and managing the stored account records. A member's account record comprises the member's unique identifier, contact data, the member's social friends, and supplier's default consumer distributorship commission setups for owner distributorship and/or user distributorship, each commission setup is either a percentage of entity pricing or a fixed value and is applicable to all the product or service entities that enrolled by the member. The account data access interface comprises registry functions for registering a member account based on user supplied data which creates an account record in the account database; update functions for updating a member's account data; and retrieval functions for accessing one or a selection of members' account data.
The entity module 202 comprises an entity database and an entity data access interface. The entity database stores a plurality of entity data records in one or more computer-readable storage media.
Each entity is either a product entity or a service entity enrolled for distribution by its supplier. Each entity data record comprises a unique entity identifier, a supplier's member identifier, entity title, description, price, entity level commission setups for owner distributorship and/or user distributorship, etc. An entity level commission setup is either a percentage of entity pricing or a fixed value and takes the precedence over its corresponding supplier's default commission setup.
The entity data access interface comprises entity enrollment function for enrolling a product or service entity into entity database for joining distribution by managed members; entity data retrieval function for retrieving detailed entity data of a given entity or a selection of entities; entity data update function for updating the entity data for a given entity or a selection of entities. Once a product or service entity is enrolled with the platform, the entity is ready for distribution by managed members.
The event module 203 comprises an event database and an event data access interface. The event database stores a plurality of event records in one or more computer-readable storage media. Each event record captures the essential historical data of a consumership acquiring order. Each event record comprises the timestamp of the event, the distributing member's identifier, the distributee's identifier, the identifier of the entity being distributed, the quantity of the entity being distributed, the type of triggering action, etc. The event data access interface comprises event insertion function for inserting a new event record into event database and event data retrieval functions for retrieving stored event data.
The transaction processing unit 204 processes each transaction initiated from a store presentation 209. Each transaction contains one or more consumership acquiring orders. Each order in a transaction is processed by order processing unit 205. Both transaction processing unit 204 and order processing unit 205 can be directly used for processing single order transaction initiated from a client store presentation. The order processing unit 205 is further illustrated in Fig 3.
The event processing unit 206 is invoked upon the completion of each order processing and is effective to that order. The event processing unit further comprises the means of. (1) event logging for creating an event record for each consumership acquiring order and storing it in the event database 203; (2) event notification for dispatching an event notification to one or more subscribing applications 210. An application may subscribe the event notification service with predefined event filter to define the attributes of the events that the application is interested in receiving.
The clients 208 comprise a plurality of store presentations 209 and applications 210. The clients 208 interact with the server 200 across communication networks and access the distribution services remotely from variety of computing devices. The data modules 100 201 202 203 and the processing units 204 205 206 may be accessed locally by native applications or remotely by store presentations 209 and client applications 210. The remote access may be implemented using various standard communication protocols. Each store presentation 209 is a user actionable commerce presentation which comprises the presentation of one or more product or service entities and associated user action means for initiating consumership acquiring actions against the presented entities. Each store presentation 209 interacts with the distribution server 200 across communication networks, in which a user action request is sent to the distribution server and the distribution server processes the request and then returns the responses back to the initiating store presentation.
A client application 210 may be hosted at the distribution server 200 side or at a 3`d party application server side. A client application may utilize one or more components and services of the distribution server 200. For example, an e-commerce application may provide the access to one or more consumership-based store presentations, an advertising application or a marketing application or a data mining application may utilize the consumer distributorship data available in distributorship module 100 and/or the consumership-based transactional data available in event module 203 for extrapolating customer intelligence data. An application may use both the consumership-based transaction services and related data services for supporting comprehensive features.
Fig 3 illustrates the steps of order processing unit 205. Entry 1 is for orders which involve purchasing and are triggered by one of the action 112 113 115 116 (Fig 1), such an order is processed by step 301, 302 and 303. Entry 2 is for orders which do not involve purchasing and are triggered by one of the action 114 117 (Fig 1), such an order is processed by step 303. For each order involving a distributing member, a distributee and a product or service entity being distributed, the order processing unit processes the order in the steps of:
(1) Distributor's commission payment 301 - This step processes distributor's commission payment. If the distributing member is a distributor of the product or service entity being distributed, the distributing member is paid a commission based on the distributorship associated with the order, otherwise the commission payable is zero. If the entity level commission setup for the associated distributorship is available, it is used for calculating the commission payable, otherwise the supplier's default commission setup for the type of distributorship is used for calculating the commission payable.
(2) Supplier's profit payment 302 - This step processes supplier's profit payment associated with the order. The supplier's profit payment is calculated by deducting from the entity pricing the commission cost and the transactional cost attributing to the supplier (if any), and the profit payable is paid to the supplier of the distributed entity.
(3) Distributee's distributorship affirmation 303 - This step grants the distributee a consumer distributorship of the distributed entity via the invocation of affirmation function 104. For an order triggered by an ownership acquiring action, an owner distributorship of said entity is affirmed for its distributee. For an order triggered by a usership acquiring action, a user distributorship of said entity is affirmed for its distributee. As a result, said distributee becomes a distributor of said entity for commissioned distributions.
With the capability of such order processing, the supplier of a consumership-based product or service entity may reach new consumers for the entity either directly or via distributors who are existing consumers, thus cutting out all the middlemen and intermediaries.
These order processing steps are specific to consumership-based distribution, other tasks that are not specific to consumership-based distribution, such as delivery service, transaction fee processing, etc.
are excluded in the description.
Fig 4 provides a detailed illustration of store presentation 209 (Fig 2), which includes the illustration of store presentation content, carrying media and rendering mechanisms. A
store presentation is a user actionable interactive media presentation comprising one or more product or service entity presentation units in a display area 401. Each entity presentation unit 107 comprises entity description 108 and user action means 109. An entity presentation may be factual, such as title, description, price, etc, or promotional multimedia presentation for advertising purpose. The user action means 109 may comprise one or more consumership acquiring actions 112-117 (Fig 1). The entity presentation units may further be organized into a navigational hierarchy using a plurality of navigational categories 402 in which when a category is selected, the entity presentation units associated with that category are shown in the display area 401. A presented entity in a store presentation may be the entity that the store owner has consumer distributorship or the entity that the store owner self-enrolled.
A member may have one or more store presentations, one or more of them may be displayed in the member's public profile associated with the distribution platform or in a third party social networking platform integrated with the distribution platform. A store presentation may further comprise the store owner's social friends 403 so that a friend's one or more store presentations may be located by following the friend linkage.
A store presentation comprises a sequence of statements, instructions and supporting data for defining its structure, content and interactivity. The store presentation may be encoded in textual formats, byte code formats or binary formats or any combinations of above.
A store presentation is a user actionable interactive media object that interacts remotely with the distribution server over communication network connections, including wired connections, wireless connections, Internet or hybrid networking connections.
A carrying medium 404 for carrying a store presentation may be any interactive content or interactive software application, such as, Internet content or application, communication and messaging content or application, mobile content or application, interactive TV content or application, interactive gaming content or application, interactive software application, or advertisement, etc.
The method of store presentation rendering 405 in a carrying medium 404 is one of the mechanisms:
(1) Referencing 406 - A store presentation may be hosted by the distribution server and referenced in a carrying media via store object identification, universal address or locator and rendered when the reference is instantiated. For example, a hyper link pointing to a store presentation may be included in an email, an instant message, a micro-blogging text, a web page, an application, etc, in which clicking the hyper link will show the destination store presentation.
(2) Embedding 407 - A store presentation may be fully embedded in a carrying medium. For example, a store presentation may be embedded in a Web page, an email, a social networking application, an e-commerce application, or an advertisement, etc. A
store presentation implemented as a rich media object may be embedded in a markup content. A
store presentation implemented as a rich media object such as interactive movie may be embedded in raw binary in a compiled or packaged content.
(3) Generating on-demand 408 - A store presentation may be dynamically generated and then rendered in a carrying medium. A dynamic store may be generated at the distribution server side and rendered to the client side. A dynamic store may be generated at the client side by the carrying medium on the fly and inserts the generated store object in-place. A dynamic store may also be generated by a remote 3`d party application that integrated with the platform. The dynamic generation of a store presentation containing one or more product or service entity presentation units may be based on certain entity selection criteria which comprise any combinations of entity properties, keywords, phrases, categories, pricing properties, and entity distribution performance properties. The selection criteria may be predetermined by the provider of the carrying medium or entered by an end user as in a search engine, or generated by computer software based on available or postulated customer intelligence data such as customer interests, purchasing history, etc.
While the above description contains many specificities, these should not be construed as limitations on the scope of the invention. Many other variations are possible.
Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their legal equivalents.
A client application 210 may be hosted at the distribution server 200 side or at a 3`d party application server side. A client application may utilize one or more components and services of the distribution server 200. For example, an e-commerce application may provide the access to one or more consumership-based store presentations, an advertising application or a marketing application or a data mining application may utilize the consumer distributorship data available in distributorship module 100 and/or the consumership-based transactional data available in event module 203 for extrapolating customer intelligence data. An application may use both the consumership-based transaction services and related data services for supporting comprehensive features.
Fig 3 illustrates the steps of order processing unit 205. Entry 1 is for orders which involve purchasing and are triggered by one of the action 112 113 115 116 (Fig 1), such an order is processed by step 301, 302 and 303. Entry 2 is for orders which do not involve purchasing and are triggered by one of the action 114 117 (Fig 1), such an order is processed by step 303. For each order involving a distributing member, a distributee and a product or service entity being distributed, the order processing unit processes the order in the steps of:
(1) Distributor's commission payment 301 - This step processes distributor's commission payment. If the distributing member is a distributor of the product or service entity being distributed, the distributing member is paid a commission based on the distributorship associated with the order, otherwise the commission payable is zero. If the entity level commission setup for the associated distributorship is available, it is used for calculating the commission payable, otherwise the supplier's default commission setup for the type of distributorship is used for calculating the commission payable.
(2) Supplier's profit payment 302 - This step processes supplier's profit payment associated with the order. The supplier's profit payment is calculated by deducting from the entity pricing the commission cost and the transactional cost attributing to the supplier (if any), and the profit payable is paid to the supplier of the distributed entity.
(3) Distributee's distributorship affirmation 303 - This step grants the distributee a consumer distributorship of the distributed entity via the invocation of affirmation function 104. For an order triggered by an ownership acquiring action, an owner distributorship of said entity is affirmed for its distributee. For an order triggered by a usership acquiring action, a user distributorship of said entity is affirmed for its distributee. As a result, said distributee becomes a distributor of said entity for commissioned distributions.
With the capability of such order processing, the supplier of a consumership-based product or service entity may reach new consumers for the entity either directly or via distributors who are existing consumers, thus cutting out all the middlemen and intermediaries.
These order processing steps are specific to consumership-based distribution, other tasks that are not specific to consumership-based distribution, such as delivery service, transaction fee processing, etc.
are excluded in the description.
Fig 4 provides a detailed illustration of store presentation 209 (Fig 2), which includes the illustration of store presentation content, carrying media and rendering mechanisms. A
store presentation is a user actionable interactive media presentation comprising one or more product or service entity presentation units in a display area 401. Each entity presentation unit 107 comprises entity description 108 and user action means 109. An entity presentation may be factual, such as title, description, price, etc, or promotional multimedia presentation for advertising purpose. The user action means 109 may comprise one or more consumership acquiring actions 112-117 (Fig 1). The entity presentation units may further be organized into a navigational hierarchy using a plurality of navigational categories 402 in which when a category is selected, the entity presentation units associated with that category are shown in the display area 401. A presented entity in a store presentation may be the entity that the store owner has consumer distributorship or the entity that the store owner self-enrolled.
A member may have one or more store presentations, one or more of them may be displayed in the member's public profile associated with the distribution platform or in a third party social networking platform integrated with the distribution platform. A store presentation may further comprise the store owner's social friends 403 so that a friend's one or more store presentations may be located by following the friend linkage.
A store presentation comprises a sequence of statements, instructions and supporting data for defining its structure, content and interactivity. The store presentation may be encoded in textual formats, byte code formats or binary formats or any combinations of above.
A store presentation is a user actionable interactive media object that interacts remotely with the distribution server over communication network connections, including wired connections, wireless connections, Internet or hybrid networking connections.
A carrying medium 404 for carrying a store presentation may be any interactive content or interactive software application, such as, Internet content or application, communication and messaging content or application, mobile content or application, interactive TV content or application, interactive gaming content or application, interactive software application, or advertisement, etc.
The method of store presentation rendering 405 in a carrying medium 404 is one of the mechanisms:
(1) Referencing 406 - A store presentation may be hosted by the distribution server and referenced in a carrying media via store object identification, universal address or locator and rendered when the reference is instantiated. For example, a hyper link pointing to a store presentation may be included in an email, an instant message, a micro-blogging text, a web page, an application, etc, in which clicking the hyper link will show the destination store presentation.
(2) Embedding 407 - A store presentation may be fully embedded in a carrying medium. For example, a store presentation may be embedded in a Web page, an email, a social networking application, an e-commerce application, or an advertisement, etc. A
store presentation implemented as a rich media object may be embedded in a markup content. A
store presentation implemented as a rich media object such as interactive movie may be embedded in raw binary in a compiled or packaged content.
(3) Generating on-demand 408 - A store presentation may be dynamically generated and then rendered in a carrying medium. A dynamic store may be generated at the distribution server side and rendered to the client side. A dynamic store may be generated at the client side by the carrying medium on the fly and inserts the generated store object in-place. A dynamic store may also be generated by a remote 3`d party application that integrated with the platform. The dynamic generation of a store presentation containing one or more product or service entity presentation units may be based on certain entity selection criteria which comprise any combinations of entity properties, keywords, phrases, categories, pricing properties, and entity distribution performance properties. The selection criteria may be predetermined by the provider of the carrying medium or entered by an end user as in a search engine, or generated by computer software based on available or postulated customer intelligence data such as customer interests, purchasing history, etc.
While the above description contains many specificities, these should not be construed as limitations on the scope of the invention. Many other variations are possible.
Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their legal equivalents.
Claims (46)
1. A computer-implemented method of distribution, operated in the environment comprising a plurality of managed members for participating in distribution, a plurality of managed product or service entities provisioned for distribution, and a plurality of store presentations for carrying out distribution, the computer-implemented method comprising the steps of:
(a) providing a distributorship data storage for storing a plurality of consumer distributorship records in one or more computer-readable storage media, wherein each consumer distributorship record comprises a member identifier and an entity identifier representing a consumer distributorship relationship between said member and said entity;
(b) providing an order processing means for processing each entity distribution order, said entity distribution order is triggered by a consumership acquiring action and causes the consumership right of said entity to be distributed from a distributing member to a distributee, said order processing means further comprises the means of affirming consumer distributorship of said entity for said distrubutee.
(a) providing a distributorship data storage for storing a plurality of consumer distributorship records in one or more computer-readable storage media, wherein each consumer distributorship record comprises a member identifier and an entity identifier representing a consumer distributorship relationship between said member and said entity;
(b) providing an order processing means for processing each entity distribution order, said entity distribution order is triggered by a consumership acquiring action and causes the consumership right of said entity to be distributed from a distributing member to a distributee, said order processing means further comprises the means of affirming consumer distributorship of said entity for said distrubutee.
2. The method of claim 1, wherein a member's consumer distributorship of an entity is permanent during the life cycle of said entity.
3. The method of claim 1, wherein a stored consumer distributorship is either an owner distributorship or a user distributorship.
4. The method of claim 1, wherein said distributorship storage provides a means for distinguishing the type of each distributorship.
5. The method of claim 1, wherein said consumership acquiring action is either an ownership acquiring action or a usership acquiring action.
6. The method of claim 5, wherein said ownership acquiring action is one selected from the group consisting of:
(a) ownership acquiring purchasing action;
(b) ownership acquiring gifting action with purchasing;
(c) ownership acquiring gifting action without purchasing.
(a) ownership acquiring purchasing action;
(b) ownership acquiring gifting action with purchasing;
(c) ownership acquiring gifting action without purchasing.
7. The method of claim 5, wherein said usership acquiring action is one selected from the group consisting of:
(a) usership acquiring purchasing action;
(b) usership acquiring gifting action with purchasing;
(c) usership acquiring gifting action without purchasing.
(a) usership acquiring purchasing action;
(b) usership acquiring gifting action with purchasing;
(c) usership acquiring gifting action without purchasing.
8. The method of claim 1, wherein said consumer distributorship being affirmed is an owner distributorship if said triggering action is an ownership acquiring action or a user distributorship if said triggering action is a usership acquiring action.
9. The method of claim 1, wherein said distributing member is either the supplier of said distributed entity or a distributor of said distributed entity.
10. The method of claim 1, wherein for each entity distribution order involving purchasing, said order processing means further comprises the means of:
(a) making a commission payment to said distributing member if said distributing member is a distributor of said distributed entity;
(b) making a profit payment to the supplier of said distributed entity.
(a) making a commission payment to said distributing member if said distributing member is a distributor of said distributed entity;
(b) making a profit payment to the supplier of said distributed entity.
11. A computer program product comprising one or more computer readable storage media having a computer program embodied therein for execution by one or more processors to carry out the method of claim 1, wherein said storage media and processors may be co-located locally or distributed across communication networks.
12. A carrier wave embodying a computer data signal representing sequences of statements and instructions which, when executed by one or more processors causes said one or more processors to carry out the method of claim 1.
13. A computer-implemented system of distribution programmed to perform the method of claim 1.
14 14. A computer-implemented method of distribution, operated in the environment comprising a plurality of managed members for participating in distribution and a plurality of managed product or service entities provisioned for distribution, the computer-implemented method comprising the steps of:
(a) providing a distribution server for facilitating distribution activities, said distribution server further comprises (1) distributorship module for consumer distributorship data storage and retrieval, and (2) transaction processing unit for processing each distribution transaction, wherein each transaction comprises one or more consumership acquiring orders, wherein each order is triggered by a consumership acquiring action and causes the consumership of said entity to be distributed from its distributing member to its distributee;
(b) supporting a plurality of clients for interacting with said distribution server, wherein said clients comprise a plurality of store presentations for initiating distribution transactions, wherein each transaction request is sent to said distribution server for processing by said transaction processing unit.
(a) providing a distribution server for facilitating distribution activities, said distribution server further comprises (1) distributorship module for consumer distributorship data storage and retrieval, and (2) transaction processing unit for processing each distribution transaction, wherein each transaction comprises one or more consumership acquiring orders, wherein each order is triggered by a consumership acquiring action and causes the consumership of said entity to be distributed from its distributing member to its distributee;
(b) supporting a plurality of clients for interacting with said distribution server, wherein said clients comprise a plurality of store presentations for initiating distribution transactions, wherein each transaction request is sent to said distribution server for processing by said transaction processing unit.
15. The method of claim 14, wherein said consumership acquiring action is an ownership acquiring action or a usership acquiring action.
16. The method of claim 15, wherein said ownership acquiring action is one selected from the group consisting of:
(a) ownership acquiring purchasing action;
(b) ownership acquiring gifting action with purchasing;
(c) ownership acquiring gifting action without purchasing.
(a) ownership acquiring purchasing action;
(b) ownership acquiring gifting action with purchasing;
(c) ownership acquiring gifting action without purchasing.
17. The method of claim 15, wherein said usership acquiring action is one selected from the group consisting of:
(a) usership acquiring purchasing action;
(b) usership acquiring gifting action with purchasing;
(c) usership acquiring gifting action without purchasing.
(a) usership acquiring purchasing action;
(b) usership acquiring gifting action with purchasing;
(c) usership acquiring gifting action without purchasing.
18. The method of claim 14, wherein each order is further processed by a single order processing unit which is effective to the act of affirming consumer distributorship of the order's distributed entity for the order's distributee.
19. The method of claim 18, wherein the affirmed consumer distributorship is an owner distributorship if the order's triggering action is an ownership acquiring action.
20. The method of claim 18, wherein the affirmed consumer distributorship is a user distributorship if the order's triggering action is a usership acquiring action.
21. The method of claim 18, wherein said order processing unit is further effective to the act of making a commission payment to the order's distributing member if said distributing member is a distributor of the order's distributed entity.
22. The method of claim 18, wherein said order processing unit is further effective to the act of making a profit payment to the supplier of the order's distributed entity.
23. The method of claim 14, wherein said distribution server further comprises:
(a) account module for storing and accessing managed member account data;
(b) entity module for storing and accessing managed product and service entity data.
(a) account module for storing and accessing managed member account data;
(b) entity module for storing and accessing managed product and service entity data.
24. The method of claim 14, wherein said distribution server further comprises (1) event module for storage and retrieval of transactional event records and (2) event processing for logging event records, said event processing is invoked upon the completion of an order processing.
25. The method of claim 24, wherein said event processing further comprises event notification for dispatching the notifications of events to one or more subscribing applications.
26. The method of claim 14, wherein a store presentation is a user actionable interactive media presentation comprising one or more product or service entity presentation units, wherein each entity presentation unit comprises entity description and user action means.
27. The method of claim 26, wherein an entity presentation is factual or promotional.
28. The method of claim 26, wherein a presented entity in a store presentation is the entity that the store owner has consumer distributorship or the entity that the store owner self-enrolled.
29. The method of claim 26, wherein the user action means comprises one or more of consumership acquiring actions.
30. The method of claim 26, wherein a store presentation further comprises one or both of (1) a plurality of navigational categories, (2) store owner's social friends.
31. The method of claim 26, wherein said store presentation interacts remotely with the distribution server over communication network connections, including wired connections, wireless connections, Internet connections or hybrid networking connections.
32. The method of claim 26, wherein a store presentation is encoded in textual format, or byte code format or binary format or any combination of above, representing a sequence of statements, instructions and supporting data for defining the structure, content and interactivity of said store presentation.
33. The method of claim 26, wherein a carrying medium for carrying a store presentation is an interactive content or an interactive software application.
34. The method of claim 33, wherein said interactive content comprises one or any combinations of internet content, messaging content, mobile content and television content.
35. The method of claim 26, wherein a store presentation is rendered in a carrying medium in one of the mechanisms:
(a) referencing mechanism, wherein a store presentation is hosted by said distribution server or a 3`a party server, referenced in a carrying medium via store object identification, universal address or locator, and rendered when the reference is instantiated;
(b) embedding mechanism, wherein a store presentation is embedded in a carrying medium and rendered when the carrying medium is rendered;
(c) generating on-demand mechanism, wherein a store presentation is dynamically generated and then rendered in a carrying medium, wherein a dynamic store may be generated at said distribution server side, at a client side or at a third party server side and then rendered at the client side.
(a) referencing mechanism, wherein a store presentation is hosted by said distribution server or a 3`a party server, referenced in a carrying medium via store object identification, universal address or locator, and rendered when the reference is instantiated;
(b) embedding mechanism, wherein a store presentation is embedded in a carrying medium and rendered when the carrying medium is rendered;
(c) generating on-demand mechanism, wherein a store presentation is dynamically generated and then rendered in a carrying medium, wherein a dynamic store may be generated at said distribution server side, at a client side or at a third party server side and then rendered at the client side.
36. The method of claim 35, wherein the dynamic generation of a store presentation is based on entity selection criteria, wherein said selection criteria are predetermined by the provider of the carrying medium or entered by an end user or generated by a computer software based on available or postulated customer intelligence data.
37. The method of claim 36, wherein said entity selection criteria are any combinations of entity properties, keywords, phrases, categories, pricing properties, and entity distribution performance properties.
38. The method of claim 14, wherein the server components reside on a same server machine or are scattered into a computing cloud.
39. The method of claim 38, wherein the server components and services are accessed locally by native applications or remotely by store presentations and client applications.
40. The method of claim 38, wherein a client application may be hosted at said distribution server side or at a 3rd party service site.
41. The method of claim 38, wherein a client application may utilize one or more components and services of said distribution server.
42. The method of claim 41, wherein a client application may provide access to one or more store presentations for carrying out consumership-based transactions.
43. The method of claim 41, wherein a client application may utilize consumer distributorship data or consumership-based transactional data or combination of both for extrapolating customer intelligence data.
44. A computer program product comprising one or more computer readable storage media having a computer program embodied therein for execution by one or more processors to carry out the method of claim 14, wherein said storage media and processors may be co-located locally or distributed across communication networks.
45. A carrier wave embodying a computer data signal representing sequences of statements and instructions which, when executed by one or more processors causes said one or more processors to carry out the method of claim 14.
46. A computer-implemented system of distribution programmed to perform the method of claim 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2682967A CA2682967A1 (en) | 2009-10-19 | 2009-10-19 | Consumership-based distribution |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2682967A CA2682967A1 (en) | 2009-10-19 | 2009-10-19 | Consumership-based distribution |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2682967A1 true CA2682967A1 (en) | 2011-04-19 |
Family
ID=43896952
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2682967A Abandoned CA2682967A1 (en) | 2009-10-19 | 2009-10-19 | Consumership-based distribution |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2682967A1 (en) |
-
2009
- 2009-10-19 CA CA2682967A patent/CA2682967A1/en not_active Abandoned
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8037193B2 (en) | Virtual token | |
| RU2549113C2 (en) | Systems and methods of delivering information content | |
| US9088423B2 (en) | System and method for facilitating on call privileges over a digital network | |
| US10970758B2 (en) | Electronic marketplace for hosted service images | |
| US20140324690A1 (en) | System and method for a single digital wallet dynamic checkout tool | |
| US20100114739A1 (en) | Systems and methods for a comprehensive integrated and universal content selling and buying platform | |
| US20110202377A1 (en) | Method and system for providing a segment based differentiated customer experience solution | |
| WO2016029813A1 (en) | Method and system for revenue generation and revenue sharing from mobile application | |
| WO2010134127A1 (en) | Internet-based online advertising platform and processes running on said platform | |
| US20190080360A1 (en) | Technologies for propogating advertisements | |
| US11049135B2 (en) | Offers system | |
| KR20140013380A (en) | Method and system of advertisement based on social network service | |
| CA2682967A1 (en) | Consumership-based distribution | |
| CA2682036A1 (en) | Usership-based distribution | |
| AU775865B2 (en) | A virtual token | |
| KR20190000221A (en) | Method and System of Advertisement Based on Online Social Network Service | |
| CA2671268A1 (en) | Ownership-based distribution | |
| WO2014084758A2 (en) | System and method for sale of goods and services with rewards for customer spending | |
| CA2655342A1 (en) | Ownership-based distribution | |
| JP2014067213A (en) | Shopping site providing method and server for succeeding in merchandise introduction information as literary work | |
| WO2014093990A1 (en) | Deal package management systems and methods of use | |
| HK1181897A (en) | Marketplace for composite application and data solutions | |
| HK1167276B (en) | Content delivery systems and methods |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |