CN112394917A - Cross-platform security service software construction method, device, equipment and storage medium - Google Patents
Cross-platform security service software construction method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112394917A CN112394917A CN202110072109.6A CN202110072109A CN112394917A CN 112394917 A CN112394917 A CN 112394917A CN 202110072109 A CN202110072109 A CN 202110072109A CN 112394917 A CN112394917 A CN 112394917A
- Authority
- CN
- China
- Prior art keywords
- security service
- service software
- service
- plug
- software
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/313—Logic programming, e.g. PROLOG programming language
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Abstract
The embodiment of the invention discloses a cross-platform security service software construction method, a device, equipment and a storage medium, wherein the cross-platform security service software construction method comprises the following steps: dividing the service logic processing of the security service software into three layers, wherein the three layers are a driving layer, a functional layer and a service scheduling layer; separating the man-machine interaction of the security service software from the business realization; the plug-in is determined in conjunction with the authorization file. The functional modules are completely independent in a plug-in mode, transverse dependence does not exist among the functional modules, and all the functional modules only depend on one common module; the functional module can realize hot plug function in the software running process. Each functional module only concerns the service logic code, but not the difference of the operating system, thereby realizing the effects of code reusability, service logic reusability, module reusability and software scalability in the real sense.
Description
Technical Field
The invention relates to the technical field of security service software construction, computer software architecture and construction technology, and the technical field of layered abstract packaging decoupling, mainly relates to a security service software construction method, a device, equipment and a storage medium, in particular to a cross-platform security service software construction method, a device, equipment and a storage medium based on hierarchy system abstraction, and comprises the following steps: and (3) dynamically and freely combining different security service products by using a plug-in plus file-only mode.
Background
The network security refers to that the hardware, software and data in the system of the network system are protected and are not damaged, changed and leaked due to accidental or malicious reasons, the system continuously, reliably and normally operates, and the network service is not interrupted. The network security has been concerned by the whole society, the security service software aiming at the network security is largely applied to various systems based on different levels, the functions of the security service software in different systems are the same, but the software components of different systems have differences, and how to eliminate the differences of different systems, the problem that one set of security service software can be deployed and applied across platforms is not solved all the time.
Specifically, the security service software is different from common application software, monitors the read-write behavior of a file under different operating systems, and performs Trojan horse static analysis on an executable file of the operating system; it is necessary to monitor and scan the operation of the entire system and provide security services to the entire system, the function of which involves various aspects of the system. There is a strong dependence on the system, including the individual applications running within the system. The existing various safety service software is basically oriented to realizing programming, strong correlation exists between the safety service software and a corresponding system, the safety service software corresponding to replacing one system or updating other applications is probably unavailable, and the safety service software which is responded can only be changed according to the system, so that the problems of repeated development and resource waste of the safety service software are brought. Meanwhile, the service functions related to the safety service software are wide, a plurality of service functions are overlapped, namely different safety service software products are inevitably provided with repeated functions, different safety service software are independently developed, and the problem of resource waste caused by repeated function development is inevitably provided, and the main problems existing in the current safety service software development are as follows:
1. and (3) repeatedly realizing the functions: different safety service software products are independently developed and programmed in a surface implementation mode, and each product can realize the same function or the function with slight difference among products, even if different products with the same function component can only be developed.
2. The function reuse rate is low: different safety service software products are independently developed, an implementation-oriented mode is adopted, an interface-oriented programming mode is not adopted, and loading reuse of each functional component among different safety service products is directly caused. The function multiplexing is usually realized by copying codes among products of the same company. Once a function needs to be modified or a bug appears to need repair. All products using this functionality need to be modified, recompiled, and there is a lot of duplication.
3. The test is difficult to automate: and the man-machine interaction implementation codes of all products are mixed with the business logic codes. Meanwhile, service functions of different products are called and connected in a non-uniform manner, so that the service logic is difficult to test automatically and only can be tested manually by a tester, and the test result depends on manual judgment; regression testing requires a large number of repeated manual tasks.
4. The system has low abstraction level: because the service function is mixed with the UI and the operating system interface, the service code is based on the realization programming, and the coupling degree is high and the multiplexing is difficult. Different operating system platforms need to be implemented separately.
5. The software has low expandability: product capability is formed through source code compiling; the whole product source code needs to be reprogrammed when a new function is added or deleted. Any minor change may affect the whole product and not comply with the principle of opening and closing.
Disclosure of Invention
The embodiment of the invention provides a cross-platform security service software construction method, a device, equipment and a storage medium, which can solve the problems of low code reuse degree, difficult automation of test, respective development of different operating systems and low software expandability in the conventional security service software construction, all functional modules are completely independent through a plug-in mode, transverse dependence does not exist among the functional modules, and all the functional modules only depend on one public module; the functional module can realize hot plug function in the software running process. Each functional module only concerns the service logic code, but not the difference of the operating system, thereby realizing the effects of code reusability, service logic reusability, module reusability and software scalability in the real sense.
The embodiment of the invention provides a cross-platform security service software construction method, which comprises the following steps:
dividing the service logic processing of the security service software into three layers, wherein the three layers are a driving layer, a functional layer and a service scheduling layer;
separating the man-machine interaction of the security service software from the business realization;
the plug-in is determined in conjunction with the authorization file.
Furthermore, the business logic processing of the security service software is divided into three layers, namely, the business logic processing is driven by a driver
The hierarchical models of the layer, the functional layer and the service scheduling layer are hierarchically abstracted, and the implementation of human-computer interaction is realized by decoupling the service logic of the security service software based on interface programming among the layers.
Further, the driver layer serves as a public dependency to encapsulate the bottom layer public application and the kernel interface of the operating system, and is used for providing a basic framework for hot plug of the service module and providing a service function interface for registration so as to realize a plug-in architecture.
Furthermore, the functional layer directly depends on an interface provided by the driver layer for programming, abstractly encapsulates the functional logic, and simultaneously keeps mutual independence among all functional components, so that the capability of combined encapsulation is provided for the service scheduling layer.
Furthermore, the service scheduling layer is used for completing the product comprehensive application function according to the strategy combination functional components of different products to form a product with a comprehensive solution.
Further, the method for separating human-computer interaction and business implementation of the security service software comprises the following steps: the implementation process of the security service software as the front end of the security service business is separated from the human-computer interaction process as the back end of the security service software, and the human-computer interaction process and the implementation process of the security service business exchange data in an IPC mode.
Further, the method for determining by the plug-in combination with the authorization file comprises the following steps: the security service software does not need all binary files when running; the framework only starts necessary functions and processes; dynamically determining the product capability in an authorization file mode, including the protection of an authorization file and the analysis of authorization content; the framework provides an interface for registering the plug-in, and manages the loading and unloading life cycle of the plug-in; the framework dispatches the business functions provided in the plug-ins as needed.
The embodiment of the invention also provides a cross-platform security service software construction device, which comprises:
the system comprises a layering module, a service scheduling module and a service management module, wherein the layering module is used for dividing the service logic processing of the security service software into three layers, and the three layers are respectively a driving layer, a functional layer and a service scheduling layer; the system is also used for dividing the service logic processing of the safety service software into three layers, namely, the three layers are layered and abstracted by using a layered model such as a driving layer, a functional layer and a service scheduling layer, and the layers are based on interface programming to decouple the service logic of the safety service software to realize the realization of man-machine interaction;
the separation module is used for separating the human-computer interaction of the security service software from the business realization; the safety service software is also used for separating the implementation process of the safety service business as the front end from the human-computer interaction process as the rear end, and the human-computer interaction process and the implementation process of the safety service business exchange data in an IPC mode;
the determining module is used for determining the plug-in by combining the authorization file; it is also used for the security service software to run without all binary files; the framework only starts necessary functions and processes; dynamically determining the product capability in an authorization file mode, including the protection of an authorization file and the analysis of authorization content; the framework provides an interface for registering the plug-in, and manages the loading and unloading life cycle of the plug-in; the framework dispatches the business functions provided in the plug-ins as needed.
The embodiment of the invention also provides cross-platform security service software construction equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the cross-platform security service software construction method when executing the program.
The embodiment of the invention also provides a computer-readable storage medium, which stores computer-executable instructions, wherein the computer-executable instructions are used for executing the cross-platform security service software construction method.
The embodiment of the invention comprises the following steps: dividing the service logic processing of the security service software into three layers, wherein the three layers are a driving layer, a functional layer and a service scheduling layer; separating the man-machine interaction of the security service software from the business realization; the plug-in is determined in conjunction with the authorization file. Therefore, the problems that in the existing security service software construction, the code reuse degree is low, the test is difficult to automate, different operating systems need to be developed respectively, and the software expandability is low can be solved. The functional modules are completely independent in a plug-in mode, transverse dependence does not exist among the modules, and all the functional modules only depend on one common module; the module can realize hot plug function in the software running process. The functional modules only concern business logic code and do not need to concern operating system differences. The code reusability, the service logic reusability, the module reusability and the software expandability are realized in the real sense.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
FIG. 1 is an overall flowchart of the cross-platform security service software construction method according to the embodiment of the present invention;
fig. 2 is a block diagram of a cross-platform security service software building apparatus according to an embodiment of the present invention.
FIG. 3 is a block diagram of the plug-in mode of an embodiment of the present invention.
Fig. 4 is a structural diagram of dividing the business logic processing of the security service software into three layers according to the embodiment of the present invention.
FIG. 5 is a flowchart of the operation of the plug-in mode of an embodiment of the present invention.
FIG. 6 is a diagram illustrating the shielding of the differences between different operating system interfaces according to an embodiment of the present invention.
Fig. 7 is a schematic diagram of separating human-computer interaction of security service software from service implementation according to the embodiment of the present invention.
FIG. 8 is a functional co-operation and differential packaging diagram of an embodiment of the present invention.
Fig. 9 is a flowchart of the service scheduling layer according to the embodiment of the present invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
The embodiment of the invention is generated for solving the problem, and the embodiment of the invention provides a cross-platform security service software construction technology based on hierarchy system abstraction; the construction technology is used for encapsulating the kernel of the bottom application and the operating system, abstracting the service function, removing the transverse dependence and forming the product capability by the service layer combined service function. The code repetition and the repeated development of different platform codes are eliminated, different products are combined in a plug-in and authorization file mode, the function reuse is realized, and the problem of source code level reuse or library level reuse only in the existing development is finally solved; the service function is difficult to automatically test; the problem of low software expandability; different operating system platforms need to be developed independently.
For the above situation, as shown in fig. 1 to 9, an embodiment of the present invention provides a method for constructing cross-platform security service software, where an interface and a human-computer interaction interface provided by an operating system in construction of the security service software are only details of software implementation, and a service processing code should not be affected by the details, and based on the three modes of a three-layer architecture model, separation of human-computer interaction and service implementation, and combination of plug-in and authorization file into three modes of product capability, the method includes:
Wherein, in one embodiment, the business logic processing of the security service software is divided into three layers, namely
The method comprises the steps that a hierarchical model comprising a driving layer, a functional layer and a service scheduling layer is used for hierarchical abstraction, the business logic of safety service software is decoupled based on interface programming among the layers to realize human-computer interaction, the service scheduling layer is constructed in a plug-in mode, and the plug-in mode dynamically combines product capability and comprises authorization file generation, encryption protection and authorization file analysis; the dynamic loading and unloading of the plug-ins and the dynamic registration of the plug-ins to the business process realize the dynamic combination of different safety service capabilities and the comprehensive reuse of the functional modules. As shown in fig. 3, one or more business logics exist in each plug-in, and the business process determines that one or more of the plug-ins 1, 2, 3 and 4 can be registered to the business process according to the authorization file. The business service capability is jointly determined by the plug-in and the authorization file.
In addition, in an embodiment, the driver layer encapsulates the bottom layer public application and kernel interfaces of the operating system as a public dependency, abstracts system calls provided by different operating systems into a uniform interface, forms a public dependency to provide services for the functional layer, and thereby shields the interface differences of different operating systems, so that the functional layer does not sense the operating system differences and only provides interfaces for the driver layer to be docked, as shown in fig. 6, linux share memory in the drawing represents a way of creating a shared memory under a linux operating system; windows ShareMemory means creating a shared memory under a windows operating system. The ShareMemory represents the creation of a shared memory abstract package, and provides a uniform Create interface for shielding operating system differences; the driver layer provides analysis of the authorization file, dynamic registration and dynamic uninstallation of the service plug-in, and performs service distribution processing according to the service unique identifier to implement a plug-in architecture, as shown in fig. 5, a plug-in workflow is described as follows:
a-1, starting a business process;
a-2, analyzing the configuration file, and loading corresponding plug-in information according to the configuration information in the configuration file;
a-3, the plug-in registers the business processing object and the unique identifier corresponding to the business processing object into a business process;
a-4, starting polling whether a new service request exists;
a-5, if there is new service request, switching to A-6 to execute; if no new business logic is executed in the A-8;
a-6: inquiring a service processing object according to the service unique identifier;
a-7: and the business object calls one or more interface combinations of the functional layer to complete business logic. Returning a service logic processing result;
a-8: whether to quit the business process, if not quit the business process, switching to A-4 to continue polling to judge whether a new business request exists, and if needing to quit the business process, switching to A-9 to execute;
a-9: and unloading the dynamically loaded plug-in and exiting the program.
Thus, the hierarchical model encapsulates the abstraction that a common underlying service includes various operating system kernel interfaces.
The functional layer is directly programmed by depending on an interface provided by the driver layer, abstractly encapsulates the functional logic, and simultaneously keeps mutual independence among all functional components to provide the capability of the service scheduling layer for combined encapsulation, as shown in fig. 4, wherein a product 1 and a product 2 respectively represent finally issued software products. The service layer is composed of a plurality of plug-ins; each plug-in consists of one or a group of related business logic; plug-in 1, plug-in 2, plug-in 3, plug-in 4 represent four different plug-ins of the service layer, each plug-in consisting of one or more services. Each business processing logic is formed by combining one or more functional components of the functional layer, and the function 1, the function 2, the function 3 and the function 4 are used for respectively representing four functional components of the functional layer, which do not have dependency relationship with each other. The driver layer abstract interface consists of a bottom layer public service and an OS kernel, wherein the bottom layer public service is used for shielding the interface difference of each operating system and providing uniform interface encapsulation for the functional layer; the OS kernel is used for shielding the communication difference between the operating system kernel and the application program. And encapsulating the functional components to a driving layer for the interdependent behaviors existing among the functional components. In this way, the functional layer exists as an independent functional component, the functional component only has dependence on the driving layer, functional logic is enclosed in the functional component, and transverse dependence between the functional components is eliminated.
The service scheduling layer is used for scheduling one or more functional components of the functional layer to form service capability according to strategies of different products, and different service components can share one or more functional components of the functional layer; therefore, the business scheduling layer combines different functional layer components in different safety service software products to form corresponding product combination delivery capacity. As shown in fig. 9, the workflow description of the service scheduling layer is specifically as follows:
b-1: the business process acquires request data;
b-2: analyzing the request data for acquiring the hard disk information, and judging to acquire the hard disk information strategy value. If the strategy is executed in the step of converting strategy 1 into B-3, and if the strategy is executed in the step of converting strategy 2 into B-4;
b-3: acquiring the serial number, the model number and the capacity of the hard disk, and switching to B-5 for execution;
b-4: acquiring the serial number, the model number and the starting times of the hard disk, and switching to B-5 for execution;
b-5: sending result data to the UI process, and switching to execute in B-6;
b-6: and finishing the service processing.
And 102, separating the man-machine interaction of the security service software from the business realization.
The method separates the human-computer interaction of the security service software from the service realization, namely, decouples the security service function from the UI expression by a front-end and back-end process separation technology; and the data exchange between the front-end process and the back-end process is completed by using IPC technology and a message queue. In one embodiment, the method for separating human-computer interaction and business implementation of security service software includes: the implementation process of the security service of the security service software as the front end is separated from the human-computer interaction process as the back end, and data exchange is carried out between the human-computer interaction process and the implementation process of the security service in an IPC mode; therefore, the human-computer interaction interface and the service function are realized by adopting a front-end process separation technology and a back-end process separation technology, and the inter-process communication adopts an IPC technology; the realization of the automatic test of the service function, the service function process provides an interface to the outside, and the specific showing details are not concerned; the tester can compile automatic test scripts for testing the interface provided by the business process, and meanwhile, the test regressiveness is realized, and a large amount of repeated work of the tester is saved.
In step 103, the plug-in is determined in conjunction with the authorization file.
In one embodiment, the method for determining by the plug-in combination with the authorization file comprises the following steps: the security service software does not need all binary files when running; the service process only needs to start an IPC channel for data interaction with the UI process, as shown in fig. 7, the interaction steps of the UI process and the service process are specifically as follows:
(1) the front end UI process triggers the service request to generate the service IPC message
(2) Sending IPC messages to business processes by UI processes through IPC channels
(3) The service process analyzes the received IPC message and calls the corresponding service processing function
(4) The service process sends the processing result data to the UI process through the IPC channel
(5) The UI process analyzes the data processed by the service process and displays the result to the UI;
the business process is responsible for analyzing the authorization file, dynamically loads the required plug-ins according to the configuration information of the authorization file, and determines which plug-ins can be loaded into the business process in an authorization file mode, so that each business module is not compiled into a target file in a binary system mode any more, and the target file can be combined into a strong product capability by analyzing the authorization file, and the concrete implementation is shown in fig. 5. The method realizes the aims of reusability of functional modules, reusability of business logic and strong software expandability.
In conclusion, the method provided by the embodiment of the invention can effectively solve the problem of low function reuse degree among safety service software; the problem that the service function of the safety service software cannot be automatically tested can be solved; the problem that independent and repeated development is needed among different operating system platforms can be effectively solved; the product capability of the security service software is not determined by a binary object file generated by static compilation, but the product capability is flexibly combined in a mode of only granting files and plug-ins; the impact of module modification of the security service software can be minimized. All modules are completely independent, and one module source code only needs to be re-programmed into an affected module without any influence on other modules.
As shown in fig. 2, an embodiment of the present invention further provides a cross-platform security service software building apparatus, including:
a layering module 71 for dividing the business logic processing of the security service software into three layers
Respectively a driving layer, a functional layer and a service scheduling layer; and is also used for logical business of security service software
The editing processing is divided into three layers, namely, layered abstraction is carried out on a layered model such as a driving layer, a functional layer and a service scheduling layer, and the implementation of human-computer interaction is realized by decoupling service logic of security service software based on interface programming among all layers;
the separation module 72 is used for separating the human-computer interaction of the security service software from the business implementation; the safety service software is also used for separating the implementation process of the safety service business as the front end from the human-computer interaction process as the rear end, and the human-computer interaction process and the implementation process of the safety service business exchange data in an IPC mode;
a decision module 73 for the plug-in to decide in conjunction with the authorization file; it is also used for the security service software to run without all binary files; the business process only starts necessary functions and flows; dynamically determining the product capability in an authorization file mode, including the protection of an authorization file and the analysis of authorization content; the business process provides an interface for registering the plug-in, and manages the loading and unloading life cycle of the plug-in; and the business process distributes and dispatches the business functions provided by the plug-in unit according to the needs.
The embodiment of the invention also provides cross-platform security service software construction equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the cross-platform security service software construction method when executing the program.
The embodiment of the invention also provides a computer-readable storage medium, which stores computer-executable instructions, wherein the computer-executable instructions are used for executing the cross-platform security service software construction method.
In this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, or other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or modulated data signals such as a carrier wave or other transport mechanism and includes any information delivery media.
Claims (10)
1. A cross-platform security service software construction method is characterized by comprising the following steps:
dividing the service logic processing of the security service software into three layers, wherein the three layers are a driving layer, a functional layer and a service scheduling layer;
separating the man-machine interaction of the security service software from the business realization;
the plug-in is determined in conjunction with the authorization file.
2. The method for constructing cross-platform security service software according to claim 1, wherein the business logic processing of the security service software is divided into three layers, that is, a hierarchical model comprising a driver layer, a functional layer and a business scheduling layer is used for hierarchical abstraction, and each layer is based on interface programming to decouple the business logic of the security service software to realize the realization of human-computer interaction.
3. The method for constructing cross-platform security service software according to claim 1, wherein the driver layer encapsulates the bottom layer common application and kernel interface of the operating system as a common dependency, and is used for providing a basic framework for hot plug of the service module and providing a registered service function interface to realize a plug-in architecture.
4. The cross-platform security service software building method according to claim 1, wherein the functional layer is directly programmed by an interface provided by a driver layer to abstract and encapsulate functional logic, and meanwhile, mutual independence among various functional components is kept, and the capability of the business scheduling layer for assembling and encapsulating is provided.
5. The method for constructing cross-platform security service software according to claim 2, wherein the service scheduling layer is configured to complete a product integrated application function according to policy combination function components of different products, so as to form a product with an integrated solution.
6. The cross-platform security service software construction method according to claim 1, wherein the method for separating human-computer interaction and business implementation of the security service software comprises: the implementation process of the security service software as the front end of the security service business is separated from the human-computer interaction process as the back end of the security service software, and the human-computer interaction process and the implementation process of the security service business exchange data in an IPC mode.
7. The cross-platform security service software building method according to claim 1, wherein the method for determining by the plug-in combination with the authorization file comprises: the security service software does not need all binary files when running; the framework only starts necessary functions and processes; dynamically determining the product capability in an authorization file mode, including the protection of an authorization file and the analysis of authorization content; the framework provides an interface for registering the plug-in, and manages the loading and unloading life cycle of the plug-in; the framework dispatches the business functions provided in the plug-ins as needed.
8. A cross-platform security services software building apparatus, comprising:
the system comprises a layering module, a service scheduling module and a service management module, wherein the layering module is used for dividing the service logic processing of the security service software into three layers, and the three layers are respectively a driving layer, a functional layer and a service scheduling layer; the system is also used for dividing the service logic processing of the safety service software into three layers, namely, the three layers are layered and abstracted by using a layered model such as a driving layer, a functional layer and a service scheduling layer, and the layers are based on interface programming to decouple the service logic of the safety service software to realize the realization of man-machine interaction;
the separation module is used for separating the human-computer interaction of the security service software from the business realization; the safety service software is also used for separating the implementation process of the safety service business as the front end from the human-computer interaction process as the rear end, and the human-computer interaction process and the implementation process of the safety service business exchange data in an IPC mode;
the determining module is used for determining the plug-in by combining the authorization file; it is also used for the security service software to run without all binary files; the framework only starts necessary functions and processes; dynamically determining the product capability in an authorization file mode, including the protection of an authorization file and the analysis of authorization content; the framework provides an interface for registering the plug-in, and manages the loading and unloading life cycle of the plug-in; the framework dispatches the business functions provided in the plug-ins as needed.
9. A cross-platform security service software construction device, comprising a memory, a processor and a computer program stored on the memory and operable on the processor, wherein the processor implements the cross-platform security service software construction method according to any one of claims 1 to 7 when executing the program.
10. A computer-readable storage medium storing computer-executable instructions for performing the cross-platform security service software construction method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110072109.6A CN112394917B (en) | 2021-01-20 | 2021-01-20 | Cross-platform security service software construction method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110072109.6A CN112394917B (en) | 2021-01-20 | 2021-01-20 | Cross-platform security service software construction method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112394917A true CN112394917A (en) | 2021-02-23 |
| CN112394917B CN112394917B (en) | 2021-04-27 |
Family
ID=74625169
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110072109.6A Active CN112394917B (en) | 2021-01-20 | 2021-01-20 | Cross-platform security service software construction method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112394917B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114817018A (en) * | 2022-04-18 | 2022-07-29 | 润芯微科技(江苏)有限公司 | Development and test system of instrument domain man-machine interaction standardized platform |
| CN115002189A (en) * | 2022-04-21 | 2022-09-02 | 上海蓝箭鸿擎科技有限公司 | Spacecraft-oriented high-separation distributed system software architecture |
| CN115237386A (en) * | 2022-09-19 | 2022-10-25 | 杭州实在智能科技有限公司 | Method and system for developing large-scale complex Windows native desktop |
| CN115510427A (en) * | 2022-11-21 | 2022-12-23 | 博智安全科技股份有限公司 | Cross-platform process running credible monitoring method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101018360A (en) * | 2007-02-09 | 2007-08-15 | 中国移动通信集团福建有限公司 | Realization method of computer system of the business service exchange platform |
| CN101539855A (en) * | 2008-12-25 | 2009-09-23 | 厦门亿力吉奥信息科技有限公司 | Service basic software platform |
| US20180341464A1 (en) * | 2016-01-26 | 2018-11-29 | Enterpriseweb Llc | Unified operating system for distributed computing |
-
2021
- 2021-01-20 CN CN202110072109.6A patent/CN112394917B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101018360A (en) * | 2007-02-09 | 2007-08-15 | 中国移动通信集团福建有限公司 | Realization method of computer system of the business service exchange platform |
| CN101539855A (en) * | 2008-12-25 | 2009-09-23 | 厦门亿力吉奥信息科技有限公司 | Service basic software platform |
| US20180341464A1 (en) * | 2016-01-26 | 2018-11-29 | Enterpriseweb Llc | Unified operating system for distributed computing |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114817018A (en) * | 2022-04-18 | 2022-07-29 | 润芯微科技(江苏)有限公司 | Development and test system of instrument domain man-machine interaction standardized platform |
| CN114817018B (en) * | 2022-04-18 | 2023-02-21 | 润芯微科技(江苏)有限公司 | Development and test system of instrument domain man-machine interaction standardized platform |
| CN115002189A (en) * | 2022-04-21 | 2022-09-02 | 上海蓝箭鸿擎科技有限公司 | Spacecraft-oriented high-separation distributed system software architecture |
| CN115237386A (en) * | 2022-09-19 | 2022-10-25 | 杭州实在智能科技有限公司 | Method and system for developing large-scale complex Windows native desktop |
| CN115237386B (en) * | 2022-09-19 | 2022-12-27 | 杭州实在智能科技有限公司 | Method and system for developing large-scale complex Windows native desktop |
| CN115510427A (en) * | 2022-11-21 | 2022-12-23 | 博智安全科技股份有限公司 | Cross-platform process running credible monitoring method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112394917B (en) | 2021-04-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112394917B (en) | Cross-platform security service software construction method, device, equipment and storage medium | |
| EP1582985B1 (en) | Test case inheritance controlled via attributes | |
| US7904886B2 (en) | Method for executing an application in a virtual container forming a virtualized environment session | |
| US11175902B2 (en) | Testing an upgrade to a microservice in a production environment | |
| US20080320071A1 (en) | Method, apparatus and program product for creating a test framework for testing operating system components in a cluster system | |
| CN101165658A (en) | Method and system for automatically generating unit test case of reproduced operation problem | |
| CN112148278A (en) | Visual block chain intelligent contract framework and intelligent contract development and deployment method | |
| CN116069648A (en) | Software testing method, system, equipment and storage medium | |
| EP1171821B1 (en) | Method and apparatus for automated software testing | |
| US20230297348A1 (en) | Method for operating second system application on first system, terminal device and storage medium | |
| US20200104244A1 (en) | Scriptless software test automation | |
| CN113094238A (en) | Method and device for monitoring abnormity of business system | |
| KR20200067474A (en) | Fault injection test method and system for vehicle software based on autosar | |
| CN111522623B (en) | Modularized software multi-process running system | |
| CN104573506A (en) | Virtual machine based real-time monitoring method and device for process behavior | |
| CN111783094A (en) | Data analysis method and device, server and readable storage medium | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN116795576A (en) | Log printing-based device driver debugging method and device and electronic device | |
| CN115756424A (en) | Method, device and equipment for generating MVP (multifunction vehicle platform) code | |
| CN116501596A (en) | Application program testing method and device | |
| US7010454B1 (en) | Test services provider | |
| CN112035192B (en) | Java class file loading method and device supporting component hot deployment | |
| CN114791884A (en) | Test environment construction method and device, storage medium and electronic equipment | |
| CN115185825A (en) | Interface test scheduling method and device | |
| Saini | Testing polymorphism in object oriented systems for improving software quality |
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 |