The present invention generally relates to an apparatus, system, and methods for marketing targeted products to users of an Internet based social media community. More particularly, this invention relates to an apparatus, system, and methods for collecting communications exchanged by users of an Internet based social media community, generating a collection of purchase decision profiles for each of those users, researching market conditions for a set of goods and services, and transforming these data into individually customized offers to buy or sell goods and services to those users and their social network contacts.
Techniques exist for identifying items that a consumer might enjoy in view of other items the consumer has previously indicated he or she enjoys. Some such techniques compare attributes of items the consumer previously indicated he or she enjoys with attributes of other items to identify items that the consumer might enjoy. Nevertheless, there exists a need for systems and methods which generate and deliver product recommendations to users of Internet-based social networks.
Hence, the present invention is directed to a system for marketing targeted products to users of an Internet-based social media community.
In one embodiment, the system may include a Recommendation, Advertisement, and Personalization (RAP) Engine for generating product recommendations. The RAP Engine may be connected to a Person Shopping Genome Sequence Repository, a Product Genome Sequence Repository, a Merchant Product's Price List Repository and a Genome Annotation Data Repository.
The system may include an AI and Semantic Engine connected to the Genome Annotation Data Repository, the Product Genome Sequence Repository, and the Merchant Product's Price List Repository. Also, the system may include a first data channel connected to the RAP Engine for communicating product recommendations to users of an Internet-based social media community.
In another aspect of the invention, the RAP Engine may be configured and adapted to perform distance search calculations involving data stored in the Person Shopping Genome Sequence Repository, the Product Genome Sequence Repository, the Merchant Product's Price List Repository, and the Genome Annotation Data Repository.
In another aspect of the invention, the Person Shopping Genome Sequence Repository may house a plurality of Person Shopping Genome Sequences, and the RAP Engine may be configured and adapted to perform distance search calculations which include calculating a Product Affinity Genome Model, and then calculating a second distance between one of the plurality of Person Shopping Genome Sequences and the Product Affinity Genome Model.
The accompanying drawings, which are incorporated herein and constitute part of this specification, illustrate an embodiment of the invention, and together with the general description given above and the detailed description given below, serve to explain the features of the invention.
The collection of data repositories (or cylinders) may include, without limitation, a Merchant Product Price List (MPPL) Repository 18, a Product Genome Sequence (PGS) Repository 20, a Person Shopping Genome Sequence (PSGS) Repository 22, and a Genome Annotation Data (GAD) Repository 24 (collectively referred to herein as “the Four Cylinders”). Preferably, these processes may occur continuously as described in connection with
As shown in
Additionally, the RAP Engine may analyze data from the Four Cylinders to develop a targeted group of users for receipt of advertisements for particular product offerings.
Accordingly, the exemplary system of
Referring to
Product Raw Data Crawler 36 is a process for periodically obtaining aggregate advertising and sales information from the Internet for a targeted list of products. This process periodically searches the Internet and stores web pages from a number of online Merchants (e.g., Amazon or eBay) to create a product raw data set. The stored web pages contain advertising information about products offered by the respective merchants. For example, one web page from an online retailer may include the product name, manufacturer, model number, class of goods or services, price, and a digital image. This process may be performed manually by one or more individuals or by an automated software program that is controllable by a single user.
Product Raw Data Repository 38 is a database that contains product raw data set information from the Product Raw Data Crawler. The information in the Product Raw Data Repository may be updated (in whole or in part) as new datasets are collected by the Product Raw Data Crawler. For instance, the database may be updated periodically during the day or at a selected time.
AI and Semantic Engine 40 is an Artificial Intelligence (AI) and Semantic Engine, which may be implemented using appropriate software. The AI and Semantic Engine may be used to extract and analyze data from the Product Raw Data Repository 38 and Social Raw Data Repository 42. The AI and Semantic Engine may create individual product vectors (or individual Product Genome Sequences) for storage in the Product Genome Sequence Repository. Additionally, the AI and Semantic Engine may be used to extract and analyze data from the Social Raw Data Repository. The AI and Semantic Engine may create individual Person Shopping Genome Sequences, which are then stored in the Person Shopping Genome Sequence Repository. Also, the AI and Semantic Engine may be used to extract and analyze data from the Product Raw Data Repository and the Social Raw Data Repository to generate Genome Annotation Data (GAD).
Product raw data set information in the Product Raw Data Repository 38 may be analyzed by the AI and Semantic Engine, and certain information may be extracted and transformed into Product Genome Sequences, which are then stored in the Product Genome Sequence Repository. For instance, a list of products that appears in the product raw data set with the highest frequency may be created. This list may be a list of the 100 products that appear with the greatest frequency. This list may be identified as the “Top 100” products in the product raw data set. The Top 100 products may be representative of products that are in high demand or are expected to be in high demand by consumers at or near the time the data set is collected.
Additionally, information extracted from the product raw data set may include other categories of data that are considered relevant to a consumer's decision to purchase a product. For example, the identity of the manufacturer, model number, class of goods or services, digital image, average price, and advertised price for each merchant in the data set may be extracted from the data set, normalized and housed in a database. All or part of the information, however, which may be extracted from the product raw data set and housed in the database, may be non-numerical or non-normalized data.
The information extracted from the product raw data may be transformed into Product Genome Sequences. Each sequence may be a data vector that associates a set of numerical values with ordered attributes of a product in the Product Raw Data Repository. For instance, each data vector may be comprised of eleven attributes that are considered relevant to a consumer's willingness to purchase a product. Each of the attributes may be assigned a numerical value ranging between zero and nine. Accordingly, an exemplary data vector may be an eleven digit sequence, and each digit may possess a numerical value equal to 0, 1, 2, 3, 4, 5, 6, 7, 8 or 9.
As described above, each digit in the sequence may represent an attribute of the product. In an illustrative sequence, the first digit of a product vector may represent the product attribute “average price.” The first digit of the product vector would be determined based on the “average price” of that product in the Product Raw Data Repository. For example, a product having an average price ranging from $0.00 to $99.00 may be assigned a numerical value of one. A product having an average price ranging from $100.00 to $150.00 dollars may be assigned a numerical value of two. Similarly, each remaining numerical value between three and nine may be associated with a different average price range. Hence, a product having an average price of $50.00 would have a product vector with a first digit of one, and a product having an average price of $150.00 would have a product vector with a first digit of two.
Creation of the Product Genome Sequences may be performed manually by one or more individuals or by an automated software program. The automated software program may be executed on a general purpose computer that is controlled by a single user. Additionally, the automated software program may utilize an AI and Semantic Engine to extract raw product data, evaluate products in the Product Raw Data Repository, and create the individual product vectors (or individual product genome sequences) for storage in the Product Genome Sequence Repository.
Product Genome Sequence Repository 20 is a database of sequences that are associated with certain products in the Product Raw Data Repository. Each sequence may be a data vector that associates a set of numerical values with ordered attributes of a product in the Product Raw Data Repository. For instance, each data vector may be comprised of eleven attributes that are considered relevant to a consumer's willingness to purchase a product. Each of the attributes may be assigned a numerical value ranging between zero and nine. Accordingly, an exemplary data vector may be an eleven digit sequence, and each digit may possess a numerical value equal to 0, 1, 2, 3, 4, 5, 6, 7, 8 or 9.
Social Network User 14 may be a person who has an account on a social network (e.g., Facebook, Google+ or Twitter) that allows the user to exchange information with other users of the social network. For example, a Facebook user may use a newsfeed to post information to the user's contacts within the social network. The users' contacts can read and post comments about what the user has written or posted and what other contacts have said about it. The newsfeed also allows the user to link to the posts of the user's contacts to see what they have posted and what other contacts said about them.
Social Raw Data Extractor 44 is a process for collecting information exchanged between a user of a social network and the user's contacts. The process involves capturing the exchanged information from the user's account and saving information considered relevant to the communication in a database called the Social Raw Data Repository. The Social Raw Data Extractor also may capture and save information from the user's contacts' newsfeeds. For example, a user of a social network, such as Facebook, may have 120 friends with whom they interact and share information. The user may post or share information with these “friends” on a newsfeed. The user also may access the contacts' newsfeeds. With permission of the user, the Social Raw Data Extractor periodically captures the information on the user's newsfeed, strips out information considered irrelevant to the application, and stores the relevant information in the Social Raw Data Repository database.
Additionally, the Social Raw Data Extractor 44 may capture available information on the newsfeed of each of the user's social contacts, strip out information considered to be irrelevant to the application, and store the information in the Social Raw Data Repository database. Thus, the Social Raw Data Extractor may periodically (e.g., daily) capture and store the user's communications with other members of the social network, as well as periodically capture and store the communications of the user's contacts' in a database.
Social Raw Data Repository 42 is a database that contains captured and filtered, but unedited, communications between users of a social network. The information in the Social Raw Data Repository may be updated (in whole or in part) periodically by the Social Raw Data Extractor. For instance, the database may be updated daily, weekly or at some other time or basis. Social raw data set information in the Social Raw Data Repository may be analyzed by the AI and Semantic Engine, and certain information may be extracted and transformed into Person Shopping Genome Sequences, which are then stored in the Person Shopping Genome Sequence Repository.
A Person Shopping Genome Sequence may be a data vector that associates a normalized set of numerical values with ordered attributes for one social network user based on information in the Social Raw Data Repository. For instance, each data vector may include tens, hundreds, or thousands of attributes that are considered relevant to a consumer's preferences and willingness to purchase a product. The number of attributes may be selected or determined empirically based on a given application. Each of the attributes may be assigned a numerical value ranging from zero to nine. Accordingly, an exemplary data vector may be a 100 digit sequence, and each digit may possess a numerical value equal to 0, 1, 2, 3, 4, 5, 6, 7, 8 or 9.
As described above, each digit in the sequence represents a normalized attribute of the social network user. In an illustrative sequence, the first digit of a social network user's Person Shopping Genome Sequence may represent the characteristic “owns a mobile communication device.” The first digit of the user's Person Shopping Genome Sequence would be determined based on communications between the user and the user's social network. The process for assigning a value to this digit may involve analyzing natural language in a stored communication from the user, which states “I am excited about my new mobile phone.” A software program using artificial intelligence and semantic algorithms may be used to analyze the user's stored communications and the communications of the user's contacts in the Social Raw Data Repository to extract the relevant information from that communication; namely, that the user is excited about having a new mobile phone, and thus “owns a mobile communication device.” The software program then may assign the first digit of the social network user's Person Shopping Genome Sequence a numerical value of 1 to indicate that the user owns a mobile communication device. In a similar manner, the values of each digit of an n-dimensional Person Shopping Genome Sequence that corresponds to n characteristics of the user may be determined.
The Person Shopping Genome Sequence Repository 20 may be populated by an automated software program. The automated software program may be executed on a general purpose computer that is controlled by a single user. The automated software program may utilize an Artificial Intelligence and Semantic Engine to create and update the individual Person Shopping Genome Sequences in the Person Shopping Genome Sequence Repository.
Accordingly, the Person Shopping Genome Sequence Repository 20 may be a database of sequences that are associated with the social network users in the Social Raw Data Repository. Each sequence (or Person Shopping Genome Sequence) may be a data vector that associates a set of numerical values with ordered attributes for one social network user based on information in the Social Raw Data Repository. For instance, each data vector may include tens, hundreds, or thousands of attributes that are considered relevant to a consumer's preferences and willingness to purchase a product. The number of attributes may be selected or determined empirically based on a given application. Each of the attributes may be assigned a numerical value ranging from zero to nine. Accordingly, an exemplary data vector may be a 100 digit sequence, and each digit may possess a numerical value equal to 0, 1, 2, 3, 4, 5, 6, 7, 8 or 9.
Genome Annotation Data (GAD) are data which are broadly related to a user's behavior, aspirations, preferences, interactions, and relationships but typically are not included in the user's Person Shopping Genome Sequence. For example, GAD relating to a user's behavior may include information that the user spent 0.33 seconds viewing an iPhone suggestion. In another example, GAD relating to a user's wishes or aspirations may include information that the user “has an iPhone” and “would love an iPad.” In yet another example, GAD relating to a user's behavior may be information that the user is currently in a bank. In yet another example, GAD relating to a user's relationships may be information that the user has a new niece. In yet another example, GAD relating to a user's behavior may include learned weighting factors for the vector components of the user's Person Shopping Genome Sequence.
GAD Engine 48 is a process for periodically obtaining GAD, which as described above, may include potentially relevant information concerning users of a social network that relate to a user's preferences or activities but does not affect the Personalized Shopping Genome Sequence of that user. The process involves capturing and analyzing communications exchanged between a user of a social network and the user's contacts. The process involves storing the information in a database called the GAD Repository 24. The GAD Engine also may capture and save information from the user's contacts' newsfeeds. In another example, the GAD Engine may capture and save information about a user's wishes or aspirations by analyzing an Internet store wishlist (e.g., an Amazon wishlist) that is associated with the user. In another example, the GAD Engine may capture and save information about a user's purchase history at an Internet store (e.g., Amazon purchase history). In yet another example, the GAD Engine may collect information about interaction choices and timings from the user's personalized store. Accordingly, the GAD Engine may collect user interaction choices and timings that unobtrusively extract evidence that a user favors (or disfavors) specific products or classes of products.
GAD Repository is a database that contains GAD from the GAD Engine and the AI and Semantic Engine. For example, the GAD repository may contain captured and filtered communications between users of a social network. Additionally, the GAD Repository may include learned weighting factors for vector components of a user's Person Shopping Genome Sequence. In another example, the GAD Repository may contain information about a user's wishes or aspirations based on analysis of an Internet store wish list (e.g., an Amazon wish list). Moreover, the GAD Repository may contain information about a user's purchase history at an Internet store (e.g., Amazon purchase history). In yet another example, the GAD Repository may contain information about interaction choices and timings from a user's personalized store. Further still, the GAD Repository may contain information that the user is currently in a bank or that the user has a new niece.
Additionally, the GAD Repository may contain data structures that describe the possible relations and connections between PSGS vectors and PGS vectors. The information in the GAD Repository may be updated (in whole or in part) periodically by the GAD Engine or AI and Semantic Engine. For instance, the database may be updated daily, weekly or at a selected time.
A non-limiting exemplary structure of Genome Annotation Data may be as follows: Person Shopping Genome ID, Item Shopping Genome ID, Record Type, Value, Date. In this example, the column “Person Shopping Genome ID” refers to a Person Shopping Genome that is associated with a particular user. The column “Item Shopping Genome ID” refers to a Product Genome Sequence that is associated with a particular product being offered for sale. The column “Record Type” refers to a parameter of interest for the user and the particular product being offered for sale. The column “Value” is a measure (or expression) of the state of relationship for the parameter of interest. The column “Date” refers to the calendar date that the data in the “Value” column were stored.
GAD may be stored in the GAD Repository in lines whose arguments correspond with the parameters associated with each column of the data structure. For example, one line of data that may be stored in the GAD Repository for the data structure described above may be as follows: 23, 21, likes, yes, Feb. 2, 2012. This line of information describes the relationship between the user associated with Person Shopping Genome ID #23 and the product associated with the Product Genome Sequence #21. The Record Type is “likes” (or product affinity), the “Value” (or argument for the Record Type) is yes, and the “Date” (or date of data entry) is Feb. 2, 2012.
In another example, the line of data may be as follows: 23, 21, has, yes, Feb. 2, 2012. This line of information describes the relationship between the user associated with Person Shopping Genome ID #23 and the product associated with the Product Genome Sequence #21. The Record Type is “has” (or product ownership), the “Value” (or argument for the Record Type) is yes, and the “Date” (or date of data entry) is Feb. 2, 2012.
In another example, the line of data may be as follows: 23, 21, viewduration, 0.33, 2/2/2012. This line of information describes the relationship between the user associated with Person Shopping Genome ID #23 and an offer for sale of the product associated with the Product Genome Sequence #21. The Record type is “viewduration” (or the elapsed time in milliseconds (ms) a user views the offering), the “Value” (or argument for the Record Type) is yes, and the “Date” (or date of data entry) is Feb. 2, 2012.
In yet another example, the line of data may be as follows: 23, NA, currentlocation, Bank-213ElmST—94301, 2/2/2012. This line of information describes the relationship between the user associated with Person Shopping Genome ID #23 and the user's location. The Record Type is “currentlocation” (or the current location of the user), the Value (or argument for the Record Type) is Bank-213ElmST—94301, and the Date (or date of data entry) is Feb. 2, 2012.
In yet another example, the line of data may be as follows: 23, 21, learningAlg1, −0.45, 2/2/2012. This line of information describes the relationship between the user associated with Person Shopping Genome ID #23 and the product associated with the Product Genome Sequence #21. The Record Type is “learningAlg1” (or the learned weight for recommendation algorithm 1), the Value (or argument for the Record Type) is −0.45, and the Date (or date of data entry) is Feb. 2, 2012.
As shown in
Merchant Raw Data Extractor 50 is a process for periodically obtaining advertising and sales information from Internet merchants for a targeted list of products. This process periodically searches the Internet and stores web pages from a number of online merchants (e.g., Amazon or eBay) to create a merchant raw data set. The stored web pages contain advertising information about products offered by the respective merchants. For example, one web page from an online retailer may include the product name, manufacturer, model number, class of goods or services, price, and a digital image. This information is stored in a Merchant Raw Data Repository database. This process may be performed by an automated software program that is controlled by a single user. Additionally, the automated software program may utilize an AI and Semantic Engine to identify, extract merchant pricing and associated information that is stored in the Merchant Raw Data Repository.
Merchant Raw Data Repository 52 is a database that contains normalized merchant pricing and other relevant information from the merchant raw data set. The normalized information in the Merchant Raw Data Repository may be updated (in whole or in part) as new merchant raw data sets are collected by the Merchant Raw Data Extractor. For instance, the database may be updated periodically during the day or at a selected time.
Price List Normalization Engine 54 is a process that analyzes the information stored in the Merchant Raw Data Repository and transforms this information into normalized pricing data for selected merchants and products. The Price List Normalization Engine may access the Merchant Raw Data Repository, analyze the web pages stored therein, and extract certain information from the stored web pages, and create a normalized data structure from the information.
For instance, Price List Normalization Engine 54 may create a merchant price look up table for selected products and merchants based on an analysis of the merchant raw data that are stored in the Merchant Raw Data Repository 52. Normalized data structures, such as merchant price look up tables, may be stored in the Merchant Product's Price List Repository 18. For example, the Merchant Product's Price List Repository may contain updated prices for the “Top 100” products advertised for sale by a selected sample of merchants.
Moreover, other information extracted from the merchant raw data set, which are considered relevant to completing an online transaction between the merchants and an online customer, may be extracted, normalized and saved in a data structure in the Merchant Product's Price List Repository 18. For example, the respective shipping terms and pricing may be extracted from the merchant raw data set, normalized and housed in the Merchant Product's Price List Repository. This process may be performed by an automated software program that is controlled by a single user. Additionally, the automated software program may utilize an AI and Semantic Engine to identify, extract, and normalize merchant pricing and associated information that is stored the Merchant Product's Price List Repository.
Merchant Price List Repository 18 is a database that contains normalized merchant pricing and other relevant information from the Merchant Raw Data Repository. The normalized information in the Merchant Price List Repository may be updated (in whole or in part) as new merchant raw data sets are collected by the Merchant Raw Data Extractor. For instance, the Price List Normalization Engine may update the normalized information in Merchant Price List Repository periodically during the day or at a selected time.
Recommendation, Advertising and Personalization (RAP) Engine 28 is a process that analyzes data from the Product Genome Sequence Repository 20, Person Shopping Genome Sequence Repository 22, Merchant Product's Price List Repository 18, and Genome Annotation Data Repository 24 (“the four cylinders”). Based on these analyses, the process interacts with users of a social network to recommend and facilitate personalized purchasing opportunities for selected products in the Merchant's Price List Repository. The process may further recommend and facilitate the resale of a user's goods as part of the purchasing opportunity.
The Recommendation Advertising and Personalization Engine (“RAP Engine”) 28 may include three or more paradigms for recommending products to users. On the most basic level, it may work on the Four Cylinders to calculate and determine whether there is a product in the merchant database that is suitable for a user of the social network. It also may work on the Four Cylinders to calculate and determine whether there is a product in the database that is suitable for a social network contact of the user. Moreover, the RAP Engine may operate on the Four Cylinders to calculate and determine whether there is a suitable product for another user in the social network that is not a contact of the user based on a comparison of the respective Person Shopping Genome sequences of the two users.
The recommended purchasing opportunities may be generated through weighted distance search calculations involving Person Shopping Genome Sequences and Product Genome Sequences. The weighted distance search calculations may include weighting factors for the vector components. Additionally, recommended transactional opportunities may be based on a weighted distance search between two Product Genome Sequences (i.e., item-based collaborative filtering) or between two Person Shopping Genome Sequences (i.e., user-based collaborative filtering).
For example, a first item-based collaborative filtering calculation may be performed by the RAP Engine that involves calculating a distance between a first Product Genome Sequence and a second Product Genome Sequence, the distance being a function of the differences between the n characteristics of the first Product Genome Sequence and the second Product Genome Sequence. The distance calculation may include the application of a weighting factor. The RAP Engine may then recommend the second product to a user based on the user's known affinity toward the first product and the magnitude of the distance. Thus, if a User 1 owns Product A, and Product B is close to Product A on some dimensions, the RAP Engine may recommend Product B to User 1.
A second item-based collaborative filtering calculation may be performed by the RAP Engine that involves calculating a first distance between a source Product Genome Sequence and a first Product Genome Sequence, the first distance being a function of the differences between the n characteristics of the source Product Genome Sequence and the first Product Genome Sequence. The first distance calculation may include the application of a weighting factor. The RAP engine may further calculate a second distance between the source Product Genome Sequence and a second Product Genome Sequence, the second distance being a function of the differences between the n characteristics of the source Product Genome Sequence and the second Product Genome Sequence. The second distance calculation may include the application of a weighting factor. The RAP Engine may recommend a product based on the magnitude of the first distance and the second distance.
In another example, a first user-based collaborative filtering calculation may be performed by the RAP Engine that involves calculating a distance between a first Person Shopping Genome Sequence and a second Person Shopping Sequence, the distance being a function of the differences between the n characteristics of the first Person Shopping Genome Sequence and a second Person Shopping Sequence. The distance calculation may include the application of a weighting factor. The RAP Engine may then recommend a product associated with the first user to the second user based on the magnitude of the distance. Thus, if a User 1 owns Product A, and the distance between the Person Shopping Genome Sequences of User 1 and User 2 is close on some dimensions, the RAP Engine may recommend Product A to User 2.
In another example, a content filtering calculation may be performed by the RAP Engine based on the purchase history (or demonstrated affinity) of a group of n users for a product. The calculation is based on the inference that elements common to the Person Shopping Genome Sequence of the n users define a Product Affinity Genome Model. The premise of the model is that other users who share the elements of Product Affinity Genome Model will share the group's interest in the product. The calculation may further involve sampling k randomly selected users who did not like the product, and removing globally similar elements identified in that population from the Product Affinity Genome Model. The resulting Product Affinity Genome Model then may be considered a unique signature of the Person Shopping Genome Sequence for that product. Then, the RAP engine may calculate the distance between an n+1 user's Person Shopping Genome Sequence and the Product Affinity Genome Model. Based on the magnitude of the distance between the n+1 user's Person Shopping Genome Sequence and the Product Affinity Genome Sequence, the RAP Engine may recommend the product to the n+1 user.
In another aspect, the RAP Engine 28 may operate on the results of continuous data analysis 26 to generate and display targeted advertising 60. For instance, the Advertising Engine Architecture allows the seller of a particular set of products to advertise those products to users with matching genomes. In this instantiation, the focus of the RAP Engine is to work on the Four Cylinders, to calculate, and determine whether there are users in the user database that are suitable for the seller's products.
In yet another aspect, the RAP Engine 28 may operate on the results of continuous data analysis 26 to generate and display personalized information 62. For instance, the Personalization Engine Architecture allows a merchant with a large set of products to provide a personalized shopping experience to a particular user. In this instantiation, the focus of the RAP Engine is to work on the Four Cylinders to rate the suitability of each product in the product set to the user. Then, a diverse set of highly suitable products may be displayed prominently to the user. By contrast, products with little or no suitability may be hidden from the user.
Referring to
Referring to
Referring to
Referring to
Referring to
In use, the apparatus and system of
For example, the RAP Engine may make a direct recommendation to a user based on an analysis of data in the four cylinders: A social network user has a Facebook account. The social network user has 130 social network contacts (or Friends) associated with the account. One year ago the social network user purchased an iPhone 4. The social network user posted a communication to the contacts in the user's social network stating that the user “is very happy with his new iPhone 4 purchase.” Soon afterward, the social network user scratches the glass cover of the device, and posts a communication to the user's contacts in the social network that “his phone fell out of his pocket on a recent business trip, scratching the front glass cover of the device.” The Social Raw Data Extractor saves potentially relevant parts of the webpage with this post to the Social Raw Data Repository. The AI and Semantic Engine analyze the communication, determine that the user owns a damaged iPhone 4, and update the user Personal Shopping Genome Sequence to reflect that the user owns a mobile communication device, that the product brand is Apple®, and that the product model is an iPhone 4. Based on an analysis of the user's Personal Shopping Genome Sequence and the Product Genome Sequence Repository, the RAP engine sends the user a recommendation to buy an iPhone 4S.
In another example, the RAP Engine evaluates the user's Personal Shopping Genome Sequence and finds that the user owns a mobile communication device, that the product brand is Apple®, that the product model is an iPhone 4, that the mobile communication device was purchased one year ago, and that it is damaged. Based on an analysis of the user's Personal Shopping Genome Sequence and the Product Genome Sequence Repository and the other cylinders, the RAP engine sends the user a recommendation to buy a cover for the iPhone 4.
In another example, a user purchases a new application for the mobile communication device. The user posts a communication to the contacts in the user's social network stating that the user “has a useful nutrition application that helped me improve my average pace for running a marathon by 30 seconds per mile.” Based on an analysis of the Personal Shopping Genome Sequences of the user and the user's social network contacts and the data in the Product Genome Sequence Repository and the other cylinders, the RAP engine sends the user an invitation to recommend the new application to one of the user's social network contacts, who enjoys swimming and owns a similar device, but does not use this application.
In another example, a user is aware of an upcoming birthday of a social network contact. The user posts a communication to contacts in the user's social network stating that “I have no idea what to get Jamie for her birthday.” Based on an analysis of the Personal Shopping Genome Sequences of the user's social network contacts, the data in the Product Genome Sequence Repository and the other cylinders, the RAP engine sends the user a recommendation to purchase the social network contact a massage and facial treatment service for a gift.
While it has been illustrated and described what at present are considered to be preferred embodiments of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made, and equivalents may be substituted for elements thereof without departing from the true scope of the invention. Additionally, features and/or elements from any embodiment may be used singly or in combination with other embodiments. Therefore, it is intended that this invention not be limited to the particular embodiments disclosed herein, but that the invention include all embodiments within the scope and the spirit of the present invention.
This application claims the benefit of U.S. patent application Ser. No. 61/595,682 filed on Feb. 6, 2012, the entire disclosure of which is incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
61595682 | Feb 2012 | US |