Data access isolation method and system under bare kernel running environment

By allocating independent memory areas and configuring access permissions for each module in a bare-core operating environment, and combining this with MMU hardware interception of anomalies, the problem of fault amplification caused by mutual influence between modules was solved, and stable data access isolation between modules was achieved.

CN122450862APending Publication Date: 2026-07-24NARI NANJING CONTROL SYSTEM CO LTD +1
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
NARI NANJING CONTROL SYSTEM CO LTD
Filing Date
2026-04-16
Publication Date
2026-07-24

AI Technical Summary

Technical Problem

In a bare-core operating environment, the mutual influence between modules can lead to an expansion of the fault range. A single module failure may cause the entire system to crash. Existing technologies cannot effectively isolate data access between multiple tasks of the same type.

Method used

The bare-core management program assigns independent module numbers, dedicated memory areas, and shared memory areas to each module, configures access permissions, switches permissions when calling across modules, and uses the MMU hardware to intercept abnormal access, record abnormal information, and prevent the spread of faults.

Benefits of technology

It effectively prevents single-module anomalies from damaging the code or data of other modules, reduces the scope of failures, supports inter-module calls, and does not limit the types and number of modules.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122450862A_ABST
    Figure CN122450862A_ABST
Patent Text Reader

Abstract

The application discloses a data access isolation method and system in a bare core running environment, wherein each module is compiled into an independent ELF file, a management program allocates a unique ID, a special memory area and a shared memory area for each module, and access permission is configured through an MMU to realize address space isolation between modules; periodic scheduling and cross-module calling are completed through TLB switching; when a module abnormally accesses beyond the range, the operation is blocked by the MMU hardware and an exception is triggered, the management program isolates the fault module, stops task scheduling and intercepts invalid calling to avoid fault diffusion. The application can realize safe isolation and normal interaction of multiple modules in a bare core environment, and improve system stability and reliability.
Need to check novelty before this filing date? Find Prior Art