Entity Authentication Engine for Web Query Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional systems face inefficiencies in processing web requests due to the need for repeated formatting adjustments, leading to increased computing, memory, and network resource usage, resulting in network bottlenecks and reduced speed when querying different search web pages with varying formats.

Innovation Solution

A system that employs a search dictionary to store web links corresponding to specific search web pages, pre-formats web requests to match the appropriate format for each page, and uses hash functions to efficiently process and rank search results, thereby reducing resource consumption and network traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the system sends web search requests to multiple search web pages with different formats, then the entity validation capability is improved, but the computing resource consumption and network traffic increase significantly

Engineering Contradiction:
Improveentity validation capabilityVSAvoidcomputing resource consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system pre-converts entity names to hash values before sending search requests to multiple search web pages. This preliminary hashing action eliminates the need for each search web page to perform format validation and conversion, significantly reducing computing resource consumption while maintaining the ability to query multiple different search formats simultaneously

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the system repeatedly queries search web pages with incorrect formats, then the user can resubmit corrected requests, but the network resources are wasted and network bottlenecks occur

Engineering Contradiction:
Improverequest correction capabilityVSAvoidnetwork traffic
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system performs format conversion to the appropriate search web page format before sending the request, ensuring correct formatting from the outset. This preliminary formatting action prevents repeated queries and reduces network traffic, while still allowing users to resubmit requests if needed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces a format conversion intermediary layer between the user's search request and the search web pages. This intermediary automatically converts requests to the correct format for each target search web page, eliminating the need for users to manually correct formats and reducing repeated network traffic

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If the system processes web requests without pre-formatting, then the request processing is simpler, but the network speed decreases due to repeated formatting adjustments

Engineering Contradiction:
Improverequest processing complexityVSAvoidnetwork speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The system performs format conversion to the appropriate search web page format before sending the request, ensuring correct formatting from the outset. This preliminary formatting action prevents repeated queries and reduces network traffic, while still allowing users to resubmit requests if needed

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10839028B2System for querying web pages using a real time entity authentication engine
Publication Date: 2020.11.17 BANK OF AMERICA CORP
  • US10839028B2 patent drawing
  • US10839028B2 patent drawing
  • US10839028B2 patent drawing

AI summary

A system for querying web pages to validate entity names is disclosed. The disclosed system receives a request for validating an entity name. The system identifies a search web link based on the information in the request. The system converts the request to a format appropriate for a search web page corresponding to the search web link. Then, the system sends the formatted request to the search web page via the search web link. The system receives a result web page and extracts a set of result entity names. The system then computes a hash value for the entity name in the request and each of the result entity names. Next, the system compares the hash value computed for the entity name in the request with hash values computed for each of the result entity names and determines a matching score for each of the result entity names based on the comparison of the hash values.