Web-Based Interactive 3D Scene Editor for Web Designers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy approaches to enabling 3D content in web applications require specialized graphics programming skills, creating a gap between web design and 3D code design environments, as web designers lack the expertise to specify camera shots and interaction events without programming in 3D graphics.

Innovation Solution

A cloud-based system with a web-based interactive editor allows web designers to use high-order shot and event components to create and embed 3D scenes in web applications without demanding 3D graphics programming, using a web-friendly object serialization format and a 3D runtime engine for rendering and event handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web designers use legacy 3D rendering tools and libraries, then 3D content can be embedded in web applications, but specialized graphics programming skills are required which creates a gap between web design and 3D code design environments

Engineering Contradiction:
Improveease of creating 3D contentVSAvoidprogramming skill requirement
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a visual editor as an intermediary tool between web designers and the complex 3D rendering system. This visual editor provides a user-friendly interface that translates design intentions into 3D scene configurations without requiring designers to write graphics programming code, thus bridging the skill gap while maintaining ease of operation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical system of manual 3D code writing with an automated visual editor system. Instead of designers directly manipulating graphics programming APIs, they use visual tools to define 3D scenes, and the system automatically generates the underlying rendering code, eliminating the need for specialized programming skills

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If web designers specify camera shots and interaction events using high order abstractions, then the gap between web design and 3D code design is bridged, but the system complexity increases to support the visual editor and runtime engine

Engineering Contradiction:
Improvedesign environment compatibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the system into distinct functional layers: a visual editor for high-order abstraction specification, a runtime engine for interpretation, and a rendering system for graphics output. This segmentation allows each component to be optimized independently and simplifies the overall architecture by clearly separating concerns between design-time abstraction and runtime execution

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter space from low-level graphics programming parameters to high-level semantic parameters. Instead of requiring designers to specify camera positions and rendering commands in detail, the system accepts high-order abstractions like 'camera shot' and 'interaction event', automatically translating these into the necessary low-level rendering parameters

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10013157B2Composing web-based interactive 3D scenes using high order visual editor commands
Publication Date: 2018.07.03 BOX INC
  • US10013157B2 patent drawing
  • US10013157B2 patent drawing
  • US10013157B2 patent drawing

AI summary

A cloud-based environment is configured to interface with storage devices that store 3D object models and a 3D rendering code base that is accessible by two or more user devices over a network using browsers or web agents. A web application is delivered to the user device, whereupon the browser or agent receives the 3D object model and the 3D rendering code into a web application that has user controls for defining at least one 3D scene that is rendered using user-defined camera shots and events associated with the 3D object model. User interactions invoke executable event handler components and executable shot components that correspond to one or more camera shots. User controls serve to invoke generation of custom event handler components and executable shot components. A preview of the 3D scene is presented by rendering the shots and events in a web browser or web agent.