Patent Grant
10692014
The present disclosure generally relates to data processing systems. More specifically, the present disclosure relates to methods, systems and computer program products for identifying a set of messages to be sent to a plurality of member accounts of a social networking service.
A social networking service is a computer- or web-based application that enables users to establish links or connections with persons for the purpose of sharing information with one another. Some social networking services aim to enable friends and family to communicate with one another, while others are specifically directed to business users with a goal of enabling the sharing of business information. For purposes of the present disclosure, the terms “social network” and “social networking service” are used in a broad sense and are meant to encompass services aimed at connecting friends and family (often referred to simply as “social networks”), as well as services that are specifically directed to enabling business people to connect and share business information (also commonly referred to as “social networks” but sometimes referred to as “business networks”).
With many social networking services, members are prompted to provide a variety of personal information, which may be displayed in a member's personal web page. Such information is commonly referred to as personal profile information, or simply “profile information”, and when shown collectively, it is commonly referred to as a member's profile. For example, with some of the many social networking services in use today, the personal information that is commonly requested and displayed includes a member's age, gender, interests, contact information, home town, address, the name of the member's spouse and/or family members, and so forth. With certain social networking services, such as some business networking services, a member's personal information may include information commonly included in a professional resume or curriculum vitae, such as information about a person's education, employment history, skills, professional organizations, and so on. With some social networking services, a member's profile may be viewable to the public by default, or alternatively, the member may specify that only some portion of the profile is to be public by default. Accordingly, many social networking services serve as a sort of directory of people to be searched and browsed.
Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:
The present disclosure describes methods and systems for identifying a total minimum number messages to be sent to a plurality of member accounts that meets multiple constraints. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various aspects of different embodiments of the present invention. It will be evident, however, to one skilled in the art, that the present invention may be practiced without all of the specific details.
A system, a machine-readable storage medium storing instructions, and a computer-implemented method are described herein are directed to a Message Diet Engine that generates a pool of messages for a plurality member accounts of a social network service. Each message being of a respective message type from a plurality of message types and targeted to a specific member account. For each respective member account, the Message Diet Engine selects a minimum number of messages, from the pool of messages, targeted to the respective member account that prompts an expected social network activity target and avoids an expected number of complaints. Based on the selected minimum number of messages for each respective member account, the Message Diet Engine identifies a total minimum number of messages, from the pool of messages, to be sent to the plurality of member accounts that prompts an expected total social network activity target and avoids a total expected number of complaints.
According to various exemplary embodiments, the Message Diet Engine determines a minimum number of total messages sent to a plurality of member accounts such that the total minimum number of sent messages prompts a desired level of member account activity while avoiding receipt of a threshold number of complaints. The Message Diet Engine selects the messages from a pool of messages, where each message is already targeted for a particular member account from the plurality of member accounts. As such, each message in the pool of messages is inherently targeted for a member account to the exclusion of the other member accounts.
The Message Diet Engine collects historical data related to previous messages sent to various member accounts and the corresponding responses to each respective previous message. A response can be, for example, an increase in member account activity due to message receipt or a member account complaint due to message receipt. The Message Diet Engine builds and trains machine learning models (or regression models) based on the historical data. The Message Diet Engine builds an Expected Activity model and an Expected Complaints model. The Expected Activity model learns regression coefficients (hereinafter “w”) that represent how likely a type of message will prompt member account activity for a member account having a particular set of features or attributes. For example, a first w coefficient represents a likelihood that a first type of message sent to a member account having a first set of features will prompt increased engagement. A second w coefficient represents a likelihood that same first type of message sent to a member account having a second set of features will prompt increased engagement. A third w coefficient represents a likelihood that a second type of message sent to the member account having the first set of features will prompt the member account to become more active. A fourth w coefficient represents a likelihood that the same second type of message sent to the member account having the second set of features will prompt the member account to become more active. Therefore, each w regression coefficient of the Expected Activity model is based on a particular message type and a particular set of features or attributes of a given member account. There can be different versions of a w regression coefficient for each particular message type with respect to various sets of member account features. The Expected Activity model returns, for each member account, an expected probability output between 0-1 that represents how likely that member account will be active if a given set of messages (specifically targeted to the member account) is selected from the pool of messages and sent to the member account. It is understood that a feature, as used herein, is data, attribute(s) and/or a profile characteristic, of a given member account that has been learned by the Message Diet Engine 206 as being predictive of whether the given member account will perform an action with regard to a particular type of content, such as a message.
The Expected Complaints model learns regression coefficients (hereinafter “c”) that represent how likely a particular type of message will prompt a member account having a particular set of features or attributes to respond with complaint activity. For example, a first c coefficient represents a likelihood that the first type of message sent to a member account having the first set of features will prompt complaint activity by the member account. A second c coefficient represents a likelihood that the same first type of message sent to the member account having the second set of features will prompt complaint activity by the member account. A third c coefficient represents a likelihood that the second type of message sent to the member account having the first set of features will prompt complaint activity by the member account. A fourth c coefficient represents a likelihood that the same second type of message sent to the member account having the second set of features will prompt complaint activity by the member account. Therefore, similar to the Expected Activity model, each c regression coefficient of the Expected Activity model is based on a particular type of message and a particular set of features or attributes of a given member account. There can be different versions of a c regression coefficient for each particular message type with respect to various sets of member account features. The Expected Complaints model returns, for each member account, an expected number of complaints that may be received if a given set of messages (specifically targeted to the member account) is selected from the pool of messages and sent to the member account.
The Message Diet Engine builds and trains the Expected Activity model and the Expected Complaints model for the purpose of solving a multi-objective optimization problem. That is, the Message Diet Engine returns a total minimum number of messages to be sent to all of the plurality of member accounts that ensures a target expected level of overall member account activity, while not exceeding a threshold number of expected complaints received from the plurality of member accounts. However, the number of each type of messages in a set of messages to be sent to each respective member account is not initially known. Each amount of message types to be included in each set of messages to be sent to a respective member account has to be identified in order to determine whether the target expected level of overall member account activity can be met and whether the threshold number of expected complaints can be avoided.
As described in various embodiments, the Message Diet Engine may be a configuration-driven system for building, training, and deploying logistic regression models. In particular, the operation of the Message Diet Engine is completely configurable and customizable by a user through a user-supplied configuration file such as a JavaScript Object Notation (JSON), eXtensible Markup Language (XML) file, etc. For example, each module in the Message Diet Engine may have text associated with it in the configuration file that describes how the module is configured, the inputs to the module, the operations to be performed by the module on the inputs, the outputs from the module, and so on. Accordingly, the user may rearrange the way these modules are connected together as well as the rules that the various modules use to perform various operations. Thus, whereas conventional modeling is often performed in a fairly ad hoc and code driven manner, the modules of the Message Diet Engine may be configured in a modular and reusable fashion, to enable more efficient prediction modeling.
As understood by those skilled in the art, logistic regression is an example of a statistics-based machine learning technique that uses a logistic function. The logistic function is based on a variable, referred to as a logit. The logit is defined in terms of a set of regression coefficients of corresponding independent predictor variables. Logistic regression can be used to predict the probability of occurrence of an event given a set of independent/predictor variables.
The independent/predictor variables of the logistic regression model are the attributes represented by the assembled feature vectors described throughout. The regression coefficients may be estimated using maximum likelihood or learned through a supervised learning technique from data collected in logs or calculated from log data, as described in more detail below. Accordingly, once the appropriate regression coefficients are determined, the features included in the assembled feature vector may be plugged in to the logistic regression model in order to predict the probability that the event Y occurs (where the event Y may be, for example, whether the particular member account becomes more active). In other words, provided an assembled feature vector including various features associated with a particular member, the assembled feature vector may be applied to a logistic regression model to determine the probability that the particular member will respond to the particular content item in a particular way (e.g., click) given the particular context. Logistic regression is well understood by those skilled in the art, and will not be described in further detail herein, in order to avoid occluding various aspects of this disclosure.
The Message Diet Engine may use various other prediction modeling techniques understood by those skilled in the art to predict whether a particular member will click on a particular content item in a particular context. For example, other prediction modeling techniques may include other machine learning models such as a Naïve Bayes model, a support vector machines (SVM) model, a decision trees model, and a neural network model, all of which are understood by those skilled in the art.
According to various exemplary embodiments, the Message Diet Engine and associated user-supplied configuration file may be used for the purposes of both off-line training (for generating, training, and refining one or more machine learning models) and online inferences (for predicting expected member account activity and complaints).
It is understood that various embodiments further include encoded instructions that comprise operations to generate a user interface(s) and various user interface elements. The user interface and the various user interface elements can be displayed to be representative of any of the operations, models, expected activity, expected complaints and a set(s) of messages to be sent, as described herein. In addition, the user interface and various user interface elements are generated by the Message Diet Engine for display on a computing device, a server computing device, a mobile computing device, etc.
Turning now to
An Application Program Interface (API) server 114 and a web server 116 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 118. The application servers 118 host one or more applications 120. The application servers 118 are, in turn, shown to be coupled to one or more database servers 124 that facilitate access to one or more databases 126. While the applications 120 are shown in
Further, while the system 100 shown in
The web client 106 accesses the various applications 120 via the web interface supported by the web server 116. Similarly, the programmatic client 108 accesses the various services and functions provided by the applications 120 via the programmatic interface provided by the API server 114.
As shown in
As shown in
In some embodiments, the application logic layer 203 includes various application server modules 204, which, in conjunction with the user interface module(s) 202, generates various user interfaces (e.g., web pages) with data retrieved from various data sources in the data layer 205. In some embodiments, individual application server modules 204 are used to implement the functionality associated with various services and features of the professional social network. For instance, the ability of an organization to establish a presence in a social graph of the social network service, including the ability to establish a customized web page on behalf of an organization, and to publish messages or status updates on behalf of an organization, may be services implemented in independent application server modules 204. Similarly, a variety of other applications or services that are made available to members of the social network service may be embodied in their own application server modules 204.
As shown in
The profile data 216 may also include information regarding settings for members of the professional social network. These settings may comprise various categories, including, but not limited to, privacy and communications. Each category may have its own set of settings that a member may control.
Once registered, a member may invite other members, or be invited by other members, to connect via the professional social network. A “connection” may require a bi-lateral agreement by the members, such that both members acknowledge the establishment of the connection. Similarly, with some embodiments, a member may elect to “follow” another member. In contrast to establishing a connection, the concept of “following” another member typically is a unilateral operation, and at least with some embodiments, does not require acknowledgement or approval by the member that is being followed. When one member follows another, the member who is following may receive status updates or other messages published by the member being followed, or relating to various activities undertaken by the member being followed. Similarly, when a member follows an organization, the member becomes eligible to receive messages or status updates published on behalf of the organization. For instance, messages or status updates published on behalf of an organization that a member is following will appear in the member's personalized data feed or content stream. In any case, the various associations and relationships that the members establish with other members, or with other entities and objects, may be stored and maintained as social graph data within a social graph database 212.
The professional social network may provide a broad range of other applications and services that allow members the opportunity to share and receive information, often customized to the interests of the member. For example, with some embodiments, the professional social network may include a photo sharing application that allows members to upload and share photos with other members. With some embodiments, members may be able to self-organize into groups, or interest groups, organized around a subject matter or topic of interest. With some embodiments, the professional social network may host various job listings providing details of job openings with various organizations.
In some embodiments, the professional social network provides an application programming interface (API) module via which third-party applications can access various services and data provided by the professional social network. For example, using an API, a third-party application may provide a user interface and logic that enables an authorized representative of an organization to publish messages from a third-party application to a content hosting platform of the professional social network that facilitates presentation of activity or content streams maintained and presented by the professional social network. Such third-party applications may be browser-based applications, or may be operating system-specific. In particular, some third-party applications may reside and execute on one or more mobile devices (e.g., a smartphone, or tablet computing devices) having a mobile operating system.
The data layer 205 further includes a training data database 214 with training data 218 based on historical message data. The data layer 205 may be accessed, used, and adjusted by the Message Diet Engine 206 as will be described in more detail below in conjunction with
The Message Diet Engine 206 implements an Optimizer module 304 to determine each set of messages, from a pool of messages 302, to be sent to each respective member account. Using regression coefficients learned for the Expected Activity model 312 and the Expected Complaints model 316, the Optimizer module 304 continually cycles through various permutations of sets of messages 306, 308 to be sent to each respective member account. For each message set permutation, the Expected Activity model 312 returns a probability output between 0-1 indicating how likely a message set permutation will prompt the respective member account to become active and the Expected Complaints model 316 returns a number of expected complaints that will be received from a different message set permutation. It is understood that the Message Diet Engine 206 compares the probability output of the Expected Activity model 312 to the activity target 314 and the number of expected complaints returned from the Expected Complaints model 316. To the complaints threshold 318.
It is understood that each set of message permutations has various different number of type of messages. For example, a first message set permutation has 3 messages of a first message type, 2 messages of a second message type and 1 message of a third message type. A second message set permutation has 2 messages of the first message type, 2 messages of the second message type and 1 message of the third message type. A third message set permutation has 2 messages of the first message type, 3 messages of the second message type and 3 messages of the third message type. It is understood that the embodiments herein are not limited to only three message types.
As the Optimizer module 304 inputs various message set permutations 306, 308 into both the Expected Activity model 312 and the Expected Complaints model 316, a convergence detector 310 detects when the sets of messages identified by the Expected Activity model 312 and Expected Complaints 314 model converge to a select set of messages 316 that both prompts a desired level of member account activity while staying below the expected complaints threshold. The select set of messages 316 is thereby identified as a message set with a minimum number of messages, of various message types, that will meet the constraints (activity target 314, complaints threshold 318). It is understood that the activity target 314 represents an expected social network activity target and the complaints threshold 318 represents an expected number of complaints. It is understood that there can be multiple message set permutations, for a given member account, which meet the constraints of the activity target 314 and the complaints threshold 318. In the case of identifying multiple select message set permutations that meet the constraints, the Message Diet Engine 206 selects a select message set with the minimum number of messages.
The Optimizer module 304 computes a total minimum number of messages to be sent to all of the plurality of member accounts that meets or exceeds the target expected level of member account activity while staying at or below the threshold number of expected complaints. The set of messages permutation with the minimum number of messages is selected by the Optimizer module 304. In some embodiments, it is understood that that the Optimizer module 304 executes a Simplex algorithm.
At operation 410, the Message Diet Engine 206 generates a pool of messages for a plurality member accounts of a social network service, each message being of a respective message type from a plurality of message types and targeted to a specific member account. For example, the pool of message 302 includes a first plurality of messages for a first member account, a second plurality of messages for a second member account and a third plurality of messages for a third member account. The first, second and third plurality of message each include various amounts of messages of different message types.
At operation 415, for each respective member account, the Message Diet Engine 206 selects a minimum number of messages, from the pool of messages, targeted to the respective member account that prompts an expected social network activity target and avoids an expected number of complaints. For example, the Message Diet Engine 206 selects various permutations of sets of messages from the first plurality of messages targeted to the first member account. The Message Diet Engine 206 inputs various message set permutations into the expected activity model 312 and the expected complaints model 316. The expected activity model 312 provides an output indicating how much social network activity of the first member account will result from sending a given message set permutation to the first member account. The expected complaints model 316 provides an output indicating how many complaints will be received from the first member account as a result from sending a different message set permutation to the first member account.
As the various message set permutations are input into the expected activity model 312 and the expected complaints model 316, the various outputs are compared to an activity target 312 and a complaints threshold 318. The Message Diet Engine 206 monitors the output of the expected activity model 312 and the expected complaints model 316 with respect to the activity target 312 and a complaints threshold 318 in order to identify a message set permutation that both meets or exceeds the activity target 312 and falls below the complaints threshold 318. The Message Diet Engine 206 identifies a select message set permutation to be sent to the first member account.
The select message set permutation includes a total minimum number messages that, when sent to the first member account, both meets or exceeds the activity target 312 and falls below the complaints threshold 318. The select message set permutation include various amounts of message of different types. It is understood that the Message Diet Engine 206 performs similar operations with respect to message set permutations for the second member account and the third member account to identify respective select message set permutations to be sent to the second member account and the third member account. The embodiments described herein are not limited to a first, second and third member account.
At operation 420, based on the selected minimum number of messages for each respective member account, the Message Diet Engine 206 identifies a total minimum number of messages, from the pool of messages, to be sent to the plurality of member accounts that prompts an expected total social network activity target and avoids a total expected number of complaints. The Message Diet Engine 206 aggregates each select message set permutation identified for each member account. Since each respective select message set permutation includes a minimum number of messages for a given member account that exceeds the activity target 312 and falls below the complaints threshold 318, the aggregate message set will thereby meet an expected total social network activity target for all member accounts and avoids a total expected number of complaints received from all the member accounts. The Message Diet Engine 206 sends a least a portion of the aggregate message set within the social network service to corresponding member accounts.
The Message Diet Engine 206 collects historical message data. The historical message data includes a plurality of messages previously sent between various member accounts in the social network service and a respective response prompted by each previously sent message. A response can be an indication of a type of social network activity by a recipient member account in response to message receipt and can also be an indication of a complaint from the recipient member account in response to message receipt. For example, a complaint can be an unsubscribe action performed by the recipient member account and can be an identification of the previously sent message as a spam message performed by the recipient member account.
The Message Diet Engine 206 generates, based on the historical message data, an expected social network activity machine learning model 312 and an expected number of complaints machine learning model 316. The expected social network activity machine learning model 312 returns first output representing a probability that a given set of messages will prompt social network activity by a given member account. The expected number of complaints machine learning model 316 returns a number of expected number of complaints from the given member account due to receipt of a given set of messages. It is understood that a given set of messages includes various numbers of messages of one or more message types.
For the expected social network activity machine learning model 312, the Message Diet Engine 206 learns a first plurality of regression coefficients 515-1, 515-2, 515-3 . . . in order to express the probability of a target member account u being active for a first regression function in variables ni where ni is the number of emails of type i to be received by the target member account u. For example, the first regression function for the expected social network activity machine learning model 312 can be expressed as: au(n1, n2, . . . nT)=wu0+wu1 n1+wu2 n2+ . . . +wuT nT. It is understood that n1 represents any number of messages of a first message type and n2 represents any of messages of a second message type.
Each regression coefficient in the first plurality of regression coefficients 515-1, 515-2, 515-3 . . . represents a degree of importance in which a given message type prompts social network activity by a member account having a given set of a plurality of features. As shown in
For the expected number of complaints machine learning model 316, the Message Diet Engine 206 learns a second plurality of regression coefficients 525-1, 525-2, 525-3 . . . . Each regression coefficient in the second plurality of regression coefficients 525-1, 525-2, 525-3 . . . represents a degree of importance in which a given message type prompts a complaint by a member account having a given set of a plurality of features. As shown in
Upon the Message Diet Engine 206 having learned the first and second regression functions using the historical message data, the Optimizer module 304 solves a multi-objective optimization problem to in order to identify a select set of messages from the message pool 302 to be sent to each respective member account.
Each message in the message pool 302 can be represented as according to a variable of e. Within the message pool 302, let Eui denote a given set of messages which are targeted for a given member account u that are also of type i. In addition, ze denotes a probability of sending message e. As such, an expected number of messages of type i which will be received by user u is thereby represented as,
According to various embodiments, the multi-objective optimization problem can hereby be represented as follows:
minimize Ze Ze
such that
The Optimizer module 304 thereby implements the multi-objective optimization problem according to one or more encoded rules in order to calculate a solution ze for each message e.
In this manner, the disclosed Message Diet Engine 206 determines sets of messages for each member account in a plurality of member accounts that will prompt a target social network activity while avoiding receipt of an expected number of complaints.
Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the term “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation, and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., application program interfaces (APIs)).
Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry (e.g., a FPGA or an ASIC).
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that that both hardware and software architectures require consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed, in various example embodiments.
The input module 605 is a hardware-implemented module that controls, manages and stores information related to any inputs from one or more components of system 102 as illustrated in
The output module 610 is a hardware-implemented module that controls, manages and stores information related to which sends any outputs to one or more components of system 100 of
The expected activity learning module 615 is a hardware implemented module which manages, controls, stores, and accesses information related to building and updating an expected social network activity machine learning model (such as the expected activity model 312). The expected activity learning module 615 also implements and executes encoded rules representing the the expected social network activity machine learning model with respect to various message set permutations.
The expected complaints learning module 620 is a hardware-implemented module which manages, controls, stores, and accesses information related to to building and updating an expected number of complaints machine learning model (such as the expected complaints model 316). The expected complaints learning module 620 also implements and executes encoded rules representing the expected number of complaints machine learning model with respect to various message set permutations.
The message set permutations module 625 is a hardware-implemented module which manages, controls, stores, and accesses information related to generating one or more message set permutations for a given member account.
The convergence module 630 is a hardware-implemented module which manages, controls, stores, and accesses information related to determining when a message set permutation has been identified that prompts an expected social network activity target and avoids an expected number of complaints.
Example computer system 700 includes a processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 704, and a static memory 706, which communicate with each other via a bus 708. Computer system 700 may further include a video display device 710 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). Computer system 700 also includes an alphanumeric input device 712 (e.g., a keyboard), a user interface (UI) navigation device 714 (e.g., a mouse or touch sensitive display), a disk drive unit 716, a signal generation device 718 (e.g., a speaker) and a network interface device 720.
Disk drive unit 716 includes a machine-readable medium 722 on which is stored one or more sets of instructions and data structures (e.g., software) 724 embodying or utilized by any one or more of the methodologies or functions described herein. Instructions 724 may also reside, completely or at least partially, within main memory 704, within static memory 706, and/or within processor 702 during execution thereof by computer system 700, main memory 704 and processor 702 also constituting machine-readable media.
While machine-readable medium 722 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions or data structures. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present technology, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including by way of example semiconductor memory devices, e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
Instructions 724 may further be transmitted or received over a communications network 726 using a transmission medium. Instructions 724 may be transmitted using network interface device 720 and any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMAX networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the technology. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7143091 | Charnock | Nov 2006 | B2 |
| 8571930 | Galperin | Oct 2013 | B1 |
| 20110060649 | Dunk | Mar 2011 | A1 |
| 20110313842 | Avner | Dec 2011 | A1 |
| 20120272160 | Spivack | Oct 2012 | A1 |
| 20130018964 | Osipkov | Jan 2013 | A1 |
| 20130097019 | Ferber | Apr 2013 | A1 |
| 20130291105 | Yan | Oct 2013 | A1 |
| 20140229407 | White | Aug 2014 | A1 |
| 20140229487 | Mukund | Aug 2014 | A1 |
| 20150347924 | Zeng | Dec 2015 | A1 |
| 20160071162 | Ogawa | Mar 2016 | A1 |
| 20160239918 | Lambur | Aug 2016 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20170372038 A1 | Dec 2017 | US |
