Live-Stream Order Compilation with Parent–Child Purchase Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing live video streaming platforms lack an efficient mechanism for compiling and managing purchase requests from viewer accounts during live streams, leading to fragmented and costly shipping processes for bundled purchases.

Innovation Solution

The Order Compilation Engine (O.C. Engine) generates parent and child nodes for purchase requests within a selected time range, linking them to create a parent order for concurrent purchases, with a single shipping fee assessed upon expiration, and manages the shipping process efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If multiple separate purchase requests are processed individually during live streams, then each request can be handled independently, but shipping costs increase and the process becomes fragmented

Engineering Contradiction:
Improveease of purchase compilationVSAvoidshipping costs
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent combines multiple purchase requests from the same viewer account into a single parent order when they are placed within a specified time range during live streams. This merging approach consolidates shipping logistics and reduces overall shipping costs while simplifying the purchase compilation process for both the platform and viewers.

Inventive Principle:
Principle #5Merging (Combining)

2Loss of energy

If purchase requests are compiled into parent orders with time ranges, then shipping costs are reduced through consolidation, but the system complexity increases

Engineering Contradiction:
Improveshipping costsVSAvoidorder management system complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent segments order management into hierarchical levels: individual purchase requests are organized into parent orders based on viewer account and time range. Each parent order contains multiple child requests, creating a structured segmentation that manages complexity through hierarchical organization rather than treating all orders as a single undifferentiated group.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary compilation mechanism that automatically groups purchase requests into parent orders based on predefined criteria (viewer account, time range). This intermediary layer handles the complexity of consolidation logic, shielding the shipping and fulfillment systems from direct complexity while achieving cost savings.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If a single shipping fee is assessed for bundled purchases, then shipping costs are reduced, but tracking and managing bundled items becomes more difficult

Engineering Contradiction:
Improveshipping costsVSAvoidorder tracking information
Core Design Contradiction:
Loss of energyVSLoss of information

Solution Approach 1:

The patent implements a nested order structure where individual purchase requests (child nodes) are contained within parent orders. This nesting preserves detailed tracking information for each individual item while consolidating shipping under a single parent order identifier, allowing both granular and aggregate tracking simultaneously.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12432421B2Live streaming product creation and order compilation
Publication Date: 2025.09.30 COMMENTSOLD LLC
  • US12432421B2 patent drawing
  • US12432421B2 patent drawing
  • US12432421B2 patent drawing

AI summary

Methods, systems and computer products disclosed herein are directed to an O.C. Engine that detects a first request sent from a requesting account during a target account session, the target account associated with multiple sessions. The O.C. Engine generates a first request parent node active for a range of time. The O.C. Engine detects a subsequent second request sent from the requesting account and generates a second request node. The O.C. Engine verifies that the subsequent second request is not an initial request by the requesting account during a range of time that has not yet expired. Upon verification, the O.C. Engine identifies the second request node as a child node by generating a link between the parent node and the child node.