Event-Based Content Selection Using Calendar Parsing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to effectively provide relevant third-party content to devices based on future events and activities associated with a user, as they rely on browsing history which may not cover all relevant topics, and lack efficient methods to utilize event-related information from calendars to suggest relevant content.

Innovation Solution

A method and system that create a data structure with relevancy scores for keyword clusters related to events, allowing for the selection of content based on event parameters and time periods, using event parsing and relevancy score generation modules to identify relevant content for display on devices associated with calendar events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If content is served based on browsing history, then content can be provided to users, but the content may not be relevant to future events and activities

Engineering Contradiction:
Improvecontent relevance to user's future eventsVSAvoidbrowsing history coverage
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system performs preliminary action by accessing calendar events before they occur and using them to determine relevant content. The event parsing module extracts information from calendar events in advance, and the relevancy score generation module pre-calculates scores for keyword clusters based on these events, enabling content to be selected that is relevant to future user activities rather than relying solely on past browsing behavior.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism by using calendar events as a bridge between user information and content selection. The event parsing module acts as an intermediary that translates calendar event data into structured event parameters, which then inform the keyword cluster selection and content relevance determination, filling the gap between browsing history and future event relevance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If event-related information from calendars is utilized to suggest content, then content relevance improves, but system complexity increases

Engineering Contradiction:
Improvecontent relevance to eventsVSAvoidsystem structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the content selection process into distinct modular components: an event parsing module that extracts calendar information, an event parameters determination module that structures the data, a keyword cluster determination module that identifies relevant topics, and a relevancy score generation module that ranks content. This modular architecture manages complexity by separating concerns while maintaining event-based content relevance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses intermediary modules to manage complexity. The event parsing module serves as an intermediary between the calendar system and the content selection logic. The event parameters determination module acts as another intermediary layer that translates raw calendar data into structured parameters that can be used by subsequent modules, thereby simplifying the overall system architecture while enabling sophisticated event-based content selection.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If keyword clusters are generated for multiple time periods, then content timing accuracy improves, but data processing requirements increase

Engineering Contradiction:
Improvecontent timing accuracyVSAvoiddata processing volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by pre-generating relevancy scores for multiple keyword clusters across different time periods relative to events. The relevancy score generation module creates these scores in advance based on event parameters, so that when content needs to be served, the system can quickly retrieve and use the pre-calculated scores rather than computing them in real-time, thereby maintaining timing accuracy while reducing processing burden during content delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies parameter changes by varying the time period parameter to generate different relevancy scores for the same keyword cluster at different stages relative to an event. For example, a keyword cluster may have high relevancy 3 days before an event but low relevancy 3 days after the event. This dynamic parameter adjustment enables precise content timing while systematically managing the data processing requirements through structured score generation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11463541B2Providing content based on event related information
Publication Date: 2022.10.04 GOOGLE LLC
  • US11463541B2 patent drawing
  • US11463541B2 patent drawing
  • US11463541B2 patent drawing

AI summary

Systems and methods for selecting content based on an event associated with a device identifier are provided. One or more processors can receive a request to serve content. The processors can identify a device identifier associated with the request. The processors can determine, from the device identifier, an event for which to serve content. The processors can determine, from the request, a length of time between a time the request to serve content is received and a time at which the event is scheduled to occur. The processors can select, based on the determined length of time and event parameters associated with the event, content for display and provide the selected content for display at a computing device associated with the device identifier.