Service-oriented plug-in management method

Abstract

The invention discloses a service-oriented plug-in management method, and belongs to the technical field of design and development of software in a ground station in the field of spaceflight measurement and control. The method comprises the steps that plug-ins needing to be managed are made into a dynamic link library; performing state management on the plug-in; one plug-in is started, the state of the plug-in is changed into an installed state from an uninstalled state, and a unique identifier is set for the plug-in; the plug-in registers one or more services through the service registry, and other plug-ins acquire the service by registering and monitoring the service registry; and managing the service interfaces registered by all the plug-ins, and completing release and acquisition of the service interfaces. According to the method, rapid customization of various types of software in the measurement and control field can be realized, and meanwhile, plug-in warehouses can be accumulated and enriched to form products or functions with high reusability, so that the software development process is rapidly and stably completed.

Description

Technical Field

[0001] The present invention relates to the technical field of the design and development of various software in ground stations in the field of aerospace measurement and control, and particularly to a service-oriented plug-in management method. Background Art

[0002] Most of the existing ground station software in the field of aerospace measurement and control is developed under the Windows operating system, and mainly uses Visual C++ or Visual C# language for development, which cannot meet the requirements of localization. At the same time, there is a lack of a unified software architecture among various software: the software structures used by each software (system monitoring software, baseband software, wave control software, safety control software, simulator software, automatic test software, etc.) are all different, so it is impossible to cooperate in division of labor, resulting in relatively large waste of personnel and time.

[0003] The dynamic expansion ability of the most widely used current integrated program framework is basically zero. After new requirements such as centralized monitoring, resource reorganization, and interface customization are added to the system monitoring software, the original program structure simply cannot be realized, and a new program architecture that can support dynamic expansion must be developed. Moreover, most of the current software development adopts structure-oriented design, which will cause high cohesion of software functions. When the project requirements change or are transformed, a change in one function will lead to global changes in the code, resulting in a large amount of work such as coding, testing, and joint testing. These large amounts of work and unforeseen modification risks also increase the risks of the development cycle.

[0004] The traditional software development mode involves a large amount of work from requirement mining, analysis, to software architecture design, code writing, joint debugging, and integration, along with unit testing, integration testing, and system testing. One of the typical scenarios is that when there are a large number of business systems of the same type, even if dynamic libraries are used for modularization, the modules still cannot be truly reused, and often need to adapt to a new architecture, and there is also a lack of monitoring and management of the modules. Summary of the Invention

[0005] In view of this, the present invention proposes a service-oriented plug-in management method. The present invention adopts a service-oriented general software framework design method for aerospace measurement and control, which can realize general service plug-ins for measurement and control software and form a general framework for measurement and control software, and can also realize rapid development of plug-ins based on the platform.

[0006] The technical solution adopted by the present invention is as follows:

[0007] A service-oriented plug-in management method, comprising the following steps:

[0008] Step 1, making the plug-ins to be managed into dynamic link libraries, where the dynamic link libraries contain resource files and metadata, and the metadata is used to describe the characteristics of the plug-ins;

[0009] Step 2, manage the status of the plug - in. The status of the plug - in includes: uninstalled, installed, completed, started, stopped, active. The plug - in can only execute code when its status is started, stopped, or active.

[0010] Step 3, enable a plug - in. The status of the plug - in changes from uninstalled to installed, and a unique identifier is set for this plug - in.

[0011] Step 4, the plug - in registers one or more services through the service registry, and other plug - ins obtain this service by registering with and listening to the service registry.

[0012] Step 5, manage the service interfaces registered by all plug - ins to complete the publication and acquisition of service interfaces.

[0013] Furthermore, the plug - in is automatically generated through templates. The templates include baseband data processing plug - in templates, system monitoring service client plug - in templates, system monitoring service server plug - in templates, general plug - in templates, and extension processing class templates.

[0014] The present invention has the following advantages compared with the background technology:

[0015] 1. The present invention adopts a plug - in approach. After analyzing and decomposing requirements according to the business system, developers develop business plug - ins and then directly integrate them through the framework. Testers only need to test the newly developed plug - in modules. In this way, after the process of one project, many plug - ins will be accumulated. When these plug - ins are used in other projects, they do not need to be re - developed and adapted. These plug - ins do not even need to be re - tested and can be directly used. These modules can achieve true reuse without the need to modify new project interfaces or adapt the architecture. After long - term accumulation through multiple projects, a plug - in repository of its own will be formed. Subsequent projects are more assembled by building blocks or simply adjusted in layout through tools. This can greatly reduce the costs of design, development, and testing and shorten the software development cycle.

[0016] 2. In response to the unified and domestic design requirements for various software in the ground control and measurement station, the present invention realizes a general software framework design for space control and measurement based on service orientation. It can be applied to the rapid development of various software in the ground control and measurement station of space, and can be adapted to mainstream domestic software and hardware platforms at the same time. The domestic framework adopts a plug-in development, modular customization, building-block deployment, and service-oriented architecture mode, so that software customization can be quickly realized, the product sequence can be improved, the plug-in warehouse can be enriched, and products or functions with high reusability can be formed, so as to quickly meet software requirements. At the same time, unified platform standards and specifications are adopted to formulate standards such as application interface specifications, service interaction specifications, and resource interface specifications; the platform standards can monitor and restrict the quality of software, and at the same time ensure and control the reasonable software design, so as to ensure the generality, scalability, robustness, and stability of the software.

[0017] 3. The present invention can build a unified software platform for different business directions, realize the rapid development and deployment of software, can quickly customize business function plug-ins, realize the reuse and recombination of business modules, can realize the dynamic configuration of services and functions, provide efficient and diverse communication methods, can provide diverse interface styles, improve the development efficiency of products, and save costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic structural diagram of the plug-in management platform in the embodiment of the present invention;

[0019] Figure 2 It is a hierarchical diagram of the plug-in management platform;

[0020] Figure 3 It is a schematic diagram of plug-in definition and composition;

[0021] Figure 4 It is a diagram of the service call relationship between plug-ins;

[0022] Figure 5 It is a diagram of the plug-in life cycle state;

[0023] Figure 6 It is a diagram of the plug-in rapid development tool. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0024] The present invention will be further described below with reference to the accompanying drawings.

[0025] A service-oriented plug-in management method includes the following steps:

[0026] Step 1, making the plug-ins to be managed into dynamic link libraries, where the dynamic link libraries contain resource files and metadata, and the metadata is used to describe the characteristics of the plug-ins;

[0027] Step 2, manage the status of the plug-ins. The status of the plug-ins includes: not installed, installed, completed, started, stopped, active. The plug-in can only execute code when the status is started, stopped, or active.

[0028] Step 3, enable a plug-in. The status of the plug-in changes from not installed to installed, and a unique identifier is set for this plug-in.

[0029] Step 4, the plug-in registers one or more services through the service registry, and other plug-ins obtain this service by registering and listening to the service registry.

[0030] Step 5, manage the service interfaces registered by all plug-ins to complete the publication and acquisition of the service interfaces.

[0031] The above method can be used to implement a service-oriented plug-in management platform. As Figure 1 shown, it is a dynamic component system written in the C++ language. In this system, the application is dynamically composed of many different (reusable) components (C++ program objects) and follows the service-oriented approach. Specifically, it includes the following content:

[0032] ① Design a platform soft bus and formulate a unified plug-in interaction standard to provide a standard model for the plug-ins, enabling them to be dynamically linked to the application. This is a development model that allows the application (dynamically) to be composed of many different (reusable) components. This model is as Figure 2 shown. It allows communication through services, and services are objects specific to between components. Among them: the plug-in is the most basic business unit; the service layer dynamically connects the plug-ins by providing a publish-find-bind model for C++ objects; the lifecycle layer is used to install, start, stop, update, and uninstall the plug-ins.

[0033] The plug-in is a C++-based dynamic link library, and its design includes resource files and metadata, as Figure 3 shown. The metadata can accurately describe the characteristics of the plug-in, enabling the plug-in management platform to manage it in various ways.

[0034] A service is an agreement rule between the provider and the user of the plug-in business function. The process of using a service includes the forms of discovering the service and reaching an agreement, that is, finding the corresponding service through the signature characteristics of the service. The plug-in registers one or more services (a service is usually a C++ class with only pure virtual methods) through the service registry, and other plug-ins obtain this service by registering and listening to the service registry, as Figure 4 shown;

[0035] ②Complete the life cycle management of the plug-ins, including installation, startup, stop, update, and uninstallation of the plug-ins. A plug-in has a unique identifier, which cannot be changed during the life cycle of the plug-in (even during plug-in updates). Uninstalling and reinstalling a plug-in must create a new unique identifier. Figure 5 This is a state transition diagram for the life cycle of a plug-in object: A plug-in has the following states (the states are dynamically changeable and can be converted into each other under specific conditions): UNINSTALLED; INSTALLED; RESOLVED; STARTING; STOPPING; ACTIVE. A plug-in can only execute code when it is in the STARTING, ACTIVE, or STOPPING state.

[0036] ③Manage all service interfaces registered by the plug-ins, and complete the publishing and acquisition of service interfaces. The provided methods allow plug-ins to: subscribe to events published by the framework; register service objects using the service registry of the framework; retrieve references to service objects from the service registry of the framework; obtain and publish service objects for referenced services; install new plug-ins in the framework; obtain a list of installed plug-ins in the framework; and obtain an object of a plug-in.

[0037] The general framework of the measurement and control software adopts the design concept of platform + plug-ins. From bottom to top, it is divided into three layers around the plug-in management platform: device management and data service layer, core and general business layer, and system business layer. Each layer of business is independent and interacts through the platform soft bus. The main design methods are as follows:

[0038] ①The design of the device management and data service layer mainly includes communication services, device management services, and data services.

[0039] ②The core and general business refers to the general business functions that are independent of specific software and are the business foundation of the entire framework; the communication service provides multiple communication modes (TCP, UDP, FTP, etc.), and various communication resources can be dynamically configured through configuration files. The framework platform dynamically initializes and allocates communication resources according to the configuration files when loading.

[0040] ③The system business consists of a group of business plug-ins. The business of each software is different, so the business plug-ins are also different.

[0041] The device management service provides the function of accessing extension data. All these extension data have been uniformly accessed and standardized through adapters. At the same time, the platform provides a set of unified rules to structurally describe the extension interfaces (XML), and can automatically generate extension code from the extension description files written according to these rules, and then perform unified adaptation management on these extension codes.

[0042] ④ The data service provides a unified data access interface to other business services in the system. Other services do not need to care about the specific data sources (Shentong database, local SQLite), thus realizing centralized data management and heterogeneous processing of data sources.

[0043] ⑤ General services refer to general functions independent of specific software. They include general services such as logging, system configuration, user permissions, parameter association relationships, runtime exception capture, dynamic system block diagram editing, as well as message services based on the publish / subscribe method and related services required for building C / S or B / S mode programs.

[0044] ⑥ The system services consist of a set of service plugins. When the software service capabilities need to be upgraded, only the relevant service plugins need to be upgraded or deployed; the plugins at other levels of the software do not require code modification and can adaptively complete the upgrade.

[0045] In addition, to achieve rapid development of plugins, a plugin development wizard can be designed and integrated into the QT development tool, as Figure 6 shown. The plugin development wizard presets several types of plugins. After selection, a code project is directly generated, and a plugin template is automatically created. It mainly includes the baseband data processing plugin template (CTI BBE ProcessPlugin), the system monitoring service client plugin template (CTI Business Plugin Client), the system monitoring service server plugin template (CTI Business Plugin Server), the general plugin template (CTIPlugin), and the extension processing class template (CTIDevice Plugin). This wizard tool can greatly reduce the entry threshold for writing plugins, and the coding personnel only need to focus on writing the business code without having to pay attention to the interaction details between the plugin and the platform.

[0046] In summary, the present invention uses the service-oriented design concept to implement a general plugin-based interaction platform. The platform takes plugins as the core, and both design and development are based on plugins. During deployment, different software systems only need to select the corresponding functional / business plugins for modular deployment. Through this plugin-based development and modular deployment architecture model, rapid customization of various software in the measurement and control field can be achieved. At the same time, the plugin repository can be accumulated and enriched to form highly reusable products or functions, thus quickly and stably completing the software development process. The present invention can be applied to the rapid development of various software in the ground station of aerospace measurement and control.

[0047] In addition to the above embodiments, the present invention may have other implementation manners. All technical solutions using equivalent substitution or equivalent transformation forms fall within the protection scope required by the present invention.

Claims

1. A service-oriented plug-in management method, characterized in that: The following steps are involved: Step 1: Make the plug-in to be managed into a dynamic link library, which contains resource files and metadata. The metadata is used to describe the characteristics of the plug-in; Step 2: Manage the status of the plug-in. The status of the plug-in includes: not installed, installed, completed, started, stopped, and active. The plug-in can only execute code when the status is started, stopped, or active. Step 3: Enable a plug-in, change the plug-in status from Not Installed to Installed, and set a unique identifier for the plug-in; Step 4: The plug-in registers one or more services through the service registry, and other plug-ins obtain this service by registering and listening to the service registry; Step 5: Manage the service interfaces registered by all plug-ins and complete the publishing and acquisition of service interfaces.

2. A service-oriented plug-in management method according to claim 1, characterized in that: The plug-in is automatically generated through templates, which include baseband data processing plug-in templates, system monitoring service client plug-in templates, system monitoring service server plug-in templates, common plug-in templates and extension processing class templates.

Images