FPGA Cloud Host Development Security via Constraint Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

FPGA cloud host development faces security challenges as users need to ensure both development and protection from malicious attacks on FPGA hardware, while existing methods lack effective security measures to prevent unauthorized access and misuse of third-party IP cores.

Innovation Solution

A method and system where users design and develop FPGAs on a user-side device, uploading a design file to a development management platform that detects the validity of constraint files to prevent malicious attacks and securely synthesizes and writes burner files into the FPGA, while managing third-party IP cores to prevent unauthorized use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users are allowed to freely modify constraint files for FPGA development, then development flexibility and ease of operation are improved, but security and reliability deteriorate due to potential malicious attacks

Engineering Contradiction:
ImproveFPGA development flexibilityVSAvoidFPGA hardware security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a development management platform as an intermediary between the user and the FPGA hardware. This platform validates constraint files before they are applied to the FPGA, acting as a security gatekeeper that allows legitimate development modifications while blocking malicious ones. The platform mediates the conflict by enabling user flexibility within security boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary validation of constraint files through checksum verification and format checking before they are loaded onto the FPGA. By performing security checks in advance rather than reactively, the system prevents malicious constraint files from compromising hardware security while still allowing legitimate development activities.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If third-party IP cores are made accessible to users for FPGA development, then adaptability and functionality are improved, but security and control deteriorate due to unauthorized use and potential attacks

Engineering Contradiction:
ImproveFPGA functionalityVSAvoidUnauthorized IP core access
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The development management platform serves as an intermediary that controls access to third-party IP cores. It manages the distribution and usage of IP cores, ensuring that only authorized users can access and use specific IP cores. This intermediary layer maintains security control while enabling legitimate adaptability and functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms to monitor and track the usage of third-party IP cores. By monitoring IP core access and usage patterns, the system can detect unauthorized use and respond appropriately, maintaining security while allowing legitimate adaptability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3712764B1FPGA cloud host development method and system
Publication Date: 2024.04.10 ALIBABA GROUP HOLDING LTD
  • EP3712764B1 patent drawingFigure 1
  • EP3712764B1 patent drawingFigure 2
  • EP3712764B1 patent drawingFigure 3

AI summary

An FPGA cloud host development method and system are provided. The method may be performed by a development management platform, and comprises: detecting, in response to a design file uploaded by a development device, validity of an actual constraint file included in the design file and corresponding to an FPGA of the FPGA cloud host; synthesis processing the design file in response to detecting that the actual constraint file is valid; and writing a burner file obtained from the synthesis processing into the FPGA. The validity of the actual constraint file is detected, so that a malicious attack of a user to FPGA hardware is prevented.