Methods and systems for protecting data integrity
Disclosed implementations may include receiving a first communication comprising first content generated by a first user; identifying authentication metadata embedded within the first communication; receiving a second communication generated by a second user, wherein the second communication comprises second content and the authentication metadata; decoding the authentication metadata from the second communication; parsing the first content of the first communication and the second content of the second communication; determining that the first content is different than the second content based at least in part on the parsing; and generating an alteration notification based at least in part on the determining.
Latest Salesforce.com Patents:
An Application Data Sheet is filed concurrently with this specification as part of the present application. Each application that the present application claims benefit of or priority to as identified in the concurrently filed Application Data Sheet is incorporated by reference herein in its entirety and for all purposes.
COPYRIGHT NOTICEA portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the United States Patent and Trademark Office patent file or records but otherwise reserves all copyright rights whatsoever.
TECHNICAL FIELDThis patent document generally relates to data processing. More specifically, this patent document discloses techniques for protecting data integrity.
BACKGROUNDData integrity may refer to the accuracy and consistency (validity) of data over its lifecycle. Each time data is replicated or transferred, it should remain intact and unaltered. Data integrity can be compromised by hackers or people with ill intention. This can potentially cause the data to be mis-interpreted as being associated with a different context.
The included drawings are for illustrative purposes and serve only to provide examples of possible structures and process operations for the disclosed techniques. These drawings in no way limit any changes in form and detail that may be made to implementations by one skilled in the art without departing from the spirit and scope of the disclosure.
Some implementations may include systems and methods for enabling data integrity at an application server. For example, a method may include receiving a first communication comprising first content generated by a first user. Authentication metadata embedded within the first communication may be identified. A second communication generated by a second user may be received. The second communication may include second content and the authentication metadata. The authentication metadata from the second communication may be decoded. The first content of the first communication and the second content of the second communication may be parsed. Based at least in part on the parsing, it may be determined that the first content is different than the second content. An alteration notification may be generated based at least in part on the determining that the first content is different than the second content.
Some implementations may include systems and methods for protecting data integrity for data transmitted across a communication network. For example, a method may include storing data related to a first communication generated by a computer system associated with a first entity in a database. The data related to the first communication may include data associated with an identifier. The data related to the first communication may also include data related to first information associated with the identifier. The identifier may be used to identify the first entity. The systems and methods may further include receiving data related to a second communication generated by a computer system associated with a second entity. The data related to the second communication may include the data associated with the identifier. The data related to the second communication may also include data related to second information associated with the identifier. The second entity may be different from the first entity. When the data related to the second information is determined to be different from the data related to the first information, data related to a notification may be generated to indicate that the first information may have been altered, and the data related to the second communication may be updated to include the data related to the notification. The updated second communication may be stored in the database such that when a request for information associated with the identifier is received from a computer system associated with a third entity, both the data related to the first communication and the data related to the updated second communication may be transmitted to the computer system associated with the third entity.
Examples of systems, apparatus, methods and computer-readable storage media according to the disclosed implementations are described in this section. These examples are being provided solely to add context and aid in the understanding of the disclosed implementations. It will thus be apparent to one skilled in the art that implementations may be practiced without some or all of these specific details. In other instances, certain operations have not been described in detail to avoid unnecessarily obscuring implementations. Other applications are possible, such that the following examples should not be taken as definitive or limiting either in scope or setting.
In the following detailed description, references are made to the accompanying drawings, which form a part of the description and in which are shown, by way of illustration, specific implementations. Although these implementations are described in sufficient detail to enable one skilled in the art to practice the disclosed implementations, it is understood that these examples are not limiting, such that other implementations may be used and changes may be made without departing from their spirit and scope. For example, the operations of methods shown and described herein are not necessarily performed in the order indicated. It should also be understood that the methods may include more or fewer operations than are indicated. In some implementations, operations described herein as separate operations may be combined. Conversely, what may be described herein as a single operation may be implemented in multiple operations.
Some implementations of the disclosed systems, apparatus, methods and computer program products may be configured to include using a server computing system associated with a third party authentication service provider to authenticate images such that when the images are transmitted across a network from a sending computing system to a receiving computing system, an unaltered version of the image is received by the receiving computing system. For some implementations, when an altered version of the image is received, notification may be generated to indicate that the image has been altered.
Some implementations may include a system for enabling data integrity. The system may include one or more hardware processors and memory, the memory comprising computer program instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform storing data related to a first communication generated by a first entity in a database, the data related to the first communication including data associated with an identifier and data related to first information associated with the identifier, the identifier used to identify the first entity; receiving data related to a second communication generated by a second entity, the data related to the second communication including the data associated with the identifier and data related to second information associated with the identifier, the second entity being different from the first entity; and based on determining that the data related to the second information is different from the data related to the first information: (a) generating data related to an alteration notification; (b) updating the data related to the second communication to include the data related to the alteration notification; and (c) storing the updated data related to the second communication in the database.
For some implementations, an image may be associated with an encrypted signature. The encrypted signature (also referred to as a first encrypted signature) may be generated using a public key of a public and private key pair. The public and private key pair may be associated with the third-party authentication service provider. The encrypted signature may be generated based on the image data associated with the image. The encrypted signature may not be modified. For some implementations, the public key may be stored as metadata associated with the image. Metadata is generally the information that is used to understand how to interpret and use the data. For example, the metadata associated with an image may be stored in a database table, and link information may be used to link the metadata to the associated image data. Different techniques may be used to generate and store the metadata.
When an image is transmitted from a sending computing system to a receiving computer system, both the image data 150 and the encrypted signature 154 may be transmitted together. When the image data 150 is stored in a database, both the image data 150 and its encrypted signature 154 may be stored together. For example, the encrypted signature 154 may be stored as metadata associated with the image 150. For some implementations, the encrypted signature may be associated with data identifying the third-party authentication service provider. For example, the data identifying the third-party authentication service provider 158 may be stored as metadata associated with the image. The third-party authentication service provider may be associated with a server computing system that may be remote from a computer system that receives the image.
A client application 178 may be installed in a receiving computing system 174. The client application 178 may be configured to communicate with the server computing system 186 associated with the third-party authentication service provider to verify the integrity of the image data. For example, the client application 178 may be configured to be installed as an add-on to a browser of the receiving computing system 174. The client application 178 may be triggered when it detects the loading of an image by the browser. For example, the loading of an image may occur when a user uses the receiving computing system 174 to connect to a social network application executing in a social network server computing system 180 and opens a web page associated with the social network. The content of the web page may include images, and the integrity of one or more of the images may be protected by the third-party authentication service provider. For example, the content of the web page may include postings of members of a social network. The postings may include an original post and a repost of the original post.
The client application 178 may detect that an image is protected by the third-party authentication service provider by reviewing the metadata associated with the image. When an image is protected, the client application 178 may generate another encrypted signature (also referred to as a second encrypted signature) using the public key 162 and the image data 150 of the image received with the web page. The client application 178 may be configured to use the network 170 to transmit both the first encrypted signature and the second encrypted signature to the server computing system 186 associated with the third-party authentication service provider to verify whether the image has been altered. The third-party authentication service provider may use the private key 188 of the public private key pair to decrypt the first encrypted signature and the second encrypted signature. The private key 188 may be stored in the database 168. When the first encrypted signature is determined to be different from the second encrypted signature, the image data may have been altered, and the server computing system 186 associated with the third-party authentication service provider may communicate with the client application 178 to cause the client application 178 to generate a notification to indicate that the image may have been altered. For example, the image may have been altered by someone using the computing system 182 and use the application 184 to alter the image.
For some implementations, the operations described with the client application 178 may be performed by verification application 179 executing in the server computing system 180. For example, when a request is received to download a web page that includes images that are to be authenticated, the verification application 179 may communicate with the server computing system 186 to determine whether the image has been altered. For some implementations, the verification application 179 may perform its operations automatically after an image has been accessed and then subsequently stored in the database 181. Encrypted signatures may be used by the verification application 179 similar to the operations performed by the client application 178. Other authenticating techniques that do not make use of encrypted signatures may also be used to authenticate the image. When an image is determined to have been altered, the verification application 179 may cause a notification to be coupled with the image such that when the image is displayed on a web page, the notification may also be displayed.
For some implementations, the server computing system 186 associated with the third-party authentication service provider described above may be configured to authenticate image data and text data associated with the image data. When the image data and the text data are transmitted across a network from a sending computing system to a receiving computing system, the client application in the receiving computing system may be used to determine whether the image data and the text data have been altered. For some implementations, one or more of the image data and text data may be associated with a unique identifier. For example, the unique identifier may represent an entity. The unique identifier may be stored as metadata associated with the image.
For some implementations, one or more of the image data and the text data may be associated with a specific emotion. As such, when one or more of the image data and text data is altered, the specific emotion may also be altered. For some implementations, a neural network such as convolutional neural network or recurrent neural network may be used to detect emotion. The neural network may be trained using a training dataset such as, for example, a dataset of emotions. The dataset of emotions may include thousands of samples that may be linked to many possible emotions that may be conveyed by texts and/or images. For example, the range of emotions may include “happy”, “pleased”, “relaxed”, “calm”, “bored”, “depressed”, “annoy”, “afraid”, etc. Different machine learning techniques may be used to detect emotion from texts and from images. For example, a facial emotion detection using machine learning may be used to detect emotion of human included in images, and emotion detection from text using machine learning may be used to extract context from texts that can be attributed to an emotion. For some implementations, the neural network may be trained to detect sentiment associated with one or more of image and text data. For example, the neural network may be based on Einstein Artificial Intelligence (AI) technology developed by Salesforce.com of San Francisco, California.
For some implementations, an emotion that is detected from an image or from a text may be stored as metadata and may not be modified. When the image or text or both the image and text are sent from a sending computing system to a receiving computing system, the associated emotion metadata may also be sent. At the receiving computing system, a client application may be triggered by the receiving of the emotion metadata, and the emotion detection operations may be performed on the associated image or text or both. This emotion detection may enable the client application to verify whether the detected emotion is different from the emotion stored in the metadata, and whether one or both of the image and the text have been altered.
For some implementations, the verification to determine whether an image or a text has been altered may be performed by the server computing system that is configured to store the image or the text such as, for example, the server computing system 179. For example, when an emotion detection neural network associated with the server computing system 179 detects a difference in emotion between an original post and a repost of the original post, a notification about the difference may be generated by the server computing system 179 and stored in the database 181.
At block 192, a request to download or view a web page may be received. The web page may include images and texts. Some of the images and texts may be identified as images and texts that need to be authenticated. For example, the identification may be performed by evaluating the metadata associated with the image data and text data. At block 194, the server computing system may initiate a request to have the current version of images and texts authenticated. The current version may be the same as the original version if the images and texts have not been altered. The request may be transmitted to a server computing system associated with a third-party authentication service provider. The request may include information unique to an original version of the images and texts. For example, the information may be in the form of an encrypted signature.
At block 196, the third-party authentication service provider may perform comparison operations to verify the authentic nature of the current version of the images and texts. This may include, for example, performing the emotion detection operations using machine learning. Based on the third-party authentication service provider determining that the images and texts have been altered, the server computing system may be configured to generate a notification indicating information related to the alteration. At block 197, the notification may be coupled with the altered image or altered text. For example, the notification may be displayed on the web page adjacent to an altered image. At block 198, the web page may be transmitted to a computing system associated with the requester of the request to download the web page.
It may be noted that the techniques described with
In a conventional social networking system such as Twitter®, Facebook® or Yammer®, a user can easily mislead other users and tarnish a brand's reputation by commenting on, sharing, retweeting, reposting, or otherwise republishing a feed item such as a post mentioning the brand and editing the item's content. By way of illustration, Orlando's, a small but popular vegetarian-friendly restaurant, has published an advertisement as a post to a Facebook® feed viewable by various users, some of whom follow Orlando's. Oliver, a troublemaker, edits and reposts the content of the advertisement. In particular, Oliver adds a note in his repost stating that “Orlando's famous ranch dressing contains rendered pork lard,” even though in reality the dressing is entirely vegetarian. This misinformation could potentially alienate Orlando's large vegetarian customer base and, ultimately, devastate Orlando's business. Some of the disclosed techniques can be implemented to protect the content of Orlando's original post and hamper Oliver's ability to spread misinformation.
For instance, a communication such as a social networking post can be protected by embedding metadata within the communication's content. Such metadata could include specific information uniquely identifying a brand, referred to herein as a brand identifier. For instance, a unique string such as 183745 could be assigned to Orlando's Restaurant as a brand identifier, while other various entities are identified by different strings. In some implementations, metadata can be formatted as an image, which is placed within the content of a post. When the post is graphically displayed in a user interface, such an image can be obscured to users viewing the post, as explained in more detail below. By way of example, the string 183745 identifying Orlando's Restaurant can be embedded as Extensible Metadata Platform (XMP) metadata in a Joint Photographic Experts Group (JPEG) image file. Along these lines, a visible watermark image that is destroyed when tampered with, such as a logo identifying the Orlando's brand, can be included in Orlando's posts. Also or alternatively, a text checksum value can be generated for, and embedded in, each of Orlando's posts. Examples of techniques for embedding and interpreting metadata as well as characteristics of such metadata can vary greatly across implementations and are described in further detail below.
Using some of the disclosed techniques, Orlando's restaurant can in some ways control its brand reputation by placing metadata in posts published by or on behalf of Orlando's. In some implementations, if Oliver edits the content of Orlando's original post, Oliver can be prevented from publishing the edited post to social network feeds. Also or alternatively, an indication of tampering such as an animated red flag or text such as “warning: the following post has been edited” can be automatically added to the content of Oliver's edited version of Orlando's post when the edited post is published to a feed.
The disclosed techniques can be used to protect or authenticate a wide range of brand-affiliated content, since the type of brand can vary greatly across implementations. By way of illustration, Celia is both a sales agent and employee of the month at Touchstone Insurance, a corporation selling insurance. Celia has several personal brands in the form of her name, her job title as a sales agent, her role or position in an organizational hierarchy, and her badge(s), one of which is employee of the month. Touchstone Insurance also is a brand in the form of the name of the corporation. Confusingly for Rosalind, a Touchstone customer, Touchstone has thousands of sales agents each with their own set of brands, some of which are different from Celia's brands. Making matters worse, Rosalind often cannot tell the difference between a junk solicitation or scam and a legitimate communication from an actual agent, especially if the agent is not someone with whom Rosalind is familiar. Rosalind's confusion can be addressed if Touchstone Insurance were to embed metadata with brand identifiers in all of its communications from its employees such as Celia and other sales agents. The brand identifiers can be configured to indicate to customers that senders of the communications have brand equity or expertise within Touchstone. For instance, if Rosalind receives a communication from Celia, Rosalind can confirm Celia's expertise because the embedded metadata can be processed to authenticate Celia's status both as an agent at Touchstone and as employee of the month.
Embedding metadata in social networking communications to identify brands can also be useful in managing database records in a database system. For instance, records of posts or reposts containing embedded metadata can be identified in and organized using one or more database tables. By way of illustration, Audrey, a marketing manager, is evaluating the “all the world is a stage” marketing campaign to promote her theater company's recent outdoor productions throughout the Forest of Arden. Metadata can be embedded in all posts, using a variety of phrases, related to the “all the world is a stage” marketing campaign. Each time the metadata identifying the “all the world is a stage” marketing campaign appears in a post, a record of the post can be stored in a database. Audrey can then evaluate the campaign's effectiveness at a granular level by examining the database records to determine the effectiveness of each of the variety of phrases used in the campaign.
Some but not all of the techniques described or referenced herein are implemented as part of or in conjunction with a social networking system. Social networking systems have become a popular way to facilitate communication among people, any of whom can be recognized as users of a social networking system. One example of a social networking system is Chatter®, provided by salesforce.com, inc. of San Francisco, California. salesforce.com, inc. is a provider of social networking services, Customer Relationship Management (CRM) services and other database management services, any of which can be accessed and used in conjunction with the techniques disclosed herein in some implementations. These various services can be provided in a cloud computing environment, for example, in the context of a multi-tenant database system. Thus, the disclosed techniques can be implemented without having to install software locally, that is, on computing devices of users interacting with services available through the cloud. While the disclosed implementations are often described with reference to Chatter®, those skilled in the art should understand that the disclosed techniques are neither limited to Chatter® nor to any other services and systems provided by salesforce.com, inc. and can be implemented in the context of various other database systems and/or social networking systems such as Facebook®, LinkedIn®, Twitter®, Google+®, Yammer® and Jive® by way of example only.
Some social networking systems can be implemented in various settings, including organizations. For instance, a social networking system can be implemented to connect users within an enterprise such as a company or business partnership, or a group of users within such an organization. For instance, Chatter® can be used by employee users in a division of a business organization to share data, communicate, and collaborate with each other for various social purposes often involving the business of the organization. In the example of a multi-tenant database system, each organization or group within the organization can be a respective tenant of the system, as described in greater detail below.
In some social networking systems, users can access one or more social network feeds, which include information updates presented as items or entries in the feed. Such a feed item can include a single information update or a collection of individual information updates. A feed item can include various types of data including character-based data, audio data, image data and/or video data. A social network feed can be displayed in a graphical user interface (GUI) on a display device such as the display of a computing device as described below. The information updates can include various social network data from various sources and can be stored in an on-demand database service environment. In some implementations, the disclosed methods, apparatus, systems, and computer-readable storage media may be configured or designed for use in a multi-tenant database environment.
In some implementations, a social networking system may allow a user to follow data objects in the form of CRM records such as cases, accounts, or opportunities, in addition to following individual users and groups of users. The “following” of a record stored in a database, as described in greater detail below, allows a user to track the progress of that record when the user is subscribed to the record. Updates to the record, also referred to herein as changes to the record, are one type of information update that can occur and be noted on a social network feed such as a record feed or a news feed of a user subscribed to the record. Examples of record updates include field changes in the record, updates to the status of a record, as well as the creation of the record itself. Some records are publicly accessible, such that any user can follow the record, while other records are private, for which appropriate security clearance/permissions are a prerequisite to a user following the record.
Information updates can include various types of updates, which may or may not be linked with a particular record. For example, information updates can be social media communications submitted by a user or can otherwise be generated in response to user actions or in response to events. Examples of social media communications include: posts, comments, indications of a user's personal preferences such as “likes” and “dislikes”, updates to a user's status, uploaded files, and user-submitted hyperlinks to social network data or other network data such as various documents and/or web pages on the Internet. Posts can include alpha-numeric or other character-based user inputs such as words, phrases, statements, questions, emotional expressions, and/or symbols. Comments generally refer to responses to posts or to other information updates, such as words, phrases, statements, answers, questions, and reactionary emotional expressions and/or symbols. Multimedia data can be included in, linked with, or attached to a post or comment. For example, a post can include textual statements in combination with a JPEG image or animated image. A like or dislike can be submitted in response to a particular post or comment. Examples of uploaded files include presentations, documents, multimedia files, and the like.
Users can follow a record by subscribing to the record, as mentioned above. Users can also follow other entities such as other types of data objects, other users, and groups of users. Feed tracked updates regarding such entities are one type of information update that can be received and included in the user's news feed. Any number of users can follow a particular entity and thus view information updates pertaining to that entity on the users' respective news feeds. In some social networks, users may follow each other by establishing connections with each other, sometimes referred to as “friending” one another. By establishing such a connection, one user may be able to see information generated by, generated about, or otherwise associated with another user. For instance, a first user may be able to see information posted by a second user to the second user's personal social network page. One implementation of such a personal social network page is a user's profile page, for example, in the form of a web page representing the user's profile. In one example, when the first user is following the second user, the first user's news feed can receive a post from the second user submitted to the second user's profile feed. A user's profile feed is also referred to herein as the user's “wall,” which is one example of a social network feed displayed on the user's profile page.
In some implementations, a social network feed may be specific to a group of users of a social networking system. For instance, a group of users may publish a news feed. Members of the group may view and post to this group feed in accordance with a permissions configuration for the feed and the group. Information updates in a group context can also include changes to group status information.
In some implementations, when data such as posts or comments input from one or more users are submitted to a social network feed for a particular user, group, object, or other construct within a social networking system, an email notification or other type of network communication may be transmitted to all users following the user, group, or object in addition to the inclusion of the data as a feed item in one or more feeds, such as a user's profile feed, a news feed, or a record feed. In some social networking systems, the occurrence of such a notification is limited to the first instance of a published input, which may form part of a larger conversation. For instance, a notification may be transmitted for an initial post, but not for comments on the post. In some other implementations, a separate notification is transmitted for each such information update.
The term “multi-tenant database system” generally refers to those systems in which various elements of hardware and/or software of a database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows of data such as feed items for a potentially much greater number of customers.
An example of a “user profile” or “user's profile” is a database object or set of objects configured to store and maintain data about a given user of a social networking system and/or database system. The data can include general information, such as name, title, phone number, a photo, a biographical summary, and a status, e.g., text describing what the user is currently doing. As mentioned below, the data can include social media communications created by other users. Where there are multiple tenants, a user is typically associated with a particular tenant. For example, a user could be a salesperson of a company, which is a tenant of the database system that provides a database service.
The term “record” generally refers to a data entity having fields with values and stored in database system. An example of a record is an instance of a data object created by a user of the database service, for example, in the form of a CRM record about a particular (actual or potential) business relationship or project. The record can have a data structure defined by the database service (a standard object) or defined by a user (custom object). For example, a record can be for a business partner or potential business partner (e.g., a client, vendor, distributor, etc.) of the user, and can include information describing an entire company, subsidiaries, or contacts at the company. As another example, a record can be a project that the user is working on, such as an opportunity (e.g., a possible sale) with an existing partner, or a project that the user is trying to get. In one implementation of a multi-tenant database system, each record for the tenants has a unique identifier stored in a common table. A record has data fields that are defined by the structure of the object (e.g., fields of certain data types and purposes). A record can also have custom fields defined by a user. A field can be another record or include links thereto, thereby providing a parent-child relationship between the records.
The terms “social network feed” and “feed” are used interchangeably herein and generally refer to a combination (e.g., a list) of feed items or entries with various types of information and data. Such feed items can be stored and maintained in one or more database tables, e.g., as rows in the table(s), that can be accessed to retrieve relevant information to be presented as part of a displayed feed. The term “feed item” (or feed element) generally refers to an item of information, which can be presented in the feed such as a post submitted by a user. Feed items of information about a user can be presented in a user's profile feed of the database, while feed items of information about a record can be presented in a record feed in the database, by way of example. A profile feed and a record feed are examples of different types of social network feeds. A second user following a first user and a record can receive the feed items associated with the first user and the record for display in the second user's news feed, which is another type of social network feed. In some implementations, the feed items from any number of followed users and records can be combined into a single social network feed of a particular user.
As examples, a feed item can be a social media communication, such as a user-generated post of text data, and a feed tracked update to a record or profile, such as a change to a field of the record. Feed tracked updates are described in greater detail below. A feed can be a combination of social media communications and feed tracked updates. Social media communications include text created by a user, and may include other data as well. Examples of social media communications include posts, user status updates, and comments. Social media communications can be created for a user's profile or for a record. Posts can be created by various users, potentially any user, although some restrictions can be applied. As an example, posts can be made to a wall section of a user's profile page (which can include a number of recent posts) or a section of a record that includes multiple posts. The posts can be organized in chronological order when displayed in a GUI, for instance, on the user's profile page, as part of the user's profile feed. In contrast to a post, a user status update changes a status of a user and can be made by that user or an administrator. A record can also have a status, the update of which can be provided by an owner of the record or other users having suitable write access permissions to the record. The owner can be a single user, multiple users, or a group.
In some implementations, a comment can be made on any feed item. In some implementations, comments are organized as a list explicitly tied to a particular feed tracked update, post, or status update. In some implementations, comments may not be listed in the first layer (in a hierarchal sense) of feed items, but listed as a second layer branching from a particular first layer feed item.
A “feed tracked update,” also referred to herein as a “feed update,” is one type of information update and generally refers to data representing an event. A feed tracked update can include text generated by the database system in response to the event, to be provided as one or more feed items for possible inclusion in one or more feeds. In one implementation, the data can initially be stored, and then the database system can later use the data to create text for describing the event. Both the data and/or the text can be a feed tracked update, as used herein. In various implementations, an event can be an update of a record and/or can be triggered by a specific action by a user. Which actions trigger an event can be configurable. Which events have feed tracked updates created and which feed updates are sent to which users can also be configurable. Social media communications and other types of feed updates can be stored as a field or child object of the record. For example, the feed can be stored as a child object of the record.
A “group” is generally a collection of users. In some implementations, the group may be defined as users with a same or similar attribute, or by membership. In some implementations, a “group feed”, also referred to herein as a “group news feed”, includes one or more feed items about any user in the group. In some implementations, the group feed also includes information updates and other feed items that are about the group as a whole, the group's purpose, the group's description, and group records and other objects stored in association with the group. Threads of information updates including group record updates and social media communications, such as posts, comments, likes, etc., can define group conversations and change over time.
An “entity feed” or “record feed” generally refers to a feed of feed items about a particular record in the database. Such feed items can include feed tracked updates about changes to the record and posts made by users about the record. An entity feed can be composed of any type of feed item. Such a feed can be displayed on a page such as a web page associated with the record, e.g., a home page of the record. As used herein, a “profile feed” or “user's profile feed” generally refers to a feed of feed items about a particular user. In one example, the feed items for a profile feed include posts and comments that other users make about or send to the particular user, and status updates made by the particular user. Such a profile feed can be displayed on a page associated with the particular user. In another example, feed items in a profile feed could include posts made by the particular user and feed tracked updates initiated based on actions of the particular user.
In
In this example, content 300 identifies the brand “Orlando's” 304, which is the name of a business organization. In other examples, the brand could be a product name such as Orlando's famous ranch dressing. In some implementations, a brand might be a service name such as Charles the Wrestler's premium Tae Kwon Do lessons, a job title such as Vice President of Marketing, or a badge, which could indicate expertise in a particular area. A brand could even be a personal role such as “Queen of Sales”, which could describe the saleswoman who has had the highest number of sales in a given year.
In
Returning to
Also or alternatively, first content 300 can include contextual information such as a location from which first content 300 was posted. By way of example, location services such as Near Field Communications (NFC) or iBeacons® can be used to determine the location of a user's computing device when post 200 is sent from the computing device at 104. A map system such as Google Maps® can then be used to determine that post 200 was sent from Orlando's Restaurant in the Forest of Arden. Information identifying that post 200 was sent from Orlando's Restaurant can then be included in first content 300.
Alternatively, at 108, metadata can be identified as being embedded in content 300. By way of example, metadata 308 may have already been embedded in post 200 by an employee of Orlando's before post 200 is received by a server. In this scenario, since metadata 308 has already been embedded in post 200 at the time that post 200 is received by a server, metadata 308 can be identified in the content of post 200.
The dotted line surrounding metadata 308 in
Embedded metadata 308 can contain a wide variety of information including a brand identifier 310 for Orlando's Restaurant. Several other non-limiting examples of information that might be contained in metadata 308 are described below. For instance, embedded metadata 308 might include a reference to content 300, post 200, or both. In some scenarios, such as when a communication is part of a conversation in a feed, embedded metadata 308 could include a reference to the conversation. Additionally, in some situations, when for example a post is part of an ongoing editing process, embedded metadata 308 can include an identification of a version of the first content, a history of edits to the first content, or both. Also or alternatively, embedded metadata 308 can include programmable logic that identifies the first content and prevents it from being edited.
Returning to
In some implementations, content 312 of post 208 includes an edited version 316 of content 300 of post 200. In the example of
Returning to
One skilled in the art will appreciate that existing techniques, such as public key cryptography, could serve as or be combined with some of the disclosed encoding/decoding techniques for extra security. For example, a public key to decode embedded metadata 308 could be provided to social networking users, while a private key to encode metadata 308 could be provided exclusively to a business, such as Orlando's Restaurant. Thus, any social networking user could view content posted by Orlando's Restaurant, but only Orlando's Restaurant would be able to generate official and original content containing metadata 308.
Returning to
In
In
Data generated at 128 of
In some implementations, in response to detecting any modifications to brand-associated content or even a keystroke in which a user attempts to modify content, a user can be prevented from publishing any such modified content. For example,
In some other implementations, the disclosed techniques can be used to trigger an offer or coupon for a wide variety of products or services. By way of example, Aliena is an avid Ganymede Cola drinker and a loyal Ganymede customer. Metadata embedded in Ganymede's social networking posts contains a brand identifier as well as an offer or coupon such that the offer coupon is generated for a user who shares or republishes content including the embedded metadata. If Aliena reposts or shares a Ganymede advertisement containing such metadata, an electronic offer or coupon can be emailed to Aliena's email account. This may incentivize users to share content and increase brand exposure for Ganymede Cola.
Systems, apparatus, and methods are described below for implementing database systems and enterprise level social and business information networking systems in conjunction with the disclosed techniques. Such implementations can provide more efficient use of a database system. For instance, a user of a database system may not easily know when important information in the database has changed, e.g., about a project or client. Such implementations can provide feed tracked updates about such changes and other events, thereby keeping users informed.
By way of example, a user can update a record in the form of a CRM object, e.g., an opportunity such as a possible sale of 1000 computers. Once the record update has been made, a feed tracked update about the record update can then automatically be provided, e.g., in a feed, to anyone subscribing to the opportunity or to the user. Thus, the user does not need to contact a manager regarding the change in the opportunity, since the feed tracked update about the update is sent via a feed to the manager's feed page or other page.
A user system 12 may be implemented as any computing device(s) or other data processing apparatus such as a machine or system used by a user to access a database system 16. For example, any of user systems 12 can be a handheld and/or portable computing device such as a mobile phone, a smartphone, a laptop computer, or a tablet. Other examples of a user system include computing devices such as a work station and/or a network of computing devices. As illustrated in
An on-demand database service, implemented using system 16 by way of example, is a service that is made available to users who do not need to necessarily be concerned with building and/or maintaining the database system. Instead, the database system may be available for their use when the users need the database system, i.e., on the demand of the users. Some on-demand database services may store information from one or more tenants into tables of a common database image to form a multi-tenant database system (MTS). A database image may include one or more database objects. A relational database management system (RDBMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system. In some implementations, application platform 18 enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12, or third party application developers accessing the on-demand database service via user systems 12.
The users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, when a salesperson is using a particular user system 12 to interact with system 16, the user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level, also called authorization.
Network 14 is any network or combination of networks of devices that communicate with one another. For example, network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. Network 14 can include a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the Internet. The Internet will be used in many of the examples herein. However, it should be understood that the networks that the present implementations might use are not so limited.
User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP signals to and from an HTTP server at system 16. Such an HTTP server might be implemented as the sole network interface 20 between system 16 and network 14, but other techniques might be used as well or instead. In some implementations, the network interface 20 between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least for users accessing system 16, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
In one implementation, system 16, shown in
One arrangement for elements of system 16 is shown in
Several elements in the system shown in
According to one implementation, each user system 12 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 16 (and additional instances of an MTS, where more than one is present) and all of its components might be operator configurable using application(s) including computer code to run using processor system 17, which may be implemented to include a central processing unit, which may include an Intel Pentium® processor or the like, and/or multiple processor units. Non-transitory computer-readable media can have instructions stored thereon/in, that can be executed by or used to program a computing device to perform any of the methods of the implementations described herein. Computer program code 26 implementing instructions for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein is preferably downloadable and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any other type of computer-readable medium or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for the disclosed implementations can be realized in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VB Script, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).
According to some implementations, each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16. As such, system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to refer to one type of computing device such as a system including processing hardware and process space(s), an associated storage medium such as a memory device or database, and, in some instances, a database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database objects described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
User system 12, network 14, system 16, tenant data storage 22, and system data storage 24 were discussed above in
Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 54 managed by tenant management process 60 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32. A detailed description of some PL/SOQL language implementations is discussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, issued on Jun. 1, 2010, and hereby incorporated by reference in its entirety and for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 66 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
Each application server 50 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23, via a different network connection. For example, one application server 501 might be coupled via the network 14 (e.g., the Internet), another application server 50N-1 might be coupled via a direct network link, and another application server 50N might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 50 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.
In certain implementations, each application server 50 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 50. In one implementation, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 50 and the user systems 12 to distribute requests to the application servers 50. In one implementation, the load balancer uses a least connections algorithm to route user requests to the application servers 50. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain implementations, three consecutive requests from the same user could hit three different application servers 50, and three requests from different users could hit the same application server 50. In this manner, by way of example, system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant-specific data, system 16 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.
In certain implementations, user systems 12 (which may be client systems) communicate with application servers 50 to request and update system-level and tenant-level data from system 16 that may involve sending one or more queries to tenant data storage 22 and/or system data storage 24. System 16 (e.g., an application server 50 in system 16) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 24 may generate query plans to access the requested data from the database.
Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects according to some implementations. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for case, account, contact, lead, and opportunity data objects, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.
In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. Commonly assigned U.S. Pat. No. 7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM, by Weissman et al., issued on Aug. 17, 2010, and hereby incorporated by reference in its entirety and for all purposes, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain implementations, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.
As shown in
Moreover, one or more of the devices in the on-demand database service environment 900 may be implemented on the same physical device or on different hardware. Some devices may be implemented using hardware or a combination of hardware and software. Thus, terms such as “data processing apparatus,” “machine,” “server” and “device” as used herein are not limited to a single hardware device, but rather include any hardware and software configured to provide the described functionality.
The cloud 904 is intended to refer to a data network or combination of data networks, often including the Internet. Client machines located in the cloud 904 may communicate with the on-demand database service environment to access services provided by the on-demand database service environment. For example, client machines may access the on-demand database service environment to retrieve, store, edit, and/or process information.
In some implementations, the edge routers 908 and 912 route packets between the cloud 904 and other components of the on-demand database service environment 900. The edge routers 908 and 912 may employ the Border Gateway Protocol (BGP). The BGP is the core routing protocol of the Internet. The edge routers 908 and 912 may maintain a table of IP networks or ‘prefixes’, which designate network reachability among autonomous systems on the Internet.
In one or more implementations, the firewall 916 may protect the inner components of the on-demand database service environment 900 from Internet traffic. The firewall 916 may block, permit, or deny access to the inner components of the on-demand database service environment 900 based upon a set of rules and other criteria. The firewall 916 may act as one or more of a packet filter, an application gateway, a stateful filter, a proxy server, or any other type of firewall.
In some implementations, the core switches 920 and 924 are high-capacity switches that transfer packets within the on-demand database service environment 900. The core switches 920 and 924 may be configured as network bridges that quickly route data between different components within the on-demand database service environment. In some implementations, the use of two or more core switches 920 and 924 may provide redundancy and/or reduced latency.
In some implementations, the pods 940 and 944 may perform the core data processing and service functions provided by the on-demand database service environment. Each pod may include various types of hardware and/or software computing resources. An example of the pod architecture is discussed in greater detail with reference to
In some implementations, communication between the pods 940 and 944 may be conducted via the pod switches 932 and 936. The pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and client machines located in the cloud 904, for example via core switches 920 and 924. Also, the pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and the database storage 956.
In some implementations, the load balancer 928 may distribute workload between the pods 940 and 944. Balancing the on-demand service requests between the pods may assist in improving the use of resources, increasing throughput, reducing response times, and/or reducing overhead. The load balancer 928 may include multilayer switches to analyze and forward traffic.
In some implementations, access to the database storage 956 may be guarded by a database firewall 948. The database firewall 948 may act as a computer application firewall operating at the database application layer of a protocol stack. The database firewall 948 may protect the database storage 956 from application attacks such as structure query language (SQL) injection, database rootkits, and unauthorized information disclosure.
In some implementations, the database firewall 948 may include a host using one or more forms of reverse proxy services to proxy traffic before passing it to a gateway router. The database firewall 948 may inspect the contents of database traffic and block certain content or database requests. The database firewall 948 may work on the SQL application level atop the TCP/IP stack, managing applications' connection to the database or SQL management interfaces as well as intercepting and enforcing packets traveling to or from a database network or application interface.
In some implementations, communication with the database storage 956 may be conducted via the database switch 952. The multi-tenant database storage 956 may include more than one hardware and/or software components for handling database queries. Accordingly, the database switch 952 may direct database queries transmitted by other components of the on-demand database service environment (e.g., the pods 940 and 944) to the correct components within the database storage 956.
In some implementations, the database storage 956 is an on-demand database system shared by many different organizations. The on-demand database service may employ a multi-tenant approach, a virtualized approach, or any other type of database approach. On-demand database services are discussed in greater detail with reference to
In some implementations, the app servers 988 may include a hardware and/or software framework dedicated to the execution of procedures (e.g., programs, routines, scripts) for supporting the construction of applications provided by the on-demand database service environment 900 via the pod 944. In some implementations, the hardware and/or software framework of an app server 988 is configured to execute operations of the services described herein, including performance of one or more of the operations of methods described herein with reference to
The content batch servers 964 may handle requests internal to the pod. These requests may be long-running and/or not tied to a particular customer. For example, the content batch servers 964 may handle requests related to log mining, cleanup work, and maintenance tasks.
The content search servers 968 may provide query and indexer functions. For example, the functions provided by the content search servers 968 may allow users to search through content stored in the on-demand database service environment.
The file servers 986 may manage requests for information stored in the file storage 998. The file storage 998 may store information such as documents, images, and basic large objects (BLOBs). By managing requests for information using the file servers 986, the image footprint on the database may be reduced.
The query servers 982 may be used to retrieve information from one or more file systems. For example, the query system 982 may receive requests for information from the app servers 988 and then transmit information queries to the NFS 996 located outside the pod.
The pod 944 may share a database instance 990 configured as a multi-tenant environment in which different organizations share access to the same database. Additionally, services rendered by the pod 944 may call upon various hardware and/or software resources. In some implementations, the ACS servers 980 may control access to data, hardware resources, or software resources.
In some implementations, the batch servers 984 may process batch jobs, which are used to run tasks at specified times. Thus, the batch servers 984 may transmit instructions to other servers, such as the app servers 988, to trigger the batch jobs.
In some implementations, the QFS 992 may be an open source file system available from Sun Microsystems® of Santa Clara, California. The QFS may serve as a rapid-access file system for storing and accessing information available within the pod 944. The QFS 992 may support some volume management capabilities, allowing many disks to be grouped together into a file system. File system metadata can be kept on a separate set of disks, which may be useful for streaming applications where long disk seeks cannot be tolerated. Thus, the QFS system may communicate with one or more content search servers 968 and/or indexers 994 to identify, retrieve, move, and/or update data stored in the network file systems 996 and/or other storage systems.
In some implementations, one or more query servers 982 may communicate with the NFS 996 to retrieve and/or update information stored outside of the pod 944. The NFS 996 may allow servers located in the pod 944 to access information to access files over a network in a manner similar to how local storage is accessed.
In some implementations, queries from the query servers 922 may be transmitted to the NFS 996 via the load balancer 928, which may distribute resource requests over various resources available in the on-demand database service environment. The NFS 996 may also communicate with the QFS 992 to update the information stored on the NFS 996 and/or to provide information to the QFS 992 for use by servers located within the pod 944.
In some implementations, the pod may include one or more database instances 990. The database instance 990 may transmit information to the QFS 992. When information is transmitted to the QFS, it may be available for use by servers within the pod 944 without using an additional database call.
In some implementations, database information may be transmitted to the indexer 994. Indexer 994 may provide an index of information available in the database 990 and/or QFS 992. The index information may be provided to file servers 986 and/or the QFS 992.
While some of the disclosed implementations may be described with reference to a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the disclosed implementations are not limited to multi-tenant databases nor deployment on application servers. Some implementations may be practiced using various database architectures such as ORACLE®, DB2® by IBM and the like without departing from the scope of the implementations claimed.
It should be understood that some of the disclosed implementations can be embodied in the form of control logic using hardware and/or computer software in a modular or integrated manner. Other ways and/or methods are possible using hardware and a combination of hardware and software.
Any of the disclosed implementations may be embodied in various types of hardware, software, firmware, and combinations thereof. For example, some techniques disclosed herein may be implemented, at least in part, by computer-readable media that include program instructions, state information, etc., for performing various services and operations described herein. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher-level code that may be executed by a computing device such as a server or other data processing apparatus using an interpreter. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as flash memory, compact disk (CD) or digital versatile disk (DVD); magneto-optical media; and hardware devices specially configured to store program instructions, such as read-only memory (“ROM”) devices and random access memory (“RAM”) devices. A computer-readable medium may be any combination of such storage devices.
Any of the operations and techniques described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer-readable medium. Computer-readable media encoded with the software/program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer-readable medium may reside on or within a single computing device or an entire computer system, and may be among other computer-readable media within a system or network. A computer system or computing device may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.
While various implementations have been described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present application should not be limited by any of the implementations described herein, but should be defined only in accordance with the following and later-submitted claims and their equivalents.
Claims
1. A computer-implemented method comprising:
- receiving, by an application server, a first communication comprising first content generated by a first user;
- identifying authentication metadata embedded within the first communication, the authentication metadata comprising data associated with the first user;
- receiving, by the application server, a second communication generated by a second user, the second communication comprising second content and the authentication metadata;
- determining if the authentication metadata from the second communication belongs to the first user by at least processing the authentication metadata from the second communication and the authentication metadata from the first communication;
- parsing, by the application server, the first content of the first communication and the second content of the second communication;
- comparing, by the application server, the first content with the second content in response to determining that the authentication metadata from the second communication belongs to the first user;
- determining that the first content is different than the second content based at least in part on the parsing and the comparing; and
- based at least in part on the determining that the first content is different than the second content, sharing, on a social network system, a version of the second communication, the version comprising an alteration notification indicating that information of the second content has been altered.
2. The method of claim 1, further comprising:
- embedding, by the application server, the authentication metadata into the first communication.
3. The method of claim 1, wherein identifying the authentication metadata comprises:
- decoding the authentication metadata in the received first communication.
4. The method of claim 1, wherein the authentication metadata comprises location information associated with the first user.
5. The method of claim 1, wherein the authentication metadata embedded within the first communication indicates an identity of the first user.
6. The method of claim 1, further comprising:
- preventing display of the second communication based at least in part on the determining that the first content is different than the second content.
7. The method of claim 1, wherein the second communication comprises an edited version of the first communication.
8. A system comprising:
- a memory; and
- one or more hardware processors configured to cause:
- obtaining a first communication comprising first content generated by a first user;
- identifying authentication metadata embedded within the first communication, the authentication metadata comprising data associated with the first user;
- obtaining a second communication generated by a second user, the second communication comprising second content and the authentication metadata;
- determining if the authentication metadata from the second communication belongs to the first user by at least processing the authentication metadata from the second communication and the authentication metadata from the first communication;
- parsing the first content of the first communication and the second content of the second communication;
- comparing the first content with the second content in response to determining that the authentication metadata from the second communication belongs to the first user;
- determining that the first content is different than the second content based at least in part on the parsing and the comparing; and
- based at least in part on the determining that the first content is different than the second content, sharing, on a social network system, a version of the second communication, the version comprising an alteration notification indicating that information of the second content has been altered.
9. The system of claim 8, the one or more hardware processors further configured to cause:
- embedding the authentication metadata into the first communication.
10. The system of claim 8, wherein identifying the authentication metadata comprises:
- decoding the authentication metadata in the obtained first communication.
11. The system of claim 8, wherein the authentication metadata comprises location information associated with the first user.
12. The system of claim 8, wherein the authentication metadata embedded within the first communication indicates an identity of the first user.
13. The system of claim 8, the one or more hardware processors further configured to cause:
- preventing display of the second communication based at least in part on the determining that the first content is different than the second content.
14. The system of claim 8, wherein the second communication comprises an edited version of the first communication.
15. A computer program product comprising a non-transitory computer-readable medium storing computer-readable program code to be executed by one or more processors, the program code comprising instructions configured to cause:
- obtaining a first communication comprising first content generated by a first user;
- identifying authentication metadata embedded within the first communication, the authentication metadata comprising data associated with the first user;
- obtaining a second communication generated by a second user, the second communication comprising second content and the authentication metadata;
- determining if the authentication metadata from the second communication belongs to the first user by at least processing the authentication metadata from the second communication and the authentication metadata from the first communication;
- parsing the first content of the first communication and the second content of the second communication;
- comparing the first content with the second content in response to determining that the authentication metadata from the second communication belongs to the first user;
- determining that the first content is different than the second content based at least in part on the parsing and the comparing; and
- based at least in part on the determining that the first content is different than the second content, sharing, on a social network system, a version of the second communication, the version comprising an alteration notification indicating that information of the second content has been altered.
16. The computer program product of claim 15, the instructions further configured to cause:
- embedding the authentication metadata into the first communication.
17. The computer program product of claim 15, wherein identifying the authentication metadata comprises:
- decoding the authentication metadata in the obtained first communication.
18. The computer program product of claim 15, wherein the authentication metadata comprises location information associated with the first user.
19. The computer program product of claim 15, wherein the authentication metadata embedded within the first communication indicates an identity of the first user.
20. The computer program product of claim 15, the instructions further configured to cause:
- preventing display of the second communication based at least in part on the determining that the first content is different than the second content.
| 5577188 | November 19, 1996 | Zhu |
| 5608872 | March 4, 1997 | Schwartz et al. |
| 5649104 | July 15, 1997 | Carleton et al. |
| 5715450 | February 3, 1998 | Ambrose et al. |
| 5761419 | June 2, 1998 | Schwartz et al. |
| 5819038 | October 6, 1998 | Carleton et al. |
| 5821937 | October 13, 1998 | Tonelli et al. |
| 5831610 | November 3, 1998 | Tonelli et al. |
| 5873096 | February 16, 1999 | Lim et al. |
| 5892900 | April 6, 1999 | Ginter et al. |
| 5918159 | June 29, 1999 | Fomukong et al. |
| 5963953 | October 5, 1999 | Cram et al. |
| 5983227 | November 9, 1999 | Nazem et al. |
| 6092083 | July 18, 2000 | Brodersen et al. |
| 6161149 | December 12, 2000 | Achacoso et al. |
| 6169534 | January 2, 2001 | Raffel et al. |
| 6178425 | January 23, 2001 | Brodersen et al. |
| 6189011 | February 13, 2001 | Lim et al. |
| 6212504 | April 3, 2001 | Hayosh |
| 6216133 | April 10, 2001 | Masthoff |
| 6216135 | April 10, 2001 | Brodersen et al. |
| 6233617 | May 15, 2001 | Rothwein et al. |
| 6236978 | May 22, 2001 | Tuzhilin |
| 6266669 | July 24, 2001 | Brodersen et al. |
| 6288717 | September 11, 2001 | Dunkle |
| 6295530 | September 25, 2001 | Ritchie et al. |
| 6324568 | November 27, 2001 | Diec |
| 6324693 | November 27, 2001 | Brodersen et al. |
| 6336137 | January 1, 2002 | Lee et al. |
| D454139 | March 5, 2002 | Feldcamp |
| 6367077 | April 2, 2002 | Brodersen et al. |
| 6393605 | May 21, 2002 | Loomans |
| 6405220 | June 11, 2002 | Brodersen et al. |
| 6411949 | June 25, 2002 | Schaffer |
| 6434550 | August 13, 2002 | Warner et al. |
| 6446089 | September 3, 2002 | Brodersen et al. |
| 6535909 | March 18, 2003 | Rust |
| 6549908 | April 15, 2003 | Loomans |
| 6553563 | April 22, 2003 | Ambrose et al. |
| 6560461 | May 6, 2003 | Fomukong et al. |
| 6574635 | June 3, 2003 | Stauber et al. |
| 6577726 | June 10, 2003 | Huang et al. |
| 6601087 | July 29, 2003 | Zhu et al. |
| 6604117 | August 5, 2003 | Lim et al. |
| 6604128 | August 5, 2003 | Diec |
| 6609150 | August 19, 2003 | Lee et al. |
| 6621834 | September 16, 2003 | Scherpbier et al. |
| 6654032 | November 25, 2003 | Zhu et al. |
| 6665648 | December 16, 2003 | Brodersen et al. |
| 6665655 | December 16, 2003 | Warner et al. |
| 6684438 | February 3, 2004 | Brodersen et al. |
| 6711565 | March 23, 2004 | Subramaniam et al. |
| 6724399 | April 20, 2004 | Katchour et al. |
| 6728702 | April 27, 2004 | Subramaniam et al. |
| 6728960 | April 27, 2004 | Loomans |
| 6732095 | May 4, 2004 | Warshavsky et al. |
| 6732100 | May 4, 2004 | Brodersen et al. |
| 6732111 | May 4, 2004 | Brodersen et al. |
| 6754681 | June 22, 2004 | Brodersen et al. |
| 6763351 | July 13, 2004 | Subramaniam et al. |
| 6763501 | July 13, 2004 | Zhu et al. |
| 6768904 | July 27, 2004 | Kim |
| 6772229 | August 3, 2004 | Achacoso et al. |
| 6782383 | August 24, 2004 | Subramaniam et al. |
| 6804330 | October 12, 2004 | Jones et al. |
| 6826565 | November 30, 2004 | Ritchie et al. |
| 6826582 | November 30, 2004 | Chatterjee et al. |
| 6826745 | November 30, 2004 | Coker et al. |
| 6829655 | December 7, 2004 | Huang et al. |
| 6842748 | January 11, 2005 | Warner et al. |
| 6850895 | February 1, 2005 | Brodersen et al. |
| 6850949 | February 1, 2005 | Warner et al. |
| 6907566 | June 14, 2005 | McElfresh et al. |
| 7062502 | June 13, 2006 | Kesler |
| 7069231 | June 27, 2006 | Cinarkaya et al. |
| 7069497 | June 27, 2006 | Desai |
| 7100111 | August 29, 2006 | McElfresh et al. |
| 7181758 | February 20, 2007 | Chan |
| 7269590 | September 11, 2007 | Hull et al. |
| 7289976 | October 30, 2007 | Kihneman et al. |
| 7340411 | March 4, 2008 | Cook |
| 7356482 | April 8, 2008 | Frankland et al. |
| 7373599 | May 13, 2008 | McElfresh et al. |
| 7401094 | July 15, 2008 | Kesler |
| 7406501 | July 29, 2008 | Szeto et al. |
| 7412455 | August 12, 2008 | Dillon |
| 7454509 | November 18, 2008 | Boulter et al. |
| 7508789 | March 24, 2009 | Chan |
| 7599935 | October 6, 2009 | La et al. |
| 7603331 | October 13, 2009 | Tuzhilin et al. |
| 7603483 | October 13, 2009 | Psounis et al. |
| 7620655 | November 17, 2009 | Larsson et al. |
| 7644122 | January 5, 2010 | Weyer et al. |
| 7668861 | February 23, 2010 | Steven |
| 7698160 | April 13, 2010 | Beaven et al. |
| 7730478 | June 1, 2010 | Weissman |
| 7747648 | June 29, 2010 | Kraft et al. |
| 7779039 | August 17, 2010 | Weissman et al. |
| 7779475 | August 17, 2010 | Jakobson et al. |
| 7827208 | November 2, 2010 | Bosworth et al. |
| 7853881 | December 14, 2010 | Aly et al. |
| 7945653 | May 17, 2011 | Zuckerberg et al. |
| 8005896 | August 23, 2011 | Cheah |
| 8014943 | September 6, 2011 | Jakobson |
| 8015495 | September 6, 2011 | Achacoso et al. |
| 8032297 | October 4, 2011 | Jakobson |
| 8073850 | December 6, 2011 | Hubbard et al. |
| 8082301 | December 20, 2011 | Ahlgren et al. |
| 8095413 | January 10, 2012 | Beaven |
| 8095531 | January 10, 2012 | Weissman et al. |
| 8095594 | January 10, 2012 | Beaven et al. |
| 8103611 | January 24, 2012 | Tuzhilin et al. |
| 8150913 | April 3, 2012 | Cheah |
| 8209308 | June 26, 2012 | Rueben et al. |
| 8209333 | June 26, 2012 | Hubbard et al. |
| 8275836 | September 25, 2012 | Beaven et al. |
| 8457545 | June 4, 2013 | Chan |
| 8472727 | June 25, 2013 | Gronau |
| 8484111 | July 9, 2013 | Frankland et al. |
| 8490025 | July 16, 2013 | Jakobson et al. |
| 8504945 | August 6, 2013 | Jakobson et al. |
| 8510045 | August 13, 2013 | Rueben et al. |
| 8510664 | August 13, 2013 | Rueben et al. |
| 8566301 | October 22, 2013 | Rueben et al. |
| 8601504 | December 3, 2013 | Stone et al. |
| 8646103 | February 4, 2014 | Jakobson et al. |
| 9652460 | May 16, 2017 | Barisic |
| 11714923 | August 1, 2023 | Taschek |
| 20010044791 | November 22, 2001 | Richter et al. |
| 20020060736 | May 23, 2002 | Wakao |
| 20020072951 | June 13, 2002 | Lee et al. |
| 20020082892 | June 27, 2002 | Raffel et al. |
| 20020129352 | September 12, 2002 | Brodersen et al. |
| 20020140731 | October 3, 2002 | Subramaniam et al. |
| 20020143997 | October 3, 2002 | Huang et al. |
| 20020162090 | October 31, 2002 | Parnell et al. |
| 20020165742 | November 7, 2002 | Robins |
| 20030004971 | January 2, 2003 | Gong et al. |
| 20030018705 | January 23, 2003 | Chen et al. |
| 20030018830 | January 23, 2003 | Chen et al. |
| 20030066031 | April 3, 2003 | Laane |
| 20030066032 | April 3, 2003 | Ramachandran et al. |
| 20030069936 | April 10, 2003 | Warner et al. |
| 20030070000 | April 10, 2003 | Coker et al. |
| 20030070004 | April 10, 2003 | Mukundan et al. |
| 20030070005 | April 10, 2003 | Mukundan et al. |
| 20030074418 | April 17, 2003 | Coker |
| 20030120675 | June 26, 2003 | Stauber et al. |
| 20030151633 | August 14, 2003 | George et al. |
| 20030159136 | August 21, 2003 | Huang et al. |
| 20030187921 | October 2, 2003 | Diec |
| 20030189600 | October 9, 2003 | Gune et al. |
| 20030204427 | October 30, 2003 | Gune et al. |
| 20030206192 | November 6, 2003 | Chen et al. |
| 20030225730 | December 4, 2003 | Warner et al. |
| 20040001092 | January 1, 2004 | Rothwein et al. |
| 20040010489 | January 15, 2004 | Rio |
| 20040015981 | January 22, 2004 | Coker et al. |
| 20040027388 | February 12, 2004 | Berg et al. |
| 20040128001 | July 1, 2004 | Levin et al. |
| 20040186860 | September 23, 2004 | Lee et al. |
| 20040193510 | September 30, 2004 | Catahan, Jr. et al. |
| 20040199489 | October 7, 2004 | Barnes-Leon et al. |
| 20040199536 | October 7, 2004 | Barnes Leon et al. |
| 20040199543 | October 7, 2004 | Braud et al. |
| 20040249854 | December 9, 2004 | Barnes-Leon et al. |
| 20040260534 | December 23, 2004 | Pak et al. |
| 20040260659 | December 23, 2004 | Chan et al. |
| 20040268299 | December 30, 2004 | Lei et al. |
| 20050050555 | March 3, 2005 | Exley et al. |
| 20050091098 | April 28, 2005 | Brodersen et al. |
| 20050114670 | May 26, 2005 | Bowe |
| 20080028220 | January 31, 2008 | Wyssen |
| 20080228733 | September 18, 2008 | Davis et al. |
| 20080249972 | October 9, 2008 | Dillon |
| 20080288509 | November 20, 2008 | Mysen |
| 20090063415 | March 5, 2009 | Chatfield et al. |
| 20090100342 | April 16, 2009 | Jakobson |
| 20090177744 | July 9, 2009 | Marlow et al. |
| 20110218958 | September 8, 2011 | Warshavsky et al. |
| 20110247051 | October 6, 2011 | Bulumulla et al. |
| 20120042218 | February 16, 2012 | Cinarkaya et al. |
| 20120150740 | June 14, 2012 | Isaacson et al. |
| 20120233137 | September 13, 2012 | Jakobson et al. |
| 20120290407 | November 15, 2012 | Hubbard et al. |
| 20130166538 | June 27, 2013 | Hadley et al. |
| 20130197984 | August 1, 2013 | Bhatt et al. |
| 20130212497 | August 15, 2013 | Zelenko et al. |
| 20130218948 | August 22, 2013 | Jakobson |
| 20130218949 | August 22, 2013 | Jakobson |
| 20130218966 | August 22, 2013 | Jakobson |
| 20130247216 | September 19, 2013 | Cinarkaya et al. |
| 20130262420 | October 3, 2013 | Edelstein |
| 20130318635 | November 28, 2013 | Verner |
| 20140019761 | January 16, 2014 | Shapiro |
| 20140359537 | December 4, 2014 | Jackobson et al. |
| 20150006289 | January 1, 2015 | Jakobson et al. |
| 20150007050 | January 1, 2015 | Jakobson et al. |
| 20150089661 | March 26, 2015 | Taschek |
| 20150095162 | April 2, 2015 | Jakobson et al. |
| 20150142596 | May 21, 2015 | Jakobson et al. |
| 20150172563 | June 18, 2015 | Jakobson et al. |
| 20160182237 | June 23, 2016 | Almgren |
| 20160379330 | December 29, 2016 | Powers |
| 20170247017 | August 31, 2017 | Lee |
| 20180276270 | September 27, 2018 | Bisbee |
| 20190089702 | March 21, 2019 | Bhatt |
| 20190114692 | April 18, 2019 | Briggs |
| 20210203555 | July 1, 2021 | Kulkarni |
| 20210334931 | October 28, 2021 | Kwon |
| 20210377052 | December 2, 2021 | Brown |
| 20220318432 | October 6, 2022 | Taschek |
- “Google Plus Users”, Google+Ripples, Oct. 31, 2011 [retrieved on Feb. 21, 2012 from Internet at http://www.googleplusers.com/google-ripples.html], 3 pages.
- ParallelDots, “Emotion Detection Using Machine Learning,” Medium, May 3, 2017, 6 pages.
- U.S Advisory Action dated Aug. 6, 2020 in U.S. Appl. No. 14/498,666.
- U.S. Final Office Action dated Aug. 31, 2018 issued in U.S. Appl. No. 14/498,666.
- U.S. Final Office Action dated May 13, 2020 issued in U.S. Appl. No. 14/498,666.
- U.S. Final office Action dated Nov. 17, 2022 in U.S. Appl. No. 17/301,545.
- U.S. Non-Final office Action dated Jul. 22, 2022 in U.S. Appl. No. 17/301,545.
- U.S. Notice of Allowance dated Mar. 13, 2023 in U.S. Appl. No. 17/301,545.
- U.S. Office Action dated Oct. 13, 2020 issued in U.S. Appl. No. 14/498,666.
- U.S. Office Action dated Oct. 31, 2017 issued in U.S. Appl. No. 14/498,666.
- U.S. Office Action dated Oct. 31, 2019 issued in U.S. Appl. No. 14/498,666.
Type: Grant
Filed: Jun 12, 2023
Date of Patent: Jun 4, 2024
Patent Publication Number: 20230325533
Assignee: Salesforce, Inc. (San Francisco, CA)
Inventor: John Walter Taschek (San Francisco, CA)
Primary Examiner: Khalid M Almaghayreh
Application Number: 18/333,003
