A multi-system task scheduling management system

By designing a multi-system task scheduling management system, defining common interface specifications and creating adapters for each RTOS, the problem of adaptation complexity of RTOS platform is solved, the unified management of applications on different RTOSes is realized, and the portability of code is improved. and development efficiency.

CN118535220BActive Publication Date: 2024-11-19重庆蓝鲸智联科技有限公司
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202410664514.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-05-27
Publication Date
2024-11-19
Estimated Expiration
2044-05-27

AI Technical Summary

Technical Problem

The application adaptation process of existing real-time operating systems (RTOS) on different platforms is cumbersome, resulting in complex development and high cost.

Method used

Design a multi-system task scheduling management system, and realize cross-platform task scheduling management by defining common interface specifications and creating adapters for each RTOS, including specification definition modules, adapter creation modules, user selection modules, error correction modules, and support modules and test modules to ensure that the application runs on different RTOSs.

Benefits of technology

It realizes unified packaging management of applications across RTOS, reduces dependence on RTOS, improves code portability and maintainability, simplifies the embedded system development process, and reduces development costs and risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118535220B_ABST
    Figure CN118535220B_ABST
Patent Text Reader

Abstract

The present invention relates to the technical field of real-time systems, and in particular to a multi-system task scheduling management system, comprising a specification definition module, an adapter creation module, a scheduling module, a user selection module, an error correction module, a support module and a test module; the specification definition module is used to define a general interface specification; the adapter creation module is used to create an adapter for each target RTOS to implement the general interface specification; the scheduling module is used to call the adapter method to perform corresponding operations in the implementation of the general interface; the user selection module is used to allow the user to select the RTOS to be used at runtime, and load the corresponding RTOS adapter according to the user's selection; the present application designs a general interface specification, and then creates an adapter for each target RTOS, ensuring that the adapter implements the general interface defined in the specification, so that the application can run on different RTOSs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of real-time systems, and in particular to a multi-system task scheduling management system. Background Art

[0002] RTOS refers to a real-time system. The correctness of a real-time system depends not only on the logical results of the system calculations, but also on the time to produce this result. A real-time system is a system that can complete system functions and respond to external or internal, synchronous or asynchronous time within a specified or determined time. Therefore, a real-time system should have the ability to recognize and process discrete events within a pre-defined time range; the system should be able to process and store large amounts of data required by the control system.

[0003] There are many real-time operating systems at present. The working principles, task scheduling algorithms, task management and synchronization mechanisms of different RTOS are different. Common RTOS include FreeRTOS, RTOS-32, VxWorks, QNX, RTT, ThreadX, etc. If you want to enable applications to run on different RTOS, each system needs to be adapted to the peripheral drivers and communication interfaces, which makes the whole process more cumbersome. Summary of the invention

[0004] The purpose of the present invention is to provide a multi-system task scheduling management system, by designing a general interface specification, and then creating an adapter for each target RTOS, ensuring that the adapter implements the general interface defined in the specification, so that the application can run on different RTOS.

[0005] To achieve the above object, the present invention provides a multi-system task scheduling management system, including a specification definition module, an adapter creation module, a scheduling module, a user selection module, an error correction module, a support module and a test module;

[0006] The specification definition module, the adapter creation module, the scheduling module, the user selection module, the error correction module, the support module and the test module are connected in sequence;

[0007] The specification definition module is used to define a general interface specification;

[0008] The adapter creation module is used to create an adapter for each target RTOS to implement the general interface specification;

[0009] The scheduling module is used to call the adapter method to perform corresponding operations in the implementation of the general interface;

[0010] The user selection module is used to allow the user to select the RTOS to be used during runtime, and load the corresponding RTOS adapter according to the user's selection;

[0011] The error correction module is used to implement an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS specific errors or abnormal situations;

[0012] The support modules are used to handle platform-specific issues and differences using conditional compilation or cross-platform libraries;

[0013] The test module is used to perform comprehensive testing and verification on different RTOS to ensure that the common interface can work properly in various situations.

[0014] Wherein, the error correction module includes an error processing unit and a debugging unit; the error processing unit is connected to the user selection module, and the debugging unit is connected to the error processing unit;

[0015] The error handling unit is used to provide error codes and error information of RTOS in the encapsulation layer and the adapter;

[0016] The debugging unit is used to help users debug task scheduling and RTOS adapter.

[0017] Wherein, the test module includes a task creation test unit and a task suspension test unit; the task suspension test unit is connected to the task creation test unit;

[0018] The task creation test unit is used to test the task creation function of different RTOS under the universal interface;

[0019] The task suspension test unit is used to test the task suspension functions of different RTOS under a universal interface.

[0020] Wherein, the test module further comprises a task recovery test unit; the task recovery test unit is connected to the task suspension test unit;

[0021] The task recovery test unit is used for task recovery functions of different RTOS under a common interface.

[0022] Wherein, the test module further comprises a timer test unit; the timer test unit is connected to the task recovery test unit;

[0023] The timer test unit is used to test the timer functions of different RTOS under a universal interface.

[0024] Wherein, the multi-system task scheduling management system further comprises a demonstration module; the demonstration module is connected to the timer test unit;

[0025] The demo module is used to create sample applications that demonstrate how to use the common interface on different RTOS.

[0026] Wherein, the multi-system task scheduling management system further includes a version update module and an optimization module; the version update module is connected to the demonstration module, and the optimization module is connected to the version update module;

[0027] The version update module is used to track and manage changes to the general interface and regularly maintain the general interface;

[0028] The optimization module is used to optimize the performance characteristics of different RTOS.

[0029] The multi-system task scheduling management system further comprises a safety detection module and a test suite establishment module; the safety detection module is connected to the optimization module; the test suite establishment module is connected to the safety detection module;

[0030] The security detection module is used to detect potential security holes in the universal interface and adapter;

[0031] The test suite building module is used to build an automated test suite to ensure that each version of the common interface on different RTOS is fully tested.

[0032] A multi-system task scheduling management system of the present invention, first, the specification definition module defines a general interface specification, including task creation, task deletion, task suspension, task recovery, timer creation, etc., these interface specifications should be platform-independent to ensure consistency on different RTOS. The adapter creation module creates an adapter or wrapper for each target RTOS to implement the general interface specification. The adapter should contain the underlying function call of a specific RTOS to implement the function of the general interface. Each adapter should be responsible for mapping the call of the general interface to the function call of the specific RTOS. In the implementation of the general interface, the scheduling module calls the method of the adapter to perform the corresponding operation, and these methods should call the corresponding adapter according to different RTOS to perform the task scheduling management operation. The user selection module implements a mechanism to allow the user to select the RTOS to be used at runtime, which can be implemented through a configuration file, a command line parameter or other user interface. The corresponding RTOS adapter is loaded according to the user's selection. The error correction module implements an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS-specific errors or abnormal situations, provide meaningful error codes and error information, so that users can diagnose and solve problems, and integrate debugging tools to help users debug task scheduling and RTOS adapters. The support module ensures that the package management solution can support different RTOS and hardware platforms, and uses conditional compilation or cross-platform libraries to handle platform-specific problems and differences. The test module performs comprehensive testing and verification on different RTOS to ensure that the general interface can work properly in various situations. The test includes various functions such as task creation, suspension, recovery, timer, etc., and simulates the environment of different RTOS to check the correctness and performance of the adapter. This application designs a general interface specification and then creates an adapter for each target RTOS to ensure that the adapter implements the general interface defined in the specification, so that the application can run on different RTOS without having to worry about the differences in the underlying RTOS; at the same time, providing error handling, cross-platform support, testing and documentation are key elements to ensure the success of the solution. Through strict design, testing and maintenance processes, a powerful unified package management solution for task scheduling management interface can be implemented, enabling applications to run on different RTOS, reducing dependence on RTOS, and improving code portability and maintainability, which also helps to accelerate the development process of embedded systems and reduce development costs and risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.

[0034] Figure 1 It is a schematic diagram of the overall structure of the first embodiment of the present invention.

[0035] Figure 2 It is a schematic diagram of the structure of the error correction module of the first embodiment of the present invention.

[0036] Figure 3 It is a schematic diagram of the structure of the test module of the first embodiment of the present invention.

[0037] Figure 4 It is a schematic diagram of the overall structure of the second embodiment of the present invention.

[0038] Figure 5 It is a schematic diagram of the overall structure of the third embodiment of the present invention.

[0039] 101-Specification definition module, 102-Adapter creation module, 103-Scheduling module, 104-User selection module, 105-Error correction module, 106-Support module, 107-Test module, 108-Error handling unit, 109-Debug unit, 110-Task creation test unit, 111-Task suspension test unit, 112-Task recovery test unit, 113-Timer test unit, 201-Demonstration module, 202-Version update module, 203-Optimization module, 204-Security detection module, 205-Test suite establishment module, 301-Extension module, 302-User training module, 303-Performance tuning module, 304-Regular review module, 305-Cooperation module. DETAILED DESCRIPTION

[0040] The first embodiment of the present application is:

[0041] See also Figure 1-Figure 3 ,in, Figure 1 is a schematic diagram of the overall structure of the first embodiment of the present invention, Figure 2 is a schematic diagram of the structure of an error correction module according to a first embodiment of the present invention, Figure 3 It is a schematic diagram of the structure of the test module of the first embodiment of the present invention.

[0042] The present invention provides a multi-system task scheduling management system, comprising a specification definition module 101, an adapter creation module 102, a scheduling module 103, a user selection module 104, an error correction module 105, a support module 106 and a test module 107; the error correction module 105 comprises an error handling unit 108 and a debugging unit 109; the test module 107 comprises a task creation test unit 110 and a task suspension test unit 111; a general interface specification is designed through the above scheme, and then an adapter is created for each target RTOS to ensure that the adapter implements the general interface defined in the specification, so that the application can run on different RTOS.

[0043] For this specific implementation, the specification definition module 101, the adapter creation module 102, the scheduling module 103, the user selection module 104, the error correction module 105, the support module 106 and the test module 107 are connected in sequence;

[0044] The specification definition module 101 is used to define a general interface specification;

[0045] The adapter creation module 102 is used to create an adapter for each target RTOS to implement the general interface specification;

[0046] The scheduling module 103 is used to call the adapter method to perform corresponding operations in the implementation of the general interface;

[0047] The user selection module 104 is used to allow the user to select the RTOS to be used during operation, and load the corresponding RTOS adapter according to the user's selection;

[0048] The error correction module 105 is used to implement an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS specific errors or abnormal situations;

[0049] The support module 106 is used to handle platform-specific issues and differences using conditional compilation or cross-platform libraries;

[0050] The test module 107 is used to perform comprehensive testing and verification on different RTOS to ensure that the universal interface can work properly under various circumstances.

[0051] First, the specification definition module 101 defines a general interface specification, including task creation, task deletion, task suspension, task recovery, timer creation, etc. These interface specifications should be platform-independent to ensure consistency on different RTOS. The adapter creation module 102 creates an adapter or wrapper for each target RTOS to implement the general interface specification. The adapter should contain the underlying function calls of a specific RTOS to implement the functions of the general interface. Each adapter should be responsible for mapping the calls of the general interface to the function calls of a specific RTOS. In the implementation of the general interface, the scheduling module 103 calls the methods of the adapter to perform corresponding operations. These methods should call the corresponding adapters according to different RTOS to perform task scheduling management operations. The user selection module 104 implements a mechanism that allows users to select the RTOS to be used at runtime, which can be achieved through configuration files, command line parameters or other user interfaces. The corresponding RTOS adapter is loaded according to the user's selection. The error correction module 105 implements an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS-specific errors or abnormal situations, provide meaningful error codes and error information so that users can diagnose and solve problems, and integrate debugging tools to help users debug task scheduling and RTOS adapters. The support module 106 ensures that the package management solution can support different RTOS and hardware platforms, and uses conditional compilation or cross-platform libraries to handle platform-specific issues and differences. The test module 107 performs comprehensive testing and verification on different RTOS to ensure that the general interface can work properly in various situations. The test includes various functions such as task creation, suspension, recovery, timer, etc., and simulates the environment of different RTOS to check the correctness and performance of the adapter. This application designs a general interface specification and then creates an adapter for each target RTOS to ensure that the adapter implements the general interface defined in the specification, so that the application can run on different RTOS.

[0052] The error handling unit 108 is connected to the user selection module 104, and the debugging unit 109 is connected to the error handling unit 108;

[0053] The error handling unit 108 is used to provide error codes and error information of the RTOS in the encapsulation layer and the adapter;

[0054] The debugging unit 109 is used to help users debug task scheduling and RTOS adapter.

[0055] The error handling unit 108 implements an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS-specific errors or abnormal situations, and provides meaningful error codes and error information so that users can diagnose and solve problems; the debugging unit 109 integrates debugging tools to help users debug task scheduling and RTOS adapters.

[0056] Secondly, the task suspension test unit 111 is connected to the task creation test unit 110;

[0057] The task creation test unit 110 is used to test the task creation function of different RTOS under the universal interface;

[0058] The task suspension test unit 111 is used to test the task suspension functions of different RTOS under a universal interface.

[0059] The task suspension test unit 111 and the task creation test unit 110 perform comprehensive testing and verification on different RTOS to ensure that the universal interface can work properly in various situations. The test includes task creation and suspension functions, simulating the environment of different RTOS to check the correctness and performance of the adapter.

[0060] At the same time, the task recovery test unit 112 is connected to the task suspension test unit 111;

[0061] The task recovery test unit 112 is used for task recovery functions of different RTOS under a common interface.

[0062] The task recovery test unit 112 performs comprehensive testing and verification on different RTOS to ensure that the universal interface can work properly in various situations. The test includes the function of task recovery and simulates the environment of different RTOS to check the correctness and performance of the adapter.

[0063] In addition, the timer test unit 113 is connected to the task recovery test unit 112;

[0064] The timer testing unit 113 is used to test the timer functions of different RTOS under the universal interface.

[0065] The timer test unit 113 performs comprehensive testing and verification on different RTOS to ensure that the universal interface can work properly in various situations. The test includes the function of the timer, simulating the environment of different RTOS to check the correctness and performance of the adapter.

[0066] When using the present invention, first, the specification definition module 101 defines a general interface specification, including task creation, task deletion, task suspension, task recovery, timer creation, etc. These interface specifications should be platform-independent to ensure consistency on different RTOS. The adapter creation module 102 creates an adapter or wrapper for each target RTOS to implement the general interface specification. The adapter should contain the underlying function calls of a specific RTOS to implement the functions of the general interface. Each adapter should be responsible for mapping the calls of the general interface to the function calls of a specific RTOS. In the implementation of the general interface, the scheduling module 103 calls the methods of the adapter to perform corresponding operations, and these methods should call the corresponding adapters according to different RTOS to perform task scheduling management operations. The user selection module 104 implements a mechanism that allows the user to select the RTOS to be used at runtime, which can be achieved through configuration files, command line parameters or other user interfaces. Load the corresponding RTOS adapter according to the user's selection. The error correction module 105 implements an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS-specific errors or abnormal situations, provides meaningful error codes and error information so that users can diagnose and solve problems, and integrates debugging tools to help users debug task scheduling and RTOS adapters. The support module 106 ensures that the encapsulation management solution can support different RTOS and hardware platforms, and uses conditional compilation or cross-platform libraries to handle platform-specific problems and differences. The test module 107 performs comprehensive testing and verification on different RTOS to ensure that the general interface can work properly in various situations. The test includes various functions such as task creation, suspension, recovery, timer, etc., and simulates the environment of different RTOS to check the correctness and performance of the adapter. This application designs a general interface specification and then creates an adapter for each target RTOS to ensure that the adapter implements the general interface defined in the specification, so that the application can run on different RTOS without having to worry about the differences in the underlying RTOS; at the same time, providing error handling, cross-platform support, testing and documentation are key elements to ensure the success of the solution. Through strict design, testing and maintenance processes, a powerful task scheduling management interface unified encapsulation management solution can be implemented, enabling applications to run on different RTOS, reducing dependence on RTOS, and improving code portability and maintainability, which also helps to accelerate the development process of embedded systems and reduce development costs and risks.

[0067] The second embodiment of the present application is:

[0068] Based on the first embodiment, please refer to Figure 4 ,in, Figure 4 It is a schematic diagram of the overall structure of the second embodiment of the present invention.

[0069] The multi-system task scheduling management system provided by the present invention further includes a demonstration module 201, a version update module 202, an optimization module 203, a security detection module 204 and a test suite establishment module 205;

[0070] For this specific implementation, the demonstration module 201 is connected to the timer test unit 113;

[0071] The demonstration module 201 is used to create a sample application to demonstrate how to use the common interface on different RTOS.

[0072] The demonstration module 201 provides detailed documentation, including instructions for use, API documentation, and sample codes, to help users understand how to use and integrate the universal interface, create sample applications, and demonstrate how to use the universal interface on different RTOS.

[0073] The version update module 202 is connected to the demonstration module 201, and the optimization module 203 is connected to the version update module 202;

[0074] The version update module 202 is used to track and manage changes to the general interface and regularly maintain the general interface;

[0075] The optimization module 203 is used to optimize the performance characteristics of different RTOS.

[0076] The version update module 202 uses version control tools, such as Git, to track and manage changes to the common interface, and regularly maintains the common interface to adapt to new versions or updates of different RTOS. The optimization module 203 optimizes the performance characteristics of different RTOS. For example, in some RTOS, priority inheritance may be a performance key point and requires special processing. The performance analysis tool provided by the RTOS is used to detect bottlenecks and perform optimization.

[0077] Secondly, the safety detection module 204 is connected to the optimization module 203; the test suite establishment module 205 is connected to the safety detection module 204;

[0078] The security detection module 204 is used to detect potential security holes in the universal interface and adapter;

[0079] The test suite building module 205 is used to build an automated test suite to ensure that each version of the common interface on different RTOSs is fully tested.

[0080] The security detection module 204 pays special attention to security and compliance issues during implementation and testing, ensuring that there are no potential security vulnerabilities in the general interface and adapters, and complying with RTOS-related compliance standards and regulations, especially in safety-critical applications. The test suite establishment module 205 establishes an automated test suite to ensure that each version of the general interface on different RTOS is fully tested, and integrates automated testing into the continuous integration (CI) system to automatically run tests and generate reports when the code is changed.

[0081] When using the present invention, the demonstration module 201 provides detailed documentation, including instructions for use, API documentation, and sample code, to help users understand how to use and integrate the universal interface, create sample applications, and demonstrate how to use the universal interface on different RTOS. The version update module 202 uses version control tools, such as Git, to track and manage changes to the universal interface, and regularly maintains the universal interface to adapt to new versions or updates of different RTOS. The optimization module 203 optimizes the performance characteristics of different RTOS. For example, in some RTOS, priority inheritance may be a performance key point and requires special treatment. The performance analysis tools provided by the RTOS are used to detect bottlenecks and optimize. The security detection module 204 pays special attention to security and compliance issues in implementation and testing, ensuring that there are no potential security vulnerabilities in the universal interface and adapter, and complying with RTOS-related compliance standards and regulations, especially in safety-critical applications. The test suite establishment module 205 establishes an automated test suite to ensure that each version of the universal interface on different RTOS is fully tested, and integrates automated testing into a continuous integration (CI) system so that tests are automatically run and reports are generated when the code is changed.

[0082] The third embodiment of the present application is:

[0083] Based on the second embodiment, please refer to Figure 5 ,in, Figure 5 It is a schematic diagram of the overall structure of the third embodiment of the present invention.

[0084] The multi-system task scheduling management system provided by the present invention further includes an expansion module 301 , a user training module 302 , a performance tuning module 303 , a periodic review module 304 and a cooperation module 305 .

[0085] For this specific implementation, the extension module 301 is connected to the test suite establishment module 205, and the user training module 302 is connected to the extension module 301;

[0086] The expansion module 301 is used to develop an adapter and comply with the general interface specification when a new RTOS needs to be supported;

[0087] The user training module 302 is used to provide training and support for users.

[0088] When the expansion module 301 needs to support a new RTOS, it develops an adapter and follows the general interface specification, and performs appropriate testing and verification when expanding support for a new RTOS. The user training module 302 provides training and support for users to ensure that they understand how to properly use the general interface packaging management solution, and provides technical support and community support to help users solve problems and share experiences.

[0089] Wherein, the performance tuning module 303, the periodic review module 304 and the cooperation module 305 are connected in sequence;

[0090] The performance tuning module 303 is used to implement a performance monitoring mechanism and perform tuning and optimization according to performance monitoring data to improve system performance;

[0091] The periodic review module 304 is used to periodically review the design and implementation of the general interface encapsulation management solution to identify potential problems and make improvements;

[0092] The cooperation module 305 is used to contribute general interface specifications and adapters to the open source community.

[0093] The performance tuning module 303 implements a performance monitoring mechanism to track task scheduling and resource usage, and performs tuning and optimization based on performance monitoring data to improve system performance. The periodic review module 304 periodically reviews the design and implementation of the general interface encapsulation management solution to identify potential problems and make improvements, collect user feedback, and continuously improve the solution based on user needs and feedback. The cooperation module 305 participates in the RTOS community, cooperates with other developers to jointly solve cross-RTOS task scheduling problems, and contributes general interface specifications and adapters to the open source community for wider promotion and use.

[0094] When using the present invention, the expansion module 301 develops adapters and follows the general interface specifications when it is necessary to support a new RTOS, and appropriate testing and verification should be performed when expanding support for a new RTOS. The user training module 302 provides training and support for users to ensure that they understand how to correctly use the general interface encapsulation management solution, and provides technical support and community support to help users solve problems and share experiences. The performance tuning module 303 implements a performance monitoring mechanism to track task scheduling and resource usage, and performs tuning and optimization based on performance monitoring data to improve system performance. The regular review module 304 regularly reviews the design and implementation of the general interface encapsulation management solution to identify potential problems and make improvements, collect user feedback, and continuously improve the solution based on user needs and feedback. The cooperation module 305 participates in the RTOS community, cooperates with other developers, jointly solves the problem of task scheduling across RTOS, and contributes general interface specifications and adapters to the open source community for wider promotion and use.

[0095] What is disclosed above is only one or more preferred embodiments of the present application, and cannot be used to limit the scope of rights of the present application. Ordinary technicians in this field can understand that all or part of the processes of implementing the above embodiments and equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A multi-system task scheduling management system, characterized in that: It includes specification definition module, adapter creation module, scheduling module, user selection module, error correction module, support module and testing module; The specification definition module, the adapter creation module, the scheduling module, the user selection module, the error correction module, the support module and the test module are connected in sequence; The specification definition module is used to define a general interface specification; The adapter creation module is used to create an adapter for each target RTOS to implement the general interface specification; The scheduling module is used to call the adapter method to perform corresponding operations in the implementation of the general interface; The user selection module is used to allow the user to select the RTOS to be used during runtime and load the corresponding RTOS adapter according to the user's selection; The error correction module is used to implement an error handling mechanism in the encapsulation layer and the adapter to handle possible RTOS-specific errors or abnormal conditions; The support modules are used to handle platform-specific issues and differences using conditional compilation or cross-platform libraries; The test module is used to perform comprehensive testing and verification on different RTOS to ensure that the common interface can work properly in various situations; The error correction module includes an error processing unit and a debugging unit; the error processing unit is connected to the user selection module, and the debugging unit is connected to the error processing unit; The error handling unit is used to provide error codes and error information of the RTOS in the encapsulation layer and the adapter; The debugging unit is used to help users debug task scheduling and RTOS adapter; The test module includes a task creation test unit and a task suspension test unit; the task suspension test unit is connected to the task creation test unit; The task creation test unit is used to test the task creation function of different RTOS under the universal interface; The task suspension test unit is used to test the task suspension function of different RTOS under a universal interface; The test module further includes a task recovery test unit; the task recovery test unit is connected to the task suspension test unit; The task recovery test unit is used for task recovery functions of different RTOS under a universal interface; The test module further includes a timer test unit; the timer test unit is connected to the task recovery test unit; The timer test unit is used to test the timer functions of different RTOS under the universal interface; The multi-system task scheduling management system further includes a demonstration module; the demonstration module is connected to the timer test unit; The demo module is used to create sample applications that demonstrate how to use the common interfaces on different RTOSs.

2. A multi-system task scheduling management system according to claim 1, characterized in that: The multi-system task scheduling and management system further includes a version update module and an optimization module; the version update module is connected to the demonstration module, and the optimization module is connected to the version update module; The version update module is used to track and manage changes to the general interface and regularly maintain the general interface; The optimization module is used to optimize the performance characteristics of different RTOS.

3. A multi-system task scheduling management system as claimed in claim 2, characterized in that: The multi-system task scheduling and management system further comprises a safety detection module and a test suite establishment module; the safety detection module is connected to the optimization module; the test suite establishment module is connected to the safety detection module; The security detection module is used to detect potential security holes in the universal interface and adapter; The test suite building module is used to build an automated test suite to ensure that each version of the common interface on different RTOSs is fully tested.

Citation Information

Patent Citations

  • Application program running method and device, electronic equipment and storage medium

    CN111880863A

  • General remote communication calling architecture and method

    CN113867988A

  • Automatic testing method and system for embedded RTOS, terminal and storage medium

    CN115576835A

  • Real-time operating system generation method and device, real-time operating system use method and device, electronic equipment and medium

    CN115826938A

  • Systems and methods with integrated gaming engines and smart contracts

    US20230173395A1