Container File Access Prioritization for Reliable Serialized Writes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing container systems struggle to serialize and prioritize writing resource utilization of device files based on the confidence level or properties of container instances, leading to potential blocking or unauthorized access that can jeopardize operational reliability.

Innovation Solution

A method involving an access control unit that checks an access identifier against an access guideline to assign prioritization levels for access requests, ensuring that access to files is serialized and restricted based on properties such as container instance signatures and network interfaces, using an expansion module or independent unit within the container runtime environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If write accesses to the file are serialized to ensure exclusive access, then system reliability is improved, but access time and productivity deteriorate

Engineering Contradiction:
Improvesystem reliabilityVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic prioritization of container instances based on confidence levels. The serialization mechanism adapts its behavior by assigning different priority levels to different containers, allowing critical containers to bypass delays while less critical ones are serialized. This dynamic approach maintains reliability through serialization while minimizing time loss for high-priority operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of access priority by evaluating confidence levels of container instances. By modifying the priority parameter dynamically based on container properties and access guidelines, the system ensures that serialization maintains reliability while high-confidence containers receive preferential treatment, reducing their access time.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If access control is implemented to prevent unauthorized access, then system security is improved, but access complexity increases

Engineering Contradiction:
Improvesystem securityVSAvoidaccess control complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the access control mechanism into modular components: confidence level evaluation, priority assignment, and access guideline checking. Each component operates independently, simplifying the overall complexity while maintaining strong security. The segmentation allows the system to enforce security policies without requiring a monolithic complex access control structure.

Inventive Principle:
Principle #1Segmentation

3Productivity

If multiple container instances access the same file in parallel, then productivity is improved, but system reliability deteriorates due to potential conflicts

Engineering Contradiction:
Improveaccess throughputVSAvoidaccess consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically adjusts parallel access permissions based on container confidence levels and access guidelines. High-confidence containers may access files in parallel while lower-confidence ones are serialized, creating a dynamic balance between productivity and reliability that adapts to the specific access scenario.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250238535A1Prioritizing access by a container instance to a file in a file system resource
Publication Date: 2025.07.24 SIEMENS AG
  • US20250238535A1 patent drawing
  • US20250238535A1 patent drawing

AI summary

A method for prioritizing access by a container instance to a file in a file system resource is provided, including: receiving, in a runtime environment of the container instance, an access request for the container instance to access the file, the access request comprising an access identifier that denotes at least one property of the accessing container instance, checking the at least one property in the access identifier against an access guideline, which includes a prioritization level for accessing at least the one file on the basis of the properties of the access identifier, by way of an access control unit in the container runtime environment, and allocating an access permission with a prioritization level relating to the access request on the basis of the result of the check, forwarding the access request to the file on the basis of the allocated prioritization level.