Flexible Tagging System for User Request Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing user computing services face challenges in efficiently managing diverse user data formats and service level agreements, leading to delays in identifying the correct support team or service, resulting in user frustration and resource inefficiencies due to incomplete data and storage of defective user requests.

Innovation Solution

A flexible tagging and searching system that encodes user data, associates critical and non-critical tags with the encoded data, and stores them in a database, allowing for efficient querying and filtering of user requests based on predefined data thresholds and service level agreements, thereby reducing resource consumption and improving support team efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the system stores all user requests including incomplete data, then storage capacity is utilized, but computational resources are wasted identifying and discarding defective requests

Engineering Contradiction:
Improvestorage capacity utilizationVSAvoidcomputational resources
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by encoding user requests with metadata tags and completeness indicators before storage. This allows the system to pre-validate and categorize data during ingestion, so that incomplete requests are identified and flagged before consuming computational resources during query processing. The encoding happens upfront, enabling efficient filtering later without re-processing defective data.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the system processes diverse data formats without standardization, then data flexibility is maintained, but delays occur in determining correct support teams

Engineering Contradiction:
Improvedata format flexibilityVSAvoidsupport team identification delay
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary encoding layer that translates diverse user request formats into a standardized structure with consistent metadata tags. This intermediary representation layer preserves the original data flexibility while enabling uniform processing rules. The encoding schema acts as a mediator between varied input formats and the support team routing logic, eliminating delays caused by format diversity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If the system stores incomplete user requests, then storage space is consumed, but storage space is wasted on defective data

Engineering Contradiction:
Improvestorage space utilizationVSAvoiddata completeness
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent applies local quality by associating specific metadata tags and completeness indicators with individual user requests during encoding. Rather than treating all stored data uniformly, the system attaches localized quality attributes to each record, enabling selective identification and handling of incomplete requests. This allows the system to maintain storage capacity while ensuring data reliability through localized quality markers on each data element.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11386153B1Flexible tagging and searching system
Publication Date: 2022.07.12 AMAZON TECH INC
  • US11386153B1 patent drawing
  • US11386153B1 patent drawing
  • US11386153B1 patent drawing

AI summary

A flexible tagging and searching system can be configured to associate tags with the input data to enable a search of the input data. The flexible tagging and searching system can receive user data and determine an identifier associated with the user data. The system can compare the identifier with other identifiers to determine that the identifier is unique. After determining that the identifier is unique, the system can associate a critical tag with the user data and store the critical tag in a database. Then the system can associate a non-critical tag with the user data. In some instances, the system can return query results such as a set of tag data and/or a set of data items.