Enterprise software operation management system and method under domestic operating system
By adopting Vue, Electron, Node.js, C# and .NET Core technologies under the domestic operating system, combining process isolation and pipeline communication, the problems of software migration and hardware adaptation during the domestic operation process are solved, and the stability and sustainable iteration of the system are achieved.
Patent Information
- Application Number
- CN202510429714.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-08
- Publication Date
- 2025-07-25
AI Technical Summary
In the process of domestic substitution, the existing technology lacks a unified migration method, which leads to each application manufacturer requiring complex re-docking and development for each operating system and hardware. The problem of secondary development interface synchronization when the software version is updated has not been effectively solved, affecting the stability of the software operation.
The Vue framework is used to develop the business logic layer, the Electron framework is used as the rendering container, Node.js and HTTP calls realize the hardware service layer, and the C# and .NET Core development main modules, combining process isolation and pipeline communication, abstract operating system-level interfaces, and providing version management modules to ensure system stability and sustainable iteration.
It improves the operation stability and adaptability of the software, supports the continuous iteration of the system, simplifies development and maintenance, reduces operation and maintenance costs, and enhances the compatibility and portability of the system.
Smart Images

Figure CN120371385A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of domestic operating systems, and particularly relates to an enterprise software operation management system and method under a domestic operating system. Background Art
[0002] With the increasing demand for safe and reliable domestic substitution solutions in the country, many industries have basically completed the replacement of domestic hardware and operating systems. However, this process has also brought a series of challenges. For the original service terminals, service desks, queuing machines programs, etc., due to the lack of a unified migration method, each application manufacturer needs to re-dock and develop for each operating system, hardware, and external device, which is undoubtedly a heavy and complex task.
[0003] In addition, some WEB application systems using peripheral OCX controls also face migration and adaptation problems. During the migration process, not only the compatibility of the software itself needs to be concerned, but also the stability and timeliness of the secondary development interface need to be ensured. For example, when the software version is updated, the corresponding secondary development interface file also needs to be updated synchronously to ensure the smooth docking of the old and new versions. Otherwise, problems such as abnormal software operation and crashing may occur, affecting the normal progress of government services.
[0004] Therefore, in the process of promoting the domestic substitution solution, it is necessary to fully consider the compatibility and adaptability of various software and hardware, formulate a scientific and reasonable migration plan, and strengthen the cooperation and communication with each application manufacturer to jointly promote the digital transformation and upgrading of services.
[0005] In order to solve the software upgrade and hardware adaptation problems faced by various industries during the domestic substitution process, the present invention proposes an enterprise software operation management system and method under a domestic operating system. Summary of the Invention
[0006] The present invention provides a simple and efficient enterprise software operation management system and method under a domestic operating system to make up for the deficiencies of the existing technology.
[0007] The present invention is realized through the following technical solutions:
[0008] An enterprise software operation management system under a domestic operating system, characterized by comprising:
[0009] A business logic layer, developed using the Vue framework, is used to process business rules and logics, and is the core part for realizing software functions and business rules, which can meet the requirements for rapid iteration and upgrade of software during the domestic substitution process;
[0010] A business presentation layer, used to display the data and functions of the business logic layer in the form of a user interface.
[0011] The business presentation layer uses the Electron framework as the presentation container, avoiding complex compilation steps. Developers can directly use web technologies for development, making the development process more intuitive and efficient.
[0012] The hardware service layer is used to uniformly provide external hardware and system interfaces, and ensure the stable operation of the main framework through process pipeline communication, realizing access to and control of underlying hardware functions.
[0013] The process pipeline communication method refers to first establishing a communication pipeline from the hardware service layer to the main module, then transmitting data and control signals through the communication pipeline, and simultaneously monitoring the status of the communication pipeline to ensure the stability and reliability of data transmission.
[0014] The hardware service layer uses two different methods, namely Node.js export and standard HTTP calls, to implement hardware calls.
[0015] The main module is a core component developed using C# and.NET Core. Leveraging the cross-platform capabilities of.NET Core, it supports running on various domestic operating systems and different CPU architectures, and is used to coordinate and manage the key functions of the entire system, including version management, process isolation, pipeline communication, and operating system-level interface abstraction, to ensure the wide compatibility and flexibility of the system.
[0016] Through communication with the version management module, the main module ensures that the versions of the overall framework and various external drivers can be updated in a timely manner, thereby guaranteeing the stability and security of the system. At the same time, it also supports the continuous iteration and improvement of the system.
[0017] To improve the stability of the system, the main module uses process isolation technology to run external driver programs. Even if a certain driver program has problems, it will not affect the operation of the main module or other system components.
[0018] The main module establishes a pipeline communication mechanism, opening up a data exchange channel between the hardware service layer and the external driver process, allowing for fast and reliable data transmission between the hardware service layer and the driver program.
[0019] The main module is also responsible for abstracting operating system-level interfaces, providing necessary system-level function support for the business logic layer, enabling the business logic layer to be unaware of the specific implementation of the underlying operating system, thus simplifying the development work and improving the portability of the code.
[0020] The version management module is used to provide WEB background management functions, supporting the release, query, and update of the main framework program and various versions of external drivers.
[0021] The WEB background management functions provided by the version management module include:
[0022] A user interface that allows administrators to log in and navigate;
[0023] The function of releasing new versions, which allows administrators to upload and deploy new versions of software packages;
[0024] The implementation of the query function, which allows administrators to view the currently installed software version and historical version records;
[0025] The implementation of the update function, which allows administrators to trigger software updates or set automatic update policies.
[0026] A method for managing the operation of enterprise software under a domestic operating system, including the following steps:
[0027] Step S1, Main module development
[0028] Develop the main module using C# and.NET Core to ensure that the system can run on domestic operating systems and various CPUs; the cross-platform characteristics of.NET Core enable the main module to adapt to different hardware and software environments;
[0029] Step S2, External driver startup and communication protocol
[0030] Formulate the startup method of the external driver and the data protocol for pipe communication, and define the communication format and control commands between the driver service process and the main module to ensure the accuracy and reliability of hardware calls;
[0031] Step S3, Peripheral driver development
[0032] According to the defined protocol, customize and complete the development of peripheral drivers under different Linux versions and CPU architectures, including writing and testing driver programs for different hardware platforms to ensure that the driver programs can cooperate seamlessly with the main module;
[0033] Step S4, Communication between the hardware service layer and the external driver
[0034] When the hardware service layer receives a request, the main module starts the external driver service process and opens the pipe communication mechanism. The main module communicates with the external driver process to complete hardware calls;
[0035] Step S5, WEB background management system development
[0036] Develop a WEB background management system to support the release, query, and update of the main framework program and various versions of external drivers; the version information includes the running Linux version and CPU architecture for easy management and maintenance;
[0037] Step S6, Version Information Query and Update:
[0038] When the client starts, the main module communicates with the version management module, queries the version information according to the running Linux version and CPU architecture, and compares the files according to the version used by the specified machine in the WEB; by default, the latest released version is used. If it is found that the files are different, the download and update process is started.
[0039] Step S7, Business System Page Loading:
[0040] The main module opens the Electron process and loads the configured business system page; Electron, as the container of the business presentation layer, allows the construction of cross-platform desktop applications using web technologies and provides a user interface.
[0041] An enterprise software operation management device under a domestic operating system, characterized in that it includes a memory and a processor; the memory is used to store computer programs, and the processor is used to implement the above method steps when executing the computer programs.
[0042] A readable storage medium, characterized in that a computer program is stored on the readable storage medium, and the computer program implements the above method steps when executed by a processor.
[0043] The beneficial effects of the present invention are: the enterprise software operation management system and method under the domestic operating system not only significantly enhance the operation stability of the software, improve the adaptability of the software to various changing systems and external environments, but also ensure the sustainable iteration of the system, providing strong support for the diversification of business. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0045] Attached Figure 1 It is a schematic diagram of the architecture of the enterprise software operation management system under the domestic operating system of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0046] To enable those skilled in the art to better understand the technical solutions in the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
[0047] The enterprise software operation management system under this domestic operating system includes:
[0048] The business logic layer is developed using the Vue framework and is used to process business rules and logics. It is the core part for implementing software functions and business rules.
[0049] Vue is a progressive JavaScript framework designed specifically for building user interfaces. By adopting the Vue framework, the business logic layer can achieve efficient, flexible, and user-friendly software development, meeting the requirements for rapid iteration and upgrade of software during the localization process.
[0050] The business presentation layer is used to present the data and functions of the business logic layer in the form of a user interface.
[0051] The business presentation layer uses the Electron framework as the presentation container. Electron is a framework for building cross-platform desktop applications using web technologies (HTML, CSS, and JavaScript). Compared with traditional desktop application development frameworks such as Qt and GTK, Electron avoids complex compilation steps. Developers can directly use web technologies for development, making the development process more intuitive and efficient. By adopting the Electron framework, the business presentation layer can achieve fast, flexible, and cross-platform user interface development, providing strong support for the rapid iteration and efficient delivery of domestic software. At the same time, these characteristics of Electron also enable the application to better adapt to the changing business requirements and technical environment.
[0052] The hardware service layer is used to uniformly provide external hardware and system interfaces, and ensure the stable operation of the main framework through the process pipeline communication method, realizing access to and control of underlying hardware functions.
[0053] The process pipeline communication method refers to first establishing a communication pipeline from the hardware service layer to the main module, then transmitting data and control signals through the communication pipeline, and simultaneously monitoring the status of the communication pipeline to ensure the stability and reliability of data transmission.
[0054] The hardware service layer uses two different methods, namely Node.js export and standard HTTP calls, to implement hardware calls.
[0055] Node.js allows developers to directly export functions or objects, which simplifies the interaction between business code and the hardware service layer because developers do not need to deal with the details of network communication;
[0056] HTTP is a widely used network protocol. Calling the hardware service layer through HTTP can ensure the universality and cross-platform compatibility of hardware services. By combining Node.js export methods and HTTP standard calls, the hardware service layer can meet different scenarios and provide a powerful and flexible hardware operation platform for the upper-level business logic.
[0057] The main module is a core component developed using C# and .NET Core. It uses the cross-platform capabilities of .NET Core to support running on various domestic operating systems and different CPU architectures. It is used to coordinate and manage key functions of the entire system, including version management, process isolation, pipeline communication, and operating system-level interface abstraction to ensure the wide compatibility and flexibility of the system.
[0058] The main module communicates with the version management module to ensure that the overall framework and the versions of various external drivers can be updated in a timely manner, thereby ensuring the stability and security of the system, while also supporting the continuous iteration and improvement of the system;
[0059] In order to improve the stability of the system, the main module uses process isolation technology to run external drivers. Even if a driver has a problem, it will not affect the operation of the main module or other system components; this isolation mechanism enhances the robustness of the system.
[0060] The main module establishes a pipeline communication mechanism to open up a data exchange channel between the hardware service layer and the external driver process. This efficient communication method allows fast and reliable data transmission between the hardware service layer and the driver.
[0061] The main module is also responsible for abstracting the operating system level interface and providing the necessary system level functional support for the business logic layer; this abstraction makes the business logic layer not need to care about the specific implementation of the underlying operating system, thereby simplifying the development work and improving the portability of the code.
[0062] Through the above functions and designs, the main module plays a vital role in the system architecture of the present invention. It not only ensures the stability and security of the system, but also provides strong support for the business logic layer, so that the entire system can run efficiently and stably. In addition, the cross-platform characteristics of .NET Core also enable the main module to easily adapt to different domestic hardware and operating system environments, providing important support for the development of domestic information systems.
[0063] A version management module, which is used to provide WEB background management functions and support the release, query, and update of the main framework program and external drivers of each version.
[0064] The WEB background management functions provided by the version management module include:
[0065] A user interface that allows administrators to log in and navigate;
[0066] The function of releasing a new version, which allows administrators to upload and deploy new version software packages;
[0067] The implementation of the query function, which allows administrators to view the currently installed software version and historical version records;
[0068] The implementation of the update function, which allows administrators to trigger software updates or set automatic update policies.
[0069] The enterprise software operation management method under this domestic operating system includes the following steps:
[0070] Step S1, Main module development
[0071] Develop the main module using C# and.NET Core to ensure that the system can run on domestic operating systems and various CPUs; the cross-platform feature of.NET Core enables the main module to adapt to different hardware and software environments;
[0072] Step S2, External driver startup and communication protocol
[0073] Formulate the startup method of the external driver and the data protocol for pipeline communication, and define the communication format and control commands between the driver service process and the main module to ensure the accuracy and reliability of hardware calls;
[0074] Step S3, Peripheral driver development
[0075] According to the defined protocol, customize and complete the development of peripheral drivers under different Linux versions and CPU architectures, including writing and testing driver programs for different hardware platforms to ensure that the driver programs can cooperate seamlessly with the main module;
[0076] Step S4, Communication between the hardware service layer and the external driver
[0077] When the hardware service layer receives a request, the main module starts the external driver service process and opens the pipeline communication mechanism, and the main module communicates with the external driver process to complete hardware calls;
[0078] Step S5, WEB background management system development
[0079] Develop a WEB background management system to support the release, query, and update of the main framework program and external drivers of each version; the version information includes the running Linux version and CPU architecture for easy management and maintenance;
[0080] Step S6: Version Information Query and Update:
[0081] When the client starts, the main module communicates with the version management module, queries the version information according to the running Linux version and CPU architecture, and compares files according to the version used by the specified machine in the WEB; by default, the latest released version is used. If the files are found to be different, the download and update process is started;
[0082] Step S7: Business System Page Loading:
[0083] The main module opens the Electron process and loads the configured business system page; Electron, as the container of the business presentation layer, allows the use of Web technologies to build cross-platform desktop applications, providing a rich user interface.
[0084] The enterprise software operation management device under this domestic operating system is characterized in that it includes a memory and a processor; the memory is used to store computer programs, and the processor is used to implement the above method steps when executing the computer programs.
[0085] The readable storage medium is characterized in that a computer program is stored on the readable storage medium, and the computer program implements the above method steps when executed by a processor.
[0086] Compared with the prior art, the enterprise software operation management system and method under this domestic operating system have the following characteristics:
[0087] First, improve compatibility and portability:
[0088] By using.NET Core and C# as the development languages, the system architecture of the present invention can support running on various domestic operating systems and different CPU architectures, improving the compatibility and portability of the system. Domestic chips such as Zhaoxin (X86), Loongson (Loong64), Huawei (ARM), and Feiteng (ARM) and self-developed operating systems based on Linux are adopted.
[0089] Second, enhance the stability and security of the system:
[0090] By adopting process isolation technology and version management mechanism, the present invention ensures the stable operation of the external driver, and through the version control and rollback mechanism, improves the security and reliability of the system.
[0091] Third, it simplifies development and maintenance:
[0092] By abstracting the operating system-level interfaces and providing a WEB background management, the present invention simplifies the development work of the business logic layer, and at the same time makes the system maintenance and version update more convenient.
[0093] Fourth, it improves the scalability and flexibility of the system:
[0094] The layered design and modularization of the system architecture make it easier to add, modify, or replace hardware services, and at the same time facilitate management and maintenance.
[0095] Fifth, it supports rapid iteration and continuous integration:
[0096] The version management module supports automated version release and update, enabling the system to quickly respond to changes in business requirements and supporting the software development practices of continuous integration and continuous deployment.
[0097] Sixth, it improves the user experience:
[0098] Through the optimized design of the business logic layer and the business presentation layer, the present invention provides a more fluent and intuitive user interface, improving the user experience.
[0099] Seventh, it reduces the operation and maintenance costs:
[0100] Through cross-platform and modular design, the present invention reduces the costs of developing and maintaining multiple versions for different platforms.
[0101] Eighth, it supports localization:
[0102] The system architecture and implementation technology of the present invention fully support localization and meet the requirements of the localization replacement solution.
[0103] The above-described embodiments are only one of the specific implementation manners of the present invention, and the ordinary changes and replacements made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.
Claims
1. An enterprise software operation management system under a domestic operating system, characterized in that: include: The business logic layer is developed using the Vue framework and is used to process business rules and logic. It is the core part of realizing software functions and business rules and can meet the needs of rapid software iteration and upgrading during the localization process. The business presentation layer is used to present the data and functions of the business logic layer in the form of a user interface; The hardware service layer is used to provide hardware and system interfaces to the outside world in a unified manner, and to ensure the stable operation of the main framework through process pipeline communication, thereby achieving access to and control of the underlying hardware functions; The main module is a core component developed using C# and .NET Core. It uses the cross-platform capabilities of .NET Core to support running on various domestic operating systems and different CPU architectures. It is used to coordinate and manage key functions of the entire system, including version management, process isolation, pipeline communication, and operating system-level interface abstraction; The version management module is used to provide WEB background management functions and support the release, query and update of the main framework program and various versions of external drivers.
2. The enterprise software operation management system under the domestic operating system according to claim 1, wherein: The business presentation layer uses the Electron framework as a presentation container. Developers directly use Web technology for development, avoiding complex compilation steps, making the development process more intuitive and efficient.
3. The enterprise software operation management system under the domestic operating system according to claim 1, characterized in that: The process pipeline communication method refers to first establishing a communication pipeline from the hardware service layer to the main module, then transmitting data and control signals through the communication pipeline, and monitoring the status of the communication pipeline to ensure the stability and reliability of data transmission.
4. The enterprise software operation management system under the domestic operating system according to claim 1, characterized in that: The hardware service layer uses two different methods: Node.js export and standard HTTP call to implement hardware calls.
5. The enterprise software operation management system under the domestic operating system according to claim 1, characterized in that: The main module communicates with the version management module to ensure that the overall framework and the versions of various external drivers can be updated in a timely manner, thereby ensuring the stability and security of the system, while also supporting the continuous iteration and improvement of the system; In order to improve the stability of the system, the main module uses process isolation technology to run the external driver. Even if a driver has a problem, it will not affect the operation of the main module or other system components. The main module establishes a pipeline communication mechanism to open up a data exchange channel between the hardware service layer and the external driver process, allowing fast and reliable data transmission between the hardware service layer and the driver; The main module is also responsible for abstracting the operating system level interface and providing necessary system level functional support for the business logic layer, so that the business logic layer does not need to care about the specific implementation of the underlying operating system, thereby simplifying the development work and improving the portability of the code.
6. The enterprise software operation management system under the domestic operating system according to claim 1, characterized in that: The WEB background management functions provided by the version management module include: A user interface that allows administrators to log in and navigate; Release new version function, allowing administrators to upload and deploy new versions of software packages; The query function allows administrators to view the currently installed software version and historical version records; Implementation of update functionality, allowing administrators to trigger software updates or set up automatic update policies.
7. A method for managing the operation of enterprise software under a domestic operating system, characterized in that: The following steps are involved: Step S1: Main module development Develop the main module using C# and.NET Core to ensure that the system can run on domestic operating systems and various CPUs; the cross-platform feature of.NET Core enables the main module to adapt to different hardware and software environments; Step S2: External driver startup and communication protocol Formulate the startup method of the external driver and the data protocol for pipe communication, and define the communication format and control commands between the driver service process and the main module to ensure the accuracy and reliability of hardware calls; Step S3: Peripheral driver development According to the defined protocol, customize and complete the development of peripheral drivers under different Linux versions and CPU architectures, including writing and testing driver programs for different hardware platforms to ensure that the driver programs can cooperate seamlessly with the main module; Step S4: Communication between the hardware service layer and the external driver When the hardware service layer receives a request, the main module starts the external driver service process and opens the pipe communication mechanism, and the main module communicates with the external driver process to complete hardware calls; Step S5: Development of the WEB background management system Develop a WEB background management system to support the release, query, and update of the main framework program and external drivers of each version; the version information includes the running Linux version and CPU architecture for easy management and maintenance; Step S6: Version information query and update: When the main module starts at the client, it communicates with the version management module, queries the version information according to the running Linux version and CPU architecture, and compares the files according to the version used by the specified machine in the WEB; by default, the latest released version is used, and if the files are found to be different, the download and update process is started; Step S7: Loading of the business system page The main module opens the Electron process and loads the configured business system page; Electron, as a container for the business presentation layer, allows the construction of cross-platform desktop applications using Web technologies to provide a user interface.
8. An enterprise software operation management device under a domestic operating system, characterized in that: It includes a memory and a processor; the memory is used to store computer programs, and the processor is used to implement the method steps as described in claim 7 when executing the computer programs.
9. A readable storage medium, characterized in that: A computer program is stored on the readable storage medium, and when the computer program is executed by the processor, it implements the method steps as described in claim 7.