Secure Memory Framework for Stream Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing devices face challenges in securely storing and retrieving stream data from input devices, such as cameras and fingerprint sensors, as the data can be tampered with during transmission between the device and the application or operating system, leading to potential playback or middleman attacks.

Innovation Solution

A method and device for securely storing stream data by using a secure memory framework that allocates secured buffers for payload data and separates headers from payloads, ensuring data integrity and preventing tampering, with a processor configured to receive and store stream data in secure memory while providing data frames to applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If stream data is stored in memory for processing, then data availability for applications is improved, but data integrity and security deteriorate due to potential tampering during transmission

Engineering Contradiction:
Improvedata integrityVSAvoiddata tampering
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments stream data into distinct header portions and payload portions, storing them in separate memory locations. The header is stored in a first memory location while the payload is stored in a second memory location, allowing independent protection and processing of each component to prevent tampering while maintaining availability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a secure memory framework as an intermediary between the stream source and applications. This framework includes secured buffers that act as a protective layer, verifying data integrity through cryptographic operations and providing a secure transmission path that prevents tampering during data flow.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If stream data is stored in secured buffers with separation of headers and payloads, then data security is improved, but memory management complexity increases

Engineering Contradiction:
Improvedata securityVSAvoidmemory management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal secure memory framework that handles multiple data types and stream sources through a standardized interface. The framework provides unified services for data verification, storage, and retrieval across different input devices, reducing the need for device-specific security implementations and simplifying overall system complexity.

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

Solution Approach 2:

The secure memory framework performs self-service operations including automatic data verification, integrity checking, and secure storage without requiring manual intervention. The system autonomously manages cryptographic operations and memory allocation, reducing the burden on applications and simplifying memory management complexity.

Inventive Principle:
Principle #25Self-service

3Productivity

If payload data is stored contiguously in secured buffers, then data retrieval efficiency is improved, but memory allocation complexity increases

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidmemory allocation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary memory allocation and buffer setup when the secure memory framework is initialized or when a new data stream is detected. Memory regions are pre-reserved and configured with appropriate security attributes before data arrives, allowing efficient contiguous storage and retrieval without complex real-time allocation decisions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic memory allocation strategies that adapt to varying data stream characteristics. The framework can adjust buffer sizes and allocation patterns based on the actual data being received, allowing efficient contiguous storage for performance-critical operations while maintaining flexibility to handle different data types and sizes.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10372947B2Parsing, processing, and/or securing stream buffers
Publication Date: 2019.08.06 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10372947B2 patent drawing
  • US10372947B2 patent drawing
  • US10372947B2 patent drawing

AI summary

Described are examples for securely storing stream data received from a stream source. Stream data can be received from the stream source for storing in one or more secured buffers of a secure memory, wherein the stream data includes a header portion generated by a driver for the stream source and a payload portion generated from the stream source. The payload portion of the stream data can be stored in the one or more secured buffers and contiguous to a previous payload portion of previous stream data received from the stream source. The header portion of the stream data can be stored in another portion of the secure memory or a non-secure memory. A data frame, from the one or more secured buffers, comprising at least the payload portion of the stream data and the previous payload portion of the previous stream data can be provided to an application.