Hierarchical Content Node Platform for Service Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The repetitive and time-consuming process of implementing content and service delivery to networked computing devices is inefficient, with significant duplication of efforts in software development, despite the availability of toolkits that only partially alleviate these issues.

Innovation Solution

A server-based platform that stores content in a hierarchical format, allowing for semantic representation and abstraction from specific data formats and transport media, enabling efficient delivery of services like digital ticketing with animated watermarks, and incorporating features like caching, activity logging, and dynamic business logic for rapid application development and deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional software development methods are used for content and service delivery to networked computing devices, then each application can be customized and tailored to specific needs, but the development process becomes lengthy, complex, and time-consuming due to repetitive implementation of common features

Engineering Contradiction:
Improveapplication customizationVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments content into hierarchical nodes that can be independently defined, stored, and reused across multiple applications. Common features are broken down into discrete content nodes that can be assembled differently for each application, eliminating repetitive development while maintaining customization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The platform creates universal content nodes that can serve multiple functions across different applications. A single content node can be referenced by multiple applications, allowing common features to be defined once and reused universally, dramatically reducing development time while maintaining adaptability.

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

2Reliability

If common features are implemented separately for each application, then each application can be optimized for its specific purpose, but significant duplication of effort occurs across projects

Engineering Contradiction:
Improveapplication optimizationVSAvoiddevelopment effort
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system creates reusable content node templates that can be copied and referenced across multiple applications. Instead of reimplementing common features, developers copy existing validated content nodes and modify them as needed, ensuring consistency and reliability while eliminating duplication of effort.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The platform merges common functionality into shared content nodes that are accessible by multiple applications. By combining repeated elements into single reusable units, the system eliminates wasted development effort while maintaining the ability to optimize each application's specific implementation.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If a rigid data format is enforced for content delivery, then system architecture becomes simpler and easier to implement, but the system loses flexibility in representing diverse content types and adapting to different device requirements

Engineering Contradiction:
Improvesystem architectureVSAvoidcontent representation flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system uses dynamic content nodes that can adapt their structure and properties based on the requesting device's capabilities. Each node contains flexible attributes that can be selectively rendered, allowing the system to maintain simple architecture while delivering customized content representations suited to different devices.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The platform changes content parameters dynamically based on device characteristics. Content nodes store multiple representations with different parameters, and the system selectively applies appropriate parameters when delivering content to specific devices, maintaining architectural simplicity while achieving versatility.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If content is delivered without an abstraction layer, then data exchange between server and devices is more direct and efficient, but content creators are restricted to specific predefined data formats and transport media

Engineering Contradiction:
Improvedata exchange efficiencyVSAvoiddata format flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system introduces content nodes as an intermediary layer between the server's diverse data sources and the devices' various formats. Nodes act as universal intermediaries that translate and adapt content efficiently, maintaining high productivity while enabling flexibility in both source and target formats.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2803214B1Platform for the delivery of content and services to networked connected computing devices
Publication Date: 2020.02.19 CORETHREE
  • EP2803214B1 patent drawingFigure 1
  • EP2803214B1 patent drawingFigure 2
  • EP2803214B1 patent drawingFigure 3

AI summary

Platform for the delivery of content and services to networked connected computing devices, in which the platform stores content by arranging nodes in a hierarchical data format that is capable of semantically representing content, with each node including a unique ID. The hierarchical format acts as an abstraction layer that insulates a content or service creator and the connected computing devices from being restricted (i) to any specific, predefined data format for the content or (ii) to any specific, predefined transport media for exchanging data over the network.