CN114047982B - Microkernel component integration method based on description specification - Google Patents
Microkernel component integration method based on description specification Download PDFInfo
- Publication number
- CN114047982B CN114047982B CN202210036231.2A CN202210036231A CN114047982B CN 114047982 B CN114047982 B CN 114047982B CN 202210036231 A CN202210036231 A CN 202210036231A CN 114047982 B CN114047982 B CN 114047982B
- Authority
- CN
- China
- Prior art keywords
- component
- information
- components
- identifier
- interface
- 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
Links
- 230000010354 integration Effects 0.000 title claims abstract description 47
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000003993 interaction Effects 0.000 claims abstract description 44
- 238000004891 communication Methods 0.000 claims description 59
- 230000002452 interceptive effect Effects 0.000 claims description 40
- 230000008569 process Effects 0.000 claims description 16
- 230000005540 biological transmission Effects 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 4
- 230000010365 information processing Effects 0.000 claims description 3
- 238000009795 derivation Methods 0.000 claims 1
- 238000011161 development Methods 0.000 abstract description 10
- 238000013461 design Methods 0.000 abstract description 8
- 230000008878 coupling Effects 0.000 abstract description 5
- 238000010168 coupling process Methods 0.000 abstract description 5
- 238000005859 coupling reaction Methods 0.000 abstract description 5
- 238000004806 packaging method and process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000012938 design process Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000002203 pretreatment Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44594—Unloading
-
- 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/542—Event management; Broadcasting; Multicasting; Notifications
-
- 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/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of computer software design, and particularly relates to a component integration method. The technical scheme of the invention is to design a microkernel component integration method based on description specifications, which is characterized in that: a microkernel is provided that includes a component description file specification, a set of integrated interface services. The service components can be directly used for integrating other products after the definition description is changed by adopting a mode of standardizing and packaging the service components, defining and describing the functions of the components and generalizing the interaction among the management components, so that the coupling degree among the components is reduced, and the team cooperation development efficiency is greatly improved; the core functions of the application framework are extracted to form the application framework in a simplified form, the basic operation of the application framework is supported, developers can design basic components to realize continuous extension of the basic functions of the application framework, and the software system is more stable and the business function extension is more flexible.
Description
Technical Field
The invention belongs to the technical field of computer software design, and particularly relates to a component integration method.
Background
The traditional method for integrating service components by application software is to package each service function into a dynamic link library file, then realize the integration of the service components by utilizing the loading and unloading functions of the dynamic link library, and realize the calling of the service functions by adopting a mode of directly calling the packaging functions of the dynamic link library. The traditional integration mode has the problems of high coupling degree, low reusability and the like, so that the multiplexing repeated development work of the service components is more, and the communication workload of the collaborative development technology is large.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a microkernel component integration method based on description specifications, which reduces the coupling degree among components and enables the service function expansion to be more flexible.
In order to achieve the purpose of the invention, the technical idea of the invention is as follows: aiming at the problem that the interactive interfaces among the components are not uniform in specification at present, the interactive interfaces have to be modified due to inevitable reasons in the development process, centralized coordination needs to be carried out again as long as the interfaces are changed, then the interactive interfaces and the logic codes are modified according to the coordination result, the workload of coordination and communication is increased, and the workload of coding is increased at the same time. Therefore, the invention provides a method for abstracting an interactive interface into a component description file specification, each component forms an information file for describing the interactive relationship between the inside and the outside of the component based on the specification, designs a group of integrated interface services, and uniformly schedules the activities of each component (the activities include the possible actions of registration, information transmission, calling, uninstalling and the like of the components in the software life cycle), thereby reducing the coupling degree among the components.
The technical scheme adopted by the invention is as follows: a microkernel component integration method based on description specifications is characterized in that: setting a microkernel comprising a component description file specification and a group of integrated interface services;
the component description file specification is a structured description template, and the description template defines the identification information of the component to the component and the structural specification of information required by the interactive relationship between the interior and the exterior of the component;
when each component is designed, writing and forming a corresponding component description file according to the component description file specification;
the integrated interface service performs unified scheduling on the components based on the component description file.
Further, the method for integrating microkernel components based on description specifications is characterized in that:
the component description file specification comprises the specification of component information, integrated information, interactive information and interface type information; the component information at least comprises information which can uniquely identify the component and is recorded as a component identifier; the integration information at least comprises information which can uniquely identify the component function point and is recorded as an integration interface identifier; the interactive information at least comprises information which can uniquely identify the component information transmission and is recorded as an interactive information identifier; the interface class information at least comprises information which can uniquely identify the component interface class and is marked as an interface class identifier.
Further, the method for integrating microkernel components based on description specifications is characterized in that: the component identifier is used for component location; the integrated interface identifier is used for logic judgment before calling the component function point; the interactive information identifier is used for unique identification of information interaction between the components; the interface class identifier is used for unique identification of an externally provided interface class object.
Further, the method for integrating microkernel components based on description specifications is characterized in that: the integrated interface service comprises a component management service, a component connection service and a component communication service; wherein:
the component management service is a management program, realizes the management of the components, and comprises the following steps: when the service is started, reading the component description file and loading, registering, inquiring, scheduling and unloading the component according to the component description file; invoking the component connection service;
the component connection service provides a component connection service abstract class for each component, and the component connection service abstract class defines interfaces for acquiring a component interface class, initializing a component and releasing the component;
the component communication service comprises a sending abstract class and a receiving abstract class, wherein the sending abstract class is used for sending the interaction information to the component through deriving a sending subclass in the component communication service; each component derives a respective component communication service reception subclass from the reception abstraction class for processing the received component communication service information.
Further, the method for integrating microkernel components based on description specifications is characterized in that: after the components complete the component description files according to the component description file specifications, the integration of the components is realized by the integration interface service; the method specifically comprises the following steps:
the component management service implements registration of the component: after the component management service program is started, automatically scanning the component description file, loading a component dynamic library, creating a component connection object according to the component connection service abstract class, acquiring a component interface class set, and storing a loaded component into a registered component set to realize the integration of the components;
the component connection service implements a connection function between components: each component derives a respective component connection service subclass from the component connection service abstract class, realizes an interface function in the component connection service subclass, and establishes a connection relation with each component;
the component communication service realizes the information interaction function among the components: creating a sending subclass derived from the sending abstract class in the component communication service, and realizing an interface function of the sending subclass, wherein the interface at least comprises two parameters of the interaction information identifier and the data flow; when the component calls the interface, the component communication service inquires a corresponding interaction rule in the registration component set according to the interaction information identifier, and calls the receiving abstract class to transmit the component information according to the interaction rule; creating a receiving subclass derived from the receiving abstract class in the component, and analyzing the data stream by the component through the receiving subclass according to the interactive information identifier during receiving to enter an information processing flow;
the component management service completes the unloading process of the component: and the component management service program sequentially takes out the components from the registered component set, calls the component connection service to release the components, and unloads the components by the component management service.
Further, the interaction rules in the component communication service as described above are characterized by: the interaction rule defines a standard followed by information interaction among the components in the component communication service, and comprises an interaction information identifier, a transmission mode and a component identifier;
the transmission mode is used for defining the information transmission mode among the components, and comprises a register mode and an instant mode; the register mode is that in the process of sending information by the component, a data stream sent by the component is temporarily stored in a sending cache area in the component communication service, the data stream in the cache area is regularly inquired by adopting a fixed time interval, and then the data stream is added into a distribution process; the instant mode is that in the process of sending information by the component, the data stream in the component communication service is directly added into the distribution flow;
the component identifier is used for identifying two-party components for information interaction in the component communication service; the component identifier comprises a sending component identifier and a receiving component identifier; the sending component identifier is used for identifying a sending component; the receiving component identifier is used to identify a group of receiving components; defining the communication mode as on-demand, multicast and broadcast by judging the receiving component identifier; the on-demand is a component communication mode that identifies a receiving component in the receiving component identifier; the multicast is a component communication mode which identifies a plurality of receiving components in the receiving component identifier; the broadcast is the component communication means that identifies all components in the received component identifier.
The invention provides a microkernel component integration method based on description specifications, which adopts a standardized encapsulation service component, a defined description component function and a universal management component interaction mode, and the service component can be directly used for integrating other products after the definition description is changed, thereby realizing the reduction of the coupling degree among the components and greatly improving the collaborative development efficiency of a large team; the invention forms a simplified application framework by extracting the core function of the application framework, which is used for supporting the basic operation of the application framework, on the basis, developers can design basic components to realize the continuous expansion of the basic function of the application framework, and simultaneously develop or reuse corresponding business components according to the product requirements to finally realize specific software products, thereby realizing more stable software system and more flexible business function expansion, solving the problem that the application framework and the business functions need to be simultaneously modified in the business function expansion in the prior art, greatly shortening the development period of the software products and improving the stability of the software products.
Drawings
FIG. 1 is a system diagram of a microkernel integrated framework according to the present invention;
FIG. 2 is an example component description file specification of the present invention;
FIG. 3 is a schematic diagram illustrating the use of the component description file specification of the present invention;
FIG. 4 is a flow diagram of a conventional application framework integration component;
FIG. 5 is a flow diagram illustrating an assembly management service integration assembly according to the present invention;
FIG. 6 is a schematic diagram of the component connection service of the present invention;
FIG. 7 is a schematic diagram of the communication service principle of the components of the present invention.
Detailed Description
The technical scheme of the invention is further specifically described with reference to the accompanying drawings and specific embodiments.
The following further describes the embodiments of the present invention with reference to the accompanying fig. 1-7. The present invention is not limited to the description of the following examples.
Example 1:
a microkernel component integration development method based on description specifications comprises the following specific steps: the microkernel integration framework comprises three integration interface services, namely a component description file specification and a component management service, a component connection service, a component communication service and the like. The component management service provides functions of loading components, registering components, inquiring components, scheduling components, unloading components and the like; the component connection service provides functions of acquiring an interface class set, initializing a component, releasing the component and the like; the component communication service is used for information interaction among the components, and comprises information sending, information preprocessing, information receiving and the like. The microkernel integrated framework system relationship is shown in figure 1.
The assembly referred to in this embodiment includes: a business component and a base component; basic components: the universal functional module is constructed for completing certain application requirements; and (4) service components: and the specialized functional module is constructed for completing the requirement of a specific application. Host program: refers to a software environment under which software lives in a computer environment. The host program directly calls the entry address of the microkernel integrated framework to mount the microkernel integrated framework; the components write and implement interface logic codes according to a set of integration interface specifications provided by a microkernel integration framework, and the microkernel integration framework is responsible for integrating and scheduling the components according to the interface specifications and providing information interaction functions, as shown in fig. 1.
First step component description file specification design
In the traditional software product design process: product developers need to decompose product functions into a plurality of components, determine interactive interfaces (such as a function calling interface and an information interactive interface) among the components and interactive interfaces (such as a component integration interface and a function scheduling interface) between an application framework and the components, and write logic codes of the interface functions. If the interactive interface has to be modified due to inevitable reasons in the design process, developers need to perform centralized coordination again, then modify the interactive interface and the logic code according to a coordination result, once the change times are increased, the workload of coordination and communication is increased, and the workload of coding is increased.
By adopting the invention, the external interaction relation designed by the traditional software product is abstracted into the component description file specification, each component refers to the file specification, writes the exclusive component description file, and simultaneously realizes the interface logic code defined in the specification. The defined component description file specification is shown in fig. 2.
The "component information" defines basic information of the component. The component identifier is a unique identification of the component name including all components in the whole software product, and call exception caused by component naming conflict is avoided.
The 'integration information' defines the functions provided by the component integration, and at least comprises an 'integration interface identifier' which can uniquely identify the information of the component function point.
"interaction information" defines interaction rules used for information interaction between components. In the sending stage, each component sends the interactive information to other components by using the defined interactive information identifier; and in the receiving stage, after each component judges the correctness of the interactive information identifier, the data stream of the interactive information is analyzed.
The interface class information defines all interface classes provided by the component, and at least comprises an interface class identifier which is used for uniquely identifying an externally provided interface class object.
The component description information is stored in an XML file format in consideration of the characteristics of cross-platform, easy reading, expandability, visualization and the like of the component description file specification.
When the component is designed, the self-defined integrated interface identifier and the self-defined interactive information identifier are judged in advance, then the corresponding logic code is executed, the two types of identifiers are filled in the component description file, and a caller calls the logic code according to the identifier defined in the component description file. When the two types of interfaces of the component are changed, the component only needs to modify the internal logic code.
The interface class provided by the component to the outside is represented by the interface class identifier in the component description file, the caller can find the corresponding interface class object through the interface class identifier, and the interface class object is used for calling the method in the interface class definition file by combining the interface class definition file provided by the component. When the interface class provided by the component changes, the component modifies the logic code of the interface class and updates the interface class definition file for the caller. The component description file specification uses the principle as shown in fig. 3.
Second step component management service design
Traditional application framework integration component process: coding each component dynamic library to realize an integrated interface function; providing the compiled component dynamic library and the integrated interface function definition file to an application framework; the application framework calls one by one according to the integrated interface function definition file to realize component integration; when the component integration interface changes, the component needs to realize the interface again and then provides the interface for the application framework integration again. A conventional component integration flow diagram is shown in fig. 4.
By adopting the method, the component description set is defined to store the component description information, and the component description information is the structured data information converted from the component description file; the registered component set is defined to store the loaded component information, which is composed of component description information, component dynamic library objects, component connection objects, component interface sets, etc. When the component management service is started, scanning a component description file, loading a component dynamic library, creating a component connection object, acquiring a component interface set, and storing a loaded component into a registered component set. The series of steps are automatically completed in sequence by the component management service without writing additional component integration codes. The component management service integration component flow diagram is shown in fig. 5.
Third step component connection service design
Providing a component connection service abstract class for each component, wherein the component connection service abstract class comprises interfaces such as an interface class set, an initialization component and a release component; each component derives its component connection service subclass from the component connection service abstract class and implements the interface function. A component connectivity service schematic is shown in fig. 6.
Fourth step component communication service design
Designing a component communication service sending abstract class, wherein the component communication service sending abstract class comprises a sending information interface, and a component calls the interface as required to realize an inter-component information sending function; designing a component communication service receiving abstract class, comprising a receiving information interface, wherein each component derives the component communication service receiving subclass from the component communication service receiving abstract class, realizes the interface function and is used for processing the received component communication service information. A component communication service schematic is shown in fig. 7.
And creating a sending subclass derived from the component communication service sending abstract class in the component communication service to realize the function of a sending information interface, wherein the interface comprises two parameters of an interactive information identifier and a data flow. When the component calls the interface, the component communication service inquires corresponding interaction rules in the registration component set according to the interaction information identifier, and transmits the component information according to a specified transmission mode. When the transmission mode is set as a register mode, the transmitted data streams are stored in a transmission cache region and then enter a distribution process one by one; when the transmission mode is set to the instant mode, the transmitted data stream will directly enter the distribution process. In the distribution process, the name of the receiving component is analyzed to determine the communication mode (such as three modes of on-demand, multicast and broadcast) of the piece of information.
Aiming at a register mode, firstly judging whether a polling timer is started, if not, starting the polling timer, inquiring an interaction request in a data cache region according to a delta t (ms) time interval, if the inquiry is successful, taking out an interaction request from the cache region, carrying out a series of pretreatments (including cache data object validity judgment, interaction rule validity judgment, component object validity judgment and the like), indirectly calling a receiving information interface of each component communication service receiving subclass by calling a component communication service receiving abstract class, and finally realizing the analysis and the specific logic processing of interaction information by a receiving component; if the query fails, the polling timer is stopped.
And (3) dibbling: a component sends interaction information to a specified component object. And sending subclasses by the component communication service to take out the registered components one by one, matching the on-demand object, and sending interactive information to the object if the matching is successful, and quitting the matching process.
Multicast: a component sends interaction information to a plurality of specified component objects. And sending subclasses by the component communication service to take out the registered components one by one, taking each component object in the multicast object as an on-demand object, matching each on-demand object in the multicast object, and sending interactive information to the object if the matching is successful until all the registered components are taken out.
Broadcasting: one component sends interaction information to all other component objects. The component communication service sends subclasses to take out the registered components one by one, treats each registered component object as an on-demand object, and sends interactive information to the object until all registered components are taken out.
Fifth step microkernel component integrated framework application
1 creating Components
And (3) creating a component dynamic link library project by utilizing the Qt Creator, copying a component connection service abstract class to the project, deriving the component connection service subclass of the component from the component connection service abstract class, and realizing all interface functions of the abstract class.
And writing the component description file of the exclusive local component according to the component description file specification provided by the component management service.
2 Loading assembly
And (3) creating a host program by utilizing the Qt Creator, copying a microkernel framework dynamic library to the project, calling an entry address of a microkernel integration framework in an entry function of the host program, and delivering to a component management service to load, connect and register each component.
3 inter-component interactive communication
The method comprises the steps that a component calls a component in component communication service as required to send an abstract class, two parameters of an interactive information identifier and a data stream are transmitted, the component communication service enters a sending process according to an interactive rule, the abstract class is received by the component to send interactive information to a designated component, and after a component receiver receives the component data interactive information, the data stream is analyzed according to the appointed interactive information identifier and enters an information processing process.
4 unloading assembly
The component management service sequentially takes out the components from the registered component set, calls the component connection service to release the components, and unloads the components by the component management service.
A microkernel component integration development method based on definition description takes the microkernel framework mentioned above as a stable core of an application framework, and achieves the purpose of finally realizing a specific software product through the expansion of basic component functions and the loading of business components according to requirements. The invention can obviously improve the software development efficiency, shorten the development period, reduce the development difficulty and the maintenance cost and produce more standardized software products.
Claims (4)
1. A microkernel component integration method based on description specifications is characterized in that: setting a microkernel comprising a component description file specification and a group of integrated interface services, wherein the integrated interface services comprise a component management service, a component connection service and a component communication service;
the component description file specification is a structured description template, and the description template defines the identification information of the component to the component and the structural specification of information required by the interactive relationship between the interior and the exterior of the component; the method specifically comprises the specification of component information, integrated information, interactive information and interface information; the component information at least comprises information which can uniquely identify the component and is recorded as a component identifier; the integration information at least comprises information which can uniquely identify the component function point and is recorded as an integration interface identifier; the interactive information at least comprises information which can uniquely identify the component information transmission and is recorded as an interactive information identifier; the interface class information at least comprises information which can uniquely identify the component interface class and is recorded as an interface class identifier;
the component identifier is used for component location; the integrated interface identifier is used for logic judgment before calling the component function point; the interactive information identifier is used for unique identification of information interaction between the components; the interface class identifier is used for unique identification of an interface class object provided by the interface class identifier to an external component;
when each component is designed, writing and forming a corresponding component description file according to the component description file specification;
the integrated interface service performs unified scheduling on the components based on the component description file, wherein:
the component connection service is used for realizing a connection function between components, the component connection service comprises a component connection service abstract class and a component connection function specification, each component derives a respective component connection service subclass from the component connection service abstract class, an interface function is realized in the component connection service subclass of each component, a connection relation with each component is established, and the interface function comprises an interface acquisition set, a component initialization and a component release; meanwhile, each component writes a respective component export function according to the component function specification for exporting the created connection service subclass object;
the component management service is used for realizing the management of the components, automatically scanning the component description files of the components, loading a component dynamic library, calling the component export function of the components according to the component connection function specification in the component connection service to realize the creation of a component connection object, acquiring a component interface class set, storing the loaded components into a registered component set, and calling the component connection service subclass of the components by calling a component connection base class in the component connection service;
the component communication service is used for realizing the information interaction function among the components, and comprises a sending abstract class and a receiving abstract class, wherein the sending abstract class is used for sending interaction information to the components through derivation sending subclasses in the component communication service; each component derives a respective component communication service reception subclass from the reception abstraction class for processing the received component communication service information.
2. The method of claim 1 for microkernel component integration based on description specification, wherein: after the components complete the component description files according to the component description file specifications, the integration of the components is realized by the integration interface service; the method specifically comprises the following steps:
when the component management service is started, reading the component description file and loading, registering, inquiring, scheduling and unloading the component according to the component description file; invoking the component connection service;
the component connection service provides a component connection service abstract class for each component, and the component connection service abstract class defines interfaces for acquiring a component interface class, initializing a component and releasing the component;
the component communication service realizes the information interaction function among the components: creating a sending subclass derived from the sending abstract class in the component communication service, and realizing an interface function of the sending subclass, wherein the interface at least comprises two parameters of the interaction information identifier and the data flow; when the component calls the interface, the component communication service inquires a corresponding interaction rule in the registration component set according to the interaction information identifier, and calls the receiving abstract class to transmit the component information according to the interaction rule; creating a receiving subclass derived from the receiving abstract class in the component, and analyzing the data stream by the component through the receiving subclass according to the interactive information identifier during receiving to enter an information processing flow;
the component management service completes the unloading process of the component: and the component management service program sequentially takes out the components from the registered component set, calls the component connection service to release the components, and unloads the components by the component management service.
3. The method of claim 2 for microkernel component integration based on description specification, wherein: storing component description information by adopting an XML file format, wherein the component comprises an integration function, an interaction function and an interface class, and an integration interface identifier corresponding to the integration function, an interaction information identifier corresponding to the interaction function and an interface class identifier corresponding to the interface class are written into the component description file;
when a component needs to call an integrated function or an interactive function in other components, a caller calls a logic code of the component according to an integrated interface identifier or an interactive information identifier defined in a description file of other components, and when other components are called, the corresponding logic code is executed by judging the integrated interface identifier and the interactive information identifier in advance;
when one component needs to call the interface class in other components, the caller finds the corresponding interface class object through the interface class identifier, and uses the interface class object to call the method in the interface class definition file by combining the interface class definition file provided by the component.
4. The method of claim 2 for microkernel component integration based on description specification, wherein: the interaction rule defines a standard followed by information interaction among the components in the component communication service, and comprises an interaction information identifier, a transmission mode and a component identifier;
the transmission mode is used for defining the information transmission mode among the components, and comprises a register mode and an instant mode; the register mode is that in the process of sending information by the component, a data stream sent by the component is temporarily stored in a sending cache area in the component communication service, the data stream in the cache area is regularly inquired by adopting a fixed time interval, and then the data stream is added into a distribution process; the instant mode is that in the process of sending information by the component, the data stream in the component communication service is directly added into the distribution flow;
the component identifier is used for identifying two-party components for information interaction in the component communication service; the component identifier comprises a sending component identifier and a receiving component identifier; the sending component identifier is used for identifying a sending component; the receiving component identifier is used to identify a group of receiving components; defining the communication mode as on-demand, multicast and broadcast by judging the receiving component identifier; the on-demand is a component communication mode that identifies a receiving component in the receiving component identifier; the multicast is a component communication mode which identifies a plurality of receiving components in the receiving component identifier; the broadcast is the component communication means that identifies all components in the received component identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210036231.2A CN114047982B (en) | 2022-01-13 | 2022-01-13 | Microkernel component integration method based on description specification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210036231.2A CN114047982B (en) | 2022-01-13 | 2022-01-13 | Microkernel component integration method based on description specification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114047982A CN114047982A (en) | 2022-02-15 |
| CN114047982B true CN114047982B (en) | 2022-04-08 |
Family
ID=80196492
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210036231.2A Active CN114047982B (en) | 2022-01-13 | 2022-01-13 | Microkernel component integration method based on description specification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114047982B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119806489A (en) * | 2024-12-17 | 2025-04-11 | 成都玖锦科技有限公司 | A microkernel architecture method, a cross-platform system based on a microkernel, and a measuring instrument |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102323879A (en) * | 2011-06-07 | 2012-01-18 | 北京大学 | Complete network middleware operation support platform and integration method of heterogeneous middleware |
| CN105677424A (en) * | 2016-01-08 | 2016-06-15 | 广东亿迅科技有限公司 | Method for hot loading of component-based development integration based on microkernel |
| CN113467972A (en) * | 2021-06-30 | 2021-10-01 | 广州华多网络科技有限公司 | Communication interface construction method, communication interface construction device, computer equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104536737B (en) * | 2014-12-16 | 2018-07-17 | 深圳市金证科技股份有限公司 | A kind of program developing apparatus component-based |
| US11042450B2 (en) * | 2016-07-28 | 2021-06-22 | International Business Machines Corporation | Mechanism for managing container runtime state |
| US11683393B2 (en) * | 2019-09-11 | 2023-06-20 | Intel Corporation | Framework for computing in radio access network (RAN) |
-
2022
- 2022-01-13 CN CN202210036231.2A patent/CN114047982B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102323879A (en) * | 2011-06-07 | 2012-01-18 | 北京大学 | Complete network middleware operation support platform and integration method of heterogeneous middleware |
| CN105677424A (en) * | 2016-01-08 | 2016-06-15 | 广东亿迅科技有限公司 | Method for hot loading of component-based development integration based on microkernel |
| CN113467972A (en) * | 2021-06-30 | 2021-10-01 | 广州华多网络科技有限公司 | Communication interface construction method, communication interface construction device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114047982A (en) | 2022-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101196926A (en) | Database access platform and access method thereof | |
| CN111857801B (en) | Construction method of mobile application | |
| CN113467972B (en) | Communication interface construction method and device, computer equipment and storage medium | |
| CN110659045A (en) | A software-based radar real-time dynamic update system | |
| CN114047982B (en) | Microkernel component integration method based on description specification | |
| CN101312580B (en) | Straight-forward station monitoring center and straight-forward station monitoring method | |
| CN103399735A (en) | Method for developing intermediate layer of remote function call interface | |
| CN109460222A (en) | Modularization method, apparatus, equipment and the storage medium of application program | |
| CN110457013B (en) | Program component configuration device and method | |
| CN102073505B (en) | Service composition-oriented declarative transaction integration method and system | |
| CN115543546B (en) | Spring-based module hot deployment method and system | |
| CN102520971B (en) | Data interaction method and device based on computer-aided design (CAD) software | |
| CN111651190B (en) | Emission control software dynamic assembly method based on multi-dimensional fusion elements | |
| CN117997915B (en) | Cloud data content synchronous distribution method in industrial field | |
| CN109388416A (en) | A kind of plug-in unit realization method and system of application software | |
| CN111666324A (en) | ETL scheduling method and device between relational databases | |
| CN114969190B (en) | Scalable blockchain data export tool | |
| CN117608553A (en) | Multi-data-source-based configurable basic data synchronization method, device and equipment | |
| CN112748907B (en) | C/S mode general measurement and control software architecture based on hardware resources and design method | |
| CN101246421A (en) | Universal frame work based on workflow engine | |
| CN113485795B (en) | Automatic container starting method based on multiple types of items | |
| CN112543190A (en) | System and method for realizing cloud-side mutual work acquisition control based on script technology | |
| CN114756492B (en) | 1553B data bus processing method suitable for various carriers | |
| CN112328302B (en) | Configuration service assembly capable of adapting to various storage systems | |
| CN117093638B (en) | Micro-service data initialization method, system, electronic equipment and storage medium |
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 |