WO2018077115A1

WO2018077115A1 - Plug-in implementation method, apparatus, and computer storage medium

Info

Publication number: WO2018077115A1
Application number: PCT/CN2017/106968
Authority: WO
Inventors: 董艳丽; 汪星
Original assignee: 上海中兴软件有限责任公司
Priority date: 2016-10-27
Filing date: 2017-10-20
Publication date: 2018-05-03
Also published as: CN108011733B; CN108011733A

Abstract

The present disclosure relates to a plug-in implementation method, apparatus, and computer storage medium, said method comprising: a first system receiving operation request information from a second system, said first system being a system corresponding to a first plug-in service formed by means of a micro-service by a plug-in separated from the second system; the first system calling a predetermined basic service according to the operation request information; the first system sending to the second system the operation result obtained after calling the predetermined basic service. The plug-in of the present disclosure exists in the form of a micro-service by means of micro-service technology; the plug-in existing in the form of a service has a complete system environment, and therefore can interact with a second system without existing in embedded form in the second system; the process of interaction does not need to occupy a process of the second system and does not present any threat to the security and reliability of the second system, thus solving the problems of the prior art. (FIG. 1)

Description

Method, device and computer storage medium for implementing plug-in

Technical field

The present disclosure relates to the field of communications, and in particular, to a method, an apparatus, and a computer storage medium for implementing the plug-in.

Background technique

With the development of NFV (Network Function Virtualization) standards and the practice of NFV commercialization, the general VNFM architecture (General Virtualised Network Function Managent, VNFM-G) is becoming more and more Many operators are used in their virtualization architecture. VNFM-G needs to manage different product lines, even different vendor network elements, which requires a dedicated VNFM plug-in (referred to as VNFM-S). When VNFM-G manages VNF (Virtualised Network Function) and sends notifications to EM (Element Managent), it needs some special adapters to ensure the normal operation. The adaptation work is done by VNFM-S.

The commonly used script mode plug-in is an abstract interface defined by VNFM-G. The specific implementation is provided in VNFM-S. The interface between VNFM-G and VNFM-S is one-way, and VNFM-S can only be called by VNFM-G.

The scripted VNFM-S is deployed inside the VNFM-G and shares the VNFM-G process. Resources are limited by the VNFM-G process. The reliability of VNFM-S directly affects the process safety and stability of VNFM-G. For example: VNFM-S failure may cause VNFM-G to be unavailable. In addition, the VNFM-S developed by script mode has a single development form and is limited by the system framework of VNFM-G.

The above just uses VNFM-G as an example to illustrate that existing plug-ins exist in the entire system by script. However, the process of sharing the system needs to be shared, so the resources are limited by the system process, and the reliability of the plug-in directly affects the system. The security and stability of the process pose a greater threat to system security and stability.

Summary of the invention

The embodiment of the invention provides a method and a device for implementing the plug-in, which solves the problems existing in the prior art and makes the system more secure and stable.

In one aspect, an embodiment of the present invention provides a method for implementing a plug-in, including: a first system receiving operation request information from a second system, wherein the first system is a plug-in that is separated from the second system. a system corresponding to the first plug-in service formed by the micro-service technology; the first system invokes a predetermined basic service according to the operation request information; the first system sends an operation result obtained after calling the predetermined basic service to the The second system.

According to an exemplary embodiment, the first system invokes a predetermined basic service according to the operation request information, including: the first system installs and registers the predetermined basic service, so that the predetermined basic service is in Available status.

In another aspect, an embodiment of the present invention further provides an apparatus for implementing a plug-in, including: a receiving module, configured to receive operation request information from a second system, where the first system is separated from the second system a plug-in module corresponding to the first plug-in service formed by the micro-service technology; a calling module, configured to invoke a predetermined basic service according to the operation request information; and a return module, configured to: obtain an operation result obtained after the predetermined basic service is invoked Sent to the second system.

According to an exemplary embodiment, the implementation device of the plug-in further includes: a determining module, configured to determine whether the second plug-in service corresponding to the operation request information exists in the plug-in service set; and a service setting module, configured to In the case of the second plugin service, the second plugin service is installed and registered to make the second plugin service available.

According to an exemplary embodiment, the calling module is configured to install and register the predetermined base service to put the predetermined base service in a usable state.

In the embodiment of the present invention, the plug-in exists in the form of a service through the micro-service technology, and the plug-in exists in the form of a service, and has a complete system environment, so that the plug-in can interact with the second system, and does not exist in the second system in an embedded manner. The interaction process does not need to occupy the second system process, and does not pose any threat to the security and reliability of the second system, and the second system process is more secure and stable.

DRAWINGS

1 is a flow chart showing a method for implementing a plug-in in a first embodiment of the present invention;

2 is a schematic structural view of an apparatus for implementing an insert in a second embodiment of the present invention;

3 is a schematic diagram showing a preferred structure of an apparatus for implementing an insert in a second embodiment of the present invention;

4 is a schematic diagram of a plug-in system based on a microservice technology in a third embodiment of the present invention;

5 is a flow chart of instantiation of a VNF in a third embodiment of the present invention;

6 is a flowchart of termination of a VNF in a fourth embodiment of the present invention;

FIG. 7 is a flow chart of a value-added service service usage in an embodiment of the present invention.

detailed description

In order to solve the following problems in the prior art: existing plug-ins exist in the entire system in a script mode. However, processes that share the system are required, so resources are limited by system processes, and the reliability of the plug-ins directly affects system processes. The invention is safe and stable, and poses a great threat to system security and stability. The present invention provides a method and an apparatus for implementing the plug-in. The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The following embodiments of the present invention can operate on devices embedded in plug-ins in various operating systems, for example, can be run on devices such as PCs or servers, but are not limited to the specific devices described above.

First embodiment

A first embodiment of the present invention provides a method for implementing a plug-in. The process of the method is as shown in FIG. 1 and includes steps S102 to S106:

S102. The first system receives operation request information from the second system, where the first system is a system corresponding to the first plug-in service formed by the micro-service technology by the plug-in separated from the second system. The first system of this embodiment is configured to include a system corresponding to the plug-in service and a system corresponding to the system corresponding to the predetermined basic service. Of course, when implemented, the setting of the first system may be different from the first embodiment of the present invention, and may be The system corresponding to the plug-in service is set up in a manner corresponding to the system corresponding to the basic service.

As long as the existing plug-ins are embedded in the system to run, the plug-ins can be separated. Therefore, as long as the plug-in separation system can be used as the second system.

S104. The first system invokes a predetermined basic service according to the operation request information. For a predetermined basic service, it can be a general service corresponding to any basic function, and the service can be called by the plug-in service, and the plug-in service completes the function corresponding to the plug-in service by calling one or more predetermined basic services.

S106. The first system sends an operation result obtained after the predetermined basic service is called to the second system.

The operation result corresponds to the operation request information. Because the plug-in service requested by the second system is different, the predetermined basic service called by the plug-in service is different, and the first system finally returns to the second system is an execution result of the plug-in service, for example, There is a ticketing system client. The original system operation of the client is a plug-in form. Now, the ticketing system client is divided into a first system and a second system, and the first system is from the original ticketing system client. A system in which each plug-in separated in the end exists in the form of a plug-in service. When the user operates in the second system, it will trigger some plug-in service work of the first system, and call some predetermined basic services to complete the function of the entire plug-in. For example, the function of purchasing a soft seat ticket exists in the form of a plug-in service, and when the plug-in service works, it is required to call a predetermined basic service such as a purchaser ID card information, a purchaser user name, etc., according to the predetermined basic services called. To achieve this function of purchasing a soft seat ticket, the final purchase of a soft seat ticket is an operation result.

In the embodiment of the present invention, the plug-in exists in the form of a service through the micro-service technology, and the plug-in exists in the form of the service, and has a complete system environment, so that the plug-in can interact with the second system, and does not exist in the second system in an embedded manner. The interaction process does not need to occupy the second system process, and does not pose any threat to the security and reliability of the second system, and solves the following problems in the prior art: the existing plug-ins are all present in a script mode. In the system, however, the process of sharing the system is required, so the resources are limited by the system process, and the reliability of the plug-in directly affects the security and stability of the system process, posing a greater threat to system security and stability.

In the process of the implementation, after the first system receives the operation request information from the second system, it is also required to determine whether there is a corresponding second plug-in service, so the first system determines whether there is a second plug-in service corresponding to the operation request in the plug-in service set; In the absence of the second plug-in service, the first system installs and registers the second plug-in service to make the second plug-in service available, so that the plug-in service exists in the first system; In the case of the plugin service, the first system directly triggers the second plugin service call according to the operation request information. Book the basic service. In the specific implementation, the predetermined basic service needs to be installed and registered to make the predetermined basic service in a usable state.

After the first system sends an operation result obtained after the predetermined basic service is called to the second system, if it is desired to stop the corresponding operation, the second system transmits the operation termination information to the first system. After the first system receives the operation termination information from the second system, the first system determines whether there is an unsubscribed predetermined basic service; if there is a predetermined basic service that is not terminated, the first system terminates all the predetermined basic services, and then, The scheduled basic service that has been terminated is deregistered; if it is directly detected that there is no unsubscribed predetermined basic service, the first system directly cancels all the terminated basic services that have been terminated. Finally, the corresponding plug-in service is terminated and logged off according to the operation termination information.

In a specific implementation, the foregoing second system may be a VNFM-G, and may of course be other systems.

Second embodiment

A second embodiment of the present invention provides an apparatus for implementing a plug-in. The structure of the apparatus is as shown in FIG. 2, and includes: a receiving module 10, configured to receive operation request information from a second system, where the first system is a slave The plug-in separated by the second system is a system corresponding to the first plug-in service formed by the micro-service technology; the calling module 20 is coupled with the receiving module 10, and is configured to invoke a predetermined basic service according to the operation request information; returning the module 30, and calling the module 20 coupling for transmitting an operation result obtained after invoking a predetermined basic service to the second system.

FIG. 3 is a schematic diagram of a preferred structure of the implementation device of the plug-in, which may further include: a determining module 40, coupled to the receiving module 10, for determining whether there is a second plug-in service corresponding to the operation request in the plug-in service set; the service setting module 50 And coupled to the determining module 40 and the calling module 20, for installing and registering the second plug-in service in the absence of the second plug-in service, so that the second plug-in service is in a usable state.

In implementation, the calling module can also be used to install and register a predetermined underlying service to make the intended underlying service available.

The function modules of the above-mentioned plug-in implementation device also have other functions, for example, if the user wants to stop the corresponding operation, the receiving module is further configured to receive operation termination information from the second system; the determining module is further configured to determine whether there is an The terminated basic service; the calling module is further configured to terminate all the predetermined basic services in the case where there is a predetermined basic service that is not terminated; and to cancel all the terminated predetermined bases in the case where there is no unscheduled predetermined basic service The service setting module is further configured to terminate and cancel the first plug-in service and the second plug-in service according to the operation termination information after canceling all the terminated scheduled basic services.

Third embodiment

The third embodiment of the present invention takes VNFM-G (equivalent to the second system) as an example, and provides a plug-in based on micro-service technology, which can use the orchestration system according to requirements (one aspect of the first system in the second embodiment, Equivalent to the service setting module), the deployment is flexible, and it can be released in association with the main system or as a stand-alone system. The following is a description of the VNFM plug-in (VNFM-S) of the communication network.

The VNFM-S of this embodiment exists in the form of a plug-in service. In addition to the VNFM-G service, it runs in a separate process and interacts with the VNFM-G based on an interface scheme, such as an HTTP RESTful interface.

Each plug-in service defines explicit boundaries, can be written in different programming languages, can be deployed independently through automated deployment, and can be dynamically scaled.

The plug-in service (not written in the first system, actually calling the module is the function of the plug-in service) is equivalent to the adapter of VNFM-G and VNF/EM. After the successful programming of the VNF, the VNF lifecycle change notification is sent. , adapt to VNF / EM interface. A VNF consists of a number of predetermined base services, and the plug-in service is reserved for the underlying service (ie, the plug-in service exists before the scheduled basic service) to assist the VNFM-G in completing the VNF lifecycle management. Plug-in services exist in the form of shared services, that is, multiple VNF instances can share a plug-in service instance.

The service discovery system (one aspect of the first system in the second embodiment, corresponding to the judgment module) manages the plug-in service and the predetermined basic service instance information, and discovers to the service through an interface scheme (for example, HTTP Restful) when the service is started. The system registers the service; when the service is stopped, the service is logged out of the service discovery system.

The installation of the plugin service is part of the VNF instantiation process. The uninstallation of the plugin service is part of the termination of the VNF instance. In the VNF instantiation process, the plug-in service instance is first created according to the plug-in service description information, and registered in the service discovery system, and the scheduled basic service relies on the plug-in service to complete its deployment.

The plug-in service is decoupled from VNFM-G. The management of the plug-in service is independent of VNFM-G, and the management is more flexible. The installation and uninstallation of a plug-in service does not affect the normal operation of VNFM-G and other plug-in services. Plug-in service exceptions will not affect VNFM-G and other plug-in service functions, and the security is better.

Based on the service-based scalability feature, you can monitor the load of the plug-in service and dynamically scale it. For example, the orchestration process needs to instantiate 2000 VNFs (that is, there are 2000 processes). If the plug-in memory and CPU exceed the load limit, multiple plug-in services can be popped up to achieve load balancing.

The implementation of the above technical solution will be further described in detail below with reference to the accompanying drawings.

4 is a schematic diagram of a function of a plug-in system (corresponding to the first system of the second embodiment) based on a micro-service technology, including a service deployment module (equivalent to a service setting module), a service discovery module (corresponding to a judgment module), and a plug-in service ( Equivalent to calling the module), interacting with VNFM-G (equivalent to the second system) throughout the process to achieve VNF/EM (equivalent to the result of the operation).

VNFM-G is a universal VNFM, which is a virtual network function management system that completes the life cycle management of the VNF. The service deployment module describes the life cycle of the package management service according to the service information, and the service discovery module registers and manages the service instance information. And provide external access interface; plug-in service, provided by the equipment manufacturer, is a special type of VNF special adapter, used to assist VNFM-G to complete VNF lifecycle management, to achieve VNF / EM management interface adaptation.

Figure 5 is a VNF instantiation flow diagram (including plug-in installation) including steps 1 through 9.

Step 1. Parse the VNF package information.

In step 2, the VNFM-G initiates an instantiation process.

Step 3: The VNFM-G queries the service discovery module for the registration information of the plug-in service.

Step 4: Query the registration information of the plugin service.

Step 5. If the plugin service does not exist, install the plugin service through the service deployment module; if the plugin service exists, continue with steps 7, 8, and 9.

Step 6. Register the plugin service with the service discovery.

Step 7. Install the scheduled basic service through the service deployment module.

Step 8. Register a predetermined basic service with the service discovery module.

Step 9. Inform the VNF to instantiate the result, and the instantiation ends.

Figure 6 is a VNF termination flow diagram (including plug-in uninstallation). The plug-in is uninstalled when the VNF is terminated. If the scheduled basic services of all VNFs associated with the plug-in service have been terminated, the plug-in will be uninstalled and the relevant information is deleted from the service registration module. information. Includes steps 1 through 6.

Step 1. The VNFM-G initiates a VNF termination operation.

In step 2, the service deployment module terminates the predetermined basic service.

Step 3: The notification service discovery module logs out the predetermined basic service information.

In step 4, VNFM-G checks if the plugin service is dependent on other predetermined base services, and if so, terminates the operation; if not, proceeds to the next step.

In step 5, the service deployment module terminates the plugin service.

In step 6, the service discovery module is notified to cancel the plug-in service information, and the termination operation ends.

In this embodiment, the VNFM-S is equivalent to a slave system of the VNFM-G, and a slave system is established by the microservice technology. The VNFM-S based on micro-service technology can be arranged and arranged according to the requirements, and can be deployed flexibly. It can be released in association with VNFM-G, published in association with VNF, or released as a stand-alone system. The micro-service-based VNFM-S is independent of the VNFM-G process and has no impact on each other, and has better security and stability. The interface between VNFM-S and VNFM-G can realize bidirectional interconnection. VNFM-G can notify VNFM-S to perform adaptation processing, and VNFM-S can also report processing progress to VNFM-G. In addition, the development language and system framework of VNFM-S can be determined by the plug-in provider, and has nothing to do with VNFM-G, thus achieving independent development. The VNFM-S service can be dynamically scaled by monitoring service performance.

Fourth embodiment

The fourth embodiment of the present invention uses big data analysis as an example to describe the working process of the plug-in service.

Big data analysis software (equivalent to the second system) can analyze the user's big data and generate an analysis report. If the user purchases the corresponding value-added service (equivalent to the plug-in service), the value-added service can be used to obtain a more detailed analysis. result. Value-added services can be deployed and deployed using the plug-in services of micro-service technology. Figure 7 shows the value-added service service usage process, including steps 1 through 7.

Step 1. The user initiates a big data processing request.

In step 2, the basic analysis service generates a processing report.

In step 3, the basic analysis service requests the value-added service A to process. In this process, you need to call some services that you need to use.

In step 4, the value-added service A generates a high-value report for the basic analysis service.

In step 5, the basic analysis service requests the value added service B to process.

In step 6, the value-added service B generates a high-value report for the basic analysis service.

Step 7. The basic analysis service summarizes the report and presents it to the user.

As can be seen from the fourth embodiment of the present invention, the present invention can be applied to various fields. As long as it is a script form or a plug-in embedded in the main system, it can be implemented by a plug-in service of the micro service technology.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems can also be used with the teaching based on the teachings herein. The structure required to construct such a system is apparent from the above description. Moreover, the invention is not directed to any particular programming language. It is to be understood that the invention may be embodied in a variety of programming language, and the description of the specific language has been described above in order to disclose the preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects reside in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the embodiments, and each of the claims as a separate embodiment of the invention.

Those skilled in the art will appreciate that the modules in the client in the embodiment can be adaptively changed and placed in one or more clients different from the embodiment. The modules in the embodiments can be combined into one module, and further they can be divided into a plurality of sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the client are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

Moreover, those skilled in the art will appreciate that while some embodiments described herein include other embodiments Some of the features are included in the description, but not in other features, but combinations of features of the different embodiments are intended to be within the scope of the invention. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components loaded with the ordered web address in accordance with an embodiment of the present invention. . The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

Industrial applicability

The technical solution provided by the embodiment of the present invention can be applied to the field of communications. The plug-in provided by the technical solution of the embodiment of the present invention exists in the form of a service through a micro-service technology, and the plug-in existing through the service form has a complete system environment, and thus can interact with the second system without being embedded. Exist in the second system, the interaction process does not need to occupy the second system process, and does not pose any threat to the security and reliability of the second system, and the second system process is more secure and stable.

Claims

A method for implementing a plugin, comprising:

The first system receives operation request information from the second system, wherein the first system is a system corresponding to the first plug-in service formed by the micro-service technology by the plug-in separated from the second system;

The first system invokes a predetermined basic service according to the operation request information;

The first system sends an operation result obtained after invoking the predetermined basic service to the second system.
The method of implementing the plug-in according to claim 1, wherein after the first system receives the operation request information from the second system, the method further includes:

Determining, by the first system, whether the second plug-in service corresponding to the operation request information exists in the plug-in service set;

In the case where the second plug-in service does not exist, the first system installs and registers the second plug-in service to make the second plug-in service in a usable state.
The method for implementing the plug-in according to claim 1 or 2, wherein the first system invokes a predetermined basic service according to the operation request information, including:

The first system installs and registers the predetermined base service to place the predetermined base service in a usable state.
The method for implementing the plug-in according to claim 1, wherein after the first system sends the operation result obtained after the calling the predetermined basic service to the second system, the method further includes:

The first system receives operation termination information from the second system;

The first system terminates and deregisters the first plug-in service and the second plug-in service according to the operation termination information.
The method of implementing the plug-in according to claim 4, wherein the method further comprises: before the first system terminates and deregisters the first plug-in service and the second plug-in service according to the operation termination information, the method further comprising:

Determining, by the first system, whether there is a predetermined basic service that is not terminated;

In the case where there is a predetermined basic service that is not terminated, the first system terminates all scheduled basic services and cancels all terminated scheduled basic services;

In the absence of a predetermined base service that is not terminated, the first system logs out all of the terminated base services that have been terminated.
The method of implementing the plug-in of claim 1, wherein the second system is a general virtual network management system VNFM-G.
A device for implementing a plug-in, comprising:

a receiving module, configured to receive operation request information from the second system, wherein the first system is a system corresponding to the first plug-in service formed by the micro-service technology by the plug-in separated from the second system;

Calling a module, configured to invoke a predetermined basic service according to the operation request information;

And returning to the module, configured to send an operation result obtained after invoking the predetermined basic service to the second system.
The device for implementing the plug-in according to claim 7, further comprising:

a determining module, configured to determine whether the second plug-in service corresponding to the operation request information exists in the plug-in service set;

The service setting module is configured to install and register the second plug-in service in the absence of the second plug-in service, so that the second plug-in service is in a usable state.
An apparatus for implementing an insert according to claim 7 or 8, wherein

The calling module is configured to install and register the predetermined base service to place the predetermined base service in a usable state.
An apparatus for implementing an insert according to claim 8, wherein

The receiving module is further configured to receive operation termination information from the second system;

The service setting module is further configured to terminate and deregister the first plug-in service and the second plug-in service according to the operation termination information.
The device for implementing the plug-in according to claim 10, further comprising:

The determining module is further configured to determine whether there is a predetermined basic service that is not terminated;

The calling module is further configured to terminate all predetermined basic services in the case where there is a predetermined basic service that is not terminated; and to cancel all the terminated basic services that are terminated in the absence of the unscheduled predetermined basic service.