Multi-Service Business Platform with Ontology and Event Datastores

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for marketing, sales, and service interactions with customers require complex and time-consuming tasks to integrate and synchronize data across different databases and systems, lacking unified support for customer interactions and customizability in CRM systems.

Innovation Solution

A multi-service business platform with an ontology datastore and event datastore that tracks event instances across multiple services, allowing for the creation and management of custom objects and event records, enabling unified event tracking and customizability across CRM, payment, and content management systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional separate systems are used for marketing, sales, and service activities, then each activity can be managed independently, but complex and time-consuming tasks are required to integrate and synchronize data across different databases and systems

Engineering Contradiction:
Improvedata integration reliabilityVSAvoiddata synchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges multiple separate systems (marketing, sales, service) into a unified multi-service business platform that shares common data structures and event systems. This eliminates the need for complex data integration and synchronization between separate databases, as all services access the same unified data model through the ontology datastore and event datastore.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal data structures (ontology objects and event records) that serve multiple functions across different business activities. The same object models and event types are used by marketing, sales, and service services, allowing a single data structure to fulfill multiple purposes and eliminating redundant data management tasks.

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

2Adaptability or versatility

If conventional CRM systems are used, then customer interactions can be tracked, but the systems lack customizability for specific business needs and unified support across multiple services

Engineering Contradiction:
Improvesystem customizabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the system into distinct layers: ontology definitions (data models), event definitions (behavioral patterns), and service implementations (business logic). This segmentation allows customization at each layer independently - businesses can modify ontology objects, add event types, or configure services without affecting the overall system architecture, thereby increasing adaptability while managing complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic and configurable data structures where ontology objects and event records can be extended and customized based on specific business needs. The system allows adding custom properties, relationships, and event types without requiring structural changes to the core system, enabling high adaptability while maintaining architectural simplicity through standardized extension mechanisms.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12406234B2Multi-service business platform system having event systems and methods
Publication Date: 2025.09.02 HUBSPOT INC
  • US12406234B2 patent drawing
  • US12406234B2 patent drawing
  • US12406234B2 patent drawing

AI summary

The disclosure is directed to various ways of improving the functioning of computer systems, information networks, data stores, search engine systems and methods, and other advantages. Among other things, provided herein are methods, systems, components, processes, modules, blocks, circuits, sub-systems, articles, and other elements (collectively referred to in some cases as the “platform” or the “system”) that collectively enable, in one or more datastores (e.g., where each datastore may include one or more databases) and systems. A system and method for maintaining unified events such as maintaining an ontology data store and an event datastore. The event datastore may store event record instances of one or more different types of event records. The system and method may identify one or more types of event records that track a specific event type based on a specific event type of a new event instance.