Discussion-topic, social network systems

• US 8,793,324 B1
• Filed: 01/13/2014
• Issued: 07/29/2014
• Est. Priority Date: 09/09/2013
• Status: Active Grant

• Current Assignee: LavaRipples LLC
• Original Assignee: LavaRipples LLC
• Inventors: Schabes, Yves, Roche, Emmanuel
• Primary Examiner(s): DENNISON, JERRY B
• Application Number:
  US14/153,587
• Time in Patent Office: 197 Days
• Field of Search: 709/206
• US Class Current: 709/206
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15

Abstract

Apparatus and methods for social media networking using devices configured to communicate in a data communications network where exchanged information is organized according to discussion topics. Users may exchange content with selected members of discussion-topic groups. Initiating comments and replies may be posted to a discussion topic for review by participants. Sub-discussion topics may be defined for discussion topics. A user may further flexibly define active tag and associated arguments for the active tags as a relational or linking structure for a discussion topic. Conventional email messages may be converted and ported into the discussion-topic system.

Claims

1. A discussion-topic server configured to manage communications and content sharing between a first device and at least one second device, wherein the discussion-topic server is configured to communicate over a data communications network with the first device and the at least one second device, the discussion-topic server comprising:

at least one network interface connected to the data communications network and configured to receive and transmit data; and

at least one processor adapted with machine-readable instructions that configure the discussion-topic server to;

receive, from the first device, a conventional email chain message;

receive, from the first device, naming data for identifying the conventional email chain message, wherein the naming data was entered by a user to name a discussion topic for the email chain message;

create a discussion-topic data structure associated with the named discussion topic;

parse email messages within the email chain as separate comment data;

store the separate comment data in association with the discussion-topic data structure;

identify at least one addressee in the email chain, in addition to the first device, as a respective participant in the named discussion topic that is permitted access to the discussion-topic data structure; and

responsive to receiving a request from the respective participant for content associated with the discussion topic, transmit first visual feed data comprising the separate comment data to the respective participant for displaying on a display a discussion-topic page identified by the named discussion topic and comprising a listing of at least a portion of the separate comment data associated with the named discussion topic.

2. The discussion-topic server of claim 1, wherein the conventional email chain message is a first transmission received by the discussion-topic server for the named discussion topic.

3. The discussion-topic server of claim 1, wherein the at least one processor is further adapted to:

provide an email inbox for the first device that is configured to receive conventional email transmissions for the first device; and

receive the conventional email chain message in the email inbox.

4. The discussion-topic server of claim 1, wherein the at least one processor is further adapted to:

determine originator identities for the separate comment data; and

transmit with the visual feed data originator identities for displaying in the listing an originator identity in association with a corresponding separate comment data.

5. The discussion-topic server of claim 1, wherein the at least one processor is further adapted to:

transmit dialog data to the first device responsive to receiving the conventional email chain message;

receive, from the first device, the naming data following the transmission of the dialog data; and

receive, from the first device, hierarchical data identifying the named discussion topic as a sub-topic or parent topic of another named discussion topic.

6. The discussion-topic server of claim 5, wherein the at least one processor is further adapted to enter in a relational data structure at least one entry identifying the named discussion topic as being related hierarchically as a sub-topic or parent topic to the other named discussion topic.

7. The discussion-topic server of claim 5, wherein the at least one processor is further adapted to:

receive, from the first device, identifiers for at least one participant other than the at least one addressee that is or are to be invited to participate in the named discussion topic; and

transmit at least one invitation to the at least one participant to join the discussion topic.

8. The discussion-topic server of claim 1, wherein the at least one processor is further adapted to:

receive first comment data from a participant in the named discussion topic, wherein the first comment data is identified as associated with the named discussion topic;

add the first comment data to the discussion-topic data structure; and

transmit a conventional email message bearing an identifier for the discussion topic and including the first comment data to a conventional email account of a second participant in the named discussion topic.

9. The discussion-topic server of claim 8, wherein the at least one processor is further adapted to:

receive a conventional email reply from the second participant;

convert the conventional email reply to second comment data;

store the second comment data in association with the named discussion topic; and

forward the first and second comment data to the first device for adding to the listing.

10. The discussion-topic server of claim 1, wherein the at least one processor is further adapted to receive active tag data for the named discussion topic, wherein the active tag data is entered by a participant and comprises identifying data for identifying an active tag associated with the named discussion topic and argument data identifying an argument associated with the active tag.

11. The discussion-topic server of claim 10, wherein the argument comprises an identifier for a participant permitted access to the first discussion data structure.

12. The discussion-topic server of claim 10, wherein the argument comprises a date.

13. The discussion-topic server of claim 10, wherein the argument comprises an identifier for a second discussion topic.

14. The discussion-topic server of claim 10, wherein the argument comprises an alphanumeric string created by the user of the first device.

15. The discussion-topic server of claim 10, wherein the argument comprises a URL link.

16. A method for managing communications and content sharing between a first device and at least one second device, wherein the first device and the at least one second device are configured to communicate over a data communications network, the method comprising:

receiving a conventional email chain message;

receiving, at the first device, naming data entered by a user for identifying the conventional email chain message;

naming a discussion topic for the email chain message based on the naming data, wherein the conventional email chain message is a first transmission received for the named discussion topic;

creating a discussion-topic data structure associated with the named discussion topic;

displaying, on a display of the first device, a discussion-topic page identified by the named discussion topic; and

displaying, on the discussion-topic page, a listing of comment data parsed from the conventional email chain message.

17. The method of claim 16, further comprising:

parsing email messages within the conventional email chain as separate comment data to be included in the listing;

storing the separate comment data in association with the discussion-topic data structure; and

identifying at least one addressee in the email chain, in addition to the first device, as a participant in the named discussion topic that is permitted access to the discussion-topic data structure.

18. The method of claim 17, further comprising:

receiving identifiers entered by a user of the first device for at least one participant other than the at least one addressee that is or are to be invited to participate in the named discussion topic; and

transmitting at least one invitation to the at least one participant to join the named discussion topic.

19. The method of claim 16, further comprising displaying on a display of the first device a discussion-topic page comprising a full-screen listing of at least a portion of the separate comment data in association with the named discussion topic.

20. The method of claim 19, further comprising:

receiving hierarchical data identifying the named discussion topic as a sub-topic or parent topic of another named discussion topic; and

visually indicating on the display a hierarchical relationship between the named discussion topic and the other named discussion topic.

21. The method of claim 19, further comprising:

determining originator identities for the separate comment data; and

displaying an originator identity in association with a corresponding separate comment data.

22. The method of claim 16, further comprising receiving active tag data for the named discussion topic, wherein the active tag data is entered by a participant and comprises identifying data for identifying an active tag associated with the named discussion topic and argument data identifying an argument associated with the active tag.

23. The method of claim 22, further comprising:

displaying, on the display of the first device, active button or active text identified as the active tag;

receiving an indication that the active button or active text has been selected; and

performing, responsive to receiving the indication, a functional operation associated with the active tag.

24. The method of claim 23, wherein the argument associated with the active tag comprises a date and the functional operation comprises displaying a calendar for selecting a date.

25. The method of claim 23, wherein the argument associated with the active tag comprises a name of another discussion topic and the functional operation comprises changing the display to a discussion page for the other discussion topic.