CN105791346B

CN105791346B - Cross-platform solution method for realizing SOAP interface, service and network equipment

Info

Publication number: CN105791346B
Application number: CN201410808566.7A
Authority: CN
Inventors: 成明
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2014-12-22
Filing date: 2014-12-22
Publication date: 2020-07-14
Anticipated expiration: 2034-12-22
Also published as: CN105791346A

Abstract

The invention discloses a cross-platform solution for realizing a SOAP interface, which comprises the following steps of receiving a SOAP request message sent by a SOAP client, analyzing and converting the received SOAP request message to generate a MM L human-machine language command in a system, sending the generated MM L command to a service processor, receiving a MM L command response message returned by the service processor after the service processor completes the processing of the MM L command, converting the MM L command response message returned by the service processor into a SOAP response message and returning the SOAP response message to the client.

Description

Cross-platform solution method for realizing SOAP interface, service and network equipment

Technical Field

The invention relates to the technical field of network data transmission, in particular to a cross-platform solution for realizing a SOAP interface, a SOAP service equipment end and network equipment.

Background

SOAP (Simple Object Access Protocol) is a standardized communication specification, and is mainly used in web services, and it appears to simplify the flow of extracting data from a web Server, so that it does not need to spend time to format a Page, and different applications can exchange data with each other in an XM L (extensible Markup language) format through HTTP (Hypertext transfer Protocol), so that it is unrelated to programming language, platform and hardware.

The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.

Disclosure of Invention

The invention mainly aims to provide a cross-platform solution for realizing a SOAP interface, a SOAP service equipment terminal and network equipment, and aims to support the customization of a SOAP access server or a client under different operating system platforms such as WINNT/L INUX/CGS L and the like.

In order to achieve the above object, the present invention provides a cross-platform solution for implementing a SOAP interface, where the cross-platform solution for implementing a SOAP interface includes the following steps:

receiving a SOAP request message sent by a SOAP client;

analyzing and converting the received SOAP request message to generate a human-computer language MM L command in the system;

sending the generated MM L command to a service processor, and receiving an MM L command response message returned by the service processor when the service processor completes the processing of the MM L command;

and converting the MM L instruction response message returned by the service processor into a SOAP response message and returning the SOAP response message to the SOAP client.

Preferably, the step of analyzing and converting the received SOAP request message to generate a man-machine language MM L command inside the system includes:

analyzing the received SOAP request message, and stripping an HTTP protocol header of the SOAP request message;

and acquiring XM L data of the SOAP request message after the HTTP protocol header is stripped, finishing conversion from the SOAP to the MM L command, parameter name and parameter value according to the XM L data, and generating the MM L command in the system.

Preferably, the step of converting the MM L instruction response message returned by the service handler into a SOAP response message to be returned to the client includes:

according to the received MM L instruction response message returned by the service processor, the conversion from MM L to SOAP message name, parameter name and parameter value is completed, and an XM L response message is generated;

loading an HTTP protocol header on the XM L response message;

and after the loading is finished, sending the SOAP response message loaded with the HTTP protocol header to the SOAP client.

In addition, to achieve the above object, the present invention further provides a SOAP service device, where the SOAP service device includes:

the request message receiving module is used for receiving the SOAP request message sent by the SOAP client;

the analysis conversion module is used for analyzing and converting the received SOAP request message to generate a human-computer language MM L command in the system;

a response message receiving module, configured to send the generated MM L command to a service processor, and receive, when the service processor completes processing of the MM L command, a MM L command response message returned by the service processor;

and the response message conversion module is used for converting the MM L instruction response message returned by the service processor into a SOAP response message and returning the SOAP response message to the SOAP client.

Preferably, the analysis conversion module includes:

the analysis processing unit is used for analyzing the received SOAP request message and stripping an HTTP (hyper text transport protocol) header of the SOAP request message;

and the MM L conversion unit is used for acquiring XM L data of the SOAP request message after the HTTP protocol header is stripped, completing the conversion from the SOAP to the MM L command, the parameter name and the parameter value according to the XM L data, and generating the MM L command in the system.

Preferably, the response message conversion module includes:

the SOAP conversion unit is used for completing the conversion from the MM L to the SOAP message name, the parameter name and the parameter value according to the received MM L instruction response message returned by the service processor and generating an XM L response message;

the loading unit is used for receiving the generated XM L response message and loading an HTTP protocol header on the XM L response message;

and the sending unit is used for sending the SOAP response message loaded with the HTTP protocol header to the SOAP client after the HTTP protocol header is loaded.

In addition, in order to achieve the above object, the present invention further provides a network device, which includes a SOAP client, a transaction handler, and a SOAP service device as described above,

the SOAP client includes:

the request message sending module is used for sending the SOAP request message to the SOAP service equipment terminal;

the receiving module is used for receiving an XM L response message which is sent by the SOAP service equipment end and is loaded with the HTTP protocol header after the SOAP service equipment end completes the HTTP protocol header loading;

the service processor comprises:

and the MM L command processing module is used for finishing the processing of the MM L command and returning a response message to the receiving SOAP service equipment end when receiving the MM L command sent by the SOAP service equipment end.

The invention generates MM L command in the system by analyzing and converting the SOAP request message, so that the service processor completes the processing of MM L command, and converts MM L command response message returned by the service processor into SOAP response message and returns the SOAP response message to the SOAP client.

Drawings

FIG. 1 is a flowchart illustrating an embodiment of a cross-platform solution for implementing a SOAP interface according to the present invention;

FIG. 2 is a detailed flowchart of step S102 in FIG. 1;

FIG. 3 is a detailed flowchart of step S104 in FIG. 1;

FIG. 4 is a diagram of a conventional serialization process for SOAP interface implementation;

FIG. 5 is a functional block diagram of an embodiment of a SOAP service device side according to the present invention;

FIG. 6 is a schematic diagram of a refinement function module of the analysis transformation module of FIG. 5;

FIG. 7 is a block diagram illustrating a detailed function of the response message conversion module of FIG. 5;

FIG. 8 is a functional block diagram of a network device according to an embodiment of the present invention;

FIG. 9 is a diagram illustrating detailed functional modules of an embodiment of the SOAP client in FIG. 8;

fig. 10 is a schematic data flow diagram of a network device according to the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The invention provides a cross-platform solution for realizing a SOAP interface, and referring to FIG. 1, in an embodiment, the cross-platform solution for realizing the SOAP interface comprises the following steps:

step S101, receiving a SOAP request message sent by a SOAP client;

in this preferred embodiment, the request message receiving module receives a SOAP request message sent by a SOAP client, and specifically, the lightweight web server webserver completes receiving and caching an HTTP message of the SOAP request message.

In the preferred embodiment, the request message receiving module is roughly divided into two layers: a TCP/IP access layer and an HTTP protocol processing layer. The TCP/IP access layer realizes a communication architecture (the TCP/IP API interfaces of different platforms are different) according to API (Application programming interface) of different operating systems and platforms; the HTTP protocol processing layer is a common part because the HTTP application protocol has no difference on different platforms. Therefore, only the TCP/IP access layer codes of different platforms and the common HTTP protocol processing layer are selected for compiling, so that a new platform can be supported and developed, and the platform is not coupled with other platform codes.

Step S102, analyzing and converting the received SOAP request message to generate a human-machine language MM L command in the system;

in the preferred embodiment, the analysis processing unit of the analysis conversion module analyzes the received SOAP request message, strips off the HTTP protocol header carrying SOAP, and sends an XM L (extensible markup language) data request to the MM L conversion unit of the analysis conversion module, the MM L conversion unit completes the conversion of the command, parameter name and MM L parameter value from SOAP to MM L according to the tree information configuration of the SOAP request in the local configuration file after receiving the XM L request, and generates an MM L command inside the system.

In this embodiment, the HTTP protocol and the SOAP protocol are implemented hierarchically, and a system component integrating HTTP and SOAP is not used, and such an architecture is a necessary condition for implementing a cross-platform common code.

Step S103, sending the generated MM L command to a service processor, and receiving an MM L command response message returned by the service processor after the service processor completes the processing of the MM L command;

in the preferred embodiment, the service handler completes processing of the MM L instruction and returns an MM L response message to the parsing conversion module.

Step S104, the MM L instruction response message returned by the service processor is converted into a SOAP response message and returned to the SOAP client.

In this embodiment, the analysis conversion module receives a response message returned by the service processor, completes the conversion from MM L to SOAP, and sends a SOAP response message to the SOAP client.

In an embodiment, as shown in fig. 2, on the basis of the embodiment of fig. 1, in this embodiment, the step S102 includes:

step S1021, analyzing the received SOAP request message, and stripping the HTTP protocol header of the SOAP request message;

in this embodiment, specifically, the lightweight web server webserver completes HTTP message analysis on a SOAP request message, strips an HTTP protocol header carrying SOAP, and sends an XM L data request to the analysis conversion unit.

Step S1022, obtaining XM L data of the SOAP request message after completing the HTTP protocol header stripping, and completing the conversion from the SOAP to the MM L, the parameter name, and the parameter value according to the XM L data, thereby generating an MM L command inside the system.

In the preferred embodiment, after receiving the XM L request, the parsing and converting module completes conversion of the command from SOAP to MM L, the parameter name, and the MM L parameter value according to the tree information configuration of the SOAP request in the local configuration file, and generates an MM L command inside the system.

In the preferred embodiment, the conversion may be based on tree information configuration to convert SOAP messages to command lines.

In an embodiment, as shown in fig. 3, on the basis of the embodiment of fig. 1, in this embodiment, the step S104 includes:

step S1041, according to the received MM L command response message returned by the service processor, completing the conversion from MM L to SOAP message name, parameter value, and generating XM L response message;

in the preferred embodiment, the parsing and converting module receives a response message returned by the service processor, completes the conversion from MM L to SOAP, and generates an XM L response message, and sends the generated XM L response message to the request message receiving module.

Step S1042, loading an HTTP protocol header on the XM L response message;

in this embodiment, the request message receiving module receives the generated XM L response message, and loads an HTTP protocol header on the XM L response message to complete the assembly of the HTTP protocol.

Step S1043, after the HTTP protocol header is loaded, sending the SOAP response message with the HTTP protocol header loaded to the SOAP client.

In this embodiment, the SOAP client receives the HTTP protocol XM L response message assembled by the request message receiving module.

Compared with the prior art, the invention has the advantages that the extraction of the SOAP command information is completed and the SOAP response message is converted into the process of internal command by requesting the SOAP message to inquire the conversion configuration through the SOAP message, and the traditional technology replaces the traditional technology to extract data through the positive and negative serialization of the SOAP message and a data structure, so that the SOAP interface can be realized without reconstructing a compiled version, in many scenes with little change to a conversion frame, such as expanding a new command interface with a similar format, increasing new parameters, changing conversion rules of internal and external parameters and the like, the data conversion between the SOAP and the internal MM L can be realized completely through modifying the configuration without reconstructing the version, and the application maintenance is very convenient.

Referring to fig. 5, in an embodiment, in a preferred embodiment, the SOAP service device further includes:

a request message receiving module 101, configured to receive a SOAP request message sent by the SOAP client 2;

in this preferred embodiment, the request message receiving module 101 receives a SOAP request message sent by the SOAP client 2, and specifically, the lightweight web server webserver completes receiving and caching an HTTP message of the SOAP request message.

In the preferred embodiment, the request message receiving module 101 is roughly divided into two layers: a TCP/IP access layer and an HTTP protocol processing layer. The TCP/IP access layer realizes a communication architecture (the TCP/IP API interfaces of different platforms are different) according to API (Application programming interface) of different operating systems and platforms; the HTTP protocol processing layer is a common part because the HTTP application protocol has no difference on different platforms. Therefore, only the TCP/IP access layer codes of different platforms and the common HTTP protocol processing layer are selected for compiling, so that a new platform can be supported and developed, and the platform is not coupled with other platform codes.

The analysis conversion module 102 is used for analyzing and converting the received SOAP request message to generate a human-computer language MM L command inside the system;

in the preferred embodiment, the parsing unit of the parsing and converting module 102 parses the received SOAP request message, strips off the HTTP protocol header carrying SOAP, and sends an XM L (extensible Markup language) data request to the MM L converting unit of the parsing and converting module 102. the MM L converting unit completes the conversion of the command, parameter name, and MM L parameter value from SOAP to MM L according to the tree information configuration of the SOAP request in the local configuration file after receiving the XM L request, and generates an MM L command inside the system.

A response message receiving module 103, configured to send the generated MM L command to a service processor, and receive, when the service processor completes processing of the MM L command, a MM L command response message returned by the service processor;

in the preferred embodiment, the service handler completes processing of the MM L instruction and returns a MM L response message to the parsing conversion module 102 it should be understood that no changes are required to the service handler in extending the SOAP interface for the service functions already supported by the system.

And the response message conversion module 104 is configured to convert the MM L instruction response message returned by the service processor into a SOAP response message and return the SOAP response message to the SOAP client.

In this embodiment, the analysis conversion module 102 receives a response message returned by the service processor, completes the conversion from MM L to SOAP, and sends a SOAP response message to the SOAP client.

In an embodiment, as shown in fig. 6, on the basis of the above embodiment of fig. 5, in this embodiment, the analysis conversion module 102 includes:

an analysis processing unit 1021, configured to analyze the received SOAP request message and strip an HTTP protocol header of the SOAP request message;

The MM L conversion unit 1022 is configured to acquire XM L data of the SOAP request message after the HTTP protocol header is stripped, complete conversion from SOAP to an MM L command, a parameter name, and a parameter value according to the XM L data, and generate an MM L command inside the system.

In the preferred embodiment, after receiving the XM L request, the parsing and converting module 102 completes conversion of the command from SOAP to MM L, the parameter name, and the MM L parameter value according to the tree information configuration of the SOAP request in the local configuration file, and generates an MM L command inside the system.

In an embodiment, as shown in fig. 7, on the basis of the above embodiment of fig. 5, in this embodiment, the response message conversion module 104 includes:

a SOAP conversion unit 1041, configured to complete conversion from the MM L to a message name, a parameter name, and a parameter value of the SOAP according to the received MM L instruction response message returned by the service processor, and generate an XM L response message;

in the preferred embodiment, the parsing and converting module 102 receives a response message returned by the service processor, completes the conversion from MM L to SOAP, and generates an XM L response message, and sends the generated XM L response message to the request message receiving module 101.

A loading unit 1042, configured to receive the generated XM L response message, and load an HTTP protocol header on the XM L response message.

In this embodiment, the request message receiving module 101 receives the generated XM L response message, and loads an HTTP protocol header on the XM L response message to complete the assembly of the HTTP protocol.

A sending unit 1043, configured to send, after the HTTP protocol header is loaded, an XM L response message in which the HTTP protocol header is loaded to the SOAP client 2.

In this embodiment, the SOAP client 2 receives the HTTP protocol XM L response message assembled by the request message receiving module 101.

The present invention further provides a network device 10, and referring to fig. 8, in an embodiment, the network device 10 includes a SOAP client 2, a service processor 3 and the SOAP service device 1 as described above,

referring to fig. 9, the SOAP client 2 includes:

a request message sending module 201, configured to send a SOAP request message to the SOAP service device 1;

a receiving module 202, configured to receive, when the SOAP service equipment terminal 1 completes HTTP protocol header loading, an XM L response message sent by the SOAP service equipment terminal 1 and having the HTTP protocol header loaded;

the service processor 3 is configured to complete processing of the MM L command when receiving the MM L command sent by the SOAP service device end 1, and return a response message to the receiving SOAP service device end 1.

In this embodiment, the service processor 3 sets a processing framework according to the MM L format, and if the internal instruction is already supported, the service processing module does not need to modify the task and can directly complete the processing.

Referring to fig. 10, in an embodiment, the data flow of the network device 10 is as follows:

step 501: the SOAP client 2 sends the SOAP request message to the SOAP service equipment terminal 1, and the lightweight webserver of the SOAP service equipment terminal 1 completes analysis processing of the HTTP message.

Step 502, webserver strips HTTP protocol header carrying SOAP and sends XM L data request to the parsing conversion module 102.

Step 503, after receiving the XM L request, the parsing and converting module 102 completes conversion of the command from SOAP to MM L, the parameter name, and the MM L parameter value according to the tree information configuration of the SOAP request in the local configuration file, and generates an MM L command inside the system.

In step 504, the service processor 3 completes the processing of the MM L command and returns an MM L response message to the parsing conversion module 102.

Step 505, the analysis and conversion module 102 receives the response message returned by the service processor 3, completes the conversion from MM L to SOAP, and generates an XM L response message, and sends the generated XM L response message to the webserver.

Step 506, the webserver receives the generated XM L response message, finishes loading the HTTP protocol header on the XM L response message and sends the assembled HTTP protocol XM L response message to the SOAP client 2.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A cross-platform solution for realizing a Simple Object Access Protocol (SOAP) interface is characterized by comprising the following steps of:

receiving a SOAP request message sent by a SOAP client;

analyzing the received SOAP request message, and stripping a hypertext transfer protocol (HTTP) protocol header of the SOAP request message;

obtaining XM L data of the SOAP request message after the HTTP protocol header is stripped, and completing conversion from SOAP to MM L, parameter names and parameter values according to the XM L data to generate MM L commands in the system;

loading an HTTP protocol header on the XM L response message;

2. A SOAP service device side, wherein the SOAP service device side includes:

a MM L conversion unit for obtaining XM L data of the SOAP request message after completing HTTP protocol header stripping, and according to the data

The XM L data completes the conversion of the command, the parameter name and the parameter value from SOAP to MM L, and generates an MM L command inside the system;

the system comprises a generating unit used for generating XM L response messages, a loading unit used for receiving the generated XM L response messages and loading HTTP protocol headers on the XM L response messages, and a sending unit used for sending the SOAP response messages loaded with the HTTP protocol headers to the SOAP client after the HTTP protocol headers are loaded.

3. A network device, characterized in that the network device comprises a SOAP client, a traffic handler and the SOAP service device side of claim 2,

the SOAP client includes:

the service processor comprises: