Centralized User-List Management via API Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in managing and integrating user-lists from multiple data owners, making it difficult for subscribers to access and utilize these lists without navigating individual data owners' interfaces, which can be cumbersome and inefficient.

Innovation Solution

A method and system that utilize an application programming interface (API) to integrate data owner databases with a centralized searchable database, allowing data owners to manage their user-lists programmatically and providing a unified user-interface for subscribers to browse and license user-lists, while enabling metadata sharing and negotiation between data owners and subscribers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data owners manage their user-lists through individual interfaces, then data owners can directly control their data, but subscribers must navigate multiple interfaces which increases system complexity and reduces ease of operation

Engineering Contradiction:
Improveease of operationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a centralized platform that acts as an intermediary between data owners and subscribers. This platform provides a unified interface for subscribers to access user-lists from multiple data owners without needing to navigate individual data owner interfaces. The platform uses APIs to communicate with data owner databases, enabling centralized management while preserving data owner control through programmatic access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a centralized searchable database is implemented to unify access to user-lists, then ease of operation for subscribers improves, but data integration complexity increases

Engineering Contradiction:
Improveease of operationVSAvoiddata integration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the system into distinct components: data owner databases that store user-lists, an API layer that handles communication and data exchange, and a centralized searchable database that provides unified access. This segmentation allows each component to operate independently while maintaining standardized interfaces, reducing the complexity of data integration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The centralized platform provides universal access to user-lists from multiple data owners through a single interface. The API design enables the system to handle various data formats and structures from different data owners, making the platform multi-functional and adaptable to diverse data sources without requiring separate integration processes for each.

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

3Productivity

If APIs are used to enable programmatic management of user-lists, then productivity and automation improve, but system complexity increases

Engineering Contradiction:
Improvedata management efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces manual interface navigation with programmatic API-based access. Data owners can manage their user-lists through automated API calls rather than manual interface interactions. This substitution increases productivity by enabling bulk operations, automated data synchronization, and programmatic control while the standardized API design keeps the added complexity manageable.

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

Data Source

PatentUS10268739B1User-list management
Publication Date: 2019.04.23 GOOGLE LLC
  • US10268739B1 patent drawing
  • US10268739B1 patent drawing
  • US10268739B1 patent drawing

AI summary

The subject matter of the disclosure is embodied in a method that includes identifying a user-list which is based on owned or permissioned data, wherein the user-list is associated with a corresponding owner database. The method also includes providing an application programming interface (API) configured to communicate with the owner database, and receiving, from the owner database through the API, metadata related to the user-list. The metadata at least includes data describing a category for the user-list. The method further includes storing in a searchable database a user-list identifier corresponding to the user-list and the associated metadata, and providing a user-interface that includes the user-list identifier and the corresponding associated metadata. The user-interface is configured to receive one or more management instructions related to the user-list from a user-list subscriber.