Content Relationship Graph for Interaction Logging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users' interactions with content items in social networks are not effectively managed, leading to difficulties in capturing and logging events, which can result in missed opportunities for the social network community to benefit from user interactions.

Innovation Solution

A computer-implemented method and system that receives notifications of user actions regarding content items, managing relationships between users and content items through a graph structure, where future and past consumption edges are created and visibility properties are managed to hide consumed content from user views, allowing for organized content management and interaction logging across distinct content systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If user interactions with content items are not captured and logged as events, then the system maintains simplicity in operation, but the social network community cannot benefit from occurrence of the event

Engineering Contradiction:
Improveuser interaction eventsVSAvoidcontent management system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system pre-establishes event tracking infrastructure and automatically captures user interactions as they occur, rather than requiring manual logging. This preliminary setup ensures events are captured without adding operational complexity to user interactions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The content management system automatically logs and processes user interactions without requiring manual intervention. The system serves itself by autonomously capturing events, managing content relationships, and updating user interfaces based on detected interactions.

Inventive Principle:
Principle #25Self-service

2Loss of information

If consumed content is manually deleted from user views, then the interface remains clean and organized, but user interaction history is lost

Engineering Contradiction:
Improveuser interaction historyVSAvoidcontent visibility management
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system segments content visibility into different states: visible content, consumed content, and archived interaction history. By dividing the content lifecycle into distinct segments, the system can manage what users see separately from what users have interacted with, maintaining clean interfaces while preserving historical data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer between content deletion and history preservation. This intermediary mechanism allows consumed content to be removed from active views while simultaneously being archived in interaction history, mediating between the need for clean interfaces and the need to preserve user behavior data.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If content items are organized across distinct content systems, then content management becomes more specialized and efficient, but managing relationships between content items becomes more complex

Engineering Contradiction:
Improvecontent management efficiencyVSAvoidrelationship management system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements a universal relationship management framework that can handle content items from multiple distinct content systems through a common interface. This multi-functional approach allows the system to manage diverse content types and relationships without requiring separate management mechanisms for each content system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces an intermediary relationship management layer that sits between distinct content systems. This intermediary translates and harmonizes relationships across different content systems, allowing specialized content management while maintaining unified relationship tracking through standardized connection types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10270733B2Systems and method for managing content
Publication Date: 2019.04.23 META PLATFORMS INC
  • US10270733B2 patent drawing
  • US10270733B2 patent drawing
  • US10270733B2 patent drawing

AI summary

A first notification of a first action by a user with respect to a first content item may be received by a computer system, the first content item having a first relationship to the user. A second notification of a second notification by the user with respect to a second content item may be received by the computer system. The second content item may have a second relationship to the user, and at least a portion of the second content item may correspond to at least a portion of the first content item. A first property of the first relationship may be managed by the computer system based on the second notification.