BRPI0616971B1 - "METHOD FOR SUBSCRIBING CONTENT, CUSTOMER SYSTEM FOR SUBSCRIBING CONTENT, AND CUSTOMER SYSTEM FOR SUBSCRIBING CONTENT" - Google Patents

Abstract

client method and system for subscribing to content. A user can subscribe to a content feed group that includes a set of content feeds. The content feed group includes a first set of content items from the included content feed set. Content items are displayed in response to a subscription to the content feed group. After a switch to a content feed group, such as adding or removing a content feed from the set, a second set of content items, reflecting the changed set of content feeds, is presented. In addition, a label can be applied to one or more content items by a user or according to predefined criteria, rules, or filters. labeled content items are associated with a secondary feed associated with the label. other users can subscribe to the secondary feed and be presented with labeled content items. The label can be system-defined or user-defined.

Description

(54) Title: METHOD TO SUBSCRIBE TO CONTENT, CLIENT SYSTEM TO SUBSCRIBE TO CONTENT, AND CLIENT SYSTEM TO SUBSCRIBE TO CONTENT (51) Int.CI .: G06F 17/30 (30) Unionist Priority: 10/07/2005 US 11 / 246,656, 10/7/2005 US 11 / 246,597 (73) Holder (s): GOOGLE LLC (72) Inventor (s): CARL L. GONSALVES; BENJAMIN G. DARNELL; JASON H. SHELLEN; CHRISTOPHER J. WETHERELL

1/29

METHOD TO SUBSCRIBE TO CONTENT, CLIENT SYSTEM TO SUBSCRIBE TO CONTENT, AND CLIENT SYSTEM TO SUBSCRIBE TO CONTENT.

TECHNICAL FIELD [001] The embodiments exposed are generally related to the publication of content, and more particularly, to providing indirect subscriptions to feed content.

BACKGROUND [002] Content publishing is growing in popularity as a way to distribute frequently updated information, such as news and blog posts, on the Internet. Using content publishing formats such as Really Simple Publishing (RSS), content providers can include content and / or links to it in a content feed. Users can subscribe to these content feeds using an application known as a reader or aggregator. When the content feed is updated with new content items, the new content items are reflected in the user's reader.

[003] A passive user may wish to avoid administering their content feed subscriptions. One way is to adopt another user's content feed subscriptions as your own, thereby delegating the responsibility of selecting content feeds for subscription to that other user. A second user can export their list of content feed subscriptions to a file. The first user can import the file into their aggregator application and subscribe to the content feeds included in the file. However, this still requires some subscription administration on the part of the first user, since he is still responsible for having unsubscribed from content feeds to which he no longer wishes to subscribe.

Petition 870180028300, of 04/09/2018, p. 3/45

2/29 [004] Therefore, there is a need for a more efficient way to subscribe to feed content.

SUMMARY OF ACCOMPLISHMENTS [005] According to some embodiments, a method of subscribing to content includes subscribing a user to a content feed group that includes a set of content feeds; present the user with a first plurality of content items according to the content feed group; and after a change to the content feed group, present the user with a second plurality of content items according to the changed content feed group.

[006] According to some embodiments, the operations mentioned above can be performed by a system having memory, one or more processors, and one or more modules stored in memory and configured for execution by the processors.

[007] According to some embodiments, instructions for the aforementioned operations can be included in a computer program product for use in conjunction with a computer system.

BRIEF DESCRIPTION OF THE DRAWINGS [008] Figure 1 is a block diagram illustrating a content feed aggregation system according to some embodiments.

[009] Figure 2 is a flowchart illustrating a process for presenting content selected by another user to a user, according to some embodiments.

[0010] Figures 3A - 3B are flowcharts illustrating a process for presenting to a user content feeds selected by another user, according to some embodiments.

Petition 870180028300, of 04/09/2018, p. 4/45

3/29 [0011] Figure 4 is a flow chart illustrating a process for presenting a user with selected content feeds according to predefined criteria, according to some embodiments.

[0012] Figure 5 is a block diagram illustrating a client computer according to some embodiments.

[0013] Figure 6 is a block diagram illustrating a server computer according to some embodiments.

[0014] Figure 7 is a diagram illustrating a feed reader user interface according to some embodiments.

[0015] Figure 8 is a diagram illustrating a page of labels according to some embodiments.

[0016] Figure 9 is a diagram illustrating an active subscription page according to some embodiments.

[0017] Figure 10 is a diagram illustrating a page of available subscriptions according to some embodiments.

[0018] Figure 11 is a diagram illustrating a data structure for food content items, according to some embodiments.

[0019] Same reference numerals refer to corresponding parts throughout the drawings.

DESCRIPTION OF CONCRETIZATIONS [0020] A content feed aggregation system can provide indirect subscriptions. Instead of subscribing directly to content feeds (or primary feeds), a user can subscribe to a group of content items or a group of content feeds selected by another user or according to predefined criteria. The selected items or feeds are repackaged into a secondary content feed, to which the user can subscribe. The content items included in the

Petition 870180028300, of 04/09/2018, p. 5/45

4/29 secondary feed may change when the selection of content items or content feeds changes, and the content items presented by the user as part of the subscription to the secondary feed change along with the changed selection.

[0021] Figure 1 is a block diagram illustrating a content feed aggregation system according to some embodiments. The content feed aggregation system 100 includes a server system 104. Server system 104 is coupled to one or more client systems 102 and one or more hosts 120 (or power supplies) over a network 106. A network 106 can be any suitable wired and / or wireless network and can include a local area network (LAN), wide area network (WAN), the Internet, etc.

[0022] Server system 104 accesses content feeds from power supplies 120. Server system 104 includes server 108 and database 110. Server 108 serves as a front end for server system 104. Server 108 retrieves content feeds from power supplies 120, and also provides an interface between server system 104 and client systems 102. In some embodiments, server roles 108 can be split or allocated between two or more servers.

[0023] Server system 104 stores content items in content feeds in database 110. In some embodiments, database 110 stores both metadata (for example, title, description, URL, date / time, and possibly other metadata) and the content of each content item. However, in some other embodiments, database 110 stores metadata, but not the content for each content item. Database 110 also stores user feed information 112

Petition 870180028300, of 04/09/2018, p. 6/45

5/29 for a plurality of users. User feed information for a particular user identifies content feed subscriptions, as well as sources, filters, and states read for that particular user. That is, user feed information associated with a user identifies the content feeds the user has subscribed to, any filters the user has defined for feeds, any labels the user has associated with individual feed items, and an indication of whether each food item has been marked as read by the user.

[0024] It should be appreciated that server system 104, including server 108 and database 110, can be implemented as a distributed system of multiple computers. However, for convenience of explanation, server system 104 is described below as being implemented on a single computer, which can be considered a single logical system.

[0025] A content feed (or channel) is a feature or service that provides a list of content items that are present, recently added, or recently updated to a 120 power supply. A content item in a content feed may include content associated with the item itself (the current content that the content item specifies), a title and / or a description of the content, a locator (for example, URL) of the content, or any combination thereof. For example, if the content item identifies a text item, the content item can include the 'inline' item itself, along with the title and locator. Alternatively, a content item can include the title, description and locator, but not the item content. Thus, some content items may include the content associated with those items, while others contain links to the associated content, but not the full content of the items. A content item can also include additional metadata that

Petition 870180028300, of 04/09/2018, p. 7/45

6/29 provide additional information about the content. The full version of the content can be any machine-readable data, including, but not limited to, web pages, images, digital audio, digital video, Portable Document Format (PDF) documents, etc.

[0026] In some embodiments, a content feed is specified using a content publishing format, such as RSS. RSS is an acronym that means rich site summary, RDF site summary or Really Simple Publication. RSS can refer to any of a family of formats based on Extensible Markup Language (XML) to specify a content feed and content items included in the feed. In some other embodiments, other content publishing formats, such as the Atom publication format or the VCALENDAR calendar format, can be used to specify content feeds.

[0027] Additional information regarding the RSS publication format known as Really Simple Publication is set out in the RSS 2.0 Specification by D. Winer, which is hereby incorporated by reference here in its entirety. M. Nottingham et al., Provide additional information regarding the Atom publication format in The Atom Syndication Format, which is hereby incorporated by reference in its entirety.

[0028] A user connects with the server system 104 and sees content items to a client system or device 102 (afterwards called the client system for ease of reference). The client system 102 includes a computer 118 or computer controlled device, such as a personal digital assistant, cell phone or the like (hereinafter referred to as the client system for ease of reference). Computer 118 typically includes one or more processors (not shown); memory, which may include voPetition memory 870180028300, from 04/09/2018, p. 8/45

7/29 latex (not shown) and non-volatile memory such as a 119 hard drive; and a display 114. Computer 118 may also have input devices such as a keyboard and mouse (not shown).

[0029] In some embodiments, a user can interact with the server system 104 via a feed reader user interface 116, which can be displayed on display 114. The user can create a list of feed subscriptions via the user interface feed reader 116. In some embodiments, using the feed reader user interface 116, the user can also create filters or labels to be applied to content feeds and / or content items, and modify the states read from feeds content and / or content items. The feed reader user interface transmits a list of content feed subscriptions, or modifications to a content feed subscription list, to server system 104 for storage in database 110. The reader user interface feed 116 presents content items stored in database 110 to the user based on the user's list of content feed subscriptions. That is, the feed reader user interface 116 presents the user with content items specified in the content feeds to which the user subscribed. A user can view the full version of the content of a content item in the feed reader user interface 116 by selecting it (for example, clicking on it with a mouse pointer). In some embodiments, a copy of the user's list of content feed subscriptions and copies of the displayed content items can be stored locally in a cache in the client system 102.

[0030] In some embodiments, the reader user interface

Petition 870180028300, of 04/09/2018, p. 9/45

8/29 feed 116 can be a web based user interface. That is, the feed reader user interface 116 includes a plurality of web pages. Web pages can be written in Hypertext Markup Language (HTML), Extensible Markup Language (XML), or any other suitable language for preparing web pages, and can include one or more texts to connect with the server system 104. The user can subscribe to content feeds, view content items, and otherwise interact with the server system 104 by interacting with feed reader user interface web pages 116. In other words, the server system 104, including the feed reader user interface 116, provides a web-based content aggregation service. The server system 104 aggregates and stores content items according to the user's content feed subscriptions. In some embodiments, the server system 104 may also apply filters or labels, or change the states read from content items according to user actions or instructions. When the user accesses the feed reader user interface 116, content items are presented to the user through the feed reader user interface 116.

[0031] In some other embodiments, the feed reader user interface 116 can be part of a standalone application that runs on client system 102. The standalone application can connect to server system 104 via a programming interface application (API).

[0032] Figure 2 is a flow chart illustrating a process 200 for presenting content selected by another user to a user, according to some embodiments. To a first customer (then Customer A for convenience), a first user (then User A for convenience) applies a tag (or label) to a

Petition 870180028300, of 04/09/2018, p. 10/45

9/29 or more content items in the feed reader user interface 116 (Figure 1) (202). Content items do not all have to be from the same content feed; content items can be from any number of content feeds at which User A is subscribed. The label can be a prefixed label, predefined by the system or a label created and defined by User A. In some embodiments, the user can define a filter or rule to automatically label (or label) items in his name. For example, the user can define a rule to apply a Sports tag to all content items with at least one of the keywords baseball, football, basketball, hockey and soccer.

[0033] For the purposes of this description, the words tag and label, whether used as a noun or as a verb, are interchangeable.

[0034] On the server, the tag is applied to one or more content items, which are stored in database 110 (Figure 1), according to the application of the tag to content items by User A (204). In some embodiments, the tag is applied to the server by associating the content items with the tag in database 110. The tagged content items are associated with a content feed that includes the tagged content items (hereinafter the secondary feed ) (206). In other words, the secondary feed is a content feed generated from tagged content items. In some embodiments, the tagged content items are aggregated and listed in a content feed document written according to a content publishing format such as RSS or Atom. The content feed document is the secondary feed. In some embodiments, the secondary supply is associated with the userPetition 870180028300, from 04/09/2018, p. 11/45

10/29 river that applied the label (User A, in this case), as well as being associated with the label.

[0035] Secondary feeding is made available for subscription by other users (208). In some embodiments, the secondary feed is added to a list, which is accessible to other users of available content feed subscriptions. Other users can view the list and select the secondary feed for subscription. In some embodiments, the availability of secondary food is limited to users selected or approved by Client A. In some embodiments, the set of users for whom secondary food is available may be limited, in the election of Client A, to users with whom Client Has a subscription for mutual presence in an instant messaging application or service.

[0036] To a second customer (hereinafter B for convenience), a second user (hereinafter B for convenience) subscribes to the secondary supply (210). The content items in the secondary feed (that is, the content items labeled by User A) are presented to the user (212). In some embodiments, items already seen by User B in the past can be hidden from the user and thus the content items actually presented can be a subset of the items in the secondary feed.

[0037] After subscribing to secondary feed by User B, User A can choose to apply the tag to additional content items or remove the tag from one or more content items to which the tags were applied. The content items in the secondary feed are changed according to the user's labeling changes. That is, the additional items labeled by User A are added to the secondary feed and the content items from which the tag was removed are removed from food 870180028300, from 04/09/2018, p. 12/45

11/29 secondary education. In some embodiments, changes to secondary feeding are also reflected in the presentation of content items for User o B.

[0038] Figures 3A - 3B are flowcharts illustrating a process for presenting a user with content feeds selected by another user, according to some embodiments. Attention is now directed to process 300 in Figure 3A, which is similar to process 200 in Figure 2. On Client A, User A applies a tag (or label) to one or more content feeds to which User A is subscribed on the user interface. user of feed reader 116 (Figure 1) (302). The tag can be a preset tag, predefined by the system or a tag created and defined by User A. Applying the tag to content feeds creates, at least conceptually, a content feed group that includes a set of one or more feeds of content. content. The content feed group is called a secondary feed here. [0039] On the server, the tag is applied to content items in the set of content feeds tagged by the user, according to the application of the tag to content feeds by User A (304). In some embodiments, the tag is applied to the server by associating the content items with the tag in database 110. The tagged content items are associated with a secondary feed (306), similar to operation 206 (Figure 2). In some embodiments, the tagged content items are aggregated and listed in a content feed document written according to a content publishing format such as RSS or Atom. The content feed document is the secondary feed. The secondary feed represents the content feed group; the secondary feed includes the content items included in the content feeds that belong

Petition 870180028300, of 04/09/2018, p. 13/45

12/29 to the content feed group. In some embodiments, the secondary supply is associated with the user who applied the label (User A, in this case), as well as being associated with the label.

[0040] Secondary feeding is made available for subscription by other users (308). In some embodiments, the secondary feed is added to a list, which is accessible to other users of available content feed subscriptions. Other users can view the list and select the secondary feed for subscription. In some embodiments, as in process 200 (Figure 2), the availability of secondary food is limited to users selected or approved by Client A. In some embodiments, the set of users for whom secondary food is available may be limited, in the election from Customer A, for users with whom Customer A has a mutual presence subscription to an instant messaging application or service.

[0041] In Client B, User B subscribes to the secondary supply (310). User B, subscribing to the secondary feed, subscribes to the content feed group represented by the secondary feed. The content items in the secondary feed (that is, the content items in the content feeds labeled by User A and belonging to the content feed group) are presented to the user (312). In some embodiments, items already seen by User B in the past can be omitted and thus the content items actually displayed can be a subset of the items in the tagged content feed.

[0042] Attention is now directed to Figure 3B, which illustrates a process 320 of presenting a changed selection of content feeds to a user. After process 300, User A can apply the same label to additional content feeds and / or

Petition 870180028300, of 04/09/2018, p. 14/45

13/29 remove the tag from one or more content feeds to which the tag has been applied. The content items presented to User B may change according to the labeling changes made by User A.

[0043] User A changes the labeling on content feeds (322). User A applies the same tag to additional content feeds and / or removes the tag from one or more content feeds to which the tag has been applied. This changes the content feed group by adding and removing content feeds from the set of content feeds included in the content feed group.

[0044] On the server, the labeling of content items is changed according to the labeling changes made by User A (324). The content items that are tagged are associated with the secondary feed (326), as in operation 306 (Figure 3A). The tag is applied to content items in the additional content feeds that were recently tagged by User A. In some embodiments, the tag is only applied to content items in the additional content feeds, dated after the tag was applied to feeds of additional content. In other words, only content items from the additional content feeds dated after the secondary feed update are added to the secondary feed. In some other embodiments, the tag is applied to all content items in the additional content feeds. That is, all content items in the recently tagged content feeds are added to the secondary feed.

[0045] For content feeds from which the tag was removed, in some embodiments, content items dated after removing the tag from content feeds are not

Petition 870180028300, of 04/09/2018, p. 15/45

14/29 tagged. In other words, the tag is not applied to content items in a content feed from which the tag was removed, from the time the tag was removed from the content feed. Thus, while content items dated after the content feed has been removed from the content feed group are not included in the secondary feed, items dated before removal can remain in the secondary feed. In some other embodiments, the tag is removed from all content items in the content feed from which the tag was removed. As a result, all content items in the removed content feed are removed from the secondary feed. [0046] Content items in the secondary feed are presented to User B (328), assuming that the subscription to the tagged content feed is still active since process 300. The content items shown include content items added to the secondary feed as a result of adding a content feed to the content feed group and can delete content items removed from the secondary feed as a result of removing a content feed from the content feed group. As described above, content items read by the user can be omitted from the presentation.

[0047] While processes 200, 300, and 320 are described as involving two users on different clients, it should be appreciated that the processes described above can involve two or more users using a multi-user computer, such as a computer that has user accounts and profiles for each computer user, but using the content aggregation service at different times.

[0048] Figure 4 is a flow chart illustrating a process for presenting a user with content feeds selected from

Petition 870180028300, of 04/09/2018, p. 16/45

15/29 according to predefined criteria, according to some embodiments. In some embodiments, rules, filters, or criteria for tagging content feeds can be predefined. These rules, filters, or criteria can be used to automatically generate secondary feeds to which users can subscribe. For example, a rule can be one to tag the five most subscribed content feeds. This rule would generate a secondary feed that includes content items from the top five content feeds in terms of global subscriptions. When subscription numbers change, the content feeds in the top five content feeds can change. The list of content items in the labeled content feed changes to reflect changes in the list of five top content feeds.

[0049] A labeling criterion, rule, or filter is identified (402). A tag is applied to content items in content feeds meeting the tagging criteria / rule / filter (404). For example, using the previous example of the rule to label the top five subscribed feeds, content items in the five most subscribed content feeds are tagged. The tagging criteria / rule / filter defines a content feed group that includes content feeds that meet the criteria / rule / filter. The tagged content items are associated with a secondary feed that represents the content feed group defined by the criteria / rule / filter (406), similar to operations 206 (Figure 2) and 306 (Figure 2). Secondary food is made available for subscription by users (408), as in operations 208 (Figure 2) and 308 (Figure 3).

[0050] A user in a customer subscribes to the secondary supply (410). It is noted that subscription operation 410 may take place before or after operations 402-408. The items of content in the Petition 870180028300, of 04/09/2018, p. 17/45

16/29 secondary mentions are presented to the user (412). As described above, content items already seen by the user can be omitted from the presentation.

[0051] In the same way that a user can add or remove tags from content feeds, the same can be done by the predefined criteria, rule, or tagging filter. Again taking the example of the rule that labels the five most subscribed content feeds, the list of the five top subscribed content feeds may change over time. When that list changes, content feeds are automatically added and removed from the content feed group. As a result, content items can be added and removed from the secondary feed, similar to adding and removing content items from the secondary feed in process 320.

[0052] In addition, tagging criteria or rules or filters for tagging individual content items from any number of content feeds, similar to a user's tagging of content items from any number of content feeds (as described in relation to process 200), can be created. For example, a rule for tagging content items having a particular keyword can be created. Such a rule can be particularly useful for aggregating content items related to a person, place, or event of journalistic interest.

[0053] As described above, a secondary feed and content items included in the secondary feed can be associated with a tag and the user who applied the tag. More precisely, the secondary supply can be associated with a user-tag pair. In some embodiments, the content aggregation service may include privacy options that control whether such secondary feeds may be disclosed to others.

Petition 870180028300, of 04/09/2018, p. 18/45

17/29 users in general (for example, in a list of available subscriptions) and thus available to other users for subscription, or only revealed to the user with whom the secondary supply is associated. In some embodiments, another privacy statement is to limit the visibility of a secondary feed to a set of users selected or approved by the user who created the secondary feed. By setting privacy options, a user can control the sharing of their tagged content items or content feeds with other users. In some embodiments, privacy options are set on a per label basis. In some embodiments, the privacy setting preset for each tag is a maximum privacy setting. As a result, a secondary feed associated with a tag applied by a first user is only made available to other users when the first user has selected less restrictive privacy settings than the preset privacy setting.

[0054] In some embodiments, the predefined criteria or rules or filters for tagging content feeds or content items can be implemented logically, on the server, as an imaginary user tagging content items or content feeds as if they were a real user of service. That is, an imaginary user representing the criteria / rule / filter is created and associated data is stored on the server. In some embodiments, privacy options for the imaginary user are always set to share their secondary food with other users in general. The secondary feed generated as a result of the criteria / rule / tagging filter is associated with the imaginary user. By implementing the tagging criteria / rule / filter as an imaginary user, data in the content aggregation service can share a uniform structure, making storage

Petition 870180028300, of 04/09/2018, p. 19/45

18/29 more efficient data.

[0055] By allowing the tagging of content items and content feeds and generating secondary feeds from them, the content aggregation service enables indirect subscriptions. A user can tag content items or content feeds of interest to him. A user can subscribe to a secondary feed, whether generated by another user or by a predefined rule to tag items or feeds, to delegate responsibility for subscribing to content to another user or entity, and / or to obtain content that may be of interest or attractive for some reason (for example, because it is popular in terms of having many subscribers, because it is a current topic with respect to a person of journalistic interest, etc.).

[0056] Figure 5 is a block diagram illustrating a client computer according to some embodiments. The client computer 500 typically includes one or more processing units (CPU) 502, one or more network or other communication interfaces 506, memory 504, and one or more communication buses 514 to interconnect these components. The client computer 500 may also include a user interface 508 including a display device 510 and a keyboard and / or mouse (or some other pointing device) 512. Memory 504 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other solid state random access memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 504 can optionally include one or more storage devices located remotely from the 502 CPU (s). In some embodiments,

Petition 870180028300, of 04/09/2018, p. 20/45

19/29 memory 504 stores the following programs, modules and data structures, or a subset of it:

[0057] an operating system 516 that includes procedures for operating various basic system services and for performing hardware-dependent tasks;

[0058] a network communication module 518 which is used to connect the client system 500 to other computers through one or more communication network interfaces 506 and one or more communication networks, such as the Internet, other area networks extensive, local area networks, metropolitan area networks, and so on; and [0059] a feed reader module 520 for operating content items from content feeds; and [0060] a 530 client application, such as a web browser.

[0061] The feed reader module 520 includes a content tag module 522 for tagging content items and content feeds in response to user input.

[0062] In some embodiments, the feed reader module 520 may be a text-based module, embedded in a web page served by the server system 104 (Figure 1). The web page can be made by a 530 client application, such as a web browser, on the client computer 500. When the web page is represented, the feed reader module 520 is executed, hereby providing a web-based interface to the server system 104. The text-based feed reader module can be written in JavaScript, ECMAScript or any other satisfactory text creation language.

[0063] In some other embodiments, the feed reader module 520 can be a standalone application stored in the memory 504 of the client computer 500. The standalone application

Petition 870180028300, of 04/09/2018, p. 21/45

20/29 may include, but is not limited to, a power aggregator application. In other additional embodiments, the feed reader module 520 can be an add-on or a plug-in to another application. For example, the feed reader module 520 can be a 'plug-in' to a web browser application or an email application.

[0064] In some embodiments, received content items can be cached locally in memory 504. Similarly, a user's list of content feed subscriptions can also be cached locally in memory 504.

[0065] Each of the elements identified above can be stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to a set of instructions for performing a function described above. The modules or programs identified above (that is, instruction sets) do not need to be implemented as separate software programs, procedures or modules, and thus several subsets of these modules can be combined or otherwise rearranged in various embodiments. In some embodiments, memory 504 can store a subset of the modules and data structures identified above. In addition, memory 504 can store additional modules and data structures not described above.

[0066] Figure 6 is a block diagram illustrating a server computer according to some embodiments. The server computer 600 typically includes one or more processing units (CPUs) 602, one or more network communication or other interfaces 606, memory 604, and one or more communication buses 610 to interconnect these components. The server system 600 can optionally include a user interface 608, which can inPetition 870180028300, from 04/09/2018, pg. 22/45

21/29 include a display device (not shown), and a keyboard and / or mouse (not shown). Memory 604 includes high speed random access memory, such as DRAM, SRAM, DDR RAM or other solid state random access memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 604 can optionally include one or more storage devices located remotely from CPU (s) 602. In some embodiments, memory 604 stores the following programs, modules and data structures, or a subset of it:

[0067] an operating system 612 that includes procedures to operate various basic system services and to perform hardware-dependent tasks;

[0068] a network communication module 614 which is used to connect the server system 600 to other computers via one or more network communication interfaces 606 and one or more communication networks, such as the Internet, other area networks extensive, local area networks, metropolitan area network, and so on; [0069] a feed tracker module 616 for retrieving content items for periodic storage and / or when content feeds are updated;

[0070] a feed content provision module 617, to identify and send content items from users to the feeds to which they have subscribed;

[0071] 618 user data, which includes data for each service user;

[0072] feed content items 620, which include content items from content feeds;

Petition 870180028300, of 04/09/2018, p. 23/45

22/29 [0073] content item tagging module 624 for tagging content items; and [0074] 626 tagging criteria, which include criteria, rules, or filters to automatically tag content items.

[0075] Feed content items 620 include content items 622 that are associated with one or more tags. A content item can be associated with one or more tags. In some embodiments, the feed content items 620 may be stored as a database of content items and tags.

[0076] User data 618 includes data for users of the service, such as registration information and user preferences. User data 618 may include subscription lists (not shown), which include lists of users' feed subscriptions. Each user has a corresponding list of content feed subscriptions.

[0077] The 617 feed content provision module identifies and sends content items to a user according to the user's feed subscriptions. The feed content provisioning module 617 can update user data 618 to identify content items seen by the user, so as to avoid sending those same items to the user again. Optionally, for example according to service characteristics selected by the user, the feed content provisioning module 617 can also update user data 618 to record other information, such as information identifying content items marked by the user or otherwise marked or selected by the user as being of special interest to the user.

[0078] Each of the elements identified above can be stored in one or more of the memory devices previously

Petition 870180028300, of 04/09/2018, p. 24/45

Mentioned 23/29. Each of the modules identified above corresponds to a set of instructions for performing a function described above. The modules or programs identified above (ie, instruction sets) do not need to be implemented as separate software programs, procedures or modules, and thus several subsets of these modules can be combined or otherwise rearranged in various embodiments. In some embodiments, memory 604 can store a subset of the modules and data structures identified above. In addition, memory 604 can store additional modules and data structures not described above.

[0079] Although Figure 6 shows a server computer, Figure 6 is designed more as a functional description of the various characteristics that may be present in a set of servers than as a structural schematic of the embodiments described here. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. For example, some items shown separately in Figure 6 could be implemented on single servers and single items could be implemented on one or more servers.

[0080] Figure 7 illustrates a feed reader user interface according to some embodiments. The user, through the feed reader user interface 116, can view, among other things, content items from their subscribed content feeds. The feed reader user interface 116 (hereinafter the UI) includes one or more buttons, menus, links, and the like 710 to enable and disable various functions and features.

[0081] The user can see the content items in a universal view. The universal view includes a 702 list of content items

Petition 870180028300, of 04/09/2018, p. 25/45

24/29 of all user subscribed feeds that have new content items not yet seen by the user. List 702 can be generated, for example, by the content feed provision module 617 of the server computer 600. In some embodiments, several criteria can be used (by the content feed provision module 617) to limit the items included in list 702, such as date and time of publication, and number of items not yet seen by the user that were published by the same source. For example, items published more than X (for example, 7) days ago, can be deleted. In another example, when there are more than Y (for example, 10) unseen items from the same source, only the most recent Y unseen items from the source can be included in list 702.

[0082] Content items 704 shown in list 702 are merged without considering the source. In some embodiments, the list is ordered by date and time of publication, for example in reverse chronological order. Also, in some embodiments, the list may only show content items that the user has not seen. The list presents identifying information for the content items, so that the user can identify a content item that she wants to see and select it. Because UI 116 can be finite in size and the list can include more items that can fit in the UI, UI 116 can display a subset of the content items at any given time and the user can scroll through the list to find other content items . The list can also include an 706 indicator of how many content items are in the list in total. Alternatively, indicator 706 can indicate the number of content items yet to be viewed.

[0083] From the list, the user can select a content item. When the user selects an item from the list in the universal view, UI 116 can display the full version of the content in a 708 viewer region. For example, if the selected content item (indiPetition 870180028300, 04/09/2018, p. 26/45

25/29 boxed with a thick border) include a link to an article on a news website or a link to a 'blog' placement, the item or 'blog' placement, respectively, can be shown in the 708 viewer region.

[0084] UI 116 can also include a 712 labels button that the user can select to open a labels page, which allows the user to create, view, edit, and remove labels (then labels). UI 116 can include a download menu 714. The user can use the download menu 714 to apply a label to the currently selected content item.

[0085] Figure 8 illustrates a page of labels according to some embodiments. The 800 label page includes a list of 802 labels (or tags). The 802 label list can include one or more prefixed system-defined labels, such as an 802-A star (or favorite label). The list of 802 labels can also include one or more labels created by the user, such as a Tech 802-B label. 804 bindings for label editing functions are provided for user-defined labels. The user can select an 804 link corresponding to a particular user-defined label to edit or delete that label. An 804 link for label editing functions is not provided for system-defined labels because such labels cannot be edited or deleted by the user. Label page 800 also includes links 806 to view content feeds associated with the label (i.e., content feeds in the content feed group represented by the label) and links 808 to view content items associated with the label (this that is, the content items in the secondary feed associated with the label). Also included are: a button 810 that the user can select to create a new label, and a button cancel 812 to cancel the page of labels 800. In some concretisPetition 870180028300, from 09/04/2018, pg. 27/45

26/29, a label can be a row of characters or an icon (or symbol) with a corresponding row of characters.

[0086] Figure 9 is a diagram illustrating an active subscription page according to some embodiments. The active subscriptions page 900 includes a list of 904 of the user's active subscriptions. Active subscriptions 904 include content feeds to which the user has subscribed, which may include content feeds (primary feeds) provided by power supplies 120 (Figure 1), such as content feed 904-A, and secondary feeds, such as secondary power 904-B. In some embodiments, the name of a 904-B secondary feed associated with a label applied by a real user (instead of an imaginary user, as described above) includes a name of the user who created the secondary feed (labeling one or more feeds content and / or content items) and the character row of the label itself. Subscriptions page 900 also includes labels 902, if any, associated with subscribed content feeds 904. Each subscribed content feed 904 can have zero or more labels. In some embodiments, even a subscribed secondary feed may have zero or more labels.

[0087] The subscriptions page may also include 906 links to view content items associated with the corresponding 904 subscribed content feed, 908 download menus to add labels to the 904 subscribed content feeds, and 910 links to unsubscribe from any of subscribed content feeds 904. A 912 cancel button can be selected by the user to cancel the 900 subscription page.

[0088] Figure 10 is a diagram illustrating a page of available subscriptions according to some embodiments. The available subscriptions page 1000 lists content feeds to which

Petition 870180028300, of 04/09/2018, p. 28/45

27/29 the user did not subscribe and can subscribe. The available subscriptions page 1000 includes the list of available content feeds 1002 and links 1004 that the user can select to subscribe to the corresponding content feed. The content feeds available in list 1002 can include any number of content feeds from power supplies 120 (Figure 1) and any number of secondary feeds. A 1006 cancellation button for canceling the available 1000 subscription page can be included. In some embodiments, a search box 1008 and a search button 1010 may be included. The user can enter one or more keywords or other parameters in the search box 1008 and select the search button 1010 to search for content feeds matching the keywords and / or parameters entered.

[0089] Figure 11 is a diagram illustrating a data structure for feeding content items, according to some embodiments. As described above, a server computer 600 (Figure 6) can store a plurality of feed content items 620. Feed content items can be stored in a data structure, such as a table 960 data structure. Feed content items 620 include content items tagged 622 (content items that are each associated with one or more tags) as well as content items not associated with any tag. The 960 feed content table includes a 970 queue for each content item from each power supply. Each row includes one or more fields (971, 972) that identify the content item, such as a content ID 971 and a feed ID 972 (that identifies the power source for the content item). In some embodiments, the content ID may include information that uniquely identifies the power supply, in

Petition 870180028300, of 04/09/2018, p. 29/45

28/29 in which case the feed ID 972 can be omitted. Each row 970 can also include content 973 from the content item. 973 content may include the content item's metadata (for example, title, description, URL, date / time, and possibly other metadata), and may also include the current content of the content item. In addition, each row 970 includes a column 975 or field for each registered user of the system. The user data in this column can include a checkmark 976, which indicates whether the user matching this column has seen the content item associated with queue 970 containing the user data and can optionally include additional user information, such as a or more 978 specified user tags or indicators. A user can tag or label content items, as well as content feeds, and a record of the tag or label that the user associated with each item of labeled content is stored in the 975 user data In some embodiments, the system may allow users to tag or label individual content items with predefined tags or labels (for example, star, red, blue, etc.), and some embodiments furthermore allow users to tag or label content items individual with user-defined labels. In addition, a content item, represented by a 970 queue, can be tagged by any number of users.

[0090] As described above, a user can set privacy options to control exposure (and availability for subscription) of their tagged content items and content feeds to other users in general. In some embodiments, a content aggregation service can be integrated with user calendars or contact lists. As part of the integration, better privacy options can be made available to the user. The user can use the best privacy options to control exposiPetition 870180028300, from 04/09/2018, pg. 30/45

29/29 tion of tagged content items or feeds not only for other users in general, but also for specific contacts or groups of contacts that are on the user's phonebook or contact list. This provides a broader spectrum of exposure, ranging from full exposure, limited exposure to approved contacts, or to no user. In some other embodiments, the content aggregation service can be integrated in addition to a social network service that includes profiles of users' interests and affiliations, among other things. Privacy controls can also be adapted to control the exposure of tagged content items or feeds to other users who may share common interests, affiliations, or the like.

[0091] The preceding description, for the purpose of explanation, has been described with reference to specific embodiments. However, the above illustrative discussions are not intended to be exhaustive or to limit the invention to the precise forms exposed. Many modifications and variations are possible in view due to the previous teachings. The embodiments have been chosen and described in order to better explain the principles of the invention and their practical applications, thereby enabling others skilled in the art to better use the invention and various embodiments with various modifications as are suitable for the particular use contemplated.

Petition 870180028300, of 04/09/2018, p. 31/45

1/5

Claims (15)

1. Method for subscribing to content, which comprises: in a first user (102, 500): subscribe a first user to a content feed group, the content feed group comprising a first set of content feeds and one or more content items labeled by a second user, where the one or more labeled content items are selected from at least one content feed that is not present in the content feed group; characterized by the fact that it also comprises: presenting simultaneously to the first user (102, 500), in a single view on a user interface, a first plurality of content items from the content feed group, including a plurality of respective content items from the first set of content feeds and a respective content item from one or more content items labeled by the second user that have been selected from at least one content feed that is not in the content feed group; and after a change of labeling in the content feed group made by the second user on a second client, simultaneously present to the first user (102, 500) a second plurality of content items from the modified content feed group according to change of lettering. 2. Method according to claim 1, characterized by the fact that the first plurality of content items comprises content items from two or more of the first set of content feeds. 3. Method, according to claim 1, characterized by the fact that the presentation of the second plurality of items of Petition 870180028300, of 04/09/2018, p. 32/45 2/5 content comprises presenting a plurality of respective content items included in a modified set of content feeds from the modified content feed group. 4. Method, according to claim 1, characterized by the fact that the change of labeling in the content feed group made by the second user comprises adding to the content feed group one or more content items other than at least one feed content that is not present in the content feed group. 5. Method according to claim 1, characterized by the fact that the content feed group additionally comprises one or more content items automatically labeled according to a rule, wherein the one or more content items automatically labeled according to according to the rule they are selected from at least one content feed that is not present in the content feed group. 6. Method, according to claim 1, characterized by the fact that: the change in labeling includes adding a new content item to the content feed group; and the second plurality of content items presented to the first user (102, 500) includes the new content item. 7. Method, according to claim 1, characterized by the fact that: the change in labeling involves removing a label from a respective content item from the content feed group; and the second plurality of content items presented to the first user (102, 500) excludes the respective content item excluded by the change in labeling. Petition 870180028300, of 04/09/2018, p. 33/45 3/5 8. Client system (102, 500) to subscribe to content, which comprises: memory (504); one or more processors (502); and one or more modules stored in memory and configured for execution by one or more processors that execute the method that comprises: subscribe a first user (102, 500) to a content feed group, the content feed group comprising a first set of content feeds and one or more content items labeled by a second user, where one or more labeled content items are selected from at least one content feed that is not present in the content feed group; characterized by the fact that it also comprises: presenting simultaneously to the first user (102, 500), in a single view on a user interface, a first plurality of content items from the content feed group, including a plurality of respective content items from the first set of content feeds and a respective content item from one or more content items labeled by the second user that have been selected from at least one content feed that is not in the content feed group; and after a change of labeling in the content feed group made by the second user on a second client, simultaneously present to the first user (102, 500) a second plurality of content items from the modified content feed group according to change of lettering. 9. System, according to claim 8, characterized by the fact that the first plurality of content items comprise Petition 870180028300, of 04/09/2018, p. 34/45 4/5 addresses content items from two or more of the first set of content feeds. 10. System according to claim 8, characterized in that the method still includes presenting a plurality of respective content items included in a modified set of content feeds from the modified content feed group. 11. System according to claim 8, characterized by the fact that the change in the content feed group comprises adding to the content feed group one or more content items other than at least one content feed that is not present in the content feed group. 12. System according to claim 8, characterized by the fact that the content feed group additionally comprises one or more content items automatically labeled according to a rule, in which the one or more content items automatically labeled according to according to the rule they are selected from at least one content feed that is not present in the content feed group. 13. System, according to claim 8, characterized by the fact that: the change in labeling involves removing a label from a respective content item from the content feed group; and the second plurality of content items presented to the first user (102, 500) excludes the respective content item excluded by the change in labeling. 14. Client system for subscribing to content, which comprises: Petition 870180028300, of 04/09/2018, p. 35/45 5/5 means for subscribing a first user (102, 500) to a content feed group, the content feed group comprising a first set of content feeds and one or more content items labeled by a second user, in that the one or more labeled content items are selected from at least one content feed that is not present in the content feed group; characterized by the fact that it also comprises: means to simultaneously present to the first user (102, 500), in a single view on a user interface, a first plurality of content items from the content feed group, including a plurality of items respective content items from the first set of content feeds and a respective content item from one or more content items labeled by the second user that were selected from at least one content feed that is not in the content feed group; and means for, after a change of labeling in the content feed group made by the second user on a second client, to simultaneously present to the first user (102, 500) a second plurality of content items according to the content feed group modified content. 15. System according to claim 14, characterized by the fact that the change in the content feed group comprises the addition to the content feed group of one or more content items other than at least one content feed that does not is present in the content feed group. Petition 870180028300, of 04/09/2018, p. 36/45 1/11 Feed Aggregation System s Client Systems 11/11 Client A Server Client B