Font Protection Management via Intermediary Service Authorization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Font providers are hesitant to license their content due to concerns about piracy, as existing techniques lack effective digital rights management (DRM) interoperable across platforms, leading to unprotected font distribution and compliance burdens on developers.

Innovation Solution

A font protection management system that involves obtaining a font package with obfuscated fonts, which requires authorization from a font protection service before use, allowing only authorized de-obfuscation and use of protected fonts within applications, with default fonts used if authorization is not granted.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If fonts are embedded unprotected in an application, then ease of operation is improved, but font security deteriorates

Engineering Contradiction:
Improveease of font usageVSAvoidfont piracy risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

A font protection service acts as an intermediary between the application and the font data. The service receives authorization requests from the application, verifies licensing terms, and returns decryption keys or authorization tokens. This intermediary mechanism enables font protection without requiring developers to implement complex custom DRM solutions, resolving the contradiction between ease of operation and font security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If individual developers negotiate licensing arrangements with font providers, then font security is improved, but device complexity increases

Engineering Contradiction:
Improvefont piracy preventionVSAvoidcompliance burden on developers
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The font protection service provides universal licensing management that works across multiple applications and font providers through a standardized interface. Instead of each developer negotiating separate arrangements with each font provider, the service handles authorization requests uniformly, reducing device complexity while maintaining font security.

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

3Object-affected harmful factors

If standard font encryption processes are implemented, then font security is improved, but ease of manufacture deteriorates

Engineering Contradiction:
Improvefont protectionVSAvoidimplementation difficulty
Core Design Contradiction:
Object-affected harmful factorsVSEase of manufacture

Solution Approach 1:

The font protection service enables self-service font protection where the system automatically handles encryption, authorization request generation, and key management. Applications include font packages with embedded protection metadata and automatically generate authorization requests when fonts are loaded, eliminating the need for manual encryption implementation and reducing ease of manufacture deterioration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9471755B2Font protection management
Publication Date: 2016.10.18 ADOBE INC
  • US9471755B2 patent drawing
  • US9471755B2 patent drawing
  • US9471755B2 patent drawing

AI summary

Font protection management is described. In one or more implementations, a font package is obtained for an application and includes fonts that are protected by obfuscation. When the application is launched, a request to determine whether use of the protected fonts is authorized in connection with the application may be communicated to a font protection service. A response that is indicative of authorization to use the protected fonts in connection with the application may be received from the font protection service. When the response indicates that use of the protected fonts is authorized, the protected fonts may be de-obfuscated and subsequently used in connection with the application. When the response indicates that use of the protected fonts is not authorized in connection with the application, however, default fonts may be used with the application instead.