Request Intermediary Tracking via Embedded Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Request processing systems face challenges in handling the sheer volume of requests from multiple content item providers, leading to difficulties in consolidating content items, understanding response outcomes, and maintaining throughput, often resulting in exhausted service capacity.

Innovation Solution

A request intermediary processing system that includes an internal exchange to manage content item providers, select suitable content items, and embed tracking tokens in responses to facilitate outcome tracking, allowing for the reporting of success metrics and maintaining a persistent connection with external exchanges.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the request processing system consolidates content items from multiple content item providers, then the usefulness of content items for specific users is improved, but the device complexity and difficulty of tracking response outcomes increase

Engineering Contradiction:
Improveresponse outcome trackingVSAvoidrequest processing system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary request processing system that sits between external exchanges and content item providers. This intermediary embeds exchange-specific request identifiers in responses, enabling outcome tracking without requiring complex integration at each content item provider. The intermediary acts as a mediator that standardizes tracking across multiple providers while maintaining service capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the request processing system handles requests from multiple exchanges, then the throughput and service coverage are improved, but the service capacity is exhausted and the system becomes unable to accommodate every request

Engineering Contradiction:
Improverequest processing throughputVSAvoidservice capacity availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the request processing system into an intermediary layer and content item provider layer. The intermediary handles request routing, identifier embedding, and outcome tracking, while content item providers focus on generating appropriate content items. This segmentation allows the system to scale throughput across multiple exchanges while maintaining reliable service capacity by distributing the processing load.

Inventive Principle:
Principle #1Segmentation

3Reliability

If the request processing system maintains minimum service level to each exchange, then the reliability of service to each exchange is improved, but the overall service capacity is severely exhausted

Engineering Contradiction:
Improveminimum service level per exchangeVSAvoidoverall service capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a universal request identifier embedding mechanism in the intermediary that works across all exchanges and content item providers. This multi-functional approach allows the same intermediary infrastructure to handle multiple exchanges simultaneously, maintaining minimum service levels for each exchange while efficiently utilizing overall service capacity through shared resources.

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

Data Source

PatentUS10523770B2Progress tracking for requests made through an intermediary
Publication Date: 2019.12.31 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10523770B2 patent drawing
  • US10523770B2 patent drawing
  • US10523770B2 patent drawing

AI summary

A request intermediary processing system which implements techniques to allow tracking of responses to requests when there is an intermediary. In an embodiment, the intermediary includes an internal exchange. The internal exchange may manage one or more content item providers and select content items from among the one or more internal content item providers to respond to requests. The intermediary may include, when responding to a request, inserting or embedding a token or other means so that the integrity of a content item provider-specific tracking data is maintained, while including request intermediary processing system-specific tracking data.