Third Party Web Content Validation for Fast Ad Rendering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network resources, such as web pages, often include slow-loading online advertisements that degrade user experience due to their complex nature and lack of adherence to validation rules, particularly in AMPHTML pages where ads must conform to specific restrictions to ensure fast rendering.
Innovation Solution
A method and apparatus for third-party validation of web content against a set of rules, where an edge server validates advertisements to ensure they conform to allowed tags, capabilities, and preferences, and signs them cryptographically to ensure quick rendering without degrading user experience, while also checking for malware and suitability for children.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional online advertisements are used in web pages, then advertising content diversity is improved, but page loading speed deteriorates
Solution Approach 1:
The advertisement rendering process is segmented into two paths: a fast path for validated AMP Ads that conform to specific rules, and a default path for other advertisements. This segmentation allows the system to handle diverse ad content while prioritizing fast rendering for compliant ads, thus resolving the contradiction between content diversity and loading speed.
Solution Approach 2:
The system performs preliminary validation of advertisement creatives against a set of rules before rendering. By pre-validating ads and signing them with a key, the system can quickly identify and render compliant ads without degradation, while still allowing diverse ad content to be served through the default path if needed.
2Productivity
If advertisement validation and signing process is implemented, then rendering performance is improved, but system complexity increases
Solution Approach 1:
A third-party validation service acts as an intermediary between the advertisement server and the client network application. This intermediary handles the complex validation and signing processes, while the client application only needs to verify signatures and route ads appropriately, thus improving rendering performance without significantly increasing client-side complexity.
Solution Approach 2:
The client network application includes a client runtime that can independently verify advertisement signatures and determine rendering paths without requiring complex server-side validation logic. This self-service capability simplifies the overall system by distributing validation responsibilities to the client side.
3Ease of operation
If fast rendering path is used for validated ads, then user experience is improved, but security risks increase
Solution Approach 1:
The system performs preliminary security validation by checking advertisement signatures before allowing fast rendering. By pre-validating that ads conform to approved rules and signing them with a trusted key, the system ensures that only secure ads receive the performance benefit of the fast path, thus improving user experience without compromising security.
Solution Approach 2:
The validation system provides feedback to the client application about whether an advertisement has been validated and signed. This feedback mechanism allows the system to dynamically route ads to appropriate rendering paths based on their validation status, ensuring that security requirements are met while still providing fast rendering for compliant ads.
Data Source
AI summary
A client network application transmits a request for a network resource to a server. The client receives a response that includes a network resource that includes a digital signature that represents that at least a portion of the received network resource has been determined to be conforming to a set of rule(s). The client determines whether the digital signature is valid. If it is valid, the client processes the network resource in a pipeline (e.g., a fast path pipeline) and if it is not valid, the client may process the network resource in a different pipeline (e.g., a non fast-path pipeline).