CN115567361B - Cross-platform bottom layer software system, application method, equipment and storage medium - Google Patents

Cross-platform bottom layer software system, application method, equipment and storage medium Download PDF

Info

Publication number
CN115567361B
CN115567361B CN202211381262.8A CN202211381262A CN115567361B CN 115567361 B CN115567361 B CN 115567361B CN 202211381262 A CN202211381262 A CN 202211381262A CN 115567361 B CN115567361 B CN 115567361B
Authority
CN
China
Prior art keywords
technical framework
module
platform
control logic
task
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202211381262.8A
Other languages
Chinese (zh)
Other versions
CN115567361A (en
Inventor
王广安
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zhixiang Technology Co Ltd
Original Assignee
Beijing Zhixiang Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zhixiang Technology Co Ltd filed Critical Beijing Zhixiang Technology Co Ltd
Priority to CN202211381262.8A priority Critical patent/CN115567361B/en
Publication of CN115567361A publication Critical patent/CN115567361A/en
Application granted granted Critical
Publication of CN115567361B publication Critical patent/CN115567361B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0246Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/044Network management architectures or arrangements comprising hierarchical management structures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

The application provides a cross-platform bottom layer software system, an application method and equipment, and relates to the technical field of computers. The cross-platform bottom software system comprises a control logic module, a technical framework interface and a plurality of technical framework modules which are connected with the control logic module through the technical framework interface and used for executing tasks of the same type, wherein different technical framework modules correspond to different system platforms; the control logic module is used for determining a task to be executed and sending the task to be executed to the technical framework module through the technical framework interface; and the technical framework module is used for executing the operation related to the system platform corresponding to the technical framework module according to the task to be executed. Because the control logic module is irrelevant to the system platform, the same control logic module is directly deployed in each system platform without repeated development, and the workload of software cross-platform transplantation is effectively reduced.

Description

Cross-platform underlying software system, application method, equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a cross-platform underlying software system, an application method, a device, and a storage medium.
Background
Software related to the control of the bottom layer of the system is generally in a layered structure and is generally divided into a presentation layer, a logic layer and a kernel layer. The presentation layer realizes the interaction with the user, the logic layer realizes the service logic of the software, and the kernel layer executes the specific control operation.
Such software related to system-level control is generally only applicable to a specific platform, and because of large differences among platforms, the software related to system-level control cannot run across platforms. If software controlled by a system bottom layer is transplanted from one platform to another platform, a targeted set of components needs to be re-developed according to the platform to be transplanted, which causes a large workload of software cross-platform transplantation for the software controlled by the system bottom layer with large software scale and high complexity.
Disclosure of Invention
The application provides a cross-platform bottom layer software system, an application method, equipment and a storage medium, which are used for solving the problem of large workload of the existing software cross-platform transplantation.
In a first aspect, the present application provides a cross-platform underlying software system, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface, where the technical framework modules are used to execute tasks of the same type, and different technical framework modules correspond to different system platforms;
the control logic module is used for determining a task to be executed and sending the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module is used for executing the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In one possible embodiment, the cross-platform underlying software system further comprises a control logic interface;
the technical framework module is used for sending an event to the control logic module through the control logic interface;
the control logic module is specifically configured to determine the task to be executed according to the event.
In a possible implementation manner, the technical framework module is configured to invoke a corresponding system function to execute an operation related to a system platform corresponding to the technical framework module according to the task to be executed.
In a possible implementation manner, the number of the technology framework interfaces is multiple, and the technology framework modules corresponding to different technology framework interfaces are used for executing different types of tasks.
In a possible implementation, the technical framework module is further configured to send the operation result to the control logic module;
and the control logic module is also used for executing corresponding control operation based on the operation result.
In one possible embodiment, the cross-platform underlying software system further comprises a module control interface;
the control logic module is also used for controlling the technical framework module to start or stop running through the module control interface.
In one possible implementation, the cross-platform underlying software system is deployed in at least one of a presentation layer, a logic layer, or a kernel layer in the system platform.
In a second aspect, the present application provides an application method for a cross-platform based underlying software system, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface and used for executing tasks of the same type, and different technical framework modules correspond to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In one possible embodiment, the control logic module determines that a task is to be performed, including:
the technical framework module sends an event to the control logic module through the control logic interface;
and the control logic module determines the task to be executed according to the event.
In a possible implementation, the technical framework module performs operations related to the system platform according to the task to be executed, and the operations include:
and the technical framework module calls corresponding system functions to execute the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In a possible implementation manner, the number of the technology framework interfaces is multiple, and the technology framework modules corresponding to different technology framework interfaces are used for executing different types of tasks.
In one possible embodiment, the method further comprises:
the technical framework module sends an operation result to the control logic module;
and the control logic module executes corresponding control operation based on the operation result.
In one possible embodiment, the cross-platform underlying software system further comprises a module control interface; the method further comprises the following steps:
and the control logic module controls the technical framework module to start or stop running through the module control interface.
In one possible implementation, the cross-platform underlying software system is deployed in at least one of a presentation layer, a logic layer, or a kernel layer in the system platform.
In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements an application method based on a cross-platform underlying software system when executing the program, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface and used for executing tasks of the same type, and different technical framework modules correspond to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In a fourth aspect, the present application provides a non-transitory computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing an application method based on a cross-platform underlying software system, the cross-platform underlying software system including a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface for performing tasks of the same type, different technical framework modules corresponding to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
The cross-platform bottom software system provided by the embodiment of the application comprises a control logic module, a technical framework interface and a plurality of technical framework modules which are connected with the control logic module through the technical framework interface and are used for executing tasks of the same type, wherein different technical framework modules correspond to different system platforms; the control logic module is used for determining a task to be executed and sending the task to be executed to the technical framework module through the technical framework interface; the technical framework module is used for executing the operation related to the system platform according to the task to be executed. According to the scheme of the embodiment of the application, aiming at cross-platform software application, a software hierarchy is divided into a control logic module and a technical framework module, the control logic module realizes software internal logic irrelevant to a system platform, and the technical framework module is used for realizing specific operation relevant to the system platform corresponding to the technical framework module. Because the bottom software system of the cross-platform comprises the computing frame modules corresponding to different system platforms, the control logic module can control the corresponding technical frame module to execute the operation related to the system platform through the technical frame interface, and the application of the software on different system platforms is realized. And because the control logic module is irrelevant to the system platform, the same control logic module is directly deployed in each system platform without repeated development, and the workload of software cross-platform transplantation is effectively reduced.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a first schematic structural diagram of a cross-platform underlying software system according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram ii of a cross-platform underlying software system according to an embodiment of the present application;
fig. 3 is a schematic diagram of a technical framework module and a technical framework interface provided in an embodiment of the present application;
fig. 4 is a schematic diagram of a network transmission management control kernel driver system according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating an application method of the cross-platform based underlying software system according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
Software related to the control of the bottom layer of the system is generally in a layered structure and is generally divided into a presentation layer, a logic layer and a kernel layer. The presentation layer realizes interaction with a user; the logic layer realizes the service logic of the software; the kernel layer performs specific control operations.
For cross-platform software, it is difficult to port software components from one platform to another because of the large differences between platforms. Even with the migration of software components, it is often necessary to develop a complete set of components containing various levels for each platform. Currently some development tools such as the application development framework (QT) can support cross-platform development, but are limited to a presentation layer and a small number of logical layers, the kernel layer not being portable across platforms.
In the prior art, a large amount of repeated development exists in the aspect of cross-platform software, the software is large in scale and high in complexity, and development and maintenance are not easy. On the other hand, the control component at the bottom layer of the system is not easy to debug, and the system is often required to be restarted when problems occur, so that the development efficiency is seriously influenced.
Based on this, the embodiment of the present application provides a cross-platform bottom layer software system, which separates the logic part of software, especially the kernel layer logic, from the control operation of the software, implements cross-platform application of the software, and reduces the repeated development in the aspect of cross-platform software.
The scheme of the embodiment of the present application will be described first with reference to fig. 1.
Fig. 1 is a schematic structural diagram of a cross-platform underlying software system provided in an embodiment of the present application, as shown in fig. 1, the cross-platform underlying software system includes a control logic module 11, a technical framework interface 12, and a plurality of technical framework modules connected to the control logic module 11 through the technical framework interface 12 and used for executing tasks of the same type, where different technical framework modules correspond to different system platforms, and only one technical framework module 13 is described as an example in fig. 1.
The control logic module 11 is configured to determine a task to be executed, and send the task to be executed to the technical framework module 13 through the technical framework interface 12;
and the technical framework module 13 is configured to execute, according to the task to be executed, an operation related to the system platform corresponding to the technical framework module 13.
As shown in fig. 1, for any hierarchy within the software, the hierarchy can be divided into two types of modules, a technical framework and control logic.
The technical framework module 13 includes basic elements for implementing a certain type of functions, and performs a certain type of specific operations related to a software execution environment, such as system control, storage device management, network communication, and the like. Optionally, according to the overall functional requirements of the software, the same layer may include a plurality of technical framework modules, which respectively execute different types of operations. Optionally, the technology framework interface 12 is an interface belonging to the technology framework module 13.
The control logic module 11 implements software internal logic irrelevant to the operating environment, the data structure of the control logic module is designed based on general data types in a combined manner, and the unified technical framework interface 12 is called to execute operations relevant to the operating environment without directly calling system functions, so that the control logic module can be operated on any platform and any hierarchy, the same control logic module 11 is directly deployed in each system platform, and repeated development is not needed. For the control logic module 11 of the kernel layer, it can be combined with the presentation layer module for testing without the kernel layer technical framework, thereby reducing the tests of the kernel layer and improving the development efficiency.
For any level in the software, after dividing the level into the technical framework module 13 and the control logic module 11, the control logic module 11 determines the task to be executed, and sends the task to be executed to the technical framework module 13 through the technical framework interface 12. Since the control logic module 11 is used for implementing software internal logic independent of the operating environment, one control logic module 11 can be used for different system platforms. The control logic module 11 controls the corresponding technical framework module 13 through the technical framework interface 12 according to the system platform corresponding to the software. After receiving the task to be executed, the technical framework module 13 may execute the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
It should be noted that, in the embodiment of the present application, one or more technical framework interfaces may be included in the cross-platform underlying software system. For any technical framework interface, the control logic module can be connected with a plurality of technical framework modules through the technical framework interface, and the technical framework modules correspond to different system platforms and are used for executing tasks of the same type.
The cross-platform bottom software system provided by the embodiment of the application comprises a control logic module, a technical framework interface and a plurality of technical framework modules connected with the control logic module through the technical framework interface, wherein different technical framework modules correspond to different system platforms; the control logic module is used for determining a task to be executed and sending the task to be executed to the technical framework module through the technical framework interface; the technical framework module is used for executing the operation related to the system platform according to the task to be executed. According to the scheme of the embodiment of the application, aiming at cross-platform software application, the software hierarchy is divided into the control logic module and the technical framework module, the control logic module realizes software internal logic irrelevant to the system platform, and the technical framework module is used for realizing specific operation relevant to the system platform. Because the bottom software system of the cross-platform comprises the computing frame modules corresponding to different system platforms, the control logic module can control the corresponding technical frame module to execute the operation related to the system platform through the technical frame interface, and the application of the software on different system platforms is realized. And because the control logic module is irrelevant to the system platform, the same control logic module is directly deployed in each system platform without repeated development, and the workload of software cross-platform transplantation is effectively reduced.
On the basis of any of the above embodiments, the following further describes aspects of the embodiments of the present application with reference to the drawings.
Fig. 2 is a structural schematic diagram of a cross-platform underlying software system according to an embodiment of the present application, and as shown in fig. 2, the cross-platform underlying software system includes a control logic module 11, a technical framework interface 12, and a plurality of technical framework modules connected to the control logic module through the technical framework interface 12, where different technical framework modules correspond to different system platforms, and only one technical framework module 13 is described as an example in fig. 2. Further, the cross-platform bottom software system further includes a control logic interface 21, and optionally, the control logic interface 21 is an interface belonging to the control logic module 11. The control logic interface 21 is defined according to the functional needs of the software for other modules of the software to call.
The control logic module 11 sends the task to be executed to the technical framework module 13 through the technical framework interface 12, so as to control the technical framework module 13 to execute the operation related to the system platform according to the task to be executed.
In one possible implementation, the control logic module 11 autonomously determines the task to be executed according to internal logic and sends the task to be executed to the technical framework module 13 via the technical framework interface 12. That is, the action of the control logic module 11 sending the technical framework module 13 to perform the task is autonomously triggered by the control logic module 11.
In another possible implementation, the technical framework module 13 sends the event to the control logic module 11 via the control logic interface 21. After receiving the event, the control logic module 11 determines the task to be executed according to the event, and sends the task to be executed to the technical framework module 13 through the technical framework interface 12. That is, the action of the control logic module 11 sending the technical framework module 13 the task to be performed is triggered by the technical framework module 13.
The control logic module 11 performs specific operations and controls by calling the unified technical framework interface 12 without considering a specific operation environment (i.e., a system platform); the technical framework module 13 calls the control logic interface 21 to send an event to the control logic module 11, and performs corresponding processing according to a return result of the control logic module 11. After receiving the task to be executed, the technical framework module 13 calls a corresponding system function to execute an operation related to the system platform according to the task to be executed.
Further, as shown in fig. 2, the cross-platform underlying software system further includes a module control interface 22, and the control logic module 11 may also control the technology framework module 13 to start or stop running through the module control interface 22, that is, the control logic module 11 may control the technology framework module 13 to start or stop running through the module control interface 22, that is, the technology framework module 13 is controlled to start or stop running.
According to the requirements of software running environments, corresponding technical framework modules are deployed in each running environment (namely different system platforms), the system is designed according to the specific requirements of the running environments, the technical framework modules executing the same operation in various running environments respectively realize a group of uniform technical framework interfaces, and the uniform technical framework interfaces are defined according to the functional requirements of the software and are called by other modules of the software. The technical framework modules corresponding to the technical framework modules for executing the tasks of the same type have the same technical framework interface, and the technical framework modules corresponding to the technical framework modules of different types are used for executing the tasks of different types.
As may be appreciated, for example, in conjunction with fig. 3. Fig. 3 is a schematic diagram corresponding to the technical framework module and the technical framework interface provided in the embodiment of the present application, and as shown in fig. 3, the cross-platform underlying software system includes a technical framework module A1, a technical framework module A2, a technical framework module B1, and a technical framework module B2, where the technical framework module A1 and the technical framework module A2 are used to execute an operation a, and the technical framework module B1 and the technical framework module B2 are used to execute an operation B.
In the example of fig. 3, the cross-platform underlying software system includes a technical framework module A1 applicable to the first platform and a technical framework module A2 applicable to the second platform, where the technical framework module A1 applicable to the first platform is used to perform the a operation on the first platform, and the technical framework module A2 applicable to the second platform is used to perform the a operation on the second platform.
Although the first platform and the second platform are different system platforms, since the technical framework module A1 applicable to the first platform and the technical framework module A2 applicable to the second platform both perform the same kind of operation (i.e., a operation), the technical framework module A1 applicable to the first platform and the technical framework module A2 applicable to the second platform both implement the same technical framework interface, i.e., interface X in fig. 3.
The control logic module determines a task to be executed and sends the task to be executed to the technical framework module A1 or the technical framework module A2 through the interface X. The technical framework module A1 suitable for the first platform can execute the operation A related to the first platform according to the task to be executed; the technical framework module A2 suitable for the second platform can execute the operation A related to the second platform according to the task to be executed.
The cross-platform bottom software system further comprises a technical framework module B1 suitable for the first platform and a technical framework module B2 suitable for the second platform, wherein the technical framework module B1 suitable for the first platform is used for executing the operation B on the first platform, and the technical framework module B2 suitable for the second platform is used for executing the operation B on the second platform.
Although the first platform and the second platform are different system platforms, since the technical framework module B1 applied to the first platform and the technical framework module B2 applied to the second platform both perform the same kind of operation (i.e., B operation), the technical framework module B1 applied to the first platform and the technical framework module B2 applied to the second platform both implement the same technical framework interface, i.e., interface Y in fig. 3.
The control logic module determines the task to be executed and sends the task to be executed to the technical framework module B1 or the technical framework module B2 through the interface Y. The technical framework module B1 suitable for the first platform can execute the operation B related to the first platform according to the task to be executed; and the technical framework module B2 suitable for the second platform can execute the operation B related to the second platform according to the task to be executed.
And after the technical framework module executes the operation related to the system platform, a corresponding operation result is obtained. Optionally, the technical framework module sends the operation result to the control logic module. And the control logic module executes corresponding control operation based on the operation result.
It should be noted that the cross-platform underlying software system in the embodiment of the present application may be deployed in at least one of a presentation layer, a logic layer, or a kernel layer in the system platform. When the cross-platform bottom software system is deployed on the presentation layer, the cross-platform bottom software system comprises a control logic module, a technical framework interface and a plurality of technical framework modules, wherein the technical framework modules are connected with the control logic module through the technical framework interface; when the cross-platform bottom software system is deployed on a logic layer, the cross-platform bottom software system comprises a control logic module, a technical framework interface and a plurality of technical framework modules, wherein the technical framework modules are connected with the control logic module through the technical framework interface; when the cross-platform bottom software system is deployed in the kernel layer, the cross-platform bottom software system comprises a control logic module under the kernel layer, a technical framework interface and a plurality of technical framework modules connected with the control logic module through the technical framework interface. For any level, the specific implementation of the cross-platform underlying software system can be referred to the introduction of any of the above embodiments.
The following describes aspects of embodiments of the present application with a specific example.
The cross-platform bottom software system in the embodiment of the application is a network transmission management and control kernel driver in the host auditing system, realizes management and control of network transmission in the system according to strategy configuration, and supports a Windows system (an operating system) and a Linux system (an operating system), wherein the Windows system and the Linux system are two different system platforms.
Fig. 4 is a schematic diagram of a Network transmission management and control kernel Driver system according to an embodiment of the present application, and as shown in fig. 4, the Network transmission management and control kernel Driver system includes two types of modules, namely, a Network Driver framework (Driver _ Network) and a Network management and control Logic (Logic _ Network).
In fig. 4, the network driver framework module is designed according to the technical specification of the software operating platform and is divided into a Windows network driver framework module and a Linux network driver framework module, so as to filter network transport layer communications in the system, including listening (Listen), accepting connection (Accept), initiating connection (Connect), sending data (Send), receiving data (Receive), and the like, and can obtain information such as local and remote addresses and port numbers, transmission protocols, and the like, and can obtain and modify sent and received data, and can decide to allow or prevent each communication operation.
As shown in fig. 4, the network driven framework module provides a set of module control interfaces (imodules) through which the network driven framework module is controlled to start or stop running.
The network driving framework module also provides a group of system operation interfaces (ISystem), which realize basic operations of thread management, resource sharing lock, synchronous event, system clock and the like for other modules to call.
The network management and control logic module corresponds to a control logic module in a bottom software system of a cross-platform, realizes internal logics such as strategy analysis, strategy matching, logic judgment, log recording and the like, is irrelevant to a software operating environment, and uses the same network management and control logic module for a Windows system and a Linux system.
The network management and control logic module controls the network driving frame module to start running or stop running through the calling module control interface, and executes system operation through calling the system operation interface without directly calling system functions, and specific running environments do not need to be considered.
The Network management and control logic module provides a group of Network management and control logic interfaces (ILogic _ Network), the Network driving framework module calls the Network management and control logic interfaces to transmit control instructions issued by the upper layer of the software to the Network management and control logic module, so that transmission strategies are realized, log records are obtained, network operations in the system are transmitted to the Network management and control logic module, the operations are allowed or prevented according to the returned results, and therefore management and control and audit records of Network transmission according to the strategies are realized.
Optionally, a system operation interface is implemented on the upper layer of the system, and the network management and control logic module is run in an application program on the upper layer of the system to perform functional logic testing, so that the efficiency is higher compared with the efficiency of performing testing on a system kernel layer.
In summary, the embodiments of the present application separate the logic portion of the software, especially the core layer logic, from the control operation of the software from the design point of view. The control operation part of the software is reduced as much as possible, the complexity is reduced, and a general technical framework is formed so as to be convenient for directly assembling and applying in other similar software; the logic part of the software is made into a series of independent modules irrelevant to the operation platform and the hierarchy, the independent modules are combined with the presentation layer for testing, and after the test is passed, each module is embedded into the component of the corresponding hierarchy of each platform without direct application of transplantation, so that unnecessary repeated development is reduced, and the maintainability and the expandability of the software are improved.
Fig. 5 is a schematic flowchart of an application method of a cross-platform based underlying software system according to an embodiment of the present application, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface and used for executing tasks of the same type, and different technical framework modules correspond to different system platforms; as shown in fig. 5, the method includes:
s51, the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and S52, the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In one possible embodiment, the control logic module determines that a task is to be performed, including:
the technical framework module sends an event to the control logic module through the control logic interface;
and the control logic module determines the task to be executed according to the event.
In a possible implementation manner, the technical framework module performs, according to the task to be executed, an operation related to a system platform corresponding to the technical framework module, including:
and the technical framework module calls corresponding system functions to execute the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In a possible implementation manner, the number of the technology framework interfaces is multiple, and the technology framework modules corresponding to different technology framework interfaces are used for executing different types of tasks.
In one possible embodiment, the method further comprises:
the technical framework module sends an operation result to the control logic module;
and the control logic module executes corresponding control operation based on the operation result.
In one possible embodiment, the cross-platform underlying software system further comprises a module control interface; the method further comprises the following steps:
and the control logic module controls the technical framework module to start or stop running through the module control interface.
In one possible implementation, the cross-platform underlying software system is deployed in at least one of a presentation layer, a logic layer, or a kernel layer in the system platform.
The implementation of the application method based on the cross-platform underlying software system provided in the embodiment of fig. 5 may specifically refer to descriptions of the cross-platform underlying software system in the embodiments of fig. 1 to fig. 4, and this embodiment is not described herein again.
Fig. 6 illustrates a physical structure diagram of an electronic device, which may include, as shown in fig. 6: a processor (processor) 610, a communication Interface (Communications Interface) 620, a memory (memory) 630 and a communication bus 640, wherein the processor 610, the communication Interface 620 and the memory 630 communicate with each other via the communication bus 640. The processor 610 may call the logic instructions in the memory 630 to execute an application method based on a cross-platform underlying software system, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface for executing the same type of task, and different technical framework modules correspond to different system platforms; the method comprises the following steps: the method comprises the following steps: the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface; and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In addition, the logic instructions in the memory 630 may be implemented in software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
In another aspect, the present application further provides a computer program product, where the computer program product includes a computer program, where the computer program is storable on a non-transitory computer readable storage medium, and when the computer program is executed by a processor, a computer is capable of executing the application method based on the cross-platform underlying software system provided in the foregoing embodiments, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface and used for executing the same type of task, and different technical framework modules correspond to different system platforms; the method comprises the following steps: the method comprises the following steps: the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface; and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
In yet another aspect, the present application further provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is implemented to perform the application method of the cross-platform based underlying software system provided in the foregoing embodiments, where the cross-platform underlying software system includes a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface, and the technical framework modules are used for performing the same type of task, where different technical framework modules correspond to different system platforms; the method comprises the following steps: the method comprises the following steps: the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface; and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment may be implemented by software plus a necessary general hardware platform, and may also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (10)

1. The cross-platform bottom software system is characterized by comprising a control logic module, a technical framework interface and a plurality of technical framework modules which are connected with the control logic module through the technical framework interface and used for executing tasks of the same type, wherein different technical framework modules correspond to different system platforms;
the control logic module is used for determining a task to be executed and sending the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module is used for executing the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
2. The cross-platform underlying software system of claim 1, further comprising a control logic interface;
the technical framework module is used for sending an event to the control logic module through the control logic interface;
the control logic module is specifically configured to determine the task to be executed according to the event.
3. The cross-platform underlying software system of claim 1,
and the technical framework module is used for calling corresponding system functions to execute the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
4. The cross-platform underlying software system according to claim 3, wherein the number of the technology framework interfaces is plural, and the technology framework modules corresponding to different technology framework interfaces are used for executing different types of tasks.
5. The cross-platform underlying software system according to any one of claims 1-4,
the technical framework module is also used for sending an operation result to the control logic module;
and the control logic module is also used for executing corresponding control operation based on the operation result.
6. The cross-platform underlying software system according to any one of claims 1-4, further comprising a module control interface;
the control logic module is also used for controlling the technical framework module to start or stop running through the module control interface.
7. The cross-platform underlying software system according to any one of claims 1-4,
the cross-platform underlying software system is deployed in at least one of a presentation layer, a logic layer, or a kernel layer in the system platform.
8. The application method of the bottom software system based on the cross platform is characterized in that the bottom software system based on the cross platform comprises a control logic module, a technical framework interface and a plurality of technical framework modules which are connected with the control logic module through the technical framework interface and are used for executing tasks of the same type, wherein different technical framework modules correspond to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
9. An electronic device, comprising a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor implements an application method based on a cross-platform bottom software system when executing the program, the cross-platform bottom software system comprises a control logic module, a technical framework interface and a plurality of technical framework modules connected with the control logic module through the technical framework interface and used for executing tasks of the same type, and different technical framework modules correspond to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
10. A non-transitory computer readable storage medium on which a computer program is stored, wherein the computer program, when executed by a processor, implements a cross-platform based application method for an underlying software system, the cross-platform underlying software system comprising a control logic module, a technical framework interface, and a plurality of technical framework modules connected to the control logic module through the technical framework interface for performing the same type of task, different technical framework modules corresponding to different system platforms; the method comprises the following steps:
the control logic module determines a task to be executed and sends the task to be executed to the technical framework module through the technical framework interface;
and the technical framework module executes the operation related to the system platform corresponding to the technical framework module according to the task to be executed.
CN202211381262.8A 2022-11-07 2022-11-07 Cross-platform bottom layer software system, application method, equipment and storage medium Active CN115567361B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211381262.8A CN115567361B (en) 2022-11-07 2022-11-07 Cross-platform bottom layer software system, application method, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211381262.8A CN115567361B (en) 2022-11-07 2022-11-07 Cross-platform bottom layer software system, application method, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN115567361A CN115567361A (en) 2023-01-03
CN115567361B true CN115567361B (en) 2023-04-07

Family

ID=84768629

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211381262.8A Active CN115567361B (en) 2022-11-07 2022-11-07 Cross-platform bottom layer software system, application method, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115567361B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012047932A2 (en) * 2010-10-04 2012-04-12 Headwater Partners I Llc System and method for providing user notifications
CN109976716A (en) * 2017-12-28 2019-07-05 天津市向华生产力促进有限公司 A kind of automated software development system
CN110018909A (en) * 2018-01-08 2019-07-16 开放电视公司 System and method for using the hardware controls of kernel proxy

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9292502B2 (en) * 2013-02-28 2016-03-22 Web Computing AS Modular platform for web applications and systems

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012047932A2 (en) * 2010-10-04 2012-04-12 Headwater Partners I Llc System and method for providing user notifications
CN109976716A (en) * 2017-12-28 2019-07-05 天津市向华生产力促进有限公司 A kind of automated software development system
CN110018909A (en) * 2018-01-08 2019-07-16 开放电视公司 System and method for using the hardware controls of kernel proxy

Also Published As

Publication number Publication date
CN115567361A (en) 2023-01-03

Similar Documents

Publication Publication Date Title
US7823023B2 (en) Test framework for testing an application
US20160378554A1 (en) Parallel and Distributed Computing Using Multiple Virtual Machines
CN103092670A (en) Cross-platform virtual computing resource management method under cloud computing environment
CN100589422C (en) A simulated single board and its simulation method
CN101765225A (en) Virtual cluster management system and cluster node
CN104951694A (en) Isolation method and apparatus for management virtual machine
US11169847B1 (en) Method and device for processing distributed data solving problem of manual intervention by data analysts
CN111857951A (en) Containerized deployment platform and deployment method
US10318343B2 (en) Migration methods and apparatuses for migrating virtual machine including locally stored and shared data
CN114237853A (en) Task execution method, device, equipment, medium and program product applied to heterogeneous system
CN115567361B (en) Cross-platform bottom layer software system, application method, equipment and storage medium
CN110324194B (en) Method, apparatus, system and medium for load balancing
CN117519972A (en) GPU resource management method and device
US11816204B2 (en) Multi-tenant actor systems with web assembly
CN109344059B (en) Server pressure testing method and device
CN115167985A (en) Virtualized computing power providing method and system
CN115129449A (en) Resource scheduling method and device for shared GPU
CN111026452B (en) Method and system for remote 32-bit process injection of 64-bit process
CN111782363A (en) Method and flow system for supporting multi-service scene calling
CN105094896B (en) Client terminal start-up method, apparatus and system on virtual platform
Paokin et al. Unified approach for provision of supercomputer center resources
CN113742104A (en) AI-based RPA (resilient packet Access) body-separating function generation method and device
CN110650063A (en) Centralized bank third-party software simulation system and method
CN115664948B (en) Method, device, system and storage medium for automatic configuration and issuing of virtual resources
CN115185700B (en) High-integration single-process container management method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant