A method and device for flexibly encapsulating a network element platform webservice interface into a standard soap interface

Abstract

The present invention discloses a method and device for flexibly encapsulating a webservice interface of a network element platform as a standard soap interface, the method comprising: S01, operation and maintenance personnel configure the device, configure the webservice interface address and port of the encapsulated network element platform; S02, perform a connectivity test, perform a connectivity test on the webservice protocol URL address of the corresponding acquisition and control source, and the test method is a simulated file transfer tool; S03, perform parameter processing; S04, perform message management; S05, perform an FTL test, if the FTL test result fails, proceed to S06, if the FTL test result succeeds, proceed to S07; S06, if the FTL test result fails, re-perform parameter processing configuration; S07, if the FTL test result succeeds, complete the capability packaging work. The present invention realizes a flexible and configurable packaging function, and compared with the previous customized development packaging capability, it can quickly deliver network capabilities and greatly improve network operation and maintenance capabilities.

Description

Technical Field

[0001] The invention relates to the field of network element encapsulation, in particular to a method and a device for flexibly encapsulating a network element platform webservice interface into a standard soap interface. Background Art

[0002] The acquisition and control platform is a unified collection and network operation centralized control platform for professional operation data promoted by various operators. It is connected to various types of professional network elements through network element direct connection, network element platform, device agent, etc., and supports the upper-layer application's operational requirements for service activation, network maintenance and management by encapsulating webservice into soap interface. Among the professional network element platforms, the number of webservice interfaces is the largest. The traditional method of encapsulating webservice interfaces is: "First define a single webservice interface protocol, and then the developer customizes and develops the interface, converts the webservice interface into a soap interface protocol, and thus realizes the encapsulation of interface capabilities", which is relatively inefficient and easily causes non-standard encapsulation interfaces. Summary of the invention

[0003] In order to solve the problems existing in the prior art, the present invention provides a method and device for flexibly encapsulating the webservice interface of a network element platform into a standard soap interface, which can quickly encapsulate the webservice interface of various platform control capabilities into standard soap interface capabilities, realize flexible and configurable encapsulation functions, and can quickly deliver network capabilities compared to previous customized development of encapsulation capabilities, greatly improving network operation and maintenance capabilities.

[0004] To achieve the above object, the present invention adopts the following technical solutions:

[0005] In one embodiment of the present invention, a method for flexibly encapsulating a network element platform webservice interface into a standard soap interface is proposed, and the method includes:

[0006] S01, the operation and maintenance personnel configure the device and configure the webservice interface address and port of the encapsulated network element platform;

[0007] S02. Conduct connectivity test, and conduct connectivity test on the webservice protocol URL address of the corresponding acquisition and control source. The test method is to simulate the file transfer tool;

[0008] S03, performing parameter processing;

[0009] S04, perform message management;

[0010] S05, perform FTL test, if the FTL test result fails, go to S06, if the FTL test result succeeds, go to S07;

[0011] S06, FTL test result failed, re-configure the parameters;

[0012] S07. If the FTL test result is successful, the capability packaging work is completed.

[0013] Further, the S01 includes:

[0014] S011. Operation and maintenance personnel perform device configuration work and configure network element information of the network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to achieve basic information management of the network element platform;

[0015] S012. The operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content; detailed content of the protocol, mainly including webservice protocol URL address information, which is used for network element platform message management.

[0016] S013. The operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, match the configured network element information and protocol information one by one, and generate unique acquisition and control source information.

[0017] Further, the S02 includes:

[0018] S021, if the connectivity test fails, the acquisition and control source activation status is not activated, and the device configuration is manually modified;

[0019] S022, if the connectivity test is successful, the acquisition and control source is enabled and the process goes to S03 for parameter handling.

[0020] Further, the S03 includes:

[0021] S031. Set the virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated;

[0022] S032, configuring the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding encapsulation;

[0023] S033. Encapsulate the command content in different devices into the same virtual instruction code, so as to achieve one encapsulation capability corresponding to the webservice interface capabilities of different manufacturers;

[0024] S034. The encapsulated message structure is a unified standard message.

[0025] Further, the S04 includes:

[0026] S041. Establish communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured in S01;

[0027] S042. Access the acquisition and control source URL address information, obtain the network element platform webservice message, and automatically fill in the actual instruction content for interacting with the network element platform;

[0028] S043. Modify the required encapsulation capability variable information in the message and replace it with the parameter information of S03 of the encapsulation capability.

[0029] Furthermore, the S043 associates different acquisition and control source URL address information, calls the network element platform webservice interface address, automatically obtains the wsdl file content published by the address, and the webservice message information of multiple vendors' network element platforms, thereby completing the unified encapsulation capability work for multiple vendors' network element platforms.

[0030] In one embodiment of the present invention, a device for flexibly encapsulating a webservice interface of a network element platform into a standard soap interface is also proposed, and the device includes:

[0031] Device configuration module 110, operation and maintenance personnel perform device configuration, configure the webservice interface address and port of the encapsulated network element platform;

[0032] Connectivity test module 120, performs connectivity test, performs connectivity test on the webservice protocol URL address of the corresponding acquisition and control source, and the test method is to simulate the file transfer tool;

[0033] The parameter processing module 130 performs parameter processing;

[0034] The message management module 140 performs message management;

[0035] The FTL test module 150 performs an FTL test. If the FTL test result fails, the process proceeds to S06. If the FTL test result succeeds, the process proceeds to S07.

[0036] Failed module 160, FTL test result failed, re-configure the parameter handling;

[0037] Success module 170: If the FTL test result is successful, the capability packaging work is completed.

[0038] Furthermore, the device configuration module 110 includes:

[0039] Basic information management module 111, operation and maintenance personnel perform device configuration work, configure network element information of network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to realize basic information management of network element platform;

[0040] Encapsulation address and port module 112, the operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content;

[0041] The acquisition and control source information generation module 113 and the operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, match the configured network element information and the protocol information one by one, and generate unique acquisition and control source information.

[0042] Furthermore, the connectivity test module 120 includes:

[0043] If the connectivity test fails in module 121, the acquisition and control source is enabled in the disabled state and the device configuration is manually modified;

[0044] If the connectivity test is successful in the connection success module 122, the acquisition and control source is enabled and the parameter processing module 130 is entered to perform the parameter processing process.

[0045] Furthermore, the parameter handling module 130 includes:

[0046] Parameter setting module 131, setting virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated;

[0047] The virtual instruction configuration module 132 configures the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding encapsulation;

[0048] The virtual instruction code encapsulation module 133 encapsulates the command content in different devices into the same virtual instruction code, so as to achieve one encapsulation capability corresponding to the webservice interface capability of different manufacturers;

[0049] The message standard unification module 134 encapsulates the message structure into a unified standard message.

[0050] Furthermore, the message management module 140 includes:

[0051] The communication establishment module 141 establishes communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured by the device configuration module 110;

[0052] The message acquisition module 142 accesses the acquisition and control source URL address information, obtains the network element platform webservice message, and automatically fills in the actual instruction content for interacting with the network element platform;

[0053] The parameter information replacement module 143 modifies the encapsulation capability variable information required in the message and replaces it with the parameter information of the encapsulation capability parameter handling module 130 .

[0054] Furthermore, the parameter information replacement module 143 associates different acquisition and control source URL address information, calls the network element platform webservice interface address, automatically obtains the wsdl file content published by the address, and the webservice message information of multiple vendor network element platforms, thereby completing the unified encapsulation capability of multiple vendor network element platforms.

[0055] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned flexible encapsulation network element platform webservice interface is implemented as a standard soap interface method.

[0056] In one embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program for executing a method for flexibly encapsulating a webservice interface of a network element platform into a standard soap interface. Beneficial Effects

[0057] The present invention realizes the automatic conversion of webservice messages into json interface devices; can quickly realize the webservice interface encapsulation of network element platforms, and can complete the interface encapsulation of a large number of network element platforms through configuration; establishes unified standard messages with network element platforms of various manufacturers to shield manufacturer differences; and realizes the standardized soap format message of the input parameter list through parameter processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 It is a flow chart of a method for flexibly encapsulating a network element platform webservice interface into a standard soap interface according to the present invention;

[0059] Figure 2 This is a schematic diagram of the network element information page for configuring the network element platform;

[0060] Figure 3 It is a schematic diagram of the webservice address and port page of the encapsulated network element platform;

[0061] Figure 4 It is a schematic diagram of the webservice protocol URL address information protocol content page;

[0062] Figure 5 This is a schematic diagram of the parameter handling page;

[0063] Figure 6 This is a schematic diagram of the message management page;

[0064] Figure 7 This is a schematic diagram of the FTL test page;

[0065] Figure 8 This is a screenshot of a page for configuring parameter information and generating standard message information in an embodiment;

[0066] Fig. 9 This is a screenshot of the page that obtains the file content of the protocol parameter address through the FTL test;

[0067] Fig.10 It is a screenshot of the page where the operator completes the encapsulation of the webservice interface of the network element platform into a standard soap interface;

[0068] Fig.11 It is a schematic diagram of the structure of a device for flexibly encapsulating a webservice interface of a network element platform into a standard soap interface according to the present invention;

[0069] Fig.12 It is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0070] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0071] Those skilled in the art know that the embodiments of the present invention can be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure can be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0072] According to the implementation mode of the present invention, a method and device for flexibly encapsulating the webservice interface of the network element platform into a standard soap interface are proposed, which can quickly encapsulate the webservice interface of various platform control capabilities into standard soap interface capabilities, realize flexible and configurable encapsulation functions, and can quickly deliver network capabilities compared with the previous customized development of encapsulation capabilities, greatly improving network operation and maintenance capabilities.

[0073] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0074] like Figure 1 As shown, the method includes:

[0075] S01, the operation and maintenance personnel configure the device and configure the webservice interface address and port of the encapsulated network element platform;

[0076] S02. Conduct connectivity test, and conduct connectivity test on the webservice protocol URL address of the corresponding acquisition and control source. The test method is to simulate the file transfer tool;

[0077] S03, performing parameter processing;

[0078] S04, perform message management;

[0079] S05, perform FTL test, if the FTL test result fails, go to S06, if the FTL test result succeeds, go to S07;

[0080] S06, FTL test result failed, re-configure the parameters;

[0081] S07. If the FTL test result is successful, the capability packaging work is completed.

[0082] The S01 includes:

[0083] S011. Operation and maintenance personnel perform device configuration work and configure network element information of the network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to achieve basic information management of the network element platform;

[0084] S012. The operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content; detailed content of the protocol, mainly including the webservice protocol URL address information, which is used for network element platform message management.

[0085] S013. The operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, match the configured network element information and protocol information one by one, and generate unique acquisition and control source information.

[0086] The S02 includes:

[0087] S021, if the connectivity test fails, the acquisition and control source activation status is not activated, and the device configuration is manually modified;

[0088] S022, if the connectivity test is successful, the acquisition and control source is enabled and the process goes to S03 for parameter handling.

[0089] The S03 includes:

[0090] S031. Set the virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated;

[0091] S032, configuring the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding encapsulation;

[0092] S033. Encapsulate the command content in different devices into the same virtual instruction code, so as to achieve one encapsulation capability corresponding to the webservice interface capabilities of different manufacturers;

[0093] S034. The encapsulated message structure is a unified standard message.

[0094] The S04 includes:

[0095] S041. Establish communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured in S01;

[0096] S042. Access the acquisition and control source URL address information, obtain the network element platform webservice message, and automatically fill in the actual instruction content for interacting with the network element platform;

[0097] S043. Modify the required encapsulation capability variable information in the message and replace it with the parameter information of S03 of the encapsulation capability.

[0098] The S043 associates different acquisition and control source URL address information, calls the network element platform webservice interface address, automatically obtains the wsdl file content published by the address, and the webservice message information of multiple vendors' network element platforms, thereby completing the unified encapsulation capability work for multiple vendors' network element platforms.

[0099] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0100] In order to explain more clearly the above-mentioned flexible encapsulation of the network element platform webservice interface as a standard soap interface method, a specific embodiment is used for illustration below. However, it is worth noting that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation on the present invention.

[0101] S01. The operation and maintenance personnel configure the device and configure the webservice interface address and port of the encapsulated network element platform.

[0102] S011. Operation and maintenance personnel perform device configuration work and configure network element information on the network element platform, such as Figure 2 The configuration content shown includes the network element name, management IP, network element type, network element category, network element model, node, manufacturer, and profession, realizing the basic information management of the network element platform.

[0103] S012, the operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, such as Figure 3 The configuration content shown includes the protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content. The detailed content of the protocol is as follows Figure 4 As shown, it mainly includes webservice protocol URL address information, which is used for network element platform message management.

[0104] S013. Operation and maintenance personnel configure the required encapsulation network element platform acquisition and control source information, such as Figure 4 As shown, the device will Figure 2 Configure network element information and Figure 3 The protocol information is mapped one by one to generate unique acquisition and control source information.

[0105] After the device configuration is completed, S02, connectivity test, is performed. The connectivity test is mainly to test the webservice protocol URL address of the corresponding acquisition and control source. The test method is to simulate the file transfer tool (hereinafter referred to as: Curl) to call the URL address and judge the connectivity test result. The judgment logic is as follows:

[0106] S021. If the connectivity test fails, the acquisition and control source activation status is not enabled, and the operation and maintenance personnel are required to modify the device configuration.

[0107] S022, if the connectivity test is successful, the acquisition and control source is enabled and enters S03 for parameter handling.

[0108] S03, perform parameter processing, such as Figure 5As shown, set the virtual instruction code, virtual instruction name, profession, configuration protocol type, real instruction type, equipment series, real instruction code, and variable requirement data of the message to be encapsulated. The device configures the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction entry and the virtual instruction encoding encapsulation. At the same time, the device encapsulates the command content in different devices into the same virtual instruction code, realizing that one encapsulation capability corresponds to the webservice interface capability of different manufacturers. At the same time, the message structure encapsulated by the device is a unified standard message, with the following examples:

[0109] {

[0110] "SUID": "",

[0111] "ID": "",

[0112] "SPAD": ""

[0113] }

[0114] S04, message management, through parameter identification function, such as Figure 6 As shown, through the device account and password information in the acquisition and control source protocol information configured in S01, the device establishes communication with the network element platform, accesses the acquisition and control source URL address information, obtains the network element platform webservice message, and automatically fills in the actual instruction content for interacting with the network element platform, and then modifies the required encapsulation capability variable information in the message to replace it with the parameter information of S03 of the encapsulation capability. In this step, by associating different acquisition and control source URL address information, the device calls the network element platform webservice interface address, automatically obtains the wsdl file content published by the address, obtains the webservice message information of multiple vendors' network element platforms, and completes the unified encapsulation capability work for multiple vendors' network element platforms.

[0115] S05, perform packaging capability test operations, such as Figure 6 Fast-Than-Light (FTL test) is shown, and the capability test operation is entered, such as Figure 7 As shown, input parameter processing information and perform FTL test. If the FTL test result fails, perform S06 operation and re-configure the parameter processing. If the FTL test result succeeds, perform S07 operation to complete the capability packaging work.

[0116] The operator configures the network element platform information on the device, as shown in Table 1:

[0117]

[0118] The operator configures the network element platform protocol information in the device, as shown in Table 2:

[0119]

[0120] like Figure 8 As shown, the operator configures parameter information in the device and generates standard message information;

[0121] like Fig. 9 As shown, the device obtains the file content of the protocol parameter address through the FTL test;

[0122] The detailed message content is as follows:

[0123] <soapenv:Envelope

[0124] xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance"

[0125] xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema"

[0126] xmlns:soapenv="http: / / schemas.xmlsoap.org / soap / envelope / "

[0127] xmlns:sus="http: / / SUService.chinatelecom.com">

[0128] <soapenv:header / >

[0129] <soapenv:body>

[0130] <sus:invoke soapenv:encodingstyle="http: / / schemas.xmlsoap.org / soap / encoding / ">

[0131] <xmlData xsi:type="soapenc:string"

[0132] xmlns:soapenc="http: / / schemas.xmlsoap.org / soap / encoding / ">

[0133] <request>

[0134] <PK_Type>

[0135] <name> GET_DATA< / name>

[0136] <code>501< / code>

[0137] < / PK_Type>

[0138] <info>

[0139] <suid> ${SUID}< / suid>

[0140] <devicelist>

[0141] <device id="${ID}"><#list SPID as key>

[0142] <spid> ${key}< / spid>

[0143] < / #list>

[0144] < / device>

[0145] < / devicelist>

[0146] < / info>

[0147] < / request>

[0148]

[0149] < / sus:invoke>

[0150] < / soapenv:body>

[0151]

[0152] like Fig.10 As shown, the operator can complete the encapsulation of the network element platform webservice interface into a standard soap interface by confirming and publishing in the device.

[0153] The calling parameters are:

[0154] {"SUID":"F6-54-BE-5D-45-3E","ID":"9999999","SPID":"1999999999"}

[0155] By converting the standard message, the message for calling the network element platform is generated as follows, thus completing the entire encapsulation process.

[0156] <soapenv:Envelope

[0157] xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance"

[0158] xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema"

[0159] xmlns:soapenv="http: / / schemas.xmlsoap.org / soap / envelope / "

[0160] xmlns:sus="http: / / SUService.chinatelecom.com">

[0161] <soapenv:header / >

[0162] <soapenv:body>

[0163] <sus:invoke soapenv:encodingstyle="http: / / schemas.xmlsoap.org / soap / encoding / ">

[0164] <xmlData xsi:type="soapenc:string"

[0165] xmlns:soapenc="http: / / schemas.xmlsoap.org / soap / encoding / ">

[0166] <request>

[0167] <PK_Type>

[0168] <name> GET_DATA< / name>

[0169] <code>501< / code>

[0170] < / PK_Type>

[0171] <info>

[0172] <suid> F6-54-BE-5D-45-3E< / suid>

[0173] <devicelist>

[0174] <device id="9999999"><#list SPID as key>

[0175] <spid> 1999999999< / spid>

[0176] < / #list>

[0177] < / device>

[0178] < / devicelist>

[0179] < / info>

[0180] < / request>

[0181]

[0182] < / sus:invoke>

[0183] < / soapenv:body>

[0184]

[0185] Based on the same inventive concept, the present invention also proposes a device for flexibly encapsulating the webservice interface of a network element platform as a standard soap interface. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated. The term "module" used below can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0186] Fig.11 This is a schematic diagram of the structure of the device for flexibly encapsulating the webservice interface of the network element platform into a standard soap interface. Fig.11 As shown, the device comprises:

[0187] Device configuration module 110, operation and maintenance personnel perform device configuration, configure the webservice interface address and port of the encapsulated network element platform;

[0188] Connectivity test module 120, performs connectivity test, performs connectivity test on the webservice protocol URL address of the corresponding acquisition and control source, and the test method is to simulate the file transfer tool;

[0189] The parameter processing module 130 performs parameter processing;

[0190] The message management module 140 performs message management;

[0191] The FTL test module 150 performs an FTL test. If the FTL test result fails, the process proceeds to S06. If the FTL test result succeeds, the process proceeds to S07.

[0192] Failed module 160, FTL test result failed, re-configure the parameter handling;

[0193] Success module 170: If the FTL test result is successful, the capability packaging work is completed.

[0194] The device configuration module 110 includes:

[0195] The basic information management module and operation and maintenance personnel perform device configuration work and configure the network element information of the network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to achieve basic information management of the network element platform;

[0196] Encapsulation address and port module, operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content;

[0197] The acquisition and control source information generation module and the operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, match the configured network element information and protocol information one by one, and generate unique acquisition and control source information.

[0198] The connectivity test module 120 includes:

[0199] If the connectivity test fails in the module or the connectivity test fails, the acquisition and control source activation status is not activated, and the device configuration needs to be modified manually;

[0200] If the module is successfully connected and the connectivity test is successful, the acquisition and control source is enabled and the parameter processing module 130 is transferred to perform the parameter processing process.

[0201] The parameter handling module 130 includes:

[0202] Parameter setting module, setting virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated;

[0203] The virtual instruction configuration module configures the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding and encapsulation;

[0204] The virtual instruction encoding encapsulation module encapsulates the command content on different devices into the same virtual instruction encoding, realizing one encapsulation capability corresponding to the webservice interface capabilities of different manufacturers;

[0205] The message standard unified module and the encapsulated message structure are unified standard messages.

[0206] The message management module 140 includes:

[0207] The communication establishment module establishes the communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured by the device configuration module 110;

[0208] The message acquisition module accesses the acquisition and control source URL address information, obtains the webservice message of the network element platform, and automatically fills in the actual instruction content for interacting with the network element platform;

[0209] The parameter information replacement module modifies the encapsulation capability variable information required in the message and replaces it with the parameter information of the encapsulation capability parameter handling module 130.

[0210] The parameter information replacement module associates different acquisition and control source URL address information, calls the network element platform webservice interface address, automatically obtains the wsdl file content published by the address and the webservice message information of multiple vendors' network element platforms, and completes the unified encapsulation capability of multiple vendors' network element platforms.

[0211] It should be noted that although the above detailed description mentions several modules that flexibly encapsulate the webservice interface of the network element platform as a standard soap interface device, this division is only exemplary and not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules described above can be concretized in one module. Conversely, the features and functions of one module described above can be further divided into multiple modules for concretization.

[0212] Based on the above invention concept, Fig.12 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220. When the processor 220 executes the computer program 230, the aforementioned flexible encapsulation network element platform webservice interface is implemented as a standard soap interface method.

[0213] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium, which stores a computer program for executing the aforementioned method of flexibly encapsulating the webservice interface of the network element platform into a standard soap interface.

[0214] The present invention realizes the automatic conversion of webservice messages into json interface devices; can quickly realize the webservice interface encapsulation of network element platforms, and can complete the interface encapsulation of a large number of network element platforms through configuration; establishes unified standard messages with network element platforms of various manufacturers to shield manufacturer differences; and realizes the standardized soap format message of the input parameter list through parameter processing.

[0215] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.

[0216] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0217] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0218] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0219] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0220] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0221] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0222] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0223] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

[0224] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for flexibly encapsulating a network element platform webservice interface as a standard soap interface, characterized in that: The method includes: S01. The operation and maintenance personnel configure the device and configure the webservice interface address and port of the encapsulated network element platform, including: S011. Operation and maintenance personnel perform device configuration work and configure network element information of the network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to achieve basic information management of the network element platform; S012. The operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content; S013. The operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, match the configured network element information and protocol information one by one, and generate unique acquisition and control source information; S02. Conduct connectivity test, and conduct connectivity test on the webservice protocol URL address of the corresponding acquisition and control source. The test method is to simulate the file transfer tool; S03. Perform parameter processing, including: S031. Set the virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated; S032, configuring the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding encapsulation; S033. Encapsulate the command content in different devices into the same virtual instruction code, so as to achieve one encapsulation capability corresponding to the webservice interface capabilities of different manufacturers; S034, the encapsulated message structure is a unified standard message; S04. Perform message management, including: S041. Establish communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured in S01; S042. Access the acquisition and control source URL address information, obtain the network element platform webservice message, and automatically fill in the actual instruction content for interacting with the network element platform; S043, modify the required encapsulation capability variable information in the message and replace it with the parameter information of S03 of the encapsulation capability; by associating the URL address information of different acquisition and control sources, calling the webservice interface address of the network element platform, automatically obtaining the wsdl file content published by the address and the webservice message information of multiple vendors' network element platforms, and completing the unified encapsulation capability work for multiple vendors' network element platforms; S05, perform a quick processing test, if the quick processing test result fails, proceed to S06, if the quick processing test result succeeds, proceed to S07; S06. Rapidly process the test result failure and reconfigure the parameter processing; S07. If the rapid processing test results are successfully completed, the capability packaging work is completed.

2. The flexible encapsulation network element platform webservice interface according to claim 1 is a standard soap interface method, characterized in that: The S02 includes: S021, if the connectivity test fails, the acquisition and control source activation status is not activated, and the device configuration is manually modified; S022, if the connectivity test is successful, the acquisition and control source is enabled and the process goes to S03 for parameter handling.

3. A device for flexibly encapsulating a webservice interface of a network element platform as a standard soap interface, characterized in that: The device includes: The device configuration module and operation and maintenance personnel perform device configuration and configure the webservice interface address and port of the encapsulated network element platform, including: The basic information management module and operation and maintenance personnel perform device configuration work and configure the network element information of the network element platform, including: network element name, management IP, network element type, network element category, network element model, node, manufacturer, and specialty, to achieve basic information management of the network element platform; Encapsulation address and port module, operation and maintenance personnel configure the required encapsulation network element platform webservice address and port, including: protocol template name, protocol type, major, protocol purpose, protocol version, and protocol content; The acquisition and control source information generation module and the operation and maintenance personnel configure the required encapsulated network element platform acquisition and control source information, and match the configured network element information and protocol information one by one to generate unique acquisition and control source information; Connectivity test module, conduct connectivity test, conduct connectivity test on the webservice protocol URL address of the corresponding acquisition and control source, and the test method is to simulate the file transfer tool; Parameter processing module, performs parameter processing, including: Parameter setting module, setting virtual instruction code, virtual instruction name, major, configuration protocol type, real instruction type, device series, real instruction code, and variable requirement data of the message to be encapsulated; The virtual instruction configuration module configures the real instructions of different manufacturers with the same encapsulation capability to correspond to the same virtual instruction, thereby realizing the corresponding relationship between the real instruction and the virtual instruction encoding and encapsulation; The virtual instruction encoding encapsulation module encapsulates the command content on different devices into the same virtual instruction encoding, realizing one encapsulation capability corresponding to the webservice interface capabilities of different manufacturers; The message standard unified module and the encapsulated message structure are unified standard messages; Message management module, performs message management, including: The communication establishment module establishes the communication between the device and the network element platform through the device account and password information in the acquisition and control source protocol information configured by the device configuration module; The message acquisition module accesses the acquisition and control source URL address information, obtains the webservice message of the network element platform, and automatically fills in the actual instruction content for interacting with the network element platform; The parameter information replacement module modifies the encapsulation capability variable information required in the message and replaces it with the parameter information of the parameter handling module of the encapsulation capability; by associating the URL address information of different acquisition and control sources, calling the webservice interface address of the network element platform, automatically obtaining the wsdl file content published by the address and the webservice message information of multiple vendors' network element platforms, and completing the unified encapsulation capability work of multiple vendors' network element platforms; A fast processing test module performs a fast processing test. If the fast processing test result fails, the module is transferred to a failure module. If the fast processing test result succeeds, the module is transferred to a success module. Failed module, quickly handles test result failures and reconfigures parameter handling; Success module, if the rapid processing test results are successful, the capability packaging work is completed.

4. The flexible encapsulation network element platform webservice interface according to claim 3 is a standard soap interface device, characterized in that: The connectivity test module includes: If the connectivity test fails in the module or the connectivity test fails, the acquisition and control source activation status is not activated, and the device configuration needs to be modified manually; If the module is successfully connected and the connectivity test is successful, the acquisition and control source activation status is enabled, and the parameter processing module is entered for the parameter processing process.

5. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 2 is implemented.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 2.

Images